Failing debian package build because of Abseil

I'm trying to build an updated cartographer_ros debian package (commit c0e713c404d3087cec3dbe07e35bd162ce802dc0 from  Wed Aug 29 12:21:47 2018)  for internal use as following (this worked before with version 1.0):
cd ros_cartographer
bloom-generate rosdebian --os-name ubuntu --os-version xenial --ros-distro kinetic
fakeroot debian/rules binary

The cartographer_ros_msgs and cartographer (commit a351a8e from Wed Sep 5 16:59:16 2018) debian packages build fine (and are installed).
Building with catkin works fine (even building install).
Errors:
[ 25%] Building CXX object CMakeFiles/cartographer_ros.dir/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc.o
/usr/bin/c++   -DROSCONSOLE_BACKEND_LOG4CXX -DROS_PACKAGE_NAME=\"cartographer_ros\" -isystem /usr/include/lua5.2 -isystem /usr/include/pcl-1.7 -isystem /usr/include/eigen3 -isystem /opt/ros/kinetic/include -isystem /opt/ros/kinetic/share/xmlrpcpp/cmake/../../../include/xmlrpcpp -I/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu -I/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros -I/usr/src/gmock/gtest/include -isystem /usr/include/cairo -isystem /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/pixman-1 -isystem /usr/include/freetype2 -isystem /usr/include/libpng12 -isystem /opt/protobuf3/include -isystem /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2     -DEIGEN_USE_NEW_STDVECTOR -DEIGEN_YES_I_KNOW_SPARSE_MODULE_IS_NOT_STABLE_YET -pthread -std=c++11 -fPIC  -Wall -Wpedantic -Werror=format-security -Werror=missing-braces -Werror=reorder -Werror=return-type -Werror=switch -Werror=uninitialized -o CMakeFiles/cartographer_ros.dir/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc.o -c /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:111:1: error: ‘MutexImpl’ does not name a type
 MutexImpl::MutexImpl() {
 ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:116:1: error: ‘MutexImpl’ does not name a type
 MutexImpl::~MutexImpl() {
 ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:123:6: error: ‘MutexImpl’ has not been declared
 void MutexImpl::Lock() {
      ^
In file included from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/base/port.h:24:0,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/base/internal/low_level_alloc.h:51,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/mutex.h:65,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:19:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: In function ‘void absl::synchronization_internal::Lock()’:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:124:38: error: ‘pthread_mutex_’ was not declared in this scope
   ABSL_RAW_CHECK(pthread_mutex_lock(&pthread_mutex_) == 0, "pthread error");
                                      ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:125:3: error: ‘locked_’ was not declared in this scope
   locked_ = true;
   ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: At global scope:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:128:6: error: ‘MutexImpl’ has not been declared
 bool MutexImpl::TryLock() {
      ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: In function ‘bool absl::synchronization_internal::TryLock()’:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:129:46: error: ‘pthread_mutex_’ was not declared in this scope
   bool locked = (0 == pthread_mutex_trylock(&pthread_mutex_));
                                              ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:130:15: error: ‘locked_’ was not declared in this scope
   if (locked) locked_ = true;
               ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: At global scope:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:134:6: error: ‘MutexImpl’ has not been declared
 void MutexImpl::Unlock() {
      ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: In function ‘void absl::synchronization_internal::Unlock()’:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:135:3: error: ‘locked_’ was not declared in this scope
   locked_ = false;
   ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:136:3: error: ‘released_’ was not declared in this scope
   released_.SignalAll();
   ^
In file included from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/base/port.h:24:0,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/base/internal/low_level_alloc.h:51,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/mutex.h:65,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:19:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:137:40: error: ‘pthread_mutex_’ was not declared in this scope
   ABSL_RAW_CHECK(pthread_mutex_unlock(&pthread_mutex_) == 0, "pthread error");
                                        ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: At global scope:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:140:1: error: ‘CondVarImpl’ does not name a type
 CondVarImpl::CondVarImpl() {
 ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:145:1: error: ‘CondVarImpl’ does not name a type
 CondVarImpl::~CondVarImpl() {
 ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:149:6: error: ‘CondVarImpl’ has not been declared
 void CondVarImpl::Signal() {
      ^
In file included from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/base/port.h:24:0,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/base/internal/low_level_alloc.h:51,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/mutex.h:65,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:19:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: In function ‘void absl::synchronization_internal::Signal()’:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:150:39: error: ‘pthread_cv_’ was not declared in this scope
   ABSL_RAW_CHECK(pthread_cond_signal(&pthread_cv_) == 0, "pthread error");
                                       ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: At global scope:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:153:6: error: ‘CondVarImpl’ has not been declared
 void CondVarImpl::SignalAll() {
      ^
In file included from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/base/port.h:24:0,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/base/internal/low_level_alloc.h:51,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/mutex.h:65,
                 from /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:19:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: In function ‘void absl::synchronization_internal::SignalAll()’:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:154:42: error: ‘pthread_cv_’ was not declared in this scope
   ABSL_RAW_CHECK(pthread_cond_broadcast(&pthread_cv_) == 0, "pthread error");
                                          ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc: At global scope:
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:157:6: error: ‘CondVarImpl’ has not been declared
 void CondVarImpl::Wait(MutexImpl* mu) {
      ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:157:24: error: variable or field ‘Wait’ declared void
 void CondVarImpl::Wait(MutexImpl* mu) {
                        ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:157:24: error: ‘MutexImpl’ was not declared in this scope
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:157:35: error: ‘mu’ was not declared in this scope
 void CondVarImpl::Wait(MutexImpl* mu) {
                                   ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:318:1: error: expected ‘}’ at end of input
 }  // namespace absl
 ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:318:1: error: expected ‘}’ at end of input
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:39:12: warning: ‘absl::Time absl::synchronization_internal::{anonymous}::DeadlineFromTimeout(absl::Duration)’ defined but not used [-Wunused-function]
 absl::Time DeadlineFromTimeout(absl::Duration timeout) {
            ^
/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc:46:12: warning: ‘absl::Time absl::synchronization_internal::{anonymous}::LimitedDeadline(absl::Time)’ defined but not used [-Wunused-function]
 absl::Time LimitedDeadline(absl::Time deadline) {
            ^
CMakeFiles/cartographer_ros.dir/build.make:1313: recipe for target 'CMakeFiles/cartographer_ros.dir/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc.o' failed
make[4]: *** [CMakeFiles/cartographer_ros.dir/abseil/src/abseil/absl/synchronization/internal/mutex_nonprod.cc.o] Error 1
make[4]: Leaving directory '/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:5220: recipe for target 'CMakeFiles/cartographer_ros.dir/all' failed
make[3]: *** [CMakeFiles/cartographer_ros.dir/all] Error 2
make[3]: Leaving directory '/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu'
Makefile:141: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/obj-x86_64-linux-gnu'
	cd /opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros
dh_auto_install: make -j1 install DESTDIR=/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros/debian/ros-kinetic-cartographer-ros AM_UPDATE_INFO_DIR=no returned exit code 2
debian/rules:57: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 2
make[1]: Leaving directory '/opt/enway/cartographer_ws/src/cartographer_ros/cartographer_ros'
debian/rules:22: recipe for target 'binary' failed
make: *** [binary] Error 2

Shouldn't the Abseil build from the cartographer package be used for the ros package? (then I wouldn't run into these problems)
We got it to compile once, but had to manually install https://github.com/google/benchmark and also add the ${ABSEIL_INCLUDE_DIRS}, add ABSEIL to the catkin package and then it worked with some weird combination of running fakeroot debian/rules binary then fakeroot debian/rules and then fakeroot debian/rules binary which points to some missing dependencies or compile race conditions...

Interesting. Why did you need google/benchmark? As soon as https://github.com/abseil/abseil-cpp/pull/182 is submitted, it will be possible to make install abseil and reuse it in cartographer/cartographer_ros.

It is used in some of the Abseil tests, which also got build at some point.

I found the issue, the CMakeLists.txt for cartographer_ros includes all files with the ending *.cc.
If you build the package with the fakeroot command separately to generate a .deb package the file(GLOB_RECURSE ALL_SRCS "*.cc" "*.h") statement will pull in not only cartographer_ros files, but also all the Abseil files. Since all cartographer_ros files are located in a sub-folder with the same name, it's sufficient to traverse only this sub-folder, such as: file(GLOB_RECURSE ALL_SRCS "cartographer_ros/*.cc" "cartographer_ros/*.h").
The same applies for similar statements. If you want I can submit a PR with changes to the CMakeLists.txt so that it builds also with bloom-generate/fakeroot.

@redkite Yes, a PR for restricting the GLOB pattern only to the required folders would be good.


How to use Mozilla AMO badges?

How to use "Mozilla Add-on", such as:
version:
rating:
SVG file probably should take add-on name (or something else) as an argument.
Currently all values are hard-coded and thus mentioned badges are useless.

The same is true for Chrome Web Store and possibly Opera Add-ons when they arrive. As one extension may be published in several stores, I would vote for store name as a default label. This way one's able to tell which badge applies to which store. It's rather obvious that "★★★★☆" and "3.4/5" means rating, so current labels are redundant. Please, compare "mozilla add-ons | 4/5" against "rating | 4/5. By the way, "mozilla add-ons | 7k downloads" would also be better than "downloads | 7k total".
Of course customized labels should be possible too!

Hi! When you say the values are hard-coded, does that mean you can't override using ?label=?

Hi, @paulmelnikow . Yep, It's hard-coded.
I check that code for Mozilla AMO badges. This issue is for
https://github.com/badges/shields/blob/c1a8166af26d79ec2b966a56b0d0b55920df6b8d/server.js#L4150
This line should be
badgeData.text[0] = getLabel('downloads',data)

or
badgeData.text[0] = data.label || 'downloads'

Same is for rating|stars|users label

Thanks @RedSparr0w for the fix!


react-native-themis not working with react-native 0.71.0

Describe the bug
Empty react-native 0.71.0 project does not create an Android release build if react-native-themis is installed.
To Reproduce
Steps to reproduce the behavior:

npx react-native init AwesomeProject
cd  AwesomeProject
yarn add react-native-themis
cd android && ./gradlew assembleRelease

> Task :react-native-themis:verifyReleaseResources FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-themis:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
   > Android resource linking failed
     ERROR:/AwesomeProject/node_modules/react-native-themis/android/build/intermediates/merged_res/release/values/values.xml:2717: AAPT: error: resource android:attr/lStar not found.

Expected behavior
Successful build.
Environment (please complete the following information):

OS: macOS 13.1 (22C65)
Hardware: MacBook Pro 2019 Intel Core i9
Themis version: 0.14.10
Installation way:

[X] via package manager
[ ] built from source

Additional context

more context: "We updated react-native to version 0.71 and it requires gradle 7.3.3 > 7.5.1 upgrade, which in turn causes an error"

more context. last time it worked in the following configuration:
"react-native": "0.70.6"
"react-native-themis": "0.14.7",

thank you @radetsky for fixing 👏
@unixvb please take a look at new 0.14.11 hotfix for Themis RN and let us know if it works for you
https://github.com/cossacklabs/themis/releases/tag/0.14.11
https://www.npmjs.com/package/react-native-themis?activeTab=readme

@vixentael perfect, everything works
Thank you!


Missing account in indexer database

Summary
Querying my indexer for 347MBNZ2JAJR2MGF6MUQZWWZO3HJSZCVEBF7IA2FOAQD7IK6NCLMI5BN3I at round 7,000,000 yields a 404:
{
  "message": "no accounts found for address: 347MBNZ2JAJR2MGF6MUQZWWZO3HJSZCVEBF7IA2FOAQD7IK6NCLMI5BN3I"
}

Yet that account definitely had some balance at that round.
Health output:
{
  "data": {
    "migration-required": false,
    "migration-status": "Migrations Complete"
  },
  "db-available": true,
  "is-migrating": false,
  "message": "14310247",
  "round": 14310247
}

Scope/Requirements
Algorand node version: 2.6.0
Algorand indexer version: 2.4.0
Both are fully synced.
Urgency/Relative Priority
It's not highly urgent for me, but probably is for the project.

Looks like this is no longer an issue:
curl -H "X-Indexer-API-Token:$AUTH_TOKEN" "https://indexer-mainnet.internal.aws.algodev.network/v2/accounts/347MBNZ2JAJR2MGF6MUQZWWZO3HJSZCVEBF7IA2FOAQD7IK6NCLMI5BN3I?pretty"


SONOFF USB 3.0 stick running 20221226 stops responding if multiple Zigbee devices lose power

I have a SONOFF Zigbee 3.0 stick on a Raspberry Pi 3 accessed over ser2net with ~164 devices running Z-Stack 3.30+ (build 20221226).
If I power off a bunch of Zigbee devices (i.e. breaker or power failure) I can get the SONOFF stick into a state where it doesn't respond over serial, and kernel messages on the machine show:
Apr  4 01:15:55 zha-coordinator kernel: [1383198.903388] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 3
Apr  4 01:16:10 zha-coordinator kernel: [1383213.915668] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 7
Apr  4 01:16:25 zha-coordinator kernel: [1383228.923033] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 6
Apr  4 01:17:25 zha-coordinator kernel: [1383288.965764] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 0
Apr  4 01:17:40 zha-coordinator kernel: [1383303.974544] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 5
Apr  4 01:18:25 zha-coordinator kernel: [1383349.005392] WARN::dwc_otg_hcd_urb_dequeue:639: Timed out waiting for FSM NP transfer to complete on 5

I can only fix it by restarting the machine or re-plugging the USB device, and then restarting HomeAssistant or reloading the integration. ZHA just responds with the following if I don't restart or re-plug the USB device:
2023-04-03 18:48:33.065 WARNING (MainThread) [homeassistant.components.zha.core.gateway] Couldn't start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator (attempt 1 of 3)
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 665, in _skip_bootloader
    result = await responses.get()
  File "/usr/local/lib/python3.10/asyncio/queues.py", line 159, in get
    await getter
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 185, in async_initialize
    self.application_controller = await app_controller_cls.new(
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 171, in new
    await app.startup(auto_form=auto_form)
  File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 145, in startup
    await self.connect()
  File "/usr/local/lib/python3.10/site-packages/zigpy_znp/zigbee/application.py", line 107, in connect
    await znp.connect()
  File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 707, in connect
    self.capabilities = (await self._skip_bootloader()).Capabilities
  File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 664, in _skip_bootloader
    async with async_timeout.timeout(CONNECT_PROBE_TIMEOUT):
  File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 129, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 212, in _do_exit
    raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

Switching to dwc2 on the RPi did not fix my issue, I can reproduce every time I flip a bunch of power on lights:
Apr  9 19:24:26 zha-coordinator kernel: [439986.981446] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Apr  9 19:24:26 zha-coordinator kernel: [439986.981603] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Apr  9 19:24:26 zha-coordinator kernel: [439987.009525] usb 1-1.4: USB disconnect, device number 4
Apr  9 19:24:26 zha-coordinator kernel: [439987.010025] cp210x ttyUSB0: failed set request 0x12 status: -19
Apr  9 19:24:26 zha-coordinator kernel: [439987.010054] cp210x ttyUSB0: failed set request 0x0 status: -19
Apr  9 19:24:26 zha-coordinator kernel: [439987.010829] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Apr  9 19:24:26 zha-coordinator kernel: [439987.018592] cp210x 1-1.4:1.0: device disconnected
Apr  9 19:24:27 zha-coordinator kernel: [439987.348531] usb 1-1.4: new full-speed USB device number 5 using dwc2
Apr  9 19:24:27 zha-coordinator kernel: [439987.452150] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Apr  9 19:24:27 zha-coordinator kernel: [439987.452193] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr  9 19:24:27 zha-coordinator kernel: [439987.452216] usb 1-1.4: Product: Sonoff Zigbee 3.0 USB Dongle Plus
Apr  9 19:24:27 zha-coordinator kernel: [439987.452237] usb 1-1.4: Manufacturer: ITead
Apr  9 19:24:27 zha-coordinator kernel: [439987.452256] usb 1-1.4: SerialNumber: a6d9bdd3aac9eb11848a8f4f1d69213e
Apr  9 19:24:27 zha-coordinator kernel: [439987.453812] cp210x 1-1.4:1.0: cp210x converter detected
Apr  9 19:24:27 zha-coordinator kernel: [439987.457775] usb 1-1.4: cp210x converter now attached to ttyUSB0

Can you test the new fw and provide feedback here? https://github.com/Koenkk/Z-Stack-firmware/issues/439

hi @Koenkk:
I am using the new firmware in #439 now (20230410). I can no longer reproduce this issue that I reported.
However, with 20230410 I am seeing 1) Latency on commands, and 2) The stick becoming unresponsive as the network was being rebuilt after upgrading, 3) Great difficulty pairing Inovelli VZM31-SN switches, it is taking >5 attempts to pair them.

Removing RPi from the mix, and ser2net:
20230410 = Spewing lots of max concurrency errors, very slow response and finally the stick stops responding
20221226 = Network immediately comes back up and is responsive

On 20230410, in home assistant logs with ZHA debugging enabled. After upgrading the firmware, I immediately get high requests, which is expected, but they do not level off:
2023-04-13 20:08:34.297 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (290 enqueued)
2023-04-13 20:08:34.332 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (291 enqueued)
2023-04-13 20:08:34.360 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (292 enqueued)
2023-04-13 20:08:34.440 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (293 enqueued)
2023-04-13 20:08:42.023 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (278 enqueued)
2023-04-13 20:08:42.050 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (279 enqueued)
2023-04-13 20:08:42.059 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (280 enqueued)
2023-04-13 20:08:42.105 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (281 enqueued)
2023-04-13 20:08:42.212 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (282 enqueued)
2023-04-13 20:08:42.219 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (283 enqueued)
2023-04-13 20:08:42.244 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (284 enqueued)
2023-04-13 20:08:42.264 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (285 enqueued)
2023-04-13 20:08:42.303 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (286 enqueued)
2023-04-13 20:08:42.370 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (287 enqueued)
2023-04-13 20:08:42.374 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (288 enqueued)
2023-04-13 20:08:42.407 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (289 enqueued)
2023-04-13 20:08:42.416 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (290 enqueued)
2023-04-13 20:08:42.444 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (291 enqueued)
2023-04-13 20:08:42.458 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (292 enqueued)
2023-04-13 20:08:42.467 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (293 enqueued)
2023-04-13 20:08:44.701 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (294 enqueued)
2023-04-13 20:08:50.721 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (0 enqueued)
2023-04-13 20:08:50.722 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (1 enqueued)
2023-04-13 20:08:50.730 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (2 enqueued)
2023-04-13 20:08:50.733 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (3 enqueued)
2023-04-13 20:08:50.735 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (4 enqueued)
2023-04-13 20:08:50.736 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (4 enqueued)
2023-04-13 20:08:50.738 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (5 enqueued)
2023-04-13 20:08:50.739 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (6 enqueued)
2023-04-13 20:08:50.741 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (7 enqueued)
2023-04-13 20:08:50.746 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (7 enqueued)
2023-04-13 20:08:50.747 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (8 enqueued)
2023-04-13 20:08:50.759 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (7 enqueued)
2023-04-13 20:08:50.760 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (8 enqueued)
2023-04-13 20:08:50.760 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (9 enqueued)
2023-04-13 20:08:50.778 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (8 enqueued)
2023-04-13 20:08:50.781 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (9 enqueued)
2023-04-13 20:08:50.785 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (9 enqueued)
2023-04-13 20:08:50.786 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (10 enqueued)
2023-04-13 20:08:50.787 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (11 enqueued)
2023-04-13 20:08:50.810 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (9 enqueued)
2023-04-13 20:08:50.831 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (8 enqueued)
2023-04-13 20:08:50.832 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (9 enqueued)
2023-04-13 20:08:50.836 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (10 enqueued)
2023-04-13 20:08:50.847 DEBUG (MainThread) [zigpy.application] Max concurrency (16) reached, delaying request (10 enqueued)

For 2023-03-13, which is a mix of 20230410 and 20221226:
$ grep -E '^2023-04-13.*Max concurrency' home-assistant.log | wc -l
13081

As soon as I downgraded to 20221226 the max concurrency messages are very little. 2023-04-14 I have only been running 20221226:
$ grep -E '^2023-04-14.*Max concurrency' home-assistant.log | wc -l
63

Can you let me know what details you'd like? I have a complete log of me upgrading, downgrading and trying various things but it's a couple GiB in size.

I'm not familiar with the ZHA logging, is there any way to see responses from the adapter?

@Koenkk Is this helpful? puddly suggested I include zigpy_znp.api to narrow down to Z-Stack itself.
But being a layman all I see is that the stick has stopped responding and then comes back?
See attached.

I see this a lot of times in the log:
2023-04-13 20:08:49.745 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x1ECA:11:0x0008]: failed to get attributes '['current_level']' on 'level' cluster: Expected SRSP response AF.DataRequestExt.Rsp(Status=<Status.SUCCESS: 0>), got AF.DataRequestExt.Rsp(Status=<Status.INVALID_PARAMETER: 2>)

Especially <Status.INVALID_PARAMETER: 2> is interesting, it seems ZHA sends invalid request to the coordinator, this should be fixed first in ZHa

@Koenkk
The original issue (USB stick crashing) with 20221226 was resolved by removing ser2net and RPi 3 from the equation. I can verify that without ser2net in the mix, the controller works reliably under conditions where I flip a breaker and a bunch of devices lose power.
I am hard pressed to understand how if 20221226 is working fine, that the issues with 20230410 that are 100% reproducible when switching are related to ZHA, since as soon as I downgrade to 20221226 the issues resolve.
puddly mentioned they can't do much if the USB coordinator disappears out from under them, as they can't communicate with them anymore.
We can close this issue out and I can provide further discussion on the other issue if you believe it is still a ZHA issue.


pin azure-cli to 2.46.0

Which issue this PR addresses:

Fixes issue with make test-python which was pulling the latest azure-cli. There appear to be some upstream changes that are currently breaking our tests.
What this PR does / why we need it:

Test plan for issue:

Is there any documentation that needs to be updated for this PR?

this will be fixed by 2.48.0 > https://github.com/Azure/azure-cli/issues/26211


Brainstorm ways to visualize the polls

Average favorability over time across all countries? By country? etc.

Single poll (full response set) - should have filters available for crosstabs
Multiple polls over time with net favorability - should have filters available for crosstabs
Single poll with crosstabs for a given crosstab
Crosstabs over time
For all trends, option to add trendline a la https://projects.fivethirtyeight.com/biden-approval-rating
Option to show table

cc @kvanalebeek


Modernize contribute script

Updates the contribute script to use docker-compose instead of the outdated docker-machine.

Hey @clayellis, you just merged a pull request, have a coin!
You now have 16 coins.


skydns cannot use port as a string

Hi there,
Just by accident I added host info with port as a string to etcd and skydns stopped resolving that domain at all.
skydns:
docker run --rm -p 153:53/udp -e ETCD_MACHINES='http://<IP_ADDRESS>:4001' \
skynetservices/skydns:2.2.0b -nameservers="<IP_ADDRESS>:" -verbose=true -addr=<IP_ADDRESS>:53

etcd:
docker run --rm -p <IP_ADDRESS>:4001:4001 quay.io/coreos/etcd

add valid record:
curl -XPUT http://<IP_ADDRESS>:4001/v2/keys/skydns/local/skydns/east/production/rails/1 \
-d value='{"host":"service1.example.com","port":8080}'

try to resolve:
dig @<IP_ADDRESS> -p 153 SRV +short rails.production.east.skydns.local
# => 10 100 8080 service1.example.com.

add another record but port as a string:
curl -XPUT http://<IP_ADDRESS>:4001/v2/keys/skydns/local/skydns/east/production/rails/2 \
-d value='{"host":"service1.example.com","port":"8080"}'

then:
dig @<IP_ADDRESS> -p 153 SRV +short rails.production.east.skydns.local

returns nothing. With verbose flag I see just:
2015/05/06 10:41:51 skydns: received DNS Request for "rails.production.east.skydns.local." from "<IP_ADDRESS>:55595" with type 33

I'm not sure about the reason, why port is not supported as a string, but I'd really appreciate to see some error message about it.
If there is any particular reason for not supporting port as a string, would be nice to know it from documentation.
Thanks!

PR for betters doc welcome.
You're right that skydns should logging something. Returning an error DNS message might not be appropriate as they are may be other services that just marshal fine. And SkyDNS should returns something always - so that's def. a bug.

Add a log.Printf in the marshalling branch. I'm a bit ambivalent on if we should care if the json is kaput. I think we should and the quickest way is to break responses. (which happened in the above case).
Anyway things like this should also be exported to a monitoring system, but I will do that when I get around to #171.


Sort out GHA set-output deprecation warnings

This pr addresses the following:

the GHA set-output deprecation warning
the lack of a versioned distribution build

See the following for more information on GHA set-output deprecation:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

@clydetealium Thanks for your contribution! Any update on this?

Sorry for the delay. I merged the #41 PR that had the same changes. Thanks @clydetealium !


DOC: Passing State in Tools is no longer supported

Issue with current documentation:
https://langchain-ai.github.io/langgraph/how-tos/pass-run-time-values-to-tools/
this no longer works.
I wanted to point it out but also I'd like to know what is the alternative.
Right now I have been passing config to tools, but this is not ideal.
Is there a new way of passing state to tools? Thanks
Idea or request for content:
No response

@streamnsight What error are you getting, and what version of LangGraph are you using?

just running the code, can't import InjectedState

Now I just upgraded and with 0.2.0 it works.
So, I guess the docs were published way before the code was released, because it was there a little while ago with 0.1.8, when it was the latest release, which is when I tried and it didn't work.


ReactVideoView does not clean up correctly

Bug

ReactVideoView manages its own instance of MediaPlayer and calls SetMediaPlayer() to initialize MediaPlayerElement.
However, it never calls SetMediaPlayer(null) and does not call Close on the MediaPlayer instance. This makes a lingering active MediaPlayer instance that sometimes makes the entire app crash as Xaml cannot handle an active MediaPlayer while the Xaml Element is no longer in the Xaml tree.
Platform

Which player are you experiencing the problem on:

Windows UWP

Environment info

React native info output:
 // paste it here

Library version: x.x.x
Steps To Reproduce

This has been reported in the wild and is a heavy hitter for apps that use Media.
Expected behaviour
No crash after Media have exited the tree.
Reproducible sample code
N/A

Video sample
If possible, include a link to the video that has the problem that can be streamed or downloaded from.
N/A

Sounds like you know how to fix it ;) Mind submitting a PR?


Mark intranet/extranet as a class

Result: html.geo-office-internal and html.geo-office-nyhq / html.geo-office-dc....

One point here: so long as this repo is public, we probably should provide the IP range as a an ENV config.
I suppose this would have to be some kind of JSON object.  Perhaps we could pass a { cird : label } object and then use something like https://github.com/skx/cidr_match.js to evaluate?
The config could look something like this:
{ "<IP_ADDRESS>/24" : "office-1", "<IP_ADDRESS>/32" : "office-2" }

Abandoned.  Not really needed at this time.


facets with user defined label header

how to implement recline facet with label as a header instead of id?

WONTFIX. (This is probably a question for the forum!)
Reason: age of issue and spring cleaning (not anything about the idea!)


TypeScript error in overloading UserResolver's deleteManyUser mutation

Describe the Bug
So it was several months before I got my hands on my code again, and since I'd learned a lot, I decided to start from scratch.
It turns out that, when I try to replace the behavior of one of the generated CRUDs (which was originally working ?), in this case deleteMany and deleteOne, I get an error with typescript :
import { Resolver, Mutation, Ctx, Info, Args } from "type-graphql";
import {
    User,
    UserCrudResolver,
    type DeleteManyUserArgs,
    type DeleteOneUserArgs,
    AffectedRowsOutput,
} from "@generated/type-graphql";
import { GraphQLResolveInfo } from "graphql";
import { Context } from "@/context";

@Resolver(() => User)
export class UserResolver extends UserCrudResolver {
    @Mutation(() => AffectedRowsOutput)
    async deleteManyUser(@Ctx() ctx: Context, @Info() info: GraphQLResolveInfo, @Args() args: DeleteManyUserArgs): Promise<AffectedRowsOutput> {
        return ctx.prisma.user.deleteMany({ ...args, where: { ...args.where, persistent: false }});
    }

    @Mutation(() => User)
    async deleteOneUser(@Ctx() ctx: Context, @Info() info: GraphQLResolveInfo, @Args() args: DeleteOneUserArgs): Promise<User | null> {
        const user = await ctx.prisma.user.findUnique({ ...args });
        if (!user || user.persistent) return null;

        return ctx.prisma.user.delete({ ...args });
    }
}

/Users/suiramdev/Projects/storedge/core/node_modules/.pnpm/type-graphql@2.0.0-beta.3_class-validator@0.14.0_graphql-scalars@1.22.2_graphql@16.8.1/node_modules/type-graphql/build/cjs/helpers/findType.js:25
        throw new errors_1.NoExplicitTypeError(prototype.constructor.name, propertyKey, parameterIndex, argName);
              ^
NoExplicitTypeError: Unable to infer GraphQL type from TypeScript reflection system. You need to provide explicit type for parameter #2 of 'deleteManyUser' of 'UserResolver' class.
    at findType (/Users/suiramdev/Projects/storedge/core/node_modules/.pnpm/type-graphql@2.0.0-beta.3_class-validator@0.14.0_graphql-scalars@1.22.2_graphql@16.8.1/node_modules/type-graphql/build/cjs/helpers/findType.js:25:15)
    at getParamInfo (/Users/suiramdev/Projects/storedge/core/node_modules/.pnpm/type-graphql@2.0.0-beta.3_class-validator@0.14.0_graphql-scalars@1.22.2_graphql@16.8.1/node_modules/type-graphql/build/cjs/helpers/params.js:10:62)
    at /Users/suiramdev/Projects/storedge/core/node_modules/.pnpm/type-graphql@2.0.0-beta.3_class-validator@0.14.0_graphql-scalars@1.22.2_graphql@16.8.1/node_modules/type-graphql/build/cjs/decorators/Args.js:12:42
    at /Users/suiramdev/Projects/storedge/core/src/schema/resolvers/user.ts:12:37
    at DecorateProperty (/Users/suiramdev/Projects/storedge/core/node_modules/.pnpm/reflect-metadata@0.1.13/node_modules/reflect-metadata/Reflect.js:553:33)
    at Reflect.decorate (/Users/suiramdev/Projects/storedge/core/node_modules/.pnpm/reflect-metadata@0.1.13/node_modules/reflect-metadata/Reflect.js:123:24)
    at __decorate (/Users/suiramdev/Projects/storedge/core/src/schema/resolvers/user.ts:4:92)
    at Object.<anonymous> (/Users/suiramdev/Projects/storedge/core/src/schema/resolvers/user.ts:15:11)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)
    at Module.m._compile (/Users/suiramdev/Projects/storedge/core/node_modules/.pnpm/ts-node@10.9.1_@types+node@20.8.2_typescript@5.2.2/node_modules/ts-node/src/index.ts:1618:23)

I can't figure out why, I've tried a bunch of things, and it sometimes warns me of the same thing on the @Ctx() field.

It can't be a type DeleteManyUserArgs as it's erased during compilation and TypeGraphQL has no type reflection available for @Args() args: DeleteManyUserArgs

Oh. Sorry for taking up your time. In fact, that was the cause of the problem, now I get it.
For anyone who cares, here is what my resolver looks like, so :
import { Resolver, Mutation, Ctx, Arg } from "type-graphql";
import {
    User,
    UserWhereInput,
    UserWhereUniqueInput,
    AffectedRowsOutput,
} from "@generated/type-graphql";
import { GraphQLError } from "graphql";
import { Context } from "@/context";

@Resolver(() => User)
export class UserResolver {
    @Mutation(() => AffectedRowsOutput)
    async deleteManyUser(@Ctx() ctx: Context, @Arg("where") where: UserWhereInput): Promise<AffectedRowsOutput> {
        return ctx.prisma.user.deleteMany({ where: { ...where, persistent: false }});
    }

    @Mutation(() => User, { nullable: true })
    async deleteOneUser(@Ctx() ctx: Context, @Arg("where") where: UserWhereUniqueInput): Promise<User | null> {
        const user = await ctx.prisma.user.findUnique({ where });
        if (!user) return null;
        if (user.persistent) throw new GraphQLError("Cannot delete a persistent user");

        return ctx.prisma.user.delete({ where });
    }
}


Add Back/Next buttons to 'New Alignment' interface

instead of having to click 1, 2, 3, etc.

Moved to wish list.


EEFACE in DunitX test resets floating point control word in other tests

Steps to reproduce:

Disable floating point exceptions in _tmain with _control87(MCW_EM, MCW_EM);
Do something in one test, which would normally cause floating point exception, such as division by zero
Tests run normally
Change some other test, so that it throws external exception EEFACE
The former test now causes floating point exception, even though they were disabled in _tmain

Expected behavior:
The other test should not cause floating point exceptions in any case, because they were disabled in _tmain.
Environment:
C++ Builder 10.1, new Clang compiler, C++ language
Using version of DunitX that came with C++ Builder 10.1: "rev: 31.00 (Windows)"
Developing on Windows 7, building for 32-bit Windows target
I have made identical bug report to Embarcadero, in case this is a bug in the compiler: https://quality.embarcadero.com/browse/RSP-15899

As far as I know, DUnitX does not do any enabling/disabling floating point exceptions, so my guess is the rtl or other external code would be the culprit.

Closing, if you have a reproducable test case, submit a pull request with a failing test added to the Tests project.


Rename props:  direction to orientation in Button package

Description
related #3428
Problem Statement/Justification
ButtonGroup component is needed for the following tasks.

[ ] Rename direction to orientation
[ ] Add @deprecated to direction

Proposed Solution or API
No response
Alternatives
No response
Are you willing to participate in implementing this feature and create a pull request include the implementation?
None
Additional Information
No response

The shorthand property for direction does not need to be set to orientation, just like flexDirection.


Can't build the repo with meson_init.sh

While running the meson_init.sh in the OpenTitan repo, I'm getting the following error. Basically, I'm unable to build it, I think there is/are pre-requisite step(s) missing before the build can be invoked with meson-init.sh. Can I get a full list of dependencies/pre-requisites needed to build this on Ubuntu Server 20.04?
Detected $REPO_TOP at /home/vagrant/opentitan.
Object directory set at /home/vagrant/opentitan/build-out.
Binary directory set at /home/vagrant/opentitan/build-bin.
OpenTitan version: opentitan-earlgrey_silver_release_v5-1547-g37162df49

Output directory already exists at /home/vagrant/opentitan/build-out; skipping.
Set up toolchain file at /home/vagrant/opentitan/build-out/toolchain-configured.txt.
+ meson -Dot_version=opentitan-earlgrey_silver_release_v5-1547-g37162df49 -Dbin_dir=/home/vagrant/opentitan/build-bin -Dkeep_includes=false -Dcoverage=false --cross-file=/home/vagrant/opentitan/build-out/toolchain-configured.txt /home/vagrant/opentitan/build-out
DEPRECATION: c_args in the [properties] section of the machine file is deprecated, use the [built-in options] section.
The Meson build system
Version: 0.59.2
Source dir: /home/vagrant/opentitan
Build dir: /home/vagrant/opentitan/build-out
Build type: cross build
Project name: opentitan
Project version: 0.1

meson.build:5:0: ERROR: Unknown compiler(s): [['/tools/riscv/bin/riscv32-unknown-elf-gcc']]
The following exception(s) were encountered:
Running "/tools/riscv/bin/riscv32-unknown-elf-gcc --version" gave "[Errno 2] No such file or directory: '/tools/riscv/bin/riscv32-unknown-elf-gcc'"

A full log can be found at /home/vagrant/opentitan/build-out/meson-logs/meson-log.txt

can you follow the instructions shown here?
https://docs.opentitan.org/doc/ug/install_instructions/
On Sat, Oct 16, 2021 at 12:14 AM saki-osive @.***>
wrote:

While running the meson_init.sh in the OpenTitan repo, I'm getting the
following error. Basically, I'm unable to build it, I think there is/are
pre-requisite step(s) missing before the build can be invoked with
meson-init.sh. Can I get a full list of dependencies/pre-requisites needed
to build this on Ubuntu Server 20.04?
Detected $REPO_TOP at /home/vagrant/opentitan.
Object directory set at /home/vagrant/opentitan/build-out.
Binary directory set at /home/vagrant/opentitan/build-bin.
OpenTitan version: opentitan-earlgrey_silver_release_v5-1547-g37162df49
Output directory already exists at /home/vagrant/opentitan/build-out; skipping.
Set up toolchain file at /home/vagrant/opentitan/build-out/toolchain-configured.txt.

meson -Dot_version=opentitan-earlgrey_silver_release_v5-1547-g37162df49 -Dbin_dir=/home/vagrant/opentitan/build-bin -Dkeep_includes=false -Dcoverage=false --cross-file=/home/vagrant/opentitan/build-out/toolchain-configured.txt /home/vagrant/opentitan/build-out
DEPRECATION: c_args in the [properties] section of the machine file is deprecated, use the [built-in options] section.
The Meson build system
Version: 0.59.2
Source dir: /home/vagrant/opentitan
Build dir: /home/vagrant/opentitan/build-out
Build type: cross build
Project name: opentitan
Project version: 0.1

meson.build:5:0: ERROR: Unknown compiler(s): [['/tools/riscv/bin/riscv32-unknown-elf-gcc']]
The following exception(s) were encountered:
Running "/tools/riscv/bin/riscv32-unknown-elf-gcc --version" gave "[Errno 2] No such file or directory: '/tools/riscv/bin/riscv32-unknown-elf-gcc'"
A full log can be found at /home/vagrant/opentitan/build-out/meson-logs/meson-log.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/8707, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSSJ6KG42VJZEFJSVDTUHEQ5ZANCNFSM5GDKTA6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

o but to your question, if you're just trying to get the elf file, no you
don't need vivado.
just install the tool chain, the python modules etc.
On Sat, Oct 16, 2021 at 1:24 AM Timothy Chen @.***> wrote:

just install whatever you need. The guide is meant to be comprehensive if
you need everything.
On Sat, Oct 16, 2021 at 1:13 AM saki-osive @.***>
wrote:

Hello, thank you for your reply, actually I need to leverage the project
for using it with Tock OS without a board. Do I really need Vivado for
it?
tock/tock#2868 https://github.com/tock/tock/discussions/2868
Can you check this?
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/8707#issuecomment-944878590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSVYF66L6UKBHD4H3OLUHEX3TANCNFSM5GDKTA6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

While following this https://docs.opentitan.org/doc/ug/install_instructions/ in order, my build is still breaking at:
./meson-init.ah
Here is the output:
vagrant@vagrant:~/opentitan$ ./meson_init.sh
Detected $REPO_TOP at /home/vagrant/opentitan.
Object directory set at /home/vagrant/opentitan/build-out.
Binary directory set at /home/vagrant/opentitan/build-bin.
OpenTitan version: opentitan-earlgrey_silver_release_v5-1575-g4ac735964

Output directory does not exist at /home/vagrant/opentitan/build-out; creating.
Set up toolchain file at /home/vagrant/opentitan/build-out/toolchain-configured.txt.
+ meson -Dot_version=opentitan-earlgrey_silver_release_v5-1575-g4ac735964 -Dbin_dir=/home/vagrant/opentitan/build-bin -Dkeep_includes=false -Dcoverage=false --cross-file=/home/vagrant/opentitan/build-out/toolchain-configured.txt /home/vagrant/opentitan/build-out
DEPRECATION: c_args in the [properties] section of the machine file is deprecated, use the [built-in options] section.
The Meson build system
Version: 0.59.2
Source dir: /home/vagrant/opentitan
Build dir: /home/vagrant/opentitan/build-out
Build type: cross build
Project name: opentitan
Project version: 0.1

meson.build:5:0: ERROR: Unknown compiler(s): [['/tools/riscv/bin/riscv32-unknown-elf-gcc']]
The following exception(s) were encountered:
Running "/tools/riscv/bin/riscv32-unknown-elf-gcc --version" gave "[Errno 2] No such file or directory: '/tools/riscv/bin/riscv32-unknown-elf-gcc'"

A full log can be found at /home/vagrant/opentitan/build-out/meson-logs/meson-log.txt

Please discuss this @tjaychen

@saki-osive could you resolve the build problems on your end? If yes, please close the issue.


[docopt_macros] Update to rustc 0.13.0-nightly (c7dd3c4d6 2015-01-05 23:51:00 +0000)

I was just about to fix this! Beat me to it. Thank you! :-)

OK, I've updates crate.io with this change in 0.6.25.


Documentation: General Work Email Signup

In addition to Signup With GitHub, Amplication will support signing up with a work email and password. The purpose of this issue is to update the documentation where necessary so that any references to signing up with GitHub specifically are instead made more general.

@PazYanoverr

@dericksozo - Sounds great. Let's avoid removing / ignoring the github signup mentions from the documentation

I'm taking care of this Issue in PR #431.

@PazYanoverr, I see this one in production now. Can we merge?

We can, but I see there is still one pending comment. Can you handle please?


i18n(ja): Add new cloudflare.mdx  translation

Description (required)

Translate cloudflare.mdx into Japanese！
file: guides/deploy/cloudflare.mdx
Related issues & labels (optional)

Closes #
Suggested label:

Hi @piro-hiroki ! Just checking if this PR should still be marked as a draft?
If it's ready for editing, then please change the status so that it is ready for review! We are hoping to merge as many PRs by next week as we can before the docs site code migrates to Starlight. So if this is ready, we would like to be able to review it.  Thanks!

Hi @piro-hiroki ! Is this one ready for a review now?


Being able to add Command Line Arguments as Environment Variables for docker version

Hello
That would be very great and super easy for everyone if you consider adding an option to be able to add Command Line Arguments as Environment Variables for docker version.

It's already implemented. You can use MICROBIN_BIND=<IP_ADDRESS> for --bind <IP_ADDRESS> or MICROBIN_PRIVATE=true for --private.

@PerchunPak Thank you for the answer, where can I find the full list/guide?

Just look at text in brackets in docs. And do not forget append to every key MICROBIN_ prefix, so if you see AUTH_USERNAME actual environment variable would be MICROBIN_AUTH_USERNAME=some_value.

Thanks a lot mate, highly appreciated.

NP, please close this, as it seems like resolved.

Might want to update the URL here, as it's broken. And the document does not make it clear that the command line arguments are not what is documented:
https://microbin.eu/docs/installation-and-configuration/configuration
MICROBIN_BASIC_AUTH_USERNAME is actually --basic_auth_username etc.


clipboard

management clipboard lack, needed to overcome the problem of type special characters like ® and ™.

This can be done using the pyperclip module. Since this is beyond the scope of pyautogui (there's no keyboard key for  ® and ™) I got to close this. Although I will open a new issue for pyautogui providing an easy way to insert these non-keyboard characters.

Thanks!

Actually, you know what, I'll reopen this. The only way to do this feature (that I can think of) is with pasting clipboard contents.

This works in pyperclip 1.5.26


Lab 1.5 typo

In the "Create Topic" section of Lab 1.5 the setting user number instruction is repeated twice.

Closing, this should have been created against the dashboard, not the code.


Upgrade embedded GLEW to version 1.13.0

Also drop all our customisations of the upstream files, by:

Fixing the buggy Haiku setup (GLEW usage on Haiku should be investigated by users of this platform, grepping for __HAIKU__ does give matches in the GLEW code, so it might be supported now)
Use SCons magic to make a static build, instead of hardcoding it in the source files

Fixes #5087.

Fails to compile on MSVC: .\drivers/gles2/rasterizer_gles2.h(51): fatal error C1083: Cannot open include file: 'gl_context/glew.h': No such file or directory

Thanks, I've fixed that locally, I'll soon push a rebased version.
I also noticed that I had forgotten to readd the #ifdef GLEW_ENABLED in glew.c, so I'm working on a SCons-based variant to have the same behaviour without having to touch the upstream source file.

Rebased and added a commit for the GLEW_ENABLED stuff :)


The enchant package no longer supports French

Line 19 of utils/helper.py calls the enchant.Dict('fr') instruction. However, after installing the enchant-2 library via apt-get under Ubuntu, on which pip's pyenchant depends, the latter returns False when executing the enchant.dict_exists("fr") instruction and does not list French (tag "fr") when executing the enchant.list_languages() instruction.
Consequently, testing the corrector via the python command autocorrector.py path/to/file returns an enchant.errors.DictNotFoundError: Dictionary for language 'fr' could not be found error.

Note: It would also be helpful to specify the structure of the file to be tested. Is it one sentence per line, one word per line!? etc.

Thank you for flagging the issue. I am going to work on it.
Note that you can use whatever structure you want for the text.

You're welcome master. Thanks for the information!


boards/odroid_go: Add bluetooth support

Add bluetooth support
Signed-off-by: Yannis Damigos<EMAIL_ADDRESS>

@sylvioalves @glaubermaroto please take a look

@ydamigos Sorry I missed this before.


Make running test easier

Currently I have to install make to run tests but it's easier to move ./node_modules/.bin/mocha -u tdd --reporter spec to npm scripts. npm test will still work and I don't think there will be problems with Travis CI too. Any reason not to do this?

No reason that I know of, as long as we can locally test & travis accepts it.

In that case I'll send a PR tomorrow and we'll see if Travis likes this idea.


Views on dom manipulation in requestIdleCallback

It suggested that we should avoid dom updates in the requestIdleCallback and use requestAnimationFrame instead. Will using this library cause dom updates during requestIdleCallback or is it upto react to find the right time and handle it accordingly?

@swapnil95 great question. requestIdleCallback will trigger a vdom update only and React handles the right time to update the DOM. Regardless of that, I think you have a point - we should wrap the callback into a rAF just to play safe

This was fixed in v1.1.0. Thank you for reporting @swapnil95


feat: resolve --cert from URL

Summary
verify and verify-blob's --cert param should accept an URL as well, so we can verify without previously downloading files, e.g.:
cosign verify-blob \
  --cert https://github.com/goreleaser/supply-chain-example/releases/download/v1.0.0/checksums.txt.pem \
  --signature https://github.com/goreleaser/supply-chain-example/releases/download/v1.0.0/checksums.txt.sig \
  https://github.com/goreleaser/supply-chain-example/releases/download/v1.0.0/checksums.txt

Ticket Link
https://github.com/gythialy/golang-cross/pull/67/files#r774120479
Release Note
verify and verify-blob resolve --cert from URL

This is safe IMO - the cert itself is signed by fulcio and must be in a transparency log, so the location of it can be untrusted.


[Spring Data Support] Make sure all features are included in reference doc. @backwind1233

Close this issue, since no new feature was added in 4.0 and existing features were included in reference doc.


Font  and Footer

As a part of GSSOC'23, I would like to change the font properties to increase the readability of the website as well I would like to improve the footer section of the website. Kindly assign me this issue to work on.

Sure @akshathar-navada

@akshathar-navada I have opened a PR. I am adding the links of the screenshot of the changes I have made in the website.
I have changed the font properties like color and font-weight to increase the readability. Also, I have made some changed in the footer section to make it look clean.
https://drive.google.com/file/d/1-FjG0yAyXuMeTBHk0MILBg_I5KaGwzOH/view?usp=sharing, https://drive.google.com/file/d/13RvwbegMcQ7pr54Pb-iKY6aiUyMmc9YD/view?usp=sharing, https://drive.google.com/file/d/1FjkWYz2McEUsmxUzNaN-AWqXbDBwfako/view?usp=sharing, https://drive.google.com/file/d/1e6hC4Zwk2CQ-4kSAsPEATgfl8aT2DWUK/view?usp=sharing, https://drive.google.com/file/d/1tAEjCFwL4bPHwFbS13Aq_vka_xL8seUD/view?usp=sharing


Update extensionsGallery.json for arc and azcli 1.2

Updates stable and insiders extension galleries to have arc and azcli version 1.2.0.

VSIX files for the arc extension and azcli extension can be found here: https://mssqltools.visualstudio.com/CrossPlatBuildScripts/_build/results?buildId=151820&view=results


Collapse bottom panel if there is no active tab

Fixes #79022

Thanks!

Cherry-picked for 4.1.1.


[epic] Modchat Bot

All PRs related to Modchat bot creation should be linked to this issue.
Spec for Modchat bot:
https://github.com/cscareerhub/megabot/blob/master/specs/modchat.spec.md

Closing as will keep track of specific bot through labels


[v1.29.0] Responsive Maestro Studio

Describe the bug
As you can see from the video when you minimize the window, it is no longer responsive, it happens with all tested browsers which are: Chrome, Firefox, Safari.
Chrome:
https://github.com/mobile-dev-inc/maestro/assets/20476002/fe32879e-62c9-4f73-85d4-a207de11121e

Firefox:

Safari:

To Reproduce

Minimize your window browser

Environment information (please complete the following information):

Maestro version 1.29.0
Platform: Chrome, Firefox, Safari

Hey, it'll be hard to provide a good responsive experience, and we don't have any plans for that.
a bit reluctantly I consider this working as intended.


Fodlereyez is one I made

https://github.com/jayber/fodlereyez
A colourful folder size tui
If it floats your boat ;-)

Hi @jayber . Thanks for this submission.
Unfortunately, as per my very new and relatively arbitrary submission criteria, I'm going to try to wait for projects to get 100 or more stars on GitHub before adding them to the list. I hope you understand. Thanks for the submission though!


disable cgo when building go code

Summary
The build settings have been changed so that the executable binary will run regardless of the execution environment.
Changes Made

Added CGO_ENABLED=0 when compiling custom handler for each OS.

Background
In the current document, the custom handler is built with dynamic link.
If you continue using this method, an error will occur when you deploy to Azure Functions, and the function will not run.  That's presumably because the dependent C library is not placed in the execution environment. Therefore, I changed it to build the custom handler with static link.
Additional Notes

The need to set CGO_ENABLED=0 is described in the official Go documentation below.

The cgo tool is enabled by default for native builds on systems where it is expected to work. It is disabled by default when cross-compiling as well as when the CC environment variable is unset and the default C compiler (typically gcc or clang) cannot be found on the system PATH. You can override the default by setting the CGO_ENABLED environment variable when running the go tool: set it to 1 to enable the use of cgo, and to 0 to disable it.

https://pkg.go.dev/cmd/cgo

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


Arabic translation by Bashar Al-Abdulhadi (KuwaitNET)

Arabic translation by Bashar Al-Abdulhadi (KuwaitNET)

شكرا جزيلا! :)
Sorry it's taken so long to get back to you on this, @Bashar. For some reason I haven't been getting notifications on this repository. We'll have it in a release soon!
@waltfy, would you be able to merge this in at the same as when you do the PT translations?


Exception after leaving bot running for days

After leaving bot running for few days, I came to find it terminated with this exception.
Line numbers may not match existing code because I've added lines to ignore messages coming from slack that doesn't contain the key "message" (a dirty fix for the previous issue)
Traceback (most recent call last):
File "app.py", line 21, in
main()
File "app.py", line 17, in main
simple_slack_bot.start()
File "/home/skor/simple_slack_bot/simple_slack_bot.py", line 112, in start
self.listen()
File "/home/skor/simple_slack_bot/simple_slack_bot.py", line 165, in listen
json_list = self._slack_client.rtm_read()
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/slackclient/_client.py", line 123, in rtm_read
json_data = self.server.websocket_safe_read()
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/slackclient/_server.py", line 141, in websocket_safe_read
data += "{0}\n".format(self.websocket.recv())
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/_core.py", line 293, in recv
opcode, data = self.recv_data()
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/_core.py", line 310, in recv_data
opcode, frame = self.recv_data_frame(control_frame)
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/_core.py", line 323, in recv_data_frame
frame = self.recv_frame()
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/_core.py", line 357, in recv_frame
return self.frame_buffer.recv_frame()
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/_abnf.py", line 336, in recv_frame
self.recv_header()
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/_abnf.py", line 286, in recv_header
header = self.recv_strict(2)
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/abnf.py", line 371, in recv_strict
bytes = self.recv(min(16384, shortage))
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/_core.py", line 427, in _recv
return recv(self.sock, bufsize)
File "/home/skor/simple_slack_bot/env/local/lib/python2.7/site-packages/websocket/_socket.py", line 93, in recv
"Connection is already closed.")
websocket._exceptions.WebSocketConnectionClosedException: Connection is already closed.

Will look into at some point. Seems like its a common problem, see https://github.com/slackapi/python-slackclient/issues/127

Yes but in my case. the bot has started successfully and ran fine for a while ( at least one day).
Also our team is just 6 persons.
I am guessing the problem in our case is that connection eventually close for one reason or another.
We can just handle this exception and try to re-connect?
We can also keep counter for number of reconnect attempts so if x attempts has failed we can just terminate the program with appropriate error

@ramast That was just an example, I wasn't specifically trying to point out the high number of users in team or the startup.
Here's another example that might have been more closely related, https://github.com/gkbrk/hackchat/issues/1

According to that last link the bug has been fixed since 2015.
I am not trying to argue just trying to find a solution

Understood, I wasn't trying to be argumentative, sorry if I came off like that. Just did some quick google searches on the error you find. I added it to my TODO list when Graduate school lets up a little bit. I appreciate the bug reports and never want to seem aggressive ha
Thank you @ramast

Update: It's been running for over a week now without any problem.
I suppose the crash only happen when slack service goes offline. Can be really sure


Latest DBAL v. 0.3.1 not compatible with Crate.io v. 2.3

Hi,
Latest DBAL v. 0.3.1 depends on PDO 0.6. see:
https://github.com/crate/crate-dbal/blob/54ac194c999b70708d042f95bfd5e3db2b69aa05/composer.json#L12
therefore is NOT compatible with Crate.io 2.3. Would you be able to make new DBAL release that depends on PDO 1.0.0 to make it work with Crate.io 2.3?
Regards,
Chris

@l7s apologies, we totally missed this issue. Crate-dbal has been released quite a view months ago in version 1.1.0 which should be compatible with CrateDB >= 2.3.


Highlighted section after an orientation change does not fit

Orientation change while showing the coach mark leads to a highlighted area which does not match the desired widget anymore.

I wrapped the content in a SafeArea and worked for myself.
 return Scaffold(       appBar: AppBar(title: Text('Friends')),       body: SafeArea(child: content),       floatingActionButton: _friends.isEmpty


Ingest Mozilla localization corpus

Tip: Mozilla has localization at https://github.com/mozilla-l10n/
There seem to be a bunch of repos for different products with different formats.  Here's an example of Standard Moroccan Tamazight:
https://github.com/mozilla-l10n/firefoxios-l10n/blob/master/zgh/firefox-ios.xliff
Or here's some Acholi:
https://github.com/mozilla-l10n/sumo-l10n/blob/master/ach/LC_MESSAGES/buddyup.po
Trying to find a nice place to just grab everything from; I've e-mailed @delphine asking for a TMX.

Replied to your email, and added Jeff Beatty as a point of contact. Thanks so much for reaching out!

It happened thanks to Jeff Beatty!  https://opus.nlpl.eu/Mozilla-I10n.php


Fix full test suite after recent packaging changes

Adjust make deps & make develop target to assume yes.
Use them instead of dnf builddep to cover generated requires.

Hm, the full test suite now seems to fail on avc:
type=AVC msg=audit(1696613906.031:704): avc:  denied  { read write } for  pid=6227 comm="bash" path="/dev/pts/0" dev="devpts" ino=3 scontext=system_u:system_r:container_t:s0:c526,c847 tcontext=system_u:object_r:container_file_t:s0:c526,c847 tclass=chr_file permissive=0

The first failing command is podman:
Error: could not find slirp4netns, the network namespace can't be configured: exec: "slirp4netns": executable file not found in $PATH
:: [ 13:31:04 ] :: [   FAIL   ] :: Command 'su -l -c 'podman run -itd --name fresh fedora' tmt-tester' (Expected 0, got 127)

So the problem with the missing slirp4netns and AVC errors was caused by installing podman without weak dependencies. Missing container-selinux caused improper labeling of files created in user home. I'll update the make develop target to fix this as well.


Suggestion for improving pairwise distance calculation

Hi,
Thanks for the great work on this library!
I have a small suggestion to improve the pairwise distance calculation
https://github.com/PyRetri/PyRetri/blob/master/pyretri/index/re_ranker/re_ranker_impl/k_reciprocal.py#L35-L51
I see this function being used in 3 places - kreciprocal, knn and query expansion.
This function can simple be replaced by 1 line - torch.cdist(query_fea, gallery_fea)
PyTorch's official docs don't list this function for 1.2 but it is supported (I've used it).
This change will reduce duplication and make the code more readable.
Thanks!

Thanks for you suggestions! I will fix it in the next vesion.

Thanks for you suggestions! I will fix it in the next vesion.


Show output img

Good morning people:
Im using Google colab to run this github for image detecction.
I would like to show the output img with corresponding bounding boxes, but i dont now if the code return a img or bounding boxes details for use it after.
How I can do it?
I hope your answers

https://github.com/YunYang1994/tensorflow-yolov3

Are you using Keras or only TF?
Do you know how I can solve my problem?

@vgilabert94  I wonder how to upload large dataset to google drive when using colab, I tried upload zip file but unzip process always went wrong.


Why hasn't the data set been accessible lately？？？

Why hasn't the data set been accessible lately？？？

I use this link to download the data:
https://web.archive.org/web/20220413011817/https://bvisionweb1.cs.unc.edu/licheng/referit/data/refclef.zip
https://web.archive.org/web/20220413011718/https://bvisionweb1.cs.unc.edu/licheng/referit/data/refcoco.zip
https://web.archive.org/web/20220413011656/https://bvisionweb1.cs.unc.edu/licheng/referit/data/refcoco+.zip
https://web.archive.org/web/20220413012904/https://bvisionweb1.cs.unc.edu/licheng/referit/data/refcocog.zip

@hydrochloricacid thanks a lot!


[ENHANCEMENT] Add cluster information to the Harvester VMs of Rancher guest cluster

Is your enhancement related to a problem? Please describe.

Currently, VMs created by Harvester node driver do not carry any cluster information, such as the cluster name.
Howerver, this infomation is useful for Harvester cloud controller manager.
Describe the solution you'd like

Add a new field to the Harvester node driver.
The Rancher UI needs to add cluster information to the newly added field when creating a new cluster, in order to avoid affecting existing clusters.
When creating a VM, the Harvester node driver adds cluster information to the label of VM .

Describe alternatives you've considered

Additional context

That's funny, I was working on this feature as a fallback to another feature. So it shouldn't be a problem to implement it.


Update create-complete-managed-instance-directly-connected.md

to keep this consistent with create-complete-managed-instance-indirectly-connected.md / not have just "an" in from of managed instance (see feedback on PR #92217 for consistency)

@bweissman : Thanks for your contribution! The author(s) have been notified to review your proposed change.

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

@MikeRayMSFT
Thanks for approving the PR. For future PRs, please note that a #sign-off comment is the best way to signal to the review team that a PR is ready to merge. A PR approval doesn't push PRs into our queues for processing.


Set title, version, description at API top level

I think these attributes are API level and so should be set in the API layer. It is then the job of the backend to serve data that is compliant with the specified API version.

We added title and version in #139 (https://github.com/stac-utils/stac-fastapi/pull/139/files#diff-4f8c5fdc9b3cca78110705589c68a6df26ac7a9d66bd4af3108db5174fdfe49cR63-R64), just need to do the same for description.


Update to IntervalArithmetic v0.22, drop IntervalBox

Closes #181.
Background
I tried to upgrade IntervalArithmetic.jl together with IntervalBoxes.jl, just to see how far it goes. Spoiler: not far.
There are two problems (already discussed in #181):

One cannot depend on IntervalBoxes without enforcing a new version of IntervalArithmetic (v0.22.12).
Three optional dependencies are not (yet) compatible with IntervalArithmetic v0.22 (as discussed above already) and thus would become not usable.

https://github.com/JuliaIntervals/TaylorModels.jl
https://github.com/JuliaIntervals/IntervalOptimisation.jl
https://github.com/JuliaIntervals/AffineArithmetic.jl

Two of these optional dependencies have not been maintained in a long time, so I am not hopeful that this will change anytime soon.
It seems silly to rely on the optional dependencies (then they are not really optional), but dropping support and tests for three backends at once would also make this package much less useful and more fragile.
This PR
As an alternative, I tried to remove IntervalBox (and instead use AbstractVector{<:Interval}) in this PR. But I did not really manage. All this PR does to the actual library is allow to use the new version of IntervalArithmetic, which works fine if only one-dimensional Intervals are used. (There is one catch: multiple enclosure methods cannot yet be combined.)
Note that the tests (and docs) still use the old version where IntervalBox is used, so the new version is currently untested. I created a second (nested) test folder with a separate Project.toml file to test the new version as well. This script essentially skips all tests with these optional dependencies and IntervalBox.
If we want to go with this change, I suggest to add a second CI test script to run those tests as well (not yet done here).
(The additional invalidations come from loading PkgVersion and should be ignored.)

Sorry to see that upgrading RangeEnclosures.jl to IA 0.22 is so difficult 😞.
Why is it so hard to replace IntervalBox with AbstractVector{<:Interval}? Are we missing some features?
For reference, TaylorModels.jl compatibility with IA depends on this PR https://github.com/JuliaDiff/TaylorSeries.jl/pull/345 which I hope will be merged soon.
I do not know about the other two libraries, but I can look into upgrading them. NB: you probably already know, but IA v0.22 requires Julia 1.9+.
If I can help, let me know!
(cc @Kolaru)


按钮回调事件和vue冲突

Event "addbtn" is emitted in component  at lib/transfer-extend.vue but the handler is registered for "addBtn". Note that HTML attributes are case-insensitive and you cannot use v-on to listen to camelCase events when using in-DOM templates. You should probably use "add-btn" instead of "addBtn".

@EdisonYoung23 v2.4.1以上已改为 @add-btn


[#118107013] Lawyer content updates

Contains all the content changes listed in this story: https://www.pivotaltracker.com/story/show/118107013

Words-only change, merging it myself to get things shipped to staging ASAP this morning.


Geant4 10.1 branch

@lopezzot can you create a geant4_10.1 branch so that I can change the PR target branch?

Let's merge this after #26 and push master to 10.1.p03 before.


koboldcpp: use python3 instead of python311; koboldcpp: fix cuda; koboldcpp: 1.68 -> 1.69.1; koboldcpp: add postPatch

Description of changes
This PR addresses:
https://github.com/NixOS/nixpkgs/pull/314450#issuecomment-2170543384
https://github.com/NixOS/nixpkgs/pull/314450#issuecomment-2208635912
Also updates koboldcpp to 1.69.1
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hey, @KiruyaMomochi @mirrexagon could you please test this?

Result of nixpkgs-review pr 325540 run on x86_64-linux 1

1 package built:

koboldcpp

Result of nixpkgs-review pr 325540 run on aarch64-darwin 1

1 package built:

koboldcpp

I decided to revert march back to being an optional setting since we can't set it manually
After doing some testing, it seems like env.NIX_CFLAGS_COMPILE wasn't being respected (as when building koboldcpp on x86_64-linux, it was using native regardless of any custom march or mtune)
So to deal with that we'll need to use postPatch to manually patch the Makefile

So to deal with that we'll need to use postPatch to manually patch the Makefile

Oh, I see. For the llama part, you can set cmakeFlags = [ (lib.cmakeBool "LLAMA_NATIVE" false) ], but yes, seems like you won't be able to avoid some patching. Not having those removed can be considered a bug on nixpkgs side, but it's ok to handle that in a separate PR if you'd rather

I think at this point the PR is done.
@SomeoneSerge I would like to thank you a lot for this detailed review. This PR has helped me learn a lot, and I appreciate all the help you gave!


Allow setting node name for redbug node

When running redbug from the command line, accept -name and -sname
arguments to set the node name for the redbug node.
The use case for this is a system that has been configured to only
accept connections from certain named nodes.

in 0.96.3


New EAR artifacts providing Metrics with embedded Alerting

Remove JMS listening between metrics and alerting, they now communicate directly.
Update name of metrics distribution

artifact hawkular-metrics-component-dist-VERSION.ear deployed as hawkular-metrics.ear

Move publishing cache under hawkular-alerts container
Up to final versions of deps
Add new alerting cache

@pilhuhn Please review and merge and do release magic.

@pilhuhn DoNotMerge, I found a problem.

@pilhuhn I fixed the issue, so merge is OK by me.


Improve UI of get in touch form

fixes : #1139
before :

after :

@Its-Aman-Yadav please review once and merge my pr


pixart_js - Stormy Ramsey

Hello,
Thank you for allowing us to get this after the deadline. I apologize that I couldn't not submit before now.

This pull request only contains work attempted for the first of 6 total expected stages.


Use psycopg2-binary instead of psycopg2

It's identical except we download pre-built binaries.
This makes builds faster and requires less dependencies.

The travis build still failed when installing psycopg2 though... cache hecking things up again, probably?

It's definitely trying to install psycopg2-binary, it's just...still installing it from source.

Apparently this is because psycopg2 doesn't have a wheel for musl-based distros, and we use alpine.
I'm going to back out of this change and just make the source install work.

Closing in favor of https://github.com/ekimekim/wubloader/pull/187


Can't delete movie from movie-list using cmdline

Actual behaviour:
$ ./bin/flexget movie-list del "movies queue" "The Fantastic Four 2"
Traceback (most recent call last):
  File "./bin/flexget", line 9, in <module>
    load_entry_point('FlexGet==2.8.17.dev', 'console_scripts', 'flexget')()
  File "/home/wyrm/flexget/flexget/__init__.py", line 42, in main
    manager.start()
  File "/home/wyrm/flexget/flexget/manager.py", line 327, in start
    self.handle_cli()
  File "/home/wyrm/flexget/flexget/manager.py", line 354, in handle_cli
    options.cli_command_callback(self, command_options)
  File "/home/wyrm/flexget/flexget/plugins/cli/movie_list.py", line 76, in do_cli
    movie_list_del(options)
  File "/home/wyrm/flexget/flexget/plugins/cli/movie_list.py", line 181, in movie_list_del
    title, year = split_title_year(options.movie_title)
  File "/home/wyrm/flexget/flexget/options.py", line 157, in __getattr__
    return getattr(self.__parent__, key)
  File "/home/wyrm/flexget/flexget/options.py", line 158, in __getattr__
    raise AttributeError("'%s' object has no attribute '%s'" % (type(self).__name__, key))
AttributeError: 'ScopedNamespace' object has no attribute 'movie_title'

I can confirm this on version 2.8.18
Crashes when trying to delete a title from your movie-list.
Debug log
`
pi@raspberrypi:~ $ flexget --debug movie-list del vic_movies "Split (2017)"
2017-01-04 23:32 DEBUG    manager                       Figuring out config load paths
2017-01-04 23:32 DEBUG    manager                       Found config: /home/pi/.flexget/config.yml
2017-01-04 23:32 DEBUG    manager                       Config file /home/pi/.flexget/config.yml selected
2017-01-04 23:32 DEBUG    manager                       sys.defaultencoding: ascii
2017-01-04 23:32 DEBUG    manager                       sys.getfilesystemencoding: UTF-8
2017-01-04 23:32 DEBUG    manager                       flexget detected io encoding: utf-8
2017-01-04 23:32 DEBUG    manager                       os.path.supports_unicode_filenames: False
There is a FlexGet process already running for this config, sending execution there.
2017-01-04 23:32 DEBUG    manager                       Sending command to running FlexGet process: [u'--debug', u'movie-list', u'del', u'vic_movies', u'Split (2017)']
2017-01-04 23:32 DEBUG    movie_list                    returning list with name vic_movies
Traceback (most recent call last):
File "/usr/local/bin/flexget", line 11, in
sys.exit(main())
File "/usr/local/lib/python2.7/dist-packages/flexget/init.py", line 42, in main
manager.start()
File "/usr/local/lib/python2.7/dist-packages/flexget/manager.py", line 310, in start
client.handle_cli(self.args)
File "/usr/local/lib/python2.7/dist-packages/rpyc/core/netref.py", line 196, in call
return syncreq(_self, consts.HANDLE_CALL, args, kwargs)
File "/usr/local/lib/python2.7/dist-packages/rpyc/core/netref.py", line 71, in syncreq
return conn.sync_request(handler, oid, *args)
File "/usr/local/lib/python2.7/dist-packages/rpyc/core/protocol.py", line 441, in sync_request
raise obj
AttributeError: 'ScopedNamespace' object has no attribute 'movie_title'
========= Remote Traceback (1) =========
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/rpyc/core/protocol.py", line 305, in _dispatch_request
res = self._HANDLERS[handler](self, *args)
File "/usr/local/lib/python2.7/dist-packages/rpyc/core/protocol.py", line 535, in _handle_call
return self._local_objects[oid](*args, **dict(kwargs))
File "/usr/local/lib/python2.7/dist-packages/flexget/ipc.py", line 85, in exposed_handle_cli
self.manager.handle_cli(options)
File "/usr/local/lib/python2.7/dist-packages/flexget/manager.py", line 354, in handle_cli
options.cli_command_callback(self, command_options)
File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/cli/movie_list.py", line 76, in do_cli
movie_list_del(options)
File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/cli/movie_list.py", line 181, in movie_list_del
title, year = split_title_year(options.movie_title)
File "/usr/local/lib/python2.7/dist-packages/flexget/options.py", line 157, in getattr
return getattr(self.parent, key)
File "/usr/local/lib/python2.7/dist-packages/flexget/options.py", line 158, in getattr
raise AttributeError("'%s' object has no attribute '%s'" % (type(self).name, key))
AttributeError: 'ScopedNamespace' object has no attribute 'movie_title'
`

sorry about this, you can delete by id as a workaround. ill address this asap

It also happens to me too, with version 2.9.9.


Added POMA R/Bioconductor package

POMA includes several visualization options for pre-processing and exploratory data analysis in addition to an automated EDA function.

Thank you!


Redundant Discord Link

Problem:
Having a table attribute for each course directing to the same Discord server 37 times is redundant and a waste of table space. Commit Addressed
Background:
I loved that OSSU finally changed from Gitter to Discord, however as @waciumawanjohi stated in issue 733 some information on a table can be duplicative and a waste, even though it links to a different discord channel it is not valuable to have a redundant link 37 times to the same discord server since there is already a link in the community section.
Proposal:

Remove the redundant link from each table cell.

Alternatives:
Maybe also use the space to provide bigger value that impacts students career path.

For context:
This change was made in response to the discussion "Future of Cohorts" in the Cohorts repo (which has since been archived). The idea came from @spamegg1 who wrote at the time,

Most people who ever come across OSSU will have a lazer sharp focus on the curriculum and nothing else. I never knew Gitter, Cohorts, or even Extras existed until recently. And I had been visiting the Curriculum page regularly for almost 2 years!
Also people will not read the "prose" inside README. They will just scroll down to the list of courses. Then some of them will come to Gitter and ask questions that are already answered in the "prose".
Therefore: on the curriculum, right next to each course, we must have links directly to a current cohort taking that class and its Gitter/whatever chat room. RIGHT NEXT TO EACH COURSE is by FAR the most important thing here. Kinda like this (just a mock-up):

Courses
Duration
Effort
Prerequisites
Students currently taking this class

How to Code - Simple Data
7 weeks
8-10 hours/week
none
Chat with your cohorts

This way the cohorts/chatrooms are ANCHORED both in the curriculum and in people's minds. So the social aspects must be directly integrated into the curriculum.
It would make sense to have PERMANENT cohort/chatrooms for each class,

I believe that @spamegg1 's hypothesis has been borne out. Since adding the links next to each course we have seen a remarkable jump in student participation in OSSU chatrooms. That participation is valuable, it's not clear to me what we could tell students that would be more important than, "If you want to talk to others taking this class, you can do so here."

I agree with you and @spamegg1 that having really visible its really important for student participation, and maybe just having the community section is not enough for visibility.
However I believe that whats been borne out its that Discord works better than Gitter because of its channels feature not the unnecessary 37 times redundant link to each course adding to the unnecessary clutter the curriculum has already.
The discord server its long overdue and you never supported it since issue 495 or maybe longer. Its awesome that you finally changed your mind, kudos for you and the good that made to the community and its participation. I love it!
So yeah, I agree with you guys that the link to the discord server should be more visible than it is right now just in the community section. But i dont think the most optimal solution its to spam the link redundantly 37 times!

Perhaps once for each section (Intro, Core, Math, etc.) instead of once for each listed course?

This Issue has been open for a few months and has not attracted a wide base of support. While I agree that the current layout is a bit clunky, I do think that one of the valuable things that OSSU does is give like-minded CS self studiers a forum for discussion and support. I'm hesitant to make a change that makes that less visible. We should keep this feedback in mind during any future overhaul of the curriculum's UI.


fix(ember-cli): Fixes #365, now handles the promise from config.search.

Fixes #365.
Used await + promise syntax for defaults and await error fallback

Closing this as the new TS change will make this a merge PITA


Challenge 4: Suggestions for UI/UX

GM maintainers
The DEX challenge inspired me to implement some basic user experience improvements and I'm curious if you might be open to my creating a pull request to implement them on the official branch. You can test drive here
Deposit Interaction

Added an additional input for balloon tokens that automatically updates similar to the experience of providing liquidity on uniswap
The logic for calling the deposit function remains unchanged so the balloon input is just for show although it does calculate how much ETH would be required to deposit x amount of balloons by mirroring the logic from the DEX contract solution

Withdraw Interaction

Replaced the integer input with a daisyui range that allows user to fine tune the amount and prevents trying to withdraw beyond max

Challenge #4

Hey @rin-st . lol i totally forgot I created this issue 7 months ago and left it open all this time :sweat_smile:
I agree that leaving potential for invalid withdrawal helps dev learn.
I probably have too much on my plate right now to put up a PR so I'm closing the issue
Thank you for the thoughtful feedback :pray:


Incompatibility with the current Jython?

I'm testing your script and reached the following problem:
>>> Start analyzing file...
Traceback (most recent call last):
  File "/opt/analyze-community-ghidra-plugin/intezer_analyze_gh_community.py", line 272, in run
    helper.create_function_map(sha256)
  File "/opt/analyze-community-ghidra-plugin/intezer_analyze_gh_community.py", line 230, in create_function_map
    function_map = self._get_function_map(sha256)
  File "/opt/analyze-community-ghidra-plugin/intezer_analyze_gh_community.py", line 155, in _get_function_map
    ghidra_plugin_report = self._proxy.get_plugin_report(result_url)
  File "/opt/analyze-community-ghidra-plugin/intezer_analyze_gh_community.py", line 110, in get_plugin_report
    response = self._get(API_URL + result_url)
  File "/opt/analyze-community-ghidra-plugin/intezer_analyze_gh_community.py", line 89, in _get
    return self.session.get(url_path, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 533, in get
    return self.request('GET', url, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 520, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 630, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 430, in send
    resp = conn.urlopen(
  File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 430, in send
    resp = conn.urlopen(
  File "/usr/lib/python2.7/dist-packages/urllib3/connectionpool.py", line 589, in urlopen
    conn = self._get_conn(timeout=pool_timeout)
  File "/usr/lib/python2.7/dist-packages/urllib3/connectionpool.py", line 589, in urlopen
    conn = self._get_conn(timeout=pool_timeout)
  File "/usr/lib/python2.7/dist-packages/urllib3/connectionpool.py", line 242, in _get_conn
    if conn and is_connection_dropped(conn):
  File "/usr/lib/python2.7/dist-packages/urllib3/util/connection.py", line 27, in is_connection_dropped
    return bool(wait_for_read(sock, timeout=0.0))
  File "/usr/lib/python2.7/dist-packages/urllib3/util/connection.py", line 27, in is_connection_dropped
    return bool(wait_for_read(sock, timeout=0.0))
  File "/usr/lib/python2.7/dist-packages/urllib3/util/wait.py", line 33, in wait_for_read
    return _wait_for_io_events(socks, EVENT_READ, timeout)
  File "/usr/lib/python2.7/dist-packages/urllib3/util/wait.py", line 24, in _wait_for_io_events
    selector.register(sock, events)
  File "/usr/lib/python2.7/dist-packages/urllib3/util/selectors.py", line 344, in register
    key = super(PollSelector, self).register(fileobj, events, data)
  File "/usr/lib/python2.7/dist-packages/urllib3/util/selectors.py", line 197, in register
    key = SelectorKey(fileobj, self._fileobj_lookup(fileobj), events, data)
  File "/usr/lib/python2.7/dist-packages/urllib3/util/selectors.py", line 181, in _fileobj_lookup
    return _fileobj_to_fd(fileobj)
  File "/usr/lib/python2.7/dist-packages/urllib3/util/selectors.py", line 50, in _fileobj_to_fd
    raise ValueError("Invalid file object: {0!r}".format(fileobj))
ValueError: Invalid file object: <ssl.SSLSocket object at 0xc15>

I found that this error could be related to the Jython version used by Ghidra. Any idea to solve this issue?

Can you run sys.version in the python command line within Ghidra?
In my case the output is : '2.7.1 (default:0df7adb1b397, Jun 30 2017, 19:02:43) \n[OpenJDK 64-Bit Server VM (AdoptOpenJDK)]'

'2.7.17 (default, Apr 15 2020, 17:20:14) \n[GCC 7.5.0]'
(System running my Ghidra instance is a Ubuntu 18.04-LTS)

@xme Did you add the correct python path in Linux?

Yes, I submitted a pull request to adapt it between Win <> Linux.

@xme What version of requests do you have installed?
It looks like it's a known issue in requests: https://github.com/psf/requests/issues/3992

2.18.4 (the Ubuntu package)
I'll investigate this and let you know!

I downgraded the Python requests module to 2.7.0. Works perfectly now. I had to add an extra directory for the local modules. I submitted a pull request for this.


D3D debug markers

On 3 different API renderdoc capture looks different from the "naming" point of view.

Vulkan: Everything as expected, every encoder actually applied name

Dx12 almost nothing named, hard to understand where is necessary draw calls (only buffers are named)

Dx11, I don't know what it that %)

Status report: as of #3427, I have added debug marker events to DX11, but begin/end events cause the timeline to get totally messed up, so are still not enabled. I have also added debug names to everything, some of which work, some of which renderdoc/nsight completely ignore.


Support matmul+bias+gelu fusion on GPUs

This PR enables the fusion pattern of MatMul+BiasAdd+Gelu on GPUs when CublasLt is enabled by TF_USE_CUBLASLT=1.
cc. @nluehr

Force pushed the PR to resolve the conflict.

Hi kaixih, does cublaslt support float64? Thank you.

Hi kaixih, does cublaslt support float64? Thank you.

Hi @njzjz As for this PR, the cublaslt doesn't support float64 for fusion. But cublaslt itself support fp64.

Any update/feedback for this PR that I can work on?

Hi, @ezhulenev , can you take a look at this PR? It seems something is blocking the merge. Thanks.

@reedwm Can you take a look at if the unhandled switch case is gone?

Gentle ping @reedwm .

Rebased to resolve the conflicts. PTAL. @reedwm

I can see some tests are failed but the log shows the failure is unrelated to this PR. Can you help check? @reedwm

Hi @kaixih Can you please resolve conflicts? Thank you!

Rebased to resolve conflicts. PTAL. @reedwm


fix: re-generate some lock files

I'm trying to figure out #54.  All of the samples tests appear to "work on my machine", and the lock files are at this point the only difference.
@alexander-fenster @stephenplusplus @callmehiphop is there any way to run samples tests against a PR like this?

TBR = @alexander-fenster