Fails to delete completion stored on s3

Describe the bug
When trying to delete a task_completion that is on s3 it fails with a NotImplementedError
To Reproduce
Steps to reproduce the behaviour:

Have completions target storage set to s3
Create a completion for a task
Delete the completion
See error

Expected behavior
Expect the task_completion to be deleted
Error
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/label_studio/utils/misc.py", line 64, in exception_f
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/label_studio/blueprint.py", line 786, in api_completion_by_id
    g.project.delete_task_completion(task_id, completion_id)
  File "/usr/local/lib/python3.6/site-packages/label_studio/project.py", line 670, in delete_task_completion
    self.target_storage.remove(task_id)
  File "/usr/local/lib/python3.6/site-packages/label_studio/storage/base.py", line 474, in remove
    raise NotImplementedError
NotImplementedError

[2021-01-13 08:47:25,016] [INFO] [werkzeug::_log::122] <IP_ADDRESS> - - [13/Jan/2021 08:47:25] "DELETE /api/tasks/0/completions/1001 HTTP/1.1" 500 -

Environment (please complete the following information):

OS: Linux b425d69e6756 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 GNU/Linux
Label Studio Version: 0.9.0

Label studio doesn't support completion deletion for storages because it could be potentially danger for user data.

Label studio doesn't support completion deletion for storages because it could be potentially danger for user data.

In general, Label Studio is not intended to fully manage cloud storage - only "List/Read" and "Put" actions are allowed. It's better to rely on storage clients. We won't support this functionality, but I agree that we should better handle that exception at the moment.

In general, Label Studio is not intended to fully manage cloud storage - only "List/Read" and "Put" actions are allowed. It's better to rely on storage clients. We won't support this functionality, but I agree that we should better handle that exception at the moment.

Thank you for your responses!! It makes sense that LS doesn't take responsibility for that.

Thank you for your responses!! It makes sense that LS doesn't take responsibility for that.


VIDEO-7662: Publish snapshots to MavenCentral

Description
JFrog no longer supports publication of snapshots. This PR provides the changes needed to publish audioswitch snapshots to MavenCentral instead. I also took the opportunity to refactor the Circle CI configuration a bit.
Breakdown
Gradle changes:

remove references to artifactory
publish snapshots to maven central snapshots repository
remove obsolete jcenter from repositories

Circle CI changes:

refactor Circle CI config file to use commands and executors
add parameter for pre-release publishing to maven central
add parameter for disabling default CI workflow
add parameter and workflow for publishing a snapshot from any branch
add comments and do other minor refactoring in CI config

Other changes:

restore patch version number to 3, since that is the next version to be published
update README with info on how to reference maven central snapshots
add CHANGELOG entry
add contributor

Validation

Built locally
CI builds are green
Published a snapshot and validated that it can be consumed by following instructions in the readme

Additional Notes
I did not explicitly validate that publishing a release works as expected, however that will happen after this PR has been merged.
Submission Checklist

[x] The source has been evaluated for semantic versioning changes and are reflected in gradle.properties
[x] The CHANGELOG.md reflects any feature, bug fixes, or known issues made in the source code

What is ETA? I'm waiting for the new release that supports Android 12 devices. Thanks.


VW istio course - create VW branch

@linsun Would you review this PR and merge when you're good?

is this something empty?  File changed tab showed 0 changes.

Weird I can see the commits individually, but I see 0 changes showing also.

If you mark this reviewed, then I'm guessing the commits will roll in.


About support for Apple pencil(Version 3.5) When apple pencil is clicked on the scrollcontainer, it will become a slide

Godot version
3.5
System information
macos 13.0.1 (22A400)
Issue description
Godot exports the project to the iPad.
When you click on the list of iPad applications with an Apple pencil,
the list will have a little sliding effect.
scroll_deadzone has been set to 10.
Steps to reproduce
When you click on the list of iPad applications with an Apple pencil
Minimal reproduction project
N/A

Is this a list of applications in the Godot app?

Can you record a video of this occurring?

https://user-images.githubusercontent.com/5889641/216864635-b153e113-27f8-4f2f-94be-253bc8d7823c.mp4

It is a list in the godot app,
The control uses ScrollContainer and GridContainer.

Do I need to create another list.

These are the logs when clicking list with apple pencil:
2023-02-10 14:21:14.456031+0800 Hdd[55108:2402134] [InputEventMouseButton:28160]
2023-02-10 14:21:14.456099+0800 Hdd[55108:2402134] [InputEventMouseButton:28160]
2023-02-10 14:21:14.456135+0800 Hdd[55108:2402134] [InputEventMouseButton:28160]
2023-02-10 14:21:14.456169+0800 Hdd[55108:2402134] [InputEventMouseButton:28160]
2023-02-10 14:21:14.456747+0800 Hdd[55108:2402134] [InputEventMouseMotion:28168]
2023-02-10 14:21:14.456791+0800 Hdd[55108:2402134] [InputEventMouseMotion:28168]
2023-02-10 14:21:14.456857+0800 Hdd[55108:2402134] [InputEventMouseMotion:28168]
2023-02-10 14:21:14.456878+0800 Hdd[55108:2402134] [InputEventMouseMotion:28168]
2023-02-10 14:21:14.457280+0800 Hdd[55108:2402134] [InputEventMouseButton:28177]
2023-02-10 14:21:14.457320+0800 Hdd[55108:2402134] [InputEventMouseButton:28177]
2023-02-10 14:21:14.457357+0800 Hdd[55108:2402134] [InputEventMouseButton:28177]
2023-02-10 14:21:14.457393+0800 Hdd[55108:2402134] [InputEventMouseButton:28177]
These are the logs when you click the list by hand:
2023-02-10 14:21:02.142501+0800 Hdd[55108:2402134] [InputEventMouseButton:28124]
2023-02-10 14:21:02.142572+0800 Hdd[55108:2402134] [InputEventMouseButton:28124]
2023-02-10 14:21:02.142608+0800 Hdd[55108:2402134] [InputEventMouseButton:28124]
2023-02-10 14:21:02.142644+0800 Hdd[55108:2402134] [InputEventMouseButton:28124]
2023-02-10 14:21:02.143101+0800 Hdd[55108:2402134] [InputEventScreenTouch:28132]
2023-02-10 14:21:02.143125+0800 Hdd[55108:2402134] [InputEventScreenTouch:28132]
2023-02-10 14:21:02.143143+0800 Hdd[55108:2402134] [InputEventScreenTouch:28132]
2023-02-10 14:21:02.143161+0800 Hdd[55108:2402134] [InputEventScreenTouch:28132]
2023-02-10 14:21:02.143378+0800 Hdd[55108:2402134] [InputEventMouseButton:28141]
2023-02-10 14:21:02.143418+0800 Hdd[55108:2402134] [InputEventMouseButton:28141]
2023-02-10 14:21:02.143451+0800 Hdd[55108:2402134] [InputEventMouseButton:28141]
2023-02-10 14:21:02.143485+0800 Hdd[55108:2402134] [InputEventMouseButton:28141]
2023-02-10 14:21:02.143734+0800 Hdd[55108:2402134] [InputEventScreenTouch:28149]
2023-02-10 14:21:02.143757+0800 Hdd[55108:2402134] [InputEventScreenTouch:28149]
2023-02-10 14:21:02.143788+0800 Hdd[55108:2402134] [InputEventScreenTouch:28149]
2023-02-10 14:21:02.143807+0800 Hdd[55108:2402134] [InputEventScreenTouch:28149]

Does this happen in other programs as well? Does it happen only in the application or in the editor also?

Our application is only used on mobile platforms, so the pen we bought is only used on iPad and Android tablet, and PC has not been tested. If it is just a scrollContainer, you can click on the item above, and it will slide for a distance while clicking. If the scrollContainer is added to the scrollContainer, and then the item is added, the bottom scrollContainer is used to slide left and right to switch pages. At this time, the item cannot be clicked, only the sliding gesture can be recognized, just like in the video

Test0213.zip
I created an empty demo, only ScrollContainer and VBoxContainer. After adding Button, it is difficult to respond to the click event of Button on the iPad by using Apple Pencil. All of them respond to scrolling events

Understood, didn't understand that the pen does not click. But to clarify, this only happens with the Godot application, not other applications on the iPad?

Because the scroll event and click event of ScrollContainer are in conflict. If it is clicked, it will respond to the click event. If it is considered as scrolling, it will cancel the click response.
Other applications of Apple Pencil on the iPad are normal. The system settings of apps and other apps developed by us are normal. When other native applications click with apple pencil, there will be gesture events coming in, and godot app does not have gesture events coming in. The difference can be seen from the above log.

Use apple pencil to click. There is no InputEventScreenTouch event, but there is an additional mouse movement event InputEventMouseMotion

Thank you for clarifying, I don't have an iPad so I won't be able to help with this but this will help others to do so

Test0213.zip
I'm sorry! There was a problem with the demo just now. I rewrote it.
Demo is to create a new scrollContainer, then add another scrollContainer on it, and then add Buttons on the scrollContainer above, so that the button cannot respond to the click event after operation.

Sorry, I found that I can't click with apple pencil. It is due to a code problem that the deadzone of the above scrollContainer has not been set, so clicking it now has an effect.
The remaining problem is still on the ScorlContainer. After clicking with apple pencil, there will be a sliding problem, that is, some InputEventMouseMotion events are added, but the InputEventScreenTouch event is missing
thank you


[SITE REQUEST] ranobes

ranobes
**Does the host have more than 15 novels?  YES **
Did you try manual grabbing? YES
Website link: https://ranobes.net/

Added


Remove WeakRefStrings from REQUIRE

It doesn't seem to be loaded/used anywhere in the package

The error your branch rans into in CI seems to be unrelated to your changes, as I just reran the old master pipeline and it broke in the same way. That's probably due to this project not being touched in a while. Will try to look at what is going on later.

@quinnj sorry for the extreme delay in looking into this. I'll merge this now because #16 should fix the current CI issue. This package has been basically abandoned. Has it been useful for you lately? If so, that changes things and gives a reason to port it to julia 1.0.


Add wmi integration test and fix filter sampler

The changes were introduced in https://github.com/DataDog/integrations-core/pull/5510
The tests were introduced in https://github.com/DataDog/integrations-core/pull/5859
This caused _query method to throw an index out of range exception on wmi_event_log integration. When throwing the exception the sampler thread dies without signaling the parent that keeps waiting forever.
This branch addresses performs changes:

Fixes compatibility with the win32 filters
Adds specific test and removes wrong one
Captures the exception so the thread does not get blocked in that case
Adds an integration test to win32 that was hanging without the prior fixes

Can you share the stacktrace ? I struggle to understand where the error was raised.
Also should we update the parent in order to watch for unexpected death of the sampler thread?

Can you share the stacktrace ? I struggle to understand where the error was raised.

Line 405 of sampler.py:
                if isinstance(value, (tuple, list)):
                    oper = value[0]
                    value = value[1]  # <---- offending line

called from _query
    def _query(self):
        try:
            formated_property_names = ",".join(self.property_names)
            wql = "Select {property_names} from {class_name}{filters}".format(
                property_names=formated_property_names, class_name=self.class_name, filters=self.formatted_filters
            )  # <---- causing index out of range exception

called from _query_sample_loop():
while True:
     ...
            self._current_sample = self._query() # <---- dies
            self._sampleCompleteEvent.set()  # <--- never gets called

So sample(), that is called from win32_event_log's check method, gets stuck:
    def sample(self):
        """
        Compute new samples.
        """
        self._sampling = True
        self._runSampleEvent.set()
        self._sampleCompleteEvent.wait()   # <---- never comes back
        self._sampleCompleteEvent.clear()
        self._sampling = False

Also should we update the parent in order to watch for unexpected death of the sampler thread?

how?

Also should we update the parent in order to watch for unexpected death of the sampler thread?

how?

Can we keep a ref to the created thread and use https://docs.python.org/3.8/library/threading.html#threading.Thread.is_alive ?
Having the whole agent stuck because of an exception is bad, we may encounter more exceptions in the future and I think we should make sure that we can limit the error to the check itself.


Missing repositories

https://github.com/N1ght-Owls/reposi/blob/e675e438fd73dde285ccf1cbb6fc9b1132631f54/app.py#L132
I faced this problem while using Github API too. I was not able to get more than 100 repos even after providing the param, but I was able to get 100 repositories repeatedly. Some of my repositories are missing here, possibly its because the next 100 repositories are not received

Ok, we will update the backend tomorrow but my last commit (https://github.com/N1ght-Owls/reposi/commit/55180e9c64046b425ae95fbff75a526168271205) fixes this. It will make page load a bit slower if you have a huge amount of repos though so we will need to allow the user to limit the number of repos.


Crashes if trying to load with a server

Describe the bug
[08:31:55] [main/ERROR]: Failed to start the minecraft server
java.lang.RuntimeException: Could not execute entrypoint stage 'main' due to errors, provided by 'yigd'!
at org.quiltmc.loader.impl.entrypoint.EntrypointUtils.lambda$invoke0$2(EntrypointUtils.java:62) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.util.ExceptionUtil.gatherExceptions(ExceptionUtil.java:33) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.entrypoint.EntrypointUtils.invoke0(EntrypointUtils.java:60) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.entrypoint.EntrypointUtils.invokeContainer(EntrypointUtils.java:45) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.entrypoint.EntrypointUtils.invoke(EntrypointUtils.java:32) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.game.minecraft.Hooks.startServer(Hooks.java:62) ~[quilt-loader-0.16.1-beta.3.jar:?]
at net.minecraft.server.Main.main(Main.java:101) [server-intermediary.jar:?]
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:577) ~[?:?]
at org.quiltmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:423) [quilt-loader-0.16.1-beta.3.jar:?]
at net.fabricmc.loader.launch.knot.Knot.launch(Knot.java:76) [quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.launch.knot.KnotHelper.launchServer(KnotHelper.java:32) [quilt-loader-0.16.1-beta.3.jar:?]
at net.fabricmc.loader.launch.knot.KnotServer.main(KnotServer.java:23) [quilt-loader-0.16.1-beta.3.jar:?]
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:577) ~[?:?]
at net.fabricmc.loader.launch.server.FabricServerLauncher.main(FabricServerLauncher.java:62) [quilt-loader-0.16.1-beta.3.jar:?]
Caused by: java.lang.NoClassDefFoundError: net/minecraft/class_437
at com.b1n_ry.yigd.Yigd.onInitialize(Yigd.java:210) ~[youre-in-grave-danger-1.3.2.jar:?]
at org.quiltmc.loader.impl.game.minecraft.Hooks.lambda$startServer$2(Hooks.java:62) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.entrypoint.EntrypointUtils.lambda$invoke$0(EntrypointUtils.java:32) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.entrypoint.EntrypointUtils.invoke0(EntrypointUtils.java:58) ~[quilt-loader-0.16.1-beta.3.jar:?]
... 13 more
Caused by: java.lang.ClassNotFoundException: net.minecraft.class_437
at jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) ~[?:?]
at jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?]
at net.fabricmc.loader.launch.knot.KnotClassLoader.loadClass(KnotClassLoader.java:158) ~[quilt-loader-0.16.1-beta.3.jar:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?]
at com.b1n_ry.yigd.Yigd.onInitialize(Yigd.java:210) ~[youre-in-grave-danger-1.3.2.jar:?]
at org.quiltmc.loader.impl.game.minecraft.Hooks.lambda$startServer$2(Hooks.java:62) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.entrypoint.EntrypointUtils.lambda$invoke$0(EntrypointUtils.java:32) ~[quilt-loader-0.16.1-beta.3.jar:?]
at org.quiltmc.loader.impl.entrypoint.EntrypointUtils.invoke0(EntrypointUtils.java:58) ~[quilt-loader-0.16.1-beta.3.jar:?]
... 13 more
Expected behavior
A normal server start.
Desktop:

OS: Windows
Minecraft Version: 1.16.2
Version: 1.3.2

Additional context
I'm using the quilt server jar. Not sure if it only applies to that.

Update: same error on 1.3.5

Update: Also happens on fabric server jar.

I just want to make sure wheb using 1.3.5 you are getting the same crash, and not the one in #46? If it's the same I'll check on it but if not you can read what I told that guy and do the same you too

I've already tried it and yes it's the very same error as seen above.

Ok great just wanted to make sure.
Also, I just noticed now, are you trying to run this version on a 1.16.2 server? Because if that's the cause of this issue then you'll justhave to try a 1.16.5 version of the mod. That version will not include as many features, but most of them will be there.
Anyway I strongly believe this is not the same error as you get in version 1.3.5, since I fixed this error in the 1.3.3 version. If you could send the crash report from version 1.3.5 that could help me further to find the problem (unless you're playing at 1.16.2, in which I'm pretty sure that won't help)

Might've been my typo sorry. I'm running 1.18.2 not 1.16
latest.log

Thanks. This does very much look like #46 actually. If you want I can fix the config file for you, or you can try to check the wiki to fix for yourself or just delete the config file and recreate it as you want it

That's strange :o I could've sworn I tried deleting the config several times now. well either way it's working now thanks!


Minor: remove useless clone based on Clippy

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Thanks @Weijun-H


import takes very long

I have a PortfolioPerformanceData.xml file which is around 60MB. It takes at least 5min to load.
Can I speed this up?

Fixed with version 0.2.0. In the examples folder is a script that can be used to test. Should now take far less than 1 min.


Update layers/meta-balena digest to c6a25b2

This PR contains the following updates:

Package
Update
Change

layers/meta-balena
digest
2e4f0c9 -> c6a25b2

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@resin-jenkins test this please

@balena-ci I self-certify!

@resin-jenkins add to whitelist

@resin-jenkins test this please

lgtm


Modal is not working

Issue description
I try to use Modal in reactstrap and its not working
Error message in console
Uncaught TypeError: ReactDOM.createPortal is not a function
Unhandled promise rejection TypeError: ReactDOM.createPortal is not a function

Code
<div>
  <Modal isOpen={true}>
   <ModalBody>
     hai
   </ModalBody>
 </Modal>
</div>

Upgrade react to 16

@TheSharpieOne Thank you so much!!

I am having react 16.5.2, reactDOM also the same version, but still got the same error

If you are getting that ReactDOM doesn't have createPortal and you are 100% certain that you are using react-dom 16.5.2, then you may want to file an issue with react itself since that function should be defined per their API docs.


Not the most accurate.

When i saw this i was like wait whats going on, there were no real instructions on how to use it. But once I figured out what was on, I quickly realized it wasn’t that accurate.
I even used my metronome with it to be sure i was tapping with consistency/on beat. But regardless of the tempo i was goin at the tempo seem to rise regardless on the app.

If you can get the tempo to be accurate, you on to something great. Keep going.

Thanks for taking a look. Do you remember about what you had the metronome set at and about what the tempo read on the site? Knowing the direction and magnitude of the error might help diagnose it. There are probably practical limitations to accuracy from relying on browser API's for time and click information, but I wouldn't be surprised if there is low-hanging fruit to improve the accuracy from where it is now.

No problem. I was kind of excited when i ran accident it. And i had my
metronome in my DAW set to 120 bpm, and the tempo online when be at 120 for
about 8 beats or so and then it would continue to increase going up to
about 150 or so. I hope this feed back helps a lot.
On Sat, Nov 20, 2021 at 10:57 AM Blake Johnson @.***>
wrote:

Thanks for taking a look. Do you remember about what you had the metronome
set at and about what the tempo read on the site? Knowing the direction and
magnitude of the error might help diagnose it. There are probably practical
limitations to accuracy from relying on browser API's for time and click
information, but I wouldn't be surprised if there is low-hanging fruit to
improve the accuracy from where it is now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/voteblake/bpm-is/issues/2#issuecomment-974670642, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWSQVAKGGR3XCZ27N5U443LUM7APTANCNFSM5IMQBB6A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Appreciate it - that definitely sounds wrong. I may not be able to get it 'perfect' but the tempo running away like that isn't even usable. I forgot to ask, which browser was this in? Since I'm relying on browser API's via WASM this behavior might be browser-specific. I'm off work all next week and will be able to poke at this a bit. Knowing the browser might help me reproduce and troubleshoot.

Yes exactly like if it at least stuck around the 120-130 that would be a
whole different world. I was using googles chrome browser on my iphone xs
and on my ipad 5th generation same browser on both.
On Sat, Nov 20, 2021 at 11:40 AM Blake Johnson @.***>
wrote:

Appreciate it - that definitely sounds wrong. I may not be able to get it
'perfect' but the tempo running away like that isn't even usable. I forgot
to ask, which browser was this in? Since I'm relying on browser API's via
WASM this behavior might be browser-specific. I'm off work all next week
and will be able to poke at this a bit. Knowing the browser might help me
reproduce and troubleshoot.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/voteblake/bpm-is/issues/2#issuecomment-974676547, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWSQVAMPBNRJPPUSXPF3TBTUM7FODANCNFSM5IMQBB6A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Fixed BPModLoaderMod RegisterBeginPlayPostHook

Description
I noticed we're only checking for the class name ModActor_C inside RegisterBeginPlayPostHook rather than the full class path so I added a check against the full class path which will only trigger PostBeginPlay once for the ModActor that fired BeginPlay.
The boolean for Log was accidentally placed inside string.format so it'd still be printing PostBeginPlay not valid with VerboseLogging set to false.
Fixes #433, #91
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Tested on 4.27 and 5.1 with multiple ModActors.
Checklist

[x] I have performed a self-review of my own code.
[x] I have added the necessary description of this PR to the changelog, and I have followed the same format as other entries.

Seems this should fix #433.
It might also at least partially fix #370, and I don't understand how the PreBeginPlay could possibly be duplicated, maybe a misunderstanding of some sort.
#91 was probably also this same problem.

Seems this should fix #433. It might also at least partially fix #370, and I don't understand how the PreBeginPlay could possibly be duplicated, maybe a misunderstanding of some sort. #91 was probably also this same problem.

I'm not certain what the issue with PreBeginPlay would be as it is working perfectly fine for me and only fires once per ModActor. It does sound like a misunderstanding to me.

Works fine for me.


add fid call for the benchmarks

@CharlyCst The branch is wip, because I need to test it, but you can already review the code :)


Added FRAGCOORD to spatial light shader

Fix #20341

Looks good.
If others might be wondering like I did, FRAGCOORD was already exposed for fragment shaders in both CanvasItem and Spatial shaders, and for light shaders in CanvasItem shaders - this fixes the missing Spatial binding.

Cherry-picked for 3.0.7.


research db options

look into what options Azure provides for databases and which ones work best. In particular, MongoDB has documentation (see issue #2 ) and may be a good place to start, though it's up to the dev.

See #2


Can't Import Sass Files

I used bower to install the material-colors dependency. The dist/ folder contains a file with .scss and .sass. When attempting to use sass to import the file like so:
@import '../../bower_components/material-colors/dist/colors.scss';

I get the following error:
Error: It's not clear which file to import for '@import "../../bower_components/material-colors/dist/colors"'.
       Candidates:
         ../../bower_components/material-colors/dist/colors.scss
         ../../bower_components/material-colors/dist/colors.sass
         ../../bower_components/material-colors/dist/colors.css
       Please delete or rename all but one of these files.

Can we not rename or move these files so we can import them appropriately with SASS?

I don't think this is an issue of this module but the tool that threw the error. What tool do you use? You can contact the maintainers of it about this problem.


[AIRFLOW-XXX] Add Betterment to companies list

Jira

No Jira issue. Add Betterment to companies list.

Description

This PR adds Betterment to the companies list in the README.md.

Tests

No tests required. No code changes.

Documentation

No code changes.

Code Quality

No code changes.

+1.  Looks good.  Thanks.


🔖(minor) bump release to 6.9.0

Changed

Upgrade ansible to 5.2.0

Fixed

Kibana: fix configuration to load balance traffic upon replicas

Bumping the minor version just because a dependency has been updated, sorry but I disagree.

:thinking:

Ansible is the core dependency of the whole thing,
Patch releases are supposed to be bug fixes (see semver spec)

Ansible is the core dependency of the whole thing,

The core dependency is docker, not Ansible. The whole is application is run in a container so there is no effect when you change a dependency.

Patch releases are supposed to be bug fixes

This is why I think it should be the version 6.8.2 and not 6.9.0

Docker is a way to ease running Ansible. Saying so is similar to saying that Marsha is not a Django project!
I don't get your point: upgrading Ansible is not a bug fix. :thinking:


Add mTLS Authentication

We need to support "service accounts". For example, the kubernetes cluster reconcile needs to poll the region service to await identity and possibly network provisioning. It can also replace event based clean up with something more resilient.
To that end the client service needs to be issued an oauth2 access token to be accepted by the resource server. Luckily for us we can use mTLS: https://datatracker.ietf.org/doc/html/rfc8705
Identity needs to:

enable optional client certificates at the ingress level

further to this is needs a method to get the client certificate as part of the HTTP headers https://kubernetes.github.io/ingress-nginx/examples/auth/client-certs/
helm charts need to support root CA generation and rotation, possibly in core?

implement x509 client IDs with a registered DN, this can allow us to fill in userinfo for auditing
certificate binding of access tokens

additional client certificate fields in token introspection

Client servers need to:

create an x509 certificate pair

CA can be specified as an in-cluster resource, or be imported, probably a copy of what's in core already for ingress self-signed CA management

add the certificate to all outbound clients
do an mTLS authentication against identity to get a token before calling a resource server, where a user token is no available (typically kubernetes controllers)

Resource servers need to:

enable optional mTLS
check the client cert against the introspection hash, if present, to authorise the request

From a UX perspective, it's really annoying to have a popup asking for a client certificate. We should also add mTLS aliases to OIDC servidce discovery, and make use of them in all client services rather than the defaults. This removes the need for optional client certificates.

Fixed by #107


Added effiicient implementation of inversion_count algorithm named as inversion_counts.cpp

Description of Change

Checklist

[x] Added description of change
[x] Added file name matches File name guidelines
[x] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Hi @Panquesito7 after doing 7 commits, my code only fails for windows-latest, can you please guide me how to resolve that.

Hi @Himalay12 I recently saw in your submission all the checks were successful, great job. Can you pls tell me why my compile check is always failing for windows-latest? I have done many attempts but I am not able to figure out what I am doing wrong

I have not made any pr for inversion count.
On Thu, Nov 5, 2020, 15:29 Amit Padaliya<EMAIL_ADDRESS>wrote:

Hi @Himalay12 https://github.com/Himalay12 I recently saw in your
submission all the checks were successful, great job. Can you pls tell me
why my compile check is always failing for windows-latest? I have done many
attempts but I am not able to figure out what I am doing wrong
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TheAlgorithms/C-Plus-Plus/pull/1424#issuecomment-722272766,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMX6C5KBWPP5QEFBNHWEJLTSOJZRDANCNFSM4TKD3IVQ
.

@Himalay12, yes you did not take any pull request for inversion_counts. I saw your pull request for quicksort. I just want to know did you do any additional things for the windows compile check?

No, i did not do any additional things for windows. I used to compile first
in editor then made pr. You should try to compile with gnu compiler.
On Thu, Nov 5, 2020, 15:48 Amit Padaliya<EMAIL_ADDRESS>wrote:

@Himalay12 https://github.com/Himalay12, yes you did not take any pull
request for inversion_counts. I saw your pull request for quicksort. I just
want to know did you do any additional things for the windows compile check?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TheAlgorithms/C-Plus-Plus/pull/1424#issuecomment-722282852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMX6C5LMIMLBYHYCZKDZEETSOJ3V5ANCNFSM4TKD3IVQ
.

@Himalay12  I have compiled the code by g++. Any idea, why it might not be passing still on windows, does it have something to do with a filename or anything else?

I don't have any idea. You can search on google. Might get help from there.
On Thu, Nov 5, 2020, 16:32 Amit Padaliya<EMAIL_ADDRESS>wrote:

@Himalay12 https://github.com/Himalay12 I have compiled the code by
g++. Any idea, why it might not be passing still on windows, does it have
something to do with a filename or anything else?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TheAlgorithms/C-Plus-Plus/pull/1424#issuecomment-722305911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMX6C5PMLAW6J7QJKFP6L2TSOKA35ANCNFSM4TKD3IVQ
.

@Himalay12 I have done many searches on google. But couldn't find out what is the issue

Hi, @Panquesito7 I have followed all the guidelines and improved my contribution from before. If you find any faults, pls inform me.


Switch to using EIP712 for the signed data

Instead of the current signed payload, switch to using the newly finalized EIP712 standard.
Here is a good Solidity example to follow:
https://github.com/ethereum/EIPs/blob/master/assets/eip-712/Example.sol

This work is ongoing on the branch eip712. I will also add improvements and suggestions from ConsenSys Diligence.

This work has now been merged into v2.0.0.


Add support for cronjob extractor application nodes

What about a test?

it's included in the extractor plugin

What about a test?

it's included in the extractor plugin

But there should be one here as well

But there should be one here as well

hm I think it's already covered. What do you think I should test here?

But there should be one here as well

hm I think it's already covered. What do you think I should test here?

That an application is created from a cronjob


Design System - Featured Card Header Height

The height of the Featured Card's Header should be 48px, with 16px top and bottom padding.
Thx,
Ismael

Let's avoid adding a fixed height on the header to compensate for longer titles or screen sizes where titles may break into multiple lines. We can move forward with adjusting the padding.

@RachelRVasquez
The padding and line-height should equal 48px (for a single line title).  We agree that the solution is not to declare a fixed height.
cc @jdrf-digitaldesigner

Merged. @jdrf-digitaldesigner @pmmck Please review.

The Featured Cards' Headers still show up as 41px high. Thx

Merged. @jdrf-digitaldesigner @pmmck Please review.

Almost. It now comes up at 49px

@jdrf-digitaldesigner it appears the border is causing the additional pixel. When I inspect the element and apply a value of 0, I get 48px tall. Thoughts?

@jdrf-digitaldesigner
@briansaycocie 's answer seems completely within the realm of reason and acceptability.

That makes, but could we place it along the bottom edge of the cell, instead of outside? We could use this as a convention for all Dividers.

@jdrf-digitaldesigner @pmmck I think it comes down to if this is possible with how we've integrated with Bootstrap. If there's a convention in Bootstrap that we're following - then the answer is no. But if we're doing this "because" and Bootstrap has the ability to allow us to implement your suggestion, then we should follow your suggestion.
cc @briansaycocie

Understood. Let's keep them at 49px. Thx!


Firefox Developer Edition Label

Did not exist... so I made one...
firefox_dev)
name="Firefox Developer Edition"
type="dmg"
downloadURL="https://download.mozilla.org/?product=firefox-devedition-latest-ssl&os=osx&lang=en-US"
firefoxVersions=$(curl -fs "https://product-details.mozilla.org/1.0/firefox_versions.json")
appNewVersion=$(getJSONValue "$firefoxVersions" "LATEST_FIREFOX_DEVEL_VERSION")
expectedTeamID="43AQ936H96"
blockingProcesses=( firefox )
printlog "WARNING for ERROR: Label firefox and firefox_intl should not be used. Instead use firefoxpkg and firefoxpkg_intl as per recommendations from Firefox. It's not fully certain that the app actually gets updated here. firefoxpkg and firefoxpkg_intl will have built in updates and make sure the client is updated in the future." REQ
;;

Fixed with #838 in 10.3


Error Messages & Feedback Improvments

Show more precise error messages, for example when a resource cannot be loaded, or when a resource is created.
Error messages should be enriched by the API error response.
Errors for sparql and elestic search queries should provide relevant feedback from the API response.
Error messages should be managed in a way they don't clutter the UI.
feedback as provided from: @annakristinkaufmann, @pafonta , @jonathanlurie

Thanks for taking into account our feedback.
I am available for user acceptance testing.


Add wrapperContainer option

This PR adds an wrapperContainer option.
With this options you can specify via an query selector where the select markup should be rendered.
Usage
<select id="select"></select>

new TomSelect('#select',{
	wrapperContainer: '#test-wrapper',
	options: [
		{id: 1, title: 'DIY', url: 'https://diy.org'},
		{id: 2, title: 'Google', url: 'http://google.com'},
		{id: 3, title: 'Yahoo', url: 'http://yahoo.com'},
	]

The select and the dropdown markup will now be a child from div#test-wrapper.
But why do you need this?
Good that you ask!
We want to implement the tom-select in our backend-rendered application that updated the Frontend Markup with DOM-Diffing.
The Problem with the current implementation is, that the auto-generated wrapper will be attached after the select and when the diff occures it will be removed.
If we could specify an seperate DOM element we could tell the "Differ" to ignore that element and everything would work.
Additionally, every empty line with spaces and trailing line spaces are removed... Sry for that, the IDE has done this automatically. I tried to commit my changes without the style fixes but it reapplied it again on save 🙈
And Additionally for the addition, I implemented no tests for that... I have never worked on a JS/TS project and don't know how and where to add this... but if you tell me where and how I will add them too 😀

Why not just move it after initialization?
var ts = new TomSelect('#select');
document.getElementById('test-wrapper').append(ts.wrapper);

Hmm... Yes this would work.
But how many other users know this?

How many of the users who might need this won't either come up the the solution on their own or find this pull request?
Not sure, but I suspect it's a pretty small number.
Also, the list of settings in TomSelect is already long and I don't think we need to add another one (adding 7 lines of code) when the alternative is a single line of code.


Treating scalars implicitly as collections doesn't fully work with custom objects ([pscustomobject])

Treating scalars as if they were collections is a powerful feature that eliminated many bugs when it was introduced in PSv3: it means that even a single object returns meaningful values for .Count and .Length and allows indexing with [0].
Unfortunately, not all scalar objects behave this way, a notable exception being custom objects ([pscstomobject]), such as the instances created by Select-Object.
The problem is the absence of the .Count / .Length properties, but note that indexing custom objects with [0] works.
I wonder if there are other cases where cmdlets return objects (other than [pscustomobject] instances) that behave the same way.
Steps to reproduce
$null.Count
(Get-Item /).Count
(Get-Item / | Select-Object Name).Count  # !! produces no output
([pscustomobject] @{ foo = 'bar' }).Count # !! produces no output

Expected behavior
0
1
1
1

Actual behavior
0
1

^ 3rd and 4th command didn't produce output, because the implicitly and explicitly created [pscustomobject] instances have no .Count and .Length properties.
Environment data

PowerShell Core v6.0.0-alpha (v6.0.0-alpha.18) on Darwin Kernel Version 16.5.0: Fri Mar  3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64

It is behavior of pscustomobject:
([PSCustomObject]@{q=1}).Count
<empty>

([PSObject]@{q=1}).Count
1

@iSazonov
Thanks for the clarification - that simplifies the issue.
I've updated the title and the initial post accordingly.
It is not a question, however, it is an inconsistency that in my estimation is a bug.

Where can I start?

@lzybkr Could you please help - where is the magic code?

I think the magic code is here but I'd need to debug to see what's going wrong because I don't see the bug with code inspection.

The code isn't called at all 😕

@iSazonov - I don't normally write code that isn't called :)  It is possible that the code I pointed to isn't reachable for pscustomobject, but it is definitely reachable.
I will also point out - most of the code in binders.cs is generating code for an operation which is cached, so if some binding happened before you set a breakpoint, you'll never hit it again. For example, if you attach after startup, it's possible loading a module or even evaluating your prompt hit the code and you won't hit it again.
Starting the process under the debugger helps, or you can resort to adding some trace output or a message box so you can attach and debug.

😄 Yes, I meant pscustomobject context. And yes, it is cache - after first call the code isn't called for "Count".
I discover a difference in GetPSMemberInfo in line

([PSObject]@{q=1}).Count - adapterSet is DotNetAdapter and canOptimize is true
([PSCustomObject]@{q=1}).Count - adapterSet is PSObjectAdapter and canOptimize is false

If I change  canOptimize to true in debuger I get right output - Count = 1.
I don't know that is right fix.

That is not the right fix.
I think the right fix is to change PSGetMemberBinder.GetAdaptedValue - before the check at the end to throw PropertyNotFoundException, check it the member name is Count and just return 1.

First part was fixed - ([pscustomobject] @{ foo = 'bar' }).Count returns 1.

@lzybkr I again don't know where right fix is for Foreach/Where.
I found that if I changed canOptimize to true in the line  the ([PSCustomObject]@{q=1}).Foreach({$_}) works due to the line. Also we have a special case for $null.Where in the line
Could you please help?

@iSazonov - the change will be similar to what you did for Count, but it will be in PSInvokeMemberBinder.InvokeAdaptedMember and would return an empty Collection<object> in both cases.


PublicClientApplication.logout should be able to log the user out without interaction

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Description
When the logout function is called, the user is redirected to a page which asks them to select which account they want to log out of. They have to make a selection even if they're only logged in to one account. I tried giving the logout function an EndSessionRequest object with the account parameter populated but that doesn't bypass the account selection either. It'd be a cleaner user experience if the user didn't have to take this seemingly unnecessary extra step.
Source
    const logoutRequest: EndSessionRequest = { account };
    await msalApplication.current.logout(logoutRequest);

[ ] Internal (Microsoft)
[ ] Customer request

@k-mehta The account object you provide to the logout function is used to clear local cache, it is not used to tell the server who to sign out. In order to sign the user out on the server the redirect to the sign-out screen is required. Without this redirect your user could sign back into your application without providing credentials again as their server session would remain active. There is currently no way to bypass the account selection screen and this is not something MSAL controls. We've heard this feedback before and we've passed it along to the server team but it's ultimately their decision whether or not they'll pick it up.
If you don't care about signing the user out of the server you can pass a callback that returns false to onRedirectNavigate on the logout request. This will skip the redirect to the server but will leave the server session active.
We'll work on improving the documentation around this so it's more clear why this is required.


Installation

Describe the bug
I tried to install MM following the instructions in the manual (make build folder, ccmake ../, ** ), but it didnt work, because of the following error:
core/src/LuaAPI.cpp:21:10: fatal error: filesystem: Datei oder Verzeichnis nicht gefunden
#include
It seems that a specific version of gcc or something is required. In the manual, it says it was tested with gcc 5.4.0. All the prerequisites listed there are installed and up to date. My Linux-Distro in Ubuntu 18.04 with gcc 7.5.0.
Are there any specific C++ standards (e.g. c++-17) or gcc versions required and if so, do you know how I can set them?
Hope, you can help me and thanks in advance!
Best regards
Simon
** the installation instructions on the main page didnt work because cmake needs at least one argument ;) i think it should be cmake .. but this didnt work either but threw an error (require_external etc.)
PS: Please update your installation manual if not up-to-date ;)

Hello Simon,
Thank you for pointing this out. We are sorry that the installation instructions are not up to date. This research software is constantly evolving and changes faster than we are able to maintain the manual. ;-) This is a detailed installation instruction for linux which will work with the current version:
$ mkdir megamol
$ git clone https://github.com/UniStuttgart-VISUS/megamol.git megamol/
$ cd megamol
$ mkdir build
$ cd build
$ cmake ..
$ ccmake .

Configure using 'c' ('e' to exit configure menu) and then 'g' to generate and exit cmake
$ make && make install

$ cd install/bin
$ ./megamol.sh ../examples/testspheres_megamol.lua
An update of the manual will follow shortly.
Please let us know if you face any further difficulties!
Best regards,
Matthias

Hello Simon,
Thank you for pointing this out. We are sorry that the installation instructions are not up to date. This research software is constantly evolving and changes faster than we are able to maintain the manual. ;-) This is a detailed installation instruction for linux which will work with the current version:
$ mkdir megamol
$ git clone https://github.com/UniStuttgart-VISUS/megamol.git megamol/
$ cd megamol
$ mkdir build
$ cd build
$ cmake ..
$ ccmake .

Configure using 'c' ('e' to exit configure menu) and then 'g' to generate and exit cmake
$ make && make install

$ cd install/bin
$ ./megamol.sh ../examples/testspheres_megamol.lua
An update of the manual will follow shortly.
Please let us know if you face any further difficulties!
Best regards,
Matthias

Hi,
thank you very much for your immediate help! Unfortunately, as I pointed out before, cmake .. didn't work. I updated my distro to Ubuntu 20 and now it works. As I guessed, it seems to be a problem with the gcc version. Mine was 7 but at least 9 (or maybe 8?) is required. Here is my approach:

Make sure to meet the installation requirements; tested with:

$ cat /proc/version
Linux version 5.4.0-65-generic (buildd@lcy01-amd64-018) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021

Clone git repository:
git clone https://github.com/UniStuttgart-VISUS/megamol.git

Create build folder and change directory:
cd megamol && mkdir build && cd build

Prepare building process
ccmake ..

Configure with c and generate build files with g

Build MegaMol:
make

Go and get some coffee cause building takes some time...

Install MegaMol:
make install

Test it by running:
cd install/bin && ./megamol.sh ../examples/testspheres_megamol.lua

In the manual it says that the OSPRAY plugin is not installed by default. Do you know how I can install/enable and test it?
Best regards,
Simon

Enabling BUILD_OSPRAY_PLUGIN_PLUGIN will allow the building of this plugin in MegaMol.
However, CMake will ask you to provide a path to an already installed OSPRay.
You can either get it from here https://www.ospray.org/ or fetch it from their Github repo.
If you build OSPRay yourself, make shure to enable the installation of externals in its CMake.
Otherwise MegaMol will complain about missing TBB and Embree.

Thanks for your help. Unfortunately it doesnt really work. I downloaded Ospray from the webpage as precompiled 64-bit package (ospray-2.4.0.x86_64.linux.tar.gz). After invoking ccmake .. , I enabled the BUILD_OSPRAY_PLUGIN_PLUGIN and set the Variable ospray_DIR to the folder in which the cmake files of Ospray are located (/home/.../ospray-2.4.0.x86_64.linux/lib/cmake/ospray-2.4.0). The build files could be generated but make leads to the following error:
[ 72%] Building CXX object plugins/OSPRay_plugin/CMakeFiles/OSPRay_plugin.dir/src/AbstractOSPRayRenderer.cpp.o
plugins/OSPRay_plugin/src/AbstractOSPRayRenderer.h:16:10: fatal error: ospray/ospray.h: Datei oder Verzeichnis nicht gefunden
   16 | #include "ospray/ospray.h"

Do you have any idea how to solve it?

I forgot to mention that OSPRay 2.x support will come with #681.
You have to use OSPRay 1.8.5 for now.

Ok, good to know! Now it works (at least the testspheres_megamol.lua without ospray). When I tried the ospray spheres, it doesnt work (of course not...)
./megamol.sh ../examples/ospray/testspheres_ospray.lua
1|[GUI] GUIView module can only be used with mmconsole frontend.
./mmconsole.sh ../examples/ospray/testspheres_ospray.lua
doesnt open any window...
Furthermore, the paths to the lua files must be absolute or relative to the megamol.sh file location. That means it is not possible to create an alias to the megamol.sh file and run the command in an arbitrary folder (eg. ../bin/megamol.sh testspheres_megamol.lua in the examples folder).

Using the old frontend mmconsole, projects have to be loaded with the '-p' option:
./mmconsole.sh -p ../examples/ospray/testspheres_ospray.lua

Just a final thought on the first issue: The recently required full std::filesystem functionality is only available since gcc 8 with the -std=c++17 flag.

Some further explanation for clarity: There are currently two frontends available for megamol. The old mmconsole and the new one simply called megamol. So far, not every example has be adapted to the new frontend.

With this project file, you can use the ospray example with the new frontend: ./megamol.sh ../examples/ospray/testspheres_ospray.lua:
`mmCreateView("Project_2", "View3D_2", "::Project_1::View3D_21")
mmCreateModule("OSPRayRenderer", "::Project_1::OSPRayRenderer1")
mmCreateModule("AmbientLight", "::Project_1::AmbientLight1")
mmCreateModule("OSPRaySphereGeometry", "::Project_1::OSPRaySphereGeometry1")
mmCreateModule("OSPRayOBJMaterial", "::Project_1::OSPRayOBJMaterial1")
mmCreateModule("TestSpheresDataSource", "::Project_1::TestSpheresDataSource1")
mmCreateCall("CallLight", "::Project_1::OSPRayRenderer1::lights", "::Project_1::AmbientLight1::deployLightSlot")
mmCreateCall("CallOSPRayStructure", "::Project_1::OSPRayRenderer1::getStructure", "::Project_1::OSPRaySphereGeometry1::deployStructureSlot")
mmCreateCall("CallRender3D_2", "::Project_1::View3D_21::rendering", "::Project_1::OSPRayRenderer1::rendering")
mmCreateCall("CallOSPRayMaterial", "::Project_1::OSPRaySphereGeometry1::getMaterialSlot", "::Project_1::OSPRayOBJMaterial1::deployMaterialSlot")
mmCreateCall("MultiParticleDataCall", "::Project_1::OSPRaySphereGeometry1::getdata", "::Project_1::TestSpheresDataSource1::getData")`

Thank you very much for the explanations! I will try the given example soon. Can you also please give some short information /example on how I can use my own data in the above code?

Furthermore, the paths to the lua files must be absolute or relative to the megamol.sh file location. That means it is not possible to (create an alias to the megamol.sh file and) run the command in an arbitrary folder (eg. ../bin/megamol.sh testspheres_megamol.lua in the examples folder).

You are using the current master branch? (not older than 2 weeks)
Then there is no need to use the *.sh wrapper scripts. You can now just directly use the megamol and mmconsole binary. This should (TM) also work from any directory now.
(Two weeks ago we switched to build MegaMol with its plugins as single static linked binary. Previously the wrapper scripts where needed to set LD_LIBRARY_PATH to find all plugins and some dependencies. Your problem with the path was one on the list of features why we switched to static build. The cleanup process after this switch is not yet fully finished, therefore the .sh files are still there currently.)

Day 3/? of the installation process...
I'm using yesterdays master branch. Good to know, thank you for the info. I tried it, but of course there is an error (error while loading shared libraries: libospray.so.0: cannot open shared object file: No such file or directory). Probably some sym links must be generated by hand...
But at this point I don't really care, since it works with absolute paths as well (you can use the $PWD variable in linux) and I just want to make it work somehow...
Can you please provide two minimal working example on how to use my own data (mmpld generated with ls1) in the lua files with and without ospray. I tried to modify the lua testspheres_example but I couldn't find the right syntax.
Thank you!
Sorry, but it is really frustrating and error-prone to install Megamol without a proper documentation.

With the following minimal project you can load your own mmpld data set by replacing $PATH_TO_MMPLD_DATA_SET_FILE$ (this project file is for the new frontend megamol):
mmCreateView("mmpld_test","View3D_2","::view")
mmCreateModule("SphereRenderer","::renderer")
mmCreateModule("DistantLight","::distantlight")
mmCreateModule("BoundingBoxRenderer","::bbox")
mmCreateModule("MMPLDDataSource","::data_source")
mmCreateModule("TransferFunction","::transfer_function")
mmCreateCall("MultiParticleDataCall","::renderer::getdata","::data_source::getdata")
mmCreateCall("CallGetTransferFunction","::renderer::gettransferfunction","::transfer_function::gettransferfunction")
mmCreateCall("CallLight","::renderer::lights","::distantlight::deployLightSlot")
mmCreateCall("CallRender3D_2","::bbox::chainRendering","::renderer::rendering")
mmCreateCall("CallRender3D_2","::view::rendering","::bbox::rendering")
mmSetParamValue("::data_source::filename",[=[$PATH_TO_MMPLD_DATA_SET_FILE$]=])

This is an analog example project using ospray:
mmCreateView("ospray", "View3D_2", "::ospray::view")
mmCreateModule("OSPRayRenderer", "::ospray::OSPRayRenderer1")
mmCreateModule("AmbientLight", "::ospray::AmbientLight1")
mmCreateModule("OSPRaySphereGeometry", "::ospray::OSPRaySphereGeometry1")
mmCreateModule("OSPRayOBJMaterial", "::ospray::OSPRayOBJMaterial1")
mmCreateModule("MMPLDDataSource", "::ospray::MMPLDDataSource1")
mmCreateModule("BoundingBoxRenderer", "::ospray::BoundingBoxRenderer1")
mmCreateCall("CallLight", "::ospray::OSPRayRenderer1::lights", "::ospray::AmbientLight1::deployLightSlot")
mmCreateCall("CallOSPRayStructure", "::ospray::OSPRayRenderer1::getStructure", "::ospray::OSPRaySphereGeometry1::deployStructureSlot")
mmCreateCall("CallOSPRayMaterial", "::ospray::OSPRaySphereGeometry1::getMaterialSlot", "::ospray::OSPRayOBJMaterial1::deployMaterialSlot")
mmCreateCall("MultiParticleDataCall", "::ospray::OSPRaySphereGeometry1::getdata", "::ospray::MMPLDDataSource1::getdata")
mmCreateCall("CallRender3D_2", "::ospray::BoundingBoxRenderer1::chainRendering", "::ospray::OSPRayRenderer1::rendering")
mmCreateCall("CallRender3D_2", "::ospray::view::rendering", "::ospray::BoundingBoxRenderer1::rendering")
mmSetParamValue("::ospray::OSPRayRenderer1::useDBcomponent", [=[true]=])
mmSetParamValue("::ospray::MMPLDDataSource1::filename", [=[$PATH_TO_MMPLD_DATA_SET_FILE$]=])

OSPRay 2.x has made it into MegaMol yesterday.
Meaning, should you update MegaMol you would need to update OSPRay as well.

I am glad to hear that it is working now!

PS: How is it possible to set the font size (in the lua file)? There is Windows -> Font Settings but it doesnt change anything when set to eg. 32.00.
 Two font files are already provided in the folder ..install\share\resources\fonts. (A general GUI scaling for better support of high DPI displays is coming soon ...)

PPS: Is it possible to change the mouse control? Its kind of messy with Ctrl+MouseLeft or Alt+MouseRight etc... Something like in Blender for example would be great ;)
In the configuration file ..install\bin\megamolcong.lua you can change the option for the arcball behaviour to òn: mmSetConfigValue("arcball",     "on")

Since the text file based project configuration can be really exhausting, you can try to configure your projects more easy via the configurator. In the menu go to Windows -> Configurator.
It is possible to start an empty MegaMol without providing a project file.

Thanks for the info! Its great to hear that higher DPI displays are supported soon. Can I somehow save the font + font size or apply it globally? Additionally, you should support copy+paste. Its quite a pain to type in long paths in the font name field ;)
Thank you, the arc ball option works!
It tried to add the screenshooter module in the configurator, but there is no way to connect it with the view module. Without connection there is an error when a screenshot is triggered.
1|Unable to find module "" for processing
1|Unable to find view or viewInstance "" for ScreenShot

It's the same when writing "::view" in the view field.

The screenshooter is not connected to the graph, it is a little bit strange to use. There is not direct connection to the graph.
Within the view field you must write the full namespaced instance name of the view, therefore please try ::ospray::view.
Within the new megamol.exe we are trying to replace the old screenshoter. The basic screenshot functionality is already available, see the screenshot menu at top (press F2 to trigger). But at the moment this will basically just write the current framebuffer to disk, the old screenshooter module is more flexibel in kind of using different resolutions etc.

The font file and font size are stored in the GUI state within the project file and should be restored after loading the project again. The font loading will also be improved in the upcoming pull request #679.
I reproduced the behaviour that copy and past is not working properly under linux. This is a bug and I will have a look on that.
Additional note to the screen shooting: If screenshots are taken consecutively, the given file name is prepended by an incrementing suffix. This way, no new file name has to be set after each screenshot.


What are the 2 new dummy outputs created for?

Firstly, thanks for putting this together!
I'm just a little confused about what the 2 new dummy outputs created are for. I see the code says:
https://github.com/magiceden-oss/msigner/blob/3de81d4aaac4d030b2fb2967d704a59070981777/src/signer.ts#L465
Is it to avoid having to create a new tx with 2 dummy inputs in a future purchase? Also, do they have any specific values?

Yes, they're used for future purchase, so that people don't need to prepare the dummy utxos again

i don't understand the need for the 2 dummy utxos, can you point me to any materials where i can learn?

I was curious about why this library uses two dummy inputs as well. I think it's because if you only use one dummy input, the ordinal winds up being unaligned. Let's say we use one dummy and have a final transaction with inputs valued A, A, and B, and outputs valued 2 A and B, with the ordinal being sold on the first sat of the second A input:
A    2A
A -> B
B

The transaction value balances, however the ordinal will wind up in the middle of the first output.
If, on the other hand, we add an additional dummy:
A    2A
A    A
A -> B
B

Then the ordinals winds up on the first sat of the second output.
And two dummy outputs are used because that's the number of dummy inputs required.


Default CSS task should report warnings in PROD environment

Currently the JS tasks reports errors in production and development environments, but the CSS task is only limited to reporting while in development environment.

Fixed this in WIP PR:
https://github.com/xwp/undercurrent/pull/13
I'll get that through with the styleguide support in undercurrent.


Realm UI refactor cleanup

Remove from the codebase elements that we are no longer using (questline name, realm description, components etc)

Let's not let this block the release.


(GH-711) prelease label should not be red

When a label is red, something wrong is implied, switching to DarkOrange
Implies a warning.

Merging this fixes #711

@mkevenaar your changes have been merged, thanks for your contribution 👍


Correct Checksums for gulp archive

It seems that checksums are no more corrects.

Our recipe of gulp is a few versions old, if you want to change the recipe to 2.0.1 and give it a test build I think that would be a much better change.


Add support for compression

There seems to be no support for compressing the data transferred between server and client. I had a look at the internals and i see there are some flags in the internalConfig for compression that defaults to false. I tried enabling it but seems there is no decompression implemented.
Would be really nice if compression could be added as we see some slow responses related to transfers taking some time.

The "compression" flag will compress the messages after the login with zlib (see https://github.com/exasol/websocket-api/blob/master/docs/WebsocketAPIV3.md#compression). I assume this would improve performance for large queries or result sets. If this is the case I will add it to the roadmap.

Yes large queries would surely see a benfit of that. And it makes sense for the decompression to be handled by the driver instead of outside i think? And even if I wanted to try to do the decompression outside of the driver there is currently no supported way to configure the driver to use compression since the compression is not part of the Config interface we can pass into the initializer.


nothing showing up that i lost contact with the server

I lost contact with one of my servers but nothing is showing up on the Dashboard that i have lost contact. The only thing i can see are the pie charts that won't move.
Webmin version 1.881
Authentic Theme 19.19

Hi,
In case you're not focused on the theme (tab) it disables background data collection. You need to make window active by clicking on it. After doing so, it will show you

I have made it active but still nothing... I haven't pressed any buttons because that will of course give me an error.

You 3xp3ct message to be shown only on Dashboard in familiar cases or all the time connection is lost. User action is important not to create unneeded load.

But i'm sure you added some kind of message that was showing when i lost connection? Why isn't that showing?
It seems that i can even open menus and press the Dashboard button and it will continue to show the dashboard as everything was okay. Not a single error message. If i do a refresh it takes 30-40 seconds and i get "The connection has timed out".
Most of the times you have the Dashboard open and you know everything will auto update (live) so that page is the most important one but i don't know if someone else have another opinion about it? For me the Dashboard is the important one.

It wasn't showing, because in the past there were complains from the users with unstable connection that this message was appearing pretty often.
I have managed to make it work, but it will take some time before it's shown, to avoid further issues.

In that case you should have added an option so users can choose how long time it should be before showing this message.

No, we already have to many options; right now it works perfectly; you will know that you'd lost connection to the server in 7-9 seconds. It's not a big of a deal at all.


MTP missing from 4 plans

🚨 Looks like you arrived from the internal review site
🚨 Do not enter Microsoft confidential information here
Following the anouncement on https://azure.microsoft.com/en-us/updates/mtp-auto-enabled/ , since the 1st of June 2020 MTP has been automatically updated for the listed subscriptions, however by checking our licensing service plan reference, I've noticed that MTP is not included in all plans.
Could you please check if currently is included in the ones missing it, and if so add it?
Product   Name | MTP included
Microsoft 365 E5 | yes
Microsoft 365 E5 Security | yes
Windows 10 Enterprise E5 | no
Enterprise Mobility + Security E5 | no
Enterprise Mobility + Security G5 GCC | no
Office 365 E5 | yes
Microsoft Cloud App Security | no

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

ID: 7c245452-161d-89a1-c026-99a0721cf071
Version Independent ID: 16dec59a-eb83-1837-4efd-4645e7aeaed2
Content: Product names and service plan identifiers for licensing - Azure AD - Microsoft Entra
Content Source: articles/active-directory/enterprise-users/licensing-service-plan-reference.md
Service: active-directory
Sub-service: enterprise-users
GitHub Login: @Nicholak-MS
Microsoft Alias: nicholak

Hi @asdcristi,
Thank you for contacting us about the issue you found. In order to help I need a bit more information. I did some spot checking on the list of products you provided above, but I am not able to easily identify the MTP item you note. I think you are referencing a service plan that is to be included in each of those products is that right? Can you provide the service plan name and GUID associated with Microsoft Threat Protection that you are expecting? That will help me to cross reference our source against what is published on the online table.
Thanks in advance for the additional details.
Thanks,
Nick

Thanks Cristian, this is very helpful. I will do some additional analysis and see if I can get to the bottom of this. Thank you for the information. I will get back to you if I need any additional details.
Thanks
Nick

Hi Cristian,
I was able to reverse lookup what products the MTP service plan exists in and I added to the relevant missing products last week. Please let me know if you discover any additional places where it is missing.
Thanks
Nick
#please-close


Recent build failure on OpenBSD 6.4

Which operating system does the issue occur on?
OpenBSD 6.4-current:
user ~/ALACRITTY/alacritty $ sysctl kern.version
kern.version=OpenBSD 6.4-current (GENERIC.MP) #433: Sun Nov 11 10:08:54 MST 2018
    deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

user ~/ALACRITTY/alacritty $ rustc -Vv
rustc 1.30.1
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-openbsd
release: 1.30.1
LLVM version: 6.0

If on linux, are you using X11 or Wayland? No Linux and no Wayland :)
I'm a happy user of alacritty on OpenBSD compiling from source. Thank you for all your work on alacritty!
I usually recompile fairly often from the master branch (now that the scroll branch has been merged).
Today I've tried to update but unfortunately the build fails:
   Compiling smithay-client-toolkit v0.4.1
error[E0432]: unresolved import `nix::sys::memfd`
 --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/smithay-client-toolkit-0.4.1/src/utils/mempool.rs
  |
4 | use nix::sys::memfd;
  |     ^^^^^^^^^^^^^^^ no `memfd` in `sys`

error: aborting due to previous error

I don't have any rust experience but it seems that https://github.com/Smithay/client-toolkit doesn't take into account that nix::sys::memfd is only available on Linux. But since Wayland is Linux specific maybe it's an honest mistake :)
I'm  not sure that's the best course of action, but would it be possible to not try and compile any Wayland things on the BSDs ?
The latest successful build of alacritty that I have on OpenBSD is from the 5th of November, so this is a recent change somewhere in the dependency tree, maybe an updated version of one of the crates.
Full build log:
user ~/ALACRITTY/alacritty $ git pull
Updating f182afa..a68ce7a
Fast-forward
 CHANGELOG.md          |  6 ++++++
 Cargo.lock            | 30 +++++++++++++++---------------
 alacritty.yml         |  2 +-
 alacritty_macos.yml   |  4 ++--
 alacritty_windows.yml |  2 +-
 ci/before_deploy.sh   |  2 +-
 src/display.rs        | 60 ++++++++++++++++++++++++++++++++++++++++--------------------
 src/renderer/mod.rs   | 47 +++++++++++++----------------------------------
 8 files changed, 79 insertions(+), 74 deletions(-)

user ~/ALACRITTY/alacritty $ cargo build --release
 Downloading proc-macro2 v0.4.23
 Downloading syn v0.15.20
   Compiling nodrop v0.1.12
   Compiling cfg-if v0.1.6
   Compiling scopeguard v0.3.3
   Compiling lazy_static v1.2.0
   Compiling memoffset v0.2.1
   Compiling libc v0.2.43
   Compiling rayon-core v1.4.1
   Compiling rayon v1.0.3
   Compiling either v1.5.0
   Compiling proc-macro2 v0.4.23
   Compiling version_check v0.1.5
   Compiling nix v0.11.0
   Compiling num-traits v0.2.6
   Compiling xml-rs v0.8.0
   Compiling semver-parser v0.7.0
   Compiling pkg-config v0.3.14
   Compiling unicode-xid v0.1.0
   Compiling num-integer v0.1.39
   Compiling rand_core v0.3.0
   Compiling void v1.0.2
   Compiling bitflags v1.0.4
   Compiling siphasher v0.2.3
   Compiling byteorder v1.2.7
   Compiling khronos_api v3.0.0
   Compiling num-derive v0.2.3
   Compiling num-iter v0.1.37
   Compiling stable_deref_trait v1.1.1
   Compiling downcast-rs v1.0.3
   Compiling adler32 v1.0.3
   Compiling khronos_api v2.2.0
   Compiling same-file v1.0.4
   Compiling num-rational v0.2.1
   Compiling color_quant v1.0.1
   Compiling xdg v2.1.0
   Compiling lzw v0.10.0
   Compiling scoped_threadpool v0.1.9
   Compiling matches v0.1.8
   Compiling serde v1.0.80
   Compiling ucd-util v0.1.2
   Compiling regex v1.0.6
   Compiling ryu v0.2.7
   Compiling foreign-types-shared v0.1.1
   Compiling lazycell v1.2.0
   Compiling utf8-ranges v1.0.2
   Compiling percent-encoding v1.0.1
   Compiling unicode-width v0.1.5
   Compiling unicode-normalization v0.1.7
   Compiling linked-hash-map v0.5.1
   Compiling quick-error v1.2.2
   Compiling slab v0.4.1
   Compiling cgmath v0.16.1
   Compiling termcolor v1.0.4
   Compiling itoa v0.4.3
   Compiling fnv v1.0.6
   Compiling ansi_term v0.11.0
   Compiling utf8parse v0.1.1
   Compiling safemem v0.3.0
   Compiling slab v0.3.0
   Compiling vec_map v0.8.1
   Compiling dtoa v0.4.3
   Compiling lazycell v0.4.0
   Compiling strsim v0.7.0
   Compiling approx v0.1.1
   Compiling static_assertions v0.2.5
   Compiling arraydeque v0.4.3
   Compiling copypasta v0.0.1 (/home/user/ALACRITTY/alacritty/copypasta)
   Compiling arrayvec v0.4.7
   Compiling thread_local v0.3.6
   Compiling crossbeam-utils v0.2.2
   Compiling log v0.4.6
   Compiling num_cpus v1.8.0
   Compiling memmap v0.6.2
   Compiling iovec v0.1.2
   Compiling shared_library v0.1.9
   Compiling net2 v0.2.33
   Compiling filetime v0.2.2
   Compiling atty v0.2.11
   Compiling rand v0.4.3
   Compiling errno v0.2.4
   Compiling unicase v1.4.2
   Compiling memchr v2.1.1
   Compiling semver v0.9.0
   Compiling rand_core v0.2.2
   Compiling xml-rs v0.7.0
   Compiling unreachable v1.0.0
   Compiling stb_truetype v0.2.4
   Compiling owning_ref v0.3.3
   Compiling inflate v0.4.3
   Compiling deflate v0.7.19
   Compiling freetype-sys v0.7.0
   Compiling servo-fontconfig-sys v4.0.7
   Compiling x11-dl v2.18.3
   Compiling walkdir v2.2.7
   Compiling gif v0.10.1
   Compiling unicode-bidi v0.3.4
   Compiling regex-syntax v0.6.3
   Compiling foreign-types v0.3.2
   Compiling wayland-scanner v0.21.4
   Compiling textwrap v0.10.0
   Compiling humantime v1.1.1
   Compiling yaml-rust v0.4.2
   Compiling base64 v0.9.3
   Compiling vte v0.3.3
   Compiling crossbeam-epoch v0.3.1
   Compiling log v0.3.9
   Compiling osmesa-sys v0.1.2
   Compiling rand v0.5.5
   Compiling mio v0.6.16
   Compiling smallvec v0.6.5
   Compiling lock_api v0.1.4
   Compiling rustc_version v0.2.3
   Compiling notify v4.0.6
   Compiling clap v2.32.0
   Compiling wayland-client v0.21.4
   Compiling wayland-protocols v0.21.4
   Compiling crossbeam-deque v0.2.0
   Compiling approx v0.3.0
   Compiling ordered-float v1.0.1
   Compiling line_drawing v0.7.0
   Compiling num-traits v0.1.43
   Compiling gl_generator v0.10.0
   Compiling parking_lot_core v0.3.1
   Compiling gl_generator v0.9.0
   Compiling quote v0.6.10
   Compiling mio-more v0.1.0
   Compiling idna v0.1.5
   Compiling phf_shared v0.7.23
   Compiling rusttype v0.7.2
   Compiling euclid v0.17.3
   Compiling aho-corasick v0.6.9
   Compiling nom v4.1.1
   Compiling serde_json v1.0.33
   Compiling serde_yaml v0.8.7
   Compiling glutin v0.19.0
   Compiling phf_generator v0.7.23
   Compiling phf v0.7.23
   Compiling syn v0.15.20
   Compiling alacritty v0.2.2 (/home/user/ALACRITTY/alacritty)
   Compiling png v0.12.0
   Compiling andrew v0.1.4
   Compiling phf_codegen v0.7.23
   Compiling parking_lot v0.6.4
   Compiling terminfo v0.6.1
   Compiling url v1.7.2
   Compiling cc v1.0.25
   Compiling jpeg-decoder v0.1.15
   Compiling libloading v0.5.0
   Compiling libz-sys v1.0.25
   Compiling cmake v0.1.35
   Compiling serde_derive v1.0.80
   Compiling dlib v0.4.1
   Compiling wayland-sys v0.21.4
   Compiling env_logger v0.5.13
   Compiling servo-freetype-sys v4.0.3 (/home/user/ALACRITTY/alacritty/servo-freetype-proxy)
   Compiling freetype-rs v0.19.0
   Compiling expat-sys v2.1.6
   Compiling wayland-commons v0.21.4
   Compiling servo-fontconfig v0.4.0
   Compiling font v0.1.0 (/home/user/ALACRITTY/alacritty/font)
   Compiling tiff v0.2.1
   Compiling image v0.20.1
   Compiling smithay-client-toolkit v0.4.1
error[E0432]: unresolved import `nix::sys::memfd`
 --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/smithay-client-toolkit-0.4.1/src/utils/mempool.rs
  |
4 | use nix::sys::memfd;
  |     ^^^^^^^^^^^^^^^ no `memfd` in `sys`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0432`.
error: Could not compile `smithay-client-toolkit`.
warning: build failed, waiting for other jobs to finish...
error: build failed

Similar to other dependencies like winpty or winapi, I'd say that a crate should build on every operating system. If it is pulled in or not is a different matter. But there's no way to support both X11 and Wayland at runtime without pulling both in at build time, the only option would be to support a "no-wayland" feature flag.

@thendiscard I've released a new version of SCTK that should compile on BSD. Can you confirm?

@vberger I've updated https://github.com/Smithay/client-toolkit/issues/41, SCTK compiles fine on OpenBSD, thanks!
I didn't want to put the details here since now I have another build failure for alacritty, in a dependency completely different than SCTK. I'll update this issue with more details shortly.

https://github.com/alexcrichton/filetime/issues/33 was fixed (by https://github.com/alexcrichton/filetime/pull/34) and the version of filetime bumped to 0.2.4 . With filetime 0.2.4 I can successfully build and use alacritty on OpenBSD 6.4-current .
However filetime is pinned (is that the correct term ?) to 0.2.3 in alacritty/Cargo.lock . I'm not sure how this is handled, should I open an alacritty PR with the Cargo.lock changes ? I've checked and https://github.com/passcod/notify doesn't have a Cargo.lock, notify only specifies filetime = "^0.2.1" in it's Cargo.toml . Again, I'm not a rust developer so I not familiar with how these details are usually handled for rust projects.
user ~/ALACRITTY/alacritty $ cargo update -v -p filetime
    Updating crates.io index
    Updating git repository `https://github.com/zacps/winpty`
    Updating filetime v0.2.3 -> v0.2.4

user ~/ALACRITTY/alacritty $ git diff
diff --git a/Cargo.lock b/Cargo.lock
index 948fc8d..ee07498 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -713,7 +713,7 @@ dependencies = [

 [[package]]
 name = "filetime"
-version = "0.2.3"
+version = "0.2.4"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 dependencies = [
  "cfg-if 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
@@ -1408,7 +1408,7 @@ version = "4.0.6"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 dependencies = [
  "bitflags 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
- "filetime 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
+ "filetime 0.2.4 (registry+https://github.com/rust-lang/crates.io-index)",
  "fsevent 0.2.17 (registry+https://github.com/rust-lang/crates.io-index)",
  "fsevent-sys 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
  "inotify 0.6.1 (registry+https://github.com/rust-lang/crates.io-index)",
@@ -2848,7 +2848,7 @@ dependencies = [
 "checksum expat-sys 2.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "658f19728920138342f68408b7cf7644d90d4784353d8ebc32e7e8663dbe45fa"
 "checksum failure 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "6dd377bcc1b1b7ce911967e3ec24fa19c3224394ec05b54aa7b083d498341ac7"
 "checksum failure_derive 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "64c2d913fe8ed3b6c6518eedf4538255b989945c14c2a7d5cbff62a5e2120596"
-"checksum filetime 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "b3ea0c97183a611b1673e5e28b160d7e1035106cad053c988aae3bbd996fdcce"
+"checksum filetime 0.2.4 (registry+https://github.com/rust-lang/crates.io-index)" = "a2df5c1a8c4be27e7707789dc42ae65976e60b394afd293d1419ab915833e646"
 "checksum flate2 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "3b0c7353385f92079524de3b7116cf99d73947c08a7472774e9b3b04bff3b901"
 "checksum fnv 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)" = "2fad85553e09a6f881f739c29f0b00b0f01357c743266d478b68951ce23285f3"
 "checksum font-loader 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "2fbd86bafc9e14ab7076e084d31eed4633120f910d0c42a017e5382aac89937f"

user ~/ALACRITTY/alacritty $ cargo build --release
 Downloading unicode-width v0.1.5
 Downloading serde_derive v1.0.80
 Downloading bitflags v1.0.4
 Downloading x11-dl v2.18.3
 Downloading serde v1.0.80
 Downloading serde_yaml v0.8.7
# ........................................................
   Compiling image v0.20.1
   Compiling smithay-client-toolkit v0.4.2
   Compiling winit v0.18.0
    Finished release [optimized + debuginfo] target(s) in 9m 01s

user ~/ALACRITTY/alacritty $ target/release/alacritty -V
alacritty 0.2.3

@thendiscard v0.2.3 doesn't mean it's pinned to one specific version. Even if you specify a dependency with 0.2.3, a non-breaking update can still be automatically applied using cargo-update. So feel free to just run that command and send a PR!


Improve scope environment variable handling

Right now, using the SCOPE environment variable is not intuitive. When requesting one scope, users can submit a single value. However, when requesting multiple scopes, users have to create a secret in their repository where the scopes they'd like to request are enclosed in brackets and double-quoted:
GitHub Secret
["scope1", "scope2"]

Not only should this be documented, but users should be able to create their SCOPE secret with a variety of syntaxes. The following are all reasonable:

scope1,scope2
'scope1','scope2'
['scope1','scope2']

Here's a quick PR for updating the README to help users until we make code changes to allow a variety of syntaxes: https://github.com/adobe/aio-apps-action/pull/40


Research Databricks Integrationtest

Synopsis
As a PO/SME
I want the developers to investigate possible frameworks for integration tests in DataBricks
so that automated tests are built correctly and so we are building working software that doesn't break when new functionality is deployed.
Acceptance criteria

[ ] Investigate how we can test that events published on eventhub is received in a streaming job in DataBricks.
[ ] Investigate possible frameworks for integration testing in DataBricks
[ ] Investigate how we can feed integration test with input and output
[ ] Team is confident in solving a subsequent issue and estimating it: https://github.com/Energinet-DataHub/geh-aggregations/issues/607
[ ] Decision on which method was chosen must be documented.

Tech notes
Evaluation criteria for an integration testing strategy / platform:

Very easy to run localhost (same tests as in PR gate)
Is part of PR gate
Must support parallel settlement (developers, PR gates, etc.)
Can read from Delta Lake
Can write to Delta Lake
Must give confidence (eg: does it look like "enough" prod?)
DX. eg do not switch between pytest and xunit (?)
perfomance (start-up of container in CI etc)
Should it support performance tests?

Tasks

[ ] Get reference from Databricks on how to obtain knowledge about integration testing best practices as mentioned in certification course in Databricks Academy. @BjarkeMeier
[ ] Describe scenario "TestCommon" based on existing tools and strategy. @kristianschneider
[ ] Describe scenario "nutter". @johevemi
[ ] Describe scenario "Databricks-connect". @ZavezX
[x] Describe scenario "Container". @BjarkeMeier and @lasrinnil
[ ] Evaluate each scenario agains criteria (score or pros/cons or ...?) (all developers)
[ ] Decide on further actions (all developers)

@lasrinnil + @ZavezX jeg har prøvet at skrive noget ned på den her. vil i ikke prøve og kigge det igennem, og tilføje/slette, ellers tager vi den jo også på backlog refinement i morgen. Vil egentlig gerne have dem over i product backloggen.

Scenario "Container"
Assumptions:

Unit tests are pytest tests that are executed in container

Description:

Integration tests as pytest tests in container
Jobs are executed in container on the spark instance (test setup must start the job)
Non-mockable resources like Event Hub namespace and blob storage for Delta Lakes are available

Same concept as TestCommon where resources are provided by Mighty Ducks
Connection strings etc are obtained from the keyvault
The keyvault url is the sole configuration needed in order to execute the tests

Regarding CI no changes should be needed as integration tests are just executed by the same action that already execute the unit tests

Scope:

Functionality regarding pyspark (no .NET involved at all)

Pros:

Assuming unit tests run in container and with pytest

this will almost just be business as usual regarding coding the tests
container dependency will not incur any new overhead

Good DX by using same tools and strategies for pyspark development

not using e.g. .NET
same tools, language etc for both unit tests and integration tests

Cons:

Spark instance in container only has a single node(?)
Is not as close to production environment as we might have liked
Is not suitable for performance testing

Scenario ":NET"

Assumptions:

We lean up against the exsisting test.common framework and use .NET code to provission cluster, jobs and deploy and python code into integrationtest resouce group

Description:

The databricks workspace is available in the integration test enviroment, similar to the eventhub and servicebus
Integration tests are written in .NET using the test.common framework.
The test will use python code build in either pipeline or VS.code (job.py, package.whl)
The test will provision the cluster and job for the test run thorugh the databricks API. All functionality is availabel though the Microsoft.Azure.Databricks.Client nuget package
The test will create storage and eventhub items as allready known in other tests.
The test copies the required files to databricks via the API in Microsoft.Azure.Databricks.Client
The test starts the job via the API in Microsoft.Azure.Databricks.Client
The test sends test data to the eventhub
The test waits for data in the output storage
The test EITHER reads directly in the storage or uses another workbook to further analyse and transform the result into a meaningful format fx. json the we can read in .NET. This is usefull for examining very large result dataset
The test asserts the results, either directly by reading parquet or using the output from a extra resultAnalyser.py job run

Pros:

.NET is familiar to the ART and provides excelent tooling and DX
test.common is a proven approach with support from MightDucks
We can have a setup that can be closer to production with elements running in Azure and could be scaled similar
We allready know how to provission parts of the setup with previous timeseries integration test

Cons:

python build is decopled from the rest of the integration test in local dev

Info:
https://www.nuget.org/packages/Microsoft.Azure.Databricks.Client/
https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/
https://github.com/Energinet-DataHub/ARCHIVED-green-energy-hub/blob/5fc4fcc28e42a4a030c8704f07ca22afb72b0d96/samples/energinet/integration-test/source/GreenEnergyHub.IntegrationTest/Helpers/ParquetHelper.cs

This story was overtaken by a team decision on the 28th of February to base the time-series domain on dotnet spark instead of pyspark. That decision naturally leads to the conclusion to build integration tests in .NET and using TestCommon and other already existing toolings and used concepts.
dotnet spark has an MIT license. @BjarkeMeier and @ZavezX talked to the software architect who supported the decision. @BjarkeMeier has sent a request to Databricks to possibly get any useful info on the decision. I'll keep the team informed when I get an answer.
I recommend that we close this issue.


[5.0] fixed global scope case where eager loading inside scope causes 'is null'

See https://github.com/laravel/framework/pull/7898.
Any input / advice / test help appreciated.

Please provide tests.

@GrahamCampbell I'm not sure how to write tests for this. Any guidance or examples of similar tests would be pretty helpful and I'll give it a shot.

https://github.com/laravel/framework/blob/5.0/tests/Database/DatabaseEloquentRelationTest.php.

We also have integration tests at https://github.com/laravel/framework/blob/5.0/tests/Database/DatabaseEloquentIntegrationTest.php.


how to run this command through httpie?

$ echo '"name"' | http -a admin PUT :5984/_node/…/public_fields


Account Switcher - Discord Source - [Issue Report]

Error when i want to download it

resolve in issue #13


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.4.276",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0015581a79bbf8e521f85dddb7d3e4a66b9f51d4"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "0015581a79bbf8e521f85dddb7d3e4a66b9f51d4",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "watchdog: sc520_wdt: Fix possible use-after-free in wdt_turnoff()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.4.276 by commit 0015581a79bbf8e521f85dddb7d3e4a66b9f51d4. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001479


[cxx-interop] Support scoped enums (enum classes).

Simply treat scoped enums as (pre-existing) "non-frozen enums". C++ scoped enums are actually imported as Swift enums (unlike other enums) and no global variables need to be created (given their "scoped" nature).
I'd really like to import all enums as Swift enums, but the ship may have sailed on that one for C, at least. Stay tuned for future patches...

@swift-ci please test.

@swift-ci please smoke test.

@swift-ci please smoke test.

@swift-ci please smoke test OS X platform.

@swift-ci please test Windows.

@swift-ci please smoke test OS X platform.

@swift-ci please test Windows.

@swift-ci please smoke test.

@swift-ci please smoke test Linux.

@swift-ci please smoke test Linux.


Add Tauri 2.0 Action Script

Tauri 2.0 requires webkitgtk 4.1 and ubuntu 22.04 should now be used. NPM projects have the CLI as part of the project where it needs to be installed with Cargo. We manually specified the Tauri version to be able to get Tauri 2.0. If you are signing the Tauri Release, you need to specify the keys and passwords in the Secrets setting in GitHub.
Adding this action demonstrates the use on a Cargo project with the Tauri 2.0 Beta. This shows how the action would look with signed releases, updated OS's and packages, and a package version check from a small js script. #595

@FabianLars Can you please review this?

I just got back from vacation, I'll look at it today or tomorrow

Okay honestly i think i have to repeat my thought from discord. I'm not a fan of this approach. I'd rather have a small and concise note about the webkitgtk version than a duplicate of the whole workflow with minor changes. Or maybe install both versions with a comment that one of them can be removed.
(Same for the ubuntu version though we may as well update all of them to use 22.04 with a small note to downgrade to 20.04 in v1 if they want better backwards compat)
The cargo install tauri-cli thing is not a v2 specific problem (though a bit of a bigger issue since the action autoinstalls v1 right now) so i'd tend to keep omitting that. Maybe we can make that part in the Caveats section more clear though.

The readme as is is already much bigger than i'd like which makes people only skim over it and always choose the last example, even though the one in the middle should be used by most.

@FabianLars I just thought about our conversation about this and you mentioned that people always skip to the last one when they should be using the middle one. If that's the case, Should we move the middle one down?

I already fixed that part here: https://github.com/tauri-apps/tauri-action/pull/620 by moving the nieche examples into seperate files so that the readme only contains 1 example for now.


Add docstring support for Scala

Add support for Scale document string, see .emacs.jcs/func/jcs-docstring.el.

Implemented with e54609b102a9022f2459494c0aff5ad7f8cdcc54.


weird behavior when selecting a value, options pops up again, if you select other value, options pops up again and again (loop)

This behavior is related to HIDE on BLUR that is now working.


[WIP] Report detailed build version from Benchmark drivers

SR-4675 Report detailed build version from Benchmark drivers
https://bugs.swift.org/browse/SR-4675
This is partial implementation of printing the version information directly from Swift Benchmark Suite binaries.
There are few issue currently, that need to be evaluated before the merge. I'm seeking advice on how to resolve this:

SwiftPM is currently crashing the build with strange errors
The cmake build doesn't trigger Version.swift re-generation when that file is modified manually
Remove debug messages from final code (?)

I'm a little bit worried if I'm doing this the right way. When I build with build-script, all works as expected. But I don't know how is cmake tracking file changes (when and what to rebuild). I have been testing the re-builing, by manually clearing the version String in the generated Version.swift like this (after the initial build-script):
Mondoshawan:swift-macosx-x86_64 mondo$ pwd
/Users/mondo/Developer/swift-source/build/Ninja-ReleaseAssert/swift-macosx-x86_64
Mondoshawan:swift-macosx-x86_64 mondo$ ninja swift-benchmark-macosx-x86_64

This doesn't always trigger re-generation and the binaries print empty string (Benchamrk_O --version), so the binary is clearly rebuilt.
The file Version.swift is added as part of the DriverUtils module, right next to ArgsParse.swift. I have moved the code that generates the Version.swift from Version.swift.in from the macro(configure_build) into  function swift_benchmark_suite_version and call that from the preexisting function swift_benchmark_compile. But doesn't help, instead it just unnecessarily triggers the generation multiple time. So that's clearly worse than before...
Can you help, @gottesmm ?

@palimondo I haven't read your responses completely, but please do not edit the main PR to communicate information to me. It doesn't show up in my email as a notification so I just won't see it until I look at the PR itself, assuming that I even look at the main PR comment again.

Also just an FYI, I am not going to have time to look at this until later in the week. I just saw your post and noticed that you edited the main PR comment and wanted to be clear that I didn't see that large edit. The rest was just incidental quick responses.

Looking at this now.

Thanks for looking into this again. I've responded inline where appropriate. I definitely need more guidance here.

@gottesmm Are you able build using Swift PM? I've been trying to follow your instructions from the upcoming update to documentation https://github.com/apple/swift/pull/17112, but it is crashing for me.

@palimondo This has since gathered a few merge conflicts.  Do you still want to hold this open?

Closing this due to age and inactivity.  If you are still interested in pursuing this change, please either rebase this pull request and reopen it or shoot us another.  Thanks for this @palimondo.


plot_entropy fails in pyqtgraph ImageExporter

  File "/usr/local/lib/python3.6/site-packages/pyqtgraph/exporters/ImageExporter.py", line 70, in export
    bg = np.empty((self.params['width'], self.params['height'], 4), dtype=np.ubyte)
TypeError: 'float' object cannot be interpreted as an integer

In the entropy model I can see that the plt object's height() and width() methods both return floats.
I worked around it in ImageExported by converting to int explicitly, but not sure if it can/should be fixed in binwalk.

The lastest code in master now uses matplotlib instead of pyqtgraph, so this should not be a problem anymore!

I wish I remember what this was from (and I had the code), so I could confirm, but I'll take your word for it.


Improve matching custom java.lang.annotation.Annotation

Fixes #270

No, my previous comment was addressed. But I keep wondering why this is necessary. Are you perhaps generating annotation classes that don't implement annotationType() properly?

Good question, I will investigate more :)

@dstepanov is there any update on this PR? Should we keep it open?

Not sure if it is still needed, we can close it for now