Problem with include path

Checklist

[X ] Check that you have the GNU C Compiler installed by typing gcc --version into a terminal.
[ X] If you don't have the linter package installed, either update to the latest version of linter-gcc or install linter directly with apm install linter.
[X ] Ensure that you are using a valid grammar - either C/C++/C++14
[X ] Ensure that you have read all the relevant information in the wiki, particularly the Common Issues page.

Issue (including debugging messages):
Hello, we are trying to use Atom with linter-gcc to develop my apps in C++. We can compile my app without problems except when I try to include headers (like opencv), I always have the same message (no such file...) We are using Atom under Windows 10, I'm try to use this file to config:
{
"execPath": "g++",
"gccDefaultCFlags": "-Wall",
"gccDefaultCppFlags": "-Wall -std=c++11",
"gccErrorLimit": 15,
"gccIncludePaths": ".,./include,./path, C:/opencv/include",
"gccSuppressWarnings": true
}
and in my cpp file:
#include
#include
#include <opencv2/core/core.hpp> //<------- The error is here
using namespace std;
int main(int argc, char const *argv[])
{
int i = 90;
cout << "Hola" << endl;
return 0;
}
Im try to use "" and <>, put ./C:/opencv/build....  But I can't to get compile correctly...
Could you help me?
Thank you very much.
Kind regards,

I am also having this problem -- did you ever find a solution?

Hello, I use Eclipse yo solve this problem.
El 3 ene. 2017 12:57 p. m., "corinthosis"<EMAIL_ADDRESS>escribió:

I am also having this problem -- did you ever find a solution?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hebaishi/linter-gcc/issues/91#issuecomment-270099652,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHo2ZDYzZ0Yf5hWP6E-tLSMG5NwUDHD_ks5rOjeLgaJpZM4Kqs_N
.

Thank you! I'll give that a try.
On Jan 3, 2017 2:46 PM, "JaviEC"<EMAIL_ADDRESS>wrote:

Hello, I use Eclipse yo solve this problem.
El 3 ene. 2017 12:57 p. m., "corinthosis"<EMAIL_ADDRESS>escribió:

I am also having this problem -- did you ever find a solution?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/hebaishi/linter-gcc/issues/91#issuecomment-270099652
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHo2ZDYzZ0Yf5hWP6E-
tLSMG5NwUDHD_ks5rOjeLgaJpZM4Kqs_N>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hebaishi/linter-gcc/issues/91#issuecomment-270117089,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXTl-kfj9-B7wmUKkuJwXaQDwwJplCXRks5rOlEjgaJpZM4Kqs_N
.


We should use "cloudfront" instead of "cloudfronted"

This fixes #6

merging since it's a hotfix.


⚠ Bofrost.lu has degraded performance

In 0ff1738, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2630 ms

Resolved: Bofrost.lu performance has improved in c401bf6 after 13 minutes.


Implement realtime Ruckig jerk-limited smoothing

Description
Implement jerk-limited smoothing in Servo. This should enable large industrial robots to be controlled in a realtime fashion.
Checklist

[ ] Extend the tutorials / documentation -- I'd like to make a new tutorial about these smoothing plugins since there are 3 of them now.

Test Instructions
Note this change in panda_simulated_config.yaml:  smoothing_filter_plugin_name: "online_signal_smoothing::RuckigFilterPlugin"
That's the only change the user needs to make.  Hopefully the issue you raised there will go somewhere in future.
There seems to be a failing clang-tidy check. Once that is clear (and if you're ready), request review and I'll give it another look.


⚠ Turnos 24x7 has degraded performance

In 9d306ac, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 854 ms

Resolved: Turnos 24x7 performance has improved in 70fb4b1.


Access denied following instructions

Describe the problem
We were previously using auth0-lock
Having followed the instructions on the Auth0 React SDK Quickstart when I attempt to login the redirects all happen then a POST to our auth0 domain /oauth/token endpoint returns a 401 with the following response.
{"error":"access_denied","error_description":"Unauthorized"}

In the Auth0 logs I can see the following rows, but no information as to what is missing
||Type || Description || Date↓ || Connection || Application↓ ||
| Success Login | Successful login | a few seconds ago | Username-Password-Authentication | MCO Admin App|
| Failed Exchange | Unauthorized | 10 minutes ago | N/A | N/A|
What was the expected behavior?
Token endpoint to return a token for use in the app
Reproduction
I tried this in a copy of the Sample code where the only changes made were to create an auth_config.json with the appropriate values
{
  "domain": "xxxxxx.eu.auth0.com",
  "clientId": "xxxxxxxxxxxxxxxxxxx"
}

and in the index.js commented out the line that set the audience in the Auth0Provider
    //audience={config.audience}

I have also had the same issue occur when providing a value for audience.
Environment

Version of auth0-react used: both 1.0.0 and 1.1.0
Chrome, Edge, Firefox
React

Hi @wozzo, could you please check that you're not being affected by this issue?

Yup. Looks like that was it, but now I get
Signature algorithm of "HS256" is not supported. Expected the ID token to be signed with "RS256".

How many other settings need specific values for it work? Is there a document describing the permissible settings?
I think updating this setting would be break our current system until we can roll out the new code.
Am I right in thinking the only way around this would be to create a new application?

Yes if you have apps tied to that Auth0 Application and rely on the HS256 signature algorithm mode, you will need to create a new application that is set to RS256.
The default settings should really work if you're setting up a new Auth0 app - are you using an application that was created quite a while ago, or using the Default App? The default for the signature algorithm for example should now be RS256 (this library does not support HS256 at all), and just make sure Token Endpoint Authentication Mode is set to 'None'.
Creating a new app would be best to get all the defaults, which should work out of the box. If you're able to try that, let me know how you get on.

Was able to get it to work with a new app. Thanks


runtime-qemu port 9000 conflicts with php-fpm default port

I tried running the example web server:
dan@galaxy ~/D/e/example-web-server (master)> npm start

> @1.0.0 start /Users/dan/Development/experiments/example-web-server
> runtimeify index.js -o initrd && runtime-qemu ./initrd

Downloading runtime-download-0.1.14
[============================================>] 100.0% of 9.22 MB (2.17 MB/s)
 --- starting qemu ---
[INITRD] Load /bundle.js len 346471
v0.1.14 kernel (v8 4.5.107)
v0.1.25 core library
loading...
[random] using entropy source js-random
[UDP] no route to <IP_ADDRESS>
listening to port 9000

Then, when trying to connect via curl:
dan@galaxy ~> curl localhost:9000
curl: (52) Empty reply from server

Do I need to manually forward the port in qemu? I thought it was supposed to automatically do it? ;)

@omnidan port 9000 should be forwarded automatically, this looks like the issue with the server itself. What's your host OS? Have you changed the example code? Or you can send me your initrd file and I'll take a look.

OS X and I haven't changed it. I can upload my initrd when I get back home

@iefserge Alright, I uploaded it here: http://caffeinery.org/initrd - Thanks for looking into it :smiley:

@omnidan thanks!
Hm, I'm on OSX and your initrd fine worked for me.
$ curl --verbose localhost:9000
* Rebuilt URL to: localhost:9000/
* Hostname was NOT found in DNS cache
*   Trying ::1...
* connect to ::1 port 9000 failed: Connection refused
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 9000 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.37.1
> Host: localhost:9000
> Accept: */*
>
< HTTP/1.1 200 OK
< connection: keep-alive
< date: Sun, 20 Sep 2015 12:13:55 GMT
< content-length: 12
* Server runtimejs is not blacklisted
< server: runtimejs
<
* Connection #0 to host localhost left intact
Hello World!%

I tried connecting using netcat as well:
nc localhost 9000

Then typed GET / HTTP/1.1 and pressed enter
GET / HTTP/1.1

HTTP/1.1 200 OK
connection: keep-alive
date: Sun, 20 Sep 2015 12:11:29 GMT
content-length: 12
server: runtimejs

Hello World!^C

Maybe network configuration failed for some reason.
What QEMU version do you use? qemu-system-x86_64 --version
You can also enable the debug mode in runtime by changing node_modules/runtimejs/package.json file runtimejs.debug key to true and post the output here.
Thank you! I'm really curious why it fails for you.

QEMU version:
> qemu-system-x86_64 --version
QEMU emulator version 2.4.0, Copyright (c) 2003-2008 Fabrice Bellard

Debug output:
> npm start

> @1.0.0 start /Users/dan/Development/experiments/example-web-server
> runtimeify index.js -o initrd && runtime-qemu ./initrd

 --- starting qemu ---
[INITRD] Load /bundle.js len 346470
v0.1.14 kernel (v8 4.5.107)
v0.1.25 core library
loading...
[random] using entropy source js-random
0:0.0 8086:1237 Bridge Device IRQ: null PIN: dont use
0:1.0 8086:7000 Bridge Device IRQ: null PIN: dont use
0:1.1 8086:7010 Mass Storage Controller IRQ: null PIN: dont use
0:1.3 8086:7113 Bridge Device IRQ: 9 PIN: A
0:2.0 1234:1111 Display Controller IRQ: null PIN: dont use
0:3.0 1af4:1000 Network Controller IRQ: 11 PIN: A
[ ADD ROUTE <IP_ADDRESS>/8 via null loopback ]
{"VIRTIO_NET_F_MAC":true,"VIRTIO_NET_F_GSO":true,"VIRTIO_NET_F_MRG_RXBUF":true,"VIRTIO_NET_F_STATUS":true,"VIRTIO_NET_F_CTRL_VQ":true,"VIRTIO_NET_F_CTRL_RX":true,"VIRTIO_NET_F_CTRL_VLAN":true,"VIRTIO_NET_F_GUEST_ANNOUNCE":true,"VIRTIO_RING_F_NOTIFY_ON_EMPTY":true,"VIRTIO_RING_F_EVENT_IDX":true}
intf add
[UDP] no route to <IP_ADDRESS>
listening to port 9000
recv UDP over IP4 67 68 548
CLIENT OK <IP_ADDRESS> 67 2,1,6,0,0,17,34,51,0,0,0,0,0,0,0,0,192,168,76,9,192,168,76,2,0,0,0,0,26,70,11,202,188,124,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,99,130,83,99,53,1,2,54,4,192,168,76,2,1,4,255,255,255,0,3,4,192,168,76,2,6,4,192,168,76,3,51,4,0,1,81,128,255,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
recv UDP over IP4 67 68 548
CLIENT OK <IP_ADDRESS> 67 2,1,6,0,0,17,34,51,0,0,0,0,0,0,0,0,192,168,76,9,192,168,76,2,0,0,0,0,26,70,11,202,188,124,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,99,130,83,99,53,1,5,54,4,192,168,76,2,1,4,255,255,255,0,3,4,192,168,76,2,6,4,192,168,76,3,51,4,0,1,81,128,255,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
configure dhcp ok {"ip":{"a":192,"b":168,"c":76,"d":9},"mask":{"a":255,"b":255,"c":255,"d":0},"routers":[{"a":192,"b":168,"c":76,"d":2}],"dns":[{"a":192,"b":168,"c":76,"d":3}]}
[ ADD ROUTE <IP_ADDRESS>/24 via null  ]
[ ADD ROUTE <IP_ADDRESS>/0 via <IP_ADDRESS>  ]
recv ARP 2 52:55:c0:a8:4c:02 <IP_ADDRESS> 1a:46:0b:ca:bc:7c <IP_ADDRESS> <IP_ADDRESS>
recv UDP over IP4 53 49152 94
DNS recv <IP_ADDRESS> 53 {"hostname":"pool.ntp.org","results":[{"hostname":"pool.ntp.org","record":"A","address":[91,206,8,70],"ttl":11},{"hostname":"pool.ntp.org","record":"A","address":[178,251,65,44],"ttl":11},{"hostname":"pool.ntp.org","record":"A","address":[193,171,23,163],"ttl":11},{"hostname":"pool.ntp.org","record":"A","address":[194,112,182,172],"ttl":11}]}
recv UDP over IP4 123 49153 48

I hope this helps you :)

@omnidan Thanks! I don't see anything wrong with the server and the network, it was able to configure itself and resolve time server hostname pool.ntp.org. Could this be an issue with your system? maybe firewall? do you have anything else listening to port 9000?

@iefserge ahhh, it seems like php-fpm is running on port 9000 - you might want to change the default port to something else ;)
anyway, I killed php-fpm and it works fine now:
dan@galaxy ~> curl localhost:9000
Hello World!⏎

Thanks a lot!  :+1:

I changed the issue title and I'll reopen it in case you want to consider changing the default port.

Relevant https://github.com/runtimejs/runtime-tools/issues/4

It's kinda pointless to change default port numbers to avoid a conflict. Besides the system ports (0-1023) where there are some well known conventions, port numbers should just be assigned by the user, or allocated automatically. Especially since there are going to be conflicts with just about every nice round-numbered port, and there's no registry to prevent conflicts. For example, php-fpm is also in conflict with the default port for the Hadoop NameNode server and DBGp.
I'd close this and just make it easier to configure via runtimejs/runtime-tools#4

@slang800 you're right :+1: I'll leave it to @iefserge to decide whether or not to close it though

@omnidan @slang800 yeah, let's keep port 9000 and just add on option to change it


Update instrumenting-Node-js-applications-with-open-telemetry.md

fix library name sdk-trace-node to sdk-trace-base

thanks!


Feature/PIMOB-1237: Support multi-flavoured billing form ui for sample app

Jira ticket
[iOS] - Create two custom versions of the new UI for the sample app, Enables testing and helps merchants to view sample code for customisation.

I am not sure we should be continuing the non standard approach to retrieving images from the assets

@alex-ioja-yang-cko Jira ticket for this one is created.
https://checkout.atlassian.net/browse/PIMOB-1227?atlOrigin=eyJpIjoiZDg5MGJkNDlkNDAyNDA4Y2JjYjdjYzY2NDA4OGE5MDAiLCJwIjoiaiJ9


Adapt to networkx >=2.0 which dropped *_iter() methods.

NetworkX dropped the _iter() methods in version 2.0.0; the default predecessor and successor methods return iterators now. Regarding backwards compatibility, I think this change should also work with earlier methods which returned lists, but I haven't tested it.

cheers


ci: update error reference docs

This PR is auto-generated by a nightly GitHub action to update the error reference docs from source code in withastro/astro.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
reference/error-reference.mdx
Source changed, localizations will be marked as outdated.

en
reference/errors/action-called-from-server-error.mdx
Source changed, localizations will be marked as outdated.

en
reference/errors/action-not-found-error.mdx
Source added, will be tracked.

en
reference/errors/actions-returned-invalid-data-error.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Onboarding ticket for Kat

New Pages Team Member Onboarding Checklist for Kat
Special Notes

Do not create this issue until the System Owner has formally authorized and requested it. You can obtain that OK by one of two ways:
A:

[ ] A: System Owner creates this issue

B:

[x] B.1: System owner emails<EMAIL_ADDRESS>and<EMAIL_ADDRESS>with their authorization
[x] B.2: An operator adds links to the email archive of the authorizing email:

https://groups.google.com/a/gsa.gov/g/cloud-gov-compliance/c/NlVQDmr4h58

Please only use first names.

Onboard Kat
Background (Optional)
https://docs.google.com/document/d/1tS-9hLb2yHtp500N3obmu0X70XpIMATuPlov2_vDVS0/edit
Acceptance Criteria

[x] Share README
[ ] Grant appropriate access to Federalist backend in cloud.gov
[ ] Add to federalist-admins
[ ] Add to federalist-admins in federalist-users org.
[x] Add to cloud-gov-team in cloud-gov org.
[ ] Add to pages-ops in cloud-gov org.
[ ] Make owner in the federalist-users org.
[x] Add to #federalist- channels in Slack as needed, and add to @federalist-operators Slack user group
[x] Add to daily standup, retro, and sprint planning
[x] Ensure user has Federalist Github project and brief on its use
[ ] Ensure user has GPG signing set up for GitHub: https://docs.google.com/document/d/11UDxvfkhncyLEs-NUCniw2u54j4uQBqsR2SBiLYPUZc/edit
[ ] Add to federalist-support, federalist-alerts, and federalist-inquiries Google Groups as needed
[ ] Add them as an agent to https://federalist-support.zendesk.com/agent
[ ] add to cloud.gov account at Search.gov
[ ] Add new user as developer to the gsa-18f-federalist cloud.gov cloudfoundry organization
[ ] Add to statuspage.io account as possible and appropriate
[ ] Have a cloud.gov operator add to the “pages.admin” group in the cloud.gov UAA by using the make-pages-admin.sh script
[ ] Have a cloud.gov operator add to the “concourse.pages” team in the cloud.gov OpsUAA by using the make-pages-ops-admin.sh script so they can access Concourse CI
[ ] Add to Docker Hub
[ ] Add to AWS (Production GovCloud only)
[x] Add to cloud.gov calendar

Thanks, @hursey013!


Added Stop-Loss option to any strategy

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This pull request adds a stop loos option to gekko which is an adjustable percentage value stored in the config and parameters backtests.

What is the current behavior? (You can also link to an open issue here)
there is no stop loss handling in gekko right now

What is the new behavior (if this is a feature change)?
If the stop loss option is enabled gekko will bind regular strategy functions to other names Consultant.strategy_${functionName} and use the stop-loss wrapper instead. The wrapper will do it's stop loss calculations and will forward calls to this.strategy_${functionName}(candle) (the original strategy function) afterwards.

Other information:
This started in a weekend night session, works well locally and i'd like to push it back to gekko itself – it's an awesome tool! I haven't touched any tests yet but are willing to add some :)

Hi @joernroeder,
This sounds like a nice feature. I was wondering is it a fixed stop loss or a trailing stop loss?

hi @uipko, yeah, that sounds like a good enhancement!
I'll push some code tomorrow and will fix the typo too.

Hi @joernroeder,
How to implement this stop-loss module to a main strategy like RSI strat for example? Can you give us a guide on how to add it so that I can also test and use this awesome tool for gekko?
Thank you.

@jaguar666 i'm currently working on this and things are not ready yet. Have a look at this comment in the latest commit to see how it works. But be aware as this is all work in progress thinks can change rapidly ;)

@uipko tailing stop loss landed :) feel free to test it out ...

@joernroeder wow that's quick! Will have a test run later this week I'll let you know the results!

@askmike Will this be merged into core? If so do you have an idea when? If not, what needs to be done?

@joernroeder thank you so much for putting this together!  However I'm having difficulty getting it to work.  Do I need TA-lib enabled?  I'm running currently running Windows 8.1 with tulip, perhaps there is a workaround?

Apologies for never getting back to this. Stops are mega important so thanks a lot for this PR.
I like your approach but right now there are a few things I personally want to do differently:

I aiming for one single step of configuration (so make the stop config part of the strat config). Even though alpha (strategy) and execution logic are very different things, there is definitely some overlap as well since very tight stops can and should impact strategy behavior (tight stops in volatile times will get hit more often, etc).
I want the stop losses to be implemented closer to the exchange, the gekko pipeline is slow by design. With the  resolution being minutely data. But the strategy sees even less precise data (depending on candle size). Especially in volatile times Gekko needs to be on top of things (bypassing the Gekko Stream using Gekko Broker).
I want this to be tightly integrated to Gekko Broker order types!

Again apologies, I realize it must be frustrating to have your PR ignored for so long just to hear it won't be accepted. The Gekko project issue tracker had more activity on it in the last few months than I was able to manage :(

hey @askmike no worries. i understand your concerns and have seen that a lot of the gekko code base has changed in the last few month. If you have another idea how to implement this which fits better into the current design than go for it, if my work inspired you to find an (even) better solution than perfect – this is what open source is all about ✌!

It very much did! I do very much want to do this once properly, so I'm
still in the process of figuring out a clean API.
On Tue, Jul 31, 2018 at 6:44 AM, Jörn Röder<EMAIL_ADDRESS>wrote:

hey @askmike https://github.com/askmike no worries. i understand your
concerns and have seen that a lot of the gekko code base has changed in the
last few month. If you have another idea how to implement this which fits
better into the current design than go for it, if my work inspired you to
find an (even) better solution than perfect – this is what open source is
all about ✌!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/pull/1317#issuecomment-409036134, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7MD6JlNHkdiAfUEm8z9vEtC0mzEST7ks5uL4xPgaJpZM4Qbq_3
.

--
PGP key at keybase.io/mikevanrossum
https://keybase.io/mikevanrossum/key.asc

@askmike just seen your strategy video and pretty much like your solution how stops are integrated now. Keep up the great work! 👍


UX improvements for rad command notifications

Further UX improvement potential according to common sense and official VS Code guidelines:

Add a Don't show again option for every notification and remember it (changes extension config)

Granularity of what to not show per click must be decided. Don't show any of push/pull/etc?
Don't show any successful ones? Don't show for successful pushes?
Upon clicking it, a new notification is shown verifying what the user actually did e.g. Notifications for successful rad push will not longer be shown. with button Undo

Remove "Show output" button on success? Maybe make it a config instead of keeping/removing it for all users?
Show a Progress Notification generically if a spawned shell command (e.g. rad push or anything else) takes more than X time (e.g. time>300ms in unfavorable network/server/payload conditions)?

What buttons (copy and actions) to include if any? e.g. cancel, show output, etc
NOTE: current implementation isn't streaming shell command's output to the extension's log

Relates to https://github.com/cytechmobile/radicle-vscode-extension/issues/8


Dev environment per dev

Since the teams is about to grow up, we need a way to each have our own dev setup.

@waliens
I got an error with a completely empty DB

{"name":"SequelizeDatabaseError","parent":{"name":"error","length":106,"severity":"ERROR","code":"42P01","position":"61","file":"parse_relation.c","line":"1160","routine":"parserOpenTable","sql":"SELECT \"id\", \"name\", \"email\", \"createdAt\", \"updatedAt\" FROM \"Players\" AS \"Player\";"},"original":{"name":"error","length":106,"severity":"ERROR","code":"42P01","position":"61","file":"parse_relation.c","line":"1160","routine":"parserOpenTable","sql":"SELECT \"id\", \"name\", \"email\", \"createdAt\", \"updatedAt\" FROM \"Players\" AS \"Player\";"},"sql":"SELECT \"id\", \"name\", \"email\", \"createdAt\", \"updatedAt\" FROM \"Players\" AS \"Player\";"}


Release 1.0.3

Maybe it is a good time to tag a new 1.0.3 release as there are enough bug fixes in the current git.

I agree... I'll do this during the weekend.
Thanks @mcuee.

:tada:
Actually released as 1.1.0 due to 4134e911be88 ("Add USBTimeoutError").

Great. Thanks.

@mcuee , @SimplicityGuy , @tormodvolden
I don't have write access to the SourceForge project.  Can one of you please upload the release sdist and associated signature there?
Besides these, the SourceForge git mirror is also outdated.  I think we should phase out that platform for everything but the mailling list (and, in the future, maybe even that), and redirect all users to this repository (or the website).

Sure, I am happy to do this. I have now uploaded the tarball and the signature, and updated the git mirror. It is surely some extra work to maintain a mirror but it is also nice to show that there are alternatives. Sourceforge also has the advantage that you can upload a proper release tarball and leave it at that - c.f. the confusing double tarballs at the github release link.

Thanks!
I guess you're right, there are some advantages to keeping SF active.  And not being able to remove the auto-generated tarballs from GitHub is really annoying : \
That said, can you also edit the project and wiki pages to guide users towards this repository, the website or, when applicable, the tutorial and FAQ?

@tormodvolden Can you add me and Jonas to the Sourceforge side? My Sourceforge user name is xiaofanc.

Good idea, mine is jonasmalaco.

Done.


Does onnxruntime QNN EP support qualcomm QCS8550 soc

Hello, I want to know if onnxruntime QNN EP support qualcomm QCS8550 soc?

Yes, as long as QNN supports.


Is calling list() reliable?

In https://github.com/symphonycms/symphony-2/blob/4410adc7154918b94224a91882d9c45274e3b1a8/symphony/lib/toolkit/class.frontendpage.php#L275 the list() construct is used. According to the PHP docs, this will behave differently depending on the PHP version. So do we have an issue here? (And should we check the core for other occurences of list()?)

Wow this is bat-shit-crazy. I was wondering why XSLT errors where not being displayed correctly on PHP 7, I now have my answer...
I would do while ($error = $this->Proc->getError()) { and will never use list anymore with numeric indexes. Wanna send a PR ? (for 2.7.x)

That may have been false alarm.
I dig deeper, and I learned that only the order of assignment has been changed — so the order of values is not reversed. See http://php.net/manual/en/migration70.incompatible.php:

In general, this only affects the case where list() is being used in conjunction with the array [] operator, as shown below:
list($a[], $a[], $a[]) = [1, 2, 3];
var_dump($a);

If you use explicit indices (or even variables) like in the following example (see http://php.net/manual/en/function.list.php):
$info = array('coffee', 'brown', 'caffeine');
list($a[0], $a[1], $a[2]) = $info;
var_dump($a);

you will be fine — only the sorting of elements in the resulting array will be different.
In PHP7:
array(3) {
  [0]=>
  string(6) "coffee"
  [1]=>
  string(5) "brown"
  [2]=>
  string(8) "caffeine"
}

In PHP5:
array(3) {
  [2]=>
  string(8) "caffeine"
  [1]=>
  string(5) "brown"
  [0]=>
  string(6) "coffee"
}

So as far as I understand this now, this is a non-issue for us, isn't it? What do you think?

I'll make some test on my own, thanks @michael-e

So I've done some testing with this code

        echo PHP_VERSION;
	echo PHP_EOL;

	$array = [1,2,3];

	list(, $v) = $array;

	var_dump($array);
	var_dump($v);

And php 5.6, 7.0, 7.1, 7.2 all put the second item in the index-based array in the $v variable, which is good. Based on our code, I think this is what we want.
What I do not like, it that if the array does not have the 0 or 1 index set, it spits a warning.
It is also not SUPER readable.  But it's not a compat problem.
That being said, I would not oppose changing it in 3.0.0.

if the array does not have the 0 or 1 index set, it spits a warning

Yes, that may be an issue in certain cases.

It is also not SUPER readable

You will even find more occurences in the core! :-)

I know! And it can be dangerous also. Just like extract() which is worst.


Smart Global Governance Connector

Please check the following conditions for your PR.

[x] apiDefinition.swagger.json is validated using paconn validate command.
[x] apiProperties.json has a valid brand color. Invalid brand colors are #007ee5 and #ffffff.

Dear Doug,
Many thanks for your comments which are really relevant 😉 I fixed all of them and pulled a new request.
Best regards
Philippe
De : Doug Elliott<EMAIL_ADDRESS>Envoyé : mercredi 27 janvier 2021 05:16
À : microsoft/PowerPlatformConnectors<EMAIL_ADDRESS>Cc : Philippe Tivolle<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [microsoft/PowerPlatformConnectors] Smart Global Governance Connector (#669)
EXTERNAL SENDER: This email originated from outside of the organization. Do not click any links or open any attachments unless you recognize & trust the sender and know the content is safe.
@dougelliott requested changes on this pull request.
In addition to the comments, please also remove the icon.png and settings.json file, as those are not needed for open sourcing. Thanks!

In certified-connectors/SmartGlobalGovernance/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#discussion_r565014905:

@@ -0,0 +1,918 @@

+{

"swagger": "2.0",

"info": {

   "title": "SMART GLOBAL GOVERNANCE",

Could the title be title case, so Smart Global Governance?

In certified-connectors/SmartGlobalGovernance/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#discussion_r565015389:

@@ -0,0 +1,918 @@

+{

"swagger": "2.0",

"info": {

   "title": "SMART GLOBAL GOVERNANCE",

   "description": "Smart Global Governance allows to interact with Smart Compliance Booster solution",

It'd be great if this description could be expanded on to highlight the functionality and value that the connector offers.

In certified-connectors/SmartGlobalGovernance/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#discussion_r565016021:

@@ -0,0 +1,918 @@

+{

"swagger": "2.0",

"info": {

   "title": "SMART GLOBAL GOVERNANCE",

   "description": "Smart Global Governance allows to interact with Smart Compliance Booster solution",

   "version": "1.0",

   "contact": {

       "name": "Benoit Guignard",

This contact information will be visible to the public, so we do not recommend having PII here. Instead, we would recommend using more generic contact information, such as your support team.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#pullrequestreview-576970316, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASS22ZO35IU75TGUGVDJMKDS36HOLANCNFSM4WTCI5FQ.

Dear Doug,
Many thanks for your comments which are really relevant 😉 I fixed all of them and pulled a new request.
Best regards
Philippe
De : Doug Elliott<EMAIL_ADDRESS>Envoyé : mercredi 27 janvier 2021 05:16
À : microsoft/PowerPlatformConnectors<EMAIL_ADDRESS>Cc : Philippe Tivolle<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [microsoft/PowerPlatformConnectors] Smart Global Governance Connector (#669)
EXTERNAL SENDER: This email originated from outside of the organization. Do not click any links or open any attachments unless you recognize & trust the sender and know the content is safe.
@dougelliott requested changes on this pull request.
In addition to the comments, please also remove the icon.png and settings.json file, as those are not needed for open sourcing. Thanks!

In certified-connectors/SmartGlobalGovernance/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#discussion_r565014905:

@@ -0,0 +1,918 @@

+{

"swagger": "2.0",

"info": {

   "title": "SMART GLOBAL GOVERNANCE",

Could the title be title case, so Smart Global Governance?

In certified-connectors/SmartGlobalGovernance/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#discussion_r565015389:

@@ -0,0 +1,918 @@

+{

"swagger": "2.0",

"info": {

   "title": "SMART GLOBAL GOVERNANCE",

   "description": "Smart Global Governance allows to interact with Smart Compliance Booster solution",

It'd be great if this description could be expanded on to highlight the functionality and value that the connector offers.

In certified-connectors/SmartGlobalGovernance/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#discussion_r565016021:

@@ -0,0 +1,918 @@

+{

"swagger": "2.0",

"info": {

   "title": "SMART GLOBAL GOVERNANCE",

   "description": "Smart Global Governance allows to interact with Smart Compliance Booster solution",

   "version": "1.0",

   "contact": {

       "name": "Benoit Guignard",

This contact information will be visible to the public, so we do not recommend having PII here. Instead, we would recommend using more generic contact information, such as your support team.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#pullrequestreview-576970316, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASS22ZO35IU75TGUGVDJMKDS36HOLANCNFSM4WTCI5FQ.

All CLA requirements met.

All CLA requirements met.

Hello,
Many thanks for your feedback. I updated the file and posted a new “Pull request”.
Best regards
Philippe
De : Srikanth Yenagandhula<EMAIL_ADDRESS>Envoyé : jeudi 28 janvier 2021 03:18
À : microsoft/PowerPlatformConnectors<EMAIL_ADDRESS>Cc : Philippe Tivolle<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Objet : Re: [microsoft/PowerPlatformConnectors] Smart Global Governance Connector (#669)
EXTERNAL SENDER: This email originated from outside of the organization. Do not click any links or open any attachments unless you recognize & trust the sender and know the content is safe.
@sriyen-msft requested changes on this pull request.

In certified-connectors/SmartGlobalGovernance/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#discussion_r565774141:

           ],

           "summary": "Create a Client",

           "description": "Create a Client and its properties",

           "operationId": "Client-create",

           "parameters": [{

                   "name": "body",

                   "in": "body",

                   "required": false,

                   "schema": {

                       "$ref": "#/definitions/Client"

                   }

               }

           ],

           "responses": {

               "default": {

                   "description": "default",

@Philippe-Tivollehttps://github.com/Philippe-Tivolle We recommend you to replace the "default" responses with expected status codes, otherwise users may see errors about incorrect schema instead of real error responses from your service in OpenAPI mode.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#pullrequestreview-577934505, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASS22ZI3GRLMMJ5UN435HDTS4DCOFANCNFSM4WTCI5FQ.

Hello,
Many thanks for your feedback. I updated the file and posted a new “Pull request”.
Best regards
Philippe
De : Srikanth Yenagandhula<EMAIL_ADDRESS>Envoyé : jeudi 28 janvier 2021 03:18
À : microsoft/PowerPlatformConnectors<EMAIL_ADDRESS>Cc : Philippe Tivolle<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Objet : Re: [microsoft/PowerPlatformConnectors] Smart Global Governance Connector (#669)
EXTERNAL SENDER: This email originated from outside of the organization. Do not click any links or open any attachments unless you recognize & trust the sender and know the content is safe.
@sriyen-msft requested changes on this pull request.

In certified-connectors/SmartGlobalGovernance/apiDefinition.swagger.jsonhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#discussion_r565774141:

           ],

           "summary": "Create a Client",

           "description": "Create a Client and its properties",

           "operationId": "Client-create",

           "parameters": [{

                   "name": "body",

                   "in": "body",

                   "required": false,

                   "schema": {

                       "$ref": "#/definitions/Client"

                   }

               }

           ],

           "responses": {

               "default": {

                   "description": "default",

@Philippe-Tivollehttps://github.com/Philippe-Tivolle We recommend you to replace the "default" responses with expected status codes, otherwise users may see errors about incorrect schema instead of real error responses from your service in OpenAPI mode.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#pullrequestreview-577934505, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASS22ZI3GRLMMJ5UN435HDTS4DCOFANCNFSM4WTCI5FQ.

Hello Doug,
Nice to read it. Please, could you tell me where we stand? What is the next step? As far as I understood, we should get your official go before submitting the connector to ISV Studio, right?
Best regards
Philippe
[https://www.smartglobalgovernance.com/wp-content/uploads/signature-1.png]https://www.smartglobalgovernance.com/fr/essai-gratuit
[https://www.smartglobalgovernance.com/wp-content/uploads/signature-4.png]https://www.linkedin.com/company/smartglobalgovernance/
[https://www.smartglobalgovernance.com/wp-content/uploads/Signature-5.png]https://twitter.com/_smartglobal
Philippe Tivolle
Infrastructure Security Engineer
Prendre rendez-vous dans mon<EMAIL_ADDRESS>+33 6 12 15 65 15 / +33 9 72 64 05 40
1240 route des Dolines - 06560 Sophia Antipolis
www.smartglobalgovernance.comhttp://www.smartglobalgovernance.com/fr/
[Réseau BPI Excellence | I.CERAM]https://www.bpifrance.fr/
[Homepage | UN Global Compact] https://www.unglobalcompact.org/
AVERTISSEMENThttps://www.smartglobalgovernance.com/fr/avertissement | DISCLAIMERhttps://www.smartglobalgovernance.com/en/disclaimer | DESCARGO DE RESPONSABILIDADhttps://www.smartglobalgovernance.com/es/descargo-de-responsabilidad | HAFTUNGSAUSSCHLUSShttps://www.smartglobalgovernance.com/de/haftungsausschluss
[https://www.smartglobalgovernance.com/wp-content/uploads/signature.png]https://app.livestorm.co/didomi/quels-sont-les-defis-de-la-mise-en-conformite-rgpd-dans-lassurance
[https://www.smartglobalgovernance.com/wp-content/uploads/signature-bas.png]https://eme.gouv.mc/
De : Doug Elliott<EMAIL_ADDRESS>Envoyé : samedi 30 janvier 2021 03:04
À : microsoft/PowerPlatformConnectors<EMAIL_ADDRESS>Cc : Philippe Tivolle<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Objet : Re: [microsoft/PowerPlatformConnectors] Smart Global Governance Connector (#669)
EXTERNAL SENDER: This email originated from outside of the organization. Do not click any links or open any attachments unless you recognize & trust the sender and know the content is safe.
@dougelliott approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/669#pullrequestreview-579717212, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASS22ZIRHKTOA4IJPRIYYIDS4NSJXANCNFSM4WTCI5FQ.


github.com/mholt/archiver package is deprecated

Feature Description
ref: https://github.com/mholt/archiver
Screenshots
No response

Move to https://github.com/mholt/archives

Maybe possible to drop the dependency completely.


Note Colors in Options Buttons Merged

Describe your bug here. If you are modding, try testing your bug in a clean version of the engine instead. Also, if you're using an older version of JSE, please try the latest version/action build. Also, be sure to check the pinned 'JS Engine: Known Issues' issue, to check if your issue hasn't already been found!

Command Prompt/Terminal/Crash logs (if existing)
None

Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Android
Did you edit anything in this build? If so, mention or summarize your changes.
None
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
No

What? Can you provide more details, please?

What? Can you provide more details, please?

Those buttons

Bro, I didn't want to stay this, but in this case you should have said "overlap" instead of "merged", This is because I had already seen your question before, but I didn't understand it and I was afraid of answering wrong.

Btw I think it has to do with the resolution of your phone

happens on wsa with 720p


Config directory needs to be created if it doesn't exist

The first time I tried to migrate from Kubernaut v1 to v2 I got this:
kubernaut config backend create --url="https://next.kubernaut.io" --name="v2" --activate $token
Traceback (most recent call last):
  File "kubernaut/cli.py", line 47, in <module>
  File "site-packages/click/core.py", line 722, in __call__
  File "site-packages/click/core.py", line 697, in main
  File "site-packages/click/core.py", line 1066, in invoke
  File "site-packages/click/core.py", line 1066, in invoke
  File "site-packages/click/core.py", line 1066, in invoke
  File "site-packages/click/core.py", line 895, in invoke
  File "site-packages/click/core.py", line 535, in invoke
  File "site-packages/click/decorators.py", line 27, in new_func
  File "kubernaut/config/cmd.py", line 49, in create_backend
  File "kubernaut/config/model.py", line 67, in save
  File "pathlib.py", line 1213, in write_text
  File "pathlib.py", line 1181, in open
  File "pathlib.py", line 1035, in _opener
  File "pathlib.py", line 387, in wrapped
FileNotFoundError: [Errno 2] No such file or directory: '/Users/flynn/Library/Application Support/kubernaut/config'
[63733] Failed to execute script cli

Running mkdir  '/Users/flynn/Library/Application Support/kubernaut/config' solved the problem.
As an aside: should we just standardize on $HOME/.config/kubernaut like V1 did, and not use click.get_app_dir()? Aside from the fact that it feels a bit odd to me that Kubernaut is using stuff in Library/Application Support since isn't a very Mac-y application, it seems that telling everyone a single config path rather than having it be platform-specific might be convenient.

Some conversation I had about the config location on Linux vs. macOS.
plombardi [10:53 AM]
Where does kubectl store configs on macOS?

What about other CLI's?

flynn [10:54 AM]
`kubectl` uses `~/.kube`.
In general, Macs are Unix boxes, so `~/.whatever` is still natural. The XDG thing hasn’t really migrated off Linux, I don’t think.

plombardi [10:55 AM]
Do you have a `.config` directory with anything in it besides datawire stuff? Eg is google cloud in there?

flynn [11:03 AM]
Yeah, actually I do, about half-and-half Datawire.
(fish, gcloud, gocode, xonsh, yarn are the non-d6e things)

plombardi [11:06 AM]
Aight. I'll probably just standardize on `~/.kubernaut` or `~/.config/kubernaut`. I don't want people to have to remember where it is depending on OS
Windows being the exception if we ever create one for Windows, but that's unlikely with WSL being a thing


Aggregation changes

We have several issues which we need to address in the aggregation area for stabalizing the package support and for making debugging easier and clearer in the development phase.
JS Injection requirement

Inplace js injection: In October 10th - @veljkopopovic helped me resolve a situation in which we saw white page errors (arghh drupal wsod :) ) on the installation of the gmap packge.
He found the the use of the way we injected the headerJS untill 55458ca82a3f373ab2cddebba9ef74bc0fe8104e caused this error.
Once we moved from " " to "" we resolved the issue but the ga and gmap packages that need to inject js inline do not work.
What this means is that we need to have an "inline" group in aggregation to enable injection of scripts that would run a document.write to build the retrieval of another remote script (like is common in google stuff)

"Disable aggregation in dev mode"
We have a recurring theme @andrija-hers has also talked with devs about regarding "disabling aggregation" for dev env - I think that upon building we should go over all of the scripts that used to be part of the aggregated object which is iterated in sortAggregateAssetsByWeight here - https://github.com/linnovate/meanio/blob/master/lib/aggregation.js
Maybe we can have a check in line 141 of https://github.com/linnovate/meanio/blob/master/lib/bootstrap.js which will see if we are in debug true and if so instead of "enabling the aggregation module" we will enable a different module (inclusion ?) which will simply iterate in system/server/views/include/head.html and simply place a sequence of script tags.
@andrija-hers @veljkopopovic does this seem reasonable?

@liorkesos We've removed aggregation in the latest versions of MeanIO/Mean. Can we close this issue?


[docs] Fix markdown in profiling doc page

The Issue
Here's how steps numbers section looks a bit broken:

How This PR Solves The Issue
Well, it looks now as initended.

Thanks @oleksii-lisovyi - Could you also say something about your blackfire usage? I was wondering if anybody used it any more since the free/hacker plan went away. I assume you use Platform.sh?

@rfay honestly just started exploring this in depth. haven't had any decent experience to be able to comment on that.
so far trying to make it work, tho there are some limitations with license I wasn't yet able to overcome.

Yeah, I don't think you can use it at all any more without a paid account.

From Blackfire pricing page:

We don't provide a free trial.

If it's paid-only, perhaps it should be extracted to an addon and removed from DDEV?

Right, there is no free trial, but I'm interested if people have a subscription and are still using it any more. Blackfire is a product of Platform.sh, a major sponsor of DDEV, but no matter how much I pester, I can't get them to bring back the hacker/localdev/free account.
Moving it to an add-on seems possible.


Fix NER best quality preset

Issue #, if available:
Description of changes:
Fix best quality ner preset
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@cheungdaven Do we need to use a smaller batch_size?

@cheungdaven Do we need to use a smaller batch_size?

fixed.


Separate simplification of operators from SummedOp.add and fix bugs of add

Summary
This PR separates same operator check in SummedOp.add and makes another method SummedOp.simplify to summing up same operators.
It also fixes all bugs found in #979 and add unit tests.
Fixes #979
minor change: remove unnecessary [] in all and any.
Details and comments
It fixes following bugs.

ListOp.equals did not compare ListOp.coeff -> Fixed https://github.com/Qiskit/qiskit-aqua/issues/979#issuecomment-630680390
SummedOp.add did not handle SummedOp.coeff correctly, especially when coeff != 1 -> Fixed https://github.com/Qiskit/qiskit-aqua/issues/979#issuecomment-630594710
SummedOp.add did not apply simplification in a particular case -> Separate out the simplification as another method and the simplification won't be applied automatically. Note that simplification should not be often invoked because it takes O(n^2) time where n is the number of operators.  https://github.com/Qiskit/qiskit-aqua/issues/979#issuecomment-629987691

I also fixed some comments of AbelianGrouper.

Thank you for your feedback!

The spellchecker is complaining about the word subops, if you add it to the .pylintdict the CI should succeed.

I changed the comment to be clear.

If you looked in the build output then the spell checker did provide alternatives like sub-ops. In general if it can be spelled out or changed its better than adding something like subops, which is not really a word, to the custom dict. So your change was the right thing in my book. Sometimes though its unavoidable as you need to refer to something defined elsewhere.

Travis failed on Test Aqua 1 Python 3.8 due to the following error.
{1} test.aqua.operators.legacy.test_tpb_grouped_weighted_pauli_operator.TestTPBGroupedWeightedPauliOperator.test_evaluate_qasm_mode [2.386731s] ... FAILED
Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "/home/travis/build/Qiskit/qiskit-aqua/test/aqua/operators/legacy/test_tpb_grouped_weighted_pauli_operator.py", line 148, in test_evaluate_qasm_mode
    self.assertGreaterEqual(reference[0].real,
      File "/opt/python/3.8.0/lib/python3.8/unittest/case.py", line 1316, in assertGreaterEqual
    self.fail(self._formatMessage(msg, standardMsg))
      File "/opt/python/3.8.0/lib/python3.8/unittest/case.py", line 753, in fail
    raise self.failureException(msg)
    AssertionError: 1.736805965121753 not greater than or equal to 1.7490732614333155

I'm wondering why results varied even if the seed of simulator is fixed.

This is a great addition, but I think it would probably be more natural to put the new simplify functionality inside SummedOp's reduce, rather than create a new function (unless simplify is slow).


Add support for sass style comment in .scss files

Comments should be in the form:
//doc
//  ---
//  title: something
//  category: ...
//  ---
//

Always have double space between the // and the content

@jdcantrell Do you think you can merge it in this state?
I'll be happy to change some things if you prefer, but I would really appreciate if I can use upstream again.

+1 for this update, would love to have this merged in as well

+1


parallel requests with different params

Hello, I want to execute parallel requests with different parameters. Parameters are in the list, but when I run the test it is running only with the last parameter from the list.
How I can resolve it?
`from locust import task
from gevent.pool import Group
class MyClass():
@task
def get_data(self):
pool = Group()
    currency = [{'network': 'network', 'currency': 'ETH'},
                {'network': 'network', 'currency': 'BTC'}]

    [pool.spawn(lambda: self.get_crypto_price(networks=i.get('network'), currency_type=i.get('currency'),
                 name_param=i.get('currency'))) for i in currency]
	pool.join()`

@STsariuk did you find any solution for this?


sharing htuch's docker instructions and fixing a container bug

like so?
On Mon, Aug 7, 2017 at 3:49 PM, htuch<EMAIL_ADDRESS>wrote:

@htuch commented on this pull request.
In ci/README.md
https://github.com/lyft/envoy/pull/1408#discussion_r131746903:

@@ -71,3 +71,22 @@ The ./ci/run_envoy_docker.sh './ci/do_ci.sh <TARGET>' targets are:

bazel.tsan — build and run tests under -c dbg --config=clang-tsan with clang-5.0.
check_format— run clang-format 5.0 and buildifier on entire source tree.
fix_format— run and enforce clang-format 5.0 and buildifier on entire source tree.

+# Testing changes to the build image as a developer
+
+While all changes to the build image should eventually be upstreamed, it can be useful to
+test those changes locally before sending out a pull request.  To experiment
+with a local clone of the upstream build image you can make changes to files such as
+build_container.sh locally and then run :
+
+```bash
+cd ci/build_container
+export TRAVIS_COMMIT=my_tag
+./docker_build.sh  # Wait patiently for quite some time
+cd ../..
+IMAGE_ID=my_tag
This should either be merged with the line below, or made an export. We
probably should be consistent in style with the above env var setting too.
I think making them both prefix env var assignments is cleaner.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/lyft/envoy/pull/1408#pullrequestreview-54756162, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARYFvUY3S4HznBQ412hNDTxmmMXmE3-Aks5sV2pVgaJpZM4OvwDz
.


Helm selected line background and foreground have same color with doom-solarized-dark

Sorry for the late response. As of df0b9b7 this should be resolved. Let me know if that isn't the case and I'll reopen it.


Template groups + clean, updates and fixes

Get rid of the template file and instead declare template groups in the stackgen.yml file
Added support for specifying multiple template groups
Prefix all bundled template groups with StackGen
stackgen.yml: change custom to global
Templates Context: change global to env
Improve/fix error descriptions
Template StackGen_Swift_BuildSystem_Bazel: switch to bazelisk for bazel version control
Template StackGen_Swift_BuildSystem_Cocoapods:

Updated to cocoapods 1.9.2
Fixed Podile alignment
Separate pods in projects
Switch to use bundle for executing gems

Codecov Report

Merging #2 into master will increase coverage by 2.83%.
The diff coverage is 78.39%.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
+ Coverage   76.30%   79.13%   +2.83%
==========================================
  Files          40       42       +2
  Lines         671      695      +24
==========================================
+ Hits          512      550      +38
+ Misses        159      145      -14

Impacted Files
Coverage Δ

...ods/Libraries/App/src/main/swift/AppDelegate.swift
63.63% <ø> (ø)

...raries/App/src/main/swift/MainViewController.swift
100.00% <ø> (ø)

...s/Libraries/App/src/main/swift/SceneDelegate.swift
53.84% <ø> (ø)

...Libraries/SwiftModule1/src/main/swift/Source.swift
0.00% <ø> (ø)

.../Libraries/SwiftModule1/src/test/swift/Tests.swift
100.00% <ø> (ø)

...Libraries/SwiftModule2/src/main/swift/Source.swift
0.00% <ø> (ø)

.../Libraries/SwiftModule2/src/test/swift/Tests.swift
100.00% <ø> (ø)

...Libraries/SwiftModule3/src/main/swift/Source.swift
0.00% <ø> (ø)

.../Libraries/SwiftModule3/src/test/swift/Tests.swift
100.00% <ø> (ø)

...Libraries/SwiftModule1/src/main/swift/Source.swift
0.00% <ø> (ø)

... and 33 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 1973fa7...fdcf3e4. Read the comment docs.


Plugin Doesn't work, possibly abandoned?

Works for me, what's wrong for you? Make sure you follow the configuration

No response, so closing this.


Selection styles list

Summary
Closes #529

+1  - ready to merge
Resolves

selection color problems listed in Issue #529

Pass

UX Review


Dont work from Wow october update

Don't work from Wow October update, don't recognize the window game.

Have you tried Custom Window option in the Advanced Settings?

fixed ty!


Stale pull request support

This isn't a GitHub hook, but rather a bin script that runs against all open Github PRs.  We will set it up as a cron job on AWS.  It will still use the same nconf configuration.  Testing this locally should be easy without having to redeploy.

Add a Settings configuration for stale PRs  (default to 7 days)
Get a list of all open PRs and the news comment from each PR.
If the newest comment is older than X days, add a comment asking Cesium committers to take a look at it. Make sure the comment is not from the bot itself, since we don't want to add additional comments for no reason.

The GitHub API makes this simpler than that: it can return all pull requests and sort by how long ago they were "updated". Still requires a check for if the bot commented already, though.
Do you think this is equivalent to what you want? I think "Updated" could include submitting commits, so this seems better than checking just the comments.

I don't know what the exact policy should be yet, but I would like to experiment with something like:

If 30 days of no activity (not just comments, but commits), bump
If another 30 days of no activity, bump and kindly suggest to close.  If the work is still relevant, keep a branch and submit an issue

(then continue to bump every 30 days if it wasn't closed and is still inactive)

This will keep things tidy and consistent so contributors don't take offense if it is closed.
CC @ggetz

Sounds good to try.


Reddit Dataset Contribution

Add Reddit Dataset available from DGL with Node Classification Task and conveted it into GLI format.
How Has This Been Tested?
Already run make pytest DATASET=reddit locally for Reddit dataset implementation test.

test_data_loading and test_node_classification_training seem work on my computer.  Let me try to replicate the error locally and check it later.

test_data_loading and test_node_classification_training seem work on my computer. Let me try to replicate the error locally and check it later.

FYI, we use pytest for testing automation and it is convenient to run/debug tests locally in VSCode:

Seems like when I use gli.io.save_task_node_classification to save train_set, val_set and test_set (int64 indices), it will first convert them to list and then to numpy array.  The dtype numpy array will eventually become int32.
Hence, when loading indices from npz file in pytest test_data_loading of dtype int32, mask[_indices] fails with Error tensors used as indices must be long, byte or bool tensors.
It works on my computer since my torch version == 2.1.1 while on server, torch version == 1.13.1
I'm trying to force the dtype of indices to be int64 when saving to node classification task npz file.

Thanks @Jason-csc for the good catch. I am opening a new issue to fix this.

Hi @Jason-csc, as #475 is merged, you may re-run your conversion script and see if everything is okay now. 🚀 Let us know if you find further issues.

Oops, I think I've uploaded the task npz file to Dropbox. Maybe it need some time to synchronize ?
Would you mind helping me have a look at that @xingjian-zhang ? Thx

Yea it takes some time for the server to sync, I re-runed the test just now. Let's wait and see the results.


Fix typo in json-serializer docstring

jsonista is used to serialize JSON instead of cheshire.

Thanks!


Documentation: decl_module! macro

Included:

Reference docs for decl_storage! per new template
Initial content review by @thiolliere

Done:

fact check w/ author
style, grammar review

Pending: final review
references: https://github.com/paritytech/substrate-developer-hub/issues/58

Should these lines use //! or we can't do that with macro docs?

Hopefully CI will be happy now.  If it is, I will merge this.

Hopefully CI will be happy now. If it is, I will merge this.

We have not been bumping impl_version for documentation. If course we could start, but then we go down a rabbit hole, like, if you just fix a few typos should you bump impl. I don't have strong feelings either way except that bumping or not bumping should be consistent.

Hopefully CI will be happy now. If it is, I will merge this.

We have not been bumping impl_version for documentation. If course we could start, but then we go down a rabbit hole, like, if you just fix a few typos should you bump impl. I don't have strong feelings either way except that bumping or not bumping should be consistent.

Looks like the Cargo.toml and Cargo.lock files were updated, maybe that is worth bumping impl. Was that necessary just to make the examples compile (and are we ok with that)?

Please revert, there is no reason to update the impl version for this pr.


How to use this code on my own data?

It is a amazing work, and I'm interested in your excellent work. Can you tell me how to train the network on my VOC like dataset (annotations in xml format)?

Hey Hansheng, thanks for your interest in the work.
Please find the this repo to generate the VOC-liked dataset. We save everything in json format.


Feature/sort modifier

-adding ability to hold shift key to change the behavior of the column sorting

Current coverage is 29.67% (diff: 100%)

Merging #78 into master will increase coverage by 0.57%

@@             master        #78   diff @@
==========================================
  Files            45         45
  Lines          1340       1341     +1
  Methods         170        170
  Messages          0          0
  Branches        315        316     +1
==========================================
+ Hits            390        398     +8
+ Misses          950        943     -7
  Partials          0          0

Powered by Codecov. Last update c70fe96...db400ce


Setting NEURON_CC_FLAGS might lead to compilation errors

Compilation parameters set using the environment variable NEURON_CC_FLAGS will produce specific NEFF binaries.
Example of flags:

the optimization level (-O1, -O2, -O3),
the accumulation type (--enable-mixed-precision-accumulation).

This will lead to two issues when associating compilation artifacts to a neuron model if NEURON_CC_FLAGS is not empty:

cache lookup will wrongly assume that cached artifacts are compatible,
serialized compilation artifacts from a local or hub model will fail to load.

The flags should be stored in the neuron config to allow stored/cached compilation artifacts to be properly aligned with the neuron model.

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!


[BUG FIX] Fix CRASH, bumping IdentifiedCollections

Solves crash bug: https://rdxworks.slack.com/archives/C03QFAWBRNX/p1715599065238219
It was a bug in IdentifiedArrayOf, fixed in 1.0.1 in PR https://github.com/pointfreeco/swift-identified-collections/pull/66

Superseeded by #1120


Update sbt-github-actions to 0.22.0

About this PR
📦 Updates com.codecommit:sbt-github-actions from 0.14.2 to 0.22.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (0.14.2).
You might want to review and update them manually.
README.md
project/Dependencies.scala

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.codecommit", artifactId = "sbt-github-actions" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.codecommit", artifactId = "sbt-github-actions" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, artifact-migrations, old-version-remains, commit-count:n:2

Superseded by #186.


Added Philips Hue White models to ZHADimmableLight quirk

Added Philips Hue White models to ZHADimmableLight quirk.

Codecov Report

Merging #753 (5c5aeaf) into dev (9d9d6e7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #753   +/-   ##
=======================================
  Coverage   83.08%   83.08%
=======================================
  Files         176      176
  Lines        3956     3956
=======================================
  Hits         3287     3287
  Misses        669      669

Impacted Files
Coverage Δ

zhaquirks/philips/zhadimmablelight.py
100.00% <ø> (ø)

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 9d9d6e7...5c5aeaf. Read the comment docs.

Codecov Report

Merging #753 (5c5aeaf) into dev (9d9d6e7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #753   +/-   ##
=======================================
  Coverage   83.08%   83.08%
=======================================
  Files         176      176
  Lines        3956     3956
=======================================
  Hits         3287     3287
  Misses        669      669

Impacted Files
Coverage Δ

zhaquirks/philips/zhadimmablelight.py
100.00% <ø> (ø)

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 9d9d6e7...5c5aeaf. Read the comment docs.

Pull Request Test Coverage Report for Build 515239698

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.089%

Totals

Change from base Build 512410068:
0.0%

Covered Lines:
3287

Relevant Lines:
3956

💛  - Coveralls

Pull Request Test Coverage Report for Build 515239698

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.089%

Totals

Change from base Build 512410068:
0.0%

Covered Lines:
3287

Relevant Lines:
3956

💛  - Coveralls

How do you getting all new lights in the lockdown times ?!?!?!?  ;-))
Great work ! !

How do you getting all new lights in the lockdown times ?!?!?!?  ;-))
Great work ! !


Replaces meta data for operator in CSV throws fatal error when no previous version of operator is found

Started seeing this issue (https://github.com/operator-framework/operator-registry/issues/47) since the postgresql-operator was updated.
The updated (v0.0.4) operator's manifest explicitly replaces the previous version of the operator:
  version: REPLACE_VERSION
  replaces: postgresql-operator.v0.0.3

However, this causes the installation of the operator to fail unless the quay repo contains a v0.0.3 instance of the operator:
  containerStatuses:
    - name: db-operators
      state:
        waiting:
          reason: CrashLoopBackOff
          message: >-
            Back-off 5m0s restarting failed container=db-operators
            pod=db-operators-54bc68548b-ngp9c_openshift-marketplace(83c21748-a1af-11e9-a9c5-02519ac499b2)
      lastState:
        terminated:
          exitCode: 1
          reason: Error
          message: >
            time="2019-07-08T19:04:48Z" level=fatal msg="error loading manifest
            from remote registry - postgresql-operator.v0.0.4 specifies
            replacement that couldn't be found" port=50051 type=appregistry
          startedAt: '2019-07-08T19:04:47Z'
          finishedAt: '2019-07-08T19:04:48Z'

Workaround = remove this line from the manifest
replaces: postgresql-operator.v0.0.3


UI: User can get invalid config by leaving a page invalid, going back, then finishing

It is possible for the user to finish the create connector wizard with an invalid config.  Consider the following scenario

Enter valid connection properties on step 2.
Click next twice - go to step 4
Enter an invalid property value on step 4 (for example enter 10 for 'Columns PK Mapping') - validate and get invalid message
Click back, go to the previous page. (on the previous page user can click Finish)
Click finish results in config with the invalid value from step 4
User should not be able to finish unless all pages are valid

Good observation. No, I think we should block the "Finish" only if something is invalid on that page or page before and the pages coming after should not have an effect on the "Finish" button.
We can handle the "Finish" button as such that if an early finish is performed than config should only contain the properties present on that page and the pages that came before.

Pr raised https://github.com/debezium/debezium-ui-poc/pull/188

PR merged, closing


fix(manisfest): correct name in package.json/README.md

Updated name from tesmart-hdmi-matrix to tesmart-hdmimatrix
Resolves bitfocus#2
Signed-off-by: Johnny Estilles<EMAIL_ADDRESS>

I'm not apposed to changing the name.
I'm just curious if there's a particular reason? I just want to know for future modules that I make.

I'm not apposed to changing the name.
I'm just curious if there's a particular reason? I just want to know for future modules that I make.

The name in the manifest (package.json) has to match the last part of the name of the repo, otherwise the module will not load (See reported issue #2).
In other words, ff the name of the name of the repo is companion-module-tesmart-hdmimatrix then the name in package.json needs to be tesmart-hdmimatrix.
I changed the name on the README.md as well just so they would match.

Ahhhh! I see. So its more of a I have the dumb moment.

Ahhhh! I see. So its more of a I have the dumb moment.

No worries. It happens to all of us. :-)
Is this module ready to be merged into the Companion core?

Yes
Sent from my iPhone

On Nov 22, 2021, at 9:53 PM, Johnny Estilles @.***> wrote:

Ahhhh! I see. So its more of a I have the dumb moment.
No worries. It happens to all of us. :-)
Is this module ready to be merged into the Companion core?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


Switches storing resume data in memory to disk

          1 Warning

:warning:
Any source code changes should have an entry in CHANGELOG.md or have #trivial in their title.

  Generated by :no_entry_sign: Danger

🚫 CI failed with log

🚫 CI failed with log


DeploymentSettings doesn't handle EnvironmentVariables if it's a secret and fails/ignore silently

What happened?
Probably related to #419 - I've tried multiple ways to set an env var with a secret and cannot get anything to show up in Pulumi Cloud. The up succeeds but silently does not create the env var if one contains a secret.
I've tried creating a secret inline, pulling an existing secret from config, doing applies, nothing seems to work.
Note that if there is a single secret value in the env var at all, none of the env vars are set, even plaintext ones.
Example
    var instance = Deployment.Instance;

    var deploymentSettingsResource = new PulumiService.DeploymentSettings("deploymentSettingsResource", new()
    {
        Organization = instance.OrganizationName,
        Project = instance.ProjectName,
        Stack = instance.StackName,
        OperationContext = new PulumiService.Inputs.DeploymentSettingsOperationContextArgs
        {
            EnvironmentVariables =
            {
                { "GH_TOKEN", Output.CreateSecret("my_secret_token") },
                { "NOT_SECRET", "I love otters" },
            },
        }
    });

Output of pulumi about
pulumi about

CLI
Version      3.139.0
Go Version   go1.23.3
Go Compiler  gc

Plugins
KIND      NAME           VERSION
resource  aws            6.60.0
resource  awsx           2.16.1
resource  docker         4.5.6
language  dotnet         unknown
resource  pulumiservice  0.27.1
resource  random         4.16.4

Host
OS       darwin
Version  15.1.1
Arch     arm64

This project is written in dotnet: executable='/Users/rsmith/.dotnet/dotnet' version='8.0.302'

Dependencies:
NAME                  VERSION
Pulumi                3.69.0
Pulumi.Aws            6.60.0
Pulumi.Awsx           2.16.1
Pulumi.PulumiService  0.27.1
Pulumi.Random         4.16.4

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Once it's fixed, if some info or an example could be added to the documentation here, that would be very helpful.  Thanks!

@bryantallison We have some examples on creation of DeploymentSettings via PSP - typescript example, + in python and yaml

Hey @IaroslavTitov this is better, thank you! I'm seeing a slightly different but related issue with v0.27.4:
Given two secrets and one plaintext:
    var ghToken = config.RequireSecret("ghtoken");

// ...

            EnvironmentVariables =
            {
                { "GH_TOKEN", ghToken },
                { "GH_TOKEN_OUTPUT", Output.CreateSecret("my_secret_token") },
                // { "GH_TOKEN", mySecret },
                // { "GH_TOKEN", "my token" },
                { "NOT_SECRET", "I love otters" },
            },

I see three secrets in the console which isn't what I expected (2 secret, 1 plaintext):

slightly different
Yes, I called it out in the PR, unfortunately this is a bug beyond PSP, with pulumi itself. For C# resources, it will turn all Env Vars secret if just one is secret.

Aha, thank you for pointing that out. Upvoting https://github.com/pulumi/pulumi-dotnet/issues/22 now😄


Fix: Issue #98

What needs to be changed:
Changing the text in the search bar of the map to be white during dark mode and not be black
Why is changed:
The text is unreadable during dark mode as the text is in black, where it should be white and be applied with the theme color.
How it is changed:
Whether in dark mode in light mode, I have ensured that the text color represents the dark or light theme

Hello @teamomiamigo,
I appreciate your efforts, but I’m encountering issues with the code. I’m unable to simulate the app, and it throws a "theme doesn't exist" error.
Additionally, when raising a PR, please include a comment in the PR description indicating the issue it resolves. For example, if the PR addresses issue #160, the first comment in the PR should be: "Fixes #160."
Thank you for your attention to these matters.

I have made new commits and changes to fix the colors so that the search bar text is in the black text and is set to the white text during dark mode now. due to simulator issues, I wasn't able to see this issue in this.


python: fix passing wrong qt5 version to pythonInterpreters

fixes c88f3adb1793cd3b007baff0292cf1fa8d0ab1e6, which resulted in qt 5.15 being used in pythonPackages, despite 5.14 being declared, and adapts qutebrowser accordingly.
Motivation for this change
'callPackage { pkgs = pkgs // { … }; }' does not work, because it does not take into account the recursive evaluation of nixpkgs:
pkgs/development/interpreters/python/default.nix calls pkgs/top-level/python-packages.nix with callPackage. Thus, even if the former gets passed the updated pkgs, the latter always gets passed pkgs.pkgs.
For the change in the qt5 version to apply consistently, 'pkgs.extend' must be used.
qutebrowser only used the right qt5 version (5.15) because all pythonPackages used it anyway.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built Evaluated and traced on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thank you, you're completely right! I've opened a new PR taking your commit with some changes https://github.com/NixOS/nixpkgs/pull/98197.


Duplicate tip

Commit 06b919d383ceb975bf07da36126607e516044c7b looks like a duplicate of this tip

:cactus: This list is growing fast, reverted, thanks.


Autorest Regen Preview to 3.0.0-alpha.20230504.7 by Dapeng Zhang from refs/pull/3282/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3282

API change check
API changes are not detected in this pull request.


feat: suport vm live migration

What type of this PR
Examples of user facing changes:

API changes

How does kube-ovn support Kubevirt vm live migration

The default NIC is only used for live migration, and the VM NIC is attached through Multus-cni.
If you need to assign fixed IP addresses to VM, use <attach>.<ns>.ovn.kubernetes.io/allow_live_migration: 'true' annotation to avoid IP conflict errors. You should also set the subnet parameter disableGatewayCheck: true.
If you use kubevirt DHCP configuration vm network, need to solve the problem of the default route, we can use <attach >.<ns>ovn.kubernetes.io/default_route: 'true' annotation to select the default routing NIC.

I'm copying my message from Slack here so that everybody can see it because it's probably a question other people might have thought about:
I'm trying to get more information on how live migration is implemented in Kube-OVN for Kubevirt VMs.
@Mengxin Liu
I believe you implemented most of the features related to it?My question is about the need for multiple interfaces on the virt-handler pods. One for migrations with the default VPC/Subnet and another with our Multus network (can be one connected to a NAT gw for example).This is related to PR https://github.com/kubeovn/kube-ovn/pull/1001
It says:
How does kube-ovn support Kubevirt vm live migration
The default NIC is only used for live migration, and the VM NIC is attached through Multus-cni.
If you need to assign fixed IP addresses to VM, use <attach>.<ns>.[ovn.kubernetes.io/allow_live_migration](http://ovn.kubernetes.io/allow_live_migration): 'true' annotation to avoid IP conflict errors. You should also set the subnet parameter disableGatewayCheck: true.
If you use kubevirt DHCP configuration vm network, need to solve the problem of the default route, we can use <attach >.<ns>[ovn.kubernetes.io/default_route](http://ovn.kubernetes.io/default_route): 'true' annotation to select the default routing NIC.

I don't get all of that, I did this configuration and it does work. But I also created a Pod with only one multus interface managed by Kube-OVN (which is now my default NIC) and it works just as well and is less complicated. So what's the point of the first network? How is it "used for live migrations" ?Concerning the second point, I get allow_live_migration ensures the IP stays static during migrations. I don't get why disableGatewayCheck needs to be set to true, it works very well with it on false.I'm asking this question because I want to use Cilium CNI chaining to handle network policies on my multus interface (which is connected to a NAT gateway), but Cilium currently doesn't handle that very well if it's not the primary interface (basically, it will start monitoring eth0 anyway). I get that to work if there's only one interface on my VM, but not if there's 2, because eth0 is binded to ovn-cluster and not my multus interface. But am I missing something? Why is my setup working, is it less reliable because it misses that interface ?
@fanriming if you get to see this. I would like to understand the tight integration between Kube-OVN and Kubevirt to better document it. There's currently nearly no documentation about it, and setting up livemigration is a must.


Default dark noise options don't work for non-SK geometries

Unless I'm missing something obvious, #101 only works if you don't change from the default geometry (i.e. SK). This is because the dark noise options are read before the geometry is actually constructed.
There's (at least) a couple of ways this could be fixed:

Get the default PMT rate the first time the AddDarkNoise() method is called, only if the messenger hasn't overwritten a (new) unphysical default value.
Create the WCSimWCAddDarkNoise class instance in the same way as the trigger/digitizer options (i.e. in WCSimEventAction::CreateDAQInstances()). Will need to store the DarkNoiseMessenger in the EventAction, and do the (somewhat laborious) job of passing of DarkNoise options from EventAction to AddDarkNoise.

Can someone please confirm the bug? And let me know which solution preference you have? 1 is much simpler to implement, and so is my preference.

Thanks for pointing this out @tdealtry. I looked back through the verification that was done when this pull request went through, and I don't think this was checked (the checks were done with the default geometry). I'll look into it more when I have a chance, which will hopefully be early next week.

Can someone explain: what is the effect of this bug if using non-SK geometry (but if I don't need to change the default PMT rate properties)?  Will everything work with HK geometry + default PMT rate.

Sorry, I've not had time to look over this bug yet, but if it is true, the dark noise will be set to the 20" PMT value. You can always explicitly specify the dark rate in the macro. For a 20" Box and Line use the lines:
/DarkRate/SetDarkRate 8.4 kHz
/DarkRate/SetConvert 1.126

Ok, looking at a couple of simple tests (running WCSim with the 40% HK geometry with the B&L dark rate explicitly set in the macro vs. running the HK geometry and allowing the dark rate to be set automatically) and it looks like the defaults aren't being set correctly. @tdealtry I think option 1 seems sensible. Let's try and get this fixed and then we should probably release a 1.5.1 with this bugfix in it.


5.70.0: ProgressPlugin broken on first build

In Webpack 5.70.0, ProgressPlugin does not log on the initial build, only on rebuilds.
This behavior was introduced in https://github.com/webpack/webpack/commit/00c57ede11ee10dbb0a42e944b2cd7a038089944.

Hm.. could you provide repro? I have log on initial build.


White screen on N3DS

New 3DS XL with Luma3DS (latest firmware)
Relaunch v4.0.1 CIA
Expected behaviour
Holding A and B opens the menu. Holding A opens file mentioned in Relaunch.ini.
Actual behaviour
Holding A and B or just A displays a white screen, which changes to a black screen, and shows nothing more.
I guess 3DS support is expected cause' there's a CIA build, so do you know what might be the issue?

How did you installed it? Also afaik you'd have to hold the Buttons quite a bit longer on 3DS, since the 3DS takes quite a bit to load into TWL_FIRM from CTR_MODE.

Installed it by downloading the zip from releases, then installing the CIA from SD card with FBI and pasting the _nds folder.
Pressing no buttons shows me the oof: Error 3 message. I guess they're being detected, else it would just show oof: Error 3.

If it freezes on a White / Black screen, then the loaded NDS app may not be supported through Relaunch.

I understand. I guess even Relaunch's own menu isn't supported in CIA build. Still hoping that I'm doing something wrong tbh. I'll report in future releases if something changes.

For the A+B Menu, make sure the menu.bin or whatever it was is in sd:/_nds/Relaunch/ or so. For the file one, make sure it matches properly (It must be sd and not sdmc iirc) and doesn't contain weird characters or so. Generally speaking, TWiLight Menu++ is a better choice, if you want to load NDS Homebrew apps or something.

File's location is /_nds/Relaunch/menu.bin, so it should be working I think.
I use TWLM++ for NDS stuff, but it stopped supporting loading DSi homebrew in 3DS. Now it just works in DSi via Unlaunch, so I thought using Relaunch could help me in this. I've made SM64 DSi port boot via Memory Pit exploit in 3DS, but it's quite cumbersome and not a practical way to do it.

Relaunch doesn't support DSi Homebrew Loading, as far as i know, so that might be why it black / white screened. Relaunch also is just a look-a-like of Unlaunch like the repo description says.


Add types to package.json exports field

Like this:
  "exports": {
    "import": "./src/index.js",
    "require": "./dist/index.cjs",
    "types": "./types/index.d.ts" // <-- this
  }

Otherwise, atleast in vscode, it produces an error saying:
Could not find a declaration file for module 'esbuild-plugin-copy-watch'. '.../node_modules/esbuild-plugin-copy-watch/src/index.js' implicitly has an 'any' type.
  There are types at '.../node_modules/esbuild-plugin-copy-watch/types/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'esbuild-plugin-copy-watch' library may need to update its package.json or typings.

added to v2.2.0


Update user_guide.md

Inserted a note about putting blank lines before and after code blocks, since we've had issues with it in the past.

Excellent point, thanks for documenting this.


Make external secret name changes get picked up

When you fetch a non-existent secret from the Doppler API, you get a payload that looks like this:
{
  "name": "FOOBAR",
  "value": {
    "raw": null,
    "computed": null
  },
  "success": true
}

This means that after the initial secret creation, if someone changed the name of the secret outside of Terraform, the only way Terraform would know is due to the secret comparison (null vs the expected value). This usually works fine, but if you're using Terraform to seed secrets and expect the value to change, you would add a lifecyle argument like this:
lifecycle {
  ignore_change = [ value ]
}

This ignores the value as expected, but has the side-effect of making it so if someone renames the secret, Terraform will never notice because it always gets an empty object with the correct name back. To fix this, we now check if the Raw and Computed values of the secret are empty. If they are, we return a truly empty secret object rather than what we got back from the API.

This actually breaks in other ways. Looking at what else we can do...


[kube-up][scale-out] kubernetes-dashboard pod stuck in CrashLoopBackOff state

What happened:
after 1x1 kube-up scale-out cluster starts, found kubernetes-dashboard is stuck in CrashLoopBackOff state:
$ ./cluster/kubectl.sh --kubeconfig=cluster/kubeconfig.tp-1 get pod -n kube-system -l k8s-app=kubernetes-dashboard
NAME                                   HASHKEY               READY   STATUS             RESTARTS   AGE
kubernetes-dashboard-848965699-288nn<PHONE_NUMBER>953097305   0/1     CrashLoopBackOff   8          25m

What you expected to happen:
pod in Running state
How to reproduce it (as minimally and precisely as possible):

starts 1x1 kube-up scale-out cluster;
on TP master, run kubectl get pod -n kube-system -l k8s-app=kubernetes-dashboard

Anything else we need to know?:
Environment:

Arktos version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools: kube-up scale-out 1x1
Network plugin and version (if this is a network-related bug):
Others:

below is the pod log:
2022-01-24T22:52:33.527601719Z stderr F 2022/01/24 22:52:33 Starting overwatch
2022-01-24T22:52:33.527705698Z stdout F 2022/01/24 22:52:33 Using in-cluster config to connect to apiserver
2022-01-24T22:52:33.528021655Z stdout F 2022/01/24 22:52:33 Using service account token for csrf signing
2022-01-24T22:52:33.628043796Z stdout F 2022/01/24 22:52:33 Error while initializing connection to Kubernetes apiserver. This most likely means that the cluster is misconfigured (e.g., it has invalid apiserver certificates or service ac
count's configuration) or the --apiserver-host param points to a server that does not exist. Reason: the server has asked for the client to provide credentials
2022-01-24T22:52:33.628086328Z stdout F Refer to our FAQ and wiki pages for more information: https://github.com/kubernetes/dashboard/wiki/FAQ

Check whether this is service related

latest (crashing)pod log is
{"log":"2022/02/25 00:52:38 Starting overwatch\n","stream":"stderr","time":"2022-02-25T00:52:38.173140985Z"}
{"log":"2022/02/25 00:52:38 Using in-cluster config to connect to apiserver\n","stream":"stdout","time":"2022-02-25T00:52:38.17335097Z"}
{"log":"2022/02/25 00:52:38 Using service account token for csrf signing\n","stream":"stdout","time":"2022-02-25T00:52:38.174494935Z"}
{"log":"2022/02/25 00:52:41 Successful initial request to the apiserver, version: v0.9.0\n","stream":"stdout","time":"2022-02-25T00:52:41.419075285Z"}
{"log":"2022/02/25 00:52:41 Generating JWE encryption key\n","stream":"stdout","time":"2022-02-25T00:52:41.419115339Z"}
{"log":"2022/02/25 00:52:41 New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Starting\n","stream":"stdout","time":"2022-02-25T00:52:41.419278836Z"}
{"log":"2022/02/25 00:52:41 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-system\n","stream":"stdout","time":"2022-02-25T00:52:41.419292974Z"}
{"log":"2022/02/25 00:52:45 Initializing JWE encryption key from synchronized object\n","stream":"stdout","time":"2022-02-25T00:52:45.576608983Z"}

I got the following error:
{"log":"2022/02/25 04:26:46 Using in-cluster config to connect to apiserver\n","stream":"stdout","time":"2022-02-25T04:26:46.464932633Z"}
{"log":"2022/02/25 04:26:46 Using service account token for csrf signing\n","stream":"stdout","time":"2022-02-25T04:26:46.4663454Z"}
{"log":"2022/02/25 04:27:16 Error while initializing connection to Kubernetes apiserver. This most likely means that the cluster is misconfigured (e.g., it has invalid apiserver certificates or service account's configuration) or the --apiserver-host param points to a server that does not exist. Reason: Get https://<IP_ADDRESS>:443/version: dial tcp <IP_ADDRESS>:443: i/o timeout\n","stream":"stdout","time":"2022-02-25T04:27:16.468615797Z"}
{"log":"Refer to our FAQ and wiki pages for more information: https://github.com/kubernetes/dashboard/wiki/FAQ\n","stream":"stdout","time":"2022-02-25T04:27:16.468661528Z"}


WRQ-12037: Investigate how to mock core/platform and webos/platform

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[x] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Enact libraries like Sandstone have a few code to work on specific browser versions or specific platform environments but we don't test those logics in unit tests due to lack of mocking.
So we should investigate how to mock core/platform and webos/platform in unit tests
Resolution
I added an example unit test here (https://github.com/enactjs/sandstone/pull/1605) to show how to mock core/platform or webos/platform.
We can mock core/platform or webos/platform by parsing "mock userAgent".
By the way, if platform information is detected once by parsing user agent, "detectedPlatform" is used after that.
We can't test multiple platform in one unit test file.
So I changed detect function not to reuse "detectedPlatform" on dev mode.
Additional Considerations
Links
WRQ-12037
Comments
Enact-DCO-1.0-Signed-off-by: Jiye Kim<EMAIL_ADDRESS>

@vJIYEv Could you update the subject and description of this PR? Thank you!


[MRG] Fix handling of cell arrays and loading of evoked mat files when channels are not in info

Reference issue
Fixes #7293
What does this implement/fix?
This PR fixes two bugs found when investigating #7293:

The error message returned when the data structure is a cell array was not intuitive.
When a channel was not present in the info object but in the loaded evoked data, the function would crash.

the azure pipelines fail with some access violation. no idea whats wrong there...

@agramfort should we rerun the tests?

Restarted but if it fails again you can ignore scalp_coupling failures if they are the cause, these will be fixed by #7319

ok, codecov complaining seems to come from the fact that pandas seems to be always available. is this correct?

It's not available on all builds, there is a minimal one. But that build also does not have h5py and a lot of other things so it might not hit all branches in your code

(this is fairly common though and not worth fighting here to deal with, we can live with it)

ok. so, from my side this is fine now. could you guys take a look and see if there is something i missed or still need to do?

ok, i added the chnages proposed by @larsoner and already added to one test by @agramfort to the other tests needing it.
CI failures seem to not come from my code....

Thanks @thht !


--script not working with aws-cfn-bootstrap

I'm guessing this is NOT a pex issue, but I'm having a hard time figuring out what the issue is as I have been able to successfully use --script for other packages so maybe someone here can point me in the right direction. When running pex with the aws-cfn-bootstrap:
$ pex -v --script cfn-signal https://s3.amazonaws.com/cloudformation-examples/aws-cfn-bootstrap-latest.zip
  aws-cfn-bootstrap 1.4solving distributions :: Packaging
  pystache 0.5.4
  python-daemon 1.6.1
  lockfile 0.12.2
  setuptools 40.4.2
Traceback (most recent call last):
  File "/usr/local/bin/pex", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/pex/bin/pex.py", line 737, in main
    pex_builder = build_pex(reqs, options, resolver_options_builder)
  File "/usr/local/lib/python2.7/dist-packages/pex/bin/pex.py", line 680, in build_pex
    pex_builder.set_script(options.script)
  File "/usr/local/lib/python2.7/dist-packages/pex/pex_builder.py", line 225, in set_script
    script, ', '.join(str(d) for d in self._distributions)))
pex.pex_builder.InvalidExecutableSpecification: Could not find script 'cfn-signal' in any distribution python-daemon 1.6.1, setuptools 40.4.2, pystache 0.5.4, lockfile 0.12.2, aws-cfn-bootstrap 1.4 within PEX!

The bin/cfn-signal script is listed in the setup.py file. I have also tried the above pex command with bin/cfn-signal which shows the same error as above.
Inside a virtualenv, if I install this same zipfile, the cfn-signal is runnable as I expect.
Versions:
sherzberg@lla434d9ba5162~/workspace
$ pex --version
pex 1.4.6
sherzberg@lla434d9ba5162~/workspace
$ python --version
Python 2.7.12

Any ideas on what the issue could be?

This is definitely a bug! We do not properly normalize - to _ in distribution names when searching for script paths. Fix coming.

Tangentially related: #383 That issue similarly concerned distributions with - in the name, but differently revolved around the generated wheel file name not properly using _ in place of -; ie: the problem was on the wheel generation end and out of pex's control. In this case pex is failing to convert - to _ when searching for a data directory internal to the wheel file itself; ie: the - to _ conversion did occur during wheel generation but pex fails to take this into account when doing script searches.

Noting this is a dup of #443


Selected interventions screen

Let's change the "Selected Interventions" header to "Created Interventions". Also, let's drop the "Base year: 2023". Finally, let's change the purple button label from "Review" to "Edit" to communicate the need for actually making changes in the models.

Udpated in version 1.14.0


Issue With Multiples Module

Hi!
I've been trying to simulate a star cluster with primordial binaries using ph4, smallN, Kepler and the multiples module. However I've noticed that this runs at the same speed as ph4 by itself. Looking further into this, I've noticed that when I run the simulation Kepler_worker and smallN_worker both run but use almost zero memory and cpu time suggesting they aren't working properly.
For testing this I've been using this amuse-masc example script: https://github.com/rieder/amuse-masc/blob/main/examples/MASC and Multiples.ipynb
According to multiples_code.get_total_multiple_energy() there are zero multiples, even if I increase the binary fraction towards 100% or reduce the semi major axis which makes the code grind to a halt. Despite this, Kepler and smallN continue to use the same negligible cpu time. Could this be a problem with my installation? Any help would be appreciated!
Thanks,
Fred

Sorry to get to this late.
Did you set a(n interaction) radius for the stars? This is required for multiples to work, if it is non-existent or set to a very small value, the gravity code will do all the work - resulting in the behaviour that you are seeing.

Ah yes, increasing the radius to a few AU makes smalln and Kepler work correctly with interactions handled with multiples. Thank you!


Changes to allow dashes "-" in branch names

Added quoting to the nodes tables so hibernate properly handles table names with dashes
Still need to add test cases

Added tests as part of refactoring for #65


Image source not updated with dark/light mode

Describe the bug
With React Native, I am trying to use "useColorModeValue" to change the path of an image, without success.
For example:
const image = mode(list_images[name], list_images[${name}_dark]) only displays the day mode image; although they both exist and displays well separately.
so my question is: how can we toggle from an image to another based on the color mode?
Platform

NativeBase version : 3.2.2
Device: all
React Native version 0.66

This might be related to https://github.com/GeekyAnts/NativeBase/issues/4268
A workaround is to change key attribute on the Image to force re-render.

This might be related to #4268 A workaround is to change key attribute on the Image to force re-render.

This was exactly the issue, thank you so much!
I've spent way too much time trying to fix this. :)

We will use #4268 for further discusssions.


License

Hello.
Can you please specify a license for this very useful project ?

Hi,
I added licence
https://github.com/hafizbilal112/ion-fab/commit/161096adbdd5e57a69876a0190385c9a5099282c

Thanks :)