Firebase.initializeApp() throws Expected a value of type 'Object', but got one of type 'Null'

I am running a simple Flutter app with FirebaseAuth on Chrome/Web platform in VSCode.
The following line in main() throws an exception when run in Web/Chrome platform:
Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);
Error: Expected a value of type 'Object', but got one of type 'Null'
A few other issues of similar nature have been raised in the past, but they have gone stale without a solution:
https://github.com/firebase/flutterfire/issues/8128
https://github.com/firebase/flutterfire/issues/10468
https://www.reddit.com/r/flutterhelp/comments/1743jjy/firebase_throws_exception_on_initializeapp/
My observation:
This happens in Debug mode.
Workaround: Run the app in Release mode without debugging enabled.
An additional observation, that may be relevant:
Flutter is unable to catch FirebaseAuthException in Debug mode.
Even though I have code to capture FirebaseAuthException, the app crashes in Debug mode.
// deliberately raise an auth exception
try {
	await FirebaseAuth.instance.signInWithEmailAndPassword(
	    email: 'invlaid_email',
	    password: 'invalid_password',
	);
} on FirebaseAuthException catch (e1) {
	// The exception is never caught, the app just crashes in Debug mode
	print(e1);
} catch (e2) {
	print(e2);
}

Hi @ramanraja, please provide the output of flutter pub deps -- --style=compact and the output of flutter doctor -v.
Does this also happen with the auth example app?

Platform: Windows 10
IDE: Visual Studio Code
Run target: Chrome/Web-javascript
or
Run target: Edge/Web-javascript
Exception occurs at the line:
->> await Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);
Error message:
Exception has occurred.
Error: Expected a value of type 'Object', but got one of type 'Null'
dart-sdk/lib/internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:49      throw
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 127:3       castError
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 742:12  cast
dart-sdk/lib/_internal/js_dev_runtime/patch/core_patch.dart 78:24                 as
The same app runs in Debug mode without crashing on Android emulator and Android phone.

flutter pub deps  --style=compact

Dart SDK 3.1.3
Flutter SDK 3.13.7
fire_users1 0.1.0
dependencies:

cloud_firestore 4.12.2 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
firebase_auth 4.12.1 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
firebase_core 2.21.0 [firebase_core_platform_interface firebase_core_web flutter meta]
firebase_messaging 14.7.3 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
firebase_storage 11.4.1 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
flutter 0.0.0 [characters collection material_color_utilities meta vector_math web sky_engine]
image_picker 1.0.4 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_linux image_picker_macos image_picker_platform_interface image_picker_windows]

dev dependencies:

flutter_lints 2.0.3 [lints]
flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math async boolean_selector characters collection material_color_utilities meta source_span stream_channel string_scanner term_glyph web]

transitive dependencies:

_flutterfire_internals 1.3.11 [collection firebase_core firebase_core_platform_interface flutter meta]
async 2.11.0 [collection meta]
boolean_selector 2.1.1 [source_span string_scanner]
characters 1.3.0
clock 1.1.1
cloud_firestore_platform_interface 6.0.3 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
cloud_firestore_web 3.8.3 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
collection 1.17.2
cross_file 0.3.3+6 [js meta]
fake_async 1.3.1 [clock collection]
file_selector_linux 0.9.2+1 [cross_file file_selector_platform_interface flutter]
file_selector_macos 0.9.3+3 [cross_file file_selector_platform_interface flutter]
file_selector_platform_interface 2.6.1 [cross_file flutter http plugin_platform_interface]
file_selector_windows 0.9.3+1 [cross_file file_selector_platform_interface flutter]
firebase_auth_platform_interface 7.0.3 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
firebase_auth_web 5.8.6 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta]
firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
firebase_core_web 2.8.1 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
firebase_messaging_platform_interface 4.5.12 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
firebase_messaging_web 3.5.12 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
firebase_storage_platform_interface 5.0.1 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
firebase_storage_web 3.6.12 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
flutter_plugin_android_lifecycle 2.0.17 [flutter]
flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math web]
http 1.1.0 [async http_parser meta]
http_parser 4.0.2 [collection source_span string_scanner typed_data]
image_picker_android 0.8.8+2 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
image_picker_for_web 3.0.1 [flutter flutter_web_plugins image_picker_platform_interface mime]
image_picker_ios 0.8.8+4 [flutter image_picker_platform_interface]
image_picker_linux 0.2.1+1 [file_selector_linux file_selector_platform_interface flutter image_picker_platform_interface]
image_picker_macos 0.2.1+1 [file_selector_macos file_selector_platform_interface flutter image_picker_platform_interface]
image_picker_platform_interface 2.9.1 [cross_file flutter http plugin_platform_interface]
image_picker_windows 0.2.1+1 [file_selector_platform_interface file_selector_windows flutter image_picker_platform_interface]
js 0.6.7 [meta]
lints 2.1.1
matcher 0.12.16 [async meta stack_trace term_glyph test_api]
material_color_utilities 0.5.0 [collection]
meta 1.9.1
mime 1.0.4
path 1.8.3
plugin_platform_interface 2.1.6 [meta]
sky_engine 0.0.99
source_span 1.10.0 [collection path term_glyph]
stack_trace 1.11.0 [path]
stream_channel 2.1.1 [async]
string_scanner 1.2.0 [source_span]
term_glyph 1.2.1
test_api 0.6.0 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
typed_data 1.3.2 [collection]
vector_math 2.1.4
web 0.1.4-beta

flutter doctor -v

[√] Flutter (Channel stable, 3.13.7, on Microsoft Windows [Version 10.0.19045.3570], locale en-IN)
• Flutter version 3.13.7 on channel stable at D:\software\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 2f708eb839 (5 weeks ago), 2023-10-09 09:58:08 -0500
• Engine revision a794cf2681
• Dart version 3.1.3
• DevTools version 2.25.0
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at C:\Users\raman\AppData\Local\Android\sdk
• Platform android-34, build-tools 34.0.0
• Java binary at: E:\Software\AndroidStudio\jbr\bin\java
• Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-10027231)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.6.5)
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.6.33829.357
• Windows 10 SDK version 10.0.20348.0
[√] Android Studio (version 2022.3)
• Android Studio at E:\Software\AndroidStudio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• android-studio-dir = E:\Software\AndroidStudio
• Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-10027231)
[√] VS Code (version 1.84.2)
• VS Code at C:\Users\raman\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.76.0
[√] Connected device (3 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19045.3570]
• Chrome (web)      • chrome  • web-javascript • Google Chrome 119.0.6045.159
• Edge (web)        • edge    • web-javascript • Microsoft Edge 119.0.2151.58
[√] Network resources
• All expected network resources are available.
• No issues found!

I created a skeleton application with the same dependencies (with the latest versions).
Thank you

hi @danagbemava-nc,  Thank you. My codebase is entangled with the Flutter database, Auth setup, messaging and storage. I tried to prune everything down to a minimal version, but the crash could not be reproduced. But the project in its original form still keeps crashing to this date, so it was not a transient phenomenon.
Two observations are relevant: (1) it crashes only in debug mode, that too with web as the run target. It works fine on the emulator and a physical Android device.  (2) making a clone of the whole code, and upgrading the dependencies to the latest versions (as of Nov 2023) solves the issue.
In view of the above, I think we can put this on the back burner and revisit it if the issue crops up again. Thanks for you very much.


New Crowdin updates

@benface checking on these?

Thanks @azf20. Just ran yarn prettier && yarn lint && yarn build and everything looks good to me. Merging.


Mastodon module regression 23.05

Describe the bug
These changes have made the Mastodon module config more opinionated than it used to be:

this assertion prevents configuration with createLocally = false and host = "/run/postgresql", even though that's a perfectly valid setup. Workaround for now is setting host = "/var/run/postgresql"
https://github.com/NixOS/nixpkgs/blob/nixos-23.05/nixos/modules/services/web-apps/mastodon.nix#L657 forces the passwordFile to be set (/dev/null seems to work) even though it's not needed, like when using peer auth

Expected behavior
Remove the assertion outright? The passwordFile script can use a lib.optionalString like is done here
Notify maintainers
@erictapen @happy-river @Izorkin

ref https://github.com/NixOS/nixpkgs/pull/117126#issuecomment-1576750168

If we remove this assertion, there may be scenarios where the user may not fully configure the database in Mastodon.
Can you give me your PostgreSQL service configuration?

Doesn't a user changing mastodon.database.createLocally to false already make sure they know to set it up themselves?

When creating the PR, I wanted to anticipate errors in the database settings and immediately warn about them.


The ego vehicle does not move (TF error)

Hello all,
My software version:
Ubuntu 18.04
ROS melodic
Autoware 1.14
Carla <IP_ADDRESS>
Problem
I followed the tutorial, basically, it works. I can see the route and point cloud in RVIZ, great contribution!
However, the vehicle could not move.

I tried these parameters, they don't help. Under manual control mode, the vehicle cannot move as well.
  <arg name='use_ground_truth_localization' default='false'/>
  <arg name='use_ground_truth_detections' default='false'/>
  <arg name='use_manual_control' default='true'/>

Error
There is a TF error.( I guess this is the main problem)
[ERROR] [1608667944.150539754,<PHONE_NUMBER>88]: Failed transform from base_link to ego_vehicle/lidar/lidar1
Can you kindly give me some suggestions?
Thanks a lot!

same issues as here:
https://github.com/carla-simulator/carla-autoware/issues/100

Finally, it worked!!
I installed git-lfs and repeated the whole process again.


Add Dutch National flag Algorithm under the sorting algorithm section

Hi,,,I am a contributor under the GGSOC 2023. I will add the Dutch National Flag Sort  Algorithm under the Sorting Algorithm section in C++. Please assign it to me @aaryahjolia

Hi @aaryahjolia , I am a GSSoC'23 contributor and would love to work on this issue.I have solved around 900 questions on leetcode(https://leetcode.com/code_hobby_2404/).

Hi @aaryahjolia , I am a GSSoC'23 contributor and would love to work on this issue.I have solved around 900 questions on leetcode(https://leetcode.com/code_hobby_2404/).

Bro I have opened this issue so that I can work on it...please stop commenting on all of the issues I created...instead find your own issues which are not already been raised by someone else


Multiple netconf client session nt working

I already have an ongoing session, when i try to connect via other netconf client to Netopeer2-server it gives it does not connect.
netopeer2-server[15736]: (cl_request_process:423) session-start request sent, waiting for response.
netopeer2-server[15736]: (cl_request_process:445) session-start response received, processing.
netopeer2-server[15736]: nc_ps_add_session: failed to wait for a pollsession condition (Connection timed out).
netopeer2-server[15736]: nc_ps_add_session: failed to wait for a pollsession condition (Connection timed out).
netopeer2-server[15736]: nc_ps_add_session: failed to wait for a pollsession condition (Connection timed out).
netopeer2-server[15736]: Internal error (/root/Netopeer2/server/main.c:591)
netopeer2-server[15736]: (cl_request_process:401) Sending session-stop request.

Hi,
please pull libnetconf2, it should be solved already.
Regards,
Michal

Problem is seen with libnetconf2 as well.
I am having libnetconf2 libraries.

Hi,
you are saying you have installed the most recent version of libnetconf2 (at least 0.6.19 for master branch and 0.7.19 for the devel branch) and this issue still occurs?
Regards,
Michal

Hi,
I also hit this issue. And I use libnetconf2 0.7.38.
set version
set(LIBNETCONF2_MAJOR_VERSION 0)
set(LIBNETCONF2_MINOR_VERSION 7)
set(LIBNETCONF2_MICRO_VERSION 38)

Hi,
the issues you replied to are really old and more importantly, closed, so please create another issue even though you have the same problem. That is, if you still experience it after updating libnetconf2 and netopeer2-server to latest versions (lnc2 0.8.62 or 0.9.4, server 0.3.75).
Regards,
Michal


How to set a td value readonly..

Hi, this tabledit have made me happy! The only thing that I was not able to do you yet it´s to set a td value as reandoly.. does anybody could do it??
Thanks
Willy

You set this in the editable array, if you want readonly leave the column out of the 'editable' array e.g.: Column 3 wouldn't be editable.
 $('#tabledit').Tabledit({ columns: {         identifier: [0, 'ID'],         editable: [[1, 'NAME'],[2,'PHONE'],[4,'DATE']] } })

hello
that right if remove Column 3 from array will not be editable ,
but there are problem if i use PHP , the value of Column 3  not send ???
any Idea how to fix this problem ???
thanks a lot


Try using async-websocket 0.23.0

https://github.com/socketry/async-websocket/issues/48
Types of Changes

Maintenance.

Contribution

[x] I agree to the Developer's Certificate of Origin 1.1.

jruby fails to install io-event (perhaps on the building of the extension?)


Feature request: Core install + modules

IMHO it would be good practice if the core of this CMS could be installed without the currently included precooked modules for blog, pages, events, faqs and promotions inside the package.
The simplest solution to accomplish this would be to (optionally) publish these modules in the separate /cms/Modules folder during setup, where the php artisan make:crud saves the template output. This way developers can choose to modify the modules easily.
Another solution would be to create a new package for these modules. I think the images, files and menu could be moved to separate packages as well.

Hmmm, I need to mull on this. I'm not against the idea, but I need to mull on this.

Hey @yapsr I did some mulling on this, and I started a concept in the branch core-modules take a look at that, it essentially would let you only publish some modules but I'm still mulling on it all

@mlantz I've just scanned your changes in the core-modules branch and I think I understand your changes. If I'm correct you make the install of some models, views, controllers etc optional during setup in the existing code. That is a good first start.
What I would recommend is to additionally move all blog, pages, events, faqs and promotions related code to a separate grafiteCMS-examples package. Installing this package would install these modules to the cms/Modules folder in the existing Laravel application. Just like the php artisan make:crud command! This separate package could be a added tot the main Laravel application composer.json file.
The GrafiteCMS directory in the vendor folder would then contain just the minimum required core functionality for the CMS, like the basic backend UI, files, documents, users, security etc.

On a technicality @yapsr the users, security etc is added by Grafite Builder, its not a core portion of the CMS. The CMS is intended to be a small addition to an application. I like the idea of being able to 'select' which modules you add to your application. I'd rather not separate all the things into smaller packages as it would cause larger changes in the system overall.
I've tested this version with a test site, and created an FAQs module, when I use comment out the core FAQ module and choose to not publish its parts then it's easy to work with the new custom one. I need to think about migrations a bit still but I'd rather avoid having multiple packages that I have to maintain, its just easier to allow a more 'custom' setup


[hotfix][table] Fix typo for method name in FieldReferenceLookup

hotfix typo, Ambigous -> Ambiguous.

Thanks for your review! @hequn8128
@flinkbot approve all
Merging...

Fixed in master : 2ffa618b989ffbb35b7f137a258623aebbc27f25


Claim only rolled characters

Which part of the code should i edit to claim only the character that i have rolled ? Do you think it is easy to implement it with the actual code (i'm a bit of a beginner with python) ?

uh yeah just turn the variable sniping to false in the code
but it still will snipe other people's kakera loot tho so keep htat in mind

Oh ok. Sorry, seems like I was running the stable branch of the repo. The main one seems more complete. Thanks a lot for your fast response. Great work you did with this Bot.

The stable version was the version before all the predictive code was added so I didn’t want to say the predictive code was stable just yet just in case users found bugs
The sniping function was added with that update because we have implement a way to determine if the roll was a personal roll or if the roll was a different user
I still wouldn’t say it is more complete as there might be more timing issues as since the stable one is less code in theory there less checks and stuff it goes thru to perform snipes
Sent from my iPhone

On Jul 16, 2021, at 8:38 AM, Pbonnamy @.***> wrote:

Oh ok. Sorry, seems like I was running the stable branch of the repo. The main one seems more complete. Thanks a lot for your fast response. Great work you did with this Bot.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


Legend Items are always "clickable"

https://github.com/uber/react-vis/blob/ec1ed9f9b9dc140c1ee1d53292e51f31f99161a1/src/legends/discrete-color-legend-item.js#L38
I think you've got a bug here.  onClick is a function, so it's always "truthy".  Thus this clickable class always gets added.
I suggest fixing this over here:
https://github.com/uber/react-vis/blob/ec1ed9f9b9dc140c1ee1d53292e51f31f99161a1/src/legends/discrete-color-legend.js#L50
By only conditionally passing in a function, otherwise path in something "falsy"

Good catch! discrete-color-legend's default value for onItemClick is what's causing the trouble. I would accept a PR that removes default from discrete-color-legend and does a presence check on discrete-color-legend-item.
Probably would also require writing a test so that we don't backslide.

oh it's a bug! I just thought it was a weird default behavior.
I've been using this to de-clickable them w styled-components:
 .rv-discrete-color-legend-item {
        cursor: default;
        &:hover {
            background: unset;
        }
    }


Loongarch Support

QEMU 7.1 will begin loongarch support: https://wiki.qemu.org/ChangeLog/7.1#LoongArch.
Currently, everything works but all check variants:
qemu-loongarch64 -strace /home/schrodinger/Downloads/loongarch64-clfs-6.0-cross-tools-gcc_and_clang-full/cross-tools/target/usr/lib64/ld-linux-loongarch-lp64d.so.1 --library-path /home/schrodinger/Downloads/loongarch64-clfs-6.0-cross-tools-gcc_and_clang-full/cross-tools/target/usr/lib64 ./func-thread_alloc_external-check

So I tried
diff --git a/src/snmalloc/pal/pal_posix.h b/src/snmalloc/pal/pal_posix.h
index 8ad7995..22314db 100644
--- a/src/snmalloc/pal/pal_posix.h
+++ b/src/snmalloc/pal/pal_posix.h
@@ -233,7 +233,10 @@ namespace snmalloc
         is_aligned_block<OS::page_size>(p, size) || (zero_mem == NoZero));

       if constexpr (PalEnforceAccess)
-        mprotect(p, size, PROT_READ | PROT_WRITE);
+      {
+        int val = mprotect(p, size, PROT_READ | PROT_WRITE);
+        SNMALLOC_ASSERT_MSG(val == 0, "mprotect is expected to succeed, address: {}, page size: {}", p, ::sysconf(_SC_PAGESIZE));
+      }
       else
       {
         UNUSED(p, size);

And it reported
assert fail: val == 0 in /home/schrodinger/Downloads/snmalloc/src/snmalloc/backend_helpers/../mem/../ds/../pal/pal_posix.h on 238 mprotect is expected to succeed, address: 0x5c24cdd000, page size: 16384

Seems that it is a problem of page size detection.

On PowerPC, qemu user mode defaults to 4 KiB pages, which confuses snmalloc, which expects 64 KiB pages.    You might need to explicitly tell qemu to use 16 KiB pages for LoongArch.

any specific guide on adding qemu pipelines?

@mjp41  Is 7.1.0 available in our pipeline？

@mjp41 Is 7.1.0 available in our pipeline？

Not convinced.  You can try, maybe we can build a docker image with it in?

Last time we used Docker, it added a lot to our end-to-end test times.  Is there an unofficial apt repo that has newer builds of qemu that we can use?

help wanted


Terraform Runs Slowly Inside Lima VM

Description
Host OS: macOS 12.3.1
Host arch: arm64
Lima version: 0.9.2
Lima VM OS: Ubuntu 21.10
Lima VM arch: arm64
Attempting to run terraform plan or apply inside a lima VM is very slow while terraform calculates the state of the environment. The code repository is cloned inside the VM (so the performance is not related to file sharing between the host OS and the VM). Just to see if I could narrow down the issue, I tried overriding the VM DNS settings in /etc/resolv.conf to my local router instead of <IP_ADDRESS> and the issue was fixed. Not sure why the systemd-resolved queries would be so much slower. The difference is very noticeable, with terraform plan taking minutes instead of seconds.

Did you build lima from the HEAD of the master branch, or are you using the latest release?
There is a bug fix in #773 to the host resolver that could cause timeout issues. Could you compile Lima itself from master and see if this change affects the slowdown you are seeing?

It's almost like DNS resolving gets overwhelmed by the way terraform works (multithreaded queries to the infrastructure APIs). When terraform plan is running I can run dig in a separate shell to the lima VM and get timeouts. But when terraform plan isn't running DNS resolves normally.

@bliles we are trying to narrow down the cause of these i/o timeouts. What kind of DNS queries terraform plan is making? is it only A, maybe AAAA and CNAME??  or are there other queries e.g TXT queries that terraform could be making? is there any way to find that out?? this can help us greatly in our process of debugging this issue.

Without setting up wireshark or something, I don't know a way I could tell you for absolute certainty. However, based on that terraform is doing, I think you can assume that most of the time terraform is just using the standard go lib to make HTTP requests to the AWS APIs. Terraform isn't directly making DNS queries, it just needs to hit various APIs for AWS services in order to query the state of the infrastructure under management.

I decided to run another test using a personal project that is running in AWS and is managed with terraform. It is a tiny terraform project that just provides a redirect domain. When I run terraform plan, it generates 10 "Refreshing state..." log lines. This is not enough queries to cause the timeouts. The timeouts are only caused when there are around 20 "Refreshing state..." log lines emitted by terraform. You can see things running normally at first in the output until we hit roughly the 20th log line at which point console output slows to a crawl. Also of note is the fact that terraform works multi-threaded so likely the DNS server is bombarded with several queries at the same time.

We are going to try to reproduce the issue by writing a test app that will issue many simultaneous queries.
I have a vague suspicions that the problems might be related to the type of DNS answers provided by AWS though (e.g. longer than usual), so not sure if the local repro is going to work.
If it doesn't, would you be able to scale up your personal terraform project to a size the reproduces the problem, and share the config with us, so we could run it ourselves?

I will try to give you a repro that I can actually share with you. I tried just adding resources to my personal project and running terraform plan so as not to actually create the resources, but it didn't result in the same behavior.

It could be related with this systemd-resoveld.
I am currently facing internal DNS resolution issues!
For example:

CoreDNS memory limits: I needed to remove that constraint.
Running Ubuntu 22 put me in problems with DNS due to the facto of systemd-resolved

I am working on a workaround to update kubelet


ARM compatibility

Describe the bug
This command don't work in a ARM enviroment.
docker run --rm livekit/livekit-server generate-keys
Server

Version: last
Environment: arm64 + ubuntu

To Reproduce
run docker run --rm livekit/livekit-server generate-keys in a ubuntu arm64
Expected behavior
generate the keys
Screenshots

Ah, looks like our arm64 builds were not done properly. Could you try this?
docker run --rm livekit/livekit-server:v0.14.1-SNAPSHOT generate-keys


Account precondition equality fix

Explain your changes:
This PR makes Account_update.Account_precondition.equal treats equivalence as equality.
Explain how you tested your changes:
I added 2 unit tests that would fail without my changes.
Checklist:

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

Closes #0000

ci-build-me

ci-build-me

!ci-build-me


Installation is OK, but "There was an error submitting job!"

Hi, I tried to follow the recommendations of other issues I've found here, but I'm still getting this error. My goal is to set up a routine to run a code on windows (locally).
I really appreciate your help!

Hi @leandromaiaf - this tool is completely untested in Windows. Under the hood, it uses CRON, which is a Linux-based application. Best advise I can give it to create a linux VM on your workstation and use it in there.

Hi @jovanni-hernandez, I'm giving a try on linux right now. Hope I'll be back with good news. Thanks for your support.


can not restart dev mode with backup database more than once

The postgres container changes file permissions for the database directory of a backup database from prod.
The dev mode init scripts check the file permissions, which no longer belong to the system user and fails to start;
...
Caused by: java.lang.RuntimeException: Directory /working/databases/horreum-db/archive-primary-20231122075209/primary-20231122075209 does not have sufficient permissions to operate!
	at io.hyperfoil.tools.horreum.infra.common.resources.PostgresResource.checkIfDirectoryIsEmtpy(PostgresResource.java:94)
	at io.hyperfoil.tools.horreum.infra.common.resources.PostgresResource.init(PostgresResource.java:54)
	at io.hyperfoil.tools.horreum.infra.common.HorreumResources.startContainers(HorreumResources.java:145)
	at io.hyperfoil.tools.horreum.dev.services.deployment.HorreumDevServicesProcessor.startHorreumContainers(HorreumDevServicesProcessor.java:129)
	... 11 more

@whitingjr what was the error that this PR fixed: https://github.com/Hyperfoil/Horreum/pull/958 ?


[msal-node] Docs update

Updating msal-node docs:

Correcting typos
Adding relevant links for a few flows

Coverage remained the same at 80.998% when pulling 8059a7e94ef69da2655b826217cdd48251858745 on msal-node-alpha-docs into c6db556ceef9012bc1852dcf27e9d46fae4c2046 on dev.


Allow DNS updates to change record type

Could you also add a test for this?
On Fri, Jul 14, 2017 at 1:15 PM John Thompson<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/cloudflare/cloudflare-go/pull/139
Commit Summary

Allow DNS updates to change record type

File Changes

M dns.go
https://github.com/cloudflare/cloudflare-go/pull/139/files#diff-0
(4)

Patch Links:

https://github.com/cloudflare/cloudflare-go/pull/139.patch
https://github.com/cloudflare/cloudflare-go/pull/139.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/cloudflare-go/pull/139, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABIcN64vpF6Ikf-lllU7r7H72pUw94uks5sN8xrgaJpZM4OYsR7
.

Can you also update flarectl to allow setting the type there please?

Hey @its-johnt - do you think you can update flarectl to handle this too?


Notebook 11. ValueError: An output parsing error occurred.

Hey folks, I keep getting parsing errors for the csv agent in Notebook 11, despite setting the model to gpt4 and adding the handling_parsing_errors=True parameter in the utils.py:451
It is probably related to some regression in the langchain, I wasn't able to pin the root cause yet.

ValueError: An output parsing error occurred. In order to pass this error back to the agent and have it try again, pass `handle_parsing_errors=True` to the AgentExecutor. This is the error: Could not parse tool input: {'arguments': "import pandas as pd\n\ndf = pd.read_csv('covid_data.csv')\nrows = df.shape[0]\nrows", 'name': 'python'} because the `arguments` is not valid JSON.

make sure you have the model version 1106 or 0125 of gpt3.5 turbo or gpt4 turbo

I tried all of those with no luck

If Notebook 7 works correctly, hence Notebook 11 should as well. Check you have the latest code.


Extends theme.txt to allow different zones for each layer fixes #5933

Just add 2 more lines in your theme.txt to create layers and their corresponding zone.

Layers: TheNextHomepage, Calendar
LayerZones: {"TheNextHomepage":"Messages, Headerhome, Edito, Agenda, Actus, Catalogue","Calendar":"Header, Navigation, AsideFirst, Messages, BeforeContent, Content, Footer"}

Then in Widgets menu, add the 2 layers TheNextHomepage and Calendar.
This also relies on alternates to create the corresponding layout-url-xxx.cshtml with code for your new zones as

@if (Model.Edito != null) {
@Zone(Model.Edito)
}

Could you add tests?

What kind of tests ? mock tests or samples ?
If you need to test it, just add  2 lines to a copy of the Theme machine and look the results in Widgets admin...

Discussion pending on the issue itself.

Demo of the features in this PR
https://youtu.be/oXNVY_LFMJc

While I understand the motivation behind the feature,I don't think themes should know anything about layers, or layers about zones. The same result could be obtained in a cleaner way buy having the widget editor be aware of multiple layouts, with different zones, whether those layouts are statically defined in the theme or dynamically built.

Bertrand zones are already in theme.txt...
But I agree that it would be nice to be able to define dynamically the zones able to host widgets for a layer.
My solution is et easy to implement: 10 lines in the pr and it preserves all the existing features.
Envoyé à partir de mon sanyo phc 25

De : Bertrand Le<EMAIL_ADDRESS>Envoyé : 19/10/2015 18:16
À<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Objet : Re: [Orchard] Extends theme.txt to allow different zones for each layer fixes #5933 (#5942)
While I understand the motivation behind the feature,I don't think themes should know anything about layers, or layers about zones. The same result could be obtained in a cleaner way buy having the widget editor be aware of multiple layouts, with different zones, whether those layouts are statically defined in the theme or dynamically built.

Reply to this email directly or view it on GitHub:
https://github.com/OrchardCMS/Orchard/pull/5942#issuecomment-149263012

I am not totally satisfied with all the layout story: to much fragmentation, too much complicated, no way to changes the files with text editor, not in phase withe zone (everything goes in content). This solution is enough for me, I get the options to put widgets where I want and I can write my theme and layout as I need.

My solution is easy to implement: 10 lines in the pr and it preserves all the existing features.

The issue is that it also mixes concepts that shouldn't. As Bertrand said the layers should not know about zones, and themes should not know about layers. What you are trying to do is just limit the list of zones visible for each layers. That's going right against the initial goal of the feature which is to let you define some content for a zone (any zone) based on a rule. And the fact that you don't want to provide all the zones for specific layers is a very special case.
I understand what you are trying to do, and I could see some better ways to do it. Like first define some alternates on Layout per layer. Like Layout-Homepage.Layer.cshtml. And independently extend the Widgets module (not the theme manifest) to limit the names of zones available for a Theme. But this will be even more useful when the LayoutPart editor is integrated in the Widgets editor, so that users can drag and drop widgets, and also optionally define custom theme-level layouts.

It is clear that what I propose is another definition for layers and its relation with zones.
What should be and what should not, I don't know.
Concerning the all drag and drop concept for orchard, it is strange for such a product and such an audience. May be some retro futurist way when tablets are everywhere.

I am closing this PR as it's not what we want. We can continue the discussion on the issue itself.

It seems I missed the discussion ?
Where does it took place ?

Bring it up at the community meeting if you want.

No chance to have this adopted in core, even if it preserves some other way - using placement, zones and widgets, not limited to Drag&Drop - to extend Orchard without breaking everything.


ExtensionManager#getExtension() can also return null

Why ? It doesn't mke sense...

Look at the body of the function. It does return null if there is no extension defined with the given $key.

Thank you, @Lctrs! :1st_place_medal:


mem-ruby: Added support for non-system-scope atomics in VIPER

Added support for performing non-SLC-set atomics in the TCC. Previously, all atomics were being passed on by the TCC to the directory. With this change, atomics will only be passed on if the SLC bit is set or if the line isn't present or available in the TCC.
If a non-SLC atomic is passed on to the directory because it is not present in the TCC, the atomic will be performed on the return path on the Data event. To accommodate the directory not performing the atomic in this case, this change also passes the SLC bit on to the directory.
The previously-named "Atomic" action has been renamed to "AtomicPassOn", with the new "Atomic" corresponding to an atomic performed directly in the TCC.
Change-Id: Ibf92f71ddceb38bd1b0da70b0a786cc4c3cf2669

Looks good. I don't have a preference regarding the tag resource constraint since it is using what was there before.

Sure, for this patch I think it's fine.  But that does seem like a (separate) bug, no?

I looked at this and other protocols and it seems that generally transitions that stall/stallAndWait/recycle do not have any resources constraints.  Based on that, I would say the resource constraints in this PR would be extraneous comments that could be removed.

Removed those comments as extraneous per @abmerop's comment. There are additional cases where a commented-out TagArrayRead resource constraint is used, but those are on untouched transitions. Should I make another PR to remove those?

Removed those comments as extraneous per @abmerop's comment. There are additional cases where a commented-out TagArrayRead resource constraint is used, but those are on untouched transitions. Should I make another PR to remove those?

I think having a separate commit for them is fine, yeah.  Thanks @DanKouch !

I looked at this and other protocols and it seems that generally transitions that stall/stallAndWait/recycle do not have any resources constraints. Based on that, I would say the resource constraints in this PR would be extraneous comments that could be removed.

Interesting, but good to know.


add husky and lint-staged

Fixes #2353
Additional description

CONTRIBUTOR checklist (do not remove)
Please complete for every pull request

[x] First-time contributors should sign the Contributor License Agreement.  If you haven't before, wait a few minutes and a bot will comment on this pull request with instructions.
[x] npm run lint:fix has been run and linting passes.
[x] Mocha, Jest (Storyshots), and components/component-docs.json CI tests pass (npm test).
[x] Tests have been added for new props to prevent regressions in the future. See readme.
[x] Review the appropriate Storybook stories. Open http://localhost:9001/.
[x] Review tests are passing in the browser. Open http://localhost:8001/.
[x] Review markup conforms to SLDS by looking at DOM snapshot strings.

REVIEWER checklist (do not remove)

[ ] TravisCI tests pass. This includes linting, Mocha, Jest, Storyshots, and components/component-docs.json tests.
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

Required only if there are markup / UX changes

[ ] Add year-first date and commit SHA to last-slds-markup-review in package.json and push.
[ ] Request a review of the deployed Heroku app by the Salesforce UX Accessibility Team.
[ ] Add year-first review date, and commit SHA, last-accessibility-review, to package.json and push.
[ ] While the contributor's branch is checked out, run npm run local-update within locally cloned site repo to confirm the site will function correctly at the next release.

@interactivellama please have a look

@nik72619c  thanks for your review please go through this article
https://docs.npmjs.com/files/package-locks#using-locked-packages
this will help you

@davidlygagnon Could you review this PR?  Thanks a lot!

PR looks good but one thing to note:
Here's the output that I get when testing linting a file that had a lint error:

Seems that husky requires node > 10 ? DSR package.json engines stills stays it supports version node 8 so that won't work for those who are still on that version. I ran into this problem first. My version of node was 8.x an npm install passed but husky never ran the pre-commit hook afterwards on git commit. I had to re-install on node > 10.

@garygong looks good to me, ready to merge unless the above is an issue.

I see the message Husky requires Node 10 too. I'll update the project to use Node 10, and then come back to merge this PR. Thanks!

I pushed a simpler config.  Thanks for working on this!


New package: YARC.YARCLauncher version v1.0.1

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue? - close #189966 - Replace #189996

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Verify:


tag names are not semver compliant

Can tag names be semver compliant? This will allow anyone to do a go get against a specific version of kcptun instead of fetching latest or pseudo version (such as go get github.com/xtaci/kcptun v0.0.0-20190611073203-bf635db2f952).
I do see the usage of go modules, but having a semver compliant tag will make it easy for users to consume specific versions of kcptun.

it's not a library, no package will depend on this one, so semver is not important


Asserts

Adding assorts that check in debug mode if function arguments respect the size of the matrix

Coverage remained the same at 100.0% when pulling 20c19d646b049eec2e4caf0d7860000c4d3f1458 on kamilritz:asserts into 2f6398168d04451998cbb60b44d7f4898279caf0 on PX4:master.

I can confirm that it builds with ARM toolchain. tested with fmu v2


Could not find block when fork network

🐛 Bug Report for zkSync Era In-Memory Node
📝 Description
I am trying to fork mainnet with command era_test_node fork mainnet
But always get this error
thread 'main' panicked at src/fork.rs:311:17:
Could not find block #16665656 (0x4cc58c0d37f08bf24a1c83b61ce41b878e1d00d8295fce3e10258ecc3c246dfd) in "https://mainnet.era.zksync.io:443"

Also try to put the --fork-at argument but still get the same err
Failed with era_test_node fork testnet too
🖥 Environment

era-test-node version: era-test-node-v0.1.0-alpha.7-aarch64-apple-darwin.tar.gz
Operating System & Version:  macOS 12.2

📎 Log Output
RUST_BACKTRACE=full era_test_node fork mainnet
thread 'main' panicked at src/fork.rs:311:17:
Could not find block #16666275 (0xcbb4282a22169d8a441a0b9db0d40168cc639c4c724ee20a4bd0e3a1dd33a2e2) in "https://mainnet.era.zksync.io:443"
stack backtrace:
   0:        0x1013a3050 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h6d4268b2ed62fb94
   1:        0x1013c2148 - core::fmt::write::h5d55d44549819258
   2:        0x1013a0310 - std::io::Write::write_fmt::hc515897f91abd6cf
   3:        0x1013a2e90 - std::sys_common::backtrace::print::h2c300c1ebedfc73c
   4:        0x1013a44f0 - std::panicking::default_hook::{{closure}}::h0aa9be5c44269370
   5:        0x1013a421c - std::panicking::default_hook::h2c0ef097934ee9e6
   6:        0x1013a4a38 - std::panicking::rust_panic_with_hook::h84c8637cb6e56008
   7:        0x1013a4944 - std::panicking::begin_panic_handler::{{closure}}::h25482adda06c7b7f
   8:        0x1013a34dc - std::sys_common::backtrace::__rust_end_short_backtrace::h0c6f3beb22324a29
   9:        0x1013a46a8 - _rust_begin_unwind
  10:        0x1014083f8 - core::panicking::panic_fmt::h9072a0246ecafd14
  11:        0x100b244ac - era_test_node::fork::ForkDetails<era_test_node::http_fork_source::HttpForkSource>::from_url_and_miniblock_and_chain::{{closure}}::hd3ba8f26c6e44228
  12:        0x100b2fcc0 - era_test_node::main::{{closure}}::h0ce5ccbd3dc13c11
  13:        0x100b16c5c - tokio::runtime::park::CachedParkThread::block_on::he9a238f63f232a69
  14:        0x100b19c30 - tokio::runtime::context::runtime::enter_runtime::h233e6973428e368c
  15:        0x100b6d3d0 - tokio::runtime::runtime::Runtime::block_on::h356f5473fded66eb
  16:        0x100b2f128 - era_test_node::main::heb6ea11c4cadf0b6
  17:        0x100b5d3dc - std::sys_common::backtrace::__rust_begin_short_backtrace::hd51efb66eb19a7b0
  18:        0x100d260cc - std::rt::lang_start::{{closure}}::h3bd6d8a7b9171166
  19:        0x10139a720 - std::rt::lang_start_internal::hadaf077a6dd0140b
  20:        0x100b31a30 - _main

This might be related to the latest release of zksync-era upstream... I'll take a closer look and we'll probably have to update the version again to match. If this is the case, I'll start a new release to get this fixed for everyone


why c++?

hi, can I ask why the devs chose c++ for making this browser in this day and age where we have rust, zig, go, swift, etc.. which are safe and modern. the government declared c++ deprecated and unsafe https://www.whitehouse.gov/wp-content/uploads/2024/02/Final-ONCD-Technical-Report.pdf

Please do not spam this issue tracker with non-issues.

im very sorry @awesomekling , where is more appropriate please for me to discuss or ask this?

If you're truly curious, come chat in the discord, in the #off-topic channel(s). The short answer is: the project began five years ago, and the developers are extremely familiar with C++.

hi thanks for responding, could you send the discord invite link?

https://github.com/LadybirdBrowser/ladybird?tab=readme-ov-file#get-in-touch-and-participate

i'm sorry @awesomekling is there a more appropriate place for me to discuss / ask this?

i just heard about this project and also felt a sock when i saw the usage of the buggy C++, but i figured out that the project may have been old and you confirmed it. Thanks for your efforts anyways.


Support Laravel 10 and remove abandoned dependency

Can this package get updated to support Laravel 10 and remove the laravecollective/html dependency because it's abandoned?
The replace package is spatie/laravel-html.
Issue:
jeremykenedy/laravel-users v4.3.0 requires laravelcollective/html (^5.4|^5.5|^5.6|^5.7|^5.8|^6.0|^7.0|^8.0)
Package laravelcollective/html is abandoned, you should avoid using it. Use spatie/laravel-html instead.

It seems to work fine on other projects that use this with Laravel 10


Add abstract location model

User Stories
As Nelly the Network Engineer,
I want...

A more flexible way to define locations and hierarchy of locations within Nautobot

So that...

I can replicate the location structure of my organization and store a variety of network related assets in Nautobot that may not be racked.
I can store a variety of network related assets in Nautobot that may not be racked (ie. UPS in a room)

I know this is done when...

Users can assign a "Location" to any other object that references Region and Site today

Assigning of Locations is consistent within child/parent relationship (honors existing Site/Region)

Users can see the new "Location" in the associated object list and detailed views for objects that are linked to the Location

Austin the Network Automation Engineer
I want…

To provide my own definitions of locations and pattern for location types
Enforce location hierarchy within my organization

So that…
MVP

I can custom model my facilities by providing my own set of attributes for Location Types (ie. buildings)
Location must either be parented by another Location or a Site (breaking change long term Site, Region, RackGroup would become LocationTypes)
Locations can only have one parent
Simple content type restriction on LocationType (Devices can only be assigned to a cabinet but not a city)
I can attach address or any other physical characteristics to my LocationType model

Can be implemented via custom fields
Will NOT require scoping custom fields down to specific LocationTypes (see: https://github.com/nautobot/nautobot/issues/899, https://github.com/nautobot/nautobot/issues/889)

Objects & locations are expected to validate that they are in the same site, region as their parent
Mandating custom attributes for specific location types would most likely need to be implemented as a custom validator

Future

Location must either be parented by another Location or none (Site, Region, RackGroup become LocationTypes)
Locations can have many parents
I can enforce my users to populate mandatory attributes for given Types of Locations
I can enforce my users to use Location Tree of my definition (ie. City -> Building -> Floor -> Room, but never “City -> Room”). Would be nice if I could use custom validators for this to be more flexible.
Location must either be parented by another Location or a Site (breaking change long term Site, Region, RackGroup would become LocationTypes)
Config context filtering by location
Location statuses

I know this is done when...

I can register my own LocationType via Nautobot plugin
I can code my own LocationTypes for custom attributes shown in the UI, API, GraphQL
I can enforce hierarchy
I can enforce mandatory attributes for specific locations

Questions

What will the migration strategy be for an eventual forced relationship to a location model

Additional Context
For more context, please see #613 and #230
This issue will supersede #613 and #230 (eventually replace) and provide a foundation for a new abstract organizational model. In the short-term, a new location model (that includes location type) is proposed that links to all objects that already link to region and site.  Similar to region, this will be an optional attribute users can take advantage to further define the location relationship to other objects.

I loveeeeee this idea.
Imagine having Site and Region instead be Location(type=LocationType("site")) and Location(type=LocationType("region")), where RegionType could be a parent of SiteType. Objects that link to a Site today, could be linked to a Location tomorrow.
This could open the door for a myriad of custom locations like:

Region (US-west)

Site (LAX)

Facility (LAX1)

Cluster (LAX1a)

Room (LAX1a-CR1)

Site (SJC)

etc...
I think concerns here would be

When we introduce this? Like do we introduce it in v1.x and start providing it as an optional alternative

If we do this, do we allow assignment of an object to either a Site/Region OR a Location but not both?

Should we think about other types of "locations" such as clusters/pods?

i.e. What about rack groups or other groupings that represent physical placement of hardware?

How do we migrate legacy Region/Site/other "location" objects to the new data model once we go all in on it (such as in v2.0.0)? Automatically? Through some kind of guided upgrade process? #YOLO?

We should probably have a flag or mechanism on a LocationType to designate which types of resources are allowed to be assigned to a location. For instance, as a user I would want to make sure a device cannot be assigned to a LocationType for regions. Prefixes, though, I might allow in this case.

When we introduce this? Like do we introduce it in v1.x and start providing it as an optional alternative

Yes.

If we do this, do we allow assignment of an object to either a Site/Region OR a Location but not both?

I would think both for now.

Should we think about other types of "locations" such as clusters/pods?

I'm not following this.  As this is proposed now, this would just be wherever there is region/site today, there would now be location.  Wouldn't add more to it than that for now.

How do we migrate legacy Region/Site/other "location" objects to the new data model once we go all in on it (such as in v2.0.0)? Automatically? Through some kind of guided upgrade process? #YOLO?

Don't know.  But automatically would be the intention.  I think it's too early to define that because we don't know what the end-state would be.

We should probably have a flag or mechanism on a LocationType to designate which types of resources are allowed to be assigned to a location. For instance, as a user I would want to make sure a device cannot be assigned to a LocationType for regions. Prefixes, though, I might allow in this case.

This makes sense.

Any thought about rebranding 'Rack Groups' for this purpose? Many users will be using rack groups in this way currently and seems to achieve the goal with out adding additional models :)

I think Rack Groups are only part of proposed Location functionality. There is big overlap on both sides, but it does not cover all the functionality.
For our use case we need to know location of Racks and Devices, but we cannot assign a Device to a Rack Group. The workaround now is to create "group" Rack with size 1 (minimum) for each Rack Group and assign non-racked devices there. This is used for example for storage room (not in production) or for devices not in any rack at all but running in production. This is where Location completely replaces Rack Group. It allows us to physically find the device.
But Rack Groups are still very much usable even when Location is introduced. They provide easy way to see elevation of multiple racks at once. An example where we use this is server room with 6 rows of racks. We have Rack Group for each of the row which allows us to see elevation of just 10 racks instead of 60. Separate Location for each row does not make much sense.

@jedelman8  - is this moving along? We have some pretty serious need for a more flexible model. Eg we want to be able to create locations like 'vpc' and 'room,' and we wan tto be able to assign prefixes to any location object. I think we've discussed this before.
Is there a target version?

Region (US-west)

Site (LAX)

Facility (LAX1)

Cluster (LAX1a)

Room (LAX1a-CR1)

Site (SJC)

This structure follows our requirement - the model would allow to represent physical location of the device/unit.
Once I agree with majority of the comments here, I'm thinking we should provide some Location types via Core:
LocationType("Rack"), LocationType("Region"), LocationType("Site") so that for the Core provided structures we are able to properly represent them as well.

[ ] Has the ability to have "Type"
[ ] #1638
[ ] #1711

@itdependsnetworks  @jdrew82
This is an important feature for our Service Provider type use cases where Nautobot centers around a Datacenter / Campus model currently, but looking beyond that in a situation where we have hundreds of DC's in multiple States, Cities, Markets, and customer premise gear tied back to those DC's, DC's tied back to other DC's across states in some cases, having more flexibility would be very helpful.

Initial Locations implementation was done by #1891. Known remaining action items for 1.4.0:

[ ] Evaluate whether to commit to proceed with django-tree-queries for Location and LocationType models or revert to django-mptt patterns instead (see comments on #1891 and #510)
[ ] Implement a pattern for filtering Locations by base_site (which is a derived attribute, not a database field) so that for example when selecting a related Site while editing an object, the Location selection menu can filter to only display Locations that exist within that Site.
[ ] Polish up the documentation around LocationType and Location

If we're committing to merging Region and Site into Locations in 2.0, let's state that more firmly in the docs
Possibly update the Regions user guide to include creation of LocationTypes and Locations
Update docs relating to tenancy and Locations (explicitly state that a Location may have a Tenant, etc.)

[ ] Evaluate database indexes on LocationType and Location to see if we need to add any explicit db_index=True, etc.
[ ] Evaluate UI/UX around Location usage, in particular how select dropdowns present the Location hierarchy or obscure it depending on permitted content-types per LocationType.

Longer-term action items:

[ ] Revisit how tree models are presented in UI list views (particularly as regards filtering of the list), possibly use JSTree or a similar library instead of django-tables2 for these models.

Initial Locations implementation was done by #1891. Known remaining action items:

[x]  Evaluate whether to commit to proceed with django-tree-queries for Location and LocationType models or revert to django-mptt patterns instead (see comments on Prototype Locations implementation #1891 and Django MPTT is no longer maintained - Migrate Existing Models to django-tree-queries #510)

[x]  Implement a pattern for filtering Locations by base_site (which is a derived attribute, not a database field) so that for example when selecting a related Site while editing an object, the Location selection menu can filter to only display Locations that exist within that Site. (tracked as Need a UI pattern for filtering tree models by parent #2518)

[x]  Polish up the documentation around LocationType and Location

If we're committing to merging Region and Site into Locations in 2.0, let's state that more firmly in the docs (Epic: Collapse Region and Site models into Location #2517)
Possibly update the Regions user guide to include creation of LocationTypes and Locations
Update docs relating to tenancy and Locations (explicitly state that a Location may have a Tenant, etc.)

[x]  Evaluate database indexes on LocationType and Location to see if we need to add any explicit db_index=True, etc.

[x]  Evaluate UI/UX around Location usage, in particular how select dropdowns present the Location hierarchy or obscure it depending on permitted content-types per LocationType.

Longer-term action items:

[ ]  Revisit how tree models are presented in UI list views (particularly as regards filtering of the list), possibly use JSTree or a similar library instead of django-tables2 for these models. (tracked as Revisit how tree data models are presented in "list" views #2516)

All remaining actions have now been resolved.
#2516 will come in as a UX improvement for the UI overhaul.


Adding groovy discovery plugin and npm-groovy-lint tool plugins.

Codecov Report

Merging #32 (282b38a) into main (ee307fb) will decrease coverage by 1.06%.
The diff coverage is 88.17%.

@@            Coverage Diff             @@
##             main      #32      +/-   ##
==========================================
- Coverage   93.38%   92.32%   -1.07%
==========================================
  Files           7        9       +2
  Lines         363      456      +93
==========================================
+ Hits          339      421      +82
- Misses         24       35      +11

Impacted Files
Coverage Δ

...statick_web/plugins/tool/groovylint_tool_plugin.py
84.28% <84.28%> (ø)

...k_web/plugins/discovery/groovy_discovery_plugin.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee307fb...282b38a. Read the comment docs.

Closing in favor of adding these plugins to the main statick repo: https://github.com/sscpac/statick/pull/370


support go fmt

integrate go fmt as an analyzer

so it is impossible to use go fmt as a lib without hard fork, I'm goin to use a hard for of from the gofumpt linter: https://github.com/mvdan/gofumpt/tree/master/go1.19/go/format

when it is released, don't want to use master branch

after deep analyzing the existent forks of the gofmt tool I decided to drop the integration with gochecker, it is much easier to run go fmt in parallel with gochecker


[Documentation] Solvcon shocktube document url can’t arrive

Type

[ ] Content inaccurate
[x] Content missing
[ ] Typo

URL

shocktube1dcalc/cese.py
shocktube1dcalc/solver_analytic.py
Description

The cese & shocktube reference url in docstring can’t arrive.

Thank you for reporting the issue. I will have a look.

The page of the url pointing to is outdated, so let me just remove it.


Chip onDelete bug with firefox

As a user using Firefox (73.0.1), when I tab onto a Chip and it has focus, then hit the "delete" key on my keyboard, I would expect the onDelete function to get fired. However, it does not. Instead the browsers "back navigation" happens and I am brought back to the previous web page.
This works as expected in Chrome (80.0.3987.100), fyi.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Focus via keyboard tabbing a Chip with an onDelete prop
Press keyboard "delete" key
Browsers back navigation occurs instead of onDelete function

Expected Behavior 🤔

Focus via keyboard tabbing a Chip with an onDelete prop
Press keyboard "delete" key
onDelete function gets fired

Steps to Reproduce 🕹
https://codesandbox.io/s/material-demo-tbp09
Steps:

Focus via keyboard tabbing the Chip with an onDelete prop
Press keyboard "delete" key
Browsers back navigation occurs instead of onDelete function

Context 🔦
This is an accessibility bug that should be resolved to give keyboard users the same experience.
Your Environment 🌎

Tech
Version

Material-UI
v4.9.5

React
v16.10.1

Browser
Firefox v73.0.1

TypeScript
v3.8.3

MacOS
v10.15.3

Which OS? On ubuntu I can't reproduce Delete triggering back navigation. This is with 73.01 though.
Is this within an incognito window or do you use any extensions?

This is on MacOS 10.15.3. I also just updated my firefox to 73.0.1 and am seeing the same behavior.

Huh, this was at least at some point the default behavior. Seems like they brought it back.
Can you observe the same behavior on https://codesandbox.io/s/material-demo-z96m3?
I guess we should prevent the default on any key we handle and trigger an action anyway.

Though I can reproduce this on macOS and firefox with Backspace I can't with Delete. But the reason is the same so once we fix it, we fix both cases.

Thank you for fixing this! <3


keep tls config in sync with msdsn host

Fixes #482
p.TLSConfig here is a pointer back to the original config, so we shouldn't overwrite its contents in this retry loop. Otherwise the TLSConfig.ServerName doesn't match p.Host on new connections for the first Handshake call.
@kardianos  once this is in can you create a 0.10.1 release for the AKS team at Microsoft to consume?
They want to pick up an official release with the fixes for bad connection marking.

@denisenkom @kardianos hi can we get this change reviewed and merged soon? It's a regression introduced when the msdsn package was added.

would love to see this get merged, it's preventing us to upgrading to a newer version
a new release would be great also!


Add small district-drawing features.

Allow users to change the font size of district numbers; get representative points instead of centroids.

Closed to be included with another PR.


Document header not shown if undefined placeholders are used

Looks like the asciidoctor-pdf will not print the header at all if placeholders are used that are not defined.
Wouldn't it be better to use an empty string for placeholders that could not be replaced?
e.g.
extends: default
header:
  height: $base_line_height_length * 3
  verso:
    left:
      content: '{doctitle} {version}'

:pdf-style: theme.yml
= Title

<<<

second page

Will render as:

instead of (my expectation):

No, this design is intentional.

If you reference an attribute which is not defined, all the text on that same line in the running content will be dropped. This feature allows you to have alternate lines that are selected when all the attribute references are satisfied.
https://github.com/asciidoctor/asciidoctor-pdf/blob/main/docs/theming-guide.adoc#attribute-references

If you want to ensure the running content is always displayed, then you need to include at least one line in which all attributes are resolved. Here's an example:
header:
  verso:
    left:
      content: |
        {blank}
        {doctitle} {version}

or
header:
  verso:
    left:
      content: |
        {doctitle}
        {version}

I'm not entertaining a proposal to change this design right now.


End offset for compatibility characters is not incremented with ICUNormalizer2CharFilter

Description
This issue comes from https://github.com/elastic/elasticsearch/issues/50008.
When tokenizing combining characters (ex. ㋀) after applying the char filter icu_normalizer, end offset of combining character is not incremented correctly.
The test which I added in TestICUNormalizer2CharFilter failed.
public void testTokenStreamCombiningCharacter() throws IOException {
  String input = "日日㋀日"; // ㋀ is the combining character
  CharFilter reader =
      new ICUNormalizer2CharFilter(
          new StringReader(input),
          Normalizer2.getInstance(null, "nfkc_cf", Normalizer2.Mode.COMPOSE));

  Tokenizer tokenStream =
      new ICUTokenizer(newAttributeFactory(), new DefaultICUTokenizerConfig(false, true));
  tokenStream.setReader(reader);

  assertTokenStreamContents(
      tokenStream,
      new String[] {"日", "日", "1", "月", "日"},
      new int[] {0, 1, 2, 3, 4}, // test pass if changed to {0, 1, 2, 2, 3}
      new int[] {1, 2, 3, 4, 5}, // test pass if changed to {1, 2, 2, 3, 4} (end offset for the word `1` is not incremented)
      input.length());
}

$ ./gradlew test --tests org.apache.lucene.analysis.icu.TestICUNormalizer2CharFilter.testTokenStreamCombiningCharacter
org.apache.lucene.analysis.icu.TestICUNormalizer2CharFilter > testTokenStreamCombiningCharacter FAILED
    java.lang.AssertionError: endOffset 2 term=1 expected:<3> but was:<2>

Version and environment details

macOS 12.3.1
openjdk 17.0.5

https://github.com/apache/lucene/issues/9820 issue could be related.

The test is wrong: the startoffsets are correct. input stream is 4 characters long.
I would expect: 0, 1, 2, 2, 3 for startoffsets and 1, 2, 3, 3, 4 for endoffsets.
both 1 and 月 should have same offsets as they come from same input character ㋀
nothing needs to go backwards. #9820 is not related and just a catch-all for misunderstandings about offsets.
Test/issue should not be named "combining character" as there are no combining characters involved. "combining character" has a very specific meaning in unicode and this is not that.

Here is my suggested test:
diff --git a/lucene/analysis/icu/src/test/org/apache/lucene/analysis/icu/TestICUNormalizer2CharFilter.java b/lucene/analysis/icu/src/test/org/apache/lucene/analysis/icu/TestICUNormalizer2CharFilter.java
index c84b8c6887e..f9febbb1d0d 100644
--- a/lucene/analysis/icu/src/test/org/apache/lucene/analysis/icu/TestICUNormalizer2CharFilter.java
+++ b/lucene/analysis/icu/src/test/org/apache/lucene/analysis/icu/TestICUNormalizer2CharFilter.java
@@ -25,6 +25,8 @@ import org.apache.lucene.analysis.Analyzer;
 import org.apache.lucene.analysis.CharFilter;
 import org.apache.lucene.analysis.Tokenizer;
 import org.apache.lucene.analysis.core.KeywordTokenizer;
+import org.apache.lucene.analysis.icu.segmentation.DefaultICUTokenizerConfig;
+import org.apache.lucene.analysis.icu.segmentation.ICUTokenizer;
 import org.apache.lucene.analysis.ngram.NGramTokenizer;
 import org.apache.lucene.index.IndexWriter;
 import org.apache.lucene.tests.analysis.BaseTokenStreamTestCase;
@@ -666,4 +668,23 @@ public class TestICUNormalizer2CharFilter extends BaseTokenStreamTestCase {
       checkAnalysisConsistency(random(), a, false, new String(text));
     }
   }
+
+  public void testDecomposeFromSameInputCharacter() throws IOException {
+    String input = "日日㋀日"; // ㋀ will decompose (compatibility character)
+    CharFilter reader =
+        new ICUNormalizer2CharFilter(
+            new StringReader(input),
+            Normalizer2.getInstance(null, "nfkc_cf", Normalizer2.Mode.COMPOSE));
+
+    Tokenizer tokenStream =
+        new ICUTokenizer(newAttributeFactory(), new DefaultICUTokenizerConfig(false, true));
+    tokenStream.setReader(reader);
+
+    assertTokenStreamContents(
+        tokenStream,
+        new String[] {"日", "日", "1", "月", "日"},
+        new int[] {0, 1, 2, 2, 3},
+        new int[] {1, 2, 3, 3, 4},
+        input.length());
+  }
 }

Thanks!

both 1 and 月 should have same offsets as they come from same input character ㋀

I run your suggested test and it failed. I am not sure this is the bug or not.
The end offset of character 1 is 2 (expected offset is 3).
$ ./gradlew test --tests org.apache.lucene.analysis.icu.TestICUNormalizer2CharFilter.testDecomposeFromSameInputCharacter
...
org.apache.lucene.analysis.icu.TestICUNormalizer2CharFilter > testDecomposeFromSameInputCharacter FAILED
    java.lang.AssertionError: endOffset 2 term=1 expected:<3> but was:<2>
...

Test/issue should not be named "combining character" as there are no combining characters involved. "combining character" has a very specific meaning in unicode and this is not that.

I changed the issue title from "combining character" to "compatibility character"
㋀ seems enclosed CJK letters and months in unicode.

Yes, I think it is a bug. But I dont know this char filter well, so I haven't tried to debug it.
Charfilter is much more complicated due to incremental processing and offset correction, so maybe you can use the tokenfilter instead as a workaround

Ok, I tried to use tokenfilter instead.
The compatibility character (㋀) is not tokenized in icu_tokenizer and excluded from the result.
It seems that the compatibility characters need to be normalized before tokening texts.

Elasticsearch request

$ curl "http://${ES_URL}/_analyze?pretty" \
 -H 'Content-Type: application/json' \
 -d '{"tokenizer" : "icu_tokenizer", "char_filter" : [], "filter": ["icu_normalizer"], "text" : "日日㋀日", "explain": true}'
{
  "detail" : {
    "custom_analyzer" : true,
    "charfilters" : [ ],
    "tokenizer" : {
      "name" : "icu_tokenizer",
      "tokens" : [
        {
          "token" : "日",
          "start_offset" : 0,
          "end_offset" : 1,
          "type" : "<IDEOGRAPHIC>",
          "position" : 0,
          "bytes" : "[e6 97 a5]",
          "positionLength" : 1,
          "script" : "Chinese/Japanese",
          "termFrequency" : 1
        },
        {
          "token" : "日",
          "start_offset" : 1,
          "end_offset" : 2,
          "type" : "<IDEOGRAPHIC>",
          "position" : 1,
          "bytes" : "[e6 97 a5]",
          "positionLength" : 1,
          "script" : "Chinese/Japanese",
          "termFrequency" : 1
        },
        {
          "token" : "日",
          "start_offset" : 3,
          "end_offset" : 4,
          "type" : "<IDEOGRAPHIC>",
          "position" : 2,
          "bytes" : "[e6 97 a5]",
          "positionLength" : 1,
          "script" : "Chinese/Japanese",
          "termFrequency" : 1
        }
      ]
    },
    "tokenfilters" : [
      {
        "name" : "icu_normalizer",
        "tokens" : [
          {
            "token" : "日",
            "start_offset" : 0,
            "end_offset" : 1,
            "type" : "<IDEOGRAPHIC>",
            "position" : 0,
            "bytes" : "[e6 97 a5]",
            "positionLength" : 1,
            "script" : "Chinese/Japanese",
            "termFrequency" : 1
          },
          {
            "token" : "日",
            "start_offset" : 1,
            "end_offset" : 2,
            "type" : "<IDEOGRAPHIC>",
            "position" : 1,
            "bytes" : "[e6 97 a5]",
            "positionLength" : 1,
            "script" : "Chinese/Japanese",
            "termFrequency" : 1
          },
          {
            "token" : "日",
            "start_offset" : 3,
            "end_offset" : 4,
            "type" : "<IDEOGRAPHIC>",
            "position" : 2,
            "bytes" : "[e6 97 a5]",
            "positionLength" : 1,
            "script" : "Chinese/Japanese",
            "termFrequency" : 1
          }
        ]
      }
    ]
  }
}

yes, normally composed/decomposed (NFC vs NFD) does not change tokenization. so you may do it before or after, doesn't matter.
but compatibility characters like this don't really work well in unicode for text processing: they are just really for compatibility/round-trip. you have to apply NFKC/D first before you can really do anything with them. Maybe for now, normalize documents before you send them to elasticsearch.

I debugged the issue, the problem is not this particular charfilter, instead the issue impacts all charfilters.
Think about this single-character string: "㋀"
Our charfilter turns it into two characters: "1" and "月"
we would expect the offsets to look like this:
first token "1" at rawStartOffset=0, rawEndOffset=1 -> startOffset=0, endOffset=1
  correctOffset(0) -> 0
  correctOffset(1) -> 1
second token "月" at rawStartOffset=1, rawEndOffset=2 -> startOffset=0, endOffset=1
  correctOffset(1) -> 0
  correctOffset(2) -> 1

As you can see, the bug is in the whole charfilter api of "correctOffset". Because we need correctOffset(1) -> 1 for the endoffset of the first token, but we need correctOffset(1) -> 0 for the start offset of the second token.
I can't see any way to fix this, without fixing actual charfilter api (e.g. supporting two separate methods: correctStartOffset() and correctEndOffset())
Sorry for the bad example/explanation. Another example would be a charfilter that converts æ to ae. a's endoffset of 1 needs to remain 1 after correction, but e's startoffset of 1 needs to be corrected to a 0.


categorize missing dominant.veg

vegtype was not classified in GROA, and therefore those records are not useable for many analyses (e.g., see this issue). This is a piece of information that can easily be pulled from the primary literature.

@Troger4 , I mentioned this task to you over the phone. Here are the instructions:
Work with the ForC_measurements file. (Reminder: please be sure not to re-order the file, or sort back to original order (by measurement.ID) before pushing.)
The goal is to fill in missing values in dominant.veg. You will use the codes in ForC_pft.csv
Records with "NAC" in dominant.veg and some content in veg.notes
For these, there is no need to access original pubs.

veg.notes will typically contain species name(s). Do a web search to look up the species, and determine the appropriate description. You'll need to determine whether the species is broadleaf of needleleaf (conifer) and whether it is evergreen or deciduous (including both drought and cold deciduous, fully or semi-decidious). For example, a broadleaf evergreen species would get the code "2TEB"
If more than one species is listed, look up all (or enough to determine PFT type). For example, a broadleaf deciduous and neeldleaf evergreen mix would get the code "2TM"
Fill in the appropriate code in dominant.veg.

Records with "NAC" in dominant.veg and no content in veg.notes
This will require accessing original pubs.
(I will provide instructions for this later.)


Integration Test - Release - 2019/02/13 18:47:38

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#backlog'

#pri2


Environment variables support.

this gives the ability to pass unlimited env variables programatically

Awesome. Released in 1.2.0


Wandb Request

Is it possible to add a WandB API for the validation feedback?
Having a simple validation inference every (x) minutes/steps/epochs can be great too, Thank you

As far as I know, there is support for tensorboard, just point the tensorboard logdir to the output folder of your training.


Detections

Hello, I have a problem. It turns out that it's complicated for me to infect the victim and they also always lose trust because the Windows Defender detects that there is a virus and it can no longer be infected. Also, the total virus has about 20 detections and when it is downloaded, the antivirus removes it.

By the way but there a thing that scares me. The thing is sometimes the grabber randomly grabbs someone that i never send the .exe for exemple this guy:

When you upload a file to virustotal, it runs the file in their virtual system for dynamic analysis. So this info you got is of that system.
Also, when you upload the file on virustotal, the website shares the signature of the file with other antiviruses. So even those antiviruses which haven't seen the file yet, start detecting it. So I'd recommend you not to upload files on virustotal that you made on your PC.
As for the number of detections, there is nothung much we can do. Unless signed with a real certificate, virustotal even detects legitimate softwares as viruses too. Thats how it goes. I hope you understood what I said.


ERROR: Cannot do the operations. Status - Out of Resources

On some virtual environments, the following error is observed:
ERROR: Cannot do the operations. Status - Out of Resources
The issue results from an empty \EFI\BOOT\bbr\SCT\Data\TestCase.ini file, which causes the SCT to display the Out of Resources error and immediately exit. TestCase.ini is normally populated with data about the test cases that are supposed to be run.
When the file is first zeroed out, SCT hangs with no error message.
The following triggers the issue::

Run the SBBRRuntimeServicesBBTestFunction  test (GUID E8C528DE-4B69-4C6B-AAEC-69645969266F) see code

After completion, SCT calls SaveTestCases() (within ContinueExecuteStart() since the NVRAM test cold resets halfway through execution).

Within SaveTestCases(), EfiIniFlush() is called. TestCase.ini appears to be zereod out inside this function, specifically line 1356. This line writes to the EFI_FILE_HANDLE provided as an argument to the function, which is presumably TestCase.ini.

The relation between the SBBRRuntimeServicesBBTestFunction   test and TestCase.ini being zeroed out is unclear. ACS automatically runs to completion when the SBBRRuntimeServicesBBTestFunction test is excluded. When the SBBRRuntimeServicesBBTestFunction test is run on its own, it succeeds, then SCT hangs.

Also, the test SBBRRuntimeServicesBBTestFunction does not seem to be adding any value, and is redudnant, as the UEFI variables rules (including NV variables) are already covered in the SCT tests upstream on TianoCore. Maybe this test should simply be removed?


Ad-hoc recording support?

As my testing Vlc.DotNet samples repo, there is no ad-hoc recording feature.
I would like to know, it is support ad-hoc recording feature like VLC Player?

[x] Continuous recording is working.
[ ] Ad-hoc recording support?

Thank you so much for your effort.

As far as I know, this belongs to the features that are reserved for VLC and that aren't exposed to libvlc


CHANGELOG: update for 0.6

No new major issues have popped up due to the new features/changes in the new version so lets release it! :tada:

Yes :+1:


Players can do more than one quest at once

How do I make it so they can only do one quest at once? they are doing like 10 quests at once.

max-quests https://github.com/PikaMug/Quests/wiki/2-‐-Configuration#configyml


fix processing of the operator option of the MATCH predicate

The operator option was silently ignored.
Relates to https://github.com/crate/crate/issues/7575.

backported to 3.0 via https://github.com/crate/crate/commit/399a1f8c22a40d022de3de0c1f42c8ed6a746bf1


Unable to ignore change capacity on autoscaling_group resource

Is your request related to a problem? Please describe.
We have Autoscaling groups that change capacity with cloudwatch triggers, so every time terraform plan find changes.
Now it's impossible to modify this behaviour because lifecycle is embedded inside module
Describe the solution you'd like.
Inject lifecycle on autoscaling resource so we can add ignore_changes  like this  ignore_changes  = ["desired_capacity"]

if you update your ASGs to use desired_capacity = null this should do the trick. unfortunately we cannot parameterize the lifecycle values and this change would cause disruption for users. its been a long requested feature from Terraform so 🙏🏼 hopefully it comes one day soon

@bryantbiggs doesn't work if you also use min_size and max_size. At least not for me. You can't set those to null.


ocamlPackages.irmin: 3.4.1 → 3.5.1

Description of changes
https://github.com/mirage/irmin/blob/3.5.1/CHANGES.md
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

ligo

@ofborg build ocamlPackages.irmin


Added Email to the title of the Login field

As mentioned in RailsCasts Episode 304, having just "Login" was confusing
Changing to Login Email should allow users and devs to know what belongs in
the text field.
http://railscasts.com/episodes/304-omniauth-identity?autoplay=true

The login will not always be the email though.  For this to work would need to be dynamically customizable.


Avg transactions per week should distinguish events traced to contract factories vs standalone contracts (in legend and stack)

The goal is to have a stacked area chart that differentiates between the type of contract that is attracting transaction volume. The hypothesis is that some projects will be very popular because they have widely used factories (eg, certain DeFi and NFT minting protocols).

Currently, the ProjectEventDataProvider only provides event categories (it doesn't offer any finer grained views on what types of artifacts those events are linked to). This is P2 territory for this specific exhibit, but perhaps it should be bumped to a P1 since it will likely come up again in the future.

Moving this to grab bag. Here's the specific component that would be affected, should we choose to implement this


gittyup: 1.2.2 -> 1.3.0

Description of changes
https://github.com/Murmele/Gittyup/compare/gittyup_v1.2.2...gittyup_v1.3.0
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Tested and works fine. Also the package looks correct (e.g.: desktop file).


[AUTOPATCHER] Patches CVE-2018-25032 for zlib

        Patches CVE-2018-25032 for zlib.
        This patch and PR was automatically generated and needs human verification before merging.

Closing PR as this issue has already been resolved.


URL hosting

@shikokuchuo and @jeroen, we agreed today to start implementing #10 using https://multiverse.r-universe.org for QA and https://production.r-universe.org for production. Thanks for taking care of all that DNS stuff.
Good news: I think I solved my proxy issue. For strange reasons that I always forget, I set envvars https_proxy, http_proxy, and all_proxy. (Probably had to do with being able to install packages at work or something.) After I unset these variables, curl -v https://r-multiverse.org worked.
Other news: when I tried available.packages("https://multiverse.r-multiverse.org") and available.packages("https://production.r-multiverse.org"), both on my personal machine and my work machine, I get:
Warning: unable to access index for repository https://releases.r-multiverse.org:
 cannot open URL 'https://releases.r-multiverse.org/PACKAGES'
    Package Version Priority Depends Imports LinkingTo Suggests Enhances
    License License_is_FOSS License_restricts_use OS_type Archs MD5sum
    NeedsCompilation File Repository

You need to specify the right argument (it's not the first one):
available.packages(repos = "https://multiverse.r-multiverse.org/")

Also just to add, there are additional redirects so this returns the same:
available.packages(repos = "https://r-multiverse.org/")

We can consider whether we want to retain this or not.

Doh! :facepalm: :laughing:

We can consider whether we want to retain this or not.

If we do retain it, we might consider a redirect to https://production.r-multiverse.org.


TooManyRedirects in requests, not in urllib2

>>> url = 'http://fasel.soup.io/'
>>> len(urllib2.urlopen(url).read())
73331
>>> len(requests.get(url).content)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "build/bdist.macosx-10.7-intel/egg/requests/api.py", line 50, in get
  File "build/bdist.macosx-10.7-intel/egg/requests/api.py", line 38, in request
  File "build/bdist.macosx-10.7-intel/egg/requests/sessions.py", line 200, in request
  File "build/bdist.macosx-10.7-intel/egg/requests/models.py", line 515, in send
  File "build/bdist.macosx-10.7-intel/egg/requests/models.py", line 209, in _build_response
requests.exceptions.TooManyRedirects

I have same problem with some FaceBook pages.

This occurs only in case of HTTP 301 redirects. AFAIK, I guess this is because, upto version 0.7.5, the HTTPRedirectHandler in monkeys.py doesn't handle the exception. The chain which executes upon a HTTP 301 has nothing to do in the method responsible for it. You can add code to handle the 301 error and fetch content from the location pointed to by the response header. Correct me if i am wrong.

I am using the current release, and I am receiving this error with www.freshdirect.com/api/login. I experienced it using the headers "User-Agent": "PostmanRuntime/7.24.1", and 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36'. I have repeatedly increased the max redirect using        self.session.max_redirects = 500. I am not getting this problem when I change my user-agent using the Requestly Chrome Extension


fix(symlink): node v6 symlink resolve update

Node v6 does not resolve symlink anymore using __dirname. This pull fixes error messages like:
Module build failed: Error: "extract-text-webpack-plugin" loader is used without the corresponding plugin, refer to https://github.com/webpack/extract-text-webpack-plugin for the usage example

when node_modules is symlinked.

Please merge this :)

Please merge this :)


Fix REQUIRE on JS

On JS, when evaluating expressions via Lumen's REPL, via the -e
command-line argument, or via Lumen's scripting system, the following
scenarios now match Node's behavior:

(require "./foo") will correctly require "./foo.js"

(require "foo") will correctly perform the node_modules
lookup algorithm.

The motivation here is exactly the same as in #82, but #82 fails in
certain circumstances, such as when Lumen is installed locally via
npm. It's also simpler than #82, and more in line with Lumen's goal
of attempting to match the JS runtime as closely as possible.
This PR implements this feature in the same way as Node.js itself.
See Node.js/lib/repl.js

Here's a concrete example of the problem this solves.
Currently:
$ LUMEN_HOST=node bin/lumen -e '(print (str (require "./bin/reader.js")))'
Error: Cannot find module './bin/reader.js'

After this PR:
$ LUMEN_HOST=node bin/lumen -e '(print (str (require "./bin/reader.js")))'
(stream: function read: function read-all: function read-string: function read-table: (: function (: function ): function ": function |: function ': function `: function ,: function))

Any chance of merging this?
Without this PR:
$ LUMEN_HOST=node bin/lumen -e '(require "./bin/reader.js")'
Error: Cannot find module './bin/reader.js'

With this PR:
$ LUMEN_HOST=node bin/lumen -e '(require "./bin/reader.js")'
(stream: function read: function read-all: function read-string: function read-table: (: function (: function ): function ": function |: function ': function `: function ,: function))

require requires some hacks to match Node’s.


feat: update Windows base images to 2024.05B

What type of PR is this?
/kind feature

What this PR does / why we need it:

WS2019: May 14, 2024—KB5037765 (OS Build 17763.5820)
WS2022: May 14, 2024—KB5037782 (OS Build 20348.2461)
WS23H2: May 14, 2024—KB5037781 (OS Build 25398.887)

Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 77.013%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3032

Relevant Lines:
3937

💛  - Coveralls


Execute privilege should not be allowed on my.cnf file

Issue #461 was merged and this should be set at 0600 and not 0700. This can result in a major security flaw if the server was to be compromised and edits done to the cnf file without the user knowing. Major damage can be done a reboot if code is injected into the cnf file that can be executed.

Might also want to look at the recent security bulletin concerning this type of issue also.

@tas50 Can this get triaged up a bit? The original PR has no explanation and this is a major issue given MySQL bugs in the wild.


typescript now checks the types of catch statements

I checked and ${error} will print the toString value of the error.

If you want you can see the compile error shown in the dependabot version of this PR:
https://github.com/concord-consortium/s3-deploy-action/pull/94


Restructure the database code.

This PR accomplishes the following:

move the direct database operations out of the handlers
create a base class object that is used declaratively, and common operations
fixed the commitDB() being called mulitple times, on all requests

The most important file is database.py.  Before looking at that code, please look through the sqlalchemy documentation at below.
http://flask.pocoo.org/docs/0.10/patterns/sqlalchemy/#declarative
I hope that I didn't leave any loose ends, but if anything gets through or breaks, please let me know.

Looks great overall. Just a couple imports to clean up, but otherwise :+1:

Done.  Good catch on the overlapping imports.
@jpevarnek, please take a look here if you have a chance.  But I have to submit first, so that ethan can merge in his changes to make the app testable.

Hey there, couple things I wanted to check in about real quick on this:
So, I realize that I had the import order wrong originally already, but in __init__.py, I'm pretty sure that the order should have been functools, os, flask, flask.ext.sqlalchemy
from models import Config again seems to violate the Python style guide I'm looking at (https://google.github.io/styleguide/pyguide.html#Imports), I think we still need to clarify what guide we are using though.
database.GetFirstRecord does not return the first record.  Implementation for that would be model.query.order_by({PRIMARY KEY OF MODEL}).limit(1).all().  We should either fix the function name there or fix the implementation.  Personally, I'd just recommend deleting that function.
It looks like indentation here was varied, I'm assuming that's because I screwed up and used two-space indentation, can you confirm that?
Can you explain the reasoning for creating the separate database model and the reasoning for writing proxy functions instead of using the class methods directly?  At the moment, it's completely ignoring the configuration values for the database and is switching away from using the Flask-specific version of SQLAlchemy (except in a few places where that is still referenced).
It does not look like there is any code to handle committing the changes to existing models (e.g. changing the config will not take effect unless a new record is added/removed from something later).  Am I missing something?
Thanks!


paying a lightning node from federation fails

I am doing some tests with my mutinywallet with federations and if I send between two wallets in the same federation all is fine, but the problem is when I want to send the amount on my core lightning node.
This is the error that the wallet return

This is the invoice: lnbc100n1pnyr0gvdqqpp5pqun46arwmwfvpypf3v7lnq8vnpt5yfawvn2aeshn8zpsvpllxfqsp5jjdctxk4u5scl4q9saw0408m0szpelcx7ewusygjdu7qz9hdw04s9qrsgqcqpjnp4qwd96x2u6rgg5mjvrdh5cs989pm3tyh869rk53u2mz9hnux85par6xqyz5vqrzjqte649ct9zh8ecjylt7w3a5d9mvpdchtgsgecu22yycumagdx3uukqqqqqqqqqqqqyqqqqqqqqqqqqqqrc6fx2xy4ala6u0kxrj5fsx6vpmq0kd5l2usej6ywdh52jax2jjlms6x5zjf748dkcgggq4gymz288ngdd2ufshnafqza96wa8rcm8cscq0um0mx and I have 2.118 sats on my wallet, so I should be able to pay it right?
This is the log file  mutiny-logs.txt

Insufficient balance: requested 2139170 msat but only 2119000 msat available

Insufficient balance: requested 2139170 msat but only 2119000 msat available

I see while looking at the log but there is anyway from the wallet point of view to show this error? or just to alert the user in some way before making the payment?


Update Go version and golangci-lint to the latest release

Chore: Bumping up the versions of Go and golangci-lint

/approve
/lgtm


Keptn Bridge doesnt show "all root" events

Right now the Keptns bridge only shows "Root Events" which are Configuration Change Events that have no stage field specified. This are the events sent through a keptn send event new-artifact.
As it is possible to send a Configuration Change Event through the API that contains a stage, e.g: direct deployment into a specific stage which kicks of a new pipeline run -> the user never gets to see these events in the keptns bridge. Not even when searching for that specific keptnContext.
Proposal: Whether there is a root event or not - if we search for a keptnContext we should always be able to list all events that belong to that keptn context.

This has been fixed in #1234 and will also be recognized by the updated bridge (in #1276).


Generate a minimalistic "linearized" version of a CMT master repo

Sometimes, the only use of a linearized master repository is to inspect diffs between subsequent exercises. In that case, the build definition should be the absolute bare minimum as not to be more distractive than necessary.
To accomplish this, an option should be added to the linearize command (this could also be a CMT setting) that reduces the build def to the minimum.

Implemented by #117


Popup refactor

Closes #1350
As well as:
Fixes #1338
Fixes #1336
Fixes #1345
Fixes #1282
Fixes #1337
Fixes #1379

I've done one more pass through the documentation to improve the instruction. I'm going to go ahead and merge this, but welcome continued testing through the remainder of this week.


Add check-text flag to return whether file is text or binary format

Use flag --check-text to return if file is Text format.

Closing for now, let's discuss in #303.


Typo in bdc_tutorial_05.ipynb

In first para, wants to use "battery" but presented as "batter".

Good catch. Thank you!


Non-wrapping text

Currently there is support for wrapping text but not for non-wrapping text.

Fixed in v2.1.3


chore(deps): update common-dev-assets digest to 1017193

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
668972c -> 1017193

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.13.1 :tada:
The release is available on:

GitHub release
v1.13.1

Your semantic-release bot :package::rocket:


ajax suggestion not working

I have followed your documentation properly and returning json properly, but suggestion is not appearing

To know the issue and its solution, you should put your code in your comment.

Also the same issue for me!
I put this response in my php code:
return new JsonResponse(['India', 'Pakistan', 'Nepal', 'UAE', 'Iran', 'Bangladesh']
On JS I use:
suggestionsAction: {
        url: //my url,
        success: function(data) {
            console.info(data);
        }

On my page, I get the correct result on console, but nothing is shown in the input!

I checked on my local pc, its working fine. Make sure when you are sending a json response through any server side script, you are also sending proper header of json.
Example for PHP, we send this json header.
header('Content-Type: application/json');

I'm having this same issue. Headers are set to application/json as well. My output is "["tires","quote"]". When I hardcode that into the suggestions it works perfect. when I use Ajax it doesn't work.


Upgrade to Rust 1.57

The clippy version included with 1.57 flagged several problems:

Multiple fields were never read, removed those.
The Default impl on Tasks could be derived.
A redundant closure
A large enum variant

cool! nice to know that we can derive Default in such cases now!

We could do that before already! Vec implements Default :)

bors r+

bors r+