npm install Cannot find module '../src/app/store/createDevStore

last commit:
commit 04337c6e7476f54d19bd5c6725420787d89f13ed
Author: Zalmoxisus<EMAIL_ADDRESS>Date:   Fri Sep 16 12:07:01 2016 +0300

    Remove React Router till v4

log
~/Projects/remotedev-app on  master ⌚ 17:32:15
$ npm i
npm WARN deprecated<EMAIL_ADDRESS>Critical security bug fixed in v7.0.0 - read more at https://github.com/electron-userland/electron-packager/issues/333
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>Deprecated, use jstransformer
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

><EMAIL_ADDRESS>install /Users/name/Projects/remotedev-app/node_modules/macos-alias
> node-gyp rebuild

  CXX(target) Release/obj.target/volume/src/volume.o
  SOLINK_MODULE(target) Release/volume.node

><EMAIL_ADDRESS>install /Users/name/Projects/remotedev-app/node_modules/fsevents
> node-pre-gyp install --fallback-to-build

[fsevents] Success: "/Users/name/Projects/remotedev-app/node_modules/fsevents/lib/binding/Release/node-v47-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

><EMAIL_ADDRESS>install /Users/name/Projects/remotedev-app/node_modules/fs-xattr
> node-gyp rebuild

  CXX(target) Release/obj.target/xattr/src/async.o
  CXX(target) Release/obj.target/xattr/src/error.o
  CXX(target) Release/obj.target/xattr/src/sync.o
  CXX(target) Release/obj.target/xattr/src/util.o
  CXX(target) Release/obj.target/xattr/src/xattr.o
  SOLINK_MODULE(target) Release/xattr.node

><EMAIL_ADDRESS>install /Users/name/Projects/remotedev-app/node_modules/chromedriver
> node install.js

Downloading http://chromedriver.storage.googleapis.com/2.24/chromedriver_mac64.zip
Saving to /var/folders/n3/4m0c5s1s5b93mp670k2l6rq80000gn/T/chromedriver/chromedriver_mac64.zip
Receiving...
Received 783K...
Received 1577K...
Received 2360K...
Received 3149K...
Received 3944K...
Received 4484K total.
Extracting zip contents
Copying to target path /Users/name/Projects/remotedev-app/node_modules/chromedriver/lib/chromedriver
Fixing file permissions
Done. ChromeDriver binary available at /Users/name/Projects/remotedev-app/node_modules/chromedriver/lib/chromedriver/chromedriver

><EMAIL_ADDRESS>postinstall /Users/name/Projects/remotedev-app/node_modules/electron-prebuilt
> node install.js

Downloading electron-v0.36.12-darwin-x64.zip
[============================================>] 100.0% of 40.52 MB (527.9 kB/s)

><EMAIL_ADDRESS>prepublish /Users/name/Projects/remotedev-app
> eslint ./src/app && npm run test && npm run build && npm run build:umd && npm run build:umd:min

><EMAIL_ADDRESS>test /Users/name/Projects/remotedev-app
> BABEL_ENV=test mocha --require test/setup.js --recursive test

module.js:341
    throw err;
    ^

Error: Cannot find module '../src/app/store/createDevStore'
    at Function.Module._resolveFilename (module.js:339:15)
    at Function.Module._load (module.js:290:25)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/name/Projects/remotedev-app/test/index.spec.js:4:1)
    at Module._compile (module.js:413:34)
    at loader (/Users/name/Projects/remotedev-app/node_modules/babel-register/lib/node.js:146:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/name/Projects/remotedev-app/node_modules/babel-register/lib/node.js:156:7)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at /Users/name/Projects/remotedev-app/node_modules/mocha/lib/mocha.js:220:27
    at Array.forEach (native)
    at Mocha.loadFiles (/Users/name/Projects/remotedev-app/node_modules/mocha/lib/mocha.js:217:14)
    at Mocha.run (/Users/name/Projects/remotedev-app/node_modules/mocha/lib/mocha.js:469:10)
    at Object.<anonymous> (/Users/name/Projects/remotedev-app/node_modules/mocha/bin/_mocha:404:18)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module.runMain (module.js:447:10)
    at startup (node.js:148:18)
    at node.js:405:3

npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node5/5.12.0/bin/node" "/usr/local/bin/npm" "run" "test"
npm ERR! node v5.12.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>test: `BABEL_ENV=test mocha --require test/setup.js --recursive test`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script 'BABEL_ENV=test mocha --require test/setup.js --recursive test'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the remotedev-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     BABEL_ENV=test mocha --require test/setup.js --recursive test
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs remotedev-app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls remotedev-app
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/name/Projects/remotedev-app/npm-debug.log

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node5/5.12.0/bin/node" "/usr/local/bin/npm" "i"
npm ERR! node v5.12.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: `eslint ./src/app && npm run test && npm run build && npm run build:umd && npm run build:umd:min`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'eslint ./src/app && npm run test && npm run build && npm run build:umd && npm run build:umd:min'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the remotedev-app package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     eslint ./src/app && npm run test && npm run build && npm run build:umd && npm run build:umd:min
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs remotedev-app
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls remotedev-app
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/name/Projects/remotedev-app/npm-debug.log

sorry, I forgot that master branch is not required to be stable

@AveVlad, thanks for the report. Yes, I forgot to remove this unused import in tests. Fixed.

thanks)


Contributed keybinding affects interactive input field even when another extension's controller is being used

Issue Type: Bug
Related to #9037
When the interactive window was created by another extension and uses a controller (kernel) from that extension, the interactive input window nevertheless reports Shift+Enter (I am on Windows) as the shortcut for running the code. The standard shortcut is Control+Enter, and this reappears after disabling the Jupyter extension.

Extension version: 2022.1.1201831736
VS Code version: Code 1.64.2 (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:02:28.252Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

Now PR https://github.com/microsoft/vscode/pull/143163 has been merged I think this can be fixed.

Turns out that to fix this we also need https://github.com/microsoft/vscode/pull/143211 which I just submitted.


Make language version optional in config, up default to 755

Resolves #1562 .
There are some whitespace inconsistencies when I run the schema script. I will undo them, but I'd like to know the cause - I did a fresh clone just to be sure and they still appear.

also see https://github.com/abaplint/abaplint/issues/1139

I'd like the script to align the whitespace but 🤷♂

It's one of my predictions that the world will end when an important enough newline is lost somewhere and everything will break. But probably not here.

thanks 👍

2.63.2 published


[Docker] - Rasa init error

Rasa version:
Latest (1.4.1) - See on Docker Hub
Docker & docker-compose versions:
Docker version 19.03.4, build 9013bf583a
docker-compose version 1.24.1, build 4667896b
Operating system (windows, osx, ...):
Ubuntu 18.04.3 LTS
Issue:
With a brand new installation of Docker, dating from the day, it is impossible to launch rasa commands (init, train_nlu, ...) via Docker as described in the docs.
I tried with an empty current directory and a non-empty current directory (where volume is mounted) : the result is the same, leading to the error below.
I am connected as root, so the problem is not due to rights or anything else (about ten other diverse containers are currently working without any problem on the same machine)
Note: I have never encountered this problem with previous versions of the rasa:latest and rasa_latest-full images.
Error (including full traceback):
root@xyz:/path/to/my/project# docker run -v $(pwd):/app rasa/rasa:latest init --no-prompt
Unable to find image 'rasa/rasa:latest' locally
latest: Pulling from rasa/rasa
[...]
Status: Downloaded newer image for rasa/rasa:latest
Warning: Output is not to a terminal (fd=1).
Warning: Input is not to a terminal (fd=0).
Welcome to Rasa! 🤖

To get started quickly, an initial project will be created.
If you need some help, check out the documentation at https://rasa.com/docs/rasa.

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/distutils/dir_util.py", line 70, in mkpath
    os.mkdir(head, mode)
PermissionError: [Errno 13] Permission denied: '__pycache__'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/build/bin/rasa", line 11, in <module>
    load_entry_point('rasa==1.5.0a1', 'console_scripts', 'rasa')()
  File "/build/lib/python3.6/site-packages/rasa/__main__.py", line 76, in main
    cmdline_arguments.func(cmdline_arguments)
  File "/build/lib/python3.6/site-packages/rasa/cli/scaffold.py", line 195, in run
    init_project(args, path)
  File "/build/lib/python3.6/site-packages/rasa/cli/scaffold.py", line 111, in init_project
    create_initial_project(path)
  File "/build/lib/python3.6/site-packages/rasa/cli/scaffold.py", line 119, in create_initial_project
    copy_tree(scaffold_path(), path)
  File "/usr/local/lib/python3.6/distutils/dir_util.py", line 159, in copy_tree
    verbose=verbose, dry_run=dry_run))
  File "/usr/local/lib/python3.6/distutils/dir_util.py", line 135, in copy_tree
    mkpath(dst, verbose=verbose)
  File "/usr/local/lib/python3.6/distutils/dir_util.py", line 74, in mkpath
    "could not create '%s': %s" % (head, exc.args[-1]))
distutils.errors.DistutilsFileError: could not create '__pycache__': Permission denied

Command or request that led to error:
docker run -v $(pwd):/app rasa/rasa:latest init --no-prompt

or
docker run -v $(pwd):/app rasa/rasa:latest-full init --no-prompt

Thanks in advance and best regards
TBX

Thanks for raising this issue, @dakshvar22 will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗

Hi @tbx0912, I tried pulling the latest docker image on macOS and running the commands work as expected. Did you just switch to Ubuntu 18.04, or were you always testing on this platform for previous versions of Rasa too?

I have the same issue with Ubuntu 18.04. What I found suspicious is that when running
docker run -it --entrypoint /bin/bash -v $(pwd):/app rasa/rasa
The user id shows up as 1001 and even a simple touch leads to a permission denied.
$ docker run -it --entrypoint /bin/bash -v $(pwd):/app rasa/rasa
I have no name!@8d124f071a6f:/app$ id
uid=1001 gid=0(root) groups=0(root)
I have no name!@8d124f071a6f:/app$ touch blah
touch: cannot touch 'blah': Permission denied

Yet interestingly an empty folder models is created with root:root permissions on rasa init (but crashing with the same error as in the original post)

Changing permissions of $(pwd) used for the volume to 1001:root fixes the issue since my own user has a different id to 1001. Presumably this bug can only be reproduced if you are non running as the "first created user" on the system.

@tbx0912 I'd try sudo rm -rf __pycache__ wherever it is and running the command again, if you haven't already
Right, I think this is also related to a much larger issue where the rasa docker containers are still running commands as root, if you check file permissions in output (like models or folders created from rasa init) via ll or ls -alF in the command line if you're unix based.
See this PR in the rasa-sdk repo for what I think should be the proper way to handle file permissions and command executions.  Below (found in the rasa Dockerfile) I don't believe allows for commands to be run as unprivileged nor handles folder permission properly.
# ...
# Make sure the default group has the same permissions as the owner
RUN chgrp -R 0 . && chmod -R g=u .

# Don't run as root
USER 1001
# ...

versus a well-placed:
# ...
RUN groupadd -g 1000 nonroot && \
  useradd -r -u 1000 -g nonroot nonroot
USER nonroot
# ...

typically this is done after any installations that require root privileges

@wochinge I'd love to hear your thoughts, because what I've seen as a pattern for nonroot command execution is something like what's found here

Below I don't believe allows for commands to be run as unprivileged nor handles folder permission properly.

Could you please explain why that's the case?
We use group 0 (aka root) in our docker images cause that's the default group used on OpenShift clusters (whereas OpenShift assigns random user ids).  The only difference I see between the current instructions and the ones you shared is, that you 1) create a new group and 2) Assign a name to the user.

I get the same error on my system.
Additionally I created a post in the forum, maybe someone has already solved this issue there.
https://forum.rasa.com/t/docker-install-fails-with-pycache-folder-error/21648

Thanks to @AndiLeni  for posting the link of the rasa forum where the issue is posted,  and @ArjaanBuijk  for giving a simple solution in the forum, that worked excellent for me. I am just posting it here for the convenience,

> Solution by @ArjaanBuijk

This is how it looks for me, on Ubuntu 18.04, when I am inside the folder
 where I will install the mood-bot:

$ stat .
  File: .
  Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: 801h/2049d	Inode: 5119770     Links: 2
Access: (0755/drwxr-xr-x)  Uid: ( 1000/  arjaan)   Gid: ( 1000/  arjaan)
Access: 2019-12-24 10:10:38.261990864 -0500
Modify: 2019-12-24 10:03:55.915369626 -0500
Change: 2019-12-24 10:03:55.915369626 -0500
 Birth: -

As you can see, access rights for the folder are for uid=1000.

So, running docker container as the user with uid=1000 will work:

$ sudo docker run --user 1000 -v $(pwd):/app rasa/rasa init --no-prompt

cd  your_dir
stat .
checke the uid  permission of the dir.
if you dont have permission,then mkdir, do as the toturial


update metadata for Articles

Docs Build status updates of commit 0061a74:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Articles/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add phases to Expr.simplify

Rough implementation of the proposal in #194
For now, I am only using two kinds of simplify categories ("general" and "lower"). In the future, we could always add categories like "projection" and "predicate-pushdown".
Note that, in contrast to the plan in #194, this PR does not require "higher-priority" optimizations to be considered in every phase. Instead, the user is allowed to specify a specific tuple of simplify categories for each phase (e.g. phases=["general", "lower", ("general", "lower")].

Hrm, the allow_group thing feels off to me.  I'm trying to think about why I dislike it and I think it's because the kind of optimization is included deeply within the optimization code itself.  I think that it would be good to keep things separate if possible.  This might mean that we have many instances of the same method name, maybe something like the following:
@optimize("general")
def _simplify_down(...):
    ...

@optimize("lower")
def _simplify_down(...):
   ...

But if we're going to do this, then we might as well just use method names:
def optimize_simplify(...):
    ...

def optimize_lower(...):
    ...

The benefit of naming optimization passes the way you do (or with the decorators) is that it makes things really extensible.  It's obvious how to add more kinds of passes.
Mixing the names and the optimization code itself though definitely makes me nervous.  Maybe that's ok though, this is more of a gut reaction than anything.

Yes, I think I shared the same gut reaction (and still do a bit). I played with the registration concept and also felt that we might as well as distinct methods.
I ultimately decided to lean hard in the direction of “extensible” for
Now. However, I was expecting that we may collectively decide to shift :)

FWIW using different methods felt too restrictive when working on the lower PR

From my perspective I kind of want each individual optimization step to be an isolated method.  This is probably mostly an aesthetic preference that comes from writing other optimization systems, where being able to inject or remove or track or measure each step has been helpful.  Pulling things apart into small units seems attractive to me.
That might not matter at all in practice here (we may not get that sophisticated) so maybe I'm over-thinking things.

I definitely understand this feeling. I would also like for different flavors of "simplify"-based logic to be separated in a more systematic way.  To be honest, I'm still hoping to find a better compromise.
Some details that are currently challenging me:

In the current state of this PR, the _simplify_up/_simplify_down implementations can make intelligent decisions about optimization ordering within the categories included in the allow_group tuple.
The most natural way of organizing distinct optimization types by distinct methods is to split them into proper optimization passes, and to add the phases argument to optimize instead of simplify (e.g. expr.optimize(phases=("simplify", "lower", "simplify", "fuse")). However, this means:

We can no longer leverage the coupling behavior above (i.e. an expression cannot coordinate multiple types of optimizations in the same phase/pass).
We need to "fully" lower the expression graph during the "lower" phase, rather than incrementally performing general optimizations as abstract nodes like Merge are lowered to other abstract nodes like Shuffle. (Not sure if this matters in practice, but our ability to do this disappears).
Non-"lower" optimizations will no longer be allowed to return abstract nodes (e.g. Shuffle, Repartition, etc..), because there is no guarantee that a "lower" phase will always follow a "simplify" phase.

Given the challenges listed above, I'm leaning towards a design that preserves the expr.simplify(phases=) approach, but requires Expr definitions to register distinct _simplify_up and _simplify_down methods for each optimization type (i.e. "general" or "lower" for now).  This means the _simplify_up/_simplify_down logic cannot coordinate multiple optimization types (something I don't believe to be very important anyway), but we can still perform multiple optimization types within the same phase.

If I were to do this without an extensible phases system, using just simplify and lower, then I would probably write it as follows.
def optimize(expr):
    old = None
    while old and old._name != expr._name:
        old = expr
        expr = expr.simplify()
        expr = expr.lower()
    return expr

We keep alternating between the two (first doing simplify) until they converge.

I'd like something extensible.  Mostly because I don't want us to paint ourselves into a corner.  In my view phases are good, but not if they force us to mix everything.  That's painting ourselves into a corner.  Separating things into separate simplify/lower methods sounds fine to me, even if the orchestration function (like my optimize function above) is not yet very sophisticated.  We can make it more sophisticated in the future without changing a bunch of optimization code.

Good point about partial lowering.
I'm also ok with something more sophisticated.  I just want the sophistication to be outside of the optimization function code.

Therefore, we will either need additional methods like project_columns(), or we will still need to add the phases concept within simplify

There is a wide world of options at our disposal :)
I think that you're ok with this, but I'll say it anyway.  Rather than have "phases" we can also have a soup of different optimizations, each tagged in different ways or part of different families.  We can then combine these optimizations in different ways.  In general when thinking of optimization I think it's good to separate out ...

The legal transfomations that can occur
The control flow that applies those transformations in some order

Building the transformations is what we've mostly done.  This is in the _simplify_* methods today.  The control flow is entirely in the simplify method.  Separating these allows us to evolve the optimization system without having to rewrite all of the transformations (really annoying to do!).  I'm going to get very nervous if we start putting control flow stuff in the transformation code.  That way leads (historically in my experience) to either great pain, for a system that is hard to evolve.
If we're expecting to have more phases/families/... to optimization then I think we probably want to start separating out transformations and tagging them like the following:
@optimization("simplify", "column-projection")
def _transform_down(expr):
    ...

@optimization("lower")
def _transform_down(expr):
    ...

Then we can screw around with control flow questions like "do we want to simplify every time after we lower?" separately from modifying all of the transformation code.

Thanks for following up @mrocklin - I'm pretty sure we agree on the kinds of things we want to do. I also agree that the ideal solution will separate the complexity/sophistication from node-local optimization logic.
I'm in no rush to merge anything here until it is clear that we are on a promising path.
I like the idea of tagging methods very much. That said, I am still struggling to think of a clean way to to configure how distinguish different optimization flavors and different graph traversal/re-write approaches. It feels as though simplify is more of a distinct approach for traversing and rewriting the graph, and cannot be categorized in the same was as the local logic defined in _simplify_up and _simplify_down.

Since this PR still falls short of what we want, perhaps it makes sense to pick up on @phofl 's work in https://github.com/dask-contrib/dask-expr/pull/192 as our short-term approach to separating general "simplify" and "lowering" logic.  The more I think about the "lower" optimization, the more I feel like it is conceptually distinct from the other flavors of "simplify" (and deserves a distinct pass over the expression graph).
I think my only preference would be for optimize to look something like:
def optimize(expr, fuse=True):

    result = expr
    while True:
        out = result.simplify().lower_once()
        if out._name == result._name:
            break
        result = out

    if fuse:
        result = optimize_blockwise_fusion(result)

    return result

(note the use of lower_once instead of lower) to capture iterative partial lowering. In the near future, we can always work out a system to tag different flavors of simplify/lower.

It feels as though simplify is more of a distinct approach for traversing and rewriting the graph, and cannot be categorized in the same was as the local logic defined in _simplify_up and _simplify_down.

To be clear, simplify is very different than _simplify_up and _simplify_down to me.  I think that simplify is control flow code (something that is likely to change in the future as we figure out more about optimization while the _simplify_up and _simplify_down implementations are transformations that are likely to remain valid for a long time.

I am still struggling to think of a clean way to to configure how distinguish different optimization flavors and different graph traversal/re-write approaches

I think that as long as we label the transformations well (simplify vs lower vs other future names) then we can explore the problem of applying transformations as an interesting problem without a lot of code burden.
I'm not sure I fully undestood your last comment though.  I'd be happy to chat live if you're free early next week.

I think that simplify is control flow code (something that is likely to change in the future as we figure out more about optimization while the _simplify_up and _simplify_down implementations are transformations that are likely to remain valid for a long time.

Yes. I think this is exactly what I am attempting to say. It is easy to write different methods for different kinds of transformation logic (i.e. different flavors of _simplify_up and _simplify_down). My only point was that we probably want different kinds of control flow for different kinds of transformation logic as well.
Given my concerns about distinguishing control flow from transformation code, #192 seems like a reasonable near-term solution.


During deployment upgrade with high max surge, some pods are stuck in ContainerCreating state

Bug report
General Information

Cilium version (run cilium version)

cilium version
Client: 1.9.8 3fcfff7 2021-05-28T02:03:28+02:00 go version go1.15.12 linux/amd64
Daemon: 1.9.8 3fcfff7 2021-05-28T02:03:28+02:00 go version go1.15.12 linux/amd64

Kernel version (run uname -a)

# uname -a
Linux ip-10-80-179-178.ec2.internal 4.14.232-176.381.amzn2.x86_64 #1 SMP Wed May 19 00:31:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Orchestration system version in use (e.g. kubectl version, ...)

# kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:10:43Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.16-eks-7737de", GitCommit:"7737de131e58a68dda49cdd0ad821b4cb3665ae8", GitTreeState:"clean", BuildDate:"2021-03-10T21:33:25Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Link to relevant artifacts (policies, deployments scripts, ...)
Generate and upload a system zip ---- attached
I added logs for one node with cilium-8bmkj which is doing the issue currently (it really random on which pod it is happening)

cilium-sysdump-20210616-103544.zip
How to reproduce the issue

Install cilium using the following helm command

helm install cilium cilium/cilium --version 1.9.8
--namespace kube-system
--set egressMasqueradeInterfaces=eth0
--set nodeinit.enabled=true

Install a deployment with around 100 pods with max surge of 50% and max unavailable of 25%
change the image tag of the deployment to trigger pods replacement

I'm seeing the following error a lot in logs. Not sure yet what could cause this.
Error while configuring proxy redirects: proxy state changes failed: context deadline exceeded

Install a deployment with around 100 pods with max surge of 50% and max unavailable of 25%

Any chance you could share such a deployment?

sure,some values were changed to placeholders.
the deployment is using the commonChart as a library chart.
tempcase.zip

Issue persists even after upgrading to 1.10.0

cilium status command give this output:
controller bpf-map-sync-cilium_ipcache is failing since 3s (6333x): 8832 map sync errors

cilium connectivity give this output:
[cluster-arn] Waiting for Cilium pod kube-system/cilium-t9965 to have all the pod IPs in eBPF ipcache...
Error: Connectivity test failed: timeout reached waiting for pod IDs in ipcache of Cilium pod kube-system/cilium-t9965

@pchaigno  what else can I do to assist with troubleshooting this issue?

https://github.com/cilium/cilium/issues/16375 might be the same root cause. I found the same proxy state changes failed message in some of the logs and it shares some of the symptoms.

@pchaigno thanks, I will keep checking the other thread as well

@pchaigno I upgraded to 1.10.2 and now I have a clearer message in the kubectl describe pod:
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "ede16d4f3c9626b5adc140c16e103c2ac03d6f9b0e62db5d9f93fef0e9480ab7" network for pod "production-stateless-trail-writer-service-aws-775687f9b5-2g2wf": networkPlugin cni failed to set up pod "production-stateless-trail-writer-service-aws-775687f9b5-2g2wf_production-services" network: Unable to create endpoint: [PUT /endpoint/{id}][429] putEndpointIdTooManyRequests

@ybialik 429 error code means rate limiting has kicked in. This is expected with such a high surge of pods. You can tune these parameters via https://docs.cilium.io/en/v1.10/configuration/api-rate-limiting/#id1

Thanks @christarazi , we already played with the limits without any success.
we did see major improvements in 1.10.3 on our staging cluster. I hope to upgrade the version on production cluster this Sunday and see if it fixes the issue for good.

@ybialik Sounds good. Please close the issue if you no longer see this or edit the issue with the most up-to-date information (after your upgrade).

I wanted to add these points here: Initially, when I just used helm upgrade with appropriate flags I've ran into the same problem above i.e, many pods were going in ContainerCreating or CrashLoopBackOff status including cilium-xxxx
The correct way to upgrade Cilium from 1.9.x to 1.10.3 is
helm upgrade cilium cilium/cilium --version 1.10.3 \
  --namespace=kube-system \
  --set upgradeCompatibility=1.9

Then check the running status via cilium status

Also kindly note I've faced errors when I've upgraded using kubectl so I highly suggest going with helm

Reference used: https://docs.cilium.io/en/stable/operations/upgrade
Hope this will help you to upgrade to the latest release @ybialik 🤞
cc: @pchaigno

After upgrading to the latest release I can verify that for the last 2-3 weeks we didn't get the issue so it was resolved.
Thank you all for the hard work.


Add Watchman support #72

Installs Watchman support automatic with creating a new Ember project.
As asked in issue "Install watchman #72"

Thanks! I added a comment about using NPM over brew. The brew module is mainly ment for future use, updating any pre-installed dependencies that happened to be installed by brew. If you could update that I'll pull down the branch, test it, and most likely merge it.

Also, watchman doesn't have a -v flag, so we can't check install that way. I'm thinking we could check install by checking the path via which. For version number we can't do much as the watchman binary doesn't have it. We could ask NPM for the version, but that won't work if the user has it from before via brew or ports. So either just return "?" from version, or check NPM first, then return ? if it's installed but not listed in NPM.

OK, I'll update it.

Problem is: Watchman installed through NPM doesn't work with Ember-CLI.
You'll still get "Could not find watchman, falling back to NodeWatcher for file system events.".
As the Ember.js documentation already said: Watchman must be installed through Homebrew.

Maybe an idea:
Let Ember-Heart check and/or install Homebrew and then install Watchman through Brew?

Oh, that's an interesting issue. I'll have to think a bit about that one, and get some input from @kimroen as well. If we need to install homebrew for the user, we may want to use that for more stuff as well.
We tried hard to avoid depending on homebrew in the first place because it's pretty invasive, but we might not have a choice at this point.

I had a IRL chat with @kimroen about this. This is our current plan (feel free to suggest alternatives):

We'll install Watchman automatically during dependency setup if you already have brew
We're planning an event log system. We'll show the same kind of warning as Ember-CLI does if you don't have Watchman, but with a popup-GUI that lets you one-click install brew and Watchman

So for this PR, we need to implement Watchman as optional based on the status of brew. Specifically, it shouldn't even be listed during installation if you don't have brew (since we don't have a way to install it for you yet). I'd love if you could add that check. If not, I might be able to fix it this weekend.

Awesome. This looks good to me now. @Vinnie1991 are you planning do do more on this PR, or should I merge? (Asking since you haven't commented after the latets commit yet). I tested locally with and without brew, and it worked as expected.

Oh sorry @thomassnielsen.
Maybe a next issue when you've decided that Brew will be used more. But for now, this is done.

Once again, thanks for the PR. This will make it into 0.4.0. With some luck we'll have it baked into the event system #87 as mentioned above as well. :+1:

You're welcome. When you've another issue I'll help again :)
(First time I'm contributing to OS)


Allow test descriptions in 1-arg version of json_is and json_message_is

The '1-arg' version of json_is and json_message_is does not accept a description, due to how the params are pulled off of @_.
So what would seem intuitive:
$t->json_is( { foo => [1, 2, 3] }, 'a simple test' );
does not actually work.
This patch fixes that. All existing tests pass.
For this small change, additional tests may be unnecessary?

Certainly it would need to be used in the test suite and need to be documented. Regarding functionality, I'm of two minds here. Originally json documents had to be either a hash or an array and so to compare the top level structure it must indeed be a reference.  That said, in the recent spec json documents may be any type and of course you can just use the empty pointer to fill up the slots.

:-1: Have to agree with @jberger on all points.

The test and docs points I could address, but if you don't agree with the functionality, I'll just close the request again.

A ref check just couldn't work with RFC 7159 compliant JSON.

I see what you mean. The json response could well be unstructured. Thanks.

In case someone else stumbles over this pull request in the future, what you can do is $t->json_is('' => {foo => [1, 2, 3]}, 'right data structure').


Scholarship page

Feature
Why is this feature being added?
To let people know what scholarships are available and how to apply for them.

What should your feature do?
Be an easy to navigate way for people to learn about scholarships.
Ideally, this would be done with some sort of template where the text can be quickly updated as things shift.

sooo per @AshTemp slack intro is probably #1 with the map #2 events and successes at #3 and scholarships. She doesn't have an opinion right now shoot her ideas

Would the scholarship content be hard coded or be stored in a database?

Is there a list of scholarships that has already been compiled for the scholarship page?

@charlessipe Eventually they would likely be stored in the DB, and fetched via API. We have an Admin Panel where non-devs can update content without delving into the code.
But, for MVP it could likely be a static JSON file - as @AshTemp noted above: "template where the text can be quickly updated as things shift".

There is already a scholarship page for logged in users.

Good call @charlessipe . I'm going to update this issue so it displays up-to-date scholarship information fetched via API from our DB.

Looks like the back-end PR https://github.com/OperationCode/operationcode_backend/pull/355 was merged, and there's a 'Scholarships' section editable in the Admin Dashboard. We should be able to add up-to-date data there and see about fetching/displaying in on the front-end now.

I'm interested in working on displaying the scholarship data on the scholarships page.

We have some placeholder data there, I believe.

Closed via #993 and Admin Dashboard updates.


Pulumi provider configuration should be made available for other azure providers

Today there are multiple azure providers available in pulumi: pulumi-azure, pulumi-azure-nextgen, pulumi-azuread.
While configuration for all of them is automatically picked up when using environment variables such ARM_TENANT_ID, setting the equivalent stack config value for the provider namespace is not, e.g. azure:tenantId.
In a project where one is working with all 3 providers, this is becoming very tedious to maintain, let's look at the following example:
...
config:
  azure:clientId: abc
  azuread:clientId: abc
  azure-nextgent:clientId: abc

There are a multiple required properties such as clientId, clientSecret, subscriptionId, tenantId and environment that one has to specify (and potentially encrypt) when using service prinicipal authentication.
Duplicating these properties is bad UX, so the ask here is to create a common config namespace for azure that is respected by all providers and can be overriden using a more specific namespace if need be.
An alternative for users is to just specify any of the namespaces e.g. azure: and then export environment variables in the code but that's not a good long-term solution.
There are multiple potential solutions here:

Create a new namespace that all providers implement
Make all providers respect other provider configs

On top of that I think there should be some clear warning in a mixed environment that these configs do not apply and provisioning falls back to the current az cli context which can do a lot of damage if it goes unnoticed.
FYI @clstokes

One option we could consider would be to have azuread and azure-nextgen use configuration provided on azure unless it is overridden by configuration on the specific provider. This might get slightly confusing in some cases of mix-n-matched configuration provided across both azuread and azure - but in common usage would likely be much easier to understand.
@mikhailshilkov Curious your thoughts on this?

@mikhailshilkov @clstokes ping on this.

Yes, I think this suggestion is reasonable


feat(useSeek): Add seekAll and seekAllByName methods to useSeek composable

This implements #236
Tldr; seekAll and seekAllByName are the same as seek and seekByName except that they return an array of all matches instead of the first match.
Both methods return an empty array [] when there are no matches

I updated the PR title, so the linter doesn't flag it.
Just FYI, here's the expected format for titles.

@andretchen0 Thanks! I'll keep that in mind. Also I've never seen the conventional commits site before, double thanks for that!
@alvarosabu I updated the documentation with a very barebones example/description and used includes over ===


Update instructions for building the C binding in README.md

Even if we follow the current instructions for building the C binding in README.md, we can't build and test it.

Thanks!


Rename storage.backend.class.name -> storage.backend.class

Following the convention from Kafka.

We were following it, at least similar to https://github.com/apache/kafka/blob/9cfc4b9373bf887ec2fb95bc607f4ebd1c8613c0/storage/src/main/java/org/apache/kafka/server/log/remote/storage/RemoteLogManagerConfig.java#L60 or https://kafka.apache.org/documentation/#brokerconfigs_alter.config.policy.class.name
Though, I can find some inconsistencies, e.g. https://kafka.apache.org/documentation/#consumerconfigs_sasl.login.callback.handler.class
I don't feel strongly about it, but be aligned with remote storage configs sounds ok to me.

Oops, it seems we've just looked at different parts of Kafka and there indeed were some inconsistency


Crash in ESTIMATE * FROM VARIABLES OF population WHERE  with ignored variables

Consider
ESTIMATE *
FROM VARIABLES OF gapminder
WHERE DEPENDENCE PROBABILITY WITH "life expectancy at birth" > 0.5

The compiled BQL is
SELECT c.name AS name
FROM bayesdb_population AS p,
bayesdb_variable AS v, bayesdb_column AS c
WHERE
p.id = 1 AND v.population_id = p.id
AND c.tabname = p.tabname
AND c.colno = v.colno
AND v.generator_id IS NULL
AND (bql_column_dependence_probability(1, NULL, 136, c.colno) > 0.5)

Because sqlite does not guarantee the order of evaluation of the expressions in the WHERE clause, it is possible that
bql_column_dependence_probability(1, NULL, 136, c.colno) > 0.5 is evaluated first, which causes a crash if c.colno is IGNORED in the population.
I believe a simple fix is to simply compile as:
SELECT v.name AS name
FROM bayesdb_variable AS v
WHERE population_id = 1
AND v.generator_id IS NULL
AND (bql_column_dependence_probability(1, NULL, 136, v.colno) > 0.5)

It is also the case that the current implementation, which is selecting names from bayesdb_column, skips latent variables.


ValueError in Stage2

Hi, I'm trying to run your code on CIFAR-10. The training and SWA in stage1 were fine, but I got the following error when training stage2:
root@864d7f9c24b4:/SupCon-Framework# python train.py --config_name configs/train/train_supcon_resnet18_cifar10_stage2.yml
{'model': {'backbone': 'resnet18', 'ckpt_pretrained': 'weights/supcon_first_stage_cifar10/swa', 'num_classes': 10}, 'train': {'n_epochs': 20, 'amp': True, 'ema': True, 'ema_decay_per_epoch': 0.3, 'logging_name': 'supcon_second_stage_cifar10', 'target_metric': 'accuracy', 'stage': 'second'}, 'dataset': 'data/cifar10', 'dataloaders': {'train_batch_size': 20, 'valid_batch_size': 20, 'num_workers': 12}, 'optimizer': {'name': 'SGD', 'params': {'lr': 0.01}}, 'scheduler': {'name': 'CosineAnnealingLR', 'params': {'T_max': 20, 'eta_min': 0.001}}, 'criterion': {'name': 'LabelSmoothing', 'params': {'classes': 10, 'smoothing': 0.01}}}
Files already downloaded and verified
Files already downloaded and verified
Traceback (most recent call last):
  File "train.py", line 111, in <module>
    train_metrics = utils.train_epoch_ce(loaders['train_features_loader'], model, criterion, optimizer, scaler, ema)
  File "/SupCon-Framework/tools/utils.py", line 250, in train_epoch_ce
    ema.update(model.parameters())
  File "/usr/local/lib/python3.8/dist-packages/torch_ema/ema.py", line 88, in update
    parameters = self._get_parameters(parameters)
  File "/usr/local/lib/python3.8/dist-packages/torch_ema/ema.py", line 65, in _get_parameters
    raise ValueError(
ValueError: Number of parameters passed as argument is different from number of shadow parameters maintained by this ExponentialMovingAverage

Another minor problem is GPU usage. I used to run another implementation of SupContrast. It requires 8x GPU memory (and higher utilization of each GPU) to train stage1 of the same backbone and batch size. Did your know what cause that difference?

Hey!

That's weird. Worst case scenario - it's possible to just erase EMA from the code, but it's better to keep it. Just as a sanity check, could you share your packages versions?

Pretty sure I do. I guess you're referring to this implementation. As I noted in my README, that implementation is very faulty. In particular, due to incorrect implementation of ResNet, it's very memory-unifficient, that's why you have this 8x utilization.

Sorry, didn't see that you included the link to another implementation. Well, then I guess I'm right as to why it works that way.

Thanks for your reply. It works when ema=False. So, I guess it's probably caused by the EMA module.


In the polywas layout, the chromosomes are ordered lexicographically

Chromosome 10 should come after 9.

Changing localeCompare to numeric mode fixed this:


'Exchange & Security Fee' is shown as '$0.00' on the 'Buy/Sell Gold Confirmation' screen even though the dollar gets cut with the exchange fee.

Frequency: 100%
App version: iOS Celo Alfajores Wallet Testflight  (1.6.0 (21) ), Internal Android Celo Alfa v1.6.0.
Repro on: Google Pixel XL 2 (9.0), Samsung Galaxy A8+ (8.0.0),
Testing Account:<PHONE_NUMBER>/backup Key
Repro Steps:

Launch the app and login with testing account.
Tap on “Gold” tab.
Tap on “Buy” gold.
Enter amount and tap on “Review” button.
Observe Exchange fee shows 0.00.
Tap on “Buy # gold” button.
Observe Dollars cuts with exchange fee.

Current Behavior: Exchange & Security Fee' is shown as '$0.00'
Impact: User will be confused as amount is cut with exchange fee where as Exchange Fee shows 0 on "Buy/Sell confirmation" screen
Expected Behavior: “Exchange & Security fee” should be shown.
Attachment: Android_exchange fee gets cut but not showning.mp4 (Bug observe at 15 and 1:15 sec)

Hey @Lss-Ankit the video ends at 1:11 so I cannot see the bug you referenced at 1:15. Could you post another video? Thanks!

@annakaz Sorry for the inconvenience. I have re-verified this issue and observed that issue is reproducing partially now in Android & iOS.
Verified on builds : iOS Test flight build : v1.6.3 (25) & Android Celo Alfa build : v1.6.2 (104794504)
Verified on Devices : iPhone SE (13.3) & Samsung Galaxy J7 Prime (6.0.1)

In Android, Respective estimation & security fee is shown on 'Buy' gold confirmation screen. Issue reproduce on 'Sell gold' confirmation screen. '0' amount is shown for estimation fee in 'Sell Gold' confirmation screen.
Attachment : Android_Exchange & Security fee
In iOS, Respective estimation & security fee is shown on 'Buy' gold confirmation screen. Issue reproduce on 'Sell gold' confirmation screen. 'Nan' text is shown for 'Estimation fee' in 'See Gold' confirmation screen. Already filed separate issue for 'Nan' text : Issue #3316
Attachment : iOS_Exchange & Security fee

Thanks!

I believe the issue of showing $0.00 as the tx fee is captured in different issues now.

Hi @tarikbellamine  I have verified this issue using latest Android Internal Build v1.3.0(1004294316) & Test Flight build v1.3.0(27) and observed that issue is still reproducing.
Repro on devices: iPhone SE2 (14.0.1) , Google Pixel XL (8.1)
- In both device it is observed that in $0 amount  is displaying instead of actually fees charged in 'Exchange Fee' & 'Security Fee' section when user tap on Fees dropdown on Buy CELO/Sell CELO page.
Attachment :

For me, these show up at $0 rather $0.00. Ideal design will show two decimal points ($x.xx) for local currency and three when CELO (x.xxx).

Hi @coreycelo I have verified this issue using latest  Android Internal Build V1.11.0(1004294337) & Test Flight Build V1.11.0(47) & observed that issue is still reproduced.
Observation: User able to see $0 in front of "Exchange & Security Fee" & unable to see actual cutting fees.
Verified on Devices: Samsung Galaxy A5(7.0), iPhone SE (13.4.1)
Attachment: FeesStillShownAs$0.png

We should calculate the actual fees and them rounded up (same logic as elsewhere).

Hey @jeanregisser I have verified this issue using Android  internal  build & Test Flight build V1.14.2 & observed following:
Observations:

User able to see "Security Fee & "Exchange Fee" as $0 even fee gets cut.
Also we have tried to find exact Fee amount using "https://explorer.celo.org/blocks" & got Fee amount which cut exactly. (Present in attachment)
Attachment: FeesForExchnage.png
Verified On Devices: iPhone SE (14.2), Redmi Note 8 (9.0)


Fix engine hang issue while add multiple reply in a flow

What kind of change does this PR introduce? (check one with "x")
[*] Bugfix
[] Feature
[] Code style update (formatting, local variables)
[] Refactoring (no functional changes, no api changes)
[] Other... Please describe:

Fixes: #181
What is the current behavior?
What is the new behavior?

Fixed at PR #183


certain PDF files are not showing up in any search, even though the SMB crawl log says they were picked up

2017-09-07 17:25:01.231: [verbose] content found //outlook/invoices/combined_80669x170906180735.pdf
2017-09-07 17:25:01.288: [verbose] meta added //outlook/invoices/combined_80669x170906180735.pdf
2017-09-07 17:25:01.377: [verbose] content found //outlook/invoices/combined_80669x170906180739.pdf
2017-09-07 17:25:01.407: [verbose] meta added //outlook/invoices/combined_80669x170906180739.pdf
I cannot find either of these two by searching by filename, or date

Hi @thesuigeneris ! Ambar workflow for new files includes two steps:

Crawl file with crawler, SMB crawler in your case
Process file with the pipeline

Processing can get some time, because it's perform OCR and text extraction. Speed of processing depends on your hardware and number of pages in pdf.

These particular PDFs are only 2-3 pages long.  All other PDFs that have been crawled are searchable almost immediately.  I've had Ambar installed and running for a couple of days now.  I've got close to 100 PDFs that have been crawled perfectly fine.  It's just these particular ones from a certain vendor giving me issues by not showing up.

Hi @thesuigeneris
Could you share one of these files with us? We'll look into the issue. Looks like the text extractor can't process is correctly.
Thnx.

I've sent a couple of the PDFs to<EMAIL_ADDRESS>since they have private info

Fixed! Please update your Ambar and upload the files again. Please report the results. Thnx.

Issue resolved!  Thank you.


Prefactoring for topic reconciling

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>Fixes #

Proposed Changes

moving the code for creating the actual topic to a reconcileBrokerTopic func

Release Note

Docs

will do same/similar for finalize


🌱 remove ironic image related checks in verify-release.sh

Ironic image is now released separately, no need to check them during CAPM3 release process anymore.

/override test-centos-e2e-integration-main  test-ubuntu-integration-main

/cherry-pick release-1.6

/cherry-pick release-1.5

/cc @adilGhaffarDev @mquhuy @smoshiur1237

/lgtm


noto-fonts: update 2017-10-24 -> 2018-11-30

Motivation for this change
Update the Noto fonts, particularly to avoid an old ligature issue. Fixes: #51498.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build noto-fonts

fixed-output derivation produced path '/nix/store/44l43pfm338impslqnjdbrxl9h4cfid4-noto-fonts-extra-2018-11-30' with sha256 hash '0l94aiy1b3qirg2mmbagbr0014vqk32za79pzck1acy2hgy716kq' instead of the expected hash '1lih49bqmsmblczvbl7qb1bhn
0bq8v5xkr991b3gjghpdkx584bc'
cannot build derivation '/nix/store/86vmv8dsi4vrdj6gxzcq64vlb807fgas-env.drv': 1 dependencies couldn't be built
[1 built (1 failed), 0.0 MiB DL]
error: build of '/nix/store/86vmv8dsi4vrdj6gxzcq64vlb807fgas-env.drv' failed
https://github.com/NixOS/nixpkgs/pull/51500
1 package failed to build:
noto-fonts-extra

1 package were build:
noto-fonts

This should probably use fetchFromGitHub, which may fix the above hash error.

@GrahamcOfBorg build noto-fonts

It was there before on aarch664

I'm confused about the naming of $out
On aarch64 it ends up being /nix/store/<blah>-noto-fonts-${version}
But on x64-linux it is /nix/store/<blah>-noto-fonts-${rev}
It wont prevent the use of the font but I wonder why Nix has a different behaviour


[material-ui][Autocomplete] Caret transformation issue with font size change #40874

The caret icon within the Autocomplete component was incorrectly positioned due to the following styles applied to the .css-1q60rmi-MuiAutocomplete-endAdornment class:

top: calc(50% - 14px);

This caused the caret icon to be misaligned when the font size was adjusted. Additionally, the 'right: 0;' style was redundant and was overridden by another class, so I removed it..
Bug Fix:

Removed the 'top' style to ensure that the caret icon remains vertically centered regardless of the font size. The caret icon is now positioned correctly within the Autocomplete component.
Removed the 'right: 0;' style as it was overridden, because it is unnecessary and the code is cleaner.

The caret icon's positioning is now consistent and follows the standard Material-UI styling.

So, I discovered that if we remove the 'right: 0;' style, the other Autocomplete components are changing, so I will add this back.


Use dynamic linking on iOS and MacOS

Currently static linking is used. This might cause problems if multiple packages in the same project use Flutter Rust Bridge.

Note: The first trials with using dylibs inside the xcframework failed. Asked for help here: https://github.com/fzyzcjy/flutter_rust_bridge/issues/1979


[BUG] When password is wrong, email ID is also cleared from the Login Form

Browser Details: Chrome
Device Details: macOS 10.15.6 (MacBook Pro)
Note: Tried on cloud.
Steps to replicate:
Case 1: Enter Correct Email ID and Incorrect password.
Actual Result: Email ID is cleared from the form.
Expected Result: If Email ID is present in the database, then it shouldn't be cleared from the form.
Case 2: Enter Incorrect Email ID and Incorrect password.
Actual Result: User is notified that there may be incorrect/invalid credentials.
Expected Result: Direct notification that Email ID doesn't exist/registered with Appsmith.

IMO the current behaviour is correct. We shouldn't be exposing this information that whether an email is incorrect or a password. The message with invalid credentials is appropriate.

Closing this issue because this is expected behaviour.


Add setting to disable offline notification

I don't believe Nylas Mail can be built from source yet, so I can't actually test this. But it looks right 🤷♂ .
Obviously someone will need to test this, or please help me build from source.
Alleviates #3300

It doesn't look like travis failed because of anything I did, but I'm definitely not certain. Please let me know if there's anything that needs to be done.


Possible fix for issue # 115 "papaduck example mqtt size off by one char"

Just added space for the null char in the topic.
Changed line number 112 from
int len = loc.length();
to
to int len = loc(length() + 1);

I have tested this and it works. Will merge and will close #115. Nice!


absl.flags._exceptions.UnrecognizedFlagError: Unknown command line flag 'new_emb_mat'

I am trying to get the repo working in TF1.7. I was able to get the training done with the help of dev branch for TF 1.4. But I failed in testing.  If I set it flags.DEFINE_integer("new_emb_mat", 0, "embedding matrix"), I got result F1 0.74 and accuracy 0.629. Is it normal? What value should we pass to new_emb_mat?
The error I got originally was :
Traceback (most recent call last):
File "/anaconda/envs/py35/lib/python3.5/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/anaconda/envs/py35/lib/python3.5/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/adminye/bi-att-flow/basic/cli.py", line 128, in
tf.app.run()
File "/anaconda/envs/py35/lib/python3.5/site-packages/tensorflow/python/platform/app.py", line 126, in run
_sys.exit(main(argv))
File "/home/adminye/bi-att-flow/basic/cli.py", line 125, in main
m(config)
File "/home/adminye/bi-att-flow/basic/main.py", line 26, in main
_test(config)
File "/home/adminye/bi-att-flow/basic/main.py", line 143, in _test
config.new_emb_mat = new_emb_mat
File "/anaconda/envs/py35/lib/python3.5/site-packages/tensorflow/python/platform/flags.py", line 88, in setattr
return self.dict['__wrapped'].setattr(name, value)
File "/anaconda/envs/py35/lib/python3.5/site-packages/absl/flags/_flagvalues.py", line 496, in setattr
return self._set_unknown_flag(name, value)
File "/anaconda/envs/py35/lib/python3.5/site-packages/absl/flags/_flagvalues.py", line 374, in _set_unknown_flag
raise _exceptions.UnrecognizedFlagError(name, value)
absl.flags._exceptions.UnrecognizedFlagError: Unknown command line flag 'new_emb_mat'

flags.DEFINE_integer("new_emb_mat", 0, "new_emb_mat")

flags.DEFINE_integer("new_emb_mat", 0, "new_emb_mat")

add it into basic\cli.py file.

flags.DEFINE_integer("new_emb_mat", 0, "new_emb_mat")

He asked What value should we pass to new_emb_mat?


JsonDeserialize annotation does not work for value class that is unboxed on the argument

Fixes #50 and #54 make it work except for the JsonDeserialize annotation when it is unboxed on the argument.

Below is the initial description.
Annotation given to function arguments containing value class does not work
Annotations with value class as an argument are compiled into synthetic functions with markers and private functions without markers.
Jackson is handling the private function, but this function does not reflect the annotation given on Kotlin.
This prevents the associated content from working.
This problem can be avoided by modifying the annotations to be given to getter, etc.
// before
data class Data(@JsonSerialize(using = /* ... */) val value: ValueClass)

// fixed
data class Data(@get:JsonSerialize(using = /* ... */) val value: ValueClass)

As for the annotations that must be given as arguments, please wait until the problem is fixed.

Fixes #50 and #54 make it work except for the JsonDeserialize annotation when it is unboxed on the argument.
Below is the initial description.
Annotation given to function arguments containing value class does not work
Annotations with value class as an argument are compiled into synthetic functions with markers and private functions without markers. Jackson is handling the private function, but this function does not reflect the annotation given on Kotlin. This prevents the associated content from working.
This problem can be avoided by modifying the annotations to be given to getter, etc.
// before
data class Data(@JsonSerialize(using = /* ... */) val value: ValueClass)

// fixed
data class Data(@get:JsonSerialize(using = /* ... */) val value: ValueClass)

As for the annotations that must be given as arguments, please wait until the problem is fixed.

    data class SummaryInfoReq(
        @get:JsonProperty("currency") val currency: Currency,
        @get:JsonProperty("vendor_net_pay") val vendorNetPay: BigDecimal,
    )

The @JsonProperty annotation works as expected (both when serializing and deserializing) when given to getter. 👏


RGB streaming

First of all, thanks for the efforts. Very interesting for my usecase (using the remarkable instead of the blackboard for teaching). I would like to have an RGB streaming mode which is needed when annotating pdf slides. I would implement it myself but I am not proficient in go.

I don't think this is possible. The reMarkable doesn't have a color-screen. We only have the framebuffer to work from and we copy that data verbatim (with the exception of a byte-swap for endianness). So we are already streaming all color information we have.
xiochitl could certainly interpret pen-strokes appropriately and then generate colored images. But that is something that would need to be added to their streaming features - it's not something that srvfb can do (and it is intentional that srvfb works that way).
I'll close this, but if I misunderstood what you want, feel free to clarify.

I didn't know the framebuffer was grayscale. If that's the case, of course there's nothing doable, other than changing the way the framebuffer works, which is out of the scope of this project of course.

FYI, someone chose a different approach to achieve something similar. As far as I'm aware they didn't end up publishing their code yet, but they might if you hit them up. It also can't mirror PDFs (it just transfers your strokes to the computer), but it might be possible to add. The approach, in any case, is far more amenable to the extension you want, as the actual drawing doesn't happen on the device, so it can be in any color you like.

Thing is that I do not need the pen strokes to be colored, just need to retain the PDF (background) in color. Can you confirm the framebuffer is in black an white? Thanks a lot.

The framebuffer is 16-bit grayscale.


Use fontTools/symfont.py to detect slant

https://github.com/fonttools/fonttools/blob/69c11928a209531a82b883fe08b6aac9ca49417a/Lib/fontTools/misc/symfont.py
(originally reported at googlefonts/fontbakery#684)

using OpenCV as suggested at https://github.com/googlefonts/FontClassificationTool/issues/6 is not necessarily easy, but I think it is probably a better aproach.


Laravel 5.7 Shift

This pull request includes the changes for upgrading to Laravel 5.7. Feel free to commit any additional changes to the shift-13330 branch.
Before merging, you should:

Checkout the shift-13330 branch
Review all pull request comments for additional changes
Update your dependencies for Laravel 5.7
Run composer update (if the pre-scripts fail, add --no-scripts)
Thoroughly test your application

If you want help with your upgrade, check out the Shift Human Services or join the Shifty Coders Slack room to get answers to all your Laravel questions.

:x: Shift could not upgrade the following configuration files since they differed from the default Laravel version. You will need to compare these configuration files against the Laravel 5.7 configuration files and merge any changes:

[ ] config/app.php
[ ] config/auth.php
[ ] config/database.php
[ ] config/filesystems.php
[ ] config/logging.php
[ ] config/mail.php
[ ] config/services.php

:warning: Laravel 5.7 changed the environment variable QUEUE_DRIVER to QUEUE_CONNECTION. You should review your server configuration or .env files to see if they need to be changed.

:information_source: Route::redirect now returns a 302 HTTP status code redirect in Laravel 5.7. Previously it returned a 301. Shift changed these to the new Route::permanentRedirect to preserve your intended behavior. You may want to review these changes if you are using the Route facade outside of the routes folder or want to return a 301.

:information_source: Laravel 5.7 removed the Blade "or" operator in favor of PHP's built-in ?? "null coalesce" operator. Shift automated this change, however, your application may still contain instances of or if you are using Blade syntax outside of the resources folder.

:x: Laravel 5.7 has a development dependency for fzaninotto/faker of ^1.4. You have a modified dependency for fzaninotto/faker in your composer.json. You should review your dependency and ensure it meets the new version requirement.

:information_source: Laravel 5.7 removed the resources/assets folder in favor of placing its sub-folders directly under resources. Shift moved these for you automatically. However, you may need to update the paths configured in your frontend build tool (e.g. webpack.mix.js) to reflect this new structure.
While Shift encourages a fully upgraded application, this new structure is not required. If this change significantly impairs your frontend build process, you can revert this commit.

:information_source: Laravel 5.7 now supports email verification when users register for your application. If you have implemented this feature yourself you may now be able to take advantage of this native functionality. For more details, review the documentation on Email Verification.

:warning: Shift found a call to setRounds() in tests/CreatesApplication.php. This was removed in a later version of Laravel 5.6 in favor of using the BCRYPT_ROUNDS environment variable and hashing.php configuration. You may be setting this explicitly, but you should compare yours against the 5.6 version and merge any changes.


chore: Setup eslint for packages/nuqs

Sharing the lint setup I created when debugging #566 in case linting is desired going forward.
This is mostly the default setup from npm init @eslint/config@latest with eslint 8, react, and ts. I added eslint-plugin-react-hooks & eslint-plugin-react-compiler.
I disabled the following rules because they throw errors in the current codebase that I didn't find particularly useful here:
rules: {
  '@typescript-eslint/no-explicit-any': 'off',
  '@typescript-eslint/ban-ts-comment': 'off',
  'no-useless-escape': 'off'
}

I also disabled eslint entirely in the *.test-d.ts files because those threw many errors with the rules of hooks and if the current usage of those files works fine for testing, I don't see any reason to lint there (at least for the rules of hooks).
Lastly, there are just a few warnings related to dependency arrays of the current hook usages:

These can be fixed very easily, but I will wait for feedback on how y'all would like to fix them (or not fix them) before making further changes.

@franky47 should I close this? I'm guessing since it's been left here, you're likely not interested which is np for me, I just like to close things to keep my PR tabs clean if they're not going anywhere.

Yeah I think we can close this. My experience with eslint has always been negative, though I see the value in a linter for community projects.
My eyes are on Biome to replace Prettier & linger steps, but last time I tried it it wasn't quite ready (especially regarding Tailwind support in the docs app).


unclutter: add module

Thanks! Looks good so I've merged it to master :-)

Sorry I should have commented before, but I had problems with unclutter so I added to nixpkgs hhpc too, whose aim is the same. Maybe this module could have been more general allowing pkg to be defined

It seems like hhpc uses different command line flags so perhaps would be best to have a separate module for it?

@nico202 Note that this module uses unclutter-xfixes by default, which is a modern fork that doesn't work the same way as the original unclutter.

@tadfisher yeah I noticed, I'll have to check it out to see if it behaves well :)
If it does not, I'll open a separate issue for hhpc, thanks


Examples throw 403

Examples from https://github.com/tannerlinsley/react-table/blob/master/docs/examples.md throw 403 in CodeSandbox. Not sure if issue with GH repo or CS itself, though

Nvm, just found #1968


Fix Visual Studio compile errors

Note: currently failing with #error: gl2.h included before glew.h error.

The two changes look good.  Approval conditional on header fix of course.


Paloma Nest Wallet: Create a Wallet

As a user of Paloma, I want to be able to sign in to Paloma Nest Wallet UI for creating a Paloma wallet.

[x] Splash/First Screen:
https://www.figma.com/file/ClniQyKFqN1hSpWizV5O4A/Paloma?node-id=1406%3A59

Community should like to Discord: https://discord.gg/8axuwfVV
Configuration: Please don't add any link for now. (need to be designed)
While hovering the icon next to Community and Configuration should turn in 45° (cross) and turn white.

Image/logo + icons: https://drive.google.com/drive/u/1/folders/1mPLJ5V6h0TVTLvNvjxZ_gCzuicBgUCT0

[x] Second Screen/Menu: After 5 second the first screen should change to the Menu Screen.
https://www.figma.com/file/ClniQyKFqN1hSpWizV5O4A/Paloma?node-id=1406%3A16

The menu have 2 options: Create a New Wallet or Connect an existing Nest Wallet. For now we will only implement the Create a New Wallet. (Connect an existing one will be part of the next flow/ticket).

While hovering the button will turn pink and the icon will turn in 45° like a cross.

Icons + Logo: https://drive.google.com/drive/u/1/folders/1mPLJ5V6h0TVTLvNvjxZ_gCzuicBgUCT0

[x] Create a New Wallet: When the user clicks on the previous menu "Create a new Wallet" should be redirected to this screen: https://www.figma.com/file/ClniQyKFqN1hSpWizV5O4A/Paloma?node-id=1500%3A521

1. Wallet Name: The user can select any name for the wallet only letters and numbers (max length: 20 characters)
2. Select a Nest Wallet icon for your Wallet: The user can select between 5 different color eggs to identify the wallet. Users will be able to pick one using a Drop Down menu.

While hovering between the possibilities will be shown with a pink background.
Please follow: https://www.figma.com/file/ClniQyKFqN1hSpWizV5O4A/Paloma?node-id=1498%3A422

3. Create a Password: The user will be able to set a password using letters, numbers, and signs.
Password will be shown with dots.
<img width="527" alt="Captura de Pantalla 2022-08-08 a las 14 01 06" src="https://user-images.githubusercontent.com/22323189/183413321-286d52d4-24bc-4e22-abc5-a4523b2240fd.png"
5. Confirm Password: The password should match.
6. Mnemonic: Should generate a unique 24-word mnemonic.
7. Disclaimer
8. Confirmation of the user wrote down the mnemonic. We will use here a check box.

9. Button: Sumit. Should be shown disabled until all the information is filled right.

[x] Confirm Mnemonic:

https://www.figma.com/file/ClniQyKFqN1hSpWizV5O4A/Paloma?node-id=1406%3A195

First push review and improvements: @wdev733

[ ] The font size on the New Wallet screen is too small. We will increase the font size from 10px to 12px. Please follow the designs: https://www.figma.com/file/ClniQyKFqN1hSpWizV5O4A/Paloma?node-id=1593%3A34

[ ] With the font sizing increasing we will also increase the sizing of the text boxes and distributions on the screen. Please check all items' sizing.

[ ] The New Wallet screen will need to use the scroll.  Screen H: 667px

Create Wallet changes.
Please follow: https://www.figma.com/file/ClniQyKFqN1hSpWizV5O4A/Paloma?node-id=1593%3A34


net: openthread: Added config for OpenThread version selection.

Config options used for selecting OpenThread stack version
were added.
Signed-off-by: Kamil Kasperczyk<EMAIL_ADDRESS>

@jukkar could you take a look on it, as @rlubos is out of the office for some time?


Return type of Postgres functions converting into interface{}  instead of Struct.

Version
1.27.0
What happened?
Sqlc not binding Postgres function's table type returning to a struct, it is directly binding into  an interface{} type as an array.
Relevant log output
[5 2024-10-07 17:42:57.801246 +0530 IST 2024-10-07 17:42:57.801246 +0530 IST]

Database schema
CREATE TABLE IF NOT EXISTS public.users
(
    id bigserial NOT NULL,
    phone text ,
    created_at timestamp with time zone,
    updated_at timestamp with time zone,
    CONSTRAINT users_pkey PRIMARY KEY (id)
)

CREATE OR REPLACE FUNCTION public.fn_authrepo_create_user(
    var_phone text,
    var_created_at timestamp with time zone,
    var_updated_at timestamp with time zone)
    RETURNS TABLE(user_id BIGINT, created_at timestamp with time zone, updated_at timestamp with time zone)
    LANGUAGE 'plpgsql'
    COST 100
    VOLATILE PARALLEL UNSAFE
AS $BODY$
DECLARE
    v_user_id BIGINT;
    v_created_at TIMESTAMPTZ;
    v_updated_at TIMESTAMPTZ;
BEGIN
    INSERT INTO users (phone, created_at, updated_at)
    VALUES (var_phone, var_created_at, var_updated_at)
    RETURNING users.id, users.created_at, users.updated_at
    INTO v_user_id, v_created_at, v_updated_at;

    RETURN QUERY SELECT v_user_id, v_created_at, v_updated_at;
END;
$BODY$;

SQL queries
-- name: CreateUser :one
SELECT * FROM fn_authrepo_create_user($1, $2, $3);

Configuration
version: "2"
cloud:
  project: "<PROJECT_ID>"
sql:
- schema: "migrations/authdb/schema/*.sql"
  queries: "migrations/authdb/queries/*.sql"
  engine: "postgresql"
  gen:
    go:
      package: "authdb"
      out: "internal/repository/authrepo/authdb"
      sql_package: "pgx/v5"
      emit_sql_as_comment: true
      emit_interface: true
      emit_prepared_queries: true

Playground URL
https://play.sqlc.dev/p/149e4929dbc625971466f68f4c1178337f2d4fb6e6168104aa2a007ff8f2f807
What operating system are you using?
Linux
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

Figured out the way to do it

Figured out the way to do it

@anazcodes Can you please explain how you made it? For now I have to write custom functions that return table into a separated .go file instead of using auto-generated one.


Need to Be able to borrow an Easy2 from a Multi

When a transfer is in progress, once you get the headers, but before the payload is received, there's no way to call functions such as Easy2::response_code(). This is because Multi takes the Easy2 object and then there's no way to access it.
I suppose simply adding something like fn Easy2Handle::get(&self) -> { &self.easy } would be sufficient and safe.

Actually, it needs to return a &mut because most of the accessors in Easy2 are &mut self

Indeed seems like something that access should be provided to! My main concern here is safety to ensure that we're not violating any invariant that libcurl expects us to uphold. For example calling .perform() on the Easy may cause issues... In any case at the very least it seems reasonable to mirror reasonable things to access onto Easy2Handle and such.

I need this now too. I might have some time this week to work on this.

I also wonder if there's a better way of describing the restriction on perform than we are currently doing. Maybe using a type state pattern:
pub struct Easy2<H: Handler, P> {
    // ...
}

pub struct Perform;

// Always starts out Perform
impl<H: Handler> Easy2<H, Perform> {
    fn new(handler: H) -> Easy2<H, Perform> {
        // ...
    }
}

// anything
impl<H, P> Easy2<H, P> {
    // Normal operations...
}

// where P = Perform
impl<H> Easy2<H, Perform> {
    fn perform(&self) -> Result<(), Error> {
        // ...
    }
}

unsafe impl<H> !Send for Easy2<H, Multi> {
    // Can't Send when attached to a multi handle
}

impl Multi {
    fn add2<H>(&self, easy: Easy2<H, Perform>) -> Result<Easy2<H, Multi>, MultiError> {
        // Change type of P from Perform to Multi
    }
}

These would be breaking changes of course, and I'm not sure if changing the API for this would be worth the breakage.

Hm yeah I think the extra type parameter may be a bit overkill for a use case like this, but perhaps we could just provide an unsafe accessor for the underlying handle and document that the unsafety has to do with reentrancy?


SRIOV-CNI failed to configure VF "failed to set vf 2 vlan: operation not supported

What happened?
Hi Team, can i request your help, i do not know if i forget something in the setting or if it is a bug.
I launch a test pod to test my installation, we use infiniband using Mellanox ConnectX-6 Card.
CNI, DEVICE where created with manifest from your repository
Multus was installed previously with Kubespray and run right with Calico as default CNI
apiVersion: v1
kind: Pod
metadata:
  name: samplepod
  annotations:
    k8s.v1.cni.cncf.io/networks: sriov-net
spec:
  containers:
  - name: testing
    command: ["/bin/bash", "-c", "sleep 300"]
    image: centos/tools
    resources:
       limits:
          "mellanox.com/mlnx_sriov_rdma" : "1"

but he do not start :
Type     Reason                  Age   From     Message
  ----     ------                  ----  ----     -------
  Normal   AddedInterface          3s    multus   Add eth0 [<IP_ADDRESS>/32] from cni0
  Warning  FailedCreatePodSandBox  2s    kubelet  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "94896576b1a37a2c3ac85f3f17dd4e0508345e240422e0540ef63d713cd341b8": [default/samplepod:sriov-net]: error adding container to network "sriov-net": SRIOV-CNI failed to configure VF "failed to set vf 2 vlan: operation not supported"
  Normal   AddedInterface          2s    multus   Add eth0 [<IP_ADDRESS>/32] from cni0
  Warning  FailedCreatePodSandBox  1s    kubelet  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "34d8ea838078f926b3133e84fa485e2c7c1e40cd4465bc934010dc7728a84c45": [default/samplepod:sriov-net]: error adding container to network "sriov-net": SRIOV-CNI failed to configure VF "failed to set vf 2 vlan: operation not supported"

logs from  kube-sriov-device-plugin-amd64 on the node where pod try to start :
I0511 09:47:15.584909       1 server.go:115] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:41:00.3],},},}
I0511 09:47:15.585011       1 netResourcePool.go:50] GetDeviceSpecs(): for devices: [0000:41:00.3]
I0511 09:47:15.585037       1 pool_stub.go:97] GetEnvs(): for devices: [0000:41:00.3]
I0511 09:47:15.585046       1 pool_stub.go:113] GetMounts(): for devices: [0000:41:00.3]
I0511 09:47:15.585061       1 server.go:124] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_MELLANOX_COM_MLNX_SRIOV_RDMA: 0000:41:00.3,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{&DeviceSpec{ContainerPath:/dev/infiniband/issm3,HostPath:/dev/infiniband/issm3,Permissions:rwm,},&DeviceSpec{ContainerPath:/dev/infiniband/umad3,HostPath:/dev/infiniband/umad3,Permissions:rwm,},&DeviceSpec{ContainerPath:/dev/infiniband/uverbs3,HostPath:/dev/infiniband/uverbs3,Permissions:rwm,},&DeviceSpec{ContainerPath:/dev/infiniband/rdma_cm,HostPath:/dev/infiniband/rdma_cm,Permissions:rwm,},},Annotations:map[string]string{},},},}

Anything else we need to know?
i configured card with  : https://github.com/k8snetworkplumbingwg/sriov-network-device-plugin/blob/master/docs/vf-setup.md#mellanox  method
[root@k8-worker-cpu-1 ~]# ibdev2netdev -v
0000:41:00.0 mlx5_0 (MT4123 - 1028SN     ) Mellanox ConnectX-6 Single Port VPI HDR QSFP Adapter fw 20.28.4512 port 1 (INIT  ) ==> ib0 (Down)
0000:41:00.1 mlx5_1 (MT4124 - NA)  fw 20.28.4512 port 1 (DOWN  ) ==> ib1 (Down)
0000:41:00.2 mlx5_2 (MT4124 - NA)  fw 20.28.4512 port 1 (DOWN  ) ==> ib1 (Down)
0000:41:00.3 mlx5_3 (MT4124 - NA)  fw 20.28.4512 port 1 (DOWN  ) ==> ib1 (Down)
0000:41:00.4 mlx5_4 (MT4124 - NA)  fw 20.28.4512 port 1 (DOWN  ) ==> ib1 (Down)
[root@k8-worker-cpu-1 ~]# lspci | grep Mellanox
41:00.0 Infiniband controller: Mellanox Technologies MT28908 Family [ConnectX-6]
41:00.1 Infiniband controller: Mellanox Technologies MT28908 Family [ConnectX-6 Virtual Function]
41:00.2 Infiniband controller: Mellanox Technologies MT28908 Family [ConnectX-6 Virtual Function]
41:00.3 Infiniband controller: Mellanox Technologies MT28908 Family [ConnectX-6 Virtual Function]
41:00.4 Infiniband controller: Mellanox Technologies MT28908 Family [ConnectX-6 Virtual Function]

Component Versions

Component
Version

whereabouts
docker.io/dougbtv/whereabouts:latest

SR-IOV CNI Plugin
ghcr.io/k8snetworkplumbingwg/sriov-cni:latest

Multus
ghcr.io/k8snetworkplumbingwg/multus-cni:v3.8

SR-IOV Network Device Plugin
ghcr.io/k8snetworkplumbingwg/sriov-network-device-plugin:v3.3.2

Kubernetes
1.21.4

OS
CentOS Linux release 7.9.2009 (Core)

Config Files
apiVersion: v1
kind: ConfigMap
metadata:
  name: sriovdp-config
  namespace: kube-system
data:
  config.json: |
    {
        "resourceList": [
        {
                "resourceName": "mlnx_sriov_rdma",
                "resourcePrefix": "mellanox.com",
                "selectors": {
                    "vendors": ["15b3"],
                    "devices": ["101c"],
                    "drivers": ["mlx5_core"],
                    "isRdma": true
                }
        }
        ]
    }

apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: sriov-net
  annotations:
    k8s.v1.cni.cncf.io/resourceName: mellanox.com/mlnx_sriov_rdma
spec:
  config: '{
  "type": "sriov",
  "cniVersion": "0.3.1",
  "name": "sriov-net",
  "ipam": {
    "type": "whereabouts",
    "range": "<IP_ADDRESS>/24",
    "range_start": "<IP_ADDRESS>",
    "range_end": "<IP_ADDRESS>",
    "gateway": "<IP_ADDRESS>"
  }
}'

Hi @seb-835 can you please try and check dmesg?
also please try to run the command manually to check if you see the same error. (if that is the case looks like a driver issue)
ip link set <pf-interface> vf 2 vlan 0

ib0 is Infiniband link type.
you should use SriovIbNetwork CR for it (which uses ib-sriov-cni)

@seb-835 did you manage to get this to work when using ib-sriov cni[1] ?
[1] https://github.com/k8snetworkplumbingwg/ib-sriov-cni

Oh damn right,

ip link set ib0 vf 2 vlan 0
RTNETLINK answers: Operation not supported

Hi, I have the same issue, did you find a way to solve this problem?

@Summerbluesea  there is no VLAN in Infiniband there is PKEY (similar yet different).
you need to use SriovIbNetwork CR if you are using sriov-network-operator.
if its just cni, you should use ib-sriov-cni as i wrote on june 14

closing this issue feel free to reopen if needed


Added missing container for hippdwi_to_template

This PR adds the autotop container to fix the missing command error for c3d when the hippdwi_to_template rule is run.
Resolves #215

actually wait, now having some strange issues with the version of c3d in that container - the rule runs fine with c3d installed on cbs server.. Will see if maybe upgrading to autotop 0.4.2 fixes it

nevermind, the issue I was just having is actually a separate one, related to reading in files from home directory (or ~/graham) when using a container rule in snakemake -- it changes the home directory when running singularity, so need to have SINGULARITY_BINDPATH that includes /home/ROBARTS:/home/ROBARTS.  I'm in the process of making this the default on the system, but will make sure we note this in the documentation too..
So I'll merge this in!


Add server, health and config sub-cmd to regproxy cmd

Proposed changes
This PR adds server, health and config sub-command to regproxy command.
It changes a command syntax in regproxy command.

Before

ngsi --stderr info regproxy --host orion-with-keyrock

After

ngsi --stderr info regproxy server --host orion-with-keyrock

Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[X] I have signed the CLA
[X] I have added tests that prove my fix is effective or that my feature works
[X] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

Coverage remained the same at 100.0% when pulling 5122bae47ab5b14c70a49e307ee8c13498bb3461 on fisuda:improve/regproxy into f5256a8715f23671bc6329528f79decdf2897875 on lets-fiware:main.


make old reservations inactive/available='No'

This needs to be done in 2 places

When fetching reservation slots for a tutor and checking for existing reservations, make old reservations inactive.
When a tutee reviews a tutor, set the available flag to 'No'.

Currently, we are only keeping the review option active for 1 day, so a user has to review his session within that day or he cannot review that session.
When the review is complete the active flag or available flag is set to no.


Check packetization-mode 1

While trying to receive H264 stream described with following SDP
a=rtpmap:102 H264/90000
a=rtcp-fb:102 goog-remb
a=rtcp-fb:102 transport-cc
a=rtcp-fb:102 ccm fir
a=rtcp-fb:102 nack
a=rtcp-fb:102 nack pli
a=fmtp:102 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42001f

first packet cannot be depayloaded. This MAY be the reason why our h264 decoder can't decode stream properly.
Packet that cannot be depayloaded (with RTP header):
<<128, 102, 115, 75, 75, 166, 248, 36, 154, 38, 21, 134, 120, 0, 14, 103, 66, 192, 31, 140, 141, 64, 80, 30, 144, 15, 8, 132, 106, 0, 4, 104, 206, 60, 128>>

The thask is to examine if we support packetization-mode 1 properly.
On the other hand h264 described with the following SDP works properly
a=rtpmap:108 H264/90000
a=rtcp-fb:108 goog-remb
a=rtcp-fb:108 transport-cc
a=rtcp-fb:108 ccm fir
a=rtcp-fb:108 nack
a=rtcp-fb:108 nack pli
a=fmtp:108 level-asymmetry-allowed=1;packetization-mode=0;profile-level-id=42e01f

should work as of #15


Create S3 bucket if it doesn't exist

When a new user tries out pywren with a bucket name that doesn't exist, right now they get an error message. We could auto create the bucket to make it easier for users

This will be fixed by #16


I'm not clear on how to create this sensor only on upcoming rain forecast.

I'm not clear on how to create this sensor only on upcoming rain forecast.
☔ Will it Rain – check if it will rain today.
The configuration screen for the integration includes temperature and wind in addition to rain. How to I create a sensor for only rain forecast?
Thank you for your work on this project!

The sensor automatically checks current conditions agains this list of bad conditions:
https://github.com/denysdovhan/ha-check-weather/blob/main/custom_components/check_weather/binary_sensor.py#L66-L74
I can work on feature for manual selection of desired conditions. I should be hard to implement.

Thanks again for you work on this project!
Just to make sure I am clear, I would like to be able to get a binary sensor for a subset of the conditions you show, in my use case, just rain above a given level, no check of temperature or wind. Perhaps picture below will give you some ideas of my interest :

You can make a template like:
{% set rain = state_attr('binary_sensor.check_weather', 'precipitation') %}
{% if rain == true%}
{% set neerslag= 'Het gaat vandaag regenen' %}
{% else %} {% set neerslag= "Als het goed is blijft het vandaag droog!" %}
{% endif %}
{{neerslag}}


Update Magma Info in README

magma-nvim-goose has been archived in favor of magma-nvim, which was briefly revived before the maintainers ran out of time again. I created Molten as a fork of Magma with a number of improvements and time to maintain it (at least for now). Would be best to update this information in this plugins README

Thanks. I saw your project earlier but hasn't tried it out yet. Looks great.


spelling mistakes

i am better than benny at this job

i went proofreading

i went proofreading

ok
666 commits moment is gone now

ok
666 commits moment is gone now


Bump rubygems to 2.4.4 and appbundler to 0.5.0 to compensate

Code looks fine, :+1: would prefer to pull in the upstream change from omnibus-sw to bump appbundler but not a big deal either way. If this fixes the repro case from the other day, let's merge it.


chromium: possible further enhancements

Issue description
Ideas for things we might want to look into enabling for Chromium:

use system ffmpeg, the blocking issue has been resolved: https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/browsers/chromium/common.nix#L71
consider enabling link_pulseaudio: https://cs.chromium.org/chromium/src/media/media_options.gni?rcl=master&l=36
enable hevc demuxing: https://cs.chromium.org/chromium/src/media/media_options.gni?rcl=master&l=72

Possibly more, wanted to open this before I forget and while I'm testing other chromium changes.
Steps to reproduce
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

Looks like HEVC requires using the system ffmpeg (based on https://cs.chromium.org/chromium/src/third_party/ffmpeg/chromium/config/Chromium/linux/x64/config.h?g=0&l=798) and I can't seem to get that to work yet.


Provide content gravity change API

We should provide a way to alter the content gravity.

Letterbox successor Pillarbox provides a VideoView whose content gravity can be changed at any time. Won't be implemented in Letterbox. Closed.


[ROS2] Failed to parse channel schema

Hi!
We just updated to the newest version of the Ros Foxglove Bridge (commit 8f327d1) and are experiencing issues reading topics. It worked fine on the version we were using previously.
Most of the topics are common schemes such as Float32 and Float64 etc. See image below:

Pressing one of the errors gives the following output, this is a Float64 message:

Closing this for now. @bertaveira feel free to re-open if the problem persists.


Error - Not able to open socket socket_0 to host: [Ubuntu IP] at port: 50001 Connection Timed out

Hi,
First of all, I am really sorry for the above confusion, its my first time using github.
I am using UR5e CB2 with controller URControl 1.8.25319, which I am trying to connect to my ROS installed in Ubuntu 16.04 on Oracle VM VirtualBox, through a router. Upon executing the three launching commands, first to bring up the ur, second to load all the  nodes for moveit and the third to launch the Rviz simulation, the code runs, no error are shown there. Then, I set the final state in rviz simuation, and clicked on the Plan and execute button. There aren't any problems shown in running these commands on the terminal. However, the error (shown in the image below) is popping up on my pendent's run logs as soon as I press the button.

At first I thought this was just the networking error but the rviz simulation is showing the correct joint states of the bot. Hence, there shouldn't be any error in the connection.
Its just that the driver is not able to evoke the joint controllers (my speculation).
Please help me through it!
Thanks.

I'm confused.
Can you give a bit more detail as to what problem you are encountering?

Hi,
First of all, I am really sorry for the above confusion, its my first time using github.
I am using UR5e CB2 with controller URControl 1.8.25319, which I am trying to connect to my ROS installed in Ubuntu 16.04 on Oracle VM VirtualBox, through a router. Upon executing the three launching commands, first to bring up the ur, second to load all the  nodes for moveit and the third to launch the Rviz simulation, the code runs, no error are shown there. Then, I set the final state in rviz simuation, and clicked on the Plan and execute button. There aren't any problems shown in running these commands on the terminal. However, the error (shown in the image below) is popping up on my pendent's run logs as soon as I press the button.

At first I thought this was just the networking error but the rviz simulation is showing the correct joint states of the bot. Hence, there shouldn't be any error in the connection.
Its just that the driver is not able to evoke the joint controllers (my speculation).
Please help me through it!
Thanks.

I am using UR5e CB2 with controller URControl 1.8.25319,

Is that really a UR5e? Or a regular UR5?

which I am trying to connect to my ROS installed in Ubuntu 16.04 on Oracle VM VirtualBox, through a router.

This is the cause of your problems.
If with "through a router" you mean: my VM has a NAT connection to my PC, then you need to configure the VM to allow connections on port 50001 to reach the guest OS.
if with "through a router" you mean: I have a physical router between me and the robot, then if the router is a NAT device (and is actually NAT-ting between your PC and the robot), you'll need to configure the router to allow connections from the robot through the NAT to your PC.

Note that with #301 merged we have better support for NAT-ed setups (as you can configure a different IP for the return connection).

As this is a local configuration issue and most likely not an issue with the package in this repository, I'm closing this.
Feel free to keep commenting on it of course @KushaagraGoyal.


Error converting to Json

After parsing the schema, the result i'm getting is of type string.
I've tried stringify and the cast to back to json.parse(), still the result im getting is of type string.
please suggest how to convert the response to javascript object

sorry, its mistake in schema file, its resolved now.  Thanks!


build: write options to file.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew tests with your changes locally?

These can be useful for later inspection or upload by gist-logs if
there's a failed install and it's unclear from logs alone what options
were used.
CC @zmwangx who was requesting this.

:+1: on this; have been thinking about similar for a while.
Might be useful to go even further and also capture the actual brew command line used to invoke the installation, to make it easier to diagnose problems with things that are installed as dependencies of the explicitly-requested formula, or expose problems with option parsing.


Support latest butbucket API.

It would be great to have an option for API switch.
The only difference is API prefix -
new: /rest/api/latest/inbox/pull-requests
old: /rest/inbox/latest/pull-requests

@bibmaster - will you create a PR?

Yes, i'll try.
I am C++, not JS developer, so don't be too keen.

Don't sweat it then, I'll do it myself.
Will take some time though as I'm a bittt occupied ATM.
If you're able to get it done, I'll merge and deploy, If not, I will soon myself.

Done. There was some bug with default config initialization during extension setup, all fields were uninitialized, can't explain why. Separated functions for parameters change and initialization solved the problem.

Released in v3.1.6


Adblocker not wokking

Script version
3.2
Describe the bug
Ads are showing not getting skipped. sometimes the ad is looping unable to skip aswell so i need to referesh multiple times and after this i need watch ad to skip.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots or a video to help explain your problem.
Desktop (please complete the following information):

OS: ios macbook air m1 chip
Browser chrome latest version. i updated it today.
Version 120.0.6099.216 (Official Build) (arm64)

Additional context
ads are showing. thats it

Check out 3.3 This should now be fixed.