Upgrade module to v5

Codecov Report

Merging #3 (cb46096) into master (582362b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   94.26%   94.26%
=======================================
  Files           7        7
  Lines         855      855
=======================================
  Hits          806      806
  Misses         33       33
  Partials       16       16

Flag
Coverage Δ

unittests
94.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 582362b...cb46096. Read the comment docs.


Used allow incorrectly instead of block

Fixed a typo in the documentation

@chrisda could you please merge this for me?


Add convenience wrapper for cancelling outstanding activities or document best practice

Currently trying to implement a scenario where OnWorkflowCancelRequested, all outstanding activities are requested to cancel, and then wait for those cancellations to process before then cancelling the workflow.
I've implemented cancelling all outstanding activities like this:
fsm.OnWorkflowCancelRequested(fsm.AddDecisions(cancelOutstandingActivities), fsm.Transition("waitForActivityCancellations"))

Where cancelOutstandingActivities looks like this:
var cancelOutstandingActivities = typed.MultiDecisionFunc(func(f *fsm.FSMContext, h *swf.HistoryEvent, d *StateData) []*swf.Decision {
	decisions := f.EmptyDecisions()
	for _, pendingActivity := range f.ActivitiesInfo() {
		cancelActivityDecision := &swf.Decision{
			DecisionType: aws.String(swf.DecisionTypeRequestCancelActivityTask),
			RequestCancelActivityTaskDecisionAttributes: &swf.RequestCancelActivityTaskDecisionAttributes{
				ActivityId: aws.String(pendingActivity.ActivityId),
			},
		}
		decisions = append(decisions, cancelActivityDecision)
	}
	return decisions
})

I then transition to waitForActivityCancellations where I'm waiting for all activities to either timeout, fail, complete, or cancel before I cancel the workflow.  But knowing when they are all done is challenging.  When events come in that would remove the activity from the correlator, they are not processed until after the event is seen by my decider.  Thinking about handling this with an interceptor that fires after the decider...
Currently have hacked around it by listening to activity timeouts, fails, completes and cancels, and if there is only 1 activity left in the correlator, verifying that it matches the incoming event.
Is there a better way to handle cancelling all outstanding activities?

This approach is reasonable, and we have done similar in at least one case here.
The other way to do it is to add some flags to your data struct, and flip them as you see the cancelations/fails/completes coming
type MyData struct {
   OtherStuff interface{}
   ActivityOneDone bool
   ActivityTwoDone bool
}

func allDone(data *MyData) bool {
   return data.ActivityOneDone && data.ActivityTwoDone
}

OnData(typed.PredicateFunc(allDone), fsm.CompleteWorkflow())

@sclasen Thanks.  What do you think about using a DecisionInterceptor.AfterDecision instead?  Wouldn't the activities list in the correlator be cleaned up by that point?

Also any thoughts on making a decider that handles this case as part of the library?  If you think it's a good approach, I could probably take a crack at it.

@ryanwalls yep and AfterDecision interceptor would work, the correlator would be cleaned up.
Sure, have a crack at that decider, no harm in including such a thing.


pls add relocating loader too

Use C compiler on system not online compilers

Use C compiler on system not online compilers


Please release new gem version

The last version is a few years old, and lacks some important changes:

Printing out the memory size for a generation
Printing out the total number of objects for the heap in the summary

I was about to add the latter feature myself, only to realize when I forked & cloned the repo that this functionality is already present in the latest master code. 😉
Thanks for a great tool!

v0.1.3 is released. Thanks for the note!


fix(openresty-patches) set_authority works on balancer phase

This change moves the ngx_http_lua_kong_set_grpc_authority to the create_request handler, so that the :authority header can be set in balancer retries, where the request is recreated.

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


Update codecov versions

Let's see if I managed to successfully setup codecov for this repo

It didn't work 😢
I don't know what I did wrong, I followed the instructions
https://app.codecov.io/gh/FluxML/SafeTensors.jl/new

I think you also need to install codecov for this repo https://github.com/apps/codecov

It seems installed... I don't know what else to do. @ToucheSir any idea?

According to https://app.codecov.io/gh/FluxML/SafeTensors.jl/new (needs login with GitHub first), we need to commit this config to the main branch first.
Also, they recommend this config:
- name: Upload coverage reports to Codecov
  uses<EMAIL_ADDRESS>  env:
    token: ${{ secrets.CODECOV_TOKEN }}
    slug: FluxML/SafeTensors.jl

Should we add the slug field?
Also also, should we make the CODECOV_TOKEN an org-wide secret like https://discourse.julialang.org/t/psa-new-version-of-codecov-action-requires-additional-setup/109857 suggests? We basically have to repeat this process for every repo that currently uses CodeCov.


configurable lookupd interval and buff

Hey @mreiferson ,
I am working with libnsq recently and make some update for it, please help to check it out.

Reconnectable for standalone nsqd
Configurable lookupd/reconnect interval.
Configurable buff length & capacity, via adding arguments of new_buffered_socket function in mreiferson/libevbuffsock#3.

this is great, thanks!

@mreiferson I've put those vars in the struct NSQDConnection, that makes codes simple and clear.

@belltoy thanks, this came out great - would you mind squashing down these commits?

@mreiferson rebased

@mreiferson Thanks for reviewing with patience 😃


Codegen bug caused by line wrapping of comment statements

I got a bad comment when I generated labservice: Bug
    NOT_APPLICABLE = "NotApplicable"  #: User either hasn't started configuring their template
or they haven't started the configuration process.
    COMPLETED = "Completed"  #: User is finished modifying the template.

my swagger config

hey @00Kai0 one thing I want to make clear is that AutoRest is not wrapping enum comments right now, it appears that a step further down in the autorest pipeline is doing this.
That being said, I do think it's worth it to wrap these comments, so will make a fix so AutoRest itself wraps these comments.
One thing to note is that we're adding support for a flag to black the generated code (pr here), which would deal with this. however, I think the outputted code should still have this wrapped regardless of whether you black the generated code or not, so still going to fix this


Update Cassandra C++ driver to 2.7.1

Hello, @andyone
cassandra-cpp-driver 2.7.1 has been released in September. It contains bug fixes without any incompatible changes, so I decide to update.

Looks good, merged. Thanks!


settings is undefined

First time clicking on a link intended to spawn colorbox results in the javascript error "settings is undefined". The little cycle arrows still work correctly.
If using the minified version of Colorbox <IP_ADDRESS>, this error seems to be "K is undefined"
Can be corrected by using this little amendment in slideshow() of the unminified version.
if (settings != undefined && settings.slideshow && $related[1]) {

Get same error in ie9. I used 1.3.18.

Then you are probably misusing the plugin, but there is nothing I can
do to help you since I can't see what you've done.  The example pages
certainly work with IE9.
On Thu, Oct 13, 2011 at 4:12 PM, vasia123
<EMAIL_ADDRESS>wrote:

Get same error in ie9. I used 1.3.18.
--
Reply to this email directly or view it on GitHub:
https://github.com/jackmoore/colorbox/issues/117#issuecomment-2400226

--
Jack Moore
colorpowered.com
twitter.com/jacklmoore

The error was my mistake, I connected a colorbox twice - in the head and before the closing tag body.  I apologize for such a hasty conclusion.

No problem, glad things worked out.
On Fri, Oct 14, 2011 at 3:10 AM, vasia123
<EMAIL_ADDRESS>wrote:

The error was my mistake, I connected a colorbox twice - in the head and before the closing tag body.  I apologize for such a hasty conclusion.
--
Reply to this email directly or view it on GitHub:
https://github.com/jackmoore/colorbox/issues/117#issuecomment-2404404

--
Jack Moore
colorpowered.com
twitter.com/jacklmoore

I concur with your Sep 27 comment.
I haven't had a chance to look at this again till today, and I haven't been able to replicate it. There must have been some kind of conflict with a minification, jquery UI or some other dunce plugin we're using.

I concur with your Sep 27 comment.
I haven't had a chance to look at this again till today, and I haven't been able to replicate it. There must have been some kind of conflict with a minification, jquery UI or some other dunce plugin we're using.


Mobile first

Previously in issues assigned it was mentioned that Indonesia's primary device is the phone, show this in code here is a link on information on mobile first design.
https://zellwk.com/blog/how-to-write-mobile-first-css/

make all pages mobile first


fix: exclude python system packages for versioned extension

We install the dependencies for an extension version in a specific path for that version alone. When one of our plpython3u functions is called, we set up the python path to include these dependencies.
For the very first extension releases, we didn't do it this way. Instead, the dependencies were installed into the system python's path. As a result, we were inadvertently using both packages installed for the system python, and the packages installed for the specific extension version. When the same package is installed in both, the system python version is chosen first. This breaks Python's assumptions about dependency resolution, and can break installed packages.
This change removes the system python dependencies from the python path, so only the actual dependencies we wanted are available.

Note: this hasn't affected us until now. The litellm python library has a dependency on a specific version of the openai client library, which is greater than the version specified in our old_requirements.txt, so litellm doesn't work.


yo office will put every files on level up to the parent folder

yo office will put every files on level up to the parent folder. i am using node v8.11.2. Is is a bug?

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

ID: 15be7148-d1e8-b58b-b026-9f072efb638a
Version Independent ID: 53a5d00c-d82b-6536-2e80-3e2a3452879a
Content: Build an Outlook add-in
Content Source: docs/add-ins/quick-start.md
Product: outlook
GitHub Login: @jasonjoh
Microsoft Alias: jasonjoh

Please file this over on the generator-office repository.


systemd/system: add<EMAIL_ADDRESS>

this service allows to conditionnally start the
<EMAIL_ADDRESS>on DO, EM, EC2 and GGE with the default core instance in order to control the<EMAIL_ADDRESS>from the generic image and not from the OEM.

See: https://github.com/flatcar/scripts/pull/1083 for context, CI and cie.

It still has the @ in it, I think the file name could be sshkeys.service


📦 NEW: Add support for @wordpress imports

Improves #59, fixes #27.
This little patch provides support for the import { … } from '@wordpress/…'; syntax. Tested on Win7 x64 with WordPress 3.9.6 and a slightly modified Columns block straight out of the Gutenberg github. Node 10.2.1, npm 5.6.0.
The main difference from the Gutenberg and the GCF exports, is that the syntax externals["@wordpress/" + wpDependency] = { this: ["wp", wpDependency] }; would result in a lot of undefined errors at runtime, while externals[ '@wordpress/${ name }' ] = 'wp.' + wpDependency works as intended. Both compile equally fine, though.
An excerpt from the source I used for the component and a screen of it showing in the editor:
edit( { attributes, setAttributes, className } ) {
  const { columns } = attributes;
  const classes = classnames( className, `has-${ columns }-columns` );

  return (
    <Fragment>
      <InspectorControls>
        <PanelBody>
          <RangeControl
            label={ __( 'Columns' ) }
            value={ columns }
            onChange={ ( nextColumns ) => {
              setAttributes( {
                columns: nextColumns,
              } );
            } }
            min={ 1 }
            max={ 6 }
          />
        </PanelBody>
      </InspectorControls>

        <InnerBlocks layouts={ getColumnLayouts } />

    </Fragment>
  );
},

save( { attributes } ) {
  const { columns } = attributes;

  return (
    <div className={ `has-${ columns }-columns` }>
      <InnerBlocks.Content />

  );
},

Thanks for the contribution @Varstahl since I am traveling, I am paging a friend @richtabor do you have time to review this PR?
CC: @asharirfan

@Varstahl  This is working great and it's a much needed feature. Only thing it needs to be updated since
ga: 'ga', // Old Google Analytics.
gtag: 'gtag', // New Google Analytics.
jquery: 'jQuery', // import $ from 'jquery' // Use the WordPress version.

Were added to packages/cgb-scripts/config/webpack.config.dev.js in the mean time. Not sure why they are not on the prod version.

Fixed the merge conflict and updated webpack.config.prod.js.

This was added in a different way without so much repetition take a look https://github.com/ahmadawais/create-guten-block/blob/master/CHANGELOG.md
Thanks anyways 👍


Linker warning "_getentropy is not implemented and will always fail"

Trying to compile my project i get the following warning after an OS upgrade that also brought in a new version of GCC:
/usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/bin/ld: /usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/lib/thumb/v6-m/nofp/libc.a(libc_a-getentropyr.o): in function `_getentropy_r':
/build/newlib-38V0JC/newlib-<IP_ADDRESS>31231/build/arm-none-eabi/thumb/v6-m/nofp/newlib/../../../../../../newlib/libc/reent/getentropyr.c:48:(.text+0xe): warning: _getentropy is not implemented and will always fail
/usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/bin/ld: /usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/lib/thumb/v6-m/nofp/libc.a(libc_a-getentropyr.o): note: the message above does not take linker garbage collection into account

OS: Ubuntu 24.04
GCC: arm-none-eabi-gcc (15:13.2.rel1-2) 13.2.1 20231009
SDK: v1.6.1
Can this safely be ignored for now or can i do something against this, besides downgrading the compiler?

i have not seen this; can you provide a minimal repro; is this with C++? are you calling something that might need getentropy?

I saw this when I upgraded to the latest LTS of Ubuntu. It might be something that gets noticed with a new version of GCC and/or a new version of newlib?

This at least shows that this problem isn't specific to just pico-sdk :wink:

Yeah, i'm sure it is a problem with newlib however the reason I asked for a repro case, is that i couldn't reproduce it!!

Sorry, haven't gotten around to create one yet. I don't want to FOSS my project just yet as i want it in a releaseworthy state, but if you could keep it under the lid until i am prepared to release it i could send you a copy.
I am using Elmchans FatFS as a library but everything else is just the normal Pico SDK and the normal C and C++ library.

As a sidenote, everything works as expected, so for now it seems one can ignore that warning.

ok, yeah maybe just worth looking at the .DIS file and see if there are any references to entropy

CLion says "Nope"

Oh, cool, this is my whole project in assembler, thanks for showing me that! ❤

Not sure if you still need that minimal repro case, but here's mine:
CMakeLists.txt
cmake_minimum_required(VERSION 3.5)
include($ENV{PICO_SDK_PATH}/external/pico_sdk_import.cmake)
set(PICOTOOL_FETCH_FROM_GIT_PATH $ENV{PICO_SDK_PATH}/fetch)
set(target_proj bug)
project(${target_proj} C CXX)
pico_sdk_init()
add_executable(${target_proj} main.cpp )
target_link_libraries(${target_proj}  pico_stdlib )

main.cpp:
#include <queue>

int main()
{
    std::queue<int> queue;
}

build commands:
#! /bin/bash
rm -rf build
/usr/bin/cmake -DCMAKE_BUILD_TYPE:STRING=Debug -S. -B./build
/usr/bin/cmake --build ./build --config Debug --target all

It seems the -DCMAKE_BUILD_TYPE is part of the trigger.   If that's not present, I don't see the warnings

Thanks @dementedmonkey , I can confirm that I was able to reproduce this linker waning with your minimal example :+1:  And I can also confirm that the warning doesn't appear if I change the CMAKE_BUILD_TYPE to Release.
@kilograham I used Docker to test this in different versions of Ubuntu last night, and the warning doesn't appear in Ubuntu 23.04 or Ubuntu 23.10 (which both use arm-none-eabi-gcc 12.2.1 and libnewlib-arm-none-eabi 3.3.0), but with Ubuntu 24.04 or Ubuntu 24.10 (which both use arm-none-eabi-gcc 13.2.1 and libnewlib-arm-none-eabi 4.4.0) the build-output includes this warning right at the end:
[ 98%] Building C object CMakeFiles/bug.dir/build_output/git.pico-sdk/src/rp2_common/pico_stdio_uart/stdio_uart.c.o
[100%] Linking CXX executable bug.elf
/usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/bin/ld: /usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/lib/thumb/v6-m/nofp/libg.a(libc_a-getentropyr.o): in function `_getentropy_r':
/build/newlib-38V0JC/newlib-<IP_ADDRESS>31231/build/arm-none-eabi/thumb/v6-m/nofp/newlib/../../../../../../newlib/libc/reent/getentropyr.c:48:(.text+0xe): warning: _getentropy is not implemented and will always fail
/usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/bin/ld: /usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/lib/thumb/v6-m/nofp/libg.a(libc_a-getentropyr.o): note: the message above does not take linker garbage collection into account
[100%] Built target bug

I may be able to contribute a hint here.
This code produces the warning:
struct test{
   test() : x{0} {};
   int x;
};

int main(){
   static test a;
}

This one does not:
struct test{
   constexpr test() : x{0} {};
   int x;
};

int main(){
   static test a;
}

The first version creates calls to __cxa_guard_acquire and __cxa_guard_release which seem to be intended to prevent access to not yet fully constructed static objects.
My hypothesis is that they somehow depend on randomness to randomize locking attempts.


Connection time out in TCP integration

https://github.com/artikcloud/leshan/tree/tcp-integration
@AlexITC
Request message cannot be sent from server side

This is issue is for https://github.com/artikcloud/leshan not https://github.com/eclipse/leshan, right ?

@AlexITC do you want to reply here ? or do you plan to open issue tab/column for artikcloud/leshan ?
Anyway, @anubhavaron I think that @AlexITC will not be able to give you a good answer without more detail about context. (step to reproduce, logs, wireshark capture, version used ...)

@AlexITC can you give the link for dowloading californium 2.0.0 M6 - Artikcloud.

@AlexITC we were using https://github.com/artikcloud/leshan/tree/tcp-integration this version. It had different server and client demos for tcp and udp. The link you provided has only one demo. Is it using TCP or udp?

It has exactly the same demos that are in the leshan project, here you could see more examples: https://github.com/artikcloud/artikcloud-lwm2m-java/tree/leshan-1.0.0-artik

Could we close this issue ?


140 failing unit tests on develop

With both clang and GCC I have 140 failing unit tests on the develop branch. Its always somthing like:
    "g++-6"   -fPIC -m64 -O0 -fno-inline -Wall -g -std=gnu++1z -DBOOST_ALL_NO_LIB=1  -I"../../.." -I"../include" -I"_include" -c -o "../../../bin.v2/libs/hana/test/test~ext~boost~fusion~deque~auto~at.test/gcc-6/debug/ext/boost/fusion/deque/auto/at.o" "ext/boost/fusion/deque/auto/at.cpp"

...failed gcc.compile.c++ ../../../bin.v2/libs/hana/test/test~ext~boost~fusion~deque~auto~at.test/gcc-6/debug/ext/boost/fusion/deque/auto/at.o...
...skipped <p../../../bin.v2/libs/hana/test/test~ext~boost~fusion~deque~auto~at.test/gcc-6/debug>test~ext~boost~fusion~deque~auto~at for lack of <p../../../bin.v2/libs/hana/test/test~ext~boost~fusion~deque~auto~at.test/gcc-6/debug>ext/boost/fusion/deque/auto/at.o...
...skipped <p../../../bin.v2/libs/hana/test/test~ext~boost~fusion~deque~auto~at.test/gcc-6/debug>test~ext~boost~fusion~deque~auto~at.run for lack of <p../../../bin.v2/libs/hana/test/test~ext~boost~fusion~deque~auto~at.test/gcc-6/debug>test~ext~boost~fusion~deque~auto~at...
gcc.compile.c++ ../../../bin.v2/libs/hana/test/test~ext~boost~fusion~deque~auto~any_of.test/gcc-6/debug/ext/boost/fusion/deque/auto/any_of.o
In file included from ../../../boost/type_traits/is_convertible.hpp:20:0,
                 from ../../../boost/type_traits/is_empty.hpp:12,
                 from ../../../boost/mpl/empty_base.hpp:23,
                 from ../../../boost/fusion/sequence/intrinsic/at.hpp:15,
                 from ../../../boost/hana/ext/boost/fusion/detail/common.hpp:22,
                 from ../../../boost/hana/ext/boost/fusion/deque.hpp:16,
                 from ext/boost/fusion/deque/auto/_specs.hpp:8,
                 from ext/boost/fusion/deque/auto/any_of.cpp:5:
../../../boost/type_traits/is_convertible.hpp: In instantiation of ‘struct boost::is_convertible<boost::hana::ext::boost::fusion::deque_tag, boost::fusion::detail::from_sequence_convertible_type>’:
../../../boost/mpl/aux_/nested_type_wknd.hpp:26:31:   required from ‘struct boost::mpl::aux::nested_type_wknd<boost::is_convertible<boost::hana::ext::boost::fusion::deque_tag, boost::fusion::detail::from_sequence_convertible_type> >’
../../../boost/mpl/not.hpp:39:8:   required from ‘struct boost::mpl::not_<boost::is_convertible<boost::hana::ext::boost::fusion::deque_tag, boost::fusion::detail::from_sequence_convertible_type> >’
../../../boost/mpl/aux_/nested_type_wknd.hpp:26:31:   required from ‘struct boost::mpl::aux::nested_type_wknd<boost::mpl::not_<boost::is_convertible<boost::hana::ext::boost::fusion::deque_tag, boost::fusion::detail::from_sequence_convertible_type> > >’
../../../boost/mpl/aux_/preprocessed/gcc/and.hpp:48:8:   required from ‘struct boost::mpl::and_<boost::mpl::not_<boost::is_convertible<boost::hana::ext::boost::fusion::deque_tag, boost::fusion::detail::from_sequence_convertible_type> >, boost::mpl::is_sequence<boost::hana::ext::boost::fusion::deque_tag>, mpl_::bool_<true>, mpl_::bool_<true>, mpl_::bool_<true> >’
../../../boost/fusion/support/detail/is_mpl_sequence.hpp:21:12:   [ skipping 2 instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ]
../../../boost/fusion/support/tag_of.hpp:52:16:   required from ‘struct boost::fusion::detail::tag_of_impl<boost::hana::ext::boost::fusion::deque_tag, void>’
../../../boost/fusion/support/tag_of.hpp:70:16:   required from ‘struct boost::fusion::traits::tag_of<boost::hana::ext::boost::fusion::deque_tag, void>’
../../../boost/hana/core/tag_of.hpp:22:12:   required from ‘struct boost::hana::tag_of<boost::hana::ext::boost::fusion::deque_tag, void>’
../../../boost/hana/concept/searchable.hpp:27:13:   required from ‘struct boost::hana::Searchable<boost::hana::ext::boost::fusion::deque_tag>’
../../../boost/hana/any_of.hpp:41:10:   required from ‘constexpr auto boost::hana::any_of_t::operator()(Xs&&, Pred&&) const [with Xs = boost::fusion::deque<>; Pred = <lambda()>::<lambda(auto:2)>]’
_include/auto/any_of.hpp:22:5:   required from here
../../../boost/static_assert.hpp:31:45: error: static assertion failed: From argument type to is_convertible must be a complete type
 #     define BOOST_STATIC_ASSERT_MSG( ... ) static_assert(__VA_ARGS__)
                                             ^
../../../boost/type_traits/is_convertible.hpp:484:4: note: in expansion of macro ‘BOOST_STATIC_ASSERT_MSG’
    BOOST_STATIC_ASSERT_MSG(boost::is_complete<From>::value || boost::is_void<From>::value || boost::is_array<From>::value, "From argument type to is_convertible must be a complete type");
    ^~~~~~~~~~~~~~~~~~~~~~~

The From is a Hana-Tag struct (boost::hana::ext::boost::fusion::deque_tag in this case) which is not complete. (BTW: Are Hana-Tags required to be compete? The documentation does not mention this explicitly, but in the examples they are not.)

Hana tags should not be required to be complete. I can't reproduce locally using the classic CMake workflow and Boost 1.65.1. Also, Travis CI does not report any failure. Can you please provide a minimal complete example of how you're setting up Hana to reproduce?

I used bjam in the test directory to compile the tests.
$ bjam toolset=gcc
$ bjam toolset=clang

I can reproduce it with a newly checked-out repository:
git clone --recursive "https://github.com/boostorg/boost.git" modular-boost
cd modular-boost
git checkout develop
git submodule foreach git checkout develop
./bootstrap.sh
./b2 headers
PATH=$(pwd):$PATH
cd libs/hana/test/
bjam toolset=gcc -j 8

I could not reproduce locally, even with your instructions, but now I just saw it fail on Travis: https://travis-ci.org/boostorg/hana/jobs/346757876. I'll look into that.

I believe this is a Fusion bug. I am able to reproduce with this:
#include <boost/fusion/include/tag_of.hpp>
struct incomplete;
using X = ::boost::fusion::traits::tag_of<incomplete>::type

int main() { }

My guess is that Fusion used to accept incomplete types in tag_of, but they don't anymore.

Ok, I believe this started happening in https://github.com/boostorg/type_traits/commit/ac351390b215b73d8a9e16d2ca37ba2d9d88a14f. Presumably, fusion::tag_of using a type trait that requires the input type to be complete, but it does not check for that (and it doesn't document that the input of tag_of must be complete AFAICT).

This should have been fixed in Fusion now. Thanks a lot for reporting, this could have been a big breakage.


Doesn't work with rails 6.1

You still haven't added support for activestorage 6.1 which goes together with rails 6.1 so you never added support for rails 6.1

Sorry, @mices, this package isn't maintained anymore.

In Gemfile:
has_friendship was resolved to 1.1.8, which depends on
activesupport (>= 4.2.0, < 6.1)
rails (~> 6.1.0) was resolved to 6.1.4, which depends on
  activesupport (= 6.1.4)

Running bundle update will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
Bundler could not find compatible versions for gem "rails":
In snapshot (Gemfile.lock):
rails (= 6.1.4)
In Gemfile:
rails (~> 6.1.0)
has_friendship was resolved to 0.0.3, which depends on
  rails (~> 4.1.8)

Sorry, I just needed to use the master branch It bundles with rails 6.1.4, so it works


chore: nft shape urn update

issue: https://github.com/decentraland/sdk/issues/745
other related PRs:

https://github.com/decentraland/js-sdk-toolchain/pull/575
https://github.com/decentraland/unity-renderer/pull/5154

Apparently wearables should be supported now so the implementation will longer, going back to draft

Supporting decentraland wearable/emote NFTs with raw urns will be tackled in another issue post-beta phase
Tried to implement matic nfts fetching support but Opensea API doesn't support fetching nft info from non-ethereum chains yet


Add header clearing

Can we add a little more context to the PR? Why was this added, what's it going to solve?


Cannot delete a cloud launch

Hi, I wanted to delete this active appliance but the website is not letting me do it. Can you please help me with this problem?
thomas3-genomics-virtual-lab-20-12-24t21-23Appliance: Genomics Virtual Lab (GVL)Version: GVL 4.3.0 (Galaxy 17.09)Cloud: Amazon Web Services | 7 hours ago | UNABLE TO CHECK STATUSHealth check failed: CloudBridgeBaseException: Unable to locate credentials from exception type: <class 'botocore.exceptions.NoCredentialsError'> Report this failure? | http://<IP_ADDRESS>/ |
-- | -- | -- | -- | --
Thanks,
Thomas

You can only delete applications from CloudLaunch if you've saved credentials. See: https://github.com/galaxyproject/cloudlaunch/issues/212#issuecomment-672057147


Q14siX.de.VokabularWAV-Maker version <IP_ADDRESS>

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree [company="Q14siX.de"]

@microsoft-github-policy-service agree


HBParameters doesn't handle repeating query parameters.

Just came across some API calls here with repeating query parameters. Things like ...?category=cars&category=engines (a bit contrived but still possible). I looked in the code for HBParameters and it's coded like I would have done it in that it's baed on a dictionary. But with this new information it needs to be able to handle repeating keys with different values. So I'm thinking more like an array of tuples or some simple struct type.

Another common way to store these is to store an array of strings in place of a single string. I think I'll do that instead. So it would be a [String: [String]] instead of a [String]

Sounds good. Would it create any issue for retrieving values though since the result could be a single String or a [String].

I would probably include a separate API for accessing multiple parameters. The current api would just return the string or the first element of the array depending on what is stored.

You wanna check out #139


cowboy shouldn't close connection after 60s when it's streaming a response

as it says in: https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_http/

idle_timeout (60000)
Time in ms with no data received before Cowboy closes the connection.

cowboy will close the connection after 60 seconds of not hearing from the client.
This is, in most of the cases, a reasonable measure: if you take more than 60 seconds to process a response, then the problem is you, not the server.
However, when streaming responses (such a video, or a large csv, for instance) using send_chunked() and chunk(), this is an annoyance, because in order for it to work you need to set idle_timeout as :infinity for every kind of response (streamed and not streamed) and that's not cool.

Cowboy can't differentiate between legitimate and illegitimate long running requests when using HTTP/1.1. That's why https://ninenines.eu/docs/en/cowboy/2.8/manual/cowboy_stream/#_set_options was introduced a while back. You can use it to update idle_timeout for this request/response specifically. There's an example for this at https://ninenines.eu/docs/en/cowboy/2.8/manual/cowboy_req.cast/#_examples

Oh boy! I have to say I'm having the hardest time trying to figure out how to use cowboy_req.set_options inside phoenix infrastructure, this is clearly beyond my league :-(

You just need to send a message to the Cowboy connection process, you don't have to use cowboy_req.

well, for the sake of anybody who's going through the same trouble, thanking @essen and also this more than great post, I've managed to dinamically change idle_timeout for a cowboy server on a per requests basis:
in config.exs, added a custom cowboy stream handler, MyApp.Middleware.TimeoutHandler:
config :api, MyApp.Endpoint,
  http: [port: 4000, stream_handlers: [MyApp.Middleware.TimeoutHandler, :cowboy_stream_h]],
  render_errors: [view: MyApp.ErrorView, accepts: ~w(json)]

and the stream handler itself. who icreases idle_timeout for a certain request path
defmodule MyApp.Middleware.TimeoutHandler do
  @moduledoc """
  A cowboy stream handler -called for every request- that checks if it needs
  to maintain connection open for longer than a minute in case it's a streamed response
  """

  @behaviour :cowboy_stream

  @doc """
  called during several stages of the request-response lifecycle. (info defines that)
  """
  def info(stream_id, info, state), do: :cowboy_stream.info(stream_id, info, state)

  def init(stream_id, req, opts) do
    # if it's a streaming response, keep conn open
    if String.contains?(req.path , "/stats/query_log") do
      :cowboy_req.cast({:set_options, %{idle_timeout: :infinity}}, req)
    end
    :cowboy_stream.init(stream_id, req, opts)
  end

  def data(stream_id, is_fin, info, state),
    do: :cowboy_stream.data(stream_id, is_fin, info, state)

  def early_error(stream_id, reason, partial_req, resp, opts),
    do: :cowboy_stream.early_error(stream_id, reason, partial_req, resp, opts)

  def terminate(stream_id, reason, state), do: :cowboy_stream.terminate(stream_id, reason, state)
end

@essen, as embarrassing as it sounds, I couldn't find how to send a message to the cowboy connection process, I couldn't even find how to reference it :disappointed:  so I have to settle with this not-entirely-elegant solution instead :disappointed_relieved:

Oh well. At least you got it working so that's fine. And now you know about stream handlers, which might help you again in the future.


Async initialization in Main not working

Description:

I want/need to do some basic initialization on app startup, like calling an API and getting my initial configuration.
I found a neat solution that it could be done in async Main for ASP Core, so I tried to reproduce it for Blazor.
But, it seems that app just "hangs" in the browser.
You'll find Autofac setup below, but it works fine, it's the Task.Delay part that breaks the App.
Of course, in my code that delay only simulates API call.
If there is better way to achieve this, please provide a sample - actually and update to official docs would be great, as this will be a common scenario.
Again - this is initial/global initialization, not specific page initialization ;).

To Reproduce:

public class Program
    {
        public static async Task Main(string[] args)
        {
            IWebAssemblyHost host = CreateHostBuilder(args).Build();
            await Initialize(host);
            host.Run();
        }

        public static IWebAssemblyHostBuilder CreateHostBuilder(string[] args) =>
            BlazorWebAssemblyHost.CreateDefaultBuilder()
                .UseServiceProviderFactory(new AutofacServiceProviderFactory(b => b.RegisterModule<ClientModule>()))
                .UseBlazorStartup<Startup>();

        public static async Task Initialize(IWebAssemblyHost host)
        {
             await Task.Delay(2000);
        }
    }

Other info:
Client side Blazor 3.1.10
Preview Visual Studio 16.5

@SteveSandersonMS - hi, sorry to bother you, but I believe you might find this scenario interesting.
Much :heart: to Blazor, it's the best thing MS did in the last decade!

Thanks for contacting us!
async main isn't supported in the version of Blazor you're using currently. However the good news is that we have implemented support for it since the last release, and the feature will be included in the next preview release within the next month.

Wow, awesome! Thanks.

hi @SteveSandersonMS
Is it possible to use two await inside a blazor lifecyle method as like below.
**protected override async Task OnInitializedAsync() {
//this action is performed.
forecasts = await Http.GetJsonAsync<WeatherForecast[]>("sample-data/weather.json");
// this action is not perfomred
await someOperation();
}**
Any suggestion for this query ?

Yes, multiple awaits works fine. Blazor doesn’t even know you are doing that as it’s inherent to C# itself.
If your code isn’t working that way, you have some other issue.


module 'gst' not available after roc master upgraded to roc_master_10133

Upgrade roc master release to the most recent best known version roc_master_10133.
Build and run RVS, got the following errors. Other modules seem working fine.
root@IVT9Lucy:~/RVS/build/bin/conf# ~/RVS/build/bin/rvs -c gst_1.conf
RVS-ERROR [CLI] could not load .so '/root/RVS/build/bin//libgst.so'
RVS-ERROR [CLI] reason: '/opt/rocm/lib/librocblas.so.0: undefined symbol: _ZN8hip_impl22hipLaunchKernelGGLImplEmRK4dim3S2_jP12ihipStream_tPPv'
RVS-ERROR [CLI] module 'gst' not available.
RVS-ERROR [CLI] action 'action_1' could not crate action object in module 'gst'

Try building a local copy of rocblas, adjust your cmake as follows:
 cd myrvs20190701/
 git clone https://github.com/ROCm-Developer-Tools/ROCmValidationSuite.git
 cd ROCmValidationSuite/
 cmake  -DRVS_ROCBLAS=1 ./ -B../build
 make -C ../build
 cd ..
 cd build/
 cd bin
 sudo ./rvs -d 3


update to Eigen 3.3.8

I know there was an update not too long ago but there seems to be plenty of bug fixes since. See the changelog.

Thanks!
We need to wait for 3.3.8 to also be available in RcppEigen because that is what rstan uses and we want to be in-sync.
We could also just upgrade as:

by the time there will be the next rstan release RcppEigen will most likely use 3.3.8
its a patch release, so there should be no interfacing changes that would break rstan

I asked the Rcppeigen devs on the timeline and if any of us can help: https://github.com/RcppCore/RcppEigen/issues/91

There is a build failure with Eigen 3.3.9 (and possibly 3.3.8). I get
In file included from /home/ben/r-devel/library/StanHeaders/include/stan/math/rev/core/matrix_vari.hpp:4,
                 from /home/ben/r-devel/library/StanHeaders/include/stan/math/rev/core.hpp:16,
                 from ./stan/model/model_base.hpp:5,
                 from Module.cpp:2:
/home/ben/r-devel/library/StanHeaders/include/stan/math/rev/mat/fun/Eigen_NumTraits.hpp:200:77: error: wrong number of template arguments (8, should be 9)
                                      RhsStorageOrder, ConjugateRhs, ColMajor> {
                                                                             ^

This is with Stan Headers set to develop Stan Math or Stan Math 3.4.0?

Current everything on CRAN except drat RcppEigen 3.3.9. I should have probably included more of the error message:
In file included from /home/ben/r-devel/library/StanHeaders/include/stan/math/rev/core/matrix_vari.hpp:4,
                 from /home/ben/r-devel/library/StanHeaders/include/stan/math/rev/core.hpp:16,
                 from ./stan/model/model_base.hpp:5,
                 from Module.cpp:2:
/home/ben/r-devel/library/StanHeaders/include/stan/math/rev/mat/fun/Eigen_NumTraits.hpp:200:77: error: wrong number of template arguments (8, should be 9)
                                      RhsStorageOrder, ConjugateRhs, ColMajor> {
                                                                             ^
In file included from /home/ben/r-devel/library/RcppEigen/include/Eigen/Core:454,
                 from /home/ben/r-devel/library/RcppEigen/include/Eigen/Dense:1,
                 from /home/ben/r-devel/library/StanHeaders/include/stan/math/prim/mat/fun/Eigen.hpp:13,
                 from /home/ben/r-devel/library/StanHeaders/include/stan/math/prim/mat/meta/append_return_type.hpp:4,
                 from /home/ben/r-devel/library/StanHeaders/include/stan/math/prim/meta.hpp:9,
                 from /home/ben/r-devel/library/StanHeaders/include/stan/math/memory/stack_alloc.hpp:7,
                 from /home/ben/r-devel/library/StanHeaders/include/stan/math/rev/core/autodiffstackstorage.hpp:4,
                 from /home/ben/r-devel/library/StanHeaders/include/stan/math/rev/core.hpp:4,
                 from ./stan/model/model_base.hpp:5,
                 from Module.cpp:2:
/home/ben/r-devel/library/RcppEigen/include/Eigen/src/Core/util/BlasUtil.h:35:8: note: provided for ‘template<class Index, class LhsScalar, int LhsStorageOrder, bool ConjugateLhs, class Rh$
 struct general_matrix_matrix_product;
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It seems that an emergency StanHeaders will have to uploaded to CRAN that branches on EIGEN_MINOR_VERSION in order to preserve compatibility with all the existing CRAN packages and pave the way for RcppEigen to upgrade to 3.3.9. Do we at least understand what we have to do with the 8 vs. 9 template arguments to the NumTraits thing?


LLM router basic template

Implementing:

basic flow for data labeling with gpt4 as a judge
basic flow for evaluation

To do:

add 1-2 simple baslines (frequency, BoW classifier)
Iterate on the explanation and overall story

In a following commit:

finetune llm router

Need to rename the branch name to avoid / for template to run


Add information on supported version skew and upgrade order

Fixes https://github.com/kubernetes/website/issues/7103
Preview available at: https://deploy-preview-11060--kubernetes-io-master-staging.netlify.com/docs/setup/version-skew-policy/
We have a document that details the deprecation policy for APIs, but no document on the website detailing supported versions and version skew between Kubernetes components.
This is important information to make clear, for many reasons:

it has implications for component upgrade order
it is necessary for cluster deployers to know what the skew guarantees are so they know what to deploy
it is necessary for component owners to know what skew they are expected to support so they know what cases to handle
it is important for reviewers to know what changes are acceptable to make in a given release

This PR attempts to clarify the currently supported state of supported Kubernetes versions and component version skew.
I'd like to resolve the following questions, get feedback from various sigs, and merge this around the time 1.13 releases (and mention it in the release notes), currently targeted for 12/3.
follow-up discussion topics/updates:

[ ] what version skew does the kube-proxy component support relative to the apiserver and kubelet? @kubernetes/sig-network-pr-reviews - https://github.com/kubernetes/website/issues/12322
[ ] is a specific upgrade order between kube-proxy and kubelet required? @kubernetes/sig-network-pr-reviews, @kubernetes/sig-node-pr-reviews - https://github.com/kubernetes/website/issues/12322
[ ] is a specific upgrade order between kube-controller-manager and kube-scheduler required? @kubernetes/sig-api-machinery-pr-reviews, @kubernetes/sig-scheduling-pr-reviews - https://github.com/kubernetes/website/issues/12323
[ ] should we add requirements (or at least a strong recommendation) to be at latest patch version of 1.x prior to upgrades, and upgrade to latest patch version of 1.x+1 (since that is what we test, and what we can fix if broken)? @kubernetes/sig-architecture-pr-reviews @kubernetes/sig-release @kubernetes/sig-cluster-lifecycle-pr-reviews - https://github.com/kubernetes/website/issues/12324
[ ] add details to kubelet upgrade procedure (whether drain is required, whether skip-level kubelet upgrades are supported, etc) @kubernetes/sig-node-pr-reviews @kubernetes/sig-storage-pr-reviews - https://github.com/kubernetes/website/issues/12326
[ ] what statement should be made about new features in version 1.x when running with a 1.x+ control plane and kubelets older than 1.x? is the user responsible for labeling nodes and workloads to only steer pods using those features to nodes with those capabilities? @kubernetes/sig-node-pr-reviews @kubernetes/sig-architecture-pr-reviews - https://github.com/kubernetes/website/issues/12325
[ ] control plane downgrade (and safe rollback in rolling HA upgrade) (https://github.com/kubernetes/website/pull/11060#discussion_r237614607, https://github.com/kubernetes/website/pull/11060#issuecomment-440142623, https://github.com/kubernetes/website/pull/11060#discussion_r237616387) - https://github.com/kubernetes/website/issues/12327
[ ] what is our stated support or testing for transitive or third-party dependencies? - https://github.com/kubernetes/website/issues/12328

are they completely out of scope?
is there a recommended or supported order for upgrading etcd vs. the control plane components?
when we say we recommend container engine A at version B for k8s release 1.n, does that imply we expect k8s release 1.n+2 to support the same?
should this be in a machine-consumable format as well?

references:

https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew
https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/patch-release-manager/README.md#release-timing
https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecating-parts-of-the-api

This covers the maximum supported version skew of 2 releases.

relevant owners for open questions:

[x] @kubernetes/sig-architecture-pr-reviews - overall support statement, discussed in sig-arch on 11/29 - https://github.com/kubernetes/website/pull/11060#issuecomment-445383166
[x] @kubernetes/sig-cluster-lifecycle-pr-reviews - upgrade order and kubeadm doc updates - https://github.com/kubernetes/website/pull/11060#issuecomment-441706912
[x] @kubernetes/sig-cli-pr-reviews - kube-apiserver/kubectl skew - https://github.com/kubernetes/website/pull/11060#pullrequestreview-176870197
[x] @kubernetes/sig-api-machinery-pr-reviews - kube-apiserver/kube-controller-manager skew - https://github.com/kubernetes/website/pull/11060#issuecomment-440428941
[x] @kubernetes/sig-cloud-provider - for kube-apiserver/cloud-controller-manager skew - https://github.com/kubernetes/website/pull/11060#discussion_r235075963

assigning representatives from the various tagged sigs/components. please review or nominate an alternate.
/assign @justaugustus
representing sig-release
/assign @bgrant0607 @smarterclayton
representing sig-architecture
/assign @thockin
for kube-proxy upgrade order question
/assign @soltysh
for kubectl
/assign @lavalamp
for kube-apiserver / kube-controller-manager
/assign @derekwaynecarr
for kubelet

/assign @timstclair
representing cluster-lifecycle

/assign @timothysc
representing cluster-lifecycle

/unassign @timstclair

(for more SIG Release eyes)
/assign @calebamiles @tpepper

/sig release

This document is excellent, thanks @liggitt !

should we add requirements to be at latest patch version of 1.x prior to upgrades, and upgrade to latest patch version of 1.x+1

IMO, ideally we should aim for seamless 1.x.y -> 1.x+1.z upgrades, where y and z are any patch version.
having a upgrade path of first upgrading from 1.x.y -> to 1.x.latest and then to 1.x+1.0, might not be necessary, because 1.x+1.0 can include temporary code anticipating any upgrade issues. such stubs can them be removed in 1.x+2.0.

ideally we should aim for seamless 1.x.y -> 1.x+1.z upgrades, where y and z are any patch version.

We must actually test everything we say we support, and claiming support for upgrading from every 1.x.y patch release to every 1.x+1.z patch release substantially increases the test matrix (upgrade tests today test latest 1.x.y to latest 1.x+1.z).
It's also unclear how we would fix an upgrade bug discovered in a particular y/z combination post-release. Anything we did to release a fix for either 1.x.y or 1.x+1.z would generate a new patch version and leave that y/z pair with the bug.

1.x+1.0 can include temporary code anticipating any upgrade issues. such stubs can them be removed in 1.x+2.0.

the implications of that approach for downgrade are significant. There have been bugs or issues found during upgrade testing that were resolved in the last 1.x.y release prior to shipping 1.x+1.0. having those bugs fixed in a patch release gives a more stable downgrade target if required.

Thanks @liggitt, kubectl pieces lgtm

I'm curious about the comments around downgrade.  My impression today is that we do not actually have anybody giving meaningful support for downgrade.  There's a very narrow use case where we have some test coverage.  It breaks regularly and there isn't an owner for the test.  I can't find people who actually use or genuinely want it.  At best we keep saying "that's Google" in SIG Release, the release teams, and SIG Cluster Lifecycle when we bump into downgrade issues, but at KubeCon last week in discussion with Chao Xu @caesarxuchao I got the distinct impression that actually this is not something Google does today and he was talking about looking in 2019 at making it functional...ie: adding meaningful support for downgrade.
As it stands the PR mentions upgrade, the skew document starts out somewhat generic in terms of skew direction, and then focuses on upgrade.
Is downgrade supported today?  If so, the document should cover it explicitly.
That said, I really prefer the engineering simplifications that come with saying "no" to allowing downgrade, but even if we say we only support forward moves, we also don't have sufficient tooling to make it easy for operators to validate forward moves ahead of attempting them or make it safe and easy to discard such attempts (ie: no manually editing etcd content to amend the mistakes).  In my experience it's dramatically easier to implement those improvements in a forward-only scheme, versus also trying to support downgrades.

/sig pm

minor comments, lgtm

@spiffxp found this:  https://github.com/kubernetes/community/blob/b3349d5b1354df814b67bbdee6890477f3c250cb/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew

@spiffxp found this: https://github.com/kubernetes/community/blob/b3349d5b1354df814b67bbdee6890477f3c250cb/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew

I think that's the same as what I included in the references section in the description

I think that's the same as what I included in the references section in the description

Yes, it is.  Haven't reviewed this yet but huge thanks for putting it together.  The canonical version of this info does not belong in a dir called "design proposals"

@liggitt I see a few comments that still need to be addressed or dismissed, yes? Also looks as though this targets the 1.13 release. Which option would you prefer?

rebase on dev-1.13 branch to get into release
wait to merge until after release

If you'd just as soon wait until after release, could you please tag with a hold?
Thanks!

/hold
it doesn't target 1.13 specifically. it is still being discussed over the next week or so

+1 to everything.  FWIW - this is pretty much SOP for kubeadm and spelled out indirectly in all the docs, but I also think having an explicit policy is also good.

This looks great.  Something I might add to open questions is transitive / third-party dependencies:

are they completely out of scope?
is there a recommended or supported order for upgrading etcd vs. the control plane components?
when we say we recommend container engine A at version B for k8s release 1.n, does that imply we expect k8s release 1.n+2 to support the same?

@liggitt merging shortly after 1.13 sounds good. Do you mind if I remove this from the 1.13 milestone to help with my tracking of 1.13 PRs?

Not at all

Thanks. My issues were resolved. Looks nice rendered, too.
/lgtm
/approve
/hold cancel

/lgtm

/assign @mistyhacks

/assign mistyhacks

/unassign @timothysc
github only allows a max of 10 assignees per issue/pr, so I'm kicking off someone who already gave a +1 to make room for @mistyhacks

/assign @mistyhacks

/approve
I already did a review pass earlier, and we can iterate.

noting this looked good for sig-node

/wg lts


FileOpenPicker.PickSingleFileAsync() Causes a crash when app is started from an elevated context/tarted as Adminitrator

Describe the bug
When a WIN UI 3 app is configured to start with elevated privileges by adding the allowElevation capability and setting the requestedExecutionLevel to requireAdministrator; invoking  FileOpenPicker.PickSingleFileAsync() causes the application to crash (note: this is irrespective of IDE as it also crashes when I run outside of Visual Studio). On further investigation wrapping  FileOpenPicker.PickSingleFileAsync() and logging the exception to a file gives the following error:

Error HRESULT E_FAIL has been returned from a call to a COM component.
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.

Checking the Event viewer logs shows:

Faulting module name: CoreMessagingXP.dll, version: 10.0.22621.1003, time stamp: 0xc93a5eeb
Exception code: 0xc000027b
Fault offset: 0x0000000000090e1c

Steps to reproduce the bug
Go to your application's Package.appxmanifest and add the capabilities:
<Capabilities>
    <rescap:Capability Name="runFullTrust" />
	<rescap:Capability Name="allowElevation"/>
  </Capabilities>

Go to the application's app.manifest and modify as follows:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
	<security>
		<requestedPrivileges>
			<requestedExecutionLevel level="requireAdministrator"/>
		</requestedPrivileges>
	</security>
  </trustInfo>

Ensure your application has a button that triggers a FileOpenDialog. See sample below:
FileOpenPicker open = new FileOpenPicker();
InitializeWithWindow.Initialize(open, MainWindowPtr); //MainWindowPtr is the pointer to the main window of the app (i.e. parent of the current page that extends Window). This line attaches the dialog to the window of your app.
open.SuggestedStartLocation = PickerLocationId.ComputerFolder;
open.FileTypeFilter.Add(".exe");
StorageFile file = await open.PickSingleFileAsync();

Note that the app crashes/throws a COM exception
Expected behavior
It should pop up the select file/folder dialog even when the app is started with administrator privileges
Screenshots
No response
NuGet package version
1.1.2
Packaging type
Packaged (MSIX)
Windows version
Insider Build (xxxxx)
IDE
Visual Studio 2022
Additional context
No response

This is a duplicate of https://github.com/microsoft/WindowsAppSDK/issues/2504 so we'll continue to track there.


Runpod on Google Colab : it used up my google disk space.

1.Followed the instruction on this blog : https://blog.runpod.io/how-to-connect-google-colab-to-runpod/ .
2.Connected to Jupyter Notebook.
3. How do we create an  SSH tunnel with port forwarding. Where are we supposed to create it? is it on local cmd, jupyter terminal, a different app altogether.
4. How do I connect my runpod to Google colab so that it stops eating my Google drive disk space. Even after paying you almost $4/hr to run my LLM models.

You might be looking for the following: https://blog.runpod.io/how-to-achieve-true-ssh-on-runpod/
I am also closing out this issue as it us unrelated with this repo, for more general RunPod questions and support please reach out using one of the methods here: https://www.runpod.io/contact


vim/keymap.lua:0: E31: No such mapping

https://github.com/wbthomason/packer.nvim/issues/1039
Error detected while processing CursorHold Autocommands for "*":
E5108: Error executing lua ...vim/site/pack/packer/opt/packer.nvim/lua/packer/load.lua:165: Vim(echomsg):E114: Missing quote: "Error in packer_compiled: ...vim/
site/pack/packer/opt/packer.nvim/lua/packer/load.lua:155: Vim(append):Error executing lua callback: /usr/share/nvim/runtime/filetype.lua:20: Vim(append):Error e
xecuting lua callback: vim/keymap.lua:0: E31: No such mapping
stack traceback:
        [C]: in function 'cmd'
        ...vim/site/pack/packer/opt/packer.nvim/lua/packer/load.lua:165: in function <...vim/site/pack/packer/opt/packer.nvim/lua/packer/load.lua:161>
        [string ":lua"]:1: in main chunk

This started happening after the commit 0a0ea5e.
If the config_queries variable is placed back where it was, the problem goes away.

Did the merged PR solve the issue?


Implement openintents PICK_COLOR action

Using your camera to pick a color is a great capability that could be utilized by other apps. The pull request https://github.com/tvbarthel/CameraColorPicker/pull/32 is one way to do that implementation that does not get in the way of the existing behavior of CameraColorPicker. Should that be merged in, or is there a better solution?

Thanks again @travisfw
I have just merged your PR #32  =)


Key alphabet: Remove unusual characters

This fixes #19.
I'm keeping -, . and _ since they are very common characters in URLs.

OK, PR is ready to merge.

I'd remove all the special characters. . sometimes gets interpreted as the end of a sentence in chats. It really doesn't matter that much and I think it will be much nicer to have pure alpha-num urls.

OK, tested and works on my server.

Thanks!


Technical difficulty

Hey there. I was having a bit of a struggle with the process of getting all the things done. I downloaded node.js the latest, I went to use my terminal and put npm install -g create-react-app
Installed it and then I named it my-app but it shows that I has 0 vulnerability. I followed all the instructions as is and nothing. I uninstalled it and reinstalled everything and still nothing. I need help please!

Please try following the instructions at https://create-react-app.dev/docs/getting-started#quick-start. It looks like you're using outdated instructions which is likely causing your issues.


Support on_schema_change feature on incremental model

Problem
Currently, dbt-athena does not support on_schema_change option.
Solution

Add custom column class AthenaColumn

Athena has different column type between DML and DDL (e.g. integer)

https://docs.aws.amazon.com/athena/latest/ug/data-types.html

To avoid error on alter table statement because of difference of column type

Overwrite macro sync_column_schemas

Athena does not support drop columns statement, but replace columns

https://docs.aws.amazon.com/athena/latest/ug/alter-table-replace-columns.html

this causes inconsistency with original sync_column_schemas, so overwrite this macro on this adaptor

Note
Just cherry-pick the commit of these PRs(https://github.com/dbt-athena/dbt-athena/pull/3, https://github.com/dbt-athena/dbt-athena/pull/28)

By the way, dbt may be updated to add a comment about metadata of environment to query,
which causes error on DDL (not DML)
This is an example of this.
/* {"app": "dbt", "dbt_version": "1.3.0", "profile_name": "test", "target_name": "dev", "node_id": "model.foo.partitioned_model"} */

    alter table dbt_sandbox.partitioned_model
          replace columns (id int, additional_column_1 string, additional_column_2 varchar(3))

So, I'll check the way to avoid adding such a comment.

https://github.com/dbt-athena/dbt-athena/pull/30#issuecomment-1321163344
The above is resolved by ee0e69c

Thank you for your quick reviewing!


error TS2321: Excessive stack depth comparing types 'MongoRepository' and 'Repository'. node_modules/typeorm/repository/MongoRepository.d.ts(12,22): error TS2589: Type instantiation is excessively deep and possibly infinite. node_modules/typeorm/repository/MongoRepository.d.ts(45,5): error TS2321: Excessive stack depth comparing types '(optionsOrConditions?: string | number | Date | ObjectID | FindOneOptions | Partial, maybeOptions?: FindOneOptions) => Promise' and '{ (id?: string | number | Date | ObjectID, options?: FindOneOptions): Promise; (options?: FindOneOptions): Promise; (conditions?: FindConditions, options?: FindOneOptions<...>): Promise<...>; }'.

TypeScript Version:  3.5.3
Installed above typescript version. Work on local environment.
When we ran docker command to build project it throws above exception.
Guide us to resolve this issue ASAP.

This issue is quite similar to #29112
I have tried the solutions mentioned in this...still it did not worked for me.

Following solution solved this issue for time being:
Added typescript as a global dependency.
For this added following commands inside docker-file.
RUN npm i -g<EMAIL_ADDRESS>RUN npm i -D<EMAIL_ADDRESS>

Worked for me too.
RUN npm i -g<EMAIL_ADDRESS>RUN npm i -D<EMAIL_ADDRESS>


Implement filtering

Allow sub-queues to be derived, and implement common filtering.

Not considering this for v3 for now.


Fix issues in  wallet api

Description
Provide a clear and concise description of the changes made in this pull request.
Fixes #592 #593
Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[x] I have performed a self-review of my code
[ ] If it is a core feature, I have added thorough tests
[ ] Do we need to implement analytics?
[ ] Will this be part of a product update? If yes, please write one phrase about this update.
[x] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

I was testing the #592.
First run is ok.

The second run doesn't return the SQLITE_CONSTRAINT_PRIMARYKEY anymore. Great.

However, it still returns 500 and, according to the RFC9110, this return code is for "unexpected conditions" which I'm sure it's the case.

The 500 (Internal Server Error) status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

It's totally predictable that the user, intentionally or not, try to create duplicated DIDs.
As such, I think that, maybe, and error 409 or even a generic 400 might be more suitable for this situation.
Let's make the web more semantic :-)

And I want to take advantage of ticket #593 to register another possible improvement that we can make in the future in our APIs: HATEOAS


Bearby provider always detected

That code: const allProviders = await providers(true, 10000); always detects Bearby provider even if Bearby extension isn't installed. It might be because we detect Bearby by checking if bearby object is injected in the window. That object seems to always be injected by some bearby library, and not the extension

Done here https://github.com/massalabs/wallet-provider/pull/198


Cannot install VMware Harbor 0.3.5 anymore

I am trying to install a new instance of VMware 0.3.5 to test the upgrade procedure before I do the real production upgrade. After I installed VMware 0.3.5 from source, I noticed that the site design is completely broken and even login text box is not showing. Its always downloading 0.5.0 docker images.  See the attached screenshot of the web UI.
Any idea, how can I fix it or it's not possible to install VMware 0.3.5 anymore?
Docker version: 1.12.3
Docker compose: 1.9.0

looks like a issue of cached page? @wknet123
@biolounge could you please try to clean the history of your browser and refresh?

what did you mean by downloading images of 0.5.0? Did you build 0.3.5 from source?

@reasonerjt: Indeed. It was a caching issue.


can you open source your evaluation code?

hi,  great work!
in your paper you mentioned that you use solvers  to generate poses from a minimal set of 3 features (3 points, 2 points and 1 line, 1 point and 2 lines, or 3 lines), then combine them in a hybrid RANSAC to recover the query camera poses.
hope that you open source these lines of code. thanks.

Hi, we will probably release the evaluation code together with the training one.
But for what you are looking for, we used this repo to extract a homography from the combinations of 3 points/lines: https://github.com/rpautrat/homography_est/.
Then you can use the Opencv  decomposeHomographyMat to recover possible camera poses, given known intrinsics.

Ah sorry, I misunderstood your question indeed. What I described is how to get the relative pose from line matches.
I think you linked twice the same repo, so not sure what is the other repo you wanted to mention.
But for the visual localization part (absolute pose), the solvers we used came from https://github.com/vlarsson/PoseLib, and the evaluation code from here: https://github.com/cvg/limap (the Readme has explanations on how to use the visual localization part).

@rpautrat sorry about link of same repo,
I am wondering that the repo is for homographt estimate, ehich seems specialize in planar case, what if the rotation + translation case?
I mean two image, I detect lots of points, lines, they sure cannot lie on one plane, can this repo https://github.com/rpautrat/homography_est/  calculate relative pose(rotation and translation)?

In the paper, we use the relative pose estimation as a proxy to evaluate homography estimation. This is not aiming to solve relative pose in general. Lines-only correspondences are anyway not enough to solve relative pose estimation, they do not offer enough constraints.
So to sum up, if you want to achieve the best results for relative pose estimation, you should use the classical point matching + essential matrix 5-point RANSAC. In the paper, the relative pose evaluation was an indirect method to evaluate the quality of the homographies.

thanks


Move constants to params

Summary
We have a couple of hard coded values that could be moved into params so that we can update them without deployment.
An incomplete list:

max contract size
gas multiplier
instance cost
compile cost
...

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Great ideas. Use the current constants as defaults and allow governance to adjust it.

Note: I will have to implement https://github.com/CosmWasm/go-cosmwasm/issues/122 before it is safe to change GasMultiplier. Let's wait on this until I update go-cosmwasm

We have closed the PR and postpone this feature

This is related to #809
We need some of these values in the stateless ValidateBasic functions. That will make usage of Params impossible.
As a first step, I would propose pulling them into module-level var rather than const.
Projects importing x/wasm could then customize them either by runtime flags or by setting them explicitly in their custom app.go or cmd/*/main.go

Closing this now as this was done with the gas register. MaxLabelSize, MaxWasmSize, MaxProposalWasmSize are vars in types/validation.go


Port track1 export/ functionality to track2

The exporter functionality is in this folder
https://github.com/microsoft/opentelemetry-azure-monitor-python/tree/master/azure_monitor/src/azure_monitor/export
transmit <=> track
https://github.com/microsoft/opentelemetry-azure-monitor-python/blob/master/azure_monitor/src/azure_monitor/export/__init__.py#L108

completed

completed


.Net: Agents - plugins with a boolean parameter is resulting in an exception

One of the functions in a plugin has a bool parameter. This works fine with regular function calling. However, including this functions as a plugin for agent is resulting in the following error:
Exception: Response status code does not indicate success: 400 (Bad Request).
{
"error": {
"message": "Invalid schema for function 'MappingSkills-applyStyleSymbology': 'Boolean' is not valid under any of the given schemas.",
"type": "invalid_request_error",
"param": "tools[3].function.parameters",
"code": "invalid_function_parameters"
}
}
Am using version 1.6.2

hi, i can confirm the same error using an agent and a simple kernel function with a boolean input parameter. Is there any link or documentation for the Agents package? thanks in advance

Boolean is understood as a type by OpenAI.
https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section-4.2.1
Correct that this isn't agent specific.

@deepinderdeol, is this an issue with native functions? Are you able to share what the signature looks like? Sounds like we need change booleans into enums or something.

@deepinderdeol  Is this still an issue?

@markwallace-microsoft I will try again and let you know


Set negative button and positive button text all caps false

If we would like to set button to all caps true, we can create a new string resources with full caps text so this allows developers to be more flexible on customizing negative and positive button text

Refer to the Material Design guideline. Text button should be all-capitalized by design. So I added the setButtonTextAllCaps(isAllCaps: Boolean) as builder option.
SnapTimePickerDialog.Builder().apply {
    /* ... */
    setButtonTextAllCaps(false)
}
.build()
.show(supportFragmentManager, SnapTimePickerDialog.TAG)

Oh.. I must have skipped that.
Thanks a lot for the info. 😊

@adrianhartanto004 I just released the version 1.0.2. It will available for you in few hour


Add the tuple_pack_element_addr SIL instruction

This allows dynamically indexing into tuples.  IRGen not yet implemented.
I think I'm going to need a type_refine_addr instruction in order to handle substitutions into the operand type that eliminate the outer layer of tuple-ness.  Gonna handle that in a follow-up commit.

@swift-ci Please test


Show error message

I just tried to play around with the github graphql api and forgot to enter my token. It only said "Server Error", I had to check the console logs to see what was wrong.

@AndreasGassmann Hmmm.. what error should it have returned?

Github returns an error message, but I don't know about other GraphQL endpoints. This is the error you get:
{
  "message": "This endpoint requires you to be authenticated.",
  "documentation_url": "https://developer.github.com/v3/#authentication"
}

In the GraphiQL client for mac it just shows that error response. It's not really important, it's just the first thing I noticed when trying it out. But I really like the look and feel of altair, so if I ever work with GraphQL I'm sure I'll use it :).

@AndreasGassmann Thanks for your feedback! I'll be sure to fix that ASAP.

Nice!
As a more general question, what is your "goal" with this project? It would be nice to have something like "Postman for GraphQL", but obviously that would require quite a lot of work. I'm just curious what your plans are.

@AndreasGassmann That is the ultimate goal for it. For now, the use case has just been for making simple graphQL queries.


New version: Gen v0.4.0

Registering package: Gen
Repository: https://github.com/probcomp/Gen.jl
Created by: @marcoct
Version: v0.4.0
Commit: c37f5ca7556ae3c8b78b69871971d3fccdb28170
Reviewed by: @marcoct
Reference: https://github.com/probcomp/Gen.jl/commit/c37f5ca7556ae3c8b78b69871971d3fccdb28170#commitcomment-45639996

I am fixing this.

I am fixing this.


discord/embedded-app-sdk/releases/tag/v1.4.2

b915ebf06620b0af758aeeed51a312bde7c42e74

b915ebf06620b0af758aeeed51a312bde7c42e74


Add note to docs about using private registry with VirtualBox driver

See: https://github.com/docker/machine/issues/1717#issuecomment-136757551
Thx to @shepmaster for pointing out a solution
e.g.:
$ docker-machine ssh default sudo mkdir /var/lib/boot2docker/certs
$ docker-machine scp my-private-ca.pem default:/var/lib/boot2docker/certs
$ docker-machine ssh default sudo /etc/init.d/docker restart

FYI, the second line
docker-machine scp my-private-ca.pem default:/var/lib/boot2docker/certs

Won't work as written due to permissions —y ou need to be root to put the cert into /var/lib/boot2docker/certs, but the scp user is not root. The original (longer) version copies the file in and then moves it as root.

The documentation for [using a selft-signed certificates] (https://docs.docker.com/registry/insecure/#using-self-signed-certificates) for docker registry state that you are ending up with two files: domain.crt and domain.key.
I read this thread and also the boot2docker doc section about Installing secure Registry certificates and both mention  the usage of a .pem file.
How do you obtain or generate the .pem file?

@cesarhernandezgt pem files can be generated from crt/key files: http://stackoverflow.com/questions/4691699/how-to-convert-crt-to-pem


How do I specify what element/div-id the chart should use?

Most plugins export a function which takes in two parameters - props and element. I'm writing my own plugin currently, and it's successfully passing the props parameter, but it's failing to pass an element parameter, instead passing { }.
Where do I specify the DOM element the chart should be contained inside?
To give you an example of what I mean, here is the beginning of the ForceDirected plugin:
function ForceDirected(element, props) {
  const { data, width, height, linkLength = 200, charge = -500 } = props;
  const div = d3.select(element);
  div.classed('superset-legacy-chart-force-directed', true);

At what point/where in the codebase is the element parameter passed?

Figured it out. Essentially, at no point do you explicitly specify the element parameter. However, you need to make sure you follow the format of other plugins and have a React[plugin].js file in the directory of your plugin folder, and make sure index.js points to it as well.


[Bug]: Contacts backup fails with a nested Contacts folder

What happened?
Failures from local tests:
--- FAIL: TestDataCollectionIntgSuite (11.28s)
    tester.go:39: TestDataCollectionIntgSuite run at 2023-05-30T23:59:41.266977Z
    --- FAIL: TestDataCollectionIntgSuite/TestExchangeDataCollection (11.28s)
        tester.go:39: TestDataCollectionIntgSuite/TestExchangeDataCollection run at 2023-05-30T23:59:41.267267Z
        --- FAIL: TestDataCollectionIntgSuite/TestExchangeDataCollection/Contacts-delta (2.39s)
            tester.go:39: TestDataCollectionIntgSuite/TestExchangeDataCollection/Contacts-delta run at 2023-05-30T23:59:48.193331Z
            data_collections_test.go:137:
                	Error Trace:	~/go/src/github.com/alcionai/corso/src/internal/connector/data_collections_test.go:137
                	            				/Users/keepers/go/pkg/mod/github.com/stretchr/testify@v1.8.3/suite/suite.go:112
                	Error:      	"3" is not greater than or equal to "4"
                	Test:       	TestDataCollectionIntgSuite/TestExchangeDataCollection/Contacts-delta
                	Messages:   	expected 1 <= num collections <= 3
            data_collections_test.go:149: Action: Backup performed on 4 of 4 objects (4.4 kB) within 3 directories.  Downloaded from  some_m365_id, some_m365_id/some_m365_id, ,
        --- FAIL: TestDataCollectionIntgSuite/TestExchangeDataCollection/Contacts-non-delta (1.96s)
            tester.go:39: TestDataCollectionIntgSuite/TestExchangeDataCollection/Contacts-non-delta run at 2023-05-30T23:59:50.58146Z
            data_collections_test.go:137:
                	Error Trace:	/Users/keepers/go/src/github.com/alcionai/corso/src/internal/connector/data_collections_test.go:137
                	            				~/go/pkg/mod/github.com/stretchr/testify@v1.8.3/suite/suite.go:112
                	Error:      	"3" is not greater than or equal to "4"
                	Test:       	TestDataCollectionIntgSuite/TestExchangeDataCollection/Contacts-non-delta
                	Messages:   	expected 1 <= num collections <= 3
            data_collections_test.go:149: Action: Backup performed on 4 of 4 objects (3.3 kB) within 3 directories.  Downloaded from  some_m365_id, some_m365_id/some_m365_id, ,

Corso Version?
Corso v0.8.0
Where are you running Corso?
any
Relevant log output
No response

Creating nested contact folders only available via Graph API. Corso users will not hit this.


Fix transifex resources

It is missing the "master" branch, which is now "main".

Hi @cemrich @comradekingu did the (possible) weblate integration happen. If not I'd be very grateful if you had the time to long into this anytime soon.

I am on it. Asked bubu. Will otherwise go with Hosted Weblate.

The instance at https://weblate.bubu1.eu is open for signup for new projects. Whoever creates a project is automatically an admin for it and should be able to add other project admins. Let me know if something doesn't work.

The problem was on my side. My brain works now.
https://weblate.bubu1.eu/projects/zapp/
Targeting "develop" for PRs.

@eUgEntOptIc44
So the -en one is selected as en_UK, but those are German strings in there.
Can't change the base language, so I am going to have to set it up again.
Before I get into another problem, why are there two resources that are seemingly English?

@comradekingu first of all thank you for quick reaction to my message. 👍
Tbh I didn't noticed the strings.xml in values/ being German not English. Sorry my fault ... I might have better had a second read through the source code.
To my personal understanding this seems to be only show blocker right now. Am I right? @comradekingu would love to hear your feedback on this as your far more experienced with weblate than myself.
I tried to apply the feedback by @comradekingu in PR #323. Would be great if @cemrich could or anyone else reading this give me some feedback on this. Please be aware that my knowledge of kotlin and development for android is quite limited.
While do so I stumbled across donottranslate.xml and tried to match this against strings.xml but didn't get anywhere.

@eUgEntOptIc44
Looks good. I wasn't actually in "reviewers" for that PR. Sorry to have missed whatever other messages I may have overlooked.
:)

Thank you very, very much for your effords!
I will not be able to look into this for the next few days, but I can clarify a few things:

donottranslate.xml are configuration strings that should not be translated.
The base language should be German - this does make sense, since most of the apps content is German anyway. The second language should be American English.

I'll let you know as soon as I have some spare time.

Well first of all thanks for looking into this. I really love the app and I'm happy to help.

donottranslate.xml are configuration strings that should not be translated.

Thanks for clarification. 👍

The base language should be German - this does make sense, since most of the apps content is German anyway. The second language should be American English.

To me personally this looks like a misunderstanding. I set English as the default so that I would work as a fallback. Take the following use case: an user locating within the boundaries of the geo-blocking (so likely Germany or France) using a device with a French, Italian, Turkish, Ukrainian ... or other not German or English locale is using the app. They would still see the English locale instead of the German.
Especially for learning German and receiving trustworthy informations by watching German TV channels the app proves very useful. To cut it short I'd ease the bar.

I set it up on https://hosted.weblate.org/projects/zapp/#information instead, since bubu WL is moving over to the Codeberg WL.
@eUgEntOptIc44
I didn't quite understand that, but the user decides on the language, and after Android  9(?) multiple languages can be selected in Android, for fallback.
In Android 13, there is per app management of languages from Android.

@eUgEntOptIc44 I commented your PR
Multiple locales can be selected since Android 7.0 (https://developer.android.com/guide/topics/resources/multilingual-support).
Per app language support is available with Android 13 (https://developer.android.com/guide/topics/resources/app-languages). But I have to enable that explicitly. I've created a new issue for that: https://github.com/mediathekview/zapp/issues/327

@eUgEntOptIc44 Seems to work now.
Add https://docs.weblate.org/en/latest/admin/continuous.html#github-setup and possibly
https://github.com/weblate to the org, and
https://github.com/marketplace/actions/weblate-locale-linter

Just needs #329 now.

@comradekingu If you could add me (@ccoenen) as admin, that would be nice.

Okay, I am still unsure about the default locale.
If I were a spanish or turkish user and my preferred languages are not supported in Zapp - what fallback language would I expect?

English, because the likelihood of me understanding even little bits and pieces is higher
German, because all other content (video language, show information, etc.) is served in German


feat: custom SEL events metrics

Added a new collector to collect custom metrics from SEL events via IPMI.
In config metrics are defined in this format:
modules:
  default:
    collectors:
      ...
      - sel-events
    sel_events:
      - name: correctable_memory_error
        regex: Correctable memory error.*

Metrics are shown as:
# HELP ipmi_sel_entries_count Current number of custom log entries in the SEL.
# TYPE ipmi_sel_entries_count gauge
ipmi_sel_events_count{name="correctable_memory_error"} 5
# HELP ipmi_sel_entries_latest_timestamp Latest timestamp of custom log entries in the SEL.
# TYPE ipmi_sel_entries_latest_timestamp counter
ipmi_sel_events_latest_timestamp{name="correctable_memory_error"} 1.703613275e+09

Closes #41

@bitfehler @SuperQ
Hello! Can you please review my PR

Thanks a lot. For the record, I think we might be handing folks a decent foot-gun here, but hey :slightly_smiling_face:


[ci skip] [cf admin skip] NO_CI adding bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I've added bot automerge as instructed in #2.
Merge this PR to enable bot automerging.
Fixes #2

@conda-forge/bot the [ci skip] didn't actually skip the CI.

That only works on master for azure. This can be merged without issue.


Disable Filters Input Textbox

Report type 3
Is there some way to delete some filter input? I want to filter only by specific columns.
Thanks in advance!
Lucas

http://js-grid.com/docs/#fields

Set filtering: false for fields not participating in filtering.

filtering: false, is not working for a text type field. It is working only for select type field. #tabalinas please suggest..


Gmail no notifications

Please search to check for an existing issue (including closed issues, for which the fix may not have yet been released) before opening a new issue: https://github.com/k9mail/k-9/issues?q=is%3Aissue
Expected behavior
New mail comes: Pop up with Email (+ preview)
Actual behavior
New mail comes: No notification, no sound, nothing. (It does receive Mails though, just no notification.)
Steps to reproduce

Add Gmail account, standard settings, nothing special.
Receive Mail.
Don't get notifications, yet the Mail arrives on the device.

Environment
K-9 Mail version: 5.600
Android version: 9
Account type (IMAP, POP3, WebDAV/Exchange):
IMAP (at least I think so)
Please take some time to retrieve logs and attach them here:

This is most likely a configuration issue of notifications on your device, not a bug in K-9 Mail.
Please use the mailing list to ask for help.


Refactor Unnest::generateOutput method

Unnest::generateOutput had become a very long method. This refactoring splits the generation of repeated columns, unnest encoding and ordinality column to individual methods.

@mbasmanova : Thanks for your review. Have addressed the comments. PTAL.

@aditi-pandit Seeing linter warning:

@aditi-pandit Seeing linter warning:

@mbasmanova : Thanks.
Have fixed the linter warning. The macos build failure was on account of that warning as well.


Treemap -SVG - long text labels and more lables in a block overlaps on another block  and labels.

Version
4.3.0
Reproduction link
https://jsfiddle.net/hemantss/jx6zwf7y/
Steps to reproduce

Create treemap with svg with long text in labels.
The output is displayed correctly. But long text labels in treemap blocks go out of blocks  Or overlap on another block.

What is expected?
It should not overlap on other blocks.
What is actually happening?
Text labels in treemap block go out of block  Or overlap on another block.

I have created issue for same problem. Treemap- SVG -Labels not fit in treemap blocks #10732.
I have tried with new version but same issue is reproduced.
Can you please share working demo with new version?
https://github.com/apache/incubator-echarts/issues/10732

Duplicate of #10732. Please follow that original issue.


Add OIDCCacheShmEntrySizeMax parameter

Fixes https://github.com/ManageIQ/manageiq/issues/20511
This PR helps to ensure OIDC Cache is not undersized for most installations by increasing OIDCCacheShmEntrySizeMax from the default of 16913 bytes to 65536.

@miq-bot add_label bug
@miq-bot add_label authentication
@miq-bot assign @abellotti

@abellotti Please take a look. Thank you! JoeV


Plan for update the examples for fluxible 0.4.x?

i edited the following in "package.json":
"fluxible": "^0.4.0",

and continued as described in README.
However, i got the following error:
WARNING in ./~/fluxible/~/es6-promise/dist/es6-promise.js
Module not found: Error: Cannot resolve module 'vertx' in /Users/gilbertwong/dev/gh/flux-examples/node_modules/fluxible/node_modules/es6-promise/dist
 @ ./~/fluxible/~/es6-promise/dist/es6-promise.js 125:20-30
require('fluxible').FluxibleMixin has been moved out of the default exports for Fluxible. Please use require('fluxible/addons/FluxibleMixin') instead.
/Users/gilbertwong/dev/gh/flux-examples/node_modules/fluxible/addons/FluxibleMixin.js:88
            storeInstance = context.getStore(store);
                                    ^
TypeError: undefined is not a function
    at [object Object].FluxibleMixin.getStore (/Users/gilbertwong/dev/gh/flux-examples/node_modules/fluxible/addons/FluxibleMixin.js:88:37)
    at [object Object].getInitialState (/Users/gilbertwong/dev/gh/flux-examples/react-router/components/Timestamp.jsx:17:21)
    at new Constructor (/Users/gilbertwong/dev/gh/flux-examples/node_modules/react/lib/ReactClass.js:853:54)
    at [object Object].ReactCompositeComponentMixin.mountComponent (/Users/gilbertwong/dev/gh/flux-examples/node_modules/react/lib/ReactCompositeComponent.js:135:16)
    at [object Object].wrapper [as mountComponent] (/Users/gilbertwong/dev/gh/flux-examples/node_modules/react/lib/ReactPerf.js:70:21)
    at Object.ReactReconciler.mountComponent (/Users/gilbertwong/dev/gh/flux-examples/node_modules/react/lib/ReactReconciler.js:38:35)
    at ReactDOMComponent.ReactMultiChild.Mixin.mountChildren (/Users/gilbertwong/dev/gh/flux-examples/node_modules/react/lib/ReactMultiChild.js:192:44)
    at ReactDOMComponent.Mixin._createContentMarkup (/Users/gilbertwong/dev/gh/flux-examples/node_modules/react/lib/ReactDOMComponent.js:287:32)
    at ReactDOMComponent.Mixin.mountComponent (/Users/gilbertwong/dev/gh/flux-examples/node_modules/react/lib/ReactDOMComponent.js:197:12)
    at Object.ReactReconciler.mountComponent (/Users/gilbertwong/dev/gh/flux-examples/node_modules/react/lib/ReactReconciler.js:38:35)

The vertex warning is happening because of this.
They have a suggestion in that post, you can add the following to the webpack config in the meantime:
plugins: [
    new webpack.IgnorePlugin(/vertx/),
],

Yes, we have a PR open here that will upgrade Fluxible to 0.4.x among other things. We're hoping to merge in the next few days.

:+1:

Closing this in favor of the PR mentioned above.


How to convert Mat to Vec?

I have a 3 channel Mat that I want to convert to a Vec<u8>. I've tried a number of ways, but the result is always a malformed image. I'd be very happy to get some help here.

I would need some more details to really help, but it sounds like you are missing the step to convert a color image to a grayscale one: https://docs.rs/opencv/latest/opencv/imgproc/fn.cvt_color.html. Something like this should help:
let mut output = Mat::default();
imgproc::cvt_color(&input, &mut output, imgproc::COLOR_BGR2GRAY, 0))?;

Hi, thanks for answering. What I specifically need is to access the color image bytes to send as payload to S3.
To do that, I need to make a ByteStream out of the Mat. Here is the documentation for ByteStream: https://docs.rs/aws-sdk-s3/0.21.0/aws_sdk_s3/types/struct.ByteStream.html.
I don't know if that helps.

Btw, I was getting qt linking errors when using highgui on arch. I had to install qt6-base, just in case you want to update the readme (it says qt5-base currently). Using version 0.84.4.

Thanks for the heads-up, I'll update the readme! Can you share the specific code that you're using and explain in more detail what is going wrong with the image uploaded to S3?

Ok I think that the arguments to combine_images and mat_from_bytes are non-encoded bytes because I tried imshowing then and only get a black window. I guess I need to convert the raw
bytes into a Mat somehow then. Thank you for your replies!

For that you can actually use Mat::from_slice_rows_cols::()

Wait, I think I misread you, if you get black windows then it means that the bytes are actually non-raw (e.g. they are encoded).

Shouldn't I be able to see the picture then?

When doing this
fn mat_from_bytes(bytes: &[u8]) -> Mat {
    let mut mat = Mat::from_slice(bytes).unwrap();
    mat.set_dims(2);
    mat.set_flags(CV_8UC3);

    opencv::highgui::imshow("mat", &mat).unwrap();
    opencv::highgui::wait_key(0).unwrap();

    mat
}

I get the following error:
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Error { code: -2, message: "OpenCV(4.8.0) /usr/src/debug/opencv/opencv-4.8.0/modules/core/src/matrix.cpp:462: error: (-2:Unspecified error) in function 'cv::Mat::Mat(cv::Size, int, void*, size_t)'\n>  (expected: '_step >= minstep'), where\n>     '_step' is 4966829\n> must be greater than or equal to\n>     'minstep' is 14900487\n" }', src/imgproc.rs:90:42

I got it to work like this:
fn mat_from_bytes(bytes: &[u8]) -> Mat {
    let mat = Mat::from_slice(bytes).unwrap();
    let mat = imgcodecs::imdecode(&mat, imgcodecs::IMREAD_COLOR).unwrap();

    opencv::highgui::imshow("mat", &mat).unwrap();
    opencv::highgui::wait_key(0).unwrap();

    mat
}

Thanks to this SO post: https://stackoverflow.com/questions/13705578/convert-a-string-of-bytes-to-cvmat.
I think my problem is solved now. Thank you very much for the help!

It's great to hear that!


Pretrained checkpoint of girl's dataset

Hi,你好！请问一下有没有dataset中girl的预训练好的模型呢？
谢谢！

We already provided the pre-trained girl model. For your convenience, you can also download it using this link  https://portland-my.sharepoint.com/:u:/g/personal/cwang355-c_my_cityu_edu_hk/ESlWkpdiu0FOslTGiOulXP4Bn1Au2YWD9dMI41_AP5L3Nw?e=SfvauL


fix(providers): Sanitize nuts properties from configuration

Fix https://github.com/darkweak/souin/issues/215#issuecomment-1158633730

@mattvb91 can you try with the --with github.com/darkweak/souin/plugins/caddy@ c37739fb65697ca15d3c872491bf448ced8c2469 --with github.com/darkweak/souin@ c37739fb65697ca15d3c872491bf448ced8c2469 ?

@darkweak I can now see the keys succesfully purged from /__cache/souin/surrogate_keys however the pages are still cached and show up on the /__cache/souin list now

What's your configuration file ? That's really weird, the E2E tests are updated to ensure everything works as expected.

So the order is the following. Restart caddy and have an empty list on both /__cache/souin/surrogate_keys & /__cache/souin.
curl http://random-c9vwf2ke.localhost/first-product

This request goes to a nextjs container which will in turn call an upstream laravel API. So I end up with a frontend html response to cache and an API json response to cache:
/__cache/souin/surrogate_keys

{
"STALE_product-5f65fd28-bd1c-418e-b0df-2b63f45260df": ",GET-random-c9vwf2ke.localhost-/api/shop/get/first-product,STALE_GET-random-c9vwf2ke.localhost-/first-product{-VARY-}Accept-Encoding:",
"product-5f65fd28-bd1c-418e-b0df-2b63f45260df": ",GET-random-c9vwf2ke.localhost-/api/shop/get/first-product,GET-random-c9vwf2ke.localhost-/first-product{-VARY-}Accept-Encoding:"
}

/__cache/souin
[
"GET-random-c9vwf2ke.localhost-/first-product{-VARY-}Accept-Encoding:",
"STALE_GET-random-c9vwf2ke.localhost-/api/shop/get/first-product",
"GET-random-c9vwf2ke.localhost-/api/shop/get/first-product",
"STALE_GET-random-c9vwf2ke.localhost-/first-product{-VARY-}Accept-Encoding:"
]

Both the API and frontend responses have been tagged with the product-5f65fd28-bd1c-418e-b0df-2b63f45260df surrogate key as can be seen in the surrogate_keys response.
curl --location --request PURGE 'http://localhost/__cache/souin' \
--header 'Surrogate-Key: product-5f65fd28-bd1c-418e-b0df-2b63f45260df' \
--header 'Host: localhost'

Now the API still has a STALE_GET response
/__cache/souin
[
"STALE_GET-random-c9vwf2ke.localhost-/api/shop/get/first-product",
]

While the keys list is empty
/__cache/souin/surrogate_keys
{
}

And looking at it it may be caused by the {-VARY-}Accept-Encoding: getting appended to the requests which then ends up being a different key?
Config:
"cache":{
   "api":{
      "basepath":"/__cache",
      "souin":{
         "basepath":"/souin",
         "enable":true
      }
   },
   "cache_keys":{
      "/_next\\/static/":{
         "disable_host":true
      }
   },
   "cdn":{
      "dynamic":true,
      "strategy":"hard"
   },
   "distributed":true,
   "log_level":"debug",
   "nuts":{
      "path":"/tmp/nuts-souin"
   },
   "stale":"0s",
   "ttl":"3600s"
}

@mattvb91 I'm not able to reproduce so I'll try to fix that blindly. Can you try with the --with github.com/darkweak/souin/plugins/caddy@17c29c8107cf566a89931a114fdf1137f354336b --with github.com/darkweak/souin@17c29c8107cf566a89931a114fdf1137f354336b please?

No luck with that,
still gets stuck in the list:
/__cache/souin

"GET-random-c9vwf2ke.localhost-/first-product{-VARY-}Accept-Encoding:gzip, deflate, br",

and it doesnt get added back into the surrogate key list either at that point because im assuming the cache entry doesnt hold the surrogate-key header anymore (That used to get sent but has gone missing in one of the last releases) so at that point there is nothing to flush by surrogate key in in the list however its still serving that cache entry.
Is there any way to disable the {-VARY-}Accept-Encoding:gzip, deflate, br from going into the cache key?

In my tests I didn't set a cache key with a comma + space, that's why it works on my side, my bad

This commit should fix this bug.

Is there any way to disable the {-VARY-}Accept-Encoding:gzip, deflate, br from going into the cache key?
No, because if the vary is not part of the cache key, you'll probably serve a wrong response that depend on the headers (e.g. language)

Im afraid on that commit nothing even gets set on /__cache/souin/surrogate_keys anymore.
I will try to put together a minimum example repo to help out over the next few days as soon as I get time.

Sorry deleted my last comment from 1 minute ago, I had accidently disabled                     'distributed' => true, to test something else.
This looks like it is working correctly on initial glance!!! Clearing both my frontend & API responses now! This is great.

Is it really working ? 😅

Yup at least with requests that have 1 surrogate key per page.
I will test tomorow with list pages that will have multiple surrogate keys to check that it flushes list pages too but yea this definitely works nicely for individual pages now great stuff :+1:

So it looks like its 90% there. If I run my whole test suite including list pages that need to get flushed it fails when there is a large number of surrogate keys in the list.
However if I restart caddy to clear the cache and run the individual test that fails which results in only a small number of surrogate keys then the test passes.
So at the moment I cant even give a concrete example cause I need to dig a bit more to find out exactly whats happening but my initial suspicion is that once there is a large number of entries then theres some kind of corruption going on in the surrogate key list / cache entries and it isn't able to cleanly flush the specified resource.

@darkweak not sure if this is related just looking into if I can get a certain order at which it fails but why do I get different header responses when using curl vs what the browser receives?
curl --head http://adw-sdrubieu.localhost

HTTP/1.1 200 OK
Cache-Status: Souin; fwd=uri-miss
Content-Length: 17293
Content-Type: text/html; charset=utf-8
Date: Sun, 19 Jun 2022 12:06:06 GMT
Etag: "438d-J+ToNOLWBws9Qd0hwDPyuodqNLk"
Surrogate-Key: adw-sdrubieu.localhost, product-e077c673-4c4a-4856-b673-1c1b91e77dbf, category-74e2d799-cce4-4423-b52a-8141ae1333fc
Vary: Accept-Encoding

Same request on chrome dev tools:
http://adw-sdrubieu.localhost

HTTP/1.1 200 OK
Age: 208
Cache-Status: Souin; hit; ttl=3392
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Date: Sun, 19 Jun 2022 12:03:09 GMT
Etag: "438d-J+ToNOLWBws9Qd0hwDPyuodqNLk"
Vary: Accept-Encoding
Transfer-Encoding: chunked

Is that because it adds keys depending on request headers coming in from the browser?

The browser send a curl like curl --location --request GET '{YOUR_URL}' --head

Thanks! Im still a bit lost as to why im getting different results I feel like it should give me back the same cache entry I must be missing something obvious?
curl --head --location --request GET 'http://random-5a9k4ose.localhost/'

HTTP/1.1 200 OK
Cache-Status: Souin; fwd=uri-miss; stored
Content-Type: text/html; charset=utf-8
Date: Sun, 19 Jun 2022 14:04:33 GMT
Etag: "43bf-6bgCw8ERYf7UEoKH526rNffgVhY"
Surrogate-Key: random-5a9k4ose.localhost, product-cf9fa866-e38e-4a3a-8bf8-34d86d68c56a, category-e087fcfc-171e-4ba1-af2b-4c1db5986804
Vary: Accept-Encoding
Transfer-Encoding: chunked

Browser:
Request URL: http://random-5a9k4ose.localhost/

Age: 1137
Cache-Status: Souin; hit; ttl=2463
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Date: Sun, 19 Jun 2022 13:46:02 GMT
Etag: "43bf-6bgCw8ERYf7UEoKH526rNffgVhY"
Transfer-Encoding: chunked
Vary: Accept-Encoding

same etag but the content being served in both instances is actually old and hasnt been cleared.