Excessive number of pending callbacks: 501

React Native version:

System:
OS: macOS Mojave 10.14.6
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Memory: 22.95 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.1 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 22, 23, 24, 25, 26, 27, 28, 29
Build Tools: 27.0.3, 28.0.2, 28.0.3, 29.0.1, 29.0.2
System Images: android-23 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64
IDEs:
Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7

Steps To Reproduce

Describe what you expected to happen:
Snack, code example, screenshot, or link to a repository:

Same problem

Seems to be occurring in async functions with awaiting promises. Here's a test

same issue here, not sure why

maybe firebase caused the problem ?

I had this error because I was looping and queuing hundreds of promises like
await Promise.all(filesToDownload.map(url => fetch(url)))

not the best plan... from the code it looks this warning is fired when there are more than 500 things pending in the message queue that hands runtime async calls off to the native code.  (I'm new to this code so just a quick interpretation)  https://github.com/facebook/react-native/blob/ce1703a84d2712a7df8f93a3f3ecbb2c04b72e57/Libraries/BatchedBridge/MessageQueue.js#L210
I ended up switching to Bluebird's Promise.map() function that has a concurrency option to limit how many promises are called at a time http://bluebirdjs.com/docs/api/promise.map.html#map-option-concurrency or you could use Async's mapLimit() https://caolan.github.io/async/v3/docs.html#mapLimit

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

No the issue still persists and requires the community's attention.

Hey bot, please don't close this. I am having the same issue.

This happens to me with RN 0.62.2, and didn't happen to me on earlier versions of RN (I upgraded from 0.59.9).
Is this going to be fixed?

This is happening to me with RN 0.63.2. I was on 0.61.5 and updated packages just 2 weeks before and this is a big issue for us since we are in production.

Still experiencing this on v63.2 (react-navigation v5). Any updates?

Still experiencing this on v63.2 (react-navigation v5). Any updates?

same issue

This happens to me with RN 0.62.2, and didn't happen to me on earlier versions of RN (I upgraded from 0.59.9).
Is this going to be fixed?

same with me.

I had this error because I was looping and queuing hundreds of promises like
await Promise.all(filesToDownload.map(url => fetch(url)))

not the best plan... from the code it looks this warning is fired when there are more than 500 things pending in the message queue that hands runtime async calls off to the native code. (I'm new to this code so just a quick interpretation)
https://github.com/facebook/react-native/blob/ce1703a84d2712a7df8f93a3f3ecbb2c04b72e57/Libraries/BatchedBridge/MessageQueue.js#L210
I ended up switching to Bluebird's Promise.map() function that has a concurrency option to limit how many promises are called at a time http://bluebirdjs.com/docs/api/promise.map.html#map-option-concurrency or you could use Async's mapLimit() https://caolan.github.io/async/v3/docs.html#mapLimit

i dont think i have this in my code.
but my screen had countdown.

Hi all! Since activity popped up here again, could someone reproduce this on a fresh RN template? There are some hints that react-navigation is the root cause?

Hi all! Since activity popped up here again, could someone reproduce this on a fresh RN template? There are some hints that react-navigation is the root cause?

i use react navigation, but for me, i dont found any problem with that.
my screen had countdown, after i tried disable the countdown, the warning is gone.
So i found the source of my problem
my countdown is set in state for remaining minute & remaining second.
so every second we update it by setState.
    this.myinterval = setInterval(() => {
      if (this.state.remainingSecond > 0) {
        this.setState({ remainingSecond: (this.state.remainingSecond - 1) });
      } else if (this.state.remainingMinute === 0) {
        clearInterval(this.myinterval); // STOP COUNTDOWN
        this._cancelOrder('ALL', 'ALERT', 'Pesanan Anda dibatalkan karena melewati batas waktu pemesanan'); // RUN CANCEL ORDER
        // this.componentDidMount();
      } else {
        this.setState({ remainingSecond: 59 });
        this.setState({ remainingMinute: (this.state.remainingMinute - 1) });
      }
    }, 1000);
  }

Unfortunately, we have the same issue, but in our case its the @react-native-community/async-storage causing the excessive number of pending callback. But there is one very interesting thing: the issue doesn't come just from nowwhere, it only happens, if we change the GoogleService-Info.plist to a different Firebase project or app bundle id.
Some more detailed repro:

We had used a certain firebase config in GoogleService-Info.plist for a long time, e.g. for the bundleID com.mycompany.ourfancyapp and the firebase project id our-fancy-app-dev.
Then, as we need to distribute the app to our client's private app store, we need to change the config to bundleID com.client.myapp and to a new Firebase project created to store specifically the client's data, e.g. projectID out-fancy-app-for-client-x.
As needed, we have registered a new bundleID within the new Firebase project and downloaded a new GoogleService-Info.plist file. But when we replaced the old firebase config file with the new one and ran the app, we could login using the new client-facing database, but after the login the whole app works, but it is extremely slow and nearly not usable (you have to click on an item 10 times and then wait for 2-3 minutes until it opens). In addition to that, the same error as described in this issue is shown, but for our case its showing a lot of RNCAsyncStorage pending callbacks:

The funny thing is, if we close the hanging app, move back the old GoogleService-Info.plist for the old dev bundleID and projectID, then the app is not laggin at all and the error regarding pending callbacks doesn't appear at all! 🤯

We use the latest module versions, here some detailed info:
@react-native-firebase/app: 8.4.4
@react-native-firebase/auth: 8.0.10
@react-native-firebase/firestore: 7.8.4
@react-native-firebase/messaging: 7.8.9
@react-native-community/async-storage: 1.12.0
Our team would really appreaciate, if some of you guys can find a solution for this issue soon. Because, otherwise we are going to lose our client as we can't deliver the app in time 😢  Thank you very much in advance! 👍

Hi @SplinterStan i would recommend opening an issue with react native firebase.

I updated my React Native version from 0.63.2 to 0.63.3, with initial testing I'm not getting this error, I will update if I'm getting this error with 0.63.3

@SplinterStan have you found a way to solve the problem? We have exactly the same problem

same here

@Badbreaddead Yes, after 2 weeks of painful search we've found the issue! It was indeed in our application code! We are using Firebase Snapshots to subscribe to live changes in firesore collections. We have 2 of the subscriptions in 1 component running in series (if Subscription 1 emits a value, then we are unsubscribing from the 2nd subscription and resubscribe to it again), e.g.:

...
  let unsubscribeFromGroupDocument = () => { };
  let unsubscribeNewslettersCollection = () => { };

  useEffect(() => {
    // Subscribe to Group document changes.
    unsubscribeFromGroupDocument = subscribeCurrentGroup();
    return () => {
      unsubscribeFromGroupDocument();
      unsubscribeNewslettersCollection();
    };
  }, []);

  /**
   * Subscribes to the current group referenced in the user document.
   */
  function subscribeCurrentGroup() {
    return firestore()
      .collection('groups')
      .doc(userDocument.groupId)
      .onSnapshot((groupDocument) => {
        if (loggedUser() && groupDocument.data()) {
          const groupDoc = groupDocument.data();
          setGroupDocument(groupDoc);
          persistDataInDevice('group', groupDoc);
          unsubscribeNewslettersCollection = subscribeToNewsletters(groupDoc);
        }
      }, () => {
        getPersistedDataFromDeviceMemory('group', true)
          .then((groupDoc) => {
            if (groupDoc) {
              setGroupDocument(groupDoc);
            }
          })
          .catch((error) => console.log('Error while getting group document data: ', error));
      });
  }

  /**
   * Subscribes to all newsletters in the newsletter collection.
   * @param {GroupDocument} groupDoc Firebase group document object of the user group.
   */
  function subscribeToNewsletters(groupDoc) {
    return firestore()
      .collection('newsletters')
      .onSnapshot((newslettersCollectionDocument) => {
        if (loggedUser() && newslettersCollectionDocument.docs.length > 0) {
          const newslettersCollection = newslettersCollectionDocument.docs.map(element => element.data());
          let allowedNewslettersLocal = newslettersCollection.filter((newsletterDoc) => groupDoc.newsletters.includes(newsletterDoc.id));
          persistDataInDevice('newsletters', allowedNewsletters);
          setAllowedNewsletters(allowedNewslettersLocal);
        }
      }, () => {
        getPersistedDataFromDeviceMemory('newsletters', true)
          .then((allowedNewsletters) => {
            if (allowedNewsletters) {
              setAllowedNewsletters(allowedNewsletters);
            }
          })
          .catch((error) => console.log('Error while getting newsletters collection data: ', error));
      });
  }

  /**
   * When a user group changes in the user document,
   * unsubscribes from active user group and newsletter collection subscriptions and subscribes anew.
   */
  function resubscribeToGroup() {
    unsubscribeFromGroupDocument();
    unsubscribeNewslettersCollection();
    unsubscribeFromGroupDocument = subscribeCurrentGroup();
  }

  return (
    <GroupDocumentProvider value={[groupDocument]}>
      <NewslettersProvider value={[allowedNewsletters]}>
        {
          userDocument && groupDocument && userDocument.groupId !== groupDocument.groupId && resubscribeToGroup()
        }
        <Stack.Navigator...

So, I don't exactly know which line of code caused the freeze/hanging issue, but I suppose that it was the infinite amount of resubscriptions done in the line userDocument && groupDocument && userDocument.groupId !== groupDocument.groupId && resubscribeToGroup(). As we are trying to cache the data from Firebase in the device memory using AsyncStorage, maybe there were asynchronity-related issues.

@SplinterStan thank you for the response. For me it also was the error in my code... Redundant dep in useEffect, which caused cycle with AsyncStorage.setItem calls

@safaiyeh  I think a better warning that points to the culprit would be useful.
My project uses react-native 0.63.3 and react-native-maps 0.27.1.
What I see common in all the comments it's the fact that the developer doesn't know why this error is happening.

@gabrielmoncea Yeah, it would definitely help, if the error message would include at least the callback function that is still pending for execution.

Same problem here when having multiple components running:
  handleOnReady = () => {
        Animated.timing(this.state.opacity, {
            toValue: 1,
            delay: 1000,
            duration: 500,
            easing: Easing.linear,
            useNativeDriver
        }).start();
   }

  this.setState(
     {
       isFollowed,
     },
     this.handleOnReady
  );

same problem.
module: ReanimatedModule, method: getValue;
module: RNC_AsyncSQLiteDBStorage, method: multiGet

same problem.
module UImanager method: measureLayout
Happens on iOS, macOS (Catalyst), Windows (react-native-windows). Not 100% about Android to be honest.
System:
OS: macOS 10.15.7
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 8.00 GB / 32.00 GB
Shell: 3.1.2 - /usr/local/bin/fish
Binaries:
Node: 14.13.1 - /usr/local/bin/node
Yarn: Not Found
npm: 6.14.8 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.2, DriverKit 20.0, macOS 11.0, tvOS 14.2, watchOS 7.1
Android SDK:
API Levels: 29, 30
Build Tools: 29.0.2, 30.0.1

This happens to me with RN 0.62.2, and didn't happen to me on earlier versions of RN (I upgraded from 0.59.9).
Is this going to be fixed?

same with me.
mine was 0.59.8 and upgrade to 0.61.5
so this is still no solution?

RN upgrade 16.13.1
the problem still exist

This happens to me with RN 0.62.2, and didn't happen to me on earlier versions of RN (I upgraded from 0.59.9).
Is this going to be fixed?

same with me.
mine was 0.59.8 and upgrade to 0.61.5
so this is still no solution?

RN upgrade 16.13.1
the problem still exist

@hotaryuzaki Take a deeper look in your code. There is definitely something that is causing an infinite callback loop as it was in our case with Firebase subscriptions.

This happens to me with RN 0.62.2, and didn't happen to me on earlier versions of RN (I upgraded from 0.59.9).
Is this going to be fixed?

same with me.
mine was 0.59.8 and upgrade to 0.61.5
so this is still no solution?

RN upgrade 16.13.1
the problem still exist

@hotaryuzaki Take a deeper look in your code. There is definitely something that is causing an infinite callback loop as it was in our case with Firebase subscriptions.

For me there is nothing to do with firebase, and I think the main problem not the firebase.
In my case the problem is because countdown/timer using setInterval.
When I disable the interval function the issue is gone.

I'm also not using firebase at all i am being warned referencing module UImanager method: measureLayout.
But I do have an interval in my logic. will have a deeper look here and report if i find anything. thanks for the hint.
Also, this issue isnt reliably reproducable in my case, which makes debugging more difficult.

same issue +1

I have the same issue with react native @ 0.63.x, what helped me was disabling debugging mode and restarting the app on my phone. It is a silly instance but worked for me in my case. I will update if this issue still persists anytime without debugging as well

I have the same issue with react native @ 0.63.x, what helped me was disabling debugging mode and restarting the app on my phone. It is a silly instance but worked for me in my case. I will update if this issue still persists anytime without debugging as well

Same problem here with @react-native-async-storage/async-storage...

Having the same problem,  not understanding the reason

React Native version:
System:
OS: macOS Mojave 10.14.6
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Memory: 22.95 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.1 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 22, 23, 24, 25, 26, 27, 28, 29
Build Tools: 27.0.3, 28.0.2, 28.0.3, 29.0.1, 29.0.2
System Images: android-23 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64
IDEs:
Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7

Steps To Reproduce
Describe what you expected to happen:
Snack, code example, screenshot, or link to a repository:

I solved my problem, I was giving this error to me when it came back, but as there was no previous page I blocked the back button like this:
`
useEffect(() => {
const handleBackButtonClick = () => {
navigation.navigate('dashboard');
return true;
};
BackHandler.addEventListener('hardwareBackPress', handleBackButtonClick);
      return () => {
        BackHandler.removeEventListener(
          'hardwareBackPress',
          handleBackButtonClick,
        );
      };
    }, [navigation]);

`

This happened to me in my Expo monorepo when I detached. I think the cause was having multiple versions of react-native in my repo. I solved it by putting this at the root of my workspace in package.json:
{
  "resolutions": { "react-native": "0.63.4" }
}

Oh sweet lord, I'm having this exact issue and I thought i was going mad. All promises from native modules including fetch just never resolve. This solution hasn't worked for me, but it's very much been caused by an ejected project that I then put into a yarn workspace that seems to have caused this issue. Hopefully can still be fixed by stopping react-native duplication somehow.

@jmarks-joshua if you're trying the yarn resolutions solution, make sure you remove all node modules folders (including in subpackages) and rebuild your Native app over again.
I gitignore ios and android folders thanks to Expo's new config plugin system. Once I deleted the ios folder and ran expo prebuild again, it worked for me.

Yeah I deleted everything straight away before trying, just as a default after fiddling with this thing for like 3 days.
I used to have nearly everything in ios and android gitignored but the expo eas build system seems to rely on things being committed into git (at least for ios), which doesn't seem documented anywhere but does seem to be required.
I've been playing endlessly with expo-yarn-workspaces and nohoist options, and I've no idea anymore which things should be in which if either. I did manage to get it working by manually deleting react-native from node_modules. This issue is exacerbated by the fact that xcode seems to run the workspace root version of react-native and therefore doesn't use the package metro.config.js. I'm sure I can edit that in the ios files though, I've just not figured out how yet.

I'm also using EAS. You don't have to keep ios in git if you're using their managed workflow (ie you don't directly edit files in the ios folder yourself.) I've been ignoring it like that for a few months now with no problem (per their recommendation.)
If you're personally editing files in iOS, then you can't gitignore it.

One other thing to try is adding all your native packages to the symlinks array in package.json of your native app's subpackage. This is a very important, yet poorly documented piece of expo-yarn-workspaces
See: https://github.com/byCedric/eas-monorepo-example

Yeah but I'm bare workflow as I've got payments including Apple and Google pay which still needs bareworkflow sadly

Did you try
yarn why react-native

Yeah but I'm bare workflow as I've got payments including Apple and Google pay which still needs bareworkflow sadly

Unless I'm missing something, these no longer have to be with bare workflow. In fact, nothing does anymore with Expo's new config plugin system in SDK 42.
Expo now has a config plugin for Stripe's new payment system, which should alleviate any need for bare workflow.
Docs: https://docs.expo.io/versions/latest/sdk/stripe

Without including in git it was failing to find various files both eas in the cloud and local. I think because I have some Ios files on git but not others it didn't like it.

One other thing to try is adding all your native packages to the symlinks array in package.json of your native app's subpackage. This is a very important, yet poorly documented piece of expo-yarn-workspaces

Yeah I gave that a go it doesn't seem to explain why it's been hoisted. I think
Unless I'm missing something, these no longer have to be with bare workflow. In fact, nothing does anymore with Expo's new config plugin system in SDK 42.

Expo now has a config plugin for Stripe's new payment system, which should alleviate any need for bare workflow.

Docs: https://docs.expo.io/versions/latest/sdk/stripe

Ahhhh! I think I misunderstood them saying it wouldn't work in Expo Go for doesn't work as managed workflow. Well that might solve several headaches. Many thanks for all your help. I'll give just deleting those files and gitignoring it all to see how i get on. I'll also forget nohoist for now and just use symlinks.

Yeah, as a final point, if you gitignore ios, it would break if you don't set your EAS profiles to be workflow: managed in eas.json

Good tip, definitely would have taken me some time to get that. Many thanks again.

In my case, I was using expo-location and expo-task-manager to fetch locations in background, everything was working fine but somehow these errors starting showing up. After investigating for a while, I saw that useEffect was missing dependency list. Which triggered the listener again and again and again. Therefore, after adding the list, the problem was solved. A small mistake.

maybe firebase caused the problem ?

in my case, wrong firebase collection subscription caused too many connections

After I saw many codes with that error I figure out that the common piece of code is
setState inside .then()  method which cause an Excessive callbacks similar to an infinite loop
so as solution you can remove that setState and if it necessary use Ref instead to avoid
re-render

Not stale. Just saw the issue asking me to report - had 501 callbacks pending.

I have the same issue
"react-native": "https://github.com/expo/react-native/archive/sdk-44.0.0.tar.gz",
Please report: Excessive number of pending callbacks: 501. Some pending callbacks that might have leaked by never being called from native code: {"15059":{},"15060":{},"15061":{},"15062":{},"15063":{},"15064":{},"15065":{},"15066":{},"15067":{},"15068":{},"15069":{},"15070":{},"15071":{},"15072":{},"15073":{"module":"UIManager","method":"measure"},"15074":{},"15075":{},"15076":{},"15077":{},"15078":{},"15079":{},"15080":{},"15081":{},"15082":{},"15083":{},"15084":{},"15085":{},"15086":{},"15087":{},"15088":{},"15089":{},"15090":{},"15091":{},"15092":{},"15093":{},"15094":{},"15095":{},"15096":{},"15097":{},"15098":{},"15099":{},"15100":{},"15101":{},"15102":{},"15103":{},"15104":{},"15106":{},"15107":{},"15108":{},"15109":{},"...(truncated keys)...":451}

++ on RN 0.65.0

This was a really hard one for me to track down.
What it came down to: This would only occur when I was running on a low spec device (Galaxy A12). I had a hook that looked like this:
  const [state, setState] = useState(1);
  useEffect(() => {
    const t = setInterval(
      () => setState(valueGoesHere),
      200,
    );
    return () => clearInterval(t);
  }, []);

To poll a value.
This worked fine on higher spec'd phones but it caused the excessive promise issue. You should comb your code for anything like the above snippet.

In my case, the cause of this issue was using onEndReachedThreshold in a FlatList component. We use onEndReached to load more data when a user scrolls to the end of the list. Removing the onEndReachedThreshold solved the issue.
React-Native: 0.64.3

I lost hope in Javascript. 😢
I have this simple function:
private getAttachmentTypeNames(): string[]{
    const { attachment_categories } = this.state;
    if (nullish(attachment_categories?.types)) {
	    return [];
    }
    const photo_type:string[] = [];
    for (let i = 0; i < attachment_categories?.types.length; i++){
	    photo_type.push(attachment_categories?.types[i]);
    }
    return photo_type;
}

Which gives me this Excessive number of pending callbacks: 501 error.
By changing the function to following, solved the issue: (WHY!!!)
private async getAttachmentTypeNames():Promise<string[]>{
        const { attachment_categories } = this.state;
        if (nullish(attachment_categories?.types)) {
	        return [];
        }
        const types = get.cloned<string[]>(attachment_categories?.types); // nothing special here
        const photo_type:string[] = [];
        for await (const type of types) {
	        photo_type.push(type);
        }
        return photo_type;
}

We resolve this by upgrading to react-native 0.61.2 to get this JS fix:

Use warnOnce for excessive number of callbacks error https://github.com/facebook/react-native/commit/0cafa0f5d1e7fa5369b765f4b97f38bf1608230a

you can also try patch-package to make the 1 commit code change needed
Our App with the issue:
    "react-native": "0.61.0",
    "react-native-reanimated": "1.7.0",
    "react-navigation": "4.3.9",

When we were resetting the react-navigation in order to move to a different flow in the app, it would trigger the error – due to react-native-reanimated doing too much

react-native-intersection-observer cause this error with a lot of components loaded.

In my case, I was using expo-location and expo-task-manager to fetch locations in background, everything was working fine but somehow these errors starting showing up. After investigating for a while, I saw that useEffect was missing dependency list. Which triggered the listener again and again and again. Therefore, after adding the list, the problem was solved. A small mistake.

Thanks a lot. You made my day!

check your asynchronous calls, for me it was a call in my index app , the call was in a useEffect hook that had no dependencies

This is happening to me with RN 0.63.2. I was on 0.61.5 and updated packages just 2 weeks before and this is a big issue for us since we are in production.
Edit - I had updated all the packages including navigation. the app just hangs while navigating between the screen via bottom tab bar. everything was working fine in 0.61.5 and react-navigation 4.x

Hey i am having the same error with similar setup to yours,Did you find the solution for the same?Thanks in advance.

Hi. Also encountered this problem.
"react": "18.0.0",
"react-native": "0.69.5",
"@react-navigation/bottom-tabs": "^6.3.2",
"@react-navigation/native": "^6.0.11",

I'm getting this from using a TouchableOpacity inside of a Flatlist or a Scrollview.  Very odd and I do not know why, but when I replace it with the TouchableOpacity from the react-native-gesture-handler package it works fine.

I'm also getting this when I have over 78 TouchableOpacity in a ScrollView. When I only have 77 it works fine. There is also a relationship to having a setState call within a .then() elsewhere in my component - this is actually where the warning seems to originate according to the warning's call stack. I can avoid the warning by doing any one of these three things: 1) change TouchableOpacity to Pressable, 2) keep the number of TouchableOpacity in the ScrollView to under 78, or 3) remove the setState() call from .then() on one of my async actions. I don't understand it, but am able to at least move on now.
"react": "18.0.0",
"react-native": "0.69.6"

i use expo 45 and react native similar in bare workflow
all works fine when i was on firebase 9.9 and nodeJs 16.15 lts
After upgrading firebase to 9.12 have this warnings and some other

This issue is occuring because you are using useEffect in many functions to check for every change in state. Reduce this number and see the magic happening.
Wrong Approach: useEffect(() => { } );
Correct Approach: useEffect(() => { }, [ ] );
Replace this wherever possible.
I solved this issue within 24 hours of facing.

I'm getting this from using a TouchableOpacity inside of a Flatlist or a Scrollview. Very odd and I do not know why, but when I replace it with the TouchableOpacity from the react-native-gesture-handler package it works fine.

WTF, I confirm this did the trick for me!
Thanks a million!!!

I had this also - thanks a lot! It was also the TouchableOpacity for me - I had this issue when using FlatList with pagination so list would grow to be quite large.
I switched to using TouchableRipple from react native paper which solved the issue.

same issue here..

i draw polyline using watchPosition on the map, but i think is not watchposition problem.
i guess setState, useState hook problem...

Changing it to react-native-gesture-handler worked for me to stop the warning on scroll. However, when I tap on an item in the list, the list freezes and shows the warning again.

It seems that it is indeed the TouchableOpacity - caused by a typo introduced here: https://github.com/facebook/react-native/commit/3eddc9abb70eb54209c68aab7dbd69e363cc7b29
There's a PR for a fix here: https://github.com/facebook/react-native/pull/35387
In the meanwhile, you should be able to patch TouchableOpacity.js according to the above PR if you are not in a poisiton to migrate to the TouchableOpacity provided by RNGH

I wrote a postinstall script using @FrikkieSnyman's PR that should correct the issue in existing source codes.
Save this in file.sh
#!/bin/bash

# Stores rn version in variable
RN_VERSION=$(npm view react-native version)
# Checks if line 268 is 'undefined' to prevent multiple command runs(not fool-proof)
LINE_268=$(sed '268q;d' node_modules/react-native/Libraries/Components/Touchable/TouchableOpacity.js)
# "  undefined" accounts for leading whitespace
if [ "$LINE_268" = "        undefined" ]; then
  # Enter your rn version below
  if [ "$RN_VERSION" = "0.70.6" ]; then
    # Deletes lines
    sed -i -e '266,268d' node_modules/react-native/Libraries/Components/Touchable/TouchableOpacity.js;
    # Inserts new lines
    sed -i '' '266i\
    flattenStyle(prevProps.style)?.opacity !== flattenStyle(this.props.style)?.opacity' node_modules/react-native/Libraries/Components/Touchable/TouchableOpacity.js
  fi
fi

Then in package.json "scripts"
"postinstall": "bash file.sh"
NOTE: This works for Mac os systems, may need to tweak a little depending on your system

#35387

The PR in reference is credited to @gabrieldonadel. I've just raised some awareness for it here

Also, @MrShakes - no need to reinvent the wheel. https://www.npmjs.com/package/patch-package is perfect for this use-case

I am rendering images in a list (Flatlist) and in the renderItem component, I am trying to get the actual size of the image using Image.getSize(), though it works fine but gives the same warning.

If you have a list/iterable of functions that return Promises, you can await for each promise/iteration.
Example:
const listOfPromises = [() => Promise<any>, () => Promise<any> .... ]

const awaitPromises = async () => {
        for await (const promise of listOfPromises) {
              const res = await promise()
              .... more code
        }
}

That way you won't stack up promise-tasks, you'll deal with them one at a time. This is just an alternative to the promise-task parallelization options mentioned here in the thread.
You can also try to make your list of Promises a list of functions that return Promises, and then use my suggestion.

Awaiting solved the same problem.

Hi. Also encountered this problem.
"react": "18.0.0", "react-native": "0.69.5", "@react-navigation/bottom-tabs": "^6.3.2", "@react-navigation/native": "^6.0.11",

Still exists in<EMAIL_ADDRESS>

I'm also getting this when I have over 78 TouchableOpacity in a ScrollView. When I only have 77 it works fine. There is also a relationship to having a setState call within a .then() elsewhere in my component - this is actually where the warning seems to originate according to the warning's call stack. I can avoid the warning by doing any one of these three things: 1) change TouchableOpacity to Pressable, 2) keep the number of TouchableOpacity in the ScrollView to under 78, or 3) remove the setState() call from .then() on one of my async actions. I don't understand it, but am able to at least move on now.
"react": "18.0.0", "react-native": "0.69.6"

Using Pressable worked for me.

Happening for both RN and Expo

I am using Redux Saga to display timer in react native app. I am calling dispatch on every count change and puttin value of redux state again to a local state. I think, this multiple storage and retrieval is giving this warning. Any help on this

Hello everyone,
This is my first contribution, and I hope it's helpful even though the issue is already closed.
I unexpectedly encountered the multiple callback error. Everything was fine, but one morning, I started my project and was greeted with this error. While the TouchableOpacity from React-Native-Gesture-Handler resolved most of the issues, there were instances where the error persisted. What worked consistently for me is the Pressable component from React Native. It may sound too straightforward, but after thorough testing, I can confidently say that this resolved my issue.
Hopefully, this can assist someone else as well.

The issue was closed due to inactivity, not because it was fixed. Can it be reopened?

Problem Statement:
Experiencing an excessive number of pending callbacks: 501.
React Native Version:
0.73.4
Debug Steps:
I began removing each component from top to bottom, starting with drilling down from App.tsx, until I narrowed down the problem to specific components.
Possible Solution:
In my case, the issue was with the Icon components wrapped in the Box component. By commenting or making it conditional rendering on this section, the warning disappeared.
(<Box>{*<Icon/>*}<Texr>Fixed</Text></Box>)

Leaving a breadcrumb here for others, I had some code like:
let [
      aSnap,
      bSnap,
      cSnap,
    ] = await Promise.all([
      db.collection('col').doc('doc').get(),
      db.collection('col').doc('doc').get(),
      db.collection('col').doc('doc').get()
]);

I was missing the await before db.collection

let [
      aSnap,
      bSnap,
      cSnap,
    ] = await Promise.all([
      **await** db.collection('col').doc('doc').get(),
      **await** db.collection('col').doc('doc').get(),
      **await** db.collection('col').doc('doc').get()
]);

I also added a semaphore to the beginning of this expensive function call like:
if (this.state.loadingObjectID === objectID) {
      return;
    }
    this.setState({loadingObjectID: objectID});

Both changes helped stop the error for me.

I had KeyboardAvoidingView wrapped around a child component and then also it's parent.  Once I removed the one around the child, this error disappeared.


Not compatible with latest version of intelli/scala plugin (2018.1.8)

After installing the latest Intellij version, I was unable to upgrade the scala plugin to the latest version until I uninstalled the scala cucumber plugin (message was that the version was incompatible).
Until I updated to the latest scala plugin version, I was unable to open/import/run any scala/sbt projects.

For me I was able to upgrade everything fine, but the plugin does not work with Intellij 2018

Upgrade for scala was fine for me too, but the cucumber for scala plugin does not work in 2018 version

Thanks for the info. We need to recompile against the latest scala library bundled in the scala-plugin (aswell as the recent scala-psi library). Does anyone want to provide a PR?

@danielwegener I'd be happy to do this but am not 100% sure what you mean.
Is this as simple as changing https://github.com/danielwegener/intellij-cucumber-scala/blob/master/build.sbt#L9 to use the latest scala-plugin (https://plugins.jetbrains.com/plugin/download?rel=true&updateId=44474) and raise a PR?

Hi is there any update on this?

I applied the patch from @pbyrne-mdsol and created a PR.

intellij-cucumber-scala_2.12-2018.1.0.jar.zip
I created a zip of the jar (github being picky) of the patch file that is in https://github.com/danielwegener/intellij-cucumber-scala/pull/35 . The plugin seems to work but I had to do it blind as sbt "runIdea xxx" is locking up the gui.
If I copy this jar to my plugins folder manually then cucumber works again with none of these problems.
Where to copy depends on system
https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs

@bbutler99a - what intellij build are you using?
I am using
Build #IU-181.4668.68, built on April 24, 2018
Fine and have removed and restarted multiple times.

I am using that same build.  My JRE is 1.8.0_152-release-1136-b29

Correction, I am using the community edition, so build is #IC.  Does it need to go in a special folder?  I am putting the file in C:\Users<USER ACCOUNT NAME>.IdeaIC2018.1\plugins.
I also just realized I am running on windows server 2016 which is not listed as being supported.

@bbutler99a - I will play with the ce edition version at home tonight.
The jar should just go in the same folder as the one with a Scala folder etc.
Alternatively you can checkout this project
Apply the patch

sbt updateIdea  (downloads the stuff)
sbt publishPlugin - puts the jar I uploaded into target I think

you can then copy it skipping all the downloading and unzipping etc in case something garbled it and see if you still have problems.
I am looking at creating a way so development can be done by having a run config instead of running from sbt to launch idea (like the actual scala plugin has). But that relies on creating a module with a customised classpath which is used in the run then this plugin should be easier to maintain.

Thank you for your work.  I was out of town for a few days, and now I see we downgraded to IDEA 17.3.5, but we are having issues with it also.  If you have created a repo, I'll try it out.  If we go back to 2018.1 I'll try the patch.

The old plugin used to be able to run the steps without defiing the glue but with @pbyrne-mdsol
patch though I can navigate to the step definitions in the IDE I aways have to manually enter the glue path.

This plugin relies on the jetbrains cucumber java plugin. No code changes were made but changes may of occurred in the ides internals.
This sounds kinda similar
https://youtrack.jetbrains.com/issue/IDEA-192267
In my projects with steps and feature files all within scope this is not a problem.
So questions are

What is project layout?
Does navigation stop working when glue config is removed?

The EAP jar from https://plugins.jetbrains.com/plugin/7460-cucumber-for-scala
works fine for me.
Many thanks

released as stable

Thank you :) believe it or not every time I try to navigate to github in chrome it prefers to navigate to this issue.

Running with IntelliJ 2018.2 and the latest JetBrains Scala plug-in (2018.2.10) and the problem may have returned.  The 'Cucumber for Scala' plugin will not load.  Below is an except from the IntelliJ logs.  The line of interest reads "Plugin 'Cucumber for Scala' can't be loaded because: Plugin since-build or until-build don't match this product's build number"
2018-08-21 14:59:40,152 [   3476]   INFO - llij.ide.plugins.PluginManager - newer plugin is incompatible, ignoring: C:\Users\raz59843\.IntelliJIdea2018.2\config\plugins\gherkin  2018-08-21 14:59:57,418 [  20742]   INFO - .intellij.idea.IdeaApplication - CPU cores: 8; ForkJoinPool.commonPool: java.util.concurrent.ForkJoinPool@a4710c4[Running, parallelism = 7, size = 0, active = 0, running = 0, steals = 0, tasks = 0, submissions = 0]; factory: com.intellij.concurrency.IdeaForkJoinWorkerThreadFactory@69c31580  2018-08-21 14:59:57,463 [  20787]   INFO -     #com.intellij.util.ui.JBUI - System scale factor: 1.0 (JRE-managed HiDPI)  2018-08-21 14:59:57,686 [  21010]   INFO - llij.ide.plugins.PluginManager - newer plugin is incompatible, ignoring: C:\Users\raz59843\.IntelliJIdea2018.2\config\plugins\gherkin  2018-08-21 14:59:58,367 [  21691]   INFO - llij.ide.plugins.PluginManager - Plugin 'Cucumber for Scala' can't be loaded because: Plugin since-build or until-build don't match this product's build number  2018-08-21 14:59:58,611 [  21935]   INFO - llij.ide.plugins.PluginManager - 136 plugins initialized in 939 ms  2018-08-21 14:59:58,611 [  21935]   INFO - llij.ide.plugins.PluginManager - Loaded bundled plugins: ASP (0.1), Android Support (<IP_ADDRESS>), AngularJS (182.3911.36), Ant Support (1.0), Application Servers View (0.2.0), AspectJ Support (1.2), Bytecode Viewer (0.1), CFML Support (3.53), CSS Support (182.3911.36), CVS Integration (11), Cloud Foundry integration (1.0), CloudBees integration (1.0), CoffeeScript (182.3911.36), Copyright (8.1), Coverage (182.3911.36), Cucumber for Groovy (182.3911.36), Cucumber for Java (182.3911.36), DSM Analysis (1.0.0), Database Tools and SQL (182.3911.36), Eclipse Integration (3.0), EditorConfig (182.3911.36), Emma (182.3911.36), Flash/Flex Support (182.3911.36), FreeMarker support (1.0), GWT Support (1.0), Geronimo Integration (1.0), Gherkin (999.999), Git Integration (8.1), GitHub (182.3911.36), GlassFish Integration (1.0), Google App Engine Integration (1.1.4), Gradle (182.3911.36), Grails (9.0), Groovy (9.0), Guice (8.0), HTML Tools (2.0), HTTP Client (182.3911.36), Haml (182.3911.36), Heroku integration (182.3911.36), Hibernate Support (1.0), I18n for Java (182.3911.36), IDE Settings Sync (182.3911.36), IDEA CORE (182.3911.36), IntelliLang (8.0), J2ME (1.0), JBoss Arquillian Support (1.0), JBoss Drools Support (1.0), JBoss Frameworks Base Support (1.0), JBoss Integration (1.0), JBoss Seam Pageflow Support (1.0), JBoss Seam Pages Support (1.0), JBoss Seam Support (1.0), JBoss jBPM (2.0.0), JSR45 Integration (1.0), JUnit (1.0), Java Bytecode Decompiler (182.3911.36), Java EE: Batch Applications (1.0), Java EE: Bean Validation Support (1.1), Java EE: Contexts and Dependency Injection (1.1), Java EE: EJB, JPA, Servlets (1.0), Java EE: JMS, JSON Processing, Concurrency, Transaction  (1.0), Java EE: Java Server Faces (2.2.X.), Java EE: RESTful Web Services (JAX-RS) (1.0), Java EE: Web Services (JAX-WS) (1.9), Java EE: WebSockets (1.0), Java Server Pages (JSP) Integration (1.0), Java Stream Debugger (182.3911.36), JavaFX (1.0), JavaScript Debugger (1.0), JavaScript Intention Power Pack (0.9.4), JavaScript Support (1.0), Jetty Integration (1.0), Kotlin (1.2.51-release-IJ2018.2-1), Less support (182.3911.36), Markdown support (182.3911.36), Maven Integration (182.3911.36), Maven Integration Extension (182.3911.36), Mercurial Integration (10.0), OpenShift integration (1.0), Osmorc (1.4.11), Perforce Integration (2.0), Persistence Frameworks Support (1.0), Playframework Support (1.0), Plugin DevKit (1.0), Properties Support (182.3911.36), Reactor framework support (1.0), Refactor-X (2.01), Remote Hosts Access (0.1), Resin Integration (8.1), SSH Remote Run (0.1), Sass support (182.3911.36), Settings Repository (182.3911.36), Smali Support (1.0), Spring AOP/@AspectJ (1.0), Spring Batch (1.0), Spring Boot (1.0), Spring Data (1.0), Spring Integration Patterns (1.0), Spring MVC (1.0), Spring OSGi (1.0), Spring Security (1.0), Spring Support (1.0), Spring Web Flow (1.0), Spring Web Services (1.0), Spring WebSocket (1.0), Spy-js (182.3911.36), Struts 1.x (2.0), Struts 2 (1.0), Stylus support (999.999), Subversion Integration (1.1), TFS Integration (999.999), Tapestry support (1.0), Task Management (1.0), Terminal (0.1), TestNG-J (8.0), Thymeleaf (1.0), Time Tracking (1.0), Tomcat and TomEE Integration (1.0), UI Designer (182.3911.36), UML Support (1.0), Vaadin Support (1.0), Velocity support (1.0), W3C Validators (2.0), WebLogic Integration (1.0), WebSphere Integration (1.0), XPathView + XSLT Support (4), XSLT-Debugger (1.4), YAML (182.3911.36), ZKM-Unscramble (1.0), dmServer Support (0.9.5), tslint (182.3911.36)  2018-08-21 14:59:58,612 [  21936]   INFO - llij.ide.plugins.PluginManager - Loaded custom plugins: Archive browser (0.11), Cucumber.js (181.4096.12), Protobuf Support (0.10.2), Scala (2018.2.10)  2018-08-21 14:59:58,612 [  21936]   INFO - llij.ide.plugins.PluginManager - Disabled plugins: Cucumber for Scala (2018.1.0)


Fix netty_unix_errors.c compilation on MacOS

Motivation:
The feature test macros did not work as expected on MacOS, so we ended up compiling for the GNU
variant which resulted in compilation errors.
Modification:
Add __APPLE__ as another indicator to use the XSI variant of strerror_r.
Result:
The project now once again compiles on MacOS.

@netty-bot test this please


Fix browser saving functionality to save the laboratory as an offline file

Right now in Chrome, if I save a webpage to my computer and try to use it, it doesn't work.
This use case is useful for those with spotty internet and would like to use the Laboratory for offline signing.

Edit; So, it turns out, in order to save the site, i must select "Webpage Complete" in order for it to save the js files.
But, it looks like this:

The bottom one is nonfunctional and links back to stellar.org

Maybe we could also build the site as a single offline .html file built by jenkins. Then, it can be downloaded in the releases page of the github project.

If we want to support offline usage, there are better ways to enable that now. Closing this as outdated.


Add fiber isolation

Thread locals are not Fiber-isolated and neither are Fiber locals Thread-isolated. The approach taken in this PR is to use a Thread local, storing the current fiber ID with the value. Then we can check the ids match when reading.

I won’t pretend to understand the code here, but given that you’re requiring Ruby 3.2 could you use Fiber[] (fiber storage - per fiber but inherited from parent fibers/threads) ?

As far as I can tell, Fiber[] does not give you Thread isolation.


ssh: improve ssh command description

What this PR does / why we need it:
Improved text which describes how to manually connect using ssh

Execute command in a separate terminal window
If the command includes a placeholder, the user is hinted to replace it accordingly
Added >  prefix to better distinguish regular regular output from the ssh-command to copy

Which issue(s) this PR fixes:
Fixes #315
Special notes for your reviewer:
Release note:

Improved text which describes how to manually connect using ssh

/invite @RaphaelVogel


Documentation: fix Curacao support

For some reason the CW country code disappeared from the map in #406,
but #394 provides full support for Curacao.

This will get overwritten the next time someone runs the build scripts. A more durable fix would be to add cw to the array of codes passed into this function:
https://github.com/ZeLonewolf/openstreetmap-americana/blob/2ea6017549a1831035201f66331190c69867ce09/scripts/status_map.js#L44-L47
Or hard-code it in the SVG:
https://github.com/ZeLonewolf/openstreetmap-americana/blob/5e32b51d1525aee6570c8980bf5c2e925057a1f3/scripts/blank_map_world.svg#L117


Chain ID textbox's keyboard should not allow entering "." in Add/edit custom RPC screen

Duplicate #3752


Support ESP8266

Shall we also support ESP8266 and generate stubs for it?

This stub is built on esp-hal, and we don't support esp8266 in esp-hal so this might be quite a lot of work to get it going.

Then I guess well keep using the C-stub for ESP8266, thanks!


Circular dependancy Issues

Environment information
System:
  OS: macOS 14.6
  CPU: (8) arm64 Apple M1
  Memory: 282.03 MB / 16.00 GB
  Shell: /opt/homebrew/bin/fish
Binaries:
  Node: 20.2.0 - ~/.nvm/versions/node/v20.2.0/bin/node
  Yarn: 1.22.19 - ~/.nvm/versions/node/v20.2.0/bin/yarn
  npm: 10.8.2 - ~/Documents/ampapps/backenddevtest/amplify-next-pages-template/node_modules/.bin/npm
  pnpm: 8.13.1 - ~/.nvm/versions/node/v20.2.0/bin/pnpm
NPM Packages:
  @aws-amplify/auth-construct: Not Found
  @aws-amplify/backend: 1.0.4
  @aws-amplify/backend-auth: Not Found
  @aws-amplify/backend-cli: 1.2.2
  @aws-amplify/backend-data: Not Found
  @aws-amplify/backend-deployer: Not Found
  @aws-amplify/backend-function: Not Found
  @aws-amplify/backend-output-schemas: Not Found
  @aws-amplify/backend-output-storage: Not Found
  @aws-amplify/backend-secret: Not Found
  @aws-amplify/backend-storage: Not Found
  @aws-amplify/cli-core: Not Found
  @aws-amplify/client-config: Not Found
  @aws-amplify/deployed-backend-client: Not Found
  @aws-amplify/form-generator: Not Found
  @aws-amplify/model-generator: Not Found
  @aws-amplify/platform-core: Not Found
  @aws-amplify/plugin-types: Not Found
  @aws-amplify/sandbox: Not Found
  @aws-amplify/schema-generator: Not Found
  aws-amplify: 6.4.3
  aws-cdk: 2.150.0
  aws-cdk-lib: 2.150.0
  typescript: 5.5.4
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
Issue tracking CloudFormation circular dependancy behavior
Current issue noting circular dependancy:
https://github.com/aws-amplify/amplify-backend/issues/1552
https://github.com/aws-amplify/amplify-category-api/issues/2554
https://github.com/aws-amplify/amplify-backend/issues/1723
https://github.com/aws-amplify/amplify-backend/issues/1740
https://github.com/aws-amplify/amplify-backend/issues/1715
https://github.com/aws-amplify/amplify-backend/issues/1659
https://github.com/aws-amplify/amplify-backend/issues/1658
https://github.com/aws-amplify/amplify-backend/issues/1699
https://github.com/aws-amplify/amplify-backend/issues/1594
https://github.com/aws-amplify/amplify-backend/issues/1459
https://github.com/aws-amplify/amplify-backend/issues/1375
https://github.com/aws-amplify/amplify-backend/issues/1803

I recently worked on the Gen 2 project and encountered some significant challenges. In my experimental project, I aimed to implement the following components:

Custom lambda authentication for data (using Cognito's JWKS to identify logged-in users, where the access token is a Cognito ID token wrapped in a custom format).
Overrides for some data create/update/delete mutations.
DynamoDB Stream handler.
An SQS to process messages.

In Gen 2, the root stack contains "auth," "data," and "function," which leads to circular dependency issues. To address this, I set up the local environment and ensured that each function is created in its own stack. This approach seems to be working well so far, but I am unsure if there are any other potential consequences that have not been addressed by this change.

Is this the right place to discuss this?


Onboarding BZD labs - CSV to API

New sender BZD labs will be sending CSV format to API. Contacts are:
Desiree Brock -<EMAIL_ADDRESS>Qais Alkurdi -<EMAIL_ADDRESS>

Hi Desiree,
I have taken a look at the sample data provided and looks like we are in pretty good shape. There are a few additions/ things to be aware of that would be great if we could get added/ironed out.
If it is possible we have a few additional columns we would like to see (they are listed in the Programmer's Guide as optional and don't need to necessarily be valued but we would like to have the columns included in sent files even if they are not populated). The additional column headers are:
patient_middle_name
patient_street2
patient_preferred_language
testing_lab_specimen_received_date
ordering_provider_middle_name
ordering_provider_street2
testing_lab_street2
comment
The other thing to be aware of is the date/time fields. We prefer a format with a UTC offset (e.g. "20220825154000-0800" for 8/25/2022 3:40 PM PDT). For date/time fields without a UTC offset value, ReportStream will assume a UTC offset of +0000 (which will result in inaccurate date/times being reported if the timestamps do not correlate with that timezone)
Finally, do you have a preference for either token-based authentication or a shared secret key for connecting to the API? Both methods are described in the Programmer's Guide (https://reportstream.cdc.gov/resources/programmers-guide
CDC Prime ReportStream
ReportStream Dashboard Application
reportstream.cdc.gov
) with examples.
Please let me know if you have any questions that I can answer. After you make the changes described above if you could send a new sample file for validation that would be appreciated. Please use fake data in the sample file that does not include any PHI/PII
Thank you,
James Gilmore
James Gilmore (Agile Six)
Senior HL7 Data Analyst
Pandemic-Ready Interoperability Modernization Effort (PRIME)

@GilmoreA6
Please review revised CSV File from Dobringroup:
Qais Alkurdi from Dobringroup.com has sent a revised CSV with the new additions and the timezone format changes.


Fix typo CDIR -> CIDR

Typo CDIR -> CIDR.
Maybe range could also be substituted by the word length in this case, but i may be exaggerating.

@snobu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@craigshoemaker
Can you review the proposed changes? Note that "CDIR" appears on line 84 as well.
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks, @snobu!
#sign-off


fix(linking): handle workspace setups by adding a fallback for artifacts

Motivation
Closes #5396.
The new linking fixes broke workspace setups that have files imported from outside the project root.
Solution
Add a fallback that is composed of the project root + the relative path obtained.

pending clippy

Thanks for the fix!


Add event sequences (dialogue, map changes, cutscenes, etc.)

Feature implementation: v 0.2.0 - Event Sequences
I'm hoping to next implement event sequences. The implementation should provide a simple, extend-able means to allow events to occur on the gameplay field. Examples of field events are:

doors opening and closing.
moving the player to a new map or playing a series of events on a different map (imagine the stereotypcial bird's eye view of the bad-guy planning session).
moving a character that's blocking a path.
dialogue (witty and gripping, of course).

Note: Event sequences may be usually known as "cutscenes". I think that the implementation should be more generic, however, than requiring a stoppage of gameplay. For example, the player walking on a given cell may cause a change on another part of the map (such as opening a door) without requiring the screen to fade or the player to stop moving.
Implementation
This milestone should include NPC conversation. As per Nathan's suggestion, I propose implementing dialogue via Dialogic 2. It is simple to pickup, robust, and quick to incorporate into the existing project.
Please note that I'm proposing that events are essentially commands from the command pattern.
Coupling is tricky here. I see the event sequences as a high-level object that should be able to manipulate most objects in the game. Instead, events could modify game state via the FieldEvents singleton, but that has several undesired consequences (i.e. should the cursor REALLY be able to change the playing music via singleton? Also, an event would still need access to various objects to await different commands, such as moving a gamepiece along a path). I think we probably want to inject dependencies into the event and allow events to be the high-level cross-system state-changing objects in the project architecture (which, incidentally, should help everything else remain decoupled).
Therefore I anticipate field events as being a subclass sandbox interface implemented as a node (added to an event pool). This has a few advantages:

event sequences can take full advantage of Godot. Want the screen to fade out or a sound to play? Compose the event from Godot's built-in nodes.
events are basically just scripts affecting whatever is slapped onto the scene. I toyed with using Dialogic's timelines for event sequences, but I think that would make the code very rigid and limited in exchange for a nice UI.
events may be found up by uid, allowing modification of anything running. Should make pausing easy.
events can be added to anything and can easily be chained together. Some will be executed by code, some will be interacted with from other gamepieces, some will be walked over on the field map, etc.

The milestone is broken down into tasks for my own benefit here. The scope and details will probably change as the main feature is being implemented.
Discussion and Feedback
I would love to hear any feedback on the propsed model before I begin the implementation.

The description you are making of the system is a little too abstract. My recommendation for these kinds of things is to always start by implementing the concrete event sequence and generalize based on that experience. Abstraction and thinking abstractly tends to increase coupling and code complexity.
Using a subclass sandbox, commands, or just some dictionary describing an event sequence, any of these approaches can generally get the job done.
Concretely you just want to have a limited list of functions to restrict what developers can do. And if so, it does not matter if these functions are accessed through a Singleton, as long as they prevent users from messing up the game.


Add workflow for DIRECTORY.md

Provide a DIRECTORY.md file that is built automatically https://github.com/TheAlgorithms/Zig/issues/10

Wow! Thanks for the contribution.


add B&H to the "Electronics" section

they sell a bunch of non-photo/video stuff as well.  computers and
things.

👍
Note to myself - if I turn this into a real site instead of just a README, things need to be in multiple categories.


Make BrAPI Lists Ordered

Feature Request
@BrapiCoordinatorSelby I think BrAPI lists serve the most use cases if they are ordered lists. Currently, there is nothing in the spec that requires ordering to be preserved. The BrAPI-Java-TestServer generally returns list items in the same order they were created in, but this is only due to the default order in which PostgreSQL returns rows when an ORDER BY clause is omitted and is not guaranteed by any means.
Possible Implementations
Adopt UUID v7
Version 7 UUIDs are time-sortable, the first 48 bits are a timestamp with millisecond precision. For entities created by the same system in the same millisecond, implementations usually use an increasing counter to ensure monotonicity within each millisecond as well.
Pros

This doesn't require adding new fields.

Cons

It's a little too clever, people generally won't look at a UUID and understand it's v7 and time-sortable. The purpose of an integer field called "position" for example is far more obvious.
It's probably better to store and represent list order explicity.
Poor options for existing data migration: either preserve primary keys of existing data and forgo time-sortability or migrate to UUID v7 and change primary keys of existing entities.

Add Field(s) to List Items
Adding a created timestamp and/or an integer list position field to list items could work in at least two ways. (1) The new field could be added to the API spec and explicitly passed back and forth when creating and reading lists (an integer position would make sense in this case) or (2) it could be a means of transparently preserving the original order of the list (a timestamp would be suitable in this case).
Pros

Explicit, obvious function.
Forces a data migration, but will not change primary keys.

Cons

Requires change to API spec or at least data model.

An example of transparently maintaining the ordering of BrAPI lists can be seen here in Breeding Insight's fork of the BrAPI-Java-TestServer.

hmmm I'm not sure I see the argument for adding an explicit order field to the Lists spec. JSON arrays are ordered and the order will be maintained from client to server. its up to the server implementation to maintain the order of the items sent from the client. And that can be done without altering the spec, as you have demonstrated with the test server.
I would be open to adding text to the spec stating that maintaining the order is a required/recommended best practice. But I don't see why the JSON data models need to become more complicated?

I see your point. I thought of a case where adding an explicit order field could be useful, though it might not be real use case.

If someone wanted to preserve non-contiguous ordering (and potentially slot in other items later).
If adding new items to a list in specific positions, one would want to specify item positions in the POST to /lists/{listDbId}/data.

I realize that's a little contrived, but it does make me think that if the documentation is changed to recommend that implementations preserve order, it would be worth describing the recommended behavior of the /lists/{listDbId}/data POST endpoint specifically as well. I think append is the most natural behavior.


Update GSOC_monitor

@peterm790, I've been immersed in SciPy and ESIP Summer Meeting last week and this one, and thought I'd better catch up on what you've been up to:  https://github.com/fsspec/GSoC-kechunk-2022/blob/main/GSOC_monitor.md
Got time for a quick update there?

Yes forgot to update! will do so now


ctrl+V in word cannot work after installing powertoys.

Windows10+ Office2019
Windows build number: [run "ver" at a command prompt]  10.0.18363.900
PowerToys version: 0.18.2
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

hi, @ecorui, can you provide more details?

does it work outside of word?
have you remapped anything
does this happen only when PT is running? or even when its not running

font{
    line-height: 1.6;
}
ul,ol{
    padding-left: 20px;
    list-style-position: inside;
}

    Hi, thank you for your response!
    It works outside of word.I have not remapped anything.When PT is not running, it also happens.When it happens, Word throws an error: File cannot be found: MathPage.wll. The error code is 53.I know mathpage.wll is a file in mathtype. Indeed, I use mathtype in word to type mathematic functions.I checked the file, it is in the right position. Mathtype always works well, even after I installed PowerToys.I have not uninstalled PT, so I do not know whether the error would disappear if I do so.Many thanks!

                            ruanruiphi

<EMAIL_ADDRESS>

    签名由
    网易邮箱大师
    定制

On 6/30/2020<EMAIL_ADDRESS>wrote：

hi, @ecorui, can you provide more details?
does it work outside of word?
have you remapped anything
does this happen only when PT is running? or even when its not running
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

hi, @ecorui, can you provide more details?

does it work outside of word?
have you remapped anything
does this happen only when PT is running? or even when its not running

Hi, thank you for your response!
It works outside of word.
I have not remapped anything.
When PT is not running, it also happens.
When it happens, Word throws an error: File cannot be found: MathPage.wll. The error code is 53.
I know mathpage.wll is a file in mathtype. Indeed, I use mathtype in word to type mathematic functions.
I checked the file, it is in the right position. Mathtype always works well, even after I installed PowerToys.
I have not uninstalled PT, so I do not know whether the error would disappear if I do so.
Many thanks!

hi, @ecorui, can you provide more details?

does it work outside of word?
have you remapped anything
does this happen only when PT is running? or even when its not running

I tried to repair my Office today with itself, and the bug disappeared.
Thx!


PandasMapper Subset Exception

Expected Behavior
Be able to create a DataFrame with the columns of DataFrame from a History request after dropping the Symbol index.
Actual Behavior
Exception in PandasMapper:
No key found for either mapped or original key. Mapped Key: {mKey}; Original Key: {oKey}

Reproducing the Problem
        [TestCase(true)]
        [TestCase(false)]
        public void BackwardsCompatibilityDataFrame_subset(bool cache)
        {
            if (cache) SymbolCache.Set("SPY", Symbols.SPY);

            using (Py.GIL())
            {
                dynamic test = PythonEngine.ModuleFromString("testModule",
                    $@"
def Test(dataFrame, symbol):
    data = dataFrame.droplevel('symbol')
    data = data[['low', 'high']][:-1]").GetAttr("Test");

                Assert.DoesNotThrow(() => test(GetTestDataFrame(Symbols.SPY), Symbols.SPY));
            }
        }

Original report: https://www.quantconnect.com/forum/discussion/12378/keyerror-039-no-key-found-for-either-mapped-or-original-key-mapped-key-original-key-039
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

FYI I was able to get my issue resolved locally when running CLI by updating tensorflow to v2 (following this post). If you were to update the libraries on the cloud that would likely fix the issue without having to modify PandasMapper.


How to optimize training and avoid overfitting for a new dataset

Thanks for the great share, I am using your repository to work with another dataset where the skeletons are not humans ( I read the dataset in by customizing the feeder etc. and I also changed the joints etc.) It is a smaller dataset, and when I train the training loss keeps going down however the validation accuracy is very low, it is around 57-62 at best during early epochs, and then it gets worse and settles around 57 at best or lower around 40.
Firstly, for this dataset (there are two actors and each has 5 joints), how can I optimize the parameters? Which ones shall I experiment with? I have clipped videos into segments of 90 frames which equals to 3 seconds.
And secondly, what measures can I take to avoid overfitting?
I believe your method intuitively makes a lot of sense so I really want this to work out, I would appreciate any thoughts, insights.

I met the same question.If you solve them,can you tell me the answer of these. I would be appreciated it~

@luoluo-gif
I am still trying to make the network perform better and decrease the validation loss further, but I was not able to. I managed to get 67% accuracy (due to a mistake I made with data reading which I fixed now)
But here are things I tried but did not improve the accuracy:
using adam optimizer
using adam optimizer with a scheduler that chnages learning rate when there is a plateu
data augmentation ( random flip, crop, shear, scale, rotation) -> Somehow data augmentation made things even worse, I also tried original data+augmented data and it performed much worse
I tried a bunch of variables for learning rates and steps but no luck
I am thinking maybe reducing network layers could work, so I checked the net and st-gcn parts of the code  but, I am not sure how I can do this. Any comments on your part? What you have tried so far?

Thanks for the great share, I am using your repository to work with another dataset where the skeletons are not humans ( I read the dataset in by customizing the feeder etc. and I also changed the joints etc.) It is a smaller dataset, and when I train the training loss keeps going down however the validation accuracy is very low, it is around 57-62 at best during early epochs, and then it gets worse and settles around 57 at best or lower around 40.
Firstly, for this dataset (there are two actors and each has 5 joints), how can I optimize the parameters? Which ones shall I experiment with? I have clipped videos into segments of 90 frames which equals to 3 seconds.
And secondly, what measures can I take to avoid overfitting?
I believe your method intuitively makes a lot of sense so I really want this to work out, I would appreciate any thoughts, insights.

Hello, may I ask how do you use openpose saving bone tag other data set?

Hi @imduygusarikaya
Did you solve the problem?
I met the same problem and I tried chage some hyperparameter
change learning rate ,batchsize ,set dropout
but still don't work

@luoluo-gif
I am still trying to make the network perform better and decrease the validation loss further, but I was not able to. I managed to get 67% accuracy (due to a mistake I made with data reading which I fixed now)
But here are things I tried but did not improve the accuracy:
using adam optimizer
using adam optimizer with a scheduler that chnages learning rate when there is a plateu
data augmentation ( random flip, crop, shear, scale, rotation) -> Somehow data augmentation made things even worse, I also tried original data+augmented data and it performed much worse
I tried a bunch of variables for learning rates and steps but no luck

what process do you apply in make dataset ? could you share some code about preprocdess dataset?

Any updates here? Regarding decreasing the validation loss.


[Request] New content descriptors for disturbing content

Hello,
I can't find the content descriptors for disturbing content that implemented on many other rating system across the world.
Many horror games at Game Jolt (which uses a customized OGRS rating system) doesn't have any content descriptors about these, and I don't know why OGRS doesn't have a content descriptors for a "disturbing content".
When you (dnaf) implement them into a OGRS Rating system, please tell me a reason why the content descriptors of disturbing content aren't implemented.
Sincely,
KirbyJoe(JoeH)

Added, thanks for the recommendation! ^-^
Also, I was unaware that GameJolt was using OGRS. It's really cool seeing my project's name on such a big website. I didn't know anyone else really used it at all!

Hello? I can’t find a “Disturbing Content” on the generator, it’s maybe a glitch. Here’s an issue for detail of that with addition of levels: https://github.com/dnaf/OGRS/issues/11


[feaLib] Glyph classes should be lists, not sets

The following is currently rejected by feaLib. The root cause is that glyph classes are currently represented as sets; should be lists instead.
Input:
feature test {
    sub [a b c d] by [T E S T];
} test;

Expected output:
        <SingleSubst index="0">
          <Substitution in="a" out="T"/>
          <Substitution in="b" out="E"/>
          <Substitution in="c" out="S"/>
          <Substitution in="d" out="T"/>
        </SingleSubst>

Observed:
bug.fea:2:5: Expected a glyph class with 4 elements after "by", but found a glyph class with 3 elements

The most recent pipeline pull that I built and ran fixes the above issue. Thanks for fixing it.

Yes, that's a biggie. In an ideal world, there should be classes that are lists and there should be classes that are sets. For UFO-style group kerning or contextual GSUB substitutions, classes should be sets, for "class by class"
GSUB substitution shorthand, they should be lists. But since there is no way to cleanly tell them apart, classes should be lists on the level of feaLib.

👍


Allow developers to implement their own Permission Prompts

Is your feature request related to a problem? Please describe.
I am developing an application which is opened via another application. When my application is launched it connects to a WebRTC connection and attempts to share the screen using navigator.mediaDevices.getUserMedia.
This is required to be done with zero user interaction.
Describe the solution you'd like
A method for developers to override the permissions dialog, to enable to show our own prompts or other custom logic.
e.g. a config flag, per permission(?), to expose events to both JS and Rust for when the application requires/requests permissions
Describe alternatives you've considered
Electron already does this but it is opt-out, meaning that no dialogs are shown for any permission requests - very bad for security
Additional context
definitely needs to be an opt-in so that the user is prompted in default configuration
See Electron GH issues above for more context
Related: tauri-apps/wry#81

My understanding is that Tauri addresses the security issue differently from Electron: Capabilities reachable from the UI are statically restricted through the tauri.conf.json manifest. This acts as damage control for compromised UIs such as through an XSS attack.
Tauri also asks for permission (soft prompts) for notifications, sound, camera etc. This is not a security feature, but rather just respectful UX and sensible defaults. It would be trivial for a malicious developer to bypass these - and there's very little Tauri can do since sandboxing on desktop OSs is very limited. Am I understanding this correctly? Is there some additional complexity around the HTML5 JS APIs that I left out?
In either case, I think it largely makes sense to be able to override these soft prompts:

It's difficult to achieve consensus on the consent criteria and what constitutes best practice.
Apps are not created equal. For instance, a sound/video app that asks for consent for playing media would be nuisance-only.
The OS sometimes provides its own prompt. I've seen MacOS ask for notification permissions - this could result in duplicate notifications – as well as confusion about where to find the relevant settings.
The app could provide it's own user-space permission UI. For instance, it's quite common to provide more fine-grained notification controls for e.g. chat apps.

Lastly, alert fatigue is a real thing. Prompts are not cost-free, particularly (1) for less technical users and (2) on first use when their attention is already saturated.


Allow list log lines for helidon

The helidon native-image build is being driven by the helidon-maven-plugin which doesn't allow for unlocking certain parameters which the maven-plugin itself is adding. Therefore, allow list the newly produced warnings for now.
Closes: #189

Related to #184

Thanks!


Allow exposing of docker and kubectl installation

This makes docker accessible for development and enables the usage
of kubectl from the inside of the vm.

Question for the group: should we enable this for the multi-machine vagrant? Seems like yes?

@robszumski Sure, any change to single-node should generally be in multinode as well.
@martinhoefling Could you elaborate on what you mean by exposing docker and the motivation behind it? Installing kubectl by default is certainly useful.

@robszumski - if it is considered useful - can port these options to the multi node setup as well.
@pbx - The additional socket file exposes the docker control socket via tcp so that it can be used from the host system. For me, this is useful since with that setup, I can use docker directly from my mac.
In conjunction with the guest install of kubectl, I can do the following:
Set up a docker registry for the cluster - expose it via kubectl on 'localhost' on the coreos machine.
Setting DOCKER_HOST to the vm ip allows me to use docker and push / pull to the 'localhost' registry and at the same time use those images from kubernetes.

Being able to interact with the docker engine running inside the node is great for development indeed! Great initiative!
I'm trying to run your fork @martinhoefling. Not being that familiar with Vagrant I'm struggling to figure out how to set EXPOSE_DOCKER=true in a way that it propagates to the user-data script. Any tips?
Thanks in advance

I did not find a way to achieve this as well. So I just modified the file. Keeping everything in git gives you an overview what is modified.

Thanks for the quick reply!
I ended up doing that as well. But it would be great if there was an option one could give to vagrant up that would override the configuration. Keeping your local modifications in sync with the origin becomes cumbersome in the long run imo :)
Great work though, I can now connect to the coreos docker daemon by setting
export DOCKER_HOST="tcp://<IP_ADDRESS>:2375"

👍 This would be very handy to have in coreos:master.
My use case is also local dev - minikube isn't cutting it for me and being able to connect directly into the docker daemon from my host + run kubectl on the node are the missing pieces!

Hey - Thanks for your help with this. I'm closing this PR because this repo is not in alignment with current versions of Kubernetes, and is no longer active. The CoreOS Kubernetes documentation has been moved to https://github.com/coreos/tectonic-docs, where it will be published and updated.


feat: add jina hub list

add hub list for show the local location of Jina executors

separated pr:
jina-core pr

Please provide a screen shot of the terminal to show how does it look like.

The code looks good generally.
Please provide a screen shot of the terminal to show how does it look like.
I'll approve if the UI looks good as well.

I see, I will record a command line video about it

The code looks good generally.
Please provide a screen shot of the terminal to show how does it look like.
I'll approve if the UI looks good as well.

I see, I will take a photo of a command line.

After the refactor the print result of hub list. it looks like:


Add volumizr to awesome-tools

We need to add volumizr to awesome-tools
source: https://github.com/TheNatureOfSoftware/volumizr

Closing this issue now. Will re-open this when we have cycles to look into this issue.


Determine what, if any, third party NPM modules should be installed by default

The runtime image could install a curated set of NPM modules that are there by default. This would allow users to avoid having to specify these in a package.json file. In simple cases, this would mean that the user could avoid an npm install step altogether.

Based on off-github conversations with @slinkydeveloper, we should at least consider bundling the top three or four test frameworks with the runtime image.

I am moving this issue to faas-js-runtime-image since whatever modules are installed will be installed globally on the image itself, and not as a part of this framework.


Unpublish 1052 studies for Hoskens PMID 33983923

oops yeah it's only 1049 - not sure how I typed that wrong! thanks @sajo-ebi


Remove pype presets from library loader

This removes presets from library loader. It was used to pick default library, however the it introduced pype dependency to core, for very little benefit

Wrong code push :D


Port parts of the Twisted sections to Python 3

This is enough to get Crossbar working, so far, plus a fair amount of tests passing that don't depend on twisted.application.

cc @oberstet


Change CI to use published Docker image

This commit modifies the CI to use a container image published to the
Github container repository. The Dockerfile for the image is also
included.
Signed-off-by: Ionut Mihalcea<EMAIL_ADDRESS>

Ok, build time dropped from 23 minutes to 12 (dominated by the all-providers build) 📉
I'll try to integrate the trusted-service-provider build in there as well, shouldn't be too bad.

Ok, this PR is READY 🔥
I moved the Trusted Services stuff in the Ubuntu 18 image (which clocks in at around 4 GB for the final image - about 9 with all the precursors), everything in Github Actions is now using the same one!
I've also added Trusted Service provider to coverage reporting! ☂

Would it be possible to host the image (or images in the future) in their own repo so that when a PR is merged, the image is automatically built and upstreamed?


Multiple debugging sessions hotkey issue

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

VS Code Version: 1.93.1
OS Version:  Windows 11

Steps to Reproduce:

Start any debugging session with your hotkey, it's F5 for me;
Press F5 again and nothing happens.

Workaround:
Hit Run in the toolbar and then Start Debugging in the context menu, the last debugging session will run.
Expected behavior:
In my opinion, debugging hotkey should behave just like the context menu button.
Notes:
The current behavior introduces inconsistency in such cases like mine. I have to debug two C++ processes at the same time. Compound debugging is not quite work for me, since main process creates the child one on user's demand and I have to attach to child process manually.

By default, while debugging, F5 is "continue". I'm not a big fan of that pattern, but I don't think we should change how the defaults work at this point. You could customize your keyboard shortcuts to run workbench.action.debug.selectandstart with F5 while in debug mode, or assign another key to it, but it sounds like that's the command you want.
You could probably get your launch + attach scenario to work, we debug vscode with a compound config like this :)

You could probably get your launch + attach scenario to work, we debug vscode with a compound config like this :)

The problem with C++ debugger there, I can't just specify process name and make VS Code wait for this process to appear. Attach debugger accepts only process ids, sadly. I have to do several clicks in main to make child process start and because of this popup window for process selection closes immediately since VS Code looses focus for a second.
But anyways, thank you for the answer, this shortcut is exactly what I wanted, guess I overlooked it somehow earlier.


GluonCV YoloV3 Darknet53 example minor fixes

Description of changes:
Fixes to GluonCV YoloV3 Darknet53 example:

Corrects cell type from markdown to code
Removes empty code cell

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

@ngluna

Cool. Thanks for fixing this.

Looks like there is another error in here. Running:
!python tools/prepare_dataset.py --dataset pascal --year 2007,2012 --set trainval --target VOCdevkit/train.lst
!rm -rf VOCdevkit/VOC2012
!python tools/prepare_dataset.py --dataset pascal --year 2007 --set test --target VOCdevkit/val.lst --no-shuffle
!rm -rf VOCdevkit/VOC2007

Returns:
AssertionError: Path does not exist: /home/ec2-user/SageMaker/amazon-sagemaker-examples/sagemaker_neo_compilation_jobs/gluoncv_yolo_darknet/tools/../VOCdevkit/VOC2007/ImageSets/Main/test.txt

That's weird, I just run this notebook on a clean repo:
!python tools/prepare_dataset.py --dataset pascal --year 2007,2012 --set trainval --target VOCdevkit/train.lst
!rm -rf VOCdevkit/VOC2012
!python tools/prepare_dataset.py --dataset pascal --year 2007 --set test --target VOCdevkit/val.lst --no-shuffle
!rm -rf VOCdevkit/VOC2007

Output:
saving list to disk...
List file VOCdevkit/train.lst generated...
Creating .rec file from /home/ec2-user/SageMaker/amazon-sagemaker-examples/sagemaker_neo_compilation_jobs/gluoncv_yolo_darknet/VOCdevkit/train.lst in /home/ec2-user/SageMaker/amazon-sagemaker-examples/sagemaker_neo_compilation_jobs/gluoncv_yolo_darknet/VOCdevkit
time: 0.031130313873291016  count: 0
time: 4.787977457046509  count: 1000
time: 4.777846813201904  count: 2000
time: 4.581155061721802  count: 3000
time: 4.637202024459839  count: 4000
time: 4.828996181488037  count: 5000
time: 4.677260637283325  count: 6000
time: 4.68686580657959  count: 7000
time: 4.578396558761597  count: 8000
time: 4.62526273727417  count: 9000
time: 4.5579094886779785  count: 10000
time: 4.505211353302002  count: 11000
time: 4.783920764923096  count: 12000
time: 4.728159666061401  count: 13000
time: 4.548075437545776  count: 14000
time: 4.400712966918945  count: 15000
time: 4.549795627593994  count: 16000
Record file VOCdevkit/train.rec generated...
saving list to disk...
List file VOCdevkit/val.lst generated...
Creating .rec file from /home/ec2-user/SageMaker/amazon-sagemaker-examples/sagemaker_neo_compilation_jobs/gluoncv_yolo_darknet/VOCdevkit/val.lst in /home/ec2-user/SageMaker/amazon-sagemaker-examples/sagemaker_neo_compilation_jobs/gluoncv_yolo_darknet/VOCdevkit
time: 0.032164812088012695  count: 0
time: 4.525963306427002  count: 1000
time: 4.500948667526245  count: 2000
time: 4.870050668716431  count: 3000
time: 4.980758428573608  count: 4000
Record file VOCdevkit/val.rec generated...`

Was there some issue with the previous step during downloading and unzipping the dataset?

Nothing is stored in VOCdevkit  when I run the cell to download the dataset:
%%time
# Download and extract the datasets

![ ! -f /tmp/VOCtrainval_11-May-2012.tar ] && { wget -P /tmp http://host.robots.ox.ac.uk/pascal/VOC/voc2012/VOCtrainval_11-May-2012.tar; tar -xf /tmp/VOCtrainval_11-May-2012.tar; }

![ ! -f /tmp/VOCtrainval_06-Nov-2007.tar ] && { wget -P /tmp http://host.robots.ox.ac.uk/pascal/VOC/voc2007/VOCtrainval_06-Nov-2007.tar; tar -xf /tmp/VOCtrainval_06-Nov-2007.tar; }

![ ! -f /tmp/VOCtest_06-Nov-2007.tar ] && { wget -P /tmp http://host.robots.ox.ac.uk/pascal/VOC/voc2007/VOCtest_06-Nov-2007.tar; tar -xf /tmp/VOCtest_06-Nov-2007.tar; }.

I am working on a clean branch as well.

Now I get it, you probably already had these files downloaded on your notebook instance under /tmp/*.tar. I have just pushed a modified code to always check for local directory. Please give it a try now.

Cool. It is now downloading. BUT
How much space do the files take? Now I am running into storage issues:
tar: VOCdevkit/VOC2012/JPEGImages/2010_004703.jpg: Wrote only 5632 of 10240 bytes
tar: VOCdevkit/VOC2012/JPEGImages/2010_004704.jpg: Cannot write: No space left on device
tar: VOCdevkit/VOC2012/JPEGImages/2010_004708.jpg: Cannot write: No space left on device
tar: VOCdevkit/VOC2012/JPEGImages/2010_004710.jpg: Cannot write: No space left on device
tar: VOCdevkit/VOC2012/JPEGImages/2010_004712.jpg: Cannot write: No space left on device
tar: VOCdevkit/VOC2012/JPEGImages/2010_004714.jpg: Cannot write: No space left on device
tar: VOCdevkit/VOC2012/JPEGImages/2010_004717.jpg: Cannot write: No space left on device
tar: VOCdevkit/VOC2012/JPEGImages/2010_004721.jpg: Cannot write: No space left on device
.
.
.

Not too large, 2.9 GB after unzipping:
sh-4.2$ du -h VOCdevkit/
2.3M    VOCdevkit/VOC2012/ImageSets/Action
80K     VOCdevkit/VOC2012/ImageSets/Segmentation
36K     VOCdevkit/VOC2012/ImageSets/Layout
7.0M    VOCdevkit/VOC2012/ImageSets/Main
9.4M    VOCdevkit/VOC2012/ImageSets
68M     VOCdevkit/VOC2012/Annotations
14M     VOCdevkit/VOC2012/SegmentationObject
14M     VOCdevkit/VOC2012/SegmentationClass
1.9G    VOCdevkit/VOC2012/JPEGImages
2.0G    VOCdevkit/VOC2012
20K     VOCdevkit/VOC2007/ImageSets/Segmentation
28K     VOCdevkit/VOC2007/ImageSets/Layout
3.3M    VOCdevkit/VOC2007/ImageSets/Main
3.3M    VOCdevkit/VOC2007/ImageSets
40M     VOCdevkit/VOC2007/Annotations
3.0M    VOCdevkit/VOC2007/SegmentationObject
3.0M    VOCdevkit/VOC2007/SegmentationClass
855M    VOCdevkit/VOC2007/JPEGImages
904M    VOCdevkit/VOC2007
2.9G    VOCdevkit/

Zipped files are about 2.8GB:
sh-4.2$ du -h /tmp/*.tar
431M    /tmp/VOCtest_06-Nov-2007.tar
439M    /tmp/VOCtrainval_06-Nov-2007.tar
1.9G    /tmp/VOCtrainval_11-May-2012.tar

Noted.
I restarted my NI which cleared up some storage space.
I will try again soon. Right the website hosting the dataset is down.
Connecting to host.robots.ox.ac.uk (host.robots.ox.ac.uk)|<IP_ADDRESS>|:80... failed: No route to host..
Confirmed this by trying to load http://host.robots.ox.ac.uk/pascal/VOC/voc2012/VOCtrainval_11-May-2012.tar from my browser

In the meantime, I'll merge the other commits so that, once the data is accessible, it'll be able to run.
If the server is permanently down, I suggest we store it in a shared S3 bucket. [We have that option now].

@bpawlik
Looks like the page is still down. Is there another website that hosts the dataset? If yay, I suggest we link to temp. And then move a copy of this dataset into our shared S3 bucket

Looks like this notebook will be removed if it is not fixed by the 30th.

@ngluna https://github.com/aws/amazon-sagemaker-examples/pull/1638


feat(): Task links

Idea for a new feature:
Add the option to pass task_links to flow.run().
task_links defines a mapping from tasks to (external) tables in the database.
When the flow is executed all tasks run as usual expect for the tasks listed in the mapping. These tasks are not executed, instead an ExternaTableReference is established for them.
If the option is not used flow.run() works as usual.
Usecase: Development on a task requires testing it on a large dataset. Development in the original database is discouraged as it is used by many users. Duplicating / rerunning the entire database takes too long / too many computational resources.
-> This feature allows to use the tables in the original database without overhead, only run the tasks/stages interesting for the development at hand and leaves the other users undisturbed.
Note: Most of the changes actually originate from moving container.py to another submodule which was needed to solve a circular import (maybe there is a better way?)
@windiana42 / @nicolasmueller WDYT?
Checklist

[ ] Added a docs/source/changelog.md entry
[ ] Added/updated documentation in docs/source/
[ ] Added/updated examples in docs/source/examples.md

I would prefer if the syntax of this PR would be similar to: https://github.com/pydiverse/pydiverse.pipedag/issues/217
This might look as follows:
    with Flow() as f:
        with Stage("sql_table_origin"):
            _ = make_external_table()

        with Stage("sql_table_linked"):
            table = duplicate_table_reference()
            _ = consume(table)
    external_link = table

    with StageLockContext():
        # Normal execution. duplicate_table_reference should return an empty table
        result = f.run()
        assert result.get(table, as_type=pd.DataFrame).shape[0] == 0

    with StageLockContext():
        # Linked execution. Body of duplicate_table_reference should not be executed,
        # instead output is referenced from the linked table
        result = f.run(
            inputs={
                external_link: ExternalTableReference(
                    "external_table",
                    schema="external_schema",
                )
            }
        )

We could even support a feature for the usecase to reference the same table in another pipeline instance:
   cfg = PipedagConfig.default.get(instance)
   input_cfg = PipedagConfig.default.get("full")

    with Flow() as f:
        with Stage("sql_table_origin"):
            _ = make_external_table()

        with Stage("sql_table_linked"):
            table = duplicate_table_reference()
            _ = consume(table)
    external_link = table

    with StageLockContext():
        # Linked execution. Body of duplicate_table_reference should not be executed,
        # instead output is referenced from the linked table
        result = f.run(
            inputs={
                external_link: input_cfg
            },
            config=cfg  # still optional
        )

This syntax would even allow to dematerialize dicts/lists/constants and multiple tables that appear in the output of duplicate_table_reference from the cache of "full" instance.


Randomness in mesh creation

https://github.com/schillij95/ThaumatoAnakalyptor/blob/85e7c54ae7192e08cee0d438e6824f81e6d042cb/ThaumatoAnakalyptor/graph_to_mesh.py#L169
https://github.com/schillij95/ThaumatoAnakalyptor/blob/85e7c54ae7192e08cee0d438e6824f81e6d042cb/ThaumatoAnakalyptor/graph_to_mesh.py#L178
https://github.com/schillij95/ThaumatoAnakalyptor/blob/85e7c54ae7192e08cee0d438e6824f81e6d042cb/ThaumatoAnakalyptor/graph_to_mesh.py#L192

Why is randomness with these thresholds introduced there? I can grasp the idea behind 1, but not 2 and 3.
Also, shouldnt we fix a seed for reproducibility?

Would always fail if only checking against previous and next means for the mesh windings closest to the middle and the outside of the scroll. Resulting in a cascade of empty lists for the adjacent_ts[u][i]'s.
Could be solved a lot more elegantly.

Idea is that some of the t values might have currently a bad estimate because of wrong original ts, but their local neighbors are better estimated, deleting the current t then helps finding the optimum faster.
Again, could be solved more elegantly and effectively.


feat(timepicker): add model state support

Adds support for the timepicker model $touched and $dirty states

This closes #3527.

:+1:


[BUG] Description of bug

Describe the bug
The Biomedical component of the data commons page is not displaying properties which should be stored in the cache after changes were made to the respective config file.
To Reproduce
URL: http://<IP_ADDRESS>:8080/bio/protein/bio/FGFR1_HUMAN
Browser:
Steps to reproduce the behavior:

Fork the master branch of the website repository.
Run a local instance of the branch.
On the local instance, add the slug "/bio/protein/bio/FGFR1_HUMAN"
Using inspect elements, look at the state of the data and the required property i.e "description" will be missing

Expected behavior
The data being pulled from the cache should have the "description" property but it is missing, despite being added to the config.

@wh1210 @shifucun , could you please help debugging this whenever possible ?


New release?

The latest version on npm is ancient:
// Last time updated: 2016-08-11 4:09:01 PM UTC

Released RecordRTC v5.4.1.


Warn and disable submit button when metamask/web3 is not detected

Fixes https://github.com/ewasm/ewasm-studio/issues/3

👌


check consistency between subject:OI and cabfOI extension

I'm not sure why this stalled out a few years ago, but now it merge conflicts. I'm trying to get ZLint back into shape and so will close this out.
If this lint is still relevant, please let me know and/or reopen rebased against main.


Why conduct experiment on SUNRGB-D dataset only?

I am a beginner, and perhaps this is a simple question. I noticed that the experiments in the article were conducted on SUNRGB-D, rather than, like other articles, on both SUNRGB-D and Scannet-V2. As far as I know, Scannet-V2 also has images. Could you please explain what differences between these two datasets led to conducting experiments on SUNRGB-D instead of Scannet-V2?

The point in scannet is complete and  does not necessitate extensive visual assistance.

Thanks.


Try the .NET Jupyter kernel

Investigate the .NET jupyter kernel, specifically looking for how it could interact with our extension.
https://github.com/dotnet/try/issues/408

We will investigate soon.

Did a quick 1.5 day spike. Code changes to enable the basics are super simple. Most of the time was setting up the kernels and poking around with variables and inspectRequest.
Results on the oneNote here:
https://microsoft.sharepoint.com/teams/python/_layouts/15/Doc.aspx?sourcedoc={30d33826-9f98-4d3e-890e-b7d198bbbcbe}&action=edit&wd=target(Python VS Code AI Tools%2FIANHU.one|df4d7e47-45af-4aef-b573-a2d9587027be%2FNon-Python language investigation summary|d158cacd-e559-4b77-a5cb-dd47104392b6%2F)&wdorigin=703

@greazer . Basic investigation is over, move this back to backlog for now?

This is actually complete. Moving it to closed.


Support multiple ports

Most of our marathon apps have only one portMapping but sometimes we have an app with multiple ports where one of the ports will be used for (http) health checks.
In newer versions of marathon you can specify labels for each port in the "portMappings". Maybe this is something we can use to register services in consul?
Example marathon app:
{
  "id": "/hello-world",
  "cpus": 0.1,
  "mem": 256,
  "instances": 1,
  "container": {
    "type": "DOCKER",
    "docker": {
      "image": "my-hello-world:latest",
      "network": "BRIDGE",
      "portMappings": [
        {
          "containerPort": 8080,
          "hostPort": 0,
          "protocol": "tcp",
          "name": "api",
          "labels": {
              "consul": "helloworld-api"
          }
        },
        {
          "containerPort": 8081,
          "hostPort": 0,
          "protocol": "tcp",
          "name": "actuator",
          "labels": {
              "consul": "helloworld-health"
          }
        }
      ]
   }
  },
  "healthChecks": [
    {
      "path": "/health",
      "protocol": "HTTP",
      "portIndex": 1,
      "gracePeriodSeconds": 300,
      "intervalSeconds": 10,
      "timeoutSeconds": 10,
      "maxConsecutiveFailures": 3,
      "ignoreHttp1xx": false
    }
  ]
}

This could be great addition to marathon-consul. Internally we don't use docker containers a lot, so it's no priority for us to support docker port labels.
Although if you need this feature we can help you to deliver it. Changes are required in consul.marathonTaskToConsulService. I recommend do it step by step:

[ ] Detect which port should be registered basde on port labels (in no one specified 0 wil be used)
[ ] Merge port labels with app labels (How to handle conflicts?)
[ ] Generate multiple consul services from one marathon task

If you need any guidance please reach us here or with e-mail/twitter/hangout so we can help you.

It appears we have a similar need now internally – registering an app under more than 1 name with different ports, but with the same healthcheck. It's not related to docker though. I'm coding such solution right now, will open a PR for discussion in a couple of days.

@pbetkier Thanks for merging #99 Just wondering if you have any timeline on when this #89 Enhancement will be available for testing.

@karthimohan I'd say 2 weeks time sounds realistic. We still need to test #99 internally.

Thanks @pbetkier Looking forward for this feature.

Thanks for the good work, I'm also be interested in testing once it's ready :)

@lwille Working feature is on development branch. It's working on one of our test environment but only one or two applications are using multi prot registering. If you like to test it you can build it from source.


SVG Support

SVG is an XML language based, the only thing you have to do is create a new SVG tree with all symbols (old separated svg icons) inside.
Like this:
<svg>
   <symbol id="maybe_file_name"> <!-- all svg stuff here --></symbol>
</svg>

With that, we can use the <use> to call the new svg sprite icon:
<svg>
   <use xlink:href="#maybe_file_name"></use>
</svg>

I created a project with Grunt using this model: svg-grunt-optimizer
Another great project in Pythons is pyconizr.


[ NUXT 2 - Bridge ] - Package subpath './nuxt' is not defined by "exports" in package.json

Package subpath './nuxt' is not defined by "exports" in<EMAIL_ADDRESS>

Same here

Having this issue as well with a greenfield Nuxt3 project. Installing the "latest" 2.0.0-beta.18 fixed it :+1:

Agree with this solution  "@vueuse/motion": "^2.0.0-beta.18" 👍

anyone having issues installing @vueuse/motion with Nuxt 3 try the following

create a .npmrc in the root of your project
add the following to it:

auto-install-peers=true
legacy-peer-deps=true

make sure your use the latest beta version in your package.json file which is "^2.0.0-beta.18" at the time of writing this.

  "dependencies": {
    "@vueuse/motion": "beta"
  }

run npm i to install

everything should work normally and you should not get any errors at this point. hope this helps!

Hey here, really sorry about the late answer.
This won't happen again.
Could you try<EMAIL_ADDRESS>?
Thank you a lot for providing workarounds in the meantime, @iojanis and @hamedbaatour. 💚

Hi !
I just had the same bug by installing the latest tag version on Nuxt 3.0.0-rc.9, and by upgrading to the beta tag version: everything went well and the library now works perfectly 🔥

Closing this as it seem resolved!
Thank you so much for the quick feedback!
Feel free to re-open!