Fail to build pydantic_core on OS X 10.11 with Python 3.10

Hi, pydantic_core >= 2.16 only provides wheels for macOS >= 10.12 and it would fail when compiling from source on OS X 10.11 with Python 3.10.11:
pip3 install --upgrade pydantic==2.7.1
Requirement already satisfied: pydantic in /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages (2.5.3)
Collecting pydantic
  Using cached pydantic-2.7.1-py3-none-any.whl.metadata (107 kB)
Requirement already satisfied: annotated-types>=0.4.0 in /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages (from pydantic) (0.6.0)
Collecting pydantic-core==2.18.2 (from pydantic)
  Using cached pydantic_core-2.18.2.tar.gz (383 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: typing-extensions>=4.6.1 in /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages (from pydantic) (4.11.0)
Using cached pydantic-2.7.1-py3-none-any.whl (409 kB)
Building wheels for collected packages: pydantic-core
  Building wheel for pydantic-core (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for pydantic-core (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [18 lines of output]
      Running `maturin pep517 build-wheel -i /Library/Frameworks/Python.framework/Versions/3.10/bin/python3 --compatibility off`
      📦 Including license file "/private/var/folders/_n/8qwtj23j0tx0bdy7ftvpg63m0000gn/T/pip-install-a3iwsm3w/pydantic-core_1e29f10ace204ee99125b93a432e3171/LICENSE"
      🍹 Building a mixed python/rust project
      🔗 Found pyo3 bindings
      🐍 Found CPython 3.10 at /Library/Frameworks/Python.framework/Versions/3.10/bin/python3
      📡 Using build options features, bindings from pyproject.toml
      💻 Using `MACOSX_DEPLOYMENT_TARGET=10.7` for x86_64-apple-darwin by default
      warning: unused manifest key `lints` (may be supported in a future version)

      this Cargo does not support nightly features, but if you
      switch to nightly channel you can pass
      `-Zlints` to enable this feature.
      error: package `pydantic-core v2.18.2 (/private/var/folders/_n/8qwtj23j0tx0bdy7ftvpg63m0000gn/T/pip-install-a3iwsm3w/pydantic-core_1e29f10ace204ee99125b93a432e3171)` cannot be built because it requires rustc 1.76 or newer, while the currently active rustc version is 1.72.1

      💥 maturin failed
        Caused by: Failed to build a native library through cargo
        Caused by: Cargo build finished with "exit status: 101": `MACOSX_DEPLOYMENT_TARGET="10.7" PYO3_ENVIRONMENT_SIGNATURE="cpython-3.10-64bit" PYO3_PYTHON="/Library/Frameworks/Python.framework/Versions/3.10/bin/python3" PYTHON_SYS_EXECUTABLE="/Library/Frameworks/Python.framework/Versions/3.10/bin/python3" "cargo" "rustc" "--features" "pyo3/extension-module" "--message-format" "json-render-diagnostics" "--manifest-path" "/private/var/folders/_n/8qwtj23j0tx0bdy7ftvpg63m0000gn/T/pip-install-a3iwsm3w/pydantic-core_1e29f10ace204ee99125b93a432e3171/Cargo.toml" "--release" "--lib" "--crate-type" "cdylib" "--" "-C" "link-arg=-undefined" "-C" "link-arg=dynamic_lookup" "-C"<EMAIL_ADDRESS>      Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/Library/Frameworks/Python.framework/Versions/3.10/bin/python3', '--compatibility', 'off'] returned non-zero exit status 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pydantic-core
Failed to build pydantic-core
ERROR: Could not build wheels for pydantic-core, which is required to install pyproject.toml-based projects

pip3 install --upgrade pydantic==2.6.4
Collecting pydantic==2.6.4
  Using cached pydantic-2.6.4-py3-none-any.whl.metadata (85 kB)
Requirement already satisfied: annotated-types>=0.4.0 in /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages (from pydantic==2.6.4) (0.6.0)
Collecting pydantic-core==2.16.3 (from pydantic==2.6.4)
  Using cached pydantic_core-2.16.3.tar.gz (368 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: typing-extensions>=4.6.1 in /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages (from pydantic==2.6.4) (4.11.0)
Using cached pydantic-2.6.4-py3-none-any.whl (394 kB)
Building wheels for collected packages: pydantic-core
  Building wheel for pydantic-core (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for pydantic-core (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [155 lines of output]
      Running `maturin pep517 build-wheel -i /Library/Frameworks/Python.framework/Versions/3.10/bin/python3 --compatibility off`
      📦 Including license file "/private/var/folders/_n/8qwtj23j0tx0bdy7ftvpg63m0000gn/T/pip-install-50dvwsdn/pydantic-core_1a7e9b4858b04882a785d743f3156b27/LICENSE"
      🍹 Building a mixed python/rust project
      🔗 Found pyo3 bindings
      🐍 Found CPython 3.10 at /Library/Frameworks/Python.framework/Versions/3.10/bin/python3
      📡 Using build options features, bindings from pyproject.toml
      💻 Using `MACOSX_DEPLOYMENT_TARGET=10.7` for x86_64-apple-darwin by default
      warning: unused manifest key `lints` (may be supported in a future version)

      this Cargo does not support nightly features, but if you
      switch to nightly channel you can pass
      `-Zlints` to enable this feature.
         Compiling autocfg v1.1.0
         Compiling proc-macro2 v1.0.76
         Compiling target-lexicon v0.12.9
         Compiling unicode-ident v1.0.10
         Compiling quote v1.0.35
         Compiling libc v0.2.147
         Compiling python3-dll-a v0.2.9
         Compiling syn v2.0.48
         Compiling pyo3-build-config v0.20.2
         Compiling once_cell v1.18.0
         Compiling version_check v0.9.4
         Compiling cfg-if v1.0.0
         Compiling heck v0.4.1
         Compiling static_assertions v1.1.0
         Compiling lexical-util v0.8.5
         Compiling ahash v0.8.7
         Compiling num-traits v0.2.16
         Compiling getrandom v0.2.10
         Compiling pyo3-ffi v0.20.2
         Compiling num-integer v0.1.45
         Compiling lock_api v0.4.10
         Compiling parking_lot_core v0.9.8
         Compiling zerocopy v0.7.32
         Compiling rustversion v1.0.13
         Compiling num-bigint v0.4.4
         Compiling memoffset v0.9.0
         Compiling tinyvec_macros v0.1.1
         Compiling scopeguard v1.1.0
         Compiling allocator-api2 v0.2.16
         Compiling smallvec v1.11.2
         Compiling hashbrown v0.14.3
         Compiling tinyvec v1.6.0
         Compiling lexical-parse-integer v0.8.6
         Compiling lexical-write-integer v0.8.5
         Compiling pyo3-macros-backend v0.20.2
         Compiling pyo3 v0.20.2
         Compiling serde v1.0.195
         Compiling memchr v2.6.3
         Compiling aho-corasick v1.0.2
         Compiling pyo3-macros v0.20.2
         Compiling lexical-write-float v0.8.5
         Compiling lexical-parse-float v0.8.5
         Compiling strum_macros v0.25.3
         Compiling unicode-normalization v0.1.22
         Compiling parking_lot v0.12.1
         Compiling serde_derive v1.0.195
         Compiling percent-encoding v2.3.1
         Compiling unindent v0.2.3
         Compiling unicode-bidi v0.3.13
         Compiling indoc v2.0.4
         Compiling equivalent v1.0.1
         Compiling regex-syntax v0.8.2
         Compiling serde_json v1.0.109
         Compiling regex-automata v0.4.3
         Compiling indexmap v2.0.0
         Compiling idna v0.5.0
         Compiling form_urlencoded v1.2.1
         Compiling strum v0.25.0
         Compiling lexical-core v0.8.5
         Compiling pydantic-core v2.16.3 (/private/var/folders/_n/8qwtj23j0tx0bdy7ftvpg63m0000gn/T/pip-install-50dvwsdn/pydantic-core_1a7e9b4858b04882a785d743f3156b27)
         Compiling itoa v1.0.8
         Compiling ryu v1.0.14
         Compiling jiter v0.0.6
         Compiling speedate v0.13.0
         Compiling url v2.5.0
         Compiling regex v1.10.2
         Compiling enum_dispatch v0.3.12
         Compiling base64 v0.21.7
         Compiling uuid v1.6.1
      error[E0446]: crate-private type `extra::Extra<'_>` in public interface
         --> src/serializers/fields.rs:149:5
          |
      149 | /     pub fn main_to_python<'py>(
      150 | |         &self,
      151 | |         py: Python<'py>,
      152 | |         main_iter: impl Iterator<Item = PyResult<(&'py PyAny, &'py PyAny)>>,
      ...   |
      155 | |         extra: Extra,
      156 | |     ) -> PyResult<&'py PyDict> {
          | |______________________________^ can't leak crate-private type
          |
         ::: src/serializers/extra.rs:73:1
          |
      73  |   pub(crate) struct Extra<'a> {
          |   --------------------------- `extra::Extra<'_>` declared as crate-private

      error[E0446]: crate-private type `extra::Extra<'_>` in public interface
         --> src/serializers/fields.rs:214:5
          |
      214 | /     pub fn main_serde_serialize<'py, S: serde::ser::Serializer>(
      215 | |         &self,
      216 | |         main_iter: impl Iterator<Item = PyResult<(&'py PyAny, &'py PyAny)>>,
      217 | |         expected_len: usize,
      ...   |
      221 | |         extra: Extra,
      222 | |     ) -> Result<S::SerializeMap, S::Error> {
          | |__________________________________________^ can't leak crate-private type
          |
         ::: src/serializers/extra.rs:73:1
          |
      73  |   pub(crate) struct Extra<'a> {
          |   --------------------------- `extra::Extra<'_>` declared as crate-private

      error[E0446]: crate-private type `extra::Extra<'_>` in public interface
         --> src/serializers/fields.rs:260:5
          |
      260 | /     pub fn add_computed_fields_python(
      261 | |         &self,
      262 | |         model: Option<&PyAny>,
      263 | |         output_dict: &PyDict,
      ...   |
      266 | |         extra: &Extra,
      267 | |     ) -> PyResult<()> {
          | |_____________________^ can't leak crate-private type
          |
         ::: src/serializers/extra.rs:73:1
          |
      73  |   pub(crate) struct Extra<'a> {
          |   --------------------------- `extra::Extra<'_>` declared as crate-private

      error[E0446]: crate-private type `extra::Extra<'_>` in public interface
         --> src/serializers/fields.rs:277:5
          |
      277 | /     pub fn add_computed_fields_json<S: serde::ser::Serializer>(
      278 | |         &self,
      279 | |         model: Option<&PyAny>,
      280 | |         map: &mut S::SerializeMap,
      ...   |
      283 | |         extra: &Extra,
      284 | |     ) -> Result<(), S::Error> {
          | |_____________________________^ can't leak crate-private type
          |
         ::: src/serializers/extra.rs:73:1
          |
      73  |   pub(crate) struct Extra<'a> {
          |   --------------------------- `extra::Extra<'_>` declared as crate-private

      For more information about this error, try `rustc --explain E0446`.
      error: could not compile `pydantic-core` (lib) due to 4 previous errors
      💥 maturin failed
        Caused by: Failed to build a native library through cargo
        Caused by: Cargo build finished with "exit status: 101": `MACOSX_DEPLOYMENT_TARGET="10.7" PYO3_ENVIRONMENT_SIGNATURE="cpython-3.10-64bit" PYO3_PYTHON="/Library/Frameworks/Python.framework/Versions/3.10/bin/python3" PYTHON_SYS_EXECUTABLE="/Library/Frameworks/Python.framework/Versions/3.10/bin/python3" "cargo" "rustc" "--features" "pyo3/extension-module" "--message-format" "json-render-diagnostics" "--manifest-path" "/private/var/folders/_n/8qwtj23j0tx0bdy7ftvpg63m0000gn/T/pip-install-50dvwsdn/pydantic-core_1a7e9b4858b04882a785d743f3156b27/Cargo.toml" "--release" "--lib" "--crate-type" "cdylib" "--" "-C" "link-arg=-undefined" "-C" "link-arg=dynamic_lookup" "-C"<EMAIL_ADDRESS>      Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/Library/Frameworks/Python.framework/Versions/3.10/bin/python3', '--compatibility', 'off'] returned non-zero exit status 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pydantic-core
Failed to build pydantic-core
ERROR: Could not build wheels for pydantic-core, which is required to install pyproject.toml-based projects

The hint here is already in your build output:
(/private/var/folders/_n/8qwtj23j0tx0bdy7ftvpg63m0000gn/T/pip-install-a3iwsm3w/pydantic-core_1e29f10ace204ee99125b93a432e3171)` cannot be built because it requires rustc 1.76 or newer, while the currently active rustc version is 1.72.1

If you update your Rust compiler (probably with rustup update) and retry, it should work.

@davidhewitt Unfortunately, starting from Rust 1.74, the minimum supported macOS platform is macOS 10.12 (see here), so the latest Rust compiler supporting OS X 10.11 is Rust 1.73. I tried installing the latest Rust using the standalone installer, but that did not work.

That's a great point. I think we should consider downgrading our minimum Rust to 1.73, but this may not be trivial.

^ reflecting on the above, I think downgrading is the right thing, but I think the reality is that extending support backwards to old macOS versions is not a high priority for me right now. If anyone is interested in helping downgrade, a PR is very welcome.

Could you please give some hints about how to contribute on this specific downgrading issue?

Rust 1.73 is missing some features. MSRV can be lowered to 1.75, but not below. See #1315

I think 1.73 would still be reachable but it'd be a lot more work.


UAI should be added

Nice web for integrating the majority of CCF conferences, but the UAI is absent, unfortunately.

Thanks for your suggestion, UAI 2023 has now been added.


Content doesn't render under navigation bar on first launch, but corrects itself after backgrounding

Before submitting a new issue

[X] I tested using the latest version of the library, as the bug might be already fixed.
[X] I tested using a supported version of react native.
[X] I checked for possible duplicate issues, with possible answers.

Bug summary
When you first launch the app, the navigation bar is opaque and content does not render under it.  If you background the app, and then open it again, then content is rendered under it.
I've created a minimal Expo 52 app to show this. The content I'm trying to render under the navigation bar is the expo router tab bar, and a formsheet modal.
I've also recorded video demonstrating the issue:
rn-edge-to-edge.webm
Library version
1.1.1
Environment info
System:
  OS: Linux 6.9 Pop!_OS 22.04 LTS
  CPU: (16) x64 AMD Ryzen 7 7800X3D 8-Core Processor
  Memory: 11.11 GB / 30.50 GB
  Shell:
    version: 3.3.1
    path: /usr/bin/fish
Binaries:
  Node:
    version: 22.11.0
    path: ~/.asdf/installs/nodejs/22.11.0/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.yarn/bin/yarn
  npm:
    version: 10.9.0
    path: ~/.asdf/plugins/nodejs/shims/npm
  Watchman:
    version: 4.9.0
    path: /usr/bin/watchman
SDKs:
  Android SDK:
    API Levels:
      - "30"
      - "31"
      - "33"
      - "34"
      - "35"
    Build Tools:
      - 29.0.2
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
      - 34.0.0
      - 35.0.0
      - 35.0.0
    System Images:
      - android-30 | Google Play Intel x86 Atom
      - android-33 | Google Play Intel x86_64 Atom
      - android-34 | Google Play Intel x86_64 Atom
      - android-35 | Google Play Intel x86_64 Atom
    Android NDK: Not Found
IDEs:
  Android Studio: AI-242.23339.11.2421.12550806
Languages:
  Java:
    version: 22.0.2
    path: /home/chris/.asdf/shims/javac
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.2
    wanted: latest
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.1
    wanted: 0.76.1
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Steps to reproduce

Launch the reproduction app I've provided
See that the tab bar and form sheet modal are not rendered behind the navigation bar
background the app (don't close it)
open the app again
see that the tab bar and form sheet modal are properly rendered behind the navigation bar now

Reproducible sample code
Repo is here: https://github.com/doughsay/expo-edge-to-edge

react-native-edge-to-edge is correctly setting edge-to-edge each time the android activity is resumed (included at start), the issue here is react-native-screens that restore the system bars.
Until this PR is merged, you need to add statusBarTranslucent and navigationBarTranslucent, or react-native-screens breaks edge-to-edge:
export default function RootLayout() {
  return (
    <ThemeProvider value={DefaultTheme}>
      <Stack
        screenOptions={{
          // You need to add this
          statusBarTranslucent: true,
          navigationBarTranslucent: true,
          navigationBarColor: "transparent",
          statusBarBackgroundColor: "transparent",
        }}
      >
        <Stack.Screen
          name="(tabs)"
          options={{
            headerShown: false,
          }}
        />

        <Stack.Screen
          name="modal"
          options={{
            presentation: "formSheet",
            sheetAllowedDetents: "fitToContents",

            // You need to add this
            statusBarTranslucent: true,
            navigationBarTranslucent: true,
            navigationBarColor: "transparent",
            statusBarBackgroundColor: "transparent",
          }}
        />
      </Stack>
    </ThemeProvider>
  );
}

And even with that, it blinks and sometimes, it doesn't apply the navigation bar color:
https://github.com/user-attachments/assets/377568ce-8072-4205-8df9-8681eee000af
I will work on a patch for react-native-screens (using patch-packages) to avoid this behavior until they fix it. If an app is started in edge-to-edge, they don't have to restore system bars.

@doughsay Opening the same issue on their repository could be a good idea, as the issue come from there.

Amazing, thank you so much for digging into this, I wouldn't have been able to figure all that out 😅.
I'll keep an eye on that expo-router issue and in the meantime I'll apply your suggested patch.  Thanks!

@doughsay expo-router 4.0.5 has been released with the fix, could you try it?

Yep, it works!  Thanks a lot for such a quick turnaround!


new types for my collection

The type of this PR is: FEAT

This PR resolves CX-2611
Description

Add ActionType.tappedUploadAnotherArtwork and OwnerType.myCollectionInsights
PR Checklist (tick all before merging)

[ ] If I've added a new file to the tree I've exported it from the common index.ts
[ ] I've added comments with examples for any new interfaces and ensured that they're in the docs
[x] No platform-specific terminology has been used outside of click and tap (platform is inferred by the DB storing events)

:rocket: PR was released in v4.48.0 :rocket:


Updated spring-data-cosmos read me to fix javadoc errors and sb3 version

Updated spring-data-cosmos read me to fix javadoc errors and sb3 version

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-spring-data-cosmos


shutter: 0.99 -> 0.99.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/shutter/versions.
meta.description for shutter is: "Screenshot and annotation tool"
meta.homepage for shutter is: "https://shutter-project.org/"
meta.changelog for shutter is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/lbiss5lcn1rfxqrna853qi11nziw597c-shutter-0.99.2/bin/.shutter-wrapped passed the binary check.
/nix/store/lbiss5lcn1rfxqrna853qi11nziw597c-shutter-0.99.2/bin/shutter passed the binary check.
0 of 2 passed binary check by having a zero exit code.
2 of 2 passed binary check by having the new version present in output.
found 0.99.2 with grep in /nix/store/lbiss5lcn1rfxqrna853qi11nziw597c-shutter-0.99.2
found 0.99.2 in filename of file in /nix/store/lbiss5lcn1rfxqrna853qi11nziw597c-shutter-0.99.2

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
shutter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lbiss5lcn1rfxqrna853qi11nziw597c-shutter-0.99.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A shutter https://github.com/r-ryantm/nixpkgs/archive/bb4a9946075e7bd9991afbadd07e5867c1e59d20.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lbiss5lcn1rfxqrna853qi11nziw597c-shutter-0.99.2
ls -la /nix/store/lbiss5lcn1rfxqrna853qi11nziw597c-shutter-0.99.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

shutter

Maintainer pings
cc @bjornfor for testing.

#144462


feat(mito): upload part writer for write cache

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This PR implements a skeleton for the WriteCache that serves as a write-through cache for object stores.
WriteCache
The WriteCache has a local store to cache files.
pub(crate) struct WriteCache {
    /// Local object storage to store files to upload.
    local_store: ObjectStore,
    /// Object store manager.
    object_store_manager: ObjectStoreManagerRef,
}

The WriteCache has an upload() method to write files to the cache (a local store) and upload them to object stores.
pub(crate) fn upload(&self, upload: Upload) -> Result<()>;

Upload can be sync or async. We might implement the sync version first.
UploadPart
Each Upload can contain multiple UploadPart.
pub(crate) struct Upload {
    /// Parts to upload.
    pub(crate) parts: Vec<UploadPart>,
}

Each part describes files created by a flush task (or a compaction task). The write cache can write them to the object store and update the region manifest later. If we reopen the engine, the write cache should recover metadata of upload tasks from the local store if we support async upload in the future.
pub(crate) struct UploadPart {
    /// Region id.
    region_id: RegionId,
    /// Directory of the region data.
    region_dir: String,
    /// Meta of files created.
    pub(crate) file_metas: Vec<FileMeta>,
    /// Target storage of SSTs.
    storage: Option<String>,
}

We use the UploadPartWriter to create an UploadPart. To write an SST to an object store, we call AccessLayer::upload_part_writer() to create an upload part. Now the upload part writer still writes to object stores directly. In the future, it will write to the local store first.
Since an Upload can hold multiple UploadParts, we can maintain multiple metadata of flushed files from different regions together and reduce IO requests to the local store.
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.
[x]  This PR does not require documentation updates.

Refer to a related PR or issue link (optional)

https://github.com/GreptimeTeam/greptimedb/issues/2965

After some experiments, I plan to simplify the implementation of the write-through cache and upload files to object stores synchronously. Then we can remove UploadPart related components. I'll get back soon.

I refactored the AccessLayer and WriteCache:

https://github.com/GreptimeTeam/greptimedb/pull/2999/commits/02785134ca579e005334f0539b1bbd410db2d765 refactors the AccessLayer to hide the details of writing SST files.
https://github.com/GreptimeTeam/greptimedb/pull/2999/commits/9f03e6746f681c960e6bb5b2988b124bd2d4c1a3 writes the SST to the write cache, though it doesn't go through the local file cache.


Add ability to delete translation variant

Add ability to delete translation variant from word. Now it's working only locally.

It's already implemented before


This requires the 'non-nullable' experiment to be enabled.

Hi, I created a file with this name "analysis_options.yaml"  in root of my project and add these lines "analyzer:
enable-experiment:
- non-nullable"
to it, but when I use "flutter run" command I receive below error for two places that I use this: "?"
Error: This requires the 'non-nullable' experiment to be enabled.
Try enabling this experiment by adding it to the command line when compiling and running.

Hi @MohammadEhsanMirzaaee
"Unfortunately I don't think it's possible to get --enable-experiment:non-nullable working "
Please take a look at this coment
Duplicate of 40490rl
Please follow up there
Thank you

#40490 was locked by the stale bot, so can we continue the discussion here? The issue is by no means fixed, so closing and locking conversations is just insulting to the community.

I echo the above, this discussion needs to continue now more than ever before.
It's still pretty fresh (following link is dated June 10th), but non-nullable/NNBD is available on the beta channel now: https://medium.com/dartlang/announcing-sound-null-safety-defd2216a6f3
I'm specifically trying with sdk: ">=2.9.0-14.1.beta <3.0.0" right now. I won't state things on behalf of the Dart team, but it seems that non-nullable types are indeed coming soon to a stable release.
With a very short exercise in converting code to use NNBD, I actually found a few bugs. One seems to be just from general improvements to the analyzer as a result, but a couple are definitely regarding null safety. And these were found in my Flutter-specific code as well as some "backend" utilities of the app. As disheartening as this was (I assure you I was trying to be safe with this project), it really highlights the benefit of bringing NNBD to Flutter apps.
For now I'll have to sigh and convert my code back to the land of unknown nulls (plus a few fixes!), but I now yearn for the NNDB future.
Rather than just "this can't happen", can we start a discussion on "what do we need to get this to work?"? (Truthfully I hope there's already a plan, but we can start here if not).
 That would be awkward.

Could everyone who still has this problem please file a new issue with the exact description of what happens, logs and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

Additionally to the packages migration and the enable-experiment in analysis_options, I also needed to explicitly run the build_runner build with the flag --enable-experiment non-nullable and it worked

All Working Possible Solution [Solved] Error: This requires the ‘non-nullable’ experiment to be enabled


add links to examples of using overlay driver with swarm mode

Proposed changes
Added links to overview topics and examples of using overlay and other network drivers with Swarm, per user feedback (issue referenced below).
Related issue
#444
Please take a look
@Bartman250 @dnephin @nathanleclaire @shin- @mstanleyjones
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

Deploy preview ready!
Built with commit 0c2abb198e6a47451035e797683947db7dd12d65
https://deploy-preview-675--docker-docs.netlify.com


verbose=False is sometimes ignored

Description of the problem
I get Adding metadata with 3 columns despite passing verbose=False to mne.Epochs.
Alas, I cannot stably reproduce it.
However, I see that BaseEpochs.__init__ in mne/epochs.py passes verbose=False to GetEpochsMixin.metadata.fset instead of its own argument verbose.
This seems wrong.
Steps to reproduce
Alas, I cannot stably reproduce it.
Link to data
No response
Expected results
no output
Actual results
Adding metadata with 3 columns

Additional information
Platform:         Linux-6.0.6-76060006-generic-x86_64-with-glibc2.35
Python:           3.10.6 (main, Nov  2 2022, 18:53:38) [GCC 11.3.0]
Executable:       /usr/bin/python3
CPU:              x86_64: 8 cores
Memory:           15.3 GB
mne:              1.2.1
numpy:            1.23.4 {OpenBLAS 0.3.20 with 8 threads}
scipy:            1.9.3
matplotlib:       3.6.2 {backend=module://matplotlib_inline.backend_inline}
sklearn:          1.1.3
numba:            Not found
nibabel:          Not found
nilearn:          Not found
dipy:             Not found
openmeeg:         Not found
cupy:             Not found
pandas:           1.5.1
pyvista:          Not found
pyvistaqt:        Not found
ipyvtklink:       Not found
vtk:              Not found
qtpy:             2.3.0 {PyQt5=5.15.3}
ipympl:           Not found
pyqtgraph:        Not found
pooch:            v1.6.0
mne_bids:         Not found
mne_nirs:         Not found
mne_features:     Not found
mne_qt_browser:   Not found
mne_connectivity: 0.4.0
mne_icalabel:     Not found

Possibly related: https://github.com/mne-tools/mne-connectivity/issues/111

My apologies, the message  Adding metadata with 3 columns is coming from spectral_connectivity_epochs.


[admission][auto-instrumentation] Support .NET

What does this PR do?
This PR sets the required environment variables to automatically instrument a .NET application with the .NET Tracer using the Admission Controller.
Motivation
Additional Notes
The E2E test will need to be updated when the official .NET init image is published to GCR. For now, it's pinned to a dev build.
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Deploy the cluster agent and auto-instrument a .NET app, validate tracing and continuous profiler is working e2e.
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

The CircleCI Pipeline GitHub Action has automatically failed, do I need to add some Circle app permission to my GitHub account?

Is there some timeframe for when this will be released, we are currently enrolling in Datadog and auto instrumentation for dotnet would be incredibly nice
to have instead of having to manually alter each image.

Hi @frankbolero - we are currently waiting on our agent release cycle, and expect this to be released sometime in early to mid April. We appreciate your interest and patience!


Created Anime listing and Episode listing feature

This commit it to sync my Mobile device with my home computer


[Request] firefox-nightly-wayland

Link to the package upstream website/repository
N/A
Utility this package has for you
Firefox but without x11 dependencies, so it's lighter :3
Do you consider the package(s) to be useful for every Chaotic-Nyx user?
YES!
Do you consider the package to be useful for feature testing/preview?

[ ] Yes

Are you sure the package isn't available upstream already?

[X] Yes

Does the package's license allow redistributing it?
YES!
Have you searched the issues to ensure this request is unique?

[X] YES!

Have you read the README to ensure this package is not banned?

[X] YES!

More information
No response

Even though I'm an enthusiast about Wayland, I don't see any point in having something that will target less users while providing the exact same features/performance as the current wider option.
All the Wayland DEs pre-compiled in nixpkgs has XWayland enabled and brings all the XOrg deps with it.


Fix bugs in LADMM.py

Found a bug in LADMM where the BlockFunction and BlockDataContainer had incompatible sizes.
I think it probably happened because f(x) and g(x) were the other way round in the referenced paper than in the documentation (and for all other algos)
I've also slightly tidied up the code and renamed some variables (mostly for my benefit)

Hi @samdporter thanks for this PR.
Your code fails in 4 ADMM unit tests we've got, with the following errors:
ValueError: BlockFunction and BlockDataContainer have incompatible size

and
ValueError: __call__ expected BlockDataContainer, got <class 'cil.framework.framework.ImageData'>

We will re-check the paper scripts but, if you could send us the script that made you think that ADMM is not working, it would be extremely helpful.

This is odd because this is exactly the error I got originally that made me look into the code.
ValueError: BlockFunction and BlockDataContainer have incompatible size
I'll have a check to make sure that I haven't done anything silly with git first and then send you the script.
I'm currently running the altered LADMM on my PC and it's working well

I think LADMM is another version of PDHG. In PDHG, we have f as composite (with an operator) and g without an operator. In LADMM, it's the opposite, g is a composite and f without an operator.  See for instance a comparison with PDHG here

I did suspect this after reading the paper (where f & g were the other way round) and tried swapping the functions but had some other issues. I'll have another look, though. If this was already tested, I'm sure it was right originally

I think this is probably redundant as the tests worked OK previously. I must have just made a mistake in my implementation last night
It fixes the "f=G, g=F" problem, but I'm not sure how much that matters. Let me know if you'd like me to carry on with the PR otherwise I'll close it.
A good experience, anyway! hopefully next time my edits will fix something that's actually broken!


RuntimeError

Hi, I converted the notebook into py but I got this error when running the code:
RuntimeError:
An attempt has been made to start a new process before the
current process has finished its bootstrapping phase.
Do you have any idea of what's causing it?

Most likely this is some problem with multiprocessing on Windows. Setting num_workers=0 in the line sampler = nocd.sampler.get_edge_sampler(A, batch_size, batch_size, num_workers=5) might help.

hi, can you please help me , i am not getting any output even after installing every said module in the code  it shows "torch not compiled with cuda " i am running this notebook code on VScode .
thankyou.

This means your computer doesn't have a CUDA-compatible GPU. You can try running this code on Google Colab, they provide free GPUs there.

Hi , can you please define me how to give an edge list as  input to this training model .  I mean to say how  can i convert my edge list into the same  DATASET format which is given in this training model ..Thankyou


country selection data needs update

GDP and land mass in country selection screen needs to be Updated in API

fixed from backend


46 seeding estimator

The estimator now saves the calibration of each of the initialization for lat, lon, alt and baro reading in the parameters file. You can now pass an argument to the estimator node individually or the launch file as a whole, that will allow you to boot using the saved initialization rather than calibrating again.

So essentially if the estimator crashes, your you need to restart it you can simply do ros2 run rosplane rosplane_estimator_node true and it will start it from saved params. In the case from launch, you can do ros2 launch rosplane rosplane.launch.py seed_estimator:=true. Either would work, and if the estimator crashes it may be better to restart all of rosplane anyway.

It does! Actually it may only work for symlink files

To be fair, I think we should transition to have everyone by default use symlink installation. It is better in every way (I think).

It also works without it being symlinked installed. However, you won't see the saved parameters in the rosflight_ws. You have to go to the share folder to find the actual param file that gets loaded.
symlink-install is a good thing to do, but I don't think we can rely on everyone having done it. That means we should just put in the documentation somewhere that a user should go to the share folder to find the saved params if he/she didn't symlink install.

Something we also want to keep in mind is if we ever publish binaries of ROSplane, then I don't think they'll be installing the source files at all, only the install folder. So if it doesn't work on a non-symlink build, then that would be a problem.

I hadn't even thought of the binaries. I think we should start testing ROSplane for that soonish. Any Idea on how that is done typically @bsutherland333?

Something we also want to keep in mind is if we ever publish binaries of ROSplane, then I don't think they'll be installing the source files at all, only the install folder. So if it doesn't work on a non-symlink build, then that would be a problem.

Since it does work for non-symlinked files, we should be fine correct? Obviously we will have to check, but it should, right?


Smol menu bar blocks CMD Shift 5 shortcuts in other apps

i cant use the shortcut anymore in Jetbrains or any other app because its bound to smol fullscreen mode.
https://github.com/smol-ai/menubar/pull/68
would be nice to disable the shortcut or bind tit to something else

Shortcut is removed in #104!


Err value: JSONLD(KeyExpansionFailed)'

Problem
Using spruceid/ssi, I have implemented a function called issue_verifiable_credential() - see the whole function here:
https://github.com/DIN-Foundation/bcs-ntnu-2021/blob/d127ca53306616f351f8464cae006261b034f851/didland/src/lib.rs#L244-L283
I get the error on the line that runs vc.generate_proof() - See line: https://github.com/DIN-Foundation/bcs-ntnu-2021/blob/d127ca53306616f351f8464cae006261b034f851/didland/src/lib.rs#L276
Question
Any idea how I can debug this? :pray:
Backtrace
$ RUST_BACKTRACE=1 cargo run issue-passport self
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/didland issue-passport self`
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: JSONLD(KeyExpansionFailed)', /home/jonas/git/github.com/din-foundation/bcs-ntnu-2021/didland/src/lib.rs:276:69
stack backtrace:
   0: rust_begin_unwind
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/core/src/option.rs:1300:5
   3: core::result::Result<T,E>::unwrap
             at /home/jonas/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:1037:23
   4: didland::issue_verifiable_credential::{{closure}}
             at ./src/lib.rs:276:17
   5: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/jonas/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
   6: didland::issue_passport::{{closure}}
             at ./src/lib.rs:217:8
   7: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/jonas/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
   8: didland::run::{{closure}}
             at ./src/lib.rs:14:46
   9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/jonas/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  10: didland::main::main::{{closure}}
             at ./src/main.rs:10:18
  11: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /home/jonas/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80:19
  12: didland::main::{{closure}}
             at ./src/main.rs:1:1
  ....

If I add a line with a debug-print like this:
println!("{:?}: {:?}", issuer_jwk, proof_options);

I get the following output:
JWK {
  public_key_use: None,
  key_operations: None,
  algorithm: None,
  key_id: None,
  x509_url: None,
  x509_certificate_chain: None,
  x509_thumbprint_sha1: None,
  x509_thumbprint_sha256: None,
  params: OKP(OctetParams {
    curve: "Ed25519",
    public_key: Base64urlUInt([53, 93, 70, 80, 209, 75, 190, 120, 76, 126, 209, 89, 97, 224, 76, 210, 35, 127, 243, 249, 174, 184, 22, 169, 133, 165, 28, 192, 4, 5, 69, 105]),
    private_key: Some(Base64urlUInt([191, 134, 220, 53, 197, 220, 126, 8, 255, 245, 226, 121, 253, 8, 234, 105, 225, 39, 207, 115, 84, 242, 159, 56, 110, 151, 80, 146, 142, 168, 55, 197]))
  })
}

LinkedDataProofOptions {
  verification_method: Some("did:key:z6Mki3a9RaEhHetkCcpNVbH52S8ThdxUpKK2QMysCQUNnxAk#z6Mki3a9RaEhHetkCcpNVbH52S8ThdxUpKK2QMysCQUNnxAk"),
  proof_purpose: Some(AssertionMethod),
  created: Some(2021-04-08T14:47:01.138Z),
  challenge: None,
  domain: None,
  checks: Some([Proof])
}

Hi @Arxcis,
KeyExpansionFailed is happening during canonicalizing the document as JSON-LD for signing with Ed25519 Signature 2018. This error happens when there is some term used in the VC, VP and/or proof that is not defined in the JSON-LD contexts. The error is thrown in the json-ld crate. To debug it you can edit json-ld's source which is in a git submodule (forked) in ./json-ld of this repo.
The LinkedDataProofOptions and JWK you posted look fine. I don't see anything obviously wrong with the code you are using to generate the VC. Can you share what the VC looks like before generating the proof?
println!("{}", serde_json::to_string_pretty(&vc).unwrap());

I solved it by changing this:
    let vc = serde_json::json!({
        "@context": [
            "https://www.w3.org/2018/credentials/v1",
        ],
        "type": credential_type,
        "issuer": issuer_doc.id,
        "issuanceDate": ssi::ldp::now_ms(),
        "credentialSubject": {
            "id": subject_doc.id
        }
    });

to this!
    let vc = serde_json::json!({
        "@context": [
            "https://www.w3.org/2018/credentials/v1",
        ],
        "type": ["VerifiableCredential", credential_type],
        "issuer": issuer_doc.id,
        "issuanceDate": ssi::ldp::now_ms(),
        "credentialSubject": {
            "id": subject_doc.id
        }
    });

:smile:

@Arxcis great. Yes, the credential must have VerifiableCredential as the first type.
Reference: https://www.w3.org/TR/vc-data-model/#types


Add identifier for those of us that already have JSON turbine type formats

Feature request
We need to be able to branch code on the basis of the first field
About me
Openwind developer
Use Case
Branch to either our legacy format or this new format
Current state
Right now it looks like you dive straight in. So do we :) We need to continue supporting our users' legacy files while we try to move them onto this new version.

I think that once this identifier is added we would add code to Openwind to track the current octue power curve schema. This would allow us to test on the fly and to add new optional objects that are already compliant with the octue schema.

Label is really the label for that specific turbine type. What I mean is something to distinguish this JSON file type from any other JSON file type.
Maybe some like
schema: IEC61400-16
Something that we can easily and reliably if/then on and that will be the same for every single file that uses this schema.
Nick
p.s. sorry for the delay in getting back to you. I am currently travelling with family in Romania.

@NicholasMRobinson that would normally done in the metadata, by whatever system is managing the files or data blobs, allowing you to identify data without introspecting the data itself (otherwise you'd essentially have to read your entire data lake in order to find out which pieces of information you're looking for).
For example, you might have a database with a table of file records for metadata whose columns look like this:
id        manufacturer_label        model_name        rated_power    file_path
1         siemens                   SWT-Whatever      6000000        gs://my-bucket/power-curves/siemens/swt-whatever

And if you wished to keep track of schema versions explicitly you could add another column (my preference is not to do that but instead to keep all things :
id     ....    schema_uri
1      ....    https://jsonschema.registry.octue.com/windpioneers/power-curve/0.0.2.json

As a related sidenote, we should avoid property names similar to ones with special meaning like, in this case [the $schema dialect property](https://json-schema.org/understanding-json-schema/reference/schema.html#:~:text=The %24schema keyword is used,to the dialect %24schema identifies..

I think I fundamentally don't understand what we're doing. I don't get why we would go for the most complicated solution we can think of when there is a simple one. What am I missing please? What I am asking for is clearly completely different from turbine metadata. I want a way to know whether I am reading an Openwind JSON turbine spec or one that is in the format we're all trying to agree on here. Is that info already in there and obvious? Is that why this is causing confusion?

Is this what we should look for then? Not sure whether you're saying above that you have this or that you're opposed to it.
id     ....    schema_uri
1      ....    https://jsonschema.registry.octue.com/windpioneers/power-curve/0.0.2.json

Following up on our discussion on this a week (or two?) ago, we decided that we could account for this use case, plus allow much more generally useful document description if we were to allow DCMI metadata entries, and require that at least one of the entries be related to the format of the file. Our consensus was that the DCMI format tag was probably the best one.
I've started work on the document_metadata section and the [draft of that section can be seen and tried out here](Draft for the document metadata improvements is here: https://codesandbox.io/s/power-curve-document-metadata-dhkjxg?file=/src/schema.json) (this link should take you to a form allowing addition of any number of metadata elements).
I suggest the next step with this is that we add a constraint requiring that at least one format element must be added whose value is IEC61400-16
Then @NicholasMRobinson's use case is solved out of the box whilst remaining totally compliant with established practices for adding document metadata.

Done


license

Would you be willing to add a permissive license, such as an MIT license to this repo?  My company will not let me use this with the unlicense.

This is a question to take upstream to https://github.com/eligrey/classList.js


Cannot run pipeline to generate sequences

Dear Author,
I followed the example code using pipeline:
rita_gen = pipeline('text-generation', model=model, tokenizer=tokenizer)
sequences = rita_gen("MAB", max_length=20, do_sample=True, top_k=950, repetition_penalty=1.2,
num_return_sequences=2, eos_token_id=2)
I got:
The model 'RITAModelForCausalLM' is not supported for text-generation. Supported models are ['BartForCausalLM', 'BertLMHeadModel', 'BertGenerationDecoder', 'BigBirdForCausalLM', 'B......'
My transformers version is 4.22.0.dev0.
Please help. Thanks.

This warning is expected, the generation should nevertheless complete correctly. It's just a HF warning about our model not being part of the main repo.
Complete working example on google colab: https://colab.research.google.com/drive/16GO9fhJwCjcrFBL3MrGHsa9fyBAgth2n?usp=sharing

This is a version issue with the transformers/tokenizers package. I had this issue with the newer versions of transformers, but solved it by reverting to transformers==4.20.1


fix the issue to close the screen CGM and pump config

When opening the screen CGM config directly from the homescreen, the top menu “close / done” is not available. I use the same approach with pump config.
Updated with the same code as Trio.

Hi Pierre,
sry totally did not see this , also was away for a while. I am not used to this great participation - thank you. Will look at it  later.
@avouspierre


ALLOW_INSTALL_AS_ROOT=true not working

In the install.sh file at line:84 (sudo install "${MY_DIR}/tanzu" "${TANZU_BIN_PATH}" || handle_sudo_failure). This line does not take ALLOW_INSTALL_AS_ROOT=true into consideration (upon inspecting I did not find implementation for handle_sudo_failure). As a result when logged in as root user the install.sh script fails to install tanzu cli.
TCE version: 0.12.1
Error:
When logged in as root and executing ./install.sh under dir ~/tanzu/tce-linux-amd64-v0.12.1/ despite setting ALLOW_INSTALL_AS_ROOT=true the script yields error and fails to install tanzu on host machine.
Error Message:
Installing tanzu cli to /usr/local/bin/tanzu
./install.sh: line 84: sudo: command not found
./install.sh: line 84: handle_sudo_failure: command not found

./install.sh: line 111: tanzu: command not found
./install.sh: line 112: tanzu: command not found
./install.sh: line 114: tanzu: command not found
./install.sh: line 116: tanzu: command not found
./install.sh: line 118: tanzu: command not found

expected behavior:
When export ALLOW_INSTALL_AS_ROOT=true the script to successfully install tanzu cli is expected. The script should not throw error due to not being able to use sudo command. A condition or an appropriate usage implementation of handle_suro_failure should tackle the issue.
Thanks

Hi @alinahid477 - the missing handle_sudo_failure was fixed in https://github.com/vmware-tanzu/community-edition/pull/4550. That is waiting for a new release, but you could apply that change to your local install.sh script.
It appears ALLOW_INSTALL_AS_ROOT is working fine, otherwise the script would fail immediately and notify you it was not allowed:
https://github.com/vmware-tanzu/community-edition/blob/main/hack/release/install.sh#L40-L42
So the other than the handle_sudo_failure part missing, it looks like this is failing because for some reason your system is missing the sudo command. This should be fine to be called by root (root can run as root), but the command itself is just not in the path: sudo: command not found.
So either sudo needs to available in your PATH or you will need to create a ~/bin directory in your home directory and add that to your PATH:
mkdir ~/bin
export PATH=$PATH:~/bin
install.sh

Hi @stmcginnis
Thanks for the update.
Great to hear that handle_sudo_failure fix is going to be released soon.
Regarding sudo fail: not sure I follow.
If I am logged in as root in Linux (mint / debian disti) there's no sudo in the path (and shouldn't be as root use does not require sudo). Hence, a command in the install.sh file that requires sudo does not make sense when ALLOW_INSTALL_AS_ROOT=true , assuming the purpose of that var is to allow root user to run the script.
I would imagine the below logic would be applied instead (and that's what I have changed in my local for now. However, hoping that the distribution will be bug free):
previous (bug) code:
sudo install "${MY_DIR}/tanzu" "${TANZU_BIN_PATH}" || handle_sudo_failure
new code (bug fix):
if  $ALLOW_INSTALL_AS_ROOT
then
   install "${MY_DIR}/tanzu" "${TANZU_BIN_PATH}" || handle_sudo_failure
else
  sudo install "${MY_DIR}/tanzu" "${TANZU_BIN_PATH}" || handle_sudo_failure
fi

That's fair. Most distros still have sudo in the path, so root calling sudo just ends up being an noop.
This sounds like a reasonable approach to handle this case where sudo is not in the path. The conditional branching shouldn't be on ALLOW_INSTALL_AS_ROOT though, since that just allows the script to run. It doesn't necessarily guarantee the user actually is root. So maybe something like:
TANZU_BIN_PATH="/usr/local/bin"
if [[ ":${PATH}:" == *":$HOME/bin:"* && -d "${HOME}/bin" ]]; then
  TANZU_BIN_PATH="${HOME}/bin"
  echo Installing tanzu cli to "${TANZU_BIN_PATH}/tanzu"
  install "${MY_DIR}/tanzu" "${TANZU_BIN_PATH}"
elif [[ "$EUID" -eq 0 ]]; then
  echo Installing tanzu cli to "${TANZU_BIN_PATH}/tanzu"
  install "${MY_DIR}/tanzu" "${TANZU_BIN_PATH}"
else
  echo Installing tanzu cli to "${TANZU_BIN_PATH}/tanzu"
  sudo install "${MY_DIR}/tanzu" "${TANZU_BIN_PATH}" || handle_sudo_failure
fi

Do you want to submit a PR to add this? If not, I can submit a patch. Just let me know. Thanks!

@stmcginnis your code is elegant and yes please submit a patch.
Thanks a lot for looking into this.


Incorrect usage reported for the previous month.

The usage reported for the previous month at the month boundary does not seem to be correct.
Setup:
SLACK: 2D
resource: linux-container

Three submissions as follows:

usage 1 start/end at<PHONE_NUMBER>000 (Sat Oct 31 2015 00:00:00 GMT+0000 (GMT)) 2GB - submitted at 10/31 02:00 GMT
usage 2 start/end at<PHONE_NUMBER>000 (Sun Nov 01 2015 00:00:00 GMT+0000 (GMT)) 2GB - submitted at 11/01 02:00 GMT [Artificial event inserted at the month boundary]
usage 3 start/end at<PHONE_NUMBER>000 (Sun Nov 01 2015 22:00:00 GMT+0000 (GMT)) 1GB - submitted at 11/01 23:00 GMT

  "usage": [
    {
      "start":<PHONE_NUMBER>000,
      "end":<PHONE_NUMBER>000,
      "region": "us-south",
      "organization_id": "us-south:b3d7fe4d-3cb1-4cc3-a831-ffe98e20cf27",
      "space_id": "baeae239-f3f8-483c-9dd0-de5d41c38b6a",
      "consumer_id": "cloud-foundry-application:baaaaaaa-f3f8-483c-9dd0-de5d41c38b6a",
      "resource_id": "linux-container",
      "plan_id": "basic",
      "resource_instance_id": "cloud-foundry-application:baaaaaaa-f3f8-483c-9dd0-de5d41c38b6a",
      "measured_usage": [
        {
          "measure": "instance_memory",
          "quantity":<PHONE_NUMBER>
        },
        {
          "measure": "running_instances",
          "quantity": 2
        }
      ]
    }
  ]
}

{
  "usage": [
    {
      "start":<PHONE_NUMBER>000,
      "end":<PHONE_NUMBER>000,
      "region": "us-south",
      "organization_id": "us-south:b3d7fe4d-3cb1-4cc3-a831-ffe98e20cf27",
      "space_id": "baeae239-f3f8-483c-9dd0-de5d41c38b6a",
      "consumer_id": "cloud-foundry-application:baaaaaaa-f3f8-483c-9dd0-de5d41c38b6a",
      "resource_id": "linux-container",
      "plan_id": "basic",
      "resource_instance_id": "cloud-foundry-application:baaaaaaa-f3f8-483c-9dd0-de5d41c38b6a",
      "measured_usage": [
        {
          "measure": "instance_memory",
          "quantity":<PHONE_NUMBER>
        },
        {
          "measure": "running_instances",
          "quantity": 2
        }
      ]
    }
  ]
}

  "usage": [
    {
      "start":<PHONE_NUMBER>000,
      "end":<PHONE_NUMBER>000,
      "region": "us-south",
      "organization_id": "us-south:b3d7fe4d-3cb1-4cc3-a831-ffe98e20cf27",
      "space_id": "baeae239-f3f8-483c-9dd0-de5d41c38b6a",
      "consumer_id": "cloud-foundry-application:baaaaaaa-f3f8-483c-9dd0-de5d41c38b6a",
      "resource_id": "linux-container",
      "plan_id": "basic",
      "resource_instance_id": "cloud-foundry-application:baaaaaaa-f3f8-483c-9dd0-de5d41c38b6a",
      "measured_usage": [
        {
          "measure": "instance_memory",
          "quantity":<PHONE_NUMBER>
        },
        {
          "measure": "running_instances",
          "quantity": 1
        }
      ]
    }
  ]
}

Retrieve report at 2015-11-03T05:00:57Z which is after the SLACK period of 2 days
curl -v http://localhost:9088/v1/metering/organizations/us-south%3Ab3d7fe4d-3cb1-4cc3-a831-ffe98e20cf27/aggregated/usage

Since there were two instances of the application with 1GB of memory running in October for 24 hours,
the aggregated usage should be 24 hours * 2 instances - 48 hours or 172800000 milliseconds.
But the report shows the following month usage
                [
                  {
                    "quantity": {
                      "consumed": 158400000,
                      "consuming": 1,
                      "since":<PHONE_NUMBER>000
                    },
                    "cost": {
                      "burned": 22176,
                      "burning": 0.00014,
                      "since":<PHONE_NUMBER>000
                    },
                    "summary": 75.0578675,
                    "charge": 0.01050810145
                  },
                  {
                    "quantity": {
                      "consumed": 0,
                      "consuming": 4,
                      "since":<PHONE_NUMBER>000
                    },
                    "cost": {
                      "burned": 0,
                      "burning": 0.00056,
                      "since":<PHONE_NUMBER>000
                    },
                    "summary": 308.23147,
                    "charge": 0.0431524058
                  }
                ]

The full report is attached
scenario-1-linux.json.txt

There's a couple of things to look at here.

Based upon the usage records you posted, there seems to be an issue inside of the aggregation. The previous month(October in this case) is somehow marking itself as consuming 4 despite no further records for October were submitted (it should be 2).

For consumed, it makes sense for it to be 0 in October since there was no additional usage to accumulate against in October. The summary in this case would play the role of providing the correct consumed value.
However, the summary in this example does not check to see if the current time falls outside of the current usage's window. For example, the summary function is always taking the difference of time instead of taking the difference for the end of October to calculate its value. This is true of the charge function as well.
I believe one way to go about this is to pass the current window's timescale(second, minute, hour, day, month) into the summary/charge functions to allow the resource config to properly calculate a charge/summary within a certain window.

Based upon the full report, it seems like the previous day slack isn't being populated on a month change despite the usage fulling within that slack window.

To clarify on what i said on point two in my last comment regarding summary/charge functions.
Given a window of(based on the example linux-container):
[
  [
    {
      "quantity": 0
    }
  ],
  [
    {
      "quantity": 0
    }
  ],
  [
    {
      "quantity": 0
    }
  ],
  [
    {
      "quantity": {
        "consuming": 2,
        "consumed": 0,
        "since":<PHONE_NUMBER>000
      }
    }
  ],
  [
    {
      "quantity": {
        "consuming": 2,
        "consumed": 0,
        "since":<PHONE_NUMBER>000
      }
    }
  ]
]

Assuming no further usage submissions, if a report for this is called on<PHONE_NUMBER>000, summary/charge will be called on every window.
If we used the day window in this case for calculating the summary, we would get:
(1449100800000 -<PHONE_NUMBER>000) * 2 / 3600000 = 384.
Using the month window, the summary will result in the same value.
Ideally, the summary function should be able to tell when t has passed beyond its time threshold.
For instance, using the day window again.
1448409600000 is November 25th. Instead of using<PHONE_NUMBER>000(December 3rd), it may rather calculate against<PHONE_NUMBER>000(November 26th) to get<PHONE_NUMBER>000 -<PHONE_NUMBER>000) * 2 / 3600000 = 48 for the whole day of November 25th. This means that the summary for that day window would be for the usage of that day rather than the usage for that day up to December 3rd.
Likewise, if we use the month window.
Instead of using<PHONE_NUMBER>000(December 3rd), it may want to use<PHONE_NUMBER>000(December 1st) to get<PHONE_NUMBER>000-<PHONE_NUMBER>000) * 2 / 3600000 = 96 for the month of November.
In short, the summary/charge functions may want to be aware on which window(second, minute, hour, day, month) window they're working on such that a resource provider is able to correctly set boundaries for calculation instead of always using the query time, such that the summary/charge may bleed over into a different window.

If I understand correctly, that means that the summarize and charge functions need to be passed two times 'from', and 'to' (the boundaries of the given time window) instead of just 't' (the report time).
Thoughts?

I think that's a good approach. I'll add from/to to the summarize and charge functions that will represent the start and end of the window for a particular slack and time scale.
For this specific case, it would just need to choose to calculate against to rather than the query time.

I also agree, the calculations should be independent of slack setting.

These problems should now be fixed with b8802b054ec6f352387f730594e77c003865dab0 a269ff60ce41a085e53b52ea32eae58b07470cc6 500a0ae89999137c65ce95238a686297fa88c7db 148c90545ff012ffd13d7d7b19d089a0a61e7fa5


Parallel downloads stalling until the first request is complete

@lucas-clemente: Didn't we conclude that is an issue with Chrome? So this is a wontfix, isn't it?

Yep, there's nothing we can do. It seems that, when downloading many files at once (e.g. via command line), Chrome waits until the first download completes and only then sends the request for the other downloads. This is identical for HTTPS or QUIC, but interestingly not for HTTP.


[Event Request] codeunit 980 "Payment Registration Mgt." - OnUpdateApplicationFieldsOnCustLedgerEntryAfterCalcRemainingAmount

Describe the request
Hello, can you please add a new Event OnUpdateApplicationFieldsOnCustLedgerEntryAfterCalcRemainingAmount in codeunit 980 "Payment Registration Mgt."?
    local procedure UpdateApplicationFieldsOnCustLedgerEntry(TempPaymentRegistrationBuffer: Record "Payment Registration Buffer" temporary)
    var
        PaymentRegistrationSetup: Record "Payment Registration Setup";
        CustLedgerEntry: Record "Cust. Ledger Entry";
        GenJnlBatch: Record "Gen. Journal Batch";
        NoSeries: Codeunit "No. Series";
    begin
        PaymentRegistrationSetup.Get(UserId);
        GenJnlBatch.Get(PaymentRegistrationSetup."Journal Template Name", PaymentRegistrationSetup."Journal Batch Name");

        CustLedgerEntry.LockTable();
        CustLedgerEntry.Get(TempPaymentRegistrationBuffer."Ledger Entry No.");
        CustLedgerEntry."Applies-to ID" :=
          NoSeries.PeekNextNo(GenJnlBatch."No. Series", TempPaymentRegistrationBuffer."Date Received");
        CustLedgerEntry.CalcFields("Remaining Amount");
        OnUpdateApplicationFieldsOnCustLedgerEntryAfterCalcRemainingAmount(CustLedgerEntry);
        if (TempPaymentRegistrationBuffer."Amount Received" > CustLedgerEntry."Remaining Amount") then
            CustLedgerEntry."Amount to Apply" := CustLedgerEntry."Remaining Amount"
        else
            CustLedgerEntry."Amount to Apply" := TempPaymentRegistrationBuffer."Amount Received";
        CODEUNIT.Run(CODEUNIT::"Cust. Entry-Edit", CustLedgerEntry);
    end;

    [IntegrationEvent(false, false)]
    local procedure OnUpdateApplicationFieldsOnCustLedgerEntryAfterCalcRemainingAmount(var CustLedgerEntry: Record "Cust. Ledger Entry")
    begin
    end;

Additional context
We have additional values to calculate the Remaining Amount and need to recalculate it before being allocated and the record being modified.
Internal work item: AB#547380

Availability update: We will publish a fix for this issue in the next update for release 25.
Build ID to track: 26614.


Text selection

Currently all text in LM is selectable with the mouse. This by itself isn't awful, but it is a little unusual.
We however also prevent all key events, and right click events. So you can select text, but you can't even copy it, making it rather useless.
I think it would be best to disable text selection by default, but allow it in the content section (possibly definable with a flag when you create your content). Then allow for right click on the content section and allow for ctrl+c.

We still need to add some capabilities for copying and pasting in the content area, and possibly even item names and descriptions. Not having this behavior can be very frustrating to users, and usually being able to copy anywhere is one of the nice features of html.


Namadillo: Unshielding Transfer throws error Pseudo extended key is not defined

There are 2 forms to perform an Unshielding Transfer.
One is through the Transfer page, but Shielded to Transparent does not seem to do anything.
The other is through the Unshield button on the MASP page (/masp/unshield?asset=tnam1qy440ynh9fwrx8aewjvvmu38zxqgukgc259fzp6h) but the form throws an error when hitting the Submit button.

You can try to remove and import account again. We are aware of this, and trying to figure out the best solution.


Possibility to set bar in custom selector

Possibility to set bar in custom selector.
Added checking for selector existence.
Added ability to fix loader at the bottom on selected block.

I'm not entirely sure what the full intent behind this PR is, but it looks like you're trying to add a configuration option to position the loading bar at the bottom of the page.  If so, this can be easily done entirely through CSS, and should not require any modifications to the loading-bar's code

In my case, i needed to add bar to the bottom of custom block. Not in body. I need those line in my header. And if i just set
cfpLoadingBarProvider.parentSelector = 'header'

I will get
"Cannot read property 'lastChild' of undefined"

So we need to check $parent[0] existance


How to create nested form elements with one to many relationship

This is not a bug report but a request for documentation. If this is the wrong place to ask a pointer to the right place would be very much appreciated.
Given a state with a one to many relationship like this:
{
	currentUser: {
		id: 1,
		name: 'John Doe',
		email<EMAIL_ADDRESS>		phones: [
			{
				id: 1,
				number: '111222333',
				type: 'private'
			},
			{
				id: 2,
				number: '444555666',
				type: 'office'
			}
		]
	}
}

How can one create a form where existing phone numbers can be changed or deleted and new phone numbers be added?
Here is a CodePen sample that illustrates the goal: https://codepen.io/patrick/pen/xPYeQK
In that sample the missing parts are:

How to render the list of phone numbers if the state lives in the form state managed by react-redux-form. In the sample the initial list is rendered from the currentUser element which comes from the regular state which is probably wrong:

{this.props.currentUser.phones.map((phone, index) => (

    Number:
    <Control.text model={track('user.phones[].number', { id: phone.id })} />
    Type:
    <Control.text model={track('user.phones[].type', { id: phone.id })} />

)}

How to add a new phone number to the form or remove a phone number if the state lives in the react-redux-form managed form store? I am not sure how to access the form store and add an element to the phones array of the user that is currently edited. The sample already contains an add new phone number event handler, but what to put there:

  handleAddNumber(event) {
  }

If multiple numbers are added all would receive an initial 0 id. Would list item tracking as shown above still work given a state with two new numbers like the below. If not, what would be the right approach?

		phones: [
			{
				id: 1,
				number: '111222333',
				type: 'private'
			},
			{
				id: 0,
				number: '123123',
				type: 'home'
			}
			{
				id: 0,
				number: '321321',
				type: 'vacation'
			}

Many thanks for taking a look!

Can anyone tell if it is possible at all with react-redux-form? If not I will need to switch to something different.

It's possible. You can dispatch actions.push('user.phones', newPhone) to add a new phone, and of course it's smart to give each phone number a unique id (otherwise tracking won't work like you'd expect - since it'll just select the first match).

Many thanks for answering! I think the CodePen is almost there now. But actions.push doesn't seem to have an effect, probably because the initial list is not rendered from the react-redux-form managed state:
{this.props.currentUser.phones.map((phone, index) => (
...
))}

How would I render the list of phones from the react-redux-form managed state if the form state has been populated using
this.props.load('user', currentUser);

...

const mapDispatchToProps = (dispatch) => {
    return {
        load: (model, value) => {
            dispatch(actions.load(model, value));
        }
    };
}

probably because the initial list is not rendered from the react-redux-form managed state:

Can I see how your store is defined?

Sure! The CodePen: https://codepen.io/patrick/pen/xPYeQK contains the whole example.

I added dispatch to actions.push, sadly still no effect:
this.props.dispatch(actions.push('user.phones', { id:3, number:'777', type:'mobile'}));
Maybe how I load the initial state is the problem:
this.props.dispatch(actions.load('user', currentUser));
currentUser comes from the redux state and is mapped to props using connect. I suspect 'user.phones' is not related to that entity.
Updated CodePen: https://codepen.io/patrick/pen/xPYeQK

I finally found where the current form state is available in the redux store. After mapping it into the props of the form component things started working:
const mapStateToProps = (state) => {
    return {
        user: state.user
    };
}

...

{user.phones.map((phone, index) => (

	  Number:
	  <Control.text model={track('user.phones[].number', { id: phone.id })} />
	  Type:
	  <Control.text model={track('user.phones[].type', { id: phone.id })} />

))}

For creating new unique ids when adding phone numbers I use this:
handleAddNumber(event) {
	let { dispatch, user } = this.props;

	let newID = -1;
	user.phones.forEach(function (phone) {
	  if (newID >= phone.id)
		newID = phone.id - 1;
	});

	dispatch(actions.push('user.phones', { id:newID, number:'', type:''}));
}

Working CodePen: https://codepen.io/patrick/pen/xPYeQK
Feel free to close this issue. Thanks for taking a look!


Add support for regional STS endpoint(s)

Supports STS endpoints in GovCloud, China and Regional partitions for AWS.

:+1:

thanks a lot for the PR, @burdzwastaken. Could you please give us a  bit more details of why not go with the default resolver?

I will admit I completely missed the default resolver. let me test it out in our govcloud environment and update the PR.


Add support for KHR_texture_transform

Objective
Support the KHR_texture_transform extension for the glTF loader.

Fixes #6335

Solution
As is, this only supports a single transform. Looking at Godot's source, they support one transform with an optional second one for detail, AO, and emission. glTF specifies one per texture. The public domain materials I looked at seem to share the same transform. So maybe having just one is acceptable for now. I tried to include a warning if multiple different transforms exist for the same material.
Note the gltf crate doesn't expose the texture transform for the normal and occlusion textures, which it should, so I just ignored those for now.
Via cargo run --release --example scene_viewer ~/src/clone/glTF-Sample-Models/2.0/TextureTransformTest/glTF/TextureTransformTest.gltf:

Changelog
Support for the KHR_texture_transform extension added.

message above is due to a network error on crates.io

Your screenshot doesn't look exactly like the expected (https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/2.0/TextureTransformTest), it seems the background for out of texture quads are not the same. Do you know why?
How would it work with https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/2.0/TextureTransformMultiTest?

Your screenshot doesn't look exactly like the expected (https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/2.0/TextureTransformTest), it seems the background for out of texture quads are not the same. Do you know why?

The default camera and lighting in the scene viewer make it hard to see. The background in the arrow texture is there, just very faint, if that's what you mean.

How would it work with https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/2.0/TextureTransformMultiTest?

This looks far from complete because the loader doesn't support texture coord sets. I see there's some TODOs in the source code. The renderer doesn't do clearcoat, and the gltf crate doesn't expose a texture transform for occlusion.

A Affine2 seems better (smaller and faster) for the transform than a Mat3?

Hi… Any update on this??

Closes #11869

I'm currently updating this PR to main and addressing the comments on my fork :)

Done, just got some questions on the new PR

Closing as adopted :)


[SUGGESTION] More/Better Planets

While I haven't seen any planets in the skies yet (I've been looking from time to time), I do know Venus, Mars, and Jupiter at the very least exist as textures in the assets. My suggestions are as follows:

Planets have phases as well.
Jupiter has a layer over it that contains up to four pixels, representing the Galilean moons. This texture also has phases, though instead of showing how sunlight reflects off them, they show the moons in different positions around Jupiter. The moons' orbit phase may be independent of Jupiter's phase.
Saturn and Uranus also show up. Their phase texture has more states than other planets, as the rings are viewed from different angles.
Mercury and Neptune also show up, and would appear similar to how Mars might as far as phases are concerned.
Mercury and Venus, if this is not already a thing, would always be near the sun, and would be the first objects to appear in the evening, and the last to disappear in the morning. They may remain visible during the day if they are in transit in front of the sun.

I do have the textures, though I have not yet used them anywhere, since am missing the mechanics.
I know it would be easier to either have the planets orbit around the Overworld or stay in the same place relative to the sky, but I really want to make some simple to use system which players can use to define solar systems with individual planets and then simply select which planet of the system the dimension corresponds to and have the sky be based on that.
That way I could easily add different planets that would show up in the sky, which would be subject to apparent retrograde motion.
Your idea with Jupiter is quite nice and I may use it if I don't find a way to make the moons orbit around Jupiter in a believable way by having them move.
As for the idea with Uranus and Saturn, that's absolutely an awesome way to showcase the rings!
Mercury and Venus being the first to appear in the morning is also a cool idea. I was already pondering if I should have multiple star layers that would be visible at different times, so this would be a nice addition to that.

What you'd about have to do is make a simple, hidden simulation of the solar system, then draw lines from the object representing the Overworld to all other objects, and then use the angles and what not to draw the various planets/stars/etc in the skybox, using the sun's location as the skybox's main point of reference as it would be too complicated to move it. With this accomplished, you can customize the orbital radius, eccentricity, inclination, etc of each planet individually, and it should show up correctly no matter what.

Yes, the biggest problem is figuring out how to make that into something players could edit inside the assets folder and then parsing it to the game

You could take inspiration from Galacticraft or Universe Sandbox for that. Have a GUI that draws the hidden simulation of the solar system on screen, as well as the orbits of planets/moons. Then, click on an object, and you get sliders to change the orbit. But that might be a bit too involved and un-Minecrafty for what you're after.

You could take inspiration from Galacticraft or Universe Sandbox for that. Have a GUI that draws the hidden simulation of the solar system on screen, as well as the orbits of planets/moons. Then, click on an object, and you get sliders to change the orbit. But that might be a bit too involved and un-Minecrafty for what you're after.

What you described is a GUI, I do like that idea, but that's not what I was talking about. Galacticraft had the planets pre-made and unchangable. I could make a GUI like that fairly simply (although given my texturing skills, it would take me a long time just to make it not look bad).
The problem is getting it to work in the first place, as I know next to nothing about how json (which are used for physically storing the information) files are accessed from the assets folder.
I know how to parse them from data folder when the game starts, but that's quite different as I have access to the server, whereas with Client-side mods (which Stellar View is supposed to be), access to server is required to be very limited (for example, doing things like spawning mobs, changing the actual light level and placing blocks is impossible), otherwise it would need to be installed on servers as well, which I do not want

The GUI would merely exist to make tweaking settings more visual and therefore easier, and shouldn't need to involve the server. The alternative is to have something similar to the setting menu to adjust the galaxy's position in the sky, where it's a load of sliders and buttons.

Yup, pretty much.
Hypothetically there might be a way to create a list of settings with unique naming, but that's thinking way too far ahead.

JSON, right?
I have some experience with that. I can make a skeleton.
{
  "mercury": {
    "orbitRadius": 0.39,
    "parent": "sun"
  },
  "venus": {
    "orbitRadius": 0.72,
    "parent": "sun"
  },
  "overworld": {
    "orbitRadius": 1.0,
    "parent": "sun"
  },
  "moon": {
    "orbitRadius": 0.0025,
    "parent": "overworld"
  },
  "mars": {
    "orbitRadius": 1.52,
    "parent": "sun"
  },
  "jupiter": {
    "orbitRadius": 5.2,
    "parent": "sun"
  },
  "saturn": {
    "orbitRadius": 9.58,
    "parent": "sun"
  },
  "uranus": {
    "orbitRadius": 19.2,
    "parent": "sun"
  },
  "neptune": {
    "orbitRadius": 30.0,
    "parent": "sun"
  }
}

Using some circle math and this JSON, you can loop through all the planets, and have them orbit the parent body. Another variable you could store for each planet is apparent magnitude, to control how large each of them appear in the sky, so they don't have to be hardcoded. And you could just add more things as needed.
If this isn't what you had in mind, I apologize.


Rust reference client

Grpc Reference Client that allows a user to specify a cosmos endpoint, steward endpoints, and TLS configurations for connections.
Client blocks until active voting period, then sends requests in parallel to all steward instances specified before returning a tuple of results and failures.

Closing because of staleness


Add ios support

It resolves #54
Solution found here: https://stackoverflow.com/a/41267511

Coverage decreased (-9.09%) to 90.909% when pulling 324655d23d1d2060c405cf236d2a565acb99e39a on shrpne:feature-ios-support into 62a3835727d21d911439758d0da656784b4249c0 on omichelsen:master.

Thanks, this does seem to fix it!
Could you remove the conditional around it (remove the node.select()) completely? I have tested that the setSelectionRange also works fine in all other browsers, and I would rather not have custom browser detection code in this lib.
It will also get the test coverage back to 100% :)

Coverage remained the same at 100.0% when pulling 65db39d05abd318b34068896035894aa91784972 on shrpne:feature-ios-support into 62a3835727d21d911439758d0da656784b4249c0 on omichelsen:master.

@omichelsen
Done.
I not tested other browsers, hope it really works, especially in mobile browsers :)

Cool, thanks!


Thermostat Room Sensors

Is is possible to get the data from the thermostat room sensors?

Hey @jamespet77, thanks for the question. I would love to add support for these! I didn't even know they existed until now.
So, what typically will happen with something like this is that I would need you to share the devices with me (temporarily) via the app. There is at least one open bug for the thermostat, so if you could share the sensor(s) and the thermostat, I can add support for this. My email for the Wyze account is shaun  tarves  net

I can do that.
just to confirm its shaun at tarves dot net

Yessir!
On Mon, Oct 10, 2022 at 6:09 PM James Peterson @.***>
wrote:

I can do that.
just to confirm its shaun at tarves dot net
—
Reply to this email directly, view it on GitHub
https://github.com/shauntarves/wyze-sdk/issues/94#issuecomment-1273860717,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEDBMATVSAWKTPO5ORBHDDWCSHZPANCNFSM6AAAAAARA6SWD4
.
You are receiving this because you commented.Message ID:
@.***>

Sent.  It has one room sensor linked.  I have another room sensor if you need multiple.

@jamespet77 I've just pushed initial support for reading room sensor data to branch 94-thermostat-room-sensors
You can get a list of sensors connected to a thermostat by issuing:
sensors = client.thermostats.get_sensors(device_mac=<device_id>, device_model='CO_EA1')

The sensor object looks like this:
for _sensor in sensors:
    print(f"    id: {_sensor.did}")
    print(f"        name: {_sensor.nickname}")
    print(f"        temperature: {_sensor.temperature}")
    print(f"        humidity: {_sensor.humidity}")
    print(f"        battery: {_sensor.battery}")
    print(f"        state: {_sensor.state}")
    print(f"        status: {_sensor.status}")
    print(f"        auto_comfort_mode: {_sensor.auto_comfort_mode}")
    print(f"        comfort_balance_weight: {_sensor.comfort_balance_weight}")
    print(f"        temperature_threshold: {_sensor.temperature_threshold}")

id: CO_TH1_XXXX
        name: Kitchen
        temperature: 73.86
        humidity: 33
        battery: RoomSensorBatteryLevel.LEVEL_3
        state: RoomSensorStateType.ONLINE
        status: RoomSensorStatusType.MANUAL_UP
        auto_comfort_mode: ThermostatSensorTemplate.HOME_SLEEP
        comfort_balance_weight: ThermostatSensorComfortBalanceMode.BALANCE
        temperature_threshold: 5

Thanks Shaun!!  big help.  Wyze needsto put you on the team.

Give it a try and make sure it's working for your use cases. If so, I'll
merge to master and make a new release.
I'm going to use this opportunity to address
https://github.com/shauntarves/wyze-sdk/issues/51 and
https://github.com/shauntarves/wyze-sdk/issues/42 so might be a few days.
On Wed, Nov 2, 2022 at 2:44 PM James Peterson @.***>
wrote:

Thanks Shaun!! big help. Wyze needsto put you on the team.
—
Reply to this email directly, view it on GitHub
https://github.com/shauntarves/wyze-sdk/issues/94#issuecomment-1301068758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEDBMFOWK3UQITWXP6Z3VTWGKZA3ANCNFSM6AAAAAARA6SWD4
.
You are receiving this because you were assigned.Message ID:
@.***>


shared-worker-loader not works

Hello!
i'm trying demo code from shared-worker-loader doc https://github.com/mrtnbroder/shared-worker-loader. Webpack compile successfully but nothing happend when page loaded (No console logs, no errors, no debugger started). What is my mistake and why Shared Worker does not loaded??
var MySharedWorker = require('shared-worker-loader!./file')

var worker = new MySharedWorker()
worker.addEventListener('message', (e) => {console.log("message !!!!!!!!!!!!!!!!!!!1")})
worker.port.onmessage = (e) => {console.log("message ????????????????????????")}
worker.port.start()

file.js
console.info("i am shared worker!!!")

onconnect = function (e) {
  sadfsadfsdaf.setdsaf().asfsadf()
  debugger
  console.log(e);
}

Better wait for an answer at https://github.com/mrtnbroder/shared-worker-loader/issues/2. Thanks. 👍


Load custom jar in JMX command

What does this PR do?
It loads custom_jar_paths from integrations init_config calling agent jmx commands.
Motivation
I need to test jboss integration, which requires a custom jar, and currently it
fails to run because it doesn't add the jar to the classpath.
Additional Notes
I haven't tested it yet.

Thanks, I think I handled everything, let me know how it looks.

A few more comments, and I'll ask again: were you actually able to test the changes? :)

No, I wasn't able to. Is there a build available in CI to test?

Tested, it works great. Thanks!


Add error callback to subscription

Currently, if an exception occurs during message processing then it is simply ignored. This PR adds an error callback to the subscriptions, addressing the FIXME in Client._process_msg.
New behavior:
If an error callback is provided and an exception occurs during message processing, then the error callback is invoked. If the error callback itself raises an exception, then that exception is logged.

Thanks for merging this.
Any idea why this broke the 3.5 tests though? I couldn't figure out why.

Not sure either, will have to take a look.

Sorry for the delay, I will do a release today with this change

Pushed new version now: https://github.com/nats-io/asyncio-nats-streaming/releases/tag/v0.2.0

Thank you @wallyqs!


MoLoader get error if msgid_plural string with msgstr[1]

The .po file is like
msgid "%s has been added to your cart."
msgid_plural "%s have been added to your cart."
msgstr[0] "%s has been added to your cart."
msgstr[1] "%s have been added to your cart."

when i try to load that .mo file with MoLoader get the php error
TypeError: Argument 1 passed to Gettext\Translation::translatePlural() must be of the type string, array given, called in composer\vendor\gettext\gettext\src\Loader\MoLoader.php on line 100 in composer\vendor\gettext\gettext\src\Translation.php on line 148
Both the .mo build with the library or Poedit get the same erro.
use Gettext 5.2.1 with php 7.3.13

Yes, It's an error indeed.
New version 5.2.2 released with this patch. Thank you!


"Uses a parameter that has not been defined" for RemoteModeActive and Smoothing/Local

As the title says, the VRChat SDK builder is telling me that these two parameters are not defined. It's especially strange since I was able to upload it just before, but I decided to tweak a blendshape and got this result out of it.

Please post screenshots of console error.


Show the reason a search result is found

Show skos:hiddenLabel in result with the search words highlighted.

We somehow need to pass the search query to the html rendering of a resource.

This issue was moved to zazuko/zack-search#5


qam3-runner add metadata feature

What should we add?
Not sure if this is the right place for a feature request on the qam3-runner program.
To make is more useful and more like the backend.run method, the user needs to be able to add metadata to the job and ideally each submitted program.
Perhaps a simple metadata:dict optional key arg to the qam3-runner would be ok.

Metadata may be attached to the circuits object (circuit.metadata), and this will be stored in the result header. This is for backward compatibility with qiskit-experiments. In general, it is not a good idea to use the job result as a database and you should store this information separately and associate it in analysis with job results..


Accessing vue instance in beforeEach or beforeEnter

I know that in beforeRouteEnter you can access the vue instance by passing a callback to next. Is it possible to access it in beforeEach/beforeEnter?

No.


Change The template of Filed

I want to change from this
{% if not field|is_checkbox %}
    {{ field}}
{% endif %}

to this
{% if not field|is_checkbox %}
    <input type="text" class="form-control" id="{{ field.auto_id }}" name="{{ field.name }}" placeholder="Name" required>
{% endif %}

but I can't know the property of the field, the only ting I know is .name and .auto_id
by the way, it is customization of https://github.com/mishbahr/djangocms-forms/blob/master/djangocms_forms/templates/djangocms_forms/form_template/default.html

FYI If you just want to add CSS class "form-control" to all inputs, simply add the following to your project settings:
DJANGOCMS_FORMS_WIDGET_CSS_CLASSES = {'__all__': ('form-control', ) }

or just to add it to "checkbox" widgets, add the following:
DJANGOCMS_FORMS_WIDGET_CSS_CLASSES = {'checkbox': ('form-control', ) }

Oh, Thanks it works perfectly!


Support shrinking in generators for dstreams

basic shrinking support is available for BatchGen

For PDStreamGen a trivial generator like the following makes no sense for temporal generators:
implicit def shrinkDStream[A] : Shrink[PDStream[A]] = Shrink(pdstream =>
  // unwrap the underlying Seq, shrink the Seq, and rewrap
  shrink(pdstream.toSeq).map(PDStream(_:_*))
)

The problem is that given a PDStream[A] value we have no way to know which temporal operator was used to generate it, or with which timeout, so if we shrink like with a Seq we get a nonsense behaviour. It could make sense to write a generator that respects the different occurrences of the different batches, the idea is given a PDStream ds with a batch b with n occurrences of b, ie ds = C[b,b,b] corresponding to a 3 hole context with that 3 occurences of b its only ocurrences, then we might shink b into b' and then shrink ds as ds' = C[b',b',b']. That can be performed for all the different batches, thus obtaining a shrunk version of ds that has the same temporal structure. This reasoning should be double checked


[Bug]: Device Type HPU is not supported for torch.generator() API

Your current environment

The output of `python collect_env.py`
Collecting environment information...
/usr/lib/python3.10/inspect.py:288: FutureWarning: `torch.distributed.reduce_op` is deprecated, please use `torch.distributed.ReduceOp` instead
  return isinstance(object, types.FunctionType)
PyTorch version: 2.4.0a0+git74cd574
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.5 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.22.1
Libc version: glibc-2.35

Python version: 3.10.12 (main, Nov  6 2024, 20:22:13) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-126-generic-x86_64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                         x86_64
CPU op-mode(s):                       32-bit, 64-bit
Address sizes:                        46 bits physical, 57 bits virtual
Byte Order:                           Little Endian
CPU(s):                               192
On-line CPU(s) list:                  0-191
Vendor ID:                            GenuineIntel
Model name:                           Intel(R) Xeon(R) Platinum 8468
CPU family:                           6
Model:                                143
Thread(s) per core:                   2
Core(s) per socket:                   48
Socket(s):                            2
Stepping:                             8
BogoMIPS:                             4200.00
Flags:                                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 invpcid_single cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr amx_bf16 avx512_fp16 amx_tile amx_int8 flush_l1d arch_capabilities
Virtualization:                       VT-x
L1d cache:                            4.5 MiB (96 instances)
L1i cache:                            3 MiB (96 instances)
L2 cache:                             192 MiB (96 instances)
L3 cache:                             210 MiB (2 instances)
NUMA node(s):                         2
NUMA node0 CPU(s):                    0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58,60,62,64,66,68,70,72,74,76,78,80,82,84,86,88,90,92,94,96,98,100,102,104,106,108,110,112,114,116,118,120,122,124,126,128,130,132,134,136,138,140,142,144,146,148,150,152,154,156,158,160,162,164,166,168,170,172,174,176,178,180,182,184,186,188,190
NUMA node1 CPU(s):                    1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59,61,63,65,67,69,71,73,75,77,79,81,83,85,87,89,91,93,95,97,99,101,103,105,107,109,111,113,115,117,119,121,123,125,127,129,131,133,135,137,139,141,143,145,147,149,151,153,155,157,159,161,163,165,167,169,171,173,175,177,179,181,183,185,187,189,191
Vulnerability Gather data sampling:   Not affected
Vulnerability Itlb multihit:          Not affected
Vulnerability L1tf:                   Not affected
Vulnerability Mds:                    Not affected
Vulnerability Meltdown:               Not affected
Vulnerability Mmio stale data:        Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Not affected
Vulnerability Spec rstack overflow:   Not affected
Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:             Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI BHI_DIS_S
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Not affected

Versions of relevant libraries:
[pip3] habana-torch-dataloader==<IP_ADDRESS>4
[pip3] habana-torch-plugin==<IP_ADDRESS>4
[pip3] numpy==1.26.4
[pip3] pynvml==8.0.4
[pip3] pytorch-lightning==2.4.0
[pip3] pyzmq==26.2.0
[pip3] torch==2.4.0a0+git74cd574
[pip3] torch_tb_profiler==0.4.0
[pip3] torchaudio==2.4.0a0+69d4077
[pip3] torchdata==0.7.1+5e6f7b7
[pip3] torchmetrics==1.6.0
[pip3] torchtext==0.18.0a0+9bed85d
[pip3] torchvision==0.19.0a0+48b1edf
[pip3] transformers==4.47.0
[pip3] triton==3.1.0
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.1.dev3707+gab085c8 (git sha: ab085c8
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
Could not collect

Model Input Dumps
No response
🐛 Describe the bug
when HPU benchmarks scripts available with vllm is run with Gaudi cards,  benchmarks/model execution is failing with error as Device Type HPU is not supported for torch.generator() API .  Attached is the screenshot of
Command to run:
root@xmr-gaudi2-dell03:/vllm# python3 benchmarks/benchmark_latency.py       --output-json results//latency_llama8B_tp1.json       --model meta-llama/Meta-Llama-3-8B-Instruct --tensor-parallel-size 1 --load-format dummy --num-iters-warmup 5 --num-iters 15
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Attached is the screenshots


Tag a release

If this module is anywhere stable, please tag a release version.

Yes, we typically apply release tags to everything in the OpenZiti project.  This repo will have tags soon.  This is a brand new repo, and is somewhat experimental in its current state.  The next wave of work will bring in tags.


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=398430205
https://github.com/Azure/azure-cli-extensions/commit/b56e5f560667a949fd8ed60da82fc106d092950f

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.