Errors during install of vue-cli on Mac OSX

Version
3.4.0
Environment info
System:
    OS: macOS 10.14.2
    CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
  Binaries:
    Node: 10.15.1 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.7.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 71.0.3578.98
    Firefox: Not Found
    Safari: 12.0.2
  npmGlobalPackages:
    @vue/cli: 3.4.0

Steps to reproduce
I cleared my entire Node and NPM and re-installed but I still get the following errors when I run:
sudo npm install -g @vue/cli
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
/usr/local/bin/vue -><EMAIL_ADDRESS>
<EMAIL_ADDRESS>install /usr/local/lib/node_modules/@vue/cli/node_modules/fsevents
node install

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Pre-built binaries not installable for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error EACCES: permission denied, mkdir '/usr/local/lib/node_modules/@vue/cli/node_modules/fsevents/lib'
gyp WARN EACCES user "root" does not have permission to access the dev dir "/Users/#myusrname#/.node-gyp/10.15.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir<EMAIL_ADDRESS>gyp WARN install got an error, rolling back install
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir<EMAIL_ADDRESS>gyp ERR! System Darwin 18.2.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build"<EMAIL_ADDRESS>"--module_name=fse" "--module_path=/usr/local/lib/node_modules/@vue/cli/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64" "--napi_version=3" "--node_abi_napi=napi"
gyp ERR! cwd /usr/local/lib/node_modules/@vue/cli/node_modules/fsevents
gyp ERR! node -v v10.15.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build<EMAIL_ADDRESS>--module_name=fse --module_path=/usr/local/lib/node_modules/@vue/cli/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64 --napi_version=3 --node_abi_napi=napi' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/usr/local/lib/node_modules/@vue/cli/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:189:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:970:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
node-pre-gyp ERR! System Darwin 18.2.0
node-pre-gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/@vue/cli/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /usr/local/lib/node_modules/@vue/cli/node_modules/fsevents
node-pre-gyp ERR! node -v v10.15.1
node-pre-gyp ERR! node-pre-gyp -v v0.10.3
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build<EMAIL_ADDRESS>--module_name=fse --module_path=/usr/local/lib/node_modules/@vue/cli/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64 --napi_version=3 --node_abi_napi=napi' (1)

<EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/@vue/cli/node_modules/protobufjs
node scripts/postinstall

<EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/@vue/cli/node_modules/nodemon
node bin/postinstall || exit 0

Love nodemon? You can now support the project via the open collective:

https://opencollective.com/nodemon/donate

npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@vue/cli/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: node install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
<EMAIL_ADDRESS>added 668 packages from 500 contributors in 42.29s
What is expected?
vue-cli installed
What is actually happening?
Vue seems installed but with the errors above

Same here on Windows 10

Same here on Windows 10 too

Similar error on Windows 10:
> npm install -g @vue/cli
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'apollo-link-context'
npm ERR! notarget

@sodatea seeing a bunch of warnings and errors doesn't give the impression of a successful install though?  How come my install on macOS skipped the optional fsevents?

@GeertClaes Sorry but I cannot reproduce this issue on my Mac. Maybe it's a npm or node-pre-gyp bug.

Cleared the entire node and npm again, added myself to wheel and staff groups and ran this: sudo chown -R $(whoami) $(npm config get prefix)/{lib/node_modules,bin,share before installing again without errors

Solved with sudo npm install -g @vue/cli --unsafe-perm

Solved with sudo npm install -g @vue/cli --unsafe-perm

Thanks. It dose work.

Solved with sudo npm install -g @vue/cli --unsafe-perm

Thanks, It worked for me.

thanks works for me

Solved with sudo npm install -g @vue/cli --unsafe-perm

thanks :)

RickdeMacBook-Pro:~ Rick$ sudo npm install -g @vue/cli --unsafe-perm
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
/usr/local/Cellar/node/10.12.0/bin/vue -><EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

<EMAIL_ADDRESS>updated 1 package in 380.888s
RickdeMacBook-Pro:~ Rick$ vue -v
-bash: vue: command not found

sudo npm install -g @vue/cli --unsafe-perm did't solve my problem

Finally, I solved with

sudo npm install -g @vue/cli --unsafe-perm

Now its work on my iMac

Solved with sudo npm install -g @vue/cli --unsafe-perm

Wow! Huge thanks to you, it solved my problem :)

sudo npm install -g @vue/cli --unsafe-perm

Solved for me too. thank you!

For me it worked with npm install -g @vue/cli@latest .
Now i have ERRORS when i try to create with : sudo vue create client .
Can anyone help me with this one?

@TodeDragos https://cli.vuejs.org/guide/troubleshooting.html#running-installation-with-sudo-or-as-root
In short: don't use sudo.

the problem was with the FOLDER of my project. It was created with some "root" permisions and because of that the vue create client didn't worked.

Finally, I solved with

sudo npm install -g @vue/cli --unsafe-perm

Worked like a charm!

Solved with sudo npm install -g @vue/cli --unsafe-perm

Solved for me too. thank you!

Solved with sudo npm install -g @vue/cli --unsafe-perm

Thank you!

sudo npm install -g @vue/cli --unsafe-perm.
Perfecto. Gracias!!

I keep getting these errors I tried  'sudo npm install -g @vue/cli --unsafe-perm' and it still gives me the following errors.
No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:223:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 19.3.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/omarzoghayyer/npm-global/lib/node_modules/@vue/cli/node_modules/fsevents
gyp ERR! node -v v12.14.1
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@vue/cli/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: node-gyp rebuild
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

<EMAIL_ADDRESS>updated 1 package in 29.322s
omarzoghayyer@admins-MacBook-Pro ~ %

@omarzoghayyer https://github.com/nodejs/node-gyp/issues/1927#issuecomment-544499926

Solved with sudo npm install -g @vue/cli --unsafe-perm

thanks for your help :)

Im getting almost  the same problem here on Mac

sudo npm install -g @vue/cli --unsafe-perm

Somewhen somebody will post a receipt sudo npm install --nuke-the-bomb, everybody will install and clap...
Doesn't work for me


Add Pagination to the API

Hi everyone, I think it could be a nice idea to add in the API section an endpoint to retrieve the shows list in paginated format, something like limit and offset in SQL. I propose this change because it would be very useful in case you want to implement a list with the contents that load on a scroll and an endpoint that returns the paginated results would be very useful.
Based on the current API structure, the endpoint could look like this:
https://syntax.fm/api/shows/paginated-[offset]-[limit]

or
https://syntax.fm/api/shows/paginated?offset=[offset]&limit=[limit]

I am developing a Flutter app for a side-project that shows the list of episodes and this feature could be very useful.

Lets mirror the params from the shows page, that way we can re-use the queries:
page=2&perPage=20&order=asc&type=hasty
Let's limit perPage to 100
Another item is that modifying this API might break some apps, but it doesnt seem to have a TON of usage: https://github.com/search?q=syntax.fm%2Fapi&type=code
This API endpoint is getting too large and using a ton of bandwidth (thx vercel)
so, rather than versioning the API, I say we to 20 episodes per page and then try notify anyone who might be using it.


Back button

On configuring a dataset or altering a facet on the Analyse page, going back to the previous page can be done with either the back button of the browser or by clicking the corresponding menu button in the menu on the left. I would like it more if there could be an arrow pointing left to the left of the page title (just as there would be in Android for example, consistent with material design: https://i.stack.imgur.com/qddYm.png).

duplicate of #47


{Script} Add retry in get_whl_from_url

To mitigate the increasing failures in Verify Extensions Index CI task recently.

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Script


SAK-41821 Assignments : student progress bar and confirmation screen

I'd like to be reviewed not only the code and functionalities, but also the default messages shown and the related properties. Thanks!

It would be ideal to add aria labels where appropriate.

@ern I've just renamed the properties.


How to use the parameter : 'DirectToLds'

After reading the source code in 'Common.py' & 'KernelWritterAssembly.py'. I wonder how 'DirectToLds' make sense. It is initialized as False and do not change with 'DirectToLds= [ True ]' even if I am sure that 'GlobalVectorWidth = 1'
Another question about this is in 'KernelWritterAssembly.py'. When 'PrefetchGlobalRead' is set, what if 'DirectToLds = True'?

Here is the Code.

I had the same problem, the condition of 'DirectToLds' is too harsh

As you mentioned, DirectToLDS is only limited to a few cases. We have relaxed some of the restrictions, but DirectToLDS still requires specific conditions to work.


camera parameters change can not change the results

Great jobs.
I have changed camera paramters, for example, changing the extrinsic parameters, but the results do not changed at all. I am wondering why.

This is a known issue. You may want to check out https://gaoruiyuan.com/magicdrive3d/ and the corresponding paper.


onConfigurationChanged orientation value does not change

I added android:configChanges="fontScale|keyboardHidden|orientation|screenSize" to my Activity definition in the manifest to handle the rotation my self .
But when I extended LocalizationActivity the value of newConfig.orientation Doesn't change when I flip the device .
Following is the POC I have made to demonstrate this issue
class MyApplication : LocalizationApplication() {
    override fun getDefaultLanguage() = Locale.ENGLISH
}

//when I change it to class MainActivity : AppCompatActivity the newConfig.orientation change correctly
class MainActivity : LocalizationActivity() {

override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
    }

override fun onConfigurationChanged(newConfig: Configuration) {
        super.onConfigurationChanged(newConfig)
        Log.d("nav", "isLandScape=" + newConfig.orientation) // stay same  value on device rotation
    }
}

is there a workaround I can do to temporarily fix this ?

It doesn't change even you using AppCompatActivity 😂

It doesn't change even you using AppCompatActivity 😂

Handle the rotation by android:configChanges isn't recommended for most use cases.
Alternatively, you can detect the screen orientation changes from context.getResources().getConfiguration().orientation. And you can also use my ScreenOrientationHelper library for this situation.

Handle the rotation by android:configChanges isn't recommended for most use cases.
Alternatively, you can detect the screen orientation changes from context.getResources().getConfiguration().orientation. And you can also use my ScreenOrientationHelper library for this situation.

I will close this issue because there's no response for a month. Feel free to re-open this issue if anyone has problem about this.


Implement "likely" branches

Blocked by #91
The idea of "likely" branch is to cause a "short" branch mispredict to fetch new instruction from branch target rather than from PC + 4.
TBD

Hello. If I get it right, we should always fetch and execute the first instruction (from a branch target), even if the branch is not taken. So that programmer who wants to write efficient and correct code should place there an instruction which won't do any harm in case of not taken branch. Am I right?

I mean we don't flush instruction in case of misprediction.

No, how would that be possible?
The idea is following: if we fetch a branch and there is no information from branch prediction, the next fetched instruction is always PC + 4:
Branch F D E B W
PC+4     F D E *
PC+8       F D *
PC+12        F *
Target         F D E M W

For likely branches, we should fetch Target as soon as possible. We cannot do it immediately since target is not decoded on F stage, so we have to use target mispredict flush to have the following pipe:
Branch  F D E B W
PC+4      F *
Target      F D E M W


Improve parsing of url's in all cases, but specifically for ssh cases.

In my case, in addition to the default git_services, I use a hosted
Gitlab that uses some ssh tunneling to reach the destination using a
port other than standard. Using the parsing as is results in parsing the
owner as <port>/actual/owner. For example ssh://gitlab.priv:2222/priv/group/repo.git
yields owner 2222/priv/group which constructs a bad url with
configuration ["gitlab.priv"] = "https://gitlab.priv/${owner}/${repository}/-/merge_requests/new?merge_request[source_branch]=${branch_name}&merge_request[target_branch]=main".
This probably generally works, because most users of ssh remotes will
either use the git scheme or the default port 22, without specifying.
This patch introduces a more robust git url parsing library function, with support for more url schemes. It also maintains compatibility with the existing implementation where owner is set to the entire path part which is not the repository name; which is correct in the basic gitlab / github cases, but not in many other git cases.
It has been tested with the following url's:

git@github.com:owner/repo.git
https://github.com/owner/repo.git
git@gitlab.com:owner/repo.git
https://gitlab.com/owner/repo.git
<EMAIL_ADDRESS>ssh://git@gitlab.priv:2222/project/path/repo.git
ssh://git:pass@gitlab.priv:2222/project/path/repo.git
https://gitlab.priv/project/path/repo.git
https://gitlab.priv:4443/project/path/repo.git

Test Results
{
  host = "github.com",
  owner = "owner",
  proto = "git",
  repo = "repo",
  repository = "repo",
  url = "git@github.com:owner/repo.git",
  user = "git"
}
{
  host = "github.com",
  owner = "owner",
  path = "owner",
  proto = "https",
  repo = "repo",
  repository = "repo",
  url = "https://github.com/owner/repo.git"
}
{
  host = "gitlab.com",
  owner = "owner",
  proto = "git",
  repo = "repo",
  repository = "repo",
  url = "git@gitlab.com:owner/repo.git",
  user = "git"
}
{
  host = "gitlab.com",
  owner = "owner",
  path = "owner",
  proto = "https",
  repo = "repo",
  repository = "repo",
  url = "https://gitlab.com/owner/repo.git"
}
{
  host = "gitlab.priv",
  owner = "project/path",
  path = "project/path",
  proto = "ssh",
  repo = "repo",
  repository = "repo",
  url =<EMAIL_ADDRESS>  user = "git"
}
{
  host = "gitlab.priv",
  owner = "project/path",
  path = "project/path",
  port = "2222",
  proto = "ssh",
  repo = "repo",
  repository = "repo",
  url = "ssh://git@gitlab.priv:2222/project/path/repo.git",
  user = "git"
}
{
  host = "gitlab.priv",
  owner = "project/path",
  path = "project/path",
  port = "2222",
  proto = "ssh",
  repo = "repo",
  repository = "repo",
  url = "ssh://git:pass@gitlab.priv:2222/project/path/repo.git",
  user = "git"
}
{
  host = "gitlab.priv",
  owner = "project/path",
  path = "project/path",
  proto = "https",
  repo = "repo",
  repository = "repo",
  url = "https://gitlab.priv/project/path/repo.git"
}
{
  host = "gitlab.priv",
  owner = "project/path",
  path = "project/path",
  port = "4443",
  proto = "https",
  repo = "repo",
  repository = "repo",
  url = "https://gitlab.priv:4443/project/path/repo.git"
}

And now it works as expected with the following configuration:
      git_services = {
        ["github.com"] = "https://github.com/${owner}/${repository}/compare/${branch_name}?expand=1",
        ["gitlab.com"] = "https://gitlab.com/${owner}/${repository}/merge_requests/new?merge_request[source_branch]=${branch_name}",
        ["gitlab.priv"] = "https://gitlab.priv/${path}/${repository}/-/merge_requests/new?merge_request[source_branch]=${branch_name}&merge_request[target_branch]=main",
      },

Lastly, the test are passing to the same extent they were before this patch.

I dig it. Nice work.


Mission Blips

Add a clear and concise description of the feature you have in mind.
Are the mission blips bugged, Mines aren't working for some missions, when I take SCVDN out it works fine.

We're sorry to say this for your first issue, but this issue only has a too vague info for us to reproduce. If you have the idea how to reproduce the issue, you'll have to write in detail (including the SHVDN version you are using).


feat(ui): display latest version in package overview

Closes #330
Fixes #330
📑 Description
This shows the LatestVersion and the Current version (if installed) on the package overview page
Images :

When a Package is installed

When a Package is not installed

✅ Checks

[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required

ℹ Additional Information

Hey @pmig why the checks are not applied for this PR. Also it shows me some message on Conflicting Files. Can you please guide me on this.

Hi @hanshal101 the reason for the conflicting files as there is conflict with the the latest state in the main branch. In order to resolve it, you can checkout the latest version of the main branch and rebase your current branch on top if it. In this step you will need to resolve the conflict. After that you can force-push to your branch and the checks will get executed.


boot2docker OSX uninstall script tweak

Hi,
The boot2docker uninstall script for osx (uninstall.sh) tests for the existance of the command 'boot2docker' before it will uninstall boot2docker related things. This means that if this particular binary does not exist, it will not delete anything at all. If you had gotten rid of only the binary of the binary was not in your path at this particular moment, it also means the rest of the boot2docker files (which might exist!) are not removed. I would suggest removing the boot2docker test.

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).


Add a Pubmed export file similar to RIS format

Added a Pubmed format file that is similar to the RIS file format with 50 open access paper references for potential future support.

Thanks.
Do you have any reason to use 50 publications here instead of 10?

Yes, given that it is a format that we do not support yet, some extra examples might help with a possible implementation.


Use generic math at test project

Related to #101

This is a nice continuation but this is not the goal of the sample, too much to grasp IMO for an introduction, it's definitely something that is better in a more advanced solution ... like ncalc ;)

I was more exploring the public API specifically for NCalc. I was exploring in my local clone for NCalc but ended with this. I agree it's too advanced.


PhpdocTrimFixer - unicode support.

closes https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/3271

Thanks for picking this one :+1:

@SpacePossum thanx. This seems to solve the problem.

Thank you @SpacePossum.


Release Google.Cloud.AssuredWorkloads.V1Beta1 version 1.0.0-beta05

Changes in this release:

Commit 28a4164: feat: Add EU Regions And Support compliance regime

Created release for Google.Cloud.AssuredWorkloads.V1Beta1-1.0.0-beta05


fix: Handle KeyError for 'stream_endpoint' in get_tags_raw method

fix: Handle KeyError for 'stream_endpoint' in get_tags_raw method.
Must check if tag_name exists in structure_all_funcs first to prevent errors.

fix: Handle KeyError for 'stream_endpoint' in get_tags_raw method. Must check if tag_name exists in structure_all_funcs first to prevent errors.

Please ask if you are sure you have solved the key error problem? When I modified according to your pull request, I still encountered a key error in get_tags_raw.
The first change:

The second change:

Ok, I made like three changes I think this one is one part of it. Will close this out I'm not going to maintain this repo.


Authentication consideration

Hello,
I want to use JWT between microservices (so between Requester <=> Responder, and Publisher <=> Subscriber). It is possible? Or something else to authenticate call?
Awesome project by the way: easy to understand and to use :)

Thanks a lot! JWT is totally possible, but would have to rely on custom implementation on your side — currently you can't prevent daemons from connecting to one another as long as they discover each other.

ok thanks. Any advice to do this custom implementation?

@FPierre I think you'll find it's really simple after you learn the API for the [jsonwebtoken](https://www.npmjs.com/package/jsonwebtoken package).  This is what we use for all of the Feathers authentication suite.

Security seems to be something missing from Cote? The use of broadcast and multicast even on closed networks without TLS and authentication/authorisation is really dangerous in production environments. It would be a really good idea to give this some focus.

@TotallyInformation You said something that made me curious. Why is it necessary to have TLS present in a closed network? Do you have good use case for me to understand your point? I do agree with the authentication logic part of your comment though (Y)

I personally believe you can't solve security by throwing concepts at it. It is a conscious decision where and how you want to implement it, taking into consideration a lot of variables. I would love to hear the scenario where "the use of broadcast and multicast on closed networks without TLS & co is really dangerous in production". Specifically, what kind of production environment is that, and how would TLS prevent a leak, as cote should be used for internal communication and securing external endpoints is out of our scope.
Having said that, in fact, cote could be extended to include TLS support — if somebody would be up for the challenge, I can offer help. Additionally, cote can already be configured (although in an obscure and hacky way at the moment) to include symmetric encryption of messages.
Then there's the issue of authentication and authorization. Both of these are out of cote's scope, as there are literally hundreds of ways to do these things. But, obviously, in every app that I do with cote, I implement a proprietary layer on top of cote for authentication and authorization. I believe the best way to support these features is via plugins or middleware, and it's currently in my immediate focus.

In enterprise networks it is very common to have networks that are extensive with loads of different users and services attached. While good network design, network isolation architectures and intermediary firewalls can help mitigate security issues, large organisations cannot be sure that attackers haven't managed to get a foothold onto the network.
Therefore it is imperative that any personal/sensitive data - including authentication and authorisation - is encrypted on the wire. This is good enterprise security practice and if more widespread would certainly reduce many of the data leaks we see today by helping prevent attackers from penetrating further into restricted networks.
This is not a case of "throwing concepts" at all! This is a case of security needing defence in depth. As a security expert, this is a constant battle I have with system designers and developers who's focus may be on ease of development and deployment rather on the wider risk management. There is no single "fix" for security but using security standards throughout certainly helps.
If you are not prepared to support security within this product, it would at least be helpful to tell people so and advise them of security best practice or at least steer them to places where they can learn.
But the real point here is what you are claiming for Cote. You are claiming that this is a "batteries included" solution and currently this is a most dangerous claim since security is virtually absent. You have even set up an e-commerce "case study" that also doesn't seem to include any real security - given the ongoing litany of security disasters we are seeing week-in and week-out from all manner of organisations, this would seem to be very much less than helpful to the community.
This is a real shame as otherwise, this seems like an excellent tool.


Inconsistent arrays test expectations

I'm implementing support for toml-test and have found what seems like an inconsistency in the expectations for a few of the tests - specifically for the table arrays.
With non-table arrays, it is expected that the JSON output specifies array for type, ala the example in /tests/valid/arrays.json where this TOML:
strings = ["a", "b", "c"]

...would output this JSON:
{
  "strings": {
    "type": "array",
    "value": [
      {"type": "string", "value": "a"},
      {"type": "string", "value": "b"},
      {"type": "string", "value": "c"}
    ]
  }
}

However, with the table arrays, the expected JSON output is showing not to expect a specified type at all, ala the example in /tests/valid/table-array-one.json where this TOML:
[[people]]
first_name = "Bruce"
last_name = "Springsteen"

...is expecting this JSON:
{
  "people": [
    {
      "first_name": {"type": "string", "value": "Bruce"},
      "last_name": {"type": "string", "value": "Springsteen"}
    }
  ]
}

Since the resulting data structure is is that people is array like any other (an array of objects), I would expect people be typed like all other arrays, like this:
{
  "people": {
    "type": "array",
    "value": [
      {
        "first_name": {"type": "string", "value": "Bruce"},
        "last_name": {"type": "string", "value": "Springsteen"}
      }
    ]
  }
}

What's the reason for the different expectations?

I would rather see that inline arrays are always seen as array, while table arrays are seen as table arrays. There's a clear distinction between the two in TOML. One is static, the other is not. Table arrays can be extended by defining more of them, while inline arrays cannot be modified.
However, I noticed when testing my parser that this code:
oo = [ { bar="\"{{baz}}\""} ]
is expected to be outputted as:
{
  "foo": [
    {
        "bar": {"type": "string", "value": "\"{{baz}}\"" }
    }
  ]
}

So a table array, even though it was defined as a static array.
Yes, I can detect that it contains inline tables, so I will have to go that path right now to make your test suite work, but it feels wrong because the json no longer represents the semantics of the types.
In my parser, a table is a value as well, and there's no real distinction between "array of integers" and "array of tables".

In the Array of Tables section of TOML v1.0 it explicitly says that "you may also use inline tables where appropriate" instead of an Array of Tables.
However toml-test seems to fail encoders if they use inline tables where appropriate instead of an Array of Tables.  This doesn't seem to be a requirement of the TOML spec itself.
An example would be an encoder providing the output
people = [{first_name = 'Bruce', last_name = 'Springsteen'}]

in the "valid/table/array-one" encoding test instead of
[[people]]
first_name = "Bruce"
last_name = "Springsteen"

Currently this fails in toml-test due to:
     Type for key 'people' differs:
       Expected:     [map[first_name:Bruce last_name:Springsteen]] ([]map[string]interface {})
       Your encoder: [map[first_name:Bruce last_name:Springsteen]] ([]interface {})

but aren't these simply two different ways of expressing the same thing?


Help me: I need your equal distribution algorithm but don't understand your code

I exactly need your algorithm that places rectangles in a grid fashion for my application.
I suspect it is in _function distributeEqually(nodes)
However I don't understand your code yet and have no experience with d3.
Can you give me any logic or semantic on how the algorithm works that places rectangles like that?

Hi!
The two main parts should be this:
https://github.com/interactivethings/d3-grid/blob/9c31fd86769647fcce0eda49ca2b17de46cc74e0/d3-grid.js#L33-L34
… which calculates the number of columns and rows, so that they're roughly equal
and
https://github.com/interactivethings/d3-grid/blob/9c31fd86769647fcce0eda49ca2b17de46cc74e0/d3-grid.js#L56-L58
… where for each node (i.e. point on the grid) its col and row are calculated.
If you need more details, please let me know!

For

… where for each node (i.e. point on the grid) its col and row are calculated.

Is this the same for the rectangles? I only need the rectangles, and not the points

What and how you draw at each point is up to you. This calculation only gives you the coordinates within the grid. For example:
const nodes = [{}, {}, {}, {}];
const n = nodes.length; // 4 in this case

// Figure out how many columns and rows we need
const cols = Math.ceil(Math.sqrt(nodes.length)); // => 2
const rows = Math.ceil(n / cols); // => 2

// Assign col/row to each node
nodes.forEach((node, i) => {
  node.col = i % cols;
  node.row = Math.floor(i / cols);
})

// Nodes now should be
// [{col: 0, row: 0}, {col: 1, row: 0}, {col: 0, row: 1}, {col: 1, row: 1}]

Perfect I just finished my task thanks to you!
Many thanks and kind regards!


DOC: show install from github (and MAINT: add requirement)

This install is a little easier (and it resolves one issue I had with the install).

Pull Request Test Coverage Report for Build 313

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.711%

Totals

Change from base Build 300:
0.0%

Covered Lines:
1600

Relevant Lines:
1981

💛  - Coveralls

Pull Request Test Coverage Report for Build 314

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.711%

Totals

Change from base Build 300:
0.0%

Covered Lines:
1600

Relevant Lines:
1981

💛  - Coveralls


Uncaught TypeError: Cannot read property 'type' of undefined

Version
"react-router-dom": "^4.1.2",
"react-router-redux": "^5.0.0-alpha.6",
Test Case
https://github.com/Deviad/redux-router-playground/blob/under_development_v5/src/epics/epic_posts.js
Steps to reproduce

npm start;
open http://localhost:3000/posts/new
fill the form
press the submit button

Expected Behavior
It should show the page it gets redirected to by means of history.push("/")
Actual Behavior
It does redirect but shows in console.log the following error message:
Uncaught TypeError: Cannot read property 'type' of undefined
I logged the contents of my action$ observable for you to see that it's ok.

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux. Thanks!


Reformat code

Closes #63.

Added prettier
Configured eslint to check correct formatting

Coverage increased (+0.2%) to 79.415% when pulling ad40778923427a8633509328ba5856e169a81455 on 63-reformat-code into adb98b9d9dbf847d34d4603b9219d7c19c74889b on master.


Provide LICENSE.txt

Hello,
tl:dr; Can you please provide an Apache License v2 compatible LICENSE.txt for this repository? I'd like to use (parts) of this code in the Apache Commons BeanUtils2 library.
Long Version: I'm working on the Apache Commons BeanUtils2 project - a rewrite of the Apache Commons BeanUtils library. BeanUtils2 provides a fluent API for reflection operations:
import static org.apache.commons.beanutils2.BeanUtils.on
...
on(myBean).set("name").with("Peter");

Currently I'm working on an API that let's users configure type conversion in a fluent way:
import static org.apache.commons.beanutils2.ConverterBuilder.from;
...
BeanUtils.newInstance()
   .withConverters(
      from(String.class).to(Integer.class).using(Integer::parseInt),
      from(String.class).to(Date.class).using(myCustomDateFormatter)
   ).build();

Further more it is possible to assign properties to a bean using a map:
Map<String, Object> properties = new HashMap<>();
properties.put("name", "peter");
properties.put("age", 48);

on(myBean).populate(properties);

When we implement a MapToBeanConverter, and combine it with the code in this repository, can can put this all together as:
on(myBean).set("address").with(
   map(
      "street" -> "Broadway 5",
      "zip" -> 10002,
      "city" -> "New York"
   )
);

And that would be pretty awesome :-) To reuse any of your code, it would have to be under Apache License v2. We would of corse give you credit for this contribution. Further more, if you're interested to join development on BeanUtils2, just ping me.
Thank you very much!
Benedikt

Hi, recently I have taken the liberty to simplify and refactor Benji's code. I have published it here https://github.com/lukas-krecan/lambda-param-name-extractor under Apache 2 license. It's just one simple class exposed as a module, feel free to use it.

I've added the licence for you.
Do be aware that this approach to lambda name reflection does rely on the current implementation of lambdas and could well stop working in the future. Also the left hand side can't be quoted.

Thank you!


ux/slider behaviour

Problem:
For years now, we've had scrubbing/sliding behaviours that could trigger other hover effects in the UI. It's a detail, but it really felt wrong / brittle.
Fix:
This trivially fixes the problem by temporarily rendering a hover-effect-blocking div for the scrubbable label, and the slider. It doesn't include the sliding behaviours of the colour picker.
NB we discussed in the past to do this via on-click-outside; can confirm this won't work (you can put a wrapper div, but that then will swallow the first click even while not  using the slider. I guess we could do this via editor state etc, but not only does that feel like a sledge hammer, but that would make it v difficult to put the insulating div in the right place, z-index-wise.

Delete SliderControl2 and the commented out prop and then this looks good to me

awkward. Done.


issue#38

Add signup data to api/user/{id} request
P.S. It seems conflict in authRoutes.php file.

@Leo24 resolved and merged


Add Renew field to FileInfo

This will allow API consumers to display whether a file is being renewed.

Closed in c3042c7b1f09d1f72a8b49340ca4907d632e75dd?


Debug: add logging

Codecov Report

Merging #8 (521c1d8) into main (0422b49) will increase coverage by 0.92%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
+ Coverage   67.64%   68.57%   +0.92%
==========================================
  Files           2        2
  Lines          68       70       +2
==========================================
+ Hits           46       48       +2
  Misses         21       21
  Partials        1        1

Impacted Files
Coverage Δ

main.go
75.00% <100.00%> (+0.80%)
:arrow_up:

Continue to review full report at Codecov.

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


docs: multiline variable clarification

this was slightly confusing to me

I think I agree with @laniakea64, interpolation isn't possible in any kind of string, so calling out triple-quoted strings in particular is confusing. I opened #2515 to add a more general note about all strings.

Awesome! That definitely adds some clarity.


Fix typo in travis setup

Kind of a critical typo in the version selection for alex and happy.

it seems this was already fixed


Replace course study mode and site flow (replace course 3 of 3)

Context
The first PR covers adding a provider #2316
The second PR covers adding a course #2317
This PR covers the final sections of the flow. Adding a study mode and a location.
Changes proposed in this pull request
Adds the study mode page

Adds the location page

Guidance to review
I've gone through and manually tested this quite a bit. It would be great if someone could test it locally too in case I've missed anything.
Link to Trello card
https://trello.com/c/kUjDNNbH/1646-dev-update-course-choices-if-course-becomes-full-while-waiting-for-references
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

@davidgisbey can you rebase this? Some commits are already in master


Lots of flash drives!

Description
I'm creating a windows setup drive, and when I pluged it to my computer I noticed I have more drives than I suppose... :-)

Steps To Reproduce
No response
Expected behavior
I woukld expect that only one H: drive appear.
Files Version
v<IP_ADDRESS>
Windows Version
windows 10 21H1
Relevant Assets
No response

Drives on sidebar are duplicated too

Happened right now when connecting a regular flash drive with only one partition (FAT32, regular for flash drives)
It showed up two identical flash drives at first, then the second disappeared when I've updated the program. Don't know why.
Files version: <IP_ADDRESS>
Windows OS: 10, Version: 10.0.19043.1348

Resolved with #8325


[Bug]  分区过多时，delete from table超时

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
1.1.2-rc02
What's Wrong?
当分区数过多时，无法使用delete 删除某个指定分区数据，即使该分区没有数据，也会返回超时
Execution failed: Error Failed to execute sql: java.sql.SQLException: (conn=2879) errCode = 2, detailMessage = failed to execute delete. transaction id 6879467, timeout(ms) 300000, unfinished replicas [BackendId=TabletId]: 11008=4423752, 11008=4423776, 11008=4423788, 11008=4423680, 11008=4423684

What You Expected?
Fix
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

已解决
1 执行时设置 SET delete_without_partition=TRUE
2 执行语句：DELETE FROM test_table PARTITION p20220820 WHERE day_id=20220820
3 执行删除时 添加指定分区名称(PARTITION p20220820)即可


Docker 17.06.2ce-1.94.amzn1 available on Amazon Linux 2017.09

Cookbook version
v2.17.0
Chef-client version
12.21.26
Platform Details
Amazon Linux 2017.09
Scenario:
docker-17.06.2ce-1.94.amzn1 is available on Amazon Linux from the amzn-updates repository but the cookbook is still defaulting to docker-17.06.2ce-1.93.amzn1.
Any chance we can get a default docker version bump in helpers_installation_package.rb?

Merged


Experimental PR for CI

Signed-off-by: UMEZAWA Takeshi<EMAIL_ADDRESS>

Fixed in #105


PartiQL queries in Redshift

This PR adds support for parsing PartiQL queries in Redshift

Thanks @yoavcloud and @iffyio


assets are unaveilable

back-link: en/ch05/index.html#fluid-elements

Ohh, yes. We moved thing to an "en" folder for english. Need to update the links


CloudTrail does not send all CloudTrail logs to an s3 bucket in logging

Some accounts send to a bucket in the logging account some send to the management account - it is applied via a security baseline.  This is 100% against AWS best practice - why have two different logging locations.  Is there a parameter in the create_config.py file that changes this - if so, nothing stands out? I've run this framework in multiple organizations and all have the same issue - so this appears to be default.  Please provide guidance.

I will be reporting this a security vulnerability.

The central and logging accounts, which are core accounts, store their logs directly in the logging account. The environment accounts (management services, transit, and any defined tenant accounts) send their logs to the management services account.
This design decision stems from the DoD requirement that there be an immutable location for logs, which is represented by an s3 bucket hosting the consolidated logs in the logging account. One of the additional security requirements prescribed by the DoD is to use a log aggregation tool (or SIEM); these tools are hosted in the management services account and are not configured to directly access the immutable consolidated logs. Although this is not configured by default (because this would generate additional costs for the duplicate logs and may not be desirable in some use cases), we recommend that users of Compliant Framework configure s3 replication to copy environment account logs hosted in the management services account to the consolidated logs bucket in the logging account.
Thanks for the question!

The template has replication configured to send the logs in the management services account to the logging account. The role used in the management services account is missing permission to change ownership in the destination bucket.
To fix:
The  role, ConsolidatedLogsReplicationRole,  used by ConsolidatedLogs rule for Management account bucket buckets that replicates logs from the Management to Logging was missing the following policy
{ "Effect":"Allow", "Action":[ "s3:ObjectOwnerOverrideToBucketOwner" ], "Resource":"arn:aws:s3:::destination-bucket/*" }


Fixed missing 'CPC' arg in 'zhmc cpc upgrade' command

Tested - no review needed.

coverage: 33.986%. first build when pulling aef457d296bcd1de7bae94bf72179beb8ecb6915 on andy/fix-cpc-upgrade into 9a1586013d4b1bb894ba6cc34a0f11c0d84bbf09 on master.


TabView can't used in multiple pages

when i add tabview in serval pages , i found all the tabitem will be show together.    i can't new another tabview instance again .
the problem is very serious， can you fix it quickly ?

Can you provide a sample code? How do you add tabs and how you use another instance?

I've reproduces the problem. Thanks for reporting it. I'll work on it

example: add tabview in  mainpage.xaml , add another tabview to  notepage.xaml . just use the simple code . you will found all the tabitem add together .


[wrangler] Add better printing for complex unsafe metadata

What this PR solves / how to test:
Currently the following:
[unsafe.metadata]
myprop = { something = "whatever" }

Will print:
Your worker has access to the following bindings:
- Unsafe Metadata:
  - myprop: [object Object]

After this PR it will print:
Your worker has access to the following bindings:
- Unsafe Metadata:
  - myprop: {"something": "whatever"}

Alternatives include:

just JSON.stringify everything, including primitives
create a more complex formatter that nests nicely, etc (not sure what unsafe bindings do here)

Associated docs issues/PR:

[insert associated docs issue(s)/PR(s)]

Author has included the following, where applicable:

[ ] Tests
[ ] Changeset

Reviewer has performed the following, where applicable:

[ ] Checked for inclusion of relevant tests
[ ] Checked for inclusion of a relevant changeset
[ ] Checked for creation of associated docs updates
[ ] Manually pulled down the changes and spot-tested

Fixes # [insert issue number].

@mhart did you have a chance to add some tests to this? This looks good to go after that!


Uncaught The "path" argument must be of type string. Received type undefined

I'm re-opening this because #19081 is closed.
Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

[Enter steps to reproduce:]

Open a file
Press ctrl-s

Atom: 1.40.1 x64
Electron: 3.1.10
OS: Microsoft Windows 10 Pro
Thrown From: Atom Core
Stack Trace
Uncaught The "path" argument must be of type string. Received type undefined
At path.js:39

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
    at assertPath (path.js:39:11)
    at Object.join (path.js:434:7)
    at onEvents.e.map.e (~/AppData/Local/atom/app-1.40.1/resources/app/static/<embedded>:14:24548)
    at Array.map (<anonymous>)
    at watcher.e (~/AppData/Local/atom/app-1.40.1/resources/app/static/<embedded>:14:24400)

Commands
     -1:31.7.0 core:save (input.hidden-input)

Non-Core Packages

Reproduces how often:
100%

I can now see it is only for the files on network drives. Probably this is an issue linked to the GitKraken failure with repositories on network drives.

Thanks for opening a new issue for this - based on the error and the fact that you're using a network drive, I think this is a duplicate of https://github.com/atom/atom/issues/14227 so you can subscribe there for updates if you'd like.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Add tslint rule for only ES6 arrow functions (no function syntax)

There really should be no need for 'function'. Especially when Traditional functions don’t bind lexical scope (and Typescript does), which can lead to unexpected behavior when accessing ‘this’.
https://palantir.github.io/tslint/rules/only-arrow-functions/

Actually, it seems that with that rules now it refuses writing methods such as:
export function config() { ... }
Locally I get:
/swsui/src/config.ts
(1,8): non-arrow functions are forbidden

And travis shows similar error

Actually, it seems that with that rules now it refuses writing methods such as:
export function config() { ... }

I think you have to write them like:
export config = () => { ... }
Or something like that :)

This PR would need to rebase the pending 9 ones to adapt it.
I guess that we consolidate first for Sprint 1 and we can then apply code style changes.
Murphy has no mercy for demo effects.

The earlier we do change the lints the better, more code will make them hard to change later. I'm +1 for this change.

This issue has been open for a while. Do we still want this or should we close the PR?

Superseded by  #119


Droppable area "shrinks" when scrolling list of draggable items

Hello,
I'm having a problem using draggable items in an "overflowY: auto" list.
It seems like the droppable area shrinks when scrolling the list down, as seen in the example below:

This seems to be happening both in the version we are using (3.1.1) and in the latest version (4.0.3 at the time of writing).
A sandbox is available here: https://codesandbox.io/s/dndkit-overflowy-changesdroppableheight-6vqg3
Is there any way to tackle this problem?
Many thanks,
Lorenzo

Duplicate of #483

https://github.com/clauderic/dnd-kit/issues/483#issuecomment-985196079 fixes the problem. Thanks!


Add team annotation

towards https://github.com/giantswarm/giantswarm/issues/28871

We don't maintain or make changes to any openstack repos as the apps aren't in use @marieroque

Sorry @glitchcrab , too many PR at the same time, I didn't see the repo was not maintained!


FR: add linter-ignore-start,linter-ignore-end

Is Your Feature Request Related to a Problem? Please Describe.
I have some special css fragments, syntax，I have some special css fragments, syntax.
I don't want this area to be formatted
Describe the Solution You'd Like
A clear and concise description of what you want to happen.
Please include an example where applicable:
<!-- linter-ignore-start -->
                          This area will not be formatted
<!-- linter-ignore-end -->

<!-- linter-ignore-start -->
                          This area will not be formatted
<!-- linter-ignore-end -->```

## Describe Alternatives You've Considered

A clear and concise description of any alternative solutions or features you've considered.

## Additional Context

Add any other context or screenshots about the feature request here.

you can see https://prettier.io/docs/en/ignore.html#range-ignore

This is definitely an interesting suggestion. I am not sure if this will be added given how much of an overhaul it would take to accommodate this kind of setup with how the current ignoring of values works. However it may be worthwhile to reevaluate what would need to be done once #334  gets implemented.

Could you provide an example block that you do not want linted? I am not sure that the ignore start and end makes the most sense to fix the problem you are hitting, but it is likely more versatile.

I have been thinking about this and I will see about adding this for the next release. This is a much simpler way of allowing custom ignore than I initially thought up for doing it (I have a bad habit of trying to over complicate things). Hopefully I can tackle it some time this coming week or sooner.

@Leiyi548 , for non-pasting rules, would it also be helpful to be able to turn off a specific rule if only 1 is causing a problem?
I am guessing that this is something that would be desired, but I want to check here before I proceed with the regular custom ignore changes so they can go out together if possible. Right now, barring any issues with custom ignore, I just need to add documentation around the global custom ignore.

My previous comment would meant that each rule would look for its own alias as part of the range ignore to see if it needed to be disabled.
So something like:
<!-- linter-ignore-remove-multiple-blank-lines-start -->

                          This area will not be formatted by multiple blank lines

<!-- linter-ignore-remove-multiple-blank-lines-end -->

@pjkaufman It's awesome

@Leiyi548 , @chrisgrieser what do you think of the above? Any caveats that you can think of or would it not be useful?
I can see using the rule name in particular being useful, but also potentially causing problems for the aliases as they do change every once and a while (i.e. when a typo is present.).

@pjkaufman No Problem

Also, should the matching be exact or allow some leeway? For example allow multiple spaces inside the html comment or more than 2 dashes in the html comment?

@pjkaufman allow some leeway.

Gotcha. I can update it to allow some leeway. I will require that it be a single html comment though for each indicator.

The logic is currently mostly in place for the range for turning all linter rules on and off. The one for specific rules may need to be manually tested, but hopefully will pose no more of an issue than global range ignore.

I will likely review my first change for this to add global range indicators and get that merged. Once that is done, I will start on the rule specific range ignores.

I like the idea for this feature.
For consistency with how other linters implement the same feature, I'd suggest maybe using the same wording as them?
For example, [eslint uses enable and disable followed by a comma-separated list of rule names](eslint uses enable and disable followed by a rule name).
One thing to note here is also that the rule aliases actually cannot be found anywhere in the linter plugin settings, you have to follow the links to the docs. Adding the aliases to the (already quite crowded) linter settings page would work, but I think it could make more sense to add them in a more accessible way. Maybe inserting them via completion similar to tags?

I am fine with using enable and disable in place of start and end.
It would be nice to be able to allow text completion, but I am not entirely sure how easy that is in Obsidian. If it is simple in Obsidian that should be doable, but it it requires a lot of UI work then it may not be feasible at least not initially.

I like the idea for this feature.
For consistency with how other linters implement the same feature, I'd suggest maybe using the same wording as them?
For example, eslint uses enable and disable followed by a comma-separated list of rule names.
One thing to note here is also that the rule aliases actually cannot be found anywhere in the linter plugin settings, you have to follow the links to the docs. Adding the aliases to the (already quite crowded) linter settings page would work, but I think it could make more sense to add them in a more accessible way. Maybe inserting them via completion similar to tags?

@chrisgrieser , would it make sense to add a command that inserted start and end ignores for a rule or rules at the current cursor or around the selected text? I could possibly add something like that. That way the user would not need to know the aliases and could interact directly with the UI to get ignore blocks added.
I am still thinking about the comma separated rules options for rule names. I really am not a fan of parsing out which rules are disabled at a specific block since that will require each rule to check if the ignore block applies to them instead of just finding what applies to them from the get go, but that would be possible.

It could also be a multiselect with a preview of what the source code would look like post insertion.
Do note that the linter disabling syntax does not care about how it is found so long as it is present, so the value being found in a code block or inline code or math any kind of math block will result in it getting triggered.

Looks like suggestions could be done like how they are done via this plugin here, but that will require work in CodeMirror: https://github.com/tth05/obsidian-completr/blob/master/src/main.ts

would it make sense to add a command that inserted start and end ignores for a rule or rules at the current cursor or around the selected text? I could possibly add something like that. That way the user would not need to know the aliases and could interact directly with the UI to get ignore blocks added.

oh, that's even better.

I am still thinking about the comma separated rules options for rule names. I really am not a fan of parsing out which rules are disabled at a specific block since that will require each rule to check if the ignore block applies to them instead of just finding what applies to them from the get go, but that would be possible.

yeah, thinking about it, having the option to disable/enable specific rules is maybe a bit overkill yeah 😅
Just disabling/enabling the linter should be totally useful on its own, yes

would it make sense to add a command that inserted start and end ignores for a rule or rules at the current cursor or around the selected text? I could possibly add something like that. That way the user would not need to know the aliases and could interact directly with the UI to get ignore blocks added.

oh, that's even better.

I am still thinking about the comma separated rules options for rule names. I really am not a fan of parsing out which rules are disabled at a specific block since that will require each rule to check if the ignore block applies to them instead of just finding what applies to them from the get go, but that would be possible.

yeah, thinking about it, having the option to disable/enable specific rules is maybe a bit overkill yeah 😅
Just disabling/enabling the linter should be totally useful on its own, yes

I am definitely fine with having a single comment per rule to disable, but that would get tedious for users. So it is definitely a balancing act.

Looks like adding the ability to do autocomplete would require an EditorSuggest which will require CodeMirror code. This is possible, but will likely take more time than I have before I would like to do this next release. As such, I will break this feature change into 2 parts:

This issue will deal with adding custom ignore for all rules
The other that I will create will deal with rule specific ignoring

The custom ignore syntax should go out in the next release. The logic for ignoring specific rules will need to be addressed in a later ticket. I will have to look into rule specific ignores down the road. In the meantime, hopefully this will take care of most use cases for now.


Storage Sync Agent and DFS

Regarding section "Distributed File System (DFS)", the topic under "DFS Namespaces (DFS-N)" is misleading.
DFS namespace servers don't have any data, so the wording "You can install the Azure File Sync agent on one or more DFS-N members" suggests, you can put the agent on the Namespace servers, which is incorrect. You have to put the agent on the servers that are folder targets in the Namespace.
if you install agent on a namespace server, what are you going to add as the ServerEndpoint in Sync Group?
I believe someone can re-write this section to  be more accurate.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1aa8c1f7-dc55-7129-95be-687a0b11a636
Version Independent ID: 4a09b58a-9fd2-69fc-0348-e6d4d0956a20
Content: Planning for an Azure File Sync deployment
Content Source: articles/storage/file-sync/file-sync-planning.md
Service: storage
Sub-service: files
GitHub Login: @khdownie
Microsoft Alias: kendownie

@ramuvr
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

Submitted PR https://github.com/MicrosoftDocs/azure-docs/pull/100991

Addressed in separate PR (see above)
#please-close

Thank you for your dedication to our documentation.
We sincerely apologize for the delayed response. After a careful review, we are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


biber hangs if nametemplates is used without proper declaration

If I use unknown name parts
@book{demeke,
  author  = {given=Kebede, patronymic=Daniel, papponymic=Demeke},
  title   = {One},
  date    = {1983}
}

then biber simply issues a warning and ignores the namepart (which is the expected behaviour):
[451] Utils.pm:395> WARN - Invalid namepart 'patronymic' found in extended name format name 'author' in entry 'demeke', ignoring
[452] Utils.pm:395> WARN - Invalid namepart 'papponymic' found in extended name format name 'author' in entry 'demeke', ignoring

If I add nametemplates=ethiopian is simply hangs. It only works again when \DeclareUniquenameTemplate
is added.
\documentclass{article}

\usepackage[style=authoryear]{biblatex}

%needed:
%\DeclareUniquenameTemplate[ethiopian]{
%  \namepart[base=true]{given}
%  \namepart[disambiguation=full]{patronymic}
%  \namepart[disambiguation=full]{papponymic}
%}

\begin{filecontents}[overwrite]{nameparts-test.bib}
@book{demeke,
  author  = {given=Kebede, patronymic=Daniel, papponymic=Demeke,nametemplates=ethiopian},
  title   = {One},
  date    = {1983}
}
\end{filecontents}

\addbibresource{nameparts-test.bib}
\begin{document}

\cite{demeke}
\end{document}

This is one of those cases where the disambiguation code goes into an infinite loop due to null disambiguation information caused in this case by a missing uniquenametemplate. Fixed in the DEV branch - biber will warn and hard exit in such a case as no good can come of this situation ...

I'm not sure about the hard exist. Normally I expect from biber/bibtex to ignore fields they don't know (with a warning if needed)

It's more serious than a missing field. In such cases, there is no way to calculate uniqueness information at all because the requisite nameparts don't exist in the default template.


install bug:  Cannot find module '....atom\packages\node-debug\install'

Hi,
I'm running Windows 10, Atom version 1.9.8 , node version 6.3.1 npm version 3.10.3
When I try to run node-debug I get the following error message:

any ideas?

Is it the lates version of node-debug?

I have the same on linux.
I installed from Atom Settings.
"version": "0.1.7"
Where should the module ~/.atom/packages/node-debug/install come from?

I also tried this and I am still getting the same error:
install bug · Issue #2 · Andifeind/atom-node-inspector
https://github.com/Andifeind/atom-node-inspector/issues/2#issuecomment-237734478

Sorry, I forgot:
Debian mix (mostly testing, some ubuntu)
nodejs v6.9.2 (from debian experimental)
npm 1.4.21
Atom 1.15.0
I installed sudo npm install -g node-inspector, and changed permissions, so I can start it from the console. Now the error message is gone, but nothing happens.
@Andifeind are you still working with the package?

ok, I now use node-inspector directly.
With process-palette and command-toolbar this is comfortable.
Thanks for listening :-)

to be complete:
In node-inspector repo I read this:
"Since version 6.3, Node.js provides a buit-in DevTools-based debugger which mostly deprecates Node Inspector, see e.g. this blog post to get started. The built-in debugger is developed directly by the V8/Chromium team and provides certain advanced features (e.g. long/async stack traces) that are too difficult to implement in Node Inspector."
I could use this as describe in the post:
node --inspect --debug-brk my-script.js

which outputs an url:
chrome-devtools://devtools/remote/serve_file/...

open this in chrome and voila!
Would be fine to have this automated...


Variables must be initialized before usage.

Title
Variables must be initialized before usage.
Description
Always initialize a variable before usage. This can improve readability and make debugging easier.
Reason for the rule
Using uninitialized variables may lead to strange behavior, the code may become harder to debug and in some cases readability of the code can decrease.
Bad code sample - developer's error - forgot to mark variable z with var
var
    x: Integer;
    z: Integer;

procedure Proc1();
var
begin
    Proc2(z);
    x := z;
end;

procedure Proc2(z: Integer);
var
begin
    z := 10;
end;

Good code sample - developer's error - forgot to mark variable z with var - fixed
var
    x: Integer;
    z: Integer;

procedure Proc1();
var
begin
    Proc2(z);
    x := z;
end;

procedure Proc2(var z: Integer);
var
begin
    z := 10;
end;

Bad code sample 2
    procedure TestFunc()
    var
        a: Integer;
        b: Integer;
    begin
        b := a + 1;
    end;

Good code sample 2
    procedure TestFunc()
    var
        a: Integer;
        b: Integer;
    begin
        a := 0;

        b := a + 1;
    end;

Good and bad practices for fixing the rule
Initialize variable
Remarks
Variables of the following types are analyzed: Integer, BigInteger, Boolean, Byte, Char, Code, Date, DateTime, Decimal, List, Record, Time
Some variables need special initialization, e.g. List is initialized via .Add(), Record initialized via .Init(), .Clear() or assignment.
Local record variables and arrays are ignored
Global record variables can be initialized in other method
Initialization is possible via evaluate, for, foreach statements
If variable is passed in method via var, the rule consider it is initialized in the method

Personally, I don't see the need for the init. You should know the default values of these variable type.

Bad code sample 2
Good code sample 2

Nothing changes except more lines. It's explicit, but didn't add value.

I agree for this simple example, but when it gets more complicated it is not that easy to spot as a developer.
    procedure TestFunc()
    var
        a: Integer;
        b: Integer;
    begin
...
// A lot of code
...
        b := a + 1;
    end;

In the A lot of code are there one code path that did not assign a value to a ???

If you have so much code in function that its not easy to spot the value of a variable, then you should refactor this function. Move code to new functions, make it readable. Then there is no need to explicitly init these variables.

Isn't this one done and can be closed, too?

The suggestion has been addressed.


Failed to compile Mapnik for Node 4.0

$ nvm install v4.0.0
$ git clone https://github.com/kartotherian/kartotherian.git krt

Cloning into 'krt'...
remote: Counting objects: 1448, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 1448 (delta 0), reused 0 (delta 0), pack-reused 1444
Receiving objects: 100% (1448/1448), 298.46 KiB | 298.00 KiB/s, done.
Resolving deltas: 100% (906/906), done.
Checking connectivity... done.

$ cd krt
$ npm install

npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">= 0.10.0 < 0.11.0"} (current: {"node":"4.0.0","npm":"2.14.2"})
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.10.x"} (current: {"node":"4.0.0","npm":"2.14.2"})
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.10.x"} (current: {"node":"4.0.0","npm":"2.14.2"})

><EMAIL_ADDRESS>install /home/yurik/wmf/kartotherian/krt/node_modules/bunyan/node_modules/dtrace-provider
> node scripts/install.js

><EMAIL_ADDRESS>install /home/yurik/wmf/kartotherian/krt/node_modules/mapnik
> node-pre-gyp install --fallback-to-build

make: Entering directory '/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/build'
  ACTION binding_gyp_make_vector_tile_target_generate_protoc_files Release/obj/gen/vector_tile.pb.cc
/bin/sh: 1: protoc: not found
make_vector_tile.target.mk:13: recipe for target 'Release/obj/gen/vector_tile.pb.cc' failed
make: *** [Release/obj/gen/vector_tile.pb.cc] Error 127
make: Leaving directory '/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/yurik/.nvm/versions/node/v4.0.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.19.0-28-generic
gyp ERR! command "/home/yurik/.nvm/versions/node/v4.0.0/bin/node" "/home/yurik/.nvm/versions/node/v4.0.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/lib/binding/node-v46-linux-x64/mapnik.node" "--module_name=mapnik" "--module_path=/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/lib/binding/node-v46-linux-x64"
gyp ERR! cwd /home/yurik/wmf/kartotherian/krt/node_modules/mapnik
gyp ERR! node -v v4.0.0
gyp ERR! node-gyp -v v3.0.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/home/yurik/.nvm/versions/node/v4.0.0/bin/node /home/yurik/.nvm/versions/node/v4.0.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/lib/binding/node-v46-linux-x64/mapnik.node --module_name=mapnik --module_path=/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/lib/binding/node-v46-linux-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:817:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Linux 3.19.0-28-generic
node-pre-gyp ERR! command "/home/yurik/.nvm/versions/node/v4.0.0/bin/node" "/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/yurik/wmf/kartotherian/krt/node_modules/mapnik
node-pre-gyp ERR! node -v v4.0.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.9
node-pre-gyp ERR! not ok
Failed to execute '/home/yurik/.nvm/versions/node/v4.0.0/bin/node /home/yurik/.nvm/versions/node/v4.0.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/lib/binding/node-v46-linux-x64/mapnik.node --module_name=mapnik --module_path=/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/lib/binding/node-v46-linux-x64' (1)
npm ERR! Linux 3.19.0-28-generic
npm ERR! argv "/home/yurik/.nvm/versions/node/v4.0.0/bin/node" "/home/yurik/.nvm/versions/node/v4.0.0/bin/npm" "install"
npm ERR! node v4.0.0
npm ERR! npm  v2.14.2
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the mapnik package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR!     npm owner ls mapnik
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/yurik/wmf/kartotherian/krt/npm-debug.log

/bin/sh: 1: protoc: not found

You need to have the protobuf tools installed.  If you're on Ubunutu, do apt-get install protobuf-compiler, for Mac OSX with Homebrew, do brew install protobuf.  Then try npm install again.

@danpat, thanks for the quick reply.  On Ubuntu, I installed protobuf-compiler 2.6.1-1, and now the error changed. Btw, it works fine for 0.10 and 0.12 versions of node, even without the protobuf-compiler.
><EMAIL_ADDRESS>install /home/yurik/wmf/kartotherian/krt/node_modules/mapnik
> node-pre-gyp install --fallback-to-build

make: Entering directory '/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/build'
  ACTION binding_gyp_make_vector_tile_target_generate_protoc_files Release/obj/gen/vector_tile.pb.cc
  ACTION binding_gyp_make_vector_tile_target_generate_setting Release/obj/gen/mapnik_settings.js
  COPY /home/yurik/wmf/kartotherian/krt/node_modules/mapnik/lib/binding/node-v46-linux-x64/mapnik_settings.js
  TOUCH Release/obj.target/make_vector_tile.stamp
  CXX(target) Release/obj.target/vector_tile/gen/vector_tile.pb.o
In file included from Release/obj/gen/vector_tile.pb.cc:5:0:
Release/obj/gen/vector_tile.pb.h:9:42: fatal error: google/protobuf/stubs/common.h: No such file or directory
 #include <google/protobuf/stubs/common.h>
                                          ^
compilation terminated.
vector_tile.target.mk:176: recipe for target 'Release/obj.target/vector_tile/gen/vector_tile.pb.o' failed
make: *** [Release/obj.target/vector_tile/gen/vector_tile.pb.o] Error 1
make: Leaving directory '/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/build'

@nyurik You'll also need libprotobuf-dev, sorry, I thought it would get installed with protobuf-compiler.
For Node 0.10 and 0.12, there are pre-packaged binaries that get installed.  Because 4.0.0 is so new, we haven't released pre-packaged binaries, so the install is falling back to compiling from source.

@danpat next batch of errors:
In file included from ../src/utils.hpp:7:0,
                 from ../src/mapnik_logger.cpp:1:
../node_modules/nan/nan.h:261:25: error: redefinition of ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Local<T>)’
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) {
                         ^
../node_modules/nan/nan.h:256:25: note: ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Handle<T>)’ previously declared here
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) {
                         ^
../node_modules/nan/nan.h:661:13: error: ‘node::smalloc’ has not been declared
     , node::smalloc::FreeCallback callback
             ^
../node_modules/nan/nan.h:661:35: error: expected ‘,’ or ‘...’ before ‘callback’
     , node::smalloc::FreeCallback callback
                                   ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(char*, size_t, int)’:
../node_modules/nan/nan.h:665:50: error: ‘callback’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                  ^
../node_modules/nan/nan.h:665:60: error: ‘hint’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                            ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(const char*, uint32_t)’:
../node_modules/nan/nan.h:672:67: error: call of overloaded ‘New(v8::Isolate*, const char*&, uint32_t&)’ is ambiguous
     return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
                                                                   ^
../node_modules/nan/nan.h:672:67: note: candidates are:
In file included from ../node_modules/nan/nan.h:25:0,
                 from ../src/utils.hpp:7,
                 from ../src/mapnik_logger.cpp:1:
/home/yurik/.node-gyp/4.0.0/include/node/node_buffer.h:31:40: note: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, v8::Local<v8::String>, node::encoding) <near match>
 NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                        ^
/home/yurik/.node-gyp/4.0.0/include/node/node_buffer.h:31:40: note:   no known conversion for argument 3 from ‘uint32_t {aka unsigned int}’ to ‘node::encoding’
/home/yurik/.node-gyp/4.0.0/include/node/node_buffer.h:43:40: note: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, char*, size_t) <near match>
 NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                        ^
/home/yurik/.node-gyp/4.0.0/include/node/node_buffer.h:43:40: note:   no known conversion for argument 2 from ‘const char*’ to ‘char*’
In file included from ../src/utils.hpp:7:0,
                 from ../src/mapnik_logger.cpp:1:
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(uint32_t)’:
../node_modules/nan/nan.h:676:61: error: could not convert ‘node::Buffer::New(v8::Isolate::GetCurrent(), ((size_t)size))’ from ‘v8::MaybeLocal<v8::Object>’ to ‘v8::Local<v8::Object>’
     return node::Buffer::New(v8::Isolate::GetCurrent(), size);
                                                             ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanBufferUse(char*, uint32_t)’:
../node_modules/nan/nan.h:683:12: error: ‘Use’ is not a member of ‘node::Buffer’
     return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
            ^
mapnik.target.mk:204: recipe for target 'Release/obj.target/mapnik/src/mapnik_logger.o' failed
make: *** [Release/obj.target/mapnik/src/mapnik_logger.o] Error 1
make: Leaving directory '/home/yurik/wmf/kartotherian/krt/node_modules/mapnik/build'

Looks these errors are related to the version of nan we're using not supporting Node v4.0.0:
https://github.com/mapnik/node-mapnik/blob/master/package.json#L44
nan 2.0.0 got support for io.js (see https://github.com/nodejs/nan/blob/master/CHANGELOG.md) and according to some google-fu, the errors above are fixed by that.

Thanks, would simply bumping package.json's nan version work?

I suspect it won't work, I think the nan API changed a bit in 2.0.0 that will require some re-work.  Give it a go and let us know, and if you are able to make a patch to get it fixed, please send it in :-)

Sorry getting into this conversation late but please see this pull request https://github.com/mapnik/node-mapnik/pull/509 once that is done we should be able to support node v4.

Closing, will track at https://github.com/mapnik/node-mapnik/pull/509


how to disable alt + mouse click actions in JWM

Is it possible to disable alt + left and right mouse click actions? Right now the defaults are;
alt + left mouse : window dragging
alt + right mouse : window scale
I cant find a way to disable this behaviour.
This is very annoying. I am a 3D Artist and i cant use my main 3d software (Autodesk Maya) because of this. Because the program is using alt + mouse click navigation. (and there are lots of other programs that uses the same behaviour) Please Joe help me. I really like your work and dont want to skip JWM because of this. Thanks in advance.

Unfortunately that's not configurable right now.  A long standing issue is to make mouse bindings configurable.  Some behaviors, such as this, are more important than others though (who really wants left click on the title bar to do something other than move?).  So I think I'll probably try to work in a near-term solution that will attempt to work like a more generic solution.
In the mean time, if you want to disable this, it can be done with a fairly minor code change.  In event.c in the DispatchBorderButtonEvent function (around line 1537), comment out the special case around the MoveClient call.  Something like this:
   /* Middle click starts a move unless it's over the maximize button. */
   action = GetBorderActionType(np, event->x, event->y);
/*
   if(event->button == Button2 && action != BA_MAXIMIZE) {
      MoveClient(np, event->x, event->y);
      return;
   }
*/

In trying to come up with a fix for this, I realized that the code that you want to remove is actually in event.c in the HandleButtonEvent function (around line 399):
         switch(event->button) {
         case Button1:
         case Button2:
            FocusClient(np);
            RaiseClient(np);
            if(move_resize) {
/*
               GetBorderSize(&np->state, &north, &south, &east, &west);
               MoveClient(np, event->x + west, event->y + north);
*/
            }
            break;

I was going to do something more extreme, but I ended up just adding a "nodrag" group option.  So, as of snapshot 1517, you can disable this binding with:
<Group>
    <Option>nodrag</Option>
</Group>

This is a little bit of a hack since complete control over key bindings is the ultimate goal, but it's a quick fix that avoids breaking existing configurations.
Please let me know if that does what you need.

Where should i add this?

thank you Joe, i tried to help the @abrasmelin , but i could not!
vlw fwi, Holmes :)

Ah so in order to this work i need to update jwm? Can you also add noscaling to groups? Because alt left mouse drags the window okay but also alt right click scales the window. Also holmes will you add this updated version?

You do need to update JWM (and be sure to exit the old version; restart won't pull in the new code).  The nodrag option should disable both left and right click over the window content.


Add nextWithEquals to TreeOfLosers

A tree of losers maintains a partial order of mergeable values. As a
value makes its way to the top of the tree, it will meet the losers of
previous comparisons. If the value meets an equal value, it is known
that there is at least one duplicate coming after the
value. nextWithEquals returns a pair of stream, equal flag, where the
flag is set if there will be at least one repeat. The streams at the
leaves of the tree are expected to produce unique sorted values. This
feature is useful for merging a group by where each stream has ordered
distinct grouping keys.

@oerling Orri, a quick question before I read the code.

The streams at the leaves of the tree are expected to produce unique sorted values.

Is this an in important requirement? We are currently using ToL for merging data that is not guaranteed to have unique sorted values.

nextWithEquals needs unique values in streams, next does not. nextWithEquals does not have to have unique values in each stream if it compares the next and previous but this does not happen in the group by case, for which nextWithEquals is intended.
There are some more tricks that can apply to ToL, like counting how many key parts of multi-part keys are shared between streams  and thus do not have to be compared but we get to these later, if needed.
From: Maria Basmanova @.>
Sent: Friday, April 8, 2022 1:37 PM
To: facebookincubator/velox @.>
Cc: oerling @.>; Mention @.>
Subject: Re: [facebookincubator/velox] Add nextWithEquals to TreeOfLosers (PR #1384)
@oerling https://github.com/oerling  Orri, a quick question before I read the code.
The streams at the leaves of the tree are expected to produce unique sorted values.
Is this an in important requirement? We are currently using ToL for merging data that is not guaranteed to have unique sorted values.
—
Reply to this email directly, view it on GitHub https://github.com/facebookincubator/velox/pull/1384#issuecomment-1093337440 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKPPPT6BX3MZDRXTKJDWBCTVECKH3ANCNFSM5S5OVKBA .
You are receiving this because you were mentioned.Message ID: @.***>


xUnit xml format uses errors not failures

Hello,
We are using the built-in xUnit reporter as part of Mocha and are running into an issue where the xml generated treats assertion failures as errors. Specifically, when a test fails as a result of an assertion, the errors attribute on the  element is used rather than the failures attribute.
/* Actual output /
<testsuite name="Mocha Tests" tests="4" failures="0" errors="1" skipped="0" timestamp="Tue, 20 Oct 2020 15:24:27 GMT" time="136.099">
/ Expected output */
<testsuite name="Mocha Tests" tests="4" failures="1" errors="0" skipped="0" timestamp="Tue, 20 Oct 2020 15:24:27 GMT" time="136.099">
Ultimately for us, this causes the test report functionality of Bitbucket Pipelines to fail rendering the xml output. Comparing Jnit xml output, it uses the failures attribute for assertion failures rather than errors, which seems correct to me.
My expectation would be that errors are used for test execution problems, not test assertion failures and seems like it should be a bug. I have included the xml output below.
<testsuite name="Mocha Tests" tests="1" failures="0" errors="1" skipped="0" timestamp="Tue, 20 Oct 2020 15:24:27 GMT" time="136.099">     <testcase classname="Class Tests" name="should test the class" time="13.213">         <failure>Setting an on purpose fail so I can see if xunit results are being reported. AssertionError [ERR_ASSERTION]: Setting an on purpose fail so I can see if xunit results are being reported.     at Context.<anonymous> (test/sample/sample.test.ts:76:16)     at processTicksAndRejections (internal/process/task_queues.js:97:5)</failure>     </testcase> </testsuite>
What is the expectation of errors vs failures for the xml file? We can work around the issue by post processing the xml file, but wanted to see if I should report a bug on this issue, or if it's working as expected.
Thanks,
Kevin

there was an issue about this before... I am not sure if there was a PR for it or what, but obviously it hasn't been addressed.
I think the main problem is that Mocha doesn't really know the difference between a "failure" and an "error".  Why?  Because all test failures come in the form of a thrown exception (or rejected Promise).  They are errors.  Thus, failures: 0 is hardcoded in the xunit reporter.
If an "error" in XUnit parlance means "test execution problem", we need to define "test execution problem".  We could assume that any exception thrown outside of the context of a test is an "error" (e.g., in a hook, in Mocha itself, etc.), but this does not always hold--some people make assertions in hooks.  Is misusing Mocha's API an "error"?  For instance, calling done twice.  What of uncaught exceptions or unhandled rejections?
We can (usually) recognize errors from Mocha itself, because have a code prop which matches /^ERR_MOCHA_/.
Further complicating things is that none of the current Mocha maintainers actually use the XUnit reporter, and we could really use help from somebody who does, and is interested in maintaining it.
To move this forward, I think what we need next is a definition of clear boundaries between "failure" and "error" in the context of Mocha.  I can't do that myself, but I can certainly provide some direction on an eventual implementation.

As a current work-around, we've got a custom reporter that essentially treats all errors as failures. This works for us currently, but we would like to jump in and contribute to the XUnit reporter if we can. It looks like there are several links on the main README.md that will be useful for us to get started...is there anything else we should read before jumping in on this? Thanks again for your help!
Kevin


Asks for "Username for '://':"

I was cloning a github repository using tortoise git.
I have permission over the git so instantly it asked the id and password of github..
After downloading all the non-lfs files github files, it asked me username and password for the lfs. Except the problem was the url it was asking for was blank.
I checked the git lfs env and found that my Endpoint was missing. So, I added this line to my config file inside .git
[lfs]
url = https://github.com/JuicedUpLabs/MidiZ.git/info/lfs
The problem now is, I had made some changes to the files in my rep and cannot pull anything. Did doing that fixed the git lfs?

Doing a "$ git lfs fetch" might seem to work..

Is it possible for you to use the origin remote? I'm guessing you're using something else. This is a current limitation of Git LFS, unfortunately.
If you can't use origin, try setting the lfs.url property in a .gitconfig file. By only setting it in your local .git directory, the setting only applies to your local clone. Any other clones will have to also set that value. You can fix this by running this:
$ git config -f .gitconfig lfs.url https://github.com/JuicedUpLabs/MidiZ.git/info/lfs

This should add a .gitconfig file that you can commit in your repository.
I know this is a subpar workaround. It's something we'd like to fix up in the future.


feat(dashboard): confirm overwrite to prevent unintended changes

SUMMARY
At Airbnb, there's reasonable amount of reporting about unintended overwritten of filter scopes settings.
We believe there must be unknown overwriting on json_metadata by other authors during editing. (json_metadata can be easily overwritten since it passes all attributes including unchanged values.)
This commit introduces the inspection step for this high volatility value changes and then proceed to update with the user's confirmation. (the inspection items are defined here)
This commit also adds the logging for the user confirmation.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/1392866/195903661-131177c7-812d-4a38-8d56-b6e429b27cbd.mov
TESTING INSTRUCTIONS

set ENABLE_CONFIRM_OVERWRITE_DASHBOARD_METADATA feature flag to true
go to any dashboard page
update css or/and filter scopes
click save to confirm the overwrite values

ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Required feature flags: ENABLE_CONFIRM_OVERWRITE_DASHBOARD_METADATA
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[ ] Removes existing feature or API

cc: @ktmud @john-bodley

Thanks for this exciting feature @justinpark! Some first-pass comments:
1 - Can we rename the feature flag to a shorter name like DASHBOARD_METADATA_DIFF or anything else?
2 - Can you add the new feature flag to RESOURCES/FEATURE_FLAGS.md?
3 - Can we set a min/max width/height to the modal to avoid the situation where it takes the whole screen?
4 - Can we make the modal appear only when there's a change to the scope or CSS? Unrelated changes shouldn't present it.
5 - Is it possible to make the scope changes more user-friendly? It's showing ID diffs that are not traceable to the screen. Maybe add the chart names to the diff or use a different kind of scope representation when comparing.

1 - Can we rename the feature flag to a shorter name like DASHBOARD_METADATA_DIFF or anything else?

I updated to CONFIRM_DASHBOARD_DIFF

2 - Can you add the new feature flag to RESOURCES/FEATURE_FLAGS.md?

Yes. updated.

3 - Can we set a min/max width/height to the modal to avoid the situation where it takes the whole screen?

Yes I added the maxWidth using responsive. (its size up to 1024px)

4 - Can we make the modal appear only when there's a change to the scope or CSS? Unrelated changes shouldn't present it.

Sure. The modal only pops up when the following values are changed.
export const OVERWRITE_INSPECT_FIELDS = ['css', 'json_metadata.filter_scopes'];

5 - Is it possible to make the scope changes more user-friendly? It's showing ID diffs that are not traceable to the screen. Maybe add the chart names to the diff or use a different kind of scope representation when comparing.

as @ktmud commented, it becomes complicated to access the scope labels and its hierarchy. I'll follow up this improvement in the next step.

1 - Can we rename the feature flag to a shorter name like DASHBOARD_METADATA_DIFF or anything else?

I updated to CONFIRM_DASHBOARD_DIFF

2 - Can you add the new feature flag to RESOURCES/FEATURE_FLAGS.md?

Yes. updated.

3 - Can we set a min/max width/height to the modal to avoid the situation where it takes the whole screen?

Yes I added the maxWidth using responsive. (its size up to 1024px)

4 - Can we make the modal appear only when there's a change to the scope or CSS? Unrelated changes shouldn't present it.

Sure. The modal only pops up when the following values are changed.
export const OVERWRITE_INSPECT_FIELDS = ['css', 'json_metadata.filter_scopes'];

5 - Is it possible to make the scope changes more user-friendly? It's showing ID diffs that are not traceable to the screen. Maybe add the chart names to the diff or use a different kind of scope representation when comparing.

as ktmud commented, it becomes complicated to access the scope labels and its hierarchy. I'll follow up this improvement in the next step.

@michael-s-molina do you have any objections with the approach? We'd like to kick off the feature with JSON diffs first. (and then will follow up the improved labels version)

@michael-s-molina do you have any objections with the approach? We'd like to kick off the feature with JSON diffs first. (and then will follow up the improved labels version)

No problem 👍🏼

@michael-s-molina do you have any objections with the approach? We'd like to kick off the feature with JSON diffs first. (and then will follow up the improved labels version)

No problem 👍🏼

Great! can you approve the change? (it's blocked by the reviewers)


Windows binaries not working starting from pkg 5.13.0

Find the reason here: https://github.com/yao-pkg/pkg-fetch/pull/37
Any help fixing this on pkg-fetch side is more then welcome

I managed to find the cause for this issue.
The order for placeholders (except bakery which occurs only once) is:
Windows binary:
<placeholder in source string> <bakery> <placeholder in bytecode(?)>
Linux binary:
<placeholder in bytecode(?)> <bakery> <placeholder in source string>
The producer always replaces the first occurence, and replacing the source string does nothing
Replacing the correct one fixes the generated binary on windows
Hacking together a quick fix works on my Windows test box
https://github.com/faulpeltz/pkg/commit/f4d254c513152d1694051307f611cd8be2fc0f68
However the fix is bit ugly, maybe there is a more elegant solution.
I'm not sure why the order is like that, maybe it depends on the platform linker settings?

@faulpeltz Thanks so much for looking at this! Could you submit a PR? I sincerly have no idea why this has changed starting from latest nodejs versions, if you find out more let me know. In the meanwhile please open a PR and also add a comment that reference to this issue