Not running

Just today the program don't run. Before it's work great.
Is there any update ?

Yes, tool not working today. Please fix.

It's since they changed the Metamon interface, it seems there's no more page. Code is going to be fixed asap :-)

At  """ Obtain list of metamons on the wallet""" replace function as bellow:
def get_wallet_properties(self):
""" Obtain list of metamons on the wallet"""
data = []
page = 1
while True:
payload = {"address": self.address, "page": page, "pageSize": 60}
headers = {
"accessToken": self.token,
}
response = post_formdata(payload, WALLET_PROPERTY_LIST, headers)
mtms = response.get("data", {}).get("metamonList", [])
if len(mtms) > 0:
data.extend(mtms)
page += 1
return data
else:
break
return data

I fixed it, now waiting for @MetaMon-game-player to accept the pull request.

I fixed it myself, thanks for raising issue


Issue with Babel Async/Await

FYI - I am trying to use this library with BabelJS in NodeJS. Below is a sample:
class Blah {
  static async DoSomething() {
    let results = await r.table("someTable").run();
    console.log(JSON.stringify(results));
  }
}

When I try to run the program, an exception is throw:
"Annonymous function returned undefined. Did you forget a return?"

Hmmmm... more info. A prior call using async/await works, so there must be something in particular about this particular query. The real query is using a filter function, which is probably the culprit somehow?
    let associations = await r.table(TABLE)
      .filter(function(association) {
        return
          association("profile")("name").match(nameMatch)
            .and(
            association("profile")("location").match(locationMatch)
          );
      })
      .pluck("id")
      .run();

??

Are you sure the function in the query using filter is the one in your code?
The filter function return undefined, which doesn't work.
On Sun, Jul 19, 2015, 21:29 Chris Beckett<EMAIL_ADDRESS>wrote:

Hmmmm... more info. A prior call using async/await works, so there must be
something in particular about this particular query. The real query is
using a filter function, which is probably the culprit somehow?
let associations = await r.table(TABLE)
  .filter(function(association) {
    return
      association("profile")("name").match(nameMatch)
        .and(
        association("profile")("location").match(locationMatch)
      );
  })
  .pluck("id")
  .run();

??
—
Reply to this email directly or view it on GitHub
https://github.com/neumino/rethinkdbdash/issues/114#issuecomment-122697019
.

Here is the query executing in the Data Explorer:
r.db("hoamlife")
  .table("associations")
	.filter(function(association) {
    return
      association("profile")("name").match("^Becky's Corner$")
      .and(
        association("profile")("location").match("^Lynnwood, WA$")
      );
  })

The nameMatch and locationMatch variables are set in my code... in the sample here I have hard-coded them. The query works.

Are your variables set to be string or RegExp in your code? RegExp are not
supported.
Or are they functions instead of strings?
On Mon, Jul 20, 2015, 02:26 Chris Beckett<EMAIL_ADDRESS>wrote:

Here is the query executing in the Data Explorer:
r.db("hoamlife")
.table("associations")
.filter(function(association) {
return
association("profile")("name").match("^Becky's Corner$")
.and(
association("profile")("location").match("^Lynnwood, WA$")
);
})
The nameMatch and locationMatch variables are set in my code... in the
sample here I have hard-coded them. The query works.
—
Reply to this email directly or view it on GitHub
https://github.com/neumino/rethinkdbdash/issues/114#issuecomment-122722233
.

Can you provide a full script with await that throws the error?

Give me a couple of days and I will try to reproduce and share a gist with something from the test database.

Closing. Please provide as this is probably more an issue with babel than with the driver.
If you still have issues, please provide a babel script and I can try to take a look at it.


perf: save an unecessary query during joinChannel

Brings into line with joinChannels (plural).
API calls should probably be "Objective-centric": what matters is whether you have the objective or not (you couldn't have the objective without already having the channel, anyway, due to DB constraints added during insert).
The channel will be re-fetched, later, (in any case) when the objective is cranked.

API calls should probably be "Objective-centric": what matters is whether you have the objective or not (you couldn't have the objective without already having the channel, anyway, due to DB constraints added during insert).

Is this true? There is no FK-relationship that I could see that enforces this.

Is this true? There is no FK-relationship that I could see that enforces this.

I believe our ORM enforces this? I remember attempting to create a test where an objective refers to a nonexistent channel but it failed on insert.

Is this true? There is no FK-relationship that I could see that enforces this.

I believe our ORM enforces this? I remember attempting to create a test where an objective refers to a nonexistent channel but it failed on insert.

There is a table objectives_channels, which will not allow a row to be inserted if the channel does not exist. But the DB will not prevent you from inserting a row into objectives, as there is no FK constraint in the objectives table.
Our application code does prevent Objective.insert from passing if the channel does not exist.
Pedantic summary:
A. Neither the DB nor the ORM prevents us from inserting objectives when the channels are not known.
B. ObjectiveModel.insert will not succeed if the "target channel" of the four DBObjectives is not stored.

Pedantic summary:

I think it is probably not worth pursuing this now, as the relationship between objectives and channels is probably going to change soon anyway, and we will hopefully know better then, when we need to do checks like this. For instance: maybe we should do the check when approving the objective.
The discrepancy between joinChannel and joinChannels remains, for now.


doc: Migrate from Annotations to Attributes

Q
A

Type
doc

BC Break
no

Fixed issues
PHPORM-193

Summary
Doctrine annotations are deprecated, I think we can remove any reference of them from the doc and rely on previous versions for projects that are still using them.
I translated every annotation example into attributes, but not tested yet. I don't have the knowledge to find what need to be modified specifically.

Reviewing this is no pleasure, but at first glance it looked fine.

I'm sorry, I've held back and only changed the attributes and a few syntax errors.

I'm sorry, I've held back and only changed the annotations and a few syntax errors.

Sorry, this shouldn't have come across as criticism. I struggle reviewing repetitive changes, so I needed to do this in multiple steps. The work itself was great and long overdue 👍


Update README.md

Replace description with authentic, standard summary of Catch's value prop and how to get started.
Update documentation, contacts, and contributing sections to reflect the sequencing we actually want merchants to follow.

Can you include some unit tests please?
:trollface:

👀
On Tue, Aug 22, 2023 at 3:35 PM Lev Kanter @.***> wrote:

Can you include some unit tests please?
[image: :trollface:]
—
Reply to this email directly, view it on GitHub
https://github.com/getcatch/catch-sfcc/pull/1#issuecomment-1689014758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPZEIQFR5OO7CVJKZXWE2DXWUX4JANCNFSM6AAAAAA32RHVGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Several issues around the flat object type

Is your feature request related to a problem? Please describe
In #6507, we add the flat object type. In current implementation, we use two stages to process the flat_object field in the document. First we use the JsonToStringXContentParser to collect all the keys and values (keyList, valueList and valueAndPathList) in the field and convert to XContentParser for return. The Lucene fields are then constructed by parsing the fields in the XContentParser.
https://github.com/opensearch-project/OpenSearch/blob/d6bda7dca75dc4d328b61abcd21b35a6bdfcab05/server/src/main/java/org/opensearch/common/xcontent/JsonToStringXContentParser.java#L80-L85
For a field of flat_object type in a document, the following internal fields will be created by default:

root StringField and SortedSetDocValuesField for each subfield key(prefiexed by root field name);
value StringField and SortedSetDocValuesField for each subfield value;
valueAndPath StringField and SortedSetDocValuesField for each subfield;
_field_name StringField for each value and valueAndPath.

PUT test
{
  "mappings": {
    "properties": {
      "field1": {
        "properties": {
          "field2": {
            "type": "flat_object"
          }
        }
      }
    }
  }
}

PUT test/_bulk
{"index": {}}
{"field1": {"field2": {"a": "1", "b": "2"}}}

For example, the request above generates the fields listed below.

There are several issues around the flat object field.

If a subfield in the flat_object field suffixed by VALUE_SUFFIX (._value) or VALUE_AND_PATH_SUFFIX (._valueAndPath),  some extra unexpected field may be created.

https://github.com/opensearch-project/OpenSearch/blob/d6bda7dca75dc4d328b61abcd21b35a6bdfcab05/server/src/main/java/org/opensearch/index/mapper/FlatObjectFieldMapper.java#L660-L669

We use '=' to concat subfield key and value, if a subfield key contains '=', the prefix query may return wrong results.

The root fields is confusing and unnecessary. AFAIK, the root field is use to execute exist query and build fielddata, but it doesn't be generated correctly. For example, if we have document {"field1": {"field2": {"field3": {"a": "1", "b": "2"}}}}, and field2 is flat_object field. After processed, the root fields contains values field1.field2.a, field1.field2.b and field1.field2.field3. The exist query of field1.field2.field3.a doesn't return correct result. On the other hand, I don't know is there any meaning to aggregate or sort on the subfield keys. In fact, I don't think that we need to support aggs on flat_object field, it's a object, not a scalar value. If we do need, then we should aggregate on the subfield values, not the subfield keys. Of course, it still makes sense to aggregate subfields, we can utilize the valueAndPath field to support this.

Creating _field_name field for value and valueAndPath is meaningless. The _field_name field is used by exist query, we just need to create it for each full leaf path of subfield.

The value of SortedSetDocValuesField of value and valueAndPath has unnecessary prefix. When create SortedSetDocValuesField, we use root field name as the prefix of value.

Two-stage processing is unnecessary. In the process of converting to JSON strings, we use a lot of additional resources, this is really unnecessary, we can add the corresponding field to parse context during the process.

Describe the solution you'd like

Use one-stage processing;
Remove the FlatObjecField;
Support the aggs on the subfield, but not the root field, which means the fielddata is not supported on the root field but the subfield;
For the indices created after 2.18.0, remove the prefix of the value of SortedSetDocValuesField.

In addition, I have no good idea to fix the issue 2, any suggestions about this or the overall issue are welcome.
Related component
Search
Describe alternatives you've considered
No response
Additional context
No response

@msfroh @kkewwei  you might be interested in this :)

@msfroh @kkewwei you might be interested in this :)

@bugmakerrrrrr Most of the optimizations make sense to me.
I also agree with the fifth point, and mentioned in the pr https://github.com/opensearch-project/OpenSearch/pull/14383#discussion_r1764553388

We use '=' to concat subfield key and value, if a subfield key contains '=', the prefix query may return wrong results.

Note that if we want to change the delimiter, we need to be careful about backward compatibility.
I believe we can tell what version of OpenSearch was used to create an index. Maybe we can continue to use the old behavior on indices created before the change, while supporting the new behavior only indices created on newer versions.

@bugmakerrrrrr Having read your PR, I really like your improvements and suggestions. Combined with @kkewwei's work in #14383, I think it might be worth it to "fork" the existing flat object code to allow us to make the backward-incompatible changes only on new indices.
Some of your improvements (like getting rid of JsonToStringXParser) can be done in a backwards-compatible way. So, maybe we isolate those changes. Other changes, like removing unnecessary prefixes, using the field names field, not using = as a delimiter, etc. could be moved into a new class and we could mark the old class as deprecated. I believe that we only guarantee backward compatibility from the last 2.x release to 3.0, so the deprecated implementation could be removed in 3.0.

@msfroh make sense to me. I'll create a new PR to make some bwc improvements firstly.


Allow to configure section order in section-out-of-order

Closes #384
Also fix unintended feature where you could configure severity of multiple rules in one --configure statement: it was breaking parsing for any other configurable with commas.
If there will be need for this in the future we can add special parsing of severity (splitting on ,) to configure_checkers_or_reports method.

Codecov Report

Merging #413 (d6c509b) into master (daaa156) will decrease coverage by 1.05%.
The diff coverage is 96.55%.

@@            Coverage Diff             @@
##           master     #413      +/-   ##
==========================================
- Coverage   97.81%   96.75%   -1.06%
==========================================
  Files          22       22
  Lines        2101     2126      +25
==========================================
+ Hits         2055     2057       +2
- Misses         46       69      +23

Impacted Files
Coverage Δ

robocop/checkers/duplications.py
98.37% <96.42%> (-0.60%)
:arrow_down:

robocop/config.py
93.89% <100.00%> (-0.03%)
:arrow_down:

robocop/checkers/misc.py
92.43% <0.00%> (-5.05%)
:arrow_down:

robocop/checkers/documentation.py
96.00% <0.00%> (-4.00%)
:arrow_down:

robocop/checkers/comments.py
96.96% <0.00%> (-3.04%)
:arrow_down:

robocop/checkers/errors.py
95.23% <0.00%> (-2.39%)
:arrow_down:

robocop/checkers/__init__.py
91.01% <0.00%> (-2.25%)
:arrow_down:

robocop/checkers/naming.py
97.25% <0.00%> (-1.65%)
:arrow_down:

robocop/utils/misc.py
97.67% <0.00%> (-1.56%)
:arrow_down:

robocop/checkers/lengths.py
98.75% <0.00%> (-1.25%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


Improve headings for new website

Description
The headers a used to autogenerated the title and table of contents, when they are missing the pages looks odd
Testing everything out over on https://prince-chrismc.github.io/pyrsia-website/ since that was easy for me

Screenshots (optional)

PR Checklist

[x] I've read the contributing guidelines.
[x] I've read "What is a Good PR?"
[x] I've included a good title and brief description along with how to review them.
[x] I've linked any associated an issue.
[x] I've requested a review  from pyrsia/collaborators.

Do we hold off on https://github.com/pyrsia/pyrsia.github.io/pull/28 since there's a lot of review that's required


Refactor/cleanup range option handling

Handle suggestedMin / suggestedMax in getMinMax
If only one of the user defined limits is set and there is no (visible) data, make sure the value is considered min and max
Move finiteOrDefault to helpers

Motivation
Remove duplicate logic and thus make the scale range options easier to manage in the future.

Filename
Size
Change

dist/chart.esm.js
62.5 kB
-75 B (0%)

dist/chart.js
89.1 kB
-14 B (0%)

dist/chart.min.js
61 kB
-10 B (0%)

dist/chunks/helpers.segment.js
15.7 kB
+19 B (0%)

dist/helpers.esm.js
996 B
+7 B (0%)


Windows 10: Notifications not working.

I installed the latest version (0.7.1) and notifications are not working. I checked to see if the option was turned on, and it is.

+1 for this. Tray icon had a badge but no notification received.

I'm not seeing any notifications either.


Add isDropped to SimpleReference.

I include some minor code improvements, and I will extract a PR against master for them, and then rebase again drop-column branch.


Swagger changes for App Gw Server Variables APIs

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

why we need this branch? If it has same functionality a 10-01? please revert in this case

do we need to create any examples?

why we need this branch? it need to be able in 2018-11-01??

Yes the respective changes will be pushed in 2018-11-01 version. So created the branch with this version.

do we need to create any examples?

I'm not aware of examples. What kind of examples do we need to create? Can you please point out any similar changeset with examples.

do we need to create any examples?

Examples have been added. Waiting to merge these changes with network-november-branch.

@nirkum18 was this PR reviewed by ADX swagger reviewers? The ADX swaggers reviewers team is the one approving and merging PRs for the December-network-release branch, so I'm not sure how this one went through, the branch is usually protected. If you did not get a review from the SDK team, could you please sync with @MikhailTryakhov on this merge? FYI - @jianghaolu , @mzehgir @salameer


[$1000] Help tab on settings page should have external link icon like Settings->about->View open jobs and not the current navigation icon

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
Open settings
Click on any tab other then Help, it will have sub menu
Click on Help tab, it will open expensify help link in new tab
Observe that Help tab, even though being a link, has navigation icon

Expected Result:
Help tab should have link icon similar to Settings->about->View open jobs, Settings->Workspaces->select any workspace->Pay bills-> View all bills

Actual Result:
Help tab has navigation icon which provides a impression that it has submenu and is inconsistent with all the link tabs throughout the application

Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number:  v1.2.62-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

https://user-images.githubusercontent.com/43996225/215811298-0d72d87c-a634-4dcb-ad92-142d9a9dcf0d.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1674552068263369
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c4af5c2d37b31ee4
Upwork Job ID:<PHONE_NUMBER>358687744
Last Price Increase: 2023-01-31

Proposal
We need to pass iconRight: Expensicons.NewWindow, in Get assistance page :-
https://github.com/Expensify/App/blob/93854081336980a19b02138a271fead29b37e5d9/src/pages/GetAssistancePage.js#L41-L47
and settings page :-
https://github.com/Expensify/App/blob/93854081336980a19b02138a271fead29b37e5d9/src/pages/settings/InitialSettingsPage.js#L174-L178
We also need to add pass iconRight={item.iconRight} in MenuItem :-
https://github.com/Expensify/App/blob/93854081336980a19b02138a271fead29b37e5d9/src/pages/settings/InitialSettingsPage.js#L197

Proposed Solution:
We have to add iconRight props for the help menu as shown under
Within src/pages/settings/InitialSettingsPage.js file we have to add code as shown under:
getDefaultMenuItems() {
    return ([
	…
        {
            translationKey: 'initialSettingsPage.help',
            icon: Expensicons.QuestionMark,
            iconRight: Expensicons.NewWindow, // Add this code
            action: () => { Link.openExternalLink(CONST.NEWHELP_URL); },
        },
    ]);
}

getMenuItem(item, index) {
    return (
        <MenuItem
           …
           floatRightAvatars={item.floatRightAvatars}
           shouldStackHorizontally={item.shouldStackHorizontally}
           iconRight={item.iconRight}  // Add this code
        />
    );
}

Proposal
There are 3 cases I found so far that don't have correct icon when go to external link on menu item click:
Help on Settings page, Schedule a setup call, Explore help docs on Get assistance page

add iconRight: Expensicons.NewWindow, to these places:
https://github.com/Expensify/App/blob/be6dfe292e38d228c3583f16974c6056832bf695/src/pages/settings/InitialSettingsPage.js#L174-L178
https://github.com/Expensify/App/blob/be6dfe292e38d228c3583f16974c6056832bf695/src/pages/GetAssistancePage.js#L41-L47
https://github.com/Expensify/App/blob/be6dfe292e38d228c3583f16974c6056832bf695/src/pages/GetAssistancePage.js#L52-L58

pass iconRight prop to MenuItem in InitialSettingsPage:
https://github.com/Expensify/App/blob/be6dfe292e38d228c3583f16974c6056832bf695/src/pages/settings/InitialSettingsPage.js#L197-L212

+               iconRight={item.iconRight}

@rushatgabhane @cristipaval thoughts on these proposals?

Thanks @rushatgabhane !
Agree with you. Let's go with @situchan 's solution. cc @anmurali

@cristipaval @rushatgabhane, The schedule call redirect was not in the scope of this issue (if I knew that it was, I would have added that to my solution), and I saw a few issues where the contributor who increased the scope of the issue is paid separately from the one who posted the solution first, like here.

Waiting for @situchan 's solution.

We can close this issue. The solution was already merged into main during weekend from #14641.
It was already being done internally.

Oh I see.. Thanks @situchan!

Hello @cristipaval , good to hear that bug is resolved. I am the reporter for this bug. I saw that it was being worked internally but when I saw the pull request, the steps seems to be exactly same as what I reported on slack. There is a slack link in pull request but I don't have access to it. By any chance, if they had referenced my bug report to start the internal issue, will I be compensated for reporting it? Can you once check and let me know?
Here is the link to my slack bug report:
https://app.slack.com/client/T03SC9DTT/threads/thread/C049HHMV9SM-1674552068.263369

Hey @dhanashree-sawant ! Thanks for raising your concern. @anmurali is in charge with the payment, she will reply soon.

Hi @anmurali , kindly let me know your thoughts on my above comment.

Paid.


Question regarding paper

Hello,
First, I apologize if this is not a proper channel to ask about your paper "MELLOTRON: MULTISPEAKER EXPRESSIVE VOICE SYNTHESIS BY CONDITIONING ON RHYTHM, PITCH AND GLOBAL STYLE TOKENS Rafael Valle*, Jason Li*, Ryan Prenger, Bryan Catanzaro NVIDIA Corporation".
According to this paper Table 1, it is giving GPE of 0.08% for both single and multi-speaker case.
I tried to replicate this but it didn't go well. VDE and FFE were replicated but not GPE.
My question is, what did you use for denominator in your equation for GPE?
Accordingto the "Towards End-to-End Prosody Transfer for Expressive Speech Synthesis with Tacotron" paper, GPE uses the number of frames that are voiced in both geneated and reference signal. However, other metrics in this paper, such as VDE and FFE uses the number of all frames.
It would make sense to me if you used the number of all frames to calculate GPE in Table 1 of "Mellotron" paper.

Thanks!

Uh,, now I am pretty sure you used the number of all the frames for the denumerator of GPE equation because your GPE and VDE sums to FFE.. but the paper you referenced for GPE "A method for fundamental frequency estimation and voicingdecision: Application to infant utterances recorded in realacoustical environments" also uses number of voiced frames as denumerator..

We use the equations described in "Towards End-to-End Prosody Transfer for Expressive Speech Synthesis with Tacotron"

But that one also has the number of voiced frames as denominator

Thanks for bringing this to our attention. You are correct, we used the wrong denominator in calculating GPE. Our new GPE numbers are as follow:
Mellotron LJS-Sally: 0.08% -> 0.26%
Mellotron LibriTTS: 0.08% -> 0.42%
We will update the paper shortly


URL not correctly set for section and geometry

Steps to reproduce

Create a new borehole
go to the tab borehole, then section or geometry
enter values or a borehole geometry
do refresh

Expected behavior
after the refresh you are in the same tab
Current behavior
after thr refresh you are in the general tab
I assume the urls are not upgraded for the two new tabs

top, danke!


[hotfix] Fix CsvRowDataDeserializationSchema constructor

The csvSchema field was wrongly initialized.

@afedulov Thanks for the backport!


Observer implementation not compatible with the Interface

In the Observers implemented for Sezzle extension, none of them is compatible with the Interface:
https://github.com/sezzle/sezzle-magento2/blob/c7825f3bf438eccbf4a084bf823f07d22b10e789/Observer/SendOrderConfirmationMailObserver.php#L48
https://github.com/sezzle/sezzle-magento2/blob/c7825f3bf438eccbf4a084bf823f07d22b10e789/Observer/PaymentMethodAvailabilityObserver.php#L45
https://github.com/sezzle/sezzle-magento2/blob/c7825f3bf438eccbf4a084bf823f07d22b10e789/Observer/OrderStatusChangeOnVoidObserver.php#L23
Please see the declaration of ObserverInterface
https://github.com/magento/magento2/blob/5a2037c35de89ce2c50e230164ff3ea7b67ac127/lib/internal/Magento/Framework/Event/ObserverInterface.php#L16-L23

Sorry, I could not find any reason why you think its not compatible unless you think its because of the return type?

@arijit-sezzle Yes, the return type of Observer classes should be void.

Makes sense. Just curious, did you find out its erroring in 2.4.7 because if this?

Before letting our Developers integrate new extensions, we perform thorough Code Review to make sure that 3rd party extension won't cause any issues. In this specific case, PHPStan reported that your code is flaky, so I fixed the issue in a Composer Patch and informed you about the problem.

The repository maintainers did not submit the update.
Fixed in https://github.com/sezzle/sezzle-magento2/commit/9836961b88488d8808e59234b58f11d49a3d51de


There are a few buttons not workingproperly. Ui is disturbed in few pages

Hi there! I am selected as GSSOC contributor and your tech stack matches mine so I would like to be a part of this project ⭐

some contributor is working on this


prefix extension properties

Based on the discussion in #204 Adding _UIKitNavigation_ prefix to all the UIViewController extension properties.

Looks like CI failed:

Value of type 'NavigationStackController' has no member 'hasViewAppeared'

I think from this line: https://github.com/pointfreeco/swift-navigation/blob/70321c441d51b0b893c3abbf79687f550a027fde/Examples/CaseStudiesTests/NavigationStackTests.swift#L240
Can you update that line and hopefully things will be green?

Ha I forgot to run the example test cases... But luckily it helped to find a type which can cause a run time crash


Missing BITCOIN PaymentInstrument

Hello,
I would like to have BITCOIN account regarding latest GoPay docs
https://help.gopay.com/cs/tema/integrace-platebni-brany/technicky-popis-integrace-platebni-brany/technicke-parametry-platebnich-metod

Closed via #37

@josefzajac Could you please try dev-master, I would like to tag a new version. We need to be sure that this feature is working ;-)

@f3l1x Commit installed and tested on prod, Bitcoin gate is used, gate.gopay.cz is redirecting to https://bitcoinpay.com/cs for payment, do you need screenshots or ... ? :)
markette/gopay-inline: dev-master#17ec3c69507adb1b3a890ae8dc090bb91c795631

Nope, it's ok. Thank you ;-)

v1.1.2 released, thanks.
https://github.com/Markette/GopayInline/releases/tag/v1.1.2


Commissioning State Machine

Problem
Existing commissioning examples do not provide a clean path to support many ecosystem-specific needs.  In particular, app-specific context injection and integration into complex, async UI flows are very difficult.  There are also many spec-centric concepts that should be readily supportable, but are not.  Some examples are a split commissioner / fabric administrator topology,  end-to-end verification of CSR attestation signature in remote PKI infrastructure, IPK distribution, and PKI-assigned fabric and node IDs.
Fixes #7951, #13500, #13501, #13503, #13504, #13657
Change overview
This adds an alternative commissioner implementation that aims to be extensible and relatively free of dependencies on existing commissioner and controller code.  Instead, a self-contained commissioner instance is instantiated for each commissionee.  On commissioning success, the commissionee can be added to a controller instance for tracking and subsequent interaction.  On failure, the commissioner object can be disposed.  Decoupling from the existing controller also means that this commissioner implementation can be readily used with alternative controller implementations that may exist outside of the tree.
The commissioner implementation leverages the new src/lib StateMachine utility, which organizes a state machine as variant state and event object types that are connected through a pattern matching transitions table.  Core sdk states and events are provided, while apps define how these should be composed into a commissioner through definition of their own transitions table.  An example is provided and integrated into chip-tool.  But consuming apps can add, remove and reorganize states as needed.  App-specific logic and context-injection are readily achievable in this design.
Another benefit of the state machine implementation is that memory footprint is reduced.  Because each state is a formal object type, each state can hold its own state data.  This removes the need to hold all state variables in a top-level object like the chip::Controller::DeviceCommissioner or CommissioneeDeviceProxy.  The design also introduces the possibility of concurrency.  If underlying resources permit, any number of concurrent commissioning instances can be instantiated.
Testing

Verified existing unit tests and chip-tool integration tests pass.
Manually tested ble-wifi commissioning of an M5Stack from Linux chip-tool
Manually tested ble-wifi commissioning of an M5Stack from Darwin chip-tool
Manually tested on-networking commissioning of Linux all-clusters app from Linux chip-tool
Manually tested on-networking commissioning of Linux all-clusters app from Darwin chip-tool

Do we actually allow more than one commissioning at once?

Yes.  The restriction on a single PASE session is only for responders (commissionees).
Providing this solution for concurrent commissioning would be useful in many scenarios.  Among are onboarding payload concatenation, where one needs to commission multiple devices at once.  Doing so in parallel is obviously faster, and would be very feasible particularly for on-network commissioning as would be the case for a bulk multi-admin migration.
UDC is another example.  For UDC, we don't currently have a good solution to the fact that a commissioner, acting as both a user-serving device and a commissionee-serving device, has no good way to arbitrate between the two usages.  I hope the existing commissioner breaks gracefully when there is contention, but I don't know that this is the case.
Also, our existing architecture already allows multiple, concurrent commissioning sessions.  The existing solution allows this by vending multiple fabric-scoped commissioners from the commissioner factory.  You could in theory commission from each concurrently.
This, however, is architecturally awkward.  In the strictest sense, commissioners don't have fabric scope at all.  In fact, they don't even need certificates.  The admin that establishes CASE and issues commissioning complete does need certificates, but this may or may not be the same node as the commissioner.  Multiple companies are targeting a split commissioner / admin topology.
And the fact we have multiple fabric-scoped commissioner identities also raises the question of who acts as the UDC server.  It does not make sense to have more than one server because: 1) advertisement semantics don't allow for it and 2) just like the underlying commissioners, UDC servers don't have a fabric identity.
https://github.com/project-chip/connectedhomeip/issues/10089 recognizes this problem.
The architecture introduced here provides reasonable answers to all of these problems.

@turon , thanks for the comments.

The formal split of Commissioner from Controller is a good step.

Yes I think there consensus that this is needed.  https://github.com/project-chip/connectedhomeip/issues/11536 recognizes this.

What happens to the original Commissioner implementation over time if this alternate approach moves forward?

For the time being, the two approaches can coexist.  But my hope would be that the utility of this approach would incentivize the migration of other example applications in addition to chip-tool.  However, the existing commissioner is somewhat reliant on integration tests through linking to example applications.  It would slowly lose this coverage as examples are migrated.  I don't have a good answer to that.

What happens to the original Commissioner implementation over time if this alternate approach moves forward?

For the time being, the two approaches can coexist. But my hope would be that the utility of this approach would incentivize the migration of other example applications in addition to chip-tool. However, the existing commissioner is somewhat reliant on integration tests through linking to example applications. It would slowly lose this coverage as examples are migrated. I don't have a good answer to that.

@msandstedt Is it correct that this patch migrates chip-tool to your new implementation?  If so, which remaining tools use the original code and how does a particular app configure to use one approach vs. another?

What happens to the original Commissioner implementation over time if this alternate approach moves forward?

For the time being, the two approaches can coexist. But my hope would be that the utility of this approach would incentivize the migration of other example applications in addition to chip-tool. However, the existing commissioner is somewhat reliant on integration tests through linking to example applications. It would slowly lose this coverage as examples are migrated. I don't have a good answer to that.

@msandstedt Is it correct that this patch migrates chip-tool to your new implementation? If so, which remaining tools use the original code and how does a particular app configure to use one approach vs. another?

Yes, it's true that this patch migrates chip-tool to the new implementation.  The python, Darwin and Andriod applications are still using the existing code for commissioning.
The way one would use the new approach is to rework the integration layer of a given app to call into the Example commissioner provided in this PR, or a copy of that with suitable extensions, instead of the existing in-tree commissioner.
The changes for chip-tool in this patch show how this would be done of this and are actually very modest when you remove the delta created by the renaming of s/commissioner/controller (where this renaming is provided as a separate commit to make this more obvious).

The formal split of Commissioner from Controller is a good step.

I second this.

My concern with this PR is not so much about the content, but about support. There's a lot of code here that is the same as the code in the current implementation but is completely separate. Chip tool has now been swapped to use this implementation, meaning when we go to add anything to the commissioning process (which we definitely will with the recent network commissioning changes, for example), we now need to double add to this new implementation as well as the current implementation. We're already supporting both chip-device-ctrl and chip-tool and will soon be supporting the repl stuff as well. we now also have to support two different commissioning examples as well as multiple device discovery examples. We're less than a month from TE8 FC.

My concern with this PR is not so much about the content, but about support. There's a lot of code here that is the same as the code in the current implementation but is completely separate. Chip tool has now been swapped to use this implementation, meaning when we go to add anything to the commissioning process (which we definitely will with the recent network commissioning changes, for example), we now need to double add to this new implementation as well as the current implementation. We're already supporting both chip-device-ctrl and chip-tool and will soon be supporting the repl stuff as well. we now also have to support two different commissioning examples as well as multiple device discovery examples. We're less than a month from TE8 FC.

I understand this concern and would welcome input on a realistic pathway by which code like this can become part of the sdk.  Do we have a list of commissioner features for upcoming test events that are yet to be delivered?

Fast tracking, given > 3 days for review.

Removing fast track, as this is in draft state.


Create lab pages

Create the individual lab pages here, then copy them to a repl assignment.

OK, well, I did this backwards. Copying the lab pages in a moment.


I can't launch my app

Hello I get this problem when I try to launch my app on android studio (on Mac ):
Warning: CocoaPods is installed but broken. Skipping pod install.
  You appear to have CocoaPods installed but it is not working.
  This can happen if the version of Ruby that CocoaPods was installed with is different from the one being used to invoke it.
  This can usually be fixed by re-installing CocoaPods. For more info, see https://github.com/flutter/flutter/issues/14293.
To re-install:
  sudo gem install cocoapods

Exception: CocoaPods not installed or not in valid state.

flutter doctor
   Woah! You appear to be trying to run flutter as root.
   We strongly recommend running the flutter tool without superuser privileges.
  /
📎
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.18.0-5.0.pre.89, on Mac OS X 10.15.4 19E287, locale en-TN)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[!] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    ✗ CocoaPods installed but not working.
        You appear to have CocoaPods installed but it is not working.
        This can happen if the version of Ruby that CocoaPods was installed with is different from the one being used to invoke it.
        This can usually be fixed by re-installing CocoaPods. For more info, see https://github.com/flutter/flutter/issues/14293.
      To re-install CocoaPods, run:
        sudo gem install cocoapods
[✓] Android Studio (version 3.6)

Hi @medlmd
does the proposed command sudo gem install cocoapods help?

i have tried it but i get the some problem
On Fri, Apr 17, 2020 at 8:07 AM Vladyslav Bondarenko <
<EMAIL_ADDRESS>wrote:

Hi @medlmd https://github.com/medlmd
does the proposed command sudo gem install cocoapods help?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/54962#issuecomment-615081802,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMLM6VOQXORFD5GPNZW4V6TRM753ZANCNFSM4MJYDW3Q
.

sudo gem install cocoapods this worked for me. Although there were some issues (suggestions came up). Ran the following additionally (in same order):

sudo gem pristine ffi --version 1.12.2
sudo gem pristine executable-hooks --version 1.6.0
sudo gem pristine gem-wrappers --version 1.4.0
sudo gem regenerate_binstubs
sudo gem pristine --binstubs

Hope this helps!

@medlmd
could you check workarounds from https://github.com/flutter/flutter/issues/14293?

sudo gem install cocoapods this worked for me. Although there were some issues (suggestions came up). Ran the following additionally (in same order):

sudo gem pristine ffi --version 1.12.2
sudo gem pristine executable-hooks --version 1.6.0
sudo gem pristine gem-wrappers --version 1.4.0
sudo gem regenerate_binstubs
sudo gem pristine --binstubs

Hope this helps!
Hello, I get this
sudo gem pristine executable-hooks --version 1.6.0
ERROR:  While executing gem ... (Gem::Exception)
Failed to find gems ["executable-hooks"] = 1.6.0

@medlmd
doesn't it help https://github.com/flutter/flutter/issues/41291#issuecomment-535117317?
(you can try with 1.9.0 version)

the some probleme ☹
On Mon, Apr 20, 2020 at 2:30 PM Vladyslav Bondarenko <
<EMAIL_ADDRESS>wrote:

@medlmd https://github.com/medlmd
doesn't it help #41291 (comment)
https://github.com/flutter/flutter/issues/41291#issuecomment-535117317?
(you can try with 1.9.0 version)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/54962#issuecomment-616553904,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMLM6VMX7QIZPGPZW5ORMULRNRE57ANCNFSM4MJYDW3Q
.

Hi @medlmd
Does it happen after updating to newer master or Is it a fresh install?

Woah! You appear to be trying to run flutter as root.
We strongly recommend running the flutter tool without superuser privileges.

If CocoaPods pod is set up on your path as your user, and you're running as root, it's probably not on your root PATH.  As the warning says, don't sudo flutter.
See CocoaPods installation instructions.

What's the output of gem list pod without sudo?

Same issue. I upgraded to the latest stable version, I then ran the app in debug mode on a physical device (no issues), ran the app in release mode of a physical device (no issues), and then attempted to run the app in debug mode on an iOS simulator.

@jrnelson333 Can we get logs with the verbose -v flag?

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.

I'm encountering the same issue, with debug not running on the iOS simulator when flutter doctor checks out OK. If I find a solution I will post it here.
Error when running debug:
`Warning: CocoaPods not installed. Skipping pod install.
CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
Without CocoaPods, plugins will not work on iOS or macOS.
For more info, see https://flutter.dev/platform-plugins
To install:
sudo gem install cocoapods
CocoaPods not installed or not in valid state.`
Doctor output:
`▶ flutter doctor -v
[✓] Flutter (Channel stable, v1.17.1, on Mac OS X 10.15.5 19F96, locale en-US)
• Flutter version 1.17.1 at /Users/xxx/flutter
• Framework revision f7a6a7906b (2 weeks ago), 2020-05-12 18:39:00 -0700
• Engine revision 6bc433c6b6
• Dart version 2.8.2
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at /Users/xxx/Library/Android/sdk
• Platform android-29, build-tools 28.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.5, Build version 11E608c
• CocoaPods version 1.9.2
[✓] Android Studio (version 3.6)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 44.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
[✓] VS Code (version 1.45.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.10.2
[✓] Connected device (2 available)
• Nokia 2 2     • xxxxxxx                  • android-arm64 • Android 10 (API 29)
• iPhone 11 Pro • xxxxxx • ios           • com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)
• No issues found!`

Just did what the @oakmad said above and it worked. In my case, it was the Dart plugin for VS Code that was awaiting for a restart to update, so I had to close and reopen VS Code, got the "Dart Code has been updated to 'xxx'" and I was able to debug on my device properly.

Very weird. It even complains after I upgraded the cocoapods:

it turns out that my path has the wrong version of gems.

It was pointing to the 2.6.0 folder. After I switched to 2.7.0, problem solved.

simples answer is this , actually this solution worked for me to open terminal by going through View -> Terminal -> write this command "sudo gem install cocoapods". and thats it

Nothing helps for me. cocoapods already installed, gem in PATH and i still can't run my app and see this error. But all works OK just yesterday! 😭

I got the same issue running on Android Studio

Warning: CocoaPods not installed. Skipping pod install.
  CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
  Without CocoaPods, plugins will not work on iOS or macOS.
  For more info, see https://flutter.dev/platform-plugins
To install:
  sudo gem install cocoapods

CocoaPods not installed or not in valid state.
Error launching application on iPhone 11 Pro Max.

When i ran it directly from the terminal i got no issues, could be an android studio issue for me.

I was able to solve this error by: closing Visual Studio and restarting my computer.
After that it was solved for me

I was able to solve this by doing invalidate caches and restart on IntelliJ/ Android Studio

I'm in the exact same situation as @wizlif ...
@ThinkDigitalSoftware what do you mean by "invalidate caches"? flutter clean?

What ide do you use?

Android Studio

@ncuillery

I'm seeing the same issue as @wizlif
Android Studio is unable to find the cocoapods installation
[!] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install:
        sudo gem install cocoapods

But when flutter doctor -v is run on terminal, everything seems to be fine.
Invalidate Caches/Restart didn't help.

Try using flutter run outside Android Studio.

I was able to get it to work by opening Android Studio directly from the terminal.
$ open /Applications/Android\ Studio.app

This time it seemed to pick the $PATH variable properly and was able to find the cocoapods installation.

@ncuillery

That's worked!

I tried everything in this post but i still get the error:
✓] Flutter (Channel stable, 1.20.3, on Mac OS X 10.15.5 19F101, locale en-GR)
    • Flutter version 1.20.3 at /Users/mixalisdobekidis/SDK/flutter
    • Framework revision 216dee60c0 (6 days ago), 2020-09-01 12:24:47 -0700
    • Engine revision d1bc06f032
    • Dart version 2.9.2

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, set ANDROID_SDK_ROOT to that location.
      You may also want to add it to your PATH environment variable.

[✓] Xcode - develop for iOS and macOS (Xcode 11.7)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.7, Build version 11E801a
    • CocoaPods version 1.9.3

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] VS Code (version 1.48.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.14.1

[✓] Connected device (1 available)
    • 7L's iPhone (mobile) • 21a54e701c409f46af355cc927962aa6002a8798 • ios • iOS 13.6.1

! Doctor found issues in 2 categories.

when trying to compile for iOS I only get the error
Warning: CocoaPods not installed. Skipping pod install.
  CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
  Without CocoaPods, plugins will not work on iOS or macOS.
  For more info, see https://flutter.dev/platform-plugins
To install:
  sudo gem install cocoapods

Exception: CocoaPods not installed or not in valid state.

When I build the App from XCode directly it works fine.

ReInstalling the flutter extension on visual code fixed this

After longer investigation, I identified two error-causing points.
Firstly,
Changing linker flags in ios/Runner.xcodeproj/project.pbxproj .
In Xcode, navigate to Project Runner -> Build Settings -> Other Linker Flags & change all the blob that there with:
$(inherited)
-framework
Flutter

Secondly,
VS Code entry in my PATH variable was incorrect. After changing it accordingly to the documentation here he error was no longer present.

@AustrisC I'm sure the CocoaPods installation issue is with the PATH, not a missing linker flag.
You shouldn't need to add that flag manually, it's being inherited from Generated.xcconfig.
OTHER_LDFLAGS=$(inherited) -framework Flutter

Can you file a separate issue about that, completely fill out the template, and include your ios/Runner.xcodeproj/project.pbxproj? (unless you already know how your project was corrupted.

reinstall code to path for vscode, fixed for me: ref

Open the Command Palette (⇧⌘P) and type 'shell command' to find the Shell Command: Install 'code' command in PATH command.


Welcome view: Grammar

"set up" is the verb and "setup" is the noun :)
Happy new year 🥳

Oops ! Thanks for the fix ! And sorry for the late merge.

Oops ! Thanks for the fix ! And sorry for the late merge.


Niftymic killed with Docker image

Dear all,
Thank you for this great package.
When I run the niftymic_reconstruct_volume, the program is always “Killed”.
I have set the memory to the maximum memory（16G + 4G swap）, but still not enough. When the memory usage of container reaches 16G, the program will be "killed". I wonder how can I solve this problem?
`# niftymic_reconstruct_volume
--filenames /www/cor/T2_bias.nii.gz /www/sag/T2_bias.nii.gz /www/tra/T2_bias.nii.gz
--filenames-masks /www/cor/T2_label.nii.gz /www/sag/T2_label.nii.gz /www/tra/T2_label.nii.gz
--output /www/srr.nii.gz \

*** Configuration: ***
--- alpha: 0.015
--- alpha_first: 0.2
--- bias_field_correction: 0
--- boundary_stacks:
10
10
0
--- config: None
--- dilation_radius: 3
--- extra_frame_target: 10
--- filenames:
/www/cor/T2_bias.nii.gz
/www/sag/T2_bias.nii.gz
/www/tra/T2_bias.nii.gz
--- filenames_masks:
/www/cor/T2_label.nii.gz
/www/sag/T2_label.nii.gz
/www/tra/T2_label.nii.gz
--- intensity_correction: 1
--- interleave: 3
--- isotropic_resolution: 1
--- iter_max: 10
--- iter_max_first: 5
--- iterations: 15
--- log_config: 1
--- metric: Correlation
--- metric_radius: 10
--- multiresolution: 0
--- outlier_rejection: 1
--- output: /www/srr.nii.gz
--- reconstruction_type: TK1L2
--- reference: None
--- reference_mask: None
--- s2v_hierarchical: False
--- sda: False
--- search_angle: 45
--- shrink_factors:
3
2
1
--- sigma: 1
--- slice_thicknesses: None
--- smoothing_sigmas:
1.5
1
0
--- subfolder_motion_correction: motion_correction
--- suffix_mask: _mask
--- target_stack: None
--- threshold: 0.8
--- threshold_first: 0.5
--- transforms_history: 0
--- two_step_cycles: 3
--- use_masks_srr: 0
--- v2v_method: RegAladin
--- v2v_robust: False
--- verbose: 0
--- viewer: itksnap
--- write_motion_correction: 1
NiftyMIC version: 0.9

--- File written to '/www/config_reconstruct_volume_20220604-094944.json'.

*** Read Data ***
--- 3 input stacks read for further processing

*** Data Preprocessing ***
--- 3 stacks were loaded for data preprocessing
--- Crop stacks to their masks

*** Volume-to-Volume Registration ***
--- Volume-to-Volume Registration -- Stack 1/3
220604-09:50:09,211 nipype.interface WARNING:
version_from_command member of CommandLine was Deprecated in nipype-1.0.0 and deleted in 1.1.0
220604-09:50:09,343 nipype.interface WARNING:
version_from_command member of CommandLine was Deprecated in nipype-1.0.0 and deleted in 1.1.0
--- Volume-to-Volume Registration -- Stack 2/3
220604-09:50:47,548 nipype.interface WARNING:
version_from_command member of CommandLine was Deprecated in nipype-1.0.0 and deleted in 1.1.0
220604-09:50:47,655 nipype.interface WARNING:
version_from_command member of CommandLine was Deprecated in nipype-1.0.0 and deleted in 1.1.0
--- Volume-to-Volume Registration -- Stack 3/3
220604-09:51:32,424 nipype.interface WARNING:
version_from_command member of CommandLine was Deprecated in nipype-1.0.0 and deleted in 1.1.0
220604-09:51:32,529 nipype.interface WARNING:
version_from_command member of CommandLine was Deprecated in nipype-1.0.0 and deleted in 1.1.0

*** Intensity Correction ***
--- Stack 1 (T2_bias): Reference image. Skipped.
--- Stack 2 (T2_bias): Intensity Correction ... done (c1 = 0.908708)
--- Stack 3 (T2_bias): Intensity Correction ... done (c1 = 0.949986)

*** Reconstruction Space Generation ***
--- Isotropic reconstruction space with 1 mm resolution is created
--- Isotropic reconstruction space is centered around joint stack masks.

*** First Estimate of HR Volume ***
*** SDA Approximation Image ***
--- Chosen SDA approach: Shepard-YVV
--- Smoothing parameter sigma = [1. 1. 1.]
--- Stack 1/3
--- Stack 2/3
--- Stack 3/3
--- Required computational time: 0:00:19.953441
*** SDA Approximation Image Mask ***
--- Chosen SDA approach: Shepard-YVV
--- Smoothing parameter sigma = [1. 1. 1.]
 Besides having more RAM available, you could create tighter masks or lower the resolution, e.g. set --isotropic-resolution to 1.5 or 2 mm. Both will reduce the memory requirements. The latter of course will reduce image quality but could be a good first step to check that you can get successful recontructions

One thing though, Docker may have less memory available than what you have on your system. Perhaps worth checking as well.

Hello. The “killed” problem has been solved, it seems that the ARM64 system used by Apple M1 is not suitable for docker. So I switched to Windows.
However I also wonder if I need to download the images of ITK_Niftymic and Simplereg to use Niftymic?

Meanwhile, I‘m having troubles with “Transformation to Template Space”. It seems that the registration was not successful.

***************************************************************************************************
*** Read Data ***

***************************************************************************************************
*** Registration ***
--- Run Registration (RegAladin) ... done
--- Registration transformation written to '/www1/results/results-0.01-t/registration-transform.txt'

***************************************************************************************************
*** Update Motion-Correction Transformations ***
--- 0 transformations written to '/www1/results/results-0.01-t/motion_correction'

***************************************************************************************************
*** Summary ***
register_image | Computational Time: 0:00:15.605149

And here is the results of SRR, But I don‘t know what is the problem causing such strange results. Hope to get your help！！！

I met similar problem after SSRI. Did you solve this issue ?  Thanks.


Routing: when there are error in the path, show warning in routing

When there are error in the path (could no generate path at gtfs import), show a warning (right now it shows -1 as distance)

@kaligrafy , should we fix the data when we import it ? We could calculate the actual distance with the data we have

We should just choose a random direction for the problematic path:
Here the node in the loop: we cannot know if the bus will stop before or after the loop, thus the ambiguity. We could just force one of the direcfiton, like the first (before the loop)


Small glitch in the code ?

Hi,
Thanks a lot for your scripts, they are awesome !
I have just noticed a small parse error while running it, I am sharing it with you.
`root@nas:/volume1/script# ./syno_hdd_db.sh -nr  --showedits
Synology_HDD_db v3.3.75
DS220+ DSM 7.2.1-69057-3
StorageManager 1.0.0-0017
Using options: -nr --showedits
Running from: /volume1/script/syno_hdd_db.sh
HDD/SSD models found: 1
WD160EDGZ-11B2DA0,85.00A85
No M.2 drives found
No M.2 PCIe cards found
No Expansion Units found
WD160EDGZ-11B2DA0 already exists in ds220+_host_v7.db
Support disk compatibility already enabled.
Support memory compatibility already disabled.
Max memory already set to 18 GB.
Drive db auto updates already disabled.
parse error: Expected value before ',' at line 1, column 96319
DSM successfully checked disk compatibility.
You may need to reboot the Synology to see the changes.
`

I suspect if you run it again with --showedits it will show the same error.
And if you run it again without --showedits it won't show the same error.
Does the following command give the same error?
jq . ds220+_host_v7.db | grep -A 11 WD160EDGZ-11B2DA0

If it does give the same error can you attach a zipped copy of your ds220+_host_v7.db file.
You can copy the file to the script shared folder with:
sudo cp /var/lib/disk-compatibility/ds220+_host_v7.db /volume1/script/ds220+_host_v7.db

I've encountered a similar error. It only happens when running with --showedits.

I suspect if you run it again with --showedits it will show the same error.
Yes
And if you run it without --showedits it won't show the error.
Exact
Does the following command give the same error?
jq . ds220+_host_v7.db | grep -A 11 WD160EDGZ-11B2DA0

root@nas:/volume1/scripts# jq . ds220+_host_v7.db | grep -A 11 WD160EDGZ-11B2DA0 parse error: Expected value before ',' at line 1, column 96319
Exact same error

If it does give the same error can you attach a zipped copy of your ds220+_host_v7.db file.
You can copy the file to the script shared folder with:
sudo cp /var/lib/disk-compatibility/ds220+_host_v7.db /volume1/script/ds220+_host_v7.db

You can find the .db file here : https://transfert.free.fr/j2sMvwz
Thanks !

Ok, I've found the issue. My script has added an extra comma so the file ends in ,,"nas_model":"ds220+"} when it should end in ,"nas_model":"ds220+"}
I'll update the script to prevent that, and fix it in the db file for people who've already run Synology_HDD_db v3.3.75

This new version v3.4.76 should work correctly with the -s or --showedits option. It also edits the ,db files to fix the ,, left from v3.3.75
https://github.com/007revad/Synology_HDD_db/releases/tag/v3.4.76

I think there's still a problem with the sed command :
`root@nas:/volume1/scripts# ./syno_hdd_db.sh -nr  --showedits
Synology_HDD_db v3.4.76
DS220+ DSM 7.2.1-69057-3
StorageManager 1.0.0-0017
Using options: -nr --showedits
Running from: /volume1/scripts/syno_hdd_db.sh
HDD/SSD models found: 1
WD160EDGZ-11B2DA0,85.00A85
No M.2 drives found
No M.2 PCIe cards found
No Expansion Units found
sed: no input files
WD160EDGZ-11B2DA0 already exists in ds220+_host_v7.db
Support disk compatibility already enabled.
Support memory compatibility already disabled.
Max memory already set to 18 GB.
Drive db auto updates already disabled.
parse error: Expected value before ',' at line 1, column 96319
DSM successfully checked disk compatibility.
You may need to reboot the Synology to see the changes.
`

I guess it helps if I tell sed which files to edit :(
All fixed now: https://github.com/007revad/Synology_HDD_db/releases/tag/v3.4.77

It definitely helps ;)
Thanks for the support and reactiveness !
bash-4.4# ./syno_hdd_db.sh -nr --showedits
Synology_HDD_db v3.4.77
DS220+ DSM 7.2.1-69057-3
StorageManager 1.0.0-0017

Using options: -nr --showedits
Running from: /volume1/scripts/syno_hdd_db.sh

HDD/SSD models found: 1
WD160EDGZ-11B2DA0,85.00A85

No M.2 drives found

No M.2 PCIe cards found

No Expansion Units found

WD160EDGZ-11B2DA0 already exists in ds220+_host_v7.db

Support disk compatibility already enabled.

Support memory compatibility already disabled.

Max memory already set to 18 GB.

Drive db auto updates already disabled.

    "WD160EDGZ-11B2DA0": {
      "85.00A85": {
        "compatibility_interval": [
          {
            "compatibility": "support",
            "not_yet_rolling_status": "support",
            "fw_dsm_update_status_notify": false,
            "barebone_installable": true,
            "smart_test_ignore": false,
            "smart_attr_ignore": false
          }
        ]

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.


feat: add effectOnceIf helper function

I'd like to propose this helper function, I'm open to implementing improvements and making changes as needed 🙌
I'm not sure about the name, so suggestions are appreciated 🤔
effectOnceIf
It is an helper function that allows you to create an effect that will be executed only once if a certain condition occurs.
Usage
@Component({})
class Example {
  count = signal(0);

  effectOnceIfRef = effectOnceIf(
    // condition function: if it returns a truly value, the execution function will run
    () => this.count() > 3,
    // execution function: will run only once
    (valueReturnedFromCondition, onCleanup) => {
        console.log(`triggered with value returned: ${valueReturnedFromCondition}`);
        onCleanup(() => console.log('cleanup'));
    });
}

// example.count.set(1);
//    -> nothing happens
// example.count.set(4);
//    -> log: triggered with value returned: true
//    -> log: cleanup
// example.count.set(6);
//    -> nothing happens

Hello @lorenzodianni
I wanted to know more about the use cases that this solves.

Hi @eneajaho,
Suppose we have a task management application where each task has a progress state that ranges from 0% to 100%. We want to trigger an alert (e.g., display a notification or log a message) when a task's progress exceeds 75% for the first time. Once this alert is triggered, it should not trigger again, even if the task's progress continues to increase.
@Component({})
class TaskProgress {
  // Declare a signal for the task's progress
  progress = signal(0);

  // Use effectOnceIf to trigger an alert when progress exceeds 75%
  effectOnceIfRef = effectOnceIf(
    // Condition: if progress exceeds 75%
    () => this.progress() > 75,
    // Execution function: triggers the alert once
    (valueReturnedFromCondition, onCleanup) => {
      console.log(`Alert: Progress has exceeded 75%! Current value: ${this.progress()}%`);
      onCleanup(() => console.log('Cleanup after alert'));
    });
}

// Update the task's progress
taskProgress.progress.set(50);
//    -> nothing happens
taskProgress.progress.set(80);
//    -> log: Alert: Progress has exceeded 75%! Current value: 80%
//    -> log: Cleanup after alert
taskProgress.progress.set(90);
//    -> nothing happens

Perhaps @lorenzodianni has other use cases.

Hi @eneajaho
I frequently use it for initializing data or libraries, DOM manipulation, or any tasks that need to be executed only once:

Initialize the library when the DOM is available.
Initialize the library when the DOM enters the viewport (using the Intersection Observer).
Invoke an API that should be called once (e.g., navigator.getCurrentPosition).

Here are some real use cases:
effectOnceIf(
  () => this.mapRenderer.isMapReady() ? this.markers() : false,
  (markers) => this.mapRenderer.addMarkers(markers),
);

effectOnceIf(
  () => {
    const myDomEl = this.myDomEl();
    return myDomEl && this.canInitializeMyDomLib() ? myDomEl : false;
  },
  (element) => {
    new MyDomLib(element, {...});
  },
);

effectOnceIf(
  () => this.userHasAcceptedGeolocationPermissions() ? this.getCurrentPosition() : false,
  (position) => this.mapRenderer.centerMap(position),
);

And of course, the use case mentioned by @nemu69 could be another one

I think for most cases it might make sense to use a computed signal as the predicate, and a normal effect to run the side effect, e.g:
countGreaterThanThree = computed(() => this.count() > 3);

effect(() => {
  if(this.countGreaterThanThree()){
    // do whatever
  }
})

But I can see the use case where you wouldn't want the effect to run again for situations where the predicate could potentially switch back to being false and then true again.
Perhaps an alternative to consider would be some sort of "trigger" or "tripwire" signal that, once it becomes true, its value can not be changed anymore, e.g something like:
countGreaterThanThree = computedUntilTrue(() => this.count() > 3);

effect(() => {
  if(this.countGreaterThanThree()){
    // do whatever
  }
});

At least to me an API like this feels more idiomatic.


Icons are not displayed with IE9

This was reported by two members on my team, I could not test it myself but the bottom line seems to be that on IE9 icons do not show. On IE8 and in other browsers things work fine.
We use jQuery 1.6.2 and have the latest version from the pre-1.0 branch. We use the type plugin to have custom icons displayed.

Apparently IE9 does not like setting the background-position property after you've set the background-url property.  I was able to hack around this issue by changing this line:
if(tp.icon.image)	{ icons_css += ' background-image:url(' + tp.icon.image + '); '; }
to this:
if(tp.icon.image)	{ icons_css += ' background:url(' + tp.icon.image + ') top left no-repeat; '; }
Of course, I believe this would render the following line useless (in IE9 at least), but for my purposes, it works because the background position for in image in my case should always be top left.


aspnet 5 dnx beta7 app fails on Azure Web Site

I have recently upgrade my beta 6 site to beta 7 and it broke my azure web site. it is currently showing a 500 and I can't seem to find the root cause of it.
I can reproduce the error when pushing the master of this repository https://github.com/hoetz/3dshootercom to a fresh Azure Web Site.
The site is hosted here: http://3dshootercom.azurewebsites.net.

Update: After deploying for the n-th time with Visual Studio I now have a working site but as soon as I deploy via git it breaks again. I am copying all the files via ftp from the azure web app and will look for any differences. This is really strange.

I just tried creating a new beta 7 MVC app using latest VS tooling, and the result does appear to work well via git publishing to a Web App. Here is my repo: https://github.com/davidebbo-test/AspNet5Beta7.
But clearly, error handling needs improvement when things go wrong with aspnet 5!

I can now confirm: current master branch of my repo works when published with VS. When pushed to master and after triggering the git CI build, it is broken again with a 500. I copied the entire directory via ftp and there doesn't seem to be a difference. Strange!

@davidfowl or @DamianEdwards: any idea how to debug a 500 (smiley oops type) in an aspnet 5 Web App? As far as I can tell, there is no log file at all getting created.

Apparently there is an AppSetting Key ASPNET_DETAILED_ERRORS. When set to true in the root web.config it's supposed to display detailed errors. Will check this out later. Thanks to @ahmelsayed for pointing this out.

My site seems to be working now even after the git CI build. Turns out Visual Studio added a global.json in the src Folder of the Web project and this caused some trouble.

Maybe this issue? https://github.com/aspnet/dnx/issues/2656

Exactly!

@davidebbo To check detailed error 500s I manually add the  node (through Kudu) to the auto-generated web.config file that Kudu creates when running the deployment script.

@ealsur yep, that's seems to be what works. Doing it via Azure App Setting does not work. Anyway, the dnx team says they'll improve error handling soon :)


Refactoring models to follow DRY principle

Is your feature request related to a problem? Please describe.
No, i just saw different model class having the same attribute

created = models.DateTimeFied(...)

Describe the solution you'd like
Can't we move the similar attribute in this case

created = models.DateTimeField(...)

to a separate class and make other class that needs created to inherit from the class?

Describe alternatives you've considered
class DateTimeModel(models.Model):
    created = models.DateTimeField(...)

    class Meta:
        abstract = True

class AnotherModel(DateTimeModel):
    ...

how can I take this issue, I want to collaborate.

Thank you for your suggestion @sulavmhrzn , i will assign this to you soon @FredyChivalan .

@PraveenMalethia if  this is not started I can pick this up. Thanks!

@PraveenMalethia  pls assign this to me.


fix(table): i18n labels weren't being passed down properly

Summary

Fix to pass the i18n labels all the way down to the RowActionsCell
docs(table): add additional documentation for the RowActions usage

Change List (commits, features, bugs, etc)

just need to pass the labels all the way down from the Table to the RowCell so that consuming components can translate their own labels.

Acceptance Test (how to verify the PR)

Verify the i18n story shows all the labels

:tada: This PR is included in version 1.48.1 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


add google as external storage for msq export

Description
Support for exporting msq results to gcs bucket. This is essentially copying the logic of s3 export for gs, originally done by @adarshsanjeev in this PR - https://github.com/apache/druid/pull/15689

Release note
Support for exporting MSQ results to a GCS path.

Key changed/added classes in this PR

GoogleExportStorageProvider.java
GoogleStorageConnectorModule.java

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[x] added documentation for new or modified features or behaviors.
[x] a release note entry in the PR description.
[x] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

Thanks for the PR! I'll take a look at it shortly.

Some minor copyedit nits. The only absolutely must fix one is the incorrect cloud provider being listed in an intro sentence

thanks @317brian added your commits

@adarshsanjeev anything else ?

@adarshsanjeev yes tested on a cluster

@adarshsanjeev - If its looks good to you, can we merge this?

Yes, the changes look good to me! Thanks for the PR!


Update deps & general cleanup!

Hi! Firstly, this project is insanely cool, so I wanted to just clean up the code a little and update the dependencies. I've tested it and everything works as it did before. As I have seen from the files present this seems to be some sort of academic research project, so I didn't want to interfere much, as that could cause issues for you, so I just decided to do a little cleanup without changing any real functionality. You may notice that debug messages are gone, and that's because it uses the tracing crate now, and to see them you can just run it with the environment variable RUST_LOG=debug. I hope you like it! :)

Hello, wow thats a lot of modifications! First of all, thank you very much for your interest and time :DD! I'll get back to this project in the coming weeks, this will be my thesis for BSc (bachelor's) :DD. For this semester one of my goals is to clean up the code and make it more understandable, as well as easier to use (configuring it with commandline arguments), and make it work for a wider range of songs (next to writing like 40 pages about it xd). While I'm not sure It'll be easier for me to continue from your modifications compared to my admittedly pretty messy one I left from last semester, I'll look at your modifications closely, and will probably continue from that (the tracing crate sounds pretty useful e.g. :D).

Hii, thank you again and sorry for the long delay! I was thinking a lot about merging it, but the biggest problem is personal preference, I feel like I can read concise/compact code better, so I don't really like that the autoformatter splits 1 semi-long line into 5-6 lines. However if multiple people are working on code then ofc it has a lot of benefits. But mostly I will be working on this and I feel like it's better if I leave it like it was, at least in this regard. But thank you very much and I'll be using parts of the code to improve the project :DDD, e.g. I'll start by updating the dependencies

No problem! Good luck!

Hello, thanks again! I did a bigger cleanup today and also used your modifications for e.g. the tracing logger :D
now the code is much slower, but much more precise (at least when used with songs exported with nbswave), sadly we lost some generality, but this will mostly be my final version for some time. Now it uses the derivative for the minimum search as well.
if you'd like to touch the code / modify it further, let me know, I'd be glad to help! I can't promise anything as I'm not that active on GitHub, but It'd be awesome seeing the project continue!

Yeah! This project is awesome and super cool and I'll probably parallelize some of it with rayon to make it faster.

Nicee :DD! I also tried doing that and it worked great (there is still a comment in main.rs), however now it's using the previously recognized note's decay to make the next recognition better, so in this regard we lost the ability to run them in parellel - at least as a straightforward modification, but ofc I'm sure there could be some way :D, e.g. by splitting the music into 4 equal parts and starting recognition from 4 points moving forward - or by replacing the previously recognized note's decay with something else.


TILA-2255 | Check reservation time to current time not reservation begin

Change log

Reservation validation check_reservation_time fix and enchancement

Other notes
The check reservation_time checker compared reservation begin time to reservation_begins and *_ends rather it should compare against current_time in the making of the reservation.
Also adds checking current time against publish_ends and begins samely as reservation_begins
Refs TILA-2255

I just remembered that you are not working today, so I'll merge this so that we'll get this fix in test ☺


Marker popups do no show for ipyleaflet maps

shinywidgets version: 0.2.1
Python version: 3.11.1
Operating System: macOS 13.4.1

Description
When I include a marker.popup the marker does not show up.
ipyleaflet==0.17.3
ipywidgets==8.0.6
shiny==0.4.0
shinyswatch==0.2.4
shinywidgets==0.2.1

What I Did
With a popup, the marker not render:
import ipyleaflet as L
from ipywidgets import HTML
from shiny import App, reactive, render, ui
from shinywidgets import output_widget, reactive_read, register_widget

app_ui = ui.page_fluid(
    output_widget("map"),
)

def server(input, output, session):
    # Initialize and display when the session starts (1)
    map = L.Map(center=(51.476852, -0.000500), zoom=12, scroll_wheel_zoom=True)

    # Add a marker with a popup
    marker = L.Marker(location=(51.476852, -0.000500), draggable=False)

    # Add a popup
    msg = HTML()
    msg.value = "Hello World"
    msg.placeholder = "Some HTML"
    msg.description = "Some HTML"
    marker.popup = msg

    # Add the layer
    map.add_layer(marker)

    # Register map
    register_widget("map", map)

app = App(app_ui, server)

With no popup, the map renders as expected:
import ipyleaflet as L
from ipywidgets import HTML
from shiny import App, reactive, render, ui
from shinywidgets import output_widget, reactive_read, register_widget

app_ui = ui.page_fluid(
    output_widget("map"),
)

def server(input, output, session):
    # Initialize and display when the session starts (1)
    map = L.Map(center=(51.476852, -0.000500), zoom=12, scroll_wheel_zoom=True)

    # Add a marker with a popup
    marker = L.Marker(location=(51.476852, -0.000500), draggable=False)

    # Add the layer
    map.add_layer(marker)

    # Register map
    register_widget("map", map)

app = App(app_ui, server)

Other info

Map example in shiny docs: https://shinylive.io/py/examples/#map
Popup example in ipyleaflet docs: https://ipyleaflet.readthedocs.io/en/latest/layers/popup.html

I'm able to run the popup example successfully with ipywidgets 7.6.5 and ipyleaflet 0.17.3. I think perhaps, something with ipywidgets >8 broke popups? https://github.com/jupyter-widgets/ipyleaflet/issues/1081
Anyway, it'd also be interesting to know if, with this same environment, whether popups work for you in a Jupyter notebook

I am able to render it successfully in JupyterLab:
import ipyleaflet as L
from ipywidgets import HTML

map = L.Map(center=(51.476852, -0.000500), zoom=12, scroll_wheel_zoom=True)

# Add a marker with a popup
marker = L.Marker(location=(51.476852, -0.000500), draggable=False)

# Add a popup
msg = HTML()
msg.value = "Hello World"
msg.placeholder = "Some HTML"
msg.description = "Some HTML"
marker.popup = msg

# Add the layer
map.add_layer(marker)

map

I was able to get my shiny for python app working with the following requirements:
shiny==0.4.0
ipywidgets==7.7.5
shinywidgets==0.2.1
ipyleaflet==0.17.3
shinyswatch==0.2.4
pins==0.8.1
pandas==1.5.3
pyarrow==12.0.1
rich==13.4.2

I am assuming that something broke in ipywidgets >= 8.0.0

The strange thing for me is that it works in jupyter/quarto, but not in Shiny. However, downgrading to a ipywidgets version < 8 solved it for me as well.

I can confirm that popups no longer work with shinywidgets and ipywidgets>=8.0.0. If I use map.add(popup) to directly add the popup to the map, I get the following client-side error:
Class HTMLStyleModel not found in module<EMAIL_ADDRESS>
I'm pretty sure that we need to update the version of @jupyter-widgets/html-manager that we use in shinywidgets https://github.com/posit-dev/py-shinywidgets/blob/d4e0f7c3066356bfd51e0174f67bb20b51ecbb57/js/package.json#L18
but this will require code changes in shinywidgets.
For now, I can get away with settings ipywidgets<8.0.0 in my requirements.txt, but this doesn't work on shinylive.
from shiny.express import input, render, ui
from shinywidgets import render_widget
from ipyleaflet import Map, Marker, Popup
from ipywidgets import HTML

@render_widget
def map():
    map = Map(center=(50.6252978589571, 0.34580993652344), zoom=3)
    popup = Popup(child=HTML(value="hello"))
    point = Marker(location=(52.204793, 0.121558), draggable=False)
    map.add(point)
    map.add(popup)

    return map

@cpsievert Here's an ipynb version of the above example where popups work as expected: https://gist.github.com/gadenbuie/621159ebb65c6bede63a66132a38b88e

Thanks for this, it is very helpful. I understand that the current setup does not work on Shinylive. Are there any guidance or recommendations to make it work on Shinylive? It would be greatly appreciated.


FW-703. Implement cryptoengine for iotlab-m3 nodes.

This PR adds support for CCM at iotlab-m3 nodes and their derivatives. It implements the CCM using hardware acceleration available in the AT86RF231 chip. While the CCM implementation passes all the unit tests available, its performance is bad due to the SPI transfer. For CCM to complete on a 127-byte frame, it takes ~5ms, making it impossible to use it for link-layer security processing.
The provided CCM implementation enables the secure join protocol to complete, so it is therefore deemed useful.

Another PR, part of an epic, has been opened:
https://github.com/openwsn-berkeley/openwsn-fw/pull/470
making this PR obsolete.


Photo Messages reloading and flickering each time a new message is sent

Hi, I've been working on a communicator app using Chatto, and I came across an issue with reloading images. If there are some Photo Messages present in the chat, and I send a new message (eg. text, the type makes no difference), all images are getting reloaded. Is this expected behaviour? I noticed that the same thing happens in your ChattoApp example, and it's not very visually appealing.
Chatto version: 3.5.0
Xcode version: 11.1

@rafrybakowski Please, check this: #610


Fix delete fork button for merged PRs

This fixes #298.
I changed the method of making the fork path to use existing methods for grabbing the username and repoName. It seems like this is appropriate for creating the path to the settings for the fork, and the existing tests (not the original repo, is merged, etc.) remained intact.

@hkdobrev better as "Fix delete fork button for merged PRs"?

@paulmolluzzo I meant the PR description body, not the title, but in any case, this PR is good to merge 😺


2 new functions, updates for sbtools

sbtools-relevant updates were all to change 'id' to 'sb_id' as the argument to a function. roxygen2 update really just affects the header that's automatically created in each .Rd file. new functions are search_sites and search_metab_models.

Same old appveyor build problem (403: forbidden error on install_github). I think the solution involves setting a GitHub personal access token (https://help.github.com/articles/creating-an-access-token-for-command-line-use/, auth_token in http://www.inside-r.org/packages/cran/devtools/docs/install_github, env var GITHUB_PAT in http://www.inside-r.org/packages/cran/devtools/docs/github_pat) so that GitHub knows it's us and that we're not abusing the API with too many calls. I will talk to some password experts soon.
In the meantime, this builds correctly on my Windows computer (with cutting-edge sbtools).


Gitea shared service supports app-service standard SKUs

What is being addressed
Gitea shared service didn't supprort standard SKUs
How is this addressed

Set diagnostic options according to what's available in the plan (as we do elsewhere)
Upgrade AzureRM
Upgrade resources to non-deprecated ones

/test-shared-services

/test-shared-services


Manually handling sending of crashes

Not sure if this is wanted or not, but we had a requirement that if the app crashed and the user has the analytics turned off, on the next launch, it would pop up saying the app crashed last time and then ask them if they want to enable analytics and send the report -

To achieve this I added 3 new methods, so I can manually handle the sending of the crashes -

bool HasCrashed();
Task SendCrashes();
void ResetCrashes();

And added 1 new property to handle the writing/ sending of the crashes -

bool WriteCrashes
- This can be defaulted to true to prevent a breaking change
bool HandleCrashes
- For some reason, I renamed IsTrackCrashesEnabled to HandleCrashes. This can be reverted to prevent a breaking change

What this allows me to do is have HandleCrashes (IsTrackCrashesEnabled) always set to try regardless of the users settings. So that all crashes get written to a file. And have WriteCrashes set too false, and have my own logic to send the crashes

As long as the stuff mentioned above is done, there aren't any breaking changes.

I really like this! I added two comments on your comment.
Can you rebase against the latest code in main and make sure it works with that one too? It should, because GitHub says it can merge, but it would be great if you can to it to verify that it works as it should.


Fix issue #32 with regenerator-runtime/runtime import

Fix issue NodeJS cannot find module regenerator-runtime/runtime #32

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

Is this project abandoned? Pyroscope remains broken for Node projects using ESM.

FYI after the big recent refactor, this now requires all relative paths (there are many more now) to end in .js.

Now that #89 is merged, this is obsolete.

Closing because of https://github.com/grafana/pyroscope-nodejs/pull/89 getting merged.


Fixes #121 Added Ask.com support

#148

[x] Added Ask.com feature
[x] Added Ask.com icon
[x]  Worked on Python 3 compatibility

@mariobehling Please review


Add a "Time Requested" Column

It will be great to have the "Time Requested" column to better analyze the requests.

I agree this is important feature. It will also allow testing for all time based attacks.
Thanks.


feat(tui): improve white theme support

Description of change
Now we check the background color of the terminal and use a more fitting color for text. (e.g. white text on a black background)
Closes #8
How has this been tested? (if applicable)
Locally, with different themes.

100ms timeout seems a bit high - I need to make it run in a thread via message passing.

Found another library which might be more suitable for this: https://github.com/Canop/terminal-light

100ms timeout seems a bit high - I need to make it run in a thread via message passing.

Turns out this is not going to work since we can't query the terminal background color correctly while the terminal events are being read at the same time.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 106 lines in your changes missing coverage. Please review.

Project coverage is 3.55%. Comparing base (29d88dc) to head (52f7ced).

Files with missing lines
Patch %
Lines

src/tui/ui.rs
0.00%
99 Missing :warning:

src/tui/state.rs
0.00%
7 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##            main     #23      +/-   ##
========================================
- Coverage   3.67%   3.55%   -0.11%
========================================
  Files         18      18
  Lines       2212    2286      +74
========================================
  Hits          81      81
- Misses      2131    2205      +74

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


Toggle maximized panel no longer maximizes the panel

https://github.com/Microsoft/vscode/issues/2806 changes maximize panel to switch sides, I rely pretty heavily on maximizing the panel (and so does @suciuvlad who called it out in https://github.com/Microsoft/vscode/issues/36903#issuecomment-339701061) and it is certainly not equivalent to switching the panel's orientation.

Even if the button was gone but the command remained that would be fine by me. I use ctrl+shift+q to maximize the terminal.

Fixed in latest insiders

Thanks!

@isidorn thanks for the quick turnaround! By the way I'm for removing the minimize/maximize button on the panel, just as long as the command is retained.


Add functionality to return multiple full names

Should be able to return multiple full names of metrics if sc_fullname() code modified to:
result <- resp[resp$dictionary.metric_prefix %in% unlist(strsplit(metric, split = ',')), 1]
or
result <- data.frame(metric_name = resp[resp$dictionary.metric_prefix %in% unlist(strsplit(metric, split = ',')), 1])

Closed and resolved in #42


1.28 + left nav button fix

gonna need some stuff updated, bucko
specifically BSML to 0.3.1 and Lapiz to 0.1.11


feat(AST parser): add remaining CLI commands + smoke tests

This PR is fairly big, but most of it is tests. 🙂
Reviewers: LMK if you'd like me to split the tests up further + merge some of that in a later PR. Thanks!

Related: we should consider replacing the manual-string-crafting in cli_yaml.py with a set of defined error classes (perhaps subclasses of some YamlValidationError type) for both code cleanliness and consistency with the approach used in this PR.
@tmatsuo @martinvarelaj LMK if you agree, and I'll file an issue to track that work. 🙂


[utils-42] Upgrading to the org.apache.parquet release of Parquet.

Necessary for https://github.com/bigdatagenomics/adam/issues/716.

Merged build triggered.

Merged build started.

Merged build finished. Test PASSed.


add My21 palisade fw fp

Tested on 2021 Hyundai palisade 2021 Limited - Hyundai Harness H used - Worked flawlessly with no errors while building

Can you post a route from this car?


Stepper Motors

Hi there - I am really sorry for being a pain in asking silly questions. I fully understand that this project is about 3-4 years old now, and i think it is the most amazing project to complete ever, and thank you so much for supplying so much information without charge, and letting it be open source.
I am having trouble finding the correct stepper motors. Can someone please point me in the correct direction?
Many thanks, Rob

You can find all of the Stepper Motors except the Nema 23.
Use this one instead "Nema 23 stepper 3Nm 4,2A 10mm shaft"

Hi there - Its all resolved now, and the robotic arm is almost fully assembled with the exception of sorting out the wiring - Thank you

Hi man, I want to know who you are?
On Wed, 7 Apr 2021, 17:00 robertall33, @.***> wrote:

Hi there - Its all resolved now, and the robotic arm is almost fully
assembled with the exception of sorting out the wiring - Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BCN3D/BCN3D-Moveo/issues/42#issuecomment-814837807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APFWUVZHOCCFGPWYRWC4G3LTHQ67HANCNFSM4TBGGXEQ
.

@robertall33 I could help you if you want.


add change style of menu and item buttons

Sorry I haven't written any documentation for this yet, but I have added recently the ability to add these props to the FloatingItem config objects:
  style,
  containerStyle,
  labelStyle,
  buttonStyle,
  buttonInnerStyle,

and these are available on the FloatingMenu element:
  buttonOuterStyle,
  buttonTouchableStyle,
  buttonInnerStyle,
  dimmerStyle,

I will close for now, please reopen if it doesn't help what you need


toUint24 removed?

Why was the "toUint24" method removed?
Here is the rather simple code to implement it:
function toUint24(bytes memory _bytes, uint256 _start) internal pure returns (uint24) {
        require(_bytes.length >= _start + 3, "toUint24_outOfBounds");
        uint24 tempUint;

        assembly {
            tempUint := mload(add(add(_bytes, 0x3), _start))
        }

        return tempUint;
}

The function toUint24 is needed sometimes.

nice


[macos] Wait more during workflow retrieval step

What does this PR do?

Increases the number of retries in the macOS GitHub Actions workflow retrieval step, to retry up to 5 minutes.
Motivation

Prevent flakiness in macOS jobs.
Additional Notes

n/a
Possible Drawbacks / Trade-offs

n/a
Describe how to test/QA your changes

n/a

/merge


[zh] Translate common-definitions/list-meta page into Chinese

Fixes: https://github.com/kubernetes/website/issues/32247
Do not have chinese docs: https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/list-meta/
so need to translate common-definitions/list-meta page into Chinese

I have modified all comments. Thanks for review.

/approve

/label tide/merge-method-squash

/assign @ydFu

Please use rebase to squash commits into only one commit.

I have rebased it. Thanks for your review.

/lgtm
Thank for your contribution.


Updated samples props to target .NET 7.0

Description
Changed target of samples to .NET 7.0
Reviewer Checklist

[x] Update the title of the PR to be succinct and less than 50 characters
[x] Tag the PR with the type of update: Bug, New-Sample, Enhancement, or New-Feature
[ ] CI is green before merge

/azp run

/azp run

/azp run

/azp run

/azp help

/azp list

/azp run Azure Health DataServices Toolkit PR, CI, and Release