ERROR Error: Uncaught (in promise): TypeError: Object doesn't support property or method 'setPrototypeOf'

Bug Report or Feature Request (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [x ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [x ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Repro steps

The log given by the failure

Desired functionality

Mention any other details that might be useful
When i clicked on the menus it show me this in IE console
https://www.screencast.com/t/kxgnKCAV
My polyfils.ts file is
/**

This file includes polyfills needed by Angular and is loaded before the app.
You can add your own extra polyfills to this file.

This file is divided into 2 sections:

Browser polyfills. These are applied before loading ZoneJS and are sorted by browsers.

Application imports. Files imported after ZoneJS that should be loaded before your main

 file.

The current setup is for so-called "evergreen" browsers; the last versions of browsers that
automatically update themselves. This includes Safari >= 10, Chrome >= 55 (including Opera),
Edge >= 13 on the desktop, and iOS 10 and Chrome on mobile.

Learn more in https://angular.io/docs/ts/latest/guide/browser-support.html
*/

/***************************************************************************************************

BROWSER POLYFILLS
*/

/** IE9, IE10 and IE11 requires all of the following polyfills. **/
import 'core-js/es6/symbol';
import 'core-js/es6/object';
import 'core-js/es6/function';
import 'core-js/es6/parse-int';
import 'core-js/es6/parse-float';
import 'core-js/es6/number';
import 'core-js/es6/math';
import 'core-js/es6/string';
import 'core-js/es6/date';
import 'core-js/es6/array';
import 'core-js/es6/regexp';
import 'core-js/es6/map';
import 'core-js/es6/weak-map';
import 'core-js/es6/set';
import 'core-js/es7/array';
/** IE10 and IE11 requires the following for NgClass support on SVG elements */
import 'classlist.js';  // Run npm install --save classlist.js.
/** IE10 and IE11 requires the following to support @angular/animation. */
import 'web-animations-js';  // Run npm install --save web-animations-js.
/** Evergreen browsers require these. **/
import 'core-js/es6/reflect';
import 'core-js/es7/reflect';
/** ALL Firefox browsers require the following to support @angular/animation. **/
import 'web-animations-js';  // Run npm install --save web-animations-js.
/***************************************************************************************************

Zone JS is required by Angular itself.
*/
import 'zone.js/dist/zone';  // Included with Angular CLI.

/***************************************************************************************************

APPLICATION IMPORTS
*/

/**

Date, currency, decimal and percent pipes.
Needed for: All but Chrome, Firefox, Edge, IE11 and Safari 10
*/
// import 'intl';  // Run npm install --save intl.
import 'intl';
import 'intl/locale-data/jsonp/en.js';

//My Package.json file is
{
"name": "angly",
"version": "1.0.0",
"license": "MIT",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
},
"private": true,
"dependencies": {
"@angular/animations": "6.0.7",
"@angular/common": "6.0.7",
"@angular/compiler": "6.0.7",
"@angular/core": "6.0.7",
"@angular/forms": "6.0.7",
"@angular/http": "6.0.7",
"@angular/platform-browser": "6.0.7",
"@angular/platform-browser-dynamic": "6.0.7",
"@angular/router": "6.0.7",
"@fancyapps/fancybox": "^3.3.5",
"classlist.js": "^1.1.20150312",
"core-js": "^2.5.7",
"font-awesome": "^4.7.0",
"hammerjs": "2.0.8",
"intl": "^1.2.5",
"ionicons": "^3.0.0",
"jquery": "^3.3.1",
"ngx-slick": "^0.1.3",
"popper.js": "^1.14.3",
"rxjs": "^6.2.1",
"rxjs-compat": "^6.2.1",
"web-animations-js": "^2.3.1",
"zone.js": "^0.8.26"
},
"devDependencies": {
"@angular-devkit/build-angular": "~0.6.8",
"@angular/cli": "6.0.8",
"@angular/compiler-cli": "6.0.7",
"@angular/language-service": "6.0.7",
"@types/jasmine": "2.8.8",
"@types/jasminewd2": "2.0.3",
"@types/node": "10.5.2",
"codelyzer": "4.4.2",
"exports-loader": "^0.7.0",
"jasmine-core": "3.1.0",
"jasmine-spec-reporter": "4.2.1",
"karma": "2.0.4",
"karma-chrome-launcher": "2.2.0",
"karma-cli": "1.0.1",
"karma-coverage-istanbul-reporter": "2.0.1",
"karma-jasmine": "1.1.2",
"karma-jasmine-html-reporter": "1.2.0",
"protractor": "^5.3.2",
"ts-node": "7.0.0",
"tslint": "5.10.0",
"typescript": "^2.7.2"
}
}

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

This issue can be related to the issue of rxjs library.
https://github.com/ReactiveX/rxjs/issues/3966


consider using two-step completion resolving

with our toplevel completion and whatnot it may be quite expensive to return the full info with documentation at once, so we gotta investigate if we should instead do two-step completion instead (1 - simple list, 2 - full info about a single item with doc and additional details)

This obviously requires compiler support and I'm not sure it's really worth it.

current stuff works fairly well, so let's can it


Vagrant: Add ldiskfs-lvm-fs provisioners

Add provisioners to create MDT and MGT on LVMs
To create an ES-like system provision with the following steps:
create-ldiskfs-lvm-fs
ha-ldiskfs-lvm-fs-step1
ha-ldiskfs-lvm-fs-step2
Set lustre version to 2.12.4
Add documentation to README.md
Fixes #1746
Signed-off-by: Nathaniel Clark<EMAIL_ADDRESS>

This change is

Trying this locally, The OST resources seem to have trouble starting:
Failed Resource Actions:
* ost0_start_0 on oss2.local 'unknown error' (1): call=47, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:54:03 2020', queued=0ms, exec=62312ms
* ost1_start_0 on oss2.local 'unknown error' (1): call=57, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:59:10 2020', queued=0ms, exec=312735ms
* ost2_start_0 on oss2.local 'unknown error' (1): call=46, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:54:03 2020', queued=0ms, exec=184205ms
* ost3_start_0 on oss2.local 'unknown error' (1): call=58, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:59:10 2020', queued=0ms, exec=416533ms
* ost4_start_0 on oss2.local 'unknown error' (1): call=48, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:54:03 2020', queued=0ms, exec=306547ms
* ost5_start_0 on oss2.local 'unknown error' (1): call=56, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:59:10 2020', queued=0ms, exec=208863ms
* ost6_start_0 on oss2.local 'unknown error' (1): call=49, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:54:03 2020', queued=0ms, exec=123539ms
* ost7_start_0 on oss2.local 'unknown error' (1): call=60, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:59:10 2020', queued=0ms, exec=520210ms
* ost8_start_0 on oss2.local 'unknown error' (1): call=50, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:54:03 2020', queued=0ms, exec=245373ms
* ost9_start_0 on oss2.local 'unknown error' (1): call=59, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:59:10 2020', queued=0ms, exec=104535ms
* ost0_start_0 on oss1.local 'unknown error' (1): call=58, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:59:10 2020', queued=0ms, exec=208412ms
* ost1_start_0 on oss1.local 'unknown error' (1): call=35, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:54:04 2020', queued=0ms, exec=122974ms
* ost2_start_0 on oss1.local 'unknown error' (1): call=60, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:59:10 2020', queued=0ms, exec=104966ms
* ost3_start_0 on oss1.local 'unknown error' (1): call=45, status=complete, exitreason='',
    last-rc-change='Tue Mar 31 20:54:04 2020', queued=0ms, exec=62714ms
* ost4_start_0 on oss1.local 'unknown error' (1): call=59, status=complete, exitreason='',

Seen during mount:
Apr 01 01:05:03 oss2.local kernel: LustreError: 2070:0:(mgc_request.c:249:do_config_log_add()) MGC<IP_ADDRESS>@tcp: failed processing log, type 1: rc = -5
Apr 01 01:05:03 oss2.local kernel: LustreError: 2070:0:(mgc_request.c:249:do_config_log_add()) Skipped 1 previous similar message
Apr 01 01:05:34 oss2.local kernel: LustreError: 2070:0:(mgc_request.c:249:do_config_log_add()) MGC<IP_ADDRESS>@tcp: failed processing log, type 4: rc = -110
Apr 01 01:05:40 oss2.local kernel: LustreError: 13a-8: Failed to get MGS log fs-OST0000 and no local copy.
Apr 01 01:05:40 oss2.local kernel: LustreError: 15c-8: MGC<IP_ADDRESS>@tcp: The configuration from log 'fs-OST0000' failed (-2). This may be the result of communication errors between this node and the MGS, a bad configuration, or other errors. See the syslog for more information.
Apr 01 01:05:40 oss2.local kernel: LustreError: 2070:0:(obd_mount_server.c:1395:server_start_targets()) failed to start server fs-OST0000: -2
Apr 01 01:05:40 oss2.local kernel: LustreError: 2070:0:(obd_mount_server.c:1990:server_fill_super()) Unable to start targets: -2
Apr 01 01:05:40 oss2.local kernel: LustreError: 2070:0:(obd_mount_server.c:1990:server_fill_super()) Skipped 1 previous similar message
Apr 01 01:05:40 oss2.local kernel: LustreError: 2070:0:(obd_mount_server.c:1598:server_put_super()) no obd fs-OST0000
Apr 01 01:05:40 oss2.local kernel: LustreError: 2070:0:(obd_mount_server.c:1598:server_put_super()) Skipped 1 previous similar message
Apr 01 01:05:40 oss2.local kernel: Lustre: server umount fs-OST0000 complete

Confirmed as working (IML sees LVs on both hosts as well) after updating the mgsnode location on osts so it can see the MGT:


Unable to use instanceof TRPCClientError

I'm having trouble getting errors to show up correctly as instances of the TRPCClientError class.
If you console.log(err.constructor.name) it's always _y
It seems it's being minified by Vite somewhere but I've played with the configuration a lot and can't seem to figure out anything different.
I realize this may be a Vite issue more so than an electron-trpc issue but I imagine everyone here is likely facing this so curious of a fix.
This issue happens in my own repo and this repos example basic-react project
import { TRPCClientError } from '@trpc/react-query'; // same issue even if you import from '@trpc/client'

 try {
          await mutateAsync();
        } catch (err) {
          if (err instanceof TRPCClientError) {
            // never happens :(
          }
        }

This is my way of hacking it for now, but obviously less than ideal
export const isTRPCClientError = (error: unknown): error is TRPCClientError<AppRouter> => {
  return typeof error === 'object' && error !== null && error['name'] === 'TRPCClientError'
}

// inside catch block
if (isTRPCClientError(error)) {
        // error is now a TRPCClientError
}


Release notes for beta-20160505

This change is

LGTM

LGTM, too. I'll add links and some Docs Updates before publishing these.


fix: remove import plugin

Artifact can be viewed here: :
https://5200-62313804-gh.circle-artifacts.com/0/sandbox/mdbook/book/index.html

Artifact can be viewed here: :
https://5201-62313804-gh.circle-artifacts.com/0/packages/style/storybook-static/index.html

Artifact can be viewed here: :
https://5201-62313804-gh.circle-artifacts.com/0/sandbox/sapper/__sapper__/export/index.html

Artifact can be viewed here: :
https://5201-62313804-gh.circle-artifacts.com/0/sandbox/vuepress/docs/.vuepress/dist/index.html

Artifact can be viewed here: :
https://5202-62313804-gh.circle-artifacts.com/0/sandbox/mdbook/book/index.html

Artifact can be viewed here: :
https://5203-62313804-gh.circle-artifacts.com/0/packages/style/storybook-static/index.html

Artifact can be viewed here: :
https://5203-62313804-gh.circle-artifacts.com/0/sandbox/sapper/__sapper__/export/index.html

Artifact can be viewed here: :
https://5203-62313804-gh.circle-artifacts.com/0/sandbox/vuepress/docs/.vuepress/dist/index.html

Artifact can be viewed here: :
https://5206-62313804-gh.circle-artifacts.com/0/sandbox/mdbook/book/index.html

Artifact can be viewed here: :
https://5207-62313804-gh.circle-artifacts.com/0/packages/style/storybook-static/index.html

Artifact can be viewed here: :
https://5207-62313804-gh.circle-artifacts.com/0/sandbox/sapper/__sapper__/export/index.html

Artifact can be viewed here: :
https://5207-62313804-gh.circle-artifacts.com/0/sandbox/vuepress/docs/.vuepress/dist/index.html

Artifact can be viewed here: :
https://5208-62313804-gh.circle-artifacts.com/0/packages/style/storybook-static/index.html

Artifact can be viewed here: :
https://5208-62313804-gh.circle-artifacts.com/0/sandbox/sapper/__sapper__/export/index.html

Artifact can be viewed here: :
https://5208-62313804-gh.circle-artifacts.com/0/sandbox/vuepress/docs/.vuepress/dist/index.html

Artifact can be viewed here: :
https://5209-62313804-gh.circle-artifacts.com/0/sandbox/mdbook/book/index.html


What is the CUDA version for this code?

What is the CUDA version for this code?

11.2 thank you!


Reorganize the folder structure and apply new CS standard

As per title, I've aligned both the CS standard and the folder structure with the one used in the main SDK. The only notable change is the introduction of declare(strict_types=1) in all files. I also deleted the whole examples folder as I judged it useless, unmaintained, and because I think it's better to improve the documentation rather than providing yet another copy of a basic Symfony app that I don't understand how it can help new users

I also deleted the whole examples folder as I judged it useless, unmaintained, and because I think it's better to improve the documentation rather than providing yet another copy of a basic Symfony app that I don't understand how it can help new users

I agree: the End2End tests serve the same purposes and are automatically aligned with the code.

I also deleted the whole examples folder as I judged it useless, unmaintained, and because I think it's better to improve the documentation rather than providing yet another copy of a basic Symfony app that I don't understand how it can help new users

I agree: the End2End tests serve the same purposes and are automatically aligned with the code.


ISPN-9643 Improve Jacoco support for Infinispan

https://issues.jboss.org/browse/ISPN-9643

@diegolovison Is this PR abandoned? If so we should close as the PR queue is pretty huge atm.

The remaining item on this PR is when using failsafe plugin.
Due that we have a new server in ISPN10, I would like to work on this later.

@diegolovison Ok, let's close the PR for now and re-open later.


Compute quickly the byte lengths without look-ups

Some look-ups could be efficiently replaced by fast instructions such as a pdep followed by a multiplication and a shift. It is unlikely to be generally faster than a look-up, but it might be worth exploring.

The length is 1 + the rightmost index in the decoding shuffle, which is within the last four entries.

As per this commit https://github.com/lemire/streamvbyte/commit/dac1b230f9a9efe9f289d5fb8c103341359b4e28 , @KWillets's approach can be enabled by defining a macro. I am concerned about making this a default without enough hard numbers.
Note that I have ported the approach to neon (note: it was trivial).

// is mod15 faster than pdep?
len = ((key * 0x0401 & 0x00033033) % 0x0F) + 4;

// simd
v = ((v >> 2) & 0x33333333) + (v & 0x33333333);
v = ((v >> 4) & 0x0F0F0F0F) + (v & 0x0F0F0F0F);
len4 = v + 0x04040404;
// todo: now extract each byte...

It is definitely susceptible to various bithacks.  I used the permutation table since it's available, but the 2-bit fields could also be summed in a few instructions.
mod15 compiles to a multiply and some shifts and subtracts, so it may be decomposable into fewer instructions in this context.
Generally I would spread the bitfields out and use a multiply to sum them into something like the most significant byte; that's what I do in the compressor when I have the 2-bit fields already spread out.  Your method of multiplying by 0x401 and masking looks promising -- they're far enough apart to sum into a nybble at that point.  Multiplying by (1<<28)|(1<<24)|(1<<16)|(1<<12) should drop them on top of each other in the high nybble, if I've got those shifts right.

@KWillets @aqrit
I ran some numbers on my blog: Bit hacking versus memoization: a Stream VByte example.

@lemire @aqrit I started a branch to see if precomputing byte lengths 8-at-a-time and prefix summing would speed up the decode loop.  The pointer arithmetic in  each decode_avx seemed like a barrier to ILP, and this modification makes it possible to dispatch the 8 decode_avx calls independently.
However it has proved slower for the two methods I've tried (scalar shift/mask/add and a pshufb LUT, both similar to the blog article).
I suspect the pshufb's are already single-threaded (there is only one port for them, I believe), and the length processing is not the critical path.

@KWillets suggestion:
len = pshuf[12 + (key >> 6)] + 1;
could eventually become:
len = 16 - pshuf[0];
If the literal data bytes get loaded at the high-end of the xmmword...
(rather than the low-end as is currently done)
then the lowest byte of the shuffle mask will also be the number of unused bytes in the data xmmword
(which can be converted to length at little to no additional cost)
gist here

The length value could broken into bits and deposited  into the sign bits of the byte shuffle table.
The length value would be retrieved using pmovmskb. The sign bits get fixed-up for pshufb by adding 0x40 to each byte.
I used this for "0124" decoding in svb0_dec.c over here.


Ensure the SDK doesn't emit unhandled rejections

Official Node 15 blog post
Snippet from blog post:

Throw on unhandled rejections
As of Node.js 15, the default mode for unhandledRejection is changed to throw (from warn). In throw mode, if an unhandledRejection hook is not set, the unhandledRejection is raised as an uncaught exception. Users that have an unhandledRejection hook should see no change in behavior, and it’s still possible to switch modes using the --unhandled-rejections=mode process flag.
Node.js has emitted an UnhandledPromiseRejectionWarning by default for many releases and the decision to switch the mode to throw was agreed to based on input from the results of the Node.js User Insights: Unhandled Promise Rejections survey, and finally a Node.js Technical Steering Committee vote. A special thank you to Mary Marchini for driving this decision forwards.

While the SDK doesn't officially support odd number versions of Node (aka non-LTS), addressing unhandled rejections will:

Improve code quality of the SDK
Prepare the SDK for Node.js 16

Things to consider: updating eslint rules, listening for process.on('unhandledRejection') in the tests, and failing if emitted.

I encountered unhandled rejections when the callbackUrl of a request to a bot included a URL that could not be resolved (that resulted in getaddrinfo ENOTFOUND). I tried to reproduce it so I could provide more details but no luck. I will update here if I manage to reproduce it.
The error was:
new RestError<EMAIL_ADDRESS>

We should rewrite the existing JS samples to have proper rejection handling. Perhaps follow the pattern set via https://github.com/microsoft/botbuilder-js/pull/3492


Parallelize pytest

Towards #223

This literally cuts the execution time of the tests in half.
Before:

After:

I dont see any downside here for now. @rabernat what do you think?

Waiting for @rabernat to merge. But to me this looks good now.


top-level await throws SyntaxError

basically the subject
// llrt-test.mjs
function foo() {
  return Promise.resolve(42)
}

console.log(await foo())

$ ./llrt llrt-test.mjs
SyntaxError: unexpected 'await' keyword
    at llrt-test.mjs:5:12

Thanks for reporting. Top-Level await is not yet supported. It's recently been added to QuickJS so will eventually be supported by LLRT.

Hi, @richarddavison ,
In rquickjs, which was released just last week, it appears that top-level await are linking quickjs with support.
For your information, the latest version is v0.6.1 at this time.

Hi @nabetti1720 . Thanks for the info, I’m aware and already been working on a PR. This will also introduce ES2023 language support. The blocker I have now is synonymously wait for imports without blocking the async runtime. I have created a PR in rquickjs.

Hi @richarddavison , This has already been resolved, correct?


Can someone help with deploy to aws ec2 instance?

I don't really know anything about docker-swarm.
So, I don't understand even the concept of deploying this template to a simple EC2 instance (or any cloud instance).
I'm running deploy commands from Readme.md but nothing really works.
So, right now I'm running with a simple docker-compose up. But I'm sure, it's not a production solution.
Could you provide me some simple instructions on how to run my project (even if it's just a fresh one from this template.) in some simple cloud instance like EC2?
Sorry, if this question was very silly, and thanks for your attention.

I saw this issue while struggling with the same problem.
Here is how I solved it.
https://towardsdatascience.com/deployment-could-be-easy-a-data-scientists-guide-to-deploy-an-image-detection-fastapi-api-using-329cdd80400

@MLWhiz Thanks for your answer.
But actually, I was more interested in managing it to work with docker-swarm.
I realize how to make it work with docker but docker-swarm approach is quite new for me so I don't really understand what is the best way to start digging into it within this project.
And, I suppose, it leads me to a misunderstanding of containers management in this cookiecutter template.

Same here. I was following dockerswarm.rocks and I got lost once I got into the "optional" steps since I don't what my workers/managers should be.

A, I missed the README.md generated. I was only looking at the README.md of this project generator.
@timofeyantonenko Maybe if you ask which part exactly in README.md you are getting stuck, then more people might be able to help.

@timofeyantonenko
When I was trying to deploy my images to docker in EC2 for a quasi production scenario I found this useful:
https://docs.docker.com/compose/production/
In regards to a "true" production mode, from my understanding that is not generally recommended at least right now in docker's current maturity(This is based on my own research, in no way am I trying to state this as fact). Unless running in some sort of cluster(ECS, docker swarm etc). IF you where to run the docker-compose in a production environment you'd for sure want to move the DB out of docker and maybe separate the front and backend containers among many other things.
If just getting the stack running in an EC2 instance via docker-compose is the problem, if you provide more details I am happy to try to help as I just setup a few instances for testing and quasi production.


Improve logging during interpreter discovery

❯ VIRTUAL_ENV=.venv cargo run -q -- pip install anyio -v
DEBUG Searching for interpreter that fulfills Python @ default in virtual environments
DEBUG Found Python interpreter cpython 3.12.3 at `.venv/bin/python` (active virtual environment)
DEBUG Using Python 3.12.3 environment at .venv/bin/python
DEBUG Trying to lock if free: .venv/.lock
DEBUG Requirement satisfied: anyio
DEBUG Requirement satisfied: idna>=2.8
DEBUG Requirement satisfied: sniffio>=1.1
DEBUG All editables satisfied:
Audited 1 package in 14ms

instead of
❯ VIRTUAL_ENV=.venv cargo run -q -- pip install anyio -v
DEBUG Searching for interpreter that fulfills Python @ default
DEBUG Searching for interpreter that fulfills Python @ default
INFO Found active virtual environment (via VIRTUAL_ENV) at: .venv
DEBUG Found a virtual environment at: /Users/zb/workspace/uv/.venv
DEBUG Using Python 3.12.3 environment at .venv/bin/python
DEBUG Trying to lock if free: .venv/.lock
DEBUG Requirement satisfied: anyio
DEBUG Requirement satisfied: idna>=2.8
DEBUG Requirement satisfied: sniffio>=1.1
DEBUG All editables satisfied:
Audited 1 package in 16ms

What is Python @ default?
Should Found Python interpreter cpython 3.12.3 perhaps be something like Found<EMAIL_ADDRESS>at...? "Python interpreter {impl}" is maybe a bit redundant?

"Python @ default" was resolved / removed in #3789
The implementation name display is being changed in https://github.com/astral-sh/uv/pull/3791 — I do agree it feels a little redundant though. Let me rebase onto main and tweak a bit more.

Now it looks like
DEBUG Searching for interpreter that fulfills any Python in virtual environments
DEBUG Found CPython 3.12.3 at `.venv/bin/python` (active virtual environment)
DEBUG Using Python 3.12.3 environment at .venv/bin/python

Specialized the search message per request kind so we can do a little better e.g.
❯ VIRTUAL_ENV=.venv cargo run -q -- pip install anyio -v
DEBUG Searching for Python interpreter in virtual environments
DEBUG Found CPython 3.12.3 at `.venv/bin/python` (active virtual environment)
DEBUG Using Python 3.12.3 environment at .venv/bin/python


Support templates

It seems like this plugin does nothing when a template is used in HTMLWebpackPlugin. It would be useful, if possible, for this plugin to add the attributes to the htmlWebpackPlugin variable that gets passed to the template somehow (in the files field or a separate field).

Same problem for me

Oh really?
This is not a use case that I have tested for - I'll take a look

Same issue too

https://github.com/hypotenuse/html-webpack-scripts-plugin. May be used in conjunction with templates and with inject: false. Also has simplified syntax.

Taking html-webpack-template as a spec for template.
Setting custom one
<!DOCTYPE html>

  <meta charset="utf-8">
  <title><%= htmlWebpackPlugin.options.title || 'Webpack Test'%></title>
  <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=5.0">
  <% for (var css in htmlWebpackPlugin.files.css) { %>
    <link href="<%= htmlWebpackPlugin.files.css[css] %>" rel="stylesheet" type="text/css">
  <% } %>

  <% for (var item in htmlWebpackPlugin.options.scripts) { %><%
      if (typeof item === 'string' || item instanceof String) { item = { src: item, type: 'text/javascript' } } %>

  <% } %>

  <% for (var chunk in htmlWebpackPlugin.files.chunks) { %>

  <% } %>

Using ScriptExtHtmlWebpackPlugin with no injection
// ..

config.plugins.push(new HtmlWebpackPlugin({
  // ..
  inject: false,
  // ..
}));

// ----------------
// ScriptExtHtmlWebpackPlugin
config.plugins.push(new ScriptExtHtmlWebpackPlugin({
  inline: [
    /runner.*.js$/
  ]
}));

// ..

It only partly works.

 for all chunks are set (template gets htmlWebpackPlugin.files.chunks)
it also compiles in , although it was asked to be inlined...
... and runner.*.js is not inlined (nothing in htmlWebpackPlugin.options.scripts)

Thanks @hypotenuse
// ----------------
// HtmlWebpackScriptsPlugin
config.plugins.push(new HtmlWebpackScriptsPlugin({
  inline: /runner.*.js$/
}));

for the same template behaves as expected.

Hello - I'm sorry to say that this plugin is no longer being maintained.  I have tried to close all issues ahead of doing this but instead have found that the issue list just keeps growing.  I simply do not have the time to keep up.  Sorry.
Please keep an eye on the README where I will record anyone who forks this repo with the intention to supporting it in the future.


ID Exchange

So I tried to use better end with my modpack. It works fine in the single player mode but when I start a Server it changes IDs of blocks as you can see in the picture. I already had the better end mod alone on the server so its not a problem causing of/with other mods. It changes the ID of seagrass or what its called (standard minecraft ID).
Thanks for helping me.
Manuki

BetterEnd doesn't change identifiers of any vanilla blocks. Here is a screenshot from server world with installed BetterEnd:

Actually all block IDs stored in block palettes, so this looks like semi-impossible:

Probably your world is corrupted, you can try to generate another one or manually fix your world with WorldEdit. If bug is still present than it is probably an API bug

The thing is that even if I start my Server and also my game only with "BetterEnd" it still have this bug. I also deleted the world more then once and let my server regenerate a new one. Yesterday I tried to set up my server from 0 but it didn't help. So the only thing that would make sense would be the API bug. My question now is how do I fix the API bug? Do I need to reinstall the Fabric API or something else?
Thanks for helping ^^

You can try to download server again, install the latest Fabric API and the latest BettrEnd version. If this will not help please send server and client logs

If this bug will appear again please reopen the issue


Fix for an small typo I saw while reading the documentation

Hello!
While reading the documentation for this project I found this small typo.

Thanks!


python311Packages.httpx-socks: 0.8.1 -> 0.9.0

Diff: https://github.com/romis2012/httpx-socks/compare/refs/tags/v0.8.1...v0.9.0
Changelog: https://github.com/romis2012/httpx-socks/releases/tag/v0.9.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 293445 run on x86_64-linux 1

6 packages built:

python311Packages.httpx-socks
python311Packages.httpx-socks.dist
python312Packages.httpx-socks
python312Packages.httpx-socks.dist
searxng
searxng.dist


Increase target area on code copy blocks

Can we please increase the target area on the code copy blocks?

I vote for the entire code block to be the target. If that isn't possible, then can we at least make the copy icon larger and add some padding to it, so that the icon target is a larger area? The copy icon is currently 12x12px I think that is smaller than our standard.
Thanks

@luciaaaaaaa, marking this for design input.


README.md: PMEM preparation in VMs

This used to be part of README-qemu-notes.md, which was removed
because it seemed obsolete. But labeling is still needed in virtual
machines.

Very good description!
You use "$ sudo ndctl" but 1st occurrence misses sudo and has double $.
Just in previous block I had used # to indicate that root account is used.
Your style with sudo is more clear. But now we have two styles next to each other.
What about other parts of doc, should we check all..

"sudo" may be clearer, but it's also longer and not always necessary. Let's stick with #. I've changed my commands.
I also made one more change:
 the virtual machine. Instead, that region must be made available for
-use with `ndctl` because when the virtual machine comes up for the
+use with PMEM-CSI because when the virtual machine comes up for the
 first time, the entire region is already allocated for use as a single

I had copied the text from the older QEMU readme, but looking at it again the wording seemed a bit odd. Clearly the region is already usable with ndctl - it's just PMEM-CSI that cannot do anything with it...


feat(dbpull): MongoDB

Note: MongoDB is a preview feature
db pull --url is not supported with MongoDB provider because it's a preview feature (it works only if a local schema has the preview flag in it)
re-introspection does not work (overwrites at the moment)

We can merge this after a review.
Next to be done https://github.com/prisma/prisma/issues/9557 (I'll check on Monday for this)


RawConfigParser instance has no attribute 'read_dict'

When trying to run GoogleScraper I get this attributeerror:   File "/usr/local/lib/python2.7/site-packages/GoogleScraper/config.py", line 70, in parse_config     cfg_parser.read_dict(Config) AttributeError: RawConfigParser instance has no attribute 'read_dict'
My command was GoogleScraper -m http --keyword "apple" -v2
Am not using in virtualenv.

My guess: Did you install GoogleScraper with pip / for python2? Then your GoogleScraper executable (mine was at /usr/local/bin/GoogleScraper) will run GoogleScraper with python2. At least this was the case for me.
My recommendation is using a virtual environment. I don't have experience in python3 but some in virtualenv - it seems that pyenv should be used instead of virtualenv, since virtualenv and python3 don't go well together. The readme mentions virtualenv, I wonder if that's just outdated.


About applies to

It's supposed that the normalization rules are applied to Teams as well. Not only to Lync/SfB

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

ID: 940f3a9e-f4cb-4c60-c57a-3d064e79677a
Version Independent ID: 52842215-3cd7-c8c8-6556-d166a92a7b48
Content: New-CsVoiceNormalizationRule (skype)
Content Source: skype/skype-ps/skype/New-CsVoiceNormalizationRule.md
Service: skypeforbusiness-powershell
GitHub Login: @tomkau
Microsoft Alias: tomkau

@officedocsbot assign @yogkumgit

@tomkau Tom, are you positive on adding Microsoft Teams to the applies to metadata field of this article?
Asking this because this would apply to many other cmdlets that are shared between SfB and Teams.
Thanks for your feedback. cc @kenwith

@EvgenyArtemyev - thank you for taking the time to open the issue. I know it takes time to share knowledge as you gain it while working with the products and I appreciate it.
I can provide some info on this one. The "applicable" in the metadata is a technical construct based on the PowerShell module. Screenshot below from the raw markdown for this file at this link: https://raw.githubusercontent.com/MicrosoftDocs/office-docs-powershell/master/skype/skype-ps/skype/New-CsVoiceNormalizationRule.md

An open source tool, PlatyPS is used to generate and update the markdown from the PowerShell modules. The same tool is also used to build an XML file so that Get-Help <cmdlet> works and pulls a recent version of the GitHub help. PlatyPS relies on the "applicable" to build that XML file.
There is Skype and Teams functionality in the Skype module so even though the module is functionally accurate to 'applicable' to Teams it is in the Skype module. It is due to how Teams pulled in Skype and uses underlying components. I have heard there is an effort to consolidate the Skype and Teams PowerShell modules into a single module and that will solve this problem when that happens. I know the product team is well aware of the confusion and I am too on the docs side.
What we can do if there are particular areas that are confusing is add a note saying something along the lines that even though the cmdlet or parameter lives in the Skype PowerShell module it also affects Teams.


scalakata playground

Would it be possible to deploy scalakata with Quill on the classpath and an in-memory db? It could be helpful to discuss issues and a good way for new users to quickly try out the lib.
I imagine the AWS's free tier would be enough to run it.
http://scalakata.com
@getquill/maintainers

Could we close that in favor of #848?

👍


Question about the Fig.12

Hi @octavian-ganea ,
Thank you for your great work!
I have a question about the Figure 12. Would you please tell me how to draw Figure 12?
In fact, I try to draw it as follows.
First, the bound and unbound data are from the folder data/benchmark5.5/structures/
Then, I calculate the crmsd and irmsd of bound and unbound structures as the code in eval_pdb_outputset.py, where the unbound coordinate as the 'pred_coord' and the bound one as the 'ground_truth_coord'. However, I met the error that most of the number of residues in bound and corresponding unbound structures are not equal (to be exact, 179 ligand not matched , and 28 receptor not matched). So, how did you matched the corresponding bound and unbound structures? Or there is any mistake as I did?
Looking forward to your reply! Thanks!

Hi,
Yes, you are right, the DB5.5 data contains many inconsistencies between the bound and unbound structures for the same protein, not sure exactly why. To generate that plot, we just did a dynamic programming implementation of the longest common subsequence problem to align the two sequences, and then only use those residues in the RMSD computations. This is not a perfect solution, but not sure what can be done to alleviate this data issue ...

Thank you for your reply!
I also try to do that as you said with the Biopython-> pairwise2.align.globalxx() function to align the bound and unbound sequences. And I get the result with complex_rmsd_median: 1.455,  complex_rmsd_mean: 2.1065, complex_rmsd_std: 2.5771. I seems similar to your published result, however, the max complex rmsd I calculated is 29.3533, which is greater than 35 in Figure 12. So I am not sure that whether there is any mistake in my code. It will be so great if you could share the code of how to get the rmsd between bound and unbound structures. Thanks so much!

Yep, here is the code (also see the full list of RMSD computed below).

import os

import numpy as np
from src.utils.protein_utils import rigid_transform_Kabsch_3D
from src.utils.db5_data import get_residues_db5
import scipy.spatial as spa

# Dynamic programming implementation of LCS problem
# Returns length of LCS for X[0..m-1], Y[0..n-1]
def LCSubSeq(X, Y):
    m = len(X)
    n = len(Y)
    L = [[0 for _ in range(n + 1)] for _ in range(m + 1)]

    # Following steps build L[m+1][n+1] in bottom up fashion. Note
    # that L[i][j] contains length of LCS of X[0..i-1] and Y[0..j-1]
    for i in range(m + 1):
        for j in range(n + 1):
            if i == 0 or j == 0:
                L[i][j] = 0
            elif X[i - 1][1]['resname'].iloc[0] == Y[j - 1][1]['resname'].iloc[0]:
                L[i][j] = L[i - 1][j - 1] + 1
            else:
                L[i][j] = max(L[i - 1][j], L[i][j - 1])

    # Following code is used to print LCS
    index = L[m][n]

    # Create a character array to store the lcs string
    # lcs = [""] * (index + 1)
    # lcs[index] = ""
    lcs_X = [""] * (index)
    lcs_Y = [""] * (index)

    # Start from the right-most-bottom-most corner and one by one store characters in lcs[]
    i = m
    j = n
    while i > 0 and j > 0:
        # If current character in X[] and Y are same, then current character is part of LCS
        if X[i - 1][1]['resname'].iloc[0] == Y[j - 1][1]['resname'].iloc[0]:
            lcs_X[index - 1] = X[i - 1]
            lcs_Y[index - 1] = Y[j - 1]
            i -= 1
            j -= 1
            index -= 1

        # If not same, then find the largest of the two and go in the direction of larger value
        elif L[i - 1][j] > L[i][j - 1]:
            i -= 1
        else:
            j -= 1
    return lcs_X, lcs_Y

def filter_residues(residues):
    residues_filtered = []
    for residue in residues:
        df = residue[1]
        Natom = df[df['atom_name'] == 'N']
        alphaCatom = df[df['atom_name'] == 'CA']
        Catom = df[df['atom_name'] == 'C']

        if Natom.shape[0] == 1 and alphaCatom.shape[0] == 1 and Catom.shape[0] == 1:
            residues_filtered.append(residue)
    return residues_filtered

###################
def get_alphaC_loc_array(bound_predic_clean_list):
    bound_alphaC_loc_clean_list = []
    for residue in bound_predic_clean_list:
        df = residue[1]
        alphaCatom = df[df['atom_name'] == 'CA']
        alphaC_loc = alphaCatom[['x', 'y', 'z']].to_numpy().squeeze().astype(np.float32)
        assert alphaC_loc.shape == (3,), \
            f"alphac loc shape problem, shape: {alphaC_loc.shape} residue {df} resid {df['residue']}"
        bound_alphaC_loc_clean_list.append(alphaC_loc)
    if len(bound_alphaC_loc_clean_list) <= 1:
        bound_alphaC_loc_clean_list.append(np.zeros(3))
    return np.stack(bound_alphaC_loc_clean_list, axis=0)  # (N_res,3)

def get_alphaC_list(bound_predic_clean_list):
    lll = []
    for residue in bound_predic_clean_list:
        df = residue[1]
        alphaCatom = df[df['atom_name'] == 'CA']['atom_number'].iloc[0]
        lll.append(alphaCatom)
    return lll

def get_CA_coords(b_file, u_file):
    b_residues = filter_residues(get_residues_db5(b_file))
    u_residues = filter_residues(get_residues_db5(u_file))
    before = len(b_residues)
    b_residues, u_residues = LCSubSeq(b_residues, u_residues)
    # print('after b_res', get_alphaC_list(b_residues))
    # print('after u_res', get_alphaC_list(u_residues))
    # print(functools.reduce(lambda x, y : x and y, map(lambda p, q: p == q, get_alphaC_list(b_residues),get_alphaC_list(u_residues)), True))

    b_residues = get_alphaC_loc_array(b_residues)
    u_residues = get_alphaC_loc_array(u_residues)
    after = b_residues.shape[0]
    if before == after == u_residues.shape[0]:
        print(b_file, u_file)
    print(before, after, u_residues.shape[0])
    return b_residues, u_residues

def plot_all():
    input_dir = './data/benchmark5.5/structures'
    pdb_files = [f for f in os.listdir(input_dir) if os.path.isfile(os.path.join(input_dir, f)) and f.endswith('.pdb')]

    all_rmsd = []

    num_test_files = 0
    for file in pdb_files:
        if file.endswith('_l_u.pdb'):
            ll = len('_l_u.pdb')
            bound_file = os.path.join(input_dir, file[:-ll] + '_l_b.pdb')
            unbound_file = os.path.join(input_dir, file[:-ll] + '_l_u.pdb')
        elif file.endswith('_r_u.pdb'):
            ll = len('_r_u.pdb')
            bound_file = os.path.join(input_dir, file[:-ll] + '_r_b.pdb')
            unbound_file = os.path.join(input_dir, file[:-ll] + '_r_u.pdb')
        else:
            continue

        b_coords, u_coords = get_CA_coords(bound_file, unbound_file)

        dmat = spa.distance.cdist(b_coords, b_coords)
        dmat = dmat + 100. * np.eye(dmat.shape[0])
        # print('mean d = ', np.min(dmat, axis=1).mean())
        # print('median d = ', np.median(np.min(dmat, axis=1)))

        if b_coords.shape[0] != u_coords.shape[0]:
            print(file)
            continue
        num_test_files += 1
        R, b = rigid_transform_Kabsch_3D(b_coords.T, u_coords.T)
        b_coords_aligned = ((R @ b_coords.T) + b).T
        rmsd = np.sqrt(np.mean(np.sum((b_coords_aligned - u_coords) ** 2, axis=1)))

        all_rmsd.append(rmsd)
        # print('num_test_files done ', num_test_files)

    print('all_rmsd', all_rmsd)
    print(len(all_rmsd))
    return all_rmsd

all_rmsd = plot_all()

# all_rmsd = [0.6962418, 27.03626981434666, 2.9686131, 3.5345614, 1.7044786, 1.319995, 5.1798444, 0.5049575, 0.45675388, 2.6630943, 2.546523, 1.2128848, 0.59461874, 1.1774287, 0.8224659, 1.5111822, 1.1599942, 1.7826275, 0.65784246, 0.5582014, 2.8252356, 1.9506255, 1.3800596, 2.7822397, 2.0161128, 1.4857557, 0.80386686, 1.2378623, 2.7285552, 19.54151, 1.5791698, 0.77282906, 0.32637906, 0.4722987, 1.2494422, 0.7638261, 1.3630565, 0.5317533, 1.9764836e-06, 0.55156565, 2.7910872, 0.9011328, 1.1561608, 2.5926828, 3.8203578, 0.70295584, 1.1666499, 0.6264738, 0.6232077, 1.1883411, 0.56530625, 1.2028227, 1.3477685, 1.8282441, 1.5747728, 2.128397, 1.7903032, 4.280821, 1.4810741, 2.0309215, 1.7389334, 1.3359979, 0.9335407, 1.2722429, 1.0772936, 1.4273612, 0.90363824, 1.1851745, 0.65965843, 0.6105662, 0.88963103, 0.7989469, 3.0286636, 1.4925646, 1.0704238, 1.2667646, 0.9554937, 2.1890259, 0.4463879, 3.0691504, 12.041163, 1.1361443, 1.6985788, 1.8809482, 0.70238364, 2.1219745, 2.4284933, 1.1817397, 0.618453, 3.5171118, 1.7590178, 0.57367647, 0.8153385, 0.5950234, 1.4212565, 0.8913942, 4.423849, 0.6001566, 3.0566185, 0.45846713, 0.3916329, 3.1001763, 0.84036165, 1.2455623, 0.94656336, 0.43186194, 0.70226103, 2.1483116, 0.65598303, 0.49707252, 9.990827, 1.2918882, 0.77361584, 1.4257747, 0.80301446, 1.5146624, 1.3873624, 0.9554937, 1.0153382, 1.3809197, 0.9295433, 0.4461008, 0.3887217, 2.71268, 0.6058705, 2.5367131, 1.5577396, 2.7555687, 1.5684363, 0.5662212, 1.8282441, 0.34369707, 3.5691407, 29.304473532867767, 0.8604853, 3.8777807, 0.3287732, 1.192507, 0.53047264, 1.1643264, 1.8756974, 4.397976, 1.9317511, 0.8851453, 4.280821, 1.6856755, 2.1955128, 1.0414593, 3.8239803, 0.6302643, 1.2624161, 2.8827038, 1.0478029, 3.4473317, 0.770314, 0.64568347, 1.4387469, 1.6138345, 1.7465917, 1.962105, 1.0688684, 1.5654682, 0.43968844, 0.7649709, 1.7110707, 1.9716086, 1.4674189, 1.9981797, 0.8618321, 0.6721722, 2.071398, 0.51870245, 2.982918, 0.8164904, 3.4028974, 1.0031127, 0.6929141, 1.1985035e-06, 22.282746453028356, 1.1930548, 0.49166816, 4.2538457, 0.889148, 1.6589879, 0.7498187, 0.4058273, 0.5056364, 0.62057555, 4.0950875, 1.1783762, 1.0915266, 9.825888, 0.6582492, 1.2743578, 0.4995857, 10.788652, 11.905804, 0.8787025, 2.2948368e-06, 3.3075848, 0.6850603, 1.7519094, 1.9719495, 0.44748992, 0.55696625, 0.6096156, 0.64054054, 3.0099761, 2.3606842, 1.6786654, 1.1942681, 0.6978604, 0.43543476, 7.2658124, 0.8521949, 1.4701211, 1.7214085, 0.5289863, 1.1149201, 3.729744, 1.7212167, 5.581814, 3.9925954, 0.9347552, 2.0152748, 5.539305, 1.3955237, 1.253993, 18.731201, 0.5405805, 1.1983395, 1.3311571, 1.0794693, 2.2760947, 38.5945, 2.7223735, 1.6750678, 0.51923317, 1.7674416, 2.7703874, 3.936683e-06, 1.4250864, 1.7576742, 0.66976196, 2.1966534e-06, 3.8855648, 0.572205, 1.06187, 0.4635174, 0.5988311, 0.46330267, 1.9889144, 1.5581557, 3.1054556, 1.0541656, 1.6353214e-06, 1.032354, 0.665778, 1.087051, 0.6215222, 0.60802054, 6.606358, 0.5751045, 0.4689752, 0.37107491, 1.067861, 4.729647, 4.178835, 1.2696042, 0.74371666, 4.3974447, 3.731839, 1.1009775, 6.2470875, 2.1379695, 2.7581146, 3.2439315, 0.7497935, 4.4688506, 0.74708706, 1.2113068, 3.0039606, 1.6956894, 0.7109091, 1.6787137, 32.79343038081955, 7.0521705e-06, 1.1089412, 0.86929286, 2.2734303, 1.9720659, 1.9889144, 0.5684412, 0.72357994, 1.0572548, 1.2094994, 0.87182486, 0.6639882, 0.6363185, 0.68100965, 1.0455867, 2.7395332, 7.231181, 0.629642, 7.0089383, 2.757306, 1.0041324, 1.650062, 2.9461417, 2.0531807, 0.3912766, 0.6195286, 2.1035693, 0.93100214, 1.7368435, 2.107763, 1.3961453, 1.3059765, 1.1841563, 7.2915254, 0.8731526, 2.5055175, 1.0232973, 2.1887197, 1.6135501, 1.7934625, 2.218598, 0.6318677, 1.1169442, 1.41212, 1.8013055, 0.83939904, 0.5386748, 1.3009996, 1.0179409, 1.5744836, 1.7691509, 1.8033211, 4.0990553, 0.40228027, 1.5470148, 2.229582, 1.0745113, 1.2127255, 0.64667904, 3.870754, 0.6516309, 0.5308961, 0.6830703, 0.37585256, 3.6248713, 1.0849175, 1.1546352, 0.35467917, 0.8584139, 1.713536, 0.9835134, 4.863827, 1.1013104, 1.5991068, 2.7803283, 0.5220013, 0.7984924, 1.1942775, 5.522912, 1.0631386, 0.45954815, 0.8350289, 1.6775175, 2.48245, 1.1269842, 0.84553206, 0.59515387, 0.7430531, 1.1843232, 0.8322676, 0.71300054, 0.8555032, 1.1336085, 1.536494, 29.936849938155948, 0.5567714, 0.50779784, 2.8568308, 0.5459214, 0.766995, 0.9020894, 1.6567634, 1.1025717, 0.7798935, 1.0375565, 0.63780326, 0.66015315, 0.5144089, 0.87448967, 2.9359785e-07, 0.51562625, 1.1334723, 1.5090711, 2.2924914, 0.9140785, 8.136824, 3.3150349, 0.3546582, 6.9085704e-06, 2.0621643, 1.1151338, 4.43456, 0.51987344, 1.9622375, 1.1580093, 0.27936888, 0.76604265, 1.1473372, 0.7945121, 1.3007371, 1.3704231, 1.1207563, 2.4275997, 1.1122599, 17.701017, 0.48094028, 3.4398391, 4.495497, 3.4427142, 1.3895931, 0.8203486, 1.0786057, 4.4397645, 3.2132168, 1.5061754e-06, 5.1517496, 4.1289624e-07, 1.9721442, 0.8347928, 9.394635, 0.35105443, 1.3121231, 1.9221034, 0.95891297, 1.2227244, 8.433344, 2.9149215, 1.9889144, 0.37265316, 2.0469155, 2.2152584, 0.4578064, 1.2578293, 2.6659403, 0.62059456, 4.739158, 8.855496, 0.48358005, 0.6706964, 0.9605975, 1.148719, 1.3905442, 3.1397026, 6.062035, 0.66542107, 1.0939509, 3.4895027, 0.7346339, 0.80699295, 3.7031268e-07, 1.1419114, 1.5155606, 0.72397625, 2.7118328, 1.6419793, 0.63384485, 0.8620122, 3.213217, 9.210633, 0.41391, 0.58243823, 0.24865517, 0.50800824, 1.123511, 1.8632666, 0.4743436, 2.338837, 2.268722, 10.291622, 0.41552648, 1.7778066, 1.0593673, 0.7203342, 1.0793355, 1.1355674, 0.2461644, 1.548148, 0.5702176, 0.5160546, 2.4865284, 1.7082264, 1.0295498, 1.2837969, 1.753832, 1.0659016, 0.7255667, 0.62942755, 2.8856826, 0.74441904, 0.46673965, 0.5662806, 1.1644644, 2.005169, 0.51830894, 1.7189244, 0.7285067, 2.3819146, 1.0490074, 0.6707141, 2.7278082, 1.0616714, 4.2380977, 0.8752755, 0.32089052, 1.5652136, 1.512635, 1.0160714, 1.4508268, 1.3173221, 0.32655928, 0.40831152, 0.5914244, 0.86104983, 2.3572385, 1.2258587, 3.525297, 10.330421, 4.2397623, 1.1214422, 0.32262784, 10.559156, 0.429923, 1.493592, 0.35212544, 0.9639773, 1.025263]

import plotly.express as px

fig = px.histogram(all_rmsd, nbins=100)
fig.add_vline(x=np.median(all_rmsd), annotation_text="median = " + "{:.1f}".format(np.median(all_rmsd)) + ' Å',
              annotation_font_size=20, annotation_position="top right", line_dash = 'dash', line_color = 'firebrick', annotation_font_color= 'firebrick')
fig.add_vline(x=np.mean(all_rmsd), annotation_text="\t<br>mean = " + "{:.1f}".format(np.mean(all_rmsd)) + ' Å',
              annotation_font_size=20, annotation_position="top right", line_dash = 'dash', line_color = 'green', annotation_font_color= 'green')

fig.update_xaxes(title='RMSD (Å) bound - unbound structures (of the Cα atomic coordinates)', title_font = {"size": 20}, tickfont = {"size": 20})
fig.update_yaxes(title='Frequency in DB5.5', title_font = {"size": 20}, tickfont = {"size": 20})

fig.show()


[Bug]: ReferenceError: CSS is not defined

Version
29.7.0
Steps to reproduce

Init new npm project.
Install jest and jest-environment-jsdom
Create file jest.config.json with {"testEnvironment": "jsdom"}
Create file css.test.js with following content:

test('CSS', () => {
  expect(CSS.escape('.foo#bar')).toBe('\\.foo\\#bar');
});

Expected behavior
Should handle CSS interface method calls without crashing.
Actual behavior
Crashes with "ReferenceError: CSS is not defined"
Additional context
Apparently this is caused by jest-environment-jsdom using outdated version of jsdom which did not have support for CSS interface at the time. So either jsdom should be updated or at least provide official workarounds in the documentation for situations where jest-environment-jsdom does not handle a specific web API.
Environment
OS: Windows 11
npm v10.2.3
node v18.19.0

Newer JSDOM versions have dropped support for the Node versions we support, so you'll need to bring your own. https://www.npmjs.com/package/@jest/environment-jsdom-abstract can help reduce the boilerplate (I should've added a readme, but you can essentially copy https://github.com/jestjs/jest/tree/v30.0.0-alpha.3/packages/jest-environment-jsdom and replace the version of jsdom)


addTrack and dtmf

Chrome currently has support for:

Legacy: addStream
Legacy: createDTMFSender
Which work together.

Chrome is also shipping (M64):

Spec: addTrack
Which does not work together with createDTMFSender.

But does not have support for:

Spec: RTCRtpSender.dtmf

When using addTrack, adapter.js's shim of RTCRtpSender.dtmf does not work because native addTrack does not work together with native createDTMFSender.
Two paths forward to resolve this issue:

Anyone who wants to use DTMF has to rely on addStream for it to work.
adapter.js keeps shimming addTrack for another version, meaning addTrack is built on top of addStream and RTCRtpSender.dtmf will work like before.

What do you think is the preferred way forward, @KaptenJansson and @fippo ? Do we keep shimming addTrack so that dtmf doesn't break or do we update failing examples - like https://webrtc.github.io/samples/src/content/peerconnection/dtmf/ fails on Canary - to use addStream instead of addTrack?

I would rather not delay testing of the native addTrack by adapter (who spot + report issues) users for the sake of DTMF

The https://webrtc.github.io/samples/src/content/peerconnection/dtmf/ is fixed by https://github.com/webrtc/samples/pull/972.
Let's keep this issue open until addTrack and dtmf works, which likely means removing shimming when properly supported by Chrome.
Also check Firefox status...

this just made it to beta in the expectations. But you know what is great: IT MEANS THE FLAKY TEST JUST FAILS ALL THE TIME 😂

Chrome has fixed addTrack+dtmf in M66, closing issue.


Include Raspberry Pi default username

I found raspberry in the top SSH passwords, should the default username be included?

Makes sense

The locations now is: Usernames/top-shortlist.txt

Duplicate. This has been included in #164.

This has been fixed. Thanks for the submission!


"ignoring prop" warnings?

Description
I am getting a bunch of these warning ignoring prop: mask, from null to null for AnimatedSprite

Im not sure why or what to do about them.
Steps to reproduce
The code looks like this:
import * as React from "react";
import { Point2D } from "@markd-co/battletabs-shared";
import { Container, AnimatedSprite } from "@inlet/react-pixi";
import * as PIXI from "pixi.js";
import { ShipSegmentMask } from "./ShipSegmentMask";
import { AnimatedSpriteWithPixelPerfectCollisions } from "./AnimatedSpriteWithPixelPerfectCollisions";
import { withPixelPerfectCollisions } from "./HOCs/withPixelPerfectCollisions";

interface Props extends React.ComponentProps<typeof AnimatedSprite> {
  pivot: Point2D;
}

const Sprite = withPixelPerfectCollisions(AnimatedSprite);

export const ShipSegment: React.FC<Props> = React.memo(({ pivot, ...rest }) => {
  const [mask, setMask] = React.useState<PIXI.Graphics | null>(null);

  return (
    <>
      <ShipSegmentMask ref={setMask} />
      <Sprite
        hitmapResourceId={"vikingShipsHitmap"}
        mask={mask}
        pivot={pivot}
        {...rest}
      />
    </>
  );
});

Additional info

@inlet/react-pixi version: 5.0.0
React version: 16.13.0
ReactDOM version: 16.13.0
PIXI version: 5.3.0

Hi @mikecann
Good point, a null value is a possible value for prop mask. Right now we prompt these warnings to tell the user a possible invalid value is set. At runtime we don’t know the valid types for a prop.
I can create a PR which bypass the mask null value.

 Ill submit PR's for these values when I come across them.

I've pushed a patch. It's now fixed in v5.0.1


Add Board Game Atlas API

Add Board Game Atlas API to Games & Comics

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Hi @andre-j3sus
Thanks for your contribution ;)
We have some problems with Public APIs, so we won't be able to review/add this improvement right now.
Read this issue for more information, please: https://github.com/public-apis/public-apis/issues/3104


App Engine Admin API

Explore using this for deploys and taking the Cloud SDK out of the picture:
https://cloudplatform.googleblog.com/2016/08/automate-deployments-and-traffic-splitting-with-the-App-Engine-Admin-API.html

This is the corresponding Java App Engine Admin API client library.

That's the beta of the Java client library. We need the release version.

I don't think there is one yet.

https://developers.google.com/api-client-library/java/apis/appengine/v1


PrismaClientValidationError: Invalid this.getSessionTable().upsert() invocation

Issue summary
Before opening this issue, I have:

[x] Upgraded to the latest version of the relevant packages

@shopify/* package and version:

  "@shopify/shopify-api": "11.1.0",
  "@shopify/shopify-app-remix": "3.0.2",
  "@shopify/shopify-app-session-storage-prisma": "5.0.2",
  "@prisma/client": "5.16.2",
  "prisma": "5.16.2",

Node version: v18.20.3
Operating system: Ubuntu 22.04 LTS
[x] Set { logger: { level: LogSeverity.Debug } } in my configuration, when applicable
[x] Found a reliable way to reproduce the problem that indicates it's a problem with the package - sort of, read below
[x] Looked for similar issues in this repository
[ ] Checked that this isn't an issue with a Shopify API - no idea how to do it, I temporary changed version of REST API to 2024-04 - no difference.

I develop an extension to Shopify theme.
 Available options are marked with ?.
10:00:48 │ remix      │     at Sn (/home/lw/project/shopify-personalization-client-editor/node_modules/@prisma/client/runtime/library.js:115:7526)
10:00:48 │ remix      │     at _n.handleRequestError (/home/lw/project/shopify-personalization-client-editor/node_modules/@prisma/client/runtime/library.js:122:6570)
10:00:48 │ remix      │     at _n.handleAndLogRequestError (/home/lw/project/shopify-personalization-client-editor/node_modules/@prisma/client/runtime/library.js:122:6235)
10:00:48 │ remix      │     at _n.request (/home/lw/project/shopify-personalization-client-editor/node_modules/@prisma/client/runtime/library.js:122:5919)
10:00:48 │ remix      │     at async l (/home/lw/project/shopify-personalization-client-editor/node_modules/@prisma/client/runtime/library.js:131:9116)
10:00:48 │ remix      │     at async PrismaSessionStorage.storeSession (/home/lw/project/shopify-personalization-client-editor/node_modules/@shopify/shopify-app-session-storage-prisma/dist/cjs/prisma.js:29:13)
10:00:48 │ remix      │     at async TokenExchangeStrategy.authenticate
(file:///home/lw/project/shopify-personalization-client-editor/node_modules/@shopify/shopify-app-remix/dist/esm/server/authenticate/admin/strategies/token-exchange.mjs:33:13)
10:00:48 │ remix      │     at async Object.authenticateAdmin [as admin]
(file:///home/lw/project/shopify-personalization-client-editor/node_modules/@shopify/shopify-app-remix/dist/esm/server/authenticate/admin/authenticate.mjs:79:29)
10:00:48 │ remix      │     at async loader (/home/lw/project/shopify-personalization-client-editor/app/routes/app.tsx:22:3)
10:00:48 │ remix      │     at async Object.callRouteLoader (/home/lw/project/shopify-personalization-client-editor/node_modules/@remix-run/server-runtime/dist/data.js:66:16) {
10:00:48 │ remix      │   clientVersion: '5.16.2'
10:00:48 │ remix      │ }

Problems started some time after I updated dependencies, at first it was everything alright, problems started with no apparent reason. Maybe I just don't understand something in Shopify's ecosystem.
My Prisma database is default - one migration executed successfully, one table Session with appropriate columns:

id          TEXT not null primary key,
shop        TEXT not null,
state       TEXT not null,
isOnline    BOOLEAN default false not null,
scope       TEXT,
expires     DATETIME,
accessToken TEXT not null,
userId      BIGINT

Expected behavior
Authenticate request successfully, write request data to Session table without problems.
Actual behavior
Exception described above, Session table stays unchanged (no new data about shop which made request)
Steps to reproduce the problem

I started the project by using shopify-remix-app-template when dependencies had corresponding latest versions:

"@shopify/shopify-api": "10.0.0",
"@shopify/shopify-app-remix": "2.8.2",
"@shopify/shopify-app-session-storage-prisma": "4.0.2",
"@prisma/client": "5.15.0",
"prisma": "5.15.0",

then updated to latest dependencies to incorporate changes from 2024-07 Shopify API release.
Remove data in Session table in Prisma database, to force authentication request.
When you want to see extension page in Shopify Admin, you see exception.

Debug logs
Output before exception:

09:51:30 │ remix      │ [shopify-api/INFO] version 11.1.0, environment Remix
09:51:30 │ remix      │ (node:41659) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
09:51:30 │ remix      │ (Use node --trace-warnings ... to show where the warning was created)
09:51:30 │ remix      │ [shopify-app/INFO] Authenticating admin request
09:51:30 │ remix      │ [shopify-app/DEBUG] Attempting to authenticate session token | {sessionToken:
{"search":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczpcL1wvaGFwaWVzLWx1a2Fzei5teXNob3BpZnkuY29tXC9hZG1pbiIsImRlc3QiOiJodHRwczpcL1wvaGFwaWVzLWx1a2Fzei5teXNob3BpZnkuY29tIiwiYXVkIjoiZDFkMDcxNjIxMjJmYWQ5N2I2OGE2N2E1MW
VkOWRkMzEiLCJzdWIiOiI4NjE0MTk2MDM2NiIsImV4cCI6MTcyMDc3MDc0NCwibmJmIjoxNzIwNzcwNjg0LCJpYXQiOjE3MjA3NzA2ODQsImp0aSI6ImJhMzFmZWUzLWUwMWUtNDMyMy1iNTU4LTIxODc3NmZlZTNmYSIsInNpZCI6ImFjNDU4MWNiLTMzZDEtNDY2My1hMDc0LWRjODc0NjJhNTFkNyIs
InNpZyI6IjEyYjQ3MmQxZGIwZmRkZTU3YjAwOTU2ZjdkZGEwMGRlODczZTI2ZDY4YTI0YTg5OTU0NmVjMjMzODM0ZGJiOGYifQ.lZ2m3NN1890K9k9VjxbU489B7z5v3iNUIdh36Fdtrp4"}}
09:51:30 │ remix      │ [shopify-app/DEBUG] Validating session token
09:51:30 │ remix      │ [shopify-app/DEBUG] Session token is valid | {payload: {"iss":"https://hapies-lukasz.myshopify.com/admin","dest":"https://hapies-lukasz.myshopify.com","aud":"d1d07162122fad97b68a67a51ed9dd31","sub":"861
41960366","exp":1720770744,"nbf":1720770684,"iat":1720770684,"jti":"ba31fee3-e01e-4323-b558-218776fee3fa","sid":"ac4581cb-33d1-4663-a074-dc87462a51d7","sig":"12b472d1db0fdde57b00956f7dda00de873e26d68a24a899546ec233834dbb8f"}}
09:51:30 │ remix      │ [shopify-app/DEBUG] Session token is valid | {shop: hapies-lukasz.myshopify.com, payload: [object Object]}
09:51:30 │ remix      │ [shopify-app/DEBUG] Loading session from storage | {sessionId: offline_hapies-lukasz.myshopify.com}
09:51:30 │ remix      │ [shopify-app/INFO] Authenticating admin request
09:51:30 │ remix      │ [shopify-app/DEBUG] Attempting to authenticate session token | {sessionToken:
{"search":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczpcL1wvaGFwaWVzLWx1a2Fzei5teXNob3BpZnkuY29tXC9hZG1pbiIsImRlc3QiOiJodHRwczpcL1wvaGFwaWVzLWx1a2Fzei5teXNob3BpZnkuY29tIiwiYXVkIjoiZDFkMDcxNjIxMjJmYWQ5N2I2OGE2N2E1MW
VkOWRkMzEiLCJzdWIiOiI4NjE0MTk2MDM2NiIsImV4cCI6MTcyMDc3MDc0NCwibmJmIjoxNzIwNzcwNjg0LCJpYXQiOjE3MjA3NzA2ODQsImp0aSI6IjkwN2VjNDliLWRiMTAtNDIyYS1hMDY3LWQ2YjU3MDVhNzdiNiIsInNpZCI6ImFjNDU4MWNiLTMzZDEtNDY2My1hMDc0LWRjODc0NjJhNTFkNyIs
InNpZyI6ImYyYjFiN2VmMWNiYjBkMDdhMzUyZGI3YjQ5NzU0ZGIxNzFkNmViZTZiYzk5MDI0NTA2MWRlYzJlMWIwM2M1MDkifQ.EXUQrt6d90teHBoeBMF_GyBYsLZqnccwOYjkm_el3_E"}}
09:51:30 │ remix      │ [shopify-app/DEBUG] Validating session token
09:51:30 │ remix      │ [shopify-app/DEBUG] Session token is valid | {payload: {"iss":"https://hapies-lukasz.myshopify.com/admin","dest":"https://hapies-lukasz.myshopify.com","aud":"d1d07162122fad97b68a67a51ed9dd31","sub":"861
41960366","exp":1720770744,"nbf":1720770684,"iat":1720770684,"jti":"907ec49b-db10-422a-a067-d6b5705a77b6","sid":"ac4581cb-33d1-4663-a074-dc87462a51d7","sig":"f2b1b7ef1cbb0d07a352db7b49754db171d6ebe6bc990245061dec2e1b03c509"}}
09:51:30 │ remix      │ [shopify-app/DEBUG] Session token is valid | {shop: hapies-lukasz.myshopify.com, payload: [object Object]}
09:51:30 │ remix      │ [shopify-app/DEBUG] Loading session from storage | {sessionId: offline_hapies-lukasz.myshopify.com}
09:51:30 │ remix      │ [shopify-app/INFO] No valid session found
09:51:30 │ remix      │ [shopify-app/INFO] Requesting offline access token
09:51:30 │ remix      │ [shopify-app/INFO] No valid session found
09:51:30 │ remix      │ [shopify-app/INFO] Requesting offline access token
09:51:30 │ remix      │ [shopify-api/INFO] Creating new session | {shop: hapies-lukasz.myshopify.com, isOnline: false}
09:51:30 │ remix      │ PrismaClientValidationError:

EDIT:
As a test, I removed @shopify/shopify-api dependency, because I see that @shopify/shopify-app-remix forces correct dependency version.
So, my package.json looked like this:
        "@shopify/shopify-app-remix": "3.0.2",
        "@shopify/shopify-app-session-storage-prisma": "4.0.5",

This set: shopify-api: "10.0.0" but Shopify CLI shows [shopify-api/INFO] version 11.1.0, environment Remix. Authentication successful, but no latest Shopify REST API (2024-07), the latest is 2024-04.
When I change shopify-app-session-storage-prisma to next version (5.0.0), this automatically sets shopify-api: 11.1.0. Authentication ends with an exception, latest Shopify REST API (2024-07) is accessible / is in node_modules of shopify-api
This is pretty messed up... Then what's the purpose of explicit @shopify/shopify-api dependency in shopify-app-remix-template when shopify-api version is determined by @shopify/shopify-app-remix?

Yeah I was blind, I didn't follow migration guide. After those steps, everything is working.
Thanks for dependency fixes @paulomarg, now everything is organized as I would expect.

Just one last thing: in the future, please be careful about posting tokens online as they can be used to make API requests. I suggest you uninstall and reinstall the app in the store contained in the logs here to reset the exposed tokens.
Thanks for the advice, already reinstalled.

Thanks for help one more time @paulomarg!


[DO NOT MERGE] DS-761 replace image element in hero

Jira
https://pegadigitalit.atlassian.net/browse/DS-761
Summary
Removes image component from the hero component
Details
How to test

Confirm no usages of the image component within the hero component
Confirm no visual changes in the hero component examples in pattern lab

Known issue with spacing:


How to identify the weather of the scene

Hello, Thank you for your great work!
As I am working on object detection, is there a weather label in the dataset?

Hi @WoodwindHu
Unfortunately, we don't have weather attributes nor do we have exact dates for the logs so we can't reference historical weather data. If you'd like to annotate weather attributes then that would be welcomed by the community.


(BOLT-843) Support retrying on failed nodes.

Bolt will now write a /.last_result.json file whenever a
command fails. Users can use this file to target nodes from the last
failure with the --retry flag.
In order to avoid spreading nodes to a new file this also adds a
target key to the status hash of Results.
This still needs predocs.

CLA signed by all contributors.


!play is broken

!play is broken, it expects YouTube video ID only and gives error in console.

Console error:
Uncaught Promise Error: TypeError: dispatcher.on(...).catch is not a function
Error at lines 16-18 of commands/play.js

Temporarily disabled the command while I find a fix for it

Removed play command and all future plans to add music commands to the bot

Closed as the fix would stop future projects with newer dependencies.

Reasons for this: https://github.com/NdT3Development/DiscordBot/projects/1#card-4201008


Any way to config generated file ?

This plugin generates file components.d.ts in root folder,  can this be configed ?

No, it's not from this plugin.

No, it's not from this plugin.

Sorry about that, It's from your vite-plugin-components. I am checking the docs.


Support triggers between workspaces

Feature description 💡
It would be great if it was possible to trigger a plan / plan&apply / plan & approve & apply etc in another workspace.
We would be able to get rid of our CI system for the ordered deployment of a change between the dev account (workspace), staging, and prod.
( it might be possible to do this now, but using VCS for the dev, and then api calls for staging and prod.)
Anything else?
In the future, we're expecting stacks from hashiconf, to vaguely group multiple workspaces of the same module, for different envs or regions.  This can be a starting block for connecting workspaces.

I believe this is very related to the state consumption by remote workspaces. Since a workspace can be a consumer of another one, any change in the consumed workspace should trigger a run in the consumer workspace. This is already implemented in TFC, and it's very useful

I believe this is very related to the state consumption by remote workspaces (which I believe it's not implemented here, because there's no way to allow consumption from certain workspaces). Since a workspace can be a consumer of another one, any change in the consumed workspace should trigger a run in the consumer workspace. This is already implemented in TFC, and it's very useful

Hello @juan-vg state consumption from one workspace to the other is supported, you could check here

Hello @juan-vg state consumption from one workspace to the other is supported, you could check here
Hello @alfespa17! While I agree it's possible, what I mean is that the way of doing so is limited compared to TFC. I mean, TFC allows to specify which workspaces are allowed to consume, so not necessarily all of them are allowed.

However, the main topic of my previous message was about triggers and how useful they are when talking about scenarios where consumers are broadly used.


Add patch

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Waiting on #5

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

(Quikc note: I still need to increase the build number etc)


handling calling parent constructor and assignment of $this->prop

FIX: $this->prop =  now causes a public $prop variable to be declared. It wasn't catching them all when multiple ones were being done.
FIX: constructors calling the parent constructor using the super(...) syntax wasn't getting expanded to parent::__construct(...)

Nice one! Thanks!


deleted deprecated dashboard

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Requesting review @brian-f-harness and @Rohit-Kaliki

@joeyouss We no longer want to update the archive/redirects/client-redirects-aug-16-2023.js file. Please add the redirect to the frontmatter.
https://harness.atlassian.net/wiki/spaces/PD/pages/21469528316/HDH+Front+Matter+Re-direct

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66609b8e461e204c251daf05--harness-developer.netlify.app


Upgrade Rust version to 1.67

FYI, this involves numerous clippy errors :)

When trying to update the rust version by executing rustup update but still shows the same version (not latest version),
then check out the following tips:
rustup override set stable
info: using existing install for 'stable-aarch64-apple-darwin'
info: override toolchain for '/Users/sigridjin.eth/Documents/github/simperby' set to 'stable-aarch64-apple-darwin'

  stable-aarch64-apple-darwin unchanged - rustc 1.67.0 (fc594f156 2023-01-24)

so do I need to wait for the toolchain to be updated to 1.67 version?


Inconsistent "content" values

Whenever the css is generated, it seems that the content values are varying slightly. So when I try to use the unicode values in my css the icons are swapping around. I tried setting descent: 0 thinking that would force the icons to sort the svg assets alphabetically but that doesn't seem to be the case. What's the best way to ensure consistent unicode content values across builds?

It seems like this isn't sorting them properly:
https://github.com/itgalaxy/webfont/blob/master/src/standalone.js#L27

@heyjones thanks for issue, yep, i think it is related to webfont, can your create issue there and provide minimum reproducible test repo, thanks!

@heyjones I thought this was a problem but I think it's actually not... assuming our problems are the same.
My experience is that yes, the content values change (the unicode value changes, I assume because webfont at the core uses an object and iterates through it which is not necessarily in order). The subsequent unicode character changes, however, are properly propagated to the resulting CSS file (from what I can tell, anyways) - in other words, despite the changes to both the font file itself and the CSS output (or scss or whatever you use), the resulting output matches as it should. The problem I have is that Webpack is not re-compiling the new changes properly, which causes breakage because the new font files get consumed by the browser but my SCSS is not being updated. @evilebottnawi I just opened an infinite recompile issue that I'm experiencing alongside this issue.. not sure if they are related (doesn't seem like it but I thought I'd point them out).

@heyjones ^ping on the above comment :)

Okay so after #77 gets merged (infinite compilation fix) this still is an issue, although it is partially solved. The cause of the issue seems to be 2 things (prior to the merging of #77):

Because of the known issue of having to ignore generated font files to avoid the infinite recompile, Webpack will therefore never recompile the font on changes. This is what #77 fixes.
Once #77 is merged, it will still be an issue because of the fact that the assets are cached by the browser. We could implement something like hashing to force a new download (particularly in the dev server) because I noticed that clearing cache now fixes the issue with my local fixes for the other issue. I haven't looked into how to do this outside of manually doing it via the webfont package but I don't really want to reach that far back to do something as simple as a cache refresh.

@evilebottnawi what are your thoughts on that?

@dudewad in fact, caching must be implemented webfont, i don't have time now for this, but we can use https://github.com/zkat/cacache or https://github.com/royriojas/flat-cache (better) for this, it should be very easy to implement.
Also, I would like to repeat that the solution was to make this plugin not quite right, it should be as loader. It is allow to use webpack cache, also it is allow to avoid problem with infinity loop. When I wrote this plugin I did not understand well webpack architecture, now my knowledge is better :smile:

It sounds like you made that decision when you knew about as much as I know now! I'd love to see the loader version someday. If there's any way I can help I'd like to -- I want to learn webpack better and the docs aren't helping much!

@dudewad let's merge, but without test it is very dangeour

@evilebottnawi I am fine waiting for test. For what it is worth, my current version is not having any issues. I'd rather you run tests so that we don't run into issues... but it sounds like you don't have time?  :/

Oh, and FYI, I don't have access to merge :) You'll have to do it.

I fixed this, setting the maxConcurrency to 1,
so it uses only 1 core of your CPU, and the content values are always the same
     new WebfontPlugin({           files: helpers.root('src/assets/svg/*.svg'),           css: true,           maxConcurrency: 1,           template: 'css',           fontName: 'webfont',           cssTemplateFontPath:${getAssetsPath(isProd)}/fonts/,           dest: {               fontsDir: helpers.root('src/assets/fonts/'),               stylesDir: helpers.root('src/assets/css/')           }       })

Beautiful! I'll give that a try... no time right now but when I get around to it I'll try to confirm that.

Fixed in webfont, just update to latest version. Thanks!

Fantastic!! Thanks!

Sorry for delay, a lot of work


Clean up employee scheduling constraint provider test

KIE bot, please don't spam me :)

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test


perf: mark the result of builder.IsZero as boolean to save constraints when used in future

Description
Hi there, thanks for your amazing work!
In the current implementation of gnark, builder.Select introduces a constraint to enforce that the condition is boolean. However, when the condition is from the result of builder.IsZero, this constraint is unnecessary, as builder.IsZero always returns a value m that is guaranteed to be either 0 or 1.
This PR marks m in builder.IsZero as boolean, so that we can save 1 constraint when using the result in subsequent operations like Select.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas (N/A)
[ ] I have made corresponding changes to the documentation (N/A)
[ ] I have added tests that prove my fix is effective or that my feature works (N/A)
[x] I did not modify files generated from templates
[x] golangci-lint does not output errors locally
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules (N/A)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @winderica - thanks for the contribution. I have been busy before holidays to review but will definitely get to it next year. Sorry for the delay.
I think the fix would be useful but I would first have to see thoroughly the test suite to see if there are not unintended side-effects.


Updated Network Plugin to handle the boot order of netsrmgr

Updated Network Plugin to handle the boot order of netsrmgr.

Removed error message that was returned if Initialize() was called when the netsrvmgr is NOT running.
Removed the thread that runs continuously to look for the netsrvmgr process and subscribe to events.
Changed the retry logic into 1sec timeout and only once if the plugin is not inited  (or the netsrvmgr dependency was not met)

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/3871/rdkcentral/rdkservices

Commit: 2db6fcabd25f93d6145d69acc1cdff07f253ab5f

Report detail: gist

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/3871/rdkcentral/rdkservices

Commit: a086f6c41aab6a1711bf491f86cd2e478b430059

Report detail: gist

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.


Update privacy policy in line with advisor

Replaces entire privacy policy with new version, as instructed by GDS privacy advisor.

Ahh excellent, thanks for spotting that @lfdebrux !

You can preview this change here:
Built with commit 44941223a220ff61918b6c0e96b80e9354a50450
https://deploy-preview-1660--govuk-design-system-preview.netlify.app


feat: implement getFragmentName

Description
Related #9055
Currently, there's no way to easily extract the name of a generated fragment.
This pull request adds the implementation for a helper function: getFragmentName to extract the fragment's name from the DocumentNode object via some AST utils.
It returns the name of the generated fragment as a string literal so we can compose fragments or queries with it:
import { graphql, getFragmentName } from './gql';

export const FilmFragment = graphql(/* GraphQL */ `
  fragment FilmItem on Film {
    id
    title
    releaseDate
    producers
  }
`);

const fragmentName = getFragmentName(FilmFragment); // 'FilmItemFragment'
//    ^? const fragmentName = "FilmItemFragment"

There are two implementations introduced here:
First, we have the function itself to traverse the AST object and return the name of the FragmentDefinitionNode.
Then there's a specific TypeScript implementation so we could statically infer the fragment's name as a string literal from  $fragmentName field on the type. One advantage of that is that returning a string type isn't helpful, I would like to be able to have the fragment's name directly in my IDE (string literal) without having to open the generated code. To achieve this, I split FragmentType into a new type: FragmentName which is reused by FragmentType and the new helper function.

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Screenshots/Sandbox

How Has This Been Tested?
The code snippet above was tested in a generated example.
Checklist:

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

Hey @charpeni, first of all, thank you for all your contributions. 😍
Could you share any use-cases for this feature - might this be even something that could be implemented in user-land?
I also think that this conflicts with this option. 🤔  https://github.com/dotansimha/graphql-code-generator/blob/1edfa6ec8651c4e55b3d15d984430bcf1e908fa7/packages/presets/client/src/index.ts#L75-L81

My pleasure, thanks to all of you for this amazing project. ❤
I've left more context and use cases in the associated issue: https://github.com/dotansimha/graphql-code-generator/issues/9055, but to quickly summarize the primary use case:
The getFragmentName() helper is helpful to retrieve the name of a giving fragment if you don't want to rely entirely on a "magic string" to consume/spread the fragment, e.g.:
+import { FilmItemFragment } from './FilmItem';

const allFilmsWithVariablesQueryDocument = graphql(/* GraphQL */ `
  query allFilmsWithVariablesQuery($first: Int!) {
    allFilms(first: $first) {
      edges {
        node {
-         ...FilmItem
+         ...${getFragmentName(FilmItemFragment)}
        }
      }
    }
  }
`);

Or, if you would like to follow Apollo's naming convention:

FilmItem.fragments = {
  film: getFragmentName(FilmItemFragment),
};

// ...

const allFilmsWithVariablesQueryDocument = graphql(/* GraphQL */ `
  query allFilmsWithVariablesQuery($first: Int!) {
    allFilms(first: $first) {
      edges {
        node {
         ...${FilmItem.fragments.film}
        }
      }
    }
  }
`);

I totally agree with you, this is something that could be implemented in user-land—or even only generated behind a feature flag. I thought it could be handy for consumers that don't want to rely entirely on magic strings. Depending on how well GraphQL is integrated into the build tools, it could be harder to maintain fragment references without hard references, especially when the feedback loop is taking longer. Another concern would be a potential conflict between fragments, the codegen tool will prevent duplicated fragments, but it doesn't prevent you from typing the wrong one.
Quickly like this, I would see three options:

We add getFragmentName to the default template for fragment-masking.ts
We hide the generation of getFragmentName behind a feature flag / config option, e.g. { generateGetFragmentNameHelper: true }
We don't include this in the code at all, but we add a mention in the documentation

@n1ru4l let me know if you find this helpful and what your recommendation would be for this helper, I will be happy to adapt the pull request.


[bug 1133771] Rework thank you page view

This reworks the Thank You page view and tests. We continue to use the
thankyou page flag, but this allows us to specify a response_id in the
querystring to make it easier to examine and debug behavior in
production.
Plus it gets rid of the thanks_sad.html template.
r?

Ok, that's all I've got. Looks pretty good.

^^^ Fixes from feedback.
Does that look ok?

Looks good! r+


Appstudio update test-component-pac-bmxp

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-bmxp-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
9 seconds
clone-repository

✅ Succeeded
18 seconds
appstudio-configure-build

✅ Succeeded
2 minutes
build-container

✅ Succeeded
7 seconds
show-summary

Pipelines as Code CI/test-component-pac-bmxp-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
8 seconds
appstudio-configure-build

✅ Succeeded
2 minutes
build-container

✅ Succeeded
9 seconds
show-summary


Allow listing casks when using brew list

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

[x] Have you successfully run brew tests with your changes locally?

Allow listing casks when running brew list --casks. Since brew list either lists formulae or casks, flags that are not accepted by brew cask list are forbidden by brew list --casks.

Makes sense, thanks again @whoiswillma!


Make CopyProp and DS2CPS handle loops

CopyProp and DS2CPS both currently either bail or fail if a loop matches their patterns.
CopyProp needed to be extended to explicitly work on branches (f, t)#cond (args, ...) instead of just directly applied non lams.
DS2CPS just died of a stack overflow due to infinitely following the loop recursion.
DS2CPS should generally be a bit more stable now.
One major downside of this change is, that when having a loop, we must not set the PE filter to true, but without doing so, we introduce some unnecessary overhead for the non-loop cases.
Note, the loop support greatly depends on copyprop being able to propagate the continuations through branches.

This looks overly complicated to me.

CopyProp needed to be extended to explicitly work on branches (f, t)#cond (args, ...) instead of just directly applied non lams.

IMHO only dealing with directly applied nom lams is enough due to the EtaExp - which makes this whole CopyProp::rewrite_conditional stuff superfluous. Maybe there is another problem with the EtaExp or its interaction with the CopyProp.

The lit/main_loop_cn.thorin test case fails for master, but is supported by this branch. The main issue here is that the continuations have to be fully removed for the ll backend to be happy. Afaict, EtaExp would not get rid of those parameters. LamSpec does not support this either and would be complicated to adapt to it (as an RWPass) and for the cases that I came up with, CopyProp seemed to be able to solve these situations by propagating through the branch as well.
I'm currently still investigating an issue with the CopyProp, though (calling the loop from the test case twice - once from main, once from the exit continuation).

I removed the CopyProp changes from this PR. I currently don't see a straightforward way to avoid that DS2CPS generates a loop where all lams have a continuation. The input for the CopyProp was already Eta reduced, which made it pretty clean.
I've been considering adding an extra PM phase so we can use the CopyProp changes without it fighting against the Beta reduction, as it currently does for some cases, but that would again require tighter coupling from the optimize function to the plugins since CopyProp is in the mem dialect. Before I do that, I'm wondering whether we might want to generalize the pass registration further:
I could imagine that it'd make sense to have a map similar to the backends map that is currently used for the ll backend. This map is filled by the plugins with pass->name() -> <Pass>* thorin_add_<dialect>_<pass>(PassMan& pass).
This has two benefits:

we can write textual descriptions of the pass pipeline, we want to use (think LLVM's new opt --passes="function(<pass>,<pass>)" syntax, where () can be used to group passes together into a PM.
we can more easily build up a custom pipeline in frontend X, since we just load all plugins we need, and don't have to ask dlsym for the creation functions, but instead can query the map directly with the passes' name.

Thoughts?

I'll merge for now. We can discuss your other points next time in our online meeting :)


Preparations before introducing checked NPEs

Including the fix of #4755.

Also, there is a typo in the main commit:

we must make sure to evaluation all
three arguments

to **evaluate **

In this case, it's not about being consistent with the JVM as much as being consistent with our own non-optimized semantics. Our optimizer must not introduce a UB NPE in a program that does not expose one.

Of course. That makes perfect sense.

If we wanted to delay NPEs until after the arguments are evaluated, like the JVM does, we would have to generate assignments of all receivers and arguments to all method calls in the entire program before doing the calls. Even with Unchecked semantics. That would explode code size. So we chose to specify NPEs as coming earlier instead.

Hm... I realize this is totally unrelated to this PR, but wouldn't it be OK to change the throwing point in unchecked mode? UB can do far worse things than changing where something fails, can't it?

Hm... I realize this is totally unrelated to this PR, but wouldn't it be OK to change the throwing point in unchecked mode? UB can do far worse things than changing where something fails, can't it?

No, it's emphatically not OK, not in that direction. From checked to unchecked, you can delay UB or remove it or do something else from the point that UB happened onwards. But you cannot have UB happen earlier than the check that would be performed in checked mode. Otherwise, even when your tests pass in checked mode, you have no guarantee about the correctness of the unchecked mode.


Render buttons after on layout

This new prop delays the rendering of the buttons until an OnLayout call has been dispatched, giving us the width of the overlay component.
This was done to fix a scenario where the buttons would show while rendering an heavy overlay item that does not span the entire screen width.
This caused a glitchy feeling of seeing the button for a sec and then having it disappear.

I need this upgrade, please!!


Add full list of supported AMD GPUs and related LLVM to troubleshooting docs

It's an extension of the 0.1.29 preview release notes, listing all supported AMD GPUs and their LLVM versions.

this looks like easy Commit, they most likely going to accepted it soon.

@Abdalmajeed-96 why do you even bother to comment this PR if you have literary nothing to add?


Start data refresh schedule on Tuesdays UTC 00:00

Fixes #2979

Thanks for contributing this change @cullenwatson! We have a standard PR template which we use for pull request descriptions: https://github.com/WordPress/openverse/blob/main/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md
Do you mind editing the description of this PR to reflect the contents of the template, with the details for this PR filled in appropriately? Thanks!

@cullenwatson for future contributions, please fill out the PR template body. It includes helpful things like an area for PR description, testing instructions, and, critically, a checklist of things that must be addressed before a PR is ready for review. In this case, the DAG documentation generator needs to be run. Please run just catalog/generate-dag-docs locally and commit the changes.

Sorry for the duplicate feedback. Madison's comment hadn't come through while I was writing mine. Thanks for updating the DAG docs and the PR description :pray:

Np, cheers to 10k commits


PingTimeout does not use a time unit.

Since Elasticsearch 2.0, time units are obligatory.
This causes connection pooling not to work because of a null reference exception in the Sniff method.
I would have liked to use TimeUnitExpression but that belongs to Nest only.  Maybe it should be moved to Elasticsearch.net?

Just pushed a slightly different approach to fixing the tostring on timespan for sniff paths.
Leaving this open as a reminder to investigate the string settings after lunch :+1:

Hey @jonyadamit, I'm tidying up the branches to rename (branch move and delete)

2.0 to master
develop (current 1.x client) to 1.x

and as a consequence, closed this PR as a result of deleting the remote 2.0 branch, sorry! I've reinstated the branch to keep track of the open PRs but feel free to close this PR and open a new one with the change against  master :smile:

Hey @russcam, actually @Mpdreamz  only kept this PR open to remind him to investigate the string settings issue (see above).  If you fixed it already or have another way to keep track of that settings issue, this PR can be closed..


Benefits / Discussion of Source Based Derivation for Brave

Issue Description
Moving Brave derivation to build from source.
Currently Brave is built from a binary release, I am not anti-binary anti-source but I noticed that Brave relies on .deb files to build in Nixpkgs. This limits the platforms the package is available on to those supported by the binary release being used (only x86-64 linux as of now).
Brave Derivation
How Brave is Built
Well according to the brave browser repo,
Brave relies a lot on NPM
git clone git@github.com:brave/brave-core.git path-to-your-project-folder/src/brave
cd path-to-your-project-folder/src/brave
npm install

# the Chromium source is downloaded, which has a large history (gigabytes of data)
# this might take really long to finish depending on internet speed

npm run init

# start the component build compile
npm run build

Thoughts
While skimming over select packages, I realized some are built this way and some aren't.
This lead me to pose some questions here for discussion.

Am I correct in assuming building from source would allow for more systems(even Darwin) to build Brave by separating the derivation from platform specific file formats like .dmg .rpm or .deb?
Was there a specific reason as to why this approach wasn't taken? As a Nix Newbie, I'd like to learn from this.
Would buildNpmPackage be a good tool to use to replace the current derivation since brave-core seems to be built with npm?
What would the cons of this approach be?
Would this change be something people are interested in?

Conclusion
These are just some thoughts I while learning about Nix. Thanks for an amazing tool guys and all the hard work, hopefully I can keep learning and contribute towards nixpkgs too!

Answer to 2 is almost always that it was/is difficult to write or/and maintain the package.
You should ping the brave maintainers, oherwise they like won't see this

Might be worth taking some inspiration from https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=brave

@uskudnik  @rht @nasirhm Would you have any input to share on this topic?

While skimming over select packages, I realized some are built this way and some aren't. This lead me to pose some questions here for discussion.
1. Am I correct in assuming building from source would allow for more systems(even Darwin) to build Brave by separating the derivation from platform specific file formats like .dmg .rpm or .deb?

To be really honest, no. Everyone loves to say that source code is more portable than a precompiled binary, but in reality not everyone has the patience or the resources to ensure their code is indeed portable.

2. Was there a specific reason as to why this approach wasn't taken? As a Nix Newbie, I'd like to learn from this.

99% of the time it is because it is too complicated to deal with the original sources.
This happens a lot around confusing codebases or toolling - like NodeJS...
(The other 1% is bootstrap concerns.)

3. Would `buildNpmPackage` be a good tool to use to replace the current derivation since brave-core seems to be built with npm?

Be brave and try by yourself! (I couldn't lose the time for this bad joke!)
I am not so courageous.

4. What would the cons of this approach be?

The same cons of building anything from sources: ensure the toolchains match, patching and working around some unwarranted suppositions that fail on NixOS, reporting upstream bugs...

5. Would this change be something people are interested in?

Yes, but...