Fill type data from multiple services

Hi Bramble,
Working with shared types, I was able to get multiple services to fill the same type when it's in the root query, but could not get this to work when the object is in an inner query.
For example assume I have a "tasks" service and a "profiles" service, and each task can have an "owner" field which is a Profile.
Given the following schema for tasks:
directive @boundary on OBJECT | FIELD_DEFINITION

type Query {
  tasks(done: Boolean): [Task]
  task(id: String): Task
  service: Service!
  tasks__profile(id: ID!): Profile @boundary
}

type Profile @boundary {
  id: ID!
}

type Task {
  _id: String
  text: String
  done: Boolean
  owner: Profile
}

type Service {
  name: String! # unique name for the service
  version: String! # any string
  schema: String! # the full schema for the service
}

And this schema for a Profile service:
directive @boundary on OBJECT | FIELD_DEFINITION

type Query {
  service: Service!
  profile(id: ID!): Profile @boundary
  someone: Profile
}

type Profile @boundary {
  id: ID!
  first_name: String
  last_name: String
}

type Service {
  name: String! # unique name for the service
  version: String! # any string
  schema: String! # the full schema for the service
}

I have no problem using the someone query to get a profile and fill its fields from both services, but when I try to read the tasks and data about their owners such as:
query {
  tasks {
    text
    owner {
       id
       first_name
    }
  }
}

I will get just "null" as the result data.
If I remove first_name field from the query everything will work and I will get the correct id of the owner, so I assume tasks service works ok.
Is there a way to get bramble gateway to fill inner owner query from a different service?

Hey @ynonp, your schema looks valid to me and the query should work. Is Bramble logging out any error? Does the query response give out any error?

If I remove first_name field from the query everything will work and I will get the correct id of the owner, so I assume tasks service works ok.
OK, but what about the profile service? Is it getting called? What is it responding with?

Closing this for now due to lack of activity. @ynonp Feel free to reopen if you'd like additional assistance.


Move host and port for groups API inside org_metadata_api config section

Host and port variables when configuring the org_metadata_api_endpoint collide with the the ones used for central.
https://github.com/CartoDB/cartodb/blob/4924-Group_metadata_API_endpoints/app/models/user.rb#L2613-L2615
We should move those inside org_metadata_api like username and password.

Merged into #4924 branch.


CHANGED: rendering of trace

Removed the glyphs
Removed the colored background
Color the Grammar element depending on the match succes or failure
Inline the matched string with the Grammar element on success
makes the output almost alf the vertical size
makes it easier to match the element to the matched string

In addition to being useful, these changes were needed for my own desired addition of toggling tracing at runtime.
My submitted pull request (https://github.com/jnthn/grammar-debugger/pull/41) incorporates these changes, though did not preserve nkh's history due to lack of patience in fixing a complex merge.
Hence this pull request can be closed.


Distutils is to be removed from the standard library in Python 3.12

In accordance with PEP 0632, distutils will be removed from the Python 3.12 standard library.
In order to retain compatibility with Python 3.12, it may be sufficient to add a runtime dependency on setuptools. See the relevant Fedora Linux python-devel mailing list thread; regarding potential incompatibilities, see https://github.com/pypa/setuptools/issues/3532.

It is not a hard runtime dependency IMO. The /bin/argparse-manpage script doesn't rely on distutils at all. Distutils are only needed for the setup.py command overrides (supported by this project).  So should our users specify the setuptools as the builddep for their projects?

It seems like this project imports from distutils:
https://github.com/praiskup/argparse-manpage/blob/28151c24bfc80d33140b2fcf69400ba5fde907df/build_manpages/build_manpages.py#L8-L9
If build_manpages isn't a "core" part of this, maybe it needs to have extras dependendencies?

In that case, you would do something like this in setup.py:
https://setuptools.pypa.io/en/latest/userguide/dependency_management.html#optional-dependencies
setup(
    ...,
    extras_require={
        "build-manpages": ['setuptools;python_version>="3.12"'],
    },
)

And in build_manpages.py:
try:
    from distutils.core import Command
    from distutils.errors import DistutilsOptionError
except ImportError:
    raise ImportError(
        'To use the build_manpages tool on Python 3.12+, '
        'you need to install argparse-manpage[build-manpages].'
    )

And in the README, you recommend adding argparse-manpage[build-manpages] to pyproject.toml's [build-system] requires.

I think you’ll find that even the CLI tool requires distutils, perhaps accidentally, and that regardless of intent, distutils currently still functions as a hard dependency in practice.
In v3, as released on PyPI, build_manpages/cli.py imports from build_manpages.build_manpage…
https://github.com/praiskup/argparse-manpage/blob/34017d1865a4c97ddb13a1e80333bfb4ace93351/build_manpages/cli.py#L10
…which imports distutils:
https://github.com/praiskup/argparse-manpage/blob/34017d1865a4c97ddb13a1e80333bfb4ace93351/build_manpages/build_manpage.py#L12-L13

In the unreleased main, this does’t seem to be the case, but distutils still gets imported, because importing build_manpages/cli.py means build_manpages/__init__.py gets imported, and that imports build_manpages/build_manpages.py…
https://github.com/praiskup/argparse-manpage/blob/28151c24bfc80d33140b2fcf69400ba5fde907df/build_manpages/__init__.py#L7
…and that still unconditionally imports distutils…
https://github.com/praiskup/argparse-manpage/blob/28151c24bfc80d33140b2fcf69400ba5fde907df/build_manpages/build_manpages.py#L8-L9
…so one still sees:
PYTHON=python3.11 PYTHONPATH=$PWD PYTHONWARNINGS=d ./argparse-manpage

 !! running argparse-manpage from git, this is not supported PYTHON=python3.11!!

/home/ben/src/argparse-manpage/build_manpages/build_manpages.py:8: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
  from distutils.core import Command

Thank you for the detailed analysis.
I plan a release soon, so let's keep v3 aside now.

In the unreleased main, this does’t seem to be the case, but distutils still
gets imported, because importing build_manpages/cli.py means
build_manpages/init.py gets imported, and that imports
build_manpages/build_manpages.py…

Hm, importing cli.py really implies importing init.py, and thus distutils?
I'd like to do something like #69, but having even the dep on setuptools
in the script seems bad.  Is there a way around it?

Hm, importing cli.py really implies importing init.py

Always.

You can wrap the entire thing that uses the classes in the try-except block from my comment.


Set permissions for GitHub actions

Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests
Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.
Signed-off-by: naveensrinivasan<EMAIL_ADDRESS>

Thank you very much Naveen @naveensrinivasan, it's an honour to merge a pull request from you 🙏.


Total Commander

Microsoft Reviewers: Open in CodeFlow

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

Sorry, didn't search all ... There is already a tcmd manifest.


Cleanup empty logs from third party libraries

This is in response to: https://github.com/terrapower/armi/issues/373
I decided to fix the problem (of lots of empty third-party logs) in two directions:

Added the delay=True to all of our custom logging.FileHandlers, to make our log file creation more lazy.
Removed all the empty log files that still exist at the end of a run.

Doing (1) meant doing some re-org of our concatLogs() function, but that's fine.

I'm happy to merge this as-is, but did you want to play around with just the delay=True?

I can play with that again, sure.  We have just hit so many edge cases with this logging, and the delay=True is so poorly documented I didn't want to risk another edge case.
But, sure, I'll play with it again.


"Delete If Migration Needed" support

DBFlow Version: 3.1.1
Issue Kind: Question
Description:
Is there a way to have DBFLow automatically recreate the DB if a migration is needed? During beta testing it is not imperative that our data is kept, and I would like to avoid forcing users to uninstall and reinstall if possible.
Is this already possible? I have gone over the docs and could not find reference to such a thing, and my google foo is coming up empty.

create a custom migration that deletes the full db, and reopens it.

This should help (https://github.com/Raizlabs/DBFlow/blob/master/usage2/Migrations.md)


hack: fix some bugs in code generation

the code generator now insists that types MUST be defined in a file called types.go
we also need to generate openapi
wipe the generated code at the start of codegen, so we don't accidentally preserve old state

(note that this doesn't affect consumers of tilt-apiserver, this is just example / sandbox code)


add gem name for use with bundler

I feel like at this point people know how to install gems.

I had to look into formulaic.gemspec to make sure the gem was not named different. e.g. formulaic-thoughtbot

Fixed in be71be7


Shape mismatch with NeuralNetworkRegressor + SamplerQNN #608

Technical discussion for #608

 Shape mismatch with NeuralNetworkRegressor + SamplerQNN #608


TUN TAP drivers

Hello,
I want to use VPN on my PYNQ board. As there are no TUN module present in the default kernel provided http://pynq.readthedocs.io/en/v2.1/getting_started.html#microsd-card-setup
So I tried to re-compiled the kernel with a line, CONFIG_TUN=m added to the file /PYNQ/sdbuild/boot_configs/Pynq-Z1-defconfig/kernel.config. However, the compiled kernel also doesn't has any TUN module.
xilinx@pynq:~$ modinfo tun modinfo: ERROR: Module tun not found.
Can someone tell what am I doing wrong ?
Kind regards,
Gourav

By using CONFIG_TUN=m you've compiled a kernel module which needs to be placed in the filesystem. In the build directory of your kernel you should find tun.ko which you can copy on to the board and load into the kernel using insmod.
Alternatively you may be able use CONFIG_TUN=y and update the uImage file in the boot partition which will compile TUN directly into the kernel.

Now I am able to load the tun.ko
Thank you for the help.


"Show Source" button on md preview throws error in 1.21

VSCode Version: Insiders dated 2/28
OS Version: Any

Steps to Reproduce:

Open preview for a markdown file
Click on the "Show Source" button on the top right corner of the preview

Expected: The editor with the source of the md preview gets focus
Actual: Notification: cannot open vscode-markdown-preview:2. Detail: no provider for vscode-markdown-preview:2
Does this issue occur when all extensions are disabled?: Yes
This doesnt happen in 1.20

Duplicate of #44523


Add feature - Avoid monolog sending email programatically

As stated in https://stackoverflow.com/questions/53923774/how-to-avoid-monolog-sending-email-programatically, it seems that is NOT possible to stop Monolog sending email programmatically. We can setup the error level for which we want to send emails, we can update the Response but I haven't found any way to make Monolog to stop sending an email for specific reasons.
What I am looking for is a kind of stopPropagation (this can be done on the event but then it stops the Exception) just for the email.
I have a set of urls that I know they are called and throw an Exception, but I don't want to receive an email. This set of urls is stored in bdd so I cannot set them in a kind of config.yml.
Don't know where to begin to make an eventual PR.

This is IMO about composing the handler chain correctly. You can wrap the mailer handler with a FingersCrossedHandler for example that has a custom activation strategy set which will look at the request and not trigger for those routes.. Or you could write a custom handler that filters the messages based on whatever. Endless possibilities, but for custom needs you need a little bit of custom code.

Thanks about your answer. I'm not against custom code as I did a bundle, but I have to understand how and what to do, and here I don't...
The thing is that the routes are unknown as stored in a database, when they are found in the database the process in monolog has already started and it seems that I can't stop it. I haven't found any way to say to monolog (event or whatever), don't go further. Moreover, I would like to integrate it in the bundle and not in the configuration of the app, as the goal is to work as is, not to add configuration.
But thanks again for your answer, and the work you provide to OSS.

Well I don't know enough about your project to really say, but it sounds to me like you could tell your custom handler to not go further whenever you have your route information. Or to wait/buffer until you have the route info and then tell it to start forwarding log records to the handlers below. Still probably requires some config changes to the app though that's for sure..

Thanks again for your time.
It looks too complicated for me, what I was looking for is a kind of method stopPropagation on GetResponseForExceptionEvent because I use a listener on kernel.exception.
As a solution I finally ended in throwing a BadRequestHttpException for the ignored case. If you want to have a look the bundle is at https://github.com/975L/ExceptionCheckerBundle and the exact line is at https://github.com/975L/ExceptionCheckerBundle/blob/dcbc169c89e97bb23244fd23fcc69494155e0d08/Listener/ExceptionListener.php#L169.
It's not really as I want it to be, but it works...


[18.09] Ruby Ver Bump (#10040)

Proposed changes
Cherry-pick #10040
Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 3dbf1ca910d95de366cf1fb5dec71af3c0b57fdc
https://deploy-preview-10041--docsdocker.netlify.com


Add tests which validate the quality of the produced SQL

This has been discussed on Discord a few times.
Currently we test that the SQL produced from a PRQL query s what we expect. But it's possible that the SQL we expect isn't correct SQL, and a higher level of testing would confirm that. It could even assert the result we expect from a query to a DB.
A few levels I could imagine this on:

Validate SQL with a tool — Is there a library that validates SQL for various DBs? That would be the simplest (it could be in our cargo tests).
Validate SQL with a DB — we could spin up a small DB in a test script and execute queries against it.
Validate query results — assert that the result of a query is expected.

Closed by @aljazerzen !


Path to a stable release?

What are your plans for a stable release? Will you be publishing signed tarballs?

I'm also curious about this. I would like to package cage for openSUSE.

Hi guys,
Sorry for the late reply. I just started a new job, moved into a new apartment and my brother was over for a visit, so I didn't have a lot of time to work on Cage.
I have tagged some issues that I'd like to make it in 1.0 (see the milestone), I think all of these are critical for a proper stable release. It'd be nice if keyboard support could get in as well, but AFAIK there is still ongoing work regarding this in Wayland. @ddevault it would be nice if you have more information on this.
The only other issues that I left out are those regarding animations and a rendering optimization. Re: animations, I don't think this is important just yet and I suspect it to be quite a lot of work (I have never done such a thing before), but if someone with more experience steps up and either guide me or open a PR I'd be more than welcome to include it in 1.0.
That leaves the rendering optimization. Since I don't expect people to use Cage with more than a handful of windows open, I don't think that the optimization (to render only the topmost window and any of its dialogs) provides a significant benefit, so I'm oke with leaving it out until later.

I noticed I had created a 0.1 milestone as well, which I had forgotten. I'm working on getting a CI going for Cage (on Sourcehut, thanks to Drew's generous offer) at which point I'll release a 0.1 version to see how I can do signed releases. Any pointers are welcome! :)

You can get some progress on virtual keyboards. Purism's virtboard should work.

It requires layer-shell though, doesn't it? Not opposed to adding it, but Cage currently doesn't support it.

Ah, so it does.

I packaged 0.1 for openSUSE. So far it's only in a private repo. Will publish it to a devel repo soon, but wait for official repos until a stable release is out.

Since you released 0.1 it might be good to also adapt the version in the meson file, I created #60 for this.

Thanks for catching this, and thanks for packaging Cage!
Since the path to a stable release is defined, I'm closing this issue. Feel free to reopen it or create a new issue if anything is unclear.


Cannot compile because 'std_tuple.hpp' file not found. Solution included.

Boost 1.57.0
Mac OS X 10.11.4
Xcode 7.3.1

Console output from make
johndoesMac:cpp-netlib-0.12.0-final johndoe$ cmake --version
cmake version 3.5.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).
johndoesMac:cpp-netlib-0.12.0-final johndoe$ cd
johndoesMac:~ johndoe$ mkdir ~/cpp-netlib-build
johndoesMac:~ johndoe$ cd cpp-netlib-build/
johndoesMac:cpp-netlib-build johndoe$ cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ $HOME/cpp-netlib
-- The C compiler identification is AppleClang <IP_ADDRESS>30031
-- The CXX compiler identification is AppleClang <IP_ADDRESS>30031
-- Check for working C compiler: /usr/bin/clang
-- Check for working C compiler: /usr/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/clang++
-- Check for working CXX compiler: /usr/bin/clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Boost version: 1.57.0
-- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing:  OPENSSL_INCLUDE_DIR)
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Found PythonInterp: /usr/bin/python (found version "2.7.10")
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/johndoe/cpp-netlib-build
johndoesMac:cpp-netlib-build johndoe$ cd ~/cpp-netlib-build
johndoesMac:cpp-netlib-build johndoe$ make
/usr/local/Cellar/cmake/3.5.1/bin/cmake -H/Users/johndoe/cpp-netlib -B/Users/johndoe/cpp-netlib-build --check-build-system CMakeFiles/Makefile.cmake 0
/usr/local/Cellar/cmake/3.5.1/bin/cmake -E cmake_progress_start /Users/johndoe/cpp-netlib-build/CMakeFiles /Users/johndoe/cpp-netlib-build/CMakeFiles/progress.marks
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f CMakeFiles/Makefile2 all
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/build.make libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/depend
cd /Users/johndoe/cpp-netlib-build && /usr/local/Cellar/cmake/3.5.1/bin/cmake -E cmake_depends "Unix Makefiles" /Users/johndoe/cpp-netlib /Users/johndoe/cpp-netlib/libs/network/src /Users/johndoe/cpp-netlib-build /Users/johndoe/cpp-netlib-build/libs/network/src /Users/johndoe/cpp-netlib-build/libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/DependInfo.cmake --color=
Scanning dependencies of target cppnetlib-client-connections
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/build.make libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/build
[  1%] Building CXX object libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o
cd /Users/johndoe/cpp-netlib-build/libs/network/src && /usr/bin/clang++   -DASIO_HEADER_ONLY -DBOOST_NETWORK_DEBUG -DBOOST_SPIRIT_THREADSAFE -DBOOST_TEST_DYN_LINK -I/usr/local/include -I/Users/johndoe/cpp-netlib/deps/asio/asio/include -I/Users/johndoe/cpp-netlib  -Wall -ftemplate-depth=256 -std=c++11 -stdlib=libc++ -g   -o CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o -c /Users/johndoe/cpp-netlib/libs/network/src/client.cpp
In file included from /Users/johndoe/cpp-netlib/libs/network/src/client.cpp:13:
In file included from /Users/johndoe/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:19:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_io_object.hpp:19:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/io_service.hpp:712:
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/impl/io_service.hpp:80:61: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
  ASIO_COMPLETION_HANDLER_CHECK(CompletionHandler, handler) type_check;
                                                            ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/impl/io_service.hpp:113:61: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
  ASIO_COMPLETION_HANDLER_CHECK(CompletionHandler, handler) type_check;
                                                            ^
In file included from /Users/johndoe/cpp-netlib/libs/network/src/client.cpp:13:
In file included from /Users/johndoe/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:19:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:20:
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket.hpp:740:57: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_CONNECT_HANDLER_CHECK(ConnectHandler, handler) type_check;
                                                        ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket.hpp:1582:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_WAIT_HANDLER_CHECK(WaitHandler, handler) type_check;
                                                  ^
In file included from /Users/johndoe/cpp-netlib/libs/network/src/client.cpp:13:
In file included from /Users/johndoe/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:19:
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:984:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_WAIT_HANDLER_CHECK(WaitHandler, handler) type_check;
                                                  ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:1098:55: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_ACCEPT_HANDLER_CHECK(AcceptHandler, handler) type_check;
                                                      ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:1209:55: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_ACCEPT_HANDLER_CHECK(AcceptHandler, handler) type_check;
                                                      ^
In file included from /Users/johndoe/cpp-netlib/libs/network/src/client.cpp:13:
In file included from /Users/johndoe/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:20:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket_iostream.hpp:24:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_socket_streambuf.hpp:31:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/deadline_timer.hpp:24:
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_deadline_timer.hpp:507:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_WAIT_HANDLER_CHECK(WaitHandler, handler) type_check;
                                                  ^
In file included from /Users/johndoe/cpp-netlib/libs/network/src/client.cpp:13:
In file included from /Users/johndoe/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:21:
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_stream_socket.hpp:351:53: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_WRITE_HANDLER_CHECK(WriteHandler, handler) type_check;
                                                    ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_stream_socket.hpp:404:53: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_WRITE_HANDLER_CHECK(WriteHandler, handler) type_check;
                                                    ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_stream_socket.hpp:561:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_READ_HANDLER_CHECK(ReadHandler, handler) type_check;
                                                  ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_stream_socket.hpp:615:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_READ_HANDLER_CHECK(ReadHandler, handler) type_check;
                                                  ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_stream_socket.hpp:724:53: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_WRITE_HANDLER_CHECK(WriteHandler, handler) type_check;
                                                    ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/basic_stream_socket.hpp:837:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
    ASIO_READ_HANDLER_CHECK(ReadHandler, handler) type_check;
                                                  ^
In file included from /Users/johndoe/cpp-netlib/libs/network/src/client.cpp:13:
In file included from /Users/johndoe/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:25:
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/ip/basic_resolver.hpp:163:44: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
        ResolveHandler, handler, iterator) type_check;
                                           ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/ip/basic_resolver.hpp:256:44: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
        ResolveHandler, handler, iterator) type_check;
                                           ^
In file included from /Users/johndoe/cpp-netlib/libs/network/src/client.cpp:13:
In file included from /Users/johndoe/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:14:
In file included from /Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/write.hpp:918:
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/impl/write.hpp:700:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
  ASIO_WRITE_HANDLER_CHECK(WriteHandler, handler) type_check;
                                                  ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/impl/write.hpp:726:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
  ASIO_WRITE_HANDLER_CHECK(WriteHandler, handler) type_check;
                                                  ^
/Users/johndoe/cpp-netlib/deps/asio/asio/include/asio/impl/write.hpp:923:51: warning: unused typedef 'type_check'
      [-Wunused-local-typedef]
  ASIO_WRITE_HANDLER_CHECK(WriteHandler, handler) type_check;
                                                  ^
19 warnings generated.
[  2%] Linking CXX static library libcppnetlib-client-connections.a
cd /Users/johndoe/cpp-netlib-build/libs/network/src && /usr/local/Cellar/cmake/3.5.1/bin/cmake -P CMakeFiles/cppnetlib-client-connections.dir/cmake_clean_target.cmake
cd /Users/johndoe/cpp-netlib-build/libs/network/src && /usr/local/Cellar/cmake/3.5.1/bin/cmake -E cmake_link_script CMakeFiles/cppnetlib-client-connections.dir/link.txt --verbose=1
/usr/bin/ar qc libcppnetlib-client-connections.a  CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o
/usr/bin/ranlib libcppnetlib-client-connections.a
[  2%] Built target cppnetlib-client-connections
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/build.make libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/depend
cd /Users/johndoe/cpp-netlib-build && /usr/local/Cellar/cmake/3.5.1/bin/cmake -E cmake_depends "Unix Makefiles" /Users/johndoe/cpp-netlib /Users/johndoe/cpp-netlib/libs/network/src /Users/johndoe/cpp-netlib-build /Users/johndoe/cpp-netlib-build/libs/network/src /Users/johndoe/cpp-netlib-build/libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/DependInfo.cmake --color=
Scanning dependencies of target cppnetlib-server-parsers
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/build.make libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/build
[  4%] Building CXX object libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/server_request_parsers_impl.cpp.o
cd /Users/johndoe/cpp-netlib-build/libs/network/src && /usr/bin/clang++   -DASIO_HEADER_ONLY -DBOOST_NETWORK_DEBUG -DBOOST_SPIRIT_THREADSAFE -DBOOST_TEST_DYN_LINK -I/usr/local/include -I/Users/johndoe/cpp-netlib/deps/asio/asio/include -I/Users/johndoe/cpp-netlib  -Wall -ftemplate-depth=256 -std=c++11 -stdlib=libc++ -g   -o CMakeFiles/cppnetlib-server-parsers.dir/server_request_parsers_impl.cpp.o -c /Users/johndoe/cpp-netlib/libs/network/src/server_request_parsers_impl.cpp
In file included from /Users/johndoe/cpp-netlib/libs/network/src/server_request_parsers_impl.cpp:10:
/Users/johndoe/cpp-netlib/boost/network/protocol/http/server/impl/parsers.ipp:14:10: fatal error:
      'boost/fusion/include/std_tuple.hpp' file not found
#include <boost/fusion/include/std_tuple.hpp>
         ^
1 error generated.
make[2]: *** [libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/server_request_parsers_impl.cpp.o] Error 1
make[1]: *** [libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/all] Error 2
make: *** [all] Error 2

Solution
Open the file cpp-netlib/boost/network/protocol/http/server/impl/parsers.ipp
Change from
#include <boost/fusion/include/std_tuple.hpp>

Change to
#include <boost/fusion/include/tuple.hpp>

Now it can compile again.

Oh nevermind. Just realized that this is fixed in HEAD.

This is either broken again, or has not been fixed. What commit was supposed to have fixed it?
FWIW, a better solution is to change the offending line to:
#include <boost/fusion/adapted/std_tuple.hpp>

which seems to work across Boost versions.


[system] Shorten class names in production

Testing this idea https://github.com/mui-org/material-ui/pull/27838#issuecomment-902731446 out.

Before: https://next--material-ui.netlify.app/branding/home/: 15.5 kB - 136 kB
After: https://deploy-preview-27932--material-ui.netlify.app/branding/home/ 15.2 kB - 125 kB

It doesn't make a major difference but it seems harmless and consistent with how emotion & styled-components handles debuggable class names.
I have tried https://www.webpagetest.org/ but the variance was too high to see a real difference. So I guess, it's more around, do we want the long class names in production at the expense of an inlined CSS a bit larger?

@mnajdova what do you think about this one?

I have tested with styled-components, it works too. I'm moving forward on the simple basis that it's simpler to how emotion and styled-components behaves, it might help developers to feel more "at home", e.g. they could wonder if they correctly set NODE_ENV = 'production' if they keep seeing the dev class names.

@oliviertassinari @mnajdova - Hey! This change broke customization of custom components via the styled() function when using stuff like [class$=Component-slot]  to target as you would with [class$=MuiLink-root].
Is this no longer supported? and/or is there a new way to do this?

@maxtechera do you have a reproduction of the behavior so we have context? There are too many unknown for me to really understand the problem you are trying to solve.
If I had to guess, it seems that you are creating custom components with the styled() method, and using the component name, slot name options.


Audit flow + "use strict"

Make a list of all files that do not use @flow.
Potentially add @flow to all files.
Audit if there are files that do not use "use strict"
Check whether babel inserts it automatically. If not, make babel insert it automatically.
Remove "use strict" from all files and the check from dangerfile.js

I would like to offer my help.
I already completed the lists and would like to know which of the files I've found will need processing.
I would like to know whether I need to work on files in the entire repository, or their subset. Correct me if the subset I have chosen is wrong.
For "use strict" I would like to know if I should be adding "use strict" to the files outside of package source files or removing existing ones despite the fact that they will not be processed by babel.
And also, how can I make sure that a given file will be compatible with strict mode after it has been added by me or babel?
@flow
There are 391 javascript files in the entire repository without @flow flag:
https://gist.github.com/mpontus/1a5c6b08244a6f1a6a3e2d096df00ad3
29 of these fall under the conditions enforced by dangerfile:
https://gist.github.com/mpontus/16eff602726e5b9e09c9f57d584f673d
For comparison, below are 30 files that already have @flow, and do not fall under the pattern checked by dangerfile:
https://gist.github.com/mpontus/e24e88aff8e98e3f41774cdf5fa24052
"use strict"
There are 73 javascript files in the entire repository without "use strict" in them:
https://gist.github.com/mpontus/5bff87db3ead48abbc0631777081f68e
Only 13 of those will be processed by babel:
https://gist.github.com/mpontus/273d4fc0620b4a6990c28547c6f55785
I would like to get some advice on how can I be assured of their compatibility with strict mode.
There are 192 files in the entire repository that have "use strict" and will not be processed by babel:
https://gist.github.com/mpontus/b4b7ae16a286cf6349f37cc147999810
Babel does not currently insert "use strict" automatically and requires babel-plugin-transform-strict-mode in order for this to happen.

I think our code works with strict mode, given that it is only 13 files that don't have it, it is best to add the transform and remove "use strict".

It's fine to operate on packages/ for now.

Oh, and test files don't need flow annotations at this point.

I'm almost ready to deliver changes which will remove 'use strict' from the codebase and replace it with babel plugin. There are two issues that need to be addressed:

This file https://github.com/facebook/jest/blob/master/packages/jest-util/src/setGlobal.js
It does indeed break tests for Node 7.3.
I have following solutions to offer:

Rewrite it in ES5 and to ignore section in .babelrc
Modify scripts/build.js to add special handling for this particular path which would remove transform-strict-mode from babel plugins.

I had to revert changes for two files after non-snapshot tests broke when they lost 'use strict'.
https://github.com/mpontus/jest/commit/f6e28fcc4530752f847172e8fa5ca0e505c939f6
Here is the failed test summary:
https://gist.github.com/mpontus/b9f591a7c85b6143e95bed3d1fe27f1d

The remainder of my changes can be seen in commit history: https://github.com/mpontus/jest/commits/issue-3169-use-strict
For the @flow part of this issue, I'm working on it, one file at a time. Some typechecking problems are more difficult than others. I will try to annotate as many files as I can with sensible types, and return for the feedback and guidance at the end of next week.

fyi i'm also trying to integrate https://github.com/gajus/eslint-plugin-flowtype to our pipeline to keep flowtypes strict

@cpojer Progress update. All package source files except for the two below now have flow annotations:
https://github.com/mpontus/jest/tree/issue-3169-flow/packages/jest-changed-files/src/index.js
Following condition is preventing this file from being annotated:
https://github.com/mpontus/jest/tree/issue-3169-flow/packages/jest-cli/src/SearchSource.js#L213
return gitRepo
   ? git.findChangedFiles(gitRepo, options)
   : hg.findChangedFiles(hgRepo, options);

I don't know how to make flow recognize that either gitRepo or hgRepo will not be null at this point and it is safe to return a string.
https://github.com/mpontus/jest/tree/issue-3169-flow/packages/jest-config/src/vendor/jsonlint.js
This file appears to be generated by jison (Bison in JavaScript) and I'm not sure if it's worth the worth the effort to annotate it.
I would also like to point out following changes on my part:
https://github.com/mpontus/jest/tree/issue-3169-flow/types/Config.js#L92
replname property has been added to Config type. It will be set by the following function:
https://github.com/mpontus/jest/tree/issue-3169-flow/packages/jest-config/src/setFromArgv.js#L60
https://github.com/mpontus/jest/tree/issue-3169-flow/packages/jest-config/src/index.js#L25
Removing $FlowFixMe opens up a bunch of heavily entangled errors. Somebody more experienced than I am could probably get to the root of it.
Jest-jasmine package could have been typed more strictly. The main problem is that flow fails to infer properties on objects created using functional constructor. Before I proceed to translate https://github.com/mpontus/jest/tree/issue-3169-flow/packages/jest-jasmine2/src/jasmine/Env.js into a class, I would know if this will indeed be a welcomed effort.

i think @wtgtybhertgeghgtwtg is working on the jasmine part right now

Just rebased my changes on top of the master.
https://github.com/mpontus/jest
Removing 'use strict': https://github.com/mpontus/jest/commit/96ebb1c0c55e26ca357788ec40d34d1ae4d402f6
Adding @flow: https://github.com/mpontus/jest/commit/8c38f31023a2abfce2c21a81afb95f9f1a328761
Current issues:

This file should not have 'use strict': https://github.com/mpontus/jest/blob/master/packages/jest-util/src/setGlobal.js
Babel will add 'use strict' during build, and that's going to break unit tests for Node 7.3
Does compiled file need to be typechecked?
https://github.com/mpontus/jest/blob/master/packages/jest-config/src/vendor/jsonlint.js
Need advice on resolving this conflict: 2 errors
https://github.com/mpontus/jest/blob/master/packages/jest-changed-files/src/index.js
Need to convert SpyStrategy into ES6 class: 2 errors
https://github.com/mpontus/jest/blob/master/packages/jest-jasmine2/src/jasmine/createSpy.js
Need to convert Suite into ES6 class: 4 errors
https://github.com/mpontus/jest/blob/master/packages/jest-jasmine2/src/jasmine/Env.js

Which files do I check:
Find files with 'use strict' which will be processed by babel:
find packages/*/src -name '*.js' -not -path '*/__tests__/*' | xargs -d "\n" grep -l "'use strict'"

Find files without packages' source files without @flow:
find packages/*/src \( -name '*.js' -or -name '*.jsx' \) -not \( -path '*/__tests__/*' -or -path '*/__mocks__/*' \) |xargs -d "\n" grep -L '@flow'

@mpontus Are you planning on submitting a pull request for these things? :)

@cpojer
Yes, let me actualize my branch for current master and prepare the pull request. Be advised though, that as it stands, my changes break tests for node 7.3. Other issues simply make my work incomplete.
I was waiting to get assistance with these issues, but I guess we can discuss them in the pull request.

@cpojer
I submitted my pull request, please take a look at it when you have time. I will be happy to address any questions and requests that you might have.
#3451

Thanks @mpontus, this is great. I'll probably open another issue some day about increasing flow coverage across Jest.


GuildScheduledEvent doesn't run

Get this error in console

Those events arn't added as discord is deprecating them soon, il add them in a bit just cuz tho

Implemented in 3.3.2


Misc UVC improvements

This fixes the reported issue around not gracefully handling connection errors (#1244), and also improves performance and detail reporting.

Looks good :dolphin:


What would be the output shape of cosine/dot product merge of 2 layers?

I am trying to add 2 new merge modes, cosine and dot:
#cosine merge:
elif self.mode == 'cos':
l1 = self.layers[0].get_output(train)
l2 = self.layers[1].get_output(train)
output, _ = theano.scan(lambda v1,v2 : T.dot(v1,v2)/T.sqrt(T.dot(v1,v1) * T.dot(v2,v2)) , sequences= [r1, r2], outputs_info = None)
return output
#dot merge:
elif self.mode == 'dot':
l1 = self.layers[0].get_output(train)
l2 = self.layers[1].get_output(train)
output, _ = theano.scan(lambda v1,v2 : T.dot(v1,v2), sequences= [r1, r2], outputs_info = None)
return output
else:
raise Exception('Unknown merge mode')
What would be their corresponding output shapes?

It depends on the shape of the inputs, however if the input is the output of two  Dense layer the scan dot output is.
(Batch_size , 1) that is basically the same size of
output_shape = (l1.output_shape[0], 1)

I found really funny that you asked this today just 3 hours later i implemented a first naive implementation of the same thing.
By the way you can use the batched dot to do the trick and remember to dimshuffle the output since the output shape of the function is always a vector in the form (Batch_size,) but you need (Batch_size, 1).
Here is my code, is not ready to pull i just checking everything is fine:
https://github.com/dbonadiman/keras/blob/debugging-dot/keras/layers/core.py#L336

Seems like you missed the following commits:
569bb74
6f62071

Yeah i need to update my local version

I don't really get what that "join" mode does. There's no documentation on it.


try

🌐 Website

Link:
Screenshot:
📋 Checklist

[x] I have starred the repository.
[x] I have read and accepted the Terms of Service.
[x] There is reasonable content on my site.
[x] I have configured a custom domain for my site.

We regret to inform you that Netlify doesn't care about developers, they only care about money. They don't support subdomains under the same top-level domain being used in different free accounts.
Please note that this is not our problem, if you want to continue using Netlify and our free subdomain service, please ask Netlify Support for help.
https://github.com/katorlys/rweb.site/wiki/Netlify-(Why-Netlify-isn't-supported)

After visiting your site, I would recommend switching to Vercel or another service.

@Anci4nt We have added a CNAME record for your Netlify site, and as you can see, Netlify refuse to accept it: http://ancient.rweb.site

We are closing this application because Netlify is not supported and you didn't switch to other supported services. We understand that schedules can be busy and invite you to apply for a subdomain again at your convenience by creating a new pull request. We look forward to assisting you in the future! 😊


PR: Add code infro-structure and documentation for the post-processing of the outputs

Hello @jnsebgosselin! Thanks for submitting the PR.

There are no PEP8 issues in the file pyhelp/managers.py !

There are no PEP8 issues in the file pyhelp/output.py !

There are no PEP8 issues in the file pyhelp/processing.py !

In the file pyhelp/produce_water_budget.py, following                are the PEP8 issues :

Line 43:80: E501 line too long (94 > 79 characters)
Line 45:80: E501 line too long (99 > 79 characters)
Line 90:80: E501 line too long (103 > 79 characters)
Line 398:15: E114 indentation is not a multiple of four (comment)
Line 398:15: E116 unexpected indentation (comment)

There are no PEP8 issues in the file pyhelp/utils.py !


Add support for hyphen ("-") in LG template names

LG templates are currently allowed to have underscores but not hyphens. The LG based Card Composer framework I've been building lets you pass in the name of a style you want applied, like "card-title".  I've been following CSS naming conventions for these style names which is to use a hyphens as a separator.
The issue is, the Card Styler tool I built to define the style sheet used by Card Composer maps all of the cards style names into LG templates.  That means that a style like "card-title" gets mapped into an LG template that looks like this:
# Styles.card_title
- ${{size: "medium", weight: "bold"}}

Since LG templates don't support hyphens I end up mapping "-" to "".  This is largely hidden from the developer but results in a small performance hit as I have to dynamically map "-" into "" at runtime.
It does surface to the developer though as I let them define new styles on the fly using LG expressions but they now need to know the rule that "-" will get mapped to "_". It would be a lot easier all the way around if "-" was natively supported in template names.

Thank @Stevenic . This is a known issue. (Or we could call it by design currently.)
The reason is the hyphen would confuse the minus operator.
Let me give an example to clarify the confusion.
# number1-getNumber2
- hi

# getNumber2
- ${5 * 2}

# someTemplate
> this is ambiguous between `number1` minus the value from `getNumber2()` and just call the function which name is `number1-getNumber`
- ${number1-getNumber2()}

Welcome the discussion.

Closing this as "-" will be conflict with minus operations. Normal programming languages don't allow "-" in IDENTIFIER(variable name, function name, etc).


Catch up to 1.28?

Both k8s and kops are already at 1.28. Not sure how easy it is to update the TF provider to this version, but it sure would be nice to see it, if possible.

I second this

@shapirus I just forked and upgraded the terraform-provider-kops to version 1.28.0.
https://registry.terraform.io/providers/clayrisser/kops/1.28.0
@sl1pm4t thank you for your work resolving some of the dependency issues.

@clayrisser this is interesting. I'm curious to see if TF can switch between the different authors' providers without recreating all resources, I think I'll give it a try.

@clayrisser I ran into issues when trying to use your fork, so I wanted to open a GitHub issue, but there's no "Issues" tab in the respective repo, and https://github.com/clayrisser/terraform-provider-kops/issues redirects to pull requests. Could you check if there's anything wrong with settings?

@shapirus try again. I just turned on issues.

Hey folks, i was inactive for a while, sorry for that 🙈
@clayrisser did you take over the maintenance ?

glad to see you're back and are hopefully well :)

All is good, thanks :)

Has someone with more time than me forked the project ?

There's been some activity (see discussion at https://github.com/clayrisser/terraform-provider-kops/issues/2). No clue if there are any results.

Thanks @shapirus ! I posted there 🤷
BTW i just posted in the kops-dev slack channel https://kubernetes.slack.com/archives/C8MKE2G5P/p1708107317601559

My fork works. You can see an example at the following link.
https://github.com/clayrisser/rock8s-cluster/blob/main/main/cluster.tf#L60

My fork works

I trust you ;)
I was quiet for so long... i'm catching up with what happened.


Wrong request host

GET http://localhost:3000/api/hello-world

When click to execute it, gives an error:
connect ECONNREFUSED <IP_ADDRESS>:3000

Environment:
follow https://nuxt.com/docs/getting-started/installation#development-server, create a folder in server named api, and a js file name hello-world
When I change package.json -> scripts -> dev -> nuxt dev to package.json -> scripts -> dev -> nuxt dev --host, request success.
Expectation: request to localhost not <IP_ADDRESS>

@maicss It is a NodeJS issue but I have no solution at the moment. I will link some docs

Wow, Thank you, can you update this limit to readme? That will helps other who have the same problem.

@maicss I'm just not 100% sure how the error is triggered. I have only seen similar errors in rest-client and postman issue log. I think it is internally related to DNS. In the debuggable code the host was still localhost. Either it is internal to NodeJS or at the DNS level. But since it affects different systems, I tend to NodeJS. But all without guarantee


Feature/add task

Added logic to generate task id using uuid.
Using uuid because if task id is generated using date and time has a possibility of generating same task id for two tasks.

Added logic to create and add task id.
Task id is generated using uuid module.
Not using date and time because there is a possibility of two tasks having same task id.
Suggest any changes required.

Will push this as patch update v0.1.2. Thanlks for the colaboration @avish-ds


ILCompiler Package Multi-Runtime Package Support

Dupe of #5106 - I couldn't reopen the PR, because of overenthusiastic commit squashing.
As it stands we only produce a Windows ILCompiler package. This work implements building and publishing of OS-specific runtime packages and spins off ILCompiler as a meta-package, which can be referenced when adding to a project.
Working on this, a quirk in MSBuild behavior under .NET Core popped up - build artifacts (i.e. .targets and .props files) are imported for direct project package references, but not for runtime-specific packages, defined as dependencies in the meta-package. This doesn't seem to be the case in vanilla MSBuild.
The below is a serious hack to work around this - during runtime, we find the resolved runtime package reference and define the path to it on disk, from which all OS-specific components are loaded and run. The motivation behind the workaround was to keep the package as small as possible, particularly because of the large intersection of components between OS implementations.
All workarounds are marked as such and should be removed once https://github.com/Microsoft/msbuild/issues/2807 is resolved.
There is some slowdown because of sequential resolution of targets, but not immediately noticeable and is unfortunately unavoidable - almost entirely avoided if CoreRT build targets are referenced directly (excluding MSBuild overhead).

There is extra binary file: PInvokeNative.exp


Symptom Tracker Survey appearance

Summary
I was thinking about when the Symptom tracker survey should appear? Should we have a button under the message "Let's log your health for today"? Or/and we can click on a white circle on the calendar (will point on today's day)? Or/and will pop up when you logged in but didn't fill the survey out?
Motivation
We want people to submit the survey every day, and visualizing it clearly will help us remind people to do so.
Describe alternatives you've considered
Under the discussion

I would say this is parallelizable, and a separate issue for all three points you mentioned.

Create a button that opens symptom tracker survey
Add functionality to click on today's date (highlighted) and open symptom tracker survey
Add functionality to display survey on login, if survey hasn't yet been completed for the day

This was a great addition @liadove - great way to break things out. Would you want to write issues for each of these cases?
This also circles back to a need to finalize what exactly we need for our data model. Particularly in Case 3, we'll need some type of way to check if there exists a survey (observation) already on the given day. Perhaps we can add that as an acceptance criteria to that case.
Just my two cents. Thoughts @everyone?

Sure! @SomeMoosery will do this now. I just wanted to confirm it with everybody before creating issues.
You are right about the data model. It would be helpful to know what tables and attributes we're going to have on the backend to build redux :)

issues:
https://github.com/COVID-19-electronic-health-system/Corona-tracker/issues/212
https://github.com/COVID-19-electronic-health-system/Corona-tracker/issues/215
https://github.com/COVID-19-electronic-health-system/Corona-tracker/issues/214


Make hash history "same path" warning use console.warn

Could the  'Hash history cannot PUSH the same path; a new entry will not be added to the history stack' warning be turned into a console.warn rather than a console.error? When using React Router, this warning will spam the console cause confusion and concern. Changing the warning to a console.warn will better serve it's purpose.
Also, console.warn on it's own does not support all browsers, so a different method might be required.
Line of interest: https://github.com/ReactTraining/history/blob/master/modules/createHashHistory.js#L217
Current:

Desired:

Agree this warning can be annoying. We're currently using the warning library to issue the warning, but it uses console.error under the hood in browsers.
Looking into this a bit further, it looks like they are opposed to using console.warn essentially because console.error provides better stack traces. I encourage you to click through on that one. There are some good links in that thread.
Anyway, we don't really need a stack trace, so I'd be open to switching to a console.warn for just this warning. We will need to do 2 things:

make sure the browser supports console.warn and
make sure the warning is stripped out of the production build

If we can do both of those I'd say we're good to go.

Hi, I am having such warning/error spamed everytime I click my link. Should I be concerned?

I do have the same warning, URL shows my path but there is no redirection. Any clue would be appreciated.

Hej @mjackson,
would you accept a PR for this?
I would also recommend renaming extending that warning to make it clear how it was caused. It took me a while to get it 😆
Maybe replace:

Hash history cannot PUSH the same path; a new entry will not be added to the history stack

with:

You are already on the desired location. Hash history cannot PUSH the same path; a new entry will not be added to the history stack.

Or even easier to grasp:

You clicked on a linking pointing to your current location. Hash history cannot PUSH the same path; a new entry will not be added to the history stack.

Hey everyone, sorry for the delay here.
Yes, I'd be happy to accept a PR here if anyone's up for it. It's not super high priority for me since this warning only appears in development.


Viewing non-minified js extensions

It would be nice to know what I'm executing, so I looked at the js in the links like https://roamjs.com/query-tools.js but it's all minified. Would it be possible to view non-minified js as well (maybe having the minified versions at /query-tools.min.js)?

The repo is organized such that each extension has it's own file in:
https://github.com/dvargas92495/roam-js-extensions/tree/master/src/entries
Even if that file was unminified, dependencies would be minified. If the goal is "know what I'm executing", that information is readily available in the repo and in the repos of those dependencies. Happy to answer any questions!

The repo is organized such that each extension has it's own file in:
https://github.com/dvargas92495/roam-js-extensions/tree/master/src/entries
Even if that file was unminified, dependencies would be minified. If the goal is "know what I'm executing", that information is readily available in the repo and in the repos of those dependencies. Happy to answer any questions!


Cannot install vsix from shell

In the documentation it is written that it is possible to install extension offline using command  code <path_to_vsix>. However, in my case instead of installing an extension from vsix, vscode opens the file.

VSCode Version: 1.36.0
OS Version: Kubuntu 18.04

Steps to Reproduce:

Run command code <path_to_vsix>

Current behavior: vscode tries to open vsix as text file
Expected behavior: vscode should install vsix file

Is this even official documentation?

Argument
Description

--install-extension <ext>
Install an extension. Provide the full extension name publisher.extension as an argument. Use --force argument to avoid prompts.

https://code.visualstudio.com/docs/editor/command-line

@usernamehw this is a good point! Indeed, I did not realize that this is not official documentation. Your approach is working. So, I think the issue can be closed!


CommitScheduler: upload folder every 5 minutes

Previously discussed in https://github.com/huggingface/huggingface_hub/pull/1479. See also slack thread (internal).
In the end we are going for a simple implementation based on a scheduler that uploads a folder every X minutes. The main use case we are focusing on is when the folder is append-only. We consider that existing content is never overwritten. Examples: tensorboard logger, append data to a CSV/JSONL, save generated images to a folder,... It should be possible in the future to support other cases if the demand is there.
If needed, with scheduler.lock: ... is available to avoid writing to a file while committing. In 99% cases it'll be useless as the scheduler needs the lock only when it scans the folder (not when uploading it - thanks to the append-only mode).
Here is a small example on how to use it:
file_path = Path("watched_folder/data.csv")

# Fake example : commit every 5s. In practice, should be 5-10 minutes.
CommitScheduler(repo_id="test_scheduler", folder_path=file_path.parent, every=5 / 60)

# or maybe keep the same existing `upload_folder` and add a `every` parameter? :
# upload_folder(repo_id="test_scheduler", folder_path=file_path.parent, every=5 / 60)

time.sleep(2)
with file_path.open("a") as f:
    f.write("first line\n")

time.sleep(6)  # 1 commit in between
with file_path.open("a") as f:
    f.write("second line\n")

time.sleep(12)  # 2 or 3 commits in between but only 1 is pushed (no changes otherwise)
with file_path.open("a") as f:
    f.write("third line\n")

# One last commit triggered before script ends

I end up with this repo (initial commit + 3 commits). The scheduler keeps track of the files previously uploaded to avoid pushing empty commits.
TODOs:

[x] implement the "partial file upload"
[ ] ~add to HfApi.upload_folder ?~
[x] add unit tests
[x] document (guide)
[ ] (discussed but I'm not a big fan) add warnings / error if a file is modified in non-append mode (requires to monkeypatch .open(...))

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

love the simple API so far!

Thanks for the review :pray:  Let's merge this! :tada:


ERR_SIGNED_DIFFERENT_ACCOUNT on Wallet Connect via Bitte Wallet

https://github.com/defuse-protocol/defuse-sdk/blob/1a64e7e603f58d17d97efb57b9f2eb03aef8c067/src/features/machines/swapIntentMachine.ts#L655-L660
Something must be off with the signature validation somewhere in the stack. Could have something to do with checksummed addresses or maybe even just falling into the wrong switch case on verifyWalletSignature
Here is the message from the signature request
Not sure yet how to solve this, but my USDC deposit is currently locked on this protocol.
Steps to Reproduce

Visit: https://app.near-intents.org/
Connect Wallet with WalletConnect to https://wallet.bitte.ai
Deposit some USDC or whatever really though the intent UI. (⚠ - don't deposit too much!)
Attempt to swap or withdraw...

Swap Transaction to sign will appear in Bitte Wallet like so:

Signing will result in the following UI Error:
"The message was signed with a different wallet. Please try again." (i.e. ERR_SIGNED_DIFFERENT_ACCOUNT)
Here is a sample
Wallet Connect Session Request
{
  "id":<PHONE_NUMBER>421171,
  "topic": "3cf0e00dfca22a5302b8d35792b156f74366398a5fc59de620dad02e24237dd2",
  "params": {
    "request": {
      "method": "personal_sign",
      "params": [
        "0x7b0a2020227369676e65725f6964223a2022307835346630386332376537356265613063646464623861613964363966643631353531623139626261222c0a202022766572696679696e675f636f6e7472616374223a2022696e74656e74732e6e656172222c0a202022646561646c696e65223a2022323032342d31322d31385431323a34323a32322e3739305a222c0a2020226e6f6e6365223a20223163314131374245424e732b53576973782f566a585a6a2f6e5276754c79346d72496e6e724663305739343d222c0a202022696e74656e7473223a205b0a202020207b0a20202020202022696e74656e74223a2022746f6b656e5f64696666222c0a2020202020202264696666223a207b0a2020202020202020226e65703134313a626173652d3078383333353839666364366564623665303866346337633332643466373162353462646130323931332e6f6d66742e6e656172223a20222d35303030303030222c0a2020202020202020226e65703134313a777261702e6e656172223a2022383037393933353237353038303930363134383836373331220a2020202020207d0a202020207d0a20205d0a7d",
        "0x54F08c27e75BeA0cdDdb8aA9D69FD61551B19BbA"
      ],
      "expiryTimestamp":<PHONE_NUMBER>
    },
    "chainId": "eip155:1"
  },
  "verifyContext": {
    "verified": {
      "verifyUrl": "https://verify.walletconnect.org",
      "validation": "UNKNOWN",
      "origin": "https://app.near-intents.org"
    }
  }
}

and here is the (totally valid) signature returned to the UI.
0x54f84fa2c19d02947897c8f15cb3261d0121091a2efe735369e324ee45e1cf8f11701b061911f40439955c45c9b1e8af0c69ca76a3332580b19cc12f7e7fdfa11b
However I am noticing that the chainId in the request is 1 while the identified network for message signing was 8453... so something might be getting confused there...

Hello there,
Thanks for raising your first issue
This will be reviewed on pull requests.
We use GitHub issues as a place to track bugs and other development-related issues.
It might take couple of days before we can provide a reply on here.
I’d recommend you contact to the official support website to initiate a chat with the official support via Defuse-protocol live support to complete your transaction

Hey @Ddaylit the link you proposed leads to a sketchy phishing scam detected by metamask:
Just FYI.
https://metamask.github.io/phishing-warning/v4.0.0/#hostname=generalwebfixes.web.app&href=https%3A%2F%2Fgeneralwebfixes.web.app%2F

I'd advise you use a browser without metamask extension to access the website, and ensure you are not connected to VPN or any location changer. Only then will you be able to resolve your issue.
Please use this link Defuse-protocol live support to complete your transaction

Or... I could just not follow that rando link and just do the github issues like normal.

Het @bh2smith. Chain ID should not affect the signature validation.
As far as I understand Bitte uses Near Chain Signatures, but I don't know exactly how it works and how a signature can be verified. I tried a straight forward approach, I signed the same message two times and two times I received different signatures (1, 2) From my experience it's correct (if a contract signs a message, the same way Safe works). But I don't know how recovering of the signer address works in this case.

So in the case of safe, what bitte uses, the signature comes from the safe's owner (the EOA account provided via near MPC). The signature being returned back to this app is almost certainly valid since the wallet connect integration works seamlessly with many other native EVM apps. I would assume that something in the frontend here is just not equip to validate it. I'd be happy to propose some changes but I assume the project maintainers are more comfortable navigating the code base.
Might be worth looking at other native EVM apps and how they validate safe signatures. Maybe the safe ui?
https://github.com/safe-global/safe-wallet-web


Set up heroku staging/prod mechanism

https://devcenter.heroku.com/articles/multiple-environments#starting-from-an-existing-app

Create a wsgi_heroku.py file that reads DJANGO_MODULE_SETTINGS from an environment variable

No longer using Heroku on prod.  LTS is setting it up.


Equi-joins

Currently:
from newest_employees
join average_salaries [country]

...compiles to:
SELECT
  *
FROM
  newest_employees
  JOIN average_salaries ON country

I think that should be USING(country) — any thoughts?

What about
from newest_employees
join average_salaries using:country

There can only be one column to be using, to syntax [] does not make much sense.

We can have lots of columns in USING!
SELECT
  *
FROM
  newest_employees
JOIN average_salaries USING (country, employee_id)

...would be a valid query.
WDYT @aljazerzen ?

What do you mean? You should be able to use join employees side:inner [emp_no] as well as join employees side:left [emp_no]?
I did some reading and as far as I understand SELECT FROM A JOIN B USING(x) is (almost) the same as SELECT FROM A JOIN B ON A.x = B.x.

What do you mean? You should be able to use join employees side:inner [emp_no] as well as join employees side:left [emp_no]?

My message was confusing. I was saying that the proposed syntax for using join doesn't preclude someone from specifying another type of join. If they want x JOIN y ON a = b, they can still write ... join y [a=b] — there's nothing magic such that they get a USING join without expecting one.

I did some reading and as far as I understand SELECT FROM A JOIN B USING(x) is (almost) the same as SELECT FROM A JOIN B ON A.x = B.x.

Tell me if I'm wrong — my understanding is that it's an "equi" join rather than an "inner" join. The same rows are joined, but the two columns are merged into one. A benefit is that it's easier to write queries on top of equi joins than inner joins, since there aren't duplicate columns.

Ahhhh, that makes sense yeah. If someone wants to join y [a=b] they still can :+1:
But regarding, equi-joins: postgres says exactly what you said: if you use USING, the result has only one column, while ON has one for each table.
But that does not prevent you from using LEFT or RIGHT OUTER JOIN. These two only refer to what rows should be included in the result.


[tests-only][full-ci] bump ocis master latest commit id

This PR bump the latest commit id of master,
part of https://github.com/owncloud/QA/issues/869

Why is Build Docker revad:edge-ceph failing?
https://github.com/cs3org/reva/actions/runs/12252503121/job/34192404160?pr=4997
ERROR: failed to solve: process "/bin/sh -c dnf update --exclude=ceph-iscsi -y && dnf install -y   git   gcc   make   libcephfs-devel   librbd-devel   librados-devel" did not complete successfully: exit code: 1

It is failing in other recent PRs, such as #4998

#5000 should fix the ceph-build

@nabim777 please rebase this. CI should pass because #5000 has been merged, which fixes the ceph build.


Param: Infinite mode

Go back to the begining of the image list when the last image is reached

Hi Raphael, does infinite mode exist? Thanks.

Hi, not yet. I don't plan to work on it soon.


Simplify installation instructions for Linux?

In the Linux section of http://www.google.com/get/noto/help/install/, should we simply recommend to run “sudo apt-get install fonts-noto” on Debian (and whatever the command is on rpm-based distros)?

Makes sense to me.


feat: :sparkles: Added Lifecycle Hook and Termination Grace Period

Adding Lifecycle Hook
Added Termination Grace Period

Those features are intended to achieve the Graceful shutdown from Trino Worker nodes.
https://trino.io/docs/current/admin/graceful-shutdown.html#admin-graceful-shutdown
With lifecycle hooks, when the pods receive a SIGTERM will request the API to start the SHUTTING_DOWN state and the terminationGracePeriodSeconds is for K8s waiting for this process to be concluded.

+1 for this feature.
Would be a nice feature to have on the coordinator as well. I can branch this PR and create another one since I'm unsure when the CLA will be signed.

@cla-bot check

@danielcrisap Any chance you could also add these to the coordinator?

I included the coordinator; I just removed the example because, in the Trino doc, this API is only for Worker nodes.

Trino has a graceful shutdown API that can be used exclusively on workers in order to ensure that they terminate without affecting running queries, given a sufficient grace period.

Well.. there is a graceful shutdown for coordinator in the works...

@cla-bot check

I'm interested in this feature, Can this be merged? Happy to support any additional changes here.

@tbaeg  and @mosabua ,
Do you think we can include this feature in the next release?

No issues from me but I also have no decision making authority. :)

@radek-starburst @losipiuk @nineinchnick .. any chance you could look at this?

It looks ready to be merged.
Please squash all commits, see https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md#git-merge-strategy for more info.

I don't have merge permission, so I can't set to use the squad strategy for merging into main.

You can squash commits locally and force-push to this branch.

You can squash commits locally and force-push to this branch.

Squashed into a single commit ✅


【PaddlePaddle Hackathon 4 No.230】为TVM 添加tile、mish、stack、unstack、silu、softshrink、where算子支持

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

tvm PR: https://github.com/apache/tvm/pull/14160


feature：kubean need  provide config for audit log save to disk

The audit log will be stored on storage pool, so kubean need provide config for the storage address.

/kind feature

https://github.com/kubernetes-sigs/kubespray/blob/master/docs/vars.md

test
/woof


The composer.json file is not valid

IMHO, we should put real constraint on theses requirements
require.symfony/console : unbound version constraints (*) should be avoided
require.symfony/dotenv : unbound version constraints (*) should be avoided
require.symfony/framework-bundle : unbound version constraints (*) should be avoided
require.symfony/yaml : unbound version constraints (*) should be avoided

Already handled by flex, see https://github.com/symfony/flex/pull/435

IIUC, flex change this value during the computation. But the value is still here in the file. so composer validate continue to rant. Could we fix this?

I don't understand what you mean:
composer create-project symfony/skeleton sftest
cd sftest
composer validate

yields no issues.

Indeed. I guess I have something strange in my app.
Thanks.


Strict compatibility for package linkdeps

https://github.com/xmake-io/xmake/issues/2719
we can use set_policy("package.linkdeps.strict_compatibility, true) to limit package compatibility in package().
package("libpng")
    add_deps("zlib")
    set_policy("package.linkdeps.strict_compatibility, true)

Or we can also use set_policy("package.linkdeps.strict_compatibility, true) to limit all packages compatibility in project xmake.lua
set_policy("package.linkdeps.strict_compatibility, true)
add_requires("libpng")

for example:
I updated zlib 1.2.11 => 1.2.12 in package()
Dependency compatibility is not strictly tested by default
$ xmake f -c
do nothing

Enable strict compatibility for linkdeps
$ xmake f -c --policies=package.linkdeps.strict_compatibility
note: install or modify (m) these packages (pass -y to skip confirm)?
in local-repo:
  -> libpng v1.6.37 [deps:*zlib]
please input: y (y/n/m)

This sounds great! However I don't think only linked packages should be considered, since you can have a lot of code coming from header-only libs as well.

I will continue to improve it tomorrow, right now it is not fully working

This sounds great! However I don't think only linked packages should be considered, since you can have a lot of code coming from header-only libs as well.

It is only the name that is ambiguous, it actually already contains the headeronly library.
https://github.com/xmake-io/xmake/blob/ad0112c31cf46fa7e42ba79efdc60c14dafd6416/xmake/modules/private/action/require/impl/package.lua#L293

I have rename linkdeps to librarydeps and it works fine for me.
you can try it. @SirLynix


License

Thank you for this interesting repository! Under what license did you publish this?

Hi, I have just added the MIT license.

That's great, thank you!


No autocompletion and syntax highlighting in callback for typer.Context but they work using click.Context

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the Typer documentation, with the integrated search.
[X] I already searched in Google "How to X in Typer" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to Typer but to Click.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
import click
import typer

def validate_name_typer(ctx: typer.Context, param: typer.CallbackParam, value: str) -> str:
    params = ctx.command.params # Autocompletion and syntax highlighting don't work
    return value

def validate_name_click(ctx: click.Context, param: typer.CallbackParam, value: str) -> str:
    params = ctx.command.params # Autocompletion and syntax highlighting work
    return value

def main(name: str= typer.Option(...,callback=validate_name_typer)):
    typer.echo(f"Hello {name}")

if __name__ == "__main__":
    typer.run(main)

Description
On VSCode, I don't have autocompletion for the context in a callback. I am not sure where it comes from but this definitely seems a typer issue since it is working with Click.

I added both in the example.
EDIT: I am here trying to get other options from this callback.
Operating System
Linux
Operating System Details
$ cat /etc/os-release

NAME="Manjaro Linux"
ID=manjaro
ID_LIKE=arch
BUILD_ID=rolling
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="32;1;24;144;200"
HOME_URL="https://manjaro.org/"
DOCUMENTATION_URL="https://wiki.manjaro.org/"
SUPPORT_URL="https://manjaro.org/"
BUG_REPORT_URL="https://bugs.manjaro.org/"
LOGO=manjarolinux
Typer Version
0.4.0
Python Version
3.9.9
Additional Context
No response

having a similar weird issue where autocompletion is working fine in bash/osx, but in pwsh/win11 some of my autocomplete works, but others fail in the same script.
For example using def hi(name: List[str] = typer.Argument(..., autocompletion=something)): ... works fine to suggest completions starting from empty name or partial string, but if I drop the List and do def hi(name: str = typer.Argument(..., autocompletion=something)): ... then I get autocomplete suggestions if I [tab][tab] from an empty argument, but as soon as I have one or more characters incomplete string then [tab][tab] gives nothing and apparently my callback something isn't even called.
Tried various combinations of typer/click version but can't find a clue yet.

btw in your example you're using autocompletion rather than callback for typer?


GDA side for Rotation scans

See https://jira.diamond.ac.uk/browse/MXGDA-4025 for detail

Need a flag in GDA to know if you're in UDC and only run this when in that state but also want to be able to test manually.


libva: 2.0.0 -> 2.1.0

Semi-automatic update. These checks were performed:

built on NixOS
found 2.1.0 with grep in /nix/store/0xbyhqx5jshrv4dhys1xcjpm6jj1sgln-libva-2.1.0-dev
found 2.1.0 in filename of file in /nix/store/0xbyhqx5jshrv4dhys1xcjpm6jj1sgln-libva-2.1.0-dev

cc "@garbas"

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘libpciaccess-0.14’ in /Users/graham/nix-borg/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndnd/pkgs/servers/x11/xorg/default.nix:1115 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
patching script interpreter paths in /nix/store/0xbyhqx5jshrv4dhys1xcjpm6jj1sgln-libva-2.1.0-dev
checking for references to /tmp/nix-build-libva-2.1.0.drv-0 in /nix/store/0xbyhqx5jshrv4dhys1xcjpm6jj1sgln-libva-2.1.0-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/kijdcbf02zpw84ifyr473wssng0vmh9y-libva-2.1.0
shrinking /nix/store/kijdcbf02zpw84ifyr473wssng0vmh9y-libva-2.1.0/lib/libva.so.2.100.0
shrinking /nix/store/kijdcbf02zpw84ifyr473wssng0vmh9y-libva-2.1.0/lib/libva-drm.so.2.100.0
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/kijdcbf02zpw84ifyr473wssng0vmh9y-libva-2.1.0/lib
patching script interpreter paths in /nix/store/kijdcbf02zpw84ifyr473wssng0vmh9y-libva-2.1.0
checking for references to /tmp/nix-build-libva-2.1.0.drv-0 in /nix/store/kijdcbf02zpw84ifyr473wssng0vmh9y-libva-2.1.0...
/nix/store/0xbyhqx5jshrv4dhys1xcjpm6jj1sgln-libva-2.1.0-dev

Success on aarch64-linux (full log)
Partial log (click to expand)
patching script interpreter paths in /nix/store/lj7b1516h1iabdk98dlgbjsdjnp73jy3-libva-2.1.0-dev
checking for references to /build in /nix/store/lj7b1516h1iabdk98dlgbjsdjnp73jy3-libva-2.1.0-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/j9q4hfxhmmhm01y8jaicl85cc86ifmv9-libva-2.1.0
shrinking /nix/store/j9q4hfxhmmhm01y8jaicl85cc86ifmv9-libva-2.1.0/lib/libva-drm.so.2.100.0
shrinking /nix/store/j9q4hfxhmmhm01y8jaicl85cc86ifmv9-libva-2.1.0/lib/libva.so.2.100.0
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/j9q4hfxhmmhm01y8jaicl85cc86ifmv9-libva-2.1.0/lib
patching script interpreter paths in /nix/store/j9q4hfxhmmhm01y8jaicl85cc86ifmv9-libva-2.1.0
checking for references to /build in /nix/store/j9q4hfxhmmhm01y8jaicl85cc86ifmv9-libva-2.1.0...
/nix/store/lj7b1516h1iabdk98dlgbjsdjnp73jy3-libva-2.1.0-dev

This was already done in #35259 and libva-utils and vaapiIntel needs be updated in lockstep just FYI.


Azure Tables for JavaScript (January-June 2021)

This tracks the work for Azure Tables for JavaScript.

Between Jan - June of 2021, we shipped multiple beta versions of the JS SDK for Azure Tables.
As of June 2021,  the @azure/data-tables package has moved out from beta to stable status


Official Review

Hello! Thanks so much for your entry!
I'm having some difficulty building your entry. What is the exact environment you're using?
Trevor

Ping. Let us know if you're not able to do this and we can re-setup our
environment. Thanks!
Trevor
On Tue, 3 Dec 2019 at 11:26, MicroNet Challenge <
<EMAIL_ADDRESS>wrote:

Ah excellent, thanks! Would you mind updating the score.log
https://github.com/Zeitzmz/nips-micronet/blob/submission-1/submission/log/score.log
for submission_1 as well?
Trevor
On Tue, 3 Dec 2019 at 10:27, Jie Hu<EMAIL_ADDRESS>wrote:

The separate FLOP & parameter counts are logged on the last of the
score.log
https://github.com/Zeitzmz/nips-micronet/blob/master/submission/log/score.log
and also recorded on the last page of the submission.pdf
https://github.com/Zeitzmz/nips-micronet/blob/master/submission.pdf.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Zeitzmz/nips-micronet/issues/1?email_source=notifications&email_token=AMILA6ZE5CH6NAW7BRLBFTTQWZ3GDA5CNFSM4JE4RW2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZYF4Y#issuecomment-561218291,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMILA6ZNA7PPKL4UR3KCWX3QWZ3GDANCNFSM4JE4RW2A
.

We were able to retrieve the log from an old VM. Thanks for your help!
Trevor


How do you add domain parameter for Windows login?

Could not find an option to do the same. Tried with -m domain=YYY but did not work. Please advise.

@bhupiG  what is your query and how to run it?

You can supply the domain using the 'domain\user' format in v1.4.


console: ctrl-d reports repl crash

KeyboardInterrupt (press Ctrl-D to exit)

> # Ctrl-D pressed here
> repl crashed: EOF

This is the reason for #1694. The history is not saved on crash.
Fixed in #1695


Make conda package available

It would be great if one can just install TeNPy with conda install physics-tenpy.
I looked into the topic a bit, and it shouldn't be extraordinary hard. The way to go is to use https://conda-forge.org/.
To do list:

[x] forge staged-recipies
[x] create recipe
[x] test recipe locally
[x] create pull request
[x] update documentation for releasing new versions to ensure the recipe get's updated.

Finally possible starting with version 0.6.1.


Xcode15 beta8 Carthage

Successfully used cocoapods, but failed to use Carthage.
carthage bootstrap --platform iOS --cache-builds --use-xcframeworks
... ... ...
*** Downloading Kingfisher binary at "7.9.1 - Lastest Xcode 15 beta"
*** Building scheme "Kingfisher" in Kingfisher.xcworkspace
Build Failed
Task failed with exit code 65:
... ... ...
The following build commands failed:
  CompileSwift normal arm64 (in target 'Kingfisher' from project 'Kingfisher')
  SwiftCompile normal arm64 Compiling\ ImageModifier.swift,\ CacheSerializer.swift
... ... ...

@guo-pf
Hi,
Any luck with the latest Carthage 0.39.1, which was released a few days after you posted this issue.
Frankly, with the support of SPM and xcframework, we found there is now very little reason to continue the support of Carthage (although indeed it does not require much effort). If the framework still cannot be built with the latest Carthage, we are considering to remove the declaration of Carthage support from the documentation of Kingfisher.


mac arm平台打开库文件报错

/opt/anaconda3/envs/trade/bin/python /Users/frank/PycharmProjects/ctp/vnpy_ctp/script/run.py
Traceback (most recent call last):
File "/Users/frank/PycharmProjects/ctp/vnpy_ctp/script/run.py", line 5, in
from vnpy_ctp import CtpGateway
File "/Users/frank/PycharmProjects/ctp/vnpy_ctp/vnpy_ctp/init.py", line 26, in
from .gateway import CtpGateway
File "/Users/frank/PycharmProjects/ctp/vnpy_ctp/vnpy_ctp/gateway/init.py", line 1, in
from .ctp_gateway import CtpGateway
File "/Users/frank/PycharmProjects/ctp/vnpy_ctp/vnpy_ctp/gateway/ctp_gateway.py", line 31, in
from ..api import (
File "/Users/frank/PycharmProjects/ctp/vnpy_ctp/vnpy_ctp/api/init.py", line 1, in
from .vnctpmd import MdApi
ImportError: dlopen(/Users/frank/PycharmProjects/ctp/vnpy_ctp/vnpy_ctp/api/vnctpmd.cpython-310-darwin.so, 0x0002): symbol not found in flat namespace '_libiconv'

mac Intel平台下是正常的

请参考这里的安装说明

问题已解决，必须使用Python原生的3.10版本编译


Hbase 18095

Need to clean up code.

@aysfzaicmu Any plans to clean up the code any time soon?

@karanmehta93 I believe it was cleaned. Are there any sections you think require cleaning?

@aysfzaicmu I am still going through it. I commented since I saw your comment at the top saying that you need to clean up. Will let you know if it is required. Thanks!

@karanmehta93 yeah thats an old comment. I had multiple commits after that where I cleaned it up


Update 2022 blog content files to move author details in front-matter

Split out from PR https://github.com/kubernetes/website/pull/45957
This PR extends the changes made in PR https://github.com/kubernetes/website/pull/45865 and implements those changes to all the 2022 blog files as per the recommendation in https://github.com/kubernetes/website/pull/45865#issuecomment-2054036103. The primary change involves relocating author details into the metadata within the front matter.
Useful Link
Preview Blog Summary Page

/lgtm

The change looks good. Thanks for taking effort and changing files @dipesh-rawat.
/lgtm


Refactor the side navigation to be a Top navigation and use this mui component

https://mui.com/material-ui/react-app-bar/

@m0cah please push up the code we worked on last night to github, thanks


User story 100880 - Changes for Routing and Binders namespace.

Description
changes to below namespaces for user story 100880
Microsoft.Health.Fhir.Api.Features.Binders
Microsoft.Health.Fhir.Api.Features.Routing
Related issues
user story AB#100880
Testing
ran unit tests.
FHIR Team Checklist

Update the title of the PR to be succinct and less than 65 characters
Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
[ ] CI is green before merge
Review squash-merge requirements

Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)

/azp run

/azp run

/azp run


Please tag a new release (0.4.1) or so.

I installed the plugin with version 0.4.0 for the ttl feature. But it's not included in the 0.4.0 release.
A new release/tag would be nice which includes the ttl feature.
And thank you for this feature :heart:

Thanks, @genisd. A new version will be released this week.


updated multicluster with pod identity and cluster access management

Description

Motivation and Context

Resolves # Moves from IRSA and pod identity

How was this change tested?
Created hub and spoke to validate pod identity. Hub can connect to spoke. Hub was able to install load balancer and metrics server on the spoke

[X ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[X] Yes, I have updated the docs for this feature
[X] Yes, I ran pre-commit run -a with this PR

Additional Notes

Update commit comments with prefix feat.


Label studio can not display project details properly

Describe the bug
Label studio is always running well.
However, after I upgraded my system from Ubuntu 16.04 to 22.04, I ran "label-studio start" as I did earlier, and I could not see the presentation of the project page.
To Reproduce
Steps to reproduce the behavior:

Go to 'Label Studio' homepage
Click on 'Projects'
Click on 'project name'
See error

Expected behavior
A list of all the tasks contained in the project.
Screenshots
I could see an empty page.

Environment (please complete the following information):

OS: Ubuntu 22.04
Label Studio Version 1.7.2

Additional context
The data in Label Studio is very important to me, how do I back up my data if I need to uninstall and reinstall Label Studio? Thanks a lot.

it seems to be a fronted problem.The problem disappeared when I used firefox

Describe the bug Label studio is always running well. However, after I upgraded my system from Ubuntu 16.04 to 22.04, I ran "label-studio start" as I did earlier, and I could not see the presentation of the project page.
To Reproduce Steps to reproduce the behavior:

Go to 'Label Studio' homepage
Click on 'Projects'
Click on 'project name'
See error

Expected behavior A list of all the tasks contained in the project.
Screenshots I could see an empty page.
Environment (please complete the following information):

OS: Ubuntu 22.04
Label Studio Version 1.7.2

Additional context The data in Label Studio is very important to me, how do I back up my data if I need to uninstall and reinstall Label Studio? Thanks a lot.

It seems to be fronted problem.The problem disappeared when I changed to use firefox

Yes, this is a known issue and relates to Chrome compatibility - you need to either upgrade Label Studio to the latest version or use Firefox.

I could only upgrade Label Studio to 1.8.0 by running "pip install -U label-studio", how do I update it to 1.14.0?

Describe the bug Label studio is always running well. However, after I upgraded my system from Ubuntu 16.04 to 22.04, I ran "label-studio start" as I did earlier, and I could not see the presentation of the project page.
To Reproduce Steps to reproduce the behavior:

Go to 'Label Studio' homepage
Click on 'Projects'
Click on 'project name'
See error

Expected behavior A list of all the tasks contained in the project.
Screenshots I could see an empty page.
Environment (please complete the following information):

OS: Ubuntu 22.04
Label Studio Version 1.7.2

Additional context The data in Label Studio is very important to me, how do I back up my data if I need to uninstall and reinstall Label Studio? Thanks a lot.

It seems to be fronted problem.The problem disappeared when I changed to use firefox

Thanks, it works. However, I wonder how to visit Label Studio through Chrome.

Yes, this is a known issue and relates to Chrome compatibility - you need to either upgrade Label Studio to the latest version or use Firefox.

I upgraded my anaconda python version from 3.7 to 3.8 with the command "conda install -c anaconda python=3.8", and after that I ran "pip install -U label-studio", Label Studio upgraded to 1.13.1.
Now, Label Studio runs well on Chrome. Thanks a lot!


Workaround for #5139 and #5450

Fixes: #5139
https://codepen.io/kurkle/pen/GPZeZz

Fixes: #5450
https://codepen.io/kurkle/pen/QzNoaE

Agree @etimberg.
It already is a bit confusing, since these configurations stack:
{ stacked: undefined, stack: 'something'}
{ stacked: true, stack: 'something' }
and this does not:
{ stacked: false, stack: 'something' }

Hmmm, if I could I'd say we should have { stacked: undefined, stack: 'something'} not stack so that it becomes an explicit opt-in feature but I don't know if that would be breaking or not. I think it's currently just undefined behaviour but the sample uses it and so many users are probably using it inadvertently.
In terms of the code here, I think it looks good. What kind of test do you think makes sense here?

Hmmm, if I could I'd say we should have { stacked: undefined, stack: 'something'} not stack so that it becomes an explicit opt-in feature but I don't know if that would be breaking or not. I think it's currently just undefined behaviour but the sample uses it and so many users are probably using it inadvertently.
In terms of the code here, I think it looks good. What kind of test do you think makes sense here?

While working on the test, I noticed that this PR is useless :)
It works exactly the same as setting stacked: true without any stack definitions, except bar width and that is wrong in this PR (2nd image in description of PR, those bars should be 2 times the width).


can it support electron

can it support electron

Should work! I haven't tried, but it uses standard web API stuff and should import cleanly as a node package.

Yes. It support.
Reference:
https://github.com/AgoraIO/Electron-SDK/blob/dev/<IP_ADDRESS>/ts/Renderer/SoftwareRenderer/index.js
https://github.com/AgoraIO/Electron-SDK


Potential issue with pachctl diff file wrapper

We are seeing an error when attempting basic usage of pachctl diff file: pattern contains path separator. Need to take a pass over this wrapper to ensure it is functioning correctly with 2.0. In general, we need more comprehensive automated testing of pachctl because several issues that have popped up through game days are related to issues with pachctl rather than underlying issues with the Go client or backend.

Closing with merge of fix: #6446


exit early if docs already built

Fixes #862
This will test if the directory exists (which would mean we already built the docs), and exit 0 to tell Travis "Hey, it's all cool".

:+1:


Asynchronous handling of long IO operations

Story
As a User, I want a visual indication that a perceptibly long operation is taking place, so that I know that Media Index hasn't just 'locked up'. Where possible and appropriate, I'd like to see the results of the operation as they become available, and also some indication of progress or how long the operation will take.
Acceptance Criteria

[ ] Integrated framework for Async operations, usable from both Qt and the mediaindex library (e.g. loading of thumbnails from a large directory)
[ ] Ability for GUI to provide:

Visual cues that an operation is taking place (e.g. 'spinner' in the status bar)
To see the results of an operation as they are available (e.g. thumbnails displayed as they are loaded)
Progress indication (e.g. progress bar in the status bar)
Responsive cancellation option

[x] Use this framework where the List View loads thumbnails

This is partially implemented. We have a simple FunctionRunner class that can execute lambdas on the Qt global thread-pool, and the list view can load thumbnails in the background), but we're going pause development of a more general background processing framework until the nature of some of our other potentially long-term tasks is clearer.
These longer-term tasks might include:

Indexing of metadata
Searching through directory structures

Issue branch merged into develop, but left open.


Archives fail to open in osx Archive Utility on versions >=0.0.52

I've been developing a feature with stream-zip and everything had been working great for about a month. I noticed after a recent library update that attempting to open the archive created by stream-zip failed to open on osx with Error 79 - Inappropriate file type or format. If i use the unzip cmd in the terminal, it unzips fine. IntelliJ is also able to peek into the archive and show me the data inside, so it appears things are still "mostly" working.
If I roll back to library 0.0.51 or below, the error goes away completely.
I'm running on an M1 Macbook Pro on Ventura 13.2.1, but others have reproduced the issue on slightly differing versions of the OS.
steps to reproduce:
slightly modifying the example on the documentation page can trigger this error. I tested with ZIP_32 and ZIP_64 compression:
from datetime import datetime
from stream_zip import ZIP_32, stream_zip

def member_files():
    modified_at = datetime.now()
    perms = 0o600

    def file_1_data():
        yield b'Some bytes 1'

    yield ('my-file-1.txt', modified_at, perms, ZIP_32, file_1_data())

zipped_chunks = stream_zip(member_files()):

with open('test.zip', 'wb') as fp:
    for zipped_chunk in zipped_chunks:
        fp.write(zipped_chunk)

additional request: I can't remember if a changelog was present prior to version 54, but it's hard to track down any potential reasons for this change without a broader context on major changes 😅
is it possible to bring back notes for versions < 54?

Hi @scott-force,
Thanks for the report. Firstly

is it possible to bring back notes for versions < 54?

So far we've never had a changelog, but more depending on the commit messages. We should probably have a more visible changelog though yes.
But on the main issue:
The main (or maybe even only) feature/code change after 51 was this one:
https://github.com/uktrade/stream-zip/commit/1130fdcb5f8a068c194392fdf5b0d8b6769a8928
Although interestingly it should have only affected ZIP_64. Just to absolutely confirm you get the issue on both ZIP_32 and ZIP_64?
(I will have a nose around and see if I can reproduce the issue myself in the meantime)
Thanks,
Michal

Although interestingly it should have only affected ZIP_64. Just to absolutely confirm you get the issue on both ZIP_32 and ZIP_64?
(I will have a nose around and see if I can reproduce the issue myself in the meantime)

I can reproduce the issue using ZIP_64, but with ZIP_32 as in your example, it seems to work fine

I'm tempted to basically revert https://github.com/uktrade/stream-zip/commit/1130fdcb5f8a068c194392fdf5b0d8b6769a8928, but I would love a test on it somehow...

Thanks for the fast reply - you are correct, I made a mistake in my testing and accidentally used the ZIP_64 data twice. ZIP_32 does in fact work well in my environment.
I am happy to help test in any way I can - I can manually make the change in https://github.com/uktrade/stream-zip/commit/1130fdcb5f8a068c194392fdf5b0d8b6769a8928 and see how it goes if that helps

I've made the change in https://github.com/uktrade/stream-zip/pull/28. If you're happy to give that a test, that would be helpful?

(Mostly just thinking out loud)
Aha - I've found that the cpio from libarchive also doesn't like the zip file made from your example with ZIP_64, and  stream-zip v0.0.56, but works fine with the change in https://github.com/uktrade/stream-zip/pull/28
Specifically
cpio -i < test.zip

gives
cpio: Inconsistent uncompressed size: 12 in central directory,<PHONE_NUMBER> in local header: Inappropriate file type or format

I can probably come up with a test
(Also it makes me wonder if Mac's Archive Utility uses libarchive under the hood...)

As expected I was able to successfully extract an archive built with ZIP_64 using the branch from https://github.com/uktrade/stream-zip/pull/28
Sounds like you've figured out how to prevent regression going forward - that's great 😄  thank you for the very quick resolution

Released fix in v0.0.57

https://pypi.org/project/stream-zip/0.0.57/
https://github.com/uktrade/stream-zip/releases/tag/v0.0.57


Assign Expressions - Step 2. towards systems engineering

Tested so far in the most trivial of cases (see below), you can now assign expressions to attributes and have them solved at build-time 🥳
module Test:
    a = 1
    b = a + 2

Which produces:
{
    'a': RangedValue(
        1.0,
        1.0,
        'dimensionless'
    ),
    'b': {
        '<removed>/test.ato:Test::b': RangedValue(
            3.0,
            3.0,
            'dimensionless'
        )
    }
}

Sounds good

Having issues combining with assertions to set component values:
simple test example:
from "generics/resistors.ato" import Resistor
module Testing1234:
voltage = 3.1V to 3.3V
current = 10mA to 12mA
resistance = voltage/current
resistor = new Resistor
resistor.footprint = "R0402"
assert resistor.value within resistance

result: