Apple rejects React Native build with "ITMS-90338: Non-public API usage"

Description
Submitting a React Native app build to the Apple App Store results in a rejection email regarding "Non-public API usage".
Dear Developer,

We identified one or more issues with a recent delivery for your app, "AppName" 1.0.0 (1.2.0). Please correct the following issues, then upload again.

ITMS-90338: Non-public API usage - The app references non-public selectors in AppName: centerY, hide:, isPassthrough, onSuccess:, permissionType, removeValuesForKeys:completion:, setLabelText:, show:, valueOffset, viewManager. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

Best regards,

The App Store Team

Version
0.68.1
Output of npx react-native info
System:
OS: macOS 11.6.4
CPU: (8) arm64 Apple M1
Memory: 148.92 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.0.0 - ~/.nvm/versions/node/v16.0.0/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v16.0.0/bin/yarn
npm: 7.10.0 - ~/.nvm/versions/node/v16.0.0/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.68.1 => 0.68.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
1:Archive App(Release scheme)
2:Upload the resulting .ipa file to App Store Connect via Transporter (available on the Apple App Store)
3:Receive an email from apple that the build was rejected.
Snack, code example, screenshot, or link to a repository

Which engine are you using?

Which engine are you using?

How can I find out?

Which engine are you using?

How can I find out?

I'm using 'jsc' engine. not hermes.
{
  "expo.jsEngine": "jsc"
}

I upgraded the OS to Monterey12.3.1, but there is no change.
However, in Xcode 13.3.1, the Validate App fails. (No error if Xcode 13.2.1)

Hey, there is a PR trying to address a similar thing - can you confirm you are trying to upload an app in debug mode? Any additional information about the issue would be helpful here @Tak-As @Andressaray

Hi there! Are you using expo-dev-client? Also, can you make sure you are using the latest version of the expo package - the latest as of writing is 45.0.4.

Hey, there is a PR trying to address a similar thing - can you confirm you are trying to upload an app in debug mode? Any additional information about the issue would be helpful here @Tak-As @Andressaray

Thanks for reply.
In my environment ("react-native": "0.68.2") the result is the same in debug mode and release mode.
I can expect that my problem will be solved if the PR is merged.

Hi there! Are you using expo-dev-client? Also, can you make sure you are using the latest version of the expo package - the latest as of writing is 45.0.4.

Thanks for reply.
Yes, I was install "expo-dev-client". but my project is rejected expo.(bare workflow)
Build fails when upgrading to expo 45.0.4 & expo-dev-client 0.9.5. (Command PhaseScriptExecution failed with a nonzero exit code)

@Tak-As please let me clarify whether the app you submit the app store had expo-dev-client installed or not?

@Tak-As please let me clarify whether the app you submit the app store had expo-dev-client installed or not?

It is installed.
Part of package.json
"dependencies": {
    "@react-native-async-storage/async-storage": "~1.17.3",
    "@react-navigation/bottom-tabs": "^6.0.9",
    "@react-navigation/native": "^6.0.6",
    "@react-navigation/native-stack": "^6.2.5",
    "expo": "~45.0.4",
    "expo-dev-client": "~0.9.5",
    "native-base": "3.3.11",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-native": "0.68.2",
    "react-native-base64": "^0.2.1",
    "react-native-safe-area-context": "4.2.4",
    "react-native-screens": "~3.11.1",
    "react-native-step-indicator": "^1.0.3",
    "react-native-storage": "^1.0.1",
    "react-native-svg": "12.3.0",
    "redux": "^4.1.2"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@types/react": "~17.0.21",
    "@types/react-native": "~0.67.6",
    "@types/react-native-base64": "^0.2.0",
    "@typescript-eslint/eslint-plugin": "^5.9.1",
    "@typescript-eslint/parser": "^5.9.1",
    "eslint": "^8.6.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin": "^1.0.1",
    "eslint-plugin-import": "^2.25.4",
    "eslint-plugin-prettier": "^4.0.0",
    "eslint-plugin-react": "^7.28.0",
    "eslint-plugin-unused-imports": "^2.0.0",
    "expo-cli": "^5.4.4",
    "prettier": "^2.5.1",
    "react-redux": "^8.0.1",
    "typescript": "4.6.4"
  },

what version of expo-modules-autolinking is installed? can you share the output of npm why expo-modules-autolinking or yarn why expo-modules-autolinking?

what version of expo-modules-autolinking is installed? can you share the output of npm why expo-modules-autolinking or yarn why expo-modules-autolinking?

yarn why v1.22.17
[1/4] 🤔  Why do we have the module "expo-modules-autolinking"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "expo-modules-autolinking"
info Reasons this module exists
   - Hoisted from "expo-cli#@expo#prebuild-config#expo-modules-autolinking"
   - Hoisted from "expo#@expo#cli#@expo#prebuild-config#expo-modules-autolinking"
info Disk size without dependencies: "944KB"
info Disk size with unique dependencies: "1.97MB"
info Disk size with transitive dependencies: "7.21MB"
info Number of shared dependencies: 40
=> Found<EMAIL_ADDRESS>info This module exists because "expo" depends on it.
info Disk size without dependencies: "432KB"
info Disk size with unique dependencies: "1.47MB"
info Disk size with transitive dependencies: "6.71MB"
info Number of shared dependencies: 40
✨  Done in 0.48s.

@Tak-As could you use patch-package or modify node_modules/react-native locally for #33153 change and try to submit to app store again? because your private apis centerY, hide:, isPassthrough, onSuccess:, permissionType, removeValuesForKeys:completion:, setLabelText:, show:, valueOffset, viewManager do not have the private key events where the pr addressed. i am wondering #33153 may not able to fix your problem. at the same time, i also feel curious where the private apis coming from.

Hello! My team is deadlocked at the same issue. We aren't using expo. Changing the names does work but I can't change all the names because some are only in binary files (found using grep). Issue #33153 seems like it might fix the problem but it looks like it might not be merged until 0.70, which we don't have time to wait for (need to submit a feature by June 30 or Apple will remove our app from the store). Has anyone found a fix for this? Here are my specs in case it helps. I appreciate anyone's help, thank you!:
OS: macOS 12.2
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 505.74 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 12.19.1 - ~/.nvm/versions/node/v12.19.1/bin/node
Yarn: Not Found
npm: 6.14.15 - ~/.nvm/versions/node/v12.19.1/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 30, 31
Build Tools: 30.0.2, 30.0.3, 31.0.0
System Images: android-30 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom_64, android-31 | Google APIs Intel x86 Atom_64, android-31 | Google Play Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8193401
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
Languages:
Java: 11.0.11 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.65.1 => 0.65.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

Today we received this message:

Dear Developer,
We identified one or more issues with a recent submission for TestFlight review for your app, "Move App Staging" 2.8.0 (44). Please correct the > following issues, then upload again.
ITMS-90338: Non-public API usage - The app references non-public selectors in ventasStaging: estimatedProgress, initWithFrame:configuration:, > isMainFrame, isPassthrough, navigationType, onSuccess:, relativeSize, removeValuesForKeys:completion:, setIsEnabled:, setNavigationDelegate:, > setProcessPool:, spanArray, spanArray_Count, underline, updateSettings:, userContentController, viewManager, websiteDataStore. If method names in your > source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. > In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. > For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
Best regards,
The App Store Team

The weirdest thing is that nothing has been installed or updated in the app, only JS code has been modified since the last build.
React Native versions:
    "react": "17.0.2",
    "react-native": "0.66.2",

Expo versions:
    "expo": "43.0.4",
    "expo-camera": "12.0.3",
    "expo-document-picker": "10.1.0",
    "expo-file-system": "13.0.3",
    "expo-image-manipulator": "10.1.2",
    "expo-keep-awake": "10.0.1",
    "expo-screen-orientation": "4.0.3",
    "expo-sharing": "10.0.3",

yarn why expo-modules-autolinking
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "expo" depends on it
   - Hoisted from "expo#expo-modules-autolinking"
info Disk size without dependencies: "836KB"
info Disk size with unique dependencies: "1.58MB"
info Disk size with transitive dependencies: "2.99MB"
info Number of shared dependencies: 30

Same issue here. We just got this error from Apple after building and submitting a new app.
The weird thing is, we just submitted an app 2 days ago, and the only change is a couple of JS lines.

I'm facing the same problem here as well

Same issue here affecting our apps this afternoon, seems to be related to the outage they had earlier today.

we are facing the same issue as well

Same on Flutter

Same issue here:
Was working 3 days ago:

Apple, what did you do?
For a brief moment it gives me hope

But then, that email

Dear Developer,

We identified one or more issues with a recent delivery for your app, "xxxx" 0.1.4 (7). Please correct the following issues, then upload again.

ITMS-90338: Non-public API usage - The app references non-public selectors in LeahMobile: estimatedProgress, initWithFrame:configuration:, initWithURL:configuration:, initWithURL:entersReaderIfAvailable:, isMainFrame, isPassthrough, navigationType, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, removeValuesForKeys:completion:, setNavigationDelegate:, setProcessPool:, socket:didAcceptNewSocket:, socket:didConnectToHost:port:, socket:didConnectToUrl:, socket:didReadData:withTag:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidDisconnect:withError:, socketDidSecure:, targetFrame, userContentController, websiteDataStore. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

Same issues here

What MacOS and XCode version are you guys using?

Xcode Version 13.4.1
MacOS Monterey Version 12.4
I don't know if this helps but I am using Expo and EAS Build and Submit to submit builds to the app store. This is just the first spot I've been able to find where someone else is having the same issues as me.

Just to provide more info (although this seems to be an Apple issue), we are not using Expo. Also we didn't update/upgrade any package.

I'm also seeing this from Apple after a few lines of JS code changes.
Only notable change since last release is I've updated Xcode (I was on latest until new update).
MacOS Monterey Version 12.4 (21F79)
Xcode Version 13.4 (13F17a)
"react": "17.0.1",
"react-native": "0.64.3",
"expo": "^44.0.0",
"expo-dev-client": "~0.8.5",
"expo-app-loading": "~1.3.0",
"expo-apple-authentication": "~4.1.0",
"expo-application": "~4.0.1",
"expo-asset": "~8.4.6",
"expo-av": "~10.2.0",
"expo-blur": "~11.0.0",
"expo-camera": "~12.1.2",
"expo-cellular": "~4.1.0",
"expo-constants": "~13.0.1",
"expo-device": "~4.1.0",
"expo-facebook": "~12.1.0",
"expo-file-system": "~13.1.2",
"expo-font": "~10.0.4",
"expo-google-sign-in": "~10.1.0",
"expo-haptics": "~11.1.0",
"expo-image-manipulator": "~10.2.0",
"expo-image-picker": "~12.0.1",
"expo-keep-awake": "~10.0.1",
"expo-linear-gradient": "~11.0.0",
"expo-linking": "~3.0.0",
"expo-media-library": "~14.0.0",
"expo-navigation-bar": "~1.1.1",
"expo-network": "~4.1.0",
"expo-permissions": "~13.1.0",
"expo-secure-store": "~11.1.0",
"expo-splash-screen": "~0.14.1",
"expo-status-bar": "~1.2.0",
"expo-store-review": "~5.1.0",
"expo-system-ui": "~1.1.0",
"expo-updates": "~0.11.7",
"expo-web-browser": "~10.1.0",

yarn why expo-modules-autolinking
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "expo" depends on it
   - Hoisted from "expo#expo-modules-autolinking"
   - Hoisted from "expo-splash-screen#@expo#prebuild-config#expo-modules-autolinking"
info Disk size without dependencies: "948KB"
info Disk size with unique dependencies: "1.74MB"
info Disk size with transitive dependencies: "3.14MB"
info Number of shared dependencies: 30

Same issue here, I was able to build and submit yesterday without any issue and we only have some minor changes.

I'm also seeing this from Apple after a few lines of JS code changes.
Only notable change since last release is I've updated Xcode (I was on latest until new update).
MacOS Monterey Version 12.4 (21F79)
Xcode Version 13.4 (13F17a)

"react": "17.0.1",

"react-native": "0.64.3",

"expo": "^44.0.0",

"expo-dev-client": "~0.8.5",

"expo-app-loading": "~1.3.0",

"expo-apple-authentication": "~4.1.0",

"expo-application": "~4.0.1",

"expo-asset": "~8.4.6",

"expo-av": "~10.2.0",

"expo-blur": "~11.0.0",

"expo-camera": "~12.1.2",

"expo-cellular": "~4.1.0",

"expo-constants": "~13.0.1",

"expo-device": "~4.1.0",

"expo-facebook": "~12.1.0",

"expo-file-system": "~13.1.2",

"expo-font": "~10.0.4",

"expo-google-sign-in": "~10.1.0",

"expo-haptics": "~11.1.0",

"expo-image-manipulator": "~10.2.0",

"expo-image-picker": "~12.0.1",

"expo-keep-awake": "~10.0.1",

"expo-linear-gradient": "~11.0.0",

"expo-linking": "~3.0.0",

"expo-media-library": "~14.0.0",

"expo-navigation-bar": "~1.1.1",

"expo-network": "~4.1.0",

"expo-permissions": "~13.1.0",

"expo-secure-store": "~11.1.0",

"expo-splash-screen": "~0.14.1",

"expo-status-bar": "~1.2.0",

"expo-store-review": "~5.1.0",

"expo-system-ui": "~1.1.0",

"expo-updates": "~0.11.7",

"expo-web-browser": "~10.1.0",

yarn why expo-modules-autolinking

=> Found<EMAIL_ADDRESS>
info Reasons this module exists

   - "expo" depends on it

   - Hoisted from "expo#expo-modules-autolinking"

   - Hoisted from "expo-splash-screen#@expo#prebuild-config#expo-modules-autolinking"

info Disk size without dependencies: "948KB"

info Disk size with unique dependencies: "1.74MB"

info Disk size with transitive dependencies: "3.14MB"

info Number of shared dependencies: 30

Just tried again after updating Xcode to 13.4.1... no luck, same outcome.

Same here, just changed one line in my TS code and it is not working anymore, no Xcode updates, nothing!

As many others, the same thing is happening to us. No packages updated, just some minor javascript changes. Not using expo. We resolved the issue in debug mode by changing a few variable names but in release mode we are getting a notification about different ones and there are way more, doesn't seem feasible to manually change them all. Glad to find this thread, at least we're not alone! Seems like an Apple issue.

Experiencing the same with React Native and everything was working as of yesterday for us.

Same here, builds are not rolling out...

This may be due to apple updating their policy. Saw a comment that suggested needing to log in to your apple developer account (separate from app store connect) and agree to the updated policy. Apparently submissions will work after this? I'm testing this now.

"The issue has been resolved on the app validation backend. Please try resubmitting. Sorry for the trouble."
by Developer Tools Engineer https://developer.apple.com/forums/thread/127678?page=6

Hi,
Message from Apple: "The issue has been resolved on the app validation backend. Please try resubmitting. Sorry for the trouble."
Thanks.

I can verify that we're able to submit now (with the same code).

I can confirm too that the issue was resolved by Apple.

"The issue has been resolved on the app validation backend. Please try resubmitting. Sorry for the trouble." by Developer Tools Engineer https://developer.apple.com/forums/thread/127678?page=6

Thanks for the callout, @BennSandoval.
Tried uploading again and found success.

I solved it once, but the problem occurred again.
Is it just my problem?

I solved it once, but the problem occurred again. Is it just my problem?

Update the macOS to Mojave and Xcode to latest version.

This issue has not yet been resolved.
Many people seem to be able to fix it by changing the schema to a release, but it doesn't seem to work in my environment.
Is there any workaround for the issue where the release build doesn't work?
thank you.

Seeing the same issue as @Tak-As. Building a release scheme. Debug mode works just fine.

I can confirm too that the issue was resolved by Apple.

how did you solve it

I can confirm too that the issue was resolved by Apple.

how did you solve it

I didn't. It was an Apple issue, after a day it was sorted out and, without doing anything different, it worked.

Still an issue.
Even with blank new ejected Expo app.
I've logged a report here https://github.com/facebook/react-native/issues/34716

https://developer.apple.com/forums/thread/127678?page=6

Still getting the same issue in October

getting the same issue with newer version of Xcode 14

This issue has gone in many different directions (in some cases it's Apple's backend, in some it's Expo-related, etc etc) and there's no clear repro that pinpoints how this is a specific issue caused by react-native core itself.
I am closing this so if anyone has this issue with the latest version of react-native 0.70 (NOT EXPO) they can open a new issue with a clear, usable repro so that it can be investigated further.


the content don't display in Android,but it's good in IOS

"react-native": "0.55.4"
"react-native-scrollable-tab-view": "^0.8.0"
I try to add a carousel component above the react-native-scrollable-tab-view like this:

but the content of the tabs don't display anything in Android, in IOS is OK, can anyone help me?

Solve it! I add a height in the ScrollableTabView, then it works.


Add go binary scanning

Add go binary scanning extractor, and use it in image scanning.
This shows quite a few false positives that can be resolved with call analysis, which will be implemented in a followup PR.

Codecov Report
Attention: Patch coverage is 80.95238% with 12 lines in your changes are missing coverage. Please review.

Project coverage is 65.56%. Comparing base (d4657bf) to head (81616ce).

Files
Patch %
Lines

pkg/lockfile/go-binary.go
76.31%
4 Missing and 5 partials :warning:

internal/image/extractor.go
88.00%
2 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1011      +/-   ##
==========================================
+ Coverage   64.97%   65.56%   +0.59%
==========================================
  Files         149      150       +1
  Lines       12257     9566    -2691
==========================================
- Hits         7964     6272    -1692
+ Misses       3842     2836    -1006
- Partials      451      458       +7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[OPENJDK-2992] Spec for deployment and route object

JIRA: https://issues.redhat.com/browse/OPENJDK-2992
NOTE: My stage-2 is failing with CRI-O failed msg which is known one with our crc setup. I will have to restart or do a fresh setup to get it working fine :) Meanwhile I thought I can raise a PR so that you can take look and commented if its syntactically fine.
Could you please review the changes?

I've just tried this out.
the deployment object starts to log errors as soon as the template is instantiated, and before the builds have completed.
Once the builds have completed, the route is not yet working (Application is not available)
I'm creating a deployment manually now to compare the objects in the OCP instance

I think the route object needs .spec.port.targetPort: 8080-tcp added (possibly also via a template variable)

Work on this continues in #514.


[Backend Development with PHP]: Error Handling (#7175)

Description 📜
Added Documentation for Error Handling in PHP
Fixes #7175
Kindly review this PR @praveenscience

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Backend Dev (PHP)

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

/assign

@praveenscience Please review this PR


Configure dependabot updates : Create dependabot.yml

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 45.959%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
563

Relevant Lines:
1225

💛  - Coveralls


Added Code for Longest Common Subsequence

@shankhanil007  correct the conflict file and then again make pull request with issue number on description.
closing the pr.


CHANGELOG.MD and Minor Corrections - Fixes #211, #208

Pull Request (PR) description
This PR corrects the CHANGELOG.MD and also fixes some minor problems:

Corrected name of working path to remove x - fixes Issue #211.
Fix bug Find-Certificate when invalid certificate path is passed - fixes
Issue #208.

This Pull Request (PR) fixes the following issues

Fixes #208
Fixes #211

Task list

[x] Added an entry under the Unreleased section of the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in the resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

@johlju - would you mind reviewing this? It should be a quick one.

This change is

Codecov Report

Merging #212 into dev will not change coverage.
The diff coverage is 100%.

@@        Coverage Diff         @@
##           dev   #212   +/-   ##
==================================
  Coverage   89%    89%
==================================
  Files        7      7
  Lines      987    987
==================================
  Hits       881    881
  Misses     106    106


Add unstable Alpine build image variants

We currently provide stable (currently Go 1.20.x) and oldstable (currently Go 1.19.x) Alpine build images (x86, x64), but not unstable (currently 1.21.x).
These items need to be updated to provide this support:

README
Makefile
CI
Dependabot
Dockerfiles

See also:

https://github.com/atc0005/go-ci/issues/1044


feat(install): Camel K offline mode

Script used to create a maven offline bundle
Instructions how to setup Camel K offline on a disconnected cluster

Closes #4118

Release Note
feat(install): Camel K offline mode

@lburgazzoli wdyt?


feat: supporting sessions and removing support for expiring apps

Description

Supporting sessions
Removing support for expiring applications

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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


This is a good test！

Description

Motivation & Context

Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[ ] I have read the contributing guidelines
[ ] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-{your_pr_number}--twbs-bootstrap.netlify.app/

Related issues

@zhaoshun43 Please make your tests in your own repository 🙏


Moved home search listener from onResume to onActivityCreated

This avoids setting the listener every time onResume is called
which made the search really slow after many searches.

Fixes https://github.com/jkuester/unlauncher/issues/52

Thank you for the fix!  This is a good change.


Authentication information in proxy chain

I have searched through the documents and have read the  example. I still have questions about implementation details.
In above example, value chainedProxyCredentials is defined at a member level. My use case is I want to read the value by previous member in proxy chain.
My proxy allows many settings as part of proxy username. It will not force authentication if source ip address is whitelisted. However browsers like chrome will not send authentication information and will remove any authentication information. My goal is to force the authentication, get relevant information and then send headers to next proxy chain. However ProxyAuthenticator does not get any state nor do chain members.
How do I achieve this? Conceptually my code is working with hardcoded values, but I want to get dynamic values that I return when browser prompts me for proxy authentication. Even if we save authentication information and pass it along to next chain members, this will work.

@nhrdl FYI the development of LittleProxy was moved to https://github.com/LittleProxy/LittleProxy
P.S. But unfortunately I cannot answer your question. :)

Thank you for pointing to right location


Change SubWord selection to avoid selecting both sides of a dot "."

Requirements
Atom    : 1.23.1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0
Description of the Change
Atom's Subword (ctrl-left/right arrow) right now move to both sides of a dot. Here are examples of the current behavior.
Current Atom's subWord selection moving forward (the "|" represents the cursor):
|this.aMethod
this|.aMethod
this.|aMethod
this.a|Method
this.aMethod|
Current Atom's SubWord selection moving backwards (the "|" represents the cursor):
this.aMethod|
this.a|Method
this.|aMethod
this|.aMethod
|this.aMethod
Now the same example with the proposed behavior:
Proposed Atom's subWord selection moving forward (the "|" represents the cursor):
|this.aMethod
this|.aMethod
this.a|Method
this.aMethod|
Porpoised Atom's SubWord selection moving backwards (the "|" represents the cursor):
this.aMethod|
this.a|Method
this.|aMethod
|this.aMethod
As it can be seen, the proposed behavior only changes the dot "." selection, everything else remains the same.
Alternate Designs
Why Should This Be In Core?
The current behavior creates an unnecessary need for an extra input to move across  subwords.
The current behavior also repeats functionality since the same behavior can be obtained by using just left/right arrow. Example (the "|" represents the cursor):
If the cursor is at the left of a dot and we are moving forward, like shown:
this|.method
Then the input alt-right arrow would produce the same output as simply right arrow:
this.|method
This also happens when selecting text by using shit-alt-arrow.
Benefits
This changes makes moving trough subwords faster, but it also is a more natural way of doing it.
Possible Drawbacks
Some user may struggle to accommodate to this change at  first.
Applicable Issues
This issues asked for a change in behavior, however, this change does not supply every change requested in them.
https://github.com/atom/atom/issues/13651
https://github.com/atom/atom/issues/13953

Apologies for taking so long to look into this and thank you very much for the contribution.
The help-wanted issue specifically requests that new commands be implemented for this option, not to change the default behavior. Because of this, we won't be able to accept this PR. Thanks again for your submission.


Build from repository fails (for me) at autoreconf on OS X

OS X 10.10.3, automake 2.69 installed with Homebrew, sile as of ee1edbdcb53cd51e7c605caa9ef718f781fd293f (2015-05-12Z05:00).
autoreconf fails with lots of error messages when I run the following:
git clone https://github.com/simoncozens/sile.git
cd sile
autoreconf --version
sh -x ./bootstrap.sh

(See the output for details below.) The same command sequence works fine for me on Debian Jessie. Unfortunately I am devoid of any Automake knowledge. All I can imagine is a shell or m4 issue. The m4 is /usr/bin/m4, and Homebrew does not seem to offer m4.
: wrixum:0:.../ni/sw; git clone https://github.com/simoncozens/sile.git
Cloning into 'sile'...
remote: Counting objects: 4322, done.
remote: Compressing objects: 100% (135/135), done.
remote: Total 4322 (delta 78), reused 0 (delta 0), pack-reused 4187
Receiving objects: 100% (4322/4322), 21.38 MiB | 1.45 MiB/s, done.
Resolving deltas: 100% (2737/2737), done.
Checking connectivity... done.
: wrixum:0:.../ni/sw; cd sile
: wrixum:0:.../sw/sile; autoreconf --version
autoreconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.
: wrixum:0:.../sw/sile; sh -x ./bootstrap.sh
+ git submodule update --init --recursive --remote
Submodule 'libtexpdf' (https://github.com/simoncozens/libtexpdf.git) registered for path 'libtexpdf'
Cloning into 'libtexpdf'...
remote: Counting objects: 2653, done.
remote: Total 2653 (delta 0), reused 0 (delta 0), pack-reused 2653
Receiving objects: 100% (2653/2653), 2.44 MiB | 421.00 KiB/s, done.
Resolving deltas: 100% (2097/2097), done.
Checking connectivity... done.
Submodule path 'libtexpdf': checked out '933e0a6129360ddcb092b7777c26921d1d23c7ff'
+ autoreconf --install
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
Makefile.am:3:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
Makefile.am:3:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
Makefile.am:3:   If 'LT_INIT' is in 'configure.ac', make sure
Makefile.am:3:   its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1
+ cd libtexpdf
+ autoreconf -I m4
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2739: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2757: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:643: AS_IF is expanded from...
../../lib/autoconf/general.m4:2046: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2059: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/functions.m4:479: AC_FUNC_CLOSEDIR_VOID is expanded from...
m4/kpse-common.m4:264: KPSE_COMMON is expanded from...
configure.ac:16: the top level
Makefile.am:3: error: Libtool library used but 'LIBTOOL' is undefined
Makefile.am:3:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
Makefile.am:3:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
Makefile.am:3:   If 'LT_INIT' is in 'configure.ac', make sure
Makefile.am:3:   its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1
+ sed 's/rm -f core/rm -f/' configure
sed: configure: No such file or directory
+ mv config.cache configure
+ chmod +x configure
: wrixum:0:.../sw/sile; l
total 168
-rw-r--r--    1 ni  staff   1079 May 12 07:01 LICENSE
-rw-r--r--    1 ni  staff    184 May 12 07:01 Makefile.am
-rw-r--r--    1 ni  staff   1983 May 12 07:01 NEWS.md
-rw-r--r--    1 ni  staff   2942 May 12 07:01 README.md
-rw-r--r--    1 ni  staff    303 May 12 07:01 ROADMAP
-rw-r--r--    1 ni  staff  49941 May 12 07:01 aclocal.m4
drwxr-xr-x    7 ni  staff    238 May 12 07:01 autom4te.cache
-rwxr-xr-x    1 ni  staff    209 May 12 07:01 bootstrap.sh
drwxr-xr-x    7 ni  staff    238 May 12 07:01 classes
-rwxr-xr-x    1 ni  staff      0 May 12 07:02 configure
-rw-r--r--    1 ni  staff   3378 May 12 07:01 configure.ac
drwxr-xr-x   30 ni  staff   1020 May 12 07:01 core
drwxr-xr-x   10 ni  staff    340 May 12 07:01 documentation
drwxr-xr-x   40 ni  staff   1360 May 12 07:01 examples
drwxr-xr-x   59 ni  staff   2006 May 12 07:01 languages
drwxr-xr-x  138 ni  staff   4692 May 12 07:02 libtexpdf
drwxr-xr-x   13 ni  staff    442 May 12 07:01 lua-libraries
drwxr-xr-x    4 ni  staff    136 May 12 07:01 m4
drwxr-xr-x   35 ni  staff   1190 May 12 07:01 packages
-rwxr-xr-x    1 ni  staff   1206 May 12 07:01 sile.in
drwxr-xr-x    7 ni  staff    238 May 12 07:01 src
drwxr-xr-x   38 ni  staff   1292 May 12 07:01 tests
: wrixum:0:.../sw/sile;

You have basically the same setup as I do; but it looks like autoconf is picking up macros from strange place, and not picking up macros. Do you have autoconf 2.69 from homebrew as well as automake?

Yes, it is autoconf 2.69 and automake 1.15 (see below). Both versions seem to be current as trying brew upgrade on them shows. Both also seem to be the only installations AFAICS; I have removed previous Fink and MacPorts installations a long while ago.
If this is just due to a weirdness of my own installation, I'd be totally content with a WONTFIX WORKSFORME. I can build (actually, have built) and use the current SILE on the Debian box. That box is remote, but ssh/scp/rsync access is fast. And then there will be the 0.9.2 release. :–)
: wrixum:0:.../sw/sile; brew list autoconf
/usr/local/Cellar/autoconf/2.69/bin/autoconf
/usr/local/Cellar/autoconf/2.69/bin/autoheader
/usr/local/Cellar/autoconf/2.69/bin/autom4te
/usr/local/Cellar/autoconf/2.69/bin/autoreconf
/usr/local/Cellar/autoconf/2.69/bin/autoscan
/usr/local/Cellar/autoconf/2.69/bin/autoupdate
/usr/local/Cellar/autoconf/2.69/bin/ifnames
/usr/local/Cellar/autoconf/2.69/share/autoconf/ (42 files)
/usr/local/Cellar/autoconf/2.69/share/emacs/ (4 files)
/usr/local/Cellar/autoconf/2.69/share/info/autoconf.info
/usr/local/Cellar/autoconf/2.69/share/man/ (9 files)
: wrixum:0:.../sw/sile; brew list automake
/usr/local/Cellar/automake/1.15/bin/aclocal
/usr/local/Cellar/automake/1.15/bin/aclocal-1.15
/usr/local/Cellar/automake/1.15/bin/automake
/usr/local/Cellar/automake/1.15/bin/automake-1.15
/usr/local/Cellar/automake/1.15/share/aclocal/ (2 files)
/usr/local/Cellar/automake/1.15/share/aclocal-1.15/ (33 files)
/usr/local/Cellar/automake/1.15/share/automake-1.15/ (76 files)
/usr/local/Cellar/automake/1.15/share/doc/automake/amhello-1.0.tar.gz
/usr/local/Cellar/automake/1.15/share/info/ (4 files)
/usr/local/Cellar/automake/1.15/share/man/ (4 files)

Well, I know it works for me but that's no solution - it might be a weirdness of my own installation. :-) I'm going to set up a clean virtualbox OS X install and see if I can get it working on that.

OK, spinning up a clean VM and installing as per the instructions, I find:

I also need to install pkg-config
I need to set PKG_CONFIG_PATH appropriately: PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/lib

and then it configures properly. Try those two things, I'll update the documentation, and if it doesn't work for you - sorry, it probably is your system.

It doesn't indeed. Apparently I had pkg-config already installed —
: wrixum:0:.../Documents/dokomente; brew install pkg-config
Warning: pkg-config-0.28 already installed

— and I have changed bootstrap.sh to set PKG_CONFIG_PATH:
: wrixum:127:.../sw/sile; cat bootstrap.sh
#!/bin/sh
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/lib
export PKG_CONFIG_PATH
git submodule update --init --recursive --remote
autoreconf --install
(cd libtexpdf; autoreconf -I m4)
sed 's/rm -f core/rm -f/' configure > config.cache
mv config.cache configure
chmod +x configure

Still I get the same symptoms.
+ PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/lib
+ export PKG_CONFIG_PATH
+ git submodule update --init --recursive --remote
Submodule 'libtexpdf' (https://github.com/simoncozens/libtexpdf.git) registered for path 'libtexpdf'
Cloning into 'libtexpdf'...
remote: Counting objects: 2653, done.
remote: Total 2653 (delta 0), reused 0 (delta 0), pack-reused 2653
Receiving objects: 100% (2653/2653), 2.44 MiB | 595.00 KiB/s, done.
Resolving deltas: 100% (2097/2097), done.
Checking connectivity... done.
Submodule path 'libtexpdf': checked out '933e0a6129360ddcb092b7777c26921d1d23c7ff'
+ autoreconf --install
configure.ac:16: warning: AC_REQUIRE: `AC_HEADER_STDC' was expanded before it was required
configure.ac:16: http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
../../lib/autoconf/headers.m4:341: _AC_INCLUDES_DEFAULT_REQUIREMENTS is expanded from...
../../lib/autoconf/headers.m4:357: AC_INCLUDES_DEFAULT is expanded from...
../../lib/autoconf/lang.m4:225: AC_LANG_SOURCE is expanded from...
../../lib/autoconf/lang.m4:242: AC_LANG_PROGRAM is expanded from...
../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from...

and so on, as above.
If you say that is my system, that may well be. I will try to do a fresh installation with VirtualBox myself.

I have now done a fresh Yosemite installation in a VirtualBox VM and get the same errors. These are the full command histories of the two shells I used to set this up; except for the bootstrap.sh and some irrelevant things there were no errors in the output.
Am I doing something wrong?
 1  wget

(has no wget in the system)
 2  curl

(but has curl)
 3  ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
 4  brew install luarocks

(Didn't work)
 5  brew install lua
 6  git
 7  type git
 8  brew install harfbuzz

(Error due to missing XQuartz; installed XQuartz)
 9  ifconfig -a
10  brew install harfbuzz

(Oops, XQuartz installer was started, but not done.)
11  brew install harfbuzz
12  brew install lua
13  brew install luarocks

(Still doesn't work)
14  brew update

(Switched to other shell; ssh'ed into the VM works better than its slow graphics console)
 1  brew install luarocks

(Still doesn't work although it should, says the luarocks wiki)
 2  brew install wget
 3  wget http://keplerproject.github.io/luarocks/releases/luarocks-2.2.2.tar.gz
 4  l
 5  ls -al
 6  tar ztvf luarocks-2.2.2.tar.gz
 7  tar zxvf luarocks-2.2.2.tar.gz
 8  cd luarocks-2.2.2
 9  l
10  ;;

(oops)
11  ll
12  ls -al

(my ls aliases are not in this shell, darn)
13  ./configure
14  make build
15  make install
16  luarocks install lpeg
17  luarocks install luaexpat
18  luarocks install lgi
19  brew install pkg-config
20  git
21  git clone https://github.com/simoncozens/sile
22  l
23  ls
24  rm -rf sile

(that was the wrong place; actually mv would have sufficed)
25  cd
26  brew install autoconf
27  brew install automake
28  git clone https://github.com/simoncozens/sile
29  ls
30  cd sile
31  ls
32  sh -x ./bootstrap
33  sh -x ./bootstrap.sh

(once you do it right..., but still the errors)
34  ls -al
35  cd ..
36  rm -rf sile
37  git clone https://github.com/simoncozens/sile
38  cd sile
39  vi bootstrap.sh

(had forgotten the PKG_CONFIG_PATH)
40  sh -x ./bootstrap.sh

At this point (with the  it should work, but I still get the same errors and an empty configure script. Ist it my bad aura?
Anyway, if you don't see what is going wrong here, I don't really need to build from the repository, so I'll gladly wait for the next release and in between build a fresh one on Debian, if necessary. This yak has been getting bigger and bigger, and my motivation to pull this through has shrunk.

Closing, then. I've updated the documentation, and released versions don't need autotools, 0.9.3 will be out soon.

That is probably the right thing to do. While I'd love to sit down with you and check what we're doing differently setting up a clean VM for a build, I am afraid that is a bit on the impractical side, and not only because I am on vacation on Mallorca right now. ;–)
Regards, Juergen.

On 02 Jun 2015, at 12:52, Simon Cozens<EMAIL_ADDRESS>wrote:
Closing, then. I've updated the documentation, and released versions don't need autotools, 0.9.3 will be out soon.
—
Reply to this email directly or view it on GitHub.


[Breaking] Migrate to scala 3

CI has passed successfully 🥳 However I don't think CI builds for 3.2.0 yet 🥲
@judu Should I change the CI build versions?

As said on Slack, I had to duplicate a test suite for Scala 2 and Scala 3 because Circe doesn't give the same results in those two versions 🤦🏻♂
I'm marking this PR as ready, but we can fix the test issue before merging if you want.

(If someone else merges this PR: please squash merge)


Update resolve-path.js

This fixes issue 43 in regards to the explicit file name generation.

Thank you :+1:
Merged


Task was cancelled Exception when polling results

Since May 4th, we started to see exceptions below when retrieving/polling the bid results from the API, preventing us from making changes to the bid values. We provided the request log and the conclusion from Google support was it appears the job took 5 minutes and finished the same time you got your error, and we were advised to open an issue for the client specific library.
Can you tell us why the request would be cancelled? Below is the exception message:
[2022-05-10 09:33:21,395] INFO - java.util.concurrent.CancellationException: Task was cancelled.
[2022-05-10 09:33:21,395] INFO - 	at com.google.common.util.concurrent.AbstractFuture.cancellationExceptionWithCause(AbstractFuture.java:1496)
[2022-05-10 09:33:21,395] INFO - 	at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:586)
[2022-05-10 09:33:21,395] INFO - 	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:463)
[2022-05-10 09:33:21,395] INFO - 	at com.google.common.util.concurrent.FluentFuture$TrustedFuture.get(FluentFuture.java:100)
[2022-05-10 09:33:21,395] INFO - 	at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:73)
[2022-05-10 09:33:21,395] INFO - 	at com.google.api.gax.longrunning.OperationFutureImpl.get(OperationFutureImpl.java:133)

Hi Josh,
Confirming this was for batch job ID<PHONE_NUMBER>. The timeout we’re using for the OperationFuture.get(long, TimeUnit) call is 20 minutes and we were seeing the cancellation after about 3-5 minutes. We also checked and we are not calling OperationFuture.get() after closing the BatchJobServiceClient either implicitly or using try-with-resources block.
What were the dates that you had this issue that got fixed regarding the long running batch jobs?
Thanks,
Austin

Hi Austin,
Some users reported seeing issues starting on May 4, and the fix I mentioned went into place yesterday (May 11).
I suspect that your canceled job was a side effect of the issue that was fixed. Could you let me know if you're continuing to see this problem?
Thanks,
Josh

Hi Josh,
The timeline you mentioned lines up exactly with what we've seen on our side. The impacted period is between May 4th to 11th, after which we did see the issue go away.
What is the best way for us to get visibility into ongoing/open issues with Ads API/processing that may be affecting us?
Thanks for your help,
Austin

Hi Austin,
The first place to check is the status dashboard at https://ads.google.com/status/publisher/. In addition, depending on the type of issue, we may also publish to our developer's blog at https://ads-developers.googleblog.com/search/label/google_ads_api.
Finally, if you're encountering any unexpected behavior (regardless of the size of the issue), you can always reach out to us on our support forum at https://groups.google.com/forum/#!forum/adwords-api. That's the best choice if the issue you are seeing is not specific to the client library as well.
Thanks,
Josh, Google Ads API Team


fix: Intermittent failure on start of AccountCreationState

Description:
If the AccountCreationState begins, but the SDK is not yet connected to a healthy node, the local node would throw this error when starting up. We need to implement some sort of retry mechanism in case this issue happens.
This PR implements a retry mechanism to handle the scenario where the SDK is not connected to a healthy node at the start of the AccountCreationState. The retry mechanism will attempt to reconnect to a healthy node a specified number of times before failing.
Changes:

Retry Mechanism:

Added a new class RetryUtils.ts with a retryTask function to handle retry logic.
Configured the retry mechanism to execute the given task a specified number of times with a delay between attempts.

Integration with AccountCreationState:

Integrated the retry mechanism into the AccountCreationState to ensure it retries each call to the SDK for account creations

Related issue(s):
Fixes #733
Notes for reviewer:

The retry mechanism parameters (number of retries and delay) can be configured as needed.
This change improves the robustness of the startup process by handling transient connection issues gracefully.

Checklist

[x] Documented (Code comments, README, etc.)
[x] Tested (unit, integration, etc.)

[x] Added unit tests in RetryUtils.spec.ts to verify the retry logic.
[x] Updated AccountCreationState.spec.ts to test the retry mechanism integration.

Codecov Report
Attention: Patch coverage is 87.87879% with 4 lines in your changes missing coverage. Please review.

Project coverage is 57.59%. Comparing base (d34c153) to head (5a823ed).
Report is 83 commits behind head on main.

Files
Patch %
Lines

src/state/AccountCreationState.ts
86.66%
0 Missing and 2 partials :warning:

src/utils/RetryUtils.ts
88.23%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #734      +/-   ##
==========================================
+ Coverage   51.39%   57.59%   +6.19%
==========================================
  Files          24       30       +6
  Lines        1181     1403     +222
  Branches      136      173      +37
==========================================
+ Hits          607      808     +201
- Misses        550      574      +24
+ Partials       24       21       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


to_string is missing from the new version of xll

in the previous version you had xloper.h file with streaming operators and to_string.
Would you be willing to add it?

I could not find a way to make that round trip. Let me know if you figure out how to do that and I'll add it.


AttributeError: module 'torchmcubes_module' has no attribute 'mcubes_cuda'

(.venv) ➜  TripoSR git:(main) python run.py examples/chair.png --output-dir output/
2024-03-05 03:56:32,235 - INFO - Initializing model ...
/media/user/home/Tools/06_MachineLearning/24_3D/TripoSR/.venv/lib/python3.9/site-packages/transformers/utils/generic.py:441: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
  _torch_pytree._register_pytree_node(
/media/user/home/Tools/06_MachineLearning/24_3D/TripoSR/.venv/lib/python3.9/site-packages/transformers/utils/generic.py:309: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
  _torch_pytree._register_pytree_node(
2024-03-05 03:56:35,758 - INFO - Initializing model finished in 3523.10ms.
2024-03-05 03:56:35,758 - INFO - Processing images ...
2024-03-05 03:56:36,412 - INFO - Processing images finished in 654.22ms.
2024-03-05 03:56:36,412 - INFO - Running image 1/1 ...
2024-03-05 03:56:36,413 - INFO - Running model ...
2024-03-05 03:56:37,038 - INFO - Running model finished in 625.03ms.
2024-03-05 03:56:37,038 - INFO - Exporting mesh ...
Traceback (most recent call last):
  File "/media/user/home/Tools/06_MachineLearning/24_3D/TripoSR/run.py", line 154, in <module>
    meshes = model.extract_mesh(scene_codes)
  File "/media/user/home/Tools/06_MachineLearning/24_3D/TripoSR/tsr/system.py", line 185, in extract_mesh
    v_pos, t_pos_idx = self.isosurface_helper(-(density - threshold))
  File "/media/user/home/Tools/06_MachineLearning/24_3D/TripoSR/.venv/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/media/user/home/Tools/06_MachineLearning/24_3D/TripoSR/.venv/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1520, in _call_impl
    return forward_call(*args, **kwargs)
  File "/media/user/home/Tools/06_MachineLearning/24_3D/TripoSR/tsr/models/isosurface.py", line 45, in forward
    v_pos, t_pos_idx = self.mc_func(level.detach(), 0.0)
  File "/media/user/home/Tools/06_MachineLearning/24_3D/TripoSR/.venv/lib/python3.9/site-packages/torchmcubes/__init__.py", line 12, in marching_cubes
    return mc.mcubes_cuda(vol, thresh)
AttributeError: module 'torchmcubes_module' has no attribute 'mcubes_cuda'

This is from an virtualenv install for Python 3.9 on Ubuntu 20.04

no dice - I tried 3.8, 3.9 and 3.10 virtual environments

Seems the torchmcubes was not properly installed.
Could you check the torch version and run pip install git+https://github.com/tatsy/torchmcubes.git and try again?

pip install torch==2.2.1 --extra-index-url https://download.pytorch.org/whl/cu118

as per the Dockerfile on HF repo, and also;
TMPDIR=/media/user/home/tmp/ pip install  --cache-dir=/media/user/home/tmp/ torch  --extra-index-url https://download.pytorch.org/whl/cu121

I've given up, will probably need to run this in a Docker container to get it to work

https://huggingface.co/spaces/stabilityai/TripoSR/blob/main/Dockerfile

How to sovle it if I don't want to run in Docker?

Probably 'WITH_CUDA' is not defined https://github.com/tatsy/torchmcubes/blob/master/cxx/mcubes.cpp#L36

Please refer to this answer to fix this problem. Have fun playing with TripoSR!

https://huggingface.co/spaces/stabilityai/TripoSR/blob/main/Dockerfile

the dockerfile is 404,  could you please pull it out, THX

https://huggingface.co/spaces/stabilityai/TripoSR/blob/main/Dockerfile
@chrisbward
the dockerfile is 404, could you please pull it out, THX


[WIP] Support Raco User-defined Aggregates

[x] make map data structures compatible with Raco UDAs
[ ] unbreak MapReduce in CMakeLists
[ ] cleanup igor script for naivebayes (shouldn't be in here)

ping: this branch is active again...