Uncaught TypeError: Invalid Point: (133, NaN)

[Enter steps to reproduce:]

...
...

Atom: 1.39.1 x64
Electron: 3.1.10
OS: Mac OS X 10.13.6
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Invalid Point: (133, NaN)
At /Applications/Atom.app/Contents/Resources/app/static/<embedded>:11

TypeError: Invalid Point: (133, NaN)
    at Function.Point.assertValid (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:48794)
    at DisplayLayer.translateScreenPosition (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:89900)
    at DisplayMarkerLayer.translateScreenPosition (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:1187509)
    at DisplayMarker.setHeadScreenPosition (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:2807483)
    at changePosition (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:521252)
    at Cursor.changePosition (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:529796)
    at Cursor.setScreenPosition (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:521218)
    at Cursor.moveLeft (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:524040)
    at modifySelection (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:533852)
    at Selection.modifySelection (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:546998)
    at Selection.selectLeft (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:533820)
    at Selection.backspace (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:538344)
    at mutateSelectedText.t (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:16061)
    at getSelectionsOrderedByBufferPosition.map (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:16220)
    at Array.map (<anonymous>)
    at transact (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:16209)
    at TextBuffer.transact (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:491299)
    at TextEditor.transact (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:24215)
    at mergeIntersectingSelections (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:16150)
    at TextEditor.mergeSelections (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:39484)
    at TextEditor.mergeIntersectingSelections (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:39038)
    at TextEditor.mutateSelectedText (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:16113)
    at TextEditor.backspace (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:16037)
    at TextEditor.e.(anonymous function) [as backspace] (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:257668)
    at TextEditor.core:backspace (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:300877)
    at /Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:306618
    at TextBuffer.transact (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:491299)
    at TextEditor.transact (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:24215)
    at HTMLElement.s.(anonymous function) (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:306561)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:348736)

Commands
     -1:01.1.0 editor:newline (input.hidden-input)
     -1:00.8.0 core:move-up (input.hidden-input)
     -1:00.6.0 core:paste (input.hidden-input)
     -0:59.7.0 snippets:next-tab-stop (input.hidden-input)
     -0:59.7.0 snippets:expand (input.hidden-input)
     -0:59.7.0 editor:indent (input.hidden-input)
     -0:59.2.0 core:undo (input.hidden-input)
     -0:58.7.0 editor:move-to-first-character-of-line (input.hidden-input)
     -0:58.1.0 snippets:next-tab-stop (input.hidden-input)
     -0:58.1.0 snippets:expand (input.hidden-input)
     -0:58.1.0 editor:indent (input.hidden-input)
     -0:57.7.0 core:save (input.hidden-input)
  3x -0:16.7.0 core:backspace (input.hidden-input)
     -0:09.0 core:save (input.hidden-input)
     -0:04.4.0 core:move-down (input.hidden-input)
  5x -0:03.9.0 core:backspace (input.hidden-input)

Non-Core Packages
atom-html-preview 0.2.6
auto-encoding 0.7.1
japanese-menu 1.14.0
textile-preview 0.1.2

Thanks for contributing!
We noticed that this looks like a duplicate of https://github.com/atom/atom/issues/19114 so you can subscribe there for updates if you'd like.   If you have repro steps or other information to share, please let us know in https://github.com/atom/atom/issues/19114.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Add e2e example with pack-based (2k,2k,2k) GEMM

Can you add e2e tests in addition to examples since we don't regress examples?  Tests can be tested, examples rot.

Can you add e2e tests in addition to examples since we don't regress examples? Tests can be tested, examples rot.

Great point - PR created. The test may be a bit slow.


[PE-D][Tester D] Programme's internal management of state is buggy

I was in the Course Page but the programme thought I was still in the Student Page.

observe the add course command returns an error in above screenshot

observe the help command returns the help info for Student page.

This bug occurred while I was testing the find course command on the Course Page.

Labels: type.FunctionalityBug severity.High
original: unfazing/ped#8

I'm unable to reproduce this bug, can anyone try it?

I'm unable to reproduce it too. I've implemented

If it's not a UI issue but rather a logical issue, then will have to dig where page CurrentSelection.currentPage is not being updated correctly.

Seems like this was fixed #215 , close it for now.


Accessibility with Tabs

Specs
Browser: Chrome v. 45, Firefox v. 40, IE 11 (essentially every browser we've tried)
Foundation: 5.5.2
Related Ticket: https://github.com/zurb/foundation/issues/6663
Issue
Hi All,
We've been using Foundation for the bulk of our new web project and have come across a snag.
When keyboard navigating the Tabs element, users are stuck within the Tabs and cannot navigate out.
This behavior is present on the Tabs examples from the Docs as well. Trying to use the keyboard to navigate further down the page, or into one of the tabs, doesn't seem to be possible.
This is very concerning for us, as our site is supposed to fully "Accessible", and screen-reader users must be able to navigate easily.
This behavior prevents any screen-reader user a chance to use the Tabs item properly. Even using the full "Accessibility" suggestions for the Tab object, it is completely useless for blind users.
Has there been any development on this item since the 6663 ticket?
If the Tabs object cannot be used for screen-reader/keyboard navigators then we will have to completely remove it from our project and code something that is compliant, which is, of course, undesirable.

@JoshuaVB Josh I will check out #6663

@dragthor Thanks for looking into this item.
After further digging, we believe part of the offending piece of code is the following from the base foundation JS file, starting line 5503:
    if ($target.length) {
          $original.attr({
            'tabindex' : '-1',
            'aria-selected' : null
          });
          $target.attr({
            'tabindex' : '0',
            'aria-selected' : true
          }).focus();
        }

This causes the other non-focused tabs to be removed from the keyboard navigation schema.

@dragthor A follow-up to the previous item, we've discovered a way to modify the Foundation.js code to partially accommodate our needs. Here's our changes:
Original
Line 5521: $('#' + $(document.activeElement).attr('href').substring(1))
.attr('aria-hidden', null);
Updated
Line 5521: $('#' + $(document.activeElement).attr('href').substring(1))
.attr('aria-hidden', null).find('a').eq(0).focus();
Since we have links in the tab content, this modification works for us. However, it is still not possible to navigate between tabs without first hitting "Tab" or "Enter" on the tab first. It is also not possible for this change to work for users without links in their tab content.

Thanks for posting your solution! This has already been addressed in Foundation for Sites 6. For people sing version 5 can you submit a pull request with your fix?

I too am having this problem, and sadly will probably have to discard Foundation's Tab implementation in lieu of an accessible one. If anyone is curious, I'll be using this one. http://a11y.nicolas-hoffmann.net/tabs/#keyboard_navigation

Just merged the PR! Thanks @JoshuaVB


There is no maxSize option

I do not see any maxSize option do we plan to add it sometime?

Duplicate of #66.


Prod deployment 2025 tracker and pending changes

Closing in favour of #1707 which does not include LUCF to LULUCF changes (data not yet in the production server)


[MXNET-484] MKLDNN C++ test for LRN operator

Description
Add C++ test for LRN MKLDNN operator.
Extend testing framework to filter certain types of test inputs / outputs.
Added note: LRN (fcompute) does not support kWriteInPlace / AddTo
Refactored LRN Execute to conform to standard (accepts out_data as input, rename SetDataHandle
and SetNewMem)
reorder LRN backward in_data (added TODO since this can be optimized)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Add C++ test for LRN MKLDNN operator.
[x] renamed variable names to be more readable.
[x Updated LRN Execute and SetDataHandle (changed to SetNewMem) to conform to MKLDNN API)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@zheng-da

@zheng-da please review.

@pengzhao-intel
I am running to an issue with the LRN backwards operation. The results are different if we run the operation with out_grad and in_grad are in the default format (nChw) vs the result when the out_grad is in the default format but the in_grad is in nChw8c format. Is this a known issue?

will add jira ticket number to this PR. dont need to rebuild just to update comment.

Hi @anirudh2290 I understand this is an urgent fix, but I would appreciate if committers merge the PR after all the reviewers approved it :)

@apeforest Apologies. Didn't notice that you suggested changes.

@anirudh2290 No problem :)


test: move execute functions from utils

Move execute command on pod functions from utils to a new package,
and also move CopyFromPod from utils to imageupload to make utils shorter.
Signed-off-by: Ben Oukhanov<EMAIL_ADDRESS>Release note:
NONE

/sig code-quality

/retest-required

It's ready for review, and previous discussion was resolved. @dankenigsberg Please let me know if we can remove hold label.

Hey @codingben! Good job!
I like the direction this PR is going towards, but still have a few concerns.
I don't really understand why we need 2 (or 3 in the current PR implementation) different functions to execute a command on a Pod. Let me explain why:
First of all, the only difference between ExecuteCommandOnPod() and ExecuteCommandOnPodV2() is that the the first one returns stdout only, while V2 returns stdout and stderr. Even if we set aside the horrible naming for these functions, I don't really see what is the motivation for having them two. Performance-wise there is no difference at all since V2 calls "V1" and simply does not return the stderr part (or more accurately returns it as an error).
Secondly, ExecCommandOnPod() was a private helper function, now it is public. I can't see why we need it to be public, or even need it at all.
What I would do is keep one function, ExecuteCommandOnPod(). This function should have V2's signature, or IOW, should return stdout, stderr and an error. This is how it would be used:
// If we need stderr
stdout, stderr, err := ExecuteCommandOnPod(virtCli, pod, containerName, command)

// If we don't need stderr
stdout, _, err := ExecuteCommandOnPod(virtCli, pod, containerName, command)

Please note again that under the hood nothing is really changed, since stderr is fetched either way (whether you use V1 or V2).
Implementation-wise, this new function needs to have the code of current ExecCommandOnPod() inside it. So eventually we end up with only one unified function.

Another small note: please squash the last commit with spaces only. I would make life difficult for rebases / backports, etc.

Another small note: please squash the last commit with spaces only. I would make life difficult for rebases / backports, etc.

Sorry, do you mean to not have that style commit and make it as part of previous commit?

Yes, exactly

By the way, I'd choose squash commits option when merging this PR. Is there any reason why kubevirt-bot isn't doing it? It's popular approach in other open source projects, for example in Angular.

Not sure who made the decision for Kubevirt, but tbh I don't like squash commits :) I think it's valuable to be able to view commits history as they were originally. For many PRs, if all of their commits were squashed, the changes were very difficult to grasp when looking through history.

Secondly, ExecCommandOnPod() was a private helper function, now it is public. I can't see why we need it to be public, or even need it at all.

It's public because it's used here, and it's giving to ExecuteCommandOnPodWithOptions custom options. In your example, there's no options parameter. WDYT?

Secondly, ExecCommandOnPod() was a private helper function, now it is public. I can't see why we need it to be public, or even need it at all.

It's public because it's used here, and it's giving to ExecuteCommandOnPodWithOptions custom options. In your example, there's no options parameter. WDYT?
We can have ExecuteCommandOnPod and ExecuteCommandOnPodWithOptions. ExecuteCommandOnPod will be merged into ExecuteCommandOnPodV2.

Aha! Got you :)
Sounds good to me, I also like your naming.
Also, if that's the case, I guess ExecuteCommandOnPod would internally call ExecuteCommandOnPodWithOptions, providing default options.

/test pull-kubevirt-e2e-k8s-1.22-sig-compute

/test pull-kubevirt-e2e-k8s-1.22-sig-compute

@codingben why is it DRAFT? Are you still experimenting? If the design is final and you expect review please change from draft to final with the use of "Ready for Review". I looks final to me. It looks good.
 It's on Draft to not trigger all CI tests. I tried to run pull-kubevirt-e2e-k8s-1.22-sig-compute twice here and it's failing - I tried to run locally and it's failing on this error:
Delete "https://<IP_ADDRESS>:49178/api/v1/namespaces/kubevirt-test-default1/serviceaccounts/kubevirt-subresource-test-sa": dial tcp <IP_ADDRESS>:49178: connect: connection refused

I think I didn't setup something properly. I'd like to try to execute another test to make sure some local tests passed before we'll execute all CI tests.

I'm going to make cluster-up :) I'll remove Draft once I'll verify tests locally.

@codingben  I think You need to rebase, then change the PR to ready for review, so all the tests run, and we can finalize the review process

I'll open another PR to just move execute functions from utils without refactoring them.


Fix an edge case that the list request may return empty value but non-null nextlink

Fixes https://github.com/Azure/azure-sdk-for-go/issues/9510

Hi @jhendrixMSFT could you please have a review?

Hi @jhendrixMSFT is it something wrong in my changes or something wrong in the pipeline? I did not quite get the point of the error in the pipeline.

Curious that after I ran npm run build and npm run regenerate, the content in generated directory still show there is diff. I had to make another commit to manually change them back. Something from 1.034e-20 to 1.034E-20

Have you verified this fixes the original issue?

Have you verified this fixes the original issue?

A bit awkward that we only identify this could happen on the customer's log, and we actually cannot reproduce this. The customer says this only happens on occasion.
Do you think we should add some more test cases in the testserver to cover this case?

@ArcturusZhang -
My company (ParkMyCloud) has been experiencing this issue as well, and have had to patch the SDK ourselves to deal with empty page handling.  We hit the problem again with a customer a couple days ago, much to our dismay. Short version: we figured out how to reproduce the problem on demand, and we have created a script that you can use to try it out. Script is at https://github.com/parkmycloud/useful_tools/blob/master/Azure/azure-cli/other_scripts/azure_create_resources.sh
TL;DR version:
We were able to observe the list of instances just before and just after the problem occurred, and noted that all of the  missing instances were all alphabetically after a certain point in the returned list of instances, where alphabetically means the lexical sequence of the full resource id, like this:
/subscriptions/11111--big-subscription-id-111111/resourceGroups/DefaultResourceGroup-CUS/providers/Microsoft.Compute/virtualMachines/ubuntu18
We are calling the SDK method ListComplete with the filter:
(resourceType eq 'Microsoft.Compute/virtualMachines' or resourceType eq 'Microsoft.Compute/virtualMachineScaleSets')
We believe this is what is happening:

The public Azure API for List (https://docs.microsoft.com/en-us/rest/api/resources/resources/list) is probably calling an underlying/backend Azure API that returns an unfiltered and paginated response containing every single resource in the subscription, and the response is alphabetical by resource ID.
The code for the public List API is then running a streaming filter against a page of the resource ID's using the filter shown above.
If the filter results in all of the resource IDs being stripped from the page, the public List API forwards an empty page to the caller, except for the nextLink field.
The GoLang SDK is seeing the empty page and treating it as end-of-data, ignoring the nextLink. (Which hopefully this PR will fix..)

The Python SDK behind the azure CLI appears to handle this correctly, as does the Java SDK used by a partner company of ours.
We reproduced the problem by creating a LOT of non-virtual machine resources (snapshots) that were in the same resource group. We do not know the precise number that triggers the issue. 2600 did not do it, 3100 did.  The resource identifier for snapshots is less than that of virtual machines (looking at the next column in the identifier after Microsoft.Compute):
/subscriptions/11111--big-subscription-id-111111/resourceGroups/TestRG /providers/Microsoft.Compute/snapshots/ASnapshot-10999
vs.
/subscriptions/11111--big-subscription-id-111111/resourceGroups/TestRG/providers/Microsoft.Compute/virtualMachines/ubuntu18
Basically:

Download the script from https://github.com/parkmycloud/useful_tools/blob/master/Azure/azure-cli/other_scripts/azure_create_resources.sh
Edit the variables at the top of the script for your subscription ID and anything else you want to tweak. Use a resource group with a name like "TestRG" (this does not matter so much for the test, except insofar as all of the other resource groups in the subscription with names greater than TestRG are about to disappear from GoLang SDK visibility...)
Run the script.
Select create a resource group
Select create VMs
Check the GoLangSDK ListComplete API - it should return all of the VMs correctly.
In the script, select create snapshots.
Check the GoLangSDK ListComplete API - it should return none of the VMs VM from a resource group with a name greater than RGTest
Apply the SDK fix from this PR
Check the GoLangSDK ListComplete API - hopefully the VMs magically reappear

Let us know of any thoughts/feedback.

@ArcturusZhang - An added note...
It looks like the code in this PR is returning empty pages to the customer code.  This is the same thing we did in our code, and we ended up having to also create a new SDK IsEmpty() function to help our code determine if it needed to skip to the next page.
Our new function looks like this (we applied the change to the downloadable SDK, not to the autorest, so I am sure your solution would have to look a bit different...):
func (iter ListResultIterator) IsEmpty() bool {
	return iter.page.lr.IsEmpty()
}

Otherwise we battled with trying to use reflection when trying to see if the returned page was empty before trying to dereference the contents.  If you are not doing to add a public ListResultIterator IsEmpty() method, could you please give a hint in the function comments as to how customer/client code can safely determine if the page is empty?
Thanks much!

I think that for iterators, it should handle the empty page case internally and just move to the next non-empty page.  That way consumers don't have to worry about checking for a nil item (plus it just seems weird that an iterator would return a nil item).

Yes, we thought of that approach as well...our concern was that it could result in a very rapid sequence of API calls that could invoke rate limiting/throttling on the Azure side, invisible to the client app.  I have not looked at the SDK in detail recently to see if there is increased visibility to rate limiting responses, so it may be that you have added code to handle that better...  With the proliferation of 3rd-party products monitoring large enterprise cloud performance, we have definitely seen an increase in the number of times we run into rate limiting issues.  Ref: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/request-limits-and-throttling
(A perfect-world-wish-list item for the SDK would be to propagate the x-ms-ratelimit* header items from the HTTP response...maybe in the context or something...?)

I think that for iterators, it should handle the empty page case internally and just move to the next non-empty page.

Agreed...

Good point about throttling.  The retry logic in go-autorest (see DoRetryForStatusCodes()) will detect throttling and sleep for the value specified in the Retry-After header before retrying the request.  Note that in earlier versions the code would infinitely retry on a 429; this was fixed in autorest/v0.10.0 (v14.0.0 if you're not using modules).  If you want to opt out of retries due to throttling you can remove the http.StatusTooManyRequests from the slice of status codes for retry here.

Hi @wsupernor I could reproduce this now, thanks! And I will continue working on this to provide a more elegant fix

Hi @jhendrixMSFT and @wsupernor I am closing this PR in favor of PR #433


structured-logging: enable KobjSlice usage and warn Kobjs usage

This pull request enables detection and warning on now deprecated KObjs.  It is suggested to use the KObjSlice instead of using Kobjs for better logging performance Since https://github.com/kubernetes/kubernetes/pull/110724 is now merged, We can reap the benefits of the change that went into the klog via https://github.com/kubernetes/klog/pull/322
Fixes Part of https://github.com/kubernetes/kubernetes/issues/110737

I think we need also a test case where KObjs is flagged as a function that shouldn't be used.

@pohly  Sorry, I have been away for a few days. I will take a look at this and get the update published this week

@pohly PTAL. I've added the required test as suggested

/cc @thockin

@pohly  PTAL when time Permits. I've added a few flag for the deprecation check and is enabled by default right now.

The code looks good now, but I remembered that https://github.com/kubernetes-sigs/logtools/blob/main/logcheck/README.md has documentation for the available checks - can you add the new one there?

@pohly Updated the README. It was also missing the verbosity-zero check. Included that as well

Keeping documentation up-to-date... always easy to forget. Everyone should just read the source code! :sweat_smile:
Thanks for updating everything.


Allow matching against a collection of selectors

Hi, thank you for this library. It is brilliant and the code is very clean.
I would like to add a feature to the selector engine. Sometimes I'd like to check an array of selectors exists in one go, so I made this PR. Let me know what you think.

Nice, thanks. released as ver 0.7.6


Support for TabPanel to have better keyboard navigation control

Feature Request
Support for TabPanel to have better keyboard navigation control from tab header to tab content
Problem description
Currently when we are using Menu as a tablist and rendering the corresponding panel as a layout we are running into issues to move keyboard focus across these two components. Ideally a tab panel should be able to move keyboard focus from tab header to the underlying tab panel as soon as user issues a keyboard event.

Please provide accessibility specification for this.

After discussions with Reach team it was concluded that this was not needed.   Please close.


WIP Using Jinja for Config Templates

Introduction to Jinja2 and Junos PyEz
Part 1 – Intro to Jinja2
Discusses Jijna2 syntax

Template rendering
{% if %}
{% for %}
{% set  %}

Part 2 – Into to PyEz

Connecting to a remote Junos device.
Getting configuration from the Junos device.
Loading configuration to the Junos device.

Part 3 –Configuring Junos Device using PyEz and Jinja2 Template

Creating Jinja2 template for Junos configuration.
Rendering Jinja2 template.
Pushing config to the Junos device using PyEz config module

Part 4 -	Optimizing Configuration Push

Use Junos PyEz inbuilt function to render Jinja2 template and  configure a single device
with Config(dev, mode='private') as cu:
cu.load(template=template, template_vars=template_vars, format='text')

Part 5 –Configuring multiple Junos devices using Jinja2 template

Use a single Jinja2 template
Use YAML file or Python dictionary as variables
Pushing basic config like hostname to multiple devices.

Closes https://github.com/nre-learning/antidote/issues/72

@Mierdin Can you please review our lesson.

@Mierdin we have made the proposed changes in stage 1 and 2 and we also reviewed the stage 3 and stage 4. Could you please check it now?

@Mierdin  I have changed the syntax snippet to three-backticks (```)  to and have renumbered the snippet accordingly.
Issue:
 Okay. Please use the three-backticks (```) here anyways so that it renders correctly - you don't have to put a button here. Note that the javascript for the run this snippet button still counts this so you'll have to update your indices for the other places you have this button appropriately.

@Mierdin We have added a new stage in the lesson based on Jeremy's recommendation. Hence, moved parts around in other lessons.


fix styling to improve heading spacing fixes #102036

This PR fixes #102036

So the first issue is that most elements have a margin-top and margin-bottom.
It made sense to remove the margin-top and let top elements push others down. (otherwise you fall into margin-collapse hell)
This means the body needs a padding on the top so that any first element has a gap (and not just the H1)
Headings have a smaller bottom margin so as to look more like a section
If 2 paragraphs are next to each other, the second paragraph reduces its top margin to bring them closer together.

Before

After

pings @mjbvz

Looks good!
Merged for the 1.48 insiders builds so we can make sure these changes work well out on real world markdown


Is crawler4j configurable to setup period of time to do crawling constantly

As title. We may need to monitor specific site for update. So we want the configuration to setup the crawler4j to periodically crawl specific site/url.

I don't believe so, you'd need to wrap the crawler in some sort of external scheduling mechanism (e.g. maybe a cron job, or something more sophisticated like Control-M if your organization has a formal batch job infrastructure.
You might also (I've never tried this myself) be able to use a java scheduling library like Quartz, but I've never done this myself.

At the moment C4J does not have infrastructure for scheduling but you can easily patch together one using the already cited Quartz or some command scheduler like plain old cron or Jenkins.


fix(time-picker): Unable to select any hours before noon, #132

All Submissions:

[x] Have you followed the guidelines in our Contributing document?

[x]  Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

[x] Does your submission pass tests? ( No tests added )

[x] Have you lint your code locally prior to submission?

[x] Have you compile/build your code locally prior to submission?

Changes to Core Features:

[x] Have you successfully ran tests with your changes locally?

Fixes web-ridge/react-native-paper-dates#132


store attribute metadata as it exists at creation, instead of nil

When the initial paper trail version is created any attribute metadata will be nil instead of the values that exist, because #{attribute}_was will always return nil for new models. This looks like an explicit decision, given there is a test, but I don't understand the logic behind it.
For background, in my case I'm building a multi-tenant application and I'm adding the tenant id attribute to my paper trail version metadata. It's important for us to be able to query the version history restricted by tenant, and with the current behavior it's impossible to match create events with a tenant without reifying the actual objects.
Any other use case for storing attribute metadata I can think of also would benefit from storing the metadata that exists at create, rather than storing nil, but maybe I'm missing something?

So as discussed in some previous issues (#185, #385, #387), this is the expected behavior, as all of the aspects of a model (including metadata) are meant to show what the model looked like PRIOR to the event driving the generation of the version. That being said, I'm guessing that lots of users (I've done this in the past as well) are often looking to have the metadata populated even on create events, so maybe it just makes sense to merge this.
Although it begs the question: How important are  create events?  I usually just skip them since they can't be reified anyways..

For me the value of create events is to have a complete history available in paper trail without having to reify anything or check existing objects. If you don't store create events the only way to get the date a model was created is to check created_at on an existing model or reify a version for deleted models. This method also only works if your model has a created_at attribute, which isn't a given.

Cheers

Isn't this a significant mismatch in behavior for new records vs update records?
When metadata may be nil for created records, this matches the created behavior for Version objects as well, where new versions represent the state of the previous, rather than current data.
It seems like this behavior breaks a few possible expectations:

That metadata matches version behavior. With this change, this is true for updates, where both the metadata and object data refer to the state prior to the change, but no longer the case for created events.
That metadata can be used for queries across versions. Per the example shown in the readme, let's say that you wanted to find all Article versions with a particular author_id, and had an Article which was created, and then had a change in author.
A query for PaperTrail::Version.where(:author_id => author_id) will return two results back for this article (rather than one), one for the initial created version, and one for the change event, both with identical metadata.
That metadata matches the current version. This is an incorrect expectation based on open issues, and documentation, but it is the apparent behavior when creating a new record.

Would a new issue be better for discussion, or has this already been hashed out?

These all seem like valid concerns, @Billiam. Ben, can address these concerns?


Add support for external grpc client

resolves https://github.com/open-traffic-generator/openapiart/issues/328
We will expose these two methods in GrpcTransport interface
	// SetClientConnection set grpc DialContext
	SetClientConnection(con *grpc.ClientConn) GrpcTransport
	// ClientConnection get grpc DialContext
	ClientConnection() *grpc.ClientConn

This is one snippet how user call it
	ctx, cancelFunc := context.WithTimeout(context.Background(), 20*time.Second)
	defer cancelFunc()
	conn, err := grpc.DialContext(ctx, grpcServer.Location, grpc.WithTransportCredentials(insecure.NewCredentials()))
	if err != nil {
		log.Fatal(fmt.Sprintf("failed grpc dialcontext due to %s", err.Error()))
	}
	clientConnApi := openapiart.NewApi()
	clientConnApi.NewGrpcTransport().SetClientConnection(conn)

Anything stopping this from being merged?

@alexmasi the change looks good but its missing a unit test which will be addressed asap.

I have created another api  clientConnApi  using SetClientConnection() which will use at the time of other UT execution.
But I agree it will better to add additional UT. Please check this UT TestGrpcClientConnection
https://github.com/open-traffic-generator/openapiart/blob/main/pkg/transport_test.go


[HUDI-2480] FileSlice after pending compaction-requested instant-time…

… is ignored by MOR snapshot reader
Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

I ll take this up. cc @bvaradar in case he has time to take a peek as well.

Hi，everyone，I have used this patch, i used flink sql execute batch query and the results were as expected  , but spark-sql still lost data when querying rt table. I want it can as release blocker.

Makes sense. Lets dig into this

Hi，everyone，I have used this patch, i used flink sql execute batch query and the results were as expected , but spark-sql still lost data when querying rt table. I want it can as release blocker.

Hi @mincwang , is that possible to reproduce the data lost in a unit test? Are you using hive rt view or Spark MOR relation?

Hi，everyone，I have used this patch, i used flink sql execute batch query and the results were as expected , but spark-sql still lost data when querying rt table. I want it can as release blocker.

Hi @mincwang , is that possible to reproduce the data lost in a unit test? Are you using hive rt view or Spark MOR relation?

Thanks for @garyli1019  reply，I used the Spark MOR query, the Spark query loses data when the Flink streaming writes to HUDi and the compression scheduler is executed but the compression plan is not executed。
-- FLINK SQL  with clause DDL
   'compaction.async.enabled' = 'false',
--    'compaction.trigger.strategy' = 'time_elapsed',
--   'compaction.delta_seconds' = '3600'

Hi @danny0405 ，Can you give we a more professional reply?

Hi @garyli1019 ，i meet some error in try spark UT , so I provide an operation detail below：

mysql

create table user(
    id   int not null primary key,
    name varchar(10) null
);

flink job

CREATE TABLE user_mysql(
 id INT ,
 name STRING,
 PRIMARY KEY(`id`) NOT ENFORCED
)WITH (
 'connector' = 'mysql-cdc',
 'hostname' = '10.49.0.x',
 'port' = '3306',
 'username' = 'root',
 'password' = '',
 'database-name' = 'poc',
 'table-name' = 'user'
);

CREATE TABLE `user_hudi`
WITH (
    'connector' = 'hudi',
    'table.type' = 'MERGE_ON_READ',
    'path' = 'hdfs:///hudi/debug/user',
    'index.state.ttl'='0',
    'index.global.enabled' = 'false',
    'write.tasks' = '1',
    'changelog.enabled' = 'true',
    'hive_sync.enable' = 'true',
    'hive_sync.metastore.uris' = 'thrift://10.49.2.x:7004,thrift://<IP_ADDRESS>:x',
    'hive_sync.mode' = 'hms',
    'hive_sync.db' = 'debug',
    'hive_sync.auto_create_db' = 'false',
    'hive_sync.table'= 'user',
    'hive_sync.username' = 'hadoop',
    'hive_sync.password' = '',
    'hive_sync.partition_extractor_class' = 'org.apache.hudi.hive.MultiPartKeysValueExtractor',
    'hoodie.datasource.write.hive_style_partitioning' = 'true',
    'compaction.async.enabled' = 'false',                 ---- highlight
    'compaction.trigger.strategy' = 'time_elapsed',  ----- highlight
    'compaction.delta_seconds' = '120'                     ---- highlight
) LIKE `user_mysql`(
    EXCLUDING ALL
    INCLUDING CONSTRAINTS
);

INSERT INTO user_hudi SELECT * FROM user_mysql;

now, we should start the flink task.
then i will interval 30 seconds execute once DML for user table of mysql
-- init insert into
INSERT INTO user VALUES(1,'1');
INSERT INTO user VALUES(2,'2');
-- delete 30 seconds after
DELETE FROM user WHERE id = 1;
-- insert into new value 60 seconds after
INSERT INTO user VALUES(3,'3');
-- update  90 seconds after
UPDATE user SET name='33' where id = 3;
-- insert into new value 120 seconds after
INSERT INTO user VALUES(4,'4');

currently for mysql，user table of query results should below:

for flink batch query（apply the hudi-2480 patch），results below：

for flink streaming changlog  query （apply the hudi-2480 patch)，results below：

for hive batch query，results below：

for spark batch query，results below：

The query results of both Hive and Spark are incorrect

Thanks for the detailed response @mincwang , will dig into this over the weekend

When I use the following command to perform the compression manually，query again
bin/flink run -c org.apache.hudi.sink.compact.HoodieFlinkCompactor lib/hudi-flink-bundle_2.12-0.10.0-SNAPSHOT.jar --path hdfs:///hudi/debug/user

hive

spark

flink
Flink batch queries also seem to have problems when I manually perform the compression into the Parquet file

Looking forward @garyli1019 fixing it

@mincwang I think I find the cause of this behavior
The codepath of hive rt query goes to https://github.com/apache/hudi/blob/0fb8556b0d9274aef650a46bb82a8cf495d4450b/hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/utils/HoodieHiveUtils.java#L158-L169
you could set the config HOODIE_CONSUME_PENDING_COMMITS to true and try again.
The Spark MOR snapshot read codepath goes to
https://github.com/apache/hudi/blob/a0dae41409a4f2d509aae1b16a4b509ec774c454/hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/utils/HoodieRealtimeInputFormatUtils.java#L238-L240
We should include the compaction request instant here as well.
Do you mind having a try with this fix?
The file listing code path of Spark/Hive/Flink is different now, which leads to this issue. We need to unify the file listing as a high-priority task.

filed a ticket https://issues.apache.org/jira/browse/HUDI-2816

Thanks for @garyli1019  reply. I will try this fix tomorrow。cc @danny0405

@mincwang I think I find the cause of this behavior The codepath of hive rt query goes to
https://github.com/apache/hudi/blob/0fb8556b0d9274aef650a46bb82a8cf495d4450b/hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/utils/HoodieHiveUtils.java#L158-L169
you could set the config HOODIE_CONSUME_PENDING_COMMITS to true and try again.
The Spark MOR snapshot read codepath goes to
https://github.com/apache/hudi/blob/a0dae41409a4f2d509aae1b16a4b509ec774c454/hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/utils/HoodieRealtimeInputFormatUtils.java#L238-L240
We should include the compaction request instant here as well.
Do you mind having a try with this fix?
The file listing code path of Spark/Hive/Flink is different now, which leads to this issue. We need to unify the file listing as a high-priority task.

Why the Spark MOR snapshot read codepath goes to hudi-hadoop-mr？It shouldn't be hudi-spark？

Why the Spark MOR snapshot read codepath goes to hudi-hadoop-mr？It shouldn't be hudi-spark？

@mincwang the original thought was to reuse file listing code for hive and spark, so I put it under hadoop-mr

Looking into this

@mincwang did the patch resolve your spark and Hive issues?

I'll verify it

This patch is great, but there is one small problem，following：

when I delete record with id 5
hive query reslut：

spark query reslut：

flink query reslut is right

because @danny0405 skipped deleted records in the snapshot query  https://github.com/apache/hudi/pull/4041

Only when I complete the compression is the result expected
and in between, I exected the following DML：
INSERT INTO user VALUES(4,'4')
UPDATE user SET name='222' where id = 2

After  complete the compression
hive：

spark：

mysql：


With 1.3.3: undefined method `[]' for #<PDF::Reader::Reference:0x2c851e0 @id=32, @gen=0>

After installing 1.3.3 I can no longer use the library. It always fails with the following error:
C:/Tools/ruby/lib/ruby/gems/2.2.0/gems/pdf-reader-1.3.3/lib/pdf/reader/page_layout.rb:17:in initial ize': undefined method[]' for #<PDF::Reader::Reference:0x2c851e0 @id=32, @gen=0> (NoMethodError)
from C:/Tools/ruby/lib/ruby/gems/2.2.0/gems/pdf-reader-1.3.3/lib/pdf/reader/page_text_receiv
er.rb:49:in new'         from C:/Tools/ruby/lib/ruby/gems/2.2.0/gems/pdf-reader-1.3.3/lib/pdf/reader/page_text_receiv er.rb:49:incontent'
from C:/Tools/ruby/lib/ruby/gems/2.2.0/gems/pdf-reader-1.3.3/lib/pdf/reader/page.rb:76:in t ext'         from C:/WORK/pdf-test.rb:17:in'

Note: Up to line 17 my code basically looks like this (comments removed):
require 'pdf-reader'
reader = PDF::Reader.new(ARGV[0])
lines = reader.pages[0].text.split(/$/)

@bback Was having the same problem. Solved with a bundle update pdf-reader. Looks like I was using ttfunk 1.2.0 and upgrading it to 1.2.2 fixed the issue.

@bback also fixed the issue by doing this in my gemfile
gem 'pdf-reader', :git => 'git://github.com/yob/pdf-reader.git'

It sounds like this might be resolved in newer releases. I'll close the issue for now, but feel free to re-open if more information becomes available.


Use SQLiteAdjustmentReader for dividends payouts.

Pass a SQLiteAdjustmentReader and use queries for the dividends table
to disperse payouts to stocks in which the algorithm has a position.

cc: @jbredeche

some minor questions/comments, lgtm otherwise.  nice work.


Somehow provide an API for dynamic query texts

Right now it looks to be impossible to compose a SQL query at runtime, as all prepare functions take a comptime query.
Do i have to use the native API for this or is it planned to add this feature?
Another option would be something like query macros where i can dynamically insert some code in the query when preparing it...

Done in #53


update gradle version

Any behavior change on build system must not affect to this library.
Merging, thanks!


Rule proposal: forbid imports

We might have a package that we want to use in one very specific place, but prevent it from being used elsewhere. It would be nice to have a rule that could be customized to prevent it from being imported anywhere.
It could take an object of package name keys and message pairs to give high-quality messages.
Options:
"import/forbid-imports": [2, {
  "some-package": "Please use some-other-package instead.",
}],

// Bad
import foo from 'some-package';
import { bar } from 'some-package';
const foo = require('some-package');
const { bar } = require('some-package');

// Good
import foo from 'some-other-package';

Thoughts?

I suppose if we can make #500 work, that would probably satisfy this scenario pretty well.

I think the core rule no-restricted-imports may cover this already.

@ljharb seems to be right. Might be a good enhancement for the core rule.

Indeed. I realize I wasn't very clear, but that's what I was trying to say about making #500 work. :)

Ah, you are right! This is already a rule. Thanks! 👍


redis.scan_iter return coroutine object

Description
I'm using scan_iter from redis library and it returns AsyncIterator in async version. Before I installed Newrelic client on my project, this piece of code was working fine:
redis = Redis.from_url("redis://localhost:6380/0")
async for found_key in redis.scan_iter(match="key"):
   some logic

I use async for since the method returns AsyncIterator. But after I installed Newrelic I got this error:
TypeError
'async for' requires an object with __aiter__ method, got coroutine

I've checked the return value of the method for both versions:
Before Newrelic:
>>> r.scan_iter(match="somekey:")
<async_generator object AsyncScanCommands.scan_iter at 0x10c95a2b0>

After installation:
>>> r.scan_iter(match="somekey:")
<coroutine object _wrap_asyncio_Redis_method_wrapper.<locals>._nr_wrapper_asyncio_Redis_async_method_ at 0x7f2957c74481>

Note that in wrapped method returns coroutine instead of async_generator. So I think there is a problem with wrapping methods from Newrelic side.
Expected Behavior
Work as before
Steps to Reproduce
Check this piece of code before and after Newrelic installation. (Your Newrelic application should be enabled of course)
import asyncio
from redis.asyncio import Redis

async def sample():
    redis = Redis.from_url("redis://localhost:6380/0")
    async for item in redis.scan_iter(match="somekey"):
        print(item)

if __name__ == '__main__':
    asyncio.run(sample())

Your Environment
newrelic==9.1.0
redis==4.6.0
python version = 3.11.3

I can confirm the instrumentation does not correctly apply tracing wrappers to generators in redis. This affects both synchronous and asynchronous clients. We'll update this in our next release.


Fix JSON report and add unit tests

Signed-off-by: Fundakowski, Lukasz<EMAIL_ADDRESS>

Codecov Report

Merging #64 (69012e1) into main (dd003db) will increase coverage by 4.60%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
+ Coverage   84.62%   89.22%   +4.60%
==========================================
  Files          41       41
  Lines        2003     2005       +2
==========================================
+ Hits         1695     1789      +94
+ Misses        308      216      -92

Impacted Files
Coverage Δ

src/twister2/report/test_results_plugin.py
98.41% <75.00%> (+63.73%)
:arrow_up:

src/twister2/twister_config.py
91.48% <0.00%> (+2.12%)
:arrow_up:

src/twister2/report/test_plan_plugin.py
100.00% <0.00%> (+2.27%)
:arrow_up:

src/twister2/log.py
100.00% <0.00%> (+11.11%)
:arrow_up:

src/twister2/report/helper.py
96.96% <0.00%> (+12.12%)
:arrow_up:

src/twister2/report/test_results_json.py
100.00% <0.00%> (+41.66%)
:arrow_up:

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


DBZ-2773 Trigger non-core connectors to resolve cross-repo builds

https://issues.redhat.com/browse/DBZ-2773

@ani-sha Could you please check the actions log? It seems to me that it checks out master branches instead of branch for which the action is part

@ani-sha Could you please check the actions log? It seems to me that it checks out master branches instead of branch for which the action is part

@jpechane yes it's checking out to master.

@jpechane Added the changes! Now it checks out to the respective branch for core and master for vitess, incubator

@ani-sha Applied, good job!


Meteor/Karma/flow-router

Hi all,
(I had just opened another issue which after a very quick and kind reply from PEM turned out to be caused by an embarrassing mistake I made. I hesitate to open another issue but I give it one more shot as this time I am more confident that this is not just stupid me).
I am using Meteor, React and FlowRouter. I have built a little app and everything works fine so far. I am also using jasmine for unit testing which means also velocity and Karma get pulled in.
My problem is that when I look at the browser window that automatically gets opened by Karma all I see in the browser is a debug button on the right and the following text on the left:

Karma v0.13.9 - connected
Chromium 48.0.2564 (Ubuntu 0.0.0) is idle

and when I look at the console it shows

There is no route for the path: /context.html

When I hit the debug button a new tab opens with a completely empty page. Looking at the console I see:

There is no route for the path: /debug.html

I searched for context.html on the server and found this:

./.meteor/local/mirrors/jasmine-client-integration/.meteor/local/build/programs/server/assets/packages/sanjo_jasmine/src/client/unit/assets/context.html
./.meteor/local/mirrors/jasmine-server-integration/.meteor/local/build/programs/server/assets/packages/sanjo_jasmine/src/client/unit/assets/context.html
./.meteor/local/build/programs/server/assets/packages/sanjo_jasmine/src/client/unit/assets/context.html
./.meteor/local/karma/jasmine-client-unit/context.html

I have written a number of test cases and they work fine. So the error which causes the two messages above does not prevent the tests from being executed. Using the console I can even debug my app. So everything is kind of working out for me. I just wonder what are context.html and debug.html good for and how can I fix the two errors.
Has anyone come across the same issue before?
Thanks very much!
Alex
p.s.
Here is my package list
meteor-base             # Packages every Meteor app needs to have
mobile-experience       # Packages for a great mobile UX
mongo                   # The database Meteor supports right now
session                 # Client-side reactive dictionary for your app
jquery                  # Helpful client-side library
tracker                 # Meteor's client-side reactive programming library

standard-minifiers      # JS/CSS minifiers run for production mode
es5-shim                # ECMAScript 5 compatibility for older browsers.
ecmascript              # Enable ECMAScript2015+ syntax in app code

velocity:html-reporter
velocity:console-reporter
sanjo:jasmine

meteorhacks:npm         # support for NPM packages
npm-container           # helper for NPM package support

cosmos:browserify
kadira:flow-router      # Router
react                   # Renderer
kadira:react-layout     # Renderer helper
stylus                  # enhanced CSS
markoshust:material-ui  # material ui including components library

@Bollux unfortunately, I have no experience in this matter. I hope someone could help you out.
Or try to ask this question on Meteor Forums, I hope you'll get more help there.


[Adaptive Cards - Card Structure]: Ensures ARIA attributes are allowed for an element's role for the 'Please choose' edit fields under 'Malt and Vine Order Form'.

Target Platforms
Other
SDK Version
1.5
Application Name
Adaptive Cards
Problem Description
Test Environment:
OS: Version 23H2 (OS Build 25381.1)
URL: https://adaptivecards.io/designer/
Browser: Edge Dev Version 115.0.1880.3 (Official build) dev (64-bit)
Tools: Accessibility Insight For Web
Repro Steps:

Open the above URL in the edge dev browser.
Navigate to 'Designer' tab item and press enter key to activate it.
Navigate to 'New Card' button and press enter key to activate it.
Run accessibility insight for web tool and observe the issue.

Actual Result:
ARIA attributes are not allowed for an element's role as for the 'Please Choose' edit field. Also, combo box is automatic getting expanded when focus comes on it,
Expected Result:
Ensures ARIA attributes should allowed for an element's role i.e. for 'Please Choose' edit field and combo box should not be expanded automatically when focus comes on it.
Element path:
#__ac-14a10d9e-6f66-472b-9bc4-c8987d22e18c
How to fix:
Fix any of the following:
ARIA attribute is not allowed: aria-required="False"
User Impact:
It will impact the screen reader if the aria attributes are allowed for the element as it will not convey the required information to the user.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html
“Have feedback to share on Bugs? Please help fill Trusted Tester Bug Feedback (office.com) “
Screenshots

Card JSON
NA

Sample Code Language
No response
Sample Code
No response

Hi @anna-dingler,
As this issue is still repro, so could you please let us know is there any future plan to fix this issue?
Snippet:

Hi @vagpt,
This issue is fixed on our internal site. I expect us to make another website release this month, so I will go ahead and mark this as completed.
Please let me know if you have any questions!

Hi @anna-dingler,
Thanks for the update.
It would be great if you please create a new label as 'NotReadyToTest' for this type of condition.

Hi @vagpt,
Apologies for the late response. I just released a new version of the website so this fix can be seen in production.
I created a NotReadyToTest label that I will use in the future.
Thanks!

Thanks @anna-dingler
Adding A11yTTValidated tag as issue is not repro on latest version.


[Backport] Upgrading netty version to 4.1.69.Final (#1363)

Signed-off-by: Vacha<EMAIL_ADDRESS>Description
Backport of #1363
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

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

Do we need this in 1.1? Are we releasing a patch?

start gradle check


Few Methods of the class com.marklogic.client.query.StructuredQueryBuilder should return StructuredQueryDefinition

The methods such as collection(), directory() etc of the class "StructuredQueryBuilder" should have a return type of "StructuredQueryDefinition" similar to the other query constructors.
The current behavior is that it returns the type "StructuredQueryBuilder.CollectionQuery" leading to compile time errors due to visibility issue.

I don't think it is accurate to say that there is a compile time issue. Instead, there is a usability issue.
Because StructuredQueryBuilder.CollectionQuery derives from StructuredQueryDefinition and because StructuredQueryDefinition is public, applications can already assign the return value of collection() to a StructuredQueryDefinition variable.
However, that is certainly not intuitive.

Should cause no regressions because the protected derived interfaces couldn't be used anyway.

No regressions seen. Verified on 08/21/2019 Jenkins test results.


Feedback

Implement feedback gotten.

Coverage decreased (-5.2%) to 91.429% when pulling 9f95f5ea3415a7a693b4d9528e43fd5c061a61f4 on feedback into f0d64dce4881c776f8abddf47778cc946d7f5c58 on develop.

Coverage decreased (-5.2%) to 91.429% when pulling 69314c42417ae0b2f60a7dc9555de5973343ac88 on feedback into f0d64dce4881c776f8abddf47778cc946d7f5c58 on develop.

Coverage decreased (-5.2%) to 91.429% when pulling 898b4f4c273a42e15045e078ed0b866d197fea48 on feedback into f0d64dce4881c776f8abddf47778cc946d7f5c58 on develop.

Coverage decreased (-5.2%) to 91.429% when pulling 898b4f4c273a42e15045e078ed0b866d197fea48 on feedback into f0d64dce4881c776f8abddf47778cc946d7f5c58 on develop.


Stop Charging Service don't work

After these last updates, the Stop Charging Service for Jaguar I-Pace stopped working.
Can't find any error on the log. It simply don't do the job...
Could it be that the service now require the pin as to open the doors and others (unlock service still works fine).

Strange... This night worked again fine... I made test during this week and many times during the day, the stop service never worked on HA, but was working on the official InControl App... This night (24-01-2024 3am) it worked fine...

Strange... This night worked again fine... I made test during this week and many times during the day, the stop service never worked on HA, but was working on the official InControl App... This night (24-01-2024 3am) it worked fine...


Setup guide for Linux based OS

Task
Describe the step by step explanation to run the project on Linux based OS
Solution (optional)

[ ] How to setup Docker
[ ] npm commands
[ ] specify API key if needed.

Type of Change

[x] Feature update/enhancement
[x] Documentation

i want to work on this

Any updates? @Itashamodi  😅

I am from LGMSOC , I actually overlooked this issue can i work on it ? i have done some work on docker

I am from LGMSOC , I actually overlooked this issue can i work on it ? i have done some work on docker

@7saikat7  Hey 👋
Ok, I'm assigning this to you
Happy Coding 🎉

@7saikat7  Any update?

yes mam I am working on it on ubuntu (LTS) version, It was working on Linux , but everyone use ubuntu also in production so I am trying on it , Sorry it's taking more time then expected !

yes mam I am working on it on ubuntu (LTS) version, It was working on Linux , but everyone use ubuntu also in production so I am trying on it , Sorry it's taking more time then expected !

Okay, no problem
If you stuck at any point feel free to ask on the slack channel.
Happy Coding 👨💻

sorry not getting proper help !


Starter changes for supporting pre/post processing for vision models.

Script to update model with pre/post processing
custom ops for decode/encode

user just has to provide jpg or png bytes
superresolution can return the updated image in jpg or png

models for testing

not sure where the best place to add tests are - will add once that's established. have tested locally and end-to-end running updated model for both mobilenet and superresolution works.
also not sure what the expected test setup is, as building tests for the C++ custom ops seems to be disabled by default

Updated cmake setup to enable building of the vision pre/post processing ops

opencv2 is treated as an internal dependency rather than the mechansim for selecting which operators to include.
clang-format has changed a bunch of spacing so easiest to ignore whitespace diffs for the changes

TODO: Can we use a domain like 'com.microsoft.extensions' for these new ops instead of 'ai.onnx.contrib'? that would be more consistent with ORT contrib ops (which use com.microsoft). currently official onnx ops use the 'ai.onnx' prefix. I can address supporting multiple domains in a separate PR if there's no objection to using this domain name.

not sure where the best place to add tests are - will add once that's established. have tested locally and end-to-end running updated model for both mobilenet and superresolution works.
the code can be checked in ./onnxruntime-extensions and test in ./test folder.
https://github.com/microsoft/onnxruntime-extensions/blob/main/test/test_onnxprocess.py can be an example of the organization, though it is deprecated.

also not sure what the expected test setup is, as building tests for the C++ custom ops seems to be disabled by default
Updated cmake setup to enable building of the vision pre/post processing ops

Enabling CTest needs ONNXRUNTIME_LIB_DIR, which is the folder libonnxruntime.so, it is already setup in CI pipeline. On local development, you need specify it on build.

TODO: Can we use a domain like 'com.microsoft.extensions' for these new ops instead of 'ai.onnx.contrib'? that would be more consistent with ORT contrib ops (which use com.microsoft). currently official onnx ops use the 'ai.onnx' prefix. I can address supporting multiple domains in a separate PR if there's no objection to using this domain name.

The new name looks better, but the existing domain may needs to be kept to avoid breaking the Office models.
We may support both domains? It needs the changes in many places like build, tool, API and test...

BTW, extensions supports editable pip install, i.e. pip install -e .. The setup will compile the C++ source and install so and python module in-place, so all consequential changes on python files will take effort immediately, without any re-installation.


Calling css({'data-css-nil': ''}) throws unexpected error

When the following is called:
css({'data-css-nil': ''})

The following error is thrown:

Error: [glamor] an unexpected rule cache miss occurred. This is probably a sign of multiple glamor instances in your app. See #79

I'm not sure whether css({'data-css-nil': ''}) should be valid - but if not, perhaps the error message should be more descriptive. In Glamorous it is possible to get this error without having multiple instances of glamor.
See:
#373
paypal/glamorous#396
paypal/glamorous#397

@threepointone any thoughts on this?


Checking singleton mock with pointer comparison

Jon, I have ran into the issue again, where it intermittently does not work with that mock comparison in the if statement. So, I think comparing pointers ought to reliably work. Let me know if you would like to discuss further. It's happening for some of us, and not for some others (it may depend on the LLVM used).

I'm going to close this for now, until I figure out some things.

Jon, I think I got a working solution now. The mock comparison was not enough. Sometimes, it was comparing nil == nil, which would be true, but not what we wanted (because self.mock was nullified and the parameter theMock was also nil. I worked around this by creating a 'tag' of the mock, using it's pointer (hence the _mockPtr) ivar. That can be assigned at construction and won't get changed by ARC's weak refs. We are not de-referencing it anywhere, so it's safe. We're just comparing to see if we should unswizzle on dealloc.


Managed file dialog

What does the pull request do?
Implements Managed System Dialogs.

Needs some minor UI polish still. DONE.

It was started by @kekekeks and then I continued his work and integrated with wasabi.
This is a backport of that work.
Its been highly tested for OpenFile, OpenFolder and SaveFile on all platforms.
What is the current behavior?
Native Dialogs only and on Linux - we crash and segfault on many distros.
What is the updated/expected behavior with this PR?
Allow user to choose to use Managed System Dialogs.

Basically the only user-facing types that we should have are:
ManagedFileChooserSources
ManagedFileDialogExtensions with UseManagedSystemDialogs(this AppBuilder builder, ManagedFileChooserSources sources = null);
and
public class ManagedFileChooserDialog
{
      public static Task<string[]> ShowFileDialogAsync(FileDialog dialog, IWindowImpl parent, ManagedFileChooserSources sources = null);
      public static Task<string> ShowFolderDialogAsync(OpenFolderDialog dialog, IWindowImpl parent, ManagedFileChooserSources sources = null);
}

Not had chance to take a proper look but many of the files here are using tabs instead of spaces.

Resolved raised issues, and done a bit of polishing.
Also added ability for the user to host the dialog in a custom window if they wish.

@AvaloniaUI/core head's up: I'm adding the drive mount detection service so please wait till that's committed here :)

@jmacato make sure to fall back to /media enumeration if udisks or entire DBus daemon are unavailable


Content assets feature

Improved comments, better html styling of the comdagen summary content asset, fixing the wrong template being used for the main-home and comdagen summary content asset

Added the last commit to the sorting branch.


Road to 2.0

Hey @TheM4hd1 😊 thanks for making this great library (and Siwa, which is even more impressive), you've done an amazing job thus far. And thanks for letting me tag along and help.
With 2.0 approaching I was wondering what was the great scheme of things, if there were milestones planned or particular features you were thinking of implementing. Cause after using this for a while I have some suggestions that might make it in a bigger update:

in-code documentation
easier permission handler, dropping the Singleton model and all the .shared, allowing users to run multiple accounts at the same time [I might start working on this today or tomorrow, if it's ok]
easier login, streamlining the process by creating accessories and hiding some boilerplate code behind private or internal
a development branch where we can push approved pull requests in order to test everything better before pushing it to the master (2.0 is definitely a big deal 😊)
naming conventions, fixing the userId, pk, userPk... and uniforming parameters names (I know I made it worse with completionHandler vs completion, but I feel like UserReference kinda makes it even hahaha), as well making functions more "swift-y" (using named parameters, etc.)
Swift 5.1, anyone? 🤔 I feel like the some Protocol pattern would be great for solving most of the login "issues"

Just some ideas though. Please let me know what priorities you have and how to help you.
Peace ✌

Hi Stefano,
I must say thanks to you for helping me and contributing this library, there is nothing more than your participation makes me happy.
This is a good idea, jumping to version 2.0 with good feature and changes.
I was thinking about implementing some extra functions which helps user to deal with library easier,
features like receiving:

High Quality Media [video or image]
Low Quality Media [video or image]
Image Thumbnail for media
Statistics functions(calculating total likes, comments, ...)
More flexible delay feature(editing it in run-time, or switching it on-off) with easier ways.
and etc....
which saves a lot of time for users, these are just ideas.
Because the library is growing up by passing the time, the library definitely needs documentation.
we definitely needs to fix naming conventions, because there are very mistakes. and I like the UserReference  idea that was nice one.
development branch is needed as well.
we should invite other users to contribute and sharing ideas here to make next version more powerful.
Thanks again.
Regards.

easier permission handler, dropping the Singleton model and all the .shared, allowing users to run multiple accounts at the same time [I might start working on this today or tomorrow, if it's ok]

I've started working on this. The actual authentication mechanism is in place, I just need to finish rewriting every single method for all the different handlers (😱), and then all it takes is making the same changes to Siwa.
What I've done so far:

APIBuilder, HttpSettings and RequestMessageModel are gone. Now you instantiate directly APIHandler with some Settings taking (option) delay, queues, device (automatically updating the User-Agent) and session (URLSession) parameters.
Nore more *Handler protocols. There was no actual point for them. Every *Handler can now be called through the APIHandler instance (UserHandler is .accounts, FeedHandler is .feeds, etc.), they're lazy properties and they're specific to the instance itself. I've done the same for HttpHelper and PaginationHelper (a.k.a. PaginationHandler in 1.*). This removes all the code duplication where every single method had to be rewritten for APIHandler, and it means "multitasking" with multiple APIHandlers for different logged users.
Authentication is now handled by one single method in the APIHandler instance: authenticate(with request: Login.Request, completionHandler: escaping (Result<(Login.Response, APIHandler), Error>) -> Void), where LoginRequest is an enum that can either take a SessionCache item (which is similar to 1.* SessionCache), and it's used for "logging back in" and with Siwa (in the future), or a LoginWebView (a.k.a. InstagramLoginWebView) — and it's so much simpler than it is now. Literally one call and you're done. This removes all the code duplication between Siwa and SwiftyInsta: if you want "headless" authentication, use Siwa and pass the sessionCache, otherwise use the web view in SwiftyInsta.
Every single method accepting either a user pk or username now takes a UserReference item instead.

I count on finishing everything by tomorrow, and then I could push it to development for further testing. I'm genuinely super excited 💪

The changes seems to very good, development branch added as well.
I'm working on a list of features and tools such as Logger and etc.
And about Authentication, this new method supports all 3 kind of authentications?

Private API Login
Web Login
Siwa

I'm done with all the changes above. I'm testing it for a while and then push a pull request.

And about Authentication, this new method supports all 3 kind of authentications?
Right now it supports web login and Siwa. I feel like the username + password authentication provided with SwiftyInsta was not up to the standards tbh. And since you've done an amazing job for it in Siwa, I really don't feel like it could be dropped (but it's just my opinion).
I feel like users wanting to do username + password should do it right from the start (i.e. with Siwa), without overcomplicating everything else. Again, just my opinion.
It can just as well be added again.

@sbertix  @canaksoy
More ideas? any update?

I was thinking about multi OS support #61
I'll try and work on it later.

High Quality Media [video or image]
Low Quality Media [video or image]
Image Thumbnail for media
Statistics functions(calculating total likes, comments, ...)
More flexible delay feature(editing it in run-time, or switching it on-off) with easier ways.
and etc....
I was thinking… why not rationalizing the way responses are presented to the user?
Instead of returning directly the decoded file (which could become like a raw property), why not returning a cleaned struct, with date already formatted, images with different qualities (like you said), stats embedded into them… etc.

Yes this is a good idea, we should edit models anyway. some of them are missing a few properties and there are many duplicates between models useless protocols and ....
We should definitely improve models and the way they represents data to user.

What about enforcing syntax rules through swiftlint?
Easy to add support for it to Travis CI, but actually super long to change the entire codebase accordingly.
But it should be worth it, imho.
What do you think? @TheM4hd1


Add support for specifying port numbers

Not sure if you are still maintaining this gem - I've got a small change to allow port numbers to be added to the config.
No change to default behavior

Thanks :)


ASim FileEvent parsers and alerts

Fixes #
Proposed Changes

I think we want also IpAddr as an alias. I forgot it, but it seems important.

I added it as a task for the future and withdraw the comment from here.

See #2775  instead


Make a class to handle allocation / access / deallocation of SHMEM

we have program abc
n bytes long
we send a request with pid 1001
at time t
When a message comes in with format like
{
	 "pid": 1001,
	  "time": t,
	  "type": 1,
	  "memsz": n bytes
}

The request will be added to the stack for later handling by the daemon. The daemon will eventually handle the process and allocate a new shared memory segment that can be used for sending large pieces of data between the client and server processes (specifically, compiled binaries that can run on the RISC-V cores).
Having a class to handle this instead of writing the logic across multiple functions in the Daemon will help keep the code much cleaner.
MessageContainer:
Allocates shmem of length size_t length
Basic Access Controls

Issue on hold; we may have to use inter-machine communication rather than IPC depending on how we implement the chip.


build crash: Error: Cannot find module 'config'

Сonfig is available!
Doxity v0.5.2
node v9.11.1
$ doxity build
contracts/ICO.sol:10:42: Warning: "throw" is deprecated in favour of "revert()", "require()" and "assert()".
        if (this.balance != totalSupply) throw;
                                         ^---^
contracts/ICO.sol:13:5: Warning: No visibility specified. Defaulting to "public".
    function ICO(uint _endOfFundingPeriod ) {
    ^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:18:5: Warning: No visibility specified. Defaulting to "public".
    function() {throw;}
    ^-----------------^
contracts/ICO.sol:18:17: Warning: "throw" is deprecated in favour of "revert()", "require()" and "assert()".
    function() {throw;}
                ^---^
contracts/ICO.sol:20:5: Warning: No visibility specified. Defaulting to "public".
    function buyMagicBeans() payable checkInvariant() {
    ^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:21:39: Warning: "throw" is deprecated in favour of "revert()", "require()" and "assert()".
        if (now > endOfFundingPeriod) throw;
                                      ^---^
contracts/ICO.sol:26:5: Warning: No visibility specified. Defaulting to "public".
    function refund() checkInvariant() returns(bool) {
    ^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:39:5: Warning: No visibility specified. Defaulting to "public".
    function fundTheProject() returns(bool) {
    ^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:1:1: Warning: Source file does not specify required compiler version!Consider adding "pragma solidity ^0.4.21;"
contract ICO {
^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:10:13: Warning: Using contract member "balance" inherited from the address type is deprecated. Convert the contract to "address" type to access the member.
        if (this.balance != totalSupply) throw;
            ^----------^
contracts/ICO.sol:41:29: Warning: Using contract member "balance" inherited from the address type is deprecated. Convert the contract to "address" type to access the member.
            && company.send(this.balance))
                            ^----------^
Generating output for 2 contracts...
  done!

><EMAIL_ADDRESS>build /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity
> gatsby build --prefix-links

Generating CSS
Generating Static HTML
Failed at generating HTML

/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/gatsby/dist/bin/cli.js:52
      throw err;
      ^
Error: Error: Cannot find module 'config'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:548:15)
    at Function.Module._load (internal/modules/cjs/loader.js:475:25)
    at requireLike (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/require-like/lib/require-like.js:15:26)
    at webpackUniversalModuleDefinition (render-page.js:3:28)
    at render-page.js:10:3
    at Script.runInContext (vm.js:74:29)
    at Script.runInNewContext (vm.js:80:15)
    at module.exports (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/eval/eval.js:69:12)
    at Compiler.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/static-site-generator-webpack-plugin/index.js:31:20)
    at Compiler.applyPluginsAsync (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:71:13)
    at Compiler.emitAssets (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compiler.js:226:7)
    at Compiler.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compiler.js:184:10)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compiler.js:403:12
    at Compiler.next (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:67:11)
    at Compiler.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/CachePlugin.js:40:4)
    at Compiler.applyPluginsAsync (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:71:13)
    at Compiler.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compiler.js:400:9)
    at Compilation.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:577:13)
    at Compilation.applyPluginsAsync (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:572:10)
    at Compilation.applyPluginsAsync (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:60:69)
    at Compilation.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:567:9)
    at Compilation.next (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:67:11)
    at ExtractTextPlugin.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/extract-text-webpack-plugin/index.js:309:4)
    at Compilation.applyPluginsAsync (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:71:13)
    at Compilation.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:563:8)
    at Compilation.next (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:67:11)
    at ExtractTextPlugin.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/extract-text-webpack-plugin/index.js:285:5)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at Object.async.forEachOf.async.eachOf (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:236:30)
    at Object.async.forEach.async.each (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:209:22)
    at ExtractTextPlugin.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/extract-text-webpack-plugin/index.js:237:10)
    at Compilation.applyPluginsAsync (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:71:13)
    at Compilation.seal (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:525:7)
    at Compiler.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compiler.js:397:15)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/tapable/lib/Tapable.js:103:11
    at Compilation.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:445:10)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:417:12
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at done (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:246:17)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:44:16
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:332:10
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:52:16
    at Object.async.forEachOf.async.eachOf (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:236:30)
    at Object.async.forEach.async.each (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/async/lib/async.js:209:22)
    at Compilation.addModuleDependencies (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:185:8)
    at Compilation.processModuleDependencies (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:170:7)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:320:12
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:123:4
    at Array.forEach (<anonymous>:null:null)
    at callback (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:122:12)
    at Compilation.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/Compilation.js:140:10)
    at NormalModule.<anonymous> (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack/lib/NormalModule.js:115:10)
    at NormalModule.onModuleBuild (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack-core/lib/NormalModuleMixin.js:310:10)
    at nextLoader (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack-core/lib/NormalModuleMixin.js:275:25)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack-core/lib/NormalModuleMixin.js:292:15
    at runSyncOrAsync (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack-core/lib/NormalModuleMixin.js:160:12)
    at nextLoader (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack-core/lib/NormalModuleMixin.js:290:3)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/webpack-core/lib/NormalModuleMixin.js:259:5
    at Storage.finished (/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:38:16)
    at /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:525:3)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `gatsby build --prefix-links`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/scientistnik/.npm/_logs/2018-04-11T11_01_11_611Z-debug.log
Published Documentation to /home/scientistnik/workspace/librebank/tests/doxity-simpleton/docs

When I install config: npm i config:
$ doxity build
contracts/ICO.sol:10:42: Warning: "throw" is deprecated in favour of "revert()", "require()" and "assert()".
        if (this.balance != totalSupply) throw;
                                         ^---^
contracts/ICO.sol:13:5: Warning: No visibility specified. Defaulting to "public".
    function ICO(uint _endOfFundingPeriod ) {
    ^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:18:5: Warning: No visibility specified. Defaulting to "public".
    function() {throw;}
    ^-----------------^
contracts/ICO.sol:18:17: Warning: "throw" is deprecated in favour of "revert()", "require()" and "assert()".
    function() {throw;}
                ^---^
contracts/ICO.sol:20:5: Warning: No visibility specified. Defaulting to "public".
    function buyMagicBeans() payable checkInvariant() {
    ^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:21:39: Warning: "throw" is deprecated in favour of "revert()", "require()" and "assert()".
        if (now > endOfFundingPeriod) throw;
                                      ^---^
contracts/ICO.sol:26:5: Warning: No visibility specified. Defaulting to "public".
    function refund() checkInvariant() returns(bool) {
    ^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:39:5: Warning: No visibility specified. Defaulting to "public".
    function fundTheProject() returns(bool) {
    ^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:1:1: Warning: Source file does not specify required compiler version!Consider adding "pragma solidity ^0.4.21;"
contract ICO {
^ (Relevant source part starts here and spans across multiple lines).
contracts/ICO.sol:10:13: Warning: Using contract member "balance" inherited from the address type is deprecated. Convert the contract to "address" type to access the member.
        if (this.balance != totalSupply) throw;
            ^----------^
contracts/ICO.sol:41:29: Warning: Using contract member "balance" inherited from the address type is deprecated. Convert the contract to "address" type to access the member.
            && company.send(this.balance))
                            ^----------^
Generating output for 2 contracts...
  done!

><EMAIL_ADDRESS>build /home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity
> gatsby build --prefix-links

Generating CSS
Generating Static HTML
WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
WARNING: No configurations found in configuration directory:/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/config
WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment.
Failed at generating HTML

/home/scientistnik/workspace/librebank/tests/doxity-simpleton/doxity/node_modules/gatsby/dist/bin/cli.js:52
      throw err;
      ^
Error: TypeError: Cannot read property 'linkPrefix' of undefined
    at prefixLink (render-page.js:30048:81)
    at module.exports (render-page.js:25338:42)
    at render-page.js:89:40
    at module.exports (render-page.js:101866:11)
    at Object.<anonymous> (render-page.js:88:2)
    at __webpack_require__ (render-page.js:30:30)
    at Object.assign.i (render-page.js:50:18)
    at render-page.js:53:10
    at webpackUniversalModuleDefinition (render-page.js:3:20)
    at render-page.js:10:3

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `gatsby build --prefix-links`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/scientistnik/.npm/_logs/2018-04-11T11_04_29_561Z-debug.log
Published Documentation to /home/scientistnik/workspace/librebank/tests/doxity-simpleton/docs

same issue

Actually not. I have warnings at compile stage, but it's compiled successfully.

this has to do with gatsby version and config.toml being depricated

have the same problem with gatsby build

fixed with using nodejs 8

Same issue. Downgraded from Node 11 to Node 8. Thanks @KatSick


Rewrite in TypeScript as a modern ES6 module

Replaced dynamic CSS keyframe animations with requestAnimationFrame

This adds support for Content Security Policy "style-src 'self';" option (resolves #115, resolves #229)
Fixes janky animation appearance in Microsoft Edge (resolves #342)
Fixes missing line with trail set to 100 in IE (resolves #327)
Animation logic is now unified in all browsers

Library is now distributed as an ES6 module (closes #341, fixes #340)
Removed useless hwaccel option
Dropped IE 6-8 support and removed VML fallback since it isn't needed for IE 9+
Moved internal functions out of Spinner instance
Removed minified files from bundle
Removed jQuery plugin (closes #325)
Removed composer/bower/component/spm support (almost everyone uses npm instead)
Updated website to use native range inputs rather than polyfill, and remove jQuery usage
Added CONTRIBUTING.md file

This should also fix #309.

You can test the new version here: https://theodorejb.github.io/spin.js/

💯 Thank you very much, your help is highly appreciated! I added you as collaborator to this repo. Feel free to modify whatever you feel is necessary.

@fgnass Thanks! Can you also add me as a collaborator on npm so I can publish releases? My username is theodorejb.
https://www.npmjs.com/package/spin.js/access

Done.


E Business Card

First Flutter app

Hi Tanishq,
Congratulations 🎉 on your first contribution to the repo. As a next step, can you please update the readme with the screenshot of the new app?
Reg,
Rahul

Hey Rahul,
As you've told me, I have added the Screenshot at the bottom of the readme.
Regards,
Tanishq

Haven't added the screenshots of the second app (BMI Calculator) though.

Hi Tanishq,
Thanks for adding that, however for every new app, it would be great to have a screenshot as well. Once you add that in, I would be happy to merge your PR.

I've Uploaded the Screenshots for both the apps


PayPal Integration

PayPal offers easy donation button generation via HTML that allows us to specify instant payment notifications. It may be easier to support PayPal before Patreon because PayPal has a higher adoption rate.
https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/Appx_websitestandard_htmlvariables/#id08A6HI0J0VU
https://developer.paypal.com/docs/classic/products/instant-payment-notification/
https://github.com/paypal/ipn-code-samples/blob/master/python/paypal_ipn.py
We should use custom to pass a JSON string with the donator's account ID as well as the ID of the story.
no_shipping should be used.
It should be noted that since this is PayPal people will lose a portion of their donations due to currency conversion fees.

See #15


ToolTippery support

https://github.com/Psychpsyo/Tooltippery is a really useful thing for my ADHD brain.
I tried to add it manually to the en.json file for the English locale located at https://github.com/Psychpsyo/DefaultTooltips
However I'm barely competent at reading the code and couldn't grok what the button names were other than "button."
If you could get it working and maybe make a getitemlink.json for it that would store in /defaultTooltips/Locales/ that would be cool.

implemented in version 1.3.0