"Remember Me" functionality doesn't work when users access my app from 2 separate browsers

I've run into a pretty annoying behavior in which "remember me" doesn't work across browsers. Here's how to reproduce it:

Log in on Browser A (remember me = true)
Log in on B (remember me = true)
Quit browser A
Re-open browser A

You are now logged out of the application on browser A. Instead, you should remain logged in on browser A until you click "log out"

Isn't that normal since you are still logged in browser B?

"Remember me" means "keep me logged in on this browser until I click log out". I.e., the behavior of "remember me" shouldn't depend on what I've done on another browser / computer somewhere.
I feel very strongly that this is the correct behavior – this is how Gmail, Facebook, and Twitter all behave. In fact, I can't think of a single famous web application that has the current sorcery behavior. (Also, AuthLogic's "remember me" behaves in my preferred manner as well)

I think that's because sorcery saves a new remember_me_token to the DB on every "remember me" request, regardless on browser. This makes the remember_me_token in other browser cookies revoked.
The solution that comes to my mind right now is to create a DB "session" record for every login from every browser, with expiration date, instead of the single token per user record. When the user cookie is sent, the token is looked up in the sessions table, and the user id is retrieved and auto-logged in.

I think the solution is to save a new remember_me token only when the use changes his password, not when he logs in with a "remember me" request.
I.e.:

Every user has a remember_me token
Checking "remember me" when you log in tells the server to add this token to your cookie
If you log into multiple browsers with "remember me", each browser gets a cookie with the same remember_me token
When the user changes his password, reset his remember_me token as well (and put the new token in his cookie if the old token was there)

This is what authlogic and most websites do.

If you don't also keep expiration info on each browser, than the expiration will take effect from the time of the first browser, even if the last browser asked for "remember me" just a minute ago (unless you put a really big expiration time and then it won't matter).
Also, when using the same token until you change password, you increase the window of getting your token read by an attacker.
I found this like:
http://stackoverflow.com/questions/2594960/best-practice-to-implement-secure-remember-me
and it made me think it might be a good security measure to generate a new token on each login via cookie. Will make the attack window even smaller. Of course, to make it work across browsers means keeping a record per browser.

Ok, so we have httpOnly turned ON (prevents javascript from reading it), the cookie is signed (prevents cookie tampering), and let's say we don't use SSL.
So an attacker can now only steal your token by listening to your network traffic.
If we switch remember_me token on every login, even if an attacker gets your token by listening, it is already void.

If you don't also keep expiration info on each browser, than the expiration will take effect from the time of the first browser, even if the last browser asked for "remember me" just a minute ago (unless you put a really big expiration time and then it won't matter).

Right, the correct behavior is to have a large (and in fact functionally infinite) expiration time. If the user checks "remember me" he shouldn't be logged until he clicks "log out". This is how almost all websites work; e.g., I think I've been using the same Gmail "remember me" token on my iPhone for over a year

If we switch remember_me token on every login, even if an attacker gets your token by listening, it is already void.

Right; this is the current behavior, and while it's more secure, it's also more inconvenient for the user (/ not what they expect). (And if security is your #1 concern, you should just disable "remember me" functionality entirely – by implementing "remember me" a developer is saying "I want to sacrifice security for convenience because this isn't a banking website" or whatever)

and it made me think it might be a good security measure to generate a new token on each login via cookie. Will make the attack window even smaller. Of course, to make it work across browsers means keeping a record per browser.

I don't see how having one token per browser is better (or functionally different at all, actually) from having one global token. As you say, the big security issue is someone sniffing any valid remember_me token. So who cares whether the user's token is "cat" on Firefox and "dog" on Chrome; you can still own him by sniffing his traffic from EITHER browser and grabbing EITHER token, no?

No no, what I meant was, the token the attacker is sniffing right now, is already obsolete, because when the user sends me his token, I give him a new one on the spot. The attacker could also sniff for the new token sent from the server, but the window to use it will be very short if it is constantly replaced. This is a very secure remember me, though a bit taxing on the DB.
Such feature will have to be managed per browser since each browser holds a different token at each time.
But that was just thinking out loud...
regarding Gmail, I'm actually logged out once a month on my browser, so it's not 9999 years expiration.
I do agree the whole feature is insecure by nature... I guess it will not be less secure than it is now with your suggestion.
However, I would like your opinion (anyone) on the ultra secure remember me feature.

No no, what I meant was, the token the attacker is sniffing right now, is already obsolete, because when the user sends me his token, I give him a new one on the spot. The attacker could also sniff for the new token sent from the server, but the window to use it will be very short if it is constantly replaced. This is a very secure remember me, though a bit taxing on the DB.

Ah – let me see if I understand:

Client logs in with "remember me"
Server gives him a remember me token (say it's "dog"), and a browser identification token (say it's "pepsi")
On next request, client sends server token "dog" (and his browser identification token "pepsi"). Server sees that it's the same client and he's logged in with "remember me" and the request succeeds
Server now gives the client a new token ("cat")
Client makes another request with token "cat" (and the same browser identification token "pepsi"). Server sees that it's the same client and he's logged in with "remember me" and the request succeeds
Server gives the client a new token again! ("house")
If the attacker had sniffed "cat" before, it's useless. The only way an attacker can own the client is by sniffing the new token the server sends down BEFORE the client uses it in a subsequent request

This does seem like a more secure strategy if you're not using SSL. But if the server REALLY cares about security, it must implement SSL anyway, which kills the advantages of this approach – I mean, without SSL the client can still get SUPER-DUPER-owned by simply having his password sniffed, and the only way to defend against that is with SSL.
Either way, I think your proposed strategy could be a future feature, but that in the meantime you should change the behavior to reset the remember_me token on password change instead of log in since, though it is less secure, it's what the user expects / wants (and it's a much simpler change).

On second thought, if I needed secure login I would just use SSL... :-)

Yes, your algo description is correct, and I've (finally) reached the conclusion that SSL is the answer...
Alright, it will be fixed when I get around to it.
Pull requests are also welcome, as always ;-)

I feel like the current approach and what people write on the internetz is too model-centric. I used authlogic previously and it was even more confusing by introducing an additional UserSession class.
Why not simply use Rails session for the remember me functionality? This is an ideal application for the session construct. They've done all the hard work for you.  As always it's best to use a database-backed session, especially if you are already using authentication (hopefully with SSL).
In your before_filter you check last_login_at with your remember-me period to decide what to do. After that you can execute require_login and everything works as always.
You don't even need adding a remember_me field to your model. It can be "volatile" in the session, but resurrected from login to login.
If you find ActiveRecord session store slow, then you can use Cache or Redis store.

A more appropriate term would be server-based session :)

*server-backed

I looked at the code yesterday and noticed that session_timeout is doing something similar, but unfortunately the current implementation doesn't allow me to leverage it to implement a session-based remember_me and inactivity timeout at the same time. When you have config.session_timeout_from_last_action = false it doesn't track last_activity in the session.

@arnvald I'd like to help out in any way possible to get this out the door. Thanks for the great gem.

@bfischer1121 @mokolabs @MartinodF
if any of you wants to take this task, I'll be very happy to help. A few months ago Devise introduced some solution, I think it's worth checking it to see if it works well and if it's easy to implement in Sorcery.
I’ve created a Gitter room for Sorcery: https://gitter.im/NoamB/sorcery - feel free to ask me any questions there.

To all waiting for some progress on this: I have implemented support for persisting the login token as a configuration option (default behavior remains unchanged). See my pull request here with full details: #690. Please use and test in your apps to see if it solves your use case.

Here's a little background on the pull request from @rubiety.
We've been using sorcery for a few years on Graffletopia, and the lack of support for multiple "remember me" browser sessions has always annoyed me.
So I thought this would be a good opportunity for us to contribute back to the sorcery project by having @rubiety devote some time to fixing this issue.
Please let me know what you think!


Error: After Effects error: File myPlaceholder is not a valid file type for import.

I got this error message "Error: After Effects error: File myPlaceholder is not a valid file type for import."
After some debug, I realized that the error was coming because I was using a layerName (myPlaceholder) without the file extension.
If you get the same error, just use a extension on your layerName like "myPlaceholder.mp4"
Should we add something warning about this on wiki? Like "If you are using layerName, you should have a file extension on the layerName".

good point, i think that best place for it would be near layerName definition in the readme

fixed in https://github.com/inlife/nexrender/commit/0c4e945150074e0e5f5163c0dca17ed515ff898c, closing the issue


Remove deprecated --worker CLI flag

WHY are these changes introduced?
This flag has been deprecated for a while and is due to be removed with the next release

WHAT is this pull request doing?

Remove deprecated (and unused) --worker flag

Checklist

[x] I've read the Contributing Guidelines
[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've added a changeset if this PR contains user-facing or noteworthy changes
[x] I've added tests to cover my changes
[x] I've added or updated the documentation

I have now reverted the --env-branch flag and updated the PR description and title accordingly


1.1.18 Bug - Missing Title in Config Flow

%key:common::config_flow::data::title% is missing / not defined in Dialog.
Version of the custom_component
1.1.18
Describe the bug
Home Assistant Config Flow Miner / Name dialog is missing the title variable.

Fixed in 1.1.19rc2.  Will have it fixed in non-prerelease with 1.1.19.


Ceedling cannot work if the header file and the source file do not share the same name?

Hello, I'm experiencing an issue with Ceedling. It seems unable to link the header file properly. In this scenario, I have two files named A.c and B.c, and both are using the same header file named M.h. When I execute the test_A.c file, I encounter an error indicating that the functions in A.c are undefined. Upon further investigation, I realize that the issue arises because the header file and the source file do not share the same name (A.c -> M.h). Therefore, I need to find a solution that allows me to work with this naming configuration. What steps can I take to resolve this?
Thanks in advance. :)

Hi. From your test, you can still include the header file (if you otherwise still want it included). In addition, you can use the following macro to specify that you also want to include an additional source file in your test:
TEST_FILE("A.c");

Also, a quick note: In the soon-to-be-released Ceedling, this feature is getting an updated name to the following:
TEST_SOURCE_FILE("A.c");

What about the header file? I don't want to include an additional source file in my test. The issue is that the header file used for this test has a different name than the source file I am testing, which causes the function I want to test to be undefined.
In this case, the header file is named bus.h, and the source file is buss.c, which includes #include "bus.h". My test file is named test_buss.c, also including #include "bus.h". The path is correct in the project.yml file.

Sorry. For clarity, is your situation that the following files exist:

bus.h
bus.c
buss.c

Or that only these two exist:

bus.h
buss.c

If it's the latter, it's easy. Your test would include the header and then specify the source file:
// test_buss.c
#include "bus.h"
TEST_FILE("buss.c")

// the rest of the file

If you're the first situation above, you're saying you want test_buss.c to use bus.h but NOT bus.c, correct?
This is going to sound silly, but you can do this:
// test_buss.c
#include "mock_bus.h"
TEST_FILE("buss.c")

// the rest of the file

The file mock_bus.h will include bus.h to give you the header you need access to, but it won't include the real bus.c. Instead, it'll include the mock... That doesn't mean you have to use the mock... you can make 0 calls to it. :)


Check lint on dev start

There are many lint errors on the current master branch. The reason It's possible is lint checking is not strict here. If no one runs lint before commit, lint would be the thing no one use.
It may be better to strict lint on dev-server start.
i.e, "start": "npm run clean-dist && npm run lint && webpack serve --config webpack.dev.js --env dev --progress --node-env development",

[x] I am willing to work on this issue and submit a pull request.

Which file? If you mean printable.md, it's generated automatically, there's no need to lint it. We have lint-staged to run lint-js on .js, .jsx, .md to make sure there is no lint issues when you're committing, so I think it wont be a problem. Besides, running lint at dev stage would introduce another overhead to the already long-running dev command.

Oh, I see. It's in printable.md Then why is it not in .eslintignore?

It won't be generated in dev environment. Only when you run 'yarn build' will it be generated.


dataset

kindly provide a direct download link for the
dataset thankyou

Hello @nida-khurshid. Thanks for your request. You can email<EMAIL_ADDRESS>to request the dataset, and we will get back to you.


Message Annotations content missing

Related with Azure/azure-event-hubs-go#131.
After some investigation, I find that the msg received in the below method only has three Annotations:
https://github.com/vcabbage/amqp/blob/7c41f1a1270d0d35b778b09b70c0e3063cd088af/client.go#L1810-L1839

The missing x-opt-partition-id annotation prevents the event hubs library to parse the partitionId for the event.
https://github.com/Azure/azure-event-hubs-go/blob/26616d904577c5d0b8c0a486b4b0e77c9c002284/event.go#L56-L62

Looking at a packet capture when receiving from Event Hubs I don't see x-opt-partition-id. Is there some thing extra that needs to be done to get EH to include that?

@devigned it seems that the x-opt-partition-id stuff is introduced in Azure/azure-event-hubs-go#108. Is there any documentation for this? I cannot find any test cases which will let the service side send this annotation.

I can’t find docs regarding x-opt-partition-id and at this point, I’m not sure if that was a meta field that previously existed or if it was a request to the service team to add the field. I’d reach out to the service team or other AMQP SDK teams for guidance.
This issue belongs in the Azure repos.


Trackr setup documentation - initial; Closes Issue #18

Initial addition of Trackr setup doc and updated event source image.

Requested change made.

Looks like I steered you wrong.  😊 You need a space between the # and the title text.

Fixed now. :)

Looks good.  I'll merge everything in.


Null pointer exception error

Description
Null pointer exception could also be renamed to for more meme potential..

Domain
Develop
Type of Contribution
Enhancement
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of bhai-lang.

Excellent suggestion


Update invitation email

The current invitation email does not account for if Swagger UI is not installed.  Update the email to be sensitive to which parts are being installed.

PR merged


Add Ludo

Ludo is a work in progress libretro frontend written in go.
https://github.com/libretro/ludo

{
"version": "0.16.18",
"description": "A libretro frontend written in golang",
"homepage": "https://github.com/libretro/ludo",
"license": "GPL-3.0-or-later",
"architecture": {
"64bit": {
"url": "https://github.com/libretro/ludo/releases/download/v0.16.18/Ludo-Windows-x86_64-0.16.18.zip",
"hash": "7dc3e65b5a9f821429bd2326d756017aff62451f0a92313fc7bc2fba84f295c6",
"extract_dir": "Ludo-Windows-x86_64-0.16.18",
"shortcuts": [
[
"ludo.exe",
"Ludo"
]
]
}
},
"checkver": "github",
"autoupdate": {
"architecture": {
"64bit": {
"url": "https://github.com/libretro/ludo/releases/download/v$version/Ludo-Windows-x86_64-$version.zip",
"extract_dir": "Ludo-Windows-x86_64-$version"
}
}
}
}


db-migrate db:create not working as intended

I've been playing around for most of the morning with db-migrate and getting myself familiar with the ins and outs. One thing I have noticed is that the db:create command doesn't seem to work as I would have expected it.
For example in my database.json I have configuration for a test database and a dev database. Now, when I run the db-migrate db:create myapptest I would expect to see that it creates a database to run my tests against. instead I get the following error:
[ERROR] Error: ER_BAD_DB_ERROR: Unknown database 'myapptest'
the whole reason for running the db:create command is because that database doesn't exist and I want to create it.
Yet if I create the database and then run the command passing a a random name it will happily create any database I want. It will also claim that I have created the same database multiple times even when it has in fact created it once.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Just has the same problem. Maybe you should rename the issue because that is a big issue.
db:create tries to connect to db before creating it.

I ran into this as well when trying to set up a new project using db-migrate.
If you remove the database name from database.json, then db-migrate db:create mydatabase works fine. But then none of the migrations will work until you put the database name back in database.json
What I expected was:

running db-migrate db:create (no database name specified) will attempt to create a database with the name as specified in database.json If there is nothing specified, it will error out.
running db-migrate db:create nameofdb will attempt to create "nameofdb", if it doesn't already exist. If it does already exist, it will report that. This will override whatever database is specified in database.json

I'm also having the same issue.
If I don't specify the database at database.json and run db:create [db name] it will create successfully. But if any database is specified at the configuration it'll try to connect to it before running anything.
I think the expected behavior should be like @deegale described.

I am having an issue where when I do db-migrate db:create <dbname>  it errors out saying database "zaidq" does not exist where I think "zaidq" is my pc user

@zaidqureshi2 @bernardocs @deegale I just solved with some magic:
TLDR: Turning off the magic flag of CONNECT_WITH_DB: https://github.com/mysqljs/mysql#default-flags
First I have the following .env:
MYSQL_URL=mysql://root:root@localhost/myapp

and the database.json:
{
  "defaultEnv": "mysql",
  "mysql": {
      "driver": "mysql",
      "url": { "ENV": "MYSQL_URL" },
      "multipleStatements": true
   }
}

So a basic configuration. The db-migrate db:create myapp fails because the database does not exists. So I either remove the database from the url but then my application won't know about which db should be used or I turn off the flag of CONNECT_WITH_DB in the mysql connection, but I want to do this only for the db:create, for the rest of the commands I want to have database there. So this is what I did:
{
  "defaultEnv": "mysql",
  "mysql": {
      "driver": "mysql",
      "url": { "ENV": "MYSQL_URL" },
      "flags": { "ENV": "MYSQL_FLAGS" },
      "multipleStatements": true
   }
}

The commands I use:

db creation: MYSQL_FLAGS="-CONNECT_WITH_DB" db-migrate sync
db sync: db-migrate sync

Since the creation and syncing are two separate steps a new connection will be created everytime.
Hope this helps you!

This occurs when trying to use Postgres as well. My driver is "pg", and I've installed db-migrate-pg.
>  db-migrate db:create $( jq ".local.database" database.json) -e local[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: database "aegisdb" does not exist
    at /usr/local/lib/node_modules/db-migrate/lib/commands/db.js:17:12
    at /usr/local/lib/node_modules/db-migrate/lib/driver/index.js:95:9
    at /usr/local/lib/node_modules/db-migrate-pg/index.js:662:7

On db-migrate 0.11.3, btw.

Having the same issue, I guess it tries to connect first using the config, then run db:create

I've added a fix, ready for review @wzrdtales

This has not been resolved in 0.11.14

Running 0.11.14 as well. Workaround still works but issue still exists.


Exploratory: Support for BigQuery data import into Meltano

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/971
Originally created by @dmor on 2019-09-10 19:40:18

BigQuery is a data warehouse where some of our users stores their data.
Idea from Davis (new analyst) on the infrastructure team - They're looking to pull billing data

View 4 previous comments from the original issue on GitLab


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_8csogwnrfp/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_8csogwnrfp/clone/recipe/meta.yaml:21: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8csogwnrfp/clone/recipe/meta.yaml:23: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_8csogwnrfp/clone/recipe/meta.yaml:40: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /tmp/abs_8csogwnrfp/clone/recipe/meta.yaml:48: missing_description: The recipe is missing a description
ERROR: /tmp/abs_8csogwnrfp/clone/recipe/meta.yaml:48: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found


Moment Calendar Bug

Hello :D so for now i found 1 bug with the calendar, when the locale is changed the calendar is without fuctions and seems to be broken, every date i pick results in:
`E	The request did not go through properly.

42000	1064	Error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'date AND (action IN (0,1)) ORDER BY rowid DESC LIMIT 0,30' at line 1`

i change the following:
index.php:

For all language support
and add to index.php :

For force german language
i think an part from the lookup.js cant understand the "de"(german) format..?
            // UNIX to JS Date             if(c.form.timeDividor < Math.abs(lastDataTime-r[i].time) || !moment(lastDataTime,"X").isSame(r[i].time*1000, "day")) {                 o += '
-	'                     + moment(r[i].time, "X").calendar(null,{                         sameDay: "[Heute um] " + c.form.timeFormat,                         lastDay: "[Gestern um] " + c.form.timeFormat,                         lastWeek: "[Letzten] dddd, " + c.form.dateFormat + " " + c.form.timeFormat,                         sameElse: c.form.dateFormat+" " + c.form.timeFormat                     })
(i have here manually translated "today" etc to german)
But how can i change it? Please help.. i have only standard html/php knowledge

Iam looking forward too it :)

Speaking of Locale, do you think it would make sense to make the entire lookup form and table column headers translatable?

What you needed to do was modify this part of the code: https://github.com/SimonOrJ/CoreProtect-Lookup-Web-Interface/blob/master/web/res/js/lookup.js#L71
    $date.datetimepicker({
        locale: "de",
        format: c.form.dateFormat+" "+c.form.timeFormat
    });

It would look like that in your case.
This is available right now for people who used git to get the project.  I'll pack an update and upload the package soon.  It'll come with a locale option in config.json. :)

The latest release should come with a one-step option to change the locale in config.json file.  Give that a try, and please tell us how it goes. :)
... I forgot to implement that setting in setup.php file... so it'll only be available by directly changing the configuration file using a text editor for now.

yeah not the problem i use notepad++ thank you for this enchant! its amazing thanks! greetz from germany ;)

What do I have to add to get the german format? de-DE?


Phrase match with any number of spaces

I found out that "Hello world" does not match if the pdf is distributing text using extra spaces and there's a
"hello      <space>      world".
I need this functionality, so I'm modifying  _calculateMatch(pageIndex) to alow regExp search. The needs for my project force me to ALLWAYS use it, so I'm doing it in a dirty way.
However, if you are interested in giving full regular expression support, I can work it out with you to agree with an acceptable implementation to be merged (new checkbox in the search view, allowing to do it from params somehow, etc).

Looks like a duplicate of #7355.

new checkbox in the search view,

That's generally not accepted, unless similar functionality exists in the Firefox findbar (given that this project exists primarily for the PDF Viewer in Firefox).

allowing to do it from params somehow

Again, we don't want non-standard hash parameters added.

Okey, thanks. I'll keep it for my project then.
BTW, you said this findbar is used for firefox PDF viewer, but my firefox (v74 Win x64) does not display search option for pdfs, but if I use native firefox ctrl+f it appears to be equivalen, ¿is that normal, some kind of "new" enhanced behaviour? Never noticed it until now, tbh, I think last time I checked it was a separate button

Closing as answered in https://github.com/mozilla/pdf.js/issues/11750#issuecomment-604428097.


Unexpected Shift via Ancestral Paragon

Hello,
with 5.8.2 I've created a gnome druid and tried to select 'Unexpected Shift' via 'Ancestral Paragon' as a level 3 general feat. Sadly the system didn't offered me this as a possible option.

Not able to reproduce. Does the character already have the feat?

I've deleted the character and recreated it again. This time it was working. Sorry for the trouble. It might be possible that it was added under bonus talent.


EvtDeviceEnableWakeAtBus and EvtDeviceDisableWakeAtBus have no reference back to the function used to set them

EvtDeviceEnableWakeAtBus and EvtDeviceDisableWakeAtBus need to have a reference back to WdfPdoInitSetEventCallbacks, the function used to set them. It was hard to discover this information. Other callbacks set by the same function, like EvtDeviceReportedMissing do have that.

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

ID: 4df2c1a5-d5a1-b6af-9ece-8964d8cdca17
Version Independent ID: 61208f2d-3314-1cb7-4d75-8570cbebc5a4
Content: EVT_WDF_DEVICE_ENABLE_WAKE_AT_BUS (wdfpdo.h) - Windows drivers
Content Source: wdk-ddi-src/content/wdfpdo/nc-wdfpdo-evt_wdf_device_enable_wake_at_bus.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Thanks for taking the time to let us know, Rahul - I'll get this done soon.

Thanks for taking the time to let us know, Rahul - I'll get this done soon.

Just pushed the fix, waiting for update to live site

Just pushed the fix, waiting for update to live site

Live site has the fixes.  Thanks again for letting us know, Rahul.

Live site has the fixes.  Thanks again for letting us know, Rahul.


Add "Open Containing Folder" button to locally saved images if save to directory is enabled

You should be able to do this with the right click sub menu. Right click "open containing folder"

This is more meant for notifications, but yes we can do that too.

Actually, negative. We cannot do that, as we don't link a local image with a remote one.


Update Yarn version in Dockerfile?

It's pegged to yarn@1. Should make sure that's correct.

Yarn is still at v1 👍


--retries

@rultor release, tag is 0.17.0

@rultor release, tag is 0.17.0

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.17.0

@yegor256 Done! FYI, the full log is here (took me 9min)


chromium: 83.0.4103.61 -> 83.0.4103.97

https://chromereleases.googleblog.com/2020/06/stable-channel-update-for-desktop.html
This update includes 5 security fixes.
CVEs: CVE-2020-6493 CVE-2020-6494 CVE-2020-6495 CVE-2020-6496
Testing status

platform
attribute
status
tester

x86_64
chromium

@danielfullmer

x86_64
nixosTests.chromium

@danielfullmer

x86_64
google-chrome

@primeos

aarch64
chromium

@thefloweringash

Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

chromium and nixosTests.chromium build and tested working on x86_64-linux.

Built chromium and nix-build nixos/tests/chromium.nix -A stable on aarch64 successfully, have not tested interactively.


I want to add more pet option in ur site

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

can u plz assign this issue to me

Heyy!! Can you please assign this to me? I'm eager to contribute and would love to work on this under GSSoC'24.
Thanks!

hello! Mythri here. I have worked with web dev projects and am eager to contribute to your website under GSSOC'24. Please Assign this issue to me! @akshitagupta15june
Thank you!


CSV filename is bad in Firefox 17.0.1

Since we aren't updating this app, we will just treat this as a known issue.


Clarify schedule is guideline

I think otherwise the spec page seem a bit harsh.

yeah i'm not a native english either, so better phrasing welcome.
On Mon, Oct 2, 2023 at 15:33 Lars Grüter @.***> wrote:

@.**** commented on this pull request.
In spec-0000/index.md
https://github.com/scientific-python/specs/pull/272#discussion_r1342701623
:

+Below is an auto generated schedule, with recommended date for considering
+stopping support. We suggest that the next release in a given quarter is

The grammar might be off here? How about "..., with recommended dates at
which dropping support should be considered." Not an expert either tough.
—
Reply to this email directly, view it on GitHub
https://github.com/scientific-python/specs/pull/272#pullrequestreview-1652764007,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACR5T7Q7Q6F47U6TWEFSALX5K7EBAVCNFSM6AAAAAA5PEIMISVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMNJSG43DIMBQG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

A more broad comment on the wording we're converging on here: is it really the technicalities of when to drop that is confusing? In my experience the big issue is what people think of when "drop" is brought up. Maybe we want to add a disclaimer that says something to the effect of:

Disclaimer on this SPEC: Drop here is not meant to convey removing support for specific versions of upstream packages. Instead, we intend to ease maintenance burden by providing a schedule where upstream version support is not guaranteed to be supported. This way maintainers have a specific window of support they may commit to without adding maintenance burden of deprecations, etc.

I think that would make things more confusing.
in practice it is removing support. I mean if you don't test on CI it might
as well be broken.
For me in IPython, when I drop, i'll bump flags in ou upgrades, and that
will likely remove conditionals like if version_info < ... , so the package
won't work.
let say it work and you put python_requires>= , then even if supported it
won't install.
I think we can leave "drop" to interpretation.
IMHO what maintainer may not realise is that often dropping from main mean
it will get drop from stable a few month later once there is a new release.
On Mon, Oct 2, 2023 at 19:41 Madicken Munk @.***> wrote:

A more broad comment on the wording we're converging on here: is it really
the technicalities of when to drop that is confusing? In my experience the
big issue is what people think of when "drop" is brought up. Maybe we want
to add a disclaimer that says something to the effect of:
Disclaimer on this SPEC: Drop here is not meant to convey removing support
for specific versions of upstream packages. Instead, we intend to ease
maintenance burden by providing a schedule where upstream version support
is not guaranteed to be supported. This way maintainers have a specific
window of support they may commit to without adding maintenance burden of
deprecations, etc.
—
Reply to this email directly, view it on GitHub
https://github.com/scientific-python/specs/pull/272#issuecomment-1743466548,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACR5T4RTRQ232HKSIAXHMDX5L4DJAVCNFSM6AAAAAA5PEIMISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGQ3DMNJUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I agree with @Carreau here. While some parts (maybe even 99.9%) keep working when dropping support, removing from CI but not explicitly changing python_requires tended to lead to more problems and a lot of headaches of sorting out bugreports.
I also like to be very explicit with minimum versions for dependencies, even if an older one might work, I bake in the minimum that I test with and don't rely on wildcarded versions either.

While some parts (maybe even 99.9%) keep working when dropping support, removing from CI but not explicitly changing python_requires tended to lead to more problems and a lot of headaches of sorting out bugreports.

That's definitely not what I was trying to imply here. I was trying to make it clear that this SPEC isn't intended to add maintenance burden for lower support versions (in both ways -- by not keeping some lower version supported for all time, but also not that dropping support needs to be some huge deal every quarter)? That was my impression from our conversations. Is there a way to be clearer about this so it isn't interpreted aggressively like we've seen in some cases?

Ahh, ok, sorry, then we're all on the very same page :)


making core threadsafe

Base is branch:
ugc1hc/feat/threading_feature
review core, make critial places thread safe and implement corresponding selftest.

Initial threding is delivered.
There are now multiple specific tickets => close this generic ticket.


Dear author, can you provide the checkpoints?

It's too long for me to train once again. Thanks a lot!

I already provide, please read the document.

oh! I saw it! https://drive.google.com/drive/folders/1NLzyvMFxuv8Qy52q_OzcNsugTS5JacAT  I'm sorry to bother you


Use a Fragment to host the embed view to fix issues with Compose interop

Relates to various discussion in https://github.com/react-native-community/discussions-and-proposals/issues/446
Nesting our view inside of a Fragment is the only way I've found so far to get the desired behavior without destroying the underlying composition when it's removed from the window. This also requires the accompanying Android change https://github.com/appcues/appcues-android-sdk/pull/476

example: an embed targeted to every screen, but the frame only exists on the embeds tab
https://github.com/appcues/appcues-react-native-module/assets/19266448/a913ffed-2c87-4787-87bc-a8182fd952c7

example: embed targeted only to screen "Embed Container"
https://github.com/appcues/appcues-react-native-module/assets/19266448/c261edda-a22b-471d-8af6-9fba14fc9adc

example: embed targeted only to "Update Profile" (not the tab the frame is on)
https://github.com/appcues/appcues-react-native-module/assets/19266448/aeb5b524-f332-4406-a1d7-13afee2e3715

example: three embeds targeted to every screen (using all frames) + another flow on event1
https://github.com/appcues/appcues-react-native-module/assets/19266448/1a386dea-979f-4a9d-b75b-f84237a3471c


Apply to Google Summer of Code

We should apply to the Google Summer of Code:
https://developers.google.com/open-source/gsoc/

Organizations apply starting January 4th, 2018.

/cc @mpl @willnorris @lindner

Does it not imply a significant amount of mentoring?

I think we missed the cutoff for this.

Yeah, sorry. Next year, I guess.

let's open another bug next year then.


Test case to test kdump with workload.

This test runs stres-ng test for 20min and triggres crash.
Signed-off-by: Pavithra<EMAIL_ADDRESS>

Raised new PR.


[api-docs-builder] Allow custom annotations

In Base UI docs, all component docs and its API reference are placed on the same page
This PR updates the docs builder so that instead of separate API and docs URLs...

...we can use custom annotations provided from where the docs builder script runs:

Is there a PR in Base UI that uses this code already?

Probably this one: https://github.com/mui/base-ui/pull/1015, not sure if it was updated locally only as I don't see bump on the package itself.


WPEFramework crash when shutting down

We see the following crash when exiting from WPEFramework service:
Core was generated by `WPEFramework -c /etc/WPEFramework/config.json'.
Program terminated with signal 11, Segmentation fault.
#0  0xb6eb6c5a in WPEFramework::RPC::Administrator::~Administrator (this=0xb6ecc754 <WPEFramework::RPC::Administrator::Instance()::systemAdministrator>, __in_chrg=<optimized out>)
    at /usr/src/debug/wpeframework/1.99+gitAUTOINC+0105e8f8ed-r0/git/Source/protocols/Administrator.cpp:38
38                  delete proxy.second;
(gdb) bt
#0  0xb6eb6c5a in WPEFramework::RPC::Administrator::~Administrator (this=0xb6ecc754 <WPEFramework::RPC::Administrator::Instance()::systemAdministrator>, __in_chrg=<optimized out>)
    at /usr/src/debug/wpeframework/1.99+gitAUTOINC+0105e8f8ed-r0/git/Source/protocols/Administrator.cpp:38
#1  0xb6cb4570 in __cxa_finalize (d=0xb6ec8138) at cxa_finalize.c:56
#2  0xb6eabb24 in __do_global_dtors_aux () from /home/build/arrisXi6_2003/build-arrisxi6/tmp/sysroots/arrisxi6/usr/lib/libWPEFrameworkProtocols.so.1.0.0
#3  0xb6f1d024 in _dl_fini () at dl-fini.c:252
#4  0xb6cb42bc in __run_exit_handlers (status=0, listp=0xb6d5e520 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#5  0xb6cb431a in __GI_exit (status=<optimized out>) at exit.c:104
#6  0xb6ca44aa in __libc_start_main (main=0x0, argc=0, argv=0xb6f30000, init=<optimized out>, fini=0x5d695 <__libc_csu_fini>, rtld_fini=0xb6f1cddd <_dl_fini>, stack_end=0xbe805d14) at libc-start.c:319
#7  0x00032994 in _start () at ../ports/sysdeps/arm/start.S:124

This is reproducible on the desktop linux with the latest master branch.
crash happens even without any plugins loaded.

Fixed: https://github.com/rdkcentral/Thunder/pull/62

@pwielders I still see this crash happening. #62 did not fix it for me

Nevermind, had to re-build cmake&make under Tools in order to install the new version of ProxyStubGenerator.
After doing that , crash is not seen, thanks!


MAINT: Create FeatureList to cleanup implementation around features #248

Codecov Report

Merging #250 (c9d0e77) into main (d9d48ac) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #250   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           43        44    +1
  Lines         1324      1407   +83
=========================================
+ Hits          1324      1407   +83

Impacted Files
Coverage Δ

pfhedge/instruments/base.py
100.00% <ø> (ø)

pfhedge/nn/modules/bs/black_scholes.py
100.00% <ø> (ø)

pfhedge/features/__init__.py
100.00% <100.00%> (ø)

pfhedge/features/_base.py
100.00% <100.00%> (ø)

pfhedge/features/container.py
100.00% <100.00%> (ø)

pfhedge/features/features.py
100.00% <100.00%> (ø)

pfhedge/features/functional.py
100.00% <100.00%> (ø)

pfhedge/instruments/__init__.py
100.00% <100.00%> (ø)

pfhedge/instruments/derivative/american_binary.py
100.00% <100.00%> (ø)

pfhedge/instruments/derivative/base.py
100.00% <100.00%> (ø)

... and 12 more

Continue to review full report at Codecov.

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


Added Color Game

Added RGB Game
issue number #492

Have made the changes, please review it

changed ref link names in index.html

further changed

update your forked repo once

You have done multiple commits. please make a Fresh PR with proper changes.


When this is merged lbry.tv will have better static asset caching

@kauffj pushed up another commit. I'll change the electron html if you think this looks good.
The main change is that now all images/fonts/js are loaded through public/ public/img and public/font. And I hardcoded the list of every asset we serve in the cache-control middleware.

@seanyesmunt I approved this because it has no issues to block merging, but please at least address the ui.js issue before moving past asset optimizations.


correctly close handle in alsa audio driver.

pcm_open looks like an unnecessary member variable and possibly caused some confusion here.
When switching devices, the old handle would be left open.
Removed it and branched against the relevant pointer instead.

CC @marcelofg55

Changes look good, pcm_open was definitely unnecessary.

Thanks!

Cherry-picked for 3.0.7.


change to post css pixrem

Decided not to do this for now as I prefer to write in px and let the grunt task change to rem


Update index.md

- Summary

- Test plan

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

👷 Deploy Preview for noithatcanho processing.

Name
Link

🔨 Latest commit
f0dbdf5d47e7adf2263b5c007e9cf6b3a4f51330

🔍 Latest deploy log
https://app.netlify.com/sites/noithatcanho/deploys/66ac5a79dc07250008c72c8f


Local terminal can't be opened: \bin\bash not found (though VS Code running on Windows)

VSCode Version: 1.66.1
Local OS Version: Windows 10
Remote OS Version: Linux
Remote Extension/Connection Type: Docker/WSL2 running on host
Logs: error message: The terminal process failed to launch: Path to shell executable "\bin\bash" does not exist.

Steps to Reproduce:

VS Code command: > Terminal: Create New Integrated Terminal (Local)
The error popup appears (see above "Logs")

Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: Yes

Seems like microsoft/vscode-remote-release#730 is broken.
I checked with @modified terminal if there are any changes. Only inside the container the following settings are set:
terminal.integrated.profiles.linux and terminal.integrated.defaultProfile.linux.
Shouldn't it run cmd or powershell locally?

Can reproduce, this doesn't happen by default but it does if you set "terminal.integrated.defaultProfile.linux": "bash"

I'm still seeing this on Windows-WSL

VS code tries to use the path in "terminal.integrated.profiles.linux":"zsh":"path" even in a local macOS environment when connected to a Linux remote. Changing this from "zsh" to "/bin/zsh" is a working workaround.

I also just ran into this, also with a local macOS environment and a Linux remote. FWIW, I found that there's an additional wrinkle: the file referred to by path needs to exist and be executable. So, for example, if you're using zsh installed by homebrew on a Apple Silicon Mac, /opt/homebrew/bin/zsh needs to exist and be executable in the container. If it doesn't, VSCode falls back to /usr/bin/zsh.
This config worked for me:
  "terminal.integrated.profiles.linux": {
    "zsh": {
      "path": "/opt/homebrew/bin/zsh"
    }
  }

I also just ran into this, also with a local macOS environment and a Linux remote. FWIW, I found that there's an additional wrinkle: the file referred to by path needs to exist and be executable. So, for example, if you're using zsh installed by homebrew on a Apple Silicon Mac, /opt/homebrew/bin/zsh needs to exist and be executable in the container. If it doesn't, VSCode falls back to /usr/bin/zsh.
This config worked for me:
  "terminal.integrated.profiles.linux": {
    "zsh": {
      "path": "/opt/homebrew/bin/zsh"
    }
  }

worked! for me was
    "terminal.integrated.profiles.linux": {
        "zsh": {
            "path": "/bin/zsh"
        }
    }

FWIW, I found that there's an additional wrinkle: the file referred to by path needs to exist and be executable

Dang, unfortunately I don't think this workaround helps for WSL since I'm not sure it's even possible to specify a path that exists in WSL as well as on the Windows host, e.g. /mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/powershell.exe (does not exist in windows) vs C:/WINDOWS/System32/WindowsPowerShell/v1.0/powershell.exe (not a valid Linux path)...


Revert "Fix custom Elements that wants to decorate State.build"

Reverts flutter/flutter#49925
This may have caused framework test failures on Cirrus.  Reverting to see...
main.log.txt

Merging on red to green out the build.

LGTM.  Thanks for tracking this down.


Comparizon Viz

comparison_viz() function created

@Birinder1469 Thanks for pointing those out. I've made the updates.
@jessimk Would you please review my work? Thanks

Talha, you probably want to take our argparse functions. Try that.

Thanks for the input Jes.
@Birinder1469 could you review my latest code.


CNDB-10152: Fix Python DTests - update pytest.fail() and skip() for newer pytest versions

The issue can be reproduced by pinning the versions for packages we have installed in Jenkins in your local requirements.txt and reinstalling them by running pip install -r requirements.txt.
This is what I had for reproduction and testing locally:
diff --git a/requirements.txt b/requirements.txt
index e33975e9..cb90dd5f 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -10,19 +10,19 @@
 # In case you want to test a patch with your own CCM branch, further to changing below CCM repo and branch name, you need to add -e flag at the beginning
 # Example: -e git+https://github.com/userb/ccm.git@cassandra-17182#egg=ccm
 git+https://github.com/riptano/ccm.git@converged-cassandra#egg=ccm
-decorator
-docopt
-enum34
-flaky
+decorator==5.1.1
+docopt==0.6.2
+enum34==1.1.10
+flaky==3.8.1
 mock
-pytest>=6.5.0
+pytest==8.2.2
 pytest-timeout==1.4.2
 pytest-repeat
 py
-parse
-pycodestyle
-psutil
-six>=1.12.0
+parse==1.20.2
+pycodestyle==2.12.0
+psutil==6.0.0
+six==1.16.0
 thrift==0.10.0
 netifaces
 beautifulsoup4

Leaving the PR as draft until I finish new round of Jenkins testing to confirm there were no more places to fix.

So we should update the requirements.txt for dtest as well?

So we should update the requirements.txt for dtest as well?
We should not, I pinned exact versions just to be able to have the same packages as Jenkins where the tests fail. For me, locally, they were not failing as my env was pulling different versions. I assumed someone else may say those tests do not fail for them locally, thus I provided the reproduction steps.
We normally do not try to stick to one version in requirements.txt, but we fix things when they break with newer ones.

Isn’t the whole point of the requirements.txt to specify the versions the code runs under?  If the code is being written for those new versions I would think we should update it?  If we want to leave the version specification as it is then I would rather we specify a max version and not change the tests.

That is why we never update things like drivers and ccm and run behind if we pin an explicit version.
I was told that in the past, we have something like two packages pinned to explicit versions here in requirements.txt.
If I pin pytest, I will need to pin some of its dependencies, too, as otherwise, tests break.
In the case of pytest, maybe it will be easier to upgrade to support new Python versions if we do not stall on the old version. I'm not sure.
Honestly, I do not have a strong opinion; it works both ways for me. The current fix was small; I can revert it. I know it is best practice to pin versions, but I know people did not do it as they know we will never update anything in CI and accumulate tech debt.

Let’s go to the new version. It’s good to stay up to date every once in a while :)

Closing this one in favor of https://github.com/datastax/cassandra-dtest/pull/72


search functinality or pages indexed

Can we get a search functionality added or the pages indexed by search engines?

For the search engines, see issue #8

google search cockpit status: 22 pages indexed, 122.686 not...
If somebody has an idea how to speed up google crawling our pages, sitemap.xml did not the trick.


Introduce the infrastructure for mutations in DCL

Context

Contributor Checklist

[ ] Review Contribution Guidelines.
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[ ] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test RFN

I've triggered the following builds for you. Click here to see all build failures.

ReadyForNightly build

@bot-gradle test RFN

@bot-gradle test QFL

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedbackLinux build

@bot-gradle test QF

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

@bot-gradle test QF

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build


feat: added category list and future modalities

/chore

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 24 (25.0%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 55.285%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/torchwebio/models/image/imageclassificationmodel.py
6
7
85.71%

src/torchwebio/exceptions.py
0
6
0.0%

src/torchwebio/webalyzer.py
0
11
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/torchwebio/webalyzer.py
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
50

Relevant Lines:
93

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-18 of 24 (25.0%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 55.285%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/torchwebio/models/image/imageclassificationmodel.py
6
7
85.71%

src/torchwebio/exceptions.py
0
6
0.0%

src/torchwebio/webalyzer.py
0
11
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/torchwebio/webalyzer.py
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
50

Relevant Lines:
93

💛  - Coveralls


Treat same username on different servers as distinct accounts (fix #194)

This PR fixes #194.
Prior to this change, if user 'jdoe' has signed in to servers 'iris-1' and 'iris-2' there would be only one InterSystems Server Credential  entry for 'jdoe' in VS Code's Accounts context menu, and using the Sign Out action from its submenu would offer to delete stored 'jdoe' passwords for every server they existed for.
This change means 'jdoe on iris-1' and 'jdoe on iris-2' are treated as separate accounts.

@hsyhhssyy please download the zipped dev VSIX from https://github.com/intersystems-community/intersystems-servermanager/suites/14579768037/artifacts/825807469, unzip it and install it, for example by drag/dropping the extracted VSIX onto Extension view. Then see if account sign-out behaves better.

@isc-bsaviano please try this dev VSIX as a cross-check that the change doesn't break anything. I'll probably wait until we've heard from @hsyhhssyy before merging, in case changes turn out to be necessary.

@gjsjohnmurray I just store my passwords in plaintext so I'll defer to the reporter to test this.

@gjsjohnmurray
I greatly appreciate your help. As I've mentioned in a comment on another issue, I've installed this plugin and it's functioning exactly as I had hoped.


AssertionError

I'm getting this issue, every time, on HASS restart:
2021-02-16 11:35:40 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/home/homeassistant/.homeassistant/custom_components/easee/controller.py", line 376, in refresh_sites_state
    self.update_ha_state()
  File "/home/homeassistant/.homeassistant/custom_components/easee/controller.py", line 284, in update_ha_state
    entity.async_schedule_update_ha_state(True)
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/helpers/entity.py", line 438, in async_schedule_update_ha_state
    assert self.hass is not None
AssertionError

I'm running the latest version via HACS (on Raspberry PI OS).
Let me know if you need any additional information. Thanks in advance.

Fixed in 0.9.27.


feat(icons): provide language specific icons in extras

What is this PR for?

Provide language specific file icons. The intent is to lay the foundation of this type of extension / configuration. I've added icons for file types that I interact with but this is definitely not holistic. I also went back and forth on whether the configuration should be within the core UI config or in the extras (I landed on the later). Definitely open to feedback on these changes.
Does this PR fix an existing issue?

Nope.
Checklist

[x] I've read the CONTRIBUTING guidelines.

Thanks!
I do think it makes most sense to contribute PR's to mini.icons.
@echasnovski what's your take on this? What are your requirements to add new icons to mini.icons vs leaving it up to the user to configure?
See the diff in this PR.
I currently added this one for example:
        ["NEWS.md"] = { glyph = "󰎕", hl = "MiniIconsYellow" },

@echasnovski what's your take on this? What are your requirements to add new icons to mini.icons vs leaving it up to the user to configure?

I am leaning on a more cautious side of adding new built-in support for icons, i.e. preferring to suggest user configurations.
Which icon names are intended to be supported in 'mini.icons' is planned to be documented. Here is a rough draft:

Category "filetype" - any filetype that is reasonably used in the wild. This is intended as a widest net for supporting use cases. Users then are encouraged to have a proper filetype detection set up. Note: this currently has some problems due to handful of manually tracked extensions which have precedence over vim.filetype.match() for speed reasons. See, for example, echasnovski/mini.nvim#1017. Give me couple of days to try to figure out the best compromise here.
Categories "directory", "file", "extension" categories - popular not language/software specific, with few exceptions (like for Git, Make, etc.).
Category "lsp" - only values of some *Kind defined in LSP specification.
Category "os" - operating systems which have nf-md-* icon (which is used as proxy for "popular OS").

There are now documented criteria in each category for an icon to be considered for adding to built-ins. TL;DR: basically what is listed in previous comment.
I plan to add new icon data tomorrow.

ok, great!
@m0lson84 would be good to check after tomorrow to see what icons can be removed from the PR

Some of the filetypes from this PR were added to 'mini.icons'. Here is the commit.
Some notes:

'tf' filetype doesn't seem to be for terraform, but for something called TinyFugue MUD client. vim.filetype.match() detects terraform only by contents so I've added special handling of 'tf' extension.
I could not find reasonable usages of 'gotmpl' and 'dotenv' filetypes, so they are not added.

Awesome, thanks @echasnovski!
The new NEWS icon however is currently the same as for changelog.
I used one of the newspaper icons. Maybe a better fit?

The new NEWS icon however is currently the same as for changelog.

This was deliberate as 'NEWS.md' and 'CHANGELOG.md' seem to be used interchangeably. But I am open to changing it to nf-md-newspaper_variant.

Added tests for mini.icons that checks that no icons are added that already exist in mini.icons...

@echasnovski for my plugins (and for a lot of repos using conventional commits), the CHANGELOG.md file is auto generated based on conventional commits.
The NEWS.md file is a manual file, more similar to what you'd find in :h news.
I noticed you didn't include any of the javascript/typescript ecosystem, while those are wildly used. Is there a reason for this? Most of those icons are the exact icons used by the related projects.

Also worth mentioning is that with this PR, fzf-lua seems broken...
No idea why though.

I noticed you didn't include any of the javascript/typescript ecosystem icons, while those are wildly used. Is there a reason for this? Most of those icons are the exact icons used by the related projects.

I think drawing the line at supporting languages/siftware only through filetypes is a healthy compromise long term. The last thing I want is to end up with tons of languages 'mini.icons' has to extensively support. There are Neovim distributions and language plugins for that :)
Thinking about it, I might have to export MiniIcons.set(), because setting icons now can be done only by calling MiniIcons.setup() (which would require careful config preservation).

Also worth mentioning is that with this PR, fzf-lua seems broken...

Very strange indeed.

@echasnovski something seems broken with the devicons integration and setting custom icons..
When I do require("nvim-web-devicons").get_icons(), I get the error below:
E5108: Error executing lua ...lke/.local/share/nvim/lazy/mini.icons/lua/mini/icons.lua:506: Invalid highlight name: 'MiniIconsGray'
stack traceback:
	[C]: in function 'get_hl_data'
	...lke/.local/share/nvim/lazy/mini.icons/lua/mini/icons.lua:506: in function 'get_hex'
	...lke/.local/share/nvim/lazy/mini.icons/lua/mini/icons.lua:529: in function 'make_icon_tbl'
	...lke/.local/share/nvim/lazy/mini.icons/lua/mini/icons.lua:535: in function 'make_category_tbl'
	...lke/.local/share/nvim/lazy/mini.icons/lua/mini/icons.lua:547: in function 'get_icons'
	[string ":lua"]:1: in main chunk

It is MiniIconsGrey, not MiniIconsGray.

Right, should have spotted that :)
Fixed!

Merged. ty!

@echasnovski Thanks for looking this over and bringing some of these suggestions into mini.icons. @folke Thanks for cleaning up my changes and fixing the broken areas 😅.

Added tests for mini.icons that checks that no icons are added that already exist in mini.icons...

I am not sure how those tests are run, but 'CODEOWNERS' is present in 'mini.icons' (and is properly present in MiniIcons.list('file')), yet tests did not fail for it also present in LazyVim.

You're right. The tests only check specs from extras. Will remove!

@echasnovski for my plugins (and for a lot of repos using conventional commits), the CHANGELOG.md file is auto generated based on conventional commits.
The NEWS.md file is a manual file, more similar to what you'd find in :h news.

@folke, do you want to do the honors and choose color for 'NEWS' icon ("󰎕', a.k.a. plain 'nf-md-newspaper')?

Anything works for me :)
Another docs I frequently use btw is TODO.md, but not sure how common that is...

There are now both 'NEWS{.md}' and 'TODO{.md}' on latest main.

Sweet! ty! :)


REPL slows down during extensions compiling

See https://youtrack.jetbrains.com/issue/KT-22740

Fixed in 0.2 by adding new REPL API and implementation


Upgrade to Buildbot Nine

Buildbot Nine is currently in beta (beta8 is due to be released in a week or so) and is getting close to a full release; we're currently running Buildbot Eight (0.8.12) and while not urgent, I'd like to upgrade when Nine is released. There are a significant number of changes in Nine, so it's not a drop-in replacement and we'll need to update our configuration.
I'd like to add more extensive (functional) test coverage to ensure a smooth upgrade; anything that has broken in the past would be a good candidate to add a regression test for. (I'm not sure exactly how Buildbot breaks when it does.)
This would also be a good opportunity to discuss switching to a different CI system since Buildbot is fragile, although I think Buildbot is fine and our biggest wins will come from moving configuration into the main Servo repo as much as possible.

I'm not opposed to a discussion of alternative CI, but what options exist besides Jenkins? Buildbot and Jenkins seem the best things out there for self-hosted stuff, and having used both I'm not sure I would switch from one to the other in either direction.

I'd love to see a world where we can rely completely on externally-hosted services (e.g., Travis and AppVeyor), but there are two things preventing it:

They need to support much larger instance types. We use c4.4xlarge on EC2, which is way bigger than the GCE instances either of them have
homu needs better status reporting/integration of multiple services

So, I'm tempted to stick with the buildbot we know for now, doing the upgrade that you've suggested, and limping along until some external services reach a larger scale point. We are not planning to scale Servo to a point internally where we'd have a team of multiple full-time engineers dedicated to keeping the system running, which is what I think we will end up needing (certainly, every other project does!) if we continue to scale on internally-hosted systems like buildbot, jenkins, etc.
This is pretty consistent with what @edunham and I have been talking about :-) She's responsible for systems across all of research, and Servo would quickly take up 100% of her time if we don't get some of it happening outside of our (virtual) datacenters.
I also agree that the more of it we move into the tree the better! Landing changes that span the source code and CI system are really awkward and require having an administrator push buttons/run scripts at exactly the right time.

Status update: Buildbot 9 was released on October 6, 2016: https://docs.buildbot.net/0.9.0.post1/relnotes/index.html
We've made progress and now read steps from the servo/servo tree, but have had to write custom code for this which has caused some bumps along the way: #515, #524, etc. Buildbot 9 has built in support for dynamic steps and a rewritten (nicer) web UI, which both sound enticing to me. However, I'm not confident that attempting an upgrade wouldn't end up causing more problems than it's worth right now without a better testing strategy. Many of the problems we had would have essentially required standing up a separate Buildbot instance to discover (as opposed to static analysis), e.g. Windows behavior differences or log file naming.

Also from the release notes, it seems like the Buildbot APIs will still be in flux until 1.0.0: https://docs.buildbot.net/0.9.0.post1/relnotes/index.html#master

Closing in favor of #559.


Tests should use *.npz files rather than *.npy

File tests/parallel/test_parallel_discrete_green_operator.py must be updated accordingly.
(initially reported by @vptran).

Solved in commit 99af1f335e909aa1f81568dcea58898f64332b35.


get_group_subscribers filter params does not work as intended

Hey, the filter param for get_group_subscribers does not work as intended.
the doc specifies to user filter={'status': 'active'} however, the code here: https://github.com/mailerlite/mailerlite-python/blob/main/mailerlite/sdk/groups.py#L143 expects the paramter in the following format:
filter={'filter[status]': 'active'}

I have not checked whether this bugs happens on other functions as well.

Hello,
This ticket appears to be marked as invalid, but is indeed a valid issue.
Per the Mailerlite documentation here:
https://developers.mailerlite.com/docs/groups.html#list-all-groups
The expected parameter is filter[name]
The documentation in the readme here:
https://github.com/mailerlite/mailerlite-python?tab=readme-ov-file#list-all-groups
specifies that the filter parameter be in the format of:
response = client.groups.list(limit=10, page=1, filter={'name': 'My'}, sort='name')
This code will return all groups, as the filter parameter is ignored.
The list function on groups (as an example) just appends the filter to the query parameters directly, without modification:
    def list(self, **kwargs):
        """
        Lists all groups

        Returns a list of all groups.
        Ref: https://developers.mailerlite.com/docs/groups.html#list-all-groups

        :param **kwargs: You can pass additional arguments - page, limit, sort or to filter by name
        :raises: :class: `TypeError` : Got an unknown argument
        :return: JSON array
        :rtype: dict
        """

        available_params = ["list", "limit", "page", "sort", "filter"]

        params = locals()
        query_params = {}
        for key, val in params["kwargs"].items():
            if key not in available_params:
                raise TypeError("Got an unknown argument '%s'" % key)
            if key == "filter":
                for filter_key, filter_value in val.items():
                    query_params[filter_key] = filter_value
            else:
                query_params[key] = val

        return self.api_client.request("GET", self.base_api_url, query_params).json()

For example:

As a suggested fix, the loop in list should be updated to something similar to:
        for key, val in params["kwargs"].items():
            if key not in available_params:
                raise TypeError("Got an unknown argument '%s'" % key)
            if key == "filter":
                for filter_key, filter_value in val.items():
                    query_params['filter[%s]' % filter_key] = filter_value
            else:
                query_params[key] = val

Hey!
I had this issue, but with segments. I think the specific issue here has been closed now, but it's present in other endpoints.
I made a more generalised fix to this type of issue in my PR, getting rid of a lot of duplicate code.
https://github.com/mailerlite/mailerlite-python/pull/28


De-nest Receptor.reactivity_measurements

Receptor.reactivity_measurements is a nested object. Move to a standalone object, such as ReceptorReactivity and embed via $ref instead.

fixed in ba626d21ad957c32259341b022f07a99986c67ec


Action is broken

Hi,
I try to update my action to 0.6.0, but it fails always with strange errors:
Workflow:
    - name: Generate provenance
      uses: philips-labs/slsa-provenance-action@8f3f6a835ccfa2c0d5fb1d6dce15691a86575659
      with:
        arguments: -d --artifact-path ${{ inputs.artifact-path }} --extra-materials material.json --output-path ${{ inputs.output }}

Debug-Logs:
docker run image=ghcr.io/philips-labs/slsa-provenance:v0.6.0 platform= entrypoint=[] cmd=["generate" "files" "--github-context" "<redacted>" "--runner-context" "<redacted>" "-d" "--artifact-path" "dist/" "--extra-materials" "material.json" "--output-path" "provenance.json"]
Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "generate": executable file not found in $PATH: unknown

This seems to be an error of the action itself, I really don't know what could be wrong to my config regarding to the docs.
Does anybody have a tip for me?
Thanks!

Hey @ckotzbauer,
Thanks for creating this issue. Just wanted to let you know that we are looking into this.
We will reply here when we have more updates.
Sorry for the inconvenience!

I've tried to reproduce it, but I can't.
https://github.com/JeroenKnoops/slsa-provenance-action-bug-135/blob/main/.github/workflows/test.yaml#L45
Are you using the GitHub cloud runners?

Yes, I use cloud-runners. I got this error when I test my workflow with act. This not exactly the same as the raw cloud-runners, but the error-message sounds like a bug with the action itself.
The PR is public: https://github.com/ckotzbauer/actions-toolkit/pull/18
The UnitTest-Workflow: https://github.com/ckotzbauer/actions-toolkit/blob/main/.github/workflows/test-action.yml
The Workflow which is run as test: https://github.com/ckotzbauer/actions-toolkit/blob/main/tests/slsa-provenance.yml

@ckotzbauer from your provided debug logs I can see the entrypoint is empty.
docker run image=ghcr.io/philips-labs/slsa-provenance:v0.6.0 platform= **entrypoint=[]** cmd=["generate" "files" "--github-context" "<redacted>" "--runner-context" "<redacted>" "-d" "--artifact-path" "dist/" "--extra-materials" "material.json" "--output-path" "provenance.json"]
Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "generate": executable file not found in $PATH: unknown

Therefore it is taking the first argument to the binary as the binary. generate does not exist as a binary. the name of the binary is slsa-provenance.
When running the docker image natively I can confirm the image is correctly defining the entrypoint as seen in the Dockerfile.
docker run ghcr.io/philips-labs/slsa-provenance:v0.6.0

Is there maybe anything else in your pipeline that might be overwriting the entrypoint as (empty)?

Nothing I'm aware of. I don't see any reason why the entrypoint could be overwritten. The image itself is valid, I checked that too.
Maybe I just merge the PR and try it "in the wild" without act. I'll give feedback. 😉

It works perfectly outside of act, so I think it is a problem with act instead. Just a bit confused, cause the test-workflow worked with older versions of the slsa-provenance-action 😆
I think this issue can be closed. Thanks for your efforts!!

Found some documentation.
https://docs.github.com/en/actions/creating-actions/dockerfile-support-for-github-actions#entrypoint
Allthough our action.yml is not overriding the entrypoint, maybe act is doing some magic there.

@ckotzbauer https://github.com/nektos/act/issues/917 seem indeed to be an issue with act.

Yes, this seems to be indeed the issue I discovered here. Thanks for research, much appreciated!

Hey @ckotzbauer,
We made some changes to the GH Action in v0.7.0 which might resolve this issue.
Could you please try using Act again with the new version?

I already tested this and it worked like charm 🎉

Fantastic, thanks a lot! Enjoy 🔥


Authentication failure after calling SetLogHandler

Description
Using SASL_PLAINTEXT with SCRAM-SHA-512 auth, I'm seeing authentication failure with .NET core on Linux (Docker mcr.microsoft.com/dotnet/core/runtime:2.2-alpine base image) after SetLogHandler is called on producer builder to replace the log handler. Confluent.Kafka version is 1.1.0. Kafka version is 2.0.0.
How to reproduce
Everything works with
new ProducerBuilder<Null, string>(config)
    //.SetLogHandler((p, l) => { ... })
    .Build();

But, changing to this
new ProducerBuilder<Null, string>(config)
    .SetLogHandler((p, l) => { ... })
    .Build();

Results in authentication failure
[thrd:sasl_plaintext://kafka-server:39092/bootstrap]: sasl_plaintext://kafka-server:39092/bootstrap: SASL authentication failure: Disconnected: check client SCRAM-SHA-512 credentials and broker logs (after 961ms in state AUTH)

I'll gather and add additional details to the issue later.
Checklist
Please provide the following information:

[ ] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[ ] Confluent.Kafka nuget version.
[ ] Apache Kafka version.
[ ] Client configuration.
[ ] Operating system.
[ ] Provide logs (with "debug" : "..." as necessary in configuration).
[ ] Provide broker log excerpts.
[ ] Critical issue.

that's surprising. does your log handler block? (e.g. file io?). perhaps you're inadvertently adding a delay somewhere that matters, perhaps try doing blocking calls in another thread (perhaps Task.Run(() => ...) and see if that helps. also note that the log handler can be called spontaneously from a number of different threads, so the implementation must be thread safe.

I tried Task.Run, an empty code block, calling SetLogHandler with a null value, all with the same result. The only thing that works so far is to not call SetLogHandler.

Took a better look at the logs this morning. The following messages repeat each time I produce/send out data and an exception is raised because the queue is full
1/1 brokers are down
sasl_plaintext://kafka-server:39092/bootstrap: SASL authentication failure: Disconnected: check client SCRAM-SHA-512 credentials and broker logs (after 0ms in state AUTH)
Local: Queue full
1/1 brokers are down
sasl_plaintext://kafka-server:39092/bootstrap: SASL authentication failure: Disconnected: check client SCRAM-SHA-512 credentials and broker logs (after 0ms in state AUTH)
Local: Queue full

After waiting long enough, the broker is up, the problem goes away. Not setting the log handler was making me see just the Local: Queue full messages, and hence to wait long enough for the problem to go away.
Sorry for the bother.


feat: Client Versioning (+ Provider Trait and ClientBuilder)

[x] I have looked for existing issues (including closed) about this

Feature Request
As model providers start getting more competitive, the provider API routes might adjust and evolve over time. We should consider specifying a standardized versioning with clients (maybe via a builder or something) that helps in specifying how requests should be made to the API.
Motivation
Cohere recently released a v2 of it's chat endpoint.
Proposal

A generic ClientBuilder can be defined to build out specific clients. That way, we can make the ClientBuilder as the singular interface for building all clients and agents.
A Provider trait that helps simplify current and future provider implementation (specifically for top-level clients).

This should make it much easier for having different versioned clients since they'd share the same set of methods to make agents, extractors, etc.

impl Provider<V> for Client<V> {
    ...
}

impl Client<1> {
    pub fn completion ...
}

impl Client<2> {
    pub fn completion ...
}

Alternatives
Only support the latest version. Against this suggestion primarily because LLM and their providers are moving so quickly that many people might be building agents that could become dated in only a month. The providers leave older version endpoints operational so it would be a shame if someone's Agent stopped working due to a breaking change.
The only positive with supporting a latest version is that it simplifies the number of clients per providers but making a provider generic over a Version might be suitable for this.

When I was looking through the source code, I've noticed that the way a completion request is created for Anthropic is not correct. It's modeled after the OpenAI API not the Anthropic one.
IIUC tackling this issue would resolve that, right? If so, could you provide a little bit more detail on how you envision the refactor? I could work on it if that's ok.


new ncnn code inference result not right

I try to using newest ncnn code to replace _dep folder ncnn code, which is only missing lstm2 layer. Compile OK, but run inference got wrong result. Is your ncnn source code do some special modifications?

You can have a look at the commit history of the master branch of
https://github.com/csukuangfj/ncnn

I will find some time to support the official ncnn.

Should be fixed by #207


Testing email notifier keeps connecting and disconnecting but never send mail

Rancher versions: 2.0 master 2/27
Steps to Reproduce:

Go to Add Notifier
Create an email notifier and click on Test

Results:  Stays in testing and if you look at mail server logs you will see a bunch of connecting/disconnecting hits.  This will continue until I delete the cluster.  Should only connect/disconnect once.  Also it never send the email.

stays in testing because when the config is invalid, there is not timeout for dial func. We should set 30s timeout for Dial func.
The email is not sent because it is treated as spam. For now I will just  validate if the config if valid but not sending a email.

Version - 2.0 master 3/2
Verified fixed


Roll Flutter Engine from f09a139101c3 to 019715e02ae6 (2 revisions)

https://github.com/flutter/engine/compare/f09a139101c3...019715e02ae6
2023-09-08<EMAIL_ADDRESS>[Web] Fix insertions/deletions at inverted selection for TextEditingDeltas (flutter/engine#44693)
2023-09-08<EMAIL_ADDRESS>Roll Skia from ece9f3a15b08 to 71e40cc0faf6 (1 revision) (flutter/engine#45575)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Make workspace relative to current dir instead of "" which is "/"

modified:   2d_classification/mednist_tutorial.ipynb
modified:   3d_classification/ignite/densenet_evaluation_array.py
modified:   3d_classification/ignite/densenet_evaluation_dict.py
modified:   3d_classification/ignite/densenet_training_array.py
modified:   3d_classification/ignite/densenet_training_dict.py
modified:   3d_classification/torch/densenet_evaluation_array.py
modified:   3d_classification/torch/densenet_evaluation_dict.py
modified:   3d_classification/torch/densenet_training_array.py
modified:   3d_classification/torch/densenet_training_dict.py
modified:   3d_segmentation/torch/unet_evaluation_dict.py
modified:   runexamples.sh

Fixes #297
Description
Fixed the following in the run examples.sh

change data_path = os.sep.join(["",  to data_path = os.sep.join([".", to use current dir instead of starting from the root
comment out modules_workload which is currently empty
make notebook (some) runnable on CPU by checking for GPU status

Status
Ready
Checks

[x] runexamples.sh

Hi @wyli ,
It looks good to me, just want to know whether it breaks cron tests.
Thanks.


Add data option for customizing loading address of highlight.js language styles.

Purpose
Previously it was fixed to load styles from cdnjs, now it allows custom loading address.
In fact, jsDelivr is the only one available public global CDN in Mainland China.
https://www.jsdelivr.com/network#china

@xxfye please can you confirm what is currently blocked for you in China - are the findings below what you experience?
❌ Blocked URLs

github.com (GitHub repositories all blocked)
fonts.googleapis.com

✅ Accessible URLs

wowchemy.com
cdnjs.cloudflare.com
https://app.netlify.com/start/deploy?repository=https://github.com/wowchemy/starter-hugo-online-course&stack=cms
https://academic-demo.netlify.app/
github.io (GitHub Pages)

Please clarify what the problem with CDNJS is that you experience? Is the issue that CDNJS is accessible but slower than you would like?

@gcushen Maybe I am too extreme, it is accurate to say that most of the websites can be accessed in mainland China. However, due to international bandwidth limitations and CDN servers not deployed in mainland China, they are actually very slow to the point that they cannot be used in production environments.

github.com ✅
fonts.googleapis.com ✅ (currently fast, cdn in mainland China. But I think it's unstable Google's service)
wowchemy.com ✅ (slow)
cdnjs.cloudflare.com ✅ (unstable)
https://app.netlify.com/start/deploy?repository=https://github.com/wowchemy/starter-hugo-online-course&stack=cms ✅ (slow)
https://academic-demo.netlify.app/ ✅ (slow)
github.io ✅ (slow)

@xxfye thanks for the feedback and contributing an improvement that can benefit all users in China!
Feel free to submit another PR to change the CDN for common assets like jQuery etc. to jsDelivr so that users in China don't need to make any modifications themselves.

This is my asstes file. I try not to change version and sri. I need more test.
# Versioning and Subresource Integrity (SRI) for Academic's JavaScript and CSS dependencies

# When updating the version of an asset below, please also update the corresponding SRI.
# How to update the SRI for an entry:
#   echo -n "sha512-" && curl --silent "https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.0/MathJax.js?config=TeX-AMS_CHTML" | openssl dgst -sha512 -binary | openssl enc -base64 -A
# Or, the SRI for the appropriate asset can be copied from https://cdnjs.com/ .

# JavaScript

[js.jQuery]
  version = "3.5.1"
  sri = "sha256-9/aliU8dGd2tb6OSsuzixeV4y/faTqgFtohetphbbj0="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/jquery/%s/jquery.min.js"
  url =<EMAIL_ADDRESS>[js.highlight]
  version = "10.2.0"
  sri = "sha512-TDKKr+IvoqZnPzc3l35hdjpHD0m+b2EC2SrLEgKDRWpxf2rFCxemkgvJ5kfU48ip+Y+m2XVKyOCD85ybtlZDmw=="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/highlight.js/%s/highlight.min.js"
  url = "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>[js.mathJax]
  version = "3"
  sri = ""  # No SRI as dynamically generated.
  url =<EMAIL_ADDRESS>  async = true
[js.isotope]
  version = "3.0.6"
  sri = "sha256-CBrpuqrMhXwcLLUd5tvQ4euBHCdh7wGlDfNz8vbu/iI="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/jquery.isotope/%s/isotope.pkgd.min.js"
  url =<EMAIL_ADDRESS>[js.imagesLoaded]
  version = "4.1.4"
  sri = "sha256-lqvxZrPLtfffUl2G/e7szqSvPBILGbwmsGE1MKlOi0Q="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/jquery.imagesloaded/%s/imagesloaded.pkgd.min.js"
  url =<EMAIL_ADDRESS>[js.gmaps]
  version = "0.4.25"
  sri = "sha256-7vjlAeb8OaTrCXZkCNun9djzuB2owUsaO72kXaFDBJs="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/gmaps.js/%s/gmaps.min.js"
  url =<EMAIL_ADDRESS>[js.leaflet]
  version = "1.7.1"
  # sri = "sha512-SeiQaaDh73yrb56sTW/RgVdi/mMqNeM2oBwubFHagc5BkixSpP1fvqF47mKzPGWYSSy4RwbBunrJBQ4Co8fRWA=="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/leaflet/%s/leaflet.min.js"
  sri = "sha256-BPfK9M5v34c2XP6p0cxVz1mUQLst0gTLk0mlc7kuodA="
  url =<EMAIL_ADDRESS>[js.fancybox]
  version = "3.5.7"
  sri = "sha256-yt2kYMy0w8AbtF89WXb2P1rfjcP/HTHLT7097U8Y5b8="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/fancybox/%s/jquery.fancybox.min.js"
  url = "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>[js.fuse]
  version = "3.2.1"
  sri = "sha256-VzgmKYmhsGNNN4Ph1kMW+BjoYJM2jV5i4IlFoeZA9XI="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/fuse.js/%s/fuse.min.js"
  url =<EMAIL_ADDRESS>[js.mark]
  version = "8.11.1"
  sri = "sha256-4HLtjeVgH0eIB3aZ9mLYF6E8oU5chNdjU6p6rrXpl9U="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/mark.js/%s/jquery.mark.min.js"
  url =<EMAIL_ADDRESS>[js.instantsearch]
  version = "2.10.2"
  sri = "sha256-gFCtPk/sonctyfwYOgjrPoWApQ0rqB6ezBBZ7p32yGc="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/instantsearch.js/%s/instantsearch.min.js"
  url =<EMAIL_ADDRESS>[js.anchor]
  version = "4.2.2"
  sri = "sha512-I7w3ZdSFzw5j3jU3ZkNikBNeIrl3i+hEuEdwNmqUJvwNcaBUNcijnP2gd9DtGlgVYDplfjGoD8vTNsID+lCjqg=="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/anchor-js/%s/anchor.min.js"
  url =<EMAIL_ADDRESS>[js.mermaid]
  version = "8.8.4"
  sri = "sha512-as1BF4+iHZ3BVO6LLDQ7zrbvTXM+c/1iZ1qII/c3c4L8Rn5tHLpFUtpaEtBNS92f+xGsCzsD7b62XP3XYap6oA=="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/mermaid/%s/mermaid.min.js"
  url =<EMAIL_ADDRESS>[js.cookieconsent]
  version = "3.1.1"
  sri = "sha256-5VhCqFam2Cn+yjw61zbBNrbHVJ6SRydPeKopYlngbiQ="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/%s/cookieconsent.min.js"
  url =<EMAIL_ADDRESS>[js.instantpage]
  version = "5.1.0"
  # sri = "sha512-1+qUtKoh9XZW7j+6LhRMAyOrgSQKenQ4mluTR+cvxXjP1Z54RxZuzstR/H9kgPXQsVB8IW7DMDFUJpzLjvhGSQ=="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/instant.page/%s/instantpage.min.js"
  sri = "sha256-DdSiNPR71ROAVMqT6NiHagLAtZv9EHeByYuVxygZM5g="
  url =<EMAIL_ADDRESS>[js.plotly]
  version = "1.55.2"
  sri = "sha512-gttPT9uTUiaLBj6XZdcB0ydKXiDaBwstInkN4Qvp1Nz3iwXNc8TTQplIEPIGxyJBDqERjwkKxf2OyO47/0EHbQ=="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/plotly.js/%s/plotly.min.js"
  url =<EMAIL_ADDRESS>
[js.highlight_lang]
  version = "10.2.0"
  sri = ""  # No SRI as highlight style is determined at run time.
  url = "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>
# CSS

[css.fontAwesome]
  version = "5.14.0"
  sri = "sha256-FMvZuGapsJLjouA6k7Eo2lusoAX9i0ShlWFG6qt7SLc="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/font-awesome/%s/css/all.min.css"
  url = "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>[css.academicons]
  version = "1.9.0"
  sri = "sha512-W4yqoT1+8NLkinBLBZko+dFB2ZbHsYLDdr50VElllRcNt2Q4/GSs6u71UHKxB7S6JEMCp5Ve4xjh3eGQl/HRvg=="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/academicons/%s/css/academicons.min.css"
  url =<EMAIL_ADDRESS>[css.leaflet]
  version = "1.7.1"
  sri = "sha512-1xoFisiGdy9nvho8EgXuXvnpR5GAMSjFwp40gSRE3NwdUdIMIKuPa7bqoUhLD0O/5tPNhteAsE5XyyMi5reQVA=="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/leaflet/%s/leaflet.min.css"
  url =<EMAIL_ADDRESS>[css.fancybox]
  version = "3.5.7"
  sri = "sha256-Vzbj7sDDS/woiFS3uNKo8eIuni59rjyNGtXfstRzStA="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/fancybox/%s/jquery.fancybox.min.css"
  url = "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>[css.instantsearch]
  version = "2.9.0"
  sri = "sha256-ZtmLe16p4jS4/2wPwwH6NzJt460SJzgLmhKrYo5yn7g="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/instantsearch.js/%s/instantsearch.min.css"
  url =<EMAIL_ADDRESS>[css.instantsearchTheme]
  version = "2.10.2"
  sri = "sha256-uL8LUd3zkI/lXvc/Hv/oOu8ld6RJcOZiUY/8c+I+3/o="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/instantsearch.js/%s/instantsearch-theme-algolia.min.css"
  url =<EMAIL_ADDRESS>[css.highlight]
  version = "10.2.0"
  sri = ""  # No SRI as highlight style is determined at run time.
  # url = "https://cdnjs.cloudflare.com/ajax/libs/highlight.js/%s/styles/%s.min.css"
  url = "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>[css.cookieconsent]
  version = "3.1.1"
  sri = "sha256-zQ0LblD/Af8vOppw18+2anxsuaz3pWYyVWi+bTvTH8Q="
  # url = "https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/%s/cookieconsent.min.css"
  url =<EMAIL_ADDRESS>


Childprocess.spawn is not a function

Childprocess.spawn is not a function. (In 'Childprocess.spawn(cmd, args, opt)', 'Childprocess.spawn' is undefined)

I have also same issue
TypeError: Childprocess.spawn is not a function. (In 'Childprocess.spawn(cmd, args, opt)', 'Childprocess.spawn' is undefined)

+1


Possible schema for the documentation of individual components

Hi @frisso! Thanks for your contribution! A minor comment, I think it may be less confusing to have this template in a different directory w.r.t. the actual documentation (e.g.; docs/templates/ instead of docs/design/)


chore(release): 2.0.0

2.0.0 (2020-11-14)
Bug Fixes

update packages (1489f83)
update packages (89ce677)
update packages (e5c32db)
update packages (16d4221)
update packages (1a38031)
update packages (1a123dc)
update packages (5741cf1)

Build System

.net 5.0 release (6053ac6)

Features

lazy loading (b632e78)
load initial configuration (13bf5af)
prerender app (ccf5040)

BREAKING CHANGES

.net 5.0 release

:white_check_mark: Build TheIdServer 2.0.0.build.891 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/7129130934 by @semantic-release-bot)


Support running consensus layer also on IPv6

SUMMARY

I would like to be able to configure consensus tendermint to listen on both IPv4 and/or IPv6.
Also to be able to specify both IPv4 and/or IPv6 as consensus external addresses at which the node
can be reached.
The configuration flags I'm referring to are
      --consensus.tendermint.core.external_address string                    tendermint address advertised to other nodes
      --consensus.tendermint.core.listen_address string                      tendermint core listen address (default "tcp://<IP_ADDRESS>:26656")

ISSUE TYPE

Feature Idea / improvement

COMPONENT NAME

I believe the component is tendermint though I can't be 100% sure.
ADDITIONAL INFORMATION

IPv4 are depleting and IPv6 is here to solve the issue and also improve Internet traffic.
Some providers are even charging a couple of bucks for an IPv4 address and give you the
choice to have only IPv6 on your server.
Sooner rather than later IPv6 will become mainstream and everybody is going to use it.
The worker already has this capability and uses IPv6 if present. See below an excerpt from
oasis-node registry node list -v of one consensus-rpc node I run.
  "tls": {
    "pub_key": "jRTuzzh5an8kVouUrJjHj+5NgDyngEwfVIQJXALlN3I=",
    "next_pub_key": "l88tNlZDV5vgB1dT/QUk39766n9o33TWW5udwWuOO6M=",
    "addresses": [
      "jRTuzzh5an8kVouUrJjHj+5NgDyngEwfVIQJXALlN3I=@<IP_ADDRESS>:9100",
      "l88tNlZDV5vgB1dT/QUk39766n9o33TWW5udwWuOO6M=@<IP_ADDRESS>:9100",
      "jRTuzzh5an8kVouUrJjHj+5NgDyngEwfVIQJXALlN3I=@[2407:3640:2066:7619::1]:9100",
      "l88tNlZDV5vgB1dT/QUk39766n9o33TWW5udwWuOO6M=@[2407:3640:2066:7619::1]:9100"
    ]
  },

Seems there's also an issue opened on tendermint about this. Hmm, I guess this won't be possible until tendermint implements it. I'll leave it here as reference https://github.com/tendermint/tendermint/issues/2317


FreeBSD support

As written above. The method of obtaining uptime is the same in FreeBSD as in Darwin, so this is a easy fix to show uptime in FreeBSD.

Hello @pianojockl 👋
I can't merge your PR as is and I don't want to rewrite your master branch.
From there I see 2 ways forward:

I decline the PR and make the changes myself
You rewrite your master branch to only have 2 commits on top of my master branch:

made _loadavg() support FreeBSD

made _uptime() support FreeBSD