There was an error running the selected code generator.

I am struggling following the tutorial as written. When I try to add a Razor page using the Entity Framework (CRUD), I get an error that says: "There was an error running the selected code generator. Package restore failed. Rolling back package...."
I know this isn't the support forum, but it is really tough working through the tutorials with no information on why the documented step could not complete.

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

ID: 6719f08e-3bd7-dc1a-71df-f2ef9fbca9d8
Version Independent ID: 7096fdb3-612e-9e00-bd0b-8ea4886a09ce
Content: Add a model to a Razor Pages app in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/model.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Could you be more specific and give us more info about the issue?
What your dev environment setup looks like (target framework, VS version, SDK version, etc etc)?
I'm guessing it is VS/Nuget-related issue with your setup so try to verify that you have proper nuget sources specified.

I followed instructions directly from the tutorial. Running VS 2017 Pro. Entity Framework 6.2 ASP.Net core 2.1. This is a new install on a new Win10 box (first project with VS).

@420tech  what version of Visual Studio and .Net core SDK?
dotnet --version

Visual Studio 15.7.4. ASP.Net core 2.1.301.

@420tech  are you following the 2.1 version of the tutorial? What step gives you an error?
That's a really old error message we saw in the 2.0 version.

The second step - "Add a model". When I tried to generate a razor page using the "Add Scaffold.." and Razor Pages using Entity Framework (CRUD).

@420tech  I assume you are using this sample? https://github.com/aspnet/Docs/tree/master/aspnetcore/tutorials/razor-pages/razor-pages-start/sample/RazorPagesMovie

I am writing the code myself directly from the tutorial. I am not using any of the code from GitHub. The tutorial I am following can be found here: https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/model?view=aspnetcore-2.1
The step it fails on is the "Add a model". The Add Scaffold part fails on the code generation. Everything I can see tells me I am using 2.1 (e.g. in the Dependencies under NuGet is EntityFramework 6.2, Microsoft.AspNetCore 2.1 and related aspnetcore - all 2.1).

That's odd, could you push your project to the repo so we can clone it and try to repro this on our own?

@420tech  try this
dotnet new webapp -o RazorPagesMovie
cd RazorPagesMovie
dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Design

dotnet tool install -g dotnet-aspnet-codegenerator --version 2.1.0

// Add movie model to project
// Build run the app.
//  From project directory, run in a command window

dotnet aspnet-codegenerator razorpage -m Movie -dc RazorPagesMovie.Data.MovieContext -udl -outDir Pages\Movies --referenceScriptLibraries

dotnet ef migrations add Initial
dotnet ef database update

Thanks @Rick-Anderson! That worked!

I'm not sure if anyone else is having the same issue anymore but a coworker fixed this error for me by building the web application and THEN creating a new razor page.

I have fixed it, by install the package Microsoft.VisualStudio.Web.CodeGeneration.Design from nuget.

In my case, the problem was caused by missing Microsoft.EntityFrameworkCore.Tools NuGet package. Installing it solved the problem.

@Rick-Anderson Thank u sooo much it solve my problem

Just connect to the Internet to download and install the package.

A year later, it seems this tutorial has not been updated. I am new to .Net Core, and am also following this tutorial:
I started on this page:
https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/razor-pages-start?view=aspnetcore-5.0&tabs=visual-studio
I then clicked on Next: Add a Model which took me to this page:
https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/model?view=aspnetcore-5.0&tabs=visual-studio
When I get to the section where I'm adding a new scaffolded item (CRUD), it fails. It seems it is trying to automatically add Entity Framework related NuGet packages that are only supported on .Net Standard, and this is a .Net Core 5 application.
Is there a new tutorial I should be following?

ckages that are only supported on .Net Standard, and this is a .Net Core 5 application.

There is no such thing as .NET Core 5. This tutorial works with .NET 5.  I'm not sure what you're doing wrong, but it works.

Yes, you are correct. I misspoke. The target framework is set to .Net 5.0.
The error seems to have something to do with the scaffolding sequence trying to do some sort of background add of additional NuGet packages, but I see no diagnostic error output other than this error dialog.
I added the following NuGet packages via the NuGet  package manager:

Microsoft.EntityFrameworkCore
Microsoft.EntityFrameworkCore.Abstractions
Microsoft.EntityFrameworkCore.Analyzers
Microsoft.EntityFrameworkCore.Design
Microsoft.EntityFrameworkCore.Relational
Microsoft.EntityFrameworkCore.Tools

I then tried to add the scaffolding again. This time I saw a quick dialog that indicates it was trying to add the NuGet package Microsoft.EntityFrameworkCore.SqlServer.  But that transient dialog quickly went away and the same error dialog appeared.
I tried to add Microsoft.EntityFrameworkCore.SqlServer, but it failed due to lots of things not being compatible with .Net 5.0. Studying its dependencies, it looked like the only thing it needed that I had not already referenced was Microsoft.Data.SqlClient, so I tried adding that. Same thing, it had dependencies to old libraries that were not compatible with .Net 5.0.
Although I am following the tutorial, I had tried jumping ahead a bit by creating my own model class.  I am going to create a new project and go through the tutorial again, this time following it exactly (i.e. creating the Movie class) and see if that works. Perhaps that will give me a hint as to where I went off track.

Found this suggestion: go to Tools -> Options -> Nuget Package Manager ->Package Manager Setting-> General -> Clear All Nuget Cache(s).
Once I did that, the dialogs during the scaffolding wizard run were a bit more informative and clearly told me it was trying to add more NuGet packages.
But eventually it still failed.
But somewhere in this sequence it started flashing a warning dialog saying I was going to overwrite the Index.cshtml file. I had been doing the right click to start the scaffolding run on the top "Pages" folder, which did have an Index.cshtml file.  So for grins, I created a new subfolder under the Pages folder, then ran the scaffolding wizard in that folder. It worked!
So this problem, from my experience, seems to have something to do with the fact that the scaffolding wizard generates an Index.cshtml file and there better not be one already there!
Bad diagnostics from Visual Studio for sure, but hopefully my post will help someone else get past this step.

I think the fix is to update your Visual Studio to the latest using Check for update in Help menu.

Yes, you are correct. I misspoke. The target framework is set to .Net 5.0.
The error seems to have something to do with the scaffolding sequence trying to do some sort of background add of additional NuGet packages, but I see no diagnostic error output other than this error dialog.
I added the following NuGet packages via the NuGet package manager:

Microsoft.EntityFrameworkCore
Microsoft.EntityFrameworkCore.Abstractions
Microsoft.EntityFrameworkCore.Analyzers
Microsoft.EntityFrameworkCore.Design
Microsoft.EntityFrameworkCore.Relational
Microsoft.EntityFrameworkCore.Tools

I then tried to add the scaffolding again. This time I saw a quick dialog that indicates it was trying to add the NuGet package Microsoft.EntityFrameworkCore.SqlServer. But that transient dialog quickly went away and the same error dialog appeared.
I tried to add Microsoft.EntityFrameworkCore.SqlServer, but it failed due to lots of things not being compatible with .Net 5.0. Studying its dependencies, it looked like the only thing it needed that I had not already referenced was Microsoft.Data.SqlClient, so I tried adding that. Same thing, it had dependencies to old libraries that were not compatible with .Net 5.0.
Although I am following the tutorial, I had tried jumping ahead a bit by creating my own model class. I am going to create a new project and go through the tutorial again, this time following it exactly (i.e. creating the Movie class) and see if that works. Perhaps that will give me a hint as to where I went off track.

I solved the issue by rolling back to v5.0.9 from v5.0.10!

i had this problem, it was because i only had the visual studio offline nuget source, adding the nuget.org as a nuget source fixed it. see here https://stackoverflow.com/questions/69045231/nuget-package-sources-missing


Term.num2str(): Ordinal number of 111 is "111th", but "111st" was returned

Summary
Term.num2str(): Ordinal number of 111 is "111th", but "111st" was returned. This bug will impact on phases names when over 111 change points exists.
Related classes

covsirphy.Term

Codes and outputs:
from covsirphy import Term
Term.num2str(111)

This code should return "111th", but "111st" was returned.
Environment

CovsirPhy version: 2.8.1
Python version; 3.8
Installation: pipenv
OS: WSL

WIll be fixed in version 2.8.1-alpha and stable version 2.8.2 or 2.9.0


⚠ Bofrost.be has degraded performance

In ac24c59, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1395 ms

Resolved: Bofrost.be performance has improved in 3aef4af.


Optional properties prevent casting generic objects

Flow version: 0.97.0

Possibly related to #5334

When you have an unsealed object map-like type defined as in the example, it is impossible to cast it to any other object type even though the additional, non-map-like properties are marked as optional. Not sure if bug or by design?
The only workaround I found was either removing the key?: string property from KeyedObject, or adding a key?: string property to MyObject. In practice, we can never populate the key property (as it is optional), but this "pollutes" my types with an extra, unwanted property.
https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVBTAHgBzgJwBcxCBPHDMAaQ1IwBMB5AIwCsMBjYgXjAG9UYMAGtaAfgBcYAM6F8ASwB2AcwA0gsAG1ZClQF0pAQ0Wl1AXwDc6bHiIlylALKkW7LmF4ChiwwFsMUjpKahry9FKKAK6+zBj45laoMBjEhvj4Us6unISaeh5aGl5CYD7+UgDkhBiyFeolYGFSAIz1YGZtxd5+AWBVNYQATHUaQk1gg20dqHqJycSidOHUtAzZXHkFABRpGStL67l6AJQWQA
Expected behavior
Flow should not throw an error.
Actual behavior
    24: let keyed: KeyedObject[] = (arr: KeyedObject[]);
                                    ^ Cannot cast `arr` to array type because property `key` is missing in `MyObject` [1] but exists in `KeyedObject` [2] in array element.
        References:
        13: let arr: MyObject[] = [
                     ^ [1]
        24: let keyed: KeyedObject[] = (arr: KeyedObject[]);
                                             ^ [2]

If this is indeed a bug, I would be happy to help with this, but I would appreciate some pointers on where to look if possible :)

Any updates on this? Running into a similar bug.

This only works if everything is readonly


#14 LayerSettings::new_with_map_type

Implementation for #14 , should this be named new_with_mesh_type or is new_with_map_type better?

Adjusted hex and iso examples to use the new function.
Corrected window titles for the iso_staggered and hex_row examples.

Maybe it would be nice to think about a builder-pattern here? It's already a bit cryptic what all those UVec2 mean without looking at the docs or using some editor support to give you the parameter names?
        UVec2::new(2, 2),
        UVec2::new(64, 64),
        Vec2::new(17.0, 15.0),
        Vec2::new(102.0, 15.0),


Some refactoring

It become to hard to do everything in one file, so I decided to split stuff into multiple files for now.
Maybe we will come back to one file after all major features will be implemented.

Wow, that's great.
We can always make one file to ship as a post-processing step, no need to hassle.


Remove Money gem as dependency into gemspec

Since Shopify is releasing the shopify-money gem to public, this won't
be included by default, but still required.

One simple way to raise if money is missing would be to add require 'money' here https://github.com/activemerchant/offsite_payments/blob/master/lib/offsite_payments.rb#L6


Include helpers._alignPixel only once

You'll need to move the _alignPixel out of core.helpers to make it work.

Hmm. Why is that?

Because core.helpers.js is not included in require('../helpers/index'), but is merged later.

Ah, thanks for the pointer! I've updated this PR


MotW character sheet French translation

Changes / Comments
Translation of the Chosen, the Spellslinger and the Wronged.
Bugfix of two issues:

Playbook dropsown translation was not functionnal
Spellslinger "tools ans technics" chapter translation mechanism was missing.

Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

It is my first contribution to the community and the first time I use github.
I am open to any comment.

Hi @Johneve thanks for the translation in the future it might be easier to get the translation submitted in Crowdin


describe content flow and dependencies

As discussed on Slack with @cpuguy83 . Hopefully this helps future people have an easier time understanding the flow (and not having to ask all of the basic questions on Slack).
I am sure some of this is incorrect; if we can get it fixed here, that would be great.

Fixed all of your comments, @AkihiroSuda . To be honest, I was kind of amazed that was all that was wrong with it! :-)
Back at you.

Updated per suggestions; please take another look.

Codecov Report

Merging #4207 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4207   +/-   ##
=======================================
  Coverage   38.34%   38.34%
=======================================
  Files          90       90
  Lines       12728    12728
=======================================
  Hits         4881     4881
  Misses       7181     7181
  Partials      666      666

Flag
Coverage Δ

#windows
38.34% <ø> (ø)

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 e094d36...825dfed. Read the comment docs.

CI doesn't like your DCO sign-off.

CI doesn't like your DCO sign-off.

That is just strange. I looked at the commit log, and it has the "Signed-off-by:" line. I have contributions all over the place that require it. How odd.
Hmm, it looks like it is not complaining about the signoff itself, but the whitespace?
+ DCO_RANGE=e094d363ac2328305805c8d72b64ae2542617dd3..9fd12dde6d6727957b7787695063e0cbe7adfa83
26
+ ../project/script/validate/dco
27
/home/runner/work/containerd/containerd/bin/git-validation
28
 9fd12dd - FAIL - has whitespace errors. See `git show --check 9fd12dde6d6727957b7787695063e0cbe7adfa83`.
29

OK, fixed that whitespace and force-pushed.

DCO is happy now @cpuguy83

Still LGTM 👍

Great! Can we get it in?

🎉 Great work!

Thanks @deitch!

Thanks @deitch ! That is great for contributors


Bugfix/click outside of modal

Click Outside Of Modal -> Asks user whether to confirm cancelling the project
https://user-images.githubusercontent.com/58348527/184081026-d92c7f40-5cf8-4be6-9533-c033987f448c.mp4

Why is this change needed?
If a user accidently clicks out of the modal, presses cancel, clicks the X or hits 'ESC' they instantly lose all progress in creating their new project. (Issue#101)
This update adds a confirmation modal that asks the user whether the user really meant to cancel the new project.

What did you change?
Added a new component CancelProjectModal which pops up when the main ModalContainer is attempted to be closed.
The projectName is cleared when the project is cancelled.

OS

[ ] Linux
[ ] MacOS
[x] Windows

Is it okay if I make a UI design for this?

Is it okay if I make a UI design for this?

Sure that sounds all good to me!
What does this entail out of curiosity? Is this just updating Figma or coming up with a better design?

Is it okay if I make a UI design for this?

Sure that sounds all good to me! What does this entail out of curiosity? Is this just updating Figma or coming up with a better design?

Yeah I just wanted to play around with what it looks like and Figma is the easiest way for me to do that. Happy to work on it and send you what I end up with or pair with you if you're interested in trying your hand at design 😄

Can you make it so that if the user is on the new project modal and there is no text in the project name box it just exits without showing the confirm modal?

Can you make it so that if the user is on the new project modal and there is no text in the project name box it just exits without showing the confirm modal?

Yup can do that!

Can you make it so that if the user is on the new project modal and there is no text in the project name box it just exits without showing the confirm modal?

@emmapainter done!


Search for opts file in the test directory

I know the --opts flags provides a solution for this, but since Mocha's defaults opts file is at ./test/mocha.opts, loading ./test/mocha-webpack.opts by default would keep parity with Mocha.
For backwards-compatibility, mocha-webpack could try to load at the current default location if it doesn't exist at ./test/mocha-webpack.opts, or you could just break BC as part of the v2 major upgrade.

Personally I don't care about this file cause it's just awful and I would prefer real config files instead of this.
CWD as default location is because all other tools uses this, too. mocha is the only one that diverges from the norm. The default location of webpack config is also cwd, so it makes sense to keep the mocha-webpack.opts file also there. Otherwise the webpack config should be moved, too.
Anyway I would prefer a solution like cosmiconfig and remove the opts file. This would also solve #62 cause it would be possible to write the config in js and extend it manually.

I actually appreciate that the config for mocha-webpack is as close as possible to the config for Mocha. In the few projects I have used mocha-webpack on, mocha-webpack.opts was very similar to mocha.opts, so anything that helps keeping them in sync is good.

Ok, makes sense for me as long as we use the opts file.
I think we should go with your suggested solution:

mocha-webpack could try to load at the current default location if it doesn't exist at ./test/mocha-webpack.opts


Babel 7 setup 'was loaded with "6.26.3"'

🐛 Bug Report
The setup suggested in the documentation doesn't seem to work and triggers the following error message:
$ jest
 FAIL  ./hi.test.js
  ● Test suite failed to run

    Requires Babel "^7.0.0-0", but was loaded with "6.26.3". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel. (While processing preset<EMAIL_ADDRESS>
      at throwVersionError (node_modules/@babel/helper-plugin-utils/lib/index.js:65:11)
          at Array.map (<anonymous>)

(inline): Requires Babel "^7.0.0-0", but was loaded with "6.26.3". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel. (While processing preset<EMAIL_ADDRESS>To Reproduce
The package.json used is the following:
{
  "name": "minimal-jest-babel-7",
  "version": "1.0.0",
  "license": "MIT",
  "scripts": {
    "start": "babel-node consumer.js",
    "test": "jest"
  },
  "babel": {
    "presets": [
      "@babel/preset-env"
    ]
  },
  "devDependencies": {
    "@babel/core": "^7.0.0-beta.52",
    "@babel/node": "^7.0.0-beta.52",
    "@babel/preset-env": "^7.0.0-beta.52",
    "babel-core": "^7.0.0-0",
    "jest": "^23.3.0"
  }
}

Expected behavior
Running jest should be able to run the test, which includes an import statement. The babel-node command of the minimal repo executes the import successfully.
Link to repl or repo (highly encouraged)
Here is a minimal repo: https://github.com/verekia/minimal-jest-babel-7
Run npx envinfo --preset jest
Paste the results here:
  System:
    OS: macOS High Sierra 10.13.5
    CPU: x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
  Binaries:
    Node: 10.1.0 - /usr/local/bin/node
    Yarn: 1.7.0 - ~/.yarn/bin/yarn
    npm: 5.6.0 - /usr/local/bin/npm
  npmPackages:
    jest: ^23.3.0 => 23.3.0

The docs says to install both jest and babel-jest (https://jestjs.io/docs/en/getting-started#using-babel). Doing that makes your reproduction pass.

Thanks. Maybe remove the sentence Note: babel-jest is automatically installed when installing Jest and will automatically transform files if a babel configuration exists in your project. ?

Actually it seems to work with an even simpler configuration:
  "babel": {
    "presets": [
      "@babel/preset-env"
    ]
  },
  "devDependencies": {
    "@babel/core": "^7.0.0-beta.52",
    "@babel/node": "^7.0.0-beta.52",
    "@babel/preset-env": "^7.0.0-beta.52",
    "jest": "^23.3.0"
  }

I updated the repo: https://github.com/verekia/minimal-jest-babel-7/blob/master/package.json

That's because of the hoisting algorithm of yarn - I wouldn't depend on it. Up to you, though! 🙂

Okay. Thank you for your insight!

My case with this error was a little different - I was getting this error because I didn't have<EMAIL_ADDRESS>installed. The "Inspect the stack trace ..." message wasn't helpful because the whole stack was babel plugins and started with babel-core.
Anyway, not sure if it's something that would be helpful to add to the error warning - but hopefully this will at least be helpful to someone coming here with the same issue.

We ran into the same problem. In our case, locally running tests ran fine, on the builder server we'd get the error. I tried many solutions outlined here and elsewhere but nothing worked. Eventually  we found switching to npm solved it. But it was really bugging me because the whole point of yarn is that it's deterministic! On reflection I think yarn's hoisting behaviour is the cause, as @SimenB pointed out. This is just a hunch, but since babel changed their package names between 6 and 7, package managers don't know babel-core is the same as @babel/core, so treat them separately. In our yarn file I noticed it had hoisted both versions of babel to the top, even though in our package file we only specify @babel/core. So my hunch is that yarn did behave deterministically and downloads the same stuff for everyone, but when we ran the jest command on our two environments, something in that command loaded one before the other. Npm doesn't hoist, so doesn't exhibit this problem.

This is pretty annoying none of the solutions work like yarn add --dev babel-jest<EMAIL_ADDRESS>@babel/core regenerator-runtime. Should I not be using the new plugins like @babel/plugin-proposal-class-properties? I have babel-jest and babel-core (v7 bridge) installed still nothing :/

None of the solutions online worked, I fixed it the following way:

Remove jest and @babel/core from package.json (keep babel-core v7 bridge)
Remove node_modules and package-lock.json
npm install
npm install jest @babel-core --save-dev

I fix this problem with them.
npm install --save-dev babel-jest<EMAIL_ADDRESS>@babel/core regenerator-runtime

// jest.config.js
'use strict';

module.exports = {
    transform: {
        '^.+\\.jsx$': 'babel-jest',
        '^.+\\.js$': 'babel-jest'
    }
};

This took me an entire day to figure out. I tried, it feels like maybe thousands of logical solutions. I used git bisect to figure out the exact commit where the issue occured. I removed the package we had added. I then finally isolated that the package-lock.json was causing the issue because when I added all files from the bad commit one by one everything worked fine, but if I swapped the package-lock.json files it broke again. However, when I tried to go back to master and just delete the package-lock.json and the node modules it did not work. I also tried DominicTobias solution and it did not work. Finally the following order of operations worked:

delete your node_modules and package-lock.json (maybe this isn't necessary but just start with a clean slate just in case because this is what I did
like ruslankhh said, run the following :  npm i -D jest babel-jest<EMAIL_ADDRESS>@babel/core regenerator-runtime
Now delete your node_modules and your package-lock.json again
Now run npm install

¯_(ツ)_/¯

I've noticed that it's important to write babel.config.js, not .babelrc :)

@ruslankhh same here

@ruslankhh and @kmwarter, thanks a lot guys, this worked for me as well!

@kmwarter that did the trick for me. thank you.

Hello, I'm just starting with Jest and I have a question related to this.
This is how my package.json looks like:
"devDependencies": {
  "@babel/cli": "^7.1.5",
  "@babel/core": "^7.1.6",
  "@babel/plugin-proposal-object-rest-spread": "^7.0.0",
  "@babel/preset-env": "^7.1.6",
  "@babel/preset-react": "^7.0.0",
  "autoprefixer": "^9.3.1",
  "babel-eslint": "^10.0.1",
  "babel-loader": "^8.0.4",
  "browser-sync-webpack-plugin": "^2.2.2",
  "clean-webpack-plugin": "^0.1.19",
  "css-loader": "^1.0.1",
  "eslint": "^5.9.0",
  "eslint-plugin-react": "^7.11.1",
  "html-webpack-plugin": "^3.2.0",
  "mini-css-extract-plugin": "^0.4.5",
  "node-sass": "^4.10.0",
  "postcss-loader": "^3.0.0",
  "sass-loader": "^7.1.0",
  "style-loader": "^0.23.1",
  "webpack": "^4.26.1",
  "webpack-clean-obsolete-chunks": "^0.4.0",
  "webpack-cli": "^3.1.2",
  "webpack-manifest-plugin": "^2.0.4"
}

If babel core is pointing to 7.1.6 and babel 7 is require, why in the package-lock,json, jest-config has the following dependencies:
"jest-config": {
  "version": "23.6.0",
  "resolved": "https://registry.npmjs.org/jest-config/-/jest-config-23.6.0.tgz",
  "integrity": "sha512-i8V7z9BeDXab1+VNo78WM0AtWpBRXJLnkT+lyT+Slx/cbP5sZJ0+NDuLcmBE5hXAoK0aUp7vI+MOxR+R4d8SRQ==",
  "dev": true,
  "requires": {
    "babel-core": "6.26.3",
    "babel-jest": "23.6.0",
    "chalk": "2.4.1",
    "glob": "7.1.2",
    "jest-environment-jsdom": "23.4.0",
    "jest-environment-node": "23.4.0",
    "jest-get-type": "22.4.3",
    "jest-jasmine2": "23.6.0",
    "jest-regex-util": "23.3.0",
    "jest-resolve": "23.6.0",
    "jest-util": "23.4.0",
    "jest-validate": "23.6.0",
    "micromatch": "2.3.11",
    "pretty-format": "23.6.0"
  },
  "dependencies": {
    "ansi-styles": {
      "version": "3.2.1",
      "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-3.2.1.tgz",
      "integrity": "sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==",
      "dev": true,
      "requires": {
        "color-convert": "1.9.1"
      }
    },
    "chalk": {
      "version": "2.4.1",
      "resolved": "https://registry.npmjs.org/chalk/-/chalk-2.4.1.tgz",
      "integrity": "sha512-ObN6h1v2fTJSmUXoS3nMQ92LbDK9be4TV+6G+omQlGJFdcUX5heKi1LZ1YnRMIgwTLEj3E24bT6tYni50rlCfQ==",
      "dev": true,
      "requires": {
        "ansi-styles": "3.2.1",
        "escape-string-regexp": "1.0.5",
        "supports-color": "5.5.0"
      }
    },
    "supports-color": {
      "version": "5.5.0",
      "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-5.5.0.tgz",
      "integrity": "sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==",
      "dev": true,
      "requires": {
        "has-flag": "3.0.0"
      }
    }
  }
}

That could basically be the cause of babel 6.26.3 being installed instead of ^7

@rhernandog use this approach: https://github.com/facebook/jest/issues/6662#issuecomment-429620436
basically - you need to add babel-bridge(but still keep that logic of install and clean up) to your project and i think it'll work for you. Just today have in issue with jest too - after following that logic - my jest script start to work

@atherdon Yeah, that solved, no problem there.
I just posted to share my guess of where this problem could be generating. In the whole package-lock.json file that is the only reference to babel 6.26.3, so that's perhaps what's causing this.

Setting my jest.config.js fixed this error for me:
// jest.config.js
module.exports = {
  transform: {},
}

As per Jest Getted Started, if you're using a babel config, jest will use that (and any transforms).  You may need to override it for jest 24 to work with babel 7 (as was required in my case).


Unless I misunderstood, and the reason this repo is called "event" singular rather than "events" plural is because there will only be one event, in which case I screwed it up by creating this issue, which is technically an event.

Can you tell a bit more maybe what this repo is about? :P

I assume it's some kind of electronic wind producing utility.

Oooooh nice! I could use one of those!
Thanks!

I propose that the project is renamed to e-vent to make it clearer that the lack of events is acceptable as the business model does not require them.


Add password as an inputStyle to avoid whacky mobile keyboard hijinks

Greetings!
TL;DR It looks like using a password input as a backing field rather than a textarea or contenteditable solves some mobile issues.
I have a project with a live playground, wherein users can compose code jsFiddle-style and share in chats and issues to demonstrate bugs, get help with concepts, etc. This works fine on desktop, but I'm usually on my phone when I get a chance to look at them. As far as editors on mobile go, CodeMirror is one of the best behaved, but there are still weird issues that crop up when GBoard (and probably others) decides that it wants to help you complete a word or autocorrect that forEach for you.
After poking around at how to stop Chrome on Android from trying to do anything related to autocorrect or suggestions, I found that CodeMirror already does its best to make the bad things stop in textarea mode, but Chrome is pretty insistent on mucking about with things you type. The only field that I could think of that doesn't get abused by GBoard in Chrome is the password input, so I gave it a go. It seems to work nicely.
Implementation
This just adds a new inputStyle, password, that when set, calls a new input PasswordInput, which is just a subclass of TextareaInput that has an override to get the backing node. I don't know if that was the best way to accomplish this, but it seemed better to have an override-able method on the class than to duplicate a whole bunch of code. It might make sense to use the TextareaInput for both cases, but just have it check the options during init, since it seems inputStyle can't be changed after init.
The default for mobile remains contenteditable.
Potential issues?
There may be a few side-effects to using a password input:

Chrome is pretty insistent on trying to save passwords when you submit a form. There are a few ways around that, mostly by throwing out some empty decoy password fields, but I'll cross that bridge if this looks like it's a useful PR.
All of the input I tried worked well. You can't use the slide-on-the-spacebar-to-move-the-cursor trick, but that also tends to delete characters at random in contenteditable mode anyway, so I'll call that a draw. There may be some corner cases that I didn't stumble across.
You get no blue teardrop cursor moving handle thing. The contenteditable mode does, but it doesn't seem to get the more useful double teardrop selection editor. It seems that select all still works, and honestly, I'm ok with poking at the place I need to drop the cursor a time or three if my input isn't randomly futzed.
On GBoard, you get no emoji button for password fields, so you can no longer have happy, crying, or pile-of-poo comments/variables.
More things that I haven't thought of? This is my first foray into editing code editor code. I also have no idea how to go about writing tests for actual functionality here.

Bonus effects:

The suggestions bar on the top of the keyboard doesn't pop up to soak up another ~30px of precious tiny screen.

Related issues
It looks like this would resolve a handful of the open issues about whackiness with autocomplete and suggestions when using mobile keyboards. One issue that I specifically checked was autocomplete plugin triggering, and I verified that < still doesn't trigger the popup for the xmlcomplete demo.
It's finally over
Thanks for reading my wall of text! If this looks like a useful PR, I'm more than happy to adjust it in whatever ways are required.

Quick followup:

Interestingly, mobile Firefox for Android works nicely in the xmlautocomplete demo with this.

I have no experience with the less Latin charsets, but Belarusian seems to work nicely.

Password fields don't appear to allow newlines, which I'm afraid would make this a bit of a non-starter—the TextareaInput assumes it can store multi-line strings in its input.
Also, having selection control is the main reason we're using contentEditable on mobile. Without that, the editing experience tends to be rather miserable.
So I don't think we're interested in having this in the main distribution. If you want to make small changes to TextareaInput to make it easier to define this in 3rd-party code, I'd be open to that.

Thanks for looking at this.
It would be nice to be able to author an add-on targeting the official distribution. Would you be open to a blessed extension name, that if present, would allow external creation of the backing input? Something like let div = this.wrapper = (cm.createHiddenInput || hiddenTextarea)()?

It should be possible to assign to CodeMirror.inputStyles.password to define a new input style. You can read CodeMirror.inputStyle.textarea to get the TextareaInput class that you want to derive from.

Oh wow, I completely missed that that is exposed statically. In that case, would the internal method on the TextareaInput to generate the wrapper be acceptable?

Sure, either update this PR or submit a new one, and I'll merge that


include types when publishing module

This should allow the type definition file (#13) to be published with the package.

I'll look into publishing :)

Success! Thank you!


Added --service-account-subject

You can use this option when connecting using --service-account. Filling
the Google account username into --service-account-subject you will be
connected as this Google account instead of the service account.
Required settings on the Google site:

Service account must be domain-wide delegated (Google APIs > IAM & Admin

Service accounts > Edit service account > check "Enable GSuite
Domain-wide Delegation". Also new OAuth 2.0 client will be created.

There must be allowed SDK API in the GDrive settings (Admin Console >
Apps > GSuite > Drive and Docs > Data access > check "Allow Drive SDK
API"
The newly created OAuth 2.0 client must be allowed in the GSuite security
settings to use GDrive API (Admin Console > Security > Show more >
Advanced settings > click Manage API client access > fill the form:

Client ID is the client id found in Google APIs > APIs & Services >
Credentials
One or more API Scopes is "https://www.googleapis.com/auth/drive"

Hi,
I have added the possibility to impersonate (connect as another user) when connecting using service account.
The key change is setting the Subject property of the jwt.Config type.

Just a little addendum to the Guide given:
If you followed all steps and you still can not impersonate due to missing permissions, creating a new google project and follow the steps again did the trick.
My project was quite old so I guess there was a migration or corruption issue within the google project.
Needless to say: Ty for the PR, saved my life


Add/remove worker nodes to/from deployed cluster

Hi @ccamacho,
Adding new worker nodes to deployed cluster is not easy now. It's actually deploy whole new cluster instead of adding new nodes.
It's better to support adding/removing worker nodes to/from deployed cluster.

@lapd-viosoft thanks a lot for the feedback, I moved all these issues as cards in a kanban project https://github.com/Kubeinit/kubeinit/projects/1 if you will like to contribute, please feel free to push any PR you will like to have included in the code. When I have some free time I'll try to implement some of them.


Turn this into an open project

Like I mentioned on Google+ : using closed platforms (private group, slack) was probably a bad idea for this.
I would like to turn this into an open learning project.
Any takers to help me out?

What kind of tasks will be necessary?


[WIP][SPARK-31365][SQL] Enable nested predicate pushdown per data sources

What changes were proposed in this pull request?

This patch proposes to replace NESTED_PREDICATE_PUSHDOWN_ENABLED with NESTED_PREDICATE_PUSHDOWN_V1_SOURCE_LIST which can configure which v1 data sources are enabled with nested predicate pushdown.
Why are the changes needed?

We added nested predicate pushdown feature that is configured by NESTED_PREDICATE_PUSHDOWN_ENABLED. However, this config is all or nothing config, and applies on all data sources.
In order to not introduce API breaking change after enabling nested predicate pushdown, we'd like to set nested predicate pushdown per data sources. Please also refer to the comments https://github.com/apache/spark/pull/27728#discussion_r410829720.
Does this PR introduce any user-facing change?

No
How was this patch tested?

WIP

Test build #121891 has started for PR 28366 at commit 6feaaa4.

Merged build finished. Test PASSed.

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

Test build #121891 has finished for PR 28366 at commit 6feaaa4.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class AbortableRpcFuture[T: ClassTag](val future: Future[T], onAbort: Throwable => Unit)
class AvroDeserializer(rootAvroType: Schema, rootCatalystType: DataType, rebaseDateTime: Boolean)
class AvroSerializer(
class ExecutorResourceRequest(object):
class ExecutorResourceRequests(object):
class ResourceProfile(object):
class ResourceProfileBuilder(object):
class TaskResourceRequest(object):
class TaskResourceRequests(object):
abstract class CurrentTimestampLike() extends LeafExpression with CodegenFallback
case class CurrentTimestamp() extends CurrentTimestampLike
case class Now() extends CurrentTimestampLike
case class YearOfWeek(child: Expression) extends UnaryExpression with ImplicitCastInputTypes
case class DateAddInterval(
class CacheManager extends Logging with AdaptiveSparkPlanHelper
case class AdaptiveExecutionContext(session: SparkSession, qe: QueryExecution)
class ParquetReadSupport(

Merged build finished. Test PASSed.

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

Test build #121981 has started for PR 28366 at commit e555a1c.

Merged build finished. Test PASSed.

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

Test build #121981 has finished for PR 28366 at commit e555a1c.

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

Merged build finished. Test PASSed.

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

Test build #122051 has started for PR 28366 at commit 84bc8dd.

Merged build finished. Test PASSed.

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

Test build #122051 has finished for PR 28366 at commit 84bc8dd.

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

Merged build finished. Test PASSed.

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

cc @cloud-fan @dbtsai @dongjoon-hyun @HyukjinKwon @gatorsmile @maropu

Test build #122162 has started for PR 28366 at commit a49b73c.

Merged build finished. Test PASSed.

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

Test build #122162 has finished for PR 28366 at commit a49b73c.

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

Merged build finished. Test PASSed.

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

Test build #122175 has started for PR 28366 at commit 17d1094.

Merged build finished. Test PASSed.

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

Test build #122175 has finished for PR 28366 at commit 17d1094.

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

Merged build finished. Test PASSed.

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

LGTM. Thanks.

Test build #122304 has started for PR 28366 at commit aa32dcc.

Merged build finished. Test PASSed.

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

Test build #122305 has started for PR 28366 at commit 00b9d47.

Merged build finished. Test PASSed.

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

Test build #122305 has finished for PR 28366 at commit 00b9d47.

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

Test build #122304 has finished for PR 28366 at commit aa32dcc.

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

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

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

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

retest this please

Test build #122310 has started for PR 28366 at commit 00b9d47.

Merged build finished. Test PASSed.

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

Test build #122310 has finished for PR 28366 at commit 00b9d47.

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

Merged build finished. Test PASSed.

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

thanks, merging to master/3.0!


Add hook for custom SSPI context for SqlConnection instances

Background
There have been a couple of active issues around NTLM/kerberos authentication and customizing it for various reasons (see discussions in #305 and #31), with an attempt of enabling this in #1379. This issue is to track an API proposal and the steps needed to integrate it into SqlClient.

NOTE:
I'm not sure of naming in this area and very open to better names for things. I haven't spent much time within the SSPI/GSS/NTLM/Kerberos/etc space and this proposal is based on my limited understanding of these concepts. If I'm missing anything important, please let me know

Proposal
The proposal is to add a provider that has the ability to generate a context given an incoming blob. There are currently a few ways that this is handled internally:

A native implementation on all Windows platforms
An internal managed implementation on .NET Standard/.NET 6
System.Net.Security.NegotiateAuthentication on .NET 7+

As part of this change, those different implementations should be moved to follow the same pattern as an external implementer would have to ensure the abstraction is sufficient. After attempting to do so, it appears the best design would be to have a class that is used per connection (retrieved via a factory method) as there is some state that may need to be accessed between invocations:
+ /// <summary>
+ /// Defines a provider to supply and operate on an SSPI context as part of integrated authentication.
+ /// </summary>
+ public abstract class SspiClientContextProvider
+ {
+     /// <summary>
+     /// Gets the server names associated with the current connection.
+     /// </summary>
+     protected IReadOnlyList<string> ServerNames { get; }

+     /// <summary>
+     /// Generates a context given a (possibly empty) previously buffer.
+     /// </summary>
+     /// <param name="incomingBlob">The incoming blob (may be empty).</param>
+     /// <returns>A memory owner of the data to be sent next.</returns>
+     protected abstract IMemoryOwner<byte> GenerateContext(ReadOnlySpan<byte> incomingBlob);
+ }

public class SqlConnection
{
+   /// <summary>
+   /// Gets or sets a factory to handle the SSPI context
+   /// </summary>
+   public Func<SspiClientContextProvider> SspiContextProviderFactory { get; set; }
}

Alternate designs

The IMemoryOwner<byte> is nice as a provider could use pooled memory that will have a guanteed lifetime. Alternately, we could do the following if that is not needed:
public abstract class SspiClientContextProvider
{
-     protected abstract IMemoryOwner<byte> GenerateContext(ReadOnlySpan<byte> incomingBlob);
+     protected abstract byte[] GenerateContext(ReadOnlySpan<byte> incomingBlob);
}

Or we could pass in a buffer writer:
public abstract class SspiClientContextProvider
{
-     protected abstract IMemoryOwner<byte> GenerateContext(ReadOnlySpan<byte> incomingBlob);
+     protected abstract void GenerateContext(ReadOnlySpan<byte> incomingBlob, IBufferWriter<byte> writer);
}

Implementation/Testing
While prototyping this, I found that as-is, it would be a fairly large change. However, I think it should be broken into three steps to make sure we don't regress anything.

Extract SSPI context generation to shared type to isolate required inputs and lifecycle (see POC)
Convert SSPI context generation to operate on ReadOnlyMemory/Span types instead of byte[] and offsets
Expose SspiClientContextProvider (see similar change using a callback rather than a provider)

The first two are mostly refactorings that I'm assuming can use current testing to ensure no regressions (please correct me if that is incorrect). For the final one, the main thing to test will be that a custom implementation is picked up and handled correctly, which can be done with unit tests. I also plan on testing the E2E of this API by enabling NTLM with this enabled hook.

Currently the closest analogy to SspiClientContextProvider in the current code base is NegotiateAuthentication, inside of TdsParserStateObjectManaged.cs:25.
Given that SspiClientContextProvider is expect to be stateful, I would imagine you would want to make it implement IDisposable.
Additionally, should it not be the responsibility of SspiClientContextProvider to report the state of the SSPI connection (e.g. Error or Complete).

Thanks @arontsang for the feedback.

Given that SspiClientContextProvider is expect to be stateful, I would imagine you would want to make it implement IDisposable.

None of the current implementations seem to need it. However, we can always check if it implements IDisposable to then dispose of it.

Additionally, should it not be the responsibility of SspiClientContextProvider to report the state of the SSPI connection (e.g. Error or Complete).

That's reasonable, but I don't see a place in the code base where that is currently surfaced. Can you point me to that?
btw feel free to assign it to me - I'm working on it in #2255

@roji For his thoughts.

Thanks @David-Engel.
I'm curious - what would be the point of having a full-blown, public abstraction here, as opposed to just implementing the various needed strategies inside SqlClient? Is the intent actually for users to provide their own custom implementations here, and if so, why and in what scenarios would they want to do that? For example, I agree that there's a bit of variance here across .NET TFMs, but e.g. on .NET 7+ shouldn't NegotiateAuthentication simply be used always?
As a data point, Npgsql (the PostgreSQL driver) has similar authentication requirements, and the need for a public abstraction has never been raised by anyone.
On a related note, I'm no expert in the area but why is it important to support Windows native implementations here, given that we're in a cross-platform context and sufficient cross-platform authentication APIs seem to be available?

@roji The main use case is to open up the possibility of authentication across untrusted domains, non-domain, and/or cross platform scenarios where it's difficult or impossible to configure authentication "correctly" on the client. Specifically, NTLM username/password authentication is never going to happen in SqlClient itself as I am not going to try to justify the feature to the security team. Similarly, there have been asks for more control over the Kerberos ticket/negotiation in the same types of environments.
The only reason for the native implementation mention is that's how it's currently done in SqlClient on Windows.

OK, thanks for the details @David-Engel. I don't really have much to add - I'd be somewhat wary of introducing such a public abstraction, where making something that fits the requirements across the various implementations may be tricky (though I really don't know much about this area). Of course it's always ideal to just expose the right config switches/APIs (e.g. around Kerberos), but if this makes sense for externalizing NTLM, then sure, I guess...

@David-Engel described the exact situation I've been seeing customers in, mostly as a stop-gap during on-prem to Azure migrations.

making something that fits the requirements across the various implementations

I totally agree with the sentiment. That's why I'm including a refactoring as part of this change to move all the current context generation into this abstraction so it at least works for everything internally :) I'm having a customer try out the completed POC in their environment to make sure it works for custom code outside of the sqlclient library.

It seems like part of this has been merged already. Would anyone be able to provide an ETA on this?

Would love to see a sample for this too. Right now this is my work-around: https://github.com/dotnet/SqlClient/issues/31#issuecomment-1156702009

Would love to see a sample for this too. Right now this is my work-around: #31 (comment)

He has some samples here which I tested in our environment early on with success.
https://github.com/twsouthwick/swick.sqlclient.sspi
My use case is I need to do a manual kerberos negotiation inside of containers and don't want to deploy side-cars etc to support the ticket refresh etc that is typically required https://github.com/dotnet/SqlClient/issues/305#issuecomment-2105161074

@twsouthwick the sample you provided works like a charm for us for our NTLM needs. Is there a timeline of when we can expect the related PRs to be merged so we can start using these extension points officially?


CC 4.0 plain text license texts: Third level numbering is lower case but referenced upper case

Description
The plain text versions of the 4.0 license text number the third level with lower case letters (a, b, ...), e.g. Section 2(1) or Section 2(5), but reference them with upper case letters (A, B, ...), .e.g. in Section 2(a)(6) or Section 3(a)(3).
This is obviously inconsistent and a deviation from the HTML version which uses upper case letters in the third level.
Expectation
Consistent referencing.
Resolution

[x] I would be interested in resolving this bug.

I would be willing to capitalise those ~30 letters if I get a go ahead.

I'm sorry, I mixed up my tabs and accidentally filed this against the wrong repository.


Attempted import error when deploying to vercel

What happened?
Attempted import error: '/vercel/path0/markdoc/tags/index.ts' does not contain a default export (imported as 'tags'). Also unable to deploy to vercel
To reproduce
Clone this repository and npm run build/yarn build
Version
0.1.2
Additional context
No response

Yes I used that repo.
I'm using MacOS Monterey 12.0.1 (21A559). I don't think the issue is in my machine cause vercel build process also showed that message. Thank you

@febriliankr I see that message locally, but it is just a warning, and should be benign. I am able to deploy the repo despite the warning message: https://markdoc-starter-stripe-oss-stripe-dev.vercel.app.
Can you try redeploying with npx vercel --force?

Closing w/ above fix. Please open a new issue with steps to reproduce if something comes up.


Cannot create new window in a thread

Trying to create a window with MahApps resource dictionaries results in
System.Windows.Markup.XamlParseException: {"'Initialization of 'MahApps.Metro.Controls.NumericUpDown' threw an exception.' Line number '31' and line position '198'."}

InnerException: {"The calling thread cannot access this object because a different thread owns it."}

Code:
Thread foo = new Thread(delegate()
{
    var window = new SettingsWindow();
    window.Show();

    System.Windows.Threading.Dispatcher.Run();
});

foo.IsBackground = true;
foo.SetApartmentState(ApartmentState.STA);
foo.Start();

Creating a new window without the resource dictionaries works fine.

That's not an MahApps.Metro issue but WPF in general. See Threading model in WPF and application resources. The solution given in mentioned article: use window resources instead of application resources.


The Active Now list is not dark

The theme doesn't work on the Active Now list, here's the screen:

Before Discord get the updates everything is dark and the theme work perfectly.

Fixed.


Migrate matplotlib/seaborn plots to Altair

Using Altair, Optimus can output the charts in Vega's JSON format. This gives the users amazing flexibility working with the charts
This charts will be ported:

histogram
frequency
boxplot
scatterplot

Also binned scatter plot will be added.

Hi @argenisleon nice to meet you! Optimus is a really great project thanks for all the things you and @FavioVazquez have put together. Altair looks pretty awesome i've been reviewing it and there are some viz available at other packages as plotly that are currently missing, what about allowing the user to choose the visualization backend ? Because maybe at some point we would like to use plot.ly as well for some specific visualizations as sankey diagrams that aren't on altair, also we would be able to keep up with cutting edge visualizations on main viz projects, what do you think ?
We would have a default one and then for some plots the user couls choose the backend as a parameter of the plotting function

Hi @wilmeragsgh ,
The main reason to select Altair was how it plays with vega-lite(JSON and Bumblebee https://github.com/ironmussa/bumblebee) and how easy is to use in python compare with matplotlib for example.
We try to create a tiny API so you can use Optimus with any plotting library. For example, you can use
df.cols.scatter(), df.cols.frequency(), df.cols.boxplot() or df.cols.hist() to output a JSON that you can process to adapt the data to any plotting library.
Right now I am not really sure if JSON is the best output format. Maybe we can pass a param to select the output as JSON or pandas? A panda data frame could be a better input for almost all python plotting libraries?
What do you think? A tiny API could help with this?

Oh i get it, that's better than i thought then. I think JSON would be easier to identify api output as auxiliar files for visualizations, but pandas persistence could be done in many ways with the pandas.DataFrame.to_* functions and therefore be more flexible to the user's environment. So i'd say pandas to do handle visualization metadata internally and exporting with the formats of pandas.DataFrame.to_* directly, what do you think ?

How about the support of HoloViews? It is a great visualization library for Python.

Hi @dclong ,
We like Altair because is json friendly and have the charts that Optimus needs.
Is there a specific reason why do you consider HoloViews?


FR: Firebase AppCheck Token Validation on Server Side Swift Backends

As server-side swift backends evolve (e.g. Vapor), there is a real need to secure them from abuse.
The missing link is way to use AppCheck to "Verify App Check tokens from a custom backend".
While there is no SDK available for Firebase Admin using Swift, maybe the functionality can be extended first to Firebase REST API?
Any workaround ideas? Calling a Lambda function or a python script sounds very inefficient.

@lahirumaramba @weixifan

@andreivladmatei As a temporary workaround you can implement the App Check token verification on your end. This blog post describes how to do it.

Thanks, I'll give it a try.
Any plans to get this supported officially?

@andreivladmatei Thank you for reporting this! We understand that there is an interest to use Firebase Admin APIs with server-side Swift. We have been discussing this topic with our teams lately, however this is not something we currently have plans to work in the near future. We will use this issue to track any progress in the future. Thanks again for your feedback. These are very valuable inputs for us to further improve our SDKs.
b/205177095

@andreivladmatei As a temporary workaround you can implement the App Check token verification on your end. This blog post describes how to do it.

Thanks @maksymmalyhin for this pointer. To expand on this and for clarification, the custom backend verification solutions outlined in the blog post are supported ways of using App Check. For any language or use case that our SDKs currently do not support, you can still follow the generic solution using App Check's Public API, as outlined in the blog post, to implement your own server-side App Check token verification.
@andreivladmatei We definitely understand that if SDKs for new languages such as Swift become available in the future, using those SDKs will be much more convenient than writing custom backend verification code that interact directly with App Check's Public API. Thank you for your feedback, and as @lahirumaramba mentioned above, we will be tracking this in our internal ticket as well.


feat(ui): update hero

Update the Hero of the OKP4 website

Sorry, next time I'll add only the modified files in my commit

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


Different Satisfactory server Timezone causes messages not being send

Hi,
I have been troubleshooting the issue of join and unjoin messages not being send.
I have found that differences in timezone causes issues with data.timestamp >= initTime   not being true. After adding RUN apk add --no-cache tzdata ENV TZ=Europe/Amsterdam to the dockerfile it started working for me.
I will try to find a way to set the timezone for your application without having to edit the dockerfile.

Hi @Luukxt8,
Thank you for raising this. It should not be necessary to set the timezone unless something has recently changed with respect to the timestamps in the Satisfactory Dedicated Server logs.
By default the Satisfactory Dedicated Server logs should contain UTC timestamps. The bot attempts to detect when an incompatible command line argument has been used for the Satisfactory Dedicated Server (e.g. -LocalLogTimes). There is some information about this in the README.
As such, the parseTimestamp function converts the log times using the Z zone designator (for UTC). Originally the bot did not do this, but this issue was fixed in #1.
It could be that the time/timezone is not correct on your Satisfactory Dedicated Server host, or in the container image - if that is how you are running the Satisfactory Dedicated Server.

Thanks for the quick reply.
I'm using wolveix/satisfactory-server (Docker), and running it in docker for windows desktop.
I will have a look at my satisfactory server config.

It would probably also be a good idea to inspect the FactoryGame.log file, as the dedicated server is running, to see if the latest timestamps match a UTC clock.

I have just checked the FactoryGame.log. It matches the UTC clock...
[2024.10.18-18.12.20:447][ 65]LogNet: Join succeeded: DrogeBezem
Wierd....I don't understand why it didn't work before my change.

I reverted my changes in the docker file. It's still working :)
Thanks for you help! I think it was a user error, tried to much changes at the same time to fix it i guess. Something else fixed it that I forgot about.

I wonder if it could be related to #35?
wolveix/satisfactory-server recently had an issue with logs which resulted in a similar issue where the bot would not send messages.
Perhaps you pulled the latest version, which is why it started working again?
Either way, I'm glad you got it working again. 👍


Hey!! Can we Push Some Stuff Related to Binary Tree.

I will help to find the Number of Unique Binary Tree from the Given Number of Node!! Its not BST it will find BT
Hope It Sound Interesting!!! 👍

sounds good :)
Please make PR

I can add how to delete a node from BST


make default WORKSPACE_MOUNT_PATH as abspath

Docker will throw errors if the default WORKSPACE_MOUNT_PATH is not abspath

Thanks for the fix!


Store configuration information in the same SPI flash that stores the gateware

It would be good to store configuration information in the SPI flash that stores the gateware.
Both the Opsis and Atlys have similar SPI flash available that is much bigger then required for the gateware.
On the Opsis, the SPI flash will also be storing two firmware for the FX2 as well. So we need some type of "file system" I guess?

Seems related to https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/111.
We first have to define memory map of the flash: bitstream / FX2 firmware1 / FX2 firmware2 and user data.
For user data, we can try to keep things simple (store raw data) or use a file system. If we choose to use a file system, IIRC something similar exists in ARTIQ.

I was suggesting we spit the flash into 2 parts, bit stream and "user".
Then put a simple file system on the user section which lets us store the
fx2 firmwares, user configs and maybe a logo or two?
On 15 Oct 2015 12:46 a.m., "enjoy-digital"<EMAIL_ADDRESS>wrote:

Seems related to #111
https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/111.
We first have to define memory map of the flash: bitstream / FX2 firmware1
/ FX2 firmware2 and user data.
For user data, we can try to keep things simple (store raw data) or use a
file system. If we choose to use a file system, IIRC something similar
exists in ARTIQ.
—
Reply to this email directly or view it on GitHub
https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/113#issuecomment-148054319
.

Is the overhead of a filesystem worth it? Could you have "partitions", with a simple header in the first page of the flash that describes the layout?

The first page has to be what ever Xilinx wants it to be for the FPGA.
The last page can be used for such a layout. That layout is pretty much a filesystem though :)
The simplest filesystem is just a concatenated list of;
filename (null terminated string)
filesize (32bit int)
pointer to filedata (pointer to byte array // offset)

Yeah. That sounds good to me.

@fallen - FYI


Add option to set number of haproxy threads per VM

This optional parameter allows to set the number of haproxy threads started for each VM. This option helps to improve the performance - especially on multicore VMs.

Great PR, but should we also include a cpu-map clause?  maybe something like
  <% if p("ha_proxy.threads") > 1 %>
     nbproc <%= p("ha_proxy.threads") %>
    <% for i in 1..threads do %>
     cpu-map <%= i %> <%= i-1 %>
     <% end %>
  <% end %>

Thoughts on pulling the cpu count out of /proc/cpuinfo, and auto-tuning accordingly?

@svrc-pivotal Thanks :) I tried that and measured no significant performance change. This may make more sense when used in combination with cpu pinning. When you want to pin a set amount of cpus to a certain frontend for example. In addition you need to think about what happens when you chose to have more threads than you have cpus (or less). Its definitely something that we should investigate going forward.
@geofffranks Actually one of my first tries was to put that kind of magic in the erb. However in our case the machine evaluating the erb has less cores as the one we deploy on (2 vCPUs vs 4). So at least my ad-hoc approach did not work out. Auto-tuning in general sounds nice though.

Ah, that would require an auto-reconfiguration in the ctl script (bosh would render the ERB into a config template, then the ctl script would re-render that into an actual config at startup).

On Jun 28, 2017, at 4:05 PM, Juergen Graf<EMAIL_ADDRESS>wrote:
@svrc-pivotal https://github.com/svrc-pivotal Thanks :) I tried that and measured no significant performance change. This may make more sense when used in combination with cpu pinning. When you want to pin a set amount of cpus to a certain frontend for example. In addition you need to think about what happens when you chose to have more threads than you have cpus (or less). Its definitely something that we should investigate going forward.
@geofffranks https://github.com/geofffranks Actually one of my first tries was to put that kind of magic in the erb. However in our case the machine evaluating the erb has less cores as the one we deploy on (2 vCPUs vs 4). So at least my ad-hoc approach did not work out. Auto-tuning in general sounds nice though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/cloudfoundry-incubator/haproxy-boshrelease/pull/61#issuecomment-311772535, or mute the thread https://github.com/notifications/unsubscribe-auth/AG2SUqTr-PjzTJjEkGLCbR6VoKJULgzpks5sIrH2gaJpZM4OID60.

So we discussed the auto-tune feature and the cpu-map suggestion.
We like the idea of having an option to use cpu-map, but we see it as a separate feature that should be enabled in combination with an option to bind threads to specific frontends - as described in http://blog.onefellow.com/post/82478335338/haproxy-mapping-process-to-cpu-core-for-maximum
Auto-tuning is a great idea, but we also need to be able to set the number of threads explicitly. For example when we only want to use 3 of 4 cores for haproxy, as we expect some load from a separate job. How about making auto-tuning optional?
For example set a specific amount of threads via
threads: 23
and enable auto-tuning with
threads: "auto"
The downside of auto-tuning is increased complexity with the template being rendered on each startup.
Whats your take on this?

What about something like this in bin/haproxy_ctl to keep complexity down? We'd probably want to handle the case where no haproxy.threads property was provided, or default to either 1, or auto in the spec file?
NUM_THREADS=<%= p("ha_proxy.threads") == "auto" ? "$(nproc --all)" : p("ha_proxy.threads") %>
THREAD_CONFIG=${JOB_DIR}/config/threads.conf
cat <EOF > ${THREAD_CONFIG}
global
  nbproc ${NUM_THREADS}
EOF

.......

"${DAEMON}" -f "${CONFIG}" -D -p "${PID_FILE}" -f ${THREAD_CONFIG} 0<&-

I find that more complex then just having a threads.conf.erb template that would handle nbproc and a future / separate cpu-map feature...

Thanks, I'll try to put something together till Tuesday.

While investigating different options for auto-tuning I stumbled across an issue regarding the stats page and socket. HAProxy keeps stats separated for each process, so in order to access the stats of all running processes we require a socket and/or a stats page per thread.
This makes things more complicated - especially when used together with auto-tuning. So I just added the changes to stats socket and pages that work for the non-auto-tuning case.
In case I want to go forward and move this functionality from the erb template to the ctl skript it can potentially become quite ugly. So should we still try to go forward with auto-tuning or do you have any suggestions regarding a simpler solution?

Seems like we should skip auto-tuning for now. I'll put in an issue with a proposal for it, and if enough people want it, I'll look into implementing it.
For now, can you update the spec file's description of the stats port to reflect the new numbering if using multiple threads?

@geofffranks Thanks, good find! I changed the documentation accordingly.

@geofffranks Sounds great, thanks! But wait, there's more... ;)


Create health check route

Date: 2023/12/06
Developer Name: yash raj

Issue Ticket Number

Closes #16.

Description

added a /health route to allow us to know if the backend is functioning properly.

Documentation Updated?

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Tested in Staging?

[ ] Yes
[x] No

Under Feature Flag

[ ] Yes
[x] No

Database Changes

[ ] Yes
[x] No

Screenshots
Attach any relevant screenshots, such as test coverage reports, before and after images, or other visual aids.
Test Coverage
Provide information on the test coverage for the changes made in this PR. Include details on the types of tests conducted and their outcomes.

closing this in favor of

#42
#43


use Solid Application Data Discovery

https://github.com/solid/solid-profile-ui/blob/3b6ec5ab4b01fd97eab1b117ac02705bb0c495ce/assets/scripts/models/profile.js#L35
Line above seems to assume /profile/ in URI. If someone used different profile editor it might have created different path. Shouldn't profile editor also use Solid Application Data Discovery and not make any special assumptions about URI patterns?

Thanks for raising this issue. We'll address it asap.

Fixed in 69b4402fd6512567e4f16ef365779428808a82a8


feat: GitHub Issue Form

Description
I have replaced old github issue templates with the new github issue forms.
Fixes #8047
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I have tested the code on my own repository before making a PR.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@Nikhil-Nandagopal @mohanarpit
Do review this and let me know if something needs to be changed.

@Rishabh-Rathod Could you please review this PR as well?

@Rishabh-Rathod Could you please review this PR as well?

Tried out creating an issue, the new form experience is really nice. This is a great contribution @Hard-Coder05  😁


change Bundle-SymbolicName to name

add tests for name and display-name in java

Just started reviewing :) :octocat: Sent from GH.

Merged, thanks! See 18aba66...0554310 :octocat: Sent from GH.


Adds the lib package preinstalled for newly created services

I'm going to hold off on this for now; maybe we consider putting this behind a flag? We'll discuss. I know I tentatively agreed earlier; will re-open shortly.


Short solution needed: "chrome headless record video" (chrome-headless)

Please help us write most modern and shortest code solution for this issue:
chrome headless record video (technology: chrome-headless)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

How to capture video


Recorded Video with KilpFlip Not Loaded

Hi,
I m using KilpFlip sdk for live stream.
My recorded video are no running on ios devices, they are showing only loaded status.
Please help us.

Experiencing the same issue. Videos are played on kickflip dashboard on web only or via https://www.hlsplayer.net/
Default implementation uses MPMoviePlayerViewController to play the saved stream. I tried changing it to AVPlayer and also tried opening the url in safari browser but the saved stream doesn't plays.


Clippy stuck at the bottom of my page

Case in point: https://daf.lol

Wait nvm

Welp. Still doesn't work.
I've tried everything. How the hell do I make it move? I've used the moveTo stuff but still no dice

I can see that the script makes a div that contains it (I can shift it up and down in chrome inspect element), but I don't see a way I can override it.

Never mind, it's an ancient script and I doubt anyone will see this.

Ancient, yes, but i saw.

woke af 👀
---- On Tue, 31 Jul 2018 18:41:34 +0000<EMAIL_ADDRESS>wrote ----
Ancient, yes, but i saw.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Container path may be missing path components

When creating an SBOM from pieces of a container, the files may appear to be directly
e.g. A.zip has a file under usr/bin/fileA
An SBOM is generated with a config file that lists:
archive = "A.zip"
extractPaths = "some-directory-with-only-usr/bin-files"
The resulting SBOM should have fileA with a container path of <parent_uuid>/usr/bin/fileA, but it actually just has <parent_uuid>/fileA. This could potentially be inferred to some degree from the provided installPrefix? But msi/exe installers get complicated.

Rebasing (absolute?) symlinks has issues in a similar situation.
e.g. symlnkA -> /usr/bin/fileAwith an extract path with only files in usr/bin that doesn't also replicate the usr and `bin folders within it results in these lines messing up:
# Rebase to get the true location
current_path = os.path.join(extract_dir, dest)

current_path becomes something like <extract_path>/usr/bin/fileA... which doesn't exist because it is just <extract_path>/fileA on the system that is doing the analysis.
A possible fix could be assuming that the layout for the extracted files and created symlinks were pulled directly from the system they run on, and that installPrefix can be used to pull out the part of the path that should not be replicated.

OK, the fix for the symlink resolving works -- however, if files from the same folder (e.g. /usr/bin) (or separate folders such as /bin or /sbin) have been split up into multiple extractPaths, the resolver doesn't consider files in those other directories.
The only way I could see to fix this would be to internally create a "file system mapping" of which installed directory different extract paths map to (one to many). Which gets into more complex questions about how to do SBOMs with files from different systems.

A "quick" solution to address this could be adding a containerPath option that specifies a path that should go between the container UUID and the relative paths for files within the extractPaths. Or users can just replicate the directory structure they want it to have in the container by having some nested folders.
I think a separate issue for refactoring Surfactant to use data structure that maps better to a file system hierarchy, and adds a mechanism to the config file to specify a unique ID representing the filesystem a particular config file entry "installs to" will be needed -- if none is specified, everything would be placed under a default filesystem ID. Resolving relationships would then be given a FS tree/hierarchy to consider, and that would avoid establishing links to files not on the same filesystem.


oc.PacketMatchTypes_IP_PROTOCOL_IP_IN_IP translated as 5 , it should be 4.

Describe the bug
oc.PacketMatchTypes_IP_PROTOCOL_IP_IN_IP ENUM variable takes 5 as value.  It should be 4 (IP-in-IP tunneling).
https://github.com/openconfig/gribigo/blob/c2737bd7779966f45cfb46e910d920b8cf8430a9/aft/oc.go
// PacketMatchTypes_IP_PROTOCOL_IP_IN_IP corresponds to the value IP_IN_IP of PacketMatchTypes_IP_PROTOCOL
PacketMatchTypes_IP_PROTOCOL_IP_IN_IP E_PacketMatchTypes_IP_PROTOCOL = 5
To Reproduce
Expected behavior
https://github.com/openconfig/public/blob/master/release/models/acl/openconfig-packet-match-types.yang
identity IP_IN_IP {
base IP_PROTOCOL;
description
"IP-in-IP tunneling (4)";
reference
"RFC2003: IP Encapsulation within IP";
}

I agree that IP-in-IP has the protocol number 4 as the value that appears in the packet IP header, but the enum constant used in the ygot generated code is unrelated to that. The aft/oc.go is ygot generated from the YANG. That particular constant will be represented as the string "IP_IN_IP" when serialized to IETF JSON.
In code, if you use oc.UnionInt64(4) that would incorrectly set the enum to "IP_IGMP".
@robshakir @wenovus


Error "accepts at most 1 arg(s), received 2" is there in v0

It worked well till 5th March. But on 6th March, job failed.
I never changed my source code during these 2 days.
I think it was because of this PR:https://github.com/anchore/sbom-action/pull/446
New version is released, v0(I was using) is also updated after this PR.
I tried the old version of v0.15.8. It worked.

Thanks @harmw -- it looks like @LinLiKinto, you're using an older version of Syft and need to update to a version that uses the scan command, rather than packages. Just removing any pinned version should fix the problem. Are you able to give that a try?

@kzantow Thank you for your advice. But we are using https://github.com/xeol-io/xeol/pull/294  after anchore/sbom-action. They are not updated for new version of syft. If we update the version of syft, we will encounter error in that GitHub Action.
But I got the point now. I will wait for their update. Before that, I will fix the version to v0.15.8.
Thank you very much.

Looks like the upstream issue on xeol is closed, so I presume this is no longer an sbom-action issue?
I'll close this, but feel free to open a new issue if required 🙏


Regression Props Warning

@Jag96
Details
Refer comment from PR  -> https://github.com/Expensify/App/pull/5095#issuecomment-920480208
Should not show that warning, so handled in the PR. The changes don't affect any expected behavior in production. But based on code changes it looks like affecting native mobile devices, so added tests for that.
Fixed Issues
$ https://github.com/Expensify/App/issues/4645
Tests

Run the app in development mode locally on Android and iOS devices.
You should not see the warning in this comment

QA Steps

Go to Settings
Click Profile
Click the pen icon to update or add a photo
Click upload photo
Refer Fix section below, it should work as shown there.
Create a new workspace if you don't have one.
Go to Setting
Click on your workspace.
Tap on the Workspace icon
Click the pen icon to update or add a photo
Click upload photo

We should show only two options now

Take photos
Choose from gallery

Tested On

[x] iOS
[x] Android

Screenshots

iOS
For Reviewer - No warning now.
https://user-images.githubusercontent.com/85645967/133804208-4c066fbb-1038-4817-a5f0-4ca6b95242b1.mp4
For QA

Android
For QA

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@tgolen clarification should I wait for this PR to get deployed in production to get paid?.

🚀 Deployed to production by @Jag96 in version: 1.1.0-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


add background remover tool

@t3dotgg Hey Theo, thank you for making videos on YouTube and for this project. Could you please review my code, because I really want to contribute to this project?


Database errors

Hey Kareem and your team.
You guys did great work for people like me who are new to android development.
Actually i want to explore your app for my learning purpose but i am facing some bugs and have no idea that how to deal with them.
The screens are empty and not showing any data and in android studio i am getting data base permission errors.
Kindly see the screen shots attached
Android studio screen shot :

app screen shot:

Hey!
can you please provide schema of db of this app?
@kareem983


temporary fix for issue #15

browserify 10.2.5+ follows symbolic links and that broke this module. This pull request set version of browserify to 10.2.4. See discussion in #15

Thanks for this temporary fix. I've released 0.2.9 with this version constraint.

thank you!!


Fix a typo error in docs

This PR is proposed to fix a simple typo error in the document.

Thanks!


pdf-sign: Fix program name in help text

Description of changes
Use correct program name, rather than wrapped program, in usage text.
Things done

Built on platform(s)

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

[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@TomaSajt Please review.

@TomaSajt Fantastic feedback. I opted for keeping the names as in your second suggestion. I considered it previously, but wasn't sure if this would break some kind of recommended practice.


gateway hostport 8080 conflict with node-local-dns hostport 8080

gateway hostport 8080 conflict with node-local-dns hostport 8080
What happened:
gateway hostport 8080 conflict with node-local-dns hostport 8080
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Diagnose information (use subctl diagnose all):
Gather information (use subctl gather):
Cloud provider or hardware configuration:
Install tools:
Others:

What version of Submariner are you using?

0.12.1

Port 8080/8081 are used for metrics and is a known issue with Submariner releases prior to 0.14.
It is addressed in 0.14 release.
Release notes: https://submariner.io/community/releases/#v0140


[Suggestion] Teleport - Negation of the tag-check proposal

I've tested out the height adjust teleport this night and found that I jumped up on all kinds of objects when I was over them!
I then found out the solution. Tag or put ExcludeTeleport to ALL your objects with a specific tag to filter them out.
It may work out well in the examples, but in most real usecases I think it's the opposite here. There are probably far less objects that you should be able to walk on.
Easy fix is to rename invalidTargetWithTagOrClass to validTargetWithTagOrClass and negate the validation check.
Then you can just mark out your groundlevel with this tag!

This question comes up a lot, but the solution you've provided isn't workable.
Firstly, if you have an opt in method where you have to tag items to teleport to, then many people will just want it the other way where they want to have it only exclude locations, they will also say "this is the most obvious use case".
Secondly, people will be adding in objects and wondering why the teleport is broken because they won't realise they have to then tag all the items before they can teleport on to them, meaning more questions will come flooding in, and no matter how much documentation there is or videos on the subject, people will always ask first then rtfm later. This means more questions is a drain on time.
What works for one person doesn't work for someone else, but the current implementation is easier for people to get their head around because teleporting naturally works until you want to prevent it from working and that's the point when you apply exclude logic.


Branch 2.2.0 palantir4 k8s

Merge branch-2.2.0-palantir4-k8s into the Palantir master branch.
This brings over the 77 commits related to Kubernetes support to the master branch now that we've worked out support for the Spark internal API breaks that came through in 2.2.0-palantir5

// handled merge conflicts through GH UI


[UNSUPPORTED PROTOTYPE] Datepicker: Add right to left language support (RTL)

Fixes #1970
Additional description
Support RTL in date picker component. The work done is mostly around keyboard interaction that was flipped. Added some tests to the existing snapshot test for the component, since story book testing for date picker is disabled (refer to story-based-tests.js)

CONTRIBUTOR checklist (do not remove)
Please complete for every pull request

[ ] First-time contributors should sign the Contributor License Agreement.  If you haven't before, wait a few minutes and a bot will comment on this pull request with instructions.
[X] npm run lint:fix has been run and linting passes.
[X] Mocha, Jest (Storyshots), and components/component-docs.json CI tests pass (npm test).
[X] Tests have been added for new props to prevent regressions in the future. See readme.
[X] Review the appropriate Storybook stories. Open http://localhost:9001/.
[X] Review tests are passing in the browser. Open http://localhost:8001/.
[X] Review markup conforms to SLDS by looking at DOM snapshot strings.

REVIEWER checklist (do not remove)

[ ] TravisCI tests pass. This includes linting, Mocha, Jest, Storyshots, and components/component-docs.json tests.
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

Required only if there are markup / UX changes

[ ] Add year-first date and commit SHA to last-slds-markup-review in package.json and push.
[ ] Request a review of the deployed Heroku app by the Salesforce UX Accessibility Team.
[ ] Add year-first review date, and commit SHA, last-accessibility-review, to package.json and push.
[ ] While the contributor's branch is checked out, run npm run local-update within locally cloned site repo to confirm the site will function correctly at the next release.

please review @minevskiy @interactivellama

@interactivellama @kevinparkerson @davidlygagnon @garygong this PR is ready for final approval and merge. Can you please take a look?

Updating my comment. I'm going to go ahead and merge tonight.

I was testing this and noticed that, since DatePicker creates its own Portal, there is no way for me as a consumer to wrap that portal into a Provider.
I think we have to wrap DatePicker into LanguageDirection and pass direction as a prop to Calendar and Day.
@interactivellama , what do you think?

Just to end this thread in case anyone is watching. We ending up wrapping the portal in order to carry over the Language Direction context.


Do not support decorator in editor

Describe the bug

TS deorator is not recognized on editor.
Link to the blitz that caused the error
https://stackblitz.com/edit/stackblitz-starters-ewicp7?file=package.json,index.ts,tsconfig.json
Steps to reproduce
Create a blank project, install class-validator and typescript, then create index.ts:
import { IsEmail, IsString, MinLength, MaxLength, Contains, IsNotEmpty } from 'class-validator';
import { validate } from 'class-validator';

class BaseContent {
  @IsEmail()
  email: string;

  @IsString()
  password: string;
  myProperty?: string;
}

class User extends BaseContent {
  @MinLength(10)
  @MaxLength(20)
  name: string;

  @Contains('hello')
  welcome: string;

  @MinLength(20)
  password: string;

  @IsNotEmpty()
  myProperty: string;
}

Expected behavior
The ts decorator will be recognized correctly.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 123
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
performance.memory = {
  "totalJSHeapSize": 129058191,
  "usedJSHeapSize": 125098623,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 7dbe22a9

Additional context
No response

Hey @yunnysunny. I just tested your project and it seems to work for me. Can you try again? Maybe something didn't loaded yet in regards to the editor?

Hey @yunnysunny. I just tested your project and it seems to work for me. Can you try again? Maybe something didn't loaded yet in regards to the editor?

Yes, it works ok now.


Underscore support to move to front of line

Related to this enhancement: https://github.com/atom/vim-mode/issues/168
I'm not too familiar with the spec testing and plan to add that, but I wanted to go ahead and send this pull request to see how off the mark this implementation might be. Originally, it was just going to be a extra mapping of the '^' key, but I learned something new from the issue comments which is that '_' with the prefix count will move it down as well. This is also my first public pull requests, so forgive me for my ignorance.

:+1: I'll definitely merge if you add some specs.

Added the spec and while I was at it I noticed other, similar motions have since been updated (I'm guessing due to the Atom API release) so I've mimicked this new style as well.

Great work @ftwillms thanks a lot.


The problem of flushandreload() function

Is it wrong that timing first then flush in the function flushandreload(). It should be flush first, should it?

No. Flush should be before the waiting, so outside of that function. The reload comes after the waiting, so at the beginning of the function.

So everything is as intended here


Make Membrane.Element.Base.{Sink,Filter,Source} less verbose

The names of the modules are ridiculously long and since they are used in every element they should be much shorter.

We should also rename Membrane.Element.Base.Mixin.SomethingBehaviour, as they are present in the documentation too

#171 closes this issue


php version 5.x compatibility issue with version 1.3.0

Hi,
We are using your plugin on a site which still uses php 5.x and have an issue with the php code in the latest version.
PHP Parse error:  syntax error, unexpected '[', expecting ',' or ';' in /wp-content/plugins/advanced-custom-fields-recaptcha-field/includes/settings-page.php on line 158
<?php echo __('Plugin Version'); ?></ echo get_plugin_data(ACF_RECAPTCHA_ABSPATH['Version'];

Fix something like this (set to a variable first):
<?php echo __('Plugin Version'); ?>: <?php
$RECAPTCHA_ABSPATH = get_plugin_data(ACF_RECAPTCHA_ABSPATH);
echo $RECAPTCHA_ABSPATH['Version'];
?>

Another issue which isn't related to the php version.
I cannot access the settings page which is linked on the plugins page.
it shows "Sorry, you are not allowed to access this page." even if i am adminstrator.
Url:
/wp-admin/options-general.php?page=acf-recaptcha
The acf field settings page is working as expected.
Url:
/wp-admin/edit.php?post_type=acf-field-group&page=acf-recaptcha
thanks in advance

Hi,
Thanks for reporting. I have confirmed the bug that Plugins settings link is incorrect.
For the record, can I check the exact version of PHP that you are using? It works fine for me on PHP 5.6.

We still have one server which runs php version 5.3.
With php 5.4. Array dereferencing was introduced
http://php.net/manual/en/language.types.array.php#example-62
So your code doesn't run on older php versions.

Noted with thanks! Version 1.3.1 should fix this problem, which should be up on the plugins repository soon.


Split test/evptests.txt into separate files.

The remaining test/evptests.txt seems to be all PKEY stuff, maybe rename it accordingly as well?

done.

commit 07fbdfe in master, thanks.!


new version Bone

https://arxiv.org/abs/2409.15371
Bone has been updated to a new version. The current Bone is faster, more memory-efficient, and performs better than the Lora series, making it a foundational structure comparable to Lora. The previous version of Bone has now been renamed to Bat, and users can use it by including "bat" in init_weight.

ddressing some of the shortcomings of the initial Bone implementation. Just to be clear: What was previously called "Bone" now corresponds to "Bat" and the current "Bone" is something different (but similar). Am I right in my understanding that the new Bone is more memory efficient and faster than Bat but Bat performs better (tables 4 and 7)?

Yes, your understanding is correct. Bone is now more like a foundational method comparable to Lora. Bat is more like an improved method compared to Pissa. However, Bone itself has already surpassed Pissa.

Finally, WDYT about updating the Bone finetuning example to explicitly show results for Bone and Bat?

I don't quite understand this issue. Currently, Bat is slower, so I think people would prefer to use Bone for training or research.
The other parts have been updated.

I don't quite understand this issue. Currently, Bat is slower, so I think people would prefer to use Bone for training or research.

That's true, but Bat has slightly better scores, right? So some users might be willing to trade memory+speed for better scores. If you think it's not really worth it, at least the example could mention that this is something that users can try out?

I don't quite understand this issue. Currently, Bat is slower, so I think people would prefer to use Bone for training or research.

That's true, but Bat has slightly better scores, right? So some users might be willing to trade memory+speed for better scores. If you think it's not really worth it, at least the example could mention that this is something that users can try out?

That's indeed the case, so where should I include this explanation?

That's indeed the case, so where should I include this explanation?

How about adding a sentence or two here: https://github.com/huggingface/peft/tree/main/examples/bone_finetuning#advanced-usage. It could also be a good idea to add a flag the args of the script to enable Bat. WDYT?

That's indeed the case, so where should I include this explanation?

How about adding a sentence or two here: https://github.com/huggingface/peft/tree/main/examples/bone_finetuning#advanced-usage. It could also be a good idea to add a flag the args of the script to enable Bat. WDYT?

Okay, I have added instructions to guide users on how to use Bat.

Thanks for this update @JL-er. Could you please merge the latest main branch of PEFT, as there is a fix there required for CI.

Thanks for this update @JL-er. Could you please merge the latest main branch of PEFT, as there is a fix there required for CI.

Completed.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@JL-er Thanks for merging. Running the tests leads to a lot of errors related to Bone, such as

FAILED tests/test_custom_models.py::PeftCustomModelTester::test_disable_adapters_with_merging_087_Vanilla_MLP_1_Bone - RuntimeError: shape '[9, 10, 5, 2]' is invalid for input of size 90

Could you please check what happened there?

fix all

Thanks for this update to the Bone method. These improvements should hopefully help with the adoption of this method.
Note that technically, this is a backwards incompatible change, since the underlying algorithm for Bone was changed. This is fine as Bone is not part of any PEFT release. But after the next PEFT release (could be next week), this type of change will no longer be possible (we can still add new variations of Bone, but the default one needs to stay the same).

Thank you for your reminder. Currently, Bone is a very basic method that is better than LoRA in terms of speed and memory usage, so I will not make any modifications to it.

@BenjaminBossan My paper has undergone significant revisions. Can I update the citations and explanations?

@JL-er Yes sure, go ahead. Did anything on the implementation side change? This would be more difficult to amend now.


Web interface problem

hello, first of all thanks for your development. the installation went smoothly, the sensor works fine, but the web interface is not available, when I want to change the setting, I cannot reach anywhere. I completely deleted the esp card, I reinstalled it many times, but the problem was not solved, what can I do?

I cannot enter web interface too, even if i try to access it manually

Hi, Did you solve it, I am in the same situation?

Were you at some point able to connect the device to your WiFi? I figured out that as soon as the WiFi connects, there's no way to change any settings, even if for example MQTT-settings are wrong. I had this issue and you can 'solve' it by removing the connection to your WiFi. This way, the esp will go back to AP-mode. Easiest solution is to turn off your WiFi until you've changed the settings. If that's not possible try wrapping a bit of aluminium foil around the esp to block the WiFi connection. Can be a bit tricky to figure out how much foil you need in order to be able to connect (e.g. with a phone) and block the WiFi but it worked for me.

I am not able to connect to web interface at all, not a single time.
Probably due to Issue #61