Clearly state the limitations of using script-block syntax for passing filter arguments, recommend using exandable strings instead

If you use {...} (a script block) to bind to a [string]-based parameter such as -RecipientFilter, the verbatim contents of the script block (everything between { and }) is passed.
This precludes using variable references and expressions in filters, and this fundamental limitation should be stated in the topics of all cmdlets that accept filters, and examples with variable use need to be given.
Better yet, given that wanting to reference variables in filters is probably the typical use case, do not recommend using { ... } at all, and instead advise users to use strings, notably expandable strings ("...") in order to embed variable and expression values.
I see that some docs were improved to at least show the expandable-string technique - e.g., in https://github.com/MicrosoftDocs/office-docs-powershell/pull/3840/files - but it's important to do it comprehensively.
See this StackOverflow answer and this related one in the context of Active Directory.

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

ID: cecbe245-8bcd-0247-f334-01754d0a69d1
Version Independent ID: c9c2f732-afb3-38b6-c378-4fe3a909a918
Content: New-AddressList (exchange)
Content Source: exchange/exchange-ps/exchange/email-addresses-and-address-books/New-AddressList.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

Hi @mklement0, thank you for your feedback.
Let me check what we can do here.

OK. I updated the descriptions and examples wherever there was a Filter or RecipientFilter (or *Filter parameter that was a string).
I'll follow-up by finding and fixing similar examples in the Exchange/Exchange Online repo
Thanks for the feedback.

@dariomws306  Thank you very much for the contribution. @chrisda  thanks for updating the documentation with PR. @mklement0 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

I appreciate the quick turnaround and the encouragement.
One thing I noticed - and since I don't have access to the cmdlets in question I can't tell if it's a problem:
The script-block syntax - { RemotePowerShellEnabled -eq $false } - makes the cmdlet see the following verbatim content: RemotePowerShellEnabled -eq $false
By contrast, "RemotePowerShellEnabled -eq $false" results in: RemotePowerShellEnabled -eq False, because the Boolean $false value is string-expanded.
Ditto for $true / True
Just want to make sure that these values are accepted interchangeably.

Yikes. Here's what I've determined after further testing:
As you described, you can't use double quotes around the whole OPath filter if you're searching for $true/$false or $null values (I call those 'system values'); you must use single quotes or braces.
So, either way, some sort of call-out required:

if you say "enclose the whole OPath filter in double quotes" you need to call out system values (which force you enclose the whole OPath filter in single quotes or braces).

If you say "enclose the whole OPath filter in braces" you need to call out variable values (which force you enclose the whole OPath filter in double quotes).

Is one of these choices inherently better than the other? Braces appear to be most compatible across a wide variety of search values, which would be important if you're using multiple criteria in the same filter.
I've summarized the results in the following table. I've also included this information (and more) in an as yet unpublished update to Recipient filters in Exchange PowerShell commands. I'll probably keep the update regardless of which way we decide to go (since it's good to know and helps explain all possible outcomes).
Comments are welcome.

Search value
OPath filter enclosed  in double quotation marks
OPath filter enclosed  in single quotation marks
OPath filter enclosed  in braces

'Text'
X

X

"Text"

X

'$Variable'
X

500
X
X
X

'500'
X

X

"500"

X

$true

X
X

you must use single quotes or braces.

` (backtick) is PowerShell's escape character, so you can also `-escape individual $ characters inside "..." to prevent their expansion: "foo -eq `$true" yields the following verbatim: foo -eq $true.
So if someone does want to use an expandable string (string interpolation, "..."), they can use ` as shown (an - obviously more cumbersome - alternative is to use an expression that uses string concatenation: ("one -eq '$foo' -or two -eq " + '$false')
The Braces construct ({ ... }) creates a [scriptblock] instance - a type that creates a code block for later execution.
It is therefore unrelated to strings, and - to avoid confusion - shouldn't be repurposed to act as a string literal of sorts.
That it looks like PowerShell code but isn't, created the massive confusion around the ActiveDirectory module's  -Filter parameter previously linked to.

P.S.: The AD provider actually can itself resolve simple variable references such as 'sAMAccountName -eq $name', but not expressions such as 'sAMAccountName -eq $obj.Name'
I don't know if that's the case here too - it's certainly worth clarifying, along with what system values refers to - but either way it is important to make it obvious that  a  string is being passed whose interpretation is up to the cmdlet - and, conversely, to avoid the misconception that just any piece of PowerShell code can be passed, which is the misconception that use of { ... } promotes.

So, the definitive information around this will be at Additional OPATH syntax information. I've updated it to include the fact that an escaped dollar sign in a system value allows the entire OPath filter to be enclosed in single quotes, double quotes, or braces. And I always define 'system values' wit the examples of "$true, $false, or $null". Those are the parameter/property values that are most used in Exchange, I don't know exactly what else to call them, and I'm not sure if there are any others.
Fundamentally, braces work in filters as long as you aren't trying to expand variables. Exchange topics have been using braces around OPath filters since the Exchange 2007 days, and for alphanumeric values or 'system values', the work just fine.

The Braces construct ({ ... }) creates a [scriptblock] instance - a type that creates a code block for later execution.
It is therefore unrelated to strings, and - to avoid confusion - shouldn't be repurposed to act as a string literal of sorts.

I get it, and I'm trying to do the technically accurate thing here, but what exactly is the harm in using OPath filters surrounded by braces if the filters work as written now that we call out the fact that you can't use braces with variables? I'm 'asking' mostly rhetorically, because I'm convinced the answer is mostly 'there is no harm' now that we call out that braces don't work if you have variables that require expansion.
Because of 12+ years of using braces in our content, I feel we must somehow pay homage to the fact that they actually work, and I think this sentence that's now used everywhere captures the correct and most reasonable sentiment:

You need to enclose the whole OPath filter in double quotation marks " or " single quotation marks ' '. Although any OPath filter object is technically a string and not a script block, you can still use braces { }, but only if the filter doesn't contain variables that require expansion.

This serves as a necessary safety blanket to everyone with working filters who might be confused/upset with our sudden global change in syntax after 12 years.
If any other call-out is required when using braces, we should definitely add it.

OK. No further response, so closing.

Sorry, dropped the ball.

what exactly is the harm in using OPath filters surrounded by braces if the filters work as written now that we call out the fact that you can't use braces with variables?

The harm is that you're promoting a misconception about what the syntax { ... } does, which may bite you in other scenarios.
{...}, as script-block literals meant to contain PowerShell code can be situationally repurposed to act as verbatim strings, but (a) that's not what they're for, (b) it doesn't always work, and (c) you may form a misconception about the true purpose of the syntax.
Try the following for instance (a contrived example, but it illustrates the point that {...} doesn't contain a string):
Write-Host { 1 + }  # BOOM!

Conversely, if you do know that { ... } are script blocks, you will expect the contents of the block to work the same way it does in PowerShell - since it doesn't, confusion is likely to ensue - your clarification notwithstanding.

All good, but I know from experience that using braces for the Filter and RecipientFilter parameters in Exchange cmdlets works in all cases EXCEPT when you're trying to expand variables.
I think I've done enough by modifying the parameter descriptions any general mention of OPath filter syntax EVERYWHERE in Exchange PowerShell/cmdlet reference content to include this statment (or a version of it):

You need to enclose the whole OPath filter in double quotation marks " " or single quotation marks ' '. Although any OPath filter object is technically a string and not a script block, you can still use braces { }, but only if the filter doesn't contain variables that require expansion.

That's about as far as I'm willing to go, unless you can suggest alternative or additional text that I need to add.

works in all cases EXCEPT when you're trying to expand variables.

Yes, it works, but my point is that use of {...} ultimately does more harm than good, for the reasons stated.
What you've done and the wording you propose are great improvements, but the problem is that your explanation won't always be present when users look at examples and real-world code that uses {...}
And even users who've read the explanation may forget over time, and scratch their heads over why their perfectly well-formed (ostensible) script block doesn't work (doesn't recognize their variables).

None of the OPath examples anywhere in Exchange PowerShell/cmdlet reference topics use {...} anymore, in particular in the original object of this issue, which was New-AddressList.
We're in the process of updating Exchange conceptual/procedural content for similar Filter/RecipientFilter OPath examples to replace {...} with '...' or "...". It will happen; it's just a question of when. From an issue tracking perspective, that work is far outside the scope of this specific issue.
So is there any reason I shouldn't close this issue?

I'm glad to hear it all.
Feel free to close.

Thank you. Closing.


Make the browsers lighter by using Firefox container tabs

Describe the feature
Using firefox cookie containers would allow a single window running multiple accounts.
Low quality example: https://github.com/ChatGPT-Hackers/ChatGPT-API-agent/blob/main/background.js

Perhaps too much work.


refactor(frontend): split the backend from the frontend folder to refactor

Closes #13
📑 Description

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed
[x] Branch name follows type/descript (e.g. feature/add-llm-agents)
[x] Ready for code review

ℹ Additional Information

Seperate frontend and backend by using frontend and gpu_bartender/sever in the root dir
Change the programming language for backend from typescript into python
Refactor and reconstruct the Webpack configuration
Update package.json setting

@YuanhuanO I checked other repo and it shows that it is not common to upload node_modules to the github repo?

check this line: https://github.com/OpenDevin/OpenDevin/blob/main/.gitignore#L176

I

it shows that it is not common to upload node_modules to the github rep

Thanks for mentioning that!


trait default spec fn bodies don't communicate across module boundaries

This issue happens on branch trait-default-resolve 72a7ddf69d3eb50b478df28480155222a5eba7f5 .
I started with code like TogetherMod in this sample. When I factored the implementation into a different module, verification failed (as it does in this sample). It seems that the body of fn foo is visible elsewhere in TogetherMod, but not to BarMod which uses it.
//use builtin::*;
use builtin_macros::*;

verus!{

mod TogetherMod {
    pub trait FooTrait {
        spec fn foo(&self) -> bool
        {
            true
        }
    }

    struct FooStruct {
    }

    impl FooTrait for FooStruct {
    }

    impl FooStruct {
        proof fn check(&self) {
            assert( self.foo() );
        }
    }
}

mod FooMod {
    pub trait FooTrait {
        spec fn foo(&self) -> bool
        {
            true
        }
    }
}

mod BarMod {
    use crate::FooMod::*;

    struct FooStruct {
    }

    impl FooTrait for FooStruct {
    }

    impl FooStruct {
        proof fn check(&self) {
            assert( self.foo() );
        }
    }
}

}

Should be fixed by https://github.com/verus-lang/verus/commit/e18a42382675113962340501b40491b24907456b


Memory game for kids (Pexeso)

Create screen with Pexeso as on web https://www.movapp.cz/kids/memory-game , https://github.com/cesko-digital/movapp/pull/109

Migrate data for pexeso (images and translations) from web https://github.com/cesko-digital/movapp to https://github.com/cesko-digital/movapp-data/
Kids navigation screen - (so far not specified with UX team it might change) Top Kids screen accessible thru bottom app bar which should contain navigation to current Kids screen / Pexeso / Fairy tales (in future)
Pexeso screen - so far can be with fixed width/height

done


No sourcemap-enabled stack trace in loadModules $injectorMinErr (at least not in Chrome)

Do you want to request a feature or report a bug?
Bug
Current behavior + steps to reproduce

Use webpack or some other concatenation/minification of scripts that benefits of sourcemaps during debugging
(to be sure that minification errors are thrown) Enable strictDi: true in angular.bootstrap (or use ng-strict-di)
Attempt to include an angular module that has a reference or other problem. In this case, there is a problem with an undefined variable in config.js
Notice that the stack trace thrown by loadModules() is referencing to your bundled/minified javascript and not using sourcemaps (latest Chrome):

Error: [$injector:modulerr] Failed to instantiate module app due to:
ReferenceError: env is not defined
    at http://localhost:8080/bundle.app.cf5a8012b28c1225c1ed.js:87540:36
    at Object.invoke (http://localhost:8080/bundle.app.cf5a8012b28c1225c1ed.js:13342:20)
    at runInvokeQueue (http://localhost:8080/bundle.app.cf5a8012b28c1225c1ed.js:13225:36)
    at http://localhost:8080/bundle.app.cf5a8012b28c1225c1ed.js:13234:12
    at forEach (http://localhost:8080/bundle.app.cf5a8012b28c1225c1ed.js:8852:21)
    at loadModules (http://localhost:8080/bundle.app.cf5a8012b28c1225c1ed.js:13215:6)
    at createInjector (http://localhost:8080/bundle.app.cf5a8012b28c1225c1ed.js:13137:20)
    at doBootstrap (http://localhost:8080/bundle.app.cf5a8012b28c1225c1ed.js:10333:21)

Also notice that it is possible to click the arrow in the Chrome dev console and see a sourcemaps-enabled stack-trace, but without the entry of config.js where the actual ReferenceError is (it starts from the parent entry to the actual error)

What is the expected behavior?
On step 4, the stack trace should reference the actual source files, so that it is easy to understand where the problem lies in the source code, namely config.js:
ReferenceError: env is not defined
    at config.js:1268
    at Object.invoke (angular.js:4847)
    at runInvokeQueue (angular.js:4730)
    at angular.js:4739
    at forEach (angular.js:357)
    at loadModules (angular.js:4720)
    at createInjector (angular.js:4642)
    at doBootstrap (angular.js:1838)
...

What is the motivation / use case for changing the behavior?
Easier debugging of module inclusion, especially important when migrating to webpack or other bundler that requires sourcemaps to even have a change debugging in the development-environment.
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
Angular 1.6.1 (latest stable)
Chrome 55
Mac OSX El Capitan
Have not tested with latest snapshot.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
A workaround is to replace the following line in angular.js:
throw $injectorMinErr('modulerr', 'Failed to instantiate module {0} due to:\n{1}',
module, e.stack || e.message || e);
with:
throw e;
This yields an understandable stacktrace in the console (shown above).
Note, according to https://bugs.chromium.org/p/chromium/issues/detail?id=376409 "there is no way to fix it for Error.stack property because this property is generated by V8 which know nothing about source map". Despite this, e.stack is preferred as the ErrorConstructor argument over e.
This is evident when running
console.log(e, e.stack);
just before the error is throw. First an error with a sourcemap-enabled stacktrace is displayed in the console, then a stacktrace without sourcemaps.
However, simply replacing "e.stack || e.message || e" with "e" leads to a stack trace with sourcemaps enable but without config.js mentioned:
Uncaught Error: [$injector:modulerr] Failed to instantiate module app due to:
{}
http://errors.angularjs.org/1.6.1/$injector/modulerr?p0=app&p1={}
at angular.js:68
at angular.js:4764
at forEach (angular.js:357)
at loadModules (angular.js:4720)
at createInjector (angular.js:4642)
at doBootstrap (angular.js:1838)
at bootstrap (angular.js:1859)

It would be nice to have better support for sourcemaps, but I am not sure how we can do this (without dropping minErr).
Maybe we could provide some hooks for people to customize their error reporting (i.e. the behavior of minErr). This could be handled together with #15433. E.g. something like:
angular.configureMinErr({
  maxDepth: 2,
  beforeError: function() {
    var lastArg = arguments[arguments.length - 1];
    if (lastArg instanceof Error) console.error(lastArg);
  }
});

@motin Thanks for the report. I've been thinking about this problem in a while. In my apps I workaround it via replacing the $exceptionHandler:
myModule
    .factory('$exceptionHandler', () => {
        'ngInject';

        return (...params) => {
            console.error(...params);
        };
    });

I've been thinking about removing this whole preprocessing inside of the $log service (this code has more than 5 years!) as the browser can only preprocess the stack trace if it gets an error logged; if we're just logging the stack as a string, the browser can't know we're printing an error stack and doesn't apply any transformations.
I've been looking at how various browsers deal with stack traces referring to files with source maps attached if and here is what I found:

Chrome & Safari map the stack traces to the original files (if you log the error).
Firefox always logs the original stack trace.
IE & Edge log the original stack trace but kind of buried inside of the object printed.

In IE/Edge you have to click once to reveal the object which will show you (among other things) the beginning of the stack. You have to then click on the stack to actually get it. Not the most pleasant experience. What's worse, in the exception handler we're actually often passing an error as the first argument and the cause (a string) as the second one. In such a case under the hood we get something like console.error(formatError(error), cause).
If we changed that to console.error(error, cause), i.e. if we remove the error formatting Edge & IE print error message and clause in the first line and everything else is wrapped in a dropdown so you have to click once more to get to the stack (3 clicks in total!). The screenshots at the bottom of this post show all the states.
Stopping formatting the errors would then decrease the developer experience in IE/Edge. Because of that, we've been thinking about user agent sniffing Edge (IE detection is simple; just check document.documentMode) and formatting the error then; in other browsers we'd disable the formatting.

Error logging in Edge (console.error(error, cause))
The first state:

After clicking on the arrow:

After clicking on the second arrow:

After clicking on the stack field:

@csuwildcat A while ago you reached to us to see if there are any issues in Edge that affect AngularJS in particular so that the Edge team can prioritize them. This is one of those issues (see my comment above, with screenshots, to get the problem). Are you still the person-to-go wrt issues affecting major frameworks/libraries? If not, who can we contact?

@csuwildcat A while ago you reached to us to see if there are any issues in Edge that affect AngularJS in particular so that the Edge team can prioritize them. This is one of those issues (see my comment above, with screenshots, to get the problem). Are you still the person-to-go wrt issues affecting major frameworks/libraries? If not, who can we contact?
I opened an issue in the Edge bug tracker about the above problem: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10868717/

@motin Thanks for the report. I've been thinking about this problem in a while. In my apps I workaround it via replacing the $exceptionHandler

Thank you! That workaround improves usability of stack traces HEAPS, simply by finally showing the actual line of the error.
Without the workaround:

With the workaround:

Night and day! :)

@mgol just seeing this, apologies on the delay. I am no longer working in depth on Edge, but I can try to track down the person who handles this now if that would still help?

@csuwildcat I opened https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10868717/ to track the issue, it's been closed as it apparently requires bigger architecture changes which have a uservoice entry at https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6225641-call-stacks-for-messages. We'd appreciate if this change was prioritized in some way but I'm not sure how feasible it is for you in the nearby future.

PR: #15767


CI/CD?

Right now you need to run git push and git push heroku master separately on every commit.
There's a way in heroku settings for all new pushes to this repo to automatically get pushed to Heroku. Set up that?

Should be simple to add

I believe all commits to main branch will now automatically reflect in main website (and testing website). Followed instructions at Heroku's website

Confirmed during 104a5d9
No plans for CI yet. Could be nice to add eventually to codebase


container_netperf benchmark fails due to change in netperf benchmark

The container_netperf benchmark uses the ParseNetperfOutput function from the netperf benchmark.  This commit https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/commit/e0a5c9fdaf11e02259fada129efc5f698a676000 to the netperf benchmark, that adds more metrics, breaks container_netperf because the list of metrics in container_netperf must match those in netperf due to sharing the output parsing function.

Thanks for the report - this should be fixed shortly - I'll close once the fix is merged

This was fixed with commit: https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/commit/431b8e8ebe2435ab15abc6f2769e964f6d8b223b
Thanks @ehankland .


Container view, detail panel, info table, ID & IMAGE ID fields contain truncated text as tooltip

Per https://github.com/weaveworks/scope/issues/1059.
The truncated text is not indicated with '...' and the tooltip is truncated text rather than untruncated text.
Same applies to the image id field.

The ID was truncated in the backend after it was agreed that we show container IDs in the same format as docker ps does.
Please reopen if new reasons exist why we should change this again.

For completeness: imageID render issues will be handled in #1058

The ID was truncated in the backend after it was agreed that we show container IDs in the same format as docker ps does.

What was the basis of the decision to have the field truncated in the tooltip? And where was that decision recorded? I have searched the issues and PRs but cannot find it. #924 and #930, which introduced this, don't even mention the truncation, let alone the rationale.

Please reopen if new reasons exist why we should change this again.

Unless there is a very good reason, whenever we truncate information, the complete information should be contained in the tooltip.
Btw, note that docker ps has a --no-trunc option.

What was the basis of the decision to have the field truncated in the tooltip? And where was that decision recorded?

There was no decision. The backend provides one value per field. The frontend renders that value, the browser provides the ellipsis if there is not enough space. The tooltip shows the same field value, but is not shortened by the browser because there is no space restriction.

Unless there is a very good reason, whenever we truncate information, the complete information should be contained in the tooltip.

It's been decided in the last scop sync to remove the backend truncation. Then the full value will appear in the backend again.

I know the commit/issue/pr where the truncation was introduced?

Anyone know the commit/issue/pr where the truncation was introduced?

See my comment above from a few months ago.


Fix for SciPy simpson function

Scipy v1.12 deprecated scipy.integrated.simps and it is removed in v1.14. Simple fix is to migrate to the replacement simpson function

Also noting that setup.py doesn't have scipy as a dep.


TypeError: Cannot use 'in' operator to search for 'default' ...

Environment
Jiti version 2.2.1 (the latest)
NodejS v22.8.0
Reproduction
To reproduce, just install npm install ffmpeg-static (v5.2.0) and import it with Jiti like that:
import pathToFfmpeg from "ffmpeg-static";

This will throw this error every time:
TypeError: Cannot use 'in' operator to search for 'default' in /var/www/videomail/prod/source/node_modules/ffmpeg-static/ffmpeg
    at /var/www/videomail/prod/source/node_modules/jiti/dist/jiti.cjs:1:182495
    at jitiInteropDefault (/var/www/videomail/prod/source/node_modules/jiti/dist/jiti.cjs:1:183330)
    at jitiRequire (/var/www/videomail/prod/source/node_modules/jiti/dist/jiti.cjs:1:187464)
    at import (/var/www/videomail/prod/source/node_modules/jiti/dist/jiti.cjs:1:196818)
    at /var/www/videomail/prod/source/src/server/util/ffmpeg/runner.ts:3:50
    at eval_evalModule (/var/www/videomail/prod/source/node_modules/jiti/dist/jiti.cjs:1:193374)
    at jitiRequire (/var/www/videomail/prod/source/node_modules/jiti/dist/jiti.cjs:1:187618)
    at import (/var/www/videomail/prod/source/node_modules/jiti/dist/jiti.cjs:1:196818)
    at /var/www/videomail/prod/source/src/server/util/ffmpeg/encodeVideo.ts:8:44
    at async import (/var/www/videomail/prod/source/node_modules/jiti/dist/jiti.cjs:1:196812)

FYI this didn't happen on Jiti v2.1.2, so this bug must have been introduced recently

I guess, probably caused by some of these changes in this commit?
https://github.com/unjs/jiti/commit/88260477e96a3e9e2790ac26f7c9524b7c7f2410

Thanks for report. Investigating now, it is related to https://github.com/unjs/jiti/pull/318

While i can guess the issue by the error message you shared, i cannot reproduce locally. Can you somehow share a runnable repo? It can help me to pinpoint exact issue.

You can verify the fix via nightly channel thanks again for the report.

Ok @pi0 thanks, I've amended JITI_CACHE=0 to the command, yet it still crashes:
/home/michael-heuberger/code/binarykitchen/videomail.io ❯❯❯ JITI_CACHE=0 npm run dev:server                                                                                dev ✭ ✱

><EMAIL_ADDRESS>dev:server
> cross-env NODE_ENV=development ENVIRON=local nodemon --watch ./src/server --watch ./src/common --ignore **/__tests__/** --exec jiti ./src/server/index.ts

[nodemon] 3.1.7
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): src/server/**/* src/common/**/*
[nodemon] watching extensions: ts,json
[nodemon] starting `jiti ./src/server/index.ts`
TypeError: Cannot use 'in' operator to search for 'default' in /home/michael-heuberger/code/binarykitchen/videomail.io/node_modules/ffmpeg-static/ffmpeg
    at /home/michael-heuberger/code/binarykitchen/videomail.io/node_modules/jiti/dist/jiti.cjs:1:182495
    ...

Anyway, I'll check out your nightly channel now ...

Yup, I just tested with the nightly channel @pi0 - that fixed it. Thanks :)
Please add more unit tests about this.

cool! we will eventually port interopDefault back to mlly repository which has unit tests. there are just too many edge cases that need respond fast, we had been fixing them since 5+ years ago and with jiti v2 it got harder since there is also native ESM...

Nice.
I'm running an ancient but popular app. Trying to migrate it slowly to TypeScript/ESM, that's why these hiccups :)


Updated policy as per recent changes in ACM 2.10

Updated policy as per recent changes in ACM 2.10. The "namespace" must be included. The kind "Placement" should be used as "PlacementRule" has been deprecated.
Signed-off-by: Ashish Saket<EMAIL_ADDRESS>

Signed-off-by: Ashish Saket<EMAIL_ADDRESS>


07-27 site management group TODOs

[ ] Joana: + join mbon section with details on what joining entails (from original document)
[X] publications view on homepage should highlight most recent publications then link to full searchable archive
[ ] merge 1st 4 about us nav sections into 1
[ ] links on top nav should go to separate pages
[ ] news display should also use tiled view & have images for each
[x] + link to MBON data portal (as a tool product?)
[ ] get started with a footer
[x] fix geobon logo

[x] can't see the e
[x] should look more like a login button

[ ] borrow homepage design from https://ioos.noaa.gov/

[ ] overview header that scrolls away then top nav (that is going to be hard to do)
[ ] lighter blue section under the nav with desc

get started with a footer

We are ready to create a custom footer using /layouts/partials/site_footer. What should we put in it? I don't recall what was suggested in the meeting.

If we want the site to align with the other ioos.us sites, @mwengren recommended the footers should (if possible):

have consistent look and feel if possible and match the content at the main ioos.us page (contact info, webmaster email, etc), and require a link to ioos.noaa.gov to more consistently associate ioos.us with ioos.noaa.gov

This isn't a requirement, just recommendation to share. We don't have to align, I don't think...


Quartus 18.1 does not have DDR2 IPCore

Hello
i try to compile on quatus 18.1 but could not find DDR2 ip core now  DDR2 altmemphy supporting
please help us how can we compile on Quartus 18.1
Thanks
Nome

Hello,
You need to use Quartus 15.1.

Hi
yes I know 15.1 does supporting but officially intel altera obsolete 15.1 no more support from website
thats why I am using 18.1
thanks
nome

I'm afraid we don't support recent versions.


Icons for Social Links

While icons work for the major social media platform using the font awesome icons ( i am using Instagram fab fa-instagram fa-2xl) it is not possible to you any other fab icon for some custom links.
For instance, i'd like to either use fa-solid fa-bolt and link to a custon URL or use my own provided png logo within static
But both ways, nothing is being displayed.
Is there any advice ?
Thanks, Max

We don't support static files for social media links. Here's the code line: https://github.com/boratanrikulu/eternity/blob/main/layouts/partials/navbar.html#L40-L46

We don't support static files for social media links. Here's the code line: https://github.com/boratanrikulu/eternity/blob/main/layouts/partials/navbar.html#L40-L46

Thanks for the swift response -
just a quick follow up (might be noob question) - where do i find in the code/config the possible and allowed social media icons ?

You check here: https://fontawesome.com/icons

[!WARNING]
This project is currently not being actively maintained.
Please do not create new issues on GitHub.


fix(types): correct import of types

Description
Fixes #4002.

d.ts files are treated as an ambient module declarations only if they don't have any imports. If you provide an import line, it's now treated as a normal module file, not the global one, so augmenting modules definitions doesn't work.

Michał Lytek from StackOverflow

Thus, the addition of imports in the client.d.ts in #3638:
import {
  ErrorPayload,
  FullReloadPayload,
  PrunePayload,
  UpdatePayload
} from 'types/hmrPayload'

Is improper and invalidates client.d.ts as an ambient declaration.
Instead, we have to import types this way:
(
  event: 'vite:beforeUpdate',
  cb: (payload: import('./types/hmrPayload').UpdatePayload) => void
): void

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

@GrygrFlzr for the rest of the types, we are duplicating the definitions instead of importing them. I am fine if this is a better approach and we start moving towards using imports, but if we plan to leave things as is, shouldn't we duplicate also these definitions to be consistent? Or is there something different from these ones in particular?

As suggested, I've swapped to consistently importing in order to remove the duplicated types. CustomEventName has been extracted out into its own file. This also fixes a missing import.meta.env.SSR property in client.d.ts.

I copied these changes into my node_modules, and my type errors have disappeared.  Seems to indeed fix #4002.  Thanks!


Accidentally cleared entire wsl data from vscode

After using vscode and wsl for a long time, there are too many folders on the wsl targets of vscode, so I want to clear all these folders and clicked a delete button around the wsl targets, then I can't connect to wsl any more
I checked the wsl root folder on the windows, and found that the root folder is decreased to < 2GB from > 100GB, I realized all system/program/code/... data is gone
（Speechless...)

The x button next to the folder doesn't delete any data.
I hope you didn't invoke the Delete Distro command in the context menu. That one really release the distro and the data, just as the dialog says.
Run wsl --list to see if your distro is still around.

I indeed invoked the Delete Distro command, I didn't realized it will delete all, I supposed that the wsl system can only be deleted from powershell(after all, once it is installed, it is rarely deleted)

Sorry for that, that's horrible. I hope you were able to recover your work.
When adding the add distro functionality I thought having delete would be good to have too.
I was hoping the the dialog message was clear enough. I see how I can improve it.


By the way, I apologize for all of the issues :)

Yeah, I've noticed the FontAwesome dependency after replacing the current icons...
TBH I've added the removal of FontAwesome to my to do list. I'm not really a fan as we definitely need to keep the current interface working with the (very specific) naming of the icons (see readme.md)

Oh, and don't mind the issues. I'm glad other people want to contribute to this repo 😊

I'd rather contribute than rebuild. I'd agree with the removal of fontAwesome and as many dependencies as possible. I'll keep making suggestions, cheers!


touying-buaa:0.2.0

I am submitting

[ ] a new package
[x] an update for a package

Description: Because @OrangeX4 made stargazer as touying built-in theme and released touying 0.5.0 (a disruptive version), I simplified the implementation of this package/template using the built-in theme and bumped to touying 0.5.0

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Wait for #937


Apply pull request #1155 on release

This is a branch to apply the pull request #1155 on the 'release' branch.

Maybe let project owner perform this pull request when they see it's necessary?

That's right. I just made a patch to merge it smoothly. Is it a correct way to give as an another pull request?

Merges to the release branch are not done for individual features. They are done as part of the release process.


Bluetooth: controller: Create HCI stubs for CIG/CIS and ISO tests

Put infrastructure for the following HCI commands/events in place:

LE Setup ISO Data Path command
LE Remove ISO Data Path command
Configure Data Path command
LE Set CIG Parameters Test command
LE ISO Read Test Counters command
LE ISO Receive Test command
LE ISO Test End command
LE ISO Transmit Test command

PR #30000, congrats!

Outstanding comments addressed


Remove obsolete parameter in VerilogLintTextStructure().

The context printing parameter is not needed inside that
function anymore as it doesn't do the printing of the message.
Signed-off-by: Henner Zeller<EMAIL_ADDRESS>

Codecov Report

Merging #996 (498d464) into master (f6cea5d) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #996   +/-   ##
=======================================
  Coverage   92.84%   92.84%
=======================================
  Files         323      323
  Lines       21040    21040
=======================================
  Hits        19535    19535
  Misses       1505     1505

Impacted Files
Coverage Δ

verilog/analysis/verilog_linter.h
100.00% <ø> (ø)

verilog/analysis/verilog_linter.cc
92.74% <100.00%> (ø)

Continue to review full report at Codecov.

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


Set Document advocate_id

Document advocate_id should be set when created as nested resource via claim

Some integration tests fail after merging (and resolving conflicts) with develop.


Fix offset-based position transform not respecting previous transforms

Closes #3821
Supersedes #3902
See https://github.com/ppy/osu-framework/pull/3902#issuecomment-699742964 for reason why superseded.

ReadIntoStartValue() is added before Apply() to fix cases where the position offset transform would be applied without its value being read, therefore leading to incorrect results. (as the commit says https://github.com/ppy/osu-framework/commit/1589926137f8e295bad6923bd939ea8af96d9c43)

@peppy This seems sane to me but I want your review too since you're more knowledgeable about the inner workings of transforms w.r.t reading of values/applying.

I think it seems sane. @smoogipoo have you cross-tested with osu! (especially gameplay/storyboard rewinding/ffwding)?

Just did, seems fine.


[vr] Support for 2D drawing on 3D (using billboards)

Right now when switching to VR mode, it's only possible to draw 3D content, raylib 2D drawing mechanism is not supported in VR mode.
2D drawing must be adapted to allow drawing 2D content into a billboard texture in 3D vr mode.
It could be done enabling a RenderTexture2D when vr mode is active and doing all 2D rendering offline, then, at EndDrawing(), just render RenderTaget2D texture into a billboard in front of the 3D content.

I've been working on this issue for a while but didn't find a proper solution yet... the more I see current VR implementation, the more I think it needs to be redesigned to better accomodate for multiple VR devices and for 2D drawing on 3D... I imagine it's the result of working for too long on a system... :P
Current implementation checks for VR device availability and fall-backs to VR simulator in case no-device is detected; additionally VR stereo-rendering can be enabled-disabled at any time.
Some considerations when working on VR system:

I'm not registering camera movement (tracking) back from VR device to user code. User camera struct should be updated in case user requires head-tracking data (required for 2D billboard).
Rendering 2D into 3D requires rendering to FBO (texture) and then using that texture as a billboard, oriented with user camera (head-tracking).
FBO texture (to be used as billboard) could require transparency, consecuently, it should be set as RGBA on FBO creation (RenderTarget2D) and also cleared to transparent value.
Really need to expose VRDeviceInfo parameters to users?

raylib VR implementation has changed on raylib v1.7. It moved from device-specific (Oculus Rift CV1) to a generic VR simulator system (stereo rendering with config parameters). So, this issue has no sense at the moment:

Not using VR device.
Not usign VR device, concept itself is right.
Option implemented.
Not at this moment.


Why init instead of init?

I was wondering why it's considered idiomatic in haliax to instantiate new modules with a @staticmethod init instead of using the built in object initializer, __init__? The latter seemed more natural to me so I've been using it instead when defining my own modules. Nothing has broken so far, but now when I try to define a transformer block:
class TBlock(eqx.Module):
    ffn: FeedForward
    attn: Attention

    def __init__(self, key):
        k1, k2 = jr.split(key, 2)
        self.ffn = FeedForward(Embed, Mlp, key)
        self.attn = Attention(Key, Embed, Head, key)

    def __call__(self, x: hax.NamedArray, padding_mask) -> hax.NamedArray:
        x = x + self.attn(x, padding_mask)
        x = x + self.ffn(x)
        return x

and then use stacked with it
self.blocks = hnn.Stacked.init(Layer, TBlock)(key=jr.split(k3, Layer.size))
I get AttributeError: type object 'TBlock' has no attribute 'init'
presumably because stacked was expecting a
@staticmethod
def init(self):
    pass

instead of my
def __init__(self):
    pass

Is there any way to get this to work with the typical idiomatic Python initialization? And why was this choice made in the library design (since, as far as I can tell, Equinox also is in keeping with traditional Python here)?

In general I wanted there to be a "boring" constructor that just takes the fields, which helps making initializing from other sources easier: loading from HF checkpoints, different initialization strategies, etc.
We could revisit, but that's why I did it the way I did

Ah ok, the more I thought about this the more it actually probably seems like the right idea. I'll change my code to be consistent with it. Have not encountered it before in ML libraries, but it does make sense to be able, e.g., to initialize a module with a very specific weight matrix or something like that. Incidentally, this strengthens my belief that haliax could be used to make a really good interpretability library!


Set up the project with Webpack and JEST

-Set up Gitflow
-Set up webpack
-Set up a JavaScript testing library (Jest)

All is done 💯


TUTORIAL: Deploying Sophia smart contracts with init parameters

TUTORIAL: Deploying Sophia smart contracts with init parameters updated by @emmanuelJet. @thepiwo and @alekseytsekov kindly review.
AE Address: ak_rLoCtHE3NK9dKyCNonJFYWkEEfeAsDUWa887GsCKqV1rhSuT6

Hello, can you make a PR that only includes the changes to one tutorial please?

Will do just that


Grammars: Remove use of /i/ in middle of terminals, to support Lark.js

Codecov Report

Merging #987 (6e2842e) into master (8874578) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #987   +/-   ##
=======================================
  Coverage   87.15%   87.15%
=======================================
  Files          50       50
  Lines        6868     6868
=======================================
  Hits         5986     5986
  Misses        882      882

Flag
Coverage Δ

unittests
87.15% <ø> (ø)

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

Continue to review full report at Codecov.

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

Just wondering, why do you have to do this?

@ThatXliner Javascript doesn't support flags in the middle of the regexp. That would mean grammars built using those terminals, wouldn't be able to run in Lark.js
There is no benefit to keep them as flags, other than perhaps an aesthetic preference.


Resources for README

Here is the pictures and other resources for README in this project.

Header

Screenshots:

Theories

Framework

Sample output of cGAN

Sample style transfer

Sample combined output

Report
Artistic_Image_Generation_from_Sketch.pdf


PIs not properly listed on some project pages

I should be listed... and likely Yochai as a Co-PI too. Curious what's wrong here but don't have time to investigate atm

OK, first of all, the data on the backend was not entered correctly. I was not specified as PI. Kotaro and Manaswi were not specified as student leads. So, that's fixed. But David Jacobs should still show as a former Co-PI

OK, that was also a data entry problem...


AXI-4 Lite transfer fail (Master write)

The testbench could work on previous code (when not swap the name of mst_ and slv_   )
when I check the result on latest code
Master read function is correct,  but it will fail when master write
From waveform.  I  can see o_wch is 0 in module:  axicb_mst_switch,  even i_wch have data
it's due to wch_empty signal is always 0

Hi Vincent,
in the last commit you mentioned, I also remove the necessary synchronisation between write address channel and write data channel, which is most likely the issue. Now the write data channel uses a FIFO to store the granted access and drive its payload.
Yesterday night I added new test bench configuration to stress some AXI4 configuration as AXI4-lite scenarios and it went well. Probably the testbench doesn't reproduce the issue.
Could you provide me a waveform, your test bench, the test case or any info to help me understand the problem? I'll have time the next days to debug and fix the problem if necessary.
Damien

By the way which simulator do you use? I currently run my verification environment only with Icarus Verilog 11.

I may have found the root cause @vincentliu84. Can I ask you to test with this commit please? :)

Sorry for late response during weekend
I use VCS and Xcelium,  also AXI VIPs in my environment,   so can you open the fsdb format?
I read the code about  mst_switch,   and submodule:   wch_gnt_fifo
The wch_empty signal is generated by wch_gnt_fifo,  and it's judged by wr and rd pointer
but when push signal is from 0 -> 1,   the empty signal is still 0
you can check the simple waveform in:   https://github.com/vincentliu84/hello-world

Hi Vincent,
srst is tied to 1 in the waveform, so the circuit remains under reset. You need to choose aresetn or srst and don't drive both.

aresetn: a asynchronous active low reset, so needs to be driven low to reset then released to 1
srst: a synchronous active high reset, so needs to be driven high to reset then released to 0
You need to choose for all interfaces the same reset strategy, using aresetn or srst, and be sure all interfaces have been reseted then released to expect a proper core behaviour.
Should be ok with this fix :) By the way the last commits introduced USER support. The test bench has been upgraded to support them and I didn't find (yet) bugs during their usage.
Have a good day
Damien

This is solved,  thanks
but I found another issue ,  if master 0 is write to slave 1  (1 master ,  2 slaves in this scenario)
I see wch signals is routed to channel 1,  but wvalid and wready is not
you can check waveform2 in  https://github.com/vincentliu84/hello-world
(waveform marked with pink is slave 0,   and green is slave 1)
Thanks

I don’t see WLAST asserted for the first transfer, which blocks the second one. You need to tied up to 1 WLAST to let it pass on the top level. That doesn’t make sense for AXI4-lite, I’ll tied it internally tonight in case of AXI_SIGNALING=0 into the interface module.
Damien

Le 16 nov. 2021 à 14:30, vincentliu84 @.***> a écrit :

This is solved, thanks
but I found another issue , if master 0 is write to slave 1 (1 master , 2 slaves in this scenario)
I see wch signals is routed to channel 1, but wvalid and wready is not
you can check waveform2 in https://github.com/vincentliu84/hello-world
(waveform marked with pink is slave 0, and green is slave 1)
Thanks
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Should be OK now with commit mentioned above. My test suite ran successfully.
I though it could be handy to create a top level of the core to expose only AXI4-lite interface signals and another for AXI4 (which could be the current one). What do you think ?

it's solved,  thank you so much.
I think it's good idea to seperate the two interfaces


[CELEBORN-1490][CIP-6] Impl worker read process in Flink Hybrid Shuffle

What changes were proposed in this pull request?
Impl worker read process in Flink Hybrid Shuffle
Does this PR introduce any user-facing change?
No

@SteNicholas Thank you for your suggestions, i have modified the PR according to your comments, PTAL.
And there may a unstable test case, could you rerun the ci?

Thanks. merge to main(v0.6.0)


add endpoint to return api version

currently there is no way to know which version is currently running on the system

do we have a versioning of delphi-epidata?

We do not currently have versioning of the server, but we should start. The new dev/main structure will help with that, since it will encourage more rigor in the release process.


chore(main): release 2.1.3

:robot: I have created a release beep boop
What's Changed

ci: update release publish step by @johnhwhite in https://github.com/johnhwhite/ng-keyboard-sort/pull/55
ci: update publish tag by @johnhwhite in https://github.com/johnhwhite/ng-keyboard-sort/pull/57

Full Changelog: https://github.com/johnhwhite/ng-keyboard-sort/compare/v2.1.2...v2.1.3

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/johnhwhite/ng-keyboard-sort/releases/tag/v2.1.3 :sunflower:


Add Log Table to Character Details Page

Description

The user should be able to see a table of logs attached to their character on the character's details page.
Expected Behavior

The user should be able to see a table of logs attached to their character on the character's details page.
Actual Behavior

The user does not see a table of logs attached to their character on the character's details page.
Steps to Reproduce

Open character details page.
Notice missing table

Context

Possible Fix

Other
Description

Additional Notes

This seems to be a copy of #194, Closing


Add stylecop ruleset

Description
Enable Stylecop in C#
If this is a bug fix, please describe the root cause and analysis of this problem.
Task Item
closes #1326
Type of change

[x] Code refactor (non-breaking change which improve code quality, clean up, add tests, etc)

Checklist

[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have functionally tested my change

I can't really validate the rules or the code changes, but this should be incorporated into the build. Can you update .github/workflows/main.yml to include a build step to run the stylecop?

@a-b-r-o-w-n ， I already set most of the rules as Errors(copied from BotBuilder-Dotnet branch), build will fail if we violate those rules, do you still need another step to run the stylecop again?

@luhan2017 I may not understand stylecop that well. Does it run as a part of dotnet build?

@luhan2017 I may not understand stylecop that well. Does it run as a part of dotnet build?

@luhan2017 I may not understand stylecop that well. Does it run as a part of dotnet build?

Yes, you can try to add any black lines in the code and the build will fail due to the rule violation.


Moved AWS SDK dep to require instead require-dev, which is "root only"

Otherwise, it can't install when running composer update, or composer update --dev.
This is addressing #310

Hi Taylor, thanks for the feedback on this post. There is any example showing how to include SQS on composer.json?


fix(apps/dev/prow/release): bump tide image

Ref https://github.com/ti-community-infra/test-infra/pull/35
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


"failed to load artifacts" error in workflow of workflows pattern

Summary
What happened/what you expected to happen?
I tried to change the workflow of workflows example to pass an artifact to the workflow being created, I expected it to run as normal. Instead, I got this message: failed to load artifacts: open /argo/secret/my-gcs-cred/accesskey: no such file or directory.
Artifacts usually work fine.
Is the issue in resource.manifest.spec.arguments.artifacts.from being "{{inputs.artifacts.message-artifact}}"? Do I need to manually enter a s3 field and specify the bucket key/path where the previous make-artifact step uploaded the artifact to?
Diagnostics
What version of Argo Workflows are you running?
v2.10.2
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  creationTimestamp: "2020-09-16T03:31:38Z"
  generateName: workflow-of-workflows-
  generation: 8
  labels:
    workflows.argoproj.io/completed: "true"
    workflows.argoproj.io/phase: Failed
  name: workflow-of-workflows-fxstn
  namespace: argo
  resourceVersion: "14930284"
  selfLink: /apis/argoproj.io/v1alpha1/namespaces/argo/workflows/workflow-of-workflows-fxstn
  uid: 166f1b69-0086-48e8-9c96-d52419954e59
spec:
  arguments: {}
  entrypoint: main
  templates:
  - arguments: {}
    inputs: {}
    metadata: {}
    name: main
    outputs: {}
    steps:
    - - arguments:
          parameters:
          - name: message
            value: I really hope this works!
        name: make-artifact
        template: make-artifact
    - - arguments:
          artifacts:
          - from: '{{steps.make-artifact.outputs.artifacts.message}}'
            name: message-artifact
          parameters:
          - name: workflowtemplate
            value: workflow-template-submittable
        name: workflow2
        template: triggerWorkflowUsingResourceWithArgument
  - arguments: {}
    container:
      args:
      - echo {{inputs.parameters.message}} > /tmp/message.txt
      command:
      - sh
      - -c
      image: alpine
      name: ""
      resources: {}
    inputs:
      parameters:
      - name: message
    metadata: {}
    name: make-artifact
    outputs:
      artifacts:
      - name: message
        path: /tmp/message.txt
  - arguments: {}
    inputs:
      artifacts:
      - name: message-artifact
        path: /tmp/message.txt
      parameters:
      - name: workflowtemplate
    metadata: {}
    name: triggerWorkflowUsingResourceWithArgument
    outputs: {}
    resource:
      action: create
      failureCondition: status.phase in (Failed, Error)
      manifest: |
        apiVersion: argoproj.io/v1alpha1
        kind: Workflow
        metadata:
          generateName: workflow-of-workflows-2-
        spec:
          arguments:
            artifacts:
            - name: message
              from: "{{inputs.artifacts.message-artifact}}"
          workflowTemplateRef:
            name: {{inputs.parameters.workflowtemplate}}
      successCondition: status.phase == Succeeded
status:
  conditions:
  - status: "True"
    type: Completed
  finishedAt: "2020-09-16T03:31:46Z"
  message: child 'workflow-of-workflows-fxstn-1678132251' failed
  nodes:
    workflow-of-workflows-fxstn:
      children:
      - workflow-of-workflows-fxstn-1409631253
      displayName: workflow-of-workflows-fxstn
      finishedAt: "2020-09-16T03:31:46Z"
      id: workflow-of-workflows-fxstn
      message: child 'workflow-of-workflows-fxstn-1678132251' failed
      name: workflow-of-workflows-fxstn
      outboundNodes:
      - workflow-of-workflows-fxstn-1678132251
      phase: Failed
      startedAt: "2020-09-16T03:31:38Z"
      templateName: main
      templateScope: local/workflow-of-workflows-fxstn
      type: Steps
    workflow-of-workflows-fxstn-803943416:
      boundaryID: workflow-of-workflows-fxstn
      children:
      - workflow-of-workflows-fxstn-1342667872
      displayName: make-artifact
      finishedAt: "2020-09-16T03:31:43Z"
      hostNodeName: gke-adtestcluster-batch-pool-e2-32-0741dae7-wwk0
      id: workflow-of-workflows-fxstn-803943416
      inputs:
        parameters:
        - name: message
          value: I really hope this works!
      name: workflow-of-workflows-fxstn[0].make-artifact
      outputs:
        artifacts:
        - name: message
          path: /tmp/message.txt
          s3:
            accessKeySecret:
              key: accesskey
              name: my-gcs-cred
            bucket: adtestclusterbucket
            endpoint: storage.googleapis.com
            key: workflow-of-workflows-fxstn/workflow-of-workflows-fxstn-803943416/message.tgz
            secretKeySecret:
              key: secretkey
              name: my-gcs-cred
        exitCode: "0"
      phase: Succeeded
      resourcesDuration:
        cpu: 4
        memory: 4
      startedAt: "2020-09-16T03:31:38Z"
      templateName: make-artifact
      templateScope: local/workflow-of-workflows-fxstn
      type: Pod
    workflow-of-workflows-fxstn-1342667872:
      boundaryID: workflow-of-workflows-fxstn
      children:
      - workflow-of-workflows-fxstn-1678132251
      displayName: '[1]'
      finishedAt: "2020-09-16T03:31:46Z"
      id: workflow-of-workflows-fxstn-1342667872
      message: child 'workflow-of-workflows-fxstn-1678132251' failed
      name: workflow-of-workflows-fxstn[1]
      phase: Failed
      startedAt: "2020-09-16T03:31:44Z"
      templateName: main
      templateScope: local/workflow-of-workflows-fxstn
      type: StepGroup
    workflow-of-workflows-fxstn-1409631253:
      boundaryID: workflow-of-workflows-fxstn
      children:
      - workflow-of-workflows-fxstn-803943416
      displayName: '[0]'
      finishedAt: "2020-09-16T03:31:44Z"
      id: workflow-of-workflows-fxstn-1409631253
      name: workflow-of-workflows-fxstn[0]
      phase: Succeeded
      startedAt: "2020-09-16T03:31:38Z"
      templateName: main
      templateScope: local/workflow-of-workflows-fxstn
      type: StepGroup
    workflow-of-workflows-fxstn-1678132251:
      boundaryID: workflow-of-workflows-fxstn
      displayName: workflow2
      finishedAt: "2020-09-16T03:31:45Z"
      hostNodeName: gke-adtestcluster-batch-pool-e2-32-0741dae7-wwk0
      id: workflow-of-workflows-fxstn-1678132251
      inputs:
        artifacts:
        - name: message-artifact
          path: /tmp/message.txt
          s3:
            accessKeySecret:
              key: accesskey
              name: my-gcs-cred
            bucket: adtestclusterbucket
            endpoint: storage.googleapis.com
            key: workflow-of-workflows-fxstn/workflow-of-workflows-fxstn-803943416/message.tgz
            secretKeySecret:
              key: secretkey
              name: my-gcs-cred
        parameters:
        - name: workflowtemplate
          value: workflow-template-submittable
      message: 'failed to load artifacts: open /argo/secret/my-gcs-cred/accesskey:
        no such file or directory'
      name: workflow-of-workflows-fxstn[1].workflow2
      phase: Error
      resourcesDuration:
        cpu: 0
        memory: 0
      startedAt: "2020-09-16T03:31:44Z"
      templateName: triggerWorkflowUsingResourceWithArgument
      templateScope: local/workflow-of-workflows-fxstn
      type: Pod
  phase: Failed
  resourcesDuration:
    cpu: 4
    memory: 4
  startedAt: "2020-09-16T03:31:38Z"

Paste the logs from the workflow controller:
time="2020-09-16T03:31:38Z" level=info msg="Processing workflow" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:38Z" level=info msg="Updated phase  -> Running" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:38Z" level=info msg="Steps node workflow-of-workflows-fxstn initialized Running" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:38Z" level=info msg="StepGroup node workflow-of-workflows-fxstn-1409631253 initialized Running" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:38Z" level=info msg="Pod node workflow-of-workflows-fxstn-803943416 initialized Pending" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:38Z" level=info msg="Created pod: workflow-of-workflows-fxstn[0].make-artifact (workflow-of-workflows-fxstn-803943416)" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:38Z" level=info msg="Workflow step group node workflow-of-workflows-fxstn-1409631253 not yet completed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:38Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=14930233 workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:39Z" level=info msg="Processing workflow" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:39Z" level=info msg="Updating node workflow-of-workflows-fxstn-803943416 message: ContainerCreating"
time="2020-09-16T03:31:39Z" level=info msg="Skipped pod workflow-of-workflows-fxstn[0].make-artifact (workflow-of-workflows-fxstn-803943416) creation: already exists" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:39Z" level=info msg="Workflow step group node workflow-of-workflows-fxstn-1409631253 not yet completed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:39Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=14930240 workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:40Z" level=info msg="Processing workflow" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:40Z" level=info msg="Skipped pod workflow-of-workflows-fxstn[0].make-artifact (workflow-of-workflows-fxstn-803943416) creation: already exists" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:40Z" level=info msg="Workflow step group node workflow-of-workflows-fxstn-1409631253 not yet completed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:42Z" level=info msg="Processing workflow" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:42Z" level=info msg="Updating node workflow-of-workflows-fxstn-803943416 status Pending -> Running"
time="2020-09-16T03:31:42Z" level=info msg="Workflow step group node workflow-of-workflows-fxstn-1409631253 not yet completed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:42Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=14930254 workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:43Z" level=info msg="insignificant pod change" key=argo/workflow-of-workflows-fxstn-803943416
time="2020-09-16T03:31:43Z" level=info msg="Processing workflow" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:43Z" level=info msg="Setting node workflow-of-workflows-fxstn-803943416 outputs"
time="2020-09-16T03:31:43Z" level=info msg="Workflow step group node workflow-of-workflows-fxstn-1409631253 not yet completed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:43Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=14930260 workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="Processing workflow" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="Updating node workflow-of-workflows-fxstn-803943416 status Running -> Succeeded"
time="2020-09-16T03:31:44Z" level=info msg="Step group node &NodeStatus{ID:workflow-of-workflows-fxstn-1409631253,Name:workflow-of-workflows-fxstn[0],DisplayName:[0],Type:StepGroup,TemplateName:main,TemplateRef:nil,Phase:Running,BoundaryID:workflow-of-workflows-fxstn,Message:,StartedAt:2020-09-16 03:31:38 +0000 UTC,FinishedAt:0001-01-01 00:00:00 +0000 UTC,PodIP:,Daemoned:nil,Inputs:nil,Outputs:nil,Children:[workflow-of-workflows-fxstn-803943416],OutboundNodes:[],StoredTemplateID:,WorkflowTemplateName:,TemplateScope:local/workflow-of-workflows-fxstn,ResourcesDuration:ResourcesDuration{},HostNodeName:,} successful" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="node workflow-of-workflows-fxstn-1409631253 phase Running -> Succeeded" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="node workflow-of-workflows-fxstn-1409631253 finished: 2020-09-16 03:31:44.740506569 +0000 UTC" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="StepGroup node workflow-of-workflows-fxstn-1342667872 initialized Running" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="SG Outbound nodes of workflow-of-workflows-fxstn-803943416 are [workflow-of-workflows-fxstn-803943416]" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="Pod node workflow-of-workflows-fxstn-1678132251 initialized Pending" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="Created pod: workflow-of-workflows-fxstn[1].workflow2 (workflow-of-workflows-fxstn-1678132251)" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="Workflow step group node workflow-of-workflows-fxstn-1342667872 not yet completed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:44Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=14930268 workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:45Z" level=info msg="insignificant pod change" key=argo/workflow-of-workflows-fxstn-1678132251
time="2020-09-16T03:31:45Z" level=info msg="Processing workflow" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:45Z" level=info msg="Updating node workflow-of-workflows-fxstn-1678132251 message: PodInitializing"
time="2020-09-16T03:31:45Z" level=info msg="node workflow-of-workflows-fxstn-1409631253 phase Succeeded -> Running" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:45Z" level=info msg="Step group node &NodeStatus{ID:workflow-of-workflows-fxstn-1409631253,Name:workflow-of-workflows-fxstn[0],DisplayName:[0],Type:StepGroup,TemplateName:main,TemplateRef:nil,Phase:Running,BoundaryID:workflow-of-workflows-fxstn,Message:,StartedAt:2020-09-16 03:31:38 +0000 UTC,FinishedAt:2020-09-16 03:31:44 +0000 UTC,PodIP:,Daemoned:nil,Inputs:nil,Outputs:nil,Children:[workflow-of-workflows-fxstn-803943416],OutboundNodes:[],StoredTemplateID:,WorkflowTemplateName:,TemplateScope:local/workflow-of-workflows-fxstn,ResourcesDuration:ResourcesDuration{},HostNodeName:,} successful" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:45Z" level=info msg="node workflow-of-workflows-fxstn-1409631253 phase Running -> Succeeded" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:45Z" level=info msg="SG Outbound nodes of workflow-of-workflows-fxstn-803943416 are [workflow-of-workflows-fxstn-803943416]" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:45Z" level=info msg="Labeled pod argo/workflow-of-workflows-fxstn-803943416 completed"
time="2020-09-16T03:31:45Z" level=info msg="Skipped pod workflow-of-workflows-fxstn[1].workflow2 (workflow-of-workflows-fxstn-1678132251) creation: already exists" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:45Z" level=info msg="Workflow step group node workflow-of-workflows-fxstn-1342667872 not yet completed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:45Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=14930279 workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Processing workflow" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Labeled pod argo/workflow-of-workflows-fxstn-803943416 completed"
time="2020-09-16T03:31:46Z" level=info msg="Updating node workflow-of-workflows-fxstn-1678132251 status Pending -> Error"
time="2020-09-16T03:31:46Z" level=info msg="Updating node workflow-of-workflows-fxstn-1678132251 message: failed to load artifacts: open /argo/secret/my-gcs-cred/accesskey: no such file or directory"
time="2020-09-16T03:31:46Z" level=info msg="node workflow-of-workflows-fxstn-1409631253 phase Succeeded -> Running" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Step group node &NodeStatus{ID:workflow-of-workflows-fxstn-1409631253,Name:workflow-of-workflows-fxstn[0],DisplayName:[0],Type:StepGroup,TemplateName:main,TemplateRef:nil,Phase:Running,BoundaryID:workflow-of-workflows-fxstn,Message:,StartedAt:2020-09-16 03:31:38 +0000 UTC,FinishedAt:2020-09-16 03:31:44 +0000 UTC,PodIP:,Daemoned:nil,Inputs:nil,Outputs:nil,Children:[workflow-of-workflows-fxstn-803943416],OutboundNodes:[],StoredTemplateID:,WorkflowTemplateName:,TemplateScope:local/workflow-of-workflows-fxstn,ResourcesDuration:ResourcesDuration{},HostNodeName:,} successful" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="node workflow-of-workflows-fxstn-1409631253 phase Running -> Succeeded" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="SG Outbound nodes of workflow-of-workflows-fxstn-803943416 are [workflow-of-workflows-fxstn-803943416]" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Step group node workflow-of-workflows-fxstn-1342667872 deemed failed: child 'workflow-of-workflows-fxstn-1678132251' failed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="node workflow-of-workflows-fxstn-1342667872 phase Running -> Failed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="node workflow-of-workflows-fxstn-1342667872 message: child 'workflow-of-workflows-fxstn-1678132251' failed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="node workflow-of-workflows-fxstn-1342667872 finished: 2020-09-16 03:31:46.793586571 +0000 UTC" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="step group workflow-of-workflows-fxstn-1342667872 was unsuccessful: child 'workflow-of-workflows-fxstn-1678132251' failed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Outbound nodes of workflow-of-workflows-fxstn-1678132251 is [workflow-of-workflows-fxstn-1678132251]" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Outbound nodes of workflow-of-workflows-fxstn is [workflow-of-workflows-fxstn-1678132251]" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="node workflow-of-workflows-fxstn phase Running -> Failed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="node workflow-of-workflows-fxstn message: child 'workflow-of-workflows-fxstn-1678132251' failed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="node workflow-of-workflows-fxstn finished: 2020-09-16 03:31:46.793654254 +0000 UTC" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Checking daemoned children of workflow-of-workflows-fxstn" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Updated phase Running -> Failed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Updated message  -> child 'workflow-of-workflows-fxstn-1678132251' failed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Marking workflow completed" namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Checking daemoned children of " namespace=argo workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:46Z" level=info msg="Workflow update successful" namespace=argo phase=Failed resourceVersion=14930284 workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:47Z" level=info msg="workflow-of-workflows-fxstn released all acquired locks"
time="2020-09-16T03:31:47Z" level=info msg="Labeled pod argo/workflow-of-workflows-fxstn-1678132251 completed"
time="2020-09-16T03:31:47Z" level=info msg="Workflow update successful" namespace=argo phase=Failed resourceVersion=14930284 workflow=workflow-of-workflows-fxstn
time="2020-09-16T03:31:48Z" level=info msg="Labeled pod argo/workflow-of-workflows-fxstn-1678132251 completed"

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@sarabala1979 says he is not sure if resource template support artifacts. He will investigate.

Input artifacts are only supported in Container and Script templates.

@sarabala1979 I was attempting to work around the issue in #3907, where a many (5k+) node workflow won't start. I was unable to get batching the parameters [[1k items],[1k items]] to work as you suggested there, so instead I tried to pass them in as a .csv artifact, and add a step that batches them into separate json lists, then spins up separate workflows to handle each.
Do you have any suggestions for how I might approach this?

Instead of using the Resource template. you can use a container template with kubectl docker image to create k8s resources.

you can do

Step1 : split the big file into multiple files and upload them to Artifact repo. The step1 will output JSON array format of each item 1000k artifact names.
Step2:  Pass Step1 output.result as withParam and  step2 template has input artifacts and refer the parameter value as key

I will try to get some sample workflow for you this weekend

Input artifacts are only supported in Container and Script templates.

@sarabala1979  Is the documentation wrong than? (https://argoproj.github.io/argo/fields/#workflowspec) It states Arguments contain the parameters **and artifacts** sent to the workflow entrypoint Parameters are referencable globally using the 'workflow' variable prefix
I am also trying to pass artifacts to a subworkflow and get a similiar error as mentioned in this issue:
failed to load artifacts: open /argo/secret/XX-argo-artifacts-sa/service-account: no such file or directory

I stumbled over the same issue (my setup is described in https://github.com/argoproj/argo/issues/4796)
My use cases is: A lot of my workflow templates are quite similar and I want to remove duplication.
Example:
WorkflowTemplates:

apply-config
change-and-apply-config

I want to change the config and than call 1 from within 2 as the apply logic is exactly the same. The files to be applied should be passed from 2 to 1


Random message/quote/cat gif

Cat gif API:
https://www.mashape.com/lilbbytrimble/random-cat-gif
Quote API
https://www.mashape.com/andruxnet/random-famous-quotes
Message API:
https://www.mashape.com/ajith/messages

Cat gif function added
https://github.com/joshcoales/Hallo/commit/e0f71e901987ca4bb8b2d2e8eb92ea99ba9c39c8

random quote added with this API:
https://market.mashape.com/andruxnet/random-famous-quotes#
https://github.com/joshcoales/Hallo/commit/ac63aa16bc359bb3828dd2723baf6dd10e87932e

Random message has been abandoned, the api doesn't seem to function or respond with useful messages

Random person added with this commit
https://github.com/joshcoales/Hallo/commit/307079036e8476d8bad871121429b6b5ddbe725d
and later modified

https://github.com/joshcoales/Hallo/pull/129


Add RethinkDB adapter

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5782582-add-rethinkdb-adapter?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github).

https://github.com/rom-rb/rom-rethinkdb

OK I'm going to close this one since now it's a WIP and we have the repo (:


Add MoLeRGenerator model

Add the MoLeRGenerator model which samples molecules autoregressively using the MoLeR decoder. Refactor MoLeRVae so that I can do this without too much code duplication.

Actually, one more thing: I guess we need to update README.md to replace the uses of ModelWrapper with VaeWrapper, as the former is now an abstract base class that cannot be instantiated?

Actually, one more thing: I guess we need to update README.md to replace the uses of ModelWrapper with VaeWrapper, as the former is now an abstract base class that cannot be instantiated?

Done. I also added VaeWrapper and GeneratorWrapper to __init__.py.


ProjectRoot() not working in .py-files

ProjectRoot() from paths/project_root.py does not work when running from .py file. Only works when used from .ipynb

You need to add more detail:

Environment
How are you executing the py files?
Are you opening them "as Notebooks" in Jupyterlab?

Works in my testing.

Dapla Lab
Percent-py file "opened as notebook"
ProjectRoot().path returns folder one step out

Here is my testcode:
https://github.com/statisticsnorway/ssb-fagfunksjoner/blob/debug_projectroot_pyfiles/demos/project_root.py
Please provide more information about the situation where it (what?) was not working.


Constant stuttering on latest PimaxXR now am not able to use PimaxXR 0.1.2

Hi,
I have a periodic stutter which basically makes DCS unplayable as it happens almost all the time (even when playing offline) when using PimaxXR 0.3.2 and OXRTK 1.2.4 in DCS <IP_ADDRESS>854.1 Open Beta. However I have had this issue in many versions of DCS and in all versions of PimaxXR, except 0.1.2 with OXRTK 1.1.0.
With PimaxXR 0.1.2 these stutters were non existent, so I got around the issue by never upgrading PimaxXR. Unfortunately now PImaxXR 0.1.2 just causes DCS to crash when it boots, so I'm forced to use the latest PimaxXR which comes along with this stutter :-(
When doing the exact same instant action mission using SteamVR these spikes are not present and its smooth.
Between the stutters with PimaxXR I can see that the fps is quite a bit higher than when using SteamVR, but sadly the stutters just make it unplayable.
Any advice on how to resolve this would be much appreciated.
My Specs:
Windows 10
Intel i9 10900K
Gigabyte AORUS GeForce RTX 3090 XTREME WATERFORCE WB
Gigabyte Z490 AORUS ULTRA
M.2 Storage
pimax-openxr.log

There is something about the way DCS uses OpenXR that does not work well with PimaxXR > 0.2.8. I'm aware of this issue, however I will likely not have a chance to work on that until May.
I am told that using OpenComposite rather than DCS native OpenXR mode still works, as long as you are not using DCS OpenBeta multi-threaded mode.
I am also told that people a found a combination of Turbo Mode and frame throttling that removes the issue (see my Discord). I've tested neither of these, since again, I am off this project at this time.

I seem to have the same issue. Glitch, stutter, wiggling, "2nd picture with big offset" caused by my head movements or objects in DCS moving. unusable.
Weirdly when I hit "Alt+Tab" to bring another App in the foreground the Problem is gone! Window out of focus and therefore unable to interact but when I look around I get no stutters or dragging glitching picture anymore.
Constant 70+ FPS on the FPS counter.
System: All maxed out :) i9+4090+64gb ram+(...)

Weirdly when I hit "Alt+Tab" to bring another App in the foreground the problem is gone

Do you have windows HAGS on? This issue happens to me when I have windows HAGS on and goes away if I turn it off.

Weirdly when I hit "Alt+Tab" to bring another App in the foreground the problem is gone

Do you have windows HAGS on? This issue happens to me when I have windows HAGS on and goes away if I turn it off.

Seems to only solve the problem partially. The stutters and the drag is 99% gone. But the frame drops and wiggling stays terrible. Wonder if it's tracking issues. Never mind. Thanks for your help anyways. And of course for what you have created. :)

Can you try PimaxXR 0.3.4 with Pimax Client 1.10? The combination of both is reported to have no performance issues?

I will try that. Thank you very much. I will let you know how it goes!Jan SundagMotion.Design.Artist.Filmkonzeption // Regie //Animation/Post // @.*** 08.05.2023 um 08:39 schrieb Matthieu Bucchianeri @.***>:
Can you try PimaxXR 0.3.4 with Pimax Client 1.10? The combination of both is reported to have no performance issues?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Hello,first of all thanks again for what you are providing.I will try and give you a more detailed description of the problem I am seeing:I am on PimaxXR v0.3.4Pitool Version <IP_ADDRESS>7(I am downloading Pimax Client 1.10 from OpenMR now. I assume thats what you meant(?))I run a “--force_enable_VR --force_OpenXR” DCS openbeta multithreaded shortcut from desktop.DCS openbeta <IP_ADDRESS>090Weird issue:Soon as I get into the DCS Main Menue my vision slowly starts “wobbling”. Within 5 sec it gets really bad so that I have to close my eyes not to get sick. If I dont move the mouse and wait long enough ( maybe 20 sec) it settles. Then I can see that my head movement is crazy “amplified”. The tiniest movement becomes a bigger shake. I can see the micromovements my head makes when I concentrate to keep it 100% still. I can see micromovents caused by my very calm heartbeat for example. Looks like when I then move the mouse i get back to the heavy shakes from the beginning. Weird enough when I then start any mission in a plane it’s completely gone. Everything runs fine! Also in mission editor. It seems that loading into an entirely other part of the application fixes it. Coming back to the Menue the issue is back right away.If you are intersted in this problem I will be happy to provide more info and whatever kind of data you need.Thanks againBestJanJan SundagMotion.Design.Artist.Filmkonzeption // Regie //Animation/Post // @.*** 08.05.2023 um 08:39 schrieb Matthieu Bucchianeri @.***>:
Can you try PimaxXR 0.3.4 with Pimax Client 1.10? The combination of both is reported to have no performance issues?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Sry to bother you further but this might also really help me:Where does PimaxXR take the “floor hight” from and what is it? How is this set and can it be adjusted? Its about 25cm above my actual head hight when I sit in the seat.Might this be the reason my vision is “rolling out of the cockpit” in DCS?Thanks again.JanJan SundagMotion.Design.Artist.Filmkonzeption // Regie //Animation/Post // @.*** 22.05.2023 um 21:27 schrieb Jan Sundag @.>:Hello,first of all thanks again for what you are providing.I will try and give you a more detailed description of the problem I am seeing:I am on PimaxXR v0.3.4Pitool Version <IP_ADDRESS>7(I am downloading Pimax Client 1.10 from OpenMR now. I assume thats what you meant(?))I run a “--force_enable_VR --force_OpenXR” DCS openbeta multithreaded shortcut from desktop.DCS openbeta <IP_ADDRESS>090Weird issue:Soon as I get into the DCS Main Menue my vision slowly starts “wobbling”. Within 5 sec it gets really bad so that I have to close my eyes not to get sick. If I dont move the mouse and wait long enough ( maybe 20 sec) it settles. Then I can see that my head movement is crazy “amplified”. The tiniest movement becomes a bigger shake. I can see the micromovements my head makes when I concentrate to keep it 100% still. I can see micromovents caused by my very calm heartbeat for example. Looks like when I then move the mouse i get back to the heavy shakes from the beginning. Weird enough when I then start any mission in a plane it’s completely gone. Everything runs fine! Also in mission editor. It seems that loading into an entirely other part of the application fixes it. Coming back to the Menue the issue is back right away.If you are intersted in this problem I will be happy to provide more info and whatever kind of data you need.Thanks againBestJanJan SundagMotion.Design.Artist.Filmkonzeption // Regie //Animation/Post // @. 08.05.2023 um 08:39 schrieb Matthieu Bucchianeri @.***>:
Can you try PimaxXR 0.3.4 with Pimax Client 1.10? The combination of both is reported to have no performance issues?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Please try the new release 0.4.0.


Hindi Language Support Added For PDF #4715

Bug
Link: https://github.com/bagisto/bagisto/issues/4715
Information

All language in the same PDF files is still not supported because right now currently it is not available anywhere. So the major challenge is about Arabic so I detected the language and then changed its font to its respective one.

Code additions

Right now Noto Sans is the one which supports mainly all languages but still Arabic not supported so for that we are using the Deja Vu Sans.
Added sample Hind fonts also.
fonts folder is needed in storage folder to support the dompdf multi-language.

Steps to execute this pull request

Run php artisan vendor:publish --all --force to publish the fonts from the UI package to the public directory.
Run php artisan optimize.
Done :100:

@devansh-webkul
the changes are only implemented on admin package, please fix it for customer also https://prnt.sc/10irdpp

@vaishaliwebkul,
The mentioned issue has been fixed.


[BUG] Shortkeys in context menu

VS Code version
OS
Extension version

1.14.0 and 1.15.0 -insider
Win 10 x64 pro (french) 14393
0.8.1

Steps to reproduce
Right click to display context menu in a markdown file.
Results
Screenshot speaks for itself. Red frame is for another extension with the same issue. See at the image bottom for your extension.

But note that the shortkeys work as expected despite the cosmetic issue and another extension share the same issue: Markdown Shortcuts
If it is a VSCode bug, refer its issue number so we can go to vote for it.
Thanks

FYI, I opened issue Microsoft/vscode#30617

Thanks. Sad to read that VSCode team doesn't seem to want to involve in that electron bug.


how to set cluster.name property in SSL connection

Issue description
i need to set cluster.name property but i don't know how to do it  in elasticsearch-hadoop.

Thanks very much for your interest.
This appears to be a user question, and we'd like to direct these kinds of things to the forums. If you can stop by there, we'd appreciate it. This allows us to use GitHub for verified bug reports, feature requests, and pull requests.
There's an active community in the forums that should be able to help get an answer to your question. As such, I hope you don't mind that I close this.


ENYO-6279: Switch to ESLint from TSLint

Adds peer dependencies as dev dependencies to support local linting and linked usage.
Adds typescript support via @typescript-eslint/eslint-plugin and @typescript-eslint/parser.
Uses babel rules when possible to avoid edge-case false positives.

Enact-DCO-1.0-Signed-off-by: Jason Robitaille<EMAIL_ADDRESS>

In my experience reviewing this, I could not get linting to work using my existing eslint 5.x install. I needed to upgrade to eslint 7.x (although I believe 6 will work as well).

Evaluating the changes, this will be a 2.0 config due to new dependencies (typescript stuff + jsx-a11y), plus updated existing dependencies, with new rules. So we'll drop 5.x support and stick with 6.x and 7.x and later.
People wishing to stay on ESLint 5.x after the framework is updated for this enhanced linting will need to install eslint-config-enact-proxy globally and stick to 1.x config. That will allow they in-editor experience to remain unaffected (though naturally very much better and only slightly more effort to just upgrade ESLint to latest anyway.). Old CLI will also still succeed on updated framework, though to match Travis fully (with the new rules in this config), people will want to upgrade CLI.
Once all the PRs are merged, it will be vastly easier to manage eslint global install too, so I consider this a justifiable update.


Replaced WebRequest with RestSharp

Removed support for .net 3.5.
Would like someone to test it with aws.
Also haven't tested what happens when using it with .net core.

Updated the dependency for .net core and it's working :)

This answers issue #48

Wow! thanks a lot @erangil2 😃
I added just few comments


🌱 update grpc option for cloudevent client.

Summary
This PR tries to update the grpc option for the cloudevent client.

remove topic from publish and subscription requests
add source to subscription request

Related issue(s)
Fixes #

/hold

/unhold

LGTM


Card collection modifying chips

At the top of a card collection UI should be controls for modifying the collection. The underlying set should be a drop-down, then filters with an x and a + to add filters (what's the UI for doing compound or dynamic ones?) , and then an optional sort
CollectionDescription would have a CopyWithoutFilter(filterName), and CopyWithFilter(filterName)

See #498


Module parse failed. Unexpected character '#'.

Expected behavior
I would like to write some unit test. But encountered the following error.
I seems like require.context is not able to parse the part #! /usr/bin/env node by:
const srcContext = require.context('../../app/src/renderer', true, /^\.\/(?!main(\.js)?$)/)

However, this is within a node_modules. But node_modules are not included for test.
The error part:
ERROR in ./app/~/JSONStream/index.js
Module parse failed: /Users/fluency03/Workplace/github/dockeron/app/node_modules/JSONStream/index.js Unexpected character '#' (1:0)
You may need an appropriate loader to handle this file type.
| #! /usr/bin/env node
|
| var Parser = require('jsonparse')
 @ ./app/~/docker-modem/lib/modem.js 11:15-36
 @ ./app/~/dockerode/lib/docker.js
 @ ./app/src/renderer/js/docker.js
 @ ./app/src/renderer ^\.\/(?!main(\.js)?$)
 @ ./test/unit/index.js

Actual behavior
$npm run unit

><EMAIL_ADDRESS>unit /Users/fluency03/Workplace/github/dockeron
> cross-env BABEL_ENV=testing-unit karma start test/unit/karma.conf.js

(node:19628) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
Hash: bd5b9b00eb149df15584
Version: webpack 2.3.2
Time: 3925ms
   Asset     Size  Chunks  Chunk Names
index.js  1.41 MB       0  index.js
chunk    {0} index.js (index.js) 510 kB [entry] [rendered]
    [9] ./app/src/renderer/js/docker.js 389 bytes {0} [built]
   [10] ./app/src/renderer/vuex/modules/index.js 236 bytes {0} [built]
   [11] ./app/src/renderer/vuex/mutation-types.js 123 bytes {0} [built]
   [13] ./app/src/renderer/components/HomePageView.vue 1.63 kB {0} [built]
   [20] ./app/src/renderer/vuex/actions.js 306 bytes {0} [built]
   [21] ./app/src/renderer/vuex/getters.js 87 bytes {0} [built]
   [22] ./app/src/renderer/vuex/modules/counters.js 459 bytes {0} [optional] [built]
   [23] ./app/src/renderer/vuex/store.js 318 bytes {0} [built]
   [25] ./app/src/renderer/components/HomePageView/SingleContainerView.vue 1.7 kB {0} [built]
   [41] ./app/src/renderer/routes.js 273 bytes {0} [optional] [built]
   [42] ./app/src/renderer/App.vue 1.53 kB {0} [optional] [built]
   [45] ./app/src/renderer ^\.\/(?!main(\.js)?$) 796 bytes {0} [built]
   [46] ./test/unit/specs \.spec$ 184 bytes {0} [built]
   [96] ./test/unit/index.js 238 bytes {0} [built]
   [97] ./test/unit/specs/HomePageView.spec.js 455 bytes {0} [optional] [built]
     + 110 hidden modules

ERROR in ./app/~/JSONStream/index.js
Module parse failed: /Users/fluency03/Workplace/github/dockeron/app/node_modules/JSONStream/index.js Unexpected character '#' (1:0)
You may need an appropriate loader to handle this file type.
| #! /usr/bin/env node
|
| var Parser = require('jsonparse')
 @ ./app/~/docker-modem/lib/modem.js 11:15-36
 @ ./app/~/dockerode/lib/docker.js
 @ ./app/src/renderer/js/docker.js
 @ ./app/src/renderer ^\.\/(?!main(\.js)?$)
 @ ./test/unit/index.js
Child html-webpack-plugin for "index.html":
         Asset    Size  Chunks  Chunk Names
    index.html  544 kB       0
    chunk    {0} index.html 541 kB [entry]
        [0] ./~/lodash/lodash.js 540 kB {0} [built]
        [1] ./~/html-webpack-plugin/lib/loader.js!./app/index.ejs 1.02 kB {0} [built]
        [2] (webpack)/buildin/module.js 517 bytes {0} [built]

Tell me about your development environment.

Node version: v7.7.4
NPM version: 4.1.2
Operating System: OSX

@fluency03
Sorry for the issue you are running into. I had issues trying to get the testing environment to treat dependencies as externals. For the moment, this will be added to the next Milestone and hopefully fixed in the coming weeks. If you find any work around feel free to post them below.

Until testing within the Vue community is improved, there unfortunately isn't much I can do here. The one main blockage for this is that karma-webpack doesn't provide any support for using externals (https://github.com/webpack-contrib/karma-webpack/issues/125), which is a major need for native node modules. The most I could recommend is just don't test those components until something in the community finds a solution for this.


Request to build a docker image

Personally I really like this theme, but I am unable to build it locally due to some unknown reason and I ended up moving to https://github.com/alshedivat/al-folio
Could you make a pre-build docker image so that weak people like me can avoid some unknown errors?

so what's the unknown error


Optional field syntax is not supported

See also Yurihaia/nbtdoc-rs@a0800c0ba2d9b1be24423f07d17cee85404c0c2e.
This will bring complexity to the nbtdoc type assignability checker. Right now any compound types are assignable to each other, as all fields are considered optional. This addition to the nbtdoc specification added a new concept of required fields, forcing the assignability checker to be aware of the required keys in each compound definition before checking the assignability between them.

Also a somehow related question: what does "optional" mean in this case? Does it mean optional when reading, or optional when writing to NBT?

Well this is kinda difficult to do as fulfilling required NBT can occur over multiple commands

I think it's ok for Spyglass to ignore whether a field is marked as optional or not, and treat every field as if it were optional. The reason the optional field syntax was added is to allow future support to validate NBT files. In those cases it needs to differentiate between the required id field and the optional tag field in item compounds.


remove declaration_count and declaration_limit from employees response

https://github.com/edenlabllc/ehealth.api/issues/3416

Coverage decreased (-0.02%) to 88.3% when pulling fbe565441d25f0b1b77ae564c84e74b044839cc5 on drop_declaration_limit#3416 into f46e85273507786ce557b9783f40f62306e649ae on develop.


fix: codebuild cleanup script

Description of changes

Grant executable permissions on refresh-credentials.sh script.
Use correct credentials and Test Account role for e2e cleanup script. This fixes the error shown below:

Things to keep in mind for later:

If the cleanup job runs above an hour on average, we will need to introduce a refresh credentials logic into it. We will monitor this data for a period of time.

CDK / CloudFormation Parameters Changed

Issue #, if available

Description of how you validated changes
Tested on beta test accounts.
Checklist

[x] PR description included
[x] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Any CDK or CloudFormation parameter changes are called out explicitly

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1547 (8ea3748) into cb (43cc3d7) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##               cb    #1547   +/-   ##
=======================================
  Coverage   62.54%   62.54%
=======================================
  Files         359      359
  Lines       21430    21430
  Branches     5090     5090
=======================================
  Hits        13403    13403
  Misses       7285     7285
  Partials      742      742

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


test implementation of log prob marginalisation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 56 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.0%) to 69.87%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/experimental/ProbabilisticGraphicalModels/log_prob_bayesnet.jl
0
56
0.0%

Totals

Change from base Build<PHONE_NUMBER>9:
-2.0%

Covered Lines:
1396

Relevant Lines:
1998

💛  - Coveralls