Add manual commit in polling loop

See issue #134

It's hard to tell from the diff what was an intentional change. Please
remove the whitespace-only changes.
On Monday, October 10, 2016, Gerald Quintana<EMAIL_ADDRESS>wrote:

See issue #134
https://github.com/logstash-plugins/logstash-input-kafka/issues/134
You can view, comment on, or merge this pull request online at:
https://github.com/logstash-plugins/logstash-input-kafka/pull/135
Commit Summary

Add manual commit in polling loop

File Changes

M lib/logstash/inputs/kafka.rb
https://github.com/logstash-plugins/logstash-input-kafka/pull/135/files#diff-0
(24)
M spec/integration/inputs/kafka_spec.rb
https://github.com/logstash-plugins/logstash-input-kafka/pull/135/files#diff-1
(33)

Patch Links:

https://github.com/logstash-plugins/logstash-input-kafka/
pull/135.patch
https://github.com/logstash-plugins/logstash-input-kafka/
pull/135.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/logstash-plugins/logstash-input-kafka/pull/135, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIC6tWw5mQgPT-b2srbaXQqRa6BoZOuks5qyka2gaJpZM4KSmpE
.

@jordansissel https://github.com/logstash-plugins/logstash-input-kafka/pull/135/files?w=1

@jordansissel I removed the whitespaces changes
The test case should be improved by restarting the input thread and checking it doesn't read the same messages again in order to check that offset have been commited. Sadly I don't know how to do that.

Trigger Travis CI

@gquintana I will test out the behavior (performance / ergonomics) of this to see how we can best handle this commit strategy.

@gquintana sorry for the delays, I would be more than happy to enable the ability to synchronously commit after ever event. I think it would be more appropriate to have a separate config option to be explicit about this commit_after_each_event or something. Since one would maybe want to use this plugin without committing at all, so having this behavior when auto_commit is false is inhibiting in that respect.
let me know what you think!

@talevy I can add a separate argument commit_after_each_event if you wish.
But it doesn't make sense to me. Try the following simple scenario:

Send data to a Kafka topic, for instance with a simple Logstash config like:

input {
  file {
    path => "C:/Java/logstash-2.4.1/test.log"
    start_position => "beginning"
  }
}
output {
  stdout {
    codec => json_lines {}
  }
  kafka {
    topic_id => "test_number"
    bootstrap_servers => "localhost:9092"
    codec => json
  }
}

Stop the log sender
Start a log consumer with auto commit disabled. Here is a simple config:

input {
  kafka {
    topics => ["test_number"]
    bootstrap_servers => "localhost:9092"
    group_id => "test_group"
    codec => json
    enable_auto_commit => false
  }
}
output {
  stdout {
    codec => json_lines {}
  }
}

The consumer gets the logs in the Kafka topic:

{"message":"One\r","@version":"1","@timestamp":"2017-02-02T14:56:41.580Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Two\r","@version":"1","@timestamp":"2017-02-02T14:56:41.584Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Five\r","@version":"1","@timestamp":"2017-02-02T14:56:41.587Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Eight\r","@version":"1","@timestamp":"2017-02-02T14:56:41.589Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Four\r","@version":"1","@timestamp":"2017-02-02T14:56:41.585Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Seven\r","@version":"1","@timestamp":"2017-02-02T14:56:41.588Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Ten\r","@version":"1","@timestamp":"2017-02-02T14:56:41.593Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Three\r","@version":"1","@timestamp":"2017-02-02T14:56:41.585Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Six\r","@version":"1","@timestamp":"2017-02-02T14:56:41.587Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Nine\r","@version":"1","@timestamp":"2017-02-02T14:56:41.592Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}

Stop and restart the Start a log consumer, still with auto commit disabled
The consumer get the same logs again (order is a bit different):

{"message":"Two\r","@version":"1","@timestamp":"2017-02-02T14:56:41.584Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Five\r","@version":"1","@timestamp":"2017-02-02T14:56:41.587Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Eight\r","@version":"1","@timestamp":"2017-02-02T14:56:41.589Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"One\r","@version":"1","@timestamp":"2017-02-02T14:56:41.580Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Four\r","@version":"1","@timestamp":"2017-02-02T14:56:41.585Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Seven\r","@version":"1","@timestamp":"2017-02-02T14:56:41.588Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Ten\r","@version":"1","@timestamp":"2017-02-02T14:56:41.593Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Three\r","@version":"1","@timestamp":"2017-02-02T14:56:41.585Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Six\r","@version":"1","@timestamp":"2017-02-02T14:56:41.587Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}
{"message":"Nine\r","@version":"1","@timestamp":"2017-02-02T14:56:41.592Z","path":"C:/Java/logstash-2.4.1/test.log","host":"ZE0PW1GU"}

Here I only have 10 records in the topic, imagine with more data...
Does it convince you that disabling auto commit and not manually committing in the code is a bad thing, at least by default?

@gquintana
Sorry for the delay. I would like to help improve the test case to verify that the messages are not repeated.
How do you want to do this? We can merge this and start on a new PR to improve the test - or work on this PR. My preference is for the merge and new PR (this one is long overdue)

@guyboertje As you like...
Writing an integration test shouldn't be that hard:

Start kafka input with auto_commit disabled and topic logstash_topic_plain for instance
Wait for messages to be consumed
Stop kafka input and restart it
Check that messages are consumed again

1 and 2 are already done in https://github.com/logstash-plugins/logstash-input-kafka/blob/master/spec/integration/inputs/kafka_spec.rb#L32 I don't know how to do 3

I was thinking along similar lines.

Send 5 strings "one", "two", etc. to a new topic like kafka_test_setup.sh does. (note the cwd will not be the gem root, probably lib/)
Start an input as you said consuming from the new topic in thread 1
Stop the input using input.stop in thread 2.
Wait for thread 1 to join
Expect that the first event in the queue is "one" and the last is "five"
Send another 5 strings "six", "seven" etc.
Do 2,3,4 again.
Expect that the sixth event in the queue is "six" and the last is "ten"


update the database ticket25

Hi @khmdagal
I don't think the header issue is with this change.
The problem with Header (and HeroBanner) is we need to have one hero banner in every page and that needs to be at the top of the page. Otherwise your page (header and the rest) doesn't look good.
I suggest to merge this PR and fix the header / heroBanner separately


Updated Icon

I'm loving Helium! It's awesome, so I wanted to make a new icon for it so it fit in the dock better with the mac icon style. I hope you like it :)

I appreciate the contribution, but I going to stick with the current icon for now. People already know the app by the current colorful icon, so I think such a drastic change would hurt recognition.

@JadenGeller You should consider option to move the app to the menubar. The current icon does just a little bit out of place in El Capitan.

That's definitely a reasonable thing to consider.

@net Thinking a bit about it, I'm hesitant to do that. The app does not always float on top—it can be temporarily disabled, or the app can be hidden—without a dock icon, it is difficult for users to find the window. I think that windowed apps really ought to show in the dock.
Is the motivation for menu bar support simply hiding the icon?

@JadenGeller Think of how much functionality could be moved to the menu bar. You could move all the menus there. You could have a hide/show toggle in the menu bar menu. Then you wouldn't have to select the helium window before accessing menu actions.

But all apps require you to select the window before accessing the menu. Why should Helium act differently in this regard?

I'm talking about this type of menu.

Transitioning to #107


Possible to add value_as_str?

If you have various primitive types in a string form from rustdocs (like 5_000i32 etc) and want to extract the 5000 without any _ (for this case a string output is fine), you can parse the strings with
pub fn value<N: FromIntegerLiteral>(&self) -> Option
But then this ignores the existing suffix

The optional type suffix of the literal is ignored by this method.

so it requires matching for all the valid suffixes to get the type N (and account for the weird fact that f32 isn't a float, but an integer, so you shouln't forget that suffix in the integers)
The alternative to get the string directly...
pub fn raw_main_part(&self) -> &str
...ignores the base

The main part containing the digits and potentially _. Do not try to parse this directly as that would ignore the base!

Would it be possible to add a function that would allow extracting the number accounting for the base and not requiring enumerating all the suffixes?

Instead of matching all different suffixes, you can just call lit.value::<u128>().map(|n| n.to_string()). I.e. you can just use the largest integer type to deal with all values. Also remember that there are no negative literals, so it actually can represent all possible integer literal values. (Well, the Rust grammar allows arbitrarily large integers in the lexicographical grammar, but it still disallows integers larger than u128 in a later stage.)
Is that what you are looking for? Would you still say that functionality should be added as function? I will probably add some docs about the "largest integer trick".

Also remember that there are no negative literals, so it actually can represent all possible integer literal values

Thanks for the reminder, I got hit by exactly this after opening the issue, and fixed it by going with the trick you later mentioned (weirdly, I already had u128 in the _ arm, but for some reason though it'd be better to stick to the "correct" types).

Would you still say that functionality should be added as function?

Yes, I think the user should not need to learn about these Rust grammar quirks, and also think number is an important part for it be easily extracted just like other chunks like base.
So hopefully with the added lenient parser mentioned https://github.com/LukasKalbertodt/litrs/issues/14 this would become a reality

Sure. I store the result in a key-value database so that I can retrieve it later in a script. The original strings are win32 API constant values that I get from parsing rustdocs for a Windows sys crate (which seems like the easiest way to get them). I use your crate to then convert those string constant values to a "clean" non-suffixed-non-_ number
So ideally I'd have a single and simple Literal::parse_lenient(const_str).value_str() call (and get the number part for numbers, and string for char/string etc) and call it a day :). Not having to handle minus signs and types gets very close to this

I've thought about this whole lenient idea again and I decided that litrs is not the right place for that. There are many different useful things one could offer (parsing integers as floats, accepting minus signs, and plus signs, ...). That easily could run into the feature creep problem. I prefer this crate to be very focused on just spec-compliant parsing of literals.
I also decided against value_as_str, since it would just be lit.value::<u128>().to_string() and seems a bit too specialized to me to provide a method for this pair of method calls. Instead, I added a hint to the docs, which helps hopefully.
I do agree though that these features are very useful to have generally. I just think they should live in a different crate. I might even build one as I have use for it as well (e.g. in confique). But no promises and don't hold your breath.
Sorry for the probably disappointing outcome!


The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

Description
When building a fresh macOS Firestore project using Cocoapods, after setting up the project and running it, multiple warnings are displayed across most of the Firestore pods.
The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.
Reproducing the issue

Create a fresh macOS project in XCode (This project was called FirestoreTest), set Minimum Deployments to 11.0, App Sandbox Network Incoming and Outgoing checked and remove the Hardened Runtime (not needed for this example)

Follow the installation guide here Install Firestore Apple ensuring that the XCode project is added to the Firestore project via the Firebase Console and the GoogleService-Info.plist downloaded and added to the XCode project

Create a podfile (see podfile info below)

Quit XCode

Command line, cd to the folder containing the project

pod install --repo-update

Open XCode using the FirestoreTest.xcworkspace file and build

Note warnings

Firebase SDK Version
10.11.0
Xcode Version
14.3.1
Installation Method
CocoaPods
Firebase Product(s)
Authentication, Firestore, Storage
Targeted Platforms
macOS
Relevant Log Output
BoringSSL-GRPC
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase.

FirebaseAppCheckInterop
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

FirebaseAuth
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

.../FirestoreTest/Pods/FirebaseAuth/FirebaseAuth/Sources/Auth/FIRAuthGlobalWorkQueue.m
.../FirestoreTest/Pods/FirebaseAuth/FirebaseAuth/Sources/Auth/FIRAuthGlobalWorkQueue.m:21:40 A function declaration without a prototype is deprecated in all versions of C

FirebaseAuthInterop
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

FirebaseCore
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

FirebaseCoreDiagnostics
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

FirebaseCoreExtension
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

FirebaseCoreInternal
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

FirebaseFirestore
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

.../FirestoreTest/Pods/FirebaseFirestore/Firestore/core/src/util/set_util.h
.../FirestoreTest/Pods/FirebaseFirestore/Firestore/core/src/util/set_util.h:39:11 Parameter 'comparator' not found in the function declaration

.../FirestoreTest/Pods/FirebaseFirestore/Firestore/core/include/firebase/firestore/timestamp.h
.../FirestoreTest/Pods/FirebaseFirestore/Firestore/core/include/firebase/firestore/timestamp.h:106:36 Empty paragraph passed to '@param' command

.../FirestoreTest/Pods/FirebaseFirestore/Firestore/core/include/firebase/firestore/timestamp.h:127:22 Empty paragraph passed to '@param' command

FirebaseFirestoreSwift
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

FirebaseStorage
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

FirebaseStorageInternal
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

GTMSessionFetcher
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

GoogleDataTransport
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

GoogleUtilities
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 13.3.99.

Libuv-gRPC
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase.

PromisesObjC
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

abseil
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase.

gRPC-C++
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase.

gRPC-C++-gRPCCertificates-Cpp
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

gRPC-Core
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase.

nanopb
.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.9, but the range of supported deployment target versions is 10.13 to 13.3.99.

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

project 'FirestoreTest.xcodeproj'
platform :osx, '11.0'
target 'FirestoreTest' do
  use_frameworks! :linkage => :static   #required for successful install. Can also `use_modular_headers!`?
  pod 'FirebaseAuth'
  pod 'FirebaseFirestore'
  pod 'FirebaseStorage'
  pod 'FirebaseFirestoreSwift', '~> 9.0.0'
end

Hi @Jaycyn, would you mind double checking that you are installing Firebase 10.11.0? You can check the console output during pod install or inspect the Podfile.lock (rather than Podfile) file.
My suspicion is that the line pod 'FirebaseFirestoreSwift', '~> 9.0.0' in your Podfile is resulting in you getting Firebase 9.6.0, the latest 9.x release, rather than 10.11.0. I changed this line to just pod 'FirebaseFirestoreSwift', ran pod update, and saw the following:
Installing FirebaseAppCheckInterop 10.11.0 (was 9.6.0)
Installing FirebaseAuth 10.11.0 (was 9.6.0)
Installing FirebaseAuthInterop 10.11.0 (was 9.6.0)
Installing FirebaseCore 10.11.0 (was 9.6.0)
Installing FirebaseCoreExtension 10.11.0 (was 9.6.0)
Installing FirebaseCoreInternal 10.11.0 (was 9.6.0)
Installing FirebaseFirestore 10.11.0 (was 9.6.0)
Installing FirebaseFirestoreSwift 10.11.0 (was 9.0.0)
Installing FirebaseSharedSwift (10.11.0)
Installing FirebaseStorage 10.11.0 (was 9.6.0)
Installing GTMSessionFetcher 3.1.1 (was 2.3.0)
Installing abseil 1.20220623.0 (was 1.20211102.0)
Installing gRPC-C++ 1.50.1 (was 1.44.0)
Installing gRPC-Core 1.50.1 (was 1.44.0)
Removing FirebaseCoreDiagnostics
Removing FirebaseStorageInternal
Removing GoogleDataTransport
Removing Libuv-gRPC

Context: macOS 10.12 was the deployment target in 9.6.0 but we increased it to macOS 10.13 in Firebase 10.0.0 to match the minimum supported by Xcode 14.
If this doesn't resolve the issue, please share your Podfile.lock as well. Hope this helps!

@andrewheard
Thanks for the quick response and the info - your guess was correct. The original intention was to stay at 9.6 for this test project but it appears that is not feasible. It is correct that the pods were 'out of sync' as some updated beyond what was compatible with 9.6?
I made your suggested change; then deintegrated cocoapods, deleted the podfile.lock opened the project and cleaned, ran it to ensure it was stable, quit and did a pod install. Note there is no other code in the project, just a default.
That resulted in a number of similar warnings being displayed like this (about 15 total);

.../FirestoreTest/Pods/Pods.xcodeproj The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99.

but there's also a hard error now

xray.upbdefs.c
'.../FirestoreTest/Pods/gRPC-Core/src/core/ext/upbdefs-generated/envoy/config/trace/v3/xray.upbdefs.c module map file '.../FirestoreTest/Pods/Headers/Private/openssl_grpc/BoringSSL-GRPC.modulemap' not found

The Podfile.lock is quite long but here are a few that were flagged with warnings (if you need the whole thing, I will edit)

BoringSSL-GRPC (0.0.24):

BoringSSL-GRPC/Implementation (= 0.0.24)
BoringSSL-GRPC/Interface (= 0.0.24)

GTMSessionFetcher/Core (3.1.1)

GoogleUtilities/AppDelegateSwizzler (7.11.1):

GoogleUtilities/Environment
GoogleUtilities/Logger
GoogleUtilities/Network
GoogleUtilities/Environment (7.11.1):

PromisesObjC (< 3.0, >= 1.2)

GoogleUtilities/Logger (7.11.1):

GoogleUtilities/Environment

PromisesObjC (2.2.0)

here's the Firebase Section

FirebaseAppCheckInterop (10.11.0)

FirebaseAuth (10.11.0):

FirebaseAppCheckInterop (~> 10.0)
FirebaseCore (~> 10.0)
GoogleUtilities/AppDelegateSwizzler (~> 7.8)
GoogleUtilities/Environment (~> 7.8)
GTMSessionFetcher/Core (< 4.0, >= 2.1)

FirebaseAuthInterop (10.11.0)
FirebaseCore (10.11.0):

FirebaseCoreInternal (~> 10.0)
GoogleUtilities/Environment (~> 7.8)
GoogleUtilities/Logger (~> 7.8)

FirebaseCoreExtension (10.11.0):

FirebaseCore (~> 10.0)

FirebaseCoreInternal (10.11.0):

"GoogleUtilities/NSData+zlib (~> 7.8)"

FirebaseFirestore (10.11.0):

abseil/algorithm (~> 1.20220623.0)
abseil/base (~> 1.20220623.0)
abseil/container/flat_hash_map (~> 1.20220623.0)
abseil/memory (~> 1.20220623.0)
abseil/meta (~> 1.20220623.0)
abseil/strings/strings (~> 1.20220623.0)
abseil/time (~> 1.20220623.0)
abseil/types (~> 1.20220623.0)
FirebaseCore (~> 10.0)
"gRPC-C++ (~> 1.50.1)"
leveldb-library (~> 1.22)
nanopb (< 2.30910.0, >= 2.30908.0)

FirebaseFirestoreSwift (10.11.0):

FirebaseCore (~> 10.0)
FirebaseCoreExtension (~> 10.0)
FirebaseFirestore (~> 10.0)
FirebaseSharedSwift (~> 10.0)

FirebaseSharedSwift (10.11.0)
FirebaseStorage (10.11.0):

FirebaseAppCheckInterop (~> 10.0)
FirebaseAuthInterop (~> 10.0)
FirebaseCore (~> 10.0)
FirebaseCoreExtension (~> 10.0)
GTMSessionFetcher/Core (< 4.0, >= 2.1)

@Jaycyn Unfortunately some of those The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.10, but the range of supported deployment target versions is 10.13 to 13.3.99. warnings in transitive dependencies are expected (e.g., GTMSessionFetcher, PromisesObjC, nanopb, etc.) since those projects haven't increased their minimum deployment targets to 10.13. Generally we'd recommend ignoring those warnings but a possible workaround would be to use an approach similar to that described in this Stack Overflow answer.

Example Post-Install Snippet
post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      if config.build_settings['MACOSX_DEPLOYMENT_TARGET'].to_f < 10.13
        config.build_settings['MACOSX_DEPLOYMENT_TARGET'] = '10.13'
      end
    end
  end
end

Note: the above snippet doesn't consider semantic versioning (just converts to floats) so 10.9 > 10.13 -- it works better for macOS 11+.

For the hard error,

xray.upbdefs.c
'.../FirestoreTest/Pods/gRPC-Core/src/core/ext/upbdefs-generated/envoy/config/trace/v3/xray.upbdefs.c module map file '.../FirestoreTest/Pods/Headers/Private/openssl_grpc/BoringSSL-GRPC.modulemap' not found

does this go away if you "Clean Build Folder..." after re-opening the xcworkspace? I think the build folder is different between the xcodeproj and xcworkspace so it may not actually be a clean state if you didn't clean again after pod installing and opening the workspace (Unfortunately I'm just guessing on this since I wasn't able to reproduce the modulemap error myself.)

@andrewheard
I cleaned build before and after which had no effect.
As a further test, I am at my office and factory reset an iMac (Retina 5K, 27-inch, 2019) upgraded to Monterey 12.6.5, installed XCode and Command line tools, ensured Cocoapods and repo were all up to date.
I followed the exact process I outlined above and am receiving similar results - with a number of libraries throwing a warning but then a hard error and Build Failed

.../FirestoreTest/Pods/gRPC-Core/src/core/ext/upbdefs-generated/envoy/config/trace/v3/zipkin.upbdefs.c
.../FirestoreTest/Pods/gRPC-C++/src/cpp/util/time_cc.cc module map file .../FirestoreTest/Pods/Headers/Private/grpc/gRPC-Core.modulemap' not found

Sorry about the trouble @Jaycyn.  We're not likely to ever be able to completely eliminate the version warnings from Firebase dependencies since some of them want to continue to support Xcode 13 and earlier versions.
Regarding the hard failure, we'll likely need a reproducible use case to help since we haven't seen the issue in our testing.

Hi @Jaycyn, just trying to narrow down any other possible differences between our project setups. Is the new project you created in Objective-C or Swift?
It is also seems like you've been able to reproduce the issue on Ventura (since Xcode 14.3.1 requires it) and Monterey (the fresh iMac). Is that accurate?
Sorry for all the back and forth!

A bit more info. Seems the issue can be narrowed to Ventura.
Starting yesterday morning, I could not build/run the project on anything.
After deintegrating, removing podfile.lock and rebuilding, the projects now build on the Monterey Macs with only a warning. It's possible something in the libraries changed yesterday, allowing the build.
I crafted a fresh project (called afirestore) following the above steps as well and it also builds on Monterey
I copied the project to the Ventura Mac and when building throws a hard error
.../afirestore/Pods/gRPC-Core/src/core/ext/upbdefs-generated/envoy/config/trace/v3/zipkin.upbdefs.c
.../afirestore/Pods/gRPC-Core/src/core/ext/upbdefs-generated/envoy/config/trace/v3/zipkin.upbdefs.c module map file '.../afirestore/Pods/Headers/Private/openssl_grpc/BoringSSL-GRPC.modulemap' not found
I then deintegrated, removed podfile.lock etc and then pod installed
That project throws the above error
Lastly, I created the project on the Ventura Mac, following the above steps and it will not build without the hard error.
On the Monterey Macs, removing cocoapods from the project and pod installing allows it to then build
So bottom line is Monterey Builds are ok (with warnings) but Ventura builds throw hard error.

Will you share the project via zip or GitHub?

@paulb777
Certainly. The attached zip file was built on Ventura and the podfile includes this line
use_frameworks! :linkage => :static
I believe the project builds and runs on Ventura as well as Monterey.
If pod deintegrate is performed (then removing podfile.lock, the xcworkspacefile etc) and that line is commented out and replaced with
use_modular_headers!
And pod install is run, the project will no longer build on Monterey and XCode generates an error regarding zipkin.upbdefs.c
As noted from CocoaPods if neither is included (which is why some clarity may be needed in the docs)
[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod FirebaseCoreInternal depends upon GoogleUtilities, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies.

So I seem to be getting really intermittent results trying to duplicate the issue - these are all being tested on 100% clean Macs, factory fresh status using Monterey on one Ventura on the other.
afirestore.zip

Hi @Jaycyn, sorry I missed the "Can also use_modular_headers!?" question in your Podfile comment. Firebase requires the use of frameworks as of version 9.0 when we introduced some Swift pods (Release Note) so use_modular_headers! won't work:

Breaking change: Podfiles must include use_frameworks! or use_frameworks! :linkage => :static.

I'll add a note to our installation docs since it isn't mentioned there.

@Jaycyn Thanks for your patience in helping us track down the documentation issue! I'll close but feel free to continue the discussion.


Unable to run the project.

Trying to run the application in VS Code using ng serve but I am unable to do so. How can i proceed? I am new to UI designing and need to create a step progress bar in HTML/CSS/Angular.

Can you tell me the steps you did?
did you follow the instructions in the readme document?

I created a new Angular project.
Ran npm install stepper-progress-bar in the terminal.
Added the changes in app.module.ts and html file.
After adding the app.component.ts changes , I get an error under this keyword. Unexpected token. A constructor,method, accessor or property was expected.
Getting this issue when i try to use the step progress bar as a component.
When i try to run the code from the downloaded zip using ng build , I get the error The build command requires to be run in Angular project, but a project defination could not be found.
Kindly excuse me if the mistakes sound rudimentary, I am new to UI app , and i need to create a step progress bar in the same way mentioned in the medium article by Michael X(https://medium.com/@beyondborders/building-a-responsive-progress-bar-ea5a0ecabe91) using HTML/CSS/TS and Angular.


debugging and cleaning

still not working - but progress

yeah, but really nice.
On Tue, Nov 26, 2024 at 11:20 AM oliviamiller @.***>
wrote:

@.**** commented on this pull request.
In cmd/cli/cmd.go
https://github.com/oliviamiller/lorawan/pull/8#discussion_r1858849054:

if err != nil {

return err

}
defer g.Close(ctx)

for i := 0; i < 10; i++ {

time.Sleep(time.Second)

r, err := g.Readings(ctx, nil)

if err != nil {

	return err

}

logger.Info(r)

}

return nil
+}

was this just for testing?
—
Reply to this email directly, view it on GitHub
https://github.com/oliviamiller/lorawan/pull/8#pullrequestreview-2462051188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAC6TOH2C2R6HH7K5UOPZ32CSNWPAVCNFSM6AAAAABSLKUHLSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINRSGA2TCMJYHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

yeah, but really nice.

We will make sure your nice test script gets in 😄 , want us to take over the pr now that there are merge conflicts? The gateway on your machine builds btw.

Yeah, you can just take it over.
On Tue, Nov 26, 2024 at 11:46 AM randhid @.***> wrote:

yeah, but really nice.
We will make sure your nice test script gets in 😄 , want us to take over
the pr now that there are merge conflicts? The gateway on your machine
builds btw.
—
Reply to this email directly, view it on GitHub
https://github.com/oliviamiller/lorawan/pull/8#issuecomment-2501380684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAC6TOCBTEKHAGKILT6EF32CSQXXAVCNFSM6AAAAABSLKUHLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGM4DANRYGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix compatibility with Python 3.8

The deprecated platform.linux_distribution function was removed
in Python 3.8 - fallback to using parse_os_release if the function
is not found.
Signed-off-by: James Page<EMAIL_ADDRESS>

+1

https://pypi.org/project/distro/ may help solve the problem.
I'm not sure whether it's also supported in python2.

jenkins, retest this please

jenkins, retest this please

jenkins, retest this please

the test failure should be addressed by #498.

https://pypi.org/project/distro/ may help solve the problem.
I'm not sure whether it's also supported in python2.

I looked at it before and seems OK, but I wouldn't add a whole dependency to replace just 4 LoC. I don't know if that package could be useful for other parts of the app that would make it valuable to require it.

jenkins, retest this please

Looks like the release 2.0.1 doesn't include the fix? When do we expect have it in the new release ?

Looks like the release 2.0.1 doesn't include the fix? When do we expect have it in the new release ? As I still hit the issue:

@Kaizhe v2.0.1 was cut 2 years ago, and it didn't include this change. see https://github.com/ceph/ceph-deploy/releases/tag/v2.0.1

Is there a plan to cut a new release?

Is there a plan to cut a new release?

i sent a mail to ceph-maintainers two months ago for inputs regarding to the interests in using ceph-deploy. no replies. so my understanding is that the community has no more interests in using it.

Is there a plan to cut a new release?

i sent a mail to ceph-maintainers two months ago for inputs regarding to the interests in using ceph-deploy. no replies. so my understanding is that the community has no more interests in using it.

Holly cr*p, this can't happen! I mean, besides using k8s, ceph-deploy is the easiest way to deploy ceph which otherwise is very complicated.
Which maintainers are you reaching? Debian, Fedora?

it's a mailing list. please search for "ceph-maintainers" https://ceph.io/irc/. you might want to subscribe it for reading its archive.

I'm commenting here as a note to myself, because the potential removal of
ceph-deploy has significant documentation impact. (I'm the upstream Ceph
docs guy.) You don't need to read this email unless you have strong
opinions about the nature of the upstream Ceph documentation.
Currently, as of August 2020, the upstream ceph documentation contains
numerous references to ceph-deploy, even though as of the release of
Octopus (March-ish 2020) ceph-deploy is not the preferred method of
installing a Ceph cluster. The preferred method of installing Ceph is now
by using the cephadm tool.
I have begun to think that the best way to document the Ceph project is to

do our best to organize the grandma's attic of docs.ceph.com so that the
tree pane is more meaningful, and 2) create a new version of the docs each
time there is a release, and incrementally update that version only to
correct errors that were made when the document was originally composed.
Doing otherwise now would require the documentation to be changed
everywhere that ceph-deploy is mentioned, and those mentions would have to
be replaced with mentions of cephadm. If HacKan is correct and many people
still use ceph-deploy, then clearly it would be irresponsible and
destructive to remove the documentation that explains how to use
ceph-deploy.

Again, this has been mostly a note to self, but it's a topic that I have
been much aware of over the past month, and it's a thorny problem if we
don't make sure to archive old docs and create new docs for each release.
On Thu, Aug 27, 2020 at 2:16 AM Kefu Chai<EMAIL_ADDRESS>wrote:

it's a mailing list. please search for "ceph-maintainers"
https://ceph.io/irc/. you might want to subscribe it for reading its
archive.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ceph/ceph-deploy/pull/496#issuecomment-680979944, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AALAZ4YBO27Q4G2EWA3YYETSCUYONANCNFSM4NHRBZOA
.

Same, from pip index versions ceph-deploy I show than version 2.1.0 is not present in pip repo ... Can you push it ?

Just wanted to reiterate that it would be immensely helpful if (the final?) release of 2.1.0 was pushed to PyPi.


Python3.9: AttributeError: 'Thread' object has no attribute 'isAlive'

threading.Thread.is_alive() should be used instead. Thanks :)
Python Version: 3.9
The traceback I'm getting (several times):
Process http://localhost:8080->ftp_brute:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/usr/local/lib/python3.9/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/home/runner/Nettacker/core/attack.py", line 136, in start_attack
    start(
  File "/home/runner/Nettacker/lib/brute/ftp/engine.py", line 213, in start
    ports = test_ports(ports, timeout_sec, target, retries, language, num, total, time_sleep, ports_tmp_filename,
  File "/home/runner/Nettacker/lib/brute/ftp/engine.py", line 156, in test_ports
    if thread.isAlive():
AttributeError: 'Thread' object has no attribute 'isAlive'

I would like to take up this issue

thanks @itsdivyanshjain - I will review this weekend. I am just just adding Python bug reference in this comment  for a background of why isAlive was deprecated in Python 3.9 https://bugs.python.org/issue37804

@securestep9 any update?

is still have a problem in my script if there is another function if deprecated please tell us


Traversal fixes

This is a PR to fix #87.
Nesting will now be set during Hostgroup initialization, preventing the need to perform _set_format_options() twice.

Looks good to me.

🫶


Ransomware Error

when someone runs everything works and sends normally expect the ransomware, it gives me this error.
Rose Report
Rose Instance - Error
Error in Doggo Ransomware occured | Help us by reporting this bug
"cannot access local variable 'key' where it is not associated with a value"

Ransomware is bugged. This will be fixed later.

fixed @githubianuser


在终端中运行，客户端可连接上，如果做为服务启动，则无法启动.

[root@host xxxx]# ss-server -v -c /etc/shadowsocks-libev/config.json
2019-01-22 17:58:35 INFO: using tcp fast open
2019-01-22 17:58:35 INFO: plugin "v2ray-plugin" enabled
2019-01-22 17:58:35 INFO: UDP relay enabled
2019-01-22 17:58:35 INFO: initializing ciphers... aes-256-gcm
2019-01-22 17:58:35 INFO: using nameserver: <IP_ADDRESS>
2019-01-22 17:58:35 INFO: tcp server listening at <IP_ADDRESS>:34797
2019-01-22 17:58:35 INFO: udp server listening at <IP_ADDRESS>:443
2019/01/22 17:58:35 V2Ray 4.13 (Po) Custom
2019/01/22 17:58:35 A unified platform for anti-censorship.
2019/01/22 17:58:35 [Warning] v2ray.com/core: V2Ray 4.13 started
2019/01/22 17:58:43 tcp:<IP_ADDRESS>:31538 accepted tcp:<IP_ADDRESS>:0
2019-01-22 17:58:43 INFO: accept a connection
2019-01-22 17:58:43 INFO: [443] connect to www.google.com:443
2019-01-22 17:58:43 INFO: found address name v6 address www.google.com
2019-01-22 17:58:43 INFO: found address name v4 address www.google.com
2019-01-22 17:58:43 INFO: successfully resolved www.google.com
2019-01-22 17:58:43 INFO: remote connected
2019-01-22 17:58:43 INFO: remote_recv close the connection
2019-01-22 17:58:43 INFO: current remote connection: 0
2019-01-22 17:58:43 INFO: current server connection: 0
config.json
{   "server":"<IP_ADDRESS>",
"server_port":443,
"password":"1234",
"timeout":300,
"method":"aes-256-gcm",
"fast_open":true,
"user":"nobody",
"nameserver":"<IP_ADDRESS>",
"mode":"tcp_and_udp",
"plugin":"v2ray-plugin",
"plugin_opts":"server;tls;host=xxxx.com;cert=/root/.acme.sh/xxxx.com/fullchain.cer;key=/root/.acme.sh/xxxx.com/xxxx.com.key"
}
在终端中运行，客户端可连接上，如果做为服务启动，则无法启动
Jan 22 17:39:43 host shadowsocks-libev: Starting Shadowsocks-libev success
Jan 22 17:39:43 host systemd: Started LSB: Fast tunnel proxy that helps you bypass firewalls.
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: using tcp fast open
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: plugin "v2ray-plugin" enabled
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: UDP relay enabled
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: initializing ciphers... aes-256-gcm
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: using nameserver: <IP_ADDRESS>
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: tcp server listening at <IP_ADDRESS>:58155
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: udp server listening at <IP_ADDRESS>:443
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: plugin service exit unexpectedly
Jan 22 17:39:43 host /usr/local/bin/ss-server[3928]: closed gracefully
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: using tcp fast open
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: plugin "v2ray-plugin" enabled
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: UDP relay enabled
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: initializing ciphers... aes-256-gcm
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: using nameserver: <IP_ADDRESS>
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: tcp server listening at <IP_ADDRESS>:47393
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: udp server listening at <IP_ADDRESS>:443
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: plugin service exit unexpectedly
Jan 22 17:52:52 host /usr/local/bin/ss-server[3945]: closed gracefully
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: using tcp fast open
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: plugin "v2ray-plugin" enabled
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: UDP relay enabled
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: initializing ciphers... aes-256-gcm
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: using nameserver: <IP_ADDRESS>
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: tcp server listening at <IP_ADDRESS>:49533
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: udp server listening at <IP_ADDRESS>:443
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: plugin service exit unexpectedly
Jan 22 17:55:24 host /usr/local/bin/ss-server[3962]: closed gracefully

想知道是如何解决的。。


Add to onboarding reproduction logs

Please continue along the onboarding path until you reach the end of the exercises, and then we'll take a look all at once.

Seeing no further progress, closing.


New hook developed to control audio

This pull request adds additional functionalities to the useAudio hook, allowing for better control over audio playback. The following functions have been added:

[x] increaseVolume: Allows to increase the volume of the audio. The increment can be specified as a parameter, otherwise it will be increased by 5% each time.

[x] decreaseVolume: Allows to decrease the volume of the audio. The decrement can be specified as a parameter, otherwise it will be decreased by 5% each time.

[x] unmute: Allows to unmute the audio.

[x] toggleMute: Toggles between muting and unmuting the audio.

[x] forward: Advances in the audio playback. The amount of seconds to advance can be specified as a parameter, otherwise it will advance by 5 seconds each time.

[x] back: Moves back in the audio playback. The amount of seconds to move back can be specified as a parameter, otherwise it will move back by 5 seconds each time.

These additions provide more flexibility and control over audio playback, thereby enhancing the user experience.
#41

Hi @uvee-dev. I'm sorry I didn't review this pr before, I was developing the useVideo hook so you can use it as a reference.
As I told you before, I want useVideo and useAudio to have approximately the same API. Obviously they can't have exactly the same one because, for example, useVideo has a function to make it full screen and it would be illogical for useAudio to have something like that.
Please see my implementation of useVideo and use the same api for useAudio.
When I mention api I mean the parameters and return values.
If you have any questions, feel free to tell me. Thank you very much in advance. 🙌


Resolve architect feedback on CLU

[ ] Make async endpoint AnalyzeConversation (LRO) plural i.e., AnalyzeConversations.
[ ] Hide (make internal) ConversationsAudience until architect re-review discussion has completed. We shouldn't need this for the 1.1.0 GA.
[ ] Remove the word "Job" from CancelAnalyzeConversationJob and friends.

@kristapratico @johanste would you want to make your analyze_conversation LRO plural (add an "s") as well for consistency?

We have a different method for the async endpoint (begin_conversation_analysis). I think it makes sense for Python to keep analzye_conversation singular since it's not overloaded and only targets the sync endpoint / one conversation.


How to dumps/loads cuckoofilter from file?

I have three question before import cuckoofilter into my project:

how to dumps and loads cuckoofilter from file in order to failover?
what's recommend ratio for data size/cuckoofilter size?
how to resize cuckoofilter for scale purpose？

@FelixSeptem  maybe we can fork this repo. change all field to start with capital . serialize to json to dump. load json to filter .

@FelixSeptem maybe we can fork this repo. change all field to start with capital . serialize to json to dump. load json to filter .

gob maybe a better choice in Golang to serialize and deserialize

@FelixSeptem  we don't need do it self .the api has Encode Decode method.
func (cf *Filter) Encode() []byte

func Decode(bytes []byte) (*Filter, error)

complete code
var (
	//todo autoresize
	filter = cuckoo.NewFilter(1000)
)

const (
	fileName = "cuckoo-filter.data"
)

func GetFilter() *cuckoo.Filter {

	bytes, err := ioutil.ReadFile(fileName)

	if err == nil {
		decodeFilter, decodeError := cuckoo.Decode(bytes)
		if decodeError == nil {
			filter = decodeFilter
		}
	}

	return filter
}

func DumpFilter() {

	bytes := filter.Encode()
	err := ioutil.WriteFile(fileName, bytes, 0755)
	if err != nil {
		log.Error(err.Error())
	}

}


3.1.1: update from main

This merges current main into v3.1.1-dev, resolving the three merge conflicts in

.gitignore: taken from main
validate-markdown.yaml: taken from v3.1.1-dev
3.1.0.md: taken from main

Why are we merging main into 3.1.1 when we're just about to merge 3.1.1 into main?  Apologies if I missed somewhere that documents this.

Same as 3.0.4: From a DM conversation, apparently this is how it's preferred to resolve conflicts, which seems messy to me but I won't object to it.


Feature/GBI-1201 - Collateral Changes and remove lbc transfers for pegout

https://rsklabs.atlassian.net/jira/software/projects/GBI/boards/42?assignee=63e26a838978d7a4353cae16&selectedIssue=GBI-1201


Check and set rebuild

This PR implements the changes for #249. Note that it depends on API in OSBS which does not exist yet: set_labels_on_build_config(). See https://github.com/projectatomic/osbs-client/pull/189 for that.

Not sure if I understand this correctly, but can't you use http://has207.github.io/flexmock/user-guide.html#automatically-checked-expectations instead of the Collect class? Flexmock will check if the method has been called with proper arguments for you.

I couldn't get that to work to start with. I see now that it was because I was calling flexmock twice for the same method, once in the (..., function=....) style.

LGTM now. Let's merge this after projectatomic/osbs-client#189 is merged.


Avoid possible loss of resolution when switching leaders

The current leader-election for HA configuration is such that once the leader stops receiving the samples from prometheus instance for a period of the timeout, it gives up the advisory-lock and the non-leader then after receiving its samples from its corresponding Prometheus attempts and takes the lock. This means the samples between the fall of leader to the rise of the non-leader are dropped.
We should prevent this by buffering possibly the samples in the non-leader instance for the time that is (timeout + prometheus scrape interval (assuming 30 seconds as ideal in clusters)) the timeout given for a shift of leader. This will assure that no samples are dropped.

Needs planning as depends on other HA features/considerations, like whether we will support label-based HA switchover like cortex

As this advisory lock-based HA approach is deprecated. closing this issue. @Harkishen-Singh feel free to re-open the issue. If you think this needs to be addressed.


XAPIC support

This PR adds support for XAPIC mode when X2APIC is not supported.
From what I understand, QEMU only supports X2APIC when running in KVM (i.e, Linux). Since I'm using OS X as a development environment it's not available for me.

Closing in favour of #2.

Closing in favour of #2.


[Roadmap] Improve Evaluation Workflow and Add new Evaluators

[x]  #1392
[x] #1394

[x] Add strings matching evaluators
[x] Add Levenstein Distance evaluator

[x] #1395
[x] #1396
[x] #1397
[x] #1398
[x] #1399

Done


Enhancement Outline filter locally defined

Our procedures contain a lot of functions and procedures that are defined in include files.
(adm includes, external function definitions for persistent procedure libaries, ...)
It would be very nice to be able to show only the locally declared function/procedures.
Currently the outline is not really useful for the adm based UI.
Of all entries in the screenshot only one is locally defined. .

Personally, I'm not interested in variable definitions in the outline.
A toggle to hide those would be helpful as well.

I agree that filtering would be useful. There are options for hiding variables in the outline: https://code.visualstudio.com/updates/v1_40#_type-filters-for-outline-and-breadcrumbs
Can you try that ?

Controlled by abl.outline.showIncludeFiles and abl.outline.showContentInIncludeFiles


Rust: Garry tweeted that EAC would be enabled "tomorrow" on the 28th. Rust Tweeted delay. See "tinkering steps."

Game Title
Rust
Status of the Anti-Cheat
🕧 Planned
Tinkering Steps
Tweet from Garry saying EAC update "tomorrow" on the 28th: https://twitter.com/garrynewman/status/1541773484015161347
Tweet from Rust saying that the update was to be delayed on the 29th: https://twitter.com/playrust/status/1542069218140721154
These two tweets lead me to believe that the EAC update MIGHT be on the 7th...
Proof of Mention
https://twitter.com/garrynewman/status/1541773484015161347 & https://twitter.com/playrust/status/1542069218140721154

Nice news!


updating title and favicon

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
thinalai, @alexfdz, @zs9024, @tatiesmars, @hsyndeniz, @0x31071, @juliavi, @eiupanther96, @Eudepistoic-D, @JJangJJoo, @fcscoin, @rohringrook, @RFG-G, @martincalveira, @Admin1993, @robgering, @ChuDiep93, @w950888, @alexanderisora, @mattgenious, @matinkaboli, @Loki-Tu, @liquizzz, @qiang, @Pepeye, @xesrevinu, @dec0dOS, @limyang51, @delta-wing, @Gitleyla, @itsstdev, @webdev-vignesh, @Ay-355, @amirrezaask, @bebetter2018, @tkersey, @tuanlongn, @DrDzy01, @juniuszhou, @allanberger, @alexhudici, @Ces-aq, @codedplanetuk, @halljson, @RubenOlt, @LeeDongHyeok, @luannguyenQV, @Evolgence, @Iza1977, @somaliz


middleware uses webob, which is not a declared dependency

$ ../venvs/virtualenv/bin/virtualenv routes
Using real prefix '/usr'
New python executable in routes/bin/python
Installing setuptools, pip...done.
$ routes/bin/pip install -U routes
Collecting routes
  Downloading Routes-2.1.tar.gz (179kB)
    100% |################################| 180kB 777kB/s
Collecting repoze.lru>=0.3 (from routes)
  Downloading repoze.lru-0.6.tar.gz
Installing collected packages: repoze.lru, routes
  Running setup.py install for repoze.lru
    Skipping installation of /scratch/routes/lib/python2.7/site-packages/repoze/__init__.py (namespace package)
    Installing /scratch/routes/lib/python2.7/site-packages/repoze.lru-0.6-py2.7-nspkg.pth
  Running setup.py install for routes
Successfully installed repoze.lru-0.6 routes-2.1
$ routes/bin/python
Python 2.7.6 (default, Mar 22 2014, 15:40:47)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import routes.middleware
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/scratch/routes/local/lib/python2.7/site-packages/routes/middleware.py", line 5, in <module>
    from webob import Request
ImportError: No module named webob

Since you've defined webob in your setup.py tests_require and also manually install it in your .travis.yml your testsuite doesn't notice this, but it definitely appears to me to be an actual requirement.

This isn't actually new in 2.1. webob was used by the middleware previously, the thought behind not requiring it was that not everyone may end up using the middleware, so requiring webob for the package as a whole would be overkill. Some folks get very picky about packages installing dep's if they're not absolute requirements, maybe that's changed in time though and I can add webob as a dep without ppl whining about it?

Thanks, description updated. And confirmed that we're separately depending on webob already in our software to work around this, so the bug report is mostly for completeness. It might be just as effective to "fix" it by documenting the optional dependency in the readme or something.

Oh, and it was added in 2.0 which we ended up blocking in our requirements lists due to issue #31 (so wouldn't have seen it until 2.1 anyway).

@fungi @bbangert
Guys, I think it makes sense to add the dependency using extras_require and document possibility of installing extra dependencies.

Something like a "middleware" extra so that pip install routes[middleware] drags in webob? That seems a reasonable compromise (though install docs could benefit from updating to reflect this optional dependency either way).

See PR #59.
/cc: @fungi @bbangert


Ignores typedoc readme argument when set to none

The markdown theme produces a README despite readme: none typedoc argument.
 --readme                  Path to the readme file that should be displayed on the index page. Pass `none` to disable the index page and start the documentation on the globals page.

The plugin always produces a README.md file as an entry point to the docs. (it essentially mirrors the behaviour of index.html on the default theme). With the arg --readme none set, this essentially becomes the api index page as opposed to including the contents of the specified readme. Hope that makes sense?


[WIP] fix clusterprovision creation race

use expectations to ensure that clusterDeployment controller does not create multiple overlapping clusterprovisions

Working through trying to understand this but initial thought, could you update the git commit msg on the second commit with some heavier details on what this is doing, how it works and why it's needed in this specific situation.

Working through trying to understand this but initial thought, could you update the git commit msg on the second commit with some heavier details on what this is doing, how it works and why it's needed in this specific situation.

Do you mean the first commit?

I need to copy the controller expectations code from k8s.io/kubernetes/pkg/controller into our codebase. That package is bringing in too much other stuff.

+1 copying sounds good.
I meant the commit with your code :) Whichever it was.

+1 copying sounds good.
I meant the commit with your code :) Whichever it was.

Sure. I will improve on the commit message.

This is great, thank you.
/lgtm

/lgtm


[AVM Module Issue]: search service module should output endpoint URI

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
Module Name
avm/res/search/search-service
(Optional) Module Version
No response
Description
Search service outputs do not include the endpoint name. Users can re-construct it themselves using the conventional URL format like https://${searchService.name}.search.windows.net but the module should be authoritative on this and output the correct endpoint as an output (even if its just doing the above internally).
(Optional) Correlation Id
No response

@stewartadam the resource provider does not return the endpoint URI, so we need to create it within the module. The proposed method in the description (https://${searchService.name}.search.windows.net) only covers the Azure Global cloud and not other environments like US Gov. Unfortunately, the Bicep function environment(), which would provide a clean way to implement the endpoint URI, does not return the DNS suffix for the search service. As mentioned in Azure/bicep#12482, this may not change soon. I suggest waiting for the avm/utl/general/get-environment module (Azure/Azure-Verified-Modules#898), which will serve as an AVM workaround for the missing DNS suffixes in the "endpoints" API.
@Azure/avm-core-team-technical-bicep what do you guys think?

Sounds reasonable to me. The environment() function actually lacks quite a few entries. Fortunately, the endpoint the @stewartadam suggested is deterministic and hence very easy to construct. Once the environment() function or the utl module is implemented, I don't see any harm in adding the output though.


What is the proper syntax for the use of multiple plugins?

I can not for the life of me find one example of the proper way to specify multiple plugins. I can only find single plugin examples which is so frustrating!
plugins: [ChromecastPlugin], [HelloWorld], ???
plugins: [ChromecastPlugin, HelloWorld], ???
Also having trouble loading plugins
Trying to load the nerd stats plugin but its not working

`

plugins: [Dash, SomethingElse, Anything]

Thankyou


canot import name 'plotvol3'

I have the following error. I tried to use the roboticstoolbox on my Ubuntu 22.04 Docker Container.  It runs python 3.10.12
It seems to be similar to https://github.com/bdaiinstitute/spatialmath-python/issues/52

from spatialmath.base import symbolic as sym
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.10/dist-packages/spatialmath/init.py", line 3, in
from spatialmath.pose2d import SO2, SE2
File "/usr/local/lib/python3.10/dist-packages/spatialmath/pose2d.py", line 26, in
import spatialmath.base as smb
File "/usr/local/lib/python3.10/dist-packages/spatialmath/base/init.py", line 8, in
from spatialmath.base.transforms3d import *  # lgtm [py/polluting-import]
File "/usr/local/lib/python3.10/dist-packages/spatialmath/base/transforms3d.py", line 48, in
from spatialmath.base.graphics import plotvol3, axes_logic
ImportError: cannot import name 'plotvol3' from 'spatialmath.base.graphics' (/usr/local/lib/python3.10/dist-packages/spatialmath/base/graphics.py)

or i tried also

from spatialmath import base as base
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.10/dist-packages/spatialmath/init.py", line 3, in
from spatialmath.pose2d import SO2, SE2
File "/usr/local/lib/python3.10/dist-packages/spatialmath/pose2d.py", line 26, in
import spatialmath.base as smb
File "/usr/local/lib/python3.10/dist-packages/spatialmath/base/init.py", line 8, in
from spatialmath.base.transforms3d import *  # lgtm [py/polluting-import]
File "/usr/local/lib/python3.10/dist-packages/spatialmath/base/transforms3d.py", line 48, in
from spatialmath.base.graphics import plotvol3, axes_logic
ImportError: cannot import name 'plotvol3' from 'spatialmath.base.graphics' (/usr/local/lib/python3.10/dist-packages/spatialmath/base/graphics.py)

If not using graphics, a hacky workaround is to just not import that line, i.e. in OP's example:
vi /usr/local/lib/python3.10/dist-packages/spatialmath/base/transforms3d.py
and comment out line 48

This is also a problem for me.

It looks like this is the same as #121 but the resolution there is to uninstall python3-matplotlib which is not very helpful, I need that package.

This is a huge hack, but for the moment you can use pip install spatialmath-python-abarryfix==1.1.12 to get around this.

@myeatman-bdai @petercorke can we get eyes on this one?

yes this seems to be the same as #121 where the conflict was

matplotlib apt installed by ROS, command dpkg - l | grep matplotlib would show version 3.5.1, it's pinned to this version;
matplotlib version required by spatialmath is a newer version (using the pip mechanism, pip install matplotlib, https://pypi.org/project/matplotlib/)

Unfortunately we don't have a good solution, only a workaround
dpkg -r --force-depends python3-matplotlib
pip install spatialmath-python # or spatialmath is already installed, do `pip install matplotlib`

python3-matplotlib is required by ROS and OpenCV.
Here's the mess I get if I try to uninstall it:
$ sudo apt remove python3-matplotlib
[sudo] password for abarry:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cppcheck evince-common fonts-lyx freeglut3 libaom-dev libarmadillo-dev libarpack2-dev libavcodec-dev libavformat-dev libavutil-dev libblas-dev libblosc-dev libcfitsio-dev libcfitsio-doc libcharls-dev
  libdav1d-dev libdc1394-dev libde265-dev libdouble-conversion-dev libevdocument3-4 libevview3-3 libexif-dev libexif-doc libfreexl-dev libfyba-dev libgdal-dev libgdcm-dev libgeos-dev libgeotiff-dev libgif-dev
  libgl2ps-dev libgl2ps1.4 libglew-dev libgphoto2-dev libheif-dev libilmbase-dev libjson-c-dev libjsoncpp-dev libkml-dev libkmlconvenience1 libkmlregionator1 libkmlxsd1 liblapack-dev liblbfgsb0 libnetcdf-c++4
  libnetcdf-cxx-legacy-dev libogdi-dev libogg-dev libopencv-calib3d-dev libopencv-contrib-dev libopencv-core-dev libopencv-dev libopencv-dnn-dev libopencv-features2d-dev libopencv-flann-dev
  libopencv-highgui-dev libopencv-imgcodecs-dev libopencv-imgproc-dev libopencv-ml-dev libopencv-objdetect-dev libopencv-photo-dev libopencv-photo4.5d libopencv-shape-dev libopencv-shape4.5d
  libopencv-stitching-dev libopencv-stitching4.5d libopencv-superres-dev libopencv-superres4.5d libopencv-video-dev libopencv-videoio-dev libopencv-videostab-dev libopencv-videostab4.5d libopencv-viz-dev
  libopencv-viz4.5d libopencv4.5-java libopencv4.5d-jni libopenexr-dev libopenjp2-7-dev libopenni-dev libopenni-sensor-pointclouds0 libopenni0 libopenni2-dev libpcl-apps1.12 libpcl-common1.12 libpcl-dev
  libpcl-features1.12 libpcl-filters1.12 libpcl-io1.12 libpcl-kdtree1.12 libpcl-keypoints1.12 libpcl-ml1.12 libpcl-octree1.12 libpcl-outofcore1.12 libpcl-people1.12 libpcl-recognition1.12
  libpcl-registration1.12 libpcl-sample-consensus1.12 libpcl-search1.12 libpcl-segmentation1.12 libpcl-stereo1.12 libpcl-surface1.12 libpcl-tracking1.12 libpcl-visualization1.12 libpoppler-dev
  libpoppler-private-dev libproj-dev libqt5designercomponents5 libqt5quicktest5 libqt5webkit5 libqt5webkit5-dev libraw1394-dev libraw1394-tools librttopo-dev libspatialite-dev libsuperlu-dev libswresample-dev
  libswscale-dev libtbb-dev libtbb12 libtheora-dev liburiparser-dev libusb-1.0-0-dev libusb-1.0-doc libutfcpp-dev libvtk9-dev libvtk9-java libvtk9-qt-dev libvtk9.1 libvtk9.1-qt libwebp-dev libx265-dev
  libxerces-c-dev libxsimd-dev mercurial mercurial-common nvidia-firmware-535-535.154.05 opencv-data openni-utils pydocstyle pyflakes3 python-matplotlib-data python3-appdirs python3-beniget
  python3-colcon-mixin python3-cycler python3-decorator python3-flake8 python3-fonttools python3-fs python3-gast python3-kiwisolver python3-lz4 python3-mccabe python3-mpi4py python3-mpmath python3-opencv
  python3-pycodestyle python3-pydocstyle python3-pydot python3-pyflakes python3-pythran python3-scipy python3-snowballstemmer python3-sympy python3-ufolib2 python3-unicodedata2 python3-vcstool python3-vcstools
  python3-vtk9 qdoc-qt5 qhelpgenerator-qt5 qt5-assistant qtattributionsscanner-qt5 qtdeclarative5-dev qtdeclarative5-dev-tools qttools5-dev qttools5-dev-tools qttools5-private-dev ros-build-essential
  ros-humble-action-tutorials-cpp ros-humble-action-tutorials-interfaces ros-humble-action-tutorials-py ros-humble-ament-cmake-auto ros-humble-ament-cmake-copyright ros-humble-ament-cmake-cppcheck
  ros-humble-ament-cmake-cpplint ros-humble-ament-cmake-flake8 ros-humble-ament-cmake-lint-cmake ros-humble-ament-cmake-pep257 ros-humble-ament-cmake-uncrustify ros-humble-ament-cmake-xmllint
  ros-humble-ament-cppcheck ros-humble-ament-cpplint ros-humble-ament-flake8 ros-humble-ament-lint-auto ros-humble-ament-lint-cmake ros-humble-ament-lint-common ros-humble-ament-pep257
  ros-humble-ament-uncrustify ros-humble-ament-xmllint ros-humble-composition ros-humble-cv-bridge ros-humble-demo-nodes-cpp ros-humble-demo-nodes-cpp-native ros-humble-demo-nodes-py
  ros-humble-depthimage-to-laserscan ros-humble-dummy-map-server ros-humble-dummy-robot-bringup ros-humble-dummy-sensors ros-humble-example-interfaces ros-humble-examples-rclcpp-minimal-action-client
  ros-humble-examples-rclcpp-minimal-action-server ros-humble-examples-rclcpp-minimal-client ros-humble-examples-rclcpp-minimal-composition ros-humble-examples-rclcpp-minimal-publisher
  ros-humble-examples-rclcpp-minimal-service ros-humble-examples-rclcpp-minimal-subscriber ros-humble-examples-rclcpp-minimal-timer ros-humble-examples-rclcpp-multithreaded-executor
  ros-humble-examples-rclpy-executors ros-humble-examples-rclpy-minimal-action-client ros-humble-examples-rclpy-minimal-action-server ros-humble-examples-rclpy-minimal-client
  ros-humble-examples-rclpy-minimal-publisher ros-humble-examples-rclpy-minimal-service ros-humble-examples-rclpy-minimal-subscriber ros-humble-geometry2 ros-humble-image-geometry ros-humble-image-tools
  ros-humble-intra-process-demo ros-humble-keyboard-handler ros-humble-launch-testing ros-humble-launch-testing-ament-cmake ros-humble-launch-testing-ros ros-humble-launch-xml ros-humble-launch-yaml
  ros-humble-lifecycle ros-humble-logging-demo ros-humble-pcl-conversions ros-humble-pcl-msgs ros-humble-pendulum-control ros-humble-pendulum-msgs ros-humble-qt-dotgraph ros-humble-qt-gui ros-humble-qt-gui-cpp
  ros-humble-qt-gui-py-common ros-humble-quality-of-service-demo-cpp ros-humble-quality-of-service-demo-py ros-humble-ros-base ros-humble-ros-core ros-humble-ros-environment ros-humble-ros2action
  ros-humble-ros2bag ros-humble-ros2cli-common-extensions ros-humble-ros2component ros-humble-ros2doctor ros-humble-ros2interface ros-humble-ros2launch ros-humble-ros2lifecycle ros-humble-ros2multicast
  ros-humble-ros2topic ros-humble-rosbag2 ros-humble-rosbag2-compression ros-humble-rosbag2-compression-zstd ros-humble-rosbag2-cpp ros-humble-rosbag2-interfaces ros-humble-rosbag2-py
  ros-humble-rosbag2-storage ros-humble-rosbag2-storage-default-plugins ros-humble-rosbag2-transport ros-humble-rosidl-default-generators ros-humble-rqt-action ros-humble-rqt-bag ros-humble-rqt-console
  ros-humble-rqt-graph ros-humble-rqt-gui ros-humble-rqt-gui-cpp ros-humble-rqt-gui-py ros-humble-rqt-image-view ros-humble-rqt-msg ros-humble-rqt-publisher ros-humble-rqt-py-common ros-humble-rqt-py-console
  ros-humble-rqt-reconfigure ros-humble-rqt-service-caller ros-humble-rqt-shell ros-humble-rqt-srv ros-humble-rqt-topic ros-humble-rttest ros-humble-shared-queues-vendor ros-humble-sqlite3-vendor
  ros-humble-sros2 ros-humble-sros2-cmake ros-humble-tango-icons-vendor ros-humble-teleop-twist-joy ros-humble-teleop-twist-keyboard ros-humble-tf2-bullet ros-humble-tf2-sensor-msgs ros-humble-tf2-tools
  ros-humble-tlsf ros-humble-tlsf-cpp ros-humble-topic-monitor ros-humble-turtlesim ros-humble-uncrustify-vendor ros-humble-zstd-vendor tango-icon-theme tcl-dev tcl8.6-dev tk-dev tk8.6-dev uncrustify
  unicode-data vtk9

We can't ask people to uninstall OpenCV and ROS to use this, is there any other workaround?

sudo dpkg -r --force-depends python3-matplotlib does work for me, but I think the package should be able to be used by default and a lot of people will run into this.

@slyandsmart @andybarry i edited my "workaround" in previous reply to clarify that we still install matplotlib, but using pip install mechanism instead. but again, that's a hack, not a solution.
please only try it if you want to participate in troubleshooting this issue as it might break your workflow and cost you more time.
for a proper solution, we can look through the spatialmath code and perhaps we don't have to use features from newer matplotlib versions, in which case we will push an update and stick to the same matplotlib version pinned by ROS2 humble.

Would the best solution be moving all plotting functions to their own file that doesn't get imported automatically by anything?

for a proper solution, we can look through the spatialmath code and perhaps we don't have to use features from newer matplotlib versions, in which case we will push an update and stick to the same matplotlib version pinned by ROS2 humble.

That would be fantastic!

This issue continues to be a big problem for us.  The apt hack breaks apt for everything else, so it makes all sorts of things not work.
To be honest, we're on the verge of using something else because of this issue.

@andybarry sorry to hear that! I am escalating this issue and hopefully cut a new release with a properly pinned matplotlib version.
will update here again once we have an estimate.

@andybarry it seems simply pinning the version would work, https://github.com/bdaiinstitute/spatialmath-python/pull/133
We still need to run more tests to make sure this change doesn't break anything. In particular, as the ROS2's apt-installed matplotlib (python3-matplotlib) is slightly old, it would also prevent installing numpy 2.0 or newer - we had to modify the pyproject.toml to narrow the numpy version to "numpy ... <2".
Tests we've done so far are listed in the PR description.
If you would like to participate in the testing, please feel free to checkout the test branch issue-127/pin-matplotlib-version and pip install ..

This is awesome, I will test it tomorrow!
On Thu, Aug 1, 2024, 9:55 AM Jien Cao @.***> wrote:

@andybarry https://github.com/andybarry it seems simply pinning the
version would work, #133
https://github.com/bdaiinstitute/spatialmath-python/pull/133
We still need to run more tests to make sure this change doesn't break
anything. In particular, as the ROS2's apt-installed matplotlib
(python3-matplotlib) is slightly old, it would also prevent installing
numpy 2.0 or newer - we had to modify the pyproject.toml to narrow the
numpy version to "numpy ... <2".
Tests we've done so far are listed in the PR description.
If you would like to participate in the testing, please feel free to
checkout the test branch issue-127/pin-matplotlib-version and pip install
..
—
Reply to this email directly, view it on GitHub
https://github.com/bdaiinstitute/spatialmath-python/issues/127#issuecomment-2263133968,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ5LKTI4TIFVK3GM5IQSJLZPI43ZAVCNFSM6AAAAABKLRSMPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGEZTGOJWHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@andybarry please kindly share your findings.
When testing in a ROS2 docker (official humble, community version), i noticed that scipy also came preinstalled with it (apt installed), and that version was also a bit old, which would further narrow the range of numpy to <=1.25 (change not included in this work-in-progress PR), seemingly a bit too restrictive.
I am curious if you see similar issue (scipy throws warning requiring lower version of numpy) in your setup?

This appears to work for me!  We will try it on a few different configurations here and let you know if we find any issues.

@Yazan-Soliman thank you for testing the changes!
Did you have to change the numpy version range (in current PR, it's numpy>=1.22,<2) in your setup?
Asking because in my test the ROS2 docker seemed to have an old scipy which warned me to further narrow the numpy range, but perhaps the docker image i used was not typical.

@jcao-bdai  in my environment i am using  numpy Version: 1.24.4

@andybarry could you please confirm if this issue can be closed?
(the underlying PR has merged, given the feedback so far)

Yes, thanks, can close.


Bugfix Handle Role Detail drawer closing properly

@Da-Colon does this fix the bug where clicking "x" incorrectly navigated back to Roles Index of closing the drawer and staying on Create Proposal?


fixed math in Camera::project_position

The mouse coordinates are now properly mapped from 2D to 3D. Old bugged version mapped
top left corner of window (0,0) to bottom left corner of camera viewport (eg. to negative y-axis instead of positive y-axis).

Makes sense


class "border-b" is not working

<CodeInput
ref="codeinput"
className="border-b"
keyboardType="numeric"
activeColor="white"
inactiveColor="white"
inputPosition='left'
cellBorderWidth={1}
space={10}
autoFocus={true}
codeLength={4}
size={60}
onFulfill={(code) => this.verify(code)}
containerStyle={{ marginTop: 50 }}
codeInputStyle={{ color: "white", fontSize: 32 }}
/>
This is the code i used to implement underline codeinput but it's not showing any border.
Is there any solution for that?
Thanks

remove cellBorderWidth={1}


fix(typescript): migrate to typescript

Does not change the interface to any consumer.

I guess I'll move it to the m2h_two repo... should be easier now though! Thanks 💯

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Performance] “addSelectKeyListener” should not be called when search is enabled

Currently
addSelectKeyListener() gets called every time the dropdown opens (toggleOpen). It adds an event listener to the native <select> then focuses the the select.
Problem
This doesn’t make sense when search is enabled since we call focus() on the searchbox right after. (Focus changes are expensive when we have a very large dataset.)
Wanted
Don’t call addSelectKeyListener() when this.search is true.

Probably also a good idea to move the focus() call out of addSelectKeyListener(). I think it’s an unexpected action for a method with that name to take.


Revert "53182 submit button jump confirmation page"

Reverts Expensify/App#53529

Ah nvm, this is already being addressed: https://github.com/Expensify/App/pull/54634


Introduce vitest to core/quantity

Continuation of this effort: #7165

can you edit the launch.json debug profile for running core quantity tests to be the same as core bentley and common

can you edit the launch.json debug profile for running core quantity tests to be the same as core bentley and common

done

My only feedback is that in some places you go from assert.strictEqual to vitest's toEqual, when technically they are slightly different including that strictEqual asserts the types are identical and toEqual doesn't (toStrictEqual would be the equivalent). If the tests pass I don't think this is worth changing though


Feature/vizzuality logo in about

Add vizzuality logo

I add a small fix for the error page also.


WIP-Temporary-Maintenance-Page / 01

A temporary maintenance page will be created to be pushed onto the main branch while the actual site is worked on.

PR created and successfully merged branch to main. Issue will now be closed and locked.


Round down FormattedTime seconds

Right now, a time like 59.8 will result in:
hours = floor(59.8 / 3600) = 0
minutes = floor((59.8 % 3600) / 60) = 0
seconds = round(59.8) % 60 = 0
Thus, 0:00 when it is formatted. This change corrects that to 0:59. 59.4 has always displayed correctly as 0:59 because the round function results in 59 % 60 = 59.
The seconds should really still be 59 because the time hasn't turned over to 1 minute yet. I can't really think of a case where it should round up.

This makes sense, good catch!

0.5.17 released!


CRA problems

We cannot use examples outside the src folder
We cannot use global styles in App for CSS Modules
We cannot use different webpack loaders without eject
We cannot use one bundle file

Research to custom configs for CRA: https://github.com/lamartire/sharec


Support null and non-json responses in FetchService. Fixes #266

Extract general purpose fetch() method from fetchJson()
Handle 204 responses in fetchJson()

In hoist-sencha we decoded/returned JSON based on the content-type - would it be better to do that here so we don't have a new method (and need to bomb a bunch of code)?  It's also the case that the vast majority of calls are for JSON content, so would be nice to keep the shorter function name for the main use case.
Another alternative if the content type proved unworkable for some reason would be to add an option to the method - e.g. decodeJSON - that defaults to true but is available to turn off.

Sorry missed that key / obvious point - was rushing

Updated the docs. I think I followed the new format correctly but please let me know if I missed anything!

👍 Great documentation!


Fix test cask macOS dependency

Closes #7777.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Thanks @gromgit!


Missing factor of 1/2 in documentation for quad_form

A factor of 1/2 missing from documentation for quad_form

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

Sorry, my bad. It was correct.


setState() callback broken

I upgraded to the recent Fauxmo 3.2 version and discovered that the callback signature for the setState() callback seems to have been changed, preventing my application from being compiled.
Where can I find a documentation on how to interpret the additional 3 unsigned int values?
For the time being I added those with a default = 0, but am not sure if the remainder will behave as before?

Where do you see the additional unsigned int values? I see and use this onSetState() function.
 fauxmo.onSetState([](unsigned char device_id, const char * device_name, bool state, unsigned char value)

Where do you see the additional unsigned int values? I see and use this onSetState() function.
 fauxmo.onSetState([](unsigned char device_id, const char * device_name, bool state, unsigned char value)

In fauxmoESP.h line 103 we have
 void onSetState(TSetStateCallback fn) { _setCallback = fn; }

`TSetStateCallback```id typedef'd in line 75:
typedef std::function<void(unsigned char, const char *, bool, unsigned char, unsigned int, unsigned int, unsigned int)> TSetStateCallback;

Are you using the latest master branch in git? If so, that's my fault.
In making changes to add ability to change colours I think there's still an incorrectly overloaded function. I've been thinking that I didn't like the way I implemented the interface for changing colours and will likely roll it back.
For now, if you're using git, try checking out the source at commit 74a69c9

I think I do use the master branch indeed. I am using Platformio for development and that hinted me to the library update after that I got the error on using the older onSetState function signature.


Documentation refactoring

Description
Current documentation layout - Github README.md doesn't reflect actual development and the user is not able to follow how to properly setup the environment, dataset import and trigger the performance benchmark and also some parts are still missing.
Proposed changes - chapter layout:

environment provisioning
** default -> minikube automation
dataset import
** basic setup is a part of the minikube automation
** automated way to load larger datasets
performance benchmark
** automated script to run it with particular parameters e.g. --server-url, --test, --client-secret, etc.

Discussion
No response
Motivation
No response
Details
No response

@lhanusov perfect timing - take a look at this PR and add anything additional which is missing from your suggestion as a review comment :) https://github.com/keycloak/keycloak-benchmark/pull/166 this modifies the existing documentation which is splintered and the new documentation is live at https://www.keycloak.org/keycloak-benchmark/

@kami619 - even after the change I can see that there should be a more step-by-step guide chaining the different projects together in a walk through. Still, get that other PR merged first, then use this issue to add what's missing.

Fair point, it would be needing more betterment in terms of chaining things.

I don't know if this is the right place for this, but there is a fairly large disconnect between the Preparing Keycloak for testing manual steps and the next Running benchmarks from the CLI step. Unless you read the manage_gatling_client.sh script (which isn't included in the distribution), you won't know how to set the values correctly so that the tests will function properly.

@xgp https://www.keycloak.org/keycloak-benchmark/benchmark-guide/latest/preparing-keycloak#manual-configuration, the steps specified in this section are what's automated in the manage_gatling_client.sh. Can you please elaborate a little bit more on the disconnect you are facing ? Would love to collect the feedback to make it better :)

@kami619 Thanks for looking at this. I'm referring to the default values.
In the manual steps in the documentation, it leaves it up to you to choose the realm name, the client name, and the client secret. Then, the next step doesn't tell you where to use/set the values you chose. There should be documentation to tell you where to set those values in the benchmark config.
If you use the script, it picks realm-0 realm name, gatling client name, and setup-for-benchmark client secret, and then the scenarios "just work".

fair point, we'll update the docs to reflect suggested/used default values. Thanks for bringing it up, anything else you might face as a hurdle in connecting the dots, do log it as a separate issue. Thanks again :)

@kami619 This issue is probably outdated now, isn't it?

@kami619 Thanks for looking at this. I'm referring to the default values.
In the manual steps in the documentation, it leaves it up to you to choose the realm name, the client name, and the client secret. Then, the next step doesn't tell you where to use/set the values you chose. There should be documentation to tell you where to set those values in the benchmark config.
If you use the script, it picks realm-0 realm name, gatling client name, and setup-for-benchmark client secret, and then the scenarios "just work".

I think the issue @xgp pointed out still exists. We need to atleast address that before closing out the broader ticket.


fix(router/atc): pcre regex compatibility

Summary
The new atc-router does not support some PCRE regex escape characters,
this PR removes some special escape characters, tries to be compatible with PCRE.
See FTI-4446
Checklist

[x] The Pull Request has tests
[ ] There's an entry in the CHANGELOG
[x] There is not a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

function sanitize_regex
update test cases

Now this fix only works in traditional_compatible, should we do the same thing in expressions?

After some discussion, we decide to use another solution.


Extension causes high cpu load

Issue Type: Performance
Extension Name: html-css-class-completion
Extension Version: 1.18.0
OS Version: Windows_NT x64 10.0.17134
VSCode version: 1.32.1

:warning: Make sure to attach this file from your home-directory: C:\Users\Lubunda Musonda\Zignd.html-css-class-completion-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Duplicate of #155. Also, it is missing the file you were expected to attach.


GH-36994: [Java][CI] Enable support for JDK21

Rationale for this change
Enable support for last Java JDK 21 version
What changes are included in this PR?
To be able to build Arrow Java using JDK21
Are these changes tested?
For initial testing, Amazon Corretto was used, but at the end Temurin JDK21 docker image should be used.
Are there any user-facing changes?
No
Closes: https://github.com/apache/arrow/issues/37914

Closes: #37914
Closes: #36994

FYI Consider: https://adoptium.net/blog/2023/09/temurin21-delay/

It seems minus that flaky test, things work on Java 21?

It seems minus that flaky test, things work on Java 21?

I tested it locally without problems and also on my local PR at https://github.com/davisusanibar/arrow/pull/8. The current errors are caused by memory leaks.
Is it possible to rerun failed job tasks?

I kicked the Java jobs


Unexpected behavior on adding multiple hidden layers

I've modified the NeuralNetwork code so the class constructor receives the number of hidden layers and the number of nodes per hidden layer, also modifying the guess and training functions to work with multiple hidden layers. It seems to work but, in the XOR example, as I create NNs with increasing number of hidden layers, the results come back wrong more and more frequently, to the point of at 5 hidden layers I always get wrong answers. Is it something I should expect or maybe there's something wrong with my implementation? My code: https://pastebin.com/iF8UVhSU

I have not looked at your code so there could be something wrong there but I have experienced with my own from-scratch NN that for simple tasks like XOR having lots of hidden layers makes it worse.


Program crashed after start

Branch: develop
There is no error and the program says: "All workers are running!" but nothing is running.
I've tried to run with docker or in python enviroment.

Hi @lewtran
If you're using the stdout notifier just check the latest code. I wrote a fix a few minutes ago.
If not, tell me what is the command you're executing and the output you're getting.
Best

Thank you for your response @laliux
I'm using Telegram notifier.
I've tried to execute two commands:
docker run --rm -ti -v $PWD/app:/app dev/crypto-signals:latest
The output is:
/usr/local/bin/python: can't open file 'app.py': [Errno 2] No such file or directory
docker run --rm -di -v $PWD/app:/app dev/crypto-signals:latest
And here is the output:
'05be1706538ba0088e4eece7b36757bcdcb8e789c3d29378bb4c55980fc09a2b'
It's seem like the docker is running but crashed right away and nothing happend.

@lewtran
Can u show your config file ...

@laliux Thank you and please close this issue.
The problem comes from my Docker version, some package cannot build correctly but without and error. After I upgrade docker, the program runs fine.


installation on CentOS 7: 'Could NOT find ZLIB: Found unsuitable version "1.2.7", but required is at least "1.2.8"'

Hello!
I'm trying to install racon on CentOS 7. When I run cmake -DCMAKE_BUILD_TYPE=Release .. I get the following error:

CMake Error at /home/centos/cmake-3.26.0-rc6-linux-x86_64/share/cmake-3.26/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find ZLIB: Found unsuitable version "1.2.7", but required is at
least "1.2.8" (found /usr/lib64/libz.so, )
Call Stack (most recent call first):
/home/centos/cmake-3.26.0-rc6-linux-x86_64/share/cmake-3.26/Modules/FindPackageHandleStandardArgs.cmake:598 (_FPHSA_FAILURE_MESSAGE)
/home/centos/cmake-3.26.0-rc6-linux-x86_64/share/cmake-3.26/Modules/FindZLIB.cmake:200 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
build/_deps/bioparser-src/CMakeLists.txt:22 (find_package)

I installed zlib 1.2.13 following these instructions but the error persists. I suspect I need to tell CMake where to find the library at compile time, but am unfamiliar how to do so. Would you know a solution for this? Thank you!

Hello,
maybe -DZLIB_LIBRARY=<path to library> -DZLIB_INCLUDE_DIR=<path to include> while running cmake.
You can also use racon through bioconda: https://anaconda.org/bioconda/racon.
Best regards,
Robert


RHBRMS-2525: Business-central startup error: jGIT: Cannot run program 'bash'

See https://issues.jboss.org/browse/RHBRMS-2525
This overrides the version in ip-bom until we move to a version containing https://github.com/jboss-integration/jboss-integration-platform-bom/pull/327

@psiroky Hi.. I think this closes the loose ends (until we can use a newer ip-bom). WDYT?

I believe we should override the version also in uberfire to make sure the jgit integration still works with the latest version.

@psiroky Good catch!
See https://github.com/uberfire/uberfire/pull/477 too.

+1 to merge (together with the UF one)


Allow a more flexible AllowOrigin response

From @mharthoorn on Wednesday, October 5, 2016 12:43:56 PM
Instead of the CorsService peeking into the CorsPolicy
   policy.Origins.Contains(origin)

A method OriginAllowed(string origin) would allow for a much more flexible lookup policy. The service would then call:
  policy.OriginAllowed(origin)

This allows the policy to respond with a more ad hoc response like a (database) lookup.
The default would simply be:
        public virtual bool OriginAllowed(string origin)
        {
            return this.Origins.Contains(origin);
        }

But an override policy could become something like:
        public override bool OriginAllowed(string origin)
        {
            return repository.Exists<Sites>(s => s.Origin == origin);
        }

Copied from original issue: aspnet/CORS#89

From @Choc13 on Sunday, October 30, 2016 9:57:37 AM
See issue #75

From @Eilon on Wednesday, November 23, 2016 2:35:06 PM
We will consider this for the next version.

This is true today - CorsService uses CorsPolicy.IsOriginAllowed to determine if an origin is allowed. CorsPolicy has a settable delegate that lets you configure it - https://github.com/aspnet/CORS/blob/master/src/Microsoft.AspNetCore.Cors/Infrastructure/CorsPolicy.cs#L77


Triage on ostracon#506

Opinion

Rather not apply

Reason

affected parts are test-related parts and parts that are removed from the upstream


Some setup guidance on error on first time executing a SQL

Using V1.12.4
Was able to authenticate and browse the default project set in settings.
When clicking a table or running a simple SQL such as " select 1 as a"  I have the following error "Query: Required Parameter Missing"

Added some setup guidance in v1.14.0 😄
Can't find any credential:

Can't find key file:

Can't find a project ID:

Logged in with an unauthorized account:

Set an unauthorized key file:


MontagePager - set_title does not work with imshow()

ax = mp.pop()
ax.set_title('abc') # not working

Needs more triages, as I couldn't replicate the bug.
This was the test code, which generates subplot titles:
# curl -LO https://github.com/aws-samples/amazon-sagemaker-gluonts-entrypoint/raw/main/references/repo-layout.png

from PIL import Image
import pandas as pd
from pathlib import Path
from smallmatter.ds import MontagePager

img = Image.open('repo-layout.png')
mp = MontagePager(Path('output'), savefig_kwargs=dict(transparent=False))
for i in range(20):
    ax = mp.pop(f'abcd-{i}')
    ax.set_title(f'ABCD-{i}')
    ax.imshow(img)
mp.savefig()


segment has no compress for complex type column

Please provide a detailed title (e.g. "Broker crashes when using TopN query with Bound filter" instead of just "Broker crashes").
Affected Version
26.0.0
Description
segment has no compress for complex type  column, when  complex column are sparse with many null values, a lot of space is wasted

#16863 adds the option for compression for complex metric column types which do not have specialized implementations


Add stack allocation check back to x86 experimental-flags benchmarks

It looks like this is impacting some tile size configurations leading to quite some regressions

It looks like this is impacting some tile size configurations leading to quite some regressions

This is an NFC change for benchmark suites. We can add the check back because I fixed some issues in https://github.com/openxla/iree/pull/14441
It looks like the regression is introduced by https://github.com/openxla/iree/commit/80312afef2426a79646852636d6e5cce41cc4b43, but we need some eyes to verify it.

I reverted 80312af and the got 23% improvement on BertLargeTF https://github.com/openxla/iree/pull/14457#issuecomment-1644334469


Update file structure for code readability.

This update move functions found in esp_dmx.h into dmx/sniffer.h and dmx/agent.h to reduce the size of esp_dmx.h.

Examples appear to be working on both ESP-IDF and Arduino. Merging...


Support for hhvm WholeProgram optimizations (drop facades)?

Hi
I tried to compile my project (L5.2) using the repo mode in hhvm and got an error:
Exception: class_alias with non-literal parameters is not allowed when WholeProgram optimizations are turned on
Is there a way to remove facade's logic which causes this (AliasLoader) since I don't use the facades anyway?
also found this: https://github.com/facebook/hhvm/issues/867

While I support the ability to disable it, I assume there are a lot of packages that assume facades exist, so it might not be possible to practically disable facades.

Is there a way to remove facade's logic which causes this (AliasLoader) since I don't use the facades anyway?

I doubt this will ever happen. Laravel needs this outside facades too.

I assume there are a lot of packages that assume facades exist, so it might not be possible to practically disable facades.

No package should ever use facades, and especially never use facade aliases.

No package should ever use facades, and especially never use facade aliases.

Unfortunately, I see a lot of poorly written packages that do use them though. Facades are intended to speed up application development. Libraries and packages are still expected to use proper code.

The quicker we can get rid of Facades, the better.