feat: add blueprint icon and more redirects

Description

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Feature]: Add flag to delete unused assets on theme push

What area(s) will this request affect?
Theme
What type of change do you want to see?
Substantial change to existing feature
Overview
Maybe there is a good reason why this doesn't exists, but how come assets that no longer exists in my local files are not being deleted on the remote when running shopify theme push?
With that said, perhaps it would be a good idea to create a new flag that makes it so assets are being deleted?
Perhaps --delete (would essentially be the opposite of --nodelete)
Motivation
I was having an issue that I spent a lot of time on, just to find out that the error was caused by a legacy asset file that was no longer used (that only existed on the remote). Therefore my dev env worked fine, but production didn't. I assume webpack was trying to load this asset even though it wasn't used anymore.
With that being said, I don't really see the point in not having the option for the CLI to remove assets that no longer exists in the changes I'm pushing.

@Shopify/theme-code-tools


Not working on latest Pi OS

Using a pizeroW and debian bookworm based PiOS I only get a black screen after startx, no matter what URL I use.  I can see midori running though, just nothing ever shows up on screen.
using the "Legacy" bullseye based PiOS loads pages as expected.

I would change the URL being loaded into the browser to say google.com and try to see if that starts. If it does, then the website is where I would start with.
Try loading the URL on a computer if it is being served on the same LAN.

i did, url doesn't matter, it never even gets the white midori screen, or the URL bar showing it's loading

These are potential things which you can check, i would think about solving it this way.

you can get away from the console, and try loading the rpi screen using VNC server.
Are you able to load midori using the desktop? If not, what errors does it give?
Is there a different browser that you can load on debian in kiosk mode instead of midori?

isn't the whole point of this project to run midori on a pi-zero without a regular desktop install?  is there another browser that would work?  desktop+browser on a pizero is painful no matter what OS version, I'm not going there.
if the answer is that we just can't do this on bookworm due to the it needing more resources than the zero has, that's fine, but the readme should say so.  bookworm takes double the disk space too, 8GB sd card minimum when bullseye does fine on 4GB

The whole point of the project is to run a browser in kiosk mode, loads a website from somewhere,  so that it eventually shows up on a screen. If you had to debug issues, it would be helpful to load the browser on the desktop just for the purposes of figuring out why it doesnt work.
The last update for the repo was in 2022, and the project installation is running fine till date. Updates have been stopped, because i dont intend to fix anything which is not broken.

understood, and on bullseye it's not broken, but bookworm it is.  I'm happy with that, but knowing it going in would have saved a lot of time


Create the Demn Folder

Create the Demn folder -> so that all the dimensions are present in one folder

Can u assign in under iwoc?


iOS10 gets device.iphone failure

iOS10 browser Useragent iPhone OS replaced iOS.

Merged manually! Thanks!


Vulnerability roundup 109: wordpress-5.7.4: 1 advisory [9.8]

search, files

[ ] CVE-2021-44223 CVSSv3=9.8 (nixos-21.05)

CVE details
CVE-2021-44223
WordPress before 5.8 lacks support for the Update URI plugin header. This makes it easier for remote attackers to execute arbitrary code via a supply-chain attack against WordPress installations that use any plugin for which the slug satisfies the naming constraints of the WordPress.org Plugin Directory but is not yet present in that directory.

Scanned versions: nixos-21.05: 3b422991781.
Cc @basvandijk

See also: #147912

Great. I personally would like to declare this a wontfix because it only affects people that use plugins that are not from the Wordpress.org Plugin directory as far as I understand. If we still want to fix this (which would be relevant for people who have third-party plugins) we would probably need to update stable to 5.8 which I think was never done before.

Also see https://make.wordpress.org/core/2021/06/29/introducing-update-uri-plugin-header-in-wordpress-5-8/#comment-41689


Detect incompatibility and raise a relevant exception

Problem to Solve
When there is an incompatibility between Client Java and the running Grakn Server, the exception thrown by the client seems unrelated to the real cause of the problem. In fact, the error message may even be incorrect, given that the keyspace does exist with the given name.
Current Workaround
If encountering this exception for the first time, only searching the web or asking the community can lead the user to the solution.
Proposed Solution
Have Client Java to identify the incompatibility and throw an exception with a helpful message. e.g. Client Java version 1.5.3 does not support the running Grakn Core server. Please refer to the documentation of client Java to ensure compatibility.
Additional Information
N/A

This issue is still relevant in 2.0.

The discussion from https://github.com/graknlabs/client-nodejs/issues/47 may be of relevance here.

To summarise:

Server should expose an RPC endpoint to describe its version number
Protocol for this endpoint should remain stable permanently* to preserve backwards compatibility
The client can then detect incompatibility and raise a relevant exception

We should also consider:

Declaring the product name (TypeDB or TypeDB Cluster) in the response
Exposing this endpoint as a client feature that a user can call manually to get basic server info

https://github.com/vaticle/typedb-studio/issues/567

Implemented in #421


reduce binary size

Hi,
Rust-analyzer works quite well in my daily work. However, upgrade often failed in bad network environment.
Here is the log from vscode.
INFO [8/5/2020, 3:41:26 PM]: Extension version: 0.2.266
INFO [8/5/2020, 3:41:26 PM]: Using configuration {
  lruCapacity: null,
  files: { watcher: 'client', exclude: [] },
  notifications: { cargoTomlNotFound: true },
  cargo: {
    autoreload: true,
    noDefaultFeatures: false,
    allFeatures: false,
    features: [],
    loadOutDirsFromCheck: false,
    target: null
  },
  rustfmt: { extraArgs: [], overrideCommand: null },
  checkOnSave: {
    enable: true,
    extraArgs: [],
    command: 'check',
    overrideCommand: null,
    allTargets: true,
    noDefaultFeatures: null,
    allFeatures: null,
    features: null
  },
  cargoRunner: null,
  runnableEnv: null,
  inlayHints: {
    enable: true,
    typeHints: true,
    chainingHints: true,
    parameterHints: true,
    maxLength: 20
  },
  completion: {
    addCallParenthesis: true,
    addCallArgumentSnippets: true,
    postfix: { enable: true }
  },
  callInfo: { full: true },
  updates: { channel: 'stable', askBeforeDownload: true },
  serverPath: null,
  trace: { server: 'off', extension: true },
  procMacro: { enable: false },
  debug: {
    engine: 'auto',
    sourceFileMap: {
      '/rustc/<id>': '${env:USERPROFILE}/.rustup/toolchains/<toolchain-id>/lib/rustlib/src/rust'
    },
    openDebugPane: false,
    engineSettings: {}
  },
  lens: { enable: true, run: true, debug: true, implementations: true },
  hoverActions: {
    enable: true,
    implementations: true,
    run: true,
    debug: true,
    gotoTypeDef: true
  },
  linkedProjects: null,
  withSysroot: true,
  diagnostics: {
    enable: true,
    enableExperimental: true,
    warningsAsInfo: [],
    warningsAsHint: []
  }
}
DEBUG [8/5/2020, 3:41:27 PM]: Issuing request for released artifacts metadata to https://api.github.com/repos/rust-analyzer/rust-analyzer/releases/tags/2020-08-04
DEBUG [8/5/2020, 3:41:40 PM]: Downloading file of 6072910 bytes size from https://github.com/rust-analyzer/rust-analyzer/releases/download/2020-08-04/rust-analyzer-mac.gz to /Users/dudu/Library/Application Support/Code/User/globalStorage/matklad.rust-analyzer/rust-analyzer-macae42334b42
ERROR [8/5/2020, 3:46:16 PM]: Bootstrap error [Error: unexpected end of file
	at Zlib.zlibOnError [as onerror] (zlib.js:170:17)] {
  errno: -5,
  code: 'Z_BUF_ERROR'
}

Reducing binary size using tools like upx could be a good way to improve the development experience .
⋊> ~/Library/Application Support/Code/User/globalStorage/matklad.rust-analyzer upx rust-analyzer-mac            15:51:34
                       Ultimate Packer for eXecutables
                          Copyright (C) 1996 - 2020
UPX 3.96        Markus Oberhumer, Laszlo Molnar & John Reiser   Jan 23rd 2020

        File size         Ratio      Format      Name
   --------------------   ------   -----------   -----------
  17729580 ->   5996560   33.82%   macho/amd64   rust-analyzer-mac

Packed 1 file.

I'm not sure I see the point. The binary is compressed with gzip, and after UPX and gzip -9 the file size is 5.6 MB (vs. 5.8 MB for the GitHub release). Do you think that reducing the binary size by 200 KB would improve the experience on unreliable networks?

Stripping the debug symbols from the Linux build yields 5.7 MB after gzip -9, vs. the 7.4 MB file on GitHub. But we've recently stopped stripping the releases to make it easier to debug any crashes reported by the users.

Thanks for reply.
I'm using Mac OS, but I noticed the binary size was increasing during the upgrade(17M after upgrade finished).  We can see that in the log you've posted:
DEBUG [8/5/2020, 3:41:40 PM]: Downloading file of 6072910 bytes size from https://github.com/rust-analyzer/rust-analyzer/releases/download/2020-08-04/rust-analyzer-mac.gz to /Users/dudu/Library/Application Support/Code/User/globalStorage/matklad.rust-analyzer/rust-analyzer-macae42334b42
ERROR [8/5/2020, 3:46:16 PM]: Bootstrap error [Error: unexpected end of file
	at Zlib.zlibOnError [as onerror] (zlib.js:170:17)] {
  errno: -5,
  code: 'Z_BUF_ERROR'
}

(Look at the URL and the zlib.js error.)
I'm not sure why it's uncompressing so slow in your case. It takes about 130 ms for me. Maybe the Node implementation is slower?

Thanks @lnicola
I thinks the http proxy in vscode I used didn't work well, which caused that error. I change another proxy and it works.
BTW, is there anyway I can download and unzip it manually to make rust-analyzer work normally?

Sure, you can download the binary from GitHub, uncompress it, and either:

put it in ~/Library/Application Support/code/User/globalStorage/matklad.rust-analyzer/rust-analyzer-mac
put it somewhere else (like ~/.cargo/bin) and configure the path in your Code settings

Thanks for your kindly reply. 😄


Change base url to use cloudant user.

Currently script, tries to work with URL_BASE="https://$USER.cloudant.com" where $USER is the user of local machine (computer host), which doesn't necessary same as OPEN_WHISK_DB_USERNAME the actual cloudant account username. Changed script to work with OPEN_WHISK_DB_USERNAME instead of $USER.

Good catch, thanks.


Row/Column Level Data Filters

Feature or Bugfix

Feature

Detail

Add row/column level filters for table share items in data.all

Relates

https://github.com/data-dot-all/dataall/issues/348

Important Call Outs for This PR

(1) data.all will NO LONGER support cross account sharing of table data to QuickSight Principals (i.e. QS Groups)

This PR introduces a more efficient sharing mechanism to directly share with foreign IAM principals (not support with QS Principals at the moment)
Access to data via QuickSight in same account is still supported as well as sharing of QuickSight dashboards
Please look at comments in issue for more details on sharing mechanism

(2) data.all will NO LONGER support "old_share" naming convention

Sharing of dataset tables was improved to reuse share DB and resource link resources as of this PR released in version v2.3.0
"old_share" naming convention can be identified as shared database resources that follow the naming convention source_db_name + '_shared_' + shareUri (new naming convention is ``source_db_name + '_shared`)
To update to new naming convention please revoke and recreate the table share on data.all >= v2.3.0
More details on migration path to be provided closer to release of v2.7.0!

(3) As part of upgrade from v2.6 -> v2.7 data.all admins will have to verify + reapply all of the table shares in data.all

There are already built-in ECS Tasks to easily manage verify + reapply for you!
This will allow data.all to migrate all table shares to the new direct share to foreign IAM principals and clean up unused LakeFormation permissions (wherever applicable)

(4) With this PR there will be a change to the way preview-ability of table data + metadata works

Please read comment below for more details

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)?

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization?

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features?

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users?

Have you used the least-privilege principle? How?

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

Testing

[ ] Create Data Filter  (both COLUMN + ROW)
[ ] List Data Filters
[ ] Attach Filters to Share Item Table
[ ] Update Filters to Share Item Table
[ ] Remove Filters from Share Item Table
[ ] Attach Filters to Share item Table on same table with same name --> violate uniqueness constraint!
[x] Approve, Verify, Revoke on a Table Share w/ Default Full Access ( + Worksheet Query)
[x] Approve, Verify, Revoke on a Table Share w/ Column Filter ( + Worksheet Query)
[x] Approve, Verify, Revoke on a Table Share w/ Row Filter ( + Worksheet Query)
[x] Approve, Verify, Revoke on a Table Share w/ Multiple Column + Row Filters ( + Worksheet Query)
[ ] Delete Data Filter w/ Existing Share Item Filter(s) --> Error Thrown (must remove share item)
[ ] Delete Data Filter
[ ] Delete Dataset Table --> All Table Data Filters deleted

Comments on Table Preview-ability
Currently in data.all (prior to this PR) - the accessability of table information is a such:

If a Table if Unclassified

Users can Preview the Table without requiring share with no restrictions (up to 50 rows)
Users can view Columns and Metrics for the Table without requiring share

If a Table is Secret or Official

Users cannot Preview or see Columns or Metrics if there is no share
But once a user gets sahre access to a particular table

Users can Preview the Table without requiring share with no restrictions (up to 50 rows)
Users can view Columns and Metrics for the Table

This is problematic when it comes to granular shares because what if a user should not be able to see data for all columns in preview EVEN AFTER gaining share access (i.e. column filter to include specific subset ONLY)?
This PR Handles table information access in the following way:

If a Table if Unclassified

Users can Preview the Table without requiring share with no restrictions (up to 50 rows)
Users can view Columns and Metrics for the Table without requiring share

If a Table is Secret or Official

Users cannot Preview or see Columns or Metrics if there is no share
If there is a share for a user to this particular table

Users can view Columns and Metrics for the Table
If share has no filters --> Users can Preview the Table without requiring share with no restrictions (up to 50 rows)
If share has filters --> Users can Preview the Table with only the same level of access as they have on the on filtered table share item

There is an edge case that is important to call out on the above:

If a given user is a part of 2 groups and each group has access to the same source table with different filters applied

How to resolve which level of data access is shown on the Preview Tab
Currently, it is at random which of the 2 (or more) types of previews are shown (i.e. whichever record is returned first when checking permissions in backend DB is used)

Because of the above complication - a more straightforward proposal would be to remove "Preview" altogether for Secret or Official tables

At the point Preview is available to a user the user must already be given some level of share access anyway
We would still keep Columns and Metrics` conditionally exposed once a user is given share access to these type of confidentials tables

Please let me know your thoughts on this - I am more inclined to switch to the model where Preview is only an option for Unclassified datasets: @petrkalos @dlpzx @SofiaSazonova

Hi @noah-paige, reviewing the key decisions on this PR:

Quicksight groups -> agree. In addition we could point out at next steps involving QS IAM IC instead of using QS groups and QS users as done now
Deprecation of old/upgrade with ECS reapply needed - agreed on all. We just need to make sure to include it in the release notes
Preview/Metrics on shares with filters: First of all, I don't like the random selection of role to read the preview hahahah. Secondly, previewing is very useful for the discovery of datasets (especially before share); but for confidential/secret datasets ensuring a very restricted data access is more important that some users being able to see actual real sample data. In my opinion, priority number one should be that there is no information disclosure. Again preview is useful for data discovery (before sharing), when data is already shared as you pointed out users already have some level of access. In short, I agree with option " a more straightforward proposal would be to remove "Preview" altogether for Secret or Official tables" because protecting secret/official data is a MUST, while the impact of not previewing already shared data is not that great for users

Tested:

migration script
create filter ----> ERROR: An error occurred (AccessDeniedException) when calling the CreateDataCellsFilter operation: User: arn:aws:sts::XXXXX:assumed-role/dataall-aburrida-ia476u0x/dataall-aburrida-ia476u0x is not authorized to perform: lakeformation:CreateDataCellsFilter on resource: arn:aws:lakeformation:eu-west-1:XXXXXX:catalog:XXXXXXX because no identity-based policy allows the lakeformation:CreateDataCellsFilter action ----> I think we are missing permissions in the dataset role that is used in the lf client no?

* create filter ----> ERROR: `An error occurred (AccessDeniedException) when calling the CreateDataCellsFilter operation: User: arn:aws:sts::XXXXX:assumed-role/dataall-aburrida-ia476u0x/dataall-aburrida-ia476u0x is not authorized to perform: lakeformation:CreateDataCellsFilter on resource: arn:aws:lakeformation:eu-west-1:XXXXXX:catalog:XXXXXXX because no identity-based policy allows the lakeformation:CreateDataCellsFilter action` ----> I think we are missing permissions in the dataset role that is used in the lf client no?

Yup - you are exactly correct, had manually scoped down permissions on IAM Role but slipped my mind to include in dataset stack IaC for PR. Should be reflected now

It is a great implementation of the feature, thanks @noah-paige! Some things that we should not forget to do:

[ ] Add documentation!
[ ] Add in the description of this PR some messages to warn users:
- Deprecated old shared db names
- force upgrade of lake formation to version 3 or more

It is a great implementation of the feature, thanks @noah-paige! Some things that we should not forget to do:
* [ ]  Add documentation!

* [ ]  Add in the description of this PR some messages to warn users:
  - Deprecated old shared db names
  - force upgrade of lake formation to version 3 or more

Call outs in PR should already be there - I will update User Guide documentation and push as a separate PR


Security Update: laminas/laminas-diactoros

See: https://github.com/advisories/GHSA-8274-h5jp-97vr

See: https://github.com/Noctis/kickstart-app/pull/76


Implement HEXPIRE command

Sets the expiration, in seconds, of a field in a hash.
Reference: https://redis.io/docs/latest/commands/hexpire/
Client-Server Spec:
Command File: ./internal/modules/hash/commands.go
Test File: ./internal/modules/hash/commands_test.go
Command: hexpire
Module: constants.HashModule
Categories:  contants.HashCategory, constants.WriteCategory, constants.FastCategory
Description: (HEXPIRE key seconds [NX | XX | GT | LT] FIELDS numfields   field [field ...]) Sets the expiration, in seconds, of a field in a hash.
Sync: true
NOTE: You may need to change the internal representation of the hash to hold a more complex data type that includes the field's value and expiry time instead of just the value. If the representation is already changed from a previous implementation, use the current one.
Embedded Spec:
Command File: ./echovault/api_hash.go
Test File: ./echovault/api_hash_test.go
Documentation
Add documentation to ./docs/docs/commands/hash/HEXPIRE.mdx

I'll work on this next.

Based on our current implementation of expiration elsewhere, I think updating hash to use a struct for the value would be the cleanest approach. When I was looking over the codebase thinking through other options, trying to track expiration elsewhere felt inconsistent and hacky. So I'm thinking something like this -
type HashValue struct {
	Value    interface{}
	ExpireAt time.Time
}

type Hash map[string]HashValue

@osteensco I agree. This is the approach I had in mind as well.


Status Filter Always Displays 'Unknown' Events

When using the 'Status' filter in Uchiwa, selecting 'Critical' or 'Warning' will still display 'Unknown' events
Expected Behavior
Unknown events should only display when the status filter is set to 'All Status' or 'Unknown'. When filtering by 'Critical' or 'Warning', the 'Unknown' events should be filtered away.
Current Behavior
When using the 'Status' filter in Uchiwa, selecting 'Critical' or 'Warning' will still display 'Unknown' events
Steps to Reproduce (for bugs)

Have active events in Sensu, both unknown and warning/critical
Filter the status to warning/critical
Unknown events are still displayed

Context
Not sure if this is intended design or not but I would expect the filter to behave according to the name, especially given that there is a specific filter option for unknown checks
Your Environment

Uchiwa version used: 0.21.0
Sensu version used: 0.26.5
Operating System and version (e.g. Ubuntu 14.04): CentOS 7.2

I'm no longer seeing this behavior in Uchiwa -- Only thing that has changed in the stack is an upgrade from Sensu to 0.28.4. and Uchiwa restarts.
Not sure what was happening when I came across this issue. Closing anyway.


RPP Resize Mirror Normalize Bugfix

@kiritigowda @rrawther This PR adds a minor bugfix for MaskRCNN to converge with RPP's RMN.
We need this in master sooner than the other RPP open PRs, since master is used by default for training.
QA tests for this function in Tensor Test Suite + CI will be added incrementally, but for now, here's the screenshot below to show that accuracies are okay and Training Convergence is achieved.

100% tests passed, 0 tests failed out of 28


Typo

Oh, yes, it's definitely worth going through the whole peer-review dance to fix a documentation typo that involves moving one character. Great use of my time and mental bandwidth. Oh yeah.

Can you push to master without a PR?  You are the owner of this code and I think you should be able to do that if needed.

I agree that I should be able to; but I am not. Because of FOLIO's commitment to "quality".


Fix rs-logger device reset reconnect bug

@maloel do you feel this is still relevant?

@maloel do you feel this is still relevant?

I think it needs re-examining: much of this code has completely changed. I know of no current issue and this PR doesn't explain how to reproduce an issue.
Let's close unless @shlon can verify it's still relevant.

Hi I am not sure if you will are able to see my message since I am not longer under Librealsense area in github
I was part of RealSense under Intel as an employee
If I recall correctly the issue was that if the logger is running and we reset the camera with ipex( that’s what we called it at the time) the logger does not recognize the camera again
Steps to reproduce

Run only rs-logger as a standa lone and not the full librealsense suit
Connect camera
we see FW logs
Reset the camera with ipex
We do not see new FW logs
*   We should be able to see FW logs

Regards,
Marwan Shlon
From: Eran @.>
Sent: Tuesday, 4 June, 2024 12:00
To: IntelRealSense/librealsense @.>
Cc: Marwan Shlon @.>; Mention @.>
Subject: Re: [IntelRealSense/librealsense] Fix rs-logger device reset reconnect bug (#4691)
@maloelhttps://github.com/maloel do you feel this is still relevant?
I think it needs re-examining: much of this code has completely changed. I know of no current issue and this PR doesn't explain how to reproduce an issue.
Let's close unless @shlonhttps://github.com/shlon can verify it's still relevant.
—
Reply to this email directly, view it on GitHubhttps://github.com/IntelRealSense/librealsense/pull/4691#issuecomment-2146986157, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGWOPOUEFFYQBKW5T6PGXPDZFV62DAVCNFSM4IOFZWVKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJUGY4TQNRRGU3Q.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Better variable naming

Why
For people not knowing the Alba paper well, the variable names are hard to follow.
What
We suggest here to change the variable names to be more descriptive and add a mapping to the paper.

Ideas from @curiecrypt:
Sp: prover_set
np: set_size
nf: threshold or verifier_threshold (?)
u: proof_size
d: search_depth
q: selection_probability
r: num_of_repetitions
b: bound
s: set_item
s_list: item_list
t: tuple_index
v: attempt_index
H0: item_hash
H1: prefix_hash
H2: final_hash

Ideas from @tolikzinovyev :
np - prover set size
nf - adversary set size
d - search width / number of search trees
q - final selection probability
r - number of tries (just to make it shorter, attempts is also fine)
b - DFS bound
s - element (to be consistent with the paper)
s_list - I'm guessing it's a (partial) tuple? tuple / element sequence
t - tree index
v - try index (just to make it short, attempt is also fine)
H0 - bin hash function

@rrtoledo, @djetchev, @tolikzinovyev. Here is a list of all suggestions we have. State your choice by putting x beside it.
Also, add more lines if you have more suggestions.
Sp:

prover_set x

np:

set_size x
prover set size

nf:

threshold x
verifier_threshold
adversary set size

u:

proof_size x

d:

search_depth x
search width
number of search trees

q:

selection_probability
final selection probability x

r:

num_of_repetitions
number of tries x
attempts

b:

bound
DFS bound x

s:

set_item
element x

s_list:

item_list
tuple
element sequence x

t:

tuple_index
tree index x

v:

attempt_index x
try index

H0:

item_hash
bin hash function
element_hash x

H1:

prefix_hash x

H2:

final_hash x

@curiecrypt I reordered the variables (to link t with d, and v with r), added a few options and voted.
I have a preference for Merkle/tree terminology as I think it makes it easier to reason with (especially with a whiteboard).
I am not sure about d, I chose so far search_width but I wonder if choosing forest/polytree might be better: we keep the picture in mind, but forests/polytrees are not as "famous" as trees. We also have to agree first on our representation: whether the trees are disjoint (forest) or not (polytree).

Added my letter T to my choices. No matter what we choose, we should make sure the naming is consistent. For example, if v is "attempt index", r should be "number of attempts", not "number of tries". Or if q is "final_selection_probability", H2 should be "final hash".

Added my letter T to my choices. No matter what we choose, we should make sure the naming is consistent. For example, if v is "attempt index", r should be "number of attempts", not "number of tries". Or if q is "final_selection_probability", H2 should be "final hash".

@tolikzinovyev I agree with you about the consistency.
Now, I will make a list for the final version of each variable. @rrtoledo , @tolikzinovyev let me know if you have any problems with the final decision.

Looks good, just one thing, if we choose d: search_width, to be consistent as @tolikzinovyev said, let's rename t:search_index (or t:search_counter)

Looks good, I'm just not sure about nf. What are the tradeoffs between different options? Maybe I just don't understand the logic behind "threshold".

Looks good, just one thing, if we choose d: search_width, to be consistent as @tolikzinovyev said, let's rename t:search_index (or t:search_counter)

search_index sounds good

I used search_counter cause we used retry_counter for $v$. I can change if you wish

Looks good, I'm just not sure about nf. What are the tradeoffs between different options? Maybe I just don't understand the logic behind "threshold".

I think the threshold word better complies with the literature, but I am not insistent about it. I tried to choose the most voted-on options.

I used search_counter cause we used retry_counter for v . I can change if you wish

They definitely should be consistent! I have a slight preference for "index".

Looks good, I'm just not sure about nf. What are the tradeoffs between different options? Maybe I just don't understand the logic behind "threshold".

I think the threshold word better complies with the literature, but I am not insistent about it. I tried to choose the most voted-on options.

Like from "threshold multi-signatures"?

I think threshold comes more from the application (Peras) than Alba as there is no real link between threshold and lower bounds.
Would you prefer lower_bound for nf?

I think threshold comes more from the application (Peras) than Alba as there is no real link between threshold and lower bounds. Would you prefer lower_bound for nf?

lower_bound sounds good

Any thoughts about "proven set size"? I feel like it says more than "lower bound". The prover proves that he has nf elements (> nf actually).
By the way, are we talking about the unweighted case only or both? If the later, is "size" the right word for us (applies to np too)?

Any thoughts about "proven set size"? I feel like it says more than "lower bound". The prover proves that he has nf elements (> nf actually).
By the way, are we talking about the unweighted case only or both? If the later, is "size" the right word for us (applies to np too)?

I think we should consider a generic name, for all versions.
However, proven_set_size does not cover the exact meaning in my head. Isn't it possible to have a proof that has a size >nf. In that case, this name does not make sense. Also, lower_bound means that we at least want a set of size nf but it could be larger.
Actually, the terms and variable names are a bit confusing. But, the I deduce this when I read the paper. If I deduce it in a wrong way, then we must be so careful to explain it better to other users.

I think @curiecrypt and I prefer putting the emphasis on the lower bound idea, hence threshold or lower_bound.
I think "set_size" might be misleading (it is not the set size but a lower bound on it |Sp|>nf) and "proven" does not bring much, just the idea of goal.
I remember we mentioned in the past target_bound, that could be an adequate compromise.

So far, this is only for the centralized PR.
When we implement (decentralised) weight and reuse the centralised code, I expect us to call telescope_centralised.Prove on a new set with specific parameter (from weighted/decentralised_weighted.setup). So the variables inside of centralised should not matter to (decentralised) weight too much.

@curiecrypt @rrtoledo I think you misunderstood what I mean by "proven set size". It is not what the prover has, it is what the verifier is convinced the prover has. Specifically, the verifier knows the prover has nf+1 elements, but he cannot know the prover has nf+2 elements.

We forgot a few parameters:
lambda_sec

soundness_param

lambda_rel

completeness_param

h

round_hash

h_usize

round_number

I think we should consider a generic name, for all versions. However, proven_set_size does not cover the exact meaning in my head. Isn't it possible to have a proof that has a size >nf. In that case, this name does not make sense. Also, lower_bound means that we at least want a set of size nf but it could be larger.
Actually, the terms and variable names are a bit confusing. But, the I deduce this when I read the paper. If I deduce it in a wrong way, then we must be so careful to explain it better to other users.

Technically you are right. If the lambdas are big enough, or np/nf small enough, u can be greater than nf indeed! Hence u can also be greater than |Sp|. I wonder however if you are not getting confused now between the "proof size" u and nf. haha
I agree we have to be very careful with the variable names. We do not want to confuse anyone, starting with us.

So is nf vs nf+1 the only drawback of "proven set size", or there are others? Just trying to understand pros and cons.
My strategy is this: if I know what alba does and I see a term like "proven set size", will I know what it refers to (e.g., np, nf, or something else)? With "proven set size", it most likely refers to nf. With "threshold", I really wouldn't know if it's np, nf or maybe something else. "lower bound" almost certainly refers to nf given that it's in "approximate lower bound arguments", but maybe it's a lower bound on the number of elements the proven needs to succeed. "target" seems too general (i.e. not very descriptive), I would certainly need to look up what it refers to.
Feel free to disagree with me. I just want to synchronize us on this.

I want to dismiss any potential confusion. The name "proven set size" to me can be confusing and defintiely is not accurate for the reasons I listed before (nf/nf+1, and let's steer from any "prove" related word).

nf given that it's in "approximate lower bound arguments", but maybe it's a lower bound on the number of elements the proven needs to succeed.

It also is if you look at the definition of soundness.
The word "target" is general indeed, I only suggested it to replace "proven" and make sure to differentiate nf's name from the "dfs_bound". We could have "lower_bound", "set_bound", ...

!Future!
I remember that I commented that we should comply with the names in the paper.
However, limit does not seem to cover its actual functionality.

@curiecrypt @tolikzinovyev We forgot a few parameters and variable names:
lambda_sec

soundness_param R

lambda_rel

completeness_param R

h (= hash(v,t, element_sequence))

round_hash R

h_usize (= h1( v,t, element_sequence ) = Uni_np(h) )

round_number R
round_id R

limit

limit R
step R

@curiecrypt @tolikzinovyev Make sure to vote here too!

what is the reason for calling the function parameter hash? Isn't that just an array of bytes?
For the oracles

let's steer from any "prove" related word

What's wrong with "proven" though? It refers to "proof of knowledge".

@curiecrypt @tolikzinovyev We forgot a few parameters and variable names:
lambda_sec

soundness_param RG
lambda_sec T

lambda_rel

completeness_param RG
lambda_rel T

h (= hash(v,t, element_sequence))

round_hash RG

h_usize (= h1( v,t, element_sequence ) = Uni_np(h) )

round_number R
round_id RG

limit

limit R
step RG

@curiecrypt @tolikzinovyev Make sure to vote here too!

We should try to keep variable names short also I think (soundness_param, completeness_param).
What does limit signify, number of steps made or number of steps remaining?

How is h different from H1?


ISSUE-308: Registry UI Exception

Fixed various react libraries version since auto-updating (via npm install) breaks the UI.

Thanks @shahsank3t for fixing this issue.


start disassembler

Closes #41

Codecov Report

Merging #70 (e3668e9) into main (7d0a05f) will decrease coverage by 1.41%.
The diff coverage is 6.73%.

@@            Coverage Diff             @@
##             main      #70      +/-   ##
==========================================
- Coverage   52.59%   51.18%   -1.42%
==========================================
  Files          74       78       +4
  Lines        6335     6514     +179
==========================================
+ Hits         3332     3334       +2
- Misses       2859     3036     +177
  Partials      144      144


Improve Debugging for template errors

Currently if a helm template generates invalid yaml you get cryptic error messages like this:
Error: YAML parse error on mysql/templates/deployment.yaml: error converting YAML to JSON: yaml: line 106: mapping values are not allowed in this context

When trying to debug this, there is currently no easy way to do this, unless you printline debug your templates. This is not nice. In this example the line number 106 reflects the line in the rendered template, which is not visible to the user at all. This should be improved.
A simple way to improve this, would be to print the rendered templates in debug mode (right after this https://github.com/helm/helm/blob/865c46c014cdb7622f97ae287ee92fb8a280f3a9/pkg/action/install.go#L427,L431)
This should include line numbers, to easy debugging.

Example code:
diff --git a/pkg/action/install.go b/pkg/action/install.go
index 8f1b5528..56c96811 100644
--- a/pkg/action/install.go
+++ b/pkg/action/install.go
@@ -19,6 +19,7 @@ package action
 import (
        "bytes"
        "fmt"
+       "bufio"
        "io/ioutil"
        "os"
        "path"
@@ -429,6 +430,24 @@ func (c *Configuration) renderResources(ch *chart.Chart, values chartutil.Values
                return hs, b, "", err
        }

+       // If the template is broken and generates non yaml files (e.g. by skipping line endings etc)
+       // you get an error message by that there is an error in line xxx of the file deployment.yaml.
+       // However the line number is the line number of the generated yaml "text" after the template
+       // engine, which is rather stupid and does not know yaml at all. Debugging those issues
+       // is hard, therefore we print the rendered templates with line numbers in debug mode.
+       c.Log("Result after template processor\n--------------")
+       for fName, f := range files {
+               scanner := bufio.NewScanner(strings.NewReader(f))
+               scanner.Split(bufio.ScanLines)
+               c.Log(fmt.Sprintf("#Source:%s\n---", fName))
+               count := 0
+               for scanner.Scan() {
+                       count++
+                       c.Log(fmt.Sprintf("%d\t%s",count,scanner.Text()))
+               }
+       }
+
+
        // NOTES.txt gets rendered like all the other files, but because it's not a hook nor a resource,
        // pull it out of here into a separate file so that we can actually use the output of the rendered
        // text file. We have to spin through this map because the file contains path information, so we

This is even more important if you are using the "tpl" function to interpolate values.yaml.

Any news on this?
Besides the suggestion above, it would also be very useful to be able to have the option to render the intermediate YAML that is being converted to JSON.
Thx

Duplicate of #7088, which was fixed with #7556.


Built-in JavaScript constructs are not suggested in the debug repl

Testing #10997
I would expect Boo to suggest Boolean, etc. There are also Math and probably many more that I don't know about.

With the fix for https://github.com/Microsoft/vscode/issues/11186 I'm now considering all scopes, which fixes this issue too.


error in disconnect for disk corruption, not inconsistency

f54580e7e from Core#10195

utACK. Noted ApplyTxInUndo made static rather than changing the return type in the test version.


AadHttpClient constructor removed from 1.5 plusbeta release

Category

[X] Question
[X] Bug

Expected or Desired Behavior
We should be able to use the AadHttpClient in 1.5 plusbeta. Thats what the beta is for, right?
Observed Behavior
The Typescript Definition file states     Excluded from this release type: __constructor
So how should we use the AadHttpClient?

Possible duplicate of https://github.com/SharePoint/sp-dev-docs/issues/1964

We are working on fixing this with updated npm packages within upcoming days. Sorry for the inconvenience.

This is what I use and it works:
let _client = new (AadHttpClient as any)(this.context.serviceScope, '')

Solution here #2093

Is it just my lack of understanding or did 1.5.1 remove the export of a bunch of stuff @VesaJuvonen ?
In 1.5.1 index-internal.d.ts (which is referenced from index.d.ts) there is /* Excluded from this release type: AadHttpClient */ as well as a bunch of other things.
Seems like there was quite a bit of change in the pipeline from 1.4.1 to 1.5.1 no? At least
the below seems to indicate that to me :)
//
// It is copied by a rule from config/post-copy.json during the build.
// You should not add it to Git.
//
// For documentation, please see sp-core-library/etc/test-api-pattern/README.md

export * from './index-internal';```

Sorry - this should have been closed a long time ago.


Fix Flame Design System Santander

Fix. It has no code but it has designers kit.
Update. The name of the Kit to Flame Design System Santander

There's a conflict due to updates in the master repo after I forked it. So I'll fork it again and do the PR after pulling the new repo.


feat: Create "About" page for Mentorship

Is your feature request related to a problem? Please describe.
Create the About page for Mentorship on the navbar**(Mentorship >> About)**
Please assign yourself to the task if working on it🙏
Describe the solution you'd like

Design: https://www.figma.com/file/ncdevYZK7NGuTK3hc6mP4e/Design-Kit-Draft-(WCC)?type=design&node-id=54821-25572&mode=design&viewport=2608%2C-276%2C0.19&t=0KxB8FJuumD2KskU-0

Content: https://docs.google.com/document/d/1PJjyWfgi3r-awNzJyISR2tVgrLXpSgpoX809rkwx1Dg/edit#heading=h.78q4sam49eix

Reference: https://womenwhocode.github.io/london/

Describe alternatives you've considered
Additional context

assigned @nverbic


User guide for migrating jobs from collab to dev

resolution_fixed   |    by<EMAIL_ADDRESS>
Provide a guide to existing users of accesscollab on how they can start running jobs from accessdev
Mostly how to sync home directories, at this stage work under the assumption that collab will remain available while people are still using

Issue migrated from trac:110 at 2024-01-31 18:04:22 +1100

<EMAIL_ADDRESS>changed status from new to closed

<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>commented

https://trac.nci.org.au/trac/access/wiki/Moving from Accesscollab

<EMAIL_ADDRESS>removed milestone (was accessdev v1.0)

<EMAIL_ADDRESS>commented

Milestone accessdev v1.0 deleted


use GitHub Actions for CI

as mentioned here the UCB-MDS cookiecutter does this so we could adapt / integrate with theirs
https://github.com/pyOpenSci/cookiecutter-pyopensci/issues/25#issuecomment-809529342
@xmnlab and @mbjoseph discussed Azure Pipelines in #13 but my impression is that GitHub Actions is a million times easier to use, especially for newbies (and people like me who aren't so newbie but do not want to spent their whole lives thinking about CI pipelines)

Thanks @NickleDave I agree GitHub actions > Azure at present!

@NickleDave you're right. nowadays muchos han migrado de azure pipelines para github actions (including me :) )

oh yea. actions are so nice for windows-mac-linux. i'm using them now on all of our packages. including earthpy and abc-classroom.
just a note that i have a few reservations about poetry.  it seems  to be very  pip focused. i  need to revisit our cookie cutter again but pip and conda do  not place  nicely together. And for some applications (SPATIAL!!)  pip is not optimal given GDAL conflicts. so we need to think carefully about what best practice recommendations look like. i may also be wrong about poetry  but that was my first take when i looked at it. i've slowly been moving towards conda and conda-lock to lock environment  builds .  very open  to any and all feedback  here and to build upon the great work that @ttimbers has done!!

Tagging @TomasBeuzen here because he has more experience than I do mixing poetry with conda. AFAIK from my discussions with him, the two do play well together, and we plan to better explain that in our book.
@TomasBeuzen - can you elaborate a bit here on your experiences mixing  poetry with conda? And any cons/challenges in doing so?

I'm a bit convoluted in my workflow. I use conda exclusively for environment management and for installing packages into those environments where possible. I use poetry to make pure Python packages, but I don't use it for dependency management 😬 . I don't have much experience installing packages into an environment using conda and poetry, but I suspect you'll run into the same kinds of problems you get when mixing conda and pip.

Ah, I see. I think I misunderstood what you told me before Tom!

Just to be clear - conda environments work great with poetry and I use the two together like that all the time, I'm just not too sure about how well the two mix together when installing things :)

thank you all for this. it will be great to sort this all out! even mixing conda  forge and defaults can cause conflicts  so i'm just  sensitive to those pain points!  i do hope to find some time to play with  poetry to  better understand  what it offers! (and to  revisit our cookie cutter as well!  And i seriously appreciate  everyone's input  here - thank you!! keep the discussion and suggestions coming!

My usage lines up with @TomasBeuzen -- I use conda as a quick and dirty way to manage environments, e.g. for a project  that's mainly experiments + analysis, not a library
I use poetry for developing pure Python packages, and I also try to use it to "pin" the development environment for myself.
I for sure agree that there are both pros and cons to every tool and I definitely don't mean to suggest we should impose poetry as the one true way.
I just really like how easy it can be for pure Python packages and I bet that captures a lot of use cases, especially for devs that we want to support. That's why I like the book from @ttimbers and @TomasBeuzen ... an advantage might be making it as easy as possible to get started for as many people as possible, without having to worry about the 12 different ways
As for cons ... witness some of my interactions with the poetry maintainers here:
https://github.com/python-poetry/poetry/discussions/3757#discussioncomment-436537
😬 Not my proudest moment but I think the discussion highlights a lot of the pain points in packaging.
I am still myself fighting to build up a packaging "concept map" in my head, and understand how all the moving parts relate to each other.
I was excited to learn from one of the maintainers that we will soon be able to declare metadata in a "tool neutral" section in pyrproject.toml files:
https://github.com/python-poetry/poetry/discussions/3757#discussioncomment-436232
so there will be less 'lock-in' and tools like conda-build will be able to leverage it as well
flit just added experimental support for this:
https://github.com/takluyver/flit/pull/393

Hi Friends!! This is an old issues and i'm cleaning up all of these older issues as we are now updating our cookie (using copier). We have decided to use hatch's backend for our work here given its ease of use, connection to the community and PyPA and also really great and communicative maintainer. copier will set this all up. thanks to @Midnighter
I will close this issue but please feel free to reopen or create new issues if you have any questions, concerns or ideas!! I think the new cookie is going to be great!


Comparison with pytorch 2.0

Hi folks.
Not an issue per se but I was looking at kernl to explore better inference for transformer models.
I saw the recent pytorch announcement and their approach with dynamo and inductor and triton seems similar.
Are there plans to align these two efforts?

Hi, thank you for your message.
For Bert we have included Inductor in the benchmark (it's the Triton compiler from PyTorch 2.0).
In Inference, PyTorch 2.0 perf are quite far behind (in corner case it may even be slower than doing nothing).
As written by Mark from PyTorch team, Inductor is thought for training more than inference. In particular it can do something similar to gradient checkpointing in a much more aggressive way. Have a check the PyTorch dev forum for more detailed info.
Moreover, Inductor is generic and optimize kernels based on automatic compiler rules, kernels from this lib are made manually and tend to be much more optimized as we are free to leverage any new paper, etc.
Let me know if it answers you question, or if it needs some clarification.

Thanks for explaining.
I was trying to use it a week ago with FLAN T5 but ran into some errors - I'll give it a try next week and see how much faster it is in BF16 compared with Inductor.
Ty!

Tks, not tried Flan but if you have some error please report here with reproductible code and we will investigate

@acostin1 Have you been able to run vanilla PyTorch nightly with Flan ?
It seems that PyTorch 2.0 has an issue with some T5 models... and so we have the same.

I have not - I am running Pytorch latest (with their version of Triton) and it doesn't even compile. Are you folks planning to make Kernl compatible with Pytorch 1.14 nightly?

I'm getting this error when trying the BERT example. Python 3.9.5, pytorch nightly
"name": "BackendCompilerFailed",
"message": "_compiler raised Exception: Invoking operators with non-Fake Tensor inputs in FakeTensorMode is not yet supported. Please convert all Tensors to FakeTensors first. Found in aten.embedding.default(*(Parameter containing:\ntensor([[-0.0568,  0.0299,  0.0031,  ...,  0.1054,  0.0106, -0.0408],\n        [ 0.0033, -0.0552, -0.0054,  ..., -0.0317, -0.0055, -0.0274],\n        [-0.0132,  0.1356,  0.0669,  ...,  0.0010,  0.0773,  0.0414],\n        ...,\n        [-0.0321,  0.1130,  0.0724,  ...,  0.0187,  0.1477, -0.1466],\n        [-0.1248, -0.1178, -0.0843,  ..., -0.1224,  0.0079, -0.1960],\n        [ 0.0142, -0.0268,  0.0035,  ..., -0.0068,  0.0106, -0.0071]],\n       device='cuda:0', requires_grad=True), FakeTensor(FakeTensor(..., device='meta', size=(1, 8), dtype=torch.int64), cuda:0), 1), **{})\n\nSet torch._dynamo.config.verbose=True for more information\n\n\nYou can suppress this exception and fall back to eager by setting:\n    torch._dynamo.config.suppress_errors = True\n",

@acostin1 Hello, Yes we noticed this error on the last nightly. It doesn't happen on the pinned version we have in requirements.txt

I know but we're trying to use best of both worlds ... having you guys fix it will increase the chance of using it.

FYI, we are switching to a more recent PyTorch nightly: https://github.com/ELS-RD/kernl/pull/220/files

@acostin1 we have switched to a recent nightly, so you can now have best of both worlds :-)
Please, note that right now PyTorch is a bit buggy. Moreover, the way CUDA graph is implemented has a large memory footprint. We will work on this aspect.


Power BI REST API - error: PowerBINotAuthorizedException

Dear Microsoft.
I'm unable to extract activities from Power BI REST API. I get the following error:
{
"error": {
"code": "PowerBINotAuthorizedException",
"pbi.error": {
"code": "PowerBINotAuthorizedException",
"parameters": {},
"details": [],
"exceptionCulprit": 1
}
}
}
I have followed this guide: https://docs.microsoft.com/en-us/power-bi/admin/read-only-apis-service-principal-authentication

created an Azure AD App
created AAD group
assigned new app / enterprise app to new group
allowed service principals to use read-only Power BI admin APIs in Admin portal by adding group from #2 in Power BI admin portal

Note: I'm trying to extract the activity data from Premium capacity.
I hope you can help me understand what I'm missing.
Br,
Christoffer

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

ID: 76dd7616-4a1c-fe01-1b6b-6190bd2fdb63
Version Independent ID: 93839448-4a4b-5489-14d4-6eebe4b3d34a
Content: Enable service principal authentication for read-only admin APIs - Power BI
Content Source: powerbi-docs/admin/read-only-apis-service-principal-authentication.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @paulinbar
Microsoft Alias: painbar

Perhaps this article is relevant too: https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-admin-consent-workflow

I'll ask our IT Admin to remove the Power BI role set in the portal. I hope it will solve the problem. Thanks!

Hi again, @Koldmunch, ok, great. If that doesn't work let us know and we'l seek more help. I am going to close this issue right now, but please reopen if removing the role doesn't help. Thanks!

Hi @paulinbar it worked for me. Took a while but the NO PBI admin consent required was hard to get as it was "counter intuitive" for me :).
Here how the permissions for the Enterprise App needs to look like

Then this app needs to be in a security group

Which Security group needs to be added to the PBI Adm Portal in Read-Only Adm API


Handle two columns with same name in dataframe validation

df = pd.DataFrame({
    'a' : [1,2,3],
    'c' : [7,8,9]
})
df = df[['a', 'a', 'c']]

df['a'].dtype

AttributeError: 'DataFrame' object has no attribute 'dtype'

Shall we address this in alphabase? I think this is general issue in pandas?


Unable to retrieve video information. Please make sure the link/ID is correct

Checklist

[X] I have checked the issue page for duplicates
[X] I am running the latest version (download here)

Edition
Windows GUI Application
Describe your issue here
Unable to retrieve video information. I'm getting the error Please make sure the connection/identity is correct I'm getting the error
Fırçala help me.
Add any related files or extra information here
No response

@siuramka and you help me.


[BUG] spec test for pod_memory_hog failing

Describe the bug
The test spec test for pod_memory_hog is failing https://github.com/cnti-testcatalog/testsuite/actions/runs/9020615104/job/24793752233 after this was merged. It seems to be a problem with the spec for that test and not the test itself.
This might be caused by the upgrade to Litmus which changed some experiments.  The spec may need to be updated to match.
To Reproduce
Steps to reproduce the behavior:

spec spec/workload/resilience/pod_memory_hog_spec.cr

Expected behavior
spec should pass
Screenshots

Seen during testing of PR https://github.com/cnti-testcatalog/testsuite/pull/1949


Update Client SDK example with multi-org support

Upgrade to Fabric SDK Go v1.0.0
Refactor client_sdk/go/sample/main.go to easily switch between orgs via env vars
Provide a sample connection file
Update test-network tutorial to use the sample app with different orgs
update-connection.sh now consolidates all peers that can host FPC enclaves

Signed-off-by: Marcus brandenburger<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #562
Special notes for your reviewer:
Does this PR introduce a user-facing changes and/or breaks backward compatability?:

@TrueAbc can you please have a look at this?

Squashed and rdy for merge


Wording in argocd-root.yaml [ci skip]

I chose this wording since I'd like the text to pick either directory OR folder. And I chose directory.

Makes sense 👍


Spelling

re-based on master

do u want more of this kind of PRs?

@SimonCropp
Sure! Code improvements are always welcome :)


How to change post permalink

How to change post permalink "example.com/post/new-post.html" to "example.com/new-post.html"

I'm assuming your example should read: /post/new-post/ to /post/new-post/ as I don't believe Hugo supports .html extensions on single pages (it's certainly not default functionality).
To change permalinks in Hugo, see: https://gohugo.io/content-management/urls/#permalinks
[permalinks]
  post = "/:title"

Here is some reasoning for why Hugo doesn't have support for new-post.html - https://discourse.gohugo.io/t/links-without-a-trailing-slash/831/16

He's looking to do some SEO magic to shorten the link. Does Netlify support redirects?


Fix settings page skeleton isn't shown

Details

The setting skeleton isn't shown when we open it while the data is loading.
Fixed Issues

$ https://github.com/Expensify/App/issues/30362
PROPOSAL: https://github.com/Expensify/App/issues/30362#issuecomment-1779684592
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Requires internet connection to sign in
QA Steps

Sign out from the app
Sign in back to the app
While the data is still loading, open the Settings
Verify you see a skeleton on the settings page and the setting menu

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/50919443/27928b7f-2b1c-4ad9-905d-ad2ba261f1fa

Android: mWeb Chrome

https://github.com/Expensify/App/assets/50919443/b2f95697-438b-4560-8bdd-a9189e018ee0

iOS: Native

https://github.com/Expensify/App/assets/50919443/d8197600-aa7d-4d57-a8b8-eb022b6420b4

iOS: mWeb Safari

https://github.com/Expensify/App/assets/50919443/a7459fb9-c862-4242-8af1-779cb3c29dce

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/50919443/78722f84-dbf9-46b0-989e-3a26a50065a5

MacOS: Desktop

https://github.com/Expensify/App/assets/50919443/2b4f4059-5923-400e-9bf3-ec8ac0f0c54d

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/luacmartins in version: 1.4.1-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


What lib version

HI there, thanks for your work! May I ask what version of libraries you're using? Including pytorch, torchvision, transformers, stanza ? I'm keeping seeing errors of stop Iteration and Expected object of device type cuda but got device type cpu for argument #3 'index'.

When I ran inference I got Expected object of device type cuda but got device type cpu for argument #3 'index' in call to _th_index_select.
The error is from this line in the torch nn lib.

This line is called by in bernli.py:


bypass aliased curl

Use command curl ~add nvm_curl~ so that we can bypass aliased curl.
Context: https://github.com/nvm-sh/nvm/issues/2923#issuecomment-1299535388

With these changes, there's only two places nvm_curl is needed, which suggests that inlining command may be a better choice?
if we keep nvm_curl, we need to remember to unset it in deactivate. also, there may be tests mocking curl that need to now mock nvm_curl.

Indeed, with only 2 places need the -q option I agree it's simpler to avoid the nvm_curl function, which also make testing less complicated. I've updated the PR accordingly.

Testa are failing on master

Looking at the failed test here: https://app.travis-ci.com/github/nvm-sh/nvm/jobs/586754000

✗ nvm_list_aliases works with LTS aliases
expected lts/gallium, got >lts/hydrogen<

I believe it's because of outdated test data. hopefully it can be fixed by https://github.com/nvm-sh/nvm/pull/2933

Unfortunately it’s much more difficult than that; xenial can’t build node 18 and newer Ubuntus can’t build node 0.6.

Running the edited command curl for me does not log the edited one.

Got tests passing on master and rebased this.

@ryenus tests are still failing - specifically the ones that mock curl. are you interested in completing this PR? if not, please leave it open so I (or another contributor) can give it a shot :-)

@ljharb I just realized that the test for nvm_curl_libz_support assumes that curl can be redefined as a shell function, therefore I'm keeping it as-is.

@ryenus indeed - so i think that with this PR's change, to keep that test passing, we'd have to make the test instead mock out the PATH and provide an actual fake curl binary.

so i think that with this PR's change, to keep that test passing, we'd have to make the test instead mock out the PATH and provide an actual fake curl binary.

@ljharb you're right, though IMHO it's a bit too much, as I think in the original issue it's likely a problem with the specific alias definition, not that the curl command cannot be aliased. If that's fine I'd like to close the pr instead.

Let's keep it open; I'll try to get back to it and finish it.


move Floor, Gcd, Lcm, Pi, Power to datafusion-functions

Is your feature request related to a problem or challenge?
As part of https://github.com/apache/arrow-datafusion/issues/9285 move the  Floor, Gcd, Lcm, Pi, Power  functions to the new datafusion-functions crate in the new structure.
Describe the solution you'd like
Functions are migrated to the new crate and use the new patterns as described in https://github.com/apache/arrow-datafusion/issues/9286 & https://github.com/apache/arrow-datafusion/pull/9216
Describe alternatives you've considered
No response
Additional context
No response

@Omega359 I realised while working on #9868 that some parts (eg: simplifying expressions: search simpl_log, simpl_power) of log & power functions are dependent on each other.
I think that these functions should be migrated together. Since you're already migrating the power function, can you also pick up the log function in the same PR?

Oh, I just created the tickets .. I wasn't attempting to do all of them @tinfoil-knight  :) If you are working on something related feel free to take this ticket too

@Omega359 I just need the Power function since it's dependent on Log.
I've opened a new issue: #9875 for it. Please update this issue to not include the Power function. Thank you!

take

❤  -- thank you @Omega359


non-Latin characters can't be displayed correctly in window title

Environment
Windows build number: 21340
Your Distribution version: Ubuntu
Your WSLg version: 0.2.13

Steps to reproduce
Install any application can display non-Latin characters to window title, such as Spotify.
(In this repro step, Spotify is used)
Install Spotify
Launch Spotify
Select song/artist which include non-Latin characters.
Window title should show song/artist name, but when those contains non-Latin characters, it shows as "box".

Expected behavior
non-Latin characters should be shown correctly.

Same issue here.
But actually I have non-Latin fonts:
❯ fc-list | ag sourcehansans-normal
/usr/share/fonts/adobe-source-han-sans/SourceHanSans-Normal.ttc: 思源黑體 香港,Source Han Sans HC,Source Han Sans HC Normal,思源黑體 香港 Normal:style=Normal,Regular
/usr/share/fonts/adobe-source-han-sans/SourceHanSans-Normal.ttc: 思源黑体,Source Han Sans SC,Source Han Sans SC Normal,思源黑体 Normal:style=Normal,Regular
/usr/share/fonts/adobe-source-han-sans/SourceHanSans-Normal.ttc: Source Han Sans,源ノ角ゴシック,Source Han Sans Normal,源ノ角ゴシック Normal:style=Normal,Regular
/usr/share/fonts/adobe-source-han-sans/SourceHanSans-Normal.ttc: Source Han Sans K,본고딕,Source Han Sans K Normal,본고딕 Normal:style=Normal,Regular
/usr/share/fonts/adobe-source-han-sans/SourceHanSans-Normal.ttc: 思源黑體,Source Han Sans TC,Source Han Sans TC Normal,思源黑體 Normal:style=Normal,Regular

@PhyX-Meow , the window title bar is rendered by system-distro, thus fonts needs to be installed inside system-distro but currently system-distro is not user configurable (such as installing other international fonts).

@PhyX-Meow, @lwldcr, FYI: we made a change to system-distro to load from Windows by https://github.com/microsoft/wslg/pull/266, thus as long as fonts for required language are installed at Windows side, it will be used. (note: system-distro does not load fonts from user-distro). Also, by https://github.com/microsoft/weston-mirror/pull/22, pango will fallback for international text. Thanks for trying out WSLg!


Version number 28.0.0 => 29.0.0

Bumped the version number – uproxy-lib now includes the freedom-port-control module.

:+1:

Not a big deal at all but FYI when adding new APIs you only need to bump the minor, i.e. middle, number -- only breaking changes require a major version bump (and the ensuing changes to uproxy's package.json).

This arguably required a major version bump because it would break uproxy at runtime until uproxy changed its freedom manifest.

OK. It's not obvious why that would be the case but thanks for clarifying.


RuntimeException while stopping Accumulo

$ ./bin/accumulo-cluster stop
Stopping Accumulo cluster...
2019-02-01 13:50:15,801 [conf.SiteConfiguration] INFO : Found Accumulo configuration on classpath at /path/to/accumulo-2.0.0-SNAPSHOT/conf/accumulo.properties
Exception in thread "Thread-2" java.lang.RuntimeException: No files-cache implementation set.
	at org.apache.commons.vfs2.provider.AbstractFileSystem.getCache(AbstractFileSystem.java:209)
	at org.apache.commons.vfs2.provider.AbstractFileSystem.getFileFromCache(AbstractFileSystem.java:222)
	at org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:332)
	at org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:317)
	at org.apache.commons.vfs2.provider.AbstractFileObject.resolveFile(AbstractFileObject.java:2007)
	at org.apache.commons.vfs2.provider.AbstractFileObject.resolveFiles(AbstractFileObject.java:2052)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getChildren(AbstractFileObject.java:1222)
	at org.apache.commons.vfs2.impl.DefaultFileMonitor$FileMonitorAgent.checkForNewChildren(DefaultFileMonitor.java:553)
	at org.apache.commons.vfs2.impl.DefaultFileMonitor$FileMonitorAgent.check(DefaultFileMonitor.java:667)
	at org.apache.commons.vfs2.impl.DefaultFileMonitor$FileMonitorAgent.access$200(DefaultFileMonitor.java:423)
	at org.apache.commons.vfs2.impl.DefaultFileMonitor.run(DefaultFileMonitor.java:376)
	at java.lang.Thread.run(Thread.java:748)
Accumulo shut down cleanly

I saw something similar #928

I think we need to look at the version of vfs2 we are running.  I don't  have a run function on line 376 in my decompiled DefaultFileMonitor class that the AccumuloReloadingVFSClassLoader uses to manage the file caching.  The IDE is telling me that DefaultFileMonitor.class if bytecode version 50.0 (Java 6) .  Maybe my environment is going to the wrong .class file?
A newer Vfs2 library may have some improvements we want.
I will keep trying to get to the bottom of this issue.

Seems like this is the most up-to-date:
https://mvnrepository.com/artifact/org.apache.commons/commons-vfs2/2.3

org.apache.commons
commons-vfs2
2.3

<!-- https://mvnrepository.com/artifact/org.apache.commons/commons-vfs2 --> <dependency>     <groupId>org.apache.commons</groupId>     <artifactId>commons-vfs2</artifactId>     <version>2.3</version> </dependency>

AccumuloVFSClassLoader.generateVfs adds providers for many file types but not one for "files-cache" which the file monitor thread seems to be looking for given the stack trace above.  We have a LruBlockCache implementation thread running but that is separate.
Inside of the AccumuloVFSClassLoader.generateVfs function a line like:
vfs.addProvider("files-cache", /* our files-cache implementation */ );
needs to be added.
I can't find a provider for "files-cache" inside of the 'org.apache.commons.vfs2.provider' package.
Should I implement this provider?  Or if we set the property general.vfs.classpaths to a place where it is will the error not occur.  On my "UNO" instance the property general.vfs.classpaths is not set.  It is null.

Can you use org.apache.commons.vfs2.provider.local.DefaultLocalFileProvider for files-cache?

Actually, it looks like we should probably pick from one of the built-ins here: http://static.javadoc.io/org.apache.commons/commons-vfs2/2.3/org/apache/commons/vfs2/cache/package-summary.html
I think we probably just have to register the provider. I don't know enough about VFS2, but it seems like if we have to do all this manual registration of providers to initialize VFS, we're probably doing something wrong... like how we used to manually initialize Log4J in code rather than rely on the built-in initialization using Log4J config files and system properties.
For now, though, the best fix is probably to find a reasonable provider, and register it explicitly, like we do for the other types.

There is no "files-cache" implementation in this list of support Vfs2 file systems:
https://commons.apache.org/proper/commons-vfs/filesystems.html
I know my code change does not fail during runtime when I shut down or anything else but I can't really say what the effect of the change will really be.

Does the upgrade to 2.3 alone fix the issue? Or does the addition of registering the "files-cache" provider fix it? If the upgrade alone fixes the issue, then we should probably omit the registration of a "files-cache" provider until we understand the effect of that change better. If both are needed, then we should do both, but I'm a bit uncomfortable registering that specific provider without understanding the implications.

My latest revision of the code catches a runtime exception if vfs cannot find an implementation while adding or removing files from the monitor and logs exception's message as at error level.  At least we won't crash and throw stack traces but we will have to look into the logs to find the error.   I am scratching my head trying to figure out what part of our code is putting "files-cache" in its URI string.

I can't positively assert whether the upgrade to 2.3 fixed anything.  I never saw this runtime error on my test system and don't really have a technique to reproduce it.  I just think upgrading the version to 2.3 has to have some advantages.


make datasets module

Make a module with data in standardized format including but not limited to:

[ ] locfish
[ ] seqFISH
[ ] MERFISH

upload data to figshare for download


Add concept page for resources

Adds a concept page explaining what resources are, what they are for and on a highlevel how they can be used.
It also adds a common intro text on resources that can now be used across languages (+special treatment for erlang:-) )
I also applied some weight changes to make them closer to what we have defined for language pages (see https://github.com/open-telemetry/opentelemetry.io/issues/2829)

Overall looks good, but some suggestions in the main concept doc

thanks, suggestions applied


Add baremetal as framework

Although Arduino is very cool it would be nice to be able to write programs in a more classic C/C++ format (especially when tinkering with the C SDK from Raspberry).

It's already added here: https://github.com/Wiz-IO/wizio-pico
Maybe it could be ported to the official platform?

The Wizio-pico library has recently disappeared. Tried to get in contact with the dev but no response yet. Would this change be enough to incentivise work on this issue?

The Wizio-pico library has recently disappeared. Tried to get in contact with the dev but no response yet. Would this change be enough to incentivise work on this issue?

I've spoken to the dev recently and he will not resume the project. He did not enjoy working with the Pico and the Pi Foundation and therefore decided to cancel it. It's a shame that he went so far as removing it from Github. So I also have the same question. Could this framework be adapted instead?

Why not using https://github.com/earlephilhower/arduino-pico ?

Why not using https://github.com/earlephilhower/arduino-pico ?

Not bare metal – still Arduino. It's plagued with Wi-Fi and socket issues as well as terrible power consumption. I'm looking for a pure C solution running only the Pico SDK – just like WizIO, but preferably one that still exists.

As a note for people looking for the disappeared platform: This commit: https://github.com/blackketter/wizio-pico/commit/a0e41397f445566efca7b26f16af4aa2416aa99b looks like last that was pushed

Hi - I too am looking for a way to use

the Official Pico SDK (Not arduino)
In Windows with Platformio IDE
and especially to be able upload and debug.

The backup of the WizeIO - would not work with the "Raspberry Pi Pico Debug Probe" (Logs says it is about to upload via CMSIS-DAP but then it goes and makes a .uf2 file and tries to update via flash). Maybe it works with 2 picos (picoprobe) only - but either way, its discontinued and unsupported.
The earlephilhower - would not run the most basic print("hello world") - linker errors with the required "stdio_init_all()" call.
All other options Id found seem to be Arduino based - which is not an option for the project I am on.
I got earlephilhower to work by copying 6 missing stdio and stdlib files from from the pico sdk to the src folder of my project - so now it can print to platformio's terminal - but anyone have a less hacky way of doing this?
thanks!

I am looking forward to this kind of integration too. Thanks @OzmoOzmo  for the feedback about the existing solutions, it helps me a lot in deciding to learn the pico sdk for the time being, as the quickest path to be able to get something.
Because I also looked at how to create a PlatformIO framework, to see if I could do something. And it seems to me that it's not something trivial and quick to do :( I mean, there is a quick guide but for me, going further (even with starting from the two existing solutions) require :

being proficient with the pico sdk and CMake, to know how the standard sdk works. (to be done, I was planning to just use platformIO on VSCode, as usual)
being proficient with platformIO and SCons, to know how platformio works (to be done, I was planning to just use the upload button on VSCode and the platformio.ini file, as usual)
study in depth one or two existing and mature non-arduino platform/frameworks, e.g. like ESP32 (to be done, I was expecting the integration to already exist, as usual)

When wizio-pico was taken down I started working on a forked version that removes the Arduino Framework. The goal was to clean up the code and get an understanding of the previous version of the SDK (severely rearranged) was included, to see if I could include the new one as a submodule and get it working.
Unfortunately I quickly realized that I need to learn more about PlatformIO and the build/debug tools to be able to implement something properly, and this is something that I don't have time for at the moment - unfortunately 🥺
I've pushed the code here if anybody else wants to take a look at it, or base something on it: https://github.com/ec-solutions/ez-pico. The README is still from the original wizio-pico project.
It would be fun if we could work on something together.

If I ever have time to study all that stuff, I'll give it a try. Don't hold your breath, though.

When wizio-pico was taken down I started working on a forked version that removes the Arduino Framework. The goal was to clean up the code and get an understanding of the previous version of the SDK (severely rearranged) was included, to see if I could include the new one as a submodule and get it working.
Unfortunately I quickly realized that I need to learn more about PlatformIO and the build/debug tools to be able to implement something properly, and this is something that I don't have time for at the moment - unfortunately 🥺
I've pushed the code here if anybody else wants to take a look at it, or base something on it: https://github.com/ec-solutions/ez-pico. The README is still from the original wizio-pico project.
It would be fun if we could work on something together.

@jonathanlundstrom I would be interested in contributing to this. I stumbled on this issue, because I am interested in the same thing, programming the pico using the C/C++ SDK instead of all the overhead of using the Arduino framework. I'm working on an MQTT Smart Thermostat with a Pico-W using the SDK. I'm finding it pretty clunky to run UTs on my dev machine, and then switch to target the pico. Seems like Platformio would be a good solution to this problem, and I was debating tweaking the code to work with Arduino so I could use it, but I would be much happier with using the SDK with Platformio.

Anecdotal but in the meantime, ive been experimenting with https://github.com/maxgerhardt/wizio-pico.git and it seems to work for me (but i have limited experience)
I would love to see a new baremetal framework that just uses https://github.com/raspberrypi/pico-sdk or maybe another alternative to just include the pico-sdk

Any news for official support?

Is there anything new in this matter?

There is a new extension for vscode from the vendor https://marketplace.visualstudio.com/items?itemName=raspberry-pi.raspberry-pi-pico

Thats pretty cool but dosn't fix the issues in platformio right?

Thats a real shame, what about using PIO to just handle building the sorta, more raspberrypi specific cmake stuff? that could still be handy even if its just backpacking on the existing SDK

There was a big discussion about here https://github.com/platformio/platform-raspberrypi/pull/36
The PIO team wants money from the raspberry pi foundation.

Hi, That link of the spat with pio and rpi is very disappointing.
Ive have Earlephilhower working perfectly for my needs. PIO compiles (as far as i remember)
Baremetal pico with no need use Arduino framework but I can serial.print() from pico back to the platformio console.
Step Debugging works perfectly using the official pico debugger. And all uploads upload very fast without having reset the pico.  All the pico sdk examples work ok. Setup is as I described above.
If this is useful, if anyone wants to try replicate what I have - to help document the setup for others, let me know.

Just adding in here that I'd love pico-sdk support in PlatformIO. It's a shame that we have to switch between different dev environments for different MCUs.
PlatformIO is really a game changer for development, but not supporting one of the most popular MCUs is very disappointing.

Yep, so disappointing. And a wake up call that some parts of PlatformIO should not be taken for granted. So much so that I plan to learn how to operate without PlatformIO, "just in case", even if I still plan to use it as a primary dev platform for supported platforms and toolchains.

I tried this platformio.ini and it works:
[env:stable]
platform = https://github.com/maxgerhardt/platform-raspberrypi.git
board = pico
framework = picosdk
board_build.core = earlephilhower
debug_tool = jlink
upload_protocol = jlink
One problem is I haven't tried the PIO, so not sure if it supports PIO. I also just started so not sure if this just has limited functions of the PicoSDK.

The earlephilhower core aka Arduino-Pico (https://github.com/earlephilhower/arduino-pico) does connect with the Raspberry Pi Pico SDK. See https://arduino-pico.readthedocs.io/en/latest/sdk.html for the documentation. Is a "baremetal framework" necessary given that capability?

earlephilhower couldnt print back to the platformio terminal last time i tried it… Maybe its been fixed?


Function is implemented in mkdocs-material - feature: navigation.indexes

ℹ
I just came across this because I was looking for this functionallity.
However after going through the mkdocs-material documentation I believe this functinoallity is build into mkdocs-material.
Just activate it with:
  features:
  - navigation.indexes

See details here: https://squidfunk.github.io/mkdocs-material/setup/setting-up-navigation/#section-index-pages
Or am I missing something?

Yeah it's mostly the same functionality, with minor config differences.
This extension arrived sooner and aimed to support any interested theme. That theme's author chose to do the same thing separately.


Associations updates (hasOne) not working - MySQL

Hi. I found a very strange behavior of library (probably bug).
So. I have created an example that demonstrates the bug. You should run (dev/app.js) and check the console output. Also you need to check MySQL connection config (dev/app/config).
Bug description:

For some reasons ORM not updating associated (hasOne) data.
For some reasons function "set[Name]" (where Name is related table) is undefined.

Settings:
  db.settings.set('instance.autoFetch', true);
  db.settings.set('instance.cache', false);
  db.settings.set('instance.cacheSaveCheck', true);
  db.settings.set('instance.returnAllErrors', true);
  db.settings.set('instance.saveAssociationsByDefault', true);
  db.settings.set('instance.debug', true);

Please, check  example!

So. After make some research (tests)  I found solution.
Please confirm this:

To update data, you must pass a parent (related) object (NOT ID, KEY or something) to the set__Name__  function.

The Answer:
http://stackoverflow.com/questions/29646089/npm-orm-save-update-of-hasone-field


can not set pub and priv key on peer-info

They don't have setters currently so

https://github.com/libp2p/js-peer-book/blob/master/src/index.js#L66
https://github.com/libp2p/js-peer-book/blob/master/src/index.js#L70

throw. Should add a test here for this and add setters on peer-info

cc @diasdavid

You mean peer-id, right? https://github.com/libp2p/js-peer-id/blob/master/src/index.js#L34-L46
Got it

This has been done :)


Bump go toolchain to 1.23.3

Please review

Hey @samuelbartels20 thanks for raising this. It looks like your starting branch was not completely clean / up to date as there are two commits showing and there are some unrelated changes included in your PR.
Can you please rebase to ensure this pr is only a single commit with just the version bumps.
Thanks!

@jmhbnz Thank you so much for the review. Please, I will work on the changes ASAP.


build: update core packages

update core dependencies (nx)
ignore linting errors of effected apps; seems to be unrelated to the scope of updating dependencies.

:tada: This PR is included in version 0.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Shutdown requests might free their memory before running the callback

UvShutdownReq's base class UvMemory only allocates a weak GC-handle. This means between creating the class in a Connection and having libuv running the callback method, it's free for collection and the Finalizer might run, which frees the memory

#60 includes a fix


Display seed/hash on J version file select as well

Right now, only the US/EU file select displays the seed.  I believe this is simply due to not knowing the address for that particular text in the J ROM.

Menu text pointers are located at address 3EEF00, two bytes for each pointer value.  The values are little-endian and the value is added to base address 3EF000 for the menu text.
The file select name text pointer is located at 3EEF54.  This looks to be the same for both versions, and it has the following values:

US: pointer value 4001, points to 3EF140 which has "Your name?" ASCII text.
J: pointer value 0901, points to 3EF109 which has some J characters.

In both cases, the next pointer is 11 bytes forward which means this text is 10 bytes long in both versions.

Solution: Write the seed value to address 3EF109 for the J version in the same manner as the US version.  Need to test this...

Tested and worked as expected, seed value is now displayed on the JP rom.


Configure CoreDNS to be more resilient to multi-nic and multi-nameserver (per nic) setups

Is your feature request related to a problem? Please describe.
Some edge users have setups where the nodes have multiple nic types. An example I hit was where they had connections from multiple providers and each nic having its own set of nameservers (set on the nic via netplan yaml). There are times where a connection via one nic goes down, but CoreDNS was relying on that nic's DNS configuration. Their resolution ultimately was to reboot the node.
Describe the solution you'd like
The user ended up setting up an intermediary network service that handles the DNS forwarding. They set the /etc/resolv.conf to point to that. This ultimately fixed this issue for them.
Perhaps we could include something like that or set up the Corefile a little differently to do something similar.

K3s just uses the system's resolv.conf. If that points at a DNS server on a specific interface, that's what we'll use. If you want to set up a special resolv.conf for K3s that points to a DNS server that is reachable via multiple interfaces, you can do so using the --resolv-conf flag:
https://rancher.com/docs/k3s/latest/en/installation/install-options/agent-config/#networking

K3s just uses the system's resolv.conf. If that points at a DNS server on a specific interface, that's what we'll use. If you want to set up a special resolv.conf for K3s that points to a DNS server that is reachable via multiple interfaces, you can do so using the --resolv-conf flag:
https://rancher.com/docs/k3s/latest/en/installation/install-options/agent-config/#networking

@brandond Interesting. That almost doesn't look to be the case for the user I'm working with:

Ubuntu DNS (systemd-resolve) appears to be able to adapt to network changes which have different DNS nameservers; but coreDNS does not, which is really a bit odd, given that the host /etc/resolve.conf has the nameserver of <IP_ADDRESS> which is the systemd-resolve service.   So, when the network switches, what is causing coreDNS lookups to fail when Ubuntu lookups are working?  Is coreDNS caching nameservers or something else?

Are you sure that the failure was due to coredns not being able to reach a specific name server? If you're using a local resolver (such as systemd-resolved) as the upstream for coredns then that should work fine. That said, I've frequently been irritated by systemd-resolved doing things I don't want it to do (such as caching lookups from an old network when switching networks), so it may in fact be causing more problems than it's solving.

@brandond I am actually wondering if this is a weird gotchya when the host's resolv.conf is pointed to resolved (?) or similar. It seems to pull the nameservers off of resolved's configs or... something instead of pointing to <IP_ADDRESS>:
root@ben-rancheragent-all-2:~# docker cp acfe56f7bf93:/etc/resolv.conf ./

root@ben-rancheragent-all-2:~# cat resolv.conf
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

root@ben-rancheragent-all-2:~# cat /etc/resolv.conf
nameserver <IP_ADDRESS>
options edns0

This also doesn't seem to adapt when I take the nic down that has those nameservers set, which I didn't expect it to, but I tested that anyways. A possible is to set the pod to use that IP instead. It works for me, but I'm having the customer test that for their use case.
spec:
  template:
    spec:
      dnsConfig:
        nameservers:
        - <IP_ADDRESS>


add new row to table

add new row to table

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi,
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


add table

Add a table in the end

There’s already a table example in the project. Closing this one out.