does anyone have a good recipe for installing on a2 hosting

I have been trying for 3 days without success to install to shared hosting account.
I have to use fcgi, with .htaccess
Problem is I cant seem to get anything working. all install steps go ok without error, but I can not view anything after install or access admin pages.
I need a basic tutorial for noob.

Hi @tcampion64 - please use the Wagtail tag on Stack Overflow for support queries. (Note that you'll need to give full details of what you've tried so far, and where it's failing)

have been trying for 3 days without success to install to shared hosting account.
I have to use wcgi, with .htaccess
Problem is I can't seem to get anything working. all install steps go ok without error, but I can not view anything after install or access admin pages.
I need a basic tutorial for noob.

@bardaguera Please use the Wagtail tag on Stack Overflow for support queries.


Fix broken url in docs

Summary
Easy navigation and easy reading for others

You are welcome 😌
On Wed, 20 Jan 2021, 9:36 am Andres Martinez Gotor, <
<EMAIL_ADDRESS>wrote:

@andresmgot approved this pull request.
Thanks for the PR!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubeless/kubeless/pull/1216#pullrequestreview-571976089,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3GBNQFUT2B3WH6WQINOS3S22IYVANCNFSM4WJHI5OA
.

You are welcome 😌
On Wed, 20 Jan 2021, 9:36 am Andres Martinez Gotor, <
<EMAIL_ADDRESS>wrote:

@andresmgot approved this pull request.
Thanks for the PR!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubeless/kubeless/pull/1216#pullrequestreview-571976089,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3GBNQFUT2B3WH6WQINOS3S22IYVANCNFSM4WJHI5OA
.


text and assets for the section technologies

Section on technologies used in Websight
Description
Text and assets ilustrating WS technology stack.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue) labeled with bug
[x] New feature (non-breaking change which adds functionality) labeled with enhancement
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code standards of this project.
[ ] My change requires updating the documentation. I have updated the documentation accordingly.

It's going to be addressed with Markdown in a separate PR.


Fix: Specify securityContext.

:bug: Specify a best-practices securityContext for each of the ingress/dispatcher pods we spin up alongside user workloads.
This popped out poking around in the new GKE security posture dashboard
/kind bug
Release Note
Have ingress/dispatcher specify a more restrictive securityContext

Docs
NONE

/lgtm

Failure doesn't look related to my change, but I can't easily rerun.

cc @evankanderson
This is in the same vein as the Serving change FYI.  Not sure who the best folks to ping on Rabbit are these days?

@mattmoor yo can ping me or @gab-satchi :) thanks for the change we'll review it next week

@gabo1208 perfect!  No rush, thanks! 🙏

/retest

FWIW, I'd love to get this into the release tomorrow, so we can pick it up and quiet some security alerts 🤞 🙏

/retest

oh nice, that works for actions now :)


where is your code?

your paper is novel, but where is the code?

We are organizing the code and will release soon.

@sion-zcfei Thanks for reply, I'm looking forward to it.

@sion-zcfei The idea of using graph in decoding is interesting. Would you provide the code? Thank you.


mWeb -Chat - Weird behavior with 3D Touch on chat screen

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:
A context menu should open without issues
Actual Result:
Context menu opens with blue flashing or opens with overlapping white background
Action Performed:

Navigate to https://staging.expensify.cash/
Login with existing account
Open any chat
Long press on any message

Workaround:
Unknown
Platform:
Where is this issue occurring?
Web
iOS
Android
Desktop App
Mobile Web ✔
Version Number: 1.0.38-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:  Issue occurs inconsistently (3/5) in iOS (iPhone 12 Pro - iOS 14.4)
Expensify/Expensify Issue URL:
https://user-images.githubusercontent.com/43996225/117212784-c7146880-adc8-11eb-88a9-e3a156d2af9c.mp4

View all open jobs on Upwork

Triggered auto assignment to @laurenreidexpensify (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

I can't replicate this on Android mWeb - gonna see if anyone can replicate on iOS and confirm.

@conorpendergrast if you can repro on iOS let me know! thanks

Reproduced on iOS, through Chrome and Safari.
Specifically, after I do a force-touch on a message, the clipboard icon is selected:

Thanks sending for Engineering Triage, who can then apply the External label

Triggered auto assignment to @tgolen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Looks like a complete issue to me. I'll send to external

Triggered auto assignment to @JmillsExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Thanks! Still waiting on proposals in Upwork.

Issue reproducible during today's KI retests

Issue reproducible today during KI retests

I'm just coming back from vacation. I'll update the Upwork post since we're not getting any proposals.

Issue reproducible today during KI retests

Still no takers in Upwork. Increased the payout to see if we get any takers.

Issue not reproducible during KI retests (First week)

Going to keep the Upwork job open while we wait and see if this is not reproducible again.

Triggered auto assignment to @marcaaron (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@marcaaron I am going to be going OOO for the next 10 days, so I reassigned this using the exported chore. Thanks for taking over for me!

Still waiting for proposals here.

Proposal
ISSUE
As per my understanding, this issue is due to the fact that text is selectable on a Web browser. Also, IOS has 3d touch.
Solution

We should make the menu Item including Icon non-selectable on the Context Menu for all platforms as I think no body would want to select the text on context menu.
Now we should make text non-selectable for message on Mobile devices and M-web. also for touch devices which are not web. For this can check of isSmallScreenWidth or canUseTouchScreen is true but we should also check the User-agent string as Few laptops could have touch screen as well on web.

This will remove the blue screens while long press.
Disabling the text selection for tablets or Ipads is also important which will be covered by canUseTouchScreen and UA string checking.
On mobile devices text message will be copied via our Copy to clipboard feature.
I don't recommend disablling 3d or haptic touch which can be done via preventDefault() on touchforcechange event. This featue decides the long-press and other unique behaviours to IOS users.
Text selection can be disable using selectable=false on Text and for icons, wrapping them in Text.

Issue reproducible today during KI retests.

We should make the menu Item including Icon non-selectable on the Context Menu for all platforms as I think nobody would want to select the text on the context menu.

This seems reasonable.

Now we should make text non-selectable for messages on Mobile devices and M-web. also for touch devices that are not web. For this, we can check if isSmallScreenWidth or canUseTouchScreen is true but we should also check the User-agent string as Few laptops could have touch screens as well on the web.

Not sure I would go this far. Why should we not be able to select only some portion of text natively? Probably the behavior should be consistent on all platforms.
Another solution could be to just clear any document selection when the menu mounts.
e.g. with https://developer.mozilla.org/en-US/docs/Web/API/Selection/removeAllRanges

Yeah. Awesome. :+1: Didn't think of it that way. Actually, there has been discussion around making text non-selectable on mobile devices.
but yeah I agree. Makes perfect sense if the issue is only producible on M-web.

Now we should make text non-selectable for messages on Mobile devices and M-web. also for touch devices that are not web. For this, we can check if isSmallScreenWidth or canUseTouchScreen is true but we should also check the User-agent string as Few laptops could have touch screens as well on the web.

But we only want to clear the selection for the above. Web needs selection.

Actually, there has been discussion around making text non-selectable on mobile devices.

Sorry I don't have much context about that.

But we only want to clear the selection for the above. Web needs selection

Maybe just do it for all small screens? Anyways, not sure if it's the best idea just one idea :)

It's worth trying and I believe it will work just fine but there could be a catch I have seen that sometimes the menu does not even open which is blocked by text selection. There seems to be an open issue to that https://github.com/Expensify/Expensify.cash/issues/2279

Issue reproducible today during KI retests.

@JmillsExpensify @parasharrajat is the only one who proposed a solution on this one so I think we can move forward.

Oh great, thanks for the clarity! @parasharrajat you want to apply for this one on Upwork and I can hire you?

@JmillsExpensify Done.

Hired! Thank you

Waiting for update on https://github.com/Expensify/Expensify.cash/issues/2279.

Issue reproducible during KI retests.

Issue reproducible during KI retests.

Sorry for delay here. Working on the PR today.

Issue reproducible during KI retests

Waiting on QA/deploy. Then'll I'll update for payment/regressions hold.


Top collector

Closes #388

Overall that looks good! There is a bit of PR stack. Let me come back to you later this week.

The build is failing but it looks like the master is already failing?

@pentlander You are right my bad. Fixing it.


Create nodes needed for example

Example
{% if name != "OFF" %}
  my name is {{ name }}
{% endif %}
{{ 5 + 1 }}

Nodes needed for parsing for given example must be implemented.

#15 adds bare nodes definitions, but it'll have to be revisited during runtime implementation


[bug] Can't resolve '@testing-library/jest-dom/matchers'

Describe the bug
In their latest versions, @storybook/testing-library and @storybook/jest give me the following error:
Module not found: Error: Can't resolve '@testing-library/jest-dom/matchers' in '/path/to/node_modules/@storybook/jest/dist'
Did you mean 'matchers.js'?
BREAKING CHANGE: The request '@testing-library/jest-dom/matchers' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

I also have installed the following related packages:
"@testing-library/jest-dom": "^6.0.1"
"@testing-library/react": "^14.0.0"

To Reproduce
Steps to reproduce the behavior:

Install Storybook along with @storybook/testing-library and @storybook/jest
Run Storybook

System
  System:
    OS: macOS 13.3
    CPU: (8) arm64 Apple M2
  Binaries:
    Node: 20.4.0 - ~/.nvm/versions/node/v20.4.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.7.2 - ~/.nvm/versions/node/v20.4.0/bin/npm
  Browsers:
    Chrome: 116.0.5845.96
    Edge: 114.0.1823.55
    Safari: 16.4
  npmPackages:
    @storybook/addon-a11y: ^7.3.2 => 7.3.2
    @storybook/addon-coverage: ^0.0.9 => 0.0.9
    @storybook/addon-essentials: ^7.3.2 => 7.3.2
    @storybook/addon-interactions: ^7.3.2 => 7.3.2
    @storybook/addon-links: ^7.3.2 => 7.3.2
    @storybook/addon-styling: ^1.3.6 => 1.3.6
    @storybook/addon-viewport: ^7.3.2 => 7.3.2
    @storybook/blocks: ^7.3.2 => 7.3.2
    @storybook/jest: ^0.2.1 => 0.2.1
    @storybook/node-logger: ^7.3.2 => 7.3.2
    @storybook/preset-create-react-app: ^7.3.2 => 7.3.2
    @storybook/react: ^7.3.2 => 7.3.2
    @storybook/react-webpack5: ^7.3.2 => 7.3.2
    @storybook/test-runner: ^0.13.0 => 0.13.0
    @storybook/testing-library: ^0.2.0 => 0.2.0

I am using "@testing-library/jest-dom: ^5.17.0" and having the same problem.
The workaround I have found is to downgrade the version to<EMAIL_ADDRESS>  "devDependencies": {
    "@storybook/addon-actions": "^7.3.2",
    "@storybook/addon-essentials": "^7.3.2",
    "@storybook/addon-interactions": "^7.3.2",
    "@storybook/addon-links": "^7.3.2",
    "@storybook/react": "^7.3.2",
    "@storybook/react-webpack5": "^7.3.2",
    "@storybook/testing-library": "^0.2.1",
    "@testing-library/jest-dom": "^5.17.0",
    "@testing-library/react": "^12.1.5",
    "@testing-library/user-event": "^14.4.3",
}

Could one of you make a reproduction, perhaps using https://storybook.new?

I think my case is related to this issue.
When running test-storybook, all tests crash with the error TypeError: expect.extend: 'default' is not a valid matcher. Must be a function, is "object".
Downgrade to "@storybook/jest": "^0.2.1" solve the problem

A reproduction would be very helpful to find out what is happening here.

It looks like so far everyone with this error is using the react-webpack5 builder.  I'm using vite, which might be why I don't see this error.  Does webpack require fully-specified imports (i.e. extensions must be included)?  Does it not support package.json exports maps?

@YTakahashii Yes<EMAIL_ADDRESS>uses jest-dom 6.  So, you could either update your own jest-dom, or you'll need to stay with the older storybook/jest package.

Hey everyone! In Storybook 8, this package functionality has been integrated to a new package called @storybook/test, which uses Vitest APIs for an improved experience. This issue should be solved or maybe it's not applicable anymore.
When upgrading to Storybook 8 with npx storybook@latest upgrade, you will get prompted and will get an automigration for the new package. Please migrate when you can! Thanks a lot <3


Refactor for OutputableBndrId changes

See https://gitlab.haskell.org/ghc/ghc/merge_requests/2010.

https://gitlab.haskell.org/ghc/ghc/merge_requests/2010 is green now.


Fix project renaming issues - renaming project can leave global config with two projects

Describe the bug
if you rename your project ddev seems to ad a new entry for the same project over and over again
Updated: If you edit an existing configured project and change its name, ddev will let you start that; it shouldn't, just as it doesn't allow the same name to be used.
To Reproduce
Steps to reproduce the behavior:

create a new project ddev config everything default
run the following script (to change the project name multiple times)

#!/usr/bin/env bash

# enable error reporting and show executed commands
set -ex

changename()
{
  # stop to have a clean state
  ddev stop
  # reconfigure project name
  echo "name: $1" > .ddev/config.site.yaml
  # restart the project with the new name
  ddev start;
}

changename "foo-example"
changename "bar-example"
changename "foo-example"
changename "bar-example"

3 ddev list shows somthing like
bar-example             php    C:/src/ddev-namechange         https://bar-example.ddev.site     running
bar-example             php    C:/src/ddev-namechange         https://bar-example.ddev.site     running
bar-example             php    C:/src/ddev-namechange         https://bar-example.ddev.site     running

Expected behavior
ddev should not dublicate the project every time it is renamed.
Version and configuration information (please complete the following information):

Windows 10 (19.17763 Build 17763)
Docker
docker version
Client: Docker Engine - Community
Version:           19.03.4
API version:       1.40
Go version:        go1.12.10
Git commit:        9013bf5
Built:             Thu Oct 17 23:44:48 2019
OS/Arch:           windows/amd64
Experimental:      false

Server: Docker Engine - Community
Engine:
Version:          19.03.4
API version:      1.40 (minimum version 1.12)
Go version:       go1.12.10
Git commit:       9013bf5
Built:            Thu Oct 17 23:50:38 2019
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          v1.2.10
GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version:          1.0.0-rc8+dev
GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version:          0.18.0
GitCommit:        fec3683

ddev  v1.11.2
config.yaml contents for the misbehaving project

APIVersion: v1.11.2
name: foo-bar
type: php
docroot: ""
php_version: "7.2"
webserver_type: nginx-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
mariadb_version: "10.2"
nfs_mount_enabled: false
provider: default
use_dns_when_possible: true
timezone: ""

just the config.site.yaml which is generated by the above script.

Additional context
we have a Polymorph Project (one project we use to deploy multiple sites). we rename the project so docker keeps the old container data an we are able to fast-switch between different sites.

I can confirm this issue, can replicate it as per the issue description, but initially encountered it when adding the same hostname twice by mistake.
An addition to this issue is that once I've removed the duplicated hostnames, it continues to appear multiple times in ddev list both when the project is stopped and started.

Could you folks please provide the contents of the project_info stanza of ~/.ddev/global_config.yaml when this happens? Thanks.
@wolffc I expect that your polymorph project does violate the concept of unique project names on the machine... There can be only one ddev project of a given name on a machine.

@rfay I'm not sure what you mean, I do not have any global_config.yaml inside my .ddev directory, I assume it's just the default config.yaml that is initially generated by DDEV.
If that is the case, this is mine
APIVersion: v1.11.2
name: foo-bar
type: drupal8
docroot: web
php_version: "7.2"
webserver_type: nginx-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
project_tld: dk.localhost
additional_hostnames: []
additional_fqdns: []
mariadb_version: "10.2"
nfs_mount_enabled: false
provider: default
use_dns_when_possible: false
timezone: "Europe/Copenhagen"

This is a clean installed test project (Drupal in my case). The only changes was to add timezone, turn off use dns and add a custom
I haven't been able to replicate it again manually, only using the bash script mentioned in the issue description. Though that changes the name, while I encountered it initially when changing the additional_hostnames, this has stopped happening.
I still have the initial project that I encountered it on showing up twice when I do ddev list even though it's stopped and I have no other projects with it's name. (I would like to share it, but the name could be a giveaway on what the project is about and I'm not sure I'm allowed to publicly share that).
To me it seems like the old project names aren't properly removed, as both my initial project that I encountered it on and the one I tested with here, appear several times in ddev list even after they have been stopped and the project removed (it only removed one of them from the list, not all).
To summarise:

Am unable to replicate the original way I encountered this issue (by having an additional hostname with the same name as project)
Replicating it using the bash script in issue description does indeed replicate the issue.
Using ddev stop --remove-data properly removes one of the entries from ddev list but the rest are still left on the list.

I hope this information helps.

I just re-read your comment @rfay and saw that you're referencing the .ddev directory in my user directory :) my bad.
I would like to share it, but it contains even more references to projects that I cannot share, so I have removed them from the file, one of them was the one where I encountered the issue initially.
APIVersion: v1.11.2
omit_containers: []
instrumentation_opt_in: false
router_bind_all_interfaces: false
last_used_version: v1.11.2
mkcert_caroot: /Users/dsj/Library/Application Support/mkcert
project_info:
  donationform:
    approot: /Users/dsj/Projects/Repositories/donationform
  foo-bar:
    approot: /Users/dsj/Projects/Repositories/foo-bar
  foo-example:
    approot: /Users/dsj/Projects/Repositories/foo-bar
  graloth:
    approot: /Users/dsj/Projects/Repositories/graloth

# You can turn off usage of the dba (phpmyadmin) container and/or
# ddev-ssh-agent containers with
# omit_containers[\"dba\", \"ddev-ssh-agent\"]
# and you can opt in or out of sending instrumentation the ddev developers with
# instrumentation_opt_in: true # or false
#
# instrumentation_user: <your_username> # can be used to give ddev specific info about who you are
# developer_mode: true # (defaults to false) is not used widely at this time.
# router_bind_all_interfaces: false  # (defaults to false)
#    If true, ddev-router will bind http/s, PHPMyAdmin, and MailHog ports on all
#    network interfaces instead of just localhost, so others on your local network can
#    access those ports. Note that this exposes the PHPMyAdmin and MailHog ports as well, which
#    can be a major security issue, so choose wisely. Consider omit_containers[dba] to avoid
#    exposing PHPMyAdmin.

What I did notice was that the initial project I had showing double, was because when I generated the config for the project it took the folder name as project name and I changed that afterwards (while messing with the additional hostnames), I think that might have caused my initial issue, since it appeared twice in the file above, one with the folder name and one with the actual project name.

That would definitely do it. ddev does try its best to prevent this, but that definitely causes the behavior.

same here:
APIVersion: v1.11.2
omit_containers: []
instrumentation_opt_in: true
router_bind_all_interfaces: false
last_used_version: v1.6.0
mkcert_caroot: C:\Users\cwolff\AppData\Local\mkcert
project_info:
  autotranslator-console:
    approot: C:\src\autotranslator-console
  bar-example:
    approot: C:\src\ddev-namechange
  cockpit-aer-de:
    approot: C:\src\ddev-cockpit
  cockpit-best-de:
    approot: C:\src\ddev-cockpit
  cockpit-conso-de:
    approot: C:\src\ddev-cockpit
  cockpit-dtt-de:
    approot: C:\src\ddev-cockpit
  cockpit-picasso-com:
    approot: C:\src\ddev-cockpit
  foo-bar:
    approot: C:\src\ddev-namechange
  foo-example:
    approot: C:\src\ddev-namechange

cockpit-* are my initial polymorph project while foo/bar are the test project from above

I see you've been using the same directory for multiple projects. It may be that ddev's defensive work is all about preventing the same project name from being reused, but it's not defensive about having the same directory reused. Simple workaround of course: Delete project before renaming it.

actuall ddev delete is not wat we want.
we have a typo3 project which is is deployed to 13 servers sytems. (all the same code base)
this project includes mutliple services. for each system 4 addtional db container,  solr, beanstalkd.. etc.
what we want is a fast way to switch from site A to B while. this includes restoring the data of the services if present. changing the project names gives us the ability (because the containers get different names)
as a workaround our "switch-site script" now uses ddev stop --unlist to stop the project list from ever growing but avoding deltetion of the project data.

I think you'd be better off with projects of different names, I guess I don't completely understand your use-case. I'd recommend having projects (and probably repos) that have different names.
One thing that might be useful (not sure) if you have to do this is a "config.name.yaml" which just has name: <specialnamehere>, then you could overwrite the name without changing the config.yaml

our project setup is like this:

1x Codebase which deploys ~ 15 websites different companies
15 Development DB dumps (nightly, scrubbed from userdata)
additional every DB needs an an indipentend set of Services.  so website 1 does not use the solr core of website 2 etc..
we have a switch-site script which activates the Correct Configuration set.

but as the configuration contains references to ID values of database reccords we can only use the Config set with the correct database.
as a developer I don't want to dublicate the same git repository 15 times. to have a working test setup. thats why we create a script "switches from one site to another"
we do so by using the some "features" of ddev. if we change the project name, ddev creates containers with the site name in it. (which is great because wie dont have to deal with the process of backing up a project state. but rather say ddev stop && change name && dev start and ddev will start up with a set of independant containers. so ddev actually works great for that purporse.
and the dublication of "project names" in global_config.yaml is just a minor issue for us. overall the workflow seems to be working very well.
and to focus on the Project name issue:
i think the following rules would make sense for ddev to enforce:
a) you are not allows to use the same project name twice
b) you can only have one project per path. (unless ddev supports this)
so if i change the project name i would exprect ddev on ddev start to look if there are other proejct defined for this path, and remove non matching from global_config.yaml

Thanks for explaining that. Pretty fancy! I imagine you'll be able to get things to work by using ddev stop --unlist at the right place, etc.
ddev already tries really hard to enforce "you are not allows to use the same project name twice", but I think not hard enough to enforce "you can only have one project per path"

I've experienced the duplicate project name phenomenon as well, a little differently. I've created a project the regular way with ddev config, started it and worked with it for a while, then realized I had a typo in the name.  So I update it, ddev restart, and everything looks fine until I ddev list and see that there are now two projects with apparently the same name.
The global config file has the two projects listed with the same approot, but different names.  The tricky thing is that ddev list shows the directory name in its NAME column instead of the configured project name. Once I found that I could get the project name from the global config file and ddev delete <duplicate_project>, everything was fine.

I see two things that might be more defensive about this:

ddev start should refuse to start if the name is different and the directory is already in use. That will prevent most of these. In the error message it should hint the removal technique (ddev stop --unlist <projectname>)
ddev list can maybe show the actual name shown in global_config.yaml (as the key) instead of the name in the container label.  That would make it less confusing.
Review the errors that get shown on duplicate name, so they provide info on how to work around (ddev stop --unlist)


Dedicated scheduler

Hi folks,
I'm working on making it easier for our users to make use of our cluster (Stratus).  Stratus is a traditional cluster with a shared login node and several compute nodes. Aside from that, we have a node setup hosting Jupyterhub/lab which is configured as a submit host (qsub test.pbs can be ran in the Jupyter terminal to submit a job).
Our original intended work flow was that users could develop their algorithm in Jupyter using a subset of our data, then stage the full dataset to LUSTRE and submit their nbconverted script to the cluster all without leaving their browser.
I'd like to take that a step further and keep an active Dask scheduler running all the time so that our users can just connect a client through their notebook and submit tasks, but we can also leverage that same scheduler for operational and infrastructure tasks (we do a lot of processing to produce datasets).
This feels like I could just create a systemd service on the Jupyter host which maintains the scheduler, then users would skip creating the scheduler in their notebook and connect directly to the existing scheduler to run their tasks.
What am I missing?

That's definitely possible, and is a workflow used by some groups.  We've found that it's a bit more common for people to want to start up their own scheduler though.  There are some challenges to using a global scheduler:

Software versions need to match, and users tend to want to use non-uniform versions of various libraries
Multi-tenancy, some users may hog resources, so it's nice to engage the resource manager when making separate clusters

The workflow that we've seen become common is to use this library, dask-jobqueue, to create your own dask cluster.
from dask_jobqueue import PBSCluster
cluster = PBSCluster()
cluster.scale(100)  # ask for 100 workers

from dask.distributed import client
client = Client(cluster)

This does force them to create their own scheduler (within the Cluster object) but this doesn't seem to be an onerous task or tripping point for most users.
You could still use your central dask scheduler for infrastructural tasks, you just become a peer to all the rest of the users.
But as I said, both models have been used by different groups.

Ahh, I think I've made some bad assumptions about the ecosystem. So its ok to have more than one scheduler running for the same HPC cluster?
Software versions will be less of a problem for us specifically as we'll have fairly good control of what is available and make liberal use of conda envs and cross mounting.
Multi-tenancy is something we're still feeling out with respect to Dask. If I got my way, it'd be all Dask all the time, but as is some users are still going to want to use traditional PBS/qsub.
I think our ideal scenario would be setting the Dask scheduler adaptive and letting it scale down to 0 when unused, or up to the whole ~4k cores if available.

Ahh, I think I've made some bad assumptions about the ecosystem. So its ok to have more than one scheduler running for the same HPC cluster?

Definitely.  It's common for each user to run their own dask scheduler.  These can be temporary and ephemeral.

Software versions will be less of a problem for us specifically as we'll have fairly good control of what is available and make liberal use of conda envs and cross mounting.

Right, but your users might also want to do this.  Different users might want to use scikit-learn version 0.19 and 0.20.  A single dask cluster must have uniform versioning, so these two users can't use the same.  It typically makes sense for each user to create their own ephemeral cluster.  This should only take a few seconds if the queue allows small jobs through.

Multi-tenancy is something we're still feeling out with respect to Dask. If I got my way, it'd be all Dask all the time, but as is some users are still going to want to use traditional PBS/qsub.

To be clear, these aren't mutually exclusive.  Typically people launch dask workers through PBS/qsub.

I think our ideal scenario would be setting the Dask scheduler adaptive and letting it scale down to 0 when unused, or up to the whole ~4k cores if available.

Yup, users can also do this on their own, using PBS/qsub to manage resources.

@bstrdsmkr do you still have questions on this topic? Has @mrocklin answered to your need?


onConferenceTerminated  not getting triggered on iOS

onClosed gets triggered but onConferenceTerminated does not when disconnecting the call

I can not reproduce this issue. Please add some steps on how to reproduce.

@saibotma Same problem here.
I am just joining a meet and when pressing the hang-up button, the trigger doesn't fire.

@efraespada Can you add the sample code please.

@saibotma
 await JitsiMeetWrapper.joinMeeting(
      options: JitsiMeetingOptions(
        roomNameOrUrl: url,
        subject: subject,
        token: token,
        isAudioOnly: !video,
        isAudioMuted: false,
        isVideoMuted: false,
        featureFlags: {
          FeatureFlag.isCallIntegrationEnabled: false,
          FeatureFlag.isInviteEnabled: false,
          FeatureFlag.isChatEnabled: false,
          FeatureFlag.isWelcomePageEnabled: false,
          FeatureFlag.isCalendarEnabled: false,
          FeatureFlag.areSecurityOptionsEnabled: false,
        },
      ),
      listener: JitsiMeetingListener(
        onConferenceWillJoin: (url) => print('onConferenceWillJoin: url: $url'),
        onConferenceJoined: (url) async {
          print('onConferenceJoined: url: $url');
        },
        onConferenceTerminated: (url, error) async {
          print('onConferenceTerminated: url: $url, error: $error'); // never called
        },
      ),
    );

Can reproduce the issue. Happens on both iOS and Android.
There exists an issue in the official SDK: https://github.com/jitsi/jitsi-meet/issues/11379


Open up token audience for authentication

While looking at that source code in the old runtime over here, I found that we pass the tokenAudience if provided otherwise environment.activeDirectoryResourceId as the resource to acquireTokenWithDeviceCode and acquireUserCode. I did not see that part being ported over.

Another issue that is tangential to the problem you are solving  was reported  in ms-rest-azure. adal-node would intermittently send an error autorization_pending and the work around was to trap that error, wait for sometime and try again till the error goes away. This was fixed over here in ms-rest-azure. Is it possible for you to patch this as well, while you are improving the interactive login auth experience in this library. It would greatly benefit everyone and all issues pertaining to auth will be resolved. If you think, it will take too much time, then that is totally fine as well. Thanks for taking time and sending a PR 👍

THANK YOU @alexeldeib!

I see. Then just having graph | batch | string | undefined would work

Actually, I think something weirder is happening. The compiler uses TokenAudience on the non-abstract implementations of TokenCredentialsBase, but it doesn't want to use accept TokenAudience type on the abstract base class?
Might be something weird on my machine/locally; happy to leave it whichever way you prefer, since it doesn't seem like there's an inherent issue.

Referencing this PR https://github.com/Azure/ms-rest-azure-env/pull/2 as it is related to this change.
@alexeldeib - Please update the min version for ms-rest-azure-env dependency to "^0.1.1"

@amarzavery thanks in return for the quick turnaround! Glad I could contribute 😄


⚠ Bofrost.at has degraded performance

In c8112cc, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1792 ms

Resolved: Bofrost.at performance has improved in e8dd870 after 7 minutes.


support 'access_token' for compatibility with OAuth 2.0  https://docs…

….docker.com/registry/spec/auth/token/#requesting-a-token

thanks!

do you know what registries use this protocol would be nice to have it documented somewhere :)

I think Azure Container Registries? Currently I get this when using reg with ACR:
$ reg ls our-registry.azurecr.io
Get https://our-registry.azurecr.io/v2/: unknown field in challege header error: Bearer realm="https://our-registry.azurecr.io/oauth2/token",service="our-registry.azurecr.io",error="malformed_token"

Although, this PR seems to have access_token, while my .docker/config.json has identitytoken. So maybe not?

thanks!


Update gRPC load balancing sample

Docs updated for new API.
PR is waiting for next gRPC package to be published with the new API.

https://github.com/MohammadAsadi1372/MohammadAsadi.MasterService


Incorrect coverage report in 13.x and 14.x

I try to get the test coverage from a more or less large Typescript project by using nyc. Nearly all my TypeScript files will have their own test files with many test cases.
In my option all this files should be covered by nyc. I try a lot with different nyc configurations and different versions of how to execute the test files.
At the beginning I start with a configuration where single files (which actually should have tests) will not appear in the coverage report. I could fix this issue by requiring "ts-node/register" and "source-map-support/register" to the nyc configuration. Now all files are listed in the coverage report but nyc think that there are no fitting tests.

I do not have any idea why this tests should not be covered. I try to reproduce it in a new bug-demo project but their, everything works well.
Troubleshooting steps

[x] still occurrring when I put cache: false in my nyc config
[x] setting tsconfig sourceMap: true makes no difference
[x] set the typescript target to es6 makes no difference
[x] execute tests with node, ts-node or jasmine-ts makes no difference
[x] still occurrring when i only use exclude without include in my nyc config
[x] using @istanbuljs/nyc-config-typescript makes no difference
[x] using "ts-node/register/transpile-only" instead of "ts-node/register" will not work (it throws
a "Cannot read property 'loc' of undefined" exception, see screenshot-2)

Environment Information
npx envinfo@latest --preset nyc
npx: Installierte 1 in 1.93s

  System:
    OS: macOS Mojave 10.14.4
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
    Memory: 130.55 MB / 16.00 GB
  Binaries:
    Node: 10.9.0 - ~/.nvm/versions/node/v10.9.0/bin/node
    npm: 6.2.0 - ~/.nvm/versions/node/v10.9.0/bin/npm
  npmPackages:
    nyc: ^14.1.0 => 14.1.0
    source-map-support: ^0.5.12 => 0.5.12
    ts-node: ^8.1.0 => 8.1.0
    typescript: ^2.9.2 => 2.9.2

---
Jasmine: 2.99.0

NYC Configuration
"nyc": {
    "cache": false,
    "all": true,
    "sourceMap": true,
    "instrument": true,
    "exclude-after-remap": false,
    "extension": [
      ".ts"
    ],
    "check-coverage": true,
    "require": [
      "ts-node/register",
      "source-map-support/register"
    ],
    "include": [
      "app"
    ],
    "reporter": [
      "lcov",
      "text",
      "html"
    ],
    "exclude": [
      "**/*.d.ts",
      "coverage/**",
      "js/**",
      "builds/**",
      "config/**",
      "**/spec/**",
      "**/*.spec.ts",
      "**/node_modules/**",
      "gulpfile.js",
      "dummy-start.ts"
    ]
  },

screenshot-2

Can you provide a link to your repo or a minimal reproduction? Also can you follow the instructions here: https://npm.im/@istanbuljs/nyc-config-typescript and see if that fixes your issue?

Also finding this on many TS projects too, have had to revert to 13.* for now.

We are having the same problem in webhint. This was working fine with 13.3.0 😞

Thank you for the really quick replay! I already tried @istanbuljs/nyc-config-typescript but it makes no differences. Depending on @istanbuljs/nyc-config-typescript I create my own nyc config like shown in the Issue. So the @istanbuljs/nyc-config-typescript don't work for me :-(
I already tried to revert to 13.* but the issue still occurs in my project.
Unfortunately, I can't reproduce this issue in a new demo project.

I have several examples of PRs I've made that simplify the nyc configuration in most projects with nyc-config-typescript... without a demo repository there's not much more help I can provide you other than suggesting you remove all the config you have and follow the instructions closely.

@molant upon reviewing the webhint repo, it appears that it makes automatic upgrades without much review, so I think your claim of a regression might just be due to a breaking change between major versions (likely to do with the --exclude-after-remap flag).
Please read the changelog and the new documentation closely. Like I suggested for OP, I would recommend resetting your config entirely and starting with the preset that is appropriate for your project. As maintainers we don't have the time to painstakingly investigate every repo like this, so we have been making a more concerted effort to update our documentation to support everyone.

@JaKXz put together a sample where nyc is failing to generate coverage:
https://github.com/Codex-/nyc-bug
nyc is only run on *.js files, no middle layers like ts-node etc.
Steps to run

npm i
npm run build
npm run test

Test simply executes: nyc --reporter=lcov --reporter=html mocha where mocha is configured to only run *.test.js files.
Output
13.3.0 lcov.info:
TN:
SF:C:\Dev\p\nyc-bug\src\index.ts
FN:1,testFunc
FNF:1
FNH:1
FNDA:1,testFunc
DA:1,1
DA:2,1
LF:2
LH:2
BRF:0
BRH:0
end_of_record

14.1.0 lcov.info
Empty

It works for me if I use the extension option from here:
https://github.com/istanbuljs/nyc#common-configuration-options
Default is just '.js' so u have to add '.ts' also
Like
nyc --reporter='lcov' --extension='.ts' mocha
or
"nyc": {
    ...
    "extension": [
        ".ts"
    ],
    ...
}

@maleeb thanks for testing / responding.
The original poster of this issue has stated that downgrading to 13.x did not fix the issue, so all problems caused by upgrade to 14.x are off topic on this ticket.  @Codex- please follow the suggestion from @maleeb (click Show Comment to see it).
All comments not related to OP's issue are hidden as off topic so it's easier to find information relevant to this specific issue.  Unless your issue can be reproduced on 13.x or you have advice for that specific issue please do not post any further comments to this ticket, please open a new ticket instead.

The latest version 15.0.0 has this issue. Downgrading back to 14.1.1 works fine.

What's your config? Probably need to raise a new issue

@Codex- I saw a latest issue


feat: add fix to eslint-plugin/sort-keys rule

What changed / motivation ?
Adds a fix for sort-keys ESLint rule.
This implementation has one major limitation, however. The comments are not taken into consideration for the fixes. The major reason for this is that taking care of adjacent comments introduces many edge cases and too often we cannot guarantee persistent formatting of the edited text. The current fix works like this:
Before:
const styles = stylex.create({
  foo: {
    // bar
    display: 'flex',
    // baz
    alignItems: 'center',
  },
});

After:
const styles = stylex.create({
  foo: {
    // bar
    alignItems: 'center',
    // baz
    display: 'flex',
  },
});

Let's discuss this limitation -- would like to hear some opinions of how critical you think it is to move around the comments.
Linked PR/Issues
Fixes #415
Screenshots, Tests, Anything Else
Pre-flight checklist

[x] I have read the contributing guidelines
Contribution Guidelines
[x] Performed a self-review of my code

hmm, I wonder what would be the proper way to treat the comments. similar implementations that I have seen move the comments above the property along with the property. to me, it seems that the determination whether comments above and/or below the property line belong to the property context is unclear. perhaps it's something that consumer could control via rule options.
another issue is formatting. it seems that it's almost impossible to write a fixer that maintains the correct formatting after moving comments in every edge case. I wonder if ESLint --fix takes care of indentation and whitespace with or without formatting tool dependency.

alright, I improved the fixer to handle the comments and added multiple test cases to test out how it works. there is a big chance that I might have missed some possible test cases; I would appreciate any input.
here's a few assumptions that I've made:

comments that start on the same line as the impacted property are always treated as part of the property context

const styles = stylex.create({
  foo: {
    display: 'flex', // this comment will be moved along with the "display" property
    alignItems: 'center' // this comment will be moved along with the "alignItems" property
  },
});

comments that are above the impacted property, and do not share the line with any other token, are always treated as part of the property context

const styles = stylex.create({
  foo: { /* this block comment is not part of the "display" context
    foo
    bar
    */
    // this comment will be moved along with the "display" property
    display: 'flex',
    // this comment will be moved along with the "alignItems" property
    alignItems: 'center'
  },
});

Just one thing to double check:
const styles = stylex.create({
  foo: { /* this block comment is not part of the "display" context
    foo
    bar
    */
    // this comment will be moved along with the "display" property
    // And this comment?
    display: 'flex',
    /*
      this comment will be moved along with the "alignItems" property
    */
    alignItems: 'center'
  },
});

If this is handled correctly, the assumptions make sense.

@nmn yup, both comments will be included in the move; the autofix will output:
const styles = stylex.create({
  foo: { /* this block comment is not part of the "display" context
    foo
    bar
    */
    /*
      this comment will be moved along with the "alignItems" property
    */
    alignItems: 'center',
    // this comment will be moved along with the "display" property
    // And this comment?
    display: 'flex',
  },
});

basically, all comments above the property that do not share the line with any other token or node will be included

Great! Sounds like it'll work. I'll do some extra testing and merge it for the next release.


📖 AP UI users can grant access to their Glue resources

User Story
As a AP UI user
I want to grant other users access to by glue resources
So that other AP UI users can use the resources within Quicksight
Value / Purpose
Necessary to meet the goals of the Quicksight MVP.
Users need to be able to grant other users access to their data.
This will allow those users to use the data within Quicksight.
This also reduces the need on the AP/data engineering teams to grant access to data.
Useful Contacts
No response
User Types
No response
Hypothesis
No response
Proposal

Create IAM service role that the AP UI can use with permissions that allow it to grant lake formation permissions
AP UI updated to allow authenticated users to view their databases
AP UI updated to allow users with grantable permissions to grant other AP UI users access to their database
Permissions are granted by the AP UI service role on behalf of users
Permissions are granted to users Identity Center user

Additional Information
As part of previous testing we have found that using users credentials (obtained as a token exchange between Entra and AWS) does not allow us to grant lake formation permissions. This is why we will need a service role for the AP UI that can grant permissions on behalf of users
Definition of Done

[ ] Proposal implemented
[ ] Testing completed in dev account
[ ] Steps to grant access documented

Work in progress PR: https://github.com/ministryofjustice/analytical-platform-ui/pull/250
Minor change to original proposal documented in the ticket - permissions are granted to the users Quicksight user, not their Identity Center user. This is because during testing we found that granting access to the Identity Center user did not propagate permissions within Quicksight. This is something that may be possible in future as AWS expands their Trusted Identity Propagation feature


Terraform plan errors if tectonic_base_domain is a variable

I'm trying to test this out in an empty AWS account and given I had to create and supply the route53 zone name I figured I could do something like this:
resource "aws_route53_zone" "tectonic" {
  name = "tectonic.example.com"
}

module "kubernetes" {
  source = "coreos/kubernetes/aws"

  tectonic_base_domain         = "${aws_route53_zone.tectonic.name}"
  tectonic_cluster_name        = "..."
  tectonic_admin_email         = "..."
  tectonic_admin_password_hash = "..."
  tectonic_aws_ssh_key         = "..."
  tectonic_license_path        = "${path.module}/tectonic-license.txt"
  tectonic_pull_secret_path    = "${path.module}/config.json"
}

However this results in the following error:
$ terraform plan

Error: module.kubernetes.module.etcd_certs.tls_cert_request.etcd_peer: dns_names: should be a list

Error: module.kubernetes.module.etcd_certs.tls_cert_request.etcd_server: dns_names: should be a list

If I change my manifest to the below, then it works but there's now no guarantee that the zone would exist before the module needs it:
resource "aws_route53_zone" "tectonic" {
  name = "tectonic.example.com"
}

module "kubernetes" {
  source = "coreos/kubernetes/aws"

  tectonic_base_domain         = "tectonic.example.com"
  tectonic_cluster_name        = "..."
  tectonic_admin_email         = "..."
  tectonic_admin_password_hash = "..."
  tectonic_aws_ssh_key         = "..."
  tectonic_license_path        = "${path.module}/tectonic-license.txt"
  tectonic_pull_secret_path    = "${path.module}/config.json"
}

If I add an output that just returns the value of ${aws_route53_zone.tectonic.name} then it returns a flat string exactly as it should so I'm not sure why it's exploding the way it is.
This is with Terraform 0.10.8 and version 1.7.5-tectonic.1 of the module.

This seems like a Terraform issue rather than an issue with this module :/ . Like you said, if you explicitly supply a string rather than a variable, the cluster builds.

I've pulled down master of this module instead of the version from the module registry and the plan seems to pass. The changes in https://github.com/coreos/terraform-aws-kubernetes/commit/e50ed698445430db6006d893dafe33f9b83a263a#diff-230559a0d099ca913894ba9ea207acb3 to tectonic.tf seem to be what has fixed it.
Incidentally, it takes a very long time (about 15 minutes) to run a terraform get as I end up pulling down 16 copies of the https://github.com/coreos/tectonic-installer repository to get the various modules in it and I end up with a .terraform/ directory that is about 2 GB in size.

@bodgit thanks for pointing this out. We will be releasing a new version within a week's time; that release will contain this change as well. As for the large download size, this is primarily a sub-optimal implementation issue in terraform, which should instead perform some type of sparse-checkout of git modules. That said, I am working on refactoring this module to eliminate this issue on our side. Could you update this issue, or open a new issue, to reflect this download size problem?

We will be releasing a new version within a week's time; that release will contain this change as well.

Ok, I can probably run from master for now, not a problem.

As for the large download size, this is primarily a sub-optimal implementation issue in terraform, which should instead perform some type of sparse-checkout of git modules.

Yeah, I figured Terraform could be a bit more intelligent with how it handles git downloads, especially if it sees multiple references to the same repository.
I'll open another issue for the download size.


Push a new release

Dependenices are very out of date. We need to merge
https://github.com/GoogleCloudPlatform/google-cloud-datastore/pull/216
and push a new release of the java artifacts to Maven central.

Release 1.6.1 (containing #216) has been pushed to Maven Central.


Fix 12 Boring tests involving NULL-SHA ciphersuites

The Boring runner attempts to enable the NULL-SHA ciphersuite using the
cipherstring "DEFAULT:NULL-SHA". However in OpenSSL DEFAULT permanently
switches off NULL ciphersuites, so we fix this up to be "ALL:NULL-SHA"
instead. We can't change the runner so we have to change the shim to
detect this.

Checklist

[ ] documentation is added or updated
[x] tests are added or updated

Description of change

@mattcaswell, it would be good if you have [extended tests] in your commit messages for these kinds of tests, so we can see them in action in Travis.  Granted, that will prolongue the build time, but...

@levitte, ok I'll remember that for the next one ;-)

I would have liked to see it for this one, but I guess I piped up too late...  ah well...


create-discord-bot v2

default language is now TypeScript for the main script
uses a more Object Oriented approach
adds script statuses
separates build and update process
adds a verification function for the app

So we are going to be committing compiled JS files?

I think so, I tried a bunch of different stuff (and I'm sure you have as well) it's the least hacky solution afaict.

I am a little confused though. Are we going to merge #47 or this?

So @Bytooo was originally working on #22 and the original workflow didn't facilitate e2e testing well. I think this PR is to enable that. And I realize this sort of change kinda flips everything on its head but I think it's worth it if we can get testing in.
On that note, @Bytooo, I would prefer tests done in this PR before actually merging since otherwise this is just a refactor.

Aight

Going to close this since it's stale.


updated books and courses

added some books for linear algebra
added some courses for machine learning

Try refactoring paid-courses.md . since i did not know the format so i added from my understanding.
:cheese:

@arpit1997 since we have a lot of things to fix here, the best thing to do is to close this PR and you can open another one sending this with the recommended alterations.
Thank you so much for taking the time to help us! :smile: :pray:


Error with 'dragEnd' for Tablet Browsers

We are seeing some random js errors related to drag + drop handling on Leaflet for iPad and Android tablet
For example, onDragEnd triggers following error report
Leaflet version: 0.7
At _onDragEnd
Message: 	undefined is not an object (evaluating 'this._positions[0]')
Exception type:	TypeError
Browser: iPad Safari 8.0
User agent:	Mozilla/5.0 (iPad; CPU OS 8_1_3 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12B466 Safari/600.1.4

Test url to drag on: http://timesmachine.nytimes.com/timesmachine/1969/07/21/issue.html
I think it's related to this line of code but not sure what might cause this to be undefined on iPad. Is there any way we could safeguard against this case on our end?
https://github.com/Leaflet/Leaflet/blob/c3a39f50cf7e36278749deebbd6855e5d83b4f98/src/map/handler/Map.Drag.js#L120

Can you provide a JSFiddle that demonstrates the issue please?

@jfirebaugh I don't have a JSFiddle for this one. I am not sure if you guys had any generic JSfiddle that loads some tiles in Leaflet. This one prob has nothing to do with our specific app but the drag and drop handling on tablet. I wonder what this would be on that line of code.

Try to set up a JSFiddle test case, it's pretty easy. Also, always verify issues on the latest stable and master versions rather than reporting an issue on an old version, since it may have been fixed already.


Add a security notice about the DSN

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Thanks!


Tasks are not aligning properly when using prettier

🐛 Describe the bug
I am using neovim obsidian + prettier, I use conform.nvim to format the markdown files, I  have a .prettierrc.json file as well in my vault's root. I have set vim.opt.conceallevel = 1, when it is set to 1 prettier doesn't format the tasks section of my notes well.
Without concealer = 1

With concealer = 1 (observe the gap marked with red rectangle).

Config
{
"epwalsh/obsidian.nvim",
version = "*", -- recommended, use latest release instead of latest commit
lazy = true,
ft = "markdown",
-- Replace the above line with this if you only want to load obsidian.nvim for markdown files in your vault:
-- event = {
--   -- If you want to use the home shortcut '~' here you need to call 'vim.fn.expand'.
--   -- E.g. "BufReadPre " .. vim.fn.expand "~" .. "/my-vault/.md"
--   "BufReadPre path/to/my-vault/.md",
--   "BufNewFile path/to/my-vault/**.md",
-- },
dependencies = {
-- Required.
"nvim-lua/plenary.nvim",
  -- see below for full list of optional dependencies 👇
},
opts = {
  workspaces = {
    {
      name = "personal",
      path = "~/Desktop/exit-pod/personal-notes",
    },
    {
      name = "work",
      path = "~/Desktop/exit-pod/office-notes",
    },
  },

  -- see below for full list of options 👇
},

}
Environment
See the images in Describe the bug section.

Sorry, I think this is a conceal's fault, I want ways to increase the size of check box's size.


[remote-shuffle]Reuse file handle in reduce stage

What changes were proposed in this pull request?
By switching on this feature, the file handles returned by Filesystem open operations will be cached/reused inside an executor(across different rounds of reduce tasks),  eliminating open overhead. This should improve the reduce stage performance only when file open operations occupy majority of the time, e.g. There is a large number of shuffle blocks, each reading a fairly small block of data, and there is no other compute in the reduce stage. Original PR @ https://github.com/Intel-bigdata/RemoteShuffle/pull/52
How was this patch tested?
Existing tests.

cc @carsonwang

Thanks!!


'Foo' is not assignable to 'Partial' where generic 'T extends Foo'

TypeScript Version:  2.5.3
Code
interface IViewState {
    data?: string;
}

class View<S extends IViewState> {

    public processState(): Partial<S> {
        return {data: "test"};
    }
}

Expected behavior:
Code to compile
Actual behavior:
C:\Users\Greg\Desktop\demo-app\greg>tsc --version
Version 2.5.3

C:\Users\Greg\Desktop\demo-app\greg>tsc --init
message TS6071: Successfully created a tsconfig.json file.

C:\Users\Greg\Desktop\demo-app\greg>tsc
test.ts(12,9): error TS2322: Type '{ data: string; }' is not assignable to type 'Partial<S>'.

Hey, thanks for filing, but this seems to be a duplicate of #19388, a duplicate of #17071, and a duplicate of #13442
In the future using the issue tracker's search functionality can make it easier for us to triage issues. Thanks!

However, I did try using a type assertion which your example doesn't use and that is indeed an error. I've filed #19470 for you there.

Thank you very much!

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Fail to generate map

Am I missing something? I get this exception when running ./generate.sh -r 110m
Note that I also had an error using this repo https://github.com/mbostock/world-atlas so may be related.
I am using node v4.1.0
bookmac:topojson-map-generator florian$ ./generate.sh -r 110m
Downloading Basemap
######################################################################## 100.0%
Warning 1: Value<PHONE_NUMBER> of field pop_est of feature 29 not successfully written. Possibly due to too larger number with respect to field width
Warning 1: Value<PHONE_NUMBER> of field pop_est of feature 72 not successfully written. Possibly due to too larger number with respect to field width
bounds: -180 -90 180 83.64513000000001 (spherical)
pre-quantization: 400m (0.00360°) 193m (0.00174°)
topology: 599 arcs, 8247 points
prune: retained 599 / 599 arcs (100%)
/Users/florian/repos-other/topojson-map-generator/node_modules/topojson/node_modules/rw/lib/rw/write-file-sync.js:26
        throw error;
        ^

Error: EAGAIN: resource temporarily unavailable, write
    at Error (native)
    at Object.fs.writeSync (fs.js:663:20)
    at Object.module.exports [as writeFileSync] (/Users/florian/repos-other/topojson-map-generator/node_modules/topojson/node_modules/rw/lib/rw/write-file-sync.js:22:28)
    at output (/Users/florian/repos-other/topojson-map-generator/node_modules/topojson/bin/topojson:313:6)
    at notify (/Users/florian/repos-other/topojson-map-generator/node_modules/topojson/node_modules/queue-async/queue.js:47:18)
    at /Users/florian/repos-other/topojson-map-generator/node_modules/topojson/node_modules/queue-async/queue.js:39:16
    at inputJson (/Users/florian/repos-other/topojson-map-generator/node_modules/topojson/bin/topojson:255:3)
    at pop (/Users/florian/repos-other/topojson-map-generator/node_modules/topojson/node_modules/queue-async/queue.js:24:14)
    at /Users/florian/repos-other/topojson-map-generator/node_modules/topojson/node_modules/queue-async/queue.js:38:39
    at /Users/florian/repos-other/topojson-map-generator/node_modules/topojson/bin/topojson:238:5
undefined:1
{"type":"Topology","objects":{"countries":{"type":"GeometryCollection","bbox":[-179.99999999999997,-90.00000000000003,180.00000000000014,83.64513000000001],"geometries":[{"type":"Polygon","properties":{"iso_a2":"AF","iso_a3":"AFG","continent":"Asia","name":"Afghanistan"},"id":"AF","arcs":[[0,1,2,3,4,5]]},{"type":"MultiPolygon","properties":{"iso_a2":"AO","iso_a3":"AGO","continent":"Africa","name":"Angola"},"id":"AO","arcs":[[[6,7,8,9]],[[10,11,12]]]},{"type":"Polygon","properties":{"iso_a2":"AL","iso_a3":"ALB","continent":"Europe","name":"Albania"},"id":"AL","arcs":[[13,14,15,16,17]]},{"type":"Polygon","properties":{"iso_a2":"AE","iso_a3":"ARE","continent":"Asia","name":"United Arab Emirates"},"id":"AE","arcs":[[18,19,20,21,22]]},{"type":"MultiPolygon","properties":{"iso_a2":"AR","iso_a3":"ARG","continent":"South America","name":"Argentina"},"id":"AR","arcs":[[[23,24]],[[25,26,27,28,29,30]]]},{"type":"Polygon","properties":{"iso_a2":"AM","iso_a3":"ARM","continent":"Asia","name":"Armenia"},"id":"

SyntaxError: Unexpected end of input
    at Object.parse (native)
    at Object.<anonymous> (/Users/florian/repos-other/topojson-map-generator/node_modules/topojson/bin/topojson-merge:60:21)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:475:10)
    at startup (node.js:117:18)
    at node.js:951:3
```

I have the same problem.. Did you find a solution?

I tried on my computer and it worked.
Try to set full permissions (777) for assets and maps. Let me know if that works.
I just updated the repo and added generated world maps.


Thread safe with sidekiq?

Hi Alloy!
I was trying to use lowdown with sidekiq with an open connection:
I have added method push_notification, which reuse existing client connection. Made lowdown client as a singleton.
 class Lowdown::Client
  def push_notification(notification, &callback)
    connection.open unless connection.open?
    send_notification(notification, &callback)
  end
end

But I'm receiving "RuntimeError: Connection already open." from sidekiq workers.
Do you have any recommendations how to use lowdown with sidekiq?

Hey, sorry about that, I missed the notification email for this ticket.
So, I haven’t used this with sidekiq yet and I have made significant changes aimed at maintaining long lived connections. https://github.com/alloy/lowdown/blob/master/examples/long-running.rb
One thing to note is that, as this uses Celluloid, you should be using Sidekiq 4 so that there aren’t any clashes in Celluloid usage.
I’ll be doing a release of this work probably tomorrow, would be great if you can give it a try as well.

I have wrote from scratch, used just one thread for opened http/2 connection. Looks like with http2 streams there is no need to have multithreads (all thread work done in http-2 gem)
Thank you very much for your gem, it was very useful to see how APNS works with http/2!

@leoniddinershtein Cool and you’re welcome :+1:
The reason for multiple threads is that I don’t want the callbacks to halt writing to the socket and processing the HTTP data coming back from the service. In addition, a connection pool requires threads as well. Finally, for long running connections you need some form of supervising, which Celluloid already handles nicely.
If any of these sound useful to you, then I invite you to try the current version out nonetheless and/or possibly improve it to work well for you as well.


reftools: unstable-2019-12-21 -> unstable-2021-02-13

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 243033 run on aarch64-darwin 1

2 packages built:

reftools
vimPlugins.vim-go


cacheline_data delivers poor perfomance with C++17 compared to C++14

Expected Behavior
When running programs compiled with either C++17 or C++14 should have roughly the same performance.
Actual Behavior
Programs compiled with C++17 are significantly slower. While investigating, it turns out that this is the culprit:
https://github.com/STEllAR-GROUP/hpx/blob/master/libs/concurrency/include/hpx/concurrency/cache_line_data.hpp#L46-L64
This has been verified by performing the following isolated benchmark:
clang: http://quick-bench.com/tn0AzNrQpe3t5gczE8pAJu1N5PI
gcc: http://quick-bench.com/SvM8Otk9FvU96uElajGEMAfw7mI

While fixing this issue, this needs to be addressed as well:
http://quick-bench.com/PkunktMrNXhZ5pdOusj9s9MRQ7c
as in, the generated constructor also initializes the padding data

Nice test. Disturbing result. Bug in the compilers? Seems odd that both gcc and clang are showing it in c++17 mode.

It looks like malloc is just bad when requesting aligned memory... at least that's what the profiler is telling me. So more a malloc bug. Do we know which allocator was in use when the problem was reported first?

@sithhell we were using tcmalloc for this.

Do we know enough about the behaviour here? Should we maybe revert back to using manual padding instead of alignas for the release until we understand the problem better?

@msimberg yes, I was planning to suggest doing exactly that - roll things back to manual alignment.

This has been fixed by merging #4235


Update vector tests with floating point

Reference: #978, PR #977 (in particular, commit https://github.com/lairworks/nas2d-core/commit/70724d54176c571fa33f1734af1dba5d84636aad appears to show some fixes for floating point)
Adds floating test cases for certain Vector operations that may produce warnings for floating pointer BaseTypes.

I didn't attempt to fix any warnings with this PR, as I haven't been able to reproduce any warnings. This PR is merely addressing the lack of tests which might reveal possible warnings for floating point type parameters.


segfault using string.dump and debug.getinfo

Source: https://groups.google.com/g/lua-l/c/wIzVAwNWTgM
sample = 'print("hello")'
stripped = load(string.dump(load(sample), true))
print(debug.getinfo(stripped, "L").activelines)

$ pluto test.lua

Segmentation fault

Given that this is an issue in upstream Lua, it will have to be fixed there, and then we will downstream the fix.


Voice mask

About the PR
Voice masking. Allows a user to change their voice at will. Also adds the voice mask - a stealth tool for antagonists that changes their voice to whatever they set using the voice mask UI.
Changelog

:cl:

add: Voice masking is now possible for mobs that speak.
add: The Syndicate has found a supplier for voice modification tools, and is now supplying them to their agents. Be aware of who you're speaking to: they might not be who they sound like.

Would you like to give toggleable feature on syndicate gas mask to merely scramble your voice to Unknown (or something like that), complete with spooky robotic speech sound? That would not hide that you are baddie, but saves you from having to mime out your demands.

right now, just taking off your ID will set the name you speak with to the generic name you have in identity

actually, having the identity name is probably too revealing sooooooo

there was some discussion on discord about the state of this feature, so i'll summarize it here:
voice masks (or, voice changers) currently mimic the SS13 functionality of voice changers, but it's not inherently intuitive for newer players, as it requires usage of the ID card currently equipped by the player - so, a proposed change was made that instead allows the player to set their current voice via a dialog
i don't necessarily agree with this, but i also implemented the functionality so that if some consensus is reached, it shouldn't take very long to use the new set of changes
pro and con list, feature wise:
SS13-style: ID cards as the voice mask name dependency

Pros:

Cheaper (1 - 2 TC balance because of how difficult it is to change identities)
Requires more interaction by the player in order to get an ID card if they forgo the agent card
Requires more book-keeping by the player in order to keep a distinct set of identities

Cons:

Not intuitive (requires knowledge that ID card will change the name, but instructions on this are filled in on the uplink description
Not realistic (doesn't make sense that the ID card dictates the voice generated by some other non-related item)
Requires more book-keeping by the player in order to keep a set of identities (managing ID cards is also annoying)

Proposed change: Voice mask name is stored in the player/mask

Pros:

More intuitive - player has gas mask, adjusts name, and uses it
More realistic - voice mask generates the player's voice without being dependent on other items
No bookkeeping - requires no ID card, so no bookkeeping of ID cards by the player is required
Flexible - no ID card requirement means that the player can speak like somebody else while looking (close enough) to somebody else

Cons:

Expensive (3 - 5 TC balance due to its ease of use)
Requires less (or zero) interaction by the player to mask a voice (player can just buy gas mask without having to deal with obtaining an ID card to use)
Flexible - no ID requirement means that voice names can be changed on a fly, making it less difficult for a player to keep up with identity changes

keep in mind that in SS13, most servers bundle the voice changer as part of a full "chameleon kit", which costs about 2 TC, and includes a full set of chameleon gear - the proposed change above would instead keep it as a separate item from the kit (unless it otherwise is bundled in by another PR)

With my proposal about suspicious toolbox mask getting scrambler, scope would be cheap identity hiding that does not hide I am bad person when I am in disguise, but saves my primary identity until I slip up somehow all while allowing me to ransom station and such.

this seems like a decent tradeoff, especially since if the role/person you're impersonating usually has something that hides their face to pair with the voice changer (when trying to be stealthy)