[REQUEST Membership]: New membership for Congrool

GitHub Username

@Congrool
Organization you are requesting membership in

@openyurtio
Sponsors

@rambohe-ch
Requirements

[x] I have joined in the community Dingding and [WeChat]
[x] I often attend Openyurt Community Week
[x] I have reviewed the [community membership docs]
[x] I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
[x] I have checked my affiliation in devstats (if it's not correct, please fix in cncf/gitdm)
[x] I am actively contributing to 1 or more OpenYurt subprojects

List of your contributions

PRs reviewed / authored:
openyurtio/openyurt#496
openyurtio/openyurt#512
openyurtio/openyurt#517
openyurtio/openyurt#520

Issues:
openyurtio/openyurt#484
openyurtio/openyurt#511

Brief Introduction
Hello, I'm a student of ZJU SEL and major in Edge Computing. It's my honor to apply for the membership of OpenYurt Community. I'd like make my contribution to the development of the community.

+1

agree +1


In which file is the path to the configs specified

title says all

File: Hooks.cpp
Line: 60 (it can be different
Code: config = std::make_unique<Config>("Osiris");

thx


Rule id:920350 block only in PL=4

Describe the bug
On the new server RHEL 8.2 I have to move to the CRS 3:
mod_security-2.9.2-8.el8.x86_64
mod_security_crs-3.0.0-5.el8.noarch
I do not understand the logic, because the rule # 920350 block requests when I set in the crs-setup setvar:tx.paranoia_level=4 only.
When I verify the file REQUEST-920-PROTOCOL-ENFORCEMENT.conf
771 SecRule REQUEST_HEADERS:Host "^[\d.:]+$" \  772   "msg:'Host header is a numeric IP address',\  773    phase:request,\  774    rev:'2',\  775    ver:'OWASP_CRS/3.0.0',\  776    maturity:'9',\  777    accuracy:'9',\  778    t:none,\  779    block,\  780    logdata:'%{matched_var}',\  781    severity:'WARNING',\  782    id:920350,\  783    tag:'application-multi',\  784    tag:'language-multi',\  785    tag:'platform-multi',\  786    tag:'attack-protocol',\  787    tag:'OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST',\  788    tag:'WASCTC/WASC-21',\  789    tag:'OWASP_TOP_10/A7',\  790    tag:'PCI/6.5.10',\  791    setvar:'tx.msg=%{rule.msg}',\  792    setvar:tx.anomaly_score=+%{tx.warning_anomaly_score},\  793    setvar:tx.%{rule.id}-OWASP_CRS/POLICY/IP_HOST-%{matched_var_name}=%{matched_var}"
there is no tag: paranoia-level
so how to manage this rule, and how to find out on which paranoia-level will be activated if there is no tag?
how to activate this rule in another global paranoia-level for example 2?

Hi @askifyouneed you may want to ask that question on the OWASP CRS project - https://github.com/coreruleset/coreruleset

Which exactly https://github.com/coreruleset/coreruleset/issues/new/choose.
Help and support redirect to the stackexchange which is empt,
OWASP Core Rule Set mailing list redirect to the Google groups which are used by nobody
:(

I am sorry to hear that. They have moved recently to a new home. Trustwave note on that - https://github.com/SpiderLabs/owasp-modsecurity-crs/blob/v3.3/dev/README.md

sorry but I still can not find the issue where I can put my question (besides Google groups, but it looks dead)

Hi @askifyouneed,

mod_security_crs-3.0.0-5.el8.noarch

that's a bit old, there are so many modification in newer versions.

I do not understand the logic, because the rule # 920350 block requests when I set in the crs-setup setvar:tx.paranoia_level=4 only.

you mean eg. if the PL=2 then this rule isn't activated?

When I verify the file REQUEST-920-PROTOCOL-ENFORCEMENT.conf
771 SecRule REQUEST_HEADERS:Host "^[\d.:]+$"
772 "msg:'Host header is a numeric IP address',
773 phase:request,
774 rev:'2',
775 ver:'OWASP_CRS/3.0.0',
776 maturity:'9',
777 accuracy:'9',
778 t:none,
779 block,
780 logdata:'%{matched_var}',
781 severity:'WARNING',
782 id:920350,
783 tag:'application-multi',
784 tag:'language-multi',
785 tag:'platform-multi',
786 tag:'attack-protocol',
787 tag:'OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST',
788 tag:'WASCTC/WASC-21',
789 tag:'OWASP_TOP_10/A7',
790 tag:'PCI/6.5.10',
791 setvar:'tx.msg=%{rule.msg}',
792 setvar:tx.anomaly_score=+%{tx.warning_anomaly_score},
793 setvar:tx.%{rule.id}-OWASP_CRS/POLICY/IP_HOST-%{matched_var_name}=%{matched_var}"

I assume the lines above begins with the line numbers in rule - but it's a bit weird, because this rule in the v3.0/master starts in line 788.

there is no tag: paranoia-level

yes, we still found rules without PL tags. That's a bug, and any reports are very welcome.

so how to manage this rule, and how to find out on which paranoia-level will be activated if there is no tag?

you can find the previous and next control rule, eg:
25   SecRule TX:PARANOIA_LEVEL "@lt 1" "phase:1,id:920011,nolog,pass,skipAfter:END-REQUEST-920-PROTOCOL-ENFORCEMENT"
26   SecRule TX:PARANOIA_LEVEL "@lt 1" "phase:2,id:920012,nolog,pass,skipAfter:END-REQUEST-920-PROTOCOL-ENFORCEMENT"

and
1440 SecRule TX:PARANOIA_LEVEL "@lt 2" "phase:1,id:920013,nolog,pass,skipAfter:END-REQUEST-920-PROTOCOL-ENFORCEMENT"
1441 SecRule TX:PARANOIA_LEVEL "@lt 2" "phase:2,id:920014,nolog,pass,skipAfter:END-REQUEST-920-PROTOCOL-ENFORCEMENT"

Because this rule are before the skipAfter action in case of @lt 2, it means this rule activated on PL 1.

how to activate this rule in another global paranoia-level for example 2?

CRS PL follows the logic, that every rule activated which is on less or equal PL what you choose. Eg. if your PL is 4, then it means all rules are active.

sorry but I still can not find the issue where I can put my question (besides Google groups, but it looks dead)

here you can find some more info. I think Google groups is alive.
But if you think this behavior is a bug, open an issue here.

The packages from the RedHat repo are a little bit old, so I copy .conf, .data and crs-setup.conf from the
https://github.com/coreruleset/coreruleset/archive/v3.3.0.tar.gz
 718 SecRule REQUEST_HEADERS:Host "@rx ^[\d.:]+$" \  719     "id:920350,\  720     phase:2,\  721     block,\  722     t:none,\  723     msg:'Host header is a numeric IP address',\  724     logdata:'%{MATCHED_VAR}',\  725     tag:'application-multi',\  726     tag:'language-multi',\  727     tag:'platform-multi',\  728     tag:'attack-protocol',\  729     tag:'paranoia-level/1',\  730     tag:'OWASP_CRS',\  731     tag:'capec/1000/210/272',\  732     tag:'PCI/6.5.10',\  733     ver:'OWASP_CRS/3.3.0',\  734     severity:'WARNING',\  735     setvar:'tx.anomaly_score_pl1=+%{tx.warning_anomaly_score}'"
But it is worse, when I set PL=4 in crs-setup.conf
176 SecAction \ 177   "id:900000,\ 178    phase:1,\ 179    nolog,\ 180    pass,\ 181    t:none,\ 182    setvar:tx.paranoia_level=4"
I get only warning without real bloc:
[Tue Oct 06 20:42:29.971059 2020] [:error] [pid 22536:tid<PHONE_NUMBER>70848] [client <IP_ADDRESS>:60947] [client <IP_ADDRESS>] ModSecurity: Warning. Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/httpd/modsecurity.d/github_rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "735"] [id "920350"] [msg "Host header is a numeric IP address"] [data "<IP_ADDRESS>"] [severity "WARNING"] [ver "OWASP_CRS/3.3.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/210/272"] [tag "PCI/6.5.10"] [hostname "<IP_ADDRESS>"] [uri "/api/settings"] [unique_id "X3y6lfFXDXTXMQ@BGmJDZAAAAFI"], referer: https://<IP_ADDRESS>/login

hi @askifyouneed,

But it is worse, when I set PL=4 in crs-setup.conf
176 SecAction \ 177 "id:900000,\ 178 phase:1,\ 179 nolog,\ 180 pass,\ 181 t:none,\ 182 setvar:tx.paranoia_level=4"

this is correct,

I get only warning without real block:
[Tue Oct 06 20:42:29.971059 2020] [:error] [pid 22536:tid<PHONE_NUMBER>70848] [client <IP_ADDRESS>:60947] [client <IP_ADDRESS>] ModSecurity: Warning. Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/httpd/modsecurity.d/github_rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "735"] [id "920350"] [msg "Host header is a numeric IP address"] [data "<IP_ADDRESS>"] [severity "WARNING"] [ver "OWASP_CRS/3.3.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/210/272"] [tag "PCI/6.5.10"] [hostname "<IP_ADDRESS>"] [uri "/api/settings"] [unique_id "X3y6lfFXDXTXMQ@BGmJDZAAAAFI"], referer: https://<IP_ADDRESS>/login

Please check your SecRuleEngine setting in your modsecurity.conf file.

  1 <IfModule mod_security2.c>
  2     # Default recommended configuration
  3     SecRuleEngine On
  4     #SecRuleEngine DetectionOnly
  5     SecRequestBodyAccess On
  6     SecRule REQUEST_HEADERS:Content-Type "text/xml" \
  7          "id:'200000',phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=XML"
  8     SecRequestBodyLimit 13107200
  9     SecRequestBodyNoFilesLimit 131072
 10     SecRequestBodyInMemoryLimit 131072
 11     SecRequestBodyLimitAction Reject
 12     SecRule REQBODY_ERROR "!@eq 0" \
 13     "id:'200001', phase:2,t:none,log,deny,status:400,msg:'Failed to parse request body.',logdata:'%{reqbody_error_msg}',severity:2"
 14     SecRule MULTIPART_STRICT_ERROR "!@eq 0" \
 15     "id:'200002',phase:2,t:none,log,deny,status:400,msg:'Multipart request body \
 16     failed strict validation: \
 17     PE %{REQBODY_PROCESSOR_ERROR}, \
 18     BQ %{MULTIPART_BOUNDARY_QUOTED}, \
 19     BW %{MULTIPART_BOUNDARY_WHITESPACE}, \
 20     DB %{MULTIPART_DATA_BEFORE}, \
 21     DA %{MULTIPART_DATA_AFTER}, \
 22     HF %{MULTIPART_HEADER_FOLDING}, \
 23     LF %{MULTIPART_LF_LINE}, \
 24     SM %{MULTIPART_MISSING_SEMICOLON}, \
 25     IQ %{MULTIPART_INVALID_QUOTING}, \
 26     IP %{MULTIPART_INVALID_PART}, \
 27     IH %{MULTIPART_INVALID_HEADER_FOLDING}, \
 28     FL %{MULTIPART_FILE_LIMIT_EXCEEDED}'"
 29
 30     SecRule MULTIPART_UNMATCHED_BOUNDARY "!@eq 0" \
 31     "id:'200003',phase:2,t:none,log,deny,status:44,msg:'Multipart parser detected a possible unmatched boundary.'"
 32
 33     SecPcreMatchLimit 1000
 34     SecPcreMatchLimitRecursion 1000
 35
 36     SecRule TX:/^MSC_/ "!@streq 0" \
 37             "id:'200004',phase:2,t:none,deny,msg:'ModSecurity internal error flagged: %{MATCHED_VAR_NAME}'"
 38
 39     SecResponseBodyAccess Off
 40     SecDebugLog /var/log/httpd/modsec_debug.log
 41     SecDebugLogLevel 0
 42     SecAuditEngine RelevantOnly
 43     SecAuditLogRelevantStatus "^(?:5|4(?!04))"
 44     SecAuditLogParts ABIJDEFHZ
 45     SecAuditLogType Serial
 46     SecAuditLog /var/log/httpd/modsec_audit.log
 47     SecArgumentSeparator &
 48     SecCookieFormat 0
 49     SecTmpDir /var/lib/mod_security
 50     SecDataDir /var/lib/mod_security
 51
 52     # ModSecurity Core Rules Set and Local configuration
 53     IncludeOptional modsecurity.d/*.conf
 54     IncludeOptional modsecurity.d/github_rules/*.conf
 55     IncludeOptional modsecurity.d/local_rules/*.conf
 56
 57 </IfModule>

I think this happens because the rule 920350 has the block action, which performs the disruptive action defined in SecDefaultAction here. If you just simple downloaded the default config files, then it's pass.

Sorry but I do not understand. In my opinion it should be blocked despite these lines in crs-setup.conf?
 96 SecDefaultAction "phase:1,log,auditlog,pass"
 97 SecDefaultAction "phase:2,log,auditlog,pass"

In my opinion it should be blocked despite these lines in crs-setup.conf?

I think no. Please read how block action works.

I delighted to see that knowledgement is built atop of this discuss, and @askifyouneed is mitigating doubts. Perhaps you want to move this subject to a more adequate place such as the CRS GitHub issues. There you will be able to address it better. Thank you.

@zimmerle of course you are right, the problem is that there is no place where these questions could be set.
If you point me the right link I will move the discussion to this place :)


Smart Select Layout become mess when inside in a accordion

I am using smart select and If I put it in a accordion the tile and selected values become display block

Issue is closed because of outdated/irrelevant/not actual
If this issue is still actual and reproducible for latest version of Framework7, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


#653

Fix cursor bounding rect for glyph, which cause some drawing artifacts.

This PR fix this artifact

Thanks for the PR. Can you explain a little how you fixed it?
This is just for my study. I mean I didn't know how to fix the problem I described in the code (edge caret drawing problem). I think you solved it by using NSIntegralRectWithOptions. What's the background of the problem? Why we have to use this to fix it?

Hello.
So the problem was that rect was not normalize (NSIntegralRectWithOptions) and when we draw rect with fractional part as .33333 have such artifacts.
As I remember rect should be 0, 0.5 or 1 and on retina maybe another side affect with .33333.
When we normalize rect such huck as
s_lastCaret.origin.x -= 10.0;
s_lastCaret.size.width += 20.0;
not necessary.
But I can't fix problem when editing in scope


Contact us form embedded in parent dash footer

Description
This pull request relates to the implementation of the contact us form that will be embedded in the footer of the parent dashboard. It will also have a section for users to sign up to a newsletter and to access social media accounts. CSS grid was used for the styling of the footer - this allows for maximum responsivity on all view-ports.
Further PR's will be made to implement functionality, testing & responsive design.

Fixes #

What work was done?
-built out reusable footer component
Why was this work done?
allow the user to contact the company
What feature / user story is it for?
As a user I would like a form that allows me to contact staff at Story Squad.
Any relevant links or images / screenshots

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[x] Incomplete/work-in-progress, PR is for discussion/feedback

Has This Been Tested

[ ] Yes
[x] No
[ ] Not necessary

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

Unused iteration


Typo in hello example, OpenGL 4.10 doesn't exist (yet)

There seems to be a typo in the hello example main.rs, when creating an OpenGL context the minor version referenced is "10", but alas, OpenGL 4.10 does not exist (yet).
https://github.com/grovesNL/glow/blob/c6e96041c024445ca5fba8cd749fad8d8752db7a/examples/hello/src/main.rs#L69

Ah yeah that should be 1, looks like it was change while upgrading glutin. Feel free to submit a PR if you'd like!

Fixed by #298


[Windows] Cannot fetch metadata when using GCE cloud provider

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Prepare 1 Linux Ubuntu 18.04 and 1 Windows 2019
Set up a cluster with GCE cloud provider:cloud_provider:
  name: gce
  customCloudProvider: |-
    [Global]
    project-id=<your projcet ID, optional>
    network-name=<your network, optional if using default network>
    subnetwork-name=<your subnetwork of the above network, optional if using default network>
    node-instance-prefix=<your instance group name/your instance name specific prefix>
    node-tags=<your network tags, optional if not patching any tags>
services:
  kube-controller:
    extra_args:
      configure-cloud-routes: true

Add a Linux control plane + etcd + worker node
Add a Windows node
Log in Windows node, exec powershell:

> cd c:\var\log
> get-content kubelet.log -tail 2 -wait

Result:
So many repeated errors as below:

Other details that may be helpful:
After patching <IP_ADDRESS>/32 route back, the error logs gone.

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master
Installation option (single install/HA): single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version): 1.14.1

Verified on rancher:2.3.0-alpha3

Set up a GCE cloud provider cluster with:

cloud_provider:
  name: gce
services:
  kube-controller:
    extra_args:
      configure-cloud-routes: true

Register a linux node - all roles -Ubuntu 18.04.
The cluster comes up active but the node is seen in Active state with error Node created without a route
Register a Windows 2019 node - worker.
The node gets registered successfully.

Please follow this pattern:
cloud_provider:
  name: gce
  customCloudProvider: |-
    [Global]
    project-id=<your projcet ID, optional>
    network-name=<your network, optional if using default network>
    subnetwork-name=<your subnetwork of the above network, optional if using default network>
    node-instance-prefix=<your instance group name/your instance name specific prefix>
    node-tags=<your network tags, optional if not patching any tags>
services:
  kube-controller:
    extra_args:
      configure-cloud-routes: true

Only node-instance-prefix is required. However, if you configure a specifical VPC, you have better to specify it in network-name. The node-tags allows you to separate different clusters in one VPC.

reproduced the issue on rancher:2.3.0alpha3
validated this issue in rancher:master - 06/12/2019

Set up a gce cloud provider cluster
Register one linux node - Ubuntu 18.04. - all roles
Register one windows 2019 - node -worker
Log in Windows node, exec powershell:

> cd c:\var\log
> get-content kubelet.log -tail 2 -wait

No errors seen in the logs
IP route for  <IP_ADDRESS>  is seen in the route table


Proving bug with Deep nested many_many relations

When adding a filter to a many_many with a shared inheritance, the FROM table is removed and added as a LEFT JOIN which causes a syntax error.
This means $dataList->filter('ManyManyRel.ID', array(1,2)) doesn't work.

Ok, So I've fixed an issue where the FROM clause was removed from the DataQuery.
There remains a problem with the actual filter due to the collision of the table names and thus the WHERE clause in the query is ambiguous and doesn't filter on the link table (where I feel it should) and instead filters on the joined table (which is a collision with the FROM table).

@tractorcow I'd like you're thoughts on whether your ORM work will have fixed this problem?

I doubt it, I don't think I've tested this specific use case.

1) DataObjectTest::testBelongsTo
Couldn't run query:
INSERT INTO "DataObjectTest_Company" ("Created") VALUES (NOW())
Table 'ss_tmpdb2069596.DataObjectTest_Company' doesn't exist

You need to ensure you add any class with TestOnly interface to extraDataObjects variable.

thanks @tractorcow added that and now looks like the real reason for failing is happening

Did you want to fix these tests? :D I think this should be merged soon.

Ok, the tests aren't broken, it's the core itself.
For some reason the query builder is joining on the wrong column for the link table.

@dhensby any enthusiasm for remedying whatever is broken in these?

Yep, is a pretty serious bug, it's all about time for  free at the moment... :(

This API has changed a lot in later branches... you probably don't want to leave this too long before the branches diverge. :P
I would close and re-open on 3.3 if I were you.

Just ran into this one, nasty 😢 . Don’t suppose you’ve had a chance to look at this yet @dhensby?

I've gone and refreshed my memory with this issue. There are two problems here which I've now resolved, though perhaps not completely and in a very hacky and non-semver way.

Empty FROM clause when joining to the same table as the base table.

I think this has been resolved, though @kinglozzer doesn't seem to agree. Because DataQuery stores the joins and FROM clauses in the same keyed array, a join would just override the from and it'd be empty. This is fixed by checking that the table isn't already "joined" before adding the join.

Self referencing relations fail

If you have a relationship between the same ancestor classes (eg: SomePage many-many SomeOtherPage) it will select base columns from SiteTree, try to join SiteTree again (but doesn't because of fix above) and then does a WHERE on SiteTree.
The generated SQL for SomePage::get()->filter('RelatedPages', array(1,2,3)); is something like:
SELECT "SiteTree".*
FROM "SiteTree"
INNER JOIN "SomePage_RelatedPages" ON "SomePage_RelatedPages"."SomePageID" = "SiteTree"."ID"
WHERE "SiteTree"."ID" IN (1,2,3) AND "SiteTree"."ClassName" = 'SomePage';

This fails to return results as the join is not done properly and should be something closer to:
SELECT "SomePage".*
FROM "SiteTree" AS "SomePage"
INNER JOIN "SomePage_RelatedPages" ON "SomePage_RelatedPages"."SomePageID" = "SomePage"."ID"
INNER JOIN "SiteTree" AS "RelatedPage" ON "SomePage_RelatedPages"."RelatedPageID" = "RelatedPage"."ID"
WHERE "RelatedPage"."ID" IN (1,2,3) AND "SomePage"."ClassName" = 'SomePage'

This is a difficult problem to solve as the SearchFilter needs knowledge that the relation has a common inheritance and the where clause will have been aliased out.


agent try to join mesh, but the save button is disable

The test environment is as follows：
Ubuntu 22.04
pipy version:

Operating procedures：

Clone the pipy and ztm.
Install pipy.
Intall ztm gui.
Start the ca, hub and agent respectively according to the README.md.
Open the agent website and try to join mesh.
Cannot click the save button.

Hi,
Thanks for your update.
It's an UI issue. Once you entered the Hub's address, you need to press 'Enter' key to finishing the input.
Sorry for bothering.
Enjoy it!
Cheers!

thanks


Check coverage

[ ] Tests added / passed
[ ] Passes flake8 dask

Codecov Report

Merging #2 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master      #2      +/-   ##
=========================================
- Coverage   91.11%   91.1%   -0.01%
=========================================
  Files          92      92
  Lines       17128   17128
=========================================
- Hits        15606   15605       -1
- Misses       1522    1523       +1

Impacted Files
Coverage Δ

dask/bytes/http.py
73.33% <0%> (-0.61%)
:arrow_down:

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 49d5520...de9dbc2. Read the comment docs.


Script is not running well

i try to run the script via powershell and powershell v7 and it not working please fix it :-)

which one of the tool is not working?

Manage folder premission gui
בתאריך יום ב׳, 26 ביולי 2021, 15:50, מאת Agustin Gallegos [MSFT] <
@.***>:

which one of the tool is not working?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/agallego-css/tools/issues/1#issuecomment-886674067,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3U7CWWDW4OYUCQ6Q72UTDTZVKZVANCNFSM5A72PBUA
.

Done. it is working for me now on PS 5.1
it is expected to fail in PS7.
please retry and let me know

how did you run it i try with right click and run with powershell
בתאריך יום ג׳, 27 ביולי 2021 ב-16:31 מאת Agustin Gallegos [MSFT] <
@.***>:

Closed #1 https://github.com/agallego-css/tools/issues/1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/agallego-css/tools/issues/1#event-5074347726, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3U7CRGMQZEFLRH454WZMLTZ2YM5ANCNFSM5A72PBUA
.

download the PS1 from https://raw.githubusercontent.com/agallego-css/tools/master/Manage-FolderPermissions-gui/Manage-FolderPermissionsGUI.ps1
and execute from Windows Powershell:
PS C:\> .\Manage-FolderPermissionsGUI.ps1

[image: image.png]
בתאריך יום ג׳, 27 ביולי 2021 ב-20:28 מאת Agustin Gallegos [MSFT] <
@.***>:

download the PS1 from
https://raw.githubusercontent.com/agallego-css/tools/master/Manage-FolderPermissions-gui/Manage-FolderPermissionsGUI.ps1
and execute from Windows Powershell:
PS C:> .\Manage-FolderPermissionsGUI.ps1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/agallego-css/tools/issues/1#issuecomment-887695797,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3U7CQNBACEQOWNS6MZPGTTZ3UCNANCNFSM5A72PBUA
.

can't see the image.

[image: image.png]
בתאריך יום ד׳, 28 ביולי 2021 ב-14:09 מאת Agustin Gallegos [MSFT] <
@.***>:

can't see the image.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/agallego-css/tools/issues/1#issuecomment-888223598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3U7CWJIJVYSYWMDPFBGBTTZ7QO5ANCNFSM5A72PBUA
.

still not seeing the image attach.
please describe the error you have.

https://www8.zippyshare.com/v/xCOcH2Ew/file.html
בתאריך יום ד׳, 28 ביולי 2021 ב-17:15 מאת Agustin Gallegos [MSFT] <
@.***>:

still not seeing the image attach.
please describe the error you have.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/agallego-css/tools/issues/1#issuecomment-888344900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3U7CQ5ALP3IDIGINR7X5DT2AGGNANCNFSM5A72PBUA
.

you are downloading the file incorrectly.
access the raw content here: https://raw.githubusercontent.com/agallego-css/tools/master/Manage-FolderPermissions-gui/Manage-FolderPermissionsGUI.ps1
copy and save the text in a new notepad file, later save it as .ps1.
then it should run just fine.

Thanks I just make right click on the github file and save the url and download the powershell ps1 file
I will try it
Maybe you have more great tools that I could use ?
From: Agustin Gallegos [MSFT] @.>
Sent: Thursday, July 29, 2021 5:58 PM
To: agallego-css/tools @.>
Cc: galhalperin1 @.>; Author @.>
Subject: Re: [agallego-css/tools] Script is not running well (#1)
you are downloading the file incorrectly.
access the raw content here: https://raw.githubusercontent.com/agallego-css/tools/master/Manage-FolderPermissions-gui/Manage-FolderPermissionsGUI.ps1
copy and save the text in a new notepad file, later save it as .ps1.
then it should run just fine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/agallego-css/tools/issues/1#issuecomment-889217676 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AI3U7CVAKH775SV7UNZLUVTT2FT7RANCNFSM5A72PBUA .  https://github.com/notifications/beacon/AI3U7CXYNJUIIPBAL4S4EK3T2FT7RA5CNFSM5A72PBUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGUAGFDA.gif

feel free to check my repositories. all my public tools are there.

dear agustin there is an option for you to make script for gui interface
for delegation ?
it will be very helpful :-)
[image: image.png]
https://github.com/MicrosoftDocs/office-docs-powershell/issues/6327
בתאריך יום ו׳, 30 ביולי 2021 ב-20:22 מאת Agustin Gallegos [MSFT] <
@.***>:

feel free to check my repositories. all my public tools are there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/agallego-css/tools/issues/1#issuecomment-890040745,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3U7CRZAMDN6JXJHWIHKZ3T2LNWNANCNFSM5A72PBUA
.


capture user inputs on first version of main interface

One part core functionality is that this site must generate an autograder.zip file based on the following inputs for any given assignment. This .zip file is what the instructor needs to upload to gradescope. Right now, we just need to write code that accepts all of these inputs. Don’t worry about doing anything with the inputs yet, or with providing output.
Inputs

[x] Name of the assignment submission expected from students (e.g. homework1.R)
[x] List of extra packages they want to authorize students to use (e.g. tidyverse, MASS)
[ ] external .csv file data sets (variable number)
[x] variable number of logical expressions that the instructor expects to be true (e.g. myData[1,1] == 6), along with an associated name of the test, and whether its truth value should be visible to students before the deadline has passed
[x] (optional) an instructor can provide a my_tests.R file with logical expressions written

Extra thoughts:

Some of these items imply a "dynamic user interface". For example, we do not know ahead of time how many tests an instructor wants to upload. We need to allow a user to increase the number of tests at will. Same goes for .csv uploads.
Let's not worry about what to do with these inputs yet. I will probably get involved with this after the inputs have been defined.
Let's not worry about downloads or returning the zip file yet, either.

Few more comments/questions about the inputs:

name of the assignment submission is just a simple string not a file (e.g. homework1.R) Maybe use something like textInput() instead of fileInput()
list of extra packages could be a single string, separated by commas, and then we can separate/parse it later
external .csv file data sets are still file uploads, but there are a varying number of them. How can we add a variable amount of fileInputs?
Same goes for the logical expressions that the instructor expects to be true (e.g. myData[1,1] == 6). How do we add a varying number of these? These are text inputs though, n ot file inputs.
names and visibility settings are coupled with the above logical expressions. So whenever we add a new logical test window entry, we need to add a corresponding one for the name of ht etest, and corresponding varSelectInput() to choose whether it's hidden or visible.
(optional) an instructor can provide a my_tests.R file with logical expressions written. I'm not sure how we should handle this. If the instructor provides a file, we should hide all of the above buttons and text inputs that create the tests. This sounds complicated so maybe we should hold off on this part

I would say for 3. we can add multiple = FALSE in fileInputs to allow users to upload multiple csv files at the same time.

Let's get rid of the last checkpoint: "(optional) an instructor can provide a my_tests.R file with logical expressions written."
That leaves only one remaining checkpoint: "external .csv file data sets (variable number)"

Regarding "external .csv file data sets (variable number)". The current implementation does support multiple data sets. It is just unintuitive because the user has to hold control or command when selecting more than one data set. We can instead change this to be more like tests where there is a button to add/remove datasets.
For the TODO: It may not be an issue, but currently the code generates the intermediate files (setup.sh, run_autograder, etc.) and puts them in the directory with the other code. This probably is not the best behavior because if multiple users use the app at the same time, there could be weird issues with overwriting files before one user is done with them. I'm not sure what the ideal solution would be, but in-memory files would ensure that no files are being created on the server itself. Tempfiles that can be deleted as soon as they are not needed would work as well, but I still need to learn how to implement it in R.

Didn’t even notice the multiple file uploads. Woops.
regarding second point, maybe just throw an unlink() in there. https://community.rstudio.com/t/delete-temp-files-in-shiny/20473
R has some temp file stuff but it might not be suitable. The tempfile function creates files with random names, but our names need to be specific. There’s a tempdir function but cleanup happens when R session terminates.

I think the modules broke the removeTests button. Haven't quite been able to figure it out yet. Otherwise I think this issue is a wrap


After pushing to another node, namespace is gone

It seems like in the tests after pushing to remote:
		citools.RunOnNode(t, aliceNode.Container, citools.DockerRun("apples")+" touch /foo/alice")
		citools.RunOnNode(t, aliceNode.Container, "dm switch apples")
		citools.RunOnNode(t, aliceNode.Container, "dm commit -m'Alice commits'")
		citools.RunOnNode(t, aliceNode.Container, "dm push cluster_0 apples --remote-name alice/apples")

		citools.RunOnNode(t, bobNode.Container, citools.DockerRun("apples")+" touch /foo/bob")
		citools.RunOnNode(t, bobNode.Container, "dm switch apples")
		citools.RunOnNode(t, bobNode.Container, "dm commit -m'Bob commits'")
		citools.RunOnNode(t, bobNode.Container, "dm push cluster_0 apples --remote-name bob/apples")

Namespace is removed.
dm list output on nodes:
➜  dotmesh git:(test-failures) ✗ ./scripts/dex 0 0
root@cluster-20236966069537980-0-node-0:/# dm list
Current remote: local (use 'dm remote -v' to list and 'dm remote switch' to switch)

  DOT           BRANCH  SERVER           CONTAINERS  SIZE       COMMITS  DIRTY
  alice/apples  master  298aec48b752bb2              25.00 kiB  1        -
  bob/apples    master  298aec48b752bb2              38.00 kiB  2        -
root@cluster-20236966069537980-0-node-0:/# exit
➜  dotmesh git:(test-failures) ✗ ./scripts/dex 2 0
root@cluster-20236966069537980-2-node-0:/# dm list
Current remote: local (use 'dm remote -v' to list and 'dm remote switch' to switch)

  DOT                 BRANCH  SERVER            CONTAINERS  SIZE       COMMITS  DIRTY
  admin/alice-apples  master  7111ccb66e301f95              25.00 kiB  1        -
* admin/apples        master  7111ccb66e301f95              38.00 kiB  2        -
root@cluster-20236966069537980-2-node-0:/# exit
➜  dotmesh git:(test-failures) ✗ ./scripts/dex 1 0
root@cluster-20236966069537980-1-node-0:/# dm list
Current remote: local (use 'dm remote -v' to list and 'dm remote switch' to switch)

  DOT               BRANCH  SERVER            CONTAINERS  SIZE       COMMITS  DIRTY
* admin/apples      master  99fd6b689d581b35              25.00 kiB  1        -
  admin/bob-apples  master  99fd6b689d581b35              38.00 kiB  2        -

Issue was due to refactoring of types, we were accidentally using the server's String() method on VolumeName that always gives the namespace; there's a StringWithoutAdmin() method for use in the UI.

That change seemed to fix it.


Possibility to differentiate between invalid VAT and unsupported country?

Is there a possibility to know if VAT validation for specific country is supported?
We have a use case where customer submits WEB form with his name, address and VAT number etc and we should be able to validate at minimum EU VAT numbers.
Now this library works great as long as the customer is from supported countries.
If the customer is for example from Canada or India and enters their local VAT Id, response is similar as it would be for invalid VAT.
Yes I could build hard-coded list of country ISO codes and then validate VAT only for the supported ones but it would be more future proof if I could get the list of supported country ISO codes from lib or if validation response could somehow differentiate between unsupported country / invalid VAT?

You can get the list of ISO codes from the lib by taking always the first argument of the codes array on countries (wich is the  ISO 3166-1 alpha-2 (2 letters) country code) apart from greece who uses the ISO 639-1 language code (EL) that you need to do by hand (see https://www.wikiwand.com/en/VAT_identification_number)

example

this will be possible soon. In 2.3.0 via isSupportedCountry field of the result


[V3] [3.0.2] Vimeo shows controls in fullscreen on mobile when height > 2xwidth

Newer devices have a high height and the vimeo-fix with the 200% solution does not work anymore.
Let's increase it to 300% :)
// Set aspect ratio
        // For Vimeo we have an extra 300% height <div> to hide the standard controls and UI
        setAspectRatio: function setAspectRatio(input) {
            var ratio = utils.is.string(input) ? input.split(':') : this.config.ratio.split(':');
            var padding = 100 / ratio[0] * ratio[1];
            var height = 300; <- Update
            var offset = (height - padding) / (height / 50);
            this.elements.wrapper.style.paddingBottom = padding + '%';
            this.media.style.transform = 'translateY(-' + offset + '%)';
        },

.plyr__video-embed {
    // Default to 16:9 ratio but this is set by JavaScript based on config
    $padding: ((100 / 16) * 9);
    $height: 300; <- Update
    $offset: to-percentage(($height - $padding) / ($height / 50));

After this changes, it looks good again:

I'm not sure what can be done about this. I settled on 200% as otherwise the Vimeo captions start appearing in the video and I'm not sure how to turn off their rendering.

Will try 240 and see if that helps with your screen size?


Reading Efforts and Velocities in Gripper node

Hello,
I wanted to read grasping forces of the gripper, but the franka_gripper_node publishes a state topic with gripper-joints efforts and velocities set to zero.
https://github.com/frankaemika/franka_ros/blob/41a3c7808b1a141a242a1258cbdbfebc76ae2a7a/franka_visualization/src/gripper_joint_state_publisher.cpp#L44
Can you clarify what is going on here ? Is there a way to read gripper efforts with franka_ros or libfranka ?
Thanks

Why is gripper velocity and effort always zero?
I am trying to read the velocity of the gripper of Franka Emika Panda in the real-world. However, I always get the gripper velocity and effort to be zero. I get correct values for gripper velocity and effort when I use the Panda in Gazebo simulation.
I get correct values for other joints in Gazebo as well as for real-world Panda.
Could anyone please help me out? I don't understand what could be going wrong.
Thank you!


Pre-bundled dependencies doesn't dedupe imports in external files

Describe the bug

When Vite pre-bundles a dependency, if the dependency's entrypoint file imports an external file (e.g. Foo.svelte), imports in that external file aren't deduped.
For example, given foo-library in node_modules with these files:
// shared.js
export const bar = {}

<!-- Component.vue -->
<script>
import { bar } from './shared' // pay attention
</script>

// index.js
export { bar } from './shared'
export { default as Component } from ',/Component.vue`

Vite will prebundle foo-library as .vite/foo-library.js:
// foo-library.js
export const bar = {}
export { default as Component } from<EMAIL_ADDRESS>
^ This is the problem, Component.vue will import bar from it's relative './shared.js file, but .vite/foo-library.js has its own bar reference! This causes a lot of hard to catch bugs, especially for the Svelte ecosystem.

Reproduction

https://github.com/bluwy/vite-svelte-dedupe
(It's a Svelte-specific repro but the general issue applies)
System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: Linux 5.8 Ubuntu 20.10 (Groovy Gorilla)
    CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
    Memory: 4.49 GB / 11.59 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 14.15.5 - ~/.nvm/versions/node/v14.15.5/bin/node
    Yarn: 1.22.5 - ~/.yarn/bin/yarn
    npm: 7.17.0 - ~/.nvm/versions/node/v14.15.5/bin/npm
    Watchman: 20210207.192227.0 - /usr/local/bin/watchman
  Browsers:
    Chromium: 91.0.4472.114
    Firefox: 89.0.1
  npmPackages:
    vite: ^2.3.8 => 2.3.8

Used package manager:  pnpm

Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Looking back at this, perhaps the best short-term solution for now is to not prebundle any dependencies/packages that has uncompiled files that contains JS. Basically these items:
https://github.com/vitejs/vite/blob/69f91a1c03a129ab324c20fddfd2a07e729add96/packages/vite/src/node/optimizer/esbuildDepPlugin.ts#L24-L31
These extensions would all technically fail, with un-deduped imports, so it's better to not do any prebundling for libraries that exports these "raw" uncompiled files.

Currently for svelte, a heuristic (package.svelte) can be used to detect when add a library to optimizeDeps.exclude. https://github.com/sveltejs/vite-plugin-svelte/issues/125 may add this soon. This heuristic is also currently used in SvelteKit to add to ssr.noExternal which makes sense for uncompiled files.
However, the above isn't bullet-proof. It's best-effort only and may break depending on how one set up a project. Plus, this works for Svelte only. There's no equivalent heuristic for Vue or marko. So a built-in solution may be the best as proposed above.

To add on how snowpack/esinstall handles this, it currently bundles external files in the prebundling process as well, leading to one single bundle always.
There's of course some issues with this:

We need to re-prebundle whenever the config changes. (Currently snowpack doesn't do this so prebundled bundles would get stale unless explicitly prebundled, feels like a bug)
We actually need to generate two bundles, for SSR and non-SSR. Since Svelte generates different JS for these two environments.
Tricky to be adopted by Vite since Vite's prebundling is done by esbuild, and Vite plugins are written in rollup object format.

Here's also a discussion from snowpack: https://github.com/snowpackjs/snowpack/discussions/1808#discussioncomment-146930

This is a far more severe issue than just ending up with duplicate imports. It also means that CJS dependencies don't work. Since the imports aren't updated in .svelte files they remain pointing at the CJS version instead of the pre-bundled ESM version which means packages with non-JS files such as .svelte, .marko, etc. break when they have CJS dependencies.

From some discussion lately in discord and https://github.com/sveltejs/vite-plugin-svelte/issues/125, it looks that force excluding svelte (and probably marko, solid) libraries would be the way to go, there's no one compiled output for them so they can't really be pre-bundled ahead of time.
Issue
The issue now is that as @benmccann pointed out, CJS dependencies used by these excluded libraries (aka transitive CJS deps) wouldn't work in Vite, since Vite doesn't handle CJS in runtime, it expects everything to be in ESM already after prebundling, which is not the case for us. So to fix this, we have two ways:

Also optimize transitive CJS deps. This makes sure that the excluded library will use ESM code from its dependencies too, essentially eliminating any CJS code imported Vite dev server.

Problem: This would be a breaking change for pnpm users unless they set shamefully-hoist=true or explicitly install the transitive CJS deps into the root project. This is because Vite's optimizer would look for optimized libraries under /node_modules/ only, unless if it's updated to look in nested node_modules and properly duped if needed when two excluded libraries use the same library of different major versions.

Handle CJS in vite dev server. So it loads the transitive CJS deps without issues.

Problem: Could slow down dev server? (And probably more reasons I've not thought of)

Solution
An idea in mind is to work on no1, by altering the prebundling process to address the listed problem above. The altered flow should be like below:

For normal pure JS libraries, prebundle as usual.
For svelte, marko, solid (and even vue) libraries, vite will auto-exclude from optimization by default, but it'll continue to scan for imports within the library.
From the scan, for any imports found, vite will prebundle it as /node_modules/.vite/svelte-library__nested-cjs-dep.js. And make sure the library is resolved through /node_modules/svelte-library/node_modules/nested-cjs-dep, not /node_modules/nested-cjs-dep.
Import analysis should correct the imports in the excluded library to use the prebundled file (/node_modules/.vite/svelte-library__nested-cjs-dep.js).

In my mind, if I'm not missing out on anything, this would work nicely with X framework libraries OOTB.
FAQ
Q: How do we differentiate pure JS libraries vs X framework libraries?
A: The most robust heuristic is to check if that library has .svelte or .marko components, but that's unneededly taxing on pure JS libraries. Otherwise a more lax heuristic is to check package.json for "svelte", "marko", "solid-js" dependencies (credit to @dominikg for the idea)

If anyone has stumbled on this and wants a workaround, exclude the dependency from optimization, e.g. optimizeDeps.exclude: ['the-library']. However, it could cause a side effect of #3024, if that dependency imports a CJS library. To fix this there's a pending PR #4634 that will allow us to optimize that nested CJS library, by specifying it like optimizeDeps.include: ['the-library > cjs-library']. Please try the pending PR out to make sure it works!

There's now an experimental option to prebundle .svelte files: https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/config.md#prebundlesveltelibraries

Hi, not sure this is related but I have a similar issue.
I’m using React 17 and use lazy-loaded routes. The issue is happening with a font awesome SVG icon.
I have two lazy-loaded routes where I use the icon in the same way:
import { faCircleQuestion } from '@fortawesome/free-solid-svg-icons/faCircleQuestion'
import { FontAwesomeIcon } from '@fortawesome/react-fontawesome'

// ...

<FontAwesomeIcon icon={faCircleQuestion} />

If I first go to route A, the icon works. If I first go to route B, the icon doesn’t work. But, if I first go to route A, then route B, the icon works!
I looked at the code generated after building the app, and I can see this in route B’s JS files:
/* file1.js */
// ...

var oe = P
  , le = {}
  , T = y
  , N = function() {
    try {
        var n = T(Object, "defineProperty");
        return n({}, "", {}),
        n
    } catch {}
}()
  , d = N
  , u = d;

// ...

export {ie as D, oe as _, se as a, ve as b, ce as c, ue as d, le as f, fe as l};

/* file2.js */
import {D as sa, a as Ar, _ as ua, l as ca, d as fa, b as da, c as va, f as ma} from "./file1.js";

// ...

children: c(Xn, {
  icon: ma.faCircleQuestion
})

As you can see, file1.js creates a le variable containing an empty object and exports it as f. file2.js imports f as ma and then tries to use the faCircleQuestion property of ma. Since ma is an empty object, the icon definition is not passed to the FontAwesomeIcon component, and nothing renders.
I tried to add @fortawesome/free-solid-svg-icons in optimizeDeps.exclude field of my config, but nothing changed. The only way I was able to make it work on both routes first load was to import the definition property of the icon rather than its alias:
/* unbuilded code */
import { definition as faCircleQuestion } from '@fortawesome/free-solid-svg-icons/faCircleQuestion'
import { FontAwesomeIcon } from '@fortawesome/react-fontawesome'

// ...

/* file1.js */
// ...

var oe = A
  , N = {};
(function(e) {
    Object.defineProperty(e, "__esModule", {
        value: !0
    });
    var n = "fas"
      , a = "circle-question"
      , i = 512
      , r = 512
      , t = [62108, "question-circle"]
      , o = "f059"
      , l = "M256 0C114.6 0 0 114.6 0 256s114.6 256 256 256s256-114.6 256-256S397.4 0 256 0zM256 400c-18 0-32-14-32-32s13.1-32 32-32c17.1 0 32 14 32 32S273.1 400 256 400zM325.1 258L280 286V288c0 13-11 24-24 24S232 301 232 288V272c0-8 4-16 12-21l57-34C308 213 312 206 312 198C312 186 301.1 176 289.1 176h-51.1C225.1 176 216 186 216 198c0 13-11 24-24 24s-24-11-24-24C168 159 199 128 237.1 128h51.1C329 128 360 159 360 198C360 222 347 245 325.1 258z";
    e.definition = {
        prefix: n,
        iconName: a,
        icon: [i, r, t, o, l]
    },
    e.faCircleQuestion = e.definition,
    e.prefix = n,
    e.iconName = a,
    e.width = i,
    e.height = r,
    e.ligatures = t,
    e.unicode = o,
    e.svgPathData = l,
    e.aliases = t
}
)(N);

// ...

export {le as D, oe as _, ue as a, se as b, ve as c, ce as d, N as f, fe as l};

/* file2.js */

// content unchanged

This way, it works even if I first load route B, and still works when I first load route A.
I might add that this is not happening with development server, only when builded and served by a simple nginx server.

Is this problem solved, I have a similar problem
http://localhost:8082/<EMAIL_ADDRESS>
and
<EMAIL_ADDRESS>
The vite dev environment is packaged with two versions, which causes the configuration to be loaded separately, and the instance cannot be shared.
I have this problem in<EMAIL_ADDRESS>but upgrading to<EMAIL_ADDRESS>has not solved it.

@ZengTianShengZ this isn't fixed yet, but you can workaround by adding the dependency to optimizeDeps.exclude

Already spent a few weeks on my project fighting that bug. We are using vite + pnpm and a lot of third-party deps in our library, so the list of the includes is already like this:
optimizeDeps: {
  include: [
      "recharts"
      "prop-types",
      "react-is",
      "react-dom",
      "hoist-non-react-statics",
      "react/jsx-runtime",
      // Please add the icons you need here
      "@mui/icons-material/Search",
      "@mui/icons-material/ExpandMore",
      "@mui/icons-material/InfoOutlined",
      "@mui/icons-material/Info",
      "@mui/icons-material/ArrowUpwardOutlined",
      "@mui/icons-material/RemoveOutlined",
      "@mui/icons-material/PsychologyOutlined",
      "@mui/icons-material/MenuBookOutlined",
      "@mui/icons-material/GroupsOutlined",
      "@mui/icons-material/ScatterPlotOutlined",

      .....
  ]
}

The developers are super tired of adding each dependency one by one including each icon!
Do you have any advice on some bundler with a similar speed to replace Vite where it works out of the box without all those hacks?

I'm not sure this issue is related to what you're getting. You can check https://vitejs.dev/guide/dep-pre-bundling.html#monorepos-and-linked-dependencies if you're working in a monorepo.
Otherwise for your case in particular, perhaps you can try @mui/icons-material/* too.


Use Steam API to mark friend groups in player list

Using the API call http://api.steampowered.com/ISteamUser/GetFriendList/v0001/?key=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&steamid=76561197960435530&relationship=friend it's possible to get a list of friends to search through and find other players in the same match, and label them as a party.
This is useful to help figure out who is most likely preventing a cheater from being kicked or who else to keep an eye on after noticing a cheater.
Here is how I think this could look like in the tool:

Differently colored "party" icons for each party.
A possible enhancement to this feature would be to represent the "closeness" of the party members (# of friend bonds per # of players in the party) as the alpha value of their icon. Ex.; If there is a party of 5 players, but one of them is only friends with 2 others, the alpha value of his "party" icon would be 40%.
Something else that may be implemented but is more controversial is automatically marking a player's friends that are present in the match as suspect when said player is marked as a cheater. Maybe add this as a setting? Off by default?
Edit: I forgot to add that, of course, this only works if the player's profile has friends list set to public. However, while the cheater himself may not have a public friends list, the cheater friends are more likely to, making chains/groups of friends still likely to form. even though not every member has a public friends list. thanks @ClusterConsultant

This would only work if the friends list of the target profile is public. Relevant docs here

@ClusterConsultant
Was this added to the right milestone? I think it would fit better under 1.5 or 1.4. But maybe its just a question of it not being a very high priority compared to the stuff slated for those versions.

@ClusterConsultant
Was this added to the right milestone? I think it would fit better under 1.5 or 1.4. But maybe its just a question of it not being a very high priority compared to the stuff slated for those versions.

Tag update is semi feature frozen and this is less ui and more logic. I picked 1.6 since that will likely include other detection changes. If @PazerOP wants to throw it into 1.3, I have no objections. There is also the matter of trying to keep 1.3 a reasonable amount of time away

Tag update is semi feature frozen and this is less ui and more logic. I picked 1.6 since that will likely include other detection changes. If @PazerOP wants to throw it into 1.3, I have no objections. There is also the matter of trying to keep 1.3 a reasonable amount of time away


Adds Container Linux releases RSS Feed

Lots of people asking for this at https://github.com/coreos/bugs/issues/1020

Thank you very much for your contribution ❤


Unable to delete file:E:\AndroidStudio\MyHelloWorld\squidb-processor\build\libs\squidb-processor-1.0.1.jar

In my simple demo,

When i execute "Build---Clean Project" or "Build---Rebuild Project", there has a error: “Execution failed for task':squidb-processor:clean'.   >Unable to delete file:E:\AndroidStudio\MyHelloWorld\squidb-processor\build\libs\squidb-processor-1.0.1.jar”;
But When i execute "Run", there has no error, and it can work.

how to fix this problem？

Hmm I haven't seen this before. The path in that error message sounds a little odd though...perhaps something is off with the project structure? Can you describe how you're including squidb as a dependency and post the part of your build.gradle that declares it? Are you building from source or from jcenter artifacts?

ok, first please forgive my poor english!
my project is like this: First of all, i create a new project (named MyHelloWorld), and it can work.  Then, i execute "File---New
---Import Module..." to import "squidb" file to MyHelloWorld project.  In the same way, i import "squidb-annotations" and "squidb-processor" files to MyHelloWorld project.  Finally, i edit the app module's  build.gradle file.  For this file ,I just added some content copied from "squidb-sample" module's build.gradle file.
Before edit, the app module's build.gradle file  is showing below(all content):
apply plugin: 'com.android.application'
android {
compileSdkVersion 22
buildToolsVersion "23.0.0 rc3"
defaultConfig {
    applicationId "com.wochacha.myhelloworld"
    minSdkVersion 15
    targetSdkVersion 22
    versionCode 1
    versionName "1.0"
}
buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:appcompat-v7:22.1.1'
}

After edit, the app module's build.gradle file is showing below(all content):
buildscript {
repositories {
jcenter()
}
dependencies {
    classpath 'com.android.tools.build:gradle:1.2.3'
    classpath 'com.neenbedankt.gradle.plugins:android-apt:1.4'
}

}
repositories {
maven {
url "https://dl.bintray.com/yahoo/maven"
}
}
apply plugin: 'com.android.application'
apply plugin: 'com.neenbedankt.android-apt'
android {
compileSdkVersion 22
buildToolsVersion "23.0.0 rc3"
defaultConfig {
    applicationId "com.wochacha.myhelloworld"
    minSdkVersion 15
    targetSdkVersion 22
    versionCode 1
    versionName "1.0"
}
buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:appcompat-v7:22.1.1'
compile project(':squidb')
compile project(':squidb-annotations')
apt project(':squidb-processor')
compile 'javax.inject:javax.inject:1'
compile 'com.squareup.dagger:dagger:1.2.2'
apt 'com.squareup.dagger:dagger-compiler:1.2.2'

}
That's all my project. And you can try to create a new project like this to see if there has the same error.

Well, your project setup looks perfect to me. After a bit more googling, I think you may be running into this issue: https://code.google.com/p/android/issues/detail?id=61300, which appears to be an Android Studio bug of some kind. Can you try some of the suggestions towards the bottom of that thread about finding the process locking the file and killing it?

Thank you very much, it really works now!    I killed the process "java.exe", then execute "Rebuild Project" or "Clean Project", there has no error and it can work.  May be it's an Android Studio bug.
You are so great , thank you!

Awesome, glad to hear it's working now! Good to know that this Studio bug exists. I'm going to close the issue, but we'll keep an eye on things to see if a future version of Studio resolves the issue more permanently.

http://stackoverflow.com/questions/32914499/error-execution-failed-for-task-appclean-unable-to-delete-file
After I posted a bug report to the Kotlin bug tracker, I was notified of Issue 61300 on the AOSP tracker. That seems to be the cause. Since there's nothing I can do at the moment, I'll mark this question as answered, and I'll update the answer if the bug is fixed.
In the meantime, if you're running Windows, I believe I've found a workaround. You'll need to download LockHunter (at your own risk of course), then add the following to your module's gradle.build file, replacing the lockhunter variable with your path to LockHunter.exe:
task clean(type: Exec) {
ext.lockhunter = '"C:\LockHunter.exe"'
def buildDir = file(new File("build"))
commandLine 'cmd', "$lockhunter", '/delete', '/silent', buildDir
}
This causes LockHunter to forcefully and silently unlock and delete the build files when the app:clean task runs.


Feature/nikon delegates

Fixes #65 by adding to the default delegate.  I'll just PR this for now and if desired, we can discuss where it should live.  Tested with different orientations.

looks good. let me stick this into a feature branch and QA it for a while.

merged into: https://github.com/musselwhizzle/Focus-Points/tree/feature/nikon_live_view


Should  NAD+ (CHEBI:15846) be a purines (CHEBI:26401)?

Currently NAD salvage is not a child of purine-contatining compound salvage. We need contact ChEBI to ask whether NAD+ should be classified as a purine-containing compound (purines ChEBI:26401---A class of imidazopyrimidines that consists of purine and its substituted derivatives.). This categorization may be historical based on it originally being classified as a pyridine derivative. If so, NAD+ salvage (GO:0034355) will become a child of purine-containing compound salvage (this makes sense to us). If not, we can obsolete purine-containing compound salvage because it will no longer be necessary to group all the subclasses that we intend to keep.
pin @deustp01

Looking at the ChEBI ontology again, I now see that NAD+ is a nucleotide and a pyridine nucleotide. Should it also be a purine nucleotide? If so, we can propose to obsolete 'purine-contatining compound salvage' because the only classes left after this clean-up will be purine nucleotides.

Submitted request through CHEBI issue tracker.

Not yet resolved in ChEBI

Should be fixed in the Sept 1 ChEBI release

Replaced NAD with NAD+
However, CHEBI has not been updated for this be child of purine yet.

CHEBI needs to make NAD(1-) a purine nucleotide.

Is there a ChEBI ticket about this ?

There is, but I think what we did yesterday might be incorrect. It looks like some of the terms were meant for the grouping term rather than the pH7.3 term. Once we sort this out, we will update the ChEBI ticket.

Corrected the changes we made yesterday for terms meant to be grouping.


TODO: Advanced Event APIs

https://developers.facebook.com/blog/post/560/

Inviting guests to events almost works by passing a hash to the invited method
event.invited(:users => [ ... array of user ids... ])

The only problem is  the query string is being encoded, while the service isn't happy unless the request contains ids separated by commas.  Any ideas on how to get around this one?

event.invited(:users => [ ... array of user ids... ].join(','))


Add Ability to Follow Mastodon Users

How:

Add a "Follow Mastodon User" option to the + button on the Master Feeds screen
This will present UI that will ask the user for the username to follow in the format of<EMAIL_ADDRESS>NNW will convert this to the RSS url: https://<mastodon.domain>/users/<username>.rss and check to make sure it's valid
if it's valid, it will add to the account / folder selected

@brentsimmons Is this what you had in mind?
https://user-images.githubusercontent.com/7046652/203200831-da2743e7-94fe-41af-b31b-f2842ddbaca9.mov

fyi, RSS feeds don't include boosts: https://github.com/mastodon/mastodon/issues/11290
Is there another protocol endpoint that would make NNW usable as a Mastodon client?

The aim isn’t to make NetNewsWire a Mastodon client, but instead to make it easier to follow Mastodon RSS feeds.

Yeah, but boosts are part of feeds. I got here because I noticed the RSS feeds of some of the people I followed were weirdly empty, and it turned out because most of their feeds were boosts.
NNW's Reddit support doesn't even use RSS, so I didn't think that would be a blocker here…

@alltom you are correct. NNW uses the Reddit API, not RSS for its support. I don’t think we can rule out using ActivityPub for a Mastodon Extension in the future.


Fix a few misspellings found in P4_16 language spec

Seems fine to merge this in with either of your approvals.


static getInitialProps triggers page flash

When debugging locally, using getInitialProps to provide initial props to a page, the client side app seems to not get anything out of it. When reloading a page, the desired props will be passed to render, then shortly after the page will render as if no props were set.
A console error will be output in the browser : "Warning: Text content did not match."

Hi @vgrafe Can you provide an example where this can be reproduced? I tried something really basic like this and seems to work fine:
class SayHi extends React.Component {
  static async getInitialProps({ query }) {
    return {
      name: query.name
    };
  }

  render() {
    return <span>{`hi there ${this.props.name}`}</span>;
  }
}

// http://localhost:3000/about?name=batman

Ok, I found the cause of the bug. I might be doing something wrong when adding @zeit/next-typescript.
I know it is not related to your plugin but I'll leave steps to repro here to explain:
1- npm i @zeit/next-typescript --save
2- change next.config.js to the following:
const withCSS = require("@zeit/next-css");
const withTypescript = require('@zeit/next-typescript');

module.exports = withTypescript(
  withCSS({
    assetPrefix: 'https://s3.amazonaws.com/example_bucket'
  })
);

3- npm run dev
You'll observe the flash described initially. I might be missing on something when adding ts to my codebase.
No hard feelings if you close, now I'll look closer in the nextjs/ts docs.

Alright, for whoever runs into that, here's the correct code for the config file:
const withCSS = require("@zeit/next-css");
const withTypescript = require('@zeit/next-typescript');

module.exports =
  withCSS(withTypescript(), {
    assetPrefix: 'https://s3.amazonaws.com/example'
  });

Apologies. This solves TS but breaks CSS.

@vgrafe How does it break CSS?

Here is a repo for better illustration.
I found out the right way to combine plugins, but CSS loading still has some issues: the import statement loading the css file does not seem to work when the page is navigated to. As soon as the page is loaded directly (or reloaded), the css is applied for the remaining lifetime of the webapp.

@vgrafe Unfortunately I don't think the Next Links will work properly with API gateway stages in the base path, e.g. https://kw0e2oks0a.execute-api.us-east-1.amazonaws.com/dev/about, https://kw0e2oks0a.execute-api.us-east-1.amazonaws.com/dev/.
There is an open Feature Request in next to support this: https://github.com/zeit/next.js/issues/4998.
I'm looking into workarounds but for now you could try using a custom domain for your API GW and that should work fine with next links.

Sorry I was not clear - the issue happens when working locally, with yarn dev/npm run dev. I am aware of the problem with the api basepath, which is only resolved if mapped to a domain at this time.

In that case you will be better off raising the issue in the nextjs repo. When you run yarn dev in your example the plugin is not doing anything, instead just a normal next build happens. The plugin kicks in only when you run serverless deploy or serverless package commands.

Sounds good! Thank you for your help.


Fixes for 64-bit.

Compiles, but crashes on startup in a dynamic_cast in liblayout. Not sure what's going on there.

Wow, I didn't know there is an x86_64 version of liblayout...

I wonder if the dynamic cast segfault is actually a NULL dereference. Perhaps don't merge this til I have time to investigate whether or not that's actually a WonderBrush bug

From what I can tell, the commit contains only valid changes, including the fix for the liblayout system header path. So why not merge it as is?

Could this change be merged as is please?


Selection from Outside Case does not work in Demo

Could not find reason, maybe due to Ember 1.13.2 issues with bindings.

Fixed in version 0.4.0


ci.opensuse.org: Fix gerrit-git-prep builder

Drop the GIT_ORIGIN variable so GERRIT_SITE is used when cloning
repositories. This is needed because git.openstack.org (which
GIT_ORIGIN was pointing to) does no longer exist.
Also update GERRIT_SITE to reflect the openstack->opendev switch.

Untested but I hope this fixes failures like: https://ci.opensuse.org/job/openstack-rpm-packaging-sles12-Master/7605/console


User-assigned managed identity as listed as preview in the azure portal but not in documentation

Can the doc be updated to mark the service state of this identity type. It seems that user-assigned managed identities have existed for at least 10 months, what is the timeline for GA, is there any blocking issues?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7bd6bdc9-b545-f273-dc80-eeb69107d919
Version Independent ID: dbbbadd6-f533-33e3-1c1f-7cbc889b20b7
Content: Managed identities for Azure resources
Content Source: articles/active-directory/managed-identities-azure-resources/overview.md
Service: active-directory
GitHub Login: @priyamohanram
Microsoft Alias: priyamo

@priyamohanram
Could you get a confirmation on this please ?

@johnthcall : Thanks for reporting the issue. To follow availability status, please see Services that support managed identities. You can see that user-assigned managed identities are still not available or in preview for all of the supported services.
We will update this document as soon as the availability changes.
Please feel free to open a new issue if you have any questions or concerns. Thank you!
#please-close


How much time does the training take?

Based on a cluster of 96 NVIDIA DGX-A100 (8X40G), how long it will take training from scratch?

Hello @yangjingyuan, we spent ~60 days for training 400B tokens using 96 DGX A100.

I see, thank you very much.


docs: Add multi-language constructor page

Noting that in this case, the original constructor pages for TypeScript and Python have been split, with the first common section extracted to a multi-language page and the remainder left as language-specific content.  @helderco and @TomChv please review this to confirm nothing has been lost in translation.

Hey! Thanks for the changes I'm going to review this tomorrow! 👀

Note to use latest dagger version to update the output of --help since there's been some changes there. Flags, for example, have been renamed to Options, but specifically in the case of dagger call, they show as Arguments.
More context in:

https://github.com/dagger/dagger/issues/6943

Note to use latest dagger version to update the output of --help since there's been some changes there.

Updated. Can you please review again @helderco ? Thank you!

Vikram and I looked this, once links are removed and bottom note is combined I think this is ready to ship.

Noting here that the language-specific constructor pages have very different examples. These have been merged into this page under separate headings. I'm not sure if these are different because of actual disparity between SDKs or because they were authored at different times. I would like @helderco @TomChv @kpenfound to review this once and advise which of the language-specific examples could be made multi-language.

Can I also request that we call this topic "entrypoint functions" and explain that every module has one. The default one is generated automatically and has no arguments; It's possible to write a custom entrypoint function, the mechanism is SDK-specific.

Can I also request that we call this topic "entrypoint functions" and explain that every module has one. The default one is generated automatically and has no arguments; It's possible to write a custom entrypoint function, the mechanism is SDK-specific.

Done, let me know if further changes needed. I made this change in the title, intro and first section but not in the following language-specific ones since the constructor mechanism has been explained by that point.

Next steps as of 5/31 - @TomChv please take the lead to make decision for this specific comment, so we can move forward with next steps on this PR since Helder is OOO next week.

Next steps: @vikram-dagger will take the next steps on this PR.

expand complex types
Will clean up the Python-specific things into a Python tab. The other language tabs will be left blank as discussed with @marcosnils

Next steps: @vikram-dagger will take the next steps on this PR.

expand complex types

Done

Will clean up the Python-specific things into a Python tab. The other language tabs will be left blank as discussed with @marcosnils

Done, except that instead of tabs I'm leaving these as sections with a note that these are only applicable to Python (this is the format already used in other pages)


[wallet] Withdrawal does not work for second player

Currently the second player to submit their withdrawal transaction has their transaction fail with a Channel is Closed revert reason.
I think this is due to both players attempting to call concludePushOutcomeAndTransferAll
The second person to call this will fail since the channel was finalized and we require it not be finalized  _requireChannelNotFinalized(channelId);

I'm going to implement a quick work around of this by only having one player submit the transaction and the other just return success. This shouldn't be a long term solution (or should be enhanced so there's an option for player B to get their funds if player A doesn't submit the transaction).


Latest ide-toolbox and palette-antd are not compatible

Steps to reproduce

Create new React project (create-react-app)
Add antd dependency
Add toolbox

AR:
dependencies in package.json:
"@react-buddy/ide-toolbox": "^2.2.0",
"@react-buddy/palette-antd": "^4.0.0"

npm install cannot be executed:

Note: if you change ide-toolbox version to 2.0.0, npm install will work

works with
    "antd": "^4.19.5",
    "@react-buddy/ide-toolbox": "^2.2.1",
    "@react-buddy/palette-antd": "^4.1.2"

(versions that generated by studio now)


Upgrade Deps

Need to upgrade deps to support new movement e stop param on the firmware.

Coverage decreased (-0.003%) to 26.732% when pulling d6f5dd50362a65a7fb04b92b8615a8f8c5726259 on RickCarlino:master into 2cc6e900d8c032a414c50fcff5bac7fad535a42c on FarmBot:master.

Coverage decreased (-0.003%) to 26.732% when pulling ca87699d772755090083b869aa2cabe024af09a7 on RickCarlino:master into 2cc6e900d8c032a414c50fcff5bac7fad535a42c on FarmBot:master.

Coverage increased (+0.005%) to 26.74% when pulling cc30147f76a732547d4b8b203a85d5826305a95e on RickCarlino:master into 2cc6e900d8c032a414c50fcff5bac7fad535a42c on FarmBot:master.

Coverage increased (+0.005%) to 26.74% when pulling 37a1d39cec3444006b04242f5c95055eb2b169a6 on RickCarlino:master into 2cc6e900d8c032a414c50fcff5bac7fad535a42c on FarmBot:master.


Put concept list in Concepticon

And change code accordingly.

Done in https://github.com/lexibank/bremerberta/commit/6d5b79d7491caabfa67c1777fe962c71819becf7


feat(webdriver-manager): update download logic with streaming

This seems to fix up some unreliable download issues that we were
previously having.

LGTM

Thanks. Merged with aded26bc9ee6172d6f64361207f6a8b04da09b0d


how do i import icons?

http://prntscr.com/g6wbi6

https://github.com/Noctem/monocle-icons

If you follow the install directions (special git flag) from the readme, it should have pulled down the icons for you.
You can do it manually as well with the link @mimikq  gave


feat: create new Go packages

This migrates some of the "schema" based types that currently live in osv-scanner over to here since they're related to the underlying OSV schema rather than the scanner specifically.
Notably to help avoid dependency cycles we now have a dedicated constants package whose sole responsibility is to house types and constants for representing enums defined in the schema with no logic whatsoever; this will ensure that this package is always a leaf in the dependency tree, preventing circular dependencies in libraries (which notably we have now in the current osv-scanner/models package).
This also introduces an ecosystem package which houses our concept of an parsed ecosystem as implicitly defined in the spec - that is, a struct made up of an ecosystem name and an optional suffix. Note the underlying Ecosystem type actually lives in constants which might seem weird at first but 1. prevents cycles as mentioned above, and 2. avoids the weird ecosystem.Ecosystem situation.
Currently this is being introduced as a port from osv-scanner - the fact that there are missing constants will be addressed in a follow-up pull request, along with other changes such as updating the validation/schema.json and (hopefully) creating some automation to help keep everything in sync.

@another-rex I think this is actually pretty much good to go as a package, but would appreciate you doing a check as I forgot the top level directory/package structure we actually discussed, and also not 100% confident I've setup the package correctly from a Go POV 😅

Something to consider is the developer experience around onboarding a new ecosystem, or how we'll ensure consistency and accuracy in All The Places...
Right now we're looking at:

docs/schema.md
validation/schema.json

I think if that blows out to include

packages/go/constants/constants.go

we're also going to need to look at what scaffolding to put in place to ensure we maintain consistency.

Yup that's exactly what I'm going to be working on next 😄

@another-rex I think this is actually pretty much good to go as a package, but would appreciate you doing a check as I forgot the top level directory/package structure we actually discussed, and also not 100% confident I've setup the package correctly from a Go POV 😅

You might need to add another subfolder called osv-schema under go, and name the module github.com/ossf/osv-schema/packages/go/osv-schema, I'm not sure on that either though.

name the module github.com/ossf/osv-schema/packages/go/osv-schema

~I'm hoping not because that feels like an annoying amount of nesting, but also the linter is using github.com/ossf/osv-schema/linter, so at least hopefully we might be able to drop the ...~
na you must be right, cause otherwise how else could Go actually find the files? (the linter doesn't actually have a public interface, so it doesn't strictly need to follow the convention which is why it's fine)

I've opened #303 adding a script that handles automatically updating the constants

I talked with @oliverchang offline and I think we should remove Parsed for now from the osv-schema repository so that this repository only contains types, constants, and structs with 0 code.
(and probably move Parsed into osv-scanner instead, but that can be a later decision).

Ok so have removed the ecosystem package, and for now osvschema has just constants - I'll do another pull request exploring add structs, since they can be more complex and the ones we've got in osv-scanner do have some logic for marshalling JSON and YAML


How can I obtain Nodal Forces at selected nodes/elements/areas for all time steps in a transient analysis?

I can get nodal reaction forces from results for whole load steap. But how i can get reaction forces just for defined area in format:
SubStep LoadStep Time TotalReactionForce
1       1        0.5          ....
2       1        1             ....

I tried with dpf-core like:
from ansys.dpf import core as dpf
.....
.....
self.result = mapdl.result  # Geting result
self.result_file = mapdl._result_file
def MaxResults(self, container):
        scoping = dpf.Scoping()
        scoping.ids = range(1, int(self.sub_step_spinbox.value()) + 1)
        container.inputs.time_scoping.connect(scoping)
        fc = container.outputs.fields_container()
        #tfq = fc.time_freq_support
        #time_field = tfq.frequencies
        normOp = dpf.Operator("norm_fc")
        minmaxOp = dpf.Operator("min_max_fc")
        normOp.inputs.fields_container.connect(fc)
        minmaxOp.inputs.connect(normOp.outputs)
        fieldMax = minmaxOp.outputs.field_max()
        return fieldMax.data
model = dpf.Model(self.result_file)
force_reaction = model.results.force()
print(self.MaxResults(force_reaction))

But getting wrong results
Im using pydpf-core v2,1
Ansys 2021 R1
Any ideas?

@bedermaus Hi, is upgrading to pydpf 0.4.2 and Ansys WB 22R1 an option for you?

@ayush-kumar-423 right now - yes, i'm using not personal pc...

@bedermaus: If upgrading is fine for you, please do. As a lot of new changes have been brought in the newer versions and reaction_force operator works fine with 0.4.2 and 22R1 (as shown in the example above).

@ayush-kumar-423
is there any more information regarding the element nodal force, I have a case where user would like to get the element nodal forces  for specific named selection which is an interface surface for contact.
This is possible in Mechanical  using the ENFO on surface named selection, in case of bonded contact user could see the exact total force in tabular data that is anticipated to flow through contact.

ENFOVECTORS using user defined results

I have tried to use the element_nodal_forces in every possible way but could not get the expected result if I just sum the results from following code

def get_ENFO(data_sources, named_selection):

    #Set up Operator zur Auswahl der Loadsteps
    t_op = dpf.operators.metadata.time_freq_provider()
    t_op.inputs.data_sources(model)

    #Set up Operator zur Auswahl der named Selection
    NS_op = dpf.operators.scoping.on_named_selection()
    NS_op.inputs.named_selection_name.connect(named_selection)
    NS_op.inputs.data_sources(model)

    #Set up Operator für das Displacement
    f_op = dpf.operators.result.element_nodal_forces()
    f_op.inputs.mesh_scoping.connect(NS_op.outputs)
    f_op.inputs.time_scoping.connect(t_op.outputs.time_freq_support().time_frequencies)
    f_op.inputs.data_sources(model)
    f_op.inputs.requested_location.connect('Nodal')

    return f_op.outputs.fields_container()

force = get_ENFO(model, 'SELECTION')

op = dpf.operators.math.accumulate()
op.inputs.fieldA.connect(force[0])
ENFO_total = op.outputs.field.get_data()
ENFO_total.data
>>>array([[ 5.62067726e-10, -6.53067131e+03,  1.56433089e-10]])

I have also tried the following, without any success
model = dpf.Model("rst_file")
#Set up Operator zur Auswahl der Loadsteps
t_op = dpf.operators.metadata.time_freq_provider()
t_op.inputs.data_sources(model)
NS_op = dpf.operators.scoping.on_named_selection()
NS_op.inputs.named_selection_name.connect("SELECTION")
NS_op.inputs.data_sources(model)
NS_op.inputs.requested_location.connect("Nodal")
sc = NS_op.outputs.mesh_scoping()
f_op = dpf.operators.result.reaction_force()
f_op.inputs.mesh_scoping.connect(sc)
f_op.inputs.time_scoping.connect(t_op.outputs.time_freq_support().time_frequencies)
f_op.inputs.data_sources(model)

here is the zip file with RST, based on the named selection "SELECTION", is it possible to get the sum of nodal force for these nodes.
file.zip

@py-1337 @bedermaus Have you tried this code in 2023R1? There was a bug with dpf.operators.result.element_nodal_forces() and has been fixed in 23R1.


test

test

@sutaakar @ricardozanini @mswiderski
does it sounds good? let me know what you guys think about it. After https://github.com/kiegroup/kogito-cloud/pull/67 is merged I'll add the remaining tests and cook the final PR.

Looks good to me.

Looks good, but the final version will run every bats inside the project, right? I’ll open a JIRA to migrate to GH Actions from CircleCI in the Operator project as well.

closing, see https://github.com/kiegroup/kogito-cloud/pull/80


ESP8266 issue

Hi,
i am trying to run this current sensor with esp8266, but i've got a lot of issues.  I solved a most of the problems myself but one i can't do for 3 days.
During start program it shows me "AttributeError: 'module' object has no attribute '_level'". Code is from your example. You can see it below. The logging.py file from official micropython github from linked file in README.

from machine import Pin, I2C
from ina219 import INA219
from logging import INFO

i2c = I2C(scl=Pin(5), sda=Pin(4), freq=400000)

SHUNT_OHMS = 0.1

ina = INA219(SHUNT_OHMS, i2c)
ina.configure()
print("Bus Voltage: %.3f V" % ina.voltage())
print("Current: %.3f mA" % ina.current())
print("Power: %.3f mW" % ina.power())

Have you got any solution of this problem?

I have not seen this before, something wrong with logging module would be my suspicion, what happens if at the REPL prompt you do:
import logging

Does this work?
If it does what does:
dir(logging)

Give you?
Chris

Investigating a bit more I can see that the logging module has been updated recently and the _level attribute remove.
So until I can update pyb_in219 to account for this, you can try versions of the logging library before this commit, perhaps the one of 27th Mar 2021 would be a good place to start, so download and install this https://raw.githubusercontent.com/micropython/micropython-lib/fa13cbbc8b53e2ec6abbb1b0fa33d085582f3c54/python-stdlib/logging/logging.py
Chris

Update to pyb_ina219 to support latest version of logging looks like it might be fairly simple, will try at the weekend.

Fix for this already in progress on PR12, am looking to complete this.

Thanks for quick reply. I tried with the commit you sent and it works.

I faced same issue reported in the OP when testing the library on a Pico W.  Applied suggestion from below link (chnge in line 409) to got it working.
https://github.com/chrisb2/pyb_ina219/pull/12/commits/8caa4e2243767ff250dacf7982588d915e6f8a88


REST HTTP booster

similar to https://github.com/wildfly-swarm-openshiftio-boosters/wfswarm-rest-http

started a very simple repo here:  https://github.com/bucharest-gold/nodejs-rest-http
currently has no "booster/obsidian/openshift" stuff.
It is basically a node clone of the swarm booster, in fact I copied the index.html from the swarm booster  :)

While the "booster" has been created here: https://github.com/bucharest-gold/nodejs-rest-http
this issue is more around the integration into the obsidian/rhoar project.
I have a branch that will be were my tests are:  https://github.com/lholmquist/nodejs-rest-http/tree/openshift-io

Initial PR for the booster catalog https://github.com/openshiftio/booster-catalog/pull/61

Other things that need to happen in the other repos are documented here:  https://docs.google.com/a/redhat.com/document/d/1mkEr2mABgG2rR2i0Z9cjnoSuqfNLtxXUpmpswXV7lAY/edit?usp=sharing

I've tagged a v1.0.0 and sent PR's for both the next branch and oso-free branch of the booster catalog:
https://github.com/openshiftio/booster-catalog/pull/69
https://github.com/openshiftio/booster-catalog/pull/68
Both have been merged. this means this booster will be in the next release of the RHOAR stuff(v8) and is also now available here https://launch-stage.openshift.io/wizard


create rke2 on azure - invalid tenant

If this is a UI issue, please file an issue at https://github.com/rancher/dashboard/
Rancher Server Setup

Rancher version: Rancher 2.6 rc1
Installation option (Docker install/Helm Chart): helm on rke1

Information about the Cluster

Kubernetes version: 1.19.3
Cluster Type -  RKE2 on Azure

Describe the bug
Just by clicking on the create cluster, the ui displays an invalid tenant id - see screenshot, even though this is not defined in the relevant cloud credential
Screenshots

Additional context
<!--Add any other context about the problem here.—>

This bug has been fixed on 2.6-head. However, there is still an issue with RKE2 on Azure https://github.com/rancher/dashboard/issues/3798


RFC: Exclude macros from importing with #[macro_use(not(...))]

Introduce #[macro_use(not(...))] syntax, applicable to extern crate declarations. The purpose is to help solving naming conflicts and prevent unintended shadowing when two or more macros with the same name are imported from different crates.
Rendered

Two :+1:s from me!

If I remember correctly, the current plan proposed by Nick Camron plan for the macro overhaul is to completely handle namespacing for macros.
So I'm not sure this change is necessary since to #[macro_use] syntax is to be deprecated.

I for one don't agree with the rationale of dismissing all changes to macro_rules, however small, in anticipation of the new macro system which is coming at some undetermined future time and may or may not fix everyone's pet macro issue (though I'm sure it will be great).

🔔 This RFC is now entering its final comment period 🔔

My personal opinion on this RFC is that we should not accept. Whilst I think we can and should land changes to the existing macro system while concentrating on macros 2.0 (although this does make the bar for RFCs slightly higher), I don't think the benefit of this RFC are high enough to warrant change while there is a better, long-term solution in-flight, nor to outweigh the disadvantage of making macro import/export (already a sore spot) more complex.

Hmm, this seems like a fairly targeted change, and I can see why it's useful. On the other hand, there doesn't seem to be a strong out-cry in favor, and one can already use explicit positive imports with macro_use to avoid conflicts -- though it could be annoying, as one must list all of the macros that you do want, which could be quite a few. I guess this means I am inclined to close at present but could be persuaded otherwise if this were going to avoid a common papercut.

So we discussed this in the @rust-lang/lang meeting. The general feeling was that we ought to close this RFC, but I would characterize it as a "weak" feeling. Mostly there didn't seem to be enough desire for it to outweigh the disadvantages (listed below). In any case, I want to leave this open a bit more to gather feedback on the two most salient arguments for closing the RFC:

This is a relatively minor case, and there exists a workaround, since one can do #[macro_use(some,specific,names)] and pick out just the names that one wants.
This would add a capability to #[macro_use] that normal use does not possess (in particular, you can't do use foo::{* - x}), and it seems better to have them have more parity with one another.

Based on the reasoning given earlier, we decided in the @rust-lang/lang meeting to close this RFC. Thanks very much for the suggestion, @Xion!


Fix fix for #1101

#1217 failed to work properly in some corner cases like 0.1e2147483649. The change here fixes these cases and makes our arbitrary JSON numbers more likely to exercise some of these corner cases.

Codecov Report

Merging #1218 into master will increase coverage by 0.54%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1218      +/-   ##
==========================================
+ Coverage   86.07%   86.61%   +0.54%
==========================================
  Files          90       90
  Lines        2800     2809       +9
  Branches      118      123       +5
==========================================
+ Hits         2410     2433      +23
+ Misses        390      376      -14

Impacted Files
Coverage Δ

...la/io/circe/numbers/testing/JsonNumberString.scala
100% <100%> (ø)
:arrow_up:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
95.18% <100%> (+6.43%)
:arrow_up:

...d/src/main/scala/io/circe/NonEmptySeqDecoder.scala
91.66% <0%> (-8.34%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
86.5% <0%> (+0.5%)
:arrow_up:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
85.38% <0%> (+0.58%)
:arrow_up:

...les/core/shared/src/main/scala/io/circe/Json.scala
79.87% <0%> (+2.43%)
:arrow_up:

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0%> (+2.7%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
:arrow_up:

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 81fc2c9...ca1f3e4. Read the comment docs.


Avoid moving result of read_attribute

 name                                        before ns/iter  after ns/iter  diff ns/iter   diff %  speedup
 context_new_and_query_location_rc           2,490,696       2,447,360            -43,336   -1.74%   x 1.02
 context_new_and_query_location_slice        772,800         773,439                  639    0.08%   x 1.00
 context_new_and_query_with_functions_rc     3,068,885       3,021,044            -47,841   -1.56%   x 1.02
 context_new_and_query_with_functions_slice  1,180,680       1,144,850            -35,830   -3.03%   x 1.03
 context_new_parse_functions_rc              37,416,109      30,829,671        -6,586,438  -17.60%   x 1.21
 context_new_parse_functions_slice           26,969,411      24,411,324        -2,558,087   -9.49%   x 1.10
 context_new_parse_lines_rc                  11,583,804      11,516,118           -67,686   -0.58%   x 1.01
 context_new_parse_lines_slice               7,296,223       7,345,699             49,476    0.68%   x 0.99
 context_new_rc                              2,311,116       2,247,925            -63,191   -2.73%   x 1.03
 context_new_slice                           626,076         621,520               -4,556   -0.73%   x 1.01
 context_query_location_rc                   726,244         727,900                1,656    0.23%   x 1.00
 context_query_location_slice                722,684         723,472                  788    0.11%   x 1.00
 context_query_with_functions_rc             4,346,361       4,280,144            -66,217   -1.52%   x 1.02
 context_query_with_functions_slice          4,328,587       4,331,231              2,644    0.06%   x 1.00
 new                                         29,658          28,688                  -970   -3.27%   x 1.03
 new_unresolved_and_resolve_separate         29,812          29,250                  -562   -1.89%   x 1.02
 trace_and_resolve_callback                  14,333          13,607                  -726   -5.07%   x 1.05
 trace_and_resolve_separate                  12,279          11,270                -1,009   -8.22%   x 1.09

This is the equivalent of https://github.com/gimli-rs/gimli/pull/456.

Coverage decreased (-0.6%) to 70.529% when pulling 292d1956144e025692c2dd2a3196304c138b884e on philipc:entries-raw-ref into af29dbae85bbac9ae15162c6a2d71f60ca9b8271 on gimli-rs:master.


getting assaulted while filing for financial aid

We have written the needed data into your clipboard because it was too large to send. Please paste.

Hi Wizibeer, is there an issue you're experiencing related to our extension?
If there are, please file a new issue, cheers!


Check jubjub key correctness independent of redjubjub / jubjub

Motivation

Specifications

Designs

Solution

Review

Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Follow Up Work

Moved back to draft due to a panic during sync, investigating...


list maps

HLSW can list the maps installed on the server (not just those in rotation). Is there any way for qstat to support this?

If the protocol supports it then this would be possible. Feel free to submit a PR.