Files altered by linting tools are not commited anymore in v9

Hi, :hand:
Description
After upgrading to lint-staged 9 and updated our config file from:
{
  "relative": true,
  "linters": {
    "*.php": [
      "./vagrant-wrapper.sh php bin/php-cs-fixer fix --config .php_cs.dist --diff",
      "./vagrant-wrapper.sh php bin/phpstan analyse --level 7 --no-ansi --no-progress",
      "git add"
    ],
    "assets/**/*.{js,jsx,vue}": [
      "eslint --fix",
      "git add"
    ],
    "*.{json,yml,yaml,md}": [
      "prettier --write",
      "git add"
    ]
  }
}

to this (the old way was better, but w/e :disappointed:) :
const path = require('path');

function makeRelativePaths(absolutePaths) {
  const cwd = process.cwd();

  return absolutePaths.map(file => path.relative(cwd, file));
}

module.exports = {
  '*.php': (absolutePaths) => {
    const relativePaths = makeRelativePaths(absolutePaths);

    return [
      `./vagrant-wrapper.sh php bin/php-cs-fixer fix --config .php_cs.dist --diff ${relativePaths.join(' ')}`,
      `./vagrant-wrapper.sh php bin/phpstan analyse --level 7 --no-ansi --no-progress ${relativePaths.join(' ')}`,
      `git add ${relativePaths.join(' ')}`,
    ];
  },
  'assets/**/*.{js,jsx,vue}': (absolutePaths) => {
    const relativePaths = makeRelativePaths(absolutePaths);

    return [
      `eslint --fix ${relativePaths.join(' ')}`,
      `git add ${relativePaths.join(' ')}`,
    ];
  },
  '*.{json,yml,yaml,md}': (absolutePaths) => {
    const relativePaths = makeRelativePaths(absolutePaths);

    return [
      `prettier --write ${relativePaths.join(' ')}`,
      `git add ${relativePaths.join(' ')}`,
    ];
  },
};

It seems that files are not added anymore to the commit after being processed by ESLint, Prettier, PHP-CS-Fixer, [...].

Running git diff, the file has been linted but not commited:

Steps to reproduce

Edit a file that will be matched by linters glob patterns
Git add this file
Git commit this file
Husky triggers lint-staged, that will execute some commands (ESLint + git add in my case)
The file is commited, but not the linted version (after being processed by ESLint)

Debug Logs

expand to view
husky > pre-commit (node v11.5.0)
  lint-staged:bin Running<EMAIL_ADDRESS>+0ms
  lint-staged Loading config using `cosmiconfig` +0ms
  lint-staged Successfully loaded config from `/path/to/app/.lintstagedrc.js`:
  lint-staged { '*.php': [Function: *.php],
  lint-staged   'assets/**/*.{js,jsx,vue}': [Function: assets/**/*.{js,jsx,vue}],
  lint-staged   '*.{json,yml,yaml,md}': [Function: *.{json,yml,yaml,md}] } +6ms
  lint-staged:cfg Validating config +0ms
Running lint-staged with the following config:
{
  '*.php': (absolutePaths) => {
    const relativePaths = makeRelativePaths(absolutePaths);

    return [
      `./vagrant-wrapper.sh php bin/php-cs-fixer fix --config .php_cs.dist --diff ${relativePaths.join(' ')}`,
      `./vagrant-wrapper.sh php bin/phpstan analyse --level 7 --no-ansi --no-progress ${relativePaths.join(' ')}`,
      `git add ${relativePaths.join(' ')}`,
    ];
  },
  'assets/**/*.{js,jsx,vue}': (absolutePaths) => {
    const relativePaths = makeRelativePaths(absolutePaths);

    return [
      `eslint --fix ${relativePaths.join(' ')}`,
      `git add ${relativePaths.join(' ')}`,
    ];
  },
  '*.{json,yml,yaml,md}': (absolutePaths) => {
    const relativePaths = makeRelativePaths(absolutePaths);

    return [
      `prettier --write ${relativePaths.join(' ')}`,
      `git add ${relativePaths.join(' ')}`,
    ];
  }
}
  lint-staged:run Running all linter scripts +0ms
  lint-staged:git Running git command [ 'rev-parse', '--show-toplevel' ] +0ms
  lint-staged:run Resolved git directory to be `/path/to/app` +13ms
  lint-staged:git Running git command [ 'diff', '--staged', '--diff-filter=ACM', '--name-only' ] +13ms
  lint-staged:run Loaded list of staged files in git:
  lint-staged:run [ 'assets/app/index.js' ] +8ms
  lint-staged:gen-tasks Generating linter tasks +0ms
  lint-staged:gen-tasks Generated task:
  lint-staged:gen-tasks { pattern: '*.php', commands: [Function: *.php], fileList: [] } +2ms
  lint-staged:gen-tasks Generated task:
  lint-staged:gen-tasks { pattern: 'assets/**/*.{js,jsx,vue}',
  lint-staged:gen-tasks   commands: [Function: assets/**/*.{js,jsx,vue}],
  lint-staged:gen-tasks   fileList: [ '/path/to/app/assets/app/index.js' ] } +2ms
  lint-staged:gen-tasks Generated task:
  lint-staged:gen-tasks { pattern: '*.{json,yml,yaml,md}',
  lint-staged:gen-tasks   commands: [Function: *.{json,yml,yaml,md}],
  lint-staged:gen-tasks   fileList: [] } +0ms
Stashing changes... [started]
  lint-staged:git Running git command [ 'status', '--porcelain' ] +16ms
Stashing changes... [skipped]
→ No partially staged files found...
Running linters... [started]
Running tasks for *.php [started]
Running tasks for assets/**/*.{js,jsx,vue} [started]
Running tasks for *.{json,yml,yaml,md} [started]
Running tasks for *.php [skipped]
→ No staged files match *.php
  lint-staged:make-cmd-tasks Creating listr tasks for commands [Function: assets/**/*.{js,jsx,vue}] +0ms
Running tasks for *.{json,yml,yaml,md} [skipped]
→ No staged files match *.{json,yml,yaml,md}
eslint --fix [file] [started]
  lint-staged:task cmd: eslint +0ms
  lint-staged:task args: [ '--fix', 'assets/app/index.js' ] +0ms
  lint-staged:task execaOptions: { preferLocal: true, reject: false, shell: false } +0ms
  lint-staged:task cmd: git +4ms
  lint-staged:task args: [ 'add', 'assets/app/index.js' ] +0ms
  lint-staged:task execaOptions: { preferLocal: true, reject: false, shell: false } +0ms
eslint --fix [file] [completed]
Running tasks for assets/**/*.{js,jsx,vue} [completed]
Running linters... [completed]
  lint-staged linters were executed successfully! +2s
[chore/deps-js 1deeb9de] test
 1 file changed, 3 insertions(+), 1 deletion(-)

Environment

OS: Debian 9.9 (Stretch)
Node.js: v11.5.0
lint-staged: 9.0.1

That's weird because in debug logs we can see that git add assets/app/index.js... :thinking:
Thanks! :)

Thanks for the clear report! I’ll check it out. One thing that comes to mind is that possibly the commands are run parallel and not sequentially in this case.
Also, your example is a good example of the power of relative: true. Does your setup not work on absolute paths?

Ah, I didn't think about parallelism. That's probably the issue but I don't know how to fix it yet.
Yes relative: true was so much useful, I'm a bit sad that it disappears but that's the life. :stuck_out_tongue_closed_eyes:
Nope it does not work with absolute paths:

We use a VM to run our Symfony app, so we want to make sure every commands are ran inside the VM (with the vagrant-wrapper.sh, but we didn't use it everywhere because.... we forgot to :smile:)
I wanted to keep commiting inside or outside the VM, to we use relative: true

I cannot reproduce this. On the lint-staged repo, at commit 6c1e42f, when I add the following .lintstagedrc.js config:
module.exports = {
  '*.{js,json,md}': ['prettier --write', 'git add'],
  '*.js': files => [`npm run lint:base --fix ${files.join(' ')}`, `git add ${files.join(' ')}`],
  '.*{rc, json}': ['jsonlint', 'git add']
}

adding empty lines to a JS file and staging it, running node ./index.js will remove the file from modified and staged, because npm run lint:base --fix  will basically just remove the files.
Also, adding console.log("test"); to a a file, staging it, and running node ./index.js, will leave an console.log('test') edit to staged.

Hum weird, I will take some time this evening to investigate 🧐

Regarding relative, I might add a --relative flag. But that's basically just moving the deprecated advanced configuration to command line flags.

That would be really nice. Was there a reason to remove the advanced configuration? :thinking:
When I saw this, I was like ... "well, we will stay with lint-staged 8 forever :tired_face:" and I'm sure I'm not the only one :smile:

I think it's related to relativePaths. For git add to work, pass absolute paths to it that you're getting in the function arguments.

Before adding, --relative, we should address how resolveTaskFn sets a different working directory for git commands vs the rest. Maybe if we add --relative, all the commands should run with the git repo root as the working directory.

I think I found an issue with how tasks are created from a function linter return an array of commands. Currently, it generates a single task with multiple promises, but I refactored it to return an array of tasks instead, hopefully fixing this issue: https://github.com/okonet/lint-staged/pull/650

Can you please re-test with<EMAIL_ADDRESS>It's hopefully fixed.

Thanks, it works really nice with 9.0.2! :)
I'm closing this issue since it's fixed


Parser crashes on array desctructuring in arrow function parameter

I'm submitting a bug report
Webpack version:
2.1.0-beta.25
Please tell us about your environment:
Windows 10
Current behavior:
Webpack Parser crashes on array destructuring in arrow function parameter.
TypeError: Cannot read property 'type' of null
    at Parser.enterPattern (...\node_modules\webpack\lib\Parser.js:906:27)
    at Parser.<anonymous> (...\node_modules\webpack\lib\Parser.js:926:8)
    at Array.forEach (native)
    at Parser.enterArrayPattern (...\node_modules\webpack\lib\Parser.js:925:19)
    at Parser.enterPattern (...\node_modules\webpack\lib\Parser.js:907:38)
    at ...\node_modules\webpack\lib\Parser.js:892:18
    at Array.forEach (native)
    at Parser.inScope (...\node_modules\webpack\lib\Parser.js:890:9)
    at Parser.walkArrowFunctionExpression (...\node_modules\webpack\lib\Parser.js:685:7)
    at Parser.walkExpression (...\node_modules\webpack\lib\Parser.js:650:40)
    at Parser.<anonymous> (...\node_modules\webpack\lib\Parser.js:644:9)
    at Array.forEach (native)

Expected/desired behavior:
The code should parse correctly.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem along with a gist/jsbin of your webpack configuration.

    let a = [].find(([, i]) => true);
    console.log(a);

Browser: all

Language: ES6

@sokra is this an acorn bug? Or specific to our parser.

Acorn can parse it fine: https://astexplorer.net/#/PtsxvTSUfZ
The bug is in webpack's parser, which doesn't expect a (perfectly valid) null entry.

I wrote a fix in #3250, but I'm not sure how to write the tests such that webpack doesn't try to run the syntax through Uglify, or doesn't try to run it in node <= 5. Node 4 doesn't support destructuring.


Allow time range >23 hours in shared ride

Scenario: False positive

Requirement:

Time 02:59 or 26:59 should be allowed

This has been fixed in commit https://github.com/TIXI24/sfitixi/commit/d66b19a42d440e631883de101a135b39e95bde4b


Load new bundles into db

subscribe to DSS and handle new bundles (Via a queue triggering a lambda)

This has been done, though we still need ETL:

On the DSS event bus for continuous updates
On a cron for database migrations


Update downloadAndInsertOpenCV.sh

@Rohan4045
Are you going to reply?
Otherwise, I'm going to close this PR.

I was trying to add opencv in my project, i have downloaded opencv, but not able to add, then i tried this script, and this also do the same work, . I have mistakenly commented out as i want only for Android. Sorry for that.


Backward compatibility broken for Xml Comments remarks in Swashbuckle 5.0

Let's do the following controller :
    [RoutePrefix("example")]
    public class TestController : ApiController
    {
        /// <summary>
        /// This comment will go into swagger to explain what the method does.
        /// </summary>
        ///<remarks>
        /// this comment will end up in implementation notes BUT ALSO in the title
        ///</remarks>
        [Route("authenticated", Name = "exampleAuthenticatedRoute")]
        [HttpGet]
        [ResponseType(typeof(string))]
        public HttpResponseMessage GetExample()
        {
             return Request.CreateResponse(HttpStatusCode.OK, "dummy");
        }
   }

In 4.1.0, the implementation note appeared inside the block for the method
In 5.0.0, it appeared inside the block and on the side of the controller name.
Note that I think it was working with 5.0.0-alpha

So, technically this looks like a bug in the embedded version of swagger-ui (v2.1.4) as opposed to Swashbuckle itself.
I've created a corresponding ticket there ...
https://github.com/swagger-api/swagger-ui/issues/937

seems fine to me.
you've done a nice bug report on swagger-ui, I hope this will be fixed quickly :)

Should be fixed in latest release (5.0.1)


Build snpguest for Windows

Hi,
I am facing some issues building snpguest for windows - looks like crate msru only supports Linux: https://docs.rs/msru/latest/msru/
Are there any plans to make snpguest windows-compatible?
Thanks.

Most of this crate is Linux-only. The underlying sev crate that we use for building most of this tool is Linux-only. I don't know if there exists an equivalent for windows.

Thanks for saving my time, I was next considering to look into sev to see if that can be built for windows.
Have you considered providing support/build an alternative for windows or is that too far off and am I the only one asking about it? The (sad) reality is that there are so many proprietary enterprise applications running on windows servers, would be a pity if attestation support would not be available for this large chunk of the market.

@nicopal unfortunately reading an MSR from user-space is not easily done on Windows (which is why msru doesn't offer windows support). Also, like @tylerfanelli mentioned, this tool is primarily Linux only due to the way we interact with the device drivers. It isn't to say we won't accept PRs adding needed support.

Thank you, we will check internally if we can prioritise this now (or near future). Adding windows support could be useful in several cases.


[Bug]:

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
infiniflow/ragflow
Commit ID
#flaskwrongrag0001
Other environment information
No response
Actual behavior

Expected behavior
No response
Steps to reproduce
i update the project because i think it's wrong with version or something,but it appears this kind of issue

Additional information
No response

No clue yet.

all right,just upgrade the huggingface_hub to fix it

run this :  pip install --upgrade huggingface_hub


Disallow installing transformers >= 4.41

transformers >= 4.41 appears to create a performance regression in the fms-hf-training fine tuning jobs.
This PR prevents the regression to happen in the fms-hf-tuning image by disallowing the installation of transformers >= 4.41, meaning that transformers == 4.40 will be installed.
This fix has been performance tested. It reverts the performance to the level prior to the publication of transformers 4.41

with the regression

with the fix

See also: RHOAIENG-8551
Closes #201

I feel we should try to understand the root cause, because not allowing updates means not getting new fixes/features also.

I feel we should try to understand the root cause, because not allowing updates means not getting new fixes/features also.

definitely. This only allows the regression not to propagate this repo for the time being.

@kpouget can you share a simple repro script?

I feel we should try to understand the root cause, because not allowing updates means not getting new fixes/features also.

Also, without understanding the root cause, we cannot exclude this regression actually fixes some incorrect behaviors.

@fabianlim I've updated the ticket https://github.com/foundation-model-stack/fms-hf-tuning/issues/201 description to include the steps to reproduce.

Hello, this PR appears not to work when we build the image, like if the requirements.txt isn't followed. Could you please double check if that's the right way to pin the dependency?

Wrong place to make this update, should be in pyproject.yaml, this file is no longer used for package dependency versions or installation
ack, I close this one


FEAT: add ansys-api-template

Fix #90 by adding the "ansys-api-template" to the collection of available templates.

I have no idea what is going on here with the CI/CD pipeline. It randomly passes and fails. I am not sure if it can be the cookiecutter version.

Just changed the cookiecutter version and this failed again on both 3.8 and 3.11.


Validate top level lookups

Fixes #45 so that configs with lookups which are wrong in ways which we can trivially detect do indeed error.
This doesn't handle properties referenced in exit conditions, which I've since noticed are also fairly constant and which we could probably validate, though I suspect those deserve a slightly different approach.

I'm not sure what's causing the test failure here. I think that example.yaml is valid here, so I'm not sure why the launched subprocess would be erroring. I've made a change to the assertions around the subprocess in #76 which I'm hoping will clarify the error.


Uninitialized value in debug version make system crash. (Assertion failed: handle->write_queue_size >= req->queued_bytes)

this crash only happen in Windows debug version.
in win/tcp.c:
int uv_tcp_write(uv_loop_t* loop,
                 uv_write_t* req,
                 uv_tcp_t* handle,
                 const uv_buf_t bufs[],
                 unsigned int nbufs,
                 uv_write_cb cb)

this function  uv_req_init(loop, (uv_req_t*) req);  uninitialized req->u.io.queued_bytes (in debug version it will be 0xCDCDCDCD, release version is  0x0,so it will not make crash). sometimes after WSASend and before initialized this value. the pGetQueuedCompletionStatusEx will immediately push the the uninitialized request to loop->pending_reqs_tail , it will have assest failed in uv_process_tcp_write_req . The probability of triggering this bug is very small. so I suggest add req->u.io.queued_bytes = 0 in the function  uv_req_init

With what version is this?  I ask because I'm not sure I follow.
uv_tcp_write() always sets req->u.io.queued_bytes after calling WSASend().  How then would it be possible to observe an uninitialized value after a call to GetQueuedCompletionStatusEx?
Are you calling uv_write() and uv_run() from different threads?

yes, different thread

Right, you can't do that - libuv is not thread-safe.  Use uv_async_send() if you need to communicate between threads.
I'll go ahead and close this.


feat: generate .bat file bin entry points during lifecycle hooks when on Windows

This was notably missing for Windows support.

Type of change

New feature or functionality (change which adds functionality)

Test plan

Covered by existing test cases
New test cases added

TODO: add test cases

Replaced by #1142


Custom Segment Behavior: Shopping Cart/Trolley Queue Metaphor - Super Slow Redraw

@b-ma Hoping you might be able to take a look at this custom behavior I've been working on for a few days and give some feedback on my approach.
Here is the gist
https://gist.github.com/justinlevi/fa6afbe108620c9806c39b325c17bdef
Summary:
I'm trying to recreate the shopping cart/ train car queue/ (trolly) metaphor. In other words, if you drag a segment left or right, it will respect the boundary of a neighbor/sibling and then push the the neighbor/sibling along the track as well.
I have this working, kind of. The redraw is jittery and slow, which makes me think there must be a better approach.
My first attempt was to create my own queue array, and during the drag, test to see if the current item's start/end (depending on direction) overlaps with a neighbor's start/end. Then, in the overridden _move method, I am looping through my queue array calling `shape.x(segment, renderingContext.timeToPixel.invert(targetX));
After reading through the code closer, I'm noticing there is an internal mechanism to track selectedItems on the Layer class. I'm wondering if there is a built in mechanism that all selected items would receive an edit callback from the Layer?
Ultimately I'm looking for a smooth UX when dragging any number of segments left/right.
As you can see, I also clearly got a bit overboard with my destructuring syntax. I very likely have some super inefficient code. Any feedback you might have would be greatly appreciated.
Full custom behavior below as well:
import * as ui from 'waves-ui';

class CollisionSegmentBehavior extends ui.behaviors.BaseBehavior {

  segmentsData = [];
  DIRECTION = {
    LEFT: 'LEFT',
    RIGHT: 'RIGHT'
  };

  segmentIndex = (search) => {return this.segmentsData.findIndex( obj => { return obj === search }); };

  segmentValues = (renderingContext, shape, dataObj) => {
    return ({
        startX: renderingContext.timeToPixel(shape.x(dataObj)),
        // y: renderingContext.valueToPixel(shape.y(dataObj)),
        endX: renderingContext.timeToPixel(shape.x(dataObj) + shape.width(dataObj)),
        // height: renderingContext.valueToPixel(shape.height(dataObj))
      });
  };

  constructor(segmentsData) {
    super();
    // segmentsData is a reference to the data defining all your segments
    this.segmentsData = segmentsData;

    // binding
    this.isTouchingSibling = this.isTouchingSibling.bind(this);
    this.connectedSiblings = this.connectedSiblings.bind(this);
  }

  edit(renderingContext, shape, datum, dx, dy, target) {
    const classList = target.classList;
    let action = 'move';

    if (classList.contains('handler') && classList.contains('left')) {
      action = 'resizeLeft';
    } else if (classList.contains('handler') && classList.contains('right')) {
      action = 'resizeRight';
    }

    this[`_${action}`](renderingContext, shape, datum, dx, dy, target);
  }

  isTouchingSibling(renderingContext, shape, currentSegmentObj, nextSegmentObj, direction) {
    if (!nextSegmentObj) { return }

    // CONVENIENCE
    const { segmentValues, DIRECTION } = this;
    const { LEFT, RIGHT} = DIRECTION;

    const currentSegmentValues = segmentValues(renderingContext, shape, currentSegmentObj);
    const cSegStart = currentSegmentValues.startX;
    const cSegEnd = currentSegmentValues.endX;

    const nextSegmentValues = segmentValues(renderingContext, shape, nextSegmentObj);
    const nSegStart = nextSegmentValues.startX;
    const nSegEnd = nextSegmentValues.endX;

    if (direction === LEFT) {
      // Does the left edge of the current segment hit the right edge of the next segment
      return (cSegStart <= nSegEnd) ? true : false;
    }else if (direction === RIGHT) {
      // Does the right edge of the current segment hit the left edge of the next segment
      return (cSegEnd >= nSegStart) ? true : false;
    }

    return false;
  }

  connectedSiblings(renderingContext, shape, currentIndex, direction, siblings = []) {
    // CONVENIENCE
    const { DIRECTION, segmentsData, isTouchingSibling, connectedSiblings } = this;
    const { LEFT, RIGHT } = DIRECTION;

    const currentSegmentObj = this.segmentsData[currentIndex];

    // Exception cases : FIRST & LAST segments
    if (currentIndex === 0 && direction === LEFT ) { return [currentSegmentObj] }
    if (currentIndex === segmentsData.length - 1 && direction === RIGHT ) { return [currentSegmentObj] }

    const siblingIndex = (direction === LEFT) ? currentIndex - 1 : currentIndex + 1;
    const sibling = segmentsData[siblingIndex];

    // recursion :(
    if ( siblingIndex >= 0 && siblingIndex < segmentsData.length){
      connectedSiblings(renderingContext, shape, siblingIndex, direction, siblings)
    }

    const isTouching = isTouchingSibling(renderingContext, shape, currentSegmentObj, sibling, direction);
    if ( isTouching === true ){
      siblings.push(sibling);

      // TO DO: TRY SELECTING NEIGHBOR
      // Do all selected neighbors receive the edit callback when an event is triggered?
    }

    return siblings;
  }

  _move(renderingContext, shape, dataObj, dx, dy, target) {
    // convenience destructuring
    const { segmentIndex, DIRECTION, connectedSiblings } = this;
    const { LEFT, RIGHT } = DIRECTION;

    // Build Collision Train Array
    const currentIndex = segmentIndex(dataObj);
    const direction = (dx < 0) ? LEFT : RIGHT;
    const train = connectedSiblings(renderingContext, shape, currentIndex, direction);

    if (train.length === 0){
      train.push(dataObj);
    }

    // TODO: loop through and make sure siblings are set end to end

    train.forEach(sibling => {
      const x = renderingContext.timeToPixel(shape.x(sibling))
      const targetX = Math.max(x + dx, 0);
      shape.x(sibling, renderingContext.timeToPixel.invert(targetX));
    });
  }

  _resizeLeft(renderingContext, shape, datum, dx, dy, target) {
    // current values
    const x     = renderingContext.timeToPixel(shape.x(datum));
    const width = renderingContext.timeToPixel(shape.width(datum));
    // target values
    let maxTargetX  = x + width;
    let targetX     = x + dx < maxTargetX ? Math.max(x + dx, 0) : x;
    let targetWidth = targetX !== 0 ? Math.max(width - dx, 1) : width;

    shape.x(datum, renderingContext.timeToPixel.invert(targetX));
    shape.width(datum, renderingContext.timeToPixel.invert(targetWidth));
  }

  _resizeRight(renderingContext, shape, datum, dx, dy, target) {
    // current values
    const width = renderingContext.timeToPixel(shape.width(datum));
    // target values
    let targetWidth = Math.max(width + dx, 1);

    shape.width(datum, renderingContext.timeToPixel.invert(targetWidth));
  }
}

export default CollisionSegmentBehavior;

I found a solution to this by using the layer to select the segment after doing a collision detection. Will post my code as soon as I get a few minutes


bug: can't configure telescope extension project

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the exsiting issues of plugins related to this issue

Neovim version (nvim -v)
0.8.1
Operating system/version
Ubuntu 20.04
Describe the bug
I can't configure the telescope extension https://github.com/nvim-telescope/telescope-project.nvim
Steps To Reproduce

create /lua/plugins/telescope.lua

return {
  {
    "nvim-telescope/telescope.nvim",
    dependencies = {
      { "nvim-lua/plenary.nvim", lazy = true },
      {
        "nvim-telescope/telescope-project.nvim",
        config = function()
          require("telescope").load_extension("project")
        end,
      },
    },
    opts = {
      extensions = {
        project = {
          base_dirs = { { path = "~", max_depth = 4 } },
        },
      },
    },
  },
}

Expected Behavior
Telescope extension project is configured.
Repro
No response

It works with this repro.lua
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
        vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
        vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
        "folke/tokyonight.nvim",
        "folke/LazyVim",
        {
                "nvim-telescope/telescope.nvim",
                dependencies = {
                        { "nvim-lua/plenary.nvim" },
                        {
                                "nvim-telescope/telescope-project.nvim",
                                config = function()
                                        require("telescope").load_extension("project")
                                end,
                        },
                },
                cmd = "Telescope",
                keys = { { "<leader>sa", false } },
                config = function()
                        local telescope = require("telescope")
                        telescope.setup({
                                extensions = {
                                        project = {
                                                base_dirs = { { path = "~", max_depth = 4 } },
                                        },
                                },
                        })
                        telescope.load_extension("project")
                end,
        },
}
require("lazy").setup(plugins, {
        root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Is it incorrect to load telescope extensions like I did before? I got this from the documentation here: https://www.lazyvim.org/configuration/recipes#add-telescope-fzf-native

I have almost your configuration in the first post
  {
    "nvim-telescope/telescope.nvim",
    dependencies = {
      {
        "nvim-telescope/telescope-project.nvim",
        keys = {
          { "<C-p>", "<cmd>lua require'telescope'.extensions.project.project{}<cr>", desc = "Telescope Project" },
        },
        config = function()
          require("telescope").load_extension("project")
        end,
      },
    },
    opts = {
      extensions = {
        project = {
          base_dirs = {
            { path = "~/Desktop/Projects/", max_depth = 4 },
          },
        },
      },
    }
  }

and it works fine for me.

and it works fine for me.

I tested your config just now and it does not work for me :(
:Telescope project works, but it does not list any projects.

I did yes.

Did you just copy/paste my config? I changed the path variable to be where my projects are. Maybe you should set it to whatever you like?

Delete telescope-projects.txt and telescope-workspaces.txt and then start Neovim. telescope-workspaces.txt also gets created from the telescope-project extension so maybe that interferes with something?

Thanks for you help :) But I did the following before testing your config changes.
rm -rf ~/.local/share/nvim ~/.local/state/nvim ~/.cache/nvim

Doing so removes all the plugins from LazyVim as well. Did you run Lazy to install the necessary plugins again? If yes, then I don't know what else to tell you since the above config works just fine for me. Maybe you should go with the config that you posted before me, which seems to solve your problem.

Lazy automatically pulls the plugins. I will close as this solves my problem.

Since telescope-project depends on an option set to telescope, it indeed has to be loaded after telescope. So your fix for that seems fine

But if you set it as a dependency to telescope doesn't that mean that it's loaded after telescope. My config works just fine the LazyVim way without having to specify the config function with requires. Something else must be going on, but since he fixed it it's ok. Still the recipe for fzf in the docs can be applied in other telescope extensions as well. Also since the config function of the extension is require("telescope).load_extensions("project") doesn't that require for telescope to be loaded already? At least that's how I understand it but of course I may be wrong, so please feel free to correct me.

@dpetka2001 but looking at your config, if the first thing you do is run <c-p>, so if you didn't do any other telescope commands, then tat would lead to the projects plugin being loaded, which means:

it will internally require("telescope")
that will autoload the telescope plugin, and as such its config
so by the time the projects config runs, the telescope one would already have been set up

If you'd instead do something like Telescope, then the following would happen:

it will load telescope dependencies
the dep is projects, so that will load
projects will internally require("telescope")
but since we are already loading telescope, it will bail out and just continue
projects config will run
telescope config will run

I hope this makes more sense :)


KOGITO-8954: Modify samples to show zero problems in Serverless Logic Web Tools

https://issues.redhat.com/browse/KOGITO-8954

CC @jesuino

@adrielparedes can we merge this one?


Error: There was an error sending your trade offer.  Please try again later. (26)

I get all the time the error that I describe in the title of this ticket. The sentry file was created on April 30th, and of course there was enough time for SteamGuard to allow trades. I logged into the Steam application and tried to perform a manually trade and was successful. What's wrong? I attach the code below:
function makeTrade(tradeUser, urlToken, itemsToTrade) {
	inTrade = true;
	var trimTokenUrl = urlToken.split('&token=');
	var tradeAccesToken = trimTokenUrl[1];
	trade.loadPartnerInventory({
	    partnerSteamId: tradeUser,
	    appId: appid,
	    contextId: contextid
	}, function(err, items) {{
	      trade.makeOffer ({
	            partnerSteamId: tradeUser,
	            accessToken: tradeAccesToken,
	            itemsFromMe: [],
	            itemsFromThem: itemsToTrade,
	      }, function(err, response){
	            if (err) {
	              logger.error(err);
	            }
	      });
	    }
	});

I get all the information from database:

tradeUser is the steamID.
urlToken is the entire public trade url.
itemsToTrade is  an array of items which structure is that:
[ { appid: 730, contextid: 2, amount: 1, assetid: '469444882' } ]

Stack trace:
Error: There was an error sending your trade offer.  Please try again later. (26)
    at SteamTradeOffers.<anonymous> (/Users/*****/node_modules/steam-tradeoffers/index.js:427:18)
    at Request.self.callback (/Users/*****/node_modules/steam-tradeoffers/node_modules/request/request.js:368:22)
    at Request.emit (events.js:110:17)
    at Request.<anonymous> (/Users/*****/node_modules/steam-tradeoffers/node_modules/request/request.js:1219:14)
    at Request.emit (events.js:129:20)
    at IncomingMessage.<anonymous> (/Users/*****/node_modules/steam-tradeoffers/node_modules/request/request.js:1167:12)
    at IncomingMessage.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickCallback (node.js:355:11)

I cant find my fault. There's no way to get it run.
P.S.: I have no pending trade offers.

All of the items in itemsToTrade are tradable?

Ofcourse, it's there since the Steam account was created (more or less). I test with skins that are without any restriction.

I tried to do manually the trade by coding like this:
function makeTrade(tradeUser, urlToken, itemsToTrade) {
	trade.loadPartnerInventory({
	    partnerSteamId: 'Steam id as string',
	    appId: 730,
	    contextId: 2
	}, function(err, items) {{
	      trade.makeOffer ({
	            partnerSteamId: 'Steam id as string',
	            accessToken: 'access token as string',
	            itemsFromMe: [],
	            itemsFromThem: [ { appid: 730, contextid: 2, amount: 1, assetid: '469444882' } ],
	      }, function(err, response){
	            if (err) {
	              logger.error(err);
	            }
	      });
	    }
	});
}

But i get te same stack trace:
Error: There was an error sending your trade offer.  Please try again later. (26)
    at SteamTradeOffers.<anonymous> (/Users/diego/node_modules/steam-tradeoffers/index.js:427:18)
    at Request.self.callback (/Users/diego/node_modules/steam-tradeoffers/node_modules/request/request.js:368:22)
    at Request.emit (events.js:110:17)
    at Request.<anonymous> (/Users/diego/node_modules/steam-tradeoffers/node_modules/request/request.js:1219:14)
    at Request.emit (events.js:129:20)
    at IncomingMessage.<anonymous> (/Users/diego/node_modules/steam-tradeoffers/node_modules/request/request.js:1167:12)
    at IncomingMessage.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickCallback (node.js:355:11)

I have no idea what's happend.

As soon as I wrote the previous comment I realize what was my fault... :confounded:
When I set the assetid on items structure, I put the classid (WROOONG!! If API says that you must put the assetid, you must put assetid and no other stuff!!) :cold_sweat:
"332001318": {"id":"332001318","classid":"469444882","instanceid":"0","amount":"1","pos":191}

In this case, the assetid is 332001318 and isn't 469444882 as I supposed.
By the way, thank you for your time to try to solve my problem. I'll close this issue.


protoc-bundled plugin should support newer protoc versions

2.6.1 and 3.0.0 seem to be missing. Support for those would be great.

3.0.0 does not appear to be released in final form yet.  Could you have a look at the 2.6.1 binaries in #35 and verify that the relevant versions work for you?  Thanks!

https://github.com/comoyo/commons/pull/41 adds support for 3.0.0


Explain when self-hosting may be more appropriate from MeltanoData UI

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1961
Originally created by @DouweM on 2020-04-21 22:16:12

View 4 previous comments from the original issue on GitLab


Hyperion does not start automatically without a user login

[x] I confirm that this is an issue rather than a question.

Bug report
I am running the latest version of Hyperion.NG on my Home Assistant server on Debian 10. When the computer is started or restarted Hyperion.NG does not start automatically until I log in on the PC (using RDP or physically).
Steps to reproduce
I don't know i followed the installation guide
What is expected?
Auto start Hyperion.NG service so once the PC is restarted we can directly browse the url
What is actually happening?
When the computer is started or restarted Hyperion.NG does not start automatically until I log in on the PC (using RDP or physically).
System

Hyperion Server:

Build:           (HEAD detached at b1a4e95c) (Paulchen-Panther-975f969a/b1a4e95c-1626550299)
Build time:      Jul 17 2021 20:46:40
Git Remote:      https://github.com/hyperion-project/hyperion.ng
Version:         2.0.0-alpha.10
UI Lang:         en (BrowserLang: en-US)
UI Access:       default
Avail Capt:      v4l2,framebuffer,x11,xcb,qt
Database:        read/write

Hyperion Server OS:

Distribution:   Debian GNU/Linux 10 (buster)
Architecture:   x86_64
CPU Model:      Intel(R) Celeron(R) CPU G3900T @ 2.60GHz
CPU Type:       94
Kernel:         linux (4.19.0-17-amd64 (WS: 64))
Qt Version:     5.7.1
Python Version: 3.5.3
Browser:        Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36 Edg/94.0.992.38

I think it's the same issue as #1350
It sounds like, that you are not using a headless ubuntu installation. The service/autostart is only installed, when you run your system headless.

@N1c093  Is there any documentation on doing so? as there is only one command I found on how to install it.
Is there any way to upgrade the current installation into the headless mode or do I need to start fresh with it?

see #1478


Creating a cluster with kubeadm -- there should be a simple, straightforward quickstart.

Just wanted to give some feedback as a relatively experienced kubernetes operator with zero kubeadm experience. I'm very surprised at the approach that is taken within the document Creating A Cluster With kubeadm. It is extremely high-level to the point of vagueness. Yes there are a couple literal commands suggested to be run, but there is no workflow that actually involves creating a cluster. If you title a document, "Creating A Cluster With kubeadm" that document should in my opinion not be a general document about the potential ways to create a cluster, but instead culminate in the actual creation of a cluster. Whatever the case the kubeadm documentation is high-level and sprawling and yet offers no concrete document that just gets someone "up and running with a vanilla single or two-node cluster". Someone clearly put a lot of time into writing these documents, but as with 99% of official kubernetes documentation pragmatism would be much more valuable than scope. Decouple the man page stuff for something like api or configuration documentation. I realize it may be tempting to suggest that I myself rewrite this given that it is an open source project, though that is entirely beside the point. I am coming to this documentation as a first time user; I expect the last impression that the author wants to give is that the documentation requires studying to be useful -- that should not be the case and can come second. Someone has taken weeks I'm betting to write this documentation and that person is clearly a master of kubeadm. That person should evolve and come back and write a quickstart or else what's the point of any of it, frankly?

Hmm, I've used this page several times to walk through spinning up a cluster successfully. Are there specific sections or flows that you find lacking? You mention a couple general concepts, but this still kind of reads as "this should be better!!"

I read half the document word-for-word and then skimmed the rest. Hopefully
the juice comes in the second half? Either way: consider if the meat comes
after the vegetables? Normally this is considered backwards. Also: the
generality of the document is the catalyst for my thesis being, "this
should be better," as you put it. I'm not in the habit of rewriting someone
else's documentation. But...I will scrutinize the hell out of this and see
if a cluster pops out.
On Fri, Feb 23, 2024, 1:06 PM Sean McGinnis @.***>
wrote:

Hmm, I've used this page several times to walk through spinning up a
cluster successfully. Are there specific sections or flows that you find
lacking? You mention a couple general concepts, but this still kind of
reads as "this should be better!!"
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/45309#issuecomment-1961847506,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO4VO5TLQCM3JGKNOQ3MUN3YVDSCPAVCNFSM6AAAAABDXFP5B2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRHA2DONJQGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

What we have now could split into two explanations:

what's involved, generally, in cluster setup

how kubeadm fits into that story

a tutorial-like page about how to set up a multi node cluster with a stacked etc, 3 × n control plane nodes, m worker nodes

you would need to pick your own container runtime and network plugin, so one of the subtasks is to prepare for the work by picking something
we should also explain how to check that your cluster is happy and healthy
a “what's next” for this page should help you find separate advice about deploying optional but common add-ons, such as the metrics server

The tutorial I'm imagining is a largely manual walkthrough. There is third party documentation from the ecosystem but we don't document that, as (so far as I know) all of these tools are either aimed as local Kubernetes development, or are not part of Kubernetes.

/language en
/sig cluster-lifecycle
/frozen
We should do this
/retitle "Creating a cluster with kubeadm—there should be a simple, straightforward quickstart”
Even if we try hard, it won't be simple and straightforward, but we can do more than we have.

Someone has taken weeks I'm betting to write this documentation and that person is clearly a master of kubeadm.

I think this might be the work of more than one contributor, not the product of a single expert.

To move this work forward, a contributor can:

look at the page
identify actionable subtasks to help reshape the existing content
file a new separate issue for some or all of those actionable subtasks

@sftim okay here are the tasks:

rename Creating a cluster with kubeadm to Cluster Considerations or whatever makes it clear that the document is not a quickstart and is more trying to cover the various and numerous scenarios that any operator with servers on any platform using any os at any state may have to think about before using kubeadm.
create a quickstart document called kubeadm quickstart and then just literally paste the kubeadm cli STDOUT in it:

    │ KUBEADM │
    │ Easily bootstrap a secure Kubernetes cluster │

    │ Please give us feedback at: │
    │ https://github.com/kubernetes/kubeadm/issues │

Example usage:

    Create a two-machine cluster with one control-plane node
    (which controls the cluster), and one worker node
    (where your workloads, like Pods and Deployments run).

    │ On the first machine: │
    │ control-plane# kubeadm init │

    │ On the second machine: │
    │ worker# kubeadm join <arguments-returned-from-init> │

    You can then repeat the second step on as many other machines as you like.

The reason it is "hard" as you say above is because the document is conflating attempting to cover all various install scenarios, as well as get people up and running; another way to say this is that the document makes no assumptions. So there needs to be a document that makes a lot of assumptions. This document should be a quickstart. It is fine for a quickstart to assume that people are using yum/dnf or apt server os's, that they have a container runtime installed, it can just link to installing a cri plugin, etc. etc. That's why I was so shocked to see the kubeadm default menu -- THAT'S THE QUICKSTART! But who's ever going to find it there?

To move this work forward, a contributor can:

look at the page
identify actionable subtasks to help reshape the existing content - see https://github.com/kubernetes/website/issues/45309#issuecomment-1962366777 for a hint
file a new separate issue for some or all of those actionable subtasks

/triage accepted


Revisit an entity's "source"

Plan as of April 5:
Store creatorId and userAgent on entity def.
Store as many details as necessary in audit log on entity.create or entity.update event. That would include entity uuid, entity def id (or entity def version), and details like whether it was an api request or bulk file upload.

For an entity.update event, Frontend will need to have some way to connect the event to the associated diff. Maybe that's a reason to store the entity def version number, not just the internal entity def id.

For an entity.update event, Frontend will need to have some way to connect the event to the associated diff.

As discussed in #828, Frontend will be able to connect the event to the diff based on the order.

@ktuite and I chatted a little about the entity source today, and I wanted to mention two takeaways from that conversation.
Takeaway 1: We need to save information about purged submissions
We don't support individual submission deletion yet, but we do support form deletion. That means that a submission that created an entity can be soft-deleted (its form is in the trash), or it can be purged. When a form is purged, its name is saved in the actees table (in the purgedName column). We don't save information about a purged form's submissions. (That's mostly a good thing, because submission data can be PII.)
However, if an entity was created from a submission that has been deleted or purged, the release criteria call for showing the submission's instance ID. That means that if a submission created an entity, we need to save its instance ID somewhere if/when its form is purged. Because submissions aren't actees, that would probably have to be somewhere outside the actees table.
In the release criteria, I've also suggested that we show the name of the submission's form. Whether or not we decide to do that, that makes me think that when we save the instance ID of a purged submission, we should save alongside it the acteeId of its purged form. An instance ID by itself doesn't actually identify a submission: you also need to know its form. The form's acteeId would link to information about the purged form.
Takeaway 2: Frontend needs to know the source of the root version
The release criteria call for showing the instance name or ID of the "creating submission". I know we're planning to return the source of the current entity version in the entity response. However, I think what Frontend actually needs is the source of the root version. I don't think Frontend needs other information from the root version, so one option might be to add a top-level source property to the entity response to indicate the source of the root version (the source of the entity itself).
Frontend shows information about the creating submission in two places: the Basic Information section of the entity detail page and the entity activity feed. However, I'm happy to grab that information from one response and use it in multiple places on the entity detail page. For example, as long as the entity response includes the source of the root version, I don't think we need to store that information in the audit log as well (at least not for Frontend's sake).

#846 returns all the information that Frontend needs about the entity's source. I think it also addresses the two takeaways above.
Even if a submission is deleted or purged, its instance ID remains in the audit log. The actee ID of its form can also be found in the audit log. (I believe the form is the actee of submission events.)
I think we still have work to do for this issue. For example, we need to account for deleted submissions when returning the source property of an entity version. However, that would only be for the API: Frontend now has what it needs. Could we maybe get away with not returning a source property at all for .3, then come back to it when we work on CSV upload?


tensorflow.python.framework.errors_impl.FailedPreconditionError: Failed to remov e a directory: train

Hi,
I repeat the program on Tensorflow 1.2.0rc0, CPU version,
There is below hint,
How should I solve it ?
(C:\ProgramData\Anaconda3\envs\tensorflow) D:\AI\srez>python srez_main.py --run
train
2017-05-31 10:33:28.029651: W c:\tf_jenkins\home\workspace\nightly-win\device\cp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE instructions, but these are available on your m
achine and could speed up CPU computations.
2017-05-31 10:33:28.029651: W c:\tf_jenkins\home\workspace\nightly-win\device\cp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE2 instructions, but these are available on your
machine and could speed up CPU computations.
2017-05-31 10:33:28.029651: W c:\tf_jenkins\home\workspace\nightly-win\device\cp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE3 instructions, but these are available on your
machine and could speed up CPU computations.
2017-05-31 10:33:28.029651: W c:\tf_jenkins\home\workspace\nightly-win\device\cp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE4.1 instructions, but these are available on you
r machine and could speed up CPU computations.
2017-05-31 10:33:28.029651: W c:\tf_jenkins\home\workspace\nightly-win\device\cp
u\os\windows\tensorflow\core\platform\cpu_feature_guard.cc:45] The TensorFlow li
brary wasn't compiled to use SSE4.2 instructions, but these are available on you
r machine and could speed up CPU computations.
Traceback (most recent call last):
2017-05-31 10:33:28.123251: E c:\tf_jenkins\home\workspace\nightly-win\device\cp
u\os\windows\tensorflow\core\util\events_writer.cc:162] The events file train\ev
ents.out.tfevents.1496198008.PC has disappeared.
2017-05-31 10:33:28.123251: E c:\tf_jenkins\home\workspace\nightly-win\device\cp
u\os\windows\tensorflow\core\util\events_writer.cc:131] Failed to flush 1 events
to train\events.out.tfevents.1496198008.PC
File "srez_main.py", line 191, in
tf.app.run()
File "C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\py
thon\platform\app.py", line 48, in run
_sys.exit(main(_sys.argv[:1] + flags_passthrough))
File "srez_main.py", line 188, in main
_train()
File "srez_main.py", line 146, in _train
all_filenames = prepare_dirs(delete_train_dir=True)
File "srez_main.py", line 76, in prepare_dirs
tf.gfile.DeleteRecursively(FLAGS.train_dir)
File "C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\py
thon\lib\io\file_io.py", line 432, in delete_recursively
pywrap_tensorflow.DeleteRecursively(compat.as_bytes(dirname), status)
File "C:\ProgramData\Anaconda3\envs\tensorflow\lib\contextlib.py", line 66, in
exit
next(self.gen)
File "C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\tensorflow\py
thon\framework\errors_impl.py", line 466, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.FailedPreconditionError: Failed to remov
e a directory: train

See #28

that is fine, and running OK, thanks!


Is it possible to add reducers after the store is already initialized?

I am currently using redux trough ngRedux in an angular application. Instead of having the reducers in some reducers directory at the top level of the app, I would prefer to have them in their respective components. This means they would have to add themselves to the store. Is this somehow achievable?

@gitnik reducer hierarchy is not necessarily mapped 1:1 to the view hierarchy.
Regarding reducers for smart components. Redux does not care where the files are. You can have your reducer code placed alongside the rest of the smart component code, and import such reducers into the root reducer.
 I believe the best approach is to write a higher order reducer per such component, use them to produce "instance reducers" and composed those into smart component reducers.
Hope this helps.

Reference: Smart and Dumb Components

You can have your reducer code placed alongside the rest of the smart component code, and import such reducers into the root reducer.

That's exactly what I'm trying to avoid because then I will end with with import statements like this:
import fooReducer from 'modules/form/sections/quality/fooReducer'

You could rollup your reducers per component, and export a getReducers method that you can test for... it would take some manual curation and require you to put those methods at each stage...
import {getReducers} from '../components';

from there, components/index.js could simply combine the reducers for it's children, and so on...

That's exactly what I'm trying to avoid because then I will end up with import statements like this:
import fooReducer from 'modules/form/sections/quality/fooReducer'

What is the problem with this statement? It makes the dependency explicit. You can even put reducers in the same files as your components, and have parent components export their parent reducers, up to the root component. Then it's not really different from how you import child components.
If you really feel you must add them dynamically see this SO question. But I wouldn't recommend doing this unless you're actually using code splitting, as this complicates the simple ideas of Redux.

ok, thanks for your input everyone :+1: guess I'm going with the long import statements for now

Why should they be long? If you use relative paths it's all about how you group files by feature.

@gitnik did you ever find a solution for this? I also encapsulate my reducers/actions inside my components dirs for 'true' portability, now looking for a way to avoid the tedious component reducer import problem.

What is the problem with this statement? It makes the dependency explicit.
It's not a dependency until you need it. Dynamic = Independent. Currently if i have a big application and a Person store i would have to import lots of reducers and they would be processed every time i need something really specific. Adding and removing reducers would be the most professional way of working. Currently redux does not apply to big softwares

@zerobytes : I'm not sure why you say that.  FWIW, there's plenty of examples of dynamically adding reducers at runtime (see the articles listed here ), and there's also several existing libraries to help automate that process.


MIT license?

I notice on CRAN that this is listed as MIT, but in this repo there isn't the MIT license text.

Sure! Thanks!
On Sep 5, 2015 9:25 PM, "mtc2013"<EMAIL_ADDRESS>wrote:

I notice on CRAN that this is listed as MIT, but in this repo there isn't
the MIT license text. Are you open to a PR to place this into an MIT
license?
—
Reply to this email directly or view it on GitHub
https://github.com/terrytangyuan/dml/issues/1.

PR is welcomed!


Unable to see any metrics on grafana dashboard

After following your instructions, I am not able to see any metrics on the 'Istio Canary' dashboard within grafana.  I tried opening prometheus and running a query for istio_requests_total just to see the raw time series data, but there is nothing there. It appears that istio is not collecting any metrics? Or possibly that the load test is not actually sending any requests through the system?
Do I need to run any commands to initiate the load test?

Maybe istio-telemetry is in a crash loop? You cloud try to restart all pods in istio-system namespace and check the Mixer container logs in the telemetry pod.

I ran through all the troubleshooting steps documented by Istio here: https://istio.io/docs/ops/telemetry/missing-metrics/
Everything is running as they recommend, so I don't think there is a problem with mixer. It seems to me that the hey load test is maybe not ever starting? I don't know much about flagger or how this load test is supposed to be starting up? Any recommendations of how to verify this?

Any errors in Flagger logs?
I don't think this is related to Flagger since a similar setup runs on every commit in CircleCI as part of the Flagger e2e testing https://github.com/weaveworks/flagger/tree/master/test

I see this in the flagger logs:
{"level":"error","ts":"2019-07-10T03:20:01.474Z","caller":"flagger/main.go:137","msg":"Metrics server http://prometheus.istio-system:9090 unreachable Get http://prometheus.istio-system:9090/api/v1/status/flags: dial tcp: lookup prometheus.istio-system on <IP_ADDRESS>:53: no such host","stacktrace":"main.main\n\t/home/circleci/build/cmd/flagger/main.go:137\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"}

After restarting flagger I see that flagger was able to successfully connect to the prometheus service:
{"level":"info","ts":"2019-07-10T03:24:46.108Z","caller":"flagger/main.go:135","msg":"Connected to metrics server http://prometheus.istio-system:9090"}

So I'm guessing that flagger is starting up before the prometheus service has actually been created/started?
Is there a way to force flux to deploy flagger after prometheus has started?

This is not an issue, Flagger will retry the Prometheus connection when a canary analysis starts. Does the canary promotion works?

Yes, the canary promotion worked both before and after I restarted flagger.
Strangely, no metrics showed up on the grafana dashboard until after I restarted the flagger pod. That doesn't really make sense though because prometheus uses pull based collection, so restarting a pod should make any changes to what prometheus is doing (unless the initial discovery failed to discover the pod). The istio_requests_total metric used in the dashboard is reported by the istio-mesh prometheus job, though, and that I assume is not related to flagger.
I am ok with you closing this issue since the problem seems to be resolved for me now, unless you want any further information.

If Flagger canary analysis worked then the problem is with Grafana probably the same issue as #5

Yeah, that is likely my problem. Thanks for your help.


Erro installing Superscriptjs on dreamhost:

Trying to install superscriptjs on dreamhost vps with nodejs and mongodb installed, I receive these errors:
In this hosting I am using php 5.6, NODEJS version is v0.12.0, with mod security enabled:
http://wiki.dreamhost.com/Mod_security
and here the dreamhost instructions about nodejs setup:
http://wiki.dreamhost.com/Passenger
Here my failed installation:
[HOSTNAME]$ npm install --global superscript
npm ERR! tar.unpack untar error /home/anonymousfolder/.npm/superscript/0.9.1/package.tgz
npm ERR! Linux 3.1.9-vs<IP_ADDRESS>vs<IP_ADDRESS>+
npm ERR! argv "/usr/local/dh/nodejs/bin/node" "/usr/bin/npm" "install" "--global" "superscript"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! path /usr/local/dh/nodejs/lib/node_modules/superscript
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! Error: EACCES, mkdir '/usr/local/dh/nodejs/lib/node_modules/superscript'
npm ERR!     at Error (native)
npm ERR!  { [Error: EACCES, mkdir '/usr/local/dh/nodejs/lib/node_modules/superscript']
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   path: '/usr/local/dh/nodejs/lib/node_modules/superscript',
npm ERR!   fstream_type: 'Directory',
npm ERR!   fstream_path: '/usr/local/dh/nodejs/lib/node_modules/superscript',
npm ERR!   fstream_class: 'DirWriter',
npm ERR!   fstream_stack:
npm ERR!    [ '/usr/local/dh/nodejs/lib/node_modules/npm/node_modules/fstream/lib/dir-writer.js:36:23',
npm ERR!      '/usr/local/dh/nodejs/lib/node_modules/npm/node_modules/mkdirp/index.js:46:53',
npm ERR!      'FSReqWrap.oncomplete (fs.js:99:15)' ] }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/anonymousfolder/anonymousdomain.com/public/npm-debug.log
[HOSTNAME]$

It looks like Dreamhost will not allow you to install it global without using "SUDO" you might have to install it locally without the "--global" flag.

You can also tell npm where to install global packages like NPM_PACKAGES=/somewhere-I-can-write/npm-packages npm install --global superscript but you will have to provide that env variable again when running it with node.
That also works if you have a package that on npm install will try to install a dependency globally (I think I had this issue with superscript in the past), so if your non-global npm install does install in node_modules, you can force any global installation called in that process to be in the same folder like NPM_PACKAGES=./node_modules npm install superscript and you don't have to provide this variable again when running it.

Thanks! Adding the sudo users then it workes, Great!
Now I am going to install the web editor of superscriptjs: https://github.com/silentrob/superscript-editor
but what about Mongodb? When and for what I have to configurate it?

All right! I installed also the editor:
SuperScript Community Editor.
Listening at http://<IP_ADDRESS>:3000
Bot Name: testbot
    Switch or create a new bot by starting `BOT=<name> node app.js`

you might want to use a service like Digital Ocean, they have MEAN stack droplets pre-configured. so you won't have to worry about mongo etc.
dreamhost (I used them myself) seems much more old-school shared php hosting...

Thanks! Considering that Dreamhost is fully managed instead on Digital Ocean then I have to take care about the security by myself, and many more.. because it is not fully managed, and that is a big task that I skip with Dreamhost... I am also evaluating other webserver with nodejs, that are also free at the start, like: heroku.com, openshift.com, Nodejitsu, Microsoft Azure, Modulus.io.

I didn't realize Nodejitsu was still running after the GoDaddy aquisition. Any platform that dives you access to the VM is all you really need. I use Ec2 and they have a free tier to play with as well.

I used to work at DreamHost, and I recommend Digital Ocean (they're who all my stuff is currently hosted with). You get more options for operating systems with DO (whereas DreamHost is limited to just Debian, and they're probably still on Wheezy)... Digital Ocean gives you full access to the VPS, whereas DreamHost is really built around the idea of managing your system through their control panel. For example, I manually added a lot of users to a DreamHost server via the CLI (adduser, etc.) to find out later that my /etc/passwd and /etc/shadow files got wiped out overnight by DreamHost when their control panel system synced configs down to my server. You can configure a DreamHost VPS to be unmanaged (by creating a sudo user through the control panel first), but that process was pretty unintuitive.

:+1:


Can't use avatar button in react

I implement library to my project but have some problem.
       <LiveChatWidget             license="*****"             visibility="minimized"         />
But is show in my code like this =>

I need change to like this =>

Hello @Aryan-mor 👋
In order to change the appearance of the minimized Chat Widget and also overall adjust the look and feel of it, you need to configure it on your LiveChat account 🙂
This project allows you to seamlessly integrate the LiveChat Chat Widget into your project but its configuration and setup are still done as always inside LiveChat Agent App after signing into your account.
You can read more about it here: https://www.livechat.com/help/customize-your-chat/#appearance


Discrepancy between the paper and your README

The AP for the hard case is different in the paper and the README.
For example the 3d detection, in README it's 74.66 but in the paper you have 69.10 only.
The BEV AP for the hard case is also different.

I use a lower nms_score_threshold in this README. you can reproduce the 69.10 with pretrained model by changing nms_score_threshold in car.config to 0.4.

Thanks. Closing the issue.


tests: dma: fix error when suspend and resume not supported

update dma loop test to avoid error in the suspend/resume
testcase when the dma drivers does not provide the service.
The test_loop_suspend_resume function exits immediately
with transfer_count set to a oversized value, so that
dma is stopped and testcase ends properly.
Fixes https://github.com/zephyrproject-rtos/zephyr/issues/44106
Signed-off-by: Francois Ramu<EMAIL_ADDRESS>

@FRASTM see #43984

Test campaign passed on the stm32xx
test,arch,platform,status,extra_args,handler,handler_time,ram_size,rom_size
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_f746zg,passed,,na,5.27608060836792,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_wb55rg,passed,,na,4.607640981674194,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_g071rb,passed,,na,4.2939393520355225,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,stm32l562e_dk,passed,,na,5.861671209335327,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_g474re,passed,,na,4.631453037261963,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_wl55jc,passed,,na,6.1563029289245605,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,stm32f3_disco,passed,,na,5.721297025680542,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_f429zi,passed,,na,5.399385452270508,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_l152re,passed,,na,9.70708680152893,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_f091rc,passed,,na,5.150474786758423,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_f103rb,passed,,na,5.766777276992798,0,0
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,disco_l475_iot1,passed,,na,5.9741127490997314,0,0

There would be a message, but it should return TC_PASS https://github.com/zephyrproject-rtos/zephyr/pull/43984/files#diff-ebead0703869e01965e37503d35285f963630eebeb50b22fcbcaac7d51205f6bR268 if -ENOSYS is returned which should be the default if the function pointer is NULL
https://github.com/zephyrproject-rtos/zephyr/pull/43984/files#diff-ebead0703869e01965e37503d35285f963630eebeb50b22fcbcaac7d5

I see the issue I think, the isr is getting called right after irq_unlock() and before test case returns resulting in the zassert failing in the isr. I have a fix in the works

please try with my latest push, it works for me on stm32f3_disco

please try with my latest push, it works for me on stm32f3_disco

that works for me too, tested on the nucleo_wb55rg or  nucleo_h743zi  (with DMAMUX) aand nucleo_l476rg (no DMAMUX)

Let's keep the https://github.com/zephyrproject-rtos/zephyr/pull/43984 instead
to fix the https://github.com/zephyrproject-rtos/zephyr/issues/44106

During the tests/drivers/dma/loop_transfer/test_dma_m2m_loop, the immediately after the dma_start, the irq is pending before the dma suspend comes. The channel is disabled and irq flag are off when _isr_wrapper arrives.

I think its fair to bail on the ISR if its stopped

@FRASTM  this fix is in driver, so the PR title shall be changed to 'driver: dma'

changing commit (and PR) title
rebase

rebased on 005968a81

rebase on 48877f8bdcd92f7e14a72ab4c830989f15f1e884
change after review

Running test suite dma_m2m_loop_test
===================================================================
START - test_dma_m2m_loop
DMA memory to memory transfer started on DMAMUX_1
Preparing DMA Controller
this platform do not support the dma channel
Starting the transfer on channel 11 and waiting for 1 second
Each RX buffer should contain the full TX buffer string.

Finished: DMA
PASS - test_dma_m2m_loop in 0.609 seconds
===================================================================
START - test_dma_m2m_loop_suspend_resume
DMA memory to memory transfer started on DMAMUX_1
Preparing DMA Controller
this platform do not support the dma channel
Starting the transfer on channel 11 and waiting for 1 second
suspend not supported PASS - test_dma_m2m_loop_suspend_resume in 0.19 seconds
===================================================================
Test suite dma_m2m_loop_test succeeded
===================================================================
RunID: a423c9eab27d9d8cd3fd5372fd6e0605
PROJECT EXECUTION SUCCESSFUL

tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_f746zg,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_wb55rg,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,stm32l562e_dk,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_g474re,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_wl55jc,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,stm32f3_disco,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_f429zi,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_l152re,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_f091rc,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,nucleo_f103rb,passed,
tests/drivers/dma/loop_transfer/drivers.dma.loop_transfer,arm,disco_l475_iot1,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,nucleo_f746zg,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,nucleo_wb55rg,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,stm32l562e_dk,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,nucleo_g474re,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,nucleo_wl55jc,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,stm32f3_disco,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,nucleo_f429zi,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,nucleo_l152re,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,nucleo_f091rc,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,nucleo_f103rb,passed,
tests/drivers/dma/chan_blen_transfer/drivers.dma.chan_blen_transfer,arm,disco_l475_iot1,passed,

@teburd Would you mind having another look ?

This PR has been set to DNM because it makes the stm32U5 trig DMA interrupt endlessly

Let me know, happy to accept the patch if it solves problems for st, sorry I missed the mention above

@erwango @gmarull please take a look


Make install ERROR Error response from daemon is not running

Hi,
I have a problem when install RasaGPT == make install. I using window 11
I also change  rasa/rasa:latest and add  USER root to RasaGPT\app\rasa\actions and  user: "root:root" to rasa-core, rasa-actions , 'rasa-credentials'.
I almost done but found error
make[2]: Leaving directory 'C:/Users/maidu/RasaGPT'
Error response from daemon: Container aa9703a170e87b8d3e0cfce416c45e4ffda368c951f889674ee5aa0f4dc85c89 is not running
make[1]: *** [Makefile:286: rasa-train] Error 1
make[1]: Leaving directory 'C:/Users/maidu/RasaGPT'
make: *** [Makefile:57: install] Error 2
Please help me !
Thanks.

I'm assuming it's the rasa-core container not running. You can look into you docker desktop and click on the container named "chat_rasa_core ", you should be able to see the logs on why it exited.

Thank you for taking the time to help me,
But when i see in docker it shows up

2023-11-21 03:23:13 chat_rasa_actions      | /opt/venv/lib/python3.10/site-packages/rasa/core/tracker_store.py:1042: MovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings.  Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
2023-11-21 03:23:13 chat_rasa_actions      |   Base: DeclarativeMeta = declarative_base()
2023-11-21 03:23:14 chat_rasa_actions      | 2023-11-20 20:23:14 DEBUG    rasa.telemetry  - Could not read telemetry settings from configuration file: Configuration 'metrics' key not found.
2023-11-21 03:23:14 chat_rasa_actions      | /opt/venv/lib/python3.10/site-packages/pkg_resources/__init__.py:121: DeprecationWarning: pkg_resources is deprecated as an API
2023-11-21 03:23:14 chat_rasa_actions      |   warnings.warn("pkg_resources is deprecated as an API", DeprecationWarning)
2023-11-21 03:23:14 chat_rasa_actions      | /opt/venv/lib/python3.10/site-packages/pkg_resources/__init__.py:2870: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('google')`.
2023-11-21 03:23:14 chat_rasa_actions      | Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
2023-11-21 03:23:14 chat_rasa_actions      |   declare_namespace(pkg)
2023-11-21 03:23:14 chat_rasa_actions      | /opt/venv/lib/python3.10/site-packages/pkg_resources/__init__.py:2870: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('mpl_toolkits')`.
2023-11-21 03:23:14 chat_rasa_actions      | Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
2023-11-21 03:23:14 chat_rasa_actions      |   declare_namespace(pkg)
2023-11-21 03:23:14 chat_rasa_actions      | /opt/venv/lib/python3.10/site-packages/pkg_resources/__init__.py:2870: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('ruamel')`.
2023-11-21 03:23:14 chat_rasa_actions      | Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
2023-11-21 03:23:14 chat_rasa_actions      |   declare_namespace(pkg)
2023-11-21 03:23:14 chat_rasa_actions      | /opt/venv/lib/python3.10/site-packages/pkg_resources/__init__.py:2870: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('ruamel.yaml')`.
2023-11-21 03:23:14 chat_rasa_actions      | Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
2023-11-21 03:23:14 chat_rasa_actions      |   declare_namespace(pkg)
2023-11-21 03:23:14 chat_rasa_actions      | <frozen importlib._bootstrap>:283: DeprecationWarning: the load_module() method is deprecated and slated for removal in Python 3.12; use exec_module() instead
2023-11-21 03:23:14 chat_rasa_actions      | /opt/venv/lib/python3.10/site-packages/sanic_cors/extension.py:39: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
2023-11-21 03:23:14 chat_rasa_actions      |   SANIC_VERSION = LooseVersion(sanic_version)
2023-11-21 03:23:14 chat_rasa_actions      | 2023-11-20 20:23:14 INFO     rasa_sdk.endpoint  - Starting action endpoint server...
2023-11-21 03:23:14 chat_rasa_actions      | 2023-11-20 20:23:14 INFO     rasa_sdk.executor  - Registered function for 'action_gpt_fallback'.
2023-11-21 03:23:14 chat_rasa_actions      | 2023-11-20 20:23:14 INFO     rasa_sdk.endpoint  - Starting plugins...
2023-11-21 03:23:14 chat_rasa_actions      | 2023-11-20 20:23:14 INFO     rasa_sdk.plugin  - No plugins found
2023-11-21 03:23:14 chat_rasa_actions      | Traceback (most recent call last):
2023-11-21 03:23:14 chat_rasa_actions      |   File "/opt/venv/lib/python3.10/site-packages/rasa_sdk/plugin.py", line 26, in _discover_plugins
2023-11-21 03:23:14 chat_rasa_actions      |     import rasa_sdk_plugins
2023-11-21 03:23:14 chat_rasa_actions      | ModuleNotFoundError: No module named 'rasa_sdk_plugins'
2023-11-21 03:23:14 chat_rasa_actions      | 2023-11-20 20:23:14 INFO     rasa_sdk.endpoint  - Action endpoint is up and running on http://<IP_ADDRESS>:5055
2023-11-21 03:23:14 chat_rasa_actions      | 2023-11-20 20:23:14 DEBUG    rasa_sdk.utils  - Using the default number of Sanic workers (1).

I think bug it's No module named 'rasa_sdk_plugins', i tried installing rasa_sdk manually with pip install rasa_sdk  but when I used the make install command again it still didn't work.
If you know what the error is, please help me,Thanks.

the rasa_sdk is installed in its own docker environment/container, so the rasa_sdk you installed manually is not being used in its docker container. However, the main issue here is presumably the problem with rasa_sdk itself. I tried searching online and it seems like the most reliable solution is to downgrade rasa_sdk to version 3.5 (presumably rasa_sdk 3.6 is being installed with the original settings). So you have to modify the pip install line in Docker file of rasa-actions to something like this:
RUN pip install python-dotenv rasa-sdk==3.5.0 requests

you might have to run 'make purge' instead of 'make install'.
I'm just started learning how to use docker these few days trying to get this repo working and am also facing the same problem as you do, so not sure if my solution will work lol.

the rasa_sdk is installed in its own docker environment/container, so the rasa_sdk you installed manually is not being used in its docker container. However, the main issue here is presumably the problem with rasa_sdk itself. I tried searching online and it seems like the most reliable solution is to downgrade rasa_sdk to version 3.5 (presumably rasa_sdk 3.6 is being installed with the original settings). So you have to modify the pip install line in Docker file of rasa-actions to something like this:
RUN pip install python-dotenv rasa-sdk==3.5.0 requests

you might have to run 'make purge' instead of 'make install'. I'm just started learning how to use docker these few days trying to get this repo working and am also facing the same problem as you do, so not sure if my solution will work lol.

Thanks, It's work
Your help is very helpful to me


Add refresh configure feature

Keep menu tab selected when hiding the left side bar
Split the map initialization into two phases to resolve the race
condition between fetching layer list and initialize map layers

init map without layers
add active layers(default or saved)
Add new property 'scope',which specify the menus the tool can be in, to interactive tool
Move edit method to map component and rename to editResource, because this method is common and can be used by tracking and annotation component.

This change is

Reviewed 16 of 16 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


[SPARK-42668][SS][FOLLOW-UP] Do not add file scheme to the Windows path

What changes were proposed in this pull request?
This PR is a followup of https://github.com/apache/spark/pull/40273 that avoids adding file:// into Windows path.
Why are the changes needed?
To fix the broken AppVeyor build
== Failed ======================================================================
-- 1. Error ('test_streaming.R:55'): read.stream, write.stream, awaitTermination
Error: Error in start : org.apache.hadoop.HadoopIllegalArgumentException: Unsupported name: has scheme but relative path-part
...

See also https://ci.appveyor.com/project/ApacheSoftwareFoundation/spark/builds/46451196
Does this PR introduce any user-facing change?
No to end users because the change has not been released out yet.
How was this patch tested?
AppVeyor build on windows.

Thanks! Merging to master.


Consider eliminating MIG resource requests/limits and MIG capacity changes

InstaSlice is controlling the pod placement (via org.instaslice resources or possibly node selectors), the MIG slice attribution to the container (via the injection of the NVIDIA_VISIBLE_DEVICES env variable into the container spec), as well as the timing of the deployment of the pod (via its scheduling gate). Therefore, there is no need for the scheduler and the kubelet to account for MIG resources such as nvidia.com/mig-1g.5gb. For instance, a pod spec such as the following will be scheduled and running on its intended MIG slice even with the MIG resource limit commented out:
apiVersion: v1
kind: Pod
metadata:
  name: sample-pod
spec:
  containers:
  - name: vectoradd
    image: "quay.io/tardieu/vectoradd:0.1.0"
    resources:
       limits:
        org.instaslice/17b63565-c7a8-489d-8491-d9a165ad4745: 1
#        nvidia.com/mig-1g.5gb: 1
    env:
    - name: NVIDIA_VISIBLE_DEVICES
      value: MIG-a8b44796-6f4a-5042-bcc8-d7648b083592

Dynamically controlling the MIG slice capacity of the node is therefore unecessary. Moreover, we have observed in practice that dynamically modifying the node capacity (capacity and/or allocatable capacity) is slow and brittle leading to recurring pod scheduling failures.

Overriding the MIG slice capacity of the node even just once, for instance at InstaSlice startup time, is also fundamentally brittle as this capacity is normally managed by the GPU operator. We have no guarantee at this point that any update we would make to this capacity will not eventually create a conflict with the GPU operator or a subsequent release of the GPU operator.

As a result, we should consider:

deleting the MIG resource requests and limits from the container spec in the InstaSlice webhook,
eliminating the MIG node capacity adjustment from the InstaSlice code altogether.

By combining this change with #101, we can completely eliminate dynamic node capacity adjustments making InstaSlice more robust and significantly faster.

Solved by #141


My input mode always in text mode

I try to speak with Jarvis, however nothing happen . Only when I type the instruction in text, jarvis do the tas

k

Have you tried to change the input mode? By default is text. Write change settings, or simple "settings" as input and you can on the fly enable the voice commands

Thank you for your response. Yeah, I tried change the input mode by editing Jarvis/src/jarvis/jarvis/setting.py before yet nothing happen.
But now its working using you guide. Thank you again!!


Package Create with Skeleton Image Shows Inaccurate Progress

Environment
Device and OS: MacOS
App version: v0.32.1
Kubernetes distro being used: N/A
Other:
Steps to reproduce

Have a component that uses the OCI skeleton in a zarf.yaml (example: https://github.com/radiusmethod/zarf-init-bigbang/blob/main/zarf.yaml)
Run zarf package create
Observe the progress bar while pulling images show a progress bar that doesn't really make sense

Expected result
The progress bar shows something that mathematically makes sense.
Actual Result
The progress bar shows a progress that is greater than the target.
Visual Proof (screenshots, videos, text, etc)

Severity/Priority
Low
Additional Context
Add any other context or screenshots about the technical debt here.

Fixed by @AustinAbro321 in #2235


invalid_client using OAuth2

Steps to reproduce:

setup a an app
create a oauth2 credentials
google-drive-ocamlfuse -id foo.apps.googleusercontent.com -secret bar -headless
open the url / paste the code

Result:
Cannot retrieve auth tokens.
Failure("Unexpected error response: {\n  \"error\": \"invalid_client\",\n  \"error_description\": \"Unauthorized\"\n}")`

Documentation about Authorization says:

You can create OAuth2 credentials from the Google APIs Console. Here you can find how to create a new application and here how to set up OAuth 2.0 credentials. When activating APIs, you must select the Drive API. When creating a new client ID, you must select "Installed applications" as Application type and "Other" as Installed application type (Redirect URI should be urn:ietf:wg:oauth:2.0:oob). Check that Drive API is among the Enabled APIs of your Developers Console.

But when creating oauth2 credentials we are not asked for "Redirect URI" (anymore) nor are we given the choice of "Other" (only "Desktop") + the referenced links of documentation are broken.
Is is still possible to google-drive-ocamlfuse with what is offered by console.developers.google.com nowadays?

Have you tried with this guide? Sorry that the info are not up to date.

Strangely enough, I was able to make it work on my local machine. Then I synced the config & state files to the remote server and got it working there too.
Closing for now & sorry for the noise.


New spacing

Better distribution of dimensions / measures spacing

@asherbitter I think some constants went out of sync here but it is cool, I am going to merge it and fix in master.

lol wrong button.


Render markdown inside an HTML tag

   ![Alt](http://example.com/image.jpg)

does not become

Is this is an intentional decision on your part? If so, please could you point me to the section of the library which I can alter to get this functionality?

That's a commonmark parser, and it follows specification.
http://spec.commonmark.org/0.21/#html-blocks
There are no good ways to mix inline content with html blocks. Your inline markdown will be wrapped to paragraphs.

Thanks for the prompt response.
When you say 'that's a commonmark parser,' do you mean I should be looking for a commonmark parser to accomplish this?
The reason I ask is that running that mixture of HTML and markdown through chjj/marked produces that output. However, marked lacks other features I'd like, notably footnotes...

I gave you link to specification, that describes this parser behaviour. Read it to investigate if your requirement can be satisfied or not. Markup-related questions should be asked at commonmark forum.

Ah I see – I misunderstood your response. Thank you.

Am I mad or has this behavior changed in the latest CommonMark spec?
https://spec.commonmark.org/0.28/#raw-html


[NG] Angular rebranding changes

Angular2 to Angular
Signed-off-by: Chris Ha<EMAIL_ADDRESS>

Change "Angular 2" to "Angular" with b8b266b

LGTM. @hippee-lee , can you review? I'll add my approval if this meets yours.


Rybrande/error page copyable

The core ask here is to add an area on the error page where it's easy to copy the stack-trace.
However, in order to do that in a sane way we needed to fix up the PageGenerator utility to work with new versions of Razor, and while we were at it we made it build the pages in the makefile so we never get back to a state of quietly failing to generate those.
The View/*.cs changes are all generated by the above process.

Hi @ryanbrandenburg, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Screenshot?

@Tratcher here's a screenshot.

All better?

I'm gonna go with :shipit: !


setIsFlipped not called

Hi,
I'm trying to use the setIsFlipped function, but for some reason, it does not get called when I try to run it. Thoughts?
I implemented it just like in the example you provided in the README.

Hey!
So I've been testing it using storybook and its working fine but its not working in an actual react project. I'll look into it and update the library soon.

It's fixed now. Thanks for bringing this to my attention.


Add Edit on GitHub to all pages

This should encourage more people to contribute and ease proofreading.

This is easily solved on GitBook.


Omnitool fixes

About the PR
Fix #11203
Lattice cutting was easy. I added new optional field for signal linker. It checks if linker has pulsing capability.
Screenshots

Changelog

:cl:

fix: Omnitool can cut lattice and pry unpowered doors

you might want to update the omnitool utility artifact effect as well

you might want to update the omnitool utility artifact effect as well

Done


31 Errors???


[Bug/Optimisation] slow startup with many block variants

seems there is a significant slowdown of loading/startup of the game when large numbers of blocks are present in the pack (things like "Chipped" and "Chisel" that add many new building blocks). i am unsure if this is something you can fix or not but if you are able to verify and fix this it'd be great. totally understandable if you cant as its not gamebreaking. im used to slow load times from forge so this is still faster than that XD

This is not a problem with open simple frames, the amount of blockstates I have never goes up all the states present are present in every version based of the config, I dont think OSF drastically slows the game in that way, or at least, only by a set amount if it does, is it specfically OSF you have isolated to be causing lag?

it is as far as i can tell it is OSF. i assume its just janky minecraft being janky. i also admit i didn't do an objectively rigerous test and simply compared it between my pack and a standalone instance as a "control". i can do more testing at a later time if you like, unless you are able to recreate the "issue" yourself. it seems to be all happening in the "pre launch" stage (after pressing play/launch but before the minecraft window pops up) on prism launcher so its also possible its doing something extra/different.

basically OSF has a set number of blockstates - this never changes theoretically, the idea is there are 100 texture states and blocks are assigned to those texture states as needed, there should be no problem with other mods as OSF only cares on right or left clicking - sorry for the long time to respond, Im going to close this issue for the time being, but if you do end up doing some testing, please let me know!


y before x - for plotting

Pull Request
Description
put y before x, when ordering nwp data
Fixes #
How Has This Been Tested?
unittests

[ ] Yes

If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?
I dont think they do

[ ] Yes

Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #590 (d49060a) into main (9561bed) will decrease coverage by 1.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #590      +/-   ##
==========================================
- Coverage   93.60%   92.56%   -1.05%
==========================================
  Files          45       45
  Lines        2878     2878
==========================================
- Hits         2694     2664      -30
- Misses        184      214      +30

Impacted Files
Coverage Δ

nowcasting_dataset/data_sources/nwp/nwp_model.py
100.00% <100.00%> (ø)

nowcasting_dataset/data_sources/data_source.py
73.93% <0.00%> (-15.76%)
:arrow_down:

nowcasting_dataset/filesystem/utils.py
93.75% <0.00%> (-5.00%)
:arrow_down:

Continue to review full report at Codecov.

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


Applies formatting that should have been in from the start

Danke. These two files keep showing up and I'm trying to keep my commits clean :(


Review scaling out metric for DNS cluster

Context:
Ahead of the PDNS switch over we need to discuss the current configuration and provision of containers for DNS. We need to decide how many containers are needed and the scaling out configuration for this.
We need to also assess if we need to add any additional metrics for scaling out.
This ticket is dependent on the DNS testing ticket.
This ticket has been spun off from ticket 182 where we encountered DNS errors.
We saw a number of unhealthy containers and the service should have auto scaled to prevent issues. Following investigations into the issue the average was being used (this needs to change) and we need to review the scaling out metrics for DNS clusters.

Hey team! Please add your planning poker estimate with Zenhub @juddin927 @satishgummadellimoj

Please add your planning poker estimate with Zenhub @smjmoj

Reviewed the cluster scaling config which is currently only using CPU metric to scale up, I suggest we also add memory as a scaling up metric too.

Could be a good introductory ticket for James

I think I have discovered a misconfiguration that attributed to the outage on the 15th August 2023. (https://app.zenhub.com/workspaces/nvvs-devops-622a0b371800e400133bb924/issues/gh/ministryofjustice/staff-device-dns-server/182)
Reviewing all the statics I conclude the reason for the outage was due to an increase in traffic between the hours of 12:00-14:00 on the 15 of August.
As a result, many of the ECS tasks got marked as unhealthy causing them to get shutdown.
Private Zenhub Image
After reading this AWS article: https://repost.aws/knowledge-center/elb-ecs-tasks-improperly-replaced
I believe we need to up the "Health check grace period" (Currently set at 0). This will give the service a grace period, to scale prior to instantly shutting down the containers.

UPDATE: Health check grace period is actually only on initiation of the task. "The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. " --health-check-grace-period-seconds (https://docs.aws.amazon.com/cli/latest/reference/ecs/update-service.html)
This means its unlikely this parameter, that attributed to the outage.

This will remain blocked until 444 is completed

This will remain blocked until 444 is completed

Looking at the history, now the scaling out metric has been added, we are scaling our ECS clusters successfully.
Private Zenhub Image
The graph shows a scale out occurring in the morning due to higher volumes of requests.
Looking at CPU statistics, it does show we spike at 100% during high traffic times, however this minor impact to availability is acceptable due to it being a DNS service.
[Private Zenhub Image (https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBOEZTQVE9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--ae32421a431f8f2b539a78fb0f52d4ad832794f7/image.png)
This will need to be continually reviewed when we start onboarding new clients to ensure we don't see severe service dedication with higher volumes of traffic.


C# tutorials - hello world

Create a basic Hello World tutorial for developers new to C#.
Tutorials should include one or more code examples, each example should also show expected output and should include an explanation of the code where it isn't obvious. Examples shouldn't be dependent on a specific IDE or target platform.

If this is still needed please assign to me and I will work on it. cc @BethMassi

Done!

Thanks!

Hi, everyone!
I would like to start contribuiting on the .NET Core documentation and I was wondering (not sure if this is the right issue for it, but anyway) wether we might use some code and documentation I have already developed for introducing C# to newer audiences - It is a separate repository with various examples and documentation..
Let me know wether we can use this in any way (I'm surely open to modifications of any kind) or wether I can start creating some new materials.
Thanks!

@BillWagner PR open

@tsolarin I see that. I will review it later today.

Duplicate of #942


Nesting ScrollView scrolling behavior

Issue on macOS with ScrollView nested in ScrollView.
Inner scroll view preventing outer Scrollview from scrolling if scrollwheel event happens in inner ScrollView.
Manfiests in RNTester FlatList and SectionList.
Regression.

Only the outer scroll view works I am trying to use both horizontal and vertical scroll but it's not working.
Please fix this issue as well.

Is this ever get fixed?