[Enhancement] Ways to configure Filters are confusing.

Is your feature request related to a problem? Please describe.
Currently, there are two ways to configure Filters in EhPanda:

Setting --> Account --> Account configuration
Setting --> General --> Filters

According to my test, it seems that:

Filters configured in the first way only filters gallerys showing up in Frontpage, Popular and Watched.
Filters configured in the second way only filters gallerys showing up in search results.

This is never mentioned in the app or any online documentation, and it's kind of frustrating.
Describe the solution you'd like
Remove the second way and provide a new way to apply Filters and other Advanced Options when searching. This is exactly what the E-Hentai website is doing.
Describe alternatives you've considered

Explain in the app about how these settings applies to certain circumstances, so users won't get confused.
Do nothing, let users find it out themselves.

Additional context
None.

Yes, putting Filters setting there is quite confusing.
In previous versions, the entry button of Filters setting positioned inside the search bar, it was much easier to infer its usage.
But since I replaced the search bar with the brand new .searchable(), it seems impossible to put a button inside, I thought about using a keyboard toolbar item instead, but the toolbar won't show up if the keyboard is summoned by .searchable(), so I have to put the entry inside the general setting temporarily.
About the "account configuration", it actually means E-Hentai settings, it should not be regarded as a Filters setting.
Thanks for your advice, I appreciate it.

About the "account configuration", it actually means E-Hentai settings, it should not be regarded as a Filters setting.

I don't think that's correct. Because you can configure what categories to show in E-Hentai settings:

For example, if we choose not to show Misc in E-Hentai settings, then those gallerys categorized as Misc won't be shown on the front page and in searches by default. This is not what EhPanda behaves currently. Filter changes made in E-Hentai settings don't apply in searches. If users want the same experience as the E-Hentai website in EhPanda, they have to manually configure EhPanda's own Filter to match the E-Hentai website's settings.

But since I replaced the search bar with the brand new .searchable(), it seems impossible to put a button inside, I thought about using a keyboard toolbar item instead, but the toolbar won't show up if the keyboard is summoned by .searchable(), so I have to put the entry inside the general setting temporarily.

It's just a little glitch, though. I'm perfectly fine with the temporary situation. I really appreciate your effort in making EhPanda a better piece of software.

Done. 489dbbd2fd2ed284671a3cb892efe26ce5e5a74b


node deselect config option

added option to disable node deselection on second click

Many thanks for this solution @rafalzmuda :)


[1.19] Enchantment Applicator not displaying essence level correctly

Industrial Foregoing Version: industrial-foregoing-1.19.2-<IP_ADDRESS>-5.jar
Titanium Version: titanium-1.19.2-3.7.3-27.jar
Crashlog If Applicable (Upload to pastebin/gist):
When using the enchantment applicator with a tank full of essence beside it pulling in the essence, it gets to the halfway point of filling the applicator and then it starts blinking (showing empty) until I turn off "pull" and then it displays the actual amount in the applicator until I turn pull on again..I have to keep turning pull on/off to see the actual amount in the applicator and if I leave the gui for the applicator and go back in, it shows empty until I toggle one of the input directions.

This should be fixed already


Bad signature for getPartitionOffset in base_consumer.js line 95

Hi Guys,
i want to share with you, an issue that i'm having in my current project.
I got "OffsetOutOfRange" when i was consuming topic from a specific Offset, so i want to handle this by moving to the first Offset in this topic, i set the option for my KAFKA consumer to Kafka.EARLIEST_OFFSET, but my consumer doesn't move to the first offset in case of ERROR "OffsetOutOfRange".
Then i checked in the library code, and found  that there's a bad signature for the function that's setting the parameter.
The function support 4 parameters, while in the library there's 5 parameters, the parameter Time is always set to NULL in that line, so in case of "OffsetOutOfRange", it's always moving to the last offset.
I'm using library version 3.2.8.
Best Regards.

Thanks, fixed in 3.2.9


Swagger doesn't generate definitions for Mono<ResponseEntity<User_Defined_class>> classes

Hi. I've just upgraded to 3.0.0-SNAPSHOT and noticed that Swagger doesn't generate definitions for response types like Mono<ResponseEntity<User_Defined_class>>. Here is an example:
fun getFullData(@RequestBody request: Request): Mono<ResponseEntity<Response>>

For this method Swagger generates no definition:

Resolver error at definitions.Service response model.properties.techData.$ref
Could not resolve reference: Could not resolve pointer: /definitions/ResponseTechData does not exist in document

/api-docs url with swagger.json also doesn't contain models that are properties of Response class. When I removed reactive Mono type and left response type as ResponseEntity everything was working fine. I also checked that simple reactive types like Mono also work and their definitions are generated by Swagger as well. So the problem is precisely when a type is a reactive type wrapping Spring Web Response Type wrapping custom classes.
Is there a way to specify Springfox how to unwrap specific types?

There is a solution proposed at https://github.com/springfox/springfox/issues/2858


readFile on android

Hello,
I got a trouble when using fs.readFile with encoding is utf8.
RNFetchBlob.fs.readFile(path, 'utf8').then((data) => {
      socket.emit('Upload', { 'Name' : filename, Data : data });
})

It read file to string and then send to server via socket io.
On server, Im using fs.write(filename,data,null,'binary') to storage file.
ps:It only works fine on ios.
Thanks,

@naviocean , I think this is similar to #247. As an alternative, you can read the file into base64 encoded string and write the string this way on server
fs.write(dest, base64Str, {encoding: 'base64'}, function(err) {
  // callback
})

I've just change to base64
RNFetchBlob.fs.readFile(source.uri, 'base64').then((data) => {
              socket.emit('Upload', { 'Name' : filename, Data : data });
            });

and backend change to
fs.write(path, data['Data'], {encoding: 'base64'}, function(err) { .. });
However, the new image file is incorrect, can not see.

I've change a litte on my backend and now it works fine.
Thanks for your support


Fix warnings on iOS 9

This makes all warnings go away in iOS 9 and iOS 8

:+1: Thank you @stefanmunz!


[Web] How to enbed other web content inside a flutter web project?

In a normal flutter project you would use webview to embed external html/css/javascript. How is this done with flutter web?

There's an index.html inside the web dir. I believe that's where you embed.

Closing as this seems to be a future feature.


fix initial sizing, fix erroneous sizing on iOS

when page loaded in landscape orientation and then the user touches and
drags down and quickly up, sometimes iOS repaints to the wrong
dimensions after we’ve resized our target. the webvradapter schedules
one additional check on iOS for this condition and forces a resize to
the available dimensions.

lgtm


uade: init at 2.13

Motivation for this change
Things done

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

[X] NixOS
[ ] macOS
[X] other Linux distributions

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

Result of nixpkgs-review pr 123723 at 8a86b7c2 run on x86_64-linux 1

2 packages built successfully:

tests.trivial
uade

3 suggestions:

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/applications/audio/uade/default.nix:24:5:
   |
24 |     license = licenses.gpl2;
   |     ^

warning: build-tools-in-build-inputs
which is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/audio/uade/default.nix:10:3:
   |
10 |   buildInputs = [ pkg-config which libao ];
   |   ^

warning: build-tools-in-build-inputs
pkg-config is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/audio/uade/default.nix:10:3:
   |
10 |   buildInputs = [ pkg-config which libao ];
   |   ^

Hmm I just noticed, we had already packaged uade123. I was confused.


SONARMSBRU-79: added placeholders to default config file for server credentials

Simplifies the user experience for users who have authentication enabled.
I don't think we want to provide suggested values in the placeholders. By default, authentication is turned off so only users who have enabled authentication will need them, and it's up to them which account they want to use.

LGTM


Remove websocket-client and future from requirements

These packages are no longer required now that websocket support has been removed.

/morph test


Configurable id for actual input field

I could not find anything so I decided to open an issue for this.
The component renders the visible <input type="text" placeholder="Add a tag"> that is being used to allow user input. It would be nice to be able to give this element an ID through configuration as well in order to be able to click a <label for="id-of-visible-input-field"> to get the focus of the field. This would e.g. make selenium specs way easier because it is more simple to select the input field (either through the label or the id of the field directly).

Agree with @pduersteler and was going to open an issue as well. I'm trying to do something like this:  @tag-added="focus('input_id')" where input_id is the next seachable tag input. It make it easier for the user to hop from one to another without having to use the mouse.

Added in the latest release. The new prop is called input-id.


fix: tx events query condition

:tada: This PR is included in version 1.188.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Save few more bytes by nudging y

nice catch. I've slowly been finding these in my old solutions from before the viewport nudging clicked, there's probably a couple more instances of this so be on the lookout 🔎


169849 - [Newsroom][Site Features and Functionality] - Subject Topic Pages - Newscards dates not translated

Severity - 3 - Medium
Steps to Reproduce: | Analysis & Proposed Solution: | Location of the Element:
Navigate to Legacy Page and Migrated Page:
Legacy:
https://newsroom.accenturebr.com/br/subjects/accenture-corporate
Migrated:
https://main--accenture-newsroom-br--hlxsites.hlx.page/br/subjects/accenture-corporate
Actual Result:

Expected Result:

Azdo link - https://dev.azure.com/accenturecio26/WebContentDigAssetMgmt_PR1093/_workitems/edit/169849
CC: @ravkiran @amol-anand @raymond-h-dev

Closing the bug, this will fix by this PR https://github.com/hlxsites/accenture-newsroom/pull/240


Stick some things in margins and fill out all the todos in "basics"

Also change the simulation used, so that in future we can make an SPR animation.
This completes the "Tree Sequence basics" tute 🍾

Good spots both. Fixed brackets and removed "multifunction".


Revert "video_calls: Drop VIDEO_ZOOM_TESTING_ configurations."

This reverts commit e43373cc1feaead7dc8521406c9cbfa28d96f62f (#20557) to prepare for another Zoom security test.

Sure.  And Tim's comment last time was, of course, prescient, since this seems like it will be coming back up on a regular cadence.

Holding merge until we find out if this path is actually going to be necessary, see Ops stream.

Closing as this didn't seem to be necessary for Zoom's review after all.


helm install missing namespace

it seems that the helm install command doesn't specify the newly created gpu-operator-resources namespace in it, and ends up in default

@nwalker-nvidia
On which EGX version are you seeing this issue ?
Please follow the 4.2 version
Thanks,
Anurag G

Closing the thread as there's no activity more than 30 days


Cleanup skipping implemented on pytest level

Generic cleanup skipping without a need to explicitly handle it in
fixtures. On the other hand uses private access == unstable interface
that can stop working one day.

I do not like this approach.
* It adds more magic done in the background

It doesn't, the discovery of this included some magic, the result is free of any incantation.

* It switches current behaviour and applies it globally

It does it right.

* It relies on pytest internals and the code is complicated

True, it relies on pytest internals and it can break in future, real problem (like with persistence, with which it this is supposed to be used primarily/exclusively; actually can be implemented as part of persistence). However the code is simple and crystal clear (stack structure is not, can be documented), placed on one place and less than 50 lines long.

* There are some finalizers/yields you always want to execute regardless of skip_cleanup and I do not see a way how to do it

Maybe... (thinking about this)

  * e.g. api_client/prod_client, where you always want to close the client and clean sessions.

Personally I did never care this particular one. :-) Nowadays I am more mature and I understand that it can cause slight troubles on server side, however still do not care. :-)


ensure OCI artifacts are handled strictly by digest

Currently artifact revision (i.e. digest) is obtain here:
https://github.com/fluxcd/source-controller/blob/53ee3a3db056b4c024d30a735607b3bccbcde54b/internal/controller/ocirepository_controller.go#L392-L393
It is also observed as a condition here:
https://github.com/fluxcd/source-controller/blob/53ee3a3db056b4c024d30a735607b3bccbcde54b/internal/controller/ocirepository_controller.go#L408-L417
However, verification and fetching is only done by URL, and it's possible there is an update in registry in between all of these calls:
https://github.com/fluxcd/source-controller/blob/53ee3a3db056b4c024d30a735607b3bccbcde54b/internal/controller/ocirepository_controller.go#L431
https://github.com/fluxcd/source-controller/blob/53ee3a3db056b4c024d30a735607b3bccbcde54b/internal/controller/ocirepository_controller.go#L455-L456
There maybe other race coditions. It will be easy enough to address this and reinfoce use of the same digest for all of the registry API calls.

We could make getRevision rerun also the digestURL and pass that to all sequential functions.

https://github.com/fluxcd/source-controller/pull/1244 will changed some of the underlying code, but this flow remains intact.

We could make getRevision return also the digestURL and pass that to all sequential functions.

Exactly. I would also want to check how artifacts are stored as well, as I'm not familiar with that part yet.

Flux has an internal artifact format common to all source types which is a gzip tarball with stripped file header info. The digest of a Flux artifact is advertised in .status.artifact.digest and all consumers (kustomize-controller, helm-controller, tf-controller, etc) verify the integrity of the artifact before the contents is extracted. The internal artifacts acquisition and verification is handled by https://github.com/fluxcd/pkg/blob/main/http/fetch/archive_fetcher.go.


Gogoro app crash  [NSBundle mainBundle]

This error starts with Electra
Also appeared in Unc0ver
Someone pointed out that it seems to be a problem with [NSBundle mainBundle]
Please refer to here https://github.com/hirakujira/TweakInjector_delay

Not jailbreak related, closing.


Make the package less of a monolith

Quick note from the Jupyter call today

@mpacer mentioned that a simple update to setup.py could make the tool runnable via nbconvert
I mentioned that breaking up the rather monolithic exporter + preprocessor setup that we have right now to make parts reusable independently (if there's value in that). The gotcha is that REST API calls to Confluence have to be made at various phases of the process to image version lookup, page version lookup, etc.

Delayed submit and I crossed the streams a bit with #3. Thanks @mpacer!

The gotcha is that REST API calls to Confluence have to be made at various phases of the process to do image version lookup

This at least is not true in my environment.  For issue #30, I simply removed the lookup of the URL and use the attachment filename as in <ri:attachment ri:filename="{{ ... }}"/>.  That means that there are parts of the pre-processor that may not be necessary.
Since the other mechanism for doing confluence attachments is needed, I suggest that the template path be also a traitlet, so that people can use different templates for their own confluence.


Use an unsigned type for JSON printer flags

When using the provided API to set multiple JSON-printer flags via flatcc_json_printer_set_flags()
some compilers and tools will give errors due to a bitwise operation on a signed integer type.
The provided flags are an enum and in C enums are signed (C99 <IP_ADDRESS>p2).
Since C doesn't mandate how to represent a negative signed value (one's complement/two's complement/..)
there is no portable way to do bit operations on signed values.
When a user wants to set multiple flags using bitwise OR with the provided flags this gives errors in the user code indicated by tools like clang-tidy. See the checker:
https://releases.llvm.org/10.0.0/tools/clasng/tools/extra/docs/clang-tidy/checks/hicpp-signed-bitwise.html
This PR proposes the use of unsigned int flags instead of an enum,
which avoids having problems in the usercode when using this library.
An example project that triggers the issue:
https://github.com/bjosv/flatcc-experiments/tree/main/issues/enums
see comment.
A C++ reference regarding the use of unsigned types for bit manipulations:
https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-unsigned

From memory I think this issue has been up before. If I remember correctly enums are so widely used in flatcc that is not practical to change to unsigned constants. Fixing the JSON printer would in that case only be a band aid.
There should be an issue discussing this somewhere.

You can see an example below:
The solution is to cast wherever logical operations are applied is shown in the comment. Note that this isn't cosmetic - it is potentially undefined behavior or something along this lines.
https://github.com/dvidelabs/flatcc/issues/231#issuecomment-1122449195
quote
index 96d4b94..09b98d3 100644
--- a/src/compiler/semantics.c
+++ b/src/compiler/semantics.c
@@ -617,7 +617,7 @@ static int analyze_struct(fb_parser_t *P, fb_compound_type_t *ct)
     }

     ct->symbol.flags |= fb_circular_closed;
-    ct->symbol.flags &= ~fb_circular_open;
+    ct->symbol.flags &= (uint16_t)~fb_circular_open;
     ct->order = P->schema.ordered_structs;
     P->schema.ordered_structs = ct;
     return ret;```

Note: I would not mind a PR that fixes this, but it is presumably a LOT of work to cover all the enums.

If I remember correctly enums are so widely used in flatcc that it is not practical to change to unsigned constants.

I have seen the use of enums in many places, but I guess the issue is only given when it's used as a flag by the user, which I haven't seen that many cases of.
Possibly when using flatcc_builder_buffer_flags which we haven't used, but maybe that is another candidate that also should be changed in this case..

Well, a limited fix to user facing flags would be fine. After all, internal use can, and have, been handled with casts.
Of course it might affect users as the interface would break slightly, but that is OK.
We just need to make sure we find all the cases. Both JSON printer and parser at least, and probably several places in the builder / emitter / allocator. I.e. inspection of all header files in include/flatcc.

As to your PR, I think the proposed changes are fine as far as they go. I am just wondering if we should use a fixed size type instead of unsigned int since unsigned int could technically be too small for some values on some (hypothetical) compilers. We could also consider adding a typedef for the flag type. The generated code with flatbuffer schema enums does something similar.

Sounds good, I can add commits with changes for flatcc_builder_buffer_flag and flatcc_json_parser_flags to this PR as well, unless you want to have it separate or do it yourself. There might be more that these two, but I'll take a deep dive..
For the type I'm open for suggestions I you prefer any, or have some previous pattern.

Please go ahead. I think one PR is fine - if it becomes huge, maybe more would be needed. Note that I generally squash the PR into master.

If you have 3 clean commits for printer, parser and buffer I would use those over squashing.

Wrt type
I'm thinking something like
typedef uint32_t flatcc_json_parser_flags_t;
but may also be uint16_t depending on the type used internally. If values are close to limit the type may have to be larger for future extension.

I could only find the printer, parser and buffer enums which now is replaced.
The buffer flag has a size dependency to the internals but should be covered by a static assert (which seems to be covered the portability layer), but the placement of it can maybe discussed..

Yes, I looked through the code, can say if it is all correct, test must confirm that, but it looks solid.
I also noticed the static assert. I'm not sure if it is necessary and if the null pointer cast is sufficiently portable.
Note: if you can the run the test with clang and gcc on Linux it would be good since only appveyor windows CI/CD is currently working. I'll check MacOS.

I have run fine with:
11333  2022-10-18 18:30:33  ./scripts/test.sh\n
11334  2022-10-18 18:30:50  CXX=clang++ CC=clang ./scripts/test.sh\n

on Linux (Ubuntu 22.04.1 LTS) with:

Ubuntu clang version 14.0.0-1ubuntu1
g++ (Ubuntu 11.2.0-19ubuntu1) 11.2.0

I'm not that familiar with appveyor, is it better than githubs CI? Might have to look into that.
Regarding the assert then I was suddenly thinking if it should be moved away from the "public" headers that users includes, since its an internal thing. Maybe it can trigger warnings in usercode by some static tool..
But its nice to have something since I add the cast, which would hide a single handed changes in the future.

Well, we can leave until someone complains ...
Appveyor is for historical reasons - the only way to test on Windows. Travis was used fo MacOS & Linux Clang & GCC, but they changed their API/URL and I never got to update.
The plan is to move to Github now that that is available. There is a vacant position for that ...

Sure, sound good regarding the assert.
I ran clang-tidy on it with big bunch of checks and current seems fine.
Aha, yes, a lot of projects had to move from travis. Github supports windows and mac as well.. so if I'm bored by other things the I know where to look :)

Ah ok, windows is not my strong side, have only setup simple jobs..
Thanks for your effort with this project, and being so quick to respond!

Thanks. Anyway, a GH build for just Linux would  also be valuable.


Mark currently broken tests as such

All JLL packages formally depends on Pkg, including the new ones that don't
actually load it.  However, in Julia nightly Pkg has an indirect dependency on
LibCURL_jll and MozillaCACerts_jll, which means that installed_jlls in
setup_dependencies always contains these two packages, see
https://github.com/JuliaPackaging/BinaryBuilderBase.jl/blob/c4c7c838ad8cc2b134d0a46551497ef92f9a9e68/src/Prefix.jl#L411-L414
This changeset is to temporarily ignore the failing tests, for the sake of
keeping the test suite working, until this is properly resolved.
CC: @staticfloat

Closing in favour of #58


InputDecorationTheme.isCollapsed doesn't seem to work

Is there an existing issue for this?

[X] I have searched the existing issues
[x] I have read the guide to filing a bug

Steps to reproduce
I want to set TextField default collapsed in ThemeData. However, setting InputDecorationTheme.isCollapsed doesn't work. However, InputDecoration.isCollapsed is working.
Expected results
The TextField should be collapsed when InputDecorationTheme.isCollapsed is set to true.
Actual results
The TextField is not collapsed when InputDecorationTheme.isCollapsed is set to true.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MainApp());
}

class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(
        inputDecorationTheme: const InputDecorationTheme(
          isCollapsed: true, // This doesn't work
          border: OutlineInputBorder(
            borderRadius: BorderRadius.all(Radius.circular(4)),
          ),
        ),
      ),
      home: const Scaffold(
        body: Center(
          child: SizedBox(
            width: 200,
            child: TextField(
              decoration: InputDecoration(
                // isCollapsed: true, // <-- This works
                hintText: 'Hello, Flutter!',
              ),
            ),
          ),
        ),
      ),
    );
  }
}

Screenshots or Video
No response
Logs
No response
Flutter Doctor output
Doctor output
[Paste your output here]

Hi @akshdeep-singh. Thanks for filing this issue. I am able to reproduce this on the latest master and stable channels.
stable, master flutter doctor -v

[✓] Flutter (Channel stable, 3.13.0, on macOS 13.0 22A380 darwin-arm64, locale
    en-NG)
    • Flutter version 3.13.0 on channel stable at
      /Users/damilolaalimi/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision efbf63d9c6 (7 days ago), 2023-08-15 21:05:06 -0500
    • Engine revision 1ac611c64e
    • Dart version 3.1.0
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/damilolaalimi/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

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

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

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

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

[✓] Connected device (4 available)
    • Damilola’s iPhone (mobile) • 71c843fa5f3dec767999f36224653c0faa78660e •
      ios            • iOS 16.6 20G75
    • iPhone 8 (mobile)          • 218697C0-911E-4F4E-9568-C387ACB184ED     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-arm64   • macOS 13.0 22A380 darwin-arm64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 116.0.5845.110

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[✓] Flutter (Channel master, 3.14.0-9.0.pre.27, on macOS 13.0 22A380 darwin-arm64, locale en-NG)
    • Flutter version 3.14.0-9.0.pre.27 on channel master at /Users/damilolaalimi/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision e085e613c8 (25 hours ago), 2023-08-22 02:58:24 -0400
    • Engine revision e183e8a940
    • Dart version 3.2.0 (build 3.2.0-94.0.dev)
    • DevTools version 2.26.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/damilolaalimi/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

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

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

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

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

[✓] Connected device (4 available)
    • Damilola’s iPhone (mobile) • 71c843fa5f3dec767999f36224653c0faa78660e • ios            • iOS 16.6 20G75
    • iPhone 8 (mobile)          • 218697C0-911E-4F4E-9568-C387ACB184ED     • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)            • macos                                    • darwin-arm64   • macOS 13.0 22A380 darwin-arm64
    • Chrome (web)               • chrome                                   • web-javascript • Google Chrome 116.0.5845.110

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Was able to fix this, should I write new tests or modify existing ones to incorporate this?

@dam-ease please do look through the PR


get a sphere noise point around the target

i use the default params ,preprocessed data using colmap script by you and train on my data,but get this strenge results:the target is good except the points around.

I note i have choose interes area,maybe i make the interest area too small?If so,why other scene works well? any advice?

Hello, yes the strange sphere looks outside the region of interest. I have just done a hack to this issue - could you try this extract_fields function below (to replace the original extract_fields function at L10 of models/renderer.py) and re-extract the mesh from your trained model again? Thanks!
def extract_fields(bound_min, bound_max, resolution, query_func):
    N = 64
    X = torch.linspace(bound_min[0], bound_max[0], resolution).split(N)
    Y = torch.linspace(bound_min[1], bound_max[1], resolution).split(N)
    Z = torch.linspace(bound_min[2], bound_max[2], resolution).split(N)

    u = np.zeros([resolution, resolution, resolution], dtype=np.float32)
    with torch.no_grad():
        for xi, xs in enumerate(X):
            for yi, ys in enumerate(Y):
                for zi, zs in enumerate(Z):
                    xx, yy, zz = torch.meshgrid(xs, ys, zs)
                    pts = torch.cat([xx.reshape(-1, 1), yy.reshape(-1, 1), zz.reshape(-1, 1)], dim=-1)
                    dis = torch.linalg.norm(pts, ord=2, dim=-1, keepdim=False)
                    val = query_func(pts).reshape(-1)
                    val[torch.where(dis > 1.0)] = -1.0
                    val = val.reshape(len(xs), len(ys), len(zs)).detach().cpu().numpy()
                    u[xi * N: xi * N + len(xs), yi * N: yi * N + len(ys), zi * N: zi * N + len(zs)] = val
    return u

i replace the function:answer is :reduce noise in the top  ,but still have the noise

Hello, yes the strange sphere looks outside the region of interest. I have just done a hack to this issue - could you try this extract_fields function below (to replace the original extract_fields function at L10 of models/renderer.py) and re-extract the mesh from your trained model again? Thanks!
def extract_fields(bound_min, bound_max, resolution, query_func):
    N = 64
    X = torch.linspace(bound_min[0], bound_max[0], resolution).split(N)
    Y = torch.linspace(bound_min[1], bound_max[1], resolution).split(N)
    Z = torch.linspace(bound_min[2], bound_max[2], resolution).split(N)

    u = np.zeros([resolution, resolution, resolution], dtype=np.float32)
    with torch.no_grad():
        for xi, xs in enumerate(X):
            for yi, ys in enumerate(Y):
                for zi, zs in enumerate(Z):
                    xx, yy, zz = torch.meshgrid(xs, ys, zs)
                    pts = torch.cat([xx.reshape(-1, 1), yy.reshape(-1, 1), zz.reshape(-1, 1)], dim=-1)
                    dis = torch.linalg.norm(pts, ord=2, dim=-1, keepdim=False)
                    val = query_func(pts).reshape(-1)
                    val[torch.where(dis > 1.0)] = -1.0
                    val = val.reshape(len(xs), len(ys), len(zs)).detach().cpu().numpy()
                    u[xi * N: xi * N + len(xs), yi * N: yi * N + len(ys), zi * N: zi * N + len(zs)] = val
    return u

here is the validate_image,it is perfect .


Webpack TypeScript types don't export 'Mode'

Bug report
What is the current behavior?
Writing Webpack v5 configuration methods cannot be typed correctly:
function vendors({ mode }: { mode: string }): Configuration {
  return {
    mode,    // Type 'string' is not assignable to type 'Mode'.ts(2322)
    entry: {
      vendor: [npmExportsFile],
    },
    output: {
      filename: '[name].[contenthash:8].packages.js',
      library: '[name]_packages',
      path: OUTPUT_DIR,
      publicPath: PUBLIC_PATH,
    },
    plugins: [
      new webpack.DllPlugin({
        name: '[name]',
        path: path.join(OUTPUT_DIR, '[name].json'),
      }),
    ],
  }
}

What is the expected behavior?
Because Mode is not exported, it can't be used as the type in the above type signature instead of string here
Other relevant information:
webpack version:  5.4.0
Node.js version: 15.1.0
Operating System: Linux x86_64
Additional tools: Typescript v4.0.5

You don't need the type. Pass "development" or "production". If you want to declare a type for it use: { mode: "development" | "production" }

@sokra oof, duplicating the type seems really Gross

You can get the Mode type using Configuration["mode"]


terraform, gcp: node pool creation followup issue diagnosis and resolution

When creating a cluster today using an updated master branch (with changes to terraform logic from #2762), the core node pool was successfully created, but the user notebook node pools were not.
Extract from terraform apply
  # google_container_node_pool.core will be created
  + resource "google_container_node_pool" "core" {
      + location                    = "southamerica-east1"
      + name                        = "core-pool"
      + node_locations              = (known after apply)

  # google_container_node_pool.notebook["large"] will be created
  + resource "google_container_node_pool" "notebook" {
      + location                    = (known after apply)
      + name                        = "nb-large"
      + node_locations              = [
          + "southamerica-east1-c",
        ]

google_container_node_pool.core: Creation complete after 1m52s [id=projects/catalystproject-392106/locations/southamerica-east1/clusters/latam-cluster/nodePools/core-pool]

│ Error: Cannot determine zone: set in this resource, or set provider-level zone.
│
│   with google_container_node_pool.notebook["large"],
│   on cluster.tf line 238, in resource "google_container_node_pool" "notebook":
│  238: resource "google_container_node_pool" "notebook" {
│
╵

Analysis
It seems like core nodes and user nodes are configured differently, where core nodes get location set, while user nodes get node_locations set, and it seems that it causes a failure for user nodes.
I opened #2769 about the possibly non-optimial situation of having core nodes not configured to the locations where user nodes run.
Trial
It seems that what was needed for things to work was to add the following config to the user node pools, which is already configured for the core pool:
location = google_container_cluster.cluster.location

Will get this resolved with a PR soon.

I thought @yuvipanda fixed that yesterday

@pnasrat I used a local branch with #2758 merged and experienced this still. I think there can be a difference between making terraform updates vs creating something from scratch as I did now.
I assume that whenever node_locations (a list of zones) are specified, you also need to specify location (a region).


[fetch] Better feature detection for FormData/FileReader/Blob

This PR bumps fetch to 0.9.0, the latest release and fixes broken feature detection originating in that self is not referring to window.self but an empty object. Assigning that object to window.self or GLOBAL won't work in the chrome dev tools because of CORS restrictions. This is a pragmatic solution but maybe not ideal.
Background to the problem can be read here: https://github.com/facebook/react-native/issues/2376

Seems good to me. Someone on the fb side will need to merge and test against their apps.

@facebook-github-bot shipit

:wave: anything I can help with to move this along?

@facebook-github-bot shipit

Sorry about this, I was testing the import script and it failed. Now should land correctly

This is a fork of https://github.com/github/fetch, so these changes need to be made there too I believe. Otherwise when this fork is updated, these changes might be lost.

@paramaggarwal wow, you are right...


Make http and grpc ports configurable.

Signed-off-by: Milan Lenco<EMAIL_ADDRESS>

Coverage decreased (-0.02%) to 67.697% when pulling b9f676846b1a7bd4534dbfd6cd502933d0e0bcba on milanlenco:dev into 61dbafd59c535dbc222a4ce48dee5d481ead2aac on contiv:dev.


Fix a file descriptor leak when handling 404

Any non-nil HTTP client response needs to have
its .Body stream closed, otherwise the client socket
associated file descriptor is not closed also and
long-running processes end up in a deadly "too many files open"
state especially when they get a lot of "Image/container not found"
responses - pretty common. Think Docker Swarm - which is actually
the case where I was bit by this and which I used to verify
that the fix is working.
Signed-off-by: Mariusz Borsa<EMAIL_ADDRESS>

LGTM
ping @vieux

LGTM


Move spine defaults from spine.yaml to C++ params

The rationale for this update is to have a single source of truth for configuration defaults (rather than upkie.config in Python and parameter defaults in C++).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

96 of 103 (93.2%)  changed or added relevant lines in 5 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 90.016%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

upkie/cpp/actuation/tests/BulletInterfaceTest.cpp
55
56
98.21%

upkie/cpp/actuation/ImuUncertainty.h
7
13
53.85%

Files with Coverage Reduction
New Missed Lines
%

upkie/cpp/actuation/BulletInterface.h
1
88.33%

upkie/cpp/actuation/ImuUncertainty.h
1
70.37%

Totals

Change from base Build<PHONE_NUMBER>5:
0.1%

Covered Lines:
2813

Relevant Lines:
3125

💛  - Coveralls

After experimenting with this proposal, I feel it has more cons than pros. The merge does not simplify much code, and we actually rather lose on visibility at spine configuration time (e.g. printing out the configuration dictionary at reset becomes useless). Having the YAML file as the single source of truth would probably be better.


Changing Cost Of Sp

Hello, I was wondering if there was a way to change the cost of spells with sp, for instance say a spell cost 200 sp and you wanted to change it to 1 sp

Yes, that is the "worth" property of spells. So add something like this to spells.yml
blink:
  worth: 2

If a spell was inherited would I have to go back to the original?
accio:
worth: 5
category: charms
inherit: pull

No, anything you add to accio will always override whatever is in push.


Problem executing callback.py

I'm trying to train samplernn in Arch Linux in a venv in my home folder instead of running it inside Google Colab and I get the following error when running train.py:
Traceback (most recent call last):
  File "/home/vasya/work/prism/prism-samplernn/train.py", line 335, in <module>
    main()
  File "/home/vasya/work/prism/prism-samplernn/train.py", line 278, in main
    TrainingStepCallback(
  File "/home/vasya/work/prism/prism-samplernn/callbacks.py", line 17, in __init__
    self.model = model
    ^^^^^^^^^^
AttributeError: property 'model' of 'TrainingStepCallback' object has no setter

I used the default train command in the colab notebook for prism samplernn with a roughly 22 minute mono .wav file that has 48000 samples per second, chunked into 175 8 second chunks.  I have tried running both python and python3.

Hi @drillkicker,
I am the original author of the code, unfortunately I no longer work at PRiSM so I can only offer limited support. I suspect this is due to what looks like a recent change in TensorFlow/Keras - it seems the Callback class no longer has a model attribute, instead it's been renamed to _model. Hence the complaint about there being no setter.
Did the Notebook run OK, or did you just experience this issue on your own machine?

@relativeflux  I didn't test the command in the notebook because I'm not familiar with Colab and couldn't figure out how to import a wav file into it.  However, I tried running the code after editing the line with the error to say self._model instead of self.model and ran the same command.  I get a different error message this time:
Traceback (most recent call last):
  File "/home/vasya/work/prism/prism-samplernn/train.py", line 335, in <module>
    main()
  File "/home/vasya/work/prism/prism-samplernn/train.py", line 285, in main
    ModelCheckpointCallback(
  File "/home/vasya/work/prism/prism-samplernn/callbacks.py", line 79, in __init__
    super(ModelCheckpointCallback, self).__init__(*args, **kwargs)
  File "/home/vasya/work/prism/lib/python3.11/site-packages/keras/src/callbacks/model_checkpoint.py", line 183, in __init__
    raise ValueError(
ValueError: When using `save_weights_only=True` in `ModelCheckpoint`, the filepath provided must end in `.weights.h5` (Keras weights format). Received: filepath=./logdir/default/21.04.2024_14.36.58/model.ckpt-{epoch}

@drillkicker Hi - yes, it looks as if the new version of Keras (Keras 3) has a lot of breaking changes for the library. Keras 3 is a complete rewrite. As I said I no longer work as PRiSM, and it doesn't look as if anyone there is maintaining this code now, but I'll get in touch with them and see if I can update it. My apologies. I certainly want to get the library back into a useable condition.
If there isn't too much to work on I'll fork it and update it myself. :)

@relativeflux Thanks for your help.  I don't work with Python so this is beyond my abilities as a hobbyist but I will be tracking any updates on this.


Remove ROS arguments before passing to QApplication

Resolves #442

Linux
Linux-aarch64
macOS
Windows

In ROS 1 the init(int argc, char ** argv) function not only used the ROS specific arguments but also updated the arguments to leave only the non-ROS arguments. I think a similar function would be very helpful to avoid the overhead from this PR.

In ROS 1 the init(int argc, char ** argv) function not only used the ROS specific arguments but also updated the arguments to leave only the non-ROS arguments. I think a similar function would be very helpful to avoid the overhead from this PR.

Sounds reasonable to me. But we should be careful in this case, since we still want to pass the argv containing ROS arguments later in main:
https://github.com/ros2/rviz/blob/265dbb345584aff51c2586daba0c8f6e2aff4c21/rviz2/src/main.cpp#L75

Also see: https://github.com/ros2/rcl/issues/219


cmake / compilation problems (wrong compiler used)

Trying to compile flexbar I am consistently running into compilation issues. I'm using -DCMAKE_CXX_FLAGS to point to the location of our TBB installation and to add the -std=c++14 to the compiler.  However the compilation consistently fails and the problem seems to be, that the wrong compiler is uses:
$  which gcc
/ibios/tbi_cluster/13.1/x86_64/gcc/gcc-6.x/bin/gcc
$ which c++
/ibios/tbi_cluster/13.1/x86_64/gcc/gcc-6.x/bin/c++
$

but
$ cmake -DCMAKE_PREFIX_PATH=/tmp/flexbar-test -DCMAKE_CXX_FLAGS="-I/ibios/tbi_cluster/13.1/x86_64/tbb/tbb-2017.1/include" DCMAKE_C_COMPILER=`which gcc` .
-- The C compiler identification is GNU 4.8.1
-- The CXX compiler identification is GNU 4.8.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Flexbar 64 bit architecture
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.8")
-- Found BZip2: /usr/lib64/libbz2.so (found version "1.0.6")
-- Looking for BZ2_bzCompressInit in /usr/lib64/libbz2.so
-- Looking for BZ2_bzCompressInit in /usr/lib64/libbz2.so - found
-- Configuring done
-- Generating done
-- Build files have been written to: /home/thommen/projects/flexbar/flexbar-2.7.0
$

Note the wrong - because too old - compiler selected by cmake (/usr/bin/cc, /usr/bin/c++).  How can this be fixed?
frank

Note the wrong - because too old - compiler selected by cmake (/usr/bin/cc, /usr/bin/c++). How can this > be fixed?

Maybe try this one?
CC=/ibios/tbi_cluster/13.1/x86_64/gcc/gcc-6.x/bin/gcc CXX=/ibios/tbi_cluster/13.1/x86_64/gcc/gcc-6.x/bin/c++ cmake -DCMAKE_PREFIX_PATH=/tmp/flexbar-test -DCMAKE_CXX_FLAGS="-I/ibios/tbi_cluster/13.1/x86_64/tbb/tbb-2017.1/include" -DCMAKE_C_COMPILER=`which gcc`
Yes, I also see:
cd /tmp/flexbar-2.7.0_build/src && /usr/bin/x86_64-pc-linux-gnu-g++  -DSEQAN_HAS_BZIP2=1 -DSEQAN_HAS_ZLIB=1 -I/tmp/flexbar-2.7.0/include   -I/usr/include/seqan-2.2 -DNDEBUG -O2 -pipe -maes -mpclmul -mpopcnt -mavx -march=native -std=c++11   -o CMakeFiles/flexbar.dir/Flexbar.cpp.o -c /tmp/flexbar-2.7.0/src/Flexbar.cpp
In file included from /usr/include/seqan-2.2/seqan/basic.h:42:0,
                 from /tmp/flexbar-2.7.0/src/Flexbar.h:17,
                 from /tmp/flexbar-2.7.0/src/Flexbar.cpp:22:
/usr/include/seqan-2.2/seqan/platform.h:155:6: error: #error SeqAn requires C++14! You must compile your application with -std=c++14, -std=gnu++14 or -std=c++1y.
     #error SeqAn requires C++14! You must compile your application with -std=c++14, -std=gnu++14 or -std=c++1y.

but adding -std=c++14 does not help because cmake anyway adds afterwards its own -std=c++11

Is this issue still prevalent, also with version 3.0 of Flexbar?


Husdltkbot

Purpose

Finnish language documents, queries and answers
Does this introduce a breaking change?

[ ] Yes
[ x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

azd up for the first run then
azd deploy for successive rounds (update only the app)

What to Check
Verify that the following are valid

...

Other Information

Self-reviewed


Find or make more efficient photo optimisation tool

Sharp is quite good at what it does, but it's proving too slow and memory inefficient for this use case. Find or make an alternative that's more efficient, or change the way images are built.
One option is to make a CLI using one of the Rust libraries that can take both an input and an output file, and then use Bun to call that CLI with the filenames. I'd rather not try and figure out WASM, and from some pretty simple tests, the Rust libraries seem to be much faster at transforming images than the JS ones.
Since my use case is specifically transforming JPEG and PNG to AVIF, I can probably get rid of a lot of the other formats, and just use the pieces I need.

I've stopped converting to AVIF, so Sharp is fast enough now. I could theoretically try rewriting the whole thing in something like Go to get even more performance, but that's a different problem, so this issue can be closed.


Does not work with Storyboard TableView and AutoLayout

Hello,
I don't get it to work with a storyboard TableView and AutoLayout :(
I did some debugging and the _contentView always has a sizeof 0.0...
Any help on this?
Thanks,
Urkman

It is easy to reproduce:
1.) make the tableview in JPBParallaxTableViewController an Outlet and machete public
2.) Add TableView to the example storyboard and connect it to the Outlet
3.) Add 0 top, left, right and bottom margins to the TableView using Constrains
4.) run the example
There you see the Tableview has disappeared...

@Urkman Since this lib adds the tableview to the scroll view you can't add it to the view in the Storyboard. To work around this setup your storyboard with your tableview till everything is the way you like then drag the tableview up a leave so that it isn't contained in the view. Then create a IBOutlet to your tableview and return that tableview in the content view method like what is shown in the example.


Please explain - "The Group Policy setting Enterprise Spotlight does not work in Windows 10, version 1607"

It would be nice to know when this feature will be supported.

@pjahn Thank you for your suggestion. We can't comment on the release of future features, but the topic will be updated when this policy setting is available.


Source build failed MacOs go1.13.5 darwin/amd64

Having an issue compiling from source on - go1.13.5 darwin/amd64?
github.com/gohugoio/hugo/tpl/internal/go_templates/htmltemplate imports
	io/fs: malformed module path "io/fs": missing dot in first path element
github.com/gohugoio/hugo/cache/filecache imports
	github.com/spf13/afero tested by
	github.com/spf13/afero.test imports
	testing/fstest: malformed module path "testing/fstest": missing dot in first path element

You need go1.16.


Add accessible versions of 'sphinx' and 'native' styles

For the SymPy docs we have been using accessible variants of the 'sphinx' and 'native' styles. See https://github.com/sympy/sympy/blob/master/doc/src/_pygments/styles.py. I would love to be able to offload the maintenances of these custom styles to this project (or ideally to upstream them to Sphinx/pygments, but that's a harder task).
Here is the script that I used to generate them https://gist.github.com/asmeurer/d78409ea033aeeb764a11bb4acaeccc2. It is unfortunately very hacky and relies on a Ruby tool, so if there is better tooling in this repo, that would be preferable. I didn't see in this repo what tooling was used to generate/test these themes to ensure they are WCAG AA compatible.
These styles are notable because they are the default styles for the Furo Sphinx theme. "sphinx" is also the default style used in many other Sphinx themes including the default one. CC @pradyunsg

Thanks for looping me in @asmeurer! This project looks like a wonderful idea!
Regarding Furo...
The default color schemes that Furo uses are tango (light) and native (dark). These specific themes are used by Furo since... well...

They were the best-among-the-defaults themes, when I was looking, that didn't look out of place with rest of Furo's neutral backgrounds.
I didn't want to figure out how to write a pygments theme and bother adding yet-another-thing for me to maintain.

I'd happily eagerly adopt more accessible alternatives to those themes (they don't need to be equivalent even!) -- as long as the background color doesn't look out of place with Furo's neutral background colors. :)
Regarding the sphinx pygments theme...
That is typically used by most Sphinx documentation, since older versions of Sphinx would spew out a pygments_style = "sphinx" (or something like that) in their template generation. This has been removed in newer versions, falling back to theme defaults -- and multiple themes use sphinx as their default (as noted already!).
I'm pretty sure getting a more-accessible color scheme for sphinx upstreamed will be relatively straightforward -- although, it'll only be beneficial after a certain version of Sphinx, so having it be available via a third-party is still a very good idea.
PS: I see why "I'd write a shorter letter if I had more time" is a thing someone said. :)

Oh I didn't realize that the Furo default wasn't "sphinx", and it's only used because of the template generation. Sorry for misspeaking on that.
Just to be clear, "sphinx" itself is based on the "friendly" pygments style, with only a few small differences, most notably the yellow background, which messes with the color contrast of some of the friendly defaults. https://github.com/sphinx-doc/sphinx/blob/master/sphinx/pygments_styles.py

Hi guys! Thanks for opening this issue, I'll work in a first version for the variants scipy use and then we can iterate from there 😬. Do you have any preferred name for the themes?

We can definitely add these other themes - and it absolutely makes sense to reduce maintenance burden or at least unify tooling and infrastructure

(or ideally to upstream them to Sphinx/pygments, but that's a harder task).

This is definitely something I/we have talked about as well as discussed with other folks working on documentation infrastructure. Long-term I'd like to see this upstreamed, though that would require IMHO additional support infra to ensure later changes to the themes would not mess up the contrast and the such.
Thanks for your contribution & thoughts @asmeurer  and @pradyunsg

though that would require IMHO additional support infra to ensure later changes to the themes would not mess up the contrast and the such.

I hadn't thought about that. Is there a Python library that can compute the WCAG contrast ratio between two web colors? I found https://pypi.org/project/wcag-contrast-ratio/, but I don't know how accurate or up-to-date it is (it was last updated in 2015).
Maybe it would be useful to have a small Python library that can compute the contrast ratios of a Pygments theme, and maybe even produce a high contrast alternative (similar to the Ruby tool I used to generate the above themes). Pygments may also be interested in having this upstream (or maybe it already exists).

yup - I have not found such a library, so we might need to engineer something like that. There are also a couple of formulas one can use to calculate the contrast ratio, which impacts the compliance results (because we like making our lives harder).
Initially, we could write a lightweight script or so to check only contrast ratios and WCAG compliance during CI or the such as a good MVP.
Still doing some research on how to go about it and what other colour contrast checkers use for this, so stay tuned.


Segfault on writing file with no points

To reproduce:
    writer::named_file::config c({0.01,0.01,0.01}, {0.0,0.0,0.0});
    writer::named_file out(tempfile, c);
    out.close(); // <- Segfault

The issue is due to pcompressor never getting set as writePoints is never called. However, writing an empty file should be a valid operation.

Fix implemented in #139


Show images

Description
Fix the path to the images
Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which refactors the code base)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[x] My code follows the pre-commit style and check guidelines of this project.
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing tests pass locally with my changes
[x] I have added a summary of my changes to the CHANGELOG (not for minor changes, docs and tests).

Thanks @ineiti! Switching to src layout broke a number of links.


Detect blur event or when user returns to home screen?

Right now my app uses a websocket connection. I'd like to break it when the user minimizes the app and returns to the home screen. The blur event is not fired when this happens, but it is fired on Mozilla's webxr viewer. Is there a way I can detect when the user has minimzed the app? Thanks!

Thanks for filing! We'll get back to you with some more info after the holidays


[BugFix] fix hdfs cache pool

Fixes https://github.com/StarRocks/starrocks/pull/29020
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)


Add Tests for quantity under the cel pkg

What type of PR is this?
/kind feature
What this PR does / why we need it:
New tests are added to the cel package for the quantity.go file.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?
NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
NONE

Hey @wzshiming, can you take a look at this and let me know if this is good to go?


Standard example fails with "Data Bag Items must contain a Hash or Mash!"

Using the standard example from the cookbook readme fails with:
Data Bag Items must contain a Hash or Mash!
code:
chef_gem 'chef-vault'
include_recipe 'chef-vault'
...snip...
begin
  data_bag('credentials')
rescue
  ruby_block "create-data_bag-secrets" do
    block do
      Chef::DataBag.validate_name!('credentials')
      databag = Chef::DataBag.new
      databag.name('credentials')
      databag.save
    end
    action :create
  end
end

chef_vault_secret 'chef_server_password' do
  data_bag 'credentials'
  raw_data({'auth' => 'Forged in a mold'})
  admins ['admin']
  clients 'vm-chef-workstation'
  search '*:*'
  action :create
end

chef-client 12.0.0
Full stacktrace:
==> vm-chef-server: ================================================================================
==> vm-chef-server: Recipe Compile Error in /etc/chef-server/chef-solo-1/cookbooks/wlc-chef-server/recipes/upload.rb
==> vm-chef-server: ================================================================================
==> vm-chef-server:
==> vm-chef-server:
==> vm-chef-server: Chef::Exceptions::ValidationFailed
==> vm-chef-server:
==> vm-chef-server: ----------------------------------
==> vm-chef-server: Data Bag Items must contain a Hash or Mash!
==> vm-chef-server:
==> vm-chef-server: Cookbook Trace:
==> vm-chef-server: ---------------
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/data_bag_item.rb:75:in `raw_data='
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/data_bag_item.rb:126:in `from_hash'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/data_bag_item.rb:155:in `load'
==> vm-chef-server:   /etc/chef-server/chef-solo-1/cookbooks/chef-vault/libraries/chef_vault_item.rb:43:in `rescue in chef_vault_item'
==> vm-chef-server:   /etc/chef-server/chef-solo-1/cookbooks/chef-vault/libraries/chef_vault_item.rb:40:in `chef_vault_item'
==> vm-chef-server:   /etc/chef-server/chef-solo-1/cookbooks/wlc-chef-server/recipes/default.rb:53:in `from_file'
==> vm-chef-server:
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/mixin/from_file.rb:30:in `instance_eval'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/mixin/from_file.rb:30:in `from_file'
==> vm-chef-server:
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/cookbook_version.rb:245:in `load_recipe'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context.rb:169:in `load_recipe'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context.rb:138:in `block in include_recipe'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context.rb:137:in `each'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context.rb:137:in `include_recipe'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/dsl/include_recipe.rb:26:in `include_recipe'
==> vm-chef-server:   /etc/chef-server/chef-solo-1/cookbooks/wlc-chef-server/recipes/upload.rb:9:in `from_file'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/mixin/from_file.rb:30:in `instance_eval'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/mixin/from_file.rb:30:in `from_file'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/cookbook_version.rb:245:in `load_recipe'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context.rb:169:in `load_recipe'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context/cookbook_compiler.rb:140:in `block in compile_recipes'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context/cookbook_compiler.rb:138:in `each'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context/cookbook_compiler.rb:138:in `compile_recipes'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context/cookbook_compiler.rb:75:in `compile'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/run_context.rb:92:in `load'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/policy_builder/expand_node_object.rb:73:in `setup_run_context'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/client.rb:235:in `setup_run_context'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/client.rb:397:in `run'
==> vm-chef-server:
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application.rb:261:in `block in fork_chef_client'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application.rb:249:in `fork'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application.rb:249:in `fork_chef_client'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application.rb:215:in `block in run_chef_client'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/local_mode.rb:38:in `with_server_connectivity'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application.rb:201:in `run_chef_client'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application/solo.rb:245:in `block in interval_run_chef_client'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application/solo.rb:234:in `loop'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application/solo.rb:234:in `interval_run_chef_client'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application/solo.rb:224:in `run_application'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/lib/chef/application.rb:58:in `run'
==> vm-chef-server:   /opt/chef/embedded/apps/chef/bin/chef-solo:25:in `<top (required)>'
==> vm-chef-server:   /usr/bin/chef-solo:40:in `load'
==> vm-chef-server:   /usr/bin/chef-solo:40:in `<main>'
==> vm-chef-server:
==> vm-chef-server: Relevant File Content:
==> vm-chef-server: ----------------------
==> vm-chef-server: /opt/chef/embedded/apps/chef/lib/chef/data_bag_item.rb:
==> vm-chef-server:
==> vm-chef-server:  68:
==> vm-chef-server:  69:      def validate_id!(id_str)
==> vm-chef-server:  70:        self.class.validate_id!(id_str)
==> vm-chef-server:
==> vm-chef-server:  71:      end
==> vm-chef-server:
==> vm-chef-server:  72:
==> vm-chef-server:  73:      def raw_data=(new_data)
==> vm-chef-server:
==> vm-chef-server:  74:        unless new_data.respond_to?(:[]) && new_data.respond_to?(:keys)
==> vm-chef-server:  75>>         raise Exceptions::ValidationFailed, "Data Bag Items must contain a Hash or Mash!"
==> vm-chef-server:  76:        end
==> vm-chef-server:  77:        validate_id!(new_data["id"])
==> vm-chef-server:  78:        @raw_data = new_data
==> vm-chef-server:  79:      end
==> vm-chef-server:  80:
==> vm-chef-server:  81:      def data_bag(arg=nil)
==> vm-chef-server:  82:        set_or_return(
==> vm-chef-server:  83:          :data_bag,
==> vm-chef-server:  84:          arg,
==> vm-chef-server:
==> vm-chef-server:
==> vm-chef-server:
==> vm-chef-server: [2014-12-25T18:53:57+00:00] ERROR: Running exception handlers
==> vm-chef-server: [2014-12-25T18:53:57+00:00] ERROR: Exception handlers complete
==> vm-chef-server: [2014-12-25T18:53:57+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> vm-chef-server: [2014-12-25T18:53:57+00:00] ERROR: Data Bag Items must contain a Hash or Mash!
==> vm-chef-server: [2014-12-25T18:53:58+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

You're hitting the fallback to a Chef::DataBagItem, this isn't using Chef Vault.

I got stuck on this all day yesterday. The problem had something to do with Chef 12 as it went away when I went back to using chef omnibus version 11.16.4. This is on a Windows 2012 vagrant machine. A Ubuntu 14.04 vagrant machine did not have any problems on Chef 12.
For anyone interested, you should be able to re-create with the following recipe and vagrantfile assuming you have set up your data bags properly (encrypted with your chef key).
Vagrant 1.6.5
VirtualBox 4.3.12
Vagrantfile
VAGRANTFILE_API_VERSION = '2'
Vagrant.require_version '>= 1.5.0'

# Following Riot's convention. This is the data bag's name.
ENVIRONMENT = 'myapp-dev'

DATA_BAGS_PATH = 'data/bags/here'
ENVIRONMENTS_PATH = 'files/environments'
CHEF_HOME = 'your/chef/home'
USER = ENV['USERNAME']

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  if Vagrant.has_plugin?("vagrant-omnibus")
	# Change to 11.16.4, then vagrant destroy and vagrant up to see it work!
	config.omnibus.chef_version = '12.0.3'
  end

  config.vm.box = 'your-windows2012-box'
  config.vm.network :private_network, ip: '<IP_ADDRESS>'
  config.berkshelf.enabled = true
  config.vm.hostname = 'chef-vault-test-berkshelf'

  # Copy our client key to the VM so that the Chef run can decrypt the local
  #   chef-vault data bag encrypted items.
  config.vm.provision :file, source: "#{CHEF_HOME}/client.pem", destination: '/chef/client.pem'

  config.vm.provision :chef_solo do |chef|
	chef.node_name = USER
	chef.environment = ENVIRONMENT
	chef.environments_path = ENVIRONMENTS_PATH
	chef.data_bags_path = DATA_BAGS_PATH

	chef.run_list = [
	  'recipe[chef-vault-test::default]'
	]
  end
end

Cookbook
#
# Cookbook Name:: chef-vault-test
# Recipe:: default
#

include_recipe 'chef-vault'
chef_vault_item('myapp-dev', 'credentials')

Un-encrypted data bag (in directory data_bags/myapp-dev)
{
  "id": "credentials",
  "devusername": "devuser",
  "devpassword": "password01",
  "adminusername": "admin",
  "adminpassword": "password02"
}

A fix would be awesome because I would love to use chef 12.

I had this error on Windows with ChefDK 12.
I fixed it. It was caused by a difference in capitalisation between the databag file and the id I was using in my recipe.
I suspect in my instance of this issue... it was caused by chef misreporting the issue. It should say "cannot find databag with id 'blah'" or similar?

I had the same error reported - like @CaseyBurnsSv mine was a mismatch between the id attribute and the filename.

I had the same error. When i use chef-solo 11.8 its work fine, when 12 its didnt work

What's going on with this issue?  Data bags that work under chef client running in zero mode do not work running under chef solo.  This seems like a very odd bug.

I have also been bitten by this recently. Would appreciate an update or workaround aside from downgrading.

I had exactly the same problem. I used Symbols to refer items in databags. The problem turned to be chef-solo. When you use chef-solo Chef::DataBagItem and Chef::DataBag use some JSON parsing magic to create databags (Chef::DataBagItem delegates to Chef::DataBag, second link). And JSON parsing results in Hash. Hash does not support Symbols as keys:
irb(main):001:0> {"a"=>"b"}["a"]
=> "b"
irb(main):002:0> {"a"=>"b"}[:a]
=> nil

you need Mash.
When I switched to chef-zero, those ifs go to another computation branches and use "server", which appears to return Mashes, this small change in Vagrantfile:
-  config.vm.provision :chef_solo do |chef|
+  config.vm.provision :chef_zero do |chef|

resolves this issues.

It seems that this issue isn't with the cookbook itself then.

duplidcated on mac os.
this issue is most likely caused by the chef 12 provisioner.
the workaround is to set config.omnibus.chef_version = '11.18.12' in Vagrantfile
This fixed the problem for me.
same issue can be found here - https://github.com/chef/chef/issues/3347


Update .env

@plutonheaven good find!
Any idea why PYTHONPATH=src does not work in CI?

I guess it has something to do with defining the paths according to the deployment of the repo on the virtual machine.
Maybe we could keep PYTHONPATH=src in .env and define it explicitely in the python-ci.yml file, just for CI. I think that is what you have tried a few times.

@plutonheaven https://github.com/nektos/act is pretty useful to debug CI locally

I think the last commit worked. At least, I had no ModuleNotFoundError in the CI console, nor on my computer.


Recommended approach to adding required to all properties in a codebase

I've been waiting for the required modifier for some years, and now it's here I'd like to add it to all the properties to which it can be added in many/all of my codebases.  Manual editing will take hours.  Do you have a recommendation for a solution-wide refactoring in this regard?
If there is a solution for this, it could maybe be added to the docs.

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

ID: e026a730-560b-909e-6204-7676db0eb963
Version Independent ID: 2d808d79-e4ce-4c98-33b5-9a45dfc2d35c
Content: required modifier - C# Reference
Content Source: docs/csharp/language-reference/keywords/required.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Nothing exists or is planned.  The user could write their own transformer tool using Roslyn.

Ok thanks.  I wrote my own rude and crude console app which adds required to all likely looking auto-properties so long as they're declared on one line and correctly formatted.  It got me 99% of the way there on a couple of large Blazor WebAssembly web apps.  I'm too embarrassed to share it, but will do if pressed.  A transformer using Roslyn would be so much better, but my tool only took an hour on a rainy Sunday afternoon.


Added force sites to Down; RC improvements related to condor

Hey @ticoann @lucacopa , I wanted to share with you this patch ASAP, it's not final yet, so please do not merge.
These are the main changes:

removed forcedSiteList (just saw there is a leftover..., in principle nobody is using it)
only change site state when there is actually a change (so fetching much less condor classAds now)
only change site thresholds (and tasks) when there is actually a change
minimum limit for site thresholds is set to 50
minimum limit for taskIO thresholds is set to 25

The only thing left - I guess - is that I want to make site thresholds to CPUBound+IOBound, to always have room to submit merge/IO jobs. Of course, some logging cleanup is also needed, I want to run some final tests.
Feel free to review and make suggestions, I shall finish it tomorrow.

I updated this PR. It should be the final version now.
I'm running the validation of the new agent (1.0.7.pre13) with this patch in.


IntelliSense: Order suggestions using good, customizable and well-defined criteria

@jrieken My intention with opening this issue is to have a place mostly for discussion on the topic of improving the order of Intellisense suggestions.
TL;DR: See setting and conclusion at the end for some feature requests
Introduction
I believe an important thing in editor suggestions is to optimize their order, using principles like locality and usefulness of the suggestion to define its relevance. There are many criteria that could be used for that. I think it's beneficial to have those criteria described in a way that's transparent and well-defined (to allow discussing the best way to optimize suggestion orders) and also customizable (so that users can optimize it to their way of thinking).
So, with this in mind, I'd like to suggest a good system for ordering editor suggestions. My intention is just to provide the idea of having a logic for ordering that is customizable in ORDER BY semantics (like in SQL). And to have the criteria described here (the ones not already implemented) being considered, so that the relevance of suggestions can be further improved.
By "order by" semantics, I mean the system works with multiple levels of sorting, where each criterion is used as a tiebreaker for the previous one.
I know that some of these criteria are already present on VSCode, but there are some things which haven't been considered yet, so I'd like to describe how I think the thing as a whole could work first, and then describe the actual feature requests at the end.
Considerations
Firstly, I'm not considering filter relevance, which is the ordering criterion that sorts matches when the name is partially typed (so that exact prefix matches come before other substring matches, for example). That logic would likely be applied separately from this system (and VSCode already does a good job on this regard).
Also, there are two ways to trigger suggestions. The first is member suggestions (triggered with . after an expression, for a member token) which is NOT what I intend to describe here, although some things here might be useful for that too. Related: #50755
What I'm describing refers to general suggestions (triggered by pressing CtrlSpace for a "top-level" token). In this case the possibilities are too broad. Because of this, the suggestion mixes everything: members of the implicit this, local variables/parameters, classes, etc. It's difficult to know the user's intention, but there are some things we can consider.
For example, in a method body, it might be a good idea to show local variables/parameters before members, since you can already have members shown first when you type this..
You may also want to sort elements by proximity in code (distance from declaration to usage; near first), if they are otherwise equally likely to be chosen.
And, most importantly, if the context receiving the value implies a type (like in an assignment or a parameter in a function call) then it would be great to have values with a compatible type being presented before the others.
Criteria for Ordering Suggestions
So, for general suggestions, I would do an "order by" in this order by default (of course, considering only whatever is applicable depending on context).
The default orders here are just an example, they are debatable, of course.
Firstly, the ordering by primary category

Existing identifiers
The most important category, so it goes first
Smart name suggestions, for new identifiers
For example, after var or class; if there is context allowing smart suggestions
Word-based suggestions; when enabled
Native elements from the language (like keywords), if enabled
Least important, since user likely knows these already (so it goes on middle-end part)
Elements customizable by the local user (like templates/constructs)
Shown last so you can easily list them by pressing Up

Then, for identifiers, tiebreakers on this order:

By semantic purpose

Identifiers that have type and value (like local variables/parameters, function calls, etc)
Identifiers for types (like classes/interfaces/enums, type parameters)
Identifiers for macros and the like
Identifiers for scopes (like namespaces/imports and elements returned from require() in JS)
Other identifiers (like labels, etc)

Then, by type compatibility with what is expected on where the cursor is
That's how well the type or return type fits in the receiving type
Only applicable for identifiers that have or are types
Only applicable in places like assignment, argument, after return or new, etc

Exact type and subtype matches
Other implicitly castable matches
Explicitly castable matches (like supertypes, sorted by "distance" to expected type)
Elements that don't match

Then, by syntax explicitness

Elements that have to be referenced necessarily in the current syntax (like variables/parameters)
Elements implicitly included in the scope, which could have been accessed with a more explicit syntax instead (like members of the current class)
Elements implicitly included by extension syntax
Other "syntatic sugars"

Then, by declaration proximity (defined below)
Lastly, by name, alphabetically

Declaration proximity is defined in this order:

By proximity of source

Elements from the same file / compilation unit
Elements from the same project
Elements from dependency libraries
Elements from standard/native libraries (user might know these already)

Then, if on same file/unit, by proximity of scope where element is declared

Same scope first, then outer scopes, in order
Inner scopes go last, if applicable (for languages like JS)

Then, if on same scope and file, by proximity of the line in code where element is declared

If before the cursor, sort by line in decreasing order, so that the line right above is shown first
If after the cursor, is shown last, if applicable (for languages like JS)

So, with these citeria, you could have settings to control sorting with "order by" syntax:
// Primary order for IntelliSense suggestions
"editor.suggest.primaryOrder": [
  "identifiers", "smartNames", "words", "language", "user"
]
// Precedence of criteria used for ordering identifier suggestions (higher precedence first)
// It's possible to disable a criterion by removing it from the list
"editor.suggest.identifiersOrderBy": [
  "semanticPurpose", // elements that have a type first
  "typeCompatibility", // types that directly fit first
  "syntaxExplicitness", // explicit syntax first, syntatic sugar last
  "declarationProximity", // near first
  "name", // a-z A-Z _
]

Conclusion
So, if this system were to be fully implemented, it would need these feature requests (based on what I think wasn't implemented yet)

[ ] Having suggestions use ORDER BY semantics, allowing better transparency of ordering criteria

[ ] A setting to customize the order criteria for identifier suggestions

[ ] Having type compatibility criterion for suggestions (aka Smart Completion)
[ ] (if that makes sense): Having syntax explicitness criterion for suggestions
[ ] (maybe, if it's worth implementing eventually): Having smart name suggestions?

Thanks for getting on this and kudos for setting the correct context, e.g focusing only on what you call "general suggestions".
I don't wanna engage (yet) in discussing the proposed solutions/ideas but just provide more context and what VS code can correctly do and what it cannot correct do (only guess).
When it comes to completions (like most other language APIs) VS code doesn't define/use programming language semantics but defines a completion domain model that describes the look and feel of the completions UI, e.g CompletionItem#label, #detail, or #kind are all used for rendering and there is no contract that e.g. label must appear in source; for example an extension is free to pick java.lang.String or String. That makes it hard to define something like (semantic) proximity sort on top of these UX recipes (btw we did make an attempt for proximity sort with editor.suggest.localityBonus)
What I am trying to say is this: Your suggestions make sense, a lot of sense, but given the current API some features must be implemented by extensions (using CompletionItem#sortText). That raises the question how we get the message to all extension authors so that more language languages feel equality smart?

Hmm I understand, so most things would have to be done by each extension. Makes sense.
In any case, I'm glad to have a starting point for discussion on this topic.
If/when you're thinking about eventually making improvements on this area, then it may be useful to have at least the general idea of a model like this in mind (preferably with some more research first, since there is probably lots of factors that I haven't considered).

That raises the question how we get the message to all extension authors so that more language languages feel equality smart?

TL;DR: The editor simply doesn't care about most of the actual semantics, extensions still define the whole process - see the end.
Well, I don't know any details on how this works in VSCode, but the two things I can think that could make it feasible of would be:

to have interfaces that the extensions could optionally implement if they want to fit in this model (then the setting would only apply to those extensions that decide to support this "smart sorting"); and
having a model like this described as documention for extension devs.

Actually, thinking a little more about it, the only thing that the editor would need for sorting would be for the extension to provide sortable values for each criterion used in completion items (and if any criterion is not applicable, it can be simply ignored in sorting). The values don't even necessarily have to fit in a specific API type, they just have to be able to be sorted, and more or less follow the semantics from the documentation, or whatever is more suitable if there is any special case.
For example, (completionItem).sortingValues.semanticPurpose doesn't have to be an enum value defined in the API. One extension could implement it as simply numbers, while other could do it with an internally defined enum or even strings or some other custom type. Or, they might just not provide a value if it's not applicable. The only requirement would be to provide a value whose sorting makes sense according to docs (in this case, smaller values for types of identifier that are more useful in completion).
So, the documentation would provide some guidelines, but it's still up to the extension to implement it with a proper semantic meaning.
Also, each criterion works independently, so if you add other criteria as possibilities, they would simply be ignored in sorting until the extension provides an implementation for them. And, of course, extensions can still implement their own sorting in the current method if they don't want to use this system.

So in summary, this "smart ordering" model defines only:

What are the sorting criteria (in the API)
How these criteria are generally expected to be used for sorting (in documentation)

And extensions/languages define in implementation:

Whether they are using "smart ordering" or their own custom ordering in completion
If they are using it: when/how each criterion applies; and the actual types of values used to achieve expected sorting for each criterion

Then all that the editor does is ordering values - it doesn't care what they mean or how they are obtained.

Don't mean to hijack this thread but I have a suggestion to revisualise intellisense to use a force directed layout with nodes / animations / tweening /parallel nodes for completion.
Please give this thought some space.
https://github.com/MicrosoftDocs/intellicode/issues/123
I don't know where to start to prototype this - I cloned the repo - but it's not so simple to get to where this control is rendered / displayed or how I can swizzle in this d3 directed layout to replace stock standard control. Any pointers appreciated.

Your ideas make sense, I have another suggestion.
TL;DR.
Personally, for long since I starting to write code, I not care about it much, but the more languages and libraries growing, the more complicated and frustrated for me.
As of today, after some shorta day I have learning Rust, with lots of reading over and over the book.
I quite grasped the ideas of the language, so finally I have some confident, to the extent I begin writing some experiment, more specifically, a web server.
As the flexibility of Rust trait (a.k.a interface in other languages), third-party packages take the most advantages of it. After more than a day struggling writing just a simple server on my own, I noticed that the implementation scattered all over the place, e.g.
close
fmt
inner
poll_close
poll_close
poll_flush
poll_flush
poll_next
poll_next
size_hint
size_hint
start_send
start_send
try_poll_next

Could you see something weird? I can ascertain that have NO typo. NO.
The methods are duplicated. This results of trait implement for type that implement other trait, as I think it's unique to Rust.
And this is just a simple version of what I faced in reality, as different library takes different approaches and efforts in making the interfaces as flexible as possible.
My suggestion is that it's show what's trait the methods lying:
self.close
Display.fmt
self.inner
Stream.poll_close
Sink.poll_close
Stream.poll_flush
Sink.poll_flush
Stream.poll_next
Sink.poll_next
...

For better, sorts alphabetically as well:
self.close
self.inner
Display.fmt
Sink.poll_close
Sink.poll_flush
Sink.poll_next
Stream.poll_close
Stream.poll_flush
Stream.poll_next
...

I think this improvement not only make sense for Rust, but also for other languages and libraries  as well. For example, Android have a whole bunches of methods for each classes, so sort by method name alphabetically are inadequate (of course you might not use Visual Studio Code for Android).
I had researched a wide range of IDEs out there, but there's seems not any IDEs with solutions well enough to have me satisfied.
It's bugging me for a moment before I decided to make some move, trying to write myself.
I don't have much freetime to do this alone, and this topic likely not going to have much attentions for a feature request. So, I'd like to collaborate with you guys, who eager to have this feature, to implement it ourselves.
Let's make a futures with less frustrating coding experiences.

Is there any way to sort the suggest items by type?

I am happy to see this discussion. I am struggling with finding the proper field/property/method also. For example, when I need to navigate in generated code (grpc services and messages mainly) that has a lot of boilerplate (classes, methods... etc). Its hard to select the ones I am interested about.
So for the above reason I would vote for a local toolbar at the top of the IntelliSense window where I could switch the ordering or include and exclude certain item types. I think the actual supported cases are less important than having a flexible mechanism that is easy to customize each time the hints are displayed. So, a settings only solution would not be efficient in this case.

Is there any way to sort the suggest items by type?

@tjx666 Not that I know of, or at least not as a generic setting or feature that works for all language extensions.
I think the only way to improve suggestions order currently is with something like Intellicode (which is AI-based), but that's out of scope here (it just improves it "smartly" with no customization or simple/clear sorting rules). I haven't used it for quite a while, as I'm not sure whether / how much data is sent to MS servers in order to provide it (the info I found seems to apply only to VS, not VSCode).
Honestly, if member completions would just give less priority to inherited entries and much less to deprecated entries (and show them in strikethrough), that would already help a lot.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!

It will be pleasant to see this feature.

While this request is not going to be implemented, I hope my analysis serves as a sort of guideline for any programming language extension developers who are looking to have good ordering of completions. Even if sorting is not made customizable, just using the logic and default order proposed here should be enough to provide a better experience for your extension users.
So the "mini-research" at the top is relevant for anyone wanting to implement code completion in extensions, i.e.: vscode.CompletionItemProvider.provideCompletionItems or LSP's "capabilities"."completionProvider".
I hope search engines help them arrive here. Or, even better, I wish the docs there would point developers to some of these guidelines, so they can make better completions.

I just want imports local to the project to be suggested before (above) imports from library code.
What can I do to achieve this? It sounds simple enough.

I just want imports local to the project to be suggested before (above) imports from library code. What can I do to achieve this? It sounds simple enough.

Couldn't figure it out either. I noticed that your project structure plays a role, though. So, if you are in Next.js, working with a /src/components folder, a node_modules folder at the root will rank higher up. I did minimal testing and then couldn't find a solution.

I would find this very useful, as currently it is very hard to find symbols declared by the actual type, and not inherited / extensions.

I would find this very useful to put suggestions for constants at the bottom, as I very rarely need those.
But when I do, it's nice to be able to just scroll through them because most of the time, seeing them makes me remember which one I'm actually looking for.
But this is in both cases annoying when they're completely mixed with everything else...

I recently filed https://github.com/golang/go/issues/66523 against the Go LSP project, and the team there has responded showing that the LSP returns results in a sane order (ie. local symbols first, then external library code), but VSCode subsequently overrides that ordering completely. If, as @geekley suggests, there are ways for an extension to control ordering in the completion dialogue, what are those mechanisms? How can the Go extension improve ordering?


METRON-1687: Upgrade the rat plugin to 0.13-SNAPSHOT

Contributor Comments
Due to https://issues.apache.org/jira/browse/RAT-234, the rat plugin is not checking the typescript files for license headers.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

Ok, I spun this up in full-dev and smoketested the UIs that these licenses touch.

+1, I'm glad to see this fixed!


Upgrade operator-observability to fix unit tests

What this PR does
Before this PR:
Unit tests failed since we have 2 recording rules with the same name.
Even if we sort the rules it could happen that the resulting order is different, since we only compare names, and not the expressions.
This causes a false semantic deepEqual, and so a (one more) patch operation.
this PR fixed it observability repo https://github.com/machadovilaca/operator-observability/pull/11
After this PR:
Uit test pass, and rules with same names count as 2 rules.

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

@avlitman I filled in the release note for you, hope you don't mind.

/approve

Thank you @avlitman !

/cherry-pick release-1.2


Screen/backlight off

Is your feature request related to a problem? Please describe.
When playing music, it's probably good if we can turn off the display. As a reference, sysdvr had the feature implemented here https://github.com/exelix11/SysDVR/commit/f1052e38c12f07d84b1a4a6b47e0e0307c363a5f
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

@kevsestre As switchfin is not overlay sysmodule , so background music play is not possibe
another method is Implement another overlay sysmodule like https://github.com/tallbl0nde/TriPlayer


Upgrade to Bevy 0.13

Thanks for your contribution!
There seem to be a problem with the "Flappin" example: on the second run (i.e. after a game-over) the pillars texture disappears, I'm not sure why.
This is not very important though, so I'll merge your PR and fix it later.


Generated migration for Postgres does not handle data type casting properly

I am using postgres and had a table with primary key column of varchar data type, I changed it to uuid and generated a migration.
When I run the generated migration I am getting an error  PostgresError: column "ticker_id" cannot be cast automatically to type uuid. I have attached the generated migration and the error I got from the database driver.
@AndriiSherman

Encountered the same problem
$ npx drizzle-kit migrate
drizzle-kit: v0.22.8
drizzle-orm: v0.33.0

No config path provided, using default path
Reading config file '/home/a/code/lol/drizzle.config.ts'
Using 'pg' driver for database querying
[⣷] applying migrations...error: column "owner_id" cannot be cast automatically to type uuid

@AleksandrSherman any updates on this?


Jquery from google will be slow in China

In accumulo home page use jquery like this:
https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js
As well know google domain name will be very slow or blocked in China.

New Issue in accumulo-website already.

https://github.com/apache/accumulo-website/issues/159


About key of chord

When you specify a chord in your code, what does the key look like? Is it the default C major?

Thank you for your reply. I have two more questions

Can I set the key?
As for the text, I would like to know if there is a general list of instruments, because I find that some instruments are not very good. Do you have any good suggestions on the writing of text content? There are some texts that I get musical representation that is not very good.
Thank you again for your patient reply and best wishes

Sorry this model cannot change the key. You can only use common chords shared with C key.
The dataset is comprised mainly of guitar, bass and drums . So generally, these instruments have best performace in prompting.


[BUG]: Dataset upload on tabular model creation does not allow uploading correct file type

Operating system
Ubuntu
Bug description
Creating a model does not allow user to upload the correct file type.
Steps to reproduce

Navigate to DLP dashboard
Click 'Train Model'
Select Tabular
Give your model an arbitrary name
Attempt to upload a file ending in .csv
Observe that the Toast message does not allow you to upload the file citing "Please upload a file ending in .csv" despite the fact that the file you uploaded is a csv.

@jamesrm67 try and emulate this and see if you can find the cause!


UniversalDashboard.Community compatibility

Is UDForge supposed to be compatible with the community edition?
When I tried to run New-UDDesktopApp I received an error saying that I need to install UniversalDashboard however I have UNiversalDashboard.Community installed.

I just created pull request #20 for this. It should fix your issue once it's merged.