Shader error with Unity 2018.1 (mac)

Cannot play example scene in Unity 2018.1.2f1 - getting shader errors:
Shader error in 'GLTF/PbrMetallicRoughness': invalid subscript 'uv2' at /Applications/Unity/Unity.app/Contents/CGIncludes/UnityStandardMeta.cginc(21) (on metal)
Shader error in 'GLTF/PbrSpecularGlossiness': invalid subscript 'uv2' at /Applications/Unity/Unity.app/Contents/CGIncludes/UnityStandardMeta.cginc(21) (on metal)

Ah these errors disappear once you build the GLTFSerialization.dll Plugins!
But now you get these compiler errors:
Assets/UnityTestTools/IntegrationTestsFramework/TestRunner/Editor/PlatformRunner/PlatformRunner.cs(93,16): error CS1502: The best overloaded method match for string.IsNullOrEmpty(string)' has some invalid arguments`
Assets/UnityTestTools/IntegrationTestsFramework/TestRunner/Editor/PlatformRunner/PlatformRunner.cs(93,30): error CS1503: Argument #1' cannot convert UnityEditor.Build.Reporting.BuildReport' expression to type `string'

While it builds ok in Unity 2108.1.2 (didn't build using older version of Unity 2017) you get the following "ShaderNotFoundException" error.

Is it possible to avoid the build step for GLTFSerialization.dll?
I made a fork of the repo and and it seems to work as scripts with some minor changes:
https://github.com/deadlyfingers/UnityGLTF/tree/unity2017-uwp/UnityGLTF/Assets/UnityGLTF/GLTFSerialization

I think the GLTF shaders need to be moved into the Resources folder as they are not referenced by anything in the test scenes and as a result don't get added to the appx. The code loads them using Shader.Find so they either need to be referenced by a material in use or by adding to Resources folder which will include them automatically or an equivalent. (I tried adding to the ''Always Include' list in Player > Graphics but this resulted in a hang using Unity 2017.4.3f1).


Failure in calculation?

I just want to understand what the author of TeslaLogger said about the calucation of efficienty (I guess) and a potential fault in TeslaMate, see  german forum post.
Can you ad your 2cents?
Thanks.

He's probably referring to the efficiency factors / "Wh_km" that are part of the vehicle detection:
https://github.com/adriankumpf/teslamate/blob/d0cec8435d37db00018bdd4088302c6c87e257e5/lib/teslamate/vehicles/identification.ex#L31-L59
I  copied those factors since that is most reliable source I found. I could only verify the given factor for the Model 3 (0.153). Some factors might be inaccurate and for some vehicles there simply is no factor. So he's right, that might lead to inaccurate or empty consumption values. Also, the way the calculation is done (by both TeslaLogger & TeslaMate) is by no means 100% accurate. It's more or less an estimation. Although it should be fairly accurate in most cases (given the efficiency factor is correct).
I also think his approach of collecting user data to improve those factors is perfectly valid. It might have been better to make that decision transparent to the users, but that's just my 2 cents.
With TeslaMate v1.7.0 there now is a dashboard panel that shows the derived efficiency factors for the users vehicle. If someone notices a discrepancy between the default and the derived factor he/she can create an issue, so that the default factors can be updated. I prefer that crowdsourcing approach and hope that this will help to complete the missing factors.

Oh, I almost forgot: thank you for bringing up TeslaMate in the TFF forum! All my posts mentioning TeslaMate got blocked (had a fresh account).

Thanks. Yeah I spot your crowdsourcing approach in the code already, just keep my eyes on commits the last week 😉

Wouldn't an own thread make sense in TFF?
Or is this here the place to discuss and ask questions?

I have lost my interest in this forum ever since they blocked all my posts that mentioned TeslaMate, to be honest. I don't like that gatekeeping approach.
GitHub is definitely the better place. It also makes it easier to keep track of issues and feature requests since everything is neatly separated instead of one long thread.
I like the idea of spreading the word on TFF though ... :D

GitHub is definitely the better place. It also makes it easier to keep track of issues and feature requests since everything is neatly separated instead of one long thread.

Indeed, I agree. I only looked into Teslamate today, but I've got the impression of a very lively community here.

I like the idea of spreading the word on TFF though ... :D

:-) Let's go...


Appstudio update test-component-pac-ugjx

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-ugjx-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
46 seconds
build-container

✅ Succeeded
10 seconds
sast-snyk-check

✅ Succeeded
7 seconds
sbom-json-check

✅ Succeeded
8 seconds
inspect-image

✅ Succeeded
9 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
37 seconds
clamav-scan

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
7 seconds
show-summary

Pipelines as Code CI/test-component-pac-ugjx-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
9 seconds
sast-snyk-check

✅ Succeeded
25 seconds
build-container

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
22 seconds
deprecated-base-image-check

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
23 seconds
inspect-image

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary


fix install jars script and docs

Small PR to fix the installation script for the Spark JARS.

I created a new venv, installed TEEHR per the instructions, installed the Spark Jars, and ran the examples...all worked as intended.


Replace Builder in creation scheme with a Context

The builder can hang off of the context object.

The Builder, Clock and Environment can hang off of this Context object

Closed in #218


Update error msg for windows download failed due to cert error

On commnunity version, dbeaver Custom Truststore feature is not avaliable. Removing the relative message to prevent misleading the users.
Reference: https://github.com/dbeaver/dbeaver/wiki/Managing-Truststore-Settings

Thank you for contribution.
The mentioned setting is available in all editions. It allows to switch between windows store and java store.
"It might help if you haven't overridden trust store." is talking only about possibility of changing the trust stores - for example, this way https://github.com/dbeaver/dbeaver/wiki/Importing-CA-certificates-from-your-local-Java-into-DBeaver (works for all editions). So the the removed part of the error message is still useful. I believe we actually don't want to remove it.

Thank you for contribution. The mentioned setting is available in all editions. It allows to switch between windows store and java store. "It might help if you haven't overridden trust store." is talking only about possibility of changing the trust stores - for example, this way https://github.com/dbeaver/dbeaver/wiki/Importing-CA-certificates-from-your-local-Java-into-DBeaver (works for all editions). So the the removed part of the error message is still useful. I believe we actually don't want to remove it.

Thanks @E1izabeth . Just want to double check.  Is Use Windows trust store features avaliable in all editions?  Can not locate it in either Version 23.2.2 or Version 21.3.5.

This setting is available in all editions and should appear in Preferences->Connections if you are running DBeaver under Windows.

I don't see either this setting on your Connections preference page either some other settings like Connection name pattern with Example result. I doubt why that settings didn't come for you. Could you send the log files? You can find instructions here https://dbeaver.com/docs/wiki/Log-files/.


fix: user can edit category and description if paid

Details

The employee can edit description and category of paid request by deep link

Fixed Issues

$ https://github.com/Expensify/App/issues/37910
PROPOSAL: https://github.com/Expensify/App/issues/37910#issuecomment-1984056331
Tests

As a employee, create a request
Go to admin account and pay the above request
As a admin, go to detail request paid and click edit category
Copy URL
Access this URL in the employee account
The not found page should be displayed

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

Offline tests

QA Steps

As a employee, create a request
Go to admin account and pay the above request
As a admin, go to detail request paid and click edit category
Copy URL
Access this URL in the employee account
The not found page should be displayed

[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: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[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 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(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[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.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/161821005/34dec3ba-421a-475a-bd99-d81126c6b5c5

Android: mWeb Chrome

https://github.com/Expensify/App/assets/161821005/3809800b-3b6f-4b7a-bcf0-a7eae73e35a2

iOS: Native

iOS: mWeb Safari

https://github.com/Expensify/App/assets/161821005/e950dde6-d778-43d6-ad97-691264f3177b

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/161821005/1a375314-f1a0-4d11-a79d-4d8dfcf72f74

MacOS: Desktop

@nkdengineer Please help to merge the latest main

@DylanDylann I just merged main.

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] 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)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] 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).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] 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.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] 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.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] 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
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] 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)
[ ] 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)
[ ] All JSX used for rendering exists in the render method
[ ] 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

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

[ ] 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

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

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

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] 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)
[ ] 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.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] 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.
[ ] 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.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

BUG: Can't edit the description/category in split bill
https://github.com/Expensify/App/assets/141406735/f84ec9eb-9851-4390-a78c-2b9546c2b2de

@DylanDylann I fixed the issue you mentioned in comment. Here is the result:

@DylanDylann I updated IOS native and desktop video

I don't know what's up with Melvin bot.
https://github.com/Expensify/App/assets/705000/f4561ace-69e1-43c5-ac3e-5ef5c665de1e

🚀 Deployed to staging by https://github.com/tylerkaraszewski in version: 1.4.56-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.4.56-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[Accessibility][Usability]A11y_VSCode_ActivityBar_Keyboard: The selected item is not identified with mouseover item.

Environment Details:
VSCode Version : 1.24.0
OS Version : Win10
Additional Details:
Keyboard,Usability
Repro Steps:
1.Navigate to "Activity Bar" at left side of the screen after login.
2.Navigate to any item such as "Explorer,Search,SourceControl,Debug,Extensions,Setting" buttons.
3.Clicked on any one mentioned button and through mouseover move the mouse to any one remaining button.
3.Observed that there is same focus is visible to user.
Actual:
After clicking on "Explorer" button then using tab/mouseover move to other button list except "Explorer" then it shows same focus color to each becuase of this user will not able to differentiate which button is selected.
Expected:
There should be some difference between the selected and non selected item. if explorer is selected then it should be dark and if other buttons are not selected then it should not look like selected.
Recommendations:
Refer below link which is repository of bug fixes code snippets.
https://microsoft.sharepoint.com/teams/msenable/mas/Pages/browse-fixes.aspx
User Impact:
User will not able to differentiate the selected and non selected button from activity bar.
Attachment For Reference:
[Accessibility][Usability]A11y_VSCode_ActivityBar_Keyboard.pptx
Does this issue occur when all extensions are disabled?: Yes

High contrast theme for reference:

This is as designed for now. And we have no plans to support this in non high contrast themes.
Every theme author can add this, thus it is up to extensions to support this if they want to.


route steps design

Description
Update route steps according to new design :

Updated fonts
Updated layout : distance is now displayed under the direction step.
Updated origin and destination icons, for now I used the new svg icon to be consistent with the new direction form. Integrating new icons asked by design + colors logic (depending on the type of poi) will be implemented in another changes set.
Used Divider where possible and cleaned some css styles. Hopefully nothing is broken.

Screenshots

Nice simplification.
Some specific rules are still need to make sure the RoadMapStep component looks good even when used in the mobile step-by-step context, as now the paddings look off.

Thanks, should be better now.


[Task] Add IP command to the API

This is necessary to determine where the host in the console commands should be poining
OR consider #2896

Not desirable... Either include the information in status or do not rely on this information; best to use fixed domain names.


Coordinator-tool initial-weights verify doesn't work

Bug Description
Steps to Reproduce
Trying to run
PS C:\repositories\concordium-governance-committee-voting\coordinator-tool\target\release> .\election-coordinator.exe initial-weights verify --node grpc.testnet.concordium.com --contract "<8866,0>"
error: the following required arguments were not provided:
  --out <OUT>

Usage: election-coordinator.exe initial-weights --out <OUT> <COMMAND>

Then trying to run:
PS C:\repositories\concordium-governance-committee-voting\coordinator-tool\target\release> .\election-coordinator.exe initial-weights verify --node grpc.testnet.concordium.com --contract "<8866,0>" --out test.csv
error: unexpected argument '--out' found

Usage: election-coordinator.exe initial-weights --out <OUT> verify --node <NODE_ENDPOINT> <--contract <CONTRACT>>

For more information, try '--help'.

Note that message provided second time also looks weird
` <--contract >
`Expected Result
User should be able to verify weights.
Actual Result
As it looks it is not possible to verify.
Versions

Software Version: 1.0.0

This is not a bug, but the intended design. It might be a little confusing that some parameters are specified between commands, but it should be clear from the documentation.


Add iOS target using Compose Multiplatform

Describe the solution you'd like
Add platform-specific code for iOS, using JetBrains Compose Multiplatform.
JB Compose iOS support is now in Alpha compose-multiplatform/releases/tag/v1.4.0 and enables the use of UiKit views in Compose.
Kotlin Multiplatform Mobile recently moved to Beta and cocoapods integration works: kotlinlang.org/docs/native-cocoapods.html
Since android-maps-compose library is a wrapper for an Android view, it may result easy to adapt the existing structure to wrap also iOS objective-c Maps sdk.
A quick implementation labeled as alpha could come handy for developers to start playing with it, while waiting JB Compose iOS support to exit Alpha state.

If you would like to upvote the priority of this issue, please comment below or react with :+1: so we can see what is popular when we triage.
@dogeweb Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

This is interesting! Adding a help wanted tag and pinning for anyone who wants to explore what it takes to add Compose MP and iOS support.

An existing challenge with Compose multiplatform apps pertains to the availability of appropriate libraries for incorporating the Map feature. The prospect of Google extending its support in this regard holds immense potential, as it could significantly bolster the advancement of Compose Multiplatform apps.

I have had success with using compose for iOS with UIKitView to render google maps.
The only part I dont have so far is the "on_____Click" call backs, so I am not able to write custom handlers for "on____Click" events.
I'm an Android dev, so I'm not sure whats necessary to make the work using Kotlin on the iOS side... all the sample code does not refer to this use case.
Here's a link to my repo. Maps are currently rendering on iOS and Android.
https://github.com/realityexpander/ContactsComposeMultiplatform
Be sure to manually give location permission on the Android, I havent implemented that part yet.
you will need to get your own google maps api key.
This is still a work in progress, and its a good head start!

So am I to understand that ive hit a dead end with looking to get "onMapClick" type of events from the Google MapView on iOS?
That I should probably wait on the Google Maps iOS "onMapClick" types of integrations?
That its likely not possible now without more low level work?

My versions....
#Gradle
org.gradle.jvmargs=-Xmx2048M -Dkotlin.daemon.jvm.options\="-Xmx2048M"

#Kotlin
kotlin.code.style=official

#MPP
kotlin.mpp.stability.nowarn=true
kotlin.mpp.enableCInteropCommonization=true
kotlin.mpp.androidSourceSetLayoutVersion=2

#Android
android.useAndroidX=true
android.compileSdk=34
android.targetSdk=34
android.minSdk=24

#Compose
org.jetbrains.compose.experimental.uikit.enabled=true

#Versions
kotlin.version=1.9.10
agp.version=8.0.2
compose.version=1.5.3

# Google Maps
google.maps.secrets-gradle-plugin.version=2.0.1

val androidMain by getting {
            dependencies {

                api("androidx.activity:activity-compose:1.8.0")
                api("androidx.appcompat:appcompat:1.6.1")
                api("androidx.core:core-ktx:1.12.0")

                // Google maps for Compose for Android
                api("com.google.android.gms:play-services-location:21.0.1")
                api("com.google.android.gms:play-services-maps:18.1.0")
                implementation("com.google.maps.android:maps-compose:$mapsComposeVersion")
                // clustering
                implementation("com.google.maps.android:maps-compose-utils:$mapsComposeVersion")

                // Ktor Client for Android
                implementation("io.ktor:ktor-client-android:$ktorClientVersion")

                // For Logger in Android todo (why doesn't this automatically put this in shared android module?)
                api("co.touchlab:kermit:2.0.1")
            }
        }

GMSMapViewDelegateProtocol

I was looking at your project to build mine. Yes, this error exists, but the application compiles and works :)

`
agp.version=8.1.2
android.defaults.buildfeatures.buildconfig=true
android.enableJetifier=true
android.nonFinalResIds=false
android.nonTransitiveRClass=true
android.useAndroidX=true
compose.version=1.5.3
kotlin.code.style=official
kotlin.mpp.androidGradlePluginCompatibility.nowarn=true
kotlin.mpp.androidSourceSetLayoutVersion=2
kotlin.mpp.enableCInteropCommonization=true
kotlin.version=1.9.10
org.gradle.jvmargs=-Xmx2048M -Dfile.encoding=UTF-8 -Dkotlin.daemon.jvm.options="-Xmx2048M"
org.jetbrains.compose.experimental.uikit.enabled=true
Google Maps
google.maps.secrets-gradle-plugin.version=2.0.1and androidMain:  val androidMain by getting {
dependencies {
implementation("app.cash.sqldelight:android-driver:$sqlDelightVersion")
implementation("androidx.lifecycle:lifecycle-viewmodel-ktx:2.6.1")
implementation("androidx.appcompat:appcompat:1.6.1")
api("androidx.core:core-ktx:1.10.1")
implementation("io.insert-koin:koin-core:$koinVersion")
implementation("io.insert-koin:koin-android:$koinVersion")
// Google maps for Compose
api("com.google.android.gms:play-services-location:21.0.1")
api("com.google.android.gms:play-services-maps:18.1.0")
implementation("com.google.maps.android:maps-compose:$mapsComposeVersion")
// For clustering
implementation("com.google.maps.android:maps-compose-utils:$mapsComposeVersion")
}
}`

Yes, i have it working on the Android side with no problems... this is an iOS issue...
Do you have the functionality on the iOS side?

I think we need to make an issue in the multiplatform compose branch, because the inability to add a delegate normally (I think so) is a library problem.

Where would that get posted? Im sure they know about it, the way im handling it on iOS side is a bit of hack, but it works, so we know it will improve from here.

Yes, i have it working on the Android side with no problems... this is an iOS issue...
Can you show the iosMain gradle versions?
Do you have the functionality on the iOS side?
Are you receiving callbacks on the iOS side for the Google Maps?
Yes, it compiles... but does it execute?

Yes it works well on the iOS side. Above I have attached a screenshot where you can clearly see the log with the print.
 cocoapods {
        summary = "Some description for the Shared Module"
        homepage = "Link to the Shared Module homepage"
        version = "1.0"
        ios.deploymentTarget = "17.0"
        podfile = project.file("../iosApp/Podfile")
        framework {
            baseName = "shared"
            isStatic = true
        }
        pod("GoogleMaps") {
            version = "8.2.0"
        }
    }

Btw use "val googleMapView = GMSMapView()" not " val googleMapView = remember { GMSMapView() }" that helped me.

GoogleMaps.zip
it's from ur project, all working properly

OK, im confused here…
Is the Google Maps “tapOnMarker” functionality working for you on the iOS side?
Yes, it all works on Android, that’s not the problem.
Are you able to use the “tapOnMarker” callback on the iOS side, or just giving the compile warning and doesn’t actually received tap events?
Thanks for the responses!
Best,
Chris

On Oct 19, 2023, at 2:19 AM, MascotWorld @.***> wrote:
GoogleMaps.zip https://github.com/googlemaps/android-maps-compose/files/13039249/GoogleMaps.zip
it's from ur project, all working properly
—
Reply to this email directly, view it on GitHub https://github.com/googlemaps/android-maps-compose/issues/312#issuecomment-1770207932, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHLEYXP5PS5ETQKUQE6JWDYADH7BAVCNFSM6AAAAAAXF6YCHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZQGIYDOOJTGI.
You are receiving this because you were mentioned.

OK, im confused here… Is the Google Maps “tapOnMarker” functionality working for you on the iOS side? Yes, it all works on Android, that’s not the problem. Are you able to use the “tapOnMarker” callback on the iOS side, or just giving the compile warning and doesn’t actually received tap events? Thanks for the responses! Best, Chris
…
On Oct 19, 2023, at 2:19 AM, MascotWorld @.***> wrote: GoogleMaps.zip https://github.com/googlemaps/android-maps-compose/files/13039249/GoogleMaps.zip it's from ur project, all working properly — Reply to this email directly, view it on GitHub <#312 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHLEYXP5PS5ETQKUQE6JWDYADH7BAVCNFSM6AAAAAAXF6YCHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZQGIYDOOJTGI. You are receiving this because you were mentioned.

The callback works great!  you can check it yourself, I attached the file GoogleMaps.kt (from iosMain), you can replace it in your project and run it.

Looked at your info, and still not able to compile any GMSMapViewDelegateProtocol on the iOS side. Error is below.
OK, there must be a versions mismatch... Can I see your build.gradle.kts (:shared)
Thanks in advance!
Best,
Chris

i have same error, but project is compiles. Here is whole project(with build files) with working click: https://drive.google.com/file/d/10vpPs69yPxUMNiTv9UCXuHbkDoVnTdru/view?usp=share_link You can check it out

i have same error, but project is compiles. Here is whole project(with build files) with working click: https://drive.google.com/file/d/10vpPs69yPxUMNiTv9UCXuHbkDoVnTdru/view?usp=share_link You can check it out. in root is screen record where i show work

WOW! Thank you for supplying this...
I loaded your supplied project in both AS Giraffe and Hedgehog (Iguana is too new yet), and have the same problems...
Im now wondering what version of AS you are running?
Here's my version info:
Android Studio Giraffe | 2022.3.1 Patch 2
Build #AI-223.8836.35.2231.10811636, built on September 14, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.5.2
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 10
Metal Rendering is ON
Registry:
    analyze.exceptions.on.the.fly=true
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.tooltip.initialDelay=812
    ide.experimental.ui=true
    ide.browser.jcef.gpu.disable=true

Non-Bundled Plugins:
    com.github.kaustubhpatange.composecolor (0.0.7)
    com.c5inco.modifiers (1.0.14)
    com.github.DerekBum.composeSlidesPresenter (0.1.2)
    com.github.copilot (<IP_ADDRESS>79)
    wu.seal.tool.jsontokotlin (3.7.4)
    idea.plugin.protoeditor (223.8214.6)
    com.wakatime.intellij.plugin (14.2.3)
    com.github.airsaid.androidlocalize (3.0.0)
    DBN (3.4.1620.0)
    net.seesharpsoft.intellij.plugins.csv (3.2.2-223)
    org.jetbrains.kotlin-js-inspection-pack-plugin (0.0.12)
    com.jetbrains.kmm (0.8.0(223)-25)
    com.squareup.sqldelight (2.0.0)
    com.developerphil.adbidea (1.6.12)
    org.jetbrains.compose.desktop.ide (1.5.3)
    by.overpass.svg-to-compose-intellij (0.12)
    mobi.hsz.idea.gitignore (4.4.4)
    com.abeade.plugin.figma.import (1.2.1)

Android Studio Hedgehog | 2023.1.1 RC 1
Build #AI-231.9392.1.2311.10949950, built on October 13, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.5.2
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 10
Metal Rendering is ON
Registry:
    analyze.exceptions.on.the.fly=true
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.tooltip.initialDelay=812
    ide.experimental.ui=true
    ide.browser.jcef.gpu.disable=true

Non-Bundled Plugins:
    com.c5inco.modifiers (1.0.14)
    com.github.copilot (<IP_ADDRESS>79)
    wu.seal.tool.jsontokotlin (3.7.4)
    org.jetbrains.kotlin (231-1.9.20-RC-release-459-AS8109.175)
    idea.plugin.protoeditor (231.9225.5)
    com.wakatime.intellij.plugin (14.2.3)
    com.github.airsaid.androidlocalize (3.0.0)
    DBN (3.4.1620.0)
    net.seesharpsoft.intellij.plugins.csv (3.2.2-231)
    com.jetbrains.kmm (0.8.0(231)-19)
    com.squareup.sqldelight (2.0.0)
    com.developerphil.adbidea (1.6.11)
    org.jetbrains.compose.desktop.ide (1.5.3)
    by.overpass.svg-to-compose-intellij (0.12)
    mobi.hsz.idea.gitignore (4.5.2)
    com.abeade.plugin.figma.import (1.2.1)

i have same error, but project is compiles. Here is whole project(with build files) with working click: https://drive.google.com/file/d/10vpPs69yPxUMNiTv9UCXuHbkDoVnTdru/view?usp=share_link You can check it out. in root is screen record where i show work

WOW! Thank you for supplying this...
I loaded your supplied project in both AS Giraffe and Hedgehog (Iguana is too new yet), and have the same problems...
Im now wondering what version of AS you are running?
Here's my version info:
Android Studio Giraffe | 2022.3.1 Patch 2
Build #AI-223.8836.35.2231.10811636, built on September 14, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.5.2
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 10
Metal Rendering is ON
Registry:
    analyze.exceptions.on.the.fly=true
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.tooltip.initialDelay=812
    ide.experimental.ui=true
    ide.browser.jcef.gpu.disable=true

Non-Bundled Plugins:
    com.github.kaustubhpatange.composecolor (0.0.7)
    com.c5inco.modifiers (1.0.14)
    com.github.DerekBum.composeSlidesPresenter (0.1.2)
    com.github.copilot (<IP_ADDRESS>79)
    wu.seal.tool.jsontokotlin (3.7.4)
    idea.plugin.protoeditor (223.8214.6)
    com.wakatime.intellij.plugin (14.2.3)
    com.github.airsaid.androidlocalize (3.0.0)
    DBN (3.4.1620.0)
    net.seesharpsoft.intellij.plugins.csv (3.2.2-223)
    org.jetbrains.kotlin-js-inspection-pack-plugin (0.0.12)
    com.jetbrains.kmm (0.8.0(223)-25)
    com.squareup.sqldelight (2.0.0)
    com.developerphil.adbidea (1.6.12)
    org.jetbrains.compose.desktop.ide (1.5.3)
    by.overpass.svg-to-compose-intellij (0.12)
    mobi.hsz.idea.gitignore (4.4.4)
    com.abeade.plugin.figma.import (1.2.1)

Android Studio Hedgehog | 2023.1.1 RC 1
Build #AI-231.9392.1.2311.10949950, built on October 13, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.5.2
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 10
Metal Rendering is ON
Registry:
    analyze.exceptions.on.the.fly=true
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.tooltip.initialDelay=812
    ide.experimental.ui=true
    ide.browser.jcef.gpu.disable=true

Non-Bundled Plugins:
    com.c5inco.modifiers (1.0.14)
    com.github.copilot (<IP_ADDRESS>79)
    wu.seal.tool.jsontokotlin (3.7.4)
    org.jetbrains.kotlin (231-1.9.20-RC-release-459-AS8109.175)
    idea.plugin.protoeditor (231.9225.5)
    com.wakatime.intellij.plugin (14.2.3)
    com.github.airsaid.androidlocalize (3.0.0)
    DBN (3.4.1620.0)
    net.seesharpsoft.intellij.plugins.csv (3.2.2-231)
    com.jetbrains.kmm (0.8.0(231)-19)
    com.squareup.sqldelight (2.0.0)
    com.developerphil.adbidea (1.6.11)
    org.jetbrains.compose.desktop.ide (1.5.3)
    by.overpass.svg-to-compose-intellij (0.12)
    mobi.hsz.idea.gitignore (4.5.2)
    com.abeade.plugin.figma.import (1.2.1)

Android Studio Giraffe | 2022.3.1 Patch 2
Build #AI-223.8836.35.2231.10811636, built on September 15, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.0
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Metal Rendering is ON
Registry:
external.system.auto.import.disabled=true
debugger.new.tool.window.layout=true
ide.text.editor.with.preview.show.floating.toolbar=false
ide.experimental.ui=true
Non-Bundled Plugins:
com.c5inco.modifiers (1.0.14)
com.levinzonr.arch.jetpackcompose.plugin (1.1.0)
com.jetbrains.kmm (0.6.1(223)-18)
com.squareup.sqldelight (2.1.0-SNAPSHOT-1697294713387)
org.jetbrains.compose.desktop.ide (1.5.3)
com.thelumiereguy.compose_helper (2.0.4)

i have same error, but project is compiles. Here is whole project(with build files) with working click: https://drive.google.com/file/d/10vpPs69yPxUMNiTv9UCXuHbkDoVnTdru/view?usp=share_link You can check it out. in root is screen record where i show work

WOW! Thank you for supplying this...
I loaded your supplied project in both AS Giraffe and Hedgehog (Iguana is too new yet), and have the same problems...
Im now wondering what version of AS you are running?
Here's my version info:
Android Studio Giraffe | 2022.3.1 Patch 2
Build #AI-223.8836.35.2231.10811636, built on September 14, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.5.2
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 10
Metal Rendering is ON
Registry:
    analyze.exceptions.on.the.fly=true
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.tooltip.initialDelay=812
    ide.experimental.ui=true
    ide.browser.jcef.gpu.disable=true

Non-Bundled Plugins:
    com.github.kaustubhpatange.composecolor (0.0.7)
    com.c5inco.modifiers (1.0.14)
    com.github.DerekBum.composeSlidesPresenter (0.1.2)
    com.github.copilot (<IP_ADDRESS>79)
    wu.seal.tool.jsontokotlin (3.7.4)
    idea.plugin.protoeditor (223.8214.6)
    com.wakatime.intellij.plugin (14.2.3)
    com.github.airsaid.androidlocalize (3.0.0)
    DBN (3.4.1620.0)
    net.seesharpsoft.intellij.plugins.csv (3.2.2-223)
    org.jetbrains.kotlin-js-inspection-pack-plugin (0.0.12)
    com.jetbrains.kmm (0.8.0(223)-25)
    com.squareup.sqldelight (2.0.0)
    com.developerphil.adbidea (1.6.12)
    org.jetbrains.compose.desktop.ide (1.5.3)
    by.overpass.svg-to-compose-intellij (0.12)
    mobi.hsz.idea.gitignore (4.4.4)
    com.abeade.plugin.figma.import (1.2.1)

Android Studio Hedgehog | 2023.1.1 RC 1
Build #AI-231.9392.1.2311.10949950, built on October 13, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.5.2
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 10
Metal Rendering is ON
Registry:
    analyze.exceptions.on.the.fly=true
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.tooltip.initialDelay=812
    ide.experimental.ui=true
    ide.browser.jcef.gpu.disable=true

Non-Bundled Plugins:
    com.c5inco.modifiers (1.0.14)
    com.github.copilot (<IP_ADDRESS>79)
    wu.seal.tool.jsontokotlin (3.7.4)
    org.jetbrains.kotlin (231-1.9.20-RC-release-459-AS8109.175)
    idea.plugin.protoeditor (231.9225.5)
    com.wakatime.intellij.plugin (14.2.3)
    com.github.airsaid.androidlocalize (3.0.0)
    DBN (3.4.1620.0)
    net.seesharpsoft.intellij.plugins.csv (3.2.2-231)
    com.jetbrains.kmm (0.8.0(231)-19)
    com.squareup.sqldelight (2.0.0)
    com.developerphil.adbidea (1.6.11)
    org.jetbrains.compose.desktop.ide (1.5.3)
    by.overpass.svg-to-compose-intellij (0.12)
    mobi.hsz.idea.gitignore (4.5.2)
    com.abeade.plugin.figma.import (1.2.1)

this is my

Android Studio Giraffe | 2022.3.1 Patch 2
Build #AI-223.8836.35.2231.10811636, built on September 15, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.0
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Metal Rendering is ON
Registry:
    external.system.auto.import.disabled=true
    debugger.new.tool.window.layout=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.experimental.ui=true

Non-Bundled Plugins:
    com.c5inco.modifiers (1.0.14)
    com.levinzonr.arch.jetpackcompose.plugin (1.1.0)
    com.jetbrains.kmm (0.6.1(223)-18)
    com.squareup.sqldelight (2.1.0-SNAPSHOT-1697294713387)
    org.jetbrains.compose.desktop.ide (1.5.3)
    com.thelumiereguy.compose_helper (2.0.4)

It looks like we are using different versions of the jetbrains KMM plugin. You have an earlier version, and mine is the latest... looks like they broke it in the latest version...
Im going to explore if I can downgrade, or I'm locked in to the latest version.

this is my
Android Studio Giraffe | 2022.3.1 Patch 2
    com.jetbrains.kmm (0.6.1(223)-18)

It looks like we are using different versions of the jetbrains KMM plugin. You have an earlier version, and mine is the latest... looks like they broke it in the latest version...
mine: com.jetbrains.kmm (0.8.0(223)-25)
yours: com.jetbrains.kmm (0.6.1(223)-18)
Im going to explore if I can downgrade, or I'm locked in to the latest version.

Maybe this is the point) Try downgrading and report back how it turned out

Just tried to use it with the 0.6.1 version of KMM plugin inside Flamingo (newer AS are incompatible and will not load the plugin)
So, Im going to chalk this up as an unsolved mystery and await a better solution from google soon. At least the Android side works great, and compose is not an issue... It's a c-interop library issue. Since they addressed it on the Android side, I can only assume they are working on this for compose.

Just tried to use it with the 0.6.1 version of KMM plugin inside Flamingo (newer AS are incompatible and will not load the plugin) - Still has the same issue.
So, Im going to chalk this up as an unsolved mystery and await a better solution from google soon. At least the Android side works great, and compose is not an issue... It's a c-interop library issue.
Since they addressed it on the Android side for Google Maps in Compse, I can only assume Google or Jetbrains are working on this for compose for KMP.
can you show the error? my android studio itself updated the plugin (ahem) and I received an error related to Could not find "co.touchlab:stately-common" and I solved it)

Just tried to use it with the 0.6.1 version of KMM plugin inside Flamingo (newer AS are incompatible and will not load the plugin) - Still has the same issue.

So, Im going to chalk this up as an unsolved mystery and await a better solution from google soon. At least the Android side works great, and compose is not an issue... It's a c-interop library issue.

Since they addressed it on the Android side for Google Maps in Compse, I can only assume Google or Jetbrains are working on this for compose for KMP.

can you show the error? my android studio itself updated the plugin (ahem) and I received an error related to Could not find "co.touchlab:stately-common" and I solved it)

It's the same error as before

Its the exact same error as I have been showing in my previous replies.
Going back to previous versions of AS and KMM plug-in are not solutions for me at this time
Chris

On Oct 23, 2023, at 4:02 AM, MascotWorld @.***> wrote:
Just tried to use it with the 0.6.1 version of KMM plugin inside Flamingo (newer AS are incompatible and will not load the plugin) - Still has the same issue.
So, Im going to chalk this up as an unsolved mystery and await a better solution from google soon. At least the Android side works great, and compose is not an issue... It's a c-interop library issue.
Since they addressed it on the Android side for Google Maps in Compse, I can only assume Google or Jetbrains are working on this for compose for KMP.
can you show the error? my android studio itself updated the plugin (ahem) and I received an error related to Could not find "co.touchlab:stately-common" and I solved it)
—
Reply to this email directly, view it on GitHub https://github.com/googlemaps/android-maps-compose/issues/312#issuecomment-1774739041, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHLEYWNSGDD4QWZVZIA7Q3YAYXA7AVCNFSM6AAAAAAXF6YCHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZUG4ZTSMBUGE.
You are receiving this because you were mentioned.

@realityexpander there is a regression introduced in android-maps-compose 1.4.21 that causes recomposed GoogleMap listeners to not be used. Wonder if this might contribute to your obstacles. #466

The
override fun mapView(
            mapView: GMSMapView,
            didTapMarker: GMSMarker
) { .. }

definitely works. You just have to run the iOS app via Xcode and not via AS.
with AS, I have the same issue like you @realityexpander, I can't compile & have the same error (Return type is 'Boolean', which is not a subtype of overridden), thus can't run the iOS app via there.
Maybe you can try running the iOS app via xcode instead.

I'll give it a try, i did not try compiling and running from xcode.

Sharing support for Compose maps for kotlin multiplatform! Yes please!

I have made substantial progress on this by taking a different approach.
You can check my work at:
https://github.com/realityexpander/FredsRoadtripStoryteller

On Dec 19, 2023, at 8:47 AM, ColtonIdle @.***> wrote:
Sharing support for Compose maps for kotlin multiplatform! Yes please!
—
Reply to this email directly, view it on GitHub https://github.com/googlemaps/android-maps-compose/issues/312#issuecomment-1862896870, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHLEYVFKDPL7K62YALHWTLYKGSJNAVCNFSM6AAAAAAXF6YCHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRSHA4TMOBXGA.
You are receiving this because you were mentioned.

Here's a playlist on yt about how I approached the project:
https://www.youtube.com/playlist?list=PLzUxWOrVXB4QmB3xvfjqkOMDZpwZnFb2x

@wangela Any news for this topic?

This would definitely come in handy! Any new information on this topic?

Any update on this?


objc associatedObjects not working

objc associated objects do not seem to be working. In the following example the value is nil when accessed in the next runloop:
objc_setAssociatedObject(self, @"myObjKey", @"MOOSE", OBJC_ASSOCIATION_RETAIN_NONATOMIC);

 // object is "MOOSE"
NSLog(@"object %@", objc_getAssociatedObject(self, @"myObjKey"));

dispatch_async(dispatch_get_main_queue(), ^{
        // object is nil
	NSLog(@"object %@", objc_getAssociatedObject(self, @"myObjKey"));
});

Is there a chance that self is getting KVO-observed (or otherwise having its class manipulated) between the two calls?
From: Rupert Daniel<EMAIL_ADDRESS>Sent: Thursday, April 28, 2016 11:31 AM
To: Microsoft/WinObjC<EMAIL_ADDRESS>Subject: [Microsoft/WinObjC] objc associatedObjects not working (#463)
objc associated objects do not seem to be working. In the following example the value is nil when accessed in the next runloop:
objc_setAssociatedObject(self, @"myObjKey", @"MOOSE", OBJC_ASSOCIATION_RETAIN_NONATOMIC);
// object is "MOOSE"
NSLog(@"object %@", objc_getAssociatedObject(self, @"myObjKey"));
dispatch_async(dispatch_get_main_queue(), ^{
    // object is nil

NSLog(@"object %@", objc_getAssociatedObject(self, @"myObjKey"));

});
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/WinObjC/issues/463

Yeah for that sample code the next line was actually:
[self addObserver:self<EMAIL_ADDRESS>options:0 context:nil];
If I comment out the observer, objc_getAssociatedObject works as expected.

We just ran into this ourselves and are looking into solutions. Thanks for the report!

This is rolled up as part of the KVO performance improvment change @dhowett-msft is working on.


Add cupyx.scipy.ndimage.label

close #3119

Measured results on Quadro GV100 and CUDA 10.2
(dtype: int32, structure: None, output: None)

mean (stdev) [unit: ms]
scipy.ndimage
cupyx.scipy.ndimage
speedup

shape:(4000, 4000), density:0.1
78.196 (1.510)
3.684 (0.019)
21.2

shape:(4000, 4000), density:0.2
96.615 (0.263)
4.031 (0.026)
24.0

shape:(4000, 4000), density:0.3
119.272 (0.320)
4.169 (0.009)
28.6

shape:(4000, 4000), density:0.4
146.165 (0.219)
4.254 (0.023)
34.4

shape:(4000, 4000), density:0.5
169.757 (0.558)
4.230 (0.012)
40.1

shape:(8000, 8000), density:0.1
326.453 (0.962)
12.326 (0.045)
26.5

shape:(8000, 8000), density:0.2
411.575 (0.891)
13.562 (0.044)
30.3

shape:(8000, 8000), density:0.3
504.746 (0.509)
14.157 (0.027)
35.7

shape:(8000, 8000), density:0.4
612.297 (0.970)
14.444 (0.039)
42.4

shape:(8000, 8000), density:0.5
707.270 (0.836)
14.414 (0.046)
49.1

shape:(200, 200, 200), density:0.1
59.186 (0.499)
2.493 (0.012)
23.7

shape:(200, 200, 200), density:0.2
79.735 (0.056)
2.656 (0.008)
30.0

shape:(200, 200, 200), density:0.3
106.947 (0.236)
2.721 (0.006)
39.3

shape:(200, 200, 200), density:0.4
133.922 (0.211)
2.680 (0.008)
50.0

shape:(200, 200, 200), density:0.5
149.658 (0.409)
2.630 (0.007)
56.9

shape:(300, 300, 300), density:0.1
203.323 (0.289)
6.415 (0.016)
31.7

shape:(300, 300, 300), density:0.2
280.825 (1.175)
7.002 (0.019)
40.1

shape:(300, 300, 300), density:0.3
372.073 (0.789)
7.164 (0.024)
51.9

shape:(300, 300, 300), density:0.4
455.918 (0.789)
6.657 (0.021)
68.5

shape:(300, 300, 300), density:0.5
509.090 (0.733)
6.402 (0.014)
79.5

test script
import numpy
import scipy.ndimage as ndimage
import cupy
import cupyx.scipy.ndimage as cpx_ndimage
import time
from statistics import mean, stdev

nmeasure = 10
dtype = numpy.int32
structure = None
size_set = [
    [2, 4000],
    [2, 8000],
    [3, 200],
    [3, 300],
]
density_set = [0.1, 0.2, 0.3, 0.4, 0.5]

for j in range(len(size_set)):
    ndim = int(size_set[j][0])
    size = int(size_set[j][1])
    shape = (size,) * ndim

    for density in density_set:
        cpu_time = []
        gpu_time = []
        for i in range(nmeasure+1):
            x = numpy.zeros(shape, dtype=dtype)
            x[numpy.random.random(shape) < density] = 1
            cp_x = cupy.array(x)

            t1 = time.time()
            labels, num_features = ndimage.label(x, structure=structure)
            elapsed_ms = (time.time() - t1) * 1000
            if i > 0:
                cpu_time = cpu_time + [elapsed_ms]

            t1 = time.time()
            labels, num_features = cpx_ndimage.label(cp_x, structure=structure)
            cupy.cuda.runtime.deviceSynchronize()
            elapsed_ms = (time.time() - t1) * 1000
            if i > 0:
                gpu_time = gpu_time + [elapsed_ms]

        print('shape:{}, density:{} | {:.3f} ({:.3f}) | {:.3f} ({:.3f}) | {:.1f}'.format(shape, density, mean(cpu_time), stdev(cpu_time), mean(gpu_time), stdev(gpu_time), mean(cpu_time) / mean(gpu_time)) )

Thanks for adding this.
Not surprisingly, I got a bit lower acceleration factors of between 12 and 33 for your test cases on a 1080 GTX Ti GPU.
An edge case in the SciPy tests that currently fails here is for 0-dimensional arrays. SciPy has the following behavior:
in[1]: scipy.ndimage.label(np.array(5.))
Out[1]: (array(1, dtype=int32), 1)

in[2]: scipy.ndimage.label(np.zeros([]))
Out[2]: (array(0, dtype=int32), 0)

possibly add to the docstring
    .. warning::

        This function may synchronize the device.

(_label transfers a scalar back to the CPU).
I think handling 0-dim arrays as in SciPy would also require synchronization in that code path as it is necessary to check the value in the array to determine what to return.

Thanks for your feedback, @grlee77 !
I added code and unit tests for 0-dim array cases and the warning about synchronization.

pfnCI, test this please.

Jenkins CI test (for commit 72df6d52639375ad2b1de49c6345e80a7edce6da, target branch master) succeeded!

Thanks for your review, @takagi . I added fixes based on your comment. Could you check it again?

Thanks! pfnCI, test this please.

Jenkins CI test (for commit dfba4f9fdcf78d052b68dffd47765700c0f9ee13, target branch master) succeeded!


Running a virtual Ubuntu arm version of vscode on Apple's silicon chip does not display properly under the virtio-ramfb virtual graphics card

Running a virtual Ubuntu arm version of vscode on Apple's silicon chip does not display properly under the virtio-ramfb virtual graphics card

you can try: --disable-gpu


Rework Roles and Users to store Cell and MC

Coverage decreased (-46.7%) to 6.433% when pulling 3bc1c37f6c7a55bb35c011bd000247d827413552 on validate-role into 80b990e43bb53d2da5c77c0d224a5eeb0a4b921c on master.


Site Statistics page is not working (FC2)

May be a feature still in Test3 / test2.
E1 U6 S7 C6: P20

This is because there are no cron tasks set up for vervet that would create the statistics. that applies to both reg and cen

So....I would have thought that this might be resolved as part of the great merge, but your last comment @Captainkirkdawson appears to indicate otherwise?

Not needed on test2/3 so closing.

Checked and broken on LIVE, so reopening and moving across.

Site statistics do not work in production or in test.
In REG they contain; number of searches, number of records by type (ba, bu, ma) and total
Since REG is updated daily all fields change on a daily basis
In CEN  we could also have number of searches, number of records by type (1841, 1851 etc) and total
But the latter field will be static for a month which is likely why the report was never produced.
Do we need it? or only when we change update process for CEN?

It's not working because I was looking on test16, not www16!   So closing.

Reopened as this was issue on site statistics

Have activated site and search statistics on test3

Tested on test3 and working fine, thank you.

It is worth adding that statistics are now in the footer


picom: 9 -> 9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/yshui/picom/releases.
meta.description for picom is: "A fork of XCompMgr, a sample compositing manager for X servers"
meta.homepage for picom is: "https://github.com/yshui/picom"
meta.changelog for picom is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1/bin/picom had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1/bin/.picom-trans-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1/bin/picom-trans had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1/bin/compton had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1/bin/compton-trans had a zero exit code or showed the expected version
0 of 5 passed binary check by having a zero exit code.
0 of 5 passed binary check by having the new version present in output.
found 9.1 with grep in /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1
found 9.1 in filename of file in /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
picom

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A picom https://github.com/r-ryantm/nixpkgs/archive/fdb4267874d29a44ab9b781730c0cbf4a793d674.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1
ls -la /nix/store/26zq2jy09r5v676kmij9pras9j47m2zv-picom-9.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

picom

Maintainer pings
cc @ertes @Twey @thiagokokada for testing.

@lourkeur do you know if we should keep picom-unstable?
I guess we can see if picom keeps it's pace with frequent releases after changes and after a couple more releases maybe we drop it?

Yeah, this was my idea when we introduced picom-unstable. Once picom releases were being done more frequently we could simply alias picom-unstable = picom.

Y'all mean picom-next right? The best answer I can give is that I use picom and I did not know we had that.

Y'all mean picom-next right? The best answer I can give is that I use picom and I did not know we had that.

Yeah, picom-next actually. Sorry.
I am on my phone so I can't exactly check the source code of nixpkgs right now.


Error: Execution of '/usr/sbin/update-rc.d gitlab-runsvdir defaults' returned 1: update-rc.d: error: unable to read /etc/init.d/gitlab-runsvdir

Hi,
On Debian Wheezy (7) after installing the error on each puppet run:
Error: Execution of '/usr/sbin/update-rc.d gitlab-runsvdir defaults' returned 1: update-rc.d: error: unable to read /etc/init.d/gitlab-runsvdir
I have tried purging the package and running from scratch with the same result.  The file /etc/init.d/gitlab-runsvdir does not exist.
Hiera data:
gitlab::external_url: 'http://gitlab.XXXX'
gitlab::gitlab_rails:
time_zone: 'UTC'
gitlab_email_enabled: false
gitlab_default_theme: 4
gitlab_email_display_name: 'Gitlab'
gitlab_email_from: 'github@XXXX'
gitlab::sidekiq:
shutdown_timeout: 5
Class call:
class { '::gitlab':
external_url => 'http://gitlab.XXXX',
}
Please let me know if you need any more info.
Thanks

FYI, my solution was to switch to Debian Jessie instead of Wheezy


Migrate grasplan documentation?

Currently lives under:
https://github.com/aprilprojecteu/grasplan_documentation
Should we migrate it to:
https://github.com/DFKI-NI/grasplan_documentation
just like we did with grasplan repo.

+1


How to preprocess datasets？

❓ Questions & Help
I'm sorry to bother you, but I'm having some problems.
I wonder how OpenSpeech preprocesses the dataset. I see preprocess, but I don't see start up. I wonder how I should use it to get Manifest.
I sent an email, but I didn't get a reply.
Details

I have responded to all emails, which dataset do you want to use?

I need manifest of KsponSpeech ,If possible, please send to<EMAIL_ADDRESS>

I have responded to all emails, which dataset do you want to use?
I can train it myself manifes？I can't find the code for this part，Can you tell me about it? thank you

I wanted to run lit_data_module.py to get the manifest, but
/home/iip/anaconda3/envs/openspeech/bin/python3.7 /home/iip/wb/openspeech/openspeech/datasets/ksponspeech/lit_data_module.py
Traceback (most recent call last):
File "/home/iip/wangbo/openspeech/openspeech/datasets/ksponspeech/lit_data_module.py", line 41, in
class LightningKsponSpeechDataModule(pl.LightningDataModule):
File "/home/iip/wangbo/openspeech/openspeech/datasets/init.py", line 46, in register_data_module_cls
raise ValueError(f"Cannot register duplicate data module ({name})")
ValueError: Cannot register duplicate data module (ksponspeech)
Process finished with exit code 1

When you run hydra_train.py, a manifest file is created in the path you specified. [LINK]
And KsponSpeech needs permission from AI Hub. So please send e-mail including the approved screenshot to<EMAIL_ADDRESS> [LINK]
This is the code that preprocesses the data to generate a manifest file.
I recommend that you read the README.md carefully.
Thanks.

When you run hydra_train.py, a manifest file is created in the path you specified. [LINK] And KsponSpeech needs permission from AI Hub. So please send e-mail including the approved screenshot to<EMAIL_ADDRESS>[LINK] This is the code that preprocesses the data to generate a manifest file.
I recommend that you read the README.md carefully. Thanks.
Ok, thank you

I also got stuck on this poin.t I ended up creating the manifest file :D Maybe removing this option dataset.manifest_file_path in cli script and creating manifest in dataset.dataset_path might be a way to go.


kitty always crashes hyprland roughly 3 seconds after running kitty, other apps function similarly

Regression?
Yes
System Info and Version
inxi output while in plasma kde
System:
2	  Host: loganpc Kernel: 6.6.45-1-lts arch: x86_64 bits: 64
3	  Desktop: KDE Plasma v: 6.1.4 Distro: EndeavourOS
4	Machine:
5	  Type: Desktop System: Gigabyte product: B450M DS3H v: N/A
6	    serial:
7	  Mobo: Gigabyte model: B450M DS3H-CF serial:
8	    BIOS: American Megatrends LLC. v: F66 date: 03/22/2024
9	CPU:
10	  Info: 6-core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP cache: L2: 3 MiB
11	  Speed (MHz): avg: 2430 min/max: 1550/3400 cores: 1: 2686 2: 1334 3: 3400
12	    4: 2859 5: 2363 6: 3609 7: 1550 8: 1550 9: 3400 10: 3400 11: 1463 12: 1550
13	Graphics:
14	  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
15	    driver: amdgpu v: kernel
16	  Display: wayland server: X.org v: <IP_ADDRESS> with: Xwayland v: 24.1.2
17	    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
18	    dri: radeonsi gpu: amdgpu resolution: 3072x1728
19	  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
20	    platforms: gbm,wayland,x11,surfaceless,device
21	  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.5-arch1.2
22	    renderer: AMD Radeon RX 580 Series (radeonsi polaris10 LLVM 18.1.8 DRM 3.54
23	    6.6.45-1-lts)
24	  API: Vulkan Message: No Vulkan data available.
25	Audio:
26	  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
27	    driver: snd_hda_intel
28	  Device-2: AMD Family 17h HD Audio driver: snd_hda_intel
29	  API: ALSA v: k6.6.45-1-lts status: kernel-api
30	  Server-1: PulseAudio v: 17.0 status: active
31	Network:
32	  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
33	    driver: r8169
34	  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: b4:2e:99:30:20:32
35	Drives:
36	  Local Storage: total: 465.76 GiB used: 153.9 GiB (33.0%)
37	  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
38	    size: 465.76 GiB
39	Partition:
40	  ID-1: / size: 457.38 GiB used: 153.9 GiB (33.6%) fs: ext4
41	    dev: /dev/nvme0n1p1
42	Swap:
43	  Alert: No swap data was found.
44	Sensors:
45	  System Temperatures: cpu: 34.9 C mobo: 26.0 C gpu: amdgpu temp: 30.0 C
46	  Fan Speeds (rpm): N/A
47	Info:
48	  Memory: total: 16 GiB available: 15.54 GiB used: 1.79 GiB (11.5%)
49	  Processes: 351 Uptime: 1m Shell: Bash inxi: 3.3.35
Description
kitty always crashes hyprland roughly 3 seconds after running kitty, other apps function similarly such as vesktop but apps like brave and dolphin work fine, foot terminal works fine.
i am a linux and hyprland noob be gentle haha
How to reproduce
i dont know how others would reproduce this issue, it seems to be a rare problem that nobody has had a solution to yet.
Crash reports, logs, images, videos
hyprlandCrashReport3354.txt

can you try updating aquamarine? this seems like an aq bug tbh

can you try updating aquamarine? this seems like an aq bug tbh

i have tried both the -git package and the package without the -git and neither have changed anything
i dont know what all ive tried at this point but i have tried a lot of different things a few others from discord have been trying to help but havent gotten anywhere.

woops lol didnt mean to click that

can you get a debug stacktrace https://wiki.hyprland.org/Crashes-and-Bugs/#obtaining-a-debug-stacktrace after building aquamarine-git in debug too

can you get a debug stacktrace https://wiki.hyprland.org/Crashes-and-Bugs/#obtaining-a-debug-stacktrace after building aquamarine-git in debug too, i think this is with using aquamarine not aquamarine-git

can you get a debug stacktrace https://wiki.hyprland.org/Crashes-and-Bugs/#obtaining-a-debug-stacktrace after building aquamarine-git in debug too
this should be with aquamarine-git and the previous ones should be just regular aquamarine

@vaxerski dont know if i should ping or not but just wanted to know if you had any ideas about whats going on with this one?

ok so that should be fixed in latest aquamarine, but I am unsure why the wayland backend is running if you are on a drm session. Anyways, try latest git

ok so that should be fixed in latest aquamarine, but I am unsure why the wayland backend is running if you are on a drm session. Anyways, try latest git

alright so i checked it and i already was using aquamarine 0.3.3 which is the newest version im seeing on the github repo, it doesnt seem to be working.

ok so that should be fixed in latest aquamarine, but I am unsure why the wayland backend is running if you are on a drm session. Anyways, try latest git

alright so i checked it and i already was using aquamarine 0.3.3 which is the newest version im seeing on the github repo, it doesnt seem to have fixed the problem.

https://github.com/hyprwm/aquamarine/commit/3989aa9b2fed9638dd2c160f0a88d2c184f77330 yeah not 3.3 but -git

ok so that should be fixed in latest aquamarine, but I am unsure why the wayland backend is running if you are on a drm session. Anyways, try latest git

alright so i checked it and i already was using aquamarine 0.3.3 which is the newest version im seeing on the github repo, it doesnt seem to have fixed the problem.

hyprwm/aquamarine@3989aa9 yeah not 3.3 but -git

ohhh i totally wasnt getting it at first, ok after some playing around i got the newest version of aquamarine going and now it works thanks for the help yall! time to play around with hyprland.


fix Sidekiq::Logger::Formatters::Base#ctx

The return value of ctx should not be Context, but Hash[String, untyped], which is the return value of Context.current.
see: https://github.com/sidekiq/sidekiq/blob/630d22fce8821aaab96ba9de6cd0440512af42c7/lib/sidekiq/logger.rb#L85

/merge


How do I install the agent on VMWare ESXi?

The readme suggests that VMWare is supported but does not show the steps to install. I have tried to look up some documentation on the net but did not find anything useful.

Hi @abhi1693
You want to install netbox-agent on your VMWare guest virtual machine, not on the hypervisor 😉


feat: add a way to disable metrics server

Metrics server is already installed on my cluster.
This PR allow me to disable its installation via the betterstack logs chart

~working as intended with this update and these values :
metrics-server:
  enabled: false
vector:
  customConfig:
    sinks:
      better_stack_http_sink:
        auth:
          token: redacted
      better_stack_http_metrics_sink:
        auth:
          token: redacted

    sources:
      better_stack_kubernetes_metrics_nodes:
        endpoint: https://metrics-server.kube-system.svc.cluster.local/apis/metrics.k8s.io/v1beta1/nodes
        tls:
          verify_certificate: false
      better_stack_kubernetes_metrics_pods:
        endpoint: https://metrics-server.kube-system.svc.cluster.local/apis/metrics.k8s.io/v1beta1/pods
        tls:
          verify_certificate: false

@JanPokorny could you please merge this PR, this is essential, metrics-server should be optional. 🙏


Expanded tree opens up multi level context menu on the parent row

The child context menu overlaps the parent context menu after  tree is expanded. The desired behaviour is to hide the child context menu when right clicked on parent row. https://i.imgur.com/dxLaZKX.png
Steps to reproduce the problem.

Enable the tree view
Expand the parent row. right click and open the context menu
Collapse tree and return to parent row , right click and open the context menu

Version 0.22.12

Thanks for the report.  Looks like there needs to be some code that detects that the parent's context menu is open and closes it.  Or is it the case that both menus pop up when a single click is performed?

This problem still exists in the current version. You can use this fiddle to reproduce.
Before expanding any parent row, the context menu seems to work fine, but after expanding a row, two menus pop up on a single click of a row in the parent grid.


Additional PySide2 caveats

Found some more cross-development tips here:

https://github.com/PySide/pyside2/wiki/My_Practice_:_Porting_python_scripts_to_PySide2

Pasting them here in case they disappear. Will need formatting.
QHBoxLayout QVBoxLayout
Background:
Qt4 (PySide):  QLayout::setAlignment(Qt::Alignment alignment)
http://doc.qt.io/qt-4.8/qlayout.html#setAlignment-2
Qt5 (PySide2): removed the above method
http://doc.qt.io/qt-5/qlayout.html#setAlignment
To upgrade to PySIde2, we have to make the following changes for
QHBoxLayout::setAlignment(Qt::Alignment alignment)
QVBoxLayout::setAlignment(Qt::Alignment alignment)
Qt4 (PySide):
layout = QHBoxLayout()
layout.setAlignment(Qt.AlignLeft)

Qt5(PySide2) : --solution
layout = QHBoxLayout()
QLayoutItem.setAlignment(layout, Qt.AlignLeft)

QHeaderView
Qt4 (PySide): http://doc.qt.io/qt-4.8/qheaderview.html
void    setResizeMode(ResizeMode mode);
void    setResizeMode(int logicalIndex, ResizeMode mode);

Qt5(PySide2) : http://doc.qt.io/qt-5/qheaderview.html
void    setSectionResizeMode(ResizeMode mode);
void    setSectionResizeMode(int logicalIndex, ResizeMode mode);

Solution:
pysideVersion = '-1'
try:
    import PySide
    pysideVersion = PySide.__version__
except ImportError:
    import PySide2
    pysideVersion = PySide2.__version__
if pysideVersion == '1.2.0':
    treeUI.header().setResizeMode(QHeaderView.Fixed)
    treeUI.header().setResizeMode(TREE_COLUMN_NAME, QHeaderView.Interactive)
    treeUI.header().setResizeMode(TREE_COLUMN_WEIGHT, QHeaderView.Stretch)
else:
    treeUI.header().setSectionResizeMode(QHeaderView.Fixed)
    treeUI.header().setSectionResizeMode(TREE_COLUMN_NAME, QHeaderView.Interactive)
    treeUI.header().setSectionResizeMode(TREE_COLUMN_WEIGHT, QHeaderView.Stretch)

QApplication.palette()
Background:
Qt4:
QPalette QApplication::palette()
http://doc.qt.io/qt-4.8/qapplication.html#palette
Qt5:
QPalette QGuiApplication::palette()
http://doc.qt.io/qt-5/qguiapplication.html#palette
Solution:
PySide(Qt4): palette = QApplication.palette()
PySide2 (Qt5): palette = QGuiApplication.palette()
Another workaround:
palette = self.palette()  # self is widget
# as you could also find palette() within QWidget class http://doc.qt.io/qt-5/qwidget.html
# it works for both Qt4 and Qt5.

Might be worth adding a link to the official wiki on the subject, to ackowledge that we've taken it into account. Should we duplicate the contents here a well? For competeness, and to protect against broken links?

https://wiki.qt.io/Differences_Between_PySide_and_PyQt

It also mentions two more projects that overlaps with what Qt.py does.

https://github.com/epage/PythonUtils/blob/master/util/qt_compat.py
https://github.com/ros-visualization/python_qt_binding

Might be worth adding a link to the official wiki on the subject

👍

Should we duplicate the contents here a well?

I'm all for completeness. I've come along too many broken links in my day...

Just a quick question on QGuiApplications.palette()... I didn't have to do this here. That code works in PySide/PyQt4 and PySide2/PyQt5.
Does that mean that PySide2 and PyQt5 are backwards compatible for palette()?

Hm, I'm not sure what that's about. I'd expect QApplication to work fine as well. Pinging the author, @zhihaoadsk. Would it be possible to shed some light on this?
What this also tells me is that we need tests for these. Something to confirm they actually are a problem.

QCoreApplication is the base class
QGuiApplication extends the base class with functionality related to handling windows and GUI stuff (non-widget related, e.g. OpenGL or QtQuick)
QApplication extends QGuiApplication with functionality related to handling widgets

Source here.
Since QApplication.palette() exists and works in both Qt4 and Qt5, I don't see any need to create a remap or similar here. For QGuiApplication, which only exists in Qt5, I guess the user must take this into consideration and do something alltogether different for Qt4 or not use this for Qt4.

Time to get this baby off the floor and into the oven as well. CAVEATS.md style!

Thanks fredrikaverpil!
Glad that it works now. skip the item please:)
Background: back then(Qt5.5) it doesn't work when I wrote the wiki. Probably Qt5.6 updated something.

HI Marcus, thanks for this.
I'm now hitting the issue with HeaderView, and wondering....
isn't there a way to provide (read wrap)  either setResizeMode to setSectionResizeMode or the other way round ?
having to fill up already pretty complex code with try/except if/else is something I would be happily avoiding :)
Thanks!

Hey @hdd, yes, definitely. This is an interesting area of research and development. The way I've pictured it is by offering subclasses via QtWidgets and such that act as their real counterparts, but implement the missing /remapped functionality. But I'm open to alternatives. The end goal should be what you expect.
It should be enough to handle a majority of compatibility issues and also work with non-Qt.py bindings as well.
Pull-requests are welcome!

This will also require a push into expanding tests to cover Qt 5 bindings as well, because at the moment they only cover PyQt4 and PySide differences.
I had an idea for how to achive this via Docker that I think will work well, both for testing via Travis and locally, without having to install every binding on a single OS.
I'll type up an issue about it.

Happy to help on this.
let me know which is the issue number so I can create a pull request against master.
I like the idea of providing both implementations, the only addition I would make is to provide notice to the users (warnings, so they can disabled) that the call they are making is for another version (if it's the case).

started looking into this https://github.com/EfestoLab/Qt.py/tree/bridge-header-resize-calls
started with a naive approach, let see whether is enough.


pReturnValue parameter documentation needs additional clarity

wcstombs_s documentation for parameter pReturnValue is unclear. In the Parameters section, it is stated to be "The number of characters converted" where as later in the Remarks section it states "it puts the size in bytes of the converted string, including the null terminator, into *pReturnValue". Given there may be multi-byte characters, and a null terminator, the first definition of the parameter is lacking.

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

ID: 79027810-d629-5a02-4e23-58164db42d1e
Version Independent ID: fb2f489f-343d-9967-7965-fbea40443d53
Content: wcstombs_s, _wcstombs_s_l
Content Source: docs/c-runtime-library/reference/wcstombs-s-wcstombs-s-l.md
Product: visual-cpp
GitHub Login: @corob-msft
Microsoft Alias: corob

@jeffwick-msft You're right, the short description in the Parameters section could use more clarity. The Remarks section describes the actual behavior. Would you like to submit a fix? We've got a handy contributor's guide that describes the not-too-complicated process.

Fixed courtesy of @MSDN-WhiteKnight, this should appear by the next scheduled publication date (next Monday by noon Pacific time).


When a subtitle file is loaded and subtitle display is toggled off, a notification should be displayed saying: "Use  to toggle subtitles on"

Users often hit the default keybind 'down' without knowing that it toggles the subtitles on and off. This change would introduce a point in the UX to let users know that this is the case.

Hii @killergerbah can I look into it ?


fix(release): use latest annotated tag only

When building the images, there may be the case where 2 tags point at HEAD. In this case, use the latest annotated tag only.
Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

bors merge

bors merge


Melodic migration (tf2)

Hello,
Has there been any work done to convert this package to tf2? I would really like to use this package on melodic.

Hi Ramon,
I'm afraid that the metapackage is not updated to use tf2. It was developed
under the European project TERESA and It has not been employed since then.
Probably you can use some of the packages contained in it independently,
and try to convert to tf2 the interesting ones by yourself.
Sorry.
Best regards,
Noé Pérez
El mar., 21 may. 2019 a las 11:15, Ramon Wijnands<EMAIL_ADDRESS>escribió:

Hello,
Has there been any work done to convert this package to tf2? I would
really like to use this package on melodic.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/robotics-upo/upo_robot_navigation/issues/3?email_source=notifications&email_token=ADUK36D2PETMNOX4OFRC2OLPWO4S3A5CNFSM4HOI65Z2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GU5ER5A,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADUK36B67CQ63PSJI4TERBTPWO4S3ANCNFSM4HOI65ZQ
.

--
NOE PEREZ HIGUERAS
Postdoctoral Researcher - RoboticsLab
Dept. Ingenieria de Sist. y Automatica
Universidad Carlos III de Madrid
c/ Butarque, 15 28911 Leganes, Madrid
España - SPAIN

OK, thank you for your quick reply


uPnP discovery also requests UDP ports

I looked at my router's uPnP entries and found entries for both TCP:9981-9984 and UDP:9981-9984. AFAIK, siad should only be requesting TCP ports and not UDP ports.

The go-upnp package always forwards both TCP and UDP to make things easier for the client. Granted, we wrote that package many years ago; I'm not sure I would make that same design decision today. If you feel strongly about it, I'm not opposed to adding ForwardTCP and ForwardUDP methods to go-upnp. But to be clear, the behavior you're observing is normal.

I don't feel that strongly. It just feels incorrect that it is grabbing ports it does not need. It is the only app I've seen doing this. Anyway, more important to me while I have a block of IPs, is #42. I would possibly class this as a low priority bug.

I have just seen on Discord #Announcements the problem with the DDOS attack last summer and your recommendation to Block UDP traffic on port 9981-9983. Sia only uses TCP., but it is Sia itself which is opening the ports if you are behind a uPnP enabled router. Perhaps this issue should have its priority raised?

Hmm, fair. IIRC it was often the routers themselves that were being overwhelmed, so hard to say if not forwarding UDP to siad would have made a big difference. But it certainly couldn't have hurt. I'll go ahead and implement this.


Add custom header level icons

Description
Adds custom icons for header levels so that we don't have to rely on plain written text to demonstrate to a user what level header they have selected and the pilcrow icon for paragraph tag.
Issue #465
What is the purpose of this pull request?

[X] New feature
[ ] Documentation update
[ ] Bug fix
[ ] Refactor
[ ] Release
[ ] Other

#465

This is a very good solution for the light mode adaptations
https://github.com/onlook-dev/onlook/pull/534

This is a very good solution for the light mode adaptations #534

we should not face such problems because of light mode. we already have required tokens which works in dark & light.
we can put all icons/logos/svg in one place ex: components/icons.tsx.
usage: <Icons.Logo className="w-24 fill-foreground" />

Merged main for light mode testing

@abhiroopc84
The icons aren't showing up in light mode –

Perhaps if you try @hitaspdotnet 's recommendation it will solve it and then we can close it out 👍

@drfarrell I've fixed the coloring for active state. Could you review the changes?


Fix for Reactive Example, update packages

Fixes

Fixes Reactive Example

Proposed Changes/Todos

[x] Fix Reactive Example
[x] Updated ReactiveUI packages

Pull Request checklist:

[ ] I've named my PR in the form of "Fixes #issue. Terse description."
[x] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
[x] My code follows the Terminal.Gui library design guidelines
[x] I ran dotnet test before commit
[ ] I have made corresponding changes to the API documentation (using /// style comments)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any poor grammar or misspellings
[x] I conducted basic QA to assure all features are working

Not quite sure what is happening here, I was surprised to see all the other commits attached to this PR.

It seems you used the v2_develop branch but created your PR into the develop branch. If you really want to create your PR based on the v2_develop you have to close this PR and create another PR with your changes by selecting the v2_develop branch and not the default develop branch.


Release not deleted if no assets attached

Hi,
the action don't delete releases which don't have assets 'attached'. I'm missing a configuration or the action is deleting releases with assets.
Thank you for the feedback!

It's likely the delete tag pattern did not match or that you have a tag with no associated releases, which in that case the delete_tag parameter can force a delete for them.
Take a look at the logs which will detail if matches were found to delete or not with your provided parameters.  The logs often give clues as to what is happening or why tags are not matching.


k8s: netpol support namespace <--> namespace(s) policy

You can test the new code using:
kubectl create -f tests/k8s/networkpolicy-ingress-allow-namespace.yaml

run skydive-unit-tests

run skydive-unit-tests

@lebauce can you check why skydive-scale-tests is failing?, thanks ...

run skydive-scale-tests

@hunchback Just retriggered the job

tx!
On Tue, Aug 28, 2018, 11:27 Sylvain Baubeau<EMAIL_ADDRESS>wrote:

@hunchback https://github.com/hunchback Just retriggered the job
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/skydive-project/skydive/pull/1255#issuecomment-416496365,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACogI_mFysq6O3fWdD2WF7nqYMIR1Ppmks5uVP7pgaJpZM4WFgAv
.


[SPARK-11896] [SQL] Support Sample in Dataset APIs

Both RDD and DataFrame APIs have these two Sample APIs. Thus, I think they could be useful in DataSet APIs. Also added two test cases.

Test build #46463 has started for PR 9877 at commit 87b5742.

Test build #46463 has finished for PR 9877 at commit 87b5742.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46463/
Test PASSed.

Test build #46495 has started for PR 9877 at commit 7430e61.

Test build #46495 has finished for PR 9877 at commit 7430e61.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46495/
Test PASSed.

close this one and will merge it to https://github.com/apache/spark/pull/9921
Thank you!


External speaker links

Guten Tag 👋 back at it with a PR to tackle #259. I've marked this as a draft to get some feedback, so fire away!
The link to the speaker (under the buttons) 'works', but if some wordforms have a long list of speakers, I think it might be better to have it on the right hand side of the page.
But anyway. Have at it – if we need to go at it together, that's good too!

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@df3d213). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #441   +/-   ##
=========================================
  Coverage          ?   85.98%
=========================================
  Files             ?       71
  Lines             ?     2598
  Branches          ?        0
=========================================
  Hits              ?     2234
  Misses            ?      364
  Partials          ?        0

Impacted Files
Coverage Δ

CreeDictionary/API/views.py
66.66% <0.00%> (ø)

...ctionary/tests/utils_tests/test_layout_combiner.py
100.00% <0.00%> (ø)

CreeDictionary/CreeDictionary/utils.py
100.00% <0.00%> (ø)

CreeDictionary/utils/shared_res_dir.py
100.00% <0.00%> (ø)

...baseManager_tests/test_xml_importer_regressions.py
100.00% <0.00%> (ø)

CreeDictionary/DatabaseManager/xml_importer.py
93.36% <0.00%> (ø)

CreeDictionary/shared/__init__.py
100.00% <0.00%> (ø)

CreeDictionary/API/admin.py
46.15% <0.00%> (ø)

CreeDictionary/tests/conftest.py
71.87% <0.00%> (ø)

CreeDictionary/CreeDictionary/forms.py
100.00% <0.00%> (ø)

... and 61 more

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 df3d213...50217c1. Read the comment docs.


request to ignore empty qualifiers

Reported by andrew wittenberg on 22 Jan 2016 21:22 UTC
There seems to have been a change in v6.97 whereby leading slashes (/) are no longer dropped from the beginning of unquoted strings.
This is a welcome change, but it's breaking some of my existing scripts which had assumed the prior behavior of chomping that leading slash.  As an example, the old behavior was:
 	NOAA/PMEL TMAP
 	FERRET v6.961 (beta)
 	Linux 2.6.32-573.8.1.el6.x86_64 64-bit - 12/09/15
 	22-Jan-16 16:09

yes? def sym qual /x=1:2; set reg/($qual)
 !-> set reg/x=1:2

While the new behavior is:
	NOAA/PMEL TMAP
 	FERRET v6.97 (PyFerret 1.3)
 	Linux 2.6.32-573.1.1.el6.x86_64 - 01/21/16
 	22-Jan-16 16:09

yes? def sym qual /x=1:2; set reg/($qual)
 **ERROR: command syntax: "/"
set reg//x=1:2

As a fix for such legacy scripts (and to get us through the transition where some folks may be running the old vs. the new version of Ferret), I'd suggest a parsing enhancement in which any "empty" qualifiers to any command are simply ignored.  So the following would all be equivalent:
set reg/x=1:2
set reg//x=1:2
set reg//x=1:2////

The analogy would be to operating systems like Linux, in which extra adjacent slashes in pathnames are ignored.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2356

Modified by andrew.wittenberg on 22 Jan 2016 21:22 UTC

Comment by ansley.b.manke on 22 Jan 2016 22:25 UTC
I'm pretty sure this comes is a change that removes the need for quotes around arguments.  This looks like some of the "dust settling" that's to be expected with the resolution to #2342.
I think what you're suggesting for qualifiers sounds reasonable.

Comment by ansley.b.manke on 4 Mar 2016 23:03 UTC
This is done in parse_command.F and tested in bench/err696_multiple_slashes.jnl

Comment by andrew.wittenberg on 7 Mar 2016 18:22 UTC
A little loose end: Ferret still complains when there's more than one trailing slash:
 	NOAA/PMEL TMAP
 	FERRET v6.97 (beta/opt)
 	Linux 2.6.32-573.18.1.el6.x86_64 64-bit - 03/04/16
 	 7-Mar-16 13:21

yes? set reg/x=1:2
yes? set reg/x=1:2/
yes? set reg/x=1:2//
 **ERROR: command syntax: "/"

Comment by ansley.b.manke on 8 Mar 2016 17:46 UTC
This is fixed, extra slash at the end of a command,

yes? set reg/x=1:2
yes? set reg/x=1:2/
yes? set reg/x=1:2//
yes? set reg/x=1:2/ /

yes?  repeat/k=1:2 (set reg/x=1:2//)
!-> REPEAT: K=1
!-> REPEAT: K=2

yes?  repeat/k=1:2 (set reg/x=1:2/ /)
!-> REPEAT: K=1
!-> REPEAT: K=2