Incorrect version of cryptography used during pip install

When I got to "Lab 4: Ansible dynamic inventory for Azure" I ran into an error running azure_rm.py
Error
[lab-user@ansibleMaster ~]$ python ./ansible/contrib/inventory/azure_rm.py --list
From cffi callback <function _verify_callback at 0x28a3c08>:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/OpenSSL/SSL.py", line 313, in wrapper
    _lib.X509_up_ref(x509)
AttributeError: 'module' object has no attribute 'X509_up_ref'
, SSLError: HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /f649c560-d5ad-47f8-9660-45061e79fa51/oauth2/token (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')],)",),))

It would appear this issue has to do with 17.5.0 pyOpenSSL Release and a requirements.txt missing the version requirement on cryptography?

pyOpenSSL Release Information
17.5.0 (2017-11-30)
Backward-incompatible changes:
The minimum cryptography version is now 2.1.4.

[lab-user@ansibleMaster ~]$ pip show cryptography
Name: cryptography
Version: 1.7.2
Summary: cryptography is a package which provides cryptographic recipes and primitives to Python developers.
Home-page: https://github.com/pyca/cryptography
Author: The cryptography developers
Author-email<EMAIL_ADDRESS>License: BSD or Apache License, Version 2.0
Location: /usr/lib64/python2.7/site-packages
Requires: idna, pyasn1, six, setuptools, enum34, ipaddress, cffi

Fix
[lab-user@ansibleMaster ~]$ sudo pip install cryptography==2.1.4
Collecting cryptography==2.1.4
  Downloading cryptography-2.1.4-cp27-cp27mu-manylinux1_x86_64.whl (2.2MB)
    100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 2.2MB 544kB/s
Collecting cffi>=1.7; platform_python_implementation != "PyPy" (from cryptography==2.1.4)
  Downloading cffi-1.11.4-cp27-cp27mu-manylinux1_x86_64.whl (406kB)
    100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 409kB 2.8MB/s
Requirement already satisfied: enum34; python_version < "3" in /usr/lib/python2.7/site-packages (from cryptography==2.1.4)
Collecting asn1crypto>=0.21.0 (from cryptography==2.1.4)
  Downloading asn1crypto-0.24.0-py2.py3-none-any.whl (101kB)
    100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 102kB 10.0MB/s
Requirement already satisfied: idna>=2.1 in /usr/lib/python2.7/site-packages (from cryptography==2.1.4)
Requirement already satisfied: six>=1.4.1 in /usr/lib/python2.7/site-packages (from cryptography==2.1.4)
Requirement already satisfied: ipaddress; python_version < "3" in /usr/lib/python2.7/site-packages (from cryptography==2.1.4)
Requirement already satisfied: pycparser in /usr/lib/python2.7/site-packages (from cffi>=1.7; platform_python_implementation != "PyPy"->cryptography==2.1.4)
Installing collected packages: cffi, asn1crypto, cryptography
  Found existing installation: cffi 1.6.0
    Uninstalling cffi-1.6.0:
      Successfully uninstalled cffi-1.6.0
  Found existing installation: cryptography 1.7.2
    Uninstalling cryptography-1.7.2:
      Successfully uninstalled cryptography-1.7.2
Successfully installed asn1crypto-0.24.0 cffi-1.11.4 cryptography-2.1.4

Try
pip uninstall pyOpenSSL cryptography
sudo pip install pyOpenSSL cryptography
shall fix the error.

Thanks much @kshitizsh12 ! For those of us facing the same issue of step 3 on lab 5.
ansible-playbook ~/ansible-azure-lab/new_vm_web.yml --extra-vars "vmname=<placeholder> resgrp=ansiblelab vnet=ansibleVnet subnet=ansibleSubnet"
 [WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

PLAY [CREATE VM PLAYBOOK] ************************************************************************************************************************************************************************
TASK [debug] *************************************************************************************************************************************************************************************ok: [localhost] => {
    "msg": "Public DNS name <placeholder>.westeurope.cloudapp.azure.com resolved to IP NXDOMAIN. "
}

TASK [Create storage account] ********************************************************************************************************************************************************************fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "From cffi callback <function _verify_callback at 0x7f2d11ff0140>:\nTraceback (most recent call last):\n  File \"/usr/lib/python2.7/site-packages/OpenSSL/SSL.py\", line 309, in wrapper\n    _lib.X509_up_ref(x509)\nAttributeError: 'module' object has no attribute 'X509_up_ref'\nTraceback (most recent call last):\n  File \"/tmp/ansible_rFL2nL/ansible_module_azure_rm_storageaccount.py\", line 456, in <module>\n    main()\n  File \"/tmp/ansible_rFL2nL/ansible_module_azure_rm_storageaccount.py\", line 453, in main\n    AzureRMStorageAccount()\n  File \"/tmp/ansible_rFL2nL/ansible_module_azure_rm_storageaccount.py\", line 195, in __init__\n    supports_check_mode=True)\n  File \"/tmp/ansible_rFL2nL/ansible_modlib.zip/ansible/module_utils/azure_rm_common.py\", line 348, in __init__\n  File \"/usr/lib/python2.7/site-packages/msrestazure/azure_active_directory.py\", line 453, in __init__\n    self.set_token()\n  File \"/usr/lib/python2.7/site-packages/msrestazure/azure_active_directory.py\", line 480, in set_token\n    raise_with_traceback(AuthenticationError, \"\", err)\n  File \"/usr/lib/python2.7/site-packages/msrest/exceptions.py\", line 48, in raise_with_traceback\n    raise error\nmsrest.exceptions.AuthenticationError: , SSLError: HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /071cb4fe-bba9-430b-83be-b26821aebcaa/oauth2/token (Caused by SSLError(SSLError(\"bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')],)\",),))\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
        to retry, use: --limit @/home/bruce/ansible-azure-lab/new_vm_web.retry

PLAY RECAP ***************************************************************************************************************************************************************************************localhost                  : ok=1    changed=0    unreachable=0    failed=1

From cffi callback <function _verify_callback at 0x7f81c18556e0>:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 309, in wrapper
_lib.X509_up_ref(x509)
AttributeError: 'module' object has no attribute 'X509_up_ref'
it did not work for me

From cffi callback <function _verify_callback at 0x7f81c18556e0>:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 309, in wrapper
_lib.X509_up_ref(x509)
AttributeError: 'module' object has no attribute 'X509_up_ref'
it did not work for me

Hi filebe777, I got the same problem as you, did you fix that?

Try
pip uninstall pyOpenSSL cryptography
sudo pip install pyOpenSSL cryptography
shall fix the error.

Thanks for your complete solution, and also there were couple of error messages for the symptom

(Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')],)",),))

File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py",  in wrapper     _lib.X509_up_ref(x509) AttributeError: 'module' object has no attribute 'X509_up_ref'

AttributeError: 'module' object has no attribute 'X509_up_ref'

Those come from the same reason and the solution can resolve.

Try
pip uninstall pyOpenSSL cryptography
sudo pip install pyOpenSSL cryptography
shall fix the error.

It works

Try
pip uninstall pyOpenSSL cryptography
sudo pip install pyOpenSSL cryptography
shall fix the error.

worked , great solution thanks

For CentOS victim^H^H^Husers, simply pip uninstall pyOpenSSL and yum install pyOpenSSL.


Unable to download UG2-DarkFace Dataset from the google drive link in the readme file

Hello Authors,
Thanks for the great paper.
Unfortunately, the google drive link to the  "UG2-DarkFace" Dataset on the readme file is broken.
Could you please add the correct link.
Thanks

Hi,
I've added the link, please check.

Thankyou for the quick response.


Option to set initial step

I tried to find option to set initial step in the stepper but couldn't find it.
Can you please provide initial attribute, so that one can set initial step different from step 0.

Hi Atul,
Thank you for your feedback. Please be sure, it will be added in the upcoming 0.1.2+7 release. I will keep you posted!
Meanwhile, if you like, you can check the latest publication about im_stepper package on medium here.
Regards
iMujtaba Nazki

Hi Atul,
The ability to set the initial step and jump to different steps has also been added. Also, a new activeStep property has been introduced in the im_stepper package that gives you access to control steppers in a much easier way.
Please check out the new release here and examples here. Once again, thank you for your patience and feedback!
Warm Regards,
iMujtaba


mtkime false positives?

the following code produces an error
$month_text = date('F', mktime(0, 0, 0, $_REQUEST['rMonth'], date("d"), $_REQUEST['rYear']));

of:
TypeError arg#5(day) is string but mktime() takes int

but date("d") does return an integer.

No it doesn't.
php > var_dump(date('d'));
string(2) "16"

Thank you for showing me the technique; I learned something new.  I will cast the output of date("d") to int.


Is this repo implement NIC_v1 or NIC_v2?

I have a question about this repo: Is this repo based the paper <Show and Tell: Lessons learned from the 2015 MSCOCO Image Captioning Challenge> or  < Show and Tell: A Neural Image Caption Generator >?
I found there are 2 paper about Show and Tell / NIC:
https://arxiv.org/pdf/1609.06647v1.pdf
《Show and Tell: Lessons learned from the 2015
MSCOCO Image Captioning Challenge》 -----------------------Implement NIC_v2
https://arxiv.org/pdf/1411.4555.pdf
《Show and Tell: A Neural Image Caption Generator》 -----------Implement NIC_v1
I noticed that the readme.md of this repo shows Show and Tell: A Neural Image Caption Generator , but I am not sure

Sorry for the delayed response..
My repo is later (NIC_v1).
Thanks for your attention!


⚠ Jenkins Plugins Artifactory has degraded performance

In 01bca2a, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1280 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 1addb1d after 59 minutes.


Application Header components not aligned correctly

Bug Report
Description
The application header contains a hamburger button (visible when the window is smaller) and the title.

In Edge and other newer browsers, the title shows properly, left-aligned.
In IE11, the title shows right-aligned.

Steps to Reproduce

Go to the project staging URL in a new browser (Chrome, Edge, etc.)

This is an internal Cerner URL; not sure I can provide it here; could you please contact me directly?

The title is left-aligned in the header as it's supposed to.
Go to the same URL in IE 11. The title is right-aligned.

Additional Context / Screenshots

Expected Behavior
This is how the header looks in newer browsers.

Possible Solution
I see in the debugger that the ApplicationHeaderLayout component uses a flexbox layout and specifies justify-content: space-between. When I change it in the debugger to flex-start, the title is aligned properly.
Environment

Component Name and Version<EMAIL_ADDRESS>Browser Name and Version: IE 11
Node/npm Version: [e.g. Node 8/npm 5] Node 10.14.2 / NPM 6.4.1 (or many other versions)
Webpack Version: 3.12.0
Windows 10 (desktop)

This is an internal Cerner URL; not sure I can provide it here; could you please contact me directly?

@alex-bronze I am trying to reproduce the issue in-house and I'd like to see the behaviour on your side. Could you please send the URL to<EMAIL_ADDRESS>Also, how are you setting the title while creating the ApplicationHeaderLayout component?

Investigation Notes:
I used the sample ApplicationLayout component to reproduce the issue without Extensions, Utilities and Navigation on IE 11 on Windows 10. I could not reproduce the issue (screen recording attached) and I need more information from @alex-bronze regarding how the component is laid out on consumers' side.
Environment

Component Name and Version: terra-application-header-layout (2.17.0 and 3.2.0<EMAIL_ADDRESS>Browser Name and Version: IE 11
Node/npm Version: Nodejs v8.15.1/ npm v6.4.1
Windows 10 (Desktop).

@alex-bronze Thank you for the offline update. I am now able to reproduce the issue with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>I shall look into it further.

Update - this issue has started to occur after the introduction of 'Skip to content' button as a sibling to the Logo in<EMAIL_ADDRESS>The example below illustrates the issue that happens in IE 11, I am working with @neilpfeiffer to find out the root cause of the problem.
https://www.w3schools.com/code/tryit.asp?filename=G205DQR6M3SB

Upon further review -- it appears that justify-content: space-between; is not at all needed for the fill class, or elements that is has been applied to.
So unless it was needed for a specific reason and by removing it solves for the layout bug with IE11 -- suggestion is to remove line 9: /src/ApplicationHeaderLayout.module.scss#L9.

That is correct. Like you mentioned offline,

the justify-content property is meant to position the child elements (that are the logo and the skip to content elements in this particular case), but none of the child elements of the header-layout do we even want positioned that way (they all have their own internal positioning or sizing as needed now).

I was able to confirm that this does fix the original issue without introducing any negative effect. I haven't written an explicit WDIO spec to test this in IE11 but I have the screenshots below.
Without Fix:

With Fix:

Application Header components not aligned correctly issue still persists after the new release(version- 4.8.0), I logged another issue https://github.com/cerner/terra-framework/issues/593


feat(applauncher): add support for sections/icons/divider

fixes https://github.com/patternfly/patternfly-next/issues/1914
@kybaker I just put images and SVGs of various shapes I found online in the example to show how they will look. There is a 24x24 area to the left of the app launcher link text where the icon will go and the log edge of the icon will stretch to fill the 24px length, and the shorter edge will scale down. And if the logo is less than 24x24, it will just be smaller. All the images will be vertically and horizontally centered.
@jgiardino I changed the title
s to
s, inline with what we're doing in the dropdown component, since you can establish a new heading hierarchy in
 elements. And added the scree-reader text.

Deploy preview for pf-next ready!
Built with commit 8996e86bfdb3fc07a00a355797ac887570964e3d
https://deploy-preview-1916--pf-next.netlify.com

👍 This looks great!
I really like how you combined the icon with the screen reader text, since they are synonymous. Looking at this html example below, this seems like a pattern that should be reusable in other places. A similar case came up with my product team today where they want to include a link to the product documentation in a dropdown menu in the masthead. Would it be possible to make this chunk of the menu item a reusable component? Or is that just something we should capture as part of https://github.com/patternfly/patternfly-next/issues/1429?

  (opens new window)

One change that I recommend is to not set opacity on .pf-c-app-launcher__menu-item-external-icon and instead set it on just the icon, to avoid any potential issues with opacity affecting screen reader perception of that text.

@jgiardino thanks, updated so that we don't have a wrapper for the external link icon, it seems unnecessary. Also updated the documentation. Should aria-hidden="true" be applied to the icon on the left of the list item, too?

@jgiardino

Would it be possible to make this chunk of the menu item a reusable component?

What would be the benefit of it being a component? I'm also curious how we would position it as a component - what might it be named? I also changed the structure with an update (removed the wrapper and now just have the icon + screen-reader text) and, assuming that works, curious if that impacts this potentially becoming a component?

What would be the benefit of it being a component?

I think this just gets back to the need to have menu items and toggles as separate components so that we can build these things just once (e.g. this would be a variation of the MenuItem component). Should I just add this as something to #1429 for now?
This is definitely something that could be useful in the Dropdown menu, only because this exact use case came up in a product planning meeting yesterday. :-)

I also changed the structure with an update (removed the wrapper and now just have the icon + screen-reader text) and, assuming that works, curious if that impacts this potentially becoming a component?

I think this works. I think if it's just a variation of a future menu item component, this would be fine.

Should I just add this as something to #1429 for now?

@jgiardino that sounds good to me, thanks!

I have a question for design (@mcarrano, @kybaker)...
Is the use case for this component that it will always have links?
A question came up off thread about whether the app launcher should always be wrapped in a  element. My thinking is that if the consumer needs a similar interaction pattern that provides a menu of action buttons instead of navigational links, then that's what the Dropdown should be used for. Does that match your expectation?
Also, in other components where we use the  element, we try to be prescriptive in how we define the labels for those regions. This is really important when screen reader users are navigating by region and there are multiple navigation regions on the page. Some of these labels we decided on are "Global" for primary nav, "Local" for tertiary nav, and "Breadcrumb" for breadcrumbs (e.g. VO announces this region as "Breadcrumb navigation").
If the app launcher is wrapped in a navigation region, what would that label be? Would "Application" match our use case for this component?
@mcoker If we do decide that all app launchers should use  and that all aria-labels should be more specific to our use case for this component, should that be captured in a separate issue (since that would require updating all examples and not just this new one)?

@mcoker If we do decide that all app launchers should use  and that all aria-labels should be more specific to our use case for this component, should that be captured in a separate issue (since that would require updating all examples and not just this new one)?

@jgiardino I'm fine with making that update in this PR if you would be OK with verifying that changeset.

My thinking is that if the consumer needs a similar interaction pattern that provides a menu of action buttons instead of navigational links, then that's what the Dropdown should be used for. Does that match your expectation?

Yes, this matches my expectations @jgiardino . Regarding the naming, I think "Application" could be ambiguous. Maybe "Application lancher" or just "launcher?"

Regarding the naming, I think "Application" could be ambiguous. Maybe "Application lancher" or just "launcher?"

I was also wondering the same thing, and thinking that "Application launcher" might be better.
"Launcher" alone seems ambiguous to me, too.
And something to keep in mind is that this label gets combined with "navigation", so for the user it would get announced as "Application launcher navigation".

@jgiardino updated the examples and documentation.

@mattnolting thanks, copied and pasted that code from the dropdown component, so committed your suggestions and updated the dropdown component if you want to take another look.

:tada: This PR is included in version 2.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Issue 70 enum constant special case

looks like EnumPattern also has the same limitation (but not normal TypeScript enum, that has other disadvantages)


定时增加选择框

Clear and concise description of the problem
对于小白选手，可以通过可视化直接操作，类似下面这种

Suggested solution
简单修改一下
Alternative
No response
Additional context
No response
Validations

[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

这个确实有用。。。。


Unable to compile sample with ESP8622 board, will compile as Arduino Uno

I can load and compile the Sample example using a Arduino Uno board.  When I change the board to Node MCU 1.0 (ESP-12E Module) I receive "Error compiling for board NodeMCU 1.0 (ESP-12E Module).
Error message also includes "StopWatch.cpp:36:14: error: invalid conversion from 'long unsigned int ()()' to 'uint32_t ()() {aka unsigned int (*)()}' [-fpermissive]
_gettime = micros;"

The type of micros() and millis have a different signature. I recently came across a similar problem in other code.
Will work on a solution this week.
Thanks for mentioning it

0.2.2 version released,
verified with ESP32 which gave the same error.

Thank you for the quick response.   Loads perfectly now!

You're welcome,
if you find other bugs in my libraries or missing features just let me know and I'll try to fix asap

Rob, thanks again for your help.
The project I was trying to build is https://github.com/BrianInGermany/ToastmastersTimerWiFi.  I was getting errors and posted an Issue, but BrianInGermany doesn’t seem to be monitoring his project.  I found his documentation slim, and wasn’t even sure if it was your StopWatch.  Now that your part is working ok, I am still getting errors compiling the ToastmastersTimer.ino with similar errors “'class StopWatch' has no member named 'ms'” .
I’m more of a hardware guy, but get lost quick in C+.
Do you have any advice?
Thanks,
Rick
From: Rob Tillaart<EMAIL_ADDRESS>Sent: Tuesday, July 14, 2020 9:30 AM
To: RobTillaart/Stopwatch_RT<EMAIL_ADDRESS>Cc: TrickyRick<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [RobTillaart/Stopwatch_RT] Unable to compile sample with ESP8622 board, will compile as Arduino Uno (#3)
You're welcome,
if you find other bugs in my libraries or missing features just let me know and I'll try to fix asap
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/RobTillaart/Stopwatch_RT/issues/3#issuecomment-658179789 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABND2HNJXLQM3KVPU4VFPULR3RMUVANCNFSM4OZBE5LA .  https://github.com/notifications/beacon/ABND2HPEVXGFIKKNSMHNBH3R3RMUVA5CNFSM4OZBE5LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE45QNTI.gif

I will check that code if I understand the problem and if it id fixable (time boxed)

Quick code scan
The project is based upon an older version of the stopwatch library.
You must rtry to eplace the calls to .ms() with calls to .elapsed(). That function is renamed after the stopwatch also supported micros and seconds as tome units.
No computer nearby to test myself.

Thanks again.  It worked!
Rick
From: Rob Tillaart<EMAIL_ADDRESS>Sent: Wednesday, July 15, 2020 12:07 AM
To: RobTillaart/Stopwatch_RT<EMAIL_ADDRESS>Cc: TrickyRick<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [RobTillaart/Stopwatch_RT] Unable to compile sample with ESP8622 board, will compile as Arduino Uno (#3)
Quick code scan
The project is based upon an older version of the stopwatch library.
You must rtry to eplace the calls to .ms() with calls to .elapsed(). That function is renamed after the stopwatch also supported micros and seconds as tome units.
No computer nearby to test myself.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/RobTillaart/Stopwatch_RT/issues/3#issuecomment-658533373 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABND2HK5TA75GP2UHW3LW3TR3UTN5ANCNFSM4OZBE5LA .


Document how to update Baker and Cookbook

Design, DnG, Product and Engineering can contribute to either repo.
When and update is made, share it and any accompanying documentation in the #cookbook channel.

We will meet monthly as a group that includes @tatusian, @HSender-lat, @golfecholima, @joyjade, @irisslee, @seangreene, @vnessamartinez, with @jperezlatimes and @james-tyner joining when possible. We'll revisit our Baker roadmap and discuss any major developments or questions.
When and update to either repo is made, please share it and any accompanying documentation in the #cookbook channel.


Please specify a swift version

Analyzing dependencies
Downloading dependencies
Installing Google-Material-Design-Icons-Swift (1.0.1)
[!] Unable to determine Swift version for the following pods:

- `Google-Material-Design-Icons-Swift-library` does not specify a Swift version and none of the targets (`Pods`) integrating it have the `SWIFT_VERSION` attribute set. Please contact the author or set the `SWIFT_VERSION` attribute in at least one of the targets that integrate this pod.

Workaround for all who don't want to wait, add this:
pod 'Google-Material-Design-Icons-Swift', :git => "https://github.com/Ahmadre/Google-Material-Design-Icons-Swift.git"


Favicon img element must have an alt attribute

Fix issue #188 and also adds "title" attibute.

LGTM

Nice, thank you!


Use cloned options...

Quite often when dealing with forms there are a number of defaults I need to use across inputs for a given form (note this is often specific to a form rather than global)
A simple example is (In HAML)...
- defaults = { :input_html => { :class => 'test' } }
= form.input :phone, details
= form.input :email, details

Because the 'defaults' is passed by reference and if modified internally by simple_form, the details variable for the email field will have all of the extra settings specific for the phone field added (e.d. HTML phone class, etc).
What really needs to happen here is to possibly change SimpleForm::Inputs::Base so that the options hash is deep cloned before it is assigned to @options. My guess is that:
@options = Marshal::load Marshal.dump(options)
would work here (I do admit this feels a little hacky). I shouldn't think the copying here would add any significant performance issues in terms of speed/mem usage.

Yes, this is indeed an issue, but -1 for Marshal.load/dump. This is going to be a huge penalty for the majority of forms that aren't in fact sharing options.

Cool, glad you agree :)
Marshal only came to mind as it was the easiest way to to a deep copy (given this is needed for things like options[:input_html][:class] without going through and individually changing various bits of code where hash modifications were made to they used a clone.

Yes, this does in fact seem a much better idea :)

Now we need to implement the same behavior to another helpers like label, association, hint and error

@josevalim, @carlosantoniodasilva, @rafaelfranca
I solved this issue but my fix is not available in Rails 3.0. Which versions should we support?

For me we can support only Rails versions greater than 3.1 for the SimpleForm 2.0 version.
Did you see any problem with this?

It all depends on the effort. If this is just for the deep_dup method, I would simply copy the implementation from Rails to Simple Form and add a TODO to change it in the future.

:+1: to copy

okay, i'm gonna copy that =(

@josevalim @rafaelfranca acceptable?

:shipit: :+1:

forgot to copy the tests for deep_dup, doing that...

A bit late here but... I'm ok about copying the method to keep support for Rails 3.0, sounds good to me.


Hyperlinks in syntax diagrams?

I develop documentation in DITA for IBM-brand products. This issue touches on, but is not entirely specific to, IBM-brand information development. I do not have direct access to internal IBM information development forums, so I am taking advantage of this public forum to raise this issue.
The IBM-specific aspect of this issue is mostly historical: back in IBMIDDoc, I could use the linkend attribute of the var element to hyperlink variable names in syntax diagrams to their descriptions in another topic. This saved me from having to duplicate the descriptions of these variables in dozens of topics. (What's that? I should have used conref to reuse the descriptions, and reproduced them in all of those topics? We can have that discussion, if you like.)
However, the IBMIDDoc-to-DITA conversion process simply dropped all of these hyperlinks. Yes, that was years ago, but I still miss those links.
The DITA var element has no equivalent to the IBMIDDoc linkend attribute.
Something I tried back in 2009 and haven't revisited since: I was hoping that something like the following—that is, using the data element as an "intermediate" wrapper for an href attribute—would work:
<var><data href="#topic/section" scope="local">value1</data></var>

Nope. No hyperlink.
Would you consider adding support—however you decide to implement it—for hyperlinks in these SVG syntax diagrams?
Here's an example that I created several years ago of hyperlinks in syntax diagrams (although, not in DITA): Complete syntax of Lua.

There will not be any support for that <data> style link -- the <data> element is intended to be for metadata and to not render by default, so (as with all other instances of <data> within normal markup) the usage above should result in nothing to render as the content of the <var> element. If it's rendering the value1 text today, that is a bug -- the data content should not be rendered.
I'm not sure if there are other (better) ways to insert a link into the content or not -- I think most of these elements are very limited as to what they can contain.

Thanks for the reply. Understood. That circa-2009 attempt with <data> was a DITA newbie's desperate attempt to claw back lost functionality. I would welcome support for hyperlinks in syntax diagrams, however it is done.


请问是否计划在mmdetection工具箱上实现CBNet？

PLEASE FOLLOW THESE INSTRUCTIONS BEFORE POSTING

Please thoroughly read README.md, INSTALL.md, GETTING_STARTED.md, and FAQ.md
Please search existing open and closed issues in case your issue has already been reported
Please try to debug the issue in case you can solve it on your own before posting

After following steps 1-3 above and agreeing to provide the detailed information requested below, you may continue with posting your issue
(Delete this line and the text above it.)
Expected results
What did you expect to see?
Actual results
What did you observe instead?
Detailed steps to reproduce
E.g.:
The command that you ran

System information

Operating system: ?
Compiler version: ?
CUDA version: ?
cuDNN version: ?
NVIDIA driver version: ?
GPU models (for all devices if they are not all the same): ?
PYTHONPATH environment variable: ?
python --version output: ?
Anything else that seems relevant: ?

The implement on mmdetection is the similar code and I will release soon

@PKUbahuangliuhe  have you finished the mmdetection version of CBNet?


Future OpenXR Support (Question)

The Khronos group is currently working on the development of OpenXR, a cross platform VR API.  Once released, will this be included into the LWJGL libraries?
OpenXR

Yes, that's the plan. We'll then deprecate and eventually remove the existing LibOVR & OpenVR bindings.

What's the point in removing existing bindings when they are not officially deprecated on their own? Even when OpenXR came, someone might want to use OpenVR or LibOVR directly. Since LWJGL 3 is modular, I don't think keeping them available will not raise any problems.

In my opinion, the bindings should be kept for several releases as deprecated, then eventually they should be removed from further releases.  Thanks @Spasi for your response!

There's no problem with keeping the current bindings, except maintenance overhead. I'm just being hopeful, given the companies involved in OpenXR, that the existing VR libraries will become obsolete. In any case, if deprecation/removal happens, there will be enough time for users to migrate their code.

The first version of OpenXR has been released. So... how far are you with the bindings for it? Are you working on this? Or do other things have more priority? I do not want to sound impatient (sorry if I do), I'm just curious about this.


128*128

hi can I use this model on size 128*128 image

Hi,
I haven't tried using the model with this resolution.
By you can try to download such a model from here


Update shortcuts.adoc to show the parenthesis of the uni.eventually shortcut

The generated documentation for uni.eventually was missing the parenthesis.
Now it is correctly showing
uni.eventually(() → System.out.println("eventually"))
instead of
uni.eventually) → System.out.println("eventually"
and
uni.onItemOrFailure().invoke((ignoredItem, ignoredException) → System.out.println("eventually"))
instead of
uni.onItemOrFailure().invokeignoredItem, ignoredException) → System.out.println("eventually"
in the documentation.

Thanks!

Thanks!


[Feature]: Workflow for closing old issues

Description
This feature aims to automate the process of managing old issues, ensuring that the repository remains organized and focused on relevant tasks. By automatically closing old issues, it reduces manual overhead for repository maintainers and helps keep the issue tracker tidy and up-to-date.
Suggested Solution
I would like a workflow that automatically identifies and closes old issues based on certain criteria, such as no recent activity or being open for a specific duration.
Alternatives
No response
Additional Context
No response

@Bhanu-code please assign me this issue under gssoc'24

@Bhanu-code please assign me this issue under gssoc'24


Fix typos

Description
Found few misspellings. None in code.
https://github.com/crate-ci/typos
Type of change

[x] Documentation change (pure documentation change)

Thanks for the PR @szepeviktor! Any interest in creating a separate PR which runs typos as part of github actions on PRs?

creating a separate PR which runs typos as part of github actions on PRs?

Done 🍏


feat: view table schema

This implement #14 view table schema..ux needs some love..

@wliao008 Thanx for your interest :heart:
and yes need some designs also for make the front-end


fix: top level comment not replacing existing ones

Fixes the issue where top level comments are not replaced after an update to the function.
Description of changes
This fixes the issue where the regex for the function top level comments are not working, resulting in duplicates of the Amplify params that is generated after an update to a function (especially resources).

Issue #, if available
NA
Description of how you validated changes
Updated a function in my local environment and the top level comments are correctly replaced.
Checklist

[X] PR description included
[X] yarn test passes
[X] Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @juniarz, thanks for your contribution!
It looks like a unit test in packages/amplify-category-function/src/__tests__/provider-utils/awscloudformation/service-walkthroughs/execPermissionsWalkthrough.test.ts is failing because the snapshot is out of date. You can run yarn jest --updateSnapshot <path to test> to update it automatically.
Additionally, are you able to add a test case to ensure the comment is updated correctly?

Hi @juniarz, thanks for your contribution!
It looks like a unit test in packages/amplify-category-function/src/__tests__/provider-utils/awscloudformation/service-walkthroughs/execPermissionsWalkthrough.test.ts is failing because the snapshot is out of date. You can run yarn jest --updateSnapshot <path to test> to update it automatically.
Additionally, are you able to add a test case to ensure the comment is updated correctly?

Hey, I resolved the issue, please check it out!


with-jest example doesnt work

when i run test from npm scripts i have error
  C:\with-jest-app\jest.setup.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { configure } from 'enzyme';
                                                                                ^

    SyntaxError: Unexpected token {

      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:316:17)

Tech
Version

next
5.1.0

node
10.0.0

Same with me. But I can fixed that by doing these steps:

Install babel-plugin-transform-es2015-modules-commonjs

npm install --save-dev babel-plugin-transform-es2015-modules-commonjs

Added it to your .babelrc file

{
  "env":{
    "development": {},
    "production": {},
    "test": {
      "plugins": [
        ["transform-es2015-modules-commonjs"]
      ],
      "presets": [["next/babel", { "preset-env": { "modules": "commonjs" } }]]
    }
  }
}

Don't forget to adjust with your own .babelrc config, then run it again.

@ikandars
I replaced es6 imports to es5. And it all worked.
const enzyme = require('enzyme')
const Adapter = require('enzyme-adapter-react-16')

enzyme.configure({ adapter: new Adapter() })

Well, I think it is still borken. babel-preset-env is missing. Complains with this infamous error:
"Couldn't find preset "env" relative to directory ..."

https://github.com/zeit/next.js#customizing-babel-config read this.

thanks but when it already works fine with next build, can't you make it work when using the yarn test command as well?

and now seeing this error
    Plugin 0 specified in "/Users/mick/code/urban-signs/node_modules/next/babel.js" provided an invalid property of "default" (While processing preset: "/Users/mick/code/urban-signs/node_modules/next/babel.js")

      at Plugin.init (node_modules/babel-core/lib/transformation/plugin.js:131:13)
      at Function.normalisePlugin (node_modules/babel-core/lib/transformation/file/options/option-manager.js:152:12)
      at node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
          at Array.map (<anonymous>)
      at Function.normalisePlugins (node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
      at OptionManager.mergeOptions (node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
      at node_modules/babel-core/lib/transformation/file/options/option-manager.js:265:14
      at node_modules/babel-core/lib/transformation/file/options/option-manager.js:323:22
          at Array.map (<anonymous>)
      at OptionManager.resolvePresets (node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)

@binarykitchen I also got that error and fixed it by adding "babel-core": "7.0.0-bridge.0" to package.json as shown here: https://github.com/zeit/next.js/blob/905da6f92bd36b48c5067f1f1525004777213e17/examples/with-jest/package.json#L5

ugh, can't this be integrated in next/babel? i am pretty sure many others will have the same problem

Well not in next/babel, since next/babel is just a babel preset. but it's already part of the Next.js dependencies 🤔 https://github.com/zeit/next.js/blob/canary/package.json#L68

@timneutkens ah good to know and then is that coming out?

I mean, that was part of 6.0.0 already.

It's also extremely hard to help anyone posting "it doesn't work in my app" or a random babel error without the actual .babelrc / next.config.js.

fair enuff. here's more.
.babelrc
{
  "presets": ["next/babel"],
  "plugins": []
}

test command
NODE_ENV=test && jest
dependencies in package.json
  "dependencies": {
    "compression": "^1.7.2",
    "express": "^4.16.3",
    "helmet": "^3.12.1",
    "material-ui": "^1.0.0-beta.47",
    "next": "^6.0.3",
    "pino": "^4.17.3",
    "react": "^16.4.0",
    "react-dom": "^16.4.0",
    "react-redux": "5.0.7",
    "redux": "4.0.0"
  },
  "devDependencies": {
    "babel-eslint": "^8.2.3",
    "enzyme": "^3.3.0",
    "jest": "^23.0.0",
    "nodemon": "^1.17.5",
    "react-test-renderer": "^16.4.0",
    "redux-devtools-extension": "2.13.2"
  }

test code
import { shallow } from 'enzyme'
import React from 'react'
import renderer from 'react-test-renderer'

import App from '../src/pages/index.js'

describe('With Enzyme', () => {
  it('App shows "Hello world!"', () => {
    const app = shallow(<App />)

    expect(app.find('p').text()).toEqual('Hello World!')
  })
})

the output again
└─❱❱❱ yarn test                                                                                1 ⏎  +8799 17:17 ❰─┘
yarn run v1.7.0
$ NODE_ENV=test && jest
 FAIL  __tests__/index.test.js
  ● Test suite failed to run

    Plugin 0 specified in "/Users/michael-heuberger/code/urban-signs/node_modules/next/babel.js" provided an invalid property of "default" (While processing preset: "/Users/michael-heuberger/code/urban-signs/node_modules/next/babel.js")

      at Plugin.init (node_modules/babel-core/lib/transformation/plugin.js:131:13)
      at Function.normalisePlugin (node_modules/babel-core/lib/transformation/file/options/option-manager.js:152:12)
      at node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
          at Array.map (<anonymous>)
      at Function.normalisePlugins (node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
      at OptionManager.mergeOptions (node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
      at node_modules/babel-core/lib/transformation/file/options/option-manager.js:265:14
      at node_modules/babel-core/lib/transformation/file/options/option-manager.js:323:22
          at Array.map (<anonymous>)
      at OptionManager.resolvePresets (node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.323s
Ran all test suites.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I had the same problem when I wanted to upgrade with-jest, and with-jest-typescript. But with with-next-typescript I was able to solve that by putting
"jest": {
"globals": {
"ts-jest": {
"useBabelrc": true
}
}
}
in package.json instead of jest.config.js
Example here: https://github.com/zeit/next.js/pull/4483/files

@binarykitchen you're not using the example 🤔 https://github.com/zeit/next.js/blob/canary/examples/with-jest/.babelrc
https://github.com/zeit/next.js/blob/canary/examples/with-jest/package.json#L5-L6

Just upgrade the last exemple with-jest in fact :
Jest@latest, babel-jest@latest and enzyme@latest
package.json :
{
  "name": "with-jest",
  "version": "1.0.0",
  "dependencies": {
    "babel-core": "7.0.0-bridge.0",
    "babel-jest": "^23.0.1",
    "next": "6.0.3",
    "react": "16.2.0",
    "react-dom": "16.2.0"
  },
  "devDependencies": {
    "enzyme": "^3.3.0",
    "enzyme-adapter-react-16": "1.1.1",
    "jest": "^23.1.0",
    "react-addons-test-utils": "15.6.2",
    "react-test-renderer": "16.2.0"
  },
  "scripts": {
    "test": "NODE_ENV=test jest",
    "dev": "next",
    "build": "next build",
    "start": "next start"
  }
}

.babelrc :
{
  "env": {
    "development": {
      "presets": ["next/babel"]
    },
    "production": {
      "presets": ["next/babel"]
    },
    "test": {
      "presets": [["next/babel", { "preset-env": { "modules": "commonjs" } }]]
    }
  }
}

Error :
><EMAIL_ADDRESS>test /mnt/c/Users/tommy/Work/git/lab/tests/nextjs/with-jest-app
> NODE_ENV=test jest

 FAIL  __tests__/index.test.js
  ● Test suite failed to run

    Plugin 0 specified in "/mnt/c/Users/tommy/Work/git/lab/tests/nextjs/with-jest-app/node_modules/next/babel.js" provided an invalid
property of "default" (While processing preset: "/mnt/c/Users/tommy/Work/git/lab/tests/nextjs/with-jest-app/node_modules/next/babel.js")

      at Plugin.init (node_modules/jest-config/node_modules/babel-core/lib/transformation/plugin.js:131:13)
          at Array.map (<anonymous>)
          at Array.map (<anonymous>)

397/5000
I do not know much about babel, but would it be because of a babel-jest update? With ts-jest it works.
A change like https://github.com/facebook/jest/commit/5d1babab7a5695026d3e9c31ba6ac1dd8fff2d73#diff-4d50022735c04444c3ed5901ee4b2208
You can read in the changelog "[babel-jest][** BREAKING **] Always return object from transformer," next uses babel internally, so maybe ...

@timneutkens nope, using the examples
https://github.com/zeit/next.js/blob/canary/examples/with-jest/.babelrc
https://github.com/zeit/next.js/blob/canary/examples/with-jest/package.json#L5-L6
still doesn't work for me. same error. and doesn't make sense why it's a dependency when babel-jest should be a dev dependency by the way.
yes, when i bump babel-jest then that error is gone but am seeing other new errors. maybe we should update the jest example to their latest packages and fix any wrong configs to make it work? cc @tommypater

wtf...
@binarykitchen try to delete package-lock.json and node_module and "npm i".
I think it comes from bad management of the npm installations.

ah now the tests pass.
but why did you put babel-core and babel-jest as a dependency when they should be under dev dependencies instead @tommypater ?

and why wont the test work with the latest jest version 23?

@binarykitchen i just retake the exemple of next.js quicky (i don't use jest without typescript). 23.1.0 is the lastest version, it was just to be more explicit. It's works now, no ? :)

no, it doesn't work with jest v23 - possible to update the jest example to make it work with latest?

@binarykitchen
jest.setup
/* eslint-disable import/no-extraneous-dependencies */
const enzyme = require('enzyme');
const Adapter = require('enzyme-adapter-react-16');

enzyme.configure({ adapter: new Adapter() });

and babel-jest, jest ^23
it working in my project

Not working for me with "jest": "^23.1.0". Any news on this?
Thanks in advance!

Hello there! I added this following .babelrc
{
  "env": {
    "development": {
      "presets": ["next/babel"]
    },
    "production": {
      "presets": ["next/babel"]
    },
    "test": {
      "presets": ["env", "react"]
    }
  }
}

and installed yarn add --dev babel-jest babel-preset-env babel-preset-react
Worked for me.

I use yarn add --dev babel-jest babel-preset-env babel-preset-react ,and fixed this issues

.babelrc
{   "presets": [     ["next/babel"],     [       "@babel/preset-env",       {         "useBuiltIns": "usage",         "include": ["es6.map", "es6.set", "es6.object.assign"],         "forceAllTransforms": true       }     ]   ],   "plugins": ["@babel/plugin-proposal-class-properties"],   "env": {     "test": {       "presets": ["@babel/env", "@babel/react"],       "plugins": ["styled-jsx/babel-test", "dynamic-import-node"]     }   } }
Using Jest with enzyme. Getting the below error. Please help me.
import React from "react";
^^^^^
SyntaxError: Unexpected identifier

  at ScriptTransformer._transformAndBuildScript

Facing this issue after trying to fix IE11.  Please help me.


post-fetch: Exception while running post-fetch job: Illegal characters in path.

So far I'm only seeing 1 user affected by this, but it affected 3 of their enlistments
time 2018-11-07 03:25:05.3436328
MountIds:
a3ad84a5497f4002a1a9fbe8c45d225f
5b6232a0f62a42278ba6cf0c9eb58aa3
9c5d6b418003410eb1a280124b578df7

Reached out the affected user, and they have formatted their drive.  Will keep this open as a placeholder if more issues like this occur.


Would JXTheme support Swift Package Manager?

Since Xcode 11, we can use SPM more easy for iOS/macOS UI project.

I will support it soon.

It's completed at 0.0.6 version.


Feature request: Support for Deno/ESM

Would be really nice if this lib supported Deno and moved away from CommonJS!
I'm experimenting on porting fido2-lib to a dual mode Node/Deno-lib on my own, and migrating everything to ES6 while at it. But I guess the changes are too big to "pull back" into this lib (?).
What need to be done/What I'm experimenting on:

Reduce usage on Node-specific stuff; Replace Buffer with ArrayBuffer, replace crypto with webcrypto/subtle where possible
Favor zero subdependency dependencies when available, bundle and modify them if dependencies depend on eachother
Favor dependencies that already support import/export module pattern.
Favor dependencies that support Deno and/or browser usage.
Pay attention to using one, and only one, implementation of each function. Also make sure that dependencies use the same implementations (base64 is a good example, i found at least 6 different implementations in fido2-lib plus it's dependencies)

Check out https://github.com/Hexagon/webauthn for ideas and inspiration, and please drop an issue of you find anything that doesn't look ok :)

Update 2022-04-25
Status of @hexagon/webauthn  - Dual platform - Deno first - Node built
https://github.com/Hexagon/webauthn is pretty much in sync with fido2-lib now.

All features are implemented
All Node tests implemented
Deno first approach, where dependencies are imported by Deno, and a platform independent bundle with zero dependencies is built (dist/webauthn.js). The bundle work in both Deno and Node, and it should technically work in browser too.
Code style (lint) upgraded to current recommended standards
Etc ...

Status of hexagon/fido2-lib fork , Dual platform - Node and Deno codebase
I've also submitted a pull request with a Node-first/Dual platform version of fido2-lib at PR https://github.com/webauthn-open-source/fido2-lib/pull/80
Two alternatives, both support both Deno and Node :)

Additional support is great, less support is bad. According to your fork, your version

Lacks all Attestation-modes except "none"
Lacks MDS
All automated tests of fido2-lib isn't implemented

I hope you understand that this wouldn't feel like an upgrade for most users. Can you clarify what the benefit of deno is, in this case? We can aim to focus on its core value.

I intend to implement all attestation modes and MDS in the long run. The pro/con list is just a glimpse at the current state. I'll add a clarification on that. I'll also make it a little clearer that @hexagon/webauth is more of a proof of concept than something production ready 👍
Deno is hopefully the future. It is essentially Node.js with typescript, linting, bundling and nvm built in in a single executable. It is fully possible to build packages that support both environments with a some effort and clever solutions. And since the codebase is pretty much the same for node and deno-libs, it is preferable to have one library that support them both.
The pros of being an ES-module is that CommonJS is slowly fading away, and isn't supported ootb by browsers or Deno. ES modules make tree-shaking possible when bundling libraries and applications.
My efforts are just a (working) proof of concept, in a perfect world you would implement changes similar to mine in fido2-lib.

That sounds like an interesting direction, but a lot of work and nights away. Maybe you can continue working on your fork and once you have the compatibility and tests implemented we can consider whats the best way to bring it together? 👍

Would be useful to be full ESM. I had to fork it...

Current state in PR #80

Update 2022-04-25
Status of @hexagon/webauthn  - Dual platform - Deno first - Node built
https://github.com/Hexagon/webauthn is pretty much in sync with fido2-lib now.

All features are implemented
All Node tests implemented
Deno first approach, where dependencies are imported by Deno, and a platform independent bundle with zero dependencies is built (dist/webauthn.js). The bundle work in both Deno and Node, and it should technically work in browser too.
Code style (lint) upgraded to current recommended standards
Etc ...

Status of hexagon/fido2-lib fork , Dual platform - Node (and Deno) first
I've also submitted a pull request with a Node-first/Dual platform version of fido2-lib at PR https://github.com/webauthn-open-source/fido2-lib/pull/80
Two alternatives, both support both Deno and Node

Thanks - so everything works as before, just with added Deno support?
Or is it a major change with new syntax etc?
If you say its ready I will start my review 👍

New PR opened, #83, with the same result as #80, but much less changes to the code base and file structure. This time i also left Deno outside to keep the PR as small and reviewable as possible.


Rethink latest-tag-button

The new React-based views mentioned in https://github.com/refined-github/refined-github/issues/6152, no longer have enough space to show  latest-tag-button

Essentially the old view is only show on isRepoRoot

What do we do with this feature? It was initially added to:

inform the user that they're looking at a version of the readme that doesn't match the latest version
see what commits haven't yet been released

Questions:

does it really be long in that area of the screen?
do we really need to show it in every folder and every file?
is there a better way to communicate this information?

The feature also lets you:

see the current view on the latest tag
compare the latest tag to the latest version on main (which is a bit awkward on non-main branches)

I wonder if we can reduce it to:

"see latest published version" link
"see unreleased commits" link
count unreleased commits

This would let us split and reposition the feature. We don't need to show the latest version on every page.

Here's my suggestion, I think it's a more direct solution to the original issue. The only missing part is that it requires 2 more clicks (without pageloads) to open "the same view, but in the latest tag." That's something I think is relatively rarely needed 🤔
unreleased-commits

Shows: Whether there are unreleased commits
Shows: How many commits are unreleased (if possible)
Action: List unreleased commits (compare view)

Resolves:

space issues: it's less than 60px wide
sizing: we can finally drop btn-sm
confusing state: it no longer confusingly shows the current tag in every single page

Missing:

The exact tag: it can appear in the tooltip

A link to the "tree" view of the tag: still available in +2 clicks in the dropdown

Something to note: unreleased-commits would only appear on the default branch; not on tags, not on commits, not on other branches. The feature would exclusively say:
Hey you're looking at a newer version than what's published

This would also leave space for:

https://github.com/refined-github/refined-github/issues/6499

Maybe we should just merge it with the branch/tag picker:
On default branch
TODO
On non-default branch
Do nothing

On latest tag
Homepage

File browser
TODO
On non-latest tag
Homepage

File browser

How to go to latest tag

I think we need to de-emphasize the importance/frequency of this action and the necessity to know the latest tag on every single page.
I think unreleased-commits would bring the benefits we had initially wanted without filling the UI with unnecessary information.
This is why I suggest dropping latest-tag-button and adding a new, focused feature.

How to go to latest tag

Open picker
Select tag tab
Click the first item

This is good enough for me, requires no features/changes from us.

I think we need to de-emphasize the importance/frequency of this action and the necessity to know the latest tag on every single page.

My proposal is about not losing any current info, of course cutting down them is welcome


Does marquee3k support dynamic content

I am having this case where user can add dynamic <li> content to a div and then the div must adapt to display a continuous marquee with no gap (if 1 <li> then there will be every same <li> on that div and so on)?

Hello @TuanDSE62171, I think what you're trying to achieve is best served by

destroying the marquee
re-initialising the marquee

Since the marquee clones content to fit the parent's width. the current refresh method does not serve this purpose since you just don't want dynamic content randomly appended after a series of cloned elements.
I still haven't had the time to look into cleaning up and introducing a destroy method but it's in the pipeline. If you are using GSAP you might be interested in looking at a WIP version:  https://github.com/ezekielaquino/Marquee3G

I found that if you initiate the script after content is loaded (via ajax), with a 200 millisecond timeout it works.
 setTimeout(function () {
      Marquee3k.init();
 },200);


Error reading CITATION.cff file that validates with jsonschema

I have a CITATION.cff file here: https://github.com/shop-planner/shop3/tree/add-citation that I am able to validate against the cff JSON schema using the python jsonschema script.
However, when I install it on my GitHub repo it does not work: it fails to display the citation tabs (APA and BibTeX) and if I click on the "view the citation file" button, nothing happens.
I wonder if this is related -- when I try to load the file according to the instructions here:
cff = CFF::File.read('CITATION.cff')

I get this error:
       14: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/file.rb:44:in `read'
       13: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/file.rb:44:in `new'
       12: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/file.rb:34:in `initialize'
       11: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/file.rb:34:in `new'
       10: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/model.rb:39:in `initialize'
        9: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/model.rb:89:in `build_model'
        8: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/model.rb:89:in `map!'
        7: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/model.rb:90:in `block in build_model'
        6: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/model.rb:90:in `new'
        5: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/reference.rb:70:in `initialize'
        4: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/reference.rb:223:in `build_model'
        3: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/reference.rb:223:in `each'
        2: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/reference.rb:224:in `block in build_model'
        1: from /Users/rpg/.gem/ruby/2.6.0/gems/cff-0.4.0/lib/cff/util.rb:29:in `build_actor_collection!'
NoMethodError (undefined method `map!' for nil:NilClass)

I'm not a ruby programmer, so this doesn't mean anything to me, but surely this file should load if it satisfies the CFF schema?
I validated with the CFF schema by:

translating CFF to JSON with yq . CITATION.cff > CITATION.json
translating the CFF schema to json similarly: yq . citation-schema.yaml > citation-scheme.json
jsonschema -i CITATION.json citation-schema.json

FILES:
Archive.zip

Hi @rpgoldman, thanks for the report.
This has been fixed on HEAD - it was a similar issue to #56 that got cleaned up at the same time. This update will percolate through to GitHub soon!

Sorry - I should have said that I have confirmed locally that I can load and validate your CITATION.cff file with the current HEAD.

Thank you @hainesr !


[YAML] Add clean code guidelines README

Why: helps us all proceed at max velocity.
I've already written it for slack. Now, make it a bit more permanent:)

Done in commit https://github.com/oceanprotocol/pdr-backend/commit/422b12efd119b23be5cc05a4e550cf10b427e9ac


added down key to types for SmoothedKeyControlConfig

I noticed the types for SmoothedKeyControlConfig were missing the "down" key definition.
Fixes #5102

👍


Let users edit Star Wars logo

I'd like not to use "Star Wars" text but to write something else with the same font.
Is it possible to change the software to add this feature? :)

Looking at the source code, the "Star Wars" text is an SVG image.
There is, however, a very similar looking font that could be used for this purpose.
Theoretically, it shouldn't take more than adding an entry field, adding JS logic to place the text in the right place and scale the input to fit its container.
In practise, I assume, fiddling around with various texts/length would be required to get everything looking proper.
And of course someone would need to find/make the time to actually implement this :grinning:

@potherca I've used the Starjedi font in the title of the page.
Both of these fonts are filled, to have the same effect as the logo it should be outlined with a yellow border and a transparent fill.
I'll check if this is possible. :wink:

@Airon90 @potherca Done!

:+1: Awesome!


Getting Started

A starting guide to help people find helpful research and how to start building an agent.

I added a getting started guide markdown page. It is a lazy start having only links to research papers @cinjon posted in discord.

nice addition. quick edit: the first name is off. i think it should be PPO. can you change that please? i'll add more color to this after we rebase it.

Cool. Done!


[RFC] Contribution Guidelines

I think it might be good to write up some short contribution guidelines for the future when people (hopefully) will be contributing some articles. Things that might be worth discussing and writing some guidelines for:

Language/Spelling/Grammar:
How strict should we be? Should we (the maintainers) proof-read every submission and note every single error or should we just say "Fix the grammatical errors please" and let them figure out themself?
Code style:
I guess we will just have them format it using nimpretty (with longer lines than the default?). Or we add it as part of the deployment automatically / as a commit hook.
New Topics:
How strict should we be about introducing new topics (out of the ordinary) that may be rather niched as to not pollute the top-level of the TOC?

Any thoughts on this?

For code style I think https://status-im.github.io/nim-style-guide/ is still the best and clear style out there. I'm also okay with just following NEP-1 and nimpretty formatting(lineLen = 120 too).
Concerning "Language/Spelling/Grammar", spelling should be correct and strict. But grammar and language can be more fluid and can be discussed on a proof-reading pass. I'd like to see discussions "I'd like to see this written in Y form" or "This sentence comes over a certain X way". Things like https://github.com/errata-ai/vale can help with this.
And lastly "New Topics", as long as they exemplify the "getting-started" scope and goals, I'd say it's all good. If it's very elaborate or too short, it should be discussed if it's better off in it's own Nimibook or maybe posted on the Nim blog.

For code style I think status-im.github.io/nim-style-guide is still the best and clear style out there. I'm also okay with just following NEP-1 and nimpretty formatting(lineLen = 120 too).

Yes that style guide is really good. If it only had a nimpretty alternative to enforce it. That's the main reason for picking nimpretty in my eyes as we don't have to bother with checking the style of the code.

Concerning "Language/Spelling/Grammar", spelling should be correct and strict. But grammar and language can be more fluid and can be discussed on a proof-reading pass. I'd like to see discussions "I'd like to see this written in Y form" or "This sentence comes over a certain X way". Things like errata-ai/vale can help with this.

Had never heard of vale before but it seems very interesting. I'm with you on the strict spelling but more free grammar and language. The only time we should remark it is if it's making it harder to understand the text. So idk if something like vale would be of much use for us?

And lastly "New Topics", as long as they exemplify the "getting-started" scope and goals, I'd say it's all good. If it's very elaborate or too short, it should be discussed if it's better off in it's own Nimibook or maybe posted on the Nim blog.

I was more thinking about putting niche topics in a misc section or something like that if the don't fit anywhere else. :) Elaborate things can get their own subtopics imo.

Yes that style guide is really good. If it only had a nimpretty alternative to enforce it. That's the main reason for picking nimpretty in my eyes as we don't have to bother with checking the style of the code.

Could maybe use https://github.com/FedericoCeratto/nimfmt for that.

Had never heard of vale before but it seems very interesting. I'm with you on the strict spelling but more free grammar and language. The only time we should remark it is if it's making it harder to understand the text. So idk if something like vale would be of much use for us?

I originally recommended Vale because it's just an helpful tool writing prose, I don't want to enforce anything to the writers haha, but say somebody would want to write something but isn't sure if "their language is correct" then Vale can be a boon, like just pick a style from here https://github.com/errata-ai/styles#available-styles and go wild!
But yes if it gets too difficult then remarks can be made, but this is in a proof-read phase, Vale comes in handy in the writing phase.

I was more thinking about putting niche topics in a misc section or something like that if the don't fit anywhere else. :) Elaborate things can get their own subtopics imo.

Ah yes, fair enough, I like this too :D.

Could maybe use FedericoCeratto/nimfmt for that.

It looks promising but it seems like it's unmaintained and a lot of the boxes in the readme aren't ticked 🤔

I originally recommended Vale because it's just an helpful tool writing prose, I don't want to enforce anything to the writers haha, but say somebody would want to write something but isn't sure if "their language is correct" then Vale can be a boon, like just pick a style from here errata-ai/styles#available-styles and go wild!
But yes if it gets too difficult then remarks can be made, but this is in a proof-read phase, Vale comes in handy in the writing phase.

Oh okay, I misunderstood the purpose of Vale then :) If it can help people write better during the writing phase it's brilliant! It could be a great way to get more people to write, especially the ones who are insecure about their English. Just point them to something like this and they might consider writing after all.

Ah yes, fair enough, I like this too :D.

Nice! :D

@zetashift While reviewing Vindaar's post on curve-fitting I noticed some odd code formatting that wasn't present in the original code. Then it hit me that Nimib let's the compiler handle the code before rendering it so there is already a kind of code formatting that we can't change whatever code-formatter we use.


Sporadic "Connection not ready" exceptions with BlockingConnectionPool since 3.2.0

Version:
3.2.0
Platform:
Python 3.6.7 | packaged by conda-forge | (default, Nov 21 2018, 02:32:25)
[GCC 4.8.2 20140120 (Red Hat 4.8.2-15)] on linux
CentOS Linux release 7.5.1804 (Core) on docker
The redis server is using the official docker image.
Redis server v=4.0.11 sha=00000000:0 malloc=jemalloc-4.0.3 bits=64 build=74253224a862200c
Description:
Since upgrading to 3.2.0, we started getting sporadic errors in getting connections.
image
The code that is running looks like this:
    pool = BlockingConnectionPool(max_connections=config.REDIS_CONNECTIONS_PER_WORKER, host=config.REDIS_HOST,  port=config.REDIS_PORT, db=0, timeout=config.REDIS_TIMEOUT)
   redis = StrictRedis(connection_pool=pool)
   redis.setex(...) / redis.get(...)

Additional information:
This code is running inside an eventlet gunicorn worker.
The server is very "network heavy" and opens lots of sockets (for example, dns queries).
<IP_ADDRESS>:6379> config get maxclients
1) "maxclients"
2) "10000"
<IP_ADDRESS>:6379> info clients
# Clients
connected_clients:104
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0

Do you have a traceback by chance?
How often is this happening?

Also, what version of redis-py did you upgrade from? I assume you weren't seeing errors in that version?

This does not occur in 3.1.0 (we reverted to that and we no longer get these errors).
How often is about 2 exceptions/minute (can be seen in the first image), and we send about 1-2K commands/minute (a graph of "cache misses" only can be seen in the second image). Each bar in the graphs represents 20 minutes.

The attached image in the issue contains a traceback from Sentry.
Here is a text version of a traceback:
[2019-02-18 09:18:57.161794] ERROR: hydrogen.app: An unexpected error has occurred on: <IP_ADDRESS> POST http /enrich/bulk?
Traceback (most recent call last):
  File "/opt/hydrogen/hydrogen/app.py", line 196, in enrich_bulk
    enriched_data = _enrich_bulk(dispatcher, bulk_data, use_mirror, metadata)
  File "/opt/hydrogen/hydrogen/app.py", line 117, in _enrich_bulk
    use_mirror=use_mirror, metadata=metadata)
  File "/opt/hydrogen/hydrogen/core/dispatcher.py", line 99, in enrich
    enrichment_data = enricher.enrich(data_type=data_type, value=value, use_mirror=use_mirror)
  File "/opt/hydrogen/hydrogen/core/enrichers/<>.py", line 55, in enrich
    cached_<> = self.redis.get(<>)
  File "/opt/conda/envs/hydrogen/lib/python3.6/site-packages/redis/client.py", line 1264, in get
    return self.execute_command('GET', name)
  File "/opt/conda/envs/hydrogen/lib/python3.6/site-packages/redis/client.py", line 772, in execute_command
    connection = pool.get_connection(command_name, **options)
  File "/opt/conda/envs/hydrogen/lib/python3.6/site-packages/redis/connection.py", line 1151, in get_connection
    raise ConnectionError('Connection not ready')
redis.exceptions.ConnectionError: Connection not ready

Interesting. Do you happen to know if eventlet is patching the select module? Do you have select.poll available in your environment?
Would it be possible for you to run the following snippet in your environment (with eventlet activated)?
from redis.selector import has_selector
has_selector('poll')

This way we'll know whether redis-py is using select.select or select.poll to determine the healthiness of the socket.

Yes, eventlet does patch the select module.
I followed their monkey_patch code, and it appears that in the bottom line  it is using select rather than poll:

I can replicate this on a different env if you'll say it's necessary (It'll take some time, and I won't touch the production server obviously).

It's in line with what I was skimming in the eventlet docs. So that means that in your environment redis-py is likely using select.select to validate the health of a connection.
select.select has a number of issues, most notably only being able to poll file descriptors with file numbers < ~1024. If you're running over that limit, the current implementation will simply return that the connection isn't ready, which would explain why you're seeing the error. See here: https://github.com/andymccurdy/redis-py/blob/master/redis/selector.py#L47
If you can correlate these errors around traffic spikes, that might further suggest that we're on the right track.
One thing you could try is to reduce the max_connections in the pool. Fewer connections means fewer file descriptors which should reduce the chance of hitting the select.select issue.
We could also make the selector more pluggable such that you could inject your own logic or turn off the health checks for your environment.
You could actually do this now with a (albeit ugly) monkey patch like so:
from redis.selector import SelectSelector

class MySelector(SelectSelector):
    def check_is_ready_for_command(self, timeout):
        return True

from redis import connection
connection.DefaultSelector = MySelector

Or another possible solution is a simple flag to the connection pool to turn of the health checks. Enabling such a flag would cause the pool to behave the same as it did in 3.1.0.

That makes a lot of sense, the server is also using lots of sockets for other tasks (other than connecting to redis) - and has the file descriptor limit (ulimit -n) set to a higher value than the default. So lowering max_connections won't do the trick.
Enabling such a flag would solve this (for now I tested this and the patch does work).
Thanks!

We were investigating a similar issue today in regards to using 3.2.0 and a monkey-patched select with eventlet. In our case, 3.2.0 solved many of the ConnectionError's caused by redis closing inactive connections, however, they didn't disappear completely and would still show on a regular basis.
We traced these latter errors down to a broken/incomplete eventlet select implementation.
As it turns out, in case a socket is both readable/writable state, select will randomly return either writable or readable, but never both at the same time (or exception for that matter).  You can see this in the following code from eventlet:
https://github.com/eventlet/eventlet/blob/a915bb642dd6cd4e92c959addff30509977a637c/eventlet/green/select.py#L51-L61
Each event handler will switch back to the original greenlet without knowing about any other events on the same file descriptor.
As a workaround, with limited testing, but so far no more errors, we found the following change to may do the job:
def check_is_ready_for_command(self, timeout):

    # first check read with no timeout
    r, _, e = select.select([self.sock],[],[self.sock], 0)
    if r or e:
        return False

    r, w, e = select.select([self.sock], [self.sock], [self.sock],
                            timeout)

    return bool(w and not r and not e)

@gogglesguy Thanks for digging into this. This is incredibly helpful.
My current thought is that we should make an EventletSelector implementation based on your patch above. Is there a canonical way to know that eventlet has patched a module in the current interpreter process? If so, we could modify DefaultSelector (https://github.com/andymccurdy/redis-py/blob/master/redis/selector.py#L186) to look for the presence of eventlet and return the EventletSelector.

Perhaps something like this:
https://github.com/ask/kombu/blob/master/kombu/syn.py

Although the workaround worked fine on our servers, the unit test (test_selector) still randomly failed (1 out of 10). I came up with a slight variation that I'm testing now which doesn't fail the unit tests. Will send a pull request.

Related eventlet issue and fix to select: https://github.com/eventlet/eventlet/issues/551
Not sure how actively maintained eventlet is these days..

And as we have been testing the eventlet patch the last couple of days, it is clear to me that we should keep redis-py as is, and fix the issue in eventlet.

why not simply drop the usage of select at all, and simple use socket.settimeout() on the socket? this will do the same thing. the usage of the select module, in blocking code is, is more or less pointles. it is meant for async code, and handling multiple sockets at once...
using socket.settimeout(), will raise an exception after the specified timeout. this archives the same thing as using the select module, but in a cleaner way.
using socket.settimeout will also allow the removal of some clunky code around the socket handling, and you will not need to take care of other async frameworks that monkey patch core libraries.

@schlitzered I was under the impression that there are specific scenarios where a connection can be broken or stalled and reading from the connection blocks until the socket timeout is hit.
If this is true and we only rely on socket.settimeout() to control the blocking interval, we would never hit our global socket_timeout to indicate that the connection is having an issue. You would see this in the pubsub listen loop and possibly other places.
I can't recall a specific scenario that produces this behavior but I seem to remember it coming up at some point years ago. If I'm wrong, then your suggestion may very well work.

i am not aware of such a scenario. if you use socket.settimeout(), it is guaranteed that a socket.timeout exception is raised after the specified timeout.

@NirBenor @gogglesguy @schlitzered
I've put together a patch that uses nonblocking sockets to test the health of connections This completely removes the usage of selectors. If you guys could help test before I merge this patch I'd really appreciate it!
https://github.com/andymccurdy/redis-py/tree/nonblocking

Sure, I'll update here in a few days.

Appears to work fine 👍

Great, thanks for testing @NirBenor. I'll get this merged in a few days.

Is this issue fixed then?

I believe this to be fixed. Please open a new issue if anyone continues to see this behavior.


feat(ProgressBarUpdate): aria update for progress bar component

fixes #1128

Adding new progress bar updates to reflect different use cases
Adjusted handlebar configuration to better reflect dynamic aria values
Replaced documentation instructions

Deploy preview for pf-next ready!
Built with commit 19f4c91f4c0985bba3da207f10b6eb8025c6ad34
https://deploy-preview-1454--pf-next.netlify.com

Thanks for making these updates, @jameslau! They look great!
The only fix I see (besides the typo @dgutride found) is that the example labeled "Progress with Dynamic Description" can be deleted from this page. We're replacing that one with the two new examples you added.
Also, it might be good to get a designer to take a look and make sure these updates match what they were expecting. I had discussed these changes with @rachael-phillips and @mceledonia when I created the issue for this. Could one of you take a quick look?

I have one more request for this PR.

Where aria-valuemax="100" is included in the documentation, I think it would be helpful to clarify when it should be "100" versus some other value. Here's what we have currently:

The maximum value for the progress bar.

Here's an updated description:

The maximum value for the progress bar. If the progress is only defined using aria-valuenow (e.g a percentage), the value should be set to "100". If the progress is defined using aria-valuetext, then this value can be a number other than 100. For example, if aria-valuetext is "2 of 5 units", then aria-valuemax can be "5" and aria-valuenow can be "2".

Where the instructions display for the new examples, I think it would be helpful to revise the text to reflect what's happening in the new examples. Here's what we have currently:

If the description is updated dynamically, then the ARIA tag aria-valuetext should be used to provide this dynamic description.

Here's an updated description:

If the status that displays with the bar is not a percentage, then the ARIA tag aria-valuetext should be used to provide this status to screen reader users. This is the only case when setting the aria-valuemax to a value other than "100" is recommended, given how different screen readers handle these attributes.

Hi @jgiardino, I just pushed up new updates for the progress bar. Please have a look.
@mceledonia and @rachael-phillips, can we get some design feedback on the new changes?

This looks good to me! Thanks again!

👍


Add svd with validation set

this adds an interface for TSVD where the truncation is chosen via a validation set.
bugfix to ASP

this is a very small change, so I'll go ahead and merge once the tests pass unless somebody tells me to block.


k8s audit plug-ins for AKS and GCP

Motivation
As today most projects are multi-cloud, we would need k8saudit plug-in for at least AKS and GCP
Feature
k8s audit plug-ins for AKS and GKE
Alternatives
Today's alternative is creating a messaging stack on each CSP to send logs to the falco Web service

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

/help

cc @ahmedameenaim

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/remove-lifecycle rotten
/reopen

@jasondellaluce: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

A plugin for GKE is in progress https://github.com/falcosecurity/plugins/pull/424

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

@alfredomagallon for GKE I think we should be all set now: https://github.com/falcosecurity/plugins/tree/main/plugins/k8saudit-gke
So I guess the only one remaining among the requested ones is the AKS integration. cc @leogr
/remove-lifecycle rotten

Regarding the AKS plugin, this project was created a while ago by sysdig: https://github.com/sysdiglabs/aks-audit-log .
Since it wasn't too actively maintained and we wanted to be able to make modifications (and not too familiar with C#), we created our own version in Go here : https://github.com/dfo-mpo/aks-audit-log-go . It is still a fairly young project, but we are actively using it at the moment.
Not sure if our Go code fits the needs here, but if it does it could serve as a starting point or we could potentially consider giving out the codebase to the falcosecurity project (I would have to discuss this option internally first).

@jemag, have you considered transforming it into a plugin? :thinking:
it would be the best option IMO, and in case you consider contributing it to falcosecurity org, we can help maintain it.

To be honest, we never thought of it. Initially there was only the sysdig code available and doing a rewrite in Go with the same approach was the fastest route for us.
I think it seems like the most reasonable route to go for in the future. The problem is we are already pretty overloaded on our side and don't really have the bandwidth to allocate to transforming it, especially since it already works for us (we are a very small team). I doubt we would be able to work on this until at least a couple of months.
If anyone wants to use it as inspiration for creating a plugin in the meantime, feel free to do so. Otherwise, individuals waiting for the plugin can also use it as is in the meantime (we'll likely publish official container images in the very near future).
If things change on our side and we have some time to allocate to a transformation, I'll provide an update in the issue.

Thank you @jemag
I believe transforming it into a plugin would not require too much for a developer already familiar with our plugin ecosystem. I totally understand your point about the bandwidth, and it's totally fair :+1: Likely, @Issif can help (as he commented here) without any significant effort from your side.
Let's see what we can do :)

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale
We only miss k8saudit for AKS. Although we don't have any estimation for that yet, I wanted to let you know that @alacuku , @Issif, and I are trying to make this happen. So stay tuned. Ofc, any help is welcome.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale


♻ Refactor computing FastAPI People, include 3 months, 6 months, 1 year, based on comment date, not discussion date

♻ Refactor computing FastAPI People, include 3 months, 6 months, 1 year, based on comment date, not discussion date
Reduce the minimum number of comments to qualify and fix the max number of experts per section.

📝 Docs preview for commit 613f8dec340fce910e2af4336b243661fb84a29f at: https://158b0586.fastapitiangolo.pages.dev

📝 Docs preview for commit dde607f3c389d64e9fe0d3df47d92e420b27f7c1 at: https://767df425.fastapitiangolo.pages.dev


LOST ALL MY CODE

Type: Bug
I've lost a long code (hours of work), because of the workspace BUT the was file saved from a long time ago. I don't know why i've lost all modifications after 31/03/2024 PLEASE HELP ME !!
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz (4 x 2592)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.79GB (0.65GB free)

Process Argv
--crash-reporter-id ee4e8043-0e3b-4cd7-99e5-96d767dfb310

Screen Reader
no

VM
0%

Extensions (27)

Extension
Author (truncated)
Version

arepl
alm
2.0.5

vscode-django
bat
1.15.0

languagetool-linter
dav
0.21.3

python-environment-manager
don
1.2.4

python-extension-pack
don
1.7.0

gitlens
eam
14.9.0

pip-packages
etm
0.4.3

remotehub
Git
0.62.0

vscode-pull-request-github
Git
0.86.1

vsc-python-indent
Kev
1.18.0

rainbow-csv
mec
3.11.0

debugpy
ms-
2024.4.0

python
ms-
2024.4.1

vscode-pylance
ms-
2024.4.1

jupyter
ms-
2024.4.2024041101

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.9

vscode-jupyter-slideshow
ms-
0.1.6

azure-repos
ms-
0.38.0

remote-repositories
ms-
0.40.0

autodocstring
njp
0.6.1

r-debugger
RDe
0.5.4

r
REd
2.8.2

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.3.1

jinja
who
0.0.8

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
dsvsc021:30996838
gd77d436:30999572
jg8ic977:31013176

### Tasks

### Tasks

you might be able to look at the TIMELINE section

I've looked at it, i only have modifications till 31/03

Do you have steps that reproduce the issue, otherwise I am not sure what we can do here?

I usually work on my file with the 'Auto save' option enabled, which has been active for quite some time. I've been working without saving for over 2 weeks now. I close the window normally and find all the modifications I've made. Last Friday, I accidentally opened VS Code, I didn't even want to work on it, and when I tried to close it, for the first time, it asked me if I wanted to save the modifications, even though I hadn't made any. Thinking that I might have accidentally typed something, I clicked on 'Don't save.' However, when I reopened the file after an hour, I realized that only a very old version of the file was available (the version from 03/31).

that's not good
there is a history folder that saves the timeline in the vscode files
but I assume it's already been purged
you could try the Windows File Recovery app
but I doubt there's anything left for it to pickup

I am sorry that you lost file changes but without some clear steps how to reproduce to understand how this happened, I will have to close this issue.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Use Transifex as a translation platform

So @ccordoba12 gave a little nudge to take a look at transifex for translations and I am adding it here so maybe there can be some questions/answers about it if any.
I already created an organization, and I think it could help improving outreach by having mor translations (which might also be part of the website eventually)
If you all @spyder-ide/core-developers consider this would help, then maybe you should consider signing in, and handing your handles over so I can make you managers/coordinators/reviewers... etc
Cheers

@manipuladordedados can you join as well?

@goanpeca yes, looks promising


feat(material/dialog): Allow @Input for data sharing

Feature Description
Currently, Angular Material's MatDialog and CDK's Dialog components use MAT_DIALOG_DATA for passing data. This feature proposes to allow the usage of @Input for data sharing instead.
Use Case
This feature allows for greater flexibility and reusability of dialog components, particularly when using the Router option withComponentInputBinding. For example:
// Proposed usage with @Input
@Component({
  selector: 'app-my-dialog',
  template: ``
})
export class MyDialogComponent {
  @Input() name: string;
  @Input() age: number;
}

// Open dialog
this.dialog.open(MyDialogComponent, {
  data: { name: 'John', age: 30 }
});

Hi @crisbeto,
In theory, this approach works:
const dialogRef = this.dialog.open(MyDialogComponent);
dialogRef.componentInstance.name = 'John';
dialogRef.componentInstance.age = 30;

However, this method is tricky and not ideal for practical use. It would be better implemented directly within the CDK to ensure a more robust and streamlined solution for data binding via @Input.
I'm not familiar with the source code, so I'm unsure how this would integrate with the new Angular feature signals for compatibility.
Thanks for considering this feature.


[FEAT] Forgot password page

A user should be able to request a password reset.

Assign to me

Connect to API left


Refactor to move GPU driver to config

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

12 of 14 (85.71%)  changed or added relevant lines in 2 files are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 71.139%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/agent/common/gpu.go
11
13
84.62%

Files with Coverage Reduction
New Missed Lines
%

pkg/agent/common/gpu.go
8
66.15%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.2%

Covered Lines:
2598

Relevant Lines:
3652

💛  - Coveralls


Resend's nextjs example shows up an error

Describe the Bug
The code below from resend's official nextjs docs shows an error  (app router example)
import { EmailTemplate } from '../../../components/EmailTemplate';
import { Resend } from 'resend';

const resend = new Resend(process.env.RESEND_API_KEY);

export async function POST() {
  try {
    const { data, error } = await resend.emails.send({
      from: 'Acme<EMAIL_ADDRESS>      to<EMAIL_ADDRESS>      subject: 'Hello world',
      react: EmailTemplate({ firstName: 'John' }),
    });

    if (error) {
      return Response.json({ error }, { status: 500 });
    }

    return Response.json(data);
  } catch (error) {
    return Response.json({ error }, { status: 500 });
  }
}

This is the error
Argument of type '{ from: string; to: string[]; subject: string; react: ReactNode; }' is not assignable to parameter of type 'CreateEmailOptions'.
  Type '{ from: string; to: string[]; subject: string; react: ReactNode; }' is not assignable to type 'Required<Pick<EmailRenderOptions, "text">> & Partial<Pick<EmailRenderOptions, "react" | "html">> & CreateEmailBaseOptions'.
    Property 'text' is missing in type '{ from: string; to: string[]; subject: string; react: ReactNode; }' but required in type 'Required<Pick<EmailRenderOptions, "text">>'.ts(2345)
index.d.ts(159, 5): 'text' is declared here.

To Reproduce
Run this code to reproduce
import { EmailTemplate } from '../../../components/EmailTemplate';
import { Resend } from 'resend';

const resend = new Resend(process.env.RESEND_API_KEY);

export async function POST() {
  try {
    const { data, error } = await resend.emails.send({
      from: 'Acme<EMAIL_ADDRESS>      to<EMAIL_ADDRESS>      subject: 'Hello world',
      react: EmailTemplate({ firstName: 'John' }),
    });

    if (error) {
      return Response.json({ error }, { status: 500 });
    }

    return Response.json(data);
  } catch (error) {
    return Response.json({ error }, { status: 500 });
  }
}

Expected Behavior
I went to the nextjs app router github example and found this code and it shows no error, maybe this should be included by default so it won't confuse beginners like me.
import { EmailTemplate } from '../../../components/email-template';
import { Resend } from 'resend';
import * as React from 'react';

const resend = new Resend(process.env.RESEND_API_KEY);

export async function POST() {
  try {
    const { data, error } = await resend.emails.send({
      from: 'Acme<EMAIL_ADDRESS>      to<EMAIL_ADDRESS>      subject: "Hello world",
      react: EmailTemplate({ firstName: "John" }) as React.ReactElement,
    });

    if (error) {
      return Response.json({ error }, { status: 500 });
    }

    return Response.json({ data });
  } catch (error) {
    return Response.json({ error }, { status: 500 });
  }
}

Can you link the example that has the issue here?

Can you link the example that has the issue here?

https://resend.com/docs/send-with-nextjs#3-send-email-using-react
see app/api/send/route.ts

@AadityaThapa Why did you close this one? Were you able to fix it, or was it an issue on your side?

Did you fix this? @aad]


[graphql-vscode] SyntaxError: Using the export keyword between a decorator and a class is not allowed. Please use export @dec class instead.

Description
Decorators break graphql-language-service
If I use export @dec class, then typescript and eslint in my project produce the error Declaration or statement expected.
Example
const decorator: ClassDecorator = target => target

@decorator
export class Test {}

Log
21.09.2022, 00:58:56 [1] (pid: 579626) graphql-language-service-usage-logs: Could not parse the TypeScript file at file:///... to extract the graphql tags:
21.09.2022, 00:58:56 [1] (pid: 579626) graphql-language-service-usage-logs: SyntaxError: Using the export keyword between a decorator and a class is not allowed. Please use `export @dec class` instead. (15:0)

seems the title of this issue is an error message you've got. Please describe how you've got that.

This is a duplicate related to enabling legacy decorators

Hey @acao , thanks your explanation!  Is this a duplicate of #2294 ?

@yoshiakis indeed! Thank you, closing for this ticket with more information