Token refresh does not work

The problem is related to #32. Unfortunately, it is not obvious to implement token refresh when a library is used by another library (dask -> pyarrow -> fsspec -> gcsfs). It would be amazing to implement more prone token refresh.
Here is an exception that we get when the job runs longer than an hour:
gcsfs version is 2023.12.2.post1
HttpError: Invalid Credentials, 401
File /opt/conda/lib/python3.10/site-packages/dask_expr/_expr.py:3727, in _execute_task()

File /opt/conda/lib/python3.10/site-packages/dask/dataframe/io/parquet/core.py:97, in __call__()

File /opt/conda/lib/python3.10/site-packages/dask/dataframe/io/parquet/core.py:645, in read_parquet_part()

File /opt/conda/lib/python3.10/site-packages/dask/dataframe/io/parquet/core.py:646, in <listcomp>()

File /opt/conda/lib/python3.10/site-packages/dask/dataframe/io/parquet/arrow.py:641, in read_partition()

File /opt/conda/lib/python3.10/site-packages/dask/dataframe/io/parquet/arrow.py:1774, in _read_table()

File /opt/conda/lib/python3.10/site-packages/dask/dataframe/io/parquet/arrow.py:264, in _read_table_from_path()

File /opt/conda/lib/python3.10/site-packages/pyarrow/parquet/core.py:341, in __init__()

File ~/.../.venv/lib/python3.10/site-packages/pyarrow/_parquet.pyx:1250, in pyarrow._parquet.ParquetReader.open()
   1248
   1249         with nogil:
-> 1250             check_status(builder.Open(self.rd_handle, properties, c_metadata))
   1251
   1252         # Set up metadata

File ~/.../.venv/lib/python3.10/site-packages/pyarrow/types.pxi:88, in pyarrow.lib._datatype_to_pep3118()
     86 """
     87 try:
---> 88     char = _pep3118_type_map[type.id()]
     89 except KeyError:
     90     return None

File /opt/conda/lib/python3.10/site-packages/fsspec/spec.py:1844, in read()

File /opt/conda/lib/python3.10/site-packages/fsspec/caching.py:69, in _fetch()

File /opt/conda/lib/python3.10/site-packages/gcsfs/core.py:1850, in _fetch_range()

File /opt/conda/lib/python3.10/site-packages/fsspec/asyn.py:118, in wrapper()

File /opt/conda/lib/python3.10/site-packages/fsspec/asyn.py:103, in sync()

File /opt/conda/lib/python3.10/site-packages/fsspec/asyn.py:56, in _runner()

File /opt/conda/lib/python3.10/site-packages/gcsfs/core.py:1027, in _cat_file()

File /opt/conda/lib/python3.10/site-packages/gcsfs/core.py:437, in _call()

File /opt/conda/lib/python3.10/site-packages/decorator.py:221, in fun()

File /opt/conda/lib/python3.10/site-packages/gcsfs/retry.py:158, in retry_request()

File /opt/conda/lib/python3.10/site-packages/gcsfs/retry.py:123, in retry_request()

File /opt/conda/lib/python3.10/site-packages/gcsfs/core.py:430, in _request()

File /opt/conda/lib/python3.10/site-packages/gcsfs/retry.py:112, in validate_response()

HttpError: Invalid Credentials, 401

It seems that the problem should be fixed in #486

To refresh the token, we are calling the following sequence of methods on each request:

GCSFileSystem.def _request()
GCSFileSystem._get_headers()
GCSFileSystem.credentials.apply()
GCSFileSystem.credentials.maybe_refresh()

My suspicion is that GoogleCredentials.credentials == None is not obligatory when we deal with anon auth. Hence, we have to keep an explicit token type identifier.

It happens only if provide token string w/o refresh_token which is expected behavior:
def get_storage_options():
    # It works, but I don't know if it's the best way to do it
    #
    # Also, seems like need to specify the scope, although worked before.
    # Source: https://stackoverflow.com/questions/60401040/getting-invalid-scope-when-attempting-to-obtain-a-refresh-token-via-the-google-a
    credentials, _ = google.auth.default(
        scopes=["https://www.googleapis.com/auth/cloud-platform"]
    )
    if not credentials.valid:
        credentials.refresh(Request())
    return {
        "token": credentials.token,
    }

pd.read_parquet(..., storage_options=get_storage_options())

Relying on any other auth method fixes the problem.


[Fix #9429] Fix Style/NegatedIfElseCondition autocorrect to keep comments in correct branch

Closes #9429

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

@tejasbubane ping :-)

@koic @bbatsov Fixed.


Abstract findPage back into base/index.js

This PR is intended as a discussion starter on where we should be going next with the API vs model layer.
In this PR, I've finished the work of generalising the code in findPage. This included moving repeated pagination-specific code into base/utils.js#pagination and filter-specific code into base/utils.js#filtering. I also moved the parts that were model-specific options or custom code into model functions with horrific names like findPageDefaultOptions(), and then moved the remainder of findPage into base/index.js, calling out to the utils & model specific functions where needs be.
It's now reasonably clean, but there are a lot of steps (especially around option handling), 4 new model-specific functions (which are kinda awkward) and 2 utils that don't really make sense. There's clearly a lot more to do to get this to be sane - and then I'll add some more tests as well of course :wink:
Suggested changes
There are a few changes that I wanted to get a bit of feedback on before I forge ahead:
1) API-level option handling
More of the option handling should be done at the API level as described in #2758. At the API level, we need to add validation that the options provided are allowed and valid. Currently there is some option validation inside the model level but this is quite a weird mix between API-logic and model-logic. E.g. the model layer permits include (and uses it heavily), but it should be receiving withRelated - this is subsequently converted in multiple places. Instead, the API should be checking that the includes are correct and converting them to a withRelated call. Conversion from filters to joins & wheres should probably also happen in the API. That way the options passed to the model are the ones that bookshelf will understand.
Fundamentally, I think the API layer should speak api-ish and be able to translate it into bookshelfish. The model layer should only speak bookshelfish.
2) Remove weird filtering behaviour from models
Our findPage functionality does a slightly odd thing where it will fetch a related model (tag, author, role), use it to perform a filter, and then return that model in data.meta.filters. This has an additional annoyance in that it is inconsistent - if you request tag=thing, you get tags: [{thing}] and the same for roles. I could write an essay just on this bit, but the short version is that this behaviour is a bit of a hack so that themes get the data they need. Therefore it can be moved into the channel layer when we get there. Filtering is a whole other ball game and needs to be consistent and extensible - issue coming soon.
3) Split base/index.js up into feature-based 'plugins' or 'mixins'.
Bookshelf supports plugins but we don't necessarily need to go quite that far. However, it would make sense to have a set of mixins covering things like BREAD, pagination, filtering, validation etc. These would provide a place for the pagination & filtering code currently sat in a weird util. This is one of those things where it's hard to know what it looks like til you try it - but does it sound sane? I think care should be taken to not over-do it, but to split out logical groups of stuff.
4) Consider treating BR and EAD differently?
This is just something that's irking me - we treat all of our BREAD methods very similarly (both in the API and Model layer), but they are quite different. B&R need to fetch data with lots of options for determining what sort of data to get. The EAD parts have a lot less options but they change things. I don't even know how this would look - I was just throwing it out there to see if anyone else had any thoughts on refactoring this stuff?
Opinions, thoughts and ideas pretty please!!!

refs #2896

move default options / custom code into model functions
sepearate more pagination logic into base/utils.pagination
move most of the filtering logic into base/utils.filtering
move the remainder of findPage back into base/index.js and remove from posts/users&tags

:+1:
I think we agreed on using filter during the initial API discussion. The tag endpoint was probably missed/existed before that?
Am I understanding it right that 'plugins' or 'mixins' are different modules for different tasks in base/? Getting rid of util or at least change it's name is a good thing but I'm not sure if it makes sense to make it too sophisticated.
I don't see a benefit in splitting this up for all resources atm. I think that it would make it more complicated for new contributors to follow and there are more important refactors that could be done (e.g.: permission handling without a promise for every API method). The only module that would imo benefit from this is api/users.js. trasferOwnership, changePassword and sendInviteEmail could be worth a look.

I think we agreed on using filter during the initial API discussion. The tag endpoint was probably missed/existed before that?

Changing to use a filter param is a separate issue (and I've not written it yet :wink:)
I was talking more about fetching extra stuff & particularly putting it into data.meta.filters inside the model layer. Seems like it's totally in the wrong place to me, and double checking with others before I start moving it.

Am I understanding it right that 'plugins' or 'mixins' are different modules for different tasks in base/? Getting rid of util or at least change it's name is a good thing but I'm not sure if it makes sense to make it too sophisticated.

Yes, but they'd stay inside the model/base folder for now. I am just imagining a file called, e.g. pagination.js which contains defaults & knows how to do paginated fetches. Bookshelf has fetch and fetchAll perhaps we could have fetchPage. The point is to hide away bits of logic we don't need to care about to give focus back to the bits of Ghost which are more specific - like coping with draft and published posts.
Here are some other nice examples of plugins from the community.

This PR has had a bit of an update - I've now split the pagination functionality out into a fully unit-tested plugin. I think this is making sense.
My plan is to add a bit more documentation into the plugin & to key bits of the model layer and call this PR 'done' as it closes #2896.
Next step is probably a new PR to do the work to move the filter logic & option handling for the API described in #2758.
Alternatively I can keep pushing commits here until the utils file is gone.

I've updated this PR again :smile:
The new pagination.js file is both 100% unit tested and fully documented. (Try running grunt docs to see the nicely formatted version - will host this somewhere soon).
findPage is refactored out of individual models, and the code for handling pagination is tucked away in pagination.js.
I also started adding a bit more documentation to the base model file, as a little bit of an indicator of how I imagine clarifying the code in there and which parts are bookshelf settings, which parts override bookshelf functions, and which parts are Ghost-specific.
#2896 is now closable, I'm in two minds as to whether these 2 commits should be squashed or not.
Feedback would be very much appreciated.

:heart_eyes:

I'm in two minds as to whether these 2 commits should be squashed or not.

1 for squashing

Updated to move module.exports to the bottom & squashed the commits together


Missing IBusRegistry registration

Is this a bug report?
YES
It seems that IBusRegistry required by MassTransitHostedService  is registered only by MSDI extension (ServiceCollectionConfigurator) what makes it impossible to use Autofac with MT hosted service.

Not impossible, but not automatically configured at this point. This was an oversight.
If you register this type in your container for now, it will get you over this hump:
builder.RegisterType<BusRegistry>()
    .As<IBusRegistry>()
    .SingleInstance();


Memory leak around g_ProcessPersonaSemaphore

Describe the bug
Memory usage increases while the application is running.
The app crashes after a few hours.
Application logic: logOn -> gamesPlayed(440, true) -> createAuthSessionTicket(440) -> idle
With 500+ SteamUser instances.
Versions
4.28.4
18.5.0
Screenshots and Error Logs
C:\snapshot\yet-another-reward\node_modules\steam-user\components\friends.js:978
                        g_ProcessPersonaSemaphore.wait(async (release) => {
                                                       ^

RangeError: Maximum call stack size exceeded
(Use `node --trace-uncaught ...` to show where the exception was thrown)

Node.js v18.5.0

Or:
<--- Last few GCs --->

[5780:000001300C5465C0] 11460942 ms: Mark-sweep 2007.5 (2080.3) -> 1991.5 (2080.3) MB, 3335.5 / 0.5 ms  (average mu = 0.129, current mu = 0.030) allocation failure; scavenge might not succeed
[5780:000001300C5465C0] 11464521 ms: Mark-sweep 2007.5 (2080.3) -> 1991.5 (2080.3) MB, 3337.8 / 0.5 ms  (average mu = 0.099, current mu = 0.067) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

The problem exists even with one instance.
Try to start the instance normally, check the memory usage, then disable the handler here
https://github.com/DoctorMcKay/node-steam-user/blob/be05d16d10ee6655b46220f17e389bab890c91ee/components/friends.js#L1105
A simple immediate return would be sufficient.
Start the instance and check the memory usage now.


build fail with gcc10

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957365
tutorials/common/common_vaapi.cpp: In function 'int open_intel_adapter()':
tutorials/common/common_vaapi.cpp:100:10: error: 'string' is not a member of 'std'
100 |     std::string adapterPath = DRI_PATH;
|          ^~~~~~
tutorials/common/common_vaapi.cpp:27:1: note: 'std::string' is defined in header ''; did you forget to '#include '?
26 | #include "common_vaapi.h"
+++ |+#include
27 |
[  9%] Building C object contrib/ipp/CMakeFiles/ipp.dir/src/pccyuvmsw7.c.o
tutorials/common/common_vaapi.cpp:101:5: error: 'adapterPath' was not declared in this scope
101 |     adapterPath += DRI_NODE_RENDER;
|     ^~~~~~~~~~~
cd build/contrib/ipp && /usr/bin/cc  -Iapi/mediasdk_structures -Iapi/include -Ibuild -I/contrib/ipp/include -I_studio/shared/include -I_studio/shared/umc/core/umc/include  -DMFX_TRACE_ENABLE_STAT -DMFX_TRACE_ENABLE_TEXTLOG -msse4.2 -m64 -g -g -O2 -fdebug-prefix-map=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fPIC -Wall -Wformat -Wformat-security -Wno-deprecated-declarations -Wno-unknown-pragmas -Wno-unused  -DUNIX -D__USE_LARGEFILE64 -D_FILE_OFFSET_BITS=64 -DLINUX -DLINUX32 -DLINUX64 -DMSDK_BUILD=""  -DMFX_BUILD_INFO=""Linux-4.19.0-6-cloud-amd64 4.19.0-6-cloud-amd64 | GNU 10.0.1 | glibc 2.29"" -DMFX_API_VERSION="1.31" -DMFX_GIT_COMMIT="" -D_Y8 -D_ARCH_EM64T      -o CMakeFiles/ipp.dir/src/pccyuvmsw7.c.o   -c contrib/ipp/src/pccyuvmsw7.c
tutorials/common/common_vaapi.cpp:107:14: error: 'string' is not a member of 'std'
107 |         std::string curAdapterPath = adapterPath + std::to_string(nodeIndex + i);
|              ^~~~~~
tutorials/common/common_vaapi.cpp:107:14: note: 'std::string' is defined in header ''; did you forget to '#include '?
tutorials/common/common_vaapi.cpp:109:23: error: 'curAdapterPath' was not declared in this scope
109 |         int fd = open(curAdapterPath.c_str(), O_RDWR);
|                       ^~~~~~~~~~~~~~
make[3]: *** [tutorials/common/CMakeFiles/tutorials_common.dir/build.make:105: tutorials/common/CMakeFiles/tutorials_common.dir/common_vaapi.cpp.o] Error 1
make[3]: Leaving directory 'build'
make[2]: *** [CMakeFiles/Makefile2:1929: tutorials/common/CMakeFiles/tutorials_common.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....

@tjaalton : original issue on debian side is reported against 19.4.0 version. Can you, please, clarify:

Do you see the issue on the latest master/release?
Are you looking for the fix for 19.4.x release series or you need a fix in latest master/release?

Package: src:intel-mediasdk
Version: 19.4.0-1
Severity: normal
Tags: sid bullseye
User<EMAIL_ADDRESS>Usertags: ftbfs-gcc-10

20.2 still fails, and the file hasn't changed in master
getting a fix in master is good enough, I'll just patch the package until there's a new release

@eponomar : I don't get it why this issue was not caught by CI? we have gcc-10 compiler configuration... Do we need to update to latest gcc-10.2 (from current gcc-10.0) to see it?

Actually this issue means that #include <string> is missed, but it was already added in this commit:
https://github.com/Intel-Media-SDK/MediaSDK/commit/c7d40371eb0c2042261fe1f91a364f69a1457235
which should be available in this releases:
git tag --contains c7d40371eb0c2042261fe1f91a364f69a1457235
intel-mediasdk-20.1.0
intel-mediasdk-20.1.1
intel-mediasdk-20.1.pre1
intel-mediasdk-20.1.pre2
intel-mediasdk-20.1.pre3
intel-mediasdk-20.2.0
intel-mediasdk-20.2.1
intel-mediasdk-20.2.pre1
intel-mediasdk-20.2.pre2
intel-mediasdk-20.2.pre3
intel-mediasdk-20.3.pre1
intel-mediasdk-20.3.pre2
intel-mediasdk-20.3.pre3
intel-mediasdk-20.3.pre4
intel-mediasdk-20.3.pre5
intel-mediasdk-20.3.pre6

@tjaalton : I believe that master branch and releases >=20.1.0 has this issue fixed. Can you, please, double check that you updated a code base and really build one of the later releases?

hum, ok.. yes, looks like my testing local testing was outdated, it does built with 20.2.0, but the tests segfault but that's something else then

but the tests segfault but that's something else then

You gave us heads up on that some time ago, but we failed to reproduce:(. If these failures will persist, please, open another issue and attach detailed logs. Rough logs and output from strace might be needed. gdb results appreciated.

so I did.. I'll test a CI build on salsa.debian.org first, to verify it's not something on the chroot/sbuild on my own system


Don't show synthetic spectra with mixed selections

A student was trying to plot a 13C spectrum from a magres file, and entered the reference for 13C in the panel, but didn't realise that they needed to select C in the selection panel to restrict the nucleus. [In MV1 it is clear that you need to select a specific element]
The synthetic spectrum plotted from 0 - 200 ppm contained the C resonances, but also some random O shifts which (referenced to 0) happened to fall in range. This is very confusing for the user.
Meaningful behaviour would be to first check that a single atom type has been selected and refuse to draw a spectrum otherwise. I also feel there should be a concept of "unreferenced", so you can't plot a chemical shift if no reference has been defined.

Thanks for raising this issue. I think I've mostly addressed them in the development version - could you take a look and suggest further changes?
https://jkshenton.github.io/magresview-2/
On 5 Nov 2024 16:49, dch0ph @.***> wrote:
A student was trying to plot a 13C spectrum from a magres file, and entered the reference for 13C in the panel, but didn't realise that they needed to select C in the selection panel to restrict the nucleus. [In MV1 it is clear that you need to select a specific element]
The synthetic spectrum plotted from 0 - 200 ppm contained the C resonances, but also some random O shifts which (referenced to 0) happened to fall in range. This is very confusing for the user.
Meaningful behaviour would be to first check that a single atom type has been selected and refuse to draw a spectrum otherwise. I also feel there should be a concept of "unreferenced", so you can't plot a chemical shift if no reference has been defined.
—
Reply to this email directly, view it on GitHubhttps://github.com/CCP-NC/magresview-2/issues/25, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACS5XH322ZXWEZASPYNJZILZ7C5HHAVCNFSM6AAAAABRGPEMO6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGYZTKMZWGU3DGMA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Add Warp Reduce based on RegTile.

I would like to discuss how to add a reduce operation for RegTile. A simple reduce implementation is as follows:
template <typename Reduce>
DEVICE DType warp_reduce(DType data, unsigned mask, Reduce reduce) {
#pragma unroll
    for (int offset = 16; offset >= 1; offset /= 2) {
        data = reduce(data, __shfl_down_sync(mask, data, offset, 32));
    }

    return data;
}

This requires each thread to provide the corresponding value, and after a single warp reduce, the final result can be obtained.
However, this requires that each thread can provide the corresponding value. After a GEMM operation, the computation results are stored through RegTile, and at this time the reduction needs to be performed along the rows.
However, the data is not stored by rows in the thread-private registers, and a single warp reduce needs to process the information of one row. I would like to discuss how the threads should specify the data dispatching?

Here is the implementation of a row-wise reduce operation in TK(https://github.com/HazyResearch/ThunderKittens/blob/main/src/ops/warp/register/tile/reductions.cuh#L27
):
/**
 * @brief Perform a row-wise reduction on a matrix in row-major layout.
 *
 * This function template performs a parallel reduction across the rows of a matrix using a specified operation.
 * It leverages warp shuffle functions for efficient intra-warp communication.
 *
 * @tparam op The operation to be applied for reduction.
 * @tparam V The vector type for the row accumulator.
 * @tparam T The matrix type with row layout.
 * @tparam reset A boolean flag indicating whether to reset the accumulator (ignore src_accum) or not.
 * @param[out] row_accum The accumulator where the result of the reduction is stored.
 * @param[in] src The source matrix on which to perform the reduction.
 * @param[in] src_accum The initial value of the accumulator, used when reset is false.
 */
template<typename op, ducks::rv::all V, ducks::rt::row_layout T, bool reset>
__device__ static inline void row_reduce(V &row_accum, const T &src, const V &src_accum) {
    // I actually like these static asserts because they give more verbose errors when things go wrong.
    static_assert(std::is_same_v<typename V::dtype, typename T::dtype>); // compatible type
    static_assert(V::inner_dim == rt_base<typename T::dtype, typename T::layout>::col_vec_pack); // compatible layout
    static_assert(V::outer_dim == T::height); // compatible size

    using dtype = V::dtype;

    const int leader = threadIdx.x & 0x1C; // 11100 in binary
    #pragma unroll
    for(int i = 0; i < src.height; i++) {
        dtype accum_top_row    = op::template op<dtype>(src.tiles[i][0].data[0], src.tiles[i][0].data[2]);
        dtype accum_bottom_row = op::template op<dtype>(src.tiles[i][0].data[1], src.tiles[i][0].data[3]);
        #pragma unroll
        for(int j = 1; j < src.width; j++) {
            #pragma unroll
            for(int k = 0; k < src.packed_per_tile; k+=2) {
                accum_top_row    = op::template op<dtype>(accum_top_row,    src.tiles[i][j].data[k+0]);
                accum_bottom_row = op::template op<dtype>(accum_bottom_row, src.tiles[i][j].data[k+1]);
            }
        }
        dtype accum_packed;
        accum_packed.x = op::template op<base_types::packing<dtype>::unpacked_type>(accum_top_row.x,    accum_top_row.y);
        accum_packed.y = op::template op<base_types::packing<dtype>::unpacked_type>(accum_bottom_row.x, accum_bottom_row.y);

        // Now we need to do a lil shuffle to make everyone happy.

        accum_packed = op::template op<dtype>(accum_packed, packed_shfl_down_sync(MASK_ALL, accum_packed, 2));
        accum_packed = op::template op<dtype>(accum_packed, packed_shfl_down_sync(MASK_ALL, accum_packed, 1));

        accum_packed = packed_shfl_sync(MASK_ALL, accum_packed, leader);

        if(reset) {
            row_accum[i][0] = accum_packed;
        }
        else {
            row_accum[i][0] = op::template op<dtype>(src_accum[i][0], accum_packed);
        }
    }
}

First, we iterate through the tiles according to their row height and column width. Within each subtile, each thread stores partial data of two rows in its private registers. Initially, we perform a partial reduction operation along the rows.
After performing the reduction within each thread, each row's threads engage in a warp shuffle with the other threads belonging to the same row. Finally, the result is computed and stored in the row_accum array.


CoreData support?

Hi,
Is CoreData support on your roadmap?
Thanks.

+1

Same here! +1

Already at it

Great, thanks.

@technotrance could you clarify? Are you working on implementing support for CoreData in the bridge?

Yes

And repair encryption

@technotrance would be great to discuss your implementation/scope/timeline – would you mind shooting me an email at nicholas dot gerard at microsoft dot com?

Closing as a dup of #57


YLDA_HOME environment variable

Hey shravanmn,
I love the YLDA code! I've been using it for a project and I have been impressed by how much better it is than the Mahout LDA implementation both in terms of speed and setup time. Thanks for making this public! I just pushed a couple of minor changes that I needed to do to get things working for my purposes and I thought I would let you know in case you want to pull them into the master branch:

I added a YLDA_HOME environment variable to the runLDA.sh script make it possible to run YLDA from outside of the source root (something that I need to do).
I was having wierd syntax problems on my system with the LDA.sh and runLDA.sh scripts, so I changed these to being /bin/bash based rather than /bin/sh based.

Cheers.
Dean

Hi Shravan,
Sorry for the belated reply. I had a crunch-time deadline the past few
weeks and I did not have a chance to adequately review the agreement
before today. Attached is the signed contribution license agreement,
giving myself and Mike Stringer the authority to contribute to the YLDA
source on behalf of Datascope Analytics.
If there is anything else you need from us, please let me know.
Cheers.
Dean
On 2011/09/13 03:56, shravanmn wrote:

Thanks Dean. This will be useful. Before I can pull this, I need a contribution license agreement signed. You can find the agreement here https://github.com/shravanmn/Yahoo_LDA/raw/master/Contribution_License_Agreement_Yahoo.pdf
If you have trouble signing this document in pdf let me know we can figure out alternate ways to that.

--
dean malmgren
+1.312.884.9214


Settings not Changing Properly

JSON file data not changing when function runs.

Run setup program
Click both buttons sequentially
Look at JSON file data
No changes made

The JSON file data should change when one of the buttons are clicked.
Windows 10 VS Code

Fixed with re program, new file may be posted on 1.2 release day


add new constraints: distributon and sort key

Is your feature request related to a problem? Please describe.
Unable to add DISTKEY and SORKEY as table constraints.
Describe the solution you'd like
Add DISTKEY and SORKEY as table constraints.
https://github.com/open-metadata/OpenMetadata/blob/9a3fa2e532ecbdf0c83d0ebce30788ce511fe965/openmetadata-core/src/main/resources/json/schema/entity/data/table.json#L103

@trillhaa these are specific to Redshift, right?

Was this released with 0.11.1?

@harshach - do you think you could support this in the next releases, is it a bigger lift? Some users in our org have requested for it.


Fixes invalid JSON in crictl info

containerd on Windows may not escape the return message for Status request
lastCNILoadStatus: "cni config load failed: no network config found in C:\Program Files\containerd\cni\conf: cni plugin not initialized: failed to load cni config"
This may result in invalid JSON in crictl info
getting status of runtime: invalid character 'P' in string escape code
What type of PR is this?
/kind bug

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes: #1426
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE

Thanks for the fix, could you fix the lint errors?

This seems to break usage with CRI-O:
FATA[0000] getting status of runtime: json: cannot unmarshal array into Go value of type map[string]interface {}

Coming from: https://github.com/kubernetes-sigs/cri-tools/pull/1429/files#diff-10fd578be2b3eb945db0ff6ff5fa5433d9f0de3ad7b773b9a45460a99f0c3910R250-R255
I'm going to revert for now to unblock our CI.

Sure. I will double check the case with CRI-O.

@laozc do you mind reopening this?


ci: update repo url in release action

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


Vs1.1 mac百度ai无法执行下去

Traceback (most recent call last):
File "main.py", line 23, in
OPTIONS_MANAGE.Init_Options()
File "/Users/**/Desktop/learning-power-master/inside/Options/Options_Manage.py", line 97, in Init_Options
cls.__Baidu_AI()
File "/Users/zrz/Desktop/learning-power-master/inside/Options/Options_Manage.py", line 77, in __Baidu_AI
with open(PATH().Baidu_AI_On, 'w', encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory: '~/Desktop/learning-power-master/inside/Task/Mitmdump/Intercept/on'

Traceback (most recent call last):
File "main.py", line 23, in
OPTIONS_MANAGE.Init_Options()
File "/Users/**/Desktop/learning-power-master/inside/Options/Options_Manage.py", line 97, in Init_Options
cls.__Baidu_AI()
File "/Users/zrz/Desktop/learning-power-master/inside/Options/Options_Manage.py", line 77, in __Baidu_AI
with open(PATH().Baidu_AI_On, 'w', encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory: '~/Desktop/learning-power-master/inside/Task/Mitmdump/Intercept/on'

文件路径问题，现在已更新为绝对路径模式，我现在搞不清mac的文件路径了。


Update use-your-data.md

Replaced text listing of regions and models with an up-to-date table

@stefanisaacs please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree
@microsoft-github-policy-service agree company="Microsoft"

@aahill
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

merging internally
#please-close


when the panel is a table,the resulting image is not complete in width and height.

Describe the issue
when the panel is a table,the resulting image is not complete in width and height.  I set the width value in the template and it doesn't seem to work.
I want to report a table to pdf ,Is there any good solution？
Template file (if applicable)
grafana_panel_image:11[dashboard="wVCbu81nz",width="1200",height="500",var-DS_PROMETHEUS="xxxxxx]

Environment (please complete the following information):

OS [e.g. Windows 10]: Windows
Environment [e.g. source, gem, docker or windows-exe]: Windows-exe
ruby Version, if source or gem environment [e.g. 2.3.7]:
reporter Version [e.g. 0.3.0]:0.5.1

Thanks for using the reporter.
You are trying to add a table as image. Please note, that you can also add it as a "real" table by using the other grafana_panel function calls.
To fix your issue, try using the render-width and render-height options.

Thanks for using the reporter.
You are trying to add a table as image. Please note, that you can also add it as a "real" table by using the other grafana_panel function calls.
To fix your issue, try using the render-width and render-height options.

can not find function grafana_panel, can you show me how to use ,thank you .

Looks like there is an internal error, i.e. An issue in the reporter.
currently I have no chance to check it. Maybe go ahead with the image processor, as specified at first.

Maybe a few more things to check in the meantime:

Could you provide a screenshot of the panel in the dashboard, where the query succeeds?
What happens if you try using grafana_panel_query_value with the same panel request?
Try to call the last http request from your debug log in the browser? Can you share the results (x-out for potentially private information)?
If you still want to render it as a image, try using render-width and render-height.

render-width and render-height work fine
screenshot of the panel in the dashboard： https://img.400511.net/2022/02/21/s6moLtLk.png
=== 1:

include::grafana_panel_query_value:11[query="A",dashboard="wVCbu81nz",job="consul-node-exporter",idc="tencent-cloud",system="westmoney",environment="pro"]

=== 2:

include::grafana_panel_query_table:11[query="A",dashboard="wVCbu81nz",job="consul-node-exporter",idc="tencent-cloud",system="westmoney",environment="pro"]

=== 3:

grafana_panel_image:11[dashboard="wVCbu81nz",from="now-30d",to="now",render-width="1200",render-height="500",var-DS_PROMETHEUS="Prometheus-<IP_ADDRESS>",var-job="consul-node-exporter",var-idc="tencent-cloud",var-system="quote",var-environment="pro"]

I, [2022-02-21T09:36:27.757273 #2516]  INFO -- : Report started at 2022-02-21 09:36:27 +0800
I, [2022-02-21T09:36:27.757459 #2516]  INFO -- : You are running ruby-grafana-reporter version 0.5.1.
D, [2022-02-21T09:36:27.757573 #2516] DEBUG -- : Document attributes: {"convert-backend"=>"pdf", "imagesdir"=>"./images", "var-template"=>"b"}
D, [2022-02-21T09:36:27.757783 #2516] DEBUG -- : Template ./templates/b.adoc contains 3 calls of grafana reporter functions.
D, [2022-02-21T09:36:27.758832 #2516] DEBUG -- : Processing PanelQueryTableIncludeProcessor (instance: default, dashboard: wVCbu81nz, panel: 11, query: A)
D, [2022-02-21T09:36:27.759037 #2516] DEBUG -- : Requesting https://monitor.sxftwork.com/api/frontend/settings with '' and timeout '60'
D, [2022-02-21T09:36:29.589283 #2516] DEBUG -- : Received response #<Net::HTTPOK:0x00000000083d9db8>
D, [2022-02-21T09:36:29.592692 #2516] DEBUG -- : Requesting https://monitor.sxftwork.com/api/dashboards/uid/wVCbu81nz with '' and timeout '60'
D, [2022-02-21T09:36:29.870558 #2516] DEBUG -- : Received response #<Net::HTTPOK:0x00000000082b06d0>
D, [2022-02-21T09:36:29.874595 #2516] DEBUG -- : Requesting https://monitor.sxftwork.com/api/datasources/proxy/1/api/v1/query?time=1645407386000&query=100-+100%2A+min_over_time%28node_memory_MemAvailable_bytes%7Bidc%3D%22tencent-cloud%22%2Csystem%3D%22devops%22%7D+%5B30d%3A5m%5D%29+%2Fnode_memory_MemTotal_bytes%7Bidc%3D%22tencent-cloud%22%2Csystem%3D%22devops%22%7D with '' and timeout '60'
D, [2022-02-21T09:36:30.089998 #2516] DEBUG -- : Received response #<Net::HTTPOK:0x000000000821d600>
E, [2022-02-21T09:36:30.092252 #2516] ERROR -- : GrafanaReporterError: The datasource request to 'Prometheus-<IP_ADDRESS>' (Grafana::PrometheusDatasource) failed with an internal error: undefined method `[]' for nil:NilClass
D, [2022-02-21T09:36:30.144786 #2516] DEBUG -- : Processing PanelQueryValueInlineMacro (instance: default, dashboard: , panel: 11, query: )
D, [2022-02-21T09:36:30.145665 #2516] DEBUG -- : Requesting https://monitor.sxftwork.com/api/dashboards/uid/ with '' and timeout '60'
D, [2022-02-21T09:36:30.402191 #2516] DEBUG -- : Received response #<Net::HTTPNotFound:0x0000000008d57480>
D, [2022-02-21T09:36:30.402919 #2516] DEBUG -- : HTTP response body: {
  "message": "Not found"
}

E, [2022-02-21T09:36:30.403345 #2516] ERROR -- : GrafanaError: The specified dashboard '' does not exist. (Grafana::DashboardDoesNotExistError)
D, [2022-02-21T09:36:30.409063 #2516] DEBUG -- : Processing PanelImageInlineMacro (instance: default, dashboard: wVCbu81nz, panel: 11)
D, [2022-02-21T09:36:30.410224 #2516] DEBUG -- : Requesting https://monitor.sxftwork.com/render/d-solo/wVCbu81nz?panelId=11&fullscreen=true&theme=light&timeout=60&var-DS_PROMETHEUS=Prometheus-<IP_ADDRESS>&var-job=consul-node-exporter&var-idc=tencent-cloud&var-environment=pro&var-system=quote&var-node=<IP_ADDRESS>%3A9100&var-template=b&width=1200&height=500&from=1642815387000&to=1645407386000 with '' and timeout '60'
D, [2022-02-21T09:36:36.901169 #2516] DEBUG -- : Received response #<Net::HTTPOK:0x0000000008c90088>
I, [2022-02-21T09:36:37.077916 #2516]  INFO -- : Report creation ended after 10 seconds with status 'finished'

http request result：
{"status":"success","data":{"resultType":"vector","result":[]}}

Thanks for your detailed feedback. Let's go through it step by step:

render-width and render-height are working as expected, which solves your initial case, right?
The test case with grafana_panel_query_value is unsuccessfull, due to a malformed request. Try the following in your template file:
grafana_panel_query_value::11[query="A",dashboard="wVCbu81nz",job="consul-node-exporter",idc="tencent-cloud",system="westmoney",environment="pro"]

(no include and double colons)
3) The test case with grafana_panel_query_table is unsuccessfull, due to an internal error:
E, [2022-02-21T09:36:30.092252 #2516] ERROR -- : GrafanaReporterError: The datasource request to 'Prometheus-<IP_ADDRESS>' (Grafana::PrometheusDatasource) failed with an internal error: undefined method `[]' for nil:NilClass

Considering the response of the HTML request, it looks like, there is an issue in building the HTTP url in the reporter. That would have to be checked in detailed. If you see any chance to provide the URL that is generated and called by grafana, feel free to post it here.
If you are able to reproduce the issue e.g. on play.grafana.org, let me know how, and I can dig deeper.

Another thing you may try:
Toggle the Instant setting of your configuration and save the dashboard. Execute the report again and post the results.

Another thing you may try:
Toggle the Instant setting of your configuration and save the dashboard. Execute the report again and post the results.

grafana:  Format: table , Instant: true,  the same issue.
grafana_panel_query_value::11[query="A",dashboard="wVCbu81nz"]

 [2022-03-01T09:47:27.208015 #13808] DEBUG -- : Processing PanelQueryValueInlineMacro (instance: default, dashboard: wVCbu81nz, panel: :11, query: A)
E, [2022-03-01T09:47:27.208850 #13808] ERROR -- : GrafanaError: The specified panel id ':11' does not exist on the dashboard 'wVCbu81nz'. (Grafana::PanelDoesNotExistError)
D, [2022-03-01T09:47:27.214867 #13808] DEBUG -- : Processing PanelImageInlineMacro (instance: default, dashboard: wVCbu81nz, panel: 11)

https://monitor.sxftwork.com/api/datasources/proxy/1/api/v1/query?time=1646099241000&query=100-+100%2A+min_over_time%28node_memory_MemAvailable_bytes%7Bidc%3D%22tencent-cloud%22%2Csystem%3D%22devops%22%7D+%5B30d%3A5m%5D%29+%2Fnode_memory_MemTotal_bytes%7Bidc%3D%22tencent-cloud%22%2Csystem%3D%22devops%22%7D

http request result is null, so  there is an issue in building the HTTP url in the reporter.

Thanks for your patience. I currently try to hunt this one down, but I'm still having issues to reproduce it.
Could you maybe post the panel JSON from grafana? This should help me to understand your panel configuration in detail.

Thanks for your patience. I currently try to hunt this one down, but I'm still having issues to reproduce it.
Could you maybe post the panel JSON from grafana? This should help me to understand your panel configuration in detail.

{
"id": 11,
"gridPos": {
"h": 18,
"w": 24,
"x": 0,
"y": 0
},
"type": "table",
"title": "Host Reporter",
"transformations": [
{
"id": "seriesToColumns",
"options": {
"byField": "instance"
}
},
{
"id": "organize",
"options": {
"excludeByName": {
"InstanceId": true,
"InstanceId 2": true,
"InstanceName": true,
"InstanceName 2": true,
"OsType": true,
"OsType 2": true,
"Time": true,
"Time 2": true,
"Time 3": true,
"Time 4": true,
"alertsource": true,
"alertsource 2": true,
"environment": true,
"environment 2": true,
"environment 3": true,
"environment 4": true,
"idc 1": true,
"idc 2": true,
"idc 3": true,
"idc 4": true,
"important": true,
"important 2": true,
"instanceid": true,
"instanceid 2": true,
"instancename 2": true,
"instancename 3": true,
"instancename 4": true,
"job": true,
"job 2": true,
"monitor_group": true,
"monitor_group 2": true,
"no_mem_warn 1": true,
"no_mem_warn 2": true,
"ostype": true,
"ostype 2": true,
"system 2": true,
"system 3": true,
"system 4": true
},
"indexByName": {
"InstanceId": 1,
"InstanceName": 2,
"OsType": 3,
"Time": 0,
"Value": 13,
"alertsource": 4,
"environment": 6,
"idc": 7,
"instance": 5,
"instanceid": 8,
"instancename": 9,
"job": 10,
"ostype": 11,
"system": 12
},
"renameByName": {
"Value": "mem_max",
"Value #A": "mem_max(%)",
"Value #B": "mem_avg(%)",
"Value #C": "cpu_max(%)",
"Value #D": "cpu_avg(%)",
"instance": "IP"
}
}
}
],
"pluginVersion": "8.3.5",
"fieldConfig": {
"defaults": {
"custom": {
"align": "center",
"displayMode": "auto"
},
"thresholds": {
"mode": "absolute",
"steps": [
{
"color": "green",
"value": null
}
]
},
"mappings": [],
"color": {
"mode": "thresholds"
},
"max": 100,
"min": 0
},
"overrides": [
{
"matcher": {
"id": "byName",
"options": "mem_avg(%)"
},
"properties": [
{
"id": "thresholds",
"value": {
"mode": "percentage",
"steps": [
{
"color": "green",
"value": null
},
{
"color": "yellow",
"value": 80
}
]
}
},
{
"id": "custom.displayMode",
"value": "color-background"
}
]
},
{
"matcher": {
"id": "byName",
"options": "cpu_avg(%)"
},
"properties": [
{
"id": "thresholds",
"value": {
"mode": "percentage",
"steps": [
{
"color": "green",
"value": null
},
{
"color": "red",
"value": 80
}
]
}
},
{
"id": "custom.displayMode",
"value": "color-background"
}
]
}
]
},
"options": {
"showHeader": true,
"footer": {
"show": false,
"reducer": [
"sum"
],
"fields": ""
}
},
"targets": [
{
"datasource": {
"type": "prometheus",
"uid": "k3SQ5N_Gk"
},
"exemplar": false,
"expr": "100- 100* min_over_time(node_memory_MemAvailable_bytes{idc="$idc",system="$system"} [30d:5m]) /node_memory_MemTotal_bytes{idc="$idc",system="$system"}",
"format": "table",
"instant": true,
"interval": "",
"legendFormat": "",
"refId": "A"
},
{
"datasource": {
"type": "prometheus",
"uid": "k3SQ5N_Gk"
},
"exemplar": false,
"expr": "100- 100* avg_over_time(node_memory_MemAvailable_bytes{idc="$idc",system="$system"} [30d:10m]) /node_memory_MemTotal_bytes{idc="$idc",system="$system"}",
"format": "table",
"hide": false,
"instant": true,
"interval": "",
"legendFormat": "",
"refId": "B"
},
{
"datasource": {
"type": "prometheus",
"uid": "k3SQ5N_Gk"
},
"exemplar": false,
"expr": "100 - min_over_time(avg by(instance,system,idc,environment,instancename) (rate(node_cpu_seconds_total{mode="idle",idc="$idc",system="$system"}[2m]))[30d:5m]) * 100",
"format": "table",
"hide": false,
"instant": true,
"interval": "",
"legendFormat": "",
"refId": "C"
},
{
"datasource": {
"type": "prometheus",
"uid": "k3SQ5N_Gk"
},
"exemplar": false,
"expr": "100 - avg_over_time(avg by(instance,system,idc,environment,instancename) (rate(node_cpu_seconds_total{mode="idle",idc="$idc",system="$system"}[2m]))[30d:5m]) * 100",
"format": "table",
"hide": false,
"instant": true,
"interval": "",
"legendFormat": "",
"refId": "D"
}
],
"datasource": null
}

I just recognized, that Grafana changed the way of storing the JSON format and also of returning values (at least for some datasources).
I tried to fix these issues in release 0.5.2. Please checkout if your issue persists with that version.
If not, please feel free to reopen a new issue (we already mixed 2 issues in this report).
Thanks for your continuing support in finding the issues - your JSON helped a lot there.


How to change the position of a floating leva panel

Hello,
I am trying to set a custom position (or at least some margins) to a leva panel. My application has a header of height 7vh and the leva panel is laying behind it even though the leva panel is being created in a component that already has a top margin of 7vh.
I've been trying including some styles to a div around Leva and LevaPanel (having the Leva instance inside and outside the div) but haven't achieved to move the panel so far.
Here is a basic code example:
const InputsPanel = () => {
  const myStore = useCreateStore();

  const controls = useControls({
    Name: "Name",
    Checked: true,
  }, { store: myStore });

  return (
    <>
        <div
          style={{
            position: 'absolute',
            top: '7vh',
            marginTop: '7vh'
          }}
        >

        <Leva />
        <LevaPanel
          store={myStore}
          titleBar={{ title: "Settings", drag: true, filter: false }}
        />
      </div>
    </>

  );
};

Is there a way to include such re-positioning of the Leva panels or some margin to them? (maybe using themes?)
Thanks in advance.

You can wrap the panel inside your node (like a div) and use the fill prop.
<div> <!-- you control the position of that div>
  <Leva fill />
</div>


fliplr_params to flip the parameters of the left hand is not giving me the right results

I used HaMeR to estimate the hand pose, and it worked well, as shown in the figure on the left. I then combined the results from HaMeR and 4D-Humans into the SMPLH model, but I was unable to get the correct reconstruction for the left hand, as you can see in the figure on the right.

I followed your advice from these two threads https://github.com/geopavlakos/hamer/issues/26 https://github.com/geopavlakos/hamer/issues/61 to convert the left hand pose from a rotation matrix to axis-angle, used the fliplr_params function, and then converted it back to a rotation matrix. However, the results are still incorrect, as shown in the figure. I have tried flipping and no flipping but to no avail.
Do you any idea why? Would greatly appreciate your help.

Thank you for responding! Here are the relevant functions in use: rotmat_to_aa, aa_to_rotmat, and fliplr_params.
from scipy.spatial.transform import Rotation as R
def rotmat_to_aa(rot_matrices):
    """
    Convert a batch of rotation matrices to axis-angle format using scipy.

    Parameters:
    rot_matrices: numpy array of shape (batch_size, 3, 3)
                  Batch of rotation matrices

    Returns:
    axis_angles: numpy array of shape (batch_size, 3)
                 Batch of axis-angle vectors
    """
    # Create a Rotation object from the rotation matrices
    rotation_obj = R.from_matrix(rot_matrices)

    # Convert to axis-angle (rotation vector) representation
    axis_angles = rotation_obj.as_rotvec()  # This gives the axis-angle representation

    return axis_angles

def aa_to_rotmat(axis_angles):
    """
    Convert a batch of axis-angle vectors to rotation matrices using scipy.

    Parameters:
    axis_angles: numpy array of shape (batch_size, 3)
                 Batch of axis-angle vectors (rotation vector format)

    Returns:
    rot_matrices: numpy array of shape (batch_size, 3, 3)
                  Batch of rotation matrices
    """
    # Create a Rotation object from the axis-angle vectors
    rotation_obj = R.from_rotvec(axis_angles)

    # Convert to rotation matrices
    rot_matrices = rotation_obj.as_matrix()  # This gives the rotation matrices

    return rot_matrices

# to flip the lr params
from typing import Dict, Tuple
def fliplr_params(mano_params: Dict, has_mano_params: Dict) -> Tuple[Dict, Dict]:
    """
    Flip MANO parameters when flipping the image.
    Args:
        mano_params (Dict): MANO parameter annotations.
        has_mano_params (Dict): Whether MANO annotations are valid.
    Returns:
        Dict, Dict: Flipped MANO parameters and valid flags.
    """
    global_orient = mano_params['global_orient'].copy()
    hand_pose = mano_params['hand_pose'].copy()
    betas = mano_params['betas'].copy()
    has_global_orient = has_mano_params['global_orient'].copy()
    has_hand_pose = has_mano_params['hand_pose'].copy()
    has_betas = has_mano_params['betas'].copy()

    global_orient[1::3] *= -1
    global_orient[2::3] *= -1
    hand_pose[1::3] *= -1
    hand_pose[2::3] *= -1

    mano_params = {'global_orient': global_orient.astype(np.float32),
                   'hand_pose': hand_pose.astype(np.float32),
                   'betas': betas.astype(np.float32)
                  }

    has_mano_params = {'global_orient': has_global_orient,
                       'hand_pose': has_hand_pose,
                       'betas': has_betas
                      }

    return mano_params#, has_mano_params

Here's how I do the flipping:

I deepcopy the output of mano mano_data whose entries have all been converted from tensors to numpy arrays.
Convert from rotation matrix to axis angle
Perform the flip for only the left hand using the function you provided
Convert it back to rotation matrix.
Copy the data back into mano_data

temp_mano_data  = copy.deepcopy(mano_data)
lhand_mano_data = {}
lhand_mano_data["betas"]            = temp_mano_data["pred_mano_params"]["betas"][0]            # [2,  10]
lhand_mano_data["global_orient"]    = temp_mano_data["pred_mano_params"]["global_orient"][0]    # [1,  3, 3]
lhand_mano_data["hand_pose"]        = temp_mano_data["pred_mano_params"]["hand_pose"][0]        # [15, 3, 3]
lhand_mano_data["hand_pose"]        = rotmat_to_aa(lhand_mano_data["hand_pose"])                # [15, 3]
lhand_mano_data                     = fliplr_params(lhand_mano_data, lhand_mano_data)
lhand_mano_data["hand_pose"]        = aa_to_rotmat(lhand_mano_data["hand_pose"])                # [15, 3, 3]
mano_data["pred_mano_params"]["hand_pose"][0] = lhand_mano_data["hand_pose"]

And then I combine the updated mano params with the output of 4D-Humans to form the smplh parameters for visualization.

I grab the output of 4D-Humans (also numpy array)
Keep its global body orient but remove the last 2 elements of ["pred_smpl_params"]["body_pose"]

# from 4D-Humans
global_body_orient  = torch.tensor(smpl_data['pred_smpl_params']['global_orient'], dtype=torch.float32)   # [1, 1,  3, 3]
body_pose           = torch.tensor(smpl_data["pred_smpl_params"]["body_pose"], dtype=torch.float32)       # [1, 23, 3, 3]
body_pose           = body_pose[:,:21]                                                                              # [1, 21, 3, 3]
betas               = torch.tensor(smpl_data['pred_smpl_params']['betas'], dtype=torch.float32)           # [1, 10]

# from HaMeR
hand_pose           = torch.tensor(mano_data['pred_mano_params']['hand_pose'], dtype=torch.float32)       # [2, 15, 3, 3]

# smplh params
pred_smplh_params = {}
pred_smplh_params['betas']           = betas                # [1, 10]
pred_smplh_params['global_orient']   = global_body_orient   # [1, 1,  3, 3]
pred_smplh_params['body_pose']       = body_pose            # [1, 21, 3, 3]
pred_smplh_params['left_hand_pose']  = hand_pose[0:1]       # [1, 15, 3, 3]
pred_smplh_params['right_hand_pose'] = hand_pose[1:2]       # [1, 15, 3, 3]

Thank you, and I hope to seek your advice.

fliplr_params() assumes that the inputs are in the form of vectors not 2D matrices (e.g., 45 dims for hand_pose instead of 15x3)

Damn that was silly of me to not notice... Thank you so much !


Move lib into a separate repository

This PR moves lib out of this repository, and into a separate one here. This is meant to make maintenance easier by allowing us to develop the two separately.
It also removes the dependency on nixpkgs, and some usages of maintainers/teams that were stopping evaluation. Probably these should come from the community repo instead.

I noticed that now https://github.com/auxolotl/lib has nixpkgs as an input, and as such nixpkgs is present within core's flake.lock file. Once we switch over to using core as the source for nix, this would create a circular dependency. Would it be possible to have a separate flake for tests? Or perhaps resolve the dependence via this: flake.md.

I think we could also have the lib flake export a function that takes a *pkgs instance and returns a derivation (but this makes running the tests a little weirder). Not sure which is best.

and some usages of maintainers/teams that were stopping evaluation. Probably these should come from the community repo instead.

As I mentioned here https://github.com/auxolotl/core/pull/2#discussion_r1598736880, that is the plan. But lets save that for a later PR.

Hopefully you can remove the upstream decency when https://github.com/auxolotl/core/pull/8 is merged.

putting it in another repo means it's one more place we have to manage issues and PRs

I generally find the same amount of issues across multiple repos easier to handle than all in one repo. Synchronising changes is obviously harder, but this would be an issue even if lib was here, so long as lib is consumed by sig repos.

especially if lib is going to do anything relating to stringing together derivations a la callPackage

The set of functions in there right now is currently just the same as nixpkgs - there might be things we don't want to provide or need to rethink. If there are library functions that are actually dependent on the package set (ie trivial builders) then I agree they probably should be in here.
My understanding is that callPackage deals with dependency injection and overrides, which we probably need to rethink for a multi-repo structure regardless. However we deal with it, this is a slightly different concern than packaging imo so it makes sense for it to not be here.

One might argue that it allows lib to be consumed independently of everything else, but if it's going to depend on Core anyway, that's kind of a moot point.

Right now this is basically a limitation of flakes, since core is only really a dev dependency. Having thought about it more, I think lib should probably have a different flake inside it for docs and tests, unless there's some better way to handle this I'm not aware of (possibly just doing tests outside of flakes?).

Right now this is basically a limitation of flakes, since core is only really a dev dependency. Having thought about it more, I think lib should probably have a different flake inside it for docs and tests, unless there's some better way to handle this I'm not aware of (possibly just doing tests outside of flakes?)

What about storing the tests in a separate branch with its own flake that depends on lib and core?

Sure, or tests and docs` could just be in a subdirectory. Probably best to open an issue in auxolotl/lib

I generally find the same amount of issues across multiple repos easier to handle than all in one repo.

Keeping repo count down isn't just for maintainers - having an additional repo to track issues in adds additional confusion to users when they go to eg. report an issue ("is this a bug in Core or lib?"). There's also the extra overhead of being another repo to checkout, with the possibility of grabbing multiple different copies of it depending on the state of lockfiles. I'm not sure I'm seeing much benefit to outweigh the downsides here.

What about storing the tests in a separate branch with its own flake that depends on lib and core?

I'm weary of doing this - I'm not a fan of branches in one repo having completely divergent histories, it doesn't lend well to code discovery (since users have to be aware the branch exists to know that code is even there). It's also an issue that just wouldn't exist if lib was a part of the Core repo, which IMO furthers the case for not splitting.

having an additional repo to track issues in adds additional confusion to users when they go to eg. report an issue ("is this a bug in Core or lib?")

To me they seem pretty easily separated, but I guess I would think that lol.

I'm weary of doing this - I'm not a fan of branches in one repo having completely divergent histories, it doesn't lend well to code discovery

Agreed.
I think right now we don't have consensus on what exactly core is meant to be, so I think we should come back to this during/after the upcoming meeting.

I'm not entirely convinced this is a good idea. What's the use case for taking lib out of core?

Well a few things.

core is almost certainly going to be complicated, and I think we should keep it as small and focused on bootstrapping as possible. Lib is the standard lib, so its going to contain helpers that core doesn't even use for bootstrapping. Lib being external is one way to minimize the complexity inside of core.
More importantly though, I think lib should be pure, no system no derivations. For example, in JS I have a repo that is exclusively Javascript code that runs everywhere (browser, node, deno, bun) and then I have another library of standard tools that only run on deno. It has been great in terms of a mental model. Nix lib could be the same way.
For minimal applications and bundling I think the should be able to import a pinned version of lib without importing core.  I think one day we might see nix bundling (like js bundling) as well, and it will be a lot easier to tree-shake lib than it will be to tree shake a bootstrapping core codebase.
I think it will be easier to combine them later than it will be to separate them later. So if we change our mind its no big deal.

But most of all, I think it will be helpful on the maintaince side. Some people who contribute to lib might never touch core. Tests for lib will be trivial to run because they're system independent, people can contribute/iterate faster when code isnt system dependent. Lib should also have different PR standards, like documentation for each helper with examples, while helpers inside of core dont need the same level or format of documentation. Even just being able to look at the git history of lib independent of core would likely be helpful.

I'm not a fan of branches in one repo having completely divergent histories

I have tried this a number of times for myself thinking it was a good idea. I've had a pretty bad time every time.
The only time it was a mediocre experience was when it was an "inherited" model, with one base branch and the others just always auto-merging that base branch into themselves. But even then it was a difficult mental model needing to not make a change on a branch, go to base, make the change, then back to the feature branch, and merge base. I very frequently forgot and had to redo commits on base.
Very much not an experience I would want to try with a team of people.

one more place we have to manage issues and PRs

I think having it as an additional place for PR's is very very much a good thing. A core PR and a lib PR should have different standards.
As for issues, I agree @Sorixelle one place is nice. I had problems reporting "nix" issues and them telling me "no that's a nixpkgs issue" and I didnt understand the difference. I think we should consider disabling issues on both lib and core, or locking them to contributors only and have all issues be reported through either the aux/auxpkgs repo.


extra_javascript in mkdocs 1.5.0 is list of objects and no longer string

According to the changelog, there is a set of changes to apply in order to be compatible with mkdocs 1.5.0 released on 26/27 July 2013.
See documentation here: https://www.mkdocs.org/about/release-notes/#upgrades-for-plugin-developers
I opened PR #79 to fix one of these issues, but I do not know if there is any other things to do.

Thanks for the fix! Is there an expectation for a release?

This issue becomes redundant, since a patch was issued in mkdocs 1.5.1 (see mkdocs/mkdocs/#3310).

The forcing to str will stay, even though it would still work with mkdocs 1.5.1. The use of fspath in path objects is not super obvious in its consequences; so for tranquillity of mind, forcing to str seems a good idea.


add workflow to build chart tag and image

What type of PR is this?
/kind feature

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

build hami mutil arch image when create a tag.
release chart tag in branch gh-page when change the chart version
add ci to verify wherher appVersion and version are the same

Does this PR introduce a user-facing change?:

/lgtm


Unable to load private remotes with ssh

Extension version: v0.64.0
VSCode Version: 1.78.2
OS: OSX 13.2.1

Steps to Reproduce:

git remote -v

origin	git@github.com:Example-Org/example-repo.git (fetch)
origin	git@github.com:Example-Org/example-repo.git (push)

gitcredentials setup

[user]
    name = foo
    email =<EMAIL_ADDRESS>[commit]
    gpgsign = false
[core]
    sshCommand = "ssh -i /Users/foo/.ssh/id_rsa"

Regular git commands work fine, both on commandline and via VSCode

This extension fails:

2023-06-05 12:34:03.310 [info] Looking for git repository
2023-06-05 12:34:03.310 [info] Found 0 repositories during activation
2023-06-05 12:34:03.310 [info] Git repository found, initializing review manager and pr tree view.
2023-06-05 12:34:03.310 [info] Registering git provider
2023-06-05 12:34:03.310 [info] Review> Validate state in progress
2023-06-05 12:34:03.310 [info] Review> Validating state...
2023-06-05 12:34:03.311 [info] Cannot updates repositories as git is uninitialized
2023-06-05 12:34:03.322 [info] Git initialization state changed: state=initialized
2023-06-05 12:34:03.322 [info] Review> Queuing additional validate state
2023-06-05 12:34:03.349 [info] Repo state for file:///Repos/example-repo/example-repo changed.
2023-06-05 12:34:03.349 [info] Repo file:///Repos/example-repo/example-repo has already been setup.
2023-06-05 12:34:03.349 [info] Review> no matching pull request metadata found for current branch develop
2023-06-05 12:34:03.349 [info] Review> No matching pull request metadata found on GitHub for current branch develop
2023-06-05 12:34:03.372 [info] Review> Validating state...
2023-06-05 12:34:03.372 [info] Found GitHub remote for folder /Repos/example-repo/example-repo
2023-06-05 12:34:03.714 [warning] Unable to resolve remote: HttpError: Not Found
2023-06-05 12:34:04.095 [info] Missing upstream check failed: HttpError: Not Found
2023-06-05 12:34:04.166 [info] Review> no matching pull request metadata found for current branch develop
2023-06-05 12:34:04.525 [error] GitHubRepository> Unable to fetch issues: Error: GraphQL error: Could not resolve to a Repository with the name 'Example-Org/example-repo'.
2023-06-05 12:34:04.525 [error] GitHubRepository> Unable to fetch issues: Error: GraphQL error: Could not resolve to a Repository with the name 'Example-Org/example-repo'.
2023-06-05 12:34:04.568 [error] GitHubRepository> Fetching pull requests for branch failed: Error: GraphQL error: Could not resolve to a Repository with the name 'Example-Org/example-repo'.
2023-06-05 12:34:04.872 [warning] GitHubRepository> Fetching default branch failed: HttpError: Not Found
2023-06-05 12:34:04.909 [warning] GitHubRepository> Fetching default branch failed: HttpError: Not Found
2023-06-05 12:34:04.951 [error] GitHubRepository> Unable to fetch issues without milestone: Error: GraphQL error: Could not resolve to a Repository with the name 'Example-Org/example-repo'.
2023-06-05 12:34:04.951 [error] GitHubRepository> Unable to fetch issues without milestone: Error: GraphQL error: Could not resolve to a Repository with the name 'Example-Org/example-repo'.
2023-06-05 12:34:05.228 [warning] GitHubRepository> Fetching default branch failed: HttpError: Not Found
2023-06-05 12:34:05.276 [error] GitHubRepository> Unable to fetch issues with query: Error: GraphQL error: Could not resolve to a Repository with the name 'Example-Org/example-repo'.
2023-06-05 12:34:05.276 [error] GitHubRepository> Unable to fetch issues with query: Error: GraphQL error: Could not resolve to a Repository with the name 'Example-Org/example-repo'.
2023-06-05 12:34:05.305 [warning] GitHubRepository> Fetching default branch failed: HttpError: Not Found```

I'm not sure what you mean by "example-org username and password".
I use the github username or email address, as prompted:

@alexr00 any updates on this? The extension just flat out doesn't work for me atm, I doubt I'm the only person using ssh hitting this bug

@dakom thanks for the screen shot, that does answer my question ✔.
I'm not sure how or if the credential setup you outline in step 2 will impact things, but I have tried just cloning a private repo in an organization with ssh and I'm not having any problems. Have you tried signing out of GitHub in VS Code and then signing in again? For where this is failing, it looks like something is up with your GitHub authentication, not with your git credentials.

Ahhhh.... interesting... yes that does explain it, thank you @alexr00 !
Hmm so now for a different can of worms. I totally lied about my setup above. My actual gitconfig is more like this:
[credential]
        # ... blah ...

[includeIf "gitdir:~/PROJECT1/"]
    path = ~/PROJECT1/gitconfig

and then that PROJECT1/gitconfig file contains other credentials
In other words, depending on the directory I'm working in, it uses different credentials.
Is there a way for the extension to use something derived from the gitconfig (such that it will stay in sync with git as I change directories)?

@alexr00 that's right, for Git I have separate credentials (e.g. separate ssh keys) and for Github I have separate accounts with separate emails/usernames - not aliases of any kind, truly separate accounts

Closing because this depends on the upstream issue https://github.com/microsoft/vscode/issues/127967 and I'll adopt here as soon as that's done. Thanks for providing all the details @dakom!


Nice tutorial!

Got everything up and runnig in ~1h - Good work!

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

ID: 965a7faf-6684-1b1e-3570-ea0b38ce02db
Version Independent ID: 2efd8393-0b5b-e827-8762-fa58d6758d93
Content: Quickstart - Azure Kubernetes cluster portal quickstart
Content Source: articles/aks/kubernetes-walkthrough-portal.md
Service: container-service
GitHub Login: @neilpeterson
Microsoft Alias: nepeters

@ascheman thanks for the feedback!
@neilpeterson nice work :)


Add react-scripts start --writeToDisk option

Emitting dev builds to disk would help in certain cases, but that's not
supported by default. You can either have dev builds served up from
memory or production minified builds emitted to disk.
There's a long-running discussion and an abandoned PR in the original
repo, and maybe this feature will make it into CRA 4.1 or so. In the
meantime, this branch applies the patch from the abandoned PR to our
copy of CRA.
I expect this to be useful for testing microfrontends served by nginx
in dev-eks as we move away from local development. We may be able to
deploy a temporary nginx container that contains locally-built files,
and it would help if those files were not prod-minified.

Sorry, this was a mistake; the github CLI submitted a PR to the upstream repo, when it should've submitted to my forked repo. Closing.


Please update aws sdk v2 version. schema-registry-serde:1.1.17 conflicts with latest aws-sdk libs.

Please update aws sdk v2 to a newer version.
When using schema-registry-serde:1.1.17 together with aws sdk v2 libraries, which versions are 2.21.7 and higher, got exceptions due to breaking changes introduced in latter aws sdk v2 versions.
Have to explicitly exclude transient dependencies from schema-registry-serde, e.g. sts library. Reason is the error below:
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apache.kafka.common.serialization.Deserializer]: Factory method 'glueDeserializer' threw exception with message: software/amazon/awssdk/protocols/query/interceptor/QueryParametersToBodyInterceptor
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:178)
at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:651)
Caused by: java.lang.NoClassDefFoundError: software/amazon/awssdk/protocols/query/interceptor/QueryParametersToBodyInterceptor
at software.amazon.awssdk.services.sts.DefaultStsBaseClientBuilder.finalizeServiceConfiguration(DefaultStsBaseClientBuilder.java:68)
at software.amazon.awssdk.awscore.client.builder.AwsDefaultClientBuilder.finalizeChildConfiguration(AwsDefaultClientBuilder.java:160)

We are working on releasing 1.1.18 right now, it should be done shortly and we will update aws sdk v2 version to latest in this release.

We have released v1.1.18 and the AWS SDK v2 version is updated! Thank you!


OperationMode correction?

The luxtronik controller returns under "0080 calculations.ID_WEB_WP_BZ_akt" the OperationMode=heating if the heatpump is effective heating.
But also if the heater of the compressor (0182 calculations.ID_WEB_LIN_VDH_out) is running. Not the compressor (0044 calculations.ID_WEB_VD1out) himself.
The heater of the compressor ensures a minimum temperature. In my case it runs about 2-3 times per hour.
I think the OperationMode heating should only report heating if the heatpump heats something productive in the building and not only himself. So I have a correction that overwrite the OperationMode in case of only running the heater of the compressor.
That do you think about this? Should we implement this in our core-module (python-luxtronik)?

In my opinion we should not manipulate the parameters / calculations itself. We could introduce a new category, maybe call it extended or something like that, where we have values that have certain constrains.
I know that AIT has several parameters / calculations that have different meanings dpendent on heatpump type and some other constrains.

Do you think we should add an optional param to the existing function or property or add another function?
At the moment I have 3 replacements:

C80 Status: Show "heating" if the compressor heater is on. Not the compressor himself. Replace with "no request".
C117 Line1: Show "heating" if the compressor heater is on. Not the compressor himself. Replace with "compressor_heater".
C117 Line1: Show "heatpump coming" on shutdown. Replace with "heatpump_shutdown".

From my point of view there should be multiple "layers" offered by python-luxtronik:

Obviously we need a low-level interface like we currently have (e.g. parameters, visibilities, calculations, etc.). The data can be represented by data types (like we currently do), but we should not introduce complexity on top of that by interpreting values differently than they are handled by the heat pump itself.
On top of that there could be another layer that deals with those kind of issues and is a more high-level representation of the heat pump. It could also offer services / functions (e.g. something like (enable_hup, or enable_heatpump, set_temperature, etc.).

Git itself also is doing something similar, it has a plumbing commands and uses those to implement high-level porcelain commands.

The idea by kbabioch sounds interesting. In a certain way, we already have to layers (namely the raw values and the converted values). It would also great, if we could have some high-level functions for setting the parameters. On the other hand, it should not be too easy to mess around with (critical settings of) your heat pump, otherwise people will start to blame the python module for killing their heat pump....
By the way: how do you enable_hup? Is there a specific parameter to trigger the pump? From my understanding, it only starts if the temperature (of hot water or heating water) is too low.

On the other hand, it should not be too easy to mess around with (critical settings of) your heat pump, otherwise people will start to blame the python module for killing their heat pump....

Yeah, there should be some consideration to not change critical values too easily. On the other hand you can always kill your heat pump, if you try hard enough ;-).

By the way: how do you enable_hup? Is there a specific parameter to trigger the pump? From my understanding, it only starts if the temperature (of hot water or heating water) is too low.

That was just an example, I have no idea if and how it could be enabled explicitly. But once we figure it out, it should be easy for consumers of this library ;-).

Yeah, there should be some consideration to not change critical values too easily. On the other hand you can always kill your heat pump, if you try hard enough ;-).

Of course, you can always take a sledge hammer -- and we can't hinder the users of this library from doing so...
Maybe a good rule of thumb is that we allow the change of all parameters which can be changed on the heat pump itself with standard user access. (And maybe also the hysteresis parameter. I do not understand why the regular user is not allowed to change these...)

I would, for instance, be interested in something like enable_zwe to enable my heating rod to use some excess PV energy to heat up the water (see BenPru/luxtronik#4).

Ok, but if you enable the heating rod, you need to either heat the warm water or the radiators since the heat pumps do not have a Pufferspeicher / storage tank for heat. (Maybe there are some models which have one??)

Ok, but if you enable the heating rod, you need to either heat the warm water or the radiators since the heat pumps do not have a Pufferspeicher / storage tank for heat. (Maybe there are some models which have one??)

You're right, in this case it should be more like make_hot_water(temperature) or something like this. In any case this was an example of why multiple layers might be needed.

Maybe a good rule of thumb is that we allow the change of all parameters which can be changed on the heat pump itself with standard user access. (And maybe also the hysteresis parameter. I do not understand why the regular user is not allowed to change these...)

That's probably a good approach.

The idea by kbabioch sounds interesting. In a certain way, we already have to layers (namely the raw values and the converted values).

I would argue that the raw values and the converted data types are a representation of the same layer. We could offer some control on whether values should be converted, but in the end they represent the same data. This is part of a the "low level" for me. On a high level I would like to offer functions that are based on low level parameters/calculations/visibilities, but are not necessarily linked to those values in a one to one relationship.


Incorrect type hint for value in Url.validate()

Currently the type hint for value in .validate() of the url classes is value: Union[T, np.ndarray, Any].
It should be value: Union[T, str, Any] though, since we actually expect a string here, not a numpy array.
This is the case for:

AudioUrl
AnyUrl
ImageUrl
VideoUrl
Url3D

Hi, I am riksucks#3292 from discord! Would love to take up this issue!

Is the issue still open @anna-charlotte ?

fixed in https://github.com/docarray/docarray/commit/1ac70ccbc4aef1cfb659d21704aa51d07a4f5838


method does not override or implement a method from a supertype

node_modules/react-native-barcodescanner/android/src/main/java/com/eguma/barcodescanner/BarcodeScannerPackage.java:20: error: method does not override or implement a method from a supertype
@Override

I am also having same issue

I am also having the same issue. Any help on this please !!


Implement overlay open file

[ ] in split ctrl+s
[ ] in vsplit ctrl+v
[ ] in tab ctrl+t

@gerardroche Would you mind adding Origami as a dependency for this feature? I'd implement this happily if that was an option (using Origami anyways).

I'm open to it if it can be implemented in a non intrusive way or as a temporary solution.
By non-intrusive I mean for example, polyfill should work without Origami installed and should only fail silently when Origami is not installed.
Ideally, I'd like see a window api plugin that provides just the window commands with no side effects e.g. doesn't override key bindings. This way both Origami aswell as other plugins like Vintageous Origami could use those commands without the side effects.
I've played around with this idea in a develop branch of Vintageous. See the SublimeWindowApi. I've implemented a few of a features of Origami, mostly because Vintageous Origami doesn't work with the newer versions of Vintageous.

It was a good idea. I don't know why I didn't do this in the first place. I remember looking at the Origami package and can't remember why I didn't use it.
Anyways, thanks for bringing this to my attention.
I wasn't able to get the open file in split, vsplit, and tab from the tree view #1. Not sure yet if it's possible.

good job :+1:


AtlassianJiraAudit-Python-3.11-version-update

Required items, please complete
Change(s):

Change in Python Version to 3.11
Repackaged the solution for Data Connector Instructions.

Reason for Change(s):

As per requirement (Deprecation of 3.8)

Version Updated:

Python version - 3.11
Solution version - 3.0.4

Testing Completed:

Yes

Raise PR with same changes -https://github.com/Azure/Azure-Sentinel/pull/11051


Refresh Parameter

Refresh parameter added to query

Badly need something like this.. Can you please do a step by step or atleast restore your branch please?


Added support to render controls above outputs

renderAboveOutputs option and new template is overcomplicated and in many cases this feature is needless.
Such a feature must be added via custom Node.vue

Ok, cool. How do you add or use a custom Node.vue?

Examples:
https://github.com/retejs/rete.js.org/blob/master/src/components/Examples/list/customization/index.js
https://github.com/retejs/rete.js.org/blob/master/src/rete/components/ecosystem/package/component.js

Ahh, got it thanks so much, appreciate the help! Awesome piece of code BTW!

You might still want to add the commonjs plugin to rete.config.js if you are having build errors with the latest version of rollup

I'll check it asap

This error also occurred for me after I reinstalled the dependencies.

You can update to v0.3.4


Update panasonic-comfort-cloud to 2.2.0

Hallo,
I updated the adapter panasonic-comfort-cloud to version 2.2.0
Thx :-)

Please update README.md to contain releasenotes for 2.2.0

@marc2016
Please update README.md to contain releasenotes for 2.2.0
(Does not require a new release, update at github is sufficient)

Done!

RE-CHECK!

2.2.0 created at 13.6.2023
OK


Update readme.md

Minor formatting fixes.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #627   +/-   ##
=======================================
  Coverage   34.51%   34.51%
=======================================
  Files          51       51
  Lines        5681     5681
=======================================
  Hits         1961     1961
  Misses       3527     3527
  Partials      193      193

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 8d7fa71...ed4000f. Read the comment docs.


Can I write the Jenkins global tool configuration for the Dependency Check as code?

Hi,
We are using the Jenkins Dependency-Check plugin. We use Docker containers for our local and live Jenkins servers and all plugin configuration is handled by Groovy code.
Have you an example of configuring the Jenkins Dependency-Check global tool configuration as code? Or documentation on the configuration classes?
Apologies if I have missed this, I have been searching high and low for an example, and it may be that I cannot see the wood for the trees.

You might want to check the Jenkins Users Google Group: https://groups.google.com/d/forum/jenkinsci-users
Since this functionality is specific to Jenkins and not the Dependency-Check plugin, you're more likely to find people with examples there.

Okay will do, thanks for the quick response.


Client: Simplify menu structure to CommonMenu with items bound to routes

The same for breadcrumbs - this will enable less classes 'round.

Done!


UI improvements suggestions

Larger characters - the presently used ones (at least as it looks under Linux) are too little for present day high-resolution monitors. Ideal would be 2x larger - if not, then at least by 50% larger.
I mean the characters used in App area - menus on the top line can remain.
Maybe could be possible to use more contrasty colour pairs? Present "brown on dark brown", "light brown on brown" - this is barely readable (white and turquoise are much better). My suggestion is to replace "brown on dark brown" with, for example, "orange on brown" and "light brown on brown" with "light green on brown".
Have a mercy over our eyes!

@ZbigniewB is this something that is still an issue?

@ZbigniewB is this something that is still an issue?

Just tried newest 1.1.19 version and I don't see these particular issues addressed. Still not possible to resize the font and still that low-contrast color scheme. In short: I have to wear glasses when using MyMonero to avoid any mistake. Please note that not all of MyMonero users are 20-years old, still having "eagle eye".

Fully understood. I took over the project mid-last year and there is a number of backlog issues like this one that we would like to address.
I will look at comparing it across the platforms to see if we can improve it based on your suggestions


Hero Image does not render on Vercel

Hi, I was looking for examples on how you handle images in posts and found that the hero images in the blog posts are not being rendered.
E.g. the anotherPost blog post clearly has a hero image but it is not being rendered on the deployed site
https://github.com/tinacms/tina-cloud-starter/blob/main/content/posts/anotherPost.mdx?plain=1#L3

Checking the Network tab in devtools reveals this error for the relevant request
invalid path: originals/3dc84ec5-afb8-4d5c-bc73-2cdff92539f6/tina-illustration.webp

I see this with a site created using tinacms init - I resolved it by opening the media manager and clicking the Sync button. @jamespohalloran do we need some additional documentation and/or better handling of media for a new project?

I see this with a site created using tinacms init - I resolved it by opening the media manager and clicking the Sync button.

Looks like our starter created with create-tina-app rather than an existing site added with tinacms init right?

@jamespohalloran do we need some additional documentation and/or better handling of media for a new project?

Was the problem here that Tina was added to a non-main branch?

You need to enable media in Tina Cloud dashboard.


Joystick type joint (2 DoF)

Hi,
I'm a student and I'm trying to use MuJoCo to create an environment for multi-agent reinforcement learning.
I'm trying to create a simple robot that uses joints behaving somewhat akin to joysticks. So basically, a ball joint that has the z-axis (rotational) degree of freedom removed.
What would be the best way to model this? Use two hinge joints perpendicular to each other?
Thanks for the help!

Yes.


question about HackAtari

Hi,
I forked the master branch from Fixed the README. After I tried to run it, I started to get theModuleNotFoundError: No module named 'hackatari'error message. I tried to install it manually using pip install hackatari, and then ran python train.py again. I got a problem with HackAtari initialization, as shown below. I saw that the game parameter was not provided during initialization. I wonder if this is related to the newly added features.
Traceback (most recent call last):
  File "train.py", line 242, in <module>
    main(**config)
  File "train.py", line 90, in main
    env = NudgeBaseEnv.from_name(environment, mode=algorithm, **env_kwargs)
  File "/Users/tianmingzhang/UNI/第八学期/explainableNudge/nudge/env.py", line 55, in from_name
    return env_module.NudgeEnv(**kwargs)
  File "in/envs/seaquest/env.py", line 25, in __init__
    self.env = HackAtari(env_name="ALE/Seaquest-v5", mode="ram",
TypeError: __init__() missing 1 required positional argument: 'game'

:) thx

Hey there, sorry for this.
env_name has been replaced by game in HackAtari init function, for consistency with OCAtari, I'll try to push a fix ASAP.

thx for the Guide. I have another question , is it possible , that we only try the policy reasoning module of NUDGE? when yes , how could I get the weight? :)

thx for the Guide. I have another question , is it possible , that we only try the policy reasoning module of NUDGE? when yes , how could I get the weight? :)

i have tried  python3 play.py -s 0 -alg logic -m getout -env getout
but have gotten this error :
Traceback (most recent call last):
  File "play.py", line 6, in <module>
    from env_src.procgen.render import render_loot, render_ecoinrun, render_threefish
  File "/Users/tianmingzhang/UNI/第八学期/explainableNudge/env_src/procgen/render.py", line 16, in <module>
    font = ImageFont.truetype(font_path, size=40)
  File "/usr/local/anaconda3/envs/Nudge/lib/python3.8/site-packages/PIL/ImageFont.py", line 807, in truetype
    return freetype(font)
  File "/usr/local/anaconda3/envs/Nudge/lib/python3.8/site-packages/PIL/ImageFont.py", line 804, in freetype
    return FreeTypeFont(font, size, index, encoding, layout_engine)
  File "/usr/local/anaconda3/envs/Nudge/lib/python3.8/site-packages/PIL/ImageFont.py", line 244, in __init__
    self.font = core.getfont(
OSError: cannot open resource

Apparently you are lacking some font, have you installed the pip package ? You should try to use Atari environments, they should be working on any OS.
To visualize the weights, you can look into this print_program function:
https://github.com/k4ntz/NUDGE/blob/96d18f5c7ecf3b715307da5aed815df7c7df3894/nudge/utils.py#L115

thx for the Guide. I have another question , is it possible , that we only try the policy reasoning module of NUDGE?

Yes, you can find the policy reasoning function here (the actor in the NsfrActorCritic class):
https://github.com/k4ntz/NUDGE/blob/master/nudge/agents/logic_agent.py#L21

thx for the Guide. I have another question , is it possible , that we only try the policy reasoning module of NUDGE?

Yes, you can find the policy reasoning function here (the actor in the NsfrActorCritic class): https://github.com/k4ntz/NUDGE/blob/master/nudge/agents/logic_agent.py#L21

thx so much for the answer, However, I still don't fully understand. Could I only try the reasoning part? If so, how could I obtain the pre-trained checkpoint? :)

Hi, i also have a little question , I have seen in train.py :
device: For example 'cpu' or 'cuda:0' The parameters can use cuda0. I would to ask if nsfr can use gpu for parallel training acceleration?
:)


How to set objc-options?

My .proto file has objc options:
syntax = "proto2";

package CompilerRPC;

// obj-c
import "objectivec-descriptor.proto";
option (google.protobuf.objectivec_file_options).package = "CompilerRPC";
option (google.protobuf.objectivec_file_options).class_prefix = "ASDTO";
option (google.protobuf.objectivec_file_options).relax_camel_case = true;
...

When trying to compile the files i'm getting an error:

MBA-Anton:ArduinoCode asmirnov$ protoc --objc_out=/tmp/ ./auth.proto
objectivec-descriptor.proto: File not found.
auth.proto: Import "objectivec-descriptor.proto" was not found or had errors.
MBA-Anton:ArduinoCode asmirnov$

if i comment this lines i'm able to generate .h/.m files

You are using not correct path for objectivec-descriptor.proto.
Create folder <your .proto files folder>/google/protobuf.
You should use protoc --proto_path= flag.
https://code.google.com/p/metasyntactic/issues/detail?id=135

i've followed https://github.com/alexeyxo/protobuf-objc, consider editing it as needed.
still not clear:

created folder 'google/protobuf'
edited file to 'import "google/protobuf/objectivec-descriptor.proto";'
invoke

'MBA-Anton:ArduinoCode asmirnov$ protoc --objc_out=/tmp/ ./auth.proto --proto_path=.
google/protobuf/objectivec-descriptor.proto: File not found.
auth.proto: Import "google/protobuf/objectivec-descriptor.proto" was not found or had errors.
MBA-Anton:ArduinoCode asmirnov$ ls ./google/protobuf/
MBA-Anton:ArduinoCode asmirnov$'

i've managed it by copying all /google/protobuf files from this repo to my project. is is required? IMHO It's not good to have this dependencies in my project as it relates to tool not to the project itself.

Another method does not exist. So working plugin in Protocol Buffers.


New website

Todo

[x] NextJS boilerplate
[x] Layout

[x] Flowbite react components
[x] footer
[x] docs layout

[x] max container width
[x] toggle sidebar (hamburger) on small screens
[x] sidebar search box
[x] fix sidebar chevrons
[x] fix sidebar left margin for nested collapse (use className directly)

[x] blog layout

[x] all articles
[x] single article

[x] marketing layout

[x] landing page / home
[x] fix contact / newsletter form
[x] reusable contact / sales form
[x] team page

[ ] Content

[ ] Team Bios
[ ] sitemap
[x] custom 404 and 500 pages
[x] favicon
[x] fix navbar link collapse on small devices
[x] customize format-enabled sections
[x] convert <a> to <Link>
[x] download images from githubusercontent
[x] fix TabsGroup styling
[x] fix Alert styling
[x] disable darkmode
[x] Add MDX support
[ ] migrate blog/web/docs pages to React Components
[x] Replace Docusaurus components and MDX blocks with alternatives

[x] CI

[x] Static analysis for ts/md(x)/js/css/html
[x] Build site to smoke test
[x] Rename www to website

Saving for part 2

[ ] Publish

[x] Move from Github Pages to Vercel to avoid possible usage policy violations
[x] Add PostHog analytics
[ ] Update DNS records
[ ] Check Google search console
[ ] Check for JS errors
[ ] Check page speed / optimization
[ ] Reconfigure Algolia Docsearch

Pull Request Test Coverage Report for Build 996822e93495c7bff6590b0b3b9211f780e71ac0-PR-1629

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

Totals

Change from base Build e1b8911b5455af760cf8c2b09ea628634fa71fd5:
0.0%

Covered Lines:
1966

Relevant Lines:
2781

💛  - Coveralls

@AndrewDryga Just requesting a quick scan through and approval, then I'll merge to master which should allow us to preview the deployment.

Screenshot of the new team page for context:

Hype!


✨ Mdsvex patch

This brings mdsvex to the site. I used a hook that is originally by @mikenikles on the gitpod website to provide the layout.children and frontmatter functionality from routify. I implemented the event section with this for demonstrate the functionality, but it's expandable for the other sections.
I also converted the config file and the main layout file because with the mdsvex installation my package manager also updated the sveltekit version.

@benmccann I converted the hook to an endpoint like you recommended (and it works). But I got a little bit stuck on the lifecycle handling of the whole thing, you can see this when reloading the events page; the console throws following:
Uncaught (in promise) TypeError: Cannot read property 'removeChild' of null
    at end_hydrating (index.mjs?v=5eb23a5c:202)
    at init (index.mjs?v=5eb23a5c:1548)
    at new Root (root.svelte? [sm]:15)
    at createProxiedComponent (svelte-hooks.js:245)
    at new ProxyComponent (proxy.js:240)
    at new Proxy<Root> (proxy.js:340)
    at Renderer._init (start.js:633)
    at Renderer.start (start.js:517)
    at async start (start.js:1083)

I wanted to ask you if you know what I'm doing wrong because I'm not good organized at handling lifecycles 🙈😅. If you find any other mistakes, let me know to.

@HAUDRAUFHAUN it looks like this project is using Svelte 3.38.1, which is a buggy version. If you upgrade to 3.38.2 hopefully that will fix the error you're seeing. Let me know if that helps or not

man i really wish we had gitpod or netlify deploy previews enabled so we can just pull up a preview here

I can open up another pr with a gitpod config @sw-yx 🙃

👍 Happy to review if you open one.

I'll look this over soon, been pretty busy these last few days

@kevmodrome what's the plan with this repo? Will you merge it into https://github.com/svelte-society/sveltesociety.dev ?

@kevmodrome what's the plan with this repo? Will you merge it into https://github.com/svelte-society/sveltesociety.dev ?

The plan is to archive the old one once this one is live


[DOCS] [7.x] Remove release dates from release notes

Removes release dates from Elasticsearch Hadoop release notes for the 7.x branch.
Backport of #1396. I plan to backport this to 7.5.
Relates to #1393 and #1396

master: a118254
7.5: 30682efa


Remove duplicate Environment and Variables keys

Prior to this commit, this repos SAM template included duplicate Environment and Variables keys which will cause parse failures for many tools, including Stackery's editor as demonstrated at https://app.stackery.io/editor/design?owner=aws-samples&repo=aws-cost-explorer-report&file=src/sam.yaml
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Fixed thanks :)


:sparkles: Add support for ImagePullSecrets in DeploymentSpec

What this PR does / why we need it:
In order to be able to pull provider images from a private registry we need to be able to also pass the image pull secrets so that we can authenticate to the registry while pulling the image.
This PR adds support for ImagePullSecrets option in provider DeploymentSpec

/ok-to-test

Fix for the linter issue: https://github.com/kubernetes-sigs/cluster-api-operator/pull/176

@adriananeci thank you for working on this!


Copy edits for spelling errors and typos

CLA signed (as @epc)
Solely affects docs subdirectory, no code changes.

@epc can you rebase?

@epc Thanks for the PR! LGTM. Just need to rebase and we can merge this.

Rebased.


ntrip_client: 1.0.0-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository ntrip_client to 1.0.0-1:

upstream repository: https://github.com/LORD-MicroStrain/ntrip_client.git
release repository: https://github.com/LORD-MicroStrain/ntrip_client-ros2-release.git
distro file: rolling/distribution.yaml
bloom version: 0.9.1
previous version for package: null

ntrip_client
* Initial implementation of ROS2 NTRIP client
* Adds ability to cache packets if they do contain some of a mesage but not the whole thing
* Contributors: drobb257, nathanmillerparker, robbiefish

Closing in favor of #31550 which adds documentation