Disappearing Source, no "output"

Valid video files have been disappearing from the watch folder, but nothing appearing in the output folder.
Since I don't keep the source files, these videos are just getting deleted.  Not good!
To diagnose, I touched a file "hb-watch.log" in the watch folder.
HB picks it up, then it disappears, yet goes nowhere.
The successful_conversions log file shows it processed the file:

/config # cat successful_conversions
/watch/hb-watch.log 854f91d87fd1a9e5f53bd5357510fcb5

Except...  It's obviously not a successful conversion.  But it deletes my file, nonetheless.
I touched a file with a .mkv extension.  It said that was successful too.  But no output, and file was deleted.

/config # tail -f successful_conversions
/watch/hb-watch.mkv 8f2074b69ab466fd2cbfd26d087a3d06

Separate but related problem: Increased DEBUG does not work...
When HANDBRAKE_DEBUG is set to 1, no additional debug output appears in the container's "/config/log/hb/conversion.log" for these "odd" files.  (Looks like that debug is only sending debug output when it ACTUALLY converts something)
Here's my Docker Compose file:
version: "3"
services:
handbrake:
image: jlesage/handbrake
ports:
- "5810:5800"
environment:
- AUTOMATED_CONVERSION_KEEP_SOURCE=0
- AUTOMATED_CONVERSION_SOURCE_STABLE_TIME=15
- AUTOMATED_CONVERSION_PRESET=Matroska/H.264 MKV 2160p60
- AUTOMATED_CONVERSION_FORMAT=mp4
- HANDBRAKE_DEBUG=1
volumes:
- /home/jherr/docker/appdata/handbrake:/config:rw
- /home/jherr:/storage:ro
- /home/jherr/movie_rips:/watch:rw
- /home/jherr/movie_converted:/output:rw
restart: unless-stopped

From the tests you did, I think the behaviour is correct.  AUTOMATED_CONVERSION_KEEP_SOURCE=0 indicates that sources files are not kept.  Also, since touching hb-watch.log or a file with the .mkv extension does not provide a real/valid video file (I assume this creates an empty file), no conversion is done.
Can you try again with a real video file and:

Check if the conversion details is added to /config/log/hb/conversion.log.
Get the container log: docker logs <container name>

Successful conversions work just fine...  There's no issue there.  I'm suggesting failed conversions are not being handled properly.
We expect the source to turn into a converted output file, and when it does, we no longer need the source file.
When the conversion is unsuccessful, I might want to explore further, re-rip the video file, etc.  I would assume that I can look at the "failed conversions" log to see what I need to re-rip, but it seems to be considered "successful", and there logged.
There is no output, source file has been deleted, logged as "successful".  I have nothing to tell me to go back and re-rip.
Am I missing something?

Note that failed_conversions and successful_conversions are internal files used only to prevent re-processing the same file more than once.  So I would not use them to check if a conversion went well or not.  The container's log (docker logs <container name>) is the way to go to have more details about what happened.
Also, a "real" failure should be handled correctly: you should have a clear indication in the container's log and the source file won't be removed.
I think the behaviour you are seeing is caused by the usage of non-video files.  Non-video files are detected and no conversion is attempted on these files.

If conversion fails, or is never attempted, the source should never be
deleted.  Think about this objectively...  A file is being removed, but
never converted to anything else.  The process is basically deleting the
file...  No recourse.
Convert and remove source, move the original source, leave the source, but
don't just delete the source.
FYI: love the failed log, even if internal
On Sun, Feb 5, 2023, 11:06 Jocelyn Le Sage @.***> wrote:

Note that failed_conversions and successful_conversions are internal
files used only to prevent re-processing the same file more than once. So I
would not use them to check if a conversion went well or not. The
container's log (docker logs ) is the way to go to have
more details about what happened.
Also, a "real" failure should be handled correctly: you should have a
clear indication in the container's log and the source file won't be
removed.
I think the behaviour you are seeing is caused by the usage of non-video
files. Non-video files are detected and no conversion is attempted on these
files.
—
Reply to this email directly, view it on GitHub
https://github.com/jlesage/docker-handbrake/issues/244#issuecomment-1418091010,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB32XY2WNVP35VHUER6KGGLWV7FZFANCNFSM6AAAAAAUJW6XYY
.
You are receiving this because you authored the thread.Message ID:
@.***>

I agree with you.  And to make things clear, today, a source that fails to be converted should never be removed.
Now I think the confusion is around non-video files.  Since these files can't be converted, they need to be handled differently.  We cannot just mark them as failed conversions.  The reasoning behind that is that some people use the watch folder as the output of downloaded files.  Thus, along with the video file, the watch folder can have files like .txt, .nfo, etc.  It would not make sense to mark them as failed conversions and let them sit in the watch folder forever.  To better cover the case of non-video files, there is the AUTOMATED_CONVERSION_NON_VIDEO_FILE_ACTION variable, which indicates if non-video files are ignored or copied to the output folder.

A file is being removed, but never converted to anything else.

This is usually want people want with non-video files.

Convert and remove source, move the original source, leave the source, but don't just delete the source.

I think this can be achieved with AUTOMATED_CONVERSION_KEEP_SOURCE and AUTOMATED_CONVERSION_NON_VIDEO_FILE_ACTION variable.
In summary, it's definitely a problem if a video file that fails to be converted is removed.  However, note that a video file is not defined only by its extension, but also by its content.    So maybe a .mkv that is not detected as a video file should be marked as a failed conversion instead of being handled like a non-video file.

Thank you so very much for your consideration and your time.  I'll look
into setting the "Non-video action" and see if that helps ensure I never
lose source video files, even if they may be malformed, etc.
You have a fabulous product with the Docker container and the automated
conversion.  You are helping many people, including me, automate their
workflow.  Thank you so much!
Jeff
On Sun, Feb 5, 2023 at 11:14 AM Jocelyn Le Sage @.***>
wrote:

I agree with you. And to make things clear, today, a source that fails to
be converted should never be removed.
Now I think the confusion is around non-video files. Since these files
can't be converted, they need to be handled differently. We cannot just
mark them as failed conversions. The reasoning behind that is that some
people use the watch folder as the output of downloaded files. Thus, along
with the video file, the watch folder can have files like .txt, .nfo,
etc. It would not make sense to mark them as failed conversions and let
them sit in the watch folder forever. To better cover the case of non-video
files, there is the AUTOMATED_CONVERSION_NON_VIDEO_FILE_ACTION variable,
which indicates if non-video files are ignored or copied to the output
folder.
A file is being removed, but never converted to anything else.
This is usually want people want with non-video files.
Convert and remove source, move the original source, leave the source, but
don't just delete the source.
I think this can be achieved with AUTOMATED_CONVERSION_KEEP_SOURCE and
AUTOMATED_CONVERSION_NON_VIDEO_FILE_ACTION variable.
In summary, it's definitely a problem if a video file that fails to be
converted is removed. However, note that a video file is not defined only
by its extension, but also by its content.  So maybe a .mkv that is not detected as a video file should be
marked as a failed conversion instead of being handled like a non-video
file.
—
Reply to this email directly, view it on GitHub
https://github.com/jlesage/docker-handbrake/issues/244#issuecomment-1418173949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB32XY2HVLEGVOR7426JUZ3WV7NXNANCNFSM6AAAAAAUJW6XYY
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
"What good is it for a man to gain the whole world, yet forfeit his soul?"

Mark 8:36
http://christianbookshelf.org/spurgeon/spurgeons_sermons_volume_2_1856/profit_and_loss.htm

FYI, the latest image includes the protection about the hole I was talking about.

You have a fabulous product with the Docker container and the automated
conversion.  You are helping many people, including me, automate their
workflow.  Thank you so much!

You are welcome !
I'm going to close this issue.  Please rep-open if needed.


🐛 [cloud_firestore] database is locked (Sqlite code 5 SQLITE_BUSY)

Bug report
I have bug reports in my crashlytics:
Fatal Exception: java.lang.RuntimeException
Internal error in Cloud Firestore (22.0.1).
com.google.firebase.firestore.util.AsyncQueue.b (AsyncQueue.java:19)
com.google.firebase.firestore.util.AsyncQueue$$Lambda$3.run (AsyncQueue.java:2)
android.os.Handler.handleCallback (Handler.java:888)
android.os.Handler.dispatchMessage (Handler.java:100)
android.os.Looper.loop (Looper.java:213)
android.app.ActivityThread.main (ActivityThread.java:8178)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:513)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1101)

Caused by java.lang.RuntimeException
android.database.sqlite.SQLiteDatabaseLockedException: database is locked (Sqlite code 5 SQLITE_BUSY), (OS error - 11:Try again)
com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor.a (AsyncQueue.java:14)
com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor$$Lambda$2.run (AsyncQueue.java:4)
java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:462)
java.util.concurrent.FutureTask.run (FutureTask.java:266)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run (ScheduledThreadPoolExecutor.java:301)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor$DelayedStartFactory.run (AsyncQueue.java:15)
java.lang.Thread.run (Thread.java:929)

Caused by android.database.sqlite.SQLiteDatabaseLockedException
database is locked (Sqlite code 5 SQLITE_BUSY), (OS error - 11:Try again)
android.database.sqlite.SQLiteConnection.nativeExecute (SQLiteConnection.java)
android.database.sqlite.SQLiteConnection.execute (SQLiteConnection.java:694)
android.database.sqlite.SQLiteSession.beginTransactionUnchecked (SQLiteSession.java:335)
android.database.sqlite.SQLiteSession.beginTransaction (SQLiteSession.java:310)
android.database.sqlite.SQLiteDatabase.beginTransaction (SQLiteDatabase.java:595)
android.database.sqlite.SQLiteDatabase.beginTransactionWithListener (SQLiteDatabase.java:558)
com.google.firebase.firestore.local.SQLitePersistence.a (SQLitePersistence.java:17)
com.google.firebase.firestore.local.LocalStore.startMutationQueue (LocalStore.java:8)
com.google.firebase.firestore.local.LocalStore.start (LocalStore.java)
com.google.firebase.firestore.core.ComponentProvider.initialize (ComponentProvider.java:43)
com.google.firebase.firestore.core.FirestoreClient.a (FirestoreClient.java:65)
com.google.firebase.firestore.core.FirestoreClient.a (FirestoreClient.java:10)
com.google.firebase.firestore.core.FirestoreClient$$Lambda$1.run (FirestoreClient.java:8)
com.google.firebase.firestore.util.AsyncQueue.lambda$enqueue$2 (AsyncQueue.java)
com.google.firebase.firestore.util.AsyncQueue$$Lambda$2.call (AsyncQueue.java:2)
com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor.access$100 (AsyncQueue.java)
com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor$$Lambda$2.run (AsyncQueue.java:4)
java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:462)
java.util.concurrent.FutureTask.run (FutureTask.java:266)
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run (ScheduledThreadPoolExecutor.java:301)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor$DelayedStartFactory.run (AsyncQueue.java:15)

Steps to reproduce
I don't know. But every crash was when the app was in the background
Flutter doctor
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, 2.3.0-0.1.pre, on macOS 11.3 20E232 darwin-x64, locale en-RU)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2021.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2021.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2020.3.3)
[✓] VS Code (version 1.55.2)
[✓] Connected device (2 available)

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.14.0-18.0.dev
Flutter SDK 2.3.0-0.1.pre
word_daily 0.1.2+75

dependencies:
- amplitude_flutter 3.1.0 [flutter]
- another_flushbar 1.10.20 [pedantic flutter]
- async 2.5.0 [collection]
- built_value 8.0.5 [built_collection collection fixnum]
- cached_network_image 3.0.0 [flutter flutter_cache_manager octo_image]
- cloud_firestore 1.0.7 [cloud_firestore_platform_interface cloud_firestore_web firebase_core firebase_core_platform_interface flutter meta]
- cloud_functions 1.0.5 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- cupertino_icons 1.0.3
- firebase_analytics 8.0.2 [firebase_analytics_platform_interface firebase_analytics_web firebase_core flutter meta]
- firebase_auth 1.1.2 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.1.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.0.2 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_dynamic_links 2.0.2 [firebase_core flutter]
- firebase_messaging 9.1.3 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_remote_config 0.6.0 [flutter firebase_core]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_email_sender 5.0.0 [flutter]
- flutter_inapp_purchase 5.0.1 [http meta flutter platform]
- flutter_local_notifications 5.0.0+3 [flutter flutter_local_notifications_platform_interface platform timezone]
- flutter_phoenix 1.0.0 [flutter]
- flutter_svg 0.22.0 [flutter meta path_drawing vector_math xml]
- google_sign_in 5.0.2 [google_sign_in_platform_interface google_sign_in_web flutter meta]
- horizontal_blocked_scroll_physics 3.0.0 [flutter pedantic]
- intl 0.17.1-nullsafety.3 [clock path]
- intl_translation 0.17.10+1 [analyzer args dart_style intl path petitparser]
- launch_options 0.0.1 [flutter]
- mime 1.0.0
- optimist_dev_common 1.6.1 [flutter http intl share json_api built_value f_logs strings]
- package_info 2.0.0 [flutter]
- permission_handler 7.1.0 [flutter meta permission_handler_platform_interface]
- provider 5.0.0 [collection flutter nested]
- pull_to_refresh 1.6.5 [flutter]
- scroll_to_index 2.0.0 [flutter]
- share 2.0.1 [meta mime flutter]
- shared_preferences 2.0.5 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web shared_preferences_windows]
- sign_in_with_apple 3.0.0 [flutter meta]
- url_launcher 5.7.10 [flutter url_launcher_platform_interface url_launcher_web url_launcher_linux url_launcher_macos url_launcher_windows]
- url_launcher_web 0.1.5+3 [url_launcher_platform_interface flutter flutter_web_plugins meta]
- video_player 2.1.1 [meta video_player_platform_interface video_player_web flutter flutter_test]
- visibility_detector 0.2.0 [flutter]
- vk_bridge 1.3.0 [js built_value built_collection rxdart meta]
- wakelock 0.5.1 [flutter meta wakelock_macos wakelock_platform_interface wakelock_web wakelock_windows]
- workmanager 0.4.0 [flutter]

dev dependencies:
- build_runner 1.12.2 [args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style glob graphs http_multi_server io js logging meta mime path pedantic pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- built_value_generator 8.0.5 [analyzer build build_config built_collection built_value source_gen quiver]
- cloud_firestore_mocks 0.8.2 [flutter cloud_firestore cloud_firestore_platform_interface collection plugin_platform_interface mockito quiver]
- flutter_launcher_icons 0.9.0 [args image path yaml]
- flutter_localizations 0.0.0 [flutter intl characters clock collection meta path typed_data vector_math]
- flutter_native_splash 1.1.8+4 [image meta path xml yaml universal_io]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]
- mockito 5.0.7 [analyzer build code_builder collection dart_style matcher meta path source_gen test_api]

dependency overrides:
- analyzer 1.5.0 [_fe_analyzer_shared cli_util collection convert crypto glob meta package_config path pub_semver source_span watcher yaml pedantic]
- args 2.1.0
- firebase_core 1.1.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- http 0.13.3 [async http_parser meta path pedantic]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- intl 0.17.1-nullsafety.3 [clock path]
- path_provider 2.0.1 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- petitparser 4.1.0 [meta]
- plugin_platform_interface 2.0.0 [meta]

transitive dependencies:
- _fe_analyzer_shared 21.0.0 [meta]
- archive 3.1.2 [crypto path]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.0.1 [analyzer async convert crypto glob logging meta path]
- build_config 0.4.7 [checked_yaml json_annotation meta path pubspec_parse yaml]
- build_daemon 2.1.10 [built_collection built_value http_multi_server logging pedantic path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.0.0 [analyzer build crypto graphs logging path package_config pool pub_semver stream_transform]
- build_runner_core 6.1.12 [async build build_config build_resolvers collection convert crypto glob graphs logging meta path package_config pedantic pool timing watcher yaml]
- built_collection 5.0.0
- characters 1.1.0
- charcode 1.2.0
- checked_yaml 2.0.1 [json_annotation source_span yaml]
- cli_util 0.3.0 [meta path]
- clock 1.1.0
- cloud_firestore_platform_interface 4.0.3 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 1.0.7 [cloud_firestore_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 5.0.3 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.0.5 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 3.7.0 [built_collection built_value collection matcher meta]
- collection 1.15.0
- convert 3.0.0 [typed_data]
- crypto 3.0.1 [collection typed_data]
- dart_style 1.3.14 [analyzer args path pub_semver source_span]
- f_logs 2.0.0 [flutter sembast path_provider intl xxtea meta path stack_trace]
- fake_async 1.2.0 [clock collection]
- ffi 1.0.0
- file 6.1.0 [meta path]
- firebase 9.0.1 [http http_parser js]
- firebase_analytics_platform_interface 2.0.0 [flutter meta]
- firebase_analytics_web 0.3.0 [firebase firebase_analytics_platform_interface flutter flutter_web_plugins meta]
- firebase_auth_platform_interface 4.2.0 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 1.1.0 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.0.0 [flutter meta plugin_platform_interface]
- firebase_core_web 1.0.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.0.2 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 2.1.3 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 1.0.6 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- fixnum 1.0.0
- flutter_blurhash 0.6.0 [flutter meta pedantic]
- flutter_cache_manager 3.0.1 [clock collection file flutter http image path path_provider pedantic rxdart sqflite uuid]
- flutter_local_notifications_platform_interface 3.0.0 [flutter plugin_platform_interface]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- glob 2.0.1 [async collection file path pedantic string_scanner]
- google_sign_in_platform_interface 2.0.1 [flutter meta quiver]
- google_sign_in_web 0.10.0 [google_sign_in_platform_interface flutter flutter_web_plugins meta js]
- graphs 1.0.0
- http_multi_server 3.0.1 [async]
- image 3.0.2 [archive meta xml]
- io 1.0.0 [meta path string_scanner]
- js 0.6.3
- json_annotation 4.0.1
- json_api 4.3.0 [http http_parser]
- lists 1.0.0 [meta]
- logging 1.0.1
- matcher 0.12.10 [stack_trace]
- meta 1.3.0
- nested 1.0.0 [flutter]
- octo_image 1.0.0+1 [flutter flutter_blurhash]
- package_config 2.0.0 [path]
- path 1.8.0
- path_drawing 0.5.0 [vector_math meta path_parsing flutter]
- path_parsing 0.2.0 [vector_math meta]
- path_provider_linux 2.0.0 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 2.0.0 [flutter]
- path_provider_platform_interface 2.0.1 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.1 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.11.0
- permission_handler_platform_interface 3.3.0 [flutter meta plugin_platform_interface]
- platform 3.0.0
- pool 1.5.0 [async stack_trace]
- process 4.2.1 [file path platform]
- pub_semver 2.0.0 [collection]
- pubspec_parse 1.0.0 [checked_yaml collection json_annotation pub_semver yaml]
- quiver 3.0.1 [matcher]
- rxdart 0.26.0
- sembast 3.0.2 [meta path synchronized pedantic]
- shared_preferences_linux 2.0.0 [flutter file meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 2.0.0 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.0 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- shared_preferences_windows 2.0.0 [shared_preferences_platform_interface flutter file meta path path_provider_platform_interface path_provider_windows]
- shelf 1.1.1 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.1 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 0.9.10+4 [analyzer async build dart_style glob meta path pedantic source_span]
- source_span 1.8.1 [collection path term_glyph]
- sqflite 2.0.0+3 [flutter sqflite_common path]
- sqflite_common 2.0.0+2 [synchronized path meta]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- strings 0.2.1 [characters unicode]
- synchronized 3.0.0
- term_glyph 1.2.0
- test_api 0.3.0 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timezone 0.7.0 [path]
- timing 1.0.0 [json_annotation]
- typed_data 1.3.0 [collection]
- unicode 0.3.0 [lists]
- universal_io 2.0.4 [collection crypto meta typed_data]
- url_launcher_linux 0.0.1+4 [flutter]
- url_launcher_macos 0.0.1+9 [flutter]
- url_launcher_platform_interface 1.0.9 [flutter meta plugin_platform_interface]
- url_launcher_windows 0.0.1+3 [flutter]
- uuid 3.0.4 [crypto]
- vector_math 2.1.0
- video_player_platform_interface 4.1.0 [flutter meta flutter_test]
- video_player_web 2.0.0 [flutter flutter_web_plugins meta video_player_platform_interface]
- wakelock_macos 0.1.0 [flutter flutter_web_plugins wakelock_platform_interface]
- wakelock_platform_interface 0.2.0 [flutter meta]
- wakelock_web 0.2.0 [flutter flutter_web_plugins js wakelock_platform_interface]
- wakelock_windows 0.1.0 [flutter wakelock_platform_interface win32]
- watcher 1.0.0 [async path pedantic]
- web_socket_channel 2.1.0 [async crypto stream_channel]
- win32 2.0.5 [ffi]
- xdg_directories 0.2.0 [meta path process]
- xml 5.1.0 [collection meta petitparser]
- xxtea 2.1.0
- yaml 3.1.0 [collection source_span string_scanner]

Hi @otopba,
Having the same problem with 23.0.0 instead of 22.0.1, did you find any solution about it, or maybe what causing it?

Hi @otopba,
Having the same problem with 23.0.0 instead of 22.0.1, did you find any solution about it, or maybe what causing it?

Hi!
I think that the problem is in using this library from several isolates. I haven't found a solution. Do you have one isolate in your application?

No, but my app uses streams and async code heavily, async queue keyword in stack trace makes me wonder if I missing some await keyword somewhere.

I had raised #6592 regarding same issue. All crashes that i have checked occur when user is interacting with the notification(which i am sending via scheduled FCM notification).

I think this is caused when we try to initialise multiple firebase apps. I was initialising firebase app in main method of my flutter app and on onBackgroundMessage that i register with FIrebaseCloudMessage service. I removed it from onBackgroundMessage and i have not seen a single crash in last 2 days. I think i saw this msg in crash logs that it maybe due to multiple firebase app initialising. But since crashes are so many i could not find the message again to paste it here.
The error message should be more clear here.
Will update this if i see same crash again.

Confirming that i have not seen this crash after i removed initialising firebase app second time in my code.
But error msg should be more clear.
Thanks for the help.

@otopba, are you able to confirm if you are also initialising Firebase in the onBackgroundMessage handler? The SQLLite error you're receiving is because there is a concurrent database connection which might be a result of two instances of Firestore.
Or at least, that appears to be what happened with @ssabbarw.

@otopba, are you able to confirm if you are also initialising Firebase in the onBackgroundMessage handler? The SQLLite error you're receiving is because there is a concurrent database connection which might be a result of two instances of Firestore.
Or at least, that appears to be what happened with @ssabbarw.

Yes, that seems to be the problem. The crash happens some time after the user receives the notification via onBackgroundMessage

I Can also confirm this was happening with our app.
Removed Firebase init from onBackgroundMessage and solved the issue.

Removing Firebase init from onBackgroundMessage doesn't compromise the functionality? For example, we are querying Firestore docs onBackgroundMessage... it will keep working without initializing Firebase?

Hello! I get the same problem, here is a link to our sentry log: https://sentry.io/share/issue/3aad3b8795e042419857027891827607/

I think I got a fix!
Instead of calling init in multiple places (onBackgroundMsg, main), do this:
Make this global:
final firebaseInit =
    Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);

And await firebaseInit wherever you need it.
I think what happens is dart reuses the same isolate as the background msg when it starts up.

Hey @najibghadri, thanks for the feedback! @otopba are you able to confirm this behaviour?

@russellwheatley I will try in next release

@russellwheatley Yes, that helped. The error no longer appears

No @russellwheatley this is still gonna call initializeApp as many times as you call init().
This is my solution:
final firebaseInit =
    Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);

It's a call to initializeApp once globally, and instead await firebaseInit. This ensures initializeApp  is called once, and you can await the completed future from wherever, any number of times

So your solution is this instead:
final init = Firebase.initializeApp(options: DefaultFirebaseConfig.platformOptions);

Future<void> _firebaseMessagingBackgroundHandler(RemoteMessage message) async {
  await init;
}

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await init;

  FirebaseMessaging.onBackgroundMessage(_firebaseMessagingBackgroundHandler);

  runApp(MessagingExampleApp());
}

You could say it's a drawback to have a global call to initializeApp, if you don't like this you can implement a proxy that checks if it has been called already, if not it does call initApp

But the real solution would be if this is fixed on the Firebase level, it shouldn't fail on a repeated call.

@russellwheatley Hi!
In my project I did this:
class FirebaseService {
  FirebaseService._();

  static final instance = FirebaseService._();
  Completer? _completer;

  Future<void> init() async {
    Completer? completer = _completer;
    if (completer == null) {
      completer = Completer();
      _completer = completer;
      _initInternal();
    }
    return completer.future;
  }

  void _initInternal() async {
    await Firebase.initializeApp(
      options: const FirebaseOptions(
        apiKey: "XXX",
        authDomain: "XXX",
        databaseURL: "XXX",
        projectId: "XXX",
        storageBucket: "XXX",
        messagingSenderId: "XXX",
        appId: "XXX",
        measurementId: "XXX",
      ),
    );
    _completer!.complete();
  }
}

Future<void> _firebaseMessagingBackgroundHandler(RemoteMessage message) async {
    await FirebaseService.instance.init();
}

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await FirebaseService.instance.init();

  FirebaseMessaging.onBackgroundMessage(_firebaseMessagingBackgroundHandler);

  runApp(App());
}


magic prompt not working

Describe the bug
i get this error when trying to use magic prompt:
Error running process: D:\stable-diffusion-webui\extensions\sd-dynamic-prompts\scripts\dynamic_prompting.py
Traceback (most recent call last):
File "D:\stable-diffusion-webui\modules\scripts.py", line 338, in process
script.process(p, *script_args)
File "D:\stable-diffusion-webui\extensions\sd-dynamic-prompts\scripts\dynamic_prompting.py", line 405, in process
generator = self._create_generator(
File "D:\stable-diffusion-webui\extensions\sd-dynamic-prompts\scripts\dynamic_prompting.py", line 188, in _create_generator
generator = AttentionGenerator(generator, min_attention=min_attention, max_attention=max_attention)
TypeError: AttentionGenerator.init() got an unexpected keyword argument 'min_attention'
To Reproduce
Steps to reproduce the behaviour, include the prompt you used if applicable:

Go to '...' magic prmpt and enable it, enable im feeling lucky, test a prompt
Click on '....' generate, then it adds nothing to the prompt and gets an error in the readout

Also mention which checkboxes have been set.
dynamic prompts checked, magic prompts checked
Expected behaviour
A clear and concise description of what you expected to happen.
i expected it to either change up the prompt or add a new prompt.
this happens whether or not im feeling lucky is checked
Additional context
Add any other context about the problem here.

my bad, i guess you can't have both checked at same time

It doesn't make sense to have both the magic prompt and I'm feeling lucky enabled at the same time, but it shouldn't break. I'll look into it. However, the error that you posted is related to the Attention Generator, I'm surprised that that threw an error. If after you've completely restarted Auto1111 you still see it, please let me know.


JWKSCache: add option to set CA certificate to trust

This is helpful when the JWKS is located on a HTTPS endpoint and the certificate is signed by a custom CA
Code (esp the "GetPEM" method) was copied from components-contrib, from the HTTP binding

Codecov Report
Attention: 18 lines in your changes are missing coverage. Please review.

Comparison is base (77f7f03) 79.98% compared to head (7725bdb) 79.72%.

Files
Patch %
Lines

jwkscache/cache.go
0.00%
18 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #81      +/-   ##
==========================================
- Coverage   79.98%   79.72%   -0.26%
==========================================
  Files          55       55
  Lines        4332     4346      +14
==========================================
  Hits         3465     3465
- Misses        720      734      +14
  Partials      147      147

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix: remove extra padding/margin from both side for mobile view in the projects section

remove extra padding/margin from both sides for mobile view in the projects section
also fix the navbar logo(just using the text) position to the right side a little bit

I want to work on this issue, can you please assign it to me?

I want to work on this issue, can you please assign it to me?

You can work on it 🤝

Thanks

Completed. Thanks for your contributions 🎉 ❤


Cookiecutter directions for new project generation

Resolves [#ISSUE, #ISSUE]

[x] docs/ have been added/updated if necessary

Fixes #273

One last suggestion, I think these instructions should also include a section on how to publish the project to GitHub/GitLab.

@hrshdhgd can you finalise this PR?

I've added the instructions for GitHub. I've never used gitlab so someone else could fill in the blanks there. But from my perspective this should be ready to merge if the TODOs are acceptable to fill in later.


root domain triggers security error

on chrome airline-club.com gets redirected to www.airline-club.com which matches the SSL cert
However for FF and edge, there's no redirect therefore warning is prompted

Fixed the cerbot to generate cert for both the www and non www domain


Add a Gitter chat badge to README.md

DavidCanHelpMe/BrooklynDart now has a Chat Room on Gitter
@DavidLiedle has just created a chat room. You can visit it here: https://gitter.im/BrooklynDart/Lobby.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Cool!


fix: Ignoring prod subdependencies without ropm keyword

Currently, if a prod dependency has another prod dependency that has no "ropm" keyword, ROPM is crashing.
Since NPM v7, the default depth is 1. This change doesn't break on NPM v6 (which has infinity depth by default)

@TwitchBronBron I updated PR's description

@TwitchBronBron any chance to review my 3 PRs soon?

I had hoped to get to them this weekend, but the whole family is sick right now. I'll try real hard to get to them in the next week or so.


Default substep order makes all substeps appear at once

The Substep Plugin documentation states for the default order of substeps:

By default, this plugin reveals substeps in the order in which they appear in the HTML.

However this does not seem to work correctly - when no order is specified, then all substeps appear at once when only the first substep should be visible. This behavior was probably introduced with commit 4c9d2e38aaf1ea038118d4ff6549609df6f1fab3, but I did not test it before that, to be honest.
Both going to the next and to the previous substep are affected.
There seems to be a simple fix, which I will provide as a PR.

Closing issue because PR #856 is going to be merged.


Introduce ChipAnimationStyle to override default chips animations durations

fixes Custom backgroundColor on Chip makes it flicker between state transitions
Example preview

https://github.com/flutter/flutter/assets/48603081/a4949ce7-f38b-4251-8201-ecc570ec447c
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Reason for revert: the newly-added unit test might cause the red tree

Reason for revert: the newly-added unit test might cause the red tree

This has happened on several PRs this week. How are these tests passing in presubmit? cc @christopherfujino I'll file an infra bug

Reason for revert: the newly-added unit test might cause the red tree

This has happened on several PRs this week. How are these tests passing in presubmit? cc @christopherfujino I'll file an infra bug

Looks like we tested the wrong commit in presubmit: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8745894885153659393/+/u/flutter_doctor/stdout
I don't think we even ran this test. Will follow up on the tracking issue.


Cache browser detection

In Utils.js, there are functions e.g. isFirefox() and isSafari() that is used quite often. It's an expensive regex operation. It would speed up performance by caching this in a simple way, e.g. storing (true/false) it in window? or another global place...

Good suggestion, I will improve the browser detection methods.


[AzureRG Deploy] Parsing the override parameter based on the type (#3…

…815)

@ds-ms,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Testing 3.0 — Store stops saving with no error when model changes

Expected result: If the model is changed the schema updates/rewrites/overrides and continues to save using the latest model
Actual result: If the model is changed, the store silently fails to save changes between app launches
Workaround: Delete old store

Hey @blainesolomon, thanks for giving Boutique 3.0 a shot! I want to make sure I understand the scenario correctly so please let me know if I'm answering the wrong question.
I assume the scenario is similar to this model below, where we have a User with this shape:
struct User {
    let id: UUID
    let name: String
}

Now we've updated the User model to add a non-optional property.
struct User {
    let id: UUID
    let name: String
    let isCat: Bool
}

[!IMPORTANT]
Emphasis on non-optional, because optional properties should decode the same way as the model without this new isCat property.

Since the models stored in Boutique will not have an isCat property, they will not decode properly into our new User, leading to the scenario you're describing in your report.
The rest of answer below assumes that this is the problem you're reporting.

Boutique doesn't have a built in way to know that the shape of the model has changed, it will only know that the shape of your models don't align. Deciphering the reason for the failure to decode would involve making assumptions about your desired model layout that I don't feel comfortable doing at the level Boutique operates at.
Instead though I think the correct solution is to run a migration when your model changes shape, modeled after (no pun intended) how database migrations are commonly performed in Core Data or server-side environments. To account for this workflow I've created a handy library called Monarch, which allows you to run a migration whenever your model changes shape. When changing the shape of your model in an app update, what you would do is run a migration that sets a default value for that property, like this.
struct AddIsCatFieldMigration: Migration {
    static let id: MigrationID = "AddDefaultEmailMigration"

    @MigrationDependency private var usersController: UsersController

    func run() async throws {
        let users = self.usersController.users
        try await self.usersController.update(users.map { user in
            var updatedUser = user
            updatedUser.isCat = false
            return updatedUser
        })
    }
}

[!NOTE]
This is how I update the values in my app where I use controllers to manage data and state, there are numerous approaches you can take to do this so I don't mean this answer to be prescriptive.

This is the approach that I take in my apps, and have found it to be a successful tactic. This allows you to have full control over how you update models, which is important because there's no way for Boutique to know why something failed to decode.
Separately, while this isn't the path that I go down in my own apps, if you'd like to bubble up errors whenever the models fail to load rather than silently returning an empty array, there is a throwing variant of the Store's initializer.
public init(storage: StorageEngine, cacheIdentifier: KeyPath<Item, String>) async throws

This initializer will allow you to know that the items in your Store failed to decode rather than receiving an empty array, without asserting any reason as to why that is the case.
Hope that helps, and if I didn't answer your question, do feel free to let me know!

Absolutely amazing. 😍  Such a detailed easy to follow response. That's everything I needed.

Im really happy that was helpful, thanks for letting me know!


PSAdapter escape is missing single quote

Using the PSAdapter with Prestashop 1.7 the search query is broken since no single quotes are added to the where conditions.
A quick workaround is to modify the escape method:
/**
* @param $string
* @param Query $query
* @return string
*/
public function escape($string, Query $query)
{
     return "'" . pSQL($string) . "'";
 }

Does the 1.7 version OK ? If so I'll get it done.

Thank you!


Kurs

using github for now
ckan compat add 1.6

It needs an abstract. Might as well add it to the GH repo:

#rebuild

I've done that, and the output is very strange.  First, it has this error:
DockingCamKURS 1.3.4 requires ModuleManager but it is not listed in the index, or not available for your version of KSP.
and second, even though the .version in the file it downloaded from Github has the following:
  "KSP_VERSION_MIN": {     "MAJOR": 1,     "MINOR": 4,     "PATCH": 5   },   "KSP_VERSION_MAX": {     "MAJOR": 1,     "MINOR": 6,     "PATCH": 1   }
it still seemed to think the min version was 1.7.0.  Is it somehow picking uup the old version?

The "URL" property overrides the contents of the AVC file, and this one says 1.7.0:
https://raw.githubusercontent.com/linuxgurugamer/DockingCam/master/DockingCamera.version


Adding Testing Stage

I would like to have an extra stage that can run arbitrary tests.
This would be for either unit testing via UTF, or to run a TestStand step. It should also allow for adding different testing methodologies in the future.
I would imagine that the build.toml would point to the tests to be run, and it would look similar to the build.steps.

@SimonRPSM has been working on adding test stage in this (fork](https://github.com/SimonRPSM/niveristand-custom-device-build-tools/tree/testStageBranch). We should look at doing a pull request as soon as this is ready.

I have been creating steps for VI Tester

That is great news. I look forward to VI Tester and UTF support making it to master in the near future.

Merged in PR 45.


Error while doing "LastGoodCheckDB": Microsoft.Data.SqlClient.SqlException (0x80131904): When converting a varchar data type to a datetime data type, the value is out of range

Hello there!
We get an attached datetime convert error while doing "LastGoodCheckDB" on on our servers. You can find german error message stack to this post.
Error message:
Microsoft.Data.SqlClient.SqlException (0x80131904): Bei der Konvertierung eines varchar-Datentyps in einen datetime-Datentyp liegt der Wert außerhalb des gültigen Bereichs. Die Anweisung wurde beendet.
(Translated: When converting a varchar data type to a datetime data type, the value is out of range. The statement has ended. )
Windows and SQL Server language: german
Server Collation: Latin1_General_CI_AS
Number of Databases: 15 (same number of error messages)
Please help me to troubleshoot this message further and provide more info to fix this bug.
Thank you.

Hi,
This is the query used for collection:
https://github.com/trimble-oss/dba-dash/blob/main/DBADash/SQL/SQLLastGoodCheckDB.sql
If it's a older SQL version it gets its data from DBCC DBINFO and newer versions will use DATABASEPROPERTYEX.  In both cases it's casting the value to a DATETIME.
It might be worth running the query above on your server to troubleshoot.  You could try removing the CAST to see what the value is.
Let me know what you find.  It will be good to know the value it's trying to cast and if it's from DBCC DBINFO or from DATABASEPROPERTYEX.
Thanks,
David

Hi David,
thanks to point in right direction.
I have multiple SQL Servers running with Language: english and german.
This issue was shown on fully patched SQL Server 2014 with german language, but I found it on other Versions running on german language.
As you correctly pointed out, error pops on all selects containing cast function, where I concentrated to line 38 of your above script.
after troubleshooting it on english SQL 2016 and german SQL 2014, by implementing "SET DATEFORMAT mdy" fixes issues on your script.
I think you have similar issue on all other sql servers with languages different from english.
How shall we procede on this case?

Thank you for the info.  The issue can be changed by using CONVERT instead of CAST for this line of code:
SELECT TOP(1) @DBID, CAST(Value as DATETIME)

To:
SELECT TOP(1) @DBID, CONVERT(DATETIME,Value,120)

I can get this fixed for the next release.
This issue will only impact older versions of SQL server that have a different date format.  The CAST is OK for newer versions of SQL server as DATABASEPROPERTYEX(name,'LastGoodCheckDbTime')  returns a SQL_VARIANT and the underlying type is DATETIME.  It's only on older versions where DBCC DBINFO is used and it needs to convert from a string.
What's interesting is I can't reproduce this on SQL 2014 - DATABASEPROPERTYEX(name,'LastGoodCheckDbTime')  is available on SQL 2014 (At least on SP3-CU4) so it shouldn't need to call DBCC DBINFO per database.
Would you be able to check your version with this:
SELECT @@VERSION

I'm wondering if you might be on SQL 2012 (where I can reproduce the issue) or an older patch version of SQL 2014.
Thanks,
David

Hi David,
my bad, it was one of unpatched SQL 2014 Servers.
Here's Version:
Microsoft SQL Server 2014 - 12.0.2000.8 (X64)   Feb 20 2014 20:04:26   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.3  (Build 17763: ) (Hypervisor)
I should push for upgrade of that server.
Thanks for help with my issue!
Sasa

It looks like `DATABASEPROPERTYEX([DatabaseName], 'lastgoodcheckdbtime') was added to SQL 2014 in SP3 and also added to SQL 2016 in SP2.
It's still a bug in DBA Dash as it should support older versions from SQL 2005 onwards and not be sensitive to language & culture settings used.

Fix to be included in the next release.

David, thanks a lot! :)

Fixed in 2.40.2 🎉


minimessage: Fix exception with single quote as tag part

The parser tries to un-quote tag parts surrounded by quotes, it does so by checking if the first character of the tag part is a quote and the last character is as well. However, things break if that first and last character are actually the same character! A StringIndexOutOfBoundsException is thrown later on.
This patch makes it so tag parts consisting of a single quote aren't tried to be un-quoted, they stay as is
Fixes https://github.com/KyoriPowered/adventure/issues/1011

thank you <3


UNDERTOW-1683 Don't throw an exception if isReady is called before re…

…quest returns
Jira: https://issues.redhat.com/browse/UNDERTOW-1683

I'm merging, given that the failures seem unrelated.


Can we give some top margin to spinner popup so that popup shows after some gap.

Currently am showing spinner but the problem is spinner collapse with its popup. I want to give some top margin to popup so that it will show after spinner

Hey @AzizFasihHazel, in the new release version 1.2.5, you can use the spinner_popup_top_padding attribute. Thanks!

Hi, thank you for your reply.
I want to give padding between the spinner and the drop down that contains
spinner items. This attribute ad space from top of drop down.
[image: Screenshot_20230227-145807.png]
On Sat, 25 Feb 2023 at 09:57, Jaewoong Eum @.***> wrote:

Hey @AzizFasihHazel https://github.com/AzizFasihHazel, in the new
release version 1.2.5, you can use the spinner_popup_top_padding
attribute. Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/skydoves/PowerSpinner/issues/142#issuecomment-1444994030,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5BYB6ABYZTOPYT7UKNDQEDWZGGNJANCNFSM6AAAAAAUDZX6VA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Implement higher-level mappings

Thanks for this library! I very much appreciate having a crate using embedded-hal for this.
Do you have thoughts about implementing higher-level mappings than e.g. the current DigitBits::from_digits - maybe something to convert arbitrary numbers to bytes? We know that we only have 4 digits to work with, so we could offer some nice interfaces here.

@Kernald Thank you for your suggestion.
This functionality was intentionally not implemented due to several reasons:

Function Signature:

fn from_number(number: u16) -> [u8; 4]: Do we want to force users to always allocate 4 bytes of memory?
fn from_number(number: u16, buf: &mut [u8]): Or do we want users to provide their allocated slice?

Function Behavior:

How should the function behave when the number is too big? Should it return an error or ignore the overflow?
How should the function behave when the number of digits is too small? Should it order digits from left to right or from right to left?

Negative Numbers: The minus sign is also supported by the display.
Other Functionalities: Implementing this function could lead to additional features, like UpCharBits::from(s: &str) or converting any sequence of ASCII bytes into the corresponding display bytes.

I've checked how other libraries implement such functionality, but as a user, I find it often makes things more complicated due to all the limitations and edge cases. As a result, I end up adapting my code to work with the library's constraints. For these reasons, I believe it's better for users to implement the logic they are comfortable with.

Cheers - that makes sense! Thanks for the detailed reply.


Hi

Hi I whant some payloads as metasploite from Metasploit on red hack well scanning if can. payluod for everything if can find it . And thanks .

您的邮件我已收到，我将及时查看！谢谢！


workshop subkey PR

add test for contract name check
use whitelist init before set_contract_version to reset version on contract

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


typechain directory not found

Hello,
I executed the yarn command to install node_modules and found the following error.
yarn install v1.22.18
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
[4/5] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "hardhat-gas-reporter ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[5/5] 🔨  Building fresh packages...
$ node ./.setup.js && hardhat typechain
An unexpected error occurred:
hardhat.config.ts:14:35 - error TS2307: Cannot find module './typechain' or its corresponding type declarations.
14 import {APMRegistry, Kernel} from './typechain';
~~~~~~~~~~~~~
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I have solved this problem, thank you very much, just execute the following command first.
yarn add hardhat
yarn hardhat compile


Drag n' drop equipaments

Hello, I currently use the GURPS GAME AID 4TH module on the Foundry VTT, and a situation happened yesterday at my table, one of the players was incapacitated, and his companion wanted to take his sword for himself in combat, but I didn't see a way to transfer the item from one sheet to another, so that I have the right skill level and damage too, any solution?
It can be through some module, macro or formula

The only solution at the moment is to create their sword as a Foundry Item: https://www.youtube.com/watch?v=cOU78-RvXdc
Foundry Items can be dragged and dropped between players.     Otherwise, you would need build it in GCA/GCS and re-import.
This is a well known, and long standing issue.   So I am going to close this.


Test database

There weren't any issues unassigned so I gave this a go.
I figured out how to make a test database the same as our heroku salesforce one.
I had both DB query files on my local branch but didn't commit them as they are on other pull requests.
A lot of the learning is in setUpDB.js
To use:
Run npm run buildtest this creates a local database, schema, user and password
add TEST_DATABASE_URL= postgres://salesforcetester:test@localhost:5432/salesforcetest to your .env
Run npm test

will need modification when the master is up to date after the new PRs are merged

change answer test re .row[0]

really interesting you cant have an ssl connection to a local database


Action doesn't support headers linking to github releases

I like to use the following format in the footer of my changelog so my release headers link to the github release pages themselves, but this doesn't appear to be supported with this action:
[Unreleased]: https://github.com/foo/bar/compare/v0.0.2...HEAD
[0.0.2]: https://github.com/foo/bar/releases/tag/v0.0.2
[0.0.1]: https://github.com/foo/bar/releases/tag/v0.0.1

When I run the action I get the following error:
Run<EMAIL_ADDRESS>(node:1591) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Error: Invalid changelog format, compare url is not standard

Action code:
      - name: Update Changelog
        uses<EMAIL_ADDRESS>        with:
          tag: ${{ github.ref_name }}

Is this something you would be able to support in future? Perhaps by detecting the format and using it automatically.

The idea of the compare URL (as per spec: https://keepachangelog.com/en/1.0.0/) is to provide people with an overview of what code changed between two versions.
I never considered supporting anything outside of that, nor have I ever seen linking to the actual release. I am not opposed to it but the spec also mentions that the changelog itself is more of an alternative to GitHub releases rather and a complement. What is the value of linking to the GitHub release if all the information should arguable already be in the changelog? What do users discover there that they can't see in the changelog?

I've been thinking it over and I might just switch to follow it exactly as it's such a minor change. Like I said it was just a personal preference.
I quite liked how the initial release linked directly to the download page and my thinking at the time was that was more intuitive to users, as I wouldn't think most people are interested in the git logs (that's why we have a changelog!).
It would be much appreciated if you'd still like to support custom link formats, but I certainly don't expect it.
Many thanks for providing this extension either way!

I am glad it works for you :)
I'll close this then. If someone else needs custom link formats at some point, we can discuss that either here or in a new issue!


DNN-8867: improving folder permission caching.

Improving folder permission caching.

George, please remove "with (NoLock)" hints. I haven't been able to notice minimal performance improvements (tested on SQL Server 2012) and the risk to affect proper results is way to high and in a platform product like DNN, you cannot test all use cases. There are way better options to improve database performance than using critical edge case options like this.

changes looks good, and merge into development branch.


fix: show error on invalid JSON in rule config

Fix https://github.com/eslint/playground/issues/42
https://user-images.githubusercontent.com/46647141/169676782-d5d60b68-4db5-4e87-8eda-d75a7973c76b.mov

I get an error when I remove a rule with invalid JSON and then add the rule back with a valid default configuration.
https://user-images.githubusercontent.com/44349756/169915130-e00211a5-9c6e-4df7-80f3-1d6ae6f31af3.mp4

@mdjermanovic resolved, can you check once again?


Add example for extracting text from MesagesResponseBody

Adds some code to the create_a_message example to demonstrate how to extract the actual response text from the MessagesResponseBody and its Content::MultipleBlock content field.
I was also thinking that it might be nice to have a simple text extractor function within MessagesResponseBody which returns something like a Result<String, Err> like body.content.text, which returns the text from either the SingleText or first MultipleBlock if it exists (and the number of ContentBlocks is 1).
What do you think?
  ~/code/m-clust ~>> git branch
    main
  * textblock_example
  ~/code/m-clust ~>> cargo run --example create_a_message -- -p hello -m hello
      Finished dev [unoptimized + debuginfo] target(s) in 0.24s
       Running `target/debug/examples/create_a_message -p hello -m hello`
  Entire result:
  {
    "id": "msg_013vikkX9jdN9sHnhphbQ7ZY",
    "type": "message",
    "role": "assistant",
    "content": [
      {
        "type": "text",
        "text": "Hello! How can I assist you today?"
      }
    ],
    "model": "claude-3-haiku-20240307",
    "stop_reason": "end_turn",
    "stop_sequence": null,
    "usage": {
      "input_tokens": 9,
      "output_tokens": 12
    }
  }
  Multi-block response text: Hello! How can I assist you today?

@mikecvet
Thank you for your pull request.

I was also thinking that it might be nice to have a simple text extractor function within MessagesResponseBody which returns something like a Result<String, Err> like body.content.text, which returns the text from either the SingleText or first MultipleBlock if it exists (and the number of ContentBlocks is 1).

That is a good idea!
I implemented clust::messages::Content::flatten_into_text() along with your idea:
https://github.com/mochi-neko/clust/blob/4500a91e92240fd1e707c1279ed39171599d454d/src/messages/content.rs#L88
and add code for examples:
https://github.com/mochi-neko/clust/blob/4500a91e92240fd1e707c1279ed39171599d454d/examples/create_a_message.rs#L66
on the latest main branch.
If there seem to be no issues, I'm going to release it in v0.6.0.

That is a good idea!
I implemented clust::messages::Content::flatten_into_text() along with your idea

This looks great. Thanks!

Thank you, too!


Streamline validate signatures, remove essentialErrorInfo

Move collectSchemas and call it prior to actual validation
Streamline signatures
Remove essentialErrorInfo as it adds little to no value

Coverage increased (+0.2%) to 91.139% when pulling e9254b5c84c91857d02a42a9a8a2b4b358d2f8e7 on edgarmueller:master into 5df2c24bd5b1885cf42dc139aa06646ab0009767 on eclipsesource:master.


Replace Census Household Schema

What is the context of this PR?
Changes to census_household.json
Trello
How to review

Have I copied and pasted correctly and yarn formatted?
I have also modified existing tests which broke since they were referencing the old test_census_household schema.

Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

Need some changes. Doesn't pass validator and routing can be improved.

I have removed some of the redundant routings. Ensure that the changes are equivalent.
There are also routing rules that can be done as skip conditions instead but I have not done this for the time being.

Updated unit and functional tests that referenced the old census schema.

Cool, I'll merge this then, though I haven't reviewed properly.


judges-action#190: add pull_request_reviews to Fbe::FakeOctokit

Need for https://github.com/zerocracy/judges-action/issues/190

@Yegorov Thanks for your contribution! As per our policy, you've earned +4 points: +4 base, -16 for no code review, -16 for no reviewer comments, and +32 to meet the minimum reward. Remember, code reviews and comments are crucial for better rewards. Keep contributing and aim for more hits-of-code to maximize your points. Your current balance is +441. 💻👍


SQL error is shown to the user

When trying to create a repository with a name of an existing repository, the following error is printed:
Error executing command: error creating repository: insert repository: ERROR: duplicate key value violates unique constr aint "catalog_repositories_name_uindex" (SQLSTATE 23505)
This should be changed to a user-friendly error.
Example command to reproduce:
lakectl repo create lakefs://existing-repo s3://example-bucket

I would like to take a shot at this

👋🏾 I'd like to take this one

Hello @ari-hacks! It's all yours.
If you need any assistance - please join our slack channel:
https://join.slack.com/t/lakefs/shared_invite/zt-g86mkroy-186GzaxR4xOar1i1Us0bzw

Awesome, thanks!

@ari-hacks are you working on this one or can I try?

@avats-dev yep, still assigned. 🙂


Clarify that Stop errors are not app errors

There is still confusion in BSOD analysis about whether a user-mode
process can cause a stop error and it is important to clarify that they
cannot.

This PR was suggested in a twitter discussion (https://twitter.com/ASwisstone/status/1376647562573271053) of the challenges of convincing customers that a BSOD that is triggered by our app is actually the fault of a driver/hardware/OS problem

Just a suggestion, based on my previous experience with MS Docs and the general codestyle therein. Would it be practical to set this additional text in a colored Note blob?
For comparison, the document contains 2 Note blobs and a Warning blob already, just in case you are wondering what it may look like.
Formatting suggestion:
> [!NOTE]
> The root cause of Stop errors is never a user-mode process. While a user-mode process (such as Notepad or Slack) may trigger a Stop error, it is merely exposing the underlying bug which is always in a driver, hardware, or the OS.

Good idea. Done.

@randomascii Although it is common OS knowledge that the mentioned errors cannot surface from the user-mode processes, the note might be useful for the confused readers. It might take a few days to have this PR copy edited and approved. Thank you for the PR and hope you contribute to the Docs again.

Understood. Thanks for the help with the process.

#sign-off


Require from in TransferFrom in CW721 pointer to be the owner

Describe your changes and provide context
Require from to be the owner of the NFT being transferred
Testing performed to validate your change
unit test

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.57%. Comparing base (9186601) to head (0cc9c64).

Additional details and impacted files

@@            Coverage Diff             @@
##            seiv2    #1516      +/-   ##
==========================================
+ Coverage   60.51%   60.57%   +0.05%
==========================================
  Files         363      363
  Lines       25703    25703
==========================================
+ Hits        15555    15569      +14
+ Misses       9175     9162      -13
+ Partials      973      972       -1

Files
Coverage Δ

x/evm/keeper/pointer.go
78.20% <100.00%> (ø)

... and 2 files with indirect coverage changes


setSelection is not working

Materialspinner.setSelection(Index) is not working with this library

hi,
try this
spinner.post(new Runnable() {
@Override
public void run() {
spinner.setSelection(index);
}
});

hi roygwsidev,
this worked for me
thanks

Thanks for the answer :)


Use texture sampler in HLSL

When trying to sample a texture in hlsl I get an error from this: https://github.com/attackgoat/screen-13/blob/71c1c05f74c17d0ca891ae784d3e701c8fdcbc12/src/graph/resolver.rs#L810
With the enum vk::DescriptorType::Sampler
I'm setting the sampler for the fragment shader with: .image_sampler((0, 1), sampler)
struct FullscreenVertexOutput
{
    float4 position : SV_Position;
    [[vk::location(0)]]
    float2 uv : TEXCOORD0;
};

[[vk::binding(0, 0)]]
Texture2D screenTexture : register(t0);
[[vk::binding(1, 0)]]
SamplerState textureSampler : register(s0);
float4 main(FullscreenVertexOutput input)
    : SV_Target
{
    return screenTexture.Sample(textureSampler, input.uv);
}

This GLSL version using a combined sampler works as expected:
#version 450

layout(binding = 0) uniform sampler2D screenTexture;

layout(location = 0) in vec2 inUV;
layout(location = 0) out vec4 outColor;

void main() { outColor = texture(screenTexture, inUV); }

Are only combined sampler currently supported?
DXC appears to support [[vk::combinedImageSampler]], but shaderc does not: https://github.com/google/shaderc/issues/1310

Thanks for the detailed issue description and links! I added support to examples/image_sampler.rs showing how to use combined and separate samplers for both GLSL and HLSL.
This was a feature I haven't needed myself and so it was unimplemented. There may be more things like that.


test-branch/execute-job/comment-from-wrong-user-on-pr/6fb43298-ffe8-4d51-9ee0-9419a8b1c4bf

PR for testing 9c4c5d9f44a65af3f6a393695f2a628dd0cb62a3

/canonical/self-hosted-runners/run-workflows 9c4c5d9f44a65af3f6a393695f2a628dd0cb62a3


refactor!: Replace 'r lifetime with 'static

Hey there, first of all, thank you for this project!
While checking the library and doing some implementation, I saw that it was "hard" to carry around a multipart (taking a look on the viability of using it on warp).
So, this change would make that a stream is bound to 'static, correct me if I am wrong but, usually that is the case, right? Do you see an use where that would not be true?
Let me know if this change makes sense or not.
Thanks in advance!

Another option there if a reference is needed, I could try to make an Owned version of it, wdyt?

Having second thoughts here, I just checked rocket's implementation and this change would break the API of multer I will just close the pr but still, fell free to comment if an owned version makes sense.

That's right - you want the lifetime! You can always alias the type with a 'static.


New Azure Logs area

Area(s)
area:new
Is your change request related to a problem? Please describe.
As discussed in the following PR that contributes Azure logs transformations to the OpenTelemetry Collector Contrib, this issue proposes to add new semantic conventions for Azure Logs.

https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32486

Describe the solution you'd like
New Azure Logs section for semantic conventions.
Describe alternatives you've considered
No response
Additional context
No response

@MikeGoldsmith is this something you will be working on? Can I assign this to you then if so?


Pivnet resource out should allow me to specify a Docs URL

We have found another interesting case, where we need the ability to specify a Docs Url. Currently, before posting our product to PivNet, we make a post to api/v2/product_files so that we can specify custom information, such as file_version, docs_url, and system_requirements. Since this falls into a new endpoint, product_files, please let me know if you want me to create a separate issue or this one is ok. Thus far, it seems like the PivNet resource only supports metadata around releases, plus the addition of the information that should happen as a result in #15. This is another unrelated field that we would like to dynamically configure.
Thanks,
Morgan

@mfine30 the metadata file currently supports a top-level product_files key where you can specify the name, the description, and upload_as to rename file during upload.
It sounds like you want the ability to add the following nested fields to that existing key:
---
product_files
- file: /some/path/to/file
  version: some-version
  docs_url: https://some.docs.url
  system_requirements:
  - some_requirement
  - another_requirement

Does this meet your requirements?
Thanks,
Rob

@robdimsdale Yes please. That does indeed cover my requirements.
Thanks,
Morgan

Thanks. I created a story to cover this:

pivnet resource out should support extra product_files metadata

I'll close this issue now.
Thanks,
Rob


HPO doesn't throw any error on passing an empty string

Passing an empty string to some of the fields (experiment_id, trial_result, result_value_type) in the HPO experiment or results json doesn't throw any error message.
To recreate the issue:

Run ./deploy_hpo.sh -c native
Post the experiment json using the curl command
Below is an example curl command to post an experiment with empty string for experiment_id

curl -s -H 'Content-Type: application/json' http://localhost:8085/experiment_trials -d '{"operation":"EXP_TRIAL_GENERATE_NEW","search_space":{"experiment_name":"petclinic-sample-2-75884c5549-npvgd","total_trials":5,"parallel_trials":1,"experiment_id":" ","value_type":"double","hpo_algo_impl":"optuna_tpe","objective_function":"transaction_response_time","tunables":[{"value_type":"double","lower_bound":150,"name":"memoryRequest","upper_bound":300,"step":1},{"value_type":"double","lower_bound":1,"name":"cpuRequest","upper_bound":3,"step":0.01}],"slo_class":"response_time","direction":"minimize"}}'

There are other scenarios that do not throw any error messages:

Pass an invalid experiment id
Pass an invalid searchspace - Tested it with just a couple of paraeters (direction & slo_class) by passing invalid values


[Share as a skill] Only root bot intents are shown in task selection. UI suggests that Dialog selection and subsequent intent selection are related but they are not.

UI suggests that Dialog selection and subsequent intent selection are related but they are not.
** 1: Select dialogs in share as a skill wizard:**

** 2: Intents shown in the subsequent screen only shows the root bot intents..**

Issue: UI makes it seem that intents shown are based on the dialog selection.

@mareekuh fyi for design backlog


Add fuzzing setup for Message::decode

See fuzz/README.md for details on how to run it.

@kpcyrd Sorry for disturbing you but if you don't mind could you look at this fuzzer setup and see if anything is obviously broken?
Thanks in advance! :bow: and have a nice day! :wave:

Thank you very much for your suggestions @kpcyrd :pray:

However, you can create a new slice with identical pointer and length like so (this is a very cheap operation):

Ha, right. I was aware of the in-memory layout of fat pointers but didn't connect that &data[..] creates a new one :man_facepalming:

The &mut is needed because it's expected by Message::decode, if it would take something like decode<R: Read>(mut reader: R) -> Result you could drop the extra &mut too. I'm not sure if that's a worthwhile idea though. Reader is implemented for impl Reader for Decoder<'_> and I'm not sure if the decode function would then insist on taking ownership of Decoder.

Alright. (Un)fortunately I don't control the Decode trait (since it comes from the RustCrypto's crate) and I've come with at different design for my other SSH crate that uses look-ahead parser (similar to programming languages).

The patch looks good to me now. 👍

Thanks a lot for your time and explanations. I really appreciate them! :bow:
I'll let the PR sit for a couple of days in case the other maintainers feel like commenting and if not merge it.
:wave:

Sure, you're welcome! :)


Can't trigger touch handler in Simulator or device(iPhone 6 plus)

hello guys :)
I download SwiftCharts Demo and run it in Simulator and Device.
But in example "Notification (interactive)" and "Show touch coords (interactive)" , I touch screen at some point can't trigger any touch handler.(e.g. popup a view and etc...)

I look into the source code for those example :NotificationExample.swift and CoordsExample.swift , I think it should be trigger some touch handler ...
What's wrong with it? thanks ;)

I uploaded a fix, please update master!
Will also do a release soon.

thanks! but could you tell me why can't touch before?

ok.I zoomed chart 2x before show it:
chart.delegate = self
chart.zoom(scaleX: 2, scaleY: 1, centerX: 0, centerY: 0)
and I also set chart's zoom setting:
chartSettings.zoomPan.maxZoomX = 20
chartSettings.zoomPan.minZoomX = 1
when I run app it show like that:

you can see points in the chart have some offset to left,I except it show like that:

In my code , the points layer is :
layerPP = ChartPointsViewsLayer(xAxis: xAxisLayer.axis, yAxis: yAxisLayer.axis, chartPoints: chartPoints, viewGenerator: circleViewGenerator, displayDelay: 0.9, delayBetweenItems: 0.5, mode: .translate)
Do I need do something with layerPP? thanks again ;)

The touch was because there's a view on top of the container to handle a special type of transform which was consuming the taps. This view shouldn't be always interactive.
The problem you're experiencing is a relatively new area, that needs some improvements. Theoretically the solution would be to set delayInit: true on the layer and call myViewLayer.initViews(chart) after the chart has been initialized, such that it gets the correct transforms, the same way it's done with the line layer in the example you're using. But it turns that this doesn't work on the view layer when you use min/max zooming.
A partial workaround for this would be to set the initial zoom programmatically instead of using min/max, of course you lose min/max, but other than that works as expected. So after creation of the chart you call
chart.zoom(deltaX: 2, deltaY: 1)

(You probably also want to pass 0, 0 anchor such that it starts at the origin, or call pan to start with a specific offset).
And then after the chart has been added as subview myViewsLayer.initViews(chart).
(And don't forget to pass delayInit: true to the views layer).
It may also work with min/max depending on the values you pass, you could experiment a little with that.
Let me know if that works for you.

It's look like not work for me :(
`
//chartSettings.zoomPan.maxZoomX = 20
//chartSettings.zoomPan.minZoomX = 1
//chartSettings.zoomPan.minZoomY = 1
//chartSettings.zoomPan.maxZoomY = 1
    let chartPointsCircleLayer = ChartPointsViewsLayer(xAxis: xAxisLayer.axis, yAxis: yAxisLayer.axis, chartPoints: chartPoints, viewGenerator: circleViewGenerator, conflictSolver: nil, displayDelay: 1.0, delayBetweenItems: 0.3, mode: .translate, keepOnFront: true, delayInit: true, clipViews: true)

    let chart = Chart(
        frame: chartFrame,
        innerFrame: innerFrame,
        settings: chartSettings,
        layers: [
            xAxisLayer,
            yAxisLayer,
            guidelinesLayer,
            chartPointsLineLayer,
            chartPointsCircleLayer
            ]
    )

    view.addSubview(chart.view)
    chart.zoom(scaleX: 2, scaleY: 1, centerX: 0, centerY: 0)

    chartPointsLineLayer.initScreenLines(chart)
    chartPointsCircleLayer.initViews(chart)

    chart.delegate = self
    self.chart = chart`

It's that what you mean?
demo is below :

you can see in the demo gif,when first into view, the points's position is wrong,but when I pan on the chart view ,their positions back to right!
what should I do?thanks  :)

update :
when I change code to below , It's seem like to work:
chart.zoom(scaleX: 2, scaleY: 1, centerX: 0, centerY: 0)
chartPointsLineLayer.initScreenLines(chart)

chartPointsCircleLayer.initViews(chart)
chartPointsCircleLayer.zoom(2, y: 1, centerX: 0, centerY: 0)

chart.delegate = self
self.chart = chart

I insert code chartPointsCircleLayer.zoom() after chartPointsCircleLayer.initViews(chart)

But I have another question :  How can I hide the guidelinesLayer in chart programmatically???
I can't find method like layer.isHide() or chart.hideLayer() in SwiftCharts
I read it carefully your example code in : MultipleAxesInteractiveExample.swift
but it's too complicated to me,I try according it to modify my code,but it's not successed ;(
Is there any easy way to make it works? thanks a lot ;)

No worries. Most of SwiftCharts is immutable, so to hide layers you have to recreate the chart.
You'd have something like createChart(hasGuidelines: Bool) and depending on the parameter add or not add the guidelines.

ok! I will try it ,thanks


Controller reset

It's such a good PID controller.
But it doesn't have a very useful reset function (reset an integral part and derivative part). The controller "off" function doesn't do it.
For example, you shut down the heater manually (via power switch) but the controller will still collect integral and derivative errors(or will turn on with the collected errors.). It is impossible to startup it clean.
Reset function will be such a good improvement.

I can see that could be useful.  If you disable the controller at the same time that you switch the heater off then it will lock the integral at the current value, preventing it winding up.
Pull Requests are always welcome.

But after the next start, I will still have initial errors and don't have any ability for the clean start.
Unfortunately, I'm not so familiar with js)

But after the next start, I will still have initial errors

Can you explain what you mean by that?

May be reset controller on every on/off is a good idea? For which reason it memorize accumulated errors?

If that were done then you would get the opposite effect to that which you don't like.  If you switched it into the disabled state (I assume that is what you mean by on/off) for just a short time and back to automatic there would be a kick in the process due to the integral term no longer matching the process conditions.

As I understand the PID controller principle, we need to accumulate and store 2 things thru time - an integral error and derivative error. After controller on/off those accumulated parameters are still in controller.
I installed and tested many hardware PID controllers and after resetting controller power (for the hardware controller this means zeroing accumulated integral and derivative errors) on the working system we will get only a small deviation in the worse case.  It can't be any kick, because of in the heating system(for example) integral part in steady regulation always more than zero, temperature not changed after resetting the controller(very short time), so P-part is still the same cause it = SP(not changed) - MV(not changed), so  P+I > P+0, so you will get a little drop of controller output value.

Could you post a chart showing the problem you are seeing. please, so I can better understand the issue. The chart should include the process value and the PID output value.

Please, pay attention to the chart.
Yesterday I reset the controller(restart PC) before start chemical feeding.
After I disable chemical feeding w/o stopping the controller for the night
and enable chemical feeding in the morning.
I'm not changing any controller parameters. SP=0.4, PB=0.4, Integral time =
2000s, Diff time = 60s
Look what can do the accumulated integral error with the process.
That's why I asked about the controller reset option.
[image: Capture2.PNG]
вт, 11 февр. 2020 г. в 11:20, Colin Law<EMAIL_ADDRESS>
Could you post a chart showing the problem you are seeing. please, so I
can better understand the issue. The chart should include the process value
and the PID output value.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/colinl/node-red-contrib-pid/issues/11?email_source=notifications&email_token=ACHTPJUVBX6CCXZQQHSLHNLRCJNWNA5CNFSM4KOYS2O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELLROMQ#issuecomment-584521522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHTPJUW2DIYFOJFYXKOEQDRCJNWNANCNFSM4KOYS2OQ
.

Unfortunately the image does not seem to have appeared, at least I can't see it.

Please find an image by link below
https://i.yapx.ru/GoMYW.png
чт, 12 мар. 2020 г. в 00:35, Colin Law<EMAIL_ADDRESS>
Unfortunately the image does not seem to have appeared, at least I can't
see it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/colinl/node-red-contrib-pid/issues/11#issuecomment-597889719,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHTPJRYUOGLGYZYVPO7SITRG772ZANCNFSM4KOYS2OQ
.

As I said previously I need to see the PID output value as well as the process value in order fully to understand what is going on.
When you get that you should be able to upload it by clicking on the "Attach files ..." link below the field for entering comments. I have not bothered fetching and uploading this one as without the pid output value it is not very helpful without the output value.
You did not make it clear whether the controller was put into manual mode when the power was switched off, as it should of course. In fact the best way to switch it off is to put the controller into manual and set the power in the controller.


Have dependency count contribute towards package score

Delaying this feature due to the large changes as part of #1292.
We should give packages with a small number of dependencies a score boost.

+10 points for zero resolved dependencies.
+5 for one or two dependencies.
No adjustment for anything more than two dependencies.

Given that #1300 isn't going to be feasible in the short term, I think we should adjust the scoring to this:

+10 points for 1 or 2 resolved dependencies.
+5 for less than 5.
No adjustment for anything more than 5.

Actually… Given that the number of dependencies is a less strong signal without #1300, I think the total available points for this should also be reduced.

+5 points for 1 or 2 resolved dependencies.
+2 for less than 5.
No adjustment for anything more than 5.


added option in the angular module for disabling syncing to the JS

This is useful when the developer wants to implement the JS persistence logic on his own. I changed it because I needed the following in my project.

I have an attribute called position, which holds each item position (1,2...)
then angular can use it to sort the list, without ever changing the order of the array elements, from this:

myArray = [
  {id: 100, name: "Alice", position: 1},
  {id: 200, name: "Bob", position: 2},
  {id: 300, name: "Charlie", position: 3}
]

to this:
myArray = [
  {id: 100, name: "Alice", position: 1},
  {id: 200, name: "Bob", position: 3},
  {id: 300, name: "Charlie", position: 2}
]

That works well for me, because with angular I can do:

{{object.name}}

$scope.sortableOptions = {
    ...
    skipSync: true
}

I can not take this PR, it breaks a event onAdd.
Can add an event onSync before scope.$apply:
onSync: function (evt) {
   // ... calculate `position`
}

Can you elaborate? I am having a hard time understanding what I should do.
If I understood correctly, I should start with:
onSync: function (/**Event*/evt) {
  _emitEvent(evt);
  // ... calculate `position`
}
onAdd: function (/**Event*/evt) {
	_sync(evt);
	_emitEvent(evt, removed);
	scope.$apply();
},
onUpdate: function (/**Event*/evt) {
	_sync(evt);
	_emitEvent(evt);
},

If it helps, here it is how I implement updating the "position" attribute in my code (Coffeescript), which runs in a directive (so that I don't need to call $scope.$apply()).
Right now it does reordering only.
onUpdate: (evt) ->
  # Helpers
  if evt.oldIndex < evt.newIndex
    predicate       = (record) -> evt.oldIndex < record.position <= evt.newIndex
    updateRecord    = (record) -> record.position--
    findNewPosition = (array)  -> Math.max.apply(null, array)
  else
    predicate       = (record) -> evt.newIndex <= record.position < evt.oldIndex
    updateRecord    = (record) -> record.position++
    findNewPosition = (array)  -> Math.min.apply(null, array)

  # Let's find out which records have been affected
  partition = evt.models.filter predicate

  # Change positions in the JS
  evt.model.position = findNewPosition partition.pluck('position')
  partition.forEach updateRecord


When starting a container fails, don't wait until the full timeout;

When starting a container fails, don't wait until the full timeout; bail out immediately.
I'm using "finishedAt" to tell if the container did start and finish. This was a change mentioned in #107, but this isn't a total fix for that issue.
This seems like a relatively safe change, and makes failures in container start a bit less annoying to troubleshoot.

.... and, not so much on the "safe" change. I believe this is a race condition issue. The order of operations I expected was:

attempt to start container
container fails to start
inspect container status: running=false, finishedWhen=nonzero
--> we conclude that container stopped

This is what I see when I run this locally. However, what appears to be happening in TravisCI is:

attempt to start container
container begins to start
inspect container status: running=true
--> we assume container started correctly
container fails to start

I can get around that by adding a minimum runtime; any container that hasn't been running at least that long will not be considered running. A small default value will eliminate this case, while also adding what might be useful functionality for containers that don't listen on a port.

Ah, that sounds unfortunate, but I guess good to have detected now.
So basically the process achieves 'running' state but crashes within milliseconds?
I think the small minimum threshold you suggest sounds right as long as the value is very small. Implementation wise is it not equivalent to a Thread.sleep before starting to check the container status?
Perhaps it's worth making configurable and defaulting to 0ms; I get the feeling that this is going to be something that some use cases need but others don't. What do you think?

On 2 Apr 2016, at 03:35, ostacey<EMAIL_ADDRESS>wrote:
.... and, not so much on the "safe" change. I believe this is a race condition issue. The order of operations I expected was:
attempt to start container
container fails to start
inspect container status: running=false, finishedWhen=nonzero
--> we conclude that container stopped
This is what I see when I run this locally. However, what appears to be happening in TravisCI is:
attempt to start container
container begins to start
inspect container status: running=true
--> we assume container started correctly
container fails to start
I can get around that by adding a minimum runtime; any container that hasn't been running at least that long will not be considered running. A small default value will eliminate this case, while also adding what might be useful functionality for containers that don't listen on a port.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

Sorry for my absence over the last few days - I'm looking at this now!


Force device type?

Describe Your Problem:

I updated Node, Homebridge, and the Meross and UI plug-ins this week. Since then, I have some MSS110 devices set up to display as power outlets in the Meross app on iOS and yet they show up as lights in the Home app and Homebridge UI.
Is there a way to change the type of a device to a power outlet instead of a light?
Environment:

Node.js Version:  14.15.3
NPM Version:  6.14.9
Homebridge Version:  1.1.7
Homebridge Meross Plugin Version: 3.4.1
Homebridge Config UI X Plugin Version: 4.36.0
Operating System:  Raspbian

I just reverted the Meross plugin to 3.1.0 and that seems to fix the issue. Maybe it's a bug?

See #151

#151 isn’t addressing the issue described here, or at least not directly. It’s about what I read is going to become a new plugin for Meross cloud support.
I’m just not going to update the plugin, as the old one is working got me, and wait.

#151 isn’t addressing the issue described here, or at least not directly. It’s about what I read is going to become a new plugin for Meross cloud support.
I’m just not going to update the plugin, as the old one is working got me, and wait.

Proposed #170 to fix this problem

Proposed #170 to fix this problem

@MrJer I have pushed through your PR! Thanks! It is in the beta branch which will push a new beta if that want's to be tested out?

@MrJer I have pushed through your PR! Thanks! It is in the beta branch which will push a new beta if that want's to be tested out?

@donavanbecker happy to help! Just pulled down v3.4.2-beta.4 and MSS110-2 is showing correctly as outlet now.

@donavanbecker happy to help! Just pulled down v3.4.2-beta.4 and MSS110-2 is showing correctly as outlet now.


introduce 2 new env vars to config ThreadCache initial state

new variables:
TCMALLOC_BATCH_SIZE_FROM_START:
Set the thread cache max length size to num_objects_to_move(cl) if defined
The default behavior is to set the initial max_length to 1 and increment it by 1 each time objects are fetched. Once the max_lenght reaches num_objects_to_move(cl), the max_length is now incremented by num_objects_to_move(cl) as it has been demonstrated that this particular size is in high demand.
This is done that way to minimize memory wasting. Bigger blocks are allocated only once the need for this size class has been confirmed.
If the possibility of wasting some memory is acceptable, enabling this option to eliminate the ramp-up period will:

reduce number of accesses to the central heap
Preserve the data locality of the objects in opposition to have the address space distributed evenly across all the caches if a particular size is requested by all threads.

This second point is not only valid when the client code access the allocated memory but also when the memory is deallocated when it is put back into a free list.
TCMALLOC_INITIAL_THREAD_CACHE_BYTES:
Set the initial cache max_size_ value.
The default behavior is to initialize the value to kStealAmount (64Kb) and increment it by kStealAmount each time a Scavenge() is triggered when a cache size reach the max_size value. This approach is the best to efficiently distribute the heap across all the caches but this imply several accesses to the central heap.
If you know the number of created threads by a process this env variable allows you to manually distribute the heap across all the threads and eliminates several central heap accesses needed to reach their stable size.
results:
The after results have been obtained with the following setting:
LD_PRELOAD=/usr/lib/libtcmalloc_minimal.so TCMALLOC_RELEASE_RATE=0 TCMALLOC_TRANSFER_NUM_OBJ=1024 TCMALLOC_MAX_TOTAL_THREAD_CACHE_BYTES=100000000 TCMALLOC_INITIAL_THREAD_CACHE_BYTES=2000000 TCMALLOC_BATCH_SIZE_FROM_START=1
This appears to be an experiment that turns out to be inconclusive. With some parameters, the performance is better,
with some others the performance is worse.
It is by far a clear-cut winner. I am not convinced myself that this should be integrated in the project.
I mostly share this experiment to stimulate and influence other experiments in that area to improve the project...
maybe with a different approach or angle, some tweaking of the idea, someone could make it work better.

this modif idea came while investigating https://github.com/gperftools/gperftools/issues/1549

Thanks for the patch. Yes, I am not convinced too. Mostly on the grounds of keeping things simpler. More tuning knobs means we have to test more. And more chances for more odd behaviors.
Patch-wise, I only want to point out that in Google C++ style and this project we always do braces even for single statement if/else things as you can see around places you changed. So for future changes (or this one if you somehow find good reasons to merge), please adjust accordingly.

ok. I have taken good note of the coding style adopted by the project... I try to look around what the code look like and respect as much as I can the style that I see... but I definitely drop few ones unintentionally.
I have mostly contributed to linux kernel lately which has a totally different style...

So, closing under assumption that this is exposing too much of internal details as noted above. Thanks for suggestion, though. Feel free to reopen if I misunderstood and you still want some version of this merged.


Add files via upload

Apologies, one of your files 1987.json is incorrect. It should be 1988.json

Thank you, sorry for the error. I have corrected the mistake, please have a look now.


Do not cache 500 responses

Description
Fix: Hydrogen no longer caches 500 responses. Any 500 response will not have a cache control-header, nor will Hydrogen cache it internally.
Additional context

Before submitting the PR, please make sure you do the following:

[X] Read the Contributing Guidelines
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[X] Update docs in this repository according to your change
[X] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

Is it possible to add a test that breaks after making a sfapi request? like .. the sfapi request itself succeeds but sub sequent request or code fails


No such file or directory

using A1111 1.10 working fine but now this error:
Error opening input files: No such file or directory
An exception occurred: Could't extract frames with ffmpeg.

Seems solved: https://civitai.com/articles/6203/v2v-helper-extension-to-create-videos-inside-automatic1111


StaggeredGridLayout

Any news about this? Would love to use your library in one of my upcoming projects.

@mradzinski, I have a couple of features in milestone 4 that I have to
implement first, then this will be my first priority.
On Mon, 2 Feb 2015 23:26 mradzinski<EMAIL_ADDRESS>wrote:

Any news about this? Would love to use your library in one of my upcoming
projects.
—
Reply to this email directly or view it on GitHub
https://github.com/TonicArtos/SuperSLiM/issues/6#issuecomment-72560984.


How to prevent close modal when press android back

I have a loading modal and I don't want close it when android back pressed

backButtonClose={false} it's already in documentation and this is default.

Even with backButtonClose={false}, the modal closes, even isDisabled={false} doesn't work.

Same here, backButtonClose={false} does not work

Okay, it's actually related to the default React-Native Modal component behavior I think, just remove the onRequestClose callback in the ModalBox implementation file, this callback is triggered when the back button is pressed, removing it solved the issue for me.

Actually rather than doing that it'd be better to check the backButtonClose prop there

I need this working, so I'll be doing a PR later today

Finally I'm found this problem. Because I'm show modal by "isOpen" props so it can't add listener event back android.


The Height is same as the status bar

Hi, I am facing a strange problem if I don't have the navigation bar. When the toast shows, the height of it is same as the status bar, so it is difficult to see. How could extend it to cover the navigation bar? Thanks.

Sorry, find the kCRToastNotificationTypeKey to set it. Case closed. Thanks.


Question: Limine on non-x86 systems

Is there a template for Limine running on ARM? Probably assuming a specific platform like the Raspberry Pi or the plain "virt" target on qemu, I guess (to avoid having too much trouble from platforms being too different?)

The AArch64 Zig target is still a bit rusty from what I remember, but I'll take a look later to see if it's possible. The last time I tried it had trouble emitting code for a feature set equivalent to the one we currently use for x86_64.

Any reasonable feature set would be fine by me (I want to expand my own OS to also support aarch64, and for the moment I'll just target the "virt" platform -- when I'm in a better spot I'll probably do more than that).

I added support for aarch64 in e659a4d9d9de77e665207721dce69e0e14af2816 and riscv64 in f235818370c45d91d8108d8cc4c946d423617b9b.