Allow tracking all subclasses of sealed! classes

This is a feature that would be analogous to the values arrays for a T::Enum: since a sealed! class is necessarily going to know what all its subclasses are, we can keep those around in an array or set and return them all.
The implementation here keeps a set, but it could as easily be an array. Additionally, this exposes the collection via a helper method on T::Utils. A runtime implementation could easy add a static helper method onto the sealed class (e.g. MySealedClass.all_subclasses) but that would be annoying from a static point of view, since calling sealed! would "magically" introduce new methods onto the sealed class. This could be implemented via a rewriter method if we really wanted it, but I felt like the T::Utils approach was cleaner overall.
Additionally, this talks about subclasses but makes no distinction between modules and classes. I wasn't sure of a better naming convention was, and I didn't think it was worth making a distinction since you can easily distinguish them later (between classes and included modules and extended modules) but subclasses is not a great name for all of those. Happy to open it up to bikeshedding!
Motivation
I've mentioned this once or twice as a thing that could significantly clean up some code that uses an ad-hoc mechanism inside Stripe. This also nicely resembles the capabilities you get from T::Enum, but by exposing it on a sealed! class we can piggyback on the sealed! guarantees as well.
Test plan
See included automated tests. Happy to include more if there are cases we feel are missing.

I remember I tried implementing this when I first wrote sealed! and I went back on it. I’ll try to see if I can remember what held me up last time.

A runtime implementation could easy add a static helper method onto the sealed class (e.g. MySealedClass.all_subclasses) but that would be annoying from a static point of view, since calling sealed! would "magically" introduce new methods onto the sealed class. This could be implemented via a rewriter method if we really wanted it, but I felt like the T::Utils approach was cleaner overall.

I actually think introducing a new method is better. Sorbet will be able to introduce it in a DSL pass, so jump-to-definition will work (can make it jump to the location of the sealed! method call.
This will also make it impossible to mis-use. There's no way to write a type signature for the T::Utils helper right now that says "any class which is sealed!" (that doesn't exist in the type system). Meanwhile, a class-level method would be easy for Sorbet to say "this method doesn't exist" if someone deleted the call to sealed! or forgot to add it.
Right now, correct usage of the T::Utils helper is only checked with a runtime raise.

A runtime implementation could easy add a static helper method onto the sealed class (e.g. MySealedClass.all_subclasses) but that would be annoying from a static point of view, since calling sealed! would "magically" introduce new methods onto the sealed class. This could be implemented via a rewriter method if we really wanted it, but I felt like the T::Utils approach was cleaner overall.

I actually think introducing a new method is better. Sorbet will be able to introduce it in a DSL pass, so jump-to-definition will work (can make it jump to the location of the sealed! method call.
This will also make it impossible to mis-use. There's no way to write a type signature for the T::Utils helper right now that says "any class which is sealed!" (that doesn't exist in the type system). Meanwhile, a class-level method would be easy for Sorbet to say "this method doesn't exist" if someone deleted the call to sealed! or forgot to add it.
Right now, correct usage of the T::Utils helper is only checked with a runtime raise.

The implementation here keeps a set, but it could as easily be an array.

I like it being a Set, because I don't want people to rely on the order of the elements.

Wanted to preserve a conversation that Getty and I had:

jez:

I’ve mentioned this once or twice as a thing that could significantly clean up some code that uses an ad-hoc mechanism inside Stripe. This also nicely resembles the capabilities you get from T::Enum, but by exposing it on a sealed! class we can piggyback on the sealed! guarantees as well.

gdritter i presume you want to replace subclasses lists with this sealed! PR?
i don’t see this as a general purpose replacement for subclasses list, because it constrains the subclasses to all be in the same file
i don’t know for sure but i’d have to guess that the overlap between people who want to use subclasses lists and the people whose subclasses are all in one file is zero
gdritter:
The intention is to replace some of them. It's not a general replacement—I've got a like four-pronged approach to that.
(It's a pretty small number of SUBCLASSES uses that could get replaced by this, but it's not zero.)
jez:
gotcha. what are the other three prongs? do they involve sealed! as well? or are they unrelated?
gdritter:
They're unrelated. (One of them is just doing SUBCLASSES in a package-local way, since there are a few dozen SUBCLASSES uses that only span one package; one of them involves automatically generating tests, since there are a number of uses of SUBCLASSES that are just "I want to enforce invariants on every subclass"; one of them involves doing static extraction of metadata so that you can "look up" a class via metadata without loading it.)
(FWIW, we can get by [for our pay-server use case] without sealed! in general, since those can always be package-local SUBCLASSES for those cases instead. But [this PR] seemed like a reasonable extension, but if there's FUD I'm happy to let it go and use other mechanisms.)
jez:
gotcha
another thing: we had considered not accidentally closing the door on supporting something which would let sealed! work across subclasses defined in separate files (e.g., write a list of file names that are allowed to subclass the class in the class definition or something)
i think that adding this change effectively traps us from being able to do that. are you okay with that tradeoff?
gdritter:
How does this change prevent that?
jez:
in this case the subclasses set will not always be populated because some files will not have loaded and been added to the set
the current PR’s correctness relies on the fact that the set is complete after loading the one file that’s guaranteed to have been loaded (the parent class’s file)
gdritter:
If the semantics of the set of files are "there will be subclasses defined in all these files" (rather than "there can be") you could verify that files have been "observed" and consequently are loaded, and trying to access the set of subclasses can raise if there are expected files that haven't been loaded.
Alternately, I think you could say, "This feature simply won't work if you've spanned multiple files, and trying to access the set of subclasses will give you an exception."
jez:
how could you detect when to raise an exception? what’s the difference between a sealed class with no subclasses vs a sealed class but the files with subclasses haven’t loaded?
or are you saying that the annotation which would allow multiple files would be enough? i think i see
gotcha i think i understand both your messages now
gdritter:
Yeah, that's what I'm suggesting. That annotation [to opt-in to multi-file sealed classes] would either let you tweak the semantics of the set of subclasses, or simply say, "You cannot safely enumerate all subclasses if you are using this feature."
jez:
yep, and it seemed like you were suggesting even potentially using LOADED_FEATURES or something (and probably caching it) to potentially allow it after all classes loaded
yeah i like it
i am now convinced that this change doesn’t trap door us
thanks!

@aisamanra Another thing: if we use a class-level helper method, we can appropriately type the return type, whereas right now the only thing you return is that it's a T::Set[Module].
Though I guess the downside is that such a method would be inherited by all the children, but it wouldn't make sense to call it unless that child class it itself a sealed class.

Another fun thing: the way that sealed!'s exhaustiveness checking works is that sealed classes already get a magic <sealedSubclasses> method synthesized that records a type like
T::Array[T.any(Child1, Child2, Child3)]

and that special class is what's used to look up the stored children.
With this change, you could potentially rename that magic method from <sealedSubclasses> to sealed_subclasses and then it would be an actual, callable method whose type would be filled in to the most specific type possible by resolver. You could also probably change it from T::Array to T::Set, i don't think that's important to resolver/infer right now.

It turns out the name of the internal method was not <sealed_subclasses>, but in fact was sealed_subclasses: in fact, this sorbet.run link currently reports the type of sealed_subclasses as T::Array[T.any(T.class_of(A::X), T.class_of(A::Y))] even without my changes!
This has reworks sealed_subclasses to use a Set instead of an Array and reworks the runtime implementation to produce the relevant method as well. I've also added some static tests to verify the inferred types of sealed_subclasses, as well.

@aisamanra another thing: would you mind adding a few words about this method to the website?

I addressed the last few things but I want review especially on the docs, in case they need some editing or moving.


Add source generator for IsLongRunning property

Supersedes https://github.com/ppy/osu-framework/pull/5763
Compared to the above PR, this uses the newer structure of HandleInputCache rather than polluting dependency injection.
Removes yet another usage of reflection inside Drawable. This is also queried every Drawable load, so could add up very easily.
I've moved the property to Drawable_IsLongRunning.cs just to isolate the potentially-reflection part of Drawable away from the main file. This way it makes it easier to remove the using System.Reflection directive and see what's left.

Method
Mean
Error
StdDev
Allocated

QueryNonLongRunningViaReflection
654.947 ns
9.9584 ns
8.8279 ns
48 B

QueryLongRunningViaReflection
1,246.236 ns
9.0457 ns
7.5536 ns
128 B

QueryNonLongRunningViaSourceGeneration
6.426 ns
0.0713 ns
0.0632 ns
-

QueryLongRunningViaSourceGeneration
6.527 ns
0.1540 ns
0.1582 ns
-

Seems good. Can reproduce benchmarked gains, framework and game tests pass.
@peppy Gonna need a sourcegen package here to proceed.


[Callout with media] Text not using color tokens and failing on dark themes

Headline, body copy, and caption in this component are not using color tokens.
Current:

Expecting: headline, body copy, and caption all use color $inverse-01

The merged PR includes discussions that brought about this new issue.  Reopening this issue to finish the work.

Fixed by @ariellalgilmore on #5828


Unable to move location of Observation from Edit window

Unable to change the location of the marker from the new observation edit window.
Steps:
From main map > New > click the Latitude/Longitude > moving the map also moves the marker so it's not possible to change the location of the marker.

57890989202db9c52b0c5e1760d8f8ab047aeb2b

iOS out of the box default is to long press the marker.  The marker will animate above your finger and you can then drag it at that point.  Release and the marker will drop.  I have added a prompt on the edit location navbar to make this more clear.


[Bugfix] Fix BNB loader target_modules

Motivation
When addressing the following TODO, I found a misconception regarding the use of target_modules. The issue arises because target_modules specifies which layers should have LoRA adapters added, rather than which layers should be quantized.
https://github.com/vllm-project/vllm/blob/15cc2a9f1acb70b68366da0a6d2a4549da3d32f4/vllm/model_executor/model_loader/loader.py#L714
Reproduce Code
from transformers import AutoModelForCausalLM
from peft import get_peft_model, LoraConfig, TaskType

model_name_or_path = "Llama-2-7b-chat-hf"
peft_config = LoraConfig(
    task_type=TaskType.CAUSAL_LM,
    inference_mode=True,
    r=8,
    lora_alpha=32,
    target_modules=[ # just add some layers to verify the effect of target_modules
        "gate_proj",
        "up_proj",
    ],
    use_rslora=False,
    use_dora=False,
)
model = AutoModelForCausalLM.from_pretrained(
    model_name_or_path, load_in_4bit=True
).eval()
model = get_peft_model(model, peft_config)
model.print_trainable_parameters()
print(model)

@mgoin  Sorry for bother you,  if you have bandwidth ，please look at this PR， thanks

Apologies for missing, this looks reasonable to me if the CI is green!


Add Application Login Option: Auto Redirect.

Auto redirect to idp when there is only one set and no other login method is enabled.

@Jonathan523 this is already supported: enable Auto signin in application edit page: https://door.casdoor.com/applications/casbin/app-casbin-oa

What I'm saying is that when password login is disabled and there is only one OAuth provider, any user attempting to log in should be redirected directly to the OAuth provider for authentication instead of automatically logging in when they have already logged into Casdoor.

Anyone who can solve this?

@Jonathan523 @fischermario fixed by: https://github.com/casdoor/casdoor/commit/0d12972e9280cf5b4ef8d8e93b7de9452c9d04ac


Return errors from rest.Backend.Test

What is the purpose of this change? What does it change?
The rest backen (and by embedding, the rclone backend) ignored errors in its Test method instead of passing them on.
I also made ErrIsNotExist private and made its Error() take a pointer receiver. Not doing so causes ambiguity when testing for a type and wastes space in the binary for an autogenerated method.
Was the change discussed in an issue or in the forum before?
Found this while working on #2797.
Checklist

[x] I have read the Contribution Guidelines
[x] I have enabled maintainer edits for this PR
[x] I have added tests for all changes in this PR
[x] I have run gofmt on the code in all commits
[x] All commit messages are formatted in the same style as the other commits in the repo
[x] I'm done, this Pull Request is ready for review

This obviously needs more work.


feat: vite migration

TODO:
Add  "*.vue": "eslint --cache --fix"

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


separate purpose field into operatorType and operatorDataStructure fields to enable better group by operations

closed in favor of https://github.com/tjjordan/dyod22-memory-tracking/issues/2


Crash on 0.60/0.61 if Compute Engine API not enabled

This was working fine on 0.59. When running gcpdiag on a project that hasn't enabled Compute Engine API, an exception is raised and cannot be bypassed, even if I try to exclude all GCE rules.
$ gcpdiag lint --project=myproject --exclude=gce

gcpdiag 🩺  0.61

Starting lint inspection (project: myproject)...

   ... fetching metadata of project myproject

Traceback (most recent call last):
  File "/opt/gcpdiag/gcpdiag/queries/gce.py", line 763, in get_project_metadata
    response = query.execute(num_retries=config.API_RETRIES)
  File "/opt/gcpdiag/.venv/lib/python3.9/site-packages/googleapiclient/_helpers.py", line 130, in positional_wrapper
    return wrapped(*args, **kwargs)
  File "/opt/gcpdiag/.venv/lib/python3.9/site-packages/googleapiclient/http.py", line 938, in execute
    raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 403 when requesting https://compute.googleapis.com/compute/v1/projects/myproject?alt=json returned "Compute Engine API has not been used in project<PHONE_NUMBER> before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/compute.googleapis.com/overview?project=1234567890 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.". Details: "[{'message': 'Compute Engine API has not been used in project<PHONE_NUMBER> before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/compute.googleapis.com/overview?project=1234567890 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.', 'domain': 'usageLimits', 'reason': 'accessNotConfigured', 'extendedHelp': 'https://console.developers.google.com'}]">

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/gcpdiag/bin/gcpdiag", line 70, in <module>
    main(sys.argv)
  File "/opt/gcpdiag/bin/gcpdiag", line 43, in main
    lint_command.run(argv)
  File "/opt/gcpdiag/gcpdiag/lint/command.py", line 342, in run
    if not gce.is_project_serial_port_logging_enabled(context.project_id) and \
  File "/opt/gcpdiag/gcpdiag/queries/gce.py", line 959, in is_project_serial_port_logging_enabled
    value = get_project_metadata(
  File "/opt/gcpdiag/gcpdiag/caching.py", line 155, in _cached_api_call_wrapper
    result = func(*args, **kwargs)
  File "/opt/gcpdiag/gcpdiag/queries/gce.py", line 765, in get_project_metadata
    raise utils.GcpApiError(err) from err
gcpdiag.utils.GcpApiError: Compute Engine API has not been used in project<PHONE_NUMBER> before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/compute.googleapis.com/overview?project=1234567890 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.

Thanks for reporting this. I updated the default version to be again 0.59 and we will work on a fix.

the current version 0.63 includes a fix to prevent an exception when Compute Engine API is not enabled.
Before closing this issue, can you check to confirm that it resolves your environment as well?


fixed non working reconnect example

reconnect example failed at https://github.com/mafintosh/multileveldown/blob/master/leveldown.js#L42
Fixed reconnect example adding an extra destroy
I also tested that pending db operations are executed when the connection resumes.

Thanks :)


chore(coverage): add coverage report

Current coverage is 99.41%

Branch #14 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.


Setting systemNavigationBarColor in SystemUiOverlayStyle undos setting of Status Bar Text/Icon Color

Steps to Reproduce
I would like to set the Status Bar to a white background with black overlay text. It works when I set the statusBarIconBrightness: Brightness.dark. However, once I set the systemNavigationBarColor: <your color here>. The text color goes back to the default white again. No matter what I do after that, the Status Bar text color stays white as long as I'm changing something with the System Navigation Bar as well.

Execute flutter run on the code sample
First, run the code without the line systemNavigationBarColor: <your color here>. You will see that the Status Bar has a white background with black text. Everything is running fine for the moment.
Now run the code again while including the systemNavigationBarColor: <your color here> line. You will see that the Status Bar Text Color changes back to the default white. The background of the Status Bar is as set, but the text changes back to white.

Expected results:
I wanted to see the Status Bar Text Brightness remain what I set it as.
Actual results:
When you include the systemNavigationBarColor: <your color here> line, the Status Bar Text Color changes back to the default white color (light brightness). And no matter what you do to change it to black, as long as the systemNavigationBarColor setting is there in SystemUiOverlayStyle, the Status Bar Text Color does NOT change.

Code sample

void main(List<String> args) async {
  WidgetsFlutterBinding.ensureInitialized();
  SystemChrome.setSystemUIOverlayStyle(const SystemUiOverlayStyle(
    statusBarColor: Colors.transparent,
    statusBarBrightness: Brightness.dark,
    statusBarIconBrightness: Brightness.dark,
    systemNavigationBarColor: Colors.transparent,
  ));
  runApp(const ProviderScope(child: MyProjectApp()));
}

Logs
Analyzing myproject...
No issues found! (ran in 2.3s)

[✓] Flutter (Channel stable, 3.3.1, on macOS 12.6 21G115 darwin-arm, locale en-US)
    • Flutter version 3.3.1 on channel stable at /Users/adityam/Documents/Dev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4f9d92fbbd (12 days ago), 2022-09-06 17:54:53 -0700
    • Engine revision 3efdf03e73
    • Dart version 2.18.0
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc2)
    • Android SDK at /Users/adityam/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A309
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.71.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.48.0

[✓] Connected device (3 available)
    • POCO M2 Pro (mobile) • fd46886c • android-arm64  • Android 11 (API 30)
    • macOS (desktop)      • macos    • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)         • chrome   • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

Hello @adifyr. I cannot reproduce what you're describing. See the code and what I output I am observing below. Could you explain exactly what you are experiencing?

Code Sample
SystemChrome.setSystemUIOverlayStyle(const SystemUiOverlayStyle(
  statusBarColor: Colors.transparent,
  statusBarBrightness: Brightness.dark,
  statusBarIconBrightness: Brightness.dark,
  systemNavigationBarColor: Colors.red,
));

Screenshot

Hi. This is the output I am receiving below. My device is POCO M2 Pro with MIUI 12.5.6:

WITH systemNavigationBarColor: <color>

SystemChrome.setSystemUIOverlayStyle(const SystemUiOverlayStyle(
  statusBarColor: Colors.transparent,
  statusBarBrightness: Brightness.dark,
  statusBarIconBrightness: Brightness.dark,
  systemNavigationBarColor: Colors.red,
));

WITHOUT systemNavigationBarColor: <color>

SystemChrome.setSystemUIOverlayStyle(const SystemUiOverlayStyle(
  statusBarColor: Colors.transparent,
  statusBarBrightness: Brightness.dark,
  statusBarIconBrightness: Brightness.dark,
));

I cannot reproduce this on a simulator running Android 13. Can you confirm if this is specific to your device or the Android version you are running on?

It may be specific to my device.

@adifyr I am marking this as a duplicate of https://github.com/flutter/flutter/issues/100027. If you disagree, please comment and I can reopen the issue. Thank you.


ARROW-7708: [Developer][Release] Include PARQUET issues in release changelogs by scraping git history

I wrote logic in dev/release/changelog.py that does the following:

Gets commit descriptions between the last major release and the new release version from git log
Uses the $PROJECT-$key strings to select from parquet-cpp issues returned by the JIRA API
These "Resolved as of the last Arrow release" Parquet issues are included in the changelog

I updated the changelogs back to 0.12.0 which was the first major release (I think) after the monorepo merge was completed. It might be nice to also update the changelogs on the website

Seems like there is an issue with the JIRA API
/home/runner/work/arrow/arrow/dev/release/02-source-test.rb:116:in `test_vote'
     113:     jql = jql_conditions.join(" AND ")
     114:     n_resolved_issues = nil
     115:     search_url = URI("#{jira_url}/rest/api/2/search?jql=#{CGI.escape(jql)}")
  => 116:     search_url.open do |response|
     117:       n_resolved_issues = JSON.parse(response.read)["total"]
     118:     end
     119:     output = source("VOTE")

+1


Clearer radicleisation of documented environment variables.

Can you rebase against master so rad tests run?

But of course they will fail ... :)


Sliders effect applied too strongly

Hello @hanatos,
When using any slider to edit pictures, i always get the feeling that the effect (exposure, shadows, ... all of them) is applied very strongly even with a very tiny bit of wheeling/scrolling.
Is that on purpose ?
I understand effects may actually be applied linearly but I always overshoot PP and must everytime resort to play a second time with the mouse at pixel level to get the expected amount of effect.
Could effects be applied less linearly but more exponentially, so that the user may apply subtle amount of effect without struggle.
Note: I use vkdt on JPEG ;-) if this is of value
Thanks a lot,
GLLM

I don't think there's anything wrong with the sliders. I can, however, understand this complaint for a few specific sliders:

the denoise slider does almost nothing for me. I see a strong effect as soon as it is unequal zero but otherwise the "strength" slider has almost no effect and the "luma" slider has no effect at all. That is without adjusting the "noise a" and "noise b" sliders in the "i-raw" module. It might be different if those are set to reasonable levels for my camera/ISO level.
when used to decrease contrast (values smaller 1), the "shadows" and "highlights" sliders in the "llap" module very quickly lead to unusable results. The usable range for some of my picures with very high dynamic range is 0.97-1.0. But again, this has nothing to do with the slider but with the module.

yes you definitely need to give good/correct noise a and noise b values, else the denoise module yields bad results.
yes the llap parameters i'm not very sure about being final/perfect. maybe it makes sense to limit the range from below (you can always ctrl-click and type to extend), that is a good idea for a simple change.

Thank you both for your comments !
I understand that you dont want to introduce distortion between the slider & the applied effect.
Indeed, darktable zoomable sliders are a suiting solution in dt.
Not sure you want to implement this here, or something similar.
I'll try using vkdt more and see if I get used to the amount of applied effect !
Thanks
GLLM

okay, closing this until then. feel free to reopen if you develop a strong opinion on it or have a concrete suggestion.


Rename the  name of some enums, constants

version: 15.0.0
I think the names of NbTransLangEnum, NB_TRANS_MAX_RETRY_TOKEN and NbTransSentenceItemEnum are not good, so I will rename them in the v15.0.0.
The "Enum" is redundant in NbTransLangEnum and NbTransSentenceItemEnum, so I will remove it;
NB_TRANS_MAX_RETRY_TOKEN does not meet rules, the "_TOKEN" will be removed

They have been renamed now.
NB_TRANS_MAX_RETRY_TOKEN has been rename as NB_TRANS_MAX_RETRY;
NbTransLangEnum has been rename as NbTransLang;
NbTransSentenceItemEnum has been rename as NbTransSentenceItem;


feat(ios/android) Month infinite scroll

Features #85

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement WebDriver

Implement a 7Facette driver.
This should use the WebDriverManager (https://github.com/bonigarcia/webdrivermanager/)
for local testing.
And also the Remote Web Driver for a Selenium Grid.

I made a basic implementation of a 7Facette Driver called FDriver.
The following features are there and already tested:

Local execution: Here we get a driver from the WebDriverManager.
Execution via Selenium Grid
Standard Selenium Screenshotting
Element interaction like click Link, click Button and write Text from the standard
File upload via Selenium Grid is possible
Screen comparison
Snapshotting of a selected Element
Snapshotting of the whole page, inclusive scroll up and down


Added Travel Journal (VanillaJS)

Closes: #691

Title : Travel Journal
Name: : Kosuri Indu
Idenitfy yourself: : GSSOC'24

Describe the add-ons or changes you've made 📃
Added the Travel Journal VanillaJS project.
How Has This Been Tested? ⚙

I have tested it on my system.
Screenshots 📷

Type of change ☑

What sort of change have you made:

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

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney
Please review and merge this PR

@Avdhesh-Varshney
Resolved the merge conflicts sir


Syntax highlighting break if we have multiline script tag

I am using prettier and at the moment it converts script tag to multi-line tag. With this volar syntax highlight breaks.

Hi @jd-solanki, I can't reproduce this problem, maybe you have installed other syntax highlight extensions and which affect syntax highlight on vue document.


Make Route struct public accessible

Motivation:
Routes struct has public method public mutating func add(_ route: Route), but there is no way to initialize Route struct from outside the framework.

Hi @diejmon - could you clarify what you mean "outside the framework"?
thanks!


[HOLD for #46838] Room - User details page can't be opened from members list

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.19-9
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/2654638
Issue reported by: Applause Internal Team
Action Performed:
Precondition: #room conversation with at least 2 users, one that has a custom avatar and the other has a default avatar

Click on the header of the conversation
Click on Members
Click on the avatar in the user details page

Expected Result:
In the conversation viewer, when clicking on the avatar of any of the users, a modal with the user information should display. When interacting the avatar inside the user details modal, a full size view of the avatar should display.
Actual Result:
Clicking on user avatar leads to user select/unselect. User details page is not opened.
Workaround:
Unknown
Platforms:

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/e6a12390-0d8a-455f-bbad-5b1a4f7b0f21

View all open jobs on GitHub

We think that this bug might be related to #vip-vsb

@Christinadobrzyn  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

I don't really understand how the expected and actual results are associated with the video. I'm going to ask the team for some clarifications on what is expected here.

@trjExpensify could you take a peek at this and let me know what is expected here or who to ask?

This will be resolved with https://github.com/Expensify/App/issues/46838 and PR https://github.com/Expensify/App/pull/47201.
I'm going to add a HOLD to this so we can test and make sure it's working as expected after https://github.com/Expensify/App/pull/47201 is deployed.

monitoring PR - https://github.com/Expensify/App/pull/47201

monitoring PR - https://github.com/Expensify/App/pull/47201

monitoring PR - https://github.com/Expensify/App/pull/47201
Heads up that I'll be ooo 9/4 - 9/10. I'm not going to assign a new BZ teammate to this as we're working on the PR. If you need a BZ teammate, please ping in slack.

monitoring PR - https://github.com/Expensify/App/pull/47201

monitoring PR - https://github.com/Expensify/App/pull/47201

This is resolved with https://github.com/Expensify/App/pull/47201! Closing.


adding software recipe end to end tests for linux

Windows support will be added later.
This PR is a little longer in length than I would generally like, let me know if it would be best to split it into multiple PRs.

Moved to https://github.com/GoogleCloudPlatform/osconfig/pull/116


Unable to add param to helper template method with #{ } - update docs?

I have a template helper method momentify that accepts one argument, createdAt
The spacebars syntax works... {{ momentify createdAt }}
This syntax does not... #{ momentify createdAt }
After reading some of the other issues, you probably would say that momentify createdAt is not a valid javascript definition, thus you don't want the jade compiler to support it, which I understand. (1) Is this correct?
However, this is not documented anywhere in your Readme. (2) For future users... I'd add a little note to the readme docs explaining this special case, since it was unclear since you mentioned you recommended using the #{ } jade syntax, thus, I figured it would be used interchangeably with the spacebars syntax.
Thanks!

@mquandalle thank you for this nice package. :+1:
May ask you to add explanation of this case in docs? You will save time for people who want to give a try to meteor-jade.

I'm referencing the following issues here, since I believe #98 is the first time this bug is mentioned and they all point to the same problem (my apologies if I missed one!):
#113
#122
#147
#153
#157
BTW, question 1 from the OP isn't actually solved by switching from #{momentify date} to #{momentify(date)}. The latter just prints that exact text instead of parsing it. The only way I can make it work is switching it to its spacebars equivalent: {{momentify date}}. HTH

There now exists a fork that seems to fix this issue: https://github.com/dalgard/meteor-jade

Yes, I've modified a fork of this package to support passing arguments to attribute helpers, together with a few other useful features. The fork has been released as dalgard:jade.
I will keep the new package in sync with the original, should there be any updates, and generally continue maintenance until, hopefully, the two packages can be merged.


Drop support for Python 3.7

Python 3.7 eol as 2023-06-27. According to SPEC 0, we recommend projects drop 3.9 in early October. I think we should support 3.8 and 3.9 a bit longer since we aren't a library and instead a developer tool. But I think dropping 3.7 now seems reasonable.

since we aren't a library and instead a developer tool.

I really like this phrasing and will use it for the pytest plugins, too (where I felt that dropping with the SPEC0 schedule was way too fast).


Disqus configuration for Firehose Community comments

@colinrubbert merge conflicts prevent me from pressing the button.

I'll take a look when I get back after lunch.

Resubmitting changes on another branch, closing this pull request.


[SPARK-38379][K8S]Fix Kubernetes Client mode when mounting persistent volume with storage class

What changes were proposed in this pull request?

Running spark-shell in client mode on Kubernetes cluster when mounting persistent volumes with a storage class results in a big warning being thrown on startup.
https://issues.apache.org/jira/browse/SPARK-38379
The issue here is there is a race condition between when spark.app.id is set in SparkContext and when its used, so change to use the KubernetesConf appId, which is what is used to set spark.app.id.
Why are the changes needed?

Throws big warning to user and I believe the label is wrong as well.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit test added.  The test fails without the fix.
Also manually tested on real k8s cluster.

Could you make a backport PR to branch-3.2, @tgravescs ?

Yep, I'll open one up.


add cluster fence state to the managed clusters

This will be used to fence and unfence a given managed cluster for the sync DR feature.

To be merged after #366


drawing toolbar doesn't hide when tab loses focus

superseded by https://github.com/lockbook/lockbook/pull/2280


request to be contributors

Hi,
I am a Phd student and working on few shot learning. This is an exciting project. Can i contribute for it? Although you have done a lot, there should be more we can do?

I found lots of meta learning methods have backbone networks like Conv32, conv64, resnet12 and resnet18 but details are a little bit different. For example, some have more layers, more filters than others.Maybe we can standardize it and integrate this part to torchmeta for fair comparison

Apologies for the very late reply. Any kind of help is very welcome, and thank you for volunteering!
I think having standard backbone networks here would be a great idea. If you add them, please include some previous papers that use them to keep track.
Another area that always requires more work is adding datasets. Some of which were suggested here #17.
I am closing this issue for now, but feel free to open other issues or PRs depending on what you want to add to Torchmeta.


vega2png, vega2pdf, .. CLI commands

for command line tools producing vega json commands such as vega2png could be useful to produce visualizations from piped input.
Something like this:
import sys
import altair as alt
from altair_saver import save
infile = sys.stdin() if sys.argv[1]=="-" else open(sys.argv[1])
chart = alt.Chart.from_json(infile.read())
save(chart,sys.argv[2])

curl http://... | vega2png - output.png would seem quite useful. Is this in scope for this package?

Why not use the command line tools directly?

do they already exist? if so I must have missed them


Replace node-fetch with isomorphic-fetch

As the title says

hy @pax-k
can i start work on this

I guess, the package has to force the use of node 18+
No issue for me, just pointing it out.

Created PR #506 for this.


[SYSTEMML-1098] Make file names direct hyperlinks in Downloads Page

make file names hyperlinks for direct download

-1
There is a requirement to go over the mirrors, and the script will help identify the closest mirror, etc... we should not have a direct link...

@lresende @jazares
I think this PR should be great if @jazares could replace the direct mirror links with the apache mirror links, by replacing the direct hosts with http://www.apache.org/dyn/closer.cgi/...

@lresende @deroneriksson removed the archive column and made file title a hyperlink to the mirrors page

@lresende @jazares
I validated that the download hyperlinks now go to the apache mirrors pages.
LGTM. I'll merge.

I created a new JIRA issue for this PR to address the consolidation of the name and archive columns. ([SYSTEMML_1100] Consolidate name and archive columns for download links)

@jazares BTW, sorry for the confusion, but would you mind renaming this PR to [SYSTEMML_1100] Consolidate name and archive columns for download links? 1098 is closed and I created 1100 to be more descriptive.

@lresende Looking back at the discussion, sorry for merging with the -1. The focus of the PR changed and I should have handled the change in a separate PR.

Thanks @jazares!


Failed to parse file:// in image markup

The following markup fail
![AAA](file://aaaaa)

https://github.com/markdown-it/markdown-it/blob/8.3.2/lib/index.js#L23-L40
That's indended for defaults. You should override validator:
var md = require('markdown-it')();
// example only, you may wish to keep `javascript://` etc links disabled
md.validateLink = function () { return true; };

I see thanks 👍


[FLINK-27892] More than 1 secondary resource related to primary

Creating the primary cache indexers using composite keys [name,namespace] in EventSourceUtils. Added a sample job to the comments to reproduce the issue: https://issues.apache.org/jira/browse/FLINK-27892.
Note: Added a one liner method to emphasise what we are doing, can be removed if needed.

cc @Aitozi

I agree it would be great to add some tests for this @morhidi . I know we didn't have tests before either but it's a bit concerning to be able to change such core logic without any test changes/failures.

Thanks folks, sure thing! Tho I'm off this week. I'll take care of this once I'm back next week.

@Aitozi @gyfora I ended up adding some extra e2e tests for multi namespace session job deployments. We don't have too much resources on a minikube cluster but I managed to squeeze in the 2 x (1 session cluster + 1 session job) we need here. PTAL

Thanks for the review @Aitozi. I also added a follow up for speeding up the e2e tests. https://issues.apache.org/jira/browse/FLINK-28059


What can I do to get the data just based on the request path?

What can I do to get the data just based on the request path?
Use the following path:
/ api / user? id = 1
I hope this path not to query, but directly return / api / user definition of the data.
Simply put, that is how to do to delete all the query parameters, pretending to get all the data?
All requests are masqueraded as get with the following code, but get also has the functionality of a query. What should I do to get request regardless of my query parameters?
server.use((req, res, next) => {
    // Converts POST to GET and move payload to query params
    // This way it will make JSON Server that it's GET request
    if (req.method != 'GET') {
        req.method = 'GET'
    }
}

怎么做才能只是根据请求路径获取数据？
使用以下路径：
/api/user?id=1
我希望这个路径不要去查询，而是直接返回 /api/user 定义的数据。
简单点说 就是怎么做才能删除掉所有的查询参数，伪装成获取所有的数据？
通过以下代码把所有请求都伪装成了get，但是get中还有查询的功能。我要怎么做才能让get请求不管我的查询参数呢？
server.use((req, res, next) => {
    // Converts POST to GET and move payload to query params
    // This way it will make JSON Server that it's GET request
    if (req.method != 'GET') {
        req.method = 'GET'
    }
}

已经用这种方式解决了
server.use((req, res, next) => {
    // Converts POST to GET and move payload to query params
    // This way it will make JSON Server that it's GET request
    if (req.method != 'GET') {
        req.method = 'GET'
        // 这句话不能要，否则报错。暂时不知道是什么原因，
        // 貌似把所有请求都伪装成get，其实在业务上来说已经抛弃了json-server提供的其他功能
        // 只是把这个作为数据源返回
        // req.query = req.body

    }
    req.query = {}
    if (req.url.includes('?')) {
        res.redirect(req.url.replace(/\?.*$/, ''))
        return
    }
    next()
})


Linux runtime error - libCHttpParser.so not found

0.11.3 was working, but with the changes in 0.11.4, the following run time error occurs:
./.build/debug/appname: error while loading shared libraries: libCHttpParser.so: cannot open shared object file: No such file or directory

Notes:

This app was built using the 'ibmcom/kitura-ubuntu:latest' docker image:
Linking in Xcode works fine.
This might be caused by the 'link "CHttpParser"' line in the module.modulemap

I just saw the resultion for issue #1.  The following docker line resolved the issue as you noted:
RUN swift build -Xcc -fblocks -Xlinker -rpath -Xlinker .build/debug


KOGITO-7909: kie-tools dependency review number one

JIRA: https://issues.redhat.com/browse/KOGITO-7909
Commits should be squashed.
Checking builds, but feel free to review if you know we need to keep some versions.

@domhanak Best way to revert changes to the pnpm-lock.yaml file is to run
git fetch origin
git checkout origin/main -- pnpm-lock.yaml
pnpm bootstrap

@tiagobento @yesamer fixed, let's wait for the builds

Upgrade of electron will be handled in separate JIRA.

Build failed because of:
2022-09-14T07:33:01.3281016Z [ERROR] Failed to execute goal on project dmn-dev-sandbox-quarkus: Could not resolve dependencies for project org.kie.kogito:dmn-dev-sandbox-quarkus:jar:0.0.0: Could not transfer artifact io.quarkus:quarkus-security-runtime-spi:jar:2.4.0.Final from/to central (https://repo1.maven.org/maven2): transfer failed for https://repo1.maven.org/maven2/io/quarkus/quarkus-security-runtime-spi/2.4.0.Final/quarkus-security-runtime-spi-2.4.0.Final.jar: Connect to repo1.maven.org:443 [repo1.maven.org/<IP_ADDRESS>] failed: Connection timed out (Connection timed out) -> [Help 1]

Build failed cos of test in online-editor:
✖  DMNGuidedTour.cy.ts

@yesamer @tiagobento :green_circle:


Add offline support to the API to make parsing events easier

When we receive events from a webhook, it is non-trivial to determine which GitHub instance the event came from
or for that matter even if the event actually came from GitHub or GitHub Enterprise.
In order to ensure that the logic for parsing events does not get replicated in clients, we need to be
able to call GitHub.parseEventPayload(Reader,Class) without knowing which GitHub the event originates from
and without the resulting objects triggering API calls back to a GitHub
Thus we add GitHub.offline() to provide an off-line connection
Thus we modify some of the object classes to return best-effort objects when off-line
Add support for more of the event types into GHEventPayload
Add tests of the event payload and accessing critical fields when using GitHub.offline()

@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


Display Altmetric badges on simple item view

Is your feature request related to a problem? Please describe.
In earlier versions of DSpace we had the ability to display Altmetric badges on item views based on an item's DOI or Handle (the dspace/config/modules/altmetrics.cfg configuration still exists in the DSpace 7 backend, though it is is not working).
Describe the solution you'd like
The ability to display Altmetric donuts on an item view based on the item's metadata. If the item has a DOI then it should be checked first, followed by the Handle. There are API endpoints for both types of identifiers, which return SVG images. In previous versions it was possible to configure the appearance of the badge (size, popup location, etc).
For example, see this DSpace 6 repository with both Altmetric and Dimensions badges:

(Bonus points for the closely related Dimensions.ai badge).

I've done a rudimentary implementation of this in a field component:

src/app/item-page/simple/field-components/specific-field/altmetric/item-page-altmetric-field.component.ts
import { Component, Input, AfterViewInit } from '@angular/core';

import { Item } from '../../../../../core/shared/item.model';
import { ItemPageFieldComponent } from '../item-page-field.component';

@Component({
  selector: 'ds-item-page-altmetric-field',
  templateUrl: './item-page-altmetric-field.component.html'
})
/**
 * This component renders an Altmetric badge.
 * It expects 1 parameter: The item
 */
export class ItemPageAltmetricFieldComponent extends ItemPageFieldComponent implements AfterViewInit {
  // Is this hacky? It feels hacky. I can't figure out any other way to load the
  // Altmetric embed.js *after* Angular finishes rendering the DOM.
  ngAfterViewInit() {
    // Altmetric embed.js
    import('./embed.js');
  }

  /**
   * The item to display metadata for
   */
  @Input() item: Item;

  /**
   * Helper function to extract the DOI itself from a URI. Should return the
   * DOI component for any variation of http, https, dx.doi.org, and doi.org.
   * @type {string}
   */
  parseDoi(doi: string) {
    const regex = /https?:\/\/(dx\.)?doi\.org\//gi;
    return doi.replace(regex, '');
  }

  /**
   * Helper function to extract the Handle itself from a URI.
   * @type {string}
   */
  parseHandle(handle: string) {
    const regex = /https?:\/\/hdl\.handle\.net\//gi;
    return handle.replace(regex, '');
  }
}

src/app/item-page/simple/field-components/specific-field/altmetric/item-page-altmetric-field.component.html

    <ds-metadata-field-wrapper [hideIfNoTextContent]="false">

                <ng-container [ngTemplateOutlet]="altmetricBadge"
                              [ngTemplateOutletContext]="{
                                                    itemDoi: item?.firstMetadataValue('cg.identifier.doi'),
                                                    itemHandle: item?.firstMetadataValue('dc.identifier.uri'),
                                                  }">
                </ng-container>

    </ds-metadata-field-wrapper>

<ng-template #altmetricBadge let-itemDoi="itemDoi" let-itemHandle="itemHandle">

</ng-template>

It works, but I am importing a static version of the Altmetric embed.js from the component. The component uses ngAfterViewInit to import the JavaScript after the div containing the DOI or Handle has been added to the DOM. A better implementation on par with DSpace 6 is welcome!
The result in our DSpace 7.6.1 repository is:

@sergius02 yes I've seen the same. I think it's because this method imports the Altmetric JavaScript and writes to the DOM after Angular has finished loading and saving the cached version of the page. When you navigate away from the page and back, the browser shows the cached version.
We need a more Angular-friendly solution eventually. Hopefully @arvoConsultores can think of something!

You're welcome, @sergius02. I am new to Angular so this was the best I could come up with. I thought I would share to help other people come up with something better! :smile:
Another thing that will be an issue is using a static import of embed.js. If Altmetric changes their script then we will be using the old one, which could create problems in the future.

do you know how to pop up the plumX metrics on dspace 7.5?


Start January 2023 - April 2023 Bugzilla Cycle

Hmm, the CI is failing with:
../../../.dub/packages/ae-0.0.3053/ae/utils/iconv.d(113,29): Error: Bidirectional control characters are disallowed for security reasons.

This doesn't seem to have anything to do with the changes in this PR.

cc @CyberShadow

https://github.com/dlang/dlang-bot/pull/299
Please rebase (and ping me again). Thanks!

@CyberShadow done

Thanks!


Bundler

Similar to #33 but is simplified to generate a type safe builder for any class that has an @InjectExtra annotation.
#33 only generates a class that will build an Intent for activities. Instead this generates a class that will build a Bundle (which can be used by Fragments, Activities, Services, POJOs).

Needs more tests.


Unable to deploy site to custom domain

I am unable to deploy open--this.site. I feel it has to do something with the domain having the 2 dashes. It throws  Error! The supplied domain is invalid (400), I have added nameservers to godaddy

I recently touched the custom domain of Punycode (IDN). This is the domain starting with "xn--".
But I have not encountered any problems.
For example: https://github.com/fu-sen/xn--ck8hk4b.tk to https://🎈😍.tk/
It is possible that a problem different from the domain is occurring.
Have you tried with a simple file structure?

Closing since this doesn't seem to be a problem any more.


TST: Implement unit tests

[x] create test subdirectory in package subfolder
[x] add testing to GitHub workflow yaml

Write basic tests for each function:

[x] magfetch
[ ] magfetchtgo
[ ] magdf
[ ] magfig
[ ] magspect
[ ] wavefig

[ ] test that the function succeeds at the thing it's supposed to do with default inputs
[ ] test that the function succeeds using all potential alternative inputs
[ ] check that the errors are raised and have the right messages in the right places
[ ] check that the logging/print statements occur at the expected times


[CSS Bug]: Highlighted gap should be reduced in image to pdf page

Installation Method
Docker
The Problem

Version of Stirling-PDF
0.28.3
Last Working Version of Stirling-PDF
No response
Page Where the Problem Occurred
http://localhost:8080/img-to-pdf
Docker Configuration
No response
Relevant Log Output
No response
Additional Information
No response
Browsers Affected
Chrome
No Duplicate of the Issue

[X] I have verified that there are no existing issues raised related to my problem.

Hi,
would like to fix this with #1860 and #1859

sounds good!


cap_set_file not permitted

Running a Centos7 container (669aa1973610) I'm getting below error when trying to install httpd.
This seems to be identical to the docker issue at https://github.com/docker/docker/issues/6980
Unfortunately, in that issue they blame aufs and suggest using btrfs.
However, I am already running btrfs.
I have no idea how to troubleshoot this further. Any advise is welcome.
[root@server ~]# yum install httpd
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.netnitco.net
 * extras: centos.netnitco.net
 * updates: centos.netnitco.net
Resolving Dependencies
--> Running transaction check
---> Package httpd.x86_64 0:2.4.6-31.el7.centos.1 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

==============================================================================================================================================================================================
 Package                                  Arch                                      Version                                                  Repository                                  Size
==============================================================================================================================================================================================
Installing:
 httpd                                    x86_64                                    2.4.6-31.el7.centos.1                                    updates                                    2.7 M

Transaction Summary
==============================================================================================================================================================================================
Install  1 Package

Total download size: 2.7 M
Installed size: 9.4 M
Is this ok [y/d/N]: y
Downloading packages:
httpd-2.4.6-31.el7.centos.1.x86_64.rpm                                                                                | 2.7 MB  00:00:02
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : httpd-2.4.6-31.el7.centos.1.x86_64                                                                                1/1
Error unpacking rpm package httpd-2.4.6-31.el7.centos.1.x86_64
error: unpacking of archive failed on file /usr/sbin/suexec: cpio: cap_set_file
  Verifying  : httpd-2.4.6-31.el7.centos.1.x86_64                                                                                1/1

Failed:
  httpd.x86_64 0:2.4.6-31.el7.centos.1

Complete!
[root@server ~]#

Is that an unprivileged container (security.privileged isn't set to true)?
If so, then that's most likely a kernel restriction as current upstream kernel doesn't allow users to set fs capabilities. @hallyn started doing some design work to fix that upstream.

Yes, this is indeed an unprivileged container.
Thanks for the explaination. I will await the upstream fixes.

What's the workaround for this?
I tried lxc config set centos7 security.nesting true but still get this error message:
  Installing : httpd-2.4.6-40.el7.centos.1.x86_64
Error unpacking rpm package httpd-2.4.6-40.el7.centos.1.x86_64
error: unpacking of archive failed on file /usr/sbin/suexec: cpio: cap_set_file
  Verifying  : httpd-2.4.6-40.el7.centos.1.x86_64

Failed:
  httpd.x86_64 0:2.4.6-40.el7.centos.1

On Sat, Jul 16, 2016 at 01:13:28PM -0700, Kai Stian Olstad wrote:

What's the workaround for this?
I tried lxc config set centos7 security.nesting true but still get this error message:
  Installing : httpd-2.4.6-40.el7.centos.1.x86_64
Error unpacking rpm package httpd-2.4.6-40.el7.centos.1.x86_64
error: unpacking of archive failed on file /usr/sbin/suexec: cpio: cap_set_file

Currently there is no workaround for this.  You cannot set file capabilities
from a user namespace other than the initial one.

Verifying  : httpd-2.4.6-40.el7.centos.1.x86_64
Failed:
httpd.x86_64 0:2.4.6-40.el7.centos.1

---
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/lxc/lxd/issues/1245#issuecomment-233148823

Until the kernel supports unprivileged fs capabilities you need security.privileged set to true which should then fix your problem, at the cost of much degraded container security.

Of course security.nesting != security.privileged.
lxc config set centos7 security.privileged true did the trick.
Thank you @stgraber

Is it a reasonable workaround to set the container to privileged, install httpd, and then set it back again?

On Fri, Oct 14, 2016 at 02:46:11AM -0700, Brian Candler wrote:

Is it a reasonable workaround to set the container to privileged, install httpd, and then set it back again?

You may then need to change the file ownerships afterward, but sure.  Or
it may be easier to just create a private package which skips the
filecaps, install that, then set the filecaps from the host.
Fwiw I'm supposed to give an update on this at the plumbers containers
track so there's a chance I'll whip up a new patch before then, and
maybe we can get something agreed on by the end of the year :)

Does anybody know if a kernel patch exists or if someone is working on it?
I'm running into similar problems when running yum update in a CentOS 7 container:
Running transaction
  Updating   : filesystem-3.2-21.el7.x86_64                                                                                1/4
Error unpacking rpm package filesystem-3.2-21.el7.x86_64
error: unpacking of archive failed on file /proc: cpio: chown
  Updating   : iputils-20160308-8.el7.x86_64                                                                                2/4
Error unpacking rpm package iputils-20160308-8.el7.x86_64
error: filesystem-3.2-21.el7.x86_64: install failed
error: unpacking of archive failed on file /usr/bin/ping;5877ab33: cpio: cap_set_file
filesystem-3.2-20.el7.x86_64 was supposed to be removed but is not!
  Verifying  : filesystem-3.2-20.el7.x86_64                                                                                1/4
iputils-20121221-7.el7.x86_64 was supposed to be removed but is not!
  Verifying  : iputils-20121221-7.el7.x86_64                                                                                2/4
  Verifying  : iputils-20160308-8.el7.x86_64                                                                                3/4
  Verifying  : filesystem-3.2-21.el7.x86_64                                                                                4/4

Failed:
  filesystem.x86_64 0:3.2-20.el7                    filesystem.x86_64 0:3.2-21.el7                    iputils.x86_64 0:20121221-7.el7                    iputils.x86_64 0:20160308-8.el7

Complete!

Is there really no better workaround?

@hallyn has a working patchset as far as I know.

Yes, see this thread https://lkml.org/lkml/2016/11/19/158

This is finally fixed upstream in Linus' kernel (not yet available in distro kernels, I assume).

Thanks for the update. Is this the commit? https://github.com/torvalds/linux/commit/8db6c34f1dbc8e06aa016a9b829b06902c3e1340

Yup.

is there really no better workaround?

Just because I'm root on host and both host and container are cenots 7 , I just did chroot to container's fs and yum update - it installed iputils in centos 7 container without need to comment out
lxc.cap.drop = mac_admin mac_override
setfcap
in centos.common.conf
and container restart :-)

is there really no better workaround?

Just because I'm root on host and both host and container are cenots 7 , I just did chroot to container's fs and yum update - it installed iputils in centos 7 container without need to comment out setfcap in
lxc.cap.drop = mac_admin mac_override setfcap
in centos.common.conf
and container restart :-)

This did not work for me at all, in fact, it made the filesystem read-only.


set ROOT_PATH env as relative path for running on the api gateway (such as KONG)

Feature Request
There is a need for an env variable so that when we run langflow using docker-compose, it executes on a relative path. for example :
ROOT_PATH=/my-dynamic/path/
Motivation
like this :
https://localhost:7860/my-dynamic-path/
Your Contribution
No response

I think you need Custom API endpoints
https://docs.langflow.org/configuration-api-keys#custom-api-endpoint

@nabrgm Thank you for answering.
I want it to run on this path when I run langflow by docker-compose : http://mydomain.com/khoshgoftar/langflow
and I want it to be dynamic so I can run multiple instance of it.
`version: "3.3"
services:
langflow:
image: langflowai/langflow:latest
ports:
- "7864:7860"
depends_on:
- postgres
environment:
- ENDPOINT=/khoshgoftar/langflow/
volumes:
  - langflow-data:/app/langflow

volumes:
langflow-data:`

If you have a VPS you can modify your setup to use Nginx as a reverse proxy to handle the path rewriting and forwards requests to the appropriate service.
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/

I use KONG API Gateway but I have the same issue, the css and js files are loaded from the root domain path.


Any guide on tuning performance of XGBoost-on-YARN?

i have my Spark cluster of two nodes with 64+88 cores and 128+128G memory. my xgb training data is around 14G.
for now, i mainly tuning these parameters:

spark.executor.memory
spark.executor.instances
spark.executor.cores
spark.task.cpus
spark.yarn.executor.memoryOverhead
spark.storage.memoryFraction
spark.driver.memory
nthread
but no matter how i tried, i just can't fully utilise all the cores. best scenario, all cores were used but with around 50% usage.
can anyone give me a detailed guide on how to tuning the performance and maybe show me the best performance i can get? appreciate it!

Please check the documentation


Can't Build with Carthage

Added Alamofire.framework to Link Binary With Libraries
created a Run Script
/usr/local/bin/carthage copy-frameworks
Input Files:
$(SRCROOT)/Carthage/Build/iOS/Parse.framework
$(SRCROOT)/Carthage/Build/iOS/Bolts.framework
$(SRCROOT)/Carthage/Build/iOS/Alamofire.framework
(Was using Parse before and everything was fine, but could not build as soon as I added Alamofire)
Also, frameworks search paths are:
$(inherited)
$(PROJECT_DIR)
$(SRCROOT)/Carthage/build/iOS
Using Swift 3.0
Xcode version 8.1 and Deployment Target is iOS 9.0
Carthage is on the latest version
Xcode displays this message when i try to build my previously working project:
ld: framework not found Alamofire
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Hi @bschron,
I'd suggest you open a question on Stack Overflow and tag alamofire. We use our GitHub project for bug reports and feature requests.
Best of luck! 🍻

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.


[Bug]When the numbers are passed in the row object for insert scenario the numbers are right aligned in the Google sheets

Description
Release Environment - It is observed that when the numbers are passed in the row objects for insert scenario then the numbers are right aligned in the Google sheet
Expected Result
Numbers should be left aligned in Googlesheet
Actual Result:
Numbers are right aligned in the Googlesheet
Steps to reproduce the behaviour:
1.launch Appmsith app in the release environment
2.Expand API and Click on Googlesheet
3.Click on Add new Datasource and configure Email
4.Copy existing spreadsheet url, sheet name , column and values
5.click on 'New Query'
6.Choose the method as 'Insert' , 'Bulk Insert, 'Update' or 'Bulk update'
7.Pass the spreadsheet url which is noted at step 4
8.Pass the sheet name which is noted at step 4
9.Pass the following row object based on the column and values which are noted at step 4
[{
"FirstName":"Yogesh",
"LastName":"J",
<EMAIL_ADDRESS>"Phone":"9952563100"
},
{
"FirstName":"Yogeshh",
"LastName":"JJ",
<EMAIL_ADDRESS>"Phone":"7550245695"
},
{
"FirstName":"Yogeshhh",
"LastName":"JJJ",
<EMAIL_ADDRESS>"Phone":"7550245123"
},
{
"FirstName":"Yogeshhh",
"LastName":"JJJ",
<EMAIL_ADDRESS>"Phone":"9952563200"
}]
10.Click on Run and verify the success message
11. Open the Google sheet and observe the values
Important Details

Version: [14.0.3 (166<IP_ADDRESS>.7)]
OS: [MacOS Big Sur 11.2.3]
Browser [S
<img width="1280" alt="Screenshot 2021-04-22 at 2 31 42 PM" src="https://user-images.githubusercontent.com/35128442/115697172-f1a20280-a380-11eb-819c-e946e26c6d48.png"
afari]

Modifying the scope for this a little bit. The behaviour that is seen is that during inserts and updates, the operations respect sheet formatting. But during create sheet, there is no formatting present for reference, and hence everything is treated as a string.
Will need to check if there is any default formatting that can be relied on. Basically it's create spreadsheet that needs to be updated here.


Prompt workspace picker if file does not exist

The URI of the text editor does not a valid for sometimes.
For example, an edamagit view uses status.magit as the uri.
In those cases, this patch shows a picker to choose workspaces rather than showing some invalid paths.
https://github.com/user-attachments/assets/8c0d6bcc-2b09-47b4-8b05-5bd0510f1547

@ytakhs Could you review this? Thanks!

@ytakhs Thank you for merging this. Could you release a new version of the extension?

@garaemon I've published it, so please give it a try!

@ytakhs Thank you! I confirmed that the latest version works as I expected.


Adding swipeLeft action on UiObject

Adding swipeLeft() action on UiObject.

This will be available in 0.3.1-SNAPSHOT after the next Travis build.


Your connection is not private

Not working : NET::ERR_CERT_COMMON_NAME_INVALID

I got this error when I tried to create certificate for *.local domain.
mkcert is already providing a  warning for this.
Warning: many browsers don't support second-level wildcards like "*.local"
I regenerated again without *.local and this error went away.

That's indeed the only case I'm aware of, if anyone encounters the error in other cases, please provide more details in a new issue.


Merge changes from 'staging' to 'main' (PR #195)

Change Summary
Summarise your changes in points

This PR includes changes from staging PR: https://github.com/ujala-singh/github-repository-dispatch-receiver/pull/195"

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code refactoring (restructuring existing code without changing any functionality)
[ ] This change requires a documentation update

Documentation/Release Plan

Problem Statement doc
Feature documentation
Release plan

Testing Checklist
Changes tested on

[ ] development
[ ] production
[ ] MABL Tests Link (if any)
[ ] Successful Workflow Links (if any)

Hey @ujala-singh, your main branch PR has been automatically created. In order to merge the PR, Please test your changes on staging (pre-prod) and update the change summary and checks accordingly.

/rebase


Add mkdocs developer docs generation

Sample docs hosted: https://ehrenb.github.io/androguard/

added docs directory containing README.md and requirements.docs.txt for building MKDocs documentation.

This implicitly generates API documentation for all py files in the project.
This expects Sphinx-style docstrings
Markdown can be used within each docstring to render intra-project links (such as functions from other Androguard modules)
Added basic contribution page in the docs
Future improvements:  Docs versioning (based on Androguard tag), porting usage examples from original RTD, ...

Fixes https://github.com/androguard/androguard/issues/1094

Refer to https://github.com/androguard/androguard/issues/988 for discussion.

@erev0s could we add a simple mkdocs build as a CI test to ensure the docs successfully build? the test will also need to install the requirements.docs.txt

great work @ehrenb !


add a browserdriver parameter in project and suite level

currently, user can only set browser driver in test case. that will become annoying if user wants every test case run in same browser for whole project or suite.
solution is to add a optional parameter in both project and suite xml tag to let user simplify the job.

I have just implement a way to transmit testproject/testsuite parameters into test case container.
refer to this commit for details.
https://github.com/bigtester/automation-test-engine/commit/69758ba47ef9005f08e65dd2eb8afda8b233726c


wasm-gc: remove package

The upstream repository has been archived, with a note that this should never be needed:
https://github.com/alexcrichton/wasm-gc
It also happens to have custom patch logic that will fail the newer cargo
verification in #79975

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@ekleog what do you say?

I kind of disagree with the argument that wasm-gc is now unnecessary (the rust compiler is not the only one), but my use case is indeed solved without it now, I don't know how many other users of it there are nowadays, and the repo is archived and thus officially unmaintained… so I'm totally ok with removing this from nixpkgs!


Inability to Use Ctrl+C to Interrupt a Vue Project in VSCode Terminal on macOS

Hello,
I am encountering an issue with Visual Studio Code (VSCode) on my macOS system. When I open a terminal within VSCode (version 1.91.1) and start a Vue project, I can see the progress percentage. However, during the startup process, I attempted to use the Ctrl+C shortcut to interrupt the operation, but found that it was not possible. The only way to stop the process was by right-clicking and selecting "Terminate".
I am running macOS Sonoma 14.5 on a 2019 Intel CPU MacBook Pro 16-inch. Is this a bug, or is there another way to interrupt the process using a keyboard shortcut? I would appreciate any assistance you can provide in resolving this issue.
Thank you for your time and attention.

/duplicate #184713


adjust tlim of restarted simulation

It would be useful to run a simulation longer than it was originally programmed to by increasing tlim on restart.

This can be done already by
bin/athenapk -r restart.final.rhdf parthenon/time/tlim=10


Merge warnings slash command

/merge_warnings

Also - the issue for this feature #88 says "a merge option", not a separate command. The command to transfer warnings already exists, it would be cleaner to make it an option on that command.

Oh.

Check on the "Files changed" tab of the PR, your changes and then changes back have screwed with the indentation

For some reason VS and stuff can be quite finicky with stuff like these. It showed a Unicode format prompt or something.

If it was line endings, make sure to set those to LF always.
Unicode, I'm not too sure about.
Probably best at this point to reset/rebase your branch and copy/paste your merge option back into it.

From what I've seen in GH Desktop, it says that it got reverted.

Didn't work for me. it just did a force traansfer:

Oh, it works for me. Lemme check if there is anything wrong with it.

I checked it again and turns out I deleted the wrong key (facepalm)

Should work as intended now

Oop I forgot to update the title so the merge commit has a weird title, oh well

Oop I forgot to update the title so the merge commit has a weird title, oh well


problem with make

I install all the dependency to install polybar (cmake cmake-data libcairo2-dev libxcb1-dev libxcb-ewmh-dev libxcb-icccm4-dev libxcb-image0-dev libxcb-randr0-dev libxcb-util0-dev libxcb-xkb-dev pkg-config python-xcbgen xcb-proto libxcb-xrm-dev i3-wm libasound2-dev libmpdclient-dev libiw-dev libcurl4-openssl-dev), but when I install with make i get this error

I can't find what are missing, I think is a problem of xcb library or there is a bug in your make file.

Please see, if this fixes your issue:
https://github.com/jaagr/polybar/wiki/Compiling#version-mismatch-between-xcb-proto-and-libxcb-randr0-dev
On Sun, Sep 17, 2017, 22:09 GabrielePuliti<EMAIL_ADDRESS>wrote:

I install all the dependency to install polybar (cmake cmake-data
libcairo2-dev libxcb1-dev libxcb-ewmh-dev libxcb-icccm4-dev
libxcb-image0-dev libxcb-randr0-dev libxcb-util0-dev libxcb-xkb-dev
pkg-config python-xcbgen xcb-proto libxcb-xrm-dev i3-wm libasound2-dev
libmpdclient-dev libiw-dev libcurl4-openssl-dev), but when I install with
make i get this error
[image: polybar]
https://user-images.githubusercontent.com/12409541/30524457-641337a0-9bf4-11e7-92af-d99c46be218b.png
I can't find what are missing, I think is a problem of xcb library or
there is a bug in your make file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jaagr/polybar/issues/761, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVqRpso7Qd-jR2JP8oVgp__uVDB6qo5ks5sjXxhgaJpZM4PaQw7
.

it works
thank you so much


[Question][Module Name] my data doesnt show on the dashboard can someone help me please

Question
im havin trouble getting my data to show un the dashboard, the data connection was a success but when i go to dashboard is not showing anything
Screenshots

when i inspect im getting those error messages and i dont know what to do please and thanks for your help

@DavidW1519  You can change this issue's type to bug, and provide more details about the version and your operations to help us reproduce it.

how to reproduce:

downloaded docker compose.yml and env.example from https://github.com/apache/incubator-devlake/releases ver 1.0.0 beta9
generated the encryption key with openssl and put it on the file .env
Run docker-compose up -d
go to http://localhost:4000 did the tutorial to connect to github
imported this https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel to my repository to make a test also made the token
after the tutorial i went to dashboard and nothing is showing so i press f12 and found this error

also tried what dosubot said but still not working


VSCode 1.86 doesn't work with stable Dev Containers extension

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.86.0
OS Version: MacOS 14.2.1

Steps to Reproduce:
The recent VSCode 1.86 stable release broke our devcontainer. Reloading the window gives the error bad option: --ms-enable-electron-run-as-node. This is likely the same as https://github.com/microsoft/vscode/issues/202096.
The workaround was to use a pre-release version of the Dev Containers extension, but it would be nice if the stable VSCode and stable Dev Containers extension would work fine.
I'm opening this issue here but feel free to move it to https://github.com/microsoft/vscode-remote-release/issues if appropriate.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Save versions (vscode, mac). Upgrading Dev Containers to v0.338.0 (pre-release) worked for me.

Thank you! Worked for me!

Make sure you are running Dev Containers v0.338.1 stable or later (recent pre-releases also work). This was caused by the stable version being released with some delay to VS Code 1.86, sorry for the inconvenience!

Still doesn't work, switching to pre-release version gives another error
[25965 ms] Start: Run in container: '/home/glue_user/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/bin/helpers/check-requirements.sh' [34476 ms] Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.24 Warning: Missing GLIBC >= 2.28! from /usr/lib64/libc-2.26.so Error: Missing required dependencies. Please refer to our FAQ https://aka.ms/vscode-remote/faq/old-linux for additional information. [34476 ms]  [34476 ms] Exit code 99 [34483 ms] Command in container failed: '/home/glue_user/.vscode-server/bin/05047486b6df5eb8d44b2ecd70ea3bdf775fd937/bin/helpers/check-requirements.sh' [34483 ms] Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib64/libstdc++.so.6.0.24 Warning: Missing GLIBC >= 2.28! from /usr/lib64/libc-2.26.so Error: Missing required dependencies. Please refer to our FAQ https://aka.ms/vscode-remote/faq/old-linux for additional information. [34484 ms] Exit code 99
docker image: amazon/aws-glue-libs:glue_libs_4.0.0_image_01
https://github.com/microsoft/vscode/commit/e2ce367fc8b433680b7abe7a649855578fc5344f
I found this recent change, before that access worked without problems
FAQ https://aka.ms/vscode-remote/faq/old-linux only returns error 503

I can confirm that's it is working for me now with v0.338.1 stable.

@lourivalcs Please see https://github.com/microsoft/vscode/issues/203967 for the error during server startup. The website appears to be back.

@rpolverini Please see above: https://github.com/microsoft/vscode/issues/203964#issuecomment-1921594165

Thanks @chrmarti  I can confirm that reinstall the new package again (1.86.0) and install the devcontainer extension v0.339.0 (pre-release) make work all again
Thanks for hyper quick response and actions on that!!

Closing as fixed. Thanks.

With reinstalling VS Code to 1.86.0 and DevContainers extension to v0.339.0 still there is an issue on MacOS.

The fix that worked for me is to downgrade VS Code to 1.85.2 and then use latest version of Dev Containers extension, which is v0.327.0.

@stanislavstoyanov99 We are working on a workaround for this for the upcoming 1.86.1 (https://github.com/microsoft/vscode/issues/204344).

VSCode broke itself on my machine on linux mint due to this. I still dont see the recommended steps about how to fix this. Everything looks up to date as far as I can tell.

Downgrade to 1.85.2 works for me!
warning: downgrading code from 1.86.2-1707854558 to 1.85.2-1705561292


Zooming the map by scrolling does not work as expected on Touchpad

Hi,
I have a touchpad that uses two finger inputs to scroll. Scrolling works in every other program. In Minutor, attempting to scroll will either do nothing, zoom in to a random zoom level, or zoom out to a random zoom level (including randomly jerking in and out across multiple zoom levels even if I am scrolling continuously on one direction on the touchpad).
This is on KDE Plasma (latest released version) on Linux. I believe my touchpad is using the xf86-input-synaptics driver.
Things I have tried:

Set up a script with xdotool to send one "scroll up" input every five seconds. This works. Minutor goes up one zoom level every five seconds.

Checked the inputs being sent to programs by the mouse driver with xev. If I scroll extremely slowly, I can get the touchpad to only send two scroll events at a time. I can't get it down to one. Note that scrolling extremely slowly does not seem to solve the problem with scrolling in Minutor.

If you don't immediately know how to fix this problem, or fixing it would create other issues, I think it would be nice to have some kind of keyboard input for scrolling as a around, and possible a zoom slider on the right of the screen as well, like the "layers" slider.

Mouse scroll wheel is ZOOM, so the behavior is intended.
Keyboard navigation is available. Just use the Cursor Keys.
You can also use modifier keys (like SHIFT ALT CTRL) to align to Chunks and whatever.

Mouse scroll wheel is ZOOM, so the behavior is intended.

Can you explain what you mean by "intended"? I understand that scroll is supposed to be zoom, but it's not functional as a zoom control for me, as I described in the issue.

Keyboard navigation is available. Just use the Cursor Keys.

Sorry, could you explain what "cursor keys" are? A search suggests you might be referring to arrow keys or the numpad cursor control keys (when enabled). Both of these pan the map for me, not zoom it. This issue is about the zoom function being broken for me, I'm going to edit the title to make that more clear.

Here is a short screencast of the problem. Although my mouse inputs aren't clearly visible, what I'm attempting to do is slowly zoom in using my touchpad. It doesn't work at all most of the time, then suddenly zooms in about 10x or so.
https://drive.google.com/file/d/1raQfAoZx0MDxzbtMiorZMuPkU4SlF35O/view?usp=sharing

Maybe I just misunderstood your explanation...
A next try with closer reading:

You have a computer with a touchpad. Most probably a laptop and not a touch-only device like a assumed before.
You use some sort of Linux operation system with KDE desktop
You use two-finger-gestures to scroll. This should be two fingers next to each other and moved up or down on the touchpad.
Somewhere in your software or configuration multiple scroll events are generated for just tiny movement of your fingers.

As far as I remember, I solved a similar issue some years ago. Therefore a question, do you use latest version of Minutor? Did you try with a self compiled version? (Latest release is very old).
There should be a Qt value we can query about the expected events per scroll wheel turn. I will look into that direction (no time immediately, more in the next weeks).

I'm compiling it, the one I was using when I opened this was https://github.com/mrkite/minutor/commit/57a47ff which is from the end of March. I'm trying to update to make sure the issue wasn't fixed, but I can't compile it at present. Bisecting reveals that https://github.com/mrkite/minutor/commit/c456e1d75dfc60a951d72d107616ec1ebffb6b62 introduced the problem. (Yes, I cherrypicked https://github.com/mrkite/minutor/commit/5d5a65ee753dcc182bce38338a42086915a891b1 to avoid that compilation issue.)
/usr/bin/ld: properties.o: in function `Properties::DisplayProperties(QVariant)':
properties.cpp:(.text+0xe8): undefined reference to `void PropertieTreeCreator::ParseIterable<QHash<QString, QVariant> >(QTreeWidgetItem*, QHash<QString, QVariant> const&)'
/usr/bin/ld: properties.cpp:(.text+0x1e7): undefined reference to `void PropertieTreeCreator::ParseIterable<QMap<QString, QVariant> >(QTreeWidgetItem*, QMap<QString, QVariant> const&)'

I'm on QT version 5.15.0. I can copy this into a new issue if you want.
I think it's worth noting that most of the time Minutor doesn't seem to react to my scroll events at all. The bug would be more understandable to me if it always zoomed in more quickly than I wanted because it was reacting to 2 scroll events instead of just one, but most of the time it seems to ignore them.

The QTWheelEvent delta() function is deprecated according to the current QT 5 docs. angleDelta() should be supported on all platforms, with pixelDelta() for some platforms (macOS is called out in the docs, with a mention that pixelDelta() is unreliable and driver-dependent on X11). Replacing delta() with angleDelta() seems to work for zooming with a mouse wheel under Windows in a quick local test, but I don't know how it will perform under other operating systems, or with a touchpad.
If that's not a viable fix, it looks like the page up/page down keys allow for keyboard zooming.

FWIW, I have the same issue on my MacBook: I cannot zoom. The "standard" mac touchpad gesture of pinching is not supported, and the "emulate scroll wheel by dragging two fingers" exhibit just the kind of jerky, random (and mostly non-working) behavior as @afontenot describes in the bug report.

FWIW, I have the same issue on my MacBook: I cannot zoom. The "standard" mac touchpad gesture of pinching is not supported, and the "emulate scroll wheel by dragging two fingers" exhibit just the kind of jerky, random (and mostly non-working) behavior as @afontenot describes in the bug report.

Can confirm that the latest version of Minutor (2.18.0) still suffers from this problem on macOS Monterey (12.1).  Seems to activate only if I do a harsh flick which then instantly zooms in or out to the max/min.
(I can, however, zoom reliably using FN-up/down cursors which makes it less of an issue for me.)

I can confirm the issue is as described by OP on an M1 MacBook Pro with macOS Monterey.
I have also found scroll-wheel input to be at best unpredictable with a Bluetooth-connected Razer mouse. Scrolling action only occasionally changes the view. Tilting the wheel (which is supposed to be an accelerated zoom) will zoom to max/min views.
I learned from the above comment that holding fn and using up and down cursor keys will zoom in and out. Also fn-left and fn-right will move the depth slider. This may be worth documenting in the README, especially if it holds true for Linux laptops.

Finally got around to fixing this myself. There might be multiple issues here, so testing (especially from anyone on macOS) would be appreciated. Note that until this is merged, you'll have to build from my tree.

I've tested the new builds on MacOS and this fixes the zoom issue. Zooming now works as expected with either touchpad or mouse wheel.
Could the same fix be implemented for the depth slider?

@bighairydave Could you clarify the issue you're seeing with the depth slider and file a separate issue for that if necessary? I don't have any problems with it (other than redraws being a little slow).

(other than redraws being a little slow)
-> a redraw after Depth Slider change has to process & render all data again, so it has to be slower than just panning.

Yeah, I didn't explain this well. The depth slider is fine, and redrawing is pretty much instant on this machine. The issue is that scrolling while holding shift doesn't move the depth slider as expected. I'm willing to bet that the fix is similar to the one for the zoom issue!

As I do not have any i-devices, could you all please describe what devices you are using exactly?
Maybe with link to a Wikipedia article about it.
(I even do not know whether you are talking about a phone or a computer)
And for those that are able to compile them self:
Please debug into MapView::wheelEvent(QWheelEvent *event)
and provide data of event when you are using your touchpad/mouse/whatever
and return values for:

QWheelEvent::pixelData()
QWheelEvent::source()