:class bindings with array + objects

For feature request: #2530
Feel free to suggest any improvements or a better way of going about the proposed solution.

Thanks a lot for the great pointers! I know the code is messy and far from perfect, I thought I'd get it in a PR and iterate over it.

Refactored the code and added some more tests.

Nice! Just a small thing (see line note) and LGTM.

Good catch, I've updated it to cache value[i]. Once the PR is merged I'll updated the related docs.

Cached value[i] and fixed prematurely returning.

Removed contains and all prevKeys are cleared out.

Nice! LGTM now - can you squash into one commit?

Squashed commits!

woot!

Thanks for all your help @yyx990803


Fixes/bin setup

Hey @pixeltrix,
I found #550 and I ran into a small issue.
Hopefully this PR fixes #550 and improves the initial setup for the project.
Let me know if it looks good.
Thanks!

Thanks @etagwerker 👍


Total peer additions metric

Describe the feature
Geth has the following metric:

p2p/dials/success - the total number of dials that result in a peer being added to the peerset

It would be great to add this to reth as well!
cc @maxwolff
Additional context
No response

will do


About Models Serialization

Ask the question
I am exploring to use tribuo in our project. In our project, we need save the ML models for the future uses. I see that the models implements java.io.Serializable interface. I think this is only supported way for serialization, right?  With this way, I just have concerns that the future upgrading will be very hard. For instance, the schema/interface of some algorithms are changed.
Is there any advice to address this concern?  Thanks a lot for the help

We've started landing ONNX export support in preparation for the 4.2 release - https://github.com/oracle/tribuo/pull/154.  It will also have the start of an alternative serialization mechanism, as you'll be able to serialize provenance objects into protobufs. This will also expand in future releases to allow serialization of all of Tribuo's models as protobufs.

As of 4.3 all models can be serialized into protobufs and we'll use that as the sole serialization mechanism for v5 replacing java.io.Serializable (ONNX export will still be available for a subset of Tribuo models).


tidy_tools deinits basejump_stl

The current GETTING_STARTED has make tidy_tools run after make tools. This removes BaseJump STL in external (since it was moved there), causing future builds to fail.
The workaround is to execute
make update_libs
after
make tidy_tools

But we should not deinit it during tidy_tools

Fixed with 'make prep' flow


Behavior of 'not' in GraphQL filter

From the filter documentation

If the operator is Not or NotEqual either the Operands or the Path and a ValueType must be filled.

Could we simplify this?
NotEqual
What about NotEqual  as a shorthand for Not(Equal)
Or shown in examples:
{ operator: "NotEqual", path: ["Car", "color"], valueString: "white" }

would be a shortcut for
{ operator: "Not", operands: [ {operator: "Equal", path: ["Car", "color"], valueString: "white" } ] }

Not
I'd make  Not into a Not/None operator.
In a simpler notation than the GrahpQL filters for clarity:
not: [ Car.color == white, Car.color == green]

would be logically equivalent to:
and: [ Car.color != white, Car.color != green]

Agreed from my side.
@laura-ham can you please update the docs to reflect this.

@moretea I'm not sure what you mean, I think it already works like this?

I'd not overload the Not to work on both a list of operands, and a path/valuetype but keep it simple by only making it work on operands.
I would propose to make the behavior of And, Or, and Not simllar.
Just like that all the (Not)Equal Greater(OrEqual)Than operators would work only values.
I guess that the intention was to have a Not(Door.isOpen), but that makes the handling & error reporting harder than using Equal(Door,isOpen, valueBool: false)

Okay thanks. Implemented it like the following:

Not should always be an operator followed by operands, which kind of acts on the same level as And and Or
NotEqual should be followed by a value to be compared

So these two queries will result in the same:
{
  Local{
    Get(where: {
      operator:Not,
      operands: [{
        path: ["Things", "City", "name"],
        operator: Equal,
        valueString: "Berlin"
      }]
    }) {
      Things{
        City{
          name
        }
      }
    }
  }
}

{
  Local{
    Get(where: {
      path: ["Things", "City", "name"],
      operator: NotEqual,
      valueString: "Berlin"
    }) {
      Things{
        City{
          name
        }
      }
    }
  }
}

Hopefully this is what you meant @moretea?

Yep, indeed!


comparisons compression option in uglifyjs webpack prod config breaks on react-mapbox-gl

Can you reproduce the problem with latest npm?
Yes (including npm 5).
Description
There seems to be an incompatibility between CRA 1.0+ and the react-mapbox-gl component. This bug was not present before CRA 1.0, and only shows up in production mode, which makes me think it's a webpack 2.0 related issue.
Expected behavior
See https://github.com/davidascher/mapbox-repro-bug for a minimal test case (single component render -- works in development mode, doesn't work in production mode)
Actual behavior
In production mode (yarn build + serve -s build) , the map doesn't show and there's an incomprehensible traceback (as it's minified).
Environment
Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected<EMAIL_ADDRESS>node -v: v7.9.0
npm -v: 5.0.0 (but it happened with 4.x as well)

Then, specify:

Operating system: OSX
Browser and version: Chrome 58.0.3029.110

Reproducible Demo
Source: https://github.com/davidascher/mapbox-repro-bug
(trivial CRA repo with one dependency).
Live site showing bug: https://build-wnyrhmqiph.now.sh/
/cc @alex3165 as he is the maintainer of react-mapbox-gl AFAICT.

Aside: confirmed with the repo above that downgrading to react-scripts 0.9.5 fixes the problem.

Confirmed that if I eject, and change the build step to use the webpack.config.dev config, the bug goes away.

If I eject and simply comment out the UglifyJsPlugin from the plugins list, the bug goes away.

With @kzc's help, this has been traced it down to an uglify option (see https://github.com/mishoo/UglifyJS2/issues/2011#issuecomment-304405775).
Setting
   compress: {
        comparisons: false
   }

in the webpack prod config for the UglifyJS plugin fixes the problem.
I'll see if I can figure out how to override the webpack configs, I vaguely remember a bug going by about that new capability.

Want to send a PR disabling that option?

Happy to.
On Fri, May 26, 2017, 5:13 PM Dan Abramov<EMAIL_ADDRESS>wrote:

Want to send a PR disabling that option?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/issues/2376#issuecomment-304412407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADITnwK1R3KcuKOrJ5WW8Cj3YUASRRnks5r92qTgaJpZM4Nn2TZ
.

Please let us know if Uglify fixes this!

@gaearon Uglify won't fix this it seems, as the root cause seems to be in webworkify doing something not kosher / out of scope.
See tail end of the uglify thread: https://github.com/mishoo/UglifyJS2/issues/2011#issuecomment-304468747
And webworkify bug: https://github.com/substack/webworkify/issues/35

I see. If it's not a bug we'll likely reenable the optimization in the future.

I don't personally yet understand where the actual bug lies.  It's possible that webworkify's Blob-creation code can be fixed to not break uglify, we'll see what the webworkify maintainers say.
I understand that the uglifyjs maintainers need to define a scope and can be strict about it.  From a CRA point of view, reenabling the optimization means from the user's PoV code that works in dev mode doesn't work in production and it's hard to understand & track down the root cause.  I would recommend against re-enabling it until we understand a workaround other than ejecting. webworkify seems to have a bunch of usage: https://www.npmjs.com/package/webworkify.  Certainly all mapbox + CRA users would feel it.
On my minimal test case (including react, react-mapbox-gl, mapbox-gl), the difference between the created JS using webpack.prod.js between 1.0.6 and 1.0.7 is:
1.0.6: 668579 bytes
1.0.7: 669116 bytes
So for this case anyway the choice is to save 537 bytes (0.08% of JS bloat) and have a production build that works, or the other way around.

webworkify is not the problem. The function in the package being stringified by webworkify is violating an assumption uglify makes about static code analysis - that the variable in question is defined in an outer scope. Of course that package in question would work correctly if not uglified - it has a different set of assumptions and clearly was not written with minification in mind. It's not correct to call it a bug in that package either - it's a confluence of factors. Can the code that makes use of webworkify be changed to work whether uglified or not? Quite possibly. If not, the end developer would have to disable uglify comparisons.

Ah, thanks for that explanation, @kzc.  I'll see if I can figure out what that code is.

There seems to be a mapbox-gl-js issue on this topic: https://github.com/mapbox/mapbox-gl-js/issues/4359

It's a confluence of factors:

A module used by mapbox-gl-js has code that checks for the presence of global using typeof global !== "undefined". At the point where global is used, there's no outer context in which a variable global is defined.
webworkify stringifies functions to send to the worker. This is risky, but is the only known solution for bundling worker code that:

Doesn't require loading a second source file from the server
Doesn't duplicate code that's used in both worker and main thread

Something in create-react-app setup wraps mapbox-gl-js in function (global) { ... }.
Uglify decides to mangle the resulting global and transform the resulting typeof g !== "undefined" to void 0 !== g. Together, this produces broken code when the stringified function is executed outside of the function (g) { ... } wrapper.

Because of this confluence, it's likely to be one of those situations where the maintainers of each of the individual components involved insist that what their code does is perfectly valid, and it's the other stuff that's making invalid assumptions and must be fixed. At the risk of doing so myself, I would say the bug is in webpack: it provides no mechanism for a package to indicate what its build/packaging/bundling requirements are. If we, the authors of mapbox-gl-js, could put something in package.json indicating "don't mess with this code, it's already been bundled and minified in the way that it needs to be; redundant wrapping, bundling, and mangling is likely to break it", then issues like this wouldn't keep cropping up.

I'm not a user of mapbox-gl-js, but here's a couple of possible workarounds to avoid the use of global...
These are the contentious globals in question browserify'd by mapbox-gl-js:
var Buffer = global.Buffer || require('./buffer');

https://github.com/mapbox/pbf/blob/v1.3.7/index.js#L5
That can be solved by upgrading pbf to the latest version which does not use global.
And util.deprecate which no one cares about in the context of mapbox-gl-js:
exports.deprecate = function(fn, msg) {
  // Allow for deprecating things in the process of starting up.
  if (isUndefined(global.process)) {

https://github.com/defunctzombie/node-util/blob/b5d10a26402c3b60ce496e675a13c58bbed47801/util.js#L67
That can be solved by making a fork of<EMAIL_ADDRESS>to remove that function.
Perhaps util.deprecate can be retained but simply remove this code:
https://github.com/defunctzombie/node-util/blob/b5d10a26402c3b60ce496e675a13c58bbed47801/util.js#L66-L71
Alternatively, if browserify (or is it webpack?) can be modified to change the order of conditions in the following generated code to check for window first and global last it may also work:
typeof global !== "undefined" ? global : typeof self !== "undefined" ? self : typeof window !== "undefined" ? window : {}

I don't know where that code is.

Hey guys; I'm a little confused: this bug (and the mapbox-gl linked bug) are both "closed" but the problem still persists, right? And the disable micro-option doesn't seem to have been pulled in (yet? is the plan to pull that in for now?)...
Just trying to understand how to workaround this issue / when/what the real fix is (going to be)

@jliebrand looks like it was fixed in version 1.0.7
https://github.com/facebookincubator/create-react-app/pull/2379
https://github.com/facebookincubator/create-react-app/releases/tag/v1.0.7

Is the issue fixed? Can we re-enable it now in our projects?

mapbox-gl fixed their webpack typeof global issue in https://github.com/mapbox/mapbox-gl-js/pull/6956.
The workaround in https://github.com/facebook/create-react-app/pull/2379/files is no longer needed and can be reverted.


Non-isotropic images should be scaled on the viewer

State of qMRLab: 1de32d47b5457431f47a1ea92618774887d429c0
Current view:

Should look like this:

Proposed fix: use voxel dimension to stretch image on the 2D viewer appropriately.

solved with the new viewer


Problems running registry on Centos 6.5

I've been able to run a private registry successfully with all defaults on a local ubuntu 14.04 machine. I'm now trying to run on a Centos 6.5 machine. I've been getting some warnings that I'm not sure what to do with. ie lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing  I can pull down a Centos image and run a container. But I've tried getting the registry to work with S3 backend and without. The container quits on it own after a minute. With the non-s3 container it stays alive up until I try to push to the registry.
I initially was getting the error below
2014/06/19 20:40:34 unable to remount sys readonly: unable to mount sys as readonly max retries reached

So i changed  /etc/sysconfig/docker to have this:
other_args="--exec-driver=lxc --selinux-enabled"

Then that issue went away and this one started. The version in the EPEL for CentOS 6 is 1.1.2. I haven't found any docs on upgrading to a later version.
Run The Registry
docker run -e SETTINGS_FLAVOR=s3 -e AWS_BUCKET=custom-docker-registry -e STORAGE_PATH=/registry -e AWS_KEY=“xxxxxx" -e AWS_SECRET=“xxxxxx" -p 8000:5000 registry
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
2014-10-14 22:39:32,012 WARNING: Cache storage disabled!
2014-10-14 22:39:32,013 WARNING: LRU cache disabled!
2014-10-14 22:39:32,084 WARNING: No S3 region specified, using boto default region, this may affect performance and stability.
Traceback (most recent call last):
  File "/usr/local/bin/docker-registry", line 9, in <module>
    load_entry_point('docker-registry==0.8.1', 'console_scripts', 'docker-registry')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 351, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2363, in load_entry_point
** [Bugsnag] No API key configured, couldn't notify
    return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2088, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/usr/local/lib/python2.7/dist-packages/docker_registry/run.py", line 18, in <module>
    from .tags import *  # noqa
  File "/usr/local/lib/python2.7/dist-packages/docker_registry/tags.py", line 21, in <module>
    store = storage.load()
  File "/usr/local/lib/python2.7/dist-packages/docker_registry/storage/__init__.py", line 38, in load
    config=cfg)
  File "/usr/local/lib/python2.7/dist-packages/docker_registry/drivers/s3.py", line 65, in __init__
    super(Storage, self).__init__(path, config)
  File "/usr/local/lib/python2.7/dist-packages/docker_registry/core/boto.py", line 135, in __init__
    self._config.boto_bucket)
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/connection.py", line 471, in get_bucket
    return self.head_bucket(bucket_name, headers=headers)
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/connection.py", line 490, in head_bucket
    response = self.make_request('HEAD', bucket_name, headers=headers)
  File "/usr/local/lib/python2.7/dist-packages/boto/s3/connection.py", line 633, in make_request
    retry_handler=retry_handler
  File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1046, in make_request
    retry_handler=retry_handler)
  File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 922, in _mexe
    request.body, request.headers)
  File "/usr/lib/python2.7/httplib.py", line 973, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python2.7/httplib.py", line 1007, in _send_request
    self.endheaders(body)
  File "/usr/lib/python2.7/httplib.py", line 969, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python2.7/httplib.py", line 829, in _send_output
    self.send(msg)
  File "/usr/lib/python2.7/httplib.py", line 791, in send
    self.connect()
  File "/usr/lib/python2.7/httplib.py", line 1172, in connect
    self.timeout, self.source_address)
  File "/usr/local/lib/python2.7/dist-packages/gevent/socket.py", line 570, in create_connection
    for res in getaddrinfo(host, port, 0 if has_ipv6 else AF_INET, SOCK_STREAM):
  File "/usr/local/lib/python2.7/dist-packages/gevent/socket.py", line 621, in getaddrinfo
    return get_hub().resolver.getaddrinfo(host, port, family, socktype, proto, flags)
  File "/usr/local/lib/python2.7/dist-packages/gevent/resolver_thread.py", line 34, in getaddrinfo
    return self.pool.apply_e(self.expected_errors, _socket.getaddrinfo, args, kwargs)
  File "/usr/local/lib/python2.7/dist-packages/gevent/threadpool.py", line 225, in apply_e
    raise result
socket.gaierror: [Errno -2] Name or service not known
lxc-start: The container failed to start.
lxc-start: Additional information can be obtained by setting the --logfile and --logpriority options.

Exit after 2 minutes
docker logs 5baf37aa62a3
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
2014-10-14 22:17:17,875 WARNING: Cache storage disabled!
2014-10-14 22:17:17,876 WARNING: LRU cache disabled!
2014-10-14 22:17:18,089 WARNING: No S3 region specified, using boto default region, this may affect performance and stability.

Tried again without S3 Environment variables
[root@com-Len acasanova]# docker logs c82a7cf6e635
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing
2014-10-14 22:20:29,588 WARNING: Cache storage disabled!
2014-10-14 22:20:29,589 WARNING: LRU cache disabled!
2014-10-14 22:20:29,595 DEBUG: Will return docker-registry.drivers.file.Storage
2014-10-14 22:20:31 [1] [INFO] Starting gunicorn 18.0
2014-10-14 22:20:31 [1] [INFO] Listening at: http://<IP_ADDRESS>:5000 (1)
2014-10-14 22:20:31 [1] [INFO] Using worker: gevent
2014-10-14 22:20:31 [16] [INFO] Booting worker with pid: 16
2014-10-14 22:20:31 [17] [INFO] Booting worker with pid: 17
2014-10-14 22:20:31 [18] [INFO] Booting worker with pid: 18
2014-10-14 22:20:31 [23] [INFO] Booting worker with pid: 23
2014-10-14 22:20:31,995 WARNING: Cache storage disabled!
2014-10-14 22:20:31,996 WARNING: LRU cache disabled!
2014-10-14 22:20:32,003 DEBUG: Will return docker-registry.drivers.file.Storage
2014-10-14 22:20:32,053 WARNING: Cache storage disabled!
2014-10-14 22:20:32,054 WARNING: LRU cache disabled!
2014-10-14 22:20:32,059 DEBUG: Will return docker-registry.drivers.file.Storage
2014-10-14 22:20:32,079 WARNING: Cache storage disabled!
2014-10-14 22:20:32,079 WARNING: LRU cache disabled!
2014-10-14 22:20:32,084 DEBUG: Will return docker-registry.drivers.file.Storage
2014-10-14 22:20:32,199 WARNING: Cache storage disabled!
2014-10-14 22:20:32,200 WARNING: LRU cache disabled!
2014-10-14 22:20:32,206 DEBUG: Will return docker-registry.drivers.file.Storage

Docker Version
docker version
Client version: 1.1.2
Client API version: 1.13
Go version (client): go1.2.2
Git commit (client): d84a070/1.1.2
Server version: 1.1.2
Server API version: 1.13
Go version (server): go1.2.2
Git commit (server): d84a070/1.1.2

uname -a
2.6.32-431.17.1.el6.x86_64 #1 SMP Wed May 7 23:32:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

docker info
Images: 54
Storage Driver: devicemapper
 Pool Name: docker-253:0-2098817-pool
 Data file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
 Data Space Used: 1940.2 Mb
 Data Space Total: 102400.0 Mb
 Metadata Space Used: 3.5 Mb
 Metadata Space Total: 2048.0 Mb
Execution Driver: lxc-1.0.5
Kernel Version: 2.6.32-431.17.1.el6.x86_64

Thanks in advance

is this still an issue with the latest version of docker and lxc 1.0.7, or can you try the native driver instead

closing as stale please ping me with details to reproduce on latest and I will reopen


Wrong environment even with "python.terminal.activateEnvironment": false

Environment data

VS Code version: 1.31.1
Extension version (available under the Extensions sidebar): XXX
OS and version: 2019.1.0
Python version (& distribution if applicable, e.g. Anaconda): Anaconda 3.6
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Relevant/affected Python packages and their versions: N/A

Expected behaviour
I have disabled this option: "python.terminal.activateEnvironment": false, because I want "vscode" to inherit the currently active environment from the terminal window from which I launch it.  This is how things used to work up till recently.
Actual behaviour
But even setting this to false, launching vscode with "code ." to open the current working directory, when I start debugging I see it is using a different environment.
Steps to reproduce:

activate the conda environment you want vs code to use:

(ell) d:\Temp\test_models>where python
d:\Anaconda3\envs\ell\python.exe
code .

notice which python the debugger is picking up, notice it is coming from the tensorflow environment which I have not activated in a few days, no idea why it keeps picking this one:

cd 'd:\Temp\test_models'; ${env:PYTHONIOENCODING}='UTF-8'; ${env:PYTHONUNBUFFERED}='1'; & 'd:\Anaconda3\envs\tensorflow\python.exe' 'c:\Users\Chris\.vscode\extensions\ms-python.python-2019.1.0\pythonFiles\ptvsd_launcher.py' '--default' '--client' '--host' 'localhost' '--port' '55113' 'd:\git\ELL\ELL-training\Gallery\test_models.py'

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Starting Jedi Python language engine.
##########Linting Output - flake8##########
29,13,F,F401:'find_ell' imported but unused
30,13,F,F401:'ell' imported but unused
32,29,W,W504:line break after binary operator

Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.

Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.
##########Linting Output - flake8##########

Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.
##########Linting Output - flake8##########
2,1,E,E265:block comment should start with '# '
5,1,E,E266:too many leading '#' for block comment
6,1,E,E266:too many leading '#' for block comment
7,1,E,E266:too many leading '#' for block comment
9,1,E,E266:too many leading '#' for block comment
15,1,F,F401:'datetime.timezone' imported but unused
23,1,F,F401:'traceback' imported but unused
27,1,F,F401:'azure.cosmosdb.table.models.Entity' imported but unused
31,1,F,F401:'ellroot' imported but unused
36,1,E,E302:expected 2 blank lines, found 1
53,1,E,E302:expected 2 blank lines, found 1
96,121,E,E501:line too long (130 > 120 characters)
116,121,E,E501:line too long (142 > 120 characters)
134,1,E,E302:expected 2 blank lines, found 1
141,121,E,E501:line too long (148 > 120 characters)
166,121,E,E501:line too long (140 > 120 characters)
207,9,F,F841:local variable 'root_name' is assigned to but never used
207,31,E,E222:multiple spaces after operator
223,121,E,E501:line too long (151 > 120 characters)
224,121,E,E501:line too long (167 > 120 characters)
266,121,E,E501:line too long (133 > 120 characters)
313,77,E,E261:at least two spaces before inline comment
313,121,E,E501:line too long (123 > 120 characters)
343,17,F,F841:local variable 'e' is assigned to but never used
418,28,E,E222:multiple spaces after operator
418,121,E,E501:line too long (123 > 120 characters)
439,121,E,E501:line too long (129 > 120 characters)
440,121,E,E501:line too long (125 > 120 characters)
443,121,E,E501:line too long (134 > 120 characters)
444,121,E,E501:line too long (131 > 120 characters)
445,121,E,E501:line too long (167 > 120 characters)
448,121,E,E501:line too long (154 > 120 characters)
449,121,E,E501:line too long (180 > 120 characters)
475,1,W,W293:blank line contains whitespace
478,121,E,E501:line too long (187 > 120 characters)

Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.
##########Linting Output - flake8##########
30,13,F,F401:'ell' imported but unused
32,29,W,W504:line break after binary operator

Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.
##########Linting Output - flake8##########
32,29,W,W504:line break after binary operator

Linter 'pylint' is not installed. Please install it or select another linter".
Error: Module 'pylint' not installed.
##########Linting Output - flake8##########

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
notificationsAlerts.ts:40 Unable to open 'launch.json': File not found (file:///d:/Temp/test_models/.vscode/launch.json).
t.onDidNotificationChange @ notificationsAlerts.ts:40
console.ts:134 [Extension Host] Python Extension: Cached data exists getEnvironmentVariables, d:\Temp\test_models
log.ts:173   ERR Data tree node not found: [object Object]: Error: Data tree node not found: [object Object]
    at i.e.getDataNode (file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:1037:266)
    at i.<anonymous> (file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:1034:703)
    at file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:33:935
    at Object.next (file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:34:33)
    at file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:33:160
    at new Promise (<anonymous>)
    at i (file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:32:952)
    at i.e.expand (file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:1034:342)
    at Array.<anonymous> (file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:5627:417)
    at t (file:///C:/Users/Chris/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:105:891)
    at process._tickCallback (internal/process/next_tick.js:68:7)
console.ts:134 [Extension Host] Python Extension: Cached data exists getEnvironmentVariables, tasks
console.ts:134 [Extension Host] Python Extension: Cached data exists getEnvironmentVariables, extension-output-#4```

I have similar problem and spent one afternoon to locate the problem.
I'm using newest VScode Insider with anaconda. If I let the integrated terminal automatically load the conda environment, which python would return the /usr/bin/python which is the default one.

Yeah, the only work around I've found so far is to manually override the "pythonPath" in each of my "launch.json" as shown below.   This is not ideal because I sping up new working directories all day long so I'm getting tired of having to do this in each one...
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File (Integrated Terminal)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "debugStdLib": true,
            "pythonPath": "d:\\Anaconda3\\envs\\ell\\python.exe",

Yeah, the only work around I've found so far is to manually override the "pythonPath" in each of my "launch.json" as shown below. This is not ideal because I spin up new working directories all day long so I'm getting tired of having to do this in each one...
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File (Integrated Terminal)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "debugStdLib": true,
            "pythonPath": "d:\\Anaconda3\\envs\\ell\\python.exe",

Thanks for your working around. I just downgraded vscode to last stable version which works fine with newest Python extension. Expect to see quick fix for that.

Terminals in VSCode do not inherit the currently active python interpreter when launching VSC via a terminal.
Unfortunately this isn't a supported scenario, as the Shell within the VSC terminal doesn't inherit the VSC environment, they are separate processes.
Initially the expectation is to manually set the python path,
You do not have to go into the file, you can always use the UI, use the command Python Select Interpreter


Run CIS Scan - User Skipped tests font can be modified to make it more noticeable

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Go to System Project --> Config
Create a config map
name: "security-scan-cfg"
key: "config.json"
value: {"skip":{"rke-cis-1.4":["1.1.11","1.1.15"}}
Refresh CIS scans page (as there is an issue currently)
Click on Run Scan
The pop up window is like

Expected Result:
The skipped tests' font can be modified to make it noticeable
Other details that may be helpful:
Related to : https://github.com/rancher/rancher/issues/26066
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - ui tag: latest2
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): rke do
Kubernetes version (use kubectl version):

1.17

I can't reproduce this but paired with @codyrancher and came up with this option

Let us know if this works. Another alternative would be to list the config skips in an additional accoridon.

@codyrancher @lvuch This looks good to me.

verified on latest master-head - commit id: ae4a76a7e ui tag: latest2
On a run scan, with user added skips in the config map, the UI is seen as


updateLayout being called on components whose layout isn't updated

I was noticing performance issues when creating a UI panel that faded into the scene, and saw from profiling that updateLayout was being called every single frame for the components, even though the layout hadn't been changed.
Further digging suggests that this is a result of https://github.com/felixmariotto/three-mesh-ui/blob/83b9e52e818bf682de3b707e41ad9e9654fb9aa1/src/components/core/MeshUIComponent.js#L483 -- by default, parent.getBestFit() will always be true since it's set to 'none' by default -- which is truthy, causing an updateLayout call with every update.

Hi @dmliao there's already a PR open with this fix here #141. Just waiting for @felixmariotto to merge it in!

@GoncaloBastos thank you for the fix, it's published as 6.3.0


Correction required in Chapter

Chap
The block at the end should say 'Model Output'

Thanks for spotting this! Gently pinging @Bibi-O for a fix when you have time :)

Thanks for the observation! Would fix it now! :)

Hi, I think I spotted a similar typo a few paragraphs below the figure:

I was going to just do a pull request, but saw this and figured it would be easier to bring up here ☺  (I don't have the repo cloned)


fix: missed case in "ring-compare"

The "ring-based prover for certain inequalities in semirings" added in #16840 missed a case, which I noticed when I started experimenting with the new linear_combination-for-inequalities (for which it serves as the discharger).  Namely, it would not prove e1 ≤ e2 if e1 and e2 ring-normalized to the same expression, and that expression had no numeric constant term.

bors merge


Ensure 1password doesn't change amount on autofill

What's this PR do?
Prevents 1password's credit-card autofill feature from changing the amount a user originally entered. There's weirdness between 1Password and the Stripe modal: Whatever card-expiration month the former fills in also gets dropped into the Flask form's amount input.
Anna H. reported this and sent along some code a VOSD developer wrote to fix it. It seemed overly complicated, though: I'm simply setting the amount field to readonlywhen the Stripe modal is open. It seems to work.
Why are we doing this? How does it help us?
To ensure people don't give the wrong amount.
How should this be manually tested?

make backing
make interactive
python3 app.py
Add a credit card to 1password and ensure you have the browser extension installed
On both /donateform and /memberform, fill out the form as normal, then click "Pay By Card." Use 1password to autofill the credit-card information. Confirm that doing so does not change the input amount in the form below the overlay. Close the Stripe modal and confirm the amount field is editable again.
On /circleform, once again fill out the form, hit "Pay by Card," and autofill the credit card info with 1password. Confirm the amount in the Flask form does not change. Close the Stripe modal and confirm the amount field is still read-only.
 (I tested there, too.)
If an iPhone user with the 1password app installed can try this (this branch is on staging), that'd be grand. I'll take care of Android.

Have automated tests been added?
No.
Has this been tested on mobile?
I tested successfully on desktop Chrome, Firefox and Safari. I feel pretty good about those results.
Are there performance implications?
No.
What are the relevant tickets?
https://3.basecamp.com/3098728/buckets/736178/todos/784219601
How should this change be communicated to end users?
NA.
Next steps?
NA.
Smells?
Toggling read-only on the amount input is a slight smell, but it's not much code, either.
TODOs:
NA.
Has the relevant documentation/wiki been updated?
NA.
Technical debt note
A tiny bit more.

I did all the testing you describe except the iPhone part. I don't think there's an automatic way to fill in credit card details with the 1Password app on iPhone.
LGTM


Spelling mistake in Footer

Description of the bug. ✍🏻
The spelling of "useful" is shown as "usefull" in the the footer section(useful links part)
Current Behaviour
Wrong spelling might give a bad impression to the user.
Expected Behaviour
Change the spelling to 'useful'
Reproduction Steps
No response
Screenshots
No response
Additional information
No response
Contributor terms

[X] I agree to follow the Contributing Instructions

Assign this issue under GSSOC '23.I'll raise the PR within 2 days.

Assign this issue under GSSOC '23

Hey @Uma-95 I would like to resolve this issue.
I'm a contributor to GSSOC'23 please assign this issue to me as a part of GSSOC'23 .

Please assign this issue to me. Kindly assign it to me under gssoc23 @praveenscience

@praveenscience  could you please assign this issue to me as a part of GSSOC'23.

hi @praveenscience could you please assign me this task under GSSoC'23

@praveenscience I would like to work on this issue could you please assign it to me under GSSoC23.
Thank you!


Build from source failed for older rust

$ cargo --version
cargo 1.76.0 (c84b36747 2024-01-18)

cargo install hawkeye throw following errors:
  Compiling hawkeye v5.8.1
error: unsupported output in build script of `hawkeye v5.8.1`: `cargo::rustc-env=SOURCE_TIMESTAMP=`
Found a `cargo::key=value` build directive which is reserved for future use.
Either change the directive to `cargo:key=value` syntax (note the single `:`) or upgrade your version of Rust.
See https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script for more information about build script outputs.
error: failed to compile `hawkeye v5.8.1`, intermediate artifacts can be found at `/var/folders/my/m6b0f0pn6b5dhx85_pzlvhzm0000gp/T/cargo-installPi3wh2`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

rustup update fix this.

https://github.com/korandoru/hawkeye/actions/runs/11433488465/job/31805559855?pr=161
Interesting. This run verifies 1.76.0 builds well.

This run verifies 1.76.0 builds well.

Could you try build on macOS?

OK. Reproduced and fixed - https://github.com/korandoru/hawkeye/pull/161/commits/365a3e02749fb992c73b565b60d6f471f7cf1171


internal/coverage: internal error in coverage meta-data tracking encountered bad pkgID list of hard-coded runtime package IDs needs revising.

Go version
golang:1.22-alpine
Output of go env in your module/workspace:
Not sure the best way to do this from the Dockerfile in the github action?

What did you do?
Ran the following github action:
https://github.com/joe-at-startupmedia/pmon3/blob/5cc0fc72173f6ec021074152bb4d09945cac2324/.github/workflows/testing.yml
From the following Dockerfile:
https://github.com/joe-at-startupmedia/pmon3/blob/5cc0fc72173f6ec021074152bb4d09945cac2324/Dockerfile
Using the following Makefile command:
PROJECT_PATH=/opt/pmon3 go test  -v -run Test -p 1 -coverprofile=coverage.txt -covermode atomic -coverpkg=pmon3/cli,pmon3/cli/cmd,pmon3/cli/cmd/base,pmon3/cli/cmd/completion,pmon3/cli/cmd/del,pmon3/cli/cmd/desc,pmon3/cli/cmd/dgraph,pmon3/cli/cmd/drop,pmon3/cli/cmd/exec,pmon3/cli/cmd/export,pmon3/cli/cmd/group,pmon3/cli/cmd/group/assign,pmon3/cli/cmd/group/create,pmon3/cli/cmd/group/del,pmon3/cli/cmd/group/desc,pmon3/cli/cmd/group/drop,pmon3/cli/cmd/group/list,pmon3/cli/cmd/group/remove,pmon3/cli/cmd/group/restart,pmon3/cli/cmd/group/stop,pmon3/cli/cmd/init,pmon3/cli/cmd/kill,pmon3/cli/cmd/list,pmon3/cli/cmd/log,pmon3/cli/cmd/logf,pmon3/cli/cmd/reset,pmon3/cli/cmd/restart,pmon3/cli/cmd/stop,pmon3/cli/cmd/topn,pmon3/cli/output/group/list,pmon3/cli/output/process/desc,pmon3/cli/output/process/list,pmon3/cli/output/process/one,pmon3/conf,pmon3/pmond,pmon3/pmond/controller,pmon3/pmond/controller/base,pmon3/pmond/controller/base/del,pmon3/pmond/controller/base/exec,pmon3/pmond/controller/base/restart,pmon3/pmond/controller/base/stop,pmon3/pmond/controller/group,pmon3/pmond/db,pmon3/pmond/god,pmon3/pmond/model,pmon3/pmond/observer,pmon3/pmond/process,pmon3/pmond/repo ./test/e2e/...

What did you see happen?
internal error in coverage meta-data tracking:
encountered bad pkgID: 0  at slot: 352  fnID: 2  numCtrs: 2
list of hard-coded runtime package IDs needs revising.
[see the comment on the 'rtPkgs' var in
 <goroot>/src/internal/coverage/pkid.go]
registered list:
slot: 0 path='pmon3/pmond/controller/base'
slot: 1 path='pmon3/pmond/model'
slot: 2 path='pmon3/conf'
slot: 3 path='pmon3/cli'
slot: 4 path='pmon3/pmond'
slot: 5 path='pmon3/pmond/observer'
slot: 6 path='pmon3/cli/output/group/list'
slot: 7 path='pmon3/cli/output/process/list'
slot: 8 path='pmon3/cli/output/process/desc'
slot: 9 path='pmon3/cli/output/process/one'
slot: 10 path='pmon3/cli/cmd/base'
slot: 11 path='pmon3/cli/cmd/del'
slot: 12 path='pmon3/cli/cmd/desc'
slot: 13 path='pmon3/cli/cmd/export'
slot: 14 path='pmon3/cli/cmd/group/desc'
slot: 15 path='pmon3/cli/cmd/group/assign'
slot: 16 path='pmon3/cli/cmd/group/drop'
slot: 17 path='pmon3/cli/cmd/group/list'
slot: 18 path='pmon3/cli/cmd/group/create'
slot: 19 path='pmon3/cli/cmd/group/del'
slot: 20 path='pmon3/cli/cmd/group/remove'
slot: 21 path='pmon3/cli/cmd/group/stop'
slot: 22 path='pmon3/cli/cmd/list'
slot: 23 path='pmon3/cli/cmd/drop'
slot: 24 path='pmon3/cli/cmd/exec'
slot: 25 path='pmon3/cli/cmd/group/restart'
slot: 26 path='pmon3/cli/cmd/init'
slot: 27 path='pmon3/cli/cmd/kill'
slot: 28 path='pmon3/cli/cmd/reset'
slot: 29 path='pmon3/cli/cmd/topn'
slot: 30 path='pmon3/pmond/db'
slot: 31 path='pmon3/pmond/repo'
slot: 32 path='pmon3/pmond/process'
slot: 33 path='pmon3/pmond/controller/base/exec'
slot: 34 path='pmon3/pmond/controller/base/restart'
slot: 35 path='pmon3/pmond/controller/base/stop'
slot: 36 path='pmon3/pmond/controller/base/del'
slot: 37 path='pmon3/pmond/controller/group'
slot: 38 path='pmon3/pmond/controller'
slot: 39 path='pmon3/pmond/god'
remap table:

internal error in coverage meta-data tracking:
encountered bad pkgID: 0  at slot: 360  fnID: 3  numCtrs: 2
list of hard-coded runtime package IDs needs revising.
[see the comment on the 'rtPkgs' var in
 <goroot>/src/internal/coverage/pkid.go]
registered list:
slot: 0 path='pmon3/pmond/controller/base'
slot: 1 path='pmon3/pmond/model'
slot: 2 path='pmon3/conf'
slot: 3 path='pmon3/cli'
slot: 4 path='pmon3/pmond'
slot: 5 path='pmon3/pmond/observer'
slot: 6 path='pmon3/cli/output/group/list'
slot: 7 path='pmon3/cli/output/process/list'
slot: 8 path='pmon3/cli/output/process/desc'
slot: 9 path='pmon3/cli/output/process/one'
slot: 10 path='pmon3/cli/cmd/base'
slot: 11 path='pmon3/cli/cmd/del'
slot: 12 path='pmon3/cli/cmd/desc'
slot: 13 path='pmon3/cli/cmd/export'
slot: 14 path='pmon3/cli/cmd/group/desc'
slot: 15 path='pmon3/cli/cmd/group/assign'
slot: 16 path='pmon3/cli/cmd/group/drop'
slot: 17 path='pmon3/cli/cmd/group/list'
slot: 18 path='pmon3/cli/cmd/group/create'
slot: 19 path='pmon3/cli/cmd/group/del'
slot: 20 path='pmon3/cli/cmd/group/remove'
slot: 21 path='pmon3/cli/cmd/group/stop'
slot: 22 path='pmon3/cli/cmd/list'
slot: 23 path='pmon3/cli/cmd/drop'
slot: 24 path='pmon3/cli/cmd/exec'
slot: 25 path='pmon3/cli/cmd/group/restart'
slot: 26 path='pmon3/cli/cmd/init'
slot: 27 path='pmon3/cli/cmd/kill'
slot: 28 path='pmon3/cli/cmd/reset'
slot: 29 path='pmon3/cli/cmd/topn'
slot: 30 path='pmon3/pmond/db'
slot: 31 path='pmon3/pmond/repo'
slot: 32 path='pmon3/pmond/process'
slot: 33 path='pmon3/pmond/controller/base/exec'
slot: 34 path='pmon3/pmond/controller/base/restart'
slot: 35 path='pmon3/pmond/controller/base/stop'
slot: 36 path='pmon3/pmond/controller/base/del'
slot: 37 path='pmon3/pmond/controller/group'
slot: 38 path='pmon3/pmond/controller'
slot: 39 path='pmon3/pmond/god'
remap table:

internal error in coverage meta-data tracking:
encountered bad pkgID: 0  at slot: 632  fnID: 1  numCtrs: 3
list of hard-coded runtime package IDs needs revising.
[see the comment on the 'rtPkgs' var in
 <goroot>/src/internal/coverage/pkid.go]
registered list:
slot: 0 path='pmon3/pmond/controller/base'
slot: 1 path='pmon3/pmond/model'
slot: 2 path='pmon3/conf'
slot: 3 path='pmon3/cli'
slot: 4 path='pmon3/pmond'
slot: 5 path='pmon3/pmond/observer'
slot: 6 path='pmon3/cli/output/group/list'
slot: 7 path='pmon3/cli/output/process/list'
slot: 8 path='pmon3/cli/output/process/desc'
slot: 9 path='pmon3/cli/output/process/one'
slot: 10 path='pmon3/cli/cmd/base'
slot: 11 path='pmon3/cli/cmd/del'
slot: 12 path='pmon3/cli/cmd/desc'
slot: 13 path='pmon3/cli/cmd/export'
slot: 14 path='pmon3/cli/cmd/group/desc'
slot: 15 path='pmon3/cli/cmd/group/assign'
slot: 16 path='pmon3/cli/cmd/group/drop'
slot: 17 path='pmon3/cli/cmd/group/list'
slot: 18 path='pmon3/cli/cmd/group/create'
slot: 19 path='pmon3/cli/cmd/group/del'
slot: 20 path='pmon3/cli/cmd/group/remove'
slot: 21 path='pmon3/cli/cmd/group/stop'
slot: 22 path='pmon3/cli/cmd/list'
slot: 23 path='pmon3/cli/cmd/drop'
slot: 24 path='pmon3/cli/cmd/exec'
slot: 25 path='pmon3/cli/cmd/group/restart'
slot: 26 path='pmon3/cli/cmd/init'
slot: 27 path='pmon3/cli/cmd/kill'
slot: 28 path='pmon3/cli/cmd/reset'
slot: 29 path='pmon3/cli/cmd/topn'
slot: 30 path='pmon3/pmond/db'
slot: 31 path='pmon3/pmond/repo'
slot: 32 path='pmon3/pmond/process'
slot: 33 path='pmon3/pmond/controller/base/exec'
slot: 34 path='pmon3/pmond/controller/base/restart'
slot: 35 path='pmon3/pmond/controller/base/stop'
slot: 36 path='pmon3/pmond/controller/base/del'
slot: 37 path='pmon3/pmond/controller/group'
slot: 38 path='pmon3/pmond/controller'
slot: 39 path='pmon3/pmond/god'
remap table:
coverage: 73.6% of statements in pmon3/cli, pmon3/cli/cmd, pmon3/cli/cmd/base, pmon3/cli/cmd/completion, pmon3/cli/cmd/del, pmon3/cli/cmd/desc, pmon3/cli/cmd/dgraph, pmon3/cli/cmd/drop, pmon3/cli/cmd/exec, pmon3/cli/cmd/export, pmon3/cli/cmd/group, pmon3/cli/cmd/group/assign, pmon3/cli/cmd/group/create, pmon3/cli/cmd/group/del, pmon3/cli/cmd/group/desc, pmon3/cli/cmd/group/drop, pmon3/cli/cmd/group/list, pmon3/cli/cmd/group/remove, pmon3/cli/cmd/group/restart, pmon3/cli/cmd/group/stop, pmon3/cli/cmd/init, pmon3/cli/cmd/kill, pmon3/cli/cmd/list, pmon3/cli/cmd/log, pmon3/cli/cmd/logf, pmon3/cli/cmd/reset, pmon3/cli/cmd/restart, pmon3/cli/cmd/stop, pmon3/cli/cmd/topn, pmon3/cli/output/group/list, pmon3/cli/output/process/desc, pmon3/cli/output/process/list, pmon3/cli/output/process/one, pmon3/conf, pmon3/pmond, pmon3/pmond/controller, pmon3/pmond/controller/base, pmon3/pmond/controller/base/del, pmon3/pmond/controller/base/exec, pmon3/pmond/controller/base/restart, pmon3/pmond/controller/base/stop, pmon3/pmond/controller/group, pmon3/pmond/db, pmon3/pmond/god, pmon3/pmond/model, pmon3/pmond/observer, pmon3/pmond/process, pmon3/pmond/repo
ok  	pmon3/test/e2e	218.039s	coverage: 73.6% of statements in pmon3/cli, pmon3/cli/cmd, pmon3/cli/cmd/base, pmon3/cli/cmd/completion, pmon3/cli/cmd/del, pmon3/cli/cmd/desc, pmon3/cli/cmd/dgraph, pmon3/cli/cmd/drop, pmon3/cli/cmd/exec, pmon3/cli/cmd/export, pmon3/cli/cmd/group, pmon3/cli/cmd/group/assign, pmon3/cli/cmd/group/create, pmon3/cli/cmd/group/del, pmon3/cli/cmd/group/desc, pmon3/cli/cmd/group/drop, pmon3/cli/cmd/group/list, pmon3/cli/cmd/group/remove, pmon3/cli/cmd/group/restart, pmon3/cli/cmd/group/stop, pmon3/cli/cmd/init, pmon3/cli/cmd/kill, pmon3/cli/cmd/list, pmon3/cli/cmd/log, pmon3/cli/cmd/logf, pmon3/cli/cmd/reset, pmon3/cli/cmd/restart, pmon3/cli/cmd/stop, pmon3/cli/cmd/topn, pmon3/cli/output/group/list, pmon3/cli/output/process/desc, pmon3/cli/output/process/list, pmon3/cli/output/process/one, pmon3/conf, pmon3/pmond, pmon3/pmond/controller, pmon3/pmond/controller/base, pmon3/pmond/controller/base/del, pmon3/pmond/controller/base/exec, pmon3/pmond/controller/base/restart, pmon3/pmond/controller/base/stop, pmon3/pmond/controller/group, pmon3/pmond/db, pmon3/pmond/god, pmon3/pmond/model, pmon3/pmond/observer, pmon3/pmond/process, pmon3/pmond/repo

What did you expect to see?
coverage report generated without any errors

link to the workflow:
https://github.com/joe-at-startupmedia/pmon3/actions/runs/11229544280/job/31215693823
Can you access this? I am new to Github Actions and not sure how Authorization is handled to the workflows of public repos.
Note: The reason for all of the explicitly provided packages to the -coverpkg command is because when those aren't provided the workflow fails before executing the codecov-cli command. I suspect it has something to do with the array utils package (using generics) which is one of several packages I omitted in troubleshooting the issue.
This is a workflow with wildcarded packages to specifically omit the pmon3/cmd package from code coverage.
https://github.com/joe-at-startupmedia/pmon3/actions/runs/11229983225/job/31216483763
Both the Dockerfile and workflow file are the same but the Makefile has been modified to issue the following test command:
PROJECT_PATH=/opt/pmon3 go test  -v -run Test -p 1 -coverprofile=coverage.txt -covermode atomic -coverpkg=pmon3/pmond/...,pmon3/cli/...,pmon3/conf/...  ./test/e2e/...

https://github.com/joe-at-startupmedia/pmon3/actions/runs/11229983225/job/31216483763#step:7:846

Does this reproduce with 1.23?

Give me a day or two, I will try to replicate on 1.23.

Same problem in 1.23.2 (the workflow fails), except the output seems to have more remap tables
using the following args for go test
PROJECT_PATH=/opt/pmon3 ARTIFACT_PATH=/tmp/pmon3 go test  -v -run Test -p 1 -coverprofile=coverage.txt -coverpkg=pmon3/pmond/...,pmon3/cli/...,pmon3/conf/... ./test/e2e/

Workflow:
https://github.com/joe-at-startupmedia/pmon3/actions/runs/11265050732/job/31326198133
Next, when all list of packages are provided the workflow produces similar errors but passes:
coverpkf value:
pmon3/cli,pmon3/cli/cmd,pmon3/cli/cmd/base,pmon3/cli/cmd/completion,pmon3/cli/cmd/del,pmon3/cli/cmd/desc,pmon3/cli/cmd/dgraph,pmon3/cli/cmd/drop,pmon3/cli/cmd/exec,pmon3/cli/cmd/export,pmon3/cli/cmd/group,pmon3/cli/cmd/group/assign,pmon3/cli/cmd/group/create,pmon3/cli/cmd/group/del,pmon3/cli/cmd/group/desc,pmon3/cli/cmd/group/drop,pmon3/cli/cmd/group/list,pmon3/cli/cmd/group/remove,pmon3/cli/cmd/group/restart,pmon3/cli/cmd/group/stop,pmon3/cli/cmd/init,pmon3/cli/cmd/kill,pmon3/cli/cmd/list,pmon3/cli/cmd/log,pmon3/cli/cmd/logf,pmon3/cli/cmd/reset,pmon3/cli/cmd/restart,pmon3/cli/cmd/stop,pmon3/cli/cmd/topn,pmon3/cli/output/group/list,pmon3/cli/output/process/desc,pmon3/cli/output/process/list,pmon3/cli/output/process/one,pmon3/cli/shell,pmon3/conf,pmon3/pmond,pmon3/pmond/controller,pmon3/pmond/controller/base,pmon3/pmond/controller/base/del,pmon3/pmond/controller/base/exec,pmon3/pmond/controller/base/restart,pmon3/pmond/controller/base/stop,pmon3/pmond/controller/group,pmon3/pmond/db,pmon3/pmond/god,pmon3/pmond/model,pmon3/pmond/observer,pmon3/pmond/process,pmon3/pmond/repo,pmon3/pmond/shell
Workflow error:
https://github.com/joe-at-startupmedia/pmon3/actions/runs/11265284155/job/31326859531#step:7:807
The workflow has been modified to accept an input for the -coverpkg flag for:

Let me know if there is a different -coverpkg value  or any other test flags I can try.

@seankhliao @cherrymui
Any updates on this? Just to clarify, this seems to be an issue on Docker only, I cannot replicate this in my own vagrant development environment.
To reiterate the errors are are consistently in the following format, albeit with says slot and fnIds:
2024-10-12T04:54:01.8289993Z
2024-10-12T04:54:01.8290186Z internal error in coverage meta-data tracking:
2024-10-12T04:54:01.8290398Z encountered bad pkgID: 0  at slot: 2312  fnID: 22  numCtrs: 15
2024-10-12T04:54:01.8290630Z list of hard-coded runtime package IDs needs revising.
2024-10-12T04:54:01.8290789Z [see the comment on the 'rtPkgs' var in
2024-10-12T04:54:01.8290928Z  <goroot>/src/internal/coverage/pkid.go]

This does not gurantee a workflow failure unless it finishes with the following:
2024-10-12T04:54:01.8299408Z error generating coverage report: processing counter data file /tmp/go-build58082508/b002/gocoverdir/covcounters.95fecc14757cb6b01b889a3437a09fda.7086.1728708841745835415: merging counters: len(dst)=4 len(src)=1

This is the latest failing workflow those error messages were grabbed from:
https://github.com/joe-at-startupmedia/pmon3/actions/runs/11302814723
Using the following test args:
PROJECT_PATH=/opt/pmon3 ARTIFACT_PATH=/tmp/pmon3 go test  -v -run "Test" -p 1 -coverprofile=coverage.txt -coverpkg="pmon3/cli/...,pmon3/conf,pmon3/pmond/controller/...,pmon3/pmond/db,pmon3/pmond/flap_detector,pmon3/pmond/god,pmon3/pmond/model,pmon3/pmond/observer,pmon3/pmond/process,pmon3/pmond/repo,pmon3/pmond/shell" ./test/e2e/

cc @golang/runtime

cc @thanm
Does this ring any bells?  Cherry thinks we just need to regenerate a list?

cc @thanm Does this ring any bells? Cherry thinks we just need to regenerate a list?

In this situation no, it's not just a question of regenerating a list; that's applicable only if runtime packages are part of the set of packages being instrumented for coverage. See this comment for a but more about why hard-coded package IDs are needed and how they are used.
The zero package ID points more to coverage counter memory being corrupted - a zero package ID indicates that the init function for package X ran, it filled a none-zero package ID, the program ran some more, and then at program or test termination when slot of memory containing the package ID somehow now has a zero in it.
I'm tied up at the moment but I can try to take a closer look towards the end of this week. If it is a public github repo I can try running the test under the debugger to see what's going on.


experiment: remove Debug traits from region rts to reduce rts size

Remove Debug traits from RTS, replacing handfull of assert_eq! by assert!.
< -rwxr-xr-x 1 crusso crusso 2717540 Jul 20 14:55 mo-rts-debug.wasm
< -rwxr-xr-x 1 crusso crusso 2885372 Jul 20 14:55 mo-rts-incremental-debug.wasm
< -rwxr-xr-x 1 crusso crusso  165883 Jul 20 14:55 mo-rts-incremental.wasm
< -rwxr-xr-x 1 crusso crusso  163350 Jul 20 14:54 mo-rts.wasm
---
> -rwxr-xr-x 1 crusso crusso 2698430 Jul 20 16:05 mo-rts-debug.wasm
> -rwxr-xr-x 1 crusso crusso 2866281 Jul 20 16:05 mo-rts-incremental-debug.wasm
> -rwxr-xr-x 1 crusso crusso  163155 Jul 20 16:05 mo-rts-incremental.wasm
> -rwxr-xr-x 1 crusso crusso  160804 Jul 20 16:05 mo-rts.wasm

Perhaps not worth the effort.

Wrong base branch?

Just doing some repo cleanup for better focussing on active work:
Closing PR as it seems inactive for a longer time. Please re-open if it is still relevant and after it has been updated with latest master changes.


[Slider] Prevent default for Home and End keys

Closes #1054

Description
As titled

@luisorbaiceta there is a bit of a gotcha with our versioning 🙈
Can you run it again and deny the workspace please?

No problem! 👍

For some reason I don't seem to have access to CHROMATIC_PROJECT_TOKEN 🤷♂ Is this expected?

@luisorbaiceta Yep, but to be honest I wouldn't expect your change cause any visual regressions.
@andy-hook @benoitgrelard Shall we just merge this or think it's worth doing our usual PR branching dance still?

@luisorbaiceta Yep, but to be honest I wouldn't expect your change to cause any visual regressions.

Will this change in the future? I'm planning to spend time in the long term contributing to this project

Shall we just merge this or think it's worth doing our usual PR branching dance still?

@jjenzz I’d prefer if we stayed consistent tbh, inconvenient as it is 😅

I'm planning to spend time in the long term contributing to this project

@luisorbaiceta That's great!

Will this change in the future?

Do you mean access to secrets in code forked PRs?

Do you mean access to secrets in code forked PRs?

A way to check if changes have visual regressions. Chromatic suggests this:

Don't know if this is convenient though...

@luisorbaiceta yes we were doing that but unfortunately, if the project-token is a secret that prevents external contributors from running chromatic.
I've just merged a PR which should fix all this. Would you mind pulling latest from main and pushing your branch again so we can see if it all works okay?

Sure! Done @jjenzz

Thanks @luisorbaiceta , you should be able to see this in the next release candidate shortly 🎉


monitoring spec machine

add property, validation monitoring spec machine

Coverage increased (+0.07%) to 59.526% when pulling 3bc0b72cfe6cab10b99a80b361f03891a74292e2 on adityahenanda:dev into 88b79418b25d9712e63820c49ff767f1ab4d1118 on danliris:dev.


Ability to enable/disable hashing for each  model in any area without any need to enable/disable the whole area

When we need to enable hashing for model X in a certain area we must add the area to config('cortex.foundation.obscure') that mean hashing will apply on all models in the area not only
model X this is not the best solution also in case we need to disable hashing for model in area added to  config('cortex.foundation.obscure')  we won't able to do that so we should make the model itself have the control enable/disable hashing in any area if we need to do that.

Thank you, merged!


ParserError first time running plotman

Discussed in https://github.com/ericaltendorf/plotman/discussions/932

Originally posted by hutchwilco September 30, 2021
I've got the following error when running plotman interactive
I've checked the yaml, several online yaml validators confirm my check.
The only thing is I'm running on a machine that had chia installed via the experimental .deb file rather than "git install" that I'm used to. So I've not activated an environment when running this. Plotman is installed in /home//.local/bin/
Any help would be appreciated. plotman v 0.5.3

raise ParserError("while parsing a block mapping", self.marks[-1],

yaml.parser.ParserError: while parsing a block mapping
in "", line 44, column 9:
tmp: /mnt/ram
^
expected , but found ''
in "", line 51, column 10:
tmp2: /mnt/nvme1
^

This doesn't seem to be a bug, at least not yet, so we can just discuss it over at https://github.com/ericaltendorf/plotman/discussions/932.


Introduction to Static Application Security Testing Method

Article checklist
Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[ ] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[ ] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[ ] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes
This closes #3538

@srishilesh I will like to review this article
CC @hectorkambow

@srishilesh I will like to review this article
CC @hectorkambow

@section-engineering-education/content-moderator-team

@ahmadmardeni1
@WanjaMIKE

@RuthAMare, please ensure you link your topic suggestion to your PR.

Done @louisefindlay23

Done @louisefindlay23

You still need to remove the backticks, @RuthAMare.

@louisefindlay23
@WanjaMIKE


Convert alpha value to an icon. Change layer's opacity value from 1α, 0.5α, to 0α.

Implemented the enhancement for issue #841. Here is a video demoing the enhancement. Ran grunt test which completed without errors.

Thanks for the PR! However, this is not really what I had in mind.
Users should still be able te decide which value they want for the opacity. But the representation of the opacity should just be an icon (therefore fixed-width) which has 3 states:

opacity == 1 -> icon is fully opaque
0 < opacity < 1-> icon is intermediary state
opacity == 0 -> icon looks "empty"

The first step here is to create this "3 states" icon.

Sure thing! So I'll modify the icon to have three states which use a color to represent the opacity value set by the user. The colors for each state as you suggested in #841 being...

opacity == 1 -> icon is fully opaque, color: white
0 < opacity < 1-> icon is intermediary state, color: gray
opacity == 0 -> icon looks "empty", color: black (black outline)


Python 3 type hints are broken/unusuable

Type hints for init are broken, blocked on https://github.com/python/mypy/issues/4441
We want to have type hints in the docs. There is no tooling for this afaik

ref #270
ref https://github.com/getsentry/sentry-docs/issues/789

BTW right now the type hints using ClientOptions are broken. kwargs for Client are not validated at all.

First step towards this in #401, but my god it's ugly.


Configuration of SequencingPolicy only in deprecated methods

Currently, sequencing policies can only be configured using deprecated methods on the EventHandlingConfiguration class.
It should remain possible to configure a SequencingPolicy per processing group (or a default one for all handlers).
Furthermore, the javadoc on some methods on the EventProcessingConfiguration still refer to a sequencing policy, even if the methods don't accept one as parameter.

Now part of 3.3.4, as commit 9742a8f has been pushed. Closing this issue as a result of that.


iRule regex parsing might cause an indefinite hang

Environment

ACC Version: 1.18
AS3 Version: N/A
BIG-IP Version: N/A

Summary
Found in a client UCS archive.
Parsing the following conf file causes ACC to become unresponsive, likely stuck in an infinite loop with 100% CPU usage. The freeze seems to only happen when there's another ltm rule object somewhere after the one with this problematic regex, otherwise we get a regular exception.
Steps To Reproduce
Steps to reproduce the behavior:

Convert following config:

ltm rule /tenant_268/application_268/l4j {
when HTTP_REQUEST_DATA {
  set tmpPayload [HTTP::payload]
  set payload [URI::decode $tmpPayload]
  while { $payload ne $tmpPayload } {
    set tmpPayload $payload
    set payload [URI::decode $tmpPayload]
  }

  if {[string tolower $payload] matches_regex {\$\{\s*(j|\$\{).+?\}}} {
    drop
    event disable all
  }
}
}
ltm rule /tenant_268/application_268/foo {

}

ACC is now frozen indefinitely.

Note that if we attempt to convert the first iRule without including the second one (or replacing it with any object, e.g. ltm pool), we get the following error:
/app/src/engines/parser.js:150
                if (!(line.trim().startsWith('#') && ruleFlag)) {
                           ^

TypeError: Error parsing input file. Please open an issue at https://github.com/f5devcentral/f5-automation-config-converter/issues and include the following error:
Cannot read properties of undefined (reading 'trim')
    at groupObjects (/app/src/engines/parser.js:150:28)
    at /app/src/engines/parser.js:255:30
    at Array.forEach (<anonymous>)
    at module.exports (/app/src/engines/parser.js:184:28)
    at mainRunner (/app/src/main.js:39:18)
    at main (/app/src/main.js:128:30)

Thank you for the report, I've added this to our internal backlog as CHARON-584 and will get this prioritized.

Fixed in 1.19


Reconstruct should consider shard buffer capacity

Currently reconstruct data and reconstruct parity allocate a new shard when the shard is marked as missing (len(shard) == 0).
Reconstruct should check whether the capacity of the shard is large enough to avoid the allocation whenever possible.

Fixed. Thanks for the report


Tests for Firebase API

Short description
Tests for the firebase API client functions
Proposed changes

Mock-tests for the firebase API client functions (pushNotificationSender)
Resolved issues
Tests for api_client_firebase #1824

#1824

Pull Request Review Guidelines

Added the tests directly to the "move firebase api to seperate app" PR
So I close it here


Resistance phenotype missing

There are apparently values (see screenshot), but it is not defined as susceptible, resistant or intermediate.
https://www.patricbrc.org/view/Antibiotic/?eq(antibiotic_name,chloramphenicol)#view_tab=amr

We solely rely on the SIR phenotypes provided by BioSample/collaborators/publications.
In other words, we do not compare given MIC values to  CLSI/EUCAST breakpoints to
infer SIR phenotypes. S, you may have situations where MIC is present but SIR is missing.
We have discussed automated translation of MIC to SIR in past, but it hasn’t happened yet.
-Maulik

On Apr 18, 2017, at 11:13 AM, hyoo<EMAIL_ADDRESS>wrote:
Assigned #1456 https://github.com/PATRIC3/patric3_website/issues/1456 to @mshukla1 https://github.com/mshukla1.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/PATRIC3/patric3_website/issues/1456#event-1046975431, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLd71Zl7jqLah7MQfLuufB6RHIDoUTyks5rxOEPgaJpZM4Mu06l.

@mshukla1 OR @ARWattam should we close this ticket?

Yes, I think we should close it.
Rebecca
On Wed, Apr 26, 2017 at 4:47 PM, hyoo<EMAIL_ADDRESS>wrote:

@mshukla1 https://github.com/mshukla1 OR @ARWattam
https://github.com/ARWattam should we close this ticket?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PATRIC3/patric3_website/issues/1456#issuecomment-297536501,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK8ZdOGoQs76Jy71oHcdEx_8d9vx11Xgks5rz61-gaJpZM4Mu06l
.[image: Web Bug from
https://github.com/notifications/beacon/AK8ZdMHh7dynql94k6i4462BMHOQFfTzks5rz61-gaJpZM4Mu06l.gif]


Bug fix 3.6/cleanup 20201117

Scope & Purpose
This is a multi-purpose PR:
It makes the number of network I/O threads properly configurable via the startup option --network.io-threads. This option existed before, but its configured value was effectively clamped to a value of 1.
This change requires forward ports to 3.7 and devel.
It also disables cluster maintenance background threads on coordinators.
The maintenance threads don't have any purpose on coordinators, so there is no need to start them there. This saves 2 or more background threads on coordinators. These threads should have mostly been idle before, so saving them will not have a huge impact except saving a few MB of thread stack memory.
The maintenance threads are already turned off on coordinators in 3.7 and devel for a while, so this does not need to be ported.
In addition this PR removes the _allowDirectExecution instance variable from RestHandlers, which in 3.6 was only set but never read back. This variable lost its meaning at point in the 3.5 cycle, so it is now useless and can be removed.
The instance variable has already been removed in 3.7 and devel a while ago, so this does not need to be ported.

[x] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification
[x] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[x] This change is a trivial rework / code cleanup without any test coverage.
[x] The behavior in this PR was manually tested

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12786/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12788/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12803/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/12806/


Python Iterators

Description
To describe iterators and related concepts in python.
Domain
Python_Domain
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

@adityabisoi  plz assign me for documentation

Successfully merged.


u-boot fails to build for raspberrypi3-64 and raspberrypi4-64

I am attempting to build an image for raspberrypi4-64 that uses u-boot. It consistently fails to build, apparently because it is unable to find libgcc:
|   aarch64-bantha-linux-ld.bfd    -Ttext 0xc100000 -g -o examples/standalone/hello_world -e hello_world examples/standalone/hello_world.o examples/standalone/libstubs.o -L . -lgcc
| aarch64-bantha-linux-ld.bfd: cannot find -lgcc

If I try switching MACHINE to raspberrypi4 or raspberrypi3 or qemux86-64 it builds fine. raspberrypi3-64 fails for me in the same way that raspberrypi4-64 does.
From what I can see, it seems like this is a fairly common problem when building u-boot in general, but I did not see a clear solution. It sounds like other people are able to build u-boot for this platform successfully, so it is possible (likely?) that there is something in my layer configuration that is messing things up.

Steps to reproduce the issue:

Assemble a project using the dunfell branches of poky, meta-raspberrypi, meta-updater, and meta-updater-raspberrypi
Set MACHINE to raspberrypi4-64
bitbake -v u-boot

Describe the results you received:
u-boot fails to compile, because it can't find libgcc
Describe the results you expected:
u-boot compiles successfully
Additional information you deem important (e.g. issue happens only occasionally):
This seems to happen consistently
Additional details (revisions used, host distro, etc.):
meta
meta-poky
meta-yocto-bsp       = "dunfell:235dff82276a8a2ff4d0ee1cf93243925537551c"
meta-oe
meta-python
meta-networking
meta-filesystems     = "dunfell:f2d02cb71eaff8eb285a1997b30be52486c160ae"
meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
meta-updater         = "dunfell:cc1b38310f4ebd0558438057a1edfeb4a3555b16"
meta-updater-qemux86-64 = "dunfell:71e2e2426b09e5aed6eabed72c8d289c0343c2de"
meta-updater-raspberrypi = "dunfell:3e4795b85861e63c54f6f7c573f8bd13b3024072"
meta-virtualization  = "dunfell:ff997b6b3ba800978546098ab3cdaa113b6695e1"
meta-bantha          = "meta-updater:9a01bec6f8e3483ad645bda05b56ac7f0f4490c4"

Host distro: I'm using the crops/poky:debian-10 container

Can you add DEPENDS_append_raspberrypi-64 = " libgcc" in u-boot_%.bbappend in your layer

@kraj I did try adding a libgcc dependency but it didn't fix it - it seems to already have the dependency, at least transitively.
I went searching through my layers to find things that were fiddling with u-boot and masking them out; I think the culprit was this bbappend from meta-updater-qemux86-64 - after adding that to BBMASK I was able to build u-boot successfully.
I'll leave this open for a bit in case there are some suggestions on how to fix that but I'll close it after I get started with work tomorrow, it looks like this is a meta-updater-qemux86-64 problem and not a meta-raspberrypi problem.

Change
SRC_URI +=" \
            file://0001-Set-up-environment-for-OSTree-integration.patch \
            file://0001-Revert-ide-remove-duplicate-defines-form-include-ata.patch \
          "

# fix after default security flags in poky
TOOLCHAIN_OPTIONS_append = "${SECURITY_NOPIE_CFLAGS}"

to
SRC_URI_append_qemux86-64 =" \
            file://0001-Set-up-environment-for-OSTree-integration.patch \
            file://0001-Revert-ide-remove-duplicate-defines-form-include-ata.patch \
          "

# fix after default security flags in poky
TOOLCHAIN_OPTIONS_append_qemux86-64 = " ${SECURITY_NOPIE_CFLAGS}"

that should help

@kraj Thanks! I've opened an issue over at the other layer's repo, I think I can go ahead and close this now.


Add auth0 auth

All though closed source, auth0 is a really easy and clean oauth provider, consolidating all other providers.

To be able to access restricted ressources It would be nice to have OAUTH2 client credentials flow together with OpenID connect enabled within the UI in a general way. That would also include the request within this ticket for the AUTH0 provider.

Discussing the backend capabilities part of this in #366

Thinking this one can be closed?  🧹
https://github.com/backstage/backstage/pull/1611

🧹


Support drivers license

Someone has used codes to revoke drivers license for me. How can I fix the issue


question about "duration of your current contract" question

Is the question:
What is the duration of your current contract?
asked of everyone, or is this just asked based on some previous answer?
I ask because the system of contracts is not how most US employers/employees function, and I'm wondering how to change this.

This question should only appears if people did not choose any permanent option on the type of contract. Is it only this question or the contract question (which type of contract) itself that is problematic for US?

It's mostly the phrasing, which I have changed now.
I just wanted to be sure I understood the context before changing the phrasing.


[DevCenter] small fix for 1.0.0-beta.2 changelog

Description
Fixing CHANGELOG.md header structure per comments from Java SDK reviewers.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


[DuckDB] Aliases are not completed in SQL statements

Description
'Insert table aliases (in FROM clause)' is set to my_table mt

Connect to DuckDB
Open SQL editor
Type statement and select table name from autocomplete list

Actual: SELECT * FROM main.TableName
Expected: SELECT * FROM main.TableName tn. It works as expected for other drivers

Client version: DuckDBJ 1.0
Server version: DuckDB v0.10.2
DBeaver Version
24.0.4

Thank you very much for the new feature, works like a charm !


Matching code was not found or was already used

Hi. It works for some month and now it get me:
{"error_message": "Matching code was not found or was already used.", "code": 400, "error_type": "OAuthException"}
I see this issue on SO, but cannot fix it(
Any ideas?

I have the same problem with some users for a couple of days. I don't know how to fix or workarround yet.

This is not a problem with the library.  It has to do with the one of the codes instagram gives you as part of getting an access code for api calls.  That other code (don't remember it's name) is single use, you need to re-authenticate from the beginning.
Yes, it's very annoying.

Hi. How do you mean about re-authenticate from the beginning ?

Please check this simple answer if you are following the same.


Bicep - DSC script - Joining Storage account to AD domain - running bicep code for second time, overwrites the settings

What happened? Provide a clear and concise description of the bug, including deployment details.
It looks like if we run the bicep code twice, in the second round if storage accounts (fslogix or msix) computer objects exist in the AD, it overwrite the directory service setup and makes it to unconfigured! Attached is the log for DSC script. August 22th, 2024 is when the script ran again while the storage accounts were domain joined already.
ManualDscStorageScriptsLog.log
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
What was the expected outcome?
No response
Relevant log output
No response

thanks for your feedback, we are investigating.

We are also experiencing issues with this when using AD DS set up. If we have a working set-up with storage accounts that are domain joined, if we redeploy the bicep deployment later, the DSC script triggers and attempts to domain join the storage account(the log file says it succeeds). But after the deployment completes without errors, and I check the storage account in the portal, it says "not configured" on fileshare 'Identity-based access'. If I delete the storage accounts computer object from AD DS, and redeploy again, the deployment succeeds, and the fileshare gets domain joined(the portal states "configured" on identity-based access).
Worth mentioning also that to be able to redeploy the AVD accellerator without it generating duplicate storage accounts and key vaults, we modify the uniquestring variable(remove time variable).

@bfond82 thanks for your feedback.
The logic of the baseline is meant to be greenfield only, if you want to use it for continuous deployment/updates, we recommend forking/cloning the repo and update the code to avoid running the deployments that are not capable of running incremental updates (VM extensions, AD objects, etc.)
@swathibhat1 let's add this item as feature request to modify the logic and enable for continuous incremental deployments.


tribute-api

generateTribute(amount);
disableTribute();
sendTribute();
endTribute();
claimTribute();

moving tabs on the dashboard currently loses the tribute object. you have to re-connect to the wallet before you can use the claim button.


TextButton - highlightColor

In FlatButton is possibility to change highlight color on has chosen by developer. I've tried find answer in documentation how can I change this attribute in TextButton, but unfortunately, I didn't find a way that I could change the highlight color. This feature is available under another name or will be accessible in the future?

@PawelZaw
I suggest you to ask this question on support channels like StackOverflow to get help, as this repo is to track bugs and feature request. If you don't get any solution on it from there, write in comments and I'll reopen to address it.
Thanks.


Rename CreateGroup to CreateGroupTypeSelect

In PR #3508, CreateGroupTypeAll is added, and to differentiate from it, CreateGroup
is renamed to CreateGroupTypeSelect.
Signed-off-by: Hongliang Liu<EMAIL_ADDRESS>

Codecov Report

Merging #3622 (321dcde) into main (7fea8d3) will decrease coverage by 22.05%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main    #3622       +/-   ##
===========================================
- Coverage   64.24%   42.18%   -22.06%
===========================================
  Files         278      324       +46
  Lines       27929    51006    +23077
===========================================
+ Hits        17942    21517     +3575
- Misses       8067    27877    +19810
+ Partials     1920     1612      -308

Flag
Coverage Δ

integration-tests
38.41% <ø> (?)

kind-e2e-tests
?

unit-tests
43.81% <0.00%> (+0.38%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/openflow/pipeline.go
23.88% <0.00%> (-49.87%)
:arrow_down:

pkg/ovs/openflow/ofctrl_bridge.go
1.18% <0.00%> (-54.11%)
:arrow_down:

pkg/ovs/openflow/default.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/util/runtime/runtime.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/openflow/groups.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/nodeportlocal/k8s/annotations.go
0.00% <0.00%> (-93.55%)
:arrow_down:

pkg/ovs/openflow/ofctrl_pipeline.go
0.00% <0.00%> (-93.34%)
:arrow_down:

pkg/apis/controlplane/register.go
0.00% <0.00%> (-90.48%)
:arrow_down:

pkg/ovs/openflow/logs.go
10.34% <0.00%> (-89.66%)
:arrow_down:

pkg/agent/controller/networkpolicy/reject.go
0.00% <0.00%> (-85.83%)
:arrow_down:

... and 384 more

I feel the renaming is not necessary. It is easy to understand from the groupID argument the func create a group for the specified group ID. And CreateGroupTypeSelect() sounds strange to me.

However, in this PR, a new method is added, maybe we should rename the original CreateGroup.
https://github.com/antrea-io/antrea/pull/3508/files#diff-5835a1d9c7aa317f3f9cde710002d428f3f7afc170b825e87f3cdbd0b08b4fa4


mirv_streams record start won't create files in the directory

Starting recording ... done.
Recording to "G:\csgo\raw\take0001".
The audio might be empty, because Valve removed code from startmovie for appending data to the WAV file!
Started recording movie, frames will record after console is cleared...

] mirv_streams record end
Finishing recording ... done.
Stopped recording movie...

The only thing that sits in the folder is a bugged audio.wav file,
don't care about it tho. I want frames the most but they do not create.
Tried it on a custom folder (g:\csgo\raw) but also tried it without custom folder (so in game's folder)
both failed
Any thoughs?
eddit: startmovie works normally

Sounds like you either didn't add any streams to be recorded or set their record property to 0 (so they won't be recorded).
If you are new to mirv_streams, please read this manual entry: https://github.com/ripieces/advancedfx/wiki/Source%3Amirv_streams Or search for some tutorial on YouTube please.

@kubak01 hey I had the same question and have been looking forever for an answer. @ripieces is correct - you need to add a normal stream: "mirv_streams add normal myName" then you should be good to go.
I never saw this mentioned on the youtube tutorials that I watched unfortunately :/

Yeah,
reoslved. Thanks @ripieces


UiConfig page settings are sticky

Description of the bug
There are currently two places that page settings can be set, layout-sets and settings.json and these both set page settings using the updateCommonPageSettings function. It is not actually defined in the layout-sets schema.
The problem is that if you set a setting like showLanguageSelector to true in one layout-set, and leave it undefined in the next layout set, the setting will not be reset when navigating to the next process step even though it is implicitly false when undefined. A refresh will reset the setting. This happens because updateCommonPageSettings uses the existing value if the new value is undefined.
I suppose the settings in the layout-sets file are "global" for all process steps, and the expected behaviour is that settings.json should override layout-sets settings if defined, and be set to false if undefined in both places.
Steps To Reproduce
.
Additional Information
No response

Reported march 2023 - I assume this was a byproduct of not resetting the state in redux? 🤔


Unhnandled Promise Rejection

When using the package I uncovered this error
 ~/dev/work/ghe/oswg/github_membership   master ±  npx orglinter godaddy.toml
npx: installed 16 in 4.035s
Loaded config for godaddy. 141 memberships expected.
Retrieving 100 GitHub members...
Retrieving 100 GitHub members...
140 total members retrieved.
0 two factor auth violators found:  []
0 undocumented memberships found:  []
1 new memberships requested:  [ 'rmarkins-godaddy' ]
Setting rmarkins-godaddy up as a(n) admin for godaddy.
0 demotions found:  []
(node:46771) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'role' of undefined
    at /Users/rmarkins/.npm/_npx/46771/lib/node_modules/orglinter/src/lib/checkers.js:25:69
    at Array.filter (<anonymous>)
    at Object.findPromotions (/Users/rmarkins/.npm/_npx/46771/lib/node_modules/orglinter/src/lib/checkers.js:24:46)
    at /Users/rmarkins/.npm/_npx/46771/lib/node_modules/orglinter/bin/cli.js:61:17
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:46771) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:46771) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
rmarkins-godaddy successfully invited to godaddy!

It appears that when sending a new request it has an issue w/ role

Hmmmm, it looks like a problem with this filter: https://github.com/godaddy/orglinter/blob/1b75cd7071eaf0efaf459992fb40f29d3d264424/src/lib/checkers.js#L24-L26
I think this may need to be changed to something more like
  (member) => configured[members] === 'ADMIN' && retrieved[member] && retrieved[member].role === 'MEMBER'

Adding that additional existence check there in the middle. I swear it did this in the past, but it must have gotten removed at some point. Or would that be better done with .hasOwnProperty(member)?
It looks like it's erroring out on the fact that your rmarkins-godaddy doesn't yet exist in the org, so it doesn't exist in the retrieved object.

Hmmmm, it looks like a problem with this filter: https://github.com/godaddy/orglinter/blob/1b75cd7071eaf0efaf459992fb40f29d3d264424/src/lib/checkers.js#L24-L26
I think this may need to be changed to something more like
  (member) => configured[members] === 'ADMIN' && retrieved[member] && retrieved[member].role === 'MEMBER'

Adding that additional existence check there in the middle. I swear it did this in the past, but it must have gotten removed at some point. Or would that be better done with .hasOwnProperty(member)?
It looks like it's erroring out on the fact that your rmarkins-godaddy doesn't yet exist in the org, so it doesn't exist in the retrieved object.


Correction training script filename

change train.py -> e2e_rlhf.py in README.md to avoid reader's confusion

@microsoft-github-policy-service agree


Unconditional break in clone.go:85

While reviewing the codebase a bit I discovered an unconditional break in commands/clone.go at line 85.
Should this be moved up into the if-condition above or is the entire loop redundant?

Good find, but the code is correct! We only want to process the first positional argument and ignore the rest.
The block could alternatively be converted into an if instead of a for..break, but not much would be gained in terms of readability.


Album Upload duplicated IDs

Something really weird happens with Album Upload. I tried to do an Album Upload using 6 completely different images, and when the Album Upload was called I noticed that not all images were being added to the album, I did an console.log(payload); after the Upload and noticed that an UploadID was present on multiple keys of the array, like this:
[ { uploadId: '1522042011914', 		type: 'photo', 		size: [ 1024, 1024 ], 		data: 'posts/1421367591430519_2118541548379783/main.jpg' }, 	{ uploadId: '1522042011925', 		type: 'photo', 		size: [ 1024, 1024 ], 		data: 'posts/1421367591430519_2118541548379783/mentada.jpg' }, 	{ uploadId: '1522042011926', 		type: 'photo', 		size: [ 1024, 1024 ], 		data: 'posts/1421367591430519_2118541548379783/felicidad.jpg' }, 	{ uploadId: '1522042011927', 		type: 'photo', 		size: [ 1024, 1024 ], 		data: 'posts/1421367591430519_2118541548379783/grafica.jpg' }, 	{ uploadId: '1522042011927', 		type: 'photo', 		size: [ 1024, 1024 ], 		data: 'posts/1421367591430519_2118541548379783/negas.jpg' }, 	{ uploadId: '1522042011927', 		type: 'photo', 		size: [ 1024, 1024 ], 		data: 'posts/1421367591430519_2118541548379783/quien.jpg' } ]
As you can see the data/path of every image is different, but the last 3 keys share the same uploadId.
What could be happening here? What would be a fix?

any solution ?


No intellisense for variables in Razor pages when adding conditions on breakpoint

This issue has been moved from a ticket on Developer Community.

There is no intellisene when you set a breakpoint and you try to add conditional statement on the breakpoint.
To reproduce this:

File new Blazor project (server side)
On FetchData page, set a breakpoint OnInitiliazedAysn()
Start the App
when it hits the breakpoint, try to add a condition by typing the forecasts variable name and nothing comes up.

Original Comments
Feedback Bot on 11/2/2020, 00:09 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions
(no solutions)

This is a super interesting point. @tmat what does it take to enable the C# completion list for breakpoints in embedded scenarios?

IIRC debugger completion (in immediate window, watch window, conditional bps) is using some legacy interfaces and complex projection buffer logic. So we'll probably want to delete it and start from scratch with LSP.

This will be a lot of work - I believe we need to 1) use C# scripting language parsing in all these scenarios (unify with interactive window), 2) switch interactive window to LSP, 3) replace immediate window UI with interactive window UI


Last action date is not displaying as expected in feeds on the person detail page

This was resolved via https://github.com/opencivicdata/pupa/pull/329 and https://github.com/datamade/django-councilmatic/pull/265.

@hancush yes, looks good!


Can kubernetes 1.12.4 install istio 1.5.4

my kubernets version is 1.12.4 .   So Can kubernetes 1.12.4 install istio 1.5.4?

No, see https://istio.io/v1.5/docs/setup/platform-setup/

You can also run precheck to see if your cluster is compatible with specific Istio version.
$ istioctl experimental precheck

您还可以运行precheck以查看您的群集是否与特定的Istio版本兼容。
$ istioctl experimental precheck

thank you @shamsher31 .  "istioctl experimental precheck" command just chek yaml file,It's not an check kubernetes cluster

不，请参阅https://istio.io/v1.5/docs/setup/platform-setup/

thank you @howardjohn 。I read the manual, but I don't want to upgrade kubernets cluster.  I'am install istio1.5.4 at kubernetes 1.12.4.  I will continue to test

Hi there,
I've more or less the same problem, I'm on K8 1.12.6 and istio 1.0.5 but i'm unable to figure out most recent working version.
I've tried 1.6 but istiod told me minimum version is 1.13
It would be really useful a compatibility matrix k8-istio versions in docs without having to download and try every version setup (supposing older version would run such check)

See https://istio.io/v1.5/docs/setup/platform-setup/ and you can replace the version with older versions as well. We are considering adding a table you suggested but the pr isn't approved

by the way, I ended up using prechek against all versions: the oldest one supporting kubernetes 1.12.x is Istio 1.2.x
All versions 1.3+ state they need at least kubernetes 1.13 to work properly (I suppose it's related to CRD management).
Hope this may come in handy waiting for a real compatibility matrix (by the way the statement "tested with" and "working with" are not the same :) )


Update Golang & Nodejs Version

Update nodejs to v12.13.1 lts
Update golang version to 1.13.5
Install nodejs/golang during pre_packaging also if used

@subhankarc Dev pipeline passed all tests on Azure. Aws had couple failures.

Yes, they look like unrelated. I'll check once and merge if looks good.


RustyCode tasks should register keybindings

RustyCode should register some common commands as key bindings like for example:
    "keybindings": [
    {
        "command": "rust.cargo.run.debug",
        "key": "Ctrl+Shift+B"
    },
   {
        "command": "rust.cargo.test",
        "key": "Ctrl+Shift+T"
   }]

in the contributes section of package.json

To whoever implements this, remember to add "when": "editorLangId == 'rust'" to the shortcuts.


Don't put error in Alert; globalize error message

Addresses crash reported when trying to follow a user that you already have a Friendship record for (Friendships can exist without a following attribute). Actually that problem was addressed by adding upsert functionality to POST /relationships, but this addresses a related problem in which adding an Error object as the body of an Alert resulted in a native crash. This also globalizes the error message when this happens and logs the error to logstash.

@angielt, you might want to take a look at this b/c I think you wrote some of this stuff. Some main takeaways are

We should not put Errors directly into Alerts
All user-facing text should be globalized
Try to make sure variable names describe what they are; id did not actually contain an ID but a params object


Custom Functions Information needs to be more clear about the versions of Office Custom Functions can run in

Article URL
https://aka.ms/customfunctions
Issue

We have many reports from customers who cannot find the correct information to build custom functions.

Often they will try on 2019 and hit issues.  We should be clear this does not work on 2019.
Our documentation still states 1810 or earlier. For production, we should stay 1904 as specified in the custom functions requirements article here

The information is here:

https://docs.microsoft.com/en-us/office/dev/add-ins/excel/custom-functions-requirements
https://docs.microsoft.com/en-us/office/dev/add-ins/reference/requirement-sets/excel-api-requirement-sets#custom-functions

But customers are not discovering it, because it is not linked via the quickstart
https://docs.microsoft.com/en-us/office/dev/add-ins/quickstarts/excel-custom-functions-quickstart?tabs=excel-windows

In a PR, thanks for the flag!

Should go up in documentation tomorrow, when the latest changes are pulled in. Going to close this issue for now, but notify me on this thread if you want me to reopen and change things. Happy to help!


[REQUEST] Creating a list of sequential numbers 1 to N (Ex: [1, 2, 3, …, 98, 99, 100])

Hello sir, I want to create a list in which there is an array of sequential numbers.
Example:-
n = 9
Then
list = [1,2,3,4,5,6,7,8,9]
As you @Ruri have suggested in the official forum that the solution to be
List<string> theNumbersMason = Enumerable.Range(1, 9).Select(i => i.ToString()).ToList();
I want you to create a separate Block for all of those who need it, this will be useful in searching some text in search engines, and we get a lot of pages like gives below.

We can parse the maximum number of pages, generate a sequel number of lists, and Then create a loop of Requests to parse all of the requests. 🙂
And I think we can use it in many other ways too, so kindly, sir consider sparing some time for this block.

Instead of having a set amount of numbers why not just take advantage of the pagination and just click "Next" until it is no visible or until the html/numbers do not change anymore.
That way no matter how many pages it will also hit them all?

Or, since you know the amount of total pages, you can do a for loop in C#
But I told him I would add this as a block since it might be useful for other purposes, so I will add it

Instead of having a set amount of numbers why not just take advantage of the pagination and just click "Next" until it is no visible or until the html/numbers do not change anymore.
That way no matter how many pages it will also hit them all and it could all be done via a while loop.

Yes sir I have thought of that way before and also tried to implement it, but haven't found an exact way to do so. Anyways This Block can also be useful for various purposes for many people so I have posted the suggestion.

It would be different depending on if you were using puppeteer or rurilib but its essentially the same
Start a loop
check if element exists (next button) either using the puppeteer block or a parse block
if visible then scrape and click next
if not end/break loop


upgrade: elevator to v2.2.2

This version prints debug messages to stdout.
See: https://github.com/resin-io-modules/elevator/pull/11
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

Shouldn't this have bumped the shrinkwrap too?

This is an optional dependency, which is not tracked by shrinkwrap.

Ahhh. Does that mean we'll always get the latest version installed anyway?

Yeah, that's right, but there is not much we can do about that, given that NPM shrinkwrap has some known limitations with regarding to optional dependencies. Maybe we should at least lock the version in package.json?

@lurch Maybe this is something to add to the integrity checks (e.g: optional dependencies can't have ranges)?


servicelb: fix ineffective toleration

noderole.kubernetes.io/master -> node-role.kubernetes.io/master

Do we need a separate PR to target each release branch or can we cherry-pick and push (after this is merged)?

Possible to get this cherry-picked to a release so we can get this fixed sooner?


Add pronto-goodcheck

Add link to pronto-goodcheck.
Note: This depends on the unreleased change to allow rainbow 3.0, so this shouldn't be merged until that change is released to avoid confusing people. I think the version conflict can be ignored if using Bundler and pronto is specified as a Git dependency instead of from RubyGems. But I think we would rather have people using RubyGems, and this also doesn't work for someone who isn't using Bundler.
cc @prontolabs/core

Thank you @aergonaut!

Thanks @doomspork. Yup, I hope we can get a new version cut soon!


More clear info that SN and not ID is needed

Also in example config inverterId is a string not number (especially important if someone do not know json very well).
I was having trouble to make it working because errors reported was not really helpful for me :(

Thanks for the PR, @sebeksd!


add: Getting Started with gRPC-Go Unary

The very first codelab example on this repo 🥳
This contains the example code required for Getting Started with gRPC-Go (unary). There are two directories, start_here/ directory serves as a starting point for the codelab, and ta_da/ directory showcases the finished code, giving you a peak
of how the final implementation should look like.
I ran through the whole codelab and was able to setup the example.
~/codelabs/codelabs/Getting Started with gRPC-Go/ta_da/client getting-started-with-grpc-go
❯ go run .
2024/08/19 15:40:54 Getting feature for point (409146138, -746188906)
2024/08/19 15:40:54 name:"Berkshire Valley Management Area Trail, Jefferson, NJ, USA"  location:{latitude:409146138  longitude:-746188906}

Getting Started with gRPC-Go (Streaming) example is in progress and would be merged in a separate PR.

Change ta_da to completed Change codelab name to start with Go

1/ Done
2/ I would prefer the codelab and the directory to be named a similar as possible.  Seems easier to organize.  I've snakecased the codelab name as dir name