Copy all non-svelte files to output directory

What?
Copy all non-svelte files to output directory.
Why?
Allows users to structure their files as like.
Also useful for things like favicon.ico which should be at the root (unless otherwise specified).

Nice.
Is there a risk of an infinite loop if the build directory happens to be nested inside the site directory?

ooh yeah, this is a good point, will fix that


added singularity.autoMounts to config

otherwise a run with -with-singularity will fail, not being able to find the transcriptome file

My only concern is that this pipeline can easily be used for demo/training purposes, as it's small enough. In these contexts, one might end up running it with singularity but without Slurm (e.g. laptop or VM). If it's confusing, a comment can be added for that line, e.g.
// the line below is required for singularity to mount all input paths, including for transcriptome file
singularity.autoMounts = true

What do you think?
Thanks

What if we add singularity profile specific for that? eg
singularity {
  singularity.autoMounts = true
  singularity.enabled = true
}

cool! just modified the config

thanks Paolo!
and just to let you know, Nextflow has now got its own independent episode in our Singularity tutorial ;-)
I will use these materials as early as this December in Sydney!
Cheers,
Marco

On 19 Nov 2019, at 9:37 pm, Paolo Di Tommaso<EMAIL_ADDRESS>wrote:
@pditommaso approved this pull request.
Well done!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nextflow-io/rnaseq-nf/pull/3?email_source=notifications&email_token=AEBPTFH2OABGVEVPD7R4NOTQUPTYLA5CNFSM4JO7SCPKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCMCCIVA#pullrequestreview-319038548, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEBPTFCF4PCOXRXGKAWMB3LQUPTYLANCNFSM4JO7SCPA.


Improve heaters display

Code cleaning and variables rename for a better display in home assistant

Thx Gus !

Thx Gus !


Export/UI: "Animation" section of export screen should be reorganized

The "Animation" panel when exporting looks like this

Shape keys and skinning have nothing to do with animation so they shouldn't be under the "Animation" section. And having a subsection of "Animation" that is also named "Animation" is dumb.

How about a new "Armatures" section, and moving Shape Keys under "Geometry" section? On that note, I think the Materials/Images options might make more sense under "Include" than "Geometry".

Mockup:

What does "Use Current Frame" do?

The mockup looks great to me. :)

Not sure about "Export Deformation bone only", if this should be in Animation or in Armature


added RC filter adressing #2 and fixed help command

Did that and fixed the .lower() problem that I introduced.

it was issue #3 oh well


change blockquotes to denote parallelism

Hey! Reading through the docs, I think there are two issues that are kind of inter-related...

That all "comments/description" seem to have to go in blockquotes?
That there's a special (hard to remember) syntax for "Run x after/before this (in parallel)".

I think there might be a simplification that will make writing the files easier, and make running things in parallel or not easier too.
First, I think all of the current use of blockquotes should be removed. Instead, let people write the commenting documentation just as normal paragraphs, since we already have the backticks as delineating code blocks to run. This makes the simple cases easier to remember. So the examples become:
## lint

Run ESLint to ensure code quality

\```bash
eslint --fix
\```

After that, we now have blockquotes entirely freed up to be used for special syntax. I think they should be used to define parallelism. For things outside of block quotes, everything is run in series as it's encountered. So that instead of writing the "Run x before this", you can just add scripts in series:
## lint

\```bash
eslint index.js
\```

## test

\```bash
maid lint
\```

\```bash
mocha test/index.js
\```

But then anything you put in a blockquote will be run in parallel, so you can easily do things like:
## start

Run the watcher command and the web server.

> \```bash
> babel ./src --out-dir ./public --watch
> \```
>
> \```bash
> serve ./public
> \```

This would run both the watcher and the web server in parallel, really easily.
You can even specify groups of parallel tasks separated by series tasks, by simply breaking the blockquotes into two with a series task in the middle.

The parallelism that blockquotes denote is for the tasks it's calling, i.e. :
## start

> Run `build:server` `build:client` before this in parallel.

This means calling tasks build:server build:client in parallel when you run maid start.
I guess blockquotes are indeed unnecessary here.

Now the block quotes are totally optional. All the paragraphs will be used as task description.
Also > Run `build:server` `build:client` before this in parallel. now should be Run tasks `build:server` `build:client` before this in parallel.

FWIW, the "Run x before this" is still super confusing. Since it's just a paragraph, it shows up in the readme as plain text, which to the user looks like a helpful recommendation, when really it's exactly the opposite of what you want them to do, since it's being handled automatically.


Enable arm64 build , hopefully we will get a multiarch images without buildx

Description:

Link to tracking Issue:
Testing:
Documentation:

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


blog: add post on starting dev loops with wash dev

Adds blog, target publish date 11/26/24

Looks good - will post just after 9am ET.


Add favicon

Adds favicon to the website

Yes will do! Looks like I accidentally added workflow stuff to the master branch :(


add anchor tag to individual tabs

Right now, if you are linking to Sanctuary Watch from another site, the best you can do is to link to an individual scene. But what if you want to link to a particular tab within a particular modal? Well, you can't do that now, but let's add that feature.
Here is an example. I created the following tab:

It would be great to be able to connect directly to this tab as either:

root-url/instance-slug/kelp-forest#CA_Sheephead_Trend_Pisco
root-url/instance-slug/kelp-forest#Trend_Pisco
some better way

The first option, within the anchor tag, combines the icon and tab title. That makes the anchor tag longer and more ungainly, but reduces the chances for duplicate anchor tag values. Note that special characters are removed from the tab in the anchor tag.
The second option provides just the tab title as the anchor tag. Play around with this to see which option (or some other option as the anchor tag) seems best.
The idea would be, I think, to add an event listener for the onload event for the scene. Upon onload, check the url to see if a .hash is present (the anchor link). If the anchor link is present, go directly to that tab.
Of course, the other half of the equation is that the user has to know what the full url for a tab should be (in case they would want to use that url as a hyperlink). I am not exactly sure how this should be presented in the user. Maybe in either  of the locations in the image above (marked as the red 1 or 2)? And I am picturing that the user would click on the link and that would be copied to the clipboard. Similar to how, here in Font Awesome, if you click on <i class="fa-solid fa-gauge"></i>, that code snippet is directly copied to the clipboard.
Thoughts? This is still a little fuzzy.

If the anchor tag approach to linking to the modal seems like a dead end, another approach might be via the GET HTTP method. You could put, in the arguments of the method, something that would indicate that a specific modal tab should be opened. It would create an odd looking hyperlink though.

currently works, format of URLs would be option 2. Option 1 (or something slightly modified) might be easier though cuz we wouldn't have to explicitly find the modal window on which the figure is found. Also, in case there are redundant tab names, it might be best to include the parent modal:
root-url/instance-slug/kelp-forest#CA_Sheephead/Trend_Pisco

resolved: created async function built on event handlers to open specific tab based on hyperlink:
https://github.com/ioos/sanctuarywatch/blob/ef543d346145f544a38a2d8daf95decb06cddce1/themes/Sanctuary_Watch/assets/js/script.js#L1732
also, modified create_tabs function to facilitate url parsing, and to actually create the URL:
https://github.com/ioos/sanctuarywatch/blob/ef543d346145f544a38a2d8daf95decb06cddce1/themes/Sanctuary_Watch/assets/js/script.js#L1020

Add button to copy tab link to clipboard somewhere

Add button to copy tab link to clipboard somewhere

works as long as browser protocol is https

modified fix to make it work on dev side of things:
added new function called waitForElement, which uses mutation observer to wait for elements to render before firing event handlers instead of timeout (which can get messy, not always intended behavior)


Oort: bad smell check: inferred A SubClassOf B when there is an asserted A SubClassOf R some B

From<EMAIL_ADDRESS>on May 15, 2013 09:30:22
WHERE
ASSERTED A SubClassOf R some B
and
INFERRED A SubClassOf B
Either issue a warning, or add extra info the the "NEW INFERRED" line in the reasoner report
E.g.
NEW INFERRED A SubClassOf B [warning: A SubClassOf R some B asserted]
Original issue: http://code.google.com/p/owltools/issues/detail?id=62

From<EMAIL_ADDRESS>on May 15, 2013 14:07:42
Implemented a method and added it to OORT and assert-inferences, see r1280 for details.
Status: Started


Ready for Packagist??

I updated Codeception/Specify to version 1.0 and it suggested me use this brand new package.
But it seems has not been in Packagist yet.
Is that in progress?

I use it with direct repository in composer, and it works fine for me. Very useful. Hope that it can be released soon, because now Specify not support 'throws' option.


Encryption? Issues. Bot only walking, not performing.

Expected Behavior
Proper functioning bot.
Actual Behavior
Good afternoon,
My bot was properly functioning before the recent API change. Now that the bot is up again, I am able to start it, but it only walks around, not hatching/catching/spinning. Some others are sharing my experience. I downloaded the encrypt.so file, placed it in the PokemonGO-Bot folder. I looked inside my init.py file, but didn't find an encrypt line. Using command+F, it wasn't detected. I suspect my issue is with the encryption part, but I don't know how to rectify.
Any insight would help as I am very new to these programs and code-language.
[14:53:32]  Server seems to be busy or offline - try again - 1/5
[14:53:34]  Starting PokemonGo Bot....
[14:53:35]  [x] Next egg incubates in 3.26 km
[14:53:39] Walking from (XX, -XX) to [XX, -XX] 0.00km
[14:53:44] Walking from (XX, -XX) to [XX, -XX] 0.20km
[14:56:29] Walking from (XX, -XX) to [XX, -XX] 0.15km
[14:58:40] Walking from (XX, -XX) to [XX, -XX] 0.20km
etc
Steps to Reproduce
cd PokemonGo-Bot
virtualenv .
source bin/activate
pip install -r requirements.txt
python pokecli.py
Other Information
OS: OSX

do you have the latest version of the bot?
did you perform a git pull?

It seems you are still using old version, you should get the latest version of the bot.
See #2540

Thanks, guys. I did perform a git pull. As for the version, I ran pip install -r requirements.txt to get the new pgoapi and I also downloaded the encrypt.so file.
Does that constitute updating the version?

@vulgy that should be enough. I found that running pip install --upgrade -r requirements.txt can sometimes resolve out-dated dependency related issues.

Kyle, thank you for that. It returned me this:
Installing collected packages: pgoapi, setuptools
Running setup.py develop for pgoapi
Found existing installation: setuptools 25.1.3
Uninstalling setuptools-25.1.3:
Successfully uninstalled setuptools-25.1.3
Successfully installed pgoapi-1.1.0 setuptools-25.1.6
Unfortunately, that did not alleviate the bot's unresponsiveness.

I have a question for you.
Where did you found your encrypt.so on Mac ?
Can't find it ...

I downloaded it from the slack chat.
I would upload it, but .so files aren't supported in this forum.

Ok thx buddy. I'll see if i can connect on.
Le 7 août 2016 22:11, "vulgy"<EMAIL_ADDRESS>a écrit :

I downloaded it from the slack chat.
I would upload it, but .so files aren't supported in this forum.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PokemonGoF/PokemonGo-Bot/issues/2906#issuecomment-238105387,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIxyjIrvnfrJARyQjXcJMHlDnfSMggzZks5qdjwIgaJpZM4JekHV
.

I can connect on but it reached the integration limit ... Can you send me a DL link via PM or post it here ?

I have found a solution in this way: I deleted my PokemonGo-Bot folder, ran:
git clone --recursive -b dev https://github.com/PokemonGoF/PokemonGo-Bot
(make sure its dev and not master), then the usual:
cd PokemonGo-Bot
virtualenv .
source bin/activate
pip install -r requirements.txt
python pokecli.py
And it worked! Caught my first poke since the API change. Thanks everyone for the help.


build: Replace sim with sim00 and sim01

Summary
follow up nuttx-testing repo change:
commit 08d766faef84e43112b70a08f6f0c54654482024
Author: Xiang Xiao<EMAIL_ADDRESS>Date:   Sun Apr 4 04:21:57 2021 +0800

    Split sim.dat to sim00.dat and sim01.dat

    to speed up the macOS build

Impact
Speed up the build check
Testing
Pass CI

Need merge https://github.com/apache/incubator-nuttx-testing/pull/96 first.

I have to merge this PR by self to unblock CI.


Internal tests run with --disable-private-check

Pull Request Description
Introduces test/Base_Internal_Tests. Modifies the build scripts to run tests with --disable-private-check when name of the test project contains _Internal_. Extracted part of #10714.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] All code follows the
Scala,
Rust
style guides.
[x] Unit tests continue to pass

Another No_Such_Method failure.


[BUG]: Deeply nested queries fail due to table name length

What version of drizzle-orm are you using?
0.30.1
What version of drizzle-kit are you using?
0.20.14
Describe the Bug
When creating a query with deeply nested data, the sql generated uses names based on the relation names that have been set up, with more text being appended to the name for each level of depth.
"table1"
"table1_table2"
"table1_table2_table3"
etc...
If this reaches the limit for the length of a table name, the database will truncate the names to the number of allowed characters, and fail with the error error: table name "documentVersions_workflowStep_workflow_contract_entities_userEn" specified more than once because there were multiple more tables in the name that are cut off. They instead all get truncated to the same string which causes an error.
Expected behavior
Drizzle should either use shorter names upon reaching the limit for a table name, or use aliases within the request that get turned back into the correct names upon response. This ideally should not be something the drizzle user has to worry about, as the query builder should preferably work without having to manually set table names for all the joins.
Environment & setup
This occurs using postgresql

Just ran into the exact same issue

@EamonHeffernan did you figured out anything for this?

I'm not a maintainer, the only workaround I've found in my own code is to either do it without query which defeats the whole point of having the query system, or to instead break it into small enough queries that don't run into this issue. I've attempted to put this issue into the discord to get some attention about it. But this seems like such a simple case to run into because it doesn't take that much nesting to run into it if you have decently long table names.

What about if the table names are hashed? With that we can ensure the length is short and the names are unique to avoid collisions

What about the table names being hashed? With that we can ensure the length is short and the names are unique to avoid collisions

Yeah, I don't think there is any reason this would need to be opt in, this should be just automatically handled because the names are not relevant to the consumer of the query. The only downside would be that it would be slightly harder to debug because the query wouldn't have useful names, but that is better than the query not running at all.

@EamonHeffernan I believe we can still have good debugging even with hashed names, if they're kept in memory in a map whenever a warning/error occurs we can fallback to that map to retrieve the original names and show the query accordingly

Anyone found a workaround for this issue?

Same issue here, any fixes?

This stops me from doing most basic queries with "with" keyword ...how is this not a biggest priority bug fix :(

Like previous commenters are saying, this completely prevents using Drizzle with any small amount of nesting :(
Is there an update from the Drizzle team about this being a priority?

An easy workaround is just giving your relations shorter names, especially for join tables, e. g.
export const customerRelations = relations(customers ({ one, many }) => ({
  o: one(organizations, {
    fields: [customers.orgId],
    references: [organizations.id],
  }),
  mgrs: many(managers),
  ma: ...
  pm: ...
}));

and use these short names in your with queries

Something has to be done to these lines
https://github.com/drizzle-team/drizzle-orm/blob/c8359a16fff4b05aff09445edd63fc65a7430ce9/drizzle-orm/src/pg-core/dialect.ts#L1228
and
https://github.com/drizzle-team/drizzle-orm/blob/c8359a16fff4b05aff09445edd63fc65a7430ce9/drizzle-orm/src/pg-core/dialect.ts#L1284

typeorm fixed this here

For now you can do patch-package with the below patch to fix the issue
`
diff --git a/node_modules/drizzle-orm/pg-core/dialect.js b/node_modules/drizzle-orm/pg-core/dialect.js
index a8dfc1f..560a664 100644
--- a/node_modules/drizzle-orm/pg-core/dialect.js
+++ b/node_modules/drizzle-orm/pg-core/dialect.js
@@ -35,6 +35,7 @@ import { ViewBaseConfig } from "../view-common.js";
import { PgViewBase } from "./view-base.js";
class PgDialect {
static [entityKind] = "PgDialect";

nameMap = {};
async migrate(migrations, session, config) {
const migrationsTable = typeof config === "string" ? "__drizzle_migrations" : config.migrationsTable ?? "__drizzle_migrations";
const migrationsSchema = typeof config === "string" ? "drizzle" : config.migrationsSchema ?? "drizzle";
@@ -73,6 +74,15 @@ class PgDialect {
escapeString(str) {
return '${str.replace(/'/g, "''")}';
}
makeHash(length = 5) {
let result = '';
const characters = 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789';
const charactersLength = characters.length;
for (let i = 0; i < length; i++) {

 result += characters.charAt(Math.floor(Math.random() * charactersLength));

}
return result;
}
buildWithCTE(queries) {
if (!queries?.length)
return void 0;
@@ -973,7 +983,9 @@ class PgDialect {
const normalizedRelation = normalizeRelation(schema, tableNamesMap, relation);
const relationTableName = getTableUniqueName(relation.referencedTable);
const relationTableTsName = tableNamesMap[relationTableName];

   const relationTableAlias = `${tableAlias}_${selectedRelationTsKey}`;

   // const relationTableAlias = `${tableAlias}_${selectedRelationTsKey}`;

   const relationTableAlias = this.makeHash();

   this.nameMap[ `${tableAlias}_${selectedRelationTsKey}`] = relationTableAlias;
   const joinOn2 = and(
     ...normalizedRelation.fields.map(
       (field2, i) => eq(

@@ -1019,7 +1031,7 @@ class PgDialect {
if (nestedQueryRelation) {
let field = sql`json_build_array(${sql.join(
selection.map(

     ({ field: field2, tsKey, isJson }) => isJson ? sql`${sql.identifier(`${tableAlias}_${tsKey}`)}.${sql.identifier("data")}` : is(field2, SQL.Aliased) ? field2.sql : field2

     ({ field: field2, tsKey, isJson }) => isJson ? sql`${sql.identifier(this.nameMap[`${tableAlias}_${tsKey}`])}.${sql.identifier("data")}` : is(field2, SQL.Aliased) ? field2.sql : field2
   ),
   sql`, `
 )})`;

`

thanks for giving this an effort! You should definitely file a PR, you are the hero we need ...but i m pretty sure there will be friction, because this would make reading queries harder with hashed table names, so probably some flag or just take few first letters or sth would be way to go, but creating PR could start a debate

I havent contributed to that many projects. Is it ok to inspire from this? Like how they used crypto and other things

thanks for giving this an effort! You should definitely file a PR, you are the hero we need ...but i m pretty sure there will be friction, because this would make reading queries harder with hashed table names, so probably some flag or just take few first letters or sth would be way to go, but creating PR could start a debate

What about to only enable it if the table/field length exceeds the limit?

Hi, is there any progress on merging #3041 to address this issue?

Facing this issue... It should be fixed ASAP

Any movement on this issue?

Also running into this issue

My implementation here as a patch for drizzle-orm+0.36.4.patch:
diff --git a/node_modules/drizzle-orm/pg-core/dialect.js b/node_modules/drizzle-orm/pg-core/dialect.js
index d7985c8..2c76926 100644
--- a/node_modules/drizzle-orm/pg-core/dialect.js
+++ b/node_modules/drizzle-orm/pg-core/dialect.js
@@ -1006,7 +1006,7 @@ class PgDialect {
         const normalizedRelation = normalizeRelation(schema, tableNamesMap, relation);
         const relationTableName = getTableUniqueName(relation.referencedTable);
         const relationTableTsName = tableNamesMap[relationTableName];
-        const relationTableAlias = `${tableAlias}_${selectedRelationTsKey}`;
+        const relationTableAlias = shortenAlias(`${tableAlias}_${selectedRelationTsKey}`);
         const joinOn2 = and(
           ...normalizedRelation.fields.map(
             (field2, i) => eq(
@@ -1052,7 +1052,7 @@ class PgDialect {
     if (nestedQueryRelation) {
       let field = sql`json_build_array(${sql.join(
         selection.map(
-          ({ field: field2, tsKey, isJson }) => isJson ? sql`${sql.identifier(`${tableAlias}_${tsKey}`)}.${sql.identifier("data")}` : is(field2, SQL.Aliased) ? field2.sql : field2
+          ({ field: field2, tsKey, isJson }) => isJson ? sql`${sql.identifier(shortenAlias(`${tableAlias}_${tsKey}`))}.${sql.identifier("data")}` : is(field2, SQL.Aliased) ? field2.sql : field2
         ),
         sql`, `
       )})`;
@@ -1126,6 +1126,20 @@ class PgDialect {
     };
   }
 }
+
+const aliasMap = new Map();
+const maxLen = 62;
+function shortenAlias(input) {
+  if (input <= maxLen) return input;
+
+  const fromCache = aliasMap.get(input);
+  if (fromCache) return fromCache;
+
+  const shortened = `__${aliasMap.size.toString(36)}__`;
+  aliasMap.set(input, shortened);
+  return shortened;
+}
+
 export {
   PgDialect
 };

This uses a base36 encoded table name which gives an address space which will be enough to run your server considerably longer than the age of the universe many times over, or have a billion table aliases for each atom in the universe.
If you use tables named with double underscores prefixing and suffixing them then this won't work well, so do something different.


[ZEPPELIN-6063] Fix delay in paragraph results rendering in new UI

What is this PR for?
In new UI, the results are rendered only after some interactions, such as a click on the other paragraph.
This PR addresses the issue by ensuring immediate rendering of the results when they are set in the ngAfterViewInit lifecycle hook. Previously, markForCheck() was used after setting this.innerHTML, which scheduled the component to be checked in the next change detection cycle but did not trigger an immediate update.
This has been changed to detectChanges() to force an immediate change detection, ensuring that the results are rendered right after they are set, without needing further user interaction.
What type of PR is it?
Bug Fix
What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/6063

How should this be tested?

Run any paragraph in new UI

Screenshots (if appropriate)
Before

After

Questions:

Does the license files need to update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Thanks, merged to master


distribute_params should use assign_parameters

distribute_params acts on the object's attribute dictionary and does not update the agent's parameters dictionary.
https://github.com/econ-ark/HARK/blob/05ef324cfc7b0351b68063ce3cbcc70a47f62783/HARK/core.py#L1428-L1458
There's a case to be made that HARK should be able to read a distribution for ex ante heterogeneity in a parameter as part of its configuration dictionary. That would be more direct.
Note this is somewhat different from the providing of distributions for the sampling of shocks as part of configuration, see #620

This is a good first issue @nicksawhney

Fixed with #1044


Position (and Department) use PrefLabvel over label if exists.

The updated database fcrepo-sandbox and fcrepo-dev have new data where some positions have a prefLabel soon organizations will have these as well.  The should be used in place of the name if it exists.
Example  (from sandbox data) .  See difference between:

and the profile page:

And see the new JSON for this contact
 "hasTitle": {
                        "@id": "ark:/87287/d7c08j/position/001300",
                        "@type": [
                            "Title",
                            "ucdlib:AcademicMember",
                            "ucdlib:SenateMemeber"
                        ],
                        "prefLabel": "Assistant Professor",
                        "name": "ASST PROF-AY"
                    }

We expect to have something similar like:
  "hasOrganizationalUnit": {
                        "@id": "ark:/87287/d7c08j/dept/011038",
                        "@type": "vcard:Organization",
"prefLabel":"Molecular & Cellular Biology (MCB)",
                        "name": "MOLECULAR & CELLULAR BIO"
                    },


Microverse Trials: Create Tribute Page

Create Tribute Page

Add index.html file
Add style.css file
Add images

[ ] Great job 👍 . Kindly add your HTML / CSS linter configurations to your repository🙏 . This will help to ensure your code keeps to the standards of the microverse organization

[ ] Kindly update your README.md file using the microverse template🙏 . This will help your README.md file to be more descriptive and help visitors understand what your repository is about


lean is not correct in documentation and actual behavior

Hi, I am using feathers-mongoose version 8.5.1 , mongoose 6.0.13, I am installing 'mongoose-lean-virtuals' and the lean attribute that we should pass in order to support that is lean: {virtuals: true}, which does not align with the code in this repo - which demands lean to be boolean.
The thing is that this actually make it work - my question is: how come ? I presume feathers just pass that to mongoose which support that ( with the plugin of course ).
is it true? if so - the documentation and code and options types should support that.

This makes sense. You can see here https://github.com/feathersjs-ecosystem/feathers-mongoose/blob/dc24ee43a54f15b2b8d015d8e26180801ad8afb9/lib/service.js#L68 that feathers-mongoose does pass whatever value you provide to lean. So the types could be updated, but I believe that will be difficult to nail down all of the potential options and will likely just be an any.
Also, the feathers way to handle virtuals is via hooks. Checkout Feathers Schema or withResult

Furthermore, the lean option should be used per service call in params. I believe this is how some other database adapters work, such as sequelize raw. So the service should default to whatever lean option the service is created with, but you can also override it with params
// This would work, but we would have to pluck `lean` off
// the mongoose param before passing to the underlying method
app.service('posts').find({ mongoose: { lean: false } });

// Don't put in mongoose param, make it a vanilla param.
// This would also work and us not have to pluck it off
// of params.mongoose, but its just kinda lonely
app.service('posts').find({ lean: false });


Web Bundle releases?

If you provided web bundles for each release, maybe more people would use this.

Please elaborate on what a "Web Bundle" is as no resource explains it online. But after that the answer will still be no.

Please elaborate on what a "Web Bundle" is as no resource explains it online. But after that the answer will still be no.

https://web.dev/web-bundles

Please elaborate on what a "Web Bundle" is as no resource explains it online. But after that the answer will still be no.

https://web.dev/web-bundles

If it can't be automatic through github actions, it isn't happening

Please elaborate on what a "Web Bundle" is as no resource explains it online. But after that the answer will still be no.

https://web.dev/web-bundles

If it can't be automatic through github actions, it isn't happening

How about hourly deployments with no interaction?
https://github.com/hello-smile6/turbowarp-web-bundle-builder

Please elaborate on what a "Web Bundle" is as no resource explains it online. But after that the answer will still be no.

https://web.dev/web-bundles

If it can't be automatic through github actions, it isn't happening

How about hourly deployments with no interaction? https://github.com/hello-smile6/turbowarp-web-bundle-builder

this isn't at all a scratch project, this is a web application. Also, this is useless. Stop making useless issue reports or you will be denied ability to do so. Also stop making issue reports just to advertise your own products.

Please elaborate on what a "Web Bundle" is as no resource explains it online. But after that the answer will still be no.

https://web.dev/web-bundles

If it can't be automatic through github actions, it isn't happening

How about hourly deployments with no interaction? https://github.com/hello-smile6/turbowarp-web-bundle-builder

this isn't at all a scratch project, this is a web application. Also, this is useless. Stop making useless issue reports or you will be denied ability to do so. Also stop making issue reports just to advertise your own products.

That's just an example. I was showing you that it was possible. Fine, I'll add your repository to the build for that one.

Please elaborate on what a "Web Bundle" is as no resource explains it online. But after that the answer will still be no.

https://web.dev/web-bundles

If it can't be automatic through github actions, it isn't happening

How about hourly deployments with no interaction? https://github.com/hello-smile6/turbowarp-web-bundle-builder

this isn't at all a scratch project, this is a web application. Also, this is useless. Stop making useless issue reports or you will be denied ability to do so. Also stop making issue reports just to advertise your own products.

That's just an example. I was showing you that it was possible. Fine, I'll add your repository to the build for that one.

Have you noticed I said "no" already? Be quiet please


Added configCCModel and other

I just checked it, it's all working but we still need to improve code quality 👍 💯


fix: respect touched forms in params generation

Signed-off-by: kernel-io<EMAIL_ADDRESS>Contributor checklist

[ ] Bug fixes include regression tests
[ ] Features include unit/acceptance tests

Suspect the build is failing because we're pointing at ash master rather than ash main. @zachdaniel worth a rename here too?

🚀 Thank you for your contribution! 🚀

@joshprice fixed in main. It was also failing because Ash upped its required elixir version by using then/2


Update user manual on how to handle patients with more than one alt phone

TODO for me: write the use case and detail plan of attack from dev side

We should just use the notes section for this.

Potential rub is that only the first two phones are searchable, so that's a potential pain point, I agree with you. Just want to make sure we have this decision documented for when someone asks us for it again.
@lwaldsc @NerdyGirl537 @vtmeghan can you weigh in on how often we get patients with 3+ phones and how problematic it is to just keep the top 2 of them?

Honestly, I've never had a patient with more than 2 phone numbers.  Definitely need 2 numbers, That happens a lot.  I think we can make it a training issue: suggest putting the line that will show up in the voice mail as the main number for searches; remind CMs to search on name if the phone number can't be found.  I'm for simplicity and have a concern with trying to cover every, single situation becoming unwieldy and limiting functionality in other ways. Just my 2¢.

Agree with @NerdyGirl537 . @lwaldsc can you weigh in, and if you agree, make any appropriate edits to the user manual about best practices when logging multiple phones?

Swore I already answered this. Agree 100% with @nerdygirl537. I'd
personally love more than two searchable numbers but I also don't want to
make the dash too busy so we're good with two.
On Mon, Oct 24, 2016 at 12:55 AM, Colin<EMAIL_ADDRESS>wrote:

Agree with @NerdyGirl537 https://github.com/NerdyGirl537 . @lwaldsc
https://github.com/lwaldsc can you weigh in, and if you agree, make any
appropriate edits to the user manual about best practices when logging
multiple phones?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/colinxfleming/dcaf_case_management/issues/677#issuecomment-255647854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKFqsGWDq3o64P-9gHNoXA8YbbbtSBFTks5q3Do-gaJpZM4KajkV
.

Sounds like we're in agreement -- @lwaldsc will you make an edit to the user manual detailing this behavior and close?

Updated and closing.


Add Documentation for Poetry Setup on Windows

Setup-
In Powershell: (Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | py - Retrieving Poetry metadata
Add to PATH: To get started you need Poetry's bin directory (Add this Path) in your PATH environment variable

Maybe just add a link to https://python-poetry.org/docs/#installing-with-the-official-installer


W: Lint/UselessAssignment: - False Positive on recursive method with incrementer (+=1)

Apologies if this isn't a bug. But it feels like one. I've tried removing the variable and leaving +=1 which doesn't work, and I've tried underscoring it, which doesn't work as I'd want to because the new variable doesn't exist in the scope.
Expected behavior
Not complain about a variable that has usage
Actual behavior
Running rubocop on the scratch.rb file below throws a warning for useless variables.
W: Lint/UselessAssignment: Useless assignment to variable - tries. (https://github.com/rubocop-hq/ruby-style-guide#underscore-unused-vars)
      looper(tries += 1)
          ^^^^^

Steps to reproduce the problem
# scratch.rb

def looper(tries = 0)
  return if tries >= 3
  puts tries
  sleep tries
  looper(tries += 1)
end

looper

RuboCop version
0.65.0 (using Parser <IP_ADDRESS>, running on ruby 2.6.1 x86_64-linux)

It’s not complaining about a useless variable, it’s complaining about a useless assignment.. The assignment is useless because tries is local to the method, and the method returns without using the variable again after the assignment (the recursive call to looper creates a new instance of the variable) The fix for the warning is
looper(tries + 1)


appengine/go11x/tasks: ScheduleTime not included

In some languages ScheduleTime on a task is demonstrated, but in golang it is not.
It is not made clear if this means we can't use ScheduleTime or if it is just not documented here.
https://github.com/GoogleCloudPlatform/golang-samples/blob/02e03864828e17ba3e86db114679d9521a737581/appengine/go11x/tasks/create_task/create_task.go#L57
I've worked out how to do it, does this project take pull requests?

Thanks for filing this issue! Yes, feel free to send a pull request. Thank you!
(See https://github.com/GoogleCloudPlatform/golang-samples/blob/master/CONTRIBUTING.md for instructions for contributing. In particular, the CLA.)


Updated unit tests in src/protocols/bdx/tests/ to use PW instead of NL.

These changes are replacing nl-unit tests with the pigweed-unit tests, continuing the efforts from #29342 and others.  I updated the tests in src/protocols/bdx/tests/  No changes were made to the logic of the tests.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Jeff Feasel seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Clize time lagging

Clizefied time lagging CLI.  Also tidied up some mess.
Testing:

[x] Ran tests and they passed OK

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

See the complete overview on Codacy

Not picking up commits.  Will re-raise.


Allow Accept header to be customized

The configuration has a headers option, which is great, but unfortunately the makeRequest method overrides the Accept header so a custom Accept header is not possible.
I'd be willing to PR this.

I see what the problem is.  The references to headers here needs to be this.headers.

What about something like this?
if(this.headers['Accept'] === null || this.headers['Accept'] === undefined) {
  xhr.setRequestHeader('Accept', settings.accepts.json);
}

:+1: At the moment I have an API that talks JSON-API except for authentication due to this issue.

@thegranddesign looks good, a PR would definitely be welcome.

@thegranddesign do you still plan to PR this?

Just ran into the same issue. @jpadilla I'll start working on a PR if it's still welcome.

Is this closed now by #178?

@JoshSmith yes!


brcmfmac fails on boot

Description
I was updating my yocto build to use the latest warrior releases from the base yocto, meta-oe, etc, and started getting the below failures on boot without any additional configuration after flashing the SD card. I had updated my meta-raspberrypi to commit 2f0fa9a087b9ded28797d3087ccfa8f48bf5dd13 ( the commit form PR #541 ) and immediately began seeing the failure. I reverted the checkout to commit 5cb49f4d76a311201bd36cf6538e23a59e3d8030 and the problem went away.
While in this state I am unable to use the wifi. iproute2 reports:
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000     link/ether b8:27:eb:f5:ff:50 brd ff:ff:ff:ff:ff:ff
Describe the results you received:
root@raspberrypi3:~# journalctl | grep brcm | head -n 30
Jan 01 00:00:06 localhost kernel: brcmfmac: F1 signature read @0x18000000=0x15264345
Jan 01 00:00:06 localhost kernel: brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
Jan 01 00:00:06 localhost kernel: usbcore: registered new interface driver brcmfmac
Jan 01 00:00:09 localhost kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May  2 2019 02:46:17 version 7.45.189 (r714228 CY) FWID 01-e1db26e2
Jan 01 00:00:09 localhost kernel: brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.136 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2019-05-02 02:31:27
Jan 03 19:41:25 raspberrypi3 NetworkManager[241]: <info>  [1578080485.7238] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/platform/soc/3f300000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill0) (driver brcmfmac)
Jan 03 19:41:29 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:29 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-110)
Jan 03 19:41:31 raspberrypi3 btuart[187]: Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
Jan 03 19:41:31 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:36 raspberrypi3 kernel: brcmfmac: brcmf_dongle_scantime: Scan assoc time error (-110)
Jan 03 19:41:39 raspberrypi3 kernel: brcmfmac: brcmf_netdev_open: failed to bring up cfg80211
Jan 03 19:41:42 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:42 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-110)
Jan 03 19:41:44 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:44 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_tx_power: error (-110)
Jan 03 19:41:47 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:47 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-110)
Jan 03 19:41:49 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:49 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_tx_power: error (-110)
Jan 03 19:41:52 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:52 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-110)
Jan 03 19:41:55 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:55 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_tx_power: error (-110)
Jan 03 19:41:57 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:41:57 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-110)
Jan 03 19:42:00 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:42:00 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_tx_power: error (-110)
Jan 03 19:42:02 raspberrypi3 kernel: brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Jan 03 19:42:02 raspberrypi3 kernel: brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-110)

Additional details (revisions used, host distro, etc.):
Raspberry Pi 3B+, no USB or ethernet devices attached, serial port attached (ENABLE_UART=1), power from a proper RPi power adapter.
Repos used:
git://git.yoctoproject.org/poky: d0f73121551dc98f6924cd77952bf9ebf5ef3dd7
git://git.openembedded.org/meta-openembedded: a24acf94d48d635eca668ea34598c6e5c857e3f8
git://git.yoctoproject.org/meta-raspberrypi: 2f0fa9a087b9ded28797d3087ccfa8f48bf5dd13
https://github.com/mendersoftware/meta-mender.git: 9650b37762443f01cf694deb1e00417751a2a719
Kernel used: 4.14.112 (Mender updates don't play nice with the firmware being on a separate, unupdatable boot partition and changing formats so I'm using the kernel I used with Yocto 2.6)
RootFS is read only
Possibly relevant Yocto config:
PREFERRED_VERSION_linux-raspberrypi ??= "4.14.%"
RPI_KERNEL_DEVICETREE = "\
    bcm2710-rpi-3-b.dtb \
    bcm2710-rpi-3-b-plus.dtb \
"
DISTRO_FEATURES += "bluez5 bluetooth wifi"
require conf/distro/include/yocto-uninative.inc
INHERIT += "uninative"

Are you able to reproduce this issue on core-image-base?

Closing due to lack of feedback.


Unable to test my component with ReadMore imported

<ReadMore> component works fine but I have trouble passing our unit tests, as shown below. I tried to mock this component but without much success. Do you know what is going on?

@Garytophatter can you share your test so that I can try it out

@Garytophatter I have found a solution mentioned here. In your package.json file you will see:
"jest": {
  "preset": "react-native"
}

replace it with
"jest": {
  "preset": "react-native",
  "transform": {
    "^.+\\.(js|jsx)?$": "babel-jest"
  },
  "transformIgnorePatterns": [
    "!node_modules/react-runtime"
  ]
}

Now run your tests and verify.
This has resolved the import issue with jest.
Give it a try!

Unfortunately, I didn't see the line you mentioned in our package.json. I just saw "jest": "^24.5.0".

@Garytophatter I created a new react native project and I could see it. Nevertheless you can simply add this in your package.json:
"jest": {
  "preset": "react-native",
  "transform": { "^.+\\.(js|jsx)?$": "babel-jest" },
  "transformIgnorePatterns": [ "!node_modules/react-runtime" ]
}

I added these lines to the package.json and yarn install, but the test is still failing.

@Garytophatter can you share the error ?
Also make sure the package babel-jest is also installed

I tried mocking this component in the test file, and it ended up working. Thanks for your help!

That's great news @Garytophatter . Also if you can share how you managed to resolve this issue, that'll be very helpful. Thanks 👍

I added this line to mock the component:
  jest.mock('@fawazahmed/react-native-read-more', () => ({
     ReadMore: jest.fn(),
  }));


Customize format function

It'd be nice to be able to modify t to use something other than Ember's fmt function.
import t from 'ember-cli-i18n';

t.fmt = function(string, attributes) {
  /* ... */
};

export default {
  greeting: 'Hello {{location}}!'
};

{{t 'greeting' location="World"}}

Hello World!

@thejameskyle please see associated PR above. The override will look like:
import service from 'ember-cli-i18n/services/i81n';

service.fmt = function(result, values) {
  // run your custom formatter
  return newResult;
}

export default service;

save this file to app/services/i18n.js

ilu


Dockerfiles

Let's set up this environment that is working with environment.yml in a Docker container and deploy it to Dockerhub
Let's also deploy another image on top of it for launching Jupyter lab

I ran into an issue with dependency resolution when creating the env in the docker container... moving PyVista back to the pip section
cc: @prisae

Interesting. Thanks!

When I upload this image to docker hub, should we call it empot, gostin, or what?

Ha, good question. Call it gostin. empot is for electromagnetics and potential field methods, the channel in Swung. However, gostin is more general for geo open-source tie-in, and the name of this hack.
Either way, it is a temporary name I'd say, but gostin is more 'inclusive'.

I will rename the environment.yml as well, and move there pyvista to pip as well again.

:-) @JesperDramsch beat me to it :+1:

Ha sorry


Proposal - Add support for large display devices (Tablets or devices with landscape orientation)

The UI of the AmpRack (as of version 4) works perfectly fine with most mobile devices' screens of small or medium size.
However, it's not working great for tablets.
Main issues are

the app doesn't support the landscape orientation
the app doesn't support a horizontal list view of plugins
also the app doesn't work correctly in the multi-window mode that is available on Android devices with big screens (it crashes during resizing the app)

Note that some of these troubles can be avoided with the usage of developer options like

allow all apps to work in landscape orientation
allow all apps to work with the multi-window mode

However, there would still be a few issues even with such workarounds.
The current app UI in such cases looks like this:

The crash is also observable during this action:

My purpose is to implement a few things of different complexity to help with it.

Add support for landscape device orientation

most of the app UI will still work fine, except for the list of plugins

Change the list of plugins to support a horizontal element view

on devices with a big display: change the Column with the list of plugins to a Row
in such cases set a default Plugin element width (for example, like 360.dp)

Hi,
I've done some work on this. I've combined some UI elements so that the user experience is a little more usable on tablets.
Do try it out and see if I've broken anything. I've only tested it on an emulator, and it's only just some minor UI redesign, so everything should be as functional as before.
Download APK:
https://github.com/djshaji/amp-rack/releases/tag/4.03-tablet
See also https://github.com/djshaji/amp-rack/issues/58

Finally can update this issue, yay.
First of all - thanks for the update.
The good news is that most of the app is working fine and no critical crashes were found.
However, there are quite a few issues with the UI layout on the big screen, as well as a few broken things now.
Will list them below.

The first issue, the most minor one, is the merged Quick screen.
While there is no bug, it looks a bit strange and it's not clear which preset is currently selected.
I would propose duplicating the mixer/tuner panel to be added here, between the switch arrows.
It contains the indicator of the current preset.

There are also a few issues on the Effects screen.

The user is not able to scroll to the end of the list of plugins, it's covered by the Bottom Navigation Bar.
The minor issue, but I would propose to leave only 1 Top App Bar with all the buttons on it.

I like the idea of merging the Recordings screen with the Drums screen.
And overall the UI looks fine.
However, it looks like there are some conflicts in the code of the both tabs.

After clicking on the Play button on the Recordings tab, part of the Drums tab UI disappears (or is covered by some UI element).

After clicking on the Play button on the Drums tab, the Play button on the Recordings tab may be triggered as well.
Note that I found no clear steps to reproduce this one issue.


lambda_function_association event_type incorrect

Description
The lambda_function_association event_type seems to be an impossible key state that would never qualify.
⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Terraform: Terraform v0.14.7

Provider(s): + provider registry.terraform.io/hashicorp/aws v3.31.0

Module: terraform-aws-modules/cloudfront/aws 1.8.0

Reproduction

Steps to reproduce the behavior:

Not using workspaces
Yes we have cleared cache
The lambda_function_association event_type = l.key this seems to be incorrect cloudfront is expecting  [origin-response, origin-request, viewer-request, viewer-response]
I expect to send the event_type like this:
lambda_function_association = [{
          event_type = "origin-request"
          lambda_arn = var.geo-restrictions-lambda
          include_body = false
      }]

then event_type in the module should be:
event_type   = l.value.event_type
https://github.com/terraform-aws-modules/terraform-aws-cloudfront/blob/f13514ff6c66e37458b0d00ba3bd815d8c30855d/main.tf#L135
repeated
https://github.com/terraform-aws-modules/terraform-aws-cloudfront/blob/f13514ff6c66e37458b0d00ba3bd815d8c30855d/main.tf#L186
Code Snippet to Reproduce

module "cdn" {

source = "terraform-aws-modules/cloudfront/aws"

......

default_cache_behavior = {
      target_origin_id       = "platform"
      viewer_protocol_policy = "redirect-to-https"

      allowed_methods = ["GET", "HEAD", "OPTIONS",  "PUT", "POST", "PATCH", "DELETE"]
      cached_methods  = ["GET", "HEAD"]
      compress        = true
      query_string    = true

      cache_policy_id = aws_cloudfront_cache_policy.georegion.id
      origin_request_policy_id= aws_cloudfront_origin_request_policy.forward-all.id

      lambda_function_association = [{
          event_type = "origin-request"
          lambda_arn = var.geo-restrictions-lambda
          include_body = false
      }]
  }

Expected behavior

default_cache_behavior {
            # (12 unchanged attributes hidden)

          + forwarded_values {
              + headers                 = (known after apply)
              + query_string            = true
              + query_string_cache_keys = []

              + cookies {
                  + forward           = "none"
                  + whitelisted_names = (known after apply)
                }
            }

          + lambda_function_association {
              + event_type   = "origin-request"
              + include_body = false
              + lambda_arn   = "xxxxxxxxxxx"
       }
}

Actual behavior
event_type   = "0"
  + lambda_function_association {
              + event_type   = "0"
              + include_body = false
              + lambda_arn   = "XXXXXXXX"

Terminal Output Screenshot(s)

module.cdn.aws_cloudfront_distribution.this[0]: Modifying... [id=E2XF1KSLDDCHS1]

Error: error updating CloudFront Distribution (E2XF1KSLDDCHS1): MalformedXML: 1 validation error detected: Value '0' at 'distributionConfig.defaultCacheBehavior.lambdaFunctionAssociations.items.1.member.eventType' failed to satisfy constraint: Member must satisfy enum value set: [origin-response, origin-request, viewer-request, viewer-response]
        status code: 400, request id: 79c93e7b-99ba-4667-9db5-f3097b8f41b8

  on .terraform/modules/cdn/main.tf line 11, in resource "aws_cloudfront_distribution" "this":
  11: resource "aws_cloudfront_distribution" "this" {

Releasing state lock. This may take a few moments...

Additional context

This is not an issue i had the syntax incorrect
https://github.com/terraform-aws-modules/terraform-aws-cloudfront/blob/f13514ff6c66e37458b0d00ba3bd815d8c30855d/examples/complete/main.tf#L91-L101


on link drag finished, adding a point at (0,0) coords

:tada: This issue has been resolved in version 2.8.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Upsert documentation needs update

This page shows a Java like api, which was luckily fixed, but the documentation was not updated.
I think you should also mention in the documentation, that you do not support vals (which is in some examples), data classes, inheritance, primary constructor parameters and whatever I left out. It's a pain to integrate the library without this information.

@ZsoltBertalan Thanks for the suggestion, we have forwarded it to the right team.


Not possible to change stroke-width on Vue icon components

Discussed in https://github.com/tailwindlabs/heroicons/discussions/946

Originally posted by Jacobtims March  9, 2023
I want to change the stroke-width of an icon on the Vue component.
Like this:
import { PlusIcon } from '@heroicons/vue/24/solid';

<PlusIcon class="h-5 w-5" stroke-width="2"/>

This unfortunately doesn't work.
It's not possible to change the stroke-width of an icon when using the Vue.js package.

Hey! Yep right now we don't expose a prop for stroke-width. If you'd like to change the stroke width you can do so with CSS:
import { PlusIcon } from '@heroicons/vue/24/solid';

<PlusIcon class="h-5 w-5 stroke-2"/>

Hope that helps! Going to close as not a bug (this would be a new feature) and no plans to work on this at the moment.

The stroke-2 class doesn't work on the component.

stroke-[4px] or any amount for that matter will work just fine. So:
<PlusIcon class="h-5 w-5 stroke-[2px]"/>


Synchronize mode transition to memory controller's REF command

This PR improves the moment of transition to payload execution and back.
Now, after writing to the start CSR, Payload Executor will not immediately disconnect the memory controller, but will wait for a REFRESH command. This way the start of payload execution is well-defined in relation to DRAM timings. The first payload instruction is executed 2 clock cycles after the REF command, so the first payload instruction should be a NOOP with timeslice=tRFC-2. On the transition back, the refresh timer in memory controller gets reset, so first REF will be issued tREFI after finishing payload execution. I updated row-hammer payload generation in rowhammer.py to include the additional NOOP and REF.
Please take a look at this @sqazi and say if this is the way we want the transition to work.

1 is the minimal timeslice value for an instruction. Just before mode transition, a refresh has been issued by the memory controller so we must wait tRFC-2. So NOOP with timeslice=max(1, tRFC-2) is actually what is now required in every payload we send to avoid violating tRFC. This is why I included these.
However, the first instruction that is added to the generated payload in the for loop is a refresh, so in order to keep the refresh interval constant I decided to use tREFI in the NOOP. But this depends on how we want to actually handle the refresh generation in the payload, so if you think it should be done differently, than I can change that.

1 is the minimal timeslice value for an instruction. Just before mode transition, a refresh has been issued by the memory controller so we must wait tRFC-2. So NOOP with timeslice=max(1, tRFC-2) is actually what is now required in every payload we send to avoid violating tRFC. This is why I included these.
However, the first instruction that is added to the generated payload in the for loop is a refresh, so in order to keep the refresh interval constant I decided to use tREFI in the NOOP. But this depends on how we want to actually handle the refresh generation in the payload, so if you think it should be done differently, than I can change that.

Oh, I see.  It's to avoid redundant refreshes, since the first thing that will happen in the loop is a refresh.  Looks good.

Oh, I see.  It's to avoid redundant refreshes, since the first thing that will happen in the loop is a refresh.  Looks good.


[Epic] Native StringView support for string functions

Is your feature request related to a problem or challenge?
We are working to add complete StringView support in DataFusion, which permits potentially much faster processing of string data. See https://github.com/apache/datafusion/issues/10918 for more background.
Today, most DataFusion string functions support DataType::Utf8 and DataType::LargeUtf8 and when called with a StringView argument DataFusion will cast the argument back to DataType::Utf8 which is expensive.
To realize the full speed of StringView, we need to ensure that all string functions support the DataType::Utf8View directly.
Describe the solution you'd like
Port all string functions

[x] https://github.com/apache/datafusion/pull/11676
[x] https://github.com/apache/datafusion/pull/11556
[x] https://github.com/apache/datafusion/issues/11786
[x] https://github.com/apache/datafusion/issues/11834
[x] https://github.com/apache/datafusion/issues/11835
[x] https://github.com/apache/datafusion/issues/11836
[x] https://github.com/apache/datafusion/issues/11837
[x] https://github.com/apache/datafusion/issues/11838
[x] https://github.com/apache/datafusion/issues/11852
[x] https://github.com/apache/datafusion/issues/11853
[x] https://github.com/apache/datafusion/issues/11854
[x] https://github.com/apache/datafusion/issues/11855
[x] https://github.com/apache/datafusion/issues/11856
[x] https://github.com/apache/datafusion/issues/11857
[x] https://github.com/apache/datafusion/issues/11858
[x] https://github.com/apache/datafusion/issues/11950
[x] https://github.com/apache/datafusion/issues/11951
[x] https://github.com/apache/datafusion/issues/11952
[x] https://github.com/apache/datafusion/issues/11953
[x] https://github.com/apache/datafusion/issues/11954
[x] https://github.com/apache/datafusion/pull/11962
[x] https://github.com/apache/datafusion/issues/13195

Describe alternatives you've considered
No response
Additional context
See coordination plan with @tshauck  and myself here: https://github.com/apache/datafusion/pull/11787#discussion_r1702294173

One thing I have noticed during implementations is that some functions such as ltrim/rtrim/btrim could be more efficient if they produced Utf8View as output in addition to accepting them as input
For example, in https://github.com/apache/datafusion/pull/11920#discussion_r1713618503 from @Kev1n8  it is actually probably a good idea to always generate StringView as output (rather than StringArray) as it could avoid a copy.
I am thinking once we get the string functions so they can support StringView as input then we can do a second pass and optimize some functions so they produce StringView as output

Inspired by @Omega359 's great PR https://github.com/apache/datafusion/pull/11941, I have some suggestion on testing Utf8View support for functions:
Although most implementation is adapted from existing implementation, but the execution takes another path, so I think comprehensive end-to-end tests are still needed.
The good news is there already exists sqllogictests for original string functions, the only thing to do is to duplicate existing testings with Utf8View
Here are the examples on how to adapt existing test cases for Utf8View input

For functions takes scalar value, use arrow_cast() like https://github.com/apache/datafusion/pull/11941/files#diff-51757b2b1d0a07b88551d88eabeba7f74e11b5217e44203ac7c6f613c0221196
For functions read from a table, string column can be converted to Utf8View column like https://github.com/apache/datafusion/blob/2cf09566af7d7d5f83a8bdff5f0adda97d40deee/datafusion/sqllogictest/test_files/string_view.slt#L30-L42

We are making pretty good progress here -- just a few more functions left 🚀

I think we can claim this is completed. Follow on work is tracked in

https://github.com/apache/datafusion/issues/13504

🎉


Integrate logging into the TypeScript API Client

It would be helpful to enable logging in the RPC client.  Pino (https://getpino.io) looks like a reasonable choice to integrate.

This has been done.


Aggregation using lookup other collection with filters

Hey everyone!
I just try to "translate" mongo-query to kmongo-query using typed query. But it seems difficult.
My example models:
data class Book(val id: Long, val path: List<Long>, val name: String...)
data class Article(val id: Long, val bookId: Long,  val status: String, val authors: List<String>...)

Books are in one collection "objects". Articles are in collection "articles".
The main target - to get list of Articles with every field.
So I wrote a query by sql in IDEA (may be so it would more comfortable to understand my query):
SELECT objects.id as 'book_id',
articles.id, status, bookId, authors
FROM objects
JOIN articles on articles.bookId = objects.id
WHERE path in (4007) AND name = 'Adventure' AND status in ('New');

In console I got a mongo-query(a bit croped extra not meaningful fields):
.getCollection("objects").aggregate([
             {
               $project: {"objects": "$$ROOT", "_id": 0}
             },
             {
               $lookup: {
                 localField: "objects.id",
                 from: "articles",
                 foreignField: "bookId",
                 as: "articles"
               }
             },
             {
               $unwind: {
                 path: "$articles",
                 preserveNullAndEmptyArrays: false
               }
             },
             {
               $match: {
                 $and: [
                   {
                     $and: [
                       {"system_objects.rootPath": {$in: [4007]}},
                       {"system_objects.type": {$eq: 'Adventure'}}
                     ]
                   },
                   {"commands.status": {$in: ['New']}}
                 ]
               }
             },
             {
               $project: {
                 "id": "$articles.id",
                 "authors": "$articles.authors",
                 "status": "$articles.status",
                 "bookId": "$articles.bookId",
                 "_id": 0
               }
             }
       ])

How could I write it with kmongo typed query? I tryed to read a sample lookup in docs, in kmongo-core-tests, but my attempts to make something similar failed.Thanks!

You can look at this unit test: https://github.com/Litote/kmongo/blob/0ae151adda35e08001142410081194cd88fe6871/kmongo-core-tests/src/main/kotlin/org/litote/kmongo/AggregateTypedTest.kt#L271
In debug mode, you can also use the .json extension to see the translation of your typed query.
https://github.com/Litote/kmongo/blob/0ae151adda35e08001142410081194cd88fe6871/kmongo-core-tests/src/main/kotlin/org/litote/kmongo/AggregateTypedTest.kt#L357
If it does not solve your issue, please ask on https://gitter.im/kmongoo/Lobby channel
HTH


Fix incorrenct pip version in pip-uninstall step

Try to fix #700
Currently pip version is pinned to 9.0.2 and is installed in /steps/python
Then pipenv is installed in steps/pipenv. This step will also upgrade pipenv which means pip is changed back to latest version 10.
Finally steps/pip-uninstall is called and this step will call pip-diff which called from pip.req import parse_requirements. However, pip 10 does not has pip.req and then exception is raised.
So --upgrade-strategy only-if-needed is added when installing pipenv to make sure only pipenv is upgraded while pip is kept as older version.

Close since latest version of pipenv requires pip 10. The pip-diff should support pip 10 instead.


Handle multiple imports in one use statement

Closes #563
This enables a wider range of cases than the one mentioned in the issue. Specifically, the target is to eventually support all patterns supported by Rust: https://doc.rust-lang.org/reference/items/use-declarations.html
Right now, the following should work:
use a::b::{c}
use a::b::{c, d}
use a::b::{c as abc, d as abd}
use a::b::{c as abc, d::{e, f::g as abdfg}}
use a::b::{c as abc, d::{e, f::g, *}}
and so on.
Using Self is not yet covered.
The parsing algorithm is recurisve since a list of items could have its own list of items etc.
I still need to add a comprehensive test but here I'm converting some of the existing tests to use the newly supported method which gives extra coverage.
Edit: Added a test that covers a few cases. The remaining gaps, I believe, are:

Supporting self (as in: use a::b::{self as ab, c as abc};)
Handling the case where we have a trailing as after the }. Rust erros out for this. e.g. use a::{b, c} as d (this, of course, is meanignless).

Edit 2: Two more changes:

Handling trailing as after the }.
Handling non-final * more generically in the language file.
So, the following should give a parsing error:
use a::b::*::c
use a::b::c::{d, e::*::f}
use a::b::{c, d} as e

CI is failing for code formatting format. Rust has an amazing canonical formatter that you can use with cargo fmt.

@adlerjohn @sezna quick question: I don't see the test I added (multi_item_import) running here in CI: https://github.com/FuelLabs/sway/runs/4722647594?check_suite_focus=true - is there something I'm missing?

It's running here actually (blame GitHub actions for being opaque): https://github.com/FuelLabs/sway/runs/4722647594?check_suite_focus=true#step:11:775

It's running here actually (blame GitHub actions for being opaque): https://github.com/FuelLabs/sway/runs/4722647594?check_suite_focus=true#step:11:775

Oh that's great! - I swear I looked there but couldn't find anything. I was relying on my browser to search through the page but it wasn't returning anything. I should've done a manual inspection instead. Thanks John!

You can also verify the tests run by running cargo run in the test directory. The only requirement is that fuel-core must be running.

I was relying on my browser to search through the page but it wasn't returning anything. I should've done a manual inspection instead.

Yeah I tried control+f at first and it didn't return anything. You actually have to go to the top-right and search through that box 🤷

You can also verify the tests run by running cargo run in the test directory. The only requirement is that fuel-core must be running.
I ran the tests locally before committing and they were okay! I just thought maybe Clippy is using an older version of the test directory or something like that (which in retrospect doens't make much sense).

Is this intended to be a draft or should we review it?

Is this intended to be a draft or should we review it?

This is ready for review now. I made additional changes. The only remaining gap is supporting Self.

The only remaining gap is supporting Self.

Can you file an issue describing the missing feature? Implementing in can be left to a subsequent PR.

The only remaining gap is supporting Self.

Can you file an issue describing the missing feature? Implementing in can be left to a subsequent PR.

Done: https://github.com/FuelLabs/sway/issues/589

I'm not sure why CI is failing. I can't reproduce the problem locally. Is this an OOM issue like this test https://github.com/FuelLabs/sway/blob/c55f7e76b010f9a0b7abcac2b7cfd6155a4236a7/test/src/e2e_vm_tests/mod.rs#L18 ? My test is very similar to it.

This looks like the VM reverted, which is what it does in the case of a panic, which is different. Not sure why this one is hitting a VM panic.
But yeah, in general, we have a memory overhead issue when declaring dependencies. Minimizing the number of dep statements should help.
I'll take a look at why you're hitting a REVERT. It's not immediately clear to me.

This looks like the VM reverted, which is what it does in the case of a panic, which is different. Not sure why this one is hitting a VM panic.
But yeah, in general, we have a memory overhead issue when declaring dependencies. Minimizing the number of dep statements should help.
I'll take a look at why you're hitting a REVERT. It's not immediately clear to me.

I needed to make one more change so CI will now run again. We'll see if the problem persists.

I still cannot reproduce the CI test failure locally. I tried running the test individually as well as running the full suite (while fuel-core is running). So, in my last commit, I reduced the size of the test to see if that helps.

cc @sezna for review before merge conflicts happen 😂

Really weird that the VM was hitting a revert, but I guess if that fixed it...I'll keep this in mind if we see that happen again


Add the ability to update a deployment

'My Appliances' page is currently a log of launched instances but should be more of a dashboard allowing live view of the deployments and more control.
For starters, enable the status of an appliance to be updated according to the state of the cloud resource. This will require access to the user's credentials across all providers used for deployments. To limit the number of requests and credentials required, perhaps it would be good to just update the status of deployments launched in the past week, or month, or? and then allow each individual deployment to be explicitly updated.

Base implementation available in https://github.com/galaxyproject/cloudlaunch/commit/467def0f88282245d397f67d19694fdfdab4f636

Done in https://github.com/galaxyproject/cloudlaunch-ui/pull/19


fix(material-experimental/theming): Update color palettes

Changes the way M3 color palettes a bit to make the color choices more in line with what the spec expects. In particular, select the secondary palette automatically based on the primary palette (secondary is intended to be a more muted version of primary). We still allow the user to select what tertiary color to pair with their primary, since the spec doesn't make the same sort of assumptions about the tertiary color.
Note: because our demo targets styles at the .mat-primary, .mat-accent, .mat-error classes, it winds up overriding the default color combo that users would see out of the box for the mat-select (a primary form-field with a secondary selected option). This is one example where the M2 color="primary/accent/warn" API doesn't quite align with how colors work in M3. We do not expect users to apply colors in this way, and we probably shouldn't do it in our demo either. For now I've added an extra checkbox to the select demo that lets us observe the form-field/select combo users would see out of the box without our overrides.

I should also add that if we want different base colors for the palettes themselves, we can easily update them. I wrote a little snippet to extract values from https://m3.material.io/theme-builder#/custom into the format we need, so just lmk what colors you'd like


Does the TouchID example work with XCode 8?

Hi,
The example looks really cool! I gave it a try for the TouchID example but didn't get much luck.
I have XCode 8, here is what I have tried

Clone this repository
Open Mobile-Sample.iOS/Passwordless-TouchID/CustomUI/Swift/MyTouchID.xcworkspace
XCode 8 asked if I want to convert Swift 2.3 to 3, selected No
Set ClientID and Domain in Info.plist
Try to build, failed with "Use Legacy Swift Language Version (SWIFT_VERSION) is required to be configured..."
Go to "Build Settings", set "Use Legacy Swift Language Version" from "Unspecified" to "Yes"
Build again, failed with 9 Swift compiler errors. (screenshot attached)

Am I missing any steps?
Thanks

If I try the Passwordless-TouchID/Lock/Swift/Passwordless-TouchID.xcworkspace example with a similar procedure, I get the following errors instead. Could you throw some light on this, please?


Take mutable reference instead of moving in callbacks

Most of our callbacks just consume part of the arguments, which are usually protobuf messages. Protobuf messages are usually too big in memory to be moved around frequently. If they are moved by pointers, a lot of memory copy can be avoided.

Hi! I would like to work on this issue if it's up for grab. Could you give me some pointers on where to begin?

Sure. You can start with src/raftstore/store/msg.rs. There are several definitions of Callbacks, you may need to change the signature from |M| to |&mut M|. If M is a combination of two large struct, it's better to separate them.

Do you still need help with this?

Do you still need help with this?

Yes please!

@nrc great! I'd like to help with it but I'm heading to Vancouver today, so will have to wait until I'm settled there. About to board 🙂

In looking at #5444 i made these comments:

@Arve Knudsen I think the lifetime formulation you'd want for this is more like

pub type WriteCallback = Box<dyn for<'a> FnOnce(&'a mut WriteResponse) + Send>;

using a 'higher rank lifetime' for the callback's lifetime (https://doc.rust-lang.org/nomicon/hrtb.html)

but i tried it and i think it's very hard to accomplish what the issue describes

i see lots of these callbacks immediately sending the argument over a channel

which pretty much precludes using a non-static lifetime

So for at least that case unless somebody can restructure all the callbacks to not use channels that they can't receive a reference. A Box might still be an improvement, particularly since these channel sends are going to each involve their own moves.
@BusyJay maybe you can take a look at #5444

I've taken a stab at this in #5444, but using boxed values instead of references since references led to some nasty lifetime conflicts. @brson and @Hoverbear provided advice.


How to deploy it on local.[enviroment variables]

After i try to deploy for 3 days, i can't stall not deploy it on my computer.     I don't know how to deploy enviroment variables.
After i seted these
process.env.SESSION_STORE = 'local';
process.env.NODE_ENV = development
it shows:
{"name":"threatdragon","hostname":"DESKTOP-5O3JJ6D","pid":17136,"level":50,"msg":"owasp threat dragon failed to start up","time":"2020-06-21T12:40:43.293Z","v":0}
{"name":"threatdragon","hostname":"DESKTOP-5O3JJ6D","pid":17136,"level":50,"msg":"OAuth2Strategy requires a clientID option","time":"2020-06-21T12:40:43.293Z","v":0}
Error: secret option required for sessions
at session (D:\CodeSpace\Final_project\node_modules\express-session\index.js:200:12)
at Layer.handle [as handle_request] (D:\CodeSpace\Final_project\node_modules\express\lib\router\layer.js:95:5)
at trim_prefix (D:\CodeSpace\Final_project\node_modules\express\lib\router\index.js:317:13)
at D:\CodeSpace\Final_project\node_modules\express\lib\router\index.js:284:7
at Function.process_params (D:\CodeSpace\Final_project\node_modules\express\lib\router\index.js:335:12)
at next (D:\CodeSpace\Final_project\node_modules\express\lib\router\index.js:275:10)
at csp (D:\CodeSpace\Final_project\node_modules\helmet-csp\dist\index.js:53:13)
at Layer.handle [as handle_request] (D:\CodeSpace\Final_project\node_modules\express\lib\router\layer.js:95:5)
at trim_prefix (D:\CodeSpace\Final_project\node_modules\express\lib\router\index.js:317:13)
at D:\CodeSpace\Final_project\node_modules\express\lib\router\index.js:284:7

D:\CodeSpace\ow\owasp-threat-dragon> set SESSION_SIGNING_KEY=local & set NODE_ENV=development & npm start

<EMAIL_ADDRESS>start D:\CodeSpace\ow\owasp-threat-dragon
node server.js

{"name":"threatdragon","excludes":["req-headers","res-headers","res","req","short-body","body","response-hrtime","incoming","user-agent","response-time","http-version"],"hostname":"DESKTOP-5O3JJ6D","pid":2780,"level":50,"security":true,"msg":"local session store used - should only happen in dev environments","time":"2020-06-21T20:16:09.056Z","v":0}
{"name":"threatdragon","hostname":"DESKTOP-5O3JJ6D","pid":2780,"level":50,"msg":"owasp threat dragon failed to start up","time":"2020-06-21T20:16:09.085Z","v":0}
{"name":"threatdragon","hostname":"DESKTOP-5O3JJ6D","pid":2780,"level":50,"msg":"OAuth2Strategy requires a clientID option","time":"2020-06-21T20:16:09.085Z","v":0}

this is how i run the code, i try to edit session.config.js,   and try to run the code with command line,   but they all doesn't works.        I don't know how to set "OAuth2Strategy requires a clientID option",

Hello @ZhangK123 , you need to set up all these environment variables:

GITHUB_CLIENT_ID
GITHUB_CLIENT_SECRET
SESSION_SIGNING_KEY
SESSION_ENCRYPTION_KEYS
SESSION_STORE
NODE_ENV

I agree the documentation is not very explicit, and it probably needs documenting more fully.
Once you have all the steps in https://github.com/settings/applications/new then you end up with entering these exports to set up your env vars:
export GITHUB_CLIENT_ID=XXXX (your github username)
export GITHUB_CLIENT_SECRET=XXXX (your github password)
export SESSION_SIGNING_KEY=XXXX(32 byte long random key)
export SESSION_ENCRYPTION_KEYS='[{"isPrimary": true, "id": 0, "value": "XXXX(32 byte key)"}, {"isPrimary": false, "id": 1, "value": "XXXX(32 byte key)"}]'
export SESSION_STORE=local
export NODE_ENV=development

OK Thank you i will try it now.

I will try and give a step-by-step guide sometime in the next day or so, but in the meantime do you want to try the desktop application first? It is easier to set up and once you have evaluated it you can then move on to using github to store your model files.
Threat Dragon Desktop version is here https://github.com/owasp/threat-dragon-desktop and the install is easy once you have downloaded the source:
https://github.com/owasp/threat-dragon-desktop/archive/main.zip
or cloned it:
git clone https://github.com/owasp/threat-dragon-desktop
npm install
npm run start

There is also version 1.2  installers at https://github.com/mike-goodwin/owasp-threat-dragon-desktop/releases/tag/v1.2

I will try it. Thank you.

Hello @ZhangK123
here are the steps to set up the environment variables:

In your github account, go to Settings -> 'Developer settings' -> 'OAuth Apps' -> 'New OAuth App'

fill out the form with the following:
Application name: not critical, suggest something like 'Threat Dragon'
Homepage URL: http://localhost:3000
Application description: not critical, suggest something like 'threat dragon for local development'
Authorization callback URL: http://localhost:3000/oauth/github

Regsister the application, screenshot below

In this new OAuth App, note the values for Client ID (for example<PHONE_NUMBER>0123456789) and Client Secret (for example<PHONE_NUMBER>abcdef0123456789abcdef01234567)

You now have all the info to set up the environment variables:

[ ] GITHUB_CLIENT_ID from  Client ID  above, for example export GITHUB_CLIENT_ID=<PHONE_NUMBER>0123456789
[ ] GITHUB_CLIENT_SECRET from  Client Secret  above, for example export GITHUB_CLIENT_SECRET=<PHONE_NUMBER>abcdef0123456789abcdef01234567
[ ] export NODE_ENV=development
[ ] export SESSION_STORE=local
[ ] SESSION_SIGNING_KEY as a random 32 character hexadecimal key, for example export SESSION_SIGNING_KEY=11223344556677889900aabbccddeeff
[ ] SESSION_ENCRYPTION_KEYS has the same 32 character key, for example export SESSION_ENCRYPTION_KEYS='[{"isPrimary": true, "id": 0, "value": "11223344556677889900aabbccddeeff"}]'

you should now be able to start the threat dragon webapp using npm run-script start and then navigate in a browser to "http://localhost:3000/"
Hope this works OK for you, if not then get back to me

Thank for your help. I finally successfully set up the enviroment variables
This is how i set these variables in Win10:
Add these lines to ./td/app.js:
6      try {
7             process.env.GITHUB_CLIENT_ID = 'a12345bc123aa123bb12 ';
8             process.env.GITHUB_CLIENT_SECRET = '0123456789abcdef0123456789abcdef01234567';
9             process.env.NODE_ENV = 'development';
10           process.env.SESSION_STORE = 'local';
11           process.env.SESSION_SIGNING_KEY = '11223344556677889900aabbccddeeff';
12               process.env.SESSION_ENCRYPTION_KEYS = '[{"isPrimary": true, "id": 0, "value": "11223344556677889900aabbccddeeff"}]'
......
Save then run the code in the cmd with "npm start"

Hello @ZhangK123 - good news that you are now running Threat Dragon, I hope you like it.
I realise that I had sent you the example commands for Linux / MacOS, not Windows ... I am a linux sort of guy myself. I will make sure I updated the instructions with Windows commands as well


Fix titles in test, broadcast and interact with network pages in SDK docs - closes #540

closes #540

Hi Mona, Apologies this was an error...You are correct 'Hello World' was done in #539

OK, I found a couple of occurrences of references to the old titles and have now updated and pushed them into this branch.  Please have a quick look Mona, thanks.


Unable to import CSV or XLSX files into OnTask on 3.0.3

We've updated to 3.0.3 but when there appears to be a bug, in importing both XLSX and CSV files.

CSV file
I tried to upload the same CSV file that I submitted as part of my bug report for issue #99, I get an error indicating that utf8-8 is an unknown encoding (CSV)

What encoding should we now be using?

XLSX file:

Uploading this file results in a "System Error" in the Table tab in OnTask v3.0.3. Unlike similar errors before, refreshing does not cause this to disappear

I've attached the CSV, XLSX and the entire workflow.
report.zip
P.S.Thanks for all the fast fixes!

This is a very strange regression. The word "utf8-8" is not used anywhere in the tool. Thanks for posting the report with the workflow. I'll take a look at it and see if I can replicate the bug.

I just tried (production B.3.0.3)

Importing  the workflow and "merging" both the CSV and XLSX. No bug found
Creating a new workflow and "loading" both the CSV and XSLX. No bug found.

And, as I said in my previous comment, the word "utf8-8" does not appear anywhere in the platform.
The next idea that comes to mind is if you can check, after you get the system error, the file ontask_b/logs/django.log and ontask_b/logs/project.log. These two files collect warnings and errors that are produced during execution. We may have a bit more insight about this glitch.

Thanks for trying - after further investigation, it seems the problem is on our end. A modification we made to an unrelated change in a different file caused the problem.
Closing issue. thanks.


Add a new pkgdev commit mangle to remove stable keywords

One of the most common maintenance tasks in the tree is a simple version bump. With this mangle, pkgdev commit can automatically remove the stable keyword from ebuilds copied from a prior version.
This should reduce contributor mistakes, and save developers time on both code review and manually editing keywords for their commits.

Following some discussion in #gentoo-dev-help
--mangle false allows this to be disabled on a per-commit basis, piggybacking the existing option. @thesamesam expressed some opinion that this should have a separate toggle, but I felt like general helpful mangling all kind of fit well under that existing flag.
One problem I realized  with this, is that it could destabilize a package unintentionally if the whole package is moved by git mv
For example git mv old-category/package new-category-package  or git mv category/oldname category/newname would be caught up in this, and the new name would lose it's stability flags.

I've added a second commit to cover the scenario where a package is renamed or moved to another category.
Because git treats all add & delete in the same commit as mv operations, we need to use a different approach to distinguish the two scenarios, we're now only removing stable keywords when the PV changes.
Happy to squash the commits, but I've left them separate until discussion is a bit further along.


Fix building CLI on Windows

I was unable to build Wren CLI on Windows using vs2017. I had to do some changes in order to fix it:

I updated libuv dependency in repository from v1.10.0 to v1.13.0, because current version didn't support vs2017.

I changed how visual studio is building libuv. Before it was downloading another copy of libuv from github, instead of using that from Wren repository. Now nothing is downloaded, it is directly compiled from files in deps/libuv.

I'm keeping directory with libuv tests, because when you are compiling it using vcbuild.bat you cannot choose which project you want to build and you have to build everything: library, tests and benchmarks. Without tests directory build on Windows won't work.

I changed how Windows is detected by preprocessor. It wasn't working for me, so I looked at some more mature cross-platform project and found the proper way to do this. I used this material as a reference: link.

I had to change which runtime library we are using, because libuv was using different one and there is no command line option in vcbuild.bat which you can use to change that (as far as I can see). This avoids linking both runtime libraries at the same time (and a linker warning).

And some other smaller things which I won't discuss unless someone asks about them.
With those changes you can build Wren CLI on Windows using vs2017. It works both in debug and release mode. There is a small linker warning in debug mode which is connected to another difference between our and libuv options.
I didn't test it on linux and mac, so please do so if you can, I hope I didn't break anything.

This PR is no longer needed :) It's appreciated though.
The Wren CLI repo has a new release and that includes all the build fixes for Windows and all platforms.
https://github.com/wren-lang/wren-cli


Random RuntimeException: Another cursor derived from this client is in exhaust

        $cursor = Store::DB()->collection($this->GetCollection())->find($query);
        $list = [];
        foreach ($cursor as $d)
        {
            $list[] = $d;
        }

MongoDB\Driver\Exception\RuntimeException: Another cursor derived from this client is in exhaust
By the way: this error message is simply a bug itself. English words. But very strange message points me towards what? ;)
Server is up and running. Other queries succeed.

I experimented with removing the $query parameter in the code above. Now the apache log says:
child pid 64953 exit signal Segmentation fault (11)

If i do inside of Store::DB()->collection():
$client = new \MongoDB\Client(null, [], ['typeMap' => ['root' => 'array', 'document' => 'array', 'array' => 'array']]);
$cursor = $client->selectCollection(Store::DB()->name, $collectionName);
return $cursor;

The $cursor->find() segfaults or has this weired error.
If i put the same ($collectionName becomes ->GetCollection():collectionName) code above the find() call, it works.

Can you share the MongoDB and driver versions in use? phpinfo() should report version information for the driver and the libmongoc and libbson libraries it is using.

MongoDB\Driver\Exception\RuntimeException: Another cursor derived from this client is in exhaust
By the way: this error message is simply a bug itself. English words. But very strange message points me towards what? ;)

That error message emanates from libmongoc, but I would only expect it if another cursor on the same client instance was opened with the exhaust option (discussed here).

I experimented with removing the $query parameter in the code above.  That may be a bug in the extension.
I'll note that since you opened this issue, we released 1.1.7 of the extension, which fixed at least one segfault related to cursor usage.

Unrelated to the actual problem, I would suggest using MongoDB\Driver\Cursor::toArray() or simply iterator_to_array() in lieu of foreach ($cursor as $d) { $list[] = $d; } if you'd like to convert the cursor into an array of documents.

Experienced the same issue with the 1.1.5 version of the driver. When updating to 1.1.8, everything worked fine!

@RobIsHere: Closing this due to inactivity and in light of @pietercolpaert's comment that a similar error may have been resolved in 1.1.8. If the issue persists and you're able to address my last questions, feel free to re-open.
Should the issue persist, I'd appreciate if you could attempt reproduction on driver version 1.2.0alpha2. This was recently released and includes significant changes to our connection handling and persistence along with a bump to our dependency on libmongoc. Thanks!


[FEATURE REQUEST] Display Responses on Multiple Lines

I really love the plugin and the feature of adding prompts. However, I find it inconvenient that the response is displayed on a single line. It would be great if the responses could be displayed on multiple lines to improve readability. Currently, I have to either copy the response or open a text editor to see what the engine replied. It would greatly enhance the user experience if the responses could be readable before selecting one of the option. Thank you!

Hi @ibrahim-kabir, I definitely like your suggestion, however this is something that I cannot control unfortunately. You could reach out to the creators of FlowLauncher to see if they are interested in adding such a feature.
Alternatively, you can go to the settings to turn on the file preview. That should give you a tiny bit more text.
Good luck!


Add interface mapping enricher

It would be handy to have interface names in metrics.
This could look like a simple map in yaml:
…
  interface_mapper:
    0: igb0
    1: igb1

with fields: in_interface_name, out_interface_name.

Interesting idea! I could see this being expandable for several fields and not just interfaces and calling it like field_mapper or something so you aren't just limited to interfaces, especially for things like sampler_address if you have multiple routers sending flows to a central Morbius instance. Could even be kinda loosely based on Prometheus relabel_configs.
  field_mapper:
    fields:
      - source_field: in_interface
        target_field: in_interface_name
        mapping: &interface_mapping
          0: igb0
          1: igb1
      - source_field: out_interface
        target_field: out_interface_name
        mapping: *interface_mapping

That's definitely a lot more verbose than your example, but technically more flexible.
There's also an existing precedent for using text/template in the config so that could also be an optional thing if you wanna get really advanced.
      - source_field: sampler_address
        target_field: sampler_name
        mapping:
          <IP_ADDRESS>: router1
          <IP_ADDRESS>: router2
      - source_field: out_interface
        target_field: out_interface_name
        template: &interface_template >
          {{ if eq .Msg.sampler_name "router1" }}
          igb{{ .SourceField }}
          {{ else if eq .Msg.sampler_name "router2" }}
          eth{{ .SourceField }}
          {{ end }}
      - source_field: in_interface
        target_field: in_interface_name
        template: *interface_template

Another consideration: the enrichers are initialized and executed in a certain order: https://github.com/sapslaj/morbius/blob/c751d232737e39ecf26cf09d869405fd3261fa4e/config/config.go#L68-L87
https://github.com/sapslaj/morbius/blob/c751d232737e39ecf26cf09d869405fd3261fa4e/transport/transport.go#L115-L117
I guess it would make sense to have something like this be at the end of the pipeline so you could potentially override labels as needed.

Yeah, this is an excellent proposal.

I've got a little bit of time on my hands so let me see what I can hack up,

Okay I've got a quick proof-of-concept up in #8. It still needs a lot of work but it seems to be working alright with just a quick smoke test.

I finally got around to cleaning up my PoC and getting that merged. I'm hoping to finish up #9 before cutting 0.2.0.

Thank you!