remove static_assert

rendered

The current form of static_assert is pretty weird. If we really aren't actually using it for anything, then :+1: on removing it. But with full-blown CTFE I'd want to have it reintroduced as a macro static_assert(cond[, message]) as I mentioned in my comment.

+1

As someone who uses static_assert, I'd rather not see it removed without a more compelling reason (unless full CTFE can actually fully reintroduce it, but it's not clear to me that it would be able to).

alternative: provide a macro static_assert!(condition); that expands to #[static_assert] static new_identifier: bool = condition; and stabilize the macro but not the implementation :P

The “want” to remove static_assert is intense here. It infects compiler all the way to trans. If we’re keeping it, I’d rather see this implemented within bounds of CTFE somehow.

@nrc given that I'm the author, I probably shouldn't shepard?

@pythonesque what's the use case? When I implemented this I planned on usnig it to assert that sizes of things were the same but constant expressions aren't powerful enough.
As the original designer and implementor, :+1:. This is a weird feature that is extremely limited.

@cmr I use it to assert that u8::MAX >= usize::MAX_BITS, which is required for correctness for my union find algorithm.  With more powerful constant expressions (which I think have been accepted now) I would be able to assert more interesting things (particularly around things like correct alignments / gaps in data structures, where I rely on two sizes matching up for memory safety).

I'm in favour of removing this and just using #[test]s until we get a nicer solution.

#[test]s are less reliable. In fact, at the moment, I've got an experimental project where, even if I create tests exactly as shown in the book, zero tests are found by cargo test. I haven't had time to figure out why yet.

No tests running at all seems like an orthogonal problem that should be solved anyway. :)
In any case, replacing the #[static_assert] const NAME: bool = expression; with #[test] fn name() { assert!(expression); } in a library should "just work" (unless one has explicitly opted for test = false in the [lib] section for that library).

Wait... the [lib] section? The project in question is currently a single-file binary project. Did the book neglect to mention #[test] only working in library projects?

I distinctly remember writing a patch that explains this, but I cannot find
it in the testing guide now :(
Yes, rustdoc is only able to test libraries, not binaries.

https://github.com/rust-lang/rust/pull/24508 <- hmmmmmm

oh! it's in http://doc.rust-lang.org/nightly/book/documentation.html#running-documentation-tests
but not in the testing guide. that's an oversight. I'll fix that now.

wooo reading github first thing in the morning. I should drink more coffee.
It's true that rustdoc cannot test binary crates, but #test doesn't
work either? I'm not aware of that.

@ssokolow hm, a src/main.rs like the following gets compiled and tested when I run cargo test.
fn main() {
    println!("Hello, world!");
}

#[test]
fn foo() {}

(If you're still having problems I'm happy to help, but we should take it to stackoverflow or users rather than here.)

Note: I have created a replacement lint-plugin: https://crates.io/crates/static_assert
So now there's zero reason for this to stay in the compiler.
Usage example:
#![feature(plugin, custom_attribute)]
#![plugin(static_assert_)]

fn main() {
    #[static_assert_]
    const TEST: bool = false;
}

I haven't figured out yet how to silence the "unused" warnings, but I'm working on it. Also the next step is to create a macro that automatically creates a temporary constant + adds the attribute (maybe even the #[allow(dead_code)] attribute) so it can be used just like the C++ static_assert on any constant expression
Note2: once static_assert isn't a builtin-attribute anymore, i can remove the trailing underscore

FWIW, I’ve replaced one usage of #[static_assert] by #[cfg(target_endian = "little")] so that the function would be missing on big-endian (and compilation would fail). The other usage in that library I’ve made a debug_assert!:
https://github.com/servo/string-cache/pull/85

Hear ye, hear ye. This RFC is now in final comment period until June 2nd.

:confetti_ball:

@SimonSapin Unless I missed an announcement that compiler plugins will work in stable channel, I'd hardly call it zero reason.

@ssokolow NB. this also doesn't work in the stable channel, so there's not much loss.

Ahh. That makes sense. It can get a bit difficult to keep track of which features I'm not currently using are stable.

@ssokolow I don’t see how my comment is related to plugins. Or did you mean @oli-obk ?

I think I agree with @huonw that, in practice, adding a #[test] (or a plugin, if you're so inclined) is better than keeping this feature around. I'm nervous about keeping random features around in unstable fashion for an indefinite period of time without strong motivation -- I don't want to allow de facto dependencies to form that prove troublesome to change. cough macro rules cough

I'm fine with removing this; when we do, we should probably open a corresponding RFC issue at the same time stating that we'd like to see this functionality provided in some manner in the future (in the abstract; its just an issue, not an RFC, after all).  At least, that's my take-away from the comment thread.

Based on the comment thread, we've decided to accept this RFC to remove static_assert. The major arguments in favor of removing it are that it complicates many parts of the compiler tool-chain and we know we would never stabilize the current design. Existing uses can be converted into tests or via a plugin. Per @pnkfelix's comment, we've created issue #1146.

Language Subteam

I will rebase my implementation PR later today or tomorrow.


feat:emoving-CDB-files

Description
Remove CDB files which are not needed since they can be built from the corresponding DS.dat files.
The goal is to reduce the library size. We passed from:

Directory
Before
After

src
55 MB
19 MB

verif
42 MB
5 MB

Issue linked
NA
Checklist

[x] I have visited and read Develop PyMAPDL.
[x] I have tested my changes locally
[x] I have added necessary documentation or updated existing documentation.
[x] I have followed the PyMAPDL coding style guidelines.
[x] I have added appropriate unit tests that also ensure the minimal coverage criteria.
[x] I have reviewed my changes before submitting this pull request.
[x] I have linked the issue or issues that are solved to the PR if any.
[x] I have assigned this PR to myself.
[x] I have marked this PR as draft if it is not ready to be reviewed yet.
[x] I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

For future references:
The rsm files you can find as part of the VMs files (in src/ansys/mapdl/core/examples/verif) are:

Radiosity (surface) mapping files
They are used when surf251 or surf252 are used in radiosity analysis.
Arey they needed for the VMs?

It's not really needed but added as a convenience.
It can be used when restarting an solve so you don't have to recompute the surf elements again (expensive step).
I think they give it in VM so we can edit the VM to use it and save time.  Or use as an example.
But these VM models don't really take a lot of time so not a problem to generate the file (IMO).

Thanks a lot @mikerife for your help and info.
Hence I am delete those files @koubaa


Improve homepage Layout and css

I added some of these changes on this Pull Request. Will close this PR.


Define MVP

So, I figured we should have a place to construct an idea of what exactly the MVP of resultly would be. Starting this off super vague and focused on the barest minimal product.

Login page - some auth system

Dashboard - shows list of races user has uploaded w/ CRUD options for races. Also shows status of data that's been uploaded (any large uploads may take time to process - figure we should manage expectations early).
Add Race - form w/ various fields/options for the race. Import CSV modal ([filepicker] (filepicker.io) maybe?).

method of importing, formatting, etc is still undefined as we don't know data source. Formatting/parsing of data will probably be a big issue here.

Edit Race - page where user can view/edit race data. MVP maybe we only allow reuploads for editing the actual race data? Seems like this would need a doozy of an interface compared to everything else
Delete Race - button to delete a race & its data, probably a modal for confirmation
Widget maker - small client-side app for customizing an embeddable widget w/ race data into somebody's site. Will have a small watermark or text noting that its 'powered by resultly' or somesuch, past that fairly customizable. This may not be necessary?
Race Display - Some sort of method to publicly display the race - group page or something.

This was just a first stab at thinking this out - what do you think?

regarding edit race I agree, I think its best to just allow a 'reupload' at first

widget maker Totally agree, I think this is one of the most important parts (IMO)

Everything else sounds great to me. What are your thoughts on allowing a public API so that users can bypass the widget and race display, and do whatever they want? Does this fall after the MVP?

After really looking at the way they handle recording times at events, we should also consider having a  spot in the DB for runners. This could/would include their names, DOBs, address, whatever... as well as being able to tie race results to their name.

re: public API - I'd say the API could be the MVP, if that's the direction we want to go. It would save us a lot of time in terms of client building, and we'd be able to offer a product sooner rather than later (and we could use that saved time to thoroughly document the API and build a user management system to potentially defray costs (IE, monetize the API, then build our own clients).
Definitely want to record runner info, though we'll have to do stuff that makes sense for privacy (IE, only stats they want broadcasted about them).


Msgpack support for vineyard objects

Describe your problem
Provides a virtual msgpack::sbuffer view upon vineyard objects to make values in vineyard fully compatible with the Ray object store.
Additional context
Part of #430 and related to #469 .

Close as won't fix as we cannot see the benefits for #430 and we have chosen another path for #469.


Improve usability by adding descriptions, tooltips, markdown, etc to dashboards and charts

Currently, dashboards are shown up without any content other than the dashboard title. We need to improve readability and usability by adding more verbosity anywhere in the superset app

I did some research and testing on this. I found out that Superset doesn't allow us to add slice_description in the YAML file that we import.
What I think could be a possible approach to do this is to make changes to the load-xapi-test-data command but that doesn't feel intuitively right.
Any suggestions on how else can we achieve this?

I think we can move this forward now. A few notes- we can add fields to the translation script for extraction. I think we should add X and Y labels, as well as chart descriptions to start.
In the chart yaml, when they are set, the following values exist:
slice_name: Grade distribution - courses
description: The distribution of grades for a course, out of 100%. Grades are bucketed
  in ranges of 10%.
...
params:
...
  y_axis_label: Number of Learners
...
  x_axis_label: Grade out of 100%
...

We should be able to mark those fields for translation, for instance here: https://github.com/openedx/tutor-contrib-aspects/blob/ceaf89893f8ebe0c4e1296fdd4566d5b21808654/scripts/utils.py#L65
We should also expand descriptions by default. We should be able to mark that at the dashboard level by setting:
"expand_slices": {"<slice_id>": true} see here: https://github.com/apache/superset/discussions/18347

@bmtcril Thanks for showing me the "chart description" text -- I agree that's the best we can do for documenting charts.
But instead of hiding Help links in there, we could put help links/markdown into the dashboards -- this would be more visible, and could be a first port of call for people trying to find out more about the charts in a dashboard?

@pomegranited I've been trying to use text on the dashboards sparingly, since there's no way to dismiss it and it will largely be clutter after the first couple of times someone reads it, but I think help links back to Aspects docs for the dashboards / charts would be a great use of that space. There's even a place set aside for that documentation: https://github.com/openedx/openedx-aspects/tree/main/docs/reference

@bmtcril That's excellent -- could I tackle building out this documentation and deep-linking to it from the various dashboards and charts?

That would be great! There are some thoughts that operators may want to hide those links with a feature flag, but I think we can add that later if need be.

I think we can call this done, it will likely need iteration based on user feedback but we have all the tools necessary to make this work really well now 👍


℮: change nuclear disk to ℮

Lmk if the copyright is wrong cuz I have no idea what it's supposed to be since this is just a Unicode symbol

About the PR

Nuclear authentication disk is now ℮
Why / Balance

＼（〇_ｏ）／
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

℮..

explain the joke please

erlang ss13 rewrite

e

what exactly is the joke? I don't really get it.
℮

### e?

what exactly is the joke? I don't really get it.

explain the joke please

That's not a joke, more like an easter egg to an album "E" made by Ecco2k that uses ℮ as an album cover

then big ass nuclear disc #26131 is more funny than this

Don't really think this is funny imo. Plus the licensing stuff is a little annoying. Thank you for your pr


Require providing at least some basic detail

Notes like
onosm.org submitted note from a business:
Accepted payment methods:
takeaway=undefined

are not really useful.
They are commonly created, see https://www.openstreetmap.org/note/4069989 and https://www.openstreetmap.org/note/4071738 for some of recent ones.
Maybe block note creation if info was not provided?

I added a check for minimum required fields (name, category/category description, city) in 0b32e6aa20c95a30e1e19c035bc0b02fd6511df2. I'm going to close this for now, but feel free to make a case for more/fewer required fields.


Filename variable filtering causes issue with variables followed by dot

Filename variable filtering requires variables to be delimited by underscores. Variables followed by a dot (e.g. a variable just before the file extension) are not identified correctly (continue until the next underscore or the end of the file name). Adding additional delimiters would be preferable.

This is better handled with a regular expression that is entirely configurable.
Tasks:

[ ] Update drs.json with variable_regex key
[ ] Update drs/__init__.py with regex match code


Fauxton navigation breaks when run as non-root

From @ekoome on February 21, 2016 18:40
I'm trying to navigate on Fauxton UI (e.g show databases, show config etc) but i get blank screen with the url redirected as follows.
Initial request:
http://localhost:3000/db/_utils/#/_all_dbs
This is redirected to be:
http://localhost:3000/db/_utils/#login?urlback=/_all_dbs
Do this have to do on authentication? Tried to click on login link but I get redirected to http://localhost:3000/db/_utils/#login?urlback=login
Here's my app:
var express = require ('express');
var app = express();
var PouchDB = require('pouchdb');
var riakdown = require('riakdown');

app.use('/db', require('express-pouchdb')(PouchDB));
var db = new PouchDB('acl', {db : riakdown, prefix: 'riak://localhost:8087/'});

app.listen(3000);

What am i missing?
Copied from original issue: pouchdb/express-pouchdb#290

From @jure on May 13, 2016 17:26
Hmm, I upgraded to the latest fauxton in https://github.com/jure/express-pouchdb/commits/upgrade_fauxton and I'm still getting this behaviour. I.e. navigation on Fauxton doesn't work. Sure, this is all fixable, but it's getting to a point where running a separate pouchdb-server on a different port, but using root paths for everything, is much more elegant and might be the best solution for most people (without digging into Fauxton).

I think the issue here is that Fauxton is not designed to run anywhere except for the root. So the fact that you have a /db in there is causing it to fail.
What this issue indicates is that we should probably update Fauxton, because apparently they fixed it recently but we haven't updated since then.

From @deckikwok on March 27, 2016 8:13
hmm when will this be updated(fixed)?

From @bensleveritt on November 3, 2016 13:34
I'm surprised more people don't encounter it considering this is the first example usage of express-pouchdb.
An official fix would be cool.

From @DTrejo on October 5, 2016 9:17
Here is a fix for this, it works for me. I will leave it as an exercise to the reader to clean up the code. Hope this helps!
var PORT = 3000
var DB_URL = '/db'

return main()

function main() {
  app.use(DB_URL, require('express-pouchdb')(PouchDB))
  console.log('http://localhost:%s', PORT)
  console.log()

  var mountedPouch = null
  var stack = app._router.stack
  for (var i = 0; i < stack.length; i++) {
    var route = stack[i]
    // not sure how dependable this check is.
    if (route.name === 'mounted_app' && route.regexp.test(DB_URL)) {
      mountedPouch = route
      break
    }
  }
  // console.log(mountedPouch)

  // handles requests to e.g. '/_session' '/_all_dbs' '/_users' '/_users'
  app.use(function fauxtonIntercept(req, res, next) {
    // e.g. http://localhost:3000/db/_utils/
    var referer = req.header('Referer')
    if (!referer) return next()

    var parsed = url.parse(referer)
    if (0 === parsed.pathname.indexOf(path.join(DB_URL, '/_utils/'))) {
      return mountedPouch.handle(req, res)
    }
    return next()
  })

From @jure on May 16, 2016 7:53
Any ideas from people more familiar with Fauxton? Perhaps this navigation issue is more of a Fauxton bug, but I find it surprising that no one is having issues with express-pouchdb's Fauxton under non-root paths? Perhaps it's something else that's causing this? Or just that nobody is using Fauxton :)

From @jwickens on December 6, 2016 23:49
Here's my version of @DTrejo fix, thanks for this! Btw in order to officially fix this the client would need a way to discover the correct paths, which sounds more like a fauxton repo feature request than one for express-pouchdb which is probably why this has been left unsolved.  You could build a fauxton client yourself with the correct paths for your setup but that seems more work than intercepting as @DTrejo is doing. I think the docs should definitely be updated though, because it even took a while to find this issue and the fix for it as I was searching "fauxton 404 error"
const express = require('express');
const app = express();
const PouchDB = require('pouchdb');
const pouchRouter = require('express-pouchdb');
const path = require('path')
const url = require('url')

const PORT = process.env.PORT || 3000;
const DB_URL = '/db';
const pouchHandle = pouchRouter(PouchDB);
const fauxtonIntercept = (req, res, next) => {
    let referer = req.header('Referer');
    if (!referer) return next();

    let parsed = url.parse(referer);
    if (0 === parsed.pathname.indexOf(path.join(DB_URL, '/_utils/'))) {
      return pouchHandle(req, res);
    }
    return next();
};

app.use(DB_URL, pouchHandle);
app.use(fauxtonIntercept);

app.listen(PORT);
console.log(`app listening on ${PORT}`);

This is a bug in http://github.com/apache/couchdb-fauxton so I'm going to close for now.

I think I got couchdb-fauxton v1.1.18 working with pouchdb.
note: yarn link would probably be smarter, but this is what worked for me.
note: I tried using the prepublish script in the pouchdb-fauxton fork but it failed in a variety of ways. so this approach just skips all that.

clone the couchdb-fauxton repo, defaults to folder named ``couchdb-fauxton. cd` into it.
yarn install
replace the settings.json.default.json with the source below.
yarn couchdb to build the app
rm -r ../<your-pouch-app>/node_modules/pouchdb-fauxton/www to clean out busted pouchdb-fauxton
cp -r dist/release/ ../<your-pouch-app>/node_modules/pouchdb-fauxton/www - replace it with fresh package

couchdb-fauxton/settings.json.default.json:
{
  "deps": [
  { "name": "fauxton" },
  { "name": "components" },
  { "name": "databases" },
  { "name": "documents" },
  { "name": "setup" },
  { "name": "activetasks" },
  { "name": "cluster" },
  { "name": "config" },
  { "name": "replication" },
  { "name": "cors" },
  { "name": "permissions" },
  { "name": "auth" },
  { "name": "verifyinstall" },
  { "name": "documentation" },
  { "name": "pouchdb-server" }
  ],
    "template": {
      "development": {
        "src": "./assets/index.underscore",
        "dest": "dist/debug/index.html",
        "variables": {
          "title": "Project Fauxton",
          "generationLabel": "Fauxton Dev",
          "largeLogoPath": "../../../../../assets/img/CouchDB-negative-logo.png",
          "smallLogoPath": "../../../../../assets/img/couchdb-logo.png",

          "bundlejs": "/bundle.js",
          "css": "./dashboard.assets/css/index.css",
          "base": null,
          "development": true
        },
        "app": {
          "root": "/",
          "host": "../..",
          "version": "1.0.dev"
        }
      },
      "release": {
        "src": "assets/index.underscore",
        "dest": "dist/release/index.html",
        "variables": {
          "title": "Project Fauxton",
          "generationLabel": "Fauxton Release",
          "largeLogoPath": "../../../../../assets/img/CouchDB-negative-logo.png",
          "smallLogoPath": "../../../../../assets/img/couchdb-logo.png",

          "bundlejs": "./dashboard.assets/js/BUNDLEJS_FILE",
          "css": "./dashboard.assets/css/CSS_FILE",
          "base": null,
          "development": false
        },
        "app": {
          "root": "/_utils",
          "host": "../..",
          "version": "1.0"
        }
      },
      "couchapp": {
        "src": "assets/index.underscore",
        "dest": "dist/debug/index.html",
        "variables": {
          "title": "Project Fauxton",
          "generationLabel": "Fauxton Pouchapp Hack",
          "largeLogoPath": "../../../../../assets/img/CouchDB-negative-logo.png",
          "smallLogoPath": "../../../../../assets/img/couchdb-logo.png",

          "bundlejs": "./js/BUNDLEJS_FILE",
          "css": "./css/CSS_FILE",
          "base": null,
          "development": false
        },
        "app": {
          "root": "/",
          "host": "../../..",
          "version": "1.0"
        }
      }
    },

    "couch_config": {
      "fauxton": {
        "db": "http://localhost:5984/fauxton",
        "app": "./couchapp.js",
        "options": {
          "okay_if_missing": true
        }
      }
    },

    "nightwatch": {
      "fauxton_username": "tester",
      "password": "testerpass",
      "fauxton_port": "8000",
      "db_protocol": "http",
      "db_host": "localhost",
      "db_port": "5984",
      "custom_commands_path": ["test/nightwatch_tests/custom-commands", "test/nightwatch_tests/custom-commands/auth"],
      "globals_path": "test/nightwatch_tests/helpers/helpers.js",
      "selenium_port": "4444"
    }
}

my pouch-server package.json:
{
  "name": "pouch",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "start": "node app.js"
  },
  "dependencies": {
    "express": "^4.16.3",
    "express-pouchdb": "^4.1.0",
    "pouchdb": "^7.0.0"
  }
}

@100ideas I am not able to build if I will change the settings
during the yarn couchdb I am getting this.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'webpack:release' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prewebpack:release',
4 verbose run-script   'webpack:release',
4 verbose run-script   'postwebpack:release' ]
5 info lifecycle fauxton@1.1.18~prewebpack:release<EMAIL_ADDRESS>6 info lifecycle fauxton@1.1.18~webpack:release<EMAIL_ADDRESS>7 verbose lifecycle fauxton@1.1.18~webpack:release: unsafe-perm in lifecycle true
8 verbose lifecycle fauxton@1.1.18~webpack:release: PATH: /usr/lib/node_modules/npm/node_modules.bundled/npm-lifecycle/node-gyp-bin:/home/user/node/couchdb-fauxton/node_modules/.bin:/home/user/node/couchdb-fauxton/node_modules/.bin:/home/user/node/node_modules/.bin:/home/user/node_modules/.bin:/home/node_modules/.bin:/node_modules/.bin:/usr/bin:/home/user/node/couchdb-fauxton/node_modules/.bin:/home/user/.config/yarn/link/node_modules/.bin:/home/user/node/couchdb-fauxton/node_modules/.bin:/home/user/.config/yarn/link/node_modules/.bin:/usr/libexec/lib/node_modules/npm/bin/node-gyp-bin:/usr/lib/node_modules/npm/bin/node-gyp-bin:/usr/bin/node_modules/npm/bin/node-gyp-bin:/home/user/.cargo/bin:/usr/lib64/qt-3.3/bin:/usr/share/Modules/bin:/usr/lib64/ccache:/home/user/.cargo/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/user/.local/bin:/home/user/bin:/usr/local/go/bin:/home/user/go/bin:/opt/GitKraken:/opt/robomongo/bin:/home/user/bin:/home/user/.local/bin:/home/user/bin:/usr/local/go/bin:/home/user/go/bin:/opt/GitKraken:/opt/robomongo/bin
9 verbose lifecycle fauxton@1.1.18~webpack:release: CWD: /home/user/node/couchdb-fauxton
10 silly lifecycle fauxton@1.1.18~webpack:release: Args: [ '-c',
10 silly lifecycle   'webpack --optimize-minimize --debug --progress --colors --config ./webpack.config.release.js' ]
11 silly lifecycle fauxton@1.1.18~webpack:release: Returned: code: 2  signal: null
12 info lifecycle fauxton@1.1.18~webpack:release: Failed to exec webpack:release script
13 verbose stack Error<EMAIL_ADDRESS>webpack:release: `webpack --optimize-minimize --debug --progress --colors --config ./webpack.config.release.js`
13 verbose stack Exit status 2
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules.bundled/npm-lifecycle/index.js:285:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules.bundled/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /home/user/node/couchdb-fauxton
16 verbose Linux 4.18.8-200.fc28.x86_64
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "webpack:release"
18 verbose node v8.11.4
19 verbose npm  v5.6.0
20 error code ELIFECYCLE
21 error errno 2
22 error<EMAIL_ADDRESS>webpack:release: `webpack --optimize-minimize --debug --progress --colors --config ./webpack.config.release.js`
22 error Exit status 2
23 error Failed at the<EMAIL_ADDRESS>webpack:release script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]


#12 Issue Fixed

Join-us cta is now Clickable

This was fixed with #17. Thanks for your submission!


Operator pruning unknown resources extremely slow

2019-12-27T17:01:06.096070Z     info    end pruning
2019-12-27T17:01:06.096074Z     info    end deleting resources
2019-12-27T17:01:06.112070Z     info    Reconciling IstioControlPlane
2019-12-27T17:01:06.112199Z     info    Deleting IstioControlPlane
2019-12-27T17:01:06.112216Z     info    begin deleting resources
2019-12-27T17:01:06.112221Z     info    begin pruning
2019-12-27T17:01:06.988056Z     warn    retrieving resources to prune type authentication.istio.io/v1alpha1, Kind=Policy: the server could not find the requested resource not found
2019-12-27T17:01:07.289312Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=Certificate: no matches for kind "Certificate" in version "certmanager.k8s.io/v1beta1" not found
2019-12-27T17:01:09.089291Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=Challenge: no matches for kind "Challenge" in version "certmanager.k8s.io/v1beta1" not found
2019-12-27T17:01:10.889458Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=Issuer: no matches for kind "Issuer" in version "certmanager.k8s.io/v1beta1" not found
2019-12-27T17:01:12.692409Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=Order: no matches for kind "Order" in version "certmanager.k8s.io/v1beta1" not found
2019-12-27T17:01:14.512474Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=adapter: no matches for kind "adapter" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:16.289173Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=attributemanifest: no matches for kind "attributemanifest" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:18.089655Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=handler: no matches for kind "handler" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:19.892489Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=instance: no matches for kind "instance" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:21.692170Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=HTTPAPISpec: no matches for kind "HTTPAPISpec" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:23.493298Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=HTTPAPISpecBinding: no matches for kind "HTTPAPISpecBinding" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:25.293822Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=QuotaSpec: no matches for kind "QuotaSpec" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:27.089588Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=QuotaSpecBinding: no matches for kind "QuotaSpecBinding" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:28.892578Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=rule: no matches for kind "rule" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:30.689837Z     warn    retrieving resources to prune type config.istio.io/v1alpha2, Kind=template: no matches for kind "template" in version "config.istio.io/v1alpha2" not found
2019-12-27T17:01:32.492908Z     warn    retrieving resources to prune type networking.istio.io/v1alpha3, Kind=DestinationRule: no matches for kind "DestinationRule" in version "networking.istio.io/v1alpha3" not found
2019-12-27T17:01:34.292485Z     warn    retrieving resources to prune type networking.istio.io/v1alpha3, Kind=EnvoyFilter: no matches for kind "EnvoyFilter" in version "networking.istio.io/v1alpha3" not found
2019-12-27T17:01:36.090013Z     warn    retrieving resources to prune type networking.istio.io/v1alpha3, Kind=Gateway: no matches for kind "Gateway" in version "networking.istio.io/v1alpha3" not found
2019-12-27T17:01:37.891573Z     warn    retrieving resources to prune type networking.istio.io/v1alpha3, Kind=ServiceEntry: no matches for kind "ServiceEntry" in version "networking.istio.io/v1alpha3" not found
2019-12-27T17:01:39.690067Z     warn    retrieving resources to prune type networking.istio.io/v1alpha3, Kind=Sidecar: no matches for kind "Sidecar" in version "networking.istio.io/v1alpha3" not found
2019-12-27T17:01:41.492317Z     warn    retrieving resources to prune type networking.istio.io/v1alpha3, Kind=VirtualService: no matches for kind "VirtualService" in version "networking.istio.io/v1alpha3" not found
2019-12-27T17:01:43.292464Z     warn    retrieving resources to prune type rbac.istio.io/v1alpha1, Kind=ClusterRbacConfig: no matches for kind "ClusterRbacConfig" in version "rbac.istio.io/v1alpha1" not found
2019-12-27T17:01:45.092543Z     warn    retrieving resources to prune type rbac.istio.io/v1alpha1, Kind=RbacConfig: no matches for kind "RbacConfig" in version "rbac.istio.io/v1alpha1" not found
2019-12-27T17:01:46.891665Z     warn    retrieving resources to prune type rbac.istio.io/v1alpha1, Kind=ServiceRole: no matches for kind "ServiceRole" in version "rbac.istio.io/v1alpha1" not found
2019-12-27T17:01:48.692186Z     warn    retrieving resources to prune type rbac.istio.io/v1alpha1, Kind=ServiceRoleBinding: no matches for kind "ServiceRoleBinding" in version "rbac.istio.io/v1alpha1" not found
2019-12-27T17:01:50.492833Z     warn    retrieving resources to prune type security.istio.io/v1beta1, Kind=AuthorizationPolicy: no matches for kind "AuthorizationPolicy" in version "security.istio.io/v1beta1" not found
2019-12-27T17:01:52.292656Z     warn    retrieving resources to prune type security.istio.io/v1beta1, Kind=RequestAuthentication: no matches for kind "RequestAuthentication" in version "security.istio.io/v1beta1" not found
2019-12-27T17:01:54.089729Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=ClusterIssuer: no matches for kind "ClusterIssuer" in version "certmanager.k8s.io/v1beta1" not found
2019-12-27T17:01:55.889936Z     warn    retrieving resources to prune type authentication.istio.io/v1alpha1, Kind=MeshPolicy: no matches for kind "MeshPolicy" in version "authentication.istio.io/v1alpha1" not found

Look at the timing -- its almost 2s per resource. I think its slower because the things its pruning do not exist (releated: https://github.com/istio/istio/issues/19815)

@howardjohn pointed out that go client API requests are rate controlled to a low value by default. We should prioritize trying out a faster rate since this will also speed up the control loop greatly.

I  have  same problem in  istio  1.5.0

See my unsuccessful attempt to bump this up in https://github.com/istio/istio/pull/21288.
If anyone's interested in delving deeper into this and doing some experimentation, please feel free to take over that PR.

@ostromart let me take this over then

Fixed in #23314


Implementing lull reporting at bundle level processing

Reverts apache/beam#30648

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.85%. Comparing base (6f6bbe1) to head (1a6a67d).
Report is 111 commits behind head on master.

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #30693       +/-   ##
=============================================
+ Coverage     54.32%   70.85%   +16.53%
- Complexity        0     2987     +2987
=============================================
  Files           307     1062      +755
  Lines         38123   132673    +94550
  Branches          0     3231     +3231
=============================================
+ Hits          20711    94012    +73301
- Misses        15779    35567    +19788
- Partials       1633     3094     +1461

Flag
Coverage Δ

java
68.56% <ø> (?)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

LGTM after the 3 comments are addressed.

The comments are addressed.

failures unrelated to current changes.

failures are unrelated to current change.

Failure looks unrelated, merging

Thanks Sam.


Refactor weather app to use basic DataManager and Config objects

With this PR in place, the new and highly important DataManager is used throughout the weather app. This should prioritize singleton usage throughout the whole streamlit instance. This should really speed things up, but make user uploads a hell more complicated, which we don't use anyway.
@AlexDo1  you could checkout this branch and run the state of this branch to report issues and errors back. These errors should then be resolved with the next release.

For some reason the tests are no longer running on Github, what did I do wrong?
On my laptop now only the topic_selector test does not run successfully and I'm not sure how to do that either, because I would have to read out the session_state in the test (?), I don't know how to do that.
Can you take over @mmaelicke ?

Ah, yeah. I broke that.

Hm there's the old xarray IO backend error again.
Locally on my machine the weather test works..

I removed the topic_selector tests altogether. I can't find any working way to mock a session state. Without that, unittesting anything relying on the state does just not work.

Hm there's the old xarray IO backend error again. Locally on my machine the weather test works..

Yeah, found the issue. There was a test that used the default config and not the test config. Thus, it was trying to load the original data, not the test data, which is not available in GH actions. Should be fixed now.

Nice, unittest are running now. I will merge


[WIP] Make DJ's oracle circuit construction independent from ground-truth

Summary
Modify Deustch-Josza's Oracle circuit construction s.t. it does not dependent on classically checked ground-truth information
Details and comments
The input bitmap truth table is used to generate the corresponding DNF (disjunctive normal form), which then builds a circuit that truthfully represents the truth table
as an attempt to partially address https://github.com/Qiskit/qiskit-aqua/issues/299

@hushaohan - A bitmap as input is the most general way to specify a function, but it doesn't scale well past three or so qubits, so a DNF as input to the oracle is better in that sense. I think supporting multiple input formats for DJ, BV and Simon is a good idea, 1. a bitmap, 2. a boolean formula, 3. no input and the oracle randomly generates the hidden string / result.


[W15-1] Fashion Match

added parseColor and parseType methods

why is this not working?

why are all of my pull requests failing, even the ones where I make almost no change!


Stop various tests from adding to the source tree

Instead of just adding test generated files to .gitignore. We should prevent them from being produced in the first place.
No test should ever write to the source code tree!

No test should ever write the to source code tree.

I wish there was an easy way to ensure that this does not happen. Perhaps we should be running the tests after chmoding the source tree to prevent this sort of behaviour?!

@zeripath We could do a similar check in CI than the css/js does (or did) for unchanged/added file to the git repo after the tests ran.

Yeah I guess that's a reasonable thing to do but it doesn't prevent tests from creating files in the tree and then deleting them or just adding them to gitignore.

@sapk something like this:
diff --git a/.drone.yml b/.drone.yml
index 7a844af8e..ae6a5f9b3 100644
--- a/.drone.yml
+++ b/.drone.yml
@@ -105,6 +105,7 @@ steps:
     image: golang:1.13
     commands:
       - make unit-test-coverage
+      - make test-check
     environment:
       GOPROXY: off
       TAGS: bindata sqlite sqlite_unlock_notify
@@ -122,6 +123,7 @@ steps:
     image: golang:1.13
     commands:
       - make test
+      - make test-check
     environment:
       GOPROXY: off
       TAGS: bindata sqlite sqlite_unlock_notify
@@ -150,6 +152,7 @@ steps:
     image: golang:1.13
     commands:
       - make test
+      - make test-check
     environment:
       GOPROXY: off
       TAGS: bindata
diff --git a/Makefile b/Makefile
index 146abf5d0..1b60997d0 100644
--- a/Makefile
+++ b/Makefile
@@ -200,6 +200,20 @@ fmt-check:
 .PHONY: test
 test:
        GO111MODULE=on $(GO) test -mod=vendor -tags='sqlite sqlite_unlock_notify' $(PACKAGES)
+       @echo "\n==>\033[32m Ok\033[m\n"
+
+.PHONY: test-check
+test-check:
+       @echo "Checking if tests have changed the source tree...";
+       @diff=$$(git status -s); \
+       if [ -n "$$diff" ]; then \
+               echo "make test has changed files in the source tree:"; \
+               echo "$${diff}"; \
+               echo "You should change the tests to create these files in a temporary directory."; \
+               echo "Do not simply add these files to .gitignore"; \
+               exit 1; \
+       fi;
+       @echo "==>\033[32m Ok\033[m\n";

 .PHONY: test\#%
 test\#%:

I guess it just relies on us being eagle-eyed for changes to .gitignore?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8841732). Click here to learn what that means.
The diff coverage is 40%.

@@           Coverage Diff            @@
##             master   #9515   +/-   ##
========================================
  Coverage          ?   41.6%
========================================
  Files             ?     573
  Lines             ?   75679
  Branches          ?       0
========================================
  Hits              ?   31487
  Misses            ?   40280
  Partials          ?    3912

Impacted Files
Coverage Δ

modules/indexer/issues/bleve.go
66.07% <40%> (ø)

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 8841732...b75266f. Read the comment docs.


Show error in status when exchange currencies can't be shown

Please show "yellow" status when exchange rate for BTC/USD wasn't received and hide second currency:
https://zpl.io/29QOgNp

When exchange rate for BTC/USD wasn't received hide second currency as in design

Hide second currency on all screens

checked


Automatic bundle update doesn't work under Linux

Requires sudo rights / askpass

Works when GEM_HOME environment variable is set


Change option name "accept_null_value" to "fill_null_for_empty_column"

To make clear meaning of options

@thangnc Could you review this?

👍


Update environment-cpu.yml

Support catboost

CatBoost has been added as part of https://github.com/drivendataorg/water-supply-forecast-rodeo-runtime/commit/2eb5bde3ec8bac399daa10496cb3a9799038acda, superseding this PR. Thanks for participating in the challenge!


[Feature Request] Alert Type: Special Attack%

I would love to set an alert for when I get 100% special attack.

Adittional request: make the percentage configurable instead of a flat 100%

Funnily enough, I actually had a "resource" alert in early development that was going to track special attack, run energy, and hp, but I never ended up implementing it because I introduced the Notification Fired alert type. You should be able to use the notification from Idle Notifier to create a custom alert for special attack. Let me know if you need help with that or if it doesn't fit your needs!

It's working, thank you.

Awesome!


Frame Carpet recipe error?

https://imgur.com/a/rsYUUb2
I'm assuming the minecraft tag changed between one of the versions? (it's now "wool_carpets" I believe)
I am using minecraft 1.19.2 and mod version blockcarpentry-1.19-<IP_ADDRESS>

I did not, every other recipe seemed normal in the JEI mod that I saw!
Love the mod btw <3

Alright, thank you very much and thanks for your nice words! I appreciate that! :)
Regards, Manu


Host app can't get the plug-in DLLs from a folder other-than the executable's folder in .NET Core!?!

Hello,
I have my previous issue resolved for .NET Framework, but I'm having problems porting the app over to .NET Core.
It works in .NET Framework just fine, but i just can't seem to get it working in .NET Core.
After much research, it looks like .NET Core doesn't have the equivalent feature:
    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <probing privatePath="Plugins"/>
        </assemblyBinding>
    </runtime>

...like it has in .NET Framework.
It appears (at this point) there is no real way for your host app to tell the .NET Core CLR where to resolve the dependencies when you have globalisaiton (i.e. vs-mef) and you want to specify a folder where your plug-in DLLs reside.
References
https://stackoverflow.com/questions/46764925/exporting-interface-from-class-net-core
https://github.com/dotnet/cli/issues/11713
https://stackoverflow.com/questions/56844233/additional-probing-paths-for-net-core-3-migration
Is there anyway or suggestions this can work in .NET core 3 ?

This doesn't sound like a VS-MEF specific issue. Rather, it sounds like your issue is "how to load assemblies from other locations on .NET Core?" Once you have that answered, VS-MEF should Just Work.
Here's a tip (I haven't tried it): https://natemcmaster.com/blog/2018/07/25/netcore-plugins/


fix: dynamically importing lottie web package

Closes #6243
lottie-web package will be dynamically imported at the time of usage only. That is only when media prop is passed with animation paths.
What did you change?
used import().then() syntax to dynamically import the package
How did you test and verify your work?
local

looks good just one comment.
also as part of the verification process could you test and shows the results of the bundle size to show that the bundle is smaller? maybe using something like webpack-bundle-analyzer if it's helpful

Hi David,
I was not able to replicate the original issue the user was referring. I couldnt see lottie-web being bundled when none of the related components (Coachmark, inLineTip) is used. I used a package source-map-explorer  to explore the bundles.
With lottie-web

**without lottie-web**

When import.then() is used, lottie-web will be bundled separately and get downloaded at the time of usage
https://github.com/user-attachments/assets/a5a70c7c-91fb-4ecf-9558-21e7c304a9d4

@matthewgallo i believe we agreed that instead of trying to implement the dynamic importing that we would just cut lottie in favor of allowing the consumer to choose to to implement the animation, right?

Yep, that's what I also remember after we last reviewed this. And also because SteppedAnimatedMedia and the other components that use it are experimental/preview we have a little more flexibility to just remove it (lottie-web).

@amal-k-joy can you open up a new issue for removing the lottie dependency? we can keep this PR up for now unless anyone else wants to close it

#6243

@matthewgallo , @davidmenendez ,
I have opened this issue to decouple lottie-web from our component. Currently we have exposed a media prop that expects either a render callback(media.render) that returns a component( <img>) or filepaths(media.filepaths) with animation data.
The new approach I am thinking is to deprecate the media prop and introduce an new callback prop called renderMedia which can return any react component. So if user needs lottie animation, they can import the package from their end and pass down the animated component as it is.
Here in this example , <SteppedAnimatedMedia> that has lottie-web will be imported only in stories . User can either use <SteppedAnimatedMedia> or their own custom component.
  <InlineTip {...args}  action={selectedAction} renderMedia={() => <SteppedAnimatedMedia
          filePaths={[InlineTipAnimation]}
          playStep={1}
        />} />

<InlineTip {...args}  action={selectedAction} renderMedia={() => <img alt="" src={InlineTipImage} />} />

<InlineTip {...args}   action={selectedAction}  />

Please share your thoughts.

Thanks @amal-k-joy for opening the follow up and documenting it nicely! We can move further discussion to the issue. 😀


ComboLineColumnChart with stacked bars

I would like to have a stacked bar chart with a line.  Is this possible?  ComboLineColumnChartData doesn't have a setStacked method whereas ColumnChartData does.

After a closer look, this functionality is already possible when specifying the ColumnChartData separately


V1.10 hp_default low on stack

During some preliminary test with 1.10RC2 I got a hp_default low on stack warning.
I can't unfortunately reproduce this behavior right now.
Here is the flight log : https://review.px4.io/plot_app?log=fd552709-201a-4904-aa05-a32a49c8a50b

Same, but I dont get it all the time.
With low stack:
https://logs.px4.io/plot_app?log=28b95b8c-e567-4e13-b546-338f91c4e8b3
Without:
https://logs.px4.io/plot_app?log=a8662dfc-e6f1-453a-9c9d-8ca576b93340

I was probably unclear but I don't get all the time as well.

I'll bump it to silence the warning.
https://github.com/PX4/Firmware/pull/13707


Garbage not reduced correctly after a table

Garbage reduction is broken, when more than 1 empty line after a table.
Exemple 1, with 2 empty lines : the header is not formatted.
|a|b|

h1. header

Output :

		a
		b

h1. Test

Exemple 2, with 3 empty lines : the header is formatted, but an empty paragraph is inserted.
|a|b|

h1. header

Output :

		a
		b

Test

Hi @borgar ,
Can take a look at this commit in my repo ? GehDoc/textile-js@071a1d3
It fixes this bug, and doesn't break any exiting test.

This is definitely something I want to look at but I have not had the time to yet. Sorry for the delay. Hopefully soon! 🙂


TypeScript doesn't recognize the constants that in Jodit

Jodit Version:  3.15.3
Browser: Chrome
OS: Windows
Is React App: True
Expected behavior:
All the constants should be defined in Jodit to be able to used it with TypeScript (constants file)
Actual behavior:
TypeScript doesn't recognize the constants that in Jodit (e.g. MODE_SOURCE)

Added Jodit.constants. Please use it instead. I don't know how to do it differently


Specify build backend for editable installs

Fixes the issue that showed up in https://github.com/jazzband/tablib/pull/500, also reproducible locally:
With the old pip==21.2.4 we could do python -m pip install -e . for an editable install.
Now, with new pip==21.3 we need to specify the build backend. See:

Support editable installs for projects that have a pyproject.toml and use a build backend that supports PEP 660. (#8212)

https://pip.pypa.io/en/stable/news/#features
See also https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/

Thanks!


Add a few new methods to Scroll

These make it possible to configure a few more aspects of the
scrollview's behaviour after it is created.
This will be used for upcoming changes to the textbox.
This also relaxes the type constraints required for some methods.
based off of #1630

@jneem @ForLoveOfCats either of you have any concerns with this?

Oh good call I keep forgetting about the changelog 😬


Messaging Gateway

Motivation
There are already many messaging applications written based on other messaging protocols, such as Kafka, MQTT and other customized messaging protocol. For those messaging applications to leverage the features/advantages of Pulsar, people have to rewrite their applications to use Pulsar API. That creates barriers for people to tryout.
As Pulsar's messaging model is a flexible and unified messaging model, which already unifies queuing and streaming into one messaging model and API. So it should be able to adopt to many other messaging models. Pulsar's tiered architecture makes it self a great messaging backend for different messaging protocols, so it would be great that Pulsar can provide a gateway/proxy to allow pluginning different protocols. So Pulsar can naturally support the messaging applications that already written in other messaging protocols/apis, such as Kafka, MQTT.
This is the master issue for tracking the idea for providing a messaging gateway in Pulsar to support different type of messaging protocols. Also it would be great to collect the feedback from Pulsar users or people who is looking into using Pulsar.

It would be great to be able to just plug in Pulsar in existing network of corporation messages where Kafka is currently in use. Right now, the only solution I have found is to manually recompile all other applications connected to Kafka with Kafka Wrapper which is only available for Java applications by the way.
With that feature implemented I could use for example Elastic Beats with Pulsar as well, since they added Kafka as supported output awhile ago.
I sincerely believe this is the must have feature at least until Pulsar will not be popular enough that every application out there would have to implement support for Pulsar in order to satisfy community's demand.

It would be great if Pulsar could act as an MQTT broker while storing the received messages.
We at HSL have sources sending us data over MQTT and we publish open APIs over MQTT. For example, our fleet produces High-frequency positioning (HFP) MQTT messages with QoS 1. Including the confidential messages, we get roughly 1000-2000 messages per second into the HFP topic tree. We'd like to store those messages in Pulsar.
 As Pulsar doesn't offer compaction that would retain only the first message for the key instead of the last, we'd have to build that kind of compaction in a Pulsar client.
Additionally, we'd like to avoid losing data due to MQTT subscriber crashes and this problem: "Effectively-once publishing in practice only makes sense when the messages are coming from a replayable source as opposed to a non-replayable source (for example online HTTP requests). For non-replayable sources, there’s no way to re-send the previous pending messages after a crash."
An approach for not losing data is to deploy several MQTT subscribers into different availability zones forwarding messages into the same Pulsar topic. The key of each Pulsar message would contain at least the digest of the payload. Again the variant of topic compaction that would retain the first message for each key would allow deduplicating the repeated data. This feels overly complicated, though, just for storing the messages.
MQTT seems to be on the rise in public transport in the Nordics. Off the top of my head I can see several reasons:

The protocol standard and several existing broker products avoids vendor lock-in.
It's fairly easy to understand the basics of MQTT.
Safely mixing public and confidential uses on the same MQTT broker is not a problem.
Easy demarcation of responsibility between data providers and consumers aids in demanding MQTT in contracts.

Unfortunately, storing the delivered data is often ignored in the contract phase but almost all of the data needs to be stored. There could be a market for an MQTT broker that acked messaged only after storing them, not after receiving them.

For people who are interested in this feature, we have introduced a general framework in 2.5.0 to support pluggable protocol handlers. We also developed a Kafka protocol handler (Kafka-on-Pulsar, #KoP) using this framework - https://github.com/streamnative/kop. If you are interested in the Kafka compatibility layer, please check it out.
We are also using the same framework to develop the protocol support for AMQP and MQTT. Please stay tuned.

Close this issue since the protocol handler mechanism has been introduced in Pulsar.
Currently Kafka and AMQP protocols are supported from this framework.
KoP: https://github.com/streamnative/kop
AoP: https://github.com/streamnative/aop


⚠ Bofrost.de has degraded performance

In 57af440, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 754 ms

Resolved: Bofrost.de performance has improved in 19b7647.


do not work disconnect

I join to app this plugin, but not good work disconnect. please help.
first once connecting, and requesting is OK.
but then disconnect and continue connect is not working.
    try {
      // scan device
      BleStandPeripheral device = await _scan(standID);
      // when I debug, second connect stop there
      this.central.connect(device);
      completer.complete("connected");
    } catch (e) {
      logger.warning(e.toString());
      completer.completeError(e.toString());
    }

Future<BleStandPeripheral> _scan(String standID) {
    logger.info("scanning... $standID");
    var completer = Completer<BleStandPeripheral>();

    _observePeripheral = this.central.scannedDevice;
    _observePeripheral
        .where((device) => standID == device.name)
        .listen((device) {
      this.central.stopScan();
      logger.info("scanned device: ${device.name}");
      completer.complete(device);
    }).onError((err) {
      logger.info(err.toString());
      completer.completeError(err.toString());
    });

    this.central.startDeviceScan();
    return completer.future;
  }

same to me , the problem is disconnect did not work well everytime(are you disconnect in dispose or deactivate,sometimes it did not execute in time ) ,so continue connect is not working somtimes
,

I ran into the same problem. Ask for help


SettingWithCopyWarning

Proof of concept: work in progress.

Some additional work is needed, in particular to transform the "file name" into something more helpful, like I usually do for tracebacks.
Since there is no traceback produced, the code does not stop running at the frame in which the warning is raised, which makes it a bit more difficult to get accurate information. However, it should be possible to get the frame in question.

Improved location with friendly_traceback 0.7.2

And here's a more interesting example when it comes to finding the location of the offending statement, even if it spans multiple lines.


Debug statement left in

https://github.com/takeflight/wagtail-charcount/blob/master/wagtailcharcount/static/hallo_charcount.js#L86
Not sure if this was on purpose but looks like a console.log() was left in

@SableWalnut, could you please create a new release with this fix?


1006v2 release exposes 2 different code bases, not fully functional with v2

1006v2 release features 2 different code bases.

The 1006v2 itself has only 2 configs in /v2 folder: 32k.json and 48k.json Hence, with v2+"40k" it uses 40k.json from /v1 folder:
infer-web.py
    if version19 == "v1" or sr2 == "40k":
        config_path = "v1/%s.json" % sr2

That means that for "40k" v2 it uses v1 config and for 32k and 48k v2 - v2 configs

Different story for 1006v2 v2 notebook. For some strange reason it fetches another codebase. This code has no specific configs for v1 or v2 all are same.
Retrieval_based_Voice_Conversion_WebUI_v2.ipynb
!git remote add origin https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI.git
!git fetch origin cfd984812804ddc9247d65b14c82cd32e56c1133 --depth=1
!git reset --hard FETCH_HEAD

And infer-web.py from this code, doesn't allow to select SR other than "40k" when "v2" selected.

Finally, v2 "40k" checkpoints D40k.pth, G40k.pth are provided within 1006v2 release. And v2 32k and 48k are there as well. All three v2 D/G checkpoints seem ready to use.
Summary. First code uses v1 40k instead of v2 40k and is okay with v2 32k and 48k. Second code is okay with v2 40k only.
I can't understand:

why two different code bases are used within 1006v2 release?
which of them to use with v2? Maybe both not fully compatible with v2

40k config, v2=v1
32k 48k config, v2!=v1


Cost Kernel Selection Spec

For triage: cost out the parts of the kernel selection spec.

Scenarios
As a data scientist… (based on assumptions on our experiences)

I want to see what kernel is being used with my notebook to ensure my notebook environment is correct

I want to see the status of my kernel to see if the kernel is dead, or if there is a long running execution, that the interrupt kernel button does its job

I want to change the corresponding kernel on my notebook because I might have notebook code that is designed to run on specific kernels only (e.g. Python2 vs Python3) or one kernel may have the specific Python packages I need

I want to connect to a remote Jupyter server to make use of remote compute power. As well, I may not be able to use VS Code remote SSH because my remote server might be shared with another user, or I might not have permissions to install VS Code on that machine (e.g. if that machine is an enterprise machine).

I want to work on 2 different notebooks that have different kernels

I want to work on a Python file in one environment and also a notebook in a different Python environment

I want VS Code to detect all the kernels globally in my system

When I change my notebook kernel, I do not want it to change my global Python Interpreter because I don’t want my workspace to use that same kernel

When I change my global Python Interpreter, I do not want it to change my notebook kernel because I changed it specifically for my Python files

UI:

Remote and Local work

Remote jupyter server/Kernel status/Kernel Name component UI - 1 day
Generate kernel spec list on startup of extension if meet conditions outlined in (#7242, #8183)  - 1 day
Update status based on different events (#8079) - 1 day
On click of server/local show quickpick with server list and ability to type in new one - 1 day
If server started, enumerate running kernels and put them in quick pick when appropriate (#3763, #4644) - 1 day
Compute kernel based on notebook metadata - 1 day
When clicking on kernel, show quick pick with kernel list (including run time etc) - 1 day
Telemetry - 1/2 day
Option to stop kernel (not spec'd, but in this bug #7926) - 1/2 day
Change to use language server per kernel (#8206) - 3 days

Local only

Create kernel specs with environment instead of starting jupyter with env (#8174, #8197) - 1 day
Turn these kernel specs into a json file and modify jupyter startup to use our list instead the default (#8175, #8125)- 2 days

Remote only

Enumerate remote kernels - 1/2 day
Keep track of previous servers - 1/2 day

Total cost: 15 days

Validated. LGTM.


Orchestrator Service Config Validation

Description
For Issue https://github.com/foundation-model-stack/fms-guardrails-orchestrator/issues/23
Changes

introduced config error type variants
made tls, chunkers and generation config sections optional

tls may also be provided inlined to a service config
chunkers can be omitted, in which case the default "whole_doc_chunker" chunker will be subsidized
generation as a whole may be omitted from configuration

support for and error handling of optional generation client configuration
implemented validation logic and error handling for tls config mapping
added more config validation tests for error handling

Thanks @pscoro. I added a couple of comments inline. I have a couple of changes that I want to ideally add to this PR, if you don't mind me pushing a commit? I didn't add them as comments as they are partially cleanups of existing code I wrote.

Sounds good go right ahead

let orchestrator = Orchestrator::new(config).await?;

@declark1 would it make sense to also move this line out of Server::run and into main as well? Every error after that point is strictly server related so maybe this will help clear up the errors a bit more

let orchestrator = Orchestrator::new(config).await?;

@declark1 would it make sense to also move this line out of Server::run and into main as well? Every error after that point is strictly server related so maybe this will help clear up the errors a bit more

Yep, makes sense to me. Btw, you have to sign your commits in the public github for the DCO check to pass. https://github.com/foundation-model-stack/fms-guardrails-orchestrator/pull/176/checks?check_run_id=29272541061

Yep, makes sense to me. Btw, you have to sign your commits in the public github for the DCO check to pass. https://github.com/foundation-model-stack/fms-guardrails-orchestrator/pull/176/checks?check_run_id=29272541061

do we have to sign with our public github email or our ibm email?

Yep, makes sense to me. Btw, you have to sign your commits in the public github for the DCO check to pass. https://github.com/foundation-model-stack/fms-guardrails-orchestrator/pull/176/checks?check_run_id=29272541061

do we have to sign with our public github email or our ibm email?

I'm not sure actually. I use my IBM one, but it probably doesn't matter.

commit signatures added. I think because of the rebasing it now says I committed all the commits but I preserved your authorship

@declark1 I pushed the last discussed change about moving orchestrator initialization out of server start up. There's a lot of follow up work that I see potential for that I have looked into, but I think for this PR I think we should wrap it up soon since every additional detail seems to want to unravel into even more fixes. Should we merge this?
List of follow up suggestions I came across while working on this and the health check issue, I have experimented with most of these on personal branches at least a bit so I can include a complexity estimate on the side of each point [/5]:

[2/5] there is similar "try to open/resolve cert files from config" logic in clients::create_http_clients() and clients::create_grpc_clients() that can not only be factored out but can probably also be done during config validation step (if tls configs exist we may as well read the cert files and resolve the config enitrely?)

this will allow us to get rid of a lot of the panics in these two functions, that are otherwise a bit challenging to propagate, by handling the behaviour in an earlier more appropriate step
[1/5] we could then also split up orchestrator::create_clients() into orchestrator::create_detector_clients() etc. to decouple a massive function, and add error propagation. From what I can tell with this design, the main function can basically say: "we set up config, orchestrator and then server. If config fails in a predictable way, that is a fatal error. If config succeeds, then we do not expect orchestrator start up to fail (given we checked config/certs properly before hand) so this step should panic on any error currently. And finally because we separated these concerns, if the call to run the server returns erroneously we know to consider this a fatal server crash"

[2/5] we could transform transforming a deserializable+with-optionals "unresolved" config type into a resolved config type, significantly reducing the number of optional checks/unwraps or accidental late-validation/re-validation of things that could have been caught already and certified by having a static type for resolved config (ie a type in which anything mandatory or that has a default value is no longer Option<...> and all the tls/cert config items are fully validated, including checking cert paths etc)
[1/5] pretty logging of fatal errors:

Working around the tracing crate with minimal additions, we can have a graceful shutdown for application misuse (eg misconfiguration). The code to enable the above image is pretty minimal. If we handle the point above about move cert validation into the config step, then I think basically all the misuse scenarios on start up can be caught and display elegantly to the service administrator like this.
[4/5] ExternalError infrastructure - Supposing that clients::Error exists to model errors encountered during or as a response from client interaction, and server::Error is for errors encountered during server execution that should result in an error response to the user and potential additional internal error handling:

Modelling errors coming in through an external protocol (http/grpc) and errors going back out can be done through shared infrastructure, I have experimented with this quite a bit and found a couple good design ideas, in particular I think a serializable/deseriazable ExternalError type with a code, message, and optional details object is a common model that can fit into both http and grpc error responses (see tonic::Status::with_details)

If any of these ideas seem valuable let me know, I imagine we would probably make issues for tracking, also no worries if none of these are worth investing effort into, just contributing my two cents.

I just pushed some changes to tweak the config::Error variants and messages a bit and updated main to return anyhow::Error instead of Box<dyn std::error::Error>, leveraging it to show the config::Error Display impl to the user instead of Debug.
A few examples from testing:
Error: failed to read config from `/Users/dan/does_not_exist.yaml`: No such file or directory (os error 2)
Error: invalid config file: generation: missing field `provider` at line 2 column 3
Error: chunker `sentence_syntax_izumo_en_stock_chunker` not found for detector `en_syntax_slate.38m.hap`

I think this is good to go now, will approve and merge.
Re: your comments above, we can discuss further, but we don't need to over-engineer the error handling as there are more important items to get to.

Completely understood, still getting a feel for what the priorities are, will put a pin in all of the above. Thanks for the review


Change permissions for the image folders

Images are not served by Nginx due to a wrong permission on the image folders.
How to fix this?
There are 2 ways:

Use flask to serve images
Set folder permission on app start.

[x] Added a flask module to serve images at 1e7af1a8002386e5a4372af6ea2edf6f9f520c1f on #47


Add unit test: addAllFiles should work correctly with non-.js files

Unit test for the PR #326

Changes Unknown when pulling 66a8118d2c24b69d8e1e042671e45d68acd5742e on rundef:master into ** on istanbuljs:master**.

@rundef give the following a try:
npm cache clear; npm i nyc@next, I've released your changes.
I'd also love the second set of eyes on the include/exclude logic, as I've released some breaking changes to how this is handled.


Automatic access token storage

It would be nice if the library automatically, or maybe optionally, would store the resulting access token, e.g., in local storage.

As per my comment in #49, I don't think this is worth the complexity here. especially since you can assume most people won't be using these more than a few times.

@RileyTomasek I'm not sure what you mean by "you can assume most people won't be using these more than a few times." Why wouldn't users of apps be using the app more than a few times? (dropbox.js  does this sort of storage automatically, and I always felt it was pretty convenient.)

oh, sorry, i thought you meant implement it in the example code. regardless, this is something that doesn't belong in the main library and should be left to the developer since there are so many different ways to do this that will work differently for each app. Maybe if we get people asking about it, we can make an example specifically to show how you would do it.


MCA Enterprise to MPA

I work for an Azure Expert MSP and we are looking to move a customer from MCA Enterprise to CSP (Azure Plan).   I'm being told by Microsoft that this requires a resource migration and is not possible via a backend billing change.  Please confirm that the documentation is correct for the following:

MCA - Enterprise
MPA
• Only CSP direct bill partners certified as an Azure Expert Managed Services Provider (MSP) can request to transfer Azure products for their customers that have a Microsoft Customer Agreement with a Microsoft representative. For more information, see Get billing ownership of Azure subscriptions to your MPA account. Product transfers are allowed only for customers who have accepted a Microsoft Customer Agreement (MCA) and purchased an Azure plan with the CSP Program.• Self-service reservation transfers are supported.• There are limitations and restrictions. For more information, see Transfer EA subscriptions to a CSP partner.

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

ID: 55151e88-c7c5-47e4-573c-04441dc23577
Version Independent ID: f0253fd2-838c-23c5-bb1f-f702ca04923d
Content: Azure subscription and reservation transfer hub
Content Source: articles/cost-management-billing/manage/subscription-transfer.md
Service: cost-management-billing
Sub-service: billing
GitHub Login: @bandersmsft
Microsoft Alias: bandersMCA - Enterprise	MPA	• Only CSP direct bill partners certified as an Azure Expert Managed Services Provider (MSP) can request to transfer Azure products for their customers that have a Microsoft Customer Agreement with a Microsoft representative. For more information, see Get billing ownership of Azure subscriptions to your MPA account. Product transfers are allowed only for customers who have accepted a Microsoft Customer Agreement (MCA) and purchased an Azure plan with the CSP Program.

• Self-service reservation transfers are supported.
• There are limitations and restrictions. For more information, see Transfer EA subscriptions to a CSP partner.

@devan10 Enterprise EA to MPA transfers are supported. https://docs.microsoft.com/azure/cost-management-billing/manage/mpa-request-ownership has the steps for both the Partner and their customer. A billing support request or interaction with a Microsoft representative shouldn't be needed.
Have you tried the process at https://docs.microsoft.com/azure/cost-management-billing/manage/mpa-request-ownership?

I see you've mentioned "Enterprise EA to MPA transfers are supported"........did you mean MCA Enterprise to MPA transfers are supported?  I just want to be clear as the link in the table goes to EA transfer process but I believe should in fact link to the MPA document you sent.
Currently the customer is not on MCA yet so we are unable to try the process.

@devan10 Sorry, I meant to say Enterprise MCA to MPA is supported.
In the article intro at https://docs.microsoft.com/azure/cost-management-billing/manage/mpa-request-ownership, it says:
Supported product (subscriptions and reservations) billing ownership transfer options include:

A direct Enterprise Agreement transfer to an Azure plan under the MPA
An enterprise Microsoft Customer Agreement transfer to an Azure plan under the MPA

The document is correct. I apologize if any Microsoft employee has said anything that refutes the article.

#please-close

Thank you for the feedback and help with this.


Add AVAX C Chain Abandon Seed

📝 Description

Add abandon seed for AVAX C Chain
Add CryptoCurrencyId in types-cryptoassets

❓ Context

Impacted projects: LLC
Linked resource(s): https://ledgerhq.atlassian.net/browse/LIVE-4261

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Most changes are related to typing improvement initiatives started with the AVAX integration, so when changing a type sometimes other files are impacted but still related to the PR


chore(master): release 1.1.74

:robot: I have created a release beep boop
1.1.74 (2023-09-11)
Bug Fixes

deps: update dependency wayofdev/laravel-cycle-orm-adapter to v4.0.93 (8ecb9e5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-webhook-client/releases/tag/v1.1.74 :sunflower:


API Endpoint Creation

Created a basic API endpoint that will ultimately pull a user's program and profile to return a solved schedule.

LGTM


Error when adding recipients to empty password store

Summary
Adding new recipients to an empty store finishes with an error.
Steps To Reproduce

Create an empty password store
Use gopass recipients add --store MyStore 0xYZM
Read Error: failed to add recipient '0xYZM': failed to commit changes to git: git has nothing to commit

Environment

OS: Mac OS X
gopass Version: 1.8.5
Installation method: brew

Use gopass recipients add --sore MyStore

Looking at your syntax there, I think you're missing the recipient's fingerprint or mail?!

Yeah sorry, just typed from the top of my head. Should've copied it from the command line. Going to fix this when I'm back at the computer. In the meantime you can still try adding a recipient to a freshly initialised store.

Still a problem when adding recipients to a freshly initialised store.

Bump


Prettier

This PR adds the Prettier code auto formatter as a fixable eslint rule.
This means that a uniform coding style will be enforced by linter rules. If you violate the coding style, ember-cli will scream warnings. You can also configure your editor to fix eslint errors on save, which I highly recommend. Doing so will ensure that your code is automatically formatted.
I disabled Prettier for some bits, as that could cause pain when upgrading ember-cli.
We adopted Prettier at work and I think it greatly improved our developer experience. 99 % the time it generates easier to read code. For the other 1% there's // prettier-ignore or /* eslint-disable prettier/prettier */.
I have no hard feelings, if you're against merging.

It's definitely not a bad thing, although I wouldn't have done some of the formatting they codified.
I'm was waiting to see what comes of https://github.com/emberjs/core-notes/blob/master/ember-cli/2017-06/june-29.md#prettier but as always you're one step ahead.

Haha, yeah. I suffer from a real bad case of shiny new toy syndrome. :joy:
It's true that there are a few places, where I would have styled differently, but the overall consistency outweighs these few for me.
Thank you for the link to the notes. Must have slipped my attention.

Given how out of date this now is, I'm going to close so we can focus on ember octane support.


ID in ToCamelCase not correct

ID in ASP.net core will be translated to id when config json in camel case but NTypewriter will be translated iD.

It does not look like System.Text.Json is available in source generators at least

It is not officially supported, but it should be available. But which version of it is available depends on VS and what is loaded to VS app domain.


GenerateResourcesAndImage for Windows 2019 fails with C:\ProgramData\docker\cli-plugins already exists

Description
Getting the following error when running GenerateResourcesAndImage for Windows2019:
"New-Item : An item with the specified name C:\ProgramData\docker\cli-plugins already exists"
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[X] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Windows 2019
Is it regression?
Not that I'm aware of
Expected behavior
I expect the build to complete and create a viable Windows 2019 build agent image
Actual behavior
Fails with the following error:
azure-arm.image: Chocolatey installed 2/2 packages.
azure-arm.image:  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
azure-arm.image: Package installed: docker-compose|2.26.0
azure-arm.image: Install-Package Docker-Compose v2

==> azure-arm.image: New-Item : An item with the specified name C:\ProgramData\docker\cli-plugins already exists.
==> azure-arm.image: At C:\Windows\Temp\script-6600d936-3c53-a9b8-af17-02b9ef79c5ce.ps1:17 char:1
==> azure-arm.image: + New-Item -Path $cliPluginsDir -ItemType Directory
==> azure-arm.image: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> azure-arm.image:     + CategoryInfo          : ResourceExists: (C:\ProgramData\docker\cli-plugins:String) [New-Item], IOException
==> azure-arm.image:     + FullyQualifiedErrorId : DirectoryExist,Microsoft.PowerShell.Commands.NewItemCommand
==> azure-arm.image:
==> azure-arm.image: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]
==> azure-arm.image: Step "StepProvision" failed
==> azure-arm.image: [c] Clean up and exit, [a] abort without cleanup, or [r] retry step (build may fail even if retry succeeds)?
Repro steps
cd
az login
Import-Module .\helpers\GenerateResourcesAndImage.ps1
GenerateResourcesAndImage -SubscriptionId  -ResourceGroupName PackerBuildAgentWindowsRG -ImageType Windows2019 -ManagedImageName "BuildAgentWin19_IMG" -AzureLocation "westus2" -ImageGenerationRepositoryRoot

Hello  @clbarrett . Thanks for your report. We working on it.

Should be fixed, please pull your main branch updates.


Closing response or session does not immediately terminate the response stream

I'm using requests to stream an SSE response. The actual streaming takes place on a separate thread:
import threading
import time

import requests
import sys

def read_response(resp):
    try:
        resp_iterator = resp.iter_content(decode_unicode=True)
        for ch in resp_iterator:
            sys.stdout.write(ch)
            sys.stdout.flush()
    except Exception as ex:
        print ex
    print 'Exited at:', time.time()

session = requests.Session()
headers = {}
headers['Cache-Control'] = 'no-cache'
headers['Accept'] = 'text/event-stream'
resp = session.get(my_url, headers=headers, stream=True)

# Kick off the stream in a different thread
thread = threading.Thread(target=read_response, args=[resp])
thread.start()

# Keep streaming for 5 seconds
time.sleep(5)

# Try to close the response
print 'Closing response...'
resp.close()
print 'Closing session...'
session.close()
print 'Closed at:', time.time()
thread.join()

In the above example I kick off the stream, wait for 5 seconds, and then close the response and the session. I expected the response iterator to end at this point (either normally or by throwing an exception). But it doesn't end for 25-30 additional seconds. Here's the output I get:
Closing response...
Closing session...
Closed at:<PHONE_NUMBER>.74
('Connection broken: error("(9, \'EBADF\')",)', error("(9, 'EBADF')",))
Exited at:<PHONE_NUMBER>.98

Notice the difference between Closed at and Exited at timestamps.
Any idea why this is? I assume it has something to do with the underlying socket remaining active for a period of time. Is there some way to force termination of the stream/iterator when the response is closed?
System Information
$ python -m requests.help

{
  "chardet": {
    "version": "3.0.4"
  },
  "cryptography": {
    "version": "2.1.4"
  },
  "idna": {
    "version": "2.7"
  },
  "implementation": {
    "name": "CPython",
    "version": "2.7.13"
  },
  "platform": {
    "release": "4.9.0-6-amd64",
    "system": "Linux"
  },
  "pyOpenSSL": {
    "openssl_version": "1010007f",
    "version": "17.5.0"
  },
  "requests": {
    "version": "2.19.1"
  },
  "system_ssl": {
    "version": "1010008f"
  },
  "urllib3": {
    "version": "1.23"
  },
  "using_pyopenssl": true
}

Sessions and responses aren't thread-safe so the behaviour of calling response.close() and session.close() outside the thread is undefined.


Learning Basic JavaScript Modules

Proposed title of article
Learning Basic JavaScript Modules
Introduction paragraph (2-3 paragraphs):
So the first question either of us can ask is what is a module? Before we get to JavaScript modules am going to take you through what a module is. A module is a function or a group of functions that are similar.  Modules in JavaScript are files containing related code. The modules are used to break code into smaller parts.
Key takeaways:
The following are the key concepts that the learner will learn;
-The learner will understand what are modules are
-The learner will understand the use of the following JavaScript modules
- import module
- export module
- default module
References:
N/A

@IsaacMuthini
Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

@IsaacMuthini
After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations.
We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic it has to serve value to the larger developer community at large.
An option and a great way to write this as an in-depth article and make it more add value to the greater developer community at large would be to walk the reader through the USE of methods and functions by building a unique, different, useful project.

We would love to learn your thought process behind the solution you arrived at using these concepts and topic.
That way a developer could see them in action.


Trying to execute an interface gives unhelpful error

cargo run examples/benchmarks/AStar.roc currently results in:

'TODO turn fn_var into a RuntimeError UnresolvedTypeVar(201)', compiler/mono/src/ir.rs:1004:35

AStar.roc is an interface file, so instead we should give an error like "you can only run app modules, and this is an interface module."

This is solved:
itself?ivo@megaverse:~/roc_code$ roc A.roc
── NO PLATFORM ─────────────────────────────────────────────────── UNKNOWN.roc ─
The input file is an interface module, but only app modules can be
run.
Tip: You can use roc check or roc test to verify an interface
module like this one.
@Anton-4 ?

Thank you @Ivo-Balbaert
$ cargo run -- run crates/compiler/load_internal/tests/fixtures/build/app_with_deps/AStar.roc
    Finished dev [unoptimized + debuginfo] target(s) in 0.49s
     Running `target/debug/roc run crates/compiler/load_internal/tests/fixtures/build/app_with_deps/AStar.roc`
── NO PLATFORM ─────────────────────────────────────────────────── UNKNOWN.roc ─

The input file is an `interface` module, but only `app` modules can be
run.

Tip: You can use `roc check` or `roc test` to verify an interface


 However, Fuchsia now uses HostFuzzer
mode, so only syz-executor (written in C) needs to run on Fuchsia; all
Go code runs on the Host OS (currently Linux).

@mvanotti

Codecov Report

Merging #1510 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1510   +/-   ##
======================================
  Coverage    56.2%   56.2%
======================================
  Files         142     142
  Lines       26415   26415
======================================
  Hits        14847   14847
  Misses      10859   10859
  Partials      709     709

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 b7a277d...7612e69. Read the comment docs.


When setting custom amount allow pasting sat amount

Is your feature request related to a problem? Please describe.
Inputting a specific amount during invoice creation
Describe the solution you'd like
Allow pasting amount from clipboard
Describe alternatives you've considered
TINA
Additional context
E.g. Robosats contract step for bonding on buyer side requires specific sat amounts to be entered, and there are users asking for this feature for more convenience and usability - see https://twitter.com/eko2one/status/1681745875737903105

I'll switch the Text components to Input components that have their state shared with the number pad. This should allow for pasting values in both the SAT and currenecy of choice fields


CSS in AMP template is not minified

Issue Summary
The CSS served in the new AMP templates is not minified, missing out on a considerable reduction in size.
Steps to Reproduce

Load a page using AMP and observe the inline style near the top of the document.

Technical details:

Ghost Version: 0.10.0

The style is 19.63 KB in size and when minified is only 8 KB. This represents a considerable saving, especially given the purpose of AMP.
I have minified this style in my AMP template, example here: https://scotthelme.co.uk/securityheaders-io-updates/amp/

For development it's a big plus that the core file is not minified, I think that's something your theme should take care of, when built.


Unify the Object Model Across Languages

Currently, different language implementations may offer slightly different object models. One example could be that on C# there is a constructor for TextBlock that conveniently takes the text to be presented, whereas an equivalent feature for C++ (and correspondingly JNI) does not exist.
On JavaScript, the object model is basically not prepared to be used for producing cards (create an empty AdaptiveCard, try to parse it, you get a number of issues). I am guessing this is out of the assumption that directly creating the JSON is more convenient from JavaScript that resorting to the model. I would agree, yet a standardized API would be of value anyhow.
A possible solution would be to find/create a DSL that allows for a generic definition of tests that can run within different languages. In my mind it would look something like this.
TEST_GROUP_PROLOGUE(ParseUtilTest)
TEST_PROLOGUE(SelectActionEmptyJsonTest)
TEST_VERSION("C++")
        {
            auto elementParserRegistration = std::make_shared<ElementParserRegistration>();

            auto actionParserRegistration = std::make_shared<ActionParserRegistration>();

            Json::Value json;

            std::shared_ptr<BaseActionElement> selectAction = ParseUtil::GetSelectAction(
                elementParserRegistration,
                actionParserRegistration,
                json,
                AdaptiveCardSchemaKey::SelectAction,
                false);

            Assert::IsTrue(selectAction == nullptr);
        }
TEST_VERSION("C#")
        {
            var elementParserRegistration  = new ElementParserRegistration();
            var actionParserRegistration = new ActionParserRegistration();

            var selectAction = ParseUtil.GetSelectAction(
                elementParserRegistration,
                actionParserRegistration,
                json,
                AdaptiveCardSchemaKey::SelectAction,
                false);

            Assert.IsTrue(selectAction == null);
        }
TEST_EPILOGUE()
TEST_GROUP_EPILOGUE()

Closing as stale