Pubsub ordering keys

Pubsub has a new upcoming feature which will allow users to send and receive messages in a guaranteed order.
@kamalaboulhosn and @kimkyung-goog, I believe that all of the features are ready to go.  Can you please review this PR?  Also, guidance would be appreciated on whether or not you feel like this can be merged to master.

@kimkyung-goog can you just verify that setting ordering keys in messages results in the messages being rejected by the Pub/Sub server for now? If that is true, then it is is safe to merge to master.

@kimkyung-goog can you just verify that setting ordering keys in messages results in the messages being rejected by the Pub/Sub server for now? If that is true, then it is is safe to merge to master.

Answered by email (since it contains some internal links)


Automated Package Upgrade

:tada: This PR is included in version 25.3.38 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


migrate from react-scripts to vite

migrated from react-scripts to vite changed the index.html, index.js index.css and added vite.config.js, tailwindcss.config.js postcss.config.js

reviewed


batch prediction ?

how to feed a batch of data to the model ?
model.input_shape
[(None, 512), (None, 512)]

,
When I was trying to feed the model with a batch of data, such as data shape = [64, 2, 512] it gives
"ValueError: Error when checking model input: the list of Numpy arrays that you are passing to your model is not the size the model expected. Expected to see 2 array(s), but instead got the following list of 1 arrays ..."
,
I was using something like this:
from keras.layers import Lambda
import keras.backend as K
def mean(x):
    return K.mean(x, axis=1, keepdims=False)
###
inputs, embeds = get_model(
    token_num=len(token_dict),
    head_num=12,
    transformer_num=12,
    embed_dim=768,
    feed_forward_dim=100,
    seq_len=512,
    pos_num=512,
    dropout_rate=0.05,
    training = False,
)
####
avg_embeds = Lambda(mean)(embeds)
pred = Dense(1, activation="sigmoid")(avg_embeds)
model = Model(inputs=inputs, outputs=pred)
model.compile(loss='binary_crossentropy', optimizer='adam', metrics=['acc'])

Thanks

You need to pass a list of two numpy arrays of size [64, 512].


ERRORS

Where does swashbuckel logs error ?
I get error forbidden when try to do view swagger in my project ?

Is there way to debug swashbuckel code locally to see exception? I m using nuget package I am not sure how to debug internal code to get exception?

ANY help would be appreciated.

Swashbuckle doesn't do any specific exception handling - in other words, all exceptions are simply bubbled up. I've no idea why your seeing a forbidden response but it's unlikely to be SB causing it.


Add support for IHostingStartup/IHostStartup  in generic host

In WebHost, there is IHostingStartup interface, see https://github.com/aspnet/Hosting/issues/1000.
Can we do something similar for generic host, something like below
/// <summary>
    /// Represents platform specific configuration that will be applied to a <see cref="IHostBuilder"/> when building an <see cref="IHost"/>.
    /// </summary>
    public interface IHostStartup
    {
        /// <summary>
        /// Configure the <see cref="IHostBuilder"/>.
        /// </summary>
        /// <remarks>
        /// Configure is intended to be called before user code, allowing a user to overwrite any changes made.
        /// </remarks>
        /// <param name="builder"></param>
        void Configure(IHostBuilder builder);
    }

I will need this to execute some platform specific logic for integration testing with Service Fabric; I could define my own interface and get it work, but it would be useful if such concept could be generic in the generic host.

IMHO it would be great to also have support for the

HostingStartupAssemblies
HostingStartupExcludeAssemblies

similar to the WebHost so a developer can inject assemblies that register/configure services prior to creation of the Host and/or IHostedService, BackgroundService without explicitly referencing/changing code.

Is this still in scope for 3.0?

Is this still in scope for 3.0?

No, it's in the backlog.

@Tratcher do you know if the plan is to get this into 3.1 ? or sooner after v3.0 release ?

We haven't made plans for 3.1 yet, and it's not clear how high a priority this scenario is, we've only heard interest from a few people.

Use case: Azure Pipelines (and other CIs) have their own syntax for parsing warnings and errors.
If we had IHostingStartup an Azure Pipelines logger assembly could just be injected using the .NET Startup Hooks and then you could run dotnet tools that use the generic host (e.g. together with the Hosting package from dotnet/command-line-api ) setup logging.
Point is under normal running the tool would log using normal console logger. In Azure Pipelines the output would actually highlight warnings and errors in the Azure Pipelines Build summary.
I actually do something quite similar for my .NET Core building tasks. I pass a custom MSBuild logger assembly as an argument to all .NET Core tasks. But the principle is very similar.

Regarding the Needs Design label, can't we simply copy the functionality from Microsoft.AspNetCore.Hosting? Only the parts required for the IHostStartup, i.e.

Add the IHostStartup interface to ....Hosting.Abstractions
Add the HostingStartupAttribute class to ....Hosting.Abstractions
Add properties PreventHostingStartup, HostingStartupAssemblies, HostingStartupExcludeAssemblies from WebHostOptions to the Microsoft.Extensions.Hosting.HostOptions class
Add and call the method ExecuteHostingStartups from the class Microsoft.AspNetCore.Hosting.GenericWebHostBuilder to the ....Hosting.HostBuilder class

@couven92 this seems on the face of it what is needed, and this would definitely assist in helping building a flexible/plugin host and dynamic configuration of services prior to the bootstrapping of services; I'm wondering if this type of process (dynamic loading of assembly) should verify that the assembly is signed using the a digital key and if the host trusts the signed key?
which in itself opens up a few questions around the current implementation in the Microsoft.AspNetCore.Hosting namespace/assembly.


Error when running SSE on Qlik Sense Desktop

Hi Daniel,
Thank you for sharing this extension, I installed the Python sse service locally and am using Qlik Sense Desktop, however I am getting the following error when trying to reload the example qvf.  I have the yelp.csv file):
qlik Connector reply error: grpc::StatusCode::UNKNOWN: 'Exception iterating responses: local variable 'translations' referenced before assignment'
Any Pointers?

Hi Daniel,
Many thanks for the swift response, I've tried the above several times, and
now am getting the following reply from the connector:
Connector reply error: grpc::StatusCode::INTERNAL: 'Received RST_STREAM
with error code 1'
Have you had any experience of this before? many thanks!
kind regards,
Harry Mehmi
Qlik Consultant
T:     +44 (0)<PHONE_NUMBER>
M:    +44 (0)<PHONE_NUMBER>
E<EMAIL_ADDRESS>W:   www.datatechnology.co.uk
Winner of the 2014 and 2015 Global Qlik Partner Award for Excellence in
Customer Advocacy
Data Technology Ltd. | Registered office: Unit 18, Building 6 Croxley Green
Business Park Watford WD18 8YH| Registered in England no: 2154023.
Privac http://www.datatechnology.co.uk/privacy-cookies/y & Unsubscribe
http://www.datatechnology.co.uk/usubscribe/
Please note, I process my emails at these times: 8.00am | 10.30am | 1.30pm
| 4.30pm
This electronic message contains information from Data Technology, which
may be privileged or confidential.  The information is intended for use
only by the individual(s) or entity named above.  If you are not the
intended recipient, be aware that any disclosure, copying, distribution or
use of the contents of this information is strictly prohibited. If you have
received this e-mail message in error, please notify us immediately by
telephone. Please also destroy and delete the message from your computer.
On Mon, 29 Oct 2018 at 17:29, danielpilla<EMAIL_ADDRESS>wrote:

Hello,
I was just able to replicate the issue. The issue arose when Google
changed their method of sending tokens, apparently, and this is a widely
known issue that affected a number of repos. You can see the specific
issues replicated on the repo itself here
https://github.com/ssut/py-googletrans/issues.
To resolve, you can try this (from stack overflow)
https://stackoverflow.com/questions/52455774/googletrans-stopped-working-with-error-nonetype-object-has-no-attribute-group
:
$ pip uninstall googletrans
$ git clone https://github.com/BoseCorp/py-googletrans.git
$ cd ./py-googletrans
$ python setup.py install
I will update the README.md.
Cheers,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danielpilla/qlik-python-sse-google-translation/issues/1#issuecomment-434001364,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATENjAPPqxKb9RHW9cQ-4vlHZvm6dE3Vks5upzr4gaJpZM4X_hwE
.


Pandas time series chapter

We really should to a chapter on time series...

:+1: :+1: :+1:

We have a notebook that can serve as a template for the book chapter


Support for labels on pages

As Developer
I want to be able to tag certain pages of my documentation
so that they can easily be found through filters and overview pages.
I have recently started writing quite a bit of documentation in sphinx and this feature would help me and my colleagues a great deal.
My initial idea is to add a custom directive .. labels:
All labels directive occurrences within a page are joined for the final set of labels. Same would happen for the singleconfluence builder.

I would be willing to implement this myself although I must warn you that I have not created directives before.
I have seen that there is currently an issue with the new style editor and that issue of course takes precedence over such a minor enhancement.
Please let me know what you think.
Cheers

@edthamm, if you want to look at trying to introduced this capability sooner than later, feel free to try to generate a PR. I would be happen to help review/test such a capability.
As you have mentioned, there will be more of a priority to focus on supporting the new document document.
My only major concern would be that such a feature would only be good long term for this extension if managing labels is still supported in the most recent APIs provided by Atlassian (i.e. if Confluence Cloud and Confluence Server 7.x series dropped supported for API-managed document labels, it would not make sense to me to try to support it in this extension).
Other notables to consider would be as follows:

It may be "better" to use a directive name confluence_label instead of just label for clarity (and to minimize risk of conflicting with possible other extension directives).
May want to consider options where a user may want to "stack" labels (add new labels; allow labels from outside publishing) versus "override" labels (removing old/legacy labels); just food-for-thought.

@jdknight cool I'll see when I can find the time. Thanks for offering the assistance.
I will check the APIs for cloud and server. My assumption was that they would keep that because they built their whole aggregation pages feature around that. But you are correct better save than sorry. Will add my results here.
Regarding your other points:

I am all in favor on namespaces after all they are a honking great idea and if sphinx wants to support that as a general concept it should be in their main line. You are correct.
I have not thought so far yet. Would do this in some testcases for the first review. My first idea was that MVP basically behaves consistent with the confluence_purge feature. I.e. labels would only be added unless the page is purged which would remove the page and recreate only currently defined labels. Might not be smart though. I will think on this

Hello,
I've introduced a PR that supports adding labels when publishing a page. This is the first time I've created a Sphinx any advice would be appreciated.
This directive seems a bit odd in that Confluence labels are stored outside of the document therefore the directive doesn't actually introduce any content to page. To work around this I used the builder configuration variable to hold the list of labels and then added them into the JSON blob when publishing via the API. This didn't seem like the best solution to me, does anyone have any other suggestions on how to approach this?
#332

This feature is now available on master through the confluence_global_labels configuration option and the confluence_metadata directive. Thanks for the contributions made to help making this feature available for everyone. This feature should also be made available next stable release.


Kyber: add F* proofs

This PR adds a new directory extraction-edited to proofs/fstar/ with a set of proof for the Kyber implementation.
The code in this new directory started as a snapshot of the generated F* code in proofs/fstar/extraction but has been hand edited with annotations, invariants, pre- and post-conditions, as well as a functional specification of Kyber.
The proofs currently check the following:

all the modules are proved to be panic-free
modular arithmetic are functionally verified (Libcrux.Kem.Kyber.Arithmetic)
constant-time operations are functionally verified (Libcrux.Kem.Kyber.Constant_time_ops)
the functions implementing IND-CPA encryption, and the IND-CCA KEM are functionally verified
part of serialization and NTT are functionally verified; in particular, we prove that all range assumptions hold, and that there are no arithmetic overflows
secret independence is partially verified (in particular, division with secret inputs is forbidden)

However, some parts remain, and we are adding open issues to track them and will address them in future PRs.

full functional correctness for NTT, matrix operations, and serialization
secret independence for the whole code

In further future work, we will seek to address the following:

minimize diffs between extraction-edited and extraction by propagating pre- and post- conditions and meaningful annotations to the source Rust code
put the proofs and the proof-related patch in extraction-edited under CI
re-verify any recent changes to the Rust code

I disabled CI for now on extraction-edited, see #168.

Ok, let's get this in. Not sure if you want to update the PROOFS.md before merging.

That file was out of date, so I removed it. The comments on this PR and the remaining issues are the ones that are most relevant.


[UX] Allow user to add consensus information AFTER adding pubkeys

I'm submitting a…

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[x ] Feature request
[ ] Documentation issue or request
[ ] Support request

Current Behavior
Given the order of Cards on the Wallet page, my guess is users will naturally fill out xpub import section before filling out Consensus information. If user fills out xpub information before getting the change to add consensus information, they do not get a chance to change this afterwards.
https://www.loom.com/share/c470dbc734824c98a0dbb33b2051cd56

Expected Behavior
It would be nice to be able to optionally add private consensus / node information after all xpub information is added.

Possible Solution
Potentially:

add the same Consensus/node Card on the screen where wallet is being created, or
Later on the actual wallet screen.

I tend to agree with the comment about the layout.  I think we should prompt the user for all of that information before allowing them to import xpubs.  I don't know how many times I have imported one or more xpubs and then had to start over because I release I had the wrong address type or network.

+1
There have been discussions about redesigning this layout completely and building it as more of a "Wizard" flow where the user is walked through each step one by one, ensuring that they are explicit with their decisions.


Update to GOV.UK Frontend v3.7.0

Closes #1267

You can preview this change here:
Built with commit a0a851c1c677a313d96cc0e70db688a16b5017e6
https://deploy-preview-1271--govuk-design-system-preview.netlify.app


Add 3D view of CAD model on the landing page

Hi , I want to work on this issue. Can you please add more details about the issue

What is expected :
Somewhat like https://sketchfab.com/tags/robot
Functions: Zoom in, zoom out and view the robot around in 3D
Resources to get started with:
https://medium.com/samsung-internet-dev/adding-3d-models-to-your-website-d374a8cbbadd
CAD files:
Will upload soon after generating in appropriate format. The format of the file will be .STL so look for ways to display the STL files only.
Let me know if you need some help

Hi!
I tried implementing it using a demo website and a demo model which was in.STL format itself. I browsed around the internet to look out for some ways to do it and found out that the only way to do it was with the three.js package and webGL but the complexity was a little high and the location of the necessary scripts for rendering STL files was changed or damaged.
I looked for some other ways and found a simple way of doing this so, I changed the file format to a .glb file and used the model-viewer to render it. The short video below shows the demo of a cube :)
https://user-images.githubusercontent.com/79045568/211429762-b6429ddd-3dea-4663-a9f7-9c0bf6d36561.mp4

Since the rover is an assembly of components, I need to see if the assembly can be exported in the said format. Will update you as soon as possible.

Please find the necessary STL file here:
https://drive.google.com/drive/folders/1ZobpWKlM0iXcPFHcfGNOf_zRO45vMgGC?usp=share_link


Syncs are failing with the latest pihole update

What happened?
My pihole docker containers auto-upgraded to 2023.3.0 overnight and I noticed this morning that orbital syncs were failing to apply to other instances. It seems like the backup was fine, but the replication to other pihole instances was failing.
I reverted pihole to 2023.2.0 and it started working again.
Version
1.5.1-0
Log output
3/23/2023, 11:16:32 AM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:16:32 AM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:16:32 AM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 11:16:32 AM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:16:32 AM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 11:16:32 AM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:16:37 AM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 11:16:40 AM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 11:16:40 AM: ⚠ Failure: 0/2 hosts synced.
3/23/2023, 11:16:42 AM: Waiting 15 minutes...
3/23/2023, 11:31:42 AM: ➡ Signing in to http://<IP_ADDRESS>/admin...
3/23/2023, 11:31:42 AM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
3/23/2023, 11:31:42 AM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
3/23/2023, 11:31:42 AM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
3/23/2023, 11:31:42 AM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:31:42 AM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:31:42 AM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 11:31:42 AM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:31:42 AM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 11:31:42 AM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:31:47 AM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 11:31:49 AM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 11:31:49 AM: ⚠ Failure: 0/2 hosts synced.
3/23/2023, 11:31:50 AM: Waiting 15 minutes...
3/23/2023, 11:46:50 AM: ➡ Signing in to http://<IP_ADDRESS>/admin...
3/23/2023, 11:46:50 AM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
3/23/2023, 11:46:50 AM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
3/23/2023, 11:46:50 AM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
3/23/2023, 11:46:50 AM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:46:50 AM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:46:50 AM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 11:46:50 AM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:46:50 AM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 11:46:50 AM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 11:46:56 AM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 11:46:57 AM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 11:46:57 AM: ⚠ Failure: 0/2 hosts synced.
3/23/2023, 11:46:58 AM: Waiting 15 minutes...
3/23/2023, 12:01:58 PM: ➡ Signing in to http://<IP_ADDRESS>/admin...
3/23/2023, 12:01:58 PM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
3/23/2023, 12:01:58 PM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
3/23/2023, 12:01:58 PM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
3/23/2023, 12:01:58 PM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:01:58 PM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:01:58 PM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:01:58 PM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:01:58 PM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:01:58 PM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:02:04 PM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 12:02:05 PM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 12:02:05 PM: ⚠ Failure: 0/2 hosts synced.
3/23/2023, 12:02:06 PM: Waiting 15 minutes...
3/23/2023, 12:17:06 PM: ➡ Signing in to http://<IP_ADDRESS>/admin...
3/23/2023, 12:17:06 PM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
3/23/2023, 12:17:06 PM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
3/23/2023, 12:17:06 PM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
3/23/2023, 12:17:06 PM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:17:06 PM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:17:06 PM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:17:06 PM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:17:06 PM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:17:06 PM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:17:12 PM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 12:17:13 PM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 12:17:13 PM: ⚠ Failure: 0/2 hosts synced.
3/23/2023, 12:17:14 PM: Waiting 15 minutes...
3/23/2023, 12:32:15 PM: ➡ Signing in to http://<IP_ADDRESS>/admin...
3/23/2023, 12:32:15 PM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
3/23/2023, 12:32:15 PM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
3/23/2023, 12:32:15 PM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
3/23/2023, 12:32:15 PM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:32:15 PM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:32:15 PM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:32:15 PM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:32:15 PM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:32:15 PM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:32:20 PM: ✔ Backup uploaded to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:32:20 PM: ➡ Updating gravity on http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:32:23 PM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".
3/23/2023, 12:32:27 PM: ✔ Gravity updated on http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:32:27 PM: ⚠ Failure: 1/2 hosts synced.
3/23/2023, 12:32:29 PM: Waiting 15 minutes...
3/23/2023, 12:47:29 PM: ➡ Signing in to http://<IP_ADDRESS>/admin...
3/23/2023, 12:47:29 PM: ✔ Successfully signed in to http://<IP_ADDRESS>/admin!
3/23/2023, 12:47:29 PM: ➡ Downloading backup from http://<IP_ADDRESS>/admin...
3/23/2023, 12:47:30 PM: ✔ Backup from http://<IP_ADDRESS>/admin completed!
3/23/2023, 12:47:30 PM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:47:30 PM: ➡ Signing in to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:47:30 PM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:47:30 PM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:47:30 PM: ✔ Successfully signed in to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:47:30 PM: ➡ Uploading backup to http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:47:35 PM: ✔ Backup uploaded to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:47:35 PM: ➡ Updating gravity on http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:47:37 PM: ✔ Backup uploaded to http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:47:37 PM: ➡ Updating gravity on http://<IP_ADDRESS>:90/admin...
3/23/2023, 12:47:42 PM: ✔ Gravity updated on http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:47:44 PM: ✔ Gravity updated on http://<IP_ADDRESS>:90/admin!
3/23/2023, 12:47:44 PM: ✔ Success: 2/2 hosts synced.
3/23/2023, 12:47:44 PM: Waiting 15 minutes...

3/23/2023, 3:22:55 PM: {"host":"http://<IP_ADDRESS>:90","path":"/admin","status":200,"responseBody":"Start importing...
\nProcessed adlist (5 entries)
\nProcessed adlist group assignments (5 entries)
\nProcessed blacklist (exact) (0 entries)
\nProcessed blacklist (regex) (0 entries)
\nProcessed client (0 entries)
\nProcessed client group assignments (0 entries)
\nProcessed local DNS records (20 entries)
\nProcessed local CNAME records (0 entries)
\nProcessed black-/whitelist group assignments (217 entries)
\nProcessed group (1 entry)
\nProcessed whitelist (exact) (206 entries)
\nProcessed whitelist (regex) (11 entries)
\nDone importing"}
3/23/2023, 3:22:55 PM: ⚠ Error: Failed to upload backup to "http://<IP_ADDRESS>:90/admin".

@mattwebbio  - weird - either error'ing silently or it's working but failing to respond, properly? Not really sure

Looks like they updated the message that a successful 'restore' completes with. Currently, Orbital is expecting it to end with 'Pi-hole blocking is enabled':
https://github.com/mattwebbio/orbital-sync/blob/cd2869ebe2153b08457d476d6c29de13666b553e/src/client.ts#L151

Fixed with version v1.5.2! Let me know if you continue to see this :)

Thx for the quick fix!


[react - useFloating] no way to control autoUpdate

Describe the bug A clear and concise description of what the bug is.
When using auto update with useFloating(), after initial mount, there is no way to turn it on or off.
I realize I could control it manually, but I kind of expect it to be a built in feature, like how the middleware have enabled: boolean.
const { refs, floatingStyles, context } = useFloating({
  // ...;
  whileElementsMounted: props.autoUpdate ? autoUpdate : undefined,
});

To Reproduce
CodeSandbox
Steps to reproduce the behavior:

Look at "my tooltip"

Expected behavior - Tooltip should switch between auto updating and stationary every 2 seconds.
Screenshots

Context:

OS: MacOs - 14.2.1
Browser Chrome
Version - 120

Yeah, it's due to whileElementsMounted being non-reactive so it doesn't check if it changes to undefined:
https://github.com/floating-ui/floating-ui/blob/77fe7480a1a3a201452fd7b993f75065ed6bbdc5/packages/react-dom/src/useFloating.ts#L75
Workaround as you mentioned is to set it up manually in an effect and avoid the whileElementsMounted option
useEffect(() => {
  if (isOpen && props.autoUpdate && elements.reference && elements.floating) {
    const cleanup = autoUpdate(
      elements.reference,
      elements.floating,
      update,
    );
    return cleanup;
  }
}, [isOpen, props.autoUpdate, elements, update]);

and I'm guessing you don't want to make it reactive in case consumers pass a function. hmmph.
maybe create a hook, useAutoUpdate()?
useAutoUpdate(context, { enabled: true, ...);

seems elegant enough, and it would make it possible to change the autoUpdate options

The option can be made reactive if it changes from a function to undefined, which useDismiss does for outsidePress, just needs a fix and doesn't require a separate hook


Storage problem in V3.17

https://github.com/heroiclabs/nakama/commit/06ed00f6c040000e3fa5915fb1f1820a6dae2d9d#r123822115

Fixed on master and will be part of the next release.

Your comment is on the read function, but you call write function and that's were error is generated.
I'll try to replicate this problem with arguments you've provided in the commenct. Which DB version do you use?


transactionId crash found when viewing transaction from >1d ago

Description
When reviewing data older than today we can still filter on data / links between app Servers, but when viewing the transactionList pinpoint reports in the UI "no data found".
The web-log reports following line:
web          | 2017-09-13 07:44:18 [INFO ](c.n.p.w.f.LinkFilter               :111) filterType:WAS_TO_UNKNOWN web          | 2017-09-13 07:44:18 [INFO ](c.n.p.w.f.LinkFilter               :116) acceptURLFilter:com.navercorp.pinpoint.web.filter.BypassURLPatternFilter@30c09948 web          | 2017-09-13 07:44:18 [INFO ](c.n.p.w.s.FilteredMapServiceImpl   :495) transactionId crash found. original:2989 filter:2368 crashKey:[
Environment

Pinpoint version: 1.6.1
OS, WAS, affected library, etc: Docker containers build by maven
Additional details (e.g. how your collector/web is set up): default container configuration

fixed with upgrade to current 1.7.0-snapshot


🐞 [Bug]: Cannot use grid_client pkg outside the ts-sdk

which package/s did you face the problem with?
grid_client
What happened?
when I installed the latest version of grid_client pkg 2.6.0-rc2 outside the ts-sdk and used the scripts/checkNodeAlive.ts script I got Error: Cannot find module '@threefold/monitoring'
Steps To Reproduce

create pkg outside ts-sdk
install the latest version of grid client 2.6.0-rc2
run any script

version
2.6.0-rc2
Relevant screenshots/screen records

Relevant log output
Error: Cannot find module '@threefold/monitoring'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /media/samar/DATA/github/threefoldtech/grid_client_pkg/scripts/checkNodeAlive.ts
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
    at Function.Module._resolveFilename.sharedData.moduleResolveFilenameHook.installedValue [as _resolveFilename] (/media/samar/DATA/github/threefoldtech/grid_client_pkg/node_modules/@cspotcode/source-map-support/source-map-support.js:811:30)
    at Function.Module._load (node:internal/modules/cjs/loader:920:27)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/media/samar/DATA/github/threefoldtech/grid_client_pkg/node_modules/@threefold/grid_client/dist/node/manageURLs.js:4:22)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Object.require.extensions.<computed> [as .js] (/media/samar/DATA/github/threefoldtech/grid_client_pkg/node_modules/ts-node/src/index.ts:1608:43)
    at Module.load (node:internal/modules/cjs/loader:1117:32) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    '/media/samar/DATA/github/threefoldtech/grid_client_pkg/scripts/checkNodeAlive.ts'
  ]
}
error Command failed with exit code 1.

Verified, Devnet @threefold/grid_client": "^2.6.0-rc3.
I tested the same scenario and a couple other scripts of the main functionality, like VM, and they all worked fine.

Add section with new created test cases: Grid Client NPM Package Contains 5 test cases


Query string not working for GET request

In zsh this works:
> curl 'https://qrng.anu.edu.au/API/jsonI.php?type=uint8&length=10'
{"type":"uint8","length":10,"data":[214,140,44,142,254,214,185,107,213,30],"success":true}

but this doesn't
> resty https://qrng.anu.edu.au/API
> GET /jsonI.php -q "type=uint8&length=10"
{"success":false}

It appears that resty quotes the ampersand:
> GET /jsonI.php -q "type=uint8&length=10" --dry-run
curl -sLv --data-binary '' -X GET -b "/home/me/.resty/c/qrng.anu.edu.au" -c "/home/me/.resty/c/qrng.anu.edu.au" "https://qrng.anu.edu.au/API/jsonI.php?type=uint8\&length=10"

am I doing something wrong?

Looks like it was introduced in commit e9559924. The line for opt in "$@"; do all_opts+=($(printf '%q' "$opt")) ; done results in '&' between query parameters being escaped to '&'
Example escape:
printf '%q' "p1=v1&p2=v2"

outputs 'p1=v1&p2=v2'


Clarity around user accounts vs contributor accounts

During the registration process for an OAR account, currently everyone needs to enter a contributor name/description, even if they're just downloading data. It would be nice to think through these user flows so not everyone gets put into the "contributor" category.

@hlennett , i'm not moving this because we have some work on the roadmap around restructuring account admin.


Support for "modern" CMake handling of installed SDK missing

Would it be please possible to add support for the "modern" CMake way of working with the installed[1] SDK, i.e.

identify components (api headers, cxx headers, icd loader)
provide *Targets.cmake and *Config.cmake file(s) for the components and
expose targets for working within CMake with the imported SDK

Furthermore, I would have expected that the "make install" handles the installation of all sub-modules (i.e. especially the headers, at least api and cxx) as well. Thank you for considering this!
[1]OTOH, there is no mention in the README about make install so maybe this is intentional? Just a thought.

This is WIP, in fact it's done and I've had it in a PR until it fell victim to the master >> main transition. This work spans across 4 repos (Headers, CLHPP, ICD-Loader, SDK), so it requires coordinated action, but rest assured that it's 90% done and as soon as I get around to it (it also touches upon significantly improving our CI coverage, as breaking away from existing Find Module detection in backwards compatible manner is tricky and requires extensive testing). It's mostly work done, but polish is essential.
I'll update you once a PRs are in flight again.

Thank you for your quick update & your efforts, they are very much appreciated! I would have otherwise tried to take a stab at this in the near future (had something cobbled together for the cxx headers locally which clashed with the changes introduces leading up to the OpenCL 3.0 release, never got around to the other components),  but given the complexity you outlined and the importance, its great that you are already mostly done!
Cheers,
Martin

Is this perchance why the headers are missing from the install directory after a cmake --install? no errors are logged during build or install, cmake simply never copies them (/lib, /bin and the exe's are however).

The headers work has been merged but is not yes referenced by this project using package config syntax. You are welcome to contribute, or wait until I (or someone) gets around to merging the same feature to the ICD and the CLHPP packages.
As I said it's a big change and requires extensive testing, some of which has already been merged into the other projects. I got limited time, but am making slow and steady progress. (End of year isn't about burning through GitHub issues. Here's to forgetting a ton about 2020 🍾)

The headers work has been merged but is not yes referenced by this project using package config syntax. You are welcome to contribute, or wait until I (or someone) gets around to merging the same feature to the ICD and the CLHPP packages.
As I said it's a big change and requires extensive testing, some of which has already been merged into the other projects. I got limited time, but am making slow and steady progress. (End of year isn't about burning through GitHub issues. Here's to forgetting a ton about 2020 🍾)

Is it currently expected to use the source directory for the 'install'? ie just build and reference the source directory ('OpenCL-SDK') directly for headers and lib?
I haven't yet been able to use the SDK as the config.cmake files are never generated on build or install, so cmake has no idea where anything even is when you try to find_package(OpenCL or OpenCL-SDK).
I also suggest as well that the names 'OpenCL and 'OpenCL-SDK' be stripped out, and just use 'OPENCL' instead in all caps. Obviously this is a library so the '-SDK' part is pointless and only confuses the matter inside cmake...

Is it currently expected to use the source directory for the 'install'? ie just build and reference the source directory ('OpenCL-SDK') directly for headers and lib?
I haven't yet been able to use the SDK as the config.cmake files are never generated on build or install, so cmake has no idea where anything even is when you try to find_package(OpenCL or OpenCL-SDK).
I also suggest as well that the names 'OpenCL and 'OpenCL-SDK' be stripped out, and just use 'OPENCL' instead in all caps. Obviously this is a library so the '-SDK' part is pointless and only confuses the matter inside cmake...

@Vectrobe The plan on how OpenCL as an API will be consumed in the "modern" way is layed out here, in the initial comment of this PR that started the work.
Referencing the source tree will not be needed. You install the SDK and point CMAKE_PREFIX_PATH to your install root, as would be expected.

I also suggest as well that the names 'OpenCL and 'OpenCL-SDK' be stripped out, and just use 'OPENCL' instead in all caps. Obviously this is a library so the '-SDK' part is pointless and only confuses the matter inside cmake...

Naming the repo is as is ,the cost of changing the name is more than the benefit of "I like it better that way". There has to be tangible benefits for such a change to occur. (I personally have no aesthetic issue with it. From a practical standpoint "OpenCL" may have been a more comfortable from a CMake perspective, but naming repos to please tools is backwards.) From a bikeshedding perspective, it is very much an SDK, not OpenCL itself. Plans are (as can be seen from the issues list) that there is an SDK library being designed aiming to take some of the tedium out of common OpenCL related tasks.
Do note (as described by the linked PR comment) that there are many things to consider, backward compatibility being a major thing. Existing
find_package(OpenCL REQUIRED)
...
target_link_libraries(${PROJECT_NAME} OpenCL::OpenCL)

scripts have to work. Breaking build scripts comes at a huge cost (manpower, losing users, etc.). I personally dislike how the SDK (all the components required to build an OpenCL app) are broken into multiple repos, but these repos have existed the way they do since the dawn of time and Linux distro maintainers have scripted to consuming them this way. The SDK has to live with the fact that the SDK needs to be installed from multiple sub-projects. The "confusion" is further aggravated by the fact that the ICD loader is called libOpenCL.so/OpenCL.dll which isn't strictly OpenCL, there are other components needed to compile an application using the C++ bindings for eg.
The targets and names as described in the (IMHO, and those of the approvers) strike a good balance between backward compat, modern and feature complete. Please keep in mind there is hidden complexity. Taking everyone from CMake modules to CMake packages in a group of repos with a decade of history without leaving anyone behind is a feat. We strive to do just that.

@Vectrobe The plan on how OpenCL as an API will be consumed in the "modern" way is layed out here, in the initial comment of this PR that started the work.
Referencing the source tree will not be needed. You install the SDK and point CMAKE_PREFIX_PATH to your install root, as would be expected.

I also suggest as well that the names 'OpenCL and 'OpenCL-SDK' be stripped out, and just use 'OPENCL' instead in all caps. Obviously this is a library so the '-SDK' part is pointless and only confuses the matter inside cmake...

Naming the repo is as is ,the cost of changing the name is more than the benefit of "I like it better that way". There has to be tangible benefits for such a change to occur. (I personally have no aesthetic issue with it. From a practical standpoint "OpenCL" may have been a more comfortable from a CMake perspective, but naming repos to please tools is backwards.) From a bikeshedding perspective, it is very much an SDK, not OpenCL itself. Plans are (as can be seen from the issues list) that there is an SDK library being designed aiming to take some of the tedium out of common OpenCL related tasks.
Do note (as described by the linked PR comment) that there are many things to consider, backward compatibility being a major thing. Existing
find_package(OpenCL REQUIRED)
...
target_link_libraries(${PROJECT_NAME} OpenCL::OpenCL)

scripts have to work. Breaking build scripts comes at a huge cost (manpower, losing users, etc.). I personally dislike how the SDK (all the components required to build an OpenCL app) are broken into multiple repos, but these repos have existed the way they do since the dawn of time and Linux distro maintainers have scripted to consuming them this way. The SDK has to live with the fact that the SDK needs to be installed from multiple sub-projects. The "confusion" is further aggravated by the fact that the ICD loader is called libOpenCL.so/OpenCL.dll which isn't strictly OpenCL, there are other components needed to compile an application using the C++ bindings for eg.
The targets and names as described in the (IMHO, and those of the approvers) strike a good balance between backward compat, modern and feature complete. Please keep in mind there is hidden complexity. Taking everyone from CMake modules to CMake packages in a group of repos with a decade of history without leaving anyone behind is a feat. We strive to do just that.

Naming the repo is as is

Oh no I didn't mean the name of the repo at all, just the cmake naming.
Currently we have project(OpenCL-SDK), target_properties(OpenCL ...), OPENCL_SDK_INCLUDE_DIRS, meanwhile other projects have required OPENCL_INCLUDE_DIR, OPENCL_DIR, (nvidia), and cmake had its own FindOpenCL using OpenCL_INCLUDE_DIRS, and so on.
The main point being that most existing projects use OpenCL for the project import, and OPENCL_... for the definitions. The current cmake config uses OpenCL-SDK and OPENCL_SDK_..., which breaks that.

Naming the repo is as is

Oh no I didn't mean the name of the repo at all, just the cmake naming.
Currently we have project(OpenCL-SDK), target_properties(OpenCL ...), OPENCL_SDK_INCLUDE_DIRS, meanwhile other projects have required OPENCL_INCLUDE_DIR, OPENCL_DIR, (nvidia), and cmake had its own FindOpenCL using OpenCL_INCLUDE_DIRS, and so on.
The main point being that most existing projects use OpenCL for the project import, and OPENCL_... for the definitions. The current cmake config uses OpenCL-SDK and OPENCL_SDK_..., which breaks that.

Please, disregard the current use of OpenCL_SDK_... variables. They are hotfixes to make the SDK compile. Those parts will disappear once I get around all the repos. Rest assured, I'm making some progress today on the ICD-Loade repo. No promises. You can follow the progress here.

Please, disregard the current use of OpenCL_SDK_... variables. They are hotfixes to make the SDK compile. Those parts will disappear once I get around all the repos. Rest assured, I'm making some progress today on the ICD-Loade repo. No promises. You can follow the progress here.


Questions regarding Pose Detection custom training on Model Maker [not bug]

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
No
OS Platform and Distribution
N/A
Python Version
N/A
MediaPipe Model Maker version
No response
Task name (e.g. Image classification, Gesture recognition etc.)
Pose Detection
Describe the actual behavior
Ability to custom train pose detection model
Describe the expected behaviour
Unable to find steps
Standalone code/steps you may have used to try to get what you need
Hey everyone, I was reviewing the new Model Maker approach for custom training the models and was looking to get some answers around pose detection specifically as I wasn't able to find the exact documentation for it. Any help would be appreciated!

How can we train the Pose detection model using the Model Maker? Is it possible?

One of the requirements for the current pose detection is the presence of a face. Is there a possibility to train the network without this requirement?

If not (2), is there a keypoint detection network that I could train with my custom data?

The model works with 3D keypoints. Would it be possible to train it on a 2D output, in hopes of getting higher FPS (on older devices)

Thanks!
Other info / Complete Logs
No response

Hi @abhinavchawla13,
Currently, our re-trainable capabilities include Objection Detection, Image Classification, Gesture Recognition, Face Stylization, Image Generation, and Text Classification as outlined in the documentation.
However, we appreciate your interest in expanding these capabilities. We will categorise this as a feature request and share it with our team. The prioritisation of this request will be determined through internal discussions aligning with team priorities. We will keep you informed of any updates regarding the potential inclusion of this feature.
Thank you!

Hi @abhinavchawla13 ,
(1) Thanks for raising this request. Unfortunately the team does not have bandwidth currently to add custom Pose Recognition. Your best bet would be to implement something similar to the Gesture Recognizer pipeline: https://github.com/google/mediapipe/tree/master/mediapipe/model_maker/python/vision/gesture_recognizer.
(2) I don't think the Pose Landmark Detection model requires a face to be present. The live demo here: https://mediapipe-studio.webapps.google.com/studio/demo/pose_landmarker works even when my face is outside the camera frame. The documentation for this model is here: https://developers.google.com/mediapipe/solutions/vision/pose_landmarker.
(4) Short answer is no. The provided pose landmark detection network cannot be re-trained and would be used only for data pre-processing in training a custom Pose recognizer model.

Thanks @joezoug, for (2), I saw in the model card that it had mentioned "Head is not visible" in out of scope applications. It does seem to sometimes work well when face isn't there, but other times also gets really confused. I think blazepose uses face detector if possible, as defined in the paper.
Either ways, hoping we can train the model on our own dataset soon. Thanks for the replies (also, @kuaashish)!

Np, happy to help! I will close the issue now.

Np, happy to help! I will close the issue now.


Network Section does not clearly talk about IP Firewall for Managed DBs

In NS section (https://learn.microsoft.com/en-us/security/benchmark/azure/baselines/sql-database-security-baseline#network-security) spends a lot of time telling us what an Azure SQL Managed database cannot be protected with. However, not a lot of time is spent on the built in IP firewall.
Yet, in PV-1 (https://learn.microsoft.com/en-us/security/benchmark/azure/baselines/sql-database-security-baseline#pv-1-establish-secure-configurations-for-azure-services) it is mentioned.
An azure customer looking for how to protect their Managed DBs and wish a defence-in-depth approach on how to restrict network level access would be forgiven by missing the IP Firewall component because the security baseline does not clearly describe it in the networking section.
If they are lucky they may stumble into https://learn.microsoft.com/en-us/azure/azure-sql/database/secure-database-tutorial?view=azuresql#create-firewall-rules which does clearly define what it is and does.

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

ID: 2561cc3d-996d-fb20-3bee-8bf0513e3cd4
Version Independent ID: 20471c47-d5ca-5c19-5fcf-3c19cdc5525b
Content: Azure security baseline for Azure SQL Database
Content Source: benchmark/azure/baselines/sql-database-security-baseline.md
Service: sql-database
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@garthoid
Thanks for your feedback! We will investigate and update as appropriate.

Hi @msmbaldwin,
Could you please look into this question. Thank you

Hi, @garthoid. The SQL Database baseline was completely rewritten to the new Microsoft Cloud Security Benchmark.  See Azure security baseline for Azure SQL: Network Security for the sections that specifically speak to the utility of firewalls.
Thank you for your feedback, we appreciate it!  #please-close


Upgrader shows the need to upgrade even on upgrade command

❯ protostar upgrade
10:49:05 [INFO] Running upgrade of protostar
10:49:05 [INFO] Looking for a new version ...
10:49:05 [INFO] Starting upgrade from version 0.3.1 to version 0.3.3
10:49:05 [INFO] Pulling latest binary, version: 0.3.3
10:49:09 [INFO] Installing latest Protostar version: 0.3.3
10:49:09 [INFO] Cleaning up after installation
10:49:09 [INFO] Upgraded successfully
10:49:10 [INFO] A new Protostar version is available: 0.3.3.
Changelog: https://github.com/software-mansion/protostar/releases/tag/v0.3.3
To install the latest Protostar version, run protostar upgrade

wasn't this fixed? @Arcticae

@Arcticae did it


Unnamed default exports don't work with --t es6 --m commonjs

Compiling the following code:
"use strict";
export default class {};

Using the command line tsc --t es6 --m commonjs produces illegal JavaScript:
"use strict";
class {
}
exports.default = default_1
;

I realize this is a weird combination of switches, however it seems necessary to target current versions of Node.js/V8 that don't yet natively support ES6 modules.

This conditional needs to be updated to emit the temp name if the class is an exported default class when not targeting ES6. Forgot about unnamed classes when adding tests in #5648.
While looking at it, it would probably also be a good idea to verify all of the results with functions and unnamed function expressions as well...

same as unnamed function.
$ tsc -v
Version 1.8.0-dev.20151130
$ cat sub.ts
export default function (name: string) {
    return `Hi! ${name}`;
}
$ tsc --target es6 --module commonjs sub.ts
$ cat "use strict";
function (name) {
    return `Hi! ${name}`;
}
exports.default = default_1;

This also appears to be a problem with named classes that are default exports.
$ tsc -v
message TS6029: Version 1.7.3

example.ts
// example.ts
export default class Example {
    public get() {
        return 1;
    }
}

subExample.ts
// subExample.ts
import Example from "./example";

export default class SubExample extends Example {
    public get() {
        return 3;
    }

    public foo() {
        return 2;
    }
}

$ tsc -t es6 -m commonjs example.ts subExample.ts

example.js
// example.js
class Example {
    get() {
        return 1;
    }
}
exports.Example = Example;

subExample.js
// subExample.js
var example_1 = require("./example");
class SubExample extends example_1.default {
    get() {
        return 3;
    }
    foo() {
        return 2;
    }
}
exports.SubExample = SubExample;

When run with node v5:
TypeError: Class extends value undefined is not a function or null
    at Object.<anonymous> (subExample.js:3:35)

That last bit duplicates #5594 and should be fixed in master. However your original issue still stands.

@joeduffy and @nmalaguti can you give typescript@next a try tomorrow and let us know if the issue has been resolved.

Thanks all, that was fast!  I'll give it a try in the AM.

This has resolved the issue with default named classes that I was seeing on 1.7 when using ts@next.
How does this interact with libraries compiled to commonjs using babel?

LGTM, works great for me.

How does this interact with libraries compiled to commonjs using babel?

not sure i understand the question.

@mhegazy when babel emits code for es6 imports, it includes a method that looks for __esModule to determine whether to wrap the import in an object defining a default:
"use strict";

Object.defineProperty(exports, "__esModule", {
    value: true
});

var _example = require("./example");

var _example2 = _interopRequireDefault(_example);

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

class SubExample extends _example2.default {
    get() {
        return 3;
    }

    foo() {
        return 2;
    }
}
exports.default = SubExample;

If example.ts in my comment above is compiled with TypeScript, and subExample.ts is compiled with babel (simulating a babel project calling a TypeScript compiled project), then the compiled code for subExample.ts above breaks.
class SubExample extends _example2.default {
                                  ^

TypeError: Class extends value #<Object> is not a function or null
    at Object.<anonymous> (/Users/nmalaguti/git/ts-es6-commonjs/subExample.js:15:35)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/Users/nmalaguti/git/ts-es6-commonjs/test.js:2:20)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)

The variable _example is { default: { default: [Function: Example] } } because __esModule was not set on it.
Is there a plan for how these will interop in the future?

Even if there isn't right now, as a workaround on your TS modules you can add the __esModule exported member yourself to force babel into doing the right thing with its interop require.

@nmalaguti i think there is something else going on here. TypeScript compiler will emit the "__esModule", so compileing your example.ts results in:
// example.ts
var Example = (function () {
    function Example() {
    }
    Example.prototype.get = function () {
        return 1;
    };
    return Example;
})();
Object.defineProperty(exports, "__esModule", { value: true });
exports.default = Example;

@mhegazy it looks like you targeted es5, not es6 (since the class was compiled into a function). The issue is when targeting es6 and using commonjs modules, the "__esModule" isn't emitted.

I thought you were passing the es6 output into Babel...

Sorry for the confusion. The use case would be I write an npm module in TypeScript with ES6 features like generators. I use tsc -t es6 -m commonjs to compile and publish.
A consumer of my library npm installs it and wants to use it with babel in order to take advantage of ES6 features. In that case, when they import my module as a default, babel will compile that down in a way that is incompatible since "__esModule" is missing in the TypeScript output.

Ah! So the issue is that we don't emit our __esModule shim when targeting ES6 with nonES6 modules! I see!

i have a fix out for this one: https://github.com/Microsoft/TypeScript/pull/5907

Oh man, I just put out #5908 with almost the same change.

great mind..

@nmalaguti give typescript@next a try later tonight and let us know if you are still running into issues.

Thanks @mhegazy and @weswigham. I was able to get things working smoothly with typescript@next.

Hum this was closed but I have the following problem :
My TS file :
'use strict'

import {Request, Response} from 'express'
import Controller from 'trails-controller'

/**
 * @module DefaultController
 *
 * @description Default Controller included with a new Trails app
 * @see {@link http://trailsjs.io/doc/api/controllers}
 * @this TrailsApp
 */
export default class DefaultController extends Controller {
  app: any;
  /**
   * Return some info about this application
   */
  info(req: Request, res: Response) {
    res.status(200).json(this.app.services.DefaultService.getApplicationInfo())
  }
}

The compiled result :
'use strict';
const trails_controller_1 = require('trails-controller');
class DefaultController extends trails_controller_1.default {
    info(req, res) {
        res.status(200).json(this.app.services.DefaultService.getApplicationInfo());
    }
}
Object.defineProperty(exports, "__esModule", { value: true });
exports.default = DefaultController;

How can I remove .default added in the extends and exports ? Because they not working in v8 I expect this output :
'use strict';
const trails_controller_1 = require('trails-controller');
class DefaultController extends trails_controller_1 {
    info(req, res) {
        res.status(200).json(this.app.services.DefaultService.getApplicationInfo());
    }
}
module.exports = DefaultController;

I wil have to look at the trails-controler definition to be able to help. You are importing it as a default export, so the output is what I would expect.

@mhegazy thanks. trails-controller is a node third module, a simple class :
'use strict'

/**
 * Trails Controller Class.
 */
module.exports = class TrailsController {

  constructor (app) {
    Object.defineProperty(this, 'app', {
      enumerable: false,
      value: app
    })
  }

  /**
   * Controller configuration
   */
  static config () {
  }

  /**
   * Return the id of this controller
   */
  get id () {
    return this.constructor.name.replace(/(\w+)Controller/, '$1').toLowerCase()
  }

  get log () {
    return this.app.log
  }

  get __ () {
    return this.app.__
  }
}

If this module doesn't export his class the right way, what is the right way to export it ? I'll make a PR on it.
https://github.com/trailsjs/trails-controller

your import should look like import Controller = require("trails-controller"); instead.
the reason is import Controller from 'trails-controller' imports the default export of the module, and this module is a pre-ES6 module, i.e. it does not have a default export.

@mhegazy thanks ! That's working (with "noLib": true,) because if I remove this flag it doesn't know about trails-controller. I try to create a .d.ts file but can't manage how to declare the class correctly :(
I try :
declare module "trails-controller" {
  export default class Controller {
    app: any
  }
}

With or without default I get ViewController.ts(27,47): error TS2507: Type 'typeof "trails-controller"' is not a constructor function type.

class Controler {...}
export=Controler;

I'm trying to write a definition for the trails-controller that @jaumard mentioned, but I lack the experience.  Is this something close?
declare module TrailsController {
  export class TrailsController {
    app: {
      config: any;
      sitemap: any;
      routes: { path: string, config: {app?: any} }[];
      services: any;
    };
    log: any;
    id: any;
    __: any;
    config: any;

    constructor(app: any);
  }
}
declare module "trails-controller" {
  export = TrailsController;
}

General questions should be on StackOverflow, Gitter or IRC, but the following works:
declare namespace TrailsController {
  class TrailsController {
    app: {
      config: any;
      sitemap: any;
      routes: { path: string, config: {app?: any} }[];
      services: any;
    };
    log: any;
    id: any;
    __: any;
    config: any;

    constructor(app: any);
  }
}

declare module "trails-controller" {
  const TrailsController: TrailsController.TrailsController;
  export = TrailsController;
}


Fix certain failing 2.13 tests [DO NOT MERGE YET]

Making a PR to kick of Travis. The one 2.13 test fix that isn't in here involves Future, but the tests all pass for me on the JVM. Will try JS and Native now.

Travis was happy. Closing this now.


Run Xcode command lines tools in native ARM

Description
On macOS ARM machines run Xcode outside Rosetta without x86 translation by prepending commands with arch -arm64.
Only update the iOS xcodebuild code paths.  More research needed to see what changes flutter build macos needs.
Related Issues
Fixes https://github.com/flutter/flutter/issues/65133
Tests
xcrun runs natively on arm64 test, updated xcrun tests.
Breaking Change

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

@alexmarkley I know you've been offering to help out with ARM support.  If you are still willing, it would be awesome if you could to take this change for a test drive and see where else the flutter command line tool falls down when running against a physical iOS device...

@jmagman thanks for tagging me! I will take a look later tonight.

@jmagman first impressions. Ran flutter upgrade in flutter channel master. Here's the output of flutter doctor -v:
DTK:~ alex$ flutter doctor -v
[✓] Flutter (Channel master, 1.23.0-19.0.pre.41, on macOS 11.0 20A5395g darwin-arm, locale en-US)
    • Flutter version 1.23.0-19.0.pre.41 at /Users/alex/Development/Flutter/flutter
    • Framework revision ed2a4809da (17 minutes ago), 2020-10-14 20:02:04 -0400
    • Engine revision ce75dda492
    • Dart version 2.11.0 (build 2.11.0-218.0.dev)

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

⣽Error executing simctl: 1
arch: posix_spawnp: xcrun: Bad CPU type in executable

[!] Xcode - develop for iOS and macOS (Xcode 12.2)
    • Xcode at /Applications/Xcode-beta.app/Contents/Developer
    • Xcode 12.2, Build version 12B5035g
    ✗ Xcode requires additional components to be installed in order to run.
      Launch Xcode and install additional required components when prompted or run:
        sudo xcodebuild -runFirstLaunch
    • CocoaPods version 1.9.3

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] Connected device (1 available)
    • macOS (desktop) • macos • darwin-x64 • macOS 11.0 20A5395g darwin-arm

! Doctor found issues in 3 categories.
DTK:~ alex$

Not sure what's going on with simctl. Running xcrun simctl --help yields:
DTK:~ alex$ xcrun simctl --help
usage: simctl [--set <path>] [--profiles <path>] <subcommand> ...
       simctl help [subcommand]
Command line utility to control the Simulator

For subcommands that require a <device> argument, you may specify a device UDID
or the special "booted" string which will cause simctl to pick a booted device.
If multiple devices are booted when the "booted" device is selected, simctl
will choose one of them.

Subcommands:
	create              Create a new device.
	clone               Clone an existing device.
	upgrade             Upgrade a device to a newer runtime.
	delete              Delete spcified devices, unavailable devices, or all devices.
	pair                Create a new watch and phone pair.
	unpair              Unpair a watch and phone pair.
	pair_activate       Set a given pair as active.
	erase               Erase a device's contents and settings.
	boot                Boot a device.
	shutdown            Shutdown a device.
	rename              Rename a device.
	getenv              Print an environment variable from a running device.
	openurl             Open a URL in a device.
	addmedia            Add photos, live photos, videos, or contacts to the library of a device.
	install             Install an app on a device.
	uninstall           Uninstall an app from a device.
	get_app_container   Print the path of the installed app's container
	install_app_data    Install an xcappdata package to a device, replacing the current contents of the container.
	launch              Launch an application by identifier on a device.
	terminate           Terminate an application by identifier on a device.
	spawn               Spawn a process by executing a given executable on a device.
	list                List available devices, device types, runtimes, or device pairs.
	icloud_sync         Trigger iCloud sync on a device.
	pbsync              Sync the pasteboard content from one pasteboard to another.
	pbcopy              Copy standard input onto the device pasteboard.
	pbpaste             Print the contents of the device's pasteboard to standard output.
	help                Prints the usage for a given subcommand.
	io                  Set up a device IO operation.
	diagnose            Collect diagnostic information and logs.
	logverbose          enable or disable verbose logging for a device
	status_bar          Set or clear status bar overrides
	ui                  Get or Set UI options
	push                Send a simulated push notification
	privacy             Grant, revoke, or reset privacy and permissions
	keychain            Manipulate a device's keychain
DTK:~ alex$

Seems like the simctl issue is preventing flutter from detecting physical devices plugged into the machine. Flutter doctor reports "No devices available" and flutter run in a hello world project yields:
DTK:helloWorldThree alex$ flutter run
Error executing simctl: 1
arch: posix_spawnp: xcrun: Bad CPU type in executable

No supported devices connected.
DTK:helloWorldThree alex$

@jmagman uh oh, this is tricky:
DTK:~ alex$ xcrun simctl --version
@(#)PROGRAM:simctl  PROJECT:CoreSimulator-7<IP_ADDRESS>
DTK:~ alex$ /Applications/Xcode-beta.app/Contents/Developer/usr/bin/simctl --version
@(#)PROGRAM:simctl  PROJECT:CoreSimulator-7<IP_ADDRESS>
DTK:~ alex$ arch -arm64 /Applications/Xcode-beta.app/Contents/Developer/usr/bin/simctl
arch: posix_spawnp: /Applications/Xcode-beta.app/Contents/Developer/usr/bin/simctl: Bad CPU type in executable
DTK:~ alex$ lipo -detailed_info /Applications/Xcode-beta.app/Contents/Developer/usr/bin/simctl
fatal error: /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: can't figure out the architecture type of: /Applications/Xcode-beta.app/Contents/Developer/usr/bin/simctl
DTK:~ alex$ file /Applications/Xcode-beta.app/Contents/Developer/usr/bin/simctl
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/simctl: Bourne-Again shell script text executable, ASCII text
DTK:~ alex$
DTK:~ alex$
DTK:~ alex$ head -n 5 /Applications/Xcode-beta.app/Contents/Developer/usr/bin/simctl
#!/bin/bash
DEVELOPER_USR_BIN_DIR=${0%/*}
DEVELOPER_USR_BIN_DIR=${DEVELOPER_USR_BIN_DIR%/local/bin}
DEVELOPER_USR_BIN_DIR=${DEVELOPER_USR_BIN_DIR%/bin}
DEVELOPER_USR_BIN_DIR=${DEVELOPER_USR_BIN_DIR}/bin
DTK:~ alex$

Oh! @jmagman I think you want this:
DTK:~ alex$ arch -arm64e xcrun simctl --version
@(#)PROGRAM:simctl  PROJECT:CoreSimulator-7<IP_ADDRESS>
DTK:~ alex$

As per this:
DTK:~ alex$ lipo -info /usr/bin/xcrun
Architectures in the fat file: /usr/bin/xcrun are: x86_64 arm64e
DTK:~ alex$

This leads to some interesting behavior like this (running inside of iTerm, which is running under Rosetta):

Hm, I was trying to figure out where arm64e was needed... on my dtk it only worked with -arm64 not -arm64e
On this commit flutter run works:

and flutter devices:

@jmagman that is somewhat baffling. I am on Beta 10 as of this afternoon, I wonder if that could factor in somehow?
I assume Apple's intention in the long term is for the xcrun to spawn ARM processes because the caller is also an ARM process. I guess that's not going to be possible with Dart in the short term?

@jmagman are you still running the image that it shipped with? https://betawiki.net/wiki/MacOS_Big_Sur_build_20A5299w
I noticed some pretty significant changes around Beta 7 and following, so maybe an update is in order. 😉


Downgrade jsoniter to 2.13.5 to restore support for JDK 8

To unblock updating bsp in bloop I downgrade jsoniter to version 2.13.5 which support JDK 8.
Apply suggestion from https://github.com/scalacenter/bloop/pull/1845#issuecomment-1307234632.

Guys, please just help me in patching of https://github.com/sbt/sbt-multi-release-jar for working with JDK 11 and crossproject sbt plugins, and then I will release jars that works on JDK 8+ without performance loss on JDK 11+.

Guys, please just help me in patching of https://github.com/sbt/sbt-multi-release-jar for working with JDK 11 and crossproject sbt plugins, and then I will release jars that works on JDK 8+ without performance loss on JDK 11+.

I think it's not really an issue with  dropping JDK 8 as we should start dropping it and not waste time on maintaining everything for JDK 8, it's perfectly sensible that you dropped the support. We need to fix a couple of things first and then we would also drop JDK 8 support in Bloop.

How about pinning this inside bloop?

The jsoniter from bsp4s is used transitively in bloop, so we don't have to pin jsoniter inside of bloop.

How about pinning this inside bloop?

@tpasternak The jsoniter from bsp4s is used transitively in bloop, so we don't have to pin jsoniter inside of bloop.

We should do an override then, @tpasternak idea is that it will be easier for Bloop to just remove the override than doing the BSP release once more

@tgodzik wrote:

I think it's not really an issue with dropping JDK 8 as we should start dropping it and not waste time on maintaining everything for JDK 8, it's perfectly sensible that you dropped the support. We need to fix a couple of things first and then we would also drop JDK 8 support in Bloop.

Isn't the whole point of this project to support build tools to implement BSP? And isn't it in the nature of build tools that they need to play well on both edges of the version spectrum, newest JDK as well as oldest one that still gets security updates? Dropping support for JDK 8 means, tools like Mill, that provide BSP with the help of this very project, are forced to find an alternative solution to provide BSP for its users.
What is this huge benefit we get from dropping JDK 8 support, that adjusts such a cut?

Guys, I'm ready to cut a version with multi-release JAR that can run on JDK 8 and support all future updates. Please just help me hack the build.sbt to pack that kind of JAR for JVM sub-modules.

@tgodzik wrote:

I think it's not really an issue with dropping JDK 8 as we should start dropping it and not waste time on maintaining everything for JDK 8, it's perfectly sensible that you dropped the support. We need to fix a couple of things first and then we would also drop JDK 8 support in Bloop.

Isn't the whole point of this project to support build tools to implement BSP? And isn't it in the nature of build tools that they need to play well on both edges of the version spectrum, newest JDK as well as oldest one that still gets security updates? Dropping support for JDK 8 means, tools like Mill, that provide BSP with the help of this very project, are forced to find an alternative solution to provide BSP for its users.
What is this huge benefit we get from dropping JDK 8 support, that adjusts such a cut?

Dropping JDK 8 would just be for Bloop. And we would still compile with the correct version, either via forked JVM for Java files, which already happens, or via the additional flags to make sure Scala code correctly compiles for a given JDK version.
As for BSP, the Scala version is only used by Bloop and bsp4j works correctly with Java 8. Unless lsp4j library decides to drop the support at some point, which already happening to some other eclipse foundation libraries.

Guys, I'm ready to cut a version with multi-release JAR that can run on JDK 8 and then support all future updates. Please just help me hack the build.sbt to pack that kind of JAR for the jsoniter-scala-coreJVM sub-module.

Would love to help, but I think I know very little about sbt. Maybe the sbt channel on discord would be of help? Eugene should be very active there.

How about pinning this inside bloop?

I have already overridden version of jsoniter in bloop - https://github.com/scalacenter/bloop/pull/1845.  So I will close this PR, because after discussion changes in bsp are not required.


Updating project to use pyansys/actions and remove requirement files

As title says. Tasks:

[x] Remove requirement files in favor of pyproject.toml requirements definitions
[x] Adapt workflow to use pyansys/actions
[ ] Check everything is working correctly

Codecov Report

Merging #42 (59817b4) into main (62d67c6) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 59817b4 differs from pull request most recent head c2ce525. Consider uploading reports for the commit c2ce525 to get more accurate results

@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   96.87%   96.87%
=======================================
  Files           3        3
  Lines          64       64
=======================================
  Hits           62       62
  Misses          2        2

Impacted Files
Coverage Δ

src/ansys/tools/versioning/utils.py
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Updates for FT 1.0.0

Implementes multiple changes for compatibility with the upcoming Featuretools 1.0.0 release.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Why there is one single _theming.scss?

Bug, feature request, or proposal:
What's the reasoning behind having one single theme helper sass file.
For example we do not use material palettes. We created our own, even if it's not following the material styleguide we set up several palettes and using them through the material theme framework. It's not a big deal but It looks odd to run the compiler through those vars never used.
I propose to move the palette variables out in a separate file and only import it if it's needed.
Another thing would be to let users extend/alter the foreground and background maps when creating new themes
I understand that angular material closely follows google's material styleguide, but I think with a few tweaks in can be made easier to use other colors as well. Today is a bit tricky.
thanks
What is the expected behavior?
What is the current behavior?
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
Is there anything else we should know?

Because we don't preserve the source file structure in the release package, which the imports for individual files are relative to.

Do you intend to break theme? Maybe in the CDK, or offer a more flexible way to theme? I managed to create a framework on the top of the theming, but I think it would nicer to offer a bit more on this.


Finalize weak coin implementation

Motivation

Closes #

Changes

vrf proposals are made based on units of spacetime

For this message is extended with Unit uint64 and included when computing signature.
Miner broadcast only smallest proposal if the has more than 1 unit.

messages for next rounds are buffered and used when the round is started

changed interface for the WeakCoin

Test Plan

TODO

[ ] Explain motivation or link existing issue(s)
[ ] Test changes and document test plan
[ ] Update documentation as needed

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

I think there is still work that needs to be done to interact with tortoise beacon in a correct way.


tech debt - consider reverting Literal workaround for pydantic bug

Is your feature request related to a specific problem?
https://github.com/ethyca/fideslang/pull/109 had a workaround for a pydantic bug. we should consider reverting this workaround in due course, if possible, just to clear out tech debt.
Describe the solution you'd like
will the underlying bug(s) have been addressed at a certain point so that we can revert the change?
Describe alternatives you've considered, if any
keep the workaround in place
Additional context
keeping track of tech debt 😄

moving to done


Add basic CRA example

Added CRA example as suggested in #21

Although the build didn't pass, this looks good to me. Thank you so much!
@all-contributors please add @etc-tiago for example!


Docs fix on similarity vs similar

Fixed similar vs similarity in docs
Upstreaming knowledge of embeddings from https://github.com/promptfoo/promptfoo/issues/146#issuecomment-1722085670

nice catch!


Clean up code

There is a lot of code that is no longer used should be cleaned up

code has been updated - Some commenting is still necessary and there is a page with lots of commented out items that are to be put to use in the future


Global access of squids is generally not good

I think that global access to squids is generally a bad idea.  If global caching is needed, using the Cloudflare CDN through something like openhtc.io is much more effective and simpler to operate.
Could disclaimers be put into the shoal documentation and configuration files to this effect?  (I assume you would not be willing to disable the designation completely at this point.)
The WLCG does operate two pairs of squids at FNAL and CERN that are globally accessible but they are not for normal operation, they are for catching failures of squids elsewhere, so they don't get put into any auto discovery service.

How would you access the cvmfs content via openhtc.io?
To have a global access for a squid is not necessarily a bad idea since what can be retrieved through the squid is limited in the squid configuration, usually limited to the major experiments cvmfs content and blocked for all other requests.
It is helpful to have a view global squids that can be used when there is nothing else close by, especially when running on different clouds. While it is preferred to have a squid in each cloud, squids on  VMs running in such clouds need to be always up but are not due to different issues with the cloud infrastructure or specific hypervisors.
Since the squid system and cvmfs in general is used by more than just CERN experiments, global squids provide a general fallback solution in case nearby or site squids are down.
The fallback squids at FNAL and CERN are not configured by default in cernvm or cvmfs as far as I am aware of, but are a fallback coded inside of experiments framework, aren't they? Are they available to non-CERN experiments?

How would you access the cvmfs content via openhtc.io?

We define names for all the stratum 1s there and set CVMFS_SERVER_URL to those aliases.  Then Cloudflare caches all the content in their huge network of caches worldwide.  We use the Cloudflare free tier.  @rptaylor has a separate Cloudflare domain for Compute Canada.
See for example the global configuration for cern.ch.

To have a global access for a squid is not necessarily a bad idea since what can be retrieved through the squid is limited in the squid configuration, usually limited to the major experiments cvmfs content and blocked for all other requests.
It is helpful to have a view global squids that can be used when there is nothing else close by, especially when running on different clouds. While it is preferred to have a squid in each cloud, squids on VMs running in such clouds need to be always up but are not due to different issues with the cloud infrastructure or specific hypervisors.

Cloudflare is much better than any squids we can provide for when nothing is close by.

Since the squid system and cvmfs in general is used by more than just CERN experiments, global squids provide a general fallback solution in case nearby or site squids are down.

Fallbacks for when local squids are down are a different situation.  I agree that you don't want to  use Cloudflare for that, because you want to be able to know when the local squids aren't working, and Cloudflare gives no detailed usage breakdown.  In order for that to be helpful, however, those backup squids need to be monitored for failover, and the owners of the squids need to be notified when there's something going wrong.  That's what we do on the WLCG Squid Monitor CVMFS failover monitor.  We have a few people that watch that and contact the squid owners.

The fallback squids at FNAL and CERN are not configured by default in cernvm or cvmfs as far as I am aware of, but are a fallback coded inside of experiments framework, aren't they? Are they available to non-CERN experiments?

The are configured by default for known domains by the cvmfs-config-default rpm and in its configuration repository for other domains it knows about (here is it's source in github).  Yes they can and are also used for CVMFS by non-CERN experiments, they're for any grid computing.  They allow connections to any well-known cvmfs stratum 1, as defined by the MAJOR_CVMFS acl in the frontier-squid source code.  It looks like we don't yet have Compute Canada stratum 1s listed there but I could add them if it's desired.  I am updating frontier-squid right now to shoal-agent-1.0.0 so it is a good time to make another change.  @rptaylor if you want to be able to use them as CVMFS fallback proxies let me know the names of the stratum 1s and their Cloudflare aliases.

@DrDaveD sure it would be useful to have CC CVMFS servers included in the MAJOR_CVMFS  ACL.
The naming scheme is
cvmfs-s1*.computecanada.ca  and   cvmfs-s1*.computecanada.net
However other than that CC CVMFS is not really related to Shoal or this ticket.


bump to version 1.1.13

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


API Never Gets to Strategy.next() on Unsupported Exchange Data

I came across the situation this week where when one of the stocks I add data to Cerebro using default datafactory, the API will never get to Strategy.next() call (it will hang forever). I didn't realize the symbol (ADRNY from OTCQX) was not traded in a supported exchange until digging into it further. I would think that would trigger an error somewhere instead of the API hanging. If I should be doing this check myself, can I get pointed to where the data going into the datafactory contains the exchange (or other location if that isn't where I should be looking)?

Hi,
you could use the Assets endpoint:
https://alpaca.markets/docs/api-documentation/api-v2/assets/
it will return data that looks like this:

you could just use it directly from the alpaca-trade-api package

That is exactly what I needed to know, thank you! Might be good if the API gives us feedback on if there is a symbol that isn't supported in the future, but this will work great for now. Thanks again!


Download PDF and CSV panel css looks messed up

Test App: https://sg-em-qaext.mapsqa.arcgis.com/apps/instant/notification/index.html?appid=01ea10aea2274497a148a6a4078b7f2e

@MikeTschudi  could you please take a look at this as well? Thanks

@aparveen, what should it look like, please?

@aparveen, how's this?

@MikeTschudi it looks great

Same code; it's fixed in both. Will submit it.

Awesome, thanks so much Mike

Looking good in QA


Don't force using the inferred parser

The inferred parser does not take into account any overrides specified
in .prettierrc.
By not specifying a parser in the options, prettier shall still infer
the parser internally, at a point where overrides specified in
.prettierrc are resolved.
This means that users can specify parsers for custom file extensions
rather than be limited to the filename->parser mapping that prettier has
built-in.

Note default inferred parsers like *.scss files using the scss parser continue to work as expected.


Where to get the model for 512*352 resolution ?

Hi thanks for the execellent work.
May I know if you will release the trained model for the 512352 resolution, so as to generate the 512352 results ?

Hi kudos for the great work. Yes, I was wondering the same. Having the weights for this model would be great and will ease the comparison with your model!


Which border router example code is latest? esp-idf/examples/openthread/ot_br or esp-thread-br/examples/basic_thread_border_router? (TZ-187)

I was trying to use the example project from esp-idf v5.1 examples/openthread/br, but it didn't seem to include the web GUI mentioned in the docs.
I just came across another example at https://github.com/espressif/esp-thread-br/tree/main/examples/basic_thread_border_router.
It's not clear what the difference/relationship is between these two examples (both projects have been updated recently):

https://github.com/espressif/esp-idf/tree/master/examples/openthread/ot_br
https://github.com/espressif/esp-thread-br/tree/main/examples/basic_thread_border_router

Could you clarify the differences (perhaps updating their READMEs to be clearer, or link to each other explaining the difference)? Which one is best to use to set up a border router for testing some simple Thread devices?

I found a little more info here:
https://github.com/espressif/esp-thread-br/issues/9#issuecomment-1506190372

If you want to run the Thread BR on ESP32-C6 single SoC, please use the ot_br example from the ESP-IDF repo:
The example in this esp-thread-br repo is designed for the two SoCs solution

However, I'm still a little confused. I was using the one from the ESP-IDF repo, but couldn't find anything about enabling the Web GUI, whereas in this repo I can see some OPENTHREAD_BR_START_WEB checks that I can't find in the other.
I presume there's nothing about the single SoC setup that prevents using the web gui, so I'm still not sure that the only difference between these examples is using 1 vs 2?

@DanTup  The difference between the two:

ot_br in esp-idf: A simple br example based on two standalong modules, with 2 wires UART connection. It's a quick example setup to demonstrate BR functionality.
basic_thread_border_router in esp-thread-br: It's the production-ready example based on the ESP Thraed Border Router Board, with more wires connection for UART/SPI, BOOT, REST and PTA. This example supports more additional features like RCP update, Web GUI and RF coexistence.

So you can use the ot_br example to tryout the BR features quickly; but if you want some more production features like RCP update and Web GUI, you should start with the basic_thread_border_router.

@chshu perfect - thanks!
It could be really useful to add a note to the top of the respective READMEs with those descriptions, and a link to/description of the other.
I was a bit confused because I found the Web GUI mentioned in some of the docs (https://docs.espressif.com/projects/esp-thread-br/en/latest/esp32/codelab/web-gui.html), but there were other docs that told me to use the esp-idf example (https://docs.espressif.com/projects/esp-idf/en/v5.1/esp32s3/api-reference/network/esp_openthread.html).

Actually, I'm still confused

ot_br in esp-idf: A simple br example based on two standalong modules

basic_thread_border_router in esp-thread-br: This example supports RF coexistence.

In the readme for esp-idf/ot_br it says:

In order to run the example on single SoC which supports both Wi-Fi and Thread, the option CONFIG_ESP_COEX_SW_COEXIST_ENABLE and option CONFIG_OPENTHREAD_RADIO_NATIVE should be enabled. The two options are enabled by default for ESP32-C6 target.

And in esp-thread-br/basic_thread_border_router there is no mention of coexistence. This seems to be the opposite of what you noted above.

@DanTup There is already a note in the ot_br README: https://github.com/espressif/esp-idf/tree/master/examples/openthread/ot_br#overview
CONFIG_ESP_COEX_SW_COEXIST_ENABLE is used to enable the Wi-Fi and Thread Internal coexistence on C6.
For the two SoCs solution, we use the External coexistence which is not mandatory, since there are two separate RF pathes on each SoC.
And more feedback here: https://github.com/espressif/esp-thread-br/issues/21#issuecomment-1637406541

There is already a note in the ot_br README

Oops, I don't know how I missed that 🤦♂ I'll close this then, probably nothing to do here :-)

For the two SoCs solution, we use the External coexistence which is not mandatory, since there are two separate RF pathes on each SoC.

Sorry if this is a basic question (this is all new to me), but can you explain why this is used if it's not required?
Thanks! :-)

The Internal Coexistence (single SoC) is mandatory since there is only one RF path, Wi-Fi and Thread can't access RF at the same time.
The External Coexistence (two SoCs) is not mandatory, since there are two SoCs with two separate RF paths, Wi-Fi and Thread can always access RF for transmiting or receiving. But the External Coexistence feature helps to reduce the interference between the two.


[Feature]Support show segment_num in be_tablets

Why I'm doing:
We can't know how much segment  of the tablet now, and we can calcuate the average segment size by data_size / num_segment to judge whether there are too many small files or compaction is doing timely,.
What I'm doing:
Show segemnt_num through information_schema.be_tablets.
Fixes #issue
*************************** 56. row ***************************
       BE_ID: 10005
    TABLE_ID: 11026
PARTITION_ID: 11025
   TABLET_ID: 11030
 NUM_VERSION: 4
 MAX_VERSION: 4
 MIN_VERSION: 1
  NUM_ROWSET: 4
     NUM_ROW: 3
   DATA_SIZE: 2177
   INDEX_MEM: 0
 CREATE_TIME:<PHONE_NUMBER>
       STATE: RUNNING
        TYPE: DUP
    DATA_DIR: /mnt/disk4/starrocks/storage
    SHARD_ID: 1
 SCHEMA_HASH:<PHONE_NUMBER>
  INDEX_DISK: 0
 NUM_SEGMENT: 3

What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

@Mergifyio backport branch-3.1

@Mergifyio backport branch 2.5

@Mergifyio backport branch-2.5

@Mergifyio backport branch-3.0

ignore backport 2.5.19


Added cxx-build to travis

Closes #31 👍

Coverage remained the same at 55.593% when pulling 0739cfb5478544ffa510c669d9e1368d9a67e500 on cxx-compile into fd476afd48204022928cfec85935720c2d25f719 on master.

Current coverage is 74.62%

Merging #89 into master will not affect coverage as of 82489b2

@@            master     #89   diff @@
======================================
  Files           25      25
  Stmts         2542    2542
  Branches         0       0
  Methods
======================================
  Hit           1897    1897
  Partial          0       0
  Missed         645     645

Review entire Coverage Diff as of 82489b2

Powered by Codecov. Updated on successful CI builds.


Import and export files to and from the desktop

Maybe dropbox integration?
Just the design
As zipped files (import/export)
Drag and drop?
URL to files?

If we decide to allow DnD into the filetree or editor window somehow, we should consider whether to do this upstream or just in our fork--there are bugs on this and/or Trello cards for this feature in Brackets.

The "unzip into filesystem" stuff is something I wrote here, and we could rework into an extension we load if you need that feature (i.e., don't always load it, since the zip/unzip code isn't small):
https://github.com/humphd/nohost/blob/master/src/webserver.js#L29-L84

From discussions today, our plan is:

Allow a user to Import a file or files.  This could be done with a button and dialog box, drag-and-drop, both
If it's a regular file or files, we add it to the current filesystem
If it's a zip file, we ask whether they want to expand it into the current filesystem OR use it as the basis for a new project
We also allow a user to Open a project by URL (i.e., an existing published URL for a project) or name (username/project-name or something).  This could be their own, or someone else's, which is similar to the concept of a remix.

I've done the file-import via dnd, so I've morphed this into the zip import/export bits.

I'm going to do the zip export in #347, and close this now that I've landed the zip import stuff.


Schema for Podcasts

Describe the feature
Are there any plans to implement a Schema also for podcast episodes?
https://unhead.unjs.io/schema-org/getting-started/setup
Additional information

[X] Would you be willing to help implement this feature?

Sure, will built it when I have some time otherwise PRs welcome :)

On further research, Google does not officially support Schema.org for podcasts so I don't plan on adding it to Unhead.


Updating CODEOWNERS for Communication Identity & Common Packages

Description
Updating CODEOWNERS for Communication Identity & Common Packages
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/check-enforcer override

I was under the impression that **/_shared/ matches the _shared folder at any depth....

@petrsvihlik : I wouldn't consider me the authoritative source on this, but that is my understanding as well.   The normal splat pattern semantics use the double-star to indicate "anything below this root."


fixes: #13

Hi @milinddethe15
Remove the first line from src/pages/NotFound.tsx and the deploy shouldn't fail.

Thanks for the contribution @milinddethe15

Join our Discord server to discuss ideas, ask questions, and collaborate with others.


o3ds 8.1-19u stuck on 9.2 upgrade decrypt9 wont load

Hello,
i have O3ds 8.1.0-19u that will not load decrypt9
I have been trying all week,
stock 3ds, drop files on root of sd, load broswer link and the bottom screen either flashes to black with multi colored artifacts/pixels, or flashes black then white. either way nothing happens after that.
what am i doing wrong, im getting super frustrated.
I have tried resetting the 3ds with the sd inside, clearing cookies, history, and clear save data

Have you tried each URL?

My first time installing A9LH browserhax worked the first time; however I've done a few for friends recently and a single device took somewhere in the order of 30 attempts. Also I'd try moving or renaming the profile folder under Nintendo DS (the profile folder is a seemingly random long string, about 32 characters long, and I think it's hex only; A through F, 0 through 9).

8.1.0-19U should be compatible with both GW Spider + Launcher.dat and CakeHax Spider + Decrypt9WIP.dat.
Please be sure you have tried both and not messing up both URL addresses.

If you really did everything right, then it might be a factory SysNAND issue.
This may be unfixable until you upgrade the SysNAND to another version.

Thanks for your responses everyone, im not sure what i should do from here :( probably going to give up this 3ds has a bad card reader that i replaced and was working for a bit, but isnt anymore so cart upgrade is out the window