Asus Users are not compatible

When will you update the Blocklauncher to be compatible with the Asus Devices?

I have an Asus and it works for me. I think you are referring to devices with Intel (x86) processor. In this case you need to install MCPE from google  play store, so you will install a "special" version for these devices. Most apks found on the internet are ARM and then not compatible with mods, if installed on x86 devices. (Or find a good friend who also has an x86 device and ask him to generate an apk for you)

Ok thanks...I bought MCPE on my other account, maybe I'll install it later and check if it works :D

Please close this if you are not sure.  You can always re-open this later on if you finally do test and find there is an issue.  I use this on x86 and arm without any issues (I use the Google Play Store version).  We do not want to take up more of @zhuowei 's time reading things that he could better spend on other issues.

Its not only on asus its on intel processators I have a acer Iconia One 7 and blocklauncher not works. But the 0.12.4 add support for intel. But the version 0.12.7 not works again


Scroll resistance between tableview and FlexibleHeightBar

Hi Bryan,
Is it possible to add a scroll resistance (rubber band effect) between the FelexibleHeightBar and the tableview? What I mean is the Bar should stays at the minimum height until the tableview is pulled down and top of the tableview reaches some distance from the bottom of the bar. Most of the pull to refresh libraries adds this type of effect.
I believe this feature is not the scope of this project but if you could include it or provide some guidance on implementing, it would be really helpful.
Thanks

That's a cool idea! You can definitely make something like that with a custom behavior definer. I had a little time so I put together a solution. The behavior is pretty similar to SquareCashStyleBehaviorDefiner, so I just subclassed that. My comments in the code should explain it.
RubberBandStyleBehaviorDefiner.h
#import "SquareCashStyleBehaviorDefiner.h"

@interface RubberBandStyleBehaviorDefiner : SquareCashStyleBehaviorDefiner

@end

and
RubberBandStyleBehaviorDefiner.m
#import "RubberBandStyleBehaviorDefiner.h"

#import "BLKFlexibleHeightBar.h"

@implementation RubberBandStyleBehaviorDefiner

- (void)scrollViewDidScroll:(UIScrollView *)scrollView
{
    // Behave like square cash whenever we're not already minimum height
    if(self.flexibleHeightBar.progress != 1.0)
    {
        [super scrollViewDidScroll:scrollView];
    }
}

- (void)scrollViewDidEndDragging:(UIScrollView *)scrollView willDecelerate:(BOOL)decelerate
{
    // Stretch scroll view by 100 pixels to snap it to maximum height
    if(scrollView.contentOffset.y < -scrollView.contentInset.top - 100.0)
    {
        [UIView animateWithDuration:0.2 animations:^{

            [self snapToProgress:0.0 scrollView:nil];

        }];
    }
    else
    {
        [super scrollViewDidEndDragging:scrollView willDecelerate:decelerate];
    }
}

@end

That's awesome. It works but still require some tweaks. I will try to sort it out and let you know soon.
Thanks.


Update maintaining.md

Add section on Handling Cask Update PRs and start a "Tips" section

Merged as d597b084987b68b710041636dea8b420473eaa8b.


run(): map error codes correctly

At the moment run() always returns EIO on any error.

Done in #38


RFC: cli-format

Provide a standard command line argument syntax for Pony tools and other programs, and a corresponding package named cli to be provided in the standard library.
https://github.com/ponylang/rfcs/blob/master/text/0038-cli-format.md

@Theodus its @cquinn who is working on this yes?
@cquinn can I add you as a contributor to this repo so you can be assigned to this issue and others in the future that you might start working on?

@SeanTAllen yes

Sure.

@cquinn invite sent. ping me here when you accept and we can add you as the assignee.

I have accepted.

PR is https://github.com/ponylang/ponyc/pull/1897


Seems to be a very old project file format - please open your project file in a more recent version of Xcode

New Issue Checklist

[ x] Updated fastlane to the latest version
[ x] I read the Contribution Guidelines
[ x] I read docs.fastlane.tools
[x ] I searched for existing GitHub issues

Issue Description
I am running fastlane in Github Actions (assisted by GameCI).
I am encoutering this issue trying to call update_code_signing_settings to sign the Pods.xcodeproj.
This happens trying to build a Unity game for iOS which uses Amplitude, which relies on cocoapods.
I saw similar issue here, but the workaround mentioned did not work for me:https://github.com/fastlane/fastlane/issues/20881
Command executed
  update_code_signing_settings(
    use_automatic_signing: false,
    team_id: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}_appstore_team-id"],
    code_sign_identity: 'iPhone Distribution',
    targets: ['Pods'],
    path: "#{ENV['IOS_BUILD_PATH']}/iOS/Pods/Pods.xcodeproj",
    profile_name: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}_appstore_profile-name"],
    profile_uuid: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}_appstore"]
  )

Complete output when running fastlane, including the stack trace and command used

 Agent pid 4722
Identity added: (stdin) ((stdin))
+---------------------------------------------------------+
|                      Used plugins                       |
+-------------------------------+---------+---------------+
| Plugin                        | Version | Action        |
+-------------------------------+---------+---------------+
| fastlane-plugin-github_action | 1.1.0   | github_action |
+-------------------------------+---------+---------------+
[20:57:17]: Sending anonymous analytics information
[20:57:17]: Learn more at https://docs.fastlane.tools/#metrics
[20:57:17]: No personal or sensitive data is sent.
[20:57:17]: You can disable this by adding opt_out_usage at the top of your Fastfile
[20:57:17]: Driving the lane 'ios beta' 🚀
[20:57:17]: -------------------------------
[20:57:17]: --- Step: update_info_plist ---
[20:57:17]: -------------------------------
[20:57:17]: Updated /Users/runner/work/FC-UI/FC-UI/build/iOS/iOS/Unity-iPhone.xcodeproj/../Info.plist 💾.
[20:57:17]: --------------------------------------
[20:57:17]: --- Step: Switch to ios build lane ---
[20:57:17]: --------------------------------------
[20:57:17]: Cruising over to lane 'ios build' 🚖
[20:57:17]: Podfile already present in the iOS build directory.
[20:57:17]: -----------------------
[20:57:17]: --- Step: cocoapods ---
[20:57:17]: -----------------------
[20:57:17]: $ cd '/Users/runner/work/FC-UI/FC-UI/build/iOS/iOS' && bundle exec pod install --clean-install
[20:57:18]: ▸ [!] The version of CocoaPods used to generate the lockfile (1.15.2) is higher than the version of the current executable (1.10.2). Incompatibility issues may arise.
[20:57:23]: ▸ Analyzing dependencies
[20:57:23]: ▸ Adding spec repo trunk with CDN https://cdn.cocoapods.org/
[20:57:23]: ▸ CocoaPods 1.15.0 is available.
[20:57:23]: ▸ To update use: gem install cocoapods
[20:57:23]: ▸ For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.15.0
[20:57:23]: ▸ Downloading dependencies
[20:57:23]: ▸ Generating Pods project
[20:57:23]: ▸ Integrating client project
[20:57:23]: ▸ [!] Please close any current Xcode sessions and use Unity-iPhone.xcworkspace for this project from now on.
[20:57:23]: ▸ Pod installation complete! There is 1 dependency from the Podfile and 2 total pods installed.
[20:57:23]: ----------------------
[20:57:23]: --- Step: setup_ci ---
[20:57:23]: ----------------------
[20:57:23]: Creating temporary keychain: "fastlane_tmp_keychain".
[20:57:23]: $ security list-keychains -d user
[20:57:23]: ▸ "/Users/runner/Library/Keychains/fastlane_tmp_keychain-db"
[20:57:23]: Found keychain '/Users/runner/Library/Keychains/fastlane_tmp_keychain-db' in list-keychains, adding to search list skipped
[20:57:23]: Enabling match readonly mode.
[20:57:23]: --------------------------------------------------
[20:57:23]: --- Step: Switch to ios sync_certificates lane ---
[20:57:23]: --------------------------------------------------
[20:57:23]: Cruising over to lane 'ios sync_certificates' 🚖
[20:57:23]: ---------------------------------------
[20:57:23]: --- Step: app_store_connect_api_key ---
[20:57:23]: ---------------------------------------
[20:57:24]: -------------------
[20:57:24]: --- Step: match ---
[20:57:24]: -------------------
+-------------------------------------------------------------------------------------------+
|                                 Summary for match 2.222.0                                 |
+----------------------------------------+--------------------------------------------------+
| type                                   | appstore                                         |
| storage_mode                           | git                                              |
| git_url                                | git@github.com:***.git                           |
| app_identifier                         | ["com.FCS.FC"]                             |
| readonly                               | false                                            |
| api_key                                | ********                                         |
| generate_apple_certs                   | true                                             |
| skip_provisioning_profiles             | false                                            |
| username                               | ***                                              |
| team_id                                | ***                                              |
| git_branch                             | master                                           |
| shallow_clone                          | false                                            |
| clone_branch_directly                  | false                                            |
| skip_google_cloud_account_confirmation | false                                            |
| s3_skip_encryption                     | false                                            |
| gitlab_host                            | https://gitlab.com                               |
| keychain_name                          | fastlane_tmp_keychain                            |
| force                                  | false                                            |
| force_for_new_devices                  | false                                            |
| include_mac_in_profiles                | false                                            |
| include_all_certificates               | false                                            |
| force_for_new_certificates             | false                                            |
| skip_confirmation                      | false                                            |
| safe_remove_certs                      | false                                            |
| skip_docs                              | false                                            |
| platform                               | ios                                              |
| derive_catalyst_app_identifier         | false                                            |
| fail_on_name_taken                     | false                                            |
| skip_certificate_matching              | false                                            |
| skip_set_partition_list                | false                                            |
| verbose                                | false                                            |
+----------------------------------------+--------------------------------------------------+
[20:57:24]: Cloning remote git repo...
[20:57:24]: If cloning the repo takes too long, you can use the clone_branch_directly option in match.
[20:57:25]: Checking out branch master...
[20:57:25]: 🔓  Successfully decrypted certificates repo
[20:57:25]: Verifying that the certificate and profile are still valid on the Dev Portal...
[20:57:25]: Creating authorization token for App Store Connect API
[20:57:26]: Installing certificate...
[20:57:26]: There are no local code signing identities found.
You can run security find-identity -v -p codesigning /Users/runner/Library/Keychains/fastlane_tmp_keychain-db to get this output.
This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774.
(Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)
[20:57:26]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
[20:57:26]: security: SecItemCopyMatching: The specified item could not be found in the keychain.
[20:57:26]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
+----------------------------------------------------------------------------+
|                           Installed Certificate                            |
+-------------------+--------------------------------------------------------+
| User ID           | ***                                                    |
| Common Name       | Apple Distribution: FC Studios Inc. (***)              |
| Organisation Unit | ***                                                    |
| Organisation      | FC Studios Inc.                                        |
| Country           | US                                                     |
| Start Datetime    | 2024-08-13 14:36:45 UTC                                |
| End Datetime      | 2025-08-13 14:36:44 UTC                                |
+-------------------+--------------------------------------------------------+
[20:57:27]: Installing provisioning profile...
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|                                                                                Installed Provisioning Profile                                                                                |
+---------------------+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+
| Parameter           | Environment Variable                                        | Value                                                                                |
+---------------------+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+
| App Identifier      |                                                             | com.FCS.FC                                                                                |
| Type                |                                                             | appstore                                                                                |
| Platform            |                                                             | ios                                                                                |
| Profile UUID        | sigh_com.FCS.FC_appstore                              | REDACTED                                                                          |
| Profile Name        | sigh_com.FCS.FC_appstore_profile-name                 | match AppStore com.FCS.FC                                                                               |
| Profile Path        | sigh_com.FCS.FC_appstore_profile-path                 | /Users/runner/Library/MobileDevice/Provisioning Profiles/REDACTED.mobileprovision |
| Development Team ID | sigh_com.FCS.FC_appstore_team-id                      | ***                                                                                |
| Certificate Name    | sigh_com.FCS.FC_appstore_certificate-name             | Apple Distribution: FC Studios Inc. (***)                                                                     |
+---------------------+-------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+
[20:57:27]: All required keys, certificates and provisioning profiles are installed 🙌
[20:57:27]: Setting Provisioning Profile type to 'app-store'
[20:57:27]: Cruising back to lane 'ios build' 🚘
[20:57:27]: ------------------------------------------
[20:57:27]: --- Step: update_code_signing_settings ---
[20:57:27]: ------------------------------------------
+---------------------------------------------------------------------------------------------------------+
|                                    Summary for code signing settings                                    |
+-----------------------+---------------------------------------------------------------------------------+
| use_automatic_signing | false                                                                           |
| team_id               | ***                                                                             |
| code_sign_identity    | iPhone Distribution                                                             |
| targets               | ["Unity-iPhone"]                                                                |
| path                  | /Users/runner/work/FC-UI/FC-UI/build/iOS/iOS/Unity-iPhone.xcodeproj             |
| profile_name          | match AppStore com.FCS.FC                                                 |
| profile_uuid          | REDACTED                                            |
+-----------------------+---------------------------------------------------------------------------------+
[20:57:27]: Updating the Automatic Codesigning flag to disabled for the given project '/Users/runner/work/FC-UI/FC-UI/build/iOS/iOS/Unity-iPhone.xcodeproj/project.pbxproj'
[20:57:27]: Set Team id to: *** for target: Unity-iPhone for build configuration: Release
[20:57:27]: Set Code Sign identity to: iPhone Distribution for target: Unity-iPhone for build configuration: Release
[20:57:27]: Set Provisioning Profile name to: match AppStore com.FCS.FC for target: Unity-iPhone for build configuration: Release
[20:57:27]: Set Provisioning Profile UUID to: REDACTED for target: Unity-iPhone for build configuration: Release
[20:57:27]: Set Team id to: *** for target: Unity-iPhone for build configuration: ReleaseForProfiling
[20:57:27]: Set Code Sign identity to: iPhone Distribution for target: Unity-iPhone for build configuration: ReleaseForProfiling
[20:57:27]: Set Provisioning Profile name to: match AppStore com.FCS.FC for target: Unity-iPhone for build configuration: ReleaseForProfiling
[20:57:27]: Set Provisioning Profile UUID to: REDACTED for target: Unity-iPhone for build configuration: ReleaseForProfiling
[20:57:27]: Set Team id to: *** for target: Unity-iPhone for build configuration: ReleaseForRunning
[20:57:27]: Set Code Sign identity to: iPhone Distribution for target: Unity-iPhone for build configuration: ReleaseForRunning
[20:57:27]: Set Provisioning Profile name to: match AppStore com.FCS.FC for target: Unity-iPhone for build configuration: ReleaseForRunning
[20:57:27]: Set Provisioning Profile UUID to: REDACTED for target: Unity-iPhone for build configuration: ReleaseForRunning
[20:57:27]: Set Team id to: *** for target: Unity-iPhone for build configuration: Debug
[20:57:27]: Set Code Sign identity to: iPhone Distribution for target: Unity-iPhone for build configuration: Debug
[20:57:27]: Set Provisioning Profile name to: match AppStore com.FCS.FC for target: Unity-iPhone for build configuration: Debug
[20:57:27]: Set Provisioning Profile UUID to: REDACTED for target: Unity-iPhone for build configuration: Debug
[20:57:27]: Skipping Unity-iPhone Tests not selected (Unity-iPhone)
[20:57:27]: Skipping UnityFramework not selected (Unity-iPhone)
[20:57:27]: Skipping GameAssembly not selected (Unity-iPhone)
[20:57:27]: Successfully updated project settings to use Code Sign Style = 'Manual'
[20:57:27]: Modified Targets:
[20:57:27]: 	 * Unity-iPhone
[20:57:27]: Modified Build Configurations:
[20:57:27]: 	 * Release
[20:57:27]: 	 * ReleaseForProfiling
[20:57:27]: 	 * ReleaseForRunning
[20:57:27]: 	 * Debug
[20:57:27]: ------------------------------------------
[20:57:27]: --- Step: update_code_signing_settings ---
[20:57:27]: ------------------------------------------
+------------------------------------------------------------------------------------------------------+
|                                  Summary for code signing settings                                   |
+-----------------------+------------------------------------------------------------------------------+
| use_automatic_signing | false                                                                        |
| team_id               | ***                                                                          |
| code_sign_identity    | iPhone Distribution                                                          |
| targets               | ["Pods"]                                                                     |
| path                  | /Users/runner/work/FC-UI/FC-UI/build/iOS/iOS/Pods/Pods.xcodeproj             |
| profile_name          | match AppStore com.FCS.FC                                            		  |
| profile_uuid          | REDACTED								                                      |
+-----------------------+------------------------------------------------------------------------------+
[20:57:27]: Updating the Automatic Codesigning flag to disabled for the given project '/Users/runner/work/FC-UI/FC-UI/build/iOS/iOS/Pods/Pods.xcodeproj/project.pbxproj'
+----------------------------------------------------------------------------------------------------------------------+
|                                                     Lane Context                                                     |
+------------------------------------+---------------------------------------------------------------------------------+
| PLATFORM_NAME                      | ios                                                                             |
| LANE_NAME                          | ios beta                                                                        |
| KEYCHAIN_PATH                      | ~/Library/Keychains/fastlane_tmp_keychain                                       |
| ORIGINAL_DEFAULT_KEYCHAIN          | "/Users/runner/Library/Keychains/login.keychain-db"                             |
| SIGH_PROFILE_TYPE                  | app-store                                                                       |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"com.FCS.FC"=>"match AppStore com.FCS.FC"}                         |
+------------------------------------+---------------------------------------------------------------------------------+
[20:57:27]: Called from Fastfile at line 83
[20:57:27]: [20:57:27]:     81:	 [20:57:27]:     82:	  # Update code signing settings for the Amplitude-Amplitude_Amplitude target in Pods.xcodeproj [20:57:27]:  => 83:	  update_code_signing_settings( [20:57:27]:     84:	    use_automatic_signing: false, [20:57:27]:     85:	    team_id: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}_appstore_team-id"], [20:57:27]:
[20:57:27]: Seems to be a very old project file format - please open your project file in a more recent version of Xcode
+-----------------------------------------------------------+
|                     fastlane summary                      |
+------+--------------------------------------+-------------+
| Step | Action                               | Time (in s) |
+------+--------------------------------------+-------------+
| 1    | update_info_plist                    | 0           |
| 2    | Switch to ios build lane             | 0           |
| 3    | cocoapods                            | 6           |
| 4    | setup_ci                             | 0           |
| 5    | Switch to ios sync_certificates lane | 0           |
| 6    | app_store_connect_api_key            | 0           |
| 7    | match                                | 3           |
| 8    | update_code_signing_settings         | 0           |
| 💥   | update_code_signing_settings         | 0           |
+------+--------------------------------------+-------------+
[20:57:27]: fastlane finished with errors
Error: Process completed with exit code 1.

Environment

 org, repo = (ENV["GITHUB_REPOSITORY"]||"").split("/")
match_org, match_repo = (ENV["MATCH_REPOSITORY"]||"").split("/")
platform :ios do
lane :init_ci do
github_action(
api_token: ENV["GH_PAT"],
org: org,
repo: repo,
match_org: match_org,
match_repo: match_repo,
writable_deploy_key: true
)
end
desc "Sync codesigning certificates"
lane :sync_certificates do
app_store_connect_api_key(
key_id: ENV["APPSTORE_KEY_ID"],
issuer_id: ENV["APPSTORE_ISSUER_ID"],
key_content: ENV['APPSTORE_P8']
)
match(
  type: "appstore",
  storage_mode: "git",
  git_url: "git@github.com:#{match_org}/#{match_repo}.git",
  app_identifier: ENV["IOS_BUNDLE_ID"],
  readonly: false # Change this to allow creating a new profile
)

end
desc "Deliver a new Release build to the App Store"
lane :release do
build
upload_to_app_store
end
desc "Deliver a new Beta build to Apple TestFlight"
lane :beta do
# Missing Export Compliance can also be set through Deliverfile
update_info_plist(
xcodeproj: "#{ENV['IOS_BUILD_PATH']}/iOS/Unity-iPhone.xcodeproj",
plist_path: 'Info.plist',
block: proc do |plist|
plist['ITSAppUsesNonExemptEncryption'] = false
end
)
build
upload_to_testflight(skip_waiting_for_build_processing: true)
end
desc "Create .ipa"
lane :build do
Check if the Podfile exists in the target directory, and copy if necessary
unless File.exist?("#{ENV['IOS_BUILD_PATH']}/iOS/Podfile")
sh "cp #{ENV['GITHUB_WORKSPACE']}/Podfile #{ENV['IOS_BUILD_PATH']}/iOS/"
UI.message "Podfile copied to iOS build directory in Fastfile."
else
UI.message "Podfile already present in the iOS build directory."
end
Run cocoapods installation with the Podfile
cocoapods(
clean_install: true,
podfile: "#{ENV['IOS_BUILD_PATH']}/iOS/Podfile"
)
setup_ci
sync_certificates
Update code signing settings for the Unity-iPhone target in Unity-iPhone.xcodeproj
update_code_signing_settings(
use_automatic_signing: false,
team_id: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}appstore_team-id"],
code_sign_identity: 'iPhone Distribution',
targets: ['Unity-iPhone'],
path: "#{ENV['IOS_BUILD_PATH']}/iOS/Unity-iPhone.xcodeproj",
profile_name: ENV["sigh#{ENV['IOS_BUNDLE_ID']}appstore_profile-name"],
profile_uuid: ENV["sigh#{ENV['IOS_BUNDLE_ID']}_appstore"]
)
Update code signing settings for the Amplitude-Amplitude_Amplitude target in Pods.xcodeproj
update_code_signing_settings(
use_automatic_signing: false,
team_id: ENV["sigh_#{ENV['IOS_BUNDLE_ID']}appstore_team-id"],
code_sign_identity: 'iPhone Distribution',
targets: ['Pods'],
path: "#{ENV['IOS_BUILD_PATH']}/iOS/Pods/Pods.xcodeproj",
profile_name: ENV["sigh#{ENV['IOS_BUNDLE_ID']}appstore_profile-name"],
profile_uuid: ENV["sigh#{ENV['IOS_BUNDLE_ID']}_appstore"]
)
build_app( #alias: gym
workspace: "#{ENV['IOS_BUILD_PATH']}/iOS/Unity-iPhone.xcworkspace",
scheme: 'Unity-iPhone',
xcargs: '-allowProvisioningUpdates IPHONEOS_DEPLOYMENT_TARGET=12.0' # Set the deployment target to 12.0
)
end
end

It looks like you're encountering an issue when trying to use update_code_signing_settings to sign Pods.xcodeproj in a Unity game build for iOS using Fastlane, within a GitHub Actions environment.
Here are some things to consider:
1. Ensure Correct Environment Variables:
Double-check the values for the environment variables:

sigh_#{ENV['IOS_BUNDLE_ID']}_appstore_team-id
sigh_#{ENV['IOS_BUNDLE_ID']}_appstore_profile-name
sigh_#{ENV['IOS_BUNDLE_ID']}_appstore

Ensure that these variables are correctly set, and their values match what is expected. You could add debugging output to ensure these values are being fetched correctly.
2. Correct Target Reference:
You mentioned targets: ['Pods']. Sometimes, the target name could vary depending on the setup. Ensure that the target name inside the Pods project matches "Pods" exactly, or try to reference it differently if needed.
3.  You may want to try running a dry run of the Fastlane lane locally to ensure there are no issues with your environment variables or setup.
4. Check Cocoapods Setup:
If Pods.xcodeproj is failing to sign, make sure your Podfile is correctly set up for iOS builds and that the necessary targets for Amplitude are correctly configured for code signing.
5. Fastlane Community:
Since you’ve referenced issue #20881, if the proposed workaround there didn’t work, try posting your issue with complete logs and setup details in the Fastlane GitHub community for further support. Other developers encountering the same problem might offer valuable insights.
Additional Suggestions:

Run fastlane update to ensure you have the latest Fastlane version.
Add verbose logging using --verbose to help track down more detailed output.
Try explicitly setting the provisioning profile and team in the Xcodeproj file directly rather than relying entirely on Fastlane automation.

Let me know if you need further assistance!
Official Website


Document compatibility with various object stores

In theory, pachyderm should work with any S3-compatible object store. In practice, however, some object store implementations have bugs/quirks that make them either hard or impossible to use with pach. As we work through setting up more object stores, it would be good if we started compiling a list of which versions/products are known to work, and config pitfalls we know how to overcome.
Object stores known to work via S3 compatibility layer:

Digital Ocean
IBM Cleversafe
Dell EMC ECS (only v3.3 and above due to #3443)
Minio
Ceph (I think? not actually 100% sure who is using this)
SwiftStack (there were some hoops to jump through to get this working: #3544)

Clarification -- these S3-compatible object stores are in addition to the three cloud object stores supported via their native APIs:

Amazon S3
Google Cloud Storage
Azure Storage

@pappasilenus is working on an "on prem" deployment doc that includes exactly this. Thanks for the issue and we'll make sure everything here gets covered.

@pappasilenus I can share my experience with zenko cloudserver deployed via its official helm chart.

@danielefranceschi that would be very helpful. Did it work completely? Any particular hoops/config/auth requirements to jump through?

that would be very helpful. Did it work completely? Any particular hoops/config/auth requirements to jump through?

I haven't encountered particular issues; the only boring thing is the requirement of https for connections from pachd to the S3 server (which IMO is annoying in a same-cluster in-house deployment), solved using a tls-enabled ingress with a valid star certificate:
helm install --namespace STORAGENS --name zenko
   --set localdata.persistentVolume.existingClaim=MYPVC
   --set api.ingress.enabled=true --set api.ingress.hosts="{\"S3.DOMAIN\"}"
   --set api.endpoint=S3.DOMAIN --set api.credentials.accessKey=ACCESSKEY
   --set api.credentials.secretKey=SECRETKEY stable/cloudserver

where MYPVC is a pvc bound to a pre-provisioned (large) PV and  S3.DOMAIN is a DNS alias pointing to the ingress node IP.
I created a bucket with
s3cmd --host=S3.DOMAIN --access_key=ACCESSKEY --secret-key=SECRETKEY
  --bucket-location=us-east-1 mb s3://BUCKETNAME

then I deployed Pachyderm with
pachctl deploy custom --etcd-storage-class=nfs --dynamic-etcd-nodes=1 --namespace=PACHNS
        --object-store s3 any-string 10 BUCKETNAME ACCESSKEY SECRETKEY S3.DOMAIN

Everything works well so far, IMHO better than Minio but with slightly greater resource requirements.
HTH

Thanks @danielefranceschi
You're right that _requiring_network-internal object stores use TLS seems a unnecessary if the transport is secured in other ways. I had thought there was a flag somewhere on the deployment to disable this requirement, but could be remembering.
@pappasilenus you were working on more comprehensive docs for on-prem clusters recently, right? Is this TLS-disabling flag something you came across?

Thanks, @danielefranceschi.  I can see having a requirement for TLS everywhere in some circumstances due to regulatory requirements or a security environment where internal threats are prioritized.   I think your solution would pass muster in those environments. Thanks, again!

Currently, any object store with an S3-compatible API should be working. We're not aware of any object stores which have recently caused any trouble. Some examples of S3-compatible object stores are referenced in the on-premises deployment documentation here. I'll go ahead and close out this issue and we'll open a new one if we encounter any object stores which need tuning or don't work.


Add Bilibili Video and Netease Music support

Add Bilibili Video and Netease Music connectors

First of all, sorry for the delay and thanks for your contribution.
Looks good to me except few places. I'll merge when you fix them.

Thanks for your advice and guidance. I fixed the problems you mentioned above, and added artistSelector in bilibili.js.


For loop fails as script but works in the REPL

What happened, and what did you expect to happen?
When running the following script using elvish script.elv fails with the following error Exception: exec: "str:trim": executable file not found in $PATH. However, copy-pasting each line in the REPL works as expected.
Script:
var lines = [one two three]
for line $lines { echo (str:trim $line ' ') }

Using Elvish 0.21.0
Output of "elvish -version"
0.21.0
Code of Conduct

[X] I agree to follow Elvish's Code of Conduct.

You have to include use str in your script.
You probably have that line in rc.elv, but elvish doesn't read the init files when executing a script. (To see what I mean, try your example in an interactive shell started as elvish -norc.)


[NO MERGE] Delete endpoints not used #3286

@Kartones can you please review? in the end, nothing to do with the related ticket, gonna rename the branch before merging.
Thanks!

Frontend tests were OK :+1: (details)

:+1:


Fixes Depreciated DropWizard Calls

The new version of DropWizard has changed the way the Environment class
works1. The correct syntax for setting environment for jersey is within the
   jersey().register()

method. Before, this was achieved with the
   addProvider

method. Sample DropWizard + Swagger fixed.
Signed-off-by: Adam Brenner<EMAIL_ADDRESS>

addressed in 1.5.x


nn.Conv2d and F.conv2d with groups == input_channels (DepthWise) generates PartitionedCall in tensorflow frozen_graph

When I define a define a model with DepthWise convolutions (groups == input_channels) the model is converted sucessfully but the tensorflow frozen_graph of this model cannot be converted to tensorflow.js. The problem is that keras.layers.Conv2D generates a PartitionedCall in the frozen_graph that cannot be converted to tensorflow.js.
I provide the python code to reproduce the problem:
import torch.nn as nn
import torch

from tensorflow.python.framework.convert_to_constants import convert_variables_to_constants_v2

import tensorflow as tf
import nobuco
from nobuco.commons import ChannelOrder, ChannelOrderingStrategy

class ExampleModel(nn.Module):
    def __init__(self,
                **kwargs):

        super(ExampleModel, self).__init__()
        self.layer1 = nn.Conv2d(16, 16, (3,3), (1,1), (0,0), (1,1), 16)
        self.layer2 = nn.ReLU()

    def forward(self, x):
        x = self.layer1(x)
        x = self.layer2(x)
        return x

model = ExampleModel()

# Put model in inference mode
model.eval()

x = torch.randn(1, 16, 113, 113, requires_grad=False)

keras_model = nobuco.pytorch_to_keras(
    model,
    args=[x], kwargs=None)

# Assuming 'model' is your Keras model
full_model = tf.function(lambda x: keras_model(x))
full_model = full_model.get_concrete_function(
    tf.TensorSpec(keras_model.inputs[0].shape, keras_model.inputs[0].dtype))

# Convert Keras model to frozen ConcreteFunction
frozen_func = convert_variables_to_constants_v2(full_model)
frozen_func.graph.as_graph_def()

# Print the input and output tensors
print("Frozen model inputs: ", frozen_func.inputs)
print("Frozen model outputs: ", frozen_func.outputs)

# Save frozen graph to disk
tf.io.write_graph(graph_or_graph_def=frozen_func.graph,
                logdir='.',
                name='ExampleModel.pb',
                as_text=False)

Inspecting the ExampleModel.pb with Netron this is what happens:

In order to fix this error, I made a custom nn.Conv2d converter:
@nobuco.converter(nn.Conv2d)
def converter_Conv2d(self, input: Tensor):
    weight = self.weight
    bias = self.bias
    groups = self.groups
    padding = self.padding
    stride = self.stride
    dilation = self.dilation

    out_filters, in_filters, kh, kw = weight.shape

    weights = weight.cpu().detach().numpy()

    if groups == 1:
        weights = tf.transpose(weights, (2, 3, 1, 0))
    else:
        weights = tf.transpose(weights, (2, 3, 0, 1))

    if bias is not None:
        biases = bias.cpu().detach().numpy()
        params = [weights, biases]
        use_bias = True
    else:
        params = [weights]
        use_bias = False

    if isinstance(dilation, numbers.Number):
        dilation = (dilation, dilation)

    if isinstance(padding, numbers.Number):
        padding = (padding, padding)

    pad_str = 'valid'
    pad_layer = None

    if padding == 'same':
        pad_str = 'same'
    elif padding != (0, 0):
        pad_layer = keras.layers.ZeroPadding2D(padding)

    if groups == 1:
        conv = keras.layers.Conv2D(filters=out_filters,
                                kernel_size=(kh, kw),
                                strides=stride,
                                padding=pad_str,
                                dilation_rate=dilation,
                                groups=groups,
                                use_bias=use_bias,
                                weights=params
                                )
    else:
        conv = keras.layers.DepthwiseConv2D(
                    kernel_size=(kh, kw),
                    strides=stride,
                    padding=pad_str,
                    use_bias=use_bias,
                    activation=None,
                    depth_multiplier=1,
                    weights=params,
                    dilation_rate=dilation,
                )

    def func(input):
        if pad_layer is not None:
            input = pad_layer(input)
        output = conv(input)
        return output
    return func

But I think that probably is better to fix this in the source code.

Hey, thanks for bringing this up! I fixed what I could in v0.12.2, but there are still problems with TFJS. It only works when groups == 1 or  groups == in_channels. As a last resort, you can always express grouped convolution as normal one, missing out on efficiency. In fact, that's how ConvTranspose1d/ConvTranspose2d are converted, Tensorflow just completely botched it: https://github.com/tensorflow/tensorflow/issues/45216.


Remove/replace featured photo from project page

I would like to modify the projects widget to display the featured.jpg photo on the preview but then remove it from the actual project webpage (or replace it with a new photo). How can I do that?

duplicate #728
A temporary (and dirty) fix is to copy page_header.html from theme/academic/layout/project into your own copy of /layout/partials/, and comment lines 57-62:

But I agree, adding an option for no or another image would be great!

Same with blog posts.

Hmm... The temporary "fix" didn't seem to work for me.

I was able to get rid of the banner by commenting out lines 34-37
``

Closing as this is a duplicate


Use as default system font

Hi minjiaesong,
I love your font and want to use it as my system font. How can I do it?

Unfortunately system fonts are not my forte. What I’ve heard is you should create bitmap font files such as .fnt, if someone can make such files, they can just copy-paste my bitmaps. For .ttf and .otf I have no idea.


Duplicate folders in .code-workspace

testing https://github.com/Microsoft/vscode/issues/30722
Insiders 1.15.0
9a308d11
Loading of folders stops if a folder is repeated in the .code-workspace file. admittedly a poorly formed file :)
loading foo.code-workspace
{
	"id": "1500494428473",
	"folders": [
		"file:///Users/chris/src/vscode-mongodb",
		"file:///Users/chris/src/vscode-docker",
		"file:///Users/chris/src/vscode-docker",
		"file:///Users/chris/src/vscode-azurelogin",
		"file:///Users/chris/src/vscode-azureappservice",
		"file:///Users/chris/src/vscode-extension-samples"
	]
}

results in only the vscode-mongodb and vscode-docker folders being loaded.

i would expect it to keep on loading the rest of the folders in this case since the vscode-docker folder is valid, you just don't have to load it 2x.

@sandy081 this should be de-duplicated on the level of the workspace service imho within the workbench.

Hmm strange.. will look into it.


Change global namespace to METEORIC

This is a good idea while there are still small user base.

I'm just gonna follow the ionic's way and just have it as all lowercase, e.g. "meteoric". @see #51


csrf: delete cookies instead of categorically denying

We mostly only care about CSRF in the presence of cookies.  Instead of denying all cross-site requests, this deletes the cookies on cross-site requests.

Cookies are all we're worried about because they're automatic, and it allows drive-by requests like  to work.

Basic & Digest authentication are also automatic: after logging in, the browser will automatically send the appropriate Authorization header each time.
So if this PR allows any type of Authorization through a cross-site request, and if we now or in the future make use of Basic or Digest authentication, then we will silently be subject to CSRF attacks.
Do notebooks use Basic or Digest, or do they use Bearer or our own scheme? If the latter, can this PR be changed to forbid the former?


Problem with Genart Review Tool

Describe the issue
I am trying to complete a review I was assigned, for draft-ietf-lsr-ospf-l2bundles.
I already emailed the review to genart. On the Complete review page I have already successfully searched for that email. It offers me:
Select one of the following messages to automatically pre-fill link and content:
followed by the subject, date, and sender of the message. But it won't allow me to select it.
This is new behavior since the last time I submitted a review. (Just a couple of days ago for artart.)
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

Never mind.


Create and Publish as a Package

https://julialang.org/contribute/developing_package/

https://github.com/JuliaRegistries/General/pull/91540

Click on the "install" button above to add the registration bot to your repository
Set the (Julia)Project.toml version field in your repository to your new desired version.
Comment @JuliaRegistrator register on the commit/branch you want to register (e.g. like https://github.com/JuliaRegistries/Registrator.jl/issues/61#issuecomment-483486641 or here).
If something is incorrect, adjust, and redo step 2.
If the automatic tests pass, but a moderator makes suggestions (e.g., manually updating your (Julia)Project.toml to include a [compat] section with version requirements for dependencies), then incorporate suggestions as you see fit into a new commit, and redo step 2 for the new commit. You don't need to do anything to close out the old request.

Registration pull request updated: JuliaRegistries/General/91540
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 7e167ff602a9f55dc2c92cf83f96a79a18ec28c3
git push origin v1.0.0

Registration pull request updated: JuliaRegistries/General/91540
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 7e167ff602a9f55dc2c92cf83f96a79a18ec28c3
git push origin v1.0.0

Lowercase package name juliaobjectsystem contains the string "julia".
Repo URL does not end with /name.jl.git, where name is the package name
There is no compat entry for julia.
The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: Suppressor
No licenses detected in the package's top-level folder. An OSI-approved license is required.

https://github.com/JuliaRegistries/General/pull/91575

https://github.com/JuliaRegistries/General/pull/91589

@EdBarrancos I'm very intrigued about your package.
Seeing an open pending registration and this issue, I thought it had not gone through and you had a change to become package 10,000, but actually your package is merged so you could close all registration PRs and this issue.
Your package seems well documented; also this one:
https://github.com/Suzhou-Tongyuan/ObjectOriented.jl
Did you know about that one?
https://github.com/JuliaRegistries/General/pull/91589

Hey @PallHaraldsson
I forgot to close this issue XD
I did not know about it previously, but after I finished I found about it. It is an interesting one, I think we take two different approaches to solve the same problem

I know of Smalltalk, and its claim to first object-oriented (or first to use that term, actually Simula earlier). Ok to use that term it for this, ans Smalltalk-like? But since there are two Julia packages (and more relating to...), and regrettable that you didn't know of the other, in case to similar (or good to have both types?):
I propose you (or I) get it documented in JuliaLang's docs. So people may know of, and at least not reimplement either (or a 3rd option?).
I suggest something like "Julia is object-oriented, but based on composition, not inheritance of implementation, not implementing classes or multiple inheritance. Two systems add such features. The package ObjectOriented.jl implementing Python's way of object orientation, and ObjectSystem.jl supporting meta-classes, like Smalltalk, the first object-oriented language, or actually in a way more similar to as done for Common Lisp (i.e. with CLOS) and Dylan languages." And link to your docs. [You have at least on typo there.]
You mention Python, but I guess no need to mention, since you don't implement they're way fully. You mention an extension, would it then be?


HTTPS proxying does not work.

Hi, this may be related to issue 152.
Also I have been sent here from npm as I originally filed an issue (https://github.com/isaacs/npm/issues/2026) there (as npm uses this module as http client). Now for the details :)
We have a working HTTP/HTTPS Squid 2.6 proxy. It appears (through a tcpdump) that when npm is attempting to contact the registry over https, it doesn't connect to the proxy using the CONNECT method, sending instead directly encrypted content, thus failing to open the connection, while our proxy only works this way (as described in http://wiki.squid-cache.org/Features/HTTPS, using eg. curl as https client)
Currently we use the http registry as a workaround, but how to get npm to use CONNECT?
OS is CentOS 5.7 i386.
$ npm -v
1.1.0-alpha-6
$ npm list -g
/usr/lib
└─┬<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>$ node -v
v0.6.5

I get a 501 response using Google Plus or Facebook API. Any temporal solution?

Closing until 0.8 ships, it has the SSL support we need.


Port SqsTest to new SQS implementation.

I see tests are failing due to some region configuration - other than that LGTM.


Button edit error

Issue : Properties not filled in button edit option as shown in image given below.

Fix issue


pkg/unittest: capture all errors and categorize them

There is a weak notion of errors in unittest at the moment.
Only one error is recorded. If an error happens 'in line' and then another happen async, only one set of details is recorded.
These should be categorized as well, so async errors during the test run are distinguishable from in-line errors in tearDown

This issue has been moved to dart-lang/test#240.


Fix/component context

closing this now, the work have been ported over to small PRs which have been merged:
#1693 #1695 #1705


Confidence of predictions

Dear authors,
Congratulations on this amazing and promising software. It's of great value for the scientific community.
I'm testing on my data the unsupervised model with SCANVI. I was looking at the documentation, tutorials and issues but I'm unable to find if the models give a measure for the confidence of the predictions.
Thanks and best,
Juanlu.

I just found it in the documentation. Sorry for the bother

I just found it in the documentation. Sorry for the bother


fix(rpc-triple): Fix missing error code

What is the purpose of the change
Fix ci execution failed duo to missing error code
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (976516c) 40.69% compared to head (147fa39) 40.71%.
Report is 6 commits behind head on 3.3.

Additional details and impacted files
@@            Coverage Diff             @@
##              3.3   #13379      +/-   ##
==========================================
+ Coverage   40.69%   40.71%   +0.02%
==========================================
  Files        1805     1806       +1
  Lines       75789    75807      +18
  Branches    10630    10637       +7
==========================================
+ Hits        30844    30868      +24
+ Misses      40640    40627      -13
- Partials     4305     4312       +7

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


Python README.md Re-Structured

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
As assigned by @shraddhavp for issue #1610, I have carefully restructured the Python README.md  file. All the Algorithms inside the Python folder are distinctly mentioned.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#1610
I request @shraddhavp @iamrajiv @HarshCasper to review this PR. Thank You 👍

@atarax665 as you requested, I have relocated the Chinese Remainder Theorem form others to math folder. In doing so I have also done the following addition:

Added description of the Chinese Remainder Theorem and the Problem Statement
Function names modified to specify their usage and comments added
Time/Space Complexity  included

I hope you appreciate the changes made by me. Thank You 👍


API Health Endpoint Implementation - GET - /api/health

Description
As a user of the currency converter API, I would like to have a /api/health endpoint added to the API so that I can easily check the health and status of the API. Additionally, I request configuration for logger and a Postman collection for testing purposes.
Acceptance Criteria

[ ] A /api/health endpoint is added to the currency converter API.
[ ] The health check endpoint returns a status indicating the health of the API.
[ ] The endpoint response includes relevant information such as server uptime, database status, etc.
[ ] Logger is configured to log relevant information for the health check endpoint.
[ ] Postman collection is provided for testing the /api/health endpoint.

Additional Information
Currently, there's no straightforward way to check the health of the currency converter API. Having a dedicated health check endpoint will greatly improve the observability and reliability of the API, allowing users to quickly determine if the API is functioning properly or if there are any issues that need to be addressed.
Configuring a logger will ensure that relevant information about the health check endpoint is logged, aiding in debugging and monitoring.
A Postman collection will provide a convenient way for users to test the /api/health endpoint and verify its functionality.
The currency converter API is built using Spring Boot, and the source code is available in the following GitHub repository: Currency Converter API GitHub Repository

I'll be working on this issue.


Pin setuptools so that we can run DETR model on GPU on Linux.

You may need to run the poetry-lock-all script here


[Bug]: UZB Stick hangging

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Z-Wave JS UI version
<IP_ADDRESS>d0208
ZwaveJS version
10.3.0
Describe the bug
System works perfectly after a reboot. Always after different times (sometimes only 2minutes or 5minutes) my blue LED on the Zwave Stick (UZB) lights up permanently and all battery powered devices show ES.
Only after a reboot the stack works for maybe 5 minutes.
To Reproduce

Expected behavior

Additional context
No response

I think it's because when I wake up a battery device. A short time later the stick then hangs. Does one have an idea?

Please attach zwave-js driver logs


Log aggregation

Aggregation and parsing of the backend microservice logs would make it easier for developers and sysadmins to troubleshoot errors.
The buzzword "Kibana" should be a good starting point to research.
Prereqs:
Backend service such as django (chris), celery (chris_worker and worker_periodic),  pman, and pfcon do logging all in different ways.

[ ] https://github.com/FNNDSC/pfcon/issues/132
[ ] https://github.com/FNNDSC/pman/issues/213
[ ] https://github.com/FNNDSC/ChRIS_ultron_backEnd/issues/443

@jennydaman I'm trying to research this and let's see if I can get anywhere near. I will ping you with any updates:crossed_fingers:

@jennydaman I have progressive research on Kibana, we can use Elasticsearch to search logs and Kibana to visualize our logs.
I will try to come up with an example

@jennydaman I have made progressive research on Kibana, we can use Elasticsearch to search logs and Kibana to visualize our logs.
I will try to come up with an example

You first need a log aggregator something like fluentd or loki before you can go ahead & dump the logs to Kibana instance which is then picked up the elasticsearch to index & query them.

@sakshi1215 you're right, it is commented out here

@sakshi1215 you're right, it is commented out here

That is a very naive installation of only the docker image, we need to make sure of the scrape targets before we can actually start utilising any log aggregator.

Hi @jennydaman, could you assign this issue to me and give me an insight into what should be done?
Thank you.
From my understanding, the last task is to see your output while running which is the log instead of getting the output in a file.

@Zainab-ik thanks for your interest in this issue! This is not a simple feature, I would suggest you have a strong background with containers and docker-compose.
First, some background: the "ChRIS backend" is not a single server, but rather a set of services and microservices, which may even be deployed on different clouds. These services include CUBE, celery, rabbitmq, PostgreSQL, pfcon, pman, just to name a few. This fragmentation has its advantages, such as being able to scale or upgrade components individually, however there is a problem: let's say you encounter an error, how do you trace it to find its cause? You'll have to check the container logs for each service individually.
To organize this increasingly complicated mess, in this issue I am proposing we use the "ELK stack" to provide log aggregation. ELK stands for ElasticSearch, LogStash, and Kibana. We can use these services to provide a friendly user interface to browsing and searching the logs from all of the ChRIS backend services at once.

A solution to this issue would be to add services to docker-compose.yml and configuration files to this repository which configure ELK (or the OpenSearch forks) to do log aggregation of the ChRIS backend services.

@Zainab-ik thanks for your interest in this issue! This is not a simple feature, I would suggest you have a strong background with containers and docker-compose.
First, some background: the "ChRIS backend" is not a single server, but rather a set of services and microservices, which may even be deployed on different clouds. These services include CUBE, celery, rabbitmq, PostgreSQL, pfcon, pman, just to name a few. This fragmentation has its advantages, such as being able to scale or upgrade components individually, however there is a problem: let's say you encounter an error, how do you trace it to find its cause? You'll have to check the container logs for each service individually.
To organize this increasingly complicated mess, in this issue I am proposing we use the "ELK stack" to provide log aggregation. ELK stands for ElasticSearch, LogStash, and Kibana. We can use these services to provide a friendly user interface to browsing and searching the logs from all of the ChRIS backend services at once.

@jennydaman, Thanks. I have a basic understanding and containers and dockers. So I'd like to give it a try.

A solution to this issue would be to add services to docker-compose.yml and configuration files to this repository which configure ELK (or the OpenSearch forks) to do log aggregation of the ChRIS backend services.

@jennydaman, I'd do research about this and update you.


[DOC] Add a supported table format

Why are the changes needed?

Brief change log

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

LGTM


derive(Event) option to use single buffering

What problem does this solve or what need does it fill?
For some types of events, like an UpdatePosition event, data that is one frame/tick behind might be useless. Having the option to disable double buffering and use single buffering per event type could be a nice performance improvement.
What solution would you like?
#[derive(Event)]
#[event(buffer = "single")]
struct PositionEvent {
    x: i32,
    y: i32,
    z: i32,
}

What alternative(s) have you considered?
Continue to use double buffering.

Related issue: #2071
Related PRs: #7957 and #2073
Note this issue unlike #2071 is specifically about the buffering aspect, not the data type used to store them.

I would also really like to see buffer = "manual", ideally as part of the same PR.


Update image_processing.py

Fix AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS' Image.ANTIALIAS was deprecated and finally removed in Pillow 10.

Dupe


FP1<void,M2MExecuteParameter*> execute_callback;

The signature of
typedef FP1<void,void*> execute_callback;
should not use void*, but a M2MExecuteParameter. Lately this was silently changed from coap_header_t to M2MExecuteParameter and that change wasn't noticed by the compiler breaking our LWM2M resources for Execute.

Hi,
Was the coap_header_t your own implementation, because we introduced M2MExecuteParameter some time back, before that it was just void*  . The idea was not to break the API signature, you might have used it to map it for your own defined structure but you can now move to M2MExecuteParameters

Yes, this was our extension and I accidentally put this in the issue description.
With the change you were breaking existing objects, then it's better to change the API rather than silently break, or?

Yes , thats a good point. It didnt break anything on our end but yes application building their own logic would have impact. We will ensure that future updates will result in major API version change, if it breaks anything on application side as well.

ARM Internal Ref: IOTCLT-830


Clarify documentation regarding moment injection

Current documentation makes it extremely unclear that while you do inject "angularMoment" into your module, you do not inject it where you intend to use it (e. g. service or controller), you inject "moment" instead.
The only place where I found that mentioned was https://github.com/urish/angular-moment/issues/236 , while it should definitely be mentioned loud and clear in the main documentation in example part. :)

Created a PR for this =)
Thanks for the link to the other issue


Change pairing mode sony headphone

Is there any way to activate pairing mode on Sony headphones using code commands? The touch function on my headphones is broken, and I can't connect to new devices.
Thank you!

which model of headphones do you own? I'm pretty sure my WH-1000XM4s can be done this way, but most headphones have a way to enter pairing modes with the physical buttons. Just need to look in the manuals.

I use sony WF-1000XM3. My touch button to activate pairing mode is broken. Can you tell me how to use the code to activate this mode? Thank you

This code atm doesn't do anything related to multipoint, so it is of no use to you. My PR does include some features of multipoint but not the new pairing feature. I do plan to add it sometime in the future, but right now I am too busy to do it.
Btw, which devices have you got paired with your earphones right now?

@aybruh00  I have currently connected it to a desktop computer and an iPhone. I want to activate the connection mode to connect it to a laptop. Can you guide me? I will study it.

If you want to program it yourself, I would suggest cloning my repository, as it has a bunch of additional stuff that would make adding the function easier.
The problem lies in figuring out what message to send to the headset. For that you would need to somehow see what messages the app sends when you do an action. I am on android, so I can dump my bluetooth snoop logs, but I have no absolutely no idea how to do this on IOS.

@aybruh00 Thanks for your help. Hope you have time to develop this feature.


feat: 🎸 utils function and basic test

It's better add some lint , format config to unifiy contributor‘s  code style

Thanks for your contribution, this is a nice ux improve!
Also need to handle monorepo, I will check how to change.

I tried to add rename, but it was difficult to read. I'm searching a more readable way to write test code.


Update redis.md

The helm command that includes --name is no longer valid.  I've update the command to reflect the current syntax.
Description
The previous helm command "helm install --name redis stable/redis" results in an error "Error: unknown flag: --name"
I've corrected the command to "helm install redis stable/redis" for helm v3.0.1
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

@paulgyro Sorry that your change was included in https://github.com/dapr/docs/pull/307
I'm closing this.


Comment out unused code and increase code coverage

Codecov Report

Merging #116 (4442070) into master (7db5b80) will increase coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #116      +/-   ##
==========================================
+ Coverage   73.87%   74.25%   +0.38%
==========================================
  Files         117      117
  Lines       34050    33997      -53
==========================================
+ Hits        25153    25244      +91
+ Misses       8897     8753     -144

Impacted Files
Coverage Δ

dynadjust/dynadjust/dnareftran/dnareftran.cpp
85.78% <ø> (+8.73%)
:arrow_up:

dynadjust/dynadjust/dnareftran/dnareftran.hpp
100.00% <ø> (ø)

.../dynadjust/dnareftranwrapper/dnareftranwrapper.cpp
77.96% <ø> (+10.34%)
:arrow_up:

dynadjust/dynadjust/dnaadjust/dnaadjust.cpp
86.85% <0.00%> (-0.02%)
:arrow_down:

dynadjust/include/functions/dnatransparamfuncs.hpp
17.25% <0.00%> (+0.27%)
:arrow_up:

dynadjust/include/config/dnaprojectfile.cpp
69.01% <0.00%> (+1.86%)
:arrow_up:

dynadjust/include/parameters/dnaepsg.hpp
44.66% <0.00%> (+1.94%)
:arrow_up:

dynadjust/include/io/dnaiodna.cpp
57.31% <0.00%> (+4.87%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7db5b80...4442070. Read the comment docs.


feat(client/sse): add {EventSource,Request}Init options param

Motivation and Context
This enables users of the SSE client to optionally send cookie-based credentials to the event source MCP server using EventSourceInit 1 & set outgoing request headers for the POST call using RequestInit 2.
How Has This Been Tested?
I ran through npm test; if there's interest in this I'll add some additional tests and make sure the change integrates cleanly with @modelcontextprotocol/inspector
Breaking Changes
N/A
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update

Checklist

[x] I have read the MCP Documentation
[x] My code follows the repository's style guidelines
[x] New and existing tests pass locally
[x] I have added appropriate error handling
[ ] I have added or updated documentation as needed

Additional context
Alternatively, giving the user the ability to inject their own EventSource/fetch implementations would achieve the same goal a bit more flexibly.
(Also hi! First time contributing here – great project, thanks for all the hard work!)

This might cover the same needs as #105, too, while allowing additional headers to be set on the outgoing POST requests.


Authorino Reconciler

This PR is the starting point to enable the deployment of Authorino instances via the operator.
Ps.: missing unit testing
Verification steps

Clone the repo from this branch
Install the operator on a cluster of your choice
Run the operator eg: make install run
Create an instance of authorino using the CR, an example can be found here.
Check if the authorino instance was deployed correctly by verifying whether a deployment is created and a pod is up and running

overall looks good. IMO the authorino_controller needs a heavy refactor to reduce complexity and DRY, but good enough for the first shoot.

Thanks for reviewing @eguzki I agree, we can make the optimize the code and improve readability and reusability. I will start working on it once we get all the initial steps in place :)

Tested on a local cluster (without TLS):
kind create cluster --name authorino
make install

kubectl create namespace authorino-operator
watch -n 3 "kubectl -n authorino-operator get pods | grep -viE 'Completed|OOMKilled'"

make docker-build
kind load docker-image authorino-operator:latest --name authorino
make deploy
kubectl -n authorino-operator patch deployment/authorino-operator-controller-manager -p '{"spec":{"template":{"spec":{"containers":[{"name":"manager","imagePullPolicy":"IfNotPresent"}]}}}}'

kubectl create namespace myapp
watch -n 3 "kubectl -n myapp get pods | grep -viE 'Completed|OOMKilled'"

kubectl -n myapp apply -f https://raw.githubusercontent.com/Kuadrant/authorino/main/examples/talker-api/talker-api-deploy.yaml

kubectl -n myapp apply -f -<<EOF
apiVersion: operator.authorino.kuadrant.io/v1beta1
kind: Authorino
metadata:
  name: authorino
  namespace: myapp
spec:
  image: quay.io/3scale/authorino:latest
  replicas: 1
  clusterWide: false
EOF

curl -L https://raw.githubusercontent.com/Kuadrant/authorino/main/examples/envoy/overlays/notls/configmap.yaml | sed -E 's/authorino-authorization/authorino-authorino-authorization/g' | kubectl -n myapp apply -f -
kubectl -n myapp apply -f https://raw.githubusercontent.com/Kuadrant/authorino/main/examples/envoy/base/envoy.yaml

kubectl -n myapp apply -f -<<EOF
apiVersion: authorino.3scale.net/v1beta1
kind: AuthConfig
metadata:
  name: talker-api-protection
spec:
  hosts:
    - talker-api
  identity:
    - name: friends
      apiKey:
        labelSelectors:
          group: friends
      credentials:
        in: authorization_header
        keySelector: APIKEY
EOF

kubectl -n myapp apply -f -<<EOF
apiVersion: v1
kind: Secret
metadata:
  name: friend-1-api-key-1
  labels:
    authorino.3scale.net/managed-by: authorino
    group: friends
stringData:
  api_key: ndyBzreUzF4zqDQsqSPMHkRhriEOtcRx
type: Opaque
EOF

kubectl -n myapp port-forward deployment/envoy 8000:8000
curl -H 'Host: talker-api' -H 'Authorization: APIKEY ndyBzreUzF4zqDQsqSPMHkRhriEOtcRx' http://localhost:8000/hello

We still need to fix the TLS cert fields, changing to secretRef probably, but so far so good.


Port Over External Resources and Forms

There are additional forms and resources that are currently hosted externally (mostly on Google docs), which need to be ported over to the website.
The forms need to connect to an API, which means someone (with the guidance of @saikat) need to create the API connection point and variables. Update this list with the URL, and list of variables for each form field as they are created. If someone builds the form first, create the field names based on existing standards for other fields (camelCase) and add the fields here for the API builder.
Whenever a resources moved over, the codebase needs to be searched to update links to go to the new local page.
Forms
District Research
https://docs.google.com/forms/d/e/1FAIpQLSe8CfK0gUULEVpYFm9Eb4iyGOL-_iDl395qB0z4hny7ek4iNw/viewform
Suggest Local Connector
https://docs.google.com/forms/d/e/1FAIpQLSceYguZI_gngXf7dLOXN6xUkLRNsYfn0b2v-aDEvZKPH-j1dQ/viewform
Resources
Organize Locally (just local files, probably should be zipped and provided as a PDF download)
https://docs.google.com/document/d/1Op0OaZNuykCJckSCn4vABDEr4VEdTrMeTsPCZFNSJo4/edit
Candidate Nomination Guide:
https://docs.google.com/document/d/1_Aob44aXGpc6OVOxzLNMSW-9_Hs7m5nghKYBGoeuUlE/edit
Plan to Rebuild America (keep external ATM since it's changing a lot)
https://docs.google.com/document/d/1sCFs5hqitbXBBqXxU6NULDyvydXqm-ALOqW21dv9P9k/edit

@ben-pr-p is this something you could do? We could start with the District Research and Suggest Local Connector forms, following the same naming standards as existing API requests. Just get me a list of the fields and I knock up the forms in a jiffy.

I could do this after setting up the backend for the dashboard which I'll do after the 11th (finishing finals)

@ben-pr-p awesome. If you could also first do this one single field addition, that would be quick and awesome:
https://github.com/BrandNewCongress/website/issues/23


Updates segment metadata query documentation

The existing documentation was a bit unclear, and I needed to dig into the source of SegmentAnalyzer and ColumnAnalysis to understand my results.  Updated to explain the source of the cardinality estimates on a per segment basis, and explain the way they are merged across segments.

@michaelschiff Thanks for the contribution.


Mailer & initial viewPath

Currently, the viewPath of \Yii::$app->mailer sets the central path for email. This requires you:

either to install all default emails from every module in the central email path (extra work)
either to use @aliases for the viewFile at the compose function in combination with the next point:
either to use pathMaps with the theme (making the whole software slower)

Wouldnt it be logical to provide extra information to the mailer to:

to point to a viewFile which always exists
if a identical custom file exists in the mailer::@viewPath, it takes this one?

Perhaby by checking 2 viewPaths. First the one centrally, then the default one, if defined
Advantages:

faster: prevent the use of pathMaps & themes or local copying
easier: no need to use pathMaps
flexible: default mails can be used + custom mails
stable: less errors in new projects because of missing mails in central viewPath

either to use @aliases for the viewFile at the compose function in combination with the next point:
either to use pathMaps with the theme (making the whole software slower)

Does this even work? I can't seem to get it working. I'm following a similar methodology to the following post with the difference that my pathMap values are full paths and not aliases : http://www.yiiframework.com/forum/index.php/topic/59859-how-can-i-override-a-mail-view-of-a-package/
Any help with getting this sorted would be awesome. I'm surprised it's been such a struggle.

I can not see how mailer compoent can take current module (controller) into account, while rendering views. Such behavior is possible in the scope of yii\base\Controller as it implements yii\base\ViewContextInterface and thus determines the location of the view files.
Being a global component mailer can not vary view path depending on current module or controller as it will be inconsistent, even while technically it is possible.

If you wish email view path vary depending on controller, you should use controller methods for the view rendering instead of the one built-in mailer component:
class FooController extends Controller
{
    public function actionMail()
    {
        $message = Yii::$app->mailer->compose();
        $message->setTextBody($this->render('mail-view', ['message' => $message]));
        // ...
        $message->send();
    }


pythonPackages.tifffile: fix python 2 build

/cc #45960
Motivation for this change
fix python 2 build
Things done

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

[ ] NixOS
[x] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build python27Packages.tifffile

Success on x86_64-darwin (full log)
Attempted: python27Packages.tifffile
Partial log (click to expand)
test_tifffile.TestSave.test_imsave_roundtrip(<type 'numpy.int16'>, array([[[28369, 12716, 26060, 21372], ... ok
test_tifffile.TestSave.test_imsave_roundtrip(<type 'numpy.float64'>, array([[[2.57466478e-01, 9.58594447e-01, 8.18057397e-01, 7.24228606e-01], ... ok
test_tifffile.test_imread_uint16 ... SKIP: Skipping test: test_imread_uint16: Test skipped due to test condition
test_tifffile.test_imread_uint16_big_endian ... SKIP: Skipping test: test_imread_uint16_big_endian: Test skipped due to test condition

----------------------------------------------------------------------
Ran 17 tests in 0.199s

OK (SKIP=2)
/nix/store/zx98shvfn89gmjjskpw48phjmsmswbg6-python2.7-tifffile-0.15.1

Success on aarch64-linux (full log)
Attempted: python27Packages.tifffile
Partial log (click to expand)
test_tifffile.TestSave.test_imsave_roundtrip(<type 'numpy.int16'>, array([[[28369, 12716, 26060, 21372], ... ok
test_tifffile.TestSave.test_imsave_roundtrip(<type 'numpy.float64'>, array([[[2.57466478e-01, 9.58594447e-01, 8.18057397e-01, 7.24228606e-01], ... ok
test_tifffile.test_imread_uint16 ... SKIP: Skipping test: test_imread_uint16: Test skipped due to test condition
test_tifffile.test_imread_uint16_big_endian ... SKIP: Skipping test: test_imread_uint16_big_endian: Test skipped due to test condition

----------------------------------------------------------------------
Ran 17 tests in 0.872s

OK (SKIP=2)
/nix/store/wgqhcwbl7scrigkhirbi6n08125araa3-python2.7-tifffile-0.15.1

backported: 32a4cbc756d


Open with Terminal option when inside a Zip on Explorer

Windows Terminal version
1.12.10983.0
Windows build number
10.0.22624.0
Other Software
No response
Steps to reproduce
On windows 11
If you open a zip file directly and you're within the folder of the extracted zip via explorer
then on right clicking you get the Open With Terminal option but clicking that doesn't do anything
Expected Behavior
It should either eliminate the option itself or return an alert or an error
Or it should somehow trace the directory of the actual temporary folder where it extracts the zip and open that up via the terminal on clicking the option
Actual Behavior
Clicking on it does nothing but the option remains so it feels like bug

I think this is fairly easy to fix. We can check if an item is both a folder and a stream and if so disable the command.
https://learn.microsoft.com/en-us/windows/win32/shell/sfgao?redirectedfrom=MSDN&f1url=%3FappId%3DDev16IDEF1%26l%3DEN-US%26k%3Dk(SHOBJIDL_CORE%252FSFGAO_FILESYSTEM)%3Bk(SFGAO_FILESYSTEM)%3Bk(SolutionItemsProject)%3Bk(SolutionItemsProject)%3Bk(DevLang-C%252B%252B)%3Bk(TargetOS-Windows)%26rd%3Dtrue
Happy to PR it.

@jamespack This sounds good for me

Yep, we're cool just disabling it in this case. Really seems like this is something that the modern file explorer extensions should have caught for us, but 🤷


Serving static files for plugins

I think here we need to cover two cases:

When static is served through flask app. To make it work we'll need to wrap our plugins into _PackageBoundObject, and expose their send_static_file in urls config just like flask itself does for blueprints. An alternative here is just to update urls config without wrapping.
When static is collected during deploy with extension like Flask-Collect. Files collected this way will be physically placed into given static folder and can be served with nginx directly (and this will save some CPU and provide better caching etc). I'm not sure if Flask-Collect plays well with Flask-Assets, but if we are going to cover that case too, we will need to create customer Flask Collect storage (https://github.com/klen/Flask-Collect/tree/develop/flask_collect/storage) that will look not only into flask app and it's blueprints but also into plugins.

Third way is to refactor plugins to be a proper blueprints but I'm not sure I have enough courage to do that now.
I'll play with no. 1 now.

Hm, not sure no. 1 will work, because flask only allows to have on handler for the same path (like "static"). Blueprints has their own static folders with their own prefixed urls
Probably a solution here would be to replace default handler for app's static folder to a handler that will try to resolve given path until it's found (starting from app's static and then going down to plugin specific static).
e.g if you are asking for static/bullshit.jpg, it will first check if app's static/ folder has bullshit.jpg and if it doesn't, it'll jump to plugins until it'll find it (or return 404 otherwise).
Hope that makes any sense.


Windows - "google/nodejs-runtime" throwing npm errors

I attempted to create the "google/nodejs-runtime" container and received the following errors:

0mnpm ERR! Error: ENOENT, open '/app/package.json'
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR!     http://github.com/npm/npm/issues
npm ERR! System Linux 4.0.5-boot2docker
npm ERR! command "/nodejs/bin/node" "/nodejs/bin/npm" "start"
npm ERR! cwd /app
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! path /app/package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /app/npm-debug.log
npm ERR! not ok code 0
I'm on Win7 x64.
Also note, I was able to install hello-world-nginx properly.
I also tried to create "google/nodejs" container and I received a 500 error (as has been reported in other issues. Didn't want to open a new ticket for that.

@williamkehl Are you still having this issue with this with new version of Toolbox / Kitematic?

so what happened as i still have this problem


Opening custom scenario bugged

Description of Problem or Question
Hi! I've been working on my own homebrew scenario for MONTHS now, and suddenly when i saved my progess, the editor closed and went to valkyrie main menu. I tried to open my scenario again and it keeps taking me to the main menu. Is the scenario gone? The other scenarios are working on the editor just fine but my main scenario which i've been working for months, seems to be gone... How do I save my beautiful scenario? Help..

Hi @Grieverouz, can you share the scenario here ? I will have a look.
I hope I can fix it for you !

Hi! Thanks for the fast answer, but how do i share it. Can't drop the whole "EditorScenario"-file here...

You need to zip the directory, and share it here.
If it's too big, you can use https://wetransfer.com/ or any other filesharing system.

I have it. I'll try to start it in debug mode, and see if I see anything.

Thanks alot mate. I'll wait for the results

You have two spawn events with "undead" and "Fleshless" required traits.
No monsters have those two traits, so the app cannot find any monster, and goes back too main menu.
To fix this in your scenario you should open the spawns.ini file, and fix this with a text editor.
Please note that app behaviour (going back to the main menu) is a bit extreme.
I will change that to just add a warning in the logs.
Also please note you need to change the directory name before submitting your scenario : it will be the unique name to identify your scenario, and it will also be used for ratings.
I hope I will have the occasion to try your scenario soon enough :)

Also don't forget to remove the .rar file in your scenario ;)

Wow, thanks alot dude! You just saved my scenario :)

You're welcome 👍


Helm repo add fails with Azure Container Registry

helm repo add fails with certain repositories when using Helm v3.3.2. The issue does not occur with v3.3.1 or earlier versions.
Example:
helm repo add jetstack https://charts.jetstack.io
Error: looks like "https://charts.jetstack.io" is not a valid chart repository or cannot be reached: error unmarshaling JSON: while decoding JSON: json: unknown field "serverInfo"

The issue does not occur with every repository. For example, https://kubernetes-charts.storage.googleapis.com/ can still be added:
helm repo add stable https://kubernetes-charts.storage.googleapis.com/
"stable" has been added to your repositories

Output of helm version:
version.BuildInfo{Version:"v3.3.2", GitCommit:"e5077257b6ca106d1f65652b4ca994736d221ab1", GitTreeState:"clean", GoVersion:"go1.14.9"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:58:53Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-20T00:20:54Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
The issue was observed on both KIND and OpenStack clusters.

Hey @mate-szalai. This is unfortunately one of the side effects of one of the security fixes.
In order to address one of the security issues, Helm now has to validate that the index.yaml file does not contain any extra fields, which chartmuseum does appear to add.
We're looking into this right now.

See https://github.com/helm/helm/pull/8762.

helm repo update is also effected on 3.3.2
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "grafana" chart repository
...Successfully got an update from the "codimd" chart repository
...Successfully got an update from the "ceph-csi" chart repository
...Successfully got an update from the "prometheus-community" chart repository
...Unable to get an update from the "jetstack" chart repository (https://charts.jetstack.io):
	error unmarshaling JSON: while decoding JSON: json: unknown field "serverInfo"
...

@HaveFun83 That is to be expected. PR #8762 will fix this also.

Helm 2.16.11 is affected, too.

@jkroepke Good call.

Thanks

This also fails now for Azure Container Registry helmcharts with:
error unmarshaling JSON: while decoding JSON: json: unknown field "acrMetadata"

I am experiencing this as well with both:
version.BuildInfo{Version:"v3.3.2", GitCommit:"e5077257b6ca106d1f65652b4ca994736d221ab1", GitTreeState:"clean", GoVersion:"go1.14.9"}

&

Client: &version.Version{SemVer:"v2.16.11", GitCommit:"73b28bab84490d18ab1b71489a574ee18e229eea", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.11", GitCommit:"73b28bab84490d18ab1b71489a574ee18e229eea", GitTreeState:"clean"}

Does anything need to be done on my side once a fix is pushed?

@mjrepo2 No, just the fix

Which change caused this issue? https://github.com/helm/helm/pull/8762 just refers to "A recent change merged into Helm fixes a number of security issues related to parsing malformed index files."

Chart.yaml files have an annotations field. Would it make sense to add that to other places, such as the index.yaml files so that people can have key/value pairs of their own?

Hi, @SteveLasker-
Looks like ACR users are seeing unexpected side effects of a Helm security fix. We’ll want to get a change into ACR’s manifests to mitigate that.
Why did this happen?
Per the recent CNCF-sponsored security audit, the Helm maintainers needed to apply a security fix that enabled strict handling of YAML data in the Helm client.
What is ACR doing right now that needs to be fixed?
ACR is using an "acrMetadata" field Helm doesn't know about, instead of using the annotations field:
apiVersion: v1
entries:
 wordpress:
 - acrMetadata:
     manifestDigest: sha256:08ef434162070bba4256414c80b001d15b7503ef2a1a4fa1f60bab174f80d4d7
   appVersion: 5.1.0
   created: "2019-03-06T16:59:25.8892193Z"

How can ACR fix things for users?
Happily, Helm already has a provision for this kind of data: annotations is a set of string/string key value pairs. So the change required looks like this:
apiVersion: v1
entries:
 wordpress:
 - annotations
     acrMetadata: "manifestDigest: sha256:08ef434162070bba4256414c80b001d15b7503ef2a1a4fa1f60bab174f80d4d7"
   appVersion: 5.1.0
   created: "2019-03-06T16:59:25.8892193Z"

Re-opening to track until ACR fix is in place.

Looks like this is Helm 2 functionality.
We'll see what we can do, but there's also a move to depreciate Helm 2 in lieu of Helm 3 registry support.

Hi @SteveLasker - it appears this is also a problem in Helm 3, based on user reports.

Based on the info, it's Helm 3, using the Helm 2 repo behavior that depends on charts.yaml which has lots of scalability problems.
We'll take a look, but we'd really guide developers to move away from Helm 2 repo persistence as depending on how many charts they push for automated builds, they'll eventually fall over as everything is attempted to be represented in a single .yaml file. It was a great idea when there were a limited set of public charts. For users private usage, it's not a very scalable solution.

Hi Steve, it appears to be that ACR is/was rewriting an invalid index at some point (per https://github.com/helm/helm/issues/8761#issuecomment-694962864). Per the recent CNCF-sponsored security audit, the Helm maintainers needed to apply a security fix that enabled strict handling of YAML data in the Helm client.
So I think what we're saying here is that ACR was invalidly munging indexes, and whereas before the security fix Helm was lax about it, now Helm is catching that invalid entry. Does that make sense? it's not immediately clear whether all or only some indexes are invalid and will bonk.... I think dapr is seeing this, for example (https://github.com/dapr/dapr/issues/2073).

I think @jdolitsky had an example of this. What I got from him in an offline chat:
apiVersion: v1
entries:
  wordpress:
  - acrMetadata:
      manifestDigest: sha256:08ef434162070bba4256414c80b001d15b7503ef2a1a4fa1f60bab174f80d4d7
    appVersion: 5.1.0
    created: "2019-03-06T16:59:25.8892193Z"

That acrMetadata field isn't supposed to be in there and should be part of the annotations in a chart

Quick update: for those using chartmuseum. charts.jetstack.io, codefresh, etc. Helm v3.3.3 is now available with a fix. Please upgrade to receive the fix.
https://github.com/helm/helm/releases/tag/v3.3.3
I've re-titled the issue to reflect the current state of things. We've tested v3.3.3 against a number of chart repositories, and they all sem to be working now. The only one that does not work currently is ACR.

Per the recent CNCF-sponsored security audit, the Helm maintainers needed to apply a security fix that enabled strict handling of YAML data in the Helm client.

It's a little unfortunate that this security fix didn't go through an embargo period to understand the impact and fix before it got rolled out. But, we are looking into it now as we do have a lot of usage. That said, to roll out a change to all Azure regions will take some time.
The helm repo behavior impacted here was an experiment that led to the OCI Artifacts work.
As noted in our ACR Roadmap, we do suggest users move to Helm 3 Registry support as it provides more scalability & reliability as all OCI compliant registries support this approach.

A quick update.
Over the weekend, we've identified the issue and are evaluating the performance impact of options.

The impacted data is in index.yaml which is maintained by the registry as charts are pushed.
We can either update the entire index.yaml for each registry or process the fix on request. As customers are automating their deployments, we see some customers with very large index.yaml files.

We recognize that customers use ACR for their private deployments of charts, and may not be able to simply re-push their charts.
We will have an update out shortly on our next steps.
As with all software, testing a new version before deploying it is a best practice, so we hope this little "test" was a means for customers to recognize "friends don't let friends use :latest for any production workload :(
But, we recognize this is a real issue and we're doing what we can to solve it ASAP.
The most immediate solution is to not upgrade Helm until we identify when we can get this rolled out.
Apologies for issues this has caused customers,
Steve

It's a little unfortunate that this security fix didn't go through an embargo period to understand the impact and fix before it got rolled out.

Last Friday I kicked off a conversation on creating an embargo period setup for security releases.
@SteveLasker if you want a project to have an embargo setup for security releases the appropriate way to discuss it is to request it. Complaining that it doesn't exist or that you are not on the list is an approach that usually doesn't win favor with open source project maintainers.
I would also suggest that the next time y'all are going to extend something with Helm it may be useful to ask about patterns in doing so upstream. We could provide some guidance and hopefully avoid issues like this in the future.

The most immediate solution is to not upgrade Helm until we identify when we can get this rolled out.

This is a somewhat scary option. ACR extended the index.yaml file rather than use the built-in annotations field at the same level as the extension. So, to avoid breaking the experience for your users due to a custom extension that no longer works (when there were other ways to approach this) you are suggesting people don't install a security update.
In the future, we are happy to help with Helm extension points (either in explaining them or discussing adding them). We would like to see ACR not end up in a broken situation where you're telling people not to apply a Helm security release.

@mattfarina, the security notification process is a good one.
In this case, the maintainers of Helm knew there were usages of helm repos and we had worked with the team on the incubation of acr helm support, and ultimately the creation of the OCI Artifact approach, now supported in multiple cloud providers. To say the team didn't know is disingenuine. To engage in a CNCF security audit, have an outcome that requires a change, and not proactively reach out to various cloud providers who have security processes and other implementors of the technology is big miss.
We're all human, and we learn from our mistakes. Are we willing to recognize that?
The fact that we used an annotation that was malformed is a bug, and we're actively working to fix it, but this behavior has been in place and working for 2 years. Being a bit more proactive on testing and understanding the impact of a security change is something to consider.
The situation customers are in is:

helm rolled out a change without testing or notifying known usages
Customers are now broken. They have a choice to roll back to a stable version, compatible with their environment or remain broken until we can get the fix rolled out to all regions. Should customers be blocked from doing deployments, which may have other security fixes?

We have a fix and will roll out following Azure Safe Deployment Practices.
As we have precise timelines, we'll post here.

Hey folks,
An official update, with some learnings applied:

The ACR engineering team is validating a fix that has been deployed for canary testing on September 22, 2020
Assuming testing goes as expected, following Azure safe deployment practices, regional deployments will start September 23, 2020
Deployments should complete by the start of business, Monday, September 28, 2020 - please check here for final confirmation and status updates.

Learnings:

We have provided full insight into the issue and learnings we're applying to an ACR Advisories page
We also encourage the Helm community to weigh in on your views on how security notifications should be handled by Helm and other CNCF projects.

A quick update for those tracking.
ACR Helm Repo Security Advisory

Date
Status

September 24, 2020
Active - in-deployment

September 22, 2020
Active - testing solution

September 18, 2020
Identified

Full details at: ACR Helm Repo Security Advisory

Full details at: ACR Helm Repo Security Advisory

@SteveLasker Broken link, since it's /edit

Woops, thanks DK. Fixed now.
I'll confirm the rollout is complete for Azure Commercial cloud regions shortly.

Engineering has confirmed Azure Public/Commercial is complete.
Azure China and Azur Gov clouds will rollout over the next two days.
I'll update the ACR Helm Repo Security Advisory shortly

@mate-szalai, I believe this issue should be closed as rollouts are complete.
I'd also respectfully ask the title be changed back to "Helm repo add fails with some repositories" as this was unique to ACR, but did help users find the issue to track the status.
Thanks,
Steve

@SteveLasker, I changed the title back and closing this now.
If the Helm maintainers wish the make changes to the issue, please feel free to do so.


Loader crashes if there is a syntax error

I am not sure if it is a bug or a feature.
But basically, if make a JS syntax error in file loaded via the worker-loader you will see some not-so-helpfull error.

Other loaders point out a syntax error.

same here :/

My quick midnight advice: fix the syntax with some linter and keep going.
On Apr 29, 2015 1:45 AM, "Julien Bouquillon"<EMAIL_ADDRESS>wrote:

same here :/
—
Reply to this email directly or view it on GitHub
https://github.com/webpack/worker-loader/issues/1#issuecomment-97264922.

@molszanski thanks but the problem is that when using webpack dev server, it crashes the process

I would guess, that the crash is caused by the wrong JS syntax in one of
your worker files. It should also break normal webpack build and most
browsers.
Try to load your worker module in a regular way and see what is the real
reason.
On Apr 29, 2015 2:54 AM, "Julien Bouquillon"<EMAIL_ADDRESS>wrote:

@molszanski https://github.com/molszanski thanks but the problem is
that when using webpack dev server, it crashes the process
—
Reply to this email directly or view it on GitHub
https://github.com/webpack/worker-loader/issues/1#issuecomment-97274765.


Can it work on NVIDIA GeForce MX130 4GB GDDR5 graphics ?

Can it work on NVIDIA GeForce MX130 4GB GDDR5 graphics ?

It's very far from the recommended minimum, a GTX 1070, so it would be extremely slow if it runs at all.

So wich graphic card you recommend best for future use also

So wich graphic card you recommend best for future use also

Sure it will work
I use the same pc

I’m getting less than 3fps on my 1650 mobile

i got it working i get 15fps which is real time


Update minimum futures market deposit

Currently users are required to deposit a minimum of $50 on each futures market deposit but this should be changed to take into consideration the amount of balance already in the market. So for example if there is $25 of margin left in the market then a minimum of $25 is required when depositing.

Duplicate of #1394