add inplace_patch function

I am trying to patch a >100Mb JSON file and it turns out that the copying / destruction of JSON objects takes quite long.
Not allocating a new JSON for each patch helps a lot in terms of speed (>100x improvement).

Pull request checklist
Read the Contribution Guidelines for detailed information.

[x]  Changes are described in the pull request, or an existing issue is referenced.
[x]  The test suite compiles and runs without error.
[x]  Code coverage is 100%. Test cases can be added by editing the test suite.
[x]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header file single_include/nlohmann/json.hpp. The whole process is described here.

Please don't

The C++11 support varies between different compilers and versions. Please note the list of supported compilers. Some compilers like GCC 4.7 (and earlier), Clang 3.3 (and earlier), or Microsoft Visual Studio 13.0 and earlier are known not to work due to missing or incomplete C++11 support. Please refrain from proposing changes that work around these compiler's limitations with #ifdefs or other means.
Specifically, I am aware of compilation problems with Microsoft Visual Studio (there even is an issue label for these kind of bugs). I understand that even in 2016, complete C++11 support isn't there yet. But please also understand that I do not want to drop features or uglify the code just to make Microsoft's sub-standard compiler happy. The past has shown that there are ways to express the functionality such that the code compiles with the most recent MSVC - unfortunately, this is not the main objective of the project.
Please refrain from proposing changes that would break JSON conformance. If you propose a conformant extension of JSON to be supported by the library, please motivate this extension.
Please do not open pull requests that address multiple issues.

Coverage remained the same at 100.0% when pulling 590b3c6fc6d23290a17eea3eeedab6d2143f960c on wolfv:inplace_patch into d4daaa897f48bf7bb2f96b46b84e49f32dd11daf on nlohmann:develop.

A couple of things:

Please run make amalgamate (see Contribution Guidelines).
I think patch_inplace would be the better name, so it appears next to patch when sorted.
The documentation needs to be updated. I suggest you move docs/mkdocs/docs/api/basic_json/patch.md to patch_inplace.md and add a new patch.md, explaining patch() in terms of patch_inplace() and linking to patch_inplace.md for details. Example files need to be duplicated and adjusted.

(Separately, we should address the quite frequent failure of MinGW in CI. Can we rehost the MinGW package without violating the license?)

@falbrechtskirchinger thanks for the notes. What do you think about keeping docs in a single document? Otherwise there would be quite some duplication.
This really drastically improves the performance for our use case as copying and destroying a 100Mb json file is really slow (on the tune of ~1 second per patch, vs a couple nanoseconds without the copy).
I wonder if the destruction could be optimized in #3583

@falbrechtskirchinger thanks for the notes. What do you think about keeping docs in a single document? Otherwise there would be quite some duplication.

@wolfv I don't think there's precedent for similarly named functions being documented in one file and while I agree with you about the duplication, @nlohmann will probably want a dedicated patch_inplace.md file. Let's wait and see.
You're at least missing an entry in docs/mkdocs/mkdocs.yml.
- 'patch_inplace': api/basic_json/patch.md

Also, can you please prepare the examples in docs/examples and include them once a decision has been made as to where patch_inplace() should be documented?
Basically, copy patch.cpp -> patch_inplace.cpp and patch.output -> patch_inplace.output and modify patch_inplace.cpp:
    // output original document
    std::cout << std::setw(4) << doc << "\n\n";

    // apply the patch inplace
    doc.patch_inplace(patch);

    // output patched document
    std::court << std::setw(4) << doc << std::endl;

Did you run make amalgamate? You need to commit the generated single_include/nlohmann/json.hpp file as well.

@wolfv I don't think there's precedent for similarly named functions being documented in one file and while I agree with you about the duplication, @nlohmann will probably want a dedicated patch_inplace.md file. Let's wait and see.

Yes, please do so.

Thanks for the review! I applied your suggestions.

Note to me:

[ ] Add new documentation to mkdocs.

@nlohmann thanks for approving! Is the remaining task something I should do?

Thanks for your work!

@nlohmann thanks for approving! Is the remaining task something I should do?

It's basically checking that the new Markdown file is added to docs/mkdocs/docs/api/basic_json/index.md, docs/mkdocs/mkdocs.yml, and docs/docset/docSet.sql. I'll take care of it.


setting icon/button not working

Description

setting button is not working
Screenshots

Additional information
No response

On which page you're getting this issue? Please try to provide the proper details.

That is actually for the theme and the settings icon is for the system default theme while other two are for light and dark mode.

Nothing needs to be fixed here right?

oh my bad sorry


This is the perfect example to use http://ember-concurrency.com/


plugin: disable Go 1.8 plugin on non-amd64

Update https://github.com/docker/containerd/issues/563
Go 1.8 plugin does not work on some architectures such as arm64. (https://github.com/golang/go/issues/17138)
So I suggest enabling the plugin only on amd64 at the moment.
(rather, should we disable it even on amd64, maybe?)
e.g. Dockerfile for arm64
FROM dockcross/linux-arm64

RUN apt-get update && apt-get install -y btrfs-tools:arm64
RUN curl -fsSL "https://golang.org/dl/go1.8.linux-amd64.tar.gz" \
        | tar -xzC /usr/local
ENV PATH /go/bin:/usr/local/go/bin:$PATH
ENV GOPATH /go

COPY . /go/src/github.com/docker/containerd
WORKDIR /go/src/github.com/docker/containerd
RUN GOARCH=arm64 CGO_ENABLED=1 make

Compilation had been failing without this PR
Step 8/8 : RUN GOARCH=arm64 CGO_ENABLED=1 make
 ---> Running in bb3361fed154
🐳 bin/ctr
🐳 bin/containerd
# github.com/docker/containerd/cmd/containerd
/usr/local/go/pkg/tool/linux_amd64/link: running /usr/bin/aarch64-linux-gnu-gcc failed: exit status 1
/usr/lib/gcc/aarch64-linux-gnu/4.9/../../../../aarch64-linux-gnu/bin/ld.gold: internal error in global, at ../../gold/aarch64.cc:4973
collect2: error: ld returned 1 exit status

make: *** [bin/containerd] Error 2
Makefile:108: recipe for target 'bin/containerd' failed
The command '/bin/sh -c GOARCH=arm64 CGO_ENABLED=1 make' returned a non-zero code: 2

Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

seems reasonable for now given we aren't depending on actual plugin support for anything at this point, right?

LGTM


Adding code to run on Powersystem

Hi
Here is my contribution to your code, its working good on powersystems.
Thanks for the code, its working good.
What do these changes do?
Added Architecture "ppc64le"
Are there changes in behavior for the user?
No

@gerrith3 I told you to quit. Don't make me report you and your people to github for abuse.


WebOS 4 -  port 3000 is closed

I can’t connect to my LG tv.
Scanning the opened ports, it seems that the 3000 is closed,
And there is no open port for the WebSocket

i have sam proplem like that, my Scanning open port
1085/tcp  open  upnp    LG WebOS upnpd (WebOS 1.5; UPnP 1.0)
1090/tcp  open  upnp    Platinum unpnd <IP_ADDRESS> (arch: i686; UPnP 1.0; DLNADOC 1.50)
7000/tcp  open  rtsp    AirTunes rtspd 377.25.06
9080/tcp  open  http    Mongoose httpd
11111/tcp open  vce?
is there any way to conncet my lg tv ?


Angular version policy?

We've been using Covalent for over 3 years in production and are very thankful for it and the community contributors. We try to stay on top of updating dependencies and look forward to new features available in Angular 10 and the latest version of TypeScript, but we don't upgrade until a release version Covalent supports the new Angular version. It's been 3 months since Angular v10 was released and not clear from https://github.com/Teradata/covalent/issues/1774 what the target/expectation should be. Obviously support for upgrades sooner rather than later is desirable, but communication to help guide our roadmap would be the most helpful. Is there a policy/target for when new Angular versions will be supported following a major Angular release?
It would also be nice to have a clear documentation of what versions of Covalent support which version(s) of Angular.

Hi Craig,
PR PR 1808 bumping Covalent to Angular 10 is pending final sign off. Approval should be soon. If you'd like to pull the code and play with it, it would be appreciated.
Regards,
Tom

@thomaslennan that's good to know re: Angular 10.
Is there a target timeline/policy for keeping Covalent in version sync with Angular on a regular basis? How can we quickly and confidently identify which version(s) of Covalent are compatible with which version(s) of Angular?

@thomaslennan any update on policy or guidance when it comes to major Angular releases and versions of Covalent? Angular is already on RC 2 for version 11.
This impacts our ability to keep Angular up-to-date. This prevents us from taking advantage of the latest Angular features. This also has a downstream impact on other dependencies. We're not able to upgrade TypeScript and we can't count on other Angular libraries publishing updates for old versions of Angular.

Is there an actual issue when trying to use angular 10? as far as i know, covalent 3.X works with angular 10v.. ive been using projects with it so im not getting any issues.
Having said that, we are trying to upgrade to angular 10 just as a way for the library to leverage the capabilities, but not because of errors or issues.

If there was a clear policy or guidance that 3.X should work with Angular 10, then we would attempt to upgrade and do our best to help resolve them. But in the absence of that we're left with ambiguity and it's unclear if we should invest effort in that attempt to upgrade. This issue is asking about any policy or guidance that is available on what version(s) of Covalent support what version(s) of Angular, specifically major versions, so that we can make an informed decision about when to plan on attempting to upgrade.

Gotcha, ill create a section on the main README.md to state which versions of angular and material should work with covalent 3.X.

Thank you! Look forward to trying Covalent 3.X with Angular 10.

Added the matrix on the README.
But please let us know if you encounter any issues, we have tested with our internal products and havent found any issues with covalent 3.X -> ng 9.X/10.X
We already merged the ng10 upgrade and are gonna start focusing on the future releases

@emoralesb05 Ed this is great, thank you again and thanks for your work on Covalent!


Use FormPage for Import Model page

What does this PR do?
Updtae the "Import Model" page to use the dedicated FormPage component instead of NavPage
Also change a few colors to support light mode (except colors in the form itself)
Screenshot / video of UI
What issues does this PR fix or reference?
Fixes #1229
How to test this PR?
Navigate to Catalog > Import

One small issue
[...]
We have a clear improvement on the light mode (nice job), but we loose the separation between the secondary navigation and the content on both theme

Do you mean the vertical shadow between the 2 zones? If so, this issue tracks the problem: https://github.com/containers/podman-desktop/issues/7549

Do you mean the vertical shadow between the 2 zones? If so, this issue tracks the problem:

Sorry if I was not clear enough, the fact that the main and secondary navigation are both the same color:

Do you mean the vertical shadow between the 2 zones? If so, this issue tracks the problem:

Sorry if I was not clear enough, the fact that the main and secondary navigation are both the same color:

I double-checked, and for me the 2 colors were already before really the same (#343434), but the shadow in the middle makes one think they are different


The audio subtitles are showing unlocalized names.

As seen here.  Love the mod

Fixed in commits 5dd8b96 (1.18.2), cf3f032(1.18.1), ee4aab8(1.16.5)


failed to compile a simple CUDA program

failed to compile a simple CUDA program
Expected Behavior

i want to use coda to speed cnn face detect but i failed to compile a simple CUDA program
Current Behavior
-- Found CUDA: /usr/local/cuda-9.0 (found suitable version "9.0", minimum required is "7.5")
-- Looking for cuDNN install...
-- Found cuDNN: /usr/local/cuda-9.0/lib64/libcudnn.so
-- Building a CUDA test project to see if your compiler is compatible with CUDA...
-- *****************************************************************************************************************
-- *** CUDA was found but your compiler failed to compile a simple CUDA program so dlib isn't going to use CUDA.
-- *** The output of the failed CUDA test compile is shown below:
-- ***   Change Dir: /home/lhw/dlib/dlib-19.13.1/build/temp.linux-x86_64-3.6/dlib_build/cuda_test_build

***   Run Build Command:"/usr/bin/make"
***   [ 50%] Building NVCC (Device) object CMakeFiles/cuda_test.dir/cuda_test_generated_cuda_test.cu.o
***   /usr/include/c++/5/functional(78): error: class "std::thread" has no member "result_type"
***             detected during:
***               instantiation of class "std::_Maybe_get_result_type<_Functor, void> [with _Functor=std::thread]"
***   (86): here
***               instantiation of class "std::_Weak_result_type_impl<_Functor> [with _Functor=std::thread]"
***   (184): here
***               instantiation of class "std::_Weak_result_type<_Functor> [with _Functor=std::thread]"
***   (264): here
***               instantiation of class "std::_Reference_wrapper_base_impl<true, true, _Tp> [with _Tp=std::thread]"
***   (283): here
***               instantiation of class "std::_Reference_wrapper_base<_Tp> [with _Tp=std::thread]"
***   (399): here
***               instantiation of class "std::reference_wrapper<_Tp> [with _Tp=std::thread]"
***   /usr/include/c++/5/future(1638): here

***   /usr/include/c++/5/functional(266): error: class "std::thread" has no member "argument_type"
***             detected during:
***               instantiation of class "std::_Reference_wrapper_base_impl<true, true, _Tp> [with _Tp=std::thread]"
***   (283): here
***               instantiation of class "std::_Reference_wrapper_base<_Tp> [with _Tp=std::thread]"
***   (399): here
***               instantiation of class "std::reference_wrapper<_Tp> [with _Tp=std::thread]"
***   /usr/include/c++/5/future(1638): here

***   /usr/include/c++/5/functional(267): error: class "std::thread" has no member "first_argument_type"
***             detected during:
***               instantiation of class "std::_Reference_wrapper_base_impl<true, true, _Tp> [with _Tp=std::thread]"
***   (283): here
***               instantiation of class "std::_Reference_wrapper_base<_Tp> [with _Tp=std::thread]"
***   (399): here
***               instantiation of class "std::reference_wrapper<_Tp> [with _Tp=std::thread]"
***   /usr/include/c++/5/future(1638): here

***   /usr/include/c++/5/functional(268): error: class "std::thread" has no member "second_argument_type"
***             detected during:
***               instantiation of class "std::_Reference_wrapper_base_impl<true, true, _Tp> [with _Tp=std::thread]"
***   (283): here
***               instantiation of class "std::_Reference_wrapper_base<_Tp> [with _Tp=std::thread]"
***   (399): here
***               instantiation of class "std::reference_wrapper<_Tp> [with _Tp=std::thread]"
***   /usr/include/c++/5/future(1638): here

***   4 errors detected in the compilation of "/tmp/tmpxft_0000fd33_00000000-7_cuda_test.cpp1.ii".
***   CMake Error at cuda_test_generated_cuda_test.cu.o.cmake:262 (message):
***     Error generating file
***     /home/lhw/dlib/dlib-19.13.1/build/temp.linux-x86_64-3.6/dlib_build/cuda_test_build/CMakeFiles/cuda_test.dir//./cuda_test_generated_cuda_test.cu.o

***   CMakeFiles/cuda_test.dir/build.make:63: recipe for target 'CMakeFiles/cuda_test.dir/cuda_test_generated_cuda_test.cu.o' failed
***   make[2]: *** [CMakeFiles/cuda_test.dir/cuda_test_generated_cuda_test.cu.o] Error 1
***   CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/cuda_test.dir/all' failed
***   make[1]: *** [CMakeFiles/cuda_test.dir/all] Error 2
***   Makefile:83: recipe for target 'all' failed
***   make: *** [all] Error 2

-- *****************************************************************************************************************
-- Disabling CUDA support for dlib.  DLIB WILL NOT USE CUDA
Steps to Reproduce

Version: 19.13.1
Where did you get dlib: pip download dlib
Platform: ubuntu 16.04 64bit
Compiler: The C compiler identification is GNU 5.4.0,The CXX compiler identification is GNU 5.4.0

I fixed this by using gcc-6 instead of gcc-5. make sure your cuda version is recent enough to support it. (for me, 9.0 works)

I had a similar problem in Ubuntu 18.04. Here are the steps I used to solve it:

cd to the dLib build directory
rm -rf *
cmake … (this fails on the CUDA test file so no CUDA support)
rm -rf *
cmake … -DCUDA_HOST_COMPILER=/usr/bin/gcc-6 (Now I have CUDA support)
cmake --build . --config Release
sudo ldconfig
cd …
python3 setup.py install (fails on CUDA test program, no cuda support)
I forgot to enable my python env
workon cv
python3 setup.py install (fails on Cuda Test program, no CUDA support)
python3 setup.py --compiler-flags “-DCUDA_HOST_COMPILER=usr/bin/gcc-6” install (no failures, but does not say CUDA support so I am assuming I have it)

Doug

You have cuda support if dlib.DLIB_USE_CUDA is true.
Also, running cmake and ldconfig are not required when using the python API.  In fact, those steps do nothing at all related to using dlib in python.   I keep seeing people post these instructions all over the place.  I assume you read them somewhere? Can you tell me where?

Hi Davis,
I saw that in a blog that you responded to saying it was not necessary. I have followed so many different blogs it is hard to get them down but here goes:
https://www.learnopencv.com/install-dlib-on-ubuntu/
https://peshmerge.io/how-to-build-dlib-on-linux-ubuntu-18-04-using-cmake-with-avx-support-and-install-its-python-api/
Are two. I usually follow what Satya Mallick and Adrian Rosebrock suggest as I am taking both courses. I put in a report on the dlib web site. It is less of a report and more of how I got around the problems I was seeing. Here is what I ended up doing:
I will post the whole thing in answer to your next email.
Best Regards / Mit freundlichen Grüßen,
Doug
<EMAIL_ADDRESS>Douglas R. Jones
Sr. Software Engineer/AdVISE Project Mgr.
Rohde & Schwarz USA, Inc.
1500 Lakeside Parkway Ste 100
Flower Mound, TX 75028
Mobile: +1<PHONE_NUMBER>
Office: +1<PHONE_NUMBER>
E-Mail: Doug.Jones<EMAIL_ADDRESS>Website: http://www.rohde-schwarz.com/
From: Davis E. King<EMAIL_ADDRESS>Sent: Monday, August 6, 2018 14:47
To: davisking/dlib<EMAIL_ADDRESS>Cc: Jones Doug 5USS<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: EXT [Newsletter] Re: [davisking/dlib] failed to compile a simple CUDA program (#1365)
You have cuda support if dlib.DLIB_USE_CUDA is true.
Also, running cmake and ldconfig are not required when using the python API. In fact, those steps do nothing at all related to using dlib in python. I keep seeing people post these instructions all over the place. I assume you read them somewhere? Can you tell me where?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/davisking/dlib/issues/1365#issuecomment-410830538, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANWi5IQN_fpT3en40jS9_vXgJ_FhStwHks5uOJ0ZgaJpZM4UttYp.

Ok.  Thanks for reporting this.
The official instructions are here: http://dlib.net/compile.html.  Did you see them?  Somehow I get the impression that many users don't find that page.  Or they ignore it.

Hi,
Yes, I did. But after being away from Linux/Unix for 10 years I just followed what Adreian and Satya suggest.
Best Regards / Mit freundlichen Grüßen,
Doug
<EMAIL_ADDRESS>Douglas R. Jones
Sr. Software Engineer/AdVISE Project Mgr.
Rohde & Schwarz USA, Inc.
1500 Lakeside Parkway Ste 100
Flower Mound, TX 75028
Mobile: +1<PHONE_NUMBER>
Office: +1<PHONE_NUMBER>
E-Mail: Doug.Jones<EMAIL_ADDRESS>Website: http://www.rohde-schwarz.com/
From: Davis E. King<EMAIL_ADDRESS>Sent: Monday, August 6, 2018 15:28
To: davisking/dlib<EMAIL_ADDRESS>Cc: Jones Doug 5USS<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: EXT [Newsletter] Re: [davisking/dlib] failed to compile a simple CUDA program (#1365)
Ok. Thanks for reporting this.
The official instructions are here: http://dlib.net/compile.html. Did you see them? Somehow I get the impression that many users don't find that page. Or they ignore it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/davisking/dlib/issues/1365#issuecomment-410842555, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANWi5LD4OZZMquFL0ZTyg7eezlewxNwMks5uOKbUgaJpZM4UttYp.

I know this issue is closed, but I encountered this issue after installing CUDA and cuDNN (Ubuntu 22.04). I couldn't get dlib to work with CUDA support as I met the error: CUDA was found but your compiler failed to compile a simple CUDA program so dlib isn't going to use CUDA.
I solved this issue by installing GCC 6 and G++ 6 and using the command python3 setup.py --set CUDA_HOST_COMPILER=/usr/bin/gcc-6 install after cleaning the build directory. After doing the above steps, I successfully compiled dlib with CUDA and received Enabling CUDA support for dlib.  DLIB WILL USE CUDA


improve directory structure + code cleanup

Reorganized project files, moved react code to app/ and subfolders.
Moved AWS settings in a separate file, same for the makeRandomHex function.
There were some inconsistencies in the use of semicolons, so I made the choice to remove all of them.
I can't test the iOS part, however the only different file being index.io.js, it should work fine (a feedback would be much appreciated).

Thanks @Hastegan


NEXT-8590 - Open product in storefront (from administration)

Description
A product detail page should have an option to open the product in the storefront. There would be a select-box to choose the sales channel to open. Next to this select-box would be a button to open the product in the selected sales channel in a new tab.
Without this change, you would have to search for your product and then choose it from the search result page.

Example
Should be self-explanatory.

The selection should be for a sales channel domain (maybe two steps or a grouped dropdown?) instead.

@kleinmann Yes, that sounds like a good idea. However, it might not be as necessary, since every domain in a sales channel should look the same. But yes, for maximum control it should be selectable.

I just drop this here
https://github.com/shopware/platform/pull/574

Hello,
thank you for creating this issue.
I have opened a ticket on our Issue Tracker for you. See the ticket link: https://issues.shopware.com/issues/NEXT-8590
Please use this ticket to track the state of your issue.

Interested

I still think this is a valid feature request. Eventhough 4 years have passed the Admin team will take this on directly now.
https://issues.shopware.com/issues/NEXT-35052

Short Update:
The UI/ UX team gave valid Feedback that this will fit better in the UI with the new Smartbar structure. That's why nothing has happened yet. Would you be fine closing this Github Issue and take NEXT-35052 as the source for this feature request? That way we don't have to update both 🙈

See above comment ⏫


Fix Timer ticks down past 0 into negative values #41

Description
Added an exit condition to startCountdown() to break out of a loop that would infinitely count negatives
Closes CommunityFocus/CommunityFocus/issues/41

I believe this will be complete after adding some more testing.


Route infos get cut on small screens

I don't know if it's possible, but I really wish the route infos would wrap to the next line instead of disapearing at the end of the window like so

Not quitely possible to wrap it, but I added a new option to set it on the line above.
please update the plugin and in your settings use
    require("laravel").setup({
      route_info = {
        enable = true,
        position = "top",
      },
    })

Yes, in general it would get quite messy if you would wrap these, if you have a lot of middlewares. Maybe it would make sense to trim the namespaces or such to make it less, and have a way to get more info, maybe some command, not sure.

Yeah I don't think wrapping is a good idea either, but as far as I know there is no way to wrap virtual text in that way. I think the idea on  the line before is good, I am currently using it. I will close the issue now.
For the case if you have a lot of middleware using multiple virtual lines is an option.
Maybe habe a short version that is in the same line as now only having method and uri, and a more detailed version that is hows on virtual lines above it.


Minor bug in the example from 'Inheriting from EventEmitter' section

Inheriting from EventEmitter section requires events and incorrectly assigns to EventEmitter object.
const EventEmitter = require('events');

It should be
const EventEmitter = require('events').EventEmitter;

Even while [introducing EventEmitter class] (https://nodejs.org/api/events.html#events_class_events_eventemitter), it mentions var EventEmitter = require('events'); which should have been var EventEmitter = require('events').EventEmitter;
Run the code otherwise complains TypeError: Object prototype may only be an Object or null, which is understandable as object returned by simply requiring events does not have prototype property.

const EventEmitter = require('events') is actually the correct way of doing this now in v4.x
Refs: https://github.com/nodejs/node/pull/3509


etcd: version orders in version-switch drop-down box

The box is really awesome and easy to switch between different versions! I really like it.
But the version is ordered randomly in my browser, which is not that clean:

Maybe change it to list from newest to oldest?

This is currently not possible to do in Jekyll, but this would be a really nice thing. The OS also struggles with this. It's on the list of things to figure out, but might be hard. In the meantime, we also need to do some CSS work to at least make this scroll for long listings.

Closing due to inactivity.


Clarify license

As far as I understand from the website, the licensing of ol3 is:

Code licensed under the 2-Clause BSD. All documentation CC BY 3.0.

 Can they be removed?

I don't even recall what that 5 year old folder was for, so I'm inclined to say that it can go.
Anybody @openlayers/core remember?

It was a simple copy from ol2: https://github.com/openlayers/ol2/tree/master/licenses
+1 to remove

Could you open this issue again and fix LICENSE.md ?

@genofire What’s wrong with LICENSE.md?

There is not written, that this is a BSD License.
At the first look, github show it like a own created (maybe not opensource) license:

Here a example, how it look, if it is correct formated:

This is because our license is closer to the BSD-2-clause-FreeBSD license than the BSD-2-clause license. You are right that this is not ideal.
@tschaub @elemoine @bartvde Should we switch to a plain BSD-2-clause license? It would mean to get rid of the last paragraph:
The views and conclusions contained in the software and documentation are those
of the authors and should not be interpreted as representing official policies,
either expressed or implied, of OpenLayers Contributors.
I think it would be reasonable to remove that paragraph, and maybe add a code of conduct to the repository instead.
Opinions?

I guess this is an artefact from the Metacarta days? I wouldn't be opposed to making the change, but would we need to get permission from all contributors?

Our previous license change, wich removed the clause about patents, did not require permission from all contributors, as far as I remember. Maybe @crschmidt knows more?

We did have a vote last time (see the motion on the old dev list).  That was a vote to change what we had previously (MetaCarta's custom modified BSD) to the BSD 2-Clause License (also known as the FreeBSD License).
This doesn't change anything about what the project's license requires, permits, or prohibits, but I added "The 2-Clause BSD License" to the top of the LICENSE.md file in #9319 to clarify what license template the project uses.


npm version not remove console.logs

npm version: 1.0.4
No matter what log level configured, once you logged the console always print logs. Then the browser will dead!

@kefengwei Can you test 1.0.5 and see if the removing of the log messages helped in your case?

@alx-andru  There is no log messages in 1.0.5. Thank for your update.

Hey @kefengwei thank you very much for confirming. Closing the issue then


Show inner hidden menu element above perfect-toolbar div

Hi
I can not see an "actions" hidden menu using onClik event into a button.
The menu is not seen entirely, it stays below the perfect-scrollbar div.
How can i see the menu above the perfect-toolbar div ?
I try every possible combination of positioning between three elements:
eg.:
.table-list-div: 	 position: absolute; z-index: 1;
.table-list-results:  position: absolute; z-index: 2;
.dropdown-menu-right: position: relative; z-index: 3;
and so on...
Steps to reproduce:

Set a perfect-scrollbar div (i do apply class=table-list-div)
Set a table with 10 query results or more (i do apply class=table-list-results)
Set a hidden menu using bootstrap library dropdown-menu class  (i do apply class=dropdown-menu-right) .

We actually do not use z-index at all, so it must show properly. Can you provide a fiddle reproducing the problem? You can start from forking basic fiddles.

Vanilla JS: https://jsfiddle.net/DanielApt/xv0rrxv3/
jQuery: https://jsfiddle.net/DanielApt/gbfLazpx/

Closed for its inactivity. Please feel free to re-open.


ci: upgrade to latest stable version of toys

This will fix issues with incompatible version usage in configs:
https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/6534421626/job/17741560442#step:5:10

cool, this should pull in https://github.com/dazuma/toys/pull/218 and make my dream of improved multi-release commit mesages true :tada:


[Feature Request]: Option to auto-dismiss Popup Notifications

+1

+1

This was added here: fbea3aa33de673bfdff8110c56cdce10877399a4, here: c326cf863fbd8d14c40e835823f1a914d8356e53, here: 0d81e07de662fa3495086083ca70033e06e6929a, and here: 245d843b3bf36701cc41aa77e9767ebb4a0ab580
The changes are available now in release 1.3.8.


Server sent events with poltergeist

if you're using Server Sent events (https://developer.mozilla.org/en-US/docs/Server-sent_events/Using_server-sent_events ) in your project and ActionController::Live then poltergeist always fails complaining on corresponding pages with error
Capybara::Poltergeist::TimeoutError:
    Timed out waiting for response to ...

But this is actually a feature of Server events, not an error. Also this error do not happen if I use long-polling with AJAX.
PS: sorry, I'm quite new to RoR, so haven't figured out how to write proper rspec test for this issue, instead I created repository with test project to reproduce this error: https://github.com/b0ric/poltergeist-sse-test

Is this working with PhantomJs 2 now?

@twalpole haven't tested this in a long time...

Closing due to lack of updates - If this is still and issue in PhantomJS 2.1.1+ we can reopen later


Add --store argument to insert command

Summary
Currently there is no way to specify the store while inserting a secret. Though gopass create supports it, using create forces one to use one of the five predefined types of secrets, thus forcing a specific directory structure on the user.
gopass insert digitalocean.com/username1 does what is needed, and creates the directory structure as expected. But it uses the default password store. What is required is to create the digitalocean directory inside a different store, say personal, so the directory structure will be ~/.password-store-personal/digitalocean/username1.
Using gopass create --store personal and selecting Website as secret type causes the directory structure to be ~/.password-store-personal/websites/digitalocean/username1. There is no way to skip the websites portion there.

Just realized I can do gopass insert personal/digitalocean/username1 and it will auto-detect the store. That was not intuitive, especially when there is an explicit --store argument available.
Maintainers, feel free to close this issue. But, personally I feel --store could be made explicit and/or docs could be added.

Thanks for reporting this issue. I see the UX implications here and we'll certainly consider how we can improve this.

I also would like the option to specify the store to use.

But what would it be for since the store detection can already be done via the secret path? I personally like how it is organized currently. Or shall it be possible to have a path multiple times if it is contained in different stores?


fix(actors): timer ticker bug

The timer task needs to wait for the execution of the first dueTime's task to start the period's timer

@vinayada1 can you review this?

@vinayada1 can you review this?

@1046102779 we will merge this as is, thanks a lot for this fix. please find the time to add a unit test in a separate PR.

@1046102779 we will merge this as is, thanks a lot for this fix. please find the time to add a unit test in a separate PR.


[Bug]: Double scroll appears on the share modal

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Two scrolls appear on the share modal as seen in the video
Steps To Reproduce

Open a workspace with at least 5-8 users so you can scroll on the share modal as seen in the video
Observe the double scroll

Public Sample App
No response
Issue video log
https://www.loom.com/share/a3a0fb53106a49339e92f625199f1cd2
Version
Cloud

not reproducible anymore
https://github.com/user-attachments/assets/ba754a4b-4a94-4d70-9c30-055715df097e


Fix install with only PyTorch

Install was failing when only PyTorch was installed.  My b for not testing in an environment w/ only PyTorch.  Going to set up a proper testing matrix (python version * os * tensorflow/pytorch)
Will fix https://github.com/brendanhasz/probflow/issues/28

Codecov Report

Merging #29 (d272539) into master (b6ed723) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #29   +/-   ##
=======================================
  Coverage   99.47%   99.47%
=======================================
  Files          66       66
  Lines        2092     2092
=======================================
  Hits         2081     2081
  Misses         11       11

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 b6ed723...d272539. Read the comment docs.

Codecov Report

Merging #29 (0224e66) into master (b6ed723) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #29   +/-   ##
=======================================
  Coverage   99.47%   99.47%
=======================================
  Files          66       66
  Lines        2092     2094    +2
=======================================
+ Hits         2081     2083    +2
  Misses         11       11

Impacted Files
Coverage Δ

src/probflow/utils/validation.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[Bug] dbt docker image are not available in GHCR

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The last docker image available on github package is dbt-core 1.7.5 but the last version available on pypi is dbt-core 1.7.8
Expected Behavior
For each release of dbt-core there should be a container available on github package.
Steps To Reproduce
docker pull ghcr.io/dbt-labs/dbt-core:1.7.8

Relevant log output
No response
Environment
No response
Which database adapter are you using with dbt?
No response
Additional Context
No response

Thanks for reporting this @scauglog 👍
I've added your report to https://github.com/dbt-labs/dbt-core/issues/7571

Thank you. An image with the latest version of dbt is fine for me.


Replace java-faker with kotlin-faker

Hi,
Since easy-random deals a lot with data generation, I thought this PR would be beneficial for this library :)
java-faker has not been well maintained lately, and has a big number of open bugs. This PR replaces java-faker with kotlin-faker, which in addition to being actively maintained, has more data providers and locales implemented and has extra "batteries" included, like generation of random class instances, unique random values, etc. It's also quite faster than java-faker.
This is my first contribution, so hope I've done everything that is required for first-time contributors.

How about using  Datafaker https://github.com/datafaker-net/datafaker
Seems like it would require less effort for refactoring.

This was addressed in #490. Moreover, we don't want to imply anything related to Kotlin or other JVM languages in ER.
Thank you for your contribution anyway! Appreciated the effort.


Embedded Sub-Pages Widget Found

docs/home/12c-ocm/data-guard.html has an embedded sub-pages widget which does not converted well.

Another occurrence is in docs/home/12c-ocm/data-guard.html.

Duplicate of #33


Markdown Frontmatter not accessible

According to https://vite-plugin-ssr.com/markdown

We can also use a so-called front matter to define the page's metadata.

however I can't get it  to work.

I have created a fork with a md_frontmatter_example branch to reproduce.
https://github.com/oliverpool/vite-plugin-ssr/commit/25d1bfbacacadde7da19ff949322290dbe82ff48

added a examples/vue-full/pages/markdown-frontmatter.page.md file with a frontmatter containing title: A Markdown Page
when visiting http://localhost:3000/markdown-frontmatter the browser tab title is still Demo and not the expected A Markdown Page

The title is however modifeid, when visiting /markdown:
<script>
export const documentProps = {
  title: 'Some Markdown Page'
}
</script>

Is there something missing to make the frontmatter work?

It's very likely a problem with your code

I took the code of the vue-full example of this repo. What should I change to make it work?
I couldn't find any hint in the documentation

Updated docs

With vue 3, vite-plugin-md exposes the frontmatter with defineExpose({ frontmatter }) : https://github.com/antfu/vite-plugin-md/blob/24ae1046f02669dcaf0040483920544b4277a12b/src/markdown.ts#L91
I am looking into your source, how support for defineExpose could be added, but I currently have no clue, where and how the files are imported into vite-plugin-ssr.

Why not simply using https://vite-plugin-ssr.com/markdown#head-pagecontext-pageexports instead of a frontmatter?

Because it is much more user/editor friendly to edit a frontmatter in mardown than a JS-Block:
export const documentProps = {
  title: 'A Markdown Page',
  description: 'Example of setting `<title>` and `<meta name="description">`'
}

(for instance the Netlify CMS supports Frontmatter very nicely).
This is probably more of a general vite question, so I asked on the vite-plugin-md repo: https://github.com/antfu/vite-plugin-md/issues/38

👍


Enables gitlab provider in controller

this enables gitlab integration with controller
using webhook.
Signed-off-by: Shivam Mukhade<EMAIL_ADDRESS>
Changes

Submitter Checklist

[x] ♽  Run make test lint before submitting a PR (ie: via pre-push github hook no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please make sure to document it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please make sure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then make sure to get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it.

See the developer guide for a bit more details.

that's a new one!

let me see to fix it properly,

/retest

Codecov Report

Merging #497 (d2a111e) into main (0b94308) will increase coverage by 2.27%.
The diff coverage is 75.43%.

@@            Coverage Diff             @@
##             main     #497      +/-   ##
==========================================
+ Coverage   71.01%   73.29%   +2.27%
==========================================
  Files          54       55       +1
  Lines        3081     3134      +53
==========================================
+ Hits         2188     2297     +109
+ Misses        688      630      -58
- Partials      205      207       +2

Impacted Files
Coverage Δ

pkg/provider/bitbucketcloud/events.go
74.75% <0.00%> (ø)

pkg/provider/bitbucketserver/events.go
71.25% <0.00%> (ø)

pkg/adapter/adapter.go
17.28% <25.00%> (+0.84%)
:arrow_up:

pkg/provider/gitlab/gitlab.go
92.50% <87.87%> (+40.45%)
:arrow_up:

pkg/provider/bitbucketcloud/bitbucket.go
80.70% <100.00%> (ø)

pkg/provider/bitbucketserver/bitbucketserver.go
85.97% <100.00%> (ø)

pkg/provider/github/github.go
87.12% <100.00%> (ø)

pkg/provider/provider.go
54.54% <100.00%> (ø)

pkg/acl/acl.go
100.00% <0.00%> (ø)

... and 1 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 0b94308...d2a111e. Read the comment docs.


Add MSSQL dependency and fix tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5718b1a). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   89.58%
=========================================
  Files             ?        1
  Lines             ?       96
  Branches          ?        0
=========================================
  Hits              ?       86
  Misses            ?        5
  Partials          ?        5

Impacted Files
Coverage Δ

xormstore.go
89.58% <ø> (ø)

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 5718b1a...a57a3db. Read the comment docs.


Don't swallow ImportError (fix #277).

Also, test various import failure modes.

I really need to get back to my remote stuff and add the triggers... you keep changing files I changed :P
+1

Ah, yes, I'm sort of aware of that, but felt, well, I should knock out these issues anyway, they aren't big and the merge won't be that bad... I hope... !

Yeah... it's annoying but relatively simple test.
On Fri, Jul 14, 2017 at 1:00 PM, Tom Swirly<EMAIL_ADDRESS>wrote:

Ah, yes, I'm sort of aware of that, but felt, well, I should knock out
these issues anyway, they aren't big and the merge won't be that bad... I
hope... !
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/286#issuecomment-315411490,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6pUtPlxmxY_KEWMfYkJ5bYA60sDrks5sN56cgaJpZM4OYZew
.


Dynamically add slides in the middle of a glide produce strange result

If I have a glide like this (where slides is an array of 3 elements):
<vue-glide>
    <vue-glide-slide v-for="(slide, i) of slides" :key="i">
        Heyy, I am slide { i }
    </vue-glide-slide>
</vue-glide>

In the rendered HTML, each slide (.glide__slide) has a data-glide-index attribute. I this case, each data-glide-index is respectively 0, 1 and 2.
but now, if I create a button who adds an element in the middle of my list (for example between index 1 and 2), the data-glide-index of each slide will be respectively 0, 1, 3, 2.
By the way, the display will be broken and I will not be able to focus the new slide.

I found a work around:
<template>
<vue-glide ref="glide">
    <vue-glide-slide v-for="(slide, i) of slides" :key="i">
        Heyy, I am slide { i }
    </vue-glide-slide>
</vue-glide>
</template>

@Component({
  components: {
    [Glide.name]: Glide,
    [GlideSlide.name]: GlideSlide
  }
})
export default class SlidesComponent extends Vue {
    slides = [{}, {}, {}]
    addSlide () {
    const glide = this.$refs.glide
    this.slides.push({})
    glide.glide.destroy()
    this.$nextTick(() => {
      glide.init()
    })
    }
}

But it still glitch a little bit (and it's not very nice if you want to stay focus on the same slide after adding the new slide)

After add new slide into array slides between index 1 and 2, data-glide-index of each slide will be respectively 0, 1, 2, 3 not 0, 1, 3, 2.
Example https://codesandbox.io/s/n722774xl

@vcastro45 Because you have manually added an item to the slide. The other of the slides are rendered through a loop from the array in which you add a new item.

@vcastro45 If you need reinit, it can be done without calling glide methods. You can add just a unique key for vue-glide, for example it can be length of array, to prevent reuse of the vue component
<template>
<vue-glide ref="glide" :key="slides.length">
    <vue-glide-slide v-for="(slide, i) of slides" :key="i">
        Heyy, I am slide { i }
    </vue-glide-slide>
</vue-glide>
</template>
``


Individual components should be given a more appropriate coordinate space to draw into

When implementing the Draw() method of a component, the 0,0 coordinate should be their upper left corner, not the their parent's upper left corner. This means that the call to draw a rectangle should not begin at instance.GetX() and instance.GetY(), but at 0,0.

This will just work with the current plan for composition in the component definition.
New components will rarely be defined as a struct that composes Component, but will instead be defined as a render function that composes child components / views. In this case, those children and the view will have the coordinates of the component itself.


Unable to Login on Dashboard

Unable to login with the id/password described in readme.

@techmkumar have you got your solution? I am facing same issue

Receiving an 'undefined' error when attempting to log in using username and password. Is there a solution for this?


Get a Rails error when using mount Hyperloop::Engine => '/hyperloop'

Hyperloop Gem version (e9b83bfa6bea)
Rails version (5.0.2)
When using mount Hyperloop::Engine => '/rr' everything works well.
When using mount Hyperloop::Engine => '/hyperloop'
I got the error:
ActionController::RoutingError (No route matches [GET] "/rr/hyperloop-read/2bd082bb-3452-4bab-b206-af440493e67f-26b7b23137ba510a0f1a06535630a123"):

cannot reproduce... please try again and close if you confirm its not a problem


Perplexity number of wikitext-103 on gpt-2 don't match the paper

Hi,
The reported perplexity number of gpt-2 (117M) on wikitext-103 is 37.5.
However when I use the pre-trained tokenizer for gpt-2 GPT2Tokenizer using:
tokenizer = GPT2Tokenizer.from_pretrained('gpt2') to tokenize wikitext-103, and then evaluate it using the pre-trained 117M gpt-2 model, I get a ppl of 48.4
Note: I have added newlines instead of EOS tags at the end of each line read. I've also normalized the loss by the number of tokens originally in wikitext-103 as mentioned by Alec Radford at https://github.com/openai/gpt-2/issues/78
Could you please let me know whats wrong here?

Are you using context length 256 by change?
On WikiText-2 I see
I see 29.17378 using context length 1024 and 43.3393707 using context length 256
This is close to OpenAI report result of  29.41
(although I don't get why it doesn't match it exactly)

No, I'm using a context length of 1024.
Although, when I evaluate it on wikitext-2, my numbers dont match with yours. Would it be possible for you to share what you've done? I believe that you might have normalized the loss by the number of tokens after the gpt-2 tokenization, and not by the number of tokens originally in wikitext-2.

Here's our loss computation
We don't normalize the loss here, just take the average output of model(batch, lm_labels=batch) where model is GPT2LMHeadModel.from_pretrained(args.model_name_or_path)
Note wikitext-103 and wikitext-2 have the same test set, so you should get 29.17378 perplexity on either one

@Akhila-Yerukola when we tried normalizing by the original token count, our ppl number got much further from the paper.
I ran wikitext-2-raw/wiki.train.raw through the encoder and got 2417793 tokens. Then I split the original on spaces and got 2088678.
math.exp(math.log(29.41) * 2088678 / 2417793) # 18.56

We got 30.4 ppl unnormalized and 28 after detokenizing, so we're still quite far from 18.56.
Another possibility is that for evaluation, instead of chunking the dataset and shoving it through, they pass it in 1 token at a time the same way they do for sample generation. This would significantly reduce the loss because the model wouldn't "forget" what it was doing at the beginning of each sequence. I'll try this later today.

As a quick test, I calculated loss based on only the last 10 tokens of the sequence without changing the chunking. I got test loss of 23.9 and train 24.9.

I'm pretty confused about the numbers reported in the gpt-2 paper now.
The Table 3 in the paper which contains Zero-shot results on many datasets has a "SOTA" row which correspond to the reported perplexity numbers on the test sets of the data sets. (I verified this for wikitext-2 and wikitext-103)
Shouldn't that mean gpt-2 should have released the perplexity numbers on the test sets of the datasets? Then why are the columns for wikitext-2 and wikitext-103 different given that their test sets are the same?

@yaroslavvb @8enmann
I still think the numbers don't match the paper.
The Table 3 in the paper which contains Zero-shot results on many datasets has a "SOTA" row which correspond to the reported perplexity numbers on the test sets of the data sets. (I verified this for wikitext-2 and wikitext-103)
When I run this evaluation script, I get ppl of 23.85 on wikitext-2 (not raw), 28.186 on wikitext-103 (not raw),  29.01 on wikitext-103-raw (and wikitext-2-raw). None of these match the reported 117M gpt-2 model numbers from the paper (29.41 for wikitext-2, 37.5 for wikitext-103)
From the looks of it wikitext-103 is way off.

You're right, our results are very different from the paper. Perhaps they used the detokenized non-raw version and also for the labels passed -1 for  tokens, which causes them not to be evaluated for loss. This, combined with the 1 at a time trick I mentioned 2 days ago, could bring PPL down to ~18. However that still leaves a big puzzle as to why the loss they reported on wikitext-103 is so much worse than wikitext-2.

Related issue, Lambada numbers also don't match the paper (31% instead of reported 46%)

@yaroslavvb @8enmann
When I run this evaluation script, I get ppl of 23.85 on wikitext-2 (not raw), 28.186 on wikitext-103 (not raw), 29.01 on wikitext-103-raw (and wikitext-2-raw). None of these match the reported 117M gpt-2 model (which is the model available) numbers from the paper (29.41 for wikitext-2, 37.5 for wikitext-103)

Is it possible to know why 0.7 and 0.3? --> 0.7exp_average_loss+0.3loss.item()

This discussion is old, so this may not be applicable anymore. But I'd like to offer a data point if it's still the case. I tried gpt2 and gpt2-medium on OpenWebText (tokenized with HuggingFace's corresponding tokenizer settings), and I got the ppl about 24 and 18, respectively, whereas the openai version of them is 17 and 13, respectively. This is good enough to say that I probably didn't make any catastrophic mistake, but there still is some gap, which may or may not explain the performance gap on other datasets.


Factor in tags from scripts

Tags added with entity.addTag() aren't considered in the tag definitions so it gets flagged as an error

Do you have a documentation link for this? and or examples. Need it to be able to implement this

https://learn.microsoft.com/en-us/minecraft/creator/scriptapi/minecraft/server/entity?view=minecraft-bedrock-stable#addtag
Lets you add a tag to an entity, like /tag but tags added via the script aren't accounted for by the extension so it throws an error whenever that tag shows up again. Like if in my script I do entity.addTag('killSoon') and in my function I do /kill @e[tag=killSoon] it gives an error

hmm this is going to be a difficult one, especially when people start to use variables for their tags

I'd imagine if it is going to be a variable, then functions probably won't be making use of them but when it's static like in the example then functions probably will use them

Anything I can do to help move this along?

Uncertain at this point, im not entirely sure I want to actually do this atm 🤔


bioconda recipe

Would it be possible to create a conda recipe (eg. at bioconda) for Sipros4? I could help if you like.
I tried to compile Sipros4 on my own and found a few problems:
Building siprosEnsembleCmake fails with:
/usr/bin/ld: attempted static link of dynamic object `/usr/lib/gcc/x86_64-linux-gnu/11/libstdc++.so'
/usr/bin/ld: attempted static link of dynamic object `/lib/x86_64-linux-gnu/libm.so.6'
/usr/bin/ld: attempted static link of dynamic object `/lib/x86_64-linux-gnu/libmvec.so.1'
/usr/bin/ld: attempted static link of dynamic object `/lib/x86_64-linux-gnu/libc.so.6'
/usr/bin/ld: attempted static link of dynamic object `/lib64/ld-linux-x86-64.so.2'
collect2: error: ld returned 1 exit status
make[2]: *** [openmp/CMakeFiles/SiprosEnsembleOMP.dir/build.make:292: bin/SiprosEnsembleOMP] Error 1
make[1]: *** [CMakeFiles/Makefile2:160: openmp/CMakeFiles/SiprosEnsembleOMP.dir/all] Error 2

I was wondering if you can/should remove all 3rd party software from your repo and use it from conda. That is, everything in
here  (e.g. zlib, sqlite, etc). I guess also license wise it would be a good idea (e.g. most of these these packages require you to ship their license which you currently do not do).

Thanks for your interest on our Sipros. The compile script in this repos is tested in the wsl ubuntu 22.04 environment on windows. May I know what your compiling environment is? I am also working on conda recipe. I have made the script for compiling it in conda envrionment. I can make a branch for the conda version. zlib and sqlite are included from mstoolkit for reading the mzml file. I can make a license file for them.

FYI https://github.com/bioconda/bioconda-recipes/pull/50631 (so far I tried to use the binaries. having it compiled would be better)

May I know what your compiling environment is?

Ubuntu 22.04.4 LTS

I can make a branch for the conda version.

Would be great for testing.

zlib and sqlite are included from mstoolkit for reading the mzml file. I can make a license file for them.

I think we should just use it from the corresponding conda packages and remove it here completely.
FYI: https://github.com/mhoopmann/mstoolkit/pull/28

I updated the compile flag in the latest commit to resolve the compilation error on Ubuntu 22.04 with g++11.

sipros-recipe.zip
I revised the recipe, and all tests passed locally using Conda build.

Thanks @xyz1396 . I incorporated your changes in my bioconda PR and played around a bit. It turns out that we can not build a package on bioconda since current versions of numpy are incompatible with python2.

@bernt-matthias . I used conda build . -c bioconda -c conda-forge for my local build test, and it succeeded. However, it seems that the recipe does not include -c conda-forge when submitting to Bioconda. I’m looking for a solution to this issue.

it succeeded finally at this commit. https://github.com/bioconda/bioconda-recipes/pull/51091


fdkaac -> libfdk-aac2

I set an a raspberry arm64 bullseye and used your script to install the codecs. Unfortunately the package fdkaac is not available in raspbians bullseye (probably booksworm too), it's called libfdk-aac2

as you can see here:
https://packages.debian.org/search?searchon=names&keywords=fdkaac
this is NOT the case.
also libfdk-aac2 is installed as an dependency on libfdk-aac-dev
try: apt show libfdk-aac-dev
have a nice day :-)

I'm sorry, you are wrong. Please read carefully, I'm on arm64 and the package is not there: https://packages.debian.org/search?suite=default&arch=arm64&searchon=names&keywords=fdkaac
Btw, the package fdkaac only is like a replacement name for actually installing libfdk-aac2.
Thank you for fixing and have a nice day!

You are right in the case the package doesn't exist for arm architectures.
On the other side do you know if things break leaving the fdkaac out of the installing process?
In this case and maintaining/extending things it would be very helpful if you want things fixed to provide a bit more infos here.
Maybe also a solution.
Best an already tested one.
It always takes a quite lot of time to get all infos together if some new usecase appears.
May you be so kind to set up several virtual machines with the different versions of Debian and architectures then test things work out if the package is fdkaac is not installed? If you have real hardware, this don't have to be VMs anyway.
Please provide me also with the output of your tests then. To proove things work out.

easiest way (depending how mouch you want to help here and how urgent your request is for you) might be to ask the debian maintainers to provide this package also for the arm architecture.
I will mark this project not supporting ARM for now.
Your help is very welcome :-)

Check https://github.com/lagerimsi-ds/debian-buster_bluetooth_aptX-LDAC/pull/15

shouldn't be be closed until now - solved but waiting for approval as I don't own an ARM-board to test.
amd64 architecture is not affected by changes and future proof as well as easy to maintain if other differences between architectures occur.
details on changes see https://github.com/lagerimsi-ds/debian-buster_bluetooth_aptX-LDAC/pull/15
so I reopen and close again when approved.

main commit of changes (some fixes came by afterwards!):
https://github.com/lagerimsi-ds/debian-buster_bluetooth_aptX-LDAC/commit/ec64082e3ad2b2c6fbc7a768ef265c1cd120b577


Regenerate markers when indent size changes

Why

When the indentation size changes (which could happen, for example, when changing language, or when the user changes a preference), the indentation markers should, ideally, change to reflect that. They currently don't.
What changed

I added check on every update that causes the markers to be regenerated if the indent size has changed. I also added a button to change indent size on the dev page.
In an unrelated change, I changed the Vite config so that there aren't HMR errors in non-Replit environments.
Test plan

Reconfigure a CM6 editor to change the indent size. The change to the dev page has an example of doing this
Indent markers should redraw to reflect the change

published in 6.2.2!


ElementUiResolver 打包后使用的组件会生成大量对应的js

Describe the bug
生成大量组件js，manualChunks: {  'element-ui': ['element-ui'] } 无法将其合并

Reproduction
1
System Info
--system --binaries --browsers

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

怎么样可以合并他们到element-ui

有什么进展吗？


PSA: Update AEAD output buffer macros to PSA API version 1.0

Description
The PSA Crypto API version 1.0 added extra parameters to the AEAD output buffer macros.
This PR updates them, and provides backwards compatibility macros using C99 vararg macros.
Closes #4163.
Status
READY
Requires Backporting
When there is a bug fix, it should be backported to all maintained and supported branches.
Changes do not have to be backported if:
No, PSA only.
Migrations
Yes, to bring us in line with PSA Crypto version 1.0.
Compatibility macros are provided.
Todos

[x] Update documentation
[x] Update uses of newly deprecated macros
[x] Update Changelog

The Travis failure is due to a bug on the development branch, that has since been fixed.
I cannot seem to re-trigger it without pushing new changes, so I'm commenting to let everyone know it can be safely ignored.

Rebased PR to fix merge conflicts.

@ronald-cron-arm

While the variadic compatibility macros contribute slightly to the overly long expansion problem, the actual root cause is in the 1.0 version of the macros introduced in the patch. In particular, the macros use PSA_AEAD_NONCE_LENGTH and PSA_AEAD_TAG_LENGTH to validate their arguments, the latter of which also calls PSA_AEAD_NONCE_LENGTH, which in turn uses PSA_ALG_AEAD_WITH_DEFAULT_LENGTH_TAG three times. So the first point would be a problem even without the compatibility layer.

The only compiler specific code I remember having introduced is the local suppression of spurious MSVC warning about standards conformant C code. It does not depend on the specific version of MSVC either. You could argue that MBEDTLS_EXPAND is also compiler specific, since it is only needed for MSVC support, but using it  doesn't use Ifdefs. Any other commits referencing other compilers were instances where the C code was not actually standards conformant, which had to be corrected.

As for the maintenance burden, I only intended this patch for the 2.x branch, with the intention being we simply break the API with the first 3.0 release. I've also tried to layer the macros logically, and in a way that makes it unnecessary to delve deeper into the inner workings of the compatibility layer to update the macros' implementation, as long as we don't change the number of arguments they take again in the future - which we Gilles has said we will avoid, and shouldn't affect the 2.x branch anyhow, with development moving on to 3.0

1. While the variadic compatibility macros contribute slightly to the overly long expansion problem, the actual root cause is in the 1.0 version of the macros introduced in the patch. In particular, the macros use `PSA_AEAD_NONCE_LENGTH` and `PSA_AEAD_TAG_LENGTH` to validate their arguments, the latter of which also calls `PSA_AEAD_NONCE_LENGTH`, which in turn uses `PSA_ALG_AEAD_WITH_DEFAULT_LENGTH_TAG` three times. So the first point would be a problem even without the compatibility layer.

ok then there is maybe something to do here. Those are macros aimed to be used by applications. We have encountered problems to use them because their expansion is very large thus some applications are likely to hit the same kind of problems at some point. One solution I see is to implement them as functions. We have psa_crypto_client.c to contain such functions needed on the client side.

We promise in the API docs, that these macros will return compile-time constants - so I don't think we can implement them as functions.
I think I can modify PSA_AEAD_NONCE_LENGTH to make this problem go away, for now at least - even with the compat layer applied.

We promise in the API docs, that these macros will return compile-time constants - so I don't think we can implement them as functions.

Right, forgot about that.

I've removed the macro expansion length workaround, and pushed a new commit that reduces the expanded size of the macros considerably.

Good that is a much better solution to me. What is the maximum expanded size now?

The longest macro expands to 2343 characters, or 2119 characters with MBEDTLS_DEPRECATED_REMOVED (the compat layer adds 224 characters).
This is down from 6482 and 6259 before the latest commit.

The longest macro expands to 2343 characters, or 2119 characters with MBEDTLS_DEPRECATED_REMOVED (i.e. the compat layer adds 224 characters).
This is down from 6482 and 6259 before the latest commit.

Great, that's good improvement. Any other idea to reduce this further as over 2000 characters is still quite big ?

With the commit I just pushed, I've further reduced the expanded size of the longest macro to 1167 characters, or 1055 with MBEDTLS_DEPRECATED_REMOVED defined.

I've pushed a new version of the PR with the compatibility layer removed. I've kept the structure of the patch series otherwise intact, to facilitate range-diffing (use git range-diff -w --creation-factor=80 development  e8fc54a 91a7ce9)
The merge conflict should resolve itself once #4348 is merged to development.

I've rebased this PR on top of development, to fix a merge conflict.

@gabor-mezei-arm please review the latest version, thanks.

Due to the change in merge strategy / merge of development_3.0 into development, we'll need a forward-port for this PR.

Please create the PR for development now.


crunchyroll premuim videos can't download

[Crunchyroll] 715673: Downloading webpage
ERROR: This is a sample clip. To watch the full video, start a free trial today!; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
plz fix

Carefully read new issue template and provide all requested information.


provide docs using sphinx

The code gained a level of complexity that requires a better way of documentation.

Implemented with PR #71


[GAE-Java] Fix GetMessage bug

What do these changes do?

Related issue number

Fix Bug in GAE Java SDK GetMessage.

Codecov Report

Merging #2079 (62cf066) into main (3af3e84) will increase coverage by 21.02%.
The diff coverage is n/a.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2079       +/-   ##
===========================================
+ Coverage   43.90%   64.92%   +21.02%
===========================================
  Files          87       89        +2
  Lines        9813     9850       +37
===========================================
+ Hits         4308     6395     +2087
+ Misses       5505     3455     -2050

Impacted Files
Coverage Δ

...aphscope/tests/kubernetes/test_resource_builder.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...on/graphscope/tests/kubernetes/test_demo_script.py
0.00% <0.00%> (-91.75%)
:arrow_down:

python/graphscope/deploy/kubernetes/utils.py
11.90% <0.00%> (-57.62%)
:arrow_down:

python/graphscope/deploy/kubernetes/cluster.py
23.19% <0.00%> (-50.96%)
:arrow_down:

python/graphscope/tests/unittest/test_java_app.py
49.33% <0.00%> (-50.67%)
:arrow_down:

...thon/graphscope/tests/kubernetes/test_with_mars.py
0.00% <0.00%> (-44.83%)
:arrow_down:

python/graphscope/analytical/app/java_app.py
24.36% <0.00%> (-44.68%)
:arrow_down:

python/graphscope/interactive/query.py
41.12% <0.00%> (-38.71%)
:arrow_down:

...n/graphscope/deploy/kubernetes/resource_builder.py
30.59% <0.00%> (-25.95%)
:arrow_down:

python/graphscope/client/rpc.py
76.85% <0.00%> (-12.97%)
:arrow_down:

... and 46 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 3af3e84...62cf066. Read the comment docs.


组件设置不能保存，重启软件后会恢复默认设置

Microsoft PowerToys version
0.53.3
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
组件设置不能保存，重启软件后会恢复默认设置
✔ Expected Behavior
修复
❌ Actual Behavior
组件设置不能保存，重启软件后会恢复默认设置
Other Software
No response

Duplicate of #15450

Thanks for reporting this. This issue is a duplicate.
I'm linking this issue to #15450 to centralize the discussion thread for tracking.
Thanks for your help to make PowerToys a better piece of software!


[FR] json output for proxy list

Thanks for this awesome project! I want to use clashctl in some of my scripts, but parsing the output of proxy list is a pain.
Maybe we can add a json output option for easy parsing. e.g. with a schema like:
{
  "name": "proxygroup1",
  "type": "Selector",
  "delay": null,
  "subproxies": [
    "proxy1",
    "proxy2",
    "proxygroup2"
  ]
}

Sorry for such a late response. Currently I'm not using clash nor clashctl anymore, which defeats the single most important reason to continue adding features for this project. I'm still willing to accept PR's and new contributors though, so if you think this is necessary, please kindly write a PR and I will be more than happy to review and merge it.


cmd/go: go test -c does not apply specified gcflags to the test package

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version devel +5f29a7a Mon Nov 20 20:29:43 2017 +0000 linux/amd64

What did you do?
go get github.com/aarzilli/testflags
cd $GOPATH/src/github.com/aarzilli/testflags
go clean -cache && go test -c -gcflags '-N -l'

What did you expect to see?
flags -N -l applied to the test package (i.e. the one defined in main_test.go)
What did you see instead?
The flags are applied to github.com/aarzilli/testflags but not to the test package.

Indeed. Will fix.


Allow "clone", "pour" etc to operate on other scopes

For example "pour air" would make a new line, "pour token air" would insert space and leave cursor on same line, "pour arg air" would insert comma and leave cursor after. Similarly, "clone air" would clone the line, but "clone token air", "clone arg air" etc would operate with the corresponding delimiters
Using action preference selection type
Springs from #230
Will rely on #202
Should we also handle "drop" / "float" / "puff" the same way?  So eg "float argue air" would insert a ,  before the argument

@AndreasArvidsson So I think the only thing missing from #672 here is "float", "drop" and "puff". Not saying we should impl those in that PR—it's already massive. But maybe we should file those into a follow-up issue?


fix: yaml unmarshal does not implement the interface correctly

The generated UnmarshalYAML method currently doesn't implement the unmarshal interface defined in the YAML package and therefore never invoked while working with it.
Since I've found some tests related to the 2 versions of the YAML package i did implement the obsolete one which is supported by both.

After discussing the matter on slack, we agreed upon dropping yaml.v2 support and only support v3. We also reworked tests to cover generated code unmarshalling.


Suspending / Resuming capture to reduce permanent CPU load

Required Info

Camera Model
D435i

Firmware Version
Signed_Image_UVC_5_12_2_100.bin

Operating System & Version
{Win 10

Platform
Embedded PC, Celeron N3160 CPU

SDK Version
2.32.1

Language
C++

Segment
Machine Control/computer vision

Issue Description
On the embedded systems of our customer, we run into thermal issues when we permanently process the 3D image of the D435i. We capture at 1280x720 but reduce on 640x30px using the decimation_filter as suggested in the rs-measure example.
So we thought about activating/deactivating the camera by starting the pipe only if needed. But this takes ~3s which is inacceptable for our use case. So we tried to block the processing_thread with a std::condition_variable. This did not help either, the CPU load was as high as before (100%).
From our application, we know when we want to capture (normally only for some seconds) so a fast resume/suspend mechansim would be great for us.
The second best solution would be to throttle down the frame rate and give the CPU some time to enter its sleep states.
Regards
Florian

If you used poll_for_frames then you could manually decide when to put the CPU to sleep and the sleep duration.
https://github.com/IntelRealSense/librealsense/issues/2422#issuecomment-423254709
If you have thermal issues and it is an embedded system (suggesting that a Module Kit circuit board version of the camera is being used) then a better heat-sink component might also be able to be designed using the guidelines in the 400 Series data sheet document.
https://dev.intelrealsense.com/docs/intel-realsense-d400-series-product-family-datasheet
Page 82 of the current edition of the data sheet contains heat sink design guidance.

Hello,
thanks for your help. No we use the cased D435i since the machine is quite big. So space is not an issue. But the computer housing is ready designed and it is quite difficult for our customer to change things on the mechanics at this time.
Yes we use poll_for_frames as in the rs-measure example. And now we block the processing_thread with an std::condition_variable before polling, this works sufficently for us. Thanks a lot.
Can't recall why it did not work on the first try anyway.
Thanks a lot & regards
Florian

You are very welcome.  :)
You may be able to shave some further % off the CPU usage by making use of a feature called GLSL Processing Blocks to offload some of the CPU work onto a GPU, though it may be ineffective to do so on low-power systems.
https://github.com/IntelRealSense/librealsense/pull/3654

Is the GPU of our Celeron N3160 (I think it's PowerVR based) supported for GLSL? Is it useful for this CPU?

GLSL is "vendor neutral", so the brand-name of the GPU should not matter, unlike CUDA offloading that only works with Nvidia GPUs.
The in-built graphics of the Celeron N3160 look pretty good, according to Intel's ARK processor details site:

@sans-ltd You are currently skipping frames using some logic. The data is still being transferred from device to your CPU and this also uses some cpu. Why don't you reduce the frame rate in the first place? Although too low framerate can blur the image. But currently if you are using say 30 FPS and skipping alternate frames, then using 15 FPS solves our problem, without a need for using frames skip logic.

Case closed due to no further comments received.


thedailybeast.com

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2021.06.06
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single video: https://www.thedailybeast.com/john-lithgow-nails-total-embarrassment-rudy-giuliani-on-colbert

Description
Plays OK on Firefox.  youtube-dl reports "ERROR: Unsupported URL"

That's just the url to the article. The HLS url is https://videos-fms.jwpsrv.com/0_6157393b_0x123780d0dd8442a8fc4e468427edd9b53b79ae02/content/conversions/6QNxZHni/videos/ewOG4zF8-25609414.mp4.m3u8.
The following should work,
youtube-dl https://videos-fms.jwpsrv.com/0_6157393b_0x123780d0dd8442a8fc4e468427edd9b53b79ae02/content/conversions/6QNxZHni/videos/ewOG4zF8-25609414.mp4.m3u8

Sadly the plain React page that yt-dl would download from the Beastly URL doesn't mention the video URL nor any of the ID-like elements in it.


I have a problem with Nested Navigation Example

https://user-images.githubusercontent.com/22948486/134266778-2e5e13d4-7a6a-46d1-a437-365d6f28d168.mov
Above is the demo running directly, the animation is not perfect. I tried to fix the navigation animation problem, but it didn't work.
this is my code.
`
import 'package:beamer/beamer.dart';
import 'package:flutter/material.dart';
import 'locations.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  final routerDelegate = BeamerDelegate(
    locationBuilder: (routeInformation, _) => HomeLocation(routeInformation),
    transitionDelegate: NoAnimationTransitionDelegate(),
    beamBackTransitionDelegate: NoAnimationTransitionDelegate(),
  );

  @override
  Widget build(BuildContext context) {
    return MaterialApp.router(
      debugShowCheckedModeBanner: false,
      routeInformationParser: BeamerParser(),
      routerDelegate: routerDelegate,
    );
  }
}

class NoAnimationTransitionDelegate<T> extends TransitionDelegate<T> {
  @override
  Iterable<RouteTransitionRecord> resolve({
    required List<RouteTransitionRecord> newPageRouteHistory,
    required Map<RouteTransitionRecord?, RouteTransitionRecord>
        locationToExitingPageRoute,
    required Map<RouteTransitionRecord?, List<RouteTransitionRecord>>
        pageRouteToPagelessRoutes,
  }) {
    final results = <RouteTransitionRecord>[];

    for (final pageRoute in newPageRouteHistory) {
      if (pageRoute.isWaitingForEnteringDecision) {
        pageRoute.markForAdd();
      }
      results.add(pageRoute);
    }

    for (final exitingPageRoute in locationToExitingPageRoute.values) {
      if (exitingPageRoute.isWaitingForExitingDecision) {
        exitingPageRoute.markForRemove();
        final pagelessRoutes = pageRouteToPagelessRoutes[exitingPageRoute];
        if (pagelessRoutes != null) {
          for (final pagelessRoute in pagelessRoutes) {
            pagelessRoute.markForRemove();
          }
        }
      }

      results.add(exitingPageRoute);
    }
    return results;
  }
}

`
this is flutter doctor.
  $ flutter doctor
  Doctor summary (to see all details, run flutter doctor -v):
  [✓] Flutter (Channel stable, 2.2.1, on macOS 11.4 20F71 darwin-x64, locale
      zh-Hans-CN)
  [✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
  [✓] Xcode - develop for iOS and macOS
  [✓] Chrome - develop for the web
  [✓] Android Studio (version 4.1)
  [✓] VS Code (version 1.60.1)
  [✓] Connected device (2 available)

  • No issues found!

This only occurs with Cupertino, the animation overlaps the widgets behind it, I worked around the problem with a wrapper, it's not perfect and it must have a better way to fix, but it works, just wrap Beamer widget with this:
import 'package:flutter/material.dart';

class BeamerWrapper extends StatelessWidget {
  const BeamerWrapper({required this.child, this.color, Key? key}) : super(key: key);

  final Widget child;
  final Color? color;

  @override
  Widget build(BuildContext context) {
    var currentPageTransition = Theme.of(context).pageTransitionsTheme.builders[Theme.of(context).platform];

    if (currentPageTransition is CupertinoPageTransitionsBuilder)
      return Container(
        decoration: BoxDecoration(
          color: color,
          boxShadow: [
            BoxShadow(
              color: Colors.black.withOpacity(0.25),
              spreadRadius: 8,
              blurRadius: 16,
              offset: Offset(-3, 0),
            ),
          ],
        ),
        child: ClipRRect(
          child: child,
        ),
      );
    else
      return child;
  }
}

The solution should also be setting the transitionDelegate: const NoAnimationTransitionDelegate() for specific Beamer.

When I tried this example today, the animation still has the bug shown by @MisariLin.  When @slovnicki closed it, I guess it was working?  Is it broken again from a change in Beamer?

Hey @jpangburn
I closed the issue because solutions provided by @talski and me work, but you're right - the example should have been updated as well. I pushed a combination of suggested 2 solutions and now it should work as expected; https://github.com/slovnicki/beamer/commit/d5a9460d6427eb0b45b75836cb9023bbcf4a52ec
If you look at the commit, you can see 2 changes;

Wrapping Beamers in ClipRRect to avoid shadows and prevent inner-most slide transition overflow
Setting NoAnimationTransitionDelegate for the 2nd level (if counting the MaterialApp.router) Beamer to avoid slide transition on the inner navigation menu.

That's WAY nicer than slapping NoAnimationTransitionDelegates all over!  With just those everywhere you end up with the inner navigation menu not having any animation, or if you put it on the top only then without the ClipRRect you get ugly transition overflow.  But your solution lets the inner navigation animate nicely 👏


No 'version' key in the manifest - please report this to the maintainer.

i noticed this today in the home assistant logs:
2021-05-15 14:11:09 ERROR (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'homee'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'homee'

Thank you for opening the issue! I added the 'version' key and a script to auto-increment the version number for new releases. However, GitHub is currently not running any CI jobs for whatever reason. Once the jobs run again there should be a new release with the fixed manifest.


Why only the log file of rank > 0 is created?

❓ Questions
I'm trying to debug a problem with nccl, but I can only see the worker_1.log output file.
I have two gpus and I'm trying to see the logs, but I can only see the log of one, is this check really necessary?
TIA

worker_1.log is actually the log file of the second worker. When running locally (eg with dora run), the output of the first worker is directly shown in the shell. It is not stored in any file.

Got it, makes sense, thanks


test: cypress -Updated tests for js to ts migration for priority tests

Updating tests from js to ts for flaky fix migration.

/ok-to-test

/ok-to-test

/ok-to-test


Translation fr

Drone translation
add missing translation key (drone) like unity for french translation
rework on fr translation from users feedbacks

I have one suggestion, please move the unit in localization from SFRPG.DroneSheet.Speed into a separate category. Something like SFRPG.Units.Feet, SFRPG.Units.Metric, etc.
This will allow us to use units and unit conversions in other places than just the DroneSheet, even if it's only the drone sheet that supports it.

Its done i have made the modification with "SRFPG.Unity.Speed"

Move to SRFPG.Units.Speed

You missed changing it on ja.json, also, could you move SFRPG.Units.Speed to above the SFRPG.LocalizationTerminator field?

Its ok now. ja translation added, and i have change the position of the new translation key above the SFRPG.LocalizationTerminator field


How to change Label position (left/right) and menu buttons popup (Up/Down) dynamically

Hi,
Thank you so much for wonderful library.
How to change Label position to (lef/right) dynamically.
and how to change the menu buttons popup orientation (Up/Down) dynamically.
Please let me know.
Thank you.

+++

@ayhansalami Can you please give sample code or any explanation about this


Don't pin versions in requirements.txt

Per https://packaging.python.org/discussions/install-requires-vs-requirements/#install-requires,
featuretools is breaking convention by pinning specific versions of all its dependencies in install-requires: "It is not considered best practice to use install_requires to pin dependencies to specific versions"
Specifically, this is causing a dependency conflict when I try to install the following packages with pipenv:
pipenv --python 2.7
pipenv install numpy scipy pandas scikit-learn tensorflow featuretools

Thanks for pointing this out. Let me look into the versions we can allow for each of the dependencies and update this as soon as possible.

@PaulHobbs I just put up #53. However, I still need to look into the minimum versions we can support. Can you share which packages / version you were having conflicts with? That would help as starting point for me to test. Thanks!

Hey Max,
Sorry I’m on my phone at the moment, but the conflict was between pandas
0.23.something and pandas 0.22.something (which featuretools requires). You
should be able to reproduce it by installing the latest version of
virtualenv and pipenv and running the commands I listed.
On Tue, Dec 26, 2017 at 20:12 Max Kanter<EMAIL_ADDRESS>wrote:

@PaulHobbs https://github.com/paulhobbs I just put up #53
https://github.com/Featuretools/featuretools/pull/53. However, I still
need to look into the minimum versions we can support. Can you share which
packages / version you were having conflicts with? That would help as
starting point for me to test. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Featuretools/featuretools/issues/52#issuecomment-354048924,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK_lIdGSlZAA50p0nJeAy2UD-7c03Ufks5tEcOcgaJpZM4RNE_Z
.

having the same issue - the main conflict is that i want to use pandas 0.21.* and featuretools is forcing 0.20.3.
It also uninstalled my existing cloudpickle (downgraded version from 0.5.2) and future (upgraded from 0.15.2).

@davidas85 thanks for the additional info. I have a PR #53 unpinning the requirements if you want to instal it directly. For some reason, tests are failing on Python 3.4, but pass on 2.7, 3.5, and 3.6.


Add commit hook to run eslint.

Already done on every PR, can we close this @ignasposka?
https://github.com/pets-oss/pets-back/blob/e4407b9ca4a1c091197d21b39063523f635ca993/.github/workflows/pull-request.yml#L44-L45
https://github.com/pets-oss/pets-back/blob/e4407b9ca4a1c091197d21b39063523f635ca993/package.json#L18

I wanted that commit hook would prevent commit locally in case of eslint errors.