bau-kit fails

After a clean install of bau-kit, the app fails to work, it just says the below without any hyperlinks:
Landing Page
bau Kit Landing Page
This is an example of a minimal site

There are no console errors running in Chrome Version 125.0.6422.142 (Official Build) (64-bit)
I get these errors if I manually try to access the admin.html or index.html pages.
><EMAIL_ADDRESS>preview
> vite preview

[vite-plugin-virtual-mpa]: Generated virtual files:
<dist>/index.html
<dist>/admin.html
  ➜  Local:   http://localhost:4173/
  ➜  Network: use --host to expose
  ➜  press h + enter to show help
[vite-plugin-virtual-mpa]: Rewriting / to /index.html
[vite-plugin-virtual-mpa]: Rewriting / to /index.html
[vite-plugin-virtual-mpa]: Rewriting /api/v1/version to /index.html
3:27:19 AM [vite] http proxy error: /api/v1/version
AggregateError
    at internalConnectMultiple (node:net:1114:18)
    at afterConnectMultiple (node:net:1667:5)
[vite-plugin-virtual-mpa]: Rewriting / to /index.html
3:27:37 AM [vite] http proxy error: /api/v1/version
AggregateError
    at internalConnectMultiple (node:net:1114:18)
    at afterConnectMultiple (node:net:1667:5)
[vite-plugin-virtual-mpa]: Rewriting /landing.html to /index.html

The footer component queries the backend for its version: https://github.com/grucloud/bau/blob/main/examples/bau-kit/src/pages/admin/footer.js
This is just an example on how to query the backend, update the footer component to suit your need.

Sorry, I do not understand how this addresses my question. The app simply
does not seem to do anything. Can you describe what it is supposed to do?
On Wed, Jun 12, 2024, 4:11 AM FredericH @.***> wrote:

The footer component queries the backend for its version:
https://github.com/grucloud/bau/blob/main/examples/bau-kit/src/pages/admin/footer.js
This is just an example on how to query the backend, update the footer
component to suit your need.
—
Reply to this email directly, view it on GitHub
https://github.com/grucloud/bau/issues/105#issuecomment-2162740093, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABF2USYRC4W4E4NZTDS4YWTZHAUELAVCNFSM6AAAAABJGCX43KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSG42DAMBZGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

bau-kit is just an example on how to architect a multi page app. It contains no functionality per se.

Ok, seems like a lot of code to do actually do nothing. Ok to close issue.

From: FredericH @.>
Sent: Wednesday, June 12, 2024 5:39:19 AM
To: grucloud/bau @.>
Cc: Simon Y. Blackwell @.>; Author @.>
Subject: Re: [grucloud/bau] bau-kit fails (Issue #105)
bau-kit is just an example on how to architect a multi page app. It contains no functionality per se.
—
Reply to this email directly, view it on GitHubhttps://github.com/grucloud/bau/issues/105#issuecomment-2162905114, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABF2US6I6FQAAD6B4CVTZA3ZHA6PPAVCNFSM6AAAAABJGCX43KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSHEYDKMJRGQ.
You are receiving this because you authored the thread.Message ID: @.***>


Whitespace recommendation for LESS/SASS operators

Should operators (+, -, etc) have whitespace or no whitespace in style values? Based on the comma whitespace recommendation for color values, I'm leaning towards no whitespace, but some clarity would be nice.
With whitespace:
  width: @gutter * 2 + 100px;
  margin: 0 1px @vertical-margin * 2 10px;

With no whitespace:
  width: @gutter*2+100px;
  margin: 0 1px @vertical-margin*2 10px;

Whitespace and parens are super helpful:
.element {
  width: (@gutter * 2) + 100px;
  margin: 0 1px (@vertical-margin * 2) 10px;
}

They work together super nicely to define natural boundaries for your eyes when skimming code.

Whitespace and parens are super helpful:

Agreed. Would you consider adding this to the guide?

Yup! Haven't had a chance to update the guide recently, but if anyone wanted to see this added sooner rather than later, PRs are most welcome :).

PR'ed! Feedback on wording is welcome.

Fixed in #131.


Add more Azure account logging

To help with debugging scenarios. Added feature to strip out stuff like tokens and the list of domains to keep the log more readable/safer.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 37 (13.51%)  changed or added relevant lines in 4 files are covered.
8 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.02%) to 41.343%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/azurecore/src/account-provider/azureAccountProvider.ts
0
1
0.0%

extensions/azurecore/src/account-provider/auths/azureAuth.ts
0
7
0.0%

src/sql/workbench/services/accountManagement/browser/accountDialog.ts
0
7
0.0%

extensions/azurecore/src/utils/Logger.ts
5
22
22.73%

Files with Coverage Reduction
New Missed Lines
%

extensions/azurecore/src/account-provider/auths/azureAuth.ts
1
32.71%

extensions/azurecore/src/account-provider/azureAccountProvider.ts
1
0%

extensions/azurecore/src/utils/Logger.ts
1
22.5%

src/sql/workbench/services/accountManagement/browser/accountDialog.ts
5
11.61%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
26440

Relevant Lines:
57981

💛  - Coveralls

Note for people looking at issues - since the logs go to an output channel now they won't show up in the console logs. Instead you can find them in the output logs, e.g. "C:\Users\chgagnon\AppData\Roaming\azuredatastudio\logs\20210820T093017\exthost1\output_logging_20210820T093029\2-Azure Accounts.log"
(note that the timestamp generated folder means that we can't easily tell users which folder to get specifically since there could be multiple. If you just use the "Needs Logs" label though those instructions have them zip up the entire logs folder which will contain this one as well so that should be enough)


Initial support for the Data tab

Adds a basic implementation of the Data tab, consisting of a table showing (in particular, Mongo) database operations and its associated metrics.  When an operation is selected, the command (bottom-left) panel will display a formatted version of the operation "command".  (For SQL, this would be the SQL command; for MongoDB, this would be the options JSON.)

Notes:

This PR introduces redux, react-redux, and reselect; the tab is the first to be implemented using that infrastructure.
At the moment, the redux "store" only contains the data needed by this new tab; @avanderhoorn is working on how redux may be applied to the Client as a whole.
At the moment, the redux store stores a transformation of the messages that represent data operations.  I've been having an internal debate about whether the store should instead contain the raw messages and with the transformation done instead as a "selector" for the table component.  I think the former is preferable now, given the simplicity of the store and as it won't overlap too much of @avanderhoorn's work.  The good news is that this would be a pretty simple refactoring that has zero impact on the UI components (yay for redux!).
@avanderhoorn might notice that the "master-detail" component is re-implementation of the one used by the Web Services tab, in particular, one based on flex-box rather than table.  I couldn't get the scrolling/sizing behavior I needed borrowing that tab's implementation so I created one from scratch.  The Web Services tab should be able to move to this, now totally abstract, layout component.

Associated with #105, #109, #110.

I'm good for this to go in :shipit:


Update remaining CC-BYs to CC BY

Type
🐛 Bugfix
Value
Uses correct (non-hyphenated) 'CC BY' attribution in Cardigan (already changed elsewhere).

Yeah, licenseType in the API will return CC-BY with a hyphen, so you’ll need the hyphen if you want to match on that.

Closing in favour of #1378.


merge from arlac77/npm-package-template-esm-only

README.md

docs(README): update from template

Codecov Report

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

@@          Coverage Diff          @@
##           master   #658   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          30     30
  Branches        9      9
=====================================
  Hits           30     30

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 019182d...9c7ae4a. Read the comment docs.

:tada: This PR is included in version 2.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Renaming a Playthrough does not rename the files

It appears like it deletes all the files, whereas all that has happened is that the playthrough has been divorced from them.
Any new saves will be under the new playthrough name, ofc.
Renaming the playthrough back to what it was will 'recover' the original saves, orphaning any new ones.
Quitting out and restarting before reverting the playthrough name will cause the auto-generation of playthrough names function to recover the files into their original playthrough name, leaving the renamed playthrough in place with its own files (if any)
Quitting out and restarting after reverting the playthrough, but also after creating new saves in the temporarily renamed playthrough will recover the orphaned saves into their own whatever-you-renamed-it-to playthrough.

My original code would also (since every slot got a default name of PlaythroughName + " " + SlotNumber) replace any instance of PlaythroughName found in the SlotName, also; having a PlaythroughName of Bar doesn't make much sense if all of the slots are still called Foo 1, Foo 2, etc.


[BUG] Missing numRows in the ColumnarBatch created in GpuBringBackToHost

Describe the bug
GpuBringBackToHost creates the ColumnarBatch without numRows, which will be set to 0 in this case. This can confuse any logic relying on the numRows metric during the query processing, such as adaptive query optimizer. The ColumnarBatch returned would be always regarded as if it were an empty batch.
Expected behavior
The right number of rows should be retrieved from the hostColumns and then set for the ColumnarBatch before it is returned.

@jihoonson great catch. Could you also check other places that we create a ColumnarBatch to be sure there are no other issues like this? The API is kind of bad because you can create a ColumnarBatch and then set the number of rows afterwards.

@revans2 I have checked other places, and did not see any. I agree that this API does not have the best design. I wonder if we should do something about it, such as adding safe wrappers, e.g., rapids.ColumnarBatches.empty() and rapids.ColumnarBatches.create(ColumnVector[] columns, int numRows), and forbidding unsafe APIs.

Regarding forbidding the use of unsafe APIs, I meant that we could use the forbidden API checker to catch them during the build.

Filed https://github.com/NVIDIA/spark-rapids/issues/11369.


Tags/Description of a property

Can the search params be modified to include the dict of Tags for each property as well as the long paragraph like description. Additional info like the property details section which is shown on an individual listing would be great as well.

Hey @reidelkins , can you show me an example of what Tags and "additional info" you're trying to search/retrieve?

A true entertainer's dream home.
Boasting with over 3000 SqFt, .98 acres, roof top deck, balcony, your own private floating dock, massive outdoor patio and a beautiful, enclosed swimming pool.
Property features
Bedrooms
Bedrooms: 5
Bathrooms
Total Bathrooms: 2
Full Bathrooms: 2
1/2 Bathrooms: 1
Interior Features
Breakfast Bar
Breakfast Nook
Ceiling Fan(s)
Flooring: Carpet, Laminate
Appliances
Washer
Refrigerator
Dishwasher
Disposal
Microwave
Garage Door Opener
Dryer
Heating and Cooling
Cooling Features: Central, Central Air
Exterior and Lot Features
Balcony - Screened
Balcony - Unscreened
Deck
Fire Pit
Porch/Patio - Screened
Road Surface Type: Asphalt
Pool and Spa
Pool Features: Pool Cover, Salt System, Concrete, Equipment Included, Screened, Electric Heat
Waterfront and Water Access
Canal Navigation
Dock Private
Land Info
Cul-De-Sac
Wooded
Lot Size Acres: 0.98
Lot Size Square Feet: 42689
Garage and Parking
Garage Spaces: 2
Parking Features: RV/Boat Space (Pvt), Electric Vehicle Charging Station(s)
Home Features
View: Pool, View - West, View - South, Wooded, Canal
Security Features
Security System Owned, Security System
School Information
Elementary School: Tropical
High School: Merritt Island
Middle School: Jefferson
Homeowners Association
Calculated Total Monthly Association Fees: 0
Association Name: HARBOR OAKS
Other Property Info
Source Listing Status: Coming Soon
County: Brevard
Tax Year: 2023
Source Property Type: Residential
Area: 254 - Newfound Harbor
MLS Area Minor: 254 - Newfound Harbor
Source Neighborhood: HARBOR OAKS
Parcel Number: 25-37-07-78-00000.0-0009.00
Subdivision: HARBOR OAKS
Property Subtype: Single Family Detached
Source System Name: C2C
Building and Construction
Total Square Feet Living: 3107
Year Built: 1989
Building Area Total: 3787
Construction Materials: Wood Siding, Stucco
Property Age: 34
Roof: Asphalt
Architectural Style: 2 Story
Utilities
Sewer: Sewer
Cable Available
Here's all the extra details I'm talking about from https://www.realtor.com/realestateandhomes-detail/1725-Harbor-Oaks-Pl_Merritt-Island_FL_32952_M60087-35357?from=srp-list-card
I got the tags working just by adding it at the root level of the area query

@reidelkins can you open a PR since you say you got the tags working and I'll take a look at it? Also the description we previously had but then removed due to real estate people telling us it gives the data a bad look as no high quality data from a MLS would provide that


Fix Top Tags

Looks like these are either hardcoded or not being scraped properly
Displayed data:

Actual top tags from RMP:

The top tags were sorted in the wrong order, showing the least reported ones first.


Expose ActionSet renderer. So that it can be over-ridden [iOS]

fixed via #1717; will close this once merged.


net-kourier should guard the prober against resync flooding

I describe the issue in detail here: https://github.com/knative-sandbox/net-istio/issues/262
Here's the call in net-kourier: https://github.com/knative-sandbox/net-kourier/blob/c31012c0d322c5b9ca2b998d5f71927c803eb92a/pkg/reconciler/ingress/ingress.go#L57

fixed by https://github.com/knative-sandbox/net-kourier/pull/202

/close


Logger Creating functions with format

Added two functions(NewLogfmtLogger() , NewJsonLogger()) for creating logger objects.

Can we change strings like "json" and "fmt" to constants
something akin to https://github.com/piotrkowalczuk/charon/blob/1cb3ccdbf8dbde053a07be4bafb9d2e0184f944e/charond/service.go#L25


Refactor chain ordering away from Ord

Closes #939
This PR is intended to be reviewed commit-by-commit.
This PR undoes some of the changes of https://github.com/IntersectMBO/ouroboros-network/pull/2743.
WIP: still needs more docs

Superseded by #1063


Support at least 2 types of rate control

Rate control where the video codec changes bitrate / resolutions / quality that it producing

Rate control where the receiver changes what encoding it is subscribed to ( and chooses one with a different rate )

That makes sense.

done


psychosocial short stature

This should not be classified as a developmental disorder, even though logically it is that to a certain extent. There should be some subhierarchy of child abuse/neglect-related diseases. I did not see any of these terms at first glance
Here is a review article
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4288037/

related to https://github.com/monarch-initiative/mondo/issues/130


Multiple issues with Unity 2017.3.x, UnityWebRequest, and S3 on iPhone

Are you guys tracking issues with UnityWebRequest in Unity 2017.3.x and 2018.x on iPhone? We've had several issues that have forced us to stay with Unity 2017.2.2f1 (where the issues don't seem to occur). The issues only occur on iPhone (using IL2CPP). We don't see them on Android (not using IL2CPP) nor in the Unity Editor on Windows and Mac.
Issue 1:
When trying to download files from a public bucket on S3 via GetObjectAsync, we occasionally crash with EXC_BAD_ACCESS (code=1, address=0xffffffff00000000). Here's the call stack:
0x00000001025413b4 in ::Job_ExecuteUnityWebRequest() at /Users/builduser/buildslave/unity/build/Modules/UnityWebRequest/Public/Prototypes/UnityWebRequestProto.h:207
0x000000010207c854 in ExecuteJobFunc [inlined] at /Users/builduser/buildslave/unity/build/Runtime/Jobs/Internal/JobQueue.cpp:386
0x000000010207c840 in ::Exec() at /Users/builduser/buildslave/unity/build/Runtime/Jobs/Internal/JobQueue.cpp:440
0x000000010207c7c0 in ::Steal() at /Users/builduser/buildslave/unity/build/Runtime/Jobs/Internal/JobQueue.cpp:573
0x000000010207cb98 in ::ExecuteJobFromQueue() at /Users/builduser/buildslave/unity/build/Runtime/Jobs/Internal/JobQueue.cpp:770
0x000000010207cc78 in ::ProcessJobs() at /Users/builduser/buildslave/unity/build/Runtime/Jobs/Internal/JobQueue.cpp:823
0x000000010207c298 in ::WorkLoop() at /Users/builduser/buildslave/unity/build/Runtime/Jobs/Internal/JobQueue.cpp:893
0x0000000102152d50 in ::RunThreadWrapper() at /Users/builduser/buildslave/unity/build/Runtime/Threads/Thread.cpp:36
0x000000019028575c in _pthread_body ()
0x000000019028566c in _pthread_start ()
0x0000000190282d84 in thread_start ()

Issue 2
The second issue is with PutObjectAsync. When trying to upload files to a secure bucket we get a SignatureDoesNotMatch AmazonServiceException. We saw that some people worked around this by disabling chunkedTransfer on the AWSSDK's UnityWebRequests and it worked for us too.
AmazonServiceException:
ErrorCode=SignatureDoesNotMatch
ErrorType=Sender
Message=The request signature we calculated does not match the signature you provided. Check your key and signing method.
StatusCode=Forbidden

Expected Behavior
GetObjectAsync shouldn't crash and PutObjectAsync shouldn't require the chunkedTransfer workaround.
Current Behavior
As described above for both issues.
Possible Solution
Issue 1: Remain with Unity 2017.2.2f1.
Issue 2: Disable chunkedTransfer or remain with Unity 2017.2.2f1.
Steps to Reproduce (for bugs)
Let me know if you need more info and I'll work to collect it for you. (logs, dumps or whatever)
Context
So far, these issues are preventing us from using the AWS SDK for S3 on the latest versions of Unity.
Your Environment

AWSSDK.Core version used: <IP_ADDRESS> from SDK version <IP_ADDRESS>
Service assembly and version used: S3.dll version <IP_ADDRESS> from SDK version <IP_ADDRESS>
Operating System and version: iPhone iOS 11
Visual Studio version: 2017 version 15.6.0
Targeted .NET platform: v3.5 (Unity)

I also reported this bug to Unity.
https://fogbugz.unity3d.com/default.asp?1020451_tjom5fclu25evsg2

You can now, use sdk of S3 modified and better: https://github.com/IsmaelNascimento/aws-sdk-s3-for-unity


Ramda path

Although not supported in older browsers, as far as I understand Ramda path function is the same as optional chaining and we should be able to easily replace it in our codebases.
Perhaps this is a good time to decommission this function in favor of bundle size and to promote more native coding experience.
Just a thought! and apologies in advance if it is something that is already planned / irrelevant :)

@ArashKianiamphora Just out of curiosity; How is there an impact on the bundle size removing R.path now there is tree-shaking and you can import { equals, … } from 'ramda';`?
When it comes to "decomission" things which are not broken, I think "promoting coding experience" is a very  subjective thing. Apart from functional point-free coding of course, which is the thing Ramda promotes I guess.
So if it'd fit in that last category I'd still hate to refactor our code-base for no concrete value, however at least Ramda's API surface would shrink.

Path allows you to do things like this: R.path(['hardcodedProperty', variableProperty, 'somethingElse'], obj), which I don't think you can do with optional chaining?

@mattgrande keeping what optional chaining not offer is great. but having multiple ways of doing the same things is always something I work to reduce as it increases complexity. as for your example isn't code below an equivalent?
obj?.hardcodedProperty?[variableProperty]?. somethingElse

@semmel tree shaking not always works and not everyone has it setup. "promoting coding experience" is a very subjective thing I agree but removing what already exists allows for more innovative problems worth solving to surface.
The problem I see in code bases atm is:
import _ from ramda
import {path, isEqual} from ramda
....
return data?.value

sure you can educate the team and put custom linter in place but why would anyone wants to give a rope to a developer to hand themselves.
Just my thought

oh no the positive side I believe path is faster than optional changing

@ArashKianiamphora How would you write that without having to ponder on a proper name for x? R.path(["outer", "inner"]) vs. x => x?.outer?.inner?
I still even use R.prop because to a certain level point-free is more readable, and when needed I like my variables properly named.

R.path(["outer", "inner"], x) is equal to x?.outer?.inner I assume.

@ArashKianiamphora:
Your examples all have you knowing the path at the time of source code creation.  How would optional chaining deal with truly dynamic paths?
This is a function I use a lot.  And while I can't share my employer's code, I've recently done something vaguely similar to this:
const getPaths = (obj) =>
  Array .isArray (obj)
    ? obj .flatMap ((x, i) => getPaths (x) .map (p => [i, ...p]))
  : Object (obj) === obj
    ? Object .entries (obj) .flatMap (([k, v]) => getPaths (v) .map (p => [k, ...p]))
  : [[]]

const validator = Object.assign(
  (spec) => {
    const paths = getPaths(spec)
    return (obj) => paths.every(p => path(p, spec) == validator.optional || path(p, obj) != null)
  },
  {
    required: Symbol(),
    optional: Symbol()
  }
)

const spec = {
  foo: validator.optional,
  bar: {
    baz: validator.required,
    qux: {
      corge: validator.required,
      grault: validator.optional
    }
  }
}

const validate = validator (spec)

validate ({foo: 1, bar: {baz: 2, qux: {corge: 3}}}) //=> true
validate ({foo: 1, bar: {box: 2, qux: {corge: 3}}}) //=> false

Would you simply need to recreate path in order to do this?  Or is there some feature of optional chaining that I'm missing?

@ArashKianiamphora

R.path(["outer", "inner"], x) is equal to x?.outer?.inner I assume.

That's not what I asked.
For function pipelining I need to type just R.path(["outer", "inner"]) which is essentially x => x?.outer?.inner. However I really don't like the x or any other name in the latter.

Thank you both for taking the time and answering my questions. at this time I very much feel like I might be missing something about path. 😕
@semmel sorry I don't understand how your example is supposed to find the data to parse through
@CrossEye Thank you for your example, without path
const getPaths = (obj) =>
  Array .isArray (obj)
    ? obj .flatMap ((x, i) => getPaths (x) .map (p => [i, ...p]))
  : Object (obj) === obj
    ? Object .entries (obj) .flatMap (([k, v]) => getPaths (v) .map (p => [k, ...p]))
  : [[]]

const validator = Object.assign(
  (spec) => {
    const paths = getPaths(spec)
    // return (obj) => paths.every(p => R.path(p, ) == validator.optional || R.path(p, obj) != null)
    return (obj) => paths.every(p => spec?.[p] === validator.optional || obj?.[p] !== null)
  },
  {
    required: Symbol(),
    optional: Symbol()
  }
)

const spec = {
  foo: validator.optional,
  bar: {
    baz: validator.required,
    qux: {
      corge: validator.required,
      grault: validator.optional
    }
  }
}

const validate = validator(spec)

console.log(validate({foo: 1, bar: {baz: 2, qux: {corge: 3}}})) //=> true

@semmel sorry end of the day here. I had to read it again to understand 😅 , You are right! that's a good use case, I do not think exists out of the box.
May I suggest a documentation update or rename to something like pathCallback instead.
either way, I am going to close this issue, as I see use for it now.

@ArashKianiamphora:
These two lines definitely don't do the same thing:
    return (obj) => paths.every(p => path(p, spec) == validator.optional || path(p, obj) != null)
    return (obj) => paths.every(p => spec?.[p] === validator.optional || obj?.[p] !== null)

For instance, when looking at a required path of p = [ "bar", "qux", "corge" ], path(p, obj) does something quite different from obj?.[p], which would be the equivalent of the nonsensical obj?.[[ "bar", "qux", "corge" ]].
Nor do I understand the suggestion of pathCallback.  path is a function which takes an array of node names and an object, and returns the value found on that object along the path represented by that array, or undefined if any of those nodes does not exist.  Or, given Ramda's currying, more commonly it's a function which takes such an array and returns a function that takes an object returning the value described.
I have no idea what pathCallback would be.
Also note that now and up until v1.0, Ramda has been code that can run in very old versions of JS.  Even after that, I don't know how soon we would adopt newer features such as optional chaining.  We certainly wouldn't abandon a function simply because the latest spec gives an alternate way to do the same thing.  We would not abandon chain because Array.prototype.flatMap has been introduced.  Not only is it not a full replacement (try it on functions, say), but it offers a different interface.  Ramda presents composable functions, and prototype methods or language syntax will never be a complete substitute.
Perhaps I'm just beating a dead horse, as this issue is already closed.  But such a suggestion makes me wonder if you understand the purpose of Ramda.  The goal is to make it simple to code in the style @semmel suggested above.

That was amazing, thank you both for making the time and explaining. I diffently agree using Ramda in a style that semmel suggested could benefit from utlising Ramda.


[YUNIKORN-2444] Create user guide for the event system

What is this PR for?
User guide to the event system & history tracking.
What type of PR is it?

[ ] - Bug Fix
[ ] - Improvement
[ ] - Feature
[x] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2444
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

I created https://issues.apache.org/jira/browse/YUNIKORN-2512 to address event.requestCapacity. After that is done, I'll update the docs again.


Feature: allow syncing of GitHub contributor list repositories to an insight page

Type of feature
🍕 Feature
Current behavior
Provide the ability to import a contributors lists from GitHub to an insight page.

Example: https://github.com/stars/jessehouwing/lists/contributed-to
Suggested solution
Based on the URL, grab the repositories from the lists and populate the insight page repositories
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

There doesn't seem to be a public API from GitHub that allows you to query for this data, as the feature is still in beta.

Closing as a duplicate of https://github.com/open-sauced/app/issues/2314

Closing as a duplicate of #2314

Not sure this is a duplicate of #2314. It would still be nice to generate a Contributor List based on an Insight page. 2314 was generating an Insight page based on a star list and unrelated.


We need a get-start document to guide how to run the project.

coremodule被注册了两次问题

cool, login problem is fixed


Add RBAC for Configured System console access

Add RBAC for Configured System console access

@miq-bot add_reviewer @h-kataria


Copy to clipboard, copies also the line numbers

anyone know how to get round this one?

I found out it works in plain text mode

Yeah, the different views allow users to copy with and without line numbers.  Is there any way I can make this clearer? You're not the first to hit this problem!

I don't know if there's a use-case where copying the line numbers is useful? Other sites that show line numbers (like pastebin) omit line numbers when highlighting and copying text to clipboard, so this is probably how people expect it to work.
If being able to include line numbers is important, perhaps add that text to the button's tooltip, like "Copy with Line Numbers" or something?

This has changed in the new version so line numbers will not be copied.

Nice!! Thank you for your hard work on this tool, it's been super useful! :)

Closing as this is fixed on www.jsonschema.net.


Sanity check for deprovision retrigger redone

Description
Changes proposed in this pull request:

Checking if GET request for given instanceID returns 404 before deprovisioning again

Related issue(s)

/retest

/retest

/test all


Add My Assets by @256ArtsDeveloper

[x] Project URL: https://www.jaydenirwin.com/myassets/
[x] Update contents.json instead of README
[x] One project per pull request
[x] Screenshot included
[x] Avoid iOS or open-source in description as it is assumed
[x] Use this commit title format if applicable: Add app-name by @github-username
[x] Use approved format for your entry

Thx!


Regression: hover no longer shows source preview

Steps to Reproduce:

selfhost open textFileEditorModelManager.ts
ctrl-hover over the disposeModelIfPossible usage
notice you do not see the contents of the method anymore

=> works in stable
=> I am not sure if this is a TS issue or a hover issue
=> see video

This is because when being asked for a symbol definition TypeScript used to return the full range of that symbol, e.g the full method declaration. Now, TypeScript returns a range which is only the first line of that method declaration.
The preview with mouse hover does the following: When a declaration has an empty range it create a new range from the given range plus 7 lines. However, when a declaration has a range that is being used (with an upper bound). The gif above shows this nicely as the first line of the method declaration is showing.
Unsure what to do. The hover wants to respect the given range  because a method or another symbol might actually only be spanning a single line. TypeScript now seems to return the range of the method name which also isn't always bad and incorrect. Changing the hover and giving up correctness would be OK with me, but I wonder this justifies a rebuild. Likely that other languages show this behaviour ever since.

Yes, I confirmed this is a change on the TypeScript side. Here's typescript 2.1.6:
[Trace - 5:48:56 PM] Sending request: definition (26). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/vscode/src/vs/workbench/services/textfile/common/textFileEditorModelManager.ts",
    "line": 109,
    "offset": 20
}
[Trace - 5:48:56 PM] Response received: definition (26). Request took 2 ms. Success: true
Result: [
    {
        "file": "/Users/matb/projects/vscode/src/vs/workbench/services/textfile/common/textFileEditorModelManager.ts",
        "start": {
            "line": 100,
            "offset": 2
        },
        "end": {
            "line": 105,
            "offset": 3
        }
    }
]

and here's TypeScript 2.2.1:
[Trace - 5:49:54 PM] Sending request: definition (16). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/vscode/src/vs/workbench/services/textfile/common/textFileEditorModelManager.ts",
    "line": 109,
    "offset": 28
}
[Trace - 5:49:54 PM] Response received: definition (16). Request took 1 ms. Success: true
Result: [
    {
        "file": "/Users/matb/projects/vscode/src/vs/workbench/services/textfile/common/textFileEditorModelManager.ts",
        "start": {
            "line": 100,
            "offset": 10
        },
        "end": {
            "line": 100,
            "offset": 32
        }
    }
]

I think we even asked for this sort of behavior at some point: https://github.com/Microsoft/TypeScript/issues/8808
I don't think we should workaround this in vscode. I can either file an issue with TS for restoring the old  the behavior or try adding a workaround in the TS extension for this

We decided not to do a rebuild because of this. @mjbvz Please mention this in the release notes as a temp regression which we will fix soon in insiders.

Suggestion from @joaomoreno is to have some sort of SymbolInformationProvider that can be asked for more things, like provideSymbolInformation(doc, pos): SomeSuperInformationContainingLotsOfInfo. So it would become a 2-step process where we first resolve the location and the resolve the symbol at that location. Needs some more thinking.
Since this is very specific to the hover we should maybe go with a low-profile solution that doesn't require much API change. We also show more surrounding code and highlight the range returned from the provider

of SymbolInformationProvider that can be asked for more things, like provideSymbolInformation(doc, pos): SomeSuperInformationContainingLotsOfInfo

We could actually try to use the DocumentSymbolProvider for this.

I have implemented a new heuristic that works with the indent of the denoted line. It works by starting with the (start) line of the returned range, read that lines indent and then going forward until a line with the same indent is found. That range (capped at 7 lines) will be used the preview range. There is still corner cases to this heuristics but it works a lot better than what we have today.


Publish 7.5-20220511112948+0000

Publish 7.5-20220511112948+0000

@bot-gradle test and merge

OK, I've already triggered a build for you.


SVG Version of the Kaiwa graphics

Greetings!
I would want  to know whether there is an SVG version of the Kaiwa graphics.
I intend to add it to the list of software provided by FASI (an HTML invitation page for XMPP).
See https://git.xmpp-it.net/sch/FASI/issues/1
Thank you!

I noticed the last two issues on this project are both by you. Are you aware that the project has been inactive for 8+ years? There are some forks, but I doubt anyone is looking at this issue tracker.

Yes. I am aware that this project is currently inactive.
Mentioning it, would increase the probability, that someone new might
be a new maintainer for this project.
Hence, I think, that it would be good to include Kaiwa.


python3Packages.mdformat: 0.7.13 -> 0.7.14

Description of changes
https://mdformat.readthedocs.io/en/stable/users/changelog.html

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 164223 run on x86_64-linux 1

3 packages built:

python310Packages.mdformat
python310Packages.mypy-boto3-builder
python39Packages.mdformat


Cmos 166 standalone deployment docs

Also adding a review request for @dhaikney as I know you wanted to look at the structure too.

Couple nitpicks but the technical content looks really good!
@maria-robobug or @RichardSmedley, would you mind taking a look at this from a docs perspective? Thanks!


FlexASIO GUI should not arbitrarily override FlexASIO defaults

It seems that FlexASIO GUI will always set bufferSizeSamples, suggestedLatencySeconds, wasapiExclusiveMode and wasapiAutoConvert, even if the user never touched them.
In general, this is not a good idea, especially for suggestedLatencySeconds, because the default in FlexASIO GUI (zero) is not the same as the FlexASIO default (3x buffer length). This can lead to the user getting confused as to what the real "default" is. This in turn can cause FlexASIO to fail, as suggestedLatencySeconds = 0 is less likely to work than the default. See dechamps/FlexASIO#110 for an example.
There is a similar problem for bufferSizeSamples, which FlexASIO GUI initially overrides to 256. In fact, if the user changes the backend to DirectSound without touching the buffer size, this will very likely result in FlexASIO failing to initialize, because DirectSound inputs are known to fail with such small buffer sizes.
There are very good reasons why the FlexASIO defaults are the way they are. FlexASIO GUI should not mess with them.

Hi, I'm not actively working on this currently since I've been working on a Mac mostly right now. I'll keep it in mind for when/if I pick it up again.

Indeed, I had Buffer checked by default with the 0 value on both in/outputs.
Which makes FlexAsio show an error code when using it with Bitwig in my case.
PS: I'm using the latest FlexAsio GUI version.


Export objects and artists in to discrete JSON files

+1. Providing JSON will save people time when working with this data.

Hey @joshkpeterson.  I hear you, and I've put together something that allows access to the same data via json or xml via REST calls.  It has just been tough to package it up to publish it publicly, notably that I am trying to tackle the issue of allowing public access to at least thumbnail images.  That is a bigger thing than it may seem.  Anyway, you can get a preview here:  https://github.com/smoore4moma/tms-api/blob/master/object.json but that is my personal git space and not related to MoMA.  We'll get there!

@straup @joshkpeterson We +1'd this as well. It's been added to the automated export and will get updates when the CSV get's updated.


Enable default RDF Protocol for subjects of existing data Cluster Setting

Usage:
val cmw = GridSubDiv(... ,
    defaultRdfProtocol = "https"
)

This should be an optional field for mappings (default is "http").
This will affect all existing data that was ingested prior to Yak release and has no "protocol" system field to be rendered with that default Cluster setting.

Related: PR #961

Verified that the option does work. Moving to done.


64 bit reference images should be saved to a separate directory.

64-bit runs often render text slightly different, causing snapshot failures if run on the wrong device.

Same problem with different iOS versions. Recently added FBSnapshotVerifyViewWithReferenceDirectorySuffix to support these differences in general. Wrap that call with your own to map configurations to reference image directories.
Here's an example for 64 bit snapshots:
#define Suffix()
({
#if LP64
NSString *suffix = @"_64";
#else
NSString *suffix = @"";
#endif
})
#define VerifyView(view__, identifier__)
{
FBSnapshotVerifyViewWithReferenceDirectorySuffix(view__, identifier__, Suffix();
}

I also have some macros for that, and for device format (iPhone 5, iPad 2, ...).
Would be nice if we could put this in folders without defining some macros.

Closing in favor of #68


Fresh install of v3.2.16 fails to initialize

please complete the following information:

OS version: Win 10
Editor version: 1.55.0
Programming language: ts
TabNine extension version: 3.2.16 & 3.2.15

If the issue is related to TabNine failure, please provide log files:
Type TabNine::config in your editor, the logs are located at the bottom of the page
Editor console logs:
Help -> Toggle Developer Tools
Issue Details:
So I tried installing the plugin for the first time today. I saw the 'tabnine' icon and name appear at the bottom of vs code in the status bar. But when I clicked it to open the tabnine hub, the page was simply blank. I tried restarting vs code, uninstalling and re-installing. No code completion was happening, and typing TabNine::config did nothing. I then tried rolling back one version to 3.2.15 to see if there was any difference, but the behavior was the same.
I then went all the way back and installed v3.1.26. This time it worked flawlessly. Tabnine hub initialized and I was finally getting completions. I then attempted to upgrade to the latest version, and it is working now.
Based on this, I imagine there is some sort of setup process that the newer version is wrongly expecting to already be there. The newer version probably works for most people if they already have a 3.1.x version installed. However a fresh installation appears to be broken, at least in the two most recent versions as of writing this issue.

Wow, thanks for the valuable feedback @StJohn3D !
We will investigate it on our side, but I have some more follow up questions:

Are you behind a proxy or do you have some firewall that might block Tabnine's communication?
Were you seeing the Initializing Tabnine notification?
Are you using some ssh development environments or WSL?

@boaz-codota no proxy or firewall. I did not see 'Initializing Tabnine' until I went back and installed the 3.1.26 version. The first time I installed the latest version, it just said tabnine 👈  with a hand emoji in the status bar. I clicked it and was taken to the tabnine hub except the entire page was blank. Also the 👈  emoji went away and never came back (assuming that was on purpose just to help me notice it the first time. Nice touch)
Also no ssh or wsl.

@StJohn3D - if it is not a problem can you please uninstall the extension, reload all vscode sessions (vscode uninstall cleanup is running on restart), reinstall the latest version(3.2.16) and send us the console log ( Help -> Toggle Developer Tools)?
Thanks again for the detailed debug session 🙏

Chiming in to say I am having the same issue. Same versions as John. Let me know if I can help you all out in any way!

@dimacodota I am having the same issue. Latest version, VSCode Insiders on M1 Macbook Air.
Attached console logs, let me know if this helps?
I also see a blank page if I go to the Tab Nine hub. I saw the suggestions once, but then it stopped, right after a re-boot it showed but then went away following times.
console.ts:137 [Extension Host] (node:15977) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (at writeOut (internal/process/warning.js:32:3))
m @ console.ts:137
console.ts:137 [Extension Host] Error handling existing version.  Fresh install Lastest vscode on Windows.
   C:\Users\Alice\AppData\Roaming\TabNine
mac :  $HOME/Library/Preferences/TabNine    /Users/Alice/Library/Preferences/TabNine
linux: $XDG_CONFIG_HOME/TabNine or $HOME/.config/TabNine     /home/alice/.config

@dimacodota just sent, thanks :)

@dimacodota send it too.

All, we released a fix (3.3.104 engine version ) please restart and approve

@dimacodota Everything seems to be working now! Good job!


test: unify handling of driver and operator deployment

This removes the code duplication introduced by
b8bfa5a71ab0ddbda0cc1df35b3105eab6a188ba which copied much of
deploy.go into operator.go.
Besides making the overall code base smaller, this is also a step
towards deploying the actual driver through the operator and then
running tests against that driver installation: because the deploy
code will now install either the operator or the driver, we don't get
conflicts when the operator installs the real driver. However, for the
current tests the non-existent image continues to be used because it
probably makes the tests run a bit faster.
Another side effect of the unification is that the operator only gets
deployed once per test suite run.

@avalluri please have a look. Tests have passed.

But in the case of testing driver deployed via operator requires both the combinations.

That then can be "operator-[lvm/direct]-[testing/production]".

And what in my mind was that in this case we deploy single operator for all driver tests suite(regardless of lvm, direct, testing or production).

We could tweak the EnsureDeployment so that it keeps the operator running when switching between operator-* deployments. There are some details to take care of though, like the deployment label of the operator. I see this as an optimization and I am not sure whether it is needed. Deploying the operator is faster than deploying the driver.
If we want to test that a single operator can deploy drivers in different modes, then we should write a dedicated test for it instead of testing it indirectly.

And the other thing what i feel missing is that the operator used to use custom namespace for running the tests.

So we need a test for deploying the operator in custom namespace.

That then can be "operator-[lvm/direct]-[testing/production]".

I've added that, so far only with a simple "does the driver really run" test. That is currently work in progress and doesn't pass:

direct mode: fails to come up (https://github.com/intel/pmem-csi/issues/581)
direct and LVM mode: the deployment lacks the metrics service

I believe this ready now. However, testing on Clear Linux failed, perhaps because the test is flaky (https://github.com/intel/pmem-csi/issues/585). I'm currently retesting.
@avalluri: please take another look

However, testing on Clear Linux failed, perhaps because the test is flaky

This was probably caused by not deleting secrets immediately when tearing down the previous deployment. The operator then proceeded (without an error!) although the existing secrets were in the process of being deleted by the apiserver's garbage collection.

I've extended RemoveObjects to also delete secrets.

I've extended RemoveObjects to also delete secrets.

@pohly I fail to understand why you needed to this deltion manually? this should be done automatically when the deployment gets deleted.

I fail to understand why you needed to this deltion manually? this should be done automatically when the deployment gets deleted.

Because DeleteObjects is supposed to delete everything itself and check that it really is gone (not just in "terminating" state). If the operator is broken for whatever reason, DeleteObjects will fix the cluster and allow the next test to continue.

this should be done automatically when the deployment gets deleted.

Yes, but as we've (probably) seen in the failed test, even in that case we need to wait for deletion. RemoveObjects does that and expedites deletion by trigger it itself.

this should be done automatically when the deployment gets deleted.
Yes, but as we've (probably) seen in the failed test, even in that case we need to wait for deletion. RemoveObjects does that and expedites deletion by trigger it itself.

If deleting of a Deployment object is not cleanig the sub-resources it crated, then its a real failure which we cannot hide by manually deleting them. To make sure that every operator tests starts in a calean environment without effecting these type of issues, running them in diffrente namespace is the right soulution in my opinion.

If deleting of a Deployment object is not cleanig the sub-resources it crated, then its a real failure which we cannot hide by manually deleting them.

This particular feature needs an explicit test, instead of relying on other tests to discover a regression accidentally.

To make sure that every operator tests starts in a calean environment without effecting these type of issues, running them in diffrente namespace is the right soulution in my opinion.

We can't rely on namespaces because we have non-namespaced objects.

@avalluri can we merge this once the current test run (https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/job/pmem-csi/job/PR-575/10) completes?

It has completed now, once without explicit secret removal (which shows that it was indeed a race condition) and once with (which should be more reliable).
I'd like to get this merged so that we can write more tests based on this infrastructure.

@pohly I have no other concerns on this PR than to use  metadata.labels in place of spec.labels.

I have no other concerns on this PR than to use metadata.labels in place of spec.labels.

Have I addressed that? Can we merge?

I have no other concerns on this PR than to use metadata.labels in place of spec.labels.
Have I addressed that? Can we merge?

Yes, it looks good to me. Let's merge this change. so that I will rebase #584.


Unexpected Server Shutdown

Currently, our server has been shut down unexpectedly. We are working with the server provider to get the incident resolved at the earliest. We appreciate your patience and understanding at this very moment and will update all one this is resolved. Thank you!

This issue is resolved. Server is Up and running.
Thanks much, We appreciate your patience and understanding!


Support for adding multiple button in MessageInput for Attachment,Emoticon,Camera

Is there a way to override the existing behaviour of MessageInput so that I can keep multiple button like WhatsApp ?
I will be able to make pull request if you guys give rough idea on how to do it 😃

There's no in-built support for such functionality, butMessageInput extends from RelativeLayout, so it's just a matter of adding those buttons and playing around with some LayoutProperties.

@ynagarjuna1995 IMHO, for this case it's much simpler to create your own view with all of the buttons included.
Best regards, Alex


Update contributors.json

Issue

Description

Checklist

[x] Added contributor object in ascending order in contributors.json
[x] Github action build passing
[x] No merge conflicts

@vigneshshettyin Closing this as you have not permitted maintainer edit and you haven't fixed conflicts and orders the values in ascending order


[ERROR] rubocop is not executable

Stack:

Elementary OS 0.4.1 - Loki
Visual Studio Code 1.17.2
RVM 1.29.3
Ruby 2.3.3
Rubocop 0.48.1

I am trying to configure the rubocop, and I am getting the follow error: "WARN: /home/andre/.rvm/gems/ruby-2.3.3@artia/bin/rubocop + rubocop is not executable".
My actual Paths configuration...
Rubocop Config Path: "/home/andre/Documents/euax/artia-app/.rubocop.yml"
Rubocop Path: "/home/andre/.rvm/gems/ruby-2.3.3@artia/bin/rubocop"
My VSCode have the follow configuration:

{
"workbench.colorTheme": "Quiet Light",
"editor.wordWrap": "on",
"editor.trimAutoWhitespace": true,
"files.trimTrailingWhitespace": true,
"window.zoomLevel": 0,
"files.exclude": {
    "log/*": true
},

"typescript.check.npmIsInstalled": false,

"ruby.rubocop.executePath": "/home/andre/.rvm/gems/ruby-2.3.3@artia/bin/rubocop",
"ruby.rubocop.configFilePath": "/home/andre/Documents/euax/artia-app/.rubocop.yml",
"ruby.rubocop.onSave": true

}

I tried to change the executePath for only the "/home/andre/.rvm/gems/ruby-2.3.3@artia/bin/" without the rubocop complete path, and not works too...
What could be happening? Thanks!!!

Try to add a trailing /:
"/home/andre/.rvm/gems/ruby-2.3.3@artia/bin/rubocop/"

I didn't understan what happened, but now, I removed the source of rubocop, and does worked...
If I have another problem, i write here, thanks for the help.

@andreleoni How do you remove the source of rubocop?

@andreleoni I would also like to know what you mean by removing the source of rubocop. Thanks!

@zachGl thank you, I too forgot to install the rubocop gem.  This solved the error.

@iampnelson @zachGl are you using RVM, and did you mean installing rubocop locally, or globally? I found this: https://pennyforyourcode.com/installing-a-ruby-gem-globally-in-rvm-ffa7222f7e7

@raywu I'm using rbenv and am setting it globally.

@raywu
I am using RVM. Remember to restart your code editor

Just an extra reminder. I forgot to install the rubocop gem when I upgraded Ruby so I was getting the same error.


mmm-pir module

Is it possible to set the relay toggling not only when switching on or off, but during both state changes.
The background is that I want to use the relay to operate my standby button on the monitor.
The relay currently switches off after a set time and switches on again when there is movement. This switches the supply voltage completely. It would be better to leave the power supply permanently connected and only switch the stanby button. But for this you need a change in the state of the relay with every process.
I couldn't get it to work in the settings. where can you change the behavior of the relay? mode 6 and mod 7 at the same time so to speak.
https://github.com/bugsounet/MMM-Pir

Hi @tommyklalau, sorry, this is not the place to handle specific issues of a module. I don't know why the issues are disabled in that repository. Please get in touch with the developer @bugsounet 🙂


Sad mad

This pull request introduces significant enhancements to our application's user interface and user experience. We have integrated Tailwind CSS for utility-first styling and have also added a new homepage.

nice job


Implement solution to use stored blend trees

With the changes we made that allows us to update the poses and see the results in the editor, we had to make sure the blend tree was made unique. This required a "deep copy" to make it reliable.
The downside of this was that we lost the link with the blend trees resource files making it harder to make changes as each hand scene now has a unique copy.
This PR solves this by recording the required blend tree file as an export variable on the hand script, and loading and duplicating that blend tree and assigning it to the animation tree node.
As an added bonus this allows for users to provide their own blend trees if they choose to do so.

Note that if you edit the blend tree files, any open hand scenes won't reflect the change until they are re-opened.

seems to work as @BastiaanOlij intended, tested it with statemachine as well as wit the basic animationtree/handblendtree

With Malcolm not feeling well and Digital having checked this, I'm merging this :)


create a new page for contact and removing it from main frontend page.

create a new page for contact and remove it from main front-end page.

for the new page make the background more attractive.
place the part in the middle of the page.
let the navbar be present as same as in the main page.
same with the footer.

@codetheorem @vinayaksh42 both of you can do this work.  :)

Sure sir @Amankumar29


Helm 3: Cannot build k8s.io/helm w/o helm.sh/helm

Output of helm version:
-bash: helm: command not found
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T18:55:03Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:14:56Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
minikube version: v1.1.0
It looks there are still references to old "helm.sh" folder.
go build  -tags '' -ldflags '-w -s -X helm.sh/helm/internal/version.gitCommit=f109b1ba5cb83eb90481b02eaea3c968b181c279 -X helm.sh/helm/internal/version.gitTreeState=clean' -o /Users/serge/go/src/k8s.io/helm/bin/helm helm.sh/helm/cmd/helm
can't load package: package helm.sh/helm/cmd/helm: cannot find package "helm.sh/helm/cmd/helm" in any of:

@Dare2python Are you building Helm v3? If so then build will fail if not running from the path $GOPATH/src/helm.sh/helm. Refer to doc for more details: https://github.com/helm/helm/blob/dev-v3/docs/install.md#from-source-linux-macos

@hickeyma Thanks!
Apparently, I've got confused of change to k8s.io in master which still v2
https://github.com/helm/helm/blob/master/docs/developers.md

Thats ok. Yes, v2 is still and will remain under k8s.io.


(Win Binary) Issue with -x/-X

Simple -x commands work fine, however, slightly more complex commands fail. This is a Windows version issue.
For example, -x 'net group "Big Boys Group" Wannabe /add' is not going to work, it won't go thru:
nxc.exe: error: unrecognized arguments
-x 'net group Big Boys Group Wannabe /add' will go thru but will return
The group name could not be found.
I've tried running nxc.exe in both PS and cmd.
Btw, this issue was present in cme's binary for windows.

Hey dude! You need to escape your "" otherwise it will break when building the command to run.
Can you try this:  -x 'net group "Big Boys Group" Wannabe /add' pls ?

For example, -x 'net group "Big Boys Group" Wannabe /add' is not going to work, it won't go thru: nxc.exe: error: unrecognized arguments

This is really weird. If you log the debug output with --debug you can see what the command is being ran, and it should run (and it runs if you run it directly in a shell on the host), but something funky is happening with the translation...

@bongobongoland okay I figured it out, I think.  Here's an example command that worked for me:
.\nxc.exe smb ip -u 'user' -p 'pass' -x 'net group \"group name\" user2 /add'
Note the single quotes on the outside and ESCAPED double quotes on the inside.

Yep. That's the trick. Cheers! This must be in our wiki :)

Good idea - the whole Windows binary thing is pretty new (the last one was years ago), so we should definitely add this 👍


[Security/Extension] [WIP]JWT Vendor for extensions

Description
Initial commit of JWT token generator for extensions

Category New feature

Issues Resolved

Relate: https://github.com/opensearch-project/security/issues/2545
Relate: Generate an auth token for an Extension Request (WIP)

Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

While we are having the discussion in this PR, I will create a META issue for Generate an auth token for an Extension Request and add a unit test.

Codecov Report

Merging #2567 (d5bfef3) into main (a5c73f9) will decrease coverage by 0.16%.
The diff coverage is 53.57%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main    #2567      +/-   ##
============================================
- Coverage     61.29%   61.14%   -0.16%
+ Complexity     3334     3332       -2
============================================
  Files           260      261       +1
  Lines         18509    18565      +56
  Branches       3269     3276       +7
============================================
+ Hits          11346    11351       +5
- Misses         5571     5610      +39
- Partials       1592     1604      +12

Impacted Files
Coverage Δ

...opensearch/security/filter/SecurityRestFilter.java
77.77% <ø> (ø)

...g/opensearch/security/authtoken/jwt/JwtVendor.java
53.57% <53.57%> (ø)

... and 8 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Hey, @RyanL1997, I noticed that this code is generating a JWT, but it doesn't seem to be connected with any user scenarios. Can you provide some insight into what you had in mind for the evolution of this pull request so it would be merged?
To enhance the functionality of this pull request, I recommend that we add the ability to generate a validated token for an authenticated user and accept the token and validate it.
Let me know your thoughts on this.

Hi, @peternied. I had a conversation with @cwperks today about the authentication backend. First for answering your questions:

Can you provide some insight into what you had in mind for the evolution of this pull request so it would be merged

I think the purpose of this PR is to setup a basic structure of this JIT token, such as, some of the components we discussed above for token claims: subject, audience ..etc. I guess the only tricky part for now is about the how are we gonna deal with the roles, encrypted/not-encrypted/include/not-included. For these parts, we can discuss it in another review session with a documentations and modify them later, but I think we can use this basic structure for future development. For now, I just started to write a draft PR for authentication backend, and I do need some of the basic concepts from this PR for token verification.

HI @peternied , since this a component of a larger feature (Security for Extensions), should we merge this into a feature branch until the feature is ready to merge to main?

Let's merge changes into the main branch when they benefit security plugin customers. I recommend moving this pull request to a feature/jwt branch, and once it's functional enough for customer use and end-to-end validation, merge it into the main branch.

Hi @scrawfor99, here is a link for place holder. Me and Craig are working on a documentation, and I will transfer that into this issue.


Link to GitHub not working

This extension looks super helpful. Unfortunately, I've been unable to get it working.
I've installed the plugin, and I tried to link it to my GitHub account. It's not connecting to GitHub, but I'm not seeing any errors. It says it's connected but not acting as I expect if it were.
I do see my "Repository" and "Branch" dropdowns in the App Script editor, but they're both empty. I don't see how to link my app script to a repo or create a new repo to store it.
I put in my username and a token in the extension options, and it says I'm logged in, but it doesn't seem to log me in. I tried using my password instead of the token, and that didn't help. I thought it might be because I have 2fa on my GitHub (though the token should still work), but I created a new GitHub account without 2fa, and it doesn't work with the token for that one either.
When I add the Github login info into the extension options, it looks the same whether I've typed in a real password or junk, saying I'm logged in as @Github.com. I would have expected setting the options to test the Github connection and only save it if the credentials are valid. Unfortunately that doesn't seem to be the case.
I may be missing a step somewhere for being able to look at my repos, but if so, I'm not sure what it would be.
Thanks in advance!

please make sure your token has the correct permission, password is not work
the logged in actually just save the token, no real login action

I did use a token with correct permissions. I just tried the password and the bogus password to see what would happen. Using an invalid token should give you an error as soon as you install it though.My colleague was able to use it when he's logged into Chrome using one of his accounts but not when he's logged in using the other. He suspects that there's a problem with the Chrome OAuth.


Add target to links of item type list

Add feature to configure a HTML target type for links of dashboard item type List.

I have added the function to all dashboard elements so that you can add linkTarget anywhere a link can be used in JSON data. The the sample packages have been extended accordingly. The merge is skipped as it is solved differently. Anyway, thanks for your work!


[Notion] Open in notion alternate action

Description
Created from https://github.com/raycast/extensions/issues/9361
Adds another action to open in Notion, which is the opposite of the default open setting. e.g. If primary action is set to open in app, secondary action will open in browser and vice versa. As explained in the linked issue, I think this will be helpful to have a choice of where to open whilst still having the default a user would want.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Could you also hide the alternate action and only show Open in Browser if a user doesn't have the Notion app installed? Otherwise, opening it will fail with an error such as this one:

Good spot, thank you! Had to change the implementation slightly, but all done now 🙂


pull request for e2e test at 11/10/2016 18:26:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[v3] Support multi format schemas in message headers

Description
The current v3 spec mentions that the Message Object headers must be of type "object". Literally says:

Schema definition of the application headers. Schema MUST be of type "object". It MUST NOT define the protocol headers. If this is a Schema Object, then the schemaFormat will be assumed to be "application/vnd.aai.asyncapi+json;version=asyncapi" where the version is equal to the AsyncAPI Version String.

Since the introduction of the support of multi-format schemas, message headers also support different schema formats.
Then, in my head, reading the sentence Schema MUST be of type "object". sounds confusing to me, especially for formats like Avro, where (afaik) there is no such type but record iirc.
This constraint is also in place in the AsyncAPI JSON Schema documents describing the message object. See https://github.com/asyncapi/spec-json-schemas/blob/next-major-spec/definitions/3.0.0/messageObject.json#L21-L27
Is that restriction in place with the purpose of limiting and simplifying what a header looks like? Shall we keep it and update it according to different possible shapes depending on the format? Or rather, after the recent changes, should we get rid of it?
Relates to https://github.com/asyncapi/spec/issues/622
cc @GreenRover @dalelane @derberg @jonaslagoni @fmvilas

yeah, sounds like Schema MUST be of type "object" is just a left over that should be removed. I don't think it is needed.

I vote for keep headers to be only async-api schema formated. To keep it simple. I see no benefit from defining header for example as avro.

Ok, my memories slowly come back. I guess Fran brought an reasons that required non ansycapi-schema as header.
But you @smoya only have concerns about the wording?
What i wanted to say is: Schema MUST be of type "object".
A headers have to be some kind of map.
A string/number like in the body is not valid.

But you @smoya only have concerns about the wording?

Not just wording. As I mentioned in the issue description, that statement goes further as it's in the messageObject JSON Schema https://github.com/asyncapi/spec-json-schemas/blob/next-major-spec/definitions/3.0.0/messageObject.json#L21-L27

I think we should leave the sentence Schema MUST be of type "object" but change it to be broader in terms of the schema formats it supports. For instance, Schema MUST represent a map of key-value pairs..

I guess Fran brought an reasons that required non ansycapi-schema as header.

We should be able to support, at least, Avro because that's what the majority of the Kafka folks are using. Making them write the same information in JSON Schema just to use it in AsyncAPI is not fair.

Schema MUST represent a map of key-value pairs.

Sounds like a more generic term, also not tied to JSON Schema, which is the intention.

We should be able to support, at least, Avro because that's what the majority of the Kafka folks are using. Making them write the same information in JSON Schema just to use it in AsyncAPI is not fair.

I would say we must support all of the schema formats anyway. This also simplifies the schemas and tooling IMHO. No special behavior or exceptions when treating schemas.

FYI, https://github.com/asyncapi/spec-json-schemas/pull/370 got merged and support for all multiple formats is also included for headers.
If there is a strong reason to revert that, please feel free to say it. Otherwise, if all agree, we can close this issue.


2.3.40 broke support for Windows network drive compilation of SASS

Unfortunately, no errors or anything, it simply does not compile SASS.
Downgrading to 2.3.39 fixes it for now.

Unfortunately, no errors or anything, it simply does not compile SASS.
Downgrading to 2.3.39 fixes it for now.

It may be caused by merge code https://github.com/Wscats/compile-hero/pull/88, I will roll back the version first.

I can confirm that the rollback of #88 fixed it. Thanks for looking into the issue!


Uncaught Error: Cannot find module "net", "fs", "tls"

Uncaught Error: Cannot find module "net", "fs", "tls" when i require 'mysql'

This sounds like you're trying to require a module meant to be used only on the server in your client code.
Are you trying to access MySQL from your browser code?

This is a client side app setup.
It is compiled for the browser, not for Node apps.

How to fix this?

It should already work. If it doesn't file a new bug report. Cheers!

it still not work for me.

@naliga24 you should not require mysql in create-react-app because it is for client side.

thank you.
2018-06-30 22:59 GMT+07:00 Jack Zhao<EMAIL_ADDRESS>
@naliga24 https://github.com/naliga24 you should not require mysql in
create-react-app because it is for client side.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/337#issuecomment-401549491,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmnxNqn7mlpsPX3oNqVeGM2Fhv8dzhVXks5uB6BNgaJpZM4JbMEx
.


Add a Code Hunt vote badge to README.md

@henriquea FYI, your repo has been featured today on @CodeHuntIO
http://codehunt.io/sub/minigrid/
TL;DR Code Hunt helps programmers discover and discuss awesome code.
This pull-request adds a "vote" badge to your README.md:

Fingers crossed that we can drive more attention to your brilliant work.
Happy coding!
@chrisjacob ^_^
p.s. I hope you found this PR helpful, if not please let me know.
p.p.s I've also tweeted about your project here https://twitter.com/hunt_javascript/status/627826223532670977

This looks like a cool product but I'm not sure if add a badge is the best way to promote it. I did signed up there and will contribute when possible.
Cheers!


New release

After merging #17/#19 a new release should be cut.
@disko @janjaapdriessen You are maintainers on PyPI, could you please cut a release or give me ('icemac') the rights to do so?

@icemac I've just added you as a maintainer – thanks for your work!

@disko Thank you! I just released https://pypi.org/project/js.deform/2.0.14/


Medications.amount field not included in medications FHIR/CSV

Hi,
Thanks for making a great piece of software! I'm an employee of a QIN/QIO that works with Medicare providers and Synthea data has been immensely helpful in prepping/strawmanning for work with provider HL7 data. I've come across the following issue--
The medications (in both FHIR and CSV format) provides the form and dosage via RxNorm, but the medication.amount field (cf. paragraph 2 here: https://www.hl7.org/fhir/medication.html) is not represented in the data. For drugs that are taken daily (e.g. a patient has a prescription for Simvistatin for 1 year, and there are 12 dispenses) the package size can be inferred. For as-needed or temporarily prescribed drugs (e.g. opioids, benzodiazepenes, stimulants) however, it's not possible to tell how many were prescribed to the patient and calculate MME, for example.
Not urgent or totally necessary, but adding an amount_dispensed field to the medications table could allow some analysis that isn't currently possible.
Thanks again!
Ben

Thanks for the report.
There aren't currently concepts in Synthea that capture the amount of medication per dose or something like that, except as part of the given code/display. In some modules, there is data for prescriptions, dosage, etc -- but that is used to state things like "2 pills per day for 1 week" than what I think Medication.amount is used for. See https://github.com/synthetichealth/synthea/wiki/Generic-Module-Framework%3A-States#medicationorder
And when that data is available, depending on the export format, it may or may not be exported. For example, in MedicationOrder or MedicationRequest resources.

@jawalonoski So there is no way to get medication taken data using Synthea ? not even if you modify a bit yourself?

@jawalonoski So there is no way to get medication taken data using Synthea ?

Medications can be optionally prescribed or administered. When it is administered, it can be considered "taken."
Otherwise, the patients do not self report if the medication was "taken."
That being said, most (but not all) modules simplistically assume that patients adhere to their prescriptions (i.e., that they do actually take their medications).

not even if you modify a bit yourself?

Of course, it is open-source. You can do nearly anything with the code. You can add "medications taken" in simple but coarse manner in a number of different ways, e.g. using an Observation state or modifying the export of medications. You can also do this in a much more sophisticated manner, but actually representing adherence across medications and the impact on multiple comorbidities. But Synthea does not currently do that today, so it would be a significant change.

If i use the Medicine Administered in the Module builder.
Will Synthea then generate a MedicationAdministation log ?
like this: https://www.hl7.org/fhir/medicationadministration.html

If i use the Medicine Administered in the Module builder.
Will Synthea then generate a MedicationAdministation log ?
like this: https://www.hl7.org/fhir/medicationadministration.html

Yes, exactly.


Can we use same backend.json in 2 kubernetes cluster

Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi @bhuwan1009,
You can use the same Trident backend configuration in two Kubernetes clusters. This will basically be a shared storage pool where each Trident instance is only aware of the volumes that it provisions.

Hi @gnarl
When i am trying to create backend from the same json file on new cluster, i am getting below error
./tridentctl -n trident create backend -f backend.json -d
Operating mode = tunnel, Trident pod = trident-csi-bb64c6cb4-7m9fh, Namespace = trident, CLI = oc
Invoking tunneled command: oc exec trident-csi-bb64c6cb4-7m9fh -n trident -c trident-main -- tridentctl --debug create backend --base64 eyJkYXRhTElGIjoiMTAuNS43NS4xMTUiLCJtYW5hZ2VtZW50TElGIjoiMTAuMjQxLjMuMTMiLCJwYXNzd29yZCI6IkFpcnRlbEAxMjMiLCJzdG9yYWdlRHJpdmVyTmFtZSI6Im9udGFwLW5hcy1lY29ub215Iiwic3ZtIjoiVFJJREVOVF9TVk0iLCJ1c2VybmFtZSI6InRyaWRlbnRfdXNlciIsInZlcnNpb24iOjF9
Operating mode = direct, Server = <IP_ADDRESS>:8000, Autosuport server = <IP_ADDRESS>:8003
Trident URL: http://<IP_ADDRESS>:8000/trident/v1
Request Method: POST
Request URL: http://<IP_ADDRESS>:8000/trident/v1/backend
Request headers: map[Content-Type:[application/json]]
Request body: {"dataLIF":"<IP_ADDRESS>","managementLIF":"<IP_ADDRESS>","password":"XXXXXX","storageDriverName":"ontap-nas-economy","svm":"TRIDENT_SVM","username":"trident_user","version":1}
................................................................................
Error: Post "http://<IP_ADDRESS>:8000/trident/v1/backend": EOF
command terminated with exit code 1
In the logs :-
time="2021-08-06T14:01:22Z" level=warning msg="Cannot terminate an uninitialized backend." backend=ontapnaseco_<IP_ADDRESS> backendUUID=c0c57f1d-23de-4994-b776-90dff9431068 driver=ontap-nas-economy requestID=892ad3e9-0c79-4cd3-b5a4-35ccb99a46b3 requestSource=REST state=failed
time="2021-08-06T14:01:22Z" level=error msg="problem initializing storage driver 'ontap-nas-economy': error initializing ontap-nas-economy driver: could not create Data ONTAP API client: error reading SVM details: Post "https://<IP_ADDRESS>/servlets/netapp.servlets.admin.XMLrequest_filer\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" backend=ontapnaseco_<IP_ADDRESS> handler=AddBackend requestID=892ad3e9-0c79-4cd3-b5a4-35ccb99a46b3 requestSource=REST
Do i need to create backend again if i have to use same on the other trident instance.

@bhuwan1009,
From the error message it doesn't look like the ONTAP management LIF is reachable from that K8S cluster.

@gnarl is right. You should confirm if the management LIF (<IP_ADDRESS>) is reachable from your Kubernetes cluster

@gnarl @balaramesh
I am able to reach it . Please find output of telnet and curl
telnet <IP_ADDRESS> 443
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.
Escape character is '^]'.
^]
telnet> q
Connection closed.
[root@n4vl-pa-ansible01 trident-installer]# curl -kv https://<IP_ADDRESS>

About to connect() to <IP_ADDRESS> port 443 (#0)
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 443 (#0)
Initializing NSS with certpath: sql:/etc/pki/nssdb
skipping SSL peer certificate verification
SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Server certificate:

  subject: C=US,CN=N2DC-NTP03-CLU01

  start date: Nov 23 13:46:10 2020 GMT

  expire date: Nov 23 13:46:10 2021 GMT

  common name: N2DC-NTP03-CLU01

  issuer: C=US,CN=N2DC-NTP03-CLU01

GET / HTTP/1.1
User-Agent: curl/7.29.0
Host: <IP_ADDRESS>
Accept: /

< HTTP/1.1 303 See Other
< Date: Fri, 06 Aug 2021 15:44:45 GMT
< Server: Apache
< X-Content-Type-Options: nosniff
< Cache-Control: no-cache, no-store, must-revalidate
< Pragma: no-cache
< Expires: 0
< X-Frame-Options: SAMEORIGIN
< Location: https://<IP_ADDRESS>/sysmgr/v4/
< Content-Length: 237
< Content-Type: text/html; charset=iso-8859-1
<

303 See Other

See Other
The answer to your request is located here.

* Connection #0 to host <IP_ADDRESS> left intact

Was this from a node on the Kubernetes cluster or a bastion host?

Hi @bhuwan1009,
Were you able to resolve your connectivity issue?

Closing this issue as we haven't received a response from @bhuwan1009. If you are still experiencing this issue it is suggested that you contact NetApp support.


"Email" - Type or namespace expected

In CreateUserViewModel
ln.20:
[Required, Email]
Changed to (only in my copy):
[Required, DataType(DataType.EmailAddress)]
Not sure this is what was supposed to be there?

The "Email" data annotation is defined in the DataAnnotationsExtensions nuget package (https://github.com/srkirkland/DataAnnotationsExtensions). Make sure you have that and the DataAnnotationsExtensions.MVC3 packages installed.


IconPack in UWP Causes Designer to Fail

Utilizing the IconPack Nuget package, VS2015 designer crashes and fails to restart.  It is worth noting that the application builds fine - designer is the only item that is having issues.  The error output I am given is as follows:
System.Runtime.Remoting.RemotingException
[13836] Designer process terminated unexpectedly!

The actual issue does not arise until I actually use an icon:
<IconPack:PackIconMaterial Kind="Settings" />

Simply placing the using statement raises no issues.

@amkuchta I figured out this happens if you select x64 for the Platform. I got no problems with x86 or Any CPU. Tested with this sample.

@amkuchta And this is maybe the explanation http://stackoverflow.com/a/5379908/920384

Apparently my comment never took... using x86 solved my issue, I don't know if you want to close this issue or not, given that this is only a work-around, but it appears that the issue is within VS and not IconPacks itself.

Also (once again), thank you.  Your work is vastly helpful, impressive, and greatly appreciated!


[Lecture10][0611] Small error in lecture slide

There is a small error in lecture#10 slide p29. I think the sigmoid function formula should be e^(-x).
Thank you.

@HJH0303 Wow, thank you for the correction (what a mistake..),
I will revise the part, then.


issue related to back button issue#141361

now the AppBar back button focus/hover circle do not fill up whole height
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

This doesn't seem like a PR that we would land, even if it had tests and an issue that explained the problem that the PR was supposed to fix. If you want to pursue this further I'd suggest starting out by filing an issue.
I'm going to close the PR for now. Feel free to reopen it once there's an issue to be resolved.


when run Artisan::call()  cause crash

the last form commit，route is ”install/databse“ ,the page show 500 error，contents is following：
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at<EMAIL_ADDRESS>to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Apache error log:
[Thu Dec 12 17:31:47.146545 2019] [core:error] [pid 27352:tid 2100] [client <IP_ADDRESS>:49172] End of script output before headers: index.php

The error position in file:
//vendor\rachidlaasri\laravel-installer\src\Helpers\DatabaseManager.php
//line 37
  Artisan::call('migrate', ["--force"=> true], $outputLog);

The Laravelinstaller's version is "4.0";
My php version is "7.1.13";
environment : "Apache on phpstudy" ;
How to solve this problem？

I guess the computer has experienced an out of memory error ，all success before，Ignore the issue！


A decorator-based API for subscribe and register

This is a decorator-based API for components to subscribe and register functions. This lets you do things like this:
component = Component(...)

@component.subscribe(
    u"com.example.",
    options=SubscribeOptions(match=u"prefix", details_arg='details'),
)
def an_event(details=None):
    print("topic '{}'".format(details.topic))

However, this doesn't have a good story for "how do I get crossbar to run it".
One option could be config-parsing so that you can describe the topic + options.
Another option would be to define an object component in crossbar that is given a module to load and it looks for a "component" object which it uses to connect to crossbar. There would be a question here about what to do about the transports/connection information -- override whatever the component has with transports defined in the crossbar config, or accept what it has from code? Or it could just be an error if there's redundant transports.

Codecov Report

Merging #798 into master will decrease coverage by 0.05%.
The diff coverage is 20%.

@@            Coverage Diff             @@
##           master     #798      +/-   ##
==========================================
- Coverage   60.39%   60.33%   -0.06%
==========================================
  Files          71       71
  Lines       11851    11865      +14
  Branches     1860     1860
==========================================
+ Hits         7157     7159       +2
- Misses       4073     4085      +12
  Partials      621      621

Impacted Files
Coverage Δ

autobahn/wamp/component.py
46.04% <20%> (-1.69%)
:arrow_down:

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 12e0b14...49021bf. Read the comment docs.

The "config parsing" thing might look like some configuration in Crossbar like this (e.g. inside a "component"):
subscriptions: [
    {
        "topic": "com.example.",
        "handler": "module.sub.my_function",
        "options": {
            "match": "prefix"
        }
    }
]

The thing I don't like about that, though, is there's some redundancy with what the code says (i.e. you'd be spelling out "options", "topic" etc in the code as well).
A similar option might be to leverage the decorators better and have them 'mark' the functions with the options etc directly, so that the above config would become just the essential information:
subscriptions: [
    {
        "handler": "module.sub.my_function"
    }
]

(or maybe it's just a list of strings that are function-names). Then the crossbar code would introspect the functions (that were marked with the decorators) to pull out topic, options, etc.

The "component" suggestion in the original comment would look kind-of like .tac files from Twisted. It might work like this:
"components": [
    {
        "type": "object",
        "module": "module.sub"
]

Then, crossbar would load module.sub and look for a variable in it called component that must be an Autobahn Component. The only question here would be: can you override connection information from crossbar's configuration? (i.e. when the component was created "in code" it probably had transports= set to something useful). This is also a bit on the "magic" side, although I guess the "name of the variable" could be an option in the config above too (i.e. default "component").

I'm not sure about the component config in CB providing actual app business stuff (registrations, subscriptions, ..) - but this independent of having decorators for regs/subs on components at the code level, right? Or do you think the former should already be given some thoughts at this stage?
Another thing that boggles me with decorators for regs/subs: what about errors? (not authorized, shared reg and previous callee gave different invocation policy, etc)
And what about progressive invocations? Does that fit into the picture?

As for "what about crossbar?" This comes down to "what if I want to move this code to a crossbar-launched thing". So yes, mostly orthogonal, because worst-case you could just run the component as a guest and it'll "just work".
What about errors? You will see the errors as logged by Autobahn/Crossbar as if they happened in any other session.on("join", ..) listener (because they do). So this would be exactly equivalent to making a bunch of .register(..) calls in an on-join listener (in fact, that's literally what the decorators do).
Progressive invocations: yes those should work fine too. On the register side, you just have to pass the "details_arg" thing, which is fine via the decorators; it's the "call" side that passes on_progress and there's no "call" decorator (and I don't think making one makes sense). In any case, I will cook up an example to make sure.

Okay, yeah progressive calls work fine; see example in PR.


Integrating Heart-Rate synchrony measures / control interfaces

Hi all,
Really cool project here, I would be interested in using goofi-pipe to run experiments (and art projects) that utilize heart-synchronization betwen 2 or more participants. I am interested in using various techniques for measuring interpersonal synchronization, e.g. sliding window correlations, or more interestingly frequency-domain specific wavelet coherence analyses (see: https://www.heartmath.org/assets/uploads/2015/01/achieving-collective-coherence.pdf; https://journals.sagepub.com/doi/full/10.1177/1088868316628405#bibr15-1088868316628405).
I am sure there are various different means of calculating synchrony, and would be happy to contribute with ideas regarding their implementation. Is anyone on the team interested in developing this further? Are there any means of utilizing  ECG via the LSL stream and calculating some basic synchrony measures in real-time via the current goofi-pipe?

We have a couple of connectivity measures that come more from M/EEG analysis, I'm not sure if they are helpful in your case. Otherwise it's possible to compute per-subject metrics (e.g. HRV) and then correlate them across subjects using the Buffer and Correlation nodes.
We don't have a lot of ECG-related nodes yet but I know @sangfrois was working on some, maybe he has some ideas as well.
Regarding using ECG via LSL it is hard to say what the problem is without further information. So far we tried the LSLClient node with several EEG devices, which usually works without problems. Please describe your problem a bit further, e.g. does goofi-pipe detect the LSL stream of your device (the devices are printed in the terminal by the LSLClient node)? What happens when you set the host and stream name of your device in the LSLClient node, i.e. is there an error?

Now I really have to push this cardiorespiratory variability node. Sorry, I was having issues with reading serial stream due to my not being able access the Arduino port. It has delayed my process a bit. I can create a PR with the untested node though.

We now have a Cardio-respiratory Variability node thanks to @sangfrois !
https://github.com/PhilippThoelke/goofi-pipe/blob/main/src/goofi/nodes/analysis/cardiorespiratoryvariability.py
To compute correlations between two (or more) participants you can pass any metric into a buffer and then compute correlation via the Connectivity node, which implements several different measures of synchrony. This might require using a Join node after the buffers of multiple participants to put all of the data into one array.


NixOS install in VMWare VM print_req_error: I/O error

To Reproduce

have a VMWare VM
install NixOS in the VM using the MBR instructions

Expected behavior
NixOS to boot.
Screenshots

Why is your NixOS installation attempting to read from the CDROM/DVDROM (sr0) during boot?

@emmanuelrosa I did not create NixOS or Linux so I have no idea. Good question though!

After a reboot the system worked without any issues.


Multiple skate versions are incompatible when idom.attributes mutation differs

There's a fundamental problem in living up to

It works with multiple versions of itself on the page.

due to how skate hooks into incremental-dom. incremental-dom exposes an attributes object which can be used to hook into the lifecycle of DOM updates, and skate leverages this to do some internal state tracking.
Unfortunately skate currently assumes that it can safely mutate attributes.___, but it forgot that it'll actually be stepping on other versions of itself.
This happened in practice with v1.0.0-beta12 and v1.2.3, because back in v1.0.0-beta12 we had the code:
// Attributes that are not handled by Incremental DOM.
attributes.key = attributes.skip = attributes.statics = function () {};

but in v1.2.3 we do need attributes.skip so we have:
// Skip handler.
incrementalDom.attributes.skip = function (elem, name, value) {
  if (value) {
    elem[$skip] = true;
  } else {
    delete elem[$skip];
  }
};

Unfortunately for me v1.0.0-beta12 was being executed after v1.2.3 and clobbering the attributes.skip hook.

Isn't this a more fundamental issue with idom? I'm home sick at the moment
but I braided an issue about making multiple idom instances work.
On Thu, 25 Aug 2016, 11:46 Bradley Ayers<EMAIL_ADDRESS>wrote:

There's a fundamental problem in living up to
It works with multiple versions of itself on the page.
due to how skate hooks into incremental-dom. incremental-dom exposes an
attributes object which can be used to hook into the lifecycle of DOM
updates, and skate leverages this to do some internal state tracking.
Unfortunately skate currently assumes that it can safely mutate
attributes.___, but it forgot that it'll actually be stepping on other
versions of itself.
This happened in practice with v1.0.0-beta12 and v1.2.3, because back in
v1.0.0-beta12 we had the code:
// Attributes that are not handled by Incremental DOM.
attributes.key = attributes.skip = attributes.statics = function () {};
but in v1.2.3 we do need attributes.skip so we have:
// Skip handler.
incrementalDom.attributes.skip = function (elem, name, value) {
if (value) {
elem[$skip] = true;
} else {
delete elem[$skip];
}
};
Unfortunately for me v1.0.0-beta12 was being executed after v1.2.3 and
clobbering the attributes.skip hook.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/skatejs/skatejs/issues/745, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIVbF9Goatoe8dE62wEamX7s6oKJ5hPks5qjPQGgaJpZM4JsnhB
.

Raised *
On Thu, 25 Aug 2016, 13:32 Trey Shugart<EMAIL_ADDRESS>wrote:

Isn't this a more fundamental issue with idom? I'm home sick at the moment
but I braided an issue about making multiple idom instances work.
On Thu, 25 Aug 2016, 11:46 Bradley Ayers<EMAIL_ADDRESS>wrote:

There's a fundamental problem in living up to
It works with multiple versions of itself on the page.
due to how skate hooks into incremental-dom. incremental-dom exposes an
attributes object which can be used to hook into the lifecycle of DOM
updates, and skate leverages this to do some internal state tracking.
Unfortunately skate currently assumes that it can safely mutate
attributes.___, but it forgot that it'll actually be stepping on other
versions of itself.
This happened in practice with v1.0.0-beta12 and v1.2.3, because back in
v1.0.0-beta12 we had the code:
// Attributes that are not handled by Incremental DOM.
attributes.key = attributes.skip = attributes.statics = function () {};
but in v1.2.3 we do need attributes.skip so we have:
// Skip handler.
incrementalDom.attributes.skip = function (elem, name, value) {
if (value) {
elem[$skip] = true;
} else {
delete elem[$skip];
}
};
Unfortunately for me v1.0.0-beta12 was being executed after v1.2.3 and
clobbering the attributes.skip hook.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/skatejs/skatejs/issues/745, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIVbF9Goatoe8dE62wEamX7s6oKJ5hPks5qjPQGgaJpZM4JsnhB
.

There's https://github.com/google/incremental-dom/issues/254. I've been biding my time with it as we haven't run into any issues until now and trying to do higher priority stuff. The gist is that iDOM needs to be updated so that attributes (and other overridables) are injected into the call to patch(), patchInner(), or patchOuter().