Adding control C-0265: detection of over-privileged system:authenticated group

User description
Overview
Added control C-0265 that test if the system:authneticated group has elevated privileges over the cluster
See more here: https://thehackernews.com/2024/01/google-kubernetes-misconfig-lets-any.html

[x] My code follows the style guidelines of this project
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have performed a self-review of my code
[x] If it is a core feature, I have added thorough tests.
[x] New and existing unit tests pass locally with my changes

Type
Enhancement

Description

Added a new control C-0265 to check if the system:authenticated group has elevated privileges over the cluster.
Updated the list of controls in allcontrols.json, clusterscan.json, and security.json to include the new control.
Added a new rule to check if the system:authenticated group has sensitive roles.
Added metadata for the new rule.
Added test cases for the new rule, including inputs and expected outputs for both passing and failing scenarios.

Changes walkthrough
Relevant filesConfiguration changes6 files

C-0265-authenticateduserhasrbac.jsonAddition of new control C-0265

controls/C-0265-authenticateduserhasrbac.json

Added a new control C-0265 to check if the system:authenticated   group has elevated privileges over the cluster.

+24/-0

allcontrols.jsonUpdate of controls list

frameworks/allcontrols.json

Added control C-0265 to the list of controls.

+7/-1

clusterscan.jsonUpdate of controls list

frameworks/clusterscan.json

Added control C-0265 to the list of controls.

+6/-0

security.jsonUpdate of controls list

frameworks/security.json

Added control C-0265 to the list of controls.

+9/-3

raw.regoAddition of new rule for system:authenticated group

rules/system-authenticated-allowed-to-take-over-cluster/raw.rego

Added a new rule to check if the system:authenticated group has   sensitive roles.

+65/-0

rule.metadata.jsonAddition of metadata for new rule

rules/system-authenticated-allowed-to-take-over-cluster/rule.metadata.json

Added metadata for the new rule.

+27/-0

Tests5 files

expected.jsonAddition of expected output for failing test case

rules/system-authenticated-allowed-to-take-over-cluster/test/fail/expected.json

Added expected output for the failing test case of the new rule.

+74/-0

clusterrole.yamlAddition of input for failing test case

rules/system-authenticated-allowed-to-take-over-cluster/test/fail/input/clusterrole.yaml

Added input for the failing test case of the new rule.

+18/-0

clusterrolebinding.yamlAddition of input for failing test case

rules/system-authenticated-allowed-to-take-over-cluster/test/fail/input/clusterrolebinding.yaml

Added input for the failing test case of the new rule.

+12/-0

expected.jsonAddition of expected output for passing test case

rules/system-authenticated-allowed-to-take-over-cluster/test/success/expected.json

Added expected output for the passing test case of the new rule.

+1/-0

rolebinding.yamlAddition of input for passing test case

rules/system-authenticated-allowed-to-take-over-cluster/test/success/input/rolebinding.yaml

Added input for the passing test case of the new rule.

+26/-0

 ✨ Usage guide:
Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the describe tool (pr_description section), use the following template:
/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:
[pr_description]
some_config1=...
some_config2=...

  Enabling\disabling automation

When you first install the app, the default mode for the describe tool is:

pr_commands = ["/describe --pr_description.add_original_user_description=true"
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:

pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

type: the PR type.
summary: the PR summary.
walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

  Custom labels
The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].
If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

Main topic:performance - pr_agent:The main topic of this PR is performance
New endpoint - pr_agent:A new endpoint was added in this PR
SQL query - pr_agent:A new SQL query was added in this PR
Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

  Inline File Walkthrough 💎
For enhanced user experience, the describe tool can add file summaries directly to the "Files changed" tab in the PR page.
This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs).
To enable inline file summary, set pr_description.inline_file_summary in the configuration file, possible values are:

'table': File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab.
true: A collapsable file comment with changes title and a changes summary for each file in the PR.
false (default): File changes walkthrough will be added only to the "Conversation" tab.

  Utilizing extra instructions
The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.
Examples for extra instructions:
[pr_description]
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the describe usage page for a comprehensive guide on using this tool.

Because the subject here will always be system:authenticated I think we should consider returning the binding as the failing object. (If so need to add a filter rego to return only the bindings so roles won't be counted as potential failing resources.)

I think it should be similar to anonymous-access-enabled, just adding roles if you want to check what permissions are being granted

@slashben after we fix @YiscahLevySilas1 requests


updated python package versions, added poetry config.

Hello, I updated the python packages by adding a poetry config.

@mishraomp There seems to be a permission issue with the docker build:
ERROR: failed to solve: failed to push ghcr.io/bcgov/nr-hydrometric-rating-curve-archived/frontend:latest: unexpected status: 403 Forbidden
Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/bcgov/nr-hydrometric-rating-curve-archived/frontend:latest: unexpected status: 403 Forbidden

Hi @tobiasmllr ,please use branches , as forks wont have permissions

Sorry just noticed this was the wrong repository anyways!


Added Emacs mode Meta-. binding 'yank last arg'

Fixes #343. Alternative implementation to #336 that uses a single function and also implements yank-nth-arg, in the same style as readline.

Hi @adamchainz,
Cool! Thanks a lot for this.
I still need to take some time to compare this implementation and the other.
Probably, I'd like to go for a solution where the key bindings are completely stateless, and the state is stored in the Buffer object. (Need to think about this.)
Jonathan

Happy to change that but I thought it was rather elegant that it can all be done with function-bound 'static' variables 😄

Hi @adamchainz,
I combined both pull request in the following commit: https://github.com/jonathanslenders/python-prompt-toolkit/commit/0c09bf034aeeb2facbfbc070cc4fa2f58620baa5
If you have time, could you have a look and see whether this implements all you need?
Thanks,
Jonathan

Thanks! Sure, will do this evening.


HOSTEDCP-2002: Add documentation around crun migration for HCP

Which issue(s) this PR fixes:
Fixes #HOSTEDCP-2002

/retest

/lgtm


代码部署到服务器上，无法登录 ,警告异地登录

0. Report Issue Guide

Please search in the issue first, and make sure your problem had not been reported before.
If your issue is related to wechaty-puppet-padchat, please report the issue at https://github.com/lijiarui/wechaty-puppet-padchat/issues/new
If your issue is related to wechaty-puppet-puppeteer, please report the issue at https://github.com/Chatie/wechaty-puppet-puppeteer/issues/new
If your issue is DIRECT related to Wechaty, then please follow the below template and make sure you fill it as required in detail.

1. Expected behavior
本地调试是可以登录的，部署到服务器上，微信提醒 【....扫码请求在其他城市的设备登陆...】
Question: What behavior do you expect?
Answer:
2. Actual behavior
Question: What actual behavior did you experience?
Answer:
3. Steps to reproduce your problem (and fixes, if any)
This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.
Question: What're the reproducible steps for us to see your problem?
Answer:
4.

登录不了了
22:11:16 WARN PuppetPuppeteerBridge onDialog() page.on(dialog) type:type() {
0|app  |     return this._type;
0|app  |   } message:当前登录环境异常。为了你的帐号安全，暂时不能登录web微信。你可以通过Windows微信、Mac微信或者手机客户端微信登录。
0|app  | (node:22502) UnhandledPromiseRejectionWarning: Error: Error: type() {
0|app  |     return this._type;
0|app  |   }(当前登录环境异常。为了你的帐号安全，暂时不能登录web微信。你可以通过Windows微信、Mac微信或者手机客户端微信登录。)
0|app  |     at PuppetPuppeteer.puppet.on.error (/www/thewave-server/node_modules/_wechaty@0.22.6@wechaty/dist/src/wechaty.js:436:44)
0|app  |     at PuppetPuppeteer.emit (events.js:182:13)
0|app  |     at PuppetPuppeteer.EventEmitter.emit (domain.js:442:20)
0|app  |     at PuppetPuppeteer.emit (/www/thewave-server/node_modules/_wechaty-puppet@0.14.1@wechaty-puppet/dist/src/puppet.js:171:22)
0|app  |     at Bridge.bridge.on.e (/www/thewave-server/node_modules/_wechaty-puppet-puppeteer@0.14.1@wechaty-puppet-puppeteer/dist/src/puppet-puppeteer.js:207:47)
0|app  |     at Bridge.emit (events.js:182:13)
0|app  |     at Bridge.EventEmitter.emit (domain.js:442:20)
0|app  |     at Bridge. (/www/thewave-server/node_modules/_wechaty-puppet-puppeteer@0.14.1@wechaty-puppet-puppeteer/dist/src/bridge.js:118:18)
0|app  |     at Generator.next ()
0|app  |     at fulfilled (/www/thewave-server/node_modules/_wechaty-puppet-puppeteer@0.14.1@wechaty-puppet-puppeteer/dist/src/bridge.js:23:58)
0|app  |     at process._tickCallback (internal/process/next_tick.js:68:7)
0|app  | (node:22502) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)

I found you are using PuppetPuppeteer which is using web wechat, web wechat has some limit, see more: https://docs.chatie.io/v/zh/#web-limit-1

page not found

服务器上，如何避免出现异地登录的警告, 谢谢！

您好，请问解决了吗

服务器上，如何避免出现异地登录的警告, 谢谢！

您好，请问解决了吗

有的时候又可以登陆了，真奇怪

服务器上，如何避免出现异地登录的警告, 谢谢！

下载客户端登陆，手机确认就可以了吧


Add auxiliary network devices support

Auxiliary devices pool is created when auxNetDevice type is specified in plugin config file. Auxiliary devices discovered for each discovered network PCI device, meaning only auxiliary network devices with parent PCI device are supported.
New AuxTypes selector allows to filter auxiliary device by the type.  For ex., given following auxiliary devices list..
foo.bar.0
fancy.bar.0
foo.bar.1
foo.baz.0

.. and selector value ["bar"], first three devices will be added to the pool.
Auxiliary network devices accept selectors: vendors, devices, drivers, pfNames, rootDevices, linkTypes, isRdma.
NOTE patchset built on top of #441

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
136 unchanged lines in 10 files lost coverage.
Overall coverage increased (+2.7%) to 79.923%

Files with Coverage Reduction
New Missed Lines
%

pkg/accelerator/accelDevice.go
2
84.62%

pkg/accelerator/accelDeviceProvider.go
4
87.5%

pkg/utils/testing.go
5
56.6%

pkg/factory/factory.go
12
89.86%

pkg/utils/netlink_provider.go
12
25.0%

pkg/netdevice/netDeviceProvider.go
14
87.18%

pkg/utils/sriovnet_provider.go
15
28.57%

pkg/netdevice/pciNetDevice.go
16
69.84%

pkg/resources/deviceSelectors.go
18
88.13%

pkg/utils/utils.go
38
82.91%

Totals

Change from base Build<PHONE_NUMBER>:
2.7%

Covered Lines:
1867

Relevant Lines:
2336

💛  - Coveralls

@DmytroLinkin
i tested out your PR and added some comments.
i was able to successfully spin up a pod with SF + RDMA resources
one issue i found is that the injected env variable is showing the parent PF instead of the allocated SF.
/ # env

KUBERNETES_SERVICE_PORT=443

KUBERNETES_PORT=tcp://<IP_ADDRESS>:443

HOSTNAME=testpod1

SHLVL=1

HOME=/root

PCIDEVICE_NVIDIA_COM_MLNX_SF=0000:03:00.0

TERM=xterm

KUBERNETES_PORT_443_TCP_ADDR=<IP_ADDRESS>

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

KUBERNETES_PORT_443_TCP_PORT=443

KUBERNETES_PORT_443_TCP_PROTO=tcp

KUBERNETES_SERVICE_PORT_HTTPS=443

KUBERNETES_PORT_443_TCP=tcp://<IP_ADDRESS>:443

KUBERNETES_SERVICE_HOST=<IP_ADDRESS>

PWD=/

@DmytroLinkin
i tested out your PR and added some comments.
i was able to successfully spin up a pod with SF + RDMA resources
one issue i found is that the injected env variable (PCIDEVICE_NVIDIA_COM_MLNX_SF) is showing the parent PF instead of the allocated SF.
/ # env

KUBERNETES_SERVICE_PORT=443

KUBERNETES_PORT=tcp://<IP_ADDRESS>:443

HOSTNAME=testpod1

SHLVL=1

HOME=/root

PCIDEVICE_NVIDIA_COM_MLNX_SF=0000:03:00.0

TERM=xterm

KUBERNETES_PORT_443_TCP_ADDR=<IP_ADDRESS>

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

KUBERNETES_PORT_443_TCP_PORT=443

KUBERNETES_PORT_443_TCP_PROTO=tcp

KUBERNETES_SERVICE_PORT_HTTPS=443

KUBERNETES_PORT_443_TCP=tcp://<IP_ADDRESS>:443

KUBERNETES_SERVICE_HOST=<IP_ADDRESS>

PWD=/

It is genericInfoProvider which returns pciAddress of the device. I changed it to return pciAddr/auxiliary

/retest

minor nit on doc update.
otherwise LGTM.
I have re-triggered Mellanox CI.

@SchSeba @Eoghan1232 PATL

@SchSeba @Eoghan1232 PTAL, id like to try and get this merged soon.
i believe the PR Is in a good state and LGTM'd it.

Thx for working on this one @DmytroLinkin  !


add a command to have voltaire add reactions

I think !volt react {emoji} would be the way to go.
Cross server behavior should be tested for custom emoji.
It would be nice to have a way to send custom emoji via dm without needing nitro. Maybe using an id? If we need to use IDs, a command to list all of the custom emoji ID would also be helpful.

Requested by @Undersc_re on the discord

added in https://github.com/nminchow/Voltaire/commit/e24919f99abd669f99ff10800a56de4be172d2b1


Segfault on invalid imports

Invalid import "\x00" causes a segfault.
Tested on yara 3.5.0 (cloned today from master).
Test data:
import "\x00"
Valgrind output: https://gist.github.com/fumfel/497b0863667d4cd4a1819872328e5b6d
Bug exists in yara/libyara/hash.c:

https://github.com/VirusTotal/yara/blob/f502bdf4903545cfc75dfe15bed650138da53a81/libyara/hash.c#L73
https://github.com/VirusTotal/yara/blob/03c2aac2c1253b096342cf4b745d66e448c7d110/libyara/hash.c#L183
https://github.com/VirusTotal/yara/blob/03c2aac2c1253b096342cf4b745d66e448c7d110/libyara/hash.c#L93

Bug found with american fuzzy lop.

Problem still exists, tested repo HEAD: a0bb3836f16e3c5d0c2a1da097a1ebacbebc3a94.

Fix is up. I'd be curious if you are able to trigger this any other way, especially via modules parsing files. :)


Hangs using IE 11

Selenium with IE works fine, but using IE in EasyRepro does not, it just hangs for many minutes and then throws a timeout exception. Here is the call stack:

I don't see the iexplore process, only IEDriverServer.
IE version:

Windows 10 Build 1803 (17134.112)
EasyRepro v9 as downloaded from here 18th June.
The code works fine with Chrome.

This issue goes away if you update IEDriver to 3.13, but you'll have to be sure it goes into your bin and not the copy from nuget, which is still on 3.12.
Now I can't login but that's a whole different issue.

@markleavesley - Do you face these issues when using version 3.4 of the IEDriver?
You'll also want to check and make sure that the Selenium.Support and Selenium.WebDriver versions are on 3.11.2 as these were the most recent versions that we've done test passes against.
Note: The IEDriver linked above is X64. The 32bit version can be found here  if required.
Please let us know if you still encounter issues with these matching versions.
Thanks,
Tyler

@TYLEROL I'm using the latest nuget packages (3.13)
I've tried the IEDriver x86 above and nuget versions you suggest and it hangs, works with x64 version. I am running Selenium to control another IE browser at the same time if that makes any difference.
With the x64 version I still get the login problem but I believe that to be an IE/domain/auto-login issue.

@markleavesley I had the same issue yesterday.
Solution : in the TestSettings.cs file, change the privateMode to false. It will switch to non private mode and it will work as expected.


Collect metrics from several applications

Is there are a way to mark metrics with some tag to separate them from other application/environment?

That's what we do, so can you please elaborate a bit more what exactly you need? Is it custom metrics?

You can set tags per application https://github.com/apiaryio/heroku-datadog-drain-golang#configuration

Sorry, I missed that metric. Closed.

No worries, documentation is really not there ...


(PUP-3045) Re-factor timeout spec test for windows

This patch splits the spec test for exec timeouts into separate Windows and
POSIX cases.

Oh right, we don't have AppVeyor for 3.8 PR CI, so no wonder this slipped through a failure for Windows.  Any luck on the 2.1.1 front?

We can backport some AppVeyor...

@ferventcoder I did in fact backport the appveyor setup: #4161 :)

@kylog \o/


Trying to decode file throws a error

I followed the README and added the usage lines to my project, but in the decodeOpus line throws the follow error below:

With this error happening I not able to use this library.

Hi sorry for the delay - try to update to the latest and LMK if you are still running into this.
Anyway I suspect you didn't link the project correctly. Make sure to run pod install


ROHD landing page website structure

Description & Motivation
It's useful to have a web landing that displays ROHD. This site is going to act as the learning center and the compilation of the bootcamp and tutorial.
https://quekyj.github.io/rohd/ to preview ROHD website.
Related Issue(s)
None
Testing
It's a static web page, don't think it requires any testing.
Backwards-compatibility
No. No major changes have been made to the codebase.
Documentation
No.

The website looks good. Great work.
The API link went to a 404. https://intel.github.io/rohd/api

The API link went to a 404. https://intel.github.io/rohd/api

This is expected until it's published, since that's at the official intel release area rather than the sandbox where it's visible now

It seems to me that it would be nice for the website to have a separate repository so as not to mix work.

It seems to me that it would be nice for the website to have a separate repository so as not to mix work. It will be possible to name the repository using the standard pattern www-rohd. Then the site names will be uniform (for example, www-rohd-vf, www-rohd-anything).

I was imagining having one website for the whole ROHD ecosystem rather than one per package, so that it feels more coherent.  Do you think there's good reason to have multiple websites per-package?  I'm interested if you have another perspective on it.
Setting up a separate repository is a bit of paperwork, but worth it if it makes things sufficiently cleaner.  I'm not sure what the best/standard practice is here.  There seems like some value in keeping documentation in the same repo as the code (examples, explanations, tutorials, etc.), but I agree there's a downside to all the website infrastructure sitting in the same repo.  One nice thing is jekyll makes all the actual contents of the website just normal Markdown, so only configuration stuff really feels like extraneous "website stuff".
I would imagine a "big" framework having different repos for sure, and a "small" framework not even having a website (or a really simple one as part of the repo).  I'm not sure where ROHD currently sits or will sit on that spectrum.  Maybe it's something where the right answer changes as ROHD grows?

I was imagining having one website for the whole ROHD ecosystem rather than one per package, so that it feels more coherent. Do you think there's good reason to have multiple websites per-package? I'm interested if you have another perspective on it.

In fact, I also like the idea of a single site more, because it simplifies maintenance, and in general I don’t see any reason for separation either (at least for now). The main thing is that ROHD itself retains a modular structure (Core, VF, Cosim, etc.), so that the user can choose what he needs.

Setting up a separate repository is a bit of paperwork, but worth it if it makes things sufficiently cleaner. I'm not sure what the best/standard practice is here. There seems like some value in keeping documentation in the same repo as the code (examples, explanations, tutorials, etc.), but I agree there's a downside to all the website infrastructure sitting in the same repo. One nice thing is jekyll makes all the actual contents of the website just normal Markdown, so only configuration stuff really feels like extraneous "website stuff".

I also think that keeping documentation and code together has advantages. But, in my opinion, the site is still not documentation of projects. And the project documentation itself is not the “native” content of the site (its “native” content can be, for example, articles, news, and so on) (by “native” I mean the content stored together with the site, in its repository).
If we consider ROHD as an umbrella project within which Core, VF, Cosim exist, then why would the website be in the Core repository? And if the documentation is tied to the site, then in this case, the documentation for VF or Cosim will have to be written in the Core repository?
It seems to me that the idea of a separate repository for a site takes on more weight if that site will serve multiple repositories. It might look like this:

Repositories (Core, VF, Cosim) generate API description as it is now (docs branch). Also, inside each repository, its own documentation / guides are written with the only condition - they should be easy to read and change. Essentially, they should just be Markdown files with no build required. The user can fully study all this without even knowing that the site exists at all.
Website - a separate repository that stores both site-specific content (for example, the start page, “404” page, etc.) and metadata associated with data in the Core, VF, Cosim repositories (we don’t need to duplicate data, we you need to know where to get them and how to process them).
Building a site is

extraction of API description files from branches docs Core, VF, Cosim,
extract documentation/guides from Core, VF, Cosim repositories,
conversion of documentation/guides using metadata (for example, adding titles necessary for Jekyll),
site generation and placement in the network.

I would imagine a "big" framework having different repos for sure, and a "small" framework not even having a website (or a really simple one as part of the repo). I'm not sure where ROHD currently sits or will sit on that spectrum. Maybe it's something where the right answer changes as ROHD grows?

Definitely. Maintenance overhead should not be too high for current conditions. Small teams should evaluate whether they have the resources to maintain individual entities.

Sorry if this all sounds like I'm pushing my decision. I'm just offering my ideas.

Some good points @chykon, thank you!
@quekyj what are your thoughts?  Anyone else watching is welcome to chime in as well :)
Meanwhile, I'll start looking into the effort of setting up a separate repo/website so we have the information.

Do we have to include VF and cosim into website as well? Because I am not sure how we are going to position ROHD. Like Django, they have a framework for web development as core repository but all the projects like Graphene-Django, Django Rest Framework, Django money have their own repository and website.  It's gone back to the developer of the project on how they are going to build and maintain the site. This is what I am thinking.
But to be honest, a separate repository is good as well. We can let other developers open pull requests to add their documentation/tutorials to the site if they want. Things is we need to really think of the ecosystem and practice.

I made some progress to figure out what process is required to get another website repo set up, and the barrier is lower than I expected.  I think @chykon's idea of a central repo that aggregates most of its content from the other ROHD ecosystem repositories makes sense, where each repo hosts vanilla Markdown documentation could be a good approach.  We could set up GitHub actions on a cron job to periodically update or something maybe.
@quekyj, I think since all these base repositories for ROHD are part of the sort-of "base" ecosystem and hosted by Intel, it is reasonable to keep one central website.  Others new frameworks on top of it could make their own website potentially
If this all sounds good, I'll hopefully be able to get through to make the new website repo next week.

A separate repo for the website has been created here: https://github.com/intel/rohd-website

Issue referred to pull request #359


Menus close before you can use them

On my mac (Chrome 119/Firefox 119) the top dropdown menus are too far away from their triggers so they close before you can use them.  It seems fine in Safari 17.0 / Edge 119?!
https://github.com/nuxt/nuxt.com/assets/2112282/f575fd79-c08c-4e8f-8461-197c472cff41

Duplicate of #1419

Should have been fixed already!

Looks good now.


What is the best practice to extract multiple entities from single sentence to Slots?

I had tried NLU and also Action. But it seems I can set Slots one element per sentence
Rasa Core version:
rasa-core==0.13.0
rasa-core-sdk==0.12.1
rasa-nlu==0.14.1

Python version:
3.6.8
Operating system (windows, osx, ...):
OSX 10.14.2
Issue:
Slot takes only latest entity. However, in the ActionConfirm I can be able to retrieve both of my values. Which is good for API calling. But when I return Slots by using list. It is not comes back to bot bot. It comes only one last element.
class ActionConfirm(Action):
    def name(self):
        return "action_confirm"

    def run(self,
            dispatcher,  # type: CollectingDispatcher
            tracker,  # type: Tracker
            domain  # type:  Dict[Text, Any]
            ):
        color = next(tracker.get_latest_entity_values("COLOR"), None)
        qty = next(tracker.get_latest_entity_values("QTY"), None)
        print(color, qty)
        dispatcher.utter_template('utter_confirm', tracker)
        return [SlotSet("COLOR", color),
                SlotSet("QTY", qty)]

From print my Action Server prints out red, 10. It is correct.
But utter_template prints สั่งของดังนี้น่ะครับ None 10.
debugger
Your input ->  red 10
2019-01-29 22:10:14 DEBUG    rasa_core.tracker_store  - Creating a new tracker for id 'default'.
2019-01-29 22:10:14 DEBUG    rasa_core.processor  - Received user message 'red 10' with intent '{'name': 'inform', 'confidence': 0.9729769229888916}' and entities '[{'start': 0, 'end': 3, 'value': 'red', 'entity': 'COLOR', 'confidence': 0.9894516453793424, 'extractor': 'ner_crf'}, {'start': 4, 'end': 6, 'value': '10', 'entity': 'QTY', 'confidence': 0.9685424175027326, 'extractor': 'ner_crf'}]'
2019-01-29 22:10:14 DEBUG    rasa_core.processor  - Logged UserUtterance - tracker now has 3 events
2019-01-29 22:10:14 DEBUG    rasa_core.processor  - Current slot values:
	COLOR: None
	COLOR_LIST: None
	PRICE_LIST: None
	QTY: 10
2019-01-29 22:10:14 DEBUG    rasa_core.policies.memoization  - Current tracker state [None, None, None, {}, {'intent_inform': 1.0, 'prev_action_listen': 1.0, 'slot_QTY_0': 0.09090909090909091, 'entity_QTY': 1.0, 'entity_COLOR': 1.0}]
2019-01-29 22:10:14 DEBUG    rasa_core.policies.memoization  - There is no memorised next action
2019-01-29 22:10:14 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-01-29 22:10:14 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_0_KerasPolicy
2019-01-29 22:10:14 DEBUG    rasa_core.processor  - Predicted next action 'action_confirm' with prob 0.49.
2019-01-29 22:10:14 DEBUG    rasa_core.actions.action  - Calling action endpoint to run action 'action_confirm'.
2019-01-29 22:10:14 DEBUG    rasa_core.processor  - Action 'action_confirm' ended with events '['SlotSet(key: COLOR, value: red)', 'SlotSet(key: QTY, value: 10)']'
2019-01-29 22:10:14 WARNING  rasa_core.processor  - Action 'action_confirm' set a slot type 'QTY' that it never set during the training. This can throw of the prediction. Make sure to include training examples in your stories for the different types of slots this action can return. Remember: you need to set the slots manually in the stories by adding '- slot{"QTY": "10"}' after the action.
2019-01-29 22:10:14 DEBUG    rasa_core.processor  - Bot utterance 'BotUttered(text: สั่งของดังนี้น่ะครับ None 10, data: {
  "elements": null,
  "buttons": null,
  "attachment": null
})'
สั่งของดังนี้น่ะครับ None 10
2019-01-29 22:10:14 DEBUG    rasa_core.policies.memoization  - Current tracker state [None, None, {}, {'intent_inform': 1.0, 'prev_action_listen': 1.0, 'slot_QTY_0': 0.09090909090909091, 'entity_QTY': 1.0, 'entity_COLOR': 1.0}, {'intent_inform': 1.0, 'slot_QTY_0': 0.09090909090909091, 'prev_action_confirm': 1.0, 'entity_QTY': 1.0, 'entity_COLOR': 1.0}]
2019-01-29 22:10:14 DEBUG    rasa_core.policies.memoization  - There is no memorised next action
2019-01-29 22:10:14 DEBUG    rasa_core.policies.form_policy  - There is no active form
2019-01-29 22:10:14 DEBUG    rasa_core.policies.ensemble  - Predicted next action using policy_0_KerasPolicy
2019-01-29 22:10:14 DEBUG    rasa_core.processor  - Predicted next action 'action_listen' with prob 0.88.
2019-01-29 22:10:14 DEBUG    rasa_core.processor  - Action 'action_listen' ended with events '[]'
<IP_ADDRESS> - - [2019-01-29 22:10:14] "POST /webhooks/rest/webhook?stream=true&token= HTTP/1.1" 200 296 0.226344

What is the best practice to extract multiple entities from single sentence to Slots?

@elcolie
Were you able to solve this issue? I am facing the same issue.


Fix a bug that prevents correct StationXMLs for stations with "EX" "EY" in their names

There's a very subtle bug that caused the Ex or Ey channels to be overwritten (with the other one) and therefore never recorded in StationXML for sites with names such as REX11, REY12 etc containing "EX" and "EY" in their names. In principle this can also happen to sites with "HX" "HY" "HZ" in their names but that hasn't happened yet. Took me a full day of debugging to locate this problem.
In from_many_mt_files.py, line 185: fn.name.lower() needs to be replaced with fn.name[len(station):].lower()

@akelbert Good find, bummer it took so long to find.  Do you need this to be in a release that can be installed by pip or conda-forge?  I added your proposed fix to the main branch.

Thanks for fixing it! Yes, would be great to merge it into a pip release. No urgency since I'm working with my local copy where I have this fixed, but the sooner the better, of course!


One proxy socket to multiple remote server connections is fully supported

Now one http proxy connection can have multiple remote server connections.
So firefox for mac is fully supported. Enjoy your browser :)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Felix Liu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

Codecov Report

Merging #53 into master will decrease coverage by -0.09%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #53      +/-   ##
=========================================
- Coverage    9.71%   9.63%   -0.09%
=========================================
  Files          96      96
  Lines        4806    4847      +41
=========================================
  Hits          467     467
- Misses       4339    4380      +41

Impacted Files
Coverage Δ

src/Socket/SocketProtocol.swift
0% <ø> (ø)
:white_check_mark:

...AdapterSocket/Shadowsocks/ShadowsocksAdapter.swift
0% <ø> (ø)
:white_check_mark:

src/Socket/ProxySocket/SOCKS5ProxySocket.swift
0% <ø> (ø)
:white_check_mark:

src/Socket/ProxySocket/HTTPProxySocket.swift
0% <ø> (ø)
:white_check_mark:

src/Tunnel/Tunnel.swift
0% <ø> (ø)
:white_check_mark:

src/Socket/AdapterSocket/SOCKS5Adapter.swift
0% <ø> (ø)
:white_check_mark:

src/Socket/AdapterSocket/DirectAdapter.swift
0% <ø> (ø)
:white_check_mark:

src/Socket/AdapterSocket/SpeedAdapter.swift
0% <ø> (ø)
:white_check_mark:

src/Socket/AdapterSocket/RejectAdapter.swift
0% <ø> (ø)
:white_check_mark:

src/Socket/AdapterSocket/AdapterSocket.swift
0% <ø> (ø)
:white_check_mark:

... and 4 more

Continue to review full report at Codecov.

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

Thank you for you contribution.
I haven't check it through but I'm not going to merge it into master, but an independent branch.
As far as I know, Firefox is the only one (probably together with some others built with Necko, do let me know if there are more) that uses one socket to send requests to different hosts to proxy servers. This behavior complies with the specification, but complicates things on the server side with little improvement on the performance.
Anyway, there is a simple workaround by setting the proxy to SOCKS5 server, which does not complicate so many things for just supporting Necko-based apps.
Since I'm working on libnekit, this project is (very likely) not going to receive more updates, so people can pick up the multihost-one-socket support on this branch without losing anything if they want to.


Add DEVICE_DEFAULT registration for DataFormatDimMap and DataFormatVecPermute

DataFormatDimMap and DataFormatVecPermute are necessary for pluggable devices with the GPU type that want to leverage existing grappler optimizations.

@rohan100jain Can you please review this PR ? Thank you!

Hi @rohan100jain Can you please review this PR ? Thank you!

Bumping this to hopefully get some eyes on it. DataFormatDimMap and DataFormatVecPermute are necessary for pluggable devices with the GPU type that want to leverage existing grappler optimizations. Thanks!


Possible OpenLane version issue

I've tried running the flow using both main branch and io_fix branch but each time flow stops with the following error:
[INFO PDN-0016] Power Delivery Network Generator: Generating PDN
  config: /home/ayildiz/efabless/clear-io_fix/openlane/fpga_core/pdn.tcl
Error: pdn.tcl, 17 TypeError in method 'microns_to_dbu', argument 1 of type 'double'
[ERROR]: during executing openroad script /openlane/scripts/openroad/pdn.tcl
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
child process exited abnormally

I also had to make small modifications in the following files to run make harden command:
diff --git a/openlane/cbx_1__0_/pin.cfg b/openlane/cbx_1__0_/pin.cfg
index c369a8a..d75187f 100644
--- a/openlane/cbx_1__0_/pin.cfg
+++ b/openlane/cbx_1__0_/pin.cfg
@@ -36,9 +36,6 @@ top_width_0_height_0__pin_[0-9].*_
 top_width_0_height_0__pin_[1][0-9]_lower.*
 top_width_0_height_0__pin_[0-9]_lower.*

-#N
-top_width_0_height_0__pin_11_lower.*
-
 #S
 bottom_grid_pin.*

diff --git a/openlane/fpga_core/interactive.tcl b/openlane/fpga_core/interactive.tcl
index 960e985..f7e2b80 100644
--- a/openlane/fpga_core/interactive.tcl
+++ b/openlane/fpga_core/interactive.tcl
@@ -75,7 +75,7 @@ add_macro_placement tie_array [expr {$floorplan_x / 2}] [expr {$switches_y(8,8)

 manual_macro_placement f

-detailed_placement
+detailed_placement_or -log $::env(placement_logs)/detailed.log -def $::env(placement_results)/$::env(DESIGN_NAME).def

 gen_pdn

@@ -107,4 +107,4 @@ run_magic_drc
 run_magic_spice_export
 run_lvs

-run_antenna_check; # to verify the above and get a final report
\ No newline at end of file
+run_antenna_check; # to verify the above and get a final report

I've also been informed that the OpenLane tag that is defined in
https://github.com/efabless/clear/blob/f7a6b19f604a677eed6efa6690fddb81fd99a67f/Makefile#L26
points to a very old version.

Closing the issue since it is linked to an older commit.


fixed pagination

Rewrite RecentTxCard to remove Static Component and just use static data. No need to duplicate components
Pagination no longer triggers page change. The parent component handles that
Added dropdown selector that changes the number of transactions to display per page
Update the design to match the design update
update the mobile display base on the conversation on slack
Fix ... showing based on https://github.com/MystenLabs/sui/pull/3157#discussion_r924570934

https://user-images.githubusercontent.com/8676844/179850272-f0dab283-9021-472f-aa06-86c95ee238d2.mov

Out of range fix
https://user-images.githubusercontent.com/8676844/179855682-e616dc2a-4d04-4a9a-9040-8749869d2d31.mov

Nice!

@666lcz https://www.figma.com/file/OzLaRFzevjxdQAbybWEZk0/Sui-Visualize?node-id=2347%3A50095
Uploading Screen Recording 2022-07-19 at 8.11.17 PM.mov…


Infinite Loading

Nothing is working on home page , not login , signup just showing loading state

There is no singup and login.
Go to stocks-api-qkyy.onrender.com/
It should show:

Oh sorry i don't know how i opened issue here . I think i opened this issue here by accidently i was opening it in other repo.


New version: FLINT_jll v200.800.400+0

Autogenerated JLL package registration

Registering JLL package FLINT_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/FLINT_jll.jl
Version: v200.800.400+0
Commit: 16d496e4594ebb2e3ca15aad44266af9a3cda92c
Revision on Yggdrasil: https://github.com/JuliaPackaging/Yggdrasil/commit/40c92adaf135c250f199fef76352f8f12189bc5f
Created by: @fingolfin

This version of the JLL is for Julia 1.0-1.5, so a CI test using Julia 1.6 won't pass.
However, we wanted to have this held anyway, so that someone (e.g. @thofma) can update LoadFlint.jl first.

This could be merged now