[APPM-1228] Proxy port is not pickedup when generating URLs on server startup

When starting the server with proxy ports it should be appended to the URLs not the default port. When publisher store URLs are generated on server startup proxy port is not appended. Refer the following segment.   INFO - StartupFinalizerServiceComponent Server : WSO2 App Manager-1.1.0 [2015-12-22 17:02:51,275] INFO - StartupFinalizerServiceComponent WSO2 Carbon started in 46 sec [2015-12-22 17:02:51,571] INFO - CarbonUIServiceComponent Mgt Console URL : https://app11.wso2.com:9443/carbon/ [2015-12-22 17:02:51,571] INFO - CarbonUIServiceComponent APP Publisher Default Context : http://app11.wso2.com:9763/publisher [2015-12-22 17:02:51,571] INFO - CarbonUIServiceComponent APP Store Default Context : http://app11.wso2.com:9763/store   Reference: https://wso2.org/jira/browse/APPM-1228

Tested on the clustered set up iot 3.1.0. Issue did not appear, hence closing the issue.


docs: update readme

change examples to reflect the 1.0.0-alpha api
enumerate any constraints:

max transfer size
max number of files to transfer
network limitations (e.g. no hole punching yet)

some perf #s?

outdated


Climate card not working on mobile app

Current Behavior
Shows a custom element does not exist error. It works on web though
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- OS: IOS
- Node:
- Version:
- Hassio:

Anything else?
No response

Duplicate https://github.com/piitaya/lovelace-mushroom/issues/621

I have the same issue where it works fine on the browser but got error on the APP (iPhone and Fire HD).
Error:
Custom element doesn't exist: mushroom-climate-card.
Already tried your recomendation about removing it from resources, deleting the files and then installing it again with no luck.

I also have this issue on android.


WIP: test

Signed-off-by: Mohamed Mahmoud<EMAIL_ADDRESS>Thanks for sending a pull request! A few things before we get started:

If this is your first time, please read the contributing guide
For non-trivial pull requests, please file an
issue first, and get
agreement that the change is a good idea, and a general guideline
for how it should be implemented, before sending code. Large PRs
that weren't first discussed and agreed upon in an issue won't be
accepted.
If the PR fixes a particular bug, please include the words "Fixed
#" in the PR text, so that the bug auto-closes when
the PR is merged.

/hold


fuge & docker-compose

Mind elaborating on what fudge gives us over docker-compose?

I see that I can just node rather than docker which is significant.
Interactive shell  is nice, but I can use docker ps and tail ect ....

This is not dogging fuge, just a newb getting up to speed.

Its much faster not running docker builds all the time for node services, and the auto restarts within fuge are awesome.
The shell gives you access to additional dev tooling such as the debug and profile commands. This is quite powerful when developing & hunting bugs, to just pick one of your services, turn it off and restart it in debug or profiling mode.
In the end, if developing with a few node.js services, I like using this as a quick service runner/tool.

On the case of deployment, I'm not really able to comment on fuge's deployment capabilities, as I have only ever wanted to use it for dev. Deployment is a separate beast completely - I don't deploy with docker-compose, I have services deployed in a kubernetes cluster with the config that entails. Another fancy tool for the same job, eh? 😆
I'm sure others can chime into this converation and correct me where I'm wrong, I haven't dived in much deeper than the shell commands listed in the readme 😄

Thanks for the discussion. It is definitely helpful. I think I will try to use some of fuge in Docker Compose so that I can control other services such as Redis all together.

Hey @tomdavidson - yes fuge is 100% a development tool. The aim is to provide a rapid development shell for microservices. Yes you can use docker compose to do this as well but we wanted a tool that was oriented to development only particularly as we will be expanding on some of the other aspects of fuge over the coming months  - for example template service generation.


[VS Code] The collaboration session expired. Please sign in and try again.

%0A%0A%23%23 Error:%0AThe collaboration session expired. Please sign in and try again.%0A%0A%23%23 Steps to Reproduce:%0A1.%0A2.%0A%0A||Version Data|%0A|-:|:-|%0A|**extensionName**|VSLS|%0A|**extensionVersion**|1.0.311|%0A|**protocolVersion**|2.2|%0A|**applicationName**|VSCode|%0A|**applicationVersion**|1.34.0|%0A|**platformName**|MacOS|%0A|**platformVersion**|18.5.0|

Hey @pableco, thanks for the feedback! Could you provide more information for us to investigate? Can you share logs with us? (>Live Share: Export Logs command)
Thanks!

@drazenp thanks for the logs! Can you elaborate on what caused this(or when did you see that) and is signing in again really helps?

@pableco @drazenp Can you confirm if you had the collaboration session open for a long time (over 20 days) before hitting this issue?

Closing due to inactivity.


Add upload function for 3dat workload

Add upload function in 'Workload Args' of frontend, mainly support for the 3DHuman-Pose-Estimation workload.
This upload function only display when 3DHuman-Pose-Estimation workload selected.

After uploaded it will be renamed and stored in the backend/workspace/media folder, and generate video download info into Workload Parameters (only available when video files exist).

We need to update the documentation "doc/CN/Workload自动部署和测试工具使用指南/Workload自动部署和测试工具使用指南.md"
If user choose workload "3DHuman", need to upload the Video

Let's close this PR and commit to internal repo, after completed Intel SDL process, then we can release to this repo.


Support order of steps

I edited the workflow, and in a separate commit renamed my configuration file. The commit that renamed my configuration file made my solution technically correct, but the exercise didn't trigger grading because there wasn't a change to the workflow. Here's the commit history.

I think it's still a push, may just have a different path!


🍢✨ Allow using classified names for rendering hooks (Bold & bold / GiphyEmbed & giphy-embed)

This adds a nicety to the HIR renderer so you can use the classified version of the type (it also enforces a lowercase convention that @blaine and I discussed briefly)

\o/


[WIP] - Update rails to version 5.1.4

WIP
First pass through the gem dependency upgrade. Specs and linting passing, not been run within a browser / with assets yet. Will resume tomorrow and tidy up / squish commits.

We have these in our gitignore files, any objections to adding?


Allow user to edit title, subtitle, title-link, and subtitle-link. Al…

…l the magic happens in headings.js. Minor css and html changes to style.css and index.html. And minor edit to afqb object in afqb.js

@anotherjoshsmith This PR adds the editable title, subtitle, etc.

Looks good, merging now!


0.6.0 - Cannot read property 0 of null.

I have just installed the app ugraded to v2 ( was waiting for this for quite a while ), and unfortunately it does not work. When I click "New work item", it's creating an empty modal with no fields to populate. In the console i can see the error "Cannot read property 0 of null ( occuring in modal.js )". Similiar thing happens when i open "Link to work item" modal - it presents the same error as with new work item. Tested od both Chrome and Edge browsers.

Found the answer on different thread. The issue is gone when i set additional credentials on PAT, as per below suggestion.

hi
I cannot seem to get the integration working..
Comments updated at either end do not flow through...
has anyone else had the issue bfore??

Leaving a note for anyone in the future who encounters this error - I was receiving it on the latest version using a PAT with work item read & write scopes. The fix for me was to give my PAT full access.


Add pre-commit hook to format shell scripts

Problem

We have quite a lot of shell scripts in the codebase. Prettier doesn't format them.
Description

shfmt is a tool for formatting shell programs. It is available as a pre-commit hook and can be readily integrated with our linting setup.
Additional context

This will undoubted cause our existing scripts to be slightly changed to match the style guide. It might be worth discussing if the changes are worth it.

Hi @WordPress/openverse-maintainers! I would like to pick this up if that is alright.


Adding a current model (gpt-3.5-turbo) still gives error

When I update the plugin to use an existing model, it gives this error...
error: This is a chat model and not supported in the v1/completions endpoint. Did you mean to use v1/chat/completions?
...suggesting maybe the whole API has been updated since this plugin was written.

I actually took the plugin and amke the changes needed to make it functional while adding a bunch of other features.  This plugin uses chatgpt4 and chatgpt4o.
https://github.com/theCompanyDream/strapi-supergpt


build ，No binaries are generated

No binaries are generated

What binary would you expect to exist?

linux x86_64

What would that binary do?

Start a socks5 server

This repository does not implement a socks5 server.


Prevent Spam with Email Validation

We want to perform two checks.

for a valid email format
for a reachable host

https://github.com/badoux/checkmail

done along with check password and username min length


master branch is broken status on rubyci

see http://rubyci.blob.core.windows.net/centos7/ruby-trunk/log/20150225T050002Z.fail.html.gz
I investigate this. I found some broken specs.

mkdir work (it's temporary dir)
git clone mspec
git clone rubyspec
run follow command

$ ruby mspec/bin/mspec -fd rubyspec/core/argf/codepoints_spec.rb

I got this fail.
% ruby mspec/bin/mspec -fd rubyspec/core/argf/codepoints_spec.rb
ruby 2.1.5p299 (2015-02-19 revision 49652) [x86_64-darwin14.0]
E....

1)
An exception occurred during: after :each
ARGF.codepoints is a public method ERROR
Errno::ENOENT: No such file or directory @ rb_sysopen - -fd
/Users/(snip)/rubyspec/core/argf/shared/each_codepoint.rb:12:in `closed?'

I changed default branch to ruby and force pushed yesterday status. because we have release plan of new version of Ruby in this month.

I cannot reproduce with ruby 2.3.0dev (2015-02-25 trunk 49725) [x86_64-linux], any idea what might be the cause?

Finished in 0.001261 seconds

1 file, 5 examples, 5 expectations, 0 failures, 0 errors

I already fixed codepoinsts_spec.rb

@nobu and me fixed some specs, but following examples still failed. Please see this lists: https://gist.github.com/hsbt/df6cf7bb7029c6cdb691

These failure seem to only happen when you run with cwd above the rubyspec and mspec directories, right?
I am used to run locally in the rubyspec dir like this:
ruby ../mspec/bin/mspec -fd core/file/to_path_spec.rb

These failure seem to only happen when you run with cwd above the rubyspec and mspec directories, right?

Yes. but rubyci uses mspec and rubyspec outside their directory.

This is due (at least the first of the list) to lack of specifying the config file, for instance
$ ruby mspec/bin/mspec --config rubyspec/ruby.2.3.mspec -fd rubyspec/core/file/to_path_spec.rb
passes
but
ruby mspec/bin/mspec -fd rubyspec/core/file/to_path_spec.rb
not

Now, I do agree this is still a bug in rubyspec in that that final test should be guarded with
with_feature :encoding do, but I would think Ruby CI should use the config file to enable encoding specs, no?
Or do you run both with and without config on Ruby CI?

In particular, http://www.rubyist.net/~akr/chkbuild/debian/ruby-trunk/log/20150225T064600Z.log.html.gz#rubyspec uses rubyspec/ruby.1.9.mspec which does not exist!
MSpec should definitely not swallow the error, but this should be changed to ruby.2.3.mspec (or ruby.mspec if you agree on https://github.com/ruby/mspec/issues/4).

Note: chkbuild is https://github.com/akr/chkbuild

Do you want to fix these failures due to lack of config file?

Should master be the default branch again?

I will fix the one related to the encode helper.

Closing this one as it is getting quite long, please reopen if there is any issue :)

@eregon I changed default branch to master, Now, some examples are still fails. I will create new issue.


Use CANCELLED everywhere instead of CANCELED.

This is necessary since orca/MonitorBakeTask expects CANCELLED.
@spinnaker/reviewers please review.

LGTM - but it looks like you'll need to rebase.

Closing in favor of https://github.com/spinnaker/orca/pull/660.


bump version in package.json to v2.22.1

release version v2.22.1

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


Testing 1,2,3.

Hi Joe.

[ ] Put together 10 paywalls and papers that we can use as testing papers for the tools. These should detail the expected responses
[ ] Test the new plugin with 5 people on hangouts. Ensure they can complete core functions

This is largely done, closing now!


Extend query text to be readable

Extend or summarize the query text so that it is readable and understandable

Just added the string length to the config file so now easy to change to your liking.


[reservations] Fix validation errors as follow up to #10297

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[x] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

Can one of the admins verify this patch?

@jianyexi , could you give suggestions on the fix on lintDiff error and breaking change error?

Would greatly appreciate suggestions, as I am leaving at the end of the week and would like to avoid having to transition the work to someone else.

/azp run automation - sdk

@aditink  This change requires a breaking change review with the Azure API Review Board

I no longer work at Microsoft. Someone else will need to pick up the PR.

The purpose is to fix the examples and should seek an approach without introduce breaking change. I close this PR since there is no bandwidth now to do this work from RP's owner perspective.


Help with Windows 8.1

I previously got this to work on Windows 8.1, but had to factory reset my laptop and now can't remember how I did it, whoops. I'm very, very new to programming.
I installed Python 2.7, downloaded and extracted pt-voicebox, and added Python to my environment variables. Then I tried to run the predictive text program through the command prompt.
When I change the directory to the folder where voicebox.py is located, and try to run it with "python voicebox.py", I've been getting the following:
"Traceback :
File voicebox.py, line 14, in
from .corpus import Corpus
Value Error: Attempted relative import in non-package"
Does anyone know what I'm possibly doing wrong? Thanks in advance~

You changed the directory to one folder too deep:

set the working directory in the command prompt to the main pt-voicebox folder
run python bin/voicebox

Also make sure you have the nose and six packages installed. This worked for me.


9391 filter data sources

Added:

Provides the all_forms prop for the Form filter
Provides endpoints for users/groups for the Submitter filter
Adds a natural_sort utility for sorting data

Changed:

Save { name, id } instead of id for selected options. Required because the map of id to name is no longer easily available (it's in select2's cache instead of our own). Nicely simplifies things.

Risks:

Related select2s (including on Form/Submitter filter, Broadcasts route, maybe others)

9736 "Parse current selection for Form filter" will come next.

CI failure details:
# Failing due to invalid Maps API key?
rspec ./spec/features/results/location_picker_spec.rb:25

# All pass locally, will diagnose soon
rspec ./spec/features/results/skip_logic_spec.rb:37
rspec ./spec/features/results/form_rendering_and_submission_spec.rb:125
rspec ./spec/features/results/form_rendering_and_submission_spec.rb:266
rspec ./spec/features/results/form_rendering_and_submission_spec.rb:244
rspec ./spec/features/results/file_upload_spec.rb:20


Upgrade Apache Commons Collections to v3.2.2

Version 3.2.1 has a CVSS 10.0 vulnerability. That's the worst kind of
vulnerability that exists. By merely existing on the classpath, this
library causes the Java serialization parser for the entire JVM process
to go from being a state machine to a turing machine. A turing machine
with an exec() function!
https://commons.apache.org/proper/commons-collections/security-reports.html
http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/
Also, do consider using Guava in the future.

Thanks for the patch, @jart. I've filed PHOENIX-2749 for this.


Consolidate Graph Builders

We currently have several classes that are concerned with creating / building graphs from certain parameters or input graphs:

Algorithm\ResidualGraph
Algorithm\TransposeGraph
Loader\CompleteGraph
Future ComplementGraph (see #60)
Possibly some others

IMHO both Algorithm and Loader are bad descriptions and do not quite describe their responsibility. As a first step, I'd vote for grouping these in a new Builder (or similar) namespace. In the future we should work out a decent API (interface).
Refs #120.

The name "Builder" will probably be confusing with regards to the builder pattern.
Ticket #119 suggests we should stabilize the core graph library and split off optional sub-namespaces. The suggested Builder namespace would probably be one such candidate, and as such we should probably avoid introducting yet another namespace in the first place.
Instead, I'd suggest we should move the CompleteGraph into the Algorithm namespace. This will obsolete this issue.

The name "Builder" will probably be confusing with regards to the builder pattern.

Marking this ticket as invalid.

Instead, I'd suggest we should move the CompleteGraph into the Algorithm namespace. This will obsolete this issue.

Loaders will be split of via #117, algorithms will be split off via #119.
As such, this is blocked until both issues have been resolved.
I've filed two new tickets that keep track of this state.


Declare defaultUsage as func

Fixes #1

Codecov Report

Merging #2 (4d049dc) into main (92ba898) will decrease coverage by 4.63%.
The diff coverage is 61.53%.

@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
- Coverage   95.93%   91.30%   -4.64%
==========================================
  Files           2        2
  Lines         123      138      +15
==========================================
+ Hits          118      126       +8
- Misses          2        8       +6
- Partials        3        4       +1

Impacted Files
Coverage Δ

acmd.go
89.38% <61.53%> (-5.52%)
:arrow_down:

Continue to review full report at Codecov.

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

ping @crayoned @quasilyte


Populated enqueued_at time during enqueue call

Fixes #109, as long as I understood the ticket :D
Even when moving scheduled jobs we need to call enqueue so just populate the field in that method.

Coverage increased (+0.04%) to 83.75% when pulling 7cb42859a066eb12cb3bb0936394541ac2867ba5 on keyan:kp_populated_enqueued_at_time into e39293e0e65abca14a69ae05990debc74b8ece65 on edgurgel:master.

Coverage increased (+0.04%) to 83.75% when pulling d4cb26bb8dc6ab7c1c3392276545e037d1192e6c on keyan:kp_populated_enqueued_at_time into e39293e0e65abca14a69ae05990debc74b8ece65 on edgurgel:master.

Coverage increased (+0.04%) to 83.75% when pulling d4cb26bb8dc6ab7c1c3392276545e037d1192e6c on keyan:kp_populated_enqueued_at_time into e39293e0e65abca14a69ae05990debc74b8ece65 on edgurgel:master.

Thanks for starting this! I created this issue today! 😮
Tthe ScheduleManager calls this script here: https://github.com/edgurgel/verk/blob/master/priv/enqueue_retriable_job.lua
Which fetches from a set (schedule, retry) and pushes to the specified queue. So we need to populate this field there also :(

Ah! I see, more difficult than it seemed :)
I guess it should first be made clear what enqueued_at means? The first time it is put into the queue? Or the latest? If the latter case then we would also need to update here: https://github.com/edgurgel/verk/blob/e39293e0e65abca14a69ae05990debc74b8ece65/priv/requeue_job_now.lua#L10

Fair enough. The definition is: "time when it was first enqueued to be processed". This is so we know since when we "want" to process this job.


Platform independent input simulation

Write or use a library for platform independent input simulation.

For X11 check this: http://www.doctort.org/adam/nerd-notes/x11-fake-keypress-event.html


Cache is empty when application quit and run background

Hi !
I have a class "CacheUtilities" i use it for stock a Static Cache of UIImage.
I have a lot of image to load from my server, so i want load it just one time and keep it on my Cache (except if user close the process of my app ! )
But i have a problem, when the user only close my app (not kill the app, just quit and make it run in background) and come back, my Cache is empty and i need to reload all images... What's the solution ?
I use the expires .Never
CacheUtilities.getCacheImage().setObject(UIImage(data: data)!, forKey: sUrl, expires: CacheExpiry.Never)

Disk write will silently fail when the key contains characters not compatible with the filesystem (it's used as filename); this is the case of URLs.
I've fixed this problem cleaning up the key using a regex solution like: http://stackoverflow.com/questions/6102333/what-characters-are-allowed-in-a-ios-file-name/18526106#18526106

I think AwesomeCache should make sure to escape the name before saving.
E.g. here: https://github.com/aschuch/AwesomeCache/blob/master/AwesomeCache/Cache.swift#L255

I have just authored version 1.0.2 of AwesomeCache that should fix this issue.


Edit collection from Main Gallery

Changes
Allow users to edit their collection through main gallery / homepage.

@kaitoo1 Thanks for the good catch!
Updated the changes. Seems like we can simplify the changes by using collectionId as a flag.

If there is collectionId in the query : back to the previous page with window back to retain scroll position
If not, we assume its coming from the wizard page

@jakzaizzat thanks for addressing, that logic makes sense!
LGTM

@kaitoo1 Sorry. Missed out this scenario 🤦🏻♂. Updated the changes


Refactor - vm interface of BuiltinFunctions

This drastically simplifies the vm interface of BuiltinFunctions so that it becomes a lot closer to the vm internal call interface:

Instead of passing ContextObject, MemoryMapping and ProgramResult the encrypted pointer to the entire EbpfVm is passed, which is then decrypted and decomposed inside declare_builtin_function(). Thanks to #534, this does not even require swapping of argument registers.
The instruction metering around syscalls from the interpreter and JIT was moved into declare_builtin_function(), which does not only deduplicate the logic, but also allows LLVM to optimize the register allocation, spilling and perform inlining, effectively reducing the cost of a syscall from three context switches between the VM and Rust ABI, down to one.

Unfortunately, encrypt_runtime_environment is now no longer optional as we can not read the config of the VM without dereferencing the potentially encrypted VM pointer.

Codecov Report

Merging #535 (0097061) into main (b1b50f7) will decrease coverage by 0.06%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##             main     #535      +/-   ##
==========================================
- Coverage   89.70%   89.65%   -0.06%
==========================================
  Files          24       24
  Lines       10213    10200      -13
==========================================
- Hits         9162     9145      -17
- Misses       1051     1055       +4

Files
Coverage Δ

src/interpreter.rs
98.81% <100.00%> (-0.03%)
:arrow_down:

src/jit.rs
91.49% <100.00%> (-0.49%)
:arrow_down:

src/vm.rs
85.90% <100.00%> (+0.06%)
:arrow_up:

src/program.rs
79.48% <82.35%> (+1.41%)
:arrow_up:


Highlighting syncs only on cursor move

The highlight doesn't sync if I undo the last deletion, I have to move the cursor to make highlighting sync

That's true, at the moment the new highlight only is applied when the cursor moves. Let me see if I can fix that.

Hmm, there doesn't seem to be a valid event for that, so it could only be achieved with some hacks which I'd rather not introduce.

That's unfortunate


feat: Add formatter for wx.RichTextCtrl

Control to format is supplied as outFile, and styles are applied according to the pygments style given. The formatter stores the contents of each control the last time it was formatted to avoid formatting unchanged text twice, making it fast enough to call on each wx.EVT_TEXT event & style the control as text is entered.

I'm not convinced we want a wx dependency in Pygments instead of having this in a plugin. It complicates testing (if we have a wx extra for example), and I don't like Pygments changing behavior based on the presence of other libraries. Can you explain the rationale while this is useful vs. a plugin? Is there a place where a plugin won't work and it has to be in Pygments upstream?

My thinking was that importing wx inside methods avoids it having to be a dependency - it's only needed if you're using the wx formatter, which you're not going to do unless you're formatting a wx element (so would have it installed). I see what you mean about complicating testing and making pygments' behaviour variable though, and I don't see any reason it can't be a plugin so I'll do that instead :)

Okay, moved it over to a plugin: https://github.com/TEParsons/pygments-gui
@Anteru is there any kind of directory I can add this to to help people find it?

Uh, sorry for missing this. Not that I'm aware of really ... maybe we could start adding this to the docs somewhere? integrate.rst sounds like a decent place?


Individual Isosurface Viewer & Bug Fix

New features:

Add an individual Isosurface viewer in Glue
Add a new fly mode for 3D Volume rendering
Add stretch functionality for volume&isosurface objects
Canvas resize for better text instruction display
Some files/variables renamed

Bug fixed:
SHIFT keypress, camera view distance, color value assignment for Isosurface visual
What could be done:

Add window labels for both viewers
Add test unit for glueviewer - don't know how to define session
Make the Isosurface visual in the right orientation - I have tried data.reshape() but it doesn't work well

Thanks for your work on this! As we discussed on the telecon:

[ ] It would be nice to be able to stretch in both directions. If the slider starts off in the center, then it could go from 0.1 to 10 for example (we should probably slide in log space to make it easier)

[ ] When adjusting the stretch, we should keep the view as-is. When I tried it, it kept zooming in

[ ] It would be nice if the initial view showed the whole data. Could you start off e.g. looking down the x or z axis (i.e. no rotation) and then with all the data fitting in the screen?

[ ] The isosuface viewer crashed for me. I will try and figure out which versions crashed.

You can push new commits to this branch and tick off any items above in my list once they are implemented.

@astrofrog Thank you for your comments. I have pushed a new commit and please let me know if there is anything should be modified.
I also found that Isosurface Visual build becomes very slow with some complicated data cube. So maybe we could create a new issue or continue the original isosurface issue about this problem.

@PennyQ - very nice, thanks! I will merge this now and indeed we can continue to keep track of the isosurface issue in https://github.com/glue-viz/glue-3d-viewer/issues/6


Luacheck isn't being installed properly on Fedora34 Docker image

Testing setup

geerlingguy/docker-fedora34-ansible:latest
geerlingguy/docker-rockylinux8-ansible:latest

Steps to reproduce
docker run -it geerlingguy/docker-fedora34-ansible:latest bash
yum install lua-devel luarocks gcc
luarocks install luacheck
luacheck
/usr/lib/luarocks/rocks-5.4/luacheck/1.1.1-1/bin/luacheck

Observed behaviour
[root@b4b90dd62f3a /]# luacheck
bash: luacheck: command not found

[root@b4b90dd62f3a /]# /usr/lib/luarocks/rocks-5.4/luacheck/1.1.1-1/bin/luacheck
lua: /usr/lib/luarocks/rocks-5.4/luacheck/1.1.1-1/bin/luacheck:2: module 'luacheck.main' not found:
        no field package.preload['luacheck.main']
        no file '/usr/share/lua/5.4/luacheck/main.lua'
        no file '/usr/share/lua/5.4/luacheck/main/init.lua'
        no file '/usr/lib64/lua/5.4/luacheck/main.lua'
        no file '/usr/lib64/lua/5.4/luacheck/main/init.lua'
        no file './luacheck/main.lua'
        no file './luacheck/main/init.lua'
        no file '/root/.luarocks/share/lua/5.4/luacheck/main.lua'
        no file '/root/.luarocks/share/lua/5.4/luacheck/main/init.lua'
        no file '/usr/lib64/lua/5.4/luacheck/main.so'
        no file '/usr/lib64/lua/5.4/loadall.so'
        no file './luacheck/main.so'
        no file '/root/.luarocks/lib64/lua/5.4/luacheck/main.so'
        no file '/usr/lib64/lua/5.4/luacheck.so'
        no file '/usr/lib64/lua/5.4/loadall.so'
        no file './luacheck.so'
        no file '/root/.luarocks/lib64/lua/5.4/luacheck.so'
stack traceback:
        [C]: in function 'require'
        /usr/lib/luarocks/rocks-5.4/luacheck/1.1.1-1/bin/luacheck:2: in main chunk
        [C]: in ?

Expected behaviour
luacheck binary is present in the default location /usr/local and there's no traceback while executing this binary.
Notes

Analogous steps on Debian and Ubuntu Docker images weren't observed (no traceback and luacheck is available under /usr/local/bin/luacheck).
I've tried to install Lua and LuaRocks from the source on Fedora34 image, but then I've encountered a bit different behaviour that deserve its own issue.

I played around a little bit and did get the same results as you, but only with that Docker image. No other platforms seem to have this problem (luacheck has been installed from luarocks 2.8 million times). Many distros tested work just fine. Furthermore it isn't just this package, the luarocks on that Docker image is not installing any binaries. I tried half a dozen other Lua packages that place stuff in the LUA_BINDIR and none of them worked.
LuaRocks itself works just fine on many platforms and I don't see any obvious misconfiguration. My conclusion is that something weird is up with those images you are using, maybe some directory protection of funky mounts or something.

I checked and verified the behavior on Fedora images 33-39, including both the official ones and those provided by @geerlinguy. I can confirm that errors were observed in both cases for images with versions less than 35.
With that being said we can close the issue.

Thanks for the follow up. I assume if you really needed to get this working there is probably something in the 34→35 release as far as changes to LuaRocks or system level configs that could be backported for older versions too.


helmfile: 0.144.0 -> 0.145.2

Description of changes

Update src to reflect the new repository (see https://github.com/roboll/helmfile/issues/1824)
0.144.0 -> 0.145.2
Add bash and zsh completion

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

1 package built:

helmfile


Intro level tutorial for Memray

Issue number of the reported bug or feature request: #
Describe your changes
We have worked on an introductory level course for people to get familiar with Memray.
Testing performed
We ran make docs-live to view the new RST files, and to see everything is rendered properly.
We also ran the exercises via instructions specified and was able to get through the whole tutorial.
Additional context
It is worth noting, that I plan to update the instructions to include running the tutorial via codespaces, but we stuck with simple venv/pip for this first PR.

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

Project coverage is 92.97%. Comparing base (41248ed) to head (71b4b5b).
Report is 33 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #586      +/-   ##
==========================================
+ Coverage   92.55%   92.97%   +0.41%
==========================================
  Files          91       91
  Lines       11304    11195     -109
  Branches     1581     2047     +466
==========================================
- Hits        10462    10408      -54
+ Misses        837      787      -50
+ Partials        5        0       -5

Flag
Coverage Δ

cpp
92.97% <ø> (+7.02%)
:arrow_up:

python_and_cython
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Closing PR for new branch with proper commit signatures.


scheduler: reservation transformer ends early with reservation affinity

Ⅰ. Describe what this PR does
The Pod declares a ReservationAffinity, which means that the Pod must reuse the Reservation resources, but there are no matching Reservations, which means that the node itself does not need to be processed. We can end early to avoid meaningless operations.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in make test

/cc @hormes @FillZpp @ZiMengSheng  PTAL

/lgtm
/approve


error build for flutter 3.22.0

Could not build the precompiled application for the device.
Error (Xcode): ../.pub-cache/hosted/pub.dev/fading_edge_scrollview-3.0.0/lib/src/fading_edge_scrollview.dart:116:31: Error: The argument type 'PageController?' can't be assigned to the parameter type 'ScrollController' because 'PageController?' is nullable and 'ScrollController' isn't.

I have the same problem, can you update the plugin fading_edge_scrollview-3.0.0 to last version fading_edge_scrollview 4.1.1

i have the same issue, cant build the app, please to update the fading_edge_scrollview to ^4.1.1.
thanks.

i have the same issue, cant build the app, please to update the fading_edge_scrollview to ^4.1.1. thanks.

done! please use the following:
  marquee:
    git:
      url: https://github.com/MarcelGarus/marquee.git
      ref: "master"
      ```


cannot start remix server on Mac

Reproduction
Hello,
I have a remix server on windows its started and works but on Mac I got this error:
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1144:15)
    at Function.Module._load (node:internal/modules/cjs/loader:985:27)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at /Users/scr/Desktop/renting24/test_vercel/node_modules/@remix-run/serve/dist/index.js:43:17
    at Layer.handle [as handle_request] (/Users/scr/Desktop/renting24/test_vercel/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/scr/Desktop/renting24/test_vercel/node_modules/express/lib/router/route.js:144:13)
    at next (/Users/scr/Desktop/renting24/test_vercel/node_modules/express/lib/router/route.js:140:7)
    at next (/Users/scr/Desktop/renting24/test_vercel/node_modules/express/lib/router/route.js:140:7)
    at next (/Users/scr/Desktop/renting24/test_vercel/node_modules/express/lib/router/route.js:140:7)

System Info
System:
    OS: macOS 14.2
    CPU: (8) arm64 Apple M3
    Memory: 155.11 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - /usr/local/bin/node
    npm: 10.4.0 - /usr/local/bin/npm
  Browsers:
    Safari: 17.2

Used Package Manager
npm
Expected Behavior
package.json
{
  "private": true,
  "sideEffects": false,
  "scripts": {
    "build": "remix build",
    "dev": "remix dev",
    "typecheck": "tsc"
  },
  "dependencies": {
    "@fullcalendar/core": "^6.1.6",
    "@fullcalendar/resource": "^6.1.6",
    "@fullcalendar/resource-timeline": "^6.1.6",
    "@mantine/core": "^7.1.2",
    "@mantine/dates": "^7.1.2",
    "@mantine/hooks": "^7.1.2",
    "@natscale/react-calendar": "^0.0.0-beta.26",
    "@paypal/react-paypal-js": "^7.8.3",
    "@react-pdf/renderer": "^3.1.14",
    "@react-spring/web": "^9.7.3",
    "@remix-run/css-bundle": "^2.0.1",
    "@remix-run/express": "^1.15.0",
    "@remix-run/node": "^1.15.0",
    "@remix-run/react": "^1.15.0",
    "@remix-run/vercel": "^1.15.0",
    "@remix-validated-form/with-yup": "^2.0.3",
    "@remix-validated-form/with-zod": "^2.0.7",
    "@stripe/react-stripe-js": "^2.1.0",
    "@stripe/stripe-js": "^1.52.1",
    "@vercel/node": "^2.10.3",
    "@vercel/remix": "^1.15.0",
    "compression": "^1.7.4",
    "cross-env": "^7.0.3",
    "dayjs": "^1.11.7",
    "express": "^4.18.2",
    "hamburger-react": "^2.5.0",
    "isbot": "^3.6.8",
    "mailgun.js": "^10.2.1",
    "mailtrap": "^3.3.0",
    "morgan": "^1.10.0",
    "nodemailer": "^6.9.9",
    "react": "^18.2.0",
    "react-calendar": "^4.2.1",
    "react-calendar-datetime-picker": "^1.6.3",
    "react-dom": "^18.2.0",
    "react-faq-component": "^1.3.4",
    "react-icons": "^5.0.1",
    "react-onclickoutside": "^6.13.0",
    "react-pdf": "^7.5.1",
    "react-rainbow-components": "^1.3.1",
    "react-slick": "^0.29.0",
    "react-spinners": "^0.13.8",
    "remix-utils": "^6.6.0",
    "remix-validated-form": "^4.6.11",
    "spinners-react": "^1.0.7",
    "stripe": "^12.1.1",
    "zod": "^3.22.4"
  },
  "devDependencies": {
    "@remix-run/dev": "^1.15.0",
    "@remix-run/eslint-config": "^1.15.0",
    "@remix-run/serve": "^1.15.0",
    "@types/lodash": "^4.14.194",
    "@types/nodemailer": "^6.4.14",
    "@types/react": "^18.0.35",
    "@types/react-dom": "^18.0.11",
    "@types/react-slick": "^0.23.10",
    "dotenv": "^16.0.3",
    "eslint": "^8.38.0",
    "eslint-plugin-you-dont-need-lodash-underscore": "^6.12.0",
    "lodash": "^4.17.21",
    "nodemon": "^2.0.20",
    "npm-run-all": "^4.1.5",
    "postcss": "^8.4.31",
    "postcss-preset-mantine": "^1.8.0",
    "postcss-simple-vars": "^7.0.1",
    "typescript": "^4.9.5"
  },
  "engines": {
    "node": ">=14"
  }
}

Actual Behavior
what I am doing wrong on Mac ?

Can you provide a reproduction repository?


Can't type Chinese in vscode installed from snap

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
1.56.2-054a9295330880ed74ceaedda236253b4f39a335-x64
OS Version:
Ubuntu 20.04.2 LTS

Steps to Reproduce:

Install vscode via snap install vscode --classic (others installed method are good, without problem.)
default Chinese input method in Ubuntu 20.04 (ibus + 新酷音) can't switch to "中", it can only type in English

@Tyriar any idea?


Exporting Layers w/ White Background/ Consistent Size

Hi There, I'm exporting files as layers ok only when I want the image to be the same size as the canvas so a square image is saved as the same rectangular shape consistently.
So for example - I have lots of odd-shaped images and I want to export them all as 2500 x 3500 with the images set in a white background. Not just exporting the layers in their odd shapes.
Hope this makes sense.
David Jenner
<EMAIL_ADDRESS>Configuration
Version of Export Layers: Latest verison
Version of GIMP: 2.10
Operating system: MacOs Big Sur

Hi David, I realize this is reply may be quite late as I just got back to maintaining this project after a hiatus, but I'll try.
I believe you can achieve this as follows:

Set the size of your image to 2500 x 3500.
Open more settings (Settings -> Show More Settings).
Uncheck "Use layer size".
Click "Add Procedure..." and add "gimp-layer-resize-to-image-size".
Click "Add Procedure..." and add "gimp-layer-flatten". This will remove the alpha channel and set the background to a color, white by default.

The screenshot below shows the settings.

Alternatively, you can replace step 1 by adding a custom procedure "gimp-image-resize" with 2500 x 3500 width and height, respectively.
Of course, if I misunderstood, let me know.


gyp ERR! stack Error: make failed with exit code: 2

When I install the library I receive this error:
> npm install -g facebook-export
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
npm WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated<EMAIL_ADDRESS>ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
/usr/local/bin/facebook-export -> /usr/local/lib/node_modules/facebook-export/bin/export.js
/usr/local/bin/facebook-analyze -> /usr/local/lib/node_modules/facebook-export/bin/analyze.js

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/facebook-export/node_modules/leveldown
> prebuild-install || node-gyp rebuild

prebuild-install WARN install No prebuilt binaries found (target=12.18.3 runtime=node arch=x64 platform=darwin)
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/builder.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/db_impl.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/db_iter.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/filename.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/dbformat.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/log_reader.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/log_writer.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/memtable.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/repair.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/table_cache.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/version_edit.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/version_set.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/db/write_batch.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/helpers/memenv/memenv.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/port/port_posix_sse.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/block.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/block_builder.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/filter_block.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/format.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/iterator.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/merger.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/table.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/table_builder.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/table/two_level_iterator.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/arena.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/bloom.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/cache.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/coding.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/comparator.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/crc32c.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/env.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/filter_policy.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/hash.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/logging.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/options.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/status.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/port/port_posix.o
  CXX(target) Release/obj.target/leveldb/deps/leveldb/leveldb-1.20/util/env_posix.o
  LIBTOOL-STATIC Release/leveldb.a
  CXX(target) Release/obj.target/snappy/deps/snappy/snappy-1.1.4/snappy-sinksource.o
  CXX(target) Release/obj.target/snappy/deps/snappy/snappy-1.1.4/snappy-stubs-internal.o
  CXX(target) Release/obj.target/snappy/deps/snappy/snappy-1.1.4/snappy.o
  LIBTOOL-STATIC Release/snappy.a
  CXX(target) Release/obj.target/leveldown/src/batch.o
In file included from ../src/batch.cc:3:
In file included from ../../nan/nan.h:192:
../../nan/nan_maybe_43_inl.h:112:15: error: no member named 'ForceSet' in 'v8::Object'
  return obj->ForceSet(isolate->GetCurrentContext(), key, value, attribs);
         ~~~  ^
In file included from ../src/batch.cc:3:
In file included from ../../nan/nan.h:197:
In file included from ../../nan/nan_converters.h:67:
../../nan/nan_converters_43_inl.h:22:1: warning: 'ToBoolean' is deprecated: ToBoolean can never throw. Use Local version. [-Wdeprecated-declarations]
X(Boolean)
^
../../nan/nan_converters_43_inl.h:18:12: note: expanded from macro 'X'
      val->To ## TYPE(v8::Isolate::GetCurrent()->GetCurrentContext())          \
           ^
<scratch space>:218:1: note: expanded from here
ToBoolean
^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2663:3: note: 'ToBoolean' has been explicitly marked deprecated here
  V8_DEPRECATED("ToBoolean can never throw. Use Local version.",
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
In file included from ../../nan/nan.h:197:
In file included from ../../nan/nan_converters.h:67:
../../nan/nan_converters_43_inl.h:40:1: warning: 'BooleanValue' is deprecated: BooleanValue can never throw. Use Isolate version. [-Wdeprecated-declarations]
X(bool, Boolean)
^
../../nan/nan_converters_43_inl.h:37:15: note: expanded from macro 'X'
  return val->NAME ## Value(isolate->GetCurrentContext());                     \
              ^
<scratch space>:225:1: note: expanded from here
BooleanValue
^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2701:3: note: 'BooleanValue' has been explicitly marked deprecated here
  V8_DEPRECATED("BooleanValue can never throw. Use Isolate version.",
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
In file included from ../../nan/nan.h:198:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:103:42: error: no viable conversion from 'v8::Isolate *' to 'Local<v8::Context>'
  return scope.Escape(v8::Function::New( isolate
                                         ^~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:186:7: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'v8::Isolate *' to 'const v8::Local<v8::Context> &' for 1st argument
class Local {
      ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:186:7: note: candidate constructor (the implicit move constructor) not viable: no known conversion from 'v8::Isolate *' to 'v8::Local<v8::Context> &&' for 1st argument
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:190:13: note: candidate template ignored: could not match 'Local<type-parameter-0-0>' against 'v8::Isolate *'
  V8_INLINE Local(Local<S> that)
            ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:4276:22: note: passing argument to parameter 'context' here
      Local<Context> context, FunctionCallback callback,
                     ^
In file included from ../src/batch.cc:3:
In file included from ../../nan/nan.h:198:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:337:37: error: too few arguments to function call, expected 2, have 1
  return v8::StringObject::New(value).As<v8::StringObject>();
         ~~~~~~~~~~~~~~~~~~~~~      ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:5531:3: note: 'New' declared here
  static Local<Value> New(Isolate* isolate, Local<String> value);
  ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:834:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/node.h:181:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED("Use MakeCallback(..., async_context)",
^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/node.h:101:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:849:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/node.h:174:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED("Use MakeCallback(..., async_context)",
^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/node.h:101:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:864:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/node.h:167:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED("Use MakeCallback(..., async_context)",
^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/node.h:101:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:911:44: error: no matching member function for call to 'ToString'
      v8::Local<v8::String> string = from->ToString();
                                     ~~~~~~^~~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2668:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
  V8_WARN_UNUSED_RESULT MaybeLocal<String> ToString(
                                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2684:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
                Local<String> ToString(Isolate* isolate) const);
                              ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:921:37: error: cannot initialize a parameter of type 'v8::Isolate *' with an lvalue of type 'char *'
        length_ = string->WriteUtf8(str_, static_cast<int>(len), 0, flags);
                                    ^~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2878:26: note: passing argument to parameter 'isolate' here
  int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                         ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:1473:31: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return scope.Escape(node::MakeCallback(
                              ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/node.h:181:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED("Use MakeCallback(..., async_context)",
^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/node.h:101:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:1533:28: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
    New(persistentHandle)->Set(New(key).ToLocalChecked(), value);
                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3498:3: note: 'Set' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:1539:28: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
    New(persistentHandle)->Set(key, value);
                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3498:3: note: 'Set' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:1545:28: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
    New(persistentHandle)->Set(index, value);
                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3507:3: note: 'Set' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:1551:32: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
        New(persistentHandle)->Get(New(key).ToLocalChecked()));
                               ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3553:3: note: 'Get' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:1557:48: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
    return scope.Escape(New(persistentHandle)->Get(key));
                                               ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3553:3: note: 'Get' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
../../nan/nan.h:1562:48: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
    return scope.Escape(New(persistentHandle)->Get(index));
                                               ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3557:3: note: 'Get' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", Local<Value> Get(uint32_t index));
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
In file included from ../../nan/nan.h:2222:
../../nan/nan_object_wrap.h:24:25: error: no member named 'IsNearDeath' in 'Nan::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object> >'
    assert(persistent().IsNearDeath());
           ~~~~~~~~~~~~ ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/assert.h:93:25: note: expanded from macro 'assert'
    (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __FILE__, __LINE__, #e) : (void)0)
                        ^
In file included from ../src/batch.cc:3:
In file included from ../../nan/nan.h:2222:
../../nan/nan_object_wrap.h:67:18: warning: 'MarkIndependent' is deprecated: Weak objects are always considered independent. Use TracedGlobal when trying to use EmbedderHeapTracer. Use a strong handle when trying to keep an object
      alive. [-Wdeprecated-declarations]
    persistent().MarkIndependent();
                 ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:566:3: note: 'MarkIndependent' has been explicitly marked deprecated here
  V8_DEPRECATED(
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:3:
In file included from ../../nan/nan.h:2222:
../../nan/nan_object_wrap.h:124:26: error: no member named 'IsNearDeath' in 'Nan::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object> >'
    assert(wrap->handle_.IsNearDeath());
           ~~~~~~~~~~~~~ ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/assert.h:93:25: note: expanded from macro 'assert'
    (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __FILE__, __LINE__, #e) : (void)0)
                        ^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:16:17: error: no matching member function for call to 'ToObject'
  return (!obj->ToObject().IsEmpty()
           ~~~~~^~~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2672:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
  V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
                                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2686:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
                Local<Object> ToObject(Isolate* isolate) const);
                              ^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:17:39: error: no matching member function for call to 'ToObject'
    && node::Buffer::HasInstance(obj->ToObject()))
                                 ~~~~~^~~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2672:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
  V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
                                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2686:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
                Local<Object> ToObject(Isolate* isolate) const);
                              ^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:18:33: error: no matching member function for call to 'ToObject'
    ? node::Buffer::Length(obj->ToObject())
                           ~~~~~^~~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2672:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
  V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
                                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2686:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
                Local<Object> ToObject(Isolate* isolate) const);
                              ^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:19:12: error: no matching member function for call to 'ToString'
    : obj->ToString()->Utf8Length();
      ~~~~~^~~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2668:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
  V8_WARN_UNUSED_RESULT MaybeLocal<String> ToString(
                                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2684:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
                Local<String> ToString(Isolate* isolate) const);
                              ^
In file included from ../src/batch.cc:5:
In file included from ../src/database.h:18:
../src/leveldown.h:30:62: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
    v8::Local<v8::Value> obj = Nan::New<v8::Object>(handle)->Get(Nan::New<v8::String>("obj").ToLocalChecked());
                                                             ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3553:3: note: 'Get' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:5:
../src/database.h:31:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
    _obj->Set(Nan::New("obj").ToLocalChecked(), obj);
          ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3498:3: note: 'Set' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:8:
../src/common.h:19:17: error: no matching member function for call to 'Has'
    && options->Has(key)
       ~~~~~~~~~^~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3590:37: note: candidate function not viable: requires 2 arguments, but 1 was provided
  V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context,
                                    ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3596:37: note: candidate function not viable: requires 2 arguments, but 1 was provided
  V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context, uint32_t index);
                                    ^
In file included from ../src/batch.cc:8:
../src/common.h:20:16: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
    ? options->Get(key)->BooleanValue()
               ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3553:3: note: 'Get' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:8:
../src/common.h:20:26: error: no matching member function for call to 'BooleanValue'
    ? options->Get(key)->BooleanValue()
      ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2699:8: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
  bool BooleanValue(Isolate* isolate) const;
       ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2702:51: note: candidate function not viable: requires single argument 'context', but no arguments were provided
                V8_WARN_UNUSED_RESULT Maybe<bool> BooleanValue(
                                                  ^
In file included from ../src/batch.cc:8:
../src/common.h:30:17: error: no matching member function for call to 'Has'
    && options->Has(key)
       ~~~~~~~~~^~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3590:37: note: candidate function not viable: requires 2 arguments, but 1 was provided
  V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context,
                                    ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3596:37: note: candidate function not viable: requires 2 arguments, but 1 was provided
  V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context, uint32_t index);
                                    ^
In file included from ../src/batch.cc:8:
../src/common.h:31:17: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
    && options->Get(key)->IsNumber()
                ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3553:3: note: 'Get' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:8:
../src/common.h:32:16: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
    ? options->Get(key)->Uint32Value()
               ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:3553:3: note: 'Get' has been explicitly marked deprecated here
  V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:328:29: note: expanded from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../src/batch.cc:8:
../src/common.h:32:38: error: too few arguments to function call, single argument 'context' was not specified
    ? options->Get(key)->Uint32Value()
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2707:3: note: 'Uint32Value' declared here
  V8_WARN_UNUSED_RESULT Maybe<uint32_t> Uint32Value(
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:368:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
                              ^
../src/batch.cc:42:67: error: no matching member function for call to 'ToObject'
  Database* database = Nan::ObjectWrap::Unwrap<Database>(info[0]->ToObject());
                                                         ~~~~~~~~~^~~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2672:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
  V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
                                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2686:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
                Local<Object> ToObject(Isolate* isolate) const);
                              ^
../src/batch.cc:72:69: error: too few arguments to function call, single argument 'context' was not specified
    maybeInstance = Nan::NewInstance(constructorHandle->GetFunction(), 1, argv);
                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:6126:3: note: 'GetFunction' declared here
  V8_WARN_UNUSED_RESULT MaybeLocal<Function> GetFunction(
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:368:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
                              ^
../src/batch.cc:75:69: error: too few arguments to function call, single argument 'context' was not specified
    maybeInstance = Nan::NewInstance(constructorHandle->GetFunction(), 2, argv);
                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:6126:3: note: 'GetFunction' declared here
  V8_WARN_UNUSED_RESULT MaybeLocal<Function> GetFunction(
  ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8config.h:368:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT __attribute__((warn_unused_result))
                              ^
../src/batch.cc:91:3: error: no matching member function for call to 'ToObject'
  LD_STRING_OR_BUFFER_TO_SLICE(key, keyBuffer, key)
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/leveldown.h:53:21: note: expanded from macro 'LD_STRING_OR_BUFFER_TO_SLICE'
  } else if (!from->ToObject().IsEmpty()                                       \
              ~~~~~~^~~~~~~~
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2672:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
  V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
                                           ^
/Users/mf/Library/Caches/node-gyp/12.18.3/include/node/v8.h:2686:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
                Local<Object> ToObject(Isolate* isolate) const);
                              ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
18 warnings and 20 errors generated.
make: *** [Release/obj.target/leveldown/src/batch.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/Cellar/node@12/12.18.3/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Darwin 20.3.0
gyp ERR! command<EMAIL_ADDRESS><EMAIL_ADDRESS>"rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/facebook-export/node_modules/leveldown
gyp ERR! node -v v12.18.3
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `prebuild-install || node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/mf/.npm/_logs/2021-02-24T12_08_27_304Z-debug.log

I have tried reisntalling and updating xcode, but to no avail. I'm in doubt whether this is caused by unmaintained code, or an issue on my machine?

same error for me


nomad: Update to nomad 1.0.16 and go1.16

Per https://github.com/hashicorp/nomad/blob/v1.0.16/CHANGELOG.md nomad
1.0.15 and 1.0.16 support go1.16 (since go 1.15 is out of support and
has CVEs).

Motivation for this change
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Just noticed there is https://github.com/NixOS/nixpkgs/pull/155038 to remove it so I'll merge that instead. Thanks anyway.


add flags for upgrade-extensions

--install-extensions: It installs the extenion if not present. By default set to true.  Formerly this flag was install-timescaledb
--upgrade-extensions: Upgrade extension to available next version. By default set to true.
--upgrade-prerelease-extensions: Upgrade to available highest prerelease if available. By default set to false.

Install TimescaleDB & Promscale extensions only if --install-extensions is enabled.
Upgrade TimescaleDB & Promscale to available latest version if --upgrade-extensions is enabled.
Upgrade TimescaleDB & Promscale to available latest rc version if --upgrade-prerelease-extensions`` is enabled.

Note:

If the current installed version in timescaleDB is an rc version we ignore --upgrade-prerelease-extensions flag that is set to false & will let promscale run with the already installed rc version.

Signed-off-by: Vineeth Pothulapati<EMAIL_ADDRESS>

Thanks cevian and others for addressing this. So I assume that

This is not merged yet and so not in the 0.1.4 release?
by setting all 3 flags to false, we will ensure that promscale never tries to install or upgrade any extension at runtime?

Thanks cevian and others for addressing this. So I assume that

This is not merged yet and so not in the 0.1.4 release?
by setting all 3 flags to false, we will ensure that promscale never tries to install or upgrade any extension at runtime?

yes, @franck102 you will have full control over extensions with these flags.

yes, @franck102 you will have full control over extensions with these flags.

@franck102 yes these flags are not in 0.1.4 yet.

@franck102 yes these flags are not in 0.1.4 yet.


Lazy load multiple maps in a page

How can i use map-lazy-load directive within a page which has multiple ng-map instances. I am getting an error when trying to add multiple map-lazy-load in a page.
Error
You have included the Google Maps API multiple times on this page. This may cause unexpected errors.

This is not a supported feature at this moment. If you load multiple times, it will try to load multiple times.

Okay will try to fix it and send the PR.


Trying to understand Umbra queries

The Umbra query for defining the Message materialized view has something in it I don't understand and I haven't been able to look up or test: what does FORCEORDER mean/do?

cc @hbirler

When doing a hash join, you build a hash table on one input and probe it with the other. In Umbra, the hash table build side is the left input and the probe side is the right input. Since building a hash table is slow, the optimizer places the smaller input to the left side and the larger input to the right. However, during a recursion, if you place the recursion input to the left side, even if the recursion input is relatively small in each iteration, you have to rebuild the hash table and probe it in every iteration. If you place a constant input to the left side, Umbra is able to only build that hash table once and reuse it for every recursion iteration. This is a difficult trade-off and Umbra was unable to make the right choice there (which might have changed with the latest versions).
Using an experimental FORCEORDER flag, we forced Umbra's optimizer to use the given order for the join (Comment on the left/hash table build side, recursion input on the right/probe side). This way, we only scan Comment once and build a hash table on it. Then, in every recursion iteration, we keep probing this same hash table with the recursion input.
Umbra's optimizer is generally great so we didn't use FORCEORDER anywhere else. I remember trying it and making the queries actually slower because my intuition was worse than Umbra's optimizer. Still, the total number of tuples that are produced within a recursion is in general extremely difficult to estimate.

I see... that makes sense. Thank you! (The query certainly seems to be working without it, but I wanted to be sure I wasn't missing an important part of its semantics.)
Would it make sense to leave a comment to indicate that it's just an optimizer hint? Happy to file a PR (or not).

@mgree sure, PRs are welcome. For larger PRs, you'll need a CLA but for adding comments, it's not required to sign one.


Tried to add Yandex Mail but it doesn't show up on Franz

Hello, i have downloaded and added the Yandex Mail recipe under the AppData/Roaming/Franz/recipes folder. Then i restarted the Franz but it didn't show up. Can you help me with this situation?
Service
Yandex Mail
Link to your repository
https://github.com/mskonovalov/franz-yandex-mail-recipe

@utkudagli  FYI, recipe folder path should be: ~/Library/Application Support/Franz/recipes/dev/yandex.
Official documentation: https://github.com/meetfranz/plugins/blob/master/docs/integration.md


[ServiceBus] error running receive_deferred_message_queue.py sample in live test pipeline

Package Name: [azure-servicebus]
Package Version: 7.0.2
Operating System: Windows
Python Version: 3.9

Describe the bug
Running the receive_deferred_message_queue.py and receive_deferred_message_queue_async.py samples results in a MessageNotFoundError. This only happens randomly in the test pipeline, but I have not been able to reproduce it locally.
To Reproduce
Steps to reproduce the behavior:

Run the azure - servicebus -test pipeline.

Expected behavior
The samples should run and the tests should pass.
Screenshots
Error log from the test pipeline:
INFO:root:Testing /mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/samples/async_samples/receive_deferred_message_queue_async.py
INFO:root:Command Array: ['/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/.tox/samples/bin/python', '/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/samples/async_samples/receive_deferred_message_queue_async.py'], Target Working Directory: /mnt/vss/_work/1/s
Failed to complete mgmt operation.
Status code: 500
Message: b'Failed to lock one or more specified messages as they were not deferred messages. TrackingId:ebd08c8e-bc45-42e6-a7c4-5557a7ee745d_B9, SystemTracker:sb-t4f9e6b00658c425d:Queue:***, Timestamp:2021-02-05T18:40:07'
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Deferring msg: Message to be deferred
Traceback (most recent call last):
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/samples/async_samples/receive_deferred_message_queue_async.py", line 54, in <module>
    loop.run_until_complete(main())
  File "/opt/hostedtoolcache/Python/3.5.10/x64/lib/python3.5/asyncio/base_events.py", line 467, in run_until_complete
    return future.result()
  File "/opt/hostedtoolcache/Python/3.5.10/x64/lib/python3.5/asyncio/futures.py", line 294, in result
    raise self._exception
  File "/opt/hostedtoolcache/Python/3.5.10/x64/lib/python3.5/asyncio/tasks.py", line 240, in _step
    result = coro.send(None)
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/samples/async_samples/receive_deferred_message_queue_async.py", line 44, in main
    sequence_numbers=deferred_sequenced_numbers
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/.tox/samples/lib/python3.5/site-packages/azure/servicebus/aio/_servicebus_receiver_async.py", line 671, in receive_deferred_messages
    timeout=timeout,
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/.tox/samples/lib/python3.5/site-packages/azure/servicebus/aio/_base_handler_async.py", line 317, in _mgmt_request_response_with_retry
    **kwargs
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/.tox/samples/lib/python3.5/site-packages/azure/servicebus/aio/_base_handler_async.py", line 209, in _do_retryable_operation
    last_exception = await self._handle_exception(exception)
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/.tox/samples/lib/python3.5/site-packages/azure/servicebus/aio/_base_handler_async.py", line 157, in _handle_exception
    raise error
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/.tox/samples/lib/python3.5/site-packages/azure/servicebus/aio/_base_handler_async.py", line 205, in _do_retryable_operation
    return await operation(**kwargs)
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/.tox/samples/lib/python3.5/site-packages/azure/servicebus/aio/_base_handler_async.py", line 299, in _mgmt_request_response
    callback=callback,
  File "/mnt/vss/_work/1/s/sdk/servicebus/azure-servicebus/.tox/samples/lib/python3.5/site-packages/uamqp/async_ops/client_async.py", line 328, in mgmt_request_async

After fixing, remove the following samples from the IGNORED_SAMPLES section of scripts/devops_tasks/test_run_samples.py:
"receive_deferred_message_queue.py",
"receive_deferred_message_queue_async.py",

was able to reproduce this issue pretty consistently, although not every time. It can also be reproduced locally.

found that this was due to a delay in deferring message, which meant it was not available to receive right away. It wouldn't be a problem normally since settlement would check for ACK from deferral op, except Python uamqp doesn't check for ACK before settling.
for now, fixing this by waiting for a second after deferring.


Scheduler defined as cron: not executed immediately when fired in UI

I hope the title describes it, is this behaviour intentional?
Cron with every: 1 minute is fired immediately and crons on sundays are not?
Maybe I understand it incorrectly: manually clicking crons in UI are there to force fire them immediately?
https://user-images.githubusercontent.com/1597621/167494571-c33c9611-2b6c-4a10-bfb3-f596d8b02737.mov
this is my schedule:
:schedule:
  valid_account_scheduler:
    description: "Checks Daily at 00:00h for paid accounts. Deactivates products if not paid."
    #    cron: "@daily"
    every: "1 minute" # each 1 minute
    class: "ValidAccountScheduler"
    queue: default

  weekly_deal_scheduler:
    description: "Calculates (22:00 on Sunday) 'Weekly deals' for each product."
    cron: "0 22 * * 7" # Sunday at 22:00
    class: "WeeklyDealScheduler"
    queue: important
    args:
      - hard: "stuff"

and that are my schedule jobs:
require 'sidekiq-scheduler'

class WeeklyDealScheduler
  include Sidekiq::Worker

  def perform
    Rails.logger.info "LOGGER info: WeeklyDealScheduler on Sidekiq-server-PID-#{::Process.pid} running..."
  end
end

require 'sidekiq-scheduler'

class ValidAccountScheduler
  include Sidekiq::Worker

  def perform
    Rails.logger.info "LOGGER info: ValidAccountScheduler-#{::Process.pid}"
  end
end

Are you running sidekiq? When you click on the "enqueue now" button in the UI sidekiq-scheduler does put the job in the queue but sidekiq still needs to be running to process them

Are you running sidekiq?
yes, as you can see in the video, jobs are processed successfully only the ones defined in format like "1.minute"...
"cronjob"-like defined jobs are not running

I made a minimal repo trying to reproduce what was described and couldn't.
https://github.com/t27duck/sidekiq_scheduler_379_test
Rails app without the need of a database. Latest sidekiq and sidekiq-scheduler installed.
sidekiq.yml defines two jobs on a schedule. One for every minute via the every: option and one for every 5 minutes with the cron: option.

Clone and bundle install
Run rails s in one terminal and bundle exec sidekiq in the other.
Visit http://localhost:3000/sidekiq/recurring-jobs
Clicking the enqueue now button for either job showed that they ran via the sidekiq log in the terminal window where sidekiq was running.

That said, while they do enqueue and run, the numbers at the top do not update which is by design. Only the main page of the sidekiq ui has a JS timer that auto refreshes the page every X seconds. So clicking the enqueue now buttons require a page refresh to see the total processed.


Publish a "Design Milestone 1" release

Close Criteria
In addition to all zenhub prerequisites, closing this ticket requires completing all of the new release process (mainly pushing the release tag).
Suggested Improvement
Part of this ticket is also defining a "release".
I think it is a combination of:

defining a release version that's described in-band in the book
timestamp entry in-band in the book about release versions (change-log style)
an associated git tag

Part of the release procedure after those are in place is to announce that new release in various fora, especially the next available  Arborist call and the forum thread on TFL
Edits

2023-11-13: Added "Close Criteria" above to help remind us to follow through on the release process.

The release process for v0.1.0 is complete.
We're still reviewing the safety arguments before we can close #60 and then we can close this capstone.

#60 is now complete.


Use run_name main with runpy for matchmove script

Changelog Description
Fixes #158

Uses runpy.run_path to run the matchmove script specifying the run name to be __name__.

Additional info
The fix was given by @BigRoy on Discord.
Testing notes:

Open Maya
AYON > Loader
Right click on matchmove product
Run Matchmove script
The camera should be created

I don't have 3DE to generate such a published script to really test with. But yes, the code change "looks" ok.
@antirotor maybe you can do a test run?

@antirotor Can we merge?


Weird Symbol Generation

Some weird symbols are generated when running over my CLI with the latest version.
The characters Γå┤seems to be in place of ↴.

The characters ΓÇö seems to be in place of — .

So that you know, I'm running this on Windows.
EDIT: I forgot to mention I'm using the print_help_markdown method.

Just a hunch, but this looks like it might be an encoding issue.
clap-markdown generates UTF-8 encoded output.
From the screenshots it looks like you're using Visual Studio Code. If you look in the bottom right corner of the window, do you see the status indicator that shows the encoding? For example, here is what I see on my computer:

Which shows I'm viewing the file using UTF-8. What encoding is present there on your computer?

I can confirm that piping it from Windows Powershell changed the encoding. The default encoding for piping in Powershell is UTF-16 LE.  I'll have it written directly to the file to avoid this problem. Thanks for the help!

 Let me know if you run into any further issues, or have any feedback or suggestions.


Kill containers after restart tests

This fixes the experimental tests from hanging because they are written poorly.
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

LGTM

LGTM

LGTM

Probably unrelated experimental failure:
12:29:55 FAIL: docker_cli_daemon_experimental_test.go:105: DockerDaemonSuite.TestDaemonRestartWithPausedRunningContainer
12:29:55
12:29:55 [d6188166] waiting for daemon to start
12:29:55 [d6188166] daemon started
12:29:55 [d6188166] waiting for daemon to start
12:29:55 [d6188166] daemon started
12:29:55 docker_cli_daemon_experimental_test.go:146:
12:29:55     t.Fatal(err)
12:29:55 ... Error: exit status 1
12:29:55
12:29:55 [d6188166] exiting daemon```

@icecrime its related, the test changed in the last rebases


Update Utils.ts

Explain your changes
Suppose there is a related issue with enough detail for a reviewer to understand your changes fully. In that case, you can omit an explanation and instead include either “Fixes #XX” or “Updates #XX” where “XX” is the issue number.
Checklist

[ ] I have read the “Pull requests” section in the contributing guidelines.
[ ] I agree to the terms within the code of conduct.

🛟 If you need help, consider asking for advice over in the Kinde community.

It's looking good! I've tested in Expo - Android


Typo "Azure Repo"→"Azure Repos"

https://docs.microsoft.com/en-us/azure/devops/user-guide/code-with-git?view=azure-devops
#PingMSFTDocs

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

The updated instance appears to be referring generically to a repository in GitHub and not to the Azure service name. We'll close the PR as not applicable in this case. Please see this explanation for instance vs. service and capitalization. Thanks @hyoshioka0128.


fix: force the prior ARM32 version for UWP CMake builds

Looks like CMake defaults to the newest SDK version, but the latest Windows Kit doesn't include ARM anymore ☠
(edit: sorry I forgot DCO! Will remediate that later, or you can close this PR)

Yeah, I ran into this a bit on the build server when the image updated recently, and I believe I fixed it there a slightly different way! But I think this is way better than mine. Nice fix, ty!
nw about the remediation, good to have, but I'm not super picky about it.


Improving the init action test for Kafka

For Kafka, adding the tests for submission of jobs and verifying instances to increase the coverage for overall scope. The test now runs kafka jobs with cruise-control and kafka-manager. Also, adding the test for cruise-control and kafka-manager instance verification.

/gcbrun

/gcbrun

/gcbrun

/gcbrun


LF-22378: media.fyre.co https conversion

https://livefyre.atlassian.net/browse/LF-22378

This is now done in the backend.


Missing tkinter module in python embedded

we will use the portable python enviroment created by WinPython.
Readme file have been updated.


feature request - compatibility with https://www.npmjs.com/package/in-publish

Would it be possible to combine npm-run-all with https://www.npmjs.com/package/in-publish (2million downloads / month)?
in-publish allows to check if the prepublish hook was invoked by npm install or npm publish  as you might want to run your test scripts only if not in install mode (there are endless open issues for npm on this topic).
Maybe you could just add a --skip-command="install" parameter and use these two functions of in-publish:
https://github.com/iarna/in-publish/blob/master/index.js#L22-L28

Thank you for this issue.
However, I don't want to add any option for this for the following reasons:

in-publish is very small CLI, so it's more proper than npm-run-all to be included in dependencies. (npm-run-all is large module relatively.)
That option is going to be a short life because the problem of prepublish script is going to resolve on npm@4.

Okay actually the npm@4 way is a good approach although yarn is struggling to implement it


Estonian language

I Translated two docs into estonian language add them please
My discord is spellecrin

Nothing is changed...still conflicts


[RELEASE-1.12] Run openshift/release/generate-release.sh

Change

Branch 1.12 now is created from branch 1.13
This PR runs openshift/release/generate-release.sh release-v1.12 to rename the yaml to 1.12.

Should we fix in e2e-commons::
  elif [[ "$branch_name" == "release-v1.12" ]]; then
    echo 'release-1.33'
  elif [[ "$branch_name" == "release-v1.13" ]]; then
    echo 'release-1.34'

We need to fix the table in e2e-commons.sh for 1.14 right?:
  elif [[ "$branch_name" == "release-v1.12" ]]; then
    echo 'release-1.33'
  elif [[ "$branch_name" == "release-v1.13" ]]; then
    echo 'release-1.34'
  elif [[ "$branch_name" == "release-v1.14" ]]; then
    echo 'release-1.35'

/lgtm let's not forget to fix the script.

/lgtm


ddl: update go.mod and sum to prepare fork

Description
Need to publish fork properly so that it can be imported by ddl.
Checklist

[ ] Code compiles correctly
[ ] Run make fmt to fix inconsistent formats
[ ] Run make lint to get lint errors and fix all of them
[ ] Created tests which fail without the change (if possible)
[ ] All tests passing
[ ] Extended the README / documentation, if necessary

not sure how I got to 73 files changed... opening another one


zerconf/info call, is missing signal strength

The zeroconf/info call contains almost all information about the current state of the device, however, wifi_signal is missing from this (weird enough).
So now I need to make an extra API call to get that information.
Example response from zeroconf/info:
{
    "seq": 6,
    "error": 0,
    "data": "{\"switch\":\"on\",\"startup\":\"off\",\"pulse\":\"off\",\"pulseWidth\":500,\"ssid\":\"sonoffDiy\",\"otaUnlock\":true}"
}

Please add it so all the information can be retrieved in a single call.

This is a request for the HTTP API. I'm not asking to publish it on the mDNS records.
Reasoning: If I would try to integrate this device into a home automation system, I would have to make 2 API calls to get all the data (info + wifi_signal), while it could be just a single call.
This is a waste of resources, additional programming and requires double the amount of HTTP calls against the device.
However, I cannot extract reasoning from your answer, since it only consists of a single sentence. Could you elaborate a bit more? Thanks! 👍

wifi signal strength info has been added in zeroconf/info in the new firmware.
Daniel


net::ERR_CERT_AUTHORITY_INVALID

Describe the bug
Getting Certificate Authority failures:
 production.ERROR: net::ERR_CERT_AUTHORITY_INVALID at http://jaspur.nl {"exception":"[object] (Nesk\\Rialto\\Exceptions\\Node\\FatalException(code: 0): net::ERR_CERT_AUTHORITY_INVALID at http://jaspur.nl at /home/foobar.com/vendor/nesk/rialto/src/ProcessSupervisor.php:307)

Reproducible example
$puppeteer = new Puppeteer;
$browser   = $puppeteer->launch();

$page = $browser->newPage();
$page->goto($url = 'http://jaspur.nl');
$page->screenshot(['path' => 'example.png');

$browser->close();

Expected behavior
A Screenshot
Error logs
 production.ERROR: net::ERR_CERT_AUTHORITY_INVALID at http://jaspur.nl {"exception":"[object] (Nesk\\Rialto\\Exceptions\\Node\\FatalException(code: 0): net::ERR_CERT_AUTHORITY_INVALID at http://jaspur.nl at /home/foobar.com/vendor/nesk/rialto/src/ProcessSupervisor.php:307)

Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: Ubuntu 18.04
Node version: v8.1.0
PHP version: 7.2.10

My Node package manager is:

[x] NPM (specify the version)
[ ] Yarn (specify the version)
[ ] Other (specify the name and version)

@nesk

Use the ignoreHTTPSErrors option.

How?

See the link I've provided in my previous message. 😉

Yea, but when I do:
$browser   = $puppeteer->launch(['ignoreHTTPSErrors' => true]);

Then this is the result:

Actually, I don't think this is related to Puppeteer or my project, maybe to your firewall configuration, or your OS? Did you try to run this script with Puppeteer (in JS)?