feat: Add additional metrics for shuffle write

Which issue does this PR close?

N/A
Rationale for this change

I would like to understand how much time is spent on shuffle writing.
What changes are included in this PR?

Introduce a new write_time native metric to record write time instead of using elapsed_time
Use elapsed_time to measure total native time (excluding executing the child plan and fetching data)
Add new input_time native metric for measuring the time for ShuffleWriterExec to execute the child plan and fetch its input data
Add new shuffleWallTime JVM metric to measure total time of shuffle
Update docs

Spark UI
Note the new metrics:

"native shuffle time"
"native shuffle input time"
"shuffle wall time"

Native plan
ShuffleWriterExec: ..., metrics=[elapsed_compute=42.425493ms, ..., input_time=255.873165ms, write_time=462.517µs]
  ScanExec: source=[ShuffleWriterInput], metrics=[elapsed_compute=254.994282ms, ...]

How are these changes tested?

Also added ipc_time.

Seeing some segmentation faults in CI:
# Problematic frame:
# C  [libcomet-9228012970092653184.so+0x274908f]  core::sync::atomic::AtomicUsize::fetch_add::h50346ebf04f5a2ef+0x4f

I may have found a bug in DataFusion
 # A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fb91a124f46, pid=762, tid=833
#
# JRE version: OpenJDK Runtime Environment Zulu11.76+21-CA (11.0.25+9) (build 11.0.25+9-LTS)
# Java VM: OpenJDK 64-Bit Server VM Zulu11.76+21-CA (11.0.25+9-LTS, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libcomet-1968252056067325991.so+0x1524f46]  datafusion_physical_plan::metrics::value::ScopedTimerGuard::stop::ha579d5e7b5f1a919+0x46

I created a new simpler PR to replace this one: https://github.com/apache/datafusion-comet/pull/1175


Streamline "advance" function

Coverage increased (+0.004%) to 98.549% when pulling 7b48600a6b83ee0fb4d6dbb5c6b37d453cc604a1 on jugglinmike:streamline-advance into d965038168d6deff2e4f3e82f1054f9373df7a3b on jshint:master.


[Discussion] Why the input of the model is 44kHz in config file

From FAQ, we know the model was trained on 11kHz. But in separation code, the input audio of the model is 44kHz (in the config file). Is there a conflict here?

Hi @yzspku,
this is a bit more complex than that. As explained in the FAQ, the model was actually not trained on 11kHz but up to 11kHz on spectrograms computed from signal sampled at 44.1kHz (this parameter can be changed for training a system for scratch, but should not be changed at inference time).
So the idea is that input (mix) and target (separated instruments) spectrograms are computed on 44.1kHz signal, so they have frequencies up to 44.1/2 = 22.05kHz. But for memory efficiency reason, the spectrogram were trimmed at 11kHz before training. The advantage of doing that instead of processing signals sampled with a lower frequency is that it still makes it possible to perform the separation at frequencies up to 22.05kHz by extending the output spectrograms or masks (either with a post-hoc method by extending masks with the mask_extension parameter of the config file or just by extending the frequency reconstruction of the model by changing the F parameter of the config file at inference). For instance, setting F to 1536, as done in the xx-16kHz configs, will process the signal up to 16kHz.


Task/maguire7/2019 01 mili plugin rewrite

Description
The new mili plugin! There are a lot of changes here: avtMilIFileFormat has been almost entirely re-written, I've added avtMiliMetaData for support, and I've updated rapidjson. These are the bulk of the changes.
I've update the test suite and data as well. The old .mili files will no longer work, but I've updated the makemili module in visit/src/bin to the new version, which generates the correct .mil files.
Tests that have changed:
mili.py has been completely re-written. I've tried to capture all of the edge cases I can think of in the new test.
pick.py has some mili focused tests which have been updated.
queriesOverTime.py also has mili focused tests that have been updated.

[ ] Bug fix
[x] New feature
[ ] New Documentation
[ ] Other (please describe below)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have updated the release notes
[ ] I have made corresponding changes to the documentation
[x] I have added debugging support to my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added any new baselines to the repo
[x] I have assigned reviewers (see VisIt's PR procedures for more information).

This is the same as the RC branch, but it is up-to-date with develop.

@aowen87 ... just wanna say a BIG THANK YOU! For all the work you put in on this. It represents a huge improvement over the old plugin. Great work!

No problem!


feat: fix _psChild bug

hi：
when i open my electron app, i use si.powerShellStart() to create a new powerShell process，then i get some hardware infos, eg：cpu gpu display...I only need to get the above information once。So after 5 seconds I call  si.powerShellRelease(); But the windows pop-up window reported an error：kill is not defined，so i fix it
in lib/utils.js
line 403

@iplaycodex fixed. Version 5.17.2 just released ... my fault, sorry!

error reproduces in<EMAIL_ADDRESS>after same actions: I call powerShellStart(), then get specs, after all call powerShellRelease()
C:\Users\user\node_modules\systeminformation\lib\util.js:419
        _psChild.kill();
                 ^

TypeError: Cannot read properties of null (reading 'kill')
    at ChildProcess.<anonymous> (C:\Users\user\node_modules\systeminformation\lib\util.js:419:18)
    at ChildProcess.emit (node:events:517:28)
    at maybeClose (node:internal/child_process:1098:16)
    at ChildProcess._handle.onexit (node:internal/child_process:303:5)

您的邮件已经收到,谢谢!

@sebhildebrandt Probably fix was wrong; @iplaycodex fixs line 403; but in main fixed line 417.

@iplaycodex @xoxloviwan ... fixed, new version 5.22.10 just released.


Add a clearer error message for when ODBC header files are missing (Install unixodbc)

Issue
I recently encountered what seems to be a common error for users, whereby if one pip install pyodbc without having the "ODBC header files" (i.e. one hasn't installed unixodbc), then you get something that looks like the following:
In file included from src/buffer.cpp:12:0:
    src/pyodbc.h:56:10: fatal error: sql.h: No such file or directory
     #include <sql.h>
              ^~~~~~~
    compilation terminated.
    error: command 'gcc' failed with exit status 1

Googling around and looking at previous GH issues here, I can eventually determine that if one installs conda install unixodbc or something like unixodbc-dev, then this problem is remediated.
However, I'm wondering if a change could be put in the neatly handle this error, perhaps printing to the user
"Installation failed. Please install unixodbc and retry"
This seems to be a common and recurring problem, I've found 3 historical issues about the same thing, so this change would definitely add value to the UX of pyodbc users!
#276
#793
#441

This error is from the gcc compiler, not sure pyODBC installer can do much about it. Also the exact package where the headers are can have different names on different OSs, updating the installation guide (if it doesn't include some scenarios) might be the best bet

For reference: installation guide is here https://github.com/mkleehammer/pyodbc/wiki/Install#installing-on-linux

You are right that it would be a great idea, but I really don't see how to do so in a way that won't cause other problems.  It might be possible to capture the compiler output and scan it for hints that it might be the problem.  I'm going to close this for now as I don't think I can do much right now, but I will keep it in mind.  Maybe a build problems FAQ would help

You are right that it would be a great idea, but I really don't see how to do so in a way that won't cause other problems.  It might be possible to capture the compiler output and scan it for hints that it might be the problem.  I'm going to close this for now as I don't think I can do much right now, but I will keep it in mind.  Maybe a build problems FAQ would help


KerasImageFileEstimator api cannot work with dataset as explained in keras_image_file_estimator.py

Hi, I am using sparkdl module from databricks. I am trying to  run an application using KerasImageFileEstimator. I am using the example explained in the keras_image_file_estimator.py which creates a dataset by
stringIndexer = StringIndexer(inputCol="imageLabel", outputCol="categoryIndex")
indexed_dateset = stringIndexer.fit(original_dataset).transform(original_dataset)
encoder = OneHotEncoder(inputCol="categoryIndex", outputCol="categoryVec")
image_dataset = encoder.transform(indexed_dateset)
I am getting error when I run
transformers = estimator.fit(image_dataset)
and the error is
_keras_label = row[label_col].array
AttributeError: 'SparseVector' object has no attribute 'array'
As far as I understand, the problem is OneHotEncoder returns a SparseVector (categoryVec) and SparseVector which is row[label_col] here does not have an attribute called array. Error raised from the _getNumpyFeaturesAndLabels function in keras_image_file_estimator.py.
I could not find a solution to this. So if you can help me, I would be glad.

Thanks for raising this issue! Based on the context and error message, we think that https://github.com/databricks/spark-deep-learning/pull/125 should fix it. If you need an immediate work around, you might have to ensure that the column represented by labelCol Param of your estimator ("categoryVector" ?) is a DenseVector by applying some custom udf to it.


Unify theme item lookup in Controls and respect default font

Okay, let's try this. This is 3.x only. Fixes https://github.com/godotengine/godot/issues/36614.
The problem was that the default font defined on any theme is never respected when looking up theme items from controls. The only way to receive the default font is to either directly fetch it from the Theme or to ask that Theme for an item that doesn't exist without checking with has_... first. This means that you can never, realistically, hit it for controls automatically. And that means, you can never get it from the custom project theme.
Now, this change is a fix for this behavior, and it matches the behavior currently present in master (added in https://github.com/godotengine/godot/pull/41100). This fix means that if any theme in the lookup chain has a default font, it will be used (as fallback), and no further lookup will be performed. This breaks current behavior, but I don't think that the impact of that change outweighs the benefit. In fact, since the default font never worked as expected, I doubt anyone actually used it. So I think this change is justified for 3.5.

While at it I've also unified the theme item lookup to match what we have in master. This can probably fix a few issues as well, since the old behavior was arbitrary for each theme item type. I excluded shaders from this change, since they are already deprecated and I don't want to add a shader type to the DataType enum and possibly create problems for the theme editor and other stuff.
This change is rather exciting, as it lays the groundwork for a backport of theme type variations (https://github.com/godotengine/godot/pull/50169). If this is accepted, theme type variations can be added without any compatibility breakage and can be a very cool feature for 3.5.

Still works!


core: fix duplicated definition

Refactor remove() function name to avoid
duplicated function definition when building
on latest AOSP. stdio in Bionic also defines
remove().

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

I'm unclear why this is an issue; it's a static function in a ".c" file, not publicly-visible or in a header file. The compiler should just resolve this reference to the corresponding reference in the same linkage unit. Are you not able to build in your environment, or are you getting shadow warnings or some other issue?

I'm building grpc as part of the AOSP framework. When building against bionic libc the
header file has a dependency on stdio.h which also defines a remove() function causing the build to fail.
bionic headers:
https://android.googlesource.com/platform/bionic/+/master/libc/include/stdio.h#144

Ok, I see. Thanks for your contribution. I'll make review comments and I'm asking for another reviewer on this as well.

Thanks for the review @vjpai. I updated the pull request with the requested change.

@vjpai ping.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Hi @y-zeng, could you please look at this? There is no reviewer activity for some time.
Thanks,
Zoltan

Jenkins, test this please

Oops! The current code is not mergeable because of formatting. Can you run
tools/distrib/clang_format_code.sh ? You may need to do this with sudo depending on how your docker is configured.

Formatting applied. It should be good now.

Jenkins, test this please

Thanks, @kuscsik , we'll merge it soon.

Test failures: #9542 and issue being addressed in #10848


Broken styles when using Tables\Group

Package
filament/filament
Package Version
v3.0@beta
Laravel Version
10
Livewire Version
v3
PHP Version
php 8.2
Problem description

Styling on table row when using the group is showing classes as text and not rendered as html
Expected behavior
Expected to be rendered as HTML
Steps to reproduce
Use table grouping
Reproduction repository
https://github.com/unable
Relevant log output
No response

Upgrade Filament, but please submit a reproduction in the future.


Error running plugin

Running the plugging stalemates for about 1-2 seconds then crashes zellij with
Received empty message from server

Looking at the logs i have:
WARN   |zellij_server::route     | 2023-08-13 17:29:47.732 [server_router] [zellij-server/src/route.rs:877]: Server ready, retrying sending instruction.
WARN   |zellij_server::plugins   | 2023-08-13 17:29:49.840 [wasm      ] [zellij-server/src/plugins/mod.rs:177]: Plugin /home/yendor/.config/zellij/plugins/cached.wasm not found, starting it instead
WARN   |zellij_utils::ipc        | 2023-08-13 17:29:52.086 [router    ] [zellij-utils/src/ipc.rs:230]: Error in IpcReceiver.recv(): InvalidMarkerRead(Error { kind: UnexpectedEof, message: "failed to fill whole buffer" })
ERROR  |zellij_client            | 2023-08-13 17:29:52.086 [router    ] [zellij-client/src/lib.rs:309]: Received empty message from server
WARN   |zellij_utils::input::layo| 2023-08-13 17:31:49.834 [main      ] [zellij-utils/src/input/layout.rs:867]: Failed to read swap layout file: /home/yendor/.config/zellij/layouts/main.swap.kdl. Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
INFO   |zellij_client            | 2023-08-13 17:31:49.836 [main      ] [zellij-client/src/lib.rs:143]: Starting Zellij client!
INFO   |zellij_server            | 2023-08-13 17:31:49.839 [main      ] [zellij-server/src/lib.rs:237]: Starting Zellij server!
INFO   |zellij_server            | 2023-08-13 17:31:49.890 [main      ] [zellij-server/src/lib.rs:862]: Compiling plugins using Cranelift
INFO   |zellij_server::plugins   | 2023-08-13 17:31:49.890 [wasm      ] [zellij-server/src/plugins/mod.rs:124]: Wasm main thread starts
INFO   |zellij_server::plugins::p| 2023-08-13 17:31:49.898 [async-std/runti] [zellij-server/src/plugins/plugin_loader.rs:595]: Loaded plugin 'tab-bar' from cache folder at '/home/yendor/.cache/zellij' in 4.693828ms
INFO   |zellij_server::plugins::p| 2023-08-13 17:31:49.899 [async-std/runti] [zellij-server/src/plugins/plugin_loader.rs:595]: Loaded plugin 'compact-bar' from cache folder at '/home/yendor/.cache/zellij' in 5.797197ms
INFO   |zellij_server::plugins::p| 2023-08-13 17:31:49.901 [async-std/runti] [zellij-server/src/plugins/plugin_loader.rs:595]: Loaded plugin 'status-bar' from cache folder at '/home/yendor/.cache/zellij' in 7.017377ms
WARN   |zellij_utils::input::layo| 2023-08-13 17:31:50.280 [main      ] [zellij-utils/src/input/layout.rs:867]: Failed to read swap layout file: ./dev.swap.kdl. Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
INFO   |zellij_server::plugins::p| 2023-08-13 17:31:50.349 [async-std/runti] [zellij-server/src/plugins/plugin_loader.rs:595]: Loaded plugin '/home/yendor/Downloads/harpoon/target/wasm32-wasi/debug/harpoon.wasm' from cache folder at '/home/yendor/.cache/zellij' in 17.748806ms
INFO   |zellij_server::plugins::p| 2023-08-13 17:31:50.683 [async-std/runti] [zellij-server/src/plugins/plugin_loader.rs:634]: Compiled plugin '/home/yendor/Downloads/harpoon/target/wasm32-wasi/debug/harpoon.wasm' in 262.540233ms
INFO   |zellij_server::plugins::w| 2023-08-13 17:32:31.338 [wasm      ] [zellij-server/src/plugins/wasm_bridge.rs:194]: Bye from plugin 4
WARN   |zellij_server::plugins   | 2023-08-13 17:32:34.369 [wasm      ] [zellij-server/src/plugins/mod.rs:177]: Plugin /home/yendor/Downloads/harpoon/target/wasm32-wasi/debug/harpoon.wasm not found, starting it instead
INFO   |zellij_server::plugins::p| 2023-08-13 17:32:36.910 [async-std/runti] [zellij-server/src/plugins/plugin_loader.rs:634]: Compiled plugin '/home/yendor/Downloads/harpoon/target/wasm32-wasi/debug/harpoon.wasm' in 250.850439ms
WARN   |zellij_utils::ipc        | 2023-08-13 17:32:43.381 [router    ] [zellij-utils/src/ipc.rs:230]: Error in IpcReceiver.recv(): InvalidMarkerRead(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })
ERROR  |zellij_client            | 2023-08-13 17:32:43.381 [router    ] [zellij-client/src/lib.rs:309]: Received empty message from server

It looks like Plugin /home/yendor/.config/zellij/plugins/cached.wasm not found. Did you build manually or using the build.sh script?
If manually, did you install cached as well? For harpoon to work we also need to run this plugin in the background to keep track of the state.

If you update Zellij to the new 0.38.0 release and reinstall harpoon it should now work without the extra setup.


[QUESTION] Could --rustdoc-json-toolchain be part of the public API?

My use case is that I'm caching a specific version of cargo-public-api in a CI job so that it won't be recompiled every run. The problem is that eventually nightly will be incompatible with the cached version. So I would like to tell cargo-public-api to use a pinned nightly version instead of the latest one. Looking through the repo, I realized that this flag would do the job, but it is undocumented. Could this feature be stabilized in some way?
Thank you for considering it!

It's a funny coincidence because 3 hours before you filed this issue I created a PR to stabilize it because I recently got the insight that it is useful for the exact use case you are describing 😀
See https://github.com/Enselic/cargo-public-api/pull/109 which I will merge and release in the coming days

Oh wow, I did look into the issues before opening this one, but I guess I forgot to look at the PRs as well (oops).
Using --toolchain would be intuitive enough, great!
Should I close this now or wait for the merge?

No worries at all! I closed it via PR because that is much more fun than closing via the close button :)

Awesome and thank you!

Heads-up: Newly released v0.15.0 supports an even more convenient syntax to specify toolchain: cargo +toolchain public-api

Checking the active toolchain is great! it's working fine with rust-toolchain files :grinning:.


Mood detection using Face Recognition

Using image processing, recognize face and determine the mood of the person (happy, sad, etc.)

Kindly assign this issue to me under gssoc'23

I have experience in a similar field, and I would also like to contribute to this. Is it possible for me to help in this issue as well??

Hi , I would like to work on this issue

hi, could you please assign me this task under gssoc 23.

hi,could you assign me this task

Hi can you please assign me this task under gssoc'23.
Thanks

Can you assign me this issue @akshitagupta15june


Notebook focus indicator is not pixel perfect

When hovering this, it expands further left than right as 3px total are being added:

This might be due to my monitor scaling. The fact that it's styled via border-left is suspicious though.


Reload not working on Windows since #9424

Summary
I have this issues for a few days now and i could track it back to the commit #9424. Before that, the reload and hot reload worked fine and now it loses the connection to my device. I tried it with multiple physical and virtual devices (Android). On linux everything seems to work just fine.
Steps to Reproduce

Create a new project
Add a new Dart file, doesn't matter if empty or not
Import Dart file into main.dart
Try HotReload or FullReload

Verbose log
[  +24 ms] [E:\Flutter\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[  +36 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] [E:\Flutter\flutter\] git ls-remote --get-url origin
[  +19 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[        ] [E:\Flutter\flutter\] git log -n 1 --pretty=format:%H
[  +18 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] ad496e142b9a1c114dea65e7d87e474cd85dd5c2
[        ] [E:\Flutter\flutter\] git log -n 1 --pretty=format:%ar
[  +16 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[        ] 4 hours ago
[ +215 ms] E:\Android\sdk\platform-tools\adb devices -l
[  +14 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb devices -l
[        ] List of devices attached
           9SYTGAZP99999999       device product:cm_mt6795 model:mediatek_mt6795 device:mt6795
[  +10 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell getprop
[  +96 ms] Launching lib/main.dart on mediatek mt6795 in debug mode...
[ +115 ms] Using gradle from C:\Program Files\Android\Android Studio\gradle\gradle-3.3\bin\gradle.bat.
[   +1 ms] [android\] C:\Program Files\Android\Android Studio\gradle\gradle-3.3\bin\gradle.bat app:properties
[+1263 ms] Exit code 0 from: C:\Program Files\Android\Android Studio\gradle\gradle-3.3\bin\gradle.bat app:properties
[  +14 ms] E:\Android\sdk\build-tools\25.0.2\aapt dump badging build\app/outputs/apk/app.apk
[  +18 ms] Exit code 0 from: E:\Android\sdk\build-tools\25.0.2\aapt dump badging build\app/outputs/apk/app.apk
[        ] package: name='com.yourcompany.HotReloadBugTest' versionCode='1' versionName='0.0.1' platformBuildVersionName='7.1.1'
           sdkVersion:'16'
           targetSdkVersion:'21'
           uses-permission: name='android.permission.INTERNET'
           application-icon-160:'res/mipmap-mdpi-v4/ic_launcher.png'
           application-icon-240:'res/mipmap-hdpi-v4/ic_launcher.png'
           application-icon-320:'res/mipmap-xhdpi-v4/ic_launcher.png'
           application-icon-480:'res/mipmap-xxhdpi-v4/ic_launcher.png'
           application-icon-640:'res/mipmap-xxxhdpi-v4/ic_launcher.png'
           application: label='' icon='res/mipmap-mdpi-v4/ic_launcher.png'
           application-debuggable
           launchable-activity: name='com.yourcompany.HotReloadBugTest.MainActivity'  label='' icon=''
           feature-group: label=''
             uses-feature: name='android.hardware.faketouch'
             uses-implied-feature: name='android.hardware.faketouch' reason='default feature for all apps'
           main
           supports-screens: 'small' 'normal' 'large' 'xlarge'
           supports-any-density: 'true'
           locales:
           densities: '160' '240' '320' '480' '640'
           native-code: 'armeabi-v7a' 'x86' 'x86_64'
[ +429 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 logcat -v time -t 1
[  +75 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 logcat -v time -t 1
[        ] --------- beginning of main
           04-22 14:17:10.536 E/Accel   (  828): AccelerationSensor: unknown event (type=2, code=7)
[   +5 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 logcat -v time
[   +2 ms] E:\Android\sdk\platform-tools\adb version
[  +10 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb version
[        ] Android Debug Bridge version 1.0.39
           Revision 5943271ace17-android
[   +3 ms] E:\Android\sdk\platform-tools\adb start-server
[  +12 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb start-server
[        ] Building APK
[  +20 ms] Using gradle from C:\Program Files\Android\Android Studio\gradle\gradle-3.3\bin\gradle.bat.
[   +2 ms] Running 'gradle assembleDebug'...
[   +1 ms] [android\] C:\Program Files\Android\Android Studio\gradle\gradle-3.3\bin\gradle.bat -Ptarget=E:\Flutter\HotReloadBugTest\lib/main.dart assembleDebug
[+1315 ms] The JavaCompile.setDependencyCacheDir() method has been deprecated and is scheduled to be removed in Gradle 4.0.
[   +1 ms]      at build_8zmbh5u1xup9qf2dtx4d0g1yt$_run_closure2.doCall(E:\Flutter\HotReloadBugTest\android\build.gradle:20)
[   +1 ms] Incremental java compilation is an incubating feature.
[   +6 ms] The TaskInputs.source(Object) method has been deprecated and is scheduled to be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty() instead.
[   +1 ms]      at build_8zmbh5u1xup9qf2dtx4d0g1yt$_run_closure2.doCall(E:\Flutter\HotReloadBugTest\android\build.gradle:20)
[  +79 ms] :app:flutterBuildX86Jar UP-TO-DATE
[        ] :app:preBuild UP-TO-DATE
[        ] :app:preDebugBuild UP-TO-DATE
[   +1 ms] :app:checkDebugManifest
[        ] :app:prepareDebugDependencies
[   +1 ms] :app:compileDebugAidl UP-TO-DATE
[   +1 ms] :app:compileDebugRenderscript UP-TO-DATE
[   +3 ms] :app:generateDebugBuildConfig UP-TO-DATE
[+5831 ms] :app:flutterBuildDebug
[   +3 ms] :app:mergeDebugShaders UP-TO-DATE
[   +1 ms] :app:compileDebugShaders UP-TO-DATE
[        ] :app:generateDebugAssets UP-TO-DATE
[   +2 ms] :app:mergeDebugAssets UP-TO-DATE
[  +16 ms] :app:copyFlutterAssetsDebug
[   +1 ms] :app:generateDebugResValues UP-TO-DATE
[        ] :app:generateDebugResources UP-TO-DATE
[   +4 ms] :app:mergeDebugResources UP-TO-DATE
[   +3 ms] :app:processDebugManifest UP-TO-DATE
[   +4 ms] :app:processDebugResources UP-TO-DATE
[        ] :app:generateDebugSources UP-TO-DATE
[   +4 ms] :app:incrementalDebugJavaCompilationSafeguard UP-TO-DATE
[   +6 ms] :app:compileDebugJavaWithJavac UP-TO-DATE
[   +3 ms] :app:compileDebugNdk UP-TO-DATE
[   +2 ms] :app:compileDebugSources UP-TO-DATE
[   +1 ms] :app:transformClassesWithDexForDebug UP-TO-DATE
[   +1 ms] :app:mergeDebugJniLibFolders UP-TO-DATE
[   +2 ms] :app:transformNative_libsWithMergeJniLibsForDebug UP-TO-DATE
[   +1 ms] :app:processDebugJavaRes UP-TO-DATE
[   +3 ms] :app:transformResourcesWithMergeJavaResForDebug UP-TO-DATE
[   +1 ms] :app:validateSigningDebug
[+1016 ms] :app:packageDebug
[   +1 ms] :app:assembleDebug
[   +1 ms] BUILD SUCCESSFUL
[        ] Total time: 8.266 secs
[ +368 ms] calculateSha: build\app/outputs/apk/app.apk
[ +289 ms] Built build\app/outputs/apk/app-debug.apk (21.9MB).
[        ] E:\Android\sdk\build-tools\25.0.2\aapt dump badging build\app/outputs/apk/app.apk
[   +6 ms] Exit code 0 from: E:\Android\sdk\build-tools\25.0.2\aapt dump badging build\app/outputs/apk/app.apk
[        ] package: name='com.yourcompany.HotReloadBugTest' versionCode='1' versionName='0.0.1' platformBuildVersionName='7.1.1'
           sdkVersion:'16'
           targetSdkVersion:'21'
           uses-permission: name='android.permission.INTERNET'
           application-icon-160:'res/mipmap-mdpi-v4/ic_launcher.png'
           application-icon-240:'res/mipmap-hdpi-v4/ic_launcher.png'
           application-icon-320:'res/mipmap-xhdpi-v4/ic_launcher.png'
           application-icon-480:'res/mipmap-xxhdpi-v4/ic_launcher.png'
           application-icon-640:'res/mipmap-xxxhdpi-v4/ic_launcher.png'
           application: label='' icon='res/mipmap-mdpi-v4/ic_launcher.png'
           application-debuggable
           launchable-activity: name='com.yourcompany.HotReloadBugTest.MainActivity'  label='' icon=''
           feature-group: label=''
             uses-feature: name='android.hardware.faketouch'
             uses-implied-feature: name='android.hardware.faketouch' reason='default feature for all apps'
           main
           supports-screens: 'small' 'normal' 'large' 'xlarge'
           supports-any-density: 'true'
           locales:
           densities: '160' '240' '320' '480' '640'
           native-code: 'armeabi-v7a' 'x86' 'x86_64'
[   +3 ms] Stopping app 'app.apk' on mediatek mt6795.
[        ] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell am force-stop com.yourcompany.HotReloadBugTest
[ +574 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell pm list packages com.yourcompany.HotReloadBugTest
[ +547 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell pm list packages com.yourcompany.HotReloadBugTest
[   +1 ms] package:com.yourcompany.HotReloadBugTest
[   +4 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell cat /data/local/tmp/sky.com.yourcompany.HotReloadBugTest.sha1
[  +42 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell cat /data/local/tmp/sky.com.yourcompany.HotReloadBugTest.sha1
[   +1 ms] eba5988537aad60097aded2182d833c0579ec9dd
[   +2 ms] Installing APK.
[   +1 ms] E:\Android\sdk\platform-tools\adb version
[  +16 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb version
[        ] Android Debug Bridge version 1.0.39
           Revision 5943271ace17-android
[   +1 ms] E:\Android\sdk\platform-tools\adb start-server
[  +17 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb start-server
[        ] Installing build\app/outputs/apk/app.apk...
[   +2 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 install -r build\app/outputs/apk/app.apk
[+5586 ms] [  0%] /data/local/tmp/app.apk
                   [  0%] /data/local/tmp/app.apk
                   [  1%] /data/local/tmp/app.apk
                   [  1%] /data/local/tmp/app.apk
                   ... (nothing special here)
                   [100%] /data/local/tmp/app.apk
                   build\app/outputs/apk/app.apk: 1 file pushed. 6.5 MB/s (22952830 bytes in 3.380s)
                        pkg: /data/local/tmp/app.apk
                   Success
[   +8 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell echo -n 4d204be13c6c8b6ccf49cd9a7b4d6049b931f146 > /data/local/tmp/sky.com.yourcompany.HotReloadBugTest.sha1
[  +24 ms] mediatek mt6795 startApp
[   +1 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell am start -a android.intent.action.RUN -f 0x20000000 --ez enable-background-compilation true --ez enable-dart-profiling true --ez enable-checked-mode true com.yourcompany.HotReloadBugTest/com.yourcompany.HotReloadBugTest.MainActivity
[ +592 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 shell am start -a android.intent.action.RUN -f 0x20000000 --ez enable-background-compilation true --ez enable-dart-profiling true --ez enable-checked-mode true com.yourcompany.HotReloadBugTest/com.yourcompany.HotReloadBugTest.MainActivity
[   +1 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.yourcompany.HotReloadBugTest/.MainActivity (has extras) }
[   +2 ms] Waiting for observatory port to be available...
[ +572 ms] Diagnostic server Uri on device: http://<IP_ADDRESS>:38169/
[   +9 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 forward tcp:8101 tcp:38169
[  +20 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 forward tcp:8101 tcp:38169
[        ] Forwarded host port 8101 to device port 38169 for Diagnostic server
[   +1 ms] Observatory Uri on device: http://<IP_ADDRESS>:37602/
[   +1 ms] E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 forward tcp:8100 tcp:37602
[  +14 ms] Exit code 0 from: E:\Android\sdk\platform-tools\adb -s 9SYTGAZP99999999 forward tcp:8100 tcp:37602
[        ] Forwarded host port 8100 to device port 37602 for Observatory
[  +21 ms] Connected to service protocol: http://<IP_ADDRESS>:8100/
[+1313 ms] DevFS: Creating new filesystem on the device (null)
[  +66 ms] DevFS: Created new filesystem on the device (file:///data/user/0/com.yourcompany.HotReloadBugTest/cache/HotReloadBugTestvIfCnY/HotReloadBugTest/)
[   +3 ms] Updating assets
[ +120 ms] Syncing files to device...
[   +2 ms] DevFS: Starting sync from LocalDirectory: 'E:\Flutter\HotReloadBugTest'
[        ] Scanning project files
[   +4 ms] Scanning package files
[  +50 ms] Scanning asset files
[        ] Scanning for deleted files
[  +18 ms] Updating files
[+3949 ms] DevFS: Sync finished
[        ] Synced 5.8MB.
[  +15 ms] Connected to _flutterView/0xe9f5de60.
[        ] 🔥  To hot reload your app on the fly, press "r". To restart the app entirely, press "R".
[        ] The Observatory debugger and profiler is available at: http://<IP_ADDRESS>:8100/
[        ] For a more detailed help message, press "h". To quit, press "q".
[+3546 ms] Initializing hot reload...
[   +2 ms] Refreshing active FlutterViews before reloading.
[ +223 ms] Syncing files to device...
[        ] DevFS: Starting sync from LocalDirectory: 'E:\Flutter\HotReloadBugTest'
[        ] Scanning project files
[        ] Scanning package files
[  +15 ms] Scanning asset files
[        ] Scanning for deleted files
[  +14 ms] DevFS: Sync finished
[        ] Synced 0.0MB.
[+1533 ms] Service protocol connection closed.
[   +2 ms] Lost connection to device.
[   +4 ms] DevFS: Deleting filesystem on the device (file:///data/user/0/com.yourcompany.HotReloadBugTest/cache/HotReloadBugTestvIfCnY/HotReloadBugTest/)
[ +252 ms] TimeoutException after 0:00:00.250000: Future not completed
[   +2 ms] 'flutter run' took 30503ms.
[ +128 ms] ensureAnalyticsSent: 124ms
[   +2 ms] exiting with code 0

Flutter Doctor
[√] Flutter (on Microsoft Windows [Version 10.0.15063], channel master)
    • Flutter at E:\Flutter\flutter
    • Framework revision ad496e142b (4 hours ago), 2017-04-22 10:27:03 +0200
    • Engine revision a5b64899c9
    • Tools Dart version 1.23.0-dev.11.11

[√] Host Executable Compatibility
    • Downloaded executables execute on host

[√] Android toolchain - develop for Android devices (Android SDK 25.0.2)
    • Android SDK at E:\Android\sdk
    • Platform android-25, build-tools 25.0.2
    • ANDROID_HOME = E:\Android
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version: OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[√] Android Studio (version 2.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Gradle version 3.3
    • Java version: OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[√] IntelliJ IDEA Community Edition (version 2017.1)
    • Dart plugin version 171.4249.16
    • Flutter plugin version 13.0

[√] Connected devices
    • mediatek mt6795 • 9SYTGAZP99999999 • android-arm • Android 6.0.1 (API 23)

@johnmccutchan @goderbauer

The "Lost connection to device." message indicates that the engine/shell has crashed. No error messages though? @goderbauer can you reproduce on a Windows machine?

Sadly i got no error message and that made it quite hard to track down the "exact" issue. Something to note here the examples are working.

I am currently unable to reproduce this on my Windows machine. According to flutter doctor the only difference between my setup and @susch19's setup is that I am still running Windows 10.0.14393 and that I am deploying to a different device:
• Nexus 6P • 84B5T15A10012703 • android-arm • Android 7.1.1 (API 25)

Other than that, our environments are identical.

@susch19 What do you mean by "the examples are working"? Do you only see this error with one specific flutter project? Or with all flutter projects on your machine?

@goderbauer All projects, except the examples included in flutter. As i written in the first post, even a new project has the same bug.

@susch19 Can you run flutter run --bug-report and perform the actions that lead to the crash? This should create a zip file with the bug report that you can send to me for further investigation.

Should i just attach it to a comment or how would you like to get the file?

That would be fine.

It's bigger than 10mb, so i uploaded it to gdrive:
https://drive.google.com/file/d/0B-nt7mNORQw-bHNLVUFOYWJ6bGc/view?usp=sharing

I think I figured it out:
This is a problem with the case-insensitivity of file names on Windows and them being case sensitive on Android. In other words, Windows doesn't care if a file is names Test.dart or test.dart. For Windows (and Dart on Windows), it's the same. However, when we copy the file over to Android, it is important that we distinguish between the two. For Android (and Dart on Android) Test.dart and test.dart are not the same! I'll work on fixing this in our code. Until that's available, there is a work-around:
Work-around: You should follow dart convention (see [1]) and name your dart packages as well as all dart files using lowercase_with_underscores style (see [1] for examples of that style in the Dart style guide). For your example, that means HotReloadBugTest should be renamed to hot_reload_bug_test, Test.dart should be renamed to test.dart and you should import it with import 'package:hot_reload_bug_test/test.dart'. If you follow this convention of naming your packages using the  lowercase_with_underscores style, hot reload should work as expected.
[1] https://www.dartlang.org/guides/language/effective-dart/style#do-name-libraries-and-source-files-using-lowercasewithunderscores

@goderbauer Thank you, this has worked

I've updated the title of this bug to better reflect what we've discovered.

Fixed with #9571.


Clicking the Port:  status bar entry should show a picker with some Live Preview commands

Testing https://github.com/microsoft/vscode/issues/125855
I didn't realize I needed to kill the server, I thought just closing the embedded browser would be enough. I tried clicking on the "Port: 3000" status bar entry, but there was no guidance on how to make that status bar entry go away.
It would be nice if clicking on that status bar entry offered to stop the server or showed a picker with "Live Preview" commands.

Good idea! Probably should allow the user to stop the server by closing the status bar entry.

Works great, thank you!


Code39 barcodes

I have some Code39 barcodes (as seen on roadid race bibs (http://www.roadid.com/sponsorship/SampleBib.aspx)
Quagga will do a partial reading sometimes and return 345 as 34 or 45.  I thought about enforcing 3 digits for the read, but RoadID doesn't always include 3 digits (e.g, 50 not 050).
Any advice? (new to barcodes)  Looking to use this in github.com/mzimmerman/racergo

I've used barcodes for years. Unless I am mistaken, Code39 requires a stop and start character of "*" so the reader shouldn't accept a reading if it doesn't see 345 or 50 ... so, that sounds to me like a bug in quagga.

@mzimmerman thanks for reporting back to me. I'm kinda short of real Code39 barcodes, that's why I'm forced to use generated codes which might not be an optimal solution. Do you have any sample images for me that I could use?
@madmanpierre do you need help setting up quagga?

Here are some real codes that I've been testing with.  I believe code39 are supposed to start/end with * which seems to be the case here.  I'm using quagga with getUserMedia and the onDetected API call.

Using the file input site these all detect properly.  I guess you need/want an example that fails?  I'll have to see how to do that; hopefully better than guess and check!

@mzimmerman Thanks for the images. I'll simply print them and use my camera to detect the issues. Stay tuned!

@serratus I am managing about 20 developers around the world along with support and sales staff. Getting quagga going in our main product is 'my' development project - as I have time :) I started on Thursday. The Typescript d.ts is tentatively done, and I'm now working on integrating it. Then I'll be having myself and one or two of my developers testing. If I have questions I'll ask. Thanks!

Thank you for pointing out the issues with Code 39 barcode reading. I've partially fixed the problem where only parts of the code are being returned. In addition, the result is only considered successful if there is content available.
Can you please give it another try and report back to me?

Initial testing shows perfect results and also seemingly must faster at detection!  I've only tested it a little bit, but it seems great!  Thank you so much!

Using version 0.8.0, I'm getting "truncated" results again.  212 rendering as 21 or 12.  Usually it's 212 however.  Using the code_39_reader with Live/LiveStream @ 1280x720 on chromium.
I can reproduce it with http://serratus.github.io/quaggaJS/examples/live_w_locator.html but when I save the images that the live locator said were "12" or "21" and input it to http://serratus.github.io/quaggaJS/examples/file_input.html 212 it always gets the correct result.
Any ideas?

I feel like the decode() function should be changed slightly.
E.g., only when the decoded characters found start and end with * -- this way, you can never read a partial.
When I read the code though, it looks as if https://github.com/serratus/quaggaJS/blob/master/src/code_39_reader.js#L79 never lets the function return a result unless an asterisk was found, but in practice I'm not seeing that.  I also can't find where or how the leading asterisk is thrown away.
I tried to modify the decode() function to only return true if result starts and ends with an asterisk, but the decode function never saw the leading asterisk.  I guess _findStart() throws it away?
https://github.com/serratus/quaggaJS/blob/master/src/code_39_reader.js#L187

Thanks again for reporting the issue with Code 39 decoding, and the example image. I was able to reproduce the error and tracked down the bug. The fix is now available in the newest version (0.8.1). Please give it another try and close the issue if it is resolved for you.

Yes, looking a lot better, no partials (12 or 21), but I'm still receiving results that aren't 212.  What I am getting are symbols and letters - e.g., 2%.  It usually does not trigger that way and instead returns the proper code of 212, but I can still reproduce it fairly easily.  Maybe with the resolutions of the images I'm using this is to be expected?  Again, not a barcode expert, there is supposed to be a check bit type piece of data with code39 too - does 2% pass that check bit?

Unfortunately, there is no check digit on code39 unless ‘you’ build it in. Code39 has some ‘character by character’ protection that should make it ‘hard’ to get a bad character – if ONE of the bars or spaces is misread in a character – then it should fail. But if more than one are misread*, it is then possible to get a misread.
There are two patterns that characters can follow in bar39.
The 1st 39 consist of 2 wide bars and 1 wide space (all the rest of the bars and spaces MUST be ‘narrow’) (a-z and 1-9 are in this set of 39 along with 3 symbols and * - * is normally reserved as the start/stop characters.)
The 2nd 4 consist of no wide bars and 3 wide spaces. (% is in this second set of 4)

Because only these 2 patterns are allowed, if there are two misreads SIDE BY SIDE should be IMPOSSIBLE to be misread – it should be thrown as a no-read. Since this would mean that a space AND a bar were misread – and the two patterns cannot be created by changing just 1 bar and 1 space. It would require either 2 bars be misread (and all spaces CORRECTLY read) or 2 spaces misread (and all bars CORRECTLY read) – or it requires MORE than 2 mistakes that ‘happen’ to end up as one of the 2 patterns – a very unlikely situation.

So if a check is done to make sure it meets one of those patterns only – it should have an extremely low bad-read rate. Since you are saying you are getting the % character as a bad read – that means there were AT LEAST 4 Bars incorrectly read. To my mind this means you should be getting dozens or hundreds of no-reads for each failed read.
If you ARE getting dozens of no-reads for each failed read then it would seem to me that your hypothesis of resolution is a reasonable guess. If you are NOT getting dozens of no-reads for each failed read, then it would seem to me more likely that it is a failure in the quagga algorithm. It has been several months since I have run Quagga with the debugging options so I don’t remember the specifics – but can I suggest you figure it out (it wasn’t hard) and report back?
Adding a check digit: There is no ‘official’ way to do it, But there is one common checksum practice. The rule of 43 (sum up the data characters, then divide by 43 and put the result as the last character just before the terminal * character.) If you have control of both the production of the codes and the reading of them– then you can use the rule of 43.
It has been several months since my company has tested quaggaJS (we use it in our product but currently have a very small number of people using it and their use is ‘light’) we are coming up to another test cycle and I can join you in testing, because I have more that I expect will want to use 39. I’ll make sure I update to the most recent Quagga before we start our testing cycle.
peter
From: Matthew Zimmerman<EMAIL_ADDRESS>Sent: November 16, 2015 6:15 AM
To: serratus/quaggaJS<EMAIL_ADDRESS>Cc: peter horwood aka Madman Pierre<EMAIL_ADDRESS>Subject: Re: [quaggaJS] Code39 barcodes (#41)
Yes, looking a lot better, no partials (12 or 21), but I'm still receiving results that aren't 212. What I am getting are symbols and letters - e.g., 2%. It usually does not trigger that way and instead returns the proper code of 212, but I can still reproduce it fairly easily. Maybe with the resolutions of the images I'm using this is to be expected? Again, not a barcode expert, there is supposed to be a check bit type piece of data with code39 too - does 2% pass that check bit?
—
Reply to this email directly or view it on GitHub https://github.com/serratus/quaggaJS/issues/41#issuecomment-157024655 .  https://github.com/notifications/beacon/AC7G01oNN640wA5J2cIF0Npx7GYhbf4Aks5pGc5TgaJpZM4E6Lg-.gif


Issues in chapter 2, in (Remote counting)

I´m following the supervised ML case studies course. I´m trying to run the following codes:
stackoverflow %>%
count(Remote)
#and
simple_glm <- stackoverflow %>%
select(-Respondent) %>%
glm(Remote ~ .,
family = "binomial",
data = .)
I´m getting this message "Error: Column Remote is unknown"
As long as i´m a very newbie R-user, this issues could be a very basic one.
Thanks,
Federico

I could solve it by using the csv given in the data file of this repository.
stackoverflow <- read_csv("https://github.com/juliasilge/supervised-ML-case-studies-course/raw/master/data/stackoverflow.csv")


Clarify why /_matrix/federation/v1/event/ returns an array

Apparently GET /_matrix/federation/v1/event/{eventId} "Retrieves a single event".
The response contains an array pdus which "Must not include more than 50 PDUs".
May it ever include more than one PDU?
What if the same eventId is used in multiple rooms?

I'm pretty sure the answer is "it always returns one and event IDs duplicated between rooms are undefined behavior": in that case the field description text in the response text should probably be changed to something like "List containing a single persistent update to a room. Note that events have a different format depending on the room version - check the room version specification for precise event formats.".

It returns a Transaction object, which awkwardly has a schema written for the /transaction endpoint. I believe we have words somewhere to say it "must only have 1 event", however this may have been lost in translation.


Set a "Starting point" savestate / Start shuffling from a savestate instead of boot

Is your feature request related to a problem? Please describe.
For a lot of games there can be a lengthy intro logo, intro scene, intro stage, intro story, unskippable cutscene, etc. before the actual games start which can make the beginning quite annoying to wait through, specially if it's many games or there are many in-game settings or when one game already got to the action while the others are still in the intro or dead time in general, this is more apparent with the damage shuffler plugin
Describe the solution you'd like
I would like to suggest a feature where the shuffler loads a savestate for each game as a starting point after starting a new session.
For example every game would start at the main menu or the beginning of the first stage (instead of starting from boot)
As for the savestates themselves, the user would have to save them manually (Or download them) beforehand and then drop them in a "start savestates" folder for the shuffler to find.
To further describe how i would use it.
Let's say i want to play megaman X1 to X6 in the shuffler, but X4 to X6 take a while to start.
So,  before starting the shuffler, i open each game and get to the intro stage then save a savestate
Then after getting the 6 savestates (1 per game) i drop them in an special folder that the shuffler will use.
Then i open the shuffler and activate and option that says something like: "Start new session from starting point savestates"
Then after i click start new session the game starts from the intro stage and when it shuffles the next game also starts at the intro stage  (or any savestate i saved).
I think it would save a lot of time and help to get straight to the action, specially if it's a game you play often, and i think it would be ideal for races aswell.
Describe alternatives you've considered
An alternative would be an option to not start shuffling until you press a custom Hotkey (Start shuffling)
So you can "set up" each game until you're ready to play them or manually load previously made savestates
But for this you would also need another hotkey to force a shuffle so you can set each game up.
Once you get all the games set and ready to the desired points of the game you press the "Start Shuffling" hotkey to begin playing.

+1, would love to see this supported.
At the moment an easy enough workaround is removing the lines of the shuffler.lua script that delete savestates at the beginning of a new session, but would love to see this properly supported by the shuffler.

This feature has been added by c9698f6a32e7ba0f67a6987478f9985d89154ddb. You will need to make a folder called start-states/ in your shuffler directory, and when you start a new session, it will use any states in that folder. I need to add documentation for this addition.


Feature Request: TypeScript migration

Is your feature request related to a problem? Please describe.
Continuation of Issue #12 , which covered the set-up for TypeScript migration. This new issue is created for the migration of React components from JSX to TSX.
Describe the solution you'd like
All React components to be written in TSX.
Describe alternatives you've considered
NIL
Additional context
This is Part 2 of 2, which involves the migration of React components to use TSX from current implementation using JSX.
Possible Implementation
NIL.
Benefits
Reduce bugs that make it to production, improve code quality, expand IDE support, and enhance developer productivity.
Risks
NIL

Migration of all React components complete.


chore(docs): add buf.gen.yaml v2 schema example

This took me a bit to figure out the right invocation, so I figured it'd be useful to others as well.

 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.


blue

 it says h2 element needs to be blue not sure if my code is correct. tried help chat but no luck.


Adding the GitHub Actions file for prombench.

This commit adds the GitHub Actions file to trigger the benchmarking process for GMP Collector (using the prombench tool).

I can only rebase & merge

Probably by design? @TheSpiritXIII

Let's rebase this PR to one commit (I don't think we want two, where second is a small fix) or we enable squash merge and merge 🤔

Cancelled lint as it passed before and we just squashed. Plus lint does not lint yaml file we are just adding.


Set .net compilation output stream to utf8

Set the .net compilation output stream to utf8 to prevent garbled characters in other languages.
Squashed version of #73861 by @dream-young-soul.

Should fix https://github.com/godotengine/godot/issues/71326
Should fix https://github.com/godotengine/godot/issues/64276 (3.x, once backported)

(Presumably) Fixes https://github.com/godotengine/godot/issues/71326 and https://github.com/godotengine/godot/issues/64276 (tho that is milestone 3.6)
Upstream fix: https://github.com/dotnet/sdk/pull/29755, but I am not sure how this interacts with this / how or if the encoding of stdin/stdout is propagated on windows; also that fix is in the .NET 8 previews and a backport candidate for 7.0.300.
Didn't / can't test this, on my system other languages work just fine with master (at least it looks ok and google correctly translates the output).
cc: @dream-young-soul

CC @bruvzg @timothyqiu

Also, I'm not sure if it will always work with this part of code:

These use cases are in the C# land, using System.Diagnostics.Process to launch and interact with a new process. So OS::execute() is not relevant.

After way too much googling, diving into framework sources and some experiments:

I don't think this can break things on non-windows platforms because there the default encoding already is UTF8 (tho without BOM)
After the upstream fix this is required on Windows 10+ to ensure that we read the same encoding as dotnet
Without that this PR can break the encoding in different ways compared to before:

if the system uses 65001 (utf8) as the default code page everything will continue working correctly with all languages
if the system used another code page, that couldn't display all required characters, things will now be broken in a different way
if the system used another code page, that could display all required chars, but used the chars 128-255 to do so, things will now be broken but worked before
if godot used a non-65001 cp and dotnet used 65001, (not sure how this can happen) this PR fixes the problems

To correctly fix all issues before the upstream patch we would need to force the dotnet process to use the utf8 cp in all cases

but it is not possible to change the code page of a different process without hooking into it and executing code there OR sharing a console with that process, but that would mean changing the code page of the godot process, which will probably code other issues somewhere.
we could probably create a intermediate process that creates a new console changes it to utf8 and then runs dotnet
it looks like creating the dotnet process with the DETACHED_PROCESS flag, which look to cause to process to use cp 0, which on .net core also maps to utf8, BUT you can't pass it when using the Process.Start api.

TL/DR:  It's complicated, but it looks like it goes into the right direction, i'll have a look how much of a pain passing DETACHED_PROCESS actually is.

TL/DR: It's complicated, but it looks like it goes into the right direction, i'll have a look how much of a pain passing DETACHED_PROCESS actually is.

As expected an enormous pain since you need to re-implement IO redirection, so it's probably not worth it.

This PRs should also set the stderr encoding:

diff --git a/modules/mono/editor/GodotTools/GodotTools/Build/BuildSystem.cs b/modules/mono/editor/GodotTools/GodotTools/Build/BuildSystem.cs
index d550c36b82..c9b686413c 100644
--- a/modules/mono/editor/GodotTools/GodotTools/Build/BuildSystem.cs
+++ b/modules/mono/editor/GodotTools/GodotTools/Build/BuildSystem.cs
@@ -38,6 +38,8 @@ namespace GodotTools.Build
             startInfo.RedirectStandardError = true;
             startInfo.UseShellExecute = false;
             startInfo.CreateNoWindow = true;
+            startInfo.StandardOutputEncoding = Encoding.UTF8;
+            startInfo.StandardErrorEncoding = Encoding.UTF8;
             startInfo.EnvironmentVariables["DOTNET_CLI_UI_LANGUAGE"]
                 = ((string)editorSettings.GetSetting("interface/editor/editor_language")).Replace('_', '-');

@@ -102,6 +104,8 @@ namespace GodotTools.Build
             startInfo.RedirectStandardOutput = true;
             startInfo.RedirectStandardError = true;
             startInfo.UseShellExecute = false;
+            startInfo.StandardOutputEncoding = Encoding.UTF8;
+            startInfo.StandardErrorEncoding = Encoding.UTF8;
             startInfo.EnvironmentVariables["DOTNET_CLI_UI_LANGUAGE"]
                 = ((string)editorSettings.GetSetting("interface/editor/editor_language")).Replace('_', '-');

diff --git a/modules/mono/editor/GodotTools/GodotTools/Build/DotNetFinder.cs b/modules/mono/editor/GodotTools/GodotTools/Build/DotNetFinder.cs
index b437c7e742..27b36d9ad1 100644
--- a/modules/mono/editor/GodotTools/GodotTools/Build/DotNetFinder.cs
+++ b/modules/mono/editor/GodotTools/GodotTools/Build/DotNetFinder.cs
@@ -4,6 +4,7 @@ using System.Diagnostics;
 using System.Diagnostics.CodeAnalysis;
 using System.IO;
 using System.Runtime.InteropServices;
+using System.Text;
 using JetBrains.Annotations;
 using OS = GodotTools.Utils.OS;

@@ -55,7 +56,9 @@ namespace GodotTools.Build
             process.StartInfo = new ProcessStartInfo(dotNetExe, "--list-sdks")
             {
                 UseShellExecute = false,
-                RedirectStandardOutput = true
+                RedirectStandardOutput = true,
+                StandardOutputEncoding = Encoding.UTF8,
+                StandardErrorEncoding = Encoding.UTF8,
             };

             process.StartInfo.EnvironmentVariables["DOTNET_CLI_UI_LANGUAGE"] = "en-US";

I Found a VM that uses CP 437 as the default, so I could actually test this and it turns out all that research and I am missing something, because in practice this PR just works somehow, for all combinations of SDK 7.0.102, 8.0.100-preview; German and Chinese; and console version and not.
So, idk, if this just work then or if there are some edge cases where there are issues / regressions with this.

I'm not really familiar with this to update it properly, I just PR'ed it to help @dream-young-soul with Git issues. I'd suggest you take this over in a new PR @RedworkDE if you're interested, as you did a lot of great research.


Add an additional maintainer for this repository

Issue:
Please add Joanna Sendorek (https://github.com/joannasendorek) as an additional maintainer of this repository.

Sorry for pointing you out CJ but that's the easiest and most reliable way to get attention. :D
Thanks in advance.

Why is this coming to me personally?
I am making this comment solely in my personal capacity and am not conveying any rights to any intellectual property of any third parties.

@CJ-Wright Sorry. It wasn't meant for you personally. I picked you from the owners by random.
Is there a channel of communication for such requests? Should I use gitter or the mailing list?

You yourself have write permissions to the repo, please read the documentation and make a pull request adding people to the recipe-maintainers.
Assigning this to a single person who is not party to this repo is an abuse of the github notification system. If you need help in the future ping one of the help teams or core.
I am making this comment solely in my personal capacity and am not conveying any rights to any intellectual property of any third parties.

Thanks and again sorry for notifying you. Will resolve this through recipe-maintainers.


Can't Import Gradle Project Without Sonatype Username and Password

Noticed this while setting up a new machine. The gradle import in IntelliJ fails if it can't find the sonatypeUsername and sonatypePassword.

The build.gradles now check if the sonatypeUsername and sonatypePassword exist before attempting to use them. This should fix the issue.


Use floating point division for benchmarking

Right now benchmarking recording input and outupt time in full seconds, resulting in weird numbers when the numbers are close or the same.
We can fix this by modifying the files something like
https://github.com/MFlowCode/MFC/blob/master/toolchain/templates/include/helpers.mako
replace date +%s with date +%s%n, which gives the time in nanoseconds (integer) (note this doesn't work on MacOS, but that's fine).
We also want to switch the elapsed output time to be in seconds not nanoseconds so:
https://github.com/MFlowCode/MFC/blob/e3c4a067e410c308e6c53c0eaa722bde0c8f44ba/toolchain/templates/include/helpers.mako#L89
should be
$(echo "($t_${target.name}_stop - $t_${target.name}_start)/1000000000" | bc -l)
I haven't tested this yet.

Update: Fixing this issue would surely fix the "divide by zero" error

Was closed by #423


Make GuardDuty finding publishing frequency configurable

By default this is 6 hours and this is too long to push alerts. This makes it configurable and sets the default frequency to every 15 minutes.
Signed-off-by: Stephen Hoekstra<EMAIL_ADDRESS>

No longer needed.


feature suggestion

hi ben i have been using dogehouse for 3hrs nice job bro but we really need some snippet sharing tool for sharing some links everybody was spelling urls to tell one another it will be really helpful bro

This is coming


[devops:bot] update deps in nix/sources.json (from: rhino-core@71aa9b7)

update nix refernces for rhino-core and|or nixpkgs to match https://github.com/rhinofi/rhino-core/blob/71aa9b771800a6975194d3ead4226e6209ca147c/nix/sources.json (branch: dev)

superseded by #221


Weird behavior when clicking on an input on iOS/iPhone

Hey,
First of all, thank you for this awesome drawer component! Really enjoying it so far. Sadly there is one thing that prevents me from using it inside my app:
I am experiencing a weird behavior when clicking on an input field inside the drawer component on my iOS device. The drawer itself is pushed down to the bottom and not visible anymore.
Here is a short demonstration. It uses the bare setup for a next.js app and only typescript, tailwindcss and vaul are installed. The styling of the drawer is similar to the Scrollable with inputs example:
https://github.com/emilkowalski/vaul/assets/58264696/5bb6305a-7757-4d15-8a4e-7b8a5a5d9d98
Here is the repository for it:
vaul-ios-bug-demo

Your demo as well as the example here works fine for me. I've had this happen to me before, restart your safari browser, that should help.

I got the same issue

Did you try the solution I provided above? @imclint21 If so, please provide a codesandbox with reproduction, your iOS version etc.

Your demo as well as the example here works fine for me. I've had this happen to me before, restart your safari browser, that should help.

Restarting the browser did indeed fix it.


feat: Add support to deploy Kepler using compose

This PR adds support for deploying Kepler on both metal and VM using Docker Compose,
ensuring local and CI environments align for easier testing and development.
Key Changes:

OS choices: Ubuntu for metal
Workflow update: create_equinix_runner.yml now accepts OS name as
input. Non-compose workflows continue using rhel9 for metal.
Inventory refactor: Moved host-specific vars to host_vars, shared vars to group_vars.
kvm_vm role:

Installs required packages based on host OS.
Moves cloud-init-script.sh to files and automates copying.
Sets vm_name, vm_user, ssh_key_path as facts for reuse.
Corrected invalid VM destroy state.
Moved static vars from defaults to vars.

New roles:

install_kepler: Installs Kepler with Docker Compose.
setup_docker: Installs Docker on metal and VM.
run_validator: Runs the validator on metal.

New playbook validator_playbook.yml:

VM creation, Docker installation, Kepler deployment, Validator execution.

Miscellaneous changes:

Removed inventory.ini
Updated equinix_metal_flow.yml, equinix_metal_e2e.yml and equinix_metal_e2e_isolated_servers.yml workflows

No existing playbooks have been modified.

Sample CI run: https://github.com/sustainable-computing-io/kepler-metal-ci/actions/runs/10843535387

@vprashar2929 please encapsulate the os dependent config and command? If the goal is to support compose, please create a dedicated workflow in addition to the current metal workflow. This will make sure the report results are consistent with the same configuration.


Display the event header

This PR adds the event header for all calendar invites.

Parse the event information and store it in the events column.
Display the event information as a header (Uses the existing events module).
Add a calendar icon in the thread list view for emails that contain invitations.

Improvements/Tests requested:

Suggest a better UI Icon to display a calendar invite in the list view.
Test the migration on other OSes.  If it doesn't work, can someone look into it?

Fixes #132 (Point no. 2)

@nirmit any chance we could get some screenshots of what this looks like please?

Sure.
The Email Header for Invites

The Thread List View (notice the icon for calendar invites)

What's wrong with the icon in the list view? That looks nice to me

We can merge this in and let people play around with it in Master.


Custom inlineEdit

Hi @hjalmers
I would like to know if the component that is used in the editing of the cell can be customized in some way, for example, add a directive or make its size the width of the column.
I have the following table and I would like that the user could only enter numbers in the editable field (directive) and that if you click anywhere in the cell you can edit the content and not have to go to where the text is

@mayraGL if you're talking about the inline editing component you can read more about how to configure it here, currently it's pretty basic but you could set the type to number to only allow numbers to be entered. It also uses full width and the input borders are hidden too but you could customize the appearance with pure css (it's basically just an input field in a table cell) if you like.
The other option would be to use a custom component like in this example and then you can do pretty much what ever you want:)


Invoke-CCLoadAccounts is not working : unable to parse data from server

Anytime I tried to use Invoke-CCLoadAccounts to load account from CSV file into a delimited file source it fails.
The errors is always the same : unable to parse the data sent.
The issue is that the file content is included into the body as a single line and there is no way to explain what's the delimiter between every line from the CSV.
So the data take the header + following line and try to interpret the last column name + the first value on second line and this fails
Using cc/api/source/loadAccounts from curl command line is working fine with the same file (or even using jar file for fileuploadutility).
Can you fix the issue to allow uploading csv file for account ?
Can you also add method to do the same for entitlement (using cc/api/source/loadEntitlements as except the url being different it's exactly the same process)

Hello @patrice-adp!
The Invoke-CCLoadAccounts cmdlet is fixed. We had to update the method we used when working with multipart form requests with files, see https://github.com/sailpoint-oss/powershell-sdk/commit/05455ac8542f1ab8d9bcebe521cfeb4560a4b5eb. I've also added the new cmdlet Invoke-CCLoadEntitlements with this latest commit https://github.com/sailpoint-oss/powershell-sdk/commit/61c7b493c46e149991ed748c462f6d4abe0353fc.
A release with all of these updates will be coming shortly!


Flutter's CDN seems to be facing issues; I couldn't switch channels or run --doctor or do a fresh install.

Steps to reproduce

Run the flutter channel <channel name> command.
(or the flutter --doctor command)
(or try downloading the flutter zip from the website)

Actual results
Any flutter command will start downloading artefacts from flutter's CDNs.
The download speed will be extremely slow (around 10 kbps).
It times out after waiting for a long time.
Similar thing with zip download.
Is there any way i can download flutter other than the default cdn?
Logs

Logs

~ % flutter --doctor

Downloading Darwin x64 Dart SDK from Flutter engine e76c956498841e1ab458577d3892003e553e4f3c...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0  214M    0  408k    0     0  37658      0  1:39:19  0:00:11  1:39:08 33096 2  2  214M    2 6529k    0     0  72620      0  0:51:30  0:01:32  0:49:58 97978

curl: (56) Recv failure: Operation timed out

/Users/<user>/dev/flutter/bin/internal/update_dart_sdk.sh: line 157: return: can only `return' from a function or sourced script
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:18 --:--:--     0
curl: (56) Recv failure: Operation timed out

Failed to retrieve the Dart SDK from: https://storage.googleapis.com/flutter_infra_release/flutter/e76c956498841e1ab458577d3892003e553e4f3c/dart-sdk-darwin-x64.zip

If you're located in China, please see this page:
  https://flutter.dev/community/china

Flutter Doctor output

Doctor output

wasn't able to get flutter doctor output as the prerequisite command doesn't run

return: can only `return' from a function or sourced script

This is probably similar to https://github.com/flutter/flutter/issues/119193
You also need to check your PATH variable in .zshrc file and see if it is pointing to correct installation.

@darshankawar I remember the path set in .zshrc file to be correct.
Also I think that error is not relevant as the root cause was that the connection to server (for downloading dart sdk) timed out.
I tried removing flutter completely and reinstalling, but that was also not possible because the download timed out.
However, the servers came back to normal the next day, so I was able to download and setup flutter.


rust-cbindgen: 0.13.1 -> 0.13.2

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eqrion/cbindgen/releases.
meta.description for rust-cbindgen is: "A project for generating C bindings from Rust code"
meta.homepage for rust-cbindgen is: "https://github.com/eqrion/cbindgen"
Updates performed:

Rust version update
Quoted meta.homepage for RFC 45

Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.13.2 with grep in /nix/store/q321xa7nd39jsgkpszpqlwdid6v56z45-rust-cbindgen-0.13.2

directory tree listing: https://gist.github.com/ed163e8a2abfd195cda4d878767731c8

du listing: https://gist.github.com/6d471dae1562cb8d3c5111bb853a1c45

Rebuild report (if merged into master) (click to expand)

36 total rebuild path(s)
10 package rebuild(s)
10 x86_64-linux rebuild(s)
10 i686-linux rebuild(s)
6 x86_64-darwin rebuild(s)
10 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
adoptopenjdk-icedtea-web
firefox-esr-68-unwrapped
firefox-unwrapped
firefoxPackages.firefox
firefoxPackages.firefox-esr-68
mozplugger
rust-cbindgen
slimerjs
thunderbird
xulrunner

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q321xa7nd39jsgkpszpqlwdid6v56z45-rust-cbindgen-0.13.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rust-cbindgen https://github.com/r-ryantm/nixpkgs/archive/76458f89f47b1b8b2db1e6272f56d3919ce682d0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q321xa7nd39jsgkpszpqlwdid6v56z45-rust-cbindgen-0.13.2
ls -la /nix/store/q321xa7nd39jsgkpszpqlwdid6v56z45-rust-cbindgen-0.13.2/bin

cc @jtojnar @andir for testing.

On 11:00 24.03.20, Jon wrote:

[5 built (2 failed), 43 copied (2027.9 MiB), 1152.9 MiB DL]
error: build of '/nix/store/8p4299inv57nma311vyw4b9jf8jy8pxa-env.drv' failed
https://github.com/NixOS/nixpkgs/pull/83247
5 package failed to build:
adoptopenjdk-icedtea-web firefox-esr-68-unwrapped xulrunner mozplugger slimerjs

2 package built:
rust-cbindgen thunderbird

That firefox package actually compiled for me. Do you have a build log?
Maybe you did run out of space in the temporary build dir?
Also I managed to build all these 5 that failed for you:

/nix/store/lvk8g3488pamv7zmfd0d00hmncrwx9vy-adoptopenjdk-icedtea-web-1.8.3
/nix/store/ad3v1cjhbxdwzncak8g62z4cy2glm7m2-firefox-esr-unwrapped-68.6.0esr
/nix/store/n5bncnlq8m7qf5j6r9a7064k2fkxd89c-firefox-unwrapped-74.0
/nix/store/pim6v44qr10y0xvcadf7ygxbxhpw4ppw-mozplugger-2.1.6
/nix/store/88japdinxfqasm06p7358xjk43g32sjb-slimerjs-1.0.0

(xulrunner builds firefox 74)

As one data point, the last time we updated rust-cbindgen nixpkgs-review failed, but it succeeded if you just ran nix-build on all the packages:
https://github.com/NixOS/nixpkgs/pull/80243#issuecomment-599272720
My suspicion is that the combination of the simultaneous firefox latest + firefox ESR rebuilds is causing your nixpkgs-review failure @jonringer, and if you just build them individually prior to running review you'll be OK.

@GrahamcOfBorg build firefox-esr-68-unwrapped

I discovered firefox build failures both in master and while building https://github.com/NixOS/nixpkgs/pull/84211, so I'm fairly confident this is a regression introduced by the bump of rust-cbindgen:

free(): invalid pointer
In file included from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Latin1.h:17,
                 from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/TextUtils.h:13,
                 from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Utf8.h:19,
                 from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/RecordReplay.h:16,
                 from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Atomics.h:22,
                 from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/nsISupportsImpl.h:24,
                 from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/nsISupportsUtils.h:14,
                 from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/nsISupports.h:79,
                 from /build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/nsIEventTarget.h:10,
                 from /build/firefox-74.0.1/xpcom/base/MemoryTelemetry.h:12,
                 from /build/firefox-74.0.1/xpcom/base/MemoryTelemetry.cpp:7,
                 from Unified_cpp_xpcom_base1.cpp:2:
/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Tuple.h: In instantiation of 'struct mozilla::detail::TupleImpl<5, long unsigned int, long unsigned int, long unsigned int, long unsigned int, bool, bool, mozilla::dom::UserActivation::State, bool, RefPtr<mozilla::dom::FeaturePolicy>, unsigned int, nsID, bool, bool, bool, mozilla::dom::GVAutoplayRequestStatus, mozilla::dom::GVAutoplayRequestStatus, float, mozilla::dom::OrientationType>':
/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Tuple.h:114:8:   recursively required from 'struct mozilla::detail::TupleImpl<1, bool, bool, nsILoadInfo::CrossOriginEmbedderPolicy, nsILoadInfo::CrossOriginOpenerPolicy, long unsigned int, long unsigned int, long unsigned int, long unsigned int, bool, bool, mozilla::dom::UserActivation::State, bool, RefPtr<mozilla::dom::FeaturePolicy>, unsigned int, nsID, bool, bool, bool, mozilla::dom::GVAutoplayRequestSta>
/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Tuple.h:114:8:   required from 'struct mozilla::detail::TupleImpl<0, nsTString<char16_t>, bool, bool, nsILoadInfo::CrossOriginEmbedderPolicy, nsILoadInfo::CrossOriginOpenerPolicy, long unsigned int, long unsigned int, long unsigned int, long unsigned int, bool, bool, mozilla::dom::UserActivation::State, bool, RefPtr<mozilla::dom::FeaturePolicy>, unsigned int, nsID, bool, bool, bool, mozilla::dom::GVAutoplayR>
/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Tuple.h:224:7:   required from 'class mozilla::Tuple<nsTString<char16_t>, bool, bool, nsILoadInfo::CrossOriginEmbedderPolicy, nsILoadInfo::CrossOriginOpenerPolicy, long unsigned int, long unsigned int, long unsigned int, long unsigned int, bool, bool, mozilla::dom::UserActivation::State, bool, RefPtr<mozilla::dom::FeaturePolicy>, unsigned int, nsID, bool, bool, bool, mozilla::dom::GVAutoplayRequestStatus, mo>
/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/dom/SyncedContext.h:162:14:   required from 'struct mozilla::dom::syncedcontext::FieldStorage<void, nsTString<char16_t>, bool, bool, nsILoadInfo::CrossOriginEmbedderPolicy, nsILoadInfo::CrossOriginOpenerPolicy, long unsigned int, long unsigned int, long unsigned int, long unsigned int, bool, bool, mozilla::dom::UserActivation::State, bool, RefPtr<mozilla::dom::FeaturePolicy>, unsigned int, nsID, bool, bool, >
/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/dom/BrowsingContext.h:128:3:   required from here
/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Tuple.h:114:8: internal compiler error: Aborted
  114 | struct TupleImpl<Index, HeadT, TailT...>
      |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
make[3]: *** [/build/firefox-74.0.1/config/rules.mk:729: Unified_cpp_xpcom_base1.o] Error 1
make[3]: Leaving directory '/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/xpcom/base'
make[2]: *** [/build/firefox-74.0.1/config/recurse.mk:74: xpcom/base/target-objects] Error 2
make[3]: Leaving directory '/build/firefox-74.0.1/obj-x86_64-pc-linux-gnu/netwerk/cache2'

I pushed a revert in 09dde57e93d.

Strange, both @andir and I managed to build  /nix/store/n5bncnlq8m7qf5j6r9a7064k2fkxd89c-firefox-unwrapped-74.0 in this PR.  I'll try again and see, but in the meantime a revert seems sensible.

I just built firefox on the last commit of master prior to the revert:
$ git checkout 09dde57e93d010b786eed4796d53f34a6c6e3891^
$ nix-build -A firefox
/nix/store/4ipn59ydqk1xwy1l9adwkb0icz1ndhlb-firefox-74.0

I suspect that the build is just huge and vulnerable to the build host running out of memory and the OS killing something, resulting in the appearance of failure.

Having built my own patched Firefox for ages, I see this sort of build failure all the time. A good signal it’s a memory issue is to build with fewer cores (--option cores). If it works with fewer cores, it was probably a memory issue. (With other packages, this would be more a sign of parallelism bugs, but with Firefox, it’s usually memory. We can be somewhat confident of that by using a smaller but still large number of cores. For example, I usually get a build failure with 48 cores, but it’s always fine with 24.)

On 03:55 04.04.20, Alyssa Ross wrote:

Having built my own patched Firefox for ages, I see this sort of build
failure all the time. A good signal it’s a memory issue is to build
with fewer cores (--option cores). If it works with fewer cores, it
was probably a memory issue. (With other packages, this would be more
a sign of parallelism bugs, but with Firefox, it’s usually memory. We
can be somewhat confident of that by using a smaller but still large
number of cores. For example, I usually get a build failure with 48
cores, but it’s always fine with 24.)

For a long time that was an issue due to how the build system did
produces outputs. THese days it is likely just the amount of scratch
space and RAM that has to be available during the compilation. On a
system with 16GB RAM you can't build Firefox on tmpfs (at least not
straight forward/with the defaults).

In doing some further experimentation, I found that, even when
constrained to a single core, the rustc proccess for the gkrust crate
(which is where I've noticed Firefox usually fails) peaks at 6.5G
resident.
6.5G!  For a single compiler invocation!

I ran the build on a AMD EPYC 7401P with 128GB, restricted to 1 core. /tmp is not on tmpfs. I can't really believe this is purely high memory usage.

I ran the build on a AMD EPYC 7401P with 128GB, restricted to 1
core. /tmp is not on tmpfs. I can't really believe this is purely
high memory usage.

Yeah I agree now.  I thought to look in dmesg and didn't see the OOM
killer get involved.  Are you also getting it on master?  I am.

You're right - I can reproduce the build failure on master…
This probably means the revert of rust-cbindgen didn't fix it, and it has already been flaky before that (just eventually somehow succeeded somewhere and was in the binary cache).
I quickly checked, it failed on hydra due to receiving a SIGKILL. I propose reverting the revert for now, and tracking this separately.

Reverted the revert in 1eae7fb887413d9cc50b292eade8b9c9a03c73bd, let's move the discussion over to https://github.com/NixOS/nixpkgs/issues/84283.


cvdupdate support on pypi

good day all,
is the cvdupdate still supported on pypi? last push was back in 2022. https://pypi.org/project/cvdupdate/1.1.1/
from my understanding the freshclam command does the same thing but just curious.

We haven't had a release since 2022.  We've made a couple minor improvements since then. It couldn't hurt to publish a 1.1.2 patch version.

Regarding freshclam vs cvdupdate -- freshclam is intended to keep a specific clamav installation up to date.  cvdupdate is intended to keep a database mirror  up to date - which requires more files.
If you already have a recent database (newer than 90 days), freshclam will update from that using one or more .cdiff patch files.  This downloads the minimum data required for the update.
cvdupdate, on the other hand, will download each .cdiff file since your current .cvd up to the latest .cvd plus the latest whole .cvd file.  So that's at least 2 file downloads and the .cvd file download which for daily.cvd is about 62MB right now.

ahh, so cvdupdate is probably the way to go but i can see the downsides. i wouldnt say no to a 1.1.2 but if 1.1.1 works as expected then thats good with us. thank you for the info and the quick response.


Longclaw with latest Wagtail and Django 3?

ISSUE_TEMPLATE

longclaw?
Wagtail?
Django3
Python3

Description
Can Longclaw be used with latest Wagtail and Django?

Duplicate of #410


Each Shadow Rift ingress is an adventure area

This attempts to make each of the 13 places you can enter a Shadow Rift a distinct adventure area.
The first time you adventure there, it goes to place.php, which redirects to adventure.php, which redirects to fight.php.
Subsequent times through the same rift, it goes straight to adventure.php which redirects to fight.php.
Automate 1 Shadow Rift (Forest Village)
Automate 1 Shadow Rift (Somewhere Over the Beanstalk)
Automate 1 Shadow Rift (Somewhere Over the Beanstalk)
Automate 2 Shadow Rift (The Castle in the Clouds in the Sky)
[742] Shadow Rift (Forest Village)
Encounter: shadow spider
...
[743] Shadow Rift (Somewhere Over the Beanstalk)
Encounter: shadow stalk
...
[744] Shadow Rift (Somewhere Over the Beanstalk)
Encounter: shadow orb
...
[745] Shadow Rift (The Castle in the Clouds in the Sky)
Encounter: shadow guy
...
[746] Shadow Rift (The Castle in the Clouds in the Sky)
Encounter: shadow bat

This successfully sets "shadowRiftIngress" each time it goes to a new place, since PlaceRequest.registerRequest is not called to do that in this case, since was automation.
This will allow canAdventure() and prepareForAdventure() to do the right thing for the individual areas.
I'll do that later. I think this is ready for review now.

I'm merging without additional review since my last commit was simply expanding the tests.


State to msas mapping

Closes #64

It certainly doesn't hurt to have the msaToNames now and it will get the rest of the code closer to the form that will ingest that endpoint. I vote we keep that file until the endpoint is available and we can switch over.


Priming work_dir

When using plrust for the first time, it takes ages to compile the first function, which is not an ideal user experience.
It does, however, help to create a function once before using the extension to prime it. Here's an example of how priming can be done.
This can apply to .deb building, .deb post-install, or other extensions' lifecycle points. Also, the upgrade story should be considered as well.

yeah, we'll take a look at this, probably next week, with an aim to get such a thing included in our .debs for the next release.  Thanks!

We've spent quite a bit of time discussing this internally and the consensus here is that it'll likely be too error-prone for PL/Rust's .deb (and future other package types) packaging to include something that builds an initial function to "prime" the target/ directory.
Our goal, such as we can accomplish it, is to continue to improve overall compilation speed.  We've got a number of ideas around this that we haven't yet explored.


Modpack Version
0.0.35
Describe your issue
尝试将无耐久的psi小刀放到砧板上会提示没有魔源支持，在把小刀取下来前无法与大部分方块正常交互
Have you modified the modpack?
No
User Modifications
No response
Did the issue happen in singleplayer or on a server?
Singleplayer

Okay, fixed in v0.0.4


Dashboard - Cannot read properties of null (reading 'awsName')

Describe the bug
This bug is on the local development with nhost cli - then on http://localhost:3030/ I see error (screenshot below). This error is on the another pages. GraphQL, Auth and storage dont work too.
To Reproduce
Steps to reproduce the behavior:

nhost up
Open http://localhost:3030/
On main screen see error "awsName"

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop:

OS: Windows + WSL2
Browser Chrome
Version Nhost CLI v0.8.12 for linux-amd64

Is the Hasura Console working OK?

Hasura Console seems to work fine.

seems or is?
And you did nothing more than nhost up?

I have the same issue on a pretty new CLI
> Nhost CLI v0.8.12 for darwin-arm64
> You have the latest version. Hurray!

It's a fresh project; I did nothing except upgrading CLI  to fix this issue
Error response from daemon: manifest for hasura/graphql-engine:v2.15.1 not found: manifest unknown: manifest unknown

and I run this command
nhost -d dev --no-browser --smtp-port 10255

It seems the Hashura dashboard works but not the Nhost dashboard.

Hasura Console works.

seems or is?
And you did nothing more than nhost up?

I run only nhost up.

Ok, I can reproduce this. Thanks. Will fix ASAP.

It will be fixed in 0.7.10 as soon as https://github.com/nhost/nhost/pull/1375 gets merged. I'll reopen in the meantime.

Hello,
awsName and reading 'region' problem is solved.
But pages Graphql, Auth and Storage has problem with error:

It is looks like some CORS problem.

Do you see the same when you run the front-end at port 3000 (i.e. `http://localhost:3000` )? :thinking:

Hello, all works fine now. Thanks.

thank you @szilarddoro !


[SDK-2162] Updated Branch SDK and moved fully to SPM

Updated the Branch SDK from 1.45.2 to 3.0.0
Updated the minimum deployment from iOS 9 to iOS 12
Moved fully from Cocoapods to SPM since Cocoapods was only being used for the FBSDK
Updated app version number to 2.0.0
Fixed the old, broken Branch Key
Removed deprecated Branch methods
Updated BranchEvent calls

Any chance this will get merged any time soon? We're just starting on an exploration of Branch's capabilities, but I'd rather deal with SPM than CocoaPods and the new 3.0.0 version of the Branch SDK if possible. Is it at least fair to start with this branch instead of master?


[usecase] Update manifest for WebAppTaskManager

MEMO PAD8:
Impacted TCs num(approved): New 0, Update 1, Delete 0
Unit test Platform: Crosswalk Project for Android 18.46.465.0
Unit test result summary: Pass 1, Fail 0, Blocked 0
https://crosswalk-project.org/jira/browse/XWALK-5747

LGTM


Format example terraform file

terraform fmt

 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.


Merge 3.0.0 changes into master

The time has come! This PR merges all of our early development work on 3.0.0 into the master branch, where we can continue to work on it as we prepare for the release.
Fixes #423, #428, #450, #452, #453, #466, #476, #479, #505, #512, #552, #320, #319, #310, #380, #398, #397, #403, and #416.

Approved
Amazing work, all!

Approved
We finally made it.

WHOA... that's an epic list of commits & issues fixed. Congrats guys. You planning a post / writeup somewhere that explains what the big v2.x => v3.x changes are? We are close to a v1 release for ngOfficeUIFabric and want to work against the latest version of you guys so the timing is good. A writeup will help others (see: us) in taking a closer look on what we should keep an eye out for.

@andrewconnell - yes! we will be working on a big 'ol blog post that helps call out the changes and how some of the new work can be used. Definitely look forward to this in the near future!

@andrewconnell: We're also planning to release Fabric 3.0 as a beta, and to provide a more detailed road map of the remaining items that we want to get in before it releases.


switch to Illuminate\Http\Request in CrudController

current solution for #1119

Well... StyleCI "destroyed" the intended order of use statements... 🤔

I don’t think so.
The backpack generated files can stay like they are I think

Thank you @OliverZiegler ! Finally been able to extensively test and merge this. Imho it's a non-breaking change so it'll be available in a patch update later today.
Cheers! Thanks a lot.

Also changed the generators to extend the default FormRequest, not CrudRequest, so we can deprecate CrudRequest in the future - https://github.com/Laravel-Backpack/Generators/commit/949e3fc7000392b421f4a71f9a9030212da0795a#diff-918597f9a671132c2ebcee64c0b50c97


unclear error message when deploying peertube with custom domain

Description
env used : mainnet
version : 2.2.0
tried to deploy a peertube solution using custom domain but got an unclear error

The error says that the host you entered as fqdn for the gateway workload doesn't point to the gateway ip. so it might not propagated yet or badly configured.

deployed multiple peertube and worked fine

https://app.testlodge.com/a/26076/projects/40893/suites/234374?expand_section=422332#case_4150341


Handling new synonyms

There are some changes in the GBIF taxonomy backbone which we should take into account. Two of our taxa as published on GBIF are now pointing to two synonyms:

Egeria densa is now synonym of Elodea densa
Heracleum sosnowskyi is now synonym of Heracleum pubescens

What does it means? I use the taxon keys related to the taxa as in the GBIF backbone for the early alert. So, we risk to miss some occurrences in the future in case somebody will publish data using the accepted taxon or other synonyms linked to it.
If you trust this synonymy link GBIF did, then I recommend to update the RIPARIAS target species list using the accepted names.

@damianooldoni in principle no problem to use the accepted name, although I think it will take some time before these new taxonomic insights will be taken into account in the various databases (cf. MAP and obs.be still use Egeria densa and will keep doing this probably, also it is their good right to have their own opinion on whether or not to follow new taxonomic insight of course).

Heracleum sosnowskyi: for the Union List species I think we should stick to the name mentioned in the legislative regime (updated consolidated versions of the Union List, which mention new synonyms, are regularly published, the last one can be found here). Otherwise, people will get confused or not realize it's on the list. In the background, of course, when we do gbif downloads, all relevant keys should be addressed so we don't miss any data.
Egeria densa: no problem to use the accepted name (the synonym is already quite old)

I am still in favour of publishing the Union List as a checklist on gbif but we still have no clue as to who should author it. Perhaps, it would be best actually to use a generic author, e.g. "RIPARIAS (2023). xxx". This way, no one claims a list that is not theirs, and at the same time it is clear which project uses it and who transposed the list to the gbif backbone.

@timadriaens: thanks.
Some answers to your thoughts:

In the document you menion I didn't found any new synonym of H. sosnowskyi. I understand your concern to stick to the EU list as much as possible
Egeria densa is not on the list so we can change it. Nice to read you agree on it 👍 1

I agree on the solution of using the keys of the accepted taxa for triggering downloads so we have all the occurrences. Of course we should probably pay attention to mention on the early alert tool About page how it works so that people are not confused about getting data of H. pubescens instead of H. sosnowskyi for example.

Notice that there is already ID sheets available mentioning Egeria densa, see https://www.riparias.be/628/download
Can we update it online? Maybe yes, but not on paper.
So, the most conservative way of proceeding could be to stick with Egeria densa as we probably will do with H. sosnowskyi.

Agreed to leave the taxa as they are in the checklist. We will use the nubKey of the accepted in the early alert tool.


WHEN CAN WE EXPECT EXPRESS 5

i think the title says it all!
regards

I'd like to know too. Some time ago, I read to answer a question that Express 4 has a long way to go. That sounds to me that we are not going to see express 5 for a long time. While Node JS is trying to adopt new forms of EcmaScript, we are still using preprocessors for javascript.

Every time this question is asked, means folks like myself need to respond instead of workijg towards it. Please ask more construtive questions in the future like "what can i do to help" instead of asking when something will happen. If you want something to happen byt are unable to offer help, sometimes offering to sponsor someone to do the work is another method.