Auto close for alerts

I would like to set a timeout for alerts, and the alert is not removed when i remove the item from the array inside the controller...
Markup:
<alert ng-repeat="alert in alerts" type="alert.type"  close="alert.close()">{{alert.msg}}</alert>

Inside controller:
$scope.alerts = [];
var alert = {
	msg: 'Please fill all the fields.'
};
alert.close = function(){
	$scope.alerts.splice($scope.alerts.indexOf(this), 1);
}
$scope.alerts.push(alert);
setTimeout(function(){
	$scope.alerts.splice($scope.alerts.indexOf(alert), 1);
}, 3000);

In this code the timeout is executed the item is removed, but the view doesn't refresh...

in controller i have
$scope.alerts =  [ ];
$scope.closeAlert = function (index) {
  $scope.alerts.splice(index, 1);
};
$timeout(function(){
  $scope.alerts.splice($scope.alerts.indexOf(alert), 1);
}, 3000);

while deleting i would like to show this message i.e.,
$scope.alerts.push({
    type: 'warning',
    msg: 'Task have been deleted!!' +
      'Click to undo'
   });

for showing the html content and ng-click purpose i use this directive i.e.,
app.directive('alert', function ($compile, $parse) {
return {
restrict: 'E',
link: function (scope, element, attr) {
scope.$watch(attr.content, function () {
element.html($parse(attr.content)(scope));
$compile(element.contents())(scope);
}, true);
}
}
});
my issue is i didn't get the close button on alert after the usage of this directive and also auto close alert is also not working.

In this example the alert is not showing properly i.e., it showing half of the alert message only in XS mode

For support, please try SO or the IRC channel

https://github.com/angular-ui/bootstrap/blob/master/src/alert/alert.js#L22-L31
<alert ng-repeat="alert in alerts" type="alert.type" dismiss-on-timeout='3000'  close="alert.close()">{{alert.msg}}</alert>

.factory("alertService", [
        "$timeout",
        function ($timeout) {
            var alerts = [];
            var service = {
                add: function (type, msg) {
                    var alert = {
                        type: type,
                        msg: msg,
                        close: function() {
                            alerts.splice(alerts.indexOf(this), 1);
                        }
                    };
                    if (type === "success") {
                        $timeout(function () {
                            alerts.splice(alerts.indexOf(alert), 1);
                        }, 1000);
                    }
                    return alerts.push(alert);
                },
                closeAlert: function (alert) {
                    return closeAlertIdx(alerts.indexOf(alert));
                },
                closeAlertIdx: function (index) {
                    return alerts.splice(index, 1);
                },
                clear: function () {
                    alerts = [];
                },
                get: function () {
                    return alerts;
                }
            };

            return service;
        }
    ])

https://github.com/angular-ui/bootstrap/blob/master/src/alert/alert.js#L22-L31

this doesn't work? or it's only me?

@sarthak-k I am having the same issue. Updated to the latest version in bower but still no dice.

@plattdl Please use dismiss-on-timeout and not dismissontimeout.

//fileName: alert.js
(function (angular) {
'use strict';
angular.module('YourName')
 .factory('alert', ['$rootScope',  function ($rootScope) {
        var alertService;
        $rootScope.alerts = [];
        return alertService = {
            add: function (type, msg, timeout) {
                return $rootScope.alerts.push({
                    type: type,
                    msg: msg,
                    close: function () {
                        return alertService.closeAlert(this);
                    }
                });
            },
            closeAlert: function (alert) {
                return this.closeAlertIdx($rootScope.alerts.indexOf(alert));
            },
            closeAlertIdx: function (index) {
                return $rootScope.alerts.splice(index, 1);
            },
            clear: function () {
                $rootScope.alerts = [];
            }
        };
    }
]);

})(window.angular);
//fileName: alert.html  ---- use ( ) in your index.html
//the dissmissOnTimeout directive from ui-bootstrap needs to have the dashes when reference directives;  dismiss-on-timeout="20000"

{{ alert.msg }}

//Your controller that uses the new alert service....
angular.module('????')
.controller('YourCtrl', ['$scope',  'alert', function ($scope, alert) {
        $scope.submit = function () {
            alert('success', 'Thanks for coding!');
        };
    }]);

thanks twmulloy and others that shared their code so I could get this working


Error in javascript file

no matter where I am in a javascript file, the following error constantly pops up:
Error detected while processing CursorHold Autocommands for "<buffer=48>":
E5108: Error executing lua ...-commentstring/lua/ts_context_commentstring/internal.lua:72: attempt to index local 'language_tree' (a nil value)

Hey! That seems strange.
Do you have the latest Neovim nightly version? Language tree was added to Neovim a few months ago, so if you have recently updated Neovim, then that shouldn't be a problem.
Another thing to check is if you have the javascript treesitter parser installed (:TSInstall javascript).
If none of those are the case, then could you share some minimal init.vim to reproduce this?

I could also add an extra if statement to check if the language_tree is set in front of lua/ts_context_commentstring/internal.lua:72. It would avoid the error, but might effectively disable the plugin for you.

Just to let you know, I added an extra check for this so you should no longer get that error, but commentstring calculation won't work in that case. Maybe the issue will be fixed by one of the ideas in the previous comment.
Anyways, let me know how it goes!

I will close this issue for now, if the issue still persists, then feel free to re-open.


[Bug]: Unable to obtain an available random port number

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
I should be able to run shopify dev --tunnel-url=https://my-project.ngrok.io:8082 and start a dev server.
Actual behavior
After following the upgrade directions on the Shopify developer website, the shopify app dev app fails:
shopify app dev --tunnel-url=https://my-project.ngrok.io:8082

Note that this command needs more documentation. It took me a while to figure out that the port number was meant to be the local port number that ngrok is mapped to. I eventually got that sorted only to be met with this error:
frontend | bbbbbb Error bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
frontend |     Unable to obtain an available random port number!
frontend |
frontend |     Stack trace:    at getRandomPort              shopify/node_modules/get-port-please/dist/index.mjs:129
frontend |     at processTicksAndRejectionb&  node:internal/process/task_queues:96
frontend |     at getRandomPort              shopify/node_modules/@shopify/cli-kit/src/port.ts:10
frontend |     at dev                        shopify/node_modules/@shopify/app/src/cli/services/dev.ts:65
frontend |     at run                        b&fy/node_modules/@shopify/app/src/cli/commands/app/dev.ts:73
frontend |
frontend | bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb

The CLI seems to be falling over just after getting the tunnel host and the frontend port, then crashes on await getRandomPort()
I don't know what could be causing this but I doubt it's a bug in get-port-please. I created an empty project and was able to get a random port number directly from that library without having a crash.
Stack trace
No response
Reproduction steps

run shopify dev with tunnel-url option set
choose existing organization
choose existing app
boom

Operating System
Mac OS Monterey
Shopify CLI version (check your project's package.json if you're not sure)
3.0.25
Shell
zsh
Node version (run node -v if you're not sure)
16.13
What language and version are you using in your application?
Node 16.13

Hi @weeksie, thanks for opening up an issue! I've not managed to reproduced locally yet, but in the meantime, I'm curious if you've tried creating a new app and seeing if the same error appears. (I did exactly that on the same CLI version and didn't see anything...)
Are you using Docker? It's possible that interferes with things as well.

Hi @amcaplan thanks for the response. Just now I was able to use yarn create @shopify/app and start a server in a bare directory with a scaffold project.
I figured out the problem—entirely on me. In the shuffle of moving package.json files, I had a copy of the generated package.json in my /web directory so the startup script was calling shopify dev --tunnel-url=... instead of vite dev
my b. Thanks again for the response.

Hey @weeksie, thanks for the update! I appreciate you keeping us in the loop, as it frees up our time to help other users who have run into issues.
I'm glad it worked out!

Sure thing, @amcaplan . The documentation for the cli is extremely sparse and I am still finding myself reading through your source code for answers to questions like:

How is my backend being proxied now?
Why were my callback urls overwritten in my app settings?
What exactly is that port number for in the tunnel-url?

And several more, I'm sure, since I'm still on this magical journey of discovery ;)
In any case, Shopify seems to write perfectly good code but as a client developer it's a little frustrating not to have clear documentation of what's happening behind the scenes. Would love to know if there's a roadmap for documenting that functionality. I'm migrating an app that was already in development so I may not be the most common use case, but the lack of documentation is causing a fair bit of friction since the happy path is clearly not working out for my configuration and I keep ending up in dark corners.

Sure thing, @amcaplan . The documentation for the cli is extremely sparse and I am still finding myself reading through your source code for answers to questions like:

How is my backend being proxied now?
Why were my callback urls overwritten in my app settings?
What exactly is that port number for in the tunnel-url?

And several more, I'm sure, since I'm still on this magical journey of discovery ;)
In any case, Shopify seems to write perfectly good code but as a client developer it's a little frustrating not to have clear documentation of what's happening behind the scenes. Would love to know if there's a roadmap for documenting that functionality. I'm migrating an app that was already in development so I may not be the most common use case, but the lack of documentation is causing a fair bit of friction since the happy path is clearly not working out for my configuration and I keep ending up in dark corners.

We know the experience is not as smooth as it should be sometimes, but we are working hard to improve it.
Regarding the URL update, we are planning to improve it by overwriting only tunnel-like URLs.


dot: expose simple client/server interfaces direclty via dot package

Finally, the root package exposes simple entry-points for the most common use cases.

Codecov Report

Merging #250 into master will decrease coverage by 0.22%.
The diff coverage is 90.9%.

@@            Coverage Diff             @@
##           master     #250      +/-   ##
==========================================
- Coverage   99.18%   98.96%   -0.23%
==========================================
  Files          67       59       -8
  Lines        2954     2407     -547
==========================================
- Hits         2930     2382     -548
  Misses         13       13
- Partials       11       12       +1

Flag
Coverage Δ

#dot
98.96% <90.9%> (?)

#dot_changes
100% <ø> (ø)
:arrow_up:

#dot_changes_diff
100% <ø> (ø)
:arrow_up:

#dot_changes_run
100% <ø> (ø)
:arrow_up:

#dot_changes_table
100% <ø> (ø)
:arrow_up:

#dot_changes_types
100% <ø> (ø)
:arrow_up:

#dot_example
100% <ø> (ø)
:arrow_up:

#dot_ops
98.43% <75%> (ø)
:arrow_up:

#dot_ops_bolt
97.61% <ø> (ø)
:arrow_up:

#dot_ops_nw
98.91% <ø> (ø)
:arrow_up:

#dot_ops_pg
97.45% <75%> (+0.06%)
:arrow_up:

#dot_refs
100% <ø> (ø)
:arrow_up:

#dot_streams
98.95% <ø> (ø)
:arrow_up:

#dot_streams_undo
100% <ø> (ø)
:arrow_up:

#dot_test_seqtest
100% <ø> (ø)
:arrow_up:

#dot_x_dotc
93.75% <ø> (ø)
:arrow_up:

#dot_x_fold
100% <ø> (ø)
:arrow_up:

#dot_x_heap
?

#dot_x_rt
?

#dot_x_ui_collab
?

#dot_x_ui_dom
?

#dot_x_ui_html
?

#dot_x_ui_input
?

Impacted Files
Coverage Δ

client.go
100% <100%> (ø)

ops/pg/pg.go
97.45% <75%> (+0.06%)
:arrow_up:

server.go
86.66% <86.66%> (ø)

x/ui/collab/keyboard.go

x/ui/html/html.go

x/ui/html/reconciler.go

x/ui/html/events.go

x/ui/collab/text.go

x/ui/dom/dom.go

x/rt/formatted.go

... and 5 more

Continue to review full report at Codecov.

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


feat(directive): add support for tel input fields

@gergderksons awesome! Thanks for the contribution.
Please strip out the changes in dist as we will update it when we bump the version after accepting this PR. Cool?

@bighappyface done :smile:

@gergderkson sorry to nitpick, but would you remove the permission changes on those files as well? We don't need that tracked under version control and you can avoid that stuff by running git config core.filemode false

@bighappyface My bad. That's it fixed.  Cheers for the pointer!

+1

Hi @gergderkson, thanks for adding the test cases! Woot! input type="tel" support!


proxy use switchomega  restart iframe

Runing 'npm start' works mormally at localhost:8080(i change port 3000->8080)
i use 'SwitchyOmega' Proxy xxx.xx.xx to localhost:8080, change the url to xxx.xx.xx
After the execution, 9 iframe pass pages are loaded at the same time
Expected Behavior
(Do not understand why it will not open 9 iframes and still perform the same address domain name)
Reproducible Demo
(Starting a create-react-app project without changing any code only use 'SwitchyOmega' Will reproduce)

This may be because of a extension in your browser, can you try opening it in an incognito/private mode and try again?

incognito/private mode is not taking the switchOmega agent,
localhost running is ok
but The project interface requires domain name and cookie validation so I have been using this proxy,
There is no problem with using this proxy in the vue project. .
I want to ask what mechanism will conflict with the browser proxy, and always restart the iframe
I hit the console in the template file Index.html and found that multiple executions should be the entire page being loaded multiple times. Conflict with this agent


Use fork of package with relay-compiler@2 installed

What do you think about this @josh? This can unblock me from updating things since we can update everything to use graphql@14.
The fork is: https://github.com/danielholmes/relay-compiler-webpack-plugin/compare/master...koddsson:relay-compiler-2

@koddsson have you considered open a PR for https://github.com/danielholmes/relay-compiler-webpack-plugin/compare/master...koddsson:relay-compiler-2? I think danielholmes would accept it upstream.

@josh Sounds good! I created https://github.com/danielholmes/relay-compiler-webpack-plugin/pull/32


return error and fix error handling when io.Copy fails in Digest

This PR corrects an oversight in #5672. My apologies.
Requesting your review @bacongobbler @technosophos @hickeyma

Thanks for the review comments. Fixed.


feature: opentelemetry for the gRPC plugin

Reason for This PR
https://github.com/roadrunner-server/roadrunner/issues/1313
Description of Changes
Possibility to use telemetry for gRPC
Doc: https://github.com/spiral/roadrunner-docs/pull/127
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

[ ] All commits in this PR are signed (git commit -s).
[ ] The reason for this PR is clearly provided (issue no. or explanation).
[ ] The description of changes is clear and encompassing.
[ ] Any required documentation changes (code and docs) are included in this PR.
[ ] Any user-facing changes are mentioned in CHANGELOG.md.
[ ] All added/changed functionality is tested.

Hey @cv65kr 👋🏻
Nice 👍🏻
One note, in the v2023 we're going to move the otel configuration out of the http. It should be available like a plugin's configs as a top yaml key.

@rustatian I push one small change for propagators, now should looks like final PR


Update djsEval.md

Makes more sense imo (although function name hella conflicting)

I mean, technically that's not wrong and the name implies it to be "discord**.js**" related.. so there shouldn't really be an issue.


Restart Flows not working

What are the steps to reproduce?
Click on "Restart Flows"
What happens?
A notification appears:
Deploy failed: {"code":"unexpected_error","message":"runtime.flows.loadFlows is not a function"}
What do you expect to happen?
Flows restarted without errors.
Please tell us about your environment:
Node-RED version: v1.2.1
Node.js version: v12.19.0
npm version: v6.14.8
Platform/OS: Windows_NT 10.0.18363 x64 LE
Browser: Chrome 86.0.4240.75

Fixed in 1.2.2


Animations should track data points when data changes

Expected Behavior
I'm building a scatter chart where the data changes on user interaction. Say there are 10 data points. When user presses a button, only 5 of those points are shown and the rest of them are filtered out.

I believe right now ChartJS uses the index of the point in the dataset to calculate which points to animate out/in. I propose an optional property key which would act similarly to how it's used in ReactJS. When the dataset changes, all points which are removed from the new dataset will be animated out, and any points with new keys will be animated in. All other points which were retained will only change their x and y positions depending upon the axes, etc.
Current Behavior
The points get animated in a haphazard way and confuse the user as to which points were retained and which got removed.
Possible Solution
We might be able to make use of an additional property called key on the data point, which would be passed to the animation module which can decide which points to animate.
Steps to Reproduce (for bugs)

Live demo of current behaviour: https://codesandbox.io/s/nn919nw7pm

Context

Environment

Chart.js version: 2.7.0
Browser name and version: Chrome 68
Link to your project: https://codesandbox.io/s/nn919nw7pm

This is actually an limitation of the react wrapper. If you modify the data array in-place, the changes are tracked. The wrapper does not seem to support this.

Closing per the above comment since this is working in v3.x


feat:  drop foreign key after dropping primary key that is referenced by the foreign key

Proposed changes
cascades drop foreign key after dropping primary key

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Mercatox withdrawal

My Mercatox withdrawal is not showing up in PWR explorer, and Mercatox swears it was sent. Could you please let me know if the explorer is updated? Tx is attached.

The blockexplorer was out of sync, i am fixing it now. thanks for bringing this to my attention.

if the last blocknr doesnt match the total blocks reported in the lower right corner it usually means the background sync job has stalled... ( it's a cron job ).
I will post here when the explorer is back in sync.

The explorer is now in sync, please let me know if you see your TX now.

I see it. Thank you.
On Friday, July 19, 2019, 02:02:14 AM EDT, Gary Hobson<EMAIL_ADDRESS>wrote:
The explorer is now in sync, please let me know if you see your TX now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ack, this tx isn't showing up either: 8c070421ea7ec71c7d3de258f1b5cfc5a30d33bf6a9447f41408277017f67b8f

The block explorer stalled again, I am investigating...
re-syncing....

I have applied the patch from https://github.com/iquidus/explorer/pull/67 , this should take care of this issue.

Mercatox and Crex24 exchanges are both tested and working properly so I am closing this issues. Many thanks to ghobson for pressuring Mercatox and getting a reasonably fast result!


[ColorPicker] Offer a "FloatingPoint" option

Provide a description of the new feature / enhancement
When working with float-point colors in game development we usually define colors as a tuple of 3 to 4 floats which encodes each channel from 0..255 to 0.0..1.0
I think adding a FloatingPoint option should be straightforward.

believe this is https://github.com/microsoft/PowerToys/issues/9966.
My biggest q is sending us proper documentation on how to do this to validate.  I think the ScA, ScR, ScG, ScB values are correct but want to be sure.


chore(.travis.yml): fix e2e tests on Travis (run on latest Chrome)

Previously, the tests would always fail/not run, because our current version of WebDriver requires a
newer version of Chrome than the one installed on the VM.

Some notes:

Our current version of WebDriver requires Chrome 46 or newer.
The default OS on Travis VMs is Ubuntu 12.04 (at the moment), which is not compatible with the latest Chrome (v51).
This PR switches to beta Travis feature: Ubuntu Trusty (14.04), which (at the moment) is compatible with the latest Chrome.
This PR also introduces directConnect: true for running the tests with scripts/private/test-all.sh, which avoids having to specify the binary Chrome path on Travis and speeds up the tests.

--
Possible alternative solutions:

Run the tests on Firefox.
Use Travis' docker support to pull down and run the tests inside a container with a more recent OS version.
Use an external provider, such as SauceLabs and/or BrowserStack.

LGTM!!


exercise 4 problem statement missing information

Problem expects
<Todo title="Learn React">15:00</Todo>

But instructions say to add
<Todo>15:00</Todo>

NVM, I see further instructions clarify to add the title.


intermediate__dev.wdi Is timing out

The model intermediate__dev.wdi is taking several minutes to run and will often time out
Logs below:
[feat/add_shared_state][~/clients (local)/United Nations/osaa-mvp]$ docker compose run --rm pipeline transform
New environment `dev` will be created from `prod`
Summary of differences against `dev`:
Models:
└── Added:
    ├── intermediate__dev.opri
    ├── .... 9 more ....
    └── wdi__dev.series
Creating physical table ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100.0% • 11/11 • 0:00:03

All model versions have been created successfully

[1/1] opri__dev.data_national evaluated in 2.05s
[1/1] opri__dev.label evaluated in 0.29s
[1/1] sdg__dev.data_national evaluated in 1.22s
[1/1] sdg__dev.label evaluated in 0.30s
[1/1] wdi__dev.csv evaluated in 4.82s
[1/1] wdi__dev.series evaluated in 0.42s
[1/1] intermediate__dev.opri evaluated in 1.02s
[1/1] intermediate__dev.sdg evaluated in 0.64s
Starting wdi_data
/usr/local/lib/python3.11/site-packages/ibis/selectors.py:82: FutureWarning: `r` is deprecated as of v9.5; use `ibis.selectors.index` instead
  util.warn_deprecated(
Completed wdi_data
Starting wdi_label
Completed wdi_label
Starting wdi_label
Evaluating models ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺━━━━━━━━━━ 72.7% •  8/11 • 0:01:24
intermediate__dev.wdi ..                                                          /app/entrypoint.sh: line 4:     7 Killed                  sqlmesh plan --auto-apply --include-unmodified --create-from prod --no-prompts "${TARGET:-dev}"

This resolved after other changes were made


ENH: added sort by due date option to issue command

You can now use -sorted or -s to sort personal issues by due date. I also added a due date column when printing issues summary.

Closing this PR as it contents code related to a personal project, ideally, we'd like to create a sorting param with more options :)


Add webpack 5 support

What kind of change does this PR introduce? (bugfix, feature, docs update, improvement)
feature
What is the current behavior? (You can also link to an open issue here)
Now it doesn't work with Webpack 5
What is the new behavior (if this is a feature change)?
It should work with Webpack 5
Does this PR introduce a breaking change?
no
Please check if the PR fulfills contributing guidelines
ok
It's is related with #359

It seems like webpack-toolkit isn't compatible with webpack 5
$ yarn test:webpack-5
...
internal/modules/cjs/loader.js:626
    throw err;
    ^

Error: Cannot find module 'webpack/lib//MultiEntryPlugin'
Require stack:
- E:\projects\svg-sprite-loader\node_modules\webpack-toolkit\lib\addEntry.js
- E:\projects\svg-sprite-loader\node_modules\webpack-toolkit\index.js
- E:\projects\svg-sprite-loader\test\utils\create-compiler.js
- E:\projects\svg-sprite-loader\test\utils\index.js
- E:\projects\svg-sprite-loader\test\loader.test.js
- E:\projects\svg-sprite-loader\node_modules\mocha\lib\mocha.js
- E:\projects\svg-sprite-loader\node_modules\mocha\index.js
- E:\projects\svg-sprite-loader\node_modules\mocha\bin\_mocha

Any updates on this? Is Webpack v5 support planned / expected?

svg-sprite-loader

please close this PR to avoid confusion as its already solved by:
https://github.com/JetBrains/svg-sprite-loader/pull/403


Added a convenience function to create a random color.

For having such a small amount of files, the package structure is quite alien to me, where are the tests? 😄

Thanks for your interest in the colour. I read your code, what is your rationale for this addition ? While I can see the functionality, I'm afraid of 2 points:

Adding function to do one liners need to be though through.
Your implementation seems to impose (hardcode) an RGB color space uniform probabilty to pick color. But what about HSL, or any other perspective ?
It seems that you are unaware of the pick_for, picker arguments, which are documented are probably very very close to what you want. I still understand that you might not need to pick a color for a specific entity in your code, but I would really be happy to hear more about such usage.
I'm not sure what is the use of your colour Factory. What is the rationale behind ?

In general, maybe you could have answered to these questions already by writing and documenting the functionality itself in README.rst or in the doc of your functions/methods so as to convey to users and to reviewers your intention. This is of course missing (we need test and doc) and maybe stems from your ignorance of where are the tests... Well, there is 96% of coverage because every functionality is documented in the README.rst and some docs provided for methods, or objects in colour.py, all this is automatically run by CI to insure us that every functionality is correctly presented in intention to users and that this doc is correctly tested. This is doctest.
To run all these tests you can use: nosetests -sx .

The rationale is that it's more intuitive and convenient but I'll just keep this in my fork

I'm sorry if my answer seemed dry or offended you in any way. I hope I succeeded in sharing about how code inclusion can be added to the project (rationale in docs and tests). Any discussion is welcome here. I'm still curious and interested to hear more about the rationale (example of usage, and why you would need a random color without affecting it to at least an identifier), I feel these could be existing, but can't figure how exactly. While I can understand why you would qualify your proposal as "more intuitive and convenient", I'm not sure it can be alone answering the multiple points I have taken the time to pinpoint.

Oh I closed it because I'm not experienced enough in either nosetests (I'm used to unit tests) or colors to adequately address  your points and turn this into a qualitative pull request :) Thanks for taking your time to look into this.


Add IoT core service renewal info to the setup wizard in the README

The subscription to the IoT core service in the Tuya account expires, and after expiration the wizard won't be able to fetch data from the Tuya cloud anymore. I have added a paragraph to the guide in the README to clarify that it is possible to renew this subscription.

Thanks @lorumic ! This is a helpful addition to our documentation. 🙏


Converted Waymo Visualization

I face the same problem as mention in #1071 . I also use this visulization tool: https://github.com/kuixu/kitti_object_vis
The visualizaion of converted waymo dataset looks wired.
The bounding boxes are under point cloud.
At first, I thought it was the problem of visulization tools.
However, the visualization of original kitti  and customized data are correct.


Faster screen updates

Specifying demo = True incurs a 2sec wait in EPD.
I have not seen any ill-effects from this change. Regular screen updates in each main() cycle render much quicker (presumably 2s quicker! Overall more like 0.5s) and just feels smoother.

Great finding @kdmukai


ARROW-14653: [R] head() hangs on CSV datasets > 600MB

This PR switches to using the asynchronous scanner by default when reading in datasets.  I've tested it locally on a large dataset (2.5Gb of CSV files) and it does resolve the original issue, but due to the size of the files involved I wasn't sure this was something I could easily write tests for.

@ursabot please benchmark lang=r

@ursabot please benchmark lang=R

@ursabot please benchmark


parseErc6492Signature is not experimental anymore

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

Review Error for eric-ships @ 2024-09-11 20:52:32 UTC
User must have write permissions to review


properly shutdown query client with await termination

Previously we didn't shutdown GRPCQueryClient managed channel properly.
This should fix https://github.com/apache/pinot/issues/8684
see stress test result in https://github.com/apache/pinot/pull/8767 (https://github.com/apache/pinot/runs/6948759053?check_suite_focus=true)

Codecov Report

Merging #8922 (4f6c5bc) into master (dd1894d) will decrease coverage by 3.38%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #8922      +/-   ##
============================================
- Coverage     69.75%   66.37%   -3.39%
+ Complexity     4859     4667     -192
============================================
  Files          1809     1356     -453
  Lines         94331    68486   -25845
  Branches      14069    10691    -3378
============================================
- Hits          65805    45456   -20349
+ Misses        23938    19779    -4159
+ Partials       4588     3251    -1337

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
66.37% <0.00%> (-0.04%)
:arrow_down:

unittests2
?

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

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


Feature: Add kubeconfig flag to allow user to select a specific kubeconfig file to use

Is your feature request related to a problem? Please describe.
When running krr It uses the config for authorization in Kubernetes.
This is a pain for developers that don't maintain a single merged kubeconfig.
Describe the solution you'd like
Add a --kubeconfig flag that will specify the kubeconfig that you want to use when running krr

Sounds like a good small feature to implement


meta tags/images for articles

so discourse (etc) can generate a preview.

I'll just follow ghost's example.

Done.
http://iframely.com/debug?uri=https%3A%2F%2Fdarksky.io%2Fgps-clock.html

@frillip try to tweet this URL: https://darksky.io/gps-clock.html to see if twitter picks it up properly


Support per-source matching?

As per https://github.com/roxma/nvim-completion-manager/issues/123#issuecomment-324838171
// cc @katsika
This is still open for discussion. It may or may not get implemented.
Here's my rough sketch:
Add an integer option custom_match, 0 by default. If it's set to 1, NCM won't filter, and sort the candidates of this source.
The source could use NCM's built-in maching on its own, via from cm_matchers.{module} import Matcher. Or it could use any other algorithms.

source custom matcher is implemented in ncm2.


Merge create_physical_skeleton undo entries.

Pressing ctrl+z after clicking "Create Physical Skeleton" will now
undo the creation of all physical bones by that operation.
Previously undo would remove one bone at a time.
Fixes https://github.com/godotengine/godot/issues/55351.

Thanks!

Cherry-picked for 3.5.

Cherry-picked for 3.4.3.


Add KKOS Berlin to list of schools

KKG is a maths and CS focused school in Berlin, Germany.
We offer advanced CS courses (2 years) from 11th to 12th grade. Students can also enroll into "Frühstudium", an early offer to start CS courses from university early before graduation.
https://www.kaethe-kollwitz-gymnasium.de/fachbereiche/mint/informatik/
kkos.net is used for mails only. The abbreviation stems from "Käthe-Kollwitz-Oberschule", the former name of the school.

@hoelscher-berlin The first verification stage is complete: the official domain for  Käthe-Kollwitz-Gymnasium Berlin is www.kaethe-kollwitz-gymnasium.de, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.kaethe-kollwitz-gymnasium.de/

The domain used for mails is kkos.net, you can check that on https://www.kaethe-kollwitz-gymnasium.de/kontakt/ where many mail addresses are listed.

@hoelscher-berlin The first verification stage is complete: the official domain for  Käthe-Kollwitz-Gymnasium Berlin is www.kaethe-kollwitz-gymnasium.de, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.kaethe-kollwitz-gymnasium.de/

@hoelscher-berlin Thank you for your patience while waiting for a review and processing your request. Pull request merged.


MTLCommandEncoder Type

I have some questions about the MTLCommandEncoder type.
In the BasicOperation , all the operations like Color processing , Blend use the MTLRenderCommandEncoder to process the image and pass to next ImageConsumer. Why not use the MTLComputeCommandEncoder to do the image process work ? Since not every filter need to render to the view.  and MTLComputeCommandEncoder can do data-parallel compute which maybe more effective.
Is there any considerations to use MTLRenderCommandEncoder ?

The two reasons we are using render operations initially over compute are a) ease of porting and b) last time I'd checked, the render pipeline was faster than compute for equivalent operations. The previous iterations of GPUImage used OpenGL (ES) shaders and by necessity were built around a rendering architecture. That makes it easier to translate those operations into another rendering architecture, this time in Metal, instead of reworking them for compute right off the bat.
An old Apple Developer Forum thread talks about performance differences that people observed initially when it comes to compute vs. render operations in Metal. I saw something similar in my initial tests years ago, but I don't know if any of that is still the case today. This hardware was originally built and optimized for rendering, but so much has been done on the compute side over the last few years that none of that may be true anymore.
This is something that we'll clearly be benchmarking as we get things stabilized, along with side-by-side comparisons with Metal Performance Shaders for relevant operations. I'm sure we'll learn quite a bit out of that. If it turns out that compute allows for better performance, we'll rework to target that.
The current simple shaders we have run so quickly on Metal-supporting devices that it's hard to benchmark differences in their performance. You're looking at maybe sub-millisecond timing changes on current hardware, so we'll need to come up with good test cases and run on as old of hardware as we can, on up.


On inplace/lib/bin vs. inplace/bin

make puts utilities in inplace/lib/bin, while the current shake build system puts them in inplace/bin, which I think is the saner solution, found this while trying to fix #35.
This is also relevant to #44, in that we might place template-hsc.h into inplace as well?

My first guess would be to put binaries into bin and header files into include. Isn't that a standard approach?

Me too. I guess, the wrapper we put into bin and the binary and includes into lib/bin and lib/includes then.
Maybe we should follow a different naming scheme with the wrapper?
Say _cmd being the binary, and cmd being the wrapper around _cmd?

I propose not to change this convention for now, because we may accidentally break some usage patterns occurring outside of the build system. This is somewhat similar to the wrappers story (#38): the build system may not need them, yet users may still want wrappers to exist.
Let us put utilities into inplace/lib/bin then as make does.

As I understand only the following utilities are placed into inplace/lib/bin: ghc-split, touchy and unlit. Since we don't build them yet (touchy seems unnecessary, unlit waits for c-only packages to be supported, ghc-split lives in driver which is not yet built), I think we can close this issue for now -- there is nothing to change in the current implementation of the build system. But I'll keep this in mind when adding build rules for these utilities.

Alright, here's a dump of tree for inplace after make.
inplace
├── bin
│   ├── deriveConstants
│   ├── dll-split
│   ├── genapply
│   ├── genprimopcode
│   ├── ghc-cabal
│   ├── ghc-pkg
│   ├── ghc-stage1
│   ├── hp2ps
│   ├── hsc2hs
│   └── mkdirhier
└── lib
    ├── bin
    │   ├── deriveConstants
    │   ├── genprimopcode
    │   ├── ghc-pkg
    │   ├── ghc-split
    │   ├── ghc-stage1
    │   ├── hsc2hs
    │   ├── unlit
    │   └── unlit.bin
    ├── package.conf.d
    │   ├── Cabal-<IP_ADDRESS>.conf
    │   ├── array-<IP_ADDRESS>.conf
    │   ├── base-<IP_ADDRESS>.conf
    │   ├── binary-<IP_ADDRESS>.conf
    │   ├── bytestring-<IP_ADDRESS>.conf
    │   ├── containers-<IP_ADDRESS>.conf
    │   ├── deepseq-<IP_ADDRESS>.conf
    │   ├── directory-<IP_ADDRESS>.conf
    │   ├── filepath-<IP_ADDRESS>.conf
    │   ├── ghc-7.11.conf
    │   ├── ghc-boot-7.11.conf
    │   ├── ghc-prim-<IP_ADDRESS>.conf
    │   ├── ghci-7.11.conf
    │   ├── haskeline-<IP_ADDRESS>.conf
    │   ├── hoopl-<IP_ADDRESS>.conf
    │   ├── hpc-<IP_ADDRESS>.conf
    │   ├── integer-gmp-<IP_ADDRESS>.conf
    │   ├── package.cache
    │   ├── pretty-<IP_ADDRESS>.conf
    │   ├── process-<IP_ADDRESS>.conf
    │   ├── rts.conf
    │   ├── template-haskell-<IP_ADDRESS>.conf
    │   ├── terminfo-<IP_ADDRESS>.conf
    │   ├── time-1.6.conf
    │   ├── transformers-<IP_ADDRESS>.conf
    │   └── unix-<IP_ADDRESS>.conf
    ├── platformConstants
    ├── settings
    └── template-hsc.h

I hope, I didn't have too many shake / make artifacts in there.

Do I understand correctly that inplace/bin/ghc-stage1 is actually a wrapper around ``inplace/lib/bin/ghc-stage1`?

Do I understand correctly that inplace/bin/ghc-stage1 is actually a wrapper around `inplace/lib/bin/ghc-stage1?

Yes exactly. Here’s the contents of inplace/bin/ghc-stage1 on my system.
#!/bin/sh
executablename="/Users/angerman/Projects/Haskell/ghc/inplace/lib/bin/ghc-stage1"
datadir="/Users/angerman/Projects/Haskell/ghc/inplace/lib"
bindir="/Users/angerman/Projects/Haskell/ghc/inplace/bin"
topdir="/Users/angerman/Projects/Haskell/ghc/inplace/lib"
pgmgcc="/usr/bin/clang"
export DYLD_LIBRARY_PATH="/Users/angerman/Projects/Haskell/ghc/compiler/stage1/build:/Users/angerman/Projects/Haskell/ghc/libraries/transformers/dist-boot/build:/Users/angerman/Projects/Haskell/ghc/libraries/template-haskell/dist-boot/build:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/prett_7UQTOB05U7lIYPkFOVraeR:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/proce_FLTz0SLwyG6LJUpZ52HjkU:/Users/angerman/Projects/Haskell/ghc/libraries/hpc/dist-boot/build:/Users/angerman/Projects/Haskell/ghc/libraries/hoopl/dist-boot/build:/Users/angerman/Projects/Haskell/ghc/libraries/ghc-boot/dist-boot/build:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/direc_KowvXytSqazBcvN7MGpFtg:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/unix_A3WgcI5QiHK4PDo4jSYdwQ:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/time_AXTdBF9VRQoBOqJT6qtmVH:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/filep_KsGE6pHE5eZHSN90ZVax6A:/Users/angerman/Projects/Haskell/ghc/libraries/binary/dist-boot/build:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/conta_LKCPrTJwOTOLk4OU37YmeN:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/bytes_6elQVSg5cWdFrvRnfxTUrH:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/deeps_LbCWUlehDDeLxurARKDH5o:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/array_E0sTtauuKsGDLZoT7lTbgZ:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/base_GDytRqRVSUX7zckgKqJjgw:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/integ_2aU3IZNMF9a7mQ0OzsZ0dS:/usr/local/Cellar/ghc/7.10.2/libexec/integer-gmp/lib:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/ghcpr_8TmvWUcS1U1IKHT0levwg3:/usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/rts${DYLD_LIBRARY_PATH:+:$DYLD_LIBRARY_PATH}"
exec "$executablename" -B"$topdir" ${1+"$@“}


Cannot add new device from helper

When using add bridge from a helper for the first time, it does not add the device.

When first building a device, the settings for editing are set so the device cannot be added.


Webview resources not loading - ERR_UNKNOWN_URL_SCHEME (vscode-insiders)

Version: 1.47.0-insider (user setup)
Commit: 0913b1aa43191d8af0ccb4a133d9a8d7c1a81d69
Date: 2020-06-23T09:03:35.861Z
Electron: 8.3.3
Chrome: 80.0.3987.165
Node.js: 12.13.0
V8: 8.0.426.27-electron.0
OS: Windows_NT x64 10.0.18362

I'm the author of the Git Graph extension. This bug is affecting all Git Graph users that use Visual Studio Code Insiders, as well as every other extension I'm aware of that loads resources (e.g. CSS, JS) in Webview's (more specifically, resources loaded by Webview.asWebviewUri). I can replicate bug on Windows & Mac, I've had reports of this from many users.
Steps to Reproduce:

Install an extension that uses a Webview (Git Graph for the following steps)
Open Visual Studio Code in a Git repository.
Click the "Git Graph" Status Bar Item
Observe that the CSS & JS resources aren't loaded:

If you run the Visual Studio Code command "Open Webview Developer Tools", the following errors can be seen:

Does this issue occur when all extensions are disabled?: No (Because it only affects extensions that use Webview's)
The resolution of this issue is being tracked for Git Graph users here.

Looping in @mjbvz.

This might also cause an issue with the Draw.io plugin which does not work anymore after updating to the current Insiders version (same version as posted by @mhutchie).

I also see this issue in the Insiders build with markdown preview and with the extension Project Dashboard.

This is also affecting Device Simultor Express

Duplicate of #100879. Should be fixed in the next insiders build

The Draw.io Plug-in works again. Thanks for the fix, @mjbvz!

@mjbvz I've had reports that this was fixed in the Insiders release 9b620b2, however it is broken again for every user I've checked with in:
Version: 1.47.0-insider (user setup)
Commit: 6c235c723cb2d8defb840f732eac620f54aa8b9d
Date: 2020-06-26T06:20:06.931Z
Electron: 8.3.3
Chrome: 80.0.3987.165
Node.js: 12.13.0
V8: 8.0.426.27-electron.0
OS: Windows_NT x64 10.0.18362
How could this occur again?


adding law of cosines calculator

I would like to add a calculator for finding angles of a triangle when sides a, b, c are given using the cosine formula.
Please assign his issue to me @sairish2001

Can I work on this issue @sairish2001 ?

Go ahead with this issue :)
Deadline 21 April 2021 11:59 PM IST


fix NEXT_PUBLIC_PARTYKIT_HOST instruction

Including the https:// in the vercel prod variable results in https://https:// prepended to URL on /chat page

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


Use Data to encode ScriptContext

Extricated from https://input-output.atlassian.net/browse/PLT-7551

Duplicate of https://github.com/IntersectMBO/plutus/issues/5929


Update readme.md

the curly braces are not allowed (jsonSchemaToZod is the default export)

That was an oversight and has been fixed. Please also check contributing guidelines in the future, thanks


Sponsor

Hello
This is Liam from PCBWay, deeply impressed by this project which is novel and creative,
I’d like to sponsor your project by providing free PCB prototyping,
All I ask for in return is a slight promotion or review of our quality or service.
Would you be interested in partnering up? Contact me<EMAIL_ADDRESS>

Hey Liam, I went ahead and sent you an email. I'll close this issue for now so we can talk through email. Glad you liked the project!


why the finetuning takes more time compared with alpaca

Alpaca's finetuning takes about 3h, however for gpt-4 data in this repo, it needs about 13h on 8 A100 GPUs. What is the difference?

Can you increase the batch size to 4?


Could not find method implementation()

React Native version: 0.56.0
react-native-fast-image version: 5.0.10
When running react-native run-android I'm getting a build error:
* Where:
Build file '/Users/oskar/Documents/Coding/SHL/app/node_modules/react-native-fast-image/android/build.gradle' line: 55

* What went wrong:
A problem occurred evaluating project ':react-native-fast-image'.
> Could not find method implementation() for arguments [com.facebook.react:react-native:+] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Any idea on how to solve this?

me too.

i am having the same issue