'VisionCamera/FrameProcessorPlugin.h' file not found

i have following package json
"@expo/react-native-action-sheet": "^3.13.0",
"@gorhom/bottom-sheet": "^4",
"@gorhom/portal": "^1.0.13",
"@react-native-async-storage/async-storage": "^1.16.1",
"@react-native-community/blur": "^3.6.0",
"@react-navigation/bottom-tabs": "^6.2.0",
"@react-navigation/native": "^6.0.8",
"@react-navigation/native-stack": "^6.5.0",
"@rneui/base": "^4.0.0-rc.1",
"@rneui/themed": "^4.0.0-rc.1",
<EMAIL_ADDRESS>"^4.5.5",
"@types/react-native-snap-carousel": "^3.8.5",
"axios": "^0.26.0",
"buffer": "^6.0.3",
"date-fns": "^2.28.0",
"form-data": "^4.0.0",
"formik": "^2.2.9",
"i18next": "^21.6.12",
"i18next-http-backend": "^1.4.0",
"lodash.clonedeep": "^4.5.0",
"lodash.debounce": "^4.0.8",
"lodash.isempty": "^4.4.0",
"lodash.isequal": "^4.5.0",
"mobx": "^6.4.2",
"mobx-devtools-mst": "^0.9.30",
"mobx-react-lite": "^3.3.0",
"mobx-state-tree": "^5.1.3",
"qs": "^6.10.3",
"querystring": "^0.2.1",
"react": "17.0.2",
"react-i18next": "^11.15.5",
"react-native": "0.68.0",
"react-native-compressor": "^1.5.2",
"react-native-config": "^1.4.5",
"react-native-currency-input": "^1.0.1",
"react-native-date-picker": "^4.2.0",
"react-native-flash-message": "^0.2.1",
"react-native-fs": "^2.19.0",
"react-native-gesture-handler": "^2.4.2",
"react-native-image-picker": "^4.7.3",
"react-native-network-logger": "^1.12.0",
"react-native-permissions": "^3.3.1",
"react-native-photo-editor": "1.0.13",
"react-native-reanimated": "^2.6.0",
"react-native-safe-area-context": "^4.0.1",
"react-native-screens": "^3.12.0",
"react-native-shake": "^5.1.1",
"react-native-snap-carousel": "^3.9.1",
"react-native-svg": "^12.1.1",
"react-native-table-component": "^1.2.2",
"react-native-text-size": "^4.0.0-rc.1",
"react-native-url-polyfill": "^1.3.0",
"react-native-vision-camera": "^2.13.1",
"react-native-web": "^0.17.7",
"react-query": "^3.34.16",
"vision-camera-code-scanner": "^0.2.0",
When i trying to build react native ios i have following error 'VisionCamera/FrameProcessorPlugin.h' file not found in VisionCameraCodeScanner-Bridging-Header.h file
Xcode Version 13.3 (13E113)

did you find a solution for this? im having exactly the same error : "'VisionCamera/FrameProcessorPlugin.h' file not found"

Same issue here

same here as well. Tried cleaning the build folder, restarting watchman, yarn starting with --reset-cache and re-creating the Pods, but still facing this issue

Same issue on RN 0.69.1 with use_frameworks! (react-native-firebase > v15 requires it) in podfile

same here as well. Tried cleaning the build folder, restarting watchman, yarn starting with --reset-cache and re-creating the Pods, but still facing this issue
edit: I resolved it locally. I believe it was because I was missing react-native-vision-camera as an import

Can you please elaborate a bit?
Where to import react-native-vision-camera?

I have the same issue - @react-native-firebase > 15 requires  use_frameworks! in the podfile  vision-camera-code-scanner/VisionCameraCodeScanner-Bridging-Header.h and VisionCameraCodeScanner.m

Same issue here

I believe this has something to do with use_frameworks! for the firebase pods.
So instead I added these lines in the Podfile.
  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  $RNFirebaseAsStaticFramework = true

And inside post_install do |installer|
    # TEMPORARY FIX UNTIL FIX IS RELEASED IN REACT NATIVE
    installer.target_installation_results.pod_target_installation_results.each do |pod_name, target_installation_result|
      target_installation_result.native_target.build_configurations.each do |config|
        # For third party modules who have React-bridging dependency to search correct headers
        config.build_settings['HEADER_SEARCH_PATHS'] ||= '$(inherited) '
        config.build_settings['HEADER_SEARCH_PATHS'] << '"$(PODS_ROOT)/Headers/Private/React-bridging/react/bridging" '
        config.build_settings['HEADER_SEARCH_PATHS'] << '"$(PODS_CONFIGURATION_BUILD_DIR)/React-bridging/react_bridging.framework/Headers" '
      end
    end

Same issue here

I have the same issue

Same issue here

I encountered the same issue, but I don't use use_frameworks! and it seems to work fine on an intel machine, but fails on a Mac m1

having the same issue, on M1 arch

sadly I am getting this on intel too :( anyone who knows how to fix this please give instructions or resources

I have this issue too, and will be glad if anyone can give a solution.

Also encountered this with firebase v15 and react native 0.70, Any possible workarounds on this?

The same issue with firebase v15.7.0 and react native 0.69.3, Any possible workarounds on this?

I downgraded firebase to v14.2.0 and changed the podfile to be without the use_frameworks!.
it worked for me.

The same issue with react native 0.69.5, Any possible workarounds on this?

The same issue with react native 0.69.5, Any possible workarounds on this?

Since use_frameworks is being used, we have to define these libraries as static. The workaround in Podfile works for me.
I've put that just above use_react_native!
  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('vision-camera-code-scanner') || pod.name.eql?('VisionCamera')
        def pod.build_type
          Pod::BuildType.static_library
        end
      end
    end
  end

@MMYurt it does not works for me.
Now I have a new error :/
-U and -bitcode_bundle (Xcode setting ENABLE_BITCODE=YES) cannot be used together in target 'RCT-Folly' from project 'Pods'

@MMYurt it does not works for me.
Now I have a new error :/
-U and -bitcode_bundle (Xcode setting ENABLE_BITCODE=YES) cannot be used together in target 'RCT-Folly' from project 'Pods'

Bitcode has been deprecated in Xcode 14 and App Store don't accept bitcode submissions anymore.
You should try to disble it: set Enable Bitcode to No under target Build Settings in Xcode.

@MMYurt it does not works for me.
Now I have a new error :/
-U and -bitcode_bundle (Xcode setting ENABLE_BITCODE=YES) cannot be used together in target 'RCT-Folly' from project 'Pods'

Bitcode has been deprecated in Xcode 14 and App Store no longer accepts bitcode submissions.
You should try to disble it: set Enable Bitcode to No under target Build Settings in Xcode.

@brynjagr I've tried this, but error persists :/

@brynjagr I've tried this, but error persists :/

I had got this error as well and added the script below into post_install
  installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['ENABLE_BITCODE'] = 'NO'
      end
    end

After that, it was continuing to gives different errors. I choose to downgrade firebase version to v14 and deleted use_frameworks

any news here?

I've also started having this issue after following the @react-native-firebase/app setup guide.
In going through the steps outlined here to have a clean install of the dependencies:
rm -rf package-lock.json && rm -rf yarn.lock && rm -rf node_modules
rm -rf ios/Podfile.lock && rm -rf ios/Pods
npm i  # or "yarn"
cd ios && pod repo update && pod update && pod install

I get the following error in the last step:
[!] CocoaPods could not find compatible versions for pod "GTMSessionFetcher/Core":
  In Podfile:
    RNFBAuth (from `../node_modules/@react-native-firebase/auth`) was resolved to 15.7.1, which depends on
      Firebase/Auth (= 10.0.0) was resolved to 10.0.0, which depends on
        FirebaseAuth (~> 10.0.0) was resolved to 10.0.0, which depends on
          GTMSessionFetcher/Core (~> 2.1)

    vision-camera-code-scanner (from `../node_modules/vision-camera-code-scanner`) was resolved to 0.2.0, which depends on
      GoogleMLKit/BarcodeScanning was resolved to 0.60.0, which depends on
        GoogleMLKit/MLKitCore (= 0.60.0) was resolved to 0.60.0, which depends on
          MLKitCommon (~> 0.60.0) was resolved to 0.60.0, which depends on
            GTMSessionFetcher/Core (~> 1.1)

Updating my package.json to depend on react-native-firebase v14 with:
"@react-native-firebase/app": "^14.12.0",
"@react-native-firebase/auth": "^14.12.0",
// other react-native-firebase packages...

As well as removing the use_frameworks! line from my Podfile (as described here) seems to have done the trick (after I clean installed everything again), allowing the application to compile.
Maybe updating the GoogleMLKit/BarcodeScanning dependency on this package would resolve the conflict with the newer react-native-firebase?

Am also facing the issue, don't know what to do next, i tried all the suggestion as said in the discussions here, but not able to overcome the issue kindly help me.
in pod file i included the following
pre_install do |installer|
installer.pod_targets.each do |pod|
if pod.name.eql?('vision-camera-code-scanner') || pod.name.eql?('VisionCamera')
def pod.build_type
Pod::BuildType.static_library
end
end
end
end
$RNFirebaseAsStaticFramework = true
post_install do |installer|
react_native_post_install(installer)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
installer.pods_project.targets.each do |target|
if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle"
target.build_configurations.each do |config|
config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
  end
end

end
end
use_frameworks! :linkage => :static
my react native info
System:
OS: macOS 13.0
CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
Memory: 36.14 MB / 8.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.13.0 - /usr/local/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 8.19.3 - ~/Work/MyProject/DLBProjeect/OspynDLB_V1.0/node_modules/.bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.1/14B47b - /usr/bin/xcodebuild
Languages:
Java: 17.0.2 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.2 => 0.66.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

did someone found a solution about it ?

target.build_configurations.each do |config|
config.build_settings['ENABLE_BITCODE'] = 'NO'
end

This works for me but after this i got another error saying :
/Users/username/Library/Developer/Xcode/DerivedData/Deelt-abafkzsficjaryhdeeerazdkxtwh/Build/Products/Debug-iphonesimulator/FirebaseFunctions/FirebaseFunctions.framework/Headers/FirebaseFunctions-Swift.h:450:2 Unsupported Swift architecture
/Users/username/Library/Developer/Xcode/DerivedData/Deelt-abafkzsficjaryhdeeerazdkxtwh/Build/Products/Debug-iphonesimulator/FirebaseStorage/FirebaseStorage.framework/Headers/FirebaseStorage-Swift.h:828:2 Unsupported Swift architecture

it almost a year now and no solution, pretty sad 🫤

In my case I only install npm i vision-camera-code-scanner , then I also install react-native-vision-camera, and build run, seems react-native-vision-camera is dependency for vision-camera-code-scanner but never the less.

This issue is preventing me from using this library at work, I've tried the podfile solutions above to no avail. It looks like [https://github.com/mrousavy/react-native-vision-camera/pull/1522](this PR here) might fix this when it's done, Would there be any chance to backport this to v2?

I also stuck with this issue after updating xcode to 14.3 and adding use_frameworks! to Podfile
ios/VisionCameraCodeScanner-Bridging-Header.h:4:9 'VisionCamera/FrameProcessorPlugin.h' file not found

Since use_frameworks is being used, we have to define these libraries as static. The workaround in Podfile works for me.
I've put that just above use_react_native!
  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('vision-camera-code-scanner') || pod.name.eql?('VisionCamera')
        def pod.build_type
          Pod::BuildType.static_library
        end
      end
    end
  end

It worked for me.

Found a solution
The problem is using this use_frameworks! in your PodFile
most people are using use_frameworks! due to firebase v15+ requirement
so if you are using use_frameworks! for any reason
remove it and use :module_headers => true instead for each library due to which you used use_frameworks! earlier
in case of firebase, after remover use_frameworks!
you can add the following line at the end of Podfile
pod 'Firebase', :modular_headers => true
pod 'FirebaseCore', :modular_headers => true
pod 'FirebaseCoreInternal', :modular_headers => true
pod 'GoogleUtilities', :modular_headers => true
This should work fine. now you will be able to use your frame processors.
Hope that helps

Try this https://www.youtube.com/watch?v=sE0MEyFA7E4&list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i&index=7 & https://www.youtube.com/watch?v=BFkIIIKgjnE&list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i&index=80

I believe this has something to do with use_frameworks! for the firebase pods.
So instead I added these lines in the Podfile.
  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  $RNFirebaseAsStaticFramework = true

And inside post_install do |installer|
    # TEMPORARY FIX UNTIL FIX IS RELEASED IN REACT NATIVE
    installer.target_installation_results.pod_target_installation_results.each do |pod_name, target_installation_result|
      target_installation_result.native_target.build_configurations.each do |config|
        # For third party modules who have React-bridging dependency to search correct headers
        config.build_settings['HEADER_SEARCH_PATHS'] ||= '$(inherited) '
        config.build_settings['HEADER_SEARCH_PATHS'] << '"$(PODS_ROOT)/Headers/Private/React-bridging/react/bridging" '
        config.build_settings['HEADER_SEARCH_PATHS'] << '"$(PODS_CONFIGURATION_BUILD_DIR)/React-bridging/react_bridging.framework/Headers" '
      end
    end

This is not effective bcz I need to check with all npm modules.

Since use_frameworks is being used, we have to define these libraries as static. The workaround in Podfile works for me.
I've put that just above use_react_native!
  pre_install do |installer|
    installer.pod_targets.each do |pod|
      if pod.name.eql?('vision-camera-code-scanner') || pod.name.eql?('VisionCamera')
        def pod.build_type
          Pod::BuildType.static_library
        end
      end
    end
  end

It worked for me, thank you

I believe this has something to do with use_frameworks! for the firebase pods.
So instead I added these lines in the Podfile.
  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  $RNFirebaseAsStaticFramework = true

And inside post_install do |installer|
    # TEMPORARY FIX UNTIL FIX IS RELEASED IN REACT NATIVE
    installer.target_installation_results.pod_target_installation_results.each do |pod_name, target_installation_result|
      target_installation_result.native_target.build_configurations.each do |config|
        # For third party modules who have React-bridging dependency to search correct headers
        config.build_settings['HEADER_SEARCH_PATHS'] ||= '$(inherited) '
        config.build_settings['HEADER_SEARCH_PATHS'] << '"$(PODS_ROOT)/Headers/Private/React-bridging/react/bridging" '
        config.build_settings['HEADER_SEARCH_PATHS'] << '"$(PODS_CONFIGURATION_BUILD_DIR)/React-bridging/react_bridging.framework/Headers" '
      end
    end

yeah it is working

This is kind of obvious but I think the installation instructions aren’t great. It’s true, you also need react-native-vision-camera as a dependency as well, it would be easy just to mention this in the setup instructions.
I also had to downgrade react-native-reanimated to v2.14.4 to get the build working. However I'm now running into another issue where .globals is not a valid Plugin property in the babel.config.js file.

installing react-native-worklets-core fixed it for me

https://github.com/mrousavy/react-native-vision-camera/issues/1987

this lib needs to be updated with V3...
https://github.com/mrousavy/react-native-vision-camera/issues/1987#issuecomment-1759411150


Update SQL Style Guide For SQL Fluff

Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/9
Originally created by @pnadolny13 on 2021-11-03 16:47:54

Some conventions arent supported by sql fluff so we should update them to allow us to fully lint with SQLFluff.

View 1 previous comment from the original issue on GitLab


After upgrading to 2.0.1, TM1py fails when a URL contains 'api/v1' inside.

Describe the bug
TM1py fails to get some data from TM1 (I'm using V11) when the URL contains '/api/v1'.
To Reproduce
Establish a connection using TM1Py 2.0.1 to a TM1 instance and retrieve for instance the count of subsets, like this:
	from tm1py import TM1Service
	tm1 = TM1Service(...)
	connection = tm1.connection.GET("/api/v1/Dimensions('Organization')/Hierarchies('Organization')/Subsets('North')/Elements/$count")

An error is triggered:
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "C:\Users\elias\anaconda3\envs\test-service\lib\site-packages\TM1py\Services\RestService.py", line 500, in GET
    return self.request(
  File "C:\Users\elias\anaconda3\envs\test-service\lib\site-packages\TM1py\Services\RestService.py", line 296, in request
    self.verify_response(response=response)
  File "C:\Users\elias\anaconda3\envs\test-service\lib\site-packages\TM1py\Services\RestService.py", line 888, in verify_response
    raise TM1pyRestException(response.text,
TM1py.Exceptions.Exceptions.TM1pyRestException: Text: '{"error":{"code":"278","message":"'api' resource can not be resolved on type 'EntityContainer'."}}' - Status Code: 404 - Reason: 'Not Found' - Headers: {'Content-Length': '106', 'Connection': 'keep-alive', 'Content-Encoding': 'gzip', 'Cache-Control': 'no-cache', 'Content-Type': 'application/json; charset=utf-8', 'OData-Version': '4.0'}

But, after removing the "/api/v1/" part from the URL, like below:
	from tm1py import TM1Service
	tm1 = TM1Service(...)
	connection = tm1.connection.GET("/Dimensions('Organization')/Hierarchies('Organization')/Subsets('North')/Elements/$count")

It works!
Expected behavior
TM1py should accept URLs containing '/api/v1' when the TM1 Version accepts them.
Version
TM1py 2.0.1
TM1 Server Version: 11.8.01900.10

Is the issue that this worked in prior versions? In v2, this is by design. TM1py figures out the proper URL structure based on the version and environment you are running. The api base url is everything that precedes and includes 'api/v1'.  When using requests directly you only need to specify the entities you want to query.

for backwards compatability we could cut off the leading /api/v1 of the url in the _url_and_body function if it is there.
https://github.com/cubewise-code/tm1py/blob/4785741606330aa4b9a5afc455e01eab8c7a926c/TM1py/Services/RestService.py#L767

@svbtropical please upgrade to branch issue/1056 with pip and verify if the issue is resolved.
pip uninstall tm1py
pip install https://github.com/cubewise-code/tm1py/archive/refs/heads/issue/1056.zip

Seems to be working fine! 🥳


Not able to run the utility as a container

Hi  I am trying to build docker image of this project. I am using Docker version 25.0.3, build 4debf41.  I am running windows 11.
When I run "docker build -t porting-advisor ." I get below error
`C:\porting-advisor-for-graviton>docker build -t porting-advisor .
[+] Building 10.3s (11/13)                                                                               docker:default
=> [internal] load build definition from Dockerfile                                                               0.0s
=> => transferring dockerfile: 824B                                                                               0.0s
=> [internal] load metadata for public.ecr.aws/amazoncorretto/amazoncorretto:17-al2023                            2.4s
=> [internal] load metadata for public.ecr.aws/amazonlinux/amazonlinux:2023                                       2.4s
=> [internal] load .dockerignore                                                                                0.0s
=> => transferring context: 2B                                                                                0.0s
=> [builder 1/6] FROM public.ecr.aws/amazonlinux/amazonlinux:2023@sha256:58b239881342c76bc01ac4a2bf442e76b7f816a  0.0s
=> [internal] load build context                                                                                0.0s
=> => transferring context: 10.79kB                                                                               0.0s
=> CACHED [runtime 1/2] FROM public.ecr.aws/amazoncorretto/amazoncorretto:17-al2023@sha256:bfc719be14f82ddb38519  0.0s
=> CACHED [builder 2/6] RUN yum install java-17-amazon-corretto python3.11 python3.11-pip maven binutils -y &&    0.0s
=> CACHED [builder 3/6] COPY src src/                                                                             0.0s
=> CACHED [builder 4/6] COPY build.sh setup-environment.sh getBinaryName.sh requirements-build.txt ./             0.0s
=> ERROR [builder 5/6] RUN /usr/bin/python3.11 -m venv .venv &&     source .venv/bin/activate &&     python3 -m   7.7s

[builder 5/6] RUN /usr/bin/python3.11 -m venv .venv &&     source .venv/bin/activate &&     python3 -m pip install -r requirements-build.txt &&     FILE_NAME=porting-advisor ./build.sh:
2.986 Collecting altgraph==0.17.3
3.344   Downloading altgraph-0.17.3-py2.py3-none-any.whl (21 kB)
3.395 Collecting certifi==2024.7.4
3.414   Downloading certifi-2024.7.4-py3-none-any.whl (162 kB)
3.550      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 163.0/163.0 kB 1.3 MB/s eta 0:00:00
4.014 Collecting coverage==7.2.7
4.035   Downloading coverage-7.2.7-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (232 kB)
4.187      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 232.6/232.6 kB 1.5 MB/s eta 0:00:00
4.226 Collecting idna==3.7
4.250   Downloading idna-3.7-py3-none-any.whl (66 kB)
4.275      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 66.8/66.8 kB 2.5 MB/s eta 0:00:00
4.311 Collecting Jinja2==3.1.4
4.334   Downloading jinja2-3.1.4-py3-none-any.whl (133 kB)
4.418      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.3/133.3 kB 1.5 MB/s eta 0:00:00
4.576 Collecting MarkupSafe==2.1.3
4.614   Downloading MarkupSafe-2.1.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (28 kB)
4.663 Collecting packaging==23.1
4.693   Downloading packaging-23.1-py3-none-any.whl (48 kB)
4.719      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 48.9/48.9 kB 1.8 MB/s eta 0:00:00
4.967 Collecting progressbar33==2.4
5.016   Downloading progressbar33-2.4.tar.gz (10 kB)
5.026   Preparing metadata (setup.py): started
5.180   Preparing metadata (setup.py): finished with status 'done'
5.265 Collecting pyinstaller==5.13.1
5.281   Downloading pyinstaller-5.13.1-py3-none-manylinux2014_x86_64.whl (660 kB)
5.630      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 660.7/660.7 kB 1.9 MB/s eta 0:00:00
5.688 Collecting pyinstaller-hooks-contrib==2023.6
5.707   Downloading pyinstaller_hooks_contrib-2023.6-py2.py3-none-any.whl (274 kB)
5.806      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 274.3/274.3 kB 3.4 MB/s eta 0:00:00
5.860 Collecting pyparsing==3.1.1
5.894   Downloading pyparsing-3.1.1-py3-none-any.whl (103 kB)
5.934      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 103.1/103.1 kB 3.1 MB/s eta 0:00:00
6.064 Collecting urllib3==2.2.2
6.087   Downloading urllib3-2.2.2-py3-none-any.whl (121 kB)
6.157      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 121.4/121.4 kB 1.7 MB/s eta 0:00:00
6.303 Collecting XlsxWriter==3.1.2
6.335   Downloading XlsxWriter-3.1.2-py3-none-any.whl (153 kB)
6.392      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 153.0/153.0 kB 2.7 MB/s eta 0:00:00
6.408 Requirement already satisfied: setuptools>=42.0.0 in /.venv/lib64/python3.11/site-packages (from pyinstaller==5.13.1->-r requirements-build.txt (line 9)) (65.5.1)
6.498 Installing collected packages: progressbar33, altgraph, XlsxWriter, urllib3, pyparsing, pyinstaller-hooks-contrib, packaging, MarkupSafe, idna, coverage, certifi, pyinstaller, Jinja2
6.499   DEPRECATION: progressbar33 is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
6.499   Running setup.py install for progressbar33: started
6.702   Running setup.py install for progressbar33: finished with status 'done'
7.423 Successfully installed Jinja2-3.1.4 MarkupSafe-2.1.3 XlsxWriter-3.1.2 altgraph-0.17.3 certifi-2024.7.4 coverage-7.2.7 idna-3.7 packaging-23.1 progressbar33-2.4 pyinstaller-5.13.1 pyinstaller-hooks-contrib-2023.6 pyparsing-3.1.1 urllib3-2.2.2
7.561
7.561 [notice] A new release of pip available: 22.3.1 -> 24.2
7.561 [notice] To update, run: pip install --upgrade pip
7.657 /bin/sh: line 1: ./build.sh: cannot execute: required file not found

Dockerfile:11
10 |     COPY build.sh setup-environment.sh getBinaryName.sh requirements-build.txt ./
11 | >>> RUN /usr/bin/python3.11 -m venv .venv &&
12 | >>>     source .venv/bin/activate &&
13 | >>>     python3 -m pip install -r requirements-build.txt &&
14 | >>>     FILE_NAME=porting-advisor ./build.sh

15

ERROR: failed to solve: process "/bin/sh -c /usr/bin/python3.11 -m venv .venv &&     source .venv/bin/activate &&     python3 -m pip install -r requirements-build.txt &&     FILE_NAME=porting-advisor ./build.sh" did not complete successfully: exit code: 127`

Thanks for reaching out, @dattakugve . The team is looking into reproducing this issue and will get back to you soon.

Following up on this issue, we were able to run it successfully using the latest version of docker (Docker version 27.1.1 build 6312585) on Windows 11, so maybe its worth trying that. Also, I'm curious to know if there are any local changes or non-standard things set up. Lastly, I would also recommend verifying that the line endings in their file are unix based, not windows based. Seems like there has been some discussion on Stack Exchange about this issue. Hope that helps!


Update how-to-connect-password-hash-synchronization.md

Add spaces to FIPSPolicy nodes for XML formatting.
When adding this line exactly to the specified location, I received multiple errors. I was not familiar with the syntax of the file, and discovered that adding this space was necessary for it to work, so I am proposing this change to potentially help others.

@billmath

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Is there a status update on this?

#sign-off


Updated section title 'Shared access signatures'

Was 'Share access signatures'

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

Verified the update; merging.
@rcabr Thanks for submitting the fix.


setup-radiopadre-virtualenv not excuted when pip install -e is used

Doesn't seem to be invoked with pip install -e.

My naive attempt at fixing it in https://github.com/ratt-ru/radiopadre/commit/afe48984a269c5ae7ac874ef811ddb8271c04ec6 didn't entirely solve it. It did make it work for python setup.py develop, but pip install -e now bombs out with
  Running setup.py develop for radiopadre
    ERROR: Command errored out with exit status 1:
     command: /home/oms/.radiopadre/venv/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/home/oms/radiopadre/setup.py'"'"'; __file__='"'"'/home/oms/radiopadre/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop --no-deps
         cwd: /home/oms/radiopadre/
    Complete output (8 lines):
    /home/oms/.radiopadre/venv/lib/python3.6/site-packages/setuptools/dist.py:476: UserWarning: Normalizing '1.0-pre4' to '1.0rc4'
      normalized_version,
    usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
       or: setup.py --help [cmd1 cmd2 ...]
       or: setup.py --help-commands
       or: setup.py cmd --help

    error: option --no-deps not recognized
    ----------------------------------------

This is beyond my setup-fu, so over to you @Athanaseus.


Ability to Adjust Separator Insets?

Is there a way to adjust cell separator insets? I've tried just passing "separatorInsets" and "layoutMargins" to the cell configuration but it's not affecting them at all.
row.configuration[FormRowDescriptor.Configuration.CellConfiguration] = ["layoutMargins" : UIEdgeInsetsZero, "separatorInsets" : UIEdgeInsetsZero]

Hello @jtkendall,
Issue is closed without any comment, is this now possible?
For empty cells this works fine (see Screenshot):
tableView.layoutMargins = UIEdgeInsetsZero
tableView.separatorInset = UIEdgeInsetsZero

For filled cells this doesn't works (see Screenshot):
override func tableView(tableView: UITableView, willDisplayCell cell: UITableViewCell, forRowAtIndexPath indexPath: NSIndexPath) {
    cell.separatorInset = UIEdgeInsetsZero
    cell.layoutMargins = UIEdgeInsetsZero
}

Thanks for your help and your library.


Ensure SplitsComponent is fully implemented

I know I'm not implementing all of the settings yet.

I want to see headers for the columns as well.

Done


Loading error with KHR_materials_unlit

metal-rough-transm.zip

https://dassaultsystemes-technology.github.io/dspbr-pt/

Drag and drop the unzippped glTF and its resources.
Result: the loading animation never ends.

Disable "use pathtracing".
Result: the glTF model is now visible.

Enable "use pathtracing"
Result: the model for "metal-roughness-0.01" reappears, along with the loading animation.

Thanks!

Fixed in 5caf980. Thanks for the reproducer.


wont build imgui version

Describe the bug
Doesn't let me build the ImGui version
To Reproduce
Hell, I don't know?
Expected behavior
a build to dll, kthx
Screenshots
http://prntscr.com/q43ycv
Additional context
well i just tried building this,
i've tried different build configurations, yet this doesnt do anything

Also,
http://prntscr.com/q4415a
in general, this is very weird and exceptionally confusing.
Precompiled headers are enabled

If you're unable to fix this, I don't recommend using this project

@EternityX There was a fix, downgrading from 2019 to 2017 using v141 toolset did the job, I just thought deadcell as being a out-of-the-box 2019 version


Add automatic weekly snapshot releases with Github Actions

See prototype in the clangd-build/empty repository
https://github.com/clangd-build/empty/releases
https://github.com/clangd-build/empty/actions

Some suggestions:

would be nicer to have some documentations (in the PR description?) describing the whole picture of the workflow
I put this in releases.md.

the release is under pre-release (https://github.com/clangd-build/empty/releases), could we make it release?
Only the periodic workflow sets the prerelease flag. The automatic snapshot releases are marked as pre-release, which I think is appropriate given that we have no idea about their stability.
We can create manual releases for whichever revision we want (e.g. matching LLVM releases) and make these "full" releases.

regarding the asset names, maybe include the release date as well, like clangd-mac-20200209.zip
Done.

shall we include the SHA-256 Hashes for the release binaries?
I'm not really sure what this would achieve - would we sign them somehow? How would the source of the hashes be more trustworthy than the files themselves?

if something is broken during the release process, will we receive an alert notification?
It seems only the "triggering user" gets the notification. That's the user who creates the release, for periodic releases it's the dummy clangd-build user I created.


How to set a ?

Given the following render function of my component:
render() {
    return (
     <button>
       <slot />
     </button>
    );
  }

How can I set the <slot> content using the configuration in *.story.ts?

This is similar to #1 - and I have an idea to easily provide this functionality. This feature will be in my next update, which should be coming soon.

You're right, sorry. Feel free to close this as a duplicate. I'm eagerly awaiting your solution :)

Closing as duplicate


feature: add middleware to remove @mentions for MSTeams

Is your feature request related to a problem? Please describe.
Messages from MS Teams include an @mention of the bots name at the beginning of every message.  This generally needs to be stripped off using ActivityExtensions.RemoveRecipientMention() otherwise TextInput actions will include it as part of the users response. I ejected my host and customized my OnTurnAsync() implementation to include the block below but we should really formalize this into a piece of middleware that can be turned on & off as a feature like the inspection middleware.
       public override async Task OnTurnAsync(ITurnContext turnContext, CancellationToken cancellationToken = default(CancellationToken))
        {
            if (turnContext.Activity.Type == "message") {
                turnContext.Activity.RemoveRecipientMention();
            }

I have this same problem when I use botframework composer for creating a MS teams groupchat scoped bot. How do I fix this like you have done @Stevenic ? Or is there a permanent solution for this issue already?


Sheet and Tree Options Not Available in Linux

I'm running MediaInfo 17.12 on Xubuntu 18.04. I notice that the Sheet and Tree view is grayed out in the GUI (see image), and I also don't have access to the Properties window to create my own Sheet view like I do in Windows. The same version of MediaInfo gives me these options when I run it in a Windows 10 VM. Dragging multiple media files to MediaInfo in Xubuntu just opens up a separate instance of MediaInfo for each file. How do I get the Sheet and Tree views in MediaInfo on Linux?

It has not (yet) been implemented, it was a work in progress some time ago but stalled due to other priorities.


Deleting a user does not work

The delete button in the user table does not seem to do anything.
main.js [sm]:225 Uncaught TypeError: Cannot read property 'deleteUser' of undefined
deleteItem @ main.js [sm]:225
deleteUser @ main.js [sm]:195
onclick @ VM544 users:586

Fixed in latest PR


Wrong download value in the attributes

Hi!
I noticed you send twice the upload instead of sending the download.
Units seems to to bauds, can we convert them to ko/s or mo/s?
@property     def extra_state_attributes(self):         """Return extra state attributes."""         return {             "connection_type": self._client.connection_type,             "interface": self._client.interface,             "down_kb_per_s": self._client.up_kb_per_s,             "up_kb_per_s": self._client.up_kb_per_s,         }

Was just about to post this.

Fixed in v1.0.0


Feature request: use environments instead of vars

Now all chat configuration like showDateHeaders, messageUseMarkdown, avatarSize, etc, are simple variables and configured through methods from ChatView extension. It means, that it's possible to set them only locally, directly with a ChatView. I suggest to use EnvironmentValues instead that allows to setup all configs globally for the whole app and override them locally if needed.
Example:
extension EnvironmentValues {

   public struct Chat: Equatable {
     public var type: ChatType = .chat
     public var showDateHeaders: Bool = true
     public var avatarSize: CGFloat = 32
     public var messageUseMarkdown: Bool = false
     public var showMessageMenuOnLongPress: Bool = true
     public var tapAvatarClosure: TapAvatarClosure?
     public var mediaPickerSelectionParameters: MediaPickerParameters?
     public var orientationHandler: MediaPickerOrientationHandler = {_ in}
     public var chatTitle: String?
     public var showMessageTimeView = true
     public var messageFont = UIFontMetrics.default.scaledFont(for: UIFont.systemFont(ofSize: 15))
     public var availablelInput: AvailableInputType = .full
   }

   private enum ChatKey: EnvironmentKey {
     static let defaultValue = EnvironmentValues.Chat()
   }

   public var chat: Chat {
      get { self[ChatKey.self] }
      set { self[ChatKey.self] = newValue }
   }
}

extension View {

    public func chatView<T>(_ keyPath: WritableKeyPath<EnvironmentValues.Chat, T>, _ value: T) -> some View {
       environment(\.chat[keyPath: keyPath], value)
    }

    // convenience methods for each var if needed
}

Hey @dankinsoid, that way you won't be able to use different settings for different chats in the same app. If you need many chats which are all the same, please just create a custom view wrapping the chat with the setting you need and reuse it. Have a nice day

Benefits:

Ability to set up styles when we cannot modify the code of the view or create a wrapper. For instance, when we use a library that utilizes ChatView under the hood, or a view that wraps a ChatView.
Unified styling API. With a wrapper, you have to duplicate all styling methods to make it configurable.
Access to the current chat style from any view that depends on the chat view style, for example, InputViewContent and MessageContent. It can also be some custom overlay or something else.
Type independence: Currently, we have to write all chat style modifiers together and cannot insert any other modifiers between them. This is fine until we want to put some of them in a function to reuse.
Unification: SwiftUI has a type-erased API with implicit DI, and while this has its downsides, it is the default approach in SwiftUI.

Strictly speaking, all these reasons are more important for small, highly reusable views like buttons, texts, checkmarks, etc., and they are not as important for a ChatView. However, I like environments a lot; they are highly useful, convenient and perfect suits for any styling.

These are good arguments, however, there are two sides to most of them:

This is for example the case with MediaPicker library which I use inside ChatView. It is also our library, so I can modify it to use environment, but I don't want everything media picker can do to stick out of the chat. Not all the available setup is useful for a picker inside a chat. I'm limiting the MediaPicker to serve as a chat picker, cutting some functionality chat won't need. And it is always easier to support API which allow less - I cannot guarantee that everything will work as expected.
Why would you duplicate everything? Just reuse what you need for every chat only creating params for need to change.

struct MyChatView: View {
    // only params you are changing
    var showDateHeaders: Bool = true

    var body: some View {
        ChatView() {
            // all the other setup here - once per project
        }
    }
}

InputViewContent and MessageContent have everything they need inside their closures. In these closures there are things which cannot be set up through environment (view builders etc.). Since I want a unified approach I'm choosing a closure.
This is a benefit in my book. There is no sense in spreading chat config all over the project, so I'm forcing users to do it where it needs to be. And there is no point in setting up .buttonStyle or .font for a chat in between other modifiers - it will do nothing. Also, you still won't be able to put too much into a function since swiftUI forces me to pass the view builders as a generic on ChatView. Modifiers perform basically the same thing as these view builders - just initial chat setup, so they go together.
For a specific type (which ChatView undoubtedly is) SwiftUI gives specific API, for example .renderingMode on Image. Setting up . tapAvatarClosure  is not at all the same as setting padding and fonts. For a chatTheme I use the environment as is customary in SwiftUI.

The bottomline is - unfortunately I don't like environment approach. Why make global that which can be local? Narrowing the scope is the first thing I've been taught as a programmer. We have encapsulation principal for a reason, and I think making everything global, while convenient, is potentially dangerous and gets hard to track fast.
Summing up:

I want to manually control what is sticking out of libraries API, so I can better ensure that it works.
There is always a way to not duplicate code, environment is not the only approach.
I want a unified approach - I can do everything through vars; I can only so simple things through environment, and still will have to do the rest through vars.
All chat configuration should be done in one place (where the chat is used) - it is not a project wide component like texts and buttons
It's a pretty complicated component, with a very specific API, so one might be surprised to find its setup somewhere in AppView file
Better keep things as local as we can
As you said yourself, environment is a good fit for styling. Styling on this project is done through environment, everything else is not.


TextInput | No variant support

As a developer, I want to set a variant to the text inputs just like Dropdown and Button to make my form easily themeable.

I'll grab this one if no one has already.


Fix for single row grid plots in bokeh

The logic in bokeh GridPlots was wrong, which was causing single dimensional layouts to be the wrong shape and not appropriately hide the axes.

Good to know that the simpler version is correct! Merging.


Sample?

Any sample code on how to raise the onclicktoact event?  I've tried every way I know how

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 829606f3-febb-1082-5233-fc754fe79bbe
Version Independent ID: be5e2a6d-674d-c598-c667-6445917a4409
Content: onclicktoact event (JavaScript API Reference) for Dynamics 365 Channel Integration Framework (CIF) version 1.0
Content Source: ce/customer-service/channel-integration-framework/reference/events/onclicktoact.md
Service: dynamics-365-customerservice
GitHub Login: @susikka
Microsoft Alias: susikka

@potsiemj Thanks for the feedback. We will try to include a code sample in the topic. Please stand by till further updates.

@potsiemj Please refer to the latest documentation: https://github.com/microsoft/Dynamics365-Apps-Samples/tree/master/customer-service/channel-integration-framework

Closing the issue as there is no response from customer on the above comment.


Bump protobuf to 3.4, mockito to 1.4 and toml to 0.8

See https://github.com/lipanski/mockito/releases/tag/1.0.0 for the migration guide I referenced
If this gets merged then #21 can be closed as it would be redundant.

I did in two seperate commit as the first one contains all of the refactorings for the mockito bump while the second has all of the refactorings for the protobuf bump

See this issue for switching from  protobuf-codegen-pure to protobuf-codegen


Add information about Contributor License Agreement

https://learningportal.xprize.org/en/custom/contentrepository/view/3362
Only necessary for programmers with commit access?
What about content creators who add content to the web site?
[--- This issue is linked with an Asana task
#attachments Screenshot 2015-11-20 17.12.19.png, Global Learning Individual CLA.pdf
---[aa]

Guidelines:
[--- Commented from Asana.com
#commenter Jo Grimstad
---[aa]


Set complement dynamically or switch the position of complement and inner

Right now seems like this package only allow user to set up complement at the beginning and the position of inner and complement is "inner | complement".
Is it possible that use a title like "complement | inner"?
Or switch the position of complement and inner?

@C0deZLee
At the moment it does not have support for this, but I will give updated in the code and insert this functionality.


Update pubspec.yaml

Imho this is not a desired change because most people will upgrade to http 1 soon. You can use it from your featurebranch if you need it for your project, but I would not like to merge this.


GATK4 GenotypeGVCFs: allow in YAML user defined 'max_alternate_allele' parameter

Hi,
Would it be possible to allow user defined GATK4 GenotypeGVCF max_alternate_allele' setting in the bcbio YAML?
The default value GATK4 GenotypeGVCF max_alternate_allele=6  setting runs too slow for some of our species and cohorts and even incoming batches of samples. Lowering this parameter improves variants/per minute significantly and decreases memory requirement also significantly.
I also noticed that for GATK3 GenotypeGVCFs  this parameters already is hard coded to `max_alternate_allele=4 in bcbio:
https://github.com/chapmanb/bcbio-nextgen/blob/master/bcbio/variation/gatkjoint.py#L105
Could you share thoughts on the optimal setting of this parameter. We are still exploring the optimal performance cost and sensitivity trade off of this parameter.
Thank you.

Hi @chapmanb . I also opened a forum post at GATK about the slow performance about GenotypeGVCFs at max_alternate_allele=6.
https://gatkforums.broadinstitute.org/gatk/discussion/11471/performance-troubleshooting-tips-for-genotypegvcfs/p1
This post has now been escalated to a developer ticket (see last few comments of the forum post).
It turns out hat using the -new-qual optoin with GATK4 GenotypeGVCFs improves the performance a lot. Even with max_alternate_allele=6, which is the GATK4 default.
Hopefully Sheila in that forum post can confirm there are now downsides to that option.
So instead of making max_alternate_allele user configurable in bcbio, it might be better to implement -new-qual as a user configurable or default option for GATK4 GenotypeGVCFs.
Thank you.

Thanks much for your work diagnosing the issue and discussing with the GATK4 team. I swapped over to use the newer quals option as a default, which is an umabiguous win here. I've tested the new qualities in the past and they validated great but I believe the GATK team decided to stick with the older as default to try and match GATK3 as much as possible.
Please let us know if you run into any scaling issues after the change. Thanks again.


Reimplement fs.info() to not depend on fs.ls()

fs.info() now only queries the properties of its argument, instead of potentially doing a full listing of the parent directory, which should improve its performance in many cases.
Fixes #377 and #380.
Note: this PR contains refactorings of related methods that I ended up not modifying otherwise, I could split them off if that makes reviewing easier.

This is nice @rlamy .  Thanks!


CRS tests for semaphores and CBs

@tt-aho , tagging you here in case you have bandwidth for this. When I looked at semaphores and CBs bringup for FD2, I didn't see anything that actually tested the "set" in CRS for these two. I added a test for runtime args test_dummy_EnqueueProgram_with_runtime_args_multi_crs

Start with Semaphore for now. We want to add a test for fast dispatch for core range sets for semaphores. Add it to tests/tt_metal/tt_metal/unit_tests_fast_dispatch/command_queue/test_EnqueueProgram.cpp similar to CommandQueueSingleCardFixture, TestSingleSemaphoreConfigCorrectlySentSingleCore.

Extend CoreRange cr({0, 0}, {0, 0}) to two core ranges.
Write different initial semaphore values to the two ranges.
Readback and check that values are correct.


How to create mobile app for Camaleon CMS and subdomains

Hi @owen2345,
Can you please let me know how to create mobile for camaleon website and its subdomain.
it would be great if you can suggest a way to access camaleon subdomain sites by creating a mobile app. Thanks.

Hi @mazharoddin ,
I think you need to use the api mode of rails and using the helper method of camaleon cms:
current_site() which get the Site according to your domain/subdomain,...
Regards,

Thanks @owen2345, yeah using API we can create an app, but just wondering is there any other way to create it.

For now there is not other way, in the future I will create a small API plugin for camaleon ready to integrate with AngularJS.
Regards,

ohh ok, Thanks @owen2345 ..


Rachael

These changes should go into your own repository

These changes should go into your own repository

Hi! I think the merge request was an accident. All the changes are in my repository and the website is up and running. How do I know if the technical onboarding was successful?

Looks like you are good to go @rachaeltdias ! Well done


Need tableData along with tableActions to pass down data to custom components

Hi!
I am building out a custom component to use to display my column headers, so that I can filter table results by each column with an additional {{input}}.  I am able to successfully pass down an action to handle filtering on key-up for my filter input by doing:
{{#light-table table tableActions=(hash filterColumn=(perform filterColumn)) as |t|}}

I am using the tableActions approach, instead of the "curried components" approach laid out in issue 405.  So I am also passing the initial filter values and state through tableActions as a workaround to have that information available to use in my custom column component (say that fast 5 times...).  It may be helpful in the future to split it out into actions and data so it could be done like this:
{{#light-table table
    tableActions=(hash filterColumn=(perform filterColumn))
    tableData=(hash filters=filters) as |t|}}

Thanks for all your hard work!

IMHO this is a great addition as it mirrors / complements tableActions. However, users must be aware, that they need to properly diff tableData, if they want to react to state changes. Pure computed properties shouldn't require any diffing though.
I can't think of any other performance implications as of now.
@alexander-alvarez your opinion?
A PR will be greatly appreciated. 😊

So kind of like the extra argument in ember-power-select?

Object to store any arbitrary configuration meant to be used by custom components

I think it would be a :+1: feature

Exactly.
@veberle-CSD up for a PR including tests? 😊 If you don't have the time, that's alright. I'll probably get around to it next week then.

If we want to talk semantics: I think we should use extra instead of tableData, so we can organize around similar APIs to what people may be familiar with, that and in my mind I associate the rows as being the table's data.

@buschtoens Yeah, I can make a note to try and put together a PR with tests over the weekend and post it by next week.
@alexander-alvarez That sounds good!


Incorrect rendering of API documentations that contains stars

Describe the bug
An API documentation that contains a star (*) is interpreted as a formatting syntax instead of content.
To Reproduce
Steps to reproduce the behavior:

Go to https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.mvcoptions.respectbrowseracceptheader?view=aspnetcore-2.2
Read the summary.

It says

Gets or sets the flag which causes content negotiation to ignore Accept header when it contains the media type /. false by default.

Note the missing stars around the slash.
HTML code for that summary: Gets or sets the flag which causes content negotiation to ignore Accept header when it contains the media type /. false by default.
Expected behavior
Expected text per source:

Gets or sets the flag which causes content negotiation to ignore Accept header when it contains the media type */*. false by default.

Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: Firefox
Version: 66.0.3

@TianqiZhang @mimisasouvanh can you take a look at this issue?

#logsuggestion

#log-suggestion

@mimisasouvanh can you log this suggestion?

@mairaw */* was treated as markdown syntax. Is it possible to escape * in the source and make it \*/\*?


STY: add ruff-format and remove flake8

The maintainer of flake8 can be a bit difficult, so nice to remove. I will add ruff the linter in a separate PR, but would be nice to get formatting done first. ruff-format is basically faster black (but some subtle differences).
Reviewed-by: Saransh Chopra<EMAIL_ADDRESS>

This will mess up git blame's output. A good practice is to add the commit where ruff made the formatting changes to a new .git-blame-ignore-revs file. For example, PyBaMM's .git-blame-ignore-revs file -<EMAIL_ADDRESS>
Wasn't aware of this idea to combat git blame, have added the file

The commit where ruff made the changes will get squashed, so we should add that file not here but in a PR immediately after.
Also, why not add the linter in this PR as well, so we only incur one massive changeset?

The commit where ruff made the changes will get squashed, so we should add that file not here but in a PR immediately after.

Ah, that too. This makes more sense then.

The commit where ruff made the changes will get squashed, so we should add that file not here but in a PR immediately after.

Yeah I wasn't sure on this

Also, why not add the linter in this PR as well, so we only incur one massive changeset?

Because formatting changes and linting changes are different. I think it will hide a lot more changes that way.

I have updated from main. I am going to merge, and then update the commit for the git blame file

Have merged directly https://github.com/glass-dev/glass/commit/e01b40ec11278be4aa02d52c9ad76ce09bc19a6a


Upcoming programming contests added

Adding feature of issue #164
Some of the sample queries are:

upcoming cp contests
programming contests
cp contest
competitive programming contests

Any update?

@torquecoder  Let's fix the tests please, one of the tests is  failing, :)


Consider showing local bindings for type hole substitutions in 8.4.3

Since GHC does not show local bindings as valid substitutions in 8.4.3, it would be cool to append the Relevant bindings include section in the bottom of the list.
One heuristic could be that if the only valid substitution is undefined or the error* functions, then appending the local bindings for help may be a good idea.
Additionally, I think it would be helpful to show the type of the binding as part of the substitution. For instance, it could read as follows:
Substitute hole (ShellCheck.AST.Token) with allFlags (ShellCheck.AST.Token -> [String])
Substitute hole (ShellCheck.AST.Token) with hasYesOption (ShellCheck.AST.Token -> Bool)
Substitute hole (ShellCheck.AST.Token) with undefined

I've followed previous commits on implementing this feature, so I think I may be able to help implement this if you think it is a good idea.

That sounds good to me! I think you should be able to hack away at GhcMod.hs for these code actions


Exponentiation operator error with negative base

Trying to parse ((-1) ** 2); fails with the following error, despite already being wrapped in parens:
Illegal expression. Wrap left hand side or entire exponentiation in parentheses. (1:3)
> 1 | ((-1) ** 2);
    |    ^

both Firefox 49 nightly and Traceur parse -1 ** 2 without requiring parens (despite what MDN says should happen).

Thanks @mroch -- I think this is the same as https://github.com/babel/babylon/issues/26 though? (Maybe that could use a better title?)

indeed, not sure why i didn't see that


Check possible problems of Editor users using new migrated pages

Context
We plan to serve all static pages from NGINX. That means that Editor users will be using our migrated static pages:

Dashboard
Profile
Account

It' likely that we won't have any problem but we need to check it.
So far, the biggest problem we've faced with a similar scenario was the preview of fav maps. This isn't going to happen in these pages since we don't preview the map.
Profile and Account are already migrated so we can pass an acceptance with an Editor enabled users.
For Dashboards we can perform this check while it's being migrated since static pages serving will start on May.
Please use this ticket to write down any discovery on this topic, bad or good.

I have checked if there can be any wrong behaviour in these pages (profile, and account) when accessed by Editor users.
In these two pages, there is nothing related to visualizations. These pages contain forms to allow the users modify its own data (email, password, website, location, description, twitter username, and disqus shortname, third party services accounts), and delete its account.
Both forms send a request to api/v3/me when retrieving and updating the user data, so AFAIK, there won't be any issue with these pages as long as the backend/API provides the same response to the requests made by both type of users.

Anything left to do here? Can we move/close this card?

I think we can close this one.
Static and non-static pages FF have been removed. So, if any problem arises, we'll know through support.


Operator Precedence table is missing ops

I'm failing to find ∘ op or any of the set ops on https://docs.perl6.org/language/operators#Operator_Precedence

∘ is level "Concatenation"
most(all?) of set ops are level "Junctive or" or "Chaining infix".
see the below
https://github.com/rakudo/rakudo/blob/3405001da07b7062a19fd6343bab6112128319f3/src/Perl6/Grammar.nqp#L4424-L4492
Then, the table's third col is with title "Examples", should we document all ops?
Last, ∘ is under the head =head1 Concatenation, which implies its precedence.
I prefer mention set ops' precedence in https://docs.perl6.org/language/setbagmix#Set/Bag_Operators

Ok. Thanks.

FWIW, b56885bfe7 ("Improve documents on set ops")


⚠ Senior School Website has degraded performance

In ae79b9b, Senior School Website (https://www.cranleigh.org) experienced degraded performance:

HTTP code: 200
Response time: 21626 ms

Resolved: Senior School Website performance has improved in 4067a84.


Flag useless rubocop:enable comments

# rubocop:disable ... comments are flagged if they don't actually suppress any offenses. This is good and helps to keep a codebase clean of extraneous junk.
We should do the same for # rubocop:enable comments, which enable a cop which was never disabled.
Does anyone see any problem with this?

Makes sense :+1:

@alexdowad: Are you still working on this / planning a PR? I see you have an implementation in your fork from a while ago (https://github.com/alexdowad/rubocop/commit/2530eba0eb5ea0c8c4b1a56a9b2c54bcdb0ba735) but it's not in rubocop proper.
I was independently wanting this feature and thinking about taking a stab at it but I decided to check the issue tracker to see if anyone else had suggested it before and found this.

@dgollahon, please go ahead. If the code in my commits is useful, please take whatever you want and don't bother crediting me. I don't have any interest in this problem right now and don't care what anybody does with this code. Or if you prefer to start from scratch, that's up to you.

@alexdowad: Great, thanks. :) I'll look into it.

@dgollahon: Did you end up making any progress on this? 🙂

@Drenmi: No, I got sidetracked by another project D: If you're interested in taking it over, that's fine by me. :) If not, I might be able to take a crack at it soon but I'm not sure exactly when.

@dgollahon: No worries. I have my eyes set on other things at the moment, and I think this issue is buried deep enough that you'll be able to come back to this when you have more time. 😉


How to add custom environment name in UI

Hi,
I want to add or display our  custom environment name in Configure Delivery Pipeline currently DEV,QA,INT,PERF,PROD environments are available.
suppose i want to add environment one new environment SIT for that how to configure or which file i have change?? or is it possible to change the existing display environment names in UI.

PR #1020 adds this functionality but has not been accepted yet.

Kindly send me the latest packge link once merge your changes in to master

It would be easiest to wait for them to get merged in.
You can build the branch here: https://github.com/paychex/Hygieia/tree/feature/TAXSDLC-1100

Sure Kindly send me  the latest link once you merge the changes into master branch.and also explain how to change our environment names.

@MarkRx
Hi,
Reg  https://github.com/paychex/Hygieia/tree/feature/TAXSDLC-1100  bild merge was completed on master branch? Kindly send me the link.

Ask @tabladrum @amitmawkin :)

Hi @tabladrum  @amitmawkin,
Reg https://github.com/paychex/Hygieia/tree/feature/TAXSDLC-1100 build merge was completed on master branch? If merge was completed Kindly send me the link.

Hi @tabladrum and @amitmawkin,
Reg https://github.com/paychex/Hygieia/tree/feature/TAXSDLC-1100 build merge was completed on master branch? If merge was completed Kindly send me the link.
Kindly respond

@vetrivelan25  - Update to latest code base and use the pipeline widget to customize the stage names for deployed environments.


Feature: save sound settings

I think it can be great if we can save the sound settings instead of change it every time we start our browser.
What do you think?

Just to add an example of why this would be great: as I just mentioned in #8, I'm half-deaf so having (almost) all browser audio default to a mono mix by default would be a fantastic quality of life improvement

@JobLeonard any reason not to use a system-wide setting for that?
The addon has really been intended for the rare "one particular piece of media is screwed up" situations; adding any kind of persistence that would mess with pages automatically instead of directly in response to user input doesn't sit right with me. Imagine a user saving some setting, removing the icon from the toolbar, forgetting about the addon, and wondering why the hell is sound weird in Firefox – on many sites except not on some because there are things SoundFixer cannot touch due to security restrictions. (Those existing is also a good reason to turn to your operating system for help instead.)

@JobLeonard any reason not to use a system-wide setting for that?
The addon has really been intended for the rare "one particular piece of media is screwed up" situations; adding any kind of persistence that would mess with pages automatically instead of directly in response to user input doesn't sit right with me. Imagine a user saving some setting, removing the icon from the toolbar, forgetting about the addon, and wondering why the hell is sound weird in Firefox – on many sites except not on some because there are things SoundFixer cannot touch due to security restrictions. (Those existing is also a good reason to turn to your operating system for help instead.)

I understand. What if we could have a toggle button in extension itself which says to persist setting or not. Users who want to save settings can toggle them on. It should be disabled by default.
This could really help a user like me, who has to visit a site regularly which has really bad / low volume by default and there is no way to amplify it except this amazing extension. I literally have to increase gain every time.
I even forked your repo and tried to add persistence using chatgpt 😆 but couldn't succeed in implementing this feature as I don't have much experience of developing browser extensions. I mean I can do this as well but it will take some huge effort (may be days) for me to understand and then plugin this required functionality.
If you can do this easily that would be really helpful and owsm!
Again I really appreciate your efforts for maintaining this extension.

@JobLeonard any reason not to use a system-wide setting for that?

Well, this is a bit specific but here goes: I'm not exactly 100% deaf on the left ear, "just" 50% but it's almost all in the middle range of frequencies used for speech. That means I prefer mono for music, for example.
However, I can still use binaural beats outside of that middle frequency range, which I often do to either focus or relax. Binaural beats only work with stereo. On a similar note, noise generators (which I use for noise blocking) are more pleasant in stereo. I do none of those things via the browser.
Also the system-wide mono setting is a bit finicky, given the lack of GUI controls or built-in keyboard shortcuts (I use Linux, fwiw). I have to figure out some command-line invocation to switch it on or off, and also do so every time I connect or disconnect my bluetooth headphones.
I totally understand that this is is a very specific scenario and not within the original scope of the add-on, so if you don't feel like adding it I won't complain. And I agree that persistent settings by default would not make sense. But opt-in persistency for people like me would be very nice.


Comment cannot be longer than 150000 characters

Describe the bug
When applying multiple changes with the help of AzOps you might run into a bug that the comments cannot be larger than 15000 characters.
Steps to reproduce

Full deployment of Enterprise Scale Policies  json

Screenshots

This is partly mitigated by #482
The failure should be solved by #470
Do we still want to improve the what-if results comment feature or can this issue be closed?

This is partly mitigated by #482
The failure should be solved by #470
Do we still want to improve the what-if results comment feature or can this issue be closed?

Given that #470 solves the failure, we will close this one for now and track potential future enhancements in separate issues.


fix avatar border opacity

Details

The avatar border overlaps the other avatar when we apply an opacity.
Fixed Issues

$ https://github.com/Expensify/App/issues/15283
PROPOSAL: https://github.com/Expensify/App/issues/15283#issuecomment-1439413441
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Same as QA Steps
QA Steps

Open any chat
Turn off the internet
Send/Request money
Verify the IOU preview
Click the IOU preview to open the detail
Verify the IOU preview avatar border inside the detail page is not semi transparent

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@joelbettner @rushatgabhane One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

I want to explain why I added needsOffscreenAlphaCompositing to ReportActionItem too. So, the IOU preview used in the chat item here is inside IOUAction which is a child of ReportActionItem. ReportActionItem also has its own OfflineWithFeedback.

https://github.com/Expensify/App/blob/7e8e8a1d881914abe7c13768eb13e4930cb8546b/src/pages/home/report/ReportActionItem.js#L230-L253
So, it looks like this

To apply the opacity, we need to have the pendingAction, but we don't pass it from ReportActionItem to the IOUPreview nested inside it and I believe this is intended because if we pass it down, the opacity will be applied twice which makes the component becomes blurrier.
Little example of the double opacity.

Interesting. Actually, it happens to me once, then I reload it and it works fine. I guess there is something wrong with the file save. Now, I can always reproduce it. Turns out, needsOffscreenAlphaCompositing default value is true. It is only false for Android as you can see at the image below.

I decided to give it undefined if it's not android, so it will use the default value for each platform.

If RN decided to change the default value from true to false, then that means they have a concern about it. Maybe there is a bug on newer versions, or it make things slower, etc. I think we don't really need to care about the default value changes, just like the other props that we don't explicitly set the values.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.2.88-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.2.88-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Update demux maturity implementation with the new tag system.

I update the merge policy so that we can correctly identify the splits to demux.
Few notes:
I was very surprised by the usage of the special tag tag_field! which indicates that, for a given split, the field is registered as tagged, I was expecting a special tag like "indicates that there are no tags in a split" like described in #887 examples. It's working well and I understand why this is like this, it was just me that did not understand correctly the usage.
Just to be clear, I will rewrite the example I wrote in #887:
split_1: no tag values => metadata contains tag_field!
split_2: contains one value tag_field:value => metadata contains tag_field:value and tag_field!
split_3: too many tag values => metadata tags is empty
split_4: tag_field was not configured as a tag field at that point. metadata does not contain tag_field!.
@fulmicoton can you confirm that this is the implementation you have in mind when you open issue #887?
I added some documentation as it's not super easy to understand.

@fmassot this is correct.


vimeo sound fix after fixing the vimeo API error

I can confirm this works better, sound works in more videos than before changes.

me too:
I can confirm this works better, sound works in more videos than before changes.


Fix DLL install directory in mingw

This installs DLL in 'bin' directory instead of 'lib' by default. In mingw environment, all DLLs and EXEs are installed in 'bin' and static & import libraries are installed in 'lib' directory. This does not affect other environment because the 'RUNTIME' and 'LIBRARY' targets are automatically set by cmake. See https://cmake.org/cmake/help/latest/command/install.html
Fixes https://github.com/mfem/mfem/issues/2913

/cc @3rav

Hi @Biswa96 and @3rav, is this ready for merging?
If so, can you please mark it with the ready-for-review label?

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...

Thanks for this contribution @Biswa96 and sorry for the delayed merge (it slipped through the cracks)


Associated Iteration should be grayed while Re-associating  the WI

Associated Iteration should be grayed while Re-associating the WI
Expected :
When "Iteration 1" already associated with WI , in that case While re-associating WI with iteration , it shouldn't show the   "Iteration 1" or it should be grayed
Video link: https://drive.google.com/a/redhat.com/file/d/0B1qUq_laG6COWFlleWdzeDU4ZFk/view?usp=sharing

@fabric8io/uxd , need your input on this !

@Essjaysee can you comment on this?

@naina-verma Great catch!  In this case, let's keep the iteration in the list, but show the it as disabled/greyed-out so you can see where the it lies within the hierarchy.


Round trip from blocks -> ts -> py -> ts -> blocks gives back identical blocks

After much ado, I settled on fixing this bug by centralizing and introducing a cache around the ts->py and py->ts transpile operations. This is done in the compiler code, so in the worker.
Probably a better, longer term fix would be to implement a "MultiViewFile" abstraction in the webapp that encapsulates all language conversions (including blocks, which was the difficult part that I punted from this PR), tracking equivalence and keeps the trio [blocks, ts, py] in sync. Discussed this in person with @riknoll . This would allow us to remove a lot of code in the webapp and elsewhere that does things like "convert from A to B and then back to A to see if things have changed" and it would likely eliminate several race conditions.
But this PR is not that, it just handles the ts <-> py case.
Fixes:
Bug repro:

open Space Destroyer in blocks
convert to python and back to blocks
notice blocks have changed

Can we revert the "generated" -> "outfiles"? it would remove a bunch of changes.

Can we revert the "generated" -> "outfiles"? it would remove a bunch of changes.

Yeah but I think it's worth it. The data structure we use almost everywhere is "CompileResult" which has an "outfiles" property. For whatever reason ts2py had it's own output data structure that had a "generated" property that contained exactly the same information. This was inconvenient in this PR because I was trying to standardize the interface. "TranspileResult" is a strict subset of "CompileResult".

Sounds good!

Can we get a build for testing?

Can we get a build for testing?

I forget the cmd for that.. what is it again? I can't find it in my notes

pxt uploadtrg

pxt uploadtrg

ty. my local build isn't working (I always use --rb and there's no --rb option for uploadtrg? Is that intentional), I'll try to get it sorted out..

What is -rb ?

rebundle

Any ticks to be added to measure where those happen?

Like ticks inside the transpile.py2ts and .ts2py functions? It'd would be very noisy. A single ts->py->ts round trip calls those functions ~6 times for unclear reasons.
Coincidentally, I think we'll get a perf win from this PR because of that inefficiency.
I believe the important tick is when the user switched languages which I believe we have already.

LGTM

Can we get a build for testing?

https://arcade.makecode.com/app/ae2dc3a32fd5dfc641beadfcad7f6ff70ffb8414-9ab6c5d9b6

project

Do you (also @pelikhan, @mmoskal ) know if anything with:
interface CompileOptions {
        fileSystem: pxt.Map<string>;
        target: CompileTarget;
        testMode?: boolean;
        sourceFiles?: string[];
        generatedFiles?: string[];
        jres?: pxt.Map<pxt.JRes>;
        hexinfo: HexInfo;
        extinfo?: ExtensionInfo;
        noEmit?: boolean;
        forceEmit?: boolean;
        ast?: boolean;
        breakpoints?: boolean;
        trace?: boolean;
        justMyCode?: boolean;
        computeUsedSymbols?: boolean;
        name?: string;
        warnDiv?: boolean; // warn when emitting division operator
        apisInfo?: ApisInfo;
        bannedCategories?: string[];
        skipPxtModulesTSC?: boolean; // skip re-checking of pxt_modules/*
        skipPxtModulesEmit?: boolean; // skip re-emit of pxt_modules/*

        syntaxInfo?: SyntaxInfo;

        alwaysDecompileOnStart?: boolean; // decompiler only
        allowedArgumentTypes?: string[]; // decompiler-only; the types allowed for user-defined function arguments in blocks (unlisted types will cause grey blocks)

        embedMeta?: string;
        embedBlob?: string; // base64

        /* @internal */
        ignoreFileResolutionErrors?: boolean; // ignores triple-slash directive errors; debug only
    }

changes when the dependencies change? Probably ApisInfo?
My goal is to create a hash representing the current dependencies.

We always reload the header when dependencies change.

We always reload the header when dependencies change. So resetting your cache is enough to handle this case.

Which header?

Using all the qNames as part of the cache key seems to be working well.
(btw I FAR prefer to use a stronger cache key than count on some event to clear the cache. Much less error prone, easier to refactor, no races, and it's truly functional. Invalidating a cache due to some event is a last resort and it's usually an anti-pattern. Caching should simply be memoization whenever possible. IMHO.)
However, now after I've merged master it appears things have regressed. I'm getting an error when going ts->py on Space Destroyer so I'm looking into that.

In CompileOptions.sourceFiles, you should be able to look at pxt.json. I don't know if that would mess up @mmoskal's two tab extension editing though.

header is the internal name for a script/program. We reload the entire user package (header) when pxt.json is modified because toolbox and other stuff need to be refreshed.  At that point, you should invalidate this cache.

See https://github.com/microsoft/pxt/blob/cf7e498116fef6b52cf22852454b4b0c713550a5/webapp/src/monaco.tsx#L1135

reloadHeaderAsync

I'd really think it's a bad idea to invalidate caches based on an event. This turned into a huge pain when I did the caching around the blockly flyout and it was brittle an hard to refactor around.
I think its better to just capture the dependencies in the cache key. Then they'll automatically be invalidated and there won't be any race between something trying to read the cache right when the dependencies are invalidated, etc.

Watching pxt.json is not enough. If you have a local dependency, the content of the dependency may have changed in another tab (this happens with double-tab testing). This is why we reload the program when you enter a tab.

Wait, I'm hitting an exception, need to investigate:
[ ] Fix null exception, probably https://github.com/microsoft/pxt-minecraft/issues/1472 will need to be fixed.

Cache needs to be cleared when project dependencies change

Fixed. See "resetCache"


update sqlite3 driver from 1.14.10 to 1.14.13

There is several tests using go-sqlite3 driver in this project.
It had to opt-in for using JSON functions.
Update go-sqlite3 driver, and we can run tests without -tags=json1.
I updated modules and modified the documentation and ci.yml.
mattn: "Released go-sqlite3 v1.14.13 json tag is now the default."
https://twitter.com/mattn_jp/status/1524936967720665088
For more detail is following page.
https://github.com/mattn/go-sqlite3/pull/1019

I fixed a CI failure.
This CI tests current master branch in a part of step of 'migration'.
https://github.com/ent/ent/blob/f7771e730f649de077b9869362565110430e8382/.github/workflows/ci.yml#L410-L414
I don't feel that I need this part of step.
To remove a remaining -tags=json1, I have to follow up after merge.

Thanks for the contribution @stoikheia 🙏

remaining unnecessary build flag -tags=json1 has been deleted.
https://github.com/ent/ent/pull/2672


Dev CES.jl to docs

I'm having some issues with the build in #26, so this just adds CalibrateEmulateSample.jl to the docs environment, and updates the packages all around.

bors r+

bors r+


feat: use vite build system instead

This closes #2472.

Please review and test it carefully as I may miss something important.

Thank you for the PR - a few things:

We can't change the names of the files generated as it's breaking. So need to keep the browser files and .mjs
Need to keep the ESM import map (import), so .d.mts files have to also be generated as well
The non .min files shouldn't be minified


Customization of about us page

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The about us page is not responsive for mobile devices and the about us button in home page should redirect in about us page
Expected behavior
Want to update responsiveness to about us page
Add ScreenShots
No response
On which device are you experiencing this bug?
Android
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

please assign this issue to me .

@azhar47-sk, are you working on that bug?

Yess


User guide for Istio Vault integration

Describe the feature request
User guide for Istio Vault integration. This user guide will be placed under https://preliminary.istio.io/docs/tasks/security/.
Describe alternatives you've considered
None.
Additional context

@lei-tang since PR 3098 was merged, can this issue be resolved?

@aerotog Yes, the issue is resolved.


Is Hydra much slower than Mamba?

I tried unit testing a single block and it seems like Hydra is at least 4x slower. Is that expected?

It is not expected to be 4x slower. It could be possible due to GPU memory constraints, or Mamba2's autotune of Triton is not optimized for your GPU. Please try the memory efficient version using use_mem_eff_path=True.

This is the code I use to test:
import torch
import torch.nn as nn
import flash_attn
from mamba_ssm import Mamba
from hydra import Hydra

HH = [1,2,4,8,16]
# HH = [2,4,8,16,32]
CC = [32,64,128,256,512]
TT = [198656,70656,18432,5120,994]
num_trials = 1000

with torch.no_grad():
    for i in range(len(HH)):
        H = HH[i]
        C = CC[i]
        T = TT[i]
        print('num_tokens:', T, 'channel_size:', C, 'num_heads:', H)

        scale = (C // H) ** -0.5
        x = torch.randn(T,C).cuda()

        if T == 198656:
            cu_seqlens = torch.tensor([
                0,   1024,   2048,   3072,   4096,   5120,   6144,   7168,   8192,
                9216,  10240,  11264,  12288,  13312,  14336,  15360,  16384,  17408,
                18432,  19456,  20480,  21504,  22528,  23552,  24576,  25600,  26624,
                27648,  28672,  29696,  30720,  31744,  32768,  33792,  34816,  35840,
                36864,  37888,  38912,  39936,  40960,  41984,  43008,  44032,  45056,
                46080,  47104,  48128,  49152,  50176,  51200,  52224,  53248,  54272,
                55296,  56320,  57344,  58368,  59392,  60416,  61440,  62464,  63488,
                64512,  65536,  66560,  67584,  68608,  69632,  70656,  71680,  72704,
                73728,  74752,  75776,  76800,  77824,  78848,  79872,  80896,  81920,
                82944,  83968,  84992,  86016,  87040,  88064,  89088,  90112,  91136,
                92160,  93184,  94208,  95232,  96256,  97280,  98304,  99328, 100352,
                101376, 102400, 103424, 104448, 105472, 106496, 107520, 108544, 109568,
                110592, 111616, 112640, 113664, 114688, 115712, 116736, 117760, 118784,
                119808, 120832, 121856, 122880, 123904, 124928, 125952, 126976, 128000,
                129024, 130048, 131072, 132096, 133120, 134144, 135168, 136192, 137216,
                138240, 139264, 140288, 141312, 142336, 143360, 144384, 145408, 146432,
                147456, 148480, 149504, 150528, 151552, 152576, 153600, 154624, 155648,
                156672, 157696, 158720, 159744, 160768, 161792, 162816, 163840, 164864,
                165888, 166912, 167936, 168960, 169984, 171008, 172032, 173056, 174080,
                175104, 176128, 177152, 178176, 179200, 180224, 181248, 182272, 183296,
                184320, 185344, 186368, 187392, 188416, 189440, 190464, 191488, 192512,
                193536, 194560, 195584, 196608, 197632, 198656], dtype=torch.int32).cuda()
        elif T == 70656:
            cu_seqlens = torch.tensor([    0,  1024,  2048,  3072,  4096,  5120,  6144,  7168,  8192,  9216,
                    10240, 11264, 12288, 13312, 14336, 15360, 16384, 17408, 18432, 19456,
                    20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696,
                    30720, 31744, 32768, 33792, 34816, 35840, 36864, 37888, 38912, 39936,
                    40960, 41984, 43008, 44032, 45056, 46080, 47104, 48128, 49152, 50176,
                    51200, 52224, 53248, 54272, 55296, 56320, 57344, 58368, 59392, 60416,
                    61440, 62464, 63488, 64512, 65536, 66560, 67584, 68608, 69632, 70656],  dtype=torch.int32).cuda()

        elif T == 18432:
            cu_seqlens = torch.tensor([    0,  1024,  2048,  3072,  4096,  5120,  6144,  7168,  8192,  9216,
                    10240, 11264, 12288, 13312, 14336, 15360, 16384, 17408, 18432],  dtype=torch.int32).cuda()
        elif T ==  5120:
            cu_seqlens = torch.tensor([   0, 1024, 2048, 3072, 4096, 5120], dtype=torch.int32).cuda()
        elif T == 994:
            cu_seqlens = torch.tensor([  0, 994], dtype=torch.int32).cuda()

        qkv_proj = torch.nn.Linear(C,C*3).cuda()
        total = 0
        count = 0
        for i in range(num_trials):
            start = torch.cuda.Event(enable_timing=True)
            end = torch.cuda.Event(enable_timing=True)
            start.record()
            qkv = qkv_proj(x)
            feat = flash_attn.flash_attn_varlen_qkvpacked_func(
                qkv.half().reshape(-1, 3, H, C // H),
                cu_seqlens,
                max_seqlen=1024,
                dropout_p=0.0,
                softmax_scale=scale,
            ).reshape(-1, C)
            end.record()
            torch.cuda.synchronize()
            elap = start.elapsed_time(end)
            if i > 100: # warmup
                total +=  elap
                count += 1
        print('flash attention', total / count)

        hydra = Hydra(
            d_model=C, # Model dimension d_model
            d_state=1,  # SSM state expansion factor
            d_conv=3,    # Local non-causal convolution width
            expand=2,    # Block expansion factor
            use_mem_eff_path=True
        ).to("cuda")

        total = 0
        count = 0
        for i in range(num_trials):
            start = torch.cuda.Event(enable_timing=True)
            end = torch.cuda.Event(enable_timing=True)
            start.record()
            y = hydra(x.unsqueeze(0))
            feat = feat.view(-1, C)
            end.record()
            torch.cuda.synchronize()
            elap = start.elapsed_time(end)
            if i > 100:
                total +=  elap
                count += 1

        print('hydra', total / count)

        mamba = Mamba(
            d_model=C, # Model dimension d_model
            d_state=1,  # SSM state expansion factor
            d_conv=4,    # Local convolution width
            expand=2,    # Block expansion factor
        ).to("cuda")

        total = 0
        count = 0
        for i in range(num_trials):
            start = torch.cuda.Event(enable_timing=True)
            end = torch.cuda.Event(enable_timing=True)
            start.record()
            y = mamba(x.unsqueeze(0))
            feat = feat.view(-1, C)
            end.record()
            torch.cuda.synchronize()
            elap = start.elapsed_time(end)
            if i > 100:
                total +=  elap
                count += 1

        print('mamba', total / count)

This is the results on RTX3090:
num_tokens: 198656 channel_size: 32 num_heads: 1
flash attention 1.4398738327493126
hydra 5.19853590009475
mamba 1.2737170286783255
num_tokens: 70656 channel_size: 64 num_heads: 2
flash attention 1.2244021445678523
hydra 3.9700514180243878
mamba 0.9193982243272698
num_tokens: 18432 channel_size: 128 num_heads: 4
flash attention 0.5656079320409009
hydra 2.4510892373701356
mamba 0.6655043213067782
num_tokens: 5120 channel_size: 256 num_heads: 8
flash attention 0.37106161046611585
hydra 2.1477266787421847
mamba 0.5596496043136309
num_tokens: 994 channel_size: 512 num_heads: 16
flash attention 0.2605083365328983
hydra 2.1441056672670156
mamba 0.4217387858169097

which shows Hydra to be at least 4x slower than Mamba.
Can I know what's wrong with this test?

Try with these please

Turn AMP on, and convert x to bf16 or fp16
Compare modules with practical settings: d_state >= 16

Tried this, get a little bit faster, but still much slower than Mamba
For my application, d_state doesn't make much difference, so I only use d_state=1. The num_tokens, channel_size and num_heads tested above are actual settings used in my network. It is for an edge device and cannot support large models.

Does that mean that hydra is only competitive in large networks?

I don't think we are planning to, but I agree that it should be much more optimizable by fusing together more kernels. Would love to see community contributions here!

@Hprairie How do you fuse kernels together to increase speed?

You have to rewrite the Mamba2 kernel so that you process both the forward and backward scan. If you do it right then you will load less data and perform fewer floating point operations, saving a chunk of time. I'm working on an implementation rn in my free time, I'll send a link when it's finished, however, I'm busy with other work so it might be a couple weeks.

For anyone interested, I have the fwd pass implemented and am working on the bwd pass rn. I have created a repo, where I will have the final kernels. A link can be found here: https://github.com/Hprairie/Bi-Mamba2
TLDR for benchmarking, the fwd pass has a slight overhead over the causal mode, which is to be expected. However, it is much better than flipping, especially since flipping in Pytorch will make a copy of the tensor.
Here is a comparison of a causal mode and a bidirectional mode:
Bidirectional Mamba Performance:
    seqlen  Causal Mamba2  Bi-Mamba2
0      2.0       0.109965   0.213840
1      4.0       0.108999   0.209290
2      8.0       0.107039   0.205770
3     16.0       0.106830   0.212640
4     32.0       0.110320   0.213240
5     64.0       0.111790   0.218340
6    128.0       0.126460   0.219845
7    256.0       0.137930   0.218290
8    512.0       0.113160   0.220190
9   1024.0       0.148601   0.228861
10  2048.0       0.215160   0.246040
11  4096.0       0.353721   0.437680
12  8192.0       0.579841   0.722961

I also want to note that these kernels aren't exactly the same as Hydra. The equation for Hydra is essentially:
$$ y = shift(SS(x)) + flip(shift(SS(flip(x)))) + Dx $$
While this kernel does this:
$$ y = SS(x) + flip(SS(flip(x))) + Dx $$
I do this as it makes it really simple to implement, however, later down the line I might add a kernel for Hydra.

This is awesome, thanks for the contributions Hayden!

For anyone interested, I have the fwd pass implemented and am working on the bwd pass rn. I have created a repo, where I will have the final kernels. A link can be found here: https://github.com/Hprairie/Bi-Mamba2

Awesome!!! Really looking forward to your work !!!


Expose DeployerValidator as a common service

There is a necessity for having a DeployerValidator at every stage (i.e, product deployment, test artifact deployment etc.). Hence we need to expose DeployerValidator as a common service.

Closing since irrelevant now.


chore(deps) - dependencies updates

github.com/bitcoin-sv/go-paymail from v0.18.0 to v0.19.0
github.com/newrelic/go-agent/v3 from v3.33.0 to v3.33.1

Pull Request Checklist

[ ] 📖 I created my PR using provided  : CODE_STANDARDS
[ ] 📖 I have read the short Code of Conduct: CODE_OF_CONDUCT
[ ] 🏠 I tested my changes locally.
[ ] ✅ I have provided tests for my changes.
[ ] 📝 I have used conventional commits.
[ ] 📗 I have updated any related documentation.
[ ] 💾 PR was issued based on the Github or Jira issue.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 48.88%. Comparing base (ac3ad4e) to head (2ba615c).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #647   +/-   ##
=======================================
  Coverage   48.88%   48.88%
=======================================
  Files         259      259
  Lines       11536    11536
=======================================
  Hits         5639     5639
  Misses       5313     5313
  Partials      584      584

Flag
Coverage Δ

unittests
48.88% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report in Codecov by Sentry.

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


Refactor tabbable.js

Make use of Number.isNaN and Array.from.
Changes proposed:

Replace window.isNaN with Number.isNaN
Replace [].slice.call with Array.from

Upgrade Path (for changed or removed APIs):
Acceptance Checklist:

[x] All commits have been squashed to one.
[ ] The commit message follows the guidelines in CONTRIBUTING.md.
[ ] Documentation (README.md) and examples have been updated as needed.
[ ] If this is a code change, a spec testing the functionality has been added.
[ ] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 76.667% when pulling f7f3c48f069c9441d13867bc84254b0dbf370f08 on abouthiroppy:feature/refactor-tabbable into e10181d20c8a1b66cbe21cfc86a19b64c9e2e9a3 on reactjs:master.

Coverage remained the same at 76.667% when pulling f7f3c48f069c9441d13867bc84254b0dbf370f08 on abouthiroppy:feature/refactor-tabbable into e10181d20c8a1b66cbe21cfc86a19b64c9e2e9a3 on reactjs:master.

That makes sense...

I'm going to setup SauceLabs testing to make it known what browsers we support and document it since it's not shown anywhere currently.

Thank you 😃

My only concern with the transform is that it might bloat the size of the package.

I agree. OK,  I will once close this PR.

That makes sense...

I'm going to setup SauceLabs testing to make it known what browsers we support and document it since it's not shown anywhere currently.

Thank you 😃

My only concern with the transform is that it might bloat the size of the package.

I agree. OK,  I will once close this PR.


Embed entries as iframes

Add embed route to display entry inside iframe
Add embed code field to entry admin attributes table

fixes #622

Coverage increased (+0.005%) to 99.053% when pulling f7cab17e345799dbdbecb408879352f025384e76 on tf:entry-embed into b8ffab00fc3b36a28add001e24fd6dac0d67de3a on codevise:master.

Coverage increased (+0.005%) to 99.053% when pulling 323417f827dd4071f116e39409f54ba3f59776e2 on tf:entry-embed into b8ffab00fc3b36a28add001e24fd6dac0d67de3a on codevise:master.

Did not know about this option. Might be something to consider in the future.