Adds HTML Starter Template - Fixes #7783

Nice! Was this pulled from one of our existing starter projects?

Yes, it came from the starter template. I simplified it and removed "" because that is not required to use foundation.

@andrewbiddinger We'd prefer to have that in there, it's a key plugin to encourage folks to use our accessibility-friendly components, while being able to remove outlines.

No problem @gakimball ! I upated that in: #7785

Thanks :)


ARB functionality in ActiveMerchant is deprecated and will be removed in a future version

Just noticed the following while utilizing the last version of your gem:
"ARB functionality in ActiveMerchant is deprecated and will be removed in a future version. Please contact the ActiveMerchant maintainers if you have an interest in taking ownership of a separate gem that continues support for it."
How are you expecting to support recurring billing if you get rid of this functionality?
Will you ultimately remove the entire AuthorizeNetArbGateway class?
Unless you have an alternative, Is there an actual reason for doing so, or could you just keep it there for people to use if they still want to?

Hi Julien,
See the discussion at https://github.com/Shopify/active_merchant/pull/1178
for more details.
Luke
On Mon, Jun 1, 2015 at 6:59 PM, Julien Defrance<EMAIL_ADDRESS>wrote:

Just noticed the following while utilizing the last version of your gem:
"ARB functionality in ActiveMerchant is deprecated and will be removed in
a future version. Please contact the ActiveMerchant maintainers if you have
an interest in taking ownership of a separate gem that continues support
for it."
How are you expecting to support recurring billing if you get rid of this
functionality?
Will you ultimately remove the entire AuthorizeNetArbGateway class?
Unless you have an alternative, Is there an actual reason for doing so, or
could you just keep it there for people to use if they still want to?
—
Reply to this email directly or view it on GitHub
https://github.com/Shopify/active_merchant/issues/1718.


TN-3250, incorrect type in check for withdrawn from study

The view used to determine which questionnaires (assessments) a given patient needs to submit, was incorrectly comparing an OverallStatus instance with the string Withdrawn.  Thus, patients withdrawn from a given study would incorrectly be administered assessments.
Extending this hotfix to include exclusion of questionnaire responses after withdrawn visits - actually now excluding ALL questionnaire responses that aren't associated with a valid questionnaire bank (i.e. a visit).

The view used to determine which questionnaires (assessments) a given patient needs to submit, was incorrectly comparing an OverallStatus instance with the string Withdrawn. Thus, patients withdrawn from a given study would incorrectly be administered assessments if any had been left in-progress.

@pbugni  that might explain the first QR that patient 5596 completed post-withdrawal (#65241), but it doesn't seem to explain what happened with their QR 72971 completed 2023-07-06, many months after their withdrawal in Oct '22.
https://movember.atlassian.net/browse/TN-3250?focusedCommentId=246743

@mcjustin sorry for the confusion in my initial comment, the in-progress scenario is not the only one that would incorrectly have been given the chance, I had just watched that scenario in the debugger.  The check was in general, for a user being withdrawn from a study.

i'd like to rename the branch (from hotfix/x to feature/x) as we're not releasing as hotfix, but that would mean closing out this PR and losing the history, so, we'll live with it.


Serve static content from CDN URL instead of root

What problem does this feature solve?
I'd like to serve static files (e.g. /favicon.ico, /nuxt/*.js files, etc) from my CDN instead of through the /root. So:

Becomes
<link rel="preload" href="https://cdn.domain.com/_nuxt/e2f83b381b20a43ed771.js" as="script">

I'm not sure if this is possible yet, but it would greatly improve PageSpeed scores.
What does the proposed changes look like?
Not sure. Perhaps setting a /root/ path in Nuxt.config that equals '/' but could also be 'https://cdn.domain.com/'

This feature request is available on Nuxt community (#c10722)

This is now implemented in Nuxt 3 as default behaviour.


Setup Bug

A setup should pause at the end of the setup and not go to the beginning of the next setup until ready

Waiting for new MachineState functionality to implement this

Now fixed to stop at the end of the setup with #393


Update Create Photo Routes

Create photo route currently responds with text "Photo Created" and directs to another page. Ideally we should support with HTMX to update the page with the created photo and a message. Staying on the same page. We can also just update the page (w/o HTMX).

#5


Instructions for HTTPS

When you get some time, could you please provide instructions for HTTPS configuration. It would be much appreciated.

Ack, will look into using acme server for let's encrypt certificates at some point and adding those instructions.

I spent some time on it this weekend...  I'm hesitant to do this because of the non-trivial complexity dealing with let's encrypt.  In particular, you must use a provider specific (eg. google domains, aws, or similar) api to enable wild card certificates for a domain, without doing manual authentication.  If this is going to be a good reference for serveo, I don't want to have steps that say "go to this point, stop, use this completely different non-trivial tutorial, and come back to this step"...  LMK.

Could you suggest a common/popular way forward? Just pick one - maybe Google Domains and add the instructions for that? I really would like to get HTTPS going.

Ok... As I use Google domains I will do that...
On Thu, Oct 10, 2019, 6:40 PM k3tan172<EMAIL_ADDRESS>wrote:

Could you suggest a common/popular way forward? Just pick one - maybe
Google Domains and add the instructions for that? I really would like to
get HTTPS going.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/japharl/serveo_local/issues/2?email_source=notifications&email_token=AAJR56XOFZYKG3NBIQ5OLLDQN6VOLA5CNFSM4IUW4RIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA6GEQI#issuecomment-540828225,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJR56XLEMFQ2RC7KKSHQPTQN6VOLANCNFSM4IUW4RIA
.

Made some progress, slowly.  Google domains isn't easy to work with.  Attempting to use digital ocean for the dns stuff.  I'll update when I make further progress.  Ran into a catch 22, which I think is related to the multiple attempts to get cert bot to work correctly.

Ran into catch 22 again.  certbot requires a different module library version than the plugin dns-digitalocean does.  I'll revisit in 2 weeks or so.

Ran into a different catch 22...
I ended up giving up on certbot. It doesn't see to work correctly with digital ocean.
I tried acme.sh .  This allows for the certificate to be correctly issued.  However, unfortunately, I'm not sure what of the certificates that were generated as to what the correct parameters are for the serveo client.  Once serveo.com comes back up, I'll ask the mailing list, but not before.

No joy... it's like serveo isn't recognizing the option for the cert directory...   If it's not doing that, I'm not sure what I can do...

It's all good, thanks for your efforts. I have a way of getting HTTPS through Cloudflare's free service, so I'll continue using that.
Thanks!

Sounds good, thank you! If I ever pick this up again I'll let you know.
On Sun, Nov 10, 2019 at 6:57 PM k3tan172<EMAIL_ADDRESS>wrote:

It's all good, thanks for your efforts. I have a way of getting HTTPS
through Cloudflare's free service, so I'll continue using that.
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/japharl/serveo_local/issues/2?email_source=notifications&email_token=AAJR56TLDTBHLPO5DURZOQLQTCNWRA5CNFSM4IUW4RIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDVKMZA#issuecomment-552248932,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJR56WPGNILDFYGWK3QFRLQTCNWRANCNFSM4IUW4RIA
.

@japharl
Zachary Zebrowski
9302 west St,
Manassas, VA 20110
Woot!
Zak


Consider adding a "Continuous Optimization" section (under Obs)

Here are some companies/projects in the space:
Spot by NetApp
Densify
Turbonomics Moved!!!
Opsani
CloudZero
Granulate
StormForge
BMC Helix
CircleCI (via Vamp)
Zesty
Cast.ai

@AndreyKozlov1984 if you have bandwidth can you work on this?

Yes
Sent from my iPhone

On 24 Feb 2022, at 20:32, Chris Aniszczyk @.***> wrote:

@AndreyKozlov1984 if you have bandwidth can you work on this?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.

I'll make it in a separate branch, let me check if these companies are already in the list or I need to add them to the landscape.yml first!

No ideas about subsections, I'll call it "Continious Optimization" too, and I'll readjust other sections a bit

SGTM
Let's keep it simple first for review. We may have to move things around as the parent section is getting large

Ok, will update you later today!

https://deploy-preview-2495--landscape.netlify.app/ - a first preview, is this ok? I just added one item (spot.io) for now

Added Densify

@caniszczyk Turbonomic is already in observability and analyzes, we can not make duplicates!

Ok, I'll move it to a new place!

This exists now!


PYTHONPATH synchronized without quotes even when spaces are present in path

From<EMAIL_ADDRESS>on 2015-01-15T03:32:21Z
Spyder Version:  2.3.2
Python Version:  2.7.6
Qt Version    :  4.8.6, PyQt4 (API v2) 4.10.4 on Windows
pyflakes >=0.5.0:  0.8.1 (OK)
pep8 >=0.6      :  1.5.7 (OK)
IPython >=0.13  :  2.3.1 (OK)
zmq >=2.1.11    :  14.4.1 (OK)
pygments >=1.6  :  2.0.1 (OK)
pandas >=0.13.1 :  0.15.2 (OK)
sphinx >=0.6.6  :  1.2.3 (OK)
rope >=0.9.2    :  0.9.4 (OK)
matplotlib >=1.0:  1.4.0 (OK)
sympy >=0.7.0   :  0.7.5 (OK)
pylint >=0.25   :  None (NOK)
What steps will reproduce the problem?

Add a path containing spaces using Spyder pythonpath manager
Synchronize path to PYTHONPATH

What is the expected output? What do you see instead?
Expected: Importing modules on the new path (containing spaces) works in spyder and on the command line.
What happens: Importing from the new path only works in spyder, because the path is added to PYTHONPATH without quotes and thus the command line cannot interpret it correctly.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=2116

From ccordoba12 on 2015-02-08T11:20:52Z
Labels: MS-v2.4


Joystick Axis and Buttons not working

I'm able to assign the joystick in the enhanced input mapper, but I can't choose a specific event. When I choose one, it only shows the device name and the event never fires.

I'm using UE5.3 and release 3.2 (the experimental one because of the 5.3 build)

Thanks for reporting this! I was able to replicate it when a device was plugged in that contained spaces in the name.
I have pushed up a fix as part of #59
I will have a release candidate for this out shortly!

3.3.0 is out!
Please feel free to raise another issue if you happen to find something!


Problems with eigenvector

array([[ 8.30060239e+01,
[ 3.62382715e+01,
[-2.02953062e+00,
[ 3.65334519e-03,
[ 2.69058151e+01,
[-2.37457767e+01,
[-2.67653494e+01,
[-2.86296451e+00,
[-1.84055308e+00,
This is the dot product between the first several eigenvectors and an all-ones function.
This appears to be off. Since the first eigenvectors is supposed to constant function and eigenvectors are orthogonal, aren't the numbers starting from the second one all supposed to be zero?
For reference, this is both the case for both robust and non-robust laplacian, regardless of the use for intrinsic representation.

Computing eigenvectors directly from np.inv(A)@W seems to give the correct eigenvalues, but I used the resulting eigenvectors to reconstruct shapes, the results is horrible(turns an apple into a spiky ball)
Using lobpcg seems to produce the correct eigenvalues AND the correct reconstruction.

Hi,
The code is fine, this is just a small mistake on your side.
The eigenvectors are not orthonormal with respect to the standard inner product, but rather with respect to the $L^2$ inner product on the surface. You can also check that they are not normalized with respect to the standard inner product.
The $L^2$ inner product is defined as $\langle f, g \rangle = f^\top A g = \sum_i A_{ii} f_i g_i$, where $A$ is the area matrix. There is a l2_inner method in the TriMesh class in the package.
In the code, this comes from the fact the Laplacian is defined as $\Delta = A^{-1} W$, with $A$ the area matrix and $W$ the stiffness matrix, and that we obtain the eigenvectors solving the generalized eigenproblem $W\Phi_j = \lambda_j A \Phi_j$. In that case, the $\Phi_j$ are orthonormal with respect the the inner product induced by matrix $A$.


DfC #653 Fixed. Added Infrastructure Encryption on Storage. Added Private Link Service Network Policies. Added DNS Proxy. Added Private DNS Zones.

Added KV Private DNS zone among many other Private DNS zones: #790
Fixed defender bug under "Discussion #653"
Added DNS Proxy on Azure Firewall and set it to use Azure DNS: #733
Added Storage Account Infrastructure Encryption: #773
Description
Defender for Cloud:
When deploying and re-deploying DfC, there are several errors that usually happen which are fixed here.
Storage Accounts:
Storage Accounts can only have infrastructure encryption enabled when created. Added code to enable that upon provisioning.
Private Link Service Network Policies:
In order to deploy services like AVD into one of the spokes, there needs to be an option to disable the Private Link Service Network Policies. Added that option and kept the defaults uniform to the Private Endpoint Network Policies.
Private DNS Zones:
Added many Private DNS zones to be used for Private Link
DNS Proxy:
Made the Azure Firewall a DNS Proxy. Azure Firewall will query Azure DNS
Forced all vNets to use the Azure Firewall as the DNS Server
UNABLE to test in Air-Gapped clouds.
Issue reference
The issue this PR will close: #653
The issue this PR will close: #733
The issue this PR will close: #773
The issue this PR will close: #790
Checklist
Please make sure you've completed the relevant tasks for this PR out of the following list:

[ ] All acceptance criteria in the backlog item are met
[ ] The documentation is updated to cover any new or changed features
[ ] Manual tests have passed
[ ] Relevant issues are linked to this PR

merging into branch to do updates


Don't run WebHookEventMapperFilter and WebHookPingRequestFilter together

WebHookPingRequestFilter should execute last of the WebHooks filters

A quick one-liner for you @rynowak

c08026b013


Spectrum display

I would love to see how the repeaters fit into the full Band plan.  I think it could be a cool and fun display for the site.
For now - this will just be an experiment.  I plan to incorporate the full band display, and the allocations as described by
WWARA.
Starting with 2m:

See also the IARU Region 2 Band Plan

Sounds like a fun little addition ! I could do this in matplotlib or something but I figure some cute interactive JS would be fun -- maybe where you can hover over a vertical band representing a frequency, and get a bubble showing the club and callsign or something. I'm probably asking for too much for a toy project...
I'm seeing this laid out quite simply -- maybe a thick, horizontal bar representing a band, with some vertical lines through it representing repeater outputs. We have several bands, so maybe we stack the band bars vertically. Just my first thought -- looking forward to seeing what you come up with !


Open Source Team support in August 2022

@dsarkar
In https://github.com/corona-warn-app/cwa-app-ios/issues/4602#issuecomment-1205004898 you wrote:

FYI, in August we, @larswmh, @svengabr, and @dsarkar from the Corona-Warn-App Open Source Team, will have only very sporadically a look here at the GitHub repositories of the CWA project.

That is quite a surprise, although I did notice that there had been no other activity from the team since last weekend.
I submitted three PRs with corrections for the website.

https://github.com/corona-warn-app/cwa-website/pull/3066
https://github.com/corona-warn-app/cwa-website/pull/3067
https://github.com/corona-warn-app/cwa-website/pull/3068

Will you (or somebody else) process these PRs?

I will also add the following questions here:

What is the plan reg. mirroring issues to JIRA? Will this be done by the developers themselves?
What about the CWA website? CMs always were responsible for updating its content, merging & reviewing PRs, etc.?
Is this break only planned for August or for an undefined period of time?

FYI @MikeMcC399, from @GisoSchroederSAP's statement in https://github.com/corona-warn-app/cwa-app-ios/issues/4602#issuecomment-1205273865:

Regarding the WebPage, which is an important part of the CWA communication and documentation, we will also continue to work on necessary changes/updates.

Closing, as now 2 of the 3 PRs have been merged.

Following up in https://github.com/corona-warn-app/cwa-website/pull/3067 which is still open


col_schema: less strict matching of types and no type matching

I really love the col_schema_match() function and its helper function col_schema(). It's helping to ensure that the columns and types for a transformed table are exactly what we think they should be.
There are some possible enhancements for col_schema(), all in the name of making this less strict (good in some circumstances):

Have an option to use all_of() and any_of() for the column types. Columns like datetime have POSIXct and POSIXt and it would be nice to just specify one of those with any_of("POSIXct")

Have it so we don't need to specify the column types (if we just want to ensure the column names are present)

Thanks again for your awesome work in this really awesome package! Like I said before, it is such an incredible contribution.

Hello @tomryder9 , I worked on your feature request and I’m quite pleased in how it turned out. I took your two-part suggestion and was able to satisfy the requirements by adding an argument (is_exact). Have a look at the updated documentation for all the details, I think you’ll like the implementation.
Thanks for posting this issue. It took some time to get to it, but I’m glad I did. Feature requests like this strengthen the project. I was able to add an extra set of tests and make corrections I might not otherwise have noticed if it weren’t for this issue!

Rich, thank you so much! Again, this is the best package ever and you are such a nice developer ♥
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, October 20, 2020 10:02 PM, Richard Iannone<EMAIL_ADDRESS>wrote:

Hello @tomryder9 , I worked on your feature request and I’m quite pleased in how it turned out. I took your two-part suggestion and was able to satisfy the requirements by adding an argument (is_exact). Have a look at the updated documentation for all the details, I think you’ll like the implementation.
Thanks for posting this issue. It took some time to get to it, but I’m glad I did. Feature requests like this strengthen the project. I was able to add an extra set of tests and make corrections I might not otherwise have noticed if it weren’t for this issue!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Update signature for LSP handlers.

The signature for LSP handlers has changed, see https://neovim.io/doc/user/lsp.html#lsp-handler
This PR should fix #261

Any updates yet?

what happend to @glepnir ?


Add function to turn pins off

Currently there is no function to release pins. Something like the following function would work:
releasePin: function(pinNumber) {
    writeCommand("release " + pinNumber);
}

It seems like this issues has been resolved by pull request #3. Shouldn't this be closed?

correct. thanks @M-Roberts


Command line output, showing detailed class/method coverage

Hello!
I have in the process of integrating coverlet into my CI builds and was wondering if there is a way to have the console output include more detailed information in the table, such as class and method level coverage?
I tried looking through the documentation but I haven't come across anything that specifies if this is possible, and if so what the cli arg would be to enable that.
I will also at some point be hooking up the reporters (such as opencover) but I would also like to have it in the output logs of the build as just a quick reference for local development runs.
Thanks for all the hard work everyone has put into this project!

I have in the process of integrating coverlet into my CI builds

Glad to hear....

if there is a way to have the console output include more detailed information in the table, such as class and method level coverage?

Unfortunatly we don't have that detail or some switch to enable it.
BTW I don't know if could  be a "usable" feature...instrumented type/method could be "a lot", btw at the moment unique solution is to parse and print "by hand" with some script.
Feel free to close the issue if I've answered to your question!And thank's for trying coverlet!

Thanks for the response!
I will close the issue now, however I do think it would be a great feature to think about including in the future if possible. I have used instanbuljs/nyc before and they have a great output table that is very valuable for local development. See their website for an example:
https://istanbul.js.org/
Thanks again!

Thanks to you for link resource!happy coding!


MailExecution keeps running forever when used with Flow triggers, as the task was designed for listeners

Issue description
TL;DR:

I am trying setup an email notifier in case of failure of the flow whose ID is fail_flow.
I have the email credentials stored as global variables just for testing purposes.
MailSend plugin works but MailExecution does not.
I am wondering if my method of using MailExecution plugin is flawed.

Flow (that is built to be failed):
Here is a sample flow. Because of the command exit 1, the flow is always destined to be a failed execution.
id: fail_flow
namespace: ipynbs
tasks:
 - id: test1
   type: io.kestra.plugin.scripts.shell.Commands
   commands:
      - exit 1 # implying processing of 'fail_flow' fails

MailSend
The MailSend plugin seems to be working fine if my flow's code is in the following manner:
id: fail_flow
namespace: ipynbs
tasks:
 - id: test1
   type: io.kestra.plugin.scripts.shell.Commands
   commands:
      - exit 1 # implying processing of 'fail_flow' fails
errors:
  - id: send_email
    type: io.kestra.plugin.notifications.mail.MailSend
    from: "{{ globals['gmail-username'] }}"
    to: "{{ globals['gmail-username'] }}"
    username: "{{ globals['gmail-username'] }}"
    password: "{{ globals['gmail-password'] }}"
    host: smtp.gmail.com
    port: 587
    transportStrategy: SMTP_TLS
    subject: "Kestra workflow '{{flow.id}}' failed"
    htmlTextContent: "Failure alert for flow {{ flow.namespace }}.{{ flow.id }} with ID {{ execution.id }}"

MailExecution
But when I try to use the MailExecution plugin in the folllowing manner (see yaml below), the failure_alert flow gets triggered but keeps running forever and I have to manually kill it:
id: failure_alert
namespace: ipynbs
tasks:
  - id: send_alert
    type: io.kestra.plugin.notifications.mail.MailExecution
    to: "{{ globals['gmail-username'] }}"
    from: "{{ globals['gmail-username'] }}"
    subject: "The workflow execution {{trigger.executionId}} failed for the flow {{trigger.flowId}} in the namespace {{trigger.namespace}}"
    host: smtp.gmail.com
    port: 587
    transportStrategy: SMTP_TLS
    username: "{{ globals['gmail-username'] }}"
    password: "{{ globals['gmail-password'] }}"
triggers:
  - id: listen_fail_flow
    type: io.kestra.core.models.triggers.types.Flow
    conditions:
      - type: io.kestra.core.models.conditions.types.ExecutionFlowCondition
        namespace: ipynbs
        flowId: fail_flow
      - type: io.kestra.core.models.conditions.types.ExecutionStatusCondition
        in:
          - FAILED

Here is the log for the failure_alert flow:

Future work:
In future I am planning to replace the following condition
      - type: io.kestra.core.models.conditions.types.ExecutionFlowCondition
        namespace: ipynbs
        flowId: fail_flow

with
      - type: io.kestra.core.models.conditions.types.ExecutionNamespaceCondition
        namespace: ipynbs

so that I get an email on failure of any flow beloning to the ipynbs namespace.

thanks for the issue, so well described!
I wonder, can you try setting sessionTimeout to a higher value e.g. 20000? this will allow to wait a bit longer for the response from email server

Hi Anna,
Looks like sessionTimeout isn't affecting the way the flow works.
I tried setting the value to 1000 (1 sec), 20000 (20 sec), 30000 (30 sec) - regardless of which I get the following output on the logs:

you are spot on, this is a bug
I checked and unfortunately, the MailExecution seems to have been written in a way that works only with listeners (which we are deprecating soon), but not yet with triggers.
for now, you can validate that this would work:
id: fail_flow
namespace: dev

tasks:
 - id: test1
   type: io.kestra.plugin.scripts.shell.Commands
   runner: PROCESS
   commands:
      - exit 1

listeners:
  - tasks:
      - id: send_execution_alert
        type: io.kestra.plugin.notifications.mail.MailExecution
        from<EMAIL_ADDRESS>        to<EMAIL_ADDRESS>        username<EMAIL_ADDRESS>        host: mail.privateemail.com
        port: 465 # 587
        password: xxxxx
        sessionTimeout: 10000
        subject: "The workflow execution {{execution.id}} failed for the flow {{flow.id}} in the namespace {{flow.namespace}}"
    conditions:
      - type: io.kestra.core.models.conditions.types.ExecutionStatusCondition
        in:
          - FAILED
          - WARNING

Thanks.
The listener task worked perfectly.
How do I setup a flow so that the listener checks for failed execution of all flows in a given namespace, instead of attaching the listener to each flow in a namespace ?

Listeners is a feature we plan to deprecate https://kestra.io/docs/migrations/listeners
So the ideal solution would be if for now, you could leverage the MailSend along with triggers, and once we fix the bug, you can update to MailExecution.

Note that all the notification *Execution tasks are designed to be used inside a listener as they have default alert messages that use the current execution information.
So if you use MailExecution (or any other tasks that end with Execution in this plugin) in a trigger you will have the execution information of the triggered flow not the original flow.

So I found what's going on: the MailExecution (and all other *Execution tasks in this plugin) will try to load an execution based on the configured executionId property (which is the current execution ID by default).
It does this with a retry, waiting for the flow to ends during 10mn.
So if you use it as is, it will wait until it's execution to be terminated during 10 minutes ... which will never occurs as the execution can only be terminated if the task that is waiting for the execution is still running. It waits for itself to ends which will never be the case. Normally after 10 minutes you should see an exception.
So, for this task to be used in a Flow trigger, you must configure it to use the trigger.executionId variable and not the flow execution.id variable so it will use the original execution not the triggered execution.
Using this flow will make it work:
id: failure_alert
namespace: ipynbs
tasks:
  - id: send_alert
    type: io.kestra.plugin.notifications.mail.MailExecution
    to: "{{ globals['gmail-username'] }}"
    from: "{{ globals['gmail-username'] }}"
    subject: "The workflow execution {{trigger.executionId}} failed for the flow {{trigger.flowId}} in the namespace {{trigger.namespace}}"
    host: smtp.gmail.com
    port: 587
    transportStrategy: SMTP_TLS
    username: "{{ globals['gmail-username'] }}"
    password: "{{ globals['gmail-password'] }}"
    executionId: "{{ trigger.executionId }}"
triggers:
  - id: listen_fail_flow
    type: io.kestra.core.models.triggers.types.Flow
    conditions:
      - type: io.kestra.core.models.conditions.types.ExecutionFlowCondition
        namespace: ipynbs
        flowId: fail_flow
      - type: io.kestra.core.models.conditions.types.ExecutionStatusCondition
        in:
          - FAILED
    ```

So this task is currently designed to be used by a listener, we'll need to discuss what you should do but as we cannot change the default for now I will add documentation clarifications.


Error [ERR_STREAM_WRITE_AFTER_END]: write after end

Environment details

OS: Google Cloud Container-Optimized OS
Node.js version: 10.17.0
npm version: 6.12.0
@google-cloud/pubsub version: 1.x (1.1.5, tried reverting down to 1.0.0, same error, currently using 0.21.1)

Steps to reproduce
Unclear so far but have been seeing it after publishing 10k+ messages to various topics. Will get back with more details when we can but if anyone else is seeing this to confirm this isn't a config issue let us know.
We are using our own wrapper around pubsub which you can find here: https://github.com/starchup/google-pubsub-wrapper, extremely bare bones
Error stacktrace

E 2019-11-19T16:49:45.701927239Z events.js:174
E 2019-11-19T16:49:45.702039214Z       throw er; // Unhandled 'error' event
E 2019-11-19T16:49:45.702047675Z       ^
E 2019-11-19T16:49:45.702054717Z
E 2019-11-19T16:49:45.702060707Z Error [ERR_STREAM_WRITE_AFTER_END]: write after end
E 2019-11-19T16:49:45.702068184Z     at writeAfterEnd (_stream_writable.js:248:12)
E 2019-11-19T16:49:45.702074930Z     at ClientHttp2Stream.Writable.write (_stream_writable.js:296:5)
E 2019-11-19T16:49:45.702081282Z     at filterStack.sendMessage.then.message (/node_modules/@grpc/grpc-js/build/src/call-stream.js:372:34)
E 2019-11-19T16:49:45.702088817Z     at process._tickCallback (internal/process/next_tick.js:68:7)
E 2019-11-19T16:49:45.702094878Z Emitted 'error' event at:
E 2019-11-19T16:49:45.702121372Z     at errorOrDestroy (internal/streams/destroy.js:107:12)
E 2019-11-19T16:49:45.702164237Z     at onwriteError (_stream_writable.js:436:5)
E 2019-11-19T16:49:45.702169699Z     at onwrite (_stream_writable.js:461:5)
E 2019-11-19T16:49:45.702174990Z     at /node_modules/async-listener/glue.js:188:31
E 2019-11-19T16:49:45.702180323Z     at process._tickCallback (internal/process/next_tick.js:63:19)

Thanks!

@glesage thanks for reporting! Do you know when this error starting popping up? Did it start after a dependency update or was it there from the start?
Also do you have any insight as to whether this might be coming from the publisher or the subscriber?

This started happening for us when we rolled out version 1.1.5 a few days ago.
Unfortunately I do not know for certain because the app that uses this is both a subscriber and publisher and the stack traces are very un-helpful /: No matter how many try catch blocks we add temporarily to debug they never seem to trigger and our app just crashes without correctly handling this error

We are actually able to go up to v0.29.1 without this issue happening so it seems possible that v0.30.0 introduced it (or exposed it)
Maybe one of the changes to grpc extensions & dependencies has something to do with it. Will try to identify more clearly where it gets thrown tomorrow

We've reverted to version 0.29.1 for now and been using for a week with no issues. Hopefully we'll find some time to debug this some more so we can upgrade but may be a while. Just throwing it out there for those who might be able to (:

As a quick note just ran another test of this and still happening with 1.5.0

Hello,
I can confirm the same behaviour. This usually happens after a couple of hours. After restarting the application everything works fine again.

We are actually able to go up to v0.29.1 without this issue happening so it seems possible that v0.30.0 introduced it (or exposed it) - https://github.com/googleapis/nodejs-pubsub/releases/tag/v0.30.0
Maybe one of the changes to grpc extensions & dependencies has something to do with it. Will try to identify more clearly where it gets thrown tomorrow

Yeah, and this happened in 0.30.0, too:
https://github.com/googleapis/nodejs-pubsub/pull/658
We're looking at just reverting back to the gRPC C++ bindings for now. I'm talking with some folks on Monday before we commit to that. In the meantime, it's possible to manually switch to them and see if it helps:
const {PubSub} = require('@google-cloud/pubsub');
const grpc = require('grpc');
const pubsub = new PubSub({grpc});

Is this still an ongoing problem for everyone? I'm hoping to get us onto grpc-js 1.x soon. That library has really stabilized lately, and is no longer considered beta, so it may help with anything that gRPC C++ previously helped with.

Yess. This issue is affecting a user running @google-cloud/pubsub v1.5.0

I spoke with @megaz94 separately, but I wanted to check once more on this - @google-cloud/pubsub version 2.0.0 should be pulling in a newer (post-1.0) grpc-js, so that may help.

We're also seeing this in @google-cloud/pubsub v1.5.0 too
Did anybody confirm v2 is a fix? I need to choose between bumping to 2.0.0 or passing grpc bindings - can't do both with limited resources, but would prefer to bump to v2

We are still seeing this error on 2.0.0

@glesage @naugtur @matetukacs Can you all describe the character of data being sent and received which is problematic? To unpack that question a bit, I'm asking for e.g. the size of messages, the frequency of message, the length of time before the problem typically happens.
That error stack looks like something from readable-stream. For me, grpc-js is pulling readable-stream 2.3.7, which seems really old. I'm not convinced that's the cause yet, but it seems like we should update that at some point. @murgatroid99 Is there anything in there that sounds familiar and might explain that problem up top?
In general, it sort of looks like the HTTP/2 connection is getting closed on us and we don't realize it, and then we try to write more. The disconnection happens naturally at about 30 minutes in, and we're supposed to be catching that and restarting it. (There was a bug recently about that, which is why I was asking about the character of messages above.)

grpc-js has never had a dependency on readable-stream, so I don't know where that could be coming from.
Regardless, a similar issue was filed in the google-gax repository and it looks like grpc/grpc-node#1436 will address it.

I think the external tag isn't the right thing here, but since there's a fix happening elsewhere potentially, I'm going to put it on there. I'll keep an eye on this for when we can bump the gax dependency.

Experiencing this issue on 2.1.0
Confirmed - I'm getting this error after idling and not receiving a message for about 15 mins<EMAIL_ADDRESS>and<EMAIL_ADDRESS>
I think I'll try switching to the C++ build of grpc

Ah, darn. I was hoping 1.0.5 would fix it. I'm going to go ahead and bump the dependency version anyway, in case it helps the others' issues.

Quick update on this, the consensus was that we probably shouldn't actually do the explicit dependency on grpc-js in here, because it might fall out of sync with other libraries accidentally. The gax library has been updating their dependencies, so in theory, that should be pulling in a newer one now.
At some point I'll plan to update the gax dependency explicitly. This is related to this: https://github.com/googleapis/nodejs-pubsub/issues/879

We are seeing this in v2.3.0 as well

@shufengh It looks like 2.5.0 is the one that pulled in the new gax version explicitly. Maybe give that one a try?
https://github.com/googleapis/nodejs-pubsub/pull/1085

Going through all the existing issues today... is there anyone who's still having this issue on the latest version of the library?

We had to roll back to older version because the grpc.js was causing some trouble.
Didn't check the latest yet.

we are also experiencing the same issue, here is the stack trace.
This issue happens when we have a long running event stream and it times out, all future request afterwards fail because the process is shutdown due to the uncaughtexception.
2020-11-25T20:18:17.836Z - error: write after end stack=Error [ERR_STREAM_WRITE_AFTER_END]: write after end
    at writeAfterEnd (_stream_writable.js:248:12)
    at ClientHttp2Stream.Writable.write (_stream_writable.js:296:5)
    at filterStack.sendMessage.then<EMAIL_ADDRESS>

Is there any solution for this?

Not that I'm aware, but there is a new grpc-js coming out soon that has more debug info that might help us figure it out. There are some related issues happening across several libraries at the moment.

Not that I'm aware, but there is a new grpc-js coming out soon that has more debug info that might help us figure it out. There are some related issues happening across several libraries at the moment.

The new grpc-js update should be available now, though you might have to remove package-lock.json and npm install again to get it.
https://github.com/grpc/grpc-node/pull/1658
As before, please set these environment variables before running your app to see if we can get some more info:
GRPC_TRACE=all
GRPC_VERBOSITY=DEBUG

The new grpc-js update should be available now, though you might have to remove package-lock.json and npm install again to get it.
https://github.com/grpc/grpc-node/pull/1658
As before, please set these environment variables before running your app to see if we can get some more info:
GRPC_TRACE=all
GRPC_VERBOSITY=DEBUG

We'll be upgrading soon and currently see this see this in production. I will follow up with our findings.

We'll be upgrading soon and currently see this see this in production. I will follow up with our findings.

Still seeing this, unfortunately.

Still seeing this, unfortunately.

@arbourd (or anyone else), any luck grabbing some more debug logs for the issue?

Hey @feywind, thanks for reminding me. I'll go check out logs, hopefully the data is still around because I completely forgot about this.
One note: we still see this with 2.8.0 (haven't tried the recently release 2.9.0 yet).

I pulled one out.

Logs
"(node:18) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)",2021-01-27T11:54:48.012083134Z
"    at filterStack.sendMessage.then (/src/node_modules/@google-cloud/pubsub/node_modules/@grpc/grpc-js/src/call-stream.ts:745:26)",2021-01-27T11:54:48.012073864Z
"    at ClientHttp2Stream.Writable.write (_stream_writable.js:296:5)",2021-01-27T11:54:48.012068951Z
"    at writeAfterEnd (_stream_writable.js:248:12)",2021-01-27T11:54:48.012063921Z
(node:18) UnhandledPromiseRejectionWarning: Error [ERR_STREAM_WRITE_AFTER_END]: write after end,2021-01-27T11:54:48.012051001Z
2021-01-27T11:54:48.011Z | call_stream | [3388] sending data chunk of length 66 (deferred),2021-01-27T11:54:48.011747591Z
2021-01-27T11:54:48.011Z | subchannel_refcount | <IP_ADDRESS>:443 callRefcount 9 -> 10,2021-01-27T11:54:48.011743210Z
2021-01-27T11:54:48.011Z | call_stream | [3388] attachHttp2Stream from subchannel <IP_ADDRESS>:443,2021-01-27T11:54:48.011738725Z
,2021-01-27T11:54:48.011734252Z
"		te: trailers",2021-01-27T11:54:48.011730543Z
"		:path: /google.pubsub.v1.Subscriber/StreamingPull",2021-01-27T11:54:48.011726074Z
"		:method: POST",2021-01-27T11:54:48.011721938Z
"		content-type: application/grpc",2021-01-27T11:54:48.011718274Z
"		user-agent: grpc-node-js/1.2.3",2021-01-27T11:54:48.011714366Z
"		:authority: pubsub.googleapis.com:443",2021-01-27T11:54:48.011710313Z
"		accept-encoding: identity,gzip",2021-01-27T11:54:48.011705983Z
"		grpc-accept-encoding: identity,deflate,gzip",2021-01-27T11:54:48.011701391Z
"		grpc-timeout: 899997m",2021-01-27T11:54:48.011688256Z
2021-01-27T11:54:48.011Z | call_stream | Starting stream on subchannel <IP_ADDRESS>:443 with headers,2021-01-27T11:54:48.011672320Z
2021-01-27T11:54:48.011Z | call_stream | [3387] sending data chunk of length 66 (deferred),2021-01-27T11:54:48.011572877Z
2021-01-27T11:54:48.011Z | subchannel_refcount | <IP_ADDRESS>:443 callRefcount 8 -> 9,2021-01-27T11:54:48.011568272Z
2021-01-27T11:54:48.011Z | call_stream | [3387] attachHttp2Stream from subchannel <IP_ADDRESS>:443,2021-01-27T11:54:48.011564143Z
,2021-01-27T11:54:48.011559440Z
"		te: trailers",2021-01-27T11:54:48.011555241Z
"		:path: /google.pubsub.v1.Subscriber/StreamingPull",2021-01-27T11:54:48.011550881Z
"		:method: POST",2021-01-27T11:54:48.011546707Z
"		content-type: application/grpc",2021-01-27T11:54:48.011542403Z
"		user-agent: grpc-node-js/1.2.3",2021-01-27T11:54:48.011538147Z
"		:authority: pubsub.googleapis.com:443",2021-01-27T11:54:48.011533648Z
"		accept-encoding: identity,gzip",2021-01-27T11:54:48.011528827Z
"		grpc-accept-encoding: identity,deflate,gzip",2021-01-27T11:54:48.011524923Z
"		grpc-timeout: 899997m",2021-01-27T11:54:48.011520364Z
2021-01-27T11:54:48.011Z | call_stream | Starting stream on subchannel <IP_ADDRESS>:443 with headers,2021-01-27T11:54:48.011506640Z
2021-01-27T11:54:48.011Z | call_stream | [3386] sending data chunk of length 66 (deferred),2021-01-27T11:54:48.011443244Z
2021-01-27T11:54:48.011Z | subchannel_refcount | <IP_ADDRESS>:443 callRefcount 7 -> 8,2021-01-27T11:54:48.011438764Z
2021-01-27T11:54:48.011Z | call_stream | [3386] attachHttp2Stream from subchannel <IP_ADDRESS>:443,2021-01-27T11:54:48.011434206Z
,2021-01-27T11:54:48.011429904Z
"		te: trailers",2021-01-27T11:54:48.011426324Z
"		:path: /google.pubsub.v1.Subscriber/StreamingPull",2021-01-27T11:54:48.011421962Z
"		:method: POST",2021-01-27T11:54:48.011417847Z
"		content-type: application/grpc",2021-01-27T11:54:48.011413900Z
"		user-agent: grpc-node-js/1.2.3",2021-01-27T11:54:48.011409738Z
"		:authority: pubsub.googleapis.com:443",2021-01-27T11:54:48.011405664Z
"		accept-encoding: identity,gzip",2021-01-27T11:54:48.011400942Z
"		grpc-accept-encoding: identity,deflate,gzip",2021-01-27T11:54:48.011395464Z
"		grpc-timeout: 899997m",2021-01-27T11:54:48.011390784Z
2021-01-27T11:54:48.011Z | call_stream | Starting stream on subchannel <IP_ADDRESS>:443 with headers,2021-01-27T11:54:48.011346076Z
"error: Failed to subscribe ""sync"" - Error [ERR_STREAM_WRITE_AFTER_END]: write after end {""timestamp"":""2021-01-27T11:54:48.010Z""}",2021-01-27T11:54:48.011048105Z

Still seeing this on 2.18.5. Just wanted to call that out. I don't have a whole lot of supplemental information unfortunately.

Linked to the meta-issue about transport problems: b/242894947


The message container is being closed (10398).

Azure Eventhubs » 0.12.0: http://mvnrepository.com/artifact/com.microsoft.azure/azure-eventhubs/0.12.0
refs:

https://github.com/Azure/azure-event-hubs-java/issues/67
https://github.com/Azure/azure-event-hubs-java/pull/78

This looks like a java event hub issue. Hence closing it. We have a new preview version "0.1.0" of the event hubs node.js client. This client was re-written from scratch. Please try the new version and let us know if you still see issues. You can find examples over here.


Publishing Tensorflow wheel package for s390x architecture

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
TensorFlow installed from (source or binary): source
TensorFlow version: v2.3.1
Python version: Python 3.6.9
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source):

Describe the problem
Currently pip install tensorflow command on s390x architecture errors out with No matching distribution found for tensorflow.
This happens because there is no corresponding s390x arch wheel available on PyPI.
I am investigating whether we could push s390x wheel on PyPI and, if so, what are the steps needed.
Nightly/release builds for s390x appear to produce corresponding wheel for s390x as seen here.  There also exists a Release Artifact which can contain s390x Tensorflow wheel which can be pushed to PyPI.
Please let me know if/how this can be achieved. I have tried installing the s390x wheel available from the CI and it appears to have installed on s390x using following commands:
apt-get install sudo wget git unzip zip python3-dev python3-pip openjdk-11-jdk pkg-config libhdf5-dev libssl-dev libblas-dev liblapack-dev gfortran cython3 -y
ldconfig
export GRPC_PYTHON_BUILD_SYSTEM_OPENSSL=True
pip3 install grpcio
pip3 install numpy wheel scipy portpicker protobuf==3.13.0
wget https://ibmz-ci.osuosl.org/job/TensorFlow_IBMZ_CI/lastStableBuild/artifact/tensorflow_whl/tensorflow-2.5.0-cp36-cp36m-linux_s390x.whl
pip3 install tensorflow-2.5.0-cp36-cp36m-linux_s390x.whl

Thanks.

This cannot be done by Google team as we lack headcount for support. Instead, it can be done via SIG Build, as a different project.

This cannot be done by Google team as we lack headcount for support. Instead, it can be done via SIG Build, as a different project.

Thanks @mihaimaruseac - I presume this is what we are referring to.

Yep, that's correct.


fix: typo to apache/superset

SUMMARY
Changed typo on line 566 of Contributing Doc.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Thanks for the typo fix!


Support Symfony PSR-18 HTTP client

To work around issue #1541, we could support the built-in Symfony PSR-18 HTTP client and make it the preferred one to use. Http\Client\Common\PluginClient ensures that a non-async client gets wrapped by EmulatedHttpAsyncClient and this allows us to not have to change anything in the rest of the codebase. There is no version of Symfony that doesn't have both the PSR-18 and Httplug client, so the possibilities of instantiating the SymfonyHttplugClient class should be none.
Since the HttpTransport is already syncronous, I don't expect any performance penalty with this change. However, the dependency on the php-http/message-factory package can now be removed safely.

Can you push the branch to this repo? This will make it easier for folks giving this a try.

Sure, here it is. I will keep it in sync with the one in my fork repo so that I don't have to open a new PR.

@cleptric do you want to move forward with this? One week should be enough to gather for feedback considering the activity of the original issue

@ste93cry please update the PR and move the branch to this repo. I can run some tests this week.

move the branch to this repo

I've already pushed the branch to this repo too. However I would prefer to keep working on my fork so that I don't need to close this PR, resulting in a loss of the context and conversations we had. In the end, the source branch should not matter much...

@cleptric do you have any news? If you don't want to proceed, I will close the PR because there's no point in keeping it open for so long

Closing this because it's evident that there is a lack of interest in merging this PR, especially now that the new SDK is out.


Which commit matches your published work (for HumanEval-rs)?

I'd like to run your code as it was implemented for the original paper.  Would it be possible to add a link in the README that points to the specific commit representing the code used to achieve your results as published in the Reflexion paper?  Thanks!

Critical reading failure on my part -- I see now that you do reference how to find the original code.  Closing this.  Thank you!

Critical reading failure on my part -- I see now that you do reference how to find the original code. Closing this. Thank you!

Reopening, as I can't find any code in reflexion-draft that references your published results against HumanEval-rs.

Hi @geekoftheweek , you can use the run script here https://github.com/noahshinn024/reflexion/blob/main/programming_runs/run_reflexion.sh. The only changes have been refactorings on the original code. Let me know if there are any questions

Hmm.  Perhaps you can help me understand, then, why these two files have different prompt text?

https://github.com/noahshinn024/reflexion/blob/8f1a188b51a8d23501ca242d2b4281eb52d5616b/generators/rs_generate.py
https://github.com/noahshinn024/reflexion/blob/49485efc8fa2514dd98edfb8427ed27ad06fb391/programming_runs/generators/rs_generate.py

@noahshinn @geekoftheweek thanks for this thread.
Are there any updates on the above.
Also, I am struggling to understand the results on alfworld (and how to reproduce them), as e.g. env 1-3 all seem to have been successful for you, however, it never reaches success if running the script.  (Unless the order of envs is different?)
Thank you.


Add information about pymm-eventserver

I added the information about pymm-eventserver at the end of the file. I had to install pandoc on top of the procedure described in the contributing guidelines to make the build of the documentation work, but I think it should be fine.

Awesome thanks!


Update comment-format/check-uppercase to ignore rule flags (fixes #1417)

Fixes #1417

thanks @IllusionMH! don't worry about the build, appveyor is often flaky

@adidahiya ok, thanks!


Why you don't put all user defined things to an independent place ???

Install x64 version, ask uninstall x86 at first, which result lost all setting/snippet .
Why you don't put all user defined things to an independent place ???
Uninstall doesn't mention buckup or export , that's really really bad .
Now I have to recollect my snippet and write settings.

We are very sorry that you've lost your settings but we doubt that VS Code is culprit. As stated in our release notes VS Code preserves all user data when upgrading from 32 to 64 bit:
https://code.visualstudio.com/updates/v1_15#_windows-64-bit

Could it be that you accidentally installed the Insiders version when upgrading? The Insiders version does store its settings in a different place as Stable.
Could it be that you have a tool installed that automatically clears settings after installing a program?

nope,  I download vscode x64 from  https://code.visualstudio.com/Download
nope,  x64 installation tell me to uninstall first, then I goto my vscode folder ,  execute unins000.exe to uninstall . Then  install x64 to same folder.

I do not understand what you mean by "vscode folder". If you mean the place where VS Code is installed, you should not really have to deal with that location.
The correct way to uninstall a program on Windows is through the "Programs and Features" control panel:

And the VS Code Installer will install VS Code into the correct location too.
VS Code does not store user data in that location.
Instead it uses the location %APPDATA%\Code\User\settings.json (which is under AppData/Roaming on my System):

Even the Snippets are stored there.
(for details see https://code.visualstudio.com/docs/getstarted/settings#_settings-file-locations)
This location is the same for 32 bit and 64 bit versions of VS Code. So upgrading does not affect that location in any way and it does not delete that data either.

I think your question "Why you don't put all user defined things to an independent place ???" is sufficiently answered now:
We do store user data independently from the VS Code program.


Install 'grpc' deps into 'lint' environ; ignore 'google' imports under pylint

Rationale:
pylint tries to guess at imports in the google namespace, and fails miserably.  We test that those imports are valid all the time in unit tests anyway, so just disable them in pylint.

@dhermes I've updated pylintrc_default to disable the redundant and buggy import-error check.

the redundant and buggy

Evidence of this? Suggestions for a replacement to lint our imports? (I believe oauth2client uses a flake8 import check plugin.)

With the import-error suppression commented out:
$ tox -e lint
...
************* Module gcloud.logging._gax
I:562, 0: Locally disabling too-many-branches (R0912) (locally-disabled)
I:608, 0: Locally enabling too-many-branches (R0912) (locally-enabled)
E: 23, 0: Unable to import 'google.logging.type.log_severity_pb2' (import-error)
E: 24, 0: Unable to import 'google.logging.v2.logging_config_pb2' (import-error)
E: 25, 0: Unable to import 'google.logging.v2.logging_metrics_pb2' (import-error)
E: 26, 0: Unable to import 'google.logging.v2.log_entry_pb2' (import-error)
...
************* Module gcloud.pubsub._gax
E: 21, 0: Unable to import 'google.pubsub.v1.pubsub_pb2' (import-error)
E: 22, 0: Unable to import 'google.pubsub.v1.pubsub_pb2' (import-error)

But, without touching the lint environment:
$ .tox/lint/bin/python -c "import google.logging.type.log_severity_pb2, google.logging.v2.logging_config_pb2, google.logging.v2.logging_metrics_pb2, google.logging.v2.log_entry_pb2, google.pubsub.v1.pubsub_pb2; print('OK')"
OK

In any case, it is pointless for them to check imports:  we have tests for that.

Maybe this is the relevant issue?

@PCManticore has been a joy to work with on pylint issues. pylint is a static analysis checker, hence the discrepancy between a working import and the pylint check. It seems we should file a bug with the GAX folks about whatever improper namespace package config is reference in https://github.com/PyCQA/pylint/issues/687

@dhermes Why would we care about pylint reporting import errors:  we know the imports are good, because 100% test coverage.

OK LGTM, go ahead and merge

@dhermes Probably worth reporting an issue on the bug tracker? Sorry for chiming in on a merged PR.

@PCManticore https://github.com/PyCQA/pylint/issues/687 looks like the open issue that matches:  the various packages which install into the google namespace do not all use the same boilerplate for the namespace's __init__.py.  GIven the widesspread adoption of pip/setuptools for installing namespace'd distributions, having the pkg_resources bit work as well as the pkgutils fallback would be ideal.


Fix(eos_cli_config_gen): Remove sorting on class-maps in policy-maps type qos

Change Summary
Remove sorting on class-maps in policy-maps type qos
Related Issue(s)
Fixes #1610
Component(s) name
arista.avd.eos_cli_config_gen
Proposed changes
Replace arista.avd.natural_sort with arista.avd.default([])
How to test
See molecule results
Checklist
Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

LGTM. But IMO, there are 2 more things to edit (which can also be done in other PR). 1) Fix the documentation template, similar to the eos template. 2) Line 10 of eos/policy-maps-qos.j2 template has an extra space before %} and this needs to be fixed.

LGTM. But IMO, there are 2 more things to edit (which can also be done in other PR). 1) Fix the documentation template, similar to the eos template. 2) Line 10 of eos/policy-maps-qos.j2 template has an extra space before %} and this needs to be fixed.

@tgodaA - great feedback, I've incorporated these changes in!


Can't generate multiple pages

I have one template test.html which contains 4 pages and separate by <pdf:nextpage />.
But it only generate one pages.
Using xhtml2pdf -s test.html that have same content with django template give me success result (multiple pages )
Any clue ?

My fault, it because i use :
	@frame {
        -pdf-frame-content: wrap;
		-pdf-keep-with-next:false;
    }

Now i can generate multiple pages :)


Pie Chart loading issue

I can not generate pie chart in Chartist.js 0.7.3 version but it works in Chartist.js 0.5.0. I want to generate horizontal bar chart and pie chart which is support in newer version not in older version. Can any one help me out in this? Bar chart is working fine with following data but pie chart is not working.
var CategoryValueTitleArray = [];
var CategoryValuePointsArray = [];
@foreach (var item in Model.LeadScoringExplicitValues)
{
<text>
CategoryValueTitleArray.push('@item.Value');
CategoryValuePointsArray.push('@item.Point');
</text>
}

var data = {
labels: CategoryValueTitleArray,
series: CategoryValuePointsArray
};
var options = {
    labelInterpolationFnc: function (value) {
        return value[0]
    }
};

var responsiveOptions = [
  ['screen and (min-width: 640px)', {
      chartPadding: 30,
      labelOffset: 50,
      labelDirection: 'explode',
      labelInterpolationFnc: function (value) {
          return value;
      }
  }],
  ['screen and (min-width: 1024px)', {
      labelOffset: 40,
      chartPadding: 20
  }]
];

new Chartist.Pie('#explicit-value-piecanvas', data, options, responsiveOptions);

Passing static data like below it's working but with above code(dynamic data) it's not working
labels: ['Bananas', 'Apples', 'Grapes'],
series: [20, 15, 40]

You should debug what kind of array you're passing to chartist effectively. In the Pie, unlike in all other chart types, you need to pass an array of values [1, 2, 3]. Other charts accept an array of series arrays of values [[1, 2, 3], [1, 2, 4]]

Values passing in array like below:
CategoryValueTitleArray : [ABC,DEF,GHI,Test input added by user,MNO,PQR,STU,WXY,Z,ABCD,XYZW]
CategoryValuePointsArray : [12,15,12,45,78,10,12,4,5,13,20]
Eventhen pie chart not created.
IS it a wrong way to pass data for pie Chart ?

Can you show the output when you do:
chart.on('data', function(data) {
  console.log(data);
});

If I m wring data then it's given [object object]
but if I write data.labels then it gives = [ABC,DEF,GHI,Test input added by user,MNO,PQR,STU,WXY,Z,ABCD,XYZW]
& if I write data.series then it gives = [12,15,12,45,78,10,12,4,5,13,20]

Issue resolved It was a silly mistake, no need for single quotes create points array
Previous :

CategoryValueTitleArray.push('@item.Value');
CategoryValuePointsArray.push('@item.Point');

After :

CategoryValueTitleArray.push('@item.Value');
CategoryValuePointsArray.push(@item.Point);

Glad you've found the issue :-)


[BEAM-115] Make in-process GroupByKey consistent with Beam model

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Rebased onto new runner location.
R: @tgroh
I'll grab a committer's attention once you have considered this.

@kennknowles @tgroh is this important? I was told that InProcess is "done"

This is part of the movement towards the new Beam runner API. The runner itself is done relative to the general state of things with all the runners. This does not pertain to the backported release.

R: @dhalperi since you asked and the tests are now passing.
Previously, tests failed and that's why this wasn't in weeks ago. But now with a rebase they are fixed. Likely it was bugs in the runner since I proposed this before it was done.

LGTM

LGTM


Output character not available in this encoding - when file name has certain character

Tested with DITA OT 3.0.4.
Originally reported here:
https://groups.yahoo.com/neo/groups/dita-users/conversations/topics/43544
So if a DITA map refers to a file name which has the character "ﬁ" in its name the publishing fails with something like:
        C:\Users\radu_coravu\Desktop\DITA OT newest\dita-ot-3.0.4\plugins\org.dita.base\build_init.xml:42: Fatal error during transformation using C:\Users\radu_coravu\Desktop\DITA OT newest\dita-ot-3.0.4\xsl\job-helper.xsl: Output character not available in this encoding (xfb01); SystemID: file:/C:/Users/radu_coravu/Desktop/DITA%20OT%20newest/dita-ot-3.0.4/xsl/job-helper.xsl; Line#: 101; Column#: 5

The XSLT stylesheet "job-helper.xsl" does not specify an encoding to write the text output and on Windows the default platform encoding is not UTF-8 (although it is UTF-8 for Linux and Mac), it's more restrictive. So maybe we can force specify an "UTF-8" encoding on it's xsl:output.

👍 One more of our end users encountered this problem:
https://www.oxygenxml.com/forum/post47819.html#p47817

Because the file lists are for backwards support in Ant, we should have a way to disable their generation and make sure we really don't rely on those files anywhere anymore.

How exactly were the old ANT tasks reading the properties files?
The ANT "loadproperties" task has an attribute to specify the encoding, otherwise it's probably the platform encoding, UTF-8 on Linux/Mac and probably CP1252 on Windows (depending possibly on the region where the installation is performed and the used Windows kit, the language packs it has).

One more similar report from one of our clients:
 [31mError: The following error occurred while executing this line:
   ....dita-ot/plugins/org.dita.base/build_init.xml:39: Fatal error during transformation using ...dita-ot/plugins/org.dita.base/xsl/job-helper.xsl:
  Output character not available in this encoding (x2014); SystemID: file:/..dita-ot/plugins/org.dita.base/xsl/job-helper.xsl; Line#: 101; Column#: 5[0m

At a glance it seems one of her files uses an em-dash instead of a plain "-" in the file name.

One more similar report from one of our clients:
 [31mError: The following error occurred while executing this line:
   ....dita-ot/plugins/org.dita.base/build_init.xml:39: Fatal error during transformation using ...dita-ot/plugins/org.dita.base/xsl/job-helper.xsl:
  Output character not available in this encoding (x2014); SystemID: file:/..dita-ot/plugins/org.dita.base/xsl/job-helper.xsl; Line#: 101; Column#: 5[0m

At a glance it seems one of her files uses an em-dash instead of a plain "-" in the file name.


bug: Starter module deployment interrupted by HTTP 409 from Docker registry

Is there an existing issue for this?

[X] I have searched the existing issues

Bootstrap or Starter Module Deployment? (Required)
starter_module
ALZ-PowerShell-Module Version (Required)
2.2.0
alz-terraform-accelerator Version (Required)
2.2.0
Starter Module (Required)
basic
Input arguments of the ALZ-PowerShell-Module (Required)
{
  "default_location": "northeurope",
  "root_id": "es",
  "root_name": "Enterprise-Scale",
  "root_parent_management_group_id": "<redacted>",
  "subscription_id_connectivity": "<redacted>",
  "subscription_id_identity": "<redacted>",
  "subscription_id_management": "<redacted>"
}

Debug Output/Panic Output (Optional)
Error: creating Container Group (Subscription: "<redacted>"
Resource Group Name: "<redacted>"
Container Group Name: "<redacted>"): performing ContainerGroupsCreateOrUpdate: unexpected status 409 (409 Conflict) with error: RegistryErrorResponse: An error response is received from the docker registry 'index.docker.io'. Please retry later.

with module.azure.azurerm_container_group.alz["agent_01"],
on ..\..\modules\azure\container_instances.tf line 1, in resource "azurerm container_group" "alz":
1: resource "azurerm_container_group" "alz" {

Expected Behaviour (Required)
Container instances for self-hosted agents should have been deployed successfully by the starter module.
Actual Behaviour (Required)
Starter module deployment interrupted by HTTP 409 from Docker registry, when trying to deploy container instances for self-hosted agents.
Steps to Reproduce (Optional)
No response
Important Factoids (Optional)
No response
References (Optional)
No response

Closing the issue, the problem was related to the accelerator-bootstrap-modules, which were fixed in version 2.2.0 of the accelerator-bootstrap-modules. Somehow in my configuration I ended up running the accelerator-bootstrap-modules from the previous version.


No response for non-supported HTTP methods

But return simply 405

Created https://github.com/cloudfoundry/uaa/pull/2129 as alternative PR


View multiple files

Using tabs.

Could use https://github.com/georgeOsdDev/react-draggable-tab for UI


[azeventgrid] Event Grid topics system events

Adding in a new systemevents subpackage for the azeventgrid module that contains the System Events used (currently) with Event Grid v1.
APIView: https://apiview.dev/Assemblies/Review/e27ae788fd2d4751ad557223146ed488?revisionId=50ba64bf04e745029373d2b7074d4ee1&diffOnly=False&doc=False&diffRevisionId=68be85f6dbe5462ebefe5c2ea3ca2a83

(Moving this back into draft as I'm doing some cleanup. I was able to add in a bunch of tests using what's in .NET, just translated to Go).


Fix ExistentialSpecializer to correctly cleanup storage.

Handle calling conventions and cleanups in all the places (hopefully).

when ExistentialSpecializer copies the specialized concrete arg into the
original existential value
when ExistentialSpecializer generates a think
when SILCombine substitutes concrete values in place of the opened
existential.

One particularly nasty problem is the existential boxes need to be
destroyed. It is not ok to simply destroy their value. The "leaks"
tool does not catch this problem.
Ownership SIL will make this all much more robust.
Fixes rdar://problem/50595630 Multiple leaks detected - Swift Perf

@swift-ci test.

@swift-ci test source compatibility

@swift-ci benchmark

Performance: -O

TEST
OLD
NEW
DELTA
RATIO

Regression

SortLargeExistentials
6600
16300
+147.0%
0.40x

StackPromo
12800
14100
+10.2%
0.91x

Improvement

BucketSort
2531
150
-94.1%
16.87x

ProtocolDispatch2
207
76
-63.3%
2.72x

ObserverForwarderStruct
660
575
-12.9%
1.15x (?)

ObserverUnappliedMethod
1710
1510
-11.7%
1.13x (?)

DataAccessBytesMedium
47
43
-8.5%
1.09x (?)

Code size: -O

TEST
OLD
NEW
DELTA
RATIO

Regression

BucketSort.o
11050
11618
+5.1%
0.95x

NIOChannelPipeline.o
4218
4357
+3.3%
0.97x

StackPromo.o
1892
1939
+2.5%
0.98x

Improvement

ProtocolDispatch2.o
1940
1740
-10.3%
1.11x

ObserverForwarderStruct.o
3728
3648
-2.1%
1.02x

Performance: -Osize

TEST
OLD
NEW
DELTA
RATIO

Regression

SortLargeExistentials
6700
16200
+141.8%
0.41x

ProtocolDispatch2
206
326
+58.3%
0.63x

DropLastCountableRangeLazy
4
5
+25.0%
0.80x (?)

DropLastAnyCollection
28
33
+17.9%
0.85x (?)

StackPromo
13000
14500
+11.5%
0.90x

PrefixAnyCollection
81
88
+8.6%
0.92x (?)

PrefixWhileAnySequence
1194
1288
+7.9%
0.93x (?)

Improvement

BucketSort
2523
145
-94.3%
17.40x

SuffixCountableRangeLazy
5
4
-20.0%
1.25x (?)

ObserverForwarderStruct
710
585
-17.6%
1.21x (?)

DropFirstAnyCollection
103
86
-16.5%
1.20x

ObserverUnappliedMethod
1740
1520
-12.6%
1.14x (?)

ReversedDictionary2
239
217
-9.2%
1.10x (?)

DataAccessBytesMedium
58
54
-6.9%
1.07x (?)

Code size: -Osize

TEST
OLD
NEW
DELTA
RATIO

Regression

NIOChannelPipeline.o
3651
3963
+8.5%
0.92x

ProtocolDispatch2.o
1968
2084
+5.9%
0.94x

BucketSort.o
11159
11431
+2.4%
0.98x

Improvement

ObserverForwarderStruct.o
3908
3708
-5.1%
1.05x

ObserverUnappliedMethod.o
5563
5354
-3.8%
1.04x

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 64 GB

I cannot reproduce the SortLargeExistentials regression locally. It only showed up in Osize which usually indicates something wasn't inlined.
@rajbarik will you have a chance to review these changes?

@atrick Sorry, I got sidetracked with something and did not see the email until now. I will have a look at it today.


AddChain and fix LSpec infrastructure

Adds some typeclasses and methods to calculate fast exponentiation.

I changed all the tests from inline #lspec to lspecIO so that they are part of the CI.


dbeaver 6.1.5 connetct hive Error: Invalid status 82

HI:
I used dbeaver 6.1.5 to connect hive (using SSH Jump Server, and the jump server connection was successful), but connection results showed that [Could not open client transport with JDBC Uri:jdbc:hive2://<IP_ADDRESS>:42652/default:Invalid status 82], I searched the reason online, but there was no information about [Invalid status 82]. can you help me??

if issue is still actual for you - feel free to reopen the ticket


Add Pony's prerequisites for CPU platforms

Fixes #2836

FreeBSD 11 64bit now has CI support and can be considered "supported".

My head is full of sawdust, but I've force-pushed a new attempt anyway, trying to improve the wording.  If it's (or something else) ok with @dipinhora, then I'll change it in the
https://github.com/ponylang/ponylang.github.io/pull/319 PR also.


using with 'skaffold deploy' made duplicated deployment

Describe the problem/challenge you have
I want to use skaffold for deploying manifest files.

skaffold deploy
backup by velero
delete namespace
restore by velero
skaffold deploy

It resulted in duplicated deployments.
Describe the solution you'd like
A skaffold checks the change of deployed manifests and only deploy difference manifests.
Anything else you would like to add:
Environment:

Velero version (use velero version): v1.0.0
Kubernetes version (use kubectl version):
Kubernetes installer & version:v1.14.0
Cloud provider or hardware configuration:On-Prem
OS (e.g. from /etc/os-release):Ubuntu 16.04.6 LTS

@skame if I understand correctly, skaffold is not recognising the restored manifests and is just re-deploying everything? Do you know what skaffold uses to track manifests?

Yes, your understanding is correct.
I'm looking for what parameter skaffold tracks but I couldn't.
ref. https://skaffold.dev/docs/
I think that label or something may be used for tracking, there I want to know what parameters are omitted in backup/restore.
ref. https://github.com/GoogleContainerTools/skaffold/pull/644

Hmm, I'm not able to reproduce this with skaffold's getting-started example:
> skaffold deploy
Loading images into kind cluster nodes...
Images loaded in 65.157µs
Starting deploy...
kubectl client version: 1.15
pod/getting-started created
Deploy complete in 369.995439ms

> velero create backup skaffold --include-namespaces skaffold
Backup request "skaffold" submitted successfully.
Run `velero backup describe skaffold` or `velero backup logs skaffold` for more details.

> kubectl delete ns skaffold
namespace "skaffold" deleted

> velero create restore --from-backup skaffold
Restore request "skaffold-20190813111246" submitted successfully.
Run `velero restore describe skaffold-20190813111246` or `velero restore logs skaffold-20190813111246` for more details.

> skaffold deploy
Loading images into kind cluster nodes...
Images loaded in 38.7µs
Starting deploy...
kubectl client version: 1.15
pod/getting-started unchanged
Deploy complete in 554.340876ms

Thank you for your test. I also tried to reproduce the situation but I couldn't.
The duplication should be caused by other reason.
I'm sorry to bother you.

@skame no worries! feel free to reopen or file a new issue if you see any issues again!


When I tested the throughput using JMH,found that hikaricp 5.0.0 was faster than version 5.0.1

version 5.0.1
Benchmark                       (jdbcUrl)  (maxPoolSize)  (pool)   Mode  Cnt     Score     Error   Units
ConnectionBench.cycleCnnection  jdbc:stub             32  hikari  thrpt   80  8328.773 ± 102.548  ops/ms
version 5.0.0
Benchmark                       (jdbcUrl)  (maxPoolSize)  (pool)   Mode  Cnt     Score     Error   Units
ConnectionBench.cycleCnnection  jdbc:stub             32  hikari  thrpt   80  10421.351 ± 101.841  ops/ms

jdk graalvm-19
use https://github.com/brettwooldridge/HikariCP-benchmark.git and change hikari version

I don't know what happen between them!

Comparing: https://github.com/brettwooldridge/HikariCP/compare/HikariCP-5.0.0...HikariCP-5.0.1
Only one effective commit https://github.com/brettwooldridge/HikariCP/commit/ed2da5f1f4ef19f871fac12effc0b199706905dc


soundcloud not working with lavaplayer < 1.3.77

Description

Soundcloud return a 401 error whenever i try to play one, problem is a known one and lavaplayer's developper already fixed it.
see here
Would be cool to have the next lavalink version to use this. thanks in advance.

https://github.com/freyacodes/Lavalink/pull/499


Performance very slow with lots of points

When plotting fine-grained data in a line chart (e.g., 3000 points) the responsiveness of the chart is extremely poor.

Try plotting fewer points? :sweat_smile:
j/k It should be able to handle that decently well on a modern machine (wouldn't try it on mobile, though). Could you please provide a bit more information re: your setup? Is transition at a value other than 0? Is interaction enabled? Disabling transition and interaction should improve performance significantly, BTW.

It's the interaction hover-over that is particularly slow :-(
On Sat, Apr 11, 2015 at 4:29 PM, Ændrew Rininsland<EMAIL_ADDRESS>
wrote:

Try plotting fewer points? [image: :sweat_smile:]
j/k It should be able to handle that decently well on a modern machine
(wouldn't try it on mobile, though). Could you please provide a bit more
information re: your setup? Is transition
http://c3js.org/reference.html#transition-duration at a value other
than 0? Is interaction
http://c3js.org/reference.html#interaction-enabled enabled? Disabling
transition and interaction should improve performance significantly, BTW.
—
Reply to this email directly or view it on GitHub
https://github.com/masayuki0812/c3/issues/1075#issuecomment-91944949.

--
Craig Soules
Natero, Founder & CEO
www.natero.com |<PHONE_NUMBER>

Ah, yep — there's probably something that can be done in the library to improve interaction performance-wise, but realise you're asking a lot out of a web-browser to render something that complex and also be interactive.
A thought: do you have any comparable benchmarks with other SVG-based JavaScript libraries, possibly Chartist, NVD3 or Dimple? If C3 is less performant in large datasets, it would be good to have an idea how much less performant it is.

Here's an example that plots 3000 arbitrary points in a C3 graph. Can confirm it's slow on my 2013 Macbook Pro. Oddly, interaction seems to now self-disable in 4.10.0 once ~750 points have been plotted.
That said — turning points off improves performance by quite a lot, because it's not having to render 3000+ circle nodes in SVG.
I haven't been able to get the performance tester on jsFiddle to work, but I might try to do a comparative thing with other SVG JS libraries once I do.

Interestingly, your second example, even set to 5000 points, is displaying
tooltips much faster than our charts with only 4000 points.  I will try
updating our C3 again, since we're on 0.4.9 and it looks like there's been
another release which may have improved performance.
Also, I notice that your chart displays the tooltip based only on the
x-position, and doesn't require hovering over a point, which probably takes
less calculation.  How is that option set, or is that also new as of 0.4.10?
Thanks!
Craig
On Sun, Apr 12, 2015 at 7:50 AM, Ændrew Rininsland<EMAIL_ADDRESS>
wrote:

Here's an example http://jsfiddle.net/aendrew/b58gkjky/ that plots 3000
arbitrary points in a C3 graph. Can confirm it's slow on my 2013 Macbook
Pro. Oddly, interaction seems to now self-disable in 4.10.0 once ~750
points have been plotted.
That said — turning points off
http://plnkr.co/edit/fGB9TIJfJpeKCKUvxK44?p=preview improves
performance by quite a lot, because it's not having to render 3000+ circle
nodes in SVG.
I haven't been able to get the performance tester on jsFiddle to work, but
I might try to do a comparative thing with other SVG JS libraries once I do.
—
Reply to this email directly or view it on GitHub
https://github.com/masayuki0812/c3/issues/1075#issuecomment-92076345.

--
Craig Soules
Natero, Founder & CEO
www.natero.com |<PHONE_NUMBER>

Hi there!
I found something interesting about this problem:

with < 1000 points tooltip is displayed properly
after a point after ~1070 points tooltip disappears strangely
I found that in this case, if  or  or any parent container overflows the screen (only x-overflow, not y) tooltip disappears. If i force the overflow to "hidden", tooltip comes back (without reload).

Thanks for your quality work!
Regards!
Balsa0

it may be could be helpful if we emulate the bind native function.
https://github.com/Funfun/c3/commit/d547a8b1423bba7bf4c540067a8181c0e6c389c4
https://gist.github.com/Funfun/d13978465d2b82690d69
in chrome, 15s vs 22s for 30000 points.

Hey all,
I want to propose a different way of handling this issue. Displaying 3000 points should never be very useful because it exceeds the resolution of any screen. IE, what does it mean to display 3000 points  on a screen that is only displaying 100-200ppi. I think an alternate solution might be to have some sort of re-sampling before rendering. I have 0 experience with javascript, but it seems like it would be fairly straight-forward to re-sample the points to go from 3000 points to something reasonable.
Lets limit ourselves to 1920pixels on the screen. It's unlikely that any plot would take up more than 80% of the screen. That leaves us 1530 pixels that can be applied to points. This is a first cut limit that the graph should never exceed or else data will already be lost so it may as well not try to plot the data anyway. IE, the re-sampling is already happening somewhere and we (or at least I) have no idea how.
In reality 1530 is still way more points then we need as we don't really need each pixel to get a point. I ran a few examples and I would argue that the most points that ever need to be plotted on any reasonable screen is 500. That's a small number! Here is an example of a sin wave with 3000, 1000, and 430 points.
The natural response to this might be that the responsibility of the quantity of data falls to the code generating the data. This is a valid response! But also, a very difficult problem for large real-time datasets. For example, in a dashboard we often want to see the most recent data in detail. So, a user might use something like a subplot to zoom in on the most recent hour of operation. If only enough data is being sent to populate the full time scale (which may be a year, a week, or a day) then there would never be enough data to populate the zoomed timescale. Thus, this is really a plotting issue.
How hard would it be to only propagate the svg with a limited dataset? Could one input to the library be a limited number of points to plot allowing a user to set a maximum number of points to display on any plot? IE, if a limit of 500 were set, the plot would display 500 points at any zoom level. This would allow the page to remain responsive.
Like I said above, I don't know anything about javascript. Nor do I really understand what step is causing c3.js to perform slow. But my guess is it is the rendering of so many points. Instead of figuring out how to render those points faster, perhaps it is valuable to think about the merits of keeping more data on the screen than pixels.

While I agree in concept, if I plot 4 lines on a chart with 500 points each, the problem remains.
It would also be nice to do the sampling within c3 itself and make that optional.

Good point about the multiple lines. That one got by me!!
As for the optional aspect, that is what I am thinking. The user should be able to stipulate some limits and then c3 would automatically sample the data based on the zoom level. If you got clever about it you could make a dynamic sampling based on the first derivative and my guess is you could get a huge reduction in rendering load.
Can we please switch the internet to python so I can actually contribute to this? Who has the time to learn javascript.

Also, I notice that your chart displays the tooltip based only on the
x-position, and doesn't require hovering over a point, which probably takes
less calculation.  How is that option set, or is that also new as of 0.4.10?

Was wondering the same. Is there an option to activate that behavior?
Same charts do it like this, some only if you hover over the graph.

To people running into @balsa0 's problem, the solution seemed to be making sure you pass data for the x columns. If you allow the default behavior (no passed x columns), it doesn't seem to work with the tooltip at larger data sizes.

@murenrb's suggestions are probably the most relevant in here, and a very good point. In my (now greater since first posting in this issue) experience with SVG, any SVG with >1000 elements will be slow. Full stop. Desktop, mobile, whatever. This is elements, not data points — with interaction on, each data point creates anywhere from 1-3 elements, each with their own event handlers (an invisible sort of Voronoi-style grid is placed above the data points, which improves UX but at the cost of performance).
What C3 probably needs more than a bunch of micro-optimisations across the board (which it needs regardless; I've never felt the underlying lib is very optimised) is the ability to render to Canvas, or a fork of C3 intended for use with Canvas. #1436 attempted to do this but is terribly outdated.
This issue has become more about tracking weirdness with interaction than anything. As a result, am closing for now.


[Bug]: Actual issue is not conveyed when a non-accessible symbol is used as a computed key with a union expected type for the mapping constructor

Description
$title.
Steps to Reproduce
proj.mod
const string NAME = "name";

proj
import proj.mod;

public function main() {
    map<string>? m = {[mod:NAME]: "Amy"};
}

proj$ bal build
Compiling source
        maryam/proj:0.1.0
ERROR [main.bal:(4:22,4:41)] incompatible mapping constructor expression for type 'map<string>?'
error: compilation contains errors

Affected Version(s)
2201.8.0
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

@MaryamZi from what I observed these const are not public. Since this is comes under module const declaration we should have the public qualifier for the constant.

Yes, the constant is not public, but the public qualifier is optional. The error here should be for the computed key, saying something like there's no such public symbol in mod.


Lease heartbeat: more description update error handling

This PR adds an explanation of Node Lease update failure handling. Corresponding k8s logic: https://github.com/kubernetes/kubernetes/blob/abe6321296123aaba8e83978f7d17951ab1b64fd/pkg/kubelet/nodelease/controller.go#L123

/lgtm

/approve

Page preview:
https://deploy-preview-19673--kubernetes-io-master-staging.netlify.com/docs/concepts/architecture/nodes/

/approve


Update babel plugin

Description
Fixes (issue #) https://github.com/Shopify/sewing-kit/issues/1572

Type of change

[ ]  Patch: Bug/ Documentation fix (non-breaking change which fixes an issue or adds documentation)
[x]  Minor: New feature (non-breaking change which adds functionality)
[ ]  Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[ ] I have added a changelog entry, prefixed by the type of change noted above

🎩
Using this branch as consumer:
https://github.com/Shopify/web-proving-ground/pull/40

in quilt yarn tophat react-i18n ../../web-proving-ground

run dev up && dev s

see dev mode using the original babel plugin

check build/server/main.js and see if (["fr"].indexOf(locale) < 0) { in the translation function of CustomerList

run yarn build

see prod mode using the index generation

check /build/server/main.js and see _translations__WEBPACK_IMPORTED_MODULE_0__[/* default */ "a"].indexOf(locale) < 0 in the translation function of CustomerList

I am still adding doc.
But the code & test are good for review!

all of the requests had been addressed 😸


Typo in example daemon.json files:  default-ulimit(s)

Problem description
It appears that there is a typo in both the in-line examples of Linux and Windows configuration files, daemon.json:  both show the property "default-ulimits": {}.  With dockerd version 17.03 (on Linux), dockerd will fail to start when this is included in daemon.json, complaining:
unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives don't match any configuration option: default-ulimits

If the s is removed from this property, dockerd will start fine.  This is consistent with the documented rule that the config file property names match the corresponding dockerd command-line arguments, which in this case is --default-ulimit (assuming the plural rule corresponds to array-type values only).
Problem location
This can be seen at https://docs.docker.com/edge/engine/reference/commandline/dockerd/#linux-configuration-file; this, I believe, corresponds to the file, _data/dockerd-cli/dockerd.yaml.
Project version(s) affected
This is seen in v1.13 of this repo.  The above mentioned test was done against Docker Engine version 17.03.
Suggestions for a fix
Edit  _data/dockerd-cli/dockerd.yaml, changing "default-ulimits" to "default-ulimit" under both the sections, Linux configuration file and Windows configuration file.  (Note: I only tested the issue under Linux.)

Actually, this may be a bug, see https://github.com/moby/moby/pull/32547

Ah, yes, it's the same - it's a bug https://github.com/moby/moby/issues/32528

Ah, yes.  My impatient searching didn't turn this up.  Thanks!

Hopefully the PR will be merged soon, but there's some investigation going on as to why integration tests didn't reveal the bug 😞

It seems that moby/moby#32547 has been merged, so the docs now reflect the product behavior. I'm going to close this issue, but feel free to comment, if I missed something.


[Observable] Set CON/NON for notifications

RFC7641 states:

A notification can be confirmable or non-confirmable, i.e., it can be
sent in a confirmable or a non-confirmable message.  The message type
used for a notification is independent of the type used for the
request and of any previous notification.

The ResponseWriter and Message interfaces are both missing an option to set the type of a message to CON/NON.
Is there a way to set message type for a notification when responding to a observe request?

I will close this issue. Please if you have still problem please reopen it. Thx


How to write dates and datetimes to database with write_to_source / write_to_model functions

I have a dataframe with date values and when writing it with write_to_model (same for write_to_source) it fails not knowing what to do with it. I tried some dtype values and had no success.
dataframe.dtypes
ds                                      datetime64[ns]
trend                                          float64
yhat_lower                                     float64
yhat_upper                                     float64

BigQuery error:
Error in script /Users/matteo/Projects/fal/jaffle_shop_with_fal/models/orders_forecast.py with model orders_forecast:
Traceback (most recent call last):
  File "/.../lib/python3.9/site-packages/dbt/adapters/bigquery/connections.py", line 174, in exception_handler
    yield
  File "/.../lib/python3.9/site-packages/dbt/adapters/bigquery/connections.py", line 549, in _retry_and_handle
    return retry.retry_target(
  File "/.../lib/python3.9/site-packages/google/api_core/retry.py", line 190, in retry_target
    return target()
  File "/.../lib/python3.9/site-packages/dbt/adapters/bigquery/connections.py", line 378, in fn
    return self._query_and_results(client, sql, conn, job_params)
  File "/.../lib/python3.9/site-packages/dbt/adapters/bigquery/connections.py", line 535, in _query_and_results
    iterator = query_job.result(timeout=timeout)
  File "/.../lib/python3.9/site-packages/google/cloud/bigquery/job/query.py", line 1498, in result
    do_get_result()
  File "/.../lib/python3.9/site-packages/google/api_core/retry.py", line 283, in retry_wrapped_func
    return retry_target(
  File "/.../lib/python3.9/site-packages/google/api_core/retry.py", line 190, in retry_target
    return target()
  File "/.../lib/python3.9/site-packages/google/cloud/bigquery/job/query.py", line 1488, in do_get_result
    super(QueryJob, self).result(retry=retry, timeout=timeout)
  File "/.../lib/python3.9/site-packages/google/cloud/bigquery/job/base.py", line 728, in result
    return super(_AsyncJob, self).result(timeout=timeout, **kwargs)
  File "/.../lib/python3.9/site-packages/google/api_core/future/polling.py", line 137, in result
    raise self._exception
google.api_core.exceptions.BadRequest: 400 Syntax error: Expected ")" or "," but got string literal '2018-01-01T00:00:00.000000000' at [2:1965]

Location: US

TODO: add Postgres error

I believe this is a constraint of the sqlalchemy library. I had to convert dates and datetimes to string

That is a good temporary solution. But I wonder if we could get fal to make this work automatically for date/datetime columns.


refactor(oas): extract uri template logic

relates-to #120

must be rebased after #134 merge

@derevnjuk complexity complains are caused by PostDataConverter, which refactoring we were decided to postpone;
is ready for review, but must be rebased after https://github.com/NeuraLegion/har-sdk/pull/134 merge


How to use asciidoctor-reducer on GitHub itself?

Sorry, this is not an issue per se. I stranded here after following the links given in https://github.com/asciidoctor/asciidoctor/issues/1088#issuecomment-87685739.
My question is, how to use asciidoctor-reducer to solve the problem that include::s are not expanded on GitHub? Optimally there would be a GitHub Action to do the job. If that would be possible, is there already an Action (I couldn't find one)? If not, what would be the steps to do?
Please note that I just started using AsciiDoctor. So a description for dummies would be welcome ;)
Many thanks in advance for your answer!!!

see https://github.com/github/markup/issues/1095
it gives an example: https://github.com/r2d2bzh/docker-build-nodejs/blob/848e41ba6249de933816bce29400606594871e59/.github/workflows/readme.yaml

Thanks for providing that example Hans! I'd be happy to add this little trick to the README.

I've submitted a PR based on this suggestion. See #47.


The regionSpan can change slightly

Hi Claus,
I've noticed the clusters to rearrange when I programmtically change the region of the map. When the user is moving the map by hand, everything is fine and the clusters stay the same. But whenever I use setCenterCoordinate:animated: or setRegion:animated:, the annotation clusters rearrange themselves. I've noticed that the CCHMapClusterController stores the MKCoordinateSpan right before the region is changed, and compares it to the new span afterwards.
In the documentation of setCenterCoordinate:animated: Apple promises:
Changing the center coordinate centers the map on the
new coordinate without changing the current zoom level.

This is true from a human point of view. At least I cannot see the map zoom in. But the span value changes slightly. I've created a branch here to illustrate the issue: https://github.com/plu/CCHMapClusterController/compare/regionSpanBeforeChange
There are three commits. If you reset to the first one (5451b4f765521d5d3fb99493b1a0420ac575b712) and tap on any of the annotations, you'll see that while it's being centered, the clusters are rearranged. The other two commits are not meant to be a proper fix. Just to illustrate the difference.
Do you have any idea how to properly fix this?
Best regards,
plu

I'm still facing issues even with using setVisibleMapRect:animated:. In my app I want to center the map whenever the user selects an annotation. In general this works fine, but in case of a big zoom level, the map view somehow ignores the CGRect that I pass to setVisibleMapRect:animated:. After setting the rect, I end up with a bigger rect than I originally passed in. I couldn't find any solutions so far. Have you experienced a similar behaviour?

I've done some testing with mapRectThatFits:(MKMapRect)mapRect before setting the rect via setVisibleMapRect:(MKMapRect)mapRect animated:(BOOL)animate like described in the docs.
According to [the Apple Docs] (https://developer.apple.com/library/ios/documentation/MapKit/Reference/MKMapView_Class/#//apple_ref/occ/instm/MKMapView/mapRectThatFits:), I assume that the return value of mapRectThatFits:(MKMapRect)mapRect should match the rect that will be applied internally when using setVisibleMapRect:(MKMapRect)mapRect animated:(BOOL)animate
The funny (or annoying) thing is that the calculated rect via
MKMapRect rect = [self.mapView visibleMapRect];
rect.origin.x = point.x - rect.size.width * 0.5;
rect.origin.y = point.y - rect.size.height * 0.5;

never matches the rect returned by [mapView mapRectThatFits:rect]. The size always differs slightly by random values below 0.5. Probably caused by because of all the internal calculations, rounding and conversions by MapKit?
I haven't found any cool way to set the center coordinate or change the visible map rect by not (slightly) changing mapView.region.span.longitudeDelta which is used in CCHMapClusterController to determine if the zoom level changed after changing the map view's region.
I was thinking about adding something like a "zoom change tolerance" so that we ignore marginal zoom changes and only re-cluster when the zoom changed significantly. @choefele what do you think? Should we re-open this issue?

Hmm, the "zoom change tolerance" prevents the CCHMapClusterController from undesired deselections. But then it might happen, that a selected annotation disappears because it gets merged into a cluster. This is caused because a marginal change of longitudeDelta might trigger a "heavy" cluster re-odering like described in https://github.com/choefele/CCHMapClusterController/issues/82. Seems like these issues are highly coupled.


I think that is a bug in telegraf

Hi,
None of data is exported to my InfluxDB, and after see the log i get:
2015/08/28 14:33:41 Error in plugin [io]: error getting disk io info: open /proc/diskstats: no such file or directory
2015/08/28 14:33:41 Error in output [influxdb]: unable to parse 'disk_total,fstype=reiserfs,host=vps371,path=/ value=107374182400i': invalid number
2015/08/28 14:33:41 Error encountered flushing outputs

I only enable mysql and server outputs (mem, cpu, ...)
What can be wrong?
Edit:
Link to screenshot:
https://www.dropbox.com/s/j985ef9uwhih5wb/Screenshot 2015-08-28 14.34.45.png?dl=0
InfluxDB: Last Version: 0.9.2
Telegraf: Last version (i made a clone and build with Go)

What version of InfluxDB and telegraf are you running?

I have edited the post with infos.

@prsolucoes your problem is that your version of telegraf is incompatible with your version of InfluxDB, you will need to downgrade to telegraf 0.1.4 or upgrade your Influx instance to 0.9.3
see the README for more info: https://github.com/influxdb/telegraf#linux-packages-for-debianubuntu-and-rhelcentos

Problems solved after update. Thanks.


Unit 3.9 & 3.11 Homework Submission

Submit your blog post here :)
Homework due 5pm Friday!

Amay's Hacks
Notes

Kaiden's Hacks

Yasha's Hacks

Quinn's

Alexa Carlson's Hacks

Safin's hacks

Jake Warren's Review Ticket

David's Hacks

Taiyo's hacks

Liav Bar's Hacks

Nathan's Hacks

Alex's Hacks

Sri's Hacks

Lydia's Hacks

Ederick's Hacks and Notes

Ava's hacks

Noor Bijapur's hacks

Ethan Tran's Hacks

Jeongwoo's Hack

Steven Zhu's Hacks

Mati Danish's Hacks

Shruthi's Hacks

Luka Hacks

Antony's hack


Test docking the plugin widget

Checks that the GUI can be initialized and docked to the napari viewer without throwing an error.

Already failing on GitHub CI!

Couldn't get Qt to work on the Linux runners. But Windows and macOS runs fine. I think as long as it tests on Windows (where the microscopes are) it's of some value.


[#28] implement send photo endpoint

hi! @Ternowy thanks for your contribution!
This night I will check your work and will merge it as soon as I finish!
:raised_hands:

Made some improvements to the docs and added more tests.
Great work! Am releasing right now :rocket:


Filetype filter

I added an optional parameter filetypes (array of strings, which are file extensions) which, if provided, adds the header only to files with the provided filetypes (extensions).
Example use case: I use octopus for deployment of .net applications. To create and push packages to octopus, I use gulp. As part of the package creation I need to add the utf-8 bom to vbhtml and cshtml files. I do not want to add the bom to other files in my stream (dll, resx, png, ...)

This is really beyond the scope of this plugin... use gulp-if in order to only apply header to certain files.


Improve options code documentation

This improves the code documentation for the standard Options types, primarily around generic type documentation.

(/cc @HaoK – this is a quick one 😄)


Should bypass error message from Browser to OidcClient

https://github.com/IdentityModel/IdentityModel.OidcClient2/blob/ed7044f9aa7803c7a3879a64167c6ad49167aaac/src/AuthorizeClient.cs#L67
Should be changed to
result.Error = browserResult.Error;

thanks - I will have a look.


import jquery

the user interface will require jquery due to it's bootstrap dependency.

Imported with commit: 8252bdba1c82dcc2d0d8a7ec23f7a66f9abda9c8


Escape "composer license" command line arguments

Addresses one point in #39
This introduces a new exit code 2 for situations when the internal command execution is failing, i.e. it is possible to signal "licenses don't fit" independent from "internal issue" if that's relevant for the consumer.
I switched to using the long command-line parameters as they better explain what they are doing.

@dominikb There are some additional points in #39 - shall I put them all into this PR here, or separate them?

I'll cleanup the fixup commits once the tests are green again

Hi, @dominikb  what's the status here. I had the impression all requested changes were addressed.

Hi, @dominikb what's the status here. I had the impression all requested changes were addressed.

Thanks for your patience I had a lot going on.
Just merged your PR and tagged a new version that should be ready to use.
Thanks again for your contribution.