feat: SLES15 enablement, HAE detection

Enhancement: Adds additional steps for SLES15 enablement:

High Availability Extension detection
Package list updated to remove SLES4SAP specific package
Cluster destroy adjusted to avoid failure when corosync-qdevice was not present
Removed logd check, because it is part of cluster packages and it should not be checked before packages are installed on SLES15
Added gather facts for NIC for corosync template.

Additionally main.yml was reordered to allow variable checks before package installation.
Readme was updated to note higher Service Pack requirement for both SLES and SLES4SAP, because of detected dependency on pattern patterns-ha-ha_sles, which failed to install using package module because of samba client version mismatch.
Reason: Adding coverage for SLES15 after cluster deployment verification.
Result: Testing completed on both SLES4SAP 15 SP5 and SLES15 SP5 with HA, cluster creation and destroy are working.
Issue Tracker Tickets (Jira or BZ if any):

[citest]

[citest]


libmachine/provision/{debian,ubuntu_systemd,ubuntu_upstart}.go explicitly run installation script from https://get.docker.com

Please notice the "curl -sSL https://get.docker.com | sh" below. Is this intentional?
✔ 15:43 (jlebc@JLEBC) ~/Projects/docker-machine [master|✔] $ date
Wed Dec  9 15:43:55 MST 2015
✔ 15:43 (jlebc@JLEBC) ~/Projects/docker-machine [master|✔] $ git log -1
commit a1275f6f1117c84e6bb6fca18dca1ab70e74b4c4
Merge: c2ed9e3 75b2d5f
Author: Jean-Laurent de Morlhon<EMAIL_ADDRESS>Date:   Wed Dec 9 16:30:01 2015 +0100

    Merge pull request #2537 from Godin/patch-1

    Fix link
✔ 15:43 (jlebc@JLEBC) ~/Projects/docker-machine [master|✔] $ find . -type f -name "*.go" -exec grep -Hi 'get[.]docker[.]com' {} \;
./commands/create.go:			Value:  "https://get.docker.com",
./libmachine/host/migrate_v0_v1.go:		InstallURL: "https://get.docker.com",
./libmachine/host/migrate_v0_v1_test.go:			InstallURL: "https://get.docker.com",
./libmachine/host/migrate_v1_v2_test.go:            "InstallURL": "https://get.docker.com"
./libmachine/libmachine.go:			InstallURL:    "https://get.docker.com",
./libmachine/provision/debian.go:		// also re-run the get.docker.com script to properly setup
./libmachine/provision/debian.go:			"curl -sSL https://get.docker.com | sh",
./libmachine/provision/ubuntu_systemd.go:		// also re-run the get.docker.com script to properly setup
./libmachine/provision/ubuntu_systemd.go:			"curl -sSL https://get.docker.com | sh",
./libmachine/provision/ubuntu_upstart.go:		// also re-run the get.docker.com script to properly setup
./libmachine/provision/ubuntu_upstart.go:			"curl -sSL https://get.docker.com | sh",

It is intentional.  The script from get.docker.com is always considered the canonical way to install Docker.  In most cases it will patch your kernel to support AUFS if available, and then install Docker using the distro's package manager.
Long-term, we want to move what the script does today, into direct Go code / SSH commands within the Machine provisioners, so that reliance on this script can be removed.

@nathanleclaire that doesn't quite answer what I was trying to ask and that is because of a poor choice of words on my part.
What I was trying to point out is that these three implementations are not honoring the InstallURL from the EngineOptions attached to the provisioner that is in scope.

@dweomer I see.  It is not intentional.  Provisioners should honor --engine-install-url.  I've updated the title to reflect this and transition this to "issue report".


feat: Rdo 6 1 liner sdk examples

@John-Memphis can you resolve the conflict?

@bazen-teklehaymanot I will resolve it. I meant to make this a draft PR

@John-Memphis all checks should pass before review


Add Groundswell Destination to Segment Doc

Proposed changes
Added Segment documentation for Groundswell integration as part of the subscription approval process, before its launch.
Merge timing

ASAP once approved

Related issues (optional)

Hi @sneha-shashidhar, do you have an idea of when this destination will move to Public Beta?

Hi @markzegarelli, we're expecting to move to Public Beta by EOW or early next week.


Implement MeshBasicMaterial.wireframe

This implements mesh wireframes, as a property on MeshBasicMaterial. This checks one of the feature in #50.
Background
There are many ways that this can be done, e.g.:

Generate line geometry from the vertices and indices and render that using a Line object. I'd rather not do that.
Render as line primitive-topology (i.e. 1px lines), using some geometry-shader-like trickery in the vertex shader.
Render pretty lines with a given thickness, similar to how we render our LineMaterial, but with mesh geometry as input.
Render the mesh as you'd normally do, but discard fragments that are too far from the edge.

I think that ThreeJS uses a variant of (2) (because it mentions "Due to limitations of the [...] WebGL renderer on most platforms linewidth will always be 1 regardless of the set value."). But Three also has a nice example with a custom wireframe, that seems to do something like (4).
Considerations
This PR implements option 4, because it has several interesting advantages:

Most of the shader code for the mesh is the same (easy to maintain).
Many features of the mesh persist: Any lighting works as expected. It works with instanced meshes. Applying a texture still works. Culling works, Picking works, etc.

Some disadvantages:

Option (2) is most probably faster.
At the edges of the object, the width of the lines can be thinner, because lines never extend past the actual object. You can see this effect in the ThreeJS example I linked (this is what tipped me of how it works).

Some implementation details: the way this works is a bit similar to how we support sub-face picking, using barycentric coodinates. Except now the barycentric coordinates are expressed as a distance in logical pixels in screen-space. In the fragment shader we can then easily check when a fragment must be discarded.
Todo

[x] Implement it.
[ ] Make sure we're happy with the API.
[x] Add an example showing a lit mesh and a wireframe together.
[ ] Add an example showing a wireframe that has different materials for front and back.

Mandatory screenshots
A new example:

Interesting look when using tick lines and combined with flat shading:

Why don't you just use PolygonMode ? It should be natively supported right?

https://github.com/gfx-rs/wgpu/blob/af960b91f42585c337aae1c0f69ca805122395c5/wgpu-types/src/lib.rs#L393
It says that it's literally meant for wireframe and native only!

It's not a feature that is exposed in WebGPU / wgpu-native. There is a mentioning in wgpu-native here though.
Not sure if there's a chance that this will become part of the API. And if it would, I'm pretty sure it would be limited to 1px lines - which arguably covers most cases.
I also don't think it would matter much for performance - with the MeshBasicMaterial without using a texture, most code paths are removed, leaving a relatively short shader.

OK, makes sense! Nice work :)

LGTM!


[Bitcoin] Implement one Input while Inscribing multiple inscriptions via Pointer

Summary
Case: https://ordinals.com/inscription/6ea3bf728b34c8c01ba4703e00ad688be100599b92fbdac71e6aea6ad8355552i0

Closes #issue

Should we remove https://github.com/rooch-network/rooch/pull/1551/files#diff-c46533574b67286155c790a07ffc1cd2a55965dd572c0c4f5319af22c395fbf9L370-L374 ?

https://github.com/rooch-network/rooch/pull/1551/files#diff-c46533574b67286155c790a07ffc1cd2a55965dd572c0c4f5319af22c395fbf9L370-L374

Still looking for such a case, which can only be determined after verification of the case: when batch inscription, the receiver address exceeds 1 address, and the number of inscriptions is greater than the number of receivers.


Params standalone

Changes proposed by this PR
closes #1

[x] Introduce a standalone Params function to allow extraction of URL parameters directly from the request context.
[x] Modify the Router type's Params method to use the new standalone Params function, ensuring backward compatibility.
[x] Update documentation and tutorial to include instructions on working with the new Params function.

Notes to reviewer

The new Params function improves the flexibility of the package by allowing clients to extract parameters without requiring an instance of the Router type. This change should not affect existing functionality, as the Router type's Params method now calls the standalone Params function internally.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Unused Variable & https vs http Call

Minor detail, but the 'signature' string variable on line 55 of the AzureStorageAuthenticationHelper class never gets used (see below).

Also, you may want to notate in the documentation that users need to update the http Rest call to https if they have 'secure transfer required' enabled on their Azure storage accounts.

Created pull requests for both of these items.


No module named ask_sdk_core.skill_builder

I'm submitting a...
https://github.com/alexa-labs/alexa-skills-kit-sdk-for-python/blob/master/samples/HelloWorld/skill_using_classes/hello_world.py

Expected Behavior
Lambda test to be successful
Current Behavior
Unable to import module 'lambda_function': No module named ask_sdk_core.skill_builder
Your Environment

ASK SDK for Python used: x.x.x
Operating System and version: Centos 7

Python version info

2.7

Hey @sercanacar , can you provide exact reproduction steps for the issue? What do you mean by lambda test? Are you trying to run hello world skill on lambda?

Hi nikhiym
I'm following the documentation from:
https://alexa-skills-kit-python-sdk.readthedocs.io/en/latest/index.html#guides
"Developing Your First Skill"
I've created a lambda function with the sample hello world python file found here.
selected runtime python2.7
handler hello_world.handler
Saved
Hit test
"Unable to import module 'lambda_function': No module named ask_sdk_core.skill_builder"

Sounds to me like the "deployment package" step was skipped (ask_sdk_core wasn't included into the uploaded zip file). That step could use more official documentation (and tooling?).

Nope. Tried that, same error. Tried zip or pasting the single python file into the editor, same error. Documentation states
"AWS Lambda includes the AWS SDK for Python (Boto 3), so you don't need to include it in your deployment package. However, if you want to use a version of Boto3 other than the one included by default, you can include it in your deployment package. "

Yeah, that's super misleading. boto3 is a different package (not even sure why it's mentioned here). That's the AWS SDK. You need the ASK SDK. Drop ask-sdk-core into your project's root directory, zip that and upload. Is that what you said you tried?

Yes I've tried uploading with ask-sdk-core on the root of the directory i zipped up

Can you copy/paste your zip structure? (zipinfo lambda.zip on mac)

@sercanacar , As @timothyaaron mentioned, you need to zip either your site-packages directory in virtual_env or the target directory where you installed the libraries, along with the skill .py file, which is an AWS lambda constraint.
We wanted to leverage the AWS Lambda deployment steps from the AWS documentation. But I see this could be little misleading as well. Do you guys want to contribute to that section with more information as needed?

@sercanacar I see your above comment as Closed. So, can you get the skill to be working?

All working.  pip install ask-sdk -t . on the root directory of the skill folder where .py files are

@sercanacar , That is cool. Do you mind closing the issue, if everything is working as expected?

Thanks @sercanacar !!


Refactor CI/CD utils

📚 Documentation preview 📚: https://ridgeplot--191.org.readthedocs.build/en/191/

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

Project coverage is 85.78%. Comparing base (dd75a69) to head (4d82109).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #191   +/-   ##
=======================================
  Coverage   85.78%   85.78%
=======================================
  Files          10       10
  Lines         401      401
  Branches       70       70
=======================================
  Hits          344      344
  Misses         48       48
  Partials        9        9

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


tf.compat.v2.summary.scalar has no attribute 'summary_scope'

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes, I have a minimal test file
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version (use command below):
tf.version
'2.0.0-alpha0'
Python version:
$ python3
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
Bazel version (if compiling from source): binary installer version 0.23
GCC/Compiler version (if compiling from source):
$ gcc --version
gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
CUDA/cuDNN version: Not supported
GPU model and memory: Not supported

You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
tf.compat.v2.summary.scalar("stddev",_st,step=count,description='stddev')
is being processed as an _api.v1.summary
Describe the expected behavior
tf.compat.v2.summary.scalar("stddev",_st,step=count,description='stddev')
is processed as an _api.v2.summary
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
tf_sdata = tf.convert_to_tensor(sdata,dtype=tf.float32,name="tf_sdata")
tfdata_stddev = tf.data.Dataset.from_tensor_slices(tf_sdata[:,0])

tfstddev_iter = tfdata_stddev.__iter__()

stats_writer = tf.compat.v2.summary.create_file_writer(logs_path,max_queue=10,flush_millis=120000,
        filename_suffix='.stats',name='stats_writer')

count = 1
for _st in tfstddev_iter:
    tf.compat.v2.summary.scalar("stddev",_st,step=count,description='stddev')
    count += 1

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Traceback (most recent call last):
File "./tf2summary_bug.py", line 71, in
tf.compat.v2.summary.scalar("stddev",_st,step=count,description='stddev')
File "/usr/lib/python3/dist-packages/tensorboard/plugins/scalar/summary_v2.py", line 55, in scalar
with tf.summary.summary_scope(
AttributeError: module 'tensorflow._api.v1.summary' has no attribute 'summary_scope'

I think you need to mark the stats_writer as default. Either by calling stats_writer.set_as_default() (do not directly add this call to the creation of the SummaryFileWriter [#25976]) or by setting up the summary scope like this:
with stats_writer.as_default():
    count = 1
    for _st in tfstddev_iter:
        tf.compat.v2.summary.scalar("stddev",_st,step=count,description='stddev')
        count += 1

meyerjo, thank you for your comment.
I tried the context: with stats_writer.as_default():
This produced the same Traceback:
Traceback (most recent call last):
File "./tf2summary_bug.py", line 72, in
tf.compat.v2.summary.scalar("stddev",_st,step=count,description='stddev')
File "/usr/lib/python3/dist-packages/tensorboard/plugins/scalar/summary_v2.py", line 55, in scalar
with tf.summary.summary_scope(
AttributeError: module 'tensorflow._api.v1.summary' has no attribute 'summary_scope'
I do not see why this would need a custom summary scope. The problem seems to be the code is executing in the summary_v2.py code as expected and encountering a v1.summary object that is not expected. I could be wrong. Just thinking out loud.


⚠ PrivateHD has degraded performance

In 9eb826f, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 5697 ms

Resolved: PrivateHD performance has improved in b0db04c.


Output verbosity settings

Type of Issue

[ ] Bug Report
[x ] Feature Request

Description
A way to increase verbosity of output errors
How To Reproduce
I'm currently converting a large library I've previously completely managed all the inlining/buildscripts/etc. I am running into a problem after applying ng-package.json and the necessary updates, an error (below) that is almost undoubtedly something I am doing wrong... but the error has not much to do with my code. Infact the error appears to point at gulp-inline-ng2-template, which I'm not sure if your library calls, or if its remnants of my old build process which shouldn't be consumed.
undefined:1
({styleUrls: string[]})
                    ^

SyntaxError: Unexpected token ]
    at replaceFrag (C:\Users\wweems\Source\Repos\IQMS.FrontEnd\node_modules\gulp-inline-ng2-template\parser.js:188:32)
    at C:\Users\wweems\Source\Repos\IQMS.FrontEnd\node_modules\async\dist\async.js:3853:24
    at replenish (C:\Users\wweems\Source\Repos\IQMS.FrontEnd\node_modules\async\dist\async.js:946:17)
    at iterateeCallback (C:\Users\wweems\Source\Repos\IQMS.FrontEnd\node_modules\async\dist\async.js:931:17)
    at C:\Users\wweems\Source\Repos\IQMS.FrontEnd\node_modules\async\dist\async.js:906:16
    at C:\Users\wweems\Source\Repos\IQMS.FrontEnd\node_modules\async\dist\async.js:3858:13

Expected Behaviour
please describe what behaviour or result you expected
I suppose just being able to better see what the actual problems were
Version Information
ng-packagr: v1.2.0
@angular: v4.x.y

I have no idea if this is related or not, but seems like ng-packagr spits out information when doing a build:lib like in the example repo, from the parent testing apps package.config rather than the inner package.config in the my-lib folder.

for those of you curious
set DEBUG=* & npm start build:lib

did the trick for me

Yes, the environment variable sets the logging output to debug


fix: Fix a typo

Fix a very little typo.

@muditchoudhary before this can be merged, please follow the instructions in https://training.plone.org/contributing/. Thank youi!

@muditchoudhary before this can be merged, please follow the instructions in https://training.plone.org/contributing/. Thank youi!

I have read that. I think I misunderstood this as optional:

In every pull request or commit message, include the following statement.

@muditchoudhary Plone cannot publish your contribution without your express written consent using one of the two options. If you plan on making more contributions, then the Plone Contributor Agreement would be better, but it takes a few days for volunteers to process. You could do both options, too, allowing us to merge this now and your future contributions without getting nagged by the bot.

@muditchoudhary Plone cannot publish your contribution without your express written consent using one of the two options. If you plan on making more contributions, then the Plone Contributor Agreement would be better, but it takes a few days for volunteers to process. You could do both options, too, allowing us to merge this now and your future contributions without getting nagged by the bot.

@muditchoudhary Plone cannot publish your contribution without your express written consent using one of the two options. If you plan on making more contributions, then the Plone Contributor Agreement would be better, but it takes a few days for volunteers to process. You could do both options, too, allowing us to merge this now and your future contributions without getting nagged by the bot.

Yes, I have read in the docs. I have already signed the agreement and it did get processed by the volunteer.

Thank you! Merging.


Add kubevirt provider

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #418
Special notes for your reviewer:
TODOs:

[x] Fix migrateUID
[x] Samples
[x] Docs

Add experimental support for a [Kubevirt](https://kubevirt.io/) provider

/test pull-machine-controller-e2e

Great PR!
But the documentation needs to state that we support KubeVirt (Except with CoreOS)

@mrIncompetent All comments addressed, all tests green, PTAL

/lgtm
/approve

/lgtm


Can I represent the fetched onclick data in tabular format ?

Hello,
Like given in the mps_prepop example I was able to fetch the data on click event and data was displayed in an alert box. So similar to that is there any way that I can display the given data in a proper tabular format.
Thank you

You can do anything you want with the data, but this library doesn't offer
functionality specifically for this, you'll have to build it yourself :)
On Fri, Oct 13, 2017 at 09:06 Siddhant Mahajani<EMAIL_ADDRESS>wrote:

Hello,
Like given in the mps_prepop example I was able to fetch the data on click
event and data was displayed in an alert box. So similar to that is there
any way that I can display the given data in a proper tabular format.
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nicolaskruchten/pivottable/issues/811, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAMbAxP3l2zmTvLSm2gSYnIwetkrEbRWks5sr1_0gaJpZM4P4dP0
.

Okay Cool! Thanks

Yes you can do this by adding  etc element into the sting and use it in alert.
Inspired by your idea, this is what I am doing now. I combine it with modal to make it looks more nice and apply bootstrap etc :-)

So use the  in the string and display the string? Correct?

@hkbeer How do you actually fire the <table> command in the alert box? I mean what is the actual syntax and how do you parse it?

When you say fire do you mean going to server side to get data from db ? I am not doing this as the pivot.js already getting what I need for my case (not sure if it is your case). I go straight to jquery dialog or js modal so I did not try html in alert but I saw it is accepting things like "\n" so I guess it may be able to read table tags.
If you indeed need to fire server side code and get data again on click, you may need to run querystring etc and cause page load. I already have done so in testing and may apply in future. But, all these are doable it seems...

@hkbeer no no not from the server side. The data is in an array.

So I just need to display that data in a tabular format.

The following is a quick code I made for you as an illustration

As Nicolas said it is possible to do it ourself outside of pivot.js.
Since this is not the issue of pivot.js pls close this post


Tutorial adding command

Submission: Do your changes in a branch named tutorial-adding-command, push to your fork, and create a PR from your fork to your team's repo. You may close the PR soon after.

Life is hard.

yea ikr


nvim: xcb_io.c :269 : poll_for_event:  « !xcb_xlib_threads_sequence_lost » assert failed

I have some issues with nvim 0.7.0 and neoclip:
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
nvim: xcb_io.c :269 : poll_for_event:  l'assertion « !xcb_xlib_threads_sequence_lost » a échoué.
277661 IOT instruction (core dumped)  nvim .

I am on Fedora 36.
@matveyt Do you need more information?

$ dnf list --installed | grep "xcb"
libX11-xcb.x86_64                                 <IP_ADDRESS>-2.fc36                      @fedora
libxcb.x86_64                                     1.13.1-9.fc36                       @fedora
libxcb-devel.x86_64                               1.13.1-9.fc36                       @fedora
xcb-util.x86_64                                   0.4.0-19.fc36                       @fedora
xcb-util-image.x86_64                             0.4.0-19.fc36                       @fedora
xcb-util-keysyms.x86_64                           0.4.0-17.fc36                       @fedora
xcb-util-renderutil.x86_64                        0.3.9-20.fc36                       @fedora
xcb-util-wm.x86_64                                0.4.1-22.fc36                       @fedora

provider: health#provider#check
========================================================================
## Clipboard (optional)
  - OK: Clipboard tool found: neoclip/X11

I run on Gnome 42 with Wayland.

Okay, so calling XInitThreads is required then. At least, on xcb backend that I never checked.
I've pushed the fix onto HEAD. Let's see if it works.

I run on Gnome 42 with Wayland.

Gnome/Mutter deliberately not supports wlr_data_control protocol. Therefore, neoclip/Wayland can't do anything. I mentioned this at :h neoclip-issues. But it has XWayland compat. layer, so neoclip/X11 should work okay after the problem with XInitThreads is gone.

No error since 1h, I think the bug is fixed.
Thanks :+1:

@stephane-klein Good. Thanks for testing.


Handle JSON tags properly on tsbs_load_timescaledb

Previously the returned values from insert tags assumed the data
was stored in a table and tried to use the first column as the key
to the client-side index. However, for JSON this first column was
a byte array representing the tags JSON, which created a mapping
with the wrong keys. Now, the JSON is unmarshalled first and then
the value corresponding to the first tags column is used as a key.
Updated version of #48, which fixes #47.

Codecov Report

Merging #55 into master will decrease coverage by 0.11%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #55      +/-   ##
==========================================
- Coverage    54.3%   54.18%   -0.12%
==========================================
  Files          66       66
  Lines        3193     3200       +7
==========================================
  Hits         1734     1734
- Misses       1447     1454       +7
  Partials       12       12

Impacted Files
Coverage Δ

cmd/tsbs_load_timescaledb/process.go
25.8% <0%> (-1.23%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 720a647...98fd523. Read the comment docs.


Improve performance of cast methods (Bridge.as, Bridge.is, Bridge.cast)

http://deck.net/469d9f0d5ebd57b95f12f40cfb252081
http://deck.net/92d3a2d79a4c53ea9c8d93152a791cd9

Related with https://github.com/bridgedotnet/Bridge/issues/1995


Use datacenter field for the IpInfo signal instead of the wrong dataCenter, deprecate IPLocation

:tada: This PR is included in version 4.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fixed select error

Fixed #345

I believe we fixed this at some point. Thanks for pointing this out to us!


Error when opening file with space(s) in name

When opening a file with a space in the name (e.g. "This File Has Spaces.txt"), the following error displays:

The file still opens, but it would be nice not having this annoying error show up (which, as you can see, requires pressing the enter key to continue).
My Vim Info
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 27 2016 22:06:17)
MS-Windows 64-bit GUI version with OLE support
Included patches: 1-1965
Compiled by hp@HP-PC

There was a similar problem a few months ago, so I have to ask: are you using the latest version of the plugin?
I can't reproduce it on OSX, but it might be related to Windows, so I'll get a Win 10 tablet later today and check again.

Okay, I can reproduce it with Vim 8.0 in Git Bash.

It should work now!

Great, works for me now. Thanks for the speedy resolution!

Thank you for bringing it up!


Exclude javax.el and jakarta.el-api, using glassfish jakarta.el instead

Fixes duplicate classes between the 3 jars
Fixes #2739
Problem:
jakarta jars are replacing javax jars, so should depend on that instead of javax.  Furthermore, the glassfish jakarta.el implementation jar includes all the classes from the jakarta.el-api jar (see https://github.com/eclipse-ee4j/el-ri/issues/32), so should only depend on the implementation jar.
Solution:
depend on org.glassfish:jakarta-el, and exclude the other 2 jars

For reference, more information is at https://eclipse-foundation.blog/2018/02/26/and-the-name-is/

Does jakarta.el-api still need to be excluded?
This is not correct in DW 4.0.1 the glassfish jakarta.el implementation jar includes all the classes from the jakarta.el-api
And it does not get included as a transitive dependency in some scenarios with DW 4.0.1


Setup Guide on Vue Components and Other Tips!

This is a guide on Vue Components. I liked working with Vue, but I had quite a bit of trouble at the start due to some confusing documentation and deprecated code that I was working with. I hope to give users all they need to know about Vue components, as well as other tips that will help them learn more.

Thanks for the tips, I guess I did go a bit overboard. And look at that, I also missed adding a link to the file in the Tech_Stacks.md file as well! Lemme just fix that.

Alright, I did what you suggested and expanded on the solution for that tip at the end, skipped the async stuff, and added in more example code! Last question though, how does it all look? I'm concerned with the ordering of the HTML and Script sections, since it sort of requires the reader shuttling back and forth between them to gain the full picture. Have I made each section standalone enough, or should I cut down or expand upon either?

Alright, I did what you suggested and expanded on the solution for that tip at the end, skipped the async stuff, and added in more example code! Last question though, how does it all look? I'm concerned with the ordering of the HTML and Script sections, since it sort of requires the reader shuttling back and forth between them to gain the full picture. Have I made each section standalone enough, or should I cut down or expand upon either?

Yay, good job integrating my feedback.
I think the ordering of the HTML and script sections is okay. I mean, there are gonna be tradeoffs - do we make people remember more stuff, or do we keep stuff isolated? And I think keeping stuff isolated to only what's relevant makes the most sense. (It also doesn't require that much shuttling).
I think sections are sufficiently standalone and don't really require additional edits. I like it!
I can't comment on how it looks because you haven't made it an .md file. For it to display properly, please do that lol.

Oops, thanks, now its an md file!

Thanks, time to merge!


fix(@schematics/angular): add migration to update web-animations-js…

… polyfill
Previous versions rely on this which breaks differential loading since it's undefined when using script tags with type module.

Blocked on https://github.com/web-animations/web-animations-js/pull/208

unblocked this by publishing a release with Minko's fix to the angular fork of the project.


[Remote File][Mac] The save, rename and show in finder options are still enabled for remote file in mac.

Description
The save, rename and show in finder options are still enabled for remote file in mac.
Steps to Reproduce

Launch brackets 1.13.
Press ctrl+shift+O for win and cmd+shift+O for mac.
Quick open modal bar will open.
Enter a network url that supports http or https. Example: https://www.google.com
The code for the page is displayed in brackets and file is visible in working files in file tree.
In the file tree, right click on file.
Context menu will appear.
Save, rename, show in finder options are still enable for remote file.
Also, the option to save the file is enabled in file menu.

Expected behavior: The save, rename and show in finder options should not be enabled for remote file.
Actual behavior: The save, rename and show in finder options are still enabled for remote file in mac.
Versions
Mac 10.12
Release 1.13 build 1.13.0-17679

@boopeshmahendran Can you please verify the issue?

Yeah, sure. Raised a PR with the fix.


Include LogGeneratedClassesTest on openj9 for jdk11+

Depends-on: https://github.com/eclipse-openj9/openj9/pull/18968
Issue: https://github.com/eclipse-openj9/openj9/issues/18556
Signed-off-by: Amarpreet Singh<EMAIL_ADDRESS>

@tajila requesting your review.


Update package.json version

Update package version so as to create a new npm release.

@googlebot I signed it!

:white_check_mark: Build karma 2834 completed (commit https://github.com/karma-runner/karma/commit/0e4cd9c960 by @jpavlic)

See #3606


Method documentation not working

I have been having an issue where none of the method xml comments appear. When I look at the raw format, those areas are blank. However all of the model information appears!
The api has its models and methods split into separate projects. I am using two xml files to build the documentation (one for models and one for methods). When tested with just one xml file at a time, only the model documentation works.
Am I missing something with the method documentation?
This is method documentation:
///
/// Lots of somethings going on here
///
///  Model Something
///  Invalid stuff
[ActionName("Something")]
public SomeResponse GetSomething([FromUri] SomeRequest request)
And this is a property documentation which appears:
///
/// The list of somethings used to create something.
///
[Name("Something")]
public List Somethings { get; set; }

Not sure if this helps, but I found I needed to add all of the XML documentation files individually. With one of the more recent updates the docs stopped using ApiExplorer and switched to manual inclusion.
var binDirectory = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, AppDomain.CurrentDomain.RelativeSearchPath);
var xmlDocs = Directory.GetFiles(binDirectory, "*.xml", SearchOption.AllDirectories)
SwaggerSpecConfig.Customize(c =>
{
  foreach (var path in xmlDocs)
  {
    c.IncludeXmlComments(path);
  }
});

@tillig is correct - Swashbuckle needs to be told about all XML files that contain relevant comments. Closing as this should solve the issue


First time connects normally, second time client connects but not receiving events

Hello, I'm having a problem with laravel-websockets, don't know if it's the server or the client, but here it goes:
I'm using an ionic capacitor mobile application with laravel-echo and pusher, when I first connect with the socket, everything works great, but in case of a disconnection or if I close the app and open again, It simply does not connect, the issue is even strange than that in the client side it says connect, and it receives ping and pong events and even has an socket id, but in the dashboard does not appear that the client has connected and if I try to send an event from the dashboard or Laravel application it does not work, It works in the following pattern: the first time it connects in a right way receives all events, after it connects the wrong way it says in the client that is connected, but it does not receives any event.
The second time connection can be anything, a disconnect, if I close the app from the background, anything, even with airplane mode.

This is already the second time I tried to connect, as you can see It connects the first time in a right way, than the second time does not show at the dashboard, as you can see I sent an event but it does not receives in the client.
This is the websocket inspect page for this second connect, as you can see it receives ping pong events, it does show that subscribed but it does not receives events:

Now with another disconnect and connect, as you can see it works flawlessly, I don't know why:

Client screenshot receiving the event (when connected the right way):

This is my pusher config from laravel, in the server, I can reproduce this in two differente apps, using the same server:
<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Default Broadcaster
    |--------------------------------------------------------------------------
    |
    | This option controls the default broadcaster that will be used by the
    | framework when an event needs to be broadcast. You may set this to
    | any of the connections defined in the "connections" array below.
    |
    | Supported: "pusher", "redis", "log", "null"
    |
    */

    'default' => env('BROADCAST_DRIVER', 'pusher'),

    /*
    |--------------------------------------------------------------------------
    | Broadcast Connections
    |--------------------------------------------------------------------------
    |
    | Here you may define all of the broadcast connections that will be used
    | to broadcast events to other systems or over websockets. Samples of
    | each available type of connection are provided     inside this array.
    |
    */

    'connections' => [

        'pusher' => [
            'driver' => 'pusher',
            'key' => env('PUSHER_APP_KEY'), // Key
            'secret' => env('PUSHER_APP_SECRET'), // Secret
            'app_id' => env('PUSHER_APP_ID'), // An app ID
            'options' => [
                'cluster' => env('PUSHER_APP_CLUSTER'),// Here I put mt1
                'host' => 'websockets',
                'port' => 6001,
                'scheme' => 'http',
            ],
        ],

        'redis' => [
            'driver' => 'redis',
            'connection' => 'default',
        ],

        'log' => [
            'driver' => 'log',
        ],

        'null' => [
            'driver' => 'null',
        ],
    ],
];

If anyone has any guesses what I'm doing wrong, It would be really thankful. Thanks a lot for the team of laravel-websockets It is a really great job.

Do you have stale connections being closed when you terminate the websocket server?
You could test the redis backend and see if the problem is fixed there, the local Channelmanager seems to have a issue


Fix utf-8 error on py 2.7

On our pre-production environment we just now got an error related to unicode encoding in the to_global_id code. I fixed it and added a test that ensures that behaviour works.
As a reference, this is the error one would see otherwise:
  File "/home/app/apps/killik_ops_dashboard.pex/third_party/python/graphql_relay/node/node.py", line 53, in to_global_id
    return base64(':'.join([type, str(id)]))
UnicodeEncodeError: 'ascii' codec can't encode character u'\u06ed' in position 39: ordinal not in range(128)

Coverage increased (+0.007%) to 99.623% when pulling 71fe34360d08c7e1ebd4ac7b2eb56807e355e322 on Globegitter:to-global-id-unicode-error into c4c65337df2e169ae5c178dc79d25e8e234debd5 on graphql-python:master.

Coverage increased (+0.007%) to 99.623% when pulling 3b4de4f428863b8d9346bafc2a1d4538ff8f6798 on Globegitter:to-global-id-unicode-error into c4c65337df2e169ae5c178dc79d25e8e234debd5 on graphql-python:master.

Coverage increased (+0.005%) to 99.62% when pulling 7a5ded46182abc4e98889c68f1345d2bb2370556 on Globegitter:to-global-id-unicode-error into c4c65337df2e169ae5c178dc79d25e8e234debd5 on graphql-python:master.

Coverage increased (+0.006%) to 99.621% when pulling a67d78e7b8a36e35b1276b42ca0290bc462f5bf6 on Globegitter:to-global-id-unicode-error into c4c65337df2e169ae5c178dc79d25e8e234debd5 on graphql-python:master.

Coverage increased (+0.006%) to 99.621% when pulling d852e75d65560318242fb920439b648c862095a9 on Globegitter:to-global-id-unicode-error into c4c65337df2e169ae5c178dc79d25e8e234debd5 on graphql-python:master.

Coverage increased (+0.007%) to 99.623% when pulling c348879155b36c5da67d4032135a487509e70b6c on Globegitter:to-global-id-unicode-error into c4c65337df2e169ae5c178dc79d25e8e234debd5 on graphql-python:master.

This test failure was really strange - it happens to me locally also on master and seems to be a dict ordering consistency issue between py2 and py3. This sorted is not great but was the only way I managed to fix it.

Coverage increased (+0.02%) to 99.636% when pulling 148575e1edd21505367a2f0060d689e5df97fe9b on Globegitter:to-global-id-unicode-error into c4c65337df2e169ae5c178dc79d25e8e234debd5 on graphql-python:master.

Noticed I did only fix it on the lower level, @syrusakbary is now ready to merge :)


Using string constants for error messages

This PR adds string constants for errors.
Resolves #208

I believe same can be done for suggestion messages

@Sadaf-A, thank you for your input. As @RonConfigu pointed out, we're planning a comprehensive consolidation of our error messages across the entire project. I'll keep you updated on when we kickstart this initiative, and we'd welcome your contribution on the respective PR.


[SPARK-14856] Correct message in assertion for 'returning batch for wide table'

What changes were proposed in this pull request?
There was a typo in the message for second assertion in "returning batch for wide table" test
How was this patch tested?
Existing tests.

@davies
Please take a look

Test build #56802 has started for PR 12639 at commit 1323fe6.

Test build #56802 has finished for PR 12639 at commit 1323fe6.

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

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

Merged build finished. Test PASSed.

Merging this into master, thanks!


first pass at forms documentation

This adds the first pass at forms documentation with samples. There are a few other details to add, but they tend to fit more into the specific form controls themselves, which will come in another PR. The UX guidelines are marked as a WIP.

This is waiting on the other forms work to be merged so putting it in a holding pattern.


fix unconfigured cors origin

This PR solves a serious bug with serving CORS headers if no allowed origins are configured and an origin header is present in an HTTP request. If CORS headers are configured, the functionality is correct.
This PR adds two test cases in already existing debugapi test and adds the same test for the api package.

It seems that this fix worked for disabling CORS for the browser. However it only stops the browser from receiving the response, but not from making it completely. For example as a test if I open this link in Chrome, it sets the welcome message of my Bee node to empty string, never mind how cors-allowed-origins is set 😬
https://test.felfele.org/cors.html?bee=http://localhost:1635/welcome-message&method=POST&body={"welcome-message":"cors"}

@agazso Indeed, the browser does log the request as blocked because of CORS Access to fetch at 'http://localhost:1635/welcome-message' from origin 'https://test.felfele.org' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. but the request is actually made, for both POST and GET.


fix queueing of undecryptable packets

Fixes #1823.

Codecov Report

Merging #1824 into master will increase coverage by 0.11%.
The diff coverage is 94.12%.

@@            Coverage Diff             @@
##           master    #1824      +/-   ##
==========================================
+ Coverage   87.03%   87.14%   +0.11%
==========================================
  Files          95       95
  Lines        6538     6549      +11
==========================================
+ Hits         5690     5707      +17
+ Misses        603      596       -7
- Partials      245      246       +1

Impacted Files
Coverage Δ

session.go
76.79% <94.12%> (+1.15%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e4bd715...b816209. Read the comment docs.


Update signalr-concept-internals.md

@vicancy : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


feat: use own logger, not global logger

Description
Instead of calling logging.debug() (or similar) directly and causing a call to logging.basicConfig(), log via our logger only. Also stop manipulating the logging level for our module and let users manage that. Fixes #9.
Testing
poetry run tox succeeds. Also ran the example from the issue and saw no output:
import logging
import serializable

@serializable.serializable_class
class Foo:
    pass

_logger = logging.getLogger()
_logger.addHandler(logging.NullHandler())
_logger.error("foo")

some tests are failing. could you get back when they pass?

@kroeschl i think all is settled,
could you do a review and see if the feature is still as you expected it?

@kroeschl i think all is settled, could you do a review and see if the feature is still as you expected it?

This PR is now a bit more than what I intended to change. Specifically:

Converting existing warnings to log messages is IMO a design decision outside the scope of this change.
Using a logger name of serializable._logging.LOGGER is counter to Python logging convention and may confuse users. Also, a logger name including variations of "logging" is somewhat redundant.
Generally, adding a logging module is probably overkill since we're not doing anything special in it (aside from the warning stacklevel change). Users can already configure logging in their own code by using getLogger("serializable") (or whatever name).
We shouldn't set a default logging level. That should be left up to the user.

I'm inclined to roll this back to just the fix for the issue and let other rework live in a separate PR.

thanks for looking into this.

* Converting existing warnings to log messages is IMO a design decision outside the scope of this change.

From a architectural perspective, it looked obvious to move all log/output to an own logger.
Warnings were sent to global warning handler, right? So better have them to a logger that you can control downstream.
Would you agree?

* Using a logger name of `serializable._logging.LOGGER` is counter to [Python logging convention](https://docs.python.org/3/library/logging.html#logger-objects) and may confuse users.

Also, a logger name including variations of "logging" is somewhat redundant.
"Python logging convention"? If there is no PEP, then there is no convention, right?
The linked documentation uses just some example to help people chose a unique name for a logger.
And most importantly, accessing the logger is possible via public API from serializable import LOGGER, so there is no need to know the name in the first place, or is there?
What do I not see? There must be something I missed.

* Generally, adding a logging module is probably overkill since we're not doing anything special in it (aside from the warning `stacklevel` change). [...]

It was needed to prevent circular dependencies ;-)

* [...] Users can already configure logging in their own code by using `getLogger("serializable")` (or whatever name).

The mentioned module is nonpublic API. And so the name is nonpublic.
Should the name be dropped, to make this obvious?

* We shouldn't set a default logging level. That should be left up to the user.

You see that the logger is a global one, so there are possibly multiple "users".
Downstream users would need to add logHandlers in the first place, so they would do log level filtering on the handler.
Let's say library A and B both uses serializable, and A wants to listen to Errors only, B wants to listen to warnings and above, then you proposed to:
each library sets the log level on the logger. This would end with a situation that the last setter wins.
In contrast, the current solution is that the logger initiates with the lowest level it is used with by this very lib, and log handlers apply filters
like in the documentation you must have seen: https://github.com/madpah/serializable/blob/1b39831011b018fca1c3bd0454cc7788f168ebdd/docs/logging.rst?plain=1
Is there something wrong with this approach?

outdated, superseded by #47


Add support for Newslaundry

About
Adds support for www.newslaundry.com (English site).
Resolves #11

You have the wire handler in there as well, please recreate the branch to include only the relevant changes.

@RikudouSage how about the new commit I force-pushed?


cant get obsidian integration to work

it does not seem to be possible to make it write straight into my obsidian vault. am i doing something wrong?

The markdown copy-pastes directly in. That's what I do. Or you could set the download location to your Obsidian library and download directly there

The markdown copy-pastes directly in. That's what I do.

that dpes not really provide a proper workflow for me. also you'd loose all the imaged and then can just go for the other plugin.(which is what i do now)

The images actually come in for me with the paste

there should be a better way to download directly to the vault.

Someone posted a solution to this problem here: https://forum.obsidian.md/t/markdownload-markdown-web-clipper/173/161?u=danielo515

thanks will check it

For me the solution was to turn on "Allow Access to File URL" in the settings for the extension. The Right-Click context menu on websites now shows an option to "Send Tab to Obsidian"


Added a learning platform

With this PR (pull request), I had added one more learning platform named "Learn Code Online", it is free while some coerces are paid.

Rahul, thanks for the contribution. Unfortunately, I could see only tiny, tiny pieces available for free. In this section, we have platforms like Frecodecamp, The Odin Project, Khan Academy and it wouldn't be fair to put them in the same group.
Thanks!


opentimeline.io must be https

Decided to address under the umbrella of #748

Decided to address under the umbrella of #748


Enable mxunit_root to be overridden. This allows user to set the css/sty...

...les location.
Example:
#results.getResultsOutput(URL.output,'railo-ajax/mxunit')#
This can help a lot testing with war deployment under differents contexts.

I got this and tweaked it a bit. Thanks Andrea!


Add tests for UsersManager

Context
HomeDBManager lacks of direct tests, which makes hard to make rework or refactorations.
Proposed solution
Specifically here, I introduce tests which call exposed UsersManager methods directly and check their result.
Also:

I removed updateUserName which seems to me useless (updateUser does the same work)
Taking a look at the getUserByLogin methods, it appears that Typescirpt infers it returns a Promise<User|null> while in no case it may resolve a nullish value, therefore I have forced to return a Promise<User> and have changed the call sites to reflect the change.

Related issues
I make this change for then working on #870
Has this been tested?

[x] 👍 yes, I added tests to the test suite
[ ] 💭 no, because this PR is a draft and still needs work
[ ] 🙅 no, because this is not relevant here
[ ] 🙋 no, because I need help

@berhalak I think of something: my test assume that they run using Sqlite.
Several questions come to my mind:

Can running these tests with Postgresql be worth?
If so: I don't see tests running with Postgresql on the CI, I can take a look to see how hard it is to support this database.
If not: I propose to skip these tests when TYPEORM_TYPE is set to postgresql

To the first question, my answer would be no, the UsersManager uses a lot of TypeORM methods, and does not seem to make SQL query directly  (but I may be a bit biased by my lazyness).

Can running these tests with Postgresql be worth?

We run some tests with Postgresql in our internal CI, but since it is not part of the grist-core yet, and those tests are rather unit tests, I think it is fine to rely on typeorm abstraction.

I'm seeing failures in tests after UsersManager in a derived version of Grist (the one for our SaaS). Haven't looked into why yet, and may be specific to us.

Thank you @paulfitz!


Make readthedocs full-width (or at least wider)

There's no reason why you should have to scroll sideways to view the whole table in the configuration section.

Closing as the documentation had major rework and the configuration options are not in such wide tables anymore.
Current configuration docs/tables:
https://pelorus.readthedocs.io/en/latest/GettingStarted/configuration/PelorusCore/


System.ArgumentNullException thrown from ZipOutputStream when writing AES encrypted/Stored entries

Steps to reproduce
Try to use ZipOutputStream to create an AES encrypted entry whose compressionMethod is set to Stored.
e.g.
using (var memoryStream = new MemoryStream())
{
	using (var zipStream = new ZipOutputStream(memoryStream))
	{
		zipStream.IsStreamOwner = false;
		zipStream.Password = "password";  // optional. Null is the same as not setting. Required if using AES.

		ZipEntry zipEntry = new ZipEntry("stored");
		zipEntry.AESKeySize = 256;
		zipEntry.DateTime = DateTime.Now;
		zipEntry.CompressionMethod = CompressionMethod.Stored;

		zipStream.PutNextEntry(zipEntry);

		byte[] dummyData = Encoding.UTF8.GetBytes(DummyDataString);

		using (var dummyStream = new MemoryStream(dummyData))
		{
			dummyStream.CopyTo(zipStream);
		}

		zipStream.CloseEntry();
	}
}

Expected behavior
The entry should be added
Actual behavior
The call to CloseEntry() throws an ArgumentNullException.
Version of SharpZipLib
Obtained from (only keep the relevant lines)

Compiled from source, commit: 25ee644

Problem seems to be that the AESAuthCode property of the output stream isn't set up in this case, so the attempt to use it @ https://github.com/icsharpcode/SharpZipLib/blob/25ee6440f444aa326ee8f0b98e6223296f35fa6d/src/ICSharpCode.SharpZipLib/Zip/ZipOutputStream.cs#L493 throws.
See referenced PR for a possible fix.

Should be fixed by #323, so i'll close this now.


Not specifying --lang should export all the available languages

Is it possible to export all translations in all languages if --lang is not specified?

I'm not sure that's entirely suitable. For example, on iOS you need to specify a different output folder for each language you export, so I'm not sure how the command line arguments specifying the output file would look in this case? As you'd have to specify multiple output files, one for each language
(I don't even know how that works for Android, but I'm guessing it's the same, you have to store the strings.xml files for each language in a different folder?)

Also note that you can simply do a simple loop in shell in the meantime:
for lang in fr en es jp pt de
do
  poesie -t … -p … -l $lang -a …
done

Thanks for the suggestion


[Node] Hash Sum mismatch when trying to install yarn

Hello, I'm running into a problem when using the node feature on Debian bookworm on an arm64 architecture. Everything seems to be working fine (and all other features I'm using in my Dev Container install flawlessly, too) until the node feature tries to install yarn via apt-get:
18.60 Now using node v20.14.0 (npm v10.7.0)
18.65 Creating default alias: default -> 20 (-> v20.14.0 *)
18.67 => Node.js version 20 has been successfully installed
18.67 => Close and reopen your terminal to start using nvm or run the following to use it now:
18.67
18.67 export NVM_DIR="/usr/local/share/nvm"
18.67 [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
18.81 default -> 20 (-> v20.14.0 *)
18.81 Updating /etc/bash.bashrc and /etc/zsh/zshrc...
19.26 Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
19.28 Get:2 https://packages.microsoft.com/repos/microsoft-debian-bookworm-prod bookworm InRelease [3618 B]
19.30 Get:3 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
19.34 Get:4 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
19.34 Get:5 https://packages.microsoft.com/repos/microsoft-debian-bookworm-prod bookworm/main arm64 Packages [9928 B]
19.37 Get:6 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
19.38 Get:7 https://packages.microsoft.com/repos/microsoft-debian-bookworm-prod bookworm/main all Packages [342 B]
19.39 Get:8 https://dl.yarnpkg.com/debian stable/main arm64 Packages [10.9 kB]
19.41 Get:9 http://deb.debian.org/debian bookworm/main arm64 Packages [8685 kB]
19.43 Get:10 https://dl.yarnpkg.com/debian stable/main all Packages [10.9 kB]
21.73 Get:11 http://deb.debian.org/debian bookworm-updates/main arm64 Packages [13.7 kB]
21.74 Get:12 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages [157 kB]
22.37 Fetched 9163 kB in 3s (2857 kB/s)
22.37 Reading package lists...
22.61 Reading package lists...
22.85 Building dependency tree...
22.91 Reading state information...
22.98 Recommended packages:
22.98   nodejs
22.99 The following NEW packages will be installed:
22.99   yarn
23.20 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
23.20 Need to get 896 kB of archives.
23.20 After this operation, 5431 kB of additional disk space will be used.
23.20 Get:1 https://dl.yarnpkg.com/debian stable/main arm64 yarn all 1.22.22-1 [896 kB]
23.39 Err:1 https://dl.yarnpkg.com/debian stable/main arm64 yarn all 1.22.22-1
23.39   Hash Sum mismatch
23.39   Hashes of expected file:
23.39    - SHA512:cc957eb4db3401df75aaae104031c98dfdf648202859d9d8d1f0de2603f3705d1e11ab75b49667573d6a5e60a313db7fa877fdaf59fa798cb76c8db0a42772da
23.39    - SHA256:bdd227d3fead0510a1a75620ffa7369f61f50711505efa9dc371e14dca04e33e
23.39    - SHA1:a3073de43242748721a5e7caf157cb928c9c1329 [weak]
23.39    - MD5Sum:cf063bf7859c42360a0e50427931c640 [weak]
23.39    - Filesize:896308 [weak]
23.39   Hashes of received file:
23.39    - SHA512:ebd2648ebcc98820145846c992048a6049b424042d4b1a2bc335ddbc50f6ad09ecd6dcf18696b215953a841072c8cb566c4ecc8b511312dbc0a7932cd5e3c02b
23.39    - SHA256:321210ab31430d5b436a46712c4a1e16334394efa4be785b85d452bf519a11a3
23.39    - SHA1:7decf6ed8e53008e34e9107e1ed91a425d917f57 [weak]
23.39    - MD5Sum:a024b975107edcc830fe7dd449c9998e [weak]
23.39    - Filesize:896308 [weak]
23.39   Last modification reported: Fri, 24 May 2024 22:08:18 +0000
23.40 Fetched 896 kB in 0s (2238 kB/s)
23.40 E: Failed to fetch https://dl.yarnpkg.com/debian/pool/main/y/yarn/yarn_1.22.22_all.deb  Hash Sum mismatch
23.40    Hashes of expected file:
23.40     - SHA512:cc957eb4db3401df75aaae104031c98dfdf648202859d9d8d1f0de2603f3705d1e11ab75b49667573d6a5e60a313db7fa877fdaf59fa798cb76c8db0a42772da
23.40     - SHA256:bdd227d3fead0510a1a75620ffa7369f61f50711505efa9dc371e14dca04e33e
23.40     - SHA1:a3073de43242748721a5e7caf157cb928c9c1329 [weak]
23.40     - MD5Sum:cf063bf7859c42360a0e50427931c640 [weak]
23.40     - Filesize:896308 [weak]
23.40    Hashes of received file:
23.40     - SHA512:ebd2648ebcc98820145846c992048a6049b424042d4b1a2bc335ddbc50f6ad09ecd6dcf18696b215953a841072c8cb566c4ecc8b511312dbc0a7932cd5e3c02b
23.40     - SHA256:321210ab31430d5b436a46712c4a1e16334394efa4be785b85d452bf519a11a3
23.40     - SHA1:7decf6ed8e53008e34e9107e1ed91a425d917f57 [weak]
23.40     - MD5Sum:a024b975107edcc830fe7dd449c9998e [weak]
23.40     - Filesize:896308 [weak]
23.40    Last modification reported: Fri, 24 May 2024 22:08:18 +0000
23.40 E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
23.40 ERROR: Feature "Node.js (via nvm), yarn and pnpm" (ghcr.io/devcontainers/features/node) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/node for help troubleshooting this error.
------
Dockerfile.extended:64
--------------------
  63 |     ENV PATH="/usr/local/share/nvm/current/bin:${PATH}"
  64 | >>> RUN --mount=type=bind,from=dev_containers_feature_content_source,source=node_4,target=/tmp/build-features-src/node_4 \
  65 | >>>     cp -ar /tmp/build-features-src/node_4 /tmp/dev-container-features \
  66 | >>>  && chmod -R 0755 /tmp/dev-container-features/node_4 \
  67 | >>>  && cd /tmp/dev-container-features/node_4 \
  68 | >>>  && chmod +x ./devcontainer-features-install.sh \
  69 | >>>  && ./devcontainer-features-install.sh \
  70 | >>>  && rm -rf /tmp/dev-container-features/node_4
  71 |
--------------------
ERROR: failed to solve: process "/bin/sh -c cp -ar /tmp/build-features-src/node_4 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/node_4  && cd /tmp/dev-container-features/node_4  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/node_4" did not complete successfully: exit code: 100

Interestingly, disabling the feature and running the installation steps manually:
https://github.com/devcontainers/features/blob/1045404ea6fe783df230cfc1c022c777a8a67349/src/node/install.sh#L196-L199
works as expected. So I'm not sure why the above problem only occurs during container creation / feature installation:
root $ apt-get -y install --no-install-recommends yarn
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Recommended packages:
  nodejs
The following NEW packages will be installed:
  yarn
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 896 kB of archives.
After this operation, 5,431 kB of additional disk space will be used.
Get:1 https://dl.yarnpkg.com/debian stable/main arm64 yarn all 1.22.22-1 [896 kB]
Fetched 896 kB in 1s (1,396 kB/s)
Selecting previously unselected package yarn.
(Reading database ... 25013 files and directories currently installed.)
Preparing to unpack .../yarn_1.22.22-1_all.deb ...
Unpacking yarn (1.22.22-1) ...
Setting up yarn (1.22.22-1) ...

Snippet from devcontainer.json:
		"ghcr.io/devcontainers/features/node:1": {
			"version": "20"
		},

I'm behind a corporate firewall, but injecting all relevant certificates into the container before any features are getting installed.
Everything was still working fine a couple weeks (days?) ago.
Any help would be greatly appreciated.

	"ghcr.io/devcontainers/features/node:1": {"version": "20"},

I'm also wondering if we couldn't use corepack on Debian-based systems too?
The yarn docs state:

The preferred way to manage Yarn is by-project and through Corepack, a tool shipped by default with Node.js. Modern releases of Yarn aren't meant to be installed globally, or from npm.

https://yarnpkg.com/getting-started/install
Currently, there is special-handling for Debian systems in the feature, stating it's for backward-compatibility. Is this really still needed?


feat: add dockerfile

Description
This pull request introduces the necessary components to create and publish a custom docker image for quality control Python scripts.
Changes
-Added a basic Dockerfile to build the docker image.
-Integrated standard Ferlab GitHub Actions to automatically build and publish the docker image
Tests descrition

I built the image locally and open a shell on it. I checked that I was able to import the required libraries (numpy, matplotlib and pandas) in the python interpreter.
Not covered: github actions: these are very difficult to test locally as we need a git repository. We might need to do hot fixes if they are not right. Apart from the docker image build process, it should not affect any other functionality.

Agreed with the team on the image name.  The dockerhub repo is created, so we should be ready to merge. I am not 100% sure that the duckerhub repo is public, but I think that it should still work.


Remove ternary operator

Description of change

Removed a slight complexity from the SetTransform function. Maybe a little cleaner 🤷♂ ?
(Love your work btw guys!)
Pre-Merge Checklist

[x] Lint process passed (npm run lint)
[x] Tests passed (npm run test)

@Ewan-Roberts, thanks for contributing. We appreciate all PRs big and small.
For us, it's important that contributors are explicit about why they are changing something. It's not clear to me what problem you're trying to solve by your description. There's no significant performance implications by removing the ternary operator so I'd assume most of what you're doing is just stylistic.
Also, as far as your change goes, there are some non-starting issues:

Tests to not pass on Travis
Did you mean to use || (or) not | (bitwise)? Because you changed the meaning here.
We'd like to maintain default values in documentation and in the argument, that's used throughout PixiJS and actually add less clarity for those looking at the code or documentation.

Unfortunately, for these reasons, I'm going to close this PR. Thank you for your suggestion.


[Summer of code] Let controller become role state after append initial logs

Make sure set the target branch to develop
What is the purpose of the change
tracking issue: https://github.com/apache/rocketmq/issues/4330
Brief changelog
Let controller become role state after append initial logs
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

@RongtongJin PTLA

Codecov Report

Merging #4442 (462a54c) into 5.0.0-beta-dledger-controller (81dc938) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

:exclamation: Current head 462a54c differs from pull request most recent head b4e222d. Consider uploading reports for the commit b4e222d to get more accurate results

@@                         Coverage Diff                         @@
##             5.0.0-beta-dledger-controller    #4442      +/-   ##
===================================================================
- Coverage                            43.17%   43.15%   -0.03%
+ Complexity                            6343     6334       -9
===================================================================
  Files                                  841      841
  Lines                                59824    59824
  Branches                              8152     8152
===================================================================
- Hits                                 25830    25815      -15
- Misses                               30643    30652       +9
- Partials                              3351     3357       +6

Impacted Files
Coverage Δ

...he/rocketmq/controller/impl/DLedgerController.java
69.94% <100.00%> (ø)

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-8.96%)
:arrow_down:

...etmq/namesrv/routeinfo/BatchUnRegisterService.java
94.73% <0.00%> (-5.27%)
:arrow_down:

...mq/broker/topic/TopicQueueMappingCleanService.java
12.43% <0.00%> (-3.63%)
:arrow_down:

...q/controller/impl/manager/ReplicasInfoManager.java
61.75% <0.00%> (-2.77%)
:arrow_down:

.../apache/rocketmq/controller/ControllerManager.java
75.58% <0.00%> (-2.33%)
:arrow_down:

...va/org/apache/rocketmq/logging/inner/Appender.java
30.33% <0.00%> (-2.25%)
:arrow_down:

...a/org/apache/rocketmq/filter/util/BloomFilter.java
59.13% <0.00%> (-2.16%)
:arrow_down:

...a/org/apache/rocketmq/store/StoreStatsService.java
49.17% <0.00%> (-1.11%)
:arrow_down:

...org/apache/rocketmq/store/DefaultMessageStore.java
53.88% <0.00%> (ø)

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 81dc938...b4e222d. Read the comment docs.

Coverage decreased (-0.02%) to 47.352% when pulling b4e222d8f402b7eeec478ab5c06cecaf89cc96fb on hzh0425:feature/delay-controller-become-leader into 81dc9386a1a5f932896bea3ddfa9452cddea1786 on apache:5.0.0-beta-dledger-controller.

Coverage decreased (-0.02%) to 47.352% when pulling b4e222d8f402b7eeec478ab5c06cecaf89cc96fb on hzh0425:feature/delay-controller-become-leader into 81dc9386a1a5f932896bea3ddfa9452cddea1786 on apache:5.0.0-beta-dledger-controller.


Modified destroy method for bug #1641

There is no need to empty input element value on destroying flatpickr instance

@chmln hey gregory, I require help to resolve the test cases

wondering if this could be moved along? Sorry I don't want to be a pest but this issue is wreaking havoc on our site.

@dunkoh it was merged in my PR. You can close this.

@bytestream @SDJLee created this PR so he can close it or @chmln could do so


[NEW ALGORITHM] Banker's Algorithm

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
[NEW ALGORITHM]  Banker's Algorithm
About:
The Banker's Algorithm is a resource allocation and deadlock avoidance algorithm used in operating systems. It ensures that resources are allocated only if the system can stay in a safe state, meaning all processes can complete without causing deadlock. The algorithm checks if the requested resources can be granted by calculating a "safe sequence," where each process can obtain its maximum required resources and release them after completion. If such a sequence exists, the system is considered safe. Otherwise, the request is denied to avoid entering an unsafe state.
Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[X] Contributor in GSSoC-ext
[X] Want to work on it

@pankaj-bind assign this issue to me.

assigned


corrected the position of start and restart

PR Description 📜
initially start and resart option were displayed at the corner .Now they will be at the centre

Mark the task you have completed ✅
#145

[x ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x ] I have performed a self-review of my own code or work.
[x ] I have commented my code, particularly in hard-to-understand areas.
[x ] My changes generates no new warnings.
[ x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x ] I have added screenshot for review.

Plz review it and suggest any changes


Order of components affects styling

react-native, react and native-base version
"native-base": "^2.3.9",
"react-native": "0.53.3",
Steps to reproduce (code snippet or screenshot)

run ejectTheme script
customise Item styles:

{
    ...
    ".regular": {
      "NativeBase.Input": {
        backgroundColor: 'red'
       }
    }
    ...
}

render component:

function SampleComponent() {
    return (
        <View>
            <Item regular>
                <Input placeholder="Email" />
            </Item>
            <Item>
                <Input placeholder="Email" />
            </Item>
        </View>
    )
}

Invert the order of the Items:

function SampleComponent() {
    return (
        <View>
            <Item>
                <Input placeholder="Email" />
            </Item>
            <Item regular>
                <Input placeholder="Email" />
            </Item>
        </View>
    )
}

On the first instance both Inputs will have a red background.
On the second instance none of the Inputs will pick up the red background.
The expected is only the Input under Item with regular attribute will have a red background.
Is the bug present in both ios and android or in any one of them?
yes

@hugofelp tried the above example. Couldn't see anything like you mentioned. Can you reset the cache and try again. Attaching a gif

Hi @akhil-geekyants. Thanks for your response.
After clearing the cache and getting the same results, I started a new project from React Native Seed to try and reproduce the bug.
It turns out I was importing View from react-native instead of importing from native-base. That is the only step missing from the description above on how to reproduce.
So I guess my problem is solved, but if you agree this is a bug and want to look into it, here is the file I have at src/boot/setup.js :
import * as React from "react"
import { View } from "react-native"
import { StyleProvider, Item, Input } from "native-base"
import getTheme from "../theme/components"
import variables from "../theme/variables/platform"

export default class Setup extends React.Component<Props, State> {
  render() {
    return (
      <StyleProvider style={getTheme(variables)}>
        <View>
          <Item>
            <Input placeholder="Email" />
          </Item>
          <Item regular>
            <Input placeholder="Email" />
          </Item>
        </View>
      </StyleProvider>
    )
  }
}

And some screenshots:

@hugofelp Importing View from NativeBase actually solves the problem


Databases not attached

output:
sql_1    | VERBOSE: Starting SQL Server
sql_1    | VERBOSE: Changing SA login credentials
sql_1    | VERBOSE: Attaching 104 database(s)
sql_1    | VERBOSE: Invoke-Sqlcmd -Query IF EXISTS (SELECT 1 FROM SYS.DATABASES WHERE NAME
sql_1    |  = '') BEGIN EXEC sp_detach_db [] END;CREATE DATABASE [] ON  FOR ATTACH;
sql_1    | Msg 1038, Level 15, State 4, Server AA70365A420D, Line 1
sql_1    | An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
sql_1    | Msg 1038, Level 15, State 4, Server AA70365A420D, Line 1
sql_1    | An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
sql_1    | Msg 156, Level 15, State 1, Server AA70365A420D, Line 1
sql_1    | Incorrect syntax near the keyword 'FOR'.

sql_1    | VERBOSE: Started SQL Server.

docker-compose.yml:
version: '3'
services:
  sql:
    image: "microsoft/mssql-server-windows-developer"
    env_file: sql.env
    volumes:
      - ./sql/dbs/:C:/temp/
    ports:
      - "1433:1433"

configuration from sql.env:
attach_dbs="[{'dbName':'foo','dbFiles':['C:\\temp\\foo.mdf','C:\\temp\\foo.ldf']}]"

Yes Same problem for me. I tried switching C:\temp\foo.mdf => C:\temp\foo.mdf and tried C:/temp/foo.mdf
nothing is working for me.

It took 4 slashes to make this work for me
attach_dbs="[{'dbName':'foo','dbFiles':['C:\\\\temp\\\\foo.mdf','C:\\\\temp\\\\foo.ldf']}]"

Yooo dbelcham that worked for me dude !! TY ALOT !!!


No parser for parsing UPLC

Check out the uplc parse by @aiken-lang for reference: https://github.com/aiken-lang/aiken/blob/main/crates/uplc/src/parser/interner.rs

A parser was added via feat/parser


Codeaon : Make Footer Responsive

Task

Make the footer responsive for all devices
Remove the wave and change the background color of the footer-container to the color of the existing wave when its mobile responsive

Before contributing read contributing.md

Would like to work on this issue.


Make a PR to the main keras repo?

I think it might make sense to add this optimizer to the main keras repo!

See also https://github.com/keras-team/keras/issues/12352

It probably won't be added right away, but it can possibly be done so after a few months of it being tested.

make PR to keras-contrib.

I suggest a PR to Tensorflow-addons https://github.com/tensorflow/addons
their release schedule is faster.


MongoDB logging stopped working on the device after some time

I noticed that the experiments were running a few seconds faster - because the MongoDB logging stopped on the device side for some reason. The results were still collected by the client but not stored in the database. Resetting the device caused the experiment logging to resume.
The actual errors may be embedded in results stored in the Jupyter notebook kernel I'm running. It had been too long to easily check if it was an issue of too many connections or some other resource limitation imposed by MongoDB. It seems more likely to have been recurring ENOMEM errors on the Pico W (i.e., too much RAM being used).

Possibly related, from error.txt
Traceback (most recent call last):
  File "main.py", line 274, in <module>
  File "/lib/umqtt/simple.py", line 71, in connect
OSError: [Errno 12] ENOMEM

Using requests library to do MongoDB logging inside of an MQTT loop may be a bit much for the Pico W microcontroller. Only logging data to an SD card and via the client is worth considering (i.e., dropping the device-side logging to MongoDB) https://github.com/sparks-baird/self-driving-lab-demo/issues/154. I am pushing the limits of the Pico W RAM.


Can't input text with physical (computer's) keyboard after test finishes in patrol develop

On Android emulator. I'm using API 34 Pixel 8 emulator, and I'm on Mac.
It used to work - every interaction could be done after test finished (more precisely - failed) during patrol develop. It's not caused by emulator's setting, bc I can do it while test still executes or when debugging app (without test, just flutter run).

Didn't check iOS, maybe there this problem doesn't occur


Feat: Team Builder

Implement a basic team builder that lets a user select 6 Pokemon with custom IVs, level (up to level 50), and moves.
Requirements

[ ] Pokemon selection component #2
[ ] Team Verifier #3
[ ] Saving a team updates the value of TeamContext
[ ] A saved team is stored in a cookie which can update TeamContext on first render

Notes

The homepage needs a link to this team builder. The team builder should be on its own route in /pages.
Styling will be a different issue, as there is no design mockup yet. The team builder will eventually be very similar to the Pokemon Showdown team builder.
@jarthur22 has a lot of team builder code available to port over.

Should be up to level 51 to account for best-buddy with XL candy

Should be up to level 51 to account for best-buddy with XL candy

👍

👍

this issue is a little too big for the deadline. i'm going to comment out the firebase features and use cookies for now. Firebase team/settings storage will be a separate issue for next milestone

So the teambuilder is nearly done, but the pokemon selector (which is part of the teambuilder) is not yet complete. I'll close this issue but keep the pokemon selector part open. No PR yet


dynamically changeable parameters

namespace from the config file has been removed
takeoff height has to be in range <0.5;10>
device_url parameter is not possible to change dynamically

@jnippula, the PR is approved from our side. When you have some time, please check it.

Update to align with master needed, will reopen once ready


Feature: Letter highlighting (as with the original 8pen)

Highlights the current letter on the pad by making it bold.
Also, update the pad to change to upper case the letter  when a complete turn is made
refs: #271

@MaethorNaur Thanks.

@MaethorNaur Thanks.

mmm.... Can someone explain why I can't merge this?

Maybe you have to rerun the workflows?

what workflows? I don't have any...

https://github.com/flide/8VIM/actions/workflows/android.yml

okay okay, been away too long, don't remember setting up a android CI. Seems the last run failed, but logs are no longer available to see why that was. Can you request a CI run again on this PR?

I am able to run it on my machine, so the build should not fail ... I don't see why the workflow failed.

I don't find the option. Otherwise, maybe you have to review the PR and accept the changes

https://user-images.githubusercontent.com/7330631/227946578-dcca6396-a474-4112-9a24-7cca9b4e12f0.mov

It seems that GitHub has some issues with PR ATM. https://www.githubstatus.com/


Append with file redirection not working running linux tools from Windows command line

On Windows (version 10.0.18362.267) I'm trying to accumulate in a file results of linux tools, but only last result is stored. Simplifying, this is the problem:
>wsl echo line1 >> file.txt
>wsl echo line2 >> file.txt
>wsl echo line3 >> file.txt
>wsl xxd file.txt
00000000: 6c69 6e65 330a                           line3.

File is always replaced. Append is not working.

Looking at your input it seems like you're running wsl through another shell (I'm going to guess CMD). That shell is interpreting and capturing the >> symbol, which is why you're running into this error.
If you want to use the command in CMD escpae out the > character by using:
wsl echo line1 ^>^> file.txt
Or you can use the command in powershell where it will work as expected.
I'll close out this issue since I believe it's resolved, if that's not the case please reopen! Thanks for filing.

Thanks for your response.
I still think actually there is an error in WSL interoperability:

Official documentation states:

https://docs.microsoft.com/en-us/windows/wsl/interop
Run Linux binaries from the Windows Command Prompt (CMD or PowerShell)
Things such as sudo, piping, and file redirection work.

You are right, I'm working with CMD (I know there are multiple aternatives to avoid the error, but I'm pointig to what I consider a problem in WSL). And CMD has not problems with file redirections.

I've compiled an EXE with same output as linux echo (to keep end lines):
CMD> wsl echo line1 | wsl xxd
00000000: 6c69 6e65 310a                           line1.
CMD> echoLinux.exe line1 | wsl xxd
00000000: 6c69 6e65 310a                           line1.

CMD, as usual, works correctly with append operations via file redirection of Windows executables:
CMD> (echoLinux.exe line1) > file1.txt
CMD> (echoLinux.exe line2) >> file1.txt
CMD> (echoLinux.exe line3) >> file1.txt
CMD> wsl xxd file1.txt
00000000: 6c69 6e65 310a 6c69 6e65 320a 6c69 6e65  line1.line2.line
00000010: 330a                                     3.

File redirection (appending) does not work when the executable is a linux tool launched with WSL:
CMD> (wsl echo line1) > file2.txt
CMD> (wsl echo line2) >> file2.txt
CMD> (wsl echo line3) >> file2.txt
CMD> wsl xxd file2.txt
00000000: 6c69 6e65 330a                           line3.

Having to escape redirection to avoid normal CMD work breaks interoperatibility between both worlds.

Thank you for the description, and also thank you to @DHowett-MSFT for taking a look at this issue as well.
This does seem to be a WSL problem. I'll reopen the issue.

@craigloewen-msft The WAR you mentioned before closing the issue for the first time does not seem to be working.
https://github.com/microsoft/WSL/issues/4400#issuecomment-520572113
It is again replacing the file instead of appending to it.
P.S Requirement is to run this command in CMD.
Command:
cmd /c wsl echo hi ^>^>temp.txt
cmd /c wsl echo hi ^>^>temp.txt
Output:
$ cat temp.txt
hi

To me it looks like writing to the file starts at the start of the file, even though I use >> to append. I would expect this to be cmd.exe's responsibility. But it only happens with wsl...

indeed it doesn't seem to truncate the file and replace the content, but indeed starts "appending" from start, the following is in git-bash:
$ cat output
cat: output: No such file or directory
$ wsl.exe echo foo >> output
$ cat output
foo
$ wsl.exe echo barbazlonger >> output
$ cat output
barbazlonger
$ wsl.exe echo foo >> output
$ cat output
foo
azlonger
$ uname
MINGW64_NT-10.0-22631

So redirects certainly won't work as expected, and at least a big fat warning should be added to the documentation.
And to throw another workaround into the mix: "wsl.exe echo foo | cat - >> output" probably the first useless use of cat that's not completely useless....


Fix various tags not being a list

When attempting to use the variables cluster_tag_name or allowed_inbound_tags_api I would get errors from Terraform about the tags not being a list. This PR fixes that issue.

@madmod Thanks for fixing this. Change looks good to me, so merging. How I wish we had automated tests for this. Hopefully we can justify setting those up at some point in the near future.


Issue opening h5py arrays

I used dask (and xarray) to combine a set of H5py files into a dataframe.
This worked great until I updated dask from 2.28 to 2021.07.1.
If I run the same script now, I always run out of memory, just after loading the files and doing any operation on the
dataframe.
I first thought it was an xarray issue (reported here: https://github.com/pydata/xarray/issues/5585).
So I switched to a pure dask solution (based on: https://docs.dask.org/en/latest/array-creation.html)
However, I keep running into the same problem.
I tried 3 different methods:

converting a h5py to a numpy dict and load as pandas df with dask.delayed. Then construct a dask dataframe from the delayed
loading the individual files as dask arrays and convert them to dask dataframe per file, then combine the dataframes
load the files as dask arrays, combine them into a big dask array, then convert that to dataframe.
All with the same results: Kernel died, due to memory

I tried different chunk sizes. Smaller chunks just makes everything slower (incl overloading the RAM). Bigger chunks just make it faster but stilll overload the memory. In any case the kernel still crashes early in the process, due to memory overload.
Also when trying to save the dataframe, nothing/just a few kbs are written.
Therefore I suspect that there is a problem with the creation of the dataframe, not saving it.
First I suspected the transformation form array to dataframe to be the issue.
But running calculation on the array itself or saving it also cause the same issue.
That's why I think it has to do with the loading of an array from h5py.
If am doing something principally wrong here, please let me know. But this code worked great for me on earlier versions of dask.
Thank you!
Here is code to reproduce. I have 16GB  RAM, so to reproduce you might need to adjust the number of files loaded if you have more RAM:
Create Datafiles (note this takes a couple of GB disk space)
import numpy as np
import h5py

from shutil import copyfile

def makefile(data, n, nfiles):
    for i in range(nfiles):
        print(f"\rCreating File: {i} / {nfiles - 1}       ", end="")
        if i == 0:
            with h5py.File(f"{i}.h5", 'w') as file:
                for par in range(n):
                    file.create_dataset(f'data/{par}',
                                        data=data,
                                        dtype='f4',
                                        maxshape=(None,),
                                        chunks= (32000,), # (dlength,),
                                        compression='gzip',
                                        compression_opts=5,
                                        fletcher32=True,
                                        shuffle=True,
                                    )
        else:
            copyfile('0.h5', f"{i}.h5")

data = np.random.randint(0, 0xFFFF, int(1e7))
makefile(data, 10, 100)    # ~100 files is enough to create an error on my 16GB RAM 24GB swap, increase if you have more RAM?
del data

Setup
import os
import h5py
import dask
import dask.dataframe as dd
import dask.array as da
import numpy as np
import pandas as pd

from dask.diagnostics import ProgressBar
ProgressBar().register()

file_list = sorted([f for f in os.listdir(".") if f.endswith('.h5')])

Method 1 (Pandas)
@dask.delayed
def hdfs_2_pd(f):
    file = h5py.File(f, 'r')["data/"]
    return pd.DataFrame.from_dict({k:v[:] for k, v in file.items()})

ddf = dd.from_delayed([hdfs_2_pd(f) for f in file_list])

Method 2 (ddf per file)
out = []
for fn in file_list:
    f = h5py.File(fn, "r") # HDF5 file
    d = f['/data/']
    x = da.stack([da.from_array(i, chunks=(100000,)) for i in d.values()], axis=1)
    keys = d.keys()
    out.append(dd.from_dask_array(x, columns=keys))
ddf = dd.concat(out)

Method 3: combine arrays
out = []

for fn in file_list:
    f = h5py.File(fn, "r") # HDF5 file
    d = f['/data/']
    x = da.stack([da.from_array(i, chunks=(100000,)) for i in d.values()], axis=1)
    keys = d.keys()
    out.append(x)

combined = da.concatenate(out)
ddf = dd.from_dask_array(combined, columns=keys)

Testing ddf
All these methods produce a dask dataframe. However in the next steps Memory will fully load
and the kernel will crash:
ddf['0'].mean().compute()

output:
[                                        ] | 0% Completed |  6min 57.9s
ddf.to_hdf("combined.h5",
           key='/data*',
           complevel=5,
           complib="blosc:lz4hc",
          )

output:
[#                                       ] | 3% Completed | 13min  8.7s
ddf.to_parquet("conbined.pq",
               compression="gzip",
               append=False,
               overwrite=True,
)

output:
[##                                      ] | 5% Completed |  4min 11.9s
da.to_hdf5('./combined_arr.h5',
           {f"/test": combined},
           compression='gzip',
           shuffle=True,
           compression_opts=5)

output:
[#                                       ] | 3% Completed |  5min 57.9s
Environment:

Dask version: '2021.07.0'
h5py version:
Python version: Python 3.8.2 (Ananconda)
Operating System: Ubuntu 21.04
Install method (conda, pip, source): conda

Thanks for raising an issue @N4321D. I wonder if you're running into https://github.com/dask/dask/issues/7583. Could you try using the distributed scheduler to see if that resolves your memory issues? This could involve adding
from dask.distributed import Client

client = Client()

to you code snippets

Thanks for you quick reply.
With client calculating the mean works:
output:
32761.672892416
but I run into: https://github.com/dask/dask/issues/7926 with saving.
traceback (for full see  https://github.com/dask/dask/issues/7926):
.....

HDF5ExtError: HDF5 error back trace

  File "H5F.c", line 509, in H5Fopen
    unable to open file
  File "H5Fint.c", line 1400, in H5F__open
    unable to open file
  File "H5Fint.c", line 1615, in H5F_open
    unable to lock the file
  File "H5FD.c", line 1640, in H5FD_lock
    driver lock request failed
  File "H5FDsec2.c", line 941, in H5FD_sec2_lock
    unable to lock file, errno = 11, error message = 'Resource temporarily unavailable'

End of HDF5 error back trace

Unable to open/create file './delme/combined.h5'

I've had the same problem using xarray's open_mfdataset to read large netcdf files. Downgrading Dask to 2.28 solved it for me.

I'm wondering if your original approach would work better now that #7583 is resolved. Are you able to update to latest dask and try again?

Thank you!
Using 2018.08.1 (newest version on anaconda)
It partly works now without the distributed cluster:
not using distributed:

Working: Calculating the mean
Working: Saving h5 with dask array (da.to_hdf)
Not working: Saving to h5 with dask dataframe (ddf.to_hdf) still overloads the memory and kills the kernel when at ~50% using the local cluster.

Using distributed cluster:

Not working: Still run into HDF5ExtError: HDF5 error back trace (https://github.com/dask/dask/issues/7926 )

Ok thanks for the report!


Fix tests that are skipped

Fixes #24
Before:
Test Suites: 3 passed, 3 total
Tests:       29 skipped, 13 passed, 42 total

After:
Test Suites: 3 passed, 3 total
Tests:       8 skipped, 34 passed, 42 total

ups, how did that happen :D

:tada: This PR is included in version 3.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix deploy eac

Pull Request Test Coverage Report for Build 1273

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.04%) to 84.004%

Files with Coverage Reduction
New Missed Lines
%

src/Stats/StatsDB.ts
1
87.3%

src/Actions/Actions.ts
3
63.21%

src/Actions/Pending.ts
4
37.84%

Totals

Change from base Build 1266:
-0.04%

Covered Lines:
558

Relevant Lines:
638

💛  - Coveralls

Pull Request Test Coverage Report for Build 1273

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.04%) to 84.004%

Files with Coverage Reduction
New Missed Lines
%

src/Stats/StatsDB.ts
1
87.3%

src/Actions/Actions.ts
3
63.21%

src/Actions/Pending.ts
4
37.84%

Totals

Change from base Build 1266:
-0.04%

Covered Lines:
558

Relevant Lines:
638

💛  - Coveralls

closing