Data Validity

Hi, we are hoping to use your data to manage our congressional web archiving activity at the Library of Congress.  We used govtrack last year to try to keep up with the social media sites for the US Congressional members.  We are integrating this output with our database right now.  Just curious about the validity of data, for example, noticed that Joe Lieberman isn't on https://raw.githubusercontent.com/unitedstates/congress-legislators/master/legislators-current.yaml
and Schock and Nunnelee missing datapoints.

Hi Gina,
That's because the file you point to is of currently-serving legislators, so it wouldn't include Lieberman, Schock or Nunnelee, since none of them are currently serving. You can find them (and the rest) in our historical legislators file.

Thanks, some how I thought I saw some retired legislators, but we don't need those, so this file is good.  Keep up the good work!


Just want to make the modal width bigger.

is there a way or property to just make the modal width bigger without extending or overriding as it was before  with maxdialogwidth ?

Hi @ozayr,
Yes it is possible. You just need to create your own modal type. Here you need to override only
class _MyModalDialog extends WoltModalType {
  @override
  BoxConstraints layoutModal(Size availableSize) {
    final availableWidth = availableSize.width;
    double width = availableWidth > 523.0 ? 312.0 : availableWidth - padding.end;
    return BoxConstraints(
      minWidth: width,
      maxWidth: width,
      minHeight: 0,
      maxHeight: availableSize.height * 0.6,
    );
  }
}

Then, when you are calling your modal:
WoltModalSheet.show(
  context: context,
  modalTypeBuilder: (BuildContext context) {
    final width = MediaQuery.sizeOf(context).width;
    if (width < 523) {
      return WoltModalType.bottomSheet();
    } else {
      return _MyModalDialog();
    },
    ...
},

@ozayr Please re-open this issue if this does not answer your request.


:status header on responses for simpleHttpClient

//> using lib "com.softwaremill.sttp.client3::core::3.8.5"

val resp = simpleHttpClient.send(quickRequest.get(uri"https://www.google.com"))
resp.headers.foreach(println)

outputs
server: gws
...
:status: 200
...

Is it expected to see this extra :status header in the response headers?
Have not tested any other Sttp clients.

It seems these are HTTP/2 pseudo-headers. Indeed, we might want to filter :status out

We'll keep the pseudo-headers as-is, as they might contain valuable information, so no need to filter them out


Unhiding a hidden model reveals all its wrapping surfaces and turns muscles red

Steps to reproduce

Load two models.
Load two motions, one for each model.
Associate motion data.
hide one Model
hide the other
unhide a the first model

Expected result
The unhidden model appears exactly as it appeared when it was hidden.
Actual result

Wrapping objects now appear
muscles turn red irrespective of the state they were in when hidden

Environment and GUI version
Mac OpenSim 651d29f-2018-03-30

I tested this with Apoorva's model on my Mac and I don't see the wrapping surfaces appear or muscles turn red after following the steps that @aseth1 describes.

Used Apoorva's model and states files. The wrapping surfaces do not open when 'show' is selected on the top level model.
System:W10
Build:04-27-2018


mavlink: Fix uninitialized variable

mask can be used without be initialized.
Signed-off-by: Flavio Ceolin<EMAIL_ADDRESS>

+1


Fix codecov upload in travis builds

Issue # (if available): None
Description of changes: Our OpenSSL overrides interfere with curl, so we need to move the curl command that uploads code coverage reports to a separate script. I added it to the script build step so that if it fails, the build will also fail. I left the "make gcov" command in the main build script to keep it with the rest of our make commands.
To verify this fix works, check the output of the first build. You'll see a successful upload to codecov.io. In a broken build, you would see the message "curl: relocation error: /usr/lib/x86_64-linux-gnu/libcurl.so.4: symbol DSA_get0_key version OPENSSL_1_1_0 not defined in file libcrypto.so.1.1 with link time reference"
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (travis_fix@d6208dd). Click here to learn what that means.
The diff coverage is n/a.


Make SceneGraph tear-down robust to python garbage collection

🐛 Bug

See PR #349 for details.

@mosra any thoughts on this old issue? Still relevant or can we close?

It'll most probably get fixed by removing all SceneGraph usage altogether :smile:  In other words, I don't plan to invest any further time into the SceneGraph given that we want to replace it anyway.


The Atom Env Path on Windows constantly breaks after updates.

I'm currently on Atom 1.5.4. I've checked the atom.cmd file and it's pointing to the correct folder, and the path is pointing to C:\Users\LukeWatts85\AppData\Local\atom\bin
However, opening from cmd using "atom" no longer works. Instead it says "Cannot find path to specified file".
The "Open with Atom Editor" in the right-click menu also no longer works.
apm no longer runs.
This has happened numerous times before also. There must be a better way to update Atom than creating versioned folders and removing the old ones.
Other info:
Atom v 1.5.4
Windows 8.1

@lukewatts sorry to hear that you've been having problems with the auto-updater.  Fortunately a lot of the issues with auto-updating on Windows should be fixed starting in Atom 1.7.0, so I'm going to close this out.
As for versioned folders that is a core feature of Squirrel.Windows, which the Atom team has decided to keep using as the Windows auto-updater framework.

That doesn't help me right though. How long until 1.7?

Any tips how I might fix this problem in the meantime?

How long until 1.7?

I can't give an estimate unfortunately - it all depends on when the core team feels that it's ready.  Though once 1.6.0 comes out (which will most likely be within the next two weeks), you should be able to install the 1.7.0 betas.
Can you paste the exact contents of the atom.cmd file here?

@echo off
"%~dp0\..\app-1.5.4\resources\cli\atom.cmd" %*

Ok, and I'm guessing where atom also returns C:\Users\LukeWatts85\AppData\Local\atom\bin\atom.cmd?  If ...\bin\atom appears before atom.cmd, can you also check the contents of that file?

It's ok now.
I added the path to the global system env path variable and it all seems to work again now. Not sure why it stopped working with the local path variable though.
Thanks for your time though!


Getting node_modules error

Describe the Bug
I got an error from node_modules of reactflow out of nowhere while rendering the project. the error said:
............................
"ERROR in<EMAIL_ADDRESS>1:0-46
Module not found: Error: Can't resolve 'react/jsx-runtime' in 'C:\Users\piyus\Desktop\testingLP\lptest\node_modules@reactflow\background\dist\esm'
Did you mean 'jsx-runtime.js'?
BREAKING CHANGE: The request 'react/jsx-runtime' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '.mjs' file, or a '.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request."
.........................
Since then i have tried a lot, but nothing works. I haven't changed anything inside the reactflow node modules. i only downgraded my react-router-dom to v4 from v6, since then i am getting this error. The error does not go away even if ii upgrade the react-router-dom again.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
1.downgrade react-router- dom to v4.
2. run the project. You get this error.
3. Again upgrade the router dom to v6. Still you will recieve this error.
Expected behavior
It should just run without errors.
Screenshots or Videos

Platform

OS: Windows
Browser:  Chrome
Version: 91.1

Additional context
No response

I'm getting the same exact error message.

I'm getting the same exact error message. I updated from reactflow 11.7.4 to 11.8.1 and I'm running react 17.0.2
Updating to react 18 fixes the error, but breaks my whole app, as its not compatible with react 18.
I think the error message is misleading because adding the requested .js file extension doesn't change the error.
I would post examples but am behind a firewall and unable to copy and past code.

Thanks for the info, you are correct, upgrading to react 18 fixes the error but breaks the project as a whole. So, something else must be the solution to this issue.  Upgrading react might not be the only solution to this. Lets hope our reactflow experts help in fixing this. This is by far the best library. They doing a great work!

We can easily reproduce the error in any example of reactflow, by just downgrading the react v18 to 17 and installing react-router-dom v4.

Hello there! Having the same issue after upgrading from 11.7.4 to 11.8.1!
Our app builds correctly but our unit tests CI fail

@thmsgbrt how does your CI setup look like?

I had the same problem, react version: 17.0.2, react-dom version: 17.0.2,react-router-dom: 6.12.1. @moklick

Should be fixed in 11.8.2 - could you all check if it works again?

11.8.2 when will it be released? @moklick

10 min ago :D

Let me test it again! @moklick

Hey! @moklick , thanks a lott! everything's working fine now! Tested the new version for react v17 and v18 and also on router dom v4 and v6. Everything is working fine!

@thmsgbrt @qiyx2019 could you already check if the new release fixes it?

Yeap I was trying right now, I confirm it solved the issue for us too! Thank you so much

awesome!

I'm getting this same error now with V12 (released 3 days ago)

Same here, i'm trying to update from v10, thats why i have react-flow-renderer on my package.json
package.json:
{     "name": "frontend",     "version": "5.4.1",     "private": true,     "dependencies": {         "@date-io/date-fns": "^2.14.0",         "@material-ui/core": "4.12.3",         "@material-ui/icons": "^4.9.1",         "@material-ui/lab": "^4.0.0-alpha.56",         "@material-ui/pickers": "^3.3.10",         "@material-ui/styles": "^4.11.5",         "@xyflow/react": "^12.0.2",         "axios": "^0.21.1",         "date-fns": "^2.16.1",         "emoji-mart": "^3.0.0",         "formik": "^2.2.0",         "formik-material-ui": "^3.0.1",         "i18next": "^19.8.2",         "i18next-browser-languagedetector": "^6.0.1",         "lodash": "^4.17.21",         "markdown-to-jsx": "^7.1.0",         "material-ui-color": "^1.2.0",         "mic-recorder-to-mp3": "^2.2.2",         "moment": "^2.29.1",         "path-browserify": "^1.0.1",         "qrcode.react": "^1.0.0",         "query-string": "^7.0.0",         "react": "^17.0.0",         "react-color": "^2.19.3",         "react-csv": "^2.2.2",         "react-dom": "^17.0.0",         "react-flow-renderer": "^10.3.17",         "react-modal-image": "^2.5.0",         "react-number-format": "^4.6.4",         "react-query": "^3.39.3",         "react-router-dom": "^5.2.0",         "react-scripts": "^5.0.1",         "react-text-mask": "^5.5.0",         "react-toastify": "9.0.0",         "recharts": "^2.0.2",         "socket.io-client": "^3.0.5",         "text-mask-addons": "^3.8.0",         "use-sound": "^2.0.1",         "uuid": "^8.3.2",         "yup": "^0.32.8"     },     "scripts": {         "start": "react-scripts start",         "build": "react-scripts build",         "builddev": "react-scripts build",         "test": "react-scripts test",         "eject": "react-scripts eject"     },     "eslintConfig": {         "extends": "react-app"     },     "browserslist": {         "production": [             ">0.2%",             "not dead",             "not op_mini all"         ],         "development": [             "last 1 chrome version",             "last 1 firefox version",             "last 1 safari version"         ]     },     "devDependencies": {         "@babel/plugin-proposal-private-property-in-object": "^7.21.11"     } }

I'm getting this same error now with V12 (released 3 days ago)

Experiencing the same issue at this moment. 11.10.3 to V12.

Describe the Bug
I got an error from node_modules of reactflow out of nowhere while rendering the project. the error said: ............................ "ERROR in<EMAIL_ADDRESS>1:0-46 Module not found: Error: Can't resolve 'react/jsx-runtime' in 'C:\Users\piyus\Desktop\testingLP\lptest\node_modules@reactflow\background\dist\esm' Did you mean 'jsx-runtime.js'? BREAKING CHANGE: The request 'react/jsx-runtime' failed to resolve only because it was resolved as fully specified (probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '.mjs' file, or a '.js' file where the package.json contains '"type": "module"'). The extension in the request is mandatory for it to be fully specified. Add the extension to the request." .........................
Since then i have tried a lot, but nothing works. I haven't changed anything inside the reactflow node modules. i only downgraded my react-router-dom to v4 from v6, since then i am getting this error. The error does not go away even if i upgrade the react-router-dom again.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
1.downgrade react-router- dom to v4. 2. run the project. You get this error. 3. Again upgrade the router dom to v6. Still you will recieve this error.
Expected behavior
It should just run without errors.
Screenshots or Videos

Platform

OS: Windows
Browser:  Chrome
Version: 91.1

Additional context
No response

I get same problem


Search box breaks after viewing an alert config

Version
2.14.2441-release
Repro:

Type something in the search box at the top of the alerts list which results in the list being filtered.
Click one alert to view the config
Click back to the list

What happened:
Now the search box input is cleared, but the alerts list is still filtered.
What was expected:
The search box input would persist, or the alerts list would restore to the full list.

If I understand this correctly, is the workaround just to type a character in the search box then backspace it?

Yup you understand correctly. Not terribly broken, but did give me a little fright thinking that all of my alerts got deleted. 😅

Looks like this is already fixed in v3! I just tested it out. Feel free to reopen if I missed something.


Add support for mobile

Currently, some features only work on desktop, making this plugin incompatible with mobile phones.
Example: When we locate the full path to an image embed, we use an undocumented API to get the absolute path on disk so that we can upload the file. This only works on desktop. The alternative is to refactor the code, read the file through Obsidian's API (we actually already do that!), write the contents to a temporary file and use the path to that file as input for the image uploads.
To quickly know how to deal with the file uploads, we can use the following API:
Platform.isDesktop()
If it's not the case, then we need to deal with temp files. Also, the absoluteFilePathAvailable property will be false on embeds:

We publish image embeds to Cloudinary (when enabled). Those uploads use the embedAbsoluteFilePath.


Wheel support for aarch64

Summary
Installing markupsafe on aarch64 via pip using command "pip3 install pyyaml" tries to build wheel from source code
Problem description
Markupsafe don't have wheel for aarch64 on PyPI repository. So, while installing markupsafe via pip on aarch64, pip builds wheel for same resulting in it takes more time to install markupsafe. Making wheel available for aarch64 will benefit aarch64 users by minimizing markupsafe installation time.
Expected Output
Pip should be able to download markupsafe wheel from PyPI repository rather than building it from source code.
@markupsafe-team, please let me know if I can help you building wheel/uploading to PyPI repository. I am curious to make markupsafe wheel available for aarch64. It will be a great opportunity for me to work with you.

You'll want to work with the cibuildwheel project, we use them to build wheels.

Linux aarch64 was added in #173.

Linux aarch64 was added in #173.


Add --from YYYY-MM-DD support for email skipping

Today, one always has to process all emails when using this tool.  If I've processed folder F last month and I want to process it again now, this tool will fetch all emails in that folder.
It would be very useful to be able to support --from YYYY-MM-DD so emails older than the given date can be skipped.  This could speed things up dramatically.
I hope there is a way to truly skip emails based on their received date.  Otherwise, if emails need to first be fetched and parsed and can be skipped only after comparing their received date with the date given, there won't be much/any speedup.

This was implemented with -d instead of --from. Seems to work.


suse registry down + vulnerable year old images are being served

https://github.com/SUSE/bci/discussions/23#discussioncomment-9850955

Confirmation that the registry is back online and serving the correct SP5 and SP6 images instead of the vulnerable SP4. Waiting for an official statement to learn more about the issues. In general, when a container registry goes down, it must fully go down (and not serve ancient images after failing).

Update: Hash values for openjdk-devel are not matching the values reported on the website. Let's revisit in a couple of days time.


use strict in global scope may break when concatenated

It seems that the main file angular-froala.js has a use strict defined at the begining of the file:
use strict;
// code starts here

So if this file is concatenated with other files, it may break since it will apply use strict; to everything that is concatenated.
I would suggest wrapping code inside a closure (that's what mostly every projects do):
(function() {
   use strict;
   // code starts here
)}():

This way use strict; is restricted to froala's code and won't impact any other code.

@warpdesign Where are you seeing this? "use strict"; is inside the angular-froala directive

@cgallarno The tagged release 1.2.8 (https://github.com/froala/angular-froala/archive/1.2.8.zip) which is the version that gets installed through bower contains a version of the directive with the "use strict" outside of the directive.
Current Git version doesn't have the version indeed.

The bug seems to have been fixed in 2.0rc: a possible workaround is to force the "v2.0.0-rc.3" version in bower.json when adding angular-froala as a dependency.

@warpdesign it's updated to V2.0.1 now.

@stefanneculai ok, thanks!


Custom SSL Certificate Verify

I am using the Tus Py Client , in a macos High Sierra environment running Python 3.6.6. I am trying to make a HTTPS request to a tusd server.
The tusd server is running successfully behind an nginx proxy with an SSL terminated connection. I can visit the /files/ endpoint successfully in a browser via an SSL/TLS connection.
I am receiving an SSL: CERTIFICATE_VERIFY_FAILED error from
Tus Py Client  when making the connection request. Looking at the source code, Tus Py Client  uses the requests library to make a web request:
@_catch_requests_error
    def create_url(self):
        """
        Return upload url.
        Makes request to tus server to create a new upload url for the required file upload.
        """
        headers = self.headers
        headers['upload-length'] = str(self.file_size)
        headers['upload-metadata'] = ','.join(self.encode_metadata())
        resp = requests.post(self.client.url, headers=headers)
        url = resp.headers.get("location")
        if url is None:
            msg = 'Attempt to retrieve create file url with status {}'.format(resp.status_code)
            raise TusCommunicationError(msg, resp.status_code, resp.content)
        return urljoin(self.client.url, url)

If I make a HTTPS request to the tusd server manually from within a python shell, specifying the root certificate to the verify parameter, I can successfully connect:
import requests
resp=requests.get('https://test.example.com:1081/files',verify=<absolute path to cert file>)

However, the Tus Py Client  does not appear to offer this override.
I understand that Python 3.6+ now has it's own internal certificate store, so that explains why the trusted certificate in the macos keystore is ignored.
Then I read the documentation for the requests library. This suggests using the REQUESTS_CA_BUNDLE environment variable to specify trusted CAs. Indeed, after setting the environment variable with the path to the root CA certificate I was able to make the HTTPS request using the Tus-Py-Client library.
Am I on the right track with this solution, or is there a better way?
Moving forward is there the possibility to raise a new feature request allowing the path to the CA certificate to be specified in TusClient constructor which then gets passed onto the requests library under the hood?
Updated on 13/11/2018
The environment variable SSL_CERT_FILE must also be set to the root CA certificate to receive a HTTPS connection for http.client. This is because upload.py uses the http.client library and request.py uses requests library.
Kind Regards
dcs3spp

Ok, many thanks :)

hi @dcs3spp do you know what URL is being requested from tuspy client at the time the error is thrown?

Hi @ifedapoolarewaju,
Firstly, if both environment variables are set it works great. A great library that has made development much easier.
The URL endpoint that I am passing to tus-py-client is the tus endpoint https://test.example.com:1081/files/. I only receive an upload URL from tus-py-client if the REQUESTS_CA_BUNDLE environment variable is set. This allows the requests library to successfully send a request for creating an upload url, e.g. https://test.example.com:1081/files/640fd39f3325f301273576e12b3e335c+e22beb02-18fe-4b8e-a57f-39de91ec9fcb
If the SSL_CERT_FILE environment is not also set then a chunk fails to upload with an SSL VERIFY Exception from the http.client library.
Moving forward is there the possibility to raise a new feature request allowing the path to the CA certificate to be specified in TusClient constructor which then gets passed onto the requests and http-client libraries?
I have tried to include a detailed account below. Hope this helps.
Kind regards
dcs3spp
The tusd server is running behind an nginx proxy with an SSL terminated connection. I can visit the /files/ and /metrics/ endpoints for tusd successfully in browsers with a SSL/TLS connection successfully.
I am making a request to tus-py-client as follows:
try:
    ........<earlier code to to set path to file to upload and initialise meta data>
    uploader = tusd_client.uploader(filepath, chunk_size=6291456, metadata=meta_data_dict)
    uploader.upload()
    log.info("test_upload_document_template :: sent upload request to tusd server")
except TusCommunicationError as ce:
    raise RuntimeError(f"tusclient error {ce}") from ce

If I do not set REQUESTS_CA_BUNDLE environment variable then tus-py-client throws an exception when using the requests library. The exception is an SSLError and is triggered at line 205 of uploader.py in the create_url function  :
SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)'),))

If I set REQUESTS_CA_BUNDLE but do not set SSL_CERT_FILE then the following occurs.

A url is created for uploaded by the create_url function in uploader.py. This is https://test.example.com:1081/files/640fd39f3325f301273576e12b3e335c+e22beb02-18fe-4b8e-a57f-39de91ec9fcb
tus-py-client creates a TusRequest instance and starts the process of uploading file chunks. When the first chunk is uploaded an exception is thrown at line 287 of the _do_request function in uploader.py. This is triggered from line 276 in the upload_chunk function. The exception that is rasied is [SSL: CERTIFICATE_VERIFY_FAILED]. Upon further inspection of the source code, TusRequest uses the http.client library

If I then set REQUESTS_CA_BUNDLE and SSL_CERT_FILE everything works.

Closing this issue due to inactivity. Feel free to leave a comment if you want to continue the discussion :)


Center align social media icons

@PGautam27 I would like to work on this issue.

@vikrammahto you are assigned

@PGautam27  I already did this type of work, so please assign it to me under hacktoberfest 22.

I am closing this issue. @S-ahil-Saxen-a you can open up a new issue stating what u wanna do.


Adding support to use certificates on StompAMQ

Superseeds #8890

test this please

test this please

I think the tests won't be triggered unless Diego gets added to one of the WMCore/DMWM teams.
Since it's a one time PR, I guess we can just skip that, this module doesn't have any unit tests anyways...
I ran a pylint and code looks good. We can merge it and proceed with further testing afterwards.

Is username and password is not mandatory parameter anymore?

I am merging it but I think we should set the default values if the parameters are optional and validate in the function. (either cert/key or user/pass  has to be set - both cannot be empty)

Sigh, I was going to reply that that was a good point :-) We could make it all kwargs, this is the only usage in WMCore:
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/REST/HeartbeatMonitorBase.py#L67


Office-attendance-system

Description
Creating an Office attendance system using python.

using python Tkinter for designing UI of the whole application.
Functionality included:-

Create a new employee profile.
update old employee profile
store all that in a separate file
easy to use interface
unique id generation features

thanks, @Astrodevil for assigning it to me


Update with articles I found in 2022

Let me know if you disagree with anything or if you'd add anything else. Cheers!

Thanks for having a look!


Cannot read properties of undefined (reading 'parameters') in reportIncompatibleCallSignatureReturn

🔎 Search Terms
reportIncompatibleCallSignatureReturn
signatureRelatedTo
🕗 Version & Regression Information

This is a crash
Tried downgrading to 4.x but the crash happened again
Nightly crashes as well

⏯ Playground Link
No response
💻 Code
I tracked down the crash to these lines:
import * as results from 'ts-results';
import { Result as _Result } from 'ts-results';

// @ts-expect-error weird exports
const { Ok, Err } = results.default ? results.default : results;

export type Ok<T = void> = typeof results.Ok<T>;
export type Err<T = string> = typeof results.Err<T>;

Commenting the exports out, would fix the crash. However, I tried to reproduce it in a minimal example and couldnt get it to crash
From what I debugged, the crash happens because in signaturesRelatedTo source and target are not from the same length.
It loops over the targetSignatures and passes sourceSignatues[i] into reportIncompatibleCallSignatureReturn which is undefined
Hence the error Cannot read properties of undefined (reading 'parameters')
I am sorry that I cannot provide more info
🙁 Actual behavior
TypeError: Cannot read properties of undefined (reading 'parameters')
    at reportIncompatibleCallSignatureReturn (/home/repos/foo/node_modules/typescript/lib/tsc.js:62105:16)
    at signaturesRelatedTo (/home/repos/foo/node_modules/typescript/lib/tsc.js:62027:13)
    at structuredTypeRelatedToWorker (/home/repos/foo/node_modules/typescript/lib/tsc.js:61488:24)
    at structuredTypeRelatedTo (/home/repos/foo/node_modules/typescript/lib/tsc.js:60946:21)
    at recursiveTypeRelatedTo (/home/repos/foo/node_modules/typescript/lib/tsc.js:60899:19)
    at isRelatedTo (/home/repos/foo/node_modules/typescript/lib/tsc.js:60344:122)
    at someTypeRelatedToType (/home/repos/foo/node_modules/typescript/lib/tsc.js:60657:25)
    at unionOrIntersectionRelatedTo (/home/repos/foo/node_modules/typescript/lib/tsc.js:60554:14)
    at structuredTypeRelatedToWorker (/home/repos/foo/node_modules/typescript/lib/tsc.js:61104:23)
    at structuredTypeRelatedTo (/home/repos/foo/node_modules/typescript/lib/tsc.js:60946:21)

🙂 Expected behavior
yarn tsc should run and not crash
Additional information about the issue
I am using node v19.8.1 but I know it also happens on node v20.

I cannot reproduce this; can you please provide a repo that exhibits the problem?

It is a private repo. I tried to recreate the circumstances as good as I can but with no luck

Can you delete code until the issue goes away? There's unfortunately not a way to debug or test this from our end without a repro...

That's what I did. That's how I narrowed it down to the information above. I ended up exporting the things differently (I seperated type and function) and the issue went away. It never happened to me that tsc crashed on me so I wanted to report it even if it is really vague

As context: ts-results exports a really weird signature. e.g. the Err type:
export declare const Err: typeof ErrImpl & (<E>(err: E) => Err<E>);
export declare type Err<E> = ErrImpl<E>;

ErrImpl is the actual Error class

I don't think that combo is particularly weird; I just don't have anything to go off of here without a self contained repro.

I went ahead and checkout out the exact commit where this is happening and I can confirm that it crashes. Let me see if I can give you access to the repo

@jakebailey I invited you to the repo. checkout the "ts-reproduction" branch and run yarn && yarn tsc

Thanks, I can repro on that branch.

This is about as minimal as I've been able to get it:
class ErrImpl<E> {
  e!: E;
}

declare const Err: typeof ErrImpl & (<E>(err: E) => Err<E>);
type Err<E> = ErrImpl<E>;

type Err2<E = string> = typeof Err<E>;

const runners = new Map<string, Runner<any>>();

export type RunnerFn<T> = (options: { Err: Err2<T>; }) => any;

export class Runner<T> {
  public async run(runner: RunnerFn<T>) {
    return 1234
  }

  get<T>() {
    (runners.get("foo") as Runner<T>) ?? new Runner<T>();
  }
}

You're right about that intersection; it's basically nonsense. Upstream: https://github.com/vultix/ts-results/blob/910789d42f2cc8469f5fad2b80b1844e0c063269/src/result.ts#L178-L180
The only reason this type makes sense is because they emitted as ES5 which lets you """construct""" a class by calling it (but that's mega dubious).
This crash is not good, but I suspect that by using a different result lib that isn't so strange, you'll avoid this.

Feel free to remove me from your repo; I don't need access anymore and I'm sure you don't want a random person to have access long-term!

Wow that was fast!
I think they wanted the same name for type and factory function which I can understand from an aesthetical point of view.
I ended up reexporting factory and type under different names and that worked
Thanks for looking into this :)


Build 64-bit android binary

Starting August 1, 2019, your apps published on Google Play will need to support 64-bit architectures:

https://developer.android.com/distribute/best-practices/develop/64-bit

Thanks @orischwartz !


Reduce snippet dependency

Evolution of #358

Place all one-time-use snippets inline
Combined snippets when possible (social media meta tags, collection sorting)
Exceptions:

Social meta tags (Open Graph and Twitter cards) are combined to one snippet
Old IE js support (Respond.js, shivs, polyfills)
Onboarding markup
Handlebars.js templates

cc @carolineschnapp @mpiotrowicz @stevebosworth @fredryk

this is great! Were any of the snippets un-snippified twice? (eg snippet contents appear twice now)

Nope, no un-snippification, aka no reused code that doesn't live in a snippet. I'll give it another once over to make sure that's the case though.


Extension Mozilla used at Tor Browser

Issue: Tor Browser 12.0.3 (based on Mozilla Firefox 102.8.0esr) (64-bit), macOS 11.7.4 (20G1120) Big Sur. In the settings of automaticDark "Change themes based on the system theme" is activated. And "Do not change themes automatically (change only on startup and setup)". Now it's common for some page views to afford a white screen because the content can only be read on a white background. In your software this is impossible. Browsers like Apple Safari macOS have the app with toggle mode in the menu bar. Mozilla Firefox shows all extensions in the menu bar (?). Tor Browser doesn´t.

Hi @StefanAndPrviate ,
Are these two separate issues? For both, can you supply screenshots?

Now it's common for some page views to afford a white screen because the content can only be read on a white background. In your software this is impossible.
Browsers like Apple Safari macOS have the app with toggle mode in the menu bar. Mozilla Firefox shows all extensions in the menu bar (?). Tor Browser doesn´t.


[MB-8898] Reprice payment request service

Description
This PR creates a service to reprice payment requests.  See this Slack thread for more details.
I'm going to put this in draft for now until we decide how we're moving forward on the status as mentioned in the reviewer notes in this PR.
Reviewer Notes

I'm awaiting word on what status we want to set the old payment request to.  For now, I've just set it to REVIEWED_AND_ALL_SERVICE_ITEMS_REJECTED as a placeholder.  See this Slack thread for more details.
I had to revisit some previously committed test data setup that was not properly associating a service type to an MTO service item because I wanted to use that functionality in this PR.

Setup
Currently, there is not a way to execute this from the app, but running make server_test will exercise the repricing service.
Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Messages

:book:
:link: MB-8898

  Generated by :no_entry_sign: dangerJS against d0a1e9f804f6c1c63388ddbcfe05186352c67d53

This is good for the payment request re-price. What will be calling this service? I was kind of thinking the MTO Shipment ID would be passed down which would be 1 layer above this. The reason being is that the weight is tied to the shipment and then the payment requests would be pulled and then this service is called. This might already be in the backlog as the next piece. Just want to make sure it is somewhere.

I think what you're describing is captured in MB-9339.  That might end up being in its own service, but either way I expect that the service in this PR will be used as a building block for it.  I was hoping to keep this PR as a generic way to rebuild a payment request with current inputs, regardless of what triggers it now or in the future.

I think what you're describing is captured in MB-9339. That might end up being in its own service, but either way I expect that the service in this PR will be used as a building block for it. I was hoping to keep this PR as a generic way to rebuild a payment request with current inputs, regardless of what triggers it now or in the future.

I agree with the scope of this PR.

@jacquelineIO I just pushed up updates to address some of your comments.  I also introduced a DEPRECATED status for payment requests and renamed files, methods, functions, etc. to use "recalculate" instead of "reprice".


Enhancement: Filtering

Hi, would like to make a suggested enhancement and not sure if this is the best place. I like using this UI however we have a lot of noise on the log files and team finds using rqt_console to be cumbersome to use when we need to filter (select/deselect) topics, etc.
Is there a way to have a multi-selection listbox (listing the topics vertically) instead of the horizontal checkbox list to select the nodes? Also could you also have the option to include specific topics/messages using dropdown list?
Thank you for your help!

Improving the plugin and adding additional features is always possible. Please consider to provide a pull request to add features which are useful for your use case. In case of more complex changes it might be good to describe the proposed changes in detail beforehand (e.g. with a sketch of the desired UI or similar). That approach will make sure that the result is generally applicable and can be merged easily.


Migrate to System.Text.Json

Tweek api currently use newtonsoft.
System.Text.Json could provide a better implementation and terms of performance and scaling.
Additionally, it's a good opportunity to remove the JsonValue adapter in favor of a standard one.

Resolved in #1315
Couchbase/jpad still uses newtonsoft, mvc now uses system.text.json


Add path argument for .json layout file

Hi Cem,
I have created a small patch to make it possible that the path to the layout file for a keyboard's keymap can be specified in the arguments to the draw-zmk.yaml workflow.
Unfortunately my linter automatically reformatted all double quotes... I am sorry about that, just saw that. Also I was unsure, whether you wanted perhaps a different implementation, like not a directory, but a full path to the .json file or so. Let me know, if I should change the PR.
Thanks a lot for the drawer - I hate it, when I have to manually generate artwork, whenever a technical document changes...
BTW: the repo where it is used is here: https://github.com/michaelrommel/zmk-config

├── README.md
├── build.yaml
├── config
│   ├── boards
│   │   └── arm
│   │       └── nightliner
│   │           ├── Kconfig
│   │           ├── Kconfig.board
│   │           ├── Kconfig.defconfig
│   │           ├── board.cmake
│   │           ├── nightliner-pinctrl.dtsi
│   │           ├── nightliner.dtsi
│   │           ├── nightliner.keymap
│   │           ├── nightliner.yaml
│   │           ├── nightliner.zmk.yml
│   │           ├── nightliner_left.dts
│   │           ├── nightliner_left_defconfig
│   │           ├── nightliner_right.dts
│   │           └── nightliner_right_defconfig
│   └── west.yml
├── images
│   ├── keymap_drawer.config.yaml
│   ├── nightliner.json
│   ├── nightliner.png
│   ├── nightliner.svg
│   ├── nightliner.yaml
│   ├── nightliner_keypositions.png
│   └── nightliner_prev.yaml
├── scripts
│   └── create_svg.sh
├── tags
└── zephyr
    └── module.yml

I understand and agree, have applied the changes, this could be finalized now, I did two checks with an invalid and a missing path, both fell back to trying to draw without the json layout spec.
On more question, though: In testing I now understood, that a subsequent job in the workflow, even if it "needs" the draw step, cannot access the new .svg file, because there is a delay between the amending commit and the file actually being available for the next checkout. I am new to GH workflows, so please forgive any newbie knowledge gap... In researching how to resolve this, I understood, that only using "artifacts" may help in this case to make a non-textual output of a workflow available to other jobs.
My question: does it make sense to you to add functionality to decide whether the svg file shall be uploaded in addition to the commit or as alternative to a commit to an artifact? I would either do a separate PR if you are interested. I need it, because my subsequent step is to render the svg to a png via an inkscape cli call.
Thanks again,
Michael.

Hm, I seem to have mistakenly closed the PR. Can you still merge? Sorry about this...

Hi Cem,
it's me again. I think I have now figured all out. What I wanted to achieve is to create an svg and a converted png in one workflow. So I changed your workflow again to make it further configurable and decide whether to directly commit the .yaml and .svg files or to upload them to an artifact.
In my calling workflow, I now call this reusable workflow, then check out my zmk-config repo, download the artifacts, do the conversion to png and then commit all three files per keyboard back to the repo.
I have not created a new PR, since I was unsure, if you wanted to include all this in your template. Maybe it's overkill for most people... Anyway the new wf lives here: https://github.com/michaelrommel/keymap-drawer/blob/artifactupload/.github/workflows/draw-zmk.yml in a new branch.
And I use it like this here: https://github.com/michaelrommel/zmk-config/actions/runs/7906653515
It would be nice, if you let me know, if you are interested or if I should repackage it into my own repo of GH reusable workflows.
Thanks and have a nice day!
Michael.

Thank you for testing and confirming, and apologies for the last description tweak I made that I hadn't caught before.
I think adding an upload artifact option is a good idea, and I like how you implemented it with the destination argument. So I'd definitely appreciate a PR! It would also help solve #58 I believe.


Create Create a build of wiremock tailored for android

References

TODO

Submitter checklist

[ ] Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
[ ] Recommended: If you participate in Hacktoberfest 2023, make sure you're signed up there and in the WireMock form
[ ] The PR request is well described and justified, including the body and the references
[ ] The PR title represents the desired changelog entry
[ ] The repository's code style is followed (see the contributing guide)
[ ] Test coverage that demonstrates that the change works as expected
[ ] For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

Closing since no response. Feel free to reopen with valid content

I think I may have been a bit premature in suggesting this task. I think it'll be much easier to create an Android build when we've:

Merged the swappable HTTP client change.
Removed Guava completely.


TV Matter Media: Updated existing cluster to sync it with latest spec change

Problem
The message cluster has been updated under PR https://github.com/CHIP-Specifications/connectedhomeip-spec/pull/8812
Change overview

Update Message cluster XML to match the spec.

Tests

Build the TV app using command:
scripts/examples/gn_build_example.sh examples/tv-app/linux out/debug/

Built the CHIP tool test client using command:
scripts/examples/gn_build_example.sh examples/chip-tool out/debug/ chip_config_network_layer_ble=false

Run tests using command:
./scripts/run_in_build_env.sh \                "./scripts/tests/run_test_suite.py \                   --runner chip_tool_python \                   --chip-tool ./out/debug/chip-tool \                   run \                   --iterations 1 \                   --test-timeout-seconds 120 \                   --tv-app ./out/debug/chip-tv-app \                "

@lazarkov - why is skip-protocol-compatibility apropriate here given that the cluster is not provisional?

@lazarkov - why is skip-protocol-compatibility apropriate here given that the cluster is not provisional?
Please add details in the summary (I assume this is a close followup on a previous change, so no released versions with the old structures should exist)

Added info in the description


investigate cancellation

See here.
If xhr.abort() is expected to throw an exception merely because the request cannot be terminated, then instead of invoking the error callback, the success callback should be invoked with boolean false to indicate the attempt to cancel was unsuccessful.
Cancelation should be used purely to conserve resources; a user would not expect a cancellation request to fail by throwing an exception. The only reason I can think of for throwing an exception during cancellation is if the cancellation attempt itself is indicative of programmer error (e.g. cancellation was already attempted before).

Yeah, you're right. I think I put that in before you explained the intended cancellation semantics in another issue.


e2e: update upgrade tag in upgrade workflow + fix v7.1 upgrade test

Description

closes: #3261
Commit Message / Changelog Entry
type: commit message

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[x] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

This test run should now pass.


Add vertices to model_ds

The plotting functions of nlmod require vertices. It would be nice if those were added to model_ds during grid discretisations (via get_vertices)

Wouldn't it be better to depend on the plotting functions of flopy? Thus via #40 provide a nice way to get back from model_ds to the flopy environment. In that case, this issue can be closed.

I think a lot of flopy's plotting utilities also accept a modelgrid object? So another method would be to build the modelgrid from model_ds, and pass that onto the plotting methods.
I think nlmod.modelgrid.mgrid.modelgrid_from_model_ds() can do this? And this object should have methods to obtain the vertices.

@dbrakenhoff That function requires gridprops to be defined. Is there already a function that generates the gridprops from model_ds?

Hmm, not sure if flopy has a method to convert to go from a modelgrid object to a gridprops dictionary... Shouldn't be too complicated, but it might make more sense to convert that method to use a modelgrid object instead of the much less commonly used gridprops dictionary?

Hmm, not sure if flopy has a method to convert to go from a modelgrid object to a gridprops dictionary... Shouldn't be too complicated, but it might make more sense to convert that method to use a modelgrid object instead of the much less commonly used gridprops dictionary?

I agree, I think the modelgrid-object is a more commonly used object, that can be used to construct a disv-package or to plot model properties.
Is there a way to to save a modelgrid object to a grb-file in Flopy? It seems only MODFLOW is able to do this.

I am working on adding information from a modelgrid to a model_ds and getting a modelgrid-object from a model_ds (without needing gridprops), will add it when I am finished.

fixed by #53


[PDI-18665] NPE when editing job or transformation job entries at job…

… level

:white_check_mark: Build finished in 3m 44s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
plugins/engine-configuration/impl

:ok_hand: All tests passed!
Tests run: 64, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


is_reference returns False if value is binary type

Adds a check for binary types in is_reference.
Fixes #541
TODO: Add a test

Ok, I see. The issue was just the test:
parsed.scheme != ''

So, we are still relying on urlparse ... but the check must be py2/py3 safe.

I think we can test the is_reference in:
https://github.com/geopython/OWSLib/blob/master/tests/test_wps.py
... with examples we expect (py2, py3).


oversteer: 0.7.2 -> 0.8.0

Description of changes
Updated Oversteer to 0.8.0
https://github.com/berarma/oversteer/releases/tag/0.8.0

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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

[x] Fits CONTRIBUTING.md.

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

1 package built:

oversteer


DOC: Add ITK scientific ecosystem section to documentation

Add ITK scientific ecosystem section to documentation:

Include other tools developed around ITK that allow to leverage its use beyond its natural boundaries.
Transition the wiki command line tools page: https://itk.org/Wiki/ITK/CommandLineTools
Mention ITKApps as a set of legacy tools that leveraged ITK's capabilities without completely transitioning the corresponding https://itk.org/Wiki/ITK/Insight_Applications wiki page, as the instructions refer to old releases and tools.

PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)

Notes:

Feel free to propose changes to the name, contents, etc.
Re https://itk-viewer.on.fleek.co/: Not sure about the status of this. Points to IPFS data, not a viewer.
Re https://itk.org/Wiki/ITK/Insight_Applications: Don't think transferring this is useful: the application repository is archived, and maybe some effort would be necessary to make things work on modern systems. The Wiki page mentions ITK versions as old as 1.6, Qt 2.0, and VTK 4.2

Slightly related:

I do not think the links/contents in https://itk.org/Wiki/ITK/Developer_Software are relevant any more:

Pretty debugging: https://itk.org/Wiki/ITK/GDBPretty : not sure how this was/can be useful.
Debug Visualizers for Visual Studio: https://itk.org/Wiki/ITK/Debug_Visualizers_for_Visual_Studio : refers to VS 2018, 2010, 2012: deprecated.

But CMake: points to https://gitlab.kitware.com/cmake/community/-/wikis/Home could be linked from somewhere else as it looks maintained/relevant


Ignore or define folders

This is may just be a question, not an issue. (Couldn't find a twitter handle)
Is there a way to configure certain folders to ignore .css files in?
Several of my projects have a template folder within the root that is just for reference. Any actual files being used are moved into a proper public folder. I suppose defining one or multiple folders could be an option as well. This may help speed up the drag on VSCode the extension has when building the cache.

I'm having this issue as well.  I've not found a way to prevent it from scanning my node_modules and vendor directories.

Same here... implement a method to ignore certain folder would be really appreciated.

I would like this feature for another reason. My "Problems" view is cluttered with css issues from the "node_modules" folder and I would like to exclude it from the linting.

I've just discoverd it also covers all my node_modules which is totally unnecessary for my project. Any way I could help @zignd ?

@zignd I'll look if I have time, any pointers on first contributing to a vscode extension? :)

@nealoke Let me see:

Clone the repo
Install Yarn
yarn install for the dependencies
code . in the repository directory
Make your changes
F5 to run the extension in Debug mode
New window opens up with an isolated VS Code instance running and the extension will be already installed in it
You can set break points in the VS Code containing the extension code (not the one running the extension installed)

In case you have any other doubts feel free to contact me, there's some contact info in my profile bio.

@nealoke I forgot to mention, documentation related to how VS Code extensions work can be found here: Extensibility Reference. And here is the documentation for the classes, methods, functions and everything code-related: vscode namespace API. Very useful resources.

+1 for this "issue"
Now it's cache all CSS in node_modules which isn't a good idea :)

The recently released version adds a feature that is supposed to solve this issue.


Bump OpenTelemetry from 1.26.0 to 1.30.0

Description
Bump OpenTelemetry 1.30.0
Related Issues
N/A

Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@reta Can you please rebase?


Support Node.js 4.*

The builds for Node.js 4.* are passing, the problem need to be analysed and fixed.

https://travis-ci.org/pjanuario/zmq-service-suite-service-js/builds/95358289


Undo/redo for 2D model

2D model integrated with QReal undo stack, implemented undo commands set for 2D model.
This also fixes some bugs that can be met in stable version.

[Current coverage][cc-pull] is 27.09%

No coverage report found for master at d406ad6.

Powered by Codecov. Last updated by [d406ad6...fa652c5][cc-compare]
[cc-base-branch]: https://codecov.io/gh/qreal/qreal/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/qreal/qreal/compare/d406ad6b478c9b42cc43c0ee8a2200c1fcc9e17a...fa652c51ed4084b88b237c0e593ed2359af0243d?src=pr
[cc-pull]: https://codecov.io/gh/qreal/qreal/pull/1650?src=pr


loop check partition number coroutine will exit stop to consume message without return the problem to the main routine

Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.

Sarama
Kafka
Go

v1.26.1
0.11
0.14.1

Configuration
What configuration values are you using for Sarama and Kafka?
	config.Consumer.Group.Rebalance.Strategy = sarama.BalanceStrategyRange
	config.Consumer.Return.Errors = true
	config.Consumer.Group.Session.Timeout = 30 * time.Second
	config.Consumer.Offsets.Initial = sarama.OffsetNewest
	config.Consumer.Group.Rebalance.Timeout = 120 * time.Second

Logs
When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set sarama.Logger to a log.Logger to capture Sarama debug
output.
logs: CLICK ME

[sarama] 2020/04/30 10:15:44 loop check partition number coroutine will exit, topics [my-topic-name]
[sarama] 2020/04/30 10:15:44 consumer/broker/2 closed dead subscription to my-topic-name/2
[sarama] 2020/04/30 10:15:44 consumer/broker/2 closed dead subscription to my-topic-name/8
[sarama] 2020/04/30 10:15:44 consumer/broker/2 closed dead subscription to my-topic-name/5
[sarama] 2020/04/30 10:15:44 consumer/broker/2 closed dead subscription to my-topic-name/11
[sarama] 2020/04/30 10:15:44 consumer/broker/1 closed dead subscription to my-topic-name/1
[sarama] 2020/04/30 10:15:44 consumer/broker/1 closed dead subscription to my-topic-name/10
[sarama] 2020/04/30 10:15:44 consumer/broker/1 closed dead subscription to my-topic-name/4
[sarama] 2020/04/30 10:15:44 consumer/broker/1 closed dead subscription to my-topic-name/7
[sarama] 2020/04/30 10:15:44 consumer/broker/0 closed dead subscription to my-topic-name/0
[sarama] 2020/04/30 10:15:44 consumer/broker/0 closed dead subscription to my-topic-name/6
[sarama] 2020/04/30 10:15:44 consumer/broker/0 closed dead subscription to my-topic-name/3
[sarama] 2020/04/30 10:15:44 consumer/broker/0 closed dead subscription to my-topic-name/9

Problem Description
Hello, we update the library to v1.26.1 and we notice that when the log loop check partition number coroutine will exit is printed the library stop consuming messaging and stop retry to reconnect to Kafka but no error are reported to the channel. This behavior block us to adopt countermeasures and the microservices can't restore connection to kafka (after manual reboot the system return working for a while but then we see this logs again). We are setting something wrong or this is an intended behaviour? If it's so how can the main routine catch the error and fix it?

I have the same problem, exactly the same.

I Have the same issue consuming from kafka in Amazon MSK.

friends, how the consumer code looks like?
are you doing this:
https://github.com/Shopify/sarama/blob/master/consumer_group.go#L41-L44
https://github.com/Shopify/sarama/blob/master/examples/consumergroup/main.go#L101-L113
tl;dr it might not be an issue at all, it might be just  Consume needed to be called agains as something have changed on the server/client and a rebalance was triggered

Hello @d1egoaz I think you just caught the problem. So your suggestion is to change and not call the function consume once but each time we consume something? If we want to optimise the call to your library how can we know when we have to do this reboot?

@bestbug456
could you please expand on this a little bit (some code maybe?), as I didn't get it

and not call the function consume once but each time we consume something

I'm going to try to explain a little bit better
This function call will block until something like the following happens:

an error has occurred: and the err variable would have the error, you can choose to continue or close the process, most of the time if there is an error, you should log it and exit, or might want to recreate entirely the client.
it will stop consuming, and no error is returned, most of the time it's because a rebalance was triggered, so you'll need to call Consume again, as all the dance for Setup, ConsumeClaim needs to be re-done, as this member might have different (more or less or different) replicas (claims) to consume, usually when a new member joins the consumer group, all the current members will need to rebalance, so that's why is important to use an infinite for loop here


Changes to build pipeline

This PR significantly simplifies the build pipeline. Most importantly, it completely removes the need for a Gulp.js asset pipeline in the theme and all the setup and rigamarole that that involves. It also updates the instructions accordingly and removes all unnecessary files.

This. Is. AWESOME! Thanks Luc – you clearly know much more about Hugo than I do. :smile:

@clouderati No problem! Happy to help. And yes, I have spent quite some time in the trenches with Hugo 💯😄
It also helps that I built the underlying theme 🙃

Heh, no way. 😆  You better bet I'm going to be learning a lot from you, then!


docs: Add Distributed Machine Learning Patterns book

My book Distributed Machine Learning Patterns from Manning Publication uses Argo Workflows and would be a good resource for people who use it for ML use cases.

@juliev0 I don't want to change it just for this one addition since this seems to be a common heading across other Argo subprojects and they may be linked by other projects/resources already.

@juliev0 I don't want to change it just for this one addition since this seems to be a common heading across other Argo subprojects and they may be linked by other projects/resources already.

Okay. If there is a link to it, I wouldn't want to mess that up. Well, let's give it a few days in case anyone else objects. After that I'll let it go. :) (the other option would be to have another heading for this)


PrivateLink multi-region updates

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c052b171e54f0a6b2d14ae13d566ce1b787e4a3d/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/network-authorization.md

Closes https://cockroachlabs.atlassian.net/browse/CC-3673

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/85ab3067f9f0d1935bc16b28f0844c8f176948b7/
Edited pages:

cockroachcloud/connect-to-your-cluster.md
cockroachcloud/network-authorization.md


Set DHW temperature in ha Automation

Hi, i have been attempting to create an automation to set the domestic hot water target temperature. Unfortunately,  I cannot manage to set it or even put the value into a separate sensor. I would be more than happy for any and all assistance.

How does your automation look like? If you want to set temperature you should call service. Here you can find instructions on how to setup your automation.

Thanks, it helped!! The connection to a target entity was what was missing.


Build failure: linuxKernel.packages.linux_6_8.vhba

Steps To Reproduce
Steps to reproduce the behavior:

Run nix-build -E '(import <nixpkgs> { }).linuxKernel.packages.linux_6_8.vhba'

Build log
https://gist.github.com/Jayman2000/5c2cf9b79db33b105fd42ece5738e0e5
Additional context
This bug is making my NixOS config fail to build. Linux 6.8 is the latest version of Linux at the moment, and my NixOS config does this:
{ pkgs, ... }:

{
  boot.kernelPackages = pkgs.linuxPackages_latest;
}

I was able to work around this bug by doing this:
{ pkgs, ... }:

{
  boot.kernelPackages = pkgs.linuxKernel.packages.linux_6_7;
}

Notify maintainers

@bendlas
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.7.9, NixOS, 23.11 (Tapir), 23.11.5286.ddcd7598b218`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-23.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

$

Add a :+1: reaction to issues you find important.

Module version can be updated. That will probably resolve it.
https://cdemu.sourceforge.io/project/#binary

Having this issue as well. I'm on the latest kernel on 23.11 (6.8.1). The VHBA module fails to build. The module update has landed in unstable but hasn't been backported to 23.11 yet. Since I need CDEmu for now, I'm forced to stick to 6.7 at the moment.
Not the end of the world, but slightly annoying that some kernel modules on stable are broken right now.

This was fixed by #285972 and #305046.


error-handling with fetchAs

Client.fetchAs doesn't give you access to the status code of the response, so one could reasonably assume that it only returns a successful Task in the success case. However, it completely ignores the status code. So if you do something like fetchAs[String] and the server responds with a 500, you get a successful Task wrapping an empty string (or whatever the body was). With this approach there's not a good way to distinguish that result from the 200 response body that you were expecting.
There was some discussion about this on Gitter.

+1 on this. fetchAs should only return the value if the response was a success with entity (namely 200 OK). Even other success responses (like, for example, 204 No Content) should not return a successful Task since they do not have the requested entity.

+1 to the general concept.
I'm not sure I see the harm in returning a 204's entity if it has one.  I consume an API that intentionally violates the spec like that. :disappointed:  I strongly believe that we should keep making it difficult to produce a 204 with an entity.
More questions:

What does fetchAs return on a non-2xx?  A failed task with some sort of UnsuccessfulResponse(response)?
Is it okay that fetchAs assumes success while fetch handles all responses?  I like the semantics of fetch, and the proposed semantics of fetchAs.  How confusing is it to have these two with similar names?
A lot of people are lifting things into EitherT.  Maybe some sort of attemptFetchAs.  I see three classes of things that can go wrong:

Network failure.  I'm happy making this a failed task.
Decode errors.  This is a good candidatefor EitherT's left.
Unsuccessful response.  This is also a good candidate for EitherT's left.  But if we're already handling decode errors, we've just widened the type of the left.  Is that okay?

A 204 with an entity is not possibly in HTTP, so I don't see why it should be supported.
I think it's OK for fetch to handle all cases while fetchAs expects a success with an entity
I like attemptFetchAs

We have an API that returns 204 when there is no content and 200 when there is something. In this case for us 204 is not an error, it's a successful result, just without a result. Thus we would need to differentiate between entity, no entity, error. The way we do it is when using fetchAs[String] we return empty string for 204 and for fetchAs[Json] we return jNull.

I'd be fine with any 2xx returning a a successful Task. There's potentially an argument for not even bothering with trying to read the body if the response is 204, but I don't have particularly strong feelings about this.
I'm wondering if network failures and decoding errors are both errors that you are less likely to try to recover from while a 404 is something that you might turn into a None, a 401 might trigger some authentication logic, etc. So I'm wondering if network failures and decode errors are best handled by a failed Task and non-success status codes should be the use-case for something like EitherT.
I've also thought about whether it might make sense to create a ResponseDecoder similar to EntityDecoder (and some may require implicit EntityDecoders) but that also gets to look at the status code of the response. Then I could see people creating their own custom ResponseDecoders that handle 404s, 401s, etc and return disjunctions etc depending on how they want to handle errors. I'll ponder this a bit more over the next couple of days as I set up some error-handling in some of my code.

Proposed strategy after gitter conversation:

Leave fetch alone.
Deprecate fetchAs, because it has surprising semantics.
Add expect[A]: Task[A], which returns a failed task wrapping the static code if status is not successful.
Add attemptFetchAs[A, B](onFailure: Response => Task[B]): Task[B \/ A] to do principled error handling with all the power of the former fetchAs.

#629 does not include attemptFetchAs.  Do people want this?


Refactor chain endpoint structure

Description

Currently, chain-specific endpoints are in folders in the main directory, ie. /evm/ and /near
These endpoints are duplicative and will be difficult to maintain in the future
Refactor the endpoints so that there is only a single /chain/ set of endpoints
Each endpoint request should include a chain parameter
Raise NotImplemented for chains that don't implement that particular endpoint
Modify unit tests

Bounty

Sponsor: Hummingbot Foundation
Bounty amount: 50,000 HBOT (P2)
Developer portion: 100%
Status: OPEN

This issue was assigned to @vic-en. Thank you for your contribution!

Thanks for your participation, the bounty has been sent to @vic-en . The fix has been deployed on development branch and  hummingbot version 1.16.0

reopening as it was paid prematurely and @vic-en is still working on this PR

@fengtality
PRS are https://github.com/hummingbot/hummingbot/pull/6445 and https://github.com/hummingbot/gateway/pull/147 on the HB Client and Gateway respectively.


npm Omit dev dependencies by default

See forums post: https://forums.inedo.com/topic/3934/pgscan-different-results-for-npm-dependencies
By default dev dependencies should be omitted, can include them by using the argument --include-dev

Used wrong ticket in commit 7fa7aabaed148bd289a8256a373af6050083b292
Should use 42 not 41


Update changelog [ci skip]

added missing entries using commit hashes instead of tags.

Codecov Report

Merging #765 (5db0de4) into development (196dec7) will decrease coverage by 0.80%.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff               @@
##           development     #765      +/-   ##
===============================================
- Coverage        89.44%   88.64%   -0.81%
===============================================
  Files              221       92     -129
  Lines            13251     6629    -6622
===============================================
- Hits             11852     5876    -5976
+ Misses            1399      753     -646

Impacted Files
Coverage Δ

framework/src/bundle/BundleRegistry.cpp
79.80% <0.00%> (-12.32%)
:arrow_down:

...mework/src/service/ServiceReferenceBasePrivate.cpp
86.45% <0.00%> (-4.98%)
:arrow_down:

framework/src/service/ServiceEvent.cpp
73.80% <0.00%> (-4.63%)
:arrow_down:

framework/src/util/FrameworkEvent.cpp
63.79% <0.00%> (-3.78%)
:arrow_down:

framework/src/service/ServiceListeners.cpp
96.26% <0.00%> (-3.12%)
:arrow_down:

framework/src/bundle/BundleResourceBuffer.cpp
67.67% <0.00%> (-3.06%)
:arrow_down:

framework/src/bundle/BundleContext.cpp
87.50% <0.00%> (-2.90%)
:arrow_down:

framework/src/bundle/BundleEvent.cpp
85.71% <0.00%> (-2.75%)
:arrow_down:

framework/src/util/Properties.cpp
55.55% <0.00%> (-2.45%)
:arrow_down:

framework/src/util/Utils.cpp
75.58% <0.00%> (-1.87%)
:arrow_down:

... and 192 more


making shopping cart icon clickable

Thank you for your contribution to the vue-unicons repo.
Before submitting this PR, please make sure:

[X] Your code builds clean without any errors or warnings
[X] Your commits follow the сonvention

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[X] Feature
[ ] Refactor

Importantly
To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on PR.

Hi @rlightner

To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on PR.
The commit name - "making shopping cart icon clickable" does not comply with the convention
Not clickable cart was made specifically


Logical Replication transactions applied multiple times

Steps to reproduce
Make Neon a subscriber to some workload that produces several inserts/sec on a table with a primary key. Then restart it. Replication will fail because of duplicate key insert.
Expected result
No duplicate key insert
Actual result
Duplicate key insert
Environment
Logs, links
Discussion: https://neondb.slack.com/archives/C04DGM6SMTM/p1708363190710839
It seems that pageserver isn't applying advancing replorigin, and so the compute's origin when it restarts is whatever was in the last checkpoint.

To achieve exactly once semantics for incoming logical replication postgres stamps each commit record with a 10-byte tuple of (origin_id, origin_lsn), where origin_id is two byte unique identifier of the replication source and origin_lsn is 8-byte lsn on the source side. Postgres maintains in-memory mapping of origin_id => origin_lsn and writes it to disk on each checkpoint including a shutdown checkpoint. On a normal start postgres would just read this disk state. During start after a crash postgres will load last on-disk state and on WAL replay it will update in-memory values on each commit record to end up in a consistent state.
That way postgres always has knowledge of remote lsn of last applied record and in case of replication reconnect it can ask to continue replication from a proper point. For context: postgres replication is somewhat pull model -- it is on replica to reconnect and ask for data starting with some lsn.
How can we support it in Neon:

There are already wal records for creating and dropping replication origins (xl_replorigin_set / xl_replorigin_drop). No need to generate aux file logical messages for repl. origins.
We store all repl. origins in one more directory-like structure. Could be sorted array of [[origin_id, lsn],...] (denser) or hashmap as before.
Commit records serve as update records for repl. origins. We maintain in-memory commit counter and each 1k commits we write out new state of repl. origins in case there were some changes.
On basebackup:

read disk state of repl. origins
find last 1k of commit records (IIUC they are now attached as updates to CLOG and we somewhat simulate range scan?) and replay them to get latest origin_lsn values
include up to date files in basebackup archive

To achieve exactly once semantics for incoming logical replication postgres stamps each commit record with a 10-byte tuple of (origin_id, origin_lsn), where origin_id is two byte unique identifier of the replication source and origin_lsn is 8-byte lsn on the source side.

Formally speaking it is not precisely true.
origin_id is not specified I commit record.
It is special kind of block_id (XLR_BLOCK_ID_DATA_SHORT, XLR_BLOCK_ID_DATA_LONG,... XLR_BLOCK_ID_DATA_SHORT).
Commit record may include origin_lsn&origin_timestamp (16 bytes totally) if XACT_XINFO_HAS_HAS_ORIGIN  but is set in xinfo. But it is not principle.

There are already wal records for creating and dropping replication origins (xl_replorigin_set / xl_replorigin_drop). No need to generate aux file logical messages for repl. origins.

Well, presence of WAL record doesn't exclude necessity to have key with which this WAL record will be associated. Please notice that our storage is key-value storage. For example now commit records are associated with CLOG pages.
AUX_FILE is such key with which xl_replorigin_set / xl_replorigin_drop can be associated (right now them are not stored as WAL records but just as single-file entry, but in principle it is the same).

We store all repl. origins in one more directory-like structure. Could be sorted array of [[origin_id, lsn],...] (denser) or hashmap as before.

No problem with it. I have already implemented this part.

Commit records serve as update records for repl. origins. We maintain in-memory commit counter and each 1k commits we write out new state of repl. origins in case there were some changes.

Do you mean that we should add REPL_ORIGIN key and associate commit records with it? It means that we need to write commit in two places: CLOG and repl. origin.

On basebackup:
read disk state of repl. origins
find last 1k of commit records (IIUC they are now attached as updates to CLOG and we somewhat simulate range scan?) > and replay them to get latest origin_lsn values
include up to date files in basebackup archiveConcerning your proposal (1-4).

There is no any efficient way to locate N last commits.
Right now original commit records are not stored in KV storage at all. Walingest stores its own CLOG update records.
But I do not understand what do we need to load N last commits at all.  If we introduce REPL_ORIGIN(id) key, then we can associate repl origin updates with this page. And we need to load just one value (preceding basebackup LSN).
The question is how to find all origins. In Postgres each slot has its own origin and we just iterate through all slots. PS knows nothing about replication slots. But it has AUX file with slot state. In principle it can get this files, parse it and so get array of origins. Alternatively we can use range scan to find all available  REPL_ORIGIN(id) keys. Last approach seems to be less efficient but easier to implement and doesn't require PS to know format of replication slot state file.
xl_replorigin_set
xl_replorigin_set is use to checkpoint origin.

This was fixed by https://github.com/neondatabase/neon/pull/7099


BYON call handling (VVOIP) PUT lacks 200 OK JSON response body

@pradeepachar-mavenir  @TEF-RicardoSerr
Problem description
The PUT method for BYON call handling does not return a JSON response body for successful requests (200 OK).
Expected behavior
The PUT method for BYON call handling needs to be updated to return a JSON response body for successful requests (200 OK). This response body should include relevant information about the updated call handling configuration.

Fully agree, PUT should return the body modified. Not empty body.
But I will go further, if we are talking about to modify a specific parameter of the session, won't be better to use PATCH? Using PUT we should include all session information, not just the parameters to change. This will allow to expand the API on the future, but just a suggestion.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/PATCH

A PATCH request is considered a set of instructions on how to modify a resource. Contrast this with PUT; which is a complete representation of a resource.

This was fixed within last version of the API 0.1.2


Some top-level EC2 functions are in the aws namespace (TypeScript)

Some functions built from data sources in Terraform's EC2 package have been put in pulumi-aws' top-level namespace.
I'm not au fait with all the Terraform modules and data sources, but I see at least three: Terraform's aws_ami, aws_ami_ids and aws_eip have become Pulumi's aws.getAmi, aws.getAmiIds and aws.getElasticIp. I expect to see these functions in the ec2 namespace: aws.ec2.getAmi, aws.ec2.getAmiIds and aws.ec2.getElasticIp.
There are only 9 top-level data sources in the Terraform AWS module, but currently 15 functions show up in VSCode when I view the IntelliSense pop-up after typing aws.get. So there may be  a few more errant functions to track down..

I think that we could duplicate the function definitions into the ec2 namespace (removing them from the top-level namespace would be a breaking change that we don't want to take). I'm not entirely sure that we have support for that in pulumi-terraform-bridge.


I read your book, curious how you test if the grammar work first. ARiGaDo!

parse.y is so much too read...

First I wrote a syntax checker to test syntax for the new language. parse.y with very basic syntax description (no actions), with simple lexer works well as a syntax checker. Check out f0df31008693df5496c69c43ed587a1bed71938d to see the syntax checker for Streem.

and what does lex.l do? XD

Lex.l is a source for the lexical analyzer. The tool named lex (or flex the GNU version) generates the C implementation of the lexical analyzer.


deprecated instruction

I am reporting for yuor information a log of platformIO
StepperISR_esp32_rmt.cpp 2
if (!q->_isRunning) {
// second invocation to stop.
rmt_tx_stop(q->channel);
rmt_rx_stop(q->channel);
rmt_memory_rw_rst(q->channel);
q->_rmtStopped = true;
}
[{
"resource": "/c:/Users/gsrad/Documents/Lavori_con_Platform/ESP32 Nema23 Test/lib/FastAccelStepper/src/StepperISR_esp32_rmt.cpp",
"owner": "cpp",
"severity": 4,
"message": "'esp_err_t rmt_memory_rw_rst(rmt_channel_t)' is deprecated: use rmt_tx_memory_reset or rmt_rx_memory_reset instead [-Wdeprecated-declarations]",
"startLineNumber": 283,
"startColumn": 28,
"endLineNumber": 283,
"endColumn": 28
}]

there are a number of deprecations in PCNT in esp-idf 5.0 as well (which arduino-esp is using under the hood), and are removed entirely in 5.1, such as PCNT_SIG_CH0_IN4_IDX. Eventually it'll crop up as a problem when arduino-esp moves to esp-idf 5.1.

Reproduced in automatic builds. Need to be fixed

The warning has been fixed in pre-0.3.12.
For esp32 just have commented the instruction out - seems to work. For esp32 derivates replaced with rmt_tx_memory_reset().


XOR Cipher in Python

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
This in an implementation of XOR cipher in Python 3.8.
It can encrypt message with a given key and decrypt the message with top 5 possible plaintext.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
https://github.com/TesseractCoding/NeoAlgo/issues/1374#issue-727903659

@thuy-ttn Format your code according to PEP 8 rules. You can refer to this http://pep8online.com/.

Done :)))

@all-contributors please add @thuy-ttn for code


Upgrade moment and moment-timezone

@timabbott This is ready for a review.

@hackerkid you should probably have upgraded using yarn. Just updating package.json does not update the yarn.lock, which needs to be updated. Or is there a reason to not do so?

Oops, yeah, I missed that.  @cPhost can you take care of doing that update?

@cPhost @timabbott Opps. I was not aware of that. Created #8635.


Discussion on StatusBar.overlaysWebView

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
The statusbar overlays the webview by default on iOS. This means that if your app is designed so that different pages have different coloured headerbars, the statusbar text might not fit the background very well.
I'm wondering what the reasoning behind this is, and whether it should actually be disabled by default, to mirror how Android works.
Expected behavior:
Don't overlay the webview by default?
Alternatively, please document how to disable this behaviour (see below for steps required).
Steps to reproduce:
ionic start --v2 MyApp blank
ionic platform add ios
ionic emulate ios

Other information:
In order to stop the statusbar overlaying the webview you need to do two things:

In your app.component.ts, add some code to prevent the statusbar from being overlayed (I prefer doing this here rather than in config.xml, so that the desired effect occurs in Ionic View as well as the real app):

this.platform.ready().then(() => {
  StatusBar.overlaysWebView(false);
  StatusBar.styleDefault();
});

When bootstrapping your app, ensure statusbarPadding is set to false:

IonicModule.forRoot(AppComponent, {
  statusbarPadding: false
})

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Your system information:

Cordova CLI: 6.4.0
Ionic CLI Version: 2.1.18
Ionic App Lib Version: 2.1.9
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 4.8
Node Version: v6.9.4
Xcode version: Not installed

This is set by default because this is how native IOS behaves.
Referencing the ios design guidelines, the statusbar should overlay the view and integrate with an apps design, indicating either a dark style (dark text) or light style (light text).
If you'd like to change the default ios behavior, how you're setting it in your sample code would work fine.

Thanks for getting back to me, that makes sense.
Could I suggest the code samples are added somewhere in the docs? It took a lot of time to figure out that both of these changes were needed.


example token must not start with GITHUB_

We use that in our examples, yet GitHub doesn't allow to create such secrets anymore

Failed to add secret. Secret names must not start with GITHUB_.

GITHUB_TOKEN is available out of the box, and coverall's repo token is needed only for private repos


⚠ Bofrost.lu has degraded performance

In 7a0af8a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1208 ms

Resolved: Bofrost.lu performance has improved in 2ab6b7e after 15 minutes.


Fix crash due to label breaking precise captures

Precise closure capture breaks when a label exists with the same name as a variable or function.
Label parsing used to rely on ParseExpr(), checking after the fact to see if the expression was a single identifier and if it is followed by a tkColon. Since it parsed, however, a pidref was pushed for the identifier setting up a new reference to that identifier which could then trick the front-end into thinking there was a closure capture where there actually wasn't.  This leads to invalid StSlots and LdSlots.
Fix it by looking for a label before parsing as an expression statement. Labels are by spec exactly a tkID followed by a tkColon.  Chakra unfortunately allows parenthesized label names, so we also check for balanced open and close parentheses here to maintain that behavior.  We will remove this legacy behavior in a future release.
If we don't find a label pattern in the syntax then we rewind and parse as an expression statement.

@pleath @Microsoft/chakra-es please review

LGTM.

In reply to: 263724757 [](ancestors = 263724757)

LGTM


feat(core): add Manager::add_capability, closes #8799

The tricky part here was making the scope mutable. Had to use an Arc, but I'm not sure if there's a better way to do it.

Needs #8802


Getting error while using parse dashboard "Configure a user to access Parse Dashboard remotely" using it through http

For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

[x] You've met the prerequisites.

[x] You're running the latest version of Parse Server.

[x] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup
Steps to reproduce
Logs/Trace

You're missing a , before "users"

And in the future, be careful sharing in plain your applicationId and masterKey....

i have done it but now i getting the error


Urllib benchmark

This relates to...

Rationale

Changes

Features

Bug Fixes

Breaking Changes and Deprecations

Status

[ ] I have read and agreed to the Developer's Certificate of Origin
[ ] Tested
[ ] Benchmarked (optional)
[ ] Documented
[ ] Review ready
[ ] In review
[ ] Merge ready

https://github.com/node-modules/urllib/commit/8247aa298148047510e3bd61f376797d671dc5f9


Remove indent

Is there a way to remove indent from where the snippet is triggered from? If I'm on a new line but indented on that line and type the trigger text and expand I would like it to insert the snippet starting on column 0 of that line instead of where the original text was typed.
    trig|

--> actual behavior
    this is the snippet
      contains some indent

--> desired behavior
this is the snippet
  contains some indent

You could use regTrig to match everything in the line before the trigger
s({trig=".*trig", regTrig=true}, {t{"this is the snippet","\tcontains some indent"}})

This should work, but there is some bug that still gives the snippet indent. I'll look into it.

Seems to work with 07cf1a1

In the example you posted should the .* be selected as a placeholder? I type trig expand and get .*|trig -> tab -> .*trig| and need to expand again to get the text with the correct indentation.

Oh that sounds weird, here's how it works for me:
https://user-images.githubusercontent.com/41961280/169680593-9e503dd0-b0fb-4e8a-a7c7-6e4829b8abff.mp4

Looks like that behavior is actually caused by cmp. If I exit the cmp menu before expanding the trigger it works as expected. Seems related to the discussion here https://github.com/saadparwaiz1/cmp_luasnip/issues/6. It seems like this should be fixable by using the name field in the snippet definition. Is the intention of that field to show that name instead of the trig text?

Tested a bit and forcing cmp_luasnip to use the name field doesn't solve the problem since it expands using this helper either way.
Here is a minimal init.lua if it helps but I'm guessing this will need to be fixed on the cmp_luasnip side.

init.lua
vim.cmd([[set runtimepath=$VIMRUNTIME]])
vim.cmd([[set packpath=/tmp/nvim/site]])

local package_root = "/tmp/nvim/site/pack"
local install_path = package_root .. "/packer/start/packer.nvim"

local function load_plugins()
    require("packer").startup({
        function(use)
            use({ "wbthomason/packer.nvim" })
            use({ "L3MON4D3/LuaSnip" })
            use({ "saadparwaiz1/cmp_luasnip" })
            use({
                "hrsh7th/nvim-cmp",
                config = function()
                    local cmp = require("cmp")
                    local luasnip = require("luasnip")

                    cmp.setup({
                        snippet = {
                            expand = function(args)
                                require("luasnip").lsp_expand(args.body)
                            end,
                        },
                        mapping = {
                            ["<C-y>"] = cmp.mapping({
                                i = function(fallback)
                                    if cmp.visible() then
                                        cmp.confirm({
                                            behavior = cmp.ConfirmBehavior.Replace,
                                            select = false,
                                        })
                                    elseif luasnip.expandable() then
                                        luasnip.expand()
                                    else
                                        fallback()
                                    end
                                end,
                            }),
                            ["<C-e>"] = cmp.mapping({
                                i = cmp.mapping.abort(),
                            }),
                            ["<C-n>"] = cmp.mapping({
                                i = function()
                                    if luasnip.choice_active() then
                                        luasnip.change_choice(1)
                                    elseif cmp.visible() then
                                        cmp.select_next_item({
                                            behavior = cmp.SelectBehavior.Insert,
                                        })
                                    else
                                        cmp.complete()
                                    end
                                end,
                            }),
                            ["<C-p>"] = cmp.mapping({
                                i = function()
                                    if luasnip.choice_active() then
                                        luasnip.change_choice(-1)
                                    elseif cmp.visible() then
                                        cmp.select_prev_item({
                                            behavior = cmp.SelectBehavior.Insert,
                                        })
                                    else
                                        cmp.complete()
                                    end
                                end,
                            }),
                            ["<Tab>"] = cmp.mapping(function(fallback)
                                if luasnip.jumpable(1) then
                                    luasnip.jump(1)
                                else
                                    fallback()
                                end
                            end, { "i", "s" }),
                            ["<S-Tab>"] = cmp.mapping(function(fallback)
                                if luasnip.jumpable(-1) then
                                    luasnip.jump(-1)
                                else
                                    fallback()
                                end
                            end, { "i", "s" }),
                        },
                        sources = {
                            { name = "luasnip" },
                        },
                    })
                end,
            })
        end,
        config = {
            package_root = package_root,
            compile_path = install_path .. "/plugin/packer_compiled.lua",
        },
    })
end

if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system({
        "git",
        "clone",
        "https://github.com/wbthomason/packer.nvim",
        install_path,
    })
    load_plugins()
    require("packer").sync()
else
    load_plugins()
    require("packer").sync()
end

In the example you posted should the .* be selected as a placeholder? I type trig expand and get .*|trig -> tab -> .*trig| and need to expand again to get the text with the correct indentation.

Ahh of course, the expand_helper expands a snippet for the pattern (this has to be done because the snippet might rely on some capture, which would not be populated when expanding the snippet via cmp), so the groups can be filled-in correctly.

I'm guessing this will need to be fixed on the cmp_luasnip side.

Im not sure if there really is anything to fix, cmp_luasnip provides a list of snippets, and one of those is expanded at the cursor. Matching the line against the trigger and removing text does not sound like the right thing to do.
There's another way to get that snippet: use the indentSnippetNode, it can reset indentation of nodes inside it. This will, however not affect the line the snippet was expanded on, so that will need to be cleared, for example using the snippet-callbacks

Okay, example didn't really work, the problem is that parts of the snippet are removed, which is never a good idea.
Instead, I added the pre_expand-callback (on brach pre_expand_callback) (example in #438) that should work even when expanded with nvim-cmp.

Tested that branch and it seems to be working for the snippet I have. Thanks!

Nice, I think I'll mehr it tomorrow or so

Merged! (#438)


Rework approach to forms/templates

Our current approach is not consistent with the actual codebase (iseveral methods and parameters in the timeline.html is not used etc.)

Should be fixed by React front-end in Kanbamps.


 It also needed because the production
database connection will be available on the DATABASE_URL environment
variable as well as the Rails secret token.

LGTM :+1:

:+1:


Add aggregate chart link in the performance issue

Also add Mako aggregate chart in the issue for performance regression.

/lgtm
/approve


Add Google Structured Data for Questions

Hey there!
Right now, we have a questions panel on each OpenList license page, but it would be even better if we could have structured data so that search engines and bots can understand the licenses (this will help our SEO). We would be using this structured data in order to let bots understand the page. If you are interested in taking this issue, you pretty much just need to convert JSON to a string and use 'dangerouslySetInnerHTML' on a script to get the same behavior that a script tag (with JSON type) would have.
If you are interested in taking this issue, please let me know in the comments below.
Cheers,
William McGonagle

I would like to work on this issue

Sounds good- I'll assign you!


tests cert providers

@lulf I need your help to review what I'm missing here.
testOpenshiftCertProvider doesn't pass despite trusting the openshift ca cert.
In all the tests the validation of the admin console doesn't pass despite trusting the corresponding ca.

@enmasse-ci run tests testcase=**.CertProviderTest

@famartinrh I think the openshift cert provider does not reflect the real use case of this feature, which is for the client to run on OpenShift and trust the cert in /var/run/secrets/kubernetes.io/serviceaccount/ca.crt . I suggest rewriting this specific test case to run a client on the cluster that reads the cert from this file.

@lulf ok, no problem

@enmasse-ci run tests testcase=**.CertProviderTest

@enmasse-ci run tests testcase=**.CertProviderTest

@enmasse-ci run tests testcase=**.CertProviderTest

@enmasse-ci run tests testcase=**.CertProviderTest

@enmasse-ci run tests testcase=**.CertProviderTest

@lulf if you approve now we can merge

@famartinrh hold on, I need to review as well

@famartinrh please rebase this branch on current master which contains reusing api-model classes :) I think this branch needs to be refactored because we don't use systemtests classes AddressSpace, AddressSpaceEndpoint etc...

I'm on it @kornys

@enmasse-ci run tests testcase=**.CertProviderTest

@famartinrh please could you test it against remote cluster? just to be sure that ingress works fine etc... :)

@enmasse-ci run tests testcase=**.CertProviderTest#testOpenshiftCertProvider

@famartinrh please move deployment of cert verificator to separated namespace, otherwise LGTM

@enmasse-ci run tests testcase=**.CertProviderTest#testOpenshiftCertProvider


Remove blspy from eth2 extras

What was wrong?
We recently implicitly added a system dependency against cmake that effects anyone trying to install trinity.
How was it fixed?
Just trying to figure out the things that would break and if we can opt-in to install bls-bindings for these plalces.
To-Do

[ ] Clean up commit history

[ ] Add entry to the release notes

Cute Animal Picture

Thinking about letting Trinity try import blspy (Chia BLS) as the default backend, and fallback to py_ecc if blspy is not available.
But I'm not sure what would the CI environments look like. Do we have an environment with blspy and one without?

Thinking about letting Trinity try import blspy (Chia BLS) as the default backend, and fallback to py_ecc if blspy is not available.

That sounds reasonable. Alternatively we could also try import it and raise an error that blspy needs to be installed. Then tests that depend on it would also have to depend on the bls-bindings extra.

Do we have an environment with blspy and one without?

We could do that but if we just don't provide a fallback and just make sure tests that depend on it install bls-bindings that might be less effort to get around it?

Ah ok. I think it might not work without an actual fallback. At least, my two minute research suggest there is no easy way to prevent these imports to get triggered. So maybe the fallback would be the best option.