Data Tools

Spinning off #1448 a bit.
It's cool that we can drill .json files in the "Formatted" mode. It would be cool if there were additional tools for accessing, analyzing and editing data not just in JSON but also XML/TSV/CSV.
In addition to the current mode of a tree that can be drilled, here are some other buttons that would be nifty when viewing such a file:

Spreadsheet: View as a spreadsheet, with filters & sorting for each column. Editing would be cool too... this site lists some JS spreadsheet projects https://jspreadsheets.com/
Pivot Table/Charts https://github.com/nicolaskruchten/pivottable

Like I mention in #1448, this seems like an idea userland tooling opportunity. I've been wondering if there could be some kind of "viewer application" system where you get tabs similar to when viewing a .json and each tab is a userland app that gets injected into the page.

The upside to viewer-apps is that it's good for working with data like you suggest, but can also use very high-level semantics. For instance, if you're looking at a .json that contains an event, it could have a calender view.


Very slow download speed

Version
v1.9.9
Details
Download speeds are much slower than before.
Related issue: https://github.com/Tyrrrz/YoutubeExplode/issues/688
Steps to reproduce
Download any video

Having the same issue myself. I'm lucky to get as "high" a speed as 5Mbps... on my 60Mbps connection, and usually it dips down to 2Mbps for most of a video download then 600kbps for the final 3% or so (which multiplies the time taken to download by a significant amount).
Of interest, I tried a website called Cobalt Video Downloader which does much the same thing as this program and it's showing the same results. So this might be something on YouTube's end...?


Multiple BUSCO lineages?

Hi!
I was wondering if it's possible to specify more than one lineage and download path for BUSCO in the .yaml file.
Thanks for the help!

Hi @malvaradol
The functionality supporting pre-downloaded path for BUSCO lineages will be maintained in future releases.
Support for the multiple BUSCO runs is not planned.
Kind regards


Implement driver click method

Original PR: https://github.com/groupon/webdriver-http-sync/pull/44

:sheep: it


ReCaptcha issues

Everytime when it's click on all the images of cars, and I select all that I could, but there are no more to select, and I hit verify, it will always return an error saying Sorry, Please try again every time, when I got clear visuals that there are no more images of cars that are visible to be selected.
Same deal is with needing to click every image that has street signs. These ones completely do not make any sense at all. I select all the visible square that HAVE signs on them, and some images will be positioned in a way where the sign and squares you need to click on are in other square spaces too, even by that little bit  into the square next to it. Other times I'm shown images of signs that are blurred out, it doesn't always make itself clear on what you need to actually click. blurred street signs to me I think you DON'T need to click on.
Street Signs that are stood on poles, don't even count as a sign, since you just need to click on the board of the sign you see. The solver algo for knowing what's a sign and what isn't is broken, because it doesn't know what's on the image, and what squares need to be clicked on.

Street signs are driving me crazy!
I do fine with cars, buses, roads, bridges, but street signs baffle me!  I can't tell what does or does not count as a street sign, and I am familiar with several languages sufficiently to tell commercial signs from traffic-related signs. But I can't find any rhyme or reason to what the system considers a "street sign". Do signs labeling streets count? Exit signs on highways? Pedestrian crossings?
I just can't crack it, so the system decides I'm "sending random signals" and blocks me out. It should be automatic that after a while the system tries some other object, but it won't. Only those blasted street signs!

@fugueink They're pretty annoying too, see you don't know whether if you have to click on the squares that only just have the street signs on them or if it means to the entire thing, pole that it's sitting on, or that tiny edge of a sign that bleeds into the next square.

This isn't directly related to the PHP code which is what this repo focuses on. However, you might want to look at the v3 support in the most recent release. That uses a wholly invisible reCAPTCHA that just returns a confidence score for the request. This might alleviate some of your issues. Example hosted at https://recaptcha-demo.appspot.com/recaptcha-v3-request-scores.php


Service for IoT

https://thingspeak.com is a platform that already connect some IoT devices so it could be nice to create a service that connect to them to have access to all of their IoT devices

We can also have a look on Azure IoT or lora wan or sigfox that are some "platform/networks" for IoT data

Migrated to https://github.com/mesg-foundation/awesome/issues/16


Fix vertical line artifact

https://github.com/fedeoo/flip_card/issues/3

Thanks @alongruss
TBH, I didn't find the difference between 0 and 0.001 on my IOS simulator.


Is there a script to calculate the average acceptance length?

Hi, thanks for you great work! When I used the EAGLE-llama2-chat-7B you provided for testing, the average acceptance length I measured was lower than the value in the paper. The way I obtained it was to get all the accept_lengths and divide them by the total number of inferences, and finally add 1, which is the token of the last sample of the large model.

You may refer to the link below.
https://github.com/SafeAILab/EAGLE/issues/153#issuecomment-2454707075

Hi, thanks for you great work! When I used the EAGLE-llama2-chat-7B you provided for testing, the average acceptance length I measured was lower than the value in the paper. The way I obtained it was to get all the accept_lengths and divide them by the total number of inferences, and finally add 1, which is the token of the last sample of the large model.

@Lyn-Lucy
My approach is the same as yours, and indeed it is on the low side.


push PR to deploy

deploy on python 3.7
see CHANGELOG.md for details

Codecov Report

Merging #656 into deploy will increase coverage by 0.09%.
The diff coverage is 85.27%.

@@            Coverage Diff             @@
##           deploy     #656      +/-   ##
==========================================
+ Coverage   53.19%   53.28%   +0.09%
==========================================
  Files         203      203
  Lines       20333    20411      +78
  Branches     2727     2735       +8
==========================================
+ Hits        10816    10877      +61
- Misses       9022     9034      +12
- Partials      495      500       +5


SMS OTP authentication flow gives a Nullpointer exception

In the SMS OTP flow, it reads a TokenExpiryTime property from the application-authentication.xml. But the property is not specified in the application-authentication.xml hence giving a null pointer exception.

Could not reproduce in the latest 5.10.0 distribution.


Smoke test for Jenkins Chart

This PR adds a very basic smoke test. It hits the UI on the Jenkins master.
cc @lachie83 @foxish

All set @foxish @prydonius. Going to continue to use the beta annotation until 1.7 comes out.

Ok to merge?

@foxish - yep, usually our workflow is a maintainer who didn't mark the PR as LGTM does a quick pass through the comments and merges the PR if everything looks ok.

LGTM


emacs: Make the application bundle name configurable

Motivation for this change
Up until a few months ago, it was possible to install Emacs under multiple application names while using emacsPackagesFor, because the code that's now in wrapper.nix used to be in a derivation where it could be overridden. The new mechanism does not allow overriding, which broke the scheme I use for separate Emacs and ERC as two different applications (and thus separately customizable in various ways).
This apparently happened due to https://github.com/NixOS/nixpkgs/issues/22893.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @ @matthewbauer

Ping @jwiegley

@adisbladis I don't know enough to answer that, actually. Would you be up for modifying this PR?

@jwiegley I rebased this PR and implemented my suggestion in https://github.com/adisbladis/nixpkgs/tree/emacs-app-bundle.
Could you see if this works for you?
It can be used in the following way:
(emacsPackages.override { darwinAppName = "aoeu"; }).emacsWithPackages(epkgs: [ epkgs.webpaste ])
With my change appName is not an attribute of the emacs derivation and hence you don't need to rebuild emacs, even with a custom bundle name.

@adisbladis No, this did not work for me, since I wasn't able to figure out how to adapt my configuration of Emacs to your solution. It claimed that darwinAppName wasn't a valid argument when I attempted to override my overridden emacsWithPackages here:


Comments in strings trip up Carbide parser

This is a regression with the latest Carbide fix.
Consider:
print("--")

In the previous build, the string would be stripped and put back and everything would be okay.
In the new build, the comment is stripped first, leaving an impartial string that then might be stripped incorrectly again.
It might be necessary to rewrite all the string/comment stripping in Carbide, sadly.

Latest update causes comments to not be preserved with Carbide. Eventually they'll be fully stripped, but for now, this fixes this bug.


Spyder 3.0.0dev + qt5.5 crashes on Mac (Segmentation fault)

Description
What steps will reproduce the problem?

Start Spyder (from Terminal cmd in my case)
Use Spyder for some time, from 30min to a few hours.
Spyder crashes (Segmentation fault).

I couldn't find out what exactly triggered the crash, but it happened repeatedly in the past week.
Version and main components

Spyder Version: 3.0.0dev
Python Version: 2.7.11
Qt Versions: 5.5.1, PyQt5 5.5.1 on Darwin

Dependencies
pyflakes >=0.5.0:  1.0.0 (OK)
pep8 >=0.6      :  1.7.0 (OK)
pygments >=1.6  :  2.1 (OK)
qtconsole >=4.0 :  4.1.1 (OK)
nbconvert >=4.0 :  4.1.0 (OK)
pandas >=0.13.1 :  0.17.1 (OK)
numpy >=1.7     :  1.10.4 (OK)
sphinx >=0.6.6  :  1.3.3 (OK)
psutil >=0.3    :  3.4.2 (OK)
rope >=0.9.4    :  0.9.4-1 (OK)
jedi >=0.8.1    :  0.8.1 (OK)
matplotlib >=1.0:  1.5.1 (OK)
sympy >=0.7.3   :  <IP_ADDRESS> (OK)
pylint >=0.25   :  1.5.2 (OK)

Other observations:
As Spyder is started from Terminal, it outputs logs like the following to the terminal:
2016-03-13 16:57:40.937 python[89775:4286586] inOptions: {
    "is.flipped" = 1;
    kCUIOrientationKey = kCUIOrientVertical;
    kCUIPartMaskKey = 768;
    kCUIThumbProportionKey = 0.1180400890868597;
    state = normal;
    value = 0.2398989898989899;
    widget = scrollbar;
}
2016-03-13 16:57:40.937 python[89775:4286586] outHitPart = -1
Segmentation fault: 11

Also, here is the crash report generated by Mac:
https://gist.github.com/ShenggaoZhu/86c3616354e5551d9a1c

@ShenggaoZhu, I almost sure this is a duplicate of issue #3041. It will be fixed by pull request #3049.

I get the same error on mac using Spyder 3.0.0.beta3.
/Users/Me/anaconda2/bin/python.app: line 3: 79864 Segmentation fault: 11  /Users/anders/anaconda2/python.app/Contents/MacOS/python "$@"
It happens when I am temporarily using some other  window (like chrome). Sometimes I also get this error -- it might be related but don't seem to be the thing causing spyder to crash.
QTextCursor::setPosition: Position '13389' out of range
QTextCursor::setPosition: Position '13389' out of range
QTextCursor::setPosition: Position '29147' out of range
QTextCursor::setPosition: Position '29147' out of range
QTextCursor::setPosition: Position '29147' out of range
QTextCursor::setPosition: Position '29147' out of range
I'd love to provide more info on system etc but not sure how to do it? (new to osx...)

Beta3 has some freezing and crashing issues that will be fixed in Beta4.

Hello,
Spyder crashes sometimes. Here is the error.
/Users/me/anaconda/bin/python.app: line 3: 56546 Segmentation fault: 11  /Users/me/anaconda/python.app/Contents/MacOS/python "$@"
I am using
Spyder 3.1.3
Python 2.7.13 64bits, Qt 5.6.2, PyQt5 5.6 on Darwin


Add use super::* to main code generation function

This allows for arbitrary response_derives derive macros to be used.

I'm a bit worried that indiscriminately importing everything could lead to name conflicts, but it's premature to worry and it fixes the issue for you, so let's merge this :)
Thanks for the PR!
closes https://github.com/graphql-rust/graphql-client/issues/348


fix : tv4 as dependency

Description
We cannot use json-schema-form-core as an npm lib, du to webpack config that declares tv4 as externals.
Installation :
yarn add json-schema-form-core

Use :
import { merge } from 'json-schema-form-core';

Result:
ReferenceError: tv4 is not defined
    at Object.eval (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:2623:18)
    at __webpack_require__ (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:29:30)
    at Object.module.exports.ObjectPath.parse.i (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:2452:62)
    at __webpack_require__ (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:29:30)
    at Object.module.exports._typeof (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:491:72)
    at __webpack_require__ (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:29:30)
    at Object.eval (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:2629:18)
    at __webpack_require__ (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:29:30)
    at module.exports.Object.defineProperty.value (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:75:18)
    at Object.eval (webpack:///./~/json-schema-form-core/dist/json-schema-form-core.js?:78:10)

Motivation :

to fix this, it requires extra webpack configuration in the user project to declare it as externals.
this should work out of the box, and not let the user fix that

Fixes Related issues

issues #4
Set tv4 as dependency.

Checklist

[ ] I have read and understand the CONTRIBUTIONS.md file --> where is it ?
[x] I have searched for and linked related issues
[ ] I have created test cases to ensure quick resolution of the PR is easier
[x] I am NOT targeting main branch
[x] I did NOT include the dist folder in my PR

@json-schema-form/angular-schema-form-lead

Thanks @jsomsanith the webpack file change will cause the entire tv4 lib to be imported into the library on build. Which negates the need for the other change, however I prefer the package file change only as I don't want to include tv4 as I hope to make it optional in a future update. If you add it back happy to accept the package change, that was my mistake :)

Hi @Anthropic, I'm not sure to understand everything you said.
Which negates the need for the other change --> what do you call the other change ?
I prefer the package file change only --> what do you call the package file change ? Do you mean to install tv4 and to add it as external in webpack config ?
Do you agree that the current situation is problematic ? (What I wrote in motivation part). If so, let's find a solution, because a lib should not be that hard to use.

Yes but at the moment you require the users to use webpack the same way you are doing it (with extra bundle)
With the following you user will not have to care about what is used to validate the JSON schema.
So with this current change:
I can use json-schema-form-core without care of what is the validation library inside.
So if you do a change one day from tv4 to sth else, this is not a problem for your user.
If you let the current situation, all the users are doing specific webpack config to add tv4.
Then you change from tv4 to sth else, all the other users will have to change their webpack config.
This is a dependency so I should not take care of it in my build.

@jmfrancois is right, this means you force everyone to update their webpack config when you change the dependency. That makes the future upgrades possibly harder or more annoying.
Obviously, for now tv4 is a dependency, without it  this lib doesn't work, it is ok to have it in the bundle.

@jsomsanith yes I agree, tv4 is problematic, I am hoping before I even get to a v1.0.0 release to make it optional, tv4 isn't supported at all any more, it is a real problem as many user issues are raised that are directly caused by it and I can't make changes to. The sooner I can remove it the better, you'll feel the same way very quickly :) I'm just trying to find the best way to do that.
I do take the point that I could include it until that time. However, that means making a breaking change against all the users who include it separately now and then another breaking change when the alternative is ready, I had hoped to only annoy everyone once. How are you including the lib, are you not using webpack?
Anyway what I meant about negating the other change was that if you include tv4 in the build then it should remain as a dev dependency only as it will not need to be included as a lib dependency, so I think you only want the change in the webpack file?

We are not using the lib yet, but we plan too. We encountered the problem at the beginning of a POC, that's why I made the PR.
Ok I did not understand that it was in your immediate goal. But please, keep what we said in mind when you'll make the change. I mean that the users should not have to configure anything in their webpack to make the lib work.
Thank you for your time.

@jsomsanith @jmfrancois I think we can discuss such things further here: https://gitter.im/json-schema-form/core
Be nice to communicate more fluidly about what you feel the API may need or things that could make it more useful before I actually start working on it in more detail. I originally expected it to be a pre-packed lib that can be re-packed by any lib wanting to embed it. But I have also recently been thinking about webpack tree shaking and can see the benefit in making it includable as a module that can be stripped of unused features.
But I am happy to accept this PR if you undo the package.json file change so that TV4 gets included for now if you like?

@jsomsanith I've added the contributing file, thanks for leting me know it was missing.


Refactor: move execution logic out of resttest.py to allow for xUnit Output Callbacks

Per https://github.com/svanoort/pyresttest/issues/163 this is in support of the xUnit changes
We are moving the test/benchmark execution logic into the macros themself:

[x] Move config/response methods and parser methods into parsing.py or a new macros.py class, and tests
[x] Move test execution logic into an execute method within the test, and invoke that for running
[x] Move benchmark analysis methods into benchmark themself
[x] Move benchmark execution logic into a benchmark execution method, and invoke that for running
[x] Define callbacks and refactor the above to execute them  --> hacky option to output JUnit here
[x] Make all of the test/benchmark methods use callbacks instead of printing directly to stdout
[ ] Create a curl handle mock for testing
[ ] Pull ugly bits of the test/benchmark execute flow into common code for macro (split up execute steps).  NEEDS SOME THOUGHT HERE.

Steps are radically different for test vs. benchmark.
Maybe need a skip callback for cases where nothing to test?
Setup/test/teardown?  Context-before, template?

[ ] Move run_testset pre/post macro logic into appropriate macro
[ ]  Somehow pull out the run_testset overall reporting... pass/fail/skip needs to be tracked in an object (this will map to a unittest TestSuite or something like that in JUnit)
[ ] Move testset execution logic into testset object (macros)
[ ] Optional: Class based registry for macros, where it does not just register parse functions (prototype for v2?) - this allows for API-level use (beta for use in the other extension points, where they look to see if it's a parse function or a class input to figure out how to use them)

Macro Execution Signature:
execute_macro(self, context=None, test_config=None, cmdline_args=None, callbacks=DefaultLogging, *args, *kwargs)

Lets you later first look for variables in self, then testConfig, then cmdlineArgs (which are a dictionary).

@spradeepv - this is the precursor to  #43 (xUnit output), which you were eagerly anticipating I believe.  It's in scope for the next release assuming I can arrive at a reasonable implementation without completely hacking up the core code (and perhaps get some volunteers to play with it).
Once it's complete, generating the xUnit output should be fairly straightforward (fingers crossed). We just register a separate set of optional callbacks and use them instead (or in addition to) the normal logging. It also lays the groundwork for parallel test/testset execution, hopefully.
CC @jeanCarloMachado and @nirsegev and @parametrization and @nitrocode - I know you all are waiting for this too and might be interested in playing with alpha versions of JUnit output once available.
Worth mentioning that this represents a huge under-the-hood change to the core logic in PyRestTest (outwardly it will look similar, inwardly it will be much more straightforward and easy to add custom handling).


Have a smaller Postgres instance

We don't need such a big database in Azure. A smaller one will do (and is way cheaper)

You should update the doc as well as the script :)

@edeandrea done ;o)


Add inChannel() Method to Message Object

Currently, it has an ephemeral() method, but not one to explicitly make a message in-channel.

Done. See PR for v0.1.2


fix image path for quick-start

Change from path docs to documentation to be able to find the promote-immutable-Terraform-code-across-envs.png image asset

Thanks for reviewing! Merging now :)


Fix post component merge errors and bugs

Summary
This PR fixes some UI bugs and e2e test failures that got introduced after merging the post component refactor.
Ticket Link
https://mattermost.atlassian.net/browse/MM-50169
https://mattermost.atlassian.net/browse/MM-50196
https://mattermost.atlassian.net/browse/MM-50205
Release Note
Fix post component related errors

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/e2e-test

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

/e2e-test

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

Thanks @nevyangelova
Are you including Forward Message ticket in this PR?
E2E report  looks good
The only difference I am seeing are 3 Messaging tests that are not failing on master
MM-T90, MM-T93 and MM-T113

@jgilliam17 the Forward messages e2e test is a bit more complicated, in part its including issues with the new menus as well, so it will take a big longer to debug. However the menu isn't obstructed in the UI its just that cypress cant bypass some selectors.
I tried multiple ways but I can't repro the new messaging tests locally :(

Thanks @nevyangelova for looking into - this looks good to merge then.


[TEST] fix: update thumbnails

Closes #736
This PR updates a total of 21 thumbnails for the following repos:

Angular: https://github.com/IBM/carbon-components-angular/pull/2110/

Svelte: https://github.com/carbon-design-system/carbon-components-svelte/pull/1307

Carbon React: https://github.com/carbon-design-system/carbon/pull/11429

Carbon for IBM.com: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/8867

TESTING:

I'm not sure how to reproduce this 👀 for testing

Make sure all images look good

Is the name change for unstable-text to text-unstable.svg intentional?

The way we're currently reading thumbnail images (locally), we're looking up the file by the asset slug:

so I think we are constrained to save the images as the asset-id for now. (this will no longer be a problem when we implement #297)

@alisonjoseph @francinelucca should be fixed!!

Looks good!

adding the do not merge label until we change code so that it's ready for prod


Update ABA_KW-OCF_ALCH_KID.ini

Added Requiem patches 'renaming' for Diverse foods Base Object swapper & Actual Sweetroll Variants

PR manually merged into GroundAura:dev in commit c9d2499 with additional fixes and changes.
Thanks for the additions! In the future please PR into GroundAura:dev as that's the branch I am using for in-progress/unreleased changes.


Update rpp-charter.md (EPP functional equivalence & analysis) #17, #18, #20, #27, #32

Adressing issue #17, #20 with text disucussed in #27
Adressing issue #32
A proposal is a bit different to #30

Added text f54eeaa in to address #18 as well


iOS Crash after plugin update to v0.8

I have used the plugin for the last 10 months with no issues up to v0.7.2. After update to v0.8.0, clicking my print button crashes my App. In Xcode, get this error:
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)

I ran into the same issue attempting to pass content to print using "document.getElementById('printContent')". Passing the content as "document.getElementById('printContent').innerHTML" worked though—albiet with no CSS included without directly adding it to the HTML using style tags.

I had the same problem, rolling back to 0.7.2 fixed the issue:
cordova plugin rm cordova-plugin-printer --force
cordova plugin add<EMAIL_ADDRESS>

I also had the same problem. 0.72 works well in my setting.


Update online codecov requirement to 98%

What and Why
Local codecov is 100%, but because of JuMP if-statements we have to jerry-rig the online coverage to reach 100%.
This is silly - let's remove the jerry-rigging and set the acceptable threshold to 98% (taking after JuMP).
Coverage tests will still break if new code in a PR has lower coverage than main.
Possible Drawbacks
Slippery slope!
Related Issues
No response

@abelsiqueira <3

This is relevant post

We discussed in person the valid coverage ranges.


Don't parse html with xml parser

This replaces the "encode & symbols" hack from my previous PR, and instead of parsing html with an xml parser, we get the necessary data straight from pysaml2.

Updated to include the code from https://github.com/knaperek/djangosaml2/pull/51, don't create two requests when using a custom template for http-post binding, and pass logger variables as arguments.


Unable to run example from README on docker swarm - Dashboard website is not launched

I'm unable to run the example from README on docker swarm.
After following the instructions, the docker stack service is brought up, and all the services are running.
However, the dashboard container does not start the website from which we can start the experiment.
The dashboard image built from calling ./KollapsAppBuilder creates an image that only runs a while true loop.
https://github.com/miguelammatos/Kollaps/blob/bc744a6c7fe746d415128af09282eb83c9683454/examples/KollapsAppBuilder#L68
https://github.com/miguelammatos/Kollaps/blob/bc744a6c7fe746d415128af09282eb83c9683454/examples/utils/dashboard/Dockerfile#L1-L24
https://github.com/miguelammatos/Kollaps/blob/bc744a6c7fe746d415128af09282eb83c9683454/examples/utils/dashboard/dashboard.sh#L1-L8
Given this current code, the dashboard does nothing, so the website is not available, and the experiments cannot be started.
There is another dashboard in dockerfiles/Dashboard, but this one seems to target the baremetal deployment with Kubernetes.
https://github.com/miguelammatos/Kollaps/blob/bc744a6c7fe746d415128af09282eb83c9683454/dockerfiles/Dashboard#L19-L23
Is there any quick fix for this?

Hi @Nandinski,
The dashboard code is correct, the functional part of the website is later injected into the container.
Can you show the output of docker logs god_***(id of god container)?

So that it runs on the host namespace and shares the filesystem with the other emulation cores to allow for metadata to be shared.
You are completely correct I will add it to the tutorial, thanks for pointing it out!
The link state tab (I think you are referring to this) is a prototype to see if the accuracy of the emulation is correct. It should not be displayed yet since it is not finished, the value is the percentage deviation of the total bandwidth available on the link from the actual bandwidth on the link (It does not account for sharing, thus it is not really useful yet).
Yes those errors can be ignored.

Got it. Thank you very much for the answers!


New Year to date progression gives wrong value for hours

My running in 2014 suddenly shows a time increase over 1000 hours on one day:

The activity in question: https://www.strava.com/activities/127518511/overview
Issue still present after full resync

@gethin88 Could you upload here your history as zip ?
Stravistix UI > Clock icon > backup history
Ty

Your activity shows an elapsed time of 1168:59:25

Indeed, overlooked that, was looking for it, but didn't find it before.
Checked on garmin connect, seems to be the issue there as well, is it possible to edit this in strava?

Strange behavior. Maybe in cropping both start and end of the activity (ten seconds each)?
If not, in exporting gpx, fixing manually the problem in the xml file, then importing it in Strava (more complex).

Issue was in the beginning, cropped the activity and it's fixed now.
Changing time zones caused the error. Started the activity before the watch found gps signal, therefor still using wrong data I assume untill it corrected itself when the signal was found.
Issue resolved, was on my end, apologies!


[BUG] Longhorn Does Not Run on Rancher on Ubuntu 22.04.

Describe the bug
I install Ubuntu 22.04 virtual machine and uninstall Rancher v2.8.3 on it. Then, when I remove longhorn in the local cluster, the pods do not revolt.
To Reproduce

Install your ubuntu 22.04 server.
and I run the following commands respectively.

sudo apt-get update && apt-get upgrade -y; curl -fsSL https://get.docker.com -o get-docker.sh; sudo sh get-docker.sh

sudo apt-get update;sudo apt-get install open-iscsi;sudo systemctl enable --now iscsid;modprobe iscsi_tcp;echo "iscsi_tcp" >> /etc/initramfs-tools/modules;echo iscsi_tcp >/etc/modules-load.d/iscsi-tcp.conf;update-initramfs -u;systemctl restart iscsid;lsmod |grep iscsi

docker run -d --restart=unless-stopped \
  --name=rancher \
  -p 80:80 -p 443:443 \
  --privileged \
  rancher/rancher:v2.8.3

After opening the rancher web interface, I go to the charts section and install longhorn directly without making any settings.
and when I examine the pods, I see the following error in the logs.

longhorn spec: failed to generate spec: path "/var/lib/longhorn/" is mounted on "/" but it is not a shared mount

Expected behavior
Direct neat installation of Longhorn.
Environment
The most current version of longhorn, installed directly from the charts section, using the Ubuntu server installed with the Ubuntu Server 22.04 LTS ISO downloaded from the original site of Ubuntu, and the Rancher v2.8.3 version installed on it.

Running Rancher server inside a standalone Docker container by following these instructions.
Accessing the Rancher server UI.
Attempting to install Longhorn on the local cluster.

If the above is correct, this is not a supported environment in which to attempt a Longhorn install. The local cluster (kubelet and all) for this setup runs inside Docker containers. It is similar to https://kind.sigs.k8s.io/ or https://k3d.io/v5.7.2/. There are other issues and questions discussing potential issues that can arise in those setups.
The immediate issue is that the longhorn-manager pod spec calls for the following bidirectional mount:
        - name: longhorn
          mountPath: /var/lib/longhorn/
          mountPropagation: Bidirectional

But /var/lib/longhorn in your install is just a directory on a file system that only exists inside a Docker container. And that file system, which has private propagation, cannot be remounted shared to the longhorn-pod. It is similar to https://github.com/longhorn/longhorn/issues/2402 and others.
eweber@laptop:~/longhorn-manager> docker ps
CONTAINER ID   IMAGE                    COMMAND           CREATED          STATUS          PORTS                                      NAMES
790bb00a15d7   rancher/rancher:latest   "entrypoint.sh"   10 minutes ago   Up 10 minutes   <IP_ADDRESS>:80->80/tcp, <IP_ADDRESS>:443->443/tcp   amazing_swanson

eweber@laptop:~/longhorn-manager> docker exec -it 790bb00a15d7 bash

790bb00a15d7:/var/lib/rancher # findmnt -o TARGET,PROPAGATION /
TARGET PROPAGATION
/      private,slave

CreateContainerError (failed to generate container "d5a0abe75ba708f6de740a987da4fac922a4309779860200833f19914c2e0933" spec: failed to generate spec: path "/var/lib/longhorn/" is mounted on "/" but it is not a shared mount)

It may be possible to overcome this issue by creating a bidirectional bind mount for /var/lib/longhorn when starting the Rancher container, but there is a good chance you will run into iSCSI issues down the line. See this discussion for some idea of what might be next.
The normal way to use Rancher and Longhorn together is like this:

Install Rancher server somewhere (the single node Docker installation is fine for non-production use).
Use Rancher server UI to provision a downstream cluster on VMs or bare metal.
Use the Rancher server UI to install Longhorn on the downstream cluster. (The downstream cluster is running kubelets in VMs / on bare metal nodes and interfacing with a container runtime in the expected way.


Questions about voxels?

How do I convert point clouds into voxel features?  Where is the Voxel Feature Encoder involved in the code?

Here:
https://github.com/Haiyang-W/DSVT/blob/8cfc2a6f23eed0b10aabcdc4768c60b184357061/pcdet/datasets/processor/data_processor.py#L120

Here:
https://github.com/Haiyang-W/DSVT/blob/8cfc2a6f23eed0b10aabcdc4768c60b184357061/pcdet/datasets/processor/data_processor.py#L120

Thank you for your reply!


Manually Resolved IHubContext is not functioning correctly.

i have scenario where i need to access Hub clients from a static class so i tried resolving an instance of HubContext this way:
`public class Startup
 {
    public static ServiceProvider Provider { get; private set; }

    public void ConfigureServices(IServiceCollection services)
    {
        // other stuff
        services.AddSignalR();

        Provider = services.BuildServiceProvider();
    }
}`

and in the static class:
 var chatHub = Startup.Provider.GetService<IHubContext<Chat>>(); chatHub.Clients.All.InvokeAsync("Send", "Hellow folks").Wait();
chatHub instance is correctly instantiated but calling InvokeAsync dose not really do anything with the clients. (note that asking to inject  to IHubContext to controller or similar objects works just fine).
asp.net Core 2.0
sdk version: 2.0
signalr version: 1.0.0-alpha1-final
Thanks in advance

I have the same problem. and i found the IHubContext _connections count is 0, so when i invoke a client method in server, client will not receive this invoke command.
What is the recommended way to push data to clients?

That code is incorrect. You can't build the service provider yourself if you don't return it to the system. You essentially have 2 service providers, your own world and the world that ASP.NET Core knows about. If you must use a static then I'd recommend storing the ApplicationServices on the IApplicationBuilder.
public class Startup
 {
    public static ServiceProvider Provider { get; private set; }

    public void ConfigureServices(IServiceCollection services)
    {
        // other stuff
        services.AddSignalR();
    }

    public void Configure(IApplicationBuilder app)
    {
          Provider = app.ApplicationServices;
    }
}

Re-evaluate if you truly need to use a static or if you can just inject the IHubContext<THub> into the appropriate class.

@davidfowl Thanks, it`s working now.
i guess it`s the only way to access hub clients from a background service that is not part of asp.net.
(i have a back ground service that generates notifications)

i guess it`s the only way to access hub clients from a background service that is not part of asp.net.
(i have a back ground service that generates notifications)

It really just depends on where things start up. If it's outside of the ASP.NET Core universe then sure, if the background service is part of the DI container and it starts up as part of the ASP.NET Core application then there's probably a better way.


1.3 is currently a breaking change

Description
When using containerd as a module, migrating from 1.2 to 1.3 is a breaking change.
Steps to reproduce the issue:
I highlighted the events in this issue
https://github.com/instrumenta/conftest/issues/8#issuecomment-522693289
Oras depends on containerd 1.2.6
Buildkit depends on containerd 1.3.0
Our application, which uses both, is forced to 1.3.0 which complains about a missing V2 field
unknown field 'V2Only' in struct literal of type "github.com/docker/docker/registry".ServiceOptions

docker/docker/registry as it is now: https://github.com/moby/moby/blob/master/registry/config.go
docker/docker/registry that removed V2 field:
https://github.com/moby/moby/commit/98fc09128b3f8221680bd22c2de5b893bd3d7ef8#diff-e1f2f7594a599fdaea710015a86eb4f9
commit of docker/docker containerd references in vendor folder:
https://github.com/moby/moby/commit/86f080cff0914e9694068ed78d503701667c4c00 (which is not an official docker/docker release)

Is this just a compile time issue because the 1.2.x and 1.3.x API versions are backwards compatible.

Yes, compile time.
When creating a project that uses a package that depends on containerd 1.2, and a package that depends on 1.3, the project (may) fail to compile because docker/docker/registry removed a public field in their ServiceOptions{} struct.

As far as I can tell, github.com/docker/docker makes no compatibility guarantee for their Go APIs — not even the usual Go guarantee of compile-time compatibility (see https://github.com/moby/moby/issues/37281#issuecomment-399102635 and https://github.com/moby/moby/issues/39056#issuecomment-483438659).
From https://github.com/moby/moby/issues/31842, it seems that they intend to semantically-version only the HTTP API.
So in order for containerd to ensure that changes do not break downstream users — that is, to ensure semantic versioning for releases — it seems like containerd would need to drop the dependency on github.com/docker/docker entirely.

(CC @justincormack @cpuguy83 for Docker context.)

Can you post the full build log for this? what code in containerd is return the error for the docker import?  I cannot find anything greping though

The simplest example I can give would be:

Fork conftest https://github.com/instrumenta/conftest
1.1 (cd into cmd/ and run go build as a sanity check)

Update the containerd reference in go.mod to point to v1.3.0-0.20190507210959-7c1e88399ec0

run go build again

jreese@TWWL-JREESE MINGW64 /c/git/github/conftest/cmd (master)
$ go build
# github.com/deislabs/oras/pkg/oras
C:\Users\jreese\go\pkg\mod\github.com\deislabs\oras@v0.6.0\pkg\oras\pull_opts.go:26:3: cannot use images.Dispatch (type func(context.Context, images.Handler, *semaphore.Weighted, ...v1.Descriptor)
error) as type func(context.Context, images.Handler, ...v1.Descriptor) error in field value
C:\Users\jreese\go\pkg\mod\github.com\deislabs\oras@v0.6.0\pkg\oras\push.go:46:69: cannot use opt.baseHandlers (type []images.Handler) as type func(images.Handler) images.Handler in argument to remotes.PushContent
C:\Users\jreese\go\pkg\mod\github.com\deislabs\oras@v0.6.0\pkg\oras\push.go:46:69: invalid use of ... in call to remotes.PushContent

Alternatively you could add a reference to github.com/asottile/dockerfile in the project, even in main.go and immediately run a build
Which then gives the specific missing V2Only error
# github.com/deislabs/oras/pkg/auth/docker
C:\Users\jreese\go\pkg\mod\github.com\deislabs\oras@v0.6.0\pkg\auth\docker\login.go:26:3: unknown field 'V2Only' in struct literal of type "github.com/docker/docker/registry".ServiceOptions

it seems like containerd would need to drop the dependency on github.com/docker/docker entirely

This is the long term plan, right now it is the CRI plugin which utilizes it. We have already banned it from containerd core.
Related to the Go client support, we should track that in a separate issue. Today the Go client API is not stable, therefore breaking changes are allowed, although we try to avoid them when not necessary. We can consider to stabilize it in an upcoming release but we first want to move to go modules and remove unstable upstream dependencies. This will not happen for the 1.3 release and we encourage importers to keep their dependency up-to-date rather than pinning to older unstable client releases.
I am closing this as a won't fix for 1.3, but please feel free to continue the conversation here or on Slack.


Scale and crop?

Should those be used together? I was thinking since they may have the same effect.

Affine scaling and cropping (with resize afterwards) should be mostly the same. The affine scaling happens by default around the image center, though that can be changed using translation.


Pnpm

Right now - the pnpm arrangement doesn’t yet fulfill the issue https://github.com/TBD54566975/developer.tbd.website/issues/532 to declare and respect one dependency (for instance Web5) across all examples and the site. For instance, “examples/todo-app/package.json” has “"@tbd54566975/web5": “0.7.8”; expecting this to be declared once uniformly at the top level so all examples and the site itself use the same version. That gives us one place to update as defined by https://github.com/TBD54566975/developer.tbd.website/issues/538.

We have a dependency at the root package.json now that says to use web5 0.7.10, however, that doesn't actually install the required package inside each project. It allows us to locally test versions.
I made a specific command for updating all dependencies in examples to take care of this:
`pnpm update:web5" will recusrively add the latest version of web5 to every example.
Here is what the package.json looks like now.
I think this is the best we can do for now, I'm sure we can get some custom hooks going to automate this just a bit further.

Got off a pair exercise w/ @dayhaysoos - here's where we landed:

He's put the web5 dependency into the top level pnpm
That makes for one declared dependency for web5, used by the site and all examples/demos/starter templates/etc
Additional dependencies that are specific to the site or examples/demos/starters/etc can still go in the package.json of that submodule

So with that arrangement, let's say @bobbilee19 wants to upgrade Web5. She could either:

Update the version number in the top-level package.json once, or
Run a pnpm command at the root level to have pnpm do the above (@dayhaysoos is documenting how in the README)

@bobbilee19 - this one is of particular interest: we advise taking the "completed" index.js in the Quickstart and instead of it being a free-floating file the user downloads, make it into a simple "quickstart-completed" application mirroring how we do it in the completed TODO app. That way:

A user has the fully runnable application available to them, which includes the package.json needed to run it
We have a uniform approach to completed applications and we can upgrade and test them all in the same way; no more standalone floating Node scripts to independently patch and manually check when we upgrade

@dayhaysoos is working through the bullets in my PR review above, looks like making great progress.
And I'm super excited because in addition to easing the maintenance burden, we're giving some really good unifying structure to the examples/completed apps/playgrounds etc which is going to make it really clear to the user how to get them, how to run them, and for us to make testsuites for them.

@dayhaysoos oh 100%, consistency, consistency and the two points for why we should do that, 100% agree...for the index.js question above.

Figure a way to inline the declared dependency into the dev site QuickStart instructions:

Due to the nature of docusaurus and MDX, I'm using an environment variable to declare the version for Web5 but also adding that value to Docusaurus's Context. We can't simply inject the version where we want because that's not how MDX works, we have to create React components to do it.
I also think we should get away from declaring which version gets installed for the npm install snippets. Probably something we should ask OSE about because this depends on how stable the next releases will be until we get to 1.0.0.
If we should keep the versions inlined on the npm lines, then I'll have to make a component explicitly for that use case in the meantime that takes advantage of the Docusaurus Context.

pnpm-lock.yaml to .gitignore

I think we actually need the lock file. This guarantees that everyone will be running the same versions of things when they pull. Tbh I can't remember the details but I was taught it's a bad practice to hide lock files.

pnpm-lock.yaml to .gitignore

I think we actually need the lock file. This guarantees that everyone will be running the same versions of things when they pull. Tbh I can't remember the details but I was taught it's a bad practice to hide lock files.

You're totally right, and I suppose just needs to be updated/synced alongside package.json so when users run the build they don't see diffs.

[ ] Reorganize examples folder as @angiejones suggests: https://discord.com/channels/937858703112155166/1111754777307660388/1123013349198794762
[ ] Update README so it's self-serve, reflecting new script changes
[ ] Existing docs reference incubating-web5-labs and web5-tutorials, which are now moved to this monorepo

Web5-quickstart-widgets index.html is still using a direct dependency declaration for Web5, outside the new pnpm system: “import { Web5 } from 'https://cdn.jsdelivr.net/npm/@tbd54566975/web5@0.7.0/dist/browser.mjs’;”

Is this the only index.html example we ever plan on doing? If so, we should leave it as is. Perhaps this will be the only thing we have to take care of manually. Getting this to work within the pnpm system is becoming a pain due to CORS related issues. Maybe I'm going about it wrong but I'd like to come back to this after other things are taken care of

The "borked" values are actually coming from the swagger.yaml source:
https://raw.githubusercontent.com/TBD54566975/ssi-service/main/doc/swagger.yaml
Not sure who to contact for this one, any ideas @ALRubinger ?

Web5-quickstart-widgets index.html is still using a direct dependency declaration for Web5, outside the new pnpm system: “import { Web5 } from 'https://cdn.jsdelivr.net/npm/@tbd54566975/web5@0.7.0/dist/browser.mjs’;”

Is this the only index.html example we ever plan on doing? If so, we should leave it as is. Perhaps this will be the only thing we have to take care of manually. Getting this to work within the pnpm system is becoming a pain due to CORS related issues. Maybe I'm going about it wrong but I'd like to come back to this after other things are taken care of

Based on the other examples I've seen throughout the DWN/Web5 repos, nope. I bet that these declarations are a common pattern for example apps because they're a class of web applicatioj that's not Node-based; they're all in-browser and really show the ease of use of Web5.

The "borked" values are actually coming from the swagger.yaml source:
https://raw.githubusercontent.com/TBD54566975/ssi-service/main/doc/swagger.yaml
Not sure who to contact for this one, any ideas @ALRubinger ?

@decentralgabe will know!
And I think we should get this external dependency out of the build, or at least lock it to a version. Changes to main at different points in time makes for non-reproducible builds of the dev site. This means that if you run the dev site build on a commit hash X, depending upon when you do that, you can get different results. A build should be "reproducible" by nature of a commit hash build always making the same result.
As a separate and related issue, the external dependency means that if this file is moved/changed, it can block builds of the dev site from completing successfully until corrected. So I recommend bringing these external pieces inside the monorepo.

@dayhaysoos which values are borked from the swagger? cc: @andresuribe87

Based on the other examples I've seen throughout the DWN/Web5 repos, nope. I bet that these declarations are a common pattern for example apps because they're a class of web applicatioj that's not Node-based; they're all in-browser and really show the ease of use of Web5.

Just took a look and I think I know what to do now, going to look at it tomorrow morning.

Two places to come back to when we figure out degit...

Changing where the example / todo-app-starter will go and how we want them to use it (cloning our entire dev docs is a lot for just the starter)... https://github.com/TBD54566975/developer.tbd.website/blob/main/site/docs/web5/build/apps/todo-app-tutorial.mdx#L14
Changing how we'll link the todo-app-completed...https://github.com/TBD54566975/developer.tbd.website/blob/main/site/docs/web5/build/apps/todo-app-tutorial.mdx#L289

@decentralgabe I don't think this is all of them but from what I can tell, the places where you can see "{{.Something}}" like in this screenshot:
https://user-images.githubusercontent.com/199891/248892883-919d9341-5cda-4198-bcc9-b9b55160e5c8.png
I ran a quick search on "{{" and saw these:

host: '{{.Server.APIHost}}'
than {{.Services.CredentialConfig.BatchCreateMaxItems}} items.
{{.Services.DIDConfig.BatchCreateMaxItems}} items.
description: '{{.Desc}}'
version: '{{.SVN}}'

@dayhaysoos the problem is those values are populated with a running SSI Service. Without a running service we won't know what to put there (e.g. what service URL, version, etc).
An option may be to have a piece of middleware that detects the pattern with a regex and removes the properties from the resulting yaml file

@decentralgabe I can look into something like that, I guess I'm curious about why these values didn't show up on docusaurus before. Do you think it'd be helpful to look at previous versions of this file for reference?

@dayhaysoos we made a change to have these values load dynamically. they weren't being set properly before. the service needs to set these dynamically, so I only can suggest a way to workaround and delete the problematic properties

And I think we should get this external dependency out of the build, or at least lock it to a version. Changes to main at different points in time makes for non-reproducible builds of the dev site. This means that if you run the dev site build on a commit hash X, depending upon when you do that, you can get different results. A build should be "reproducible" by nature of a commit hash build always making the same result.

As a separate and related issue, the external dependency means that if this file is moved/changed, it can block builds of the dev site from completing successfully until corrected. So I recommend bringing these external pieces inside the monorepo.
I agree with this, I think that maybe this should be another separate issue.

Okay thank you @decentralgabe, I have to do some research because the way we display this is entirely reliant on an external library. Not sure how much control I have over how things are surfaced but I'm sure I can figure something out

Don't think we'll be able to land this today, or we can land this and push some of the tasks to another "sprint". Here's a list of what's left and what's to be said about it:

On http://localhost:3000/docs/apis/ssi-service, templating looks borked:
External dependency issue, gabe gave some suggestions on how we can go about this. Just need to be researched.

Todo-app-tutorial - needs updating to get the starter app (web5-tutorials) and completed example (incubating-web5-labs) from their new locations (under the monorepo in examples folder)

I'ma be honest I don't even know what this means, gonna get clarity from ALR later lol

Web5-quickstart-widgets index.html is still using a direct dependency declaration for Web5, outside the new pnpm system: “import { Web5 } from 'https://cdn.jsdelivr.net/npm/@tbd54566975/web5@0.7.0/dist/browser.mjs’;”

This might actually be done by EoD today

“Running commands” section in README: what does “target specific packages” mean? Maybe this section could have an example to show what you’d be doing with this command, for instance updating web5?
This is a copy pass, done by EoD today

npm older commands like "install" still runnable directly, but can lead to the wrong build outputs? Can we remove npm from working at all, signifying that pnpm should be the build system of record?

This is possible, but I'm hesitant on it. I'd like for people to use npm if they want for running pnpm scripts detailed in the script tags. Just worth having a small discussion about this

Todo-app-tutorial - needs updating to get the starter app (web5-tutorials) and completed example (incubating-web5-labs) from their new locations (under the monorepo in examples folder)

I'ma be honest I don't even know what this means, gonna get clarity from ALR later lol

This refers to the docs for TODO App; they still instruct the user to attain the starter and completed example from the old locations:

[ ] git clone https://github.com/TBD54566975/web5-tutorials.git in the code block at the top
[ ] https://github.com/TBD54566975/incubating-web5-labs/tree/0.2.0/todo-app is the link in "finished version of the ToDo app here" at the end
[ ] "See it deployed here" at the end points to https://unrivaled-crumble-56ce70.netlify.app/, which is configured on Netlify still using the old location https://github.com/TBD54566975/incubating-web5-labs

@dayhaysoos we made a change to have these values load dynamically. they weren't being set properly before. the service needs to set these dynamically, so I only can suggest a way to workaround and delete the problematic properties

@dayhaysoos, let's spin this off into a new issue. It's not related to the pnpm work here and exists independently. So let's not have it block this PR and address separately.
We need to define a contract by which OSE is providing this source and the site can transpile it into the published version. If OSE folks need to change something about the format they're providing, or move the source file, that's cool; but it should be:

Explicitly coming to the site via a locked version so nothing changes under the hood inbetween site builds (to my point about build reproducibility above)
Adhering to the same contract and verified the new docs version looks right before the PR into the dev site is approved and merged to main

Web5-quickstart-widgets index.html is still using a direct dependency declaration for Web5, outside the new pnpm system: “import { Web5 } from 'https://cdn.jsdelivr.net/npm/@tbd54566975/web5@0.7.0/dist/browser.mjs’;”

This might actually be done by EoD today

@dayhaysoos and I agreed:

[ ] Let's spin this off into a new issue to not block this PR. Updating Web5, until this is done, will have to be done in two locations: the monorepo declaration and for this index.html file of the quickstart-widget. Some pre-build step to inject the version into the widget is something Nick will look at as part of the build. But that won't hold up this PR and we'll document all the places to update Web5 in the README in the meantime.

This is possible, but I'm hesitant on it. I'd like for people to use npm if they want for running pnpm scripts detailed in the script tags. Just worth having a small discussion about this

I've learned more about pnpm over the past few days in my own building with it - and you're right here. Convention is that it's a drop-in replacement and I've seen most projects simply have in documentation to run pnpm and there's no explicit barrier to their using npm. We only need to support the documented build flows.

[ ] Update TODO App docs to show user how to get the starter example from the new location (the code block for git clone etc)
[ ] Update TODO App docs to show user how to get completed example from new location
[ ] Update TODO App Deployment config in Netlify to point to new location in monorepo
[ ] Remove TODO App from web5-tutorials
[ ] Remove TODO App from incubating-web5-labs
[ ] Quickstart index.js should move to monorepo as a -completed appl just like we do for TODO App
[ ] ...And update user instructions to show user how to grab the completed example from new location and run it, just like we do for TODO App
[ ] Quickstart docs update to show user how to build from new -completed

Let's spin this off into a new issue to not block this PR. Updating Web5, until this is done, will have to be done in two locations: the monorepo declaration and for this index.html file of the quickstart-widget. Some pre-build step to inject the version into the widget is something Nick will look at as part of the build. But that won't hold up this PR and we'll document all the places to update Web5 in the README in the meantime.

Don't need to make a new issue for this anymore because I think it's working now. Will have to double check but this seems to be done.

"See it deployed here" at the end points to https://unrivaled-crumble-56ce70.netlify.app/, which is configured on Netlify still using the old location https://github.com/TBD54566975/incubating-web5-labs

Having some trouble getting our netlify set up right to deploy multiple sites. I think for now I'd like to make this an issue and ask for support from Netlify just so we can land this PR today.
Until then, probably won't be a good idea to remove the apps from the other repos. We'll leave it up for people to see in the mean time.


Git for Windows does not seem to come with rsync

In the docs it is suggested to use for example Git for Windows. Tested the current (2.13.0) version, and bash in that does not seem to have rsync that is required for resin sync, and thus sync does not work. These Windows instructions might need update and/or clarification? (used on Windows 10).

In case you want to use the link or copy the instructions, I followed this guide to add rsync to Git for Windows.
Worth mentioning resin sync is not working for me atm but I think it's my fault due to where I placed the shared libraries

The sync command and its rsync dependency were removed in CLI v11, replaced with the "live push" feature which is enabled by default with the balena push <ip-address> command.
Also, earlier this year the installation instructions for Windows were significantly improved:
https://github.com/balena-io/balena-cli/blob/master/INSTALL.md


Where is the online compiler/REPL

I couldn't find it in the website?

For people still finding this on Google, the editor is now found at http://elm-lang.org/try and has been greatly improved.

Online repl is at http://elmrepl.cuberoot.in/


SAG Mill Eating Secondary Output

Forge Version: <IP_ADDRESS>3
EnderIO Version: 1.7.10-<IP_ADDRESS>7
I noticed when I had a SAG mill directly outputting to an alloy furnace that while the alloy furnace would pull the primary output (in this case, the pulverized iron from the iron ore), it would (properly) not pull the others, as it wasn't keeping up.
However, once the pulverized nickel stack filled up, the SAG mill (improperly) kept running, producing more pulverized iron and (I assume) eating the excess nickel being made at that point. I expected the SAG mill to stop until it had space for the secondary outputs. And as the three secondary slots all had something in them (nickel, tin, cobble), it had nowhere else to put it.
tl;dr: SAG mill only checks space for primarily output before performing an operation and loses the when the secondary outputs are full.

Actually the SAG Mill asks the recipe for it's outputs - and a random number is chosen. If the outputs fit the process is started - otherwise it waits 1 second.
I tried to fix that - but it is not as easy as I expected. I might give it another go.

'eating' the secondary output is a consequence of that algorithm.  It will keep trying until the no secondary output option its and run it.  The only way to NOT do that is to block the run when the outputs will not fit before the chance portion is done.  Or declare the current behavior expected.

Perhaps not running unless the maximum output is available?

Yeahh I agree with @magerooster, it should not run if exceeding the storage space available is possible at all, the current algorithm is unfair.

I'll try to chance it as @braddr suggested - if that is doable without rewriting everything.
The other idea I had was to freeze the random number generation - so that it won't re-roll for each check unless the check has passed.

I probably shouldn't try reading code at this hour, but.. I think it might just work to change the 'chance' variable in this line to whatever value means always succeed:
https://github.com/SleepyTrousers/EnderIO/blob/master/src/main/java/crazypants/enderio/machine/AbstractPoweredTaskEntity.java#L276


Fix for growing Offer/Answers

In webrtc's unified-plan semantics, instead of adding tracks to streams, you
operate mostly in transceivers. When hanging up a stream, the transceiver
should be Stopped and the track removed with the RemoveTrackNew() method, which
should be used over the plan-b RemoveTrack() method.
With this change, we no longer need to force a PeerConnection reset, and it should
also improve stream latencies.
Testing locally confirms that after hanging up a stream, the transceivers are
now being stopped, and no longer included in Offer/Answers. Additionally,
previously stopped Transceivers can be used for new streams.
Previously, when switching between RAW and SPE modes, the SDP offer showed the following MIDs
1 5 6 7 (1 is the data channel, 5, 6, 7 are the streams) then 1 5 6 7 11 12 13, even though only 3 streams are playing at once.
Now, the switch goes from
1 5 6 7 to 1 11 12 13

@bshapero89 whats the max number of streams that we have tested this fix with ?

@ragnalla I had already tested it with 3 open streams and opening/closing a modal (to verify that transceivers were getting removed/reused).

Further validation: in chrome://webrtc-internals, these events are now showing up, where previously they were not:
Caused by: setRemoteDescription

getTransceivers()[3]:{
  mid:'23',
  sender:{
    track:null,
    streams:[],
  },
  receiver:{
    track:'VideoTrack-1a3358d9-1b06-43cb-8fa2-c02352550b67',
    streams:[],
  },
  stopped:true,
  direction:'recvonly',
  currentDirection:'stopped',


Test syncing extension's global state

Testing https://github.com/microsoft/vscode/issues/95209

[ ] anyOS @RMacfarlane
[ ] anyOS @sbatten

Complexity: 5
Create Issue

Extensions can now contribute global state keys those can be synchronised using proposed syncedKeys API
https://github.com/microsoft/vscode/blob/9b4f91b31cf2f8a7fafc1bbdcacf98505b84c0eb/src/vs/vscode.proposed.d.ts#L2184-L2194

Write and publish a test extension that saves and syncs some global state using above API.

Make sure you add "enableProposedApi": true flag to extension's package.json.
use --noVerify flag while publishing the extension.

Following sample, shows a welcome notification for the first time and remembers that. From thereafter it mentions that welcome was shown already.
import * as vscode from 'vscode';

const welcomeMessageShownStateKey = 'sandy081.999-test-sync-state.welcomeMessageShwon';
export function activate(context: vscode.ExtensionContext) {
	context.syncedGlobalState.syncedKeys = [welcomeMessageShownStateKey];
	if (context.syncedGlobalState.get(welcomeMessageShownStateKey)) {
		vscode.window.showInformationMessage('Activated: Welcome was shown already');
	} else {
		vscode.window.showInformationMessage('Activated: Welcome to my extension');
		context.syncedGlobalState.update(welcomeMessageShownStateKey, true);
	}
}

export function deactivate() {}

Test that extension state is synced across

Start insiders using the flag --enable-proposed-api <above-extension-id>
Install above extension (if you used above sample, then you shall see welcome notification)
Turn on settings sync
On other machine (or use another user data dir and extensions dir on same machine) start insiders with --enable-proposed-api  <above-extension-id>
Turn on settings sync and make sure above extension is installed and the extension state is synced.
For example, if you used above sample, then you shall see a notification saying welcome was shown already.
You can also check for synced extension state by

Open Synced Data view using command Settings Sync: Show Synced Data
Open the latest synced extensions.json entry and make sure extension state is synced to server.

Test that you can add or remove keys to sync by updating the syncedKeys value and make sure state is synced accordingly.
Test that explicitly setting the syncedKeys to empty array will clear the synced state on server.
Test that only state from latest extension version is synced. It means when remote and local extensions are in different versions

If local version is older than remote version, then state is not synced
If local version is newer than remote version, then remote state is replaced with local.
If local and remote are on same versions, then state is merged and synced.

Validate the documentation and naming terminology of the API

@sandy081 things just don't seem to be working as expected at all. I've created an extension that has commands for pushing new state, clearing state, and checking the sync'd state, but nothing is working as expected.
Here is the extension code with a README explaining usage: https://github.com/sbatten/vscode-sync-test-sample. PTAL and let us know if we are doing something wrong.

@sbatten Can you please check following in both machines?

Open Synced Data view using command Settings Sync: Show Synced Data
Open the latest synced extensions.json entry and make sure extension state is synced to server.

Also open Settings Sync log and check if Sync is happening, especially, check if extensions are being pushed or pulled.

I'm also seeing this problem with my own test extension, and SteVen and I looked at his sample together on a call. We verified that other data was correctly being synced, i.e. settings like the theme were correctly applied between windows. When looking at the synced data, it seemed like the incoming changes from the remote were always being deleted on the local machine

This is happening because the extension is not published. Extension state is not synced when extension is not available in the Marketplace - Please file an issue for it. I verified this by publishing your sample using extension id sandy081.999-test-sync-state and it works as expected.


VG-5233: New cart menu option to Add to Saved Search

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e8cfb14). Click here to learn what that means.
The diff coverage is 66.66%.

@@            Coverage Diff            @@
##             master     #112   +/-   ##
=========================================
  Coverage          ?   79.69%
=========================================
  Files             ?      116
  Lines             ?     7648
  Branches          ?     1148
=========================================
  Hits              ?     6095
  Misses            ?     1553
  Partials          ?        0

Impacted Files
Coverage Δ

app/src/layout/header-controller.js
91% <66.66%> (ø)

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 e8cfb14...77cd41b. Read the comment docs.


img2img producing low quality results on ARM64 Mac

Describe your environment

GPU: mps
VRAM: 8GB
CPU arch: arm
OS: macOS
Python: miniconda
Branch: main
Commit: 751283a2de81bee4bb571fbabe4adb19f1d85b97

Describe the bug
Specifying an init-image on M2 Mac is producing low quality results that do not resemble the prompt or contain artifacts.
To Reproduce

Install stable-diffusion for Mac as per the instructions here: https://github.com/lstein/stable-diffusion/blob/main/README-Mac-MPS.md
Activate the ldm environment and run the following command to launch dream.py:
python3 scripts/dream.py --full_precision
Attempt to use img2img to generate another image based on seed image (modified sample from CompVis repo) and prompt:
"A fantasy landscape, trending on artstation" --init_img ../Downloads/sketch-mountains-input-resized.jpg --strength 0.8 -W256 -H256
Note: Increase the step size to 100 does not improve results.

Expected behavior
A fantasy landscape image that follows the layout of the input image.
Screenshots
See input image below:

And examples of the results:

Is anyone able to assist, perhaps I am doing something wrong. I've tried to specify the plms sampler but it is always falling back to DDIM.
>> sampler 'plms' is not yet supported. Using DDIM sampler
Note that txt2img is working fine on my M2 Mac, even though it falls back to DDIM as well.

I have noticed running the same parameters/input/prompt here than at the original google collab yields way worse results. Is it because of constraints in input size running locally (input image 512x512) versus running on tpus (input image 1024x1024)?

Perhaps it is related to resolution; I kept the image small due to resource constraints and to make the image generate faster - will try a larger image later and see what happens.

I've noticed that increasing the step numbers helps improve sketch->image considerably. Also try changing the sampler.
If we are seeing consistently lower-quality images when performing apples to apples comparisons (same image size, sampler, scale, steps) then this is a bug we need to track down.

Also try changing the sampler.
Which sampler would you think performs the best?

Side note, increasing the steps to 200 indeed makes the image more faithful to the sketch IMHO

Also try changing the sampler. Which sampler would you think performs the best?
For what i see DDIM is the default and some are not supported yet?

 Indeed, only the DDIM sampler is supported for img2img. I think something has indeed changed between this fork and the CompViz original. I also note that you need a large number of steps in order to get decent results from inpainting.
@bakkot, I think this is a place where your expert eye is needed to identify an inadvertent change to the handling of steps and strength.

@bakkot, I think this is a place where your expert eye is needed to identify an inadvertent change to the handling of steps and strength.

I get identical (crappy) output for the given 256x256 input image on the latest commit on main as on 7cb5149a02c0a22b63c44d1220d0c05013aefa30, which is approximately the beginning of the fork. And I'm using an Nvidia card, so it's not the architecture. So I don't think this is a regression. It seems that img2img just doesn't work very well with small images, and never has.

Yup, this is the expected behavior with lower resolutions.

Thanks guys, it does appear related to resolution - I tried again with a 512x512 input and output and got a better result:
"A fantasy landscape, trending on artstation" --init_img ../Downloads/sketch-mountains-512.jpg --strength 0.8 -W512 -H512 -s100


[Feature Request]: Support running multi-language pipelines locally without Docker

What would you like to happen?
Currently, multi-language pipelines require Docker execution mode (Docker SDK harness containers when executing the pipeline). This means that multi-language pipelines may not work appropriately for environments where pipelines have to be started from Docker containers and run locally (for example, when running pipelines within a K8 cluster).
This is to track work related to supporting this potentially with new Prism runner.
cc: @robertwb @lostluck
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Thank you, I'm planning on filling the litany of issues for Prism work After I Get Back From Vacation in July.

I think I misunderstood this when originally filed, and didn't read "without docker".
But once my current prism task is complete technically this should function with prism, assuming each Xlang source is able to specify loopback mode.  As it stands, that's always per SDK/per expansion service.  I do know that combining Go SDK Loopback + Java Docker works as one would hope, as I just needed it...
Prism could in principle also support "process execution" mode to accomplish this as well, but I haven't looked at that as the Go SDK hasn't yet supported it. Otherwise I don't know how one would accomplish it.

Thanks Rebo. That makes sense. I filed this as a feature request since some users wanted to run x-lang locally without Docker. Agree that there's more than runner support needed to address this.


IDVA6-1941: Updated dependencies.

1.0) Overview
email-producer-java's dependencies have grown stale, and this might be a potential source of security vulnerabilities. The purpose of this PR is to update all of the dependencies to the latest versions.
Was able to update everything to latest version, except for ch-kafka. Version 3.0.2 works correctly, but Version 3.0.3 results in an UnsupportedVersionException.
2.0) Testing
Used the acsp-manage-users-api to drive tests. In particular, changed the email-producer-java version in acsp-manage-users-api to unversioned. Then ran the acsp-manage-users-api locally with varying environments by adjusting application.properties. For example for CI-DEV, setting kafka.broker.addr=${KAFKA_BROKER_ADDR} to kafka.broker.addr=kafka-broker1-cidev.development.aws.internal:9092.
2.1) CI-DEV
First attempted to run the acsp-manage-users-api without any changes to email-producer-java. Successfully sent notification. Test passed.
Then attempted to run the acsp-manage-users-api with PR changes to email-producer-java. Successfully sent notification. Test passed.
2.2) Phoenix1
Attempted to run the acsp-manage-users-api without any changes to email-producer-java. This was working yesterday, but is not working today. Isolated problem to kafka.broker.addr=kafka-broker1-phoenix1.development.aws.internal:9092. Unable to connect to Phoenix1 - so unable to verify. Double-checked Phoenix1 (not local) and notifications are being sent there - so this is a local development environment issue. Test Result Unknown.
Because I can't connect to Phoenix1, I can't test the PR in Phoenix1 environment. Test Result Unknown.
2.3) chs-dev
Attempted to run the acsp-manage-users-api without any changes to email-producer-java. The acsp-manage-users-api successfully throws message onto Kafka Queue. The chs-notification-api retrieves the message successfully. Suggests that email producer and consumer are working together correctly. However, chs-notification-api can't find template even though it is definitely there. Looks like unrelated bug. Test Partially Passed.
Repeated above test with PR changes. Same result. Test Partially Passed.

CI: Security warnings found!


LUCENE-9204: Remove Spans references from DisiWrapper

We have a number of helper classes in o.a.l.search that aid the
implementation of two-phase iteration over disjunctions.  These have
some Spans-specific code, which will stop compiling once Spans
are moved into the queries module.  This commit removes the
Spans references from the main code and duplicates the helper
code within the Spans package.

I had hoped to do something similar to what we did for ConjunctionUtils and pull things into shared public factory classes, but that ended up with some very nasty generics code (things like DisiWrapper<T extends DisiWrapper>) so I think just cloning the classes here is unfortunately the correct tradeoff to make.

Thanks for the reviews @mikemccand!


tf.transpose can be very slow to execute on CPU

Transpose gets very slow if the tensor has rank > 8.
TF issue https://github.com/tensorflow/tensorflow/issues/27383

May I ask why you decided to close this? Is it no longer the case?

It's not something we can fix on our end.

True, but I thought we were using this (and e.g. #31, #34) to keep track of backend issues that are relevant to us. If you don't want to do that, that's okay with me, but I personally find it useful.


596542: DDR5 thermal control threshold MRW updates

The ubuntu fail can be ignored.  I actually thought that job was disabled...

Mike P reviewed the updates in github and said they look good.


Refactor Interpreter.invoke to preserve the initialized interpreter

I just noticed that the interpreter is being recreated on each invoke call.  We should be able to keep the initialized instance around and store the tensorflow c++ interpreter as an mp_obj_t on the microlite_interpreter_t object.

This has been merged.  We probably have to revisit the destructor case.


WIP: Sgx build improvements

Some minor changes to the SGX build.rs and Makefiles to reduce redundancy in builds and make sure changes get picked up

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 31a16f14f3842d2418762b9a6e9fff52913eee3d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 59b5f8cd059ba0eb2d96a780516686094882238a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@dreemkiller what is the relationship between this changeset and #195?  Does anything in #195 need porting into this changeset (given @geky is away, and both deal with similar topics)?  If not, then I'll approve this.

There is coincidental overlap between #195 and this one.
As the author of #195, I would prefer we use #195 and eventually merge that, but I am not an impartial party :-)

This is still marked WIP in the title, is it in a state ready to merge (eyeing the backlog of PRs and trying to work out which order is best to merge)?

This one can be low-priority to merge. I need to look at @geky 's PR and see if I can use it to improve this one (or not).
Imma keep it WIP for a bit.

A good portion of these have been done in other PRs. Closing.


dotenvx: 1.22.0 -> 1.28.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dotenvx/dotenvx/releases.
meta.description for dotenvx is: Better dotenv–from the creator of `dotenv
meta.homepage for dotenvx is: https://github.com/dotenvx/dotenvx
meta.changelog for dotenvx is: https://github.com/dotenvx/dotenvx/blob/refs/tags/v1.28.0/CHANGELOG.md
Updates performed

NPM version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.28.0 with grep in /nix/store/fjyd0sylbxz7wf3iml9i8fckdjdnjgmk-dotenvx-1.28.0
found 1.28.0 in filename of file in /nix/store/fjyd0sylbxz7wf3iml9i8fckdjdnjgmk-dotenvx-1.28.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

dotenvx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fjyd0sylbxz7wf3iml9i8fckdjdnjgmk-dotenvx-1.28.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dotenvx https://github.com/r-ryantm/nixpkgs/archive/b4201751907e15de2ce291e3ce342632fa985638.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b4201751907e15de2ce291e3ce342632fa985638#dotenvx

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fjyd0sylbxz7wf3iml9i8fckdjdnjgmk-dotenvx-1.28.0
ls -la /nix/store/fjyd0sylbxz7wf3iml9i8fckdjdnjgmk-dotenvx-1.28.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

dotenvx

Maintainer pings
cc @natsukium for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 363299

aarch64-darwin

:white_check_mark: 1 package built:

dotenvx


Update Upgrade Playbook statuses

DO NOT MERGE UNTIL VETO HAS PASSED SUCCESSFULLY
Check status here before merging.

https://snapshot.org/#/citizenshouse.eth/proposal/0xe2d86afceea73f2e2734550bec73af395b78826413fb3622b57dce43b2fd7b94
https://snapshot.org/#/citizenshouse.eth/proposal/0x21f7126c1636cecdcf7522eadbf6e1b20ca22a2230faf871209fcd21dc999d81

The veto period has ended and proposals have passed, so now merging this PR


Refactor text rendering logic into a class

Should have things like a font object, a text value, a background color, a foreground(text) color, and (x,y) coordinates to draw to.
draw method should take a screen/render destination object and render the text to that location.
update method should take in a new text value.
Should totally encompass the font boilerplate functions and values that are needed to render text to a surface(screen) object.

https://github.com/Kingcitaldo125/UnitCirclePygame/commit/649d7599a8ed54be51ff44534e4c344015a727fd


[BPF] Topology Aware Hints implementation

Description
fixes 7041
Running Calico with eBPF dataplane enabled and external kube-proxy disabled in the Kubernetes clusters on AWS.  Would like to optimize the inter-AZ network costs and implement the solution offered by k8s Topology aware hints.  It is understood that this feature is enabled in k8s 1.24 onwards.

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

ebpf: Topology Aware Hints supported when/where provided by k8s.

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

/merge-when-ready

pls couold you rebase this branch on the current master?

pls could you rebase this branch on the current master?
Done


how can i change the data of result['cover_image'] use computed?

export default {
    data: function() {
        return {
            result: {
                'cover_image': ''
            },
            url: '',
            method: ''
        }
    },
    computed: {
        host: function() {
            return store.state.host
        },
        account: function() {
            return store.state.account
        },
        uploadFile: function() {
            this.result.cover_image = store.state.uploadFile
            console.log('the data has not chanage', this.result)
            return store.state.uploadFile
        }
    }
}

Could you please follow the Issue Reporting Guidelines ?
It will be much easier to give you a good answer to your problem.


Report Warning in the CLI Execution

Currently, if you run a script in the CLI any warnings produced will be swallowed silently.
It would be good if any warning that occurs in the main method variables are sent to the logging system so can be seen by the user and captured into Elastic.

With #9773 I can do GraalVM Insight experiment...
Define Insight Script in JavaScript
Create a file enso_insight.js with following content:
let mod = Polyglot.eval("enso", `
from Standard.Base import Warning, Meta

h o = Warning.has_warnings o
w o = Warning.get_all o . at 0 . to_text
t o = o.to_text
`);
let h = mod.eval_expression("h")
let w = mod.eval_expression("w")
let t = mod.eval_expression("t")

function detect_warnings_among_local_variables(ctx, frame) {
  print(`Detecting warnings at the end of ${ctx.name}`);
  for (let n in frame) {
    let o = frame[n];
    if (h(o)) {
      print(`value of ${n} is ${t(o)} has warning ${w(o)}`);
    }
  }
  insight.off('return', detect_warnings_among_local_variables)
}

insight.on('return', detect_warnings_among_local_variables, {
  roots: true,
  rootNameFilter : ".*main"
});

it contains a mixture of Enso and JavaScript code. The JavaScript part "attaches itself" to end of execution of any method with a name that matches .*main regexp. It iterates over all local variables in the frame, checks if they have a Warning attached and if so, it prints it out.
Run any Script with Insight
Create an Enso file with main method. Execute it as:
JAVA_OPTS=-Dpolyglot.insight=enso_insight.js ./built-distribution/enso-engine-*/enso-*/bin/enso  --run Main.enso
Detecting warnings at the end of local.Main::local.Main::main
value of operator32735 is /tmp/temp_file_ensodryrun6824262491422756151.xlsx has warning Warning Only a dry run has occurred, with data written to a temporary file.  Press the Record Once button ❙⬤❙ to write the actual file.

the main method is executed and then all its local variables are scanned to check if they contain a warning. If so, the warning is printed. Similar execution can be used in batch executions.

One of the problems of the GraalVM Insight is the need to mix Enso and JavaScript. One way to avoid that is to make sure Warning can be recognized via a polyglot boundary - e.g. it exposes itself via the InteropLibrary in a recognizable way.

let mod = Polyglot.eval("enso", `
from Standard.Base import Warning, Meta

h o = Warning.has_warnings o
w o = Warning.get_all o . at 0 . to_text
t o = o.to_text
`);
let h = mod.eval_expression("h")
let w = mod.eval_expression("w")
let t = mod.eval_expression("t")

That could be done if we pretended that WithWarnings is actually an InteropLibrary.isException...

The AtTheEndOfFirstMethod code gives us alternative way (other than GraalVM Insight) to stop at the end of main method execution.
There already is :list command and it can be used to dump local variables and their warnings.
CCing @radeusgd

Can we also return a non-zero exit code if errors occur in main.

The current plan:

The AtTheEndOfFirstMethod code gives us alternative way (other than GraalVM Insight) to stop at the end of main method execution.
There already is :list command and it can be used to dump local variables and their warnings.

expand the instrument to do AtTheEndOfFirstMethod code
expand the :list command to print warnings and errors
by default on and perform :list+warnings+errors-regular (e.g. dump error like values)
non-zero when there is any error
zero exit when only warnings present


All the monitor files are not being displayed

This issue arises because each process runs its own version of main.py, i.e. the deletion of files (lines: 40-54, main.py) actually takes place num_processes times. Due to this parallelism, some processes have already created their monitor.csv file before the deletion code of other processes. This is causing the deletion of freshly created monitor.csv files.
The reason for latency might be fewer cores (number of cores = 4) in my CPU
Is there a workaround for making the deletion code in main.py (lines: 40-54) run only once?

You need to store log files for different experiments in different folder (set --log-dir flag). For example as in
https://github.com/ikostrikov/pytorch-a2c-ppo-acktr/blob/master/run_all.yaml
The reason why file are removed is that otherwise they might be polluted.

Could you clarify what do you mean by "different experiments"? Are you referring to each process of main.py as a different experiment? It is confusing because you have made several changes to the code within 24hrs.
I am using on an older version of this repository (num_step = 5 and num_processes = 16). In the older version, as we are using multiprocessing, the code in main.py is run 17 times (1 + num_processes). While the monitor.csv files are created by each of the child_processes (16 in total), each of these child_processes also tries to delete any existing files in the log-dir directory. My guess is that this won't be an issue if the CPU has more than 16 cores. However, as my CPU has only 4 cores, the 16 processes run in 4 batches of 4 and as a result I end up with 4 monitor.csv files each time I run the code.
I understand the reason why we want to delete previous monitor files before re-running the code.

Child processes themselves do not delete monitor.csv files. They can only override them. Also each child process writes to it's own monitor.csv file.
By an experiment I mean running main.py

All I am trying to say is that if you put a print statement in line: 39 main.py, it will be printed 17 times (i.e., 1 + num_processes). Which means the code between lines: 41-54 also gets executed 17 times. For each child_process make_vec_envs (line: 61, main.py) creates a *.monitor.csv file in log_dir directory.
In simple words, each child_process after creation first tries to delete all the *.monitor.csv files in log_dir directory (line: 45, main.py) and then attempts to freshly create the respective (*(env_rank)*).monitor.csv file (line:61, main.py).
I guess you are trying to say that the child_processes don't have access to code written outside main() function. However, that's not the case in my local system.

Hey, I went through the latest changes in the repository and the updates in the envs.py file has resolved the above-stated issue. Thanks :+1:


helper to send messages to topics

duplicate of #33 #34 and possibly simpler by using the send_with_notification_key() function.

@mangar and @alwaysanirudh  what do you think about doing it this way?


Add terminated to TransportSource protocol

wait_for_termination() is not included because it's deprecated. Users can still access in a non-typed context.

Shall we also replace wait_for_termination() and Transport iterator usage in examples?

I am also thinking about it, but actually methods are not removed. Users
need to switch to new methods if they want to enable pytype, otherwise the
old methods are still available.
Gilles Boccon-Gibod @.***> 於 2023年9月11日 週一 13:47 寫道：

@.**** commented on this pull request.
In bumble/transport/common.py
https://github.com/google/bumble/pull/280#discussion_r1321019316:

@@ -257,13 +259,6 @@ def on_transport_lost(self) -> None:
if hasattr(self.parser.sink, 'on_transport_lost'):
self.parser.sink.on_transport_lost()

async def wait_for_termination(self) -> None:

It's too early to remove this method, it is still being used by a lot of
code.
—
Reply to this email directly, view it on GitHub
https://github.com/google/bumble/pull/280#pullrequestreview-1619162896,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWBGOLH2NIRCEJO7GHQT3D3XZ2QYDANCNFSM6AAAAAA4SLOBFA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Small refactorings

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

27 of 27 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 36.469%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
5202

Relevant Lines:
14264

💛  - Coveralls


Create flag to inform services that need an assumption about potential reorg depth

We have multiple services that are in part parameterized by the user's risk tolerance for reorgs.
pruning-blocks-retained and Xsynchronizer-fast-sync-pivot-distance for example.
I propose we create a new flag that will create a floor for these parameters, ensuring that those services are at least as wary of chain reorgs as the user would like them to be.

Closing as stale. @RatanRSur - can you review for re-open? Pruner and fast-sync not supported at this point.

@diega - any need for this feature on PoW side?

not for the moment


Fixed vulnerability

Fixed this vulnerability: https://github.com/CosmWasm/docs/security/dependabot/5.
After upgrading to new version of next some changes were needed.
Old _meta.json files are required now to be named _meta.js
Old _app.json file is required now to be named _app.js
In flexsearch the attribute codeblock is not valid anymore.

@abefernan:  ATTENTION:
I don't know why, but the page "How to doc" appears again, I do not know how to disable it without removing from repository.

This seems to break dark mode for me (text, code blocks and top bar change, but background stays light)

Not relevant in the context of migration to Docusaurus.


Option to return results form subset of known channel claim ids

I don't think we are doing this anymore.


Update Stage 0 .NET Core SDK, as well as .NET Core bootstrap process

This updates the bootstrap process for .NET Core.  Instead of copying the whole sdk folder from the Stage 0 .NET Core SDK and then overwriting some MSBuild assets, we now publish a project which has the correct dependencies we need to create a functional .NET Core version of MSBuild.
This does mean that MSBuild now has (development-only) dependencies on specific versions of the NuGet.Build.Tasks and Microsoft.Extensions.DependencyModel versions, and we'll probably need to update those versions (defined in Versions.props) when MSBuild updates to a Stage 0 .NET Core SDK that uses different versions of those dependencies. @livarcocc @nguerrera @emgarten FYI for this dependency flow.
@AndyGerlicher I think this PR should unblock the .NET Core RAR caching support you are working on.

Can you validate that this fixes #2951?

Can you validate that this fixes #2951?

I have verified that it does

I like this approach to bootstrap since it makes our runtime ("publish", sort of) dependencies more explicit for what we need to actually run a build.
Looks like a lot of test failures though, and I don't see anything obvious :( @dsplaisted did you have a chance to look at any of them?

@dotnet-bot test OSX10.13 Build for CoreCLR

@cdmihai It looks like this is down to one test failure on non-Windows.  Could you investigate it?  The failing test is Microsoft.Build.UnitTests.ToolTask_Tests.ErrorWhenTextSentToStandardError.  I removed the triple quoting from 4 of the ToolTask tests due to a change in .NET Core 2.1 (see https://github.com/dotnet/corefx/issues/23496).  That fixed 3 of the tests but this one is still failing.

@cdmihai @jeffkl @rainersigwald @AndyGerlicher This should be ready for review.
I disabled some tests where the expected behavior of the File APIs has changed.  It might be better to have the same test coverage testing with different expected behavior for these scenarios on .NET Core.
I also disabled more tests against #2926, where the working directory isn't preserved.  I'm still not sure if this is a product issue or not.
I originally disabled multiprocess builds, because I was getting test hangs which I thought were happening because different test projects running in parallel were talking to each other when testing multiprocess build scenarios (because the process handshake for the different copies of MSBuild for each test project would be the same).  After all the other fixes, I was able to run the tests successfully with multiprocess build enabled.  So I've rebased that commit out.  It's something to keep in mind as a possible culprit if we see test hangs in the future though.


Redirects don't change the URL

if a page a link opens redirects to other page, it doesn't show the final url in the url bar ...is there a way to fix that?

I'm interested in this. Is the server-side header thing implemented?

It still isn’t.

Maybe it’ll be done with a meta tag or something instead of a header, as it’s easier to deal with, and there may be cases where someone doesn’t have control over their header (though I can’t think of one where you have a redirect too, but the fact that it’s easier is reason enough to go that way).

Same question. I think a server header is OK.

I'm not sure if anything has changed about the XHR api since 2015, but I'm using Chromium on Linux. I fixed the issue by going to line 748, where changePage is being called. I changed $url to $xhr.responseURL. It works perfectly with my server.
I'll submit a pull request if I can confirm it works with all other browsers.

This is 2014 issue, 5 years and this bug is still here...?