Create Endpoint_Malware_Investigation_-_Generic_V2.md

Status
In Progress
Description
This article will provide guidelines for Endpoint Malware Investigation - Generic V2 playbook
Screenshots
Paste here any images that will help the reviewer

@evisochek Doc review completed.

@ShahafBenYakir @kirbles19 who should approve/merge these PR on GitHub once they get the "docs approved"?

@evisochek I can't seem to find this playbook in content repo is it there? why aren't we adding this README through the content repo?

This PB is the new version to "Endpoint_Malware_Investigation_-_Generic" due to the implementation of indicators extraction rules for 6.2 version.
@ShahafBenYakir


Fix console errors

Summary
Fixes two console errors currently in master:

tabfocus on textbox component was marked as required, wasn't provided in create_post, but also wasn't used in textbox ... made it optional, used it in textbox and defaulted to 0 (the existing hardcoded value)
direct handling of focus was removed from settingitemmin a while back, but still expected by themesetting component to be passed to settingitemmin ... removed

Ticket Link
No ticket, quicker to just fix and push. :P
Release Note
Neither of these should have visible impact beyond the ugly console error in dev, so I don't think release notes are necessary
NONE

Thanks @calebroseland!
My only intent here is to correct a console error where tabindex was being expected (even though it wasn't even being used) but not provided. Let me know if I misunderstood!


Feature: Add Support for Project Folders

With Monodevelop in can structure my Projects in Folders, like:

This is nice to keep large projects structuriesed and it would be great to have this with Protobuild.
In the .sln it looks like this:
# Visual Studio 2010
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "WzSharpEngine.Linux", "Engine\WzSharpEngine.Linux.csproj", "{68CBEFC5-7261-4570-6E67-696E652E4C69}"
EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Format", "Format", "{8F946CBF-31C0-47C5-9A1F-DA4E3E879367}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "WzSharpEngine.Format.Ini.Linux", "Format\Ini\WzSharpEngine.Format.Ini.Linux.csproj", "{DCB4E7C9-BB8F-AEDE-9CB3-D2DCDAA6466F}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "WzSharpEngine.Format.Xml.Linux", "Format\Xml\WzSharpEngine.Format.Xml.Linux.csproj", "{DCB4E7C9-CA8F-B1DD-9CB3-D2DCDAA6466F}"
EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Renderer3D", "Renderer3D", "{1CEEDF42-75F1-411A-8A28-60242A44A2D9}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "WzSharpEngine.Renderer3D.Terrain.Linux", "Renderer3D\Terrain\WzSharpEngine.Renderer3D.Terrain.Linux.csproj", "{48212AF3-5C3B-89A3-9CBB-CEE0D78FBBD3}"
EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "ThirdParty", "ThirdParty", "{C61894B6-BC81-4698-B10A-EC6A92163069}"
EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "MonoGame-GLSL", "MonoGame-GLSL", "{2F5AA4E6-7198-4573-B19A-4E77F50079C1}"
EndProject

Closing this off as no-one has indicated further interest in it and no-one has stepped up to implement it.


onChange event on key for input tag

Is it normal that the onChange event is not fired on every key for an input tag with Inferno?

onchange events only dispatch after you blur/defocus the text/textarea input. this is typical DOM behavior (unrelated to Inferno). oninput and onkeyup can be used instead.

@vinej This is expected behaviour for onchange – like @leeoniya has said above, you're best using another event for what you're trying to do :)


camera：takePicture() displays the last photo taken

In my fluttle adnroid application, when I use takepicture to take photos for many times, the photos displayed are often taken in the last pose. For example, this time, when I preview and take photos with my head straight, the photos I took last time when my header was Sideways are displayed! It's terrible.
camera: ^0.8.1+1
[✓] Flutter (Channel unknown, 2.5.0, on macOS 11.6.1 20G224 darwin-x64, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 2020.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2020.2.2)
[✓] VS Code (version 1.38.0)
[✓] Connected device (3 available)

Real machine model: Xiaomi mix 3

@clycheng2015
You are using an old version of the plugin and framework. Current plugin version is ^0.9.4+5 and stable is 2.8.0. I recommend to upgrade both and try again to see if behavior still persists or not.
If yes, then provide updated flutter doctor -v, plugin version and a complete minimal reproducible code sample that we can use to verify.
Thanks.


Change 'bool operator ==(dynamic other))' to 'bool operator ==(Object other))'

While using Moskito, there exists an error after running the build_runner concerning the override of the operator.
The override that is used in this package seems to be not correct, because in object.dart of the dart language there is an abstract method like this:
external bool operator ==(Object other);
I think that's why mockito does not find the correct implementation of this override.
There was also an discussion about this: https://github.com/dart-lang/mockito/issues/479
Also consider: With this implementation its ok to compare Version and null; while Object specify the compared value not to be null.

Fixed in : https://github.com/dartninja/version/pull/21

I might be a bit behind, why wouldn't it be desirable to check if a version object is null?

Since null safety, this is the correct override for the equals operator: https://api.dart.dev/stable/2.19.2/dart-core/Object/operator_equals.html
Before null safety, it's totally fine to check on null.


Minh Branch

Assignee Tasks

[ ] added unit tests (or none needed)
[ ] written relevant docs (or none needed)
[ ] referenced any relevant issues (or none exist)

Guidelines
Please add a description of this Pull Request's motivation, scope, outstanding issues or potential alternatives, reasoning behind the current solution, and any other relevant information for posterity.

Your PR Notes Here

minh made changes to new branch "minh-branch"


Enable cache-busting for try.dot.net assets

try.dot.net takes advantage of browser caching to speed up load times, but does not have a cache busting strategy in place. Some changes now require Ctrl+F5 in order to load on client machines. This should be done automatically through version strings in resource request URLs or some similar mechanism.

This is done.


Add: Coverage from Gradle Managed Devices.

Gradle Managed Devices collect code coverage (if configured) for instrumented tests as well. The path at which the coverage files are written is build/outputs/managed_device_code_coverage/<managed device name>/coverage.ec.
The Android Gradle Plugin creates an "allDevices" task, which has to run if instrumented Android tests are enabled according to the configuration.

@Rolf-Smit 👋 Let me know if this MR is OK. What this is missing right now is a way to test that the managed devices' coverage file is used. Any ideas for that? 🤔

Thanks for you PR 👍.
At first glance everything looks OK, I will indeed have to look into the testing part. I will dive into this further this evening when I have some spare time.

Just a small heads-up, I tried the code on your branch and there are some things for me to figure out, most importantly:

How to make sure people can choose between using Gradle Managed Device or regular devices available via ADB (emulators or real devices)? One way would be to indeed check the Gradle configuration for configured devices, and if any assume to run on those. However this may not always be the preferred method. Should this plugin maybe publish several different tasks based on the devices that are avaialble( e.g. rootCoverageReportAllDevices, rootCoverageReportPixel2)?

How to make sure people can configure on which device (of all the Gradle Managed Devices) to run the code coverage? Default to all devices? Or make this configurable?

I possibly need to change some CI settings, to make sure these changes can be tested on Gradle Managed Devices.

I have started to experiment with this on a local branch, and will try to keep you up-to-date on the progress.

Thanks for having a look!
When it comes to configuration, I thought perhaps there's an easier way: Change this plugin to only use mustRunAfter to ensure its tasks are run after all the tasks that produce coverage information. Then users can select which test tasks to invoke when they invoke Gradle, e.g., ./gradlew :app:allDevicesDebugAndroidTest :app2:pixel2DebugAndroidTest :rootCoverageReport.
The main issue with this idea is that this plugin won't know which *.ec files to pick up. I personally just used executionData.from(fileTree(buildDir) { include("**/*.exec", "**/*.ec") }) before I found this great plugin. This was fine as I only collect coverage data in my CI pipeline, which always does a clean build. However, as you outline via a code comment, the plugin might accidentally pick up previous builds' coverage data if the build isn't clean. That's not what we want, of course!
https://github.com/NeoTech-Software/Android-Root-Coverage-Plugin/blob/4ee5da69f900134cfff92d8458350caf7207aa19/plugin/src/main/kotlin/org/neotech/plugin/rootcoverage/JaCoCoConfiguration.kt#L59-L60
Perhaps there is a way to know which tasks produced coverage file results in the current Gradle invocation? 🤔

So I have been thinking and experimenting a bit, and I think there are 2 "problems" to solve:

How to avoid unwanted (old) execution data from being included in the final report(s).
How to make device selection (classic devices vs Gradle Managed Devices) possible?

1. How to avoid unwanted (old) execution data from being included in the final report(s)?
To be honest I think we can get away (for now) with including the Gradle Managed Device paths in the configuration, even if this can indeed lead to pollution of results. Why? Because pollution of results can now also happen. For example: if you run on device A, then switch branches and run on device B, without a clean in between both execution data files will be picked up.
Is this a solvable issue? Maybe. As of now I'm not aware of an official API to get the execution data paths from the Android Gradle Plugin tasks that execute the tests. I'm also not aware of an unofficial method. However this should not be impossible to do.
Is this something that needs fixing before introducing support for Gradle Managed Devices? I don't think so, since the issue already exists. I instead will update documentation and recommend clean builds.
2. How to make device selection (classic devices vs Gradle Managed Devices) possible?
Currently this plugin will (with default setup) execute test tasks on all available devices (available meaning: through ADB). This behavior can be altered by:
a. Disable test executing completely (through rootCoverage.executeAndroidTests = false), allowing you to run on device test tasks manually (before executing the coverage Gradle tasks*).
b. Run only on a specific device, by using the ANDROID_SERIAL environment variable.
*This only works reliably when indeed mustRunAfter is used, this is something that could be a PR on it's own.
Can we do the same for Gradle Managed Devices?
a. Yes, we can still disable execution completely (however this requires the plugin to know the execution data paths, see point 1)
b. Yes, if the plugin would allow the user to choose to depend on ${deviceName}AndroidTest instead of allDevicesAndroidTest. However to complicate things, the user not only needs to choose the device for the whole run, the user needs to possibly specify a specific device for each module (unless the same device names per module are used).
For now, supporting option a. and for b. just allDevicesAndroidTest as the default behavior would be fine I believe.
However for the future I'm thinking to provide a configuration option so users can choose which single Gradle Managed Device (or list of devices) must be used.
Separate points of action for me (subject to change as I go forward and think more about this):

[ ] Introduce mustRunAfter (or similar) to make sure coverage tasks always run after test tasks. This allows option a. to work super easily, without having to run 2 separate Gradle commands).
[] Add support for execution data generated by Gradle Managed Devices, so it is included in reports
[] Change the behavior of the plugin to, if Gradle Managed Devices are found, the tests are run on those (by default allDevices)
[] Update documentation and advise to make sure clean is used between coverage runs, to avoid poluting results, and...
[] ...find a way to exactly figure out which execution data was generated in a specific Gradle run and should be included.
[] Add a way to configure on which Gradle Managed Devices tests should run.

I believe this is about it. I will start working on this and I will let you know what to do with this PR, because it has some useful points for sure, I may request some changes so we can go forward in small steps.

That all sounds good to me.
One thing to note since I've been looking into the ability to retrieve the output of a specific run:
gradle.taskGraph.whenReady {
    val coverageFiles = allTasks.flatMap { task -> task.outputs.files.asFileTree.filter { file -> file.extension == "exec" || file.extension == "ec" } }
    tasks.named<JacocoReport>("rootCoverageReport").configure { executionData.setFrom(coverageFiles) }
    println(tasks.named<JacocoReport>("rootCoverageReport").get().executionData.asPath)
}

This is a very crude test I did. You'll notice the asFileTree only picks up the files once they are created. So while this snippet can work to grab the output of all tasks part of the current run (which Gradle calls the "task execution graph" btw!), the actual act of checking for the files in the various task.outputs must be done after the respective task has run. Assuming that's done, the above snippet shows how to configure the executionData accordingly.
I also tried a different attempt:
gradle.taskGraph.whenReady {
    allTasks.forEach {
        val coverageDirectory = when (it) {
            is AndroidUnitTest -> {
                println(it.outputs.files.filter { it.extension == "exec" }.asPath)
                (AndroidUnitTest::class.java.getDeclaredMethod("getJacocoCoverageOutputFile").invoke(it) as RegularFileProperty).get().asFile.parent
            }
            is DeviceProviderInstrumentTestTask -> it.coverageDirectory.get().asFile.absolutePath
            is ManagedDeviceInstrumentationTestTask -> it.getCoverageDirectory().get().asFile.absolutePath
            else -> null
        }

        if (coverageDirectory != null) {
            println("Found: ${it.name} - $coverageDirectory")
        }
    }
}

Now with all that said, I think the best path moving forward is to simply require a clean build. It would simplify this plugin a lot if we could simply set it to grab all coverage files via executionData.from(fileTree(buildDir) { include("**/*.exec", "**/*.ec") }). As long as that is clear in the documentation, I don't see any downside to it.
One important thing I want to point out once more: If you were to change it to pick up all coverage files like that, I don't think this plugin needs to offer tasks for specific test tasks at all. As I explained in the earlier comment, all we need is to set up mustRunAfter to run after all potentially found tasks that produce coverage data. Then the user can simply decide which test tasks (unit, instrumentation against running emulator, managed device; all of which can be module-specific) by ensuring those tasks are listed as part of their Gradle run.
I know that's a breaking change, but it would mean the user has more flexibility (i.e. any other test tasks this plugin currently doesn't know about can be made to work with the plugin easily) and more importantly, this plugin's implementation is simpler and can pick up changes to the coverage file paths or whole new features like managed devices without requiring an update.

Unfortunate my private life got in the way, and I was only able to work on this now. I had to make quite some additional changes to make this functionality ready for the plugin, and finished the work in this PR: #83. Therefore I'm closing this PR.
The support will be released with version 1.7.0 of this plugin. Thanks for your contribution!


containerd process building from k3s costs more memory than building from containerd

we know that starting k3s agent will have two processes: k3s main process and containerd process, actually, containerd process will cost more memory than real containerd from "https://github.com/containerd/containerd/releases". It seems the mechanism of reexec function will cost more memories if containerd start in this condition. it is a performance problem for edge computing scene.
the data comparison( I means using "./containerd" start process separately and collect statistics):
unique containerd memory: 49348
k3s  containerd memory:  83600
Version:

v1.0.0
Describe the bug

containerd cost more memories
To Reproduce

start containerd process separately and compare
Expected behavior

k3s containerd cost as little memory as possible because it is a unique sub process.
Actual behavior

Additional context

appreciated for any reply

wouldn't most of the difference there be shared, resident?

wouldn't most of the difference there be shared, resident?

i mean, since the k3s and containerd processes are two separate invocations of the k3s executable i'd be surprised if your total memory usage on the system was lower with a separately compiled containerd

I guess reexec mechanism will integrate one binary, which can link other binary we need(containerd, ctr, crictl, etc), but containerd process have a same entrypoint with k3s,  containerd process will invoke reexec branch, which import other library  and pakcage k3s need but containerd do not need.
I mean if there is no containerd process separately other than all function(kubelet, containerd, flannel) embed into k3s process，which should cost less memory.

I mean k3s process and containerd subprocess have a same main() function, the different is containerd enter into reexec branch( if{} statement ), maybe import package use repeated memory?
of course this do minus disk space

Yes, this makes the k3s binary rather large on disk but it should be less than if you compiled k3s without containerd, then the compiled containerd and then measure the combined total size. The k3s compiled with containerd should total at least a few MB less (de-duped go runtime).
Now, unless I am mistaken, two processes sourced from the same executable, regardless of whether or not they are on different branches of execution (implies different memory profiles), should use in total less memory because the OS can share the loaded code between them. Less memory in total when compared to the hypothesized k3s-without-containerd + containerd multi-executable scenario above.
Re-reading your responses, I think you agree with me. If not, I encourage you to run the same comparative experiment again but this time focus on total persistent disk used and total free memory.


Main Menu enhancements

Description
Task: Main Menu Enhancements: Add More Sprites, Sound, and Owl Size Bug Fix
Feature: #519
This task focuses on enhancing the main menu by adding new sprites, integrating sound effects, refining visual elements such as fixing the owl size bug, and refactoring the minimize/maximize button functionality. The goal is to create a more dynamic and polished main menu experience. The addition of sound effects will make interactions more immersive, while the refactor of the minimize/maximize button functionality and the owl size fix will ensure visual consistency across screen resolutions and improve the user interface.
Example (optional)

Owl Size Bug Fix: Ensure that the owl’s size remains consistent across all screen resolutions, particularly when switching to full-screen mode.
Sound Effects: Integrate sound effects for main menu interactions, such as hovering over or clicking buttons, to create a more immersive experience.
Refactor Minimize/Maximize Button: Clean up and improve the functionality of the minimize/maximize button to prevent screen resizing issues and ensure smoother transitions.

Dependencies
None
Milestones
List of steps that need to be completed for this task.

[x] Add Additional Sprites to Main Menu (Due Oct. 8)
[ ] Integrate Sound Effects for Menu Interactions (Due Oct. 9)
[x] Fix Owl Size Bug on Full-Screen Mode (Due Oct. 10)
[x] Refactor Minimize/Maximize Button Functionality (Due Oct. 11)
[x] Test Main Menu Enhancements Across Different Screen Resolutions (Due Oct. 11)

Completion Deadline: Oct. 11
Documentation

To be updated

Member

Jay Thakkar (@jt-09)

fixed in pr #653


things table needs playcount column added

On a new install, the things database doesn't exist.
It needs to have metadata like playcount added to the table, currently that's manually.

this does this now on first run


move react-is to peerDeps

Correct, but most people have it installed already. It’s important to move
to peer deps for deduping.
On Tue, Apr 23, 2019 at 3:28 AM Max Stoiber<EMAIL_ADDRESS>wrote:

@mxstbr requested changes on this pull request.
Wouldn't this require everybody using styled-components to also explicitly
install react-is even though they never use react-is themselves?!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/pull/2187#pullrequestreview-229385806,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAELFVWYGCVKJZ7LOOE5VZDPR23BTANCNFSM4GBVV5IQ
.

I strongly disagree. I have never once installed react-is manually and literally have no clue what that package even does. I do not want to require users of styled-components to also have to install a dependency without ever actually using it themselves.
If people need to dedupe they should just use the yarn resolutions feature which handles exactly that.
{
  "resolutions": {
    "react-is": "whatever"
  }
}

That will make sure to only install a single version of it across your monorepo.

I noticed this was merged into the beta for v5, has the intention on this changed, and if so is there another issue to read up on the reasoning here?
Thanks!

I was wondering the same as @kilpatty.
I see it was added in ff771d5e668907b51e7fbe4b69e9d55e69781274 by @kitten. Was this intentional?


Dolby Digital Plus Detection

Hi.
MediaInfo now detects E-AC-3 into a wrong bitrate. I assume it's not fully supported. Any idea of fixing?
Audio
ID : 2
Format : E-AC-3
Format/Info : Enhanced Audio Coding 3
Codec ID : A_EAC3
Duration : 2 min 42 s
Bit rate mode : Constant
Bit rate : 500 b/s
Channel(s) : 8 channels
Channel(s)_Original : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 187.500 FPS (256 SPF)
Compression mode : Lossy
Stream size : 24.7 MiB (64%)
Service kind : Complete Main
Default : Yes
Forced : No
sample https://nofile.io/f/Twb7S2WWtCc#d5fe63d16a8f592e

Due to non "pure" E-AC-3 stream (the core stream is in AC-3), and MediaInfo was not well supported such hybrid content (AC-3 for core and E-AC-3 for additional channels)
Fixed in https://github.com/MediaArea/MediaInfoLib/pull/896, you can test a development snapshot.


Legged robot raisim example is unstable

Hello,
when running the legged_robot_raisim example the pose of the robot immediately changes, the center of mass moves slightly in the x direction and contact forces of the front legs change the orientation. The robot is in some kind of an unstable state and the optimal forces oscillate slightly. After a while, even without any gait command, the right hind leg starts to float in the air and the computation crushes.
Is this a bug or is it due to the use of raisim simulator on a simplified model?
This is the pose of the robot after 2 seconds of the simulation. No gait commanded, no trajectory commanded.

I had the same problem. Do I need to tune the joint Kp and Kd gain, or change the parameters of RaiSim?

Do we have to implement a WBC controller for simulation?

Hi @Kate88L and @matheecs,
This is not due to the use of a simplified robot model and no need to tune gains or implement WBC. The main issue here is that for the positionErrorGain in the ZeroVelocityConstraint for the EE it is currently assumed that the terrain is flat. You have two options:

Set the generateTerrain flag to false (recommended if flat terrain works for you): https://github.com/leggedrobotics/ocs2/blob/main/ocs2_raisim/ocs2_legged_robot_raisim/config/raisim.info#L11
Set the positionErrorGain to 0.0 (recommended if you need rough terrain): https://github.com/leggedrobotics/ocs2/blob/main/ocs2_robotic_examples/ocs2_legged_robot/config/mpc/task.info#L12

@farbod-farshidian FYI

Works like a charm. Thanks for the quick reply  :)


Jove

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Jove has now DRM's for its content encrypted with Sample-AES.
However preview videos (first 2 minutes) for paying content can be downloaded.

links updated (changes /video to /v)
Thumbnails changed to jpg
Regex modified to match the new DOM
Removes the comments downloading
Download preview video for non-free content
Throws an error for free content as it is DRM protected using Sample-AES

No time to modify the pull request so I close it.


Fix min-versions; add min-version CI check

In an ongoing quest of mine to run a min-versions test for imxrt-uart-panic, I stumbled across incorrect minimal versions in this crate.
I also added a CI check that makes sure versions are updated in the future.

I stumbled across incorrect minimal versions in this crate.

I don't see why today's cortex-m and usb-device versions are incorrect. If I pin these two dependencies to something old, like
[dependencies]
cortex-m = "=0.7.0"
usb-device = "=0.3.0"

run cargo update and build the package with cargo build, then everything succeeds. If imxrt-usbd truly required the minimum versions suggested here, then I would have expected my test build to fail.
What am I missing?

Reverting the direct dependencies sadly isn't enough, for a full min-version checks the dependencies of dependencies also need to be reverted to their minimal semver compatible version.

For cortex-m:
It seems that bare-metal required had an error with newer Rust compilers that got in bare-metal 0.2.3.
The min-version of bare-metal is currently 0.2.1, though. That's why cortex-m bumped it in cortex-m 0.7.4.
The exact error with =0.7.0 looks to me like this:
> cargo minimal-versions check
info: running `cargo hack check`
info: running `cargo check` on imxrt-usbd (1/1)
    Checking bare-metal v0.2.1
error[E0557]: feature has been removed
 --> C:\Users\Martin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bare-metal-0.2.1\src\lib.rs:7:13
  |
7 |     feature(const_fn, const_unsafe_cell_new)
  |             ^^^^^^^^ feature has been removed
  |
  = note: split into finer-grained feature gates

error[E0554]: `#![feature]` may not be used on the stable release channel
 --> C:\Users\Martin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bare-metal-0.2.1\src\lib.rs:7:23
  |
7 |     feature(const_fn, const_unsafe_cell_new)
  |                       ^^^^^^^^^^^^^^^^^^^^^

Some errors have detailed explanations: E0554, E0557.
For more information about an error, try `rustc --explain E0554`.
error: could not compile `bare-metal` (lib) due to 2 previous errors
error: process didn't exit successfully: `\\?\C:\Users\Martin\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin\cargo.exe check --manifest-path Cargo.toml` (exit code: 101)
error: process didn't exit successfully: `\\?\C:\Users\Martin\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin\cargo.exe hack check` (exit code: 1)

For usb-device:
The error only occurs when running cargo test, although it's debatable if tests should influence min-versions.
It's actually a failing doctest:
running 6 tests
test src\lib.rs - Peripherals (line 73) - compile ... ok
test src\bus.rs - bus::BusAdapter (line 46) - compile ... FAILED
test src\gpt.rs - gpt (line 13) - compile ... FAILED
test src\buffer.rs - buffer::EndpointMemory (line 20) ... ok
test src\state.rs - state::EndpointState (line 74) ... ok
test src\state.rs - state::EndpointState (line 90) ... ok

failures:

---- src\bus.rs - bus::BusAdapter (line 46) stdout ----
error[E0433]: failed to resolve: use of undeclared type `StringDescriptors`
  --> src\bus.rs:69:16
   |
26 |     .strings(&[StringDescriptors::default().product("imxrt-usbd")]).unwrap()
   |                ^^^^^^^^^^^^^^^^^ use of undeclared type `StringDescriptors`
   |
help: consider importing this struct
   |
2  + use usb_device::device::StringDescriptors;
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0433`.
Couldn't compile the test.
---- src\gpt.rs - gpt (line 13) stdout ----
error[E0433]: failed to resolve: use of undeclared type `StringDescriptors`
  --> src\gpt.rs:47:16
   |
37 |     .strings(&[StringDescriptors::default().product("imxrt-usbd")]).unwrap()
   |                ^^^^^^^^^^^^^^^^^ use of undeclared type `StringDescriptors`
   |
help: consider importing this struct
   |
2  + use usb_device::device::StringDescriptors;
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0433`.
Couldn't compile the test.

failures:
    src\bus.rs - bus::BusAdapter (line 46)
    src\gpt.rs - gpt (line 13)

test result: FAILED. 4 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.18s

It seems that StringDescriptors got added to the prelude in usb_device 0.3.1

I yet have to find out what's up with the proc_macro_span_shrink, this doesn't happen on my Windows machine. Gotta debug on a linux machine, I'm on it.

@mciantyre Think I fixed it. It was accidentally using the nightly toolchain to do the main MSRV check, and it seems like there is a bug in the current nightly.

The error only occurs when running cargo test, although it's debatable if tests should influence min-versions.

We're free to introduce a development dependency that requires a minimum usb-device of 0.3.1. That solves the cargo test issue. Since it's a development dependency, this kind of minimum version doesn't impact all imxrt-usbd users.
Let's focus on cortex-m for simplicity. Consider a user who wants to specifically use cortex-m 0.7.0 throughout their entire build. They pin the dependency in their program's Cargo.toml. If we adopt this change to require at least version 0.7.4, I'm concerned we'll break this user's build.
I pushed a CI job to demonstrate the concern. Why should we prevent this user from building their firmware, especially when we could support their build?

The error only occurs when running cargo test, although it's debatable if tests should influence min-versions.

We're free to introduce a development dependency that requires a minimum usb-device of 0.3.1. That solves the cargo test issue. Since it's a development dependency, this kind of minimum version doesn't impact all imxrt-usbd users.
Let's focus on cortex-m for simplicity. Consider a user who wants to specifically use cortex-m 0.7.0 throughout their entire build. They pin the dependency in their program's Cargo.toml. If we adopt this change to require at least version 0.7.4, I'm concerned we'll break this user's build.
I pushed a CI job to demonstrate the concern. Why should we prevent this user from building their firmware, especially when we could support their build?

OK, I get your point now.
I guess in the end this is a convention. If you don't really use the features that caused cortex-m to go from0.6 to 0.7, you could also argue that you should instead define cortex-m = ">= 0.6".
crates.io gives the recommendation that you should always define the full version.
On the one side you might force a user to update a package by specifying a newer version. On the other hand, if you don't specify it, you risk that when the user updates only your package, it's dependencies don't get properly updated. It's an opinion thing in the end.
For me the big plus is that if a project has a min version check and at some point dependencies break because of their msrv or similar, I can always revert to the min versions and it is guaranteed to work again.
Otherwise you need to find the right intermediate versions that work, and for a project with 30+ (indirect) this can be a pain (been there).

@mciantyre I actually have a good idea that kind of fixes the issues that you have with both of my PRs. What if we combine the two checks? Like, a min-version check on the MSRV.
This guarantees that dependencies cannot break the MSRV through updates, and gives the user a known working rust compiler + dependencies version that will work now and always.
What do you think?

Replaced by #28.


Pack unicode strings

If I have the following variables:
keys = [u'1', u'12', u'13', u'123', u'132', u'1234']
vals = [u'a', u'b', u'c', u'd', u'e', u'f']
fmt = "s"
trie = marisa_trie.RecordTrie(fmt, zip(keys, vals))
But I keep getting argument for 's' must be a string
Any help?

Hi,
it is not possible to serialize unicode (or str in Python 3) using the struct module. You have to manually encode vals to bytes and then pass them to RecordTrie:
trie = matrisa_trie.RecordTrie("s", zip(keys, map(vals, str.encode)))


Obsolete logging facility V5

Again this felt great, thanks for leading the way ....

Adding the V5 milestone to this. I think I will bail out of this for now and start working on explicit assembly versions as we discussed. I am even happy to close this out once we have made more traction on the v4 stuff, dont like things hanging around open. I also have this on branch so it is really not a problem.


接口返回502 bad gateway

'\r\n502 Bad Gateway\r\n\r\n502 Bad Gateway\r\nnginx/1.16.1\r\n\r\n\r\n'

same issue

same issue

same issue

Hello @BlankerL
Maybe the application server has been  down, could you help to check about that ?
Thank you.

另外，api的帮助界面也打不开了。

#30 提到：
暂时先使用此 https://lab.ahusmart.com/ 替换 https://lab.isaaclin.cn/ ，接口协议完全一致

抱歉，服务器访问量过大，已经重启服务器了。

抱歉，服务器访问量过大，已经重启服务器了。
Sorry for the trouble, there are too many connections to the server. I have rebooted the server and it is functioning now.

谢谢！

已经添加uWSGI守护进程Supervisor，测试强制关闭uWSGI后，守护进程会自动重启uWSGI。
Use Supervisor to screen and daemonize uWSGI. After manually killing uWSGI, Supervisor will restart it automatically.


kernel crashes at Oracle Linux 8

Kubernetes v1.27.5
Bare metal nodes
LVM Thinpool
piraeus-operator v2.4.1
Oracle Linux 8
Kernel 5.15.0-<IP_ADDRESS>.el8uek.x86_64 + default drbd image drbd9-jammy
Also reproduced with kernel 4.18 + drbd image drbd9-almalinux8
How to reproduce:
Create and subsequently delete a number of volumes and attach them. I tested with about 8 pvc-s and pod-s and made around 20 operations of creation and then deletion of them. Randomly the server goes to reboot because of crash. Most often it happened during volumes deletion but also it was reproduced during a new pvc creation.
UEK kernel Makefile (/usr/src/kernels/5.15.0-<IP_ADDRESS>.el8uek.x86_64/Makefile) patched to be able to build drbd:
--- Makefile	2024-01-15 12:24:44.452296691 +0000
+++ Makefile	2024-01-15 12:25:36.325543428 +0000
@@ -853,18 +853,18 @@
 endif

 # Initialize all stack variables with a 0xAA pattern.
-ifdef CONFIG_INIT_STACK_ALL_PATTERN
-KBUILD_CFLAGS	+= -ftrivial-auto-var-init=pattern
-endif
+#ifdef CONFIG_INIT_STACK_ALL_PATTERN
+#KBUILD_CFLAGS	+= -ftrivial-auto-var-init=pattern
+#endif

 # Initialize all stack variables with a zero value.
-ifdef CONFIG_INIT_STACK_ALL_ZERO
-KBUILD_CFLAGS	+= -ftrivial-auto-var-init=zero
-ifdef CONFIG_CC_HAS_AUTO_VAR_INIT_ZERO_ENABLER
+#ifdef CONFIG_INIT_STACK_ALL_ZERO
+#KBUILD_CFLAGS	+= -ftrivial-auto-var-init=zero
+#ifdef CONFIG_CC_HAS_AUTO_VAR_INIT_ZERO_ENABLER
 # https://github.com/llvm/llvm-project/issues/44842
-KBUILD_CFLAGS	+= -enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang
-endif
-endif
+#KBUILD_CFLAGS	+= -enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang
+#endif
+#endif

apiVersion: piraeus.io/v1
kind: LinstorSatelliteConfiguration
metadata:
  name: piraeus-storage-pool
spec:
  storagePools:
    - name: piraeus-storage-pool-lvmthin
      lvmThinPool:
        volumeGroup: lvmvgthin
        thinPool: thinpool_piraeus
  podTemplate:
    spec:
      hostNetwork: true
  nodeAffinity:
    nodeSelectorTerms:
    - matchExpressions:
      - key: node-role.kubernetes.io/control-plane
        operator: DoesNotExist
      - key: piraeus
        operator: In
        values:
         - enabled

---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: piraeus-storage-replicated-lvm
provisioner: linstor.csi.linbit.com
allowVolumeExpansion: true
volumeBindingMode: WaitForFirstConsumer
reclaimPolicy: Delete
parameters:
  # https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-sc-parameters
  ## CSI related parameters
  csi.storage.k8s.io/fstype: ext4
  ## LINSTOR parameters
  linstor.csi.linbit.com/storagePool: piraeus-storage-pool-lvmthin
  linstor.csi.linbit.com/placementCount: "2"
  linstor.csi.linbit.com/mountOpts: noatime,discard
  property.linstor.csi.linbit.com/DrbdOptions/Net/max-buffers: "11000"

---
apiVersion: piraeus.io/v1
kind: LinstorCluster
metadata:
  name: linstorcluster
spec:
  nodeAffinity:
    nodeSelectorTerms:
    - matchExpressions:
      - key: node-role.kubernetes.io/control-plane
        operator: DoesNotExist
  # https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-autoplace-linstor
  properties:
    - name: DrbdOptions/Net/max-buffers # controller level
      value: "10000"
    - name: Autoplacer/Weights/MaxFreeSpace
      value: "0" # 1 default
    - name: Autoplacer/Weights/MinReservedSpace
      value: "10" # preferr nodes with minimal reserved space on thin pool
    - name: Autoplacer/Weights/MinRscCount
      value: "0"
    # - name: Autoplacer/Weights/MaxThroughput
    #   value: "0" # COOL but not today

cat /proc/drbd
version: 9.2.8 (api:2/proto:86-122)
GIT-hash: e163b05a76254c0f51f999970e861d72bb16409a build by @srvh52.example.com, 2024-03-28 15:13:48
Transports (api:20): tcp (9.2.8) lb-tcp (9.2.8) rdma (9.2.8)

[ 4083.197349] Call Trace:
[ 4083.208990]  <TASK>
[ 4083.220334]  ? show_trace_log_lvl+0x1d6/0x2f9
[ 4083.231532]  ? show_trace_log_lvl+0x1d6/0x2f9
[ 4083.242553]  ? drbd_free_peer_req+0x99/0x210 [drbd]
[ 4083.253383]  ? __die_body.cold+0x8/0xa
[ 4083.263954]  ? page_fault_oops+0x16d/0x1ac
[ 4083.274325]  ? exc_page_fault+0x68/0x13b
[ 4083.284460]  ? asm_exc_page_fault+0x22/0x27
[ 4083.294360]  ? _raw_spin_lock_irq+0x13/0x58
[ 4083.303995]  drbd_free_peer_req+0x99/0x210 [drbd]
[ 4083.313482]  drbd_finish_peer_reqs+0xc0/0x180 [drbd]
[ 4083.322880]  drain_resync_activity+0x25b/0x43a [drbd]
[ 4083.332060]  conn_disconnect+0xf4/0x650 [drbd]
[ 4083.341017]  drbd_receiver+0x53/0x60 [drbd]
[ 4083.349787]  drbd_thread_setup+0x77/0x1df [drbd]
[ 4083.358332]  ? drbd_reclaim_path+0x90/0x90 [drbd]
[ 4083.366677]  kthread+0x127/0x144
[ 4083.374961]  ? set_kthread_struct+0x60/0x52
[ 4083.382938]  ret_from_fork+0x22/0x2d
[ 4083.390678]  </TASK>

vmcore-dmesg.txt.tar.gz
Full log attached
Any tips or ideas are highly appreciated

Looks like this is similar to https://github.com/LINBIT/drbd/issues/86

Hello! Thanks for the report. I guess it would be a good idea to add that information to the DRBD issue, as that seems to be the root cause.
We have seen it internally, but never been able to reproduce it reliably. Adding more context seems like a good idea.

Thanks for the answer. Should I add more details how I reproduced that?

Also, does it make sense to try with some older piraeus version? It's also reproduced with drbd 9.2.6 and piraeus v2.3.0

You could try DRBD 9.1.18.
That does mean you have to use host networking, but you already do use that.

@WanzenBug hello. There are our reproduction steps:
We have 5-nodes k8s cluster with SSD storage pools of 100 GB each (Thin LVM)
All queues are processed in 1 parallel operation:
csiAttacherWorkerThreads: 1
csiProvisionerWorkerThreads: 1
csiSnapshotterWorkerThreads: 1
csiResizerWorkerThreads: 1

30 STS are made with 3 replicas each, and each replica have 5 gigabytes PV
When pods are up, we change the size of all PVCs to 5.1 gigabytes
After all PV resize finished, we delete the namespace.
After that we restart the process from the beginning

When such a scheme is launched in a continuous cycle, we almost invariably have several node reboots per day. The operating system is not essential; we have encountered a similar problem with various 5.x and 6.x kernels from different distributions. However, the issue is definitely reproducible on the current LTS Ubuntu 22.04.
STS spec:
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: flog-generator-0
  namespace: test1
spec:
  podManagementPolicy: OrderedReady
  replicas: 3
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app.kubernetes.io/name: flog-generator-0
  serviceName: ""
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/name: flog-generator-0
    spec:
      containers:
      - args:
        - -c
        - /srv/flog/run.sh 2>&1 | tee -a /var/log/flog/fake.log
        command:
        - /bin/sh
        env:
        - name: FLOG_BATCH_SIZE
          value: "1024000"
        - name: FLOG_TIME_INTERVAL
          value: "1"
        image: ex42zav/flog:0.4.3
        imagePullPolicy: IfNotPresent
        name: flog-generator
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/log/flog
          name: flog-pv
      - env:
        - name: LOGS_DIRECTORIES
          value: /var/log/flog
        - name: LOGROTATE_INTERVAL
          value: hourly
        - name: LOGROTATE_COPIES
          value: "2"
        - name: LOGROTATE_SIZE
          value: 500M
        - name: LOGROTATE_CRONSCHEDULE
          value: 0 2 * * * *
        image: blacklabelops/logrotate
        imagePullPolicy: Always
        name: logrotate
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/log/flog
          name: flog-pv
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: default
      serviceAccountName: default
      terminationGracePeriodSeconds: 30
  updateStrategy:
    rollingUpdate:
      partition: 0
    type: RollingUpdate
  volumeClaimTemplates:
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      name: flog-pv
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 5Gi
      storageClassName: linstor-r2
      volumeMode: Filesystem

Thanks! You could also try switching to DRBD 9.1.18. We suspect there is a race condition introduced in the 9.2 branch.

Another idea on what might be causing the issue, with a work around in the CSI driver: https://github.com/piraeusdatastore/linstor-csi/pull/256
You might try that by using the  v1.5.0-2-g16c206a tag for the CSI image. You can edit the piraeus-operator-image-config to change the image.

We have tested with DRBD 9.1.18. Looks like the issue is not reproduced with this version

I'm also testing 9.1.18 now.
Can you tell, please, Is it safe to move existing installation from 9.2.5 to 9.1.18?

Can you tell, please, is it safe to move existing installation from 9.2.5 to 9.1.18?

Yes, it is safe.

@WanzenBug it looks like v1.5.0-2-g16c206a solves the node restart problem. Will you please create a tag version with it? (maybe like 1.5.1)
Also, it looks like there also problem inside DRBD, that cause crash in some conditions? Will you solve it? If you can't reproduce situation, I think, I can gave an ssh access to cluster where I can reproduce situation for you.

We tested this with 9.2.5 and 9.2.8, and above CSI version. Yes, there were no crash anymore.
Thank you, I'll wait for your solution.
Can you tell, will fix from  v1.5.0-2-g16c206a come in 1.5.1?

Yes, there will be a 1.5.1 with that. We still intend to fix the issue in DRBD, too.

Just wanted to let you know that we think we have tracked down the issue, no fix yet but we should have something ready for next DRBD release.

Fixed on the DRBD side with https://github.com/LINBIT/drbd/commit/857db82c989b36993ff7a3df3944c9862db1408d and https://github.com/LINBIT/drbd/commit/343e077e9664b203e5ebf8146dacc5c869b80e30.


Fe: (Performance) Item previews and Map

It'd be faster if we could simply reload the NFT rather than reload the entire page for Webaverse TV: https://webaverse.com/tv/1

Also it would be useful if there was progress loading animation for the NFT so we can tell what's happening, especially if the NFT media is large.

Map takes a long time to load, would be useful to have a loading bar in meantime.

The TV and map cases are separate.
For the TV case we should do a postMessage.
For the map case, we need to render the map serverside, without anyone relying on the hack I did to generate the map in realtime.

Broken out into:

https://github.com/webaverse/app/issues/1024
https://github.com/webaverse/app/issues/583


My App is not listed here

Hello,
even my app is not listed here. can someone tell me why is not listed here?
my app name is : SmartPark
If needed, I can share you the screenshot of the acknowledgment received on submission of our app to "flutter create".

@developer042 You can contribute here.

@pinkeshdarji, What can I contribute? I'm not clear. please let me know why is my app not listed here ?

@pinkeshdarji I don't have push access...pls grant me. thanks


ImGui doesn't support scale mode 'viewport' when executing games that use resized graphics.

When running Godot applications that use resized viewport for graphics, i expected the ImGui interface to display as normal, but didn't expect the interface to actually look pixelated instead.

When i look at the console, there's a error: imgui-godot: scale mode viewport is unsupported
How do i use ImGui on resized viewports?

It's not possible to support viewport scaling, but you can achieve a very similar effect by using stretch mode disabled, and putting your entire game in a SubViewport instead. Attached a project which shows the basics of how you might set that up.
GdsViewport.zip


Extra taxonomical columns in download

Data downloads will include in addition to the originally submitted SpeciesCodeType and SpeciesCode:

[x] SpeciesScientificName: Scientific name, if available (from ESAS)
[x] SpeciesEnglishName: English name, if available (from ESAS)
[x] WormsAphiaID: Accepted Aphia ID: link to latest accepted name for that taxon in WoRMS
[x] WormsScientificName: Accepted Aphia scientificName: link to latest accepted name for that taxon in WoRMS

Note that "accepted" might be a misnomer, because not all taxa have an accepted name in WoRMS (e.g. Pisces)

SpeciesScientificName: Scientific name, if available (this will come from the ESAS translation table)
SpeciesEnglishName: English name, if available (this will come from the ESAS translation table)

Both, in download and WebAPI

Nice! I notice that empty values are coded as "" rather than as null. I don't think it will cause any issues, but if it is easy to change, I would use null values.
"speciesCodeType":"ESAS",
"speciesCode":"5659",
"speciesScientificName":"", <---
"speciesEnglishName":"unidentified wader",
"wormsAphiaID":"2682",
"wormsScientificName":"Charadriiformes"

Yes, it is very easy.
That came from the value provided in the table, it's null now instead of an empty string:
https://esas.ices.dk/api/getObservationRecords?SpeciesCode=5659


Connection synchronization

When you use tokio-tungstenite to run a server, accepting a new connection blocks the acceptor loop until the websocket handshake is complete. This opens a DOS vector where malicious clients can prevent other clients from connecting by hogging the acceptor loop.
The solution here seems to be spawning a new tokio task to finish accepting a connection after the TcpListener connects.

ah yeah, that's true.
That should be an easy fix.

it's actually the same as https://github.com/gbaranski/ezsockets/issues/30.
We can move there.


refactor: correct config endpoint order

A summary of what changes this PR introduces and why they were made.

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[x] Refactor
[ ] Performance
[ ] Tests
[ ] Build
[ ] Documentation
[ ] Code style update
[ ] Continuous Integration
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR release a new version?

[x] Yes
[ ] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ ] It's submitted to the develop branch, not the master branch
[x] All tests are passing
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

The ci/circleci: node-10 job is failing as of 12bff314fbbc839cdeffbcdc545ac56defec42f5. Please review the logs for more information.
Once you've pushed the fixes, the build will automatically re-run. Thanks!


Fixes

PR checklist
Small changes to address comments from @drpatelh

[x] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!

[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/bactmap branch on the nf-core/test-datasets repository.

[ ] Make sure your code lints (nf-core lint .).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

Need to move this line up and out of the workflow section too @aunderwo . See this issue https://github.com/nf-core/viralrecon/issues/201


Library preferences

Should be able to read gradle/maven to pull available libraries and use that as context for code generation. That or gather imports from other files and use that as library preferences

https://aider.chat/docs/repomap.html


L2 distance benchmark fails validation

The L2 distance numba_dpex_k implementation fails the data validation step on CPU devices. Incidentally, the reference dpcpp implementation also fails data validation. The issue may point to use of atomic references. Needs further investigation and can be migration to numba-dpex or dpcpp once we know the root cause.

No validation failure in l2 distance. See log from latest CI run below. If issue occurs again, please reopen.
5  04.03.2023_21.07.58            l2_norm              S        1MB        Success     Unimplemented  Failed Execution           Success        Success  Unimplemented        Success        Success  Unimplemented        Success


Broken link to FS.File API in documentation

The FS.File API documentation in the Wiki
https://github.com/CollectionFS/Meteor-CollectionFS/wiki/FS.File
points to this broken link:
https://github.com/CollectionFS/DEPRECATING-cfs-file/blob/master/api.md

I assume the link should point to:
https://github.com/CollectionFS/Meteor-CollectionFS/blob/devel/packages/file/api.md

BTW: I also found out that I have to state .url() instead of .url if I want to retrieve the File's URL. This is not documented in the API description.


comment fixes, dead code removal

[x] ~Tests added / passed~ (N/A)
[x] Passes black dask / flake8 dask

Factored out of #6661 (DDF.iloc).

hmm dask/array/tests/test_linalg.py::test_norm_any_slice[False--1-shape1-chunks1], I suspect this is a flaky test.
Is there a way I can trigger a retry of a given GHA?

Apologies for the inconvenience, test_norm_any_slice is a known flaky tests which we're working to resolve (xref https://github.com/dask/dask/issues/7189). I just bumped CI

Thanks! I also rebased this on top of #7217 to try to get CI passing; can re-rebase once #7220 is in

alright, I trimmed this to just the comment typo fixes. I'll send a PR w/ the dead code removal, but defer to y'all about whether the "obsolete test" removal / random-test-seeding is worth the PR noise.

hmm this looks like a spurious failure? pip failed to resolve some dep? Can someone try running it again? (I dl'd a full log just in case)
Run<EMAIL_ADDRESS>install pre-commit
  /opt/hostedtoolcache/Python/3.9.2/x64/bin/pip install pre-commit
  Collecting pre-commit
    Downloading pre_commit-2.11.1-py2.py3-none-any.whl (187 kB)
  Collecting virtualenv>=20.0.8
    Downloading virtualenv-20.4.2-py2.py3-none-any.whl (7.2 MB)
  Collecting toml
    Downloading toml-0.10.2-py2.py3-none-any.whl (16 kB)
  Collecting pyyaml>=5.1
    Downloading PyYAML-5.4.1-cp39-cp39-manylinux1_x86_64.whl (630 kB)
  ERROR: Exception:
  Traceback (most recent call last):
    File "/opt/hostedtoolcache/Python/3.9.2/x64/lib/python3.9/site-packages/pip/_vendor/resolvelib/resolvers.py", line 171, in _merge_into_criterion
      crit = self.state.criteria[name]
  KeyError: 'pyyaml'


feat(params): network configurations via environment vars

Mainly this PR adds:

New Private network type for private or testing setups
CELESTIA_PRIVATE_GENESIS env var which intstructs private network on a node via setting genesis hash
CELESTIA_BOOTSTRAPPERS env var which sets custom bootstrappers for any network.
CELESTIA_NETWORK env var which sets the network for the node.
Closes: https://github.com/celestiaorg/celestia-node/issues/550

@jbowen93, tagging you here as you might be interested in this. I recommend migrating the ephemeral cluster to use Private Network. Also, the trusted-hash flag will soon be deprecated for Bridge Node, so migration will be required at some point.

Converting into the draft as #556 changes this a little.

@liamsi, the code must commit to such network-wide stuff.

why? Also default configs can also be considered part of the code or not?

And more: we define bootstrappers, not the user. We define genesis, not the user. Allowing users to change network-wide params we define is error prone.

I need to understand the rationale here better.

@liamsi, the rationale behind hardcoding stuff like we do already:

Genesis per network should be hardcoded because this is the only way you can have trustless sync for a node from scratch and without the need to manually get somewhere else. If you have a valid binary with genesis info inside, you have almost everything to sync reliably, the missing part is a long-range attack. (I believe we discussed this already and mentioned that Ethereum, Bitcoin and etc are doing this. Tendermint uses manual genesis doc distribution)
The long-range attack is addressed by hardcoding the set of bootstrappers. Bootstrappers in this case are not only providing us entrance to the p2p network but also peers that we(Celestia) guarantee to be honest. This is what prevents any node to be eclipsed by bots and etc, as each node has at least one honest peer to whom it maintains a connection(with celestia-node we don't have a guarantee for such connection). The important part is hardcoding the address and pubkey(peerid), so this honest connection can't be MITMed.

The rationale for env vars:

There should be a way to run private networks. Previously, when you run celestia-node you are automatically connect to some default public network. This PR preserves this behavior, but allows running the node with custom genesis for a custom private network with a custom set of bootstrappers through env. The reasons why it is through env:

For setups like Ephemeral cluster or any CI it is easier to control things from the env and a good practice. Accessing values on the config is PITA in such cases.
Config fields are available to users. It might be ok to expose them in config, but I don't see a reason why regular user would won't to run their own private network. In case it is a dev, his dev environment will use the env.

Similarly there should be a way to control the network bootstrappers for private network, thus the env var to do so.

Closed in favour of https://github.com/celestiaorg/celestia-node/pull/561


Fair benchmark with the other libraries

the augbench package needs further development and its results need to be reported in the README.
the benchmark needs to cover random transformations rather than the static ones. It is important to make comparison for three cases: image, image mask, and image+10 masks (instance segmentation task).

Closed in PR #44


Pin tab not working anymore on CE 24.1.4

Description
I just downloaded DBeaver CE 24.1.4 (version <IP_ADDRESS>408041450) on my Win 11 Home PC.
I opened a SQLite connection, wrote and ran a query, then I pinned its result.
After I wrote a different query and the result was subscribed in the pinned tab instead of creating a new one.
I attach a video I just recorded : https://github.com/user-attachments/assets/ddc2179c-5e0d-4f25-be99-7467f1269b1d
DBeaver Version
Community Edition 24.1.4
Operating System
Windows 11 Home
Database and driver
I tried with SQLite and Oracle
Steps to reproduce

I connect to a DB
I write a first query on row 1
I execute the query on row 1
I pin the tab with the result of query on row 1
I write another query on row 2
I execute the second query on row 2

Additional context
No response

Thank you for bug report.
I'm closing it as it's a duplicate of #35072
You can try Early Access version with fix (https://dbeaver.io/files/ea/) or wait for the next release


//mixer/pkg/config/crd:go_default_test  and //pilot/platform/kube/admit:go_default_test  fails on x86

//mixer/pkg/config/crd:go_default_test  and //pilot/platform/kube/admit:go_default_test  fails on x86. The above mentioned TC fail on x86.
Any update on this?

Can you copy&paste the test results?  Also which kubernetes environment are you using?
Some test cases (including those two) actually connect to a kubernetes cluster, and I see sometimes error happens during error executing access token when using GKE. In that case, running kubectl get pods will refresh the access token and retry tests.

HI @jmuk ,
I tried the baove thing. STill the TC fails
the error details are seen below
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
2017/12/22 17:33:44 http: TLS handshake error from [::1]:44774: remote error: tls: bad certificate
2017/12/22 17:33:44 http: TLS handshake error from [::1]:44776: remote error: tls: bad certificate
2017/12/22 17:33:44 http: TLS handshake error from [::1]:44778: remote error: tls: bad certificate
2017/12/22 17:33:44 http: TLS handshake error from [::1]:44780: remote error: tls: bad certificate
--- FAIL: TestServe (0.03s)
admit_test.go:370: valid: Post(application/json, {"spec":{"kind":{"group":"","version":"","kind":""},"object":{"kind":"mock","metadata":{"name":"mock-config0","namespace":"watched"},"spec":{"foo":1}},"oldObject":null,"operation":"CREATE","resource":{"group":"","version":"","resource":""},"userInfo":{}},"status":{"allowed":false}}) failed Post https://[::1]:45928: x509: certificate is valid for <IP_ADDRESS>, not ::1
admit_test.go:370: invalid: Post(application/json, {"spec":{"kind":{"group":"","version":"","kind":""},"object":{"kind":"mock","metadata":{"name":"mock-config0","namespace":"watched"},"spec":{"foo":1}},"oldObject":null,"operation":"CREATE","resource":{"group":"","version":"","resource":""},"userInfo":{}},"status":{"allowed":false}}) failed Post https://[::1]:45928: x509: certificate is valid for <IP_ADDRESS>, not ::1
admit_test.go:370: wrong content-type: Post(application/yaml, {"spec":{"kind":{"group":"","version":"","kind":""},"object":{"kind":"mock","metadata":{"name":"mock-config0","namespace":"watched"},"spec":{"foo":1}},"oldObject":null,"operation":"CREATE","resource":{"group":"","version":"","resource":""},"userInfo":{}},"status":{"allowed":false}}) failed Post https://[::1]:45928: x509: certificate is valid for <IP_ADDRESS>, not ::1
admit_test.go:370: bad content: Post(application/json, ^@^A^B^C^D^E) failed Post https://[::1]:45928: x509: certificate is valid for <IP_ADDRESS>, not ::1
FAIL
The kbernetes setup being used is of version 1.8.3
Any updates on this?

Aah, I see. So the test client tries to connect through IPv6 address [::1], which isn't covered by our test certificates.
This is a bug unrelated to kubernetes, we haven't been aware of it. I'll work on the fix. cc: @ayj


Schaaf-Yang syndrome

Mondo term (ID and Label): MONDO:0014243 Prader-Willi syndrome due to point mutation
Synonym to be added: Schaaf-Yang syndrome
Synonym subtype: ie, broad/exact/narrow/related: Unsure.
Database cross reference for the synonym Such as PubMed ID (in the format PMID:XXXXXX) or a cross-reference to another ontology, like OMIM or Orphanet.:
PMID: 24076603
OMIM: # 615547
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here
ClinGen ID/Autism GCEP

I see that it is already labeled as a synonym however, is there any way to relabel this as Schaaf-Yang syndrome with Prader-Willi syndrome due to point mutation as a synonym. Please let me know if you have any questions. Happy to discuss this further. Thank you.

@tibingaman yes, we'll do that.
Action items:

[ ] relabel term as Schaaf-Yang syndrome
[ ] add exact synonym Schaaf-Yang syndrome, add has synonym type 'clingen preferred', add dbxref: OMIM:615547, PMID:24076603
[ ] add exact synonym Prader-Willi syndrome due to point mutation, add dbxref: Orphanet:398069
[ ] add seeAlso: this ticket

@kallia-p would you be able to work on this ticket before the end of the week? We'd like to get this in for the September release. No worries if not, we can reassign. Thanks!

Is there a difference between
MONDO:0018355 Prader-Willi-like syndrome due to point mutation
and MONDO:0014243 Schaaf-Yang syndrome that I am missing?
Maybe MONDO:0018355 should be renamed to match ORPHA:398079: "SIM1-related Prader-Willi-like syndrome"   or "Prader-Willi-like syndrome due to SIM1 point mutation" so the disease doesn't start with a gene symbol ?

I added the synonym MAGEL2-related Prader-Willi-like syndrome (from Orphanet) to MONDO:0014243 Schaaf-Yang syndrome
I deprecated the synonyms Prader-Willi syndrome due to point mutation and PWS due to a point mutation on MONDO:0014243 Schaaf-Yang syndrome, as these do not appear to be used by Orphanet
I relabeled MONDO_0018355 to SIM1-related Prader-Willi-like syndrome and added the synonym SIM1-related PWLS (from Orphanet)
I deprecated the synonyms Prader-Willi-like syndrome due to a point mutation, PWS-like due to a point mutation, and PWS-like due to point mutation, as these do not appear to be used by Orphanet any longer either.


[MM-37278] Removing data retention feature flag

Summary
Removing the data retention feature flag
Ticket Link
https://mattermost.atlassian.net/browse/MM-37278
Related Pull Requests

https://github.com/mattermost/enterprise/pull/1034
https://github.com/mattermost/mattermost-server/pull/17992

Release Note
Removing data retention feature flag

Cherry pick is scheduled.

Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
From github.com:mattermost/mattermost-webapp
 * [new branch]          MM-32187-timestamp-position-deleted-message -> upstream/MM-32187-timestamp-position-deleted-message
 * [new branch]          MM-32342_remove-legacy-sidebar -> upstream/MM-32342_remove-legacy-sidebar
 * [new branch]          MM-36866-mid-month-proration-new -> upstream/MM-36866-mid-month-proration-new
 * [new branch]          MM-37118-dont-mark-channel-as-read-for-crt-reply -> upstream/MM-37118-dont-mark-channel-as-read-for-crt-reply
 * [new branch]          MM-37426_refresh-whitespace -> upstream/MM-37426_refresh-whitespace
   bd9677e7d..64c032a53  ParserOnProp         -> upstream/ParserOnProp
   d067276e3..d37d74bc4  cloud                -> upstream/cloud
   1d12f6d3b..8368e8597  fix-help-page-images -> upstream/fix-help-page-images
   05a5e9164..4b3be7efb  master               -> upstream/master
 * [new branch]          mm-37457-remove-target-blank -> upstream/mm-37457-remove-target-blank
Fetching origin
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
+++ Updating remotes done...
!!! 'upstream/release-5.38' not found. The second argument should be something like upstream/release-0.21.
    (In particular, it needs to be a valid, existing remote branch that I can 'git checkout'.)

+++ Returning you to the master branch and cleaning up.

/cherry-pick release-5.38

Cherry pick is scheduled.


Cannot set enumeration for nullptr values

Version and Platform (required):

Binary Ninja Version: 3.4.4133-dev
OS: Windows 11, x64

Bug Description:
See the GIF please. Maybe this is because I try to set enum for nullptr value? Even if it because of nullptr, I believe that this shouldn't be happening.
Expected Behavior:
I expect it to set nullptr to my enum or do not open select enum dialog for nullptr values.
Screenshots:

I wonder what happens if you use "y" to change the function parameter type instead of the UI since it looks like it's misaligned. Also, does it behave the same in HLIL as well?

If I change 4th parameter type to int (which was PSTR before) and then select enum again this is what happens:

It set enumeration value to CC_FASTCALL for both 3rd and 4th parameter. Which is also does not correct, because I just want to set it for 4th parameter. CC_FASTCALL is meaningless here, I just use it in order to demonstrate the bug.
I'm not sure what you mean by HLIL. The GIF above is from HLIL output. If you mean what happens for examples like below, it does not change value to enum, it left it as nullptr.
004174e9  void* var_650 = nullptr
004174ed  void var_648

Are you sure the gif isn't pseudo c? It shows casts in C style and it doesn't have names on the parameters.

Yes I'm sure. I disabled names for parameters. Pseudo-C always have ; in the end of statements.

I guess this is for all nullptr values. I can reproduce it for all nullptr values that I saw on function call. Let me show some examples:
Let's say I've this:
function(a, 0, nullptr, b);

When I try to select enum for third parameter, actually it sets for second parameter.
function2(a, nullptr, b);

For the example above, when I try to set enum for second parameter, nothing happens.
Another example:
function3(1, 1, 6, nullptr, 0, 0)

When I try to set enum for fourth parameter here, it sets enum for fiveth and sixth parameter.
When I try to set enum for nullptr variables (var114 = nullptr ), again, nothing happens.


Reading the QoS from entities

I have a question about the Python interface.
Is there a way to get a QoS assigned to an Entity back later?
In my code I need to get the partition name passed via QoS back from a Listener attached to a DataReader derived from a Subscriber
pub_qos = Qos([PartitionQosPolicy(['partition_name'])])
pub = dp.create_publisher(pub_qos)
listener = SomeListener()
reader = pub.create_datareader(..., listener )

...python
# now I would like to use something like this in the listener

def on_data_available(entity):

    partition_list = entity.parent.get_qos(PARTITION_QOS_POLICY_ID).to_list()

Is that possible somehow?

Yes, It is possible to get the QoS from any DDS entities.
In your case you can get the partitions name from listener by calling:
entity.parent.qos.partition.ps
Your subscriber code looks like:
subscriber_qos = Qos([PresentationQosPolicy(DDSPresentationAccessScopeKind.TOPIC, True, True), PartitionQosPolicy(['A', 'B'])])
Create participant
dp = DomainParticipant()
Create Subscriber
sub = dp.create_subscriber(subscriber_qos)
You can get the subscriber QoS here
Your on_data_available code s
def on_data_available(self, entity):
partition_list = entity.parent.qos.partition.ps
# Here I have printed partition names
print(partition_list[0])
print(partition_list[1])
With Best Regards,
Vivek K Pandey
Solutions Architect
ADLINK Technology

Dear Solar Joe,
The above feature is not available in the current OSPL community edition (V 6.9) but it is available in the current commercial edition.


Ansible Traffic_Ops role creates invalid ldap.conf config file with default variables.

This Bug Report affects these Traffic Control components:

Automation (Ansible)

Current behavior:
The ldap.conf file is rendered based on the template and ldap variables when the traffic_ops role is run. The _to_ldap_setup_ boolean variable is not used to determine if the config file should be rendered or not.  It seems that Traffic Ops Golang 6.1.0 ( and maybe older versions ) will read the ldap.conf file regardless of if the ldap.conf path is defined in cdn.conf, for perl backwards compatibility.
When running the playbook without defining any of the ldap variables ( eg to_ldap_hostname ) I end up with a /opt/traffic_ops/app/conf/ldap.conf file like this:
{
   "admin_pass" : "",
   "search_base" : "",
   "admin_dn" : "",
   "host" : "",
   "search_query" : "",
   "insecure" : 0
}

because that file is in the default conf directory, Traffic Ops Golang will read it on service start. This gives the following error:
Mar 18 12:18:43 vm024572 traffic_ops[39187]: Loading Config: parsing LDAP conf '[123 10 32 32 32 34 97 100 109 105 110 95 112 97 115 115 34 32 58 32 34 34 44 10 32 32 32 34 115 101 97 114 99 104 95 98 97 115 101 34 32 58 32 34 34 44 10 32 32 32 34 97 100 109 105 110 95 100 110 34 32 58 32 34 34 44 10 32 32 32 34 104 111 115 116 34 32 58 32 34 34 44 10 32 32 32 34 115 101 97 114 99 104 95 113 117 101 114 121 34 32 58 32 34 34 44 10 32 32 32 34 105 110 115 101 99 117 114 101 34 32 58 32 48 10 125 10]': json: cannot unmarshal number into Go struct field ConfigLDAP.insecure of type bool

I'm unsure what the array of numbers means in the error message....
When I alter the _to_ldap_insecure_ in infrastructure/ansible/roles/traffic_ops/defaults/main.yml to be a boolean instead of a number, the error changes to:
Mar 18 12:46:23 vm024572 traffic_ops[52203]: Loading Config: LDAP conf missing admin_pass field

In both situtations, the daemon does not start.
I think the ldap.conf file should not be rendered in all situation by infrastructure/ansible/roles/traffic_ops/tasks/traffic_ops.yml, and a conditional should be used instead.
Expected behavior:
The traffic_ops role, when using default ldap config should allow the daemon to start
Steps to reproduce:
Don't set any LDAP variables, so the defaults are used and then run the traffic_ops playbook.

I'm unsure what the array of numbers means in the error message....

My guess is it's printing the raw config, but it's not being coerced to a string so you're seeing byte values.


How to setup display objects with custom blendmode?

I'm using PDParticleSystem library in my as3 project: Sprite + many Shapes with blendMode="add".
How to make WebGLRenderer to use blendMode "add"? I see some javascript  objects pass blendmode parameter, but I'm not sure how to use it for Shape/pack of Shapes.
Could you help, please?

the "add" is the gl.ONE, gl.ONE

Ok, I overrided __update function for ParticleSystem:
	override public function __update(ctx:CanvasRenderingContext2D):void { 		if (/*stage && */visible) { 			var len:int = _particles.length; 			if (len) { 				var glctx:GLCanvasRenderingContext2D = ctx as GLCanvasRenderingContext2D; 				//glctx.batchFinish(); 				glctx.ctx.setBlendFactors(flash.display3D.Context3DBlendFactor.SOURCE_ALPHA, flash.display3D.Context3DBlendFactor.ONE); 				for (var i:int = 0; i < len; i++) { 					var c:DisplayObject = _particles[i]; 					c.__update(ctx); 				} 				glctx.ctx.setBlendFactors(flash.display3D.Context3DBlendFactor.SOURCE_ALPHA, flash.display3D.Context3DBlendFactor.ONE_MINUS_SOURCE_ALPHA); 			} 		} 	}
It works perfect for "gpu" mode, but "gpu batch" fails. Is there some function to make it compatible with batch mode? I tried "batchFinish()" with no success.

1 it maybe has bug.
2 I suggest you change the code to get the blender into effect
https://github.com/matrix3d/spriteflexjs/blob/master/src/flash/__native/WebGLRenderer.as#L45

i have setup display objects with custom blendmode.pls check it.

Yes, your version works fine! Thank you! )

pls give me a simple source.zip

Sorry, I was in no internet area )
You can add one line in TestBunnymark to reproduce it:
bunny.display.blendMode = flash.display.BlendMode.ADD;
This works good for "gpu" mode and no effect for "gpu batch" mode.

i have find the bug code.the blendmode use the last blendmode.
and i now have no time to fixed it.

I see! Thank you.

maybe fixed ,pls try it.

Not fixed. Blendmode applied to the previous sprite.
Try this in bunnymark example:
	public function counter_click(e:Event):void
	{
			var bunny:Bunny = new Bunny();
			bunny.display = new Bitmap(bunnyAsset);
			tilesheet.addChild(bunny.display);
			bunny.display.x = 300;
			bunny.display.y = 300;

		var i:int = 10;
		numBunnies += i;
		trace("numBunies",numBunnies);
		while(i-->0){
			bunny = new Bunny();
			bunny.display = new Bitmap(bunnyAsset);
			bunny.display.blendMode = BlendMode.ADD;

			tilesheet.addChild(bunny.display);
			//bunny .position = new Point();
			bunny.speedX = Math.random() * 5;
			bunny.speedY = (Math.random() * 5) - 2.5;
			bunny.display.x = Math.random() * 100;
			bunny.display.y = Math.random() * 100;
			bunny.display.scaleX =
			bunny.display.scaleY =
			 0.3 + Math.random();
			bunny.display.rotation = 120*(15 - Math.random() * 30);
			bunnies.push (bunny);
		}

		stage_resize(null);
	}

are you the
https://github.com/matrix3d/spriteflexjs/blob/master/src/flash/__native/WebGLRenderer.as#L51
my gpu batch work good.

can you give me this line code in chrome?
https://github.com/matrix3d/spriteflexjs/blob/master/src/flash/__native/WebGLRenderer.as#L51

and the same image the one batch just same blend

It works with all new updates! Thank you! :)


Update to latest Microsoft.Data.SqlClient preview in Sql Cache

Tracking issue for updating to latest SqlClient preview.

We're somewhat blocked on https://github.com/dotnet/SqlClient/issues/137 . I can send a PR to start off though.

Closing in lieu of https://github.com/aspnet/Extensions/issues/2156


fix the MouseEvent.prototype.button to the correct number

fixed the MouseEvent.prototype.button to the correct number, and also implemented logic for ctrl clicks and alt clicks.

@buzinas Thank you! Could you also raise a PR against dev too? That would be great thanks.

@buzinas Ignore my last message, I see you've already done it. Haha. :)


Extension causes high cpu load

eamodio.gitlens-unresponsive.cpuprofile.txt

Issue Type: Performance
Extension Name: gitlens
Extension Version: 9.4.1
OS Version: Linux x64 4.15.0-43-generic
VSCode version: 1.30.2

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Closing because this is quite old. If this can be reproduced on GitLens 10 please re-open.


fix(rekor): enable rekor search ui by default

This PR updates the operator to enable the Rekor Search UI by default.
Changes:

enable default to true
swap enabled flag to a pointer rather than a boolean, regenerated types
updates relevant tests to use the updated type
update tests that compare rekor instance objects to check specific properties instead

NOTE: I'm experiencing some failures locally for CTLog and the following for Rekor, so leaving this as a draft for now:
Summarizing 2 Failures:
  [FAIL] Rekor controller Rekor controller test [It] should successfully reconcile a custom resource for Rekor
  /secure-sign-operator/controllers/rekor/rekor_controller_test.go:219
  [FAIL] Rekor hot update test Rekor update test [It] should successfully reconcile a custom resource for Rekor
  /secure-sign-operator/controllers/rekor/rekor_hot_update_test.go:146

Ran 2 of 2 Specs in 133.229 seconds
FAIL! -- 0 Passed | 2 Failed | 0 Pending | 0 Skipped

I've run out of time today so I'll continue to look at it next week. cc @lance @osmman @JasonPowr

/lgtm

/approved

/approve


Feat: Support json running orders

To allow easy manipulation of rundowns by testing tools, allow rundowns to be represented as JSON documents.
Also adds @Julusian util library to support runtime conversion of existing rundown snapshots.

Tests on a more complex rundown failed. I made a couple of fixes. Re-requesting review for quick sanity check.


Fix Plot3D reader for walls

Addresses issue #42
The previous Plot3D reader was incorrect. This is now fixed, taking the reading loop directly from NASA's example page.
Despite the Plot3D reader being fixed, there is still a major limitation for wall input files. The current implementation uses a quadrilateral source panel (directly from Katz & Plotkin, Low Speed Aerodynamics, section 10.4.1), requiring that all points on each quadrilateral be coplanar. The implementation can be seen in https://github.com/SNL-WaterPower/CACTUS/blob/dev/src/mod/quadsourcepanel.f95#L19-L186.
Only the simplest of geometries can be meshed using such panels. Perhaps just ruled surfaces? If you can approximate your geometry as a collection of ruled surfaces, then this should be fine. But that's kind of a pain to do.
For more complex geometries, a generic rectilinear boundary element will need to be implemented. Another thought - perhaps the existing quadrilateral elements degenerate gracefully into triangular elements (when two points of the quad are coincident). Would need some testing.

@danrhouck @sakibsadman7


Select based on Model

Let's say I have code that looks like
var contactsFilter = client.For<Contact>()                 .Filter(x => x.CIF.StartsWith("473"))
And when I'm looking at the BuildReqeustFor I want it to also do a $select= based only the fields from the model. So in the model if I only have FirstName, LastName for Contact, is there an easy way to have it create the URL with the $select=FirstName,LastName instead of returning all the values without having to use .Select(x=>new {x.FirstName, x.LastName})
Thanks,
Jamie

I have the same question !!
@jamierytlewski Did you find a solution?
@object Do you have any idea how we can achieve this?

@ericcanadas I never found a solution except to do the .Select(x=> new {x.})


Enable OIDC Backchannel Logout check box doesn't  exist in Console.

Describe the issue:
Enable OIDC Backchannel Logout check box doesn't  exist in Console.  This is exist on Management console.
Console

Management Console.

How to reproduce:

Login to console and create OIDC application
Navigate to the Protocol section  try to enable the OIDC Backchannel Logout

Expected behavior:
Enable button should be available.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0] IS 5.12.0 alpha 16
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

We don't need that config to enable that flow. Adding the Back-channel logout URI is enough to enable the Back-channel logout.


Link to paragraph
https://dbalague.pages.ewi.tudelft.nl/openlabook/Chapter2/LinearCombinations.html#fig-linearcombinations-spanthreevectors2
What type of applet is this?
Interactive applet 3D
Link to applet
https://openla.ewi.tudelft.nl/applet/linear_combinations/span_three_plane
What state is the static image?
Yes, Dennis has created a static image
Static image

Requirements
None
What elements are interactive?
No response
Does this issue relate or depend on other issues?
No response
Steps to completion:

[X] assign yourself & check labels
[X] implement new applet described above
[ ] embed the image in the book (with review status)
[ ] get feedback from the math teachers
[ ] get feedback from writers
[ ] remove review status in book

LGTM

is this embedded in the book?

[ ] Add a toggle to remove vectors u, v, w

Then allowed to merge in the book -> no new review needed

[ ] need to add toggle for w


Fix outputting of <Popen> when running g

Changes
Tests: Add  G_IS_TEST`
Or else running g would be command (as expected), but followed by
output like this: <Popen: returncode: 1 args: ['git']>

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

Comparison is base (25f7d30) 71.24% compared to head (138aff7) 72.15%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
+ Coverage   71.24%   72.15%   +0.91%
==========================================
  Files           4        5       +1
  Lines         153      158       +5
==========================================
+ Hits          109      114       +5
  Misses         44       44

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


Update enzyme-adapter-react-16

I am working on a project that uses fusion-cli. We'd like to use React.memo in the project, but the current enzyme adapter does not support this. Support for this was added fairly recently: https://github.com/airbnb/enzyme/pull/1914/files but fusion-cli is using an older version of enzyme as well as enzyme-adapter-react-16

Merged as part of #766


I2c support

@szczys I have tested the code from here: https://www.engineersgarage.com/adxl345-accelerometer-arduino-i2c/
It is simple and plain thus making easier to debug and implement.

Builds successfully:
└─❯ git status
On branch i2c-support
Your branch is up to date with 'origin/i2c-support'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        .cache/
        build/
        cores/arduino/api

nothing added to commit but untracked files present (use "git add" to track)

┌───────────────────took 18ms
│.../gsoc-2022-arduino-core on  i2c-support [$?]
└─❯ west build -p -b arduino_nano_33_ble_sense samples/i2cdemo     -DZEPHYR_EXTRA_MODULES=/home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core
-- west build: making build dir /home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/samples/i2cdemo
-- Found Python3: /usr/bin/python3.10 (found suitable exact version "3.10.4") found components: Interpreter
-- Cache files will be written to: /home/dhruva/.cache/zephyr
-- Zephyr version: 3.1.99 (/home/dhruva/zephyrproject/zephyr)
-- Found west (found suitable version "0.13.1", minimum required is "0.7.1")
-- Board: arduino_nano_33_ble_sense
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.14.2 (/home/dhruva/zephyr-sdk-0.14.2)
-- Found dtc: /home/dhruva/zephyr-sdk-0.14.2/sysroots/x86_64-pokysdk-linux/usr/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: zephyr 0.14.2 (/home/dhruva/zephyr-sdk-0.14.2)
-- Found BOARD.dts: /home/dhruva/zephyrproject/zephyr/boards/arm/arduino_nano_33_ble/arduino_nano_33_ble_sense.dts
-- Found devicetree overlay: /home/dhruva/zephyrproject/zephyr/../modules/lib/Arduino-Zephyr-API/variants/arduino_nano_33_ble_sense/arduino_nano_33_ble_sense.overlay
-- Generated zephyr.dts: /home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: /home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/build/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: /home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/build/zephyr/dts.cmake
Parsing /home/dhruva/zephyrproject/zephyr/Kconfig
Loaded configuration '/home/dhruva/zephyrproject/zephyr/boards/arm/arduino_nano_33_ble/arduino_nano_33_ble_sense_defconfig'
Merged configuration '/home/dhruva/zephyrproject/zephyr/../modules/lib/Arduino-Zephyr-API/module.conf'
Configuration saved to '/home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/build/zephyr/.config'
Kconfig header saved to '/home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/build/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 10.3.0
-- The CXX compiler identification is GNU 10.3.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/dhruva/zephyr-sdk-0.14.2/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Configuring done
-- Generating done
-- Build files have been written to: /home/dhruva/zephyrproject/modules/lib/gsoc-2022-arduino-core/build
-- west build: building application
[1/163] Preparing syscall dependency handling

[3/163] Generating include/generated/version.h
-- Zephyr version: 3.1.99 (/home/dhruva/zephyrproject/zephyr), build: zephyr-v3.1.0-3166-g0b6f4c7537ba
[153/163] Linking CXX executable zephyr/zephyr_pre0.elf

[157/163] Linking CXX executable zephyr/zephyr_pre1.elf

[163/163] Linking CXX executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       44260 B       928 KB      4.66%
            SRAM:        5696 B       256 KB      2.17%
        IDT_LIST:          0 GB         2 KB      0.00%

Also tested with very minimal changes with an external library (https://github.com/Seeed-Studio/Accelerometer_ADXL345), and it seems we still have to implement a few more SErial wrappers, but otherwise I2C seems completely functional (it builds, and runs!)\


Add limbo revenge by tymq69

Song Name
limbo revenge
Artist Name
tymq69
Source
Youtube
Youtube Link
emwdbZBehEA
Direct File Link
No response
Song ID
76743
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 86084399
Downloaded: No

accept


refactor: update option page theme

Brief Information
This pull request is in the type of (more info about types):

[ ] build
[ ] ci
[ ] docs
[ ] feat
[ ] fix
[ ] perf
[x] refactor
[ ] test

Related issues (all available keywords):
Details
I am really fond of the VSCode default dark theme configs. So I implement a new theme for the option page which follows VSCode dark theme styles.
It looks like this now:

Don't know if you like this or not, just fire a PR first.
And since GitHub and Gitee token procedure will be updated, I did not correct the input component position right now.
Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA

Others

It looks beautiful.

Feel that the content and the background have a little degree of differentiation, will be more beautiful.

Feel that the content and the background have a little degree of differentiation, will be more beautiful.

I am not quite sure because VSCode setting does not have a background for main container area, this makes it consistent for different screen resolution.

OK

There is indeed no distinction made in VSCode. Since it is in VSCode style, let's focus on the original VSCode style first. Continuously make adjustments in subsequent usage feedback. I will first resolve the conflict of this PR and then merge it.

Merge conflicts.
I'm not sure if it should be a circular button or a right angled button.

And after this PR is merged, a new version can be released. @Xsy41

@wangyantong2000 I think right-angled button is good.

@Xsy41 And https://hypercrx.cn is also ready now for the repo https://github.com/hypertrons/hypertrons-crx-website , you can also start to add the content of user docs on the website.

@wangyantong2000 I think right-angled button is good.

This doesn't look like a perfect right angle, it's like a circular button with a very small radius

I am not quite sure, you can decide which style to use since the css is generated by GPT-4~

After the refactoring work on the options page is merged, you can update and modify the comments on the token related part of the FastPR process in 911 again~ And after this PR is merged, a new version can be released. And https://hypercrx.cn/ is also ready now for the repo https://github.com/hypertrons/hypertrons-crx-website , you can also start to add the content of user docs on the website.

OK, I’ll update the token-related comments for #911 after the refactoring work is merged and start adding user documentation to https://hypercrx.cn/ for the website repo.


Proposal - Add label filters for network

This is the new request change because of
https://github.com/docker/docker/pull/21270 which added network label support

#dibs

ping @thaJeztah  and @tiborvass or others if know about it.
Please let me know if this is good for this proposal

Yup, sounds good to me :+1: