Would you recommend using this library in production?

Hi there. I'm building a library called nact. The design goal behind it is to make actor systems and the abstractions one can build atop them more accessible to JavaScript developers.
With this goal, I decided to start out by iterating on user facing APIs rather than immediately working on clustering, service discovery and other more technical aspects of distributed actor systems.
While it is a tiny data point, my team was able to grasp the concept of how actor systems work far more easily than I've experienced with other teams when introducing Akka.Net. I'm sure there is a lot of ways to increase usability and reduce boilerplate, but I feel the project is now at a stage where I want to start looking at ways to enable cluster sharding and service discovery.
Would you say clsuterluck is robust enough for production use? I would love to use something like this in nact.

Hi @ncthbrt, that's very interesting and we'll definitely be following along with that library.
To answer your question: yes I think this is production ready. We've been using it in production for about 6-8 months on an application that uses it for sharding stateful network connections across a cluster, and it's worked well so far. Granted, that application doesn't see a ton of traffic yet, but on our deployments of 3-6 nodes it hasn't shown any problems.
That being said, this is still JavaScript and the library does have its limitations and caveats, so for good measure I'll list out some of those now, that way if you do hit any of these hopefully this list will help.

All ring additions are eventually consistent (from gossip protocol). No transactions exist for these changes yet, so if there's a long lasting network partition between two large enough sectors of the cluster, two different ideas about the ring will persist for the entirety of that partition; this can lead to strange behavior if doing large volume stateful storage that requires high consistency (even high quorum) or low replication factor.
Changes are LWW for gossip server; if 'insert A' is issued on B and 'insert C' is issued on D without D knowing about insertion on B, whichever command was issued last will resolve the inevitable vector clock conflict.
The only way to do transitive changes of ring is through 'meet' command (listed in documentation, but good to keep in mind).
Transfer protocol is JSON, not binary (due to use of node-ipc), so any serialization outside of JSON needs to go to strings and will be deserialized from that format into JSON (since it's javascript). On that note, if you see performance issues it's most likely that a JSON.parse or JSON.stringify is the culprit.
Native dependencies; if any native module fails to build on an architecture then the library won't work. See the docs for which versions of gcc/clang have been tested.
Vector clock conflict resolution strategy (outside of gossip server) is left to the user of the library. An LWW function is included by default on the gossip server, but could move to utils for more accessible use if anybody needs it.
No promise support for asynchronous actor calls (open for PRs though), which would open up use of async/await syntax.
No supervision trees (this isn't Erlang), so error/exception handling is a whole ball of wax and is left to the user.

Thanks for the detailed answer and the honest list of caveats. None of them seem like huge deal breakers. I think I'll create a prototype implementation when space on our road-map opens up.
Hope this isn't too much to ask, but wouldn't mind a review when that happens; you know your lib the best after all.  :)

Yeah absolutely, feel free to ping myself or @kevinwilson541 whenever you'd like.


Issue/5987 sidebar visual changes

Description
remove distance between stencil elements and removes shadows, adds borders to them.
Fix shadow in stencilSidebar not to be overflowed by canvas paper - I think that those shadows that align with the design are visually really good, fix is better that removal of them but can be discussed.

closes #5987 #6038
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Code is clear and sufficiently documented
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Processing this pull request

Pull request rejected by merge tool. Pull request is not mergeable. Please check for merge conflicts before re-adding the merge-tool-ready label.

Merged into branches master in d5ba20ff057590a7223740f595ab57d6d07e8f3f


Meteor > 1.4 uses node 4.x

We can't hardcode the node version for all Meteor installs. This is probably solved in demeteorizer, but opening the issue here for now.
Reported: onmodulus/modulus-cli#136

For those affected by this issue who need a 'quick fix', you might try demeterorizing locally and deploying the output to a node runtime:
$ demeteorizer --json "{ \"engines\": { \"node\": \"4.4.7\" } }"

I was thinking of a plausible solution:

Check the Meteor version (we already do that)
If the version is 1.4 (unfortunately it would have to equal that exact version for now) pass --json to demeteorizer command

It's only a hot fix, but something to get things working for now.

We currently check the version in node during deploy, but we would need to do it here in bash, right? Or create a new node script that outputs the version of node to use?

Yup! We should totally utilize node more in these build scripts. It makes life easier

Working on a solution on demeteorizer

Any luck?  I have a project that requires deployment as soon as possible and I am waiting on this issue to deploy meteor 1.4

Hey @baberuth22 we're working on a long term solution. In the meantime, you can still deploy your Meteor app to Modulus. There just requires a few changes. Here are the steps:

Demeteorize your app locally. You can set the npm/node version with flags. If you don't use the flags to set the node/npm version you can update the package.json located in bundle/programs/server/package.json
Zip your demeteorized application and deploy to Modulus under the Node.js runtime.

@baberuth22 Are you able to provide some source code that needs Meteor to use node@v4? If the source is deployed to Modulus can you provide me with the project id?

I tried running demeteorizer locally with demeteorizer --json "{ \"engines\": { \"node\": \"4.4.7\" } }"
Deployment goes through, but in the Application Log I'm getting an error: Can't find npm module 'meteor-deque'. Tried updating modulus CLI based on this https://github.com/onmodulus/demeteorizer/issues/175, but still getting error after each deploy.
As well, now when I run modulus deploy without first demeteorizing on an older version of my app that doesn't use node 4.x I get the message "You are deploying a Meteor project to a Node.js runtime. Please select the correct runtime." I have selected Node.js runtime in the administration panel. So, I have no way to get a version of my production app back up.

@harlanj I've had issues demeteorizing locally and using node runtime.  And it sounds like Jared is having trouble, so I'd prefer to continue as Meteor app if possible.
I don't know that my code needs node@v4, but I've upgraded to the latest version of meteor and it's difficult to downgrade.
My project id is 79658.  If you can do something to make it work, by all means do so.   I'd be stoked!

@jaredloson @baberuth22 try running these commands when you demeteorize:
$ demeteorizer --node-version 4.4.7
$ npm install --production # only if you have a package.json in the root of your project
$ mv ./node_modules ./demeteorized/bundle/programs/server # only if you have a package.json in the root of your project
$ cd .demeteorized
$ modulus deploy

There's a flag in demeteorizer to specifically set the node/npm version in the generated package.json. This will handle that. Let me know how that goes.

@harlanj Running demeteorizer and converting to a nodejs project seemed to work.

deploy -> v4.4.7
Uploading completed build.
Provisioning and deploying bundle to servos...
[✓] booking2 running at booking2-79658.onmodulus.net

But going to the domain I see:
Unable to connect to any application instances.

@baberuth22 did you try fully stopping and starting your project?

@baberuth22 you need to change your runtime to Node.js. I recommend creating a new project and deploying the same way I informed you, set up your environment variables and all, and if it works, move your custom domain to your new project.

@harlanj tried the above but still get the npm error about not finding "meteor-deque".
Also, just noting that I do have a package.json in my root, but the node_modules folder is also in the root, so I changed the move command to mv node_modules .demeteorized/bundle/programs/server. I verified that the node_modules folder had indeed been moved before deploying.
I need to get a Plan B in place for an event tonight, but I may try creating a new project later and let you know how it goes.

@harlanj @timmyg I fully stopped and started my project and changed the runtime to nodejs.
Now I didn't create a new project as I figured it was uneccessary. Also, I didn't want to regenerate app settings and desired to keep the same URL.
I guess I could try with a new project.

@harlanj I created a new node project and have the same result.
v4.4.7
deploy -> v4.4.7
Uploading completed build.
Provisioning and deploying bundle to servos...
[✓] booking3 running at booking3-86695.onmodulus.net

Hm... Have you tried adding that package to your package.json just to ensure that it installs?

Is there a solution to "Unable to connect to any application instances."?   How do we debug that?

Check your application logs. When demeteorizing can you add the --server-only flag? I forgot to mention that @baberuth22

@harlanj That didn't work unfortunately.
demeteorizer --json "{ \"engines\": { \"node\": \"4.4.7\" } }" --server-only
Why is this issue closed?

FYI, I am having the same issue and tried all the various permutations  / suggestions above. Is there a clear cut resolution to this issue?
I've also demeteorized locally and uploaded the bundle manually.
Presently I am seeing:

Now using node v4.4.7
Found package.json: ./programs/server/package.json
Start script specified in package.json: node ../../main
Running command: npm start

><EMAIL_ADDRESS>start /mnt/app/programs/server
> node ../../main

/mnt/app/programs/server/node_modules/fibers/future.js:280
						throw(ex);
						^

Error: /mnt/app/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt/build/Release/bcrypt_lib.node: invalid ELF header
    at Error (native)
    at Object.Module._extensions..node (module.js:434:18)
    at Module.load (module.js:343:32)
    at Module.Mp.load (/mnt/app/programs/server/npm/node_modules/meteor/babel-compiler/node_modules/reify/node/runtime.js:16:23)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at bindings (/mnt/app/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bindings/bindings.js:76:44)
    at Object.<anonymous> (/mnt/app/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt/bcrypt.js:3:35)
    at Module._compile (module.js:409:26)

npm ERR! Linux 3.13.0-92-generic
npm ERR! argv "/mnt/app/.modulus/nvm/versions/node/v4.4.7/bin/node" "/mnt/app/.modulus/nvm/versions/node/v4.4.7/bin/npm" "start"
npm ERR! node v4.4.7
npm ERR! npm  v3.10.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `node ../../main`
npm ERR! Exit status 1

As mentioned, I am also not having much luck trying to back off to Meteor <IP_ADDRESS>. If other have a way to do that, I am more than willing to go that route until this Meteor 1.4 messiness gets resolved on Modulus.  This is getting pretty frustrating I must say!

Any updates on when this might be resolved. I'm getting the same issues.

@Gervwyk The fix is on staging and going through QA. The release should be before the end of the week.

@gschleic what version of meteor are you using? I've seen that error before on multiple Meteor threads, but for alpha/beta (non stable) releases.

I need to have my project deployed for a client today.  @harlanj I just sent you an email in response to your instructions.

Why am I getting this error?
~/Meteor/booking3: demeteorizer --server-only --node-version 4.4.7 --architecture os.linux.x86_64
error: unknown option `--node-version'

I guess I can run this command instead:
demeteorizer --server-only  --architecture os.linux.x86_64  --json "{ "engines": { "node": "4.4.7" } }"
Is this the same?
@harlanj Can you deploy the fix to production from staging?   I have a deadline for a client today and it is the end of week 2.

Every time I deploy I get:
Unable to connect to any application instances.
So here is my terminal log:
~/Meteor/booking3:  demeteorizer --server-only  --architecture os.linux.x86_64  --json "{ "engines": { "node": "4.4.7" } }"
~/Meteor/booking3: cd .demeteorized/
~/Meteor/booking3/.demeteorized: modulus deploy --include-modules
Welcome to Modulus
You are logged in as sltwtr
Please choose which project to use:

booking2  Meteor
booking3  Node.js
[?] project 2
Selecting booking3

Compressing project...
20.8 MB written
Uploading project...
Upload progress [===================] 100%
Deploying project into Node.js runtime...
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Package found: /bundle/programs/server/package.json
Installing node 4.4.7
Installing npm 3.10.6
Installing packages from /bundle/programs/server/package.json
WARN: npm-shrinkwrap.json will override dependencies declared in package.json.

<EMAIL_ADDRESS>install /mnt/input/bundle/programs/server/node_modules/fibers
node build.js || nodejs build.js

linux-x64-v8-4.5 exists; testing
Binary is fine; exiting
<EMAIL_ADDRESS>/mnt/input/bundle/programs/server
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.
v4.4.7
deploy -> v4.4.7
Uploading completed build.
Provisioning and deploying bundle to servos...
[✓] booking3 running at booking3-86695.onmodulus.net
AND HERE IS THE ERROR LOG:
npm ERR! Linux 3.13.0-73-generic
npm ERR! argv "/mnt/app/.modulus/nvm/versions/node/v4.4.7/bin/node" "/mnt/app/.modulus/nvm/versions/node/v4.4.7/bin/npm" "start"
npm ERR! node v4.4.7
npm ERR! npm  v3.10.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: node ../../main
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node ../../main'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ../../main
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs meteor-dev-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls meteor-dev-bundle
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/app/bundle/programs/server/npm-debug.log
Now using node v4.4.7
Found package.json: ./bundle/programs/server/package.json
Start script specified in package.json: node ../../main
Running command: npm start

<EMAIL_ADDRESS>start /mnt/app/bundle/programs/server
node ../../main

/mnt/app/bundle/programs/server/node_modules/fibers/future.js:280
throw(ex);
^
Error: Module did not self-register.
at Error (native)
at Object.Module._extensions..node (module.js:434:18)
at Module.load (module.js:343:32)
at Module.Mp.load (/mnt/app/bundle/programs/server/npm/node_modules/meteor/babel-compiler/node_modules/reify/node/runtime.js:16:23)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at bindings (/mnt/app/bundle/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bindings/bindings.js:76:44)
at Object. (/mnt/app/bundle/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt/bcrypt.js:3:35)
at Module._compile (module.js:409:26)
npm ERR! Linux 3.13.0-73-generic
npm ERR! argv "/mnt/app/.modulus/nvm/versions/node/v4.4.7/bin/node" "/mnt/app/.modulus/nvm/versions/node/v4.4.7/bin/npm" "start"
npm ERR! node v4.4.7
npm ERR! npm  v3.10.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: node ../../main
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node ../../main'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ../../main
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs meteor-dev-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls meteor-dev-bundle
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/app/bundle/programs/server/npm-debug.log
Now using node v4.4.7
Found package.json: ./bundle/programs/server/package.json
Start script specified in package.json: node ../../main
Running command: npm start

<EMAIL_ADDRESS>start /mnt/app/bundle/programs/server
node ../../main

<IP_ADDRESS>
My issues on this have been enough to get me to try out Galaxy hosting from MDG. Working there so that is my work around for the time being.
Sent from my iPhone

On Aug 10, 2016, at 9:18 AM, Jeremiah Harlan<EMAIL_ADDRESS>wrote:
@gschleic what version of meteor are you using? I've seen that error before on multiple Meteor threads, but for alpha/beta (non stable) releases.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Likewise.  I got my site running on Heroku without issue using this tutorial http://justmeteor.com/blog/deploy-to-production-on-heroku/
I am still using the mongo db from modulus for now.

@Gervwyk did the issue release fix date change, "before end of week" passed ? Any new estimated date for fixing available ?

It's been 10 days and this critical issue has not been fixed, I am considering switching to another service. I feel like this happened too many times recently with Modulus.

+1
When does the fix go live?

Backend services were update on Thursday, and updated CLI pushed right after. Please try using
npm i modulus@next -g
I apologize that no one updated this thread, hopefully we have an approach now that resolves everyones issues with<EMAIL_ADDRESS>(and node 4.x).

@jackboberg the console is still throwing the same error after using the update.
server/boot.js:9:13)
    at Module._compile (module.js:456:26)

npm ERR! Linux 3.13.0-66-generic
npm ERR! argv "node" "/mnt/app/.modulus/nvm/v0.10.41/bin/npm" "start"
npm ERR! node v0.10.41
npm ERR! npm  v3.10.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `node ../../main`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node ../../main'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ../../main
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs meteor-dev-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls meteor-dev-bundle
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/app/bundle/programs/server/npm-debug.log
Now using node v0.10.41 (npm v3.10.6)
Found package.json: ./bundle/programs/server/package.json
Running command: npm start

><EMAIL_ADDRESS>start /mnt/app/bundle/programs/server
> node ../../main

assert.js:93
  throw new assert.AssertionError({
        ^
AssertionError: "undefined" === "function"
    at wrapPathFunction (/mnt/app/bundle/programs/server/mini-files.js:77:10)
    at Object.<anonymous> (/mnt/app/bundle/programs/server/mini-files.js:108:24)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/mnt/app/bundle/programs/server/boot.js:9:13)
    at Module._compile (module.js:456:26)

npm ERR! Linux 3.13.0-66-generic
npm ERR! argv "node" "/mnt/app/.modulus/nvm/v0.10.41/bin/npm" "start"
npm ERR! node v0.10.41
npm ERR! npm  v3.10.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `node ../../main`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node ../../main'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ../../main
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs meteor-dev-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls meteor-dev-bundle
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/app/bundle/programs/server/npm-debug.log

Also receiving the exact same error after updating as suggested.

@nickoj81 do you mean the same error that @hrdymchl has posted, or that you are receiving the same different error that you were getting before updating the CLI?
We also have some people sending in issues to<EMAIL_ADDRESS>with the same mini-files.js line errors. Can anyone confirm that their project which required node 4.x and did not work before, now works? If so, I'd like to close this thread and open a new issue to more directly work on the mini-files error.

I did the update as @jackboberg has proposed get now the error with the mini-file.js. So still not working.

<EMAIL_ADDRESS>start /mnt/app/bundle/programs/server
node ../../main

assert.js:93
throw new assert.AssertionError({
^
AssertionError: "undefined" === "function"
at wrapPathFunction (/mnt/app/bundle/programs/server/mini-files.js:77:10)
at Object. (/mnt/app/bundle/programs/server/mini-files.js:108:24)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/mnt/app/bundle/programs/server/boot.js:9:13)
at Module._compile (module.js:456:26)
npm ERR! Linux 3.13.0-43-generic
npm ERR! argv "node" "/mnt/app/.modulus/nvm/v0.10.41/bin/npm" "start"
npm ERR! node v0.10.41
npm ERR! npm  v3.10.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: node ../../main
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node ../../main'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ../../main
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs meteor-dev-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls meteor-dev-bundle
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/app/bundle/programs/server/npm-debug.log
Now using node v0.10.41 (npm v3.10.6)
Found package.json: ./bundle/programs/server/package.json
Running command: npm start

<EMAIL_ADDRESS>start /mnt/app/bundle/programs/server
node ../../main

assert.js:93
throw new assert.AssertionError({
^
AssertionError: "undefined" === "function"
at wrapPathFunction (/mnt/app/bundle/programs/server/mini-files.js:77:10)
at Object. (/mnt/app/bundle/programs/server/mini-files.js:108:24)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/mnt/app/bundle/programs/server/boot.js:9:13)
at Module._compile (module.js:456:26)
npm ERR! Linux 3.13.0-43-generic
npm ERR! argv "node" "/mnt/app/.modulus/nvm/v0.10.41/bin/npm" "start"
npm ERR! node v0.10.41
npm ERR! npm  v3.10.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: node ../../main
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node ../../main'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ../../main
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs meteor-dev-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls meteor-dev-bundle
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/app/bundle/programs/server/npm-debug.log
Now using node v0.10.41 (npm v3.10.6)
Found package.json: ./bundle/programs/server/package.json

I'm also getting the same error as talfco, even after the update. I have moved a instance to galaxy and all worked no problems on their system.. Please keep us posted. Would like to move the instance back to modulus.

@jackboberg I mean the same error as with mini-file.js

assert.js:93
  throw new assert.AssertionError({
        ^
AssertionError: "undefined" === "function"
    at wrapPathFunction (/mnt/app/bundle/programs/server/mini-files.js:77:10)
    at Object.<anonymous> (/mnt/app/bundle/programs/server/mini-files.js:108:24)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/mnt/app/bundle/programs/server/boot.js:9:13)
    at Module._compile (module.js:456:26)

npm ERR! Linux 3.13.0-46-generic
npm ERR! argv "node" "/mnt/app/.modulus/nvm/v0.10.41/bin/npm" "start"
npm ERR! node v0.10.41
npm ERR! npm  v3.10.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `node ../../main`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node ../../main'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ../../main
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs meteor-dev-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls meteor-dev-bundle
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/app/bundle/programs/server/npm-debug.log
Now using node v0.10.41 (npm v3.10.6)
Found package.json: ./bundle/programs/server/package.json
Running command: npm start

I've opened a new issue specifically to deal with the mini-files error. I'm going to close this issue, since we have solved using<EMAIL_ADDRESS>with<EMAIL_ADDRESS>npm i<EMAIL_ADDRESS>-g # currently tagged as 'next'
cd /your/project
modulus deploy --node-version 4

If you are trying that and still not seeing node@4 in your servo, or having issues specifically around node version during build, please re-open this issue..otherwise let's pick up more focused conversations in separate threads.

Above instructions yielded the following (I don't see how this issue is closed)
Deploying Meteor version <IP_ADDRESS>

Compressing project...
13.9 MB written
Uploading project...
Upload progress [===================] 100%
Deploying project into Meteor runtime...
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Now using node v4.4.7 (npm v3.10.5)
Initializing Meteor environment.
Using<EMAIL_ADDRESS>Node version 4 specified.
Demeteorizing application...

[Error] There was a problem deploying your project.

...and that's the whole output.

@fvpDev previously a meteor build would always use<EMAIL_ADDRESS>this issue was specifically addressing the need for some users to have<EMAIL_ADDRESS>during build/run..that is resolved.
I am opening several issues across our build and run images to address related issues now.

I tried again after deleting .meteor/local folder and it seems to demeteorize now (with the dependency issue for now, of course) but I'm not sure what got me the above error. Thanks for all your help Jack

any updates? i'm still having this issue.

@secondspace What version of the CLI are you using? Can you open an issue specific to the problem you are having, or post to an open one?

Modulus CLI is 6.3.
The error I'm receiving is the same as @nickoj81 is having above.
Thank you for promptly replying. Much appreciated.

Chipping in here. I also tried to do a deploy last night with 1.4.x on what I believe was the latest CLI, and consistently got @nickoj81's output. We had to temp deploy to Heroku. =\

@jackboberg
Seems like it demeteorizes with the correct versions of NPM & Node, but then I get this right after:
npm WARN deprecated This version of npm lacks support for important features,
npm WARN deprecated such as scoped packages, offered by the primary npm
npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
npm WARN deprecated latest stable version. To upgrade to npm@2, run:
npm WARN deprecated
npm WARN deprecated   npm -g install npm@latest-2
npm WARN deprecated
npm WARN deprecated To upgrade to the latest stable version, run:
npm WARN deprecated
npm WARN deprecated   npm -g install npm@latest
npm WARN deprecated
npm WARN deprecated (Depending on how Node.js was installed on your system, you
npm WARN deprecated may need to prefix the preceding commands with sudo, or if
npm WARN deprecated on Windows, run them from an Administrator prompt.)
npm WARN deprecated
npm WARN deprecated If you're running the version of npm bundled with
npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
npm WARN deprecated will be bundled with a version of npm@2, which has some small
npm WARN deprecated backwards-incompatible changes made to npm run-script and
npm WARN deprecated semver behavior.
Now using node v0.10.41 (npm v1.4.29)
deploy -> v0.10.41
Installing packages from /mnt/output/bundle/programs/server/package.json
WARN: npm-shrinkwrap.json will override dependencies declared in package.json.

<EMAIL_ADDRESS>install /mnt/output/bundle/programs/server/node_modules/fibers
node build.js || nodejs build.js

gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
make: Entering directory /mnt/output/bundle/programs/server/node_modules/fibers/build'  CXX(target) Release/obj.target/fibers/src/fibers.o  CXX(target) Release/obj.target/fibers/src/coroutine.o  CC(target) Release/obj.target/fibers/src/libcoro/coro.o  SOLINK_MODULE(target) Release/obj.target/fibers.node  COPY Release/fibers.node make: Leaving directory /mnt/output/bundle/programs/server/node_modules/fibers/build'
Installed in /mnt/output/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node
<EMAIL_ADDRESS>/mnt/output/bundle/programs/server
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.
Uploading completed build.
Provisioning and deploying bundle to servos...

@nickoj81's error is resolved, see https://github.com/onmodulus/docker-build-meteor/issues/28#issuecomment-240871386
I am locking this thread, please move conversation to appropriate issues. This issue was for supporting node v4, which is definitely resolved.
For every instance I have seen so far with mini-files, using modulus deploy --node-version 4 fixes it. If not, comment here: onmodulus/docker-build-meteor#28
@secondspace @eliasthompson


:vm_import feature in SupportsFeatureMixin

Added :vm_import feature to SupportsFeatureMixin that replaces
validate_import_vm method.

@miq-bot assign martinpovolny

Rubocop warning is false, elements of the hash are aligned.

Needs to be merged together with https://github.com/ManageIQ/manageiq-ui-classic/pull/2807, otherwise, this will cause UI breakages.

@miq-bot add_labels gaprindashvili/yes

Gaprindashvili backport details:
$ git log -1
commit 8d446f47875a9462a8ff6aa8cf95bf48d2c73fe2
Author: Martin Povolny<EMAIL_ADDRESS>Date:   Thu Nov 23 19:51:15 2017 +0100

    Merge pull request #16526 from smelamud/supports-vm-import

    :vm_import feature in SupportsFeatureMixin
    (cherry picked from commit a4125affe209ba97466385e8cd383b7c3ca9c62b)


install --dry-run not so dry (makes changes)

According to TFM (https://netapp-trident.readthedocs.io/en/stable-v18.10/kubernetes/deploying.html):

"The --dry-run argument tells the installer to inspect the current environment and checks that everything looks good for a Trident installation, but it makes no changes to the environment and will not install Trident."

./tridentctl install --dry-run -n trident
INFO Created installer service account.            serviceaccount=trident-installer
INFO Created installer cluster role.               clusterrole=trident-installer
INFO Created installer cluster role binding.       clusterrolebinding=trident-installer
INFO Created installer configmap.                  configmap=trident-installer
INFO Created installer pod.                        pod=trident-installer
INFO Waiting for Trident installer pod to start.
INFO Trident installer pod started.                namespace=trident pod=trident-installer
INFO Starting storage driver.                      backend=/setup/backend.json
ERRO API request failed.                           request=GetAccountByName responseCode=401 responseStatus="401 Unauthorized"
ERRO API request failed.                           request=AddAccount responseCode=401 responseStatus="401 Unauthorized"
ERRO Error detected in AddAccount API response: HTTP error: 401 Unauthorized
ERRO Failed to initialize SolidFire driver while creating account.  error="device API error" tenantName=trident
FATA Install failed; could not start the storage backend driver; problem initializing storage driver 'solidfire-san': device API error.  Resolve the issue; use 'tridentctl uninstall' to clean up; and try again.

I had a typo in my backend.json (for solidfire-san.json, concretely).
But why is it saying I should uninstall? I used --dry-run....  Fix the typo and try again:
sean@k8s1:~/trident-installer$ ./tridentctl install --dry-run -n trident
FATA Install failed; trident installer pod 'trident-installer' is already present in namespace trident; please remove it manually and try again.  Resolve the issue; use 'tridentctl uninstall' to clean up; and try again.

Oops... Okay, uninstall, fix the typo and try another dry run:
 ./tridentctl install --dry-run -n trident
INFO Created installer service account.            serviceaccount=trident-installer
INFO Created installer cluster role.               clusterrole=trident-installer
INFO Created installer cluster role binding.       clusterrolebinding=trident-installer
INFO Created installer configmap.                  configmap=trident-installer
INFO Created installer pod.                        pod=trident-installer
INFO Waiting for Trident installer pod to start.
INFO Trident installer pod started.                namespace=trident pod=trident-installer
INFO Starting storage driver.                      backend=/setup/backend.json
INFO Please ensure all relevant hosts are added to one of the specified Volume Access Groups.  AccessGroups="[2]" SVIP="<IP_ADDRESS>:3260" UseCHAP=false driver=solidfire-san
INFO Storage driver loaded.                        driver=solidfire-san
INFO Dry run completed, no problems found.
INFO Waiting for Trident installer pod to finish.
INFO Trident installer pod finished.               namespace=trident pod=trident-installer
INFO Deleted installer pod.                        pod=trident-installer
INFO Deleted installer configmap.                  configmap=trident-installer
INFO In-cluster installation completed.
INFO Deleted installer cluster role binding.
INFO Deleted installer cluster role.
INFO Deleted installer service account.

Created... and Deleted... look like changes to me.
Perhaps the doco should be changed to say it won't create changes if it can complete without errors... But that may not be how --dry-run is expected to behave, IMHO.

Good catch. This is an artifact of new installer behavior that runs the bulk of the install in the cluster itself. In order to do that it has to create temporary resources in the cluster for the installer itself, even when it's performing a dry run. It should not be leaving those resources behind if the dry run (or even a regular run) fails, however.

I think we may actually be creating changes in solidfire in successful dry runs as well. Specifically it will create the tenant/account if it doesn’t exist.

If the install fails, the installer leaves the trident-installer pod around in case any further inspection is warranted.  The uninstaller always starts by cleaning up any leftover install pod.

I think that's fine if it's not a dry run. A dry run should always leave both the cluster and the storage in the same state it was in before it started.

--dry-run is no longer needed with Trident 19.07 (or later), and is no longer in the documentation. The --dry-run feature was only needed to validate that Trident could access the backend to create it's own PV for etcd. Since Trident now uses CRDs for it's persistent storage, you don't need to check for a backend any longer.


Pre-made report for Stripe data: MRR (Monthly Recurring Revenue)

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1640
Originally created by @dmor on 2020-01-29 14:35:05

This is what the report looks like in the Stripe UI https://dashboard.stripe.com/dashboard

MRR - Definition
Stripe defines MRR as: "Monthly recurring revenue (MRR) is your normalized monthly revenue from all active subscriptions. It’s the best single measure of the health and trajectory of a recurring revenue business."
More info at https://support.stripe.com/questions/common-events-that-affect-monthly-recurring-revenue-mrr-totals
And https://support.stripe.com/questions/calculating-monthly-recurring-revenue-mrr-in-billing
Requirements

Show total aggregate amount for the time period
Show the % change over time for the total aggregate value for the period vs. the same prior period (e.g. this 4 weeks versus previous 4 weeks, this quarter versus prior quarter)
Show the individual amounts for each point shown on the graph
Default time range should be past 4 weeks
Time range should be adjustable

View 6 previous comments from the original issue on GitLab


socialnetwork_nginx-thrift_1 showing restarting

I wish to try this benchmark but I'm not sure why it's showing problem.
I noticed that I'm not able to connect to 8080 port and docker-compose ps show these 2 container as restarting always - socialnetwork_nginx-thrift_1                   /usr/local/openresty/bin/o ...   Restarting and socialnetwork_media-frontend_1                 /usr/local/openresty/bin/o ...   Restarting
It's the same problem with all three microservices for me.
Can someone please help what can be the possible issue? Thanks in advance

I'm not sure about the issue but setenforce 0 helped.
Both the containers are up now.

I'm not sure about the issue but setenforce 0 helped.
Both the containers are up now.


Delete all data if a dataset gets deleted

we only logically delete a dataset, but all data and the partition tables should be removed in that case.
Import metrics and file stored trees also need to be removed

The metadata should stay as it was so we still know what the record is about.
We only logically delete dataset records, i.e. we set the deleted timestamp.
Deleted datasets will not show up in dataset searches anymore.
But you can still call them by their id if needed.
Where does a deleted dataset show up wrongly?
The frontend needs to mark a deleted dataset somehow like we do in GBIF:
https://www.gbif.org/dataset/587b0989-6ade-4c6d-b366-ffdc70396159


Switch to poetry-core

Description
poetry-core is intended to be a light weight, fully compliant, self-contained package allowing PEP 517 compatible build frontends to build Poetry managed projects.
Using poetry-core allows distribution packages to depend only on the build backend.
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[x] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR

NOne

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to @fabaff for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

Hi @fabaff, what's the goal of this PR? How does it change our workflow?
I was thinking of migrating to PDM in future as I find it having a better dev experience, but I'm waiting for autopub to add support for it before being able to switch :)

I'll close this PR since we might move to PDM or Hatch in future 😊

@patrick91 https://python-poetry.org/docs/pyproject/#poetry-and-pep-517

I guess it will be, and couldn't find any info that it is.
https://github.com/python-poetry/poetry-core

In most cases, the usage of this package is transparent to the end-user as it is either made use by Poetry itself or a PEP 517 frontend (eg: pip).

Prior to the release of version 1.1.0, Poetry was a project management tool that included a PEP 517 build backend. This was inefficient and time consuming when a PEP 517 build was required. For example, both pip and tox (with isolated builds) would install Poetry and all dependencies it required. Most of these dependencies are not required when the objective is to simply build either a source or binary distribution of your project.
In order to improve the above situation, poetry-core was created. Shared functionality pertaining to PEP 517 build backends, including reading lock file, pyproject.toml and building wheel/sdist, were implemented in this package. This makes PEP 517 builds extremely fast for Poetry managed packages.


Export shared getFormatter() method for grunt-nsp module

Ref: https://github.com/nodesecurity/grunt-nsp/issues/19
Saves having to copy-pasta that utility function to grunt-nsp and probably gulp-nsp.

good call! thanks @pdehaan

Not entirely related, but more of a side conversation, but I think we're also having some unexpected side effects from using shrinkwrap. In trying to debug this today, I realized that the package.json file uses some semver range operators so it looks like it would install "nsp": "^2.3.0", but because of the npm-shrinkwrap.json file, it will always only install exactly "version": "2.3.0" — which means we'd have to regenerate the npm-shrinkwrap.json file every tiem we release a new version of nsp.

are you referring to your app that uses nsp? do you have it in your devDependencies?

@nlf, sorry, I was referring to the grunt-nsp module directly.

ah, then yes you're absolutely correct. since nsp is the only dependency there though and it has its own shrinkwrap, i'll remove it from grunt-nsp. gulp-nsp only has one other dependency so i'll have to evaluate how i feel about removing the shrinkwrap there.


[SPARK-20690][SQL][WIP] Analyzer shouldn't add missing attributes through subqueries

What changes were proposed in this pull request?
We add missing attributes into Filter in Analyzer. But we shouldn't do it through subqueries like this:
select 1 from  (select 1 from onerow t1 LIMIT 1) where  t1.c1=1

This query works in current codebase. However, the outside where clause shouldn't be able to refer t1.c1 attribute.
How was this patch tested?
Jenkins tests.
Please review http://spark.apache.org/contributing.html before opening a pull request.

Test build #76743 has started for PR 17935 at commit bb16061.

Test build #76745 has started for PR 17935 at commit 974217f.

Test build #76743 has finished for PR 17935 at commit bb16061.

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

Merged build finished. Test FAILed.

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

Test build #76745 has finished for PR 17935 at commit 974217f.

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

Merged build finished. Test FAILed.

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

Test build #76771 has started for PR 17935 at commit 51aafde.

Test build #76771 has finished for PR 17935 at commit 51aafde.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ColumnStatsMap(originalMap: AttributeMap[ColumnStat])
              s\"($

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

Merged build finished. Test FAILed.

Test build #76772 has started for PR 17935 at commit c19cbbb.

Test build #76772 has finished for PR 17935 at commit c19cbbb.

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

Merged build finished. Test FAILed.

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

Test build #76783 has started for PR 17935 at commit a904214.

Merged build finished. Test FAILed.

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

retest this please.

Test build #76785 has started for PR 17935 at commit a904214.

Test build #76785 has finished for PR 17935 at commit a904214.

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

Merged build finished. Test PASSed.

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

cc @cloud-fan

Test build #76969 has started for PR 17935 at commit 1e595b2.

Test build #76969 has finished for PR 17935 at commit 1e595b2.

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

Merged build finished. Test FAILed.

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

Test build #76994 has started for PR 17935 at commit 9ec0414.

Test build #76994 has finished for PR 17935 at commit 9ec0414.

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

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

Merged build finished. Test PASSed.

Sure.
On May 17, 2017 12:10 PM, "Wenchen Fan"<EMAIL_ADDRESS>wrote:

@cloud-fan commented on this pull request.
In sql/core/src/test/scala/org/apache/spark/sql/CachedTableSuite.scala
https://github.com/apache/spark/pull/17935#discussion_r116906916:

@@ -631,13 +631,13 @@ class CachedTableSuite extends QueryTest with SQLTestUtils with SharedSQLContext
val ds2 =
sql(
"""

       |SELECT * FROM (SELECT max(c1) FROM t1 GROUP BY c1)

       |SELECT * FROM (SELECT max(c1) as c1 FROM t1 GROUP BY c1) t1

can you pick another name? t1 appeared twice...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/17935#pullrequestreview-38566144,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEM97DecogWUFu4HTI-KqSoijpKuJPsks5r6nMcgaJpZM4NWVlc
.

Test build #77007 has started for PR 17935 at commit 9b117f4.

thanks, merging to master!

oops, you pushed a new commit... But it should be fine as the change is very small.

Thanks @cloud-fan @hvanhovell @gatorsmile @wzhfy

@cloud-fan Yeah, I change the aliased name in one test. I tested it locally.

Test build #77007 has finished for PR 17935 at commit 9b117f4.

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

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

No problem. The new commit passes tests.

I was trying to run a test case from another database which does support unaliased subqueries in the FROM clause and hit a confusing parser error due to this patch's behavior change. While I agree that we shouldn't necessarily support this syntax, I think that the current error message that we're returning isn't very good so I've file https://issues.apache.org/jira/browse/SPARK-20916 to improve it.

@JoshRosen Thanks for filing this issue. I'll look into it.

@JoshRosen what was the other type of database you were using?

@ash211, I was attempting to re-use test cases from CockroachDB (which is surprisingly permissive in the SQL it accepts compared to Postgres).

Guys - isn't this API breaking?

Also the description / title is completely different from the JIRA ticket.

@rxin Sorry I forgot to change JIRA ticket. I changed it now.

Other committers please revert this change until we find a solution or verify that almost no users write queries like this.

I'm ok to revert this. Just a little reference.
Seems it is required to have alias name for derived table:
https://github.com/ronsavage/SQL/blob/master/sql-2003-2.bnf#L2221
And as investigating before, MySQL, Postgres, Oracle require alias name for derived table.
So it seems to me that the syntax of no alias name is incorrect and the users tending to write queries like this is expected to be few.
For your reference.

I don't think that argument is useful at all. For example, none of the other databases support the DataFrame API. Does that mean few users will write DataFrame code?

Sorry, to be accurate, for the syntax of derived table in SQL, the databases I listed above are commonly seen in the market, and they don't support it without alias name. SQL 2003 grammar also doesn't support it.
Based on the above, I'd tend to think that derived table without alias name is not a widely used syntax among database users.
But we know there's exception such as CockroachDB, as @JoshRosen pointed out.
This isn't an argument to object reverting, rather just a reference for you to decide on this issue.

The reason I found out about this is because the one of the widely circulated TPC-DS benchmark harness online uses this.


macos: --disable-xattr

As in (Linux only)  patch 9.0.1962 we can disable the check on macOS
Follow-up: https://github.com/vim/vim/pull/13229

I don't this is right. This just makes sure, that the CI is compiled with non-xattr support, but we should rather disable xattr completly when compiling on Mac OS X. (because otherwise all Mac users will have to add the new configure flag --disable-xattr). At least until we have working xattr support on Mac OS X
That's what #13232 is trying to perform.


Instantiate a Session with an existing session id

What is the expected feature or enhancement?
One should be able to instantiate a Session object with an existing session id str.
Acceptance criteria
Users should have the ability to instantiate a Session object with its private _session_id attribute set.
One implementation might look like:
session_id: str = ...
session = Session.from_id(session_id)

One use case / need for this is: A user is submitting consecutive jobs to the backend within a session, and their kernel crashes. They cannot easily instantiate a new Session object and resume their work before the timeout. They would need to use a different/more complicated interface (QiskitRuntimeService.run).
Another use case is: A user who has a Session instantiation inside a remote function. Provider is not serializable, so it is often difficult to pass Qiskit Runtime objects to cloud functions. It may require passing a QiskitRuntimeService and the Provider/Session be spun up inside the remote function.
In this case, a user may want to also submit a session_id to the remote function, so when they instantiate the new Session, they can easily get back to the front of the queue. The service.run interface is more difficult to deal with in my experience.


Can i run on windows?

I tried to run on windows and i get this error
ERROR:    Traceback (most recent call last):
  File "C:\streamlit-llama\venv\lib\site-packages\starlette\routing.py", line 677, in lifespan
    async with self.lifespan_context(app) as maybe_state:
  File "C:\streamlit-llama\venv\lib\site-packages\starlette\routing.py", line 566, in __aenter__
    await self._router.startup()
  File "C:\streamlit-llama\venv\lib\site-packages\starlette\routing.py", line 654, in startup
    await handler()
  File "C:\streamlit-llama\api.py", line 22, in startup_event
    app.state.model = load_model()
  File "C:\streamlit-llama\api.py", line 15, in load_model
    return AutoModelForCausalLM.from_pretrained(
  File "C:\streamlit-llama\venv\lib\site-packages\ctransformers\hub.py", line 168, in from_pretrained
    return LLM(
  File "C:\streamlit-llama\venv\lib\site-packages\ctransformers\llm.py", line 206, in __init__
    self._lib = load_library(lib, cuda=config.gpu_layers > 0)
  File "C:\streamlit-llama\venv\lib\site-packages\ctransformers\llm.py", line 102, in load_library
    lib = CDLL(path)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.3056.0_x64__qbz5n2kfra8p0\lib\ctypes\__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
FileNotFoundError: Could not find module 'C:\streamlit-llama\venv\Lib\site-packages\ctransformers\lib\avx2\ctransformers.dll' (or one of its dependencies). Try using the full path with constructor syntax.

ERROR:    Application startup failed. Exiting.

Windows 11

Windows 10 and python 3.10 is working for me just fine.

are you using conda ?

No not using Conda. Just ordinary or "vanilla" python.
> py -3.10
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>

I most likely just installed the .exe executable from and added PATH during the installation:

https://www.python.org/downloads/release/python-3106/

I think this one:
`

Windows installer (64-bit)
Windows
Recommended
8f46453e68ef38e5544a76d84df3994c
28916488
SIG

[Windows installer (64-bit)](https://www.python.org/ftp/python/3.10.6/python-3.10.6-amd64.exe)	Windows	Recommended	8f46453e68ef38e5544a76d84df3994c	28916488	[SIG](https://www.python.org/ftp/python/3.10.6/python-3.10.6-amd64.exe.asc)`

I have the same issue in Mac OS X, with python 3.10, ctransformers <IP_ADDRESS> (the last) using Conda


Pass Inputs dictionary

Description
Aligning Inputs between problem, observer and model.
Issue reference
Fixes #358.
Review
Before you mark your PR as ready for review, please ensure that you've considered the following:

Updated the CHANGELOG.md in reverse chronological order (newest at the top) with a concise description of the changes, including the PR number.
Noted any breaking changes, including details on how it might impact existing functionality.

Type of change

[ ] New Feature: A non-breaking change that adds new functionality.
[ ] Optimization: A code change that improves performance.
[ ] Examples: A change to existing or additional examples.
[ ] Bug Fix: A non-breaking change that addresses an issue.
[ ] Documentation: Updates to documentation or new documentation for new features.
[ ] Refactoring: Non-functional changes that improve the codebase.
[ ] Style: Non-functional changes related to code style (formatting, naming, etc).
[ ] Testing: Additional tests to improve coverage or confirm functionality.
[ ] Other: (Insert description of change)

Key checklist:

[ ] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All unit tests pass: $ nox -s tests
[ ] The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.
Further checks:

[ ] Code is well-commented, especially in complex or unclear areas.
[ ] Added tests that prove my fix is effective or that my feature works.
[ ] Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

The diff of this PR is 100% covered and I've added a number of tests but the project coverage is still down by 0.11%. I think it might worth continuing with the review despite this.

Note that there will be conflicts with #352, as mentioned here: https://github.com/pybop-team/PyBOP/pull/352#issuecomment-2165214729

Thanks for the helpful chat @BradyPlanden! I've added a parameters.verify function, so I think this is now ready for review.

Hi @BradyPlanden, thanks for the review. The two failing integration tests also fail when run with matching parameter values on develop. Should I investigate on this branch or shall we leave this for #338?

Noting that I applied the suggestions by @BradyPlanden to revert the passing of inputs as dictionaries, back to lists, in the tests. We will continue to support lists of parameter values, although it is safer to use dictionaries. The allowable Inputs are defined in Parameters verify.


Add simple download progress tracker

#5925
Adds a progress bar when downloading a platform
The progress bar looks like this:
[0.1 / 72.5 MB]

It should be easy to use idicatif for a more graphical bar in the future, but I think this one is good enough

progress bar now prints this if we don't know the total size:
[0.1 MB]

otherwise this:
[0.1 / 70.0 MB]


No handlers found: "torchvision::roi_align". Skipped

Thank you for your great work!
I encountered this warning when using torchprofile. It seems like torchprofile cannot calculate the MACs of
UserWarning:  No handlers found: "torchvision::roi_align". Skipped
UserWarning: No handlers found: "aten::sqrt". Skipped
UserWarning: No handlers found: "aten::log2". Skipped
UserWarning: No handlers found: "aten::reciprocal". Skipped.
UserWarning: No handlers found: "aten::scalarimplicit". Skipped.
UserWarning: No handlers found: "aten::max". Skipped.
By the way, apart from the MACs, Is there any way to calculate the model memory use?

Thanks for reporting this issue. Most of these operators have no MACs or very few MACs, so the MACs should be roughly correct. I will work on supporting these operators.

Hi,
I met a similar warning when profiling my customized model wich contains of custom layers with some operators like permute, reshape and einsum.
Here's the log:
[/home/tien/anaconda3/lib/python3.9/site-packages/torchprofile/profile.py:22](https://file+.vscode-resource.vscode-cdn.net/home/tien/anaconda3/lib/python3.9/site-packages/torchprofile/profile.py:22): UserWarning: No handlers found: "aten::copy_". Skipped.
  warnings.warn('No handlers found: "{}". Skipped.'.format(
[/home/tien/anaconda3/lib/python3.9/site-packages/torchprofile/profile.py:22](https://file+.vscode-resource.vscode-cdn.net/home/tien/anaconda3/lib/python3.9/site-packages/torchprofile/profile.py:22): UserWarning: No handlers found: "aten::permute". Skipped.
  warnings.warn('No handlers found: "{}". Skipped.'.format(
[/home/tien/anaconda3/lib/python3.9/site-packages/torchprofile/profile.py:22](https://file+.vscode-resource.vscode-cdn.net/home/tien/anaconda3/lib/python3.9/site-packages/torchprofile/profile.py:22): UserWarning: No handlers found: "aten::reshape". Skipped.
  warnings.warn('No handlers found: "{}". Skipped.'.format(
[/home/tien/anaconda3/lib/python3.9/site-packages/torchprofile/profile.py:22](https://file+.vscode-resource.vscode-cdn.net/home/tien/anaconda3/lib/python3.9/site-packages/torchprofile/profile.py:22): UserWarning: No handlers found: "aten::einsum". Skipped.
  warnings.warn('No handlers found: "{}". Skipped.'.format(

I guess it doesn't affect the final result. Just mentioning.
Thanks!


Possible bug: Biodiversity::Parser.parse() complains about two arguments given

Hi,
Just installed the latest biodiversity gem.
When trying the example:
Biodiversity::Parser.parse("Plantago major", simple = true)

I get that error:
/root/.gem/gems/biodiversity-5.5.2/lib/biodiversity/parser.rb:36:in `parse': wrong number of arguments (given 2, expected 1) (ArgumentError)

Has the API changed? If so then the example could perhaps be modified.

Yes, it did. README might be outdated.
https://github.com/GlobalNamesArchitecture/biodiversity/blob/c3b75547afdc5b5cb1e18c7a9072d47aa3672d9b/lib/biodiversity/parser.rb#L36
Correct form would be Biodiversity::Parser.parse("Plantago major", simple: true)

Thanks for spotting outdated bits in the README, fixed now.


[Bug]: setting cookies for some GET requests causes session problems

Actual Behavior
When you log into the system, and then refresh home page or any other page, the user will be logged out. But this scenario happens when PrestaShop sets two cookies instead of a cookie for sessions. So, the wishlist, cart, addresses, and other GET requests will replace wrong cookie and the customer will log out..
setting cookies for cart and wishlist get requests causes session problems
Possible Solution
No response
Steps to reproduce
No response
What version of PrestaShop integration are you using?
any
What version of Node.js are you using?
any
What browser (and version) are you using?
any
What operating system (and version) are you using?
any
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This issue written when I got the error:
https://github.com/vuestorefront-community/prestashop/issues/137
but fix related to the current issue will be a refinement not a solution to the issue 137.


Simplify reader/writer classes

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
Accounts for #193
Can review in commit order :)
Tests
All GDK tests pass
Local deployment still works with monobehaviours (the spinner spins!)
Primary reviewers
If your change will take a long time to review, you can name at most two primary reviewers who are ultimately responsible for reviewing this request. @ mention them.
@zeroZshadow @MPeti01

Rebasing

rebase complete, diff looks good


Optimise command registration

By only getting all the online players once, this should speed the server startup time by a few minutes or ~23 seconds per plugin.
Example from the log files
[05:43:21] [Server thread/INFO]: [CivChat2] Connected to database!
[05:43:44] [Server thread/INFO]: [CivChat2] [CivChatCommandManager] Command [Afk] registered.

Semi-duplicate of #339

I missed that one


How can I call this in a jest test? with typescript?

https://github.com/miguelgrinberg/twilio-video-backgrounds/blob/0f1fc3671e92fdd0fecdf13c30f095e51bd9e668/public/index.js#L13

I can't really comment without having context, but maybe you want to mock this, since there is not really much this class can do that is testable?


Remove dependence on faPlotLength

Currently, we require that each fiber in a bundle has the same length. While looking to solve #184, I realized that these should all be the same length but there's no reason that it has to be faPlotLength. So this PR removes the dependence on faPlotLength and the supporting waiter function.
This does not resolve issue #184 since it still requires each fiber in a bundle to be the same length (that length can be different for each bundle). See the discussion on #184 for that.

This looks good to me, but let's merge #185 first.

Rebased onto master after the merge of #185.

@richford should I test this or does it need to be rebased?

Just rebased.

Tested this in 2 ways - by removing all nodes >20 and removing all nodes <80. It worked fine in both cases. But the x-axis should be rescaled based on the number of nodes. See below image. Ideally, the min and max of the x-axis would reflect the true number of nodes. In the tracula case we will have many fewer nodes so it would be good to still use the full axis length

This PR was more about the 3D panel. We wanted to eliminate the dependence in the 3D panel on faPlotLength to prepare for the TRACULA data, which has variable length bundles. So I think to test it out, we'd need to vary the number of nodes in each streamline in data_partial.json, rather than in nodes.csv. The TRACULA data has varying node numbers for each bundle so that should test out this change. For the 2D plots issue that you brought up, I think it might be best to open a new issue.

@richford @jyeatman I opened #196 to address the 2D plots issue. Working on it this morning.


Fix incorrect order in JSON output

I found out that dict.values() and json.dumps() will break the current order of dict.
I tried to use OrderedDict instead of dict and the issue was resolved.

Working on https://github.com/jorgebastida/glue/compare/pr/186 - Python 2.6 doesn't support OrderedDict


Distinction between Elan and JS libraries

This should be read in conjunction with #199.
We need to be able to distinguish between .JS libraries that have been compiled from Elan source, and others. Probably the Elan libraries must include the source code (as well as object code) and both include the hash.
Compiled Elan libraries
May be called directly as procedures and/or trusted functions.
JS libraries
How do you even know whether a method is going to return something?
How do we handle type conversion?

Covered elsewhere


[Spark] [Fuzzer] Common eval throws after retry success.

Description
Currently when  an expression fails in expression fuzzer we run it with try enabled and verify that both common eval and simplified eval show similar results. If this succeeds we again verify against the non - errored rows and expect no errors to be thrown in common or simple eval.
In the expression below we see that we are seeing an error when verifying after retry.
Error Reproduction
Flags:
--retry_with_try
--repro_persist_path=/Users/kpai/src/Velox/_velox_errors
--enable_variadic_signatures
--velox_fuzzer_enable_complex_types
--velox_fuzzer_enable_column_reuse
--velox_fuzzer_enable_expression_reuse
--lazy_vector_generation_ratio
0.2

Seed :<PHONE_NUMBER>
Unfortunately in this particular case I cant attach a repro as fuzzer creates constant varbinaries in sql which currently cant be sql'ized (#4243 )
Relevant logs
No response

this is not happening over and over an is old plus we do not have artifact to reproduce there is nothing we can do here.


Use exact match when checking PR title

Proposed fix for #25
hub pr list will only output the list of PR title.
This way we can use grep -Fx to find lines that is exact match with the UPDATE_MESSAGE
The downside is that the link to PR will not be shown on the output anymore

Going with #27


Feat: add SignUp with google option in create account section

Is your feature request related to a problem? Please describe.
I often find it frustrating to create new accounts on different platforms because it requires filling out multiple fields and remembering yet another password. This process is time-consuming and can lead to lower user engagement and higher bounce rates on the registration page.
Describe the solution you'd like
would like to implement a "Sign Up with Google" option in the "Create Account" section. This feature should allow users to quickly and securely sign up for an account using their Google credentials, reducing the friction associated with the sign-up process. Here's a step-by-step plan to integrate this feature:
go to website and click on user login
click on SignUp
add SignUp with google option above the signup option.
ScreenShot:

@jaibhedia please assign this issue to me under Gssoc'24

I want to work on this issue. Please assign it to me.


Data Structures: Size of the Set

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Closes #XXXXX

@ezioda004, @cmccormack This PR is stale now.  What can we do to get it fixed and merged?

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason: Since your PR was created, the master branch content has updated making some of your changes unnecessary or need to be reorganized to fit the current version.  Please re-sync your fork so you are looking at the latest version of master and then create a new PR if you find any changes warranted.  The challenge file being changed is no longer present in the repo due to merging of PR 34717 which combined 3 challenges into one.  In a separate PR, we will delete the guide article (present on this PR) as it is no longer needed.
Thank you and happy coding.


Fix typo ElaspedTime in Metrics

@MirekVales -
Thanks for submitting. Since this would be a breaking change to a public class, we would have to release in a major release.
-Jeff

Guys, the CLA signing does not work correctly. I can see "Individual contributor agreement. Signed already." but the robot has closed it anyway due to timeout.

Hi @MirekVales - please can you check the same email you used to sign the commit is the same one you use for github please. That's how it verifies the CLA has been signed.
Thanks


Sharing browsers with VSCode Live share inside of Remote SSH

Hi,
The Situation:
Because of company policies I a forced to work on a company laptop without admin rights. I do have access to an Azure VM (linux) where I do have admin rights. So I connect to the VM using Remote SSH extension. When I am connected I use the Live share extension to pair program with other people.
The Problem:
We both have the browser preview extension installed but only the person who joins the session can see the "shared browser" section when going to the live share panel.

Do both of you have Chrome installed on your Azure VM?

Closing due to inactivity.


fix: encode search keyword

Fix #2901

Note: need to review as encoding the keyword is a change in behavior and might cause a breaking change.

@dyaskur thanks for the review. However, adding is_encoded:true in the script will not affect the serverSide implementation as the js library will not send it back in the ajax request.
How about if we add another control on a column level that toggles encoded search? Maybe something like:
->encodedSearch(['col1', 'col2'])

I see, I thought datatable will send all column attribute to the ajax request. If can't send by client side, we need to set it on server side. And I think your idea looks a good idea.

@yajra , recently came up with a similar solution while debugging a weird behavior with the collection as a source. This change adds equality to a search input and modified collection at DataProcessor escapeRow which uses laravel's e() func.
Any estimates on when this will be merged?

@aravael, would you be able to test this and see the impact on your existing project? Would you approve this PR?

Hi @yajra . Recently managed to test it, can't approve this patch. Though it fixes the collection search, it breaks the builder source. Since we sanitize the input with e(), the database data are still not modified, therefore not found the result.
It works with a collection because both the collection  and input sanitized. In case of builder source it doesn't work that way. Need to process that out.


more info

Can I use this code for free in my application? Are there any licensing issues involved?

@shantanuo, you can use it under the terms of the MIT license. See https://github.com/geopy/geopy/blob/master/LICENSE.


ESO Status command

A status command for the popular video game “Elder Scrolls Online” by Zenimax Media

I will deploy it for now as private, will complete it and open to public l8er


[BUG] ui console error

Describe the bug

To Reproduce
Steps to reproduce the behavior:

click any tab menu
click Harvester logo

Expected behavior

no any error
Log

Environment:

Harvester ISO version:
Installation Mode: ISO/app-mode
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Tested in master-f38adc70-head. Verified as fixed. No console error


add max gauge type to registry

This was added a while back to the AtlasRegistry for
use in the aggregator service and is used internally
to timer and distribution summary implementations. To
make things more consistent it is being added to the
main registry interface.

Build failure is due to travis issues:

We are now also seeing builds timing out on the sudo-enabled infrastructure (i.e. builds with sudo: required). We are continuing to look into it. Thank you for your patience.
May 9, 13:52 UTC


support windows arm64

I'm not sure if github action supports windows arm64 but you could quite easily build and exe for yourself. Just install clone the repo.
Install dependencies
python -m pip install -r requirements.txt pyinstaller

Then run pyinstaller
pyinstaller main.py --onefile --add-data=assets:assets --hide-console hide-late --uac-admin


LDAP sync: add field to person in Biblio which stores the current UGentID

Story
Add a field to the person model in Biblio Frontend API which stores the current UGentID.  For active users, this will make it less error prone to generate the phonebook link in the backoffice and frontend.
The field is populated when cron job triggers the nightly LDAP sync.

Needs actionable example

@netsensei Does this story belong in the person service? https://github.com/ugent-library/person-service

@mietcls closing, already implemented in new person service


Please inquire about the current availability of this project

Hi,I run lsp.tcl directly, hover can do not work, can you help me.

Hi,
This LSP is just a test vehicle for me, nothing like production ready. Sorry about that, but making a LSP for Tcl is a big task.
Kind regards,
Jos.

OK, thanks.


Fullcalendar not rendering fully inside a Jquery-steps tab.

as the title says.

I tried using the .fullCalendar('render') on onStepChanging function still it's not rendering fully.
[UPDATE]
I SOLVED it by calling the fullcalendar  before calling the steps.
[UPDATE2]
i forgot to test the calendar itself, it actually renders but it is now frozen, when I click the arrows it doesn't change months.

Hi mickaboy72 - did you ever find a solution to this issue?

http://stackoverflow.com/questions/39487356/fullcalendar-within-jquerysteps/39487552#39487552


KAFKA-5043 : Add FindCoordinatorRPC stub and update InitPidRequest for transactions in KIP-98.

cc @ijuma @mjsax @dguy

So I did an audit of the usages of all the renamed exceptions. They are all retriable, and are handled in JoinGroup, SyncGroup, the heartbeat thread, and during offset commits.
In all cases but one, the operations are retried when they hit a retriable exception, so these should not be returned to the client.
The one case where the behavior is unclear is in commitOffsetsAsync() : https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java#L524
I think in this case, the exception is returned to the user. If this true, it seems like we will have to either:

Introduce new error codes and exceptions for the transaction coordinator.
Reuse the GroupCoordinator errors and exception codes for the transaction coordinator.

Neither of these is ideal, but seems unavoidable unless I am wrong.
@ijuma : in the async offsets commit path, am I reading the code wrong? Or are the retriable exceptions really returned to the user?

Thanks, LGTM. Included the changes from https://github.com/apurvam/kafka/pull/3 before merging.


migrate regression/product-details to cypress

See #1102 for original spike.
Take a look at big happy path for example.
See cypress video in our wiki.
Likely doesn't have login but if it needs login, set this to FR2 (and do after #1216).
all epic/cypressmigration tickets should be merged into epic branch "epic/cypressmigration-fr1".
if this epic branch doesn't exist, you're probably the first, so create it.

Skipped one test (should contain tabs with correct text) since #1408 is not resolved


Unable to View Messages

Expected behavior
When I tap on a message, I should be able to read that message.
Actual behavior
The message opens, but the message contents are missing.
Steps to reproduce

Tap on Google email message.
Message opens.
There is no message.
Rinse and repeat for each Google email account.
Try uninstalling and reinstalling. No change.

Environment
K-9 Mail version: 5.110
Android version: 5.0.1
Account type (IMAP, POP3, WebDAV/Exchange): IMAP

Please attach the source of the message that doesn't show and/or record a debug log: https://github.com/k9mail/k-9/wiki/LoggingErrors


Inspect Queue Behaviour

If problematic, implement your own queue using localStorage or sessionStorage

I'm closing this issue and creating a new issue for implementing my own queue function.


MPF crashes if no coils or switches are defined

It would be nice for testing other things (shows, etc.) if it didn't crash.

Fixed in 0.18.0a9


Revert "Update README.md"

Reverts paritytech/companion-for-processbot-staging#27
companion: https://github.com/paritytech/companion-for-processbot-staging#28

bot merge


Rework the cmd package to remove the indexer type and move it into it…

…s own configurable package

Closes #78


chore: fix up subscribe/unsubscribe

Codecov Report

Merging #129 into gsv1.1 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           gsv1.1     #129   +/-   ##
=======================================
  Coverage   91.66%   91.66%
=======================================
  Files           2        2
  Lines          24       24
=======================================
  Hits           22       22
  Misses          2        2

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 4841fd4...cd61649. Read the comment docs.


xESMF regridding showing repeated values at latitude poles?

I am working on regridding a three-dimensional (time, lat, lon) xarray dataset on a global scale, using bilinear interpolation. Everything is working as it should, except for at the poles (latitudes -90 and 90), where it shows repeated values (2.58851004e+00,  2.58851004e+00,  2.58851004e+00, ...) for each variable. I have also compared it with the CDO regridder to verify, and it showed differences of 0 at every lat/lon point, save for lats -90 and 90. Is there a fix for this?

This version of the package is no longer maintained. Would you mind moving your issue to https://github.com/pangeo-data/xESMF?

Will do! Thank you
On Thu, Nov 18, 2021 at 9:06 AM Ryan Abernathey @.***>
wrote:

This version of the package is no longer maintained. Would you mind moving
your issue to https://github.com/pangeo-data/xESMF?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JiaweiZhuang/xESMF/issues/124#issuecomment-972895997,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AONFLCWIWCNDVDBBBIRJFJLUMUB6LANCNFSM5HOF2MBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Maggie Trimpin
Pronouns: She/Her
Towson University
B.S | Computer Science

@.*** @.**>
443-909-8322


neo-cli fails to run

System: Windows 10 1709
neo-cli version: 2.4.1
dotnet neo-cli.dll --rpc

Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'libleveldb': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
   at Neo.Implementations.Blockchains.LevelDB.Native.leveldb_options_create()
   at Neo.Implementations.Blockchains.LevelDB.LevelDBBlockchain..ctor(String path)
   at Neo.Shell.MainService.OnStart(String[] args)
   at Neo.Services.ConsoleServiceBase.Run(String[] args)
   at Neo.Program.Main(String[] args)

Is the LevelDB not included, or is missing from this build..?

The latest version has included it.

Thanks @erikzhang ! But...
dotnet neo-cli.dll
Error:
  An assembly specified in the application dependencies manifest (neo-cli.deps.json) was not found:
    package: 'Newtonsoft.Json', version: '10.0.1'
    path: 'lib/netstandard1.3/Newtonsoft.Json.dll'

Using the new release (v.2.5.0). I'd love to help here, but .Net, not so much for me.

Try this:
neo-cli.exe

It is very important that dotnet neo-cli.dll works.
This allows for all kinds of cross platform integrations on *nix systems, for instance the private network Docker image: https://github.com/CityOfZion/neo-privatenet-docker

If you need to use dotnet neo-cli.dll, you have to install .NET Core Runtime 2.0 first.

Oh alright, sorry I think I've mixed things up ^^ I just noticed that the Docker image doesn't work when upgrading to neo-cli 2.5.0, but haven't had the time to look into the cause and assumed this may be related. I'll check later today! Thank you ;)


Under search "Angebote" field of search Area "von Grösse" is not defined.

when size of the Zimmer or any Apartment is typed in the search field and click to "Suche"
All Search result appear

@Dummylearners this seems to be a dublicate of

Yes, it is. the ticket will be combined with #286 in the upcoming backlog refinement


FYI Don't upgrade to Stack Heroku-16

In the settings section of an app in Heroku, there's now an option to upgrade to new Stack (if you were using old Cedar-14 Stack)

In the changelog of the new stack, they state among the changes that the HEROKU_ namespace for config vars is reserved, and its recommended to not set variables with that namespace to avoid conflicts.

The HEROKU_ namespace is reserved for config vars set by the Heroku platform in order to offer functionality. If you have created HEROKU_ config vars, we suggest you change them when upgrading to Heroku-16, in order to avoid config var conflicts.

And as the setup of this gem requires:

Add your Heroku app name / API key as config vars to your Heroku instance.
heroku config:add HEROKU_API_KEY=yourapikey APP_NAME=yourherokuappname

It's better to avoid upgrading, at least until the gem supports a different config var name.

Thank you for this report, I'll look into changing this config var to another name.

I've released version 2.1.0 to address this issue. Can you verify the new version works correctly?
I've tested the new version in my own production apps and it I haven't encountered any errors.

Hi @davidakachaos I've found another occurrence of the HEROKU_API_KEY in the scaler file. Should that be changed too?

Please go to this issue on the Workless repository. Thank you!


oadp-1.1: OADP-1150 Add Env to dpa.Spec.PodConfig

Makes Velero and Restic pods Environment variables configurable.
OADP-1150

Codecov Report
Base: 33.54% // Head: 33.45% // Decreases project coverage by -0.09% :warning:

Coverage data is based on head (8dbcec1) compared to base (0204698).
Patch coverage: 35.48% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##           oadp-1.1     #886      +/-   ##
============================================
- Coverage     33.54%   33.45%   -0.09%
============================================
  Files            17       17
  Lines          3151     3171      +20
============================================
+ Hits           1057     1061       +4
- Misses         2002     2018      +16
  Partials         92       92

Impacted Files
Coverage Δ

pkg/common/common.go
42.42% <0.00%> (-39.93%)
:arrow_down:

controllers/velero.go
57.22% <60.00%> (+0.23%)
:arrow_up:

controllers/restic.go
52.38% <100.00%> (+0.18%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

/retest

/retest

2023/01/26 20:42:03 command: /usr/bin/bash /go/src/github.com/openshift/oadp-operator/docs/scripts/dc-restic-post-restore.sh mysql-restic-e2e-836a8451-9db9-11ed-9210-0a580a8022d5
2023/01/26 20:42:03 stdout: using OADP Namespace openshift-adp
restore: mysql-restic-e2e-836a8451-9db9-11ed-9210-0a580a8022d5
label: mysql-restic-e2e-836a8451-9db9-11ed-9210-0a580a8022d5
Deleting disconnected restore pods
2023/01/26 20:42:03 stderr: &{%!s(int=32768) Unable to connect to the server: dial tcp <IP_ADDRESS>:6443: i/o timeout

/retest

/retest


Read and store joypad events in a separate thread on x11 platform

Currently, joypad events are only read once every iteration. As demonstrated in #55850, this can result in joypad events being missed. The OS will drop old events in its queue if they are not read and its queue gets full.
This PR creates a separate thread to read the OS' joypad events and store them in a Godot queue until they are processed. This PR only fixes the Linux platform. The other platforms probably need to be updated in the same way.
Note: A lot of the changes are around updating the mutexes; as there are now three threads trying to access the joypads array:

Instead of putting a mutex on methods that may access this array, the mutex is now used to protect access to the Joypad elements at the time they're accessed.
To minimise the time a mutex is locked (when looping through the array) which may delay other threads, each Joypad element in the array now has its own mutex.
To minimise the use of mutexes and the risk of deadlocks, access to the arrays is now only done when opening or closing a connection to a joypad or reading and writing to the Joypad event queues.
Instead of being allowed to access the arrays themselves, other methods are passed a reference to the mutex protected Joypad element.

Fixes #55850.

Sorry for the delay reviewing. Should be fine to merge after a rebase.

Thanks!


Comments could not be fetched

Of late pipe-viewer is unable to display comments for videos. This is the error-msg being displayed if I run gtk-pipe-viewer from the cmdline: [500 Internal Server Error] Error occurred on URL: https://yt.drgnz.club/api/v1/comments/UzBF_IBNi1o?hl=en-US&sort_by=top
This issue doesn't happen with gtk-youtube-viewer. Request @trizen to kindly look into this and provide a fix. Thanks in advance!

Related to: https://github.com/iv-org/invidious/issues/4566
Try to set ytdlp_comments => 1 in the config-file, to extract the comments with yt-dlp.

Hi @trizen, I tried fetching comments with yt-dlp, and it did work once. But threw the following error for subsequent instances, so I presume that something new is being worked out (as mentioned in iv-org, issue #4566):
WARNING: [youtube] UzBF_IBNi1o: Cannot decrypt nsig without player_url: You may experience throttling for some formats.
Closing this issue for now.


added support for encrypted PDF

Closes https://github.com/GrapheneOS/PdfViewer/issues/71 and https://github.com/GrapheneOS/PdfViewer/issues/15


RPC is not updated when HTML file is opened

I recently started creating my own assets for elcord. While I'm doing that I noticed something when I open a HTML file (without having any form of configuration done for HTML files) the RPC is not showing that I'm editing that HTML file even after the delay (15 secs) and the RPC shows the buffer that I was last edited.
On the other hand, my friend, who has the web mode when edited a HTML file the RPC is showing that he is editing the HTML file.

Unfortunately I can't replicate this - Maybe there's another mode enabled in Emacs that is somehow conflicting?

So it's a emacs problem?
P.S: I tried in a fresh emacs just installed elcord still not working.

Okay, found out what's causing this - The reason is that the default HTML mode in Emacs has a mode name that is ((sgml-xml-mode "XHTML+" "HTML+") (:eval (mhtml--submode-lighter)))
Which isn't a string and causes a bad message to get sent.
I'll add an entry for it in elcord-mode-text-alist, but also coerce the name to a string so that in the future this is captured - I didn't know mode-name could be anything other than a string

Thanks!

Thanks for Fixing


maxPostSize of request exceeds server default configuration

Expected behavior
setting max. Filesize to 50 (MB)
Actual behavior
error during upload of file for files >  ~2MB
seems, that uploading files using your approach (sending the file in pieces of 30K in 1 request) can exceed the maximum allowable POST request size configured on the webserver
Steps to reproduce the issue
APEX version (4.2.6 / 5.0.3)
5.0.3
Used web server / version and platform (ORDS 3.0.3 / Tomcat 7 / Apache 2.4 / Linux x64)
Tomcat 8.0, maxPostSize:
The maximum size in bytes of the POST which will be handled by the container FORM URL parameter parsing. The limit can be disabled by setting this attribute to a value less than zero. If not specified, this attribute is set to 2097152 (2 megabytes). Note that the FailedRequestFilter can be used to reject requests that exceed this limit.
I have no access to the servers configuration in the customers corporate environment.
My suggestion: split the upload request in multiple requests rather then using one single request or using the good-old-fashined CLOB upload method instead (http://www.talkapex.com/2012/08/how-to-sendupload-clob-from-browser-to.html)
Used web browser / version and platform (Chrome 48 Mac / Firefox 44 Windows)

Hey @crokitta
over the holidays I spent some of my time on this plugin and now version 2.0 is ready to go. This version is built from ground up new, this means it is not compatible with version 1.xx (changed a whole bunch of attributes & logic).  Thus version 2 has a new Internal name you can install it beside version 1 and can migrate to the new version...see the readme note.
The new version now has the possibility to choose the Upload Mechanism. Here you can select "Chunked". This Method splits a file to 1MB chunks and uploads every chunk separately to the server via AJAX (To a Temp Collection). On server side the Temp Collection is read and builds the final file...This Method is incompatible with old Web servers like OHS or WebTier.
Hope this helps and of course happy new year!;)


documentation: Coding style references rust constructs

We removed rust altogether, so this document needs a big update.

Should it reference clang-format and C++ coding standards for things like the runtime or manual C++ code for jakttest and other utiltiies?

Should it describe idealized jakt coding styles and patterns?

Should it reference clang-format and C++ coding standards for things like the runtime or manual C++ code for jakttest and other utiltiies?

Maybe? This seems less important.

Should it describe idealized jakt coding styles and patterns?

Totally! That would be a great document to start building.


Fix stale notification

By consolidating all calls to weatherCommand execute in the AppDelegate it becomes much easier to reason about when the command is executing. This made it easier to figure out at which times in the launch cycle we to execute it and how to prevent the command being executed multiple times.
The weather is currently updated when:

in application:didFinishLaunchingWithOptions: if the options dictionary does not contain UIApplicationLaunchOptionsRemoteNotificationKey
in applicationWillEnterForeground
in application:didReceiveRemoteNotification:fetchCompletionHandler:

The first two replace the weather updates in WeatherViewController in response to viewDidLoad and UIApplicationWillEnterForegroundNotification. By moving this into the app delegate we can more easily detect when the application is launched by a remote notification and prevent any weather updates normally done to update the UI.
This PR resolves #184.

I'm going to merge this so I can release it in a beta.


feat: ServiceMonitor add label

Description
ServiceMonitor generates labels based on crd configurationl
Issues Resolved
solve issue #572

Thanks for your contribution @loon-hejw, can you please re-base from main, a recent PR is merged https://github.com/opensearch-project/opensearch-k8s-operator/pull/767 that should fix the CI checks.
Thanks
@bbarani @swoehrl-mw @salyh

@loon-hejw Please cleanly rebase your commit on main. You have a few diffs/changes in your PR that are already in main and bloat up the diff.

@swoehrl-mw  cr

@swoehrl-mw re


Git similar should suggest all possible commands

Testing #161846

Execute git stattus
See that there is a terminal quick fix for git status since it's the only similar command
Execute git pul
See there is no quick fix as both pull and push are recommended as possible commands.

The quick fix should contain both so I can choose which to execute.

/duplicate https://github.com/microsoft/vscode/issues/161595