Fix localhost

We were running into a situation where Fast-RTPS would not pass any data when all network interfaces were down except for localhost.  It turns out that Fast-RTPS was ignoring localhost as a valid communications interface in some circumstances.  These fixes things so that Fast-RTPS will now consider localhost
as a communications interface, allowing this to work.
I've run the basic tests against this patchset, and they seem to pass.  I also ran this patchset as part of the ROS2 CI (linux, windows, osx), and things seem to be happy there as well.  I don't know what other knock-on effects this might have, so thoughts/review on that would be appreciated.  Finally, I'm pretty sure there is a similar problem in UDPv6, but I'm much less familiar with IPv6 and I don't have time to debug it right now.

@richiware Friendly ping.

@miguelcompany and me were reviewing the PR, but we think the solution  is not ideal. With this PR the locator <IP_ADDRESS>
is sent to remote endpoints through discovery. I'm working on a better solution in branch
hotfix/#3559. I will be informing you.
↪ 2018-10-23 mar 00:14, Dirk Thomas<EMAIL_ADDRESS>
@richiware Friendly ping.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/eProsima/Fast-RTPS/pull/267#issuecomment-432009853

@MiguelCompany and me were reviewing the PR, but we think the solution is not ideal. With this PR the locator <IP_ADDRESS> is sent to remote endpoints through discovery. I'm working on a better solution in branch hotfix/#3559. I will be informing you.

Great, thanks for the update @richiware

Hi @clalancette and @dirk-thomas
I've seen a better way to address the case when running on a machine with all the network interfaces down except localhost. You can see the code on #303. I have tested the HelloWorldExample on Ubuntu 18 and Windows and the publisher and subscriber match and communicate correctly.
When that PR is merged it will close this one, so I wanted to inform you so you can check it solves the problem originally posted here.

@MiguelCompany I just got a chance to test out PR #303 (really, I tested the develop branch), and things seem to work great there!  It actually fixes the problem better than this PR, since I no longer even need to setup lo for MULTICAST.  Thank you so much for the fixes.  I'm going to close this PR out now.


Error reading version line when launch kimera_semantics.launch play_bag:=true

dear repository,
I installed kimera-semantics and ros  correctly following the instruction online, when I use the command : roslaunch kimera_semantics_ros kimera_semantic.launch play_bag:=true  ,the error is throwed out: Error reading version line
what's wrong  with this ?
my OS version is :ubunt16.04
ROS version: ros kinetic

I can't reproduce this error, but, alternatively, just play the rosbag in another terminal (and leave play_bag as its default which is false). Or do you really read to use the rosbag to play in the same launch file?

Closing, but feel free to re-open if you still have this error.


Fix some E2E tests

What happened?
Some code submissions after @petersopko 's initial creation of basic E2E tests have broken some of those tests.
-> Needs to be fixed asap after blocker is merged
blocked by https://github.com/kodadot/nft-gallery/pull/3689
you can quickly get a sense of whats going on by using GUI Cypress suite via  "test:e2e-gui": "cypress open --project tests", :fire

Payment link for reward
https://kodadot.xyz/transfer/?target=EqdyzrzVmeHwMdMwvPeCMnNdbuQDbD3YrjY93xq9Ln3jUGW
Code of Conduct

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

Thanks for reporting this ❤ I've most likely merged something without tags today, will fix tomorrow morning.

@kkukelka hmm, I've just pulled the latest main and it's all passing?

sweet


Expose L2 (Euclidean) distance to JavaScript

Describe what you are looking for
The 79300f45bdae1088640a1eb925a93be769d7c3ec commit exposes kernels for the L2 Euclidean metric, extending beyond the previously available L2sq - the squared Euclidean distance. It may be useful to expose the new interface in the NPM package.
Can you contribute to the implementation?

[ ] I can contribute

Is your feature request specific to a certain interface?
Other bindings
Contact Details
No response
Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

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

Hi @ashvardanian , I would like to learn and contribute to SimSIMD ! Can I take a shot at this issue and raise a PR ?

Sure, @GoWind, thanks!


Declare autocorrect as unsafe for RSpec/Capybara/SpecificFinders

Fixes #1468

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Updated documentation.
[x] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

If you have created a new cop:

[ ] Added the new cop to config/default.yml.
[ ] The cop is configured as Enabled: pending in config/default.yml.
[ ] The cop is configured as Enabled: true in .rubocop.yml.
[ ] The cop documents examples of good and bad code.
[ ] The tests assert both that bad code is reported and that good code is not reported.
[ ] Set VersionAdded in default/config.yml to the next minor version.

If you have modified an existing cop's configuration options:

[x] Set VersionChanged in config/default.yml to the next major version.

Is it in the cop’s design that the autocorrection is inherently unsafe, and it is impossible to fix the cop?
Or are there deficiencies due to some edge cases that we’ve missed previously, but are well aware of presently?

@pirj Thanks for reply.
See my comments on #1468 for edge cases. It may be possible to fix, but not easy.

I am planning to work on edge case support. What do you think?
We do not consider this cop is Unsafe, as it may be difficult to accommodate, but not impossible.

We’re not practicing marking cops that are not unsafe by design as such. If a cop has bugs, or uncovered edge cases, we encourage affected users to exclude problematic files from inspection using .rubocop_todo.unless or by local rubocop:disable statements.
Thank you for understanding.


1.x compatibility API silently ignores "h" and "m" precision when writing

After successfuly writing data to a 2.0.7 instance, using the 1.x compatibiliy with "m" precision I was unable to find it.
It turned out  that because models/points.go:GetPrecisionMultiplier()  silently considers anything that is not "us|ms|s" as "ns", data was written without proper multiplication of the timestamp.
I'm not sure what was the reason behind the dropping of these precisions (in 65bf4bb383693bb49e674e8cfc0a615a01388b12).
Anyway, I think that even if there is one, then either documentation should be corrected, and write handler probably made to  detect this and fail,
or better, it should be supported (possibly only when using 1.x compatibility API if this is an issue for v2)
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

Write data with "m" or "h" precision and a timestamp

Expected behavior:
be able to get this data via a query for original timestamp
Actual behavior:
timestamp is incorrect.
Environment info:

InfluxDB version: InfluxDB 2.0.7 (git: 2a45f0c037) build_date: 2021-06-04T19:17:40Z / latest docker 2.0 image

Not only this, it also as the key for microseconds changed from u in 1.x to us in 2.0, the compatibility is broken as the timestamp in us is treated as ns and becomes an invalid timestamp causing below error. The old applications do not work out of box.
Note: I am using a python module influxdb that has a check for these allowed timestamps as per v1.x, I had to hack to bypass this.
Failed writing data: 422: {"code":"unprocessable entity","message":"failure writing points to database: partial write: points beyond retention policy dropped=101"}

I was affected by u being silently (doc-wise) deprecated. One of the appliance types we're using submits data points with u precision, without any option to change it. This makes writes fail like in the post above:
<Response [422 Unprocessable Entity]>
{"code":"unprocessable entity","message":"failure writing points to database: partial write: points beyond retention policy dropped=13"}

This new behaviour is not reflected in any way in the v2.2 docs. v1.8 docs do not list ns and us as allowed options, so I can't just request the vendor to change precision to from u to us, as this will break InfluxDB v1.x.
This ultimately breaks v1 API compatibility.
Tested in InfluxDB v2.2.0 (git: a2f8538837) build_date: 2022-04-06T17:36:40Z

I can relay similar and broader behavior v2.2.0's v1 compatibility mode.  We actually see that when passing "precision=u", the number is interpreted as nanoseconds and returns only 204 and no error, so the point is written 3 orders of magnitude off.
ANY value passed to precision, like "precsion=xy" will silently interpret the timestamp as nanoseconds and return 204
This behavior is different in v1.8.3, where passing "precsion=us" returns a 404 with json error content, but nonetheless still writes the point with the wrong precision.
So it seems that in development, there is confusion about providing v1 compatibility regarding the precision= parameter. Here is what Influx's own document's describe:


Types too wide for page path query parameter.

Why is the query parameter for a page route typed as string | string[] | undefined? Shouldn't a matched route always be available and a single string?

Next.js collapses path parameters and search parameters into a single query object


Request for new version of aci-deploy action

Logging this request to tag a new release of this action as it looks like a fix has been merged that addresses a bug relating to the parsing of secrets/strings. There have been a few issues/PR raised for the handling of = in environment secrets

https://github.com/Azure/aci-deploy/issues/13
https://github.com/Azure/aci-deploy/pull/10
https://github.com/Azure/aci-deploy/pull/14
https://github.com/Azure/aci-deploy/pull/8

--
The following was Originally posted by @mitsha-microsoft in https://github.com/Azure/aci-deploy/pull/8#issuecomment-720900090
@jesseward yes simply pointing to aci-deploy@master won't work since it's not a good advice to point directly to the master branch. Forwarding your issue to @narula0781 and @ashishonce who can release a new version of this action with the updates.

Tagging @narula0781 and @ashishonce here as well.

We need #18 to be included. Please merge and tag a new release. Thx

@ashishonce and @narula0781 : it looks like this is a higher priority now due to the set-env changes as well. Please see the commenary within https://github.com/Azure/aci-deploy/issues/22 as well..

Please also take note of issue https://github.com/Azure/aci-deploy/issues/28 when doing the next release. node_modules needs to be checked in for the update to @actions/core to be included:

@jesseward can I help with anything to release faster?

@jesseward can I help with anything to release faster?

hi @brenoalvs , this ticket was created to request a new release. I am not a project owner (just a consumer ;-) ). I have pinged the owners of the project in the issue comments

@jesseward Oh sorry, I forgot to check.
@mitsha-microsoft It seems that you're the guy. There's anything I can help you?

+1 waiting for this

@brenoalvs I am not the current owner now. I wrote the action. @narula0781 @ashishonce  own this now 😄 Tagged them here

@narula0781 and @ashishonce Is this issue being fixed? Please let me know.
We have customers who are unable to deploy to Azure ACI using GitHub action.

My builds are all down too. 👎

👋 hi folks - from the ACI team here. This issue is under investigation
If you'd like to provide feedback on the Action here is a short 5-minute form

I have made the required changes.
Please try out the latest changes using the same version v1 and it should work.

Works for me :-)

Confirmed working here as well. Thanks for the updates

Thanks for confirming. I am closing this issue.

Closing the issue


Create / Gather graphics elements for Wallet App

We will need several graphics, layout, and color bits to make a consistent looking app.  These elements include:
#Components Needed
For guidance, refer to this issue:

[x] #10
[x ] https://github.com/roots-id/rootswallet/issues/10
[ ] favicon :tada:
[ ] background default color
[ ] highlight color
[ ] Font style
[ ] Font color - default / highlighted / greyed out
[ ] splash screen image
[ ] background image
[ ] etc

do we need to hire a designer?

@Essbante  has the connections.  Happy to send some Ada to cover it.

sure!

same elements are here https://www.rootswallet.com/.  so either we use what we already have or update website, youtube, github, etc

current theme pallet
data-color="#e69138"
data-color="#b0bf93"
data-color="#000000"
data-color="#1c1c1c"
data-color="#2f2f2f"
data-color="#f9f9f9"

font is montserrat 12
favicon, banner, and background images are from our branding images


There is a contradiction between the functionality and examples of MSDCFG.SSM

The function of MSDCFG.SSM is described as follows in section8.3:
When SSM is 0, the SRL configuration enables the RDSM to configure a RCID prefix value in the srmcfg.RCID field while allowing the supervisor domain to program the low order SRL bits of the field. When SSM is 1, the supervisor domain may only program a RCID value in the range 0 through 2^RCIDLEN - 2^SRL - 1 where RCIDLEN is the number of implemented bits of the RCID field.
The example of how to use MSDCFG.SSM is described as follows in section8.3:
Consider a QRI that supports 32 RCIDs and is mediated by RDSM between two SDs.The RDSM may allocate 24 RCIDs to the first SD and 8 RCIDs to the second SD. The SRL and SSM configurations used by the RDSM to support this use case are as follows:
The RDSM configures SRL to 3 and SSM to 0 for first SD. This allows the first SD to select RCID values 0 through 23 in srmcfg.The value of  SSM need be 1 for first SD?
The RDSM configures SRL to 3 and SSM to 1 for the second SD and programs the srmcfg with a value of 24.The value of  SSM need be 0 for second SD?

You are right that the examples have the SSM value specified incorrectly. Fixed in #101


copilot suddenly stopped working

I started using copilot about 2 weeks ago, it was working fine until yesterday, when I start typing code then it doesn't show any suggestions anymore, when I check the log for github copilot it has this: [INFO] [ghostText] [2023-09-27T10:05:27.285Z] Cancelled during debounce [INFO] [default] [2023-09-27T10:05:27.407Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex [INFO] [default] [2023-09-27T10:05:27.952Z] [fetchCompletions] engine https://copilot-proxy.githubusercontent.com/v1/engines/copilot-codex [ERROR] [ghostText] [2023-09-27T10:05:31.222Z] Error on ghost text request: (FetchError) Client network socket disconnected before secure TLS connection was established.  does anyone have any ideas of how I could fix it, I am still signed in to github

This repo is for a Go client library called go-github and does not handle GitHub tech support for Copilot or any of GitHub's products.
A quick search, however, might help you out.
Closing.


[hotfix] Exclude whole tools directory instead of tools/releasing/shared from source release

With this change currently releasing connector-parent source release will be cleaned (no tools directory) and next source releases of connectors will be cleaned as well.
FYI: @zentol @MartijnVisser as discussed in the ML

Self merging


Need aws-go-sdk version updated to support iam:AssumeRoleWithWebIdentity at EKS

Hi, I've been using Escalator so far for scaling k8s clusters with Spark batch jobs running inside. Thanks for building an awesome product!
I'm currently running Kubernetes cluster with Kops+Kiam which do not have any issue about assuming IAM role for Escalator pod, but when I try to run Escalator on EKS-managed cluster, it can't assume IAM role given by service account.
The root cause is that older version of AWS SDK does not support iam:AssumeRoleWithWebIdentity with OIDC provider. it seems resolvable when we update AWS SDK to the latest version - 1.23.13 is the minimum verison required.
It will be greatly appreciated if the new version with updated SDK is released. Thank you so much!

Thanks for raising this issue @hippothewild! This is perfectly doable.

Just opened a PR to handle this issue.


Support for python "re" module for doing regex in jinja templates

Describe the feature
I have a case where I'd like to be able to do a regex in a jinja template for matching a particular set of values.  It would be handier to have a access to python's re module than having to use normal string manipulation and matching
Describe alternatives you've considered
For now I'll probably use text manipulation using if, |replace and + to do the same thing to get the string into the right format, but it would be much handier to be able to get the values from regex groups.
Additional context
Not database specific, would apply to all jinja templates in the same way that datetime and pytz modules are made available.
Who will this benefit?
Anybody who wants to do more complex string manipulation and string checking in a more straight-foward way than is possible today.

Hey @whisperstream! What kind of regexing are you planning on doing in the jinja context? I'm open to this idea, but I'd like to better understand what your use case is here

Sure it's part of the same problem I've been trying solve for better handling permissions in dbt models https://github.com/fishtown-analytics/dbt/issues/1695.
So for for this problem I have the following:
        {%- if row['granted_on'].lower() == 'role' and (row['name'].lower().startswith('dev_br') or  row['name'].lower().startswith('dev_raw')) -%}
            {%- set value = row['name'][4:].lower() -%}

whereas with re I could do:
        {% set matcher = re.match('^dev_((br|raw)_\w+)', row['name]|lower) %}
        {%- if matcher is not none -%}
            {%- set value = matcher.group(1) -%}

I think regex is pretty standard these days and so having a more concise way of expressing these conditions could be useful.

roger! That makes a lot of sense.
Is this something you'd be interested in submitting a PR for? You can find the code where modules are injected into the context here: https://github.com/fishtown-analytics/dbt/blob/f9bc7c56e512d424248c4c0eeaceab5a2cc04fd0/core/dbt/context/common.py#L344-L348
We limit the methods that are exported from a module -- check out get_datetime_module_context or get_pytz_module_context in that same file for an example.

yeah I'm happy to give that PR a shot.

Ah! Sorry, totally missed this. For posterity: use the default branch shown at https://github.com/fishtown-analytics/dbt -- that will always be the dev/ branch we're working on. In this case, it's dev/louisa-may-alcott!

@drewbanin I am also very interested in that feature! I am trying to tweak your star macro to add a regex argument to select only a subset of columns based on this regex! I guess the PR hasn't been opened/merged, right ?

hey @machupichu - that's right - we haven't yet made a code change that adds support for the re module yet.
Check out the discussion here for some background on why solving this problem in the general case is tough: https://github.com/fishtown-analytics/dbt/pull/1997
I'm a-ok with adding specific support for the re module if we can make sure that it doesn't leak out attributes that would lead to any security issues. Check out this comment in particular for more info: https://github.com/fishtown-analytics/dbt/pull/1997#issuecomment-564215181


Allow Users to Create Custom Themes in Caido UI

Hey @bebiksior I was planning on working on a new feature where users can use a color picker to create their own custom themes in the Caido UI.
I thought it would be cool to create a new "Appearance" tab next to the "EvenBetter" tab which has a couple color pickers like this https://www.w3schools.com/colors/colors_picker.asp so the user can make and use their own custom themes on the fly within the UI.
Please let me know what you think before I start on it.

Great idea, man :D Sounds awesome! Let me know if you run into any issues with creating a new tab, had many issues with it, and the current code there isn't great.

Hey, just pushed to the dev branch improvements how EvenBetter determines the opened tab and made adding new tabs a bit easier. Hope it helps :D
https://github.com/bebiksior/EvenBetter/tree/dev


[SuiteHeader] javascript urls in links

What package is this for?

[X] React
[ ] Angular

Describe the bug
While cleaning up testing output we've uncovered some other bugs that may introduce breaking changes that need to be fixed in v3.
  ● Console

    console.error
      Warning: A future version of React will block javascript: URLs as a security precaution. Use event handlers instead if you can. If you need to generate unsafe HTML try using dangerouslySetInnerHTML instead. React was passed "javascript:void(0)".
          in a (created by Link)
          in Link (created by ForwardRef(HeaderMenuItem))
          in li (created by ForwardRef(HeaderMenuItem))
          in ForwardRef(HeaderMenuItem) (created by HeaderActionMenu)
          in ul (created by HeaderActionMenu)
          in div (created by HeaderActionMenu)
          in HeaderActionMenu (created by ForwardRef)
          in ForwardRef (created by HeaderAction)
          in div (created by HeaderAction)
          in HeaderAction (created by HeaderActionGroup)
          in div (created by HeaderGlobalBar)
          in HeaderGlobalBar (created by HeaderActionGroup)
          in div (created by HeaderActionGroup)
          in HeaderActionGroup (created by Header)
          in header (created by Header)
          in Header (created by Header)
          in Header (created by SuiteHeader)
          in SuiteHeader

      at printWarning (../../node_modules/react-dom/cjs/react-dom.development.js:88:30)
      at error (../../node_modules/react-dom/cjs/react-dom.development.js:60:5)
      at sanitizeURL (../../node_modules/react-dom/cjs/react-dom.development.js:1171:7)
      at setValueForProperty (../../node_modules/react-dom/cjs/react-dom.development.js:1343:9)
      at setInitialDOMProperties (../../node_modules/react-dom/cjs/react-dom.development.js:5831:7)
      at setInitialProperties (../../node_modules/react-dom/cjs/react-dom.development.js:6026:3)
      at finalizeInitialChildren (../../node_modules/react-dom/cjs/react-dom.development.js:7499:3)
      at completeWork (../../node_modules/react-dom/cjs/react-dom.development.js:18978:17)

closed by linked PR


Problem about using multipath plugin

The connection always closed with error when I try to establish the connection with multipath_rtt_cond.plugin.
like that:
`Successfully inserted preplugin plugins/multipath/multipath_rtt_cond.plugin
Register plugin be.qdeconinck.multipath.rtt for full registration
include multipath_cond.plugin...
Successfully injected post plugins for be.qdeconinck.multipath.rtt
Negotiated ALPN: hq-29
Almost ready!
ERROR: trying to get input 5, but there are only 5 inputs available
Connection established. Version = ff00001d, I-CID: 3598041ec8f8c14b
No progress for 10 seconds. Closing.
-1.0
Client exit with code = 0`
What should I do to solve this problem?

Did you ever figure out how to fix this issue? Currently running into the same thing.


Opinionated code cleanup

I was starting to work on extending this, and decided to take 5 min and clean up the code a little bit, to make it easier for me to work with.

Thanks


Strtolower($string)

Laravel Version: 5.4
Voyager Version: dev-master
PHP Version: 7
Database Driver & Version:

Description:
Need to use mb_strtolower instead of strlower for Unicode in widgets.
Russian lang example.
strlower = ������������
mb_strlower = Пользователь
And nedd to change alert get messages way for menu builder
From voyager.menu.builder_successfully_deleted to voyager.menu_builder.successfully_deleted

issue is fixed

Labels: locale, bug

Resolved by #1743


[Feature Request]: Get info on PDF to have (i) info buttons explaining what operations do

Feature Description
Get info on PDF to have (i) info buttons explaining what operations do
Possibly have a short automated description explaining unique aspects of the PDF
"This PDF is encrypted so may face issues with some applications, additionally I has X permission restricted, (you can change this at link finally it has x complicaincy meaning it is..."
Why is this feature valuable?
Gets info on a PDF which users can understand
Suggested Implementation
No response
Additional Information
No response
No Duplicate of the Feature

[X] I have verified that there are no existing features requests similar to my request.

Hi @Frooodle! I’ve reviewed the feature request and have a general understanding of the intended functionality. However, after checking the current feature, I noticed that there's a lot of technical data being displayed, which might not be very user-friendly or easily understandable for many users.
Could you provide a bit more context to clarify the requirements for presenting this data?


No ref fix build mysql dep

Closed in favor of https://github.com/cluePrints/vatic/pull/5

Closed in favor of https://github.com/cluePrints/vatic/pull/5


UI Designs For Different Components

We Would Love to have Interactive, Fluid, and Lucrative designs for our platform.
There are a lot of components such as Login, SignUp, AboutUs, and ContactUs etc.
Remember to Make the designs in Figma and also that they should maintain a constant binary color theme.

Submit Component Designs Below this Issue Only.

Refer Figma for more Information
Also Check Out Preferred Binary Color gave in this Issue

Hey there! How's it going? I'd like to take responsibility for this issue.

Hi @Dhruvil-P Please go ahead. Assigning this to you.

Thanks for letting me know. Will start working on it.

Hey! Can you confirm the components which need to be redesigned in Figma? Thanks.

Hi @Dhruvil-P You can try starting with search page Book details page Home page or you can choose any other page present in website you want to re-design.

Perfect. 👍🏻

Hey! The designs are done. How should I proceed?

Hey @RohitKumar-200. I created a PR for the designs. Here's a quick look if wanna review it. And, lemme know what other design tasks I need to do.

Hi @Dhruvil-P
I am sorry, I couldn't reply to you as I was little busy.
I reviewed your pull request #275
Since you are adding figma link directly, you can add the link in readme.md itself
For reference, here is a screenshot, you can put all your links just above future plan heading:

You can create different pages in same figma file (You can see this in the top left corner), so attach different links for different pages:

So, please add the design page in this manner (In readme.md), you can either add all pages at once, or create separate pull requests for different page designs.
If you have any queries, feel free to ask. This time, I will try to reply faster 🙃

By the way, your designs are really great!!
Thanks for your contribution @Dhruvil-P  🙌

Great Work @Dhruvil-P 🙌

Hi @Dhruvil-P
I am sorry, I couldn't reply to you as I was little busy.
I reviewed your pull request #275 Since you are adding figma link directly, you can add the link in readme.md itself
For reference, here is a screenshot, you can put all your links just above future plan heading:
You can create different pages in same figma file (You can see this in the top left corner), so attach different links for different pages:
So, please add the design page in this manner (In readme.md), you can either add all pages at once, or create separate pull requests for different page designs.
If you have any queries, feel free to ask. This time, I will try to reply faster 🙃

`

Hi @Dhruvil-P
I am sorry, I couldn't reply to you as I was little busy.
I reviewed your pull request #275 Since you are adding figma link directly, you can add the link in readme.md itself
For reference, here is a screenshot, you can put all your links just above future plan heading:
You can create different pages in same figma file (You can see this in the top left corner), so attach different links for different pages:
So, please add the design page in this manner (In readme.md), you can either add all pages at once, or create separate pull requests for different page designs.
If you have any queries, feel free to ask. This time, I will try to reply faster 🙃

Understood. I'll create PRs for separate Figma pages.

Thanks, guys. Glad ya'll like it.

Issue is resolved.
Closing it now.


issue with the rendering of the custom font

Hello everybody i'm currently on:
WIN10 64 bit last version
Powershell 7.4.4
i cant seem to be able to render the text correctly after installing the profile:
~ 
~ 
~  cd .\Desktop
~\Desktop 

now one more thing is that the profile errored out since i already had chocolatey so i deleted the folder and the script seemed to go without issue, problem is the script itself has issues if it finds the same chocolatey installation the script itself installed 5 minutes ago instead of skipping it.

i do understand that ohmyposh says:
To ensure correct rendering of the glyphs you will need to enable the option Use the new text renderer ("AtlasEngine") in your terminal settings. For further details, see here.
but it gives the same thing on the terminal app as well.

@BletaJonatan
Are you using Powershell or Windows Terminal?
Both you need to set the default font, and it need to be a Nerd Font to be able to see icons

the 0xproto nerd font is installed and selected, the edit profile function was not used.

i've understood that i needed to reapply the theme as well in the profile ps1, my bad.


file name mustnot be an absolute path

i have installed it on fresh installation on firefox developer edition
on save it show this message file name must not be an absolute path
following pattern is showing in box
C:/Users/mypc/Downloads/graphics/${pageTitle}/${index} - ${name}${ext}

You have to use a relative path for the filename. It is always related to the default download folder. Try changing the pattern to graphics/${pageTitle}/${index} - ${name}${ext}


Inconsistent encoding in provable authn account proofs

Problem
I was reviewing this PR from @bfbachmann, which ports the account proof encoding to the Go SDK, and noticed some potential issues in the encoding here: https://github.com/onflow/fcl-js/blob/master/packages/fcl/src/wallet-utils/encode-provable-authn-signing.js#L8-L20
If I'm reading correctly, this is how the encoding works now:
MESSAGE =
  HEX(USER_DOMAIN_TAG) +
  RLP(
    HEX(APP_DOMAIN_TAG),
    HEX(ADDRESS),
    TIMESTAMP)
  )

In particular, I don't think we should use hexadecimal (UTF-8) strings when passing addresses to the RLP function, as this inconsistent with how addresses are encoded inside transactions. The Flow protocol represents addresses as byte arrays, so for a canonical data structure like this, I think makes sense to just pass the raw bytes rather than a string. This also avoids a double encoding step for other implementors.
The APP_DOMAIN_TAG also doesn't need the extra hex encoding.
I think the whole thing can be simplified to:
# Assume USER_DOMAIN_TAG, APP_DOMAIN_TAG, ADDRESS are of type Buffer

MESSAGE =
  HEX(
    USER_DOMAIN_TAG,
    RLP(
      APP_DOMAIN_TAG,
      ADDRESS,
      TIMESTAMP
    )
  )

Context
This affects implementations of provable authn in FCL wallets.

Hi all - after consulting with the team, the path forward we're considering is to:

As @psiemens suggested, leave all field that can exist as Buffers before RLP encoding as Buffers. e.g:

// USER_DOMAIN_TAG, APP_DOMAIN_TAG, ADDRESS are Buffers
// TIMESTAMP is Number

MESSAGE =
  HEX(
    USER_DOMAIN_TAG, // Buffer, right padded to 32 bytes long
    RLP(
      APP_DOMAIN_TAG, // [Optional] Buffer, right padded to 32 bytes long
      ADDRESS,  // Buffer, left padded to 8 bytes long
      TIMESTAMP // Number
    )
  )

This strategy will help maintain greater consistency with how these fields are treated when encoded in other areas of Flow.
We will need to test that this new path forward will maintain backwards compatibility. As we learn more, we will keep this issue updated with our progress.


Revert "[8.x] Allow eloquent model type in be/actingAs"

Reverts laravel/framework#38055

Why was this reverted ? 🤔