1.6.0-beta2 to 1.6.0-rc03 causes sync failure

After upgrading Compose Multiplatform from beta2 to rc03 and attempting a sync, the sync works. but during post-sync processing this error occurs:
removeContentEntry: removed content entry url 'file://D:/WorkingShared/Monay2/uiCommon/src/commonMain/composeResources' still exists after removing

There is no call stack or other console messaging.
Environment:
Windows 11 64 bit on AMD
Android Studio Jellyfish Canary 10
Gradle 8.6
Kotlin 1,9,22
In this project, uiCommon is the module name for the Compose Multiplatform code. The new compose resources support is used only for a few PNG icons in the drawable subdirectory.  The directory in the error messages contains the standard drawables subdirectory along with others.
This error causes the sync to fail even though the gradle build portion of the sync succeeds. The error indicates an attempt to delete a directory that to me should NOT BE deleted as it contains the source for the drawables in use during the build.
Switching back to beta02 causes the sync to succeed without error. RC01,  RC02 and RC03 all get the error, so bug starts with rc01.

Could you attach a project where you reproduce the issue?

The project this is happening on is large, has non-public dependencies and is not on Github, so would not be workable for either of us. I will try out a smaller project on rc03, if it happens there I can post that on Github even though that project is a very early work-in-progress.

I'm wondering if this has something to do with a Duplicate content roots detected warning I get on this project at end of sync. Here is a snippet from the last fail (using rc03) from idea.log. I added blank lines around the suspect stuff:
2024-02-23 15:52:09,407 [20933606]   INFO - #o.j.p.g.s.e.GradleExecutionHelper - Passing command-line to Gradle Tooling API: --init-script D:\Temp\ijMapper1.gradle -Didea.gradle.download.sources=true -Didea.sync.active=true -Didea.resolveSourceSetDependencies=true -Porg.gradle.kotlin.dsl.provider.cid=832530945911400 --init-script D:\Temp\sync.studio.tooling3.gradle -Djava.awt.headless=true --continue --stacktrace -Pandroid.injected.build.model.only=true -Pandroid.injected.build.model.only.advanced=true -Pandroid.injected.invoked.from.ide=true -Pandroid.injected.build.model.only.versioned=3 -Pandroid.studio.version=233.14475.28.2331.11456607 -Pandroid.injected.build.model.disable.src.download=true -Pidea.gradle.do.not.build.tasks=false -Pandroid.injected.avoid.task.registration=false -Dorg.gradle.internal.GradleProjectBuilderOptions=omit_all_tasks -Pkotlin.mpp.enableIntransitiveMetadataConfiguration=true --init-script D:\Temp\ijInit1.gradle -Didea.active=true -Didea.version=2023.3 -Didea.vendor.name=Google
2024-02-23 15:52:52,065 [20976264]   WARN - #c.i.o.p.i.j.JdkAuto - Multiple SdkType candidates [JavaSDK, Android SDK]. Proceeding with a first candidate: JavaSDK
2024-02-23 15:52:52,066 [20976265]   INFO - #c.i.o.p.i.j.JdkAuto - Looking for a local SDK for JDK with name SdkLookup{JDK, name=17}
2024-02-23 15:52:52,673 [20976872]   INFO - #com.android.tools.idea.gradle.project.sync.GradleSyncStateHolder$SyncStateUpdater - onSuccess(RESOLVE_PROJECT:9)
2024-02-23 15:52:52,673 [20976872]   INFO - #com.android.tools.idea.gradle.project.sync.GradleSyncStateHolder - Started setup of project 'Monay2'.
2024-02-23 15:52:52,678 [20976877]   INFO - #o.j.k.i.g.s.r.GradleBuildRootIndex - D:/WorkingShared/Monay2: org.jetbrains.kotlin.idea.gradleJava.scripting.roots.Imported@3c6768fa -> org.jetbrains.kotlin.idea.gradleJava.scripting.roots.Imported@c689906
2024-02-23 15:52:52,688 [20976887]   INFO - #c.i.o.e.u.ExternalSystemUtil - External project [D:/WorkingShared/Monay2] resolution task executed in 43397 ms.
2024-02-23 15:52:52,698 [20976897]   INFO - #c.i.o.e.s.p.IdeModifiableModelsProviderImpl - Ide modifiable models provider, create builder from version 72
2024-02-23 15:52:52,722 [20976921]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: com.ionspin.kotlin:bignum-jvm:0.3.9'
2024-02-23 15:52:52,722 [20976921]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.jetbrains.kotlinx:kotlinx-serialization-core-jvm:1.6.3'
2024-02-23 15:52:52,722 [20976921]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.jetbrains.kotlinx:kotlinx-serialization-json-jvm:1.6.3'
2024-02-23 15:52:52,722 [20976921]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.jetbrains.kotlin:kotlin-stdlib:1.9.22'
2024-02-23 15:52:52,722 [20976921]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.jetbrains.kotlinx:atomicfu-jvm:0.23.2'
2024-02-23 15:52:52,722 [20976921]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm:1.8.0'
2024-02-23 15:52:52,722 [20976921]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.jetbrains.kotlinx:kotlinx-coroutines-test-jvm:1.8.0'
2024-02-23 15:52:52,722 [20976921]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.junit.platform:junit-platform-engine:1.10.2'
2024-02-23 15:52:52,723 [20976922]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.junit.platform:junit-platform-commons:1.10.2'
2024-02-23 15:52:52,723 [20976922]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.junit.jupiter:junit-jupiter-engine:5.10.2'
2024-02-23 15:52:52,723 [20976922]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.junit.jupiter:junit-jupiter-api:5.10.2'
2024-02-23 15:52:52,723 [20976922]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.jetbrains:annotations:23.0.0'
2024-02-23 15:52:52,723 [20976922]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.opentest4j:opentest4j:1.3.0'
2024-02-23 15:52:52,723 [20976922]   WARN - #c.i.o.e.s.p.m.LibraryDataService - Multiple project level libraries found with the same name 'Gradle: org.apiguardian:apiguardian-api:1.1.2'

**2024-02-23 15:52:52,821 [20977020]   WARN - #c.i.o.e.s.p.m.ContentRootDataService - Duplicating content roots detected.**
2024-02-23 15:52:52,821 [20977020]   WARN - #c.i.o.e.s.p.m.ContentRootDataService - Path [D:/WorkingShared/Monay2/monayCommon/src/commonMain/resources] of module [Monay2.androidApp.main] was removed from modules [Monay2.monayCommon.commonMain]
2024-02-23 15:52:52,821 [20977020]   WARN - #c.i.o.e.s.p.m.ContentRootDataService - Path [D:/WorkingShared/Monay2/androidApp/src/main/res] of module [Monay2.androidApp.main] was removed from modules [Monay2.androidApp.androidTest]
2024-02-23 15:52:52,821 [20977020]   WARN - #c.i.o.e.s.p.m.ContentRootDataService - Path [D:/WorkingShared/Monay2/uiCommon/src/commonTest/composeResources] of module [Monay2.uiCommon.commonTest] was removed from modules [Monay2.uiCommon.unitTest]
2024-02-23 15:52:52,821 [20977020]   WARN - #c.i.o.e.s.p.m.ContentRootDataService - Path [D:/WorkingShared/Monay2/uiCommon/build/generated/compose/resourceGenerator/commonAndroidComposeResources] of module [Monay2.uiCommon.main] was removed from modules [Monay2.uiCommon.unitTest, Monay2.uiCommon.androidTest]

2024-02-23 15:52:52,881 [20977080]   INFO - #com.android.tools.idea.gradle.project.sync.GradleSyncStateHolder$DataImportListener - onImportFailed(D:/WorkingShared/Monay2)
2024-02-23 15:52:52,882 [20977081]   INFO - #com.android.tools.idea.gradle.project.sync.GradleSyncStateHolder$SyncStateUpdaterService - stopTrackingTask(D:/WorkingShared/Monay2)
2024-02-23 15:52:52,882 [20977081]   INFO - #com.android.tools.idea.gradle.project.sync.GradleSyncStateHolder$SyncStateUpdaterService - stopTrackingTask(RESOLVE_PROJECT:9)
2024-02-23 15:52:52,882 [20977081]   WARN - #com.android.tools.idea.gradle.project.sync.GradleSyncStateHolder - Gradle sync failed in 43 s 587 ms. Failed to import project structure
2024-02-23 15:52:52,912 [20977111]   INFO - #c.i.o.p.DumbServiceImpl - enter dumb mode [Monay2]
2024-02-23 15:52:52,918 [20977117]   INFO - #com.google.services.firebase.insights.config.FirebaseAppManager - New app states: {Module: 'Monay2.androidApp'=FirebaseApp(connections=[CrashlyticsVariantConnection(connection=CrashlyticsConnection(appId=PLACEHOLDER, mobileSdkAppId=, projectId=, projectNumber=), variantData=VariantData(module=Module: 'Monay2.androidApp', variantName=All), isConfigured=false)])}.
2024-02-23 15:52:52,920 [20977119]   INFO - #c.i.o.p.MergingQueueGuiExecutor - Running task: (dumb mode task) com.android.tools.idea.res.AndroidProjectRootListener$MyDumbModeTask@48f133f9
2024-02-23 15:52:52,921 [20977120]   INFO - #c.i.o.p.MergingQueueGuiExecutor - Task finished: (dumb mode task) com.android.tools.idea.res.AndroidProjectRootListener$MyDumbModeTask@48f133f9
2024-02-23 15:52:52,928 [20977127]   INFO - #c.i.w.i.i.EntitiesOrphanageImpl - Update orphanage. 0 modules added
2024-02-23 15:52:52,968 [20977167]   INFO - #c.i.o.p.MergingQueueGuiExecutor - Running task: (dumb mode task) com.android.tools.idea.res.AndroidProjectRootListener$MyDumbModeTask@21792409
2024-02-23 15:52:52,969 [20977168]   INFO - #c.i.o.p.MergingQueueGuiExecutor - Task finished: (dumb mode task) com.android.tools.idea.res.AndroidProjectRootListener$MyDumbModeTask@21792409
2024-02-23 15:52:53,017 [20977216]   INFO - #c.i.o.p.MergingQueueGuiExecutor - Running task: (dumb mode task) com.intellij.util.indexing.UnindexedFilesScanner$2@7fe637a
2024-02-23 15:52:53,017 [20977216]   INFO - #c.i.o.p.MergingQueueGuiExecutor - Task finished: (dumb mode task) com.intellij.util.indexing.UnindexedFilesScanner$2@7fe637a
2024-02-23 15:52:53,017 [20977216]   INFO - #c.i.o.p.MergingQueueGuiExecutor - Running task: UnindexedFilesScanner[Monay2, 2 iterators]
2024-02-23 15:52:53,018 [20977217]   INFO - #c.i.u.i.UnindexedFilesScanner - Started scanning for indexing of Monay2. Reason: changes in: "External roots from entity (compose-gradle-plugin-1.6.0-rc03.jar; empty; empty; empty)", "External roots from entity (classes; empty; empty; empty)"
2024-02-23 15:52:53,018 [20977217]   INFO - #c.i.u.i.UnindexedFilesScanner - Performing delayed pushing properties tasks for Monay2 took 0ms; general responsiveness: ok; EDT responsiveness: ok
2024-02-23 15:52:53,018 [20977217]   INFO - #c.i.u.i.UnindexedFilesScanner - Scanning of Monay2 uses 47 scanning threads
2024-02-23 15:52:53,022 [20977221]   INFO - #c.i.o.p.DumbServiceImpl - exit dumb mode [Monay2]
2024-02-23 15:52:53,229 [20977428]   INFO - #c.i.u.i.UnindexedFilesScanner - Scanning completed for Monay2. Number of scanned files: 2315; number of files for indexing: 0 took 211ms; general responsiveness: ok; EDT responsiveness: ok
2024-02-23 15:52:53,229 [20977428]   INFO - #c.i.u.i.PerProjectIndexingQueue - Finished for Monay2. No files to index with loading content.
2024-02-23 15:52:53,230 [20977429]   INFO - #c.i.o.p.MergingQueueGuiExecutor - Task finished: UnindexedFilesScanner[Monay2, 2 iterators]

Ok, tried a different small project using Compose Multiplatform rc03 and the same environment as the big project, and sync there works fine but also does not display the Android Studio warning box bottom-right warning about Duplicate content roots. Unfortunately it does not use compose resources either. Don't know if this is useful info, but I guess bottom line is I still don't have a project I can send you that recreates the issue. I'm gonna try to look in the source of the compose gradle plugin and see if I can tell what specifically is causing this error. I can't use anything newer than beta02 on my large project until this is resolved.

Still looking, but wanted to post that I just got a successful sync by deleting .idea directory, invalidating cache and restarting Android Studio.  Saw similar errors mentioned in StackOverflow in other situations where invalidating cache fixed similar "removeContentEntry" errors, so tried it out and it worked. Don't know what's different between beta02 and rc0x that requires a cache invalidate.  Will continue to work with this to see if I can get more info.

I think this can be closed, I can no longer recreate the error since the cache invalidate.

TLDR: downgrade Android Studio from Koala to Jellyfish
I have the same problem in configuration compose-resources 1.6.11 and Android Studio Koala 2024.1.1.
With compose-resources 1.6.2 everything works fine, but after update version to 1.6.11 Android Studio got the error removeContentEntry: removed content entry url '.../src/commonMain/composeResources' still exists after removing.
Surprisingly, from terminal build works fine and correct ./gradlew assembleRelease.
So I decided to downgrade Android Studio to Jellyfish 2023.3.1 Patch 2 and it helps, compose-resources 1.6.11 now works fine.
So I guess the problem in Android Studio Koala 2024.1.1

@comm1x try this:

close your AndroidStudio
delete .idea directory
open the AndroidStudio
open the project from a scratch (don't use recents projects!)

confirming @terrakok's solution. I don't know why but it wasn't even related to compose multiplatform. My project is not using it.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Confused re new version

Write your question here
HI
I have just updated and read your well explained latest version, but i didn’t fully understand it sorry.

I had it running correctly but now i am getting a log error, but on the frontend, it still looks correct.
I don’t understand what i am supposed to do you mention 2 stages and 10 different blueprints seems more complicated than before :)
This error originated from a custom integration.
Logger: custom_components.garbage_collection
Source: custom_components/garbage_collection/init.py:324
Integration: Garbage Collection (documentation, issues)
First occurred: 16:48:34 (3 occurrences)
Last logged: 16:48:34
Removed data config {'offset': 21, 'holiday_in_week_move': False, 'holiday_move_offset': 1, 'observed': True, 'include_dates': ['2022-03-07']}. Please check the documentation how to configure the functionality.
Removed data config {'offset': 14, 'holiday_in_week_move': False, 'holiday_move_offset': -2, 'observed': True}. Please check the documentation how to configure the functionality.
Removed data config {'offset': 14, 'holiday_in_week_move': False, 'holiday_move_offset': 1, 'observed': True}. Please check the documentation how to configure the functionality.
Diagnotics see here

The error is just a reminder that it removed the parameters, that were previously obsolete and now are removed.
Looking at them, I see 3 things.

There is a partial configuration for moving schedule based on a country holidays, but you did not configure any country, so this is not used, right?
You have 1 date you want to include manually. But that does not make any sense as you already have a regular collection on this date. I am not sure why you configured it, but to me it looks like it was redundant.
I am a bit confused by your offset configuration. You have the collection set-up for every  21 days, starting on 2022-03-07. But then you ask to manually offset it by 21 days. That makes no sense. What the offst used to do was, it would calculate the schedule, and then apply a manual offset. So if you had it configured let's say for 1st wednesday each month, with offset -7 it would be last wednesday (the previous month). But in your case, having it with period 21 days and offseting it by 21 days makes no sense (except for the first date, which you then added manually).

So my conclusion is, that your configuration is fine and simple as you say. Previously, you had it over-complicated, proabably becase it was so complicated and confusing (which was the reasn for the chnage). Ok?

So, in my case I can leave it as it is?
I though i had to start importing 3 different blueprints to reconfigure it!
So on 7 March when green bin starts again its 3-week cycle do i have to get a new blueprint

Ok, so you need to have 2 entities, both with 14 days period, but one with a starting date a week later than the other.
Alternatively, you can configure one for odd and one for even week number - but that is based on week numbers, so thsi might be an issue on new year, if the year has an odd number of weeks, and then it starts with week number 1, it would basically reset in January. So it might not be what you want.
For the 3rd one, just configure the first month and last month - that's a standard config on the second screen. I think you have that configured. And you need to configure it either every 21 days (3 weeks) starting from a chosen date. The challenge here is, that it will repeat evey 21 dats starting from the initial date, and it will just cut out the two months. So when you configure it to start on March 7 2022, for next year it will start in a multiply of 21 days from the March 7 - that will be March 20 I am afraid. This is how it always worked, I did not change a ting in this. So you'd have to adjust the config next year to start on March 6 next year.
Or, you can now configure it for a weekly schedule, configure it for a manual update and then make an automation to drop the collections in the two weeks in between. So technically, it is now possible (was not before). But if thsi is not your thing, I'd leave it there.

HI
I cannot work out where i get to step 2 ?
I set everyndays but it get an error if i hit submit!
Where is the area i set days or dates?

After you submit. But it looks like you found a bug. Let me check....

Also another errror

That's interesting, I had this out for quite some time, but nobody found this. Anyhow, i just made a release fixing the first issue. I cannot replicate the other one, that one works fine for me.

Well at least it was found early :)
The one just did it 1 time but now looks ok

I have the new version but i think the day calcs are out.
My next collection is tomorrow so i expect to see 1 day
My Brown Bin is next Wed i expect to see 8 days
Under the old settings that was correct.
But now i have set it via the UI is shows Black Bin 0 Days which means today  & Brown Bin & Days which is next Tue

Feb 9 2021 was Tuesday. Today is Tuesday. So the collection should today, not tomorrow.

Sorry I didn't see the year default back to 2021

Now it is working pure genius very easy to use well done


A way to select to delete downloads/ the loading thing before downloading should be removed or faster

A way to select to delete downloads, i use file manager to delete in bulk🙃
the loading thing before downloading should be removed or faster because i can escape it  and it still downloads or goes to que

As I already mentioned in your issue yesterday that select to delete is not getting developed (at least in the near future). It would be a waste of time compared to other features and fixes.

the loading thing before downloading should be removed or faster because i can escape it and it still downloads or goes to que

I am not planning on changing that. The loading screen signals to the user that the button is working and responsive to prevent them from clicking twice. It would be preferable to make the loading on the button only instead of a popup, but that would entail tons of work fixing something already working. If I ever run out of stuff to do I might make it display the loading on the button.


Add GetOrReserveArtifact API

TL;DR
Create an API GetOrReserveArtifact that will be used by flytepropeller to reserve a spot for populating the artifact if the artifact does not exist yet.
Will implement ExtendReservation & ReleaseReservation APIs in separate PRs.
Type

[ ] Bug Fix
[X] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[X] Unit tests added
[X] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
Create an API GetOrReserveArtifact that will be used by flytepropeller to reserve a spot for populating the artifact if the artifact does not exist yet. A new Reservation table is created to track which task is occupying the spot.
Check https://docs.google.com/document/d/1Oq8f0yVoHMHDCUbxhu9V-4dDLzbbM4YWcnNNscEnYkM/edit#heading=h.ipjr4byywfgm for more details,
Tracking Issue
https://github.com/flyteorg/flyte/issues/872
Follow-up issue
NA
OR
https://github.com/lyft/flyte/issues/

cc: @kumare3 @EngHabu

@milton0825 are you still working on this?

Yeah this was previously blocked by the gorm upgrade because we need the upsert feature.

@katrogan no I haven't. Just want to make sure that we are aligned with this approach before I invest more effort to add more tests & integration testing on sandbox

@milton0825 got it 👍
@EngHabu still want to take a look?

Cool sounds like we are aligned with the approach and I will be adding docs/tests.


bug(docs): keystore path as a folder

Component
Cast
Have you ensured that all of these are up to date?

[X] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (3ff3d05 2024-10-01T00:25:45.808130533Z)
What command(s) is the bug in?
cast send
Operating System
Linux
Describe the bug
When using cast send with the --keystore path, cast command complains that we need to specify the file, while in the docs, we can specify the folder. In fact, the folder is much more better, as in dapp tools.
❯ cast send 0x... 'transfer(address,uint256)' 0x... 0x... --keystore ~/user/secrets
Error:
Keystore path `"/home/user/secrets"` is a directory. Please specify the keystore file directly.

but the docs permits using a folder as a path:
--keystore path
    Use the keystore in the given folder or file.
    Environment: ETH_KEYSTORE

Thanks @henry-hz for your report, I've updated the documentation to reflect that you are required to specify the filename.

Thanks @zerosnacks , in fact it would be great if cast could support also a file path as in dapp.tools seth supports


Allow configurable number of trusted reverse-proxies

Currently we assume there's only one reverse-proxy between CiviForm and the public internet, so we take the rightmost IP from X-Forwaded-For when the CLIENT_IP_TYPE is FORWARDED.
Per the MDN docs we should take the rightmost IP that isn't a trusted proxy:

The count of reverse proxies between the internet and the server is configured. The X-Forwarded-For IP list is searched from the rightmost by that count minus one. (For example, if there is only one reverse proxy, that proxy will add the client's IP address, so the rightmost address should be used. If there are three reverse proxies, the last two IP addresses will be internal.)

This is fixed when there's a NUM_TRUSTED_PROXIES flag that's used when selecting a client IP address.

Config updated in Add NUM_TRUSTED_PROXIES to example config file


Multi-Platform support

Added support for macOS, tvOS and watchOS.
Bumped the version of the PromiseKit dependency.
Replaced the previous project with another one which includes framework and test targets for all the supported platforms.
Updated the Travis CI script.
Removed the AwaitKit class to avoid conflicts with the AwaitKit namespace.
Moved the methods from the DispatchQueue extensions to the main file because Swift wrongly detects ambiguous use for them.
Updated the .gitignore file to include the Pods so that the Travis builds will be faster and won’t time out.

Current coverage is 1.19% (diff: 1.19%)

No coverage report found for master at 111f9ab.

Powered by Codecov. Last update 111f9ab...86ecb9d

Hi,
Thank you for your contribution, this is really helpful. However there are some points I detailed in the reviews that you should update. For example you updated the method signatures in a way that is against to the swift API design guideline. I think we should keep the original way. But in order to avoid conflit with the DispatchQueue apis we could create a sub-category like with the Kingfisher library.
Moreover the the code coverage don't seems to work anymore.
Thanks,
Yannick

Hey @yannickl, thanks. The whole point of this PR was just to bootstrap the project in a more fashionable way, just like for example AlamofireImage is doing (https://github.com/Alamofire/AlamofireImage). I've created a new project that's building the framework for the same platforms that PromiseKit is available and I've included the tests for each platform and also the Example target.

Yes I understand. In fact AlamofireImage uses both approach:
// When working with requests
Alamofire.request("https://httpbin.org/image/png")

// For extensions
let imageView = UIImageView(frame: frame)
imageView.af_setImage(withURL: url, placeholderImage: placeholderImage)

May be we could do the same thing, by adding an extension to the DispatchQueue and allowing by the same to use the AwaitKit namespace style.
Yeah codecov is not really stable, there is often issues with this service... :/ Will be see the next build if it'll work properly.

I've updated the extension to follow the Kingfisher's approach.
Cheers!

Sorry for the late, I was really busy. Thank you for your great work. I'll update the project this w-e. 👍


Need Proofreading on YARN Basics

Lot of information given on YARN Basics, which is great!
However, I feel there is a need of Proofreading on content.
Example:
Sentence (as stated above) “The ResourceManager grants cluster compute resources to applications like MapReduce jobs.”
May be stated as:
The ResourceManager grants cluster’s compute resources to applications like MapReduce jobs.
--Correction: Use of apostrophe
The ResourceManager grants cluster’s compute resources to MapReduce jobs.
--Correction: Use of apostrophe and sentence optimisation

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

ID: 40fdbf85-03fc-7ba1-dca8-4c46ad35500f
Version Independent ID: 5d635132-623b-ba6a-27d7-1b801fe74fdf
Content: Hadoop architecture - Azure HDInsight
Content Source: articles/hdinsight/hdinsight-hadoop-architecture.md
Service: hdinsight
GitHub Login: @ashishthaps
Microsoft Alias: ashishth

@jpchauhan
Thanks for the feedback! We are currently investigating and will update you shortly.

@jpchauhan I don't agree.  If you want to use the apostrophe, you would need to add an article in front of the word that is demonstrating possession:
"The ResourceManager grants a cluster’s compute resources to MapReduce jobs."
or
"The ResourceManager grants the cluster’s compute resources to MapReduce jobs."
As far as the optimization suggestion, the part of the sentence "applications like" suggests that not all applications the Resource Manager deals with are MapReduce.  This seems appropriate since YARN can run arbitrary processing paradigms beyond MapReduce.  Your suggestion is a true statement, but it is not necessarily better, only shorter.
We are closing this issue for now but feel free to add more comments.   @ashishthaps feel free to chime in if you have an opinion.


Add yarn cache to Travis

Codecov Report

Merging #23 into master will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff          @@
##           master   #23   +/-   ##
====================================
  Coverage      55%   55%
====================================
  Files          32    32
  Lines         560   560
====================================
  Hits          308   308
  Misses        252   252

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 9f0919a...1858f50. Read the comment docs.


Updates before 0.22.1

Mostly boring, but we'll get Boopickle for Scala 3 now.

I'm going to spin off boopickle.  It doesn't work on Scala 3.


Feature/wjiang/#117 install new profiler

Description

A new profiler (MAPL_Profiler) package is added, which eventually will replace the MAPL_Profiler module. Both profilers are now co-existing  and reporting the results in MAPL.
Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Trivial change (affects only documentation or cleanup)

Checklist:

[x] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[ ] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

I'm not really qualified to review this. I just wanted to say: Daaaaaaang! Complex! Nice job, @weiyuan-jiang
I might be coming to you once this is in to ask how to run your new pFUnit tests. I'd like to (try to) add them to my CI tests.

These change are largely ones that Atanas implemented before in the bridge repo.   A few difference.  I've reviewed and for now we have left the original timers in place.   Once Scott adopts MAPL 2.1, we can start eliminating the old timers in the gridcomps and accumulating the new ones that could not be handled purely inside MAPL.


Cache@2 does not handle junction / symbolic link gracefully (caches and restores as folders/files)

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: Cache
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks/Cache
Environment

Server - Azure Pipelines or TFS on-premises?

Azure Pipelines
- If using TFS on-premises, provide the version:

- If using Azure Pipelines, provide the account name, team project name, build definition name/build number:

N/A / Private / Proprietary

Agent - Hosted or Private:

Private
- If using Hosted agent, provide agent queue name:

- If using private agent, provide the OS of the machine running the agent and the agent version:

OS: Windows_NT / 10.0.17763
Agent: 2.195.0
Issue Description
The Cache@2 task does not handle junctions/symlinks gracefully. Instead of recognizing them as junctions, it crawls the entire folder and caches everything as static folders/files.
We have a complex npm structure with workspaces, and those workspaces are referenced as packages by the root and by each other. npm handles this by creating symbolic links / junctions in order to handle the relative references to the other local packages.
Due to the size of our node_modules folders, simply caching the npm cache doesn't really save us any time. Because we are using private agents, we actually have instead set up a common npm cache for all the agents on a box which does help to shave a small fraction of the time for the install, but not much. The packages download reasonably quickly however reconstructing the node_modules folder takes a while even with all the modules cached globally. It therefore makes more sense for us to use the Cache task to cache the node_modules folder (using package lock as the key) and only run npm ci when there is a cache miss.
Because of the fact that the Cache task does not handle symlinks/junctions well, it ends up caching old source code in the node_modules folders instead of restoring the symlink to the actual source location.
For now, we are working around this by deleting the specific workspace package folders in the node_modules and running a targeted npm install for the workspace packages.
Ideally, it would be nice to see one of two options to resolve this in the task:

The task should be able to recreate symlinks instead of blindly copying everything to the cache
If this isn't a valid option, the task should be able to support path exclusions so we could simply omit the symlink folders (we would still need to run the targeted npm install to restore the symlinks but at least bad data isn't getting cached).

Task logs
N/A
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
N/A
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
N/A
[Insert error from the logs here for a quick overview]

I agree caching of NPM could be better (faster / smarter at restoring node_modules instead of rebuilding it every time), and we all seem to be trying to build it because we want faster development cycles. I'm going to do what @richshadman has suggested "run the targeted npm install to restore the symlinks"

@johnterickson  or anyone really has there been a behavior change? it seems on 9/16 that this behavior changed with the cache task. It is now restoring symlinks which has ironically broken our current pipelines as it is caching our source code in workspaces and restoring it OVER the source code pulled from git.

For now I'm going to change our pipeline logic to clear out the symlinks before the job finishes so it won't cache them at all. This avoids any behavior changes in the future, whether it is due to a change in cache task, or npm behavior with how it manages symlinks.

@richshadman we shell out to the environment's tar : https://github.com/microsoft/azure-pipelines-agent/blob/23233ae52ce8100bf293ff126ac37dc15d134664/src/Agent.Plugins/PipelineCache/TarUtils.cs#L168 so maybe that changed for you?

The only thing that has changed on these servers are routing patching (windows updates) and Visual Studio updates. We did update VS in the past month. Is it possible this downstream dependency was updated with Visual Studio? We don't install a tar utility directly.


Ground truth image

did you convert the ground truth image as jpg?

Hi @zafor44,
The ground truths were originally downloaded as RGB jpg images. I did not had to explicitly convert them to jpg.

Would you please share the code to patches the images or how could we divide the bid size image to a smaller number of segment.
Thanks


Fix db migration syntax error

File<PHONE_NUMBER>13.do.nys-privacy-v3.sql contains a syntax error that causes DB migrations to fail. Due to how the NPM migrations module works I'm not 100% sure that removing the migration file will result in a valid migration. Instead I've commented out the UPDATE statement and have replaced it with a SELECT of no data to ensure something is run in the file that will not cause an error.

Sent to wrong fork/branch. Sorry.


Open the coverage report with preselection of suite, model and run

Hi,
would it be possible to open the coverage report with a preselection of the dropdowns for test suite, model and run?
Background: we embed the coverage report into out own test results webpage, where we display the inputs and outputs of each test case. We would like to provide a link for each test case, that goes directly to the coverage of that particular test case.
Like  report.html?suite=OrderProcessTest&model=order-process&run=testHappyPath
I tried to look at the code for the html, but the javascript seems to be minified. Is it maintained somewhere else?
Thanks a lot!

This sounds like a good enhancement. Actually there are some changes I would like to see on the report page.
The source is hosted here https://github.com/Miragon/flowcov-viewer and therefore not directly hosted in this repository.


Do basic R2RC theming on "member hub"

[ ] fonts
[ ] color scheme
[ ] logo

Made a new custom theme - can edit from here.

Made a total hash of the header bar too, changes are in layout.html

For Color Scheme:
Turn current red to R2RC red. Turn what's currently blue/grey to R2RC grey.


I can't get 'event("reaction_added", {..})' to work

Description
Describe your issue here.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[X] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Hello, I'm trying to create a basic Typescript Bolt application, for that I started from the Template provided in the example folder.
The application listens on the following two methods :
app.message("hello", async ({ message, say }) => {
  if (message.subtype === undefined || message.subtype === "bot_message") {
    await say({
      blocs : [...],
      text : `Hey there <@${message.user}>!`,
    }) ;
  }
}) ;

and
app.event("reaction_added", async ({ event, context }) => {
  try {
    // The `event` object contains information about the reaction added
    const { user, reaction, item } = event;

    // Do something with the event data
    console.log(`User ${user} added reaction ${reaction} to item ${item}`);
  } catch (error) {
    console.error(error);
  }
});

When I type "hello" in the general channel of my slack, the method is well executed.
Problem : But when I add reactions I can never get into the hook "reaction_added" ?
Thanks in advance for your help
package version: ^3.3.0
node version: v16.17.0
OS version(s): Mac Ventura 13.0.1
What you expected to happen :
When I add an emoji on a message I expect the "reaction_added" hook code to be executed
Actual result:
Nothing happened, function is not triggered
Attachments:
I tried to add several permissions without success, do I miss something ?
display_information:
  name: MyApp
  description: MyDescription
  background_color: "#000000"
features:
  bot_user:
    display_name: Test
    always_online: true
oauth_config:
  scopes:
    user:
      - reactions:read
    bot:
      - channels:history
      - channels:join
      - channels:read
      - chat:write
      - commands
      - groups:read
      - groups:history
      - im:history
      - im:read
      - mpim:read
      - users:read
      - reactions:read
settings:
  event_subscriptions:
    user_events:
      - reaction_added
    bot_events:
      - message.groups
      - reaction_added
      - message.channels
      - message.im
  interactivity:
    is_enabled: true
  org_deploy_enabled: false
  socket_mode_enabled: true
  token_rotation_enabled: false

Hi @victorlrz, thanks for asking the question!
Your app manifest looks valid, and I made sure that a brand-new app with the settings works without any issues. Please double-check the following points:

your app's bot user must be a member of the channels where reactions can be added
if you added the reaction_added event subscription after the app's initial installation, your app needs to be installed again

I hope this helps.

Hi @seratch,
Thanks a lot for your feedback, I just reinstalled the App and it worked! 🙏

if you added the reaction_added event subscription after the app's initial installation, your app needs to be installed again

But according to slack's description, it seems we are not required to re-install app again if we already own scope in Bot Token Scopes, and the issue for me is that reaction_added seems not reliable, my app sometimes cannot receive such reaction events and we have to react several times


Additional feature: Image name as text variable for display

Thanks for producing this.
A feature that would be nice quality of life thing (possibly needs manufacturer support)
ImageLibrary File Names visible on Still button test for simpler selection
When a user wants to switch to a different still - having the text (filename) as uploaded, can be a handy way to make it known what still you are switching to. This can be stored in the Gostream as the filename is provided on upload, and then the filename (minus extention) can be presented to companion as a variable, which can be used in the text display of the button. That's far more user friendly than Still 1/ Still2 / Still 3
workflow:
upload roadsign.jpg to ImageLibrary1
upload testPattern.jpg to ImageLibrary2
upload Cat.jpg to ImageLibrary3
upload dog.jpg to ImageLibrary4
Still 1 active slot has ImageLibrary 1 image attached
Still 2 active slot has ImageLibrary 3 image attached
Thus, $(gostreamdeck:ImageLibrary_1_Text) would be "roadsign"
Thus, $(gostreamdeck:ImageLibrary_2_Text) would be "testPattern"
Thus, $(gostreamdeck:ImageLibrary_3_Text) would be "Cat"
Thus, $(gostreamdeck:ImageLibrary_4_Text) would be "dog"
Thus, $(gostreamdeck:StillImage_Slot1_Text) would be "roadsign"
Thus, $(gostreamdeck:StillImage_Slot2_Text) would be "Cat"
and you can select the file (by name) for each slot, by assigning buttons and including the filename on the button text using those variables.
I looked, but couldn't see this in the current published release. Could have missed it though!

Corollary: The Labels applied to each of the inputs (via the software) could also read from the names assigned to sources (there appears to be a way to label input 1 as camera1, input 2 as wide, input 3 as PC, etc, for the multiview display.)
That could also be handy on the input labels, already implemented in $(gostreamdeck:pre1_input_id), etc
Again, this may need manufacturer support as well.


Update configuration for k8s.

@fiji-flo quick r?

Coverage remained the same at 89.494% when pulling 676f7947988448a480f9441ed1ac13a43b4bd394 on akatsoulas:dev-preview-integration into 5ef50c48420bbb4d671350b57f3fdcb88e71e042 on mozilla:master.


Support the CaRT format

[ ] Download samples from the server
[ ] Uploading samples to the server

Existing Rust crate: https://github.com/CybercentreCanada/cart-rs, https://crates.io/crates/cart_container
Use the headers to store hashes, server validates if present.

Blocked on https://github.com/CybercentreCanada/cart-rs/issues/1, the Rust compiler can't see the crate, but the IDE can.

Closed via a34c5c042e25d942c6ea795932bfeb08772b9ba9, 313128ab6f320940c5eae36d0f5d7e51582cfb96


Improve install instruction

Maybe will be useful to notice, that we need to run installer by root-user to place binary in /usr/local/bin/
Also, installer check shasum, but by default this script is not installed
bash d8-install.sh
Downloading https://github.com/deckhouse/deckhouse-cli/releases/download/v0.2.1/d8-v0.2.1-linux-amd64.tar.gz
Verifying checksum... d8-install.sh: строка 89: shasum: команда не найдена

We need package libdigest-sha-perl for Debian-like and something like perl-Digest-SHA on CentOS-like
Also, maybe better to switch to /usr/bin/sha256sum looks like it exists by default (coreutils package)

This has been addressed in https://github.com/deckhouse/deckhouse-cli/pull/41


[OSSM-107] Add LuaJIT patch for s390x

Commit Message: Add LuaJIT patch for s390x
Additional Description: This is a followup from comments in https://github.com/maistra/proxy/pull/114
Risk Level: Low
Testing: Scratch build downstream
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: Maintains status-quo on s390x wrt luajit plugin.
/cc @dmitri-d

/ok-to-test

@yselkowitz: Thanks for the PR. This lgtm, provided CI is happy. @jwendell: could you too take a look please?

Retitled the PR.


malformed URL

We got an issue with "malformed URL" in one of our tests, see https://github.com/LibreCat/Catmandu-SRU/issues/41. We used $server->url and passed it to Furl which will throw an error:
Passed malformed URL: http://[::1]:46249/?...
Is it possible to get a "proper" URL?

Hi,
The URL is generated from the socket class (ipv4 or ipv6), and should be routable in every case. I think the bug is more that Furl doesn't understand ipv6 HTTP URLs.
If you really want http://localhost:nnnn as URL, you can munge the URL in $server (untested) as a workaround:
$server->host('localhost')

-max
Am 23. September 2019 10:38:00 MESZ schrieb Johann Rolschewski<EMAIL_ADDRESS>
We got an issue with "malformed URL" in one of our test, see
https://github.com/LibreCat/Catmandu-SRU/issues/41. We used
$server->url and passed it to
Furl
which will throw an error:
Passed malformed URL: http://[::1]:46249/?...
Is it possible to get a "proper" URL?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/Corion/Test-HTTP-LocalServer/issues/4

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

... looking at the code, it's more like
$server->{_server_url}->host('localhost')

-max
Am 23. September 2019 10:38:00 MESZ schrieb Johann Rolschewski<EMAIL_ADDRESS>
We got an issue with "malformed URL" in one of our test, see
https://github.com/LibreCat/Catmandu-SRU/issues/41. We used
$server->url and passed it to
Furl
which will throw an error:
Passed malformed URL: http://[::1]:46249/?...
Is it possible to get a "proper" URL?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/Corion/Test-HTTP-LocalServer/issues/4

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Thanks!


Incorrect completion inside comment

Sometimes at the end of a comment line, I hit Return and VS Code decides to insert some meaningless completion.  GIF attached.

Similar issue: https://github.com/ballerina-platform/ballerina-lang/issues/30696


Slides having Popper hides behind the next slide

Check that this is really a bug

[X] I confirm

Reproduction link
https://stackblitz.com/edit/swiper-angular-example-nvddeg?file=src%2Fapp%2Fapp.component.html,src%2Fapp%2Fapp.component.scss,src%2Fapp%2Fapp.component.ts,src%2Fapp%2Ffocus-slide.directive.ts,src%2Fapp%2Fapp.module.ts
Bug description
I have used ngx-popper to display a dropdown of links inside a slide. When I open the dropdown and it expands onto the next slide, a portion of the dropdown is hidden behind the next slide.
Expected Behavior
The dropdown should not be hidden behind slides
Actual Behavior
A portion of the dropdown is hidden behind the next slide.

Swiper version
10.3.1
Platform/Target and Browser Versions
Chrome is up to date Version 115.0.5790.110 (Official Build) (64-bit)
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Do you want to ask a question? Are you looking for support? Stack Overflow or Swiper Discussions is the best places for getting support

Please, don't use GitHub issues for questions


Switched to setuptools_scm

You will have to add version tags to git ("1.0b1" etc.) for this to work.


Billing seems off

A user reported that they think they are being billed too much on mainnet. After investigating a bit, I found some behaviors I can't explain.
The user has 37 VMs deployed on a mix of certified and non certified nodes with the same specs, and all VMs have a public IP reserved.
Here's an example contract:
    "nodeContracts": [
      {
        "resourcesUsed": {
          "cru": "8",
          "hru": "0",
          "mru": "34359738368",
          "sru": "377957122048"
        },
        "contractID": "338060",
        "nodeID": 2014
      }
    ],

Based on the dashboard calculator, this contract should be bill as seen below. I've entered the users actual approximate balance which should qualify for the gold discount level:

I also double checked this calculation against another spreadsheet we use for working with the billing calculations and the figures were very close.
But when I check some recent billing reports for this contract, I see the following:
    "contractBillReports": [
      {
        "amountBilled": "60000910",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712108136"
      },
      {
        "amountBilled": "65250724",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712104536"
      },
      {
        "amountBilled": "49563869",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712100936"
      },
      {
        "amountBilled": "59312443",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712097336"
      },
      {
        "amountBilled": "55289678",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712093736"
      },
      {
        "amountBilled": "52322507",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712090136"
      },
      {
        "amountBilled": "52550164",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712086536"
      },
      {
        "amountBilled": "50999400",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712082936"
      },
      {
        "amountBilled": "44415086",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712079336"
      },
      {
        "amountBilled": "50868664",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712075736"
      }

The amounts billed seem much too high and only a silver discount is applied. These are hourly bills, so the amount should be more like:
921 TFT/month / 30 / 24 = 1.28 TFT/hour

Instead of:
60000910 / 1e7 = 6.000091 TFT/hour

Here's another example of a contract with the same specs, also on a DIY node, with rather different billing over its last ten billing reports:
    "contractBillReports": [
      {
        "amountBilled": "47836986",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712109474"
      },
      {
        "amountBilled": "45252290",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712105874"
      },
      {
        "amountBilled": "40629248",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712102274"
      },
      {
        "amountBilled": "40951972",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712098674"
      },
      {
        "amountBilled": "36341400",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712095074"
      },
      {
        "amountBilled": "33882664",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712091474"
      },
      {
        "amountBilled": "21187343",
        "contractID": "340083",
        "discountReceived": "Gold",
        "timestamp": "1712087874"
      },
      {
        "amountBilled": "52841422",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712084274"
      },
      {
        "amountBilled": "55805207",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712080674"
      },
      {
        "amountBilled": "56989307",
        "contractID": "340083",
        "discountReceived": "Silver",
        "timestamp": "1712077074"
      }

I can't find any reason to explain why these contracts should be billing at multiples times what's shown by the calculator.

Public traffic is also billed

I did some maths to check these numbers including NU for last billing and nru reports.
I chose 2 last reports that correspond to more or less same period of time (billing reports and nru reports are not sent at same moment even if sent at same frequency)
See here:
{
  "data": {
    "contractBillReports": [
      {
        "amountBilled": "57965722",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712151336"
      },
      {
        "amountBilled": "57764807",
        "contractID": "338060",
        "discountReceived": "Silver",
        "timestamp": "1712154936"
      }
    ],
    "nruConsumptions": [
      {
        "contractID": "338060",
        "nru": "118471108134",
        "timestamp": "1712148920",
        "window": "3600"
      },
      {
        "contractID": "338060",
        "nru": "117846081049",
        "timestamp": "1712152520",
        "window": "3600"
      }
    ]
  }
}

Given the what calculator gives for Gold discount for such resources
921 tft/month / 30 / 24 = 1.28 tft/hour
This means only CU SU IPU resources before discount
Before 60% discount = Gold * 2.5
cost [CU SU IPU] =  2302,5 tft/month or 3,19 tft/hour

Now let see NU resources cost per hour
nru consumption * nru price
nru consumption =<PHONE_NUMBER>49 * 10e-9 = 117,84 Gb
nru price usd = 15000 * 10e7 = 0.0015 usd/hour
nru price tft = 0.0015 usd/hour / 0.02642 usd/tft = 0.0567 tft/hour
cost [NU] = 117,84 * 0.0567 = 6,68 tft/hour

So it gives
Total cost [NU CU SU IPU] = 3,19 + 6,68 = 9,87 tft/hour

After applying 40% Silver discount which is on billing report
Total cost [Silver] = 9,87 * 0,6 = 5,922 tft/hour

Which corresponds to what was billed on billing report
57764807 * 10e7 = 5,77 tft for 1 hour

Thanks guys. Billing for network traffic indeed explains what's going on here.


Graph inspect (ghost image)

Hi,
When I enable the Graph Inspect id toggle, all the sub content is behind the other buttons, it does not get pushed down.
It happens on linux or Windows or Mac, no matter what browser I use.
I'm using Grafana Cloud (SaaS) 9.1.3

Grafana support team answer:
"Hi again,
I reached out to my team, and they helped me realize this is for a 3rd party plugin.
You will have to reach out to the developer of this plugin in order to get an update.
I am sorry for the confusion and inconvenience, but that is the next best step to get a fix here."

same issue here

same here

same here

same here


Enabling transforms for histogram, box, violin

Could we try to enable transforms for these three trace types? If it doesn't work, can we try to figure out why?

I was just about to open an issue on this.  I would suggest line plot as well as the trace types you listed.  There is nothing preventing filter transforms for histogram, box, line (and presumably violin), and that would be very useful for me.
Could we enable filtering, even if aggregate (or split) doesn't make sense for those types?

Line is already supported AFAIK because it's a specialization of scatter. And yes, what I'd like is all three transform types for these three trace-types.


iLO4 - ParseError: no element found

I've been running a few iLO containers for a while now and I keep seeing the following error occur. The frequency is sporadic, some containers don't error for months, others are many times a day and the ones erroring frequently are not always the same ones. The error out of the logs is as follows:
hpilo-exporter-4_1       | <IP_ADDRESS> - - [18/Aug/2021 00:42:19] "GET /metrics?ilo_port=443&ilo_user=monitoring HTTP/1.1" 200 - hpilo-exporter-4_1       | <IP_ADDRESS> - - [18/Aug/2021 00:46:19] "GET /metrics?ilo_port=443&ilo_user=monitoring HTTP/1.1" 200 - hpilo-exporter-4_1       | <IP_ADDRESS> - - [18/Aug/2021 00:50:20] "GET /metrics?ilo_port=443&ilo_user=monitoring HTTP/1.1" 200 - hpilo-exporter-4_1       | <IP_ADDRESS> - - [18/Aug/2021 00:54:20] "GET /metrics?ilo_port=443&ilo_user=monitoring HTTP/1.1" 200 - hpilo-exporter-4_1       | <IP_ADDRESS> - - [18/Aug/2021 00:58:20] "GET /metrics?ilo_port=443&ilo_user=monitoring HTTP/1.1" 200 - hpilo-exporter-4_1       | <IP_ADDRESS> - - [18/Aug/2021 01:02:20] "GET /metrics?ilo_port=443&ilo_user=monitoring HTTP/1.1" 200 - hpilo-exporter-4_1       | <IP_ADDRESS> - - [18/Aug/2021 01:06:21] "GET /metrics?ilo_port=443&ilo_user=monitoring HTTP/1.1" 200 - hpilo-exporter-4_1       | <IP_ADDRESS> - - [18/Aug/2021 01:10:21] "GET /metrics?ilo_port=443&ilo_user=monitoring HTTP/1.1" 200 - hpilo-exporter-4_1       | Traceback (most recent call last): hpilo-exporter-4_1       |   File "/usr/lib/python2.7/SocketServer.py", line 596, in process_request_thread hpilo-exporter-4_1       |     self.finish_request(request, client_address) hpilo-exporter-4_1       |   File "/usr/lib/python2.7/SocketServer.py", line 331, in finish_request hpilo-exporter-4_1       |     self.RequestHandlerClass(request, client_address, self) hpilo-exporter-4_1       |   File "/usr/lib/python2.7/SocketServer.py", line 652, in __init__ hpilo-exporter-4_1       |     self.handle() hpilo-exporter-4_1       |   File "/usr/lib/python2.7/BaseHTTPServer.py", line 340, in handle hpilo-exporter-4_1       |     self.handle_one_request() hpilo-exporter-4_1       |   File "/usr/lib/python2.7/BaseHTTPServer.py", line 328, in handle_one_request hpilo-exporter-4_1       |     method() hpilo-exporter-4_1       |   File "/usr/src/hpilo_exporter/src/hpilo_exporter/exporter.py", line 159, in do_GET hpilo-exporter-4_1       |     metrics = iloGetMetrics(ilo_host, ilo_port, ilo_user, ilo_password) hpilo-exporter-4_1       |   File "/usr/src/hpilo_exporter/src/hpilo_exporter/exporter.py", line 69, in iloGetMetrics hpilo-exporter-4_1       |     health_at_glance = ilo.get_embedded_health()['health_at_a_glance'] hpilo-exporter-4_1       |   File "/usr/lib/python2.7/site-packages/hpilo.py", line 961, in get_embedded_health hpilo-exporter-4_1       |     process=process) hpilo-exporter-4_1       |   File "/usr/lib/python2.7/site-packages/hpilo.py", line 698, in _info_tag hpilo-exporter-4_1       |     header, message = self._request(root) hpilo-exporter-4_1       |   File "/usr/lib/python2.7/site-packages/hpilo.py", line 250, in _request hpilo-exporter-4_1       |     message = self._parse_message(data) hpilo-exporter-4_1       |   File "/usr/lib/python2.7/site-packages/hpilo.py", line 556, in _parse_message hpilo-exporter-4_1       |     message = etree.fromstring(data) hpilo-exporter-4_1       |   File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1312, in XML hpilo-exporter-4_1       |     return parser.close() hpilo-exporter-4_1       |   File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1665, in close hpilo-exporter-4_1       |     self._raiseerror(v) hpilo-exporter-4_1       |   File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1517, in _raiseerror hpilo-exporter-4_1       |     raise err hpilo-exporter-4_1       | ParseError: no element found: line 409, column 46

I found the issue, the issues arises when iLO accepts the login but does not provide a valid response, I believe it is due to too many API calls but haven't been able to confirm this yet.


can you add support to minimumTrackTintColor for single thumb?

can you add support to minimumTrackTintColor for single thumb?

Im not sure what you mean on this one sorry!


Why can’t I reproduce the results of the paper?

I reproduced it on the RAD data set following to the instructions you provided.
But the result like above

"python3 train_rad.py --checkpoint ./pretrain/med_pretrain_29.pth  --output_dir ./output/rad"

@languandong Did you solve the problem of reproducing? I have trouble reproducing the result on RAD dataset too. And it looks like this (freeform only):

@pengfeiliHEU  I am figuring what went wrong. Can I ask how you split the data in train and test set? Because I see that in the original evaluation code the phrase type checks "freeform" when use freeform mode. However, in my test data split, the freeform question is marked "test_freeform". This is where it confuses and I modified the evaluation code to be "test_freeform" to fit my test data.


break_chained_methods behaviour

There shoud be option to set max num of chained methods before breaking it:
Eg:
"break_chained_methods": 2

this.$("#fileName").val().addClass("disabled")
    .prop("disabled", true)

I see no sense in breaking when there is only 1 meth (it's not a chain in this case :)). So maybe default behaviour should be: if there is more than 1 chained meth then perform breaking.

Definitely, this would be extremely useful. It is also the recommendation of AirBnB Javascript guidelines: https://github.com/airbnb/javascript#whitespace--chains

Use indentation when making long method chains (more than 2 method chains)

And makes all sense in terms of readibility

@joaobarcia
This is an interesting guideline.  In this "good" example:
$('#items')
  .find('.selected')
    .highlight()
    .end()
  .find('.open')
    .updateCount();

How are the indents for .hightlight() and .end() determined to be 4 instead of 2?  If anything there have been more requests for unindenting - see #482.

@bitwiseman I believe they are increasing identation after each selector to make it easier to check what is being 'highlighted' and 'updated the count'.
But if that should be done or not is probably a whole other question by itself :P
Nevertheless, the part of "break chain if chain longer than x" I believe would be quite useful.


Server Error when npm run serve

Getting this Error: Server Error with following stack trace when running production mode i.e. npm run serve. Below I have also included the browser console output.
Error: Server Error     at E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\dist\private\server.js:83:23     at Layer.handle_error (E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\node_modules\express\lib\router\layer.js:71:5)     at trim_prefix (E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\node_modules\express\lib\router\index.js:310:13)     at E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\node_modules\express\lib\router\index.js:280:7     at Function.process_params (E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\node_modules\express\lib\router\index.js:330:12)     at next (E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\node_modules\express\lib\router\index.js:271:10)     at E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\dist\private\server.js:69:13     at Layer.handle [as handle_request] (E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\node_modules\express\lib\router\layer.js:95:5)     at trim_prefix (E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\node_modules\express\lib\router\index.js:312:13)     at E:\0000.src\02.web.02\00.webpack\angular2-starter-kit-master\node_modules\express\lib\router\index.js:280:7 DEPRECATION WARNING:renderToStringWithPrebootis no longer supported and will be removed in next release. DEPRECATION WARNING:renderToStringis no longer supported and will be removed in next release. DEPRECATION WARNING:renderToStringWithPrebootis no longer supported and will be removed in next release. DEPRECATION WARNING:renderToStringis no longer supported and will be removed in next release.
Browser console output:
dom_adapter.ts:143POST http://localhost:3000/sockjs-node/464/f41f5cug/xhr_streaming?t=1461350744960 500 (Internal Server Error)scheduleTask @ dom_adapter.ts:143ZoneDelegate.scheduleTask @ dom_adapter.ts:143Zone.scheduleMacroTask @ dom_adapter.ts:143(anonymous function) @ dom_adapter.ts:143send @ VM1625:3AbstractXHRObject._start @ abstract-xhr.js:128(anonymous function) @ abstract-xhr.js:21ZoneDelegate.invokeTask @ dom_adapter.ts:143Zone.runTask @ dom_adapter.ts:143ZoneTask.invoke @ dom_adapter.ts:143 (index):1 EventSource's response has a MIME type ("text/html") that is not "text/event-stream".  Aborting the connection.

Will look into that. Thanks for reporting

Sorry, missed the npm run build step. After executing it the production mode runs without any errors.
Closing the issue and adding a star.

I'm glad that it works for you and thanks for the start :)


[Meta] Improve development speed?

First off, I really like libui-ng, and I'm appreciative of all the work that has been contributed to it. I want to see libui-ng succeed
as a library for making user interfaces that is easy to use from a variety of different languages :slightly_smiling_face:
I do have some nits with the status quo. In particular: pull requests seem to be piling up; the README still needs to be adjusted to reflect the current organizational structure; there isn't a place chat about libui apart from Github; and there seems to be only one person with the rights to merge to the repository. I think the underlying issue I perceive is a slow pace of development, and that's what I want to fix. I understand that libui is largely driven by volunteers without pay so there's only so much that can be expected. But I think there are some changes that can be made without requiring more resources.

Add one or more contributors to the libui-ng organization with merge access. This means not all PRs would have to go through @cody271
Make a procedure for trusted contributors to approve PRs to be merged. The system I am imagining would be a requirement of two reviews from contributors before the PR is approved (any new changes to a PR would require re-approval).

I'm not an expert on running an open source project though, so take my suggestions with a grain of salt. My goal here is to trigger discussion about improving the project, and NOT to rag on anything/anyone in particular.

I often find using libui more difficult than many people think.
'Difficult' means it needs many steps and much time.
First, libui is not just one library. It looks like one to users, but it is actually three different libraries for Windows, Mac, and Linux. So, there is three times more work. It's hard to find someone good at all three platforms, and switching between them can be tough on the brain.
Also, automating GUI tests is difficult. You can't do all the tests just with terminal commands. This means tools like GitHub Actions are not enough. People need to look and touch the screen to test. This requires many computers. Using cloud services can help but costs money and still needs different setups. So, it takes a lot of work. For full testing, you need many types of computers like Intel Mac, M1 Mac, M2 Mac, Raspberry Pi, and Win32.
In reality, users choose libui to avoid these complexities, but you can't reduce the complexities of the real world. So, we should think that these complexities are embedded in the development of libui.
It would be good to have more reviewers, but it might be hard to find suitable people. I think these hard parts are a big reason why developing libui is difficult. Finding ways to make this easier would be great...

A feasible system I came up with is to give tester roles to trusted contributors.
They make qa (or unit) tests, and report the results as PR comments, and they can put a tag like  tested.
Then, cody can merge PRs without testing, and focus on logical matters.

Have we heard of sikulix? https://sikulix.github.io/
It can use image recognition to click on buttons, as well as acting as a replacement for AutoHotKey (for Linux/Windows/MacOS).
Paired with xvfb you could create a graphical test suite for libui.


NextJS: next-i18next incompatibility

Steps to reproduce
Either pigment or next-i18next i18n library can work on a project:
https://github.com/rkurbatov/acq-test - here is example repository for NextJS v12. We managed to fix next-i18next import problem I created earlier (https://github.com/mui/pigment-css/issues/115 - author provided the fixed version) but here we have the new one, that looks totally unrelated on first sight.
Current behavior
https://github.com/rkurbatov/acq-test/blob/master/pages/_error.tsx - watch this file. Once you try to uncomment the code and import the Image component the build fails complaining on problems with the import of the next/image component (something __esModule related):
EvalError: Cannot assign to read only property '__esModule' of function 'function Head({ children  }) {
    const ampState = (0, _react).useContext(_ampContext.AmpStateContext);
    co...<omitted>..

The problem goes away if you comment either css() function call and related code or useTranslation() hook usage.
If you try NextJS version 13 it doesn't work even with the commented page complaining on something totally unrelated:
TypeError: result.then(...).finally is not a function
    at /home/rkurbatov/WebstormProjects/acq-test/node_modules/.pnpm/next@13.5.6_@babel+core@7.24.9_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/server/lib/trace/tracer.js:123:98
    at NoopContextManager.with (/home/rkurbatov/WebstormProjects/acq-test/node_modules/.pnpm/next@13.5.6_@babel+core@7.24.9_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:7057)

Disabling either css() function or useTranslate() hook helps as also.
I really don't understand how import of the translation hooks ruins things but it does, probably that's related to the way pigment transpiles the source code. For now that stops us from the usage of the pigment library that looks like the best alternative to emotion we use currently.
Expected behavior
No response
Context
No response
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: NextJS next-i18next

There are several NextJS related issues that are making pigment unsable for now. Unluckily.

@rkurbatov Yeah, I've been hitting many walls with pigment over the past few weeks. I really want to push ahead with it for my latest project because of code style familiarity, but there's such a wide variety of nasty issues. (The EISDIR one I posted, particularly. Have you not encountered this one?)
I did change my project over from next-i18next to next-intl for use with pigment and I'm actually much happier with next-intl than next-i18next which I've used for many previous projects. If your circumstances make it possible, I'd recommend a switch over!

@rhoiyds the problem is our project is pretty big and pretty old. We are using emotion everywhere but NextJS 13+ doesn't support it so we were searching for a good CSS library that allows simple conversion. The problem is I need to update multiple pacakages at once on a big codebase. And I cannot migrate styles partially. That works on a minimal projects but once I add something new - it fails due to incompatibilty. And when I resolve issue on the main project - there is another one that I have to find (as it fails silently quite often), fix on small repo and the fix on the main repo. And because pigment is still inmature and has way many issues with nextjs especially (that is known for its import joggling) I am afraid we have to search for something else.

@rkurbatov Yeah, I've been hitting many walls with pigment over the past few weeks. I really want to push ahead with it for my latest project because of code style familiarity, but there's such a wide variety of nasty issues. (The EISDIR one I posted, particularly. Have you not encountered this one?) I did change my project over from next-i18next to next-intl for use with pigment and I'm actually much happier with next-intl than next-i18next which I've used for many previous projects. If your circumstances make it possible, I'd recommend a switch over!

Feeling your pain and frustration. If this is the V6 direction for material-ui, then I am seriously considering other options as I am finding issue after issue with pigment making the DX super frustrating...


multidim variance fixes

multidim variance fixes

Refer to this link for build results (access rights to CI server needed):
/job/libnd4j_PR/53/


action

Good Day
I get an action is undefined?? please can you explain #newbie

@RAIDZA, can you please share the part of the code that is causing this error?

try: #Tries terminating an action if it exists
action.terminate()
except:
pass

Thank you for your quick response by the way.

``            keyword_index = self.porcupine.process(pcm)
        if keyword_index >= 0:
            print("Hotword Detected")

            try: #Tries terminating an action if it exists
                action.terminate()
            except:
                pass

will do. Will update a bit later thank you

Just checking out the code, action is not assigned to anything its #out


CMake modules are missing from tarball

I have eosio and eosio.cdt installed via Homebrew, and there are no CMake modules installed with eosio:
ls -la /usr/local/Cellar/eosio/1.7.1/opt/eosio/lib/cmake
total 0
drwxr-xr-x  2 Jeiwan  staff  64 Apr  3 23:47 .
drwxr-xr-x  3 Jeiwan  staff  96 Apr  3 23:47 ..

As I just found out they're commented out in the script that builds tarball:
https://github.com/EOSIO/eos/blob/686f0deb5dac097cc292f735ccb47c238e763de0/scripts/generate_tarball.sh#L24-L25
These modules are required to compile contract tests. eosio.contracts repo contains CMakeLists.txt that requires eosio package:
https://github.com/EOSIO/eosio.contracts/blob/master/tests/CMakeLists.txt#L7
But this package is not provided by eosio.cdt as well, thus there's currently no way to write and run contract tests.

Fixed by compiling EOS from sources.


Database interfaces and an implementation

Requirements:

#45
#46

ToDo:

[x] code
[x] test
[x] code documentation (more or less)
[ ] version.md
[ ] uncrustify

Codecov Report
Patch coverage: 73.33% and project coverage change: +0.25 :tada:

Comparison is base (b3aa70d) 73.55% compared to head (75a2a29) 73.80%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #49      +/-   ##
==========================================
+ Coverage   73.55%   73.80%   +0.25%
==========================================
  Files          54       59       +5
  Lines         983     1092     +109
  Branches      230      269      +39
==========================================
+ Hits          723      806      +83
+ Misses        137      132       -5
- Partials      123      154      +31

Impacted Files
Coverage Δ

...pp_utils/collection/database/impl/SafeDatabase.ipp
66.66% <66.66%> (ø)

...de/cpp_utils/user_interface/impl/CommandReader.ipp
66.66% <66.66%> (ø)

cpp_utils/src/cpp/utils.cpp
68.18% <71.42%> (+1.51%)
:arrow_up:

cpp_utils/src/cpp/event/StdinEventHandler.cpp
91.30% <91.30%> (ø)

...include/cpp_utils/user_interface/CommandReader.hpp
100.00% <100.00%> (ø)

... and 6 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


some problem about sgx_ecdsa attentation

I use the dcap client 'teaclave_sgx_tool ' to get attentation with the dcap service, but some error was occured.
The commend is:
./teaclave_sgx_tool attestation   --url https://localhost:8080 --algorithm sgx_ecdsa
The error is：
root@cc:~/incubator-teaclave#  Configured for development.
=> address: localhost
=> port: 8080
=> log: normal
=> workers: 4
=> secret key: generated
=> limits: forms = 32KiB
=> keep-alive: 5s
=> tls: enabled
Mounting /:
=> POST /sgx/dev/attestation/v4/report application/json (verify_quote)
Rocket has launched from https://localhost:8080
POST /sgx/dev/attestation/v4/report application/json:
=> Matched: POST /sgx/dev/attestation/v4/report application/json (verify_quote)
sgx_qv_verify_quote fialed: SGX_QL_QUOTE_CERTIFICATION_DATA_UNSUPPORTED
=> Outcome: Failure
=> Warning: Responding with 400 Bad Request catcher.
=> Response succeeded.
Where is the problem about it?

Hi @xglreal, thanks for your question! Sorry, I couldn't help you if you cannot provide more detailed information. Like how did you setup the environment?

Hi @xglreal, thanks for your question! Sorry, I couldn't help you if you cannot provide more detailed information. Like how did you setup the environment?

Hi @xglreal, thanks for your question! Sorry, I couldn't help you if you cannot provide more detailed information. Like how did you setup the environment?
The teaclave_dcap_ref_as is builded on the steps:
**docker run --rm -v $(pwd):/teaclave -w /teaclave
-it teaclave/teaclave-build-ubuntu-1804-sgx-dcap-1.6:latest
bash -c ". /root/.cargo/env &&
. /opt/sgxsdk/environment &&
mkdir -p build && cd build &&
cmake -DTEST_MODE=ON -DDCAP=ON .. &&
make"

docker run --rm -v $(pwd):/teaclave -w /teaclave
-it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
bash -c ". /root/.cargo/env &&
. /opt/sgxsdk/environment &&
mkdir -p build && cd build &&
cmake -DTEST_MODE=ON -DDCAP=ON .. &&
make"**
and the teaclave_dcap_ref_as will appear in the directory incubator-teaclave/release/dcap/.
I use incubator-teaclave/release/dcap/teaclave_dcap_ref_as, the builded tool to start dcap service. The setup message is below:
Configured for development.
=> address: localhost
=> port: 8080
=> log: normal
=> workers: 4
=> secret key: generated
=> limits: forms = 32KiB
=> keep-alive: 5s
=> tls: enabled
Mounting /:
=> POST /sgx/dev/attestation/v4/report application/json (verify_quote)
Rocket has launched from https://localhost:8080
Then, I use the command ./teaclave_sgx_tool attestation  --url https://localhost:8080 --algorithm sgx_ecdsa to get the dcap service, but eventually I fail to get the service.
The error message is below:
Error: ServiceError
Is there anyone can help me to fix it?
Thanks.

Hi @xglreal, thanks for your question! Sorry, I couldn't help you if you cannot provide more detailed information. Like how did you setup the environment?
The teaclave_dcap_ref_as is builded on the steps:
**docker run --rm -v $(pwd):/teaclave -w /teaclave
-it teaclave/teaclave-build-ubuntu-1804-sgx-dcap-1.6:latest
bash -c ". /root/.cargo/env &&
. /opt/sgxsdk/environment &&
mkdir -p build && cd build &&
cmake -DTEST_MODE=ON -DDCAP=ON .. &&
make"

docker run --rm -v $(pwd):/teaclave -w /teaclave
-it teaclave/teaclave-build-ubuntu-1804-sgx-2.9.1:latest
bash -c ". /root/.cargo/env &&
. /opt/sgxsdk/environment &&
mkdir -p build && cd build &&
cmake -DTEST_MODE=ON -DDCAP=ON .. &&
make"**
and the teaclave_dcap_ref_as will appear in the directory incubator-teaclave/release/dcap/.
I use incubator-teaclave/release/dcap/teaclave_dcap_ref_as, the builded tool to start dcap service. The setup message is below:
Configured for development.
=> address: localhost
=> port: 8080
=> log: normal
=> workers: 4
=> secret key: generated
=> limits: forms = 32KiB
=> keep-alive: 5s
=> tls: enabled
Mounting /:
=> POST /sgx/dev/attestation/v4/report application/json (verify_quote)
Rocket has launched from https://localhost:8080
Then, I use the command ./teaclave_sgx_tool attestation  --url https://localhost:8080 --algorithm sgx_ecdsa to get the dcap service, but eventually I fail to get the service.
The error message is below:
Error: ServiceError
Is there anyone can help me to fix it?
Thanks.


quest suggestion

hello i was wondering if possible could you add a collect option on the quest list when you click on items when starting a quest so then people can go and collect items and then bring them back to hand the quest in because at the moment there is craft break enchant ect so for example the quest could go go collect 45 red tulips and then deliver the items for rewards and so on thank you for taking the time to read this many thanks Pookylish

Thanks for your suggestion. If you want players to collect and deliver tulips, simply use a "Break block" objective for Stage 1, followed by a "Deliver item" objective for Stage 2.


Dev: 'Total will update when you're back online' is not displayed for send money in offline mode

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to web chrome
Go offline
Go to any chat
First request money in a different currency and not your default currency and notice that it displays 'Total will update when you're back online'
But now, send money with a different currency again (and not your default curency) and notice that 'Total will update when you're back online' is not shown while sending money. Now, if you go online, it actually updates the amount in your own default currency. Thus, it should have shown the text ''Total will update when you're back online' in the previous case while sending money in offline mode

Expected Result:
Total will update when you're back online' should also be displayed for send money in offline mode
Actual Result:
Total will update when you're back online' is not displayed for send money in offline mode
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Version Number: dev
Reproducible in staging?: n/a
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/236946601-782ede9d-5081-4e82-9790-09e19e33a737.mp4
Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683530506313509
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Dev: 'Total will update when you're back online' is not displayed for send money in offline mode
What is the root cause of that problem?
We are checking the variable shouldShowPendingConversionMessage in order to show the "Total will update...." message here:
https://github.com/Expensify/App/blob/5e69967c90456682a94d28dd2825d773fe851c88/src/components/ReportActionItem/IOUPreview.js#L216-L220
https://github.com/Expensify/App/blob/7fb641e058f792d2e6da62a72f2f3b25171b5416/src/components/ReportActionItem/IOUAction.js#L83-L93
At line 88, isMostRecentIOUReportAction is the latest CONST.IOU.REPORT_ACTION_TYPE.CREATE Or CONST.IOU.REPORT_ACTION_TYPE.SPLIT action is calculated here:
https://github.com/Expensify/App/blob/7fb641e058f792d2e6da62a72f2f3b25171b5416/src/libs/ReportActionsUtils.js#L84-L94
Because of that, we didn't calculate the latest action for CONST.IOU.REPORT_ACTION_TYPE.PAY request, that's why this message only shows when it's Split or Request action.
What changes do you think we should make in order to solve the problem?
Solution 1:
We can implement it similar with the way we implement the prop isMostRecentIOUReportAction, let call it isMostRecentIOUSendReportAction

we should update shouldShowPendingConversionMessage condition:

 if (
        !_.isEmpty(props.iouReport)
        && !_.isEmpty(props.reportActions)
        && props.chatReport.hasOutstandingIOU
        && (props.isMostRecentIOUReportAction || props.isMostRecentIOUSendReportAction)
        && props.action.pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD
        && props.network.isOffline
    ) {
        shouldShowPendingConversionMessage = IOUUtils.isIOUReportPendingCurrencyConversion(props.reportActions, props.iouReport);
    }

Update isIOUReportPendingCurrencyConversion function, because it's now only calculate the pending diff currency for type CONST.IOU.REPORT_ACTION_TYPE.CREATE. So the way we calculate the pendingRequestsInDifferentCurrency will look like this:

    const pendingRequestsInDifferentCurrency = _.chain(getIOUReportActions(
        reportActions,
        iouReport,
        [CONST.IOU.REPORT_ACTION_TYPE.CREATE, CONST.IOU.REPORT_ACTION_TYPE.PAY],
        CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD,
        true,
    )).map(action => action.originalMessage.IOUTransactionID)
        .sort()
        .value();
    // Pending deleted money requests that are in a different currency
    const pendingDeletedRequestsInDifferentCurrency = _.chain(getIOUReportActions(
        reportActions,
        iouReport,
        [CONST.IOU.REPORT_ACTION_TYPE.DELETE],
        CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD,
        true,
    )).map(action => action.originalMessage.IOUTransactionID)
        .sort()
        .value();

Update getIOUReportActions's params types, so we can pass the types as an array of actions like step 2:

function getIOUReportActions(reportActions, iouReport, types = [], pendingAction = '', filterRequestsInDifferentCurrency = false) {
    return _.chain(reportActions)
        .filter(action => action.originalMessage
            && action.actionName === CONST.REPORT.ACTIONS.TYPE.IOU
            && (!_.isEmpty(types) ? types.includes(action.originalMessage.type) : true))
        .filter(action => action.originalMessage.IOUReportID.toString() === iouReport.reportID.toString())
        .filter(action => (!_.isEmpty(pendingAction) ? action.pendingAction === pendingAction : true))
        .filter(action => (filterRequestsInDifferentCurrency ? action.originalMessage.currency !== iouReport.currency : true))
        .value();

And finally, remove the !isCurrentUserManager inside IOUPreview.

                    {props.shouldShowPendingConversionMessage && (
                        <Text style={[styles.textLabel, styles.colorMuted]}>
                            {props.translate('iou.pendingConversionMessage')}
                        </Text>
                    )}

Solution 2:
Update the isMostRecentIOUReportAction report ReportActionList props instead of creating a new props.

Update isMostRecentIOUReportAction props inside ReportActionList,mostRecentIOUSendReportActionId is the latest send report action.

isMostRecentIOUReportAction={reportAction.reportActionID === mostRecentIOUReportActionID || reportAction.reportActionID === mostRecentIOUSendReportActionId}

Do the step 2,3,4 in the  Solution 1

What alternative solutions did you explore? (Optional)
None.
Result:
https://user-images.githubusercontent.com/16502320/236990092-ae2648dc-f0a0-424c-ae59-df7364f0dc8c.mov

@mallenexpensify Yep, that makes sense. However, my perspective on this was, while you go online after sending the money in an offline mode, it actually updates and converts the currency as well as the amount. Thus, initially my idea was, at least it should have displayed something or alerted the user while sending money in an offline mode in a similar way how it does in the request money by displaying 'Total will update when you're back online' or any other text.
But if this was on purpose by the team and if it's not a bug, we can close this out then :smiley: :smiley:

Thanks @priya-zha , I'm going to close for now as it appears to be working as expected.


New branch Data pipeline

A new branch will be created for data pipeline from main branch. The branch will contain all the issue and commits regarding the Apache airflow.
New branch can be found here apache-airflow-pipeline
Strictly to follow

Request made for any changes in data pipeline needs to be done on the above-mentioned branch
No direct merge in main or in prod.

Done ! and  merged too


Added functionality to create a New Demandware Cartridge and link it with DWRE Server

Added following functionalities:

Create New DWRE cartridge with required directory structure
Auto-Upload the newly created cartridge to Sandbox
Auto-Import the newly created cartridge to atom workspace.

Great staff, I'll test and merge this


The parameter GEMM_PREFERED_SIZE is not set for Neoverse V1

Hello.
The parameter GEMM_PREFERED_SIZE is set for recent XEON and POWER CPUs, but no specific value is set for Arm CPUs in param.h. Isn’t it better to set the parameter, especially for CPUs with SIMD features?
If so, I would like to evaluate the appropriate value for Neoverse V1 using Graviton3E up to 64 threads.

Yes, this has not yet been explored for any of the SVE targets as far as I am aware - I'm not sure if it is as important for Arm hardware as it was for x86_64, but it is certainly worth a look.

Thanks for your comment.  I will add fix for this after evaluating preferable settings.


GH-4382 Fix usage of deprecated Jackson APIs

GitHub issue resolved: #4382
Briefly describe the changes proposed in this PR:
This PR fixes all use of currently deprecated Jackson APIs.

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[ ] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits where necessary
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

I think that maybe this should be targeted at develop instead of main since it's not strictly a bug fix.

@abrokenjester Is this ready to merge into main and be released in the next patch release?


Add Go client page

Fixes #1495

I recently set up everything to build go-duckdb with the latest version of duckdb locally on an AWS instance like this. Might it be interesting to include this?
Instance Information

c5.4xlarge
amd64, 30GB storage, Ubuntu (ubuntu-jammy-22.04, default AWS option)

Setup
sudo apt-get update
sudo apt install make
sudo apt install cmake
sudo apt install g++
sudo apt install golang-go

Optional (for faster builds)
sudo apt install ccache
sudo apt install ninja-build
export GEN=ninja

Prepare go-duckdb
Clone the latest go-duckdb and duckdb releases
git clone https://github.com/marcboeker/go-duckdb.git
cd go-duckdb
git clone https://github.com/duckdb/duckdb.git

Update the duckdb header file
cp duckdb/src/include/duckdb.h duckdb.h

Update the Makefile to avoid building with an official duckdb release, and instead use duckdb's cutting-edge version.
vim Makefile

remove the following line git clone -b v${DUCKDB_VERSION} --depth 1 https://github.com/duckdb/duckdb.git in the deps.linux.amd64: section

Build go-duckdb with the cutting-edge version of duckdb
make deps.linux.amd64
go build

Point an example application to the local go-duckdb module
Create an example application
cd ..
mkdir attach
vim attach.go

Copy-paste content into the file, and import marcboeker/go-duckdb. We will create a local replacement for this import.

Initialize the module and adjust the go-duckdb module path to a local version (../go-duckdb)
go mod init example/attach
go mod edit -replace marcboeker/go-duckdb=../go-duckdb
go mod tidy

Output: go: found marcboeker/go-duckdb in marcboeker/go-duckdb v0.0.0-00010101000000-000000000000

Run the example application with the new ATTACH IF NOT EXISTS functionality
go run .

Output: 2023/11/21 13:47:43 attached 5 files


[Docs] README: fix for link to quick start guide

Signed-off-by: leecalcote<EMAIL_ADDRESS>Description
This PR fixes #2029
Signed commits

[x] Yes, I signed my commits.

@Keenal, you might give this PR a review.


Add indexes to commonly queried fields

@webdevcody Hey!
Idea:
We should add indexes to table fields that are commonly queried on, and do not already have a unique, primary or composite index. This will allow for more scalable queries. It may also prompt people to think about indexing when they inspect and use the starter kit.
Scope:
I think adding indexes especially where there will be an enduring need for the field query regardless of how the "forkee" adapts the starter kit, will make the most sense to start. Examples of this might include:

accounts.userId
accounts.githubId
accounts.googleId
groups.isPublic
memberships.userId
....

Before adding these in, it would be good to conduct a brief analysis to identify fields where this does make sense, as well as identify fields that while are queried on, it might not make sense to apply an index.
What do you think? I would be happy to do that analysis and then submit a PR you agree it makes sense.
P.s. Needless to say – thank you for setting up this starter kit and your hard work!

I think it would be useful.  I don't think I invested too much time looking into performance.  I'd merge it if you work on it!


Not recognizing latest Git tag

I have project that I am packaging using setuptools-git-versioning based on Git tags.
I have a staging branch that is stable and a feature/myfeature branch created from staging.
Now staging branch has the existing tag v0.0.0rc1.
And I created a new Git tag on feature/myfeature branch, called v0.0.0b1. Note the this tag is created AFTER v0.0.0rc1 tag on the staging branch.
I run the command python3 setup.py sdist bdist_wheel on the feature branch, and the version of wheel file built is 0.0.0rc1 instead of 0.0.0b1. I am a 100% sure that I am running setup tools on the feature branch.
Here is the snippet for setuptools-git-versioning configuration in my setup.py file:
   version_config={         "template": "{tag}",         "dev_template": "{tag}",         "dirty_template": "{tag}",         "version_callback": None,         "version_file": None,         "count_commits_from_version_file": False,         "branch_formatter": None,     },      setup_requires=["setuptools-git-versioning"]
My issue here is that setuptools-git-versioning is NOT recognizing the latest Git tag, and I don't understand why.
I need help resolving this issue.

Upon further investigation, I realized it's because of the command used to retrieve latest git tag, git tag --sort=-version:refname --merged. This command is asking for tags in reverse lexicographical order and hence the result I am observing. Is there a way to provide an option to choose instead to get the chronological ordering of the tags and get the latest tag based on chronological order?

Hi.
Could you please check v1.6.0?

Yes, version v1.6.0 is working in chronological order for tags. Thanks.


Ts sdk

New pull request for typescript / javascript sdk. This is an abstract sdk, it's serverSentEventGenerator needs to be
extended by a concrete runtime. But all tests pass.
My next step is the node sdk, which I'd already written, so I just need to port to this new version, I'll push it to this branch later, but at least people can review the abstract class.

Agreed, looks great!

I've added a node impl, but I'm trying to make it cross-runtime. The readSignal works fine, but I havent yet found out the best method for the streaming. I need to read up on WritableStreams.

So I think I've managed to make it cross-runtime (it should even work in service workers). Had to make some changes to the sdk interface because of how js uses callbacks for everything. Now you need to call the static stream method on the class and pass it a function. The function will have access to the class and can do all the sdk methods. But I'm open to suggestions on how to do it better.
Now I'm struggling with getting vite to start a node server and I think my next step will be replacing vite with esbuild so the task build task can build the sdk at the same time.

Do you want us to approve where it's at, or wait for your esbuild changes?

No it can wait, I just pushed and gave an update to keep people in the loop. I'll call you if I struggle with esbuild.

@delaneyj can you review the changes to the build code ? I'm sure you have notes. Otherwise everything works on both deno and node. I'm writting docs next then we can merge.
I want to do a command line based test suite for sdks, but that's orthogonal.

Dont review the code too much yet, I'm still going through some minor fixes as I realize I missed a few things in the spec for events other then datastar-merge-fragments.


Select Instruments and Genres open multiple times in Search

If I tap twice on the Select Instruments/Select Genres buttons before the first selection list appears, another one appears.
See screen capture.

This has not been fixed


GCC 13 cstdint include

main with GCC 13:
/home/matt/src/elastix/Core/Kernel/elxlog.h:1:1: note: ‘uint8_t’ is def
ined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
  +++ |+#include <cstdint>
    1 | /*=============================================================
============

Thanks @thewtex So you think it's sufficient to just add an #include <cstdint> inside elastix/Core/Kernel/elxlog.h, to fix both this issue and issue #915 (enum usage)?

@N-Dekker that will help to fix this issue, but I think #915 is separate.


Management tooling - Backup/restore

Subissue of #117
evitaDB supports backing up and restoring catalogs. We want to have UI for it.  We want backup listing for each catalog where new backups can be created and old existing ones can be restored under new name. Also, in context of connection itself, there will option to import new catalog from external file.

Backup
Dialog window will take:

date of point in time which we want to backup
whether download WAL as well (disabled by default)

if true, while restoring newer history will be applied resulting in newest possible version of that catalog

Request will be added to the job listing #146 where it will be available for download.

Restore
Dialog window will accept file representing backed up version of a catalog.
Restoring request will be added to the job listing #146

Import from file

Implemented


Weird texture for ArchitecTHOR_SceneManipulation-v1 Env

I am testing demo_random_action using ArchitecTHOR_SceneManipulation-v1 env. The texture doesn't look good. Anyone has idea what I did wrong?
https://github.com/user-attachments/assets/af678cfb-96df-42a6-9b1c-4a90845e2df1
Also seems teleop doesn't support ArchitecTHOR_SceneManipulation-v1. The motion planner for "fetch" is missing. I tried ReplicaCAD_SceneManipulation-v1, and the error is the same. What modification should I do to add a new env/robot into teleop?

Currently we don't have easy to use teleop tools yet for mobile manipulation. It is something we will add in the future. It generally requires some engineering effort to essentially keyboard key presses to various actions.
As for the rendering, the AI2 THOR scenes do not have backfaces so you have to move inside the house to see inside it more clearly. If you click an object it will add transparency to it to show you selected it.
If you want a higher rendering quality you can turn on ray-tracing. Note that only ReplicaCAD and Robocasa scenes have tuned lighting. The AI2THOR scenes don't have lighting defined so it might not look that good unless you add it.


Suggest fix for buying multiple bots issues.

Items implementing ISalable in StardewValley return a getOne when the player purchases an item from the shop.
By creating SalableBot we can add this to the list of items to sell instead of a Bot instance, and on purchase it creates a new instance of a Bot instead of calling getOne which attempts to duplicate a Bot that already exists.
+Victory photo

.

This looks good!  I will need to study it a bit more and integrate it next week.  Thank you for submitting it!