docs: Mention macOS ARM vs Intel Homebrew dagger install path diff

This supersedes https://github.com/dagger/dagger/pull/1998. We appreciate the contribution @sauzy34 and want to get it merged. Thank you!

Please merge if all checks pass & you are OK with the changes @slumbering @TomChv (#1998 reviewers)

I think that the Netlify failure is due to a https://github.com/dagger/dagger/pull/2173 side-effect: https://app.netlify.com/sites/devel-docs-dagger-io/deploys/62570cbd8d3caa00085e5440#L78-L80

I am not sure what is the exact problem, investigating...

Doesn't this erase original author information for the commits?

While the intent is the same as https://github.com/dagger/dagger/pull/1998, the change is different, as is the author:

Can you think of a better way of addressing the absence of a follow-up while moving this forward? https://github.com/dagger/dagger/pull/1998#issuecomment-1096492588

WDYT @dolanor @grouville @helderco @TomChv?


BugFix: It's too hard to press names to auto-insert nicks.

https://github.com/vector-im/vector-ios/issues/309

LGTM


Packages being built even if flagged as "only-binary"

I have this minimal pyproject.toml
[project]
name = "my-project"
version = "0.2.0"
description = "Cool project"
requires-python = ">=3.10"
dependencies = [ "pyarrow==17.0.0" ]

[tool.uv]
[tool.uv.pip]
only-binary = ["pyarrow"]

(venv) (base) ➜  test_uv  uv cache clean
Clearing cache at: /Users/arnaldovarela/.cache/uv
Removed 1770 files (200.6MiB)
(venv) (base) ➜  test_uv  uv self update
info: Checking for updates...
success: You're on the latest version of uv (v0.4.25)
(venv) (base) ➜  test_uv  uv sync
warning: `VIRTUAL_ENV=venv` does not match the project environment path `.venv` and will be ignored
Using CPython 3.10.4
Creating virtual environment at: .venv
Resolved 3 packages in 0.92ms
   Built numpy==2.1.2                                                                                error: Failed to prepare distributions
  Caused by: Failed to download and build `pyarrow==17.0.0`
...

And the packages are built instead of using the binaries.
This is a problem as to build pyarrow some apache dependencies and cmake are required to be installed.
I'm running this on a Mac M1 running 14.5 (23F79).
When installing with Pipfile:
[[source]]
url = "https://pypi.org/simple"
name = "pypi"
verify_ssl = true

[packages]
pyarrow = "==17.0.0"

[requires]
python_version = "3.10"

it takes just a few seconds and no need to build:
(venv) (base) ➜  test_uv  pipenv install
Loading .env environment variables...
Courtesy Notice:
Pipenv found itself running within a virtual environment,  so it will automatically use that environment, instead of  creating its own for any project. You can set
PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create  its own instead.
You can set PIPENV_VERBOSITY=-1 to suppress this warning.
Pipfile.lock not found, creating...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✔ Success!
Locking [dev-packages] dependencies...
Updated Pipfile.lock (9f6dbf61cecaca8a7db4e36abb151730ab51fadc17e8c779b2687808a27abe20)!
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (7abe20)...

Also i think is a bug that it tries to build the package as, according to the docs

but operations that require building distributions will exit with an error.

And it isnt, it is trying to build and the errors depend on the build phase error:

cmake missing
apache-arrow missing
Some arrow build flag missing

Looks like you're using uv sync but configuring things at the tool.uv.pip level. See https://docs.astral.sh/uv/configuration/files/#configuring-the-pip-interface

Ok interesting, that does make sense.
Isn't there a way to force/require binaries only in uv commands (like sync)? :(

Okok that in fact makes sense @zanieb thanks a lot.
Do you see anyway, then, for me to specify the package as dependency and not build it but taking the built wheel directly using sync? 🙏

Hm, interesting yeah this works fine for me
❯ echo pyarrow==17.0.0 | uv pip compile --only-binary pyarrow -
Resolved 2 packages in 5ms
# This file was autogenerated by uv via the following command:
#    uv pip compile --only-binary pyarrow -
numpy==2.1.2
    # via pyarrow
pyarrow==17.0.0

Does it work if you configure tool.uv.no-build-package instead of setting it on the CLI?

I get the same issue of it not finding the binary 😭

Does it work with uv pip compile as in my example?

Nope, same error:
(venv) (base) ➜  pipfile_to_uv  uv cache clean
Clearing cache at: /Users/arnaldovarela/.cache/uv
Removed 10 files (2.9MiB)
(venv) (base) ➜  pipfile_to_uv  uv venv
warning: `VIRTUAL_ENV=venv` does not match the project environment path `.venv` and will be ignored
Using CPython 3.10.4
Creating virtual environment at: .venv
Activate with: source .venv/bin/activate
(venv) (base) ➜  pipfile_to_uv  source .venv/bin/activate
(pipfile_to_uv) (base) ➜  pipfile_to_uv  echo pyarrow==17.0.0 | uv pip compile --only-binary pyarrow -
  × No solution found when resolving dependencies:
  ╰─▶ Because pyarrow==17.0.0 has no usable wheels and building from source is disabled and you require pyarrow==17.0.0, we can conclude that your requirements are unsatisfiable.

Then there must be something different about your platform. Can you provide verbose logs (i.e. -v)?

This is what came out:
(pipfile_to_uv) (base) ➜  pipfile_to_uv  echo pyarrow==17.0.0 | uv pip compile -v --only-binary pyarrow -
DEBUG uv 0.4.25 (97eb6ab4a 2024-10-21)
DEBUG Starting Python discovery for a default Python
DEBUG Looking for exact match for request a default Python
DEBUG Searching for default Python interpreter in managed installations or system path
DEBUG Found `cpython-3.10.4-macos-aarch64-none` at `/Users/arnaldovarela/Documents/repos/pipfile_to_uv/.venv/bin/python3` (active virtual environment)
DEBUG Using Python 3.10.4 interpreter at .venv/bin/python3 for builds
DEBUG Using request timeout of 30s
DEBUG Solving with installed Python version: 3.10.4
DEBUG Solving with target Python version: >=3.10.4
DEBUG Adding direct dependency: pyarrow==17.0.0
DEBUG Found stale response for: https://pypi.org/simple/pyarrow/
DEBUG Sending revalidation request for: https://pypi.org/simple/pyarrow/
DEBUG Found not-modified response for: https://pypi.org/simple/pyarrow/
DEBUG Searching for a compatible version of pyarrow (==17.0.0)
  × No solution found when resolving dependencies:
  ╰─▶ Because pyarrow==17.0.0 has no usable wheels and building from source is disabled and you require pyarrow==17.0.0, we can conclude that your requirements are unsatisfiable.

I think is related to the cpython version being chosen + the wheels available. Seems like the "aarch" versions don't properly map for mac, being "manylinux" in the pyarrow wheels.
After a uv uv python list --all-versions I found that cpython-3.10.15-macos-x86_64-none was available.
I changed my commands to:
uv venv --python 3.10.15
source .venv/bin/activate
 echo pyarrow==17.0.0 | uv pip compile -v --only-binary pyarrow -
uv sync
uv cache clean
uv venv --python 3.10.15
source .venv/bin/activate
uv sync

I think this kinda solves my problem, but i wonder if the manylinux wheels should or shouldn't have been mapped to my cpython version 🤔

Sweet!
You can't use manylinux wheels on macOS. Are you suggesting something else?

https://pypi.org/project/pyarrow/#files  should have your explanation.
You have macos and Python 3.10, these are the available wheels:

pyarrow-17.0.0-cp310-cp310-macosx_11_0_arm64.whl (27.2 MB view hashes)

Uploaded Jul 16, 2024 CPython 3.10 macOS 11.0+ ARM64

pyarrow-17.0.0-cp310-cp310-macosx_10_15_x86_64.whl (29.0 MB view hashes)

Uploaded Jul 16, 2024 CPython 3.10 macOS 10.15+ x86-64
The first one fits your arm64 configuration but it requires macos version 11, so it can't be used for you and I think that's the reason.

Ok, turns out i'm actually on macos 15.0.1 but there is a configuration when they went from macos 10 to 11 to show a legacy version number.
Most recent wheels for mac are buing built for 11+ on arm64.
Setting the environment variable SYSTEM_VERSION_COMPAT=0 changed the macos version determined by python to:
macOS-15.0.1-arm64-arm-64bit
with this my install problems have been solved so far.
thanks both!

I know this is closed already, but I made an article at my job on migrating Pipenv to uv as there were no other guides.
I included the macOS issue and a minimal script to migrate from Pipfile to pyproject.toml
In case you care:
https://medium.com/clarityai-engineering/migrating-from-pipenv-pipfile-to-uv-59ba2846636f

Struggled installing pyarrow in a similar fashion (failing to find pyarrow 17 binary, on macos). Turned out I had a .python-version specifying 3.13, which seemingly made uv use 3.13 for resolution, even though I had used uv venv -p 3.11 to setup venv. Setting 3.11 in .python-version solved the issue.


Allow avoiding office address geocode w/ admin #68

Fixes #68

I have the tests written for both happy and unhappy paths for an invalid address on office creation.  I would like to have a stub_request for the failed address geocode but was not able to get VCR to record with geocoder when I tried.  So at the moment this one test hits the smartystreets API.
I believe this may be ready for review & suggestions. cc @nvick

Since we're stubbing Geocode requests we may also use it's own stubbing techniques: https://github.com/alexreisner/geocoder#testing
I'll look into this later.  It may be an easier solution overall.

Thanks @danielpclark! @dinjas will review this on Friday this week.

Closing in favor of #136


Fix console not loading sometimes

Issue was data.line was null. it then would not iniate properly. simple if statement to prevent the issue and the console is super reliable now in all browsers.
Posted here as a pull request by request of Dane in the discord

Could you also add a CHANGELOG entry indicating this is fixed?

Yep, 0.7 :)

Just committed the CHANGELOG. seems to show in this pull request so I guess that is it done (kinda new to pull requests)

Yep, you're doing it right. In the future it might help to make a new branch on your own repo for changes, but once you make a PR Github will track changes you push into the linked repo and branch, and update this PR accordingly.

Cool. in future I will do a new branch for sure.
 I ain't a good typist


Bugs Report and Fix

Bugs about invoke_result: build/include/eigen3/Eigen/src/Core/util/Meta.h:617:25: error: ‘invoke_result’ in namespace ‘std’ does not name a template type

This is a bug caused by not compiling with c++17. However, although the CMAKE_CXX_STANDARD flag is 17 in the CMakeList.txt, the bug still exists. The probable solution is to comment these lines in the head files, e.g., when compiling, change the code from
#if EIGEN_HAS_STD_INVOKE_RESULT
template<typename F, typename... ArgTypes>
struct invoke_result {
   typedef typename std::invoke_result<F, ArgTypes...>::type type1;
   typedef typename remove_all<type1>::type type;
 };
 #elif EIGEN_HAS_CXX11
 template<typename F, typename... ArgTypes>
 struct invoke_result {
   typedef typename result_of<F(ArgTypes...)>::type type1;
   typedef typename remove_all<type1>::type type;
 };
 #else
 template<typename F, typename ArgType0 = void, typename ArgType1 = void, typename ArgType2 = void>
 struct invoke_result {
   typedef typename result_of<F(ArgType0, ArgType1, ArgType2)>::type type1;
   typedef typename remove_all<type1>::type type;
 };

to
/*#if EIGEN_HAS_STD_INVOKE_RESULT
template<typename F, typename... ArgTypes>
struct invoke_result {
   typedef typename std::invoke_result<F, ArgTypes...>::type type1;
   typedef typename remove_all<type1>::type type;
 };*/
 #if EIGEN_HAS_CXX11
 template<typename F, typename... ArgTypes>
 struct invoke_result {
   typedef typename result_of<F(ArgTypes...)>::type type1;
   typedef typename remove_all<type1>::type type;
 };
 #else
 template<typename F, typename ArgType0 = void, typename ArgType1 = void, typename ArgType2 = void>
 struct invoke_result {
   typedef typename result_of<F(ArgType0, ArgType1, ArgType2)>::type type1;
   typedef typename remove_all<type1>::type type;
 };

You can do the same thing in other files when this bug emerges.

Bugs about io: SceneGraphFusion/libGraphSLAMGUI/../renderer/Scan3R_json_loader.h:9:18: error: ‘io’ in namespace ‘::’ does not name a type

You just need to delete the "::io" in some related files.

Bugs about clamp: SceneGraphFusion/libGraphSLAMGUI/graphDrawer/graph_drawer.cpp:81:23: error: ‘clamp’ is not a member of ‘std’

This is also a bug caused by C++ standard. You can change the clamp function from:
float scale = std::clamp((5-std::sqrt(point.z()))/5.f,0.1f,1.f);

to
float scale = (5-std::sqrt(point.z()))/5.f;
if (scale < 0.1f)
{
  scale = 0.1f;
}
else if (scale > 1.f)
{
  scale = 1.f;
}

Bugs about atomoic: it  emerges in the https://github.com/ShunChengWu/SceneGraphFusion/blob/4c632d12dd492c362ee2708a85410f367724b572/libGraphSLAM/node.h#L52 and https://github.com/ShunChengWu/SceneGraphFusion/blob/4c632d12dd492c362ee2708a85410f367724b572/libGraphSLAM/node.h#L61.

It may be also caused by c++17 standard. You can change them to
std::atomic_int instance_idx = {0};

std::atomic_bool mbNeedUpdateNodeFeature = {false};

https://github.com/ShunChengWu/SceneGraphFusion/blob/4c632d12dd492c362ee2708a85410f367724b572/libGraphSLAM/node.cpp#L74

This line should be changed to std::unique_lock<std::mutex> lock_node(mMutNode);

About eigen

If this bug emege, you may build and install the eigen3 from source.

Bugs about freetype2 (I guess it may be caused by HarfBuzz), the error may emerge as: SceneGraphFusion/build/external/FreeType2/src/autofit/afscript.h:35:11: error: ‘HB_SCRIPT_ADLAM’ undeclared here (not in a function) and SceneGraphFusion/build/external/FreeType2/src/autofit/afscript.h:278:11: error: ‘HB_SCRIPT_OSAGE’ undeclared here (not in a function)

The temporary solution is to find out the associated lines in these head files and comment them. Another head file is afstyle.h.

When running the executable file, you should put the 3RScan.json and objects.json(from 3DSSG) under the correct directory. E.g., if the --pth_in is scans/sequence_idxxxx/sequence/, you should put these two files under scans/

It seems that the GUI does not support remote X forward, i.e., if you compile the project on a remote server and run it on the local computer, the error may emerge: Error: GLX: Forward compatibility requested but GLX_ARB_create_context_profile is unavailable. Finally I compiled it on the local computer with an NVIDIA GPU.

Hey, thanks for the detailed report and suggestion. The code hasn't been tested under a different environment. We have only tested it within a docker environment but with the same setup.
I will try to merge your suggestions into the code to make it easier to compile.
Thanks


Add documentation for http proxy middleware in API Routes Nextjs

Describe the feature you'd love to see
Add documentation for http proxy middleware in API Routes Nextjs
Additional context (optional)
No response

I've found the examples provided elsewhere don't work correctly on the first request.  The first request triggers .on('upgrade') registration, causing subsequent requests to succeed. But the first request hangs indefinitely.

@justin-together could you give concrete urls to the examples you are referring to?
Here you can find a Next.js recipe:
https://github.com/chimurai/http-proxy-middleware/blob/master/recipes/servers.md#nextjs


Moving middleware out of repo to dapr/samples

Description
Moving middleware sample out of this repo and into the dapr/samples repo
Issue reference
Fixes #512
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] The quickstart code compiles correctly
[x] You've tested new builds of the quickstart if you changed quickstart code
[x] You've updated the quickstart's README if necessary
[x] If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

Related to: https://github.com/dapr/samples/pull/94
@msfussell

You also have to edit the https://github.com/dapr/quickstarts readme file, to remove the middleware from the list and the page

@msfussell  good catch, i did this from docs but not readme itself.  thank you.

All tests pass after re-run.


文本提取器提取中文的问题

Microsoft PowerToys version
v0.62.0
Running as admin

[x] Yes

Area(s) with issue?
TextExtractor
Steps to reproduce

✔ Expected Behavior
正常识别
❌ Actual Behavior
识别中文时每个字符之间有一个空格。
Other Software
None

Thank you for your report. This is a Duplicate of another issue. Additional comments may be added there. /dup #20319


Snapshot update

Work in progress #75

[x] Add more specs to test all possible scenarios
[ ] Add usage documentation to this PR as well as make updates to the documentation including this new functionality.
[x] Self code review.

Looks like it's broke on windows as of right now.

@gantman, the appVoyer runner is for windows? That makes much more sense.
The issue is around the use of the spread operator. I'll look into windows/node limitations.

It's a problem introduced upstream in gluegun with the new table stuff.
Is Appveyor targeting < 8.6 of Node.  If so, then great.  We should have checks like this up on gluegun.

Ok, I have PR in place now.  We'll get this merged in shortly and cut a new build of gluegun.

I also have a place on this PR where I'm using the spread operator. I can make the switch to Object.assign to be safe.

Thanks for picking that up @skellock

^ having trouble actually adding a file rule.
That error message I added to your code, to identify the issue.

Also, looks like it's overwriting and not appending:

Yeah, I saw that when righting more specs this evening. I've got a fix for that but, I'm working through some test failures.

@mattathompson - cool bud!   Let me know when you want me to test again 👍

Yeah, I haven't had as much time as I'd like to work on opensorce this
week. I'll ping you when it's ready.
On Nov 29, 2017 10:27 PM, "Gant Laborde"<EMAIL_ADDRESS>wrote:

@mattathompson https://github.com/mattathompson - cool bud! Let me know
when you want me to test again 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinitered/solidarity/pull/134#issuecomment-348071903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF83KwWub59U-rgZ8AnkxZVyAM99ycN-ks5s7iCcgaJpZM4QqhGY
.

Playing around with the new functionality I've noticed one use case of interest:
Adding a rule that already exists in the solidarity file... Should we handle that? I built something to handle it w/ cli rules but, would need to extend to all of the other rules.

Just pulled latest, here's my report:
Clean up the unexpected path experience.

Forgot to specify specific: I think when someone types
solidarity snapshot cli but forgets to mention the CLI they want, we can just ask with an extra question.  "What's the name of the CLI you'd like to add a rule for?"
Forgot to specify rule:  If we get parameters that make no sense like forgetting that they need to specify the rule type -> solidarity snapshot node we should give a friendly error. "node is not a known solidarity rule.  To add a rule via snapshot you can type solidarity snapshot <rule> <item>"

Duplicates (as you already pointed out)

Specifying a CLI that already exists:   Adding CLI requirement for Ruby, works first time, I got to add a second time, and I saw Your new requirement was not added.

Specifying a PATH/FILE/DIR Rule that already exists:  Just lets me add it twice.

I think replacing would be best.
New Shell Command

need a way to add the new shell command provided in #133

This PR is starting to really shape up.  Let me know if I can help in any way 👍

Heya @mattathompson - just got back from a biz trip.  Anything I can do to help?

@GantMan, I'm working on this today. I've addressed all the issues but one so far. Currently right now if you add a duplicate you end up just having two of the same rule.
Thinking through a solution for that.

Awesome bud.  Let me know if I can help in any way.

Btw I’m presenting this lib at a meetup on the 19th! I’ll be giving you a shoutout

Travis tests have failed
Hey Matthew Thompson,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: node
Node.js: 8

@GantMan Ready for Review. Need to update the documentation but, this is good to test drive/ code review.

Travis tests have failed
Hey Matthew Thompson,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: node

npm run test:ci

><EMAIL_ADDRESS>test:ci /home/travis/build/infinitered/solidarity
> jest --ci && tslint -p .

 PASS  __tests__/schema/validateExampleSchema.ts (22.658s)
events.js:136
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:606:16)
    at Object.send (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/fork.js:24:17)
    at Farm.stopChild (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:131:11)
    at Farm.<anonymous> (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:96:10)
    at ontimeout (timers.js:466:11)
    at tryOnTimeout (timers.js:304:5)
    at Timer.listOnTimeout (timers.js:264:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:ci: `jest --ci && tslint -p .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:ci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: node

npm run test:ci

><EMAIL_ADDRESS>test:ci /home/travis/build/infinitered/solidarity
> jest --ci && tslint -p .

 PASS  __tests__/commands/help.ts (22.263s)
 PASS  __tests__/command_helpers/removeNonVersionCharacters.ts (25.062s)
 PASS  __tests__/docs/testDocs.ts (26.673s)
 PASS  __tests__/command_helpers/checkENV.ts (27.238s)
 PASS  __tests__/command_helpers/setSolidaritySettings.ts (27.055s)
 PASS  __tests__/schema/validateExampleSchema.ts (27.083s)
 PASS  __tests__/command_helpers/getLineWithVersion.ts (27.91s)
 PASS  __tests__/command_helpers/skipRule.ts (28.871s)
 PASS  __tests__/command_helpers/getSolidaritySettings.ts (32.396s)
events.js:136
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:606:16)
    at Object.send (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/fork.js:24:17)
    at Farm.stopChild (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:131:11)
    at Farm.<anonymous> (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:96:10)
    at ontimeout (timers.js:466:11)
    at tryOnTimeout (timers.js:304:5)
    at Timer.listOnTimeout (timers.js:264:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:ci: `jest --ci && tslint -p .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:ci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2017-12-21T17_07_32_845Z-debug.log

We've been getting this random failure ^ Not sure what this is about. I've seen it now twice in different tests. Have not seen it locally.

I believe it's a timeout issue.  I can increase the timeout for those tests.  I merged your code with master, will test soon.

🔥 🔥

[x] - Test that snapshot still works
[x] - Test snapshot file without file name requests file name
[x] - Test file with name does not ask for file name
[x] - Test add file to existing requirement
[x] - Test add file to new requirement
[x] - Test add cli without name
[x] - Test add cli with name
[x] - Add cli to requirement with existing name
[x] - Add env rule without name
[x] - Add environment rule
[x] - Add dir rule without name
[x] - Add dir rule with name
[x] - Add shell rule without name
[x] - Add shell rule with name

Bug
❌   Add  new shell asks for what to match against, but does not add match prop to .solidarity file
UX issues
❌   Create rule without name but do not type name when prompted (accidental enter issue) result: creates name undefined in json
❌   Add  new requirement, but do not type a name  (creates name undefined in json)
❌   When adding a shell rule, it says "What is the name of the shell you'd like to add rule for", perhaps here it should say "What is the shell command you'd like to add a rule for"
Summary
Dude, epic PR!  just a few issues to make it mergable.  Also, do you want to do the docs in this PR or a separate one?  I can help 👍

Whatever you think is best regarding the documentation! If you want to knock those out I can start on the issues you've raised.
I'm on vacation starting now so I should be able to knock these out pretty quickly.
Thanks for your review!

[ ] Add new shell asks for what to match against, but does not add match prop to .solidarity file

UX issues

[ ] Create rule without name but do not type name when prompted (accidental enter issue) result: creates name undefined in json
[ ] Add new requirement, but do not type a name (creates name undefined in json)
[ ] When adding a shell rule, it says "What is the name of the shell you'd like to add rule for", perhaps here it should say "What is the shell command you'd like to add a rule for"

Looking good so far!  👍

Travis tests have failed
Hey Matthew Thompson,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: node

npm run test:ci

><EMAIL_ADDRESS>test:ci /home/travis/build/infinitered/solidarity
> jest --ci && tslint -p .

 PASS  __tests__/commands/help.ts (18.602s)
 PASS  __tests__/command_helpers/skipRule.ts (21.114s)
 PASS  __tests__/command_helpers/removeNonVersionCharacters.ts (21.242s)
 PASS  __tests__/docs/testDocs.ts (20.717s)
 PASS  __tests__/command_helpers/getLineWithVersion.ts (21.593s)
 PASS  __tests__/command_helpers/checkENV.ts (21.539s)
 PASS  __tests__/schema/validateExampleSchema.ts (21.102s)
 PASS  __tests__/command_helpers/setSolidaritySettings.ts (27.351s)
events.js:136
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:606:16)
    at Object.send (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/fork.js:24:17)
    at Farm.stopChild (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:131:11)
    at Farm.<anonymous> (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:96:10)
    at ontimeout (timers.js:466:11)
    at tryOnTimeout (timers.js:304:5)
    at Timer.listOnTimeout (timers.js:264:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:ci: `jest --ci && tslint -p .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:ci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2017-12-23T17_43_11_652Z-debug.log

@GantMan Baring the test passes on CI all the issues have been addressed.

Travis tests have failed
Hey Matthew Thompson,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: node

npm run test:ci

><EMAIL_ADDRESS>test:ci /home/travis/build/infinitered/solidarity
> jest --ci && tslint -p .

 PASS  __tests__/command_helpers/removeNonVersionCharacters.ts (17.798s)
 PASS  __tests__/command_helpers/getLineWithVersion.ts (17.874s)
 PASS  __tests__/command_helpers/skipRule.ts (18.972s)
 PASS  __tests__/commands/help.ts (19.308s)
 PASS  __tests__/command_helpers/checkENV.ts (19.382s)
 PASS  __tests__/command_helpers/setSolidaritySettings.ts (19.165s)
 PASS  __tests__/docs/testDocs.ts (19.209s)
 PASS  __tests__/schema/validateExampleSchema.ts (20.087s)
events.js:136
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:606:16)
    at Object.send (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/fork.js:24:17)
    at Farm.stopChild (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:131:11)
    at Farm.<anonymous> (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:96:10)
    at ontimeout (timers.js:466:11)
    at tryOnTimeout (timers.js:304:5)
    at Timer.listOnTimeout (timers.js:264:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:ci: `jest --ci && tslint -p .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:ci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2017-12-23T19_56_02_003Z-debug.log

Travis tests have failed
Hey Matthew Thompson,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: node

npm run test:ci

><EMAIL_ADDRESS>test:ci /home/travis/build/infinitered/solidarity
> jest --ci && tslint -p .

 PASS  __tests__/commands/help.ts (27.775s)
 PASS  __tests__/command_helpers/setSolidaritySettings.ts (27.552s)
 PASS  __tests__/command_helpers/getLineWithVersion.ts (28.832s)
 PASS  __tests__/command_helpers/checkENV.ts (28.452s)
 PASS  __tests__/docs/testDocs.ts (27.951s)
 PASS  __tests__/command_helpers/skipRule.ts (29.485s)
 PASS  __tests__/command_helpers/removeNonVersionCharacters.ts (29.99s)
 PASS  __tests__/schema/validateExampleSchema.ts (30.672s)
events.js:136
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:606:16)
    at Object.send (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/fork.js:24:17)
    at Farm.stopChild (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:131:11)
    at Farm.<anonymous> (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:96:10)
    at ontimeout (timers.js:466:11)
    at tryOnTimeout (timers.js:304:5)
    at Timer.listOnTimeout (timers.js:264:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:ci: `jest --ci && tslint -p .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:ci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2017-12-23T20_20_14_465Z-debug.log

@GantMan, Thoughts ^ seems to be happening more frequently after adding a few more tests.

Travis tests have failed
Hey Matthew Thompson,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.
Node.js: node

npm run test:ci

><EMAIL_ADDRESS>test:ci /home/travis/build/infinitered/solidarity
> jest --ci && tslint -p .

 PASS  __tests__/command_helpers/skipRule.ts (23.052s)
 PASS  __tests__/docs/testDocs.ts (23.209s)
 PASS  __tests__/schema/validateExampleSchema.ts (23.068s)
 PASS  __tests__/command_helpers/setSolidaritySettings.ts (24.206s)
 PASS  __tests__/command_helpers/getLineWithVersion.ts (24.061s)
 PASS  __tests__/command_helpers/removeNonVersionCharacters.ts (25.784s)
 PASS  __tests__/command_helpers/checkENV.ts (26.352s)
 PASS  __tests__/commands/help.ts (26.948s)
events.js:136
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:606:16)
    at Object.send (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/fork.js:24:17)
    at Farm.stopChild (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:131:11)
    at Farm.<anonymous> (/home/travis/build/infinitered/solidarity/node_modules/worker-farm/lib/farm.js:96:10)
    at ontimeout (timers.js:466:11)
    at tryOnTimeout (timers.js:304:5)
    at Timer.listOnTimeout (timers.js:264:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:ci: `jest --ci && tslint -p .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:ci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!
We can adjust it like so:  https://github.com/infinitered/solidarity/blob/d55a791bab899ef50f210f0895b430af87b30d5b/tests/integration/solidarity-check/check-invalid.ts#L11
Or jest.setTimeout(10000); // 10 second timeout

I re-ran tests.  Looks good now!
Also did a quick local test 👍
Let's do docs in a separate PR - Let me know if you want them or if I should.

It's ALIVE!!!!

NOICE! Love me some Jurassic Park.
On Sat, Dec 23, 2017 at 11:25 PM, Gant Laborde<EMAIL_ADDRESS>wrote:

It's ALIVE!!!!
[image: noice]
https://camo.githubusercontent.com/0428042a51b7a8dabf4b079d6e37b017503d9020/68747470733a2f2f6d656469612e67697068792e636f6d2f6d656469612f52517a7841614167336141552f67697068792e676966
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinitered/solidarity/pull/134#issuecomment-353764535,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF83KwTdbiL_UgxsyOGO1lns2aOcLfJEks5tDdIngaJpZM4QqhGY
.


Add verification code to RC email

The script that generates an RC and an email gives a suggested command to download the staging repo.  If could also suggest a short script to verify sigs and hashes like the following.
for file in $(find . -type f -regex '.*\.\(pom\|jar\|gz\)'); do
  echo $file
  gpg --verify "$file".asc $file
  diff -Z "$file".md5 <(md5sum $file | cut -d ' ' -f 1)
  diff -Z "$file".sha1 <(sha1sum $file | cut -d ' ' -f 1)
done

Maybe simpler, and leaves some MD5SUM, SHA1SUM files around to manually check later:
function checkFile {
  local file; file=$1
  echo '='
  echo "$file"
  gpg2 --verify "$file".asc "$file"
  echo "$(cat "$file".md5) *$file" >> MD5SUM
  echo "$(cat "$file".sha1) *$file" >> SHA1SUM
}
export -f checkFile
rm MD5SUM SHA1SUM
#find . -type f -name '*.asc' -exec bash -c 'checkFile "$(dirname "$0")/$(basename "$0" .asc)"' {} \;
find . -type f -regex '.*\.\(pom\|jar\|gz\)' -exec bash -c 'checkFile "$0"' {} \;
md5sum --quiet -c MD5SUM
sha1sum --quiet -c SHA1SUM

The commented out find command is a little more comprehensive... it'll check all files with a detached gpg signature. The original one only checks for pom, jar, and gz files, and that may not catch everything.

Instead of putting this info in the email, we should have the email point to web page with information on how to download and verify the release.

Check out the Validating a Release section of the following page.
http://kylin.apache.org/development/howto_release.html

The commented out find command is a little more comprehensive... it'll check all files with a detached gpg signature. The original one only checks for pom, jar, and gz files, and that may not catch everything.

Only checking files with detached sig would miss file that was missing a detached sig.  For example if a jar was missing a signature for some reason.   Maybe could find the list of all files that are not sig or hash and check those.

Here's one that checks all files downloaded:
function checkFile {
  echo '='
  echo "$1"
  gpg2 --verify "$1".asc "$1"
  echo "$(cat "$1".md5) *$1" >> MD5SUM
  echo "$(cat "$1".sha1) *$1" >> SHA1SUM
}
export -f checkFile
rm MD5SUM SHA1SUM
find . -type f -not -name '*.asc' -not -name '*.md5' -not -name '*.sha1' -exec bash -c 'checkFile "$0"' {} \;
md5sum --quiet -c MD5SUM
sha1sum --quiet -c SHA1SUM

This assumes the download of the staging repo skipped webserver generated content, and maven repo content, as in:
    wget -erobots=off --no-verbose \
      --recursive --level inf --no-parent --no-host-directories \
      --reject 'index.html,maven-metadata.xml*,archetype-catalog.xml' \
      -P download \
      "$url"


8.0 release notes: missing the closing quote.

Signed-off-by: Michael J Bailey<EMAIL_ADDRESS>Fix for 8.0 release notes

@bot-gradle test and merge

I've triggered a build for you.


Fixed bug with initial size and position calculation for X11Window

What does the pull request do?
There is chicken and egg problem with position and scaling of the window on linux. To center window correctly it should know scaling, but to know scaling window should be positioned.
So I added some workaround that calls SetWindowStartupLocation twice. Not very nice but at least it works.
What is the current behavior?
On Linux in some cases window is positioned incorrectly (i.e. CenterScreen with scaling > 1)
What is the updated/expected behavior with this PR?
Window position is correct on linux

The only concern here is an extra PositionChanged even during Show.
cc: @grokys


[BEAM-5417] Parity between GCS and local match

List files recursively in order to replicate the prefix matching that
GCS does.
I think this is a minor bugfix.
Without this PR, LocalFileSystem.match(['foo/*/file.txt']) would not match foo/a/file.txt.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

@udim I see you touched LocalFileSystem._list() recently(ish) in https://github.com/apache/beam/commit/36a250615b4a5d72c80b03f8f87957b5c0aaf791. Is there a valid reason to not support foo/*/file.txt on filesystems with directories or was it just overlooked?

@udim I see you touched LocalFileSystem._list() recently(ish) in 36a2506. Is there a valid reason to not support foo/*/file.txt on filesystems with directories or was it just overlooked?

Hi @joar. I don't remember why exactly, but it was a deliberate choice: https://github.com/apache/beam/blob/b7c2975c16c2a4d3051b0ea21ef5f515a0b8d50b/sdks/python/apache_beam/io/filesystem.py#L554.
We used fnmatch.fnmatch() instead of glob.glob() to support both Unix and Windows style paths.
To fully add support for paths like foo/*/file.txt (and d:\foo\*\file.txt):

Convert * in patterns to [!/\] (see fnmatch docs, I belive this should support both Unix and Windows paths)
Convert ** in patterns to * (optional, this would be a new feature)
Document these changes

Convert * in patterns to [!/\] (see fnmatch docs, I belive this should support both Unix and Windows paths)

It seems that [!/\] only matches a single character in fnmatch:
>>> import fnmatch
>>> fnmatch.translate(r'[!\/]')
'[^\\\\/]\\Z(?ms)'

so having * matching anything except / and \ would require abandoning fnmatch it seems.

@joar
I see two options here:

Convert the glob into a regex instead. Something like: re.sub(r'\*', r'[^/\\\\]*', pattern), but it's more complicated because of special characters that need escaping. See how it's done in Java SDK: https://github.com/apache/beam/blob/279a05604b83a54e8e5a79e13d8761f94841f326/sdks/java/extensions/google-cloud-platform-core/src/main/java/org/apache/beam/sdk/util/GcsUtil.java#L155
Use Python 3's pathlib (PurePath.match()), falling back on pathlib2 in Python 2.

I'm leaning towards the second option, since it's less code to maintain and uses standard libraries in Python 3.

@udim Good call, PurePath looks like a nice place to keep the complexity.

@udim It took me too long to realize thahPurePath.match() also uses fnmatch.
Maintaining our own state machine seems to be the only remaining solution.

Unless of course we use pathlib.Path().glob() rather than PurePath().match(), and in LocalFileSystem only rather than FileSystem. I'm done for today though, I'll have to check back later.

I think I understand now what you mean. PurePath.match() doesn't support recursive (**) matching.
>>> pathlib.PurePath('gs://foo/bar/foo.txt').match('gs://*/*/*')
True
>>> pathlib.PurePath('gs://foo/bar/foo.txt').match('gs://**')
False

And glob() only works on (Python) readable paths, which limits it to LocalFileSystem.
I think that doing our own conversion of glob pattern to regex is the best solution.

I think that doing our own conversion of glob pattern to regex is the best solution.

@udim I agree, pushed a solution that uses a customized version of Python 2.7's fnmatch.translate.

Still reviewing, but FYI I have a related PR out https://github.com/apache/beam/pull/6480 that touches gcsio.py. I don't believe it conflicts with this PR.

Ah, I thought fixed that one, but I put them in the wrong order. Fixed in 2639e3

PTAL @chamikaramj

Merged. Thanks for the contribution Joar.


The uname call in Fp causes it to not be JSOO portable

I ported all of the Unix externals that the Fp library needs to JSOO assuming you're running in a nodejs environment, but with the merge of #251 the uname call was moved our of Dir and into Fp.
If that call is replaced, the Fp library can be used in nodejs again.

This was fixed in #261


[BUG]

Describe the bug
Attempting to Vote on Proposal but get non descriptive error message.
To Reproduce
Steps to reproduce the behavior:

Go to https://cast.fyi/#/community/39/proposal/114
Click on Connect wallet
Connect Blocto Wallet (0x4f8959ef27d8cd1d)
Click on Voting Choice
Click Vote
Confirm Vote
Approve Signature Request
Get Error that says "There was an error trying to complete your request." with no additional information on error. See Screenshot.

Expected behavior
Based on the rules of the vote and my wallet status, vote should be accepted.  If error, need more descriptive error message to rectify situation.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser [e.g. chrome, safari] Chrome and Edge
Version [e.g. 22] Chrome: 111 and Edge: 112

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Follow up:  I was able to vote in my Blocto Wallet browser on my phone (ios).


contribution idea

I think it would be nice to contribute to a real project. That might be hard, but some project owner might be willing to let your students implement a new feature

Thank you for this! I agree and received some good feedback from @dariusk in a similar direction. I plan on rewriting the description and outline somewhat significantly in the next week and will leave this pull request open for reference. Thank you for the contribution!

I've made some updates to the syllabus. The project proposals made mid semester can involve contributions to an existing project and this will be encouraged through exercises in the first half. Thanks for this note!


openjdk11: Revert libjvm linkage

Related to #66
Checklist

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

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

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

This is not the correct solution. We should fix r-rjava

Can you add file to yum_requirements.txt?

Seems like more things are missing but the error message is too cryptic for me.

@conda-forge-admin please rerender

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

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.


LUCENE-10507: Make it more likely to perform concurrent search in tests

I took a stab at this, these are the changes that I made:

Replace default useThreads value: rarely() -> randomBoolean()
apply lower slices thresholds more frequently: randomBoolean() -> frequently
lower maxDocsPerSlice and maxSegmentsPerSlice threshold when applied
apply lower maxSegments and maxSegmentsPerSlice also when wrapWithAssertions is true

Please let me know what you think. Would it be better to rather make one change at a time, or make less aggressive changes?

I like the idea of better exercising concurrent search. I wonder if this has potential to slow down tests due to repeated instantiations of threads. I'm inclined to merge and watch how long tests need over the coming days. http://people.apache.org/~mikemccand/lucenebench/antcleantest.html

I wonder if this has potential to slow down tests due to repeated instantiations of threads.

Yes I wonder the same, this needs some runs before we can evaluate how it affects tests duration. Some datapoint will give us an indication of whether the changes I am suggesting are too aggressively forcing concurrent searches, causing overhead.

It's also going to make tests less likely to reproduce though, isn't it?

This is my expectation as well, similarly to tests that use ConcurrentMergeScheduler.

It's also going to make tests less likely to reproduce though, isn't it?

Do you mean if there are new failures caused by running concurrent searches more often, these are going to be harder to reproduce as they are subject to timing? Though these are potentially bugs that we want to uncover?

Just wondering what the impact is going to be, that's all. Can the returned order of documents from the (parallel) searcher be different? For score-sorted cases it may not be a problem but whenever there are ties, and the assertions somehow depend on document order, things will be more problematic.

Yep I see what you mean, I've seen that in the past that some tests may rely on assumptions that are no longer true if you run the search concurrently. Some may be test bugs, that may be fixed by adapting the assertions or disabling concurrency, some actual production bugs.

Can the returned order of documents from the (parallel) searcher be different? For score-sorted cases it may not be a problem but whenever there are ties, and the assertions somehow depend on document order, things will be more problematic.

I agree this is a risk, but I would expect whether you search concurrently or serially, Lucene really should return the same top hits nomatter the query sort or docid tie-breaking etc.  But likely there are bugs lurking :)  Hopefully we catch them with this change!
The one thing I think (?) can change is the estimated total hit count if BMW kicked in.  That can change even if you search the same segments, serially, but in a different order, I think.

The one thing I think (?) can change is the estimated total hit count if BMW kicked in. That can change even if you search the same segments, serially, but in a different order, I think.

This is correct.


jsch: scpFileToServer failing on quarkus-platform test

Bug description
While releasing Camel Quarkus 3.8.0, the test below was failing on the quarkus-platform:

org.apache.camel.quarkus.component.jsch.it.JschTest.scpFileToServer(Path)

java.lang.RuntimeException: java.lang.RuntimeException: Unable to start Quarkus test resource class org.apache.camel.quarkus.component.jsch.it.JschTestResource
	at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:638)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:722)
	at java.base/java.util.Optional.orElseGet(Optional.java:364)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.lang.RuntimeException: Unable to start Quarkus test resource class org.apache.camel.quarkus.component.jsch.it.JschTestResource
	at io.quarkus.test.common.TestResourceManager$TestResourceEntryRunnable.run(TestResourceManager.java:506)

This passes fine for me. Also passed on the latest successful build on the platform 3.8.0 upgrade PR:
2024-02-27T11:33:58.8828559Z [INFO] -------------------------------------------------------
2024-02-27T11:33:58.8829246Z [INFO]  T E S T S
2024-02-27T11:33:58.8829856Z [INFO] -------------------------------------------------------
2024-02-27T11:33:59.5277277Z [INFO] Running org.apache.camel.quarkus.component.jsch.it.JschTest
2024-02-27T11:34:02.1623222Z Downloading from google-maven-central: https://maven-central.storage-download.googleapis.com/maven2/org/apache/camel/quarkus/camel-quarkus-jsch-deployment/3.8.0/camel-quarkus-jsch-deployment-3.8.0.jar
2024-02-27T11:34:02.5627466Z Downloaded from google-maven-central: https://maven-central.storage-download.googleapis.com/maven2/org/apache/camel/quarkus/camel-quarkus-jsch-deployment/3.8.0/camel-quarkus-jsch-deployment-3.8.0.jar (4.6 kB at 14 kB/s)
2024-02-27T11:34:04.8725745Z 2024-02-27 11:34:04,843 INFO  [org.tes.ima.PullPolicy] (pool-3-thread-1) Image pull policy will be performed by: DefaultPullPolicy()
2024-02-27T11:34:04.8729212Z 2024-02-27 11:34:04,845 INFO  [org.tes.uti.ImageNameSubstitutor] (pool-3-thread-1) Image name substitution will be performed by: DefaultImageNameSubstitutor (composite of 'ConfigurationFileImageNameSubstitutor' and 'PrefixingImageNameSubstitutor')
2024-02-27T11:34:05.0780556Z 2024-02-27 11:34:05,025 INFO  [org.tes.doc.DockerClientProviderStrategy] (pool-3-thread-1) Loaded org.testcontainers.dockerclient.UnixSocketClientProviderStrategy from ~/.testcontainers.properties, will try it first
2024-02-27T11:34:05.2782926Z 2024-02-27 11:34:05,179 INFO  [org.tes.doc.DockerClientProviderStrategy] (pool-3-thread-1) Found Docker environment with local Unix socket (unix:///var/run/docker.sock)
2024-02-27T11:34:05.2785780Z 2024-02-27 11:34:05,180 INFO  [org.tes.DockerClientFactory] (pool-3-thread-1) Docker host IP address is localhost
2024-02-27T11:34:05.2787976Z 2024-02-27 11:34:05,195 INFO  [org.tes.DockerClientFactory] (pool-3-thread-1) Connected to docker:
2024-02-27T11:34:05.2789319Z   Server Version: 24.0.8
2024-02-27T11:34:05.2790161Z   API Version: 1.43
2024-02-27T11:34:05.2790995Z   Operating System: Ubuntu 22.04.4 LTS
2024-02-27T11:34:05.2791588Z   Total Memory: 15981 MB
2024-02-27T11:34:05.2792826Z 2024-02-27 11:34:05,229 INFO  [tc.tes.6.0] (pool-3-thread-1) Creating container for image: testcontainers/ryuk:0.6.0
2024-02-27T11:34:05.3790367Z 2024-02-27 11:34:05,313 INFO  [tc.tes.6.0] (pool-3-thread-1) Container testcontainers/ryuk:0.6.0 is starting: 3573aedf7cad35c9701442b7edb5c60f9395ee4375ce7a56ad9ee3d613097175
2024-02-27T11:34:05.6817784Z 2024-02-27 11:34:05,644 INFO  [tc.tes.6.0] (pool-3-thread-1) Container testcontainers/ryuk:0.6.0 started in PT0.41465202S
2024-02-27T11:34:05.6820455Z 2024-02-27 11:34:05,647 INFO  [org.tes.uti.RyukResourceReaper] (pool-3-thread-1) Ryuk started - will monitor and terminate Testcontainers containers on JVM exit
2024-02-27T11:34:05.6822762Z 2024-02-27 11:34:05,648 INFO  [org.tes.DockerClientFactory] (pool-3-thread-1) Checking the system...
2024-02-27T11:34:05.6824882Z 2024-02-27 11:34:05,648 INFO  [org.tes.DockerClientFactory] (pool-3-thread-1) ✔ Docker server version should be at least 1.6.0
2024-02-27T11:34:05.6828297Z 2024-02-27 11:34:05,655 INFO  [tc.doc.io/.3_p2-r0] (pool-3-thread-1) Pulling docker image: docker.io/linuxserver/openssh-server:version-9.3_p2-r0. Please be patient; this may take some time but only needs to be done once.
2024-02-27T11:34:05.8819303Z 2024-02-27 11:34:05,845 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Starting to pull image
2024-02-27T11:34:05.8820876Z 2024-02-27 11:34:05,860 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  0 downloaded,  0 extracted, (0 bytes/0 bytes)
2024-02-27T11:34:06.0822619Z 2024-02-27 11:34:05,987 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  6 pending,  1 downloaded,  0 extracted, (966 bytes/? MB)
2024-02-27T11:34:06.0824648Z 2024-02-27 11:34:06,010 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  5 pending,  2 downloaded,  0 extracted, (5 KB/? MB)
2024-02-27T11:34:06.0826026Z 2024-02-27 11:34:06,053 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  4 pending,  3 downloaded,  0 extracted, (60 KB/? MB)
2024-02-27T11:34:06.0827384Z 2024-02-27 11:34:06,077 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  3 pending,  4 downloaded,  0 extracted, (60 KB/? MB)
2024-02-27T11:34:06.1823901Z 2024-02-27 11:34:06,135 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  2 pending,  5 downloaded,  0 extracted, (149 KB/? MB)
2024-02-27T11:34:06.1825713Z 2024-02-27 11:34:06,139 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  1 pending,  6 downloaded,  0 extracted, (152 KB/? MB)
2024-02-27T11:34:06.1827365Z 2024-02-27 11:34:06,157 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  7 downloaded,  0 extracted, (152 KB/13 MB)
2024-02-27T11:34:06.4826912Z 2024-02-27 11:34:06,391 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  7 downloaded,  1 extracted, (5 MB/13 MB)
2024-02-27T11:34:06.4829402Z 2024-02-27 11:34:06,429 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  7 downloaded,  2 extracted, (5 MB/13 MB)
2024-02-27T11:34:06.4832037Z 2024-02-27 11:34:06,440 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  7 downloaded,  3 extracted, (5 MB/13 MB)
2024-02-27T11:34:06.9833354Z 2024-02-27 11:34:06,912 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  7 downloaded,  4 extracted, (10 MB/13 MB)
2024-02-27T11:34:06.9835963Z 2024-02-27 11:34:06,940 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  7 downloaded,  5 extracted, (10 MB/13 MB)
2024-02-27T11:34:07.0834981Z 2024-02-27 11:34:07,019 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  7 downloaded,  6 extracted, (13 MB/13 MB)
2024-02-27T11:34:07.0837550Z 2024-02-27 11:34:07,034 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pulling image layers:  0 pending,  7 downloaded,  7 extracted, (13 MB/13 MB)
2024-02-27T11:34:07.0839940Z 2024-02-27 11:34:07,041 INFO  [tc.doc.io/.3_p2-r0] (docker-java-stream-841559818) Pull complete. 7 layers, pulled in 1s (downloaded 13 MB at 13 MB/s)
2024-02-27T11:34:07.0842293Z 2024-02-27 11:34:07,041 INFO  [tc.doc.io/.3_p2-r0] (pool-3-thread-1) Image docker.io/linuxserver/openssh-server:version-9.3_p2-r0 pull took PT1.386028602S
2024-02-27T11:34:07.0844643Z 2024-02-27 11:34:07,044 INFO  [tc.doc.io/.3_p2-r0] (pool-3-thread-1) Creating container for image: docker.io/linuxserver/openssh-server:version-9.3_p2-r0
2024-02-27T11:34:07.0847483Z 2024-02-27 11:34:07,056 INFO  [tc.doc.io/.3_p2-r0] (pool-3-thread-1) Container docker.io/linuxserver/openssh-server:version-9.3_p2-r0 is starting: 2c77c2685146a7581444f03e2fe2360c43717205c9da4b383da0ddd6732f97ee
2024-02-27T11:34:09.8869222Z 2024-02-27 11:34:09,854 INFO  [tc.doc.io/.3_p2-r0] (pool-3-thread-1) Container docker.io/linuxserver/openssh-server:version-9.3_p2-r0 started in PT2.810370729S
2024-02-27T11:34:10.4876235Z 2024-02-27 11:34:10,406 INFO  [org.apa.cam.qua.cor.CamelBootstrapRecorder] (main) Bootstrap runtime: org.apache.camel.quarkus.main.CamelMainRuntime
2024-02-27T11:34:10.4878590Z 2024-02-27 11:34:10,408 INFO  [org.apa.cam.mai.MainSupport] (main) Apache Camel (Main) 4.4.0 is starting
2024-02-27T11:34:10.4880643Z 2024-02-27 11:34:10,461 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.4.0 (camel-1) is starting
2024-02-27T11:34:10.4882869Z 2024-02-27 11:34:10,468 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Routes startup (started:0)
2024-02-27T11:34:10.4885739Z 2024-02-27 11:34:10,468 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.4.0 (camel-1) started in 4ms (build:0ms init:0ms start:4ms)
2024-02-27T11:34:10.5806993Z 2024-02-27 11:34:10,560 INFO  [io.quarkus] (main) camel-quarkus-integration-test-jsch 999-SNAPSHOT on JVM (powered by Quarkus 3.8.0) started in 7.661s. Listening on: http://localhost:8081
2024-02-27T11:34:10.5809559Z 2024-02-27 11:34:10,561 INFO  [io.quarkus] (main) Profile test activated.
2024-02-27T11:34:10.5811945Z 2024-02-27 11:34:10,561 INFO  [io.quarkus] (main) Installed features: [camel-core, camel-file, camel-ftp, camel-jsch, cdi, jsch, resteasy, smallrye-context-propagation, vertx]
2024-02-27T11:34:11.8893451Z 2024-02-27 11:34:11,878 WARN  [org.apa.cam.com.scp.ScpOperations] (executor-thread-1) Private Key authentication not supported
2024-02-27T11:34:11.8902156Z 2024-02-27 11:34:11,878 WARN  [org.apa.cam.com.scp.ScpOperations] (executor-thread-1) Private Key authentication not supported
2024-02-27T11:34:11.8904706Z 2024-02-27 11:34:11,878 WARN  [org.apa.cam.com.scp.ScpOperations] (executor-thread-1) Private Key authentication not supported
2024-02-27T11:34:11.8906823Z 2024-02-27 11:34:11,878 WARN  [org.apa.cam.com.scp.ScpOperations] (executor-thread-1) Private Key authentication not supported
2024-02-27T11:34:11.8908988Z 2024-02-27 11:34:11,878 WARN  [org.apa.cam.com.scp.ScpOperations] (executor-thread-1) Private Key authentication not supported
2024-02-27T11:34:11.9894808Z 2024-02-27 11:34:11,950 WARN  [org.apa.cam.com.scp.ScpComponent] (executor-thread-1) [JSCH] getInputStream() should be called before connect()
2024-02-27T11:34:12.2547613Z [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.717 s - in org.apache.camel.quarkus.component.jsch.it.JschTest
2024-02-27T11:34:12.3933558Z 2024-02-27 11:34:12,258 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.4.0 (camel-1) is shutting down (timeout:45s)
2024-02-27T11:34:12.3936261Z 2024-02-27 11:34:12,260 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Routes stopped (stopped:0)
2024-02-27T11:34:12.3938334Z 2024-02-27 11:34:12,262 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.4.0 (camel-1) shutdown in 3ms (uptime:1s)
2024-02-27T11:34:12.3940286Z 2024-02-27 11:34:12,276 INFO  [io.quarkus] (main) camel-quarkus-integration-test-jsch stopped in 0.029s```


Monitor Implementation

https://github.com/pegnet/pegnet/blob/4b9d0d5f72dcdf5105415560519d7007d564ae29/common/monitor.go#L13
Two observations:

The monitor is never stopped
There's only one monitor instance that runs single threaded.

It is possible to just make it a singleton.
There's a lot of superfluous functionality (like stopping) and mutex juggling. I don't think mutexes are even necessary in this case, since the info struct is just swapped out with a new one but there are no goroutines that write data to the fields itself.
Is the stop functionality ever needed in theory? The only instance I can think of is if you hotswap the factomd connection during runtime to a different node that potentially has difference issues with directoryblockheights, but that seems a far fetched scenario.
Any objections to a slight of this file to reduce mutexes?

Support this. Could certainly do with a trim.
Was originally pulling from the struct to serve up stats but the data is duplicated elsewhere and much more accessible.

closing this issue since the pr was merged. thanks everyone!


cmd/skopeo: show full help on 'copy' with no args

Signed-off-by: Vincent Batts<EMAIL_ADDRESS>

LGTM

LGTM


Not able to register on Stackstorm slack channel

I have registered with email id:--<EMAIL_ADDRESS>but didn't get any invite yet. I want to ask a question where my action file is on path /opt/stackstorm/packs/examples/actions but still while creating the action it is getting registered in default instead of examples. please help

Look at the action metadata file. Does it have a line that contains something like pack: <pack>? If so, is it the correct pack name? If it does not exist, or is the wrong name, then change it.

Also, Slack shows that you signed up on Mar 16, 2017. If you have forgotten your password, Slack has procedures for resetting your password.


[docs] Update Workspaces/Environment

Notes for Reviewers
Updates docs for environments/workspaces.
This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit 9c78c398e1f5bdc7124ccb0582735fd467b594b8 at: https://653b57d4783fbf1994571dff--meshery-docs-preview.netlify.app


Default value of properties should be None

The default value of StructureData properties should be None. However, default properties for each site should be default ones. In this way, we can always access a given property for each site.
I will still keep always stored masses, for now. However we can always have a 1-to-1 mapping from symbols...
to summarize:

[x] This means that if a given properties is provided in the site list way of providing input, and is the default value for each site, it will be not stored in the structure.properties but only under the sites. So, it will not be stored in the db (we avoid unnecessary storing of stuff and we can search for given structure with/without a given prop);
[x]  This means that default values which are ignored in the structure properties will not be stored in the database. This means that we avoid unnecessary/unwanted store of properties;
[x] Define the above behaviour in the documentation; list of properties which are never in the db;
[x] tests

Fixed in https://github.com/mikibonacci/aiida-atomistic/pull/7


Unconfirmed tx information is not being displayed

I only see a blank screen whenever I click on an unconfirmed tx. I spoke with @wy who said the remote node should be called to retrieve the tx info.
Below is a selected unconfirmed tx:

This shows the blank screen that is displayed corresponding to the unconfirmed tx:

Thanks, I will investigate on this

Hey there it looks like this is working now! @wy prompted me to check after the point release. Good work!
Only other comment was that it was not immediately obvious to me that it was working because I looked on my phone and the tx return is below the unconfirmed list so you have to know to scroll down to it. But that is just my opinion. Keep up the go

Looks there is still some issues, will look into it more

Can you investigate node 585 @i25959341 , looks like it is working fine with other nodes but 585 isn't returning.

API response is showing:

        <meta http-equiv="content-type" content="text/html;charset=utf-8">
        <title>502 Server Error</title>

Error: Server Error

The server encountered a temporary error and could not complete your request.

Please try again in 30 seconds.

I think it might be because of this:
requests.exceptions.SSLError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=10331): Max retries exceeded with url: / (Caused by SSLError(CertificateError("hostname '<IP_ADDRESS>' doesn't match either of 'switcheo.network', '*.switcheo.network'",),))

This is node 585
requests.exceptions.SSLError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=10331): Max retries exceeded with url: / (Caused by SSLError(CertificateError("hostname '<IP_ADDRESS>' doesn't match either of 'switcheo.network', '*.switcheo.network'",),))

Fixed #93


[Windows] Unable to build with the MinGW compiler and CMake

I'm using standalone MinGW (winlibs.com), not MSYS2. This is the error message:
C:/Work/Melon/include/mln_alloc.h:13:10: fatal error: 'sys/mman.h' file not found
   13 | #include <sys/mman.h>
      |          ^~~~~~~~~~~~
1 error generated.

MinGW64 is no longer supported on Windows.


Polyglot Notebook: Using set for JavaScript doesn't work, but does work for C#

Describe the bug
Using extension Polyglot Notebook in VS Code
When wanting the variable value from a previous cell, I should be able to retrieve it using #!set
Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

OS

[ ] Windows 11
[x] Windows 10
[ ] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[x] Edge
[ ] Firefox
[ ] Safari

Frontend

[ ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[x] Visual Studio Code
[ ] Visual Studio Code Insiders
[ ] Visual Studio
[ ] Other (please specify)

Actions to repeat

Create cell with JavaScript kernel

Give it the following content:
let jsname = "chris";
jsname

Create another cell below with same kernel and give it the following content:
#!set --value @javascript:jsname --name jsname2

console.log("Hello", jsname2);

This renders "Hello null"
Note: works as intended using C#

Screenshots

the problem is that for variables to be sharable from js they must be global declarations, the use of var, let, and const will cause them to be in the scope of the submission only.
This code will work
jsname = "chris";
jsname

#!set --value @javascript:jsname --name jsname2

console.log("Hello", jsname2);

side by side case

@colombod many thanks for this explanation


python virtual environment not activating even when code . launched from a terminal where virtual environment is activated

Steps to reproduce the problem:

Fresh install of VS Code on a Mac. All past settings and extensions deleted before fresh install. Fresh install of Python extension.
Launched VS Code using code . from a folder where python virtual environment is activated. Virtual environment exists in .venv directory in that folder. Virtual environment was created using python3 -m venv .venv. which python3 results in .../.venv/bin/python3
However, when VS Code launches it cannot find the virtual environment. And this is the output - pasted below.

Any suggestions as to how this can be avoided?
Thank you!
2024-03-31 13:47:38.456 [info] Experiment 'pythonRecommendTensorboardExt' is active
2024-03-31 13:47:38.456 [info] Experiment 'pythonREPLSmartSend' is active
2024-03-31 13:47:38.456 [info] Experiment 'pythonSurveyNotificationcf' is active
2024-03-31 13:47:38.456 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2024-03-31 13:47:38.456 [info] Experiment 'pythonTestAdapter' is active
2024-03-31 13:47:38.478 [info] Default formatter is set to null for workspace /Users/user1/Documents/python_project
2024-03-31 13:47:38.483 [info] VS Code was launched from an activated environment: '.venv', selecting it as the interpreter for workspace.
2024-03-31 13:47:38.484 [info] Test server listening.
2024-03-31 13:47:38.486 [warning] Failed to check if .venv is an executable [Error: ENOENT: no such file or directory, lstat '.venv'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'lstat',
  path: '.venv'
}
2024-03-31 13:47:38.623 [warning] Failed to check if .venv is an executable [Error: ENOENT: no such file or directory, lstat '.venv'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'lstat',
  path: '.venv'
}
2024-03-31 13:47:38.628 [info] > .venv -c "import sys;print(sys.executable)"
2024-03-31 13:47:38.637 [error] [Error: Command failed: .venv -c "import sys;print(sys.executable)"
/bin/sh: .venv: command not found

	at ChildProcess.exithandler (node:child_process:420:12)
	at ChildProcess.emit (node:events:526:35)
	at maybeClose (node:internal/child_process:1091:16)
	at Socket.<anonymous> (node:internal/child_process:449:11)
	at Socket.emit (node:events:514:28)
	at Pipe.<anonymous> (node:net:323:12)] {
  code: 127,
  killed: false,
  signal: null,
  cmd: '.venv -c "import sys;print(sys.executable)"'
}
2024-03-31 13:47:38.650 [info] > .venv -I ~/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/interpreterInfo.py
2024-03-31 13:47:38.653 [error] [Error: Command failed: .venv -I /Users/user1/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/get_output_via_markers.py /Users/user1/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/interpreterInfo.py
/bin/sh: .venv: command not found

	at ChildProcess.exithandler (node:child_process:420:12)
	at ChildProcess.emit (node:events:526:35)
	at maybeClose (node:internal/child_process:1091:16)
	at Socket.<anonymous> (node:internal/child_process:449:11)
	at Socket.emit (node:events:514:28)
	at Pipe.<anonymous> (node:net:323:12)] {
  code: 127,
  killed: false,
  signal: null,
  cmd: '.venv -I /Users/user1/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/get_output_via_markers.py /Users/user1/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/interpreterInfo.py'
}
2024-03-31 13:47:39.486 [info] Starting Pylance language server.
2024-03-31 13:47:40.660 [info] > .venv -I ~/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/interpreterInfo.py
2024-03-31 13:47:40.665 [error] [Error: Command failed: .venv -I /Users/user1/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/get_output_via_markers.py /Users/user1/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/interpreterInfo.py
/bin/sh: .venv: command not found

	at ChildProcess.exithandler (node:child_process:420:12)
	at ChildProcess.emit (node:events:526:35)
	at maybeClose (node:internal/child_process:1091:16)
	at Process.onexit (node:internal/child_process:302:5)] {
  code: 127,
  killed: false,
  signal: null,
  cmd: '.venv -I /Users/user1/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/get_output_via_markers.py /Users/user1/.vscode/extensions/ms-python.python-2024.2.1/pythonFiles/interpreterInfo.py'
}
2024-03-31 13:48:12.313 [error] Cannot trigger test discovery as a valid interpreter is not selected

Ok - I learnt that the issue was how direnv was activating the virtual environment for me.
I changed the virtual environment function to use source .venv/bin/activate.
And once that was done, VS Code launched with the right virtual environment.
Closing the issue. Thank you.


doctl: 1.5.0 -> 1.7.2

Motivation for this change
Update doctl to latest release.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

could you have a look @siddharthist ?

@GrahamcOfBorg build doctl

Success on aarch64-linux (full log)
Attempted: doctl
Partial log (click to expand)
/nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/github.com/spf13/pflag/verify/gofmt.sh: interpreter directive changed from "/bin/bash" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/bash"
/nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/github.com/spf13/pflag/verify/golint.sh: interpreter directive changed from "/bin/bash" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/bash"
/nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/golang.org/x/sys/plan9/mkall.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/bash"
/nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/golang.org/x/sys/plan9/mkerrors.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/bash"
/nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/golang.org/x/sys/plan9/mksysnum_plan9.sh: interpreter directive changed from "/bin/sh" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/sh"
/nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/golang.org/x/sys/unix/mkall.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/bash"
/nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/golang.org/x/sys/unix/mkerrors.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/bash"
/nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/google.golang.org/appengine/internal/regen.sh: interpreter directive changed from "/bin/bash -e" to "/nix/store/3gg2p6n4kv2f0lsxd41f5iz1ivkbzyzr-bash-4.4-p19/bin/bash -e"
checking for references to /build in /nix/store/inz27h5ynmf1vz7zzj7g2mn41my69z7s-doctl-1.7.2...
/nix/store/4w9f63vwamc8znrhlv5crw156c4vhl5f-doctl-1.7.2-bin

Success on x86_64-linux (full log)
Attempted: doctl
Partial log (click to expand)
/nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/golang.org/x/sys/plan9/mksysnum_plan9.sh: interpreter directive changed from "/bin/sh" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/sh"
/nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/golang.org/x/sys/plan9/mkerrors.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/golang.org/x/sys/plan9/mkall.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/google.golang.org/appengine/internal/regen.sh: interpreter directive changed from "/bin/bash -e" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash -e"
/nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/github.com/spf13/pflag/verify/gofmt.sh: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/github.com/spf13/pflag/verify/all.sh: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/github.com/spf13/pflag/verify/golint.sh: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2/share/go/src/github.com/digitalocean/doctl/vendor/github.com/golang/protobuf/types/regen.sh: interpreter directive changed from "/bin/bash -e" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash -e"
checking for references to /build in /nix/store/a8yxx8hphrp3bqvvglmk20k878h26gza-doctl-1.7.2...
/nix/store/w4qqpznpzm4kd2njwpgbvp37hqbnz9z7-doctl-1.7.2-bin

Thanks!


Disable the repo wiki

Since the docs are located elsewhere this repo's empty wiki should be disabled.

Done!


WIP Added option to return prep-file output paths w/study id.

Output is one line per file, w/study id in parentheses. (Easily readable by human or machine).

Unit-tests forthcoming

@antgonza ready for review!


[SPARK-21318][SQL]Improve exception message thrown by lookupFunction

What changes were proposed in this pull request?
The function actually exists in current selected database, and it's failed to init during lookupFunciton, but the exception message is:
This function is neither a registered temporary function nor a permanent function registered in the database 'default'.

This is not conducive to positioning problems. This PR fix the problem.
How was this patch tested?
Exists tests + manual tests

cc @liancheng

Can one of the admins verify this patch?

@stanzhai Could you please add test cases?

ok to test

Test build #80295 has started for PR 18544 at commit 373fc5c.

Test build #80295 has finished for PR 18544 at commit 373fc5c.

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

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

Merged build finished. Test FAILed.

Jenkins, retest this please

Test build #80309 has started for PR 18544 at commit 373fc5c.

Test build #80309 has finished for PR 18544 at commit 373fc5c.

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

Merged build finished. Test FAILed.

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

Test build #80392 has started for PR 18544 at commit bb454b1.

Test build #80393 has started for PR 18544 at commit 9fa7078.

@gatorsmile
Some test cases have been added.
Thanks for reviewing.

Test build #80392 has finished for PR 18544 at commit bb454b1.

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

Merged build finished. Test FAILed.

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

Test build #80393 has finished for PR 18544 at commit 9fa7078.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class BaseReadWrite(object):
class MLWriter(BaseReadWrite):
class MLReader(BaseReadWrite):
class DefaultParamsWritable(MLWritable):
class DefaultParamsWriter(MLWriter):
class DefaultParamsReadable(MLReadable):
class DefaultParamsReader(MLReader):
               \"class name

Merged build finished. Test FAILed.

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

Test build #80474 has started for PR 18544 at commit c41475e.

Test build #80474 has finished for PR 18544 at commit c41475e.

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

Merged build finished. Test FAILed.

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

ping @stanzhai

Hi @gatorsmile , I've added some test cases, and passed on my machine.

retest this please

Test build #83134 has started for PR 18544 at commit c41475e.

Test build #83134 has finished for PR 18544 at commit c41475e.

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

Merged build finished. Test FAILed.

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

The failures are related to the changes you made here. Could you fix them? Thanks!

Test build #83178 has started for PR 18544 at commit 95a946e.

fixed @gatorsmile . retest this please

Test build #83178 has finished for PR 18544 at commit 95a946e.

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

Merged build finished. Test PASSed.

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

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

retest this please

Test build #92774 has started for PR 18544 at commit 95a946e.

cc @stanzhai Could you address my above comments? Thanks!

Test build #92786 has started for PR 18544 at commit 9a38fcf.

Test build #92774 has finished for PR 18544 at commit 95a946e.

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

Merged build finished. Test PASSed.

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

Test build #92786 has finished for PR 18544 at commit 9a38fcf.

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/92786/
Test PASSed.

Merged build finished. Test PASSed.

Test build #92800 has started for PR 18544 at commit b615d02.

Test build #92800 has finished for PR 18544 at commit b615d02.

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

Test build #92840 has started for PR 18544 at commit 2446e73.

cc @gatorsmile Addressed. Review this please. Thanks!

Test build #92840 has finished for PR 18544 at commit 2446e73.

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

Merged build finished. Test FAILed.

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

Test build #93101 has started for PR 18544 at commit dfa6a9e.

Test build #93101 has finished for PR 18544 at commit dfa6a9e.

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

Merged build finished. Test PASSed.

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

cc @gatorsmile changes in sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala has been reverted.

@stanzhai Could we just fix it by changing failFunctionLookup?

It's not reasonable, failFunctionLookup throws NoSuchFunctionException.
The function actually exists in current selected database, we should throw the exception which is due to an initialization failure, but not NoSuchFunctionException.

what's the status here?

@stanzhai ping

Test build #96177 has started for PR 18544 at commit ac53d6a.

The issue has been addressed a long time ago @cloud-fan @maropu

@cloud-fan
User's hive UDFs are registered in externalCatalog which not exists in functionRegistry.
It will throws a NoSuchFunctionException when an exception is encountered while loading a hive UDF.
But we should throw the original exception.
So, I just fix the issue by:
if (functionRegistry.functionExists(funcName)) {
  throw error
} else {
  ...
}

changed to:
if (super.functionExists(name)) {
  throw error
} else {
  ...
}

The following is implementation of super.functionExists
def functionExists(name: FunctionIdentifier): Boolean = {
  val db = formatDatabaseName(name.database.getOrElse(getCurrentDatabase))
  requireDbExists(db)
  functionRegistry.functionExists(name) ||
    externalCatalog.functionExists(db, name.funcName)
}

Test build #96422 has started for PR 18544 at commit 6f12ad6.

Test build #96424 has started for PR 18544 at commit 9f07557.

LGTM

Test build #96422 has finished for PR 18544 at commit 6f12ad6.

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

Merged build finished. Test PASSed.

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

Test build #96424 has finished for PR 18544 at commit 9f07557.

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

Merged build finished. Test PASSed.

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

Test build #96478 has started for PR 18544 at commit 53dc155.

Test build #96479 has started for PR 18544 at commit 623b282.

Test build #96479 has finished for PR 18544 at commit 623b282.

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

Merged build finished. Test PASSed.

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

thanks, merging to master/2.4!
Thanks for your patience! This PR is open for over a year 😂


Fixes for type mismatch, prototypes, and potential memory leak

These 22 commits are mainly to fix minor issues, such as type mismatch like (const char *) vs (char *) to make the bmd WARNS=6 clean.  However, the following two are substantial bug fixes:

del_var() does not release the specified element,
group, owner, and md_unit can hold a negative value to represent nonexistence while they are declared as unsigned types.  Conditionals like “if (group == -1)” make no sense.

Note that issues involving alignment constraints (in 496829f) were not fixed properly.  This should be revisited.

Thanks for reviewing my code. I understand the issues and merge your commits!


Neater systems adding

As the previous README.md stated, we possibly want Neater systems adding.
I'm currently satisfied with the way Systems are added, so if @paked can either clarify or close the issue, that'd be great. :-)

This was before we had the current model!


[FEAT] /redo

I looked at the code
303                elif command == "revert" OR "redo":
and later
elif command == "redo":
action=action
goto 343 //you might have to make a function out of that part, but you get what i mean.
Sorry i can't really code in python, but this pseudo code should be easy to implement for real.
Sometime the AI come up with crazy story line, it would be convenient to cancel it and redo the same action with a single command.

Agreed. AI Dungeon does not make it easy to undo the last response (/revert) and then resubmit the same text.

Thank you.


bump cosmos iavl for v16.x

backport of #826 (origin offer matt) -> v16 release branch
running on my testnet valiadtor & mainnet rpc nodes now

golanglint failure is due to an updated lint check in the latest version, this is fixed in v17 but did not apply to v16 at the time. Leaving unchanged

tested on my node, not consensus breaking ✅


feat(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1608

Questions ?
Please refer to the Backport tool documentation


Support Amazon S3 Infrequent Access Storage

Output of restic version
restic 0.3.2 (v0.3.2-4-gb0997d0)
compiled with go1.7 on linux/amd64

Hi,
It would be great if restic supports S3 Infrequent Access Storage.
https://aws.amazon.com/s3/faqs/#sia_anchor
There is a huge price difference between Standard Storage and Infrequent Access Storage. If I read correctly this setting valid for per object and not per bucket.

You can directly PUT into Standard – IA by specifying STANDARD_IA in the x-amz-storage-class header.

Thank you,
Mihaly

Thanks for the suggestion!

You can set a lifecycle policy in your S3 bucket in the new S3 console.  You would want to have it automatically move files that have not been accessed in 30 days to 'Infrequent Access'.  Per the documentation 'There is a retrieval fee associated with STANDARD_IA objects which makes it most suitable for infrequently accessed data'.  So you would not want to do this to all files as it would get pricey if your indexes were in IA and you were paying to access them every backup for example.

@sedlund

move files that have not been accessed in 30 days to 'Infrequent Access'.

This is since the date is it stored and not since last accessed.
https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html#lifecycle-config-conceptual-ex4

Transition objects to the STANDARD_IA storage class 30 days after creation.

Be able to set this STANDARD_IA should only be done to the objects that are really infrequent. The files that are accessed frequently restic should not set the flag.

My understanding is since Restic v0.8 there is a local cache of the indexes stored on S3, so the indexes probably aren't going to be downloaded and used regularly.
You can set a lifecycle policy that applies only to data files as per this example.
If you have a bucket that contains a restic backup you should use a prefix
data/
If you have a bucket with a subfolder called "PhotosBackup" that has a restic backup inside the prefix would be
PhotosBackup/data/
With this information it's fairly simple to have S3 change data files to IA class, leaving indexes and everything else standard class.
Costs
Assumptions (I don't know Restic internals at all):

Files on S3 are immutable. Once a file is uploaded it's never changed (why would you when you have the source file?)
We're not restoring data regularly. If you are then then there will be extra costs.

S3 standard currently costs $0.023 per GB, S3-IA costs $0.0125 per GB. Transitions to IA class cost $0.01 per 1,000 requests. You can go to single IA but the saving isn't great and you lose reliability. Glacier storage class is 1/3 the price of S3IA, but it takes a few hours to retrieve the files, they're in cold storage - I'm not sure how practical that is. I'm interested in comments though, as it would make this a lot cheaper.
If you have 1TB of data that's going to be around 100,000 files. S3 standard is $23.56 per month, IA $12.80. Transitioning 1M objects costs $10. So even in your first month you come out ahead, and in a year you save around $120 by using IA class.
If you can use Glacier class it'd be $4.10 per month. As above I'm not sure if that's going to work with Restic.

Hi
I am using lifecycle policies to move data from S3 to Glacier.
I have setup permissions so that my account can access both S3 and Glacier.
The data now backed up with restic has been moved to Glacier.
I try to list snapshots though get this error:
[user@server ~]$ restic list snapshots
Load(<key/3039516f24>, 0, 0) returned error, retrying after 696.958435ms: The operation is not valid for the object's storage class

Does restic support restoring data after it's been moved from S3 to Glacier?

You can't read data from glacier, you need to restore it to S3 first.
On Mon, Jul 30, 2018, 14:55 Douglas Duckworth<EMAIL_ADDRESS>wrote:

Hi
I am using lifecycle policies to move data from S3 to Glacier.
I have setup permissions so that my account can access both S3 and Glacier.
The data now backed up with restic has been moved to Glacier.
I try to list snapshots though get this error:
[user@server ~]$ restic list snapshots
Load(<key/3039516f24>, 0, 0) returned error, retrying after 696.958435ms: The operation is not valid for the object's storage class
Does restic support restoring data after it's been moved from S3 to
Glacier?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/restic/restic/issues/706#issuecomment-408853337, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAiCg-xtLtE7FxQsPwMQiLz4so0pNvypks5uLwJPgaJpZM4LS7Wt
.

Thanks @rickard-von-essen though how can I make restic backup still work?
It looks like a file called config while folder called snapshots was moved from S3 to Glacier.
Do I need to ensure these are never moved out of S3?

@tomwaldnz depends on you need, for me this is the offsite copy of a site backup solution so it very  unlikely I ever need it unless there is a break-in or the house burns down.

@rickard-von-essen what I do for that situation is every six months I zip up my new or changed files and store them directly in Glacier. I keep the much smaller set of "recently changed" files in a backup system stored on S3 in IA class. It's more manual, but it's not so bad.
I suspect to use the S3 Glacier class would probably require Restic to support it directly, setting storage classes on upload with defined lifecycle polices.

A new feature that could be helpful is AWS S3 Auto Tiering. In short, any objects not accessed within 30 days are moved to infrequent access class. You can have a lifecycle rule modify the storage class to intelligent tiering on upload - it may take a few hours.
To move objects to Glacier storage class you still need a lifecycle rule. If you need to restore your data it will take a day or so to be ready, and I've never done it so not sure how difficult it us. I tend to just use Glacier directly for that archiving.
Glacier Deep Archive is another new feature that will let you store data for $1 / TB / month. It's not available quiet yet, check for that later this year. I don't know if S3 will support it or if you'll have to use Glacier directly. Restic won't work with Glacier, Glacier is a tape backup replacement and is a bit fiddly.


bug: Menu opens behind cards

What version of daisyUI are you using?
Since 3.0.1
Describe your issue
Before version 3 the menu would be the top most layer. Since version 3 the menu now appears behind my stack of cards.
EG:
-> Navbar with dropdown, center logo and icon
-> flex (Card with image overlay) x n
I can see the drop-down menu (text) between the spaces in the cards.
Is there a simple work around?
If you can't see the problem I will attempt to knock up a simple example, the menu is heavily embedded in my code so I will need to create something from scratch.
Thanks.

What browsers are you seeing the problem on?
All browsers
Reproduction URL (optional)
No response

Duplicate of https://github.com/saadeghi/daisyui/issues/1948#issuecomment-1581632158


[ Tizen7.0 ] Include some headers in -dev header for neuralnet.h

In the previous PR (77e56f1), neuralnet.h was included in dev package.
However, some headers were missing used in nueralnet.h
This PR adds headers which have dependencies with neuralnet.h
This version is tested; It supports ReinforcementLearning example app on Tizen7.0

Self evaluation:
Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2731. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


removed spurious MPI var definitions in non MPI cygnets

@Halolegend94 , if you like it, feel free to go ahead in approving and merging.

@dipietrantonio closing this one