setup needs administrator rights

Just a question. I installed a default setup on my system. I got twice a "configuration as an admin" dialog to allow writing into the registry for example.
Is this working for example on a machine without admin rights or does the setup stop in this moment, which would be a pitty.

this has to be done only once.
if you want to know if the config fails without admin rights simply click on cancel and see how the scripts behave.

No time for testing right now, but I will have a look before we finalize the release. As I do not have windows as OS such tests are a little low prio from my end.

Maybe we should allow a variable / property to disable stesp that need admin rights. Then such users can put this variable into their ~/devon.properties.

This is caused by the following two lines at the end of setup.bat:
call regedit.exe /s system/windows/cmd/devon-cmd.reg
call regedit.exe /s system/windows/power-shell/devon-power-shell.reg

This does not need admin right since only the current user's registry path is changed. I'd the message of the user account control would look different for admin rights.
Anyway it seems to work without the pop up, when the "newer" (less older) reg.exe were used:
reg import system/windows/cmd/devon-cmd.reg
reg import system/windows/power-shell/devon-power-shell.reg

Should be fixed with PR #183
@maybeec and @markusschuh you rock!
I will also add you as developers in the POM. Thanks for your contributions and making devon-ide better. I think we need some final testing and bugfixing and can then go for our first official release.

FYI: To be consistent, we should make the change for all places using regedit.exe:
This one was missed:
https://github.com/devonfw/devon-ide/blob/8aeb3b4713d60276c0978c23acb68274a1ab07b6/scripts/src/main/resources/scripts/command/ide#L178

Now complete.


update() requires filtering by the column being updated

When calling the update() function, it requires you to filter by the column being updated.
i.e. if I run the query SampleQuery::create()->filterById($id)->update(array("Information" => "New information"));, it returns 1, indicating a row was updated. However, checking the database information, nothing was actually updated. The Information column still contains "Old information" (the previous value).
In order to make the above query work, it would have to be ran as SampleQuery::create()->filterByInformation("Old information")->update(array("Information" => "New information")), which doesn't make sense.

Hi @guitarman0831 , which version did you use? i tried againts the master branch, and i can't produce the issue, here is the test case #941

2.0.0-dev

Wrong repo. Correct: https://github.com/propelorm/Propel2.


CAP_NET_BIND_SERVICE not working for port less then 1024

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description

I'm trying to bind port less then 1024 without root permission.
Steps to reproduce the issue:
What I've done is the following:

sudo setcap cap_net_bind_service=+ep /usr/bin/slirp4netns
podman run -it -p 990:990 arm32v7/debian bash

Describe the results you received:
Error: error from slirp4netns while setting up port redirection: map[desc:bad request: add_hostfwd: slirp_add_hostfwd failed]

Output of podman version:
Version:            1.6.2
RemoteAPI Version:  1
Go Version:         go1.13.3
OS/Arch:            linux/arm

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.13.3
  podman version: 1.6.2
host:
  BuildahVersion: 1.11.3
  CgroupVersion: v1
  Conmon:
    package: Unknown
    path: /usr/bin/conmon
    version: 'conmon version 2.0.2, commit: 65fe0226d85b69fc9e527e376795c9791199153d'
  Distribution:
    distribution: archarm
    version: unknown
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 10000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 10000
      size: 65536
  MemFree: 50843648
  MemTotal: 979066880
  OCIRuntime:
    name: runc
    package: Unknown
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc9
      commit: d736ef14f0288d6993a1845745d6756cfc9ddd5a
      spec: 1.0.1-dev
  SwapFree: 0
  SwapTotal: 0
  arch: arm
  cpus: 4
  eventlogger: journald
  hostname: alarmpi
  kernel: 4.19.83-1-ARCH
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: Unknown
    Version: |-
      slirp4netns version 0.4.2
      commit: 69153b0d1cb82216d6782179ff7c3c5e91c731a1
  uptime: 1h 14m 26.84s (Approximately 0.04 days)
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /home/alarm/.config/containers/storage.conf
  ContainerStore:
    number: 3
  GraphDriverName: vfs
  GraphOptions: {}
  GraphRoot: /home/alarm/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 12
  RunRoot: /run/user/1000
  VolumePath: /home/alarm/.local/share/containers/storage/volumes

slirp4netns is called from within the rootless user namespace.  CAP_NET_BIND_SERVICE in this case would apply to the unprivileged user namespace.
Closing the issue as running slirp4netns from the host user namespace is not a supported use case, but please keep commenting on the issue if you have more questions.
If you'd like to bind ports < 1024 as unprivileged you need to tweak /proc/sys/net/ipv4/ip_unprivileged_port_start


update code for upstream notifications plugin

FLPATH-1249
https://issues.redhat.com/browse/FLPATH-1249

converted to draft until orchestrator starts using the upstream notification plugin


Spoke vNET for Identity Subscription

The existing Enterprise-Scale Landing Zone Arm templates currenlty include an option to have an Identity Subscirption that can host Active Directory Domain Controlleers. A vNET spoke is created that is peered to the Hub vNET. Are there any plans to incorprorate this into the ALZ-Bicep modules?

Hey @gin1974,
You can do this today with the hubPeeredSpoke module 👍
This module was created from a discussion around the identity subscription also, it's worth a read if you're interested here: https://github.com/Azure/ALZ-Bicep/issues/173
Do you think we should call this out in our wiki a little more? If so, can you suggest a location in the wiki to call it out? 👍
Looking forward to hearing from you, but hopefully you can use the hubPeeredSpoke module right away to achieve your requirement 👍
Thanks
Jack

Thanks for the reply Jack. This is what I was looking for. Didn't see that in the closed feature requests. It would possibly be good to call this out here https://github.com/Azure/ALZ-Bicep/tree/main/infra-as-code/bicep/orchestration/hubPeeredSpoke and specify that this can be looped to create multiple hub-spoke peerings as per the option in the Enterprise-Scale ARM templates for the identity scubscription that often hosts DC's


renamed stat-based load balancer to least-latency

As a nitpicker, I have to point out that the package name is responsetime, and the class name is LeastLatency. Latency and response time, while often used interchangeably, are actually two different things :-)

As a nitpicker, I have to point out that the package name is responsetime, and the class name is LeastLatency. Latency and response time, while often used interchangeably, are actually two different things :-)

good catch, will fix it

@Ladicek fixed

Ah sorry, I wasn't clear. What you measure is actually response time, not latency :-) But then, as I said, the two terms are often used interchangeably, so as long as the codebase is internally consistent, it's fine. Nitpicker logging off :laughing:

Ah sorry, I wasn't clear. What you measure is actually response time, not latency :-) But then, as I said, the two terms are often used interchangeably, so as long as the codebase is internally consistent, it's fine. Nitpicker logging off

Hmmm... at first I just wanted to make it consistent. But maybe I should rename to least-response-time. It's not that long and closest to true (only omits the fact that we treat errors even worse than long response times)

@cescoffier how do you like least-response-time?

+1
On Tue 14 Sep 2021 at 21:40, Michał Szynkiewicz @.***>
wrote:

@cescoffier https://github.com/cescoffier how do you like
least-response-time?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/smallrye/smallrye-stork/pull/69#issuecomment-919458811,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADCG7OEQ76DANKENB42LK3UB6QLVANCNFSM5D7Y2ZYA
.


Update fsharp.core.unittests

Enable nunit from nuget for all OSS unittests
Update nunit to 2.6.4
Add iSurfaceArea verification for all profiles.
Separate SurfaceArea into separate project

Can you put your changes in a separate branch so that this doesn't get mixed in with the rest of what's happening on fsharp4? That's the normal PR workflow.
Seems like 2 unrelated things are happening here. Can you split this into 2 PRs?

Migrating to nuget
Changing the FSharp.Core surface area tests

I'm curious why a whole new test suite is needed just for the surface area test cases?  What is the problem with the existing approach? (granted I know it's a bit stale at the moment, but that's a small fix)

I can split it up sure.  The unit tests run against the specific fsharp.core, whereas the surface area test reflects over the target fsharp.core and compares the types and methods against a known good list.

@KevinRansom -  Ignore the AppVeyor failure, it wasn't properly configured.  If you'd like to re-run the job you can do that from https://ci.appveyor.com/project/KevinRansom/visualfsharp-radou/build/1.0.5 (since you have admin rights on the AppVeyor project)

@KevinRansom Could you add Don and Lincoln as users/collaborators at https://ci.appveyor.com/team (see http://help.appveyor.com/discussions/questions/569-allow-github-project-collaborator-to-configure-appveyor-project-configuration)? It will be easier if more people have access to the CI build.

I have a less invasive fix for the surface area guys, will send PR shortly. We just need to properly add them to the existing portable unit test suites.


ignore dropView method when view is null

Summary

In #20288, we solved com.facebook.react.uimanager.NativeViewHierarchyManager.dropView (NativeViewHierarchyManager.java:536) by adding codes that prevent to run method on view object when view.getId() is null.
But if view is null, view.getId() can make error about NullPointerException. So, I think dropView method  needs to check if view is null.
If you need more information, Please read #24346.
Changelog

[Android] [Fixed] - Ignore dropView method when view is null.
Test Plan

This issue is unpredictable bug so please just read code.
And You can see also #20288 related on this issue.

Please add description and changelog, so that release managers can prepare release notes easily. Thank you

Let me try this again…


fix(RELEASE-1004): fix various multi-arch issues

revert to using single oras_arg
properly obtain origin_digest with platform arg since we want manifest index image

let's hold off merging this until I complete tests for RHEL AI with OCI artifacts.


The download links for the export templates are broken.

When I click the link to download the latest version of the export templates (as of the last couple of weeks), I get a long page filled with garbled text instead of a file that downloads (Google Chrome, latest version on Win10 64 bit).
I'm not sure if this will be read, but the builds page says to report here.

This was due to a server configuration mistake (.tpz didn't have an application/zip MIME type so Chrome attempted to display it as text instead) and should be fixed now, please try again after clearing your cache.


mit-scheme fails to build on 10.11

Gist
Build fails both --without-x11 and no flags. Something about being unable to compute sizeof (intptr_t)?
Let me know if I can provide more info.

Hmmm, seems I didn't run xcode-select --install earlier... Build still fails, though, with some pretty strange config output...
gist

Found it!
mit-scheme is hard-coded to look for /Applications/Xcode.app, which doesn't exist for beta versions. Symlinking /Applications/Xcode-beta.app to /Applications/Xcode.app did the trick, and I presume changing the configuration script to look for Xcode-beta if Xcode isn't there would do the same thing.
The line in question is in mit-scheme-c-9.2/src/microcode/configure:5478. If I can figure out how patching works I'll see if I can't submit something...

Should the build work also when I don't have XCode.all but just the command line tools installed in
/Library/Developer/CommandLineTools ?

@MassimoLauria I'm not sure what exactly mit-scheme uses from xcode, but IIRC brew wouldn't let me build mit-scheme without it on 10.10

Same problem with @aw1621107
With only CLT fail to build, Xcode 7 fix it.
Thanks.

If they've hardcoded it to look for Xcode on build you'll need to have that on the system, aye. It might be worth reporting this upstream and finding out what parts of Xcode they need and whether the CLT is enough by itself.

Going to close this one out. There are a few formula that do this in the core and the advice is more or less if you encounter one, symlink the beta Xcode to /Applications/Xcode.app.
I've added a xcode build dependency so at least folks with the CLT installed and who try to install from source don't get magically elusive failure messages. You can still pour the bottle fine without needing Xcode.
Feel free to kick this upstream and ask if there's any way for them to remove the requirement on Xcode, which is a rather hefty requirement.

Submitted a bad feature request upstream, so hopefully it'll get fixed eventually


Thank you for this workaround... SVG issue.

I currently have a project that has globalCSS in npm components and this workaround is what I'm attempting to use.
Unfortunately, I also use the next-images package for important images of all file types (including SVGs).
No matter what, running next-global-css attempts to also parse SVG files and always errors with:
error - SyntaxError: Unexpected token '<'
Is there a way to exclude SVG files easily from next-global-css, or make it skip them entirely by default?

Hi @gfmjr, you can create repo or gist with reproduce this issue?

Here's what helped me
yarn add @svgr/webpack
next.config.js
const { patchWebpackConfig } = require('next-global-css')

module.exports = {
    webpack: (config, options) => {
        patchWebpackConfig(config, options);
        config.module.rules.push({
            include: /node_modules[\\/]@s7[\\/]ui-kit/,
            test: /\.svg$/,
            use: ['@svgr/webpack'],
        });
        return config;
    }
}

Hi @gfmjr, can you check this #12 (comment) solution work for you?

It's not the best solution, but it works.  We managed to resolved it in this fashion with a different package....  I probably could have made your solution work as well but we  had other repos using this already so stuck with what our team already knew.
`const withImages = require("next-images");
const withTM = require("next-transpile-modules")(['@design/system']);
const baseConfig = withImages({
... ,
webpack(config) {
return config;
}
});
module.exports = withTM({
...baseConfig,
}
);
`


GestureDetector groups / Listener group / GestureDetector links

The problem
I encountered a situation where I want to listen for pointerDown event on one widget and catch pointerUp on another widget.
But it's impossible. If I started tap on GestureDetector 1, I cannot end it on GestureDetector 2 (it will be considered like GestureDetector 1 tapCancel event). The same to the Listener widget. If I touched the screen on Listener 1, then Listener 2 knows nothing about a Listener 1`s pointer and will not catch the pointerUp event.
Use case
For example, I'm crafting a WeChat clone and want to send a voice message.
I press the button and hold it down, waiting for modal screen (overlay) to appear. It has 3 buttons: "send", "translate" and "cancel". And I want to release the tap on one of them.
It looks like a basic task, but I cannot find any ready-made solution for it. I'm thinking about workarounds like listening raw pointer data from SingletonFlutterWindow and using MouseRegion to check if I'm inside the certain widget and the pointer is down. But I want some simple solution out-of-the box.
Proposal
My idea is to introduce GestureDetectors groups.
You could connect GestureDetectors by tag. Say, if two or more GestureDetectors have the same tag, they are considered to be in the same group, and you can start the gesture on the one and to end it on the another. The same to Listeners.

Doesn't DragTarget help you?

Doesn't DragTarget help you?

How exactly it will help?
I should have some Draggable widget for it. But there's nothing to drag.
Any help is appreciated

@subzero911
Can you provide us a code sample representing your use case along with actual vs expected result, so that we can take a look and verify it properly ?
Thanks.

Doesn't DragTarget help you?

I tried DragTarget and it worked like charm.
I used LongPressDraggable with hapticFeedback on a button to simulate longpress (button has empty handler and is just a decoration). I also used an empty SizedBox as a feedback widget.
In DragTarget, onWillAccept is working as "onEnter" and onLeave is "onExit", and onAccept to perform some actions. What's enough for my tasks.


How to see widget hierarchy?

I'm using emacs, not intellj / vsc
is possible for me to see hierary tree of widget?

Widget tree is not a feature provided by the analysis server. That's coming from the an extension to the vm service protocol.
See https://flutter.github.io/devtools/cli for a supported option.


[SPARK-29152][CORE][2.4] Executor Plugin shutdown when dynamic allocation is enabled

What changes were proposed in this pull request?
Added a Shutdown Hook in executor.scala which will ensure that executor's stop() method is always called.

Why are the changes needed?
In case executors are not going down gracefully, their stop() is not called.

Does this PR introduce any user-facing change?
No.

How was this patch tested?
Manually

Can one of the admins verify this patch?

Can one of the admins verify this patch?

cc @dongjoon-hyun

ok to test

Thank you, @iRakson !

Test build #115373 has started for PR 26901 at commit b528283.

Merged build finished. Test PASSed.

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

Test build #115373 has finished for PR 26901 at commit b528283.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Retest this please

Test build #115383 has started for PR 26901 at commit b528283.

Merged build finished. Test PASSed.

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

Test build #115383 has finished for PR 26901 at commit b528283.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

I will check the issue.

Thank you, @iRakson !

 They all seem to be on the driver side, which is not touched by this PR, so it's unclear to me how the change here could cause those failures.
I can't reproduce the OOM locally, but if someone can and is able to attach a debugger or get a heap dump, it could help.

Retest this please.

Merged build finished. Test PASSed.

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

Test build #115521 has started for PR 26901 at commit b528283.

Test build #115521 has finished for PR 26901 at commit b528283.

This patch fails from timeout after a configured wait of 400m.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

According to the failure history, this PR always fails with Maven at the following. And, mostly, it causes non-OOM failures.
BarrierTaskContextSuite:
- global sync by barrier() call
- support multiple barrier() call within a single task *** FAILED ***
  org.apache.spark.SparkException: Job aborted due to stage failure: Could not recover from a failed barrier ResultStage. Most recent failure reason: Stage failed because barrier task ResultTask(0, 1) finished unsuccessfully.

That's what is reported on the UI.  From the latest timed out run:
===== TEST OUTPUT FOR o.a.s.scheduler.BarrierTaskContextSuite: 'support multiple barrier() call within a single task' =====

...

19/12/18 10:08:53.307 rpc-server-4270-2 ERROR TransportRequestHandler: Error sending result RpcResponse{requestId=6150562811854402958, body=NioManagedBuffer{buf=java.nio.HeapByteBuffer[pos=0 lim=47 cap=64]}} to /<IP_ADDRESS>:43378; closing connection
io.netty.handler.codec.EncoderException: java.lang.OutOfMemoryError: Java heap space
	at io.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:107)
	at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:716)
	at io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:708)

Oh, got it, @vanzin .

Ping, @iRakson .

Retest this please.

Retest this please

Test build #117970 has started for PR 26901 at commit b528283.

Merged build finished. Test PASSed.

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

Test build #117970 has finished for PR 26901 at commit b528283.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Retest this please.

Test build #118006 has started for PR 26901 at commit b528283.

Merged build finished. Test PASSed.

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

Test build #118006 has finished for PR 26901 at commit b528283.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build finished. Test PASSed.

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

Test build #121006 has started for PR 26901 at commit c7e969a.

@dongjoon-hyun @vanzin
Please take a look at this approach for solving this issue.
Earlier i was adding a shutdown hook in the executor.scala which calls stop() method of executors.
Instead of adding a shutdown hook, now i am passing StopExecutor call to executors before killing them. This way they will stop themselves on their own before being killed.
I think this approach is better than forcing a shutdown hook.

Test build #121006 has finished for PR 26901 at commit c7e969a.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please.

Retest this please

Test build #121038 has started for PR 26901 at commit c7e969a.

Merged build finished. Test PASSed.

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

Test build #121038 has finished for PR 26901 at commit c7e969a.

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

Merged build finished. Test PASSed.

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

gentle ping @dongjoon-hyun @vanzin

If this one is better, shall we update master and branch-3.0 first?
We had better be consistent in all active branches if there is no reason.

If this one is better, shall we update master and branch-3.0 first?
We had better be consistent in all active branches if there is no reason.

Yes. Actually that is what I was thinking as well. We should update it in master and 3.0 as well.
I have one doubt though.
Should I create a new JIRA and raise PR for that, I mean that way it will be better to track the changes ?

Since 3.0 is not released yet, you can create a follow-up PR like [SPARK-29152][CORE][FOLLOWUP] on master branch.

Since 3.0 is not released yet, you can create a follow-up PR like [[SPARK-29152](https://issues.apache.org/jira/browse/SPARK-29152)][CORE][FOLLOWUP] on master branch.

@dongjoon-hyun
I did not see this comment before creating another JIRA. :( I am extremely sorry.
Please review this PR

Test build #123827 has started for PR 26901 at commit 123f429.

Merged build finished. Test PASSed.

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

Test build #123827 has finished for PR 26901 at commit 123f429.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

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

Test build #123832 has started for PR 26901 at commit 123f429.

Test build #123832 has finished for PR 26901 at commit 123f429.

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

Merged build finished. Test PASSed.

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

retest this please

Test build #123844 has started for PR 26901 at commit 123f429.

Merged build finished. Test PASSed.

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

Test build #123844 has finished for PR 26901 at commit 123f429.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

@dongjoon-hyun @vanzin  I have tested this a couple of times, older approach of adding shutdownhook is working fine. Last failure is unrelated to this. Also about the other approach, I think Vanzin's comment is valid one. Covering all the executor exit scenarios can be difficult. This seems a better fix to our problem.

Test build #123847 has started for PR 26901 at commit 123f429.

Merged build finished. Test PASSed.

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

Test build #123847 has finished for PR 26901 at commit 123f429.

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

Merged build finished. Test PASSed.

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

cc @srowen

@dongjoon-hyun @vanzin Can we get this in 2.4 ?
I think now this is fine. It should not break the code.
I have already tested this multiple times.

Hi, @iRakson . So, this is your final decision and are you going to close #28254 ?
This PR looks like to be reverted into the original patch. In that case, we don't need #28254 , do we?

Hi, @iRakson . So, this is your final decision and are you going to close #28254 ?
This PR looks like to be reverted into the original patch. In that case, we don't need #28254 , do we?

Yeah, we don't need #28254 .

#28254 has been closed.

Unfortunately, this seems to break all branch-2.4 Jenkins jobs again.

https://amplab.cs.berkeley.edu/jenkins/view/Spark QA Test (Dashboard)/job/spark-branch-2.4-test-maven-hadoop-2.6/909/ (Failed)
https://amplab.cs.berkeley.edu/jenkins/view/Spark QA Test (Dashboard)/job/spark-branch-2.4-test-maven-hadoop-2.7/912/ (Still running with UT failures)
https://amplab.cs.berkeley.edu/jenkins/view/Spark QA Test (Dashboard)/job/spark-branch-2.4-test-sbt-hadoop-2.6/921/ (Failed)
https://amplab.cs.berkeley.edu/jenkins/view/Spark QA Test (Dashboard)/job/spark-branch-2.4-test-sbt-hadoop-2.7/923/ (Failed)

I'm still monitoring the Apache Spark Jenkins farm.

The situation is the same. There are OOM errors.
java.lang.OutOfMemoryError: OOM while handling another exception
	at org.apache.spark.executor.FetchFailureHidingRDD.compute(ExecutorSuite.scala:377)
	at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:346)
	at org.apache.spark.rdd.RDD.iterator(RDD.scala:310)
	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90)
	at org.apache.spark.scheduler.Task.run(Task.scala:123)
	at org.apache.spark.executor.Executor$TaskRunner$$anonfun$11.apply(Executor.scala:416)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1360)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:422)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
20/06/14 16:21:15.737 ScalaTest-main-running-ExecutorSuite INFO ExecutorSuite:

Sorry again, @iRakson . I fully understand you spent lots of time to make this contribution and the failed test cases passed individually and locally. However, we cannot keep this patch in branch-2.4 because this will hide all the other failures.
I admit that this is my bad because I reviewed and merged the same PR twice and reverted. With two tries, we proved that the original patch has some issue with branch-2.4 definitely. Instead of putting more efforts on this, shall we move on to use new Apache Spark 3.0.0 since we have 3.0.0 release now? Technically, the original bug is a behavior since Apache Spark 2.4.0.
For now, I'll revert this commit to recover branch-2.4. The hang situation looks worse than the other failures.

@dongjoon-hyun Its behaviour is pretty confusing. But yeah, if this is breaking branch again then we should not keep it. Yes, this patch failed twice so we must move on.
Thank you for actively monitoring this patch. :) :)

I know why. Here is the reason and the fix: https://github.com/apache/spark/pull/32748


cubed Array vs cubed.CoreArray

Hi, I'm just a bit confused by what the difference is between the Array object defined in cubed.array_api.array_object and the cubed.CoreArray that is returned by cubed.from_array and asarray. CoreArray doesn't implement the numpy API, but Array isn't importable from cubed's top-level namespace.
Is this deliberate or should things be changed so that the only type a user sees is Array?

This does seem wrong - thanks for raising it.

Is this deliberate or should things be changed so that the only type a user sees is Array?

Yes. Array should be the type in the the top-level namespace and the user-facing documentation. CoreArray is an internal implementation detail.


FILEUPLOAD-302: JUnit Jupiter migration

This PR upgrades the project's testing framework from JUnit 4.12 to the modern JUnit Jupiter 5.5.2.
Since JUnit 5 Jupiter is not backwards compatible to JUnit 4.x (or even JUnit Vintage), this PR is a bit large, even though most of the changes are merely cosmetic (such as changing the argument order,
see details below). In order to make the reviewer's task as easy as possible, this PR does not presume to use JUnit Jupiter's best practices and all its new functionality, but only to migrate the
existing tests with as little change as possible. Following PRs may want to improve the tests by using some of JUnit Jupiter's new features.
This PR includes the following changes:

Maven dependency changes:

junit:junit was replaced with org.junit.jupiter:junit-jupiter.

Annotations:

org.junit.jupiter.api.Test was used as a drop in replacement for org.juit.Test without arguments. See 3.i. for handling of @Test annotations with an expected argument.
org.junit.jupiter.api.BeforeEach was used as an drop in replacement for org.junit.Before.
org.junit.jupiter.api.AfterEach was used as an drop in replacement for org.junit.After.

Assertions:

org.junit.jupiter.api.Assertions' methods were used as drop in replacements for org.junit.Assert's methods with the same name in the simple case of an assertion without a message. In the case of an assertion with a message, org.junit.jupiter.api.Assertions' methods were used, but the argument order was changed - Assert's methods take the message as the first argument, while Assertions' methods take the message as the last argument.
org.junit.jupiter.api.Assertions' methods were used as drop in replacements for junit.framework.TestCase's methods with the same name in the simple case of an assertion without a message.
org.junit.jupiter.api.Assertions#assertThrows was used to assert that a specific exception was throws instead of an org.junit.Test annotation with an expected argument. As a side bonus, this change makes the tests slightly stricter, as now they can assert the exception was thrown from a specific line and prevent false positives where the test's "set-up" code accidentally threw that exception.

Parameterized tests:

FileUploadTest was rewritten with @ParameterizedTest and @MethodSource in order to gain an equivalent functionality of JUnit 4's Parameterized runner.

Coverage decreased (-2.3%) to 76.382% when pulling ebe28d4a6bb0229e0570d3594860773147aea89b on mureinik:FILEUPLOAD-302-jupiter-migration into 273cb114512f79dfe6cbce281a22976f174b588e on apache:master.

@kinow the failure in @coveralls above unveiled a mistake where I forgot to add @Test annotations after removing the TestCase dependency in StreamingTest (point 2.ii in the PR message).
It's fixed now, and the coverage is OK again.
(so pending a second review or merge based on the previous approval)

@mureinik Thank you for the PR. :-)
@kinow Thank you for the review. :-)

What benefit does Jupiter provide, apart from "We're using the latest, and greatest."?
Besides, doesn't Jupiter have a compatibility layer, tha would allow to update without changing the test classes?
(I think, it's called "Vintage".)


addToWaitList throws 403 error when target user has no playlists

If the bot tries to add a user to the waitlist, and the user has no playlists and/or songs, the bot crashes with this error in log:
Error: https://plug.dj/_/booth/add responded with 403 (FORBIDDEN
  at process.nextTick (D:\PhpstormProjects\HoRM\rockbot-v2\node_modules\plugapi\lib\client.js:625:39)
  at _combinedTickCallback (internal/process/next_tick.js:131:7)
  at process._tickCallback (internal/process/next_tick.js:180:9)

The error doesn't seem to be catchable. At least not like this:
try {
  data.from.addToWaitList();
}
catch (error) {
  bot.sendChat('Error adding a user to waitlist.');
  console.error(error);
}

You can use bot.moderateAddDJ with a Node-style callback instead:
bot.moderateAddDJ(data.from.id, function (err) {
  if (err) bot.sendChat('Error adding a user to waitlist.')
})

At first, I thought the issue is solved by your response, but apparently not. Even moderateAddDJ does the same thing.
bot.moderateAddDJ(data.from.id, (err) => {
  bot.sendChat('Error adding a user to waitlist.');
  console.error(err);
});

Again, bot crashes with:
/home/tom/PhpstormProjects/plug/rockbot-v2/node_modules/plugapi/lib/client.js:625
                                throw new Error(`${opts.url} responded with ${err.statusCode} (${err.statusMessage}`);
                                ^

Error: https://plug.dj/_/booth/add responded with 403 (FORBIDDEN
    at process.nextTick (/home/tom/PhpstormProjects/plug/rockbot-v2/node_modules/plugapi/lib/client.js:625:39)
    at process._tickCallback (internal/process/next_tick.js:176:11)

Process finished with exit code 1

The same thing happens if the boin tries to join itself with an empty playlist:
/home/kawaiibot/bot.js/node_modules/plugapi/lib/client.js:625
                                throw new Error(`${opts.url} responded with ${err.statusCode} (${err.statusMessage}`);
                                ^

Error: https://plug.dj/_/booth responded with 403 (FORBIDDEN
    at process.nextTick (/home/kawaiibot/bot.js/node_modules/plugapi/lib/client.js:625:39)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)


Add transformer String to VNode

Description
I contribute to yewprint. I use VNode as a type of some props and I want to allow the user to pass a component instead of just a String.
Example: https://github.com/cecton/yewprint/pull/55/commits/d2f5ee8442a01863adc78ee714f2dc41af2eb731
error[E0277]: the trait bound `yew::virtual_dom::VComp: yew::virtual_dom::Transformer<&str, yew::virtual_dom::VNode>` is not satisfied
  --> yewprint-doc/src/progressbar/mod.rs:84:35
   |
84 | ...                   label="Animate"
   |                             ^^^^^^^^^ the trait `yew::virtual_dom::Transformer<&str, yew::virtual_dom::VNode>` is not implemented for `yew::virtual_dom::VComp`
   |

In this example, I have try to use a VNode as a label and now I need to replace all the labels in my code with label=html!("Animate") and that in 31 places.
Checklist

[ ] I have run cargo make pr-flow
[x] I have reviewed my own code
[x] I have added tests

This, to me, feels too implicit given that a more explicit version already exists:
html! {
  <Comp label=html!("Cooperative") />
}

If you think that's too verbose for your use case you can create a dedicated type and implement the transformation for that.
struct MyWrapper(Html);
impl Transformer<Html, MyWrapper> for VComp {}
impl Transformer<&'_ str, MyWrapper> for VComp {}

struct Props {
  label: MyWrapper,
}

html! {
  <Model label=html!{ "works!" } />
  <Model label="also works" />
}

I'm mentoring @Yozhgoor , the PR was my idea 🙂
I forgot you can do html!("string"). In a node you can't do that so it feels counter intuitive. (html!(<div>"string"</div>) is invalid)
I guess this is fine by me. Thanks! We can close this PR if @Yozhgoor think it's ok.

(The wrapper thingy is a no go solution imo. It would introduce some specific magic to a library of yew, it will feel counter intuitive to the user)


Proposal: Use rc-style command escaping

Proposing to change the current command escaping, based on POSIX shell:

Words are delimited by unquoted whitespace;
A backslash \ escapes the next character;
Double-quotes " escape everything inside them, excluding backslashes;
Single-quotes ' escape everything inside them, including backslashes.

to the following scheme, based on the Plan 9 rc shell:

Words are delimited by unqouted whitespace;
Single-quotes ' escape everything inside them, except a run of two single quotes, which represent a literal '. (Note: an unquoted '' is an empty string, not a

Any use of \ can be replaced by surrounding the offending character (now only whitespace and single-quote qualify) in ', and doubling it if it was a single quote to begin with.
Examples

depeche\ mode becomes depeche' 'mode or 'depeche mode';
C:\\foo\\bar\\baz becomes C:\foo\bar\baz (no need to escape backslashes anymore!);
'I'\''m A Little Teapot' becomes 'I''m A Little Teapot'

Advantages

Much simpler and less redundant scheme;
Works better for Windows paths: now paths without spaces need absolutely no escaping;
Prods clients towards using the same schemes for encoding arguments, instead of getting bogged down in 'did I produce the most efficient encoding?';
Producing a literal single quote in single-quotes mode goes from the rather unwieldy '\'' (unquote, escape single-quote, requote) to the more palatable '';
Will almost certainly simplify the tokeniser code;
Easiest to do this sort of change before any more clients are coded.

Disadvantages

Less intuitive scheme for human clients (but they'd have to look up the fact that it's POSIX shell style anyway, so this is likely moot);
'Ew, Plan 9,' I hear you say (yes, I did find this style through Plan 9, but it's fairly general and well-suited on its own merits);
Yet another arguably-bikeshed code change.

Closing this: it was recently revisited, and the general opinion is still that it isn't worth it.  Besides, this is now a spec issue rather than a playd issue!


publishrelease/install.sh: install -d /usr/local/bin if it does not exist.

Maybe also warn that it's not in their path?

Warning for path settings requires a little more investigation. Gonna fix the bug where we do the wrong thing and said we did the right thing first...happy to revisit path setting afterwards.

SGTM.
On Thu, Feb 20, 2020 at 6:14 PM Aaron Son<EMAIL_ADDRESS>wrote:

Warning for path settings requires a little more investigation. Gonna fix
the bug where we do the wrong thing and said we did the right thing
first...happy to revisit path setting afterwards.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/liquidata-inc/dolt/pull/415?email_source=notifications&email_token=ABJAR3FSCPJ2R7ES5NDZPE3RD4FEBA5CNFSM4KYYQR5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMQZB5I#issuecomment-589402357,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJAR3FTQWNWIW2H2MNZU5TRD4FEBANCNFSM4KYYQR5A
.


Do not differentiate between empty and null span - rename macro.

Fixes https://github.com/Azure/azure-sdk-for-c/issues/1082
Also fixes https://github.com/Azure/azure-sdk-for-c/issues/1171

This is the rename and can be largely ignored for review:
Do not differentiate between empty and null span - rename macro. - https://github.com/Azure/azure-sdk-for-c/pull/1168/commits/e10cd875cb8b2bb70239a3bf108400d3859f426c
This is the important commit worth reviewing and folks should take a look at it:
Update all code paths that relied on az_span_ptr == NULL to differentiate between a null span and an empty span to use az_span_size == 0 - https://github.com/Azure/azure-sdk-for-c/pull/1168/commits/5bdc9d323897684fe2bc4ca50384734e0961a088

Should we update precondition macro (so that 0 can have null ptr, >0 can't), or review the existing preconditions we have in place?

I believe it already behaves this way.
I thought about removing the reliance on the null ptr check even in the preconditions, but given the preconditions also enforce that the span was correctly formed, I decided to leave it as is. Even though folks shouldn't rely on null ptr, we do create one with null (as an implementation detail) and are just using that fact within the precondition to validate well-formedness.

As a final user, can it happen that I want to know when az_span is not yet init/used  vs when it has already been?
// Creating az_span like this will let ptr = NULL and size = 0
az_span my_span;

// at this point I know my_span is empty

// say I call some functions or do stuff here
my_span = foo(...);
// OR
az_result = foo(&out_my_span);  // Do we ask/request to never use az_span* for out params?

// At this point my_span can still be empty. But ptr could be relevant for me.

I wonder if by letting AZ_SPAN_NULL and empty az_span be different we support more than one programing style for using az_span as a customer.

I wonder if by letting AZ_SPAN_NULL and empty az_span be different we support more than one programing style for using az_span as a customer.

I thought about this for a while. I don't see a concrete scenario where the user would want to rely on the NULL ptr which cannot be substituted for a size check that would be worth the trade-off for increased complexity and security scrutiny.
There is pretty big precedence with .NET and even Golang which have the semantic behavior proposed in this PR and issue, which increases my confidence on the design.

As a final user, can it happen that I want to know when az_span is not yet init/used vs when it has already been?

@vhvb1989 - let me know if you have some other thoughts and scenarios on this issue and I will work with you to resolve them, or at least understand it. For now, merging this PR since it impacts API surface.

Test reply from email.
From: Anton Kolesnyk<EMAIL_ADDRESS>Sent: Monday, August 31, 2020 11:16 AM
To: Azure/azure-sdk-for-c<EMAIL_ADDRESS>Cc: Ahson Khan<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [Azure/azure-sdk-for-c] Do not differentiate between empty and null span - rename macro. (#1168)
@antkmsft approved this pull request.
Should we update precondition macro (so that 0 can have null ptr, >0 can't), or review the existing preconditions we have in place? I remember, in particular in url-encode code (or was it base64?) where we distinguish between 0-length spans with NULL ptr, and ones with 0-size and non-NULL ptr, and disallow one of them.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-c%2Fpull%2F1168%23pullrequestreview-478835281&data=02|01|ahkha%40microsoft.com|29e5a8f5ef214d4f65dc08d84dd9e0a0|72f988bf86f141af91ab2d7cd011db47|1|0|637344945453578234&sdata=EVjvWSJNOXqC0vk0g%2B9m%2BcNoTXFkT2J2KM%2BElJuvl0g%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABRZRIOM2E7J3BSMNGX2QFLSDPSE7ANCNFSM4QOQKCIA&data=02|01|ahkha%40microsoft.com|29e5a8f5ef214d4f65dc08d84dd9e0a0|72f988bf86f141af91ab2d7cd011db47|1|0|637344945453578234&sdata=qWQWn4CG9X%2Bv1AMFN05bU%2BCDZk0R%2FBUveCwsvOfmbFo%3D&reserved=0.


Add Fair loss

http://research.microsoft.com/en-us/um/people/zhang/INRIA/Publis/Tutorial-Estim/node24.html
TODO:

[ ] merge & rebase #178

Hi @henry0312, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@guolinke ready for review :)


Add support for AWS/MWAA metrics

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
Autodiscovering AWS/MWAA not supported.
https://docs.aws.amazon.com/mwaa/latest/userguide/accessing-metrics-cw-container-queue-db.html
this is about the AWS / MWAA service, do not confuse with Amazon / MWAA these are different services.
AmazonMWAA - supported
https://docs.aws.amazon.com/mwaa/latest/userguide/access-metrics-cw-202.html
What might the configuration look like?
No response
Anything else?
No response

Is there any update on this?
Airflow internal metrics are supported now

But the resources utilization metrics

are not supported?
Can this be added?

This is supported now.


BuildExecutable use-case question

Thanks for making this package.
I am relatively new to Julia and am trying to get rid of the JIT overhead in my application.
Is it true, if I use BuildExecutable and upon using the executable, I should get no JIT overhead ? So basically mimic a 2nd time call to the script (like we do for benchmarking) ?
thanks!

I'm pretty sure you will still have the JIT overhead based on the discussion here, but @dhoegh can confirm.

@amellnik Thanks, does that mean that BuildExecutable does not do a static compilation ? I am trying to see how I can remove the JIT overhead from my application. I don't use any dynamic features like (@eval) etc.

That's my understanding -- see for example @ChrisRackauckas's post here.  All this package does is bundle julia along with the script in an executable.

Yes that's correct and hence it will still require jit compilation of the methods. But technically you could get rid of the jit, by ensuring all functions in a module is precompiled with the correct arguments and having type stable functions, but that's true for any module with precompilation on.

@amellnik , @dhoegh Thanks, I see.
What do you guys think about this post from @vtjnash ?
It lays out a way to achieve static compilation, but looks little daunting.

@amellnik , @dhoegh Thanks, I see.
What do you guys think about this post from @vtjnash ?
It lays out a way to achieve static compilation, but looks little daunting.

Yeah, static compilation works (in many cases), and you can follow that to do it. What we really need is someone to make a package that makes static compilation easier. That just requiring really figuring out how to do it, and automating some of the steps. Since it's all nicely laid out in one giant blog post, the "hard" work is already done, and the icing needs to be added.

I just found this package based on @ChrisRackauckas's discourse post and I have a question about usage. So the use case I have is to bundle a julia script into an EXE that users on Windows can use "without installing anything" I don't know the exact definition of "without installing anything" on windows.  But I know that using an administrator account to modify some system files definitely won't fly. It doesn't matter if the julia runtime and LLVM come with that EXE, either way it satisfies the constraints.
Will BuildExecutible.jl work for such a use case? Namely, make an EXE that you can run with a double click without an Admin account?


docs/filter: only filter categories with a full match

i feel this filtering logic serves the majority of use cases better
before:

after:

i agree
:cow2:

:deciduous_tree:

Yup.  There was talk about adding the ability to search by something like 'cat:Function', and maybe we'll get there some day, but this is definitely an improvement.


Uncatched IndexError at mdformat_myst/_directives.py", line 104, in parse_opts_and_content

Describe the problem
Using a fresh install of mdformat-myst (mdformat 0.7.11 (mdformat_frontmatter: 0.4.1, mdformat_myst: 0.1.4, mdformat_tables: 0.4.1)) on a complex and broken md file (see steps to reproduce bellow) throw this exception:
raceback (most recent call last):
  File "/home/biapy/.local/bin/mdformat", line 8, in <module>
    sys.exit(run())
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/__main__.py", line 8, in run
    exit_code = mdformat._cli.run(sys.argv[1:])
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/_cli.py", line 74, in run
    formatted_str = mdformat.text(
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/_api.py", line 29, in text
    rendering = mdit.render(md)
  File "/home/biapy/.local/lib/python3.9/site-packages/markdown_it/main.py", line 275, in render
    return self.renderer.render(self.parse(src, env), self.options, env)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/renderer/__init__.py", line 56, in render
    return self.render_tree(tree, options, env, finalize=finalize)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/renderer/__init__.py", line 90, in render_tree
    text = tree.render(render_context)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/renderer/_tree.py", line 11, in render
    text = renderer(self, context)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/renderer/_context.py", line 48, in render_children
    return separator.join(child.render(context) for child in node.children)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/renderer/_context.py", line 48, in <genexpr>
    return separator.join(child.render(context) for child in node.children)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat/renderer/_tree.py", line 11, in render
    text = renderer(self, context)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat_myst/_directives.py", line 64, in fence
    code_block = format_directive_content(code_block)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat_myst/_directives.py", line 75, in format_directive_content
    parse_result = parse_opts_and_content(raw_content)
  File "/home/biapy/.local/lib/python3.9/site-packages/mdformat_myst/_directives.py", line 104, in parse_opts_and_content
    line = lines.pop(0)
IndexError: pop from empty list

Link to your repository or website
No response
Steps to reproduce
Running this command with additions-to-a-default-ubuntu-install.md:
~/.local/bin/mdformat  'additions-to-a-default-ubuntu-install.md'

The version of Python you're using
3.9.7
Your operating system
Lubuntu 21.10
Versions of your packages
No response
Additional context
The markdown is partially generated using Clipboard 2 Markdown and copy pasting content from Compléments à l'installation d'Ubuntu

Thanks the is an issue with the mdformat-myst plugin so I've transferred the issue.
I'm fairly sure this will be fixed by https://github.com/executablebooks/mdformat-myst/pull/12

Hi, i confirm #12 fix the issue.

Fixed in https://github.com/executablebooks/mdformat-myst/pull/12


Mounting a writable existing persistent disk?

I've had some good successes with mounting existing read-only persistent disks to the VM running a dsub job, and its very cool that one can do this.  However I was wondering about attached writable disks.  According to the Life Science API documentation:

If all Mount references to this disk have the readOnly flag set to true, the disk will be attached in read-only mode and can be shared with other instances. Otherwise, the disk will be available for writing but cannot be shared.

I'm not exactly sure what they mean by Mount references.  Do they mean that the disk is attached to zero or more VMs in read only mode?  As that would seem to be what is implied by the description.  (I'm not sure how outside of the VM that GCP would explicitly know how the disk is actually mounted).  I've done some testing with a persistent disk that's unattached to any VMs, and one that was already attached in read only mode to a VM and in either case when I launch a dsub job the persistent disk is always attached in read only mode regardless.

By Mount reference I'm assuming they mean this object in the request: https://cloud.google.com/life-sciences/docs/reference/rest/v2beta/projects.locations.pipelines/run#mount . There is a read-only flag here.
For persistent and existing disks, dsub always mounts this read-only (e.g. https://github.com/DataBiosphere/dsub/blob/main/dsub/providers/google_v2_base.py#L721). We do briefly mention that resource data can be mounted read-only: https://github.com/DataBiosphere/dsub#mounting-resource-data
The idea is that these disks contain resource data to be used as inputs for your workflows, so it made sense for dsub to mount as read-only. Would you mind describing your use case for mounting these disks as writable?

Yep that's what I was referring to in regards to Mount reference.  Later in that same document it goes on to talk about existing disks and if the readOnly flag is true or not.  After rereading the description in the context of the previous section, maybe it was restating just in a different way that you can only attach a writable compute disk to a single VM (usually that is).  I was just inferring something different out of the documentation.
I would heartily agree that it almost always makes sense for dsub to mount as read-only for resource/reference data.  I was chaining together an analysis that could benefit from having a shared persistent disk for performance where one step collectively operated on a set of large files and then executed a second step that used the combined result from the first step and each individual file.  The second step of course is very easily run in parallel using dsub.  Since I have to copy all of the files out of GCS for the first step, using a persistent disk here would save having to copy the files twice out of storage. And there are more downstream steps on the whole and individual results from the first two steps.  But what I was really just trying to make setting up the resource/reference disk part of the whole process to make it easier to maintain.


Put kotlin-stdlib to compile scope

If I'm not mistaken, one should only use testCompile scope for the libraries that are only useful in tests.
(Admittedly I changed this as a workaround because Intellij expected it. But after thinking twice I consider it reasonable)
This is pretty trivial so I didn't doc it.

We did it on purpose to ease usage of different Kotlin versions - KTX users have to explicitly declare dependency on a specific Kotlin standard library version and we do not want to override that. If I'm not mistaken, Gradle (for example) always chooses the newest library version that was declared either by your script or one of your dependencies. This isn't an issue as long as KTX depends on the same or an older Kotlin version - but we do not want to force the users to use a newer Kotlin version if they do not want that, for whatever reason.
KTX libraries that do not need Kotlin standard library features - and rely only on the basic language syntax - do not depend on it at all. Other libraries use include it as provided dependency.


fix drawer onscoll event override issue by using addEventListener

#762 hello @katspaugh, please help review my pull request. Thanks!

Thanks a lot!


plan policy logic

In app/policies/plan_policy.rb initialize method
we have this line
plan || plan.publicly_visible?
Shouldn't it be plan && plan.publicly_visible?
because we will only get to the .publicly_visible? part only if plan exist but the logic state if plan exist then just return true so the second part is redundant.

@Yu-Chieh-Henry-Yang agreed, this logic is wrong.
https://github.com/DMPRoadmap/roadmap/blob/master/app/policies/plan_policy.rb#L7
@xsrust @briri Shouldn't a Plan also be visible to some Users when its visibility is organisationally_visible?.

@briri @xsrust not sure whether this is still an issue? can we close?


Why do you parse HTML pages?

I can't understand: why do you parse HTML pages from social networks instead of using API to grab information?
All hidden information in social network pages contains in API responses.
Using API much faster and easier to code.
Sorry, if I don't understand project's philosophy, but I read README several times and tried to understand it :(

The reason is that to get all information for some account through API you need to know it's internal id in this network. And for most methods – access token, received in a moment when your user authorizes your application. But what if you have only your access token and link to someone's profile? You can just use ids_please to get an internal id and use it in public API methods with your access token to get his feed for example. Or you don't have to have your own application at all to make requests to social network and just get info from parsing HTML page in a unified way from any social network ids_please knows how to grab.

Ok. I'm understood :+1:
Wait for PRs 😉

Also, if you can help me with clarifying readme – it would be great. Maybe we need to provide some clear examples

Yes, I'll try.
I had this question, because AFAIK for all information, which your app grabs, there is no need access token. Also, by passing link to social network's API, it's available to get this information

for example:
https://instagram.com/developer/endpoints/users/#get_users you need an ID and access token
https://developers.facebook.com/docs/graph-api/reference/user - you should have an ID and access_token (http://graph.facebook.com/v2.4/1322232597)
https://vk.com/dev/users.get - you should have an ID or screen name that can be parsed from a link but you'll receive not full info, just full name and id.
etc..
Of course with some social networks, you can work writing own small scripts. But why if there is a small gem without a lot of dependencies which doing the same stuff in one way for many social networks? You just feed it with array of links and get all information

Ok. I didn't work with Instagram and FB APIs and don't know about it
And I'm agree with you about a lot of rubygems' dependencies
I have thoughts how I can clarify it in README.


Handle internal resources in builtin scoped authorizer

Description
We do not checked internal resources returning error scope checker for them while thy should be handled as normal resource.
Testing Performed
CI

Current dependencies on/for this PR:

master

PR #2800   👈

PR #2726

PR #2722

PR #2750

PR #2751

PR #2752

PR #2774

PR #2775


Support inline locking too

I think Sidekiq lock should still allow workers to be run inline. Locking behavior should be the same
via Worker.new.perform(args)
As of right now lock is nil.
I'm implementing this functionality now. Hopefully you wont mind it being merged back in
Thanks

Hello @jacquescrocker
Right now as you said it won't work as the lock method is defined using sidekiq's middleware; but I'm not sure what would be the real-life use-case here 🤔 can u plz elaborate?

@jacquescrocker I believe you only need the middleware setup before testing your workers in inline mode.
require "sidekiq/testing"
require "sidekiq/lock/testing/inline"
require "sidekiq/lock/middleware"

RSpec.configure do |config|
  config.before(:all) do
    Sidekiq::Testing.server_middleware do |chain|
      chain.add Sidekiq::Lock::Middleware
    end

    Sidekiq::Testing.inline!
  end
end

With this, your lock should work as expected.
https://github.com/mperham/sidekiq/wiki/Testing#testing-server-middleware

Thx for feedback @emaiax <3
I suppose we can close this stale issue 😅


Amplify Gen2 Deploy fails when referencing Functions or Storage

Environment information
System:
  OS: macOS 14.1
  CPU: (8) arm64 Apple M3
  Memory: 173.72 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.13.1 - ~/.nvm/versions/node/v20.13.1/bin/node
  Yarn: undefined - undefined
  npm: 10.8.2 - ~/.nvm/versions/node/v20.13.1/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 1.0.4
  @aws-amplify/backend-cli: 1.1.1
  aws-amplify: 6.4.0
  aws-cdk: 2.149.0
  aws-cdk-lib: 2.149.0
  typescript: 5.5.3
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
Can anyone help here, as soon as i attempt to add services like Storage or Functions, it fails to build. Runs locally on sandbox fine, no typescript errors. Not even trying anything fancy just importing the libraries into the build.
Build below:

0

2024-08-07T07:28:20.063Z [INFO]: # Cloning repository: git@github.com:milesmarshall/amplify-vite-react-template.git

1

2024-08-07T07:28:21.125Z [INFO]:

2

2024-08-07T07:28:21.125Z [INFO]: Cloning into 'amplify-vite-react-template'...

3

2024-08-07T07:28:21.125Z [INFO]: # Switching to commit: 95575f4ba27ea4c26e9dde40557e2be2ce053e1e

4

2024-08-07T07:28:21.140Z [INFO]: Note: switching to '95575f4ba27ea4c26e9dde40557e2be2ce053e1e'.

5

You are in 'detached HEAD' state. You can look around, make experimental

6

changes and commit them, and you can discard any commits you make in this

7

state without impacting any branches by switching back to a branch.

8

If you want to create a new branch to retain commits you create, you may

9

do so (now or later) by using -c with the switch command. Example:

10

git switch -c <new-branch-name>

11

Or undo this operation with:

12

git switch -

13

Turn off this advice by setting config variable advice.detachedHead to false

14

HEAD is now at 95575f4 added storage

15

2024-08-07T07:28:21.217Z [INFO]: Successfully cleaned up Git credentials

16

2024-08-07T07:28:21.218Z [INFO]: # Checking for Git submodules at: /codebuild/output/src3867197661/src/amplify-vite-react-template/.gitmodules

17

2024-08-07T07:28:21.225Z [INFO]: # Retrieving environment cache...

18

2024-08-07T07:28:21.277Z [INFO]: # Retrieved environment cache

19

2024-08-07T07:28:21.278Z [INFO]: ---- Setting Up SSM Secrets ----

20

2024-08-07T07:28:21.278Z [INFO]: SSM params {"Path":"/amplify/d2ihq7kuu4ddhp/main/","WithDecryption":true}

21

2024-08-07T07:28:25.277Z [INFO]: # Patching NPM package '@aws-amplify/cli' from 12.8.2 to 12.12.6...

22

2024-08-07T07:29:04.972Z [INFO]: # Installed '<EMAIL_ADDRESS>
23

2024-08-07T07:29:05.085Z [INFO]: # Done patching NPM package '@aws-amplify/cli' to version 12.12.6

24

2024-08-07T07:29:05.091Z [INFO]: # Retrieving cache...

25

2024-08-07T07:30:19.839Z [INFO]: # Extracting cache...

26

2024-08-07T07:30:31.596Z [INFO]: # Extraction completed

27

2024-08-07T07:30:31.880Z [INFO]: # Retrieved cache

28

2024-08-07T07:30:34.747Z [INFO]: ## Starting Backend Build

29

# Starting phase: build

30

# Executing command: npm ci --cache .npm --prefer-offline

31

2024-08-07T07:30:53.300Z [WARNING]: npm

32

2024-08-07T07:30:53.305Z [WARNING]: WARN deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

33

2024-08-07T07:30:53.426Z [WARNING]: npm

34

2024-08-07T07:30:53.427Z [WARNING]: WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.

35

2024-08-07T07:30:53.604Z [WARNING]: npm WARN

36

2024-08-07T07:30:53.604Z [WARNING]: deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead

37

2024-08-07T07:30:53.666Z [WARNING]: npm

38

2024-08-07T07:30:53.666Z [WARNING]: WARN deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported

39

2024-08-07T07:30:53.916Z [WARNING]: npm WARN

40

2024-08-07T07:30:53.917Z [WARNING]: deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead

41

2024-08-07T07:30:53.931Z [WARNING]: npm

42

2024-08-07T07:30:53.931Z [WARNING]: WARN deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported

43

2024-08-07T07:30:53.979Z [WARNING]: npm WARN deprecated

44

2024-08-07T07:30:53.979Z [WARNING]<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported

45

2024-08-07T07:30:54.003Z [WARNING]: npm WARN

46

2024-08-07T07:30:54.003Z [WARNING]: deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.

47

2024-08-07T07:31:02.425Z [WARNING]: npm

48

2024-08-07T07:31:02.430Z [WARNING]: WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

49

2024-08-07T07:31:04.321Z [INFO]: added 1486 packages, and audited 1603 packages in 29s

50

2024-08-07T07:31:04.322Z [INFO]: 169 packages are looking for funding

51

run `npm fund` for details

52

2024-08-07T07:31:04.437Z [INFO]: 29 high severity vulnerabilities

53

To address issues that do not require attention, run:

54

npm audit fix

55

To address all issues (including breaking changes), run:

56

npm audit fix --force

57

Run `npm audit` for details.

58

2024-08-07T07:31:04.484Z [INFO]: # Executing command: npx ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID

59

2024-08-07T07:31:09.492Z [INFO]:

60

2024-08-07T07:31:14.834Z [INFO]: amplify/backend.ts(4,26): error TS2307: Cannot find module './functions/say-hello/resource' or its corresponding type declarations.

61

2024-08-07T07:31:14.840Z [INFO]: amplify/backend.ts(5,25): error TS2307: Cannot find module './storage/resource' or its corresponding type declarations.

62

2024-08-07T07:31:14.875Z [INFO]:

63

2024-08-07T07:31:14.875Z [WARNING]: ampx pipeline-deploy

64

Command to deploy backends in a custom CI/CD pipeline. This command is not inten

65

ded to be used locally.

66

Options:

67

--debug Print debug logs to the console [boolean] [default: false]

68

--help Show help [boolean]

69

--branch Name of the git branch being deployed [string] [required]

70

--app-id The app id of the target Amplify app [string] [required]

71

--outputs-out-dir A path to directory where amplify_outputs is written. If no

72

t provided defaults to current process working directory.

73

[string]

74

--outputs-version Version of the configuration. Version 0 represents classic

75

amplify-cli config file amplify-configuration and 1 represe

76

nts newer config file amplify_outputs

77

[string] [choices: "0", "1"] [default: "1"]

78

--outputs-format amplify_outputs file format

79

[string] [choices: "mjs", "json", "json-mobile", "ts", "dart"]

80

2024-08-07T07:31:14.875Z [INFO]: SyntaxError: TypeScript validation check failed.

81

Resolution: Fix the syntax and type errors in your backend definition.

82

Cause:

83

2024-08-07T07:31:14.986Z [ERROR]: !!! Build failed

84

2024-08-07T07:31:14.986Z [ERROR]: !!! Error: Command failed with exit code 1

85

2024-08-07T07:31:14.986Z [INFO]: # Starting environment caching...

86

2024-08-07T07:31:14.987Z [INFO]: # Uploading environment cache artifact...

87

2024-08-07T07:31:15.086Z [INFO]: # Uploaded environment cache artifact

88

2024-08-07T07:31:15.086Z [INFO]: # Environment caching completed

Hey @milesmarshall, thank you for reaching out. Could you provide us some additional information or screenshot on how the backend and repository is currently setup.
Could you try adding ls -la amplify/ in the amplify.yml build specification before the deploy command?

Hello, I was facing the same issue: 'amplify/backend.ts(5,25): error TS2307: Cannot find module './storage/resource' or its corresponding type declarations.' during the deployment. I decided to follow a comment suggesting to run the following command before deploying: 'ls -la amplify/'. This command showed me that the storage folder was indeed missing. So, I checked my GitHub repository and saw that the folder was also missing there. After confirming it wasn't present, I did another push to the repository, and this time the folder appeared. As a result, the deployment was successful. Perhaps this is related to the fact that I recently made my repository private?


Allow pdf file upload

For logged in users, enable upload of a pdf file containing their existing tie sheet (required) when they choose to upload an existing sheet

Validated as it currently works. It will be further confirmed when the Uploaded Tiesheet function is wired up to access/preview/download the uploaded sheet. (do you want a task/issue for that @steveoh)

If there is not already a task then yes.


[Fix bug 1119510] Fixed the search results going beyond scope CSS issue.

Coverage remained the same at 93.0% when pulling 043556fb2ce31ccf11fcb3aa04c724793261dd51 on akasantony:fix-search-css into 4a747df5f7a73bf7f1c95a8cf1efc2aa07ba4d29 on mozilla:master.


created an embed example page

changes
added a page with an embed example (inspired by discord.js)
also added a screenshot to demonstrate the example
hopefully i made everything correctly
I named the page "Sending Embeds". If someone have a better name, feel free to change it

thanks, ive merged this and it should be live in the docs in a few minutes 👍


Linux install issue

make: *** No rule to make target vive-diy-position-sensor-upload'.  Stop.`
Ubuntu 14.04, seems to be compiling properly.

I seem to be able to upload hex files with the teensyduino uploader, so I guess I'll stick to that for now.

Check you have a tyc command-line uploader (see https://github.com/Koromix/ty), placed into /usr/local/bin/. Regular teensyduino uploader works as well, yep!


UI nodes don't resize when toggling fullscreen

Bevy version
0.14.0
Relevant system information
Linux with i3wm (tiling window manager).
AdapterInfo { name: "AMD Radeon RX 570 Series (RADV POLARIS10)", vendor: 4098, device: 26591, device_type: DiscreteGpu, driver: "radv", driver_info: "Mesa 24.0.6-arch1.2", backend: Vulkan }

What you did
Toggle fullscreen while looking at my title screen UI.
What went wrong
This is how my UI normally looks:

This is how my UI sometimes looks after toggling from fullscreen to windowed:

I checked, and the buttons in this case are the same size as they were while in fullscreen.
This issue can happen in reverse as well, with the fullscreen buttons being as small as they were while windowed.
Resizing the window slightly after the bug occurs will snap the buttons back to the correct size.

It seems like the single UI layout update after the window resize isn't enough. You could try a system something like this to force  it to reupdate again for few frames after the window resizes:
fn force_ui_reupdate_on_window_resized(
    mut counter: Local<u8>,
    mut window_resized_events: EventReader<WindowResized>,
    mut ui_scale: ResMut<UiScale>,
    mut ui_node_query: Query<(&mut Style, Option<&mut Text>)>,
) {
    if 0 < *counter {
        ui_scale.set_changed();
        for (mut style, maybe_text) in ui_node_query.iter_mut() {
            style.set_changed();
            if let Some(mut text) = maybe_text {
                text.set_changed();
            }
        }
    }

    *counter = counter.saturating_sub(1);
    if !window_resized_events.is_empty() {
        window_resized_events.clear();
        *counter = 2;
    }
}

I just typed this out quickly, it's not tested but I think it should work. The query might be overkill, maybe it'll correct itself just with set ing UiScale to changed the frame directly after the window resize.

Duplicate of #14255.

I'm seeing this build in the itch.io release of my jam game as well. This is much more severe than the related bug, because the size difference between windowed and fullscreen makes the UI completely bugged instead of "slightly off / delayed".

This appears to be a system ordering bug. I ran the same app 25 times without recompiling and saw the bug 9/25 times. Whenever the bug was present, it happened 100% consistently on every fullscreen toggle.

I suspect that this is a system ordering bug between CameraUpdateSystem and UiSystem::Layout, which both run in PostUpdate with no ordering specified between them. The former set contains a system that updates the Camera's viewport size, while the latter has a system that reads the Camera's viewport size if the window has been resized.

Well. I wasn't able to reproduce the bug in a modified bevy example, but I tried explicitly ordering CameraUpdateSystem before UiSystem::Layout and it triggered the exact same behavior.

Opened PR :)


read the docs build are broken

Describe the bug
default build env isn't healthy (this is not unique to VisIt)
readthedocs/readthedocs.org#8616
Fix from axom:
LLNL/axom#696

How did you notice? Did you get email notification of build failures?


Is the use of WebAPI in code components supported?

It has been listed as a limitation in the documentation https://docs.microsoft.com/en-us/powerapps/developer/component-framework/limitations
Thanks in advance
//Adam

@adamjbradley WebAPI methods can be used in code components only for Model-driven apps and currently not available for canvas apps.


pyinotify event queue overflowed

I am getting this when moving ~10K files in the watcher folder. Can someone guide me on how to increase the "max_queued_events" size for pyinotify?

To change the queue length to 256K:
sysctl -w fs.inotify.max_queued_events=262144

This is only part of the problem. Other parts of this problem are:

Linux doesn't tell you how many overflow events there were
This python interface doesn't tell you how much work it did (#190)


add guardrails to avoid failed calculations

[x] multiplicity

fix/hack: automatically inferring charge from name of mol; setting multiplicity to 1 manually


FeedAHelp: Collect all Ingredient Images and Icons

Related to #102 , #101
We will need transparent PNG image version of all ingredients
Sample

Link of the excel sheet: https://docs.google.com/spreadsheets/d/1oYA7eE_2IzpT-_iedU5bA2vzIX281GUdxUN4Mbk7uHM/edit#gid=0

@MuksanaAkter Nice work we have #177 now, lets close this


Update BPI

The tests are failing because, the collateral utxo is not taken into account.
  Value assertion failed on own wallet:
        Expected: 44707600 lovelace
        Got: 34561400 lovelace

The difference between got and expected is exactly 10Ada, which is the value of collateral utxo. To confirm this feel free to change the pcCollateralSize.

Yep, we'll need to adjust for this, this PR was mostly just to get BPI updated quickly.
@nazrhom will you have time to take a look at the tests?

@samuelWilliams99 I have managed to fix the failing tests, as expected I had to take collateral Value and it's fee into account https://github.com/mlabs-haskell/plutip/pull/100 . But I think it's more of a temporary solution, the better solution will be creating the collateral  utxo automatically when initializing the wallet, i.e. every wallet will come with it's own initAda and collateral utxo

Hey @IAmPara0x I see the last test is still failing in that PR, I pushed here the changes that seem to work while running my own tests locally.

Those tests are failing because of a bug, that I don't think is related to collateral handling. Here's the summary of that bug:
There's sometimes a discrepancy of 7,600 lovelace, while running the same tests, i.e. when same tests are run sometimes there's 7,600 lovelace less in the wallet and sometimes everything is fine and the tests passes.

Please check your latest commit, it's also failing because of that bug. As said earlier, if you will run those tests more that 1 time, everything will succeed, it's kinda "random", therefore it makes hard to guess where the 7,600 lovelace goes. But, I will look into it later.

Ahh sorry, I had missed you commenting on that bug, was just noticing I am also getting this strange random behaviour.
Thanks!

with #100 merged there's no need for this anymore, should we close it @mikekeke ?

Closed by #100


Validate impact of azimuth angles on rupture building

Currently we have examples of ruptures that start out north->south then switch direction to south->north.
TODO attach example.
Done when we can answer these questions:

[ ] are there any constraints on ruptures relating to azimuth in play now?
Please add links to any relevant code in this issue
[ ] if there are, are they working correctly?

NB After these code questions are answered we can ask SRM team if this is enough, or whether more/better constraints are needed (new feature).

https://github.com/opensha/opensha-ucerf3/tree/master/src/org/opensha/sha/earthquake/faultSysSolution/ruptures/doc#notes-on-azimuth-change-calculations

I found four possible plausibility filters:
In org.opensha.sha.earthquake.faultSysSolution.ruptures.plausibility.impl

JumpAzimuthChangeFilter
TotalAzimuthChangeFilter

and in scratch.UCERF3.inversion.laughTest

AzimuthChangeFilter
CumulativeAzimuthChangeFilter

@voj  FYI here's some debugger output from our earlier StandaloneRuptureGen example, and this was able to generate ruptures for the full NZ 2010 crustal model with maxDistance = 0.5
NB This may have relevance to #28 also. I'm seeing several different variations and usages of 'distance' in the above example.
These values are setup here: https://github.com/GNS-Science/nshm-nz-opensha/blob/7a938f96df1992b412eb749dd7a8eb53b7aab577/src/main/java/scratch/kevin/ucerf3/StandaloneSubSectRupGenMG.java#L147
laughTest	UCERF3PlausibilityConfig  (id=57)
	allowSingleSectDuringJumps	true
	applyGarlockPintoMtnFix	true
	coulombRates	null
	coulombTester	CoulombRatesTester  (id=60)
	laughTests	null
	maxAzimuthChange	60.0
	maxCmlAzimuthChange	560.0
	maxCmlJumpDist	Infinity
	maxCmlRakeChange	180.0
	maxJumpDist	5.0
	maxTotAzimuthChange	60.0
	minNumSectInRup	2
	parentSectsToIgnore	null
	ucerf3p2Filter	false

All questions answered, and we now know we must get them in play. I'll create a new story for this.


Wrong summary message in import from CLI

$result['counts'] and $result['errors'] it is arrays, so, $summary always is FALSE instead of message

Hi @scapital
This code has also been refactored.
Thank you!


Sponsorship should move to the "ddev" org on GitHub

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
Sponsorship is currently done via the "rfay" user. But now that we've landed at github.com/ddev/ddev, it's time to set up sponsorship on the org, so it's not so confusing. And of course, sponsorship funds don't go to rfay, they go to the Localdev Foundation for funding work outside rfay's work.
Describe your solution

[ ] Open up sponsorship on ddev/ddev. This requires a new application on GitHub
[ ] Change the "sponsor this project" to point to it
[ ] Update the sponsorship details
[ ] Send an email to existing sponsors asking them to move (and consider increasing their sponsorship)
[ ] Mention that invoiced support contracts are also available

Describe alternatives
No response
Additional context
No response

I have submitted the request to GitHub to enable sponsorships on ddev org.
Next steps:

[ ] Change "Sponsor this project" to ddev org
[ ] Email to current sponsors asking them to move to ddev org
[ ] Email needs to explain that we can do ACH and can also bill them.
[ ] Help them understand if they're sponsoring at the right level.

Sponsorship is live, although not announced. It's at https://github.com/sponsors/ddev
We can follow the instructions at https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository to do a funding.yml that shows for all repos.
@mattstein there's a little complex thing that's going to happen here. We're going to have sponsors on both rfay and ddev, and we'd prefer to show both of them (the sum of them). That sounds complicated on the https://ddev.com/support-ddev/ "Sponsor development" section.

If it’s a matter of querying a second set of sponsorships and merging the results, it should be a straightforward thing to do here. That’s where the landing and Support DDEV pages both get their sponsor data.

I think we're close enough now with this, so I'm going to close it.
But @mattstein could you please review https://github.com/sponsors/ddev and make your suggestions about how to improve it?

Reopening for suggestions from anyone including @mattstein

But @mattstein could you please review https://github.com/sponsors/ddev and make your suggestions about how to improve it?

Sure! I’d probably make a bunch of small edits to sharpen what’s there into something more brief. To me, though, it feels like the page describes where funds go but not necessarily where DDEV is going. As a potential sponsor, I might be more motivated to contribute if I know I can help the organization or product toward specific goals.
Happy to suggest edits, but we surely don’t want me making up higher-level goals.

Why don't you suggest edits on https://gist.github.com/rfay/2772ea8209896b169ef9ddb2f0db6374#file-sponsors-md -
I appreciate the suggestion about specific goals, it's a worthy conversation but like you say probably needs a different starting point.

Thanks for the great edit/writing @mattstein . I put that in place and also updated https://github.com/sponsors/rfay to point people there. Let me know if you would like anything better there.
I think we have this one.


Fix a typo in IntegrationWithExistingApps.md.

[x] Explain the motivation for making this change.
[x] Provide a test plan demonstrating that the code is solid.
[x] (N/A) Match the code formatting of the rest of the codebase.
[x] Target the master branch, NOT a "stable" branch.

Motivation (required)
Fixed a typo in documentation IntegrationWithExistingApps.md.
"Your should see" -> "You should see"
Test Plan (required)
Screenshots
Before:

After:

@facebook-github-bot shipit


VisionWorks crashes when changing min_disparity

When launching the VisionWorks image_proc nodelet via the provided launch file, everything work fines with the default parameters. However, when rqt_reconfigure is used to tune the parameters, changing min_disparity causes the VisionWork nodelet to exit with the following error message.
[ERROR] [1597894512.268134406]: VX ERROR: -10
[FATAL] [1597894512.268307656]: ASSERTION FAILED
	file = /home/ubuntu/cam_ws/src/gpu_stereo_image_proc/src/libgpu_stereo_image_proc/vx_stereo_matcher.cpp
	line = 215
	cond = status == VX_SUCCESS

Currently am testing the package with L4T 32.4.3 (Ubuntu 18.04) with ROS Melodic, on a Jetson Xavier NX (ARM 64Bit).

Thank you for the report and sorry for the late response.
I'll try to reproduce it on my NX on this weekend.


Issues with Complaints about no space when there is plenty

I'm having an issue where docker-compose up doesn't work due to some check for space stating there is no space available.
However, I know this is false because there is 500GB thin provisioned assigned to it and it is only using 30GB.
Anyway, to fix the scripts or make some changes to resolve this issue so that it can be ran on an ESXi host guest VM?

I gave that a shot, but no dice. Got any other ideas?

Need more info about server, like output of some command:
df -h

sudo docker system df -v

docker -v && docker-compose -v

😭 I figured it out! It was something very basic and dumb!
It had something to do with how I configured my VM templates on the ESXi Host. Rookie mistake.
The error about space issues was valid.


Faster launching

Now launching time takes a little longer than before (1.9?). Let's make this faster. My guess is the fix for #879 is the culprit.

CC @wasedaigo

Even though we could defer the commands, the commands are executed later, and the number of commands did not change.
I'll leave this as 'won't fix'. Let's revisit this when we find another good way.


Support alternate oauth2 authorization header

For Pier One...

Will fix #11

Changes Unknown when pulling 5409aaca8a02f6a9577aaa2fe664cf36064661b1 on support-alternate-oauth2-authorization-header into ** on master**.


Could not convert Dec to Decl ()

Running derive/v2_6_2 with GHC8 I'm getting this error:
Bug2.hs:1:1: error:
    Exception when trying to run compile-time code:
      Could not convert Dec to Decl ()
TySynD Main.NewType [] (ConT Main.DataType)
derive/v2_6_2/src/Language/Haskell/Convert.hs:(41,14)-(45,8): Non-exhaustive patterns in case

CallStack (from HasCallStack):
derive/v2_6_2/src/Language/Haskell/Convert.hs:22:87 in thirdU-UpartyS-ShaskellS-SderiveS-Sv2U-U6U-U2S-SderiveD-Dlib:Language.Haskell.Convert
    Code: derive makeNFData ''NewType

for the code below:
{-# LANGUAGE TemplateHaskell #-}

import Control.DeepSeq(NFData(..))
import Data.DeriveTH

type NewType = DataType
data DataType = DataType
$(derive makeNFData ''NewType)

Admittedly deriving something for a type is not exactly the best idea, but a more helpful error would be nice.

Come to think of it, the issue is not in fact silly. In full code my data is parameterized by a type family. So I do need to derive the instance for the type Type = DataType Identity. Making this work is a functional requirement.
FWIW, this workaround kind of works, but I loathe mixing different styles of NFData:
deriving instance Generic Type
instance NFData Type

Warning: This package has no official maintainer anymore. Use at your own risk. You may wish to consider the built-in mechanism GHC.Generics or libraries such as generic-deriving.


System.UnauthorizedAccessException

I just loaded this up in a Universal Windows Application (C#) which I'm attempting to learn right now.  When copy in the sample line of code to search for devices I get the message:
An exception of type 'System.UnauthorizedAccessException' occurred in mscorlib.ni.dll but was not handled in user code
WinRT information: At least one of either InternetClientServer or PrivateNetworkClientServer capabilities is required to listen for or receive traffic
Additional information: Access is denied.
I'm using your sample (I should have a printer that is discoverable):
public async Task ProbeForNetworkPrinters()
{
IReadOnlyList results = await
ZeroconfResolver.ResolveAsync("_printer._tcp.local.");
}

Sorry; Universal Windows permission issue (not used to this; your library works just fine)


olric in k8s is always in the initial member list

env: ubuntu 18.04  k8s
describe: When I update the version, there will be a problem of synchronizing nodes all the time.Then it will be killed over time(20minutes). Never wait for this sentence Join completed

this is my config
olricd:
  bindPort: 3320
  serializer: gob
  keepAlivePeriod: 300s
  requestTimeout: 5s
  partitionCount:  271
  replicaCount: 1
  writeQuorum: 1
  readQuorum: 1
  readRepair: false
  bootstrapTimeout: 1000s
  replicationMode: 0
  memberCountQuorum: 1

storageEngines:
  config:
    kvstore:
      tableSize: 4194304

logging:
  verbosity: 6
  level: DEBUG
  output: stderr

memberlist:
  environment: "lan"
  bindPort: 3322
  enableCompression: false
  joinRetryInterval: "500ms"
  maxJoinAttempts: 100

client:
  dialTimeout: -1s
  readTimeout: 2s
  writeTimeout: 2s
  keepAlive: 15s
  minConn: 1
  maxConn: 100
  poolTimeout: 2s

dmaps:
  img-bucket:
    maxIdleDuration: "3600s"
    ttlDuration: "14400s"
    maxKeys: 15000
    maxInuse:<PHONE_NUMBER> # in bytes ;3GB
    lRUSamples: 10
    evictionPolicy: "LRU" # NONE/LRU

  resp-bucket:
    maxIdleDuration: "36000s"
    ttlDuration: "36000s"
    maxKeys: 150000
    maxInuse: 300000000 # in bytes ;300MB
    lRUSamples: 10
    evictionPolicy: "LRU" # NONE/LRU

serviceDiscovery:
  provider: "k8s"
  path: "/usr/lib/olric-cloud-plugin.so"
  args: 'label_selector="app = img-proxy"'

Hi @hacktmz,
I couldn't see any problem in the logs. Join completed message can be printed anywhere in the logs. It's printed after the initial join process is completed.
To inspect the cluster health, you can use the Stats method of the Olric API.  See this: https://github.com/buraksezer/olric#stats
Alternatively, you can use the olric-stats command to inspect the cluster health.
$ olric-stats -a <address> -m

For detailed info: https://github.com/buraksezer/olric#olric-stats
Messages like Stream connection from... is debug level messages of memberlist. It's completely normal. An Olric node constantly transfers messages with the other nodes to discover the failures in the cluster. You can change the log level to INFO if you don't want to see this kind of message. In addition to that, you are using 6 as verbosity level which enables trace level logging. 3 is good for developing applications with Olric.

I tried olric-stats -a <address> -m
but it always shows timeout, but it can be detected by telnet

Stats Info:  ClusterCoordinator Name <IP_ADDRESS>:3320; Member Name <IP_ADDRESS>:3320 ; ClusterMembers   <IP_ADDRESS>:3320
I recorded the log. It may be that k8s started pods at the same time, causing all pods to not find member, and finally became stand-alone mode.

I always have a few pods stuck in the initialization process and cannot get logger.Infof(" Olric is db init ready2.1 err %v", err.Error()) log output. Then the pod will stay stuck until it times out
package cache
import (
"context"
"github.com/buraksezer/olric"
"github.com/buraksezer/olric/config"
"os"
)
var Cache *olric.Olric = nil
var Dmap *olric.DMap = nil
var DmapResp *olric.DMap = nil
func Init() (*olric.Olric, *olric.DMap, *olric.DMap) {
// Deployment scenario: embedded-member
// This creates a single-node Olric cluster. It's good enough for experimenting.
// config.New returns a new config.Config with sane defaults. Available values for env:
// local, lan, wan
c, err := config.Load(cfg.EnvConfigFile)
if err != nil {
	logger.Errorf("Failed to load configuration: %v", err)
}
logger.Infof("[INFO] Olric load config file :%s", cfg.EnvConfigFile)
// Callback function. It's called when this node is ready to accept connections.
ctx, cancel := context.WithCancel(context.Background())
c.Started = func() {
	defer cancel()
	logger.Infof("[INFO] Olric is ready to accept connections")
}

db, err := olric.New(c)
if err != nil {
	logger.Errorf("Failed to create Olric instance: %v", err)
	os.Exit(0)
}

go func() {
	// Call Start at background. It's a blocker call.
	err = db.Start()
	if err != nil {
		logger.Errorf("olric.Start returned an error: %v", err)
		os.Exit(0)

	}
}()
<-ctx.Done()
logger.Infof(" Olric is db init ready")

dm, err := db.NewDMap("img-bucket")
logger.Infof(" Olric is db init ready2.1 err %v",err.Error())
if err != nil {
	logger.Errorf("olric.NewDMap img-bucket returned an error: %v", err)
	os.Exit(0)
}
logger.Infof(" Olric is db init ready2")

dmResp, err := db.NewDMap("resp-bucket")
logger.Infof(" Olric is db init ready3.1 err %v",err.Error())
if err != nil {
	logger.Errorf("olric.NewDMap resp-bucket returned an error: %v", err)
	os.Exit(0)

}
logger.Infof(" Olric is db init ready3")

return db, dm, dmResp

}

Hi,
I couldn't debug the issue with this little info about your Kubernetes setup, but we have a document to set up Olric clusters on K8s. It has a dedicated section to access the cluster: https://github.com/buraksezer/olric-kubernetes#accessing-the-cluster
AFAIK, you couldn't access the containers with their IP address. Could you please send your Kubernetes config for Olric, if it's possible? Full logs of Olric nodes would be a nice addition here.

I recorded the log. It may be that k8s started pods at the same time, causing all pods to not find any member, and finally became stand-alone mode.But I don’t know any good solutions

It seems that your setup works as I expected. Because I can see "Node joined" messages in the first post. If some nodes create an independent cluster, you may need to increase joinRetryInterval.


[Update] Azure patterns & practices - Freshness pass

Remove link to github issues and instead use UUF
Be clear this is "Azure" patterns & practices, not any of the other PnP teams
Replace martin with our new manager, Luke

#assign-reviewer:"@skabou"

#sign-off

This is ready for you @jehchow, @carlyrevier, or @Kiranchandratrey

Thanks, Mike


Use ephemeral sessions instead of cloning for each eval

May close #20.
Closes #50.

Thank you! I think ephemeral sessions fit great into this use-case


Add checkerframework and errorprone

Try checkerframework and errorprone

@vlsi Any feedback about the 2 tools and how I added them in the build (even if I was inspired by what you did on pg-driver)?
@krmahadevan WDYT? They highlight a lot of minor issues but some potential problems too.

@juherr - This is definitely a good addition. I am yet to explore both these tools. I have already seen error prone being used by jhipster when it scaffolds a new project based on my inputs.
Couple of questions:

These highlight the problems in our code, but would it prevent TestNG from being used incorrectly by its consumers (especially the ones that use the TestNG apis to provide customised runners etc., ?)
The CI has failed, mainly because of the discrepancies in our code, which you also highlighted. So for us to adopt these two tools, I believe we would need to iterate on all the failures and then fix them right ?

Thanks.

These highlight the problems in our code, but would it prevent TestNG from being used incorrectly by its consumers (especially the ones that use the TestNG apis to provide customised runners etc., ?)

As I understand, yes. It provides extra data in bytecode thanks to the annotations.
The drawback is it is adding a new runtime dependency (because the annotations are stored in the bytecode).

The CI has failed, mainly because of the discrepancies in our code, which you also highlighted. So for us to adopt these two tools, I believe we would need to iterate on all the failures and then fix them right ?

To be honest, I hoped there were a bit less. That's why I sent the draft before fixing them all.

"nullability" is not trivial, so it might take some time to properly annotate and identify nullable types.
The general advice is assume "everything is not nullable by default" (==almost never put @NotNull), and annotate @Nullable where null values are allowed.

In my experience, checkerframework nullability verification takes time, so I tend to activate it only when -PenableCheckerframework parameter is specified. Then checkerframework executes in a single CI job only.
See https://github.com/apache/jmeter/blob/c94db9741f0547235f9a67b1ece40389add6b742/build-logic/build-parameters/build.gradle.kts#L77 , and https://github.com/apache/jmeter/blob/c94db9741f0547235f9a67b1ece40389add6b742/build-logic/verification/src/main/kotlin/build-logic.style.gradle.kts#L42-L43 (conditional activation of .checkerframework.gradle.kts)

Updated according to reviews.
All issues are not fixed yet.
Still 2 gradle issues: not succeeding in using the parameters plugin + not finding the way to merge package-info

I would suggest merging errorprone first as it would require much fewer changes.