Milestone 0.3.0

Codecov Report

Merging #5 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #5   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           6      7    +1
=====================================
+ Hits            6      7    +1

Impacted Files
Coverage Δ

src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Changes Unknown when pulling 45ee3afce90a0a5fb706316280a6b1fe5bc705ad on milestone-0.3.0 into ** on master**.

Changes Unknown when pulling 45dbbd134c196e39b824679c5d769b0fc378c059 on milestone-0.3.0 into ** on master**.


Adding create_secret for SecretManager

Adding create_secret for SecretManager
Need region reset for test to work
update secret_arn to take arguments

Looks good but I'd prefer a few changes :)

Added tests and made some changes per feedback and test results. Squshed commits and ready for another review 👍

Great work @sepulworld :+1:


readme connection example up to date?

Hi,
When I try to connect as in the readme example:
dialer := gremgo.NewDialer("<IP_ADDRESS>") // Returns a WebSocket dialer to connect to Gremlin Server
g, err := gremgo.Dial(dialer) // Returns a gremgo client to interact with
if err != nil {
fmt.Println(err)
return
}
I get the following compilation error:
cannot use dialer (type gremgo.Ws) as type gremgo.dialer in argument to gremgo.Dial:
gremgo.Ws does not implement gremgo.dialer (gremgo.connect method has pointer receiver)
Is this connection example uptodate?
Thanks!

Hello,
Thank you for bringing this issue to light. Upon closer inspection I discovered that the problem seems to have spawned from the dialer creation function (NewDialer) and not the README. I have fixed the bug now in the master branch and it should be working properly.
Thanks,
Marcus

Thanks, looks better!
To get this working, I also had to modify something else:
in client.go:
func NewDialer(szhost string) (dialer Ws) {
return Ws{host: szhost}  //was hardcoding to <IP_ADDRESS>
}
also from the Readme example, I had to change how to call NewDialer:
dialer := gremgo.NewDialer("ws://localhost:8182")
This project looks awesome!  So glad to see a tinkerpop client for golang that doesn't create a new connection for each query.  Looking forward to playing with this library.


Add fastai dependency

fastai is now available conda-forge. This PR adds the fastai to the dependency list of autogluon.tabular.
@Innixma  @gradientsky

Checklist

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

@conda-forge-admin, please rerender

Tested the recipe locally and I can confirm that autogluon.tabular still supports GPU after adding fastai.


fixed reading of unicode text properly

Could you explain what this fixes? Please also add a test which failed previously but passes with this change. Thanks.

Bump.

The rebase didn't work. Since master was replaced with release-0.8, you need to rebase on the new master and ensure you don't include any commits from the old one.

It is actually not UTF-8 problem. After further investigation, I found out that the files I have issue with are latin format. So I added latin1 support. I'm changing the pull request name to this.
Also I've added a test for it

Sorry, but I don't think we want to support custom encodings like this. People should rather use StringEncodings to convert the file contents before passing them to readtable. Your solution using transcode won't work in general for any encoding.

Okay.

Thanks for making a PR though.


Error while compiling: size of array 'altStackMem' is not an integral constant-expression

I am trying to install and compile OpenFPGA using the tutorial and got this error while running make all -j:

How to fix? Thanks

Hello, please provide your OS and compiler information. You can follow the issue template: https://github.com/lnis-uofu/OpenFPGA/blob/master/.github/ISSUE_TEMPLATE/bug_report.md

我正在尝试使用教程安装和编译 OpenFPGA 并在运行时出现此错误 make all -j： 怎么修？ 谢谢
Have you fixed this problem? I had the same problem，my ubuntu is 2204. thx

@tangxifan
I am compiling using the below OS and compiler. I tried replacing SIGSTKSZ with the constant 32768 but I then got further errors. I think I am approaching the installation process incorrectly.

Enviornment (please complete the following information):

OS: Ubuntu 22.04

Compiler: gcc-9

Version: Current master

@LvmhZhD I have not managed to make progress for this error.

@tangxifan 我正在使用以下操作系统和编译器进行编译。我尝试用常量32768替换SIGSTKSZ，但随后我遇到了进一步的错误。我认为我错误地处理了安装过程。

环境（请填写以下信息）：

操作系统： 乌班图 22.04

编译器： gcc-9

版本：当前主站

@LvmhZhD我没有设法为这个错误取得进展。

I found a soultion :change some tool version, but errors come again subsequently .I am also 2204, maybe OpenFPGA need to run in Ubuntu 20 04 without any changing default setting.

@jaysunl @LvmhZhD Hi All, please be aware that

We ensure OpenFPGA has no issues when compiling on Ubuntu 18.04 through CIs.
We have also tested on local machines with Ubuntu 20.04 and it is working fine.
We have not tested on Ubuntu 22.04. There could be some issues that we currently do not have any solution.

We do plan to extend our OS support, e.g., Windows and latest ubuntu. Please give a try on latest master, where we have upgraded VtR to its latest version. See if this problem remains or not.

@jaysunl @LvmhZhD The compilation errors should be gone if you use the latest OpenFPGA v1.2.x
Close it now. If you still see issues, please let us know,

Works well now.Thank you


I have a page where same ui is shown for 10 or more tabs how do i validate each tab?

I have page where i have 10 to 15 tabs for a particular injury and I added a custom directive for validation  it works fine when i have a single tab.
But when i have more tabs then it fails neither the validation message is shown in a particular tab .Since the element/field name is same for all the tab i think it doesn't work.
Please if any one has done this  please give me some idea
Thanks
Saroj

https://github.com/angular-ui/bootstrap/blob/master/CONTRIBUTING.md#got-a-question-or-problem

Finally got the solutions, We need to use ng-form inside the main form to get this functionality

Examination

Clear
Incomplete info
Incomplete Information

Hope this may help .


Improve Documentation

This is not so much a bug as it is a modest suggestion.
The documentation mentioned Configure Domains almost in passing. Should be more strongly emphasized. The .env file for example lists mariadb as here in it's definitions:
DB_NAME=wordpress
DB_USER=wordpress
DB_PASSWORD=wordpress
DB_ROOT_PASSWORD=password
DB_HOST=mariadb
without making clear that

mariadb

here is/should be a hostname. It is missing from the example:

Hi, mariadb is the name of the service in docker-compose.yml, docker uses services' names as hosts in its private network. In the table, we list only services with http ports so you can use them to access containers from the host machine. MariaDB has no http ports and you don't need any domain to connect WP internally with mariadb via $DB_PORT that should  be used in wp-config.php

Thanks. Could you make the documentation a tad clearer on that?

Not sure which part there's to improve, docker4wordpress assumes you're familiar with how docker and docker-compose work


[Bug]: volumePercentage.js bug with last Spotify version

🔍 Have you checked that you are using an auto updating method or latest version of the extension?

[X] I have checked that I am on the latest version.

🔍 Is there already an issue for your problem?

[X] I have checked older issues, open and closed

Choose the extension for bug report.
Volume Percentage
ℹ Environment / Computer Info
- Spotify version: <IP_ADDRESS>9.g9b38fc27
- Spicetify version: v2.22.2

📝 Description
Hi
Your volumePercentage.js extension no longer work on the last Spotify version (<IP_ADDRESS>9.g9b38fc27), either through manual install nor Marketplace install.
Works fine with the <IP_ADDRESS>9.g9b38fc27-20 version.
No logs related to the extension found in the DevTools console.
Could you take a look please ? :)
Thank you in advance.
📸 Screenshots
No response

Can you try removing everything(theme and extensions) and test then, I have the same versions, and it's working fine for me.
It might be some theme is messing with it.
P.S. Just export your settings in marketplace settings and reset, and after testing you can import again

Can you try removing everything(theme and extensions) and test then, I have the same versions, and it's working fine for me. It might be some theme is messing with it. P.S. Just export your settings in marketplace settings and reset, and after testing you can import again

Hm ok go for test

Can you try running document.querySelector(".volume-bar"); in devtools and share ss of what you get, as attached below, see the volume bar is highlighted when I hover over the element in devtools.

Ok but where/how in the console i have to run your command ?

First, enable devtools by running spicetify enable-devtools, then open it by ctrl+shift+i or cmd+option+i inside Spotify to open.
And click on the console tab.

First, enable devtools by running spicetify enable-devtools, then open it by ctrl+shift+i or cmd+option+i inside Spotify to open.
And click on the console tab.

I know about this part, i just don't know how to run your command

Oh lol, just paste it right beside the blue arrow not in the filter box(clear it), see my attached ss in the previous comment.

Oh lol, just paste it right beside the blue arrow not in the filter box(clear it), see my attached ss in the previous comment.

Like that ?

Yeah, like that, not sure why it's coming as null. Weird
Can you try clicking on the button to the left of elements tab and select the volume bar inside spotify, and share ss of devtools what's opening up.
I have the exact same versions, it's working fine for me. You may need to do a clean install, if this doesn't work.

Can you try clicking on the button to the left of elements tab and select the volume bar inside spotify, and share ss of devtools what's opening up.

Same result happened.

I have the exact same versions, it's working fine for me. You may need to do a clean install, if this doesn't work.

OK, I admit i'm a bit scared to reinstall Spotify just for that, so i'll go back to the previous version and check if this bug disappears in future versions
Thx anyway for your help/support and have a good day.

Hi @daksh2k i just did a clean install of Spotify (<IP_ADDRESS>0.g2a8a8a57) and Spicetify (v2.23.2)
Same issue, the extension won't works and same result on Console tab of DevTools.
Some extensions works fine (goToSong, fullAppDisplay and power-bar), some won't (your one, copytoclipboard2 and fullAlbumDate), maybe it would help us to see things more clearly..
Another change with the Spicetify/Spotify cleanup setup: is now show the note (second line after the command)

The bug is either in the Experimental settings (simple method to compare my ones with yours ?) nor in Spicetify (a fairly recent bug had broken all the extensions for quite a few users, perhaps this is a repeat ?)
Back to <IP_ADDRESS>9.g9b38fc27-20, your extension work again.

There was some change done in #109  , that should have fixed it. I still have the 1.2.19 version, it works fine.
Haven't got 1.2.20 version yet, so can't say.


Direct local .aar file dependencies are not supported when building an AAR

New Issue Checklist

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

Issue Description

react-native CLI is able to produce a release build without issues
android studio is able to produce a release build without issues
fastlane's gradle action failing with errors: (it wasn't before)

Relevant change: Upgraded from RN 0.63 > RN 0.64
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':adobe_react-native-aepassurance:bundleReleaseAar'.
> Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error). The following direct local .aar file dependencies of the :adobe_react-native-aepassurance project caused this error: /Users/<app<EMAIL_ADDRESS>
Command executed

Gradle command from Fastfile:

    gradle(
      task: 'assemble',
      build_type: 'Release',
      print_command: false,
      properties: {
        "android.injected.signing.store.file" => releaseFilePath,
        "android.injected.signing.store.password" => store_password,
        "android.injected.signing.key.alias" => "my-key-alias",
        "android.injected.signing.key.password" => key_password,
      }
    )

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

...
> Task :adobe_react-native-acpuserprofile:compileReleaseJavaWithJavac
warning: [options] source value 7 is obsolete and will be removed in a future release
warning: [options] target value 7 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
3 warnings

Task :adobe_react-native-acpuserprofile:extractReleaseAnnotations
Task :adobe_react-native-acpuserprofile:mergeReleaseGeneratedProguardFiles UP-TO-DATE
Task :adobe_react-native-acpuserprofile:mergeReleaseConsumerProguardFiles UP-TO-DATE
Task :adobe_react-native-acpuserprofile:compileReleaseSources
Task :expo-permissions:generateReleaseResValues
Task :expo-permissions:generateReleaseResources
Task :expo-permissions:packageReleaseResources
Task :expo-splash-screen:compileReleaseRenderscript NO-SOURCE
Task :expo-splash-screen:generateReleaseResValues
Task :expo-splash-screen:generateReleaseResources
Task :expo-splash-screen:packageReleaseResources
Task :expo-sqlite:compileReleaseRenderscript NO-SOURCE
Task :expo-sqlite:generateReleaseResValues
Task :expo-sqlite:generateReleaseResources
Task :expo-sqlite:packageReleaseResources
Task :expo-web-browser:compileReleaseRenderscript NO-SOURCE
Task :expo-web-browser:generateReleaseResValues
Task :expo-web-browser:generateReleaseResources
Task :expo-web-browser:packageReleaseResources
Task :adobe_react-native-aepassurance:generateReleaseRFile

Task :adobe_react-native-aepassurance:compileReleaseJavaWithJavac
warning: [options] source value 7 is obsolete and will be removed in a future release
warning: [options] target value 7 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
3 warnings

Task :adobe_react-native-aepassurance:extractReleaseAnnotations
Task :adobe_react-native-aepassurance:mergeReleaseGeneratedProguardFiles UP-TO-DATE
Task :adobe_react-native-aepassurance:mergeReleaseConsumerProguardFiles UP-TO-DATE
Task :adobe_react-native-aepassurance:compileReleaseSources
Task :react-native-async-storage_async-storage:compileReleaseRenderscript NO-SOURCE
Task :react-native-async-storage_async-storage:generateReleaseResValues
Task :react-native-async-storage_async-storage:generateReleaseResources
Task :react-native-async-storage_async-storage:packageReleaseResources
Task :react-native-community_masked-view:compileReleaseRenderscript NO-SOURCE
Task :react-native-community_masked-view:generateReleaseResValues
Task :react-native-community_masked-view:generateReleaseResources
Task :react-native-community_masked-view:packageReleaseResources
Task :react-native-device-info:compileReleaseRenderscript NO-SOURCE
Task :react-native-device-info:generateReleaseResValues
Task :react-native-device-info:generateReleaseResources
Task :react-native-device-info:packageReleaseResources
Task :react-native-gesture-handler:compileReleaseRenderscript NO-SOURCE
Task :react-native-gesture-handler:generateReleaseResValues
Task :react-native-gesture-handler:generateReleaseResources
Task :react-native-gesture-handler:packageReleaseResources
Task :react-native-jw-media-player:compileReleaseRenderscript NO-SOURCE
Task :react-native-jw-media-player:generateReleaseResValues
Task :react-native-jw-media-player:generateReleaseResources
Task :react-native-jw-media-player:packageReleaseResources
Task :react-native-maps:compileReleaseRenderscript NO-SOURCE
Task :react-native-maps:generateReleaseResValues
Task :react-native-maps:generateReleaseResources
Task :react-native-maps:packageReleaseResources
Task :react-native-reanimated:compileReleaseRenderscript NO-SOURCE
Task :react-native-reanimated:generateReleaseResValues
Task :react-native-reanimated:generateReleaseResources
Task :react-native-reanimated:packageReleaseResources
Task :react-native-restart:compileReleaseRenderscript NO-SOURCE
Task :react-native-restart:generateReleaseResValues
Task :react-native-restart:generateReleaseResources
Task :react-native-restart:packageReleaseResources
Task :react-native-safe-area-context:compileReleaseRenderscript NO-SOURCE
Task :react-native-safe-area-context:generateReleaseResValues
Task :react-native-safe-area-context:generateReleaseResources
Task :react-native-safe-area-context:packageReleaseResources
Task :react-native-screens:compileReleaseRenderscript NO-SOURCE
Task :react-native-screens:generateReleaseResValues
Task :react-native-screens:generateReleaseResources
Task :react-native-screens:packageReleaseResources
Task :react-native-svg:compileReleaseRenderscript NO-SOURCE
Task :react-native-svg:generateReleaseResValues
Task :react-native-svg:generateReleaseResources
Task :react-native-svg:packageReleaseResources
Task :react-native-webview:compileReleaseRenderscript NO-SOURCE
Task :react-native-webview:generateReleaseResValues
Task :react-native-webview:generateReleaseResources
Task :react-native-webview:packageReleaseResources
Task :unimodules-app-loader:compileReleaseRenderscript NO-SOURCE
Task :unimodules-app-loader:generateReleaseResValues
Task :unimodules-app-loader:generateReleaseResources
Task :unimodules-app-loader:packageReleaseResources
Task :unimodules-barcode-scanner-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-barcode-scanner-interface:generateReleaseResValues
Task :unimodules-barcode-scanner-interface:generateReleaseResources
Task :unimodules-barcode-scanner-interface:packageReleaseResources
Task :unimodules-camera-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-camera-interface:generateReleaseResValues
Task :unimodules-camera-interface:generateReleaseResources
Task :unimodules-camera-interface:packageReleaseResources
Task :unimodules-constants-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-constants-interface:generateReleaseResValues
Task :unimodules-constants-interface:generateReleaseResources
Task :unimodules-constants-interface:packageReleaseResources
Task :unimodules-core:compileReleaseRenderscript NO-SOURCE
Task :unimodules-core:generateReleaseResValues
Task :unimodules-core:generateReleaseResources
Task :unimodules-core:packageReleaseResources
Task :unimodules-face-detector-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-face-detector-interface:generateReleaseResValues
Task :unimodules-face-detector-interface:generateReleaseResources
Task :unimodules-face-detector-interface:packageReleaseResources
Task :unimodules-file-system-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-file-system-interface:generateReleaseResValues
Task :unimodules-file-system-interface:generateReleaseResources
Task :unimodules-file-system-interface:packageReleaseResources
Task :unimodules-font-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-font-interface:generateReleaseResValues
Task :unimodules-font-interface:generateReleaseResources
Task :unimodules-font-interface:packageReleaseResources
Task :unimodules-image-loader-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-image-loader-interface:generateReleaseResValues
Task :unimodules-image-loader-interface:generateReleaseResources
Task :unimodules-image-loader-interface:packageReleaseResources
Task :unimodules-permissions-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-permissions-interface:generateReleaseResValues
Task :unimodules-permissions-interface:generateReleaseResources
Task :unimodules-permissions-interface:packageReleaseResources
Task :unimodules-react-native-adapter:compileReleaseRenderscript NO-SOURCE
Task :unimodules-react-native-adapter:generateReleaseResValues
Task :unimodules-react-native-adapter:generateReleaseResources
Task :unimodules-react-native-adapter:packageReleaseResources
Task :unimodules-sensors-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-sensors-interface:generateReleaseResValues
Task :unimodules-sensors-interface:generateReleaseResources
Task :unimodules-sensors-interface:packageReleaseResources
Task :unimodules-task-manager-interface:compileReleaseRenderscript NO-SOURCE
Task :unimodules-task-manager-interface:generateReleaseResValues
Task :unimodules-task-manager-interface:generateReleaseResources
Task :unimodules-task-manager-interface:packageReleaseResources
Task :adobe_react-native-acpanalytics:extractDeepLinksRelease
Task :adobe_react-native-acpcore:extractDeepLinksRelease
Task :adobe_react-native-acpuserprofile:extractDeepLinksRelease
Task :adobe_react-native-aepassurance:extractDeepLinksRelease
Task :app:createReleaseCompatibleScreenManifests
Task :app:extractDeepLinksRelease
Task :expo-av:extractDeepLinksRelease
Task :expo-constants:extractDeepLinksRelease
Task :adobe_react-native-aepassurance:bundleLibCompileToJarRelease
Task :expo-error-recovery:extractDeepLinksRelease
Task :adobe_react-native-acpuserprofile:bundleLibCompileToJarRelease
Task :expo-file-system:extractDeepLinksRelease
Task :expo-error-recovery:processReleaseManifest
Task :expo-font:extractDeepLinksRelease

Task :expo-file-system:processReleaseManifest
/Users//node_modules/react-native-unimodules/node_modules/expo-file-system/android/src/main/AndroidManifest.xml:9:9-20:20 Warning:
provider#expo.modules.filesystem.FileSystemFileProvider@android:authorities was tagged at AndroidManifest.xml:9 to replace other declarations but no other declaration present

Task :expo-image-loader:extractDeepLinksRelease
Task :expo-keep-awake:extractDeepLinksRelease
Task :expo-image-loader:processReleaseManifest
Task :expo-linear-gradient:extractDeepLinksRelease
Task :expo-av:processReleaseManifest
Task :expo-location:extractDeepLinksRelease
Task :expo-permissions:extractDeepLinksRelease
Task :expo-keep-awake:processReleaseManifest
Task :expo-splash-screen:extractDeepLinksRelease
Task :expo-permissions:processReleaseManifest
Task :expo-sqlite:extractDeepLinksRelease
Task :expo-font:processReleaseManifest
Task :expo-web-browser:extractDeepLinksRelease
Task :expo-sqlite:processReleaseManifest
Task :react-native-async-storage_async-storage:extractDeepLinksRelease
Task :react-native-community_masked-view:extractDeepLinksRelease
Task :react-native-async-storage_async-storage:processReleaseManifest
Task :react-native-device-info:extractDeepLinksRelease
Task :expo-constants:processReleaseManifest
Task :react-native-gesture-handler:extractDeepLinksRelease
Task :react-native-jw-media-player:extractDeepLinksRelease
Task :react-native-gesture-handler:processReleaseManifest
Task :react-native-maps:extractDeepLinksRelease
Task :react-native-jw-media-player:processReleaseManifest
Task :react-native-reanimated:extractDeepLinksRelease
Task :react-native-maps:processReleaseManifest
Task :react-native-restart:extractDeepLinksRelease
Task :react-native-reanimated:processReleaseManifest
Task :react-native-safe-area-context:extractDeepLinksRelease
Task :expo-linear-gradient:processReleaseManifest
Task :react-native-screens:extractDeepLinksRelease
Task :react-native-safe-area-context:processReleaseManifest
Task :react-native-svg:extractDeepLinksRelease
Task :expo-location:processReleaseManifest
Task :react-native-webview:extractDeepLinksRelease
Task :react-native-restart:processReleaseManifest
Task :unimodules-app-loader:extractDeepLinksRelease
Task :react-native-webview:processReleaseManifest
Task :unimodules-barcode-scanner-interface:extractDeepLinksRelease
Task :unimodules-app-loader:processReleaseManifest
Task :unimodules-camera-interface:extractDeepLinksRelease
Task :unimodules-barcode-scanner-interface:processReleaseManifest
Task :unimodules-constants-interface:extractDeepLinksRelease
Task :adobe_react-native-acpuserprofile:syncReleaseLibJars
Task :adobe_react-native-acpuserprofile:bundleReleaseAar
Task :adobe_react-native-acpuserprofile:assembleRelease
Task :unimodules-core:extractDeepLinksRelease
Task :react-native-community_masked-view:processReleaseManifest
Task :unimodules-face-detector-interface:extractDeepLinksRelease
Task :unimodules-core:processReleaseManifest
Task :unimodules-file-system-interface:extractDeepLinksRelease
Task :unimodules-camera-interface:processReleaseManifest
Task :unimodules-font-interface:extractDeepLinksRelease
Task :unimodules-file-system-interface:processReleaseManifest
Task :unimodules-image-loader-interface:extractDeepLinksRelease
Task :unimodules-font-interface:processReleaseManifest
Task :unimodules-permissions-interface:extractDeepLinksRelease
Task :unimodules-image-loader-interface:processReleaseManifest
Task :unimodules-react-native-adapter:extractDeepLinksRelease
Task :unimodules-permissions-interface:processReleaseManifest
Task :unimodules-face-detector-interface:processReleaseManifest
Task :unimodules-sensors-interface:extractDeepLinksRelease
Task :unimodules-task-manager-interface:extractDeepLinksRelease
Task :unimodules-sensors-interface:processReleaseManifest
Task :unimodules-task-manager-interface:processReleaseManifest
Task :adobe_react-native-aepassurance:syncReleaseLibJars
Task :adobe_react-native-aepassurance:bundleReleaseAar FAILED
Task :expo-av:parseReleaseLocalResources
Task :unimodules-react-native-adapter:processReleaseManifest
Task :expo-av:compileReleaseLibraryResources
Task :unimodules-constants-interface:processReleaseManifest
Task :expo-web-browser:processReleaseManifest
Task :app:mergeReleaseResources
Task :react-native-device-info:processReleaseManifest
Task :expo-splash-screen:processReleaseManifest
Task :react-native-screens:processReleaseManifest
Task :react-native-svg:processReleaseManifest

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':adobe_react-native-aepassurance:bundleReleaseAar'.

Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error). The following direct local .aar file dependencies of the :adobe_react-native-aepassurance project caused this error<EMAIL_ADDRESS>

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.7/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 2m 14s
385 actionable tasks: 339 executed, 46 up-to-date]

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
11.1

Ruby
2.6.6

Bundler?
false

Git
git version 2.24.3 (Apple Git-128)

Installation Source
/usr/local/Cellar/fastlane/2.180.1/libexec/bin/fastlane

Host
macOS 11.1 (20C69)

Ruby Lib Dir
<EMAIL_ADDRESS>

OpenSSL Version
OpenSSL 1.1.1i  8 Dec 2020

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
12.4

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
skip_docs # Do not create fastlane/README on run
slack_url = "******"

default_platform(:android)

platform :android do
  desc "Submit a new Beta Build to Play Store"
  lane :beta do
    confirm = UI.confirm "Have you added a changelog to this release?"
    if !confirm
      UI.user_error!("Please add a changelog for this release and try again")
    end
    ensure_git_status_clean
    store_password = prompt(text: "Signing Store Password: ", secure_text: true)
    key_password = prompt(text: "Alias Key Password: ", secure_text: true)
    releaseFilePath = File.join(Dir.pwd, "..", "my-release-key.keystore")
    increment_version_code # Bumps build number
    gradle(task: 'clean')
    add_badge # Add beta badge to app icon
    gradle(
      task: 'assemble',
      build_type: 'Release',
      print_command: false,
      properties: {
        "android.injected.signing.store.file" => releaseFilePath,
        "android.injected.signing.store.password" => store_password,
        "android.injected.signing.key.alias" => "my-key-alias",
        "android.injected.signing.key.password" => key_password,
      }
    )
    upload_to_play_store(
      track: 'internal',
      apk: 'app/build/outputs/apk/release/app-release.apk'
      )
  end

  after_all do |lane|
    # This block is called, only if the executed lane was successful
    slack(
      slack_url: slack_url,
      message: "Android build successfully published to Google Play Store! :rocket:",
      success: true,
      default_payloads: ["git_branch", "last_git_commit_hash"]
    )
  end

end

`./fastlane/Appfile`
json_key_file("key.json") # Path to the json secret file
package_name("com.****")

fastlane gems

Gem
Version
Update-Status

fastlane
2.180.1
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-increment_version_code
0.4.3
✅ Up-To-Date

fastlane-plugin-badge
1.5.0
✅ Up-To-Date

Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.3

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.6.0

public_suffix
4.0.6

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.79.0

faraday-net_http
1.0.1

ruby2_keywords
0.0.4

faraday
1.3.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.3

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.11.0

naturally
2.2.1

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.7.6

bundler
2.2.15

simctl
1.6.8

jwt
2.2.2

uber
0.1.0

declarative
0.0.20

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.1.0

multi_json
1.15.0

signet
0.15.0

memoist
0.16.2

os
1.1.1

googleauth
0.16.1

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.5.0

google-cloud-errors
1.1.0

google-cloud-core
1.6.0

rexml
3.1.9

webrick
1.4.2

google-apis-core
0.3.0

google-apis-iamcredentials_v1
0.3.0

google-apis-storage_v1
0.3.0

rake
13.0.3

digest-crc
0.6.3

google-cloud-storage
1.31.0

emoji_regex
3.2.2

jmespath
1.4.0

aws-partitions
1.443.0

aws-eventstream
1.1.1

aws-sigv4
1.2.3

aws-sdk-core
3.113.1

aws-sdk-kms
1.43.0

aws-sdk-s3
1.93.0

forwardable
1.2.0

logger
1.3.0

date
2.0.0

stringio
0.0.2

zlib
1.0.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

psych
3.1.0

mutex_m
0.1.0

fastlane-plugin-increment_version_code
0.4.3

badge
0.13.0

fastlane-plugin-badge
1.5.0

generated on: 2021-04-13

MacOS Big Sur: 11.1
Android Studio: 4.1.3
React Native: 0.64
Fastlane: 2.180.1

build.gradle snippet:

buildscript {
    ext {
        buildToolsVersion = "29.0.3"
        minSdkVersion = 21
        compileSdkVersion = 29
        targetSdkVersion = 29
        ndkVersion = "20.1.5948944"
    }
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath('com.android.tools.build:gradle:4.0.1')
    }
}

✅ fastlane environment ✅
Stack

Key
Value

OS
11.1

Ruby
2.6.6

Bundler?
false

Git
git version 2.24.3 (Apple Git-128)

Installation Source
/usr/local/Cellar/fastlane/2.180.1/libexec/bin/fastlane

Host
macOS 11.1 (20C69)

Ruby Lib Dir
<EMAIL_ADDRESS>

OpenSSL Version
OpenSSL 1.1.1i  8 Dec 2020

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
12.4

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
skip_docs # Do not create fastlane/README on run
slack_url = "******"

default_platform(:android)

platform :android do
  desc "Submit a new Beta Build to Play Store"
  lane :beta do
    confirm = UI.confirm "Have you added a changelog to this release?"
    if !confirm
      UI.user_error!("Please add a changelog for this release and try again")
    end
    ensure_git_status_clean
    store_password = prompt(text: "Signing Store Password: ", secure_text: true)
    key_password = prompt(text: "Alias Key Password: ", secure_text: true)
    releaseFilePath = File.join(Dir.pwd, "..", "my-release-key.keystore")
    increment_version_code # Bumps build number
    gradle(task: 'clean')
    add_badge # Add beta badge to app icon
    gradle(
      task: 'assemble',
      build_type: 'Release',
      print_command: false,
      properties: {
        "android.injected.signing.store.file" => releaseFilePath,
        "android.injected.signing.store.password" => store_password,
        "android.injected.signing.key.alias" => "my-key-alias",
        "android.injected.signing.key.password" => key_password,
      }
    )
    upload_to_play_store(
      track: 'internal',
      apk: 'app/build/outputs/apk/release/app-release.apk'
      )
  end

  after_all do |lane|
    # This block is called, only if the executed lane was successful
    slack(
      slack_url: slack_url,
      message: "Android build successfully published to Google Play Store! :rocket:",
      success: true,
      default_payloads: ["git_branch", "last_git_commit_hash"]
    )
  end

end

`./fastlane/Appfile`
json_key_file("key.json") # Path to the json secret file
package_name("com.****")

fastlane gems

Gem
Version
Update-Status

fastlane
2.180.1
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-increment_version_code
0.4.3
✅ Up-To-Date

fastlane-plugin-badge
1.5.0
✅ Up-To-Date

Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.3

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.6.0

public_suffix
4.0.6

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.79.0

faraday-net_http
1.0.1

ruby2_keywords
0.0.4

faraday
1.3.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.3

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.11.0

naturally
2.2.1

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.7.6

bundler
2.2.15

simctl
1.6.8

jwt
2.2.2

uber
0.1.0

declarative
0.0.20

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.1.0

multi_json
1.15.0

signet
0.15.0

memoist
0.16.2

os
1.1.1

googleauth
0.16.1

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.5.0

google-cloud-errors
1.1.0

google-cloud-core
1.6.0

rexml
3.1.9

webrick
1.4.2

google-apis-core
0.3.0

google-apis-iamcredentials_v1
0.3.0

google-apis-storage_v1
0.3.0

rake
13.0.3

digest-crc
0.6.3

google-cloud-storage
1.31.0

emoji_regex
3.2.2

jmespath
1.4.0

aws-partitions
1.443.0

aws-eventstream
1.1.1

aws-sigv4
1.2.3

aws-sdk-core
3.113.1

aws-sdk-kms
1.43.0

aws-sdk-s3
1.93.0

forwardable
1.2.0

logger
1.3.0

date
2.0.0

stringio
0.0.2

zlib
1.0.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

psych
3.1.0

mutex_m
0.1.0

fastlane-plugin-increment_version_code
0.4.3

badge
0.13.0

fastlane-plugin-badge
1.5.0

generated on: 2021-04-13

Are you able to build it with gradle in general? It's not "our" or "fastlane's" gradle. It's just gradle AFAIK, which is probably failing here.

Appears that this problem was related to the package itself, has been resolved in: https://github.com/adobe/react-native-aepassurance/issues/13
Thank you!


Error gracefully when Run command cannot find the executable

the error info is written on the forked process stderr stream, which is reported back to the client.

I think this would be better as an error returned by the API rather than printed on stdout.
For example, if I were to execute:
someContainer.Run(garden.ProcessSpec{Path: "/some/bogus/path"})

I would prefer the call to .Run to return an error. That way it's unambiguous that the command failed to even start, and not just that it exited with a particular code and printed something.

hi Vito, thanks for having a look at the PRs.
About the point of container.run() could also return err with similar information (I did put a comment on a similar PR - [https://github.com/cloudfoundry-incubator/garden-linux/pull/37]). This might be a little tricky and am not sure if its Ok; Based on the code that I did check, the process is run through iodaemon and wsh; and the stdio and error status are sent back over pipes passed back to the caller over sockets. As per this pipeline (or framework) the user of container.run() is supposed to wait on the returned process (process.Wait()), which eventually tells if the process executed successfully or not and it might be a while the spawned process returns (for some other error scenario). I was not entirely sure if I could circumvent this.
However, you certainly have a point that we need to differentiate that command failed to launch in the first place. I could only think of couple of ways to implement this:

One (probably horrible) way of defining a standalone command (or script) which can be run using same method of wsh and wshd and does env check stuff (wrong user, wrong path, incorrect process name etc) right before executing the real process; and in case something is improper, does not launch the actual process at all.
Another one in which, we open additional pipes in wshd, for pre-reporting problems that might occur until exec (but in some cases after fork). These pipes report err msg (and/or some status code) back to the caller and are closed right before exec, to report successful run till exec to the caller. This way, container.Run() would wait till it either gets a successfully closed pipe or get an error message on it and can choose to still return the process and the stdio streams to the caller. (the error info might be duplicated)

I am not at all sure that either of this makes any sense to you; and you might certainly have some other amazing way of solving this problem. I am looking for suggestions.. :-)
Having said this, I actually based these PRs on comments in story [#84690384] in garden tracker. By doing this much alone, the actual use case might be solved. (or may be not.. :) ). I anxiously wait for pointers from you!!

hey @irfanurrehman - one thing to consider here is that we're currently a good chunk of the way through rewriting wshd in golang. Once this is done this story will become much easier to implement along the lines @vito suggests, so it might be worth waiting until that work is done before restarting this one.

thats interesting; @julz thanks for your suggestion. I will wait for the new wshd update and then see, how these tasks can be taken forward.

Hi @irfanurrehman. Since the implementation for this will be completely different after the wshd update is merged, I'm going to close this (and #39) for now.
Thanks very much for your contribution. You can follow this story on Tracker to see when the wshd update is completed.

Ok @goonzoid. Thanks for the update.


Fix matplotlib deprecated function call

ax.get_axis_bgcolor() in line 151 is deprecated and removed, it is now used as ax.get_fc()

Hi, if this problem still exists and you'd like to create a PR to fix it please direct it to https://github.com/MarvinT/calmap/
That is the version that gets published to pypi and has received several updates to fix some existing issues.

Thank you for your contribution. Unfortunately I don't have the time to maintain this project. As per @MarvinT 's comment, please see https://github.com/MarvinT/calmap/ instead.


在构建检测器的时候显示：KeyError: "CascadeRCNN: 'SwinTransformer is not in the backbone registry'"

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
I have read the FAQ documentation but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
A clear and concise description of what the bug is.
Reproduction

What command or script did you run?

A placeholder for the command.

Did you make any modifications on the code or config? Did you understand what you have modified?
What dataset did you use?

Environment

Please run python mmdet/utils/collect_env.py to collect necessary environment information and paste it here.
You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Error traceback
If applicable, paste the error trackback here.
A placeholder for trackback.

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

在这一行中

执行这行时：
model = build_detector(
cfg.model,
train_cfg=cfg.get('train_cfg'),
test_cfg=cfg.get('test_cfg'))
出现如下错误：
KeyError: "CascadeRCNN: 'SwinTransformer is not in the backbone registry'"

We have not yet supported SwinTransformer, we would support it in the next month.

@jshilong You mentioned that the SwinTransformer would be supported, regarding the time you gave it should be supported now. Is there any advancement in this process?


Remove Cielo device

Hi, How do I remove a Cielo device that is not in use any more but shows as a device in HA?
ty

Anyone?

Normally if you remove completely the integration and re add it. You should be ok.


Lua_helper.add_callback(lua,   -> funk.set(

You should give @TheLeerName some social credit points

You should give @TheLeerName some social credit points

nuh uh


fix(shared-data): fix well bottom shape of nest_96_wellplate_2ml_deep

Overview
Closes #6171
Changelog

changes nest_96_wellplate_2ml_deep wellBottomShape from U to V, matching the real labware

Review requests

Compare LL to production, should show a V-bottom not U-bottom
This wellBottomShape field truly is only metadata: it's only used for display (specifically, only in LL) and does not affect behavior. Right?

Risk assessment
Low. Mutates a labware definition, but only mutates a metadata field.

makes sense to me, do we need to update the image somewhere too?

makes sense to me, do we need to update the image somewhere too?

The U vs V image should update itself (see sandbox build), doesn't look like we have a photo for this one so nothing to update there


Add convenience properties for the DecodeError.

This PR adds error and errorString properties to Decoded, making it more convenient to extract DecodeErrors and their descriptions.
Would you like any tests?

I'm definitely ok with the error addition. Still unsure about errorString.

@tonyd256 @gfontenot I've removed errorString.

@jshier Great thanks! If you could add a test for this as well, that would be awesome!

@jshier I'm thinking about cutting a new release tomorrow. Would you be able to get this in?

I'll try to get it done by noon EST.

@tonyd256 I've added tests, let me know if you think they're appropriate.

@tonyd256 Do you want any mention of this property in the documentation? I know it's still in flux, so I haven't touched anything.

This is great! Thanks!

Merged here: b2ebd2ff8a2de71e34a1d0b16af30a28bef6158b


fix(CL): broken CLI queries

Background
osmosisd q concentratedliquidity pools
Error: proto: wrong wireType = 2 for field Id
osmosisd q concentratedliquidity pool 1
Error: rpc error: code = Unknown desc = unknown query path: unknown request

Acceptance Criteria

fixed
tested on localosmosis

currently working on my end
❯ osmosisd q concentratedliquidity pools
pagination:
  next_key: null
  total: "0"
pools:
- '@type': /osmosis.concentratedliquidity.v1beta1.Pool
  address: osmo1ad4r3uh5pdn5pgg5hnl6u5utfeqmpwstlvgvg2h2jdztrcnwkqgs3hs85z
  current_sqrt_price: "0.014142135623730951"
  current_tick: "-350000"
  current_tick_liquidity: "70710678.118654755000100000"
  exponent_at_price_one: "-4"
  id: "4"
  incentives_address: osmo1ra25mx8lch089mxf97nr6cnzns7vesecvw0mxj32fcaj5ygrsd8sqwhjpk
  last_liquidity_update: "2023-04-14T03:31:51.593814278Z"
  swap_fee: "0.010000000000000000"
  tick_spacing: "1"
  token0: uosmo
  token1: uion

Fixed per above comment ^


Support multiple structs in one macro block?

Could multiple structs in one macro block be supported? instead of wrapping every struct in its own block

Sure, that's simple. I've released a new version.


Provide Access to Attached Files

Feature / Enhancement proposed
Extend the API to read attached files.
Usecase:
To automate the setup of web/app servers it is necessary to access the private-key for the https service.
Workarounds
None
Has the feature been requested before?
Here
If the feature request is approved, would you be willing to submit a PR?
(Help can be provided if you need assistance submitting a PR)
[] Yes [x] No

Hi @jifox. Nice to see you again.
get_secret() should return file attachments by default:
def get_secret(self, id, fetch_file_attachments=True, query_params=None)
Is this not working for you? Do you have an example output you can share?

@jifox Do you have any update on the above comment?

Hi it is working as expected now


[relationships] update selectors to represent correct path

Notes for Reviewers
The json paths listed in the mutated_refs were incorrect causing the evaluation results to be empty.
The PR updates them to correct path.
Signed commits

[ ] Yes, I signed my commits.

// @aabidsofi19


Error loading IFC wasmModule.OpenModel is not a function

Hello
Im trying to load a IFC file using the library, i have setup the library alongside with three.js 0.152.0, web-ifc v0.0.41, web-ifc-three
v0.0.125.
I tried rolling back  to three.js 0.149.0 but the problem persists
I have copied the WASM files bundled with the library and set the WASM path to those files. When loading the file im getting the following error.
    at IfcAPI2.OpenModel (web-ifc-api.js:63155:34)
    at IFCParser.newIfcModel (IFCLoader.js:159:49)
    at IFCParser.parse (IFCLoader.js:139:16)
    at async IFCManager.parse (IFCLoader.js:2417:17)
    at async Object.eval [as onLoad] (IFCLoader.js:2645:16)
eval @ IFCLoader.js:2650
await in eval (async)
eval @ three.module.js:41908
Promise.then (async)
load @ three.module.js:41896
load @ IFCLoader.js:2640
App @ app.js:63
eval @ main.js:7
./src/main.js @ main.bundle.js:398
__webpack_require__ @ main.bundle.js:427
(anonymous) @ main.bundle.js:1507
(anonymous) @ main.bundle.js:1509

Here is the IFC file that im trying to load EscritorioEQS.zip.
Thanks in advance

can u show your code in file where that error showing
for me its loading perfectly

same

We use web-ifc-three in a project, and both web-ifc's WASM version 0.0.40 and 0.0.41 have the TypeError: this.wasmModule.OpenModel is not a function issue.
WASM of web-ifc version 0.0.39 works fine.

I guess you guys installed web-ifc-three first then you also installed web-ifc

I guess you guys installed web-ifc-three first then you also installed web-ifc

There is no install/import order, getting it from npm and importing it as a module into code.

I have the same issue

Hello
Im trying to load a IFC file using the library, i have setup the library alongside with three.js 0.152.0, web-ifc v0.0.41, web-ifc-three v0.0.125.
I tried rolling back to three.js 0.149.0 but the problem persists
I have copied the WASM files bundled with the library and set the WASM path to those files. When loading the file im getting the following error.
    at IfcAPI2.OpenModel (web-ifc-api.js:63155:34)
    at IFCParser.newIfcModel (IFCLoader.js:159:49)
    at IFCParser.parse (IFCLoader.js:139:16)
    at async IFCManager.parse (IFCLoader.js:2417:17)
    at async Object.eval [as onLoad] (IFCLoader.js:2645:16)
eval @ IFCLoader.js:2650
await in eval (async)
eval @ three.module.js:41908
Promise.then (async)
load @ three.module.js:41896
load @ IFCLoader.js:2640
App @ app.js:63
eval @ main.js:7
./src/main.js @ main.bundle.js:398
__webpack_require__ @ main.bundle.js:427
(anonymous) @ main.bundle.js:1507
(anonymous) @ main.bundle.js:1509

Here is the IFC file that im trying to load EscritorioEQS.zip.
Thanks in advance

The solution to this problem is to copy WASM files from the web-ifc-three to your root project and setWasmpath to that directory.  DO NOT COPY THE WASM FILE FROM OTHER PACKAGES LIKE web-ifc.
ifcLoader.ifcManager.setWasmPath("../../");

Dear @bholathapa7
As far as I know, there is no *.wasm file inside the web-ifc-three package, they are inside web-ifc.
Even in the documentation of the web-ifc-three, it's mentioned to copy them from web-ifc:
https://ifcjs.github.io/info/docs/Guide/web-ifc-three/api/#setwasmpath

To fix the problem i have removed "web-ifc" from the package.json.
"web-ifc-three" seems to be only compatible with older versions of the "web-ifc" project, so the WASM file from the last version is not compatible.


 Where are you initialising your database pool? It should be something like var db *sqlx.DB as a package global (as the simplest implementation).
Calling sqlx.Get directly won't work as there's no database connection to use.

I know. This is only the problem part.
var DB *sqlx.DB

type Device struct {
	Id int64 `db:"id"`
}

func ConnectToDatabase() {
	var err error

	DB, err = sqlx.Connect("mysql", "uuu:ppp@(localhost:3306)/ddd?charset=utf8")
	if err != nil {
		Log("Erro while connect to database: " + err.Error())
		os.Exit(1)
	}
}

What error messages are you getting? Are you getting anything back? A panic?
Your actual SQL query doesn't look problematic (I assume that query works via psql).

Ops, sorry man. I forgot put the error:
./main.go:243: cannot use &device (type *Device) as type sqlx.Queryer in argument to sqlx.Get:
	*Device does not implement sqlx.Queryer (missing Query method)

Sorry, my fault :(

This is because you're calling sqlx.Get (https://godoc.org/github.com/jmoiron/sqlx#Get) and not db.Get (https://godoc.org/github.com/jmoiron/sqlx#DB.Get).
sqlx.Get expects a Queryer as the first argument, not a type to marshal the query results into.
Change your code to err := db.Get(&device, "SELECT id FROM device WHERE imei = :imei LIMIT 1", imei) will work (as per my first comment!) :+1:

Ok. Near to work.
Now the Device object is not filled if code is:
var device = Device{}
err := DB.Get(&device, "SELECT id FROM device WHERE imei = $1 LIMIT 1", imei)

But filled if is:
var device = Device{}
err := DB.Get(&device, "SELECT id FROM device WHERE imei = 'TEST' LIMIT 1")

How i can correctly pass named query to Get?

Can you help me?

Log the value of imei before your query - e.g.
log.Printf("imei before: %v", imei)
err := DB.Get(&device, "SELECT id FROM device WHERE imei = $1 LIMIT 1", imei)
log.Printf("imei after: %v", imei)

Also use the psql command line client for PostgreSQL to run your query against whichever IMEI you're checking against to 100% confirm that that IMEI exists.

Yes, imei exsts. I run the query on datadase. Imei is a fixed strings that i sent to app. Now its only a test.

Im using mysql.
imei = "TEST"
err := DB.Get(&device, "SELECT id FROM device WHERE imei = $1 LIMIT 1", imei)

I gave up. Now it is working with pure sql/database. Thanks.

MySQL? Use ? instead of $1 / $2 / etc. I had assumed you were using the
right placeholder type for your database.
On Mon, 2 Nov 2015 at 1:42 AM, prsolucoes<EMAIL_ADDRESS>wrote:

I gave up. Now it is working with pure sql/database. Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/jmoiron/sqlx/issues/183#issuecomment-152848163.

Even if you decide not to use sqlx, please read the sqlx documentation as it contains a lot of general information that is useful to most users of database/sql.  It would have cleared up your bindvar issue.


[FAQ] Default value for tooltip formatter on pie chart

What problem does this feature solve?
Does somebody know what is the default tooltip.formatter value for pie charts ?
Currently I am using version 5.4.2, and for previous versions it was like this {a}
{b}: {c} ({d}%), but now you can see that there is an icon near category name, and I want to catch it.
I want to get something similar to this formatter: {b.icon} {b}: {c} ({d}%)
More information you can get here
What does the proposed API look like?
option = {
  title: {
    text: 'Referer of a Website',
    subtext: 'Fake Data',
    left: 'center'
  },
  tooltip: {
    trigger: 'item',
    formatter: '{b.icon} {b}: {c} ({d}%)'
  },
  legend: {
    orient: 'vertical',
    left: 'left'
  },
  series: [
    {
      name: 'Access From',
      type: 'pie',
      radius: '50%',
      data: [
        { value: 1048, name: 'Search Engine' },
        { value: 735, name: 'Direct' },
        { value: 580, name: 'Email' },
        { value: 484, name: 'Union Ads' },
        { value: 300, name: 'Video Ads' }
      ],
      emphasis: {
        itemStyle: {
          shadowBlur: 10,
          shadowOffsetX: 0,
          shadowColor: 'rgba(0, 0, 0, 0.5)'
        }
      }
    }
  ]
};

Thanks for your advice. The label has been added.


Failing when macro has % in it, e.g. Tracing

Here's a sample code:
            TraceLayer::new_for_http()
                .make_span_with(|request: &Request<Body>| {
                    tracing::info_span!(
                        "request",
                        method = %request.method(),
                        uri = %request.uri(), status = tracing::field::Empty,
                        latency = tracing::field::Empty,
                    )
                })

this uses a macro from tracing to create the Span. However the % in there makes rustfmt fail.

Thanks for reaching out.  What version of rustfmt are you using? (run rustfmt --version to find out). I'm using rustfmt 1.5.1-nightly (38659ec6 2022-08-18), and can't reproduce any issues. Are you using any non default config options? Could you please post the larger code snippet.

$ rustfmt --version
rustfmt 1.5.1-stable (4b91a6e 2022-08-08)

reproducible examples: (add tracing = "0.1.36" to Cargo.toml)
fn main() {
    let span = tracing::info_span!("request", method = %request.method(), uri = %request.uri(), status = tracing::field::Empty, latency = tracing::field::Empty,);
}

fn main() {
    let span = tracing::info_span!(
        "request",
        method = %request.method(),
        uri = %request.uri(), status = tracing::field::Empty,
        latency = tracing::field::Empty,
    );
}

expected output:
fn main() {
    let span = tracing::info_span!(
        "request",
        method = %request.method(),
        uri = %request.uri(),
        status = tracing::field::Empty,
        latency = tracing::field::Empty,
    );
}

If you remove the % in examples, you'll get the same output as "expected", obviously without the %. Otherwise, rustfmt doesn't make any change to the two examples.

We actually don't need to to add tracing = "0.1.36" to Cargo.toml to reproduce. I understand now that the issue is that we're not formatting the macro at all, and unfortunately as things currently stand there's not much we can do. You're correct that the % are causing the issue.
Formatting macros is tricky as they can contain arbitrary tokens and in this case the % prevents us from parsing the macro args as valid rust code so we just emit the macro as is. rustfmt isn't programmed to handle cases where macro args don't parse as valid rust code e.g %request.
The only way to handle this would be to special case the info_span! macro and customize how we parse and format its args. Given the team's backlog this is an extremely low priority item.

I'm not familiar with the tracing::info_span! macro, and found some more details on the % by reading the Recorder Fields section of the docs. Looks like ? is also used sometimes.

I'lll just add that while ? is also used, it behaves slightly differently.
One can use any of the following with the first three being equivalent and the fourth through sixth being equivalent.

o tracing::info!(?x, "text")
x tracing::info!(x = ?x, "text")
o tracing::info!(x = format!("{x:?}"), "text")
x tracing::info!(%x, "text")
x tracing::info!(x = %x, "text")
o tracing::info!(x = format!("{x}"), "text")

Only the first, third, and sixth (with o in front of them) are being considered by rustfmt. I am somewhat surprised by the first one since that does not seem like valid rust syntax either.
In case this is done by making exception for the tracing macros, these are the macros I know of where this syntax is permissible:

List of macros

span!
debug_span!
info_span!
warn_span!
error_span!
event!
debug!
info!
warn!
error!

I'm seeing this issue on rustfmt 1.7.0-nightly (f9b16149 2024-04-19), mainly with the ? sigil rather than the %. It seems like not only does the macro itself not get formatted, neither does any of the surrounding code.

@saffaffi the Issues with ? and % are the same. rustfmt can only format a macro calls if it's able to parse their arguments as valid rust syntax. The ?x in the macro call tracing::info!(?x) isn't valid rust.
You won't notice the impact of rustfmt failing to format tracing::info!(?x) because you probably already expect that's how it should be formatted, however, in other cases failing to format a long macro could lead to surrounding code being left unformatted.
It would be best for you to open a new issue and provide a minimal code example that demonstrates the problem you're currently experiencing.


Markdown code blocks are badly rendered

so apparently I'm having a problem with the code blocks in markdown, where all the whitespace preceding the first line is being trimmed off, or there is some more that is being appended on the subsequent lines, no idea which one of the two is the case.
to give you more context, if I write:
$ git remote rm origin
$ git remote add origin git://your/repository/git

(that is prepending 4 spaces before each line)
the output is:
$ git remote rm origin
       $ git remote add origin git://your/repository/git

the generated markup is the following:

$ git remote rm origin
       $ git remote add origin git://your/repository/git

:sob:
doesn't change anything if I use
    ```

to wrap the code in markdown

the problem was on my side, more specifically in the way a subtemplate inclusion tag was indented within the page template, (the {{{content}}} was too but that wasn't a problem apparently). this caused the mess in the output from handlebar!
Closing now.


#111 Created a bridge between the Pathlike and the Bucket API

closes #111
Submission Checklist

[ ] Bumped version number
[ ] Updated Documentation
[ ] Updated API Documentation
[ yes] Updated the changelog

@Nicoretti, I haven't yet acted on your comments about moving the code into a separate sub-module because the names and meanings of the classes have changed slightly. Please have another look and advise if you still want them to be moved into a sub-module.


Installing Plugin Error

I copied the adbox folder to the plugin folder in the engine. Once i activate it and restart the engine the plugin causes the engine to crash. My project is 4.12.5. i also tried 4.10 and 4.11 no luck. This looks awesome i need some type of large add in my project. Stupid that ureal only has banners still

Please follow the steps described in Readme file (Plugin Installation section). If you have any questions please don't hesitate to ask.


[Question]: Why Running Llama 2 require OpenAI API Key

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
When I am running the program using llama2_7b_chat, and at this line:
index = load_index_from_storage(storage_context)

It reports the error
Could not load OpenAI model. If you intended to use OpenAI, please check your OPENAI_API_KEY.
Original error:
No API key found for OpenAI.
Please set either the OPENAI_API_KEY environment variable or openai.api_key prior to initialization.
API keys can be found or created at https://platform.openai.com/account/api-keys
To disable the LLM entirely, set llm=None.

I am wondering why running Llama-2 still require an OpenAI key?
Thanks!

@DerrickYLJ you need to pass in the service context
service_context = ServiceContext.from_defaults(llm=llm, embed_model=embed_model, ...)
index = load_index_from_storage(storage_context, service_context=service_context)


Implement GitHub actions and Code Scanning

What Koala extension does this refer to (if applicable)
N/A
Is your feature request related to a problem? Please describe.
Currently we rely on Travis, which is great but doesn't have certain options such as code scanning which can be used to automatically look for security issues (or at least I haven't looked into it)
Describe the solution you'd like
Create an actions workflow that repeats what is done by Travis (incase we had to stop using it, but also redundancy) and utilise CodeQL Analysis (code scanning)
Describe alternatives you've considered
N/A
Additional context
Suggested by @ChrisF999

Also can look into Jenkins Webhook support within Actions


HUE-5169 [spark] cannot spark submit jar or python

cannot spark submit jar or python due to incorrect params to create livy session.
The Spark Livy create batch session api does not accept 'pyFiles' == null or 'files' == null params.

Thanks for the patch!
And to avoid some duplication, how about we just don't set them when they are empty?
properties = {
   ...
   ... without 'py_file' and 'files'
}

if snippet['properties'].get('py_file'):
  properties['pyFiles'] = snippet['properties']['py_file']
if snippet['properties'].get('files'):
  properties['files'] = snippet['properties']['files']

I am afraid not. The keys in properties for submit jar and python are different. For submitting jar, the 'file' field value is extracted from 'app_jar', while for submitting python, the 'file' field value is extracted from 'py_file', and 'className' param is not needed.
Moreover, the Spark Livy create batch session api does not accept 'pyFiles' or 'files' params at all, no mater whether they are null or not.

@romainr: fyi

Thanks! I see, this would fix errors like this?
'PySpark
"java.lang.NoSuchFieldError: PYSPARK_ARCHIVES" (error 500)'

And could you just sign the legal list of contributors?
https://github.com/cloudera/hue/wiki/Ccla

Done


Higher register spilling when using block pointers

We are considering switching our GEMM implementation to block pointers.
Currenly we use old-style manual operations to generate blocks of pointers. Switching to block pointers works, but results in significantly more spilled registers as reported by ptxas and runs slower on several internal benchmarks. From comparing TTIR and looking at MakeTensorPtrOp and RewriteTensorPointer.cpp I assume the problem comes from permanent usage of 64-bit pointers in the block pointer approach. Currently using manual generation of pointers we decide ourselves based on tensor dimensions whether we need 64-bit pointers or are 32-bit ones sufficient.
I attach the source with 2 kernel implementations to compare (just copied from the tutorials) and the results of its compilation.
ptxas info    : 0 bytes gmem
ptxas info    : Compiling entry function 'matmul_kernel_0d1d2d34567c89c1011c' for 'sm_80'
ptxas info    : Function properties for matmul_kernel_0d1d2d34567c89c1011c
    664 bytes stack frame, 1048 bytes spill stores, 1040 bytes spill loads
ptxas info    : Used 255 registers, 400 bytes cmem[0]

ptxas info    : 0 bytes gmem
ptxas info    : Compiling entry function 'matmul_kernel_with_block_pointers_0d1d2d34567c89c1011c' for 'sm_80'
ptxas info    : Function properties for matmul_kernel_with_block_pointers_0d1d2d34567c89c1011c
    1080 bytes stack frame, 2012 bytes spill stores, 1540 bytes spill loads
ptxas info    : Used 255 registers, 400 bytes cmem[0]

matmul.py.txt
matmul_kernel.ttir.txt
matmul_kernel_with_block_pointers.ttir.txt

cc @LyricZhao

To align with TMA, the current code does all the calculation in i64 mode. How about adding a new option require_i64 to make_block_ptr? @ptillet This will only take effect while the target is < sm_90.

Yes, i think it's a good idea!

OK, I will work on it in the next week :)

Hi guys, I will work on this fix since @LyricZhao is busy with other works.


unable to run the project.

My environment is perfectly set up and I tried to run other projects they are running perfectly fine. Please find the error below.
error Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:

Fixed with commit