Do not send router to MPAs

Describe the problem
I recently made the same simple app using two frameworks for comparison, SvelteKit and Astro + svelte with a single reactive component in each
The component consisted of a large list of products fetched during server-side rendering and a search bar that filtered the list on the fly.
The app made using Astro resulted in an html file twice the size as it needed to serialize the product list, while the app made using SvelteKit did not as the data fetching was done in a universal load
Even so, the total size of the app created with SvelteKit was three times bigger than the app created using Astro due to the javascript sent, since both had only 1 identical component, I could only assume that the culprit for the size of the app was the client router, which was not being used since the app only had one page
Describe the proposed solution
Don't send the router if:

The app only has one page
No page references another page of the same app
All links are under the tag of a data-sveltekit-reload attribute

Alternatives considered
No response
Importance
nice to have
Additional Information
No response

The app only has one page
No page references another page of the same app
All links are under the tag of a data-sveltekit-reload attribute

IMO, this is wayyyy too complicated a heuristic for a feature that's not likely to be useful for most people. If we expose a way to serve the app without a client-side router, it should just be an opt-in config option.

I really don't understand what the complexity would be to create the functionality, but at least from a pure guess it seems to me that:

Among all the points, checking the number of pages is really quite simple.
The anchor tag check suggested in points 2 and 3 is already something the framework does during pre-rendering

Anyway, if it really isn't feasible, an optional configuration would be good enough for me, but it would seem like an inferior experience to what the framework usually offers

already something the framework does during pre-rendering

Sort of, but not really -- it's totally possible for a link to be part of a dynamic route that's not hit during prerendering (this is the whole point of config.kit.prerender.entries and the entries page-level export), and it's also possible to dynamically render links in such a way that we wouldn't ever see them during build (for example, in an each block that's only triggered under some runtime conditions). I don't think it's realistically possible for us to determine either one of these, but maybe Rich'll chime in with some magic solution.

Thanks for the explanation, now I understand the complexity a bit better
Apparently an opt-in config is the best you can get then
When I created the issue I thought it was just a nice thing to have, but on second thought it's not even the first professional project I've worked on where something like that would be useful
I think it would be something interesting for any MPA or One Page App

Comparisons like 'three times bigger' aren't all that valuable in this context, because we're talking about some fairly modest numbers. The amount of code we're talking about won't affect user experience at all, and will be overtaken by app code for anything non-trivial. (It will also be cached immutably, so the user only downloads it once.)
Building the framework in such a way that the router was optional would add considerable complexity, once you start to factor in things like 'beforeNavigate/afterNavigate callbacks still need to be called at the right time'. You'd basically be talking about maintaining two separate SvelteKit clients.
So the question is: is it worth the maintenance overhead? I would argue that it isn't, since there's essentially no real world impact.


Doesn't follow scale

Shard scenes don't follow the parents scale even when dynamically generated

@valkyrienyanko Any clues on this? Not getting any help on the forums haha. The shards themselves follow the scale but when I try and scale the container or parent it doesn't work, and scaling just the shards doesn't move their position so they are glitched in one another.

I only looked at the C# to quickly touch up some things here and there. But I never tried testing out the project itself. I will try to understand this project more since you mentioned me. But for now I sleep as it is 3 am.

e

Ah no problem if no problem, you just seemed quite knowledge in this so thought I would try haha.

https://user-images.githubusercontent.com/6277739/235366345-2a621a8d-13e0-4115-9200-36f048f54eb6.mp4
Works for me?

Yeah, the shards follow the scale but they spawn inside each other because their positions aren't scaled. This means they bug out as seen in your video. If possible I would like for their positions to all move accordingly so without explosive power it just falls flat like the 1x scale cube.

Any ideas?


[OSX] "Uncaught Error: ENOENT: no such file or directory, lstat '/index.js'", source: ATOM_SHELL_ASAR.js (118)

hey everyone,
i'm getting this error after starting the electron process.
using electron 0.30.4
"Uncaught Error: ENOENT: no such file or directory, lstat '/index.js'", source: ATOM_SHELL_ASAR.js (118)
i narrowed it down a bit already.
this warning shows up when building the app with webpack and target set to "atom"
a problem with the ndarray-fill package
WARNING in ../~/ndarray-fill/~/cwise/~/static-module/~/falafel/~/acorn/dist/acorn.js
Critical dependencies:
1:478-485 This seems to be a pre-built javascript file. Though this is possible, it's not recommended.
Try to require the original source to get better results.
@ ../~/ndarray-fill/~/cwise/~/static-module/~/falafel/~/acorn/dist/acorn.js 1:478-485
if i dont require ndarray-fill anywhere the error in electron goes away but the app itself of course crashes here and there cause i need ndarray-fill in different places.
any ideas?

Can you provide a small demo app?

Closing until there is more information provided.


Make advertising of NUMA node optional

This change adds support for making advertising of NUMA node optional.
This can be done per resource pool by setting the config
"exclude_topology" to true. Default behavior is to advertise NUMA node
information.
#320
Signed-off-by: Ravindra Thakur<EMAIL_ADDRESS>

/cc @adrianchiris @Eoghan1232

Looks good to me. Thank you @rthakur-est

LGTM

when will this be merged?

LGTM,
need to update README with new resource config knob. this can be done in this PR or a separate one as discussed in Yesterday's community meeting.

LGTM,
need to update README with new resource config knob. this can be done in this PR or a separate one as discussed in Yesterday's community meeting.

My colleague @rthakur-est is on leave. He will push another review updating the README soon. This review can be merged if its good.

@SchSeba do you have additional comments ? shall we proceed with merge ?

raised PR for documentation - #425

Merging.


impl Deref for set::Entry

This originally suggested by @caelunshun in https://github.com/crossbeam-rs/crossbeam/pull/535#issue-440783380.
cc #635

bors r=Vtec234


Reduce competition progress chart to only top 5

Right now it's top 10, and it might make the graph too crowded.
It also would be nice to have an algorithm that "smooths" snapshot lists, as you can see in the image, some of the snapshots are too close together, and it's a diservice to the user. It would be best to have an algorithm to select which ones are relevant enough.

On top of this, implement #150 on the client-side with a "density" toggle for the chaert component.


Major updates

Coverage decreased (-0.09%) to 96.243% when pulling 1660bc79e83fab224c0b5b5f2742760f092e7d48 on dev into 464e1446e2d1df30ebf55b2c05b9215f7dfd6e88 on master.


New Sheet: Blood and Doom v1.0.0

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: Blood and Doom

The publisher of this game is: DicetaleGames

The name of this game system/family is: Blood and Doom

[x] I have followed the Character Sheets Standards when building this sheet.

[x] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

This is a publisher-supported character sheet for upcoming RPG Blood and Doom by Dicetale Games. The sheet was developed by me on contract with them.
You can find the publisher here: https://dicetalegames.com/

Initial release of the sheet.

Full support for all necessary information during play.
Action, damage and Doom rolls
Re-rolling the failed dice of the last Action Roll, automatically deducting Doom points
Character Path tab for biographic information
3 different background themes

Character Sheet Info Roll20 Internal Use only.


Fixed bug breaking pip-sync on Python 3, raising TypeError

Fixes #569
Moved and renamed resolver._dep_key to utils.key_from_ireq and use it
for the InstallRequirements sort in sync.sync.
In the future, we might want to change calls like
key_from_req(ireq.req) to key_from_ireq(ireq), but I'll keep the
change to a minimum here for this bugfix before doing additional tests.
Contributor checklist

[x] Provided the tests for the changes
[x] Added the changes to CHANGELOG.md
[ ] Requested (or received) a review from another contributor

@jdufresne This works on Docker for me, can you confirm this works for you?
(pip install git+https://github.com/vphilippon/pip-tools@fix-pip-sync-py3#egg=pip-tools)

Worked for me! Thanks for the quick fix.

@vphilippon 1.10.1 is out.


Show valgrind and checkstyle errors

e.g. submission: https://tmc.mooc.fi/mooc/paste/IMGY3ynRyubazIfcvfq_8A#valgrind

Print the string from getValgrind method at submit results.


[SPARK-26006][mllib] unpersist 'dataInternalRepr' in the PrefixSpan

What changes were proposed in this pull request?
Mllib's Prefixspan - run method - cached RDD stays in cache. After run is comlpeted , rdd remain in cache.
We need to unpersist the cached RDD after run method.
How was this patch tested?
Existing tests

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #98728 has started for PR 23016 at commit 2e3b089.

cc @srowen Kindly review

I'm not sure about that, because the returned PrefixSpanModel has an RDD that depends on that RDD. We could cache the final RDD instead and materialize it; that could make more sense.
In other places we have done such a thing only when the input is cached, in order to kind of follow the caller's lead, but there isn't a consistent standard for this.
I'd be OK improving this to persist the final RDD only, and then unpersist the intermediate one. That makes at least more sense. You can cache at the same storage level as the input (which might be NONE)

Thanks @srowen , I will update the PR

Test build #98853 has finished for PR 23016 at commit 5c4949d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98853/
Test PASSed.

Test build #98950 has started for PR 23016 at commit 7a4ede8.

Test build #98951 has started for PR 23016 at commit a4c5597.

Test build #98950 has finished for PR 23016 at commit 7a4ede8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98950/
Test PASSed.

Test build #98951 has finished for PR 23016 at commit a4c5597.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged to master

Thank you @srowen

Wouldn't the added count increase the execution time? did you do a benchmark?

I am currently using it with spark 2.3 as

org.apache.spark
spark-mllib_2.11

How can i get this fix?

@idlevi Actually, input and output of the prefix span are RDD. Earlier intermediate rdd was cached, now final rdd is cached, and materialized it. So, if you materialize the model, earlier it will compute from the intermediate level, now it directly get from the finalRdd.
I ran all the UTs in the prefixSpanSuite, and there is hardly any time difference with/without the patch.

I am currently using it with spark 2.3 as
org.apache.spark
spark-mllib_2.11
How can i get this fix?

You can cherry pick the commit from the master branch.


Windows 10 error unless run as administrator

Etcher version: v1.0.0-beta.13
Operating system and architecture: Windows 10 1607 AMD x64
Do you see any meaningful error information on DevTools? This error text below:

tracker.js:10 WRITER: Attempting to elevate
tracker.js:10 Wed Aug 17 2016 17:43:30 GMT+0100 (GMT Summer Time) Flash error
tracker.js:10 Error: { Error: Command failed: C:\Users\zacchaeus\AppData\Local\Temp\8AF3.tmp.exe -c -n -h -w set ELECTRON_RUN_AS_NODE=1 && set ETCHER_INTERNAL_LOG_FILE=C:\Users\ZACCHA~1\AppData\Local\Temp\etcher-10176ErEmPClzcjQr.log && call C:\Program Files (x86)\Etcher\Etcher.exe C:\Program Files (x86)\Etcher\resources\app.asar\lib\src\child-writer\writer-proxy.js C:\Program Files (x86)\Etcher\resources\app.asar C:\Users\zacchaeus\Desktop\Raspberry pi\2016-05-27-raspbian-jessie.img --robot --drive \\.\PHYSICALDRIVE1 --unmount --check --log C:\Users\ZACCHA~1\AppData\Local\Temp\etcher-10176ErEmPClzcjQr.log

    at ChildProcess.exithandler (child_process.js:214:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:850:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
  cause:
   { Error: Command failed: C:\Users\zacchaeus\AppData\Local\Temp\8AF3.tmp.exe -c -n -h -w set ELECTRON_RUN_AS_NODE=1 && set ETCHER_INTERNAL_LOG_FILE=C:\Users\ZACCHA~1\AppData\Local\Temp\etcher-10176ErEmPClzcjQr.log && call C:\Program Files (x86)\Etcher\Etcher.exe C:\Program Files (x86)\Etcher\resources\app.asar\lib\src\child-writer\writer-proxy.js C:\Program Files (x86)\Etcher\resources\app.asar C:\Users\zacchaeus\Desktop\Raspberry pi\2016-05-27-raspbian-jessie.img --robot --drive \\.\PHYSICALDRIVE1 --unmount --check --log C:\Users\ZACCHA~1\AppData\Local\Temp\etcher-10176ErEmPClzcjQr.log

       at ChildProcess.exithandler (child_process.js:214:12)
       at emitTwo (events.js:106:13)
       at ChildProcess.emit (events.js:191:7)
       at maybeClose (internal/child_process.js:850:16)
       at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
     killed: false,
     code:<PHONE_NUMBER>,
     signal: null,
     cmd: 'C:\\Users\\zacchaeus\\AppData\\Local\\Temp\\8AF3.tmp.exe -c -n -h -w set ELECTRON_RUN_AS_NODE=1 && set ETCHER_INTERNAL_LOG_FILE=C:\\Users\\ZACCHA~1\\AppData\\Local\\Temp\\etcher-10176ErEmPClzcjQr.log && call C:\\Program Files (x86)\\Etcher\\Etcher.exe C:\\Program Files (x86)\\Etcher\\resources\\app.asar\\lib\\src\\child-writer\\writer-proxy.js C:\\Program Files (x86)\\Etcher\\resources\\app.asar C:\\Users\\zacchaeus\\Desktop\\Raspberry pi\\2016-05-27-raspbian-jessie.img --robot --drive \\\\.\\PHYSICALDRIVE1 --unmount --check --log C:\\Users\\ZACCHA~1\\AppData\\Local\\Temp\\etcher-10176ErEmPClzcjQr.log' },
  isOperational: true,
  killed: false,
  code:<PHONE_NUMBER>,
  signal: null,
  cmd: 'C:\\Users\\zacchaeus\\AppData\\Local\\Temp\\8AF3.tmp.exe -c -n -h -w set ELECTRON_RUN_AS_NODE=1 && set ETCHER_INTERNAL_LOG_FILE=C:\\Users\\ZACCHA~1\\AppData\\Local\\Temp\\etcher-10176ErEmPClzcjQr.log && call C:\\Program Files (x86)\\Etcher\\Etcher.exe C:\\Program Files (x86)\\Etcher\\resources\\app.asar\\lib\\src\\child-writer\\writer-proxy.js C:\\Program Files (x86)\\Etcher\\resources\\app.asar C:\\Users\\zacchaeus\\Desktop\\Raspberry pi\\2016-05-27-raspbian-jessie.img --robot --drive \\\\.\\PHYSICALDRIVE1 --unmount --check --log C:\\Users\\ZACCHA~1\\AppData\\Local\\Temp\\etcher-10176ErEmPClzcjQr.log' }

    at Socket.child.stderr.on (C:\Program Files (x86)\Etcher\resources\app.asar\lib\src\child-writer\index.js:85:29)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:172:18)
    at Socket.Readable.push (_stream_readable.js:130:10)
    at Pipe.onread (net.js:542:20)

Then when I press ok a banner says 'Your removable drive may be corrupted'. I'm trying to flash a new sd card which I've formatted, and it worked fine flashing with USB Image Tool.
I ran etcher with admin privileges and it now works, so this appears to be some problem with elevating privileges.

Hey there,
Thanks a lot for reporting. This is indeed a very weird one. Can you check if you can reproduce back if running as a normal user and going through the UAC elevation dialog again?
If so, can you run the command being reported as failing (C:\Users\zacchaeus\AppData\Local\Temp\8AF3.tmp.exe -c -n -h -w set ELECTRON_RUN_AS_NODE=1 && set ETCHER_INTERNAL_LOG_FILE=C:\Users\ZACCHA~1\AppData\Local\Temp\etcher-10176ErEmPClzcjQr.log && call C:\Program Files (x86)\Etcher\Etcher.exe C:\Program Files (x86)\Etcher\resources\app.asar\lib\src\child-writer\writer-proxy.js C:\Program Files (x86)\Etcher\resources\app.asar C:\Users\zacchaeus\Desktop\Raspberry pi\2016-05-27-raspbian-jessie.img --robot --drive \\.\PHYSICALDRIVE1 --unmount --check --log C:\Users\ZACCHA~1\AppData\Local\Temp\etcher-10176ErEmPClzcjQr.log in this case, but will be slightly different for sure, while you keep Etcher and the error window open (otherwise the temp files are wiped out)? What do you get?

The UAC elevation dialog never appears.
When trying to run that command I get a system Error:
The program can't start because MSVCR120.dll is missing from your computer. Try reinstalling the program to fix this problem.
I repaired the Visual C++ Redistributable Packages for Visual Studio 2013 (which didn't seem to do anything)
Then I uninstalled/reinstalled Etcher and it now seems to work.

Hi @zacchaeusluke ,
Thanks for the quick answer. As far as I can see, that file is a library that should be coming from Visual Studio 2013. My bet is that repairing Visual Studio 2013 fixed the issue, but took an Etcher re-install for the program to be re-configured correctly.
I'm closing this as resolved, but please re-open if the issue ever happens again!


Bump minimal python version to 3.9 (#4149)

Pull request opened by the merge tool on behalf of #4149

Merged into branches iso5 in 1aefa3b81860e83c79838a698130a8a4403172eb


Mouse missing option for show / hide cursor

The Mouse class does not implement the equivalent of the XNA Game Studio Game.IsMouseVisible property. It's currently only implicit with the Absolute vs. Relative mode.

Fixed in this commit


master latest run flutter doctor error

Failed to download
https://storage.flutter-io.cn/flutter_infra_release/flutter/4ac53a5b86709351aa53
e011c6fd8703ee2bd8fe/flutter_patched_sdk_product.zip. Ensure you have network
connectivity and then try again.
Exception: 404

@xiaocode337317439
As the error indicates, it could be happening due to poor / slow network connectivity. Try again with a better / faster network connection. See this for more details.
Closing, as this is related to connectivity.


Issue number 4 - README

README
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

I completed the readme and I now understand the importance in having a readme for web development. It explains what the project and the purpose and what my project does. It also has some credentials to the work, like tutorials, collaborators, etc.


cli: fix underlined multi-line help text

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[ ] Have you successfully run brew man locally and committed any changes?

Help text such as *May remove files which are shared between applications.* is automatically underlined by CLI::Parser
This pull request fixes underlines for wrapped text made to fit the terminal window.
This can be tested with brew help remove, particularly these two lines:
                                   May remove files which are shared between
                                   applications.

Without this PR, the spaces preceding the word applications are underlined.

Review period will end on 2020-12-22 at 00:00:00 UTC.

Review period skipped due to critical label.


arel-extensions clobbers order clauses in sqlite

I'm not sure how this has never come up, but it seems like order clauses are clobbered when arel-extensions is activated. I've created a test that replicates this.
This behaviour seems limited to having arel-extensions along with sqlite. If you remove gem "arel_extensions", "2.0.8" from the test, or use mysql instead of sqlite, the test passes.
I've run this on ruby 2.6. Rails 6 with every 2.x version fails. I've also tried using rails 5 and arel_extensions 1.2.12 and it fails there as well.

The strange thing is User.order(:score).to_sql does in fact show the correct statement, but when the query executes, the order clause is gone.

Seems to be related to https://github.com/Faveod/arel-extensions/blob/ad9e1be64c055e20b986c0e5764abc968f0c3f19/lib/arel_extensions/visitors/sqlite.rb#L370-L373
Changing the query to User.order(:score).limit(5) will pass the test.

Hi Daniel,
Thanks you for this report.
This code has been added to remove order in subqueries when there was no limit. Otherwise the query breaks in most DBMS.
In other DBMS this code is triggered only on subqueries but apparently not in Sqlite visitor (maybe because of the adapter) in triggered always.
Next gem will correct that.


fixing link for new signature

fixing link
Description
Please include a summary of the change and which issue was fixed by it.
Fixes # (issue)
Type of change
Please delete the option that is not relevant.

[ ] Signature (please update title to "Signature 'your name'")
[ ] Propose Update to Manifesto (please update title to "Propose Update to Manifesto - 'update description'")

cert seems to be expired on https://garygruver.com/engineering-digital-transformation.php causing pipeline to fail. should we update  link to amazon? or some other source?

I'd switch into Amazon and I'll also inform Gary.


DeOldify.hmodel using Stable Weights

Hi - Great package!
Is it please possible to also convert the Stable Weights as well, sometimes they colourize better
Thanks

I agree that this would be a very useful addition. What does it take to convert the model? I have never heard of the .HMODEL format before...

What does it take to convert the model?

To do this, it is needed to read the original .pth checkpoint, extract the parameters of the neural network from it, convert it to the half data type and sequentially save it in binary form to a file.

I have never heard of the .HMODEL format before...

This is not a file format. This is a binary file containing half numbers without any metadata. To read such a file, it is necessary to know in what sequence and what dimension the tensors were written to the file. This is the simplest and most effective way to store weights for a neural network in this case.

Is this script available to read the original .pth file and extract the parameters to create the .hmodel file?

I tried to do this, but I ran into a problem: it required too much memory to perform coloring with stable weights.

It looks like this problem has been solved. A new convolution algorithm and memory allocation using a different function will solve this problem. Work on stable weights has begun.

Stable model support is implemented. See the startup instructions for more information.


Adding test

Separating the test from this PR: https://github.com/rancher/rancher/pull/22388

This PR will be ready for merge once the original PR is fixed and merged. Otherwise, this will result in a test failure and drone will have issues.


Investigate string[pyarrow] failure

Previously, changing type string to string[pyarrow] caused some issues in EvalML in the 0.16.0 release of WW. We reverted these chages in 0.16.1, but this issue tracks looking into these failures and re-adding this type if possible.

EvalML might be failing because of this:

https://github.com/pandas-dev/pandas/issues/42597


Naming convention method for a new module- Azure cognitive search service

Need support for automatic caf naming convention method to a new module that will be developed - azure cognitive search service

https://github.com/aztfmod/terraform-provider-azurecaf/pull/269

Closing as merged


[BLOG] Green Reviews Initiative Progress: Key Milestones and Next Steps

Authors: @immavalls @AntonioDiTuri
Reviewers: @nikimanoledaki @AntonioDiTuri @rossf7
TAG ENV Lead: @guidemetothemoon

Abstract
This blog will introduce the Green Reviews WG, highlighting/summarizing the progress so far (e.g., https://github.com/cncf-tags/green-reviews-tooling), the milestones reached, and next steps.
Scope
Beginner-friendly introduction to what the WG is doing, with more technical content, what has been built so far. and where to go from here. It can also serve as a call to action for contributors that might be interested in the WG.
Expected audience

Beginners who have none or little knowledge about what the WG does.
Future contributors to the WG.

Goals and Non Goals
Goals:

Awareness of the WG.
Explain what the group has been working on, what is next, and how to contribute.

Non-goals:

Get too technical or deep dive into the topics, we can point readers to the WG's design document that should be migrated to the WG repo.

Tasks

[ ] Outline Blog post

[x] [Author] described the abstract of the blog post, defined the scope, goals and non-goals, and defined the expected audience.
[ ] [Author] notified TAG ENV community to review the outline via Slack on the tag-env-sustainability channel.
[ ] [TAG ENV Lead] One of the TAG ENV leads assigned themselves to wrangle the blog
[ ] [TAG ENV Lead] Blog post outline and theme has been discussed

[ ] [Author] Blog post written and ready for review
[ ] Review

[ ] [Author] blog post PR opened (blog posts are added to the website/content/en/blog folder for English content, images to website/static/images/blog/<YEAR>-<MONTH>-<title>/*.jpg)
[ ] [Author] notified TAG ENV community for review via Slack on the tag-env-sustainability channel.
[ ] [Author] gave a minimum of a week to collect public feedback, depending on reviews this will get extended. If there is a major event (conference, etc.) or holidays coming up, please extend accordingly.
[ ] [Author] Feedback and comments have been resolved.
[ ] [Reviewers] reviewed blog post.
[ ] [TAG ENV Lead] reviewed blog post.
[ ] [TAG ENV Lead] ready to get published.
[ ] [TAG ENV Lead] notified one of the ToC liaisons to sign off the blog post.
[ ] [TAG ENV ToC Liaison] reviewed blog post.
[ ] [TAG ENV Lead] merged blog post.
[ ] optional [TAG ENV Lead] schedule the blog post on the CNCF blog next to the TAG ENV blog
[ ] [Author] Wrote feedback about the blog post process as a comment under this issue

Comments
Draft document in Google Docs: https://docs.google.com/document/d/1_MnYd1hHhRysHsWCfaSuNpAEc09GuBF61Qt0rCqJDrk/edit?usp=sharing

@nikimanoledaki @AntonioDiTuri @rossf7 @leonardpahlke, can you provide further details so we can start the write-up?
@guidemetothemoon can you review the issue, assign labels, possibly create the initial google doc? I am not sure I have access to do that 🙏

Created the Google Docs file: https://docs.google.com/document/d/1_MnYd1hHhRysHsWCfaSuNpAEc09GuBF61Qt0rCqJDrk/edit?usp=sharing

Thanks a lot @immavalls for creating the issue and willing to contribute to the blog and thanks @leonardpahlke for creating the draft document. I've added labels and linked the doc to the issue description.
@nikimanoledaki @rossf7 @AntonioDiTuri please add some highlights to what you would like to be included into the post to the draft doc. Also, will one of you be able to assist Imma and others who will be writing the blog post to ensure that they get all the necessary information?
I set the deadline to KubeCon+CloudNativeCon EU but we'll see if we manage that.
@caradelia @patricia-cahill @savitharaghunathan FYI.

Thanks @guidemetothemoon I created an outline in https://docs.google.com/document/d/1_MnYd1hHhRysHsWCfaSuNpAEc09GuBF61Qt0rCqJDrk/edit?usp=sharing, if you can have a look, together with @nikimanoledaki @rossf7 @AntonioDiTuri , I can start a draft. I wanted to make sure this is what we want to share in the blog or if we have different goals.

Thank you all for leading this! 💚
@immavalls, I added a few additional links to your comments in the doc. As you pointed out, there should be enough info to write a summary of the project from the Charter, Roadmap, current Milestone, docs, Community section in the README, and Contributing guide.
If you have any questions or if I can review things in a few days, please let me know. We can also grab some time to chat anytime next week and/or the week after :)
We could also add more content as a group during the next WG Green Reviews meeting in 2 weeks on March 13th.

Thanks @nikimanoledaki I will try to have an initial draft in a week so we can further discuss 🙌

Do we plan to release the blog before Kubecon (i suggest so - but its just 2 weeks away)? cc @caradelia @savitharaghunathan. I will assign @guidemetothemoon as TAG Lead Liaison to this blog. @nikimanoledaki @AntonioDiTuri @rossf7 could you review the content once the initial draft is ready?
TYSM @immavalls! 🙌

@nikimanoledaki @AntonioDiTuri — did we already placed this issue in wg-green-reviews with a call for contribution? Perhaps someone would like to support @immavalls writing it.

@leonardpahlke do you think that we need one more issue for this since the issue is already visible on the WG project board https://github.com/orgs/cncf/projects/10/views/12 ? It has also been added as an agenda point for the Green Reviews WG meeting last week.

@nikimanoledaki @AntonioDiTuri — did we already placed this issue in wg-green-reviews with a call for contribution? Perhaps someone would like to support @immavalls writing it.

@leonardpahlke - shared a callout on the channel now!
@guidemetothemoon added the issue to the WG board + mentioned it during the last WG meeting as well 👍 I mentioned in my earlier comment that I can meet with Imma to go through it and/or review it anytime.
@immavalls I added a point to the agenda for the WG meeting next week so that we can go over it, answer any questions, add content, etc.

@immavalls I am up for helping in writing the article, I will give my inputs soon :)

Thanks @AntonioDiTuri 🙌

@immavalls @AntonioDiTuri thank you for working on this blogpost. My one suggestion is to change cloud-native to cloud native as cncf prefers the latter style. I noted it in the doc but not on all the occurrences, thats why mentioning it here.

Thanks @savitharaghunathan I replaced all the occurrences! And we'll keep an eye, Grammarly suggests cloud-native and I might fall for that again

@immavalls @AntonioDiTuri Just checking in on the progress. Are we on target to get this published before KubeCon? Do you need any help from the leads or co-chairs? happy to support in any way I can.

Thanks for checking in @savitharaghunathan. From my side, we are okay. I did the intro and closing and reviewed the comments. Open to additional comments if anyone else has the time to read it. Once we are ok with the draft, @AntonioDiTuri wrote the progress update, I can open the PR for the blog. I'm not sure if we want to wait until next week as this is on the agenda for the WG meeting @nikimanoledaki ?

I reviewed the comments related to the project update and modified accordingly. Is there anyone we could refer to to have a WG-logo? Also if anyone has ideas for the picture in that section I am open to suggestions :)

@AntonioDiTuri @immavalls @leonardpahlke I added some adjustments to the intro and conclusion of the blog post + blog post title and such. In addition for the mid-section of the blog post I've added  suggestions for the section and subsection titles + notes on what those sections should include and how some of the content can be moved around a bit. It's a combination of direct notes and comments. Does this help/make sense?
I didn't have enough time to review further on the mid-section but I'll see if I can find some time during the week. Don't hesitate to modify as you see fit in case you have any objections ☺

Hi @guidemetothemoon thanks for the structure proposal! I reshaped my content and reviewed it according to your suggestions! Please Let me know if you have some other comments.

@AntonioDiTuri @nikimanoledaki @leonardpahlke @immavalls @rossf7 I just did one more detailed review of the document - added minor changes directly and added some comments and suggestions to some minor improvements before it LGTM from my side. Please take a look and let me know if there's a need with a final review once all the comments are resolved😊

Likewise, I left some final suggestions then LGTM from my side as well!

looks good.

@AntonioDiTuri @immavalls all reviewers have now signed off and I think that we're good to create a PR and get the blog post published!🥳 Can one of you create a PR, please, if you have time?
Great work and effort everyone involved, thanks a lot for the time you put into making this blog post happen!💚
@savitharaghunathan FYI, the blog post is ready and we'll create a PR soon to get it published on the TAG ENV website asap, but you also mentioned that we should send it over to publish on CNCF website as well so here's a heads up 😊

I can create the PR @guidemetothemoon. Is it okay to have it later today?

Yes, sounds great, @immavalls, thanks a lot!

@savitharaghunathan FYI, the blog post is ready and we'll create a PR soon to get it published on the TAG ENV website asap, but you also mentioned that we should send it over to publish on CNCF website as well so here's a heads up 😊

Hmmm, do we want to get it published at both the places then? @leonardpahlke


NULL Item in Personalizations

Issue Summary
We are sending the same individual email to 100s/1000s of users with substitutions so that certain parts of the email are unique to the individual recipient.
I believe my logic is sound and as you will see below the resulting JSON payload look correct, except for one thing. The first item in the personalizations array is NULL.
Steps to Reproduce
Here is some truncated code that we are using. Since SendGrid can only process 1,000 emails at a time, we chunk the returned array of users from the database into separate arrays. So, for example, if we have to send 3,000 emails, this will chunk into 3 ($i) and then the personalization will loop through the users in those chunks ($j). This will result in making 3 requests of 1,000 personalized emails.
This all works great.
for ($i = 0; $i < $intNumberOfChunks; $i++) {

    $objSendGrid = new SendGrid(SENDGRID_API_KEY);
    $objEmail = new SendGrid\Mail\Mail();

    $objFrom = new SendGrid\Mail\From(EMAIL_FROM_ADDRESS, EMAIL_FROM_NAME);
    $objEmail -> setFrom($objFrom);

    $objSubject = new SendGrid\Mail\Subject("test subject");
    $objEmail -> setSubject($objSubject);

    $objContent = new SendGrid\Mail\Content("text/html", "test content");
    $objEmail -> addContent($objContent);

    for ($j = 0; $j < count($arrChunkedUserEmails[$i]); $j++) {

        $objPersonalization = new SendGrid\Mail\Personalization();

        $objTo = new SendGrid\Mail\To($arrChunkedUserEmails[$i][$j], $arrChunkedUserFirstNames[$i][$j] . " " . $arrChunkedUserLastNames[$i][$j]);
        $objPersonalization -> addTo($objTo);

        $objPersonalization -> addSubstitution("{{firstname}}", $arrChunkedUserFirstNames[$i][$j]);

        $objPersonalization -> addSubstitution("{{lastname}}", $arrChunkedUserLastNames[$i][$j]);

        $objEmail -> addPersonalization($objPersonalization);

    }

    echo(json_encode($objEmail, JSON_PRETTY_PRINT));

    $response = $objSendGrid -> client -> mail() -> send() -> post($objEmail);

}

The trouble comes when I view the JSON of the $objMail. Here is a truncated example of the JSON payload I get.
"personalizations": [
    null,
    {
        "to": [
            {
                "name": "User One",
                "email"<EMAIL_ADDRESS>            }
        ],
        "substitutions": {
            "{{firstname}}": "User",
            "{{lastname}}": "One"
        }
    },
    {
        "to": [
            {
                "name": "User Two",
                "email"<EMAIL_ADDRESS>            }
        ],
        "substitutions": {
            "{{firstname}}": "User",
            "{{lastname}}": "Two"
        }
    }
],
"from": {
    "name": "Test From",
    "email"<EMAIL_ADDRESS>},
"subject": "test subject",
"content": [
    {
        "type": "text\/html",
        "value": "test content"
    }
]

The JSON payload looks correct except for the first NULL item personalization array.
Does anybody know why the NULL is being inserted?
Thanks!
EDIT: I just noticed the person in ISSUE #650 was having a very similar issue to me with the NULL personalization item. I implemented the fix (inserting a from address in the mail constructor) and it seems to have worked.
new Mail(new<EMAIL_ADDRESS>'AppName'));

My question now is why does the NULL issue happen? And, how does inserting a from address into the mail constructor fix it? Nowhere in any docs have I seen the from address inserted directly into the mail constructor.
Technical details:

sendgrid-php Version: master (latest commit: 7.2.0)
PHP Version: 5.6.35 via WAMP3

Good catch @mlammert! I've added this to our backlog for further investigation.
When you use the constructor, we create a default personalization object for you. I believe that is probably the source of this odd behavior.
With Best Regards,
Elmer

@thinkingserious
So, I know inserting the from address in the mail constructor seems to get rid of the NULL item. However, that seems sort of "hack-ish" to me.
Is there a better recommended way to remove the NULL item from the personalziation array?
Thanks!

I agree @mlammert, this is not expected behavior. This issue is currently on our backlog for an investigation and fix. Thanks!

@thinkingserious
Did some debugging here:
If there’s no parameters passed to \SendGrid\Mail\Mail constructor, it initiates personalization attribute with an empty Personalization instance immediately followed by a return.
if (!isset($from)
    && !isset($to)
    && !isset($subject)
    && !isset($plainTextContent)
    && !isset($htmlContent)
    && !isset($globalSubstitutions)
) {
    $this->personalization[] = new Personalization();
    return;
}

I couldn’t see any specific reason for initialising like this. Please correct me if I’m wrong here.
If this initialisation is removed the above mentioned issue will get resolved.
Please let me know as I’m happy to help here.

Hi @remyapv,
I believe the purpose of that initialization was to make sure there was at least on personalization created when you create a Mail object.
But I think you are right, by doing that we cause more confusion and our Kitchen Sink example would not work properly.
This issue is all yours :)
Thanks!
With Best Regards,
Elmer

@thinkingserious can you please take a look at the patch?

currently migrating from 5.0.4 to 7.3.0.
searched for hours, and this solved my {"errors":[{"message":"Invalid type. Expected: object, given: null.","field":"personalizations.0","help":null},{"message":"Invalid type. Expected: object, given: string.","field":"personalizations.1.to.0","help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#message.personalizations.to"},{"message":"Invalid type. Expected: object, given: string.","field":"personalizations.2.to.0","help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#message.personalizations.to"}]} api error.
the doc didnt give me any hints for that. :confused:

Looking now @reisraff.
My apologies @mercredo! It looks like we should be able to merge and deploy @reisraff's patch.

Fixed by #705


LDAP/AD Group +JWT Authentication

LDAP/AD Group +JWT Authentication
I feel an integral piece of the roadmap should incorporate a way to access LDAP and Windows AD groups, and issue a JWT, as well as place restrictions or filters on what data gets sent to the UI based on a group.

One suggestion is to ditch the immature Kestrel server completely and have .NET Core run on NGINX, and use NGINX's JWT modules and LDAP features for authentication via RESTful services.

@danroth27 should this get tracked somewhere?

I believe https://github.com/dotnet/corefx/issues/2089 tracks adding support for LDAP to .NET Core.
ASP.NET Core already provides support for validating JWT tokens sent as bearer tokens. We support acquiring JWT tokens via OIDC. We also plan to provide an OIDC provider component in an upcoming release.
There are no plans to ditch Kestrel - we need Kestrel as a high performance cross-platform web server that is independent of any one particular host. But you can still use ASP.NET Core with Nginx
Does that cover all of the scenarios you are interested in?

I'm going to close this now. Let us know if there are still more questions.


[Field] Removed the F4913 field

As per #65

It's a minor change that I'm blocked on, so I'll merge right away without waiting for a review.


Synchronizing master with release

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


Update CONTRIBUTING.md with more Review App info

Updates review app creation steps based on pairing session with @dleve123

@dleve123 - Some notes from the output:

It doesn't look like it outputted the fully resolved external endpoint
a193ef1e6e63411e9aff2127c3b176f7-543241782.us-east-1.elb.amazonaws.com

xperimental-app-shell: digest: sha256:caff3e049b7c8984d13bf5457abb738bb614c960b87dcd2b06b9a47a23e10afa size: 2425
Pushed hokusai_force:latest to<PHONE_NUMBER>24.dkr.ecr.us-east-1.amazonaws.com/force:experimental-app-shell

# Edit the K8S YAML to reference the proper Docker image
# sed -i '' 's/:staging/:auct-281/g' hokusai/auct-281.yml
#
# The weird `-i ''` is needed on MacOS:
# https://stackoverflow.com/a/44864004
# WARNING: This might not work on Linux.
sed -i '' "s/:staging/:$NAME/g" hokusai/$NAME.yml

# Edit the K8S YAML to remove the instructions that enforce that the service
# can only be accessible via Cloudflare
#
# First, remove the `loadBalancerSourceRanges:` line
sed -i '' '/loadBalancer/d' hokusai/$NAME.yml

# Then, delete all the IP address lines.
#
# WARNING: This is a bit sketchy as this will
# delete any line of the form "- [number][number][number].". This is my best
# approx for an regex for an IP address, and I'm sure that there are better
# ones.
sed -i '' "/- [[:digit:]][[:digit:]][[:digit:]]./d" hokusai/$NAME.yml

# Provision the review app
hokusai review_app create $NAME --verbose
namespace "experimental-app-shell" created
deployment.extensions "force-web" created
horizontalpodautoscaler.autoscaling "force-web" created
service "force-web" created
Created Kubernetes environment /Users/cn/Sites/artsy/force/hokusai/experimental-app-shell.yml

# Copy Force staging's ConfigMap to your review app
hokusai review_app env copy $NAME --verbose
==> hokusai exec `kubectl --context staging get configmap force-environment -o yaml`

==> hokusai exec `kubectl --context staging --namespace experimental-app-shell apply -f /var/folders/5f/kd05sp0n0dd1zmpkkh3mmtmw0000gn/T/tmpohBzXY`

# Copy the staging-shared nginx config to your review app
==> hokusai exec `kubectl --context staging --namespace default get configmap nginx-config -o yaml`

==> hokusai exec `kubectl --context staging --namespace experimental-app-shell apply -f /var/folders/5f/kd05sp0n0dd1zmpkkh3mmtmw0000gn/T/tmp4ovDL9`

2) In order to find the url, I had to run
```sh
hokusai review_app status experimental-app-shell

where I could then grab the external IP:
a193ef1e6e63411e9aff2127c3b176f7-543241782.us-east-1.elb.amazonaws.com

However, going to this, it then redirects to staging.artsy.net, without me adding anything to DynDNS.
I've just updated Dyn with this url, lets see what happens...

@damassi when you try to access the load-balancer directly, it's probably redirecting you to what it thinks is its SSL URL (but it's not, since the review app's APP_URL was probably just copied from staging).
For SSL to work correctly on the review app, you'll need to access it at a *.artsy.net name. This can be done with an actual DNS entry, or a trick that works locally is to add a line to the /etc/hosts file that associates a valid name to an IP address for that load-balancer. E.g.:
dig a193ef1e6e63411e9aff2127c3b176f7-543241782.us-east-1.elb.amazonaws.com
...
;; ANSWER SECTION:
... <IP_ADDRESS>

Then add to /etc/hosts a line like:
myreviewapp.artsy.net <IP_ADDRESS>

@joeyAghion - I've created a Dyn entry pointing to
http://experimental-app-shell.artsy.net
But it redirects to staging.artsy.net. Perhaps I have to update APP_URL to https://experimental-app-shell.artsy.net?

Yes I think you have to set APP_URL to the correct URL. Did you hokusai review_app refresh <name> after setting the updated config?
This is the line that redirects to APP_URL: https://github.com/artsy/force/blob/84446b89032ce2c5b01d182cf6a0aa080c2dcb85/src/lib/middleware/ensure_ssl.coffee#L11
I can successfully hit https://experimental-app-shell.artsy.net, but I see those asset 403 failures. I'm not familiar enough with the asset compilation to understand if that's due to the image being hosted or the config somehow.

Notably the script does set APP_URL, but there isn't a step that forces getting new pods via restart. I wonder if the 2nd to last step (after the env-setting step) should be a hokusai review_app deploy $name. This should kill 2 bids with 1 stone by:

Ensuring that we get fresh pods, with the updated environment variables
Ensuring that we run yarn publish-assets – ensuring that we are building and using the latest client.

@dleve123 - see https://github.com/artsy/force/pull/4629


Scala Kinesis Enrich: ensure correct behavior in case of resharding

@fblundun - I don't think there's anything further to check here, do you?

No, I think we know that this works now.

Cool, closing


Stopped setting tzinfo in typecast_timestamp().

This seems unneeded, although I'm not sure when it became so.

It's was added in 9b1cb755a28f020e27d4268c214b25315d4de42e and it's unnecessary since cef3f2d3c64055c9fc1757fd61dba24b557a2add.

It was required because localtime() cannot be applied to a naive datetime: https://github.com/django/django/blob/d8e233352877c37c469687287e7761e05bdae94e/django/db/backends/sqlite3/base.py#L429


Bump chip wheels to 2024.4 (sdk 1.3)

Bumps the wheels to version 2024.4 which is based on Matter SDK version 1.3

This one is ready for review/merge.
Tested for several days and found no regressions/side effects.

not merge this one yet after we released a new stable version


Remove time estimates or revise to standard, single unit (hours)

Allan votes for removing the estimates entirely as one needs to make too many assumptions and can't ever possibly be accurate.

Removed entirely revisit later


Configure different tracing provider for different workloads & workloads in different clusters

(This is used to request new product features, please visit https://github.com/istio/istio/discussions for questions on using Istio)
Describe the feature request
We are trying to export traces to different endpoint in different clusters, for example, we export traces to cloud provider for cluster A for higher stability and some advanced features, but for cluster B, we export traces to customized zipkin endpoint to reduce cost and increase confidentiality. It seems that in current version it can not be achieved since only one tracing provider can be used.
Is it possible to add annotation like tracing.istio.io/provider to specify providers workloads trying to export, when this annotation is not specified, global provider will be used. Or is there any better way to achieve that?
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

In Telemetry, you can specify which workloads to attach to, and which provider to use. This should enable this use case.


remove accidentally added duplicate file

/kind improvement
I accidentally duplicated index_node.h in #508

/lgtm


next 13 and lucid

hello there !
I hope some one can help me.
I been using lucid in next js 12 without problems, but now my site migrated to next 13.
I dont know how to make it work, site build breaks with this messages:
'''Error occurred prerendering page "/". Read more:
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined.'''
I already have working lucid with next js 12 with:
'''webpack: (config) => {
config.stats = 'verbose'; // or 'errors-only', 'minimal', etc.
config.resolve.alias['react-native-sqlite-storage'] = false;
config.experiments = {
asyncWebAssembly: true,
topLevelAwait: true,
layers: true, // optional, with some bundlers/frameworks it doesn't work without
}
return config
},
'''
If i comment the use of lucid, site builds
And if i use some parts of lucid, site builds
But for example when trying to import Emulator, site breaks as i shown before
'''import { Assets, Emulator } from "lucid-cardano";
const emulator = new Emulator([]);''''
It works for Assets for example, but not for Emulator class
I would appreciated any help
Does anybody have a full functional lucid-cardano setup for next js 13?
Regards!

This is what I used to get it working. Just got it up and running.
https://jser.dev/2023-07-25-how-lazy-works-internally/
you will have to define your own delay class, but wrap the class that contains Lucid inside of the "LazyComponent"

Same issue... There are any solution without using LazyComponents?


8955 - 8960 Unknown USB descriptor

8955 and 8960 shows unknown USB descriptor in windows after PATCH

i can also confirm.

@0x7ff this still exists on 7ffffffeb14dab3ff1d7f4335bed25140f0e098b, please help us windows A7 and A6X users :D

also not patched with #32

latest commit may or may not fix A6X (i dont know as i dont have one) and 100% not A7.

tried with latest commit but still same, now is just stucked on PATCH and does not continue..

This also is broken on Linux, PATCHING indefinitely on A7. A6X I don't now as I don't have one.

This also is broken on Linux, PATCHing indefinitely on A7. A6X I don't now as I don't have one.

haven't tested any of the latest commits for this.

i have a problem on ipad6,4 (iPad Pro 9,7)

i have a problem on ipad6,4 (iPad Pro 9,7)

That's A9X, make a new issue.

@0x7ff any way to fix this?

still broke on latest commit

dont mind me having a ton of binaries

any update?

This issue exists within the spray stage as it uses large leak method on these devices and it sometimes sends the USB packet without the header so nothing was sent to the device and we can use a different driver to fix this issue like iRemoval Pro which uses the UsbDk driver or by adding USBPcap support in gaster to reliably detect the unsent packets.

@0x7ff hmm, alright. i dont really know libusb so i cant really craft a pr.

libusbK, dont know how to install UsbDk

https://github.com/daynix/UsbDk/releases

Alright, now with UsbDk, it patches forever, like Linux does.

Alright, now with UsbDk, it patches forever, like Linux does.

you must restart first after install of usdbk pcap, also you should check if the value of usdbk upperfilter is added on the reg like this :

you must restart first after install of usdbk pcap

i rebooted, and the value of the upperfilter is correct. im on A7 iPhone6,1 (5s gsm)

you must restart first after install of usdbk pcap

i rebooted, and the value of the upperfilter is correct. im on A7 iPhone6,1 (5s gsm)

if you run this on cmd : set LIBUSB_DEBUG=4 then run gaster pwn what you get? i afraid need libusb debug version for that(this from last year i dont remember in detail)

looks like it still needs libusbk installed..

gaster_debug.log
@P5-2005 heres the debug log... its massive.

@P5-2005 yes, but linux also patches forever... so im guessing thats a different issue

@P5-2005 usbdkhelper.dll is also opensource, https://github.com/daynix/UsbDk/tree/master/UsbDkHelper

@P5-2005 yes, but linux also patches forever... so im guessing thats a different issue

if you see checkra1n on linux with A7 is same issue, because of libusb xD

@P5-2005 yes, but linux also patches forever... so im guessing thats a different issue

if you see checkra1n on linux with A7 is same issue, because of libusb xD

i know

@P5-2005 yes, but linux also patches forever... so im guessing thats a different issue

Have experienced it before..
https://github.com/0x7ff/gaster/issues/22
i think the output from kmsg has same usb descriptor error..
4,1064,190137372,-;usb 1-1: config index 0 descriptor too short (expected 25, got 9)
SUBSYSTEM=usb
DEVICE=+usb:1-1
4,1065,190137384,-;usb 1-1: config 1 has 0 interfaces, different from the descriptor's value: 1

@amats211 i meant like won't stop patching... seems like somehow it's not able to patch correctly on these devices...

@amats211 i meant like won't stop patching... seems like somehow it's not able to patch correctly on these devices...

oh that problem, you just need to put the libusb-1.0.dll in the folder where gaster.exe is before you run it

oh that problem, you just need to put the libusb-1.0.dll in the folder where gaster.exe is before you run it

@amats211 what about on linux? im on A7 (8960)


Update to current

As a consumer if this library, I'm concerned about the shear size of the changes being requested without any description or reasons being given.  Do these changes address any outstanding issues?


(docs) Revise description of trusted_server_facts setting

After merging, please regenerate man pages, eg https://github.com/puppetlabs/puppet/pull/3947

@hkenney or @hlindberg can you review?

:+1:  Looks good! One thought:
I'm not sure whether or not we need to explicitly make the distinction between what changes in an agent run vs apply. With an apply only the environment part of the hash will be present. That may be too low level for the user to care about, not sure.

@nfagerlund thoughts on ^ ??

@hkenney @kylog I think the right place for that level of detail is probably in the language reference where we talk about these pre-populated variables, not in the list of settings. I'm cool with leaving the setting description pretty high-level.

That seem's totally reasonable to me. I'm :+1: on merging this as is.

Note that Travis CI ran a build but appveyor did not. :)

This means the AppVeyor filters are working appropriately.


FIPS support invistigation

Check why microdnf complains:
“(microdnf:7): librhsm-WARNING **: 09:10:16.588: Found 0 entitlement certificates”.
What else do we need to support FIPS

From stackoverflow:
You can ignore the warning: just like running regular dnf, microdnf is configured to work with Red Hat subscriptions. If you have entitlements on your host, they will be automatically mounted into the container, giving you access to subscription-only resources.

If you don't have entitlements, you'll see the warning, but you can ignore it.


Issue/1123: updated steps to get started

updated steps to get started to include running scripts/test. and scripts.done.sh

Codecov Report

Merging #1128 into develop will increase coverage by 0.04%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop    #1128      +/-   ##
===========================================
+ Coverage    95.77%   95.81%   +0.04%
===========================================
  Files           49       49
  Lines         3500     3515      +15
===========================================
+ Hits          3352     3368      +16
+ Misses         148      147       -1

Impacted Files
Coverage Δ

tests/test_wrap_modes.py
100% <ø> (ø)
:arrow_up:

tests/test_comments.py
100% <ø> (ø)
:arrow_up:

tests/test_main.py
100% <ø> (ø)
:arrow_up:

tests/test_output.py
100% <ø> (ø)
:arrow_up:

tests/test_setuptools_command.py
85.71% <ø> (ø)
:arrow_up:

tests/test_io.py
100% <ø> (ø)
:arrow_up:

tests/test_parse.py
100% <ø> (ø)
:arrow_up:

tests/test_format.py
100% <100%> (ø)
:arrow_up:

isort/pylama_isort.py
100% <0%> (ø)
:arrow_up:

isort/io.py
100% <0%> (ø)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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

This is awesome, thank you!


Update support files NuGet package to support .NETStandard 2.0

Sorry if this is not the correct place for this request.
To support .NETStandard 2.0 for TraceEvent, we need the .NETStandard 2.0 version of the support files here:
https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.TraceEvent.SupportFiles/
Thanks!

We have more discussion on #611 for the same request. I am close this one as a duplicate.


Found a math error Test-DbaIdentityUsage with negative bigints

Bug Report
I was running this against a table that had been seeded as the max bigint negative value.  The current math tries to subtract negative which ends up adding the max bigint value to itself and cannot fit in bigint.
General Troubleshooting steps

[X ] Verified running latest release of dbatools?
[X ] Verified errors are not related to permissions?
[X ] Can duplicate in new/fresh PowerShell.exe session?

Version Information

Operating System (Name|Version): Win10
PowerShell Version: 5.1
SQL Server (Edition|Version): 2012 Ent

Steps to Reproduce
Run against a table that has bigint and seed value is max - value and then add 2 tables

[ ] Attach any screenshots (if possible/allowed)
[ ] Attach logs generated by dbatools (Get-DbatoolsLog)
[ ] Attach output from PowerShell console (if possible/allowed)

I don't believe this is an issue anymore. If it is, please feel free to reopen.


[REQ] Dynamic Docker image location

Is your request related to a workflow problem?
When GH action tries to get the docker image 'ast-cli' our internal company network blocks it which i am assuming could be the case with a lot of enterprises due to security protocols. Only approved images are available to consume and are stored in an internal company repo
Propose a solution
Add another argument in GH action 'docker-image-path' which would give the user the freedom to use internally stored image and run the GH action. Make use of the argument in the dockerfile.
Additional comments
Add any other context, alternative solutions, current workarounds or screenshots about the request here.

Hi @techdoodle ,
This was added to the GH action roadmap.


Create a Nav component

This is the navbar thing in the Figma document.
For now:

Add the "Home" "About" "Sponsors" links from Giga bowser (they all point to /#about etc)
Up for discussion!
Profile Dropdown: Add a right-justified thing that shows the logged in user email (and allow them to log out) (THIS IS ONLY UI PART)

If #6 is done bonus points for wiring it up using the hook

For the links on the nav: It should be Home, Events, and Apply.


What is technical debt? (Warning: Meta Question)

Actually the question is not really, what technical debt is ;-)
I reference the concept in Introduce Boy Scout Rule, Gernot references it in the introduction and long term goal.
How do we want to handle things like this?
Technical debt is a well known concept to some and has been wildly discussed - on the other hand it is also subject to a huge amount of semantic diffusion so it might be appropriate to have a section on the concept itself.
So here are the resulting questions:
a) (concrete) Do we want to have our own description of the concept technical debt?
b) (meta) If we would like to have such a description - where would we put it (and others like it)
c) (concrete) IF a.false() { which article(s) to link to? And where to put the links? }
Suggestions for c)

http://www.infoq.com/news/2008/08/tech-debt-wkshp
Ward Cunningham's video
The c2 explanation
Martin Fowler's interpretation
All of the above ;-)

http://www.betterprojects.net/2015/01/technical-debt-systems-perspective.html
nice and current writeup of some interesting aspects

include reference and parts of the argumentation of
http://reinertsenassociates.com/technical-debt-adding-math-metaphor/

Great post on technical debt and the problems we might have with this metaphor


Make Schemas final in IndicesService

Follow up to https://github.com/crate/crate/pull/15988, which removed
the setter but didn't update the comment on the field.
Also removes the unused client

let's port to 5.7, same as https://github.com/crate/crate/pull/15988?

let's port to 5.7, same as #15988?

Maybe we need to revert this backport ^^, based on what we decided to do on: https://github.com/crate/crate/pull/16004, please see discussion.


Half Auto

The motivation for this PR is that it allows one to derive an ADT but without it escaping into other people's types. Combined with the @deriving annotation it means we can write this
@deriving(Show, Equal, Arbitrary)
sealed abstract class JsValue
final case object JsNull                                    extends JsValue
final case class JsObject(fields: IList[(String, JsValue)]) extends JsValue
final case class JsArray(elements: IList[JsValue])          extends JsValue
final case class JsBoolean(value: Boolean)                  extends JsValue
final case class JsString(value: String)                    extends JsValue
final case class JsDouble(value: Double)                    extends JsValue
final case class JsInteger(value: Long)                     extends JsValue

instead of having to derive for all the products individually (and making their instances visible!)
@deriving(Show, Arbitrary)
final case object JsNull extends JsValue
@deriving(Show, Arbitrary)
final case class JsObject(fields: IList[(String, JsValue)]) extends JsValue
@deriving(Show, Arbitrary)
final case class JsArray(elements: IList[JsValue]) extends JsValue
@deriving(Show, Arbitrary)
final case class JsBoolean(value: Boolean) extends JsValue
@deriving(Show, Arbitrary)
final case class JsString(value: String) extends JsValue
@deriving(Show, Arbitrary)
final case class JsDouble(value: Double) extends JsValue
@deriving(Show, Arbitrary)
final case class JsInteger(value: Long) extends JsValue

@joroKr21 something we could use to define the semantics would be the name of the gen method. implicit could imply full auto, then if it is called semiauto it would never recurse, otherwise do this "half auto":
- `implicit def gen` - full auto
- `def gen` - half auto
- `def semiauto` - semi auto only, require each product to be derived separately

I'd prefer not to add significance to the name of the method. I'm not sure what would (or should) happen under a renaming import. And it would be surprising if the behaviour changed when a name changed. There is enough magic going on with "finding" the methods on the derivation object, anyway. ;)

@propensive updated


Release 0.21.0

Preparing for release 0.21.0

relates to https://github.com/runatlantis/atlantis/pull/2734


trivial-builders.nix functions should take a ... argument and pass it through to runCommand

This probably shouldn't be hard to implement.

which functions in particular are you thinking of as a lot of these look curried (and therefore could not have a ... argument?


Invalid references in Pulumi package schema

@davidspielmann and I recently started looking deeper into Pulumi package schemas and bumped into some issues with named types/references in the schema of the aws classic provider. Talking about it at PulumiUP, @mnlumi encouraged us to share our insight. Perhaps it can help to get some of the references fixed with the upcoming 6.0 release :)
Background: Pulumi package schemas include "Named Types", which are references (a URI string) to a type specification. Our understanding of how these URIs are resolved from the $ref field is https://github.com/pulumi/pulumi/blob/master/pkg/codegen/schema/schema.go#L1409-L1416
Valid references are the built-in types pulumi.json#/Archive, pulumi.json#/Asset, pulumi.json#/Any, and pulumi.json#/Json. All other references have the format [origin]#/{resources,types}/[urn] where [origin] is the file path or URL of a schema file (empty for in-document references) and [urn] the identifier of the respective type definition under "resources" or "types" in that schema.
Expectation: All references in a package schema can be resolved. However, 168 references (25 URIs) in the schema of<EMAIL_ADDRESS>cannot be resolved as defined above. These are the non-resolvable URIs we found; some of them are also noted in other GH issues (referenced).
These 77 references (15 URIs) cannot be resolved but are valid resources, i.e., they could be resolved when prefixing with #/resources/:

aws:apigateway/deployment:Deployment (2 occurrences)
aws:apigateway/restApi:RestApi (24 occurrences)
aws:cloudwatch/logGroup:LogGroup (2 occurrences)
aws:ec2/launchConfiguration:LaunchConfiguration (2 occurrences)
aws:ec2/placementGroup:PlacementGroup (2 occurrences)
aws:elasticbeanstalk/application:Application (4 occurrences)
aws:elasticbeanstalk/applicationVersion:ApplicationVersion (3 occurrences) https://github.com/pulumi/pulumi-aws/issues/2358
aws:iam/group:Group (4 occurrences)
aws:iam/instanceProfile:InstanceProfile (4 occurrences)
aws:iam/role:Role (8 occurrences) https://github.com/pulumi/pulumi-aws/issues/1820
aws:iam/user:User (4 occurrences)
aws:iot/policy:Policy (2 occurrences)
aws:lambda/function:Function (2 occurrences)
aws:s3/bucket:Bucket (6 occurrences)
aws:sns/topic:Topic (8 occurrences)

These 21 references (5 URIs) cannot be resolved but are valid types if treated case-insensitive, i.e., they could be resolved when ignoring the case and prefixing with #/types/:

aws:alb/ipAddressType:IpAddressType (6 occurrences) https://github.com/pulumi/pulumi-aws/issues/2362
aws:alb/loadBalancerType:LoadBalancerType (6 occurrences) https://github.com/pulumi/pulumi-aws/issues/2362
aws:autoscaling/notificationType:NotificationType (3 occurrences)
aws:index/region:Region (3 occurrences) https://github.com/pulumi/pulumi-aws/issues/2463
aws:rds/engineType:EngineType (3 occurrences)

These 70 references (5 URIs) cannot be resolved and we did not find a way to fix it:

aws:autoscaling/metrics:Metric (3 occurrences)
aws:ecr/lifecyclePolicyDocument:LifecyclePolicyDocument (2 occurrences)
aws:iam/documents:PolicyDocument (22 occurrences)
aws:index/aRN:ARN (42 occurrences)  https://github.com/pulumi/pulumi-aws/issues/1682
aws:s3/routingRules:RoutingRule (1 occurrences)

This is the Python notebook we used for this analysis. It also applies the analyis to<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>For most of them, all references are fine, with minimal exceptions (which, ideally, also would be fixed).
https://gist.github.com/DSoko2/4630a14c97a9469385dceed0ab07bc1f
We hope this helps to improve this provider's schema, i.e, eliminate workarounds and non-resolvable URIs. If you should have questions or we can help somehow, please let us know.

@DSoko2 Thanks a lot for this comprehensive analysis! It sounds like we should start from the bottom and figure out the entirely missing references.
For my understanding, how blocked are you on this? Are you able to ignore them and proceed with other tasks, or is there anything we can do to unblock you quickly?

For now, we are not blocked because we can hack around it with the knowledge we got through the analysis.
Still, I think fixing these issues is important: The longer these inconsistencies consist, the more workaround people in the ecosystem may implement. It also may question the reliability of the schemas in general given the popularity of this provider.

It sounds like we should start from the bottom and figure out the entirely missing references.

Yes, this would certainly be valuable! However, fixing the other ones (First two lists in the initial post with workarounds) seems to me like it could be done rather soon and would prevent people like us from adding hacky resolution workarounds to their tools. Certainly, fixing them could still impact schema consumer implementations that solely implemented the workaround but I would argue that the default, documented way of resolving URIs should have priority. Eventually, consuming implementations with workarounds that also support the documented URI resolution shouldn't be impacted.

Quick update, I'm checking up on how we are doing here in the 6x series of AWS. I can confirm that the following references still do not resolve to entries under .types.
    schema_test.go:38: Dangling reference: aws:alb/ipAddressType:IpAddressType (isRes=false)
    schema_test.go:38: Dangling reference: aws:alb/loadBalancerType:LoadBalancerType (isRes=false)
    schema_test.go:38: Dangling reference: aws:apigateway/deployment:Deployment (isRes=true)
    schema_test.go:38: Dangling reference: aws:apigateway/restApi:RestApi (isRes=true)
    schema_test.go:38: Dangling reference: aws:autoscaling/metrics:Metric (isRes=false)
    schema_test.go:38: Dangling reference: aws:autoscaling/notificationType:NotificationType (isRes=false)
    schema_test.go:38: Dangling reference: aws:cloudwatch/logGroup:LogGroup (isRes=true)
    schema_test.go:38: Dangling reference: aws:ec2/launchConfiguration:LaunchConfiguration (isRes=true)
    schema_test.go:38: Dangling reference: aws:ec2/placementGroup:PlacementGroup (isRes=true)
    schema_test.go:38: Dangling reference: aws:ecr/lifecyclePolicyDocument:LifecyclePolicyDocument (isRes=false)
    schema_test.go:38: Dangling reference: aws:elasticbeanstalk/application:Application (isRes=true)
    schema_test.go:38: Dangling reference: aws:elasticbeanstalk/applicationVersion:ApplicationVersion (isRes=true)
    schema_test.go:38: Dangling reference: aws:iam/Role:Role (isRes=false)
    schema_test.go:38: Dangling reference: aws:iam/documents:PolicyDocument (isRes=false)
    schema_test.go:38: Dangling reference: aws:iam/group:Group (isRes=true)
    schema_test.go:38: Dangling reference: aws:iam/instanceProfile:InstanceProfile (isRes=true)
    schema_test.go:38: Dangling reference: aws:iam/role:Role (isRes=true)
    schema_test.go:38: Dangling reference: aws:iam/user:User (isRes=true)
    schema_test.go:38: Dangling reference: aws:index/aRN:ARN (isRes=false)
    schema_test.go:38: Dangling reference: aws:index/region:Region (isRes=false)
    schema_test.go:38: Dangling reference: aws:iot/policy:Policy (isRes=true)
    schema_test.go:38: Dangling reference: aws:lambda/function:Function (isRes=true)
    schema_test.go:38: Dangling reference: aws:rds/engineType:EngineType (isRes=false)
    schema_test.go:38: Dangling reference: aws:s3/bucket:Bucket (isRes=true)
    schema_test.go:38: Dangling reference: aws:s3/routingRules:RoutingRule (isRes=false)
    schema_test.go:38: Dangling reference: aws:sns/topic:Topic (isRes=true)

I've taken stock off the non-resource dangling references. All these originate from Node-only type overlays. There are two ways forward with these:

remove Node-only overlays and support the functionality for every language; breaking change waiting for AWS v7
register the overlay tokens in the schema; unfortunately this is blocked on https://github.com/pulumi/pulumi/issues/17274 at the moment

I will follow up on the resource danging references next.

Currently due to limitations in the bridge, resource references are exposed as type references.
For example, looking at "aws:cloudwatch/logSubscriptionFilter:LogSubscriptionFilter":
                "logGroup": {
                    "type": "string",
                    "oneOf": [
                        {
                            "type": "string"
                        },
                        {
                            "type": "string",
                            "$ref": "#/types/aws:cloudwatch/logGroup:LogGroup"
                        }
                    ],
                    "description": "The name of the log group to associate the subscription filter with\n",
                    "willReplaceOnChanges": true
                },

It is possible to change that to use a resource reference which still works:
                "logGroup": {
                    "type": "string",
                    "oneOf": [
                        {
                            "type": "string"
                        },
                        {
                            "type": "string",
                            "$ref": "#/resources/aws:cloudwatch/logGroup:LogGroup"
                        }
                    ],
                    "description": "The name of the log group to associate the subscription filter with\n",
                    "willReplaceOnChanges": true
                },

This change generates no diffs for Node but it does generate slight changes in other languages:
-        public Input<string> LogGroup { get; set; } = null!;
+        public InputUnion<string, Pulumi.Aws.CloudWatch.LogGroup> LogGroup { get; set; } = null!;

-                 log_group: pulumi.Input[str],
+                 log_group: pulumi.Input[Union[str, 'LogGroup']],

Java:
-    private Output<String> logGroup;
+    private Output<Either<String,LogGroup>> logGroup;

-        public Builder logGroup(String logGroup) {
+        public Builder logGroup(Either<String,LogGroup> logGroup) {
             return logGroup(Output.of(logGroup));
         }

+        /**
+         * @param logGroup The name of the log group to associate the subscription filter with
+         *
+         * @return builder
+         *
+         */
+        public Builder logGroup(String logGroup) {
+            return logGroup(Either.ofLeft(logGroup));
+        }
+
+        /**
+         * @param logGroup The name of the log group to associate the subscription filter with
+         *
+         * @return builder
+         *
+         */
+        public Builder logGroup(LogGroup logGroup) {
+            return logGroup(Either.ofRight(logGroup));
+        }
+

I think these changes are not breaking on the input side, but can be technically breaking on the output side (in the Java example above). This is sufficiently well-contained this could be something we can clean up without waiting for a major release.

Since https://github.com/pulumi/pulumi-aws/releases/tag/v6.55.0 the provider includes a feature to serve a schema without any invalid references (see https://github.com/pulumi/pulumi-aws/pull/4587). This is currently under a feature flag. We are unable to make this the official schema yet until the next major release because it involves taking breaking changes in the Node JS SDKs. Please take a look and let us know if this helps your use cases.

@t0yv0 does this work with pulumi package get-schema or could we add support for it?

I was expecting this to work but verifying on latest it seems that it is not working properly. I'll have closer look.
PULUMI_AWS_MINIMAL_SCHEMA=true
anton@anton-mbp-m3> pulumi package get-schema aws  | shasum
41c5c74551c17d67580e8fb1a4033c8c8bd23fcf  -
anton@anton-mbp-m3> PULUMI_AWS_MINIMAL_SCHEMA=false
anton@anton-mbp-m3> pulumi package get-schema aws  | shasum
41c5c74551c17d67580e8fb1a4033c8c8bd23fcf  -

let me know if it would be helpful if I opened a separate issue tracking that feature

That won't be necessary. Looks like I got the tag references wrong, apologies, https://github.com/pulumi/pulumi-aws/pull/4587 did not make it into the 6.55.0 release yet. We will be releasing with the next minor update (building that now https://github.com/pulumi/pulumi-aws/pull/4638) and I will double check that get-schema works.

#4587 got shipped in 6.56.0

We're preparing another release which will also include https://github.com/pulumi/pulumi-aws/pull/4640 , I'll comment here once I've confirmed this is working.

With the v6.56.1 release pulumi package get-schema aws respects PULUMI_AWS_MINIMAL_SCHEMA=true, please have a look and let us know if this is helpful. CC @zbuchheit

Closing per conversation with @zbuchheit - thanks everyone.


Use map_blocks in higher level functions to reduce memory and allow parallel execution

Work toward #25

Codecov Report

Merging #23 (4203ebb) into main (bc2c461) will decrease coverage by 0.16%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
- Coverage   70.35%   70.18%   -0.17%
==========================================
  Files          15       15
  Lines         425      426       +1
  Branches       23       23
==========================================
  Hits          299      299
- Misses        121      122       +1
  Partials        5        5

Impacted Files
Coverage Δ

sarsen/apps.py
13.69% <0.00%> (-0.20%)
:arrow_down:

Continue to review full report at Codecov.

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

Close as RTC is broken and not easy to fix. See #29


Create PaginatingLazyVStack as a generic scrollable list container

📲 What
Add PaginatingLazyVStack to our component library.
🤔 Why
As part of SwiftUI work, I'm working on re-writing the old backer dashboard using SwiftUI. (Even if it never ships, I think the work will be educational.)
The main component of this page is going to be a scrolling list of cards. That seems like fairly generic functionality, so I wrote this paginating/refreshable VStack as a generic implementation of it.
👀 See
Here's what the example view looks like - it supports infinite scroll and pull-to-refresh.

Closing this as a revised version of this PR was merged in #2180.


Generating address from ExtendedPublicKey

Hi,
Is it possible to generate address directly from the ExtendedPublicKey you get from appAda.getExtendedPublicKey()?
I mean, instead of querying Ledger for new address multiple times, can Ledger be queried for the ExtendedPublicKey, and then addresses derived from that without having to query the ledger.
appAda.getExtendedPublicKey().deriveAddress() -> utils.bech32_encodeAddress()
Thanks in advance.

Hi @Zireael, this library is intended just as a thin wrapper over Ledger's calls, never the less, you can take the account public key (1852'/1815'/<account index>' for Shelley or 44'/1815'/` for Byron addresses) and use e.g. cardano-serialization-lib to derive the respective child keys and assemble the addresses without interacting with ledger: https://github.com/Emurgo/cardano-serialization-lib/blob/master/doc/getting-started/generating-keys.md

Thanks, I got the cardano-serialization working and with ledgerjs-cardano-shelley am able to export the public key in two parts:
{
  publicKeyHex: 'e6cb70c56fffffffffffffffffffffffffffffffffffffffffffffffffff',
  chainCodeHex: '1fadcf740ffffffffffffffffffffffffffffffffffffffffffffffffffff'
}

However cardano-serialization expects the public key in the format 'xpub6DLjthA5JrEnopfffffffffffffffffffffffffffffffffff' and I can't figure out how to do the conversion.
From what I gather, public key is 64-byte: the 32-byte ED25519 public key plus the 32-byte chain code of the public key. How do I construct that?
"xpub" + publicKeyHex + chainCodeHex ?
Something like this?
const rootKey = CardanoWASM.Bip32PublicKey.from_bytes(
  Buffer.from(
    "e6ab70c569d8c47bef9b0c01b54c1a0c19dfc6d8fef5957a0a68cb78f8fa64a5" +
      "1faacf74053f64e9109d4b36fa9702e1b0e392a06524e6d0d69f5465dcf58d4f",
    "hex"
  )
);

I checked in runkit and the extended public key as a buffer seems to work fine:
var csl = require("@emurgo/cardano-serialization-lib-nodejs")

const rootKey = csl.Bip32PublicKey.from_bytes(
  Buffer.from(
    "e6ab70c569d8c47bef9b0c01b54c1a0c19dfc6d8fef5957a0a68cb78f8fa64a5" +
      "1faacf74053f64e9109d4b36fa9702e1b0e392a06524e6d0d69f5465dcf58d4f",
    "hex"
  )
); // account (m/1852'/1815'/0') key obtained from ledger (presumably)

const paymentKey = rootKey
    .derive(0) // visible address
    .derive(0)
    .to_raw_key(); // address index 0

const stakeKey = rootKey
    .derive(2) // staking chain
    .derive(0) // fixed value for staking keys for given account
    .to_raw_key();

const addr = csl.BaseAddress.new(
        1, // mainnet chain
        csl.StakeCredential.from_keyhash(paymentKey.hash()),
        csl.StakeCredential.from_keyhash(stakeKey.hash())
      ).to_address();

console.log(addr.to_bytes());
console.log(addr.to_bech32());

You can look up up in Yoroi codebase how child keys are derived and addresses are obtained from the keys https://github.com/Emurgo/yoroi-frontend/blob/2fd4541b5745601dcfa36fde56873d67012dcbfa/app/api/ada/lib/cardanoCrypto/plate.js#L75
And you can use then Ledger's deriveAddress call to sanity-check your results. Disclaimer - I'm not that familiar with cardano-serialization-lib as I use cardano-crypto.js in my projects which is rougher, so there may be errors in the implementation above, however the general idea should be right and you can easily sanity-check your results with Ledger.

Thanks, this seems to work ^^


Update aka links

Update aka links for configure ie mode and edge advisor because the old aka links will be repurposed.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@kelleyvice-msft Please merge this PR. Thanks


Optimize api calls

https://cdn.discordapp.com/attachments/935586414878400512/960756938495389706/unknown.png

Looks like the #255 solves it

Nice, I saw that the api no longers have MAX CALL REACHED problem. But it might be better if we don't query the same token price for each quest having the same token + total for dashboard

But it might be better if we don't query the same token price for each quest having the same token

What you mean? I think already done that. I create new list without the duplicates token prices.

But it might be better if we don't query the same token price for each quest having the same token

What you mean? I think already done that. I create new list without the duplicates token prices.

I was talking about quest list not dashboard


Need a release with support for axios 0.21.1

It was necessary to down-grade axios in my project in order to make use of this module. If axios-auth-refresh can function with 0.21.1 of axios, it would be helpful to have a new release. The 0.20.0 version of axios has a serious vulnerability.

Closing due to existing PR for this (https://github.com/Flyrell/axios-auth-refresh/pull/140).

Closing due to existing PR for this (https://github.com/Flyrell/axios-auth-refresh/pull/140).


[Bug]: Very slow response on embeddings collection in chroma 0.4

What happened?
Hi,
I have a test embeddings collection made from Gutenberg library (180 of text files, made by INSTRUCTOR_Transformer, that produced 5.9GB chroma db).
When I'm running it on Linux with SSD disk , 24GB GPU NVidia V10, with 8 cores CPU. the response is very slow, take more than 30 seconds to respond.
Did kill -s SIGUSR1 on the python process and got :
Thread 0x00007fbd8cbfd700 (most recent call first):
  File "/mnt/miniconda3/envs/python311/lib/python3.11/concurrent/futures/thread.py", line 81 in _worker
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 975 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 995 in _bootstrap

Thread 0x00007fbda03b6700 (most recent call first):
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/chromadb/segment/impl/metadata/sqlite.py", line 163 in _records
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/chromadb/segment/impl/metadata/sqlite.py", line 148 in get_metadata
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/chromadb/api/segment.py", line 446 in _query
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/chromadb/api/models/Collection.py", line 220 in query
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/langchain/vectorstores/chroma.py", line 156 in __query_collection
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/langchain/utils/utils.py", line 30 in wrapper
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/langchain/vectorstores/chroma.py", line 323 in similarity_search_with_score
  File "/mnt/AI/h2ogpt/src/gpt_langchain.py", line 3521 in get_docs_with_score
  File "/mnt/AI/h2ogpt/src/gpt_langchain.py", line 3900 in get_chain
  File "/mnt/AI/h2ogpt/src/gpt_langchain.py", line 3367 in _run_qa_db
  File "/mnt/AI/h2ogpt/src/gen.py", line 2301 in evaluate
  File "/mnt/AI/h2ogpt/src/gradio_runner.py", line 2939 in get_response
  File "/mnt/AI/h2ogpt/src/gradio_runner.py", line 2990 in bot
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/gradio/utils.py", line 695 in gen_wrapper
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/gradio/utils.py", line 326 in run_sync_iterator_async
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 807 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 995 in _bootstrap

Thread 0x00007fbf15bcb700 (most recent call first):
  File "/mnt/miniconda3/envs/python311/lib/python3.11/asyncio/runners.py", line 118 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/asyncio/runners.py", line 190 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/uvicorn/server.py", line 61 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 975 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 995 in _bootstrap

Thread 0x00007fbf151ca700 (most recent call first):
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 324 in wait
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 622 in wait
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/apscheduler/schedulers/blocking.py", line 30 in _main_loop
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 975 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 995 in _bootstrap

Thread 0x00007fbf147c9700 (most recent call first):
  File "/mnt/miniconda3/envs/python311/lib/python3.11/selectors.py", line 415 in select
  File "/mnt/miniconda3/envs/python311/lib/python3.11/multiprocessing/connection.py", line 930 in wait
  File "/mnt/miniconda3/envs/python311/lib/python3.11/concurrent/futures/process.py", line 412 in wait_result_broken_or_wakeup
  File "/mnt/miniconda3/envs/python311/lib/python3.11/concurrent/futures/process.py", line 339 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 995 in _bootstrap

Thread 0x00007fbe111f8700 (most recent call first):
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 324 in wait
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 622 in wait
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/tqdm/_monitor.py", line 60 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 995 in _bootstrap

Thread 0x00007fbe1349c700 (most recent call first):
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 324 in wait
  File "/mnt/miniconda3/envs/python311/lib/python3.11/queue.py", line 180 in get
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/posthog/consumer.py", line 104 in next
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/posthog/consumer.py", line 73 in upload
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/posthog/consumer.py", line 62 in run
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
  File "/mnt/miniconda3/envs/python311/lib/python3.11/threading.py", line 995 in _bootstrap

Current thread 0x00007fbf218e8740 (most recent call first):
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/gradio/blocks.py", line 2202 in block_thread
  File "/mnt/AI/h2ogpt/src/gradio_runner.py", line 4090 in go_gradio
  File "/mnt/AI/h2ogpt/src/gen.py", line 1226 in main
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/fire/core.py", line 691 in _CallAndUpdateTrace
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/fire/core.py", line 475 in _Fire
  File "/mnt/miniconda3/envs/python311/lib/python3.11/site-packages/fire/core.py", line 141 in Fire
  File "/mnt/AI/h2ogpt/src/utils.py", line 59 in H2O_Fire
  File "/mnt/AI/h2ogpt/generate.py", line 12 in entrypoint_main
  File "/mnt/AI/h2ogpt/generate.py", line 16 in <module>

Please advise if that slow response from chroma is expected or something is not working properly.
This also described in that issue (h2ogpt project) : https://github.com/h2oai/h2ogpt/issues/870
I can share the DB with you, as it a quite big need find a place how I can share with you.
Thanks
Versions
Chroma 0.4.10. Amazon Linux 2023, Python 3.11.5
Relevant log output
No response

I see same thing.  duckdb doing a filter for a document was very fast, even a 20GB database would only take 30s first time and <1s each further query.
However, sqlite takes huge amount of time every time.    It makes sqlite way useless unless have trivial number of documents.

While old duckdb chroma is fast for db.get() by massive amount than new chroma...
Even old chroma with duckdb is very slow if any filter is required.  It also leads to excessive memory use when filtering.  Getting 1000 similar documents on a 5GB database with  711730 entries takes more than 64GB memory.
I don't know why filtering is so slow.

Indeed, for duckdb chroma, if I do db.get() on a 5GB database (takes about 3 seconds) and then filter that entire collection using list comprehension (instant for 700k entries), it's vastly faster than chroma's native filtering that takes 30 seconds.
I would think the most efficient way to filter is to filter along the way of doing sim search.  i.e. Do normal sim search, and if document doesn't satisfy filter, reject it.  This would be no slower than sim search without filter IMO, and so whatever chroma is doing must be much worse.

Closing since h2oGPT found work-arounds.

Work around is good, but I think Chroma should solve such issues.

I have the same problem with a db of about 1GB in size. The latency is about 9 seconds.


Feature: User-defined functions

Description
Add support in the compiler for defining functions and using them in your code.
Function features:

Parameters
Local variables
Return values

Input
int MyFunction(int x) {
    return x + 2
}

num = MyFunction(4)

Expected Behavior
procedure ➤MyFunction x 0
    ♥_return_System_Int32 = ♥x + 2
end procedure

call name ➤MyFunction x 4
♥num = ♥_return_System_Int32

Actual Behavior
SYNTAX ERROR

Specifications, at time of writing
(Can be found by running the CLI with argument --version)

RobotPlusPlus.Core v0.7.18310.1069-indev
RobotPlusPlus.CLI v0.4.0

Bug with local variables
As of G1ANT.Robot 4.61.18249.1835 (possibly earlier), local variables are not working correctly.
Example problem
The following results in dialog.ask (link to manual) trying to use global variable askResponse, while dialog (link to manual) is correctly using the local variable, and therefore whatever you write in the dialog.ask the dialog will always display the text "hello".
call name ➤myFunc

procedure ➤myFunc askResponse ‴hello‴
    dialog.ask message ‴foo bar‴ result ♥askResponse
    dialog ♥askResponse
end procedure

Workaround
Workaround this bug by using a temporary variable as result variable, then assign the local variable to the value of the temporary variable.
call name ➤myFunc

procedure ➤myFunc askResponse ‴hello‴
    dialog.ask message ‴foo bar‴ result ♥tmp
    ♥askResponse = ♥tmp
    dialog ♥askResponse
end procedure


File type with AWS Gateway Binary

Hello,
I think that your project jrestless is wonderful and is exactly what I need.
I'm try to use the AWS Gateway Binary but I see that is return a inputstream but I need the file name and the file type.
So I have a question. Can the rest receive a File and not a InputStream ?

Hi @klebermagno ,
No, you cannot receive a "File object". What you can do is the following, assuming you want to upload a file using an HTML formular:
@POST
@Path("/upload")
@Consumes(MediaType.MULTIPART_FORM_DATA)
public void uploadFile(@FormDataParam("file") InputStream uploadedInputStream,
                                    @FormDataParam("file") FormDataBodyPart body) {
  LOG.info("file name: {}", body.getContentDisposition().getFileName());
  LOG.info("file type: {}", body.getMediaType());
  LOG.info("file contents: {}", new String(toByteArray(uploadedInputStream), StandardCharsets.UTF_8));
}

I extended aws-gateway-binary to illustrate this, check the commit for details.
Please note, however, that using binary with API Gateway has some limitations (those are limitations by API Gateway and not JResteless):

You need to register all binary media types, else you'll see base64 encoded content.
There's a limit of 10MB

And in case you are using the serverless framework for deployment: there's no way to set the binary media types, directly => that's a manual step.

closing; assuming fixed