Fix: anonymous user can delete task

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/37999
PROPOSAL: https://github.com/Expensify/App/issues/37999#issuecomment-1988249717
Tests

Log out if logged in
Go to a public room with task. (https://staging.new.expensify.com/r/2376199970894587
)
Click on the task
Click three-dot menu > Delete task
Delete the task
User will be presented with login modal when attempting to delete task anonymous

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Log out if logged in
Go to a public room with task. (https://staging.new.expensify.com/r/2376199970894587
)
Click on the task
Click three-dot menu > Delete task
Delete the task
User will be presented with login modal when attempting to delete task anonymous

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/161821005/2737ae4b-5615-490e-8723-d99c2a9a54fb

Android: mWeb Chrome

https://github.com/Expensify/App/assets/161821005/7bc20ced-5d4d-41a6-87ae-656da164b314

iOS: Native

https://github.com/Expensify/App/assets/161821005/98ec33fb-b5de-4666-b103-15a931980f97

iOS: mWeb Safari

https://github.com/Expensify/App/assets/161821005/a5cbde17-d863-43b1-ac21-3cae961877d0

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/161821005/44b792c2-ad43-42b6-886a-ce5bfd9f7e6b

MacOS: Desktop

https://github.com/Expensify/App/assets/161821005/edf85f6b-d922-4759-b702-19f3d2795efb

@c3024 PR is ready to review

@c3024 Bump to review once you have a chance

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Hmmm strange, everything seemed fine when I merged, and looking at the checks I don't see anything that failed. Fluke? Unsure. Either way I think this should be fine.


[BUG] Build with "Release6" branch fails

Describe the bug
When I try to build KeyDB with legacy FLASH, with make MALLOC=memkind, it makes the following error.
zmalloc.cpp:246:46: error: macro "realloc" requires 3 arguments, but only 2 given
     newptr = realloc(realptr,size+PREFIX_SIZE);
                                              ^
zmalloc.cpp: In function ‘void* ztryrealloc_usable(void*, size_t, size_t*)’:
zmalloc.cpp:246:12: error: invalid conversion from ‘void* (*)(void*, size_t) throw () {aka void* (*)(void*, long unsigned int) throw ()}’ to ‘void*’ [-fpermissive]
     newptr = realloc(realptr,size+PREFIX_SIZE);

To reproduce
Tested with both ubuntu 16.04 and 18.04. Ran the following commands.
git clone git@github.com:EQ-Alpha/KeyDB.git
cd KeyDB
git checkout -b release6 5169f97
make MALLOC=memkind

Expected behavior
Build success.

Confirmed. Same problem here.

Legacy FLASH is not supported anymore, and seem not compatible with 6.x codebase.
See also https://community.keydb.dev/t/enabling-legacy-flash/109/2

Its more like the whole project is dead, as far as responses to bugreports ect. go.

We apologize for some of the delayed responses, please bear with us. We will be ramping up support for open source bugs in the coming months and are currently working on a big open source release scheduled early Q2

I checked in change d132b27cd which fixes the build breaks with memkind FLASH support.  To be honest this type of FLASH support was a bit of a failed experiment, the kernel doesn't do a good job of choosing which to page and which not to and so you get hit with performance walls once you use too much memory.  We try to help it by differentiating pageable vs non-pageable but the granularity is quite low and it affects every malloc call so it really makes merging new Redis versions difficult.
The criticism of not responding to bugs in a reasonable period is pretty valid.  Most of my time was spent on Pro the last while, and so we're working on open sourcing more of that code as I think we got the balance wrong.  I'm not particularly good at responding to messages, as a result you'll see Ben do more of the initial triage and comments.


Considering to use license?

Hi,
Nice work on your JS local recorder.
Do you consider to add license file (ex. MIT or Apache etc.) and put this under license cover?
Thank you

MIT license now included


Installation package conflict

The conflict is caused by:
    The user requested starlette==0.27.0
    fastapi 0.95.0 depends on starlette<0.27.0 and >=0.26.1

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

https://github.com/tiangolo/fastapi/releases/tag/0.95.2

I think can upgrade fastapi to 0.95.2


escape multi line bash documentation

Makes copy pasting the examples less error-prone.

@all-contributors please add @mcanlas for doc


Azure Data Explorer: iter.Next is deprecated: Use NextRowOrError() instead

Report
Azure Data Explorer code needs to be updated, I have set an exception to the .golangci.yaml in the meantime:
https://github.com/kedacore/keda/blob/92fe72f6a8a5eb7d03e92cc665d3c4f8d3085a5a/.golangci.yml#L78
make golangci
golangci-lint run
pkg/scalers/azure/azure_data_explorer.go:95:14: SA1019: iter.Next is deprecated: Use NextRowOrError() instead for more robust error handling. In a future version, this will be removed, and NextRowOrError will replace it. Next gets the next Row from the query. io.EOF is returned if there are no more entries in the output. This method will fail on errors inline within the rows, even though they could potentially be recovered and more data might be available. Once Next() returns an error, all subsequent calls will return the same error. (staticcheck)
        row, err := iter.Next()
                    ^
pkg/scalers/azure/azure_data_explorer.go:105:11: SA1019: iter.Next is deprecated: Use NextRowOrError() instead for more robust error handling. In a future version, this will be removed, and NextRowOrError will replace it. Next gets the next Row from the query. io.EOF is returned if there are no more entries in the output. This method will fail on errors inline within the rows, even though they could potentially be recovered and more data might be available. Once Next() returns an error, all subsequent calls will return the same error. (staticcheck)
        _, err = iter.Next()

Expected Behavior
golangci pass without an expection
Actual Behavior
iter.Next is deprecated
Steps to Reproduce the Problem

make golangci

Logs from KEDA operator
No response
KEDA Version
No response
Kubernetes Version
No response
Platform
No response
Scaler Details
No response
Anything else?
No response

I think that this PR is needed before to have the updated dependency

Yeah, I will update this one once it is merged. I needed a link to an issue in the PR chicken-egg problem 😄

This needs to be updated once is this issue solved https://github.com/kedacore/keda/blob/92fe72f6a8a5eb7d03e92cc665d3c4f8d3085a5a/.golangci.yml#L78


bling_fire_tokenizer.py: imports fail for Token

Import for the script bling_fire_tokenizer.py fails for the Token object
with Python v. 3.9 and 3.8.
Problem lies with the changed allennlp import for the Token object,
Problem is fixed by adding:
from allennlp.data.tokenizers.token_class import Token
from blingfire import text_to_words

s. also image for diff.
BR

use
pip install allennlp==0.9.0


use @cycle/storage

Not ready to merge yet.

Anyway, sorry for the broken PR earlier @staltz. I'll see to fixing this as soon as possible.

OK @staltz, for some reason my changes to cycle/storage (which was just a refactoring basically, so I don't know if that is really because of my changes) introduced a race condition so that .merge() and .scan() did not provide the desired result. First all the modification-functions came through and then the todoData. I changed it to using .combineLatest() and .map() and it seems to work for me now.
Can you have a look at the change (https://github.com/kahlil/todomvc-cycle/commit/86351eecc94fd362e03ac65bf9564e8eca81edef#diff-2e064487718803adeada2cb9831822c7R109) and let me know if this is OK?

Morning @staltz do you have a plan on how to proceed with this?

Hi, I've been really short of time lately.

I changed it to using .combineLatest() and .map() and it seems to work for me now.

We definitely need to keep it as merge+scan. combineLatest might fix the problem in this specific case, but in general it's proven (in my experience) to be the wrong combinator to manage state in the model.
About going forward, we can either wait until Saturday when I have to time to work on all things Cycle related, or you can try doing the fixes yourself with my support. At first, I think we can try this: maybe combineLatest worked because it buffers the latest value, and merge doesn't. So if sourceTodosData$ is hot, merge won't buffer the value. So what you can do instead is use shareReplay on the sourceTodosData$ before merging+scanning it.

Understood.
I'd really like to fix this myself with your support. Thanks for the input I'll try that out!

Ok shareReplay does not seem to change anything.
On an empty localStorage these are the three data items coming through when we merge the localstorage stream with the modification stream:
function (todosData) {
      todosData.filter = route.replace('/', '').trim();
      todosData.filterFn = filterFn;
      return todosData;
}
// ---
function (todosData) {
      todosData.filter = route.replace('/', '').trim();
      todosData.filterFn = filterFn;
      return todosData;
}
// ---
Object {list: Array[0], filter: ""}

it really should be
Object {list: Array[0], filter: ""}
//---
function (todosData) {
      todosData.filter = route.replace('/', '').trim();
      todosData.filterFn = filterFn;
      return todosData;
    }

Any idea on why?

Honestly I have to work a little more on the understanding of the mechanics you had implemented here in the first place. I am a little stumped with this right now... Gonna dive in :smile:

@staltz OK after poking around the problem to me, does look like a race condition. I made the storage driver somewhat DRYer in the last update which seems to have the effect to make the localStorage come through just a little less quicker. It should be the first data coming through the merged Observables but it is the last. Is there any elegant way to merge them in a way so that the localStorage data is guaranteed to comes through first?

Is there any elegant way to merge them in a way so that the localStorage data is guaranteed to comes through first?

concat operator usually does that.

Cool, I'll try that out.

Am 19.12.2015 um 12:36 schrieb André Staltz<EMAIL_ADDRESS>Is there any elegant way to merge them in a way so that the localStorage data is guaranteed to comes through first?
concat operator usually does that.
—
Reply to this email directly or view it on GitHub.

That fixed it! \o/
I had actually tried concat before but I forgot to do .take(1) on the localStorage$ so it crashed the browser with an endlessly concatenating loop :grinning:
I also was not confident trying other methods since it sounded like you wanted this solved with merge+scan. So thanks for pointing me in the right direction!
This works now and I think it actually describes what is happening a little better, since scan really requires the localStorage data to come first in order to work properly.
You can verify this working by checking out this branch and doing an npm install && npm start.
Thanks for taking out the time to help me!

Does this need to be changed in order to work with Cycle.js 2.0?

Does this need to be changed in order to work with Cycle.js 2.0?

Thanks @kahlil for your patience, you don't need to change much since I already had todomvc for Cycle Nested in a separate branch which I just merged. I've been slow to merge this because I'm flooded with things to do and todomvc is an important example that must be done perfectly. In other cases I merge PRs more easily. Since you said this is now working, I'll attempt to merge manually.

OK, sounds great. I am excited to see this being merged in soon.
No problem by the way, I am well aware of the mountain of work you are faced with because of the new release.

Does this need to be changed in order to work with Cycle.js 2.0?
Thanks @kahlil https://github.com/kahlil for your patience, you don't need to change much since I already had todomvc for Cycle Nested in a separate branch which I just merged. I've been slow to merge this because I'm flooded with things to do and todomvc is an important example that must be done perfectly. In other cases I merge PRs more easily. Since you said this is now working, I'll attempt to merge manually.
—
Reply to this email directly or view it on GitHub https://github.com/cyclejs/todomvc-cycle/pull/19#issuecomment-168500380.

Finally merged! Super thanks!

Yeeeey! \o/ awesome!

On 04 Jan 2016, at 20:35, André Staltz<EMAIL_ADDRESS>wrote:
Finally merged! Super thanks!
—
Reply to this email directly or view it on GitHub.


Try to solve issue 93 progress/range bar starts out at 50% before jum…

We set initial progress value to 0, and we create a temporal progress value (audio.currentTime / audio.duration). After we check if temporal progress is bigger than 0, and we update progress.

Hey @edezacas Does this change any other functionality?

Not, only improve the initial progress value.

Seems legit :+1:


[type:refactor] refactor it ci.

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #5078 (b69cf5e) into master (6d341fd) will decrease coverage by 0.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #5078      +/-   ##
============================================
- Coverage     63.17%   63.01%   -0.16%
+ Complexity     8517     8500      -17
============================================
  Files          1221     1221
  Lines         36367    36353      -14
  Branches       3328     3324       -4
============================================
- Hits          22974    22907      -67
- Misses        11503    11552      +49
- Partials       1890     1894       +4

see 27 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


DIDComm V2 messaging support

Hello, Team
You are doing really great job!
I see that the main direction of project evaluation is related DIDComm messaging of the first version.
Do you have any plans regarding moving to the second version of DIDComm or even to the third one?
For our project, we took the Aries Framework as the basis and implemented our custom protocols with the integration of DIDComm's second version.
In order to integrate DIDComm V2 we had to make several important changes some of which contradict current approaches :

We reworked Message Sender / Message Receiver to support both types of messages DIDComm V1 and DIDComm V2.
We added Key Service - an extra module/layer for keys generation, management, and storing in the collection. Libindy wallet API is used to store keys ( same as for other AFJ collections). We had to do it because the package we used for packing DIDComm V2 messages requires the implementation of methods for receiving the private key parts. Libindy which is currently used for DIDComm V1 does not provide an ability to get it. Proper way here was integration of DIDComm V2 directly into Libindy, but it is more difficult and requires much more work.
We also added DID Service - managing DIDs in a similar manner.
We tried to preserve existing DIDComm V1 protocols working but have not tested them for a while. They may be broken, but there should not be difficult issues.  So DIDComm V1 messaging is still used for old V1 protocols like connection, issuance, and verification. We have not adopted them for DIDComm V2.
Connection: DIDComm V1 protocols (like issuance, verification) depends on the Connection module and record. There is not any connection protocol or object for DIDComm V2. So DIDs are just passed directly into protocol starting functions.
We adopted the Request Mediation protocol for DIDComm V2 (but we broke DIDComm V1). It should be possible to fix.
We adopted the Trust Ping protocol for DIDComm V2.

Taking into account these important points, would you be interested if we contribute our changes to the upstream?  We are asking it in advance because it may take significant time to prepare our changes for the merge request.

Great job! Were you able to run the rust library in react native? Last week in the AFJ call we had a discussion about DIDComm v2 implementation. Your contribution is more than appreciated!.

@rodolfomiranda yes. here is react-native package working on both android and ios.

Yes, awesome work @Artemkaaas! Here are some notes from that meeting last week
And we'd love to have you at the meeting this Thursday (i'm hosting and can put you at the top of the agenda, to discuss)

This is becoming a 'hot topic' within our community, as it took most of last week call and we were willing to continue the discussion 😄. There is a thread in Discord channel as well. Different approaches are under analysis and of course one of them is about using SICPA library.
If i'm not wrong, one of the main concerns about SICPA library was about React Native support, but if it's already there, we are good to go. Other issue is that, as you may have noticed, there was a massive amount of changes since your original fork (including the refactoring being done in 0.3.0-pre), so some interesting integration work should be done there.
BTW the branch containing your development is this one, right? I've seen in one of your latest PR that you've added a summary of changes in both your fork, which is really useful.
Thanks for opening this issue. It's a good way to explore different options and keep track of our thoughts and findings on this area.

@TimoGlastra and @genaris please provide guidance for inclusion of this work in 0.3.0

@TimoGlastra and @genaris please provide guidance for inclusion of this work in 0.3.0

I don't think it is a good idea for this to be included in 0.3.0. We can talk about it during the next next WG Call, but I think it should be when we modularised the framework.

We're really interested in a contribution of DIDComm v2! Not sure if we can make it in 0.3.0, as we want to get it released as soon as possible.
One thing I'm worried about is the conflicts that are between your fork and the current 0.3.0 branch. We've made A LOT of changes since (big architectural changes), and it seems you also made a lot of big architectural changes. Some points mentioned we have a similair solution for, and we need to be careful to not create technical debt.
That said, really looking forward to this. I think my preferred approach would be to start making incremental PRs with not too much changes so we can understand what is being contributed here. If that's not possible I think we should first have some calls and see what the changes and impact are of these PRs.
As @blu3beri mentioned, we should discuss it during the WG call. Are you available next week to join? Not sure what has been discussed this week, if it's already been discussed I'll re-watch the recording

@Artemkaaas we'd love for you to join the newly formed aries-didcomm-v2 channel as I'm trying to collects the threads regarding DIDComm v2 support in ACA-py and AFJ so that we can discuss how to push forward together and accelerate adoption https://discord.com/channels/905194001349627914/1032736844053483621


Dedupe inner spaces

As discussed in discord, convert a series of spaces in the interior of a line to single space. This removes the weird smashing of the space bar necessary with vertical alignment. For example, 2 fields in a go struct:
struct User {
  Email:    string
  Username: string
}

Tests are passing. I need some guidance on how to really test this locally. I tried changing some of the URLs the seeder uses for import as well as changing the postgres column directly but couldn't see confirmation that getFormattedText was actually being called.

Code looks good! I just have to test it.
For this to work on production, we also need to write a backfill command which runs the formatting on all current go challenges.
It should be something like get all go challenges from database, iterate over, run formatter, update.
Which I then need to run once on production.

Doing some testing, looks to be parsing correctly
:heavy_check_mark:

https://github.com/etcd-io/etcd/blob/afade99a7930544a01eb785c681f1431896350b6/client/v3/kv.go/#L137-L143
:heavy_check_mark:

https://github.com/etcd-io/etcd/blob/afade99a7930544a01eb785c681f1431896350b6/etcdctl/ctlv3/command/version_command.go/#L26-L32
:heavy_check_mark:

https://github.com/etcd-io/etcd/blob/afade99a7930544a01eb785c681f1431896350b6/etcdctl/ctlv3/command/auth_command.go/#L40-L46

Doing some regression testing on other languages, looks good as well.


feat: Add provision and deprovision DetailType

Issue # (if applicable)
N/A
Reason for this change
There are no DetailType values for provisioning and deprovisioning.
Stack de/provisioning and tenant on/offboarding can be mutually exclusive and we need to accommodate this.
For example, an application stack/cell may be de/provisioned as part of a scaling or migration activity without tenant on/offboarding.
Description of changes
Added PROVISION_REQUEST and DEPROVISION_REQUEST to DetailType and updated EventManager accordingly.
Description of how you validated changes
Normal testing of stack deployment. No changes to tests were required.
Checklist

[ x ] My code adheres to the CONTRIBUTING GUIDE
[ x ] I have updated the relevant documentation (if applicable).

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

I would also raise the topic of standardising the verb-age used in DetailType. Some use the infinitive, ie. PROVISION_, and others use the '-ing' form, ie. ONBOARDING_.

I would also raise the topic of standardising the verb-age used in DetailType. Some use the infinitive, ie. PROVISION__, and others use the '-ing' form, ie. ONBOARDING__.

+1 to this. This will also be a breaking change, but I think it's important.


feat: bitcoin-s oracle implementation

Add a BitcoinSOracle struct that implements DdkOracle. Maybe call it KrystalBull? (RIP) and add it as a feature flag.
Include a build to run locally and apart of the just deps script

https://hub.docker.com/r/bitcoinscala/bitcoin-s-oracle-server/tags?page=1&ordering=last_updated

https://bitcoin-s.org/docs/oracle/build-oracle-server


Logging when setProperties failed

Good afternoon,
My connector failed when the short description was longer than 2500 characters.
With a try/catch I tried to log which properties gave the error. But the debugger doesn't enter the catch. What can I do to catch the detailed error message?
const logger = createLogger();
const maxLengthSD = 2500;

export function addCase(datum: CaseDetailResponse, result: services.IResult): records.IResultEntityRecord<typeof FraudCase> {
  const uniqueId = datum.id;
  const entity = result.addEntity(FraudCase, uniqueId);

  try {
    entity.setProperties({
      'Case Number': datum.pt_casenumber,
      'Short Description': datum.pt_shortdescription.length > maxLengthSD ? datum.pt_shortdescription.slice(0, maxLengthSD) : datum.pt_shortdescription,
      'Other Information': datum.pt_otherinformation != null ? datum.pt_otherinformation : "",
    });
  } catch (error) {
    logger.error(`Error setting properties addCase with ID ${datum.id}:`, error);
  }

  entity.setSourceReference(sourceReference);

  return entity;
};

Hi Colvin,
With failed I mean I got this error in ANB and I can't find logs which say that I try to add too much characters to the field 'Short Description'.
I changed the max length already to 2500, but the response has >2500 characters.

I understand. The issue is that the Gateway server initiates the request to the connector, so it's validating the connector's response, so it isn't possible for it to send the result of validation to the connector.
Getting all the logs into one place is something you would need to arrange externally, e.g. using something like Logstash

I understand. Is the validation done with the Gateway schema or with the connector schema?
Would it be possible to add a new validation function in the Gateway which can be called before returning the case entity (in the addCase function)?

Is the validation done with the Gateway schema or with the connector schema?

If the connector has a schema with that entity type then that's what will be used by default for the validation.

Would it be possible to add a new validation function in the Gateway which can be called before returning the case entity (in the addCase function)?

I'm afraid that doesn't fit with the flow of the interactions between the Gateway and Connector. The interaction is along the lines below, where the calls to addCase are all happening within the Connector itself. It would require a lot of communication between the Gateway and Connector.
sequenceDiagram
    Client->>Gateway: /acquire {query conditions+seeds}
    Gateway->>Connector: /validate {query conditions+seeds}
    Connector-->>Gateway: {validation response}
    Gateway->>Connector: /query {query conditions+seeds}
    Connector->>Connector: addCase[s]
    Connector-->>Gateway: {query response}
    Gateway->>Gateway: Process and store results
    Gateway-->>Client: Results

Though I guess what you're really asking is whether the Connector SDK could provide some of the validation that the Gateway provides for more immediate feedback and unit testing? Though such validation would only be a subset of what the Gateway does, because the Connector wouldn't have all the context of the system.
Alternatively, we could look at providing a configuration option that tells the Gateway to truncate the data rather than rejecting it.
I suggest you raise an RFE if you want to take this further.

Thanks a lot Colvin for the clear overview!
I'll raise an RFE to add a validation function (subset of the Gateway one) in the Connector SDK.


[RFC] Improving UI editor

What's the problem? 🤔
Resizing/positioning elements in the Toolpad canvas is still quite restricted and, in some cases, unintuitive. Some of the current problems are:

It’s not always intuitive or possible to place an element exactly where the user wants it.
Creating horizontal space between elements feels a bit clunky.
It’s impossible to create vertical space.
Only some elements are vertically resizable, which might be hard to guess.
Elements with variable width are not resizable by dragging from their edges, as a user might expect.

What are the requirements? ❓
The general requirements for a good UI building system should be to allow users to build all or most UIs that they want, and to be able to do it as intuitively and with as little friction as possible.
There can be many ways to reach these requirements, and the problems listed with our current UI building system get in the way of these goals.
What are our options? 💡
So far the 2 paradigms for UI building we seem to have found in other tools are:

Absolute position (e.g.: Retool, Appsmith)

Every element can be dragged and resized freely in the canvas.
Some pros:

More freedom to create the UI the user intends to
Intuitive, as the lack of grid restrictions allow for a consistent and predictable drag-and-drop / resizing experience of every element
Similar to design tools such as Figma or Photoshop
Most tools are using it, so there’s less risk in following the same approach as them

Some cons:

The lack of structure or guidance might result in confusing, disorganized layouts
Due to it being a quite generic approach, it might not always translate well to designing responsive web pages

Grid (rows and columns) (e.g.: Makeswift)

Elements are placed inside rows and columns, in a grid-like layout.
Some pros:

Follows traditional web design principles, which is the way that many web design systems, such as Boostrap, work. One could argue that this results in better-designed app layouts, as it is a good and commonly-used abstraction for web pages.
The familiarity that many UI developers have with this type of system could be a factor that makes it easier for them to understand the grid system and feel efficient using it
Makes it simple/quick to take common actions such as placing two elements in a visual group, or aligning them
If well-implemented, could be an upside of Toolpad compared to most tools

Some cons:

Does not allow for as much freedom as an “absolute position” approach
Some drag & drop or resizing behavior might not be as intuitive as in an “absolute position” approach, mostly due to the restrictions imposed by the rows and columns

Besides these 2 paradigms, many details can be implemented differently, even when mostly adopting a certain paradigm.
Our current system follows a grid-like approach, and even while maintaining that approach, smaller changes could already help solve some of the problems listed initially in this RFC, such as:

Adding a “spacer” component consisting of a container with no element inside, which can be used and resized to create space between elements.

So a paradigm shift is not necessarily needed, we just need to find good solutions to each problem.
There can also be hybrid approaches that try to combine the strengths of both the paradigms listed, as the one in this proposal.
Proposed solution 🟢
This proposal is for a hybrid approach that tries to combine the freedom of absolute positioning with the structure of a grid approach, combining the “pros” from both paradigms, and reducing or eliminating the “cons”.
Just like right now, every element in Toolpad would consist of the element itself, and a rectangular container around it. This has some similarities to the CSS box model, which might make it easier for developers to understand it.

Containers:

would be completely resizable horizontally, vertically and diagonally by dragging their edges or corners. This would be the primary way to create space around an element. Currently, containers are only resizable horizontally, except for Data Grid components. It would not be possible to resize a container to be smaller than the element inside it.
The container boundaries could be highlighted while hovering the mouse over them, to indicate that they are draggable from that cursor position.
During dragging, arrows with numbers could be shown measuring the distance from the element edges to the container edge(s) being dragged. These distances could follow discrete increments. This would allow the user to more easily control the margins around the element.

Elements:

some components would be resizable by dragging some of their edges, depending on the component. Images, for example, would be resizable in all directions, but buttons or text inputs would only be resizable horizontally. Resizing outside the limits of the element container could force the container to expand.
Additionally, all elements would be draggable from the inside in order to change their absolute position, just like in most low-code editors following the “absolute position” approach, but they could only be moved inside the limits of their container, in discrete increments.
Perhaps the element should snap to the center of the container when dragging near it, to make it easier to center it inside its container. We could also just have some options to automatically align the element as we do right now, or even support different “modes” of positioning an element inside its container(e.g.: absolute position or auto-align)
The element boundaries could be highlighted while hovering the mouse over them, to indicate that they are draggable from that cursor position.
There could eventually be a modifier key to switch between resizing the container or the element while hovering over their edges, which would be helpful when their edges overlap.

Resources and benchmarks 🔗
No response

Will put this in the Shaping DB instead. Sorry for the confusion.


Packaging requests: promql-cli

Project description
Command-line tool to query a Prometheus server with PromQL and visualize the output
Metadata

homepage URL: https://github.com/nalbury/promql-cli
source URL: https://github.com/nalbury/promql-cli
license: asl20
platforms: linux, darwin

I have packaged the application in the pull request https://github.com/NixOS/nixpkgs/pull/191041.


Modals don't open if Remote Debugger is active

The modals work great until I turn on Remote JS Debugging in the android emulator. When it is active the modals "show" but they are not visible. I have redux form in a modal and I can see it is creating the forms when I click show, but the modal doesn't actually pop up. I can even drag down on the screen and it closes the invisible modal.
Any ideas what this could be?

I noticed it does actually open with the debugger, its just delayed by a minute or two


onAppear not triggered unless whole component is in view

The title says it all, it would be nice (even if an optional parameter) if we could check if an element is even a little on the screen for onAppear

It's what I expect. But maybe onAppearCompletely for it :D

Maybe put it in the past? onAppear is first appear and didAppear means it was fully there?


Create SnakeGame.htm

For Inserting or for adding link to this page so as to play traditional Snake Game for making little bit  more happy and fun resume

🐍


[Bug] project list modules bug fixed

[Bug] project list modules bug fixed
What changes were proposed in this pull request
Issue Number: close #xxx

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): no

cc @MonsterChenzhuo PTAL, thanks

LGTM


Update xProcess resource to fix PSSA and style Issues

Hello everyone,
Another PR to fix #132  PSSA and style issues. Please review at your earliest convenience.
Thanks very much,
Daniel

Script Analyzer:

Before

After

Reviewed 1 of 2 files at r1.
Review status: 0 of 2 files reviewed at latest revision, 13 unresolved discussions.

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 140 [r1] (raw file):

If this the
If this is the

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 224 [r1] (raw file):

If this the
If this is the

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 296 [r1] (raw file):

    if ($null -ne $PsDscContext.RunAsUser)
    {
        $params = @{

$params should have a more descriptive name. (ex: $exceptionParams, $invalidArgParams, $newInvalidArgumentExceptionParams)

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 320 [r1] (raw file):

    if ($Ensure -eq 'Absent')
    {
        $params = @{

$params should have a more descriptive name. (ex: $assertHashtableParams, $assertArgsParams)

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 373 [r1] (raw file):

            if (-not [String]::IsNullOrEmpty($PSBoundParameters[$shouldBeRootedPathArgument]))
            {
                $params = @{

$params needs a more descriptive name

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 387 [r1] (raw file):

            if (-not [String]::IsNullOrEmpty($PSBoundParameters[$shouldExistPathArgument]))
            {
                $params = @{

$params needs a more descriptive name

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 412 [r1] (raw file):

            {
                $parameterKey = $startProcessOptionalArgumentMap[$startProcessOptionalArgumentName]
                $value = $PSBoundParameters[$parameterKey]

$value needs a more descriptive name (ex: $parameterValue, $startProcessArugmentValue, etc...)

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 440 [r1] (raw file):

                    foreach ($key in @('StandardOutputPath','StandardInputPath','WorkingDirectory'))
                    {
                        $params = {

$params needs a more descriptive name

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 507 [r1] (raw file):

If this the
If this is the

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 521 [r1] (raw file):

Set this property to "Present" to ensure that the process
exists. Otherwise, set it to "Absent".

Set this property to "Present" to return true if the process exisits.
Otherwise, set it to "Absent" to return true if the process does not exist.
Test-TargetResource will not change the state of the process.

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 524 [r1] (raw file):

        exists. Otherwise, set it to "Absent". The default is "Present".

    .PARAMETER StandardOutputPath

Only the Path, Arguments, Credential, and Ensure parameters are actually used for this function.
Can you please change the descriptions of the other parameters accordingly?

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 580 [r1] (raw file):

    if ($null -ne $PsDscContext.RunAsUser)
    {
        $params = @{

$params needs a more descriptive name

DSCResources/MSFT_xProcessResource/MSFT_xProcessResource.psm1, line 748 [r1] (raw file):

            {
                Write-Verbose -Message ($LocalizedData.VerboseInProcessHandle -f $process.Id)
                $params = @{

$params needs a more descriptive name

Comments from Reviewable

@kwirkykat , thanks so much for your thorough review on a Sunday 👍 . I've pushed a new commit to my branch which should fix everything you've highlighted with your comments.

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Create a flattened version of Module1 version 2. [9/7/22] - Kelsey

For Kelsey.
Some of the statistics the Subcomittee would like for Chicago will include some of the Background
Warren's code does not handle module 1, so this will take some time
Back burner for now

@KELSEYDOWLING7 I set up a Warren-style query generator for both versions of M1 and generated those queries. You can find them in the queryGenerators/M1 folder in this repo. I also saved them as flatM1_JP_SA and flatM2_V2_JP_SA in each environment. There is a new corresponding table for each query in the M1 dataset. I did not add any new variables yet, I simply added all of the variables from Zhouliang's original query. Please let me know what you think and if you have any questions/suggestions.


request get ESOCKETTIMEDOUT

env:
node version v7.10.0
uname -a
Linux iZ2zebqg2v1h2g7jmo9endZ 3.10.0-514.6.2.el7.x86_64 #1 SMP Thu Feb 23 03:04:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
request package version: "request": "^2.74.0"

and use express:4.13.4,
I find some log:
{ Error: ESOCKETTIMEDOUT
       at ClientRequest.<anonymous> (/data1/baas_server/baas_x37/node_modules/request/request.js:819:19)
       at Object.onceWrapper (events.js:293:19)
       at emitNone (events.js:86:13)
       at ClientRequest.emit (events.js:188:7)
       at Socket.emitTimeout (_http_client.js:679:10)
       at Object.onceWrapper (events.js:293:19)
       at emitNone (events.js:86:13)
       at Socket.emit (events.js:188:7)
       at Socket._onTimeout (net.js:352:8)
       at ontimeout (timers.js:386:14)
       at tryOnTimeout (timers.js:250:5)
       at Timer.listOnTimeout (timers.js:214:5) code: 'ESOCKETTIMEDOUT', connect: false }

I look the source code,get a lot annotation:
 var setReqTimeout = function() {
      // This timeout sets the amount of time to wait *between* bytes sent
      // from the server once connected.
      //
      // In particular, it's useful for erroring if the server fails to send
      // data halfway through streaming a response.
      self.req.setTimeout(timeout, function () {
        if (self.req) {
          self.abort()
          var e = new Error('ESOCKETTIMEDOUT')
          e.code = 'ESOCKETTIMEDOUT'
          e.connect = false
          self.emit('error', e)
        }
      })
    }

so i want to why the reason and how to fix the bug;
and i don't know how to trigger it,i only find it in log or find request is error;
thanks;

@Fov6363  I have the same problem, have you fixed?

@liujb I update redis conf, set the timeout 0

I have solve the problem, It's not about the request. Nginx's problem.

me too
node ProxyServer.js
start: <IP_ADDRESS>:8080
events.js:182
      throw er; // Unhandled 'error' event
      ^

Error: ESOCKETTIMEDOUT
    at ClientRequest.<anonymous> (/Users/safe/myhktools/node_modules/request/request.js:819:19)
    at Object.onceWrapper (events.js:314:30)
    at emitNone (events.js:105:13)
    at ClientRequest.emit (events.js:207:7)
    at Socket.emitTimeout (_http_client.js:722:34)
    at Object.onceWrapper (events.js:314:30)
    at emitNone (events.js:105:13)
    at Socket.emit (events.js:207:7)
    at Socket._onTimeout (net.js:402:8)
    at ontimeout (timers.js:469:11)

I found this because the server used the proxy

@liujb Hello, you said it is Nginx's problem. How do you fix this problem?

ESOCKETTIMEDOUT is connection timeouts or read timeouts?
200 request/sec, comes up with servial this error.

I found if there are too many async requests, then this exception happens in linux. The workaround I've found is doing this:
setting this options:
agent: false, pool: {maxSockets: 100}

Now the timeout can be lying so you might need to increase it.

The same is here - with single put request to node express -based worker.
No proxy, no streaming, just single request which starts several async promises dealing with DB on worker side.
Suggested agent: false, pool: {maxSockets: 100} in request options didn't help.
Any suggestions from mantainers?

agent: false, pool: {maxSockets: 100}
After I set above options errors reduce from 55 to 8.
And then I set maxSockets:200  . only one error left
I don't know the reason but it does work

It happens to me with request 2.88.0, we occasionally get ESOCKETTIMEDOUT for those requests which were sent out from our app and were processed on receiving part with 200 status code. It looks like a bug somewhere in between request or https modules. Again, request lib throws exception to https request that is processed with 200 http status code? Any ideas are welcome. The problem is easily reproducible on our side (about every 200's request fails) so if you guys interested I can provide more details.
P.S. We did a workaround by implementing retries for failed requests.

Hi,
The documentation says there are "connection timeouts and read timeouts".
Is there a way to set each of them separately?
I'm having a connection timeout sometimes due to an unidentified network issue, and I would like to timeout as fast as I can to be able to retry the request without having to wait for the full timeout that is considering the time to receive the answer.
Thanks.

fix to:
EventEmitter = require('events').EventEmitter
EventEmitter.prototype._maxListeners = n_maxLs;
var _fnNull = function(e){if(program && program.verbose)console.log(e)};
process.on('uncaughtException', _fnNull);
process.on('unhandledRejection', _fnNull);

EventEmitter.defaultMaxListeners = n_maxLs;
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";
process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0;

@MumiaIrrequieta @anosulchik @deluo

fix to:
EventEmitter = require('events').EventEmitter
EventEmitter.prototype._maxListeners = n_maxLs;
var _fnNull = function(e){if(program && program.verbose)console.log(e)};
process.on('uncaughtException', _fnNull);
process.on('unhandledRejection', _fnNull);

EventEmitter.defaultMaxListeners = n_maxLs;
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";
process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0;

@MumiaIrrequieta @anosulchik @deluo

How does this helps setting separate timeouts?
What's the difference between the last couple of lines?

It doesn't look like a fix for ESOCKETTIMEDOUT for me either. @hktalent can you give more info on this please?

Also having this issue. I send out thousands of requests every minute; after about 1 week of running all the connections just immediately start responding with ESOCKETTIMEDOUT.

@SirLancelot-OG did you solve it?

I poll data every minute, looks like there were some APIs sporadically slowing down and causing the total request to run over a minute which stacked up and led to timeouts. Didn't have the proper logging in place.
Have now moved to using websockets for my data!

I get this issue with every request consistently.  I will make a request and the request does pipe and complete.  But if timeout is 10 seconds, I will allows get an 'ESOCKETTIMEDOUT' after 10 seconds of a single request.

Anyone fixed this?

I have solve the problem, It's not about the request. Nginx's problem.

how to solve the Nginx's problem

We are having this and it is failing builds... what is this mysterious mystical nginx fix??

facing this issue recently. anyone can help ?


sudo start broken after latest update (trusty 14.04)

crouton: version 1-20150811114815~master:f6b810fe
release: trusty
architecture: amd64
xmethod: xorg
targets: lxde,audio,xorg,chrome
host: version 7077.123.0 (Official Build) stable-channel lumpy
kernel: Linux localhost 3.4.0 #1 SMP Sat Aug 8 00:58:09 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux
freon: no
Version 44.0.2403.155 (64-bit)
Platform 7077.123.0 (Official Build) stable-channel lumpy
Firmware Google_Lumpy.2.111.0
problem - seems like X-server is crashing. I get the following errors with sudo startlxde
X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-76-generic x86_64 Ubuntu
Current Operating System: Linux localhost 3.4.0 #1 SMP Sat Aug 8 00:58:09 PDT 2015 x86_64
Kernel command line: cros_secure  console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=ba2f7a95-968a-8149-bfc6-224605874bed/PARTNROFF=1 hashtree=PARTUUID=ba2f7a95-968a-8149-bfc6-224605874bed/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=db9083d76973e18ee2d0ce5613378f139b86e68f salt=3b984704cf028e93fff7f0b8162fada45d8c3d51972b07da422d334e08701517" noinitrd vt.global_cursor_default=0 kern_guid=ba2f7a95-968a-8149-bfc6-224605874bed add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic iTCO_vendor_support.vendorsupport=3
Build Date: 12 February 2015  02:49:29PM
xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed Aug 12 20:54:48 2015
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f4dbaba1848]
(EE) 1: /usr/bin/X (0x7f4dba9f8000+0x1ad539) [0x7f4dbaba5539]
(EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4db9af4000+0x10340) [0x7f4db9b04340]
(EE) 3: /usr/bin/X (0x7f4dba9f8000+0xb57a6) [0x7f4dbaaad7a6]
(EE) 4: /usr/bin/X (xf86BusProbe+0x9) [0x7f4dbaa81099]
(EE) 5: /usr/bin/X (InitOutput+0x74d) [0x7f4dbaa8f6fd]
(EE) 6: /usr/bin/X (0x7f4dba9f8000+0x59bab) [0x7f4dbaa51bab]
(EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f4db8534ec5]
(EE) 8: /usr/bin/X (0x7f4dba9f8000+0x451ee) [0x7f4dbaa3d1ee]
(EE)
(EE) Segmentation fault at address 0x0
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.

@mkasick's hack is protected by [ -n freon ], so it shouldn't be the cause here...but just in case, what does sudo enter-chroot grep getuid0 /usr/lib/xorg/modules/drivers/intel_drv.so give you?

returns nothing - is that what it's supposed to return?
thanks for the help.
Tom
On Wed, Aug 12, 2015 at 9:28 PM, David Schneider<EMAIL_ADDRESS>wrote:

@mkasick https://github.com/mkasick's hack is protected by [ -n freon ],
so it shouldn't be the cause here...but just in case, what does sudo
enter-chroot grep getuid0 /usr/lib/xorg/modules/drivers/intel_drv.so give
you?
—
Reply to this email directly or view it on GitHub
https://github.com/dnschneid/crouton/issues/2017#issuecomment-130528716.

restored from an old backup (~ May 5, 2015). Works again. I'm nervous about updating crouton, but now I have a working backup, so it only burns a little time.

Try updating once #2097 is merged.


Comparison of Inheritance in C++ and Java

Proposed title of article
Comparison of Inheritance in C++ and Java
Proposed article introduction
The purpose of inheritance is the same in C++ and Java. Inheritance is used in both languages for reusing code and/or creating an ‘is-a’ relationship.
In this article I will use examples that
demonstrate the differences between Java and C++ that provide support for inheritance. For instance, when creating a class in Java it automatically inherits from the Object class. In C++ however, there is a forest of classes; when we create a class that doesn’t inherit from another, we create a new tree in a forest.
Key takeaways
1.Understanding inheritance and its application in C++ and Java
2..Simple inheritance using Java and C++
3.Level inheritance using  Java and C++
4.Multiple inheritance using Java and C++
5.Class Hierarchy in Java and C++
6.Conclusion
Article quality
I plan to use examples to illustrate differences and similarities of inheritance in C++ and Java.My content will be written in a language that a beginner will understand without loosing the enthusiasm of programming.
References
N/A

Hello @mbuthiajn, we thank you for submitting your topic.
However, after some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentations.
We typically refrain from publishing content that is covered widely on the net or other blogs. As we're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
Please feel free to explore another more in-depth topic.


improving the text message bar

Currently, the "write your message" bar does not look that appealing, it can be improved.

I will like to fix this issue as a part of GSsoc21, please assign it to me.

@Arshanshagarwal Yes ! that's a great idea . You can work on this issue 😄


Does not fall back correctly on windows in mingw?

Anthony@AnthonysDesktop MINGW64 ~/Desktop/git/pre-commit ((7034711...))
$ venv-pre_commit/Scripts/python.exe -c 'import backports.shutil_get_terminal_size as shutil; print(shutil.get_terminal_size())'
terminal_size(columns=0, lines=0)
(venv-pre_commit)
Anthony@AnthonysDesktop MINGW64 ~/Desktop/git/pre-commit ((7034711...))
$ /c/Python35/python.exe -c 'import shutil; print(shutil.get_terminal_size())'
os.terminal_size(columns=80, lines=24)

Seems broken on linux too -- I'll make a separate patch for that:
$ python -c 'import backports.shutil_get_terminal_size as shutil; print(shutil.get_terminal_size())' | cat
terminal_size(columns=0, lines=0)

I've added the patch for linux, and fixed py32 on travis (due to pip being too new)


[DNM] bluetooth: Shell 'init' and 'advertise' commands rework

Init command was calling shell_fprintf from different context
than shell thread which is not allowed. Changed command
implementation to pend on 'ready' callback and print to shell
only in the context of shell thread.
Additionally, reworked advertise command by adding subcommands
for options.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

I was asked by @cvinayak to look at not working bt shell. BT avertising on was returning error and shell uart with interrupts was primary suspect. It turned out that error was cause by number of mandatory arguments for advertise
SHELL_CMD_ARG(advertise, NULL, "help", cmd_advertise, 3, 0),
I also found that handling of advertise command was manual and i modified it to work with subcommands. Imo, it is cleaner and less error prone (autocompletion and typos handled by shell).
bt init change is about calling shell API from shell thread. It was called from callback in work queue and that is not allowed.

Note that bt init is probably not the only case of shell api misuse and ideally all commands that uses some callbacks shall be reworked in the same fashion.

Codecov Report

Merging #11604 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11604      +/-   ##
==========================================
+ Coverage   48.13%   48.22%   +0.08%
==========================================
  Files         279      279
  Lines       43268    43281      +13
  Branches    10354    10355       +1
==========================================
+ Hits        20827    20872      +45
+ Misses      18298    18270      -28
+ Partials     4143     4139       -4

Impacted Files
Coverage Δ

include/logging/log_core.h
100% <0%> (ø)
:arrow_up:

include/logging/log_msg.h
90.9% <0%> (+1.81%)
:arrow_up:

misc/printk.c
84.93% <0%> (+3.12%)
:arrow_up:

subsys/logging/log_core.c
75.53% <0%> (+4.68%)
:arrow_up:

subsys/logging/log_output.c
72.33% <0%> (+8.73%)
:arrow_up:

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 19c598f...668afec. Read the comment docs.

Why not just remove the bt_ready callback and call bt_enable in a blocking fashion, i.e. pass NULL as the callback? That way everything happens in the same context.

@cvinayak @Vudentz @jhedberg note that i've changed device_found to use printk for printing devices and added CONFIG_LOG_PRINTK=y to project configuration. I would see 'printk' as temporary solution as i  would recommend to modify this command so that scanning establishes database of found devices and addtional command (e.g. scan list) lists found devices. Additionally, this database can be used to autocomplete bt connect command with the address.
In nrf5 sdk we have ble interactive app which do more or less the same and we took that approach there.
CONFIG_LOG_PRINTK must be enabled because now shell is using uart with interrupts and standard printk is using polling and they compete for uart so sooner or later that crashes. By enabling this feature printk goes through log and shell.

@jhedberg : you can print messages on a shell from different context, the only limitation is that you cannot use shell_fprintf function for that. This function according to the docummentation cannot be used outside of command context because it can lead to undefined behaviour. For such cases shell and logger architecture allows to use either printk or logger. Next shell will synchronize messages for correct text display on a screen.

@jhe there are two things: shell output and log output. Logs can be used from any context (including printk). Only shell output is limited to command context. If we enable shell output from handler then there is a risk that at the same time another command is typed and output of two commands will collide.
Maybe we can look into following scheme: allow printing from other contexts but provide function for indicating in the command to stay in given context, add ctrl+c that would terminate given command.

sorry for that. Put DNM label. I'm working towards enabling shell_fprintf from other contexts.

@nordic-krch for the record, my issue looks like a stack overflow. I increase the shell and main stack sizes and the issue went away.

After enabling kernel stack info and the kernel shell module I was able to get the following:
***** Booting Zephyr OS zephyr-v1.13.0-2305-g0a18d54dc1 *****
Type "help" for supported commandsBefore any Bluetooth commands you must `bt init` to initialize the stack.
uart:~$ bt init
Initialized.
ecc stack (real size 2016):     unused 1096     usage 920 / 2016 (45 %)
uart:~$ kernel stacks
0x2000354C NA         (real size 4024): unused 3784     usage 240 / 4024 (5 %)
0x200035EC NA         (real size 440):  unused 296      usage 144 / 440 (32 %)
0x200006D8 NA         (real size 1976): unused 1096     usage 880 / 1976 (44 %)
0x20000804 NA         (real size 952):  unused 624      usage 328 / 952 (34 %)
0x20003704 sysworkq   (real size 1976): unused 392      usage 1584 / 1976 (80 %)
0x200004D8 shell_uart (real size 4056): unused 1992     usage 2064 / 4056 (50 %)
0x20003454 logging    (real size 952):  unused 768      usage 184 / 952 (19 %)
0x200032F8 idle       (real size 280):  unused 224      usage 56 / 280 (20 %)
0x20003398 main       (real size 2008): unused 1672     usage 336 / 2008 (16 %)

So looks like the default 2048 for the shell isn't enough. (in my case I increased it to 4k)

And if someone is curious the additions I made to tests/bluetooth/prj.conf are as follows:
CONFIG_SHELL_STACK_SIZE=4096
CONFIG_MAIN_STACK_SIZE=2048
CONFIG_KERNEL_SHELL=y
CONFIG_INIT_STACKS=y
CONFIG_THREAD_MONITOR=y
CONFIG_THREAD_STACK_INFO=y
CONFIG_THREAD_NAME=y

Any estimate when you think this PR will be in a mergable shape? Currently the Bluetooth shell is pretty broken, and this PR would seem to fix at least the issues I've seen with it.

@jhedberg i should have something tomorrow.

@jhedberg

So looks like the default 2048 for the shell isn't enough.

I think it may be related to blocking bt init since probably shell thread stack will be used for that. I will try to fix that by extending #11897 allowing terminating command through the API and not only through CTRL+C. By adding that we can still use bt_ready callback but exit shell foreground from there.

It's been rebased on #11897

@nordic-krch

So looks like the default 2048 for the shell isn't enough.

I think it may be related to blocking bt init since probably shell thread stack will be used for that. I will try to fix that by extending #11897 allowing terminating command through the API and not only through CTRL+C. By adding that we can still use bt_ready callback but exit shell foreground from there.

I also think it's related to the blocking bt_init, but not directly: you're now calling settings_load() in the same context as bt_init(), and I think it's the settings_load() that's increasing stack usage significantly. This might change once #9521 is merged since that should reduce the stack usage.
Anyway, I'm fine with moving back to a callback-based bt_init as well.

bt init works again with callback. bt scan works fine. I think there are still many commands to check since many are using callback. I have not enough bluetooth expertise to fix that. For example I've tried bt connect with wrong address, expecting to get into connected callback with err code but i'm never getting there. Not sure if that is correct behavior or not.

I've tried bt connect with wrong address, expecting to get into connected callback with err code but i'm never getting there. Not sure if that is correct behavior or not.

@nordic-krch if you use bt_conn_create_le() on a device that's not around then the stack will keep scanning for the device indefinitely until you call bt_conn_disconnect(). What you might be able to get a connection error with is through directed advertising, i.e. the "directed-adv" command, since that should have a timeout associated with it.
It's still unclear to me what the value of the command_enter/exit API is, since it's not possible to accurately map these to shell commands and callback functions for Bluetooth. E.g. a disconnected callback can happen because the disconnect shell command was issued, but it could also happen because the remote device went out of range or initiated disconnection from its side. Is it ok for the enter/exit calls not to be balanced?

@jhedberg

E.g. a disconnected callback can happen because the disconnect shell command was issued, but it could also happen because the remote device went out of range or initiated disconnection from its side.

I was also thinking about this case. Actually, 'unexpected' disconnect callback should actually use log and not shell. With current philosophy output on shell appears as the response to triggered command. With that approach, asynchronous output is considered a log message. That's the current state. It seems reasonable as if you allow asynchronous output being printed to shell, it starts to duplicate logger functionality.

@nordic-krch using log instead of shell for callbacks that don't explicitly and unambiguously map to a shell command sounds fine to me. How does that match what you currently have in this PR? Do you still need to do some updates to it?

Do you still need to do some updates to it?

Yes. Currently, asynchronous disconnect will not be printed since it will use shell. So we need to detect in that callback if we are in the command or not. One way would be to set shell_ctx on command handler (not only in init) and unset it in the callback. That would have additional benefit that commands could be called from multiple shells as now it is limited to the shell that called bt init.
@jhedberg @Vudentz what do you think about that approach?

@nordic-krch yes, that sounds like a good approach.

PR #11897 updated this documentation, so should the .rst files changes here be removed?


Link to HDD image for the 0.1.1 release appears to download 0.1.0

The download link in GitHub for the HDD image in the 0.1.1 release (https://github.com/dracc/NevolutionX/releases/download/v0.1.1/nevox_hdd.zip) appears to download the 0.1.0 version. When unzipped, the downloaded file has a date of 3/18. Tried clearing browser cache, different browser, etc...

Thank you so much for opening this issue.
Please try again as I've uploaded a new file, generated a couple of minutes ago.

It is fixed. Thanks.


feat: add failure workflow step to report issues

Signed-off-by: Asra Ali<EMAIL_ADDRESS>Inspired by https://github.com/slsa-framework/example-package/blob/main/.github/workflows/scripts/e2e-report-failure.sh
Fixes https://github.com/sigstore/root-signing/issues/352

Summary

Release Note

Documentation

This looks great!


[Do not commit] Refactor creds in Jenkinsfile

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 48s

Maven dependency ordering for branch

+1 :green_heart:
shadedclient
13m 32s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 3 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
13m 10s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 34s

The patch does not generate ASF License warnings.

42m 58s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3165/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3165

Optional Tests
dupname asflicense codespell shellcheck shelldocs

uname
Linux 2cffc6bef16f 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c0e4a8378c8cbef3524cb888f1ebcc0b14c826ca

Max. process+thread count
633 (vs. ulimit of 5500)

modules
C:  U:

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3165/4/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 26s

Maven dependency ordering for branch

+1 :green_heart:
shadedclient
15m 40s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 22s

Maven dependency ordering for patch

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 3 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
15m 24s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

47m  0s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3165/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3165

Optional Tests
dupname asflicense codespell shellcheck shelldocs

uname
Linux 8484275b7ed9 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 60cdb6b8dd399f9bf2ec65f320c64137030803e5

Max. process+thread count
521 (vs. ulimit of 5500)

modules
C:  U:

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3165/5/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Closing this PR since this was only for dev/testing. Will take this forward in https://github.com/apache/hadoop/pull/3167.


Implement vector::operator==() using equal()

https://en.cppreference.com/w/cpp/algorithm/equal

https://github.com/DymOK93/KTL/commit/44e466114839500c9f9ce1e38c7ecca5c05d86aa


<the argument Type 'void ...' cannot be assigned to ... 'ImageStreamListener'>

Hi @hagyao520
from the error you posted seems that in your code a void is passed as StreamListener.
This platform is not met for assistance on personal code,
please see https://flutter.dev/community for resources for asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it.
Please refrain from posting pictures if not necessary.
Thank you

更新版本后，cached_network_image这个dart调用就报错，我并没有使用，只是import

Hi @hagyao520
could you please provide your updated  flutter doctor -v
and your flutter run --verbose?
Also, to better address the issue, would be helpful
if you could post a minimal code sample to reproduce the problem
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.


dummy issue to test teams integration

ignore me :smile:
Configuration information

EHRbase version:
openEHR_SDK version:
Archie version:
PostgreSQL version:
Java Runtime version:
Operating System version:

Steps to reproduce

Actual result

Expected result (Acceptance Criteria)

Definition of Done

[ ] The defect is checked by an unit or an integration test (Robot)
[ ] Merge Request approved
[ ] Unit tests passed
[ ] Build without errors
[ ] Release notes prepared
[ ] No additional runtime warnings

test comment

test comment

works :!!:


Celestia Core Devs Call 5

Celestia Core Devs Call 5

Meeting Information
When: Tuesday, February 20, 5:00 PM CET, 60 minutes max
Where: Youtube Livestream
Agenda

Roll Call

Consensus:

Core/app Team
Strangelove
IBC team
Binary Builders
Informal

DA

celestia-node
Eiger

Working Groups Updates

Updates from DA Working Group
Updates from Interface Working Group
Updates from ZK Working Group

CIP-9 Moving to Final
CIPs Moving to Last Call

CIP-6
CIP-10
CIP-12

CIP-17
CIP-14 to Review

ok

Recording: https://www.youtube.com/watch?v=WFPEMAuGEM0
Notes: https://twitter.com/JoshCStein/status/1759972091724526084

CDC 6: https://github.com/celestiaorg/CIPs/issues/87


Redirect to "Exercice" page after "Fin d'exercice" ends

In real life, I often click on "Exercice" after "Fin d'exercice" ends.
Make it redirect automatically.

Done in 1894db6cba72ca12933f839ca388cae156954488


change default encoder for CV Apps

The default encoder of  CV is BigTransferEncoder, which requires downloading the pretrained models manually. It's better to switch something like ImageKerasEncoder or ImageTorchEncoder that having downloading functions.

Created this PR for fix: https://github.com/jina-ai/cookiecutter-jina/pull/31


impersonation

First, thanks SO MUCH for keeping this library going.  Those of us who are depending on you are grateful and appreciative.
I've gotten V4.0.0.-beta.1 working in my main use case, which is wholly passwordless.  Huzzah!
However, impersonation no longer works. Instead, I get a "state" error as listed below.
The Auth0 docs leave a lot to be desired on this end.  Searching through the library code doesn't seem to even have reference to the state parameter.  So I'm a bit stuck.  I'm leaving the "state" field blank in my impersonation request as I did under 3.0, but this doesn't appear to work in v4.  Thoughts?  Approach?
"Error: Auth0 returned error `invalid_token`: `state` does not match.↵    at Auth0Error.EmberError (http://localhost:4200/assets/vendor.js:28661:25)↵    at new Auth0Error (http://localhost:4200/assets/vendor.js:171830:16)↵    at auth0.parseHash (http://localhost:4200/assets/vendor.js:171568:27)↵    at WebAuth.validateAuthenticationResponse (http://localhost:4200/assets/vendor.js:86120:13)↵    at WebAuth.parseHash (http://localhost:4200/assets/vendor.js:86093:16)↵    at RSVP.Promise (http://localhost:4200/assets/vendor.js:171566:15)↵    at initializePromise (http://localhost:4200/assets/vendor.js:65985:7)↵    at new Promise (http://localhost:4200/assets/vendor.js:66464:35)↵    at Class._getUrlHashData (http://localhost:4200/assets/vendor.js:171565:14)↵    at tryCatcher (http://localhost:4200/assets/vendor.js:65782:21)"
__proto__
:
EmberError

Glad to help! Bit of an odd set of circumstances that led me here, but here we are. :P
Poking at this a bit, Auth0's guide on User Impersonation does warn against leaving the state field blank:

State: The state is a required parameter and leaving it blank may lead to errors like Impersonation - Bad mac.

...Having said that, though, I can reproduce the error regardless of whether or not I put something in the state field, so something's definitely goofy. I'll take a look.

Tracked this down; it's an auth0.js change. The short version is that impersonation now needs to be enabled via flag when calling a certain method (parseHash, which this addon uses).
Auth0 has stated this was motivated by security concerns (though they haven't elaborated just yet), so I'm going to follow suit and add an enableImpersonation flag to Ember's environment configuration so it's strictly an opt-in thing. That sound good?
It's a breaking change, but it's convenient that we're preparing for a major release anyway. ;)

Perfect
On Mar 16, 2018, 08:00 -0700, Xaser Acheron<EMAIL_ADDRESS>wrote:

Tracked this down; it's an auth0.js change. The short version is that impersonation now needs to be enabled via flag when calling a certain method (parseHash, which this addon uses).
Auth0 has stated this was motivated by security concerns (though they haven't elaborated just yet), so I'm going to follow suit and add an enableImpersonation flag to Ember's environment configuration so it's strictly an opt-in thing. That sound good?
It's a breaking change, but it's convenient that we're preparing for a major release anyway. ;)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Just published v4.0.0-beta.2 with the new flag. Set it in your app's config/environment.js and you should be good to go!
// config/environment.js
module.exports = function(environment) {
  let ENV = {
    'ember-simple-auth': {
      authenticationRoute: 'login',
      auth0: {
        clientID: '1234',
        domain: 'my-company.auth0.com',
        logoutReturnToURL: '/logout',
        enableImpersonation: true
      }
    }
  };

  return ENV;
};


The tooltip is fixed after clicking the tooltip bound element

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior
The popup tooltip should disappear when another tooltip appear or pointer has left the tooltip bound element.
Actual behavior

The tooltip will be fixed after clicking the tooltip bound element.
Reproduction of behavior

Click the tooltip bound element.
Environment details

Angular version:
2.4.2

Clarity version:
0.8.7

OS and version:
Mac/Ubuntu

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
All

As a user I would rather consider this as a feature. But it could be valuable if I could copy the tooltip text, which is not possible with the current implementation.
Any UX comment, Clarity Team?

Sometimes the issue may cause confusions.

I totally agree that there should be only one fixed.

hi @steven-zou we just released a tooltip angular component in 0.8.13. Try it and let us know if you still experience the same issue.

Upgrade to 0.8.15, issue is fixed. Close this issue now.


Use dbt-action with token (for eg DataBricks)

DataBricks dbt profiles use a token instead of username/password
Is that possible today?

Hi there,
Many thanks for writing. I'd be happy to work on adding support for databricks. Would you be able to send me a sample profiles.yml file so I can see the required fields.

Sure, here you go!
default:   target: dev   outputs:     dev:       type: spark       method: http       schema: dev_ernest       host: dbc-0b1dfbf6-3cc5.cloud.databricks.com       port: 443       token: HIDDEN       cluster: 0505-153618-tours233       connect_timeout: 30       connect_retries: 15       threads: 5

OK let's try this since I don't yet use databricks myself.

In your profiles.yml, please change HIDDEN to _token_ so it should look like this:

default:
  target: dev
  outputs:
    dev:
      type: spark
      method: http
      schema: dev_ernest
      host: dbc-0b1dfbf6-3cc5.cloud.databricks.com
      port: 443
      token: _token_
      cluster: 0505-153618-tours233
      connect_timeout: 30
      connect_retries: 15
      threads: 5

Create a secret in your repo to hold the value of the databricks token, eg TOKEN

In your workflows file that uses this action, use this format:

    - name: dbt-action
      uses: mwhitaker/dbt-action@databricks
      with:
        dbt_command: "dbt run --profiles-dir ."
      env:
        DBT_TOKEN: ${{ secrets.TOKEN }}

Let me know if that works so I can add it to the main branch.

Hmm, didn't seem to work.

It complains about the missing spark adapter. I can try changing to http
It didn't seem to see the token.  I had to specify an "Environment" for the Secret - not sure that matters

/usr/bin/docker run --name a33c1ca867f13194f41ed88f6cb280670103b_b27b9b --label 8a33c1 --workdir /github/workspace --rm -e DBT_TOKEN -e INPUT_DBT_COMMAND -e INPUT_DBT_PROJECT_FOLDER -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/dbt_salesforce/dbt_salesforce":"/github/workspace" 8a33c1:ca867f13194f41ed88f6cb280670103b  "dbt run --profiles-dir ."
8
dbt project folder set as: "."
9
no token provided
10
saving console output in "./dbt_console_output.txt"
11
Running with dbt=0.19.0
12
Encountered an error while reading profiles:
13
  ERROR Runtime Error
14
  Credentials in profile "default", target "dev" invalid: Runtime Error
15
    Could not find adapter type spark!
16

Ah, it is already using the http adapter for spark.  It may need to be build into the environment. I wonder if it would help to run the dba-env command?
https://github.com/drernie/dbt_salesforce/pull/1/checks?check_run_id=2733635047

Does this seem to be the right way to add the secret?

I don't think it's an issue with the secret - I just have a bad echo statement about the token missing that I'll take out. I think this has something to do with missing dependencies that databricks might need. Is there an example of a Dockerfile that works with dbt and databricks? Since I don't have any experience with databricks this is hard for me to test, so an option would be if you invite me to access your repo so I can try a few things to get this working.

As a quick fix, I added dbt-spark to the Dockerfile. Can you try running the workflow again and see if it works?
Maybe also try with the simple dbt --version command:
- name: dbt-action
   uses: mwhitaker/dbt-action@databricks
   with:
      dbt_command: "dbt --version"

it should print out that the spark plugin is installed

Added you. Re-pushing
      - name: dbt-action
        uses: mwhitaker/dbt-action@databricks
        with:
          dbt_command: "dbt --version"
        env:
          DBT_TOKEN: ${{ secrets.TOKEN }}
      - name: dbt-action
        uses: mwhitaker/dbt-action@databricks
        with:
          dbt_command: "dbt debug --profiles-dir ."
        env:
          DBT_TOKEN: ${{ secrets.TOKEN }}
      - name: dbt-action
        uses: mwhitaker/dbt-action@databricks
        with:
          dbt_command: "dbt run --profiles-dir ."
        env:
          DBT_TOKEN: ${{ secrets.TOKEN }}

OK - I think it works after I updated the Dockerfile to add some dependencies. Check your repo. You just have an error with the models themselves so I commented out the step that actually runs dbt, but you can see that it successfully connects to databricks.
I'll work on merging this into the main branch. Many thanks for helping to add support for databricks!

Actually you do still have a connection error, but I think that dbt itself runs OK. Try to use the repo secret and not environment secret: https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository

By George, I think we've got it:
https://github.com/drernie/dbt_salesforce/pull/1/checks#
(last fix was adding 'dbt deps' -- may want to remind people of that.
I also plan to add 'dbt test' - I don't think 'dbt run' does that automatically, does it?

Sweet - so you were only able to run it if you use dbt deps in an earlier step? I never had to use it before, but my use case may be simpler than yours.
In any case you can now expand on the workflow to add cron schedules, trigger the run with an API call, use conditional steps, email results, etc. I personally think that using dbt with Github Actions comes with so many benefits. Thanks again for helping out!

Yes, we are golden.  Thanks so much for your responsiveness!


[Help] support turn msvc compile commands to clang compile commands?

Hi, @0xabu this repo is very useful to export msvc compile commands.
But could it support export change cl.exe to clang++?
Thanks again for this repo!

You have a project that builds with MSVC but want to have a compilation database with clang commands. Why would that be useful?
It sounds like a messy problem that is probably impossible to solve in a general sense. It would involve mapping command-line arguments between compilers. Obviously that mapping is not complete (some MSVC flags have no Clang equivalent), but even if it were, it would not make sense to pass the same parameters (e.g. system headers, libc/STL headers, will differ between the compilers).

Ah, ok. In that case it probably just cares about a few specific flags (e.g. CPP defines, include paths, forced includes, language standards, etc.), so it may be practical to build a bunch of replacements to handle those. I'm not sure it makes sense as part of this project however.

@0xabu Yes, agree with the last sentence. Thanks!

I was in same situation - I wanted to use VIM with LSP support for editing files in a MSVC project. I managed to enable clang-cl support with a little bit of tweaking.
See attached patch. It is meant to be applied to commit d9b1dec. Works for me™, I'm sure for the real world the patch would need more work.
CompileCommandsJson-clang.patch


Snackbar issue

Bug, feature request, or proposal:
Maybe a bug
What is the expected behavior?
What is the current behavior?
What are the steps to reproduce?
I have a google map which has a polygon. When you click on the polygon, a mark is created and if you want to drag it out of it, you can not, showing an error message inside a snackbar. The problem is that the snackbar is not working correctly. Is it my mistake? Snackbar error? Ghost error? Thx
https://stackblitz.com/edit/angular-fojeor
Other example (My PC, not https://stackblitz.com)

Stackblitz example (.gif)

What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Material 5.2.4
Is there anything else we should know?

I'm having a hard time reproducing the issue @avechuche. At what point is the snack bar supposed to show up?

Hello @crisbeto , thanks for the attention. The snackbar should appear in the lower and centered part of the screen, the default position. I do not know why it appears above on the left, it can not be closed either. Many instances open (see image). If you can not reproduce the error, expand the right panel of stackblitz. I added some marks when I started the map. I attach a .gif to show the problem.

Sorry, what I meant is in your example I'm not seeing any snack bars at all. None are in the DOM either.

@crisbeto I see, a confusion. The snackbars appear in the DOM when I try to drag a mark out of the polygon. They are not in the DOM. The image shows how they accumulate in the DOM each time I drag a mark outside the polygon. I can not close them and they do not close alone with 'duration' property, as you can see in the .gif

Thanks, now I can reproduce it.

It looks like your issue comes from the fact that the Google Maps callbacks are being run outside of the NgZone. You can get it working by running the snack bar calls inside the zone. Here's a working fork of your example.


Fix huge message spacing in v0.66.1

A recent Rocket.Chat update made a change or something that caused the spacing between sequential messages to be really big. This PR fixes it.

Fantastic, thank you!


Automatic cluster discovery in Tectonic Installer

Feature Request
Environment
What hardware/cloud provider/hypervisor is being used with Tectonic?
bare-metal
Desired Feature
It would be great if the Tectonic Installer would automatically discover cluster nodes.
Other Information

In "Cluster DNS" I have to provide the DNS names of the controllers and the workers. But in "Cluster Size", you ask me how many controllers and workers there are. You could deduce this from the number of DNS A records you found in the "Cluster DNS" step and insert that as default values during the "Cluster Size" step.
You could deduce the node's MAC addresses and individual DNS names from the same controllers and workers DNS records. MAC addresses: Resolve the A RR to an IP and run arping on that. DNS names: Resolve the A RR to the IP and follow the PTR.
You could also read all of this from an existing CMDB, like Collins or Clusto.
You could utilize LLDP to gather this information (e.g. using lldpd) and implement your own CMDB.

Obviously these automatisma could fail in various ways, so the result should only be given as default values for the various fields of the installer, with the user easily being able to confirm or correct them.

Hey @urzds - thanks for filing this. Will look into this request and get back to you in the next few days!

Not sure if this issue is the same as mine, but basically my install fails if I have more than one NIC on the nodes I'm trying to connect to the installer.
It seems that whatever iso gets pxe-booted pics the wrong NIC to use to identify itself with the matchbox/bootcfg server.