Agent Response guide

Issues

Did you download a release or pull from Master? Which release?
-> downloaded 0.12.3 version

What operating system are you running?
->Ubuntu

Are you running locally or in the cloud?
->Locally

Which browser are you using?
->Chrome

Hi Guys !
I'm having a small trouble finishing small task using articulate.
Maybe someone here will  be able to help me.
So what i want to do is to ask question to articulate like.

Are there any errors on counter1 or 2 or 3 or 4  ?
Articulate connects to private Webhook API that contains this type of JSON:
(In real life it contains much more counters)

[{ 	"counterName": "counter1", 	"Result": "No Error detected", 	"errors": [] }, { 	"counterName": "counter2", 	"Result": "No Error detected", 	"errors": [] }, { 	"counterName": "counter3", 	"Result": "No Error detected", 	"errors": [] }, { 	"counterName": "counter4", 	"Result": "Error detected", 	"errors": ["some type of error"] }]
My problem is that I am not so familiar with using Handlebars.
Would there be anyone that could show me how would an Agent Response look like for this type of request ?
My Expectations:
User : Are there any errors on counter4 ?
Bot : There are errors on counter4 and these are: "some type of error"
I am using Entities with counter names to allow articulate recognize which counter I am talking about.
Thanks in advance !
Kind Regards,
Bart

@bkurowski I would look through the handlebar helpers available here: https://github.com/helpers/handlebars-helpers#array I think you're solution would be easier to accomplish if the counterName was the key for it's respective data rather than a value inside an object.
However I think you can get there with handlebar helpers and the array filter. Here's how I would try to get the correct answer.

Let's see what the entire web hook is returning. Remove all other agent responses on this intent and create one with {{{JSONstringify webhookResponse}}}. That should show you the entire response.

Remove the above response and add a new one. This time let's try to just return object in the array pertinent to counter2: {{#filter webhookResponse "counter2" property="counterName"}}{{{JSONstringify this}}}{{/filter}}

try that and let me know if it works.

Hi @wrathagom thank you for your reply.
Yes my plan is to use counterName now to find all the values I need.

When I have tried this {{{JSONstringify webhookResponse}}}
It gave me an output of.
[{"counterName":"Counter1","Result":"No Errors detected","errors":[]},{"counterName":"Counter2","Result":"No Errors detected","errors":[]},{"counterName":"Counter3","Result":"No Errors detected","errors":[]},{"counterName":"Counter4","Result":"Errors detected","errors":["Sample Error 123"]}]

When I have tried this {{#filter webhookResponse "counter2" property="counterName"}}{{{JSONstringify this}}}{{/filter}}
It gave me an output of.
{"counterName":"counter2","Result":"No Errors detected","errors":[]}

It matches nicely, that is what i was expecting thank you.
Also would you be able to tell me how to pass on the context to the agent response just like below.
In this example I am not using Text Prompt, and I am unsure how to pass context from the whole sentence the user is sending.
When I am using text prompt i would use {{slots.[ENTITY].value}} not sure about full sentence, how can I pick the counter name from it and pass it on to Agent Response.
User: Are there any errors on "Counter3" ?
Bot: These are errors on "Counter3"
You are a big help thank you,
Bart

When I apply {{#filter webhookResponse {{slots.Counters.value}} property="counterName"}}{{{JSONstringify this}}}{{/filter}}
It doesn't know what I am trying to pass to the agent response. I might be using wrong syntax.
I am just having a problem with building this type of syntax as it is new for me.

Can I get a screenshot?

@bkurowski I was suggesting that you don't try to do the dynamic counter, but rather put exactly what I had provided in to see if we could pull out counter2.
If you want to try to jump straight to the dynamic counter then try this:
{{#filter webhookResponse slots.Counters.value property="counterName"}}{{{JSONstringify this}}}{{/filter}}

but again without seeing the output of the above two steps it will be hard for me to help you troubleshoot.

When you did the static counter2 did you capitalize Counter?

The name was copied exactly as it is given from JSON so it was exact as it meant to be.
In my example all counters start with "pm" small letters.
So i think it should not be a problem.

I'm worried that the slot.Counters.value isn't what it needs to be. Can you try a response that is just {{slots.Counters.value}} to see if it would match the JSON. Again it would have to be exact. Value gets forced to lowercase by Rasa, if you need it to be something else and an exact match you could use synonyms to format it correctly.

I have tried having only this {{slots.Counters.value}} to be agent response.
And it gave me exact counter name as I have specified in the message.
Input: Anomalies on counter counter2.
Output: counter2

So this works, but doesn't get passed on in this example for some reason.

{{#filter webhookResponse slots.Counters.value property="counterName"}}{{{JSONstringify this}}}{{/filter}}

I have also checked my "User Says" if i does not have any unwanted spaces. It does not contain any unwanted spaces too.
Or would this be a sign of the bot not being trained enough yet ? Maybe it needs more examples ? "User Says" ?
Thanks

Ok i have observed the problem. It gives me error as:

it doesn't know how to reply

because as you said rasa changes the whole capital letters in the name to lower case letters.
So it gives me answer like that because it can not compare it and see it as it is not there.
I will test it now again and i will message you on the progress.
Thank you.

okay, if that is the problem, then I would recommend using synonyms to format exactly as the data is stored. For example create the counter entity with exact values and synonyms for possible variants:

Counter2 - counter2, Counter2, counter 2, Counter 2
Counter3 - counter3, Counter3, counter 3, Counter 3

etc

Now i understand where the problem was. Thanks for pointing it out.
Now it works dynamically using this :

{{#filter webhookResponse slots.Counters.value property="counterName"}}{{{JSONstringify this}}}{{/filter}}

The output of this looks like as follows:

{"counterName":"counter1","Result":"No Errors detected","errors":[]}

Would you be able to put me on the right tracks and tell me how can I strip out only "Result" out of that output ?
Example:
User: Any errors on counter 1 ?
Bot: Result
Thank you.

Try something like
On {{slots.Counters.original}} there were {{#filter webhookResponse slots.Counters.value property="counterName"}}{{this.Result}}{{/filter}}.

Since it looks like result is Title cased maybe you should do this as well:
On {{slots.Counters.original}} there were {{#filter webhookResponse slots.Counters.value property="counterName"}}{{lowercase this.Result}}{{/filter}}.

That is perfect thank you very much for your help !
Works exactly as I wanted it to work.
Kind Regards !
Bart

You're welcome. Feel free to create a new issue with any more troubles you may have.


Add database changes for product shadow

Implement the database changes in https://github.com/united-manufacturing-hub/united-manufacturing-hub/issues/297#issuecomment-880796956

Latest Update of the timescaleDB changes for digital shadow:

Notes:

step_id instead of station_id allows us more flexibility in the naming convention. There are cases, where a differentiation into stations would not make sense but the differentiation into steps would. This allows us to model multistep processes better.
Quality_class should be deletet: instead the information will be stored in the productTagTable or productTagStringTable
The structure of the inheritance table models every single path in the inheritance of parts. While it is easy to understand and use, it might make problems because of possibly to many entries. To make shure it works in the future we should test the use of this table with a few million test data points. To increase perfomance we should make both the child_uid and the parent_uid to an index.
Maybe we could use the name uniqueProductExternalID instead of uniqueProductAlternativeID.

Thank you @Gornoka, @JeremyTheocharis and @Scarjit for your help!!!

Additional thoughts,
Unique product table as in other schema:
Hypertable time = Id additional partitioning column assetId
Possible double table architecture for inheritance with child of asset and parent of asset table, each as hypertables for faster search performance and quick resolution of immediate relatives, ie in case of a defect I've product quick steps to isolate related products. Whether this is useful and feasible to implement should be evaluated in a benchmark.
For the product/unique product table defaults can be calculated by dividing machine memory through a constant factor (TBD, depending on final table row size) the other tables would be highly dependent on the complexity of the product tree with many child/parent connections yielding the low values.  Maybe it is useful to add an expected complexity field to the asset table, which could scale the time axis for the inheritance tables. To spread these high edge components into more different subtables. This would require a custom time partitioning function and an immutable Value for every asset, since the information in the hypertable on all products manufactured in the asset would be lost on scaling value change.

results from @Scarjit s benchmarks on this topic last week:

fastest speed would be achieved with a database specially designed for graphs (no suprise here)
implementation with 2 hypertables is more than 10X faster than the current implementation with 1 double indexed table.
for now the performance should be be sufficient with the double hypertable approach, and there would be the benefit of not using multiple databases in tandem. The size of the hypertable may need to be experimented on different example production chains. maybe a test tool could be added to the next milestone. @JeremyTheocharis


⚠ Processors has degraded performance

In f6bb773, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 56 ms

Resolved: Processors performance has improved in e80065a.


Dither not working

Expected Behavior
this image

to something like this

Current Behavior
this image

to this image

there is just nothing happening

Failure Information (for bugs)
the image is not being dithered
Steps to Reproduce
my code snippet:

Jimp.read('./server/images/example.png', async function (err, image) {

            async function dithering() {
                console.log('dithering', file)

                image.dither565()
                image.write(`./server/images/dithered_image.png`)

                file = `./server/images/dithered_image.png`
            }
     //...
     //...

step 1: dither the image
step 2: see the result

Context

Jimp Version: 0.16.1
Operating System: Windows 10 64 bit
Node version: v14.16.0

Failure Logs
no errors / logs

Maybe we can look into a 3rd party lib devoted to dithering


Noisemaker not working properly

Will this be updated to the latest version of LE?
There are some quite important fixes which seem to be still be an issue here.

Any issue in particular you're referring to?

One that is mainly a problem atm is that custom noisemakers pitch don't align with the settings if that makes sense

That should be fixed in the latest version 1.3.15

Awesome


Lightbox: Accommodate new posts

https://www.pivotaltracker.com/story/show/154906504

@alanpeabody I pulled this out into a separate PR (merging into gb/lightbox-arrow-keys, not master) because enough had changed that I thought you might want a quick 👀.
Aside from accommodating brand new posts, a lot of the stuff that was duplicated all over ImageRegion is now centralized in some helper functions. 👌


Question: Clean Code Query

Background:
So if I understand correctly the principles of Clean Architecture, the only reliance that the Application Layer should have is inward to the Domain. But if this is the case then why does the Northwind.Application have a reference to the Persistence layer?
Even more stand to me is the GetCustomerDetailQueryHandler having a direct dependency on the implemenation of the persistence layer's NorthwindDbContext.
Question:
Why is the above acceptable if the project is trying to be constructed as per Clean Architecture principles?

Hello and thanks for you interest.

Why is the above acceptable if the project is trying to be constructed as per Clean Architecture principles?

This is discussed in detail here; https://github.com/JasonGT/NorthwindTraders/issues/18.


Allow private server usage in Client.

It looks like there aren't many ways to set a custom request URL (without modifying the library itself), which could help with tools targeting private GD servers.

You can use the http.change(url=PRIVATE_SERVER_URL) context manager for that.
client = gd.Client()

with client.http.change(url=PRIVATE_SERVER_URL):
    daily = await client.get_daily()

Thanks, it worked.


Fix -Wrange-loop-analysis warning

Clang 10 has -Wrange-loop-analysis included in -Wall (since removed in https://reviews.llvm.org/D73434). If -Werror is also specified, this will cause compilation to fail.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add Generated Files to .gitignore

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the Modus style guidelines

Proposal
To maintain clarity and simplicity in our PRs, I recommend adding applicable generated files to the .gitignore file. This will result in a more streamlined code review process
Motivation and context
No response
What is the issue regarding ?
@trimble-oss/modus-web-components
Priority
Low
What product/project are you using Modus Components for ?
Work Center
What is your team/division name ?
Trimble Viewpoint
Are you willing to contribute ?
Maybe
Are you using Modus Web Components in production ?
Yes

I agree! Could you make a PR for this Ryan?

Yep, I can give this a shot If I can find some time here soon


Remove ObjectSerializer#serialized_json

Removes the deprecated ObjectSerializer#serialized_json.  It's been a few months and the warnings are creating too much noise in our logs, it's time to say goodbye!

:raised_hands: :upside_down_face:

@stas Given this major change, we should create a v2 release today.  Just want to make sure you're in agreement.

Yup, though I don't see why we need to release it right away. Let's schedule it for end of this week. This way we can also take some time to prepare the #86 maybe?!
How does that sound?

Sounds good!

@kpheasey and @stas thanks for this PR. 🎉


Running tests in IDE

Is it possible to run the tests though an IDE like IntelliJ? It has of course not any support internal, but is it possible to get it to trigger what sbt does?

+1.  I'm trying to contribute to monix.  Not being able to debug tests in intellij is really impacting my ability to understand and learn the code.

@lukestephenson you can already debug tests in IntelliJ.
Start your SBT like this:
sbt -jvm-debug 5005

It will say:
Listening for transport dt_socket at address: 5005

Then in IntelliJ IDEA do: Run, then Debug..., then create a new Remote configuration, using the 5005 port, specified above. This will make IntelliJ IDEA connect to that remote port and do debugging on it.
You can then set breakpoints and upon running the tests, it will hit them ;-)


Move to Wayland

We all know X11 is old, jolly, and stable, but Wayland is set to be the next standard for display servers in Linux, at least.
Currently, we do not ship anything related to Wayland. So, here's a list of what we should look to.

[x] Have a Wayland session.
[ ] Working on a Wayland-enabled desktop.
[ ] Outside of Waylands' issues, no showstopping bugs.

Recently Qt 5.15.0 was made available from Neon, this version of Qt is said to be more compatible with Nvidia fancy EFL extensions, meaning, that it should be usable now, at least. But we still have to try it, and figure how to se it as default if it's indeed usable.

Status Update
We're currently including both regular X11-based Plasma and Wayland-based Plasma. Both sessions are available to select from SDDM. However, the Wayland session does not work correctly when using the Nvidia proprietary driver.
According to this blog post from one of the KDE developers, adding a script to /etc/profile.d and adding a kernel parameter should be enough; unfortunately, that didn't work for me.
I believe that may be because we use ZSH as the user shell instead of Bash in the distribution, and ZSH ignores these files.


Update security.md

Fixes #16003

cc @anurse to explain why credentials are enabled while I'm out.


Exit gotty server when connection is closed?

Hi, my use case is I'm trying to provide an in-browser SSH client, however I'll be spawning up the gotty process when the request comes in and I want to kill it when the user exits ssh. What I'm using is:
gotty -w ssh<EMAIL_ADDRESS>
The problem currently I'm seeing is, when I go to browser and exit the ssh prompt (with exit command for instance), the gotty process stays alive and keeps accepting connections and new connections cause ssh command above to be restarted.
What I do need instead is, gotty server to quit when user quits by exiting the process so that I can garbage collect resources and next time user visits my service (say<EMAIL_ADDRESS>I will spawn another gotty server.
@yudai does it sound like a good proposal to have an argument that makes the gotty server quit once the executed process quits (rather than staying alive and re-execing the specified command when a new request comes in)?

Hi, thank you for the feedback and proposal.
To implement your requirement, we need figure out what should happen to the other clients when a client exit its command. Gotty forces all clients to drop their connections, or just stop accepting new clients and wait for the other clients to complete their command.
I assume that what you want to archive needs another option to limit the max connection number like -n 1.
If you can write a script for your garbage collection, using a shell script might be a better way.
#!/bin/sh
ssh<EMAIL_ADDRESS>
# do some garbage collection
rm something

then run gotty -w your_script.sh

@yudai by garbage collection I just meant collecting the gotty server actually. If gotty dies when ssh user@host command above exits, then my process can realize "ok, the user has quit".
Hypothetically, let's say I am building a web service where you give me your hostname, username, password/SSH key and I'm creating a gotty server and giving you http://gotty-host:ip of the SSH session.
When the process, yes, it makes sense to drop all client connections to gotty in this scenario. However I don't think I would need a max connection count here.
In a nutshell, if the exec-ed process exits, gotty probably should exit, too (instead of re-exec'ing) the process. I think we can achieve this simply by a --quit-if-command-exits flag and just os.Exit(0)ing when the executed process quits.

How about a option like --one-time? With this option, gotty accepts only one connection and once it exists, gotty exists.

:+1:

Done (OMG, I forgot to mention this issue in the commit again...)!

@yudai Thanks for this feature. I downloaded the latest pre-release from github (has --once) and when I run
gotty --once -w ssh user@host

(ssh doesn't prompt for credentials, I have public-key authentication set up) and go to the URL in my browser process just dies:
[...]
2015/08/24 11:44:47 URL: http://<IP_ADDRESS>:8080/
2015/08/24 11:44:52 GET /
2015/08/24 11:44:52 GET /hterm.js
2015/08/24 11:44:52 GET /gotty.js
2015/08/24 11:44:52 GET /ws
2015/08/24 11:44:52 Last client accepted, closing the listener.
2015/08/24 11:44:52 New client connected: <IP_ADDRESS>:49554
2015/08/24 11:44:52 Exiting...
$

It was a race condition issue. I pushed a fix that fixes the issue. Let me know if it still doesn't work properly.
Thank you for the feedback and report.

Will do. Btw by --once I didnt mean "accept only one client". It's just "exit when process finishes" I was trying to achieve. What's the reason for limiting clients?

@yudai I just tested the fix. it works, but as I said in the comment above "accept only one client" is pretty bad...
When I refresh the page, process just dies and my connection is dropped. I don't think this is a desirable behavior for anyone.

Thanks for testing.
The reason the current gotty accepts only one client (sometimes two ore more client can make a session due to lazy management of race conditions) is that I feel like it's uncomfortable that the behavior of a client can affect the other clients. If there is only one client, it's always safe to exit gotty by interaction from the client (like exit the command).
It's currently not easy to support refreshing. If you refresh your terminal window, that drops the websocket session between the gotty server and your browser. gotty recognizes that you've left from the session and simply exits the process by closing the pty (SIGHUP should be sent to the process). To support refreshing, or more precisely, reconnecting to the same process, gotty must support re-attaching to the existing pty from different clients. However, it's a kind of session management stuff and for now, I think it's out of the scope of gotty. I assume you can achieve your goal by using tmux.
What about using command like this:
gotty --once -w tmux -S /tmp/<host> new ssh <user>@<host>

I'm not sure if I understand your goal properly, so please let me know if this doesn't help you.

Closing as no activities last week. Please reopen if this issue still exists.

Ran into a similar issue, what I'm doing now is this:
./gotty -w bash -c "/bin/bash; killall gotty"

E.g. run something on when the user explicitly closes the shell (but does nothing not on disconnect).


"pandas", "emcee", "pycuda", "ROOT", "libPyROOT", "MCEq", "nuSQUIDSpy" optional dependencies are being ignored right now, but it would be nice to have these installed (if fast enough to be practical) for all unit tests to be able to run

Extract remaining (relevant) tasks from #586 to be able to close the latter soon.


Mac DVR fix

This PR replaces a few uses of glBufferData with glBufferSubData.
The benefits are:

it improves performance (by a small amount)
it behaves more friendly with mac. In fact, it stop crashing on Sam's mac. However, it still crashes on John's mac.

Discard is supposed to behave that way, but there is a comment in the VAPOR2 code that says discard is broken on the mac.

On Jan 31, 2019, at 6:19 PM, StasJ<EMAIL_ADDRESS>wrote:
@StasJ approved this pull request.
Discard terminates the thread so there is no need to return after. Just FYI
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

John Clyne
National Center for Atmospheric Research
303.497.1236 (w),<PHONE_NUMBER> (c)
<EMAIL_ADDRESS>

Discard certainly hasn't given me any surprises yet... Maybe they fixed the
VAPOR2 era bug? But I thought it doesn't hurt to have a return statement
there.
On Thu, Jan 31, 2019 at 6:40 PM clyne<EMAIL_ADDRESS>wrote:

Discard is supposed to behave that way, but there is a comment in the
VAPOR2 code that says discard is broken on the mac.

On Jan 31, 2019, at 6:19 PM, StasJ<EMAIL_ADDRESS>wrote:
@StasJ approved this pull request.
Discard terminates the thread so there is no need to return after. Just
FYI
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

John Clyne
National Center for Atmospheric Research
303.497.1236 (w),<PHONE_NUMBER> (c)
<EMAIL_ADDRESS>—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/VAPOR/pull/1443#issuecomment-459574194, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAxvJRANzjcwNOVlYqwGlcUXqQOaaMqAks5vI5sEgaJpZM4adb1q
.


feat(network): impl PropagateTransactionsTo helper in TransactionsCommand

Related issues

issue #4651

Changes

add the implementation of PropagateTransactionsTo helper

Hi, I already put in a PR for this here: https://github.com/paradigmxyz/reth/pull/4772

Hi, I already put in a PR for this here: #4772

Oh, it seems that we are solving the same problem.
I have been following the #4651, while you following #4691
They share the same goal, and I tried to discuss it here and here.

thanks for this, but this is a dup of #4772


Find the mono binary on OSX 10.11.

It is not in $PATH anymore if System Integrity Protection is on.

This is good.  But do you know how the change will propagate to the many other copies of NuGet.targets in the wild (in other repos)?  thanks

There's no good solution really, each repository will have to fix it themselves.
Fortunately this does not appear to be a problem in NuGet 3, so eventually it'll resolve itself.


fix(race-conditon): fix data race condition when accessing stderr on pipe

There was a race condition that existed in Pipe.Exec, which spins up a goroutine that access Pipe.stderr without a lock. This PR fixes that by protecting Pipe.stderr with Pipe.mu. This PR fixes #193.
Testing
Created a simple unit test as follows:
func TestDataRaceStdErr(t *testing.T) {
	stdOut := new(bytes.Buffer)
	stdErr := new(bytes.Buffer)

	_, err := script.Exec("echo").WithStdout(stdOut).WithStderr(stdErr).Stdout()
	if err != nil {
		t.Fatal(err)
	}
}

Running go test -race before the changes in this PR outputted the same warning seen in the issue. Running it again with the changes in the PR cause the tests to pass.

question: we currently do not run go test in the CI with the -race flag so I removed the regression test. Do we want to run the tests with the -race flag? If so, should I add the regression test back in?

If we can have race conditions, we should definitely run CI tests with the race detector on!

If we can have race conditions, we should definitely run CI tests with the race detector on!

Added the -race flag to ci.yml and added a regression test.

@mahadzaryab1 I'm happy if you're happy—do you want to go ahead and do a final quality pass, checking documentation comments, alphabetical order, gotestdox-friendly test names, and so on? You know the house style now 😄

@mahadzaryab1 I'm happy if you're happy—do you want to go ahead and do a final quality pass, checking documentation comments, alphabetical order, gotestdox-friendly test names, and so on? You know the house style now 😄

@bitfield Done! Let me know if there's anything I missed.


React 16 problem with ref on stateless component

Hi there, thanks again for this plugin, which we are now using in production on console.snips.ai.
Just tried upgrading to React 16, and while it's still in beta, I think these warnings/errors will remain:

They do seem to be coming from substyle so I opened an issue there as well.

Fixed in<EMAIL_ADDRESS>via https://github.com/jfschwarz/substyle/pull/21.


[Homebrew/macOS] .NET 6 and 7 build patches/workarounds

Opening an issue to track various patches/workarounds we do in Homebrew for macOS build to find out which are already fixed, if we need to upstream some, to discuss better ways to fix, and/or if should be part of documentation.
Some prior discussion in #2719 and 6.0.102 work in Homebrew PR Homebrew/homebrew-core#95339 (EDIT: 6.0.103 work in PR Homebrew/homebrew-core#96612)

[ ] Build failure on macOS ARM due to osx-x64 override. The following is the patch we use to allow using osx-arm64. If acceptable, I can create PR in dotnet/installer:

Patch
diff --git a/src/SourceBuild/tarball/content/repos/installer.proj b/src/SourceBuild/tarball/content/repos/installer.proj
index 712d7cd14..31d54866c 100644
--- a/src/SourceBuild/tarball/content/repos/installer.proj
+++ b/src/SourceBuild/tarball/content/repos/installer.proj
@@ -7,7 +7,7 @@
   <PropertyGroup>
     <OverrideTargetRid>$(TargetRid)</OverrideTargetRid>
-    <OverrideTargetRid Condition="'$(TargetOS)' == 'OSX'">osx-x64</OverrideTargetRid>
+    <OverrideTargetRid Condition="'$(TargetOS)' == 'OSX'">osx-$(Platform)</OverrideTargetRid>
     <OSNameOverride>$(OverrideTargetRid.Substring(0, $(OverrideTargetRid.IndexOf("-"))))</OSNameOverride>
     <RuntimeArg>--runtime-id $(OverrideTargetRid)</RuntimeArg>
@@ -28,7 +28,7 @@
     <BuildCommandArgs Condition="'$(TargetOS)' == 'Linux'">$(BuildCommandArgs) /p:AspNetCoreSharedFxInstallerRid=linux-$(Platform)</BuildCommandArgs>
     <!-- core-sdk always wants to build portable on OSX and FreeBSD -->
     <BuildCommandArgs Condition="'$(TargetOS)' == 'FreeBSD'">$(BuildCommandArgs) /p:CoreSetupRid=freebsd-x64 /p:PortableBuild=true</BuildCommandArgs>
-    <BuildCommandArgs Condition="'$(TargetOS)' == 'OSX'">$(BuildCommandArgs) /p:CoreSetupRid=osx-x64</BuildCommandArgs>
+    <BuildCommandArgs Condition="'$(TargetOS)' == 'OSX'">$(BuildCommandArgs) /p:CoreSetupRid=osx-$(Platform)</BuildCommandArgs>
     <BuildCommandArgs Condition="'$(TargetOS)' == 'Linux'">$(BuildCommandArgs) /p:CoreSetupRid=$(TargetRid)</BuildCommandArgs>
     <!-- Consume the source-built Core-Setup and toolset. This line must be removed to source-build CLI without source-building Core-Setup first. -->
diff --git a/src/SourceBuild/tarball/content/repos/runtime.proj b/src/SourceBuild/tarball/content/repos/runtime.proj
index f3ed143f8..2c62d6854 100644
--- a/src/SourceBuild/tarball/content/repos/runtime.proj
+++ b/src/SourceBuild/tarball/content/repos/runtime.proj
@@ -3,7 +3,7 @@
   <PropertyGroup>
     <OverrideTargetRid>$(TargetRid)</OverrideTargetRid>
-    <OverrideTargetRid Condition="'$(TargetOS)' == 'OSX'">osx-x64</OverrideTargetRid>
+    <OverrideTargetRid Condition="'$(TargetOS)' == 'OSX'">osx-$(Platform)</OverrideTargetRid>
     <OverrideTargetRid Condition="'$(TargetOS)' == 'FreeBSD'">freebsd-x64</OverrideTargetRid>
     <OverrideTargetRid Condition="'$(TargetOS)' == 'Windows_NT'">win-x64</OverrideTargetRid>

[ ] Build failure on macOS due to missing ILAsm/ILDAsm. This seems to be common issue on Linux too. The odd thing though is that RuntimeOsxArm64MicrosoftNETCoreILAsmVersion exists but RuntimeOsxX64MicrosoftNETCoreILAsmVersion doesn't, so needed to use Linux's version for x64. Not sure if this should be added, or if this is a .NET packaging issue that will be fixed. (EDIT: In 6.0.103, need to use Linux versions for osx-arm64 too) e.g.

Patch (v6.0.102)
diff --git a/src/SourceBuild/tarball/content/scripts/bootstrap/buildBootstrapPreviouslySB.csproj b/src/SourceBuild/tarball/content/scripts/bootstrap/buildBootstrapPreviouslySB.csproj
index 0a2fcff17..9033ff11a 100644
--- a/src/SourceBuild/tarball/content/scripts/bootstrap/buildBootstrapPreviouslySB.csproj
+++ b/src/SourceBuild/tarball/content/scripts/bootstrap/buildBootstrapPreviouslySB.csproj
@@ -23,6 +23,14 @@
     <PackageReference Include="runtime.linux-x64.Microsoft.NETCore.ILDAsm" Version="$(RuntimeLinuxX64MicrosoftNETCoreILDAsmVersion)" />
     <PackageReference Include="runtime.linux-x64.Microsoft.NETCore.TestHost" Version="$(RuntimeLinuxX64MicrosoftNETCoreTestHostVersion)" />
     <PackageReference Include="runtime.linux-x64.runtime.native.System.IO.Ports" Version="$(RuntimeLinuxX64RuntimeNativeSystemIOPortsVersion)" />
+    <PackageReference Include="runtime.osx-arm64.Microsoft.NETCore.ILAsm" Version="$(RuntimeOsxArm64MicrosoftNETCoreILAsmVersion)" />
+    <PackageReference Include="runtime.osx-arm64.Microsoft.NETCore.ILDAsm" Version="$(RuntimeOsxArm64MicrosoftNETCoreILDAsmVersion)" />
+    <PackageReference Include="runtime.osx-arm64.Microsoft.NETCore.TestHost" Version="$(RuntimeOsxArm64MicrosoftNETCoreTestHostVersion)" />
+    <PackageReference Include="runtime.osx-arm64.runtime.native.System.IO.Ports" Version="$(RuntimeOsxArm64RuntimeNativeSystemIOPortsVersion)" />
+    <PackageReference Include="runtime.osx-x64.Microsoft.NETCore.ILAsm" Version="$(RuntimeLinuxX64MicrosoftNETCoreILAsmVersion)" />
+    <PackageReference Include="runtime.osx-x64.Microsoft.NETCore.ILDAsm" Version="$(RuntimeLinuxX64MicrosoftNETCoreILDAsmVersion)" />
+    <PackageReference Include="runtime.osx-x64.Microsoft.NETCore.TestHost" Version="$(RuntimeLinuxX64MicrosoftNETCoreTestHostVersion)" />
+    <PackageReference Include="runtime.osx-x64.runtime.native.System.IO.Ports" Version="$(RuntimeLinuxX64RuntimeNativeSystemIOPortsVersion)" />
    </ItemGroup>

    <Target Name="BuildBoostrapPreviouslySourceBuilt" AfterTargets="Restore">

Patch (v6.0.103)
diff --git a/src/SourceBuild/tarball/content/scripts/bootstrap/buildBootstrapPreviouslySB.csproj b/src/SourceBuild/tarball/content/scripts/bootstrap/buildBootstrapPreviouslySB.csproj
index 14921a48f..3a34e8749 100644
--- a/src/SourceBuild/tarball/content/scripts/bootstrap/buildBootstrapPreviouslySB.csproj
+++ b/src/SourceBuild/tarball/content/scripts/bootstrap/buildBootstrapPreviouslySB.csproj
@@ -33,6 +33,14 @@
     <!-- There's no nuget package for runtime.linux-musl-x64.runtime.native.System.IO.Ports
     <PackageReference Include="runtime.linux-musl-x64.runtime.native.System.IO.Ports" Version="$(RuntimeLinuxX64RuntimeNativeSystemIOPortsVersion)" />
     -->
+    <PackageReference Include="runtime.osx-arm64.Microsoft.NETCore.ILAsm" Version="$(RuntimeLinuxX64MicrosoftNETCoreILAsmVersion)" />
+    <PackageReference Include="runtime.osx-arm64.Microsoft.NETCore.ILDAsm" Version="$(RuntimeLinuxX64MicrosoftNETCoreILDAsmVersion)" />
+    <PackageReference Include="runtime.osx-arm64.Microsoft.NETCore.TestHost" Version="$(RuntimeLinuxX64MicrosoftNETCoreTestHostVersion)" />
+    <PackageReference Include="runtime.osx-arm64.runtime.native.System.IO.Ports" Version="$(RuntimeLinuxX64RuntimeNativeSystemIOPortsVersion)" />
+    <PackageReference Include="runtime.osx-x64.Microsoft.NETCore.ILAsm" Version="$(RuntimeLinuxX64MicrosoftNETCoreILAsmVersion)" />
+    <PackageReference Include="runtime.osx-x64.Microsoft.NETCore.ILDAsm" Version="$(RuntimeLinuxX64MicrosoftNETCoreILDAsmVersion)" />
+    <PackageReference Include="runtime.osx-x64.Microsoft.NETCore.TestHost" Version="$(RuntimeLinuxX64MicrosoftNETCoreTestHostVersion)" />
+    <PackageReference Include="runtime.osx-x64.runtime.native.System.IO.Ports" Version="$(RuntimeLinuxX64RuntimeNativeSystemIOPortsVersion)" />
   </ItemGroup>

   <Target Name="BuildBoostrapPreviouslySourceBuilt" AfterTargets="Restore">

[x] Error MSB4018 while building 'installer in tarball' due to trying to find aspnetcore-runtime-internal v6.0.0 rather than current. Need to find out why this is happening. The hack done is change MicrosoftAspNetCoreAppRuntimePackageVersion to MicrosoftAspNetCoreAppRuntimewinx64PackageVersion inside src/installer.*/src/redist/targets/GenerateLayout.targets

EDIT 1: May not be needed anymore in 6.0.103
EDIT 2: Actual, based on Homebrew PR, still needed on osx-x64 as looking for v6.0.2
EDIT 3: Fixed in dotnet/installer#14938

[x] Needed to introduce GNU sed rather than default BSD sed. Not too important and can keep as build dependency, but may want to document if it remains hard requirement. The problem is due to sed -i usage in https://github.com/dotnet/arcade/blob/main/eng%2FSourceBuild.props#L38

Should be indirectly fixed by dropping sed -i usage in  https://github.com/dotnet/arcade/commit/b8007eed82adabd50c604a9849277a6e7be5c971
EDIT: Fixed in .NET 7

[x] Temporary issue but need to manually remove src/nuget-client.*/eng/source-build-patches/0001-Rename-NuGet.Config*.patch since macOS is case-insensitive OS. Would be good to be able to identify patches that are platform-compatible and have source-build skip them. Otherwise, Homebrew can continue removing incompatible patches as necessary.

Can track in #3149

[Triage] @crummel, please take a look at these, comment which ones should be pushed upstream and note if there are any related tracking issues.

[ ] Build failure on macOS ARM due to osx-x64 override. The following is the patch we use to allow using osx-arm64. If acceptable, I can create PR in dotnet/installer:

This looks good to me as an installer patch.

[ ] Build failure on macOS due to missing ILAsm/ILDAsm. This seems to be common issue on Linux too. The odd thing though is that RuntimeOsxArm64MicrosoftNETCoreILAsmVersion exists but RuntimeOsxX64MicrosoftNETCoreILAsmVersion doesn't, so needed to use Linux's version for x64. Not sure if this should be added, or if this is a .NET packaging issue that will be fixed. (EDIT: In 6.0.103, need to use Linux versions for osx-arm64 too) e.g.

The missing package is probably because we aren't building for OSX, so the packages never get fed into the previously-source-built set of packages.  I believe this means you'll be using prebuilt versions of ILAsm/ILDAsm in at least your first build; after that you can save off the produced packages and use them for future builds (this is similar to what Fedora does).  In the (very-) long-term we will probably build on OSX again but we don't have the bandwidth to look at it right now.  So in summary I don't think you need this as a permanent patch if you're going to be collecting the packages and managing your own previously-source-built.  Otherwise I think this is fine to upstream to installer.

[ ] Error MSB4018 while building 'installer in tarball' due to trying to find aspnetcore-runtime-internal v6.0.0 rather than current. Need to find out why this is happening. The hack done is change MicrosoftAspNetCoreAppRuntimePackageVersion to MicrosoftAspNetCoreAppRuntimewinx64PackageVersion inside src/installer.*/src/redist/targets/GenerateLayout.targets

EDIT 1: May not be needed anymore in 6.0.103
EDIT 2: Actual, based on Homebrew PR, still needed on osx-x64 as looking for v6.0.2.

This is interesting and I wonder if it's another RID-related problem.  ASP.NET was updated in 6.0.103 so it's odd that it's looking for 6.0.2.  If you have a copy of your artifacts/obj/<arch>/Release/PackageVersions.props.pre.installer.xml handy that might be interesting to look at.

[ ] Needed to introduce GNU sed rather than default BSD sed. Not too important and can keep as build dependency, but may want to document if it remains hard requirement. The problem is due to sed -i usage in https://github.com/dotnet/arcade/blob/main/eng%2FSourceBuild.props#L38

We're also fine with changing this to BSD sed syntax (i.e. -ibak) since it's still compatible with GNU sed.  This could possibly be considered a regression actually, we used to do it in 3.1.

[ ] Temporary issue but need to manually remove src/nuget-client.*/eng/source-build-patches/0001-Rename-NuGet.Config*.patch since macOS is case-insensitive OS. Would be good to be able to identify patches that are platform-compatible and have source-build skip them. Otherwise, Homebrew can continue removing incompatible patches as necessary.

Yes, this is a bad patch and I hope to remove it soon - the PR is https://github.com/dotnet/arcade/pull/7549.
Thanks for finding these issues and writing them up!  Let us know if you run into any more issues and feel free to ping me or dotnet/source-build-internal if you open any PRs.

Hi @cho-m, would you mind opening a separate issue for the RID-related stuff (the ASP.NET and ILAsm versions)?  Then after the rest of the PRs are up we can close this one and chase those down separately.  Thanks!

Hi @cho-m, have you had any time to look at this?  Thanks again for tracking these issues down!

Sorry I haven't had much time to respond. I'll try to work on creating PRs and separate issues by this week or next.
I will note that GNU vs BSD sed issue is probably fixed in 7.0.0 with https://github.com/dotnet/arcade/commit/b8007eed82adabd50c604a9849277a6e7be5c971
While there is a new issue with dotnet-install script on 6.0 -- https://github.com/dotnet/install-scripts/issues/318

One thing for dotnet/installer patch, what is the original value of TargetRid on macOS? Is it possible to just skip the OverrideTargetRid like Linux instead?

Perhaps we should have a call on this to see if we can come up with a plan.
@cho-m @fel1x-developer @asbjornu
Sound good?

I'd like to be included too!

The need to remove the src/nuget-client.*/eng/source-build-patches/0001-Rename-NuGet.Config*.patch is being addressed in https://github.com/NuGet/NuGet.Client/pull/5414.

All issues in the original write-up have been fixed in .NET 8.0.  Closing.


Arrangement and execution of the meeting for implementation of GitHubInterface class that provides simple interface for PyGitHub library (issue #868 related)

The goal is to arrange and execute the meeting for implementation of GitHubInterface class that provides simple interface for PyGitHub library. The following things should be prepared:

[x] scope and schedule of meeting (in one week);

[ ] conducting team (in two weeks);

[x] guide or instructions with examples (one week before meeting);

[ ] announcement (in Slack and Teams channel) with basic information (conducting persons, date,scope,schedule) (one week before meeting);

[x] exemplary code in Jupyter (link) (one week before meeting).

DONE


Fonts are rendered with periodic subpixel blurring instead of being pixel-hinted

VSCode Version: 0.10.11
OS Version: Windows 7 x64 SP1

Initially I commented about it in #2043, but I guess it's worth opening a new issue.
Something is wrong with font rendering in VS Code, font widths seem to be fractional or hinting is not respected (I might be using the wrong term). Compare these renderings of the same string in Visual Studio 2015 and in VS Code:

Notice how vertical elements periodically loose pixel hintning and become blurry and then sharp again, and that VS Code renders the sample string one pixel shorter than VS2015.
Steps to Reproduce:

Set some strongly hinted font (I use Envy Code R) in settings.json
Type any string long enough to see vertical lines of symbols becoming progressively blurrier.

Seems related to this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=534732

possible dupe of #15181 ?

also possible dupe of #1896

Found a solution over at https://github.com/Microsoft/vscode/issues/1896#issuecomment-283858289

Todays VS Code insider build comes with Electron 1.6.x, would be interesting to hear if this update solves this issue for anyone: http://code.visualstudio.com/Download#insiders

This is an upstream issue (possibly within Chromium), and there are no known workarounds that we could implement on our side. This means there is no possible code change for us to do in VS Code sources to improve things.
To keep the number of issues in our inbox at a manageable level, we’re closing issues that have been on the backlog for a long time but haven’t gained traction or that are not actionable. Thank you for your time and understanding.


"No proc named" for existing proc

Trying to compile /vg/station, the following error occurs:
Error at code\names.dm:1:31: No proc named "file2list"

The relevant code in names.dm:
var/list/ai_names = file2list("config/names/ai.txt")

file2list is defined as:
/proc/file2list(filename, seperator="\n")
	return splittext(return_file_text(filename),seperator)

Maybe it has something to do with there being a number in the proc name, because it also occurs for the proc:
file2listExceptComments
defined as:
/proc/file2listExceptComments(filename, seperator="\n", comment_prefix="#", trim_all=TRUE)
	. = list()
	var/prefixlen=length(comment_prefix)
	for(var/line in file2list(filename,seperator))
		var/trim_line=trim(line)
		// Drop empty lines.
		if(trim_line == "")
			continue
		// Drop comments.
		if(copytext(trim_line,1,1+prefixlen)==comment_prefix)
			continue
		. += (trim_all ? trim_line : line)

Maybe it has something to do with there being a number in the proc name

The compiler correctly handles identifiers that contain numbers, so that's not the issue.
The issue is that the compiler is attempting to use the file2list() proc before it gets defined. Currently it resolves the values of global vars as soon as it encounters them, and code/names.dm is compiled before code/__HELPERS/type2type.dm where the proc is defined.

So processing _ earlier than alphanumerics would fix it? That seems like the it could be the reason why the folder is  __HELPERS instead of just helpers. DM has a similar issue with #defines, but that might be less avoidable.

The compiler already processes the files in the order they're #included in the DME, which is (typically) already set up by the Dream Maker software. Dream Maker includes the files alphabetically with _ coming first, but it also includes all the files in a folder before moving on to subdirectories.
Fixing the issue would require postponing the step of resolving global var values until after every global proc has been defined.

Dupe of another issue

This isn't a dupe of any issue

There's also an issue where:
40 var/wires = WIRE_RECEIVE | WIRE_PULSE
41
42 var/const/WIRE_RECEIVE = 1			//Allows Pulsed(0) to call Activate()
43 var/const/WIRE_PULSE = 2				//Allows Pulse(0) to act on the holder

errors Error at code\modules\assembly\assembly.dm:40:39: Unknown identifier "WIRE_PULSE"
Is this caused by the same or a similar thing? It seems like maybe BYOND defines all consts before evaluating the value of non-const vars.

Am I on the right track in thinking that order to fix this:
// TODO Nuke this pass
foreach (DMObject dmObject in DMObjectTree.AllObjects) {
    dmObject.CreateInitializationProc();
}

foreach (DMProc proc in DMObjectTree.AllProcs)
    proc.Compile();

in DMObjectBuilder.cs would need to be changed to put all of the unparsed var definitions into a list for all files, and then once all files are processed, go through that list and evaluate them?

Taking a deeper look at this, this is actually relatively easy to fix. The only thing that tries to resolve a var's proc call before it can be defined is this line, which could be replaced with a method that gets the proc's name without ever resolving the proc itself.

There's also an issue where:
40 var/wires = WIRE_RECEIVE | WIRE_PULSE
41
42 var/const/WIRE_RECEIVE = 1			//Allows Pulsed(0) to call Activate()
43 var/const/WIRE_PULSE = 2				//Allows Pulse(0) to act on the holder

errors Error at code\modules\assembly\assembly.dm:40:39: Unknown identifier "WIRE_PULSE" Is this caused by the same or a similar thing? It seems like maybe BYOND defines all consts before evaluating the value of non-const vars.

It's caused by a similar issue, though more difficult to fix. The OD compiler is trying to resolve the var's value immediately instead of waiting until every const is defined.
The solution for this is to postpone setting these variables' values until after this ProcessBlockInner() call. What makes this complicated is knowing when the var depends on a const that doesn't exist yet, and postponing it until after it is. Because of code snippets like this, it could even end up taking multiple iterations:
/var/const/A = B
/var/const/B = C
/var/const/C = D
/var/const/D = 1

Trying to compile that in BYOND results in:
code\test.dm:1:warning: B: use of B precedes its definition
code\test.dm:2:warning: B: definition is here
code\test.dm:2:warning: C: use of C precedes its definition
code\test.dm:3:warning: C: definition is here
code\test.dm:3:warning: D: use of D precedes its definition
code\test.dm:4:warning: D: definition is here

So maybe it wouldn't have be iterative.

Yes, but it does work, interestingly enough.

This no longer occurs and seems like it was fixed by #872.


"X" (formerly Twitter) flags the gitbook URL as potentially scammy.

I only got https://ebay.gitbook.io/mindpatterns posted on X using a URL shortener. Clicking the shortened link results in a warning page. When you choose to ignore the warning you get forwarded to the correct page.
Trying to post the un-obfuscated link results in an error.

I imagine it's because of the word ebay in the url.

Raised the issue through X.com support, with following ref details...
Case#<PHONE_NUMBER>
ref:00DA0000000K0A8.500Vp00000CyNXd:ref

Looks like the issue might have been fixed.


AM-2907  test RAS PR from ORM

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/AM-2907
Change description
Test hmcts/am-role-assignment-service#2005
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Closing this test PR as AM-2907 has been merged, see hmcts/am-role-assignment-service#2005.


Add autoScrollSelect option

Add option to disable auto scroll in multiple select.
In very long dropdowns, this feature jumps focus to lowest select option
when trying to toggle upper options. Disabling allows toggling of upper
options sequentially.

Hey, @jerram !
It looks like a bug in JCF library. I've fixed it in master branch. Please check, will it work for you?

Yep, can confirm that works a treat Sergey. Thanks mate! Ill close this pull request.


MultiReactiveSystem of bug?

GetTrigger function carried out before the end of the ctor, which is odd, is a bug?

Entitas versions:1.4.1

Hi,
it's not a but. ReactiveSystem base calls GetTrigger()
https://github.com/sschmid/Entitas-CSharp/blob/develop/Entitas/Entitas/Systems/ReactiveSystem.cs#L16-L17

oh.


An error occurred when I set batch_readahead = 0 for parquet ScanOptions

Describe the bug, including details regarding any error messages, version, and platform.
In arrow cpp version 8.0.0, the error message is "Could not read from readahead_queue". And the details are as follows:
Firstly, I set use_threads to false, batch_readahead to 0, and set batch_size, dataset_schema, project, and filter in setScanOptions();.
    // project & filter
    setScanOptions();

Secondly, I use ParquetFileFormat::ScanBatchesAsync function to scan a ParquetFileFragment.
Then I follow the code below:
    // parquetFileFormat is an object of ParquetFileFormat class
    // parquetFileFragment is an object of FileFragment class
    auto recordBatchIterator = arrow::MakeGeneratorIterator(
                                std::move(parquetFileFormat->ScanBatchesAsync(parquetScanOptions, parquetFileFragment).ValueOrDie()));
    std::shared_ptr<arrow::RecordBatch> recordBatch;
    auto recordBatch_res = recordBatchIterator.Next();
    std::shared_ptr<arrow::RecordBatch> recordBatch;
    if (recordBatch_res.ok())
        recordBatch= recordBatch_res.ValueOrDie();

Finally, during debugging, the error message in recordBatch_res is "Could not read from readahead_queue".
I found this error message in the SerialReadaheadGenerator class, probably because of the data structure util::SpscQueue<std::shared_ptr<Future>> readahead_queue_.
template <typename T>
using SpscQueue = arrow_vendored::folly::ProducerConsumerQueue<T>;

The size of the corresponding ProducerConsumerQueue class must be greater than or equal to 2, which is described in the code comments. Therefore, if I set batch_readahead to 0, the size of ProducerConsumerQueue is 1, and an error occurs when I read the parquet file.

src\arrow\util\async_generator.h  583
src\arrow\vendored\ProducerConsumerQueue.h  75

My requirement is not to use multithreading, but when I set use_threads to false, if batch_readahead * batch_size > the number of rows in a row_group which to be read, it will read multiple row_groups at the same time in the parquetFileFragment. This means that when I turn use_threads off, multithreaded reads still occur in my code. My existing code doesn't support multithreading, so it reads errors.
Then I want to set batch_readahead to 0, and the above error occurs, which may be a bug. So, could you please fix this bug or help me to avoid reading multiple row_groups at the same time?
Component(s)
C++

My requirement is not to use multithreading, but when I set use_threads to false, if batch_readahead * batch_size > the number of rows in a row_group which to be read, it will read multiple row_groups at the same time in the parquetFileFragment. This means that when I turn use_threads off, multithreaded reads still occur in my code. My existing code doesn't support multithreading, so it reads errors.

Most effort on threading has been to avoid using multiple threads for compute.  In 11.0.0 the threading controls for execution plans are improving and it should be easier to avoid using additional threads for compute.
However, there has not been much effort in avoiding multiple threads for read.  Is there a particular reason you want this?  I/O routines are blocking and I/O threads are typically going to be stuck in a waiting state for most of their life, not using up many resources.  If you are reading from an HDD then you might not see much of a performance hit.  However, just about any other type of disk will benefit from at least some parallel I/O.
One option you could try would be to change the I/O thread pool size to 1 using arrow::io::SetIOThreadPoolCapacity.
The fix is probably:
diff --git a/cpp/src/arrow/dataset/file_parquet.cc b/cpp/src/arrow/dataset/file_parquet.cc
index 0d95e1817..10a1ac8ce 100644
--- a/cpp/src/arrow/dataset/file_parquet.cc
+++ b/cpp/src/arrow/dataset/file_parquet.cc
@@ -471,6 +471,9 @@ Result<RecordBatchGenerator> ParquetFileFormat::ScanBatchesAsync(
                               reader, row_groups, column_projection,
                               ::arrow::internal::GetCpuThreadPool(), rows_to_readahead));
     RecordBatchGenerator sliced = SlicingGenerator(std::move(generator), batch_size);
+    if (batch_readahead == 0) {
+      return sliced;
+    }
     RecordBatchGenerator sliced_readahead =
         MakeSerialReadaheadGenerator(std::move(sliced), batch_readahead);
     return sliced_readahead;

Are you able to try this patch out?
I will have to get some tests added to get this merged in.

Ok, thanks for your help and solution!


Set P4est preferences before MPIPreferences

With #88 being merged, it might be necessary to first set the preferences and then the MPIPreferences if you want to use the new convenience functions because otherwise P4est.jl cannot be loaded if the MPIPreferences (with local OpenMPI) are set, but not the P4est preferences. This should not be necessary anymore once P4est_jll is correctly build for OpenMPI. For now I just adjust the instructions in the README. Additionally, the new functions are used to configure the packages for CI.

I enabled the debug mode for p4est since I observed this error also locally. This cannot be caused by this PR and looks like a bug in p4est? I try to reproduce this from C.


Enable myAccount status indicator

Describe the issue:
With this effort, myAccount can be enabled and disabled and hence the indicator has to work accordingly.
How to reproduce:

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

Closing the issue since this is done.


Authentication failure

I have migrated an old DSA (1 year+) deployment to the new one by copying the .dsa directory to the new VM and using deploy.sh script:
  ./deploy.sh -j 4  --assetstore PATH/.dsa/assetstore/ --cache 8192 -d  PATH/.dsa/db/ --logs PATH/.dsa/logs --port 9090 --user "USER" --password "PASS" --cli start
I get the following error:
...
TASK [provision : Wait for girder startup] *************************************
ok: [localhost]
TASK [provision : Wait for girder to report version] ***************************
ok: [localhost]

TASK [provision : Set worker broker setting] ***********************************

fatal: [localhost]: FAILED! => {"changed": false, "msg": "Could not Authenticate!"}
PLAY RECAP *********************************************************************
localhost                  : ok=12   changed=5    unreachable=0    failed=1    skipped=80   rescued=0    ignored=0

Any idea?
dsa_mongodb looks fine:
{"t":{"$date":"2023-07-11T16:45:52.252+00:00"},"s":"I",  "c":"NETWORK",  "id":4915701, "ctx":"-","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":17},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":17},"outgoing":{"minWireVersion":6,"maxWireVersion":17},"isInternalClient":true}}}
{"t":{"$date":"2023-07-11T16:45:52.256+00:00"},"s":"I",  "c":"CONTROL",  "id":23285,   "ctx":"-","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2023-07-11T16:45:52.258+00:00"},"s":"I",  "c":"NETWORK",  "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize."}
{"t":{"$date":"2023-07-11T16:45:52.260+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","namespace":"config.tenantMigrationDonors"}}
{"t":{"$date":"2023-07-11T16:45:52.260+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","namespace":"config.tenantMigrationRecipients"}}
{"t":{"$date":"2023-07-11T16:45:52.260+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"ShardSplitDonorService","namespace":"config.tenantSplitDonors"}}
{"t":{"$date":"2023-07-11T16:45:52.260+00:00"},"s":"I",  "c":"CONTROL",  "id":5945603, "ctx":"main","msg":"Multi threading initialized"}
{"t":{"$date":"2023-07-11T16:45:52.261+00:00"},"s":"I",  "c":"CONTROL",  "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1,"port":27017,"dbPath":"/data/db","architecture":"64-bit","host":"mongodb"}}
{"t":{"$date":"2023-07-11T16:45:52.261+00:00"},"s":"I",  "c":"CONTROL",  "id":23403,   "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"6.0.7","gitVersion":"202ad4fda2618c652e35f5981ef2f903d8dd1f1a","openSSLVersion":"OpenSSL 3.0.2 15 Mar 2022","modules":[],"allocator":"tcmalloc","environment":{"distmod":"ubuntu2204","distarch":"x86_64","target_arch":"x86_64"}}}}
{"t":{"$date":"2023-07-11T16:45:52.261+00:00"},"s":"I",  "c":"CONTROL",  "id":51765,   "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Ubuntu","version":"22.04"}}}
{"t":{"$date":"2023-07-11T16:45:52.261+00:00"},"s":"I",  "c":"CONTROL",  "id":21951,   "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"bindIp":"*"}}}}
{"t":{"$date":"2023-07-11T16:45:52.263+00:00"},"s":"W",  "c":"STORAGE",  "id":22271,   "ctx":"initandlisten","msg":"Detected unclean shutdown - Lock file is not empty","attr":{"lockFile":"/data/db/mongod.lock"}}
{"t":{"$date":"2023-07-11T16:45:52.263+00:00"},"s":"I",  "c":"STORAGE",  "id":22270,   "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"/data/db","storageEngine":"wiredTiger"}}
{"t":{"$date":"2023-07-11T16:45:52.263+00:00"},"s":"W",  "c":"STORAGE",  "id":22302,   "ctx":"initandlisten","msg":"Recovering data from the last clean checkpoint."}
{"t":{"$date":"2023-07-11T16:45:52.263+00:00"},"s":"I",  "c":"STORAGE",  "id":22297,   "ctx":"initandlisten","msg":"Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem","tags":["startupWarnings"]}
{"t":{"$date":"2023-07-11T16:45:52.263+00:00"},"s":"I",  "c":"STORAGE",  "id":22315,   "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=3455M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,remove=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=2000),statistics_log=(wait=0),json_output=(error,message),verbose=[recovery_progress:1,checkpoint_progress:1,compact_progress:1,backup:0,checkpoint:0,compact:0,evict:0,history_store:0,recovery:0,rts:0,salvage:0,tiered:0,timestamp:0,transaction:0,verify:0,log:0],"}}
{"t":{"$date":"2023-07-11T16:45:53.915+00:00"},"s":"I",  "c":"STORAGE",  "id":4795906, "ctx":"initandlisten","msg":"WiredTiger opened","attr":{"durationMillis":1652}}
{"t":{"$date":"2023-07-11T16:45:53.915+00:00"},"s":"I",  "c":"RECOVERY", "id":23987,   "ctx":"initandlisten","msg":"WiredTiger recoveryTimestamp","attr":{"recoveryTimestamp":{"$timestamp":{"t":0,"i":0}}}}
{"t":{"$date":"2023-07-11T16:45:53.993+00:00"},"s":"W",  "c":"CONTROL",  "id":22120,   "ctx":"initandlisten","msg":"Access control is not enabled for the database. Read and write access to data and configuration is unrestricted","tags":["startupWarnings"]}
{"t":{"$date":"2023-07-11T16:45:53.993+00:00"},"s":"W",  "c":"CONTROL",  "id":5123300, "ctx":"initandlisten","msg":"vm.max_map_count is too low","attr":{"currentValue":65530,"recommendedMinimum":1677720,"maxConns":838860},"tags":["startupWarnings"]}
{"t":{"$date":"2023-07-11T16:45:54.026+00:00"},"s":"I",  "c":"NETWORK",  "id":4915702, "ctx":"initandlisten","msg":"Updated wire specification","attr":{"oldSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":17},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":17},"outgoing":{"minWireVersion":6,"maxWireVersion":17},"isInternalClient":true},"newSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":17},"incomingInternalClient":{"minWireVersion":17,"maxWireVersion":17},"outgoing":{"minWireVersion":17,"maxWireVersion":17},"isInternalClient":true}}}
{"t":{"$date":"2023-07-11T16:45:54.026+00:00"},"s":"I",  "c":"REPL",     "id":5853300, "ctx":"initandlisten","msg":"current featureCompatibilityVersion value","attr":{"featureCompatibilityVersion":"6.0","context":"startup"}}
{"t":{"$date":"2023-07-11T16:45:54.027+00:00"},"s":"I",  "c":"STORAGE",  "id":5071100, "ctx":"initandlisten","msg":"Clearing temp directory"}
{"t":{"$date":"2023-07-11T16:45:54.089+00:00"},"s":"I",  "c":"CONTROL",  "id":20536,   "ctx":"initandlisten","msg":"Flow Control is enabled on this deployment"}
{"t":{"$date":"2023-07-11T16:45:54.090+00:00"},"s":"I",  "c":"FTDC",     "id":20625,   "ctx":"initandlisten","msg":"Initializing full-time diagnostic data capture","attr":{"dataDirectory":"/data/db/diagnostic.data"}}
{"t":{"$date":"2023-07-11T16:45:54.233+00:00"},"s":"I",  "c":"REPL",     "id":6015317, "ctx":"initandlisten","msg":"Setting new configuration state","attr":{"newState":"ConfigReplicationDisabled","oldState":"ConfigPreStart"}}
{"t":{"$date":"2023-07-11T16:45:54.233+00:00"},"s":"I",  "c":"STORAGE",  "id":22262,   "ctx":"initandlisten","msg":"Timestamp monitor starting"}
{"t":{"$date":"2023-07-11T16:45:54.237+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"/tmp/mongodb-27017.sock"}}
{"t":{"$date":"2023-07-11T16:45:54.237+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"<IP_ADDRESS>"}}
{"t":{"$date":"2023-07-11T16:45:54.237+00:00"},"s":"I",  "c":"NETWORK",  "id":23016,   "ctx":"listener","msg":"Waiting for connections","attr":{"port":27017,"ssl":"off"}}
{"t":{"$date":"2023-07-11T16:47:09.507+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:50292","uuid":"f88899bf-9164-41eb-8f9f-839498dcc135","connectionId":1,"connectionCount":1}}
{"t":{"$date":"2023-07-11T16:47:09.508+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn1","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:50292","client":"conn1","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:47:09.510+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:50300","uuid":"aa987c70-d033-4ced-97a5-aaf8bbfd3ae8","connectionId":2,"connectionCount":2}}
{"t":{"$date":"2023-07-11T16:47:09.511+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn2","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:50300","client":"conn2","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:47:09.511+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:50306","uuid":"28b190a1-29b6-4c21-b3b7-fbcda5e194d6","connectionId":3,"connectionCount":3}}
{"t":{"$date":"2023-07-11T16:47:09.512+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn3","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:50306","client":"conn3","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:47:16.782+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:50322","uuid":"af5fda2e-b840-4a88-baf8-83b7d9638233","connectionId":4,"connectionCount":4}}
{"t":{"$date":"2023-07-11T16:47:16.782+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn4","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:50322","client":"conn4","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:47:16.784+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:50330","uuid":"6bfe1fe4-b713-4554-86e4-f766493d40c2","connectionId":5,"connectionCount":5}}
{"t":{"$date":"2023-07-11T16:47:16.784+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn5","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:50330","client":"conn5","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:47:16.785+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:50342","uuid":"35aa685e-88ce-4086-9dc1-636fd86f7125","connectionId":6,"connectionCount":6}}
{"t":{"$date":"2023-07-11T16:47:16.786+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn6","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:50342","client":"conn6","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:47:47.828+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn6","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:50342","uuid":"35aa685e-88ce-4086-9dc1-636fd86f7125","connectionId":6,"connectionCount":4}}
{"t":{"$date":"2023-07-11T16:47:47.828+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn5","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:50330","uuid":"6bfe1fe4-b713-4554-86e4-f766493d40c2","connectionId":5,"connectionCount":5}}
{"t":{"$date":"2023-07-11T16:47:47.829+00:00"},"s":"I",  "c":"-",        "id":20883,   "ctx":"conn4","msg":"Interrupted operation as its client disconnected","attr":{"opId":1566}}
{"t":{"$date":"2023-07-11T16:47:47.829+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn4","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:50322","uuid":"af5fda2e-b840-4a88-baf8-83b7d9638233","connectionId":4,"connectionCount":3}}
{"t":{"$date":"2023-07-11T16:47:49.302+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:49032","uuid":"c7d37c06-7d58-4c99-9c34-d9259df6d17c","connectionId":7,"connectionCount":4}}
{"t":{"$date":"2023-07-11T16:47:49.303+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn7","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:49032","client":"conn7","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:47:49.305+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:49044","uuid":"25950aa2-30ba-432e-a6c6-f6d320b1a0fb","connectionId":8,"connectionCount":5}}
{"t":{"$date":"2023-07-11T16:47:49.306+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn8","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:49044","client":"conn8","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:47:49.306+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:49050","uuid":"729571ac-b7b4-4723-81d9-a9fe441df75f","connectionId":9,"connectionCount":6}}
{"t":{"$date":"2023-07-11T16:47:49.307+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn9","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:49050","client":"conn9","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:48:10.013+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn9","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:49050","uuid":"729571ac-b7b4-4723-81d9-a9fe441df75f","connectionId":9,"connectionCount":5}}
{"t":{"$date":"2023-07-11T16:48:10.013+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn8","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:49044","uuid":"25950aa2-30ba-432e-a6c6-f6d320b1a0fb","connectionId":8,"connectionCount":4}}
{"t":{"$date":"2023-07-11T16:48:10.013+00:00"},"s":"I",  "c":"-",        "id":20883,   "ctx":"conn7","msg":"Interrupted operation as its client disconnected","attr":{"opId":1934}}
{"t":{"$date":"2023-07-11T16:48:10.014+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn7","msg":"Connection ended","attr":{"remote":"<IP_ADDRESS>:49032","uuid":"c7d37c06-7d58-4c99-9c34-d9259df6d17c","connectionId":7,"connectionCount":3}}
{"t":{"$date":"2023-07-11T16:48:11.426+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:45490","uuid":"fb938d99-0a52-4c91-b961-4f1e12ddc11c","connectionId":10,"connectionCount":4}}
{"t":{"$date":"2023-07-11T16:48:11.427+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn10","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:45490","client":"conn10","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:48:11.429+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:45496","uuid":"d13b6edf-2422-4903-a296-127294f3d4ef","connectionId":11,"connectionCount":5}}
{"t":{"$date":"2023-07-11T16:48:11.430+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn11","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:45496","client":"conn11","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}
{"t":{"$date":"2023-07-11T16:48:11.434+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:45502","uuid":"2da84403-1a4c-472b-9176-dcc3a2cc4487","connectionId":12,"connectionCount":6}}
{"t":{"$date":"2023-07-11T16:48:11.434+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn12","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:45502","client":"conn12","doc":{"driver":{"name":"PyMongo","version":"3.13.0"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"5.19.0-1027-gcp"},"platform":"CPython 3.8.10.final.0"}}}

Credentials used with the deploy script are 100% OK.

It uses the provided admin username and password to set a value on the girder remote worker plugin.  By the time ansible is printing that message, the system should be up enough that you can visit it via web browser.  Can you see the remote worker plugin?  Can you change the broker setting manually using your credentials?

Thank you @manthey  for the fast reply!
I am able to get to the Girder, but unable to log in with the old credentials. Do you have any solution? The old deployment is running fine, but we want to migrate it to the cloud and would really like to preserve all the data, users, etc. I could do that last year when I moved from HDD to SSD. The same process (with probably much newer versions of sub-components is giving me a hard time now). The alternative is to transfer the data and annotations via API, but then we lose all the metadata (time & date) and it's also cumbersome.

Looks like dsa_mongodb does not have all the data, despite moving .dsa folder and pointing the right paths in the deploy script. Note also that in the old deploy, I have quite and old MongoDB (4.4.19).
Old deploy (note 20GB of data):
mongo "mongodb://localhost:27017/girder"

"New" deploy:
mongosh "mongodb://localhost:27017/girder" (newer MongoDB uses "mongosh" instead of "mongo")

So it looks like that also MongoDB was not picked up?

so as you noted, it could be the mongo database credentials may have
changed.  Although the girder database is there... no?  Although 308KB
seems kind of small..
On Tue, Jul 11, 2023 at 2:54 PM Dejan Štepec @.***>
wrote:

Looks like dsa_mongodb does not have all the data, despite moving .dsa
folder and pointing the right paths in the deploy script. Note also that in
the old deploy, I have quite and old MongoDB (4.4.19).
Old deploy (note 20GB of data):
mongo "mongodb://localhost:27017/girder"
[image: image]
https://user-images.githubusercontent.com/25041003/252764345-ffa8e3bc-9931-46bf-9361-1b7471c6251a.png
"New" deploy:
mongosh "mongodb://localhost:27017/girder" (newer MongoDB uses "mongosh"
instead of "mongo")
[image: image]
https://user-images.githubusercontent.com/25041003/252764584-2b9dbdd2-1293-4565-a50c-d49650ab3b12.png
So it looks like that also MongoDB was not picked up?
—
Reply to this email directly, view it on GitHub
https://github.com/DigitalSlideArchive/digital_slide_archive/issues/276#issuecomment-1631350962,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFODTWXRQYEOGJAUVTW6K3XPWOOPANCNFSM6AAAAAA2GJH22I
.
You are receiving this because you are subscribed to this thread.Message
ID: <DigitalSlideArchive/digital_slide_archive/issues/276/1631350962@
github.com>

--
David A Gutman, M.D. Ph.D.
Associate Professor of Pathology
Emory University School of Medicine

Should be 20GB as in the old deployment. I think that it just created a default new tables in Mongo as it couldn't somehow access the old mongo /db files. No credentials were used for mongo, as default. Credentials I think are only used for Girder

yeah--- I meant whether or not you can connect to mongo.  So when you start
up the docker with the docker-compose, you can try and also explicitly
choose an older version of mongo, just in case something weird happened
between the latest version and the one you were using.
Also, (obviously), make a copy of the your mongo directory, and run from
the copy...
What is likely happening though, is in the docker-compose file, not the
./db:/data/db line...   make sure that gets changed to ./.dsa:/data/db (or
wherever relative from where you are running the docker container the
database is living..
mongodb:
image: "mongo:latest"
# Set DSA_USER to your user id (e.g., DSA_USER=$(id -u):$(id -g))
# so that database files are owned by yourself.
user: ${DSA_USER:-PLEASE SET DSA_USER}
restart: unless-stopped
# Using --nojournal means that changes can be lost between the last
# checkpoint and an unexpected shutdown, but can substantially reduce
# writes.
#   Limiting maxConns reduces the amount of shared memory demanded by
# mongo.  Remove this limit or increase the host vm.max_map_count value.
command: --nojournal --maxConns 1000
volumes:
# Location to store database files
- ./db:/data/db
On Tue, Jul 11, 2023 at 4:39 PM Dejan Štepec @.***>
wrote:

Should be 20GB as in the old deployment. I think that it just created a
default new tables in Mongo as it couldn't somehow access the old mongo /db
files. No credentials were used for mongo, as default. Credentials I think
are only used for Girder
—
Reply to this email directly, view it on GitHub
https://github.com/DigitalSlideArchive/digital_slide_archive/issues/276#issuecomment-1631478276,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFODTTAEI2LJ3LPKILUGMDXPW2WLANCNFSM6AAAAAA2GJH22I
.
You are receiving this because you commented.Message ID:
@.***
com>

--
David A Gutman, M.D. Ph.D.
Associate Professor of Pathology
Emory University School of Medicine

I have moved to docker-compose deploy instead of my old deploy-docker.py. I have moved the asset in db files to /dsa/db etc. (so that the default paths in docker-compose were OK), and made sure that DSA_USER was set to the same PID. I have also used the same version of MongoDB. I have thus no idea what else can it be :(
I didn't add a user and pass, but if I understand correctly, it's not even needed, given that there already is an admin user in the db, which is not default.
no idea.

The mystery deepens...  so once the containers are running (docker ps), can
you exec into the docker container?  i.e.   'docker exec -it dsa-mongodb-1
bash'
I think that's what it is called, you can confirm by running 'docker ps'
and double checking the exact name given to it by the docker compose up
script..
Double check your data is actually in /data/db .. i.e. there's 20 gigs of
stuff there, not 300 kb.  Also it's possible there's just some weird
permission things so your dsa data directory is not readable by the DSA
user once or some other painful permission issue... at the very least
confirm that within the context of the dockercontainer, it's actually
pointing to /data/db ..
On Tue, Jul 11, 2023 at 6:30 PM Dejan Štepec @.***>
wrote:

I have moved to docker-compose deploy instead of my old deploy-docker.py.
I have moved the asset in db files to /dsa/db etc. (so that the default
paths in docker-compose were OK), and made sure that DSA_USER was set to
the same PID. I have also used the same version of MongoDB. I have thus no
idea what else can it be :(
I didn't add a user and pass, but if I understand correctly, it's not even
needed, given that there already is an admin user in the db, which is not
default.
no idea.
—
Reply to this email directly, view it on GitHub
https://github.com/DigitalSlideArchive/digital_slide_archive/issues/276#issuecomment-1631591502,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFODTQDV64QUMB7UOQ7EGDXPXHZZANCNFSM6AAAAAA2GJH22I
.
You are receiving this because you commented.Message ID:
@.***
com>

--
David A Gutman, M.D. Ph.D.
Associate Professor of Pathology
Emory University School of Medicine

Yes, I am inside dsa_mongodb
I have no name!@c1b106c14368:/$ du -sh /data/db/
20G	/data/db/

Shows that ./db is mounted inside dsa_mongodb...but...
then I go to MongoDB inside the same container:
mongo "mongodb://localhost:27017/girder"
and then execute "show dbs" and get:
> show dbs
admin   0.000GB
config  0.000GB
girder  0.001GB
local   0.000GB
>

So looks like new DB entries (empty) were created as the DSA is fully functioning, just fresh :) I did the exact same thing a couple of months ago and it worked with such a copy of MongoDB files. I don't want to touch now the old deployment, because probably it works due to still old images of either DSA or some dependency.

I have stopped the existing deployment, copied  DB files to the new VM...and then restarted the old deployment and it still works (with old images that were already there). But the copied db files on the new VM with the latest images (except for MongoDB I now have exact same version - 4.4.19)...mystery :)

I have managed to fix it, but it involved some go-arounds.
I have used mongodump to dump the existing DBs from the working deployment that I wanted to migrate. Note that this is not efficient, as mongodump results in much larger dump (e.g., 20GB resulted in 60GB BSON files).
I have then connected to the dsa_mongodb container on the new deployment, which did not "recognize" the before copied raw MongoDB /db files and have manually restored the content of the db by using the dump using mongorestore.
I could now log in to the new DSA using old credentials. All the data (labels, users) were preserved. The slides (copied assetstore) did not work initially, but the problem was that it expected the assetstore to be mounted in /opt/digital_slide_archive/assetstore instead of /assetstore, as default in the docker-compose configuration. I have just changed that and seem like I have successfully migrated the old DB to the new deployment.
I have used the same MongoDB version as in the old deployment (4.4.19). I haven't tried migrating with mongodump one could migrate to a newer MongoDB version. Probably not, as MongoDB4 and MongoDB5 should not be directly compatible. Same with 4-5-6.
This is not the fix. But gets the problem solved. I would be interested to know why the new DSA is not picking up simply copied MongoDB /db files. It just creates clean MongoDB tables.


Osher/mgmt 1038 - Should not allow to update hosts when the installation has started

MGMT-1038 prevent update while cluster is installing

The ticket says "after starting the installation", which is all of the states that I mentioned.  Also note that this relates to MGMT-923.
FYI @filanov

The ticket says "after starting the installation", which is all of the states that I mentioned. Also note that this relates to MGMT-923.
FYI @filanov

Agree with @avishayt

@avishayt @filanov   What about cluster in error ?

@avishayt @filanov What about cluster in error ?

same, can't update

@filanov can you please re-approve, had to push conflict fixes.

@filanov can you please re-approve, had to push conflict fixes.

done


Allow web pages to be referred during context creation

Now that we have different chats associated to a vscode workspace and its persisted . I can switch between the and build classified contexts. This is awesome.!
What I am missing is ability to refer to a web page like if I am building a rest api using fast api in python, then I want to use pydantic. I could possibly scrape the getting started page of pydantic and feed it into the context. This /web option would be a great idea to build context from the web page rather than copy it from the web.

Please see: https://github.blog/changelog/2024-10-29-web-search-in-github-copilot-chat-now-available-for-copilot-individual/


ES2015 "..." not supported?

Hi,
I love your package, it's great!  feature. My code fails to run in atom-runner. The code runs when using Babel test site.
var a = {
  street: "test",
  number: 3
}

console.log(a);

function update(obj) {
  return {
    ...obj,
   number: 32
  }
}

console.log(update(a))

I get this error:
    ...obj,
    ^^^

SyntaxError: Unexpected token ...
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:387:25)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module.runMain (module.js:447:10)
    at startup (node.js:140:18)
    at node.js:1001:3

Is it because there is not 100% support for all ES2016 features?

Looks like you're just using a version of Node.js that does not support your features. console.log(process.version) will tell you what you are running.
Atom-runner doesn't parse or execute your code directly, so this is not an issue with the plugin.


Fix ShellCheck errors

Pull Request
Related issue
Fixes #687
What does this PR do?

...

PR checklist
Please check if your PR fulfills the following requirements:

[ ] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[ ] Have you read the contributing guidelines?
[ ] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Closing this due to lack of answer


Check released before trying to stage/release to Maven

Right now, there are only a couple of service directories, ResourceManager and Spring, that aren't using ESRP release. Both have a large number of libraries and are waiting for ESRP batch release to be enabled. With retries, the logic is that when we fail the maven release we check to see if the library has already been released. As we saw yesterday, if Maven is having connectivity issues for publishing, this fails in such a way where it breaks out of the attempt and fails.
Check to see if the library has been released prior to staging/releasing. The IsMavenPackageVersionPublished takes roughly 1 second to complete and only checks the POM (POM is 100% required) and if that returns true, we then call Test-ReleasedPackage which checks all of the package artifacts (POM, jars, .md files) and their hashes. The reason for this is that Test-ReleasedPackage takes around 90 seconds to fail verification if the package hasn't been released but only takes about 25 seconds to verify if so. This alleviates the connectivity problem that staging/release can have with Maven't server on retries for libraries that have already been released.

Since this has already been tested and there's no pipeline for required checks for this file, I'm going to override check enforcer.

/check-enforcer override


Fix 6-pubsub dependency versions

Hold please! :hand:
ensuring that all projects build on this branch & making sure it merges with #25

LGTM.


show button only when swipe

Hi, i want to implement the 'swipe to reply' method like whats app, here is what i want to do:
https://youtu.be/DgsYAJtz74U?t=136
But the problem is i do not know how to hide/show the reply button based on swipe state, can u help? Thanks in advance
Im using FlatList (giftedChat) for chat message screen

I have the same question


Feature Request: Make extension browser compatible.

Extension currently will not work on web editors like github.dev. Ideally it should just be a change in the package.json unless there are incompatible dependencies.
https://code.visualstudio.com/api/extension-guides/web-extensions

Done in 0878cfa2d2500189887432deb3eea49821d4e3d0


#936 Refresh of Vacancy Page

What's included?
Update the UI of vacancies and vacancy details page when a candidate is not signed into the platform.
https://www.figma.com/proto/toOjVICtIYu5WmNbhJuyxm/JAC-Candidate-Profile?page-id=146%3A1970&node-id=1093%3A4988&viewport=-2547%2C1394%2C0.08&scaling=min-zoom&starting-point-node-id=1093%3A4988
Note: the BackToTop button will be applied to all pages to have a smooth scroll transition in the apply site.
Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?
Develop site: https://jac-apply-develop--pr939-feature-936-refresh-o1y9n24p.web.app
Staging site: https://jac-apply-staging--pr939-feature-936-refresh-yzsk3ino.web.app
Vacancies:

Go to vacancies page.
Check if the information shows properly in different advert types.
Check if the search functionality works properly.

Vacancy details:

Select a vacancy and click Vacancy details.
Check if the information shows properly in the vacancy details.
Check if the Expand all information, Collapse all information, Print all information, View more, and View less work properly.

Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
Additional context
Screenshot of vacancies:

Screenshot of vacancy details:

PREVIEW:DEVELOP

@warrensearle I have checked with @andrew-isaac that Relevant information (downloads) will not show if the advert type is basic.


Need support for linking kernel files

The build_runner generates kernel dill files modularly.  We need to be able to link these together into a single file to run on the VM.
Per @kmillikin , the intent was to just allow concatenation.  Per @natebosch and @jakemac53 , that does not work today.
Marking P1, as I believe this is blocking efficient execution of VM tests.

Note that this does appear to work in some scenarios, and hasn't been confirmed to be the problem with our modular kernel pipeline although it is something we suspect might be part of the problem.

@natebosch - can you confirm if this is an issue and refile to @kmillikin if it is?

The issue on the build side is https://github.com/dart-lang/build/issues/1428

@kmillikin - I think we need some help here. Repro steps at https://github.com/dart-lang/build/issues/1428#issuecomment-391054216

I will take a look.

For the VM we eliminate mixin applications by replacing them with normal classes, creating a forwarding constructor that calls the superclass constructor, and copying in all the method implementations from the mixed-in class.
This transformation is being applied, because the Object with ListMixin superclass of QueueList is transformed.  However, it does not have implementations of the method bodies.  Perhaps it was applied using the interface of ListMixin (we call it an "outline") instead of the implementation?
I see:
  abstract class _QueueList&Object&ListMixin<E extends core::Object = dynamic> extends core::Object implements col::ListMixin<que::_QueueList&Object&ListMixin::E> {
    synthetic constructor •() → void
      : super core::Object::•()
      ;
    get /* from null */ iterator() → core::Iterator<que::_QueueList&Object&ListMixin::E>
      ;

But I'd expect:
abstract class _QueueList&Object&ListMixin<E extends core::Object = dynamic> extends core::Object implements col::ListMixin<self::_QueueList&Object&ListMixin::E> {
  synthetic constructor •() → void
    : super core::Object::•()
    ;
  get /* from file:///[snip]/dart.git/sdk/sdk/lib/collection/list.dart */ iterator() → core::Iterator<self::_QueueList&Object&ListMixin::E>
    return new _in::ListIterator::•<self::_QueueList&Object&ListMixin::E>(this);

Perhaps it was applied using the interface of ListMixin (we call it an "outline") instead of the implementation?

Ah! So yes when creating the full kernel files I was using the outline kernel files of dependencies, because that will have better behavior in terms of build invalidation. I will try using the full kernel files for dependencies instead and see if that works.

Fyi with the latest sdk I started getting this - reverting back my merge of the latest sdk for now:
===== CRASH =====
version=2.0.0-edge.f034f14b636affeaf4b6d26ea93aa5564b12eb25 (Wed Jun 6 09:05:13 2018 -0700) on "linux_x64"
si_signo=Segmentation fault(11), si_code=1, si_addr=0x120
Dumping native stack trace for thread 3bc25
  [0x000000000086d028] Unknown symbol
  [0x000000000086d028] Unknown symbol
  [0x0000000000aad982] dart::DRT_InlineCacheMissHandlerTwoArgs(dart::NativeArguments)
  [0x00007f69a574085b] Unknown symbol
  [0x00007f69a5741bde] Unknown symbol
  [0x00007f69a7113627] Unknown symbol
  [0x00007f69a424ee80] Unknown symbol
  [0x00007f69a424c8ce] Unknown symbol
  [0x00007f69a424c30b] Unknown symbol
  [0x00007f69a5740ce3] Unknown symbol
  [0x000000000090ef10] dart::DartEntry::InvokeFunction(dart::Function const&, dart::Array const&, dart::Array const&, unsigned long)
  [0x0000000000c3f70c] dart::Compiler::EvaluateStaticInitializer(dart::Field const&)
  [0x00000000009aba25] dart::Field::EvaluateInitializer() const
  [0x0000000000ab4002] dart::DRT_InitStaticField(dart::NativeArguments)
  [0x00007f69a574085b] Unknown symbol
  [0x00007f69a424c21a] Unknown symbol
  [0x00007f69a424bece] Unknown symbol
  [0x00007f69a4249c93] Unknown symbol
  [0x00007f69a4248ed7] Unknown symbol
  [0x00007f69a5740ce3] Unknown symbol
  [0x000000000090ef10] dart::DartEntry::InvokeFunction(dart::Function const&, dart::Array const&, dart::Array const&, unsigned long)
  [0x0000000000c7556c] Dart_Invoke
  [0x00000000006fe7a6] dart::bin::DartUtils::ResolveScript(_Dart_Handle*)
  [0x00000000006e4fb4] Unknown symbol
  [0x00000000006e3d78] Unknown symbol
  [0x00000000006e338b] dart::bin::RunMainIsolate(char const*, dart::bin::CommandLineOptions*)
  [0x00000000006e440d] dart::bin::main(int, char**)
  [0x00000000006e4c49] Unknown symbol
-- End of DumpStackTrace

@kmillikin confirmed this works as long as I provide full outlines! Thanks :).


fcitx5-nord: init at unstable-2021-07-27, fcitx5-material-color: init at 0.2.1

Description of changes
Add two fcitx theme, both of them are already in archlinux extra repo, so I hope that it could help some people ^_^.
https://github.com/hosxy/Fcitx5-Material-Color
https://github.com/tonyfettes/fcitx5-nord
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 263319 run on x86_64-linux 1

2 packages built:

fcitx5-material-color
fcitx5-nord

I don't mind this being the PR that gets merged, I currently also have #263035 up

I don't mind this being the PR that gets merged, but please note that I currently also have #263035 up

Apologies. Would it be more acceptable if I add you as a Co-Author and maintainers, or I could also delete this package in this PR.

No worries :)
Let's use this PR, since it has more going for it. I'd be happy to co-maintain the package.

I don't have time to test this stuff right now. I'll test it in the upcoming days if it hasn't been merged already


bizarre pointer switching

@pubpub-zz
I have no idea what this is: the pointer is in drawing mode, but at certain areas of screen it turns into cursor Oo
https://user-images.githubusercontent.com/61389799/112223840-18123800-8c33-11eb-88e8-bb98f5490b12.mp4

I've got it : this is a side effect of in progress development : I'll fix it for official release : should occur tommorow or the day after


All notion.so subpages from their sitemap.xml are inherited on my website

I don't know whether it's a bug or a feature but when I add any subpage of notion.so which are listed here:
https://www.notion.so/sitemap.xml
i can see that subpage hosted under my domain. Is there any way to prevent it?
Example: https://patrykpalej.dev/blog/may-li-khoe

I noticed this for my site as well! It's so annoying. Have you found a solution yet?

I found a workaround but it's not too elegant. Still, probably nothing better would work.

Declare a constant somewhere on the top of the code (paths taken from sitemap.xml):

const EXCLUDE_PATHNAMES = ['/about', '/blog', '/careers', '/confluence', '/contact-sales', '/customers',
    '/desktop', '/educators', '/enterprise', '/evernote', '/guides', '/help', '/login', '/mobile', '/nonprofits',
    '/notes', '/pages', '/personal', '/pricing', '/product', '/projects', '/remote', '/security', '/signup',
    '/startups', '/students', '/teams', '/templates', '/web-clipper', '/wikis']

Put this to your custom script to avoid "Super sketchy" problem

const superSketchyUrl = 'b14645e57719428ba29e6357faefc1e9';
    if (document.URL.includes(superSketchyUrl)) {
        window.location=MY_DOMAIN;
        };

Put the following code to fetchAndApply function. I put it just before let response;:

 for (const path of EXCLUDE_PATHNAMES) {
        if (url.pathname.startsWith(path)) {
            return Response.redirect('https://' + MY_DOMAIN + '/', 301);
        }
    }

All this issue takes place even without using fruition, just with notion.site, co it's a Notion feature in general.
I advice you all to check https://anytype.io/en . It's an open source privacy friendly clone of Notion, currently in alpha stage. Maybe they will allow sharing to the web as well in the future.

Interesting. I've also heard about AnyType but still not sure whether they can be a CMS with custom domain. I'll try it out. Thanks!