Update to Chromium 129.0.6668.58

This PR updates to Chromium 129.0.6668.58.
Notes:

all-add-trk-prefixes-to-possibly-evil-connections.patch had some removals for [5766804]

fix-building-with-prunned-binaries.patch had a decent amount of new additions for existing code due to the changes in [5762356]

The safebrowsing and remove-unused-preferences-fields patches had changes due to [5783615], [5791493], [5753105], and [5730314]

The missing-dependencies patch has a new addition due to [5800779] using a base::ThreadPool function without including the header.

The enable_component_updater gn flag has been removed in [5754151]

Change log
Blog post

portable linux builds fine and runs at least on Manjaro, Ubuntu 20.04/24.04 and Fedora WS 40

portable linux also builds fine for .58

Getting a build failure when overlaid on the Debian builds:
../../chrome/browser/ui/lens/lens_overlay_controller.cc:1110:9: error: no member named 'ThreadPool' in namespace 'base'
 1110 |   base::ThreadPool::PostTaskAndReplyWithResult(
      |   ~~~~~~^
2 warnings and 1 error generated.

I'm getting the following error when building on macOS arm64:
[740/63782] LINK ./protoc-gen-js
FAILED: protoc-gen-js protoc-gen-js.dSYM/Contents/Info.plist protoc-gen-js.dSYM/Contents/Resources/DWARF/protoc-gen-js
TOOL_VERSION=1726610393 ../../build/toolchain/apple/linker_driver.py -Wcrl,driver,../../third_party/llvm-build/Release+Asserts/bin/clang++ -Wcrl,strippath,/Applications/Xcode-16.0.0-Beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip -Wcrl,installnametoolpath,../../third_party/llvm-build/Release+Asserts/bin/llvm-install-name-tool  -Wcrl,dsym,. -Wcrl,dsymutilpath,/usr/bin/dsymutil  -fuse-ld=lld -Wl,--icf=all -Wl,--color-diagnostics -Wl,-mllvm,-instcombine-lower-dbg-declare=0 -Wl,-mllvm,-split-threshold-for-reg-with-hint=0 -Wl,-cache_path_lto,thinlto-cache -Wl,--thinlto-cache-policy=cache_size=10\%:cache_size_bytes=40g:cache_size_files=100000 -flto=thin -Wl,--thinlto-jobs=all -Wl,-mllvm,-import-instr-limit=30 -Wcrl,object_path_lto -Wl,-mllvm,-disable-auto-upgrade-debug-info -Wl,-mllvm,-inlinehint-threshold=360 -fwhole-program-vtables -Wl,--strict-auto-link -Wl,--no-call-graph-profile-sort --target=arm64-apple-macos -Wl,-mllvm,-enable-machine-outliner=never -no-canonical-prefixes -Wl,-dead_strip -Wl,-no_data_in_code_info -Wl,-no_function_starts -nostdlib++ -isysroot ../../../../../../../Applications/Xcode-16.0.0-Beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.0.sdk -mmacos-version-min=11.0 -Wl,--lto-O0 -Wl,-ObjC -Wcrl,strip,-x,-S -Wl,--no-warn-duplicate-rpath -Wl,-no_warn_duplicate_libraries -o "./protoc-gen-js"<EMAIL_ADDRESS>ld64.lld: error: unknown argument '--no-warn-duplicate-rpath'
ld64.lld: error: unknown argument '-no_warn_duplicate_libraries'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

Getting a build failure when overlaid on the Debian builds:

Looks like this patch fixes it, no other compilation failures:
--- chrome/browser/ui/lens/lens_overlay_controller.cc
+++ chrome/browser/ui/lens/lens_overlay_controller.cc
@@ -9,6 +9,7 @@
 #include "base/metrics/histogram_functions.h"
 #include "base/no_destructor.h"
 #include "base/system/sys_info.h"
+#include "base/task/thread_pool.h"
 #include "base/task/bind_post_task.h"
 #include "base/task/sequenced_task_runner.h"
 #include "chrome/browser/feedback/show_feedback_page.h"

I'm getting the following error when building on macOS arm64:
[740/63782] LINK ./protoc-gen-js
FAILED: protoc-gen-js protoc-gen-js.dSYM/Contents/Info.plist protoc-gen-js.dSYM/Contents/Resources/DWARF/protoc-gen-js
TOOL_VERSION=1726610393 ../../build/toolchain/apple/linker_driver.py -Wcrl,driver,../../third_party/llvm-build/Release+Asserts/bin/clang++ -Wcrl,strippath,/Applications/Xcode-16.0.0-Beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip -Wcrl,installnametoolpath,../../third_party/llvm-build/Release+Asserts/bin/llvm-install-name-tool  -Wcrl,dsym,. -Wcrl,dsymutilpath,/usr/bin/dsymutil  -fuse-ld=lld -Wl,--icf=all -Wl,--color-diagnostics -Wl,-mllvm,-instcombine-lower-dbg-declare=0 -Wl,-mllvm,-split-threshold-for-reg-with-hint=0 -Wl,-cache_path_lto,thinlto-cache -Wl,--thinlto-cache-policy=cache_size=10\%:cache_size_bytes=40g:cache_size_files=100000 -flto=thin -Wl,--thinlto-jobs=all -Wl,-mllvm,-import-instr-limit=30 -Wcrl,object_path_lto -Wl,-mllvm,-disable-auto-upgrade-debug-info -Wl,-mllvm,-inlinehint-threshold=360 -fwhole-program-vtables -Wl,--strict-auto-link -Wl,--no-call-graph-profile-sort --target=arm64-apple-macos -Wl,-mllvm,-enable-machine-outliner=never -no-canonical-prefixes -Wl,-dead_strip -Wl,-no_data_in_code_info -Wl,-no_function_starts -nostdlib++ -isysroot ../../../../../../../Applications/Xcode-16.0.0-Beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.0.sdk -mmacos-version-min=11.0 -Wl,--lto-O0 -Wl,-ObjC -Wcrl,strip,-x,-S -Wl,--no-warn-duplicate-rpath -Wl,-no_warn_duplicate_libraries -o "./protoc-gen-js"<EMAIL_ADDRESS>ld64.lld: error: unknown argument '--no-warn-duplicate-rpath'
ld64.lld: error: unknown argument '-no_warn_duplicate_libraries'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

I think update to LLVM will solve this issue, but I am waiting for LLVM to build, or I will remove these flags (ref).

@tpearson-ssc That change is already in the PR in upstream-fixes/missing-dependencies.patch

@Cubik65536 The first argument was added because of #99289, so if the version you're building has that change then it should be fine.
The second argument was added for ios builds.  Removing both should allow you to use your current version of LLVM.

@Cubik65536 The first argument was added because of #99289, so if the version you're building has that change then it should be fine. The second argument was added for ios builds. Removing both should allow you to use your current version of LLVM.

Yeah, I've seen the LLVM Project PR. The LLVM that is building on GitHub Action now will include #99289, and I will just remove the second later.

@tpearson-ssc That change is already in the PR in upstream-fixes/missing-dependencies.patch

Sounds good.   -Igen -I../../buildtools/third_party/libc++ -I../../third_party/perfetto/include -Igen/third_party/perfetto/build_config -Igen/third_party/perfetto -I../../net/third_party/quiche/overrides -I../../net/third_party/quiche/src/quiche/common/platform/default -I../../net/third_party/quiche/src -I../../third_party/skia -Igen/third_party/skia -I../../third_party/wuffs/src/release/c -Igen/third_party/dawn/include -I../../third_party/dawn/include -I../../third_party/libyuv/include -I../../third_party/khronos -I../../gpu -Igen/third_party/private_membership/src -Igen/third_party/shell-encryption/src -Igen/components/policy/proto -I../../base/allocator/partition_allocator/src -Igen/base/allocator/partition_allocator/src -I../../third_party/abseil-cpp -I../../third_party/boringssl/src/include -I../../third_party/protobuf/src -Igen/protoc_out -I../../third_party/icu/source/common -I../../third_party/icu/source/i18n -I../../third_party/ced/src -I../../third_party/ipcz/include -I../../third_party/leveldatabase -I../../third_party/leveldatabase/src -I../../third_party/leveldatabase/src/include -Igen/net/third_party/quiche/src -I../../third_party/libaddressinput/src/cpp/include -I../../third_party/webrtc_overrides -I../../third_party/webrtc -Igen/third_party/webrtc -Wall -Wextra -Wimplicit-fallthrough -Wextra-semi -Wunreachable-code-aggressive -Wthread-safety -Wunguarded-availability -Wno-missing-field-initializers -Wno-unused-parameter -Wno-psabi -Wloop-analysis -Wno-unneeded-internal-declaration -Wno-cast-function-type -Wno-deprecated-this-capture -Wno-invalid-offsetof -Wno-vla-extension -Wno-thread-safety-reference-return -Wshadow -fno-delete-null-pointer-checks -fno-ident -fno-strict-aliasing -fstack-protector -fcolor-diagnostics -fmerge-all-constants -fno-sized-deallocation -fcrash-diagnostics-dir=../../tools/clang/crashreports -mllvm -instcombine-lower-dbg-declare=0 -mllvm -split-threshold-for-reg-with-hint=0 -ffp-contract=off -flto=thin -fsplit-lto-unit -mllvm -inlinehint-threshold=360 -fwhole-program-vtables -fcomplete-member-pointers --target=arm64-apple-macos -Wno-unknown-warning-option -mno-outline -no-canonical-prefixes -ftrivial-auto-var-init=pattern -O2 -fno-math-errno -fno-omit-frame-pointer -g0 -isysroot ../../../../../../../Applications/Xcode-16.0.0-Beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.0.sdk -mmacos-version-min=11.0 -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -DPROTOBUF_ALLOW_DEPRECATED=1 -Wenum-compare-conditional -Wno-c++11-narrowing-const-reference -Wno-missing-template-arg-list-after-template-kw -Wno-dangling-assignment-gsl -std=c++20 -Wno-trigraphs -fno-exceptions -fno-rtti -nostdinc++ -isystem../../third_party/libc++/src/include -isystem../../third_party/libc++abi/src/include -fvisibility-inlines-hidden -c ../../components/plus_addresses/plus_address_service.cc -o obj/components/plus_addresses/plus_addresses/plus_address_service.o
In file included from ../../components/plus_addresses/plus_address_service.cc:31:
In file included from ../../components/plus_addresses/plus_address_blocklist_data.h:11:
../../third_party/re2/src/re2/re2.h:223:10: fatal error: 're2/stringpiece.h' file not found
  223 | #include "re2/stringpiece.h"
      |          ^~~~~~~~~~~~~~~~~~~
1 error generated.

I got the same error on windows. I think I fixed it by removing the 're2/' part of that include. I'll post the patch later...

I got the same error on windows. I think I fixed it by removing the 're2/' part of that include. I'll post the patch later...

I also think it's that, just did it and waiting for rebuild, then it seems that it'll work...

They broke it upstream in https://chromium-review.googlesource.com/c/chromium/src/+/5772057 by directly including #include "third_party/re2/src/re2/re2.h" in components/plus_addresses/plus_address_blocklist_data.h. It builds with system re2 library just fine, but fails with the bundled one. I'm not sure we should fix this issue in ungoogled-chromium, should we?

Maybe we should include the fix in the affected repos rather this repo.

I got the same error on windows. I think I fixed it by removing the 're2/' part of that include. I'll post the patch later...

For the sake of completeness :)
--- a/third_party/re2/src/re2/re2.h
+++ b/third_party/re2/src/re2/re2.h
@@ -220,7 +220,7 @@
 #include "absl/base/call_once.h"
 #include "absl/strings/string_view.h"
 #include "absl/types/optional.h"
-#include "re2/stringpiece.h"
+#include "stringpiece.h"

 #if defined(__APPLE__)
 #include <TargetConditionals.h>

For the record, this issue doesn't occur when compiling regular Chromium so it is UGC specific. I try to follow the standard Chromium package on Flatpak as closely as possible, but only UGC has this issue with the same build configuration.
I attempted this as a workaround: https://github.com/flathub/io.github.ungoogled_software.ungoogled_chromium/pull/53/commits/fb0c3ea757a0b6ae7d5c4d6e9fb916c0b15aa427
Not sure if it will work.

I believe this is the real fix:
--- a/components/plus_addresses/BUILD.gn
+++ b/components/plus_addresses/BUILD.gn
@@ -95,6 +95,7 @@ source_set("plus_addresses") {
     "//net",
     "//services/data_decoder/public/cpp",
     "//services/network/public/cpp",
+    "//third_party/re2",
     "//ui/base",
   ]
   public_deps = [
--- a/components/component_updater/installer_policies/BUILD.gn
+++ b/components/component_updater/installer_policies/BUILD.gn
@@ -45,6 +45,7 @@ static_library("installer_policies_no_co
     "//components/update_client",
     "//mojo/public/cpp/base:protobuf_support",
     "//services/network/public/cpp",
+    "//third_party/re2",
   ]

   # Disallow depending on content.

Verified in a successful u-c test build on Ubuntu 22.04. The build was failing in two places:
obj/components/plus_addresses/plus_addresses/plus_address_service.o
obj/components/component_updater/installer_policies/installer_policies_no_content_deps/plus_address_blocklist_component_installer.o

Dozens of other source files in the tree have that same exact #include, together with that item in deps. These two instances lacked the latter.

Exactly as I suspected! Should we add this patch as "fixes" until fixed upstream?

Just out of curiosity but why does this occur only for Ungoogled Chromium? I've got identical build manifest to regular Chromium on flatpak (excl applying Uc patches) yet only UGC has this issue.

Exactly as I suspected! Should we add this patch as "fixes" until fixed upstream?

I think so. This issue affects multiple platforms, and it would be cumbersome if each one had to patch it separately.

Just out of curiosity but why does this occur only for Ungoogled Chromium?

Good question. I can confirm that (1) the regular Chromium build (on Debian/Ubuntu) does compile the same two object files at issue, and (2) the compiler command line for them has -I../../third_party/re2/src despite the dependency not being listed. Maybe some kind of transitive dependency mechanism is pulling it in at the GN level?

Yeah that's something we should add to the missing-dependencies patch.  This happens more often with ungoogled-chromium because those dependencies are sometimes indirectly supplied by something we've removed.  They really should be adding the deps they use when they add them.  I feel like they've been getting sloppier with that over the years, but the ninja upgrade showed that it was happening before as well and we just weren't aware until recently.
Would it be better to create a new PR with a -2 revision or wait to add it to the update in a couple days?

I'm fine with waiting for the next minor release.

I'm fine with it being fixed by the next release. I already have that workaround working but would rather revert it so I don't deviate too much from the regular Chromium package.

@iskunk The honor is yours to submit the PR before the next release, if you will of course :)

@PF4Public: Thanks, I've posted it at #3036. Let me know if anything needs touching up!

BTW, uazo had to do the same: https://github.com/uazo/cromite/blob/bbcb812cffa4e2815760cd7fc3e34b00b4e39ea1/build/patches/Fix-chromium-build-bugs.patch#L90-L100


Add a "compatiblewith" well-known model label

See #210
Add a "well-known labels" section to the spec and include this one in there.
ping @Fannon for descriptive text for the label.
From our notes:
-Compatibility Rules:
-Summary: The data that follows my model is also valid according to the base / extend model.

Mandatory or optional properties can be added

Here we need to be careful to not run into problems once the core spec gets more attributes, that they are incompatible with local extensions.

Optional properties can be made mandatory
Careful with mandatory: If the local model makes properties (existing or new) mandatory that are not mandatory in the base model, it can not import content that does not have the mandatory properties.
Optional properties can be omitted or removed from the meta model
Additional constraints to existing properties can be enforced (narrowing), but no broadening allowed

@duglin  - do you have added it already, as its marked Done?
If yes, should I create a PR to propose more description - e.g. in a section that describes well-known labels?

@Fannon yes it's part of https://github.com/xregistry/spec/pull/222
I added this stuff: https://github.com/xregistry/spec/pull/222/files#diff-1748a963736c86b1ae7e1139dbbffbb26f059c25811b9c4899e2e2d4a0e605a2R1991
You can either do another PR to expand on it (and run the risk of having to rebase after my PR is merged), or can just add a comment to that PR with any changes you want to make.  Up to you.

Thanks Doug! I'll try to find some time these days and would then start with a comment suggestion first.
If more things pile up, I'll consider a dedicated PR.


Jim

App is easy to use and load contacts. However the main reason for it isn’t working for me. I tried sending a message to two different iPhones under the group selection and even the single selection but in both cases was able to respond from one recipient to all three.
I have an iPhone XR that is up to date.
please help- jim

Hi Jim. There are two ways to send mass text messages in the app. One is just like a standard group message with reply all and the other is no reply all.
Use the top button to send to each contact individually and your recipients will not be able to reply to all.


[Translation] HSL in English should be HSB

Description of the problem
HSL in English should be HSB.
Propose a translation

Language
Old
New

en-US
HSL
HSB

fr-FR
HSL
HSL

Screenshot
No response

After further research, no it isn't HSB, but HSL.


Closes #241 241_allow_expressions: allow expressions

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

@bms63 , are you ok with my updates or did I miss anything?

LMTPR

???

Let's Merge this Pull Request!!

I wonder if we should wait for https://github.com/pharmaverse/admiral/pull/1846. What do you think?

We probably should wait and do them at the same time.  It is on my list of tomorrow to finish review. @zdz2101 can you also make a push to review the admiral-related PR for this issue please.

@bms63 , @zdz2101 , I have added some updates to fix the failing R-CMD check for 4.2 in https://github.com/pharmaverse/admiral/pull/1846.

We probably should wait and do them at the same time. It is on my list of tomorrow to finish review. @zdz2101 can you also make a push to review the admiral-related PR for this issue please.

Yes I agree to hold off, I'll be done with my review shortly


Segregate all Old Phone Code

Describe the problem
There is a lot of dead code associated with the old AWS Connect phone system mixed in with the new Ring Central code. It should be segregated for possible later use.
Describe the solution
Please place all of the old AWS Connect code in a folder clearly labeled as "old," "aws_connect" or something. The code may be useful in the future if we launch in Australia, so we probably shouldn't delete it.
This should happen in -web and -api.
Additional context and instructions
Add any other context or screenshots about the feature request here.

Done


Expected BioJS package folder structure?

Can we have a skeleton structure of the directory for BioJS package in its wiki similar to the one mentioned in BioJS 1.0 documentation as an example [here] (https://docs.google.com/document/d/1oS4M0EKAMre4IDERV61VVTDXJH9F-HGbHxKwNXqjWuo/edit)?
i.e. The default or basic structure of directory that we get after running this command cd <your-project> && slush biojs.

Good idea :)
Is this comprehensive?

Yes! Thank you :+1:


Add delete button for layers

What does this PR do? Why are doing this? References?
This PR adds a delete button above the layer list. Clicking the button will deleted the selected layers if there are any. Alternatively dragging and dropping onto the delete button will delete the dragged layers along with any others that are selected if the dragged layer is also selected.
Right now the deleting happens automatically. In the future we could add dialog box seeking confirmation before a delete that could be disabled in preferences.
One thing to note also is that if you delete all the layers and then try and add a new one you get an error. This behavior is true even if deleting layers directly from the notebook and should be fixed in some future PR.
One final note is that this PR also contains the drag and drop changes in PR #64 which have not been merged yet. The first 8 commits are in that PR and it should probably be merged first and then this one can be merged with only the changes relevant to the delete button.
Type of change
[Please delete options that are not relevant.]

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

[x] TestCase A Run examples.ipynb and manually interacted with the gui

Final Checklist:

[x] My PR is the possible minimum work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

My initial impulse was to have the trashicon on every button, but then I moved away from it as similar applications with layers have a single trash button, but I remain open to the possibility.
I can try deleting the weakref call and seeing if I get the same error

The independent trashcan icon seems most intuitive to me, but I would like to note that while other applications typically modify their layers in-place, we will typically be creating a new layer every time. In that scenario, perhaps making the deletion of individual layers as easy as possible should be a priority.


[FEATURE REQUEST] - no blank line after a value formatted as Task in Capture

I want to add a task with the Capture - insert after line ===== Task ======
I always get a blank line after the task. The same does not happen if i remove the "Format the value as task" option.
My capture format is {{VALUE}} {{DATE:YYYY-MM-DD HH:mm}}
I would like no blank line added after the task

I just watched the demo video earlier today and it indicated you can add a line break after your format which will get persisted into your note. You can either add a \t at the end of the line, or press the enter key. I'm not sure if this is the issue you are describing, but it might be worth referencing the video at this timestamp:
https://youtu.be/gYK3VDQsZJo?t=904

I'm having the same problem. A simple workaround is to not format as a task using the option and instead include the task formatting in your capture format, eg;
- [ ] {{VALUE}} {{DATE:YYYY-MM-DD HH:mm}}

It works exactly the same except it doesn't append a newline


Is it support to Rails 5.2.2?

Our current application using Rails 3 and we are using Puret gem for multiple languages. Now we are upgrading Rails 5.2.2 version so this Puret gem not working.
May I know, is it support or any optional for it?

Currently they are looking for maintaining this gem. I think currently you do not get full support for rails 5.


bug(a11y): sbb-form-field should support negative context

Preflight Checklist

[X] I have read the Contributing Guidelines for this project.
[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Bug type
Accessibility
It affects the following packages
Design Tokens
Which version of Lyne Components are you using
0.33.10
Operating system
No response
Browser / Browser version
No response
Input mode
None
Additional settings
No response
What happened?
If we have a dark background and want to use a form-field, we should have a light focus style when tabbing to the field.
use case (search-overlay with a negative sbb-dialog)
Steps to reproduce the issue

Step one
Step two
...

Relevant log output
No response

Hi @WalkingOS
This is probably not well documented, but wherever you set the dark background in styles, you should set
`--sbb-focus-outline-color: var(--sbb-focus-outline-color-dark);
With that, all arbitrary usage of the focus outline will be changed.

@WalkingOS : My answer was wrong!
For the sbb-form-field we don't use normal focus outline, so we need to create a special solution here for negative context. @mcilurzo, Can you think about a solution?

@jeripeierSBB at least you can give the delete-button the focus style.
I'm not sure if this the scope of this. But it seems that the cursor of the input field is not visible when the background is negative

hmm I see the cursor. In which browser you don't see the cursor?
Fix for cases like the delete button: https://github.com/lyne-design-system/lyne-components/pull/1947

@jeripeierSBB True.. in Macos Chrome/safari its working. In Windows chrome i dont see the cursor :D

@jeripeierSBB True.. in Macos Chrome/safari its working. In Windows chrome i dont see the cursor :D

At least with a remote connection to a windows computer I couldn't reproduce this. I'll have to try later. Did you also test with https://lyne-components-preview-pr1815.app.sbb.ch/iframe.html?args=&id=pages-search-overlay--search-instant-results&viewMode=story ?

negative form-fields: https://www.figma.com/file/9r6xSfNmEfCFxl1yFYedrj/Lyne-Components?type=design&node-id=140%3A23&mode=design&t=wTD4Pg1oFNHF8scT-1


Add metadata to sliced PDFs

Using exitfool? Maybe also with lualatex/pdflatex itself (https://github.com/latex3/pdfresources?)
Example:

Idea: Use JabRef to put in meta data.


Failed to exexute script...

Getting this Error when launching the exe. I suppose its because the program expects League to be installed on C Drive, which is not the case for me.
Traceback (most recent call last):
  File "multiprocessing\process.py", line 314, in _bootstrap
  File "multiprocessing\process.py", line 108, in run
  File "disabler.py", line 9, in disableNativePresence
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Riot Games\\League of Legends\\Plugins\\plugin-manifest.json'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "DetailedLoLRPC.py", line 18, in <module>
  File "PyInstaller\hooks\rthooks\pyi_rth_multiprocessing.py", line 50, in _freeze_support
  File "multiprocessing\spawn.py", line 120, in spawn_main
  File "multiprocessing\spawn.py", line 133, in _main
  File "multiprocessing\process.py", line 329, in _bootstrap
AttributeError: 'NoneType' object has no attribute 'write'

Yeah, it searches for the Riot Client and expects League to be in the same "Riot Games" folder as the Riot Client.
To fix this, you can try to manually reset the preferences:

Press Windows + R, type in %appdata%, then delete the entire DetailedLoLRPC folder.
Manually open League through Riot Client.
Open DLRPC, when it prompts you that it might not work properly if opened after League, press Yes.
Close League, then start the game through DetailedLoLRPC.

If this still doesn't work, I'll probably have to implement manual path selection.

Please let me know if it worked or not xd


Expose api so writeMessage does not create a message in a new line

Expose APIs similar to java's print() and println() so that a user can control if the messages go into a new line on the report.

Closing this as an old issue. However, any PR's to fix this will be merged.


Google Colab (demo.ipynb) crashing

After installing all requirements by,
pip install -r requirements.txt
The runtime needs to be restarted, but it's unable to restart and reconnect as runtime crashes.
Solution?

Don't install it.


Ensure all disks are deleted on destroy in Virtualbox

This PR fixes issue #59. We create an additional disk during provisioning, and we've to make sure it's deleted when destroying the VM.
Note: this fix applies to VirtualBox only, as the disk addition.
Fixes #59.

Yes. Sometimes, when you destroy and recreate VMs, you get an error after setting the VM name because the VM directory already exists.


Cannot use in Xcode 6.3.2

It can not used in Xcode 6.3.2 when i have updated Xcode from 6.2。why?
anyone who can tell me how to fix it? Thank you!
I also used command line to delete VVDocumenter-Xcode.xcplugin and reinstall it. but it can not work.

Restart your Xcode completely and load bundle


failed to run custom build command for openssl-sys v0.9.7

debian 8 up to date
cargo build --release
   Compiling openssl-sys v0.9.7
   Compiling clap v2.20.3
error: failed to run custom build command for `openssl-sys v0.9.7`
process didn't exit successfully: `/var/www/note/mysteryshack/target/release/build/openssl-sys-a41752c102bebd07/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "Failed to run `\"pkg-config\" \"--libs\" \"--cflags\" \"openssl\"`: No such file or directory (os error 2)"', /checkout/src/libcore/result.rs:906:4
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:381
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:397
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:611
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:572
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:522
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:498
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:71
   9: core::result::unwrap_failed
  10: build_script_build::main
  11: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:99
  12: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:459
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:61
  13: __libc_start_main
  14: <unknown>

I got openssl :
➜  mysteryshack git:(master) openssl version
OpenSSL 1.0.1t  3 May 2016

I'm new to rust and i could'nt find any answer on the net :(

"Failed to run \"pkg-config\" \"--libs\" \"--cflags\" \"openssl\": No such file or directory (os error 2)"

I suspect that the pkg-config command is missing on your system.
On Thu, Oct 26, 2017 at 09:09:21AM +0000, Antoxyde wrote:

debian 8 up to date
cargo build --release
   Compiling openssl-sys v0.9.7
   Compiling clap v2.20.3
error: failed to run custom build command for `openssl-sys v0.9.7`
process didn't exit successfully: `/var/www/note/mysteryshack/target/release/build/openssl-sys-a41752c102bebd07/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "Failed to run `\"pkg-config\" \"--libs\" \"--cflags\" \"openssl\"`: No such file or directory (os error 2)"', /checkout/src/libcore/result.rs:906:4
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:381
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:397
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:611
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:572
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:522
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:498
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:71
   9: core::result::unwrap_failed
  10: build_script_build::main
  11: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:99
  12: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:459
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:61
  13: __libc_start_main
  14: <unknown>

I got openssl :
➜  mysteryshack git:(master) openssl version
OpenSSL 1.0.1t  3 May 2016

I'm new to rust and i could'nt find any answer on the net :(
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/untitaker/mysteryshack/issues/72

Ok you were right ^^
Thanks the compilation ended well!


combine subspecies

like #40, but with cleaner history

@sdtaylor - can you give this a review when you get a few minutes.

does the package RPostgres work for both of you? The only one I have via CRAN is RPostgreSQL, which looks like it's exactly the same thing but with a different name.

I just used the one that was used in filter_species.  It works fine for me, except it doesn’t seem to respect my PGUSER variable.

On Apr 25, 2016, at 11:11 AM, Shawn<EMAIL_ADDRESS>wrote:
does the package RPostgres work for both of you? The only one I have via CRAN is RPostgreSQL, which looks like it's exactly the same thing but with a different name.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/weecology/bbs-forecasting/pull/42#issuecomment-214386518

working around it for now. It shouldn't be an issue once everything is switched to sqlite in #38

https://github.com/rstats-db/RPostgres

@sdtaylor would you mind reviewing this version? Thanks for the dplyr::summarize suggestion.

Thanks @sdtaylor! I changed those lines like you suggested.  Ready to merge?

Yep, looks good.


Inference benchmarks for V2: Depth anything V2

I tried to replicate the results from your benchmarks using docker gpu with this docker image nvidia/cuda:12.6.1-cudnn-devel-ubuntu22.04 and nvidia/cuda:12.1.0-cudnn8-devel-ubuntu22.04. After I install all the requirements I cannot get close to your results. The best times are around 98ms for the small model.
I used different GPUs, like: tesla-t4, a10-gpu, a100 and h100, no significant improvement
Depth anything V2 small 518x518: last results of 100 iterations in seconds
Inference: 0.0989875050000002
Inference: 0.09922104800000042
Inference: 0.10035349300000007
Inference: 0.09872460100000069
Inference: 0.09940112099999965
Inference: 0.10043860399999716
I dont know if the benchmarks you have here are from depth-anything v1.
In any case, could you share benchmarks fro Depth anything V2?
Reference from the readme.md
We observe the following average latencies using the CUDA Execution Provider:

Device
Encoder
Input Shape
Average Latency (ms)

RTX4080 12GB
ViT-S
(1, 3, 518, 518)
13.3

RTX4080 12GB
ViT-B
(1, 3, 518, 518)
29.3

RTX4080 12GB
ViT-L
(1, 3, 518, 518)
83.2

Hi @sarmientoF, thank you for your interest in Depth-Anything-ONNX.
Firstly, thanks for trying the models out on various GPUs.
Those measurements from the readme are for V2. I measure using ONNXRuntime's profiler:
sess_options = ort.SessionOptions()
sess_options.enable_profiling = True

...

for _ in range(100):
    session.run_with_iobinding(binding)

ORT will output a trace JSON file that you can open in, for example, https://www.ui.perfetto.dev/
This is the trace file I obtain when running the ViT-S model on my machine under Ubuntu WSL (it's around 70MB so I zipped it):
onnxruntime_profile__vits.zip
Discounting the first few runs (warm-up) and averaging over the latter runs, I get 12983208.33 nanoseconds or 12.98 milliseconds:

Honestly, I'm not sure where the issue is. Did you try running inference directly (without Docker)?


Refactored By creating new components

Created some new components and replaced them with the code in Upload_ReactComponent.react.js.
Please feel free to suggest more refactoring if required.
Also I didn't setup the python environment , as I was only making the changes with React.

I merged these to another branch: https://github.com/np-8/dash-uploader/tree/refactor_upload
I also continued the refactoring by merging all of the Button components (Cancel, Start, Pause) into one Button component, and tried to tidy the code a bit. There is still room for improvement but it looks much nicer now :)

Actually, planning to publish these all in the next (0.5.0) release, so merged to: https://github.com/np-8/dash-uploader/tree/0.5.0

@np-8 Thanks for reviewing and merging it. I would like to contribute more to this project. Let me know if I can connect with you or anything that you would like me to work on.


oem-ibm dump offload :Avoid Unmap of DMA on EINTR error

These changes will handle the case where host crashes in the
middle of outofband DMA transfer during system dump offload.
When the host crashes during the DMA transfer,
PLDM receives EINTR(interrupt) and it unmaps the memory.
XDMA driver doesn't know that the operation is interrupted,
it still thinks that operation is in progress.
munmap will hang if xdma driver thinks the operation is in progress.

Can one of the admins verify this patch?

Fixes  https://w3.rchland.ibm.com/projects/bestquest/?defect=SW553074


Unavailable debugger with multiple game instance

Godot version:
3.0
OS/device including version:
MacBook Pro 13-inch 2017 (10.14.1 Mojave)
Issue description:
Unable to debug with two instance of godot: client and server. Which is very very very useful when creating networking multiplayer game.
This is a known issue since 2016 but may be forgotten: Godot QA.
In one editor, we can't open more than one game.
If we run two editors, the last game window opened can't connect to the godot debugger.
(For those who don't know how to run multiple instance of a programme in Mac: open -n -a <program in apps or .app file>)
There is an error message in the last editor which launch the game: Error listening on port 6007.
May be the problem is due to the listening port which is the same for all godot editor instance/window.
Could you think is it possible to start an available port discovery to start the godot debugger and game with the same available port, we could so run multiple game instance for client/server ?

Yeah, seems like a duplicate of #20020. Closed.


Epic: Remove _existing state from Fluid Framework (container, data store, DDS)

At container, data store & DDS levels we have notion if "existing" which tells those layers if layer was loaded from storage (exists in a file/document) or was created locally.
There are multiple design problems with it:

First, the notion of "existing" is short-lived, vs. property being available all the time. This is means that it's very likely to be either incorrect or used incorrectly through lifetime of the layer
Code uses it to infer other type of information. this inference becomes incorrect over time as we design and build new workflows. The too latest examples are detached container, and serialization & de-serialization of detached container. In later case, we have to mimic as if layers are not existing (as they are locally created, with no delay loading required), yet other parts of the code using existing flags needs to be changed to load state from local snapshot.

Much better direction is to align all the code that uses existing with one of the following

In places where we pivot on creation, move / split code into creation and loading paths. These paths are becoming explicit paths across all layers
In places where existing flag is used to infer some other knowledge, use more appropriate and more explicit signals (might need to add them), like detached vs. not detached (container, data store, dds).

I'd suggest to use this issue as a root, and create child issues for each individual layers.
Given that most of the latest work happens at container level, I'd start there, and move downstream.

[ ] https://github.com/microsoft/FluidFramework/issues/7223

Relates item - #6033
@andre4i , assigning to you. This item needs to be broken into individual work items (i.e. instantiateRuntime(), creation of Data store, creation of DDS).

@andre4i, that's an old issue, and I'm not sure what's left here.
Is there anything that @kian-thompson can help with? Like scoped task that is clearly defined that he can learn from and complete?

@tyler-cai-microsoft recently created this issue - https://github.com/microsoft/FluidFramework/issues/9646 which is kinda related.

Duplicate of 363


Self-dismiss or cue next on a timer

In some situations it would be a better user experience if the popover would self-dismiss (or go to the next step) after a specified time interval. To get this behavior, I am playing with some combination of adding a custom property to the step and using onPopoverRender. It would be a nice addition to have this in the API though.

Thank you for the suggestion but to keep the bundle size smaller there are no plans to add that.


fix single cell portal donwload links and paths

@felix0097 I stumbled across some dataloaders in sfaira which rely on data from the broad single cell portal. given that download from there cannot be done by sfaira automatically (portal requires manual login), this needs to be stated in the download url. otherwise sfaira will crash when it's asked to download data for these dataloaders.
I have also adapted the loader paths as it seems like these relied on manually created subdirectories. I guess we want files to all be in the toplevel datadir.
do these changes look good to you or did I miss something here?

looks good to me, but didn't test the data loaders myself

With these, I tried to put the bulk download link to the collection on SCP (there is a bottom on the top on that page somewhere where you can download all data, but I couldnt link that) in as the download link to make manual download easier and then point to the decompressed files in the loader, i think in this case this makes sense as we wont get around private downloads for this portal, ie you only have to visit the site of each collection once and press one bottom. So I would keep as is but prefix private to the exisiting URL and maybe add this in the data usage documentation on read the docs?

Ah I see! Didn't see the bulk download button before.
I'd be a bit reluctant to introduce an entirely download workflow for the SCP as it's not a mjor source of datasets for us. I feel like we're buying potential ease of use with quite a lot of potential confusion if the download procedure is no longer self-explanatory but rather has special cases which are documented separately.
Additionally we're not usually requiring all the files form the SCP and running wget on say up to 6 download inks seems feasible as these datasets are a bit of edge case anyways.
So not sure introducing this extra complexity is worth it but I'm of course happy to be convinced otherwise.


[FEATURE] Full resource name security for OpenSearch entities: Templates, Aliases, Pipelines

Is your feature request related to a problem?
We're implementing security configurations for OpenSearch based on database as a service approach.
So we allow every user to work with indexes it owns, in our cases which start from {username} prefix.
For example, user1 can create/update/write/read to index user1-test, but can't to user2-test.
We reached it with the role:
{
  "admin_role" : {
    "reserved" : false,
    "hidden" : false,
    "cluster_permissions" : [
      "cluster_composite_ops",
      "indices:data/read/scroll/clear",
      "indices:admin/index_template/put",
      "indices:admin/index_template/get",
      "indices:admin/index_template/delete"
    ],
    "index_permissions" : [
      {
        "index_patterns" : [
          "${attr.internal.username}*"
        ],
        "allowed_actions" : [
          "indices:*",
        ]
      },
      {
        "index_patterns" : [
          "*"
        ],
        "allowed_actions" : [
          "indices:admin/resize"
        ]
      }
    ],
    "tenant_permissions" : [ ],
    "static" : false
  }
}

We previously faced an issue, that it is not possible to strict creating aliases with specific name, but it's not critical, because created alias can't linked with index of user don't have permission to.
Most important problem that we can't configure granular security for Index Templates.
We would like user to create only Template with allowed name ({username} prefix), and specify "index_pattern" only indexes, allowed by security pattern ({username} prefix). But now OpenSearch security requires to add template cluster wide permissions and there are no granularity for name pattern.
What solution would you like?

First of all I think we need additional configurations for Roles, targeted to Templates, Aliases and Pipelines (probably I missed something else).
Something like:

"index_permissions" : [
      {
        "index_patterns" : [
          "${attr.internal.username}*"
        ],
        "allowed_actions" : [
           "indices:*",
        ]
      }
  ],
"template_permissions": [
  "template_patterns" : [
          "${attr.internal.username}*"
        ],
        "allowed_actions" : [
          "template_all"
        ]
      }
  ],
"alias_pemissions": [
  "alias_patterns" : [
          "${attr.internal.username}*"
        ],
        "allowed_actions" : [
          "alias_all"
        ]
      }
  ]

And when user tries to access entity with some name it should be checked with granular permissions, not cluster.

There should be validation for Index Templates for index_pattern field to allow user to create templates only with index pattern they have an access (covered with their role).

Do you have any additional context?
Created after discussion Add any other context or screenshots about the feature request here.

[Triage] Hi @mrMigles, thank you for filing this issue. Without seeing additional details in the form of either a pull request or design draft, it is not clear whether this feature is something the security plugin is able to support long term. If you would like to contribute towards either of these, that could help bring the maintainers towards a conclusion about this request.
Thank you.

Hi @scrawfor99,
I created this Feature request to understand is in interesting for OpenSearch community or not and to find someone who also needs such feature. If this requirement corresponds the targets of OpenSearch security evolution I think we consider the development from our side and prepare Pull Request.
Thank you!

[Triage] @mrMigles It looks like there is some interest on this issue. If you have any high level design for this feature it would be helpful for the maintainers when reviewing this feature request.

I've got a prototype for resources permissions [1] to be used in conjunction with a new feature from OpenSearch call Views, maybe you can see how that case aligns with the scenarios you are considering.
  ...
  resource_permissions:
    - resource_type: "view"
      resource_ids: ["songs", "albums"]
    - resource_type: "search-template"
      resource_ids: ["top-billboard-songs"]

[1] https://github.com/peternied/OpenSearch-1/pull/139


Fieldset legend class configuration

I'm not sure if I just could not find it or if it is indeed something that I'd consider to be a missing thing, so I though I just put it up here and see what happens.
Right now, the formtastic configurations and custom input class possibilities allow for customizing almost anything, which is great. What I am currently looking for is an option to define a default class for the fieldset/legend that is being generated.
<%= f.inputs "My fieldset title" do %>
  ...
<% end %>

The code above will render the following:
<fieldset>
  <legend>
    My fieldset title
  </legend>
  ...
</fieldset>

As my SCSS is BEM-oriented, a configurable option to give it a default class would be very nice. There are already options in the initializer for various things like Formtastic::Helpers::FormHelper.default_form_class. Maybe something along these lines for a default legend class would be an option? I'm not sure if this would collide with the fieldset that is generated for e.g. a checkbox collection, though.
If there is already a way to modify this part, I'd happy to get a hint.

I know it is a poor substitute, but could you create your own semantic form builder and override:
https://github.com/formtastic/formtastic/blob/60fb31ea55af13b8f568673755588578514d59e1/lib/formtastic/helpers/fieldset_wrapper.rb#L51-L57
And the same applies for fieldset/ol https://github.com/formtastic/formtastic/blob/60fb31ea55af13b8f568673755588578514d59e1/lib/formtastic/helpers/fieldset_wrapper.rb#L24-L49
Maybe give it a try in your app and see if that fixes the problem for you.
Possibly the solution could be to make it easier to modify these methods and make them a bit cleaner.

Thanks, this works so far!


creating a process in the ui renders the project un-exportable

While investigating dataset stuck in export ticket ebi-ait/hca-ebi-wrangler-central#869 @MightyAx and @amnonkhen found the following bug:
Creating a new process or biomaterial via the UI creates the relevant entity but does not properly connect it to the project entity, because it does not add it to the projects attribute.
During export the contents of the projects attributes is read, but processes that were created in the UI it is empty. This results in a failure to export, which is evident by an error message of "index out of range error" in the exporter log.

@MightyAx retest it in staging

Pre-fix test case, Projects list for Process created from the UI is blank:
processes/62ea957ed9314d329d7b8bd2/projects
Post-fix test case, Projects list for Process created from the UI is populated:
processes/62f0daa1e5248105fb1b031b/projects


Multiple rows matching is only checked when there is an UPDATE clause

  def multipleSourceRowMatchingTargetRowInMergeException(spark: SparkSession): Throwable = {
    new UnsupportedOperationException(
      s"""Cannot perform MERGE as multiple source rows matched and attempted to update the same
         |target row in the Delta table. By SQL semantics of merge, when multiple source rows match
         |on the same target row, the update operation is ambiguous as it is unclear which source
         |should be used to update the matching target row.
         |You can preprocess the source table to eliminate the possibility of multiple matches.
         |Please refer to
         |${generateDocsLink(spark.sparkContext.getConf,
        "/delta-update.html#upsert-into-a-table-using-merge")}""".stripMargin
    )
  }

Checking multiple rows matching is to avoid updating the same target row in the Delta table. So for delete only clause (without update clause), we should not throw this exception.

To further optimize, in delete only case, we can use
val touchedFileNames =
      joinToFindTouchedFiles.select(col(FILE_NAME_COL)).distinct().as[String].collect()

to get touchedFileNames instead of
 val touchedFileNames = touchedFilesAccum.value.iterator().asScala.toSeq

This can prevent using accumulator to save Spark driver memory.

Gentle ping @tdas @zsxwing @jose-torres @brkyvz

@tdas could you help to rerun the CI?

The ci seems to be running into some weird issue. Thats okay, I will run our internal tests before merging. I am on it.

Gentle ping @tdas

Hey your PR has been merged internally, we just haven't pushed out the changes to this OSS repo in a while. Thats our bad. For you there is nothing left to be done in this PR. When we push the changes out, this PR will close automatically.

Thank you @tdas


Walking distance not reduced by overheat penalty, but sprint is

Rince WindToday at 5:40 AM
Walking distance not reduced by overheat, sprinting distance is.

RogueLogs.zip

Nothing in the logs that indicates why this is, and cannot replicate locally. Always works as expected for me.

mech_can_walk_farther_than_run.zip
Another report from Figing...

Okay. I've spent some time investigating but I don't see what the root cause is here.
I've added the logs to https://github.com/BattletechModders/CBTBehaviorsEnhanced/issues/75
GitHub
Walking distance not reduced by overheat penalty, but sprint is · I...
Rince WindToday at 5:40 AM Walking distance not reduced by overheat, sprinting distance is.
Only thing I know to do is add some logging around the path recompute and see if I catch it there. It sure seems like most everything except the walk path realizes what's going on. Maybe a conflict with the melee mover transiples


LibWeb/Bindings: Some simplifications for item lookup

I was looking into some possible minor perf improvements in PlatformObject by saving some lookups on named items or indexed items. E.g, by converting 3 lookups to look up a named item from a platform object into a single lookup.
This doesn't do all of that, but does make some simplfiications on looking up those items, e.g:

Removing uneeded exception handling (no exception can be thrown)
Remove is_supported_property_name for all legacy PlatformObjects
Making return value of named_item a bit more clear
For a net loss of code

Sitting ontop of https://github.com/LadybirdBrowser/ladybird/pull/823 as that was made just before I finished off these changes.

This has conflicts.

This has conflicts.


[main] Upgrade to latest dependencies (#125)

upgrade to latest dependencies
bumping knative.dev/eventing 5168dc3...3ef831c:

3ef831c Increase expiration buffer time of OIDCTokenProviders cache to 5 minutes (# 7355)

Signed-off-by: Knative Automation<EMAIL_ADDRESS>

OCF Webhook is merging this PR

OCF Webhook is merging this PR


Panic if container is set to linkerd-proxy

Bug Description
The following is thrown when trying to impersonate a linkerd2 proxy:
thread '<unnamed>' panicked at 'failed to set environment variable `""` to `"\n-----END CERTIFICATE-----\n"`: Invalid argument (os error 22)', library/std/src/env.rs:353:9

I did not expect it to be supported, but this panic is definitely unexpected.
Steps to Reproduce
mirrord exec -a foo -n foo -c --steal --no-fs --pod-name foo --impersonated-container-name linkerd-proxy ...
Backtrace
stack backtrace:
   0:     0x7fd4546df734 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h2f4d863594a68c91
   1:     0x7fd45395f030 - core::fmt::write::h9fd78932fc37b51c
   2:     0x7fd45466f99b - std::io::Write::write_fmt::h6066f9f8807a65d2
   3:     0x7fd4546e47dd - std::panicking::default_hook::{{closure}}::h9412e92c58f99121
   4:     0x7fd4546e3f3a - std::panicking::default_hook::h1a8b46d36ee22d51
   5:     0x7fd4546e6308 - std::panicking::rust_panic_with_hook::he6adbff8aae13c88
   6:     0x7fd4546e5cd1 - std::panicking::begin_panic_handler::{{closure}}::hc2cade6d6762c671
   7:     0x7fd4546e5b3c - std::sys_common::backtrace::__rust_end_short_backtrace::h2a054ca94f99dcb2
   8:     0x7fd4546e5b1a - rust_begin_unwind
   9:     0x7fd453959082 - core::panicking::panic_fmt::h5894a80f27bddaf0
  10:     0x7fd4546c26e9 - std::env::_set_var::h9c4eed906eefa7f1
  11:     0x7fd45411d539 - std::env::set_var::h0c06ee08d1d49102
  12:     0x7fd453f3f85c - mirrord_layer::start_layer_thread::{{closure}}::h1b1ea585a7f14cb4
  13:     0x7fd454267430 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::haa1c7c1cefc58899
  14:     0x7fd4538c6bb6 - tokio::park::thread::CachedParkThread::block_on::{{closure}}::h66149ca45b5c4bf6
  15:     0x7fd4538c2460 - tokio::coop::with_budget::{{closure}}::h418e4c271f67103c
  16:     0x7fd45411fc62 - std::thread::local::LocalKey<T>::try_with::h0064b8e26f46e3ea
  17:     0x7fd45411fb38 - std::thread::local::LocalKey<T>::with::hdfe826b7346f6211
  18:     0x7fd4538c39b8 - tokio::park::thread::CachedParkThread::block_on::h0d087d3389eed450
  19:     0x7fd4541925a7 - tokio::runtime::enter::Enter::block_on::h3d00830d6f179576
  20:     0x7fd4542eaa8a - tokio::runtime::scheduler::multi_thread::MultiThread::block_on::hd64c90dda3e0aae6
  21:     0x7fd453fe54b1 - tokio::runtime::Runtime::block_on::hba8d1dca2d91fffc
  22:     0x7fd453f09d87 - mirrord_layer::init::hb3c48f01a5682cee
  23:     0x7fd453865746 - mirrord_layer::init___rust_ctor___ctor::init___rust_ctor___ctor::hc683bd277cd85a44
  24:     0x7fd454f9ccee - <unknown>
  25:     0x7fd454f9cddc - <unknown>
  26:     0x7fd454fb36a0 - <unknown>

Relevant Logs
No response
Your operating system and version
Linux 5.19.7-arch1-1
Local process
a rust web server
Local process version
No response
Additional Info
No response

I think it might be related to https://github.com/metalbear-co/mirrord/pull/387
We'll try to test it, but if you want to compile from master (it's already merged) and test it out let us know :)

It does not seem to be fixed by that, I'll try to see what the issue is exactly.

@tamasfe sorry I missed out that the patch is in the agent, hence even if you recompile it won't work as long as you use the remote image (which you probably did). I hope we'll release another version today so you can see if it works (it seems to have reproduced and fixed on our checks so you should be good!)

Thanks, indeed I haven't built the agent. I'll try again after the release.

@tamasfe The new version (3.0.3-alpha) is out, if you get a chance to test it let us know :)

Thanks! It seems to start up as expected.


no_std support

It would be nice to make this library compatible with no_std environments. I think it would just require guarding some modules behind a feature flag and replacing references to std with core and alloc. I don't think there's much of a need for dedicated buffer structs for this use case. no_std users could use audio::wrap::sequential/interleaved on plain arrays to make use of the Buf/BufMut traits.

Oh, this is already implemented. :smile:  Just not documented.


Streamlit sidebar

close #69

@KarinDuong could you share a screenshot?

Thanks. Could you please avoid the bold font and output only the first 6 characters.

6 charaters for both ? Because it will be 2024-0 and 116b9e

Or you want something like that :

6 characters, only for the hash (we usually print the 6 first characters)

@KarinDuong are we ready to merge?


Post Process Task is triggered on Test

When testing a dataset it appears the server is also running the post process task.  This may not be correct based on the post process task.  For example the carto post process task will create a new dataset based upon the pluto dataset.  At best case this will fail because the pluto dataset doesn't exist.  At worst case it may actually modify the carto dataset without performing the pluto upload.
This should either be blocked on test or the user should have the option to specify if it can be triggered on test.

For simplicity I changed the code so that post tasks are not run during a test.


Minor spelling corrections

Corrected letter transpositions, and capitalized Alt+Tab for consistency (all other key names were at the beginning of their respective lines, so were already capitalized, but on my Surface Book all modifier keys and Tab are capitalized)

Merged, minus corrections that were done in previous PRs.
Thank you for the contribution!


Bug: Printing if statement inside bracketless if-else

See https://github.com/benjamn/recast/issues/416
Same issue with escodegen.generate(ast)

That is not a program.

I am confused. What is not a program?
Is escodegen only intended for code rewrite and not AST modification?

The AST you referenced does not represent a program. What program do you think it represents? If you add the curly braces you suggested in the linked issue, that is a different AST. We could possibly throw when passed non-programs, but it would make the common case slower, so :-1:.
Try using esvalid before passing the AST to escodegen so you know what you get from escodegen is meaningful.

Thank you for that hint.

I think mentioning in the readme that escodegen accepts any program without warning would be helpful.

@adiba I agree. Would you like to send a PR?


The function 'Redefine_nn' doesn't make the network follow LRP rule

When I debug the program, I find that whether I comment out the below code or not

I got the same relevance in the function 'relprop'

But this result doesn't meet the expectation, which we will get different relevance after redefining the network in terms of  LRP rule. So I think the function 'redefine'  doesn't work following expection.


rename modules to replace 'akka' with 'pekko'

aim is that all the akka-* jars will become pekko-* jars

Could I argue that the "commands" used to make these changes,  that result in "massive commits", should be checked in as a script in a commit before the actual rename, so that:

The script can be reviewed instead of the change
The script can be applied to check that the rename commit result matches the script execution

@pjfanning Since https://github.com/apache/incubator-pekko/pull/20 is abandoned, are you going to recreate it or should I? I was also thinking of rather than renaming the modules from akka-* to pekko-* (i.e. akka-actor to pekko-actor) that instead we should just have the module name without pekko (i.e. akka-actor would just become actor).
The reasoning is the same as renaming akka-docs to just docs, i.e. its extra/unneeded noise and its also not consistent with the other pekko repo's (i.e. alpakka doesn't have akka- prefix for each of their sbt modules). Since we are renaming the sbt modules anyways there isn't going to be any extra noise, only thing we need to do is to make sure to add the pekko- prefix in the generated jar which is quite easy.

@pjfanning Since #20 is abandoned, are you going to recreate it or should I? I was also thinking of rather than renaming the modules from akka-* to pekko-* (i.e. akka-actor to pekko-actor) that instead we should just have the module name without pekko (i.e. akka-actor would just become actor).
The reasoning is the same as renaming akka-docs to just docs, i.e. its extra/unneeded noise and its also not consistent with the other pekko repo's (i.e. alpakka doesn't have akka- prefix for each of their sbt modules). Since we are renaming the sbt modules anyways there isn't going to be any extra noise, only thing we need to do is to make sure to add the pekko- prefix in the generated jar which is quite easy.
Should also do this after #35 gets merged so as to not deal with a lot of merge conflicts.

I'd prefer to keep the dir names for the modules to match the jar names. And I think the jar names should be like 'pekko-actor', etc.

I'd prefer to keep the dir names for the modules to match the jar names.

Right, but this is only the case for core akka, every other akka repo does not follow in this. In fact arguably from what I have seen in standard OS SBT projects, this isn't really idiomatic either.

And I think the jar names should be like 'pekko-actor', etc.

This would be unchanged even with my suggestion, in fact its very easy to do this with SBT.
Would you be more open if I created a PR demonstrating this? Its actually not that hard.

sure, try it out

I guess this is what #71 is about.

#71 is merged


Update rebar.config to reflect erlang.mk

Rather simple patch that tries to bring master into order with what erlang.mk requires in versions.

I know there's warnings, but I can't do anything about that. Soon that file will be entirely generated, and I don't have that kind of information to fill it in. So merging this now to remove it a couple weeks later doesn't make much sense.

It's now in sync and will stay in sync because the file is now generated. Thanks!


Quotes aren't smartly replaced when used in #Requires statements.

I noticed quotes aren't smartly replaced when used in #Requires statements.
Steps to reproduce
Look at the following lines. Note that the double quote chars probably don't need to be used on that first line, but I don't think it's an error to use them. And when they are used, they should be processed properly by PSScriptAnalyzer.
#Requires -Modules "Az.Accounts"
#Requires -Modules @{ ModuleName="Pester"; RequiredVersion='4.9.0' }

Expected behavior
I had expected the double quote chars to be replaced by single quote chars, like this:
#Requires -Modules 'Az.Accounts'
#Requires -Modules @{ ModuleName='Pester'; RequiredVersion='4.9.0' }

Actual behavior
The quotes remain unchanged.
#Requires -Modules "Az.Accounts"
#Requires -Modules @{ ModuleName="Pester"; RequiredVersion='4.9.0' }

It seems PSScriptAnalyzer treats #Requires lines as mere comments and doesn't process them.
Environment data

> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.17763.5830
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.5830
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

> (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() }

1.22.0
1.22.0

I like the idea of this - but it could be a difficult one to implement.
The way the majority of the rules work within PSSA is that they analyze the Abstract Syntax Tree and not the source files directly.

That indeed sounds like a lot of work. To be honest, the whole #requires syntax makes it seem it isn't really part of the Powershell language. Like it's more of a meta language thing, like pragma pre-processor instructions in C. I wonder why they chose to implement it this way.
Based on your answer, it seems the best way would be for the Abstract Syntax Tree to have better support for #requires statements. And the alternative would be to create some hack/workaround in PSSA that parses #requires statements for this use case, right?


RC.6 issues

I m using angular-cli 1.0.0-beta.11-webpack.8 and RC6.
I get this console error:
select.component.js:15 Uncaught TypeError: core_1.Provider is not a constructor
thee are the code lines:
exports.SELECT_VALUE_ACCESSOR = new core_1.Provider(forms_1.NG_VALUE_ACCESSOR, {     useExisting: core_1.forwardRef(function () { return SelectComponent; }),     multi: true
any idea what is going on?
Thanks

My guess is that this breaking change occured in RC6:
`core: These forms of providers are no longer accepted:
bind(MyClass).toFactory(...)
new Provider(MyClass, toFactory: ...)
We now only accept:
{provider: MyClass, toFactory: ...}`

Sorry, at the moment I cannot have a look at it because I am on vacation. I will do this as soon as I get back (in about two weeks).

Will also need to update the peer dependencies
<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>and RC6 uses<EMAIL_ADDRESS>

The update to angular 2.0.0, the updated dependencies, and @dipolediamond 's fix should resolve the issue.


add async parameter to compiled webpack file

My file is getting compiled and loading fine with following configuration:-
{% load render_bundle from webpack_loader %}
{% render_bundle 'main' %}
{% javascript 'wlhome'  %}

However when I change it to following to add async behavior its not loading on the page:-
{% load render_bundle from webpack_loader %}
{% render_bundle 'main' 'js' 'DEFAULT' attrs='async charset="UTF-8"' %}
{% javascript 'wlhome'  %}

Can you please help me on this?

was just going over the code, looks like attrs feature is added in the updated version, once I updated my version its working fine. Closing the issue
P.S: its documentation it should be "charset" instead of "chatset" under attrs right?


Make drawer scrollable

Is there any methods to make this drawer scrollable ? Thanks for help.

I have just found that you just have to set height:100% and overflow:scroll


Improved math alignment documentation

In order to improve math alignment documentation (Issue #2496 ), I added another example aiming to demonstrate how alignment works when there are multiple &s in each line and also when there are differing numbers of &s in each line.  This should help users who were previously confused about how alignment works.

Thanks! I wanted to reword the text a bit, but I'll do that in a separate commit alongside some unrelated improvements.


MINOR:Delete unnecessary comment information

Delete unnecessary comment information：SnapshotWriter.createWithHeader()

@showuon  PTAL, thanks.

@socutes , sorry that I didn't catch the issue that @dajac mentioned. Please update the PR. Thank you.

@showuon @dajac Thanks~.  fixed


New loader image

Please, replace original Electron's loader image / animation:

With static company logo:

Source file (linked above) is rectangle, but (if possible) make our loader square. Pure white company logo on black text.
As for the dimensions, this doesn't matter really. You can use the same as original Electron's loader has, slightly bigger or our logo's original images. Please, make some tests and decide.

We stopped using squirrel, so there is no such loading screen right now. Closing.


Run checks without formatting on CI but with formatting on local

I would like to run the check (without formatting) on the CI, but still run the check and format  locally.
Is it possible to do it without  a custom detekt.yml file?

Is it possible to do it without a custom detekt.yml file?

Why this would be a problem? Is actually the easiest way that comes to my mind to address your scenario.

You can also specify multiple config files and have the different configuration options in a separate file.
Please take a look at the following config option copied from here.
--config, -c
  Path to the config file (path/to/config.yml).
  Multiple configuration files can be specified with ',' or ';' as separator.

@tallnato hey, with the newer detekt versions RC15+ you can have two detekt tasks, one with autoCorrect one without. Please take a look at our build.gradle.kts file for examples on adding additional detekt tasks.


Create version release tag v0.1.0

There has been a "maint" branch for a few weeks now, and its been collecting fixes. However, we need to tag-off the inital maint branch for a formal v0.1.0 release. This means going through all of the subprojects and tagging them as well, and making sure the branches have propgated correctly with the git subtee usage.

https://github.com/pothosware/pothos/wiki/Releases


Wrote the test for ReLU function

Wrote the Test for ReLU function

test_Relu() function too big. Can be optimized to fewer lines.

Okay, will revert back with it.

Have Optimised it now by shortening the code.

LGTM.

@SomshuvraBasu Some lint errors are present in your code.
Always check if you python code is formatted correctly by running the flake8 utility. To check details of why your code is failing see this.


bin: rm

remove bin
remove stream api
remove docs

Probably need to improve the docs after this && clean up some of the internals as being done in #29
Closes #33

looks good to me. :+1:

awesome! Merging but not releasing quite yet; probably best to publish milestones/transform-only in a single go


NONE: Remove unused function

Build has failed because of a flaky test. I have found the cause, will send a PR (non-deterministic variable checking because of the map iteration order).


[AutoPR mediaservices/resource-manager] [Hub Generated] Review request for Microsoft.Media to add version stable/2018-07-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6143

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/5516


effects keyword to describe side-effects

A way to describe side-effects in prose for documentation purposes, e.g.:
log(value) => Void, effects( log to console )

You can spread the description over multiple lines:
log(value) => Void, effects(
  log to console,
  POST to logging server
)

This would be spicy 🌶


[Bug] Previews not working when it jumps to next episode

The previews work perfectly when i explicitly open a specific episode and the previews are shown for that exact same episode but when it finishes playing and jumps to next episode, previews does not appear.
For example, here I opened an item S01E02 (works):

But when I open S01E01 and then jump to/let it finish playing and start the next episode (does not work):

(Occurs on both web client as well as jmp)

From my testings, I found that GetBif is not called in subsequent episodes:
S01E01 (opened directly so it got called):

S01E02 (after jumping from S01E02 so not directly opened):

As you can see from this, GetBif is not called on the subsequent episode when jumped. Gets called when directly opened though
https://user-images.githubusercontent.com/98979876/184525276-069b1d79-2690-466e-bcad-bc31b78ee413.mp4

Yeah Ill try to fix this soon. Looking to rewrite a good bit of the client script

Fixed by https://github.com/nicknsy/jellyscrub/commit/c5720a285e1d08ccfef4b80886976948b10f8d9c

Fixed by https://github.com/nicknsy/jellyscrub/commit/f69f784889063ce5b3ea7d1e5ce674e8af32ed23


Add  functionality to export answer(s) to clipboard as markdown

Feature details
I've never built an Alfred Workflow, but I'd like to take the content of an answer and copy into markdown... Is this idea a logical idea for Alfred?
Is this something one could develop as an extension to your workflow?

You can already copy the workflow’s answers as Markdown. Shortcuts are in the documentation and at the bottom of the window.

apologies... I didn't even try it and I assumed it wasn't markdown.


BBQueue object is not safe to move after splitting

If the BBQueue moves after you have split, the Producer and Consumer will point to bad data. Producer and Consumer should probably take references to BBQueue to prevent this, or BBQueue should be Pin or something.
This is not an issue if you use the bbq!() macro, or Box methods.

This will be addressed by 0.4.0, see #37


High frequencies get cut?

Hey there!
Kudos for the project – the results are pretty impressive already!
However, I noticed the default 2-stem model and the 5-stem model seem to cut higher frequencies from the material, like a (Nyquist?) knife really. I ran spleeter on a certain US pop star's song about temperature differences, i.e.
spleeter separate -i hot_n_cold.wav -o . -c wav

where hot_n_cold.wav is a pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s stream, then jury-rigged this A/B test environment in FL Studio where one can compare the original version and the summed stems. You can probably tell from the spectrogram in the below screenshot where I flipped the crossfade slider over to the Spleetered (Spleeted?) version.

The output stems are pcm_s16le, 44100 Hz, stereo, s16, 1411 kb/s, so it's not like the file itself is at fault here.
Is this expected? Can this be tuned/changed somehow?

It looks like all models only output up to 11 kHz. Would be nice to know if this is part of the model or stems from the original training data

Hey Aarni,
Thanks for your feedback. Indeed the default behavior is to cut frequencies above 11Khz but it can be changed in the settings. Read this comment for details.

@mmoussallam but this still means that the models do not predict masks above 11khz, right? is this hardcoded in a training config?

@faroit, yes, you're right: models are only trained until 11kHz and don't predict anything above.
This is set in the training config through the F parameter (see the wiki).
This is just a design choice that we made, when training the models we provide.

@mmoussallam Thank you for the clarification!

We've just updated the FAQ for making clearer how you can actually perform separation above 11kHz.
Notably we pushed alternate configuration files (spleeter:2stems-16kHz, spleeter:4stems-16kHz and spleeter:5stems-16kHz) that perform separation up to 16kHz and explained how you can set upper separation frequency in the config file if you need another value.

Just a quick follow up,
I've been trying to incorporate the alternate 16kHz configuration using
spleeter separate -i audio_example.mp3 -o audio_output -p spleeter:4stems-16kHz
which raises the following error:
ERROR:spleeter:No embedded configuration 2stems-16kHz found
And
spleeter separate -i my_audio_file.mp3 -c spleeter:4stems-16kHz -o /output/path
which raises the following error:
spleeter separate: error: argument -c/--codec: invalid choice:
I'm currently running a Mac OSX, Python 3.7.3, I also attempted to reinstall spleeter with the same results. Any idea whats going on here?
Thanks,

@khaleelyo
Try using this cmd :: python3 -m spleeter separate -i audio_example.mp3 -o output -p spleeter:2stems-16kHz


fix: remove goccy/go-yaml

Fixes #115
I could confirm this fixes the perf regression.
I suspect describeYamlError won't work after this, @fzipi could you follow up after this PR to fix it and add some unit tests for the cases?

My proposal is to downgrade the library instead of removing it. There are still some features we want, and in the future, it is the only one that brings additional YAML features like anchors and aliases that might help when writing tests.
So I'm proposing to close this one and go for #117.

For the record, which features are you thinking of? Generally it's good to reduce dependencies for software chain reasons so it should be something significant IMO

There are still some features we want, and in the future, it is the only one that brings additional YAML features like anchors and aliases that might help when writing tests.

@anuraaga ☝

Sorry read those as future not now, oops.
As far as I can tell, those features are only for marshaling while go-yaml supports them fine for unmarshal. Does that mean it's not meaningful here?

Per https://github.com/goccy/go-yaml#2-reference-elements-declared-in-another-file, looks like I want that.

IIUC it's the ability to define anchors in separate files instead of just one. If that's the case, I guess it's not actually yaml.
While go-ftw may be a primary implementer of the tests, it can't be the only one. I don't think it's safe for CRS to be defining tests in a way that does not support standard yaml parsers. There's already support for generating regexes so wouldn't we want to add tooling for generating compliant yaml instead of forcing parser implementations?

+1 on using standard yaml only.
On Mon, 21 Nov 2022, 13:23 Anuraag Agrawal, @.***>
wrote:

IIUC it's the ability to define anchors in separate files instead of just
one. If that's the case, I guess it's not actually yaml.
While go-ftw may be a primary implementer of the tests, it can't be the
only one. I don't think it's safe for CRS to be defining tests in a way
that does not support standard yaml parsers. There's already support for
generating regexes so wouldn't we want to add tooling for generating
compliant yaml instead of forcing parser implementations?
—
Reply to this email directly, view it on GitHub
https://github.com/coreruleset/go-ftw/pull/116#issuecomment-1321980454,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAXDIJ3WZIRXWLGXIZ3WJNSUDANCNFSM6AAAAAASGIU4UQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I don't think this is the place to discuss this. If we want to, let's raise a new issue and discuss there.

So, in summary:

there is no need to remove this library, as of now. The functionality we use out of the box is going to break when removed, so more work is needed to replace and/or re-implement it.
while the desire is to keep the number of libraries used to a minimum (reusing vs. implementing something) when there is a library that provides the same feature, I don't think it is worth it for this kind of project. I can understand it for Coraza or a project that needs to be extremely performant. This is not the case.
anchors and aliases are standard yaml: https://yaml.org/spec/1.2.2/#anchors-and-aliases. The inability of the go "standard" library to parse those are a problem for that library.

Also, the "standard" library gopkg.in/yaml.v3 is not part of the core, is just another library 😄 .

I agree with @fzipi. Downgrade the library. They will notice the performance impact at some point and then we can upgrade.


pull request for e2e test at 02/03/2017 12:26:06

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


CONJUBILEE-3123: Updating CommandOutput with valid command output schema

Description
What is the intent of this change and why is it being made?

JIRA: https://sailpoint.atlassian.net/browse/CONJUBILEE-3123
Fix for Output Schema validation error for application discovery command

How Has This Been Tested?
What testing have you done to verify this change?

Tested mannually

 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.


script: Add repository settings

Purpose of pull request
Debian has entered the ELTS phase, the DEBIAN_MIRROR URL defined in Poky will eventually no longer be available.
So, add setting to local.conf for refer to 'archive.debian.org'.
And, same to definition of DEBIAN_SECURITY_UPDATE_MIRROR, but 'debian-security' archive does not yet exist, add it to MIRRORS for the future.
Test
How to test

Run setup-emlinux script
$ source setup-emlinux test

Check local.conf setting
test$ echo 'DISTRO = "emlinux"' >> conf/local.conf
test$ echo 'MACHINE = "qemuarm64"' >> conf/local.conf
test$ tail -n 20 conf/local.conf

Confirm fetch
test$ rm -fr ../downloads
test$ bitbake core-image-minimal --runall=fetch
test$ ls ../downloads | head
test$ grep -B 5 "Saving to:" tmp-glibc/work/aarch64-emlinux-linux/acl/2.2.53-r0/temp/log.do_fetch

Test result
1. Run setup-emlinux script
$ source setup-emlinux test
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.

You had no conf/bblayers.conf file. This configuration file has therefore been
created for you with some default values. To add additional metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/

### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
NOTE: Starting bitbake server...
NOTE: Starting bitbake server...
NOTE: Starting bitbake server...

2. Check local.conf setting
local.conf is configured as expected.
test$ tail -n 20 conf/local.conf
           poky/meta/recipes-graphics/xorg-lib/libxxf86misc_1.0.4.bb \
           meta-debian/recipes-debian/fcode-utils/fcode-utils_debian.bb"
DEBIAN_MIRROR="http://archive.debian.org/debian/pool"
DEBIAN_SECURITY_UPDATE_MIRROR="http://security.debian.org/debian-security/pool/updates"
DEBIAN_ELTS_SECURITY_UPDATE_MIRROR="http://deb.freexian.com/extended-lts/pool"
MIRRORS+="${DEBIAN_SECURITY_UPDATE_MIRROR}    http://archive.debian.org/debian-security/pool/updates/ \n"
CTJ_DEBIAN_MIRROR='http://emlinux-pkgs.miraclelinux.com/debian/pool'
MIRRORS+="${DEBIAN_MIRROR}    ${CTJ_DEBIAN_MIRROR} \n"
CTJ_DEBIAN_SECURITY_UPDATE_MIRROR='http://emlinux-pkgs.miraclelinux.com/debian-security/pool/updates'
MIRRORS+="${DEBIAN_SECURITY_UPDATE_MIRROR}    ${CTJ_DEBIAN_SECURITY_UPDATE_MIRROR} \n"
CTJ_DEBIAN_ELTS_SECURITY_UPDATE_MIRROR='http://emlinux-pkgs.miraclelinux.com/extended-lts/pool'
MIRRORS+="${DEBIAN_ELTS_SECURITY_UPDATE_MIRROR}    ${CTJ_DEBIAN_ELTS_SECURITY_UPDATE_MIRROR} \n"
CTJ_SOURCE_MIRROR = 'http://emlinux-pkgs.miraclelinux.com/mirror/sources'
MIRRORS += "git://.*/.*    ${CTJ_SOURCE_MIRROR} \n"
MIRRORS += "http://.*/.*    ${CTJ_SOURCE_MIRROR} \n"
MIRRORS += "https://.*/.*    ${CTJ_SOURCE_MIRROR} \n"
MIRRORS += "ftp://.*/.*    ${CTJ_SOURCE_MIRROR} \n"
PREMIRRORS_append = "\n git://git.kernel.org/pub/scm/linux/kernel/git/cip    git://gitlab.com/cip-project/cip-kernel \n"
DISTRO = "emlinux"
MACHINE = "qemuarm64"

3. Confirm fetch
As expected, the source code was successfully fetched from "archive.debian.org".
test$ bitbake core-image-minimal --runall=fetch
Parsing recipes: 100% |#################################################################################################| Time: 0:00:36
Parsing of 1359 .bb files complete (0 cached, 1359 parsed). 2381 targets, 81 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.42.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-20.04"
TARGET_SYS           = "aarch64-emlinux-linux"
MACHINE              = "qemuarm64"
DISTRO               = "emlinux"
DISTRO_VERSION       = "2.9"
TUNE_FEATURES        = "aarch64 armv8a crc"
TARGET_FPU           = ""
meta
meta-yocto-bsp       = "HEAD:d4b57c68b22027c2bedff335dee06af963e4f8a8"
meta-debian          = "HEAD:40440f15e2c2d06f685da17b9af7bb105467954a"
meta-debian-extended = "HEAD:1c715cd814488f37b7fe8c57181541faa23795be"
meta-emlinux         = "add-repository-setting:7bbcbf34901dfe8a618de45dea95e1d5f6a117f7"
meta-emlinux-private = "HEAD:33c0e2e32b02917b5bae6538579eea4325fdcf1c"

NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/2.9/x86_64-nativesdk-libc.tar.xz;sha256sum=d07916b95c419c81541a19c8ef0ed8cbd78ae18437ff28a4c8a60ef40518e423
Initialising tasks: 100% |##############################################################################################| Time: 0:00:02
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 219 tasks of which 0 didn't need to be rerun and all succeeded.

test$ ls ../downloads | head
Error-0.17027.tar.gz
Error-0.17027.tar.gz.done
acl_2.2.53-4.debian.tar.xz
acl_2.2.53-4.debian.tar.xz.done
acl_2.2.53-4.dsc
acl_2.2.53-4.dsc.done
acl_2.2.53.orig.tar.gz
acl_2.2.53.orig.tar.gz.asc
acl_2.2.53.orig.tar.gz.asc.done
acl_2.2.53.orig.tar.gz.done

test$ grep -B 5 "Saving to:" tmp-glibc/work/aarch64-emlinux-linux/acl/2.2.53-r0/temp/log.do_fetch
--2024-07-17 09:01:40--  http://archive.debian.org/debian/pool/main/a/acl/acl_2.2.53-4.dsc
Resolving proxy-sgy.miraclelinux.com (proxy-sgy.miraclelinux.com)... <IP_ADDRESS>
Connecting to proxy-sgy.miraclelinux.com (proxy-sgy.miraclelinux.com)|<IP_ADDRESS>|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 2330 (2.3K) [text/prs.lines.tag]
Saving to: ‘/project/security-update/test3/test/../downloads/acl_2.2.53-4.dsc’
--
--2024-07-17 09:01:40--  http://archive.debian.org/debian/pool/main/a/acl/acl_2.2.53.orig.tar.gz
Resolving proxy-sgy.miraclelinux.com (proxy-sgy.miraclelinux.com)... <IP_ADDRESS>
Connecting to proxy-sgy.miraclelinux.com (proxy-sgy.miraclelinux.com)|<IP_ADDRESS>|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 524300 (512K) [application/x-gzip]
Saving to: ‘/project/security-update/test3/test/../downloads/acl_2.2.53.orig.tar.gz’
--
--2024-07-17 09:01:40--  http://archive.debian.org/debian/pool/main/a/acl/acl_2.2.53.orig.tar.gz.asc
Resolving proxy-sgy.miraclelinux.com (proxy-sgy.miraclelinux.com)... <IP_ADDRESS>
Connecting to proxy-sgy.miraclelinux.com (proxy-sgy.miraclelinux.com)|<IP_ADDRESS>|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 833 [application/pgp-keys]
Saving to: ‘/project/security-update/test3/test/../downloads/acl_2.2.53.orig.tar.gz.asc’
--
--2024-07-17 09:01:40--  http://archive.debian.org/debian/pool/main/a/acl/acl_2.2.53-4.debian.tar.xz
Resolving proxy-sgy.miraclelinux.com (proxy-sgy.miraclelinux.com)... <IP_ADDRESS>
Connecting to proxy-sgy.miraclelinux.com (proxy-sgy.miraclelinux.com)|<IP_ADDRESS>|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 18572 (18K) [application/x-xz]
Saving to: ‘/project/security-update/test3/test/../downloads/acl_2.2.53-4.debian.tar.xz’

@teradat thank you.


Document interpretation of axis-angle quantities

The SpatialLocation API provides angular velocity and acceleration as axis-angle values, but the documentation does not explain how to interpret these values. These changes add details to explain how the values should be interpreted.

@hickeys Could you review this pull request?
Thank you

@thetuvix FYI.

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

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

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

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

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

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


[DDW-374] Submit network and software versions to reporting server

This PR changes the information we are sending on support requests to the reporting server.
Todo:
application field and submit these values based on the network:

[x] Remove the application field
[x] Submit these new values:

product: Cardano Wallet
frontendVersion: 0.11.0 (from the environment)
backendVersion: 1.3.0 (from the environment)
buildNumber: 211221 (from the environment)
network: testnet (from the environment)

Note: Currently the field build sends ${API_VERSION}.${BUILD_NUMBER}. With this change, this information will be sent through a new field called installerVersion, whereas build will send, in fact, only the build number.
Before:
build: <IP_ADDRESS>221,

After:
build: 211221,
installerVersion: <IP_ADDRESS>221,

Todo:

[ ] Todo
[ ] Todo
[ ] Todo

Screenshots:

Screenshot

Review Checklist:
Basics

[ ] PR is updated to the most recent version of target branch (and there are no conflicts)
[ ] PR has good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance tests are passing (yarn run test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn run dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn run package / CI builds)
[ ] There are no flow errors or warnings (yarn run flow:test)
[ ] There are no lint errors or warnings (yarn run lint)
[ ] Text changes are proofread and approved (Jane Wild)
[ ] There are no missing translations (running yarn run manage:translations produces no changes)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn run storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly documented and commented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-rendering
[ ] Any code that only works in Electron is neatly separated from components

Testing

[ ] New feature / change is covered by acceptance tests
[ ] All existing acceptance tests are still up-to-date
[ ] New feature / change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review:

[ ] Merge PR
[ ] Delete source branch
[ ] Move ticket to done on the Youtrack board

@daniloprates I have updated release/0.11.1 branch by merging latest master branch into it. Can you please fix the conflicts in your branch?

There is a new staging Cardano report server URL: https://github.com/input-output-hk/daedalus/pull/1036/commits/95a148bb948ba6ca14d2ab488ac07b628a63f8aa
We need to test it before merging this PR...
cc @darko-mijic @daniloprates @deepfire

@daniloprates @darko-mijic we have tested report submission against Zendesk mainnet account and it is fully operational: https://iohk.zendesk.com/agent/tickets/27630

Merging this PR now! :) 🎉


react-native keep calling ws://localhost:8097 and getting 500

dosen't seems to cause any problem right now, but annoying
RN: 0.44.0
OS: 10.13.1

Hi @dktan. Did you ever found out the reason of this issue?


Dragging in the Mesh Preview editor creates a "drag and drop" action.

Godot version
Godot v4.2.dev6 - Pop!_OS 22.04 LTS - X11 - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) () - 12th Gen Intel(R) Core(TM) i5-1235U (12 Threads)
System information
Godot v4.2.dev6 - Pop!_OS 22.04 LTS - X11 - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) () - 12th Gen Intel(R) Core(TM) i5-1235U (12 Threads)
Issue description
https://github.com/godotengine/godot/assets/85438892/b46c7045-c50c-44ef-92c8-04c5f21342b8
Steps to reproduce
I get this most of the time with mesh previews.
Minimal reproduction project
N/A

This is probably caused by the fact that the mesh editor preview is a standalone class while the material editor preview is part of the material editor (not standalone).

In general I don't see this with any other editor previews, so MeshPreview probably does something different that can be investigated.

As this was reported against 4.2-dev6 I wrongly assumed it was a regression, but I just tested and it behaves the same in 4.1-stable.
I'm not even sure it's a bug actually, there's the same behavior for most properties, they can be dragged to the script editor to copy their name, which is what happens here.

I'm not even sure it's a bug actually, there's the same behavior for most properties, they can be dragged to the script editor to copy their name, which is what happens here.

I don't think this should happen over the preview, though. Or we need to remove other interactions from it, because from the user perspective this doesn't work right.

Yes, this should only happen when you drag the property, not the preview under it.

Can't reproduce it in 4.3. Can you confirm it's fixed?

Seems like I can't reproduce it anymore either.


D435 Color and Depth misalignment

Hi,
In the images below, a red block is placed on the edge of my desk, and as you can see, the edge of the red block is projected to the floor.

I suspect this is due to a misalignment in the color and depth images.
The images are obtained with factory-calibrated RealSense 435.
Re-calibrating the extrinsic parameters of the camera with the Dynamic Calibration Software provided by Intel did not fix the issue.
Is this an expected behavior? Is there a way to alleviate this problem?
Best regards,

@dorodnic
Thank you so much!

Hi @Michae1Park
Please note the Occlusion Removal combo-box in the top panel. Try switching it from Off to Heuristic. This should do the trick.
This feature has been part of librealsense for quite a while now, and yet we still don't have a good documentation (that I know of) explaining this effect...
This effect is caused by the fact that the Depth and RGB cameras are not sharing the exact same position (there is about a 1.5 cm of displacement between them).
The problematic "red" pixels in the background are actually pixels that Depth sensor can see, but RGB sensor cannot, because from the RGB view-port, they are occluded by the red box.

In this scene the RGB camera does not see the blue cone since it is occluded in its view-port. Only the depth camera can see it. In the RGB image, the color of these pixels is red, thus in the 3D viewer you'd see the cone as red, despite it having no texture information at all.
The Viewer has two occlusion filters and these can also be enabled programmatically, although I don't think we have a good code sample for that.