PermissionsAndroid.request never resolves

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes.
Environment
Environment:
OS: macOS Sierra 10.12.6
Node: 9.4.0
Yarn: 1.3.2
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 3.0 AI-171.4443003
Packages: (wanted => installed)
react: 16.2.0 => 16.2.0
react-native: 0.53.0 => 0.53.0
Edit: according to @MateRyze, it still happens on react-native 0.55.4.
Target Platform: Android 6.0.1
Steps to Reproduce
We have a Camera component and it should check for the Camera permission before mounting.
In my app's AndroidManifest.xml I have the line, along with many other permissions:
<uses-permission android:name="android.permission.CAMERA"/>

In our component's componentDidMount() we call a function that should return true if we have permission and false if we do not have, here is the relevant snippet of the function:
if (Platform.OS === 'android') {
const isGranted = await PermissionsAndroid.check(PermissionsAndroid.PERMISSIONS.CAMERA);
      if (isGranted) {
        return true;
      }
      try {
        console.log('before request');
        const granted = await PermissionsAndroid.request(
          PermissionsAndroid.PERMISSIONS.CAMERA,
          {
            title: 'Dialog Title',
            message: 'Dialog Message',
          }
        );
        console.log('after request');
        return granted === PermissionsAndroid.RESULTS.GRANTED;
      } catch (err) {
        console.log('error');
        console.log(err);
      }
}

Expected Behavior
A dialog with my title and message should appear, if the user clicks on "Allow", the promise should resolve and my component should render as expected.
Actual Behavior
A dialog with a different message and title appears. I click on "Allow" and the promise is never resolved or rejected.
In my logs, only the "before request" log appears. Neitherconsole.log('after request') or console.log('error') is logged, so I presume the code is stuck in the await.
I am following this doc.

up :(

Up again. This error happens in one of our apps in production, we tried to make a workaround for it multiple times but nothing works. Even if we ask for the permission when the app starts, it still hangs and never resolves.
@aryo, will try to confirm what you said, thanks
Would love any follow up

The alert asking for permission is shown as expected, but sometimes in case of denial the promise do not resolves and because of this the app flow stops. If the permission is granted the flow goes as expected, the promise resolves.

This is happening to us, appears to most reliably happen on one of our testers' Nexus 6; doesn't repro on some other Android devices. For us no matter if the permission is granted or denied, it can lead to the unresolving promise it seems.
react-native-cli: 2.0.1
react-native: 0.51.0
platform: android
builds: at least release builds

It happens with different android versions and different devices for us.
First we hoped it would be because of the old react native version 0.38 it is, but i don't think this is the case after your comment jslz.
We tried different build tool versions and target/compile versions. The issue still remains the same.

I have a similar problem with PERMISSIONS.ACCESS_FINE_LOCATION: the dialog doesn't appear and the promise is also not resolved.
react-native version: 0.55.4

@MateRyze as an aside & by the by, apparently some Android permissions are not considered "dangerous" and so I guess those ones do not put up an extra dialog box from Android OS itself?
https://stackoverflow.com/questions/34808769/android-6-0-what-is-the-difference-between-dangerous-and-special-permissions
(That's separate from the promise-never-resolving issue.)

@jgfidelis Are you using react-native-navigation?
I have the same issue you have, and I think it is because the onRequestPermissionsResult method in the MainActivity never get's called due to NavigationActivity.

@rcidt, yes fwiw we are using wix rnn.

@jslz I am 99% sure that is the reason the promise never resolves. I am opening a ticket with them, maybe they can help.

I found this PR https://github.com/wix/react-native-navigation/pull/470 there are some important details at the end of the thread

@jslz but the location permission is dangerous. Moreover it doesn't resolve :(

@MateRyze oh dang. Thanks for pointing that out.

We have the "not resolving" issue in a project without any navigation
library.
jslz<EMAIL_ADDRESS>ezt írta (időpont: 2018. máj. 24., Cs
22:12):

@MateRyze https://github.com/MateRyze oh dang. Thanks for pointing that
out.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/17985#issuecomment-391843574,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AP4R9jLAe1tTX4ZPCAWBrOq3Oro2G6F2ks5t1xQQgaJpZM4SFz46
.

@rcidt No, we do not use react-native-navigation on the app we have this issue.

I am seeing this happen 90% of the time. A few times the promise actually resolves, but that's like 10% of the time.
This issue is making our android app basically unusable :(

Updated RN to 0.55 and I have no more issues with PermissionsAndroid

Confirmed, upgrading to the following versions fixes the issue:
    "react": "16.4.0",
    "react-native": "0.55.4",

@MateRyze before you installed:
"react": "16.4.0",
"react-native": "0.55.4",

did you also do a rm -rf ./node_modules package-lock.json?
The only difference might be that I'm using the "promise/then" syntax in lieu of "async/await", ex:
    requestAndroidPermissions() {
        if (Platform.OS === 'android') {
            var permissions = [
                PermissionsAndroid.PERMISSIONS.ACCESS_FINE_LOCATION,
                PermissionsAndroid.PERMISSIONS.ACCESS_COARSE_LOCATION
            ];

            try {
                PermissionsAndroid.requestMultiple(permissions).then(granted => {
                    // Object.entries(granted).map(([key, value]) => {
                    // });
                    this.nextAction();
                });
            } catch (err) {
                console.warn(err);
            }
        } else if (Platform.OS === 'ios') {
            this.nextAction();
        }
    }

which shouldn't matter, but perhaps it does.

@MateRyze also using
PermissionsAndroid.requestMultiple()

@MateRyze this is a long shot, but can you try changing your code to use then rather then awai/async just to see if the bug still happens? I don't think it will make any difference, but lets try anything...

We fixed it by requesting the permission on app startup.

I just wrapped it in another promise, seems to work well for me.
getPermissions() {
  return new Promise(async(resolve, reject) => {
    const permissions = await PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.READ_EXTERNAL_STORAGE);
    if (permissions === PermissionsAndroid.RESULTS.GRANTED) resolve(true);
    else reject(false);
  });
}

@Asleepace so PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.READ_EXTERNAL_STORAGE) works because the rationale is undefined.
What happens if you pass rationale as the second parameters?

@kanekotic still works with the rationale as well
    getPermissions() {
      return new Promise(async(resolve) => {
        const permissions = await PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.READ_EXTERNAL_STORAGE,{
          'title': __('Local Storage Permissions'),
        'message': __('Needed for uploading files with the share extension.')
        });
        if (permissions === PermissionsAndroid.RESULTS.GRANTED) resolve(true);
        else resolve(false);
      });
    }

This code:
import React, { PureComponent } from 'react'
import { View, Text, Image, Platform, TouchableOpacity, PermissionsAndroid } from 'react-native'
import styles from './styles'
import i18n from '../../../../assets/i18n/'

export default class extends PureComponent {
  componentDidMount() {
    this.checkLocationPermissions()
  }

  async checkLocationPermissions() {
    try {
      const granted = await PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.ACCESS_FINE_LOCATION, {
        title: i18n.t('locationRequest.title'),
        message: i18n.t('locationRequest.message')
      })
      console.log('checkLocationPermissions granted: ', granted)
      if (granted === PermissionsAndroid.RESULTS.GRANTED) {
        console.log('checkLocationPermissions granted ')
      } else {
        console.log('checkLocationPermissions denied')
      }
    } catch (err) {
      console.log('checkLocationPermissions err: ', err)
    }
  }

  render() {
    return <View style={{ flex: 1, backgroundColor: 'blue' }} />
  }
}

With:
    "react": "16.4.1",
    "react-native": "0.56.0",

In Xiaomi Mi Mix 2 (Android 8 with MIUI) and Motorola Moto G (Android 6):

(granted == 'never_ask_again')

still the issue persists. I'm using RN v0.53. Any workaround, as I don't want to upgrade my RN version

anyone can tell me how to use permissionandroid in reactantive webview ?

In our case this was happening because our main activity does not extend ReactActivity.
ReactActivity has some glue that handles notifying React Native that a permissions request is finished via PermissionListener. We had to roll this ourselves - when React calls requestPermissions on the activity, save off the provided PermissionListener, and then later call listener.onRequestPermissionsResult when your activity's onRequestPermissionsResult is invoked.

I am running into this problem with PermissionsAndroid.requestMultiple() when permissions are not already granted. If permissions are not already granted when requestMultiple() is called and the dialog has to be shown to the user, the promise never gets fulfilled.

_requestLocationPermission(){
return new Promise(async() => {
const permissions = await PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.ACCESS_FINE_LOCATION);
if (permissions === PermissionsAndroid.RESULTS.GRANTED){
alert('access true');
}
else{
alert('access false');
}
});
}

Happening on RN 0.58.3.

Hello there 👋 this issue has been reported for an old version of React Native. Ideally we'd like everyone to be using 0.59 (see the awesome changes it brought) but we know updating can be a pain. We are going to close this issue because it's from a version before 0.57, which is really old.
But please, if it's actually still an issue with 0.59 please comment below and we can reopen it 😊

still does not resolves using 0.59 (the same behavior as in 0.57)

Any way to provide rationale to .multipleRequest()?. I want to give the user more insight into why I need the permission for respective request. In short, Customized title and message with multiple requests.

I'm using:
"react": "16.8.3",
"react-native": "0.59.9",

Relevant snippet:
  const askCameraPermission = async () => {
    try {
      const granted = await PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.CAMERA);
      console.log(granted)
    } catch {
      (e) => console.log(e)
    };
  };

App info's permissions after -> before run method
pending -> granted BUT promise is not resolved, console.log doesn't show. 👎
granted -> don't ask for permission because is already granted AND promise is resolved, console.log show 'granted' 👍

Issue still persists in RN .60

I have upgraded my project from 0.57 to 0.61 . But the issue still exists. However if I try to create a new project with react-native 0.61 this issue is not there. I am stuck here. Please some one help me

Maybe you Override onRequestPermissionsResult in MainActivity extends ReactActivity but forget to call super.onRequestPermissionsResult.


There are some bugs in ICaffeParser

I used "ICaffeParser" to parse caffemodel and prototxt as follows:
INetworkDefinition* network = builder->createNetworkV2(1U << static_cast<uint32_t>(NetworkDefinitionCreationFlag::kEXPLICIT_BATCH));
const IBlobNameToTensor* blobNameToTensor = parser->parse(deployFile,modelFile, *network, nvinfer1::DataType::kFLOAT);
There is a "Permute" layer in prototxt. Like that:
layer {
name: "permute"
type: "Permute"
bottom: "conv1"
top: "conv1_permute"
permute_param{
order: 0
order: 3
order: 2
order: 1
}
}
If the size of input layer is fixed, all is ok.
However, if the size is dynamic as follows:
input: "data"
input_shape {
dim: 1
dim: 1
dim: 32
dim: -1
}
errors occured:
caffe/caffeParser.cpp:1599: nvinfer1::ILayer* parsePermute(nvinfer1::INetworkDefinition&, const ditcaffe::LayerParameter&, CaffeWeightFactory&, BlobNameToTensor&): Assertion `volume(topDims) == volume(bottomDims)' failed.
help me!!

ICaffeParser is part of TensorRT, not TRTIS. You should ask your question in the linked forum, which is monitored by the TensorRT team: https://devtalk.nvidia.com/default/board/304/tensorrt/

Duplicate: https://github.com/NVIDIA/TensorRT/issues/211


Support for mdx v3?

The main readme says this uses mdx v2, but v3 has been released. Are there plans to support that?

The 2 big items (there's not much more)

support for await
ES2024

https://mdxjs.com/blog/v3/

Actually, is this just an outdated readme?
https://github.com/kentcdodds/mdx-bundler/commit/da24af7aaa186244a7a9993258a71338e8c420de

It is, just tested that { await Promise.resolve(42)} works!

I would update the README first


Hotfix altgraph 0.11.0+ to use setuptools

Needed as they use pkg_resources.
xref: https://github.com/conda-forge/altgraph-feedstock/pull/9
cc @conda-forge/altgraph

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Relevant patch details:
noarch::altgraph-0.14-py_0.tar.bz2
+    "setuptools",
noarch::altgraph-0.15-py_0.tar.bz2
+    "setuptools",
noarch::altgraph-0.16.1-py_0.tar.bz2
+    "setuptools",
noarch::altgraph-0.17-pyhd8ed1ab_0.tar.bz2
-    "python >=3.6"
+    "python >=3.6",
+    "setuptools"
noarch::altgraph-0.17.1-pyhd8ed1ab_0.tar.bz2
-    "python >=3.6"
+    "python >=3.6",
+    "setuptools"
noarch::altgraph-0.17.2-pyhd8ed1ab_0.tar.bz2
-    "python >=3.6"
+    "python >=3.6",
+    "setuptools"

@conda-forge/core, this is ready for review! 😄

Thanks Chris! 🙏


hashicorp/aws 5.0.0 Filter block not expected here.

Describe the Bug
When using the aws provider >=5.0.0, we get a filter block not expected here.
See https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-5-upgrade#data-sourceaws_identitystore_group
Expected Behavior
Plan and applies to work on latest version of aws provider
Steps to Reproduce
terraform init -upgrade a repo using the module
terraform plan
Screenshots
No response
Environment
No response
Additional Context
No response

Closing as fixed by #44


fix: Skipping wizard steps

Let's switch all occurrences of wire:loading.attr.delay="disabled"

Yeah, its not a visual change like wire:loading.class so we dont need the delay

@danharrin, done!


Integration setup_resilience_path fails when deleting a file and getting a "no such file" error

Traceback (most recent call last):
  File "/home/travis/build/WallarooLabs/wallaroo/testing/correctness/tests/restart_without_resilience/restart_without_resilience.py", line 43, in test_restart_machida
    _test_restart(command)
  File "/home/travis/build/WallarooLabs/wallaroo/testing/correctness/tests/restart_without_resilience/restart_without_resilience.py", line 59, in _test_restart
    setup_resilience_path(res_dir)
  File "/home/travis/build/WallarooLabs/wallaroo/testing/tools/integration/integration.py", line 759, in setup_resilience_path
    os.remove(os.path.join(res_dir, f))
OSError: [Errno 2] No such file or directory: '/tmp/res-data/sequence_window-worker1.workers'
===================== 1 failed, 1 passed in 11.38 seconds ======================
make: *** [restart_without_resilience_tests] Error 1

Possible causes for this are a race between the previous test's workers doing cleanup and the current test's setup function firing...
I think the best way to resolve this is to ensure the previous test doesn't complete until all workers successfully exit with a 0 status.

Leaving this for the after the new year

Ouch, the same/very similar error just happened to @jtfmumm while working on #2027, see https://circleci.com/gh/WallarooLabs/wallaroo/890.
Linking ./weighted_test
cd /root/project/testing/correctness/tests/autoscale_grow/ && \
python2 -m pytest --color=yes --tb=native --verbose autoscale_grow.py
============================= test session starts ==============================
platform linux2 -- Python 2.7.12, pytest-3.2.2, py-1.5.2, pluggy-0.4.0 -- /usr/bin/python2
cachedir: .cache
rootdir: /root/project/testing/correctness/tests/autoscale_grow, inifile:
collected 4 items

autoscale_grow.py::test_autoscale_grow_pony_by_1 PASSED
autoscale_grow.py::test_autoscale_grow_machida_by_1 PASSED
autoscale_grow.py::test_autoscale_grow_pony_by_4 PASSED
autoscale_grow.py::test_autoscale_grow_machida_by_4 FAILED

=================================== FAILURES ===================================
_______________________ test_autoscale_grow_machida_by_4 _______________________
Traceback (most recent call last):
  File "/root/project/testing/correctness/tests/autoscale_grow/autoscale_grow.py", line 83, in test_autoscale_grow_machida_by_4
    _test_autoscale_grow(command, worker_count=5)
  File "/root/project/testing/correctness/tests/autoscale_grow/autoscale_grow.py", line 105, in _test_autoscale_grow
    setup_resilience_path(res_dir)
  File "/root/project/testing/tools/integration/integration.py", line 762, in setup_resilience_path
    os.remove(os.path.join(res_dir, f))
OSError: [Errno 2] No such file or directory: '/tmp/res-data/alphabet-contest-worker4.tcp-data'
===================== 1 failed, 3 passed in 37.79 seconds ======================
testing/correctness/tests/autoscale_grow/Makefile:51: recipe for target 'autoscale_grow_tests' failed
make: *** [autoscale_grow_tests] Error 1
Exited with code 2


Optimize combined distinct queries

Optimize distinct queries with single value per rowgroup:
Gathering distinct values of (non optional) dictionary encoded columns
is a constant operation per rowgroup when the dictionary only has a
single value. Additionally distinct projections using binary expressions
such as timestamp > 0 can be determined without loading the row if the
column index has sufficient data. For example when the index notes that
all timestamps are between 5 and 8, then all values for timestamp > 0
are true, and therefore true for any distinct values in the rowgroup.

pqarrow: Optimize distinct where all but one column are single value:
When all but one column have only a single value, then the whole
rowgroup does not have to be scanned as the possible combination of
distinct values are the non-single column values combined with all
single value columns.

With these two optimizations profile type queries in Parca (which make heavy use of distinct queries) are about 94% better:
$ benchstat old.txt new.txt
name              old time/op  new time/op  delta
_ProfileTypes-10   760ms ± 7%    49ms ± 8%  -93.60%  (p=0.008 n=5+5)

This was a pretty extreme benchmark with lots of data. A typical query is now <10ms, and Parca servers only ingesting a single type of profile (eg. only using the Parca Agent as it only ingests CPU profiles) even faster.


transformClassesWithParanoidFor task is still being run after disabling paranoid

is there a way to stop this task from executing? I have intention to not use paranoid in debug build as this task is taking up a huge chunk of our compilation time.

Duplicate of this:
https://github.com/MichaelRocks/paranoid/issues/69
?
And there is a library now that uses the same code and should solve it, and it works well with normal modules but I failed to use it for AAR library module and the developers there locked the conversation too soon without letting me verify if what they provided helps:
https://github.com/LSPosed/LSParanoid/issues/8


[Enhancement]: Add a munge sanity check

We should have a method to check if munge is working correctly, since this functionality is used by
all Slurm charms, and we would reduce some code duplication this way.

This is something that we could add to mungectl.
Similar to terraform/tofu, we could have a mungectl validate command that emits a 0 exit code if everything is good and then a non-zero exit code if something is wrong with munge such as if NTP is out of sync or there is a key mismatch.


fix container resizing

ReactSVGPanZoom.componentWillReceiveProps loses viewerWidth and viewerHeight updates, so container's resizing is not handled correctly.

Thanks for your PR. I've just merged it and released a new version (v2.13).
Now the resize is correctly handled https://chrvadala.github.io/react-svg-pan-zoom/?selectedKind=React SVG Pan Zoom&selectedStory=Runtime Resize&full=0&down=1&left=1&panelRight=1&downPanel=storybooks%2Fstorybook-addon-knobs


[feature]: Add a hamburger button for applications under test cases

Is there an existing feature request for this?

[X] I have searched the existing issues

Summary
When we navigate to the test cases section at keploy server, the applications tested are listed on the left (here-superhero-api). We can add a hamburger button to hide and show them as per user's convenience like the one done for Test cases and Test runs.

Why should this be worked on?
This feature will make the UI more responsive

Would like to work on this. Can you assign me to this issue ?

Hey. Is there an update on this PR ?

ping @SanskritiHarmukh

@titanventura my apologies I couldn't look into this. I will review and merge the PR this week itself. Thanks for reminding.

ping @nehagup


Develop Unstable GitHub Action CI/CD to I&T Staging venue

💡 Description

Merge to develop branch -> deploy to I&T staging venue

Based on this answer, we'll use the Roundup Action for the CI part of things, and a future action for CD.
Roundup Action supports Maven- and Python-based repositories for unit testing, documentation generation, and publication of artifacts to Sonatype (for Maven) and PyPI (for Python). It's object-oriented, meaning that each step it executes is generic and doesn't know what the underlying repository is, be that Maven or Python. So it provides a framework for plugging in additional kinds of repositories.
Enter Node.js.
Since I'm not a Node.js developer, though, I'll need some help, so I'm roping in @anilnatha to provide some insight.
Roundup Action "Steps"
The Roundup Action executes a series of steps which are configurable and depend on the "assembly" being run. An assembly defines the steps and the order in which they're run. There's the NoOpAssembly which has zero steps. There's the EnvironmentalAssembly which takes its steps from an environment variable. And there's the PDSAssembly which is what we use and has the following steps, in order:

preparation (StepName.preparation)
unit test (StepName.unitTest)
integration test (StepName.integrationTest)
docs (StepName.docs)
version bump (StepName.versionBump)
build (StepName.build)
artifact publication (StepName.artifactPublication)
requirements (StepName.requirements)
changelog (StepName.changeLog)
GitHub release (StepName.githubRelease)
doc publication (StepName.docPublication)
version commit (StepName.versionCommit)
cleanup (StepName.cleanup)

An assembly can be either "stable" or "unstable". The StablePDSAssembly is stable; UnstablePDSSAssembly is unstable. You can see in your repository's stable-cicd.yaml and unstable-cicd.yaml how this flag is set. A stable assembly is for an official, stable release of the software and releases an official artifact to the correct artifactory, publishes documentation, updates the changelog and issues, and gets the next development version ready for work. An unstable release creates a -SNAPSHOT release (for Maven) or a test.pypi.org release (for Python) and deletes prior unstable releases.
An assembly is associated with a Context that maps the step enumerated StepNames to the Step classes that implement each step and also provide environment variables and command-line arguments.
The Step Classes
Class Step is abstract and expect concrete subclasses to implement the execute method to do the work when it's run. For example, the Maven class _UnitTestStep's execute method does mvn test while the Python class _UnitTestStep's execute tries to run tox -e py39 but if that fails falls back to python setup.py test.
As another example, the Maven class _BuildStep does mvn compile and the Python class _BuildStep does python setup.py bdist_wheel.
Some steps are common between Maven and Python. The ChangeLogStep is one such step. It uses the GitHub Changelog Generator to automatically create our CHANGELOG.md file. The RequirementsStep uses our own lasso-requirements to create our requirements report. And so on.
Node.js Classes
Our task therefore is to define for Node.js repositories what it will mean to do the following.
Preparation
For Maven repositories, the preparation step involves creating the settings.xml file used by Maven and also generating the GPG key in order to sign artifacts. For Python, this creates a Python venv and installs the package being rounded up into it.
❓ Does NPM use signed artifacts? What preparation steps are needed for Node.js repositories? Is it npm install . or something more involved?
Unit Test
As mentioned above, for Maven this is mvn test and for Python it's tox -e py39 etc.
❓ Is this just npm test?
Integration Test
Neither of the current Maven and Python Roundups do anything for the integration test step so we'll skip it for Node.js as well.
Documentation Generation
In Maven repositories, we automatically generate documentation with mvn package site site:stage and with Python we do sphinx-build -a -b html docs/source docs/build.
❓ Does Node.js have automatically-generated documentation and if so, how?
Version Bumping
At this point in the roundup, we're ready to increment the version number of the project. This only happens for stable builds, so unstable builds make this a no-op.
In Maven repositories, we use git describe --tags --abbrev=0 --match release/* in order to find out if we have a release/X.Y.Z kind of push. We then add this version label to an open bugs that remain in the project. Maven roundups then run mvn -DgenerateBackupPoms=false -DnewVersion=X.Y.Z versions:set which updates the pom.xml with the new version number.
In Python repositories, we use the same git command to get the release/X.Y.Z tag and add the version label to open bugs. We then find the VERSION.txt file and set its contents to X.Y.Z.
❓ Does npm provide a command to update the version key in package.json? If not, we'll update package.json directly.
Build Step
As mentioned above, Maven does mvn compile and Python does python setup.py bdist_wheel. These generate the corresponding artifacts target/whatever-X.Y.Z.jar (among others) and dist/whatever-X.Y.Z.whl.
❓ What's the equivalent for Node.js?
Artifact Publication
For Maven this means running mvn --activate-profiles release clean package site deploy to create the source, documentation, and binary jar files to Sonatype for a stable release, and mvn clean site deploy for an unstable release. For Python, it's twine upload --repository-url URL with URL = https://upload.pypi.org/legacy/ for a stable release or https://test.pypi.org/legacy/ for an unstable release.
❓ What will this mean for Node.js? Are there separate artifactories for Node.js for stable and unstable releases is there just one and there are somehow marked differently?
GitHub Release
In addition to publishing artifacts at the language-specific repository (Sonatype for Maven, PyPI for Python, https://www.npmjs.com/ for Node.js), we also push artifacts to the release page on GitHub.
In Maven repositories, we do the following:

Delete all release tags that have SNAPSHOT in their name
For unstable releases, use lasso-releasers to publish a new SNAPSHOT release tag, then clean up any leftover release/* tags
For stable releases, use git tag --annotate to tag the release as X.Y.Z (from release/X.Y.Z) and then use lasso-releasers to publish a new official release tag

In Python repositories, it's similar:

Delete all release tags with dev in their name
For unstable releases, use lass-releasers to publish a new dev release, then clean up any leftover release/* tags
For stable releases, use git tag --annotate to tag the release as X.Y.Z (from release/X.Y.Z) and then use lasso-releasers to publish a new official release tag

❓ For Node.js, we will have to update lasso-releasers with its own support for publishing artifacts to GitHub. Perhaps @anilnatha can work with @tloubrieu-jpl on this?
Documentation Publication
Documentation publication is a generic step but Maven and Python subclass this to provide the location of the documentation directory, since the two kinds of repositories end up depositing their files in different locations.
❓ As for "Documentation Generation" above, does Node.js have automatically-generated documentation?
Version Commit
The penultimate step in the PDS assembly is to commit any changed version files. This only happens in stable assemblies, so for unstable roundups, this is a no-op.
In Maven, this just means committing the pom.xml file (and any pom.xml files in subdirectories for multi-module repositories). In Python, this is just committing the VERSION.txt file.
❓ In Node.js, is this as simple as committing the package.json?
Cleanup
Cleanup is the final step in the PDS assembly and only happens for stable roundups.
In Maven-land, this means finding the newly-committed version in pom.xml and adding one to the minor version number and resetting the micro number to zero, so if we just released stable version 1.2.3, the next version is 1.3.0. This new version is written to the pom.xml (and any pom.xml files in subdirectories for multi-module repositories) along with -SNAPSHOT so the next cycle of development can begin. These pom.xml files are then committed.
In Python-land, we do the same thing but for the one VERSION.txt file.
❓ Can we just update version in package.json as well and then commit it?
Final Questions
What's the difference between npm, npx, and yarn—and why are there three?

@nutjob4life ### I'll include my answers inline below:

Based on this answer, we'll use the Roundup Action for the CI part of things, and a future action for CD.
Roundup Action supports Maven- and Python-based repositories for unit testing, documentation generation, and publication of artifacts to Sonatype (for Maven) and PyPI (for Python). It's object-oriented, meaning that each step it executes is generic and doesn't know what the underlying repository is, be that Maven or Python. So it provides a framework for plugging in additional kinds of repositories.
Enter Node.js.
Since I'm not a Node.js developer, though, I'll need some help, so I'm roping in @anilnatha to provide some insight.
Roundup Action "Steps"
The Roundup Action executes a series of steps which are configurable and depend on the "assembly" being run. An assembly defines the steps and the order in which they're run. There's the NoOpAssembly which has zero steps. There's the EnvironmentalAssembly which takes its steps from an environment variable. And there's the PDSAssembly which is what we use and has the following steps, in order:

preparation (StepName.preparation)
unit test (StepName.unitTest)
integration test (StepName.integrationTest)
docs (StepName.docs)
version bump (StepName.versionBump)
build (StepName.build)
artifact publication (StepName.artifactPublication)
requirements (StepName.requirements)
changelog (StepName.changeLog)
GitHub release (StepName.githubRelease)
doc publication (StepName.docPublication)
version commit (StepName.versionCommit)
cleanup (StepName.cleanup)

An assembly can be either "stable" or "unstable". The StablePDSAssembly is stable; UnstablePDSSAssembly is unstable. You can see in your repository's stable-cicd.yaml and unstable-cicd.yaml how this flag is set. A stable assembly is for an official, stable release of the software and releases an official artifact to the correct artifactory, publishes documentation, updates the changelog and issues, and gets the next development version ready for work. An unstable release creates a -SNAPSHOT release (for Maven) or a test.pypi.org release (for Python) and deletes prior unstable releases.
An assembly is associated with a Context that maps the step enumerated StepNames to the Step classes that implement each step and also provide environment variables and command-line arguments.
The Step Classes
Class Step is abstract and expect concrete subclasses to implement the execute method to do the work when it's run. For example, the Maven class _UnitTestStep's execute method does mvn test while the Python class _UnitTestStep's execute tries to run tox -e py39 but if that fails falls back to python setup.py test.
As another example, the Maven class _BuildStep does mvn compile and the Python class _BuildStep does python setup.py bdist_wheel.
Some steps are common between Maven and Python. The ChangeLogStep is one such step. It uses the GitHub Changelog Generator to automatically create our CHANGELOG.md file. The RequirementsStep uses our own lasso-requirements to create our requirements report. And so on.
Node.js Classes
Our task therefore is to define for Node.js repositories what it will mean to do the following.
Preparation
For Maven repositories, the preparation step involves creating the settings.xml file used by Maven and also generating the GPG key in order to sign artifacts. For Python, this creates a Python venv and installs the package being rounded up into it.
❓ Does NPM use signed artifacts? What preparation steps are needed for Node.js repositories? Is it npm install . or something more involved?

I’m not completely familiar with Maven repositories and artifacts but for node.js usually just running npm install is enough. Of course it depends on the project. Npm install installs all the dependencies and creates the npm-package.lock file which contains the exact versioned dependency tree of what was installed.
You can also add your own scripts to the package.json if you need to do something else.
As for integrity checks, since they’re coming from the same source npmjs.com we’re not so worried about MIM attacks as with JARs downloaded from different mirrors. Although npm might do some key verification under the hood.

Unit Test
As mentioned above, for Maven this is mvn test and for Python it's tox -e py39 etc.
❓ Is this just npm test?

There are various testing frameworks for different projects in npm. They are usually hooked into “npm test” although that command might change depending on what is included inside the package.json scripts object.
One popular example for testing react projects is Jest https://jestjs.io/docs/getting-started The script is added in the package.json file
{
  "scripts": {
    "test": "jest"
  }
}

So running npm test would run “jest”

Integration Test
Neither of the current Maven and Python Roundups do anything for the integration test step so we'll skip it for Node.js as well.
Documentation Generation
In Maven repositories, we automatically generate documentation with mvn package site site:stage and with Python we do sphinx-build -a -b html docs/source docs/build.
❓ Does Node.js have automatically-generated documentation and if so, how?

In the same way as for testing there are various documentation creation frameworks in npm. They can have various ways to run the documentation build. Usually if it exists it would be in the scripts section the package.json file.
One popular example for react is jsdoc https://jsdoc.app The script is added in the package.json file
"scripts": {
  ...
    "docs": "jsdoc -c jsdoc.conf.json"
  ...
}

So to run it would be the command npm docs although you can always change the word “docs” to whatever you wish.

Version Bumping
At this point in the roundup, we're ready to increment the version number of the project. This only happens for stable builds, so unstable builds make this a no-op.
In Maven repositories, we use git describe --tags --abbrev=0 --match release/* in order to find out if we have a release/X.Y.Z kind of push. We then add this version label to an open bugs that remain in the project. Maven roundups then run mvn -DgenerateBackupPoms=false -DnewVersion=X.Y.Z versions:set which updates the pom.xml with the new version number.
In Python repositories, we use the same git command to get the release/X.Y.Z tag and add the version label to open bugs. We then find the VERSION.txt file and set its contents to X.Y.Z.
❓ Does npm provide a command to update the version key in package.json? If not, we'll update package.json directly.

There are some libraries that can handle automatically updating the version on the package.json but I haven’t used them so I can’t vouch for their reliability. I usually set it manually.  Npm packages use semantic versioning spec otherwise known as “semver” https://docs.npmjs.com/about-semantic-versioning

Build Step
As mentioned above, Maven does mvn compile and Python does python setup.py bdist_wheel. These generate the corresponding artifacts target/whatever-X.Y.Z.jar (among others) and dist/whatever-X.Y.Z.whl.
❓ What's the equivalent for Node.js?

This probably correlates to npm build It will spit out the distribution files that are to be uploaded to the server as you would do with jars.

Artifact Publication
For Maven this means running mvn --activate-profiles release clean package site deploy to create the source, documentation, and binary jar files to Sonatype for a stable release, and mvn clean site deploy for an unstable release. For Python, it's twine upload --repository-url URL with URL = https://upload.pypi.org/legacy/ for a stable release or https://test.pypi.org/legacy/ for an unstable release.
❓ What will this mean for Node.js? Are there separate artifactories for Node.js for stable and unstable releases is there just one and there are somehow marked differently?

On the npm js website you can deploy various versions with different tags with only the official one being automatically downloaded with npm install
For example if we want unstable tag to differentiate from stable versions then when updating the version in the /package.json file you can use the X.X.X semver syntax to set a stable version or X.X.X-unstable.X semver syntax for an unstable version.
Use npm publish to publish a stable version or use npm publish --tag unstable to publish an unstable version.
If you want to test an unstable version make sure to install the unstable version instead of the latest version. For example use npm install @nasapds/<unstable_project>@unstable for the latest unstable version or npm install<EMAIL_ADDRESS>for a specific version.
An example is at https://www.npmjs.com/package/@nasapds/pds-wds-react?activeTab=versions we have normal stable versions and beta versions. All in the version history but with different tags.

GitHub Release
In addition to publishing artifacts at the language-specific repository (Sonatype for Maven, PyPI for Python, https://www.npmjs.com/ for Node.js), we also push artifacts to the release page on GitHub.
In Maven repositories, we do the following:

Delete all release tags that have SNAPSHOT in their name
For unstable releases, use lasso-releasers to publish a new SNAPSHOT release tag, then clean up any leftover release/* tags
For stable releases, use git tag --annotate to tag the release as X.Y.Z (from release/X.Y.Z) and then use lasso-releasers to publish a new official release tag

In Python repositories, it's similar:

Delete all release tags with dev in their name
For unstable releases, use lass-releasers to publish a new dev release, then clean up any leftover release/* tags
For stable releases, use git tag --annotate to tag the release as X.Y.Z (from release/X.Y.Z) and then use lasso-releasers to publish a new official release tag

❓ For Node.js, we will have to update lasso-releasers with its own support for publishing artifacts to GitHub. Perhaps @anilnatha can work with @tloubrieu-jpl on this?

I’m not sure about this one. I’ll leave it to @tloubrieu-jpl  and @anilnatha

Documentation Publication
Documentation publication is a generic step but Maven and Python subclass this to provide the location of the documentation directory, since the two kinds of repositories end up depositing their files in different locations.
❓ As for "Documentation Generation" above, does Node.js have automatically-generated documentation?

As with the third question about documentation the generated docs will be available in a directory in the project. This can then be put anywhere you wish. The location of where it gets placed though is up to the generator and if it has a way to set a custom location.

Version Commit
The penultimate step in the PDS assembly is to commit any changed version files. This only happens in stable assemblies, so for unstable roundups, this is a no-op.
In Maven, this just means committing the pom.xml file (and any pom.xml files in subdirectories for multi-module repositories). In Python, this is just committing the VERSION.txt file.
❓ In Node.js, is this as simple as committing the package.json?

I'm a bit confused on this one. Do you mean how does nodejs know about the commits related to a version change?

Cleanup
Cleanup is the final step in the PDS assembly and only happens for stable roundups.
In Maven-land, this means finding the newly-committed version in pom.xml and adding one to the minor version number and resetting the micro number to zero, so if we just released stable version 1.2.3, the next version is 1.3.0. This new version is written to the pom.xml (and any pom.xml files in subdirectories for multi-module repositories) along with -SNAPSHOT so the next cycle of development can begin. These pom.xml files are then committed.
In Python-land, we do the same thing but for the one VERSION.txt file.
❓ Can we just update version in package.json as well and then commit it?

Yes updating the “version” value in the package.json file should be enough to let npmjs know this is a different version. Remember to use semver! https://docs.npmjs.com/about-semantic-versioning

Final Questions
What's the difference between npm, npx, and yarn—and why are there three?

Npm is is a package manager that handles downloading and managing projects from the online repository npmjs.com. Its installed along with with node.js from http://nodejs.org
Npx does the same as npm but instead of downloading the project it can run it without saving it to your disk. It can even run projects straight off GitHub without having to install. It is also installed with node.js from http://nodejs.org
Yarn is another package manager that does the same thing as npm such as handling downloads and managing projects from the online repository npmjs.com. It is meant to be an improvement over npm but is not as popular as npm. It has to be installed separately from node.js and npm
npm and npx are included in the nodejs download and they fulfill different roles. Yarn is an alternative to npm. nodejs isn't limited to these 3 CLI's but these are three common ones indeed.

As mentioned above, Maven does mvn compile and Python does python setup.py bdist_wheel. These generate the corresponding artifacts target/whatever-X.Y.Z.jar (among others) and dist/whatever-X.Y.Z.whl.
❓ What's the equivalent for Node.js?

This probably correlates to npm build It will spit out the distribution files that are to be uploaded to the server as you would do with jars.

Thanks @eddiesarevalo! One quick question: does npm build rely on some earlier invocation or dependency? I get Unknown command: "build":
$ cat package.json
{
  "name": "mynodetest",
  "version": "0.0.0",
  "description": "Just a test for node.js",
  "main": "index.js",
  "scripts": {
    "test": "jest",
    "docs": "jsdoc -c jsdoc.conf.json"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/NASA-PDS/mynodetest.git"
  },
  "keywords": [
    "testing"
  ],
  "author": "nutjob4life",
  "license": "Apache-2.0",
  "bugs": {
    "url": "https://github.com/NASA-PDS/mynodetest/issues"
  },
  "homepage": "https://github.com/NASA-PDS/mynodetest",
  "dependencies": {},
  "devDependencies": {
    "jest": "29.7",
    "jsdoc": "^4.0.2"
  }
}
$ cat index.js
console.log('hello, 🌎');
$ node index.js
hello, 🌎
$ npm build
Unknown command: "build"

To see a list of supported npm commands, run:
  npm help

Node.js support is really what this ticket is all about now!

@nutjob4life requested help from @anilnatha and @eddiesarevalo .

Still blocked.

@nutjob4life (fyi) I'm trying to ascertain what we need to do/try to get this working, as soon as I have something, I'll report back.

@anilnatha I don't think you need to do anything. You already figured it out!
@tloubrieu-jpl this is no longer blocked.

Ahhh, I thought there was something else I needed to look into, was playing catch up with the messages in this ticket. @nutjob4life

Also, @nutjob4life , as part of our deployments, we should be running npm clean-install in lieu of npm install if we aren't already.

This is done, @nutjob4life will create a PR after he develops the stable part of roundup for nodejs.

I believe this pull request will close the following issues

#63
#64
#66
#69

Re-opening this ticket. I think we have the unstable build performing CI, but we do not have CD to a Dev venue in the cloud.


FSLeyes crashing

Describe the bug
When I first installed ADS a few months ago, I remember trying out fsleyes and installing the plugin. Everything worked fine from what I recall. I volunteered to write some doc for the plugin (#473) but now I can't open fsleyes anymore... I get the following error:
Traceback (most recent call last):
  File "/home/herman/.conda/envs/ads_venv/lib/python3.7/site-packages/fsl/utils/idle.py", line 576, in __idleLoop
    task.task(*task.args, **task.kwargs)
  File "/home/herman/.conda/envs/ads_venv/lib/python3.7/site-packages/fsleyes/gl/__init__.py", line 612, in create
    self.__createWXGLContext()
  File "/home/herman/.conda/envs/ads_venv/lib/python3.7/site-packages/fsleyes/gl/__init__.py", line 746, in __createWXGLContext
    self.__context = wxgl.GLContext(self.__canvas)
wx._core.wxAssertionError: C++ assertion ""tempContext"" failed at /home/conda/feedstock_root/build_artifacts/wxpython_1616628589829/work/ext/wxWidgets/src/unix/glx11.cpp(498) in wxGLContext(): glXCreateContext failed

To Reproduce
$ conda activate ads_venv
$ fsleyes

Platform (please complete the following information):

OS: Manjaro 21.0.7 Ornara (kernel: x86_64 Linux 5.10.35-1-rt39-MANJARO)
AxonDeepSeg version number: 3.2.0 (master)

I am aware that there are issues installing fsleyes on Linux. I feel like I'm in a deadend right now because there doesn't seem to be a pre-release wxPython build for my distro and getting it up and running looks like a potential nightmare. I'll update this issue if I find anything useful.

Could you try the following:

Create a new conda environment and activate it
Download wxPython, perhaps not the most recent one. We could try this one: conda install -c anaconda wxpython=4.0.1
Try to download FSLeyes conda install -c conda-forge fsleyes=0.33.1

If my last suggestion doesn't work, here's one last thing we could try:

Create a new conda environment and activate it
Install the most recent version of FSLeyes with this command: conda install -c conda-forge fsleyes

If that doesn't work, we might have to open an issue in the FSLeyes github project (https://github.com/pauldmccarthy/fsleyes).

Unfortunately I tried your suggestions but nothing has changed. If I can't get it to work tomorrow, I'll open an issue in the FSLeyes github project.

Do we have any update on this?

Sorry @Stoyan-I-A I haven't had the chance to investigate this further in the last weeks and it slipped my mind. Just opened an issue here.

Here's a quick update:
For the past few days, the fsleyes maintainer has been trying to figure out what is causing my problem. I admire his efforts, but I am forced to ask the following question: is fsleyes really the GUI option we want to maintain? I know there were efforts to find a more stable software for ADS integration.
I was told fsleyes is still somewhat widely used, so maybe it is still a good approach.
In defense of the fsleyes program, I admit my OS is definitely whimsical, making it hard to install these kinds of open-source projects and I'm considering dual booting another distro.

is fsleyes really the GUI option we want to maintain?

Ideally, no. I would prefer something with more compatibility across operating systems.
FSLeyes was used because it was fairly simple to integrate ADS on it as a plugin.

is fsleyes really the GUI option we want to maintain? I know there were efforts to find a more stable software for ADS integration.

nope! 😊   see: #404

I was told fsleyes is still somewhat widely used, so maybe it is still a good approach.

it depends on the community. It is widely used by the MRI community and it is absolutely not used by the microscopy community. As @Stoyan-I-A said in https://github.com/neuropoly/axondeepseg/issues/544#issuecomment-889929672 we used FSLeyes because we know it, but it is not a good enough reason to keep it if it is not a good long term solution.

Stale - no longer supporting FSLeyes


hack: Remove the unused test helper scripts after merging the feature-e2e-rewrite branch.

Description:
This would remove the hack/integration.sh and hack/e2e-test-runner.sh scripts which were removed in the feature-e2e-rewrite branch, but added back when merging the two branches together.
We should continue to monitor whether or not there's any other leakage, but I took a quick look at the diffs, and that scripts appear to be the only rebase mistake thus far:
tflannag@localhost operator-metering [fix-merging-feature-e2e-rewrite]
└─ $ ▶ git diff upstream/feature-e2e-rewrite --stat !(vendor|Documentation|charts|images)
 Dockerfile.metering-ansible-operator                                           |  2 +-
 Dockerfile.metering-ansible-operator.rhel                                      |  2 +-
 Gopkg.lock                                                                     | 28 +++++++++++++++-------------
 hack/get-metering-package-images.sh                                            | 17 ++++++++++++++++-
 hack/mirror-ose-images-into-cluster.sh                                         | 52 +++++++++++++++++++++++++++++++++++++++++++++-------
 manifests/deploy/ocp-testing/metering-ansible-operator/hive.crd.yaml           |  4 +++-
 manifests/deploy/ocp-testing/metering-ansible-operator/meteringconfig.crd.yaml | 25 +++++++++++++++++++++----
 manifests/deploy/ocp-testing/olm/bundle/4.3/hive.crd.yaml                      |  4 +++-
 manifests/deploy/ocp-testing/olm/bundle/4.3/meteringconfig.crd.yaml            | 25 +++++++++++++++++++++----
 manifests/deploy/openshift/metering-ansible-operator/hive.crd.yaml             |  4 +++-
 manifests/deploy/openshift/metering-ansible-operator/meteringconfig.crd.yaml   | 25 +++++++++++++++++++++----
 manifests/deploy/openshift/olm/bundle/4.3/hive.crd.yaml                        |  4 +++-
 manifests/deploy/openshift/olm/bundle/4.3/meteringconfig.crd.yaml              | 25 +++++++++++++++++++++----
 manifests/deploy/openshift/telemeter/list.yaml                                 | 25 ++++++++++++++++++++++---
 manifests/deploy/upstream/metering-ansible-operator/hive.crd.yaml              |  4 +++-
 manifests/deploy/upstream/metering-ansible-operator/meteringconfig.crd.yaml    | 25 +++++++++++++++++++++----
 manifests/deploy/upstream/olm/bundle/4.3/hive.crd.yaml                         |  4 +++-
 manifests/deploy/upstream/olm/bundle/4.3/meteringconfig.crd.yaml               | 25 +++++++++++++++++++++----
 pkg/aws/client.go                                                              | 22 +++++++++++++++++++---
 pkg/aws/manifest.go                                                            | 29 +++++++++++++++++------------
 pkg/operator/aws_usage_hive.go                                                 | 13 ++++++++-----
 pkg/operator/datasources.go                                                    |  2 +-
 pkg/operator/hivetables.go                                                     |  5 +++--
 pkg/operator/reporting/db.go                                                   | 16 ++++++++--------
 pkg/presto/util.go                                                             |  7 ++++++-
 25 files changed, 306 insertions(+), 88 deletions(-)
tflannag@localhost operator-metering [fix-merging-feature-e2e-rewrite]
└─ $ ▶ git diff upstream/feature-e2e-rewrite --stat !(vendor|Documentation|charts|images)

We should update the makefile and our config in the release repo too.
https://github.com/openshift/release/blob/master/ci-operator/config/operator-framework/operator-metering/operator-framework-operator-metering-master.yaml#L66-L67

@chancez agreed, and then we can remove the make integration target from our Makefile.

/lgtm
/approve


forever + JSON Configuration Files + set command option

Hi,
How do I make to set command option in forever.json? I need use -c coffee.
I tried:
    "command": "coffee"
    "c: "coffee"
    "COMMAND": "coffee"
    "cmd": "coffee"

And nothing work. This option can be set in json config?
thanks!

I met the same problem, have you resolved it?

when I use forever.json to run app, the command option not work.
{
    "uid": "app-uid",
    "append": true,
    "watch": true,
    "command": "/usr/local/n/versions/node/7.10.0/bin/node",
    "script": "index.js"
}

Hi @Dengyy ,
Not work with coffee.. I had to compile js code to work.

sad news /(ㄒoㄒ)/~~

Any changes?

any update???


Add Lume Theme Shiraha

Thanks for this, Beautiful work!
Just one thing: The image must be png. Lume converts it automatically to webp.

OK, it has been updated.

Thank you!


Prepare release v2.0.0

This PR should prepare the project for release v2.0.0.
This includes some deprecations and changes to some flags.
Also, I started moving the different parts of documentation from the readme to separate files, so we can easily enhance them in the future.

Closing this, because we decided to take a different approach for the next versions


fix to skip node not in graph.

fix to skip node not in graph because some network cannot be hybridized with some var unused.
Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

Could you add some test case for it?

@icemelon9 what kind of tests, please?

I am going to merge this for now, given it is a change to the nnvm code. However, based on my current impression, I am not really sure if such relaxation should be done, given that node2index is supposed to only contain nodes in the graph, @chinakook would be great if you can comment a bit.

@tqchen  As I'v just tested, It's a op named _FusedOp that cannot be CHECK success.

i see, perhaps you also want to confirm with the mxnet devs to make sure it is the intended behavior cc @szha

I'm sure some network will be fail to hybridize after this https://github.com/apache/incubator-mxnet/pull/15167 PR. So we can add e.node->op()->name.compare("_FusedOp")==0 at first. However, this op name is specified to mxnet but not tvm.

This is not right and should be reverted IMO - the problem in the original issue (apache/incubator-mxnet#18624) was a genuine bug in the fusion graph pass that generated a cycle in the graph. Omitting such node from indexed graph would result in incorrect result being produced.

@ptrendx feel free to send a PR to revert the change then

@tqchen PR #6680 done.


[BUG] [ThrottlingException] An error occurred while responding for Claude Sonnet 3.5

Describe the bug
Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
Any messages I send to Claude Sonnet 3.5 get throttled and subsequently show the error in UI: "An error occurred while responding.". I see an error in Cloudwatch logs for the /aws/lambda/BedrockChatStack-WebSocketHandler logstream:
Failed to run stream handler: An error occurred (ThrottlingException) when calling the ConverseStream operation (reached max retries: 4): Too many requests, please wait before trying again.

To Reproduce
Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
Steps to reproduce the behavior:

Go to new chat
Select Claude 3.5 Sonnet
Send a message
Expect a reply
Send another message within 5 seconds after the reply
See error: "An error occurred while responding."

Screenshots

If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

AWS Region: us-east-1
Did NOT purchase any provisioned throughput

Does it always happen? If not so, this issue is not related to this repository.

Yes, it is a persistent issue that I am able to reproduce every time

Does it still occur when you use management console?

Yup it does. Looks like Claude 3.5 Sonnet has provisioned throughput only in us-west-2, where as I deployed everything in us-east-1. Is there a way to use the us-west-2 sonnet 3.5 while everything is as-is in us-east-1?

See: bedrockRegion option

Using us-west-2 solved it. Thank you!


Remove the upscaling of the voxel size in shrink-wrap

Issue:
The ShrinkWrap tightens the convex hulls to reduce the conservativeness of the convex hulls compared to the original geometry. But it also results in "leakage" of the original geometry, that is in some areas the convex hull shrinks too much and becomes less conservative than the original geometry as shown in the left image below.
Solution:
As the distance threshold parameter of the shrinkwrap, the voxel size scaled by factor of 4 is passed. It is not clear to me why that is. But removing that factor, and therefore using a smaller distance threshold seems to reduce the leakage as shown in the right image below.

Thanks for the contribution.


Add tolgee/svelte to Tools

There a mix usage of tabulation and spaces.
Only tabulations are allowed in the json file.
You can run npm run format to fix it automatically.


Gradle-plugin: Upgrade transitive log4j dependency to 2.17.1

Hi,
with using the newest version of gatling (3.7.3) I'm getting error:
Could not resolve all artifacts for configuration ':classpath'.
   > Could not find org.apache.logging.log4j:log4j-core:2.11.0.
     Searched in the following locations:
       - file: <...>/.m2/repository/org/apache/logging/log4j/log4j-core/2.11.0/log4j-core-2.11.0.pom
     Required by:
         project : > io.gatling.gradle:io.gatling.gradle.gradle.plugin:3.7.3 > gradle.plugin.io.gatling.gradle:gatling-gradle-plugin:3.7.3 > com.github.jengelman.gradle.plugins:shadow:5.2.0

I was checking it also for version 3.7.1.
I suppose there is some dependencies of jengelman which were not updated.
Our artifactory is blocking vulnerable version of log4j.
When this will be updated? Or how to do it by myself manually in gradle?

We'll have a new release tomorrow.

Gradle plugin <IP_ADDRESS> is out.


HBASE-23664 Upgrade JUnit to 4.13

Backport of #1004 to branch-1.

Doesn't seem to be a junit5 issue open. Follow-up?

https://issues.apache.org/jira/browse/HBASE-23671

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
6m 28s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
8m 22s
branch-1 passed

+1 :green_heart:
compile
1m 48s
branch-1 passed with JDK v1.8.0_232

+1 :green_heart:
compile
1m 57s
branch-1 passed with JDK v1.7.0_242

+1 :green_heart:
shadedjars
3m 10s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 13s
branch-1 passed with JDK v1.8.0_232

+1 :green_heart:
javadoc
4m  5s
branch-1 passed with JDK v1.7.0_242

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m  8s
the patch passed

+1 :green_heart:
compile
1m 48s
the patch passed with JDK v1.8.0_232

+1 :green_heart:
javac
1m 48s
the patch passed

+1 :green_heart:
compile
1m 56s
the patch passed with JDK v1.7.0_242

+1 :green_heart:
javac
1m 56s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
xml
0m  0s
The patch has 1 ill-formed XML file(s).

+1 :green_heart:
shadedjars
3m  6s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
5m 11s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
2m  5s
the patch passed with JDK v1.8.0_232

+1 :green_heart:
javadoc
4m  7s
the patch passed with JDK v1.7.0_242

_ Other Tests _

-1 :x:
unit
186m 22s
root in the patch failed.

+1 :green_heart:
asflicense
0m 34s
The patch does not generate ASF License warnings.

238m 52s

Reason
Tests

XML
Parsing Error(s):

pom.xml

Failed junit tests
hadoop.hbase.client.TestSnapshotTemporaryDirectory

hadoop.hbase.mapreduce.TestLoadIncrementalHFiles

hadoop.hbase.mapreduce.TestLoadIncrementalHFilesUseSecurityEndPoint

hadoop.hbase.client.TestSnapshotDFSTemporaryDirectory

hadoop.hbase.client.replication.TestReplicationAdminWithClusters

hadoop.hbase.client.TestAdmin1

hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas

hadoop.hbase.regionserver.TestCompactionState

hadoop.hbase.client.TestAdmin2

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1010

Optional Tests
dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile

uname
Linux 4e1a2e21534f 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1010/out/precommit/personality/provided.sh

git revision
branch-1 / 6b940ae

Default Java
1.7.0_242

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_232 /usr/lib/jvm/zulu-7-amd64:1.7.0_242

xml
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/1/artifact/out/xml.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/1/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/1/testReport/

Max. process+thread count
3896 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/1/console

versions
git=1.9.1 maven=3.0.5

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

That's a lot of failures. Kicking the PR job to try again.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
7m 11s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

+1 :green_heart:
mvninstall
8m 43s
branch-1 passed

+1 :green_heart:
compile
1m 42s
branch-1 passed with JDK v1.8.0_232

+1 :green_heart:
compile
1m 49s
branch-1 passed with JDK v1.7.0_242

+1 :green_heart:
shadedjars
2m 49s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 13s
branch-1 passed with JDK v1.8.0_232

+1 :green_heart:
javadoc
3m 46s
branch-1 passed with JDK v1.7.0_242

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m  1s
the patch passed

+1 :green_heart:
compile
1m 42s
the patch passed with JDK v1.8.0_232

+1 :green_heart:
javac
1m 42s
the patch passed

+1 :green_heart:
compile
1m 45s
the patch passed with JDK v1.7.0_242

+1 :green_heart:
javac
1m 45s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
xml
0m  1s
The patch has 1 ill-formed XML file(s).

+1 :green_heart:
shadedjars
2m 43s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
5m  0s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
javadoc
2m  7s
the patch passed with JDK v1.8.0_232

+1 :green_heart:
javadoc
3m 48s
the patch passed with JDK v1.7.0_242

_ Other Tests _

-1 :x:
unit
147m 38s
root in the patch failed.

+1 :green_heart:
asflicense
0m 38s
The patch does not generate ASF License warnings.

198m 52s

Reason
Tests

XML
Parsing Error(s):

pom.xml

Failed junit tests
hadoop.hbase.client.TestAdmin2

hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas

hadoop.hbase.client.TestSnapshotDFSTemporaryDirectory

hadoop.hbase.regionserver.TestCompactionState

hadoop.hbase.security.token.TestGenerateDelegationToken

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1010

Optional Tests
dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile

uname
Linux 84529f3a5ea7 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1010/out/precommit/personality/provided.sh

git revision
branch-1 / 6b940ae

Default Java
1.7.0_242

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_232 /usr/lib/jvm/zulu-7-amd64:1.7.0_242

xml
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/2/artifact/out/xml.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/2/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/2/testReport/

Max. process+thread count
4560 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1010/2/console

versions
git=1.9.1 maven=3.0.5

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Isekai Human Heritage Idea

As the title states, an idea for another human heritage:
Name:
Isekai Crossbreed Human
Description:
Let us be honest, there is a reason why for any mixed race classification it is always enough to name the non human options.
Because generally it is simply save to assume that the other part of it will be human.
There is no other race, except for dragons, that is as flexible when it comes to its choice of bed partners and none as flexible when it comes to being fertile when crossbreeding and realistically by now there are no true pure humans left because everyone is at least (1/2)^100 something else.
And no matter how close to 0 that number is it is not 0 and for some reason in you all that blood became active as if you were a full member of that species.
What it would do would be actually adding other races to the character so that you count as a member of that speciesas far as feat requirements are concerned.
Sadly not all of the racial bonuses are optional heritages you need to select, some are hardcoded in the species feat added by this.
Dwarf always gives +2 to con and wis and -2 to charisma no matter what heritages you select.
As a result adding all other races as subtypes would end with quite a high modifier.
So I was thinking instead it probably should be a selection where you could select 2 to 3 other races as options.
What do people think of the idea of the heritage at all?
Also what do you think would be a reasonable limit for the amount of selections?

I think you should be able to select just 1 race for stats (just a race (e.g. Dwarf's +2 Constitution, +2 Wisdom, -2 Charisma though compatibility with tabletop tweaks should be maintained since it gives some races multiple stat heritage choices where there weren't any before) or a racial heritage (e.g. Faultspawn (Asura-Spawn) or Angelkin (Angel-Blooded))) and feat prerequisite and then select between 1 and 3 races purely for feat prerequisites and/or racial features (e.g. Light Halo & Celestial Resistance or Negative Energy Affinity & Resist Level Drain & Undead Resistance)

See the actual statement above, the racial stats were not even supposed to be the main focus of this heritage but rather the feat qualification.
However because some of those racial stats are hardcoded on the race itself rather than a feature automatically gained or a heritage selectable by it they can not be avoided.
Removing them all and then adding hidden feats that would readd them would be fairly risky.
Also most of what you listed above are not feats requiring a specific race but actual racial traits or heritages.
Those I did not intend to touch with this.

Then I must have misunderstood I had thought that stat's were supposed to be a focus in this heritage, I don't really mind if you alter it to something like this since I don't really care fore the stat choice myself either:
Human

Isekai Crossbreed Human

selectable race

grants ability to select a feat exclusive to a specific race
(not necessary) a/all racial feats*
(not necessary)(if applicable) heritage feature **

selectable race

grants ability to select a feat exclusive to a specific race
(not necessary) a/all racial feats*
(not necessary)(if applicable) heritage feature **

selectable race

grants ability to select a feat exclusive to a specific race
(not necessary) a/all racial feats*
(not necessary)(if applicable) heritage feature **

"*" == e.g. Light Halo &/or Celestial Resistance or Negative Energy Affinity, Resist Level Drain &/or Undead Resistance
"**" == e.g. Motherless' bite attack or Angelkin's Lesser Restoration
IMPORTANT not the extra proficiencies, or if you prefer only the proficiencies

Through this the human should be able to have dwarf stats and dhampir racial feats, and be able to obtain both Natural Charmer and Steel Soul

Instead of this, it would be somthing more like the human whould be able to have both Dwarf, Dhampir & Oread racial feats and a Dhampir & Oread heritage ability, and be able to obtain both Natural Charmer, Steel Soul and Echoes of Stone
Though since this human inherited the oreads racial feats it should also have a slower base movement speed etc.

An idea I had for a human heritage is something like a "Mythical Hero", that might add a specific legacy to your character depending on the hero chosen, such as:

Joan of Arc: Paladin
Nobunaga: Tactician
Gilgamesh: Instinctual Warrior

This way more heroes and legacies can always be added later as well.

hm, that is not a bad idea, a bit complicated to implement but not bad.
For one such a heritage would require you to definitly pick IP as a class because any progression needs a target class with Level to be added onto. Just going by character level is sadly not possible so it would also be a class specific heritage rahter than just a race specific one.
It also would need a few more suggestions to fill up the initial list.
I also disagree with Joan of Arc as a Paladin, she would be a Cavalier with the Order of the Star or the Order of the Lion preselected

Great suggestions.
My only goal with presenting my idea, was to try and come up with a way of creating a heritage for humans that fits the theme of Isekai. I figured by using history or mythology certain character themes could explored and added to for as long as people are willing to contibute to this awesome mod. I agree with you about Joan of Arc, Order of the Star Cavalier is a much better fit. As for more suggestion;

Hercules/ Heracles: Invulnerable Rager
Roland (Paladin of Charlemagne): Paladin
Musashi: Sword Saint
Cu Chulainn: spear wielding Mutation Warrior

I'm not a programmer or anything, I just read this post and got excited about sharing this idea. If it's to complex to implement or you think it should go in another direction, that's totally fine. Thank you for taking the time to consider it.

...any progression needs a target class

ok so, this is just a random idea, but what if it had a special human-only additional legacy? it would bypass Godking's needing to spend a special power for one, and would be an extra slot whenever the IP class is chosen, if it can be implemented in some way akin to the class+bloodline specific bonus tieflings get regarding their charisma penalty. If that's out of the question, a human-only general feat requiring IP 1st lvl for an extra legacy?
This is maybe outside the bounds of the original idea, though, especially if the intent is to provide something for humans that can be used outside of the class.
for that, my only ideas are like, some kind of human-only heritage tag that grants a special list of feats that are just copies of racial feats. I dunno if it's easier to copy/paste with a different kind of prerequisite flag or to add that heritage as an -OR- to any of the tags with a racial requirement.

that actually depends, are there any racial feats that are not part of the racial feat selection besides Destiny beyond Birth?

If you mean things like Arcane Focus (elf) and Blood Drinker/Feaster (dhampir) or Breadth of Experience (elf, dwarf, or gnome) then yeah, there's a few. Plenty aren't all that amazing but an Edge Lord human with blood feast would be pretty on par for aesthetics.

I think I was mostly considering the ideas in the second half of piggy's longer post. In terms of general build momentum, humans are already considered top-tier because of the extra feat, so my idea was along something that would be really strong in a class that gives bonus feats to take the pressure off the base feat progression without necessarily becoming overwhelming if it were slapped on a mercenary while the option to give them the IP class is turned off. Which mostly serves to pad the pedestal the MC of wotr already has, now that I say that.

crossbreed human as a version that just gets access to the feats and no ridiculous stat bonuses implemented, since you still need to take them as actual feats I think that is balanced

Not really sure if it would fit but my suggestion would be
Artificial Human:
You are not born, but created by the hand of (eg) Areelu Vorlesh . While she tried to bind the Soul of her Child, it was your Soul of another World, who was forced into this new body.
Think this would fit really good into the story itself, doesnt it?
for what it does, I allow myself just to quote the construct powers of PF, not all can and or should be implemented, but it should be a good working progress (tbh, has a lot of similarities of an undead...)
No Constitution score. Any DCs or other statistics that rely on a Constitution score treat a construct as having a score of 10 (no bonus or penalty).
Low-light vision.
Darkvision 60 feet.
Immunity to all mind-affecting effects (charms, compulsions, morale effects, patterns, and phantasms).
Immunity to disease, death effects, necromancy effects, paralysis, poison, sleep effects, and stunning.
Cannot heal damage on its own, but often can be repaired via exposure to a certain kind of effect. Constructs can also be healed through spells such as [make whole]. A construct with the fast healing special quality still benefits from that quality.
Not subject to ability damage and drain, fatigue, exhaustion, energy drain, or nonlethal damage.
Immunity to any effect that requires a Fortitude save (unless the effect also works on objects, or is harmless).
Not at risk of death from massive damage. Immediately destroyed when reduced to 0 hit points or less.
A construct cannot be raised or resurrected.
A construct is hard to destroy, and gains bonus hit points based on size, as shown on the following table.
Proficient with its natural weapons only, unless generally humanoid in form, in which case proficient with any weapon mentioned in its entry.
Proficient with no armor.
Constructs do not breathe, eat, or sleep.

possible but a lot of customization and quite a few of those effecs are hard to add

Artificial Human

the forgeborn from 3.5e feels like a better place to start than full-on constructs, but that's still a lot of custom stuff.


My first branch

I create a branch, add PROFILE.md, and ask for a pull request

I merged my first branch and main


GH-37614: [R][CI] Update CI jobs due to duckdb repo moving

Rationale for this change
Duckdb have moved the R package to a separate repo
What changes are included in this PR?
Updates the duckdb R package dev repo
Are these changes tested?
No
Are there any user-facing changes?
No

Closes: #37614

@github-actions crossbow submit test-r-dev-duckdb

(test failure due to another issue, and not repo location)


Capture Team history

As a stakeholder, I want to see the maturity evolution that a specific team has made over a certain timeframe so that I can shower them with compliments and prizes.
When saving the maturity score of a team, the file could contain a timestamp e.g. team-A-XXXXXX.json that allows me to re-create saves over a certain period.
Saving the timestamp could be optional and used similarly to a tag (e.g July 2016).

That is already on the pipeline and my current plan is to implement it with git commits (see #93)
that will give your a full historic analysis of the data (and proper backups with integrity and chain of authority)


I want to send request body parameters with json type to a url. It works in android  but I get an error in ios

I want to open a url and send it a json request in body.
I am able to open the url in android phone but in I get an error in ios. Error code is -1103 and error message as "resource exceeds maximum size"
This is my code
InAppWebView(
initialUrlRequest: URLRequest(
url: Uri.parse(
widget.url,
),
headers: {
"Accept": "application/json",
"Authorization": "${userDetails.accessToken}",
"Content-Type": "application/json"
},
body:
Uint8List.fromList((utf8.encode(body.toString()))),
),
initialOptions: InAppWebViewGroupOptions(
crossPlatform: InAppWebViewOptions(
),
),
onWebViewCreated:
(InAppWebViewController controller) async {
},
onLoadStart:
(InAppWebViewController controller, Uri? url) async {
},
onLoadError: (_, __, , ) {
print();
print();
},
onLoadStop:
(InAppWebViewController controller, Uri? url) async {
},
)

In my optionion, on iOS it's not allowed to add a body in GET request.

In my optionion, on iOS it's not allowed to add a body in GET request.

Yes, I figured it out. I had to explicitly set method as 'POST'. After that it worked. Thank you for replying


Support hierarchical naming scheme to avoid cluttering the UI in TensorBoard

The previous naming scheme for the logging summaries made cluttered tabs in tensorboard. I added a simple forward slash to make subcategory summaries grouped together.

Hey this looks great!
Ok one recent change, take a look at latest commit 8ca1819 which gets rid of the annoying group_slash kwarg and just does it automatically when using a tf_summary_writer.  Seeing this PR made me realize to do that :)  Want to simplify this PR on top of that?

Yeah, that looks great!

I removed the group_slash kwarg as you suggested. Let me know if there is anything else before merging!

OK actually I just noticed this handy context manager in the logger:
https://github.com/astooke/rlpyt/blob/8f36bda2ddc57c5d828eea0d69569f325cb8dc88/rlpyt/utils/logging/logger.py#L240
Looks like it would make it easier to add/remove other fields as people wish.
However it might also require adding the prefix to the summary writer line of record_tabular:
https://github.com/astooke/rlpyt/blob/8f36bda2ddc57c5d828eea0d69569f325cb8dc88/rlpyt/utils/logging/logger.py#L215
Sorry to extend the work here but I think this could make it nice and clean.  What do you think about wrapping the multiple logger.record_tabular() calls with the tabular prefix context manager?  And then probably doing the super().log_diagnostics() call outside the context manager, presuming it will have its own?

I'm not really sure how to do that, but you can modify this PR as you see fit!

OK thanks for the access.  Take a look at that commit and see if it seems to do the same thing you wanted?

Hey look at that...your test caught my typo  :)

Cool! I verified it works in TensorBoard


Allow Data Files to be Loaded Recursively

For particularly large data-sets, the author may wish to use directory structures within the data-set directory to segment and structure their data.
Blox should support recursively loading data files within the data-set directory.

Silly me, this does work.


naive ui 引入报错

Uncaught SyntaxError: The requested module '/node_modules/.vite/naive-ui.js?v=fb89fadc' does not provide an export named 'NEl'

naive-ui没有导出NEI 请使用NElement

ref https://github.com/TuSimple/naive-ui/pull/1739

PR is merged, You can close this issue. @antfu


SyMS Service API Swagger Client

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[x] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@piyushdubey See https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/271/Azure-REST-API-Stewardship

@weidongxu-microsoft I don't have the permission to add tags to the issue.
Here's the Issue - https://github.com/Azure/azure-rest-api-specs/issues/18744
I cannot link PR to the issue either. Appreciate your help.


reminiscence 0.3.2 (new formula)

REminiscence is a reimplementation of the engine used in the game Flashback.

Merged. Thank you for your contribution to Homebrew!


Suggestion: Easier toggle for floating

I was looking for a shortcut to quickly enable/disable floating for a window, but couldn't find any.
Hence my suggestion: Move the Float setting ("Always on Top") to the Window menu. This would allow us to assign a shortcut via system.
Thanks for considering, and thanks for the useful app!
– Tom

This is actually a great suggestion, thanks for reaching out!
As a first step, I have added a toggle to the header, which you access via Command + Shift + P:

I'm looking into refactoring the header of the app, and that will be the occasion for having all settings in the menu bar, like:

Feature is now available on main branch, will send to app store today
Cheers!


Hello Worlds that require multiple files

Should I create a sub-folder or just not do it? An example of one is NotXactlyC

Depends on how many and what each one does. Go for individual subfolders for now.

👍


[Issue] GitHub action warning message setup-azd v0.1.0 is using deprecated Node.js 16

Using<EMAIL_ADDRESS>I get this warning message:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20<EMAIL_ADDRESS>For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
May 13th, 2024, Node 20 will be enforced: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
According to this information, node20 is already used (but the warning tells otherwise):
https://github.com/marketplace/actions/setup-azd#usage
I've seen a pull request was already done to update to Node 20:
https://github.com/Azure/setup-azd/pull/87
But the latest release was from an earlier date:
https://github.com/Azure/setup-azd/releases

@hemarina should we do another release of setup-azd? Please feel free to pull this into milestones cc @vhvb1989

node16 to node20 is a breaking change, see: https://github.com/microsoft/setup-msbuild/issues/125
We need to release a major version