Status - GO release and PAINT annotations

Hi @cmungall
What is the status on PAINT annotations integration (and export) in the GO database?
For example this family have been modified in July - this is not yet showing up in AmiGO (annotation should be deleted):
TMS1 | Vacuolar membrane protein of unknown function |   | L-serine transmembrane transporter activity |   | GO_Central | Saccharomyces cerevisiae S288C | IBA | PANTHER:PTN000043695 | serine incorporator pthr10383 |   | SGD_REF:S000185201 | 20150303
Thanks, Pascale

This looks OK to me now, I don't see this annotation on http://amigo.geneontology.org/amigo/gene_product/SGD:S000002512.   OK to close?

Looks good. Thanks for checking !


Convert examples/learning/helloworld.html to await/async

Issue this pull request solves:
closes #14121

Thanks, I had a little problem with npm install and that was the reason why of the error but everything is working now


[ADAM-681] Remove menacing error message about reqd .adam extension

lgtm!

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

Merged! Thanks @laserson!


out of memory error on windows

Environment info
Operating System:
Windows Server 2016
MXNet version:
0.11.0
Or if installed from source:
Install with pip install mxnet-cu80
Python version and distribution:
2.7
run python train_mnist.py in examples folder would cause out of memory error, which is weird since the memory is sufficient enough.

[17:45:39] G:\deeplearn\mxnet\dmlc-core\include\dmlc/logging.h:308: [17:45:39] g:\deeplearn\mxnet\src\storage./pinned_memory_storage.h:54: Check failed: e == cudaSuccess || e == cudaErrorCudartUnloading CUDA: out of memory
[17:45:39] G:\deeplearn\mxnet\dmlc-core\include\dmlc/logging.h:308: [17:45:39] g:\deeplearn\mxnet\src\engine./threaded_engine.h:347: [17:45:39] g:\deeplearn\mxnet\src\storage./pinned_memory_storage.h:54: Check failed: e == cudaSuccess || e == cudaErrorCudartUnloading CUDA: out of memory
An fatal error occurred in asynchronous engine operation. If you do not know what caused this error, you can try set environment variable MXNET_ENGINE_TYPE to NaiveEngine and run with debugger (i.e. gdb). This will force all operations to be synchronous and backtrace will give you the series of calls that lead to this error. Remember to set MXNET_ENGINE_TYPE back to empty after debugging.

Is it possible to install python package on Windows with pip???? Any documentation about this, I couldn't find it. Just type pip install mxnet-cu80 is sufficient?

According to this issue, it can be installed with pip. https://github.com/apache/incubator-mxnet/issues/7362 . However, it always fails with out of memory on multi GPUs training in my experiments.

Can you create a large matrix on gpu to test?
For example
import mxnet as mx
a = mx.nd.ones(shape=(256, 1024, 2000), ctx=mx.gpu(0))

will create a 2000M matrix on gpu

It works fine creating a large matrix on GPU. However when I run train_mnist.py it still fails and the python stop working. The GPU is M40. I tried run train_mnist.py on K40, it works fine.

@yajiedesign

how many you system physics memory?this is alloc pinned memory.it must enough physics memory.

The free physical memory is enough. I just found that it's due to GPU 0 is broken. Even I set to use other GPUS it still fails. If I set CUDA_VISIBLE_DEVICES to mask GPU 0, the code can work without errors.  Thank you for your reply.

I got mxnet with python installed on Windows 10 with pip using Anaconda 2. Seems to work with VS2017, although Anaconda2 has to be installed with the VS2017 installer. Thank you for the tips!
Would be good if using pip install for Windows is reference on the installation webpage of mxnet.io . Really saves tons of work.

Unfortunately the mxnet pyhton on windows through 'pip install -U --pre mxnet' does not run on GPU:
C:\projects\mxnet-distro-win\mxnet-build\dmlc-core\include\dmlc/logging.h:308: [16:09:26] C:\projects\mxnet-distro-win\mxnet-build\src\storage\storage.cc:113: Compile with USE_CUDA=1 to enable GPU usage
Is it possible to pip install a version with gpu support?

I install mxnet by pip install mxnet-cu80 so that I can use GPU.

Thanks, I should have read the thread #7362 better. But yeah, it works now!!! many thanx.


Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.github.smarteist:autoimageslider:1.4.0.

Describe the bug
Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.github.smarteist:autoimageslider:1.4.0.
**To fit it **
Steps to reproduce the behavior:

Go to 'setting.gradel'
2.Add ' jcenter() ' and
' maven { url 'https://jitpack.io' } '

@CHENNURUGURUSANKAR  jcenter is depreciated and was replace with mavenCentral. Does that means this library was not moved to mavenCentral?

Adding jcenter() will fix the error

thanks bro ....

These error are solved
Solution :- Follow this link:-
https://github.com/smarteist/Android-Image-Slider/issues/248#issuecomment-1403067934


[Function Exposure] codeunit 99000845 "Reservation Management" - ResvExistsForHeader

Please make function ResvExistsForHeader externally available.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 40912.


Promise.all arguments is null or undefined

Hi,
I've noticed that when running the following code on browsers that supports promises and browsers that doesn't support (with this the polyfill) i get a different result:
Promise.all(null) .then(function () { console.log('then'); }) .catch(function (e) { console.log('catch', e); });
Supported browsers result:
Calling the 'catch' statement with an error of 'TypeError'.
Unsupported browsers (with the polyfill):
Throws an error on the arguments slice, doesn't call the 'catch' statement.
Is this the behavior aimed for in this polyfill?
Thanks,

It should behave the same. Would you mind creating a pull request?


Web: Support attrs extension functions in sub elements too

Eg SvgRectElement extends SvgElement, but width is defined in AttrsScope<SvgElement> which is not usable in SvgRectElement attrs builder because the element types don't match.

Thank you!


Specify swift version for the Pod framework

This PR allows for Freddy to be pulled in using cocoapods. Currently Cocoapods isn't setting the SWIFT_VERSION compiler setting to anything, so Freddy will not build. Looking at the current issues/PRs for cocoapods, it is unclear if they have a real solution to this or not. Ideally each pod should have a say into which swift version it supports. This change allows us to control the version from the podspec. We can revisit once cocoapods has a real solution for this problem.

This will fix issue #195

See why :construction_worker: is upset.


Implement NAN values

Today, Nan values aren't supported by DebiAI, to support them will take a lot of work because each widget need to be tested, (the parallel coordinate plot does not display a line where one of the value is none, ...)
But they could be analyzed on their own and be treated as contexts, there is a lot of project with empty values.

Done with 0.29


Introduce light colour theme

Resolves https://github.com/jotaen/klog/issues/289.
klog now supports light-themed terminals via the colour_scheme = light entry in the config.ini file (see klog config --help).
The default is dark (as before), and it’s also possible to disable colouring altogether via no_colour.

Awesome, thanks for spending time on this! I’ve installed the version from main and played around a little bit, and the color scheme looks fine to me.


Log the gradient norm of loss component and model parameters

Pull Request Summary
To better understand multitask training behavior, this PR adds features to log the gradient norms (for the model parameter and the loss components). And, as @andrrizzi speculated correctly, this feature requires two additional backward passes (to calculate the loss component gradient norm) and, therefore, adds additional computational costs.   This features is not enabled by default.
This is added to the WandB report:

Pull Request Checklist

[ ] Issue(s) raised/addressed and linked
[ ] Includes appropriate unit test(s)
[ ] Appropriate docstring(s) added/updated
[ ] Appropriate .rst doc file(s) added/updated
[ ] PR is ready for review

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.32%. Comparing base (9b3ed45) to head (676091c).

Additional details and impacted files


wpt-pr-bot missed a webhook - reviewer missing

https://github.com/web-platform-tests/wpt/pull/13693 Missing a review when the PE is created

Thanks for the report! The only change in the referenced pull request is a file deletion. That's fairly unique, so it initially seemed like an edge case we weren't handling properly. However, running the code against that pull request right now yields the expected result.
The logs have this to say:
Oct 24 01:06:13 wpt-pr-bot app/web.1: #13693 pull request opened
Oct 24 01:06:14 wpt-pr-bot heroku/router: at=info method=POST path="/github-hook" host=wpt-pr-bot.herokuapp.com request_id=0000000 fwd="<IP_ADDRESS>" dyno=web.1 connect=1ms service=4ms status=200 bytes=224 protocol=https
Oct 24 01:06:14 wpt-pr-bot app/web.1: #13693: not handled. action: labeled isComment: false
Oct 24 01:06:18 wpt-pr-bot app/web.1: GET https://api.github.com/repos/web-platform-tests/wpt/pulls/13693/files
Oct 24 01:06:18 wpt-pr-bot app/web.1: #13693: THIS SHOULDN'T EVER HAPPEN
Oct 24 01:06:18 wpt-pr-bot app/web.1:  Error: Not Found
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at errFrom (/app/lib/github.js:10:15)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at Request.onResponse [as _callback] (/app/lib/github.js:86:29)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at Request.self.callback (/app/node_modules/request/request.js:372:22)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at emitTwo (events.js:126:13)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at Request.emit (events.js:214:7)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at Request.<anonymous> (/app/node_modules/request/request.js:1317:14)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at emitOne (events.js:121:20)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at Request.emit (events.js:211:7)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at IncomingMessage.<anonymous> (/app/node_modules/request/request.js:1265:12)
Oct 24 01:06:18 wpt-pr-bot app/web.1:     at emitNone (events.js:111:20)

The requested resource is available now, so this may have been the result of a transient network connectivity issue.

Interesting. That error was the reason for filing https://github.com/web-platform-tests/wpt/issues/13710 so possibly the guess (by @tobie) at the cause was incorrect.
Maybe the code could retry after a timeout if the problem is connectivity?

That error was the reason for filing https://github.com/web-platform-tests/wpt/issues/13710 so possibly the guess (by @tobie) at the cause was incorrect.

The string "THIS SHOULDN'T EVER HAPPEN" is logged in response many distinct errors. Although this particular case is unrelated to user permissions, Tobie's diagnosis was for other cases which are caused by permissions. So unfortunately, https://github.com/web-platform-tests/wpt/issues/13710 is still a valid bug.

Maybe the code could retry after a timeout if the problem is connectivity?

It could! https://github.com/web-platform-tests/wpt-pr-bot/pull/49


Adding a Custom Login Screen to your HXE system

Tutorial URL: https://developers.sap.com/tutorials/hxe-custom-login.html
Is there a way to do the same on XSA ?

Hi, this is not possible. I believe this was addressed in the community too (it belongs there). Thanks!


Use img tag for image control instead of background-image

On the image control: why not using an  tag ? Currently, the image is inserted as a span`s background-image.
Accessibility-wise, content images should not be inserted this way as screen readers can't parse it. And as a pure styling matter, it makes manipulating image dimensions a pain, as we can't just let the image resize homothetically depending on intrinsic size and container limits and flow in the content, as an img would allow it.
In most case, using an img is the recommanded way to insert images.
And one more thing : the current background image vertical positioning of 40% feels weird. Why not centering the image in its container by default ?

trying to simplify image button with text

@JaufreyTpy How would you go about making the text more visible?
it is in a span that has this style
overflow: "hidden",
pointerEvents: "none",
position: "absolute",
zIndex: 0,
top: 0,
right: 0,
bottom: 0,
left: 0,
borderRadius: "inherit",
display: "flex",
justifyContent: "center",
alignItems: "center",

Wow... like this, it feels like a very bad idea to me. Whatever the solution we use, if we lay the text over the image there is too much risk for the text to lack readbility.
I would either put the text in a tooltip or place it under the image.

 Whatever the
solution we use, if we lay the text over the image there is too much risk
for the text to lack readbility.
I would either put the text in a tooltip or place it under the image.
—
Reply to this email directly, view it on GitHub
https://github.com/Avaiga/taipy-gui/issues/632#issuecomment-1449923976,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVQBA5AICFJAMNXMP5ZDDBDWZ4WABANCNFSM6AAAAAAVJIE23Q
.
You are receiving this because you were assigned.Message ID:
@.***>

from src.taipy.gui import Gui

my_image_file = "c:\\users\\jeu\\downloads\\fred.png"
my_svg_file = "c:\\users\\jeu\\downloads\\LogoTaipy.svg"
my_svg = """
<svg version="1.1"
    viewBox="0 0 300 200"
     xmlns="http://www.w3.org/2000/svg">
  <rect width="100%" height="100%" fill="red" />
  <circle cx="150" cy="100" r="80" fill="green" />
  <text x="150" y="125" font-size="60" text-anchor="middle" fill="white">SVG</text>
</svg>
"""

def on_action(state):
    print("on_action(state)")

page = """
<|toggle|theme|>
<|image|content={my_image_file}|width=unset|>
<|image|content={my_svg_file}|>
<|image|content={my_svg}|>
<|image|content={my_image_file}|label=image label|>
<|image|content={my_svg_file}|label=svg label|>
<|image|content={my_svg}|label=svg label|>
<|image|content={my_image_file}|on_action=on_action|>
<|image|content={my_svg_file}|on_action=on_action|>
<|image|content={my_svg}|on_action=on_action|>
<|image|content={my_image_file}|on_action=on_action|label=image label with action|>
<|image|content={my_svg_file}|on_action=on_action|label=svg label with action|>
<|image|content={my_svg}|on_action=on_action|label=svg label with action|>
"""

Gui(page=page).run(use_reloader=False, debug=True)


Application.java and Controller.java seem to have wrong indendation

e.g. generated java files contains Tab for methods main() and sayhello()

@Incarnation-p-lee


Update Cats to 0.7.2

Current coverage is 80.68% (diff: 100%)

Merging #361 into master will increase coverage by 0.10%

Powered by Codecov. Last update 304956f...e60da47


Clear all button doesn't clear everything

Here's a video showing the issue #1 that's present
Anything with a level or refinement doesn't get deleted, and some 5* mats also. As you can see in the video, the normal clear command works normally.

I read the source code, the default setting is lv1,refinement1,rank4 if not specified, so i should also provide these parameters to choose from. I will improve it in next version.


libdarknet_ros_lib.so:  undefined reference to `ipl_into_image'....where is the function "ipl_into_image" ?

[ 61%] Linking CXX shared library /home/nvidia/BLland_ws/devel/lib/libdarknet_ros_lib.so
[ 98%] Built target darknet_ros_lib
[ 98%] Linking CXX executable /home/nvidia/BLland_ws/devel/lib/darknet_ros/darknet_ros
/home/nvidia/BLland_ws/devel/lib/libdarknet_ros_lib.so: undefined reference to `ipl_into_image'
collect2: error: ld returned 1 exit status

where is the function "ipl_into_image" ?

solved

Hi, i have the same problem with you, could you tell me how do you solve the 'undefined reference to `ipl_into_image'? Thanks a lot!

Hey, could you tell me how to solve this problem, thanks

I have exactly the same problem. Please, if anyone knows the solution, it would be appreciated if you published it. Thank you.


Is there official support/no support for Sets?

I swear I read before something about Sets not working, but I'm striking out finding it again. Is it supposed to handle Sets, or is that out of scope currently? It looks like it saves them as empty objects.

Currently, it doesn't support Set, Map etc ...
For that we'd need to write/update the custom json serializer and deserializer to support those type

Right, of course. Is that something that fits in the design goals for this project, or not so much?
I'm currently using arrays/objects and then converting them as as they cross the memory/store boundary, which doesn't seem wrong.


Dockerfile updates

Hello,
This pull request changes Dockerfile so that the local working copy of localshop is built into a Docker image.  This is completely different from the way it currently works; feedback welcome.
Thank you.

Checking in on this, ping @mvantellingen


Burn hypercerts

Added test file
Closes #68

@ryscheng it's no longer minted, the entry is stored at the URI for the ClaimToken (TypeID, etc) and there's an event emitted for indexing purposes. In theory, the ClaimToken can be 'burned' by whiping the URI and the values amount.


Add a skip button

Add a button to accelerate the game and animations, passing everything faster.
Gotta see how it's done in VN games first, like, if it pauses when reaching a choice.

Closed by dac47fc7432fe368effe211b9603ab6fb88ebf0a


Installation-Building from source error

Hi
I've tried installing kasa using conda but the kasa build command gives me error- illegal instructions (core dumped).When I tried compiling the files using source,I am facing an error-
[ 97%] Building CXX object CMakeFiles/kASA.dir/zlib/gzstream.cpp.o
make[2]: *** No rule to make target '../zlib/zlibBuild/libz.a', needed by 'kASA'.  Stop.
make[1]: *** [CMakeFiles/Makefile2:142: CMakeFiles/kASA.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
I'm working in linux environment with config x86_64.
If you can kindly help me with the issue.Thank you!

Hi,
I have no idea why the build command from the conda installation fails because the information provided is not sufficient.
As for the built from source: Could it be, that you forgot to build the zlib beforehand? I tried the instructions from the Readme again on my Ubuntu 22.04 WSL and it worked so please double check if you've done it exactly as written.

Closed due to inactivity.


Add lombok support #205

At the moment lombok is downloaded to the LS directory but never used. This loads the plugin when loading the jdtls.

Is the -Xbootclasspath/a argument also not needed, for older Java versions?

@williamboman Java 9 removed the support for the flag I think. Not quite sure but releases from last 2 year doesn't seem to require the Xbootclasspath flag.

The reason the jdtls cmd doesn't include

Eclipse and Idea does not include Lombok too. But they are easy to enable in IDEs.

The idea is that people can include lombok manually should they want it (like so)

It doesn't work for me. Note that the where you put the flag is important here. If you append it after -jar it won't work

Do you know whether the lombok agent comes with much overhead?

Lombok is only being used at compile time. I don't think it is heavy at all.


Clarify the range of medlow code model on rv64

Range of medlow code model is highest 2GiB and lowest 2GiB, but the spec
only say lowest 2GiB.
And also put the detail to show how those range come from.
Ref:
[1] https://www.sifive.com/blog/all-aboard-part-4-risc-v-code-models

@palmer-dabbelt

Looks like this was introduced in https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/153.
@jim-wilson pointed it out in his review https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/153#discussion_r443149571, which apparently wasn't addressed.

@nick-knight thanks for dig out the history :)

Changes:

Rebase

Changes:

Apply @jrtc27's suggestion

Changes:

Fix wrong comment on calculate the medlow range for rv64


Generate Ruby gRPC file using the Ruby gem grpc-tools

Resolves #72.

Current coverage is 80.47% (diff: 94.73%)

Merging #84 into master will increase coverage by 0.40%

@@             master        #84   diff @@
==========================================
  Files            36         36
  Lines          1179       1214    +35
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            944        977    +33
- Misses          235        237     +2
  Partials          0          0

Powered by Codecov. Last update 0dac256...801ccae

It's sad, but @garrettjonesgoogle pointed out that possibly it's better to keep packman task for protoc. That's actually more consistent with other language pipelines. Sorry for my misunderstanding.
Let's revive the packman tasks, but

add --proto_compiler flag and --proto_compiler_args flag (if necessary) to the packman task. IIRC Python one is doing so already.
then, your copying task can be used to copy the result of packman's proto compilation to the expected file location.
also -- please fix Dockerfile to install grpc_tools_ruby_protoc command.

@jmuk, PTAL.
The packman task now uses the grpc-tools proto compiler as well as copies the files to the main repo.

Sorry I'm changing opinions so frequently, but as I commented at https://github.com/googleapis/packman/pull/104, I got unsure about the approach of --proto_compiler approach. I now think that the logic of grpc_tools_ruby_protoc if language == ruby should be in packman instead.
So sorry, but with that RubyGrpcPackmanTask wouldn't be necessary. Let's talk about this tomorrow.
By the way -- it's weird googlebot warns about CLA. Let's also talk about that.

@Landrito Looks like you haven't joined the google and googleapis groups. That's why you're getting the CLA request.

I added a relevant comment to https://github.com/googleapis/packman/pull/104 (the Python analogue) for this discussion.

Ah I see. I got added to the googleapis group but not the google group. It should be fixed now. Thanks for the heads up.

Hey -- you don't have to close this issue. Are you trying to create a new PR?
The difference of Python and Ruby is that currently Ruby is working. We just want to switch to the right tool.
But, the copy task will be still a good thing to do.

BTW, the correct Python analogue is actually https://github.com/googleapis/artman/pull/86

@jmuk This PR has been reduce down to only have the copy task. PTAL

LGTM!
Sorry for the confusion along with my saying.

No worries! Thanks for the review.


Modifier.pointerHoverIcon resets icon to default on click

Compose 1.0.0-beta3, Windows 11
https://user-images.githubusercontent.com/5963351/138863295-b61da859-54f5-4d1a-9cad-fa20de126886.mp4

Run run1 example from Compose sources
Hover Base button
Press Left mouse button

Actual:
Cursor icon changes to Default
Expected:
Cursor icon stays as Hand icon

Should be fixed in 1.0.0-beta6-dev474

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


Question: Where are kube-system configs defined (scaledown)

Specifically, to enable scale-down we need to specify Pod Disruption Budgets:
apiVersion: policy/v1beta1
kind: PodDisruptionBudget
metadata:
  name: heapster-pdb
  namespace: kube-system
spec:
  minAvailable: 1
  selector:
    matchLabels:
      k8s-app: heapster

However, it seems (At least for us) that the heapster deployment is defined with a single pod, what's the recommended practice?  Is there something we can do in the cluster.yaml to configure that?  Or is it generally recommended to have a follow up script that executes the required changes.
Thanks!

Hi @luck02, currently most of the deployments that form the basis of a standard kube-aws setup are defined inside cloud-config-controller. You will find this under the userdata folder during the rendering steps, look for the manifest references. If you wish to update them locally you can do so there prior to deploying/updating the stack and you should see the changes being reflected when the first new controller node launches.
If you think the updates should be part of our standard setup, we welcome contributions. Not everything is fully up to date with upstream k8s 1.8.x yet. The source for that is here.

Awesome ,thanks @c-knowles much appreciated!

I'd like to get that into kube-aws as part of the deployment.  I'm hoping to get time to work on that in the next couple of weeks.


Initial Version of New ReadMe (Also some other firmware changes that are still in progress)

Made a more detailed readme for the upcoming version.

Merge work in progress of all changes pertaining to non-blocking irrigation events, time based scheduling, and valve logic.


Java error=12, cannot allocate memory (also chmod)

Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!

A brief description

Java, chmod & other tools fail with "Cannot allocate memory" when trying to build an open source project (Apache Ranger). Same code builds fine on non-MS unix systems with less memory (ie 4GB -- this system has 16)

Expected results

Apache Ranger builds ok

Actual results (with terminal output if applicable)

jonesn@DESKTOP-2V27KS0:~/src/ranger$ cat ../ranger100.log | grep allocate
java.io.IOException: Cannot run program "chmod": error=12, Cannot allocate memory
Caused by: java.io.IOException: error=12, Cannot allocate memory
Caused by: java.io.IOException: Cannot run program "chmod": error=12, Cannot allocate memory
Caused by: java.io.IOException: error=12, Cannot allocate memory
java.io.IOException: Cannot run program "chmod": error=12, Cannot allocate memory
Caused by: java.io.IOException: error=12, Cannot allocate memory
Caused by: java.io.IOException: Cannot run program "chmod": error=12, Cannot allocate memory
Caused by: java.io.IOException: error=12, Cannot allocate memory
Caused by: java.io.IOException: Cannot run program "chmod": error=12, Cannot allocate memory
Caused by: java.io.IOException: error=12, Cannot allocate memory
(will attach full log)

Your Windows build number
14971

Steps / All commands required to reproduce the error from a brand new installation
Build apache ranger as per http://ranger.apache.org/quick_start_guide.html
(Note - open jdk 1.8 is installed, and as of 21/11/16 a 1.8 patch is needed as per https://reviews.apache.org/r/53924/ - business as usual. ...)

Strace of the failing command
not obtained

Required packages and commands to install
See apache page above

See our contributing instructions for assistance.

See http://pastebin.com/26fA3XHX for the ranger build logs. Search for "allocate"
Also:
jonesn@DESKTOP-2V27KS0:~/src$ free -m
total       used       free     shared    buffers     cached
Mem:         15946      10281       5664         17         33        184
-/+ buffers/cache:      10064       5882
Swap:         6873        473       6399

And here's the fork failure from the log:
Caused by: java.io.IOException: error=12, Cannot allocate memory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 40 more
And some version info:
jonesn@DESKTOP-2V27KS0:/mnt/c/tmp$ dpkg -l | grep openjdk
ii  openjdk-7-jdk:amd64                 7u121-2.6.8-1ubuntu<IP_ADDRESS>      amd64        OpenJDK Development Kit (JDK)
ii  openjdk-7-jre:amd64                 7u121-2.6.8-1ubuntu<IP_ADDRESS>      amd64        OpenJDK Java runtime, using Hotspot JIT
ii  openjdk-7-jre-headless:amd64        7u121-2.6.8-1ubuntu<IP_ADDRESS>      amd64        OpenJDK Java runtime, using Hotspot JIT (headless)
ii  openjdk-8-jdk:amd64                 8u111-b14-3~14.04.1               amd64        OpenJDK Development Kit (JDK)
ii  openjdk-8-jdk-headless:amd64        8u111-b14-3~14.04.1               amd64        OpenJDK Development Kit (JDK) (headless)
ii  openjdk-8-jre:amd64                 8u111-b14-3~14.04.1               amd64        OpenJDK Java runtime, using Hotspot JIT
ii  openjdk-8-jre-headless:amd64        8u111-b14-3~14.04.1               amd64        OpenJDK Java runtime, using Hotspot JIT (headless)
jonesn@DESKTOP-2V27KS0:/mnt/c/tmp$ java -version
openjdk version "1.8.0_111"
OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)

Hi @planetf1 -- thanks for reporting this!  I suspect that it might have the same underlying cause as #1019 ; specifically, some operations in WSL currently don't work properly if your system's page file is small as compared to your available RAM.  Could you try the instructions in the last comment on that ticket to see if they help your situation?

#1286 is also a dup.

Thanks. My virtual memory settings currently are
c: System Managed (11205 MB)
d: None
I have 16GB ram
Unfortunately I'm also rather constrainted on storage space -- it's a mere 120 GB SSD...  I'll however try setting it to a fixed size, say 16GB & report back

Setting to fixed 16GB allowed the compile to progress past this step. However it failed later on with a different error (one of the test cases seemed to exit prematurely). No obvious cause that I can precisely describe here for debugging in particular as the open source project is a new one for me that I'm getting up to speed with. I can only say the build is fine in regular ubuntu in hyper-v, or a remote system, or CentOS, so I'm going to have to revert to those environments for now. It would be good to understand more about the initial memory issue going on here though - I would have thought things should work just fine with a system managed page file? Thanks.

I assume (though I don't know for sure) that the memory limitation is due to the difference in the behavior of the NT kernel vs the Linux kernel:
Windows assumes that, if an application maps ("asks the kernel to let it use in the future") a block of virtual-memory pages, it does actually intend to use them eventually.  It therefore requires that enough memory currently be available, either as real physical memory or as swap, to allow the entirety of any given mapping to be allocated and to have data assigned to it.  If it gets some unmanageably-large allocations (I'm sure there are specific rules but I don't know the rules offhand), it doesn't necessarily grow the page file; it may instead choose to return an error code to indicate to the application that it probably doesn't want to be allocating that much memory on this machine.  This approach can be a little clunky/limiting, but it has some nice correctness guarantees and it tends to encourage good application behavior.
Linux pretty much always lets applications map whatever they want, whether or not it's reasonable on the current machine.  Therefore, for simplicity, some applications' runtimes (notably including Java; I'm not personally aware of any other major applications that do this to such a large extent) tend to map giant chunks of memory up front, presumably so that they don't have to think about mapping more memory later.  They then allocate and use only as much memory as they actually use.  If they allocate more memory than is available on the system (and the swap file runs out of space, etc), which they can do because the kernel has already promised the mapping, at that point it's too late for the kernel to provide an error code; the only correct thing it can do is to force-kill the application.
Supporting the Linux behavior on Windows would therefore require either allowing the Windows pagefile to grow much larger than the amount of memory that Java is likely to actually use, just in case it does use it (which would be problematic on machines like yours with limited disk space), or implementing the Linux out-of-memory killer in Windows, which I would expect to require a change to the core NT kernel (not WSL-specific code).
(Disclaimer:  I'm not actually a WSL dev, just a Windows and Linux user; this is just my best guess at the cause based on the behavior of the two kernels' public APIs, it's certainly possible that there's a different limitation going on under the hood.)

The chakracore guys allocate 32GB of virtual memory out of the gate, lol. I made a 40GB page file to make it start. #708.

Linux also has some interesting semantics around noreserve that we aren't currently honoring 100%. We have a work item to improve this scenario in a few ways:

Count swap size as maximum page size not current page size
Potentially allow overcommit (toggelable via a procfs file just like real Linux.
Honor noreserve semantics.

This work is in progress.

Thanks for the update, I'm familiar with how some of the different memory allocation algorithms differ between OSs.... Good to hear it's an area that's evolving.  I'll keep prodding at the area for other projects and see how things go especially as I'm tracking the insider builds anyway.

This should be resolved in recent Windows Insider builds. Please reopen if you continue to have issues.

@benhillis https://gist.github.com/shelru/b44272a3b0a2cee4e17a2f9b28f18056

Some error, on last preview

@shelru - It seems like you are running build 14393, which is the Anniversary Update build. This issue is fixed in the insider builds, the updates for which are not yet available to Anniversary Update build. You can either wait for the Creators Update build (which will be an update to the Anniversary Update build) or try out the Insider builds.


Fix typos, add full stops, fix JSON

Nice work! The application looks very good and storing whiteboards in Matrix is a great idea.
Here are some suggestions for improving the project's documentation.

This is super kind! @jaller94 Thank you so much!
This was really important to do.


[ACM-8209] Refactored code for cleanup

Description
Refactor code to reduce code smells.
Related Issue
https://issues.redhat.com/browse/ACM-8209
Changes Made
Updated code to reduce code smells.
Screenshots (if applicable)
Add screenshots or GIFs that demonstrate the changes visually, if relevant.
Checklist

[ ] I have tested the changes locally and they are functioning as expected.
[ ] I have updated the documentation (if necessary) to reflect the changes.
[ ] I have added/updated relevant unit tests (if applicable).
[ ] I have ensured that my code follows the project's coding standards.
[ ] I have checked for any potential security issues and addressed them.
[ ] I have added necessary comments to the code, especially in complex or unclear sections.
[ ] I have rebased my branch on top of the latest main/master branch.

Additional Notes
Add any additional notes, context, or information that might be helpful for reviewers.
Reviewers
Tag the appropriate reviewers who should review this pull request. To add reviewers, please add the following line: /cc @reviewer1 @reviewer2
/cc @cameronmwall @ngraham20
Definition of Done

[ ] Code is reviewed.
[ ] Code is tested.
[ ] Documentation is updated.
[ ] All checks and tests pass.
[ ] Approved by at least one reviewer.
[ ] Merged into the main/master branch.

/retest

/override sonar-pre-submit
Will override the sonar pre submit job, since the code changes that were made are mostly correcting print statements and removing redundant or unused code.

/override ci/prow/sonar-pre-submit
Will override the sonar pre submit job, since the code changes that were made are mostly correcting print statements and removing redundant or unused code.

I will work towards adding more test cases in a separate PR.

/lgtm


Embeds Aren't Responsive

They are broken and increase the page width and things, we should set some css to fix this

Duplicate of #21


Specify grafana version

Backport the Grafana version fix to the 1.0 release

Usually, we are backporting to a staging branch, then merging that staging branch to 1-0 after testing it on an LR network.
@peterschwarz @dcmiddle Thoughts on skipping the 1-0-staging-00 branch based on the nature of this change? Seems pretty safe but then we aren't testing the specific resulting commit id (which @dcmiddle has advocated for previousy).  I think it should probably go to 1-0-staging-00 unless there is a specific reason not to do that.


Reduce docker image size

The dockerfiles have now utilize a multi-stage build in order
to avoid running chown .... on the /opt directory at build time.
Additionally, building the container will now require a later version
of docker (19.03) due to the use of ARGs in the --chown flag
After these changes:

alluxio/alluxio: 688M
alluxio/alluxio-fuse: 1.08G

Closes #9896

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/Alluxio-Pull-Request-Builder/5975/
Test FAILed.

jenkins, test 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/Alluxio-Pull-Request-Builder/5981/
Test PASSed.

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/Alluxio-Pull-Request-Builder/5990/
Test PASSed.

@jiacheliu3 my understanding is that this is a build time requirement. in that case we don't need to update the doc. @ZacBlanco can confirm

alluxio-bot, merge this please

@madanadit do we want to cherry-pick this to branch-2.0 as well?

@ZacBlanco the non-root user change did not go into branch-2.0, so we don't need to cherry-pick.


Add Internal/Friends Execute Stored Procedure Function With PK Range Id Option

Add Internal/Friends Execute Stored Procedure Function With PK Range Id Option.
Add an internal/Friends "ReadPartitionKeyRangeFeedAsync" client/container function for Cosmos DB V3 .NET SDK similar to V2.

For things like this, would love to see eve a one-liner as to the use case
For instance I'd be interested to see if the stored proc exec overlaps with the bulk facility as covered in https://github.com/Azure/azure-cosmos-dotnet-v3/issues/1496#issuecomment-1674933345

All public Stroe procedure invocations are scoped to a single logical partition key.
There are some internal specific use cases where this capability is needed (ex: V2 bulk library etc...)

This is covered with msdata PR: 1322381

PR merged to master


[SPARK-50348][PYTHON] Make static import Python data source configurable

What changes were proposed in this pull request?

This PR adds a new static config spark.sql.pyspark.sources.staticImport.enabled (default: true) to make the static import of Python data sources configurable.
Why are the changes needed?

This allows users to enable or disable the automatic loading of all Python data sources installed in the environment, providing greater flexibility over resource usage and startup behavior.
Does this PR introduce any user-facing change?

No
How was this patch tested?

UT and spark shell
Was this patch authored or co-authored using generative AI tooling?

No

This PR no longer needed (replaced by https://github.com/apache/spark/pull/48971)


Revert "Revert "new protocol (chrome 62)""

Reverts MasterDevs/ChromeDevTools#29

I reverted a PR that I thought broke the build.  It appears something else is wrong.  So I'm un-reverting the PR here.


Plugin is using deprecated register function

videojs-hotkeys is using videojs.plugin() instead of videojs.registerPlugin(). plugin() is deprecated and may be removed in future versions of videojs, so it would be nice to rewrite it to registerPlugin().

Or make it future-proof:
// Cross-compatibility for Video.js 5 and 6.
var registerPlugin = videojs.registerPlugin || videojs.plugin;


[rocko] edk2: deploy fip.bin directly into $DEPLOYDIR/bootloader/

Same as master.

closing this PR because it should be cherry-picked from https://github.com/96boards/meta-96boards/pull/213 once it's merged in master.


[Tables] Unify error handling for multiple operations on batching with .NET/Java

Parse out the body from the returned error and use that to raise a singular exception. Cosmos and Tables raise different errors when a single row has multiple operations on it in a single batch.

@seankane-msft Do you know who owns configuration for the bot? I think we got mistakenly tagged here


Added a missing lim in proof of Proposition 8.14

There is a limit missing in the proof of Proposition 8.14

Thanks again! Much appreciated.


Create 1.49.0.yaml

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate <manifest>, where <manifest> is the name of the manifest you're submitting?
[ ] Have you tested your manifest locally with winget install -m <manifest>?

Microsoft Reviewers: Open in CodeFlow

Thanks for contributing. I think you need to change the name of the yaml file too.
See: https://docs.github.com/en/github/managing-files-in-a-repository/renaming-a-file

This pr needs to be closed.  1.49.0 is exist with this pr: #3549


fix: config dev port (fix #317)

Description
Dev port was always 6006 when not defined in the command line
Additional context
Example histoire config:
// vite.config.js
/// <reference types="histoire" />

import { defineConfig } from 'vite'

export default defineConfig({
  // ...
  histoire: {
    vite: {
      server: {
        port: 1980,
      },
    },
  },
})

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

What happens when we don't configure the port in histoire config? Will it be the normal vite port? I'd prefer it to be 6006 by default unless explicitly set in histoireConfig.vite.server.port.

Hum, I see... I updated the fix so that the port configured in the vite config file default to 6006.


Support run tox

The following are automatically added:

Add reviewers from OWNER file (in the root of the repository) under reviewers section.
Set PR size label.
New issue is created for the PR.

Available user actions:

To mark PR as verified add !verified to a PR comment, to un-verify add !-verified to a PR comment.
Verified label removed on each new commit push.
To cherry pick a merged PR add !cherry-pick <target branch to cherry-pick to> to a PR comment.
To add a label by comment use !<label name>, to remove, use !-<label name>
Supported labels:      * do-not-merge

verified
wip
lgtm

code-check: install_deps> python -I -m pip install pre-commit
code-check: commands[0]> pre-commit run --all-files
[INFO] Initializing environment for https://github.com/myint/autoflake.
[INFO] Initializing environment for https://github.com/hadialqattan/pycln.
[INFO] Initializing environment for https://github.com/PyCQA/flake8:flake8-mutable,git+https://github.com/RedHatQE/flake8-plugins.git,pep8-naming.
[INFO] Installing environment for https://github.com/myint/autoflake.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/hadialqattan/pycln.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/PyCQA/flake8.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
autoflake................................................................Passed
pycln....................................................................Failed

hook id: pycln
exit code: 1

webhook-server-container/github_api.py:614:1 SyntaxError: invalid syntax '<<<<<<< HEAD' ⛔
webhook-server-container/github_api.py:614:1 SyntaxError: invalid syntax '<<<<<<< HEAD' ⛔
webhook-server-container/github_api.py:614:1 SyntaxError: invalid syntax '<<<<<<< HEAD' ⛔
Oh no, there were errors! 💔 ☹
5 files left unchanged, 3 files have failed to be cleaned.
isort....................................................................Passed
black....................................................................Failed

hook id: black
exit code: 123

error: cannot format webhook-server-container/github_api.py: Cannot parse: 614:0: <<<<<<< HEAD
Oh no! 💥 💔 💥
5 files left unchanged, 1 file failed to reformat.
check for merge conflicts................................................Passed
debug statements (python)................................................Failed

hook id: debug-statements
exit code: 1

webhook-server-container/github_api.py - Could not parse ast
Traceback (most recent call last):
  File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/lib/python3.9/site-packages/pre_commit_hooks/debug_statement_hook.py", line 56, in check_file
    ast_obj = ast.parse(f.read(), filename=filename)
  File "/usr/local/lib/python3.9/ast.py", line 50, in parse
    return compile(source, filename, mode, flags,
  File "webhook-server-container/github_api.py", line 614
    <<<<<<< HEAD
    ^
SyntaxError: invalid syntax

webhook-server-container/github_api.py - Could not parse ast
Traceback (most recent call last):
  File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/lib/python3.9/site-packages/pre_commit_hooks/debug_statement_hook.py", line 56, in check_file
    ast_obj = ast.parse(f.read(), filename=filename)
  File "/usr/local/lib/python3.9/ast.py", line 50, in parse
    return compile(source, filename, mode, flags,
  File "webhook-server-container/github_api.py", line 614
    <<<<<<< HEAD
    ^
SyntaxError: invalid syntax

webhook-server-container/github_api.py - Could not parse ast
Traceback (most recent call last):
  File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/lib/python3.9/site-packages/pre_commit_hooks/debug_statement_hook.py", line 56, in check_file
    ast_obj = ast.parse(f.read(), filename=filename)
  File "/usr/local/lib/python3.9/ast.py", line 50, in parse
    return compile(source, filename, mode, flags,
  File "webhook-server-container/github_api.py", line 614
    <<<<<<< HEAD
    ^
SyntaxError: invalid syntax

trim trailing whitespace.................................................Passed
fix end of files.........................................................Passed
check python ast.........................................................Failed

hook id: check-ast
exit code: 1

webhook-server-container/github_api.py: failed parsing with CPython 3.9.16:
Traceback (most recent call last):
  File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/lib/python3.9/site-packages/pre_commit_hooks/check_ast.py", line 21, in main
    ast.parse(f.read(), filename=filename)
  File "/usr/local/lib/python3.9/ast.py", line 50, in parse
    return compile(source, filename, mode, flags,
  File "webhook-server-container/github_api.py", line 614
    <<<<<<< HEAD
    ^
SyntaxError: invalid syntax

webhook-server-container/github_api.py: failed parsing with CPython 3.9.16:
Traceback (most recent call last):
  File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/lib/python3.9/site-packages/pre_commit_hooks/check_ast.py", line 21, in main
    ast.parse(f.read(), filename=filename)
  File "/usr/local/lib/python3.9/ast.py", line 50, in parse
    return compile(source, filename, mode, flags,
  File "webhook-server-container/github_api.py", line 614
    <<<<<<< HEAD
    ^
SyntaxError: invalid syntax

webhook-server-container/github_api.py: failed parsing with CPython 3.9.16:
Traceback (most recent call last):
  File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/lib/python3.9/site-packages/pre_commit_hooks/check_ast.py", line 21, in main
    ast.parse(f.read(), filename=filename)
  File "/usr/local/lib/python3.9/ast.py", line 50, in parse
    return compile(source, filename, mode, flags,
  File "webhook-server-container/github_api.py", line 614
    <<<<<<< HEAD
    ^
SyntaxError: invalid syntax

check builtin type constructor use.......................................Failed

hook id: check-builtin-literals
exit code: 1

Traceback (most recent call last):
File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/bin/check-builtin-literals", line 8, in
sys.exit(main())
File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/lib/python3.9/site-packages/pre_commit_hooks/check_builtin_literals.py", line 89, in main
calls = check_file(
File "/root/.cache/pre-commit/repoopxhhp2n/py_env-python3/lib/python3.9/site-packages/pre_commit_hooks/check_builtin_literals.py", line 62, in check_file
tree = ast.parse(f.read(), filename=filename)
File "/usr/local/lib/python3.9/ast.py", line 50, in parse
return compile(source, filename, mode, flags,
File "webhook-server-container/github_api.py", line 614
<<<<<<< HEAD
^
SyntaxError: invalid syntax
flake8...................................................................Failed

hook id: flake8
exit code: 1

webhook-server-container/github_api.py:614:1: E999 SyntaxError: invalid syntax
webhook-server-container/github_api.py:614:1: E999 SyntaxError: invalid syntax
webhook-server-container/github_api.py:614:1: E999 SyntaxError: invalid syntax
code-check: exit 1 (37.47 seconds) /github-gitlab-webhook-server-tox-43384be2-0db0-4db0-b214-90b5cb77373b> pre-commit run --all-files pid=868
code-check: FAIL code 1 (41.64=setup[4.17]+cmd[37.47] seconds)
evaluation failed :( (41.79 seconds)

!verified


Dynamic Trees not animated by Shaders

I have Millenaire, Dynamic Trees and Shaders installed. Vanilla trees created by the Millenaire villagers are animated by the shaders - that is, the leaf blocks sway in a 'breeze' - but those of DT are not.

I updated to the latest version, just to be safe:
Sildurs Vibrant Shaders v1.17 Extreme
https://www.minecraftforum.net/forums/mapping-and-modding-java-edition/minecraft-mods/1291396-1-6-4-1-12-2-sildurs-shaders-pc-mac-intel

What MC version are you using?

I can confirm this, although I'm not sure why the leaves aren't animated since the animations seem to work on other modded leaves.

 I was able to solve the issue by updating to version 0.7.3c.

It seems shaders just don't recognize modded leaves at all, but Better Foliage will fix this. If you don't like Better Foliage, you can install it and then disable the mod using it's in-game options menu and it will still make modded leaves wave.

Weird, my DT mod file is DynamicTrees-1.12.2-0.7.4.jar.

Did the better foliage suggestion resolve your problem?

Confirmed: BetterFoliage-MC1.12-2.1.10 fixes the issue, thanks.

The conclusion here is that Better Foliage adds code to allow modded leaves to sway properly with optifine.  Thanks OctarineNoise!


Any result on more longer max_length? just like 2k,4k,8k ...

Hi  Shadow.
We just released 1B pretrained models with 1024 token context size. I know it's quite a late response but I thought it might be still useful for you.
https://github.com/McGill-NLP/length-generalization#1b-scale-pretrained-models


Split date and time entry

What you want:
In the data entry screen, split the date entry from time, i.e. have two different fields that can be clicked on.
Why you want it:
This is only very minor, but would save me one tap each time! I quite often have to change the time field (e.g. because I took the reading earlier in the day, but didn't enter it into the app until later), but not the date field. At the moment, I click the combined field and always have to immediately click Next to get to the time entry. As I say, not the end of the world, but slightly annoying each time. It would be great if I could skip directly to the time entry.
The only downsides I can see to having two fields is 1) a little more visual clutter (two boxes rather than one) on the data entry screen, and 2) if there are users who regularly edit both date and time, they would actually require one extra screen tap.
Presumably you don't have any analytics to be able to tell whether scenario 2 is common or not. My gut feeling is that it wouldn't be common to want to change both date and time, but I could be wrong.
Thanks for reading :)

Thanks for the input. You are correct, I don't have analytics on this. Material 3 also recommends splitting date and time input and I assume they did some research.
From my own app usage and common use cases I had in mind while building there is no real need for combining the inputs. I would even say that changing the date is never required during regular usage. Currently, the time input shows the time in the user-specified format. Unless you have a better idea I would have to ignore the user format here.
About the visual clutter: Two boxes (without two pens) would be fine but I don't know how (new) users would know that those are editable.

This could be influenced by how #309 turns out.

Thanks for your considered response. I agree two boxes wouldn't be too cluttered. On my screen, there would even be room for two pens. Although, I'm not sure you need the pens - I think it might be more discoverable than you think for users to try clicking on them to edit them, especially if you make sure they look like the other editable inputs. Maybe it would help if you put field titles (i.e. "Date" and "Time") in the top borders of the two boxes.
I'm not sure what you mean about ignoring the user format for time?

@JohnVeness I mocked up 3 designs for an input. What do you think?

I don't quite like either of them so feel free to suggest something different. The first one feels allot like a text input, the third one is quite cluttered and the second one, while very visually clear looks unlike the rest of the form and has too much emphasis in my opinion.

Thanks for the mockups. Personally I think the first one looks fine. I get what you're saying that they look like text inputs, but I think that's OK as it would encourage people to click in them, and they would soon see that they are specialist inputs. It'd be like the Color input - it looks like a textbox, but you soon learn it isn't.


Making the library safer to use.

Hello!
This library is useful but I ran into a few issues which I then proceeded to solve and include in this PR.
The main two changes are:

No longer modifying the underlying data provided to NewBStreamReader(data []byte). It caused all sorts of weird unexpected behavior because it's not usually the case in idiomatic Go that readers modify data.

Now supporting reading & writing on the same *BStream object. Previously a single remainCount int was used to track both operations, which meant that data corruption would happen.

Sorry for the late reply, thank you for your PR


Fire Emblem logo blending seems off

contrasted to

Looks like the blend targets haven't quite worked out

There's some clever PPU shenanigans going on here.  Background 0 is the fire effect and has highest priority.
The obj window is set up such that obj window has blending, bg 0 and objs but not other backgrounds. bg 0 is disabled outside of windows.
So we really should only be seeing fire effect blended on the object window areas.

The issue was that the sprites were large palette and I'd mixed up how to calculate backdrop color of a pixel on large palette but only for obj window


Add .debug_frame based stack unwinding

related #293
also, see https://github.com/parca-dev/parca-agent/issues/782 (.zdebug_frame)

[ ] DWARF64 parsing support
[ ] Ability to specify additional debug information

This has some good information on the differences: https://docs.rs/gimli/0.16.0/gimli/struct.DebugFrame.html#differences-between-debug_frame-and-eh_frame

Parca Agent amd64 and arm64 of v0.9.1 have .eh_frame sections: https://gist.github.com/brancz/b163d154e9f8179051ef457f0f4a9983

The x86_64 ABI require .eh_frame (it's a loadable section), but not .debug_frame. So far we've been able to profile all the native processes we tried with the DWARF CFI info in the former section.
Are there any users/customers that need .debug_frame support?

The x86_64 ABI require .eh_frame (it's a loadable section), but not .debug_frame. So far we've been able to profile all the native processes we tried with the DWARF CFI info in the former section.
Are there any users/customers that need .debug_frame support?

Maybe another question, is there a case where we don't have .eh_frame but .debug_frame?
I'm happy to close it until we have an actual request or real-life case.

Maybe another question, is there a case where we don't have .eh_frame but .debug_frame?

Not that I know of, but my knowledge here might not be complete

The x86_64 ABI require .eh_frame (it's a loadable section), but not .debug_frame. So far we've been able to profile all the native processes we tried with the DWARF CFI info in the former section.
Are there any users/customers that need .debug_frame support?

Maybe another question, is there a case where we don't have .eh_frame but .debug_frame?

Wasn't that the case with CGO applications :thinking: But I don't remember exactly what was the conclusion of the research when we looked for it last time.
But I agree though. We should probably wait for working on this until we come across the real use case.

I've been put in contact with the engineers working on debuginfo on the GraalVM and it turns out that it only populates .debug_frame, and any entries in .eh_frame only happen to be there because of GCC. (RE: #1915)


Broken spec?

I tried multiple generators (https://github.com/asyncapi/nodejs-ws-template#cli and https://github.com/pearmaster/asyncapi-codegen) to generate the async-api. I just cloned this repo and tried to generate the s2-rm.yaml from the s2-asyncapi folder. The generators all failed. I think you miss "type: string" before the currency enum.
It would be nice if you could add instructions to the readme on how you generate the code from your end so that people know how the spec was tested.

Hi, thanks for taking an interest in S2!
Although AsyncAPI seems the best fit for what we want to specify here (JSON messages over a WebSocket), we've noticed that the OpenAPI specification itself is still being changed quite often and that the code generators are not yet of a very high quality. That is why we ourselves work with the JSON Schema's or even the OpenAPI specification (and ignore the REST stuff and implement the WebSocket ourselves), since they are much more mature.
The easiest way to get started is to use the s2-python module... if you're planning to use Python. For other programming languages I would advise you to start with JSON Schema.
Having said that, I agree the README and the OpenAPI specification can be improved. I'll keep this issue open until these points are addressed.
Also don't forget to check out the s2-analyzer project.
Cheers,
Wilco


idea to make go faster and still easy.

i have idea to make go faster and still easy.
i see in rust they use Ownership and borrowing to make faster program but it is difficult to use .
the idea i have is to add two keyword the first keyword is unsafe like rust the second is Ownership the Ownership is just keyword that start code block like unsafe.
this two keyword will make golang code work very fast and still easy to read and write.
just to know if they add this two keyword in golang new version i don't think old code will brock.

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


Two-handed tremor, and app color

fix primary app color to match the tulip logo on the study overview screen (since that image is not made in a way that allows it to take on the app tint color)

looks good


Windows - NumericUpDown doesn't load the first time since .NET MAUI 6.0.312

I have noticed that with the new version 6.0.312 of .NET MAUI the NumericUpDown control in Windows is no longer loaded the first time it is rendered, however if you navigate back and return to the page it will be displayed, in Android it works fine .

Same thing happenning in ProgressRadial page. Hopefully new releases will fix this >_<

The issue will be fixed with the upcoming .NET MAUI SR.


leading TAB by snippets won't replace by spaces

VSCode Version: 1.46.1
OS Version: Linux x64 4.4.0-184-generic

Steps to Reproduce:

Create a simple snippet with leading \t
Use snippet while vscode is in Indent using spaces mode.
All '\ts would be replaced by spaces except the leading one.

Does this issue occur when all extensions are disabled?: Yes
Sample user snippet (shellscript.json):
{
  "test": {
    "prefix": "test",
    "body": "\tHello World\n\tNew Line",
    "description": "Test snippet"
  }
}

I'm using  2 spaces at \t and here is the result:
🡒Hello.World
 ..New.Line

The TAB before Hello is not replaced with spaces.

Looks like we do that on purpose but the question is why...

To make a good example of double standard?

I think it's more a case of "why would one author a script like that?". Fix should be easy and I don't see an obvious negative impact

Thanks. The actual snippet where I faced this issue is here.

Confused? That snippet doesn't start with \t on its first line

In that snippet it happens at the first line after comment. Line 11 start's with \t.
..# comment out next...
🡒trap 'tput...
..trap 'exit...

Thanks for clarifying. I have pushed a failing/omitted test for this but fixing this is actually harder then I thought. Not sure anymore if this will happen in July


Reduce the interceptor logging on DEBUG

In my eyes the geoserver interceptor was logging too much on the DEBUG level, which lead to messy logs during development (and may even slow down the performance) as a lot of "trace-level" information like HTTP headers etc were logged.
This will PR changes some logs from DEBUG to TRACE, but for an intercepted request, the following logs will still remain on DEBUG:
2017-10-17 14:57:27,995 DEBUG [de.terrestris.shogun2.service.GeoServerInterceptorService] - Finding the GeoServer base URI by the provided EndPoint: foo:bar
2017-10-17 14:57:27,999 DEBUG [de.terrestris.shogun2.service.GeoServerInterceptorService] - The corresponding GeoServer base URI is: http://localhost:8080/geoserver/foo/ows
2017-10-17 14:57:27,999 DEBUG [de.terrestris.shogun2.util.interceptor.OgcMessageDistributor] - Request is ALLOWED, not intercepting the request.
2017-10-17 14:57:28,184 DEBUG [de.terrestris.shogun2.util.interceptor.OgcMessageDistributor] - Response is ALLOWED, not intercepting the response.

LGTM. Please merge at will.


Add support laravel 6.0

Question
Answer

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed tickets
comma-separated list of tickets fixed by the PR, if any

License
MIT

Doc PR
reference to the documentation PR, if any

php 7.3
branch: master

my PR:

I'm guessing this line needs to be updated?
https://github.com/php-cache/cache/blob/202cd2b3433e5841d822c4a3a24ee20ac656c88d/src/Adapter/Illuminate/IlluminateCachePool.php#L47
https://laravel.com/docs/5.8/upgrade#cache-ttl-in-seconds

no longer relevant, sawed out the library and advise others.

@rez1dent3 anything I could help to speed up supporting Laravel 6.x?

FWIW, the only change I needed to make for it to work with my Laravel 6 project was the version bump

Using Symfony's cache adapter worked for me.


Clean-up code is not executed in some cases with streaming responses if client cancels the request

This is continuation of the discussion from https://github.com/emmett-framework/granian/issues/286#issuecomment-2389694146
Hello! I experience an issue when running Litestar with Granian that I do not have when use Uvicorn. In the previous discussion I don't think I've provided a sufficient illustration.
Here’s a new one:
import asyncio
import math
import typing

import litestar
from litestar.response import ServerSentEvent

async def iter_sse_data() -> typing.AsyncIterable[str]:
    yield "hi"
    try:
        print("about to sleep indefinitely")
        await asyncio.sleep(math.inf)
    finally:
        print("cleaned up")

@litestar.get("/")
async def root() -> ServerSentEvent:
    return ServerSentEvent(iter_sse_data())

app = litestar.Litestar([root])

Run the app with Granian.
Run curl http://localhost:8000/, wait for data: hi and press Ctrl+C.
See that logs do not contain cleaned up.

Run the app with Uvicorn—and you’ll see that cleaned up was printed.

I'm happy to file an issue in Litestar repository, but it seems weird to me that Uvicorn behavior is different.

Hi @vrslev,
I probably need to clarify the underlying Granian behaviour before everything else, as there is a major difference when compared to uvicorn – which is indeed the difference you experience when comparing the two:

Granian won't be able to notify to the application when the connection gets closed by the client. As explained in #286, this is due to the design of the Hyper crate, which is used by Granian to deal with HTTP protocol. Uvicorn, on the other side, rely on asyncio Protocol, which includes this capability.
This means Granian will notify the application about the closed connection only on a receive or send operation. You can think about this difference in the same way of eager and lazy code.

Now, getting back to the various MREs you provided, we can divide those into two main categories:

cases in which you keep receiving/sending data
cases in which you block indefinitely waiting for a connection close

Now, while the former ones should work as expected in Granian, as the only difference when compared to Uvicorn is that you delay the application cancellation to the time between two send operations, the latter cannot be implemented at all in Granian (which is what #286 OP is about).
To my perspective, given all of your examples are based on SSE, you should be able to do cleanup operations with no issues, as soon as you don't block the send iterator and use a separated asyncio task to achieve the result.
Conditions in which an async iterator responsible of sending data blocks indefinitely are borderline cases for SSE, and should probably be implemented otherwise (websockets sounds like a better option to me).
Which is also why #286 is related, but not representative of your case: the whole point behind that issue is to stop running expensive operations if the client disconnects, not to perform blocking operations before/during/after the request.
To summarise: while #286 might be resolved in the future (but again, that really depends on the underlying libraries), it is quite hard for me to imagine granian would ever support blocking streams in an async protocol – to be even more clear, even if #286 will be fixed, it won't change the fact blocking an iterator forever will block the whole app forever.

Hi @gi0baro! Thanks for rich clarification!
My initial MRE contained Redis BLPOP that block indefinitely:
import contextlib
import typing

import litestar
import redis.asyncio
from litestar.response import ServerSentEvent

@contextlib.asynccontextmanager
async def create_redis_client() -> typing.AsyncGenerator[redis.asyncio.Redis, None]:
    redis_client = redis.asyncio.Redis(host="localhost", port="6379")
    try:
        await redis_client.initialize()
        print("initialized redis client")
        yield redis_client
    finally:
        await redis_client.aclose()
        print("closed redis client")

redis_list_key = "whatever"

async def iter_sse_data() -> typing.AsyncIterable[str]:
    async with create_redis_client() as redis_client:
        while True:
            try:
                # BLPOP blocks redis client until an item in list is available,
                # i. e. you can't do anything with the client while waiting here.
                _list_key, event_content = await redis_client.blpop(redis_list_key)
            except BaseException as exception:
                print("caught an exception from blpop:", exception)
                raise exception

            yield event_content

@litestar.get("/sse")
async def root() -> ServerSentEvent:
    return ServerSentEvent(iter_sse_data())

app = litestar.Litestar([root])

Removing the infinitely blocking operations and changing clean-up step to be executed in separate asyncio task, indeed, makes it work as expected:
import asyncio
import contextlib
import typing

import litestar
import redis.asyncio
from litestar.response import ServerSentEvent

@contextlib.asynccontextmanager
async def create_redis_client() -> typing.AsyncGenerator[redis.asyncio.Redis, None]:
    redis_client = redis.asyncio.Redis(host="localhost", port="6379")
    try:
        await redis_client.initialize()
        print("initialized redis client")
        yield redis_client
    finally:

        async def close_redis_client() -> None:
            await redis_client.aclose()
            print("closed redis client")

        asyncio.create_task(close_redis_client())

async def iter_sse_data() -> typing.AsyncIterable[str]:
    async with create_redis_client() as redis_client:
        while True:
            if blpop_result := await redis_client.blpop("whatever", timeout=5):
                _list_key, event_content = blpop_result
                yield event_content
            else:
                yield None

@litestar.get("/")
async def root() -> ServerSentEvent:
    return ServerSentEvent(iter_sse_data())

app = litestar.Litestar([root])

@vrslev out of curiosity, any specific reason for using a single list key with blpop instead of pub/sub?

We needed exactly-once delivery with persistence

Also, it's one-to-one, so there's no need for anything more sotisficated

As I remember, sub in Redis is blocking operation as well

As I remember, sub in Redis is blocking operation as well

It's an async iterable, so for the specific context yes. The main difference is that it doesn't lock the entire redis client, so you won't need to initialize/destroy the client per every request.

Hi again! As I can see, there're two issues:
Litestar immediately cancels execution of async iterator when client disconnects

To my perspective, given all of your examples are based on SSE, you should be able to do cleanup operations with no issues, as soon as you don't block the send iterator and use a separated asyncio task to achieve the result.

This can be mitigated with use of anyio.CancelScope(shield=True) in case of Uvicorn, and with running the clean-up in separate task (asyncio.create_task()) in case of Granian.
I'm not sure who'd be responsible for this issue: Litestar or Granian, since the behavior differs between Uvicorn and Granian. I've posted the issue for Litestar before starting discussion in #286: https://github.com/litestar-org/litestar/issues/3772, though now I think it should be updated but not sure how exactly.
Support for blocking streams in async protocol

it is quite hard for me to imagine granian would ever support blocking streams in an async protocol

This one is when you block async iterator indefinitely. MRE in the first comment of this issue is sufficient, though the title should be updated probably.
As I understand, it can be a "wontfix" issue, but it definitely belongs to Granian.

I'd say https://github.com/litestar-org/litestar/issues/3772 should be addressed on their side (based on their own judgement) independently of Granian – also 'cause I can't see any way for Granian to fix that on its side. On the fact that the solution appears to be different from Uvicorn, I'd say the separated task should work on Uvicorn as well – but I need to better check the code to be sure.
On the other aspect, I think it can be also seen as an indirect consequence of #286, meaning that having #286 fixed would at least give options to manually handle a blocking case using cancellation as a trigger. So if we come to the agreement that this is not related to SSE/iterators per se, I'm willing to merge the two issues.

Understood 👍


Topic/joint limits

Added the joint limit parsing and storage.
Joint limits are "statically" stored in the joint model and "dynamically" computed with algorithm jointLimits.
There are a few warning "unused parameters"  due to the fact that for the moment limits do not change. But in the future we could have a limit for each joint depending on the configuration or other.

Good job, but I think that the default value for joint limits in addBody could lead to unexpected behaviors because the size of the vector is not the same as the the joint configuration vector.
Moreover, the correction of indentation is only partial. I think we need to postpone this commit to deal with this problem globally.

In fact in the method jointBase::set<effort/limits> there is a check on the size of the vector. If the vector is valid then we use it. If it is not valid, we implement a default value. ( we fill the limits with default values : +/- inf )
The point on this is because of retrocompatibility : to ensure retrocompatibility with previous calls of addBody, i have put the limits at the end of the function call BUT as there are optional arguments, these arguments must be also optional. That's why i decided to use this default value.

should be better now

Just a last point, you might change the type of return for accessors of joint limits in src/multibody/joint/joint-base.hpp by returning a const reference. Just a matter of performances.


Increase title.max_length in Gallery and Photo

I'm proposing to increase the maximum allowed length of the title fields in both the Gallery and the Photo model. My experience is that the current limit is to restrictive; a common gallery title like this

2015-01-01 person A, person B & person C - playing music in a very impressive location

does not fit into a 50 char text field. Is there a rationale behind having the limit at 50 or 60 characters?

There's no rationale behind 50/60 chars - other than it sounds like a sensible limit :-)
My only reservation about increasing the length of the fields is the use of database space for users with 10 of thousands of photos; but it's probably an edge case. So I'm happy with your proposal.
I do have one request for you though: in forms.py, there is a 'title' field that allows you to set a gallery title on uploading a zip. It would make sense for this field to also see its size increased. Could you make this change please?

Sorry for the delay. The title in the GalleryUpload form is altered now altered and a migrations is added as well.

Thanks for the PR - I'm merging it into master.


Database hits when caching

While running the same query in a loop, within the same database context, I get cached values from the first instance of query materialization which is as expected.  However, I was running an Sql Profiler at the same time and observed that the query is actually executed every time against the sql server database. These database hits are needless excess as I proved to myself by updating affected row from outside the db context and verifying that cached data did not change.
I believe that you could save countless hits to the database for all EF users by not hitting the database after the data is cached.
Steps to reproduce

Open Sql Server Management Studio (SSMS)
Open "Create database script.sql" part and execute it in SSMS
Click on Tools-->Sql Profiler, connect to 'localhost' db server and Run the trace
Run the program attached to this ticket (ExcessDbHits)
Stop the Sql Profiler and examine its trace to confirm that database query was executed 5 times even though EF returns a cached value.

ExcessDbHits.zip
Further technical details
EF Core version:
Sql Server: 2012
Operating system: Windows 10
IDE: Visual Studio 2015

This seems to be a duplicate of #1948.

@ebudimlic also, BTW, I think one possible reason we don't get this request more often is because we already have the Find which you can use as a replacement for simple queries for a single entity by key, and which already looks first in the cache.

Duplicate of #1948


Feature Grid Unit Testing

Adds unit testing to the feature-grid-desktop block

@toka1300 can you close this PR if it's not ready to merge?

@toka1300 ah ok, fair 👍


Drop v1alpha4 support on main branch

Based on https://cluster-api.sigs.k8s.io/contributing?highlight=support#support-and-guarantees, CAPI is planning to stop supporting API version v1alpha3 (CAPM3 v1alpha4 compatible) from 2022-02-23.
The notice to drop the CAPM3 v1a4 support was given during the metal3 community meeting on 2022-01-26, this is the issue created for visibility and get to know if there are any objections to these changes.
Note: v1a4 API types will be removed only from the main branch, and people using it can always use one of the releases from the release branch release-0.4.

/triage accepted
/assign

/kind feature


bump the build number

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12388601105. Examine the logs at this URL for more detail.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/recipe.yaml:

ℹ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12408172117. Examine the logs at this URL for more detail.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.


CGI-Stereo pretrained_model

Hello author, excuse me. May I ask the pre-trained model by CGI-Stereo?

Hello author, excuse me. May I ask the pre-trained model by CGI-Stereo?


Unit tests

It's that time of the year.
All of our pure functions should have solid unit test coverage.

Baring a few functions that are "pure" effects, some trampolines and the cli.py and x.py modules, we're now sitting at 100% coverage. 🎉


X25519 implementation complicates curve order preference for consuming applications

X25519 is currently implemented separately from the main ECC / ECDH functionality. I am told this is due to the fact that X25519 does not have parameters. Unfortunately the existing implementation is causing problems with consuming applications' ability to allow user-selectable curve order preferences, such as in Apache and nginx.
I believe the current behaviour in OpenSSL is to select X25519 by default when an ECDH cipher suite is selected. This is of course preferable, as P-curves have rigidity concerns (although it is worth noting that the perceived validity of this concern is orthogonal to this issue). In practice, however, it appears that consuming applications currently have to provide their own glue-code in order to support X25519 as part of a configurable curve order preference list.
This is best demonstrated in nginx. If left in a default state, X25519 is prioritised and P-curves (P-256 and P-384, iirc) are accepted as a fallback. However, if you specify the ssl_ecdh_curve configuration directive, such as in the case of wanting to disable P-256 entirely, X25519 cannot be selected at all as it is not part of the generic ECDH implementation. This means that users are stuck with either the default configuration provided by OpenSSL, or a custom curve order with no X25519 support.
In Apache it appears that the default behaviour is different, at least from experimentation (I haven't reviewed the source). By default Apache sets P-256 and P-384 as supported. Again, using the SSLOpenSSLConfCmd ECDHParameters configuration directive does not allow X25519 to be selected. This implies that Apache has no X25519 support at all at the moment. This is arguably an Apache bug rather than a flaw in OpenSSL, but I would assume that it stems from the Apache team explicitly selecting a known curve preference order rather than relying upon the OpenSSL defaults, which is arguably a reasonable security decision for them to have made, albeit with unexpected side-effects.
My concern is that the current implementation forces consuming applications to include parsing and glue code for ECDH curve order lists, if the application wishes to expose this as a user preference via the accepted string-based format without (unexpectedly) losing X25519 support. While a competent developer may implement such functionality without problems, it is generally poor practice (at least in my opinion) to defer such an edge-case to the consuming application's developer, particularly when there is likely to be an expectation that all curve selection would be possible by the generic approach.
I would suggest one of two alternative approaches:

Make X25519 available as part of the regular ECDH APIs internally, but return an error or warning if non-null parameters are passed, thus making the distinction largely transparent to the consuming application.
Integrate X25519 support within function which accepts the colon-separated curve order preference string, thus alleviating the need for such code in the consuming application, but otherwise leave the ECDH APIs alone.

Should both of these approaches be deemed inappropriate, I would be interested to hear any alternative approach which results in X25519 being transparently supported as part of curve order preferences. I also admit that I am not intimately familiar with OpenSSL internals, so my apologies for any inaccuracies here.
Tagging @richsalz as I have discussed this with him to some extent on Twitter.

Inspecting the source, your option 2 appears to already be the case. Are you sure you are spelling it right? NGINX's ssl_ecdh_curve hook is implemented using the SSL_CTX_set1_curves_list (available in all versions X25519 is available) which does not depend on the EC_KEY machinery. Note how, if EC_curve_nist2nid can't find a NIST curve, it just looks up the NID by name. X25519 has a NID named "X25519".
https://github.com/openssl/openssl/blob/master/ssl/t1_lib.c#L429

I was going to say the same thing. AFAIK option 2 is already the case?

I don't have nginx to hand to re-verify, but Apache 2.4.27 with OpenSSL 1.1.0f uses P-256 by default:
# openssl version
OpenSSL 1.1.0f  25 May 2017

# openssl s_client -debug -connect <IP_ADDRESS>:443
[snip]
---
No client certificate CA names sent
Peer signing digest: SHA512
Server Temp Key: ECDH, P-256, 256 bits
---
[snip]

Specifying SSLOpenSSLConfCmd ECDHParameters X25519 fails:
[ssl:emerg] [pid 4016:tid 396] AH02407: "SSLOpenSSLConfCmd ECDHParameters X25519" failed for servertwo.tld:443
[ssl:emerg] [pid 4016:tid 396] AH02312: Fatal error initialising mod_ssl, exiting.

As does SSLOpenSSLConfCmd Curves X25519:
[ssl:emerg] [pid 4316:tid 412] AH02407: "SSLOpenSSLConfCmd Curves X25519" failed for servertwo.tld:443
[ssl:emerg] [pid 4316:tid 412] AH02312: Fatal error initialising mod_ssl, exiting.

Whereas both cases work just fine when P-256 is given as a curve name.
It appears that I may be wrong about nginx's behaviour, although the configuration has caused some confusion to other users regardless (see #2188).

As folks said on that bug, #2188 has nothing to do with whether X25519 is an EC_KEY and instead is because TLS 1.2 uses the same curve list for ECDSA as ECDHE. This means you cannot use an ECDSA certificate without allowing the corresponding curve. Indeed that it got as far as failing the handshake like that suggests setting X25519 in NGINX does work.
The ECDHParameters string command indeed wraps the legacy API and does not work with X25519. That can probably be fixed but since it only supports one curve, you would run into the same issue as #2188 for an ECDSA certificate.
https://github.com/openssl/openssl/blob/master/ssl/ssl_conf.c#L222
The Curves command should call the same function as NGINX (which, per #2188 does accept X25519). Are you sure your Apache is actually running against 1.1.0f? That it has a default of P-256 makes me think you linked against a system copy of 1.0.2 or so.

At least in the master branch, using "-groups P-256" or "-groups X25519" works for me for both client and server and seems to do what is expected.
But the -groups option was added in the master branch, not in the 1.1.0 stable versions.
And we actually seem to test for X25519 in the 1.1.0 stable branch's test suite, so I assume it just works there too.
(Curves is an alias for Groups in master, Curves should work in 1.1.0, both should work in master.)

davidben said:

Are you sure your Apache is actually running against 1.1.0f? That it has a default of P-256 makes me think you linked against a system copy of 1.0.2 or so.

D'oh! I was testing against a Windows version of Apache which had the new OpenSSL libraries (libssl, libcrypto) but also the old 1.0.2 libeay32/ssleay32 libraries, and for some reason it was using those old libraries despite having the latest mod_ssl version.
Wiping the directory and loading a brand new VC15 build in with only the libssl/libcrypto libraries resolved the issue. X25519 is now used by default. Apologies for all the confusion and huge thanks for giving me the nudge in the right direction!

The main reason X25519 is implemented separately is differences between the algorithm and other curves. The ASN.1 format for keys has a new "top level" algorithm OID for it instead of using the ecPublicKey with a separate curve OID.


⚠ Redacted has degraded performance

In 71f8efd, Redacted ($RED) experienced degraded performance:

HTTP code: 200
Response time: 5721 ms

Resolved: Redacted performance has improved in c337e21.


feat(NOTIFY-853): add account syncing feature

Explanation

References

Changelog

@metamask/package-a

: Your change here
: Your change here

@metamask/package-b

: Your change here
: Your change here

Checklist

[ ] I've updated the test suite for new or updated code as appropriate
[ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate

@metamaskbot publish-preview

@metamaskbot publish-preview


Implement Web Sockets for Check out Endpoints

Change check out endpoints to use WebSockets for realtime simultaneous broadcast to all clients . Eliminate constant spamming of the APIs to reduce the number of calls that the client is making to the APIs

To be addressed after the Refactor

Not high priority. check in through out the PI


Added code for Dijkstra's Algorithm

LGTM! Take input from the user for the graph rather than declaring it statically, then I'll merge it
Also reference the issues you are solving by adding them in the description of the PR

@ekdnam  I have re-written the code to get user input for the graph.

Dijkstra has been added. So, instead, I am giving a hacktoberfest label to your PR. Hopefully it will be helpful


Wrong file name when downloading video

Auto-Editor version 21w11a from pip
What went wrong
Passing an URL to a video downloads it to a different file than auto-editor expects. This only affects URLs of an actual video, e.g. extracting from YouTube works fine.
$ auto-editor https://github.com/WyattBlue/auto-editor/raw/master/example.mp4
Falling back on generic information extractor. ETA 10:38
URL could be a direct video link, returning it as such.
https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4
Warning! Couldn't automatically detect audio bitrate.
Error! getFrameRate had an invalid output: https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4: No such file or directory

youtube-dl saves video to https-github-com-WyattBlue-auto-editor-raw-master-example-mp4 (without extension), auto-editor seems to expect it at https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4 (with .mp4 extension)
Does the example video work? (if applicable)
When downloading it manually and passing the downloaded file it works.
What does the program output when --debug or --show_ffmpeg_debug is appended to your command/use case
$ auto-editor https://github.com/WyattBlue/auto-editor/raw/master/example.mp4 --debug --show_ffmpeg_debug

   - Temp Directory: /var/folders/2y/3g_5v79s1ln64ld7gx50b6v80000gp/T/tmpdhjy1tzk
Falling back on generic information extractor. ETA 10:40
URL could be a direct video link, returning it as such.
https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4
   - Speeds: [99999, 1.0]
   - INPUT_FILE: https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4
   - newOutput: https-github-com-WyattBlue-auto-editor-raw-master-example-mp4_ALTERED.mp4
['/path/to/venv/lib/python3.9/site-packages/auto_editor/mac-ffmpeg/bin/ffprobe', '-v', 'error', '-select_streams', 'a:0', '-show_entries', 'stream=sample_rate', '-of', 'compact=p=0:nk=1', 'https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4']
https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4: No such file or directory

   - sampleRate: https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4: No such file or directory
['/path/to/venv/lib/python3.9/site-packages/auto_editor/mac-ffmpeg/bin/ffprobe', '-v', 'error', '-select_streams', 'a:0', '-show_entries', 'stream=bit_rate', '-of', 'compact=p=0:nk=1', 'https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4']
https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4: No such file or directory

Warning! Couldn't automatically detect audio bitrate.
   - audioBitrate: None
['/path/to/venv/lib/python3.9/site-packages/auto_editor/mac-ffmpeg/bin/ffprobe', '-v', 'error', '-select_streams', 'v', '-show_entries', 'stream=r_frame_rate', '-of', 'compact=p=0:nk=1', 'https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4']
https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4: No such file or directory

Error! getFrameRate had an invalid output: https-github-com-WyattBlue-auto-editor-raw-master-example-mp4.mp4: No such file or directory
   - Removed Temp Directory.

What's your platform? (if applicable)
Python Version: 3.9.2 64-bit
Platform: Darwin 20.2.0
Config File path: /path/to/venv/lib/python3.9/site-packages/auto_editor/config.txt
FFmpeg path: /path/to/venv/lib/python3.9/site-packages/auto_editor/mac-ffmpeg/bin/ffmpeg
FFmpeg version: 4.3
Auto-Editor version 21w11a

What's your input? (if applicable)
Any URL to a video file

Thank's for the report, I was able to confirm this behavior and fix in commit c7c08a6ea7b724c87a170210aa2f749c656d2b39


app-backend: serve templated index.html from memory

Hey, I just made a Pull Request!
This switches the templating of index.html in the app backend to happen in memory rather than being written to the filesystem. This means you no longer need to use the app.disableConfigInjection flag when using a read-only filesystem, allowing for config injection there too.
This also removes the double config injection that was present for a few releases as we move from injecting config into the static config to instead have it in index.html.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@freben yeah same. I remember it being tricky last time I looked at it, but I think that was before switching to templating `index.html


new tab operation should be focus the browser window to the new tab together

Is your feature request related to a problem? Please describe.
When typing new tab shortcut, vimari just trriger a new tab, but it doesn't move to the tab, it's not convenient to do the next operation.
Describe the solution you'd like
type new tab and also jump into it, and default focus on the address bar, so we don't need to click the bar or use cmd + l.
Just act like Vimium on Chrome.

I would like this feature as well. I can set default search engine to Google or DuckDuckGo and search directly from the address bar without waiting for the web page to load.

Please add this feature. Opening a tab with the URL bar already selected is quicker than waiting for a search page to load.

Found a partial fix for this.  If you add this to the config file:
  "openTabUrl": "favorites://",
Instead of the blank default, a new tab gets focused.  But it still won't go to the URL bar by default.


Handle dependent range without further useEffects

Suggestion how to avoid the useRef and useLayoutEffect and keep things simple
The main things I did were

pass vizConfig.dependentAxisRange ?? defaultDependentAxisRange to both the plot component and plot controls - this means we can reset vizConfig.dependentAxisRange to undefined which makes things cleaner.
add a new flag to the onChangeHandlerFactory to reset the dependentAxisRange for valueSpec and showMissingness handlers (onVariableChange also resets the dependent axis range, which I think is a good idea)

I also updated the thumbnail dependencies.

@bobular I am checking and testing this now and it looks good so far 👍 Will test intensively and if it works fine, then I will update other Vizs.

Looks great, but merging this into the parent branch, where I will complete the review :-)
I would like all the new code in the same PR.


One-hot encoded input?

I'm looking through the code, and I'm not seeing the token IDs being converted to one-hot encoded vectors. Is the input to the language model with autoregressive wrapper the token IDs?

@matthew-jurewicz Hi Matthew! Yup, you just to pass the token ids and make sure you instantiate the language model with the num_tokens set to the maximum of the ids! The token embedding are fetched from the embedding table here https://github.com/lucidrains/routing-transformer/blob/master/routing_transformer/routing_transformer.py#L523

Excellent! I'm a big fan of your work!

This was an implementation of someone else's research https://openreview.net/forum?id=B1gjs6EtDr Hope you find it useful!

What I mean is, as far as I know, no one's written the code for a fully-functional sparse transformer, much less this.


Odd problems with RS machines & their state

Issue description:
Whenever I leave the immediate area of RS, they seem to shut off the entire network.
All the machines seem to get this dark color and/or full metal casing.... view picture to see.
What happens:
Leaving area or dimension puts the RS machines / system into an off state with a GUI that
makes the machines fully encapsulated into a metal frame... view picture.
What you expected to happen:
I expect the RS system to be self sustaining as a chunkloader for any machines connected to the controller. (its a wish)
Steps to reproduce:

Leave immediate area or go into another deminsion

Return to the RS system where the controller and other RS machines are at

You will notice all machines are turned off & a metal casing is wrapped around them
view picture.
...

Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: <IP_ADDRESS>9
Refined Storage: 1.5.21

Does this issue occur on a server? [yes/no]
Not playing on server, - Its single player private.
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]
This is with the machines on before leaving area or to another dimension.
https://imgur.com/a/JXJKi
This is when I return to the RS system after being away.
IMAGE <<<-----  https://imgur.com/a/cvCuQ
These are showing the machines completely turned off, even though power is running through system.
A - https://imgur.com/a/0BzSF
B - https://imgur.com/a/GDmBO
NOTE:::::::
In order for me to place the machines back into its on state after this happens..
I have to break the controller, and place it back down again.....
Thats when the system will turn completely back on and everything works fine,
So long as I dont leave the area or go to another dimension...
Its a bit frustrating that every time I come back home, I have to get into  the habit of breaking the controller and placing it back down again to get the system working like it should.
.
PS>>
I dont know if its my game itself, or the mod, so thats why I am posting here just incase .
also, love your mod  :P
.

Erm, looking at your screenshots, looks like your chunk is corrupted during saving (direction of the blocks is reset). Any logs of when this happens (on leaving / entering chunk)?

no so far no logs.... it just happens....
:/

As long as there are no logs, there is not much I can do. :/


Clear console logs from the js files

Currently, there are a lot of console logs in the script files, which may be necessary for debugging purpose, but need not be shown to the users! I think we can clear them out from the script files in order to avoid unnecessary things being logged into the user's console, and hence, enhance the user's experience.

Yes. A great issue. Thanks for pointing it out. While you're at it, please see if there's any unused commented code that needs to be cleaned as well. Thanks.

Sure!  I will cleanup the code and send a PR👍