The "IsAndroid" parameter is not supported by the "XamarinDownloadArchives" task

I recently updated several NuGets and now when I try to build in Release mode for Android I get the following error messages:
MSB4064: The "IsAndroid" parameter is not supported by the "XamarinDownloadArchives" task loaded from assembly: Xamarin.Build.Download, Version=1.0.6646.18282, Culture=neutral, PublicKeyToken=null from the path: C:\Users\<me>\.nuget\packages\xamarin.build.download\0.4.9\build\Xamarin.Build.Download.dll. Verify that the parameter exists on the task, the <UsingTask> points to the correct assembly, and it is a settable public instance property. MSB4063: The "XamarinDownloadArchives" task could not be initialized with its input parameters.  Done building project "MyApp.Droid.csproj" -- FAILED
It looks like the issue may be in this page:
https://github.com/xamarin/XamarinComponents/blob/main/Util/Xamarin.Build.Download/source/Xamarin.Build.Download/Xamarin.Build.Download.targets
Thanks for looking at it.

I ran into this today too. I had two Android projects (app and lib) that referenced different versions of various Xamarin.GooglePlayServices.* nugets. This caused the library project to pull in Xamarin.Build.Download 0.4.9 and the app to pull in Xamarin.Build.Download 0.11.0, which caused the above error when you try to build it.
I found that deleting the 0.4.9 folder from the nuget/packages folder or adding an explicit reference to Xamarin.Build.Download 0.11.0 to the library resolved this.
Hope this helps!

Update Xamarin.Build.Download in iOS Project.

downgrade the "Xamarin.GooglePlayServices.Ads.Lite" to 122.3.0.


[2550] Added validation to prevent future dates for outcome

Context
Outcome date
Changes proposed in this pull request
Added validation to prevent future dates for outcome
Guidance to review
Put in a future date

 Don't allow future standards met date


Link broken in readme.md

The first link in the documentation section is broken

Hi!
Sorry about that, thanks for letting me know! It's because the repo changed name from Centurion to centurion. A simple fix is to change the C to be lowercase in the link. I'll make sure to fix this in v5.1 which I'm working on right now.
I hope that helps a little bit!

Hi!
Sorry about that, thanks for letting me know! It's because the repo changed name from Centurion to centurion. A simple fix is to change the C to be lowercase in the link. I'll make sure to fix this in v5.1 which I'm working on right now.
I hope that helps a little bit!

This has been addressed in the work-in-progress branch for version 5.1.0, thanks for your help!

This has been addressed in the work-in-progress branch for version 5.1.0, thanks for your help!


IBPCollectionCompositionalLayoutSolverResult is empty and crashed

uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 0 beyond bounds for empty array'

- (IBPNSCollectionLayoutItem *)layoutItemAtIndexPath:(NSIndexPath *)indexPath {
    NSArray<IBPCollectionCompositionalLayoutSolverResult *> *results = self.results;
    IBPCollectionCompositionalLayoutSolverResult *result = [results objectAtIndex:indexPath.item % results.count];
    return result.layoutItem;
}

I think #136 will resolve that issue


Add read-only bots display for teams

This PR adds a bots tab similar to the one in the chat infopanel which lists the bots and restricted bots in a team. There's a menu on each of these items, but it's not hooked up to anything yet - that'll come in a separate PR.

A lot of white space changes in here, does this pass prettier?

Ran prettier on my local machine a few times and it seems to!


docs(material/chips): remove docs-private from avatar and trailing icon

Removes the @docs-private tag from the chip avatar and trailing icon since they are public APIs. Internally the tag gets transformed into something which implies that they are private.

Currently they are, but they shouldn't be.


Send infura requests using secret

https://infura.io/docs/ethereum#section/Securing-Your-Credentials/Authenticating-using-a-Project-ID

closing for now—too difficult to coordinate with blocknative. will probably revisit later in the future


Improve docstrings of Raster.value_at_coords and Raster.interp_points, or merge the two methods.

Is your feature request related to a problem? Please describe.
See https://github.com/GlacioHack/xdem/issues/423 for the general context of this issue. Basically, the docstrings of Raster.value_at_coords and Raster.interp_points are so similar that it's very difficult to figure out which one to use.
@rhugonnet described it nicely:

I have a deadline today, will look in more details tomorrow.
Quick answer on your last question:
* The `value_at_coords` function extracts the closest point value to the coords or its average (any type of reductor function) within a square window of a certain size (doesn't require to load the entire Raster).

* The `interp_points` function performs a regular grid interpolation (nearest, linear, cubic) to extract the values at the coords.

More details in the examples: https://geoutils.readthedocs.io/en/stable/analysis_examples/index.html#point-extraction But, yes, we definitely need to change the names and improve the docstrings of those functions...

Describe the solution you'd like
I see two potential solutions for this:

Improve the docstrings to make them stand out more from each other. They could also refer to each other to be even clearer on the different use cases
Merge the two functions and make the interp_points extra functionality into a keyword argument.

Another point:
The docstring of Raster.interp_point regarding argument input_latlon is not clear enough. It's unclear whether the input coordinates should be given as (lon, lat) or (lat, lon). It currently says "Whether the input is in latlon, unregarding of Raster CRS".
According to the test suite, it looks like it is (lat, lon). This would need to be checked and clarified in the doc.


[Enhancement]:  Master typing -start/restart button functions need to upgrade

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
The letters should popup only after pressing start button and  the restart button should be named reset  because the button is clearing the timer and also the game's state.
Describe the solution you'd like

[ ] -  Launch the game application.
[ ]  - Navigate to the main menu or game interface where the start/restart button is located.
[ ]  - Attempt to click on the start or restart button.

Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Tasnuva12 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Update specs2-cats, specs2-core, ... to 4.10.2

Updates

org.specs2:specs2-cats
org.specs2:specs2-core
org.specs2:specs2-matcher
org.specs2:specs2-matcher-extra
org.specs2:specs2-scalacheck

from 4.10.0 to 4.10.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

labels: library-update, semver-patch

Looks like we broke mergify when we integrated scalafix.


Exercise 3

Draft pull request with the rendered notebook for ease of comments.
Once we are happy with the structure and scope I will create the snippets and remove the output before we merge.

[x] Add snippets
[x] Update filepath for the cloud
[x] Test on cloud 23.0
[ ] Remove output

Looks good to me.  No need to add further material, it's quite complete and comprehensive as is.

Made changes.  If everyone is happy I'll strip the output and then merge.


Upgrade mapnik to 1.4.15-cdb8

Stuff that depends on node mapnik:

windshaft

abaculus
tilelive-bridge

mapnik-pool

tilelive-mapnik

I'd like to merge this, close and tag this version 1.19.1 (and open a new stub one) and proceed with the changes and deploy of windshaft-cartodb. Can I proceed, @rochoa ?

Thanks a lot @rafatower !!! ❤


Add Compression capability for the file transport

Add the zippedArchive attribute, which is set to true will compress the previous (not the current) files. Since log files tend to have a pretty good compression rate this will result in an ability to save much more file / time frames.

Cherry-picked. Thanks!


Update README.md

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Completed my first pull request practise on EddieHub community

Completed my first pull request practise on EddieHub community


SE Config can be created from MP Config

Environment variables were not honored correctly - now we use MP config as the implementation and we have an SE config implementation fronting it when creating SE config from MP Config.
Resolves #2059

Looks like there are a few test failures and a SpotBugs issue to address.
As for the implementation, I understand and agree with the overall approach, but can't really provide much feedback on the actual implementation.


feat: run region

Summary
Support #222
Testing
Select Run Region from context menu, see correct SAS code block where current cursor/selection belongs run.

1.Make sure there are no regression issues
2.Verify that it can run region (SAS code block where current cursor/selection belongs) successfully.
3.Verify that ‘Run region’ works well if the current cursor positions between two blocks
4.Verify that ‘Run region’ works well if the current cursor positions in the first or last empty line
5.Verify that ‘Run region’ works well if trying to select multi-code blocks
6.Verify 1~5 in OS: Windows and Mac
7.Verify 1~6 in NLS environment

Try to run the same region, it has error in VSC SAS Extension.  It works well in SASStudio.


Switch to new default view

The goal is to emphasize the cities with no mandates (citywide and all uses).

[x] Default have "No parking requirements" toggle ON
[x] Move toggle into filter popup
[ ] Add city counter (position where toggle used to be)
[ ] Move filter/gear button next to city counter
[ ] Adjust search bar to length
[ ] Update tests

Pushed to production. Great job @tunglinn!


Modality dropout

I found that the accuracy will decrease when using modality drop out. Does it require longer training iterations when using this trick?

there is no relation about the training time
the reason is that  modality dropout will test all possible input combinations and calculate their average accuracy as output.
for a special input combination the performance would increase
---- Replied Message ----
| From | @.> |
| Date | 10/23/2023 13:00 |
| To | @.> |
| Cc | @.***> |
| Subject | [shicaiwei123/MMANet-CVPR2023] Modality dropout (Issue #4) |
I found that the accuracy will decrease when using modality drop out. Does it require longer training iterations when using this trick?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

In the testing phase, it is not possible to obtain all different modal combinations, only specific modal combinations, so how can the average accuracy be obtained?


No way to list directory itself rather than its contents

Expected behavior
In "regular" ls, there is a -d flag:
       -d, --directory
              list directories themselves, not their contents

I often find this useful when checking ownership and permissions. I suspect it might be impossible to show file metadata for the root directory with lsd without this flag, i.e. lsd -l / shows the contents of / not the directory itself.
Here's the behaviour I would expect:
$ lsd -ld src
drwxr-xr-x  gavin  staff       -   Tue Apr 23 16:17:38 2019    src

Here's the behaviour of /bin/ls on Ubuntu 18.04:
$ /bin/ls -ld /
drwxr-xr-x 24 root root 4096 Apr  3 17:53 /

Actual behavior
$ lsd -ld src
error: Found argument '-d' which wasn't expected, or isn't valid in this context

USAGE:
    lsd --long

For more information try --help

I am new to this codebase, but I have some, er, rusty experience with Rust. If someone has ~1h to spare, I'm interested in pairing to add this flag.

20c83e14e031328a3ca31b389cc3606a0e90a087 has argument parsing. A slightly tricky question is how does -d behave in relation to --tree, --recursive, etc. My approach is to say it conflicts and sidestep the question. The data model in Flags does not prevent such impossible states, however.

Hey @allenap , you can ping me if you need help with the codebase.
What I am thinking is we could probably just add another value for Display flag here https://github.com/Peltoche/lsd/blob/c4505e61f8626e1b5b2aab88b923f8e0381b2a05/src/flags.rs#L133.
Something like DirOnly maybe.
And we could check for the flag and get only the directory inside this function https://github.com/Peltoche/lsd/blob/c4505e61f8626e1b5b2aab88b923f8e0381b2a05/src/meta/mod.rs#L43.


Jupyter Notebook Support Cannot Find Correct Conda Environment

Hi,
My Jupyter Notebook cannot find the correct conda environment when used in VS Code.
Specifically, when running Jupyter Notebook via VS Code, Python always finds packages in the base conda environment, no matter which environment is selected.
Please see the following details:
In the bottom left of VS Code, the python version and the name of the conda environment is shown to be:

However, the Jupyter Notebook is actually run in the base environment, whose python version is 3.6.6:

What is more strange is, I can get the correct environment name using the following codes (in the same notebook file):

which is consistent with what is shown in the bottom left of VS Code.
When run in a terminal, the above codes will all give correct outputs:

Hope you can help me. Thank you very much!

Reload Python Extension works for me.

Thanks!


Fix: typo in typography header comment

"pattenr" corrected to "pattern". :1st_place_medal:

@dhaspden Thank you :)


fix: Remove (CITATION?). Currently, these results are not published a…

…nywhere

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

Thanks for the fix @mseeger! And thanks for reporting this @ystein!


Adding Helper Function To Support Wildcards With Specific Path Matching

to: @airbnb/streamalert-maintainers
cc: @ryandeivert
size: small
Background
Needed to support the use of path specific wild carding. See difference between fnmatch() and PurePath().match() below.

Changes

Added path_matches_any() to helpers/base.py
Added unit testing for path_matches_any()

Testing
Local Unit Testing
$ nosetests -s -v ~/repos/streamalert/tests/unit/stream_alert_rule_processor/test_rule_helpers.py
nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
Helpers - Path Matches Any ... ok
Helpers - Starts With Any ... ok
Helpers - Starts With Any ... ok
Helpers - Contains Any ... ok
Helpers - Matches Any ... ok
Helpers - Last Hour ... ok
Helpers - Fetch values from a record by normalized type ... ok
Helpers - Loading valid JSON ... ok
Helpers - Loading invalid JSON ... ok

----------------------------------------------------------------------
Ran 9 tests in 0.002s

OK

Coverage remained the same at 97.617% when pulling 24af35a05ababbcffe691af9a9d3ebe6ca2d5845 on jbussing_add_path_matches_helper_function into cf93a662d9f1f0b0d7a21aa40f74386f8a0bda1d on master.


4.4 final: multiple addresses found

Just wanted to let you know I tried this on 14.4 Final but arm64e IDSProtoKeyTransparencyTrustedServiceReadFrom appears to have found multiple addresses, see below. I tried using the first one, but messages were not coming through.
$ uname -a
Darwin Mackey.local 23.4.0 Darwin Kernel Version 23.4.0: Wed Feb 21 21:45:49 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6020 arm64

$ ./find_fat_binary_offsets.py /System/Library/PrivateFrameworks/IDS.framework/identityservicesd.app/Contents/MacOS/identityservicesd
-= Universal Binary Sections =-
Architecture 0 (x86_64):
  CPU Type: 16777223 (0x1000007)
  CPU Subtype: 3 (0x3)
  CPU Subtype Capability: 0 (0x0)
  Offset: 0x4000 (Valid Mach-O Header: Yes)
  Size: 8880384
  Align: 14
Architecture 1 (arm64e):
  CPU Type: 16777228 (0x100000c)
  CPU Subtype: 2 (0x2)
  CPU Subtype Capability: 128 (0x80)
  Offset: 0x880000 (Valid Mach-O Header: Yes)
  Size: 9865136
  Align: 14

-= Found Symbol Offsets =-
Offset of _IDSProtoKeyTransparencyTrustedServiceReadFrom in architecture x86_64: 0x0d6715
Offset of _IDSProtoKeyTransparencyTrustedServiceReadFrom in architecture arm64e: 0x0c0b84

-= Found Hex Offsets (with pure python fixed sequence search + regex) =-
Architecture 0 (x86_64):
  IDSProtoKeyTransparencyTrustedServiceReadFrom: 0xd6715
  NACInitAddress: 0x557cd0
  NACKeyEstablishmentAddress: 0x537d10
  NACSignAddress: 0x54b000
Architecture 1 (arm64e):
  IDSProtoKeyTransparencyTrustedServiceReadFrom: 0xc0b84; 0x2f5d0c; 0x322dac; 0x33a660
  NACInitAddress: 0x4c2468
  NACKeyEstablishmentAddress: 0x4afccc
  NACSignAddress: 0x489ed8

By the way, thanks for making this utility!!

identityservicesd-14.4-final.zip

@matusfaro Thanks for the heads up.
The tool actually has 2 methods for trying to get the offsets for IDSProtoKeyTransparencyTrustedServiceReadFrom, the 'hex offsets' (which unfortunately often doesn't get a unique match), and the 'symbol offsets' (which is pretty much always guaranteed to be correct due to the nature of how it works).
I would suspect if you use the offset value from the 'symbol offsets' it should work for you (arm64e: 0x0c0b84), but given that seems to match the first offset listed in the 'hex offsets' section, and you said that didn't work, then I'm not too sure what the issue is without digging deeper into it unfortunately.

identityservicesd-14.4-final.zip

⇒ sha256sum samples/macos-14.4-final-sonoma-identityservicesd
b82c5c6c9010a42cb64397e3760dd31144cbd471126111de9bb27fa3d2d2639a  samples/macos-14.4-final-sonoma-identityservicesd


Issue #580: Changes BubbleSort Algorithm to generic

What does this PR do?
Deletes previous bubble_sort.java and adds new algorithm that sorts all generic Datatypes.
Test Plan
This a basic test conducted by me.
PS H:\GitHub\Ultimate-Java-Resources\Sorting> cat .\BubbleSort.java
package Sorting;

import java.util.Arrays;

/***************************************************
 * Sorts a array through BubbleSort.
 *
 * @author https://github.com/AkMo3
 *
 **************************************************/
public class InsertionSort<E extends Comparable<E>> {

  public static void main(String[] args) {
    String[] a = {"Sachin", "Virat", "Bhuvi", "Jadeja", "Rohit", "Ashwin"};
    sort(a);
    System.out.println(Arrays.toString(a));
  }

  /**
   * Main method to sort the required array.
   *
   * @param a - array that is to be sorted.
   */
  public static void sort(Comparable[] a) {
    for (int i = 0; i < a.length - 1; i++) {
      for (int j = 0; j < a.length - 1 - i; j++) {
        if (greater(a, j)) {
          swap(a, j);
        }
      }
    }
  }

  /**
   * Method to check whether element greater than the next.
   *
   * @param array - The array that is to be sorted.
   * @param index - index of position that is to be compared.
   */
  private static boolean greater(Comparable[] array, int index) {
    return array[index].compareTo(array[index + 1]) > 0;
  }

  /**
   * Method to swap positions of array.
   *
   * @param array - array in which array that is to be sorted
   * @param index - index that is to be swaped
   */
  private static void swap(Comparable[] array, int index) {
    Comparable temp = array[index];
    array[index] = array[index + 1];
    array[index + 1] = temp;
  }
}
PS H:\GitHub\Ultimate-Java-Resources\Sorting> java .\BubbleSort.java
Note: .\BubbleSort.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
[Ashwin, Bhuvi, Jadeja, Rohit, Sachin, Virat]

Steps to test-

Create a new Generic Array in the main class.
Import this class in your code.
Call "sort" function from the above class and sort the array.
Check if the array if sorted or not.

Related PRs and Issues
Closes: #580
Have you read the Contributing Guidelines?
Yes

@dubesar Review this PR


"Important News" widget

The "Important News" widget should allow a message to stick-out on the widgets column
Requested:

Widget that is on top of all other widgets
Content of the widget is visible on the content part of the index page for small devices

Implemented


Fix warnings in POM files

Does not compile yet. I suspect that the latest snapshots of the uno.informatics libraries have not been deployed to Sonatype.


[BUG] Lombok tries to apply an extension method to a wrong type

I use @ExtensionMethod annotation to add some methods to collections.
I declare an extension method filter() for List<T> but Lombok tries to apply this method to Stream<T> type.
How to reproduce
import java.util.Arrays;
import java.util.List;
import java.util.function.Predicate;
import java.util.stream.Stream;
import lombok.experimental.ExtensionMethod;

@ExtensionMethod(Main.ExtensionMethods.class)
public class Main
{
    public static class ExtensionMethods
    {
        public static <T> Stream<T> filter(List<T> list, Predicate<? super T> predicate)
        {
            return list.stream().filter(predicate);
        }
    }

    public static void main(String[] args)
    {
        List<Integer> list = Arrays.asList(1, 2, 3);

        Stream<Integer> stream = list.filter(i -> true);
        Stream<Integer> itWorks = stream.filter(i -> true);

        Stream<Integer> itDoesntWork = list.filter(i -> true).filter(i -> true);
    }
}

Expected behavior
It should work.
Actual behavior
Lombok returns the following error during a compilation process:
error: method filter in class ExtensionMethods cannot be applied to given types;
  required: List<T>,Predicate<? super T>
  found: Stream<Integer>,(i)->true
  reason: no instance(s) of type variable(s) T exist so that Stream<T> conforms to List<T>
  where T is a type-variable:
    T extends Object declared in method <T>filter(List<T>,Predicate<? super T>)
1 error

Version info:

Lombok version: I tried two versions – 16.16, 18.18
Platform Gradle, IntelliJ IDEA,
JVM: 1.8.0_252 (Amazon.com Inc. 25.252-b09), 11.0.7 (Amazon.com Inc. 11.0.7+10-LTS)

Thanks for the reproducer, should be fixed with the linked PR.


Unit test which exposes bug (which is fixed)

a start on regression tests.
this test exposed a bug in the new simplified sqlroot class, which this commit also fixes.
the four commits subsequent to this should also be pulled, but this is the main one conceptually.

Note: I think actually psys.root['sql'] = SqlRoot() should just work.  Which removes the need for the Hybrid class I wrote yesterday!  I'm still surprised by simple code this pv design produces/requires.

And you can have several of SqlRoot instances.


Configurable thresholds

Right now it's hardcoded in booleans, category, coverage comparison.
It makes sense to make it configurable so it can be changed globally.
    err_diffs = difs[difs > 10]
    if not err_diffs.empty:

This requires to having a reloadable config.
At the minimum level, threshold can be an argument.


type error for composite primary keys in service options

  const options = {
    Model,
    id: ['entityId', 'otherEntityId'],
    paginate: app.get('paginate')
  }

Throws a type error, "string[] is not assignable to string", but according to the feathers-objection docs, this is how you use composite primary keys.
Unfortunately, I think fixing this also requires a change in feathers.  It looks like the upstream feathers AdapterService class doesn't allow a way to override its options object type.  So, even if we did
export interface ObjectionServiceOptions extends Omit<ServiceOptions, 'id'> {
  model: typeof Model;
  id: string | string[];  // <--change
  // ...
}

We would still get a type error here:
export class Service<T = any> extends AdapterService<T> implements InternalServiceMethods<T> {
  Model: typeof Model;
  options: ObjectionServiceOptions;
  // ...
}

The actual fix is probably to make the feathers AdapterService accept an additional type parameter:  AdapterService<T = any, S = ServiceOptions>, or to change ServiceOptions, but I think that might be more breaking.

@daffl , can you please take a look at this?


Changing backgrounds

Hi, thanks for this amazing project. I want to change the background image of the render animations as follows:
filepath = "ground.jpeg"
img = bpy.data.images.load(filepath)
cam = bpy.context.scene.camera
cam.data.show_background_images = True
bg = cam.data.background_images.new()
bg.image = img
But it doesn't work. I only know how to change the color of background now. Could you help me fix this?

Thanks for the issue @annopackage. This won't be supported for now, but it would be an interesting question for the Blender Stack Exchange (https://blender.stackexchange.com/) and might help other people with this problem.


One-off calls

Often I want to look up documentation, jump to definition, etc of something that's not currently written in my Lisp file.  Is there a way I can look up the definition of (or jump to, etc etc) an arbitrary string without typing it into my lisp buffer, running the key mapping, then undoing the typing?
Ideally I'd be able to make a mapping like nnoremap <localleader>dd? :call VlimeDocumentationForSymbol(input("Symbol Name? "))<cr>.  I looked in the Vlime source and it seems like VlimeDocumentationForSymbol() just expects one of the two magic strings "atom" or "operator"... any change we could get a separate function that could take the symbol name itself?

Good point. I can certainly add mappings for these one-off calls, but maybe re-arrange the code a bit first.
In the mean time, you can use the lower-level APIs to achieve what you want. Try this in your vimrc:
function! RcVlimeDoc(sym)
    let conn = VlimeGetConnection()
    if type(conn) == type(v:null)
        return
    endif
    call conn.DocumentationSymbol(a:sym,
                \ {c, r -> vlime#ui#ShowPreview(c, r, v:false)})
endfunction

augroup LocalVlimeKeys
    autocmd!
    autocmd FileType lisp nnoremap <silent> <buffer> <LocalLeader>dd? :call RcVlimeDoc(input('Symbol name? '))<cr>
augroup end

As of 7282f1f, there are default mappings for some one-off operations, and most of the top-level API functions are updated to have an one-off input mode.

This looks perfect, thanks!


Set of Taylor changes

Hey. These changes came about when hacking to make #17 .
See the commits for details..
Hopefully some are useful.

This is amazing, thank you for doing this! I won't have a chance to get this merged until early June but I'm very keen to.
I am curious how you found the experience of developing Taylor as I think you're probably the first person other than me to have a crack.

Hey, no worries. I found it tricky to get everything compiled right. I see the Docker based automation but I didn't have resources (mainly disk space) to use it, so was compiling directly on my Debian 11 system.
I got there in the end, but had to change some compiler arguments. And I think I may have changed the mruby-require implementation to one that offers the $" (usually aliased to $LOADED_FEATURES - the files that have been required) variable.
Other than that it's quite a pleasant experience and it's nice to see the C++ code I would have found difficult to write, there and working, and cross-platform.
Raylib is an attractive microlibrary to build on
I do have some API ideas that might differ. For instance, to add the Ruby methods to modules organised by their task:
Display.get_resolution rather than get_display_resolution, etc
But it would be okay to coexist and still help each other, if we don't find whole agreement!

I'm glad you managed to get it working! And yeah, the annoyance of getting it working on a local machine was the inspiration behind the docker based workflow.
I see you also commented on #11 so you know that I do plan to clean up the global namespace, I just want to get the shaders implemented before I do the big namespace cleanup and remove as much as physically possible from it.

Hey, mostly just housekeeping. Added the gem changes to the build config for all platforms, then did a full rebuild using Docker.
I'd squash / elide some of the commits, but don't want to give you trouble if you've already got a checkout :-)


Added possibility to specify username and password via system properties

Hi @tobiasstadler, thank you for your pull request. I was wondering whether this extension is indeed needed, as Maven already has support for specifying property values via system properties, e.g. if you don't want to hardcode the password in your pom.xml:
<plugin>
  <groupId>org.sahli.asciidoc.confluence.publisher</groupId>
  <artifactId>asciidoc-confluence-publisher-maven-plugin</artifactId>
  <configuration>
    <asciidocRootFolder>etc/docs</asciidocRootFolder>
    <...>
    <username>${confluence.username}</username>
    <password>${confluence.password}</password>
  </configuration>
</plugin>

Then, you can invoke Maven by adding -Dconfluence.username=xyz -Dconfluence.password=secret ... to the command and get your property replaced. Please also see the last paragraph under Maven Plugin Configuration in the official Confluence Publisher documentation
Would that be an option for you?
If not, we would have to discuss about whether we should then support system properties for all configuration values (not only username and password), and also test and document that feature. I am not sure though whether that is actually worth it.

Hi @cstettler,
your approach is what I am currently using. But with my change I can get rid of
    <username>${confluence.username}</username>
    <password>${confluence.password}</password>

My use case only requires username and password as system property. But you are right, I might be also interesting for other parameters.

Hi @tobiasstadler, thank you for the feedback. If the currently supported approach with the custom placeholders in the configuration is working for you, too, I would opt for sticking with it, as I don't see enough advantage by introducing yet another way of specifying system properties. It not only has to be developed, tested and documented, but also maintained over time. Do you agree?

I am fine with that


Feature/refactor with options

This is a bit of a refactor after I wanted to add in the ability to do options too.  The main points are:

kmod::options support
Refactored "generic" into kmod::setting which is implemented by alias, install, option and blacklist to try and reduce the amount of duplicated augeas stuff.
Doc updates

Come to think of it, I'd like to create a 2.x branch for this and move kmod::generic into an augeas provider.

@mcanevet what do you think?

@raphink +1 for the augeas provider

@mcanevet I mostly meant about creating a 2.x branch to work on a new version (including an augeas provider)

I created a 2.x branch so we can get started with this. Ideally, I'd like to replace kmod::generic with a kernel_module type & augeas provider.

I've merged this into the 2.x branch as 5b74b8ef576b964f2cd289a47c6c2247bc9fccf9. Let's move from there and try to see what we can do to keep improving it, using Augeas providers.


Add ubi8/openjdk-11 image as supported

Adding ubi8/openjdk-11 image as supported because there is latest image difference between 4.5 and 4.6 cluster. More details are in issue https://github.com/openshift/odo/issues/4138#issuecomment-723857666 . We need to open one pr in odo as well after init image release.

Related pr on odo https://github.com/openshift/odo/pull/4206. As both the prs are dependent on each other, this one needs to get merged forcibly into the master so that we can break the dependency. @mohammedzee1000 could you please merge this and initiate the init release process.

Looks good
/lgtm

/approve


Database

connection to mongdb established, added 'create profile' and 'search your friend' feature

Can you just rebase with main and do a force push? It seems that this is just one new commit.


Add all main Filters (total: 10)

String-Filter:
- federalState
- samplingStage
- origin
- category
- productionType
Date-Filter:
- sampling year
Object-Filter:
- antimicrobial resistance

All done, ready to merge.
I try to stick to the convention of only making one non-reject-comment in the next reviews, to make things faster :)


Prep work toward decoupling navigation from Redux.

Some preparation for #3804.

Thanks for the review! Just pushed some changes and responded to your comments above.

Not a big deal, but I suspect you can make this change after the "Tell all screens on AppNavigator" commit (and include the RealmScreen change in that one.) If you do, then I think the story to tell in this one's commit message becomes simpler, because no foreshadowing is necessary.

Since you said it's not a big deal, I'll go ahead as-is, if that's OK; see the error in https://github.com/zulip/zulip-mobile/pull/4273#discussion_r499905037 that I got when I tried the suggested adjustment.


Few Item / ItemBlock related mappings

Just some small additions. I've moved ItemBlock implementations into net.minecraft.item.block for now, though maybe it would make sense to move ItemBlock and ItemBlockColored into net.minecraft.item?

LGTM

LGTM


Forecasting in the renewal eqn session

I think my view is that we shouldn't include the forecasting piece in the random walk model in the renewal equation session (introduced in #112).
For me it interrupts the nice flow of building up the model and comparing line by line - especially by adding the transformed data and generated quantities blocks which aren't introduced at this point, unlike other blocks previously.
Not the biggest deal but in an already busy session it kinda just raises questions that aren't answered. So I don't quite see the advantage, compared to adding forecasting into the stan code at the time that it's first used (I assume in forecasting).
I know it means adding another stan model to the lineup but this doesn't really affect the learner. Is this a big barrier? I'm open to understanding more the motivation for introducing it earlier.

I agree that for didactic purposes I think it's best if models are the minimum needed at any stage (and build upon each other), even if at the expense of maintainability. The main downside I think is that if we ever want to change something in one model we then have to change it in all for consistency.

will then need to update data-raw/generate-example-forecasts.r once https://github.com/nfidd/nfidd/pull/126/files is merged

I'm not sure totally where we are on this but I think it might have snuck back in due to someones dubious ability to rebase

no it's never made it due to someone's dubious practice of side-addressing issues in PRs centered around other ones #132
We'll need a separate PR for this I think.


Add page number to cache key in character search

/character/search API endpoint seems to be caching responses using name and server only. Subsequent paginated requests to this endpoint hits the cache and returns cached page instead of the requested one until the cached page expires.
This PR adds page to the cache key, so page is also considered when caching search results.
Problem:
First request returns the expected result set
//<PHONE_NUMBER>5446
// https://xivapi.com/character/search?name=Gor&server=Exodus&page=1

{
  "Pagination": {
    "Page": 1,
    "PageNext": 2,
    "PagePrev": null,
    "PageTotal": 20,
    "Results": 50,
    "ResultsPerPage": 50,
    "ResultsTotal": 1000
  },
  "Results": [ ... ]

Second request specifying the identical name and server, but different page still returns previously cached page
//<PHONE_NUMBER>5514
// https://xivapi.com/character/search?name=Gor&server=Exodus&page=6

{
  "Pagination": {
    "Page": 1,
    "PageNext": 2,
    "PagePrev": null,
    "PageTotal": 20,
    "Results": 50,
    "ResultsPerPage": 50,
    "ResultsTotal": 1000
  },
  "Results": [ ... ]

Hi, thanks a lot for your PR ! This change will be effective after the next XIVAPI update (which will happen soon anyways since 6.0)


With nmake, invoking $(MAKE) needs /$(MAKEFLAGS)

The slash should be there according to Microsoft documentation,
see https://msdn.microsoft.com/en-us/library/7cafx990.aspx
Fixes #5277

Wow, that was fast! Applied patch manually to my 1.1.0 and it works perfectly, both with no options and with /s, thanks!

Merged. 22626b972c024d5ae9922e4a9d710a5f9e51f753
@qris, it was an easy fix, so...  ;-)


mac 上使用 docker 部署出错。

➜  ProxyPool: docker-compose up
[+] Running 0/1
⠇ proxypool Pulling                                                       5.9s
no matching manifest for linux/arm64/v8 in the manifest list entries

您好，我已收到您的邮件，我将尽快给您回复。Hello, I have received your email, I will reply to you as soon as possible.

可以试一试，在 docker-compose.yml 中，给 proxypool 增加配置 platform: linux/amd64。

已解决


Add a close button to the following settings

Add a close button to the following settings

This is not possible. It is part of Style Settings plugin.
Could you explain it better? Thanks

Add a toggle button for the alignment line that the arrow is pointing to.

Allows the user to turn off arrow-pointing snaplines.

I'm not sure if I understood correctly. But you can already disable this reading indicator (vertical orange line in your image). Just set the width to zero.

Let me know if this is the effect you are trying to achieve. If not, please explain in more detail.
Thanks

It works, but it would be much better to have a button to enable or disable it.

The functionality is already there, just set it to 0. Anyway, I will see what I can do about it.

Please check theme version 20.12.0. I added a toggle to Reading Mode submenu -> Reading Indicator and Labels. There is an option to hide the reading indicator (toggle)

All the best


update standup to add name for capvcd tests

What this PR does
Checklist

[ ] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

  {"level":"info","ts":"2024-09-25T14:09:31Z","msg":"Cluster App status: AppVersion='', Version='', ReleaseStatus='values-schema-violation', ReleaseReason='values don't meet the specifications of the schema(s) in the following chart(s):\ncluster-cloud-director:\n- global.metadata: Additional property name is not allowed\n', LastDeployed='0001-01-01 00:00:00 +0000 UTC'"}

Has cluster-cloud-director actually been updated and released to support this change?

Not yet

So this isn't going to pass.
What's the plan?

Antonia is probably working off that branch locally to have it ready

I think we should do a vcd release today so that it will be easier to test the next batch of changes. I'll take care of it.

/run cluster-test-suites

vcd tests passed! I am merging this so that we can use tests for other vcd PRs


Creating user

Description
[Provide a brief description of the changes made in this pull request.]

created users
stored users in database
hashed password

Related Issue(s)
[Closes #[issue_number]] (if applicable)
#45
Proposed Changes
[Describe the changes made in this pull request in detail. Include any relevant code snippets or configuration files.]
Checklist

[x] I have tested these changes locally.
[x] I have added necessary documentation or updated existing documentation (if applicable).
[x] I have followed the project's coding style and best practices.
[x] I have added/updated tests to ensure the changes are working as expected.
[x] I have reviewed the changes and ensured there are no typos or syntax errors.

Screenshots (if applicable)
[Include any relevant screenshots or images to showcase the changes (if applicable).]

Additional Information (optional)
[Add any additional information or context about the pull request.]

First successful stuff done with mysql


vertical scrollwheel not working on linux

When running the program under linux the vertical scrollwheel is not working, which makes the programm hardly usable.
System info:
OS: Arch Linux x86_64
Host: Blade 3.04
Kernel: 5.14.2-arch1-2
Packages: 1735 (pacman)
Shell: bash 5.1.8
Resolution: 1920x1080
DE: Plasma 5.22.5
WM: KWin
WM Theme: McMojave
Theme: McMojave [Plasma], Sierra-dark-alt [GTK2/3]
Icons: breeze-dark [Plasma], breeze-dark [GTK2/3]
Terminal: konsole
CPU: Intel i7-9750H (12) @ 4.500GHz
GPU: NVIDIA GeForce RTX 2070 Mobile
GPU: Intel CoffeeLake-H GT2 [UHD Graphics 630]
Memory: 1470MiB / 15900MiB

do u build reclass.net on linux yourself????

Duplicate of #236, still not fixed.


Upgrade templates to react-native 0.60.3

[x] Applied theming to react-navigation header.
[x] Update pacakges.

Applied theming to react-navigation header.
Update packages.


Offline functionality.

I am creating an Electron Application using React as a frontend framework that is likely to be used in an offline scenario.
I would like to play a Rive animation, but the library tries to access https://unpkg.com/<EMAIL_ADDRESS>Is there a way to play the animation without accessing anything from the web first?

You should be able to load in the WASM yourself by hosting it where needed:
https://help.rive.app/runtimes/overview/web-js/preloading-wasm

I will check this out, thank you.


atoma-vllm: in the Scheduler implementation, internal scheduling methods should be allowed to mutate self instead of consuming queue values

Deprecated


v1.46.1 failing with updater failure

This is potentially related to https://github.com/dependabot/cli/issues/229
From another project:
13:45:39    proxy | 2024/01/09 20:38:49 0/1119 calls cached (0%)
13:45:40      cli | 2024/01/09 20:38:50 updater failure: updater exited with code 1

From our test project reported in 229:
12:24:04  updater | Dependabot encountered '3' error(s) during execution, please check the logs for more details.
12:24:04  updater | +-----------------------------------------------------+
12:24:04  updater | |            Dependencies failed to update            |
12:24:04  updater | +-------------------------------------+---------------+
12:24:04  updater | | javax.servlet:javax.servlet-api     | unknown_error |
12:24:04  updater | | org.apache.logging.log4j:log4j-core | unknown_error |
12:24:04  updater | | org.apache.commons:commons-text     | unknown_error |
12:24:04  updater | +-------------------------------------+---------------+
12:24:07    proxy | 2024/01/09 19:17:18 0/0 calls cached (0%)
12:24:08      cli | 2024/01/09 19:17:19 updater failure: updater exited with code 1

Tried v1.44.1 and the error disappears.

@jakecoffman This appears to be happening again (without the key error of #229) in a different repo:
09:03:10  updater | Dependabot encountered '1119' error(s) during execution, please check the logs for more details.
09:03:10  updater | +-----------------------------------------------------------------------------------------------------------------------+
09:03:10  updater | |                                             Dependencies failed to update                                             |
09:03:10  updater | +-------------------------------------------------------------------------------+---------------------------------------+
09:03:10  updater | | @angular/animations                                                           | private_source_authentication_failure |
09:03:10  updater | | @angular/common                                                               | private_source_authentication_failure |
09:03:10  updater | | @angular/compiler                                                             | private_source_authentication_failure |
09:03:10  updater | | @angular/core                                                                 | private_source_authentication_failure |
09:03:10  updater | | @angular/forms                                                                | private_source_authentication_failure |
09:03:10  updater | | @angular/localize                                                             | private_source_authentication_failure |
09:03:10  updater | | @angular/platform-browser                                                     | private_source_authentication_failure |
09:03:10  updater | | @angular/platform-browser-dynamic                                             | private_source_authentication_failure |
09:03:10  updater | | @angular/pwa                                                                  | private_source_authentication_failure |
09:03:10  updater | | @angular/router                                                               | private_source_authentication_failure |
09:03:10  updater | | @angular/service-worker                                                       | private_source_authentication_failure |
09:03:10  updater | | @fortawesome/angular-fontawesome
...
09:03:12    proxy | 2024/01/22 15:55:37 0/1119 calls cached (0%)
09:03:13      cli | 2024/01/22 15:55:38 updater failure: updater exited with code 1

While the reason given is different from "unknown_error", I don't think private source auth didn't use to fail the run?

Yeah if you want to post a new issue and provide the logs around one of those dependencies that would help us track down the problem.
Also would be good to see the input file like how you posted here: https://github.com/dependabot/cli/issues/229#issuecomment-1900634125


Documentation: Add frontmatter to WSL docs

The WSL 2 installation instructions page https://open-horizon.github.io/docs/mgmt-hub/docs/WSL/ is currently shown as a top-level navigation item (see screenshot below):

This is because it is missing front matter.  Please add the front matter, and ensure the navigation is updated to show the page as falling under advanced manual installation:
---

copyright:
years: 2021 - 2023
lastupdated: "2023-09-26" <-- ensure the right date here
title: "Manual agent install" <-- ensure the right title here

parent: Edge devices info
grand_parent: Edge devices
nav_order: 5
---

Hey @joewxboy, I would like to work on this issue. can you assign it to me?

@sajdakabir Sure.  Let me know if you have any questions


Flush logs on crash to desktop

Problem
When the game crash to desktop, some logs will not be flushed. It can prevents meaningful data to be logged. While a debugger could be used to workaround this behavior, it is not possible / expected when requesting logs from players.
Solution
Hook when game's crash handler is triggered, and manually flush current logs.
As proposed by @jac3km4, this native function should be a good candidate to hook on.
I'll look at this later and draft a PR.

These are the address patterns from my WIP update for ctd_helper to 2.12a
/// @pattern 4C 89 4C 24 20 53 55 56 57 41 54 41 56 48 83 EC 68 80 3D ? ? ? 00 00 49 8B F8 8B F2 48 8B E9
__int64 AssertionFailed(const char *, int, const char *, const char *...);

/// @pattern 48 8B 02 48 83 C0 13 48 89 02 44 0F B6 10 48 FF C0 48 89 02 41 8B C2 4C 8D 15 ? ? ? ? 49 FF
void __fastcall Breakpoint(RED4ext::IScriptable *context, RED4ext::CStackFrame *stackFrame, uintptr_t a3, uintptr_t a4);

/// @pattern 4C 8B DC 49 89 5B 08 49 89 73 10 57 48 83 EC 20 48 8B 05 ? ? ? 01 48 8B FA 40 8A F1 48 83 F8
void __fastcall CrashFunc(uint8_t a1, uintptr_t a2);

Addresses for 2.12a are:
#define AssertionFailed_Addr 0x29387E8
#define Breakpoint_Addr 0x2026C1C
#define CrashFunc_Addr 0x2939C64

I couldn't find any of those addresses in cyberpunk2077_addresses.json though

Thank you @flibdev :)

Found the address hashes (I had missed the 0x1000 offset):
#define AssertionFailed_Hash<PHONE_NUMBER>
#define Breakpoint_Hash<PHONE_NUMBER>
#define CrashFunc_Hash<PHONE_NUMBER>

Currently I hook AssertionFailed, log a crash report and do App::Get()->Shutdown() to gracefully shutdown + flush logs, before calling original function. In such case, CrashReporter is not triggered (no popup). Would it be a problem?
@flibdev , crash report is actually what ctd_helper does. Shouldn't it be better to have this right into RED4ext instead of a dependency?


fix(tools): disable i18n linting

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Disables the schema validation for non-English translation files. This will allow us to merge PRs without having to modify the i18n objects through GitHub, ensuring that we are doing those changes through Crowdin explicitly.
This comes from a discussion with @RandellDawson about how to best avoid duplicate work, and how to approach the addition of new UI elements that require translation. With this flow, a PR that adds a new UI element would only add the key to the appropriate English file. Then we would upload the change to Crowdin, pull down the translation, and merge that to land the key on the other locale files.
As it stands, there are some concerns about this approach. We'll want to establish the infrastructure to allow running CI on specific language builds, so we can adjust this to test the language file for each locale and prevent deployments with missing translation keys.
/cc @raisedadead

I see this discussion pop-up quite a bit. I think we should lock-in the policy.
TL;DR:
It's okay if non-English sites show the exact English copy for however long it takes to get Strings translated and approved.
The detailed version:
Here are some of the minimum needs for deployment.
 That gives us a clear path to deployments for emergency patches (especially security & show stoppers).
A commit's "deployability" is determined with linting checks & CI checks.
I agree this means we would be needing to make a trade-off somewhere. Here is a workflow that we should enforce that establishes that tradeoff:

Workflow diagram

This means with PRs like #41002 we will overwrite the changes on the repo. Those could either be a manual on-off translation to non-English files we make over in #41002 or an English string that was copy pasted over to the non-English file.
One other thing, we stop using these debug bits like "ES Translate help" etc. When need of test bits let's just use Google translate. I understand it's not accurate - and that is the point to get a true copy from Crowdin via the policy above. You can think of it as getting an improved translation of original string.
I intentionally used a Google translated bit in the screenshots on #41002 to see how it fits.
So, there it's always nice to use a Google translated version for testing and debugging, and when making a PR copy paste over the exact English string to non-English counterpart.
That way we can keep our sanity with the linting and testing we have in place for deployments.
@nhcarrigan,
You should adjust this PR if needed accordingly.

when making a PR copy paste over the exact English string to non-English counterpart.

With the policy being that we copy the English key-value pairs to the non-English files, this PR can be closed and we can retain the same lint step we currently have, which asserts that all translation objects match the correct schema.

Perfect, in that case we should just update the PR to add some docs instead for reference.

Can we discuss this further?  I don't like the idea of having English scattered throughout the home page of the Chinese site.  It is one thing to do this for a section of the site (where we have a note about needing help for translation), but for the main part of the site to have a mix of English and non-English seems strange to me.

I think the key point is we need an 'emergency path to deployment' and that's the only time we might have English.

Going to close this, since we are implementing the flow of adding the English key-value pairs to the i18n objects.
Will create a separate PR for the documentation discussed above.


Numeric values override sorting in bar chart and other charts

Hey guys,
I plotted out the result of a wordcount and got some strange result: Words, that are numbers themself, are printed first in the chart, although the sql-query sorts by count.
The resulting charts are attached.
I used the current master merged with branch spark-1.2, Spark 1.2.1 and zeppelin.spark.useHiveContext = true.
All charts display the "numeric words" first:

For table-view, everything is just fine

Oh, I could reproduce the bug with following query:
%sql
select * from
(select 1 a, 3 b union select 2 a, 2 b union select "a" a, 1 b) c
order by b
On Wed Feb 11 2015 at 12:54:39 AM biggedi<EMAIL_ADDRESS>wrote:

Hey guys,
I plotted out the result of a wordcount and got some strange result:
Words, that are numbers themself, are printed first in the chart, although
the sql-query sorts by count.
I attached the resulting charts.
I used the current master merged with branch spark-1.2 and Spark 1.2.1.
All charts display the "numeric words" first:
[image: image]
https://cloud.githubusercontent.com/assets/1087140/6130415/4b5b3c54-b145-11e4-84fa-131f32547d51.png
[image: image]
https://cloud.githubusercontent.com/assets/1087140/6130418/57b82c78-b145-11e4-807f-b1444bf65a31.png
For table-view, everything is just fine
[image: image]
https://cloud.githubusercontent.com/assets/1087140/6130428/67c0ea10-b145-11e4-9937-696c8e7e492c.png
—
Reply to this email directly or view it on GitHub
https://github.com/NFLabs/zeppelin/issues/334.

I got that one a few days ago, currently the graph in itself is ordering using the x axis all the time. We would need a order option


Add configuration option for export file types

We should let users select which file types Mirrorful exports because some/most projects don't need tokens in all formats. We can enable this by adding a property like files to the configuration object whose value is an array of export file types.
See this Slack thread.

@alexdanilowicz / @Teddarific, feel free to assign this to me 🙋🏻

Assigned, love it. I myself have been wanting this. Thanks for opening an issue so that it is tracked!


Cut a release that builds with a currently supported version of Electron

I'm the packager for the official Arch Linux packages for Keybase. They are terribly out of date because all current builds have been failing to build on any currently supported version of Electron for some time. At the time the current 6.2.x releases were made Electron26 was supported, but it went EOL shortly afterwards and we were never able to get it build. The package is currently stuck on 6.0.x, and even at that the relic of an Electron package it depends on is going to get dropped soon.
If we don't get a solution for building with current dependencies then it is going to get downgraded from official package status to an AUR package where end users have to build it themselves and work out the mess on their own.
Current supported versions are 28, 29, and 30. Please make a bump to something that is not EOL a priority so that downstream packaging can happen smoothly.
Looking around the issue tracker it looks like Fedora and others are having trouble because of this too and just using a current Electron build should make a lot of issues go away.
For a security focused app ecosystem it is unreasonable to expect people to run it on an EOL version of Electron & Chromium that is no longer being patched for known security issues.

Honestly the fact that the Keybase-client dependencies are horridly out of date is becoming an issue on all Linux distros. The Debian/Ubuntu package depends on packages that are no longer available in Ubuntu 23.10, nor 24.04.

This is sad, Ubuntu 24.04 is lacking the needed dependencies libappindicator1 | libayatana-appindicator1 and libgconf-2-4 to install Keybase. Ever since Keybase was sold to Zoom, it seems like Keybase is dying a slow death. What do you guys think the chances are that maintenance will catch up soon? Maybe it is time to leave the sinking boat? I am sad, loving Keybase and have been using it for many many years.

The fact that this repos issues and issue comments are full of crypto scammers and nobody is even bothering to do issue triage and report the bad comments does not speak well of how this project is being managed.

A few months ago, I was approached by an individual who claimed to be a successful cryptocurrency trader with a foolproof investment opportunity. They promised high returns in a short period and assured me that my investment was safe and secure. Filled with excitement and the prospect of making quick profits, I decided to invest a significant amount of money in the scheme. The initial weeks seemed promising as I saw small returns on my investment, which further fueled my belief in the operation's legitimacy. However, as time passed, the individual became increasingly difficult to reach, and my requests to withdraw my profits were ignored. It soon became clear that I had fallen victim to a cryptocurrency investment scam. I had lost a substantial sum of money, and the promises of high returns were nothing but a facade to lure unsuspecting investors.   However, I refused to give up hope and began searching for solutions online. That's when I came across Trust Geeks Hack Expert  specializes in recovering stolen cryptocurrency. I reached out to them and explained my situation, and they immediately sprang into action. Through their expertise, determination, and relentless effort, they were able to track down my lost Bitcoin and recover it for me. I was overjoyed and relieved beyond words when I received the news that my funds had been successfully retrieved. If you find yourself in a similar situation look for assistance from Trust Geeks Hack Expert. I urge everyone to exercise caution when approached with investment opportunities that seem too good to be true, especially in the realm of cryptocurrency.
Contact Service
Email::  trustgeekshackexpert[Dot]fastservice[At]come
Website. https://trustgeekshackexpert.com/
Telegram ID : Trustgeekshackexpert

At the end of 2023, I found myself ensnared in a nightmare of epic proportions. It was a year marked by loss and betrayal, as I fell victim to the siren song of a fraudulent Forex Investment Company, losing a significant portion of my hard-earned Bitcoin in the process. The aftermath was a whirlwind of despair and uncertainty, as I grappled with the harsh reality of my situation. How could I ever hope to recover what had been so callously taken from me? It seemed like an insurmountable task, a mountain too steep to climb. But amidst the chaos and despair, a glimmer of hope emerged on the horizon – Trust Geeks Hack Expert. With nothing left to lose, I reached out to them, laying bare the extent of my misfortune and placing my trust in their capable hands. From the moment they took on my case, I knew I was in good hands. Their team of professionals and hackers worked tirelessly, employing every tool and technique at their disposal to track down and retrieve my stolen funds. It was a Herculean effort, a battle fought on the front lines of the digital battlefield. Days turned into weeks, and weeks into months, but still, they persisted. Their dedication knew no bounds, their determination unwavering in the face of seemingly insurmountable odds. And then, like a bolt from the blue, came the news I had scarcely dared to hope for – my lost Bitcoin, all 2 million Euros worth, had been successfully recovered. It was a moment of disbelief and profound relief, as I realized that what had once seemed impossible had become a reality. Trust Geeks Hack Expert  not only restored my financial security but also restored my faith in the power of resilience and determination. Their expertise and dedication were unmatched, and their commitment to justice was unwavering in the face of adversity. They were not just a team of professionals but a beacon of hope for those who had lost their way in the labyrinth of deception. To anyone who finds themselves in a similar situation, I offer this advice – do not lose hope. Reach out to Trust Geeks Hack Expert website. https://trustgeekshackexpert.com/ &   Telegram ID : Trustgeekshackexpert , for they possess the knowledge and skill to turn despair into triumph, and darkness into light. In a world where trust is often betrayed and dreams shattered, Trust Geeks Hack Expert stands as a testament to the power of perseverance and determination. They are the real deal when it comes to reclaiming what is rightfully yours, and I will forever be grateful for their unwavering support and expertise.


beitv2 512 pretrain models

Thanks for releasing Beitv2 code and pretrain models, it's really an exciting work.
I have a question that whether you have the plan to release beitv2_512 pretrain models. If not, how can I finetune beitv2_224 pretrain models with 512×512 images?

Yes, we will release the 512 checkpoints.


fix: readme install instructions typo

Description
The native installation instructions in the readme have .env.example as the name of the example env file, where the file is actually called .env-example. This PR updates this section of the readme to use the correct filename.

Testing
N/A

New dependencies
N/A

Good catch. Thanks!


⚠ Hartman Foundation has degraded performance

In c2531eb, Hartman Foundation (https://gordonhartman.com/) experienced degraded performance:

HTTP code: 200
Response time: 2811 ms

Resolved: Hartman Foundation performance has improved in 83ee123.


[AutoRelease] t2-sqlvirtualmachine-2022-12-20-80948(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3572
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1034
BuildTargetingString
azure-mgmt-sqlvirtualmachine
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/3572

@Wzb123456789 @msyyc can you help review this PR?

/check-enforcer override

/check-enforcer override


Multi-frame shader compilation

[ci no changelog needed]
Pull Request Description
Implements #181681597. This is a PR that uses a lot of code from https://github.com/enso-org/enso/pull/3372.

Important Notes

This code has a FIXME left in 2 places. These are small refactorings – that will be fixed after the first review.
This code exposes tracing crate in prelude. We will be moving to tracing from our logger in the near future, but tracing_wasm needs to be fixed to support our use cases (@mwu-tow is working on it).
The application needs to be heavily tested as this code touches core rendering concepts.

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Scala, Java, and Rust style guides.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed: Enso GUI was tested when built using BOTH ./run dist and ./run watch.

Details on the performance issue: It seems Chromium (and Electron) has limits on the number of compile/link jobs that can be in flight. If the limits are exceeded, it applies a crude form of backpressure by blocking until all pending jobs complete. We can avoid that happening by implementing limits on the number of jobs in the compiling and linking states. I've found that these (very low) limits work on my machine: ensure concurrent compiling jobs <= 2 (i.e. 2 pairs of shaders), ensure concurrent linking jobs <= 4. I expect those values would avoid getting throttled in any Chromium/Electron environment where khr_completion_status is supported, because chromium always forks at least 4 shader-compiling processes when the extension is available. I don't know the optimal values for these limits, or whether they're machine-dependent; it would be nice to find out how high we can safely raise the limits so we can get shaders compiled faster, but it isn't hugely important now that we aren't blocking on shader compilation.

@kazcw thank you so much for such a detailed check on these. We can either hardcode the max concurrent linking jobs or we can just spawn them until one blocks for longer and then remember the number for the rest of the app lifetime. What do you think about it?

@wdanilo
Increasing parallelism would only benefit CPUs with more than 8 threads (due to the way Chromium determines its thread limits). Users with lower-end hardware would also be the most affected by hitting the blocking case. I wouldn't like to see low-end performance slowed down that much to improve high-end performance.
It would be useful to know what we'd gain by increasing parallelism (for hardware that supports it); I also really don't like not knowing for sure what's causing this. So I gathered more data: I used low-level profilers to change how we measure this code, so that we track not just what compile-stages we're executing, but how they fit into the lifetime of each shader. (I'll PR the profiling changes to your branch, but I need to separate it from my quick and dirty throttling implementation first.)
Summary of findings

The vast majority of the time we spend compiling shaders is when we initially render the graph; we don't do much compiling after coloring information arrives. So at least until the backend provides type info much sooner, compiling shaders faster will not significantly impact total startup time.
Some shader is taking 500ms to compile. This is probably related to the blocking case. I wonder if it has anything to do with the MacOS crashes? We need to find out what's going on with this shader.

The data
Without the job-limit workaround
Here's a profile without implementing limits, demonstrating the blocking case (rendered with #3382):

The top part shows the main thread; you can see where we block for about 500 ms on the completion check. Each line in the tall stack below is a shader compile job. All the shaders jobs finish at the same time, confirming that it is a full pipeline flush: The completion check blocks until everything is done compiling. (The timings of everything else in the main thread would normally be much shorter, but this is a debug/opt-level=1 build; optimization level doesn't affect the timings of the relevant calls.)
With the workaround
Here's a proflie with a limit of 4 concurrent jobs--scale is about the same.

(I'm only showing the shader-compiling part here; compiling never blocks the main thread in this case.) The weird thing here is that first compile--it takes 500ms for one shader?? The shader in question is the first one to start compiling when we start preparing to draw the graph editor. I'll add some more instrumentation and find out what code that would be.

@kazcw @MichaelMauderer I applied your comments here. It's ready for review and hopefully for merge. A few notes:

@kazcw, I created a limit for max parallel compilation jobs. However, as we do not know when the compilation is finished and when the linking starts, we set the limit globally, in such a way that there are max 2 compilation & linking jobs in total. Please check it out and if you'd have a better idea, let me know.
The f32 vs f64 time issue is important, but let's fix it in a separate PR.
Please test this PR and check if everything works in the product as it should. Then, let's merge it :)


Collision Map needs to expand to match tilemap

The collision map needs to also be set to the same size as the tilemap or the collision will wrap causing errors.

This is causing issue trying to parse collision maps that don't match the same size as the tilemap.

This has been fixed.


RoutingHashReactHooks does not work in TryPureScript

This recipe causes odd behavior in TryPureScript (as first noted here: https://github.com/JordanMartinez/purescript-cookbook/pull/271#issuecomment-774830288, and pictured below) where clicking on a link will re-direct such that the <iframe> renders a nested instance of TryPureScript. I've added a tryUnsupported.md and removed the Try link from the README table of contents. Interestingly this exact code will work if run as a gist in TryPureScript. This seems to be unexpected behavior; should I open an actual issue to track this?

I want to say this is an issue with Try PureScript, but I'm not really sure what is causing it.
Either way, I think we should merge this to prevent this unexpected behavior.

try.ps.ai generates the iframe a bit differently than the original site, and this is definitely a regression. Thanks for reporting. I'll dig into this whenever I get around to making another pass at merging with upstream.


build: fix version for checkstyle, marvin

Description
This PR...
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

Thanks @shwstppr this PR is no longer needed, fixed


Implement nested modules

This implements the ABS proposal, discussed in #4883, but without use of
the module keyword.
It also doesn't reserve module names, which I'll do in a follow up.
Also postponed to a follow up: possibly moving a number of the existing
modules into the std:: namespace.
Also postponed to a follow up (that I will probably try to pawn off
onto @raddevon): documentation.

I think we are good to go here; could I get a final review from @elprans or @aljazerzen?


Clarify requirement for validator balances body

Looking at the validator_balances endpoint there is some ambiguity around what to do in some cases.  Specifically, for POST to /eth/v1/beacon/states/head/validator_balances:
With no body:

lighthouse returns an error
lodestar returns an error
nimbus returns an error
prysm returns an error
teku returns all balances

With an empty array in the body:

lighthouse returns no balances
lodestar returns no balances
nimbus returns all balances
prysm returns all balances
teku returns all balances

I think that the best balance of attempting to retain existing functionality whilst firming up the spec is to state that no body will return an error, and an empty array will return all balances.  This also ensures that users have a way to obtain all balances easily..

an empty array will return all balances

Agreed, this behavior is likely for the best. And just yesterday I noticed few interop issues between clients when using postStateValidators.
E.g. Prysm VC sends an empty statuses array which leads to some clients not returning any data. We might wanna add the same note there as well.
Empty array should equal omitting the property and not apply any filtering as otherwise it will always return no data.

I'm not sure I 100% agree that 'no body' equates to error. It's logically the same as an empty array... We can throw an error, but it's a bit weird IMO.
In real terms you haven't requested anything specifically in both cases, and the default is 'return all data'.

I'm not sure I 100% agree that 'no body' equates to error. It's logically the same as an empty array.

We might wanna keep the body as required : false, we don't really gain anything if server throws an error if body is omitted, or just leave it up to the server implementation to decide.
This is also much more user friendly if you wanna do a quick curl as you can just do
curl -X POST http://localhost:9596/eth/v1/beacon/states/head/validator_balances

no extra headers and  -d "[]" required

I'm not sure I 100% agree that 'no body' equates to error. It's logically the same as an empty array.

We might wanna keep the body as required : false, we don't really gain anything if server throws an error if body is omitted, or just leave it up to the server implementation to decide.
This is also much more user friendly if you wanna do a quick curl as you can just do
curl -X POST http://localhost:9596/eth/v1/beacon/states/head/validator_balances

no extra headers and -d "[]" required

It's handy. technically adding required probably could be argued as breaking but given that most clients already error i'm not going to make that argument :) I'm fairly sure that accepting it as equivalent to an empty array is about 1-2 lines of code if people would just do that...
Teku generally has tests for empty array of a post as well as the empty body as equivalence for endpoints that query in that way.

Teku generally has tests for empty array of a post as well as the empty body as equivalence for endpoints that query in that way.

Have updated Lodestar to behave the same as there is no downside if the server accepts an empty body for routes that only apply it to filter the response, but the client will still send an empty array if no filtering is applied.

Have updated Lodestar to behave the same as there is no downside if the server accepts an empty body for routes that only apply it to filter the response, but the client will still send an empty array if no filtering is applied.

this sounds like basically what we do - we always do send empty array if required, as technically that is correct, but no real down side to allowing no body - ta for update.

Latest update tweaks the wording to consider both [] and an empty body as "return all validators".


Request test builds from running Dune build in watch mode

When there is a dune build in watch mode, the extension should instead do an rpc request to dune rather than run its own dune.

The exact isusue is https://github.com/ocaml/dune/issues/8114 now.


Migrate Fragments to viewBinding

Task/Issue URL: https://app.asana.com/0/488551667048375/1201260849403183/f
Description
Migrate the following fragments to use viewBindings:

DownloadConfirmationFragment
EmailAutofillTooltipFragment
DefaultBrowserPage
WelcomePage

Steps to test this PR
==Test the onboarding fragments==

fresh install from this branch
open app
verify the Set DuckDuckGo as your default browser app dialog shows during onboarding

==Test the email autofill==

install from this branch
ensure email beta is enabled (in settings)
go to https://www.idealista.com/en/nuevo-usuario
in email address click on Dax
verify autofill dialog shows
verify both buttons in dialog work as expected

==Test download dialog==

install from this branch
go to https://www.thinkbroadband.com/download
download a file
download the same file
verify download dialog shows
verify all dialog options work as expected

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Update: @joshliebe feel free to review this PR. https://github.com/duckduckgo/Android/pull/1492 was closed, so there will be no conflicts.

Current dependencies on/for this PR:

develop

PR #1521  (this PR)

This comment was auto-generated by Graphite and will continue to be automatically updated while this PR remains open.

@joshliebe can you take a look or assign a new reviewer?

@joshliebe can you take a look or assign a new reviewer?

@malmstein I'm waiting for the bitrise issues to be sorted, then I can review 👍


Fix prompt dialog bug

When user clicks the prompt button, it doesn't work.

Add PROMPTER_ROLE to private key account


Function declarations with explicit type annotations compile to the wrong Erlang code

Describe the bug
Explicit type annotations seem to compile to the wrong Erlang code.
To Reproduce
(* example.ml *)
let f (x : int) : int = x + 1

compiles to:
% Source code generated with Caramel.
-module(example).

-export([f/1]).

-spec f(integer()) -> integer().
f(_) -> erlang:'+'(fun x/0, 1).

Expected behavior
I'd expect something like this:
% Source code generated with Caramel.
-module(example).

-export([f/1]).

-spec f(integer()) -> integer().
f(X) -> erlang:'+'(X, 1).

I have been working on a new one but I can't promise when it'll be public.

Ok. What does the new compiler bring to the table that couldn't be done with the current one?

If you're still looking for a type-safe language on the BEAM that you can start using today, try out Gleam ✨

I've looked into Gleam and I don't see it bringing anything that OCaml doesn't do better. Maybe a different approach based on dependent typing or something else not related to the HM typesystem would be valuable, but I don't think Gleam is going in that direction.

The new compiler is a full rewrite that uses the OCaml Lambda and translates it directly into Core Erlang. It's also architected so much better, so onboarding into it, fixing things and growing it, will be much more productive.
The last thing I've been playing around is a syntax that has less quirks and is more modern, mainly inspired by ReScript and Rust. This would also allow building an interesting macro system that doesn't rely on ppx or other off-chain code transforms, that we could use to get rid of a lot of boilerplate without losing any type-safety. This is still highly experimental so nothing to show just yet, but the macro system is heavily inspired in Racket, Rust, and Elixir.
Anyway, I've said too much! 😱

The new compiler is a full rewrite that uses the OCaml Lambda and translates it directly into Core Erlang. It's also architected so much better, so onboarding into it, fixing things and growing it, will be much more productive.

I once tried to hack OCaml's Lambda intermediate representation, but I didn't have much success. I hope you succeed there! I agree with you that's probably the best representation if you want to compile to Erlang (I believe that they added more metadada to the Lambda representation which probably makes it easier).

The last thing I've been playing around is a syntax that has less quirks and is more modern, mainly inspired by ReScript and Rust.

I'm not a huge fan of OCaml's syntax (although it's less noisier and better than most - better than Elixir for example, for sure), but I think that using a different syntax brings very few benefits and a lot of costs. Namely, it makes it impossible to reuse normal OCaml tools (like editor plugins). This is my opinion, though, and I understand you might have different criteria which leads to a different solution.

This would allow for two things. First, it allows the compiler to restrain what type-level features you can use rather than just crashing with a "oops, unsupported feature!" or whatnot.

This is an example of a valid reason to change the syntax, although personally I'd prefer to keep support for as many OCaml features as possible. The OCaml typesystem is very cool and very complete, and can probably support any programing paradigm that makes sense on the BEAM.

Anyway, I've said too much! 😱 I don't expect any of this to be usable this year.

Is there any way you could make it public earlier, so other people could play with it? I totally respect your decision to keep it private while you want to, of course. I'm just curious.

@tmbb re: as many features as possible, I hear you. I think one example would be OCaml 5 effects -- this may be one of the features that are just too hard to map onto the BEAM. A lot of ground to explore here, and barely any resources to do it! 😄
re: trying it out, the branch is up under the name sugarcane (yes! another candy from my land), but you need a fork of the OCaml compiler to run it -- specifically, you need this PR: https://github.com/ocaml/ocaml/pull/11064 -- so its a little tricky to get it up and running atm.

specifically, you need this PR: ocaml/ocaml#11064 -- so its a little tricky to get it up and running atm.

I understand why you'd need a full year, then. The metadata you add is important to deal with variants, but it's a little invasive for the compiler.

The current main branch doesn't depend on my OCaml fork, but it also has several bugs that you'd have to work around. If you are interested in trying this out for real, I'd love to learn more about your use case to see how much work sugarcane needs to fit your needs.
Worst case scenario, we can just use the OCaml fork while we wait for changes to be upstreamed. After all, as a language user you'd be getting the binaries straight out of Github, and you wouldn't need a custom OCaml installation.
Would you mind sending me an email to leandro at abstractmachines dot dev with more info?


Update Microsoft.Databricks  table

From<EMAIL_ADDRESS>For Microsoft.Databricks
The table is incorrect for the part that "Tag in cost reports" for "workspaces" should be marked as "Yes".

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 66769e1b-720b-f1b1-a5e3-ed5cb24cd233
Version Independent ID: b6272e61-58c1-3e2f-3e36-a9ee920c0915
Content: Tag support for resources - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/tag-support.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

Microsoft triage team, please assign this issue to @davidsmatlak. Thanks.

@stbof thank you for the documentation feedback. I submitted the fix for this issue and when it merges, this issue will automatically close. After the merge, the updated document will be online within 24 hours.

#please-close


Tauri ACL/Allowlist v2 Implementation and Plugin System Refactor

This PR contains several (breaking) changes related to:

Tauri plugins
The new allowlist
Tauri build process

The current proposal and extended documentation for these changes can be found in a public HackMD document here. This document will be undergoing several changes during the implementation but shows the general approach and architecture. We strongly recommend reading this document before commenting.
We currently believe this is the one big major change needed to make v2.0 feature complete for a beta/rc/release,
therefore work on this PR should be prioritized.
Tauri Plugins
In v2 of Tauri most of the commands were moved into dedicated plugins and outside of the core of Tauri.
The move to plugins rendered the existing allowlist unusable, as the system was not designed to be compatible with plugins or code outside of Tauri. This PR addresses this by adding a new allowlist and access control for Tauri commands written by app or plugin developers.
The plugin-workspace repository contains all of the previous (and more) functionality now available as plugins (see the v2 branch). This reduces the amount of complexity in Tauri itself. Additionally, it allows more fast paced changes of system interaction functionality, as no complete understanding of Tauri itself is needed to contribute. It also allows breaking releases/changes to specific plugins independently from Tauri.
To further define what Tauri plugins are and what they need to implement the tauri-plugin crate was created.
It can be found in core/tauri-plugin in this PR branch.
Plugin developers need to depend on this crate and implement the defined traits, define default permissions and optionally define scope types.
A lot of work (not tracked here) is required to upgrade plugins from v1 to v2 and convenience tooling like tauri plugin init, tauri permission init/add/remove needs to be created, while existing tooling like tauri-cli and create-tauri-app need to be changed to be compatible with the new permissions/capabilities/plugins.
Allowlist
In v1 of Tauri most of the commands were Tauri internal APIs built into the core of Tauri. The allowlist was used to restrict the access from the Webview to the Tauri core and system resources.
With this PR the new allowlist is built in a way to be used by all plugins and application developers and is no longer exclusive for Tauri inbuilt functionality. It also allows more fine grained control, while being able to abstract away a lot of things.
We introduce several new naming conventions and move the allowlist to a capability driven configuration. Permissions define command enablement and scope, while capabilities link permissions with windows of the application.
A simplified example allowlist/capabilities configuration could look like:
"capabilities": [
    {
        "context": "local",
        "windows": [
            "*"
        ],
        "permissions": [
            "fs:full-homefolder-access",
            "fs:block-homefolder-sensitive-access"
        ]
    }
]

with an example permission, which could also be inbuilt/defined by the fs plugin:
{
    "version": 1,
    "identifier": "full-homefolder-access",
    "description": "This allows read write access to the complete $HOME folder.",
    "commands": {
        "allow": [
            "fs:readDirectory",
            "fs:readFile"
        ]
    },
    "scope": {
        "allow": [
            {
                "path": "$HOME/**"
            }
        ]
    }
}

or even simpler when the capabilities are further abstracted:
"capabilities": [
        "default",
        "admin-windows"
]

Tauri Build System
The build system will be enhanced (most likely) in a non-breaking way to understand metadata information provided by plugins and will allow us to pass information from plugins into the Tauri application.
It also will allow us to highlight issues to the application developer when commands are enabled in the capabilities but the plugin implementing these commands is not initialized/used. Also the other way around when no commands of a plugin are enabled but the plugin is initialized.
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[x] Refactor
[x] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[x] Yes
[ ] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[x] I have added a convincing reason for adding this feature, if necessary

Other information
Related issues:

#7461 the new v2 implementation will deprecate the dangerousRemoteIPCAccess as it will be part of the capability definition

We have states now!
#[allow(dead_code)]
#[derive(Debug, Deserialize)]
struct PingScope {
  path: PathBuf,
}

#[allow(dead_code)]
#[derive(Debug, Deserialize)]
struct SampleScope {
  path: PathBuf,
}

#[tauri::command]
fn ping<R: tauri::Runtime>(
  app: tauri::AppHandle<R>,
  value: Option<String>,
  scope: tauri::command::CommandScope<PingScope>,
  global_scope: tauri::command::GlobalScope<SampleScope>,
) -> std::result::Result<PingResponse, String> {
  println!("local scope {:?}", scope);
  println!("global scope {:?}", global_scope);
  todo!()
}

I'm not sure how useful command-specific scopes are going to be (probably too confusing for users?) but it's there


CLOUDP-272416: Remove datalake tests

Proposed changes

Jira ticket: CLOUDP-272416
Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[ ] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[ ] I have updated test/README.md (if an e2e test has been added)
[ ] I have run make fmt and formatted my code

Further comments

also: currently
➜  mongodb-atlas-cli git:(master) ./bin/atlas datalake
Command "dataLakes" is deprecated, Please use 'atlas datafederation'
The datalakes command provides access to your project data lakes. You can create, edit, and delete data lakes.

Usage:

/bin/atlas datalake

that's datalake, you need to deprecate atlas dataLakePipelines


K8SPXC-308: add service per pod functionality

Test name
Status

recreate
passed

scheduled-backup
passed

upgrade-haproxy
passed

haproxy
passed

storage
passed

scaling
passed

big-data
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

limits
passed

self-healing-chaos
passed

monitoring-2-0
passed

self-healing-advanced
passed

affinity
passed

one-pod
passed

self-healing-advanced-chaos
passed

demand-backup
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/891/commits/12c8de2038f38fe0b1cd80be7dff878954a9c167
image: perconalab/percona-xtradb-cluster-operator:PR-891-12c8de20

Test name
Status

upgrade-haproxy
passed

storage
passed

scaling
passed

haproxy
passed

recreate
passed

big-data
passed

scheduled-backup
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

security-context
passed

limits
passed

self-healing-chaos
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
passed

self-healing-advanced
passed

affinity
passed

one-pod
failed

self-healing-advanced-chaos
passed

pitr
passed

operator-self-healing
passed

upgrade-consistency
passed

operator-self-healing-chaos
passed

demand-backup-encrypted-with-tls
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/891/commits/d04b4b81366cac23246b4978bc9f572a79ef8704
image: perconalab/percona-xtradb-cluster-operator:PR-891-d04b4b81

Test name
Status

scaling
passed

big-data
passed

recreate
passed

upgrade-haproxy
passed

storage
passed

haproxy
passed

scheduled-backup
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

monitoring-2-0
passed

smart-update
passed

self-healing-chaos
passed

affinity
passed

one-pod
passed

self-healing-advanced
passed

auto-tuning
passed

self-healing-advanced-chaos
passed

demand-backup
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
passed

users
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

pitr
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/891/commits/982872a865575c301d3d67efb21aed89fba457a6
image: perconalab/percona-xtradb-cluster-operator:PR-891-982872a8

Test name
Status

recreate
passed

scheduled-backup
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

pitr
passed

upgrade-haproxy
passed

big-data
passed

scaling
passed

scaling-proxysql
passed

security-context
passed

storage
passed

self-healing
passed

self-healing-chaos
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/891/commits/982872a865575c301d3d67efb21aed89fba457a6
image: perconalab/percona-xtradb-cluster-operator:PR-891-982872a8

Test name
Status

storage
passed

upgrade-haproxy
passed

recreate
passed

scaling
passed

haproxy
passed

big-data
passed

scheduled-backup
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-chaos
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
passed

self-healing-advanced
passed

affinity
passed

one-pod
failed

self-healing-advanced-chaos
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

upgrade-consistency
passed

users
passed

operator-self-healing-chaos
passed

tls-issue-self
passed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/891/commits/15b53dfd89bc2946b6eff23032c602ae93a902f3
image: perconalab/percona-xtradb-cluster-operator:PR-891-15b53dfd

Test name
Status

haproxy
passed

storage
passed

scheduled-backup
passed

recreate
passed

upgrade-haproxy
passed

big-data
passed

scaling
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

security-context
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

self-healing-chaos
passed

limits
passed

demand-backup
passed

smart-update
passed

monitoring-2-0
passed

self-healing-advanced
passed

affinity
passed

one-pod
passed

self-healing-advanced-chaos
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

operator-self-healing
passed

users
passed

upgrade-consistency
passed

operator-self-healing-chaos
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

demand-backup-encrypted-with-tls
failed

tls-issue-cert-manager-ref
passed

validation-hook
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/891/commits/2cd3e8fd133873d1fc3ffa6f1c2666008b753d10
image: perconalab/percona-xtradb-cluster-operator:PR-891-2cd3e8fd

Test name
Status

storage
passed

self-healing
passed

self-healing-chaos
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

haproxy
passed

big-data
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

upgrade-haproxy
passed

scaling
passed

auto-tuning
passed

scaling-proxysql
passed

proxysql-sidecar-res-limits
passed

security-context
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

scheduled-backup
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/891/commits/2cd3e8fd133873d1fc3ffa6f1c2666008b753d10
image: perconalab/percona-xtradb-cluster-operator:PR-891-2cd3e8fd

Test name
Status

storage
passed

haproxy
passed

big-data
passed

scheduled-backup
passed

recreate
passed

upgrade-haproxy
passed

scaling
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-chaos
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
failed

self-healing-advanced
passed

affinity
passed

one-pod
passed

self-healing-advanced-chaos
passed

auto-tuning
passed

pitr
passed

operator-self-healing
passed

proxysql-sidecar-res-limits
failed

upgrade-consistency
passed

operator-self-healing-chaos
passed

demand-backup-encrypted-with-tls
failed

users
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/891/commits/cfa5b3249ae0f36a2dea3a2216d5ff8a8c6229a6
image: perconalab/percona-xtradb-cluster-operator:PR-891-cfa5b324


Expose available modules, extensions, and other server configurations in server endpoint

 Issue by landonreed
Friday Nov 16, 2018 at 17:21 GMT
Originally opened as https://github.com/catalogueglobal/datatools-ui/issues/258

Instead of duplicating configuration data in both the server and UI repos, use the appInfo endpoint to inform the UI of the available modules/extensions that it can utilize.
Originally posted by @skinkie in https://github.com/catalogueglobal/datatools-ui/issues/217#issuecomment-404514565

:tada: This issue has been resolved in version 4.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: