improve online check

internet.sh checks if device is online by pinging dns services - thats suboptimal, because this is happening in a loop done by background process. This could be avoided in the future by first checking if bitcoind system service is active and the checking the numbers of peers (later use redis cache) also check if tor service has similar info that can be used. If those are services have peer connection the device is online. If not then fallback check ping to dns services.

OK implemented the Bitcoin peer check ... but it seems that Bitcoind signals peer connections long after network connection gets removed. Test this again in a setting where internet can be cut while local network connection is still OK.


TTY::Screen.width not respecting my Terminal window size

Describe the problem
While using Fastlane, the width of the table when Fastlane displays the commands is defaulted to 80.
I know this repository is not fastlane, but it seems like the culprit is in print_table.rb > def transform_output(rows, transform: :newline) > number_of_cols = TTY::Screen.width.
I tried to fix this issue but to no avail with my given time. Tried debugging with logs such as:
def transform_output(rows, transform: :newline)
  ...
  number_of_cols = TTY::Screen.width
  puts "hello"
  puts number_of_cols

The above always prints out 80 even when I set my Terminal window to different size and width.
Steps to reproduce the problem
Run fastlane and the width of the available command is confined to 80, and it makes things hard to read.
Actual behaviour
The table width when I type fastlane is always the width of 80.
Expected behaviour
When I change my window width to X, the width should be X instead of 80.
Describe your environment
fastlane 2.108.0
macOS Terminal 2.9.1 (421.1)

OS version: macOS 10.14.1 Mojave
Ruby version: ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-darwin18]
TTY::Screen version: v0.6.5

Hi Genki,
The thing is it all works fine for me on Ruby 2.5.3 on Mac and Debian. The reason you're seeing 80 as the default is because other 10 ways of checking width of your terminal have failed! This is last resort really when Ruby itself cannot even determine the width of your terminal!
So you would need to debug your machine for me to see what each call is returning. Could you please check the following in your IRB session:
require 'tty-screen'
TTY::Screen.width => ?
TTY::Screen.size_from_ioctl => ?
TTY::Screen.size_from_io_console => ?
TTY::Screen.size_from_readline => ?
TTY::Screen.size_from_tput  => ?
TTY::Screen.size_from_stty => ?
TTY::Screen.size_from_env => ?

ENV['COLUMNS]' => ?
ENV['LINES'] => ?

Then in your terminal please let me know what the following commands return:
stty size  => ?
tput cols => ?

Thanks for getting back really quick.
I ran the commands you provided and they do get the expected values rather than the default 80 as follows:
irb(main):003:0> require_relative 'tty-screen-0.6.5/lib/tty-screen.rb'
=> true
irb(main):004:0> TTY::Screen.width
=> 149
irb(main):005:0> TTY::Screen.size_from_ioctl
=> [54, 149]
irb(main):006:0> TTY::Screen.size_from_io_console
=> [54, 149]
irb(main):007:0> TTY::Screen.size_from_readline
=> [54, 149]
irb(main):008:0> TTY::Screen.size_from_tput
=> [54, 149]
irb(main):009:0> TTY::Screen.size_from_stty
=> [54, 149]
irb(main):010:0> TTY::Screen.size_from_env
=> [54, 149]
irb(main):011:0> ENV['COLUMNS]'
irb(main):012:1> ENV['LINES']
$ stty size
54 149
$ tput cols
149

It seems like I can only repro when I run fastlane. Perhaps because I installed fastlane through Homebrew? I'll do some more research.

For context, when I run fastlane with some debugging:
def transform_output(rows, transform: :newline)
        return rows unless should_transform?

        require 'fastlane_core/string_filters'
        require 'tty-screen'

        number_of_cols = TTY::Screen.width
        puts "test1"
        puts number_of_cols
        puts TTY::Screen.size_from_ioctl
        puts TTY::Screen.size_from_io_console
        puts TTY::Screen.size_from_readline
        puts TTY::Screen.size_from_tput
        puts TTY::Screen.size_from_stty
        puts TTY::Screen.size_from_env

        puts "ENV"

        puts ENV['COLUMNS']
        puts ENV['LINES']

        puts "genkitest2"

I get result as follows:
genki$ fastlane
[22:05:44]: fastlane detected a Gemfile in the current directory
[22:05:44]: however it seems like you don't use `bundle exec`
[22:05:44]: to launch fastlane faster, please use
[22:05:44]:
[22:05:44]: $ bundle exec fastlane
[22:05:44]:
[22:05:44]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[22:05:45]: ----------------------------------------
[22:05:45]: --- Step: Verifying fastlane version ---
[22:05:45]: ----------------------------------------
[22:05:45]: Your fastlane version 2.108.0 matches the minimum requirement of 1.105.0  ✅
[22:05:45]: ------------------------------
[22:05:45]: --- Step: default_platform ---
[22:05:45]: ------------------------------
test1
80

ENV

genkitest2
[22:05:45]: Welcome to fastlane! Here's what your app is setup to do:
+--------+------------------+-----------------------+
|              Available lanes to run               |
+--------+------------------+-----------------------+
| Number | Lane Name        | Description           |
+--------+------------------+-----------------------+
| 1      | ios test         | Runs all the tests    |
| 2      | ios beta         | Submit a new Beta     |
|        |                  | Build to Apple        |
|        |                  | TestFlight This will  |
|        |                  | also make sure the    |
|        |                  | profile is up to date |
| 3      | ios release      | Deploy a new version  |
|        |                  | to the App Store      |
| 4      | ios release_lite | Lite version app      |
|        |                  | store                 |
| 0      | cancel           | No selection, exit    |
|        |                  | fastlane!             |
+--------+------------------+-----------------------+

I'm not sure installation vi Homebrew is doing it. However, you can always try installing directly via gem install fastlane and checking it this way.
It is interesting that none of the TTY::Screen methods can actually determine terminal size, even Unix tools like tput or stty when called inside fastlane instance. This suggests to me that the environment the fastlane binary runs in must do some serious modifications to the shell, like messing around with $PATH and environment variables? I don't know much about the tool but there must be something happening outside of the transform_output method that influences this behaviour. Are they overwriting Ruby system call to run commands?
I've seen this before though but in CI environments where script runs as non-login shell and there are virtually no utilities installed and no environment variables present. This isolates the script but similarly doesn't allow to detect the terminal size since such thing doesn't really exist. But why would fastlane need to do this?
@KrauseFx Turns out when fastlane is called it strips out env variables so that the ENV['COLUMNS'] is nil. Do you happen to know why fastlane would behave this way?  Sorry don't know much about the tool...


Can't get past requestPermission

My program keeps getting stuck on requestPermission as the promise never resolves. It never returns the grantedPermissions object and it remains empty. I get the dialogue box to allow access to health connect but when I click steps/distance and click allow, I get back to my main screen and no state is updated, as hitting allow doesn't finish that requestPermission method. It will never reach that console.log('hello) step or write to my state field, and as such androidPermissions remains empty. I'm not using expo.
console.log('1');
const grantedPermissions = await requestPermission([
  { accessType: 'read', recordType: 'Steps' },
  { accessType: 'read', recordType: 'Distance' },
]);
console.log('hello')
setAndroidPermissions(grantedPermissions);

Did you follow the document to setup your Android project in the native code?
https://matinzd.github.io/react-native-health-connect/docs/get-started

Yes I did. I do get permissions but await requestPermission() will never finish running and return the granted permissions. I have to run requestPermissions twice to see the updated permissions using getGrantedPermissions.
Also, how do we link/grab the steps or distance for each exercise session? I can read the cycling, walking, or running sessions I've done but I can't get their respective distances. How do I get that?
Lastly, do you know how distance is actually recorded? Because I see loads of distance records that last around 2 ms each, instead of entire walking sessions around 30 minutes.

Please open another issue for the second question. For the permission issue please send me a reproduction so I can find what's going on. Thanks!

Also try to always fill in the bug report template for other repositories as well. Removing the template and not providing any debug/version information will reduce the possibility of fixing the issue.
Thanks for your collaboration.

I faced the same issue.requestPermission as the promise never resolves

@BlocknBoom123

Yes I did. I do get permissions but await requestPermission() will never finish running and return the granted permissions. I have to run requestPermissions twice to see the updated permissions using getGrantedPermissions.
Also, how do we link/grab the steps or distance for each exercise session? I can read the cycling, walking, or running sessions I've done but I can't get their respective distances. How do I get that?
Lastly, do you know how distance is actually recorded? Because I see loads of distance records that last around 2 ms each, instead of entire walking sessions around 30 minutes.

Has there been any progress on finding a solution to this issue?

Duplicate of https://github.com/matinzd/react-native-health-connect/issues/147.
Closing.


Missing semicolon

Amend 45e44ac7d1d2c3ed41c6d6cb2438452fcb74a629 from #7935

Thanks god (and @asterite too) we don't have them in Crystal :smile:


/deis/platform/version missing in new installation

Recently I've recreated my cluster from scratch with Deis 1.9. Today I've noticed that there's no /deis/platform/version key present. On http://docs.deis.io/en/latest/installing_deis/install-platform/ page there are no instructions to set version, though on http://docs.deis.io/en/latest/managing_deis/upgrading-deis/ there are.
Is this key not required? That's weird that you have to set it for upgrade, but not for installation.

Is this key not required? That's weird that you have to set it for upgrade, but not for installation.

It's not required. The version is first read from /deis/platform/version, which overrides the default value in /etc/deis-release. The etcd key enables you to override the default version, such as when you're upgrading.

Ah, great. Thank you.


Imp catcher - Aggressive npcs in the area force local player to be in combat.

If a snake or scorpion attacks the local player, the isInCombat function returns true and can either kill the local player (low lvl localplayer) or force it to be stuck (if the auto retaliation is off) and not attack any imps for the duration of the running script.

another solution is to find an area with the only possibility of other attackable NPCs in the area being Imp(s)


Fix tranq rounds injecting when reflected

About the PR

Tranquilizer rounds no longer inject their target when they are successfully reflected.
Why / Balance

Fixes #26137
Technical details

Changed SolutionInjectOnCollideSystem to subscribe to ProjectileHitEvent instead of StartCollideEvent. This also simplifies the logic a little and removes a component field (FixtureId), since SolutionInjectOnCollideSystem no longer has to check for fixture match or fixture hardness (these are already checked by ProjectileSystem before raising ProjectileHitEvent).
Media

https://github.com/space-wizards/space-station-14/assets/85356/beb47792-5408-4231-ba96-97be25a96e8c

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

fix: Reflected tranquilizer rounds no longer inject the character who reflected them.

Our strongest warrior, fixing bugs in record time


Prevent already closed applications being 'terminated'

I just noticed the option to definitively close an application is also available for applications that have been approved (and have thus been 'closed' already).

Renamed the title, as this will probably also apply to already rejected or 'revision necessary' reviews as well


IOS - How to remove touch sound while tapping on any actions

Hi,
I hear a touch sound whenever I tap on any widgets in Flutter using ios. How to disabled the sound programatically on Flutter and does all apps made by Flutter produce such sound on ios?
I can't 100% sure that this issue relates to the iphone itself, but other apps installed on it such as whatsApp and pre-installed apps doesn't produce the touch sounds.
Thank you.

Hi @haizadvnet
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


/Spectators Option for /LFG

Is your feature request related to a problem? Please describe.
Currently, SpellBot sends a link to spectate a game directly to the members who are playing the game. This isn't very useful because it's only visible to players already in the game.
Describe the solution you'd like
I'd like a /Spectators Boolean option added to the /LFG command. When set to true, it would add a Spectate button link to the original LFG interaction embed for users to join and spectate. It would also allow other discord users to join the voice channel if the relevant option is enabled. Ideally, the created voice channel would match the permissions of the text channel/thread /LFG was originally used in.
Describe alternatives you've considered
Add a SpellBot server setting to set the default behavior for this option. If set to enabled, the above functionality would apply to all games created with SpellBot.

Hi @wise-io, thanks for the issue report! Would it be possible to use the Toggle Public Links feature of the /setup command to turn on the Public Links setting on your server?
Used the /setup command:

Clicked the Toggle Public Links button:

And now when I use /lfg in a channel, the links (voice, game, and spectate) are all visible directly in the channel:

This feature is off by default as a way of combating abuse. In some guilds users will harass others by constantly joining their games to shout at them. When the links are only shown in direct messages, it prevents this kind of harassment.
Note that admins have another option for finding information about a game, even if Public Links is off. They can use the /info command to get details. For example, if I run /info game_id: SB221496 I get:

Do these features resolve this issue for you?

Holy cow. Not sure how I missed this functionality. Thank you for responding and sorry for wasting your time with this issue!
Thanks again for the awesome bot!


Create a shipment - submitting the draft

Hi team, I am using the Trexity API with sandbox environment and I am wondering if there is any way of submitting the draft of the created route.
For now I am only able to draft a route and update the parcels. I went through the API documentation but I was not able to figure out if there is a way of submiting a drafted route. (I guess it might not be possible hence when we submit manually, we have to agree on some conditions...).
Best regards,
Francois

Hey @Francois-Jo, you can schedule the shipments when creating them or you can schedule the shipment with a request to update the shipment. However, in the sandbox environment there are no couriers so beyond scheduling, the shipment lifecycle stops there.

Hi @dschnare , thank you for your quick reply. Scheduling the shipment is fine, it is more that when I create a shipment, it stays in the status "draft" :

and there is no way to "submit" it : we can only confirm delivery manually

Is there a way to "confirm the delivery" through the API ?

That's correct. You can schedule the delivery via the UI (your second screenshot) OR via the API using the "pickupStartAt" field in the request to create the shipment or update the shipment. However, the lifecycle of the shipment will not proceed past this point.


port gradle improvements to Lucene

Description
Port https://github.com/apache/solr/commit/7a9ce356bc7c90c8237437b1e16ed030e4d67900 and https://github.com/apache/solr/commit/bde8c14bddecc2a417d2fd36abe965675e8e670e to Lucene

Actually the basic changes can simply be cherry-picked cross-repository, so maybe its easy. I can also have a look.

Yeah I tried cherry picking the changes from solr but it looked like there were some small differences between them that required a few changes.

The problem is often that some changes in Lucene were not ported to Solr. It is often advisable to start in Lucene as it often is more modern. I know the problem. It still often works very easy.

Submitted Gradle Optimizations PR

Handled by https://github.com/apache/lucene/pull/12150


Added source File name for emitAsset func

Signed-off-by: Gurkiran Singh<EMAIL_ADDRESS>

What kind of change does this PR introduce?
Added the source File Info for emitAsset func .
Resolves #13695
Since, this is my first pr to webpack, I wasn't sure how to test this after making the changes. If someone can please let me know, that be really helpful.

Did you add tests for your changes?
No

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
Nothing

/cc @snitin315 Can you resend this and add a test case, thank you

Fixed by https://github.com/webpack/webpack/pull/15888


Test-only modules don't get fixed

rustfix does not seem to descend into #[cfg(test)] modules.
Test case
$ rustup --version
rustup 1.11.0 (e751ff9f8 2018-02-13)
$ cat rust-toolchain
nightly-2018-07-18
$ cargo fix --version
cargo-fix 0.4.1

lib.rs
#![feature(rust_2018_preview)]
use helpers::*; // This should be fixed

#[cfg(test)]
mod tests;
mod helpers;

pub fn exported_foo() -> usize {
  foo()
}

helpers.rs
pub fn foo() -> usize { 1 }

tests.rs
use helpers::*; // This does not get fixed and it should

#[test]
fn it_works() {
  assert_eq!(1, foo());
}

Output of cargo fix
diff --git a/src/lib.rs b/src/lib.rs
index 54c2d4a..eaa3bdf 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -1,5 +1,5 @@
 #![feature(rust_2018_preview)]
-use helpers::*;
+use crate::helpers::*;

 #[cfg(test)]
 mod tests;

Expected result
That use helpers::* in tests.rs would get rewritten to use crate::helpers::* as well.

Thanks for the great report! Can you try if it works when using --all-targets?
Relatedly, https://github.com/rust-lang/cargo/issues/5739 :)

Hmm, it doesn't seem to be available:
$ cargo fix --all-targets --prepare-for 2018
error: Found argument '--all-targets' which wasn't expected, or isn't valid in this context

USAGE:
    cargo fix [FLAGS] [OPTIONS] [args]...

For more information try --help
$ cargo fix --prepare-for 2018 --all-targets
error: Found argument '--all-targets' which wasn't expected, or isn't valid in this context

USAGE:
    cargo fix --prepare-for <edition>

For more information try --help

@jrvidal oh for now temporarily you'll need to do cargo fix --prepare-for 2018 -- --all-targets (note the extra --)

That does the trick. Please feel free to close this, or to leave it open until --all-targets is added by default (or whatever ends up being implemented).

Cool! We already have rust-lang/cargo#5739 to track making it the default so I'll close this one.
Thanks for reporting this!


ci: Update trivy.yml

Description
Fix trivy.
Why
Action Failures: Actions should only fail if there is an error with the Action "Engine" itself or if there is a misconfiguration in the workflow. Failures should not occur based solely on high-severity findings.
Issue
Link to Github issue.
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally

@scherersebastian thanks for the fix!
I just find it useful that the config is checked by kics and trivy, so I quickly created a separate PR https://github.com/eclipse-tractusx/portal-frontend/pull/359
For the other portal repos, I'll do the same.


Function calculateDistance accepts non-numeric values

I have noticed that the calculateDistance function in the codebase is not handling non-numeric input values properly. When non-numeric values are passed for latitude and longitude, the function proceeds without validating them, which may lead to unexpected behavior.
Steps to Reproduce:

Use the calculateDistance function with non-numeric values for latitude and/or longitude.
Observe that the function does not throw an exception for non-numeric values.

Expected Behavior:
The function should validate input values and throw an exception if any of them is not a number.
Actual Behavior:
The function does not validate input values, allowing non-numeric values to be processed without any warning.

Thank you for bringing this to our attention. The issue has been addressed, and the calculateDistance function now properly validates input values for latitude and longitude. If non-numeric values are provided, the function will throw an exception, ensuring better handling of invalid input. Feel free to test it again, and let us know if you encounter any further issues. Your feedback is valuable to us!


Integrate sqllogictest

What feature are you requesting?
Integrate SQLLogicTest to streamline FDW testing:

Provides a simple, declarative syntax for SQL test cases
Supports complex query verification
Enables easy test case addition and maintenance

Why are you requesting this feature?
While working on #132, I encountered difficulties writing tests related to Foreign Data Wrappers (FDW). The current test suite contains significant code duplication for table initialization, making it cumbersome to add new tests.
This feature could benefit pg_search and pg_analytics.
What is your proposed implementation for this feature?
No response
Full Name:
Weijun Huang
Affiliation:
Individual

If this ticket sounds good to you, I could try to work on it.

If this ticket sounds good to you, I could try to work on it.

That feature sounds very useful yes. If we can improve the way we write tests it would be great.
Where do you see it be most useful for pg_search?

If this ticket sounds good to you, I could try to work on it.

That feature sounds very useful yes. If we can improve the way we write tests it would be great.
Where do you see it be most useful for pg_search?

Because this feature could change the existing most of tests to .slt not only pg_analytics but also pg_search.  It makes tests more maintainable and serves as clear documentation. For pg_search, this approach would standardize the testing approach, potentially improve test execution speed, and make it easier to add comprehensive test cases in the long term.

/take

/take

@Weijun-H. I just reviewed #152. I am unclear on whether we want this. I would suggest you make a very small sqllogictest for pg_search and PR it in that repo. The rest of the team can weigh in. Based on what they say, we can decide whether to do it here/there.

@Weijun-H. We moved all our tests in a separate crate in paradedb/paradedb. I guess we could do the same here. Imitating the same approach would be optimal

@Weijun-H. We moved all our tests in a separate crate in paradedb/paradedb. I guess we could do the same here. Imitating the same approach would be optimal

I think that deserves a separate ticket

At this time, we've decided this is not a priority.


Uploading payloads greater than 1.5kb causes timeouts

Something between the client and server causes payloads that are greater than 1.5kb to timeout

Problem is solved with proxy rules
gop package --key-file=private-key.pem
2696434
<Response [200]>
b''


Add PR template

Are PRs to this repo intended to replace mailing list / discourse threads?

@merwok Not sure I understand what you mean, we don't usually create mailing list / discourse threads for new classifiers. They live at https://github.com/pypa/pypi-support/issues?q=is%3Aopen+is%3Aissue+label%3A"classifier+request" currently.

Ha I had a totally wrong recollection of the current process!


Support cpuid-based selection of top-level functions

Optimizing the whole zlib-ng library for a more capable processor provides a noticeable speed increase. I tried various different flags, and managed to figure out that the primary benefit comes from allowing -mbmi2:
zlib-ng 6264b5a58d7470333a64d69b247a2bd561bbbe68:
fast: Compressed<PHONE_NUMBER> bytes to<PHONE_NUMBER> bytes in 17.402995566s
default: Compressed<PHONE_NUMBER> bytes to<PHONE_NUMBER> bytes in 57.6245043s
decompression: Decompressed<PHONE_NUMBER> bytes to<PHONE_NUMBER> bytes in 9.386560726s

zlib-ng 6264b5a58d7470333a64d69b247a2bd561bbbe68 with -mbmi2:
fast: Compressed<PHONE_NUMBER> bytes to<PHONE_NUMBER> bytes in 16.677151077s
default: Compressed<PHONE_NUMBER> bytes to<PHONE_NUMBER> bytes in 56.543926808s
decompression: Decompressed<PHONE_NUMBER> bytes to<PHONE_NUMBER> bytes in 8.847878558s

I think it'd be beneficial to compile multiple copies of some functions, such as inflate.c and inflate_fast.c, with different compiler options and a prefix on functions, and then use the cached CPUID result to determine which function to call. (Macros similar to PREFIX would work for this, applied to non-static functions and to calls to non-static functions.)
Based on extensive experimentation with compiler options, I'd suggest adding a copy compiled with -mbmi2 (called when the corresponding CPUID feature exists); that's the only option that appears to give a substantial improvement.

The problem with supporting instruction sets like BMI2 is that compression/decompression programs heavily depend on bit manipulation, so basically the time-critical functions are the ones that would benefit the most from use of the instructions. This means making the code optional would most likely counter most of the speed gain from the speedup of bit manipulation instructions.

@mtl1979 That's why I'm suggesting compiling the top-level functions for it, and switching at that level, rather than trying to optimize a specific internal function with it.

@joshtriplett That would increase the library size by factor of 6 or more...

@mtl1979 I don't think it would require 6 different variations, only variations that actually make a difference in practice. I tested every single CPU feature available on my Kaby Lake laptop, and the only one that made a difference like this was bmi2.
(Also, if someone is looking to optimize for code size rather than performance, they could always disable this.)

@joshtriplett Basically for 64-bit Intel you would need version with just SSE2, version with SSE3, version with SSSE3, SSE4, SSE4.2, AVX2. For AMD processors it would get even more complicated.

I wonder which functions would make the most difference..

@nmoinvaz I would assume macros/code that do both shifting and masking...

I'm not suggesting changing the approach that zlib-ng currently uses for other instruction sets. I'm just suggesting this approach for bmi2, because its usage is so intertwined into other functions.

@joshtriplett I'm saying it doesn't make sense to make exception for one small instruction set, when it can already get enabled when larger instruction set is also enabled.


improvements to make documentation work

the file 'intl.dart' was exported; and I changed FormBuilder Stepper by FormBuilderTouchSpin so that the example works

Thanks for your contribution @zkmark.


revert to before classics

THIS IS ONLY A TEST PULL REQUEST, DONT APPROVE
for checking what changed in development for classics


FPS UNLOCKER

when i download and open the bloxstrap, it doesn't show the fps unlocker for some reason ?? it only shows the discord rich presence, reshade, miscellaneous, and custom integrations ( i have the x64 downloaded )

Please use the left sidebar.

Please use the left sidebar. Also note that you must be 13 or older to use an GitHub account.

what left sidebar and i am older than 13?

We're not using rbxfpsunlocker anymore. Check your FPS in-game with Shift + F5 and see if it's being unlocked.

We're not using rbxfpsunlocker anymore. It's delegated to a FastFlag in the Mods tab now. Check your FPS in-game with Shift + F5 and see if it's being unlocked.

ty


tap-gitlab Extractor Settings step iteration

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/710
Originally created by @dmor on 2019-06-13 16:37:24

Right now, when setting up the extractor settings for tap-GitLab the user is presented with this screen:

It is a little difficult to know what to do here to successfully complete the step:

Is it okay for me to leave these fields just as they are, or do I need to edit them?

At the very least, it felt like I needed to add my API token... but I've never used it before and I'm not sure where to get it.

[x]  @derek-knox could we add a tooltip to each of these fields, telling the user what they need to do / where they need to go to get the required info? (@dmor https://gitlab.com/meltano/meltano/issues/739 should be our go-to for this)
[x]  @derek-knox for "API start date" can we provide an example of the right date format, or offer a date selector instead?
[x]  @derek-knox should it allow me to successfully "Save" when I haven't filled in the fields?

After I "Save" without editing other fields I get a bug flag in the bottom right (see screenshot below) but not any info on what it means:

Tasks

[x] <ConnectorSettings> component
[x] consumes extractor and loader settings
[x] form validation
[x] accounts for string, password, email, boolean, and date_iso8601
[ ] accounts for required, non-required, non-editable controls/inputs
[ ] groups controls intelligently (username + password, etc.)

View 14 previous comments from the original issue on GitLab


Ability to invalidate a custom identifier on goto()

Describe the problem
I know there is an issue discussing this here but this seems a wider issue.
To extend on the discussion here it could be very useful to invalidate an identifier on goto(). A common use case is as follow:
in a simple CRUD with the following pages :
/list
/list/[id]

Say you have a delete button on the [id] page that calls a DELETE action at the same level, if you plan to invalidate then goto(parent_page) the [id] load function will get in-between a not found error (obviously).
goto(invalidateAll) won't really work if you have unrelated parametrized load functions in previous segments of the URL (ie if you're using depends anywhere).
You can solve this by redirecting to the parent page on error in the load function but this doesn't feel right (one extra -and failed- request per deletion).
Describe the proposed solution
goto( { invalidate: ['myidentifier'] } )
Alternatives considered
I could redirect to some dummy invalidation page or add a query parameter that would trigger an invalidation in the list page but it feels complicated.
Importance
would make my life easier
Additional Information
No response

I'm new to SvelteKit and had the same issue with CRUD delete. I currently workaround it with:
await goto(parentLocation)
invalidateAll() // presumably will work also for specific invalidations

This seems to correctly cause the invalidation after the goto, so it doesn't hit the 404 between the delete and goto parent. The parent then doesn't need to have a default redirect to parent on not found (I'd prefer we get proper 404 when an ID doesn't exist).
Not sure if this is idiomatic and feels potentially brittle? But working. If relevant, it's currently executing in an onResult callback in superforms, I'm unsure exactly how that might affect the page lifecycle so YMMV.
Also wasn't exactly sure what you meant by:

goto(invalidateAll) won't really work if you have unrelated parametrized load functions in previous segments of the URL (ie if you're using depends anywhere).
So apologies if that makes this workaround not applicable.

Also wasn't exactly sure what you meant by

goto already have an invalidateAll arg as seen on the docs so doing goto(url, { invalidateAll: true })) will entirely solve your problem.
This issue is about having the same kind of option when using depends where invalidateAll does too much.

Right, I realised that, but I'm wondering if this approach works for you for specific invalidations. That is, await the goto (or use .then) and perform invalidate after goto has resolved?

Right, I realised that, but I'm wondering if this approach works for you for specific invalidations. That is, await the goto (or use .then) and perform invalidate after goto has resolved?

In my experience this can (randomly) trigger weird behaviors on non-basic apps through race conditions. But if I recall correctly this technique was officially documented in Sapper (SvelteKit ancester). I don't have much knowledge of SK internals so I prefer to avoid that right now.

Running into the same issue where { invalidateAll: true } would do too much and waste backend resources.
Would love something like what @gterras proposed.

goto( { invalidate: ['myidentifier'] } )


Initializing ace editor content using $http service

I'm rendering content of the editor using $http service. But  onLoad function is being called much before data is rendered in editor.
When I'm adding code inside $timeout service then it is working properly. Is there any way to achieve this without using $timeout service.
funciton onLoad(editor) {
   /*
     It will set the some of  the lines readyonly. But because onLoad is executing much
     before data is rendered from $http service, it does not find any lines.
   */
   set_readonly_lines(editor);
}

funciton onLoad(editor) {
   /*
     Using timeout it is working properly
   */
   $timeout(function() {
      set_readonly_lines(editor);
   }, 1);
}

Store the editor from onLoad in $scope.
$scope.aceLoaded = function($editor) {

    $scope.$editor = $editor;
};

$scope.onOpen = function(code, fileExtension) {
    let mode = resolveExtension(fileExtension);
    $scope.html = code;
    $scope.$editor.session.setMode('ace/mode/' + mode);
}

Excuse me for my poor inferring, but I'm not able to get you

Sorry I fogot add the service
$scope.openFile = function(file) {
    //Here I prefer use factory.
    //fileFactory.openFile(file).then(fn,fn);
    $http.post('/api', file).then(function (res) {
        $scope.onOpen( res.data.content, res.data.extension)
    },angular.noop);
}


App Settings context menu inconsistent with Functions

Figured while we're working on app settings stuff, might as well make the two consistent.
Functions:

App Service:

Should remove "Open in Portal" from the App Service context menu?


DWD weather data missing

Home Assistant 2023.10.5
Supervisor 2023.10.0
Operating System 11.0
Frontend 20231005.0 - latest
Version of the custom_component  2023.8.2
Describe the bug
No data available
My Station
01475
Debug log
2023-10-24 00:12:13.670 ERROR (MainThread) [frontend.js.latest.202310050] Uncaught error from WebKit 605.1.15 on Mac OS 10.15.7
Error: Weather entity "weather.dwd_weather_mittelnkirchen_hohen" does not support daily forecasts.
subscribeForecastEvents (/hacsfiles/clock-weather-card/clock-weather-card.js:242:6674)
connectedCallback (/hacsfiles/clock-weather-card/clock-weather-card.js:196:122)
this (src/scoped-custom-element-registry.js:248:47)
appendChild ([native code]::)
_createPanel (src/layouts/hass-router-page.ts:318:21)
loadProm.then( (src/layouts/hass-router-page.ts:215:10)
2023-10-24 00:12:14.089 ERROR (MainThread) [frontend.js.latest.202310050] Uncaught error from WebKit 605.1.15 on Mac OS 10.15.7
Error: Weather entity "weather.dwd_weather_mittelnkirchen_hohen" does not support daily forecasts.
subscribeForecastEvents (/hacsfiles/clock-weather-card/clock-weather-card.js:242:6674)
connectedCallback (/hacsfiles/clock-weather-card/clock-weather-card.js:196:122)
this (src/scoped-custom-element-registry.js:248:47)
appendChild ([native code]::)
document.createElement (src/panels/lovelace/hui-root.ts:943:21)
2023-10-24 00:12:36.174 DEBUG (MainThread) [custom_components.dwd_weather] Finished fetching DWD Weather Coordinator for 01475 data in 0.001 seconds (success: True)
2023-10-24 00:13:36.174 DEBUG (MainThread) [custom_components.dwd_weather] Finished fetching DWD Weather Coordinator for 01475 data in 0.001 seconds (success: True)
2023-10-24 00:14:36.174 DEBUG (MainThread) [custom_components.dwd_weather] Finished fetching DWD Weather Coordinator for 01475 data in 0.001 seconds (success: True)

{{ state_attr('weather.bad_bentheim','temperature') | default('0') }} -> works
{{ state_attr('weather.bad_bentheim','forecast')[0].condition | default('0')  }} -> doesn't work
forecast is broken since last updates...
hope it's easy to fix ;-)
thx
M.

OK, give me a hint for testing.
thx L

here is a work around...
was not easy to find out ...
but this is a safe way also for future... since HA updated the api...
Automation:
`alias: Wetter Aktualisierung
description: Aktualisiert die Wetterdaten
trigger:

platform: time_pattern
hours: "/1"
platform: homeassistant
event: start
platform: event
event_type: event_template_reloaded
condition: []
action:
service: weather.get_forecast
data:
type: daily
target:
entity_id: weather.bad_bentheim
response_variable: weather_data
service: system_log.write
data:
message: "Debug: weather_data: {{ weather_data }}"
level: warning
alias: Set Weather Data
repeat:
count: "{{ [weather_data['forecast']|length, 8]|min }}"
sequence:
- service: input_text.set_value
target:
entity_id: "input_text.dwd_weather_forecast_temp_day{{ repeat.index }}max"
data:
value: "{{ weather_data['forecast'][repeat.index]['temperature'] }}"
- service: input_text.set_value
target:
entity_id: "input_text.dwd_weather_forecast_temp_day{{ repeat.index }}min"
data:
value: "{{ weather_data['forecast'][repeat.index]['templow'] }}"
- service: input_text.set_value
target:
entity_id: "input_text.dwd_weather_condition{{ repeat.index }}d"
data:
value: "{{ weather_data['forecast'][repeat.index]['condition'] }}"
- service: input_text.set_value
target:
entity_id: "input_text.dwd_weather_precipitation_probability{{ repeat.index }}d"
data:
value: "{{ weather_data['forecast'][repeat.index]['precipitation_probability'] }}"
- service: input_text.set_value
target:
entity_id: "input_text.dwd_weather_precipitation_{{ repeat.index }}d"
data:
value: "{{ weather_data['forecast'][repeat.index]['precipitation'] }}"
- service: input_text.set_value
target:
entity_id: "input_text.dwd_weather_wind_bearing_{{ repeat.index }}d"
data:
value: "{{ weather_data['forecast'][repeat.index]['wind_bearing'] }}"
- service: input_text.set_value
target:
entity_id: "input_text.dwd_weather_wind_gusts_{{ repeat.index }}d"
data:
value: "{{ weather_data['forecast'][repeat.index]['wind_gusts'] }}"
- service: input_text.set_value
target:
entity_id: "input_text.dwd_weather_wind_speed_{{ repeat.index }}d"
data:
value: "{{ weather_data['forecast'][repeat.index]['wind_speed'] }}"
mode: single
`

and in config you need to add:
input_text: dwd_weather_condition_0d:     name: DWD Forecast Day 0 dwd_weather_precipitation_probability_0d:     name: DWD Precipitation Probability Day 0 dwd_weather_precipitation_0d:     name: DWD Precipitation Day 0 dwd_weather_wind_bearing_0d:     name: DWD Wind Bearing Day 0 dwd_weather_wind_gusts_0d:     name: DWD Wind Gusts Day 0 dwd_weather_wind_speed_0d:     name: DWD Wind Speed Day 0 dwd_weather_forecast_temp_day0_max:     name: DWD Forecast Temp Day 0 Max dwd_weather_forecast_temp_day0_min:     name: DWD Forecast Temp Day 0 Min ->you need to add day 0-8 for each...
and if you need a Sensor for Platinum Weather Card or other:
`template:

sensor:

name: "DWD Bad Bentheim Vorhersage Heute Max"
unique_id: dwd_bad_bentheim_forecast_today_max
unit_of_measurement: "°C"
state: "{{ states('input_text.dwd_weather_forecast_temp_day0_max') }}"

sensor:

name: "DWD Bad Bentheim Vorhersage Heute Min"
unique_id: dwd_bad_bentheim_forecast_today_min
unit_of_measurement: "°C"
state: "{{ states('input_text.dwd_weather_forecast_temp_day0_min') }}"`

it's some work... but safe and future proof... you only need to change entity_id: weather.bad_bentheim to another like the build in for testing... all weather station that work with same format and are supported by - service: weather.get_forecast should work... ;-)

OK, create automation and change to YAML editor. copy and paste and try to set right spaces on left side.
On save I get the error as shown in the screenshot.

whats wrong

I just confirmed your station 'mittelnkirchen' produces a daily forecast. So this more likely an error in the clock-weather-card.

I just delete  (cleared files) and reinstall (there were new versions yesterday) and adapt my dashboard
Now ist works!
Thanks for support

the end


Cisco  WS-C3850-24T CPU 使用率采集异常

下面是我设备的show version信息：
Cisco IOS XE Software, Version 16.06.06
Cisco IOS Software [Everest], Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9-M), Version 16.6.6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2019 by Cisco Systems, Inc.
Compiled Thu 11-Apr-19 02:24 by mcpre
Cisco IOS-XE software, Copyright (c) 2005-2019 by cisco Systems, Inc.
All rights reserved.  Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0.  The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY.  You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0.  For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: IOS-XE ROMMON
BOOTLDR: CAT3K_CAA Boot Loader (CAT3K_CAA-HBOOT-M) Version 3.58, RELEASE SOFTWARE (P)
BJB2-HJSW-10.100 uptime is 8 weeks, 20 hours, 48 minutes
Uptime for this control processor is 8 weeks, 20 hours, 53 minutes
System returned to ROM by Power Failure or Unknown
System image file is "flash:cat3k_caa-universalk<IP_ADDRESS>.SPA.bin"
Last reload reason: Power Failure or Unknown
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
<EMAIL_ADDRESS>Technology Package License Information:

Technology-package                   Technology-package
Current             Type             Next reboot
ipservicesk9        Permanent        ipservicesk9
cisco WS-C3850-24T (MIPS) processor (revision AC0) with 852917K/6147K bytes of memory.
Processor board ID FCW2305F0SJ
9 Virtual Ethernet interfaces
56 Gigabit Ethernet interfaces
8 Ten Gigabit Ethernet interfaces
2048K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
250456K bytes of Crash Files at crashinfo:.
257008K bytes of Crash Files at crashinfo-2:.
1609272K bytes of Flash at flash:.
1590435K bytes of Flash at flash-2:.
0K bytes of WebUI ODM Files at webui:.
Base Ethernet MAC Address          : d0:ec:35:ab:6d:00
Motherboard Assembly Number        : 73-16297-05
Motherboard Serial Number          : FOC230468VD
Model Revision Number              : AC0
Motherboard Revision Number        : B0
Model Number                       : WS-C3850-24T
System Serial Number               : FCW2305F0SJ
Switch Ports Model              SW Version        SW Image              Mode

1 32    WS-C3850-24T       16.6.6            CAT3K_CAA-UNIVERSALK9 BUNDLE
2 32    WS-C3850-24T       16.6.6            CAT3K_CAA-UNIVERSALK9 BUNDLE

Switch 02
Switch uptime                      : 8 weeks, 20 hours, 53 minutes
Base Ethernet MAC Address          : 00:d6:fe:71:3a:00
Motherboard Assembly Number        : 73-16297-05
Motherboard Serial Number          : FOC22312NKK
Model Revision Number              : AC0
Motherboard Revision Number        : B0
Model Number                       : WS-C3850-24T
System Serial Number               : FCW2231D1FA
Configuration register is 0x102

可能是 oid 不匹配
手头的只有 WS-C3850-24XS，Version 03.07.04.E RELEASE SOFTWARE (fc1)
cpu 采集正常。
谁能贡献下 issue 对应型号的 cpu oid ，snmpwalk 测试一下~


da.linalg.norm errors for ndims>2 & axis=something

Using numpy.linalg.norm, if I have a nD array of vectors X, I can calculate the nD array of norms of these vectors using the axis kwarg in the following way:
import numpy as np

X = np.random.random(5,5,2)
Xnorms = np.linalg.norm(X, axis=-1)

One would expect this to work with da.linalg.norm as well, but this throws an error:
import dask.array as da

X = da.random.random(5,5,2, chunks=(1,1,2))
Xnorms = da.linalg.norm(X, axis=-1)

However:
  File "C:\ProgramData\Anaconda3\lib\site-packages\dask\array\linalg.py", line 1085, in norm
    #    raise ValueError("Improper number of dimensions to norm.")
ValueError: Improper number of dimensions to norm.

I disagree with this error message for this case. In fact, when removing the raising of this error, everything computes fine.
I think the solution is editing the requirements in the following lines:
https://github.com/dask/dask/blob/6a9fc9a342d62c102d8cfc9607ebab2c25f45781/dask/array/linalg.py#L1082-L1092
Where we should check x.ndims <= 2 only if axis=None and for completeness if axis is a tuple check if it is not more than a 2-tuple (see also the relevant numpy docs ).
Or are there any hurdles I am not aware of? Otherwise I will just implement this.

My first guess is that that code was copied verbatim from Numpy at a time
when Numpy didn't support norm of greater than 2.  I'm not sure though.  I
suspect that @jakirkham would know more.
On Tue, Aug 21, 2018 at 12:55 PM, Tobias de Jong<EMAIL_ADDRESS>wrote:

Using numpy.linalg.norm, if I have a nD array of vectors X, I can
calculate the nD array of norms of these vectors using the axis kwarg in
the following way:
import numpy as np
X = np.random.random(5,5,2)
Xnorms = np.linalg.norm(X, axis=-1)
One would expect this to work with da.linalg.norm as well, but this
throws an error:
import dask.array as da
X = da.random.random(5,5,2, chunks=(1,1,2))
Xnorms = da.linalg.norm(X, axis=-1)
However:
File "C:\ProgramData\Anaconda3\lib\site-packages\dask\array\linalg.py", line 1085, in norm
#    raise ValueError("Improper number of dimensions to norm.")
ValueError: Improper number of dimensions to norm.
I disagree with this error message for this case. In fact, when removing
the raising of this error, everything computes fine.
I think the solution is editing the requirements in the following lines:
https://github.com/dask/dask/blob/6a9fc9a342d62c102d8cfc9607ebab
2c25f45781/dask/array/linalg.py#L1082-L1092
Where we should check x.ndims <= 2 only if axis=None and for completeness
if axis is a tuple check if it is not more than a 2-tuple (see also the
relevant numpy docs
https://docs.scipy.org/doc/numpy/reference/generated/numpy.linalg.norm.html
).
Or are there any hurdles I am not aware of? Otherwise I will just
implement this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/3895, or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszIUcCKayTPKVLjmlyRnWuDUnf85Fks5uTDuLgaJpZM4WGKzV
.

The axis argument was introduced in version 1.8.0. of numpy, from 2013 or so, so that would be a bit surprising. Equivalent code is (here)[https://github.com/numpy/numpy/blob/18f2385b29bdd62701a1a82d7bf33fd87430a05e/numpy/linalg/linalg.py#L2357-L2382] btw.

In that case I suggest that we wait to see if @jakirkham has thoughts.  I
suspect that he has a good answer here.
On Tue, Aug 21, 2018 at 1:17 PM, Tobias de Jong<EMAIL_ADDRESS>wrote:

The axis argument was introduced in version 1.8.0. of numpy, from 2013 or
so, so that would be a bit surprising. Equivalent code is (here)[
https://github.com/numpy/numpy/blob/18f2385b29bdd62701a1a82d7bf33f
d87430a05e/numpy/linalg/linalg.py#L2357-L2382] btw.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/3895#issuecomment-414752346, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszKqBsfik2f4xDwFRed7D0yglmPB9ks5uTECTgaJpZM4WGKzV
.

Hmm...it's pretty hard to remember why I wrote some code a particular way a year ago. Sorry to not be more insightful.
My guess is that I didn't have a good use case to drive adding such functionality or test it. So left it out figuring if it was important someone (like yourself) would show up looking for it and we could discuss such improvements.
Expect that if we generalize the function to N-D a few checks within the function will need to be updated as they seem to assume the array is either 1-D or 2-D, but don't consider catching cases that are higher dimensionality. Would expect this is straightforward to do, but there is a bit of bookkeeping. Testing some N-D arrays with all norms should help flush these issues out.

To be precise and avoid confusion @jakirkham: I am not talking about extending the norm to more than 2D ( I am not even sure if this is a thing mathematically), but to be able to use the axis argument to take the norm of 1D or 2D slices of an nD array, as is implemented by numpy.

Right, that's what I meant as well. Sorry to be imprecise.

I am working on a pull request for this. Most of it is straight forward, except for the SVD-based norms on slices of ND arrays. I see that np.linalg itself only supports operating on the last two dimensions of ND-arrays for the svd here: https://docs.scipy.org/doc/numpy/reference/routines.linalg.html#linear-algebra-on-several-matrices-at-once, although np.linalg.norm handles this somehow.
This means we can either create some application of map_blocks/apply_along_axes on the existing da.linalg.svr (or the underlying da.linalg.tsqr) in this case for norm, or extend one of these to operate on the last 2 dimensions of an N-D array, or to take an axis argument, respectively replicating or superseding the stacked linalg computation functionality of numpy.
I guess matching numpy functionality and operate on the last two dimensions would be the best, as introducing a full axis argument for svd/tsqr would just hide away an underlying transpose.
Any thoughts on this?
P.S. Working on both thus and some applications I notice there is only an da.apply_along_axis, and no da.apply_along_axes for mapping operations on general subdimensions, requiring instead to write some wrapper function to put in a map_blocks in order to handle extra non-one dimensions of blocks. Maybe this would be a nice extension/generalization of the API, or am I missing a function for this?

Closing this as it is resolved for most cases, the left over NotImplementedError cases for SVD-based norms are discussed in the new issue #3962 .


Can't install localy

Hello,
Im trying to install the model locally by following the installation steps, but im stuck at the first step
pip install git+https://github.com/huggingface/parler-tts.git
here is the error:
Downloading tests/audio/ir/h179_Bar_1txts.wav (50 KB)
  Error downloading object: tests/audio/ir/h179_Bar_1txts.wav (206aee1): Smudge error: Error downloading tests/audio/ir/h179_Bar_1txts.wav (206aee1e87c966ead8a5755b2b90470eaa7c19d55ddbbbeca263ce203c8cab3a): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

My local env :

Mac Pro M1
Python 3.13 (same with 3.9)
virtual env : venv

Reproduction steps :

create a venv
run pip install git+https://github.com/huggingface/parler-tts.git

Thank you

same here


Add ComponentDialog, DialogSet, WaterfallDialog and WaterfallStepContext tests

And fix a WaterfallDialog.runStep() bug

Pull Request Test Coverage Report for Build 1721

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+1.04%) to 71.496%

Files with Coverage Reduction
New Missed Lines
%

libraries/botframework-config/src/botConfigurationBase.ts
2
85.59%

Totals

Change from base Build 1702:
1.04%

Covered Lines:
2242

Relevant Lines:
3004

💛  - Coveralls


/ - Keyboard shortcut to focus on current chat prompt input

This fixes #511
Summary of Changes
This adds a / shortcut that sets focus on the current Chat prompt entry.
This adds two methods to the ChatBase component:
handleChatInputFocus() - sets focus on Chat prompt entry
handleForwardSlash - useEffect that listens for '/' key entry when user is not focused on a text input box
I initially tried to do this by extending useKeyDownHandler with a method to handle forward slashes and adding a useKeyDownHandler instance to the ChatBase component, but the listener would only trigger when inside a text area (like the search bar or chat prompt entry).
If there's a better way to implement this please let me know.

@chadparker do you want to test this fix out for us?  You can use the preview URL at https://8a118347.console-overthinker-dev.pages.dev/

I tried it out and the functionality seems great, thank you!
(I don't know React, but the code seems sensible. I'll let somebody closer to the project officially review it, though.)


Update testnet release notes for 0.76.1

Merges pre-release 0.76.0.preview-1 and -preview-3 in to a full 0.76.1 set of release notes

Closing in favour of pushing these release notes in to #1049 and getting both updated at the same time


[Warmfix] Issue:146 remove direct donation

Problem
Previous binary was rejected by Apple as LF is not a charity (though is a Non-Profit).  They asked us to change the Donation working and functionality
Issue
#146
Approach
The Support Litecoin Foundation button fires a sheet with and embedded webpage that the user can use to send grants to Litecoin Foundation
Steps

Removed Donation code
Added more SwiftUI Code
Added some Test Stubs
Check the LTC address matches

Screenshot/GIF

Resulting Action in Send

There are issues with the rebase...closing

There are issues with the rebase...closing

OK but take my review into account


Customer questions on reference semantics with value types

From a live fyre comment on this topic

This sounds cool but I'm confused about a bunch of things.

Suppose a method takes a readonly struct as an argument. Should that also be an "in" parameter? That seems redundant and unnecessary.
Does this change the recommendations on when to define something as a Struct versus a Class? The recommendations on Struct say it should be a small thing to avoid a lot of copying, but if you define it as readonly then won't it always get passed by reference in which case the size doesn't matter?
If my general practice is to define structs as ReadOnly, then can't the compiler be smart about ALWAYS passing by reference without having to use "in" or "ref readonly".
Overall I'm using a lot of "readonly struct" since I like immutability. Do I really need to do anything else to make things efficient?

/cc @VSadov @jaredpar @jcouv @stephentoub

Here are my thoughts:

Suppose a method takes a readonly struct as an argument. Should that also be an "in" parameter? That seems redundant and unnecessary.

Without any modifiers on the method declaration, all arguments are passed by value. You need in, to specify pass-by-reference.

Does this change the recommendations on when to define something as a Struct versus a Class? The recommendations on Struct say it should be a small thing to avoid a lot of copying, but if you define it as readonly then won't it always get passed by reference in which case the size doesn't matter?

I would think that it should. I'd like clarification from the product folks before updating any docs to include this.

If my general practice is to define structs as ReadOnly, then can't the compiler be smart about ALWAYS passing by reference without having to use "in" or "ref readonly".

That is an interesting idea, but I don't think that's what happens now. Open question: should this be a feature request for a future version?

Overall I'm using a lot of "readonly struct" since I like immutability. Do I really need to do anything else to make things efficient?

All arguments and return values in C# are by value. Furthermore, I don't think it is a universal truth that pass by reference is faster than pass by value. You should always measure performance for that kind of work.  I would experiment and measure. The fact that the in modifier is only needed at the method declaration should make that reasonably easy to do.

Suppose a method takes a readonly struct as an argument. Should that also be an "in" parameter? That seems redundant and unnecessary.

Without any modifiers on the method declaration, all arguments are passed by value. You need in, to specify pass-by-reference.

Couple other reasons why this isn't done by default:

Making a struct readonly is designed to be a completely safe, non-breaking change. If it also changed argument passing from value to ref then that would be breaking source + binary change.
Moving from value to in is not a slam dunk win. It's generally better for readonly structs but it can have negative side effects in uncommon cases. Hence a decision that needs to be made explicitly.

Does this change the recommendations on when to define something as a Struct versus a Class? The recommendations on Struct say it should be a small thing to avoid a lot of copying, but if you define it as readonly then won't it always get passed by reference in which case the size doesn't matter?

I'd like input from @terrajobst here as well.
For me the answer is no. This is about adding an extra layer of correctness to an existing decision + allowing the compiler to avoid a lot of unneeded copies. It wouldn't influence my struct / class decision but rather help me enforce behaviors I already want on my struct.

To me the easiest reason to choose between class and struct is a matter of instance identity.
If you have something called “Customer” and it has “Name” or “Id”, it better be a class, especually if the entity is mutable. Struct would be incinvenient due to byval copying - you can easily end up with two customers named “Bob”, one copy of another but with different orders or something.
If you have some measure-like thing like “Complex” or “Color” where all instances are the same as long as they have the same content, then instance identity that cimes with class is useless - having two distinct instances of “Red” with exactly same values is confusing.
Of course there are some “gray area” cases and immutable/sungleton patterns complicate the choice.
It is still most often a question whether having distinct instances of the type is a desirable thing or not.

I have another question on the topic, which I'll rephrase from what I've already asked at the docs page.
Consider the following struct:
    readonly struct MyStruct
    {
        private readonly int value;

        public MyStruct(int value)
        {
            this.value = value;
        }

        public override string ToString()
        {
            // Defensive copy!
            return value.ToString();
        }
    }

Here I use primitive type for a filed, but still get defensive copies when calling methods on that primitive type. That obviously happens because Int32 structure is not marked as readonly. Thus, readonly structs have a limitation which may not be apparent at the first look: to avoid defensive copies fields must be readonly structs OR, in case of primitive value types, you must use only primitive type operations (which end up with corresponding IL instructions and not method calls).
Having that, my question is: why aren't primitive value type structs (such as Int32) marked as readonly? In case of Int32, even its m_value filed is not readonly though  its not modified in the code.

bump and +1 to the notion/ask of optimizing the use of in for readonly structs.  Seems like there should be a way to check this and add it automatically.  Yeah I hear that it's complicated to do, but WE'RE DEVELOPERS MAN THIS IS WHAT WE DO!! 😄
Especially when you consider how oft-used ValueTuple is (or will be used), it seems like this should be a problem to solve to transparently add better performance across the board for those who wish to opt into it.
Of course, showing how much of a newb I am to this topic, I just now looked it up and ValueTuple is using writable fields for its "properties."  My impression was that it was/is immutable, boh.  It would seem that with the rise/popularity of immutability, along with the new staple of value-based tuples, there would be a further addition here to help enlist into the performance magic.
So yes, I think that's a feature request? 😆

Whoever is interested in in modifier and readonly structs might find this blog post from Sergey Teplyakov interesting as well.
Quote conclusions from there:

The readonly structs are very useful from the design and the performance points of view.
If the size of a readonly struct is bigger than IntPtr.Size you should pass it as an in-parameter for performance reasons.
You may consider using the in-parameters for reference types to express your intent more clearly.
You should never use a non-readonly struct as the in parameters because it may negatively affect performance and could lead to an obscure behavior if the struct is mutable.

Overall I think that's a pretty reasonable set of recommendations.

I still have my question unanswered:

why aren't primitive value type structs (such as Int32) marked as readonly? In case of Int32, even its m_value field is not readonly though its not modified in the code.

Please, can somebody comment on this?

@andriysavin Thanks for pointing this out.
I'll make another PR to address that.  In the meantime, here's the text I need to add:

While the unmanaged types are  not explicitly marked as a readonly struct the compiler treats them as such and are considered readonly from the perspective of the language. The compiler knows  them to be immutable which is even a stronger guarantee than readonly can provide.

@BillWagner I'm not sure we're talking about the same thing. I mean primitive types like Int32.

We are talking about the same concept. (I need to make an issue to clearly surface the term "unmanaged type" better).  The term is defined in the Pointer types section of the C# language spec.  The pertinent paragraph is this:

An unmanaged_type is any type that isn't a reference_type or constructed type, and doesn't contain reference_type or constructed type fields at any level of nesting. In other words, an unmanaged_type is one of the following:

sbyte, byte, short, ushort, int, uint, long, ulong, char, float, double, decimal, or bool.
Any enum_type.
Any pointer_type.
Any user-defined struct_type that is not a constructed type and contains fields of unmanaged_types only.

why aren't primitive value type structs (such as Int32) marked as readonly? In case of Int32, even its m_value field is not readonly though its not modified in the code.

They are in current .NET Core builds: https://github.com/dotnet/coreclr/blob/master/src/System.Private.CoreLib/shared/System/Int32.cs

Ping @jaredpar @agocke
See the above two comments. How do we want to resolve this for the docs and the spec?

@mikedn Yes, saw that too, and that's strange this wasn't done at the same time as readonly feature was introduced.
@BillWagner thanks for explaining. Why I was concerned with this in the first place is because I was observing defensive copies with primitive types at IL level when calling something like Int32.ToString(). Maybe compiler (JIT Compiler?) removes those defensive copies because, as you said, it handles them specially, but this doesn't look obvious.

Why I was concerned with this in the first place is because I was observing defensive copies with primitive types at IL level when calling something like Int32.ToString().

AFAIK that's the reason why there made readonly in the end. Though the C# compiler should now that they are readonly, it seems that it didn't always take advantage of that and it probably made more sense to make these types readonly than to add more special casing to the compiler.

Maybe compiler (JIT Compiler?) removes those defensive copies because, as you said, it handles them specially, but this doesn't look obvious.

The JIT can't do much about this. It does not know about readonly and it doesn't know that ToString does not modify the value unless ToString inlines. And even then, it may have problems figuring out that copies aren't needed. Once the address of variable is taken things can get complicated.

In theory C# compiler is even further than JIT from seeing the actual implementation of int.ToString() or double.GetHashCode(), so it cannot assume the methods are not mutating.
Even if mutations would not make sense, there are no specs either C# or CLR that demand or promise that.
We actually went on the route of treating Nulable<T> as readonly. Nullable<T> instances can be pretty large, so it would be desirable. And then we had to dial that back since it was demonstrated that it is in fact possible to write code that (ab)uses writeability of the T field.
As I remember it was about at that point that we changed our mind about specialcasing primitives as well.
Basically we realized that there is  cost :

additional burden of specing/justifying the special casing in the language spec.
if CLR/FX would annotate primitives as readonly, the above hack is unnecessary but has to stay in the language spec forever.
there is a risk of our assumptions being wrong in some corner case or on some runtime.
After seeing a good deal of alternative/experimental CLR runtimes, mutable System.Int32 or System.Double would amuse me but would not be very shocking to see :-)

At the same time the benefits from avoiding copying tiny register-size values is diminishingly small.
Annotating primitive types as readonly (if implementation indeed never writes the fields) is the right thing to do IMO.


C++ always warning auto etc because is not C++11

I have changed every C++ standard related settings to C++17 (including C/C++ extension, c_cpp_properties etc), but it still warning like auto, emplaces methods that are c++11 features etc, very annoying! Even I have uninstalled the C++ extension, same warning!

<img width="721" alt="Screenshot 2021-09-25 at 13 28 41" src="https://user-images.githubusercontent.com/56354990/134759686-df84c1a8-60f1-4131-9c98-1fca7d962de0.png"

/extCpp
These diagnostics are provided by extension. Please report this problem in extension's repo.


Order Column API does not recognize column name when it has a dot '.' inside its name

The tutorial on https://datatables.yajrabox.com/eloquent/order-column gave me the idea of replacing the sorted column with the other column. For example, the code below will make sure that when the title column is sorted, it will be sorted by email instead.
orderColumn('title', 'email $1')

But the other tutorial, searching with relationships, https://yajrabox.com/docs/laravel-datatables/master/relationships, suggested that the name of the column should be the relation.column_name, so the name of the column became posts.title.
Then I continued to update the column name in orderColumn,
it became orderColumn('posts.title', 'email $1'), but it did not work, the column will be sorted by the title, not email.
I guess because the name of the column has the '.' inside its name.
So are there any workaround? Thanks in advance.

Maybe try using a name alias on js and use it instead?
{data: 'posts.title', name: 'post_title'}

->orderColumn('post_title', 'email $1')

Yeah, that would work, but it will make the search function raise errors because the generated SQL query will use the post_title as the column name, but post_title does not exist.

@yajra. I got the solution. This would work:
{data: 'relationship_function_name_declared_in_model.title', name: 'post_title'}

->orderColumn('real_table_name.title', 'email $1')


New Landing Page

i will come up with a fresh landing page

@0silverback0
assign me with hacktoberfest labels

sorry i thought i sent this already. We are currently awaiting a new landing page design but your more than welcome to work on it still

can you assign this issue to me ?


change as suggested by original programmer and user of ecc software

As suggested in https://github.com/Itseez/opencv/issues/4230

:+1:


Not able to configure swift toolkit 2.4.0 using carthage

Bug Report
I am trying to upgrade swift-toolkit version via carthage  using :--> github "readium/swift-toolkit" ~> 2.4.0
What happened?
I am trying to upgrade  swift-toolkit using carthage:--> github "readium/swift-toolkit" ~> 2.4.0
Initially it started updating carthages and continued processing for couple of hours and later it terminated the process in terminal.
At the end updating carthage remains unsuccessful.
Expected behavior

I need to upgrade swift-toolkit to version 2.4.0 using :-  github "readium/swift-toolkit" ~> 2.4.0
FYI: Previously we were using followings to install swift toolkit frameworks
Question: Will these still work for us to fetch updated frameworks version from develop branch
github "readium/r2-shared-swift" "develop"
github "readium/r2-streamer-swift" "develop"
github "readium/r2-navigator-swift" "develop"
github "readium/r2-opds-swift" "develop"
github "readium/r2-lcp-swift" "develop"

How to reproduce?

Updated this in cart file :-> github "readium/swift-toolkit" ~> 2.4.0
Followed the steps to update the Carthages via Terminal XCode14.0
It initiated the upgrading carthages.
Continue updating and stuck at random point in between for couple of hours and later it terminates the process.

Environment

Readium version: binary "https://liblcp.dita.digital/readium/liblcp/ios/carthage/XXXXXXXX/liblcp.json" ~> 2.0.0

@mickael-menu  Thanks for quick response.
Here's he command I am using to install carthages.

brew cleanup
rm -rf ~/Library/Developer/Xcode/DerivedData
rm -rf ~/Library/Caches/org.carthage.CarthageKit
rm -rf ~/Library/Caches/carthage
rm -rf Carthage
carthage update --use-xcframeworks --platform ios

And below is the SS from terminal as end result.

And with the --verbose flag added to the carthage command?

Run carthage update --use-xcframeworks --platform ios --verbose.

@mickael-menu I have tried with this command as well
carthage update --use-xcframeworks --platform ios --verbose
But still same output, not such detailed logs there in terminal
See attached SS.

Then I'm not sure what's the problem, it looks like an issue with Carthage on your end. It runs fine for me.

Hi @mickael-menu  I have configured carthages for swift toolkit successfully
Thank for your support.
We have one small query.
After updating swift-toolkit to 2.4.0, Does R2Lcp binaries needs to be updated to the latest version?
We are having r2Lcp binaries i.e: "https://liblcp.dita.digital/readium/liblcp/ios/carthage/XXXXXXXX/liblcp.json" ~> 2.0.0
Which is having some older versions like 2.0.0, 2.1.0 etc...
Also some of the new binaries we have with 3.0.0 & 3.1.0 versions.
Do we need to update all these binaries to the latest versions?

No the liblcp is a different project than the Readium toolkit and you don't need to update them at the same time.

@mickael-menu Thank you for your reply.
Would like to understand that when do we need to update this liblcp binaries?


Redesign Header

Header of any website is the first element to be noticed, try to make it more appealing to the audience.

I can work on this, kindly assign it to me.
Also pls tell if you have any specification/preferences/requirements for it.


Watch in apiserver proposal

This is (hopefully) cleaner and a bit more detailed proposal of having watch in apiserver than the one described in https://github.com/GoogleCloudPlatform/kubernetes/issues/10475#issuecomment-117211186. But the overall idea is mostly the same.
Ref #10475
cc @bprashanth @lavalamp @davidopp
cc @smarterclayton @derekwaynecarr @timothysc

Thanks for the comments @smarterclayton - I've tried to answer them, but didn't update the doc yet (since at least in some places I'm not sure if you suggest different approach or just my doc is not clear enough to understand it :P )

Resending my last response - wasn't sure whether GitHub ate it:
We can also support "last seen" for a watch. Imagine a watch opened on "services" and one opened on "services/test" (by name).  Once we start watching "services", we know "test" implicitly does or does not change by observing it is not updated.  Therefore, if we track the last resource version seen in a map for that particular watch (t1), if the "services/test" watch is disconnected, then reconnects with an older resource version (t1) than that last version seen, we know we can start the watch for the client at the latest resource version we have seen for any service.
This is another reason for having all the watches on a single watch on etcd across all resources.  Our most common LIST comes from watches to infrequently changed resource types in the presence of rapid updates in other types - example, services rarely change but events are firing all the time, so the odds of a services client being able to reconnect within the window are low. However, if we observe most resources with one watch (potentially excluding events) then we can easily track the HWM resource version for each type or watch, and given that we know when we can tell clients to watch from latest, vs relisting.
While I originally thought that sending the list of events through watch would make clients easier, I think it has some limitations.  First, all clients have to support a new type of event, even those that don't want it.  Second, we may eventually want to paginate that list for a client (50K pods at 1K each in one watch event?), which means sending multiple resync events in sequence with starting and closing.  I'd really prefer that to be part of a list API (since it's also useful there).
If we want to serve list results from memory, we can do that this way, or by operating a higher level cache.  Or we could just run an etcd proxy (in process), which would do all that for us and be able to serve stale reads as well.  The TCP churn for rewatches is significant - but if we do plan to mirror etcd it might be worth asking whether we just want a local etcd proxy (the one that maintains the state map, not an HTTP proxy).

The etcd proxy code may not be suitable in all cases - however, it does mirror raft (I believe) which is implicitly cheaper because we'll be streaming protobufs from the etcd server, instead of http+json.  On the other hand, we'd be mirroring the full raft state which may be larger in memory than our custom cache could be.

We can also support "last seen" for a watch. Imagine a watch opened on "services" and one opened on "services/test" (by name). Once we start watching "services", we know "test" implicitly does or does not change by observing it is not updated. Therefore, if we track the last resource version seen in a map for that particular watch (t1), if the "services/test" watch is disconnected, then reconnects with an older resource version (t1) than that last version seen, we know we can start the watch for the client at the latest resource version we have seen for any service.
I think that either "last seen" doesn't fully solve the problem or I'm missing something.
Assume that we know that "last seen" for a watch "services/test" is at t1, and the latest event in the cache is at "t2" (t1 < t2). Then if for watch "services" "last seen" is also t1, it's ok, but if it's greater than t1, we have to relist. So you're suggesting that it's not a problem, right?

This is another reason for having all the watches on a single watch on etcd across all resources. Our most common LIST comes from watches to infrequently changed resource types in the presence of rapid updates in other types - example, services rarely change but events are firing all the time, so the odds of a services client being able to reconnect within the window are low. However, if we observe most resources with one watch (potentially excluding events) then we can easily track the HWM resource version for each type or watch, and given that we know when we can tell clients to watch from latest, vs relisting.
I'm not fully convinced about single cache vs. cache per-type, but I think it's more an implementation detail - it doesn't change anything significantly.

While I originally thought that sending the list of events through watch would make clients easier, I think it has some limitations. First, all clients have to support a new type of event, even those that don't want it. Second, we may eventually want to paginate that list for a client (50K pods at 1K each in one watch event?), which means sending multiple resync events in sequence with starting and closing. I'd really prefer that to be part of a list API (since it's also useful there).
I agree with your point, that all clients need to support the new event type. This is some limitation.
However, I don't understand why sending 50K pods in one watch is bad and sending them in one list is ok. Why do you think it's a problem to send "big" watch events?

This is another reason for having all the watches on a single watch on etcd across all resources. Our most common LIST comes from watches to infrequently changed resource types in the presence of rapid updates in other types - example, services rarely change but events are firing all the time, so the odds of a services client being able to reconnect within the window are low.
One more observation about it - basically we can workaround it also having per-type cache. If services are not changing frequently, having a separate cache for them would mean that it will be changing rarely. So it can be much smaller to store the same length of history.
In other words, having per-type cache we can configure it so that for each resource type we will have at least, say, X minutes of history - this would probably mean having e.g. 50x bigger cache for pods than e.g. for services, but then it's doable.
So in per-resource-types approach, you can ensure that you have at least few watch events for every type - this can't be done with a single cache for all resources.
[To be clear - I'm not saying my proposal is strictly better - I'm saying both have advantages and I would like to make a good decision in the end]

Also - I think that once we have just one watch per type open to etcd, the "out of window" errors from etcd will be significantly less frequent.

One more thing I would like to emphasize - the whole idea behind introducing the "Resync" watch event is to avoid a lot of LIST request to etcd at the same time, whenever "out of window" error happens for the "internal" watch. If we think this will not be a problem, maybe it doesn't make sense to do it then (but I'm still not convinced).

1 request - the ability to dump the cache (for testing and profiling), possibly via a signal...
+1 if it includes hitcounts.

I'm on PTO this week but will follow up on Monday.
On Jul 3, 2015, at 6:21 AM, Wojciech Tyczynski<EMAIL_ADDRESS>wrote:
We can also support "last seen" for a watch. Imagine a watch opened on
"services" and one opened on "services/test" (by name). Once we start
watching "services", we know "test" implicitly does or does not change by
observing it is not updated. Therefore, if we track the last resource
version seen in a map for that particular watch (t1), if the
"services/test" watch is disconnected, then reconnects with an older
resource version (t1) than that last version seen, we know we can start the
watch for the client at the latest resource version we have seen for any
service.
I think that either "last seen" doesn't fully solve the problem or I'm
missing something.
Assume that we know that "last seen" for a watch "services/test" is at t1,
and the latest event in the cache is at "t2" (t1 < t2). Then if for watch
"services" "last seen" is also t1, it's ok, but if it's greater than t1, we
have to relist. So you're suggesting that it's not a problem, right?
This is another reason for having all the watches on a single watch on etcd
across all resources. Our most common LIST comes from watches to
infrequently changed resource types in the presence of rapid updates in
other types - example, services rarely change but events are firing all the
time, so the odds of a services client being able to reconnect within the
window are low. However, if we observe most resources with one watch
(potentially excluding events) then we can easily track the HWM resource
version for each type or watch, and given that we know when we can tell
clients to watch from latest, vs relisting.
I'm not fully convinced about single cache vs. cache per-type, but I think
it's more an implementation detail - it doesn't change anything
significantly.
While I originally thought that sending the list of events through watch
would make clients easier, I think it has some limitations. First, all
clients have to support a new type of event, even those that don't want it.
Second, we may eventually want to paginate that list for a client (50K pods
at 1K each in one watch event?), which means sending multiple resync events
in sequence with starting and closing. I'd really prefer that to be part of
a list API (since it's also useful there).
I agree with your point, that all clients need to support the new event
type. This is some limitation.
However, I don't understand why sending 50K pods in one watch is bad and
sending them in one list is ok. Why do you think it's a problem to send
"big" watch events?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/10679#issuecomment-118307105
.

imho I would like to offload "events" entirely out of the main etcd, as there is no reason history needs to reside with actionable cluster-state.

In etcd 3 we'll be able to control archival of events at an application
scope, which means events can pass through the cluster and out into
supporting tools (audit, graph dbs, usage tracking) in a consistent
fashion.  I agree it should be an option to move them more rapidly or
directly to a different system, but requiring a separate solution increases
setup / on ramp scenarios.
On Jul 8, 2015, at 2:56 PM, Timothy St. Clair<EMAIL_ADDRESS>wrote:
imho I would like to offload "events" entirely out of the main etcd, as
there is no reason history needs to reside with actionable cluster-state.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/10679#issuecomment-119696254
.

Overall, I am fine with this, with these two caveats:

Implementation: turn tools.EtcdHelper into an interface, use that as your API.
Leave out resync for the first pass. We can judge whether its necessary by seeing how much relisting happens when we try turning this on for some resources.

Thanks for all your comments @lavalamp @smarterclayton and @timothysc - I agree with most of them. I'm going to apply them to the doc either today or tomorrow. I will ping this thread when the doc is updated.
Once again thanks for very detailed review (or just the first pass of it? :))

To be clear - I'm answering to some comments, but I will upload the new version once I address all of them.

Comments applied - PTAL (I would like to start working on the implementation next week).

Looks much better, thanks! LGTM

LGTM

Thanks a lot for review!
I'm going to start working on the implementation on Monday.


eslint: Fix unicorn/prefer-spread

This was initially disabled for IE/Babel-related reasons that no longer apply.

Yay, merged, thanks @andersk!


[timeseries] Update log messages

Description of changes:

Raise a human-readable exception when calling leaderboard if all models failed during training
Remove redundant log messages

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

These are minor changes that can be postponed to the next minor version


Das_Geek: Watch rammafoundationrepair.ca

Das_Geek requests the watch of the watch_keyword rammafoundationrepair\.ca. See the MS search here and the Stack Exchange search here.

rammafoundationrepair\.ca has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Handle headers in TsvFileParser

Added simple functionality for headers in TSV parser. This way you can dynamically add TSV files w a subset of columns using insertInto. Also added an example of possible use.

Ok, so I have made some changes to the pull request. The change gets to be a bit larger but should be more intuitive to work with.

Hi, I think it's a good PR given the already existing code. Me and Jörgen had a chat and worked a bit on refactoring the code so that FileParser takes the File in the constructor. That way method getColumnNames does not have to be exposed. However, to keep the safeguards for ambiguous column names specifications, the TableDataBuilder would also have to be rebuilt to fully build the state once build is called. As of now, the state is partially built before build() is called and that requires columns to be known and an implicit call order of the builder.
We postpone these changes to the next major release as it is much simpler to do if we make some small breaking changes to the builder.
Given that, it's a go on the PR.
/Pelle

@teabot Do you have any more comments? Otherwise we'll merge this PR.


Prefer constant name.

Prefer using the constant available.

 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.


Translate concepts/scheduling/kube-scheduler.md in Korean

Added concepts/scheduling/kube-scheduler.md file and translated it in Korean.

I didn't follow the right process. I'll rework for this.


chore: typing cd

Codecov Report
Attention: Patch coverage is 0% with 21 lines in your changes missing coverage. Please review.

Project coverage is 6.40%. Comparing base (7e66870) to head (9ebe2a2).

Files
Patch %
Lines

midealocal/devices/cd/message.py
0.00%
13 Missing :warning:

midealocal/devices/cd/__init__.py
0.00%
8 Missing :warning:

Additional details and impacted files
@@           Coverage Diff            @@
##            main     #57      +/-   ##
========================================
- Coverage   6.40%   6.40%   -0.01%
========================================
  Files         77      77
  Lines       6588    6589       +1
========================================
  Hits         422     422
- Misses      6166    6167       +1

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


bug: css does not work with npm install but works with cdn link. i am working in vite + react project

What version of daisyUI are you using?
2.47.0
Describe your issue
I am working on a project with vite + react where css of daisy ui is not working with npm install. But after adding cdn in html file, it works fine. I am sure that i'm using latest version of tailwind css upto 3.0 and 2.47.0 version of daisy ui. What's the problem? why css is not working? I am including my github repo of the project.
What browsers are you seeing the problem on?
Chrome
Reproduction URL (optional)
https://github.com/shufolislam1/eduWeb

I can't see your project on GitHub. Is it a public project?
Also, make sure that the content object on your tailwind.config.js file is including the path to all your markup files. Otherwise, Tailwind CSS can't generate styles for the class names you used.

I can't see your project on GitHub. Is it a public project?
Also, make sure that the content object on your tailwind.config.js file is including the path to all your markup files. Otherwise, Tailwind CSS can't generate styles for the class names you used.

ok. Bug fixed. Thank you. Actually, my tailwind css was having some problems. Issue fixed.


Added setMaxValue method in ProfilePercentageView class

this will help people to set the maxValue from java/kotlin code or data binding

Fix: https://github.com/smartSenseSolutions/ProfilePercentageView/issues/1


Trojan in latest Windows release 1.2

Trojan:Win32/Wacatac.B!ml
Listed twice as: "Severe" in Windows scan of unzipped .exe file
Same response when tried several times. Should this be ignored?
When both trojans are removed, unzipped file won't run and quickly disappears.

@Bruce33333 The installation file was downloaded from the releases section? https://github.com/chidiwilliams/buzz/releases
Installation files for Windows are not signed, so windows will warn you about that. It is safe to ignore that warning and click "Run anyway"
Security tools should not detect any trojans or security issues. You can try downloading the installation zip again from the releases section.
sha256 sum of the zip file should be 6a44c0b2ba35a9ce822124fe87b4746f22e673baa2bf07e537b9829ab6b9ace0
sha256 sum of the Buzz-1.2.0-windows.exe should be bbc37eb36c517d3e9f25d5d247728a2684f355ae8702dcac85c45e7f332b8244
Command co check the SHA256 sum of the file certutil -hashfile .\Buzz-1.2.0-windows.exe SHA256
Windows defender on Windows 10 did not detect any issues with the file from releases section

Re d/l and everything now works fine.
Not sure what exactly happened but it must have been on my end.
Nice to see you here and appreciate the work you are doing.


Updated imports, moved metrics calls to init

The main changes are
(1) the compute metrics calls and the list of metrics was moved to src/init.py, so that one can access the metrics via
from sharpness import compute_all_metrics
(2) That method will automatically check if you entered X  or X and T. If X only, only single-image metrics are returned. Else all metrics are returned and single metrics are computed for each X and T and returned as a tuple.
I did a little light modifications inside metrics.py (just removing T from the two single-image metrics "grad" and "s1" and calling each one at a time in init when there are two images.

Feel free to tell me to change stuff as you see fit. I kind of just threw this together by going with "I want to be able to: from sharpness import (stuff)". Also the README will have gradient-based metric descriptions on my next commit!


iOS: initial support of Metal rendering backend (early Alpha)

I just noticed Solar2D creates and uploads luminance texture data every frame (for displaying text it seems). Luminance texture format data upload is currently not very efficient in MetalANGLE due to conversion from luminance to RGBA. I will try to optimize it.
However, there is a better way. You could change Texture::kLuminance handling code in getFormatTokens() (https://github.com/coronalabs/corona/blob/fb1dd283ca52d0ace430fe7470aaab24c320dcbd/librtt/Renderer/Rtt_GLTexture.cpp#L39) to use GL_RED_EXT instead GL_LUMINANCE (GL_RED_EXT is from extension GL_EXT_texture_rg but MetalANGLE supports it on all Metal devices)

Running #139 sample code on simulator I saw noticeable micro stuttering due to format conversion. The stuttering went away after changing GL_LUMINANCE  to GL_RED_EXT.

Thanks so much. I had to cut some corners to make it work at first, but results are awesome so far.
Also, if you noticed I changed to my fork, which uses submodules and some minor changes. Would you like me to make a pull request for them?

Thanks, the submodules changes I don't want to merge just yet. I still want to keep the old dependencies structure so that it would be easy to merge with upstream ANGLE repo.
I saw you changed min iOS SDK to 8.0. That's nice but I'm afraid it would introduce some compatibility issues that I'm not aware. So let's see how it goes with Solar2D project for now.


Change routing for shielding question

This change uses the information from the shielding advice in the
session to determine what questions should be asked.
If shielding advice is 1 it should ask the basic-care-needs question.
Going to wait for https://github.com/alphagov/govuk-shielded-vulnerable-people-service/pull/251 to address local testing changes needed for e2e.

We would need to update the values for POSTCODE_TIER_OVERRIDE in concourse before this can be deployed.

We would need to update the values for POSTCODE_TIER_OVERRIDE in concourse before this can be deployed.


A stamp with the specified name already exists in the location BLU

When attempting to deploy a new Function app in a Container App Environment, I received an "A stamp with the specified name already exists in the location BLU" error.
I'm not sure what "BLU" is in this context.  The error doesn't give me enough information to resolve.
{
  "code": "DeploymentFailed",
  "target": "/subscriptions/xxxxxx/resourceGroups/rg-func-aca-mcollier/providers/Microsoft.Resources/deployments/func-apps-deployment",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
  "details": [
    {
      "target": "/subscriptions/xxxxxx/resourceGroups/rg-func-aca-mcollier/providers/Microsoft.Resources/deployments/func-apps-deployment",
      "message": "A stamp with the specified name already exists in the location BLU."
    }
  ]
}

Thanks for reporting this issue. BLU here means East US region. We are investigating the root cause of this issue, this is a known intermittent issue. We are adding more logs to get the reason. Can you re-try with different name and let us know?

I was able to successful provision the resources by using a new resource group name and new Container Apps Environment name.


Bump redoc to 2.1.3

Update redoc to the latest 2.1.3 release and enable dependabot updates.

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

Project coverage is 91.70%. Comparing base (45a2cb7) to head (56c1808).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2807   +/-   ##
=======================================
  Coverage   91.70%   91.70%
=======================================
  Files          91       91
  Lines        3025     3025
  Branches      519      519
=======================================
  Hits         2774     2774
  Misses        251      251

Flag
Coverage Δ

Linux
91.70% <ø> (ø)

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


set up automatic pushing of 538 raptor and elo data to zoltar

This involves writing a script to scrape data from this page, format in Zoltar-ready format and push into Zoltar, and setting up that script to run as an Action.

Some of the code in this file can help getting the RAPTOR model predictions, but I haven't figured out how to scrape the Elo ones.


scd-test

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/platform_tests ref=scd_fix

/benchmark module=tabular preset=tabular_best benchmark=tabular_full time_limit=1h


chore(deps): Update dependencies

Updated:

maven to 3.9.6
maven-wrapper to 3.3.1
jakarta.inject to 1.0.5
Ubuntu to 24.04
Import BOM instead of overriding maven.version

Not updated due to breaking changes:

slf4j 1.7.36 to 2.0.13
4.0.0-alpha-8 to 4.0.0-alpha-13

@gnodet Thank you for closing my work without explanation 👍


Update Makefile and README.md

Clean up readme.  Allow user to pick a compiler other than gcc.
Explicitly link pthread library (for clang).

Sorry for the delay in reviewing. All good. Thanks.


Refs #28816 -- Prevented silencing data loss when decreasing CharField.max_length for ArrayField.base_field on PostgreSQL.

Fix for ticket 28816 comment.

@felixxm, Thanks for the comment.
I changed the patch based on your comment.

@felixxm Thanks for your nice patch.
I remove test_alter_array_field_change_base_field_type_and_length.

@hramezani Thanks :+1:. I decided to create a separate hook for base fields types.


No longer removing branches

Not sure if its isolated to me or now but i fresh no longer removes branches when i run it
running g fresh -f nets me
Fetching origin
Pruning origin
URL: https://github.com/wheniwork/{repo}
 * [pruned] origin/feature/update-deps
 * [pruned] origin/fix/fix-case
 * [pruned] origin/fix/fix-jenkins
Already on 'master'
Your branch is up-to-date with 'origin/master'.

when the following marked branches are merged.
g branch --list
  feature/add-devtool-docs < merged
  feature/add-pull-approve < merged
  feature/add-uploader-analytics
  feature/add-webpack-dashboard < merged
  feature/analytics-mk1 < merged
  feature/billing-react
  feature/de-ify-dependancies
  feature/invite-coworker
  feature/pending-coworkers
  feature/update-deps < merged
  feature/workchat-firebase-poc
  fix/correct-readme < merged
  fix/fix-case < merged
  fix/fix-jenkins < merged
* master
  react

Also on git 2.9.3

Actaully appears to be due to github implementing squash commits is there a way to still use this in that case?

For what it's worth i found t his that does what i want any chance of implementing it? in this?
git fetch --prune && git branch -r | awk '{print $1}' | egrep -v -f /dev/fd/0 <(git branch -vv | grep origin) | awk '{print $1}' | xargs git branch -D

or a shorter version git config --global alias.purge '!git branch -vv | awk '''/: gone]/{print $1}''' | xargs git branch -d && :'

will look into it, i think squash commits should still work

@th3fallen turns out squash commits from github provide no information about their original branch
it's not possible to delete stale branches that resulted in squashed PR commits