PR: Update PR Template

This merge adds as new Pull Request template copied from the Inundation Mapping project PR template.
Changes

/.github/PULL_REQUEST_TEMPLATE.md

Checklist
You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.

[x] Informative and human-readable title, using the format: [_pt] PR: <description>
[ ] Links are provided if this PR resolves an issue, or depends on another other PR
[x] If submitting a PR to the dev branch (the default branch), you have a descriptive Feature Branch name using the format: dev-<description-of-change> (e.g.: dev-revise-levee-masking)
[x] Changes are limited to a single goal (no scope creep)
[x] The feature branch you're submitting as a PR is up to date (merged) with the latest dev branch
[x] Changes adhere to PEP-8 Style Guidelines
[x] Any change in functionality is tested
[ ] Passes all unit tests locally (inside interactive Docker container, at /foss_fim/, run: pytest unit_tests/)
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[x] Project documentation has been updated (CHANGELOG and/or README)
[ ] Reviewers requested

We chose the 4-segment system for FIM because the first digit was already chosen by leadership (i.e. FIM3 and FIM4). ras2fim has no such mandate, so I think the 3 segment system is appropriate.


Tasks: Consider introducing "Add Configuration..." like in debug

Refs: #29442
Currently in debug land I find it easier to add a new configuration due to some UX on top which helps with that.
Consider introducing the same in tasks land.

@egamma and I discussed that.


File watcher ignoring excludes

Type: Bug
Here is my files.watcherExclude:
        "files.watcherExclude": {
                "**/bazel-bando/**": true,
                "**/bazel-bin/**": true,
                "**/bazel-out/**": true,
                "**/bazel-testlogs/**": true,
                "/**/.cache/**": true
        },

Despite this configuration, I'm seeing log lines like the following after enabling remote logging for File Watcher
2024-10-30 20:43:38.135 [trace] [File Watcher ('parcel')] Request to start watching: /home/builder/.cache/bazel/_bazel_builder/111d6a28ddfe7cb2f314c9d3cd6a7751/execroot/ritta/bazel-out/aarch64-dbg/bin (excludes: **/.git/objects/**,**/.git/subtree-cache/**,**/.hg/store/**,**/bazel-bando/**,**/bazel-bin/**,**/bazel-out/**,**/bazel-testlogs/**,/**/.cache/**,/home/builder/.vscode-server/extensions/**, includes: <all>, filter: <none>, correlationId: <none>),/home/builder/.cache/bazel/_bazel_builder/111d6a28ddfe7cb2f314c9d3cd6a7751/external/python3_10_aarch64-unknown-linux-gnu/lib/python3.10 (excludes: **/.git/objects/**,**/.git/subtree-cache/**,**/.hg/store/**,**/bazel-bando/**,**/bazel-bin/**,**/bazel-out/**,**/bazel-testlogs/**,/**/.cache/**,/home/builder/.vscode-server/extensions/**, includes: <all>, filter: <none>, correlationId: <none>),/usr/lib/python3/dist-packages (excludes: **/.git/objects/**,**/.git/subtree-cache/**,**/.hg/store/**,**/bazel-bando/**,**/bazel-bin/**,**/bazel-out/**,**/bazel-testlogs/**,/**/.cache/**,/home/builder/.vscode-server/extensions/**, includes: <all>, filter: <none>, correlationId: <none>),/usr/lib/python3.10 (excludes: **/.git/objects/**,**/.git/subtree-cache/**,**/.hg/store/**,**/bazel-bando/**,**/bazel-bin/**,**/bazel-out/**,**/bazel-testlogs/**,/**/.cache/**,/home/builder/.vscode-server/extensions/**, includes: <all>, filter: <none>, correlationId: <none>),/usr/local/lib/python3.10/dist-packages (excludes: **/.git/objects/**,**/.git/subtree-cache/**,**/.hg/store/**,**/bazel-bando/**,**/bazel-bin/**,**/bazel-out/**,**/bazel-testlogs/**,/**/.cache/**,/home/builder/.vscode-server/extensions/**, includes: <all>, filter: <none>, correlationId: <none>)

I've tried this with both absolute ignore rules like /**/.cache/** as well as relative like **/.cache/**. Nothing seems to match enough to catch this.
I /think/ VS Code is finding this path because of the following symlink in my workspace root
$  ls -al bazel-*
lrwxr-xr-x 1 builder dialout  89 Sep 19 21:22 bazel-bando -> /home/builder/.cache/bazel/_bazel_builder/111d6a28ddfe7cb2f314c9d3cd6a7751/execroot/ritta/
lrwxr-xr-x 1 builder dialout 115 Oct 29 19:19 bazel-bin -> /home/builder/.cache/bazel/_bazel_builder/111d6a28ddfe7cb2f314c9d3cd6a7751/execroot/ritta/bazel-out/aarch64-dbg/bin/
lrwxr-xr-x 1 builder dialout  99 Sep 19 21:22 bazel-out -> /home/builder/.cache/bazel/_bazel_builder/111d6a28ddfe7cb2f314c9d3cd6a7751/execroot/ritta/bazel-out/
lrwxr-xr-x 1 builder dialout 120 Oct 29 19:19 bazel-testlogs -> /home/builder/.cache/bazel/_bazel_builder/111d6a28ddfe7cb2f314c9d3cd6a7751/execroot/ritta/bazel-out/aarch64-dbg/testlogs/

... but again the existing exclude rules should have caught the symlink source.
VS Code version: Code 1.95.0 (912bb683695358a54ae0c670461738984cbb5b95, 2024-10-28T20:16:24.561Z)
OS version: Darwin arm64 23.6.0
Modes:
Remote OS version: Linux arm64 6.10.4-linuxkit

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
4, 8, 9

Memory (System)
16.00GB (0.03GB free)

Process Argv
--crash-reporter-id 8b9e2792-5ee0-48ef-a561-5f6b02100b14

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: localdev

OS
Linux arm64 6.10.4-linuxkit

CPUs
unknown (10 x 0)

Memory (System)
7.66GB (5.79GB free)

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

remote-ssh
ms-
0.116.2024100715

remote-ssh-edit
ms-
0.87.0

remote-explorer
ms-
0.4.3

vim
vsc
1.28.1

vscode-bazel
Baz
0.10.0

gitlens
eam
15.6.2

black-formatter
ms-
2024.4.0

debugpy
ms-
2024.12.0

python
ms-
2024.16.1

vscode-pylance
ms-
2024.10.1

(1 theme extensions excluded)

Excludes are actually applied on the file watcher library and so the message you see does not necessarily mean that the file watcher is also applied on disk. You can assume that the path is not watched given your glob pattern.

I think my answer needs further clarification: files.watcherExclude behaves differently depending on your platform and also whether a glob pattern is used vs. a path.
glob pattern vs path
The setting already explains this: glob patterns are actually only matched on the relative path portion relative to the watched root. So if you are watching a path of /Users/bpasero/Desktop/test-ts, a glob pattern of **/bpasero/** would not match that path.
A path is taken as is and matched against the absolute path of the watcher.
platform differences
The files.watcherExclude setting was mainly introduced for Linux to workaround platform limitations when watching large folders and running out of file handles: Only on Linux, a folder is watched recursively by installing file watchers on each folder that is found beginning from the root. files.watcherExclude is applied while traversing the folders making it easy to reduce the file handle overhead by reducing large folders (such as output).
Windows and macOS on the other hand have very efficient recursive folder watchers built in: here you cannot really disable watching a folder that VS Code wants to watch unless you disable all file watching (by putting ** into the files.watcherExclude setting).
tl;dr;
files.watcherExclude will not prevent a folder from being watched that VS Code wants to watch recursively, but helps a lot on Linux to reduce the overhead.
In all cases, files.watcherExclude will also be applied on resulting file events to filter them out from being dispatched to VS Code, so this setting still helps reducing CPU overhead of processing the events.

Thanks, @bpasero.
I'm trying to track down some issues with bootstrap-fork --type=fileWatcher running at 100% CPU on Linux. I'll try adding the /home/builder/.cache/baze/ path instead of a glob and see if that catches it.

Does it never stop running at 100% or eventually settles?

Yeah, it does eventually stop.

I am still wondering how /home/builder/.cache/bazel/_bazel_builder/111d6a28ddfe7cb2f314c9d3cd6a7751/execroot/ritta/bazel-out/aarch64-dbg/bin is requested to being watched. You are not opening that as a folder workspace?
We do have extension API to install more watchers, so its possible that you have an extension that watches this path?

We have symlinks in the workspace root that point into there.

Ahhh yes I have a Bazel extension active. I can try disabling that.

Symbolic links are actually not automatically followed for file watching.


Add option to prevent same file opening twice

Sometimes I've forgotten that I have opened the same file twice in two or more panes in vscode. This has led me to edit the wrong file opened which in turn creates confusion as to why my code isn't working as intended.
I'm wondering, could an option be added to prevent the same file being opened more than once. If it is opened in a new pane, let the other opened version close (do you want to save edits etc.).

This issue has already been reported. Please use the search function next time before reporting an issue and/or this time if you are curious about the progress of the issue.


v1.3: SolidFire does not dynamically create account if "TenantName" does not exist

According to the SolidFire config documentation if the TenantName (Account on SolidFire) does not exist it will be dynamically created.  Testing shows this to not be the case.
The code snippet in solidfire_san.go that does not appear to function properly is:
// lookup the specified account; if not found, dynamically create it
	account, err := client.GetAccountByName(&req)
	if err != nil {
		req := sfapi.AddAccountRequest{
			Username: c.TenantName,
		}
		tenantID, err = client.AddAccount(&req)
		if err != nil {
			log.Fatal("Failed to initialize solidfire driver while creating tenant: ", err)
		}
	} else {
		tenantID = account.AccountID
	}

debug: true logging snippet is:
time="2017-01-26T20:43:35Z" level=info msg="Using storage driver: solidfire-san"
time="2017-01-26T20:43:35Z" level=info msg="Using config: {1 solidfire-san true false [] []}"
time="2017-01-26T20:43:35Z" level=info msg="Starting docker volume plugin with the following options:" port=27609 volume-driver=netapp volumeDir="/var/lib/docker-volumes/netapp"
time="2017-01-26T20:43:48Z" level=debug msg="Get({hellpo map[]})"
time="2017-01-26T20:43:48Z" level=debug msg="Getting path for volume 'netappdvp-hello' as '/var/lib/docker-volumes/netapp/netappdvp-hellpo'"
time="2017-01-26T20:43:48Z" level=debug msg="Create({hellpo map[]})"
time="2017-01-26T20:43:48Z" level=debug msg="SolidfireSANStorageDriver#Create(netappdvp-hellpo)"
time="2017-01-26T20:43:48Z" level=debug msg="GetVolumeByName: netappdvp-hello, 0"
time="2017-01-26T20:43:48Z" level=debug msg="Options passed in to create: map[]"
time="2017-01-26T20:43:48Z" level=debug msg="Issueing request to SolidFire Endpoint..."
time="2017-01-26T20:43:48Z" level=debug msg="POST request to<EMAIL_ADDRESS>time="2017-01-26T20:43:48Z" level=debug msg="request:816 method:ListVolumesForAccount params:&{0}" ="{\n  \"error\": {\n    \"code\": 500,\n    \"message\": \"Illegal AccountID 0\",\n    \"name\": \"xAccountIDDoesNotExist\"\n  },\n  \"id\": 816\n}"
time="2017-01-26T20:43:48Z" level=error msg="Received error response from API request"
time="2017-01-26T20:43:48Z" level=error msg="Error retrieving volumes: Received error response from API request"
time="2017-01-26T20:43:48Z" level=debug msg="Options after conversion: map[]"
time="2017-01-26T20:43:48Z" level=info msg="Creating with default size of:<PHONE_NUMBER>"
time="2017-01-26T20:43:48Z" level=debug msg="Issueing request to SolidFire Endpoint..."
time="2017-01-26T20:43:48Z" level=debug msg="POST request to<EMAIL_ADDRESS>time="2017-01-26T20:43:48Z" level=debug msg="request:918 method:CreateVolume params:&{netappdvp-hellpo 0<PHONE_NUMBER> false {0 0 0 0} map[platform:Docker-NDVP]}" ="{\n  \"error\": {\n    \"code\": 500,\n    \"message\": \"Could not find an account with the given accountID.\",\n    \"name\": \"xAccountIDDoesNotExist\"\n  },\n  \"id\": 918\n}"

Yup, you're correct.  The original SFDP did this for you but that got lost in the import somewhere, I'll get a fix up for it.

So it turns out that it does work, but there's something going on intermittently that we're not catching or reporting clearly.  I did see this in some testing earlier, but in trying to force the issue this afternoon I'm not having any luck reproducing it again.  If you can make this happen consistently I'd love to instrument your setup with some additional debugging.  Even just some debug statements around the GetAccountByName response and Create.

I found it: RBAC.  I was using a user that had only volume access rights.  When I enabled the user for accounts as well it worked.  Duh.
I guess the "fix" for nDVP would be to improve logging in case it encountered a problem during dynamic account creation, including RBAC permission denied.  Especially because the SF event log is silent in case of blocked API calls (maybe open an RFE there?) the root cause isn't obvious by checking logs...
Thanks!

I've added debug logging during init, I think this will address the issue you're seeing.  Check out the latest release and let me know if there's still a problem you're seeing.  I believe this can be closed at this point.

@j-griffith Do you know which commit resolved this issue?

Hi @j-griffith,
Here is the result if you start the netappdvp using a config.json where the tenant does not exist and the user does not have enough RBAC priv to create it:
[root@centos72 netappdvp]# ./netappdvp -debug
ERRO[2017-02-08T11:05:59Z] error detected in API response: {ID:859 Error:{Code:500 Message:xUnknownAccount Name:xUnknownAccount}}
ERRO[2017-02-08T11:05:59Z] error detected in API response: {ID:175 Error:{Code:500 Message:xPermissionDenied Name:xPermissionDenied}}
INFO[2017-02-08T11:05:59Z] successfully initialized SolidFire Docker driver version 1.3.3 [native]
Logfile Location (Level: debug): /var/log/netappdvp/netapp.log

If the tenant does not exist and you do have enough priv to create:
[root@centos72 netappdvp]# ./netappdvp -debug
ERRO[2017-02-08T11:10:38Z] error detected in API response: {ID:90 Error:{Code:500 Message:xUnknownAccount Name:xUnknownAccount}}
INFO[2017-02-08T11:10:38Z] successfully initialized SolidFire Docker driver version 1.3.3 [native]
Logfile Location (Level: debug): /var/log/netappdvp/netapp.log

The errors were logged to the interactive session and are not found in the netapp.log logfile.
I would suggest:

Make sure logging occurs to the netapp.log file
Remove the ERROR thrown if the account doesn't exist and instead log a more descriptive INFO message explaning that the account was not found and will be created.
In case the account can't be created log an ERROR that the Account doesn't exist and could not be created and then exit.  Leave the existing 500 errror with permission denied as-is.

My 2 cents.  Thanks for your work on this!

Tried this myself with the latest code and I still see the root issue when using a user that's unable to create a tenant and that tenant does not yet exist. Recent logging changes do assure that the error shows up in the log file now, but we're not any more clear about the reason for the failure. We also allow the plugin to continue to initialize and start in this scenario even though all subsequent operations will fail.

I've added some detection for unauthorized in the response from API requests, log it and return an error which should result in a fatal during init.  The sequence looks like this, I hope that this will be sufficient:
ubuntu@ndvp:~/go/src/github.com/netapp/netappdvp$ sudo ./netappdvp -debug -config /etc/netappdvp/solidfire.json -log-level debug
time="2017-05-24T19:43:15Z" level=info msg="Initialized logging." buildTime=unknown driverBuild="17.07.0-custom+unknown" driverVersion=17.07.0-custom logFileLocation="/var/log/netappdvp/netapp.log" logLevel=debug
time="2017-05-24T19:43:15Z" level=debug msg="Setting default volume size." size=1G
time="2017-05-24T19:43:15Z" level=debug msg="Parsed commonConfig: {Version:1 StorageDriverName:solidfire-san Debug:false DebugTraceFlags:map[] DisableDelete:false StoragePrefixRaw:[] SnapshotPrefixRaw:[] CommonStorageDriverConfigDefaults:{Size:1G}}"
time="2017-05-24T19:43:15Z" level=debug msg="SolidfireSANStorageDriver#Initialize(...)"
time="2017-05-24T19:43:15Z" level=debug msg="Reparsed into solidfireConfig" DisableDelete=false SnapshotPrefixRaw= StorageDriverName=solidfire-san StoragePrefixRaw= Version=1
time="2017-05-24T19:43:15Z" level=debug msg="Decoded to &{CommonStorageDriverConfig:{Version:1 StorageDriverName:solidfire-san Debug:false DebugTraceFlags:map[] DisableDelete:false StoragePrefixRaw:[] SnapshotPrefixRaw:[] CommonStorageDriverConfigDefaults:{Size:}} TenantName:ndvp<EMAIL_ADDRESS>DefaultVolSz:1 SVIP:<IP_ADDRESS>:3260 InitiatorIFace:default Types:0xc4200d0fc0 LegacyNamePrefix:netappdvp-}"
time="2017-05-24T19:43:15Z" level=debug msg="About to call NewFromParameters" cfg={ndvp<EMAIL_ADDRESS><IP_ADDRESS>:3260 default 0xc4200d0fc0 netappdvp-} defaultTenantName=ndvp<EMAIL_ADDRESS>svip="<IP_ADDRESS>:3260"
time="2017-05-24T19:43:15Z" level=debug msg="issuing request to SolidFire endpoint:  {"id":521,"method":"GetAccountByName","params":{"username":"ndvp"}}"
time="2017-05-24T19:43:15Z" level=debug msg="response to api call GetAccountByName: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Content-Type:[application/json] Access-Control-Allow-Methods:[GET, POST, OPTIONS] Access-Control-Allow-Headers:[DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization] Access-Control-Allow-Credentials:[true] Server:[nginx/1.9.14] Date:[Wed, 24 May 2017 19:43:15 GMT] Connection:[keep-alive] Vary:[Accept-Encoding]] Body:0xc420010240 ContentLength:-1 TransferEncoding:[chunked] Close:false Uncompressed:true Trailer:map[] Request:0xc4200d6870 TLS:0xc4200a86e0}"
time="2017-05-24T19:43:15Z" level=warning msg="error detected in API response: {ID:521 Error:{Code:500 Message:xUnknownAccount Name:xUnknownAccount}}"
time="2017-05-24T19:43:15Z" level=debug msg="issuing request to SolidFire endpoint:  {"id":615,"method":"AddAccount","params":{"username":"ndvp"}}"
time="2017-05-24T19:43:15Z" level=debug msg="response to api call AddAccount: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Connection:[keep-alive] Vary:[Accept-Encoding] Access-Control-Allow-Headers:[DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization] Access-Control-Allow-Credentials:[true] Date:[Wed, 24 May 2017 19:43:15 GMT] Content-Type:[application/json] Access-Control-Allow-Methods:[GET, POST, OPTIONS] Server:[nginx/1.9.14]] Body:0xc420010ba0 ContentLength:-1 TransferEncoding:[chunked] Close:false Uncompressed:true Trailer:map[] Request:0xc4201624b0 TLS:0xc4200a8790}"
time="2017-05-24T19:43:15Z" level=warning msg="error detected in API response: {ID:615 Error:{Code:500 Message:xPermissionDenied Name:xPermissionDenied}}"
time="2017-05-24T19:43:15Z" level=error msg="error detected in AddAccount API response: device API error: xPermissionDenied"
time="2017-05-24T19:43:15Z" level=fatal msg="failed to initialize solidfire driver while creating tenant: device API error"


Adds Adwerx repository

Glad to find the hub; excited to add more charts.
Let me know if there's anything that needs ammending!

@mattfarina Absolutely. Sorry, I missed that check. Should be good now.


Update zero_to_fp32.py - to support deepspeed_stage_1

Since deepspeed 1 checkpoint structure is identical to deepspeed 2 (AFAIK), we should just change the stage check and add support accordingly
However I am not 100% sure if this is intentional by design, or some coincidence in my use case - so might need someone with more knowledge on this topic to weigh in 🤔

@stas00, do you remember why stage 1 was excluded?

@PicoCreator, thanks for this PR.

Glad to see my wild guess, work and be of use (found a few issues on dependent projects that encounted this)
I currently use deepspeed 1 to train small toy models (<=3B), as fast as possible, and to test param/model architecture changes =) on consumer hardware (where the gpu-to-gpu communication of deepspeed 2 is noticeable)


Refactor giganto codes

Change an ambiguous bool type (use enum type)
Change &Vec to &[u8]
Change the creation of NetworkKeys to a new constructor
Change unnecessary channel transfers (using notify)

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@e148d22). Click here to learn what that means.
Patch coverage: 96.15% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #292   +/-   ##
=======================================
  Coverage        ?   78.18%
=======================================
  Files           ?       27
  Lines           ?     4030
  Branches        ?        0
=======================================
  Hits            ?     3151
  Misses          ?      879
  Partials        ?        0

Impacted Files
Coverage Δ

src/publish.rs
71.24% <ø> (ø)

src/ingest.rs
85.24% <94.11%> (ø)

src/publish/tests.rs
99.44% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Small fixes

Pull Request Test Coverage Report for Build 860

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 79.425%

Totals

Change from base Build 859:
0.01%

Covered Lines:
1682

Relevant Lines:
2029

💛  - Coveralls


QAFExtendendWebDriver is throwing error when using the AndridUIAutomator to scroll the page till end

QAF Version

Note: only the latest version is supported

Steps To Reproduce
1. When I'm trying to scroll the page to find the mobile element (the elements are dynamic each time the xpath will get change)
2.
3.

Expected behavior
Using AndroidUIAutomator, it has to scroll/ swipe the till the end of the page
Actual behavior
It is not scrolling till the end of the page instead It is throwing error "The class com.qmetry.qaf.automation.ui.webdriver.QAFExtendedWebDriver of the given context doesn't implement io.appium.java_client.FindsByAndroidUIAutomator nor io.appium.java_client.FindsByFluentSelector"
Is the issue reproducible on runner?

[x] QAS
[ x] Maven
[ ] Gradle
[x] Ant
[ ] Eclipse

Test case sample

Please, share the test case (as small as possible) which shows the issue
Using the below code snippet it has to scroll till end of the page
driver.findElement(MobileBy.AndroidUIAutomator(
"new UiScrollable(new UiSelector().scrollable(true)).scrollToEnd(10)"));

But it is throwing error
"The class com.qmetry.qaf.automation.ui.webdriver.QAFExtendedWebDriver of the given context doesn't implement io.appium.java_client.FindsByAndroidUIAutomator nor io.appium.java_client.FindsByFluentSelector"
Ref: http://appium.io/docs/en/writing-running-appium/tutorial/swipe/android-tricks/

For your case, you can use native locator strategy directly without any code. Refer documentation for locating element. For example:
my.ele.loc = -android uiautomator=new UiScrollable(new UiSelector().scrollable(true)).scrollToEnd(10)
care.book.appointment.btn=-android uiautomator=new UiScrollable(new UiSelector().scrollable(true).instance(0)).scrollIntoView(new UiSelector().textContains("Book an appointment").instance(0))

you can use this locator as usual. For example:
driver.findElement("my.ele.loc")
//or
$("my.ele.loc").isPresent();

For other cases, If you are not using remote driver and you want to use under laying driver object you can use getUnderLayingDriver() method. For example, when you are using driver.name=appiumDriver and providing driver class in capability like example here, you can access AppiumDriver as below
AppiumDriver<WebElement> driver = (AppiumDriver<WebElement>)getDriver().getUnderLayingDriver();


116 lint intrf+first

Printing can be improved - e.g. print only once VPC name for all relevant issues. Not in this PR
toJSON still not implemented


Support pagination for groups

Requirement
Currently, when we list the Users from the UI and via SCIM, we have the option to paginate the user listing. If we do the same to the groups, we don't have the option to paginate the groups listing.
Related Issues

https://github.com/wso2/product-is/issues/7664

Duplicate of https://github.com/wso2/product-is/issues/7662


Adding Azure Game Developer Virtual Machine bicep template

Description

If you haven't already, read the full contribution guide. The guide may have changed since the last time you read it, so please double-check.
Adding a new module

[ ] A proposal has been submitted and approved.
[ ] I have included "Closes #{module_proposal_issue_number}" in the PR description.
[ ] I have run brm validate locally to verify the module files.
[ ] I have run deployment tests locally to ensure the module is deployable.

Updating an existing module

[ ] This is a bug fix:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] I have run brm validate locally to verify the module files.
[ ] I have run deployment tests locally to ensure the module is deployable.
[ ] I have read the Updating an existing module section in the contributing guide and updated the version.json file properly:

[ ] The PR contains backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json.
[ ] The PR contains backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] The PR contains breaking changes, and I have bumped the MAJOR version in version.json.

#129

@shenglol , this is also ready for review.
@alex-frankel , @bmoore-msft , there was a discussion about a "parameters" file for bicep which I jumped in on.
Take a look at this PR, and all of the parameters in my main.bicep. The majority of these are duplicates with the "GameDev VMSS" template. It would be ideal if there was a way that I could "add" parameter sets to a main.bicep, which are declared in a common folder. Scala has a process for this called "Traits", which is a little less then full on inheritance but I think it's a great example to look at.

It would be ideal if there was a way that I could "add" parameter sets to a main.bicep, which are declared in a common folder.

This is definitely a scenario we are interested in and something we are considering now that we have native bicep parameters and is called out in the spec. I hope we get to it soon!


[ Docs ] Move docs to separate package

Since docs will be shared for every version of SFUI (react/vue/whatever) they should become a separate package ( @storefrontui/docs )

Hi @filrak For this issue you want the entire docs folder to be moved to a separate package in this case docs just like we have the vue and shared packages?

@lauragift21 sorry i somehow missed your reply. Yes, entire docs


Multiple logs?

Is there a possibility to define multiple log streams for the notifications. I do not mind if all notifications go into the same channel (I saw a fork related to notifications into multiple channels) but I would love to be able to get notified about errors in multiple logs.

It should be pretty easy to spin up multiple lambdas for this, one for each channel. I'll look sometime into if it makes sense to do multiple logs into one lambda; maybe with some aggregation it would work well.

Thank you!

Thank you!


feat export image

feat: add export image
fix: double click error

looks like

Thank you! Can you provide a screenshot and what is the difference between the added feature and Figma’s built-in export feature?

Thank you! ~Can you provide a screenshot and~ missed that on my phone
What is the difference between the added feature and Figma’s built-in export feature?

This PR doesn't differ much from Figma; it simply makes operations more convenient and more similar to DevMode. The actual goal is to add a button for uploading to the CDN in the future.

The main purpose of this extension is not to compete with Dev Mode and I do not intend to include features already accessible in view-only mode in Figma. Uploading to CDN sounds useful but it will introduce quite a lot complexity into this extension (for both implementation and user preferences).

The main purpose of this extension is not to compete with Dev Mode and I do not intend to include features already accessible in view-only mode in Figma. Uploading to CDN sounds useful but it will introduce quite a lot complexity into this extension (for both implementation and user preferences).

I get it, but there have other problem, u didn't preventDefault double click with the IconButton

I get it, but there have other problem, u didn't preventDefault double click with the IconButton

Yes that's a good catch. Would you mind split the PR and make a separate fix for this?

PS. I think in such case it's better to not stop double click from the button. Instead we should ensure when we listen to click or double click events on a container element which might contain other clickable elements, the event target isn't coming from some interactive (eg. not from inside a focusable element (inputs, buttons, elements with tabindex or contenteditable, etc.)).

I'm gonna close this for now as we do have access to similar features already in Figma itself.


Move DNS Controller into its own component

What
With DNSPolicy moving to kuadrant operator, we need to move the DNS logic somewhere other than the MGC. To do this we will set up a new repo for the DNSController that will contain the logic to reconcile DNSRecords and HealthChecks

New Repo Created: https://github.com/kuadrant/kuadrant-dns-operator

Apart from doc updates and a few small tweaks this repo is ready https://github.com/Kuadrant/kuadrant-dns-operator.
Follow up tasks:

https://github.com/Kuadrant/kuadrant-dns-operator/issues/10
https://github.com/Kuadrant/kuadrant-dns-operator/issues/11


[rstmgr] Verification sign-off for M2.5

This tracks open verification tasks for M2.5.
See effort estimation docs for details.
CC @msfschaffner @matutem

Should this contain checkboxes for pending issues?

At the moment this is just a placeholder.
If you'd like to add more details and link to the individual issues, you are welcome to.


Syntactic sugar for UI scheduler and Test scheduler erasable to UI scheduler

Note: UIScheduler has different specialization than AnySchedulerOf, which means UIScheduler.eraseToAnyScheduler() is not compatible with AnySchedulerOf. Likewise, the existing DispatchQueue.test.eraseToAnyScheduler() is not compatible with TestSchedulerOf.

@stephencelis Thanks for the clarification! The scenario you mentioned is my scenario exactly. I'll give an example from my app.
final class HomeViewModel: ObservableObject {
  private var subscriptions: [AnyCancellable] = []

  // A list of books continuously updated, displayed in some List view.
  @Published private(set) var books: [Book] = []

  init(
    // A service that publishes a list of books, which can change over time. Starts with an initial value.
    bookService: BookService,
    uiScheduler: AnyScheduler<DispatchQueue.SchedulerTimeType, Never> = .ui
  ) {
    bookService.allBooks()
      // Make sure the @Published property is updated on main queue. The publisher may send values
      // on other queues, however the initial value is sent on the current queue. UI scheduler is needed
      // to avoid an unnecessary thread hop and to avoid displaying momentarily the default (empty)
      // list of books - this would look like a glitch.
      .receive(on: uiScheduler)
      .assign(to: \.books, on: self, ownership: .weak)
      .store(in: &subscriptions)
  }
}

For uniformity, I am using TestScheduler everywhere in tests (no ImmediateScheduler).

@emixb In this case, do you need to use a test scheduler? Since no timing is involved would an immediate scheduler suffice in tests?

@stephencelis Technically, an immediate scheduler is sufficient for the example from above. But my team is using TestScheduler for all tests (perhaps for simplicity or uniformity). We've tried several approaches over the years with RxSwift and eventually settled on using only TestScheduler - this one is both simple and powerful enough to use in all scenarios.

Thanks a lot for your help and for maintaining this library! It's been super helpful!


Incorrect display of content when the program switch tab

I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Hello everybody. The problem is that there is an application in which the rootpage is tabs, with four child tabs. According to the logic of the application, the first tab should be hidden. I add to the first tab the attribute show =" false ", tab (on the tabbar) is hidden. Then, when the application loads, the first visible tab opens. In this tab, in the file * .ts (ie on the page that belongs to this tab) I define:
NgAfterViewInit () { This.app.getRootNav (). GetActiveChildNav (). Select (0); }
And turn on the desired, hidden tab. The problem is that the content of this tab is drawn from the very top, ignoring the page header, swam under it.

Expected behavior:
Correct display of content.

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Сordova CLI: 6.5.0
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.2.4
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 7
Node Version: v6.9.4
Xcode version: Not installed

Hello! Thanks for opening an issue with us! As this seems like more of a support question I will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


[Issue-1324] - adds required import for generating dnssec keys thru API

fixes #1324

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/367/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/324/


Replace IRemove Instruction with __REMOVE__ aux function

This change causes following type checking imprecision, which needs to be addressed.
* 2 type errors are detected.
[ParamTypeMismatch] argument assignment to first parameter _elem_ when function call from GlobalEnvironmentRecord.DeleteBinding (step 6.b.i, 11:20-58) to __REMOVE__
- expected: Purevalue
- actual  : String
[ParamTypeMismatch] argument assignment to second parameter _list_ when function call from GlobalEnvironmentRecord.DeleteBinding (step 6.b.i, 11:20-58) to __REMOVE__
- expected: List
- actual  : List[String]

Left to do:
analzyer

Result of sbt test:
[info] All tests passed.

Result of esmeta test262-test:
esmeta test262-test

I'm not sure of consequence of this PR on type analyzer. How can I check this?

sbt test : [info] All tests passed.


Feat/cs 37725

Closing this PR for now as there is a blocker from API side, and the release dates are yet to be decided.


Added entry for IndexOption-india in market-hours-database.json

Description
I have added an entry for IndexOptionIndia in the market hour database. The related issue is 6908
https://github.com/QuantConnect/Lean/issues/6908
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Non-functional change (xml comments/documentation/etc)

Checklist:

[ ] My code follows the code style of this project.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Closing for now until review addressed 👍


I typed in dotnet new console in vscode but didn't recognise it

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

I made a file and set it in vscode. Started a terminal typed dotnet new console and vscode didn't recognise it.


Tablet not working when i installed sync

idk my tablet just doesnt move

Sync is a portable software, not need to install any client software or edit computer settings. May other problem cause your tablet stop working.
You can try re-install table driver.( Remember backup your tablet settings)


Doesn't work with d3 on observable

see: https://observablehq.com/@randomfractals/hello-gemini
& https://observablehq.com/@d3/d3v6-migration-guide#group

@RandomFractals I've updated the code to use d3.v6's groups instead of nest. Let me know if it does not work.
Thanks!!

https://observablehq.com/@yhoonkim01/hello-gemini
It seems to work!


iptable just "return" by uid as the parameter u indicates

resolve this https://github.com/istio/istio/issues/6557

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: rokii
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mandarjog
Assign the PR to them by writing /assign @mandarjog in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @rokii. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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

/assign @mandarjog

/ok-to-test

@nmittler should be a better person to review this.

@costinm should take a look as well

@costinm I'm not sure the original intent of matching on the group.  Is this something that we can safely remove?

If group has to be an option,it is better to provide   -g param separately

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: nmittler, rokii
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mandarjog
Assign the PR to them by writing /assign @mandarjog in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rokii: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

@rokii: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-mixer-no_auth

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

@rokii: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-bookInfo-envoyv2-v1alpha3

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

@rokii: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-dashboard.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-dashboard

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

/retest

@rokii: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-v1alpha3.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-simple

prow/e2e-dashboard.sh
dfc9b8e6e1f9f00836e6c7fba01de691c22e9a9a
link
/test e2e-dashboard

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


feat: add pr action

What type of PR is this?

Check the PR title.

[ ] This PR title match the format: <type>(optional scope): <description>
[ ] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):
(Optional) Which issue(s) this PR fixes:

/fix:format

/fix:format

/fix:format


Illuminate/view has hidden dependency on illuminate/conditionable not specified in composer.json

Laravel Version: 8.81
PHP Version:  7.4.27
Database Driver & Version: standalone blade package.

Description:
I'm using Blade as a standalone templating engine without the full framework.
There is a hidden dependency in the illuminate/view package that will cause a Fatal Error At runtime.
Fatal error: Trait 'Illuminate\Support\Traits\Conditionable'
The ComponentAttributeBag requires Illuminate\Support\Traits\Conditionable but that package is not specified in composer.json

This trait is present in the support component which is a dependency of the view component in 8.x so this can't happen under the version you specified. However, it seems this dependency is indeed missing in 9.x so I've sent in a fix for that: https://github.com/laravel/framework/pull/40725
Thanks

I also think this already works in 9.x because conditionable is a dependency of support which is a dependency of view.

I double-checked again why this happens. It happens when you run composer install with the --prefer-lowest option, which I need in CI/CD. And since the Conditionable trait was added in illuminate/support 8.45 ( I think ) it blows up because it will install 8.0.0

@driesvints So basically the first tagged version of illuminate\view that uses the Conditionable trait should explicitly set the illuminate/support version to ^8.45". First introduced in 8.45

@calvinalkan I see. Yeah we can do that. Feel free to send in a PR 👍

@driesvints How would you go about this?
The problem also exists for other dependencies. For example, illuminate view will also break with any version of collections lower than 8.32 due to the value() helper not accepting args.
see here.

Yeah we'll need to update the constraints everywhere where a minimum dependency is needed of another component.


When will this be available for nodejs?

[Enter feedback here]
This feature is exactly what we were looking for, but we have a nodejs based bot. Is there an ETA for nodejs version?
Thanks!

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

ID: ee5b7a1a-86c5-37a6-5a47-61dc29d9fa57
Version Independent ID: a054ad1c-266f-9e28-bb7d-9fb4ee6c8988
Content: Introduction to adaptive dialogs - Bot Service
Content Source: articles/v4sdk/bot-builder-adaptive-dialog-Introduction.md
Service: bot-service
GitHub Login: @WashingtonKayaker
Microsoft Alias: kamrani

@shikshik Adaptive dialogs are currently in preview in JavaScript. See botbuilder-dialogs-adaptive on npm. In the upcoming release, adaptive dialogs should be a release candidate in JS.

Great! I will definitely try it out.
Thanks @JonathanFingold !

Hey, @JonathanFingold!
Is there any updates with the nodejs version? Or at least an example code / documentation?

@shikshik - The dev team still hasn't updated the readme for the npm package, but the JavaScript has preview support for adaptive dialogs. The JavaScript adaptive dialog samples are in the samples repo in the experimental/adaptive-dialog/javascript_nodejs folder. Many of the how-to docs for adaptive dialogs describe both the JavaScript and C# code, such as how to Create a bot using adaptive dialogs.

Thank you @JonathanFingold .
I already managed to find the samples after reading every single document available :)
Also managed to test it in our bot.
Everything seems pretty good, but we are waiting for the end result with a finished version of the adaptive dialogs.
I see that you are planning to finish development until November 15, will it be released as a production version as well or it might take a bit longer for further processes after dev period is finished?

The JS Version of Adaptive Dialogs is in active development. This is an open-source project and there are nightly builds you could consume. We don't yet have a "GA" Release schedule for Adaptive Dialogs on the Node platform.


SkeletonViewer: Added option to show local rotation axis on each bone.

Added support for new displayOptions: showLocalAxes and localAxesSize.
The new option showLocalAxes defaults to false but when enabled it lets you debug the rotations of a skeleton:

Only a nit, LGTM!

@Popov72, I removed some of the checks, but my IDE was complaining about risk of _utilityLayer being null so I left that one in there.

I noticed that the local axes only show if the skeleton is assigned to a mesh (ie mesh.skeleton = mySkeleton). If the displayMode  is set to DISPLAY_SPHERE_AND_SPURS this is always true, but for DISPLAY_LINES it might not be.
Adding the following to _buildLocalAxes works, but feels a bit awkward. Do you think it's an acceptable solution?
if (this.displayMode === SkeletonViewer.DISPLAY_LINES) {
	axisX.skeleton = this.skeleton;
}

@Popov72, I removed some of the checks, but my IDE was complaining about risk of _utilityLayer being null so I left that one in there.

You can use this._utilityLayer!.utilityLayerScene as you know that _utilityLayer won't be null/undefined.

I noticed that the local axes only show if the skeleton is assigned to a mesh (ie mesh.skeleton = mySkeleton). If the displayMode is set to DISPLAY_SPHERE_AND_SPURS this is always true, but for DISPLAY_LINES it might not be.

I think that's because the world matrices of the bones are not recalculated if the skeleton is not applied to at least one mesh of the scene.
I think setting the skeleton property of the axis is ok, as the skeleton will be processed only a single time even if set to multiple meshes anyway, and it avoid to put the burden on the user in this case. Maybe add a comment to explain why this line is needed.

Alright, thanks!

Linting is reporting an issue

I would argue that these should be in a single line system.  Otherwise that is ton of drawcalls.

I tried merging them to one mesh but I failed. Then I figured the use case is to debug one or a few skeletons, not win a benchmark competition. Any pointers on how to merge them is appreciated though.

@Pryme8 I figured out at least how to combine them to one mesh per bone...

Now it's good to go!! Thanks to @Popov72 and @Pryme8. I owe you beers!

Seems good to me. Only one ask: is that exposed in the Inspector?

Ok maybe with another PR: https://github.com/BabylonJS/Babylon.js/blob/master/inspector/src/components/actionTabs/tabs/propertyGrids/meshes/skeletonPropertyGridComponent.tsx#L47

I'm gonna message you about this too @reimund, as I am writing the SkeletonViewer docs as we speak and would like to include this in it.

I'm gonna message you about this too @reimund, as I am writing the SkeletonViewer docs as we speak and would like to include this in it.

Sure. I actually added all the other options to the table as well but figured it should not be part of this PR.
Slightly off topic, but I wonder if the displayOptions should be part of an enum or be static constants instead of magic strings?


Empty Response Body When Bad Request

What I expected the validation error from api, but got {}, this the example from postman

I am having the same issue. Additionally, if I return a plain text response () => 'Hello, World!', the response body from Scalar is empty. Neither of these issues are present with the swagger-ui provider.

If you're using bun as the runtime, the headers get set as an octet/stream instead of text/html or application/json. With Node, I don't run into the issue. If you go to the api endpoint you'll download a file instead of getting raw json/text/whatever.

If you're using bun as the runtime, the headers get set as an octet/stream instead of text/html or application/json. With Node, I don't run into the issue. If you go to the api endpoint you'll download a file instead of getting raw json/text/whatever.


Access to /dev/ttyUSB0

After inserting a device /dev/ttyUSB0 becomes available, but how do I make it such that the permissions are set such that a user or set of users has access to it? I'd expect a suitable udev rule would accomplish this.
In the context of Arduino, it would be useful if there were a NixOS arduino module, which would use the above non-existing mechanism.
https://stackoverflow.com/questions/59925105/nix-package-requires-sudo-to-access-usb-device provides further context, but should not be required to understand the above.

What would such a module do? To access /dev/ttyUSB0 your user needs to be in the "dialout" group (see users.users.<username>.extraGroups. If, for whatever reason the group is not "dialout" you can find out which one it is with ls -al /dev/ttyUSB0.

https://nixos.org/manual/nixos/stable/ does not even contain the word dialout.
man configuration.nix also does not specify what dialout is supposed to do.
Just because other operating systems might do that, doesn't mean NixOS also does that, unless the manual specifies that "it does the same as distro X".

There is nothing NixOS-specific about this. It is simply what udev does by default.
Not sure if the manual really needs a chapter on arduino/serial consoles, but it would definitely be a useful addition to the community wiki. That said, if you do have a good idea for what such a nixos module / chapter in the manual would contain I'm all ears.

We could choose not to invent a square wheel: https://docs.freebsd.org/doc/6.3-RELEASE/usr/share/doc/handbook/serialconsole-setup.html.
Ideally, when the Arduino IDE is started, it could just say "Please ask your administrator to add the following text to your configuration.nix and it will work. ".

Ideally, when the Arduino IDE is started, it could just say

Just because other operating systems might do that, doesn't mean NixOS also does that, unless the manual specifies that "it does the same as distro X".

I think you're fundamentally misunderstanding how NixOS and it's development work.
You're expecting there's people having full understanding and control over the entire operating system and applications; that may be the case for some proprietary OSs or BSDs, but it's certainly not the case of NixOS.
NixOS, being a GNU/Linux distribution, is a curated collection of software components (independently developed by many different groups) that has merely been configured to work more or less well together.
From a user perspective this is not great: sometimes it can be hard to even find which component is at fault when something goes wrong, but that's the reality of it.

https://nixos.org/manual/nixos/stable/ does not even contain the word dialout.

You can't reasonably ask for the NixOS manual to contain an explanation of the >80000 software packages
distributed. NixOS has its peculiarities (many) and the manual mainly covers that, along with other common tasks and how specific software interacts with each other, but it's not meant to be a comprehensive guide to Unix systems administration.

You're expecting there's people having full understanding and control over the entire operating system and applications; that may be the case for some proprietary OSs or BSDs, but it's certainly not the case of NixOS.

How do you mean "control"? Access rights? Or the ability to change literally everything across the stack? As for the first, I have root (and many developers have). As for the last, NixOS is uniquely suited to provide extreme customization and integration and a great out of the box experience.
In short, I have no idea what you are trying to communicate.

but it's not meant to be a comprehensive guide to Unix systems administration.

Clearly, whoever started this had an idea in mind for how groups should work, right? As such, that person could just write down "I was a Debian user and I have modeled everything that isn't documented like Debian". That seems like a perfectly valid way to resolve the lack of documentation. If you are saying NixOS is just a huge mess, then I suppose the question is: why and do you want to keep it like that?

I have root (and many developers have). As for the last, NixOS is uniquely suited to provide extreme customization and integration and a great out of the box experience.

Yes, but to some extents: for example I don't think NixOS patching the Arduino IDE to add a warning is a sensible idea.
If it's beneficial to all users the changes should be done in the original project, not NixOS. So, report that to the Arduino people.
In general these sort of changes requires maintaining a significant amount of code downstream, i.e. as patches outside of the original project. This is generally dreaded upon by maintainers because it slows down the process of upgrading a package (when a conflicts happens the patches need to be rebased manually) and divergences in the behavior of the programs can cause bugs and security issues.
NixOS already does some extensive modifications to the compiler toolchain and systemd, but these are absolutely essential for the goal of the project (purity, reproducibility, etc) and sometimes can't be upstreamed.

Clearly, whoever started this had an idea in mind for how groups should work, right? As such, that person could just write down "I was a Debian user and I have modeled everything that isn't documented like Debian".

No, I don't a single person in NixOS (or Debian) sat down and decided how groups should work. The default system groups are inherited by various components like systemd, CUPS, X.org etc. In this case the dialout group is something udev assigns to certain devices in the default rules, so it was simply carried over (0f1a368d75d2151b1ccc6da0cbd5e0f7510542e5).

That seems like a perfectly valid way to resolve the lack of documentation.

Uhm, I'm so sure: if we just refer to what distro X, we should also make sure it continues to act as NixOS does. At this point it's easier to document what NixOS does.

If you are saying NixOS is just a huge mess, then I suppose the question is: why and do you want to keep it like that?

No, I would say it's only a moderate mess ;)
The reason for why a lot of things are broken, missing or in an undesirable state is usually due to the lack of people volunteering their time to make them right. So, If you find this important I'd suggest you make the changes you'd like to see.

Clearly, whoever started this had an idea in mind for how groups should work, right? As such, that person could just write down "I was a Debian user and I have modeled everything that isn't documented like Debian". That seems like a perfectly valid way to resolve the lack of documentation.

No. Devices are added by udev. Whenever it is reasonable-ish, we just keep udev defaults. In general, in Nix* we keep upstream defaults when it doesn't create Nix*-specific problems, we don't bother whether Debian changes these defaults or not unless we have a complicated trade-off discussion and looking up arguments made by major distributions for their choces.

If you are saying NixOS is just a huge mess, then I suppose the question is: why and do you want to keep it like that?

NixOS is implicitly aimed at people who know enough of the GNU/Linux defaults and have detailed enough preferences to actually have a chance of benefitting from it. I want at least Nixpkgs to have reaonably close to upstream behaviours, because a) we already lack the throughput for doing update as well as people would prefer, b) I don;t want distro-specific weird behaviours.
Yes, if you go and write a Wiki page and put «as of March 2022» in the text, it will be a net positive. NixOS manual entry… I am not even sure about that. NixOS module for device access, probably useful.

Ideally, when the Arduino IDE is started, it could just say "Please ask your administrator to add the following text to your configuration.nix and it will work. ".

Cargo-culting like "Paste the following into your config" is universally bad advice that results in unnecessary cruft and sooner or later some really bizarre breakage.
I do agree that Arduino IDE could remind people to make sure their user is part of the relevant groups, however that is best left to upstream since they will have the most knowledgeable people for this. They can even keep track of which groups are needed for specific devices/actions and show a "ask your administrator to add your user to the X group(s)" when you are attempting stuff where that is relevant, if your user is not already in said group(s). That way it'll benefit all their users regardless of distro.
"Your administrator" should know how to do basic things like modifying user groups on whatever system it is you are using, so no need to specify that in a distro-specific way in the application. And if "your administrator" doesn't know how to do it yet, that is a thing that belongs in the distro-specific manual.


llama3.1 8B losses context

What is the issue?
llama3.1 doesn't seems to remember the context.
Here is an example:

Me:
Hello can you tell me how much is 56*9?
llama3.1:
That's a simple one!
56 * 9 = 504
Is that correct?
Me:
can you divide this by 4?
llama3.1
However, I don't see any specific numbers or values mentioned in the text that can be divided by 4.
If you're looking for a way to break up the content into smaller chunks, I could try suggesting some possible ways to reorganize it. For example:

Divide into sections: Break down the content into distinct sections or topics, such as "Core Principles and Capabilities", "Advanced Features", "Technical Details", etc.
Create a summary: Extract the main points or key information from the text and create a concise summary.
Organize by feature: Group related features or capabilities together, such as "Content Generation", "Knowledge Base", "Reasoning Capabilities", etc.

Please let me know if any of these options sound helpful!

On the other hand, when I use the same prompt with llama3 it work perfectly.
OS
Linux
GPU
AMD
CPU
AMD
Ollama version
0.3.0

Which model settings did you use?

@Damien2s Can you please verify that if this problem is fixed in latest Ollama and latest Llama3.1 recently uploaded? If no, please provide model settings as well.

I just give it a try and the problem seems to be solved with the latest version of Ollama. Thanks.


how can I create field with type array in orator models?

@sdispater  please help me to understand how can I store array field in model?

You can store it in a TEXT field and cast the array as a "dict", as explained in the docs.
Also consider creating a separate model for the array items and using relations to link the array items to your primary model.


nat_geo_1986 NGS.csv link

The NGS.csv looks like it links to the large file system--not sure how to load it with load_data, as I just get the three-line file.

It's a token describing the location of the real file.  This is going to take some work to fix the right way (because pyrfume and rfume will need to get user-associated API tokens to git-lfs).  We can fix this the fast way by hosting these files elsewhere, and adding a check that, after loading the .csv file, looks to see if it is this kind of "link" file, and then follows it to get the real data.  Bob would have to implement this in parallel.  Another option is to break this into about 30 chunks (behavior_1, behavior_2, etc.) so each one could be downloaded directly from GitHub in sequence and then concatenated.

Currently loads with pyrfume; rfume will need to implement the same logic to load it.  Have @KingFunk contact me if interested.


Permit to specify the State structure when using createStore

Feature request
According to this twitter discussion
Need
In order to getting more solid store typing, it could be nice to specify the type which will reflect the store. Currently, the state is inferred by the state initialization.
To be honest, it's already possible by this way :
type MainStare = {
  counter: number;
  name: string;
}

export const useMainStore = createStore<string, MainState>({
  id: 'main',
  state: () => ({
    counter: 0,
    name: 'Edimitchel',
  }),
  // ...
})

As you can see, the current API forced us to specify the first generic type (see here).
My request
My simple request is following : Could it be possible to swap these two lines ?
If accepted, I would create the PR
The result would be like this (with a better usage if we have nested or optional state) :
export type MainStare = {
  counter: number;
  name: string;
  team?: {
    name: string;
    createdAt?: Date;
  }
}

export const useMainStore = createStore<MainState>({
  id: 'main',
  state: () => ({
    counter: 0,
    name: 'Edimitchel',
    team: {
      name: 'Vue Community'
    }
  }),
  // ...
})

I guess, following could be subject to another issue by amending the createStore signature :
export type MainStare = {
  counter: number;
  name: string;
  team?: {
    name: string;
    createdAt?: Date;
  }
}

export const useMainStore = createStore<MainState>('main', {
  state: () => ({
    counter: 0,
    name: 'Edimitchel',
    team: {
      name: 'Vue Community'
    }
  }),
  // ...
})

To be honest, it's already possible by this way :

Does that actually work? When I try it on my end I get a Expected 4 type arguments, but got 2. error

I didn't tried because of low bandwidth during the Vue Conference. But yes, it's logical that doesn't work. I've just said it's technically possible, not working ;)

Oh my bad! I thought you said it was already possible in your original post 🙂  Happy conference!

@rijkvanzanten You've been right, the PR I proposed add defaults to others generic types

You can do
export const useMainStore = createStore({
  id: 'main',
  state: (): MainState => ({
    counter: 0,
    name: 'Edimitchel',
  }),
  // ...
})

This approach works well for me.

Cool, but do have a way to specify a action? Because the action type is a actions?: A & ThisType<A & StoreWithState<Id, S> & StoreWithGetters<S, G>>; and i did:
// abstractCrudStore.ts

export interface AbsctractActions<T> {
  getList(): Promise<void>;
  deleteItem: (id: number) => void;
  save: (form: T) => void;
  edit: (id: number, form: T) => void;
}

const abstractCrudStore = <T>(params: AbstractCrudStoreParams) =>
  createStore({
    id: params.id,
    state: (): AbstractState<T> => ({
      pageName: params.pageName,
      list: [],
      baseUrl: params.baseUrl,
      loading: false,
      tableFields: params.tableFields,
      paginationControl: {
        currentPage: 1,
        perPage: 7,
      },
    }),
    getters: {
      pagination: (state) => ({
        totalPages: state.list.length / state.paginationControl.perPage,
        totalRows: state.list.length,
      }),
    },
    actions: {
      async getList() {
        this.state.loading = true;
        const { data }: any = await request.get(this.state.baseUrl);
        this.state.loading = false;
        this.state.list = data.params;
      },
      async deleteItem(id: number) {
        await request.delete(`${this.state.baseUrl}/${id}`);
        this.getList();
      },
      save(form: T) {
        return request.post(`${this.state.baseUrl}`, form);
      },
      edit(id: number, form: T) {
        return request.put(`${this.state.baseUrl}/${id}`, form);
      },
    } as AbsctractActions<T>,
  });

export default abstractCrudStore;

To type a state is as @MartinMalinda did but i a have a problem to type the actions, some ideia?

I added https://github.com/posva/pinia/issues/85#issuecomment-631473019 to the documentation as a preferred way to do

Thanks, sorry for lacks of contribution.

Weird. The same but with object method syntax does not have type safety even when just inferring (no interface):
import { createStore } from 'pinia';

export const userStore = createStore({
  id: 'userStore',
  state() {
    return {
      name: 'Pinia'
    };
  },
  getters: {
    // @ts-expect-error ts2339 (no error thrown)
    nameCapitalized: (state, getters) => state.somethingThatDoesntExist.toUpperCase()
  }
})


[Debugger] Unable to STEP_IN inside object init() method

Description:
Unable to STEP_IN inside object init() method
Steps to reproduce:

Consider the below code snippet:

    public int age;
    public string firstName;
    public string lastName;

    function init(int age, string firstName, string lastName) {
        self.age = age;
        self.firstName = firstName;
        self.lastName = lastName;
    }

    function getFullName() returns string {
        return self.firstName + " " + self.lastName;
    }
}

public function main() {
    Person person = new Person(30, "Jack", "Sparrow");
    string personFullName = person.getFullName();
}

Add debug point in object initialization line in main() method.
-- In front of Person person = new Person(30, "Jack", "Sparrow");
Start the program in debug mode.
When the debug point get hit in object initialization line, do a STEP_IN

We can observe that the debug navigator is unable to STEP-IN inside the object init() method
Affected Versions:
Ballerina Swan Lake Preview 7
Language specification v2020-09-22
Update Tool 0.8.10

Unable to STEP_IN inside object init() method is only observed when we create an object for the first time. This behaviour is not observed when we create an object for the 2nd or 3rd time.
Consider the below code segment:
class Person {
    public  string name;

    function init(string name) {
        self.name = name;
        panic error("Error!!!");
    }

    function getName() returns string {
        return self.name;
    }
}

public function main() {
    Person person1 = new("Praveen");
    Person person2 = new("David");
}

When we create an object for the 2nd or 3rd time(In the above example person2 object), the following stack trace is observed from debug- adapter:

But when we create an object for the first time(In the above example person1 object), the following stack trace is observed from debug- adapter:

From the above stack trace, it seems like by the time we STEP_IN, the person1 object not created and it is in the class loading phase.

Unable to STEP_IN inside object init() method is only observed when we create an object for the first time. This behaviour is not observed when we create an object for the 2nd or 3rd time.
Consider the below code segment:
class Person {
    public  string name;

    function init(string name) {
        self.name = name;
        panic error("Error!!!");
    }

    function getName() returns string {
        return self.name;
    }
}

public function main() {
    Person person1 = new("Praveen");
    Person person2 = new("David");
}

When we create an object for the 2nd or 3rd time(In the above example person2 object), the following stack trace is observed from debug- adapter:

But when we create an object for the first time(In the above example person1 object), the following stack trace is observed from debug- adapter:

From the above stack trace, it seems like by the time we STEP_IN, the person1 object not created and it is in the class loading phase.

Closing since a similar issue is reported in https://github.com/ballerina-platform/ballerina-lang/issues/30739.


panicked at 'the runtime has not been set'

when i run application to this：
let stream = TcpStream::connect(server).await?;
rootthread ':' panicked at 'the runtime has not been set '
i use rust as a lib， does not have main func ，so i can not use "#[runtime:main]",or i  don't kown how to use "#[runtime:main]"

i want to kown how can i solve this problem？

When you say: "I use Rust as a lib" does that mean you're then calling it from C/C++? There's been conversations about writing a non-attribute version of the entry macros (likely block_on, see in part #73) which may help with this.
But currently it's not possible quite yet; apologies!

yes，i calling api（writted by rust） from c，and in my rust api progrem， i use runtime packge
and the problem as above。

I have a similar problem with clap: as the clap::App isn't Send I had to split the main function into a sync (clap) and an async part.  Given I need a nightly compiler anyway (i.e. it might break anytime) I didn't mind using the hidden runtime::raw::enter like this:
// sync part of main
runtime::raw::enter(runtime_tokio::TokioCurrentThread, async move {
    // async part of main
});


update dfe-analytics gem to 1.11.6

Trello card
Update DfE Analytics
Context
To help improve analytics, the Data Insights team would like us to enable an Entity Table Check job
Changes proposed in this pull request
Guidance to review

Closing until we update infrastructure to include an ActiveJob based queue processor.


Inconsistent behavior when setting FullWidth with Dialog

Bug type
Component
Component name
MudDialog
What happened?
When setting FullWidth property to false, under certain scenarios, the width of the dialog would be adjusted improperly. This is tricky to reproduce but I found one. Here is the screen capture that show the problem

Expected behavior
The width of the dialog should not be expanded, only the height.
Reproduction link
https://try.mudblazor.com/snippet/waGFFPvAFzUdzbqI
Reproduction steps

Click the buttons with the * in the name
Toggle the switch button
The width of the dialog now is bigger than previously
Click other buttons to see the normal behaviors

Relevant log output
No response
Version (bug)
6.0.2
Version (working)
No response
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

FullWidth in this scenario does just mean it takes up its full width, without your content having to do it.
You also have MaxWidth, read more about it here: https://mudblazor.com/components/dialog#configuration

@Garderoben I understand those settings but there is definitely an issue with FullWidth = false in some cases. If you look at my example, I have the dialog contains a grid of 3 textbox that have default settings with no size adjustment and one of them is hidden and only rendered when the toggle is switched on. The screen capture shown that when the third textbox is being rendered, the dialog somehow adjusted to different size even though the textbox size does not change at all.

@Garderoben I understand those settings but there is definitely an issue with FullWidth = false in some cases. If you look at my example, I have the dialog contains a grid of 3 textbox that have default settings with no size adjustment and one of them is hidden and only rendered when the toggle is switched on. The screen capture shown that when the third textbox is being rendered, the dialog somehow adjusted to different size even though the textbox size does not change at all.

yeah becuse you are using a mud grid inside and they are all set to auto grow. Its not a issue with the dialog.
https://try.mudblazor.com/snippet/cawFFbvUVJdtEzOi

@Garderoben I understand those settings but there is definitely an issue with FullWidth = false in some cases. If you look at my example, I have the dialog contains a grid of 3 textbox that have default settings with no size adjustment and one of them is hidden and only rendered when the toggle is switched on. The screen capture shown that when the third textbox is being rendered, the dialog somehow adjusted to different size even though the textbox size does not change at all.

yeah becuse you are using a mud grid inside and they are all set to auto grow. Its not a issue with the dialog.
https://try.mudblazor.com/snippet/cawFFbvUVJdtEzOi

So would that be an issue with MudGrid? Why would a grid grow on the width during the render if all the child elements of that grid are all the same size?


Add filtered params to plug metadata output

Adding HTTP params to plug metadata with filter sensitive values feature (copy and paste from Phoenix).
README as formatted and I added the options accepted by plug. I could keep only the options accepted reverting the format if you want.

Coverage decreased (-0.3%) to 73.333% when pulling dc03931625d5a8d778370349e5bdb664be24447a on thiagogsr:master into d01f0bccf5571473b5afc816ddcf7e02869abe9a on Nebo15:master.

Coverage decreased (-0.3%) to 73.333% when pulling dc03931625d5a8d778370349e5bdb664be24447a on thiagogsr:master into d01f0bccf5571473b5afc816ddcf7e02869abe9a on Nebo15:master.

Thank you. I'll make a more thoughtful review over the weekend, merge and release a new version

@dsnipe my name is Andrii or Andrew for people that have a hard time with pronunciation, not whatever you think it is.
Honestly, your approach gives me a crystal clear guess about your homeland: russia. Who else but a Russian would boldly assume the authority to rename me and make demands about how I should maintain my open-source software in a single message? This comes off as particularly rich amid the genocide war that russia started to erase Ukrainian freedom, language, culture, and right to live our lives the way we want.
You are not welcome here. Please abstain from using any of my open-source projects and perhaps consider going back to where you came from.

@thiagogsr The main had to be rewritten before we go with features like this one, sorry for such a long reply. I know you want this feature so I will manually merge it with the new codebase and release a new version ~next week. Thank you!


composer?

Tried to get this go with composer. Is it possible you will add a composer.json file later?

@brownrl ,@Senn0 ,
I added a composer.json and regitered at the http://packagist.org/
I also added a service hook but I'm not sure that works already.  We shall see on the next release.
Can you have a try and any suggestion to improvement is welcome ;-)

AWESOME!!!!!! thank you so much.
Know that "javascript" aren't the intended purpose of composer... but composer is becoming more of the catch all way of tying everything together in a project.


prettify.format is possibly undefined

I'm using this code with prettify 0.5.5-beta.1:
import prettify from '@liquify/prettify';

await prettify.format(sourceXml, { language: 'xml' });

I'm getting a TypeScript error on prettify.format:

Cannot invoke an object which is possibly 'undefined'.ts(2722)

The type definition for format is:
https://github.com/panoply/prettify/blob/b48fb59f6aa2a06286a2ca55356244dd539423f2/index.d.ts#L46
I'm not a TypeScript expert, but doesn't that mean that the format property itself may be undefined? Should it be something like this instead?
format: Format<Promise<string | undefined>>

As a workaround, this works but isn't ideal:
if (prettify.format) {
  await prettify.format(sourceXml, { language: 'xml' });
}

Thanks!

Hey @bmaupin
This project has moved to Æsthetic.


CSS to XPath?

My project depends on CSS selector to XPath conversion. I've got it implemented in javascript but I'd like to write a solid c++ version. It accepts any combination of CSS, XPath, CSS with XPath, and XPath with CSS expressions. Since it's type agnostic, my idea would be to use it for Element.find by default. That way libxmljs would have native support for both without having the user specify which. If I were to implement this and create a pull request would it be an acceptable feature in terms of the project scope or is it something you would like to keep separate?

It would be outside of the project scope to include this since it is not a libxml feature. However, we can reference it in the wiki so others can find it as they read through the documentation.


dataframe.ix is deprecated for pandas >=0.20.0

dataframe.ix[start_index:end_index].copy()
http://pandas.pydata.org/pandas-docs/stable/indexing.html#ix-indexer-is-deprecated
using influxdb (4.1.1)

Thanks for reporting this! Fix pushed for PR in #530


Integration with Leap Motion

Just got my Leap Motion and it is very precise with hand tracking it could work holding the PS Move Controller, or Navigation Controller.
Maybe removing the tracking of PS Eye and using the Leap Motion track with integration of Buttons and Feedback of the PS Move Controllers.
https://www.youtube.com/watch?v=hYZ2FgtDvxI

Just to add one small thing. It would not be necessary to use PSMoveService for the buttons because the are recognised natively in Windows. I agree that the tracking isn't as good if you hold something. I was surprised that they took the tool recognition (and a few other bits) out of orion (but it was probably to improve the tracking I guess).

https://www.youtube.com/watch?v=8q31ztsEYdo
hand tracking as Vive Controllers, just needed the PS Thumbstick and buttons

@andregm3 When we get PSNavi support baked in then you're welcome to use PSMoveService for it, but as @zelmon64 said, there are other more-native solutions for capturing button presses on arbitrary controllers.

yes, that was what i was thinking, when Navi support came out, but a shame it don't have vibration feedback, BTW did you see that RiftCat shared my video on they timeline ? i got like 3.000 views and added link to the project here, many more adepts to the PS Move !

@andregm3 You can already access the functions of a PSNavi by using the original version (and possibly the latest version) of ScpToolkit (it gets recognised as an Xbox controller).


⚠ Bofrost.es has degraded performance

In 5d5a36f, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1839 ms

Resolved: Bofrost.es performance has improved in 4fc6f9e after 13 minutes.


-mips1 double literals misdetected as two floats

From IDO 5.3 as1:
/*<PHONE_NUMBER>1804 8F818070 */  lw          $at, %got(FLT_10018C00)($gp)
/*<PHONE_NUMBER>1808 00000000 */  nop
/* 04180C 0044180C C4278C00 */  lwc1        $f7, %lo(FLT_10018C00)($at)
/*<PHONE_NUMBER>1810 C4268C04 */  lwc1        $f6, %lo(FLT_10018C04)($at)
...
glabel FLT_10018C00
/* 0B0C00 10018C00 47EFFFFF */ .float<PHONE_NUMBER>875

glabel FLT_10018C04
/* 0B0C04 10018C04 E091FF3D */ .float -8.41615545981605e+19

Do you happen to know how this would look like on a little endian machine? I'm wondering mainly about the register usage
Would it look like something like this? (notice the swapped registers)
lwc1        $f6, %lo(FLT_10018C00)($at)
lwc1        $f7, %lo(FLT_10018C04)($at)

I don't. Testing on PS1/PS2 on decomp.me just shows that those platforms don't support doubles at all.

I managed to test this on decomp.me and it seems like it flips the registers on little endian
Big endian (https://decomp.me/scratch/3O9WL):
lwc1    $f9,%lo(.rodata+0x28)(at)
lwc1    $f8,%lo(.rodata+0x2c)(at)

Little endian (https://decomp.me/scratch/Fzbf9):
lwc1    $f8,%lo(.rodata+0x28)(at)
lwc1    $f9,%lo(.rodata+0x2c)(at)

Fixed in release 1.12.2


Fix code scanning alert - Potentially unsafe external link

Tracking issue for:

[ ] https://github.com/edonyzpc/memos/security/code-scanning/1

TODO


Additional Query Parameters

Describe the feature
This feature would aim to expand upon the previous Engine class by adding additional (and optional) query parameters that are specific to each URL. This could be, for example,

https://www.google.com/search?q=someSearch&num=10 | generate a URL that will fetch a specific # of results for a query
https://chrome.google.com/webstore/search/someSearc?_feature=5stars | generate a URL that will fetch only 5 star extensions

as result of changing the Engine class to support this, the search function would also be tweaked in the process.
Provide any alternatives to the feature you've considered
Allowing the search function to directly accept additional query params as kwargs or a dictionary parameter to allow broader functionality at the user's discretion.  This is similar to the original proposal.
Additional information
This is based off the assumption that this project would want to move beyond minimalistic search querying. In the case a user would want to generate a URL with additional query parameters past the standard search query, they would have to manually write a wrapper for the search function which is for sure an inconvenience.

Great idea! Thanks for submitting.

Could you assign this task to me?


Issue in providing cw4_stake.wasm contract values for initiating

Hi, I'm facing with issue for prepare denom for  initiating cw4_stake.wasm contract?
These are  properties which are need for initiaing:
pub struct InstantiateMsg {
    /// denom of the token to stake
    pub denom: Denom,
    pub tokens_per_weight: Uint128,
    pub min_bond: Uint128,
    pub unbonding_period: Duration,
}

I've provided blow INIT but I'm getting error for providing denom value.
INIT='{"denom":"native","tokens_per_weight":1,"min_bond":1,"unbonding_period":{"time":3600}}'

My denum is udmotus but when I use it I get error as well.
Error:
Error: rpc error: code = InvalidArgument desc = failed to execute message; message index: 0: Error parsing into type cw4_stake::msg::InstantiateMsg: Invalid type: instantiate wasm contract failed: invalid request

Your both Denom type usage is incorrect.
If you want to see how it supposed to be used, generate schema for that contract and pay attention to the types.
Correct form would be:
{
   "denom": {
      "native": "ujuno"
   },
   "tokens_per_weight": 1,
   "min_bond": 1,
   "unbonding_period": {
      "time": 3600
   }
}

Also, next time please just questions on discord instead of creating an issue: https://discord.gg/b28Q7EvNGY

Hi, I changed the denom as you said but still there is an issue:
For bellow params:
INIT='{"denom":{"native":"utmotus"},"tokens_per_weight": 1,"min_bond": 1,"unbonding_period":{"time":3600}}'
I'm getting below issue:
Error: rpc error: code = InvalidArgument desc = failed to execute message; message index: 0: Error parsing into type cw4_stake::msg::InstantiateMsg: Invalid type: instantiate wasm contract failed: invalid request

Because Uint128 is parsed from String. You're missing quotation marks next to min_bond and tokens_per_weight.

Yea, I see types in this link  and they are not string, but after settin up those as string, issue fixed. Thank you so much
https://github.com/CosmWasm/cw-plus/blob/dd2ca3dd5558b4a65ca112b2f655ae043d956c20/contracts/cw4-stake/src/msg.rs#L12
I will close this conversation as answered and solved.


Select permissions list has radio buttons instead of checkboxes

Describe the bug
The Select permissions list should have checkboxes instead of radio buttons. When you select a group of permissions, the radio button and the blue tick disappears till you hover again on the group of permissions. This shouldn't be the experience.

AB#8784

@thewahome In design, multi-select is depicted by checkboxes while uni-select (I just made up this word ;) ) is depicted by radio buttons.
Also when you select on the top level, you have to hover to see if the group of permissions is selected, and this is not the expected behaviour.

#1087


default export EventEmitter class

Use export default for EventEmitter class to be in sync with the actual code which exports default using module.exports = EventEmitter. Fixes #95

I think this is ok but I would be great if someone who actually uses TypeScript can review this.
cc: @Stubb0rn @delta62.

CommonJS export module.exports = EventEmitter is not equivalent to export default EventEmitter in ES6 modules. Actually there is no equivalent for this type of export in ES6 modules. Sure, some module loaders add default export for CommonJS modules in runtime, but adding this to typings is misleading because default export is not in the actual code.

@Stubb0rn Agree that module.exports = EventEmitter is not equivalent to export default EventEmitter in ES6 modules since there is not default export in commonjs, but named export EventEmitter equivalent in commonjs is module.exports = { EventEmitter : EventEmitter }. So the appropriate way to apply create typing in this case is export default.

The JavaScript code exports the EventEmitter function both as a default and as a named property of the module.
Here is an example of using the current type definitions in a NodeJS app. I am able to compile and run it.
So I'm not sure exactly what problem we're trying to solve here. Maybe you can provide us with a little more information as to how you're consuming the module or what errors you're seeing?

@delta62 Thanks for the info, I didn't notice that is exported as named property as well, I thought it is just exported as default. I think we can close this in this case.


Rearrange and refactor dialog_node.gd to be split up into multiple scripts

Having a single big script file that accounts for a million things is going to be a huge bottleneck extremely quickly, like a snowball effect.
To avoid it developing into a 3000+ line nightmare, it must be split up into multiple single-responsibility scripts early on.
Additional benefit is it's much easier to interface with dialogic and implement new things without majorly altering pre-existing behavior, as well as easier development and resolving of merge-conflicts if any even arise.
Closes https://github.com/coppolaemilio/dialogic/issues/45

Just be careful when making changes, there is a big PR (#104) in the works, with a lot of changes in resources handling. I did not change the behavior of dialog_node.gd, but I changed some lines to integrate it with the new system.

Continued in https://github.com/coppolaemilio/dialogic/pull/197

Resource Reformat branch is based on this proposal


It will be covered by the figure and reduce visibility, if the job name is too long

In the figure below, call / compare-renovate-logs / generate logs for default branch and Run npx renovate --schedule= --require-config=ignored --dry-run korosuke613/homepage-2nd overlap.

I found Mamaid.js provides a way to customize the style of diagrams, but mermaid in GitHub Flavored Markdown does not accept this customization.
Mermaid.js provides way to customize some style by inline that called frontmatter. I found properties that can be used to customize style in gantt diagrams. It seems that leftPadding property is related to the width of section title, so I tried this code at https://mermaid.live/.
---
config:
    gantt:
        leftPadding: 1000
---

gantt
title Compare Renovate
dateFormat  HH:mm:ss
axisFormat  %H:%M:%S
section call / Get version
Waiting for a runner (9s) :active, job0-0, 00:00:01, 9s
Set up job (0s) :job0-1, after job0-0, 0s
Get latest major renovate version (8s) :job0-2, after job0-1, 8s
Complete job (0s) :job0-3, after job0-2, 0s
section call / compare-renovate-logs / Setup
Waiting for a runner (7s) :active, job1-0, 00:00:01, 7s
Set up job (0s) :job1-1, after job1-0, 0s
Get latest major renovate version (3s) :job1-2, after job1-1, 3s
Complete job (0s) :job1-3, after job1-2, 0s
section call / compare-renovate-logs / Generate logs for default branch
Waiting for a runner (6s) :active, job2-0, 00:00:14, 6s
Set up job (1s) :job2-1, after job2-0, 1s
Run actions/checkout@v3 (1s) :job2-2, after job2-1, 1s
Run actions/cache@v3 (3s) :job2-3, after job2-2, 3s
Run npx renovate --schedule= --require-config=ignored --dry-run Kesin11/renovate_config_sandbox \ (12s) :crit, job2-4, after job2-3, 12s
Run actions/upload-artifact@v3 (0s) :done, job2-5, after job2-4, 0s
Post Run actions/cache@v3 (0s) :done, job2-6, after job2-5, 0s
Post Run actions/checkout@v3 (0s) :job2-7, after job2-6, 0s
Complete job (0s) :job2-8, after job2-7, 0s
section call / compare-renovate-logs / Generate logs for topic branch
Waiting for a runner (7s) :active, job3-0, 00:00:15, 7s
Set up job (2s) :job3-1, after job3-0, 2s
Run actions/checkout@v3 (1s) :job3-2, after job3-1, 1s
Run actions/cache@v3 (1s) :job3-3, after job3-2, 1s
Run npx renovate --schedule= --require-config=ignored --dry-run Kesin11/renovate_config_sandbox \ (50s) :crit, job3-4, after job3-3, 50s
Run actions/upload-artifact@v3 (0s) :done, job3-5, after job3-4, 0s
Post Run actions/cache@v3 (0s) :done, job3-6, after job3-5, 0s
Post Run actions/checkout@v3 (0s) :job3-7, after job3-6, 0s
Complete job (0s) :job3-8, after job3-7, 0s

Custom configuration is works! Unfortunately, if you copy & paste the same code to github, you would not to see same result. It seems that GitHub does not accept frontmatter configuration. So, I gave up to solve this issue by customizing diagram style.
It is possible for actions-timeline to omit section titles that are too long, but it may make it difficult for users to identify each one. Any ideas?


use python package manager to clean this repository

package manager, e.g., pdm

https://github.com/hust-open-atom-club/S2VulnHub/commit/b6c9907583c20e1a073619aa485595ca6d671efd


UXComponents.NonCanvas tests being excluded accidentally

Describe the bug
When we split the canvas and non-canvas UX packages, we forgot to update the testables in the manifest json. As a result, we weren't running any of our UX components tests (buttons, sliders) and therefore they've gone out of date/broken.
Additional context
We'll need to re-add both canvas/noncanvas testables to the manifest and fix the out of date tests.

Completed by #11113.


Commands/ts/scan

Issue #, if available:
Add SCAN command to TS
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing for now until we'll complete SCAN design


fixing TypeError: data argument

if you get TypeError: data argument can't be an iterator is because of the zip version you are using

Since the release 0.24.0, we don't need to generate the list from the zip anymore. I ran the notebook on colab and it didn't have issue but then when I tried to run it on paperspace and floydhub that's when I got the error. So one can either update or generate the list


Allow literal '.' in /api/v2/domains/name

fixes #832

The CI failure is irrelevant to this PR. See #849 .


Invalid option docker run

Using Docker 1.9.1 on Windows 8 and pulled down the latest docker-neo4j repo
Ran a Docker build from the 2.3.1 directory using the tag neo4j/neo4j.  Tried running with STDIN back:
 docker run -i -t --rm -p 7474:7474 -v //d/<path to data>:/data --name graphdb neo4j/neo4j

Every time I get ": invalid option".  Not sure if I am missing an argument after the image?  Note, that the volume to the image's data directory on my Windows machine is empty.  Wondering if I am doing a rookie mistake with Docker or just missing something fundamental when try to run the neo4j image?

@MatthewDavidYoung Are you using Docker Toolbox?
I'm not sure about the intricacies of running Docker on Windows. One thing I suspect is that the path you specify on the host side for the volume needs to be under c:\Users\<your-user> in order for it to be automatically mounted into the Docker host VM.
Can I suggest that you try this with a simple, standard Docker image (e.g. hello-world or debian) so that we can see if it's a problem with the Neo4j image or the command line arguments that you're providing?

@benbc Thanks!  Newbee to both Docker and VirtualBox.  Didn't realize that volumes from the outside world on Windows have to reside under the C:/Users/ directory.  Is this a Docker thing or VirtualBox thing?

@MatthewDavidYoung It's due to the way Docker is set up to work on Windows. Details here.


Feature/create facet place

Rebased branch and made all changes listed in PR #32

Coverage increased (+0.09%) to 96.7% when pulling 2d2bb505c86eac3ed3dbd907033e2b44c3662710 on feature/create_facet_place into 55d70f79987d713494c2e73318a92653f017b4d7 on development.

Coverage increased (+0.09%) to 96.7% when pulling 3d22ea7c0eea1e2717d9ab6b4373f07c364852d6 on feature/create_facet_place into 55d70f79987d713494c2e73318a92653f017b4d7 on development.

@barnabyalter ,
Changed code according to your feedback last week. I had to change a test value for a test that I was not working on for it to pass. Thanks.


Model Training Notebook

Search before asking

[X] I have searched the EvaDB issues and found no similar feature requests.

Description
We'd like to have a colab notebook for ludwig-based model training.
Use case
No response
Are you willing to submit a PR?

[ ] Yes I'd like to help by submitting a PR!

Duplicate of #999


Add  info on adding teammates to insights page

In the Insights feature page, we should include a portion that says something like:

After you've created your insights page, share it with your team.

Add an explanation why
Add directions
Add a link to this video: https://www.youtube.com/watch?v=L5ztLP1O7BY

Hi @BekahHW , can I work on the issue?

@adiati98
This is the next issue I will be working on.


Add optional S3 VPC endpoint

Option for adding a VPC S3 gateway endpoint to route S3 traffic over private network. More details can be found in the readme changes.
Also updates CircleCI to 2.0. Release job is commented out because I haven't tested it.

Feel free to make a new release when you merge this.