Purchasing - Shipping

This PR adds shipping to the purchase view.

@rmisio this is ready for review.

I noticed a bug in the shipping option template.

The missing price formatting in the shipping option is fixed now.

If I select a Shipping Address with no name, the ShippingOptions view bombs:

@rmisio how are you using a shipping address with no name? The name is required when you save the address.

how are you using a shipping address with no name? The name is required when you save the address.

Oh sorry, it did have a name. I just wiped my data, so I don't have the details, but I'm pretty sure I gave it the minimum data. Anyhow, the error is bombing because whatever object name is supposedly on is undefined.
I think what I was doing was purchasing when I had a single address - click add new address - add a new one and then back on the Purchase modal, select the new one I just created. That was causing it to bomb.

I think what I was doing was purchasing when I had a single address - click add new address - add a new one and then back on the Purchase modal, select the new one I just created. That was causing it to bomb.

I changed some things related to that in my current branch, which may have fixed it, as I can't replicate it with my current code (which will be in the next PR shortly).
We can probably close this one when I submit the next PR, since it polishes some things along with adding the receipt code.

re: the errors, my thinking was a) other than quantity, it would be really unusual to actually have an error, and b) I was being a little lazy.
The _.each is because it's an object instead of an array, it worked as expected when I tested it. I'll tinker with getting the errors into places that make more sense/


Update gradient function to return both value and gradient

Return value doesn't introduce any cost and it would save some computation for place where value is needed right after gradient evaluation.

I am trying the library now.
For now I defined a (mutable struct) storage buffer that stores the logdensity, gradient, and vector used for calling them.
The gradient and density functions check if the new parameter vector === the old one. If not, update the stored ValueGradient object and params.
If they are ===, simply return the old.
This relies on AdvancedHMC.jl not mutating the parameter vectors.
If the library is later updated to work in place, without yet resolving this issue, I'll use == instead, and copy data over. It'd take a lot of failed checks to be slower than evaluating the log density (200 microseconds vs 73 parameters).
As an off topic aside, my first impressions of AdvancedHMC.jl are very positive. The library seems very fast -- which probably mostly means that the trees are relatively shallow.
I was struggling to get convergence at all, but this library seems to converge rather well. So far it looks like I'm having more success with a DiagEuclideanMetric than a DenseEuclideanMetric.
Besides being fast and actually converging, I love progress=true while sampling. When my model fails to converge, the step size shrinks to < 1e-4. It's nice to get a live update on that and acceptance rate while mucking with settings.

Thanks for sharing this trick. The issue is likely to be resolved before the mutation PR got in - so here is no worries.

Closed by PR #79.


Fix more hashchange things.

I merged the next 2 commits.  Left off the last one -- I don't think I agree conceptually with treating settings/org as separate overlays; they are just different sections of a single overlay.  What's your thinking on that?  (I guess what makes sense here depends a bit on what "more stuff" is, but I definitely don't want to be reloading the overlay from scratch, since it's a thing that e.g. we want to be possible with left/right type keyboard navigation in the future)

@timabbott We discussed the objections you raised above on chat, and you agreed with my approach once you had a bit more context.
I've added several commits, but I still haven't fixed all quirks.

These all look good, merged, thanks @showell!  I'll let you decide whether to close this or keep this open for the next batch of commits.  Definitely appreciate the documentation update, though I think we also need a commit for ReadTheDocs: https://zulip.readthedocs.io/en/latest/subsystems/hashchange-system.html ?

Merged, after adding a hashchange: prefix to some commit messages.  Thanks @showell!


add xray processor example

This PR fixes #69 .
Description of changes
This PR adds an example for Xray processor and Xray image reader.
Possible influences of this PR.
Describe what are the possible side-effects of the code change.
Test Conducted
Describe what test cases are included for the PR.

@Piyush13y could you review this PR !


AWS S3 copy and move tasks and S3Bucket methods

Added

prefect_aws.s3.s3_copy
prefect_aws.s3.s3_move
prefect_aws.s3.S3Bucket.copy_object
prefect_aws.s3.S3Bucket.move_object

Closes #315
Example
from prefect_aws.s3 import s3_copy, s3_move

@flow
async def test_flow():
    await s3_copy(
        source_path="object",
        source_bucket_name="my-bucket",
        target_path="my-bucket/object",
        target_bucket_name="my-backup-bucket",
        aws_credentials=aws_credentials,
        aws_client_parameters=client_parameters,
    )
    await s3_move(
        source_path="object",
        source_bucket_name="my-bucket",
        target_path="archive/object",
        aws_credentials=aws_credentials,
        aws_client_parameters=client_parameters,
    )

from prefect_aws import S3Bucket

my_bucket = S3Bucket("my-bucket")
my_bucket.copy_object("critical/object", "my-bucket/object", target_bucket_name="my-backup-bucket")

my_bucket.move_object("object", "archive/object")

Screenshots

Checklist

[x] References any related issue by including "Closes #" or "Closes ".

If no issue exists and your change is not a small fix, please create an issue first.

[x] Includes tests or only affects documentation.
[x] Passes pre-commit checks.

Run pre-commit install && pre-commit run --all locally for formatting and linting.

[ ] Includes screenshots of documentation updates.

Run mkdocs serve view documentation locally.

[x] Summarizes PR's changes in CHANGELOG.md

@desertaxle

Added documentation to suggest when the native S3 operations should be used versus S3Bucket.stream_from.
client credentials are no longer passed directly to s3_copy nor s3_move
s3_copy and s3_move use AwsCredentials.get_s3_client
client_parameters direct fixture removed from test functions

The fixture is necessary for other fixtures. Removing it throws an error like so
/Users/dominictarro/Documents/GitHub/prefect-aws/tests/test_s3.py::test_s3_copy failed with error: Test failed with exception
request = <SubRequest 'client_parameters' for <Function test_s3_copy>>
    @pytest.fixture
    def client_parameters(request):
>       client_parameters = request.param
E       AttributeError: 'SubRequest' object has no attribute 'param'
tests/test_s3.py:41: AttributeError

Ah, that's right. I forgot about the logic that populates client_parameters. This looks good to me then!


Not able to render assets in face effect.

System information (Please provide as much relevant information as possible)

Have I written custom code (as opposed to using a stock example script provided in MediaPipe): Nope
OS Platform and Distribution (e.g., Linux Ubuntu 16.04, Android 11, iOS 14.4): Android 11
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: Realme X7 5G
MediaPipe version:  v0.8.9
Bazel version (if compiling from source): bazel 5.0.0
Android Studio, NDK, SDK versions (if issue is related to building in Android environment):

Describe the current behavior:
I'm building the apk file using the BUILD file present inside  //mediapipe/examples/android/src/java/com/google/mediapipe/apps/faceeffect using the command -
bazel build -c opt --strip=ALWAYS     --host_crosstool_top=@bazel_tools//tools/cpp:toolchain     --fat_apk_cpu=arm64-v8a,armeabi-v7a     --legacy_whole_archive=0     --features=-legacy_whole_archive     --copt=-fvisibility=hidden     --copt=-ffunction-sections     --copt=-fdata-sections     --copt=-fstack-protector     --copt=-Oz     --copt=-fomit-frame-pointer     --copt=-DABSL_MIN_LOG_LEVEL=2     --linkopt=-Wl,--gc-sections,--strip-all     //mediapipe/examples/android/src/java/com/google/mediapipe/apps/faceeffect:faceeffect.apk . The apk file is getting built without any error but I'm not able see any effects rendered on my screen.
Describe the expected behavior:
See the effects rendered on the screen.
Other info / Complete Logs :
I tried copying the code under faceeffect directory and built the face effect aar file, by setting USE_FACE_DETECTION_INPUT_SOURCE
I was able to render only the axis asset.

@sureshdagooglecom Any updates on this ?

Hi @Gojo1729 ,
Could you provide steps to reproduce this issue.

@sureshdagooglecom Just build the android binary for face effect using BUILD file present in \\mediapipe\examples\android\src\java\com\google\mediapipe\apps\faceeffect using the command
bazel build -c opt --strip=ALWAYS --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --fat_apk_cpu=arm64-v8a,armeabi-v7a --legacy_whole_archive=0 --features=-legacy_whole_archive --copt=-fvisibility=hidden --copt=-ffunction-sections --copt=-fdata-sections --copt=-fstack-protector --copt=-Oz --copt=-fomit-frame-pointer --copt=-DABSL_MIN_LOG_LEVEL=2 --linkopt=-Wl,--gc-sections,--strip-all //mediapipe/examples/android/src/java/com/google/mediapipe/apps/faceeffect:faceeffect.apk

And install the apk, this apk is not rendering the assets which it was suppose to render - glasses, face mask

@sureshdagooglecom  Any updates on this ?

@sgowroji Any suggestions here ? The rest all apks built using the BUILD file present inside
mediapipe\mediapipe\examples\android\src\java\com\google\mediapipe\apps  are working fine apart from faceeffect

@sureshdagooglecom It's working in v0.8.10

Hi @Gojo1729 ,
Are you facing any challanges with v0.8.10?

The issue is with v0.8.9, I think I might have made some unnoticed changes in the files, after creating a new clone it's working


fix: error handling

Fixes Android app crashing when the the tracker is not initialised.
The issue was that the code was throwing an Error class, but only catching Exception class throwables, which is not a superclass of Error. This resulted in the following kind of errors when attempting to track events before initialisation was completed:
Caused by java.lang.Error: Tracker is not initialized
       at com.reactnativepiwikprosdk.PiwikProSdkModule.trackEvent(PiwikProSdkModule.java:79)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:149)

Here we fix the issue by changing the type of class thrown when the tracker has not been initialised.

Yes, that is a valid concern. Looking at the code for the react native Promise.reject we see that it accepts any Throwable, of which both Error and Exception are subclassed.


fix: slightly improve CSS

Instrument flight PR to remove offending (invalid) CSS cursor declarations as well as 0 values that don’t need a unit.

As this is approved, how’s merging handled for contributions? @kenwheeler?

Anyone, @kenwheeler, @acasperw? Anything anyone can do to get out these small improvements?

Anyone there to merge this? @kenwheeler, @acasperw?


Easy interface for cr.pl.graph

I often want to quickly visualise a small directed graph and I think your function would be nice for this. It would be great if we could add a way to just pass it a numpy array or sparse matrix, instead of having to save the matrix in an anndata object first. Do you agree, or do you think I should just use networkx straight away?

Done via #43

Thanks, will check this out as well.

P_1 = np.array([[0.8, 0.1, 0.1], [0.5, 0.0, 0.5], [0.0, 0.1, 0.9]])
cr.pl.graph(data=P_1)

gives
--------------------
TypeErrorTraceback (most recent call last)
<ipython-input-129-f4145b11bf6c> in <module>
----> 1 cr.pl.graph(data=P_1)

TypeError: graph() missing 1 required positional argument: 'graph_key'

Should be fixed on master now.


Add 'version' arg to command line derivations

This adds the arg --version to the fqtk command line, which is apparently a requirement for adding it to nf-core, etc.

Hm... would seem our tool-chain file setup is not working, as it seems like the CI is failing in an untouched section due to a recently added clippy lint. I'll open an issue about that.

@NatPRoach can you fix up the CI and then would like a release so we can unblock https://github.com/fulcrumgenomics/nf-core-modules/pull/2

Thank-you!


[Event Request] Table 36  - Function RecreateSalesLines

We Like to have a OnBeforeRecreateSalesLines to be able to decided whether the RecreationProcess applies.

We already have this event
LOCAL RecreateSalesLines(ChangedFieldName : Text[100])
IF NOT SalesLinesExist THEN
EXIT;
OnRecreateSalesLinesOnBeforeConfirm(Rec,xRec,ChangedFieldName,HideValidationDialog,Confirmed,IsHandled);
IF NOT IsHandled THEN


Generate the extension vsix for each build

CI build needs to :

build extension vsix
attach built vsix to CI runs (useful to test PRs)
attach built vsix to rolling Development release for the main branch

@lavanyaj3 any progress on this one? I can make the changes myself now if you're having some issues.

Hi Fred,
The code is ready with the change.
Apologises for the delay in responding. We were having public holiday in Kochi location .
Will create Pull request today
Thanks,
Lavanya
From: Fred Bricon @.>
Date: Tuesday, 17 September 2024 at 6:19 PM
To: redhat-developer/vscode-granite @.>
Cc: Lavanya J @.>, Mention @.>
Subject: [EXTERNAL] Re: [redhat-developer/vscode-granite] Generate the extension vsix for each build (Issue #8)
@ lavanyaj3 any progress on this one? I can make the changes myself now if you're having some issues. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned. Message ID: <redhat-developer/vscode-granite/issues/8/2355665795@ github. com>
@lavanyaj3https://github.com/lavanyaj3 any progress on this one? I can make the changes myself now if you're having some issues.
—
Reply to this email directly, view it on GitHubhttps://github.com/redhat-developer/vscode-granite/issues/8#issuecomment-2355665795, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLAY5NMVE7XYGM2SPKAEWXDZXAQL7AVCNFSM6AAAAABNY3EPSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJVGY3DKNZZGU.
You are receiving this because you were mentioned.Message ID: @.***>

Fixed with #35


Add method to access url

This PR adds a method url() which enables you to access the url of the font stored locally (or else the fallback).
Sometimes this is needed, for example to use this package with the Filament admin panel: https://filamentphp.com/docs/2.x/admin/appearance#including-frontend-assets.
Filament::registerStyles([
    app(GoogleFonts::class)->load()->url(),
]);

Could you add a test that proves that it works?

Sure @freekmurze! ✅

Thanks!


Fix cilium panic when HttpRoute with missing port.

Must have port for Service reference
Fixes: #27956
Refer to https://github.com/cilium/cilium/blob/main/vendor/sigs.k8s.io/gateway-api/apis/v1beta1/object_reference_types.go#L95
Fixes: #issue-number
Must have port for Service reference

/cc @meyskens @sig-servicemesh  Ready for review, PTAL. Thanks~

Thanks good find! Might it be worth also adding a operator check like https://github.com/cilium/cilium/blob/main/operator/pkg/gateway-api/routechecks/route_checks.go#L40 so we can alert the user the route is not valid? As far as I know it is not there yet.

Hi, @meyskens Please take a look again. Thanks~

/test


python Visualization error

While trying to visualize field a2t

a2t = serializer.read("a2t", constantsoint)
Visualizer(a2t, "a2t")
Traceback (most recent call last):
File "", line 1, in
File "/scratch/cosuna/serialbox2/build_gcc_gfortran/install/python/serialbox/visualizer.py", line 59, in init
self.__jend = field.shape[1] - halospec[1][1]
IndexError: tuple index out of range

I have quite some other bugs,
from p_s_nnew in DycoreUnittest.DoStep-in
Traceback (most recent call last):
File "", line 1, in
File "/scratch/cosuna/serialbox2/build_gcc_gfortran/install/python/serialbox/visualizer.py", line 69, in init
self.__slider = Slider(slideraxes, 'K level', 0, field.shape[2] - 1, valinit=0)
IndexError: tuple index out of range


ssh/knownhosts: fix line matching, when multiple lines

When using knownhosts.New() over a standard file generated by ssh
with multiples hosts, the callback doesn't validate match any host
even when is on the file. This commit fix the issue and adds a
test to validate the solution.
Fixes golang/go#19994
Change-Id: I4aec415f3233ad6e85d9f5f4ab2f3d93b56d93cf

sorry, wrong place


Import causes Module not found Error

Describe the bug
After installing and importing into project, get this error:
Module not found: Error: Default condition should be last one
To Reproduce
Steps to reproduce the behavior:

pnpm install @marcellejs/core --save
setup project with webpack and ts
import * as marcelle from '@marcellejs/core'
run with webpack-dev-server
See error

Additional Information
OS: Linux
Node: v16.18.0 (npm v8.19.2)
webpack-dev-server: 4.11.1
Could be fixed by changing the order of export in the marcelle's package.json in node_modules

Thanks for the report, I will have a look at the PR shortly


Unable to download data from https://rubygems.org/ (error on windows)

On release v0.4.1 (rails-new-x86_64-pc-windows-gnu.zip) and Docker version 27.2.0, build 3ab4256
Running rails-new proj --devcontainer
`
=> ERROR [2/2] RUN if [ -z "7.2.0" ] ; then gem install rails ; else gem install rails -v 7.2.0 ; fi              1.2s

[2/2] RUN if [ -z "7.2.0" ] ; then gem install rails ; else gem install rails -v 7.2.0 ; fi:
1.022 ERROR:  Could not find a valid gem 'rails' (= 7.2.0), here is why:
1.022           Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 peeraddr=<IP_ADDRESS>:443 state=error: sslv3 alert handshake failure (SSL alert number 40) (https://rubygems.org/specs.4.8.gz)

Dockerfile:5
3 |     ARG RAILS_VERSION
4 |     # Install Rails based on the version specified but if not specified, install the latest version.
5 | >>> RUN if [ -z "$RAILS_VERSION" ] ; then gem install rails ; else gem install rails -v $RAILS_VERSION ; fi

6

ERROR: failed to solve: process "/bin/sh -c if [ -z "$RAILS_VERSION" ] ; then gem install rails ; else gem install rails -v $RAILS_VERSION ; fi" did not complete successfully: exit code: 2

thread 'main' panicked at src/main.rs:41:5:

assertion failed: status.success()

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

`

Looks like my organization IT has blocked access to rubygems.org


failed to snapshot query in hive when query a empty partition

When query a empty partition, hive will return a empty file in split path. In snapshot query this path will be added as a NonHoodieInputPaths. In this case HoodieParquetRealtimeInputFormat read a file split rather than a RealtimeSplit. Throw a exception:
HoodieRealtimeRecordReader can only work on RealtimeSplit and not with hdfs://test-cluster/tmp/hive/20220520/hive/4273589d-49be-4a60-9890-a29660d81927/hive_2022-11-14_11-32-41_221_5694963332005566615-17/-mr-10004/74adf5bb-b07e-4eac-a90b-1b5a7fc3d5c4/emptyFile:0+466

tracked in https://issues.apache.org/jira/browse/HUDI-5220


No reference to what-input in documentation for version 6

The readme is missing a reference to the js library "what-input". According to the Zurb Foundation installation docs and Changelog what-input is used instead of modernizr.

The absence of what-input.js will cause issues with Dropdown on the latest release (6.2.4, but fixed in https://github.com/zurb/foundation-sites/pull/9354).
In the meantime you can grab a copy, put it in vendor/assets/javascripts and require it in application.js.
More background on what-input


Minor changes to build with clang 7.

The changes in oslcomp.cpp seem only to be necessary with particular
combinations of clang7 and older llvm. Which we don't recommend!  Better
to use the same generation of clang and llvm. But in any case, may as
well make set those options explicitly.
Also switch SPI to build with clang7/llvm7 by default.

Can you backport this to the 1.9 branch please?

yes, will do

backport proposed in #919


Cucumber reports are not generated

After successfully running the tests through the command line using either ./gradlew connectedAndroidTest or ./gradlew connectedCheck it is showing on the Android Monitor the print

Retrieving Cucumber test report to /xx_myProjectPath_xx/CleanGUITestArchitecture/app/build

However, when I review on the project view the cucumber-reports folder it is empty. I am able to creat the report with spoon abd the default with androidTests, though not the case with cucumber-reports.

It seems there is a pending bug to fix since few years ago. What is more, I came across on the internet with other questions in StackOverflow and Google groups and yet, there is no a solution for this situation.
Google Groups Discussion

Another thing you can try is to align the report paths to write to and read from in your phone to a path that matches your project and see if the files are writen in the phone to that folder after running, modify:
https://github.com/sebaslogen/CleanGUITestArchitecture/blob/master/app/src/androidTest/java/com/neoranga55/cleanguitestarchitecture/test/CucumberTestCase.java#L18
https://github.com/sebaslogen/CleanGUITestArchitecture/blob/master/app/build.gradle#L43

Hi,
I've loaded, compiled and run the application successfully in Android Studio 2.3.2. However when I run Feature: defaults I experience a failure with the output below. Any ideas on what's going wrong? Do you require additional files?
Thanks,
H
...
Testing started at 11:54 ...
Undefined step: Given  I can see the Main Activity view
Undefined step: When  I enter the My Microwave Power value
Undefined step: Then  I should be able to save my microwave power value
1 Scenarios (1 undefined)
3 Steps (3 undefined)
0m0.000s
You can implement missing steps with the snippets below:
@Given...

Hey @sebaslogen sorry for the delay in replying. I did not understand very well your suggestion. You mean to change the format path on CucumberTestCase class and must be same as defined on build.gradle?

Yes and check if any file is created on the phone in that folder.

I changed the path folder in CucumberTestCase class, from /data/data/com.neoranga55.cleanguitestarchitecture/cucumber-reports/ to
/mnt/sdcard/cucumber-reports/
However, when running the instrumented tests. Cucumber jvm is not recognizing

On the same way, I also tried changing the path from gradle file. When finishing syn an running it still not creating the cucumber reports and do not create any file on my /data... path on the mobile,

@JairAviles  I just submitted a change to align both reporting folders in build.gradle and in CucumberTestCase to /mnt/sdcard/cucumber-reports/ - I executed it on an emulator (Nexus 4 API 21) and it works well. I suggest trying with the latest code and an emulator.
On the other hand, when I tried with the /data/data... I see the folder is created and filled while the tests are being executed but it's deleted just as the test finishes and probably before the gradle task that retrieves the report is executed.

HI @JairAviles, I am currently facing this issue on configuring my application.Can you please share the solution how you resolved taking the report from the Phone to your computer. I am using Android 6.0 emulator to run my tests.Do I need to add anything for device's API > 21?


Initial openedX deployment

We need an initial deployment of openedX to an RC environment for our first milestone. The setup for this should be similar to how we did it for xPro

Hardcoded Openedx configuration
Install social_auth mitxpro (this isn't specific to xpro, it's just named as such because that was our sole use case when implementing)
Install mitxpro_openedx_extensions

This is currently deployed to lms-qa.mitxonline.mit.edu


[beta] Sandpack - new bundler

Sandpack bundler v2 - demo
The Sandpack bundler v2 aims to eventually replace the current sandpack with a more streamlined and faster version. Plus, it allows us to implement even more improvements in the future, thanks to a fresh codebase that allowed us to remove many of the bottlenecks from the previous bundler.
The new bundler:

Skips transpiling step for dependencies by caching them in our custom-built CDN;
Fetches dependencies from our very own CDN, no longer third-party involved;
Uses less resource (avoid fetching unnecessary files) and lot quicker;

Same benefits from the previous bundler
Security
The bundler evaluates and transpiles all files in an iframe under a different subdomain. This is important because it prevents attackers from tampering with cookies of the host domain when evaluating code.
Scoped styles/javascript execution
There’s no risk of any executed code affecting the main page, which avoids unexpected styles or unhandled errors.
Performance
We heavily make use of Web Workers for transpilations, and only for those sandboxes that are in the viewport and the user is interacting with, meaning that we only use resources as needed.
Bundle Size
Another reason to host the bundler externally is because of code splitting: we split all our transpilers away and load them on-demand.
React DevTools
Sandpack bundler supports running react-devtools-inline in isolated mode, as an external dependency, which means you can run more than one instance per page and lazily load it.
Others

npm dependency support;
Hot module reloading;
Error overlaying;
Caching;

Benchmarketing

v1
v2

Memory usage (iframe thread)
~20MB
~ 5MB

Memory usage (babel) [1]
6.8 - 10.2MB
6.6 - 6.6MB

Network (compressed) [2]
2.8MB
863kb

Time to load (first time) [3]
9293ms
4149ms

Time to load (second time) [4]
565ms
566ms

Time to load [5]
854ms
214ms

[1] idle - peek
[2] Exclude local resource & external, except sandpack & disabled cache;
[3] Incognito window (fresh cache) & Fast 3G
[4] Cache enabled & Fast 3G
[5] Incognito window (fresh cache) & no throttling

Known issues / what’s next

[x] Implement react-devtools-inline  protocol;
[x] Server Components (still on discovery phase);

How to test it & how to use it
How to test
This PR is completely disposable, and it's only for testing purposes. So, in order to test it follow the steps:

Deploy this PR;
Access /sandpack page or this example page https://reactjs-org-do4znpw6x-danilowoz.vercel.app/sandpack;
Tick the checkbox to switch between bundle versions for all pages;
Feel free to navigate between pages and note that there's a timer to count how long a sandbox takes to load;

How to use
<SandpackProvider
	...
+   bundlerURL="https://cf56a978.sandpack-bundler.pages.dev"
 >

Hope it addresses most of the problems we've discussed before. We're looking forward to hearing any feedback about this new version and please let us know about any problem you notice.
Kudos to @DeMoorJasper for all the hard work on this! 🙌

I've been focused on other stuff for a bit. What is the current status on this?

Hey @gaearon, I was about to ping you about this issue.
So, we've fixed all the known issues (like react-devtools-inline) and I just updated this PR to use the latest version of the bundler and a versioned one (the previous was using a URL from the main branch, which was vulnerable to broken deploys).
Although the new bundler is still in beta, we're confident that for React templates the bundler is stable and ready to be used. Of course, we might end up with some edge cases, but given the benefits (bundle size, speed, reliability) it's worth giving it a try.

Can we remove the timer etc so that this is ready to merge? Thanks!

This breaks runtime error reporting.
https://user-images.githubusercontent.com/810438/167263973-e46fed05-14d0-4900-93df-9eaef5430628.mov

Latest changes:

Bundler: catch global errors and pass them as a message to Sandpack;
Sandpack: Use useId instead of random string for ids;
Sandpack: omit logs from bundlers;

Something about reporting errors regressed because it shows internal frames now.
Before:

After:

Opened a PR to disable the error stacks for node_modules https://github.com/codesandbox/sandpack-bundler/pull/21 which should fix the issue you mentioned

Let's try it! Thank you so much!!


Feat/ QuipuSwap connector for Tezos chain

Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
Added support for QuipuSwap Dex on the Tezos chain.
Tests performed by the developer:

Added unit tests for the controller and QuipuSwap main class.
Tested amm_arb between Binance and QuipuSwap.

Tips for QA testing:

Launch the Hummingbot client as usual.
Then add a non-empty Tezos wallet using it.
Then create some strategy including QuipuSwap Dex connector on it.
Then start the bot.

Hi @david-hummingbot
I've create the PR here: https://github.com/hummingbot/hummingbot-site/pull/340


Option to provide partition column and partition expiry time

While creating a new table using pandas, it would be nice if it can partition the table and set an partition expiry time. The python bigquery library already supports it
# from google.cloud import bigquery
# client = bigquery.Client()
# dataset_ref = client.dataset('my_dataset')

table_ref = dataset_ref.table("my_partitioned_table")
schema = [
    bigquery.SchemaField("name", "STRING"),
    bigquery.SchemaField("post_abbr", "STRING"),
    bigquery.SchemaField("date", "DATE"),
]
table = bigquery.Table(table_ref, schema=schema)
table.time_partitioning = bigquery.TimePartitioning(
    type_=bigquery.TimePartitioningType.DAY,
    field="date",  # name of column to use for partitioning
    expiration_ms=7776000000,
)  # 90 days

table = client.create_table(table)

print(
    "Created table {}, partitioned on column {}".format(
        table.table_id, table.time_partitioning.field
    )
)

https://cloud.google.com/bigquery/docs/creating-column-partitions
I can create a pull request, if people feel like it's something they find useful. At least in my work, we create lot of monitoring tables on bigquery using pandas, and push data to it. These tables keep growing and since we can't set the partition when a table has already been created, these tables just become too big, and expensive.

I'm open to a pull request that adds this.
Ideally, I'd like to see to_gbq gain a configuration parameter that takes a load job JSON configuration. (job configuration resource, load job configuration resource)
Example:
pandas_gbq.to_gbq(
  df,
  configuration={
    "load": {
      "timePartitioning": {
         "type": "DAY",
         "expirationMs": str(1000*60*60*24*30),  # 30 days
         "field": "my_timestamp_col"
      }
    }
  }
)

One problem with the configuration proposal is that currently pandas-gbq creates tables with calls to create_table if the table doesn't exist, rather than letting the load job create it. I'd like to refactor to_gbq to avoid this (unnecessary, IMO) step. Open to PRs to do that refactoring, but if you'd like to extract options from configuration when creating the table, that might be simpler short-term.

Yeah, I had something like configuration thing in mind. Why does the expirationMs  need to be passed as a string though?

Why does the expirationMs need to be passed as a string though?

It's a historical artifact of the BigQuery REST endpoint using an older JSON parsing implementation that only had JavaScript Number (floating point) available. Encoding it as a string allows the BigQuery REST endpoint to interpret the value as a 64-bit integer without loss of precision.
I believe an integer will be accepted, but you might lose precision for large values.

I'm open to a pull request that adds this.
Ideally, I'd like to see to_gbq gain a configuration parameter that takes a load job JSON configuration. (job configuration resource, load job configuration resource)
Example:
pandas_gbq.to_gbq(
  df,
  configuration={
    "load": {
      "timePartitioning": {
         "type": "DAY",
         "expirationMs": str(1000*60*60*24*30),  # 30 days
         "field": "my_timestamp_col"
      }
    }
  }
)

One problem with the configuration proposal is that currently pandas-gbq creates tables with calls to create_table if the table doesn't exist, rather than letting the load job create it. I'd like to refactor to_gbq to avoid this (unnecessary, IMO) step. Open to PRs to do that refactoring, but if you'd like to extract options from configuration when creating the table, that might be simpler short-term.

Are you still open to a PR that does the refactoring? If so, I'd be interested to work on it.

I referenced this issue from https://github.com/googleapis/python-bigquery-pandas/issues/425, but will keep this open in case we don't decide to rely on the load job for table creation.


Introduce fail-fast option

Introducing a fail-fast option
Default behaviour is to continue planning even after one of the terraform plans have failed. This option if set to true will change behaviour to fail after the first terraform plan or apply has failed

As it turns out, it seems like it's already the default behavior, except for the fact that when using a mono-repo , the workflow will currently continue when a project lock is already acquired by another PR.
I think the workflow should fail in that case to be consistent.

To add-on to my last comment, now that digger combines multiple plan outputs into a single comment, the fact that the workflow is not failing when a lock can be acquired can be confusing / misleading


Add support for variable last column widths in Markdown tables

Add support for variable last column widths in Markdown tables.
Often the last column in a Markdown table is the widest, and adding new rows with long pieces of text can cause the whole table to need reformatting, which isn't ideal in a Git diff view.
If the last column in a Markdown table can be variable with, the example given in https://github.com/bitwiser73/MarkdownTableFormatter/issues/22 is a single-line change, rather than a seven-line change.
Closes: https://github.com/bitwiser73/MarkdownTableFormatter/issues/22.

@bitwiser73 What do you think of this PR? I'm using the changes locally and they work great for me.
I think the code could be optimized so that rather than making the change after the initial column widths are calculated, the final column setting is just set up front and there's no attempt at calculating it dynamically.
That said, it's probably not a very costly operation either way.


💡 [REQUEST] - Reorder Allowed/Blocked words on UI

Reference Issues
No response
Summary
Make the blocked words show by default when opening the extension instead of the allowed words. Users would have installed this extension to block out certain content so they are more likely to want to see the blocked list of keywords first.

Basic Example
The allowed and blocked tabs will be switched ("Allowed" on the left and "Blocked" on the right). The correct list of keywords and correct edit button should also display.
Drawbacks
Usually, it's positive action first, then negative action. E.g. "Yes" and "No", rather than "No" and "Yes". But, I think it makes more sense to have "Blocked" first due to the reasons above.
Unresolved questions
No response

Approved


Toggle dynamic batcher for add_samples(), others

What changes are proposed in this pull request?

Add StaticBatcher as an option to use in place of DynamicBatcher. The latter attempts to optimize for a nice flowing progress bar, whereas the former optimizes for predictability and is better in cases where latency between machine and MongoDB is higher.
Add configuration to allow switching from the default "dynamic" to new "static". Also database batcher size is configurable.

TODO

[ ] add to configuration section of docs

How is this patch tested? If it is not, please explain why.

By default, add_samples() should do the same thing.
Only if you configure it to use StaticBatcher will it change behavior.
Added some unit tests for batch factory and static batcher

import fiftyone as fo

dataset1 = fo.zoo.load_zoo_dataset("quickstart")

dataset2 = fo.Dataset()

# Can set this or not, default is 'dynamic'
#fo.config.default_batcher = "dynamic"

# Should see irregular batch size with progress bar flowing smoothly.
dataset2.add_samples(dataset1)

# Should see regular batch size of 10 in the progress bar
fo.config.default_batcher = "static"
fo.config.default_database_batch_size = 10
dataset2.add_samples(dataset1)

dataset1.delete()
dataset2.delete()

Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[x] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

Added choice of a static batcher for greater predictability in some batched database operations such as add_samples().
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[x] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

rebased

Rebased after bulk_write config merge, and made final suggested changes.

ok last time 🤞🏼