WE NEEd more tuts.

 I probably won't get to them before 15 of May!:)

willCOVerThis as part of another bug I will file👍


📜 Add login/logout logs with player

Duplicated by #32

Resolved by #32

TEI-of-GitHub-Enterprise.pdf

Hey en n


Getting up and running in vagrant

Hi,
I'm trying to get PXT (for the micro:bit) up and running inside a vagrant box. I can't work out how to add projects and declare them as dependencies, and I'm not sure what to do about the ws=3233&local_token=...
I can get things working by installing nginx, nodejs, and npm. I can them get to a point where pxt serve runs and my nginx config is proxy-ing vagrant-ip:80 -> localhost:3233 and vagrant-ip:8000 -> localhost:3233.
So now I can open up vagrant-ip#ws=8000&local_token=... on my host machine and see the PXT website running. Everything seems to work as it should.
Question 1) I assume that the ws=3323 part of the URL that pxt serve shows me is to tell the website which port to use for a web socket? What does this do? How do I check that it's working? I think the reverse proxy is set up to do the right thing but I can't find any information on what this is for, so I don't know for sure.
Question 2) What does the local_token do? Is it important?
Question 3) How can I add more packages to my package list? The documentation says to put them in the projects folder and then add them to another project's dependencies like this: "banana": "file:../pxt-banana". However, when I try this I get the error message: Cannot load package: can't convert null to object.
Question 4) Is it supposed to save projects to the projects directory? When I hit save in the website I can download the .hex but nothing appears in the projects directory.
Here's the documentation I've been reading:

https://makecode.com/cli
https://makecode.com/defining-blocks
https://github.com/Microsoft/pxt/blob/master/common-docs/packages.md

Here's the code I'm using so far: https://github.com/CodeGuild-co/pxt
This is for a Computer Science course I'm running soon. It's aimed at 16-18 year-olds studying Computer Science at A-level. The plan is that they build something for the micro:bit and then package it up as a reusable block. I ran this course last year and we had trouble getting the packaging to work. At the time we were using a cloud-based VM, this time I thought that vagrant would give me more control over the environment (and means I can prep more in advance).
Thanks for your help (and sorry for the wall of text).

ws=3233 is indeed the web socket port. @pelikhan why aren't we using just one port for everything? we could attach the upgrade handler to the main node server object.
The web socket server does a few things - it saves in projects/ directory (of the server, not the browser - this is probably why you're not seeing them), it also flashes the microbit if it is connected. Additionally it monitors serial ports. I'm not sure if you'll be able to get any of this working with vagrant - depends what VM engine you use.
localtoken=... is for authentication of requests to the web socket server.

pxt serve is designed for a single user/dev experience. It is not meant to support serving an instance of PXT to multiple users. Yes, we should only have 1 web socket, probably technical debt here. @guillaumejenkins can we unify ws servers?

@guillaumejenkins @pelikhan - we do have only one web socket server and one http server. However, we could use the http server as also the web socket server.

Yes, we only have 1 server for the websockets. The websocket library we use lets us open multiple "sockets" over the same port using URL paths (for example, one websocket for wsserver:port/socket1 and one for wsserver:port/socket2). In the end it's still just 1 TCP connection to 1 port, and the library takes care of routing the messages to the right "websocket" object.
@WilliamMayor
To answer question 2): The local_token is just when doing local development, to prevent external computers from trying to query your local PXT dev server. There is no local_token for the online website.
To answer question 3): I don't think there is a way to do that for the online website right now. I think the doc you're reading is for local development only (the file:... protocol cannot be used in the online website), and it could be outdated.
To answer question 4): pxt serve is meant for local development only, and because of that, we handle saving projects in a special way. When serving locally, the server can access the local file system, so we automatically save the projects to a "projects" folder, as you noticed. This lets devs inspect the projects more easily. When accessing the real online website, there is no access to the local file system, so we have to use the browser's download dialog if users want to save projects to a local folder.
Hope this helps!

OK, I think I understand. My websocket stuff must not be working because I cannot save the work I do in the browser to the projects folder. That's fine, I don't really need that side of things anyway.
I would like my students to be able to create their own packages and test them in the browser. The computer suite we're using isn't great and I hoped to be able to use vagrant to get things up and running. Is it not going to be possible at all? It sounds like all I need to do to get it running is find out how to add dependencies using the file protocol. Is there any documentation for this? Or can anyone point me to where the code is that would deal with this side of things?
If I wanted to create a showcase of the student packages (basically a fork of the pxt.microbit.org website, with extra packages). Would this be possible? If the official site doesn't use pxt serve to run, what does it use instead? Can I inject extra packages into this environment too?
Thanks!

If you use https://pxt.microbit.org/beta, your students can use the custom block support documented at https://pxt.microbit.org/blocks/custom

We have recently enabled a "share" feature, where students click the share button and get back a permanent URL for their project. Anyone can click that URL to get a copy of the project. Could that be what you are looking for?

Perfect! I'll use that!
Thanks!

@WilliamMayor note that it will not be possible to develop C++ code in the browser without local installation. You can use existing C++ packages, but you can only create new ones with "pxt serve" etc. You can create TypeScript packages to your heart's content, and most likely this will be enough with the I2C and other stuff we support there.
@guillaumejenkins indeed we have only one web socket server, but we also have a regular HTTP server. It's possible to merge the two, and thus get rid of the entire ws=... argument altogether (which would be a welcome simplification I guess). All one has to do is to attach the 'upgrade' handler to existing HTTP server and not create a new one.


Error when starting

Hi, I'm pretty sure that I wrote all the passwords correctly (I tried three times) but it gives me this error when I start:
local:vickitrix setw$ python vickitrix trade
Enter password for profile "default":
Traceback (most recent call last):
  File "vickitrix/__init__.py", line 597, in go
    get_dough(gdax_client, status_update=True)
  File "vickitrix/__init__.py", line 127, in get_dough
    dough[account['currency']] = account['available']
TypeError: string indices must be integers

Chances are, this opaque error happened because either
a) You entered incorrect security credentials when you were configuring vickitrix.
b) You entered the wrong password above.

Is there any chance that it is some kind of other error?

Nevermind, I already solved it. It was a problem with the internet connection :/


feat(clipboardcopy): add copy to clipboard component

Close #505
Note: Designs have been slightly updated.
@mcoker @matthewcarleton I'm having trouble with the left/right borders from the buttons and text displaying, which is causing a thicker line when these elements are meet. I want to achieve what is done in the input group.

Deploy preview for pf-next ready!
Built with commit 444d770873588490d0cf3d73173a7e1fe13b9872
https://deploy-preview-1340--pf-next.netlify.com

Looks good @christiemolloy, just a few comments. Re: the double borders, you can do what we do in InputGroup and add:
.pf-c-clipboard-copy__group {
    * + * {
      margin-left: -1px;
    }
}

@mcoker made updates. the expandable content isn't positioned absolutely now

@mcarrano could you double check the positioning of the expandable content?

Looks good to me. @mceledonia can you also take a look?

@christiemolloy when you put a lot of text in the editable example, you get a bunch of space to the right of the span. Was there a particular reason it wasn't an input, or input.pf-c-form-control? The patternfly-ng version is, and clipboard.js is, too. Then you could use readonly for the read only versions.

@mcoker I originally didn't use an input/ input.pf-c-form-control component because to me that feels as though data is being submitted where as this is just an area for text to be copied. Maybe it would be worth @jgiardino weighing in on this. clipboard.js has two variations using an input and a textarea

Reproducing what @mcoker describes, this is how it displays. Here are a few thoughts that come to mind:

I'm not sure if just the attribute contenteditable creates the weirdness in the example below, or if it's a combination of this attribute and css styles, but I think we can avoid this issue with just using input (e.g. that would allow us to not truncate the text)
If we use a readonly input, I don't think we're required to include it inside a form. A similar control in github uses a readonly input and is not inside a form.
I assume the purpose of the editable variation is to use it in the context of a form. Is there a reason why it would not be used in a form?

I think I side with @mcoker on using an input. I could also see us adding a variation that uses a textarea, but I don't think that's critical for this PR.

@mcoker removed the input-group component, @jgiardino made a11y updates, thanks for your feedback!

@jgiardino when you said

I'm not sure if just the attribute contenteditable creates the weirdness in the example below, or if it's a combination of this attribute and css styles, but I think we can avoid this issue with just using input (e.g. that would allow us to not truncate the text)

do you think the text in the input shouldn't truncate? I was going to ask if we could add text-truncate: ellipsis; to the input so it doesn't just cut off.

I said:

I'm not sure if just the attribute contenteditable creates the weirdness in the example below, or if it's a combination of this attribute and css styles, but I think we can avoid this issue with just using input (e.g. that would allow us to not truncate the text)

then @mcoker said:

do you think the text in the input shouldn't truncate? I was going to ask if we could add text-truncate: ellipsis; to the input so it doesn't just cut off.

For the <input> element, showing an ellipsis for the cut off text seems fine (at least when testing in Chrome). I think what I meant is that using an <input> is nice because it allows the user to highlight and select specific portions of the text, which I think would be harder to do having just <p> contents that are truncated. For the <input> when the ellipsis displays, if I place focus in the input, the ellipsis will go away and I can shift my cursor to see contents beyond where the ellipsis was, which seems to fine (but again I was only testing in Chrome).


Spray 1.2.4 and phantom 1.9.8 have conflicts using shapeless

We are trying to use phantom 1.9.8 in one of our projects which already uses spray routing (1.2.4). Our observation is the code which uses phantom fails with
[error] bad symbolic reference. A signature in ImplicitMechanism.class refers to term shapeless
[error] in package  which is not available.
[error] It may be completely missing from the current classpath, or the version on
[error] the classpath might be incompatible with the version used when compiling ImplicitMechanism.class.
[error] bad symbolic reference. A signature in ImplicitMechanism.class refers to term package
[error] in value shapeless which is not available.
We did follow one of your other threads and excluded the shapeless as below, but that did not help.
val phantomDSL = "com.websudos" %% "phantom-dsl" % "1.9.8" exclude ("com.chuusai", "shapeless_2.10")
Any idea how to get away from this ? Is is ok to expect phantom to work with lower version of shapeless ?

we are using this "io.spray" %%  "spray-routing-shapeless2" % SprayVersion

Hi @jtjeferreira , @anujag231 ,
I've added your comment to the Wiki page on how to include phantom. All future users will now know how to deal with this easily. Many thanks for all your help!
Regards.


Cannot Access PWD GUI after following steps from development section in README

I followed the steps listed below as described in the Readme section:
tart the Docker daemon on your machine and run docker pull franela/dind.

Install go 1.7.1+ with brew on Mac or through a package manager.

go get -v -d -t ./...

Start PWD as a container with docker-compose up.

Point to http://localhost and click "New Instance"

So all my containers are up and running and I can access my grafana container at http://ip:3000 but I cannot do the same for my pwd sessions. Is there something I need to do, to get this working? In other words step 4 is not working for me.
I appreciate the help.

Hi. You need to use localhost as your hostname. Check the haproxy.conf file.

Hi, Thank you for the quick response. I did use localhost as my hostname, instead of getting directed to a page where I can add instances, I get directed to a Windows Internet Information Services page.


fix compile errors

Fixed several bugs preventing rhai-wasm from compiling:

Removed the redundant feature of lsp-async-stub
Fixed AsyncWriteExt import
Implemented the write_file function required by the Environment for WasmEnvironment with reference to read_file (Not tested, I'm not sure if it works correctly)

Much appreciated, thanks!


signal 11: Segmentation fault

I've pulled fresh version of postgresml from github instead of using ubuntu package (as from what I saw it still doesn't have preprocessing features) and managed to compile it and update .so library with the new one. But now it gives me a segfault even on the basic example:
2023-02-03 16:34:32.815 UTC [125591] LOG:  database system is ready to accept connections
2023-02-03 16:34:44.698 UTC [125591] LOG:  server process (PID 125611) was terminated by signal 11: Segmentation fault
2023-02-03 16:34:44.698 UTC [125591] DETAIL:  Failed process was running: SELECT * FROM pgml.train(
project_name => 'Breast Cancer Detection',
task => 'classification',
relation_name => 'pgml.breast_cancer',
y_column_name => 'malignant'
)
ubuntu 22.04, postgresql 14

I'm guessing you can successfully run tests locally on your build with cargo pgx test? Did you build w/ cargo pgx package? This sounds like there may be some incompatibility between different parts of the installation, maybe something is leftover from the previous create extension ... call? Have you tried doing a cargo pgx install (which depends on pg_config being setup with the correct paths)?
Can you add the exact steps you went through to upgrade the .so?
PS. We're planning to cut a new release with preprocessing next week.

all tests run successfully:
test result: ok. 47 passed; 0 failed; 0 ignored; 0 measured; 0 filtered
out; finished in 279.30s
Yes, built with cargo pgx package.
For the steps, I just followed the exact instructions on building from
source and just copied the compiled .so instead of the one that came from
the .deb package.
Tried now with cargo pgx install also, it was done successfully but still
the same seg fault. If there's anything else I can provide please let me
know, otherwise I'll have to wait for the prepared package.
On Sun, Feb 5, 2023 at 4:13 AM Montana Low @.***> wrote:

I'm guessing you can successfully run tests locally on your build with cargo
pgx test? Did you build w/ cargo pgx package? This sounds like there may
be some incompatibility between different parts of the installation, maybe
something is leftover from the previous create extension ... call? Have
you tried doing a cargo pgx install (which depends on pg_config being
setup with the correct paths)?
Can you add the exact steps you went through to upgrade the .so?
PS. We're planning to cut a new release with preprocessing next week.
—
Reply to this email directly, view it on GitHub
https://github.com/postgresml/postgresml/issues/530#issuecomment-1416910982,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEHJFYZDAKVFIWJ3QZ4373WV4LHFANCNFSM6AAAAAAUQOWQPI
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is interesting. I can't repro any segfaults on my setup, but I can get one on our build machine during cargo pgx package. It's coming from the installation process during pgx macros generating function signatures. Why this works on some machines and not others is not obvious to me. I'm going to work on a patch for the build process, including updating pgx, before doing an actually release (that includes preprocessing).

Thanks, if you need me to test that patch before releasing let me know, also this is my test vm running nothing but pgml so I can give you access if you need it for some testing etc.

I’d love to know if this patch fixes it for you. It’s a shot in the dark.
On Mon, Feb 6, 2023 at 11:18 PM dusanmarjanovic @.***>
wrote:

Thanks, if you need me to test that patch before releasing let me know,
also this is my test vm running nothing but pgml so I can give you access
if you need it for some testing etc.
—
Reply to this email directly, view it on GitHub
https://github.com/postgresml/postgresml/issues/530#issuecomment-1420304319,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACDNHJOYCLWTUSHA5JBNPLWWHZOFANCNFSM6AAAAAAUQOWQPI
.
You are receiving this because you commented.Message ID:
@.***>

hi, any progress on this? thanks
On Tue, Feb 7, 2023 at 1:07 PM Montana Low @.***> wrote:

I’d love to know if this patch fixes it for you. It’s a shot in the dark.
On Mon, Feb 6, 2023 at 11:18 PM dusanmarjanovic @.***>
wrote:

Thanks, if you need me to test that patch before releasing let me know,
also this is my test vm running nothing but pgml so I can give you access
if you need it for some testing etc.
—
Reply to this email directly, view it on GitHub
<
https://github.com/postgresml/postgresml/issues/530#issuecomment-1420304319
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AACDNHJOYCLWTUSHA5JBNPLWWHZOFANCNFSM6AAAAAAUQOWQPI
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/postgresml/postgresml/issues/530#issuecomment-1420666890,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEHJFYGOUTDMELDKCIV6PLWWI3GJANCNFSM6AAAAAAUQOWQPI
.
You are receiving this because you authored the thread.Message ID:
@.***>

@dusanmarjanovic were you able to test a new build w/ #533?

sorry for late reply @montanalow, i did try and it was the same, but installed from the apt and its working fine


Missing Permission Type

Hi,
It seems that the document assumes that the user has Global Admin role rights.
Please may I ask that it be considered that the requred user right be in the prerequisists in order to create and deploy a blueprint?
Thank you,
Rui
[Enter feedback here]

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

ID: 526dc7c5-6317-cf35-53a9-e010f4701b60
Version Independent ID: 087272dd-50ee-87a7-48d8-9b3b9008474f
Content: Quickstart: Create a blueprint in the portal - Azure Blueprints
Content Source: articles/governance/blueprints/create-blueprint-portal.md
Service: blueprints
GitHub Login: @mumian
Microsoft Alias: jgao

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

@PrimeDime1 Thanks for your feedback. To use blueprints, you must be granted permissions through Azure role-based access control (Azure RBAC). To read or view a blueprint in Azure portal, your account must have read access to the scope where the blueprint definition is located.
To create blueprints, your account needs the following permissions:

Microsoft.Blueprint/blueprints/write - Create a blueprint definition
Microsoft.Blueprint/blueprints/artifacts/write - Create artifacts on a blueprint definition
Microsoft.Blueprint/blueprints/versions/write - Publish a blueprint

To delete blueprints, your account needs the following permissions:

Microsoft.Blueprint/blueprints/delete
Microsoft.Blueprint/blueprints/artifacts/delete
Microsoft.Blueprint/blueprints/versions/delete

Same information is available in this document here : https://learn.microsoft.com/en-us/azure/governance/blueprints/overview#permissions-in-azure-blueprints
I also updated the document that you have requested. We will close the issue for now. If there are further questions , please revert and we will be glad to assist you.


Could you provide a  direct link of the dataset used in this paper? thanks~

Yes please. Can you host the 6 datasets in your /raw folder on google drive or dropbox? Thanks

google driver is ok~ On 10/19/2018 08:08, Rohan Chandra wrote: Yes please. Can you host the 6 datasets in your /raw folder on google drive or dropbox? Thanks — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Or， could you privide the trainset.mat valset.mat testset.mat ? On 10/19/2018 08:19, LiuChuang wrote: google driver is ok~ On 10/19/2018 08:08, Rohan Chandra wrote: Yes please. Can you host the 6 datasets in your /raw folder on google drive or dropbox? Thanks — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

How do you extract the latitudinal and longitudinal maneuvers from the data files?

Sorry for the late response. I'm not sure if I'm allowed to host the data. I'll try to include a line to download it in the pre-processing script.

@nachiket92 First of all, congratulations for this fantastic work!
I have downloaded all the zip files as well as the large csv file
"Next_Generation_Simulation__NGSIM__Vehicle_Trajectories_and_Supporting_Data.csv"
But the data needs to be processed to get the corresponding six files.
So I hope that you can provide download links for six files.
thank you for you help

https://data.transportation.gov/Automobiles/Next-Generation-Simulation-NGSIM-Vehicle-Trajector/8ect-6jqj


What is extract-criteria-fields for?

Is https://github.com/linuxfoundation/cii-best-practices-badge/blob/master/doc/extract-criteria-fields used for anything? It seems buggy in that it's only reporting MUST fields.

I'm pretty sure that is completely vestigial. I'd forgotten all about it.

It became obsolete in Nov 2015, it's essentially early scaffolding.  I'll remove it.

Let's add a fuzzer that deletes random files in the repo and see if any tests fail. Just like what happens with gene transcription sometimes.
Dan Kohn<EMAIL_ADDRESS>Executive Director, Cloud Native Computing Foundation https://cncf.io
tel:+1-415-233-1000

On Jun 9, 2017, at 20:27, David A. Wheeler<EMAIL_ADDRESS>wrote:
I'm pretty sure that is completely vestigial. I'd forgotten all about it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Start of 1.9 dev

This pull requests contains:

Gradle changes

Adding DeobfMC as Gradle plugin to deobfuscate Minecraft (no need for more complicated setup, simply clone and run applySpecialSource to setup contribution workspace)
Dependencies is now managed by Gradle.

Code Changes

Quantum Agent - a initialization option for Quantum API

Compiling Changes

Tons of compile errors from going to 1.8 -> 1.9. (90 errors+)

I think for now it would be best if people contribute to cold sections of the project such as gradle. If you'd like, @PizzaCrust, I can add you to the team and you can manage gradle (@code you need to talk to me!).
I personally find the fact that gradle removes IDE dependency a great thing, but also somewhat too complex, and thus I have no interest in learning Gradle. I would rather someone else handle it or I make my own simpler-with-more-options environment setter upper. Again, I don't like learning a large framework just to do one simple task.

@EzraEn1 ^**

@LinkTheProgrammer
I would love to manage Gradle.

I guess merge?

A few changes need to be made before merge:

we will work on 1.8 first before we move on.
-DeobfMC will not be needed. If someone wants to make base edits with my API, they'll have to use MCP to decompile and deobfuscate minecraft source, as I will be making a medium for modding the base built on top of Mixin.
-remove the minecraft and javassist dependencies. Developers won't need those.

If you were making this gradle project for development of Quantum API, I appreciate the offer, but I don't think we will need gradle to build this. If you want to make a gradle for the team, make a new branch "gradle".

DeobfMC is not for base edits. It adds Minecraft as a dependency.
It has benefits:

MCP is no longer required for deobfuscation. Mappings can be provided directly by QuantumAPI contributors. Allowing for faster releases.
MCP is also no longer required for obfuscating, too. Mappings can be reversed by DeobfMC.

Would you consider giving DeobfMC to QuantumTheoryMC?

Sure.

Thank you! Would you mind transferring the repository please?

Transferred. We should transfer this chat. Trello, Skype, Email?

Slack. What's your email?
On Saturday, March 26, 2016, PizzaCrust<EMAIL_ADDRESS>wrote:

Transferred. We should transfer this chat. Trello, Skype, Email?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/QuantumTheoryMC/QuantumAPI/pull/5#issuecomment-201831763

<EMAIL_ADDRESS>

Check your email
On Saturday, March 26, 2016, PizzaCrust<EMAIL_ADDRESS>wrote:

<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','pizzacrustcoder@gmail.com');>
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/QuantumTheoryMC/QuantumAPI/pull/5#issuecomment-201831824

I'm on it.

this pull request is no longer needed.


Enable Cross Compilation

The biggest change is that cmake is now an optional method of building that can be enabled with the use-cmake feature flag. However, by default, cc will be used (with the parallel feature) for compilation. This was the easiest way to get physx to compile for windows uses clang-cl on a non-Windows host platform.
In addition, the structgen executable, which is also built and executed by the build script, is also behind a feature flag, structgen, and will not be compiled or executed by default. Instead, the outputs for linux, macos, and windows have been checked in to the repository which means they can be used when running on a platform other than the target.
Changes were made to the CI to run tests and the ball example in debug and release with all, none, only structgen, and only cmake feature flags on to make sure that the various scenarios all "work".
Note that this supplants #41 as it takes into account the CXX compiler in the same way that cc-rs does.
Resolves: #41
TODO: Put cooking and the visual debugger behind feature flags as they're not required for the core physx functionality

Oh right, and I will update the README/docs once this gets some more eyes on it.

Being able to build this without CMAKE, and to cross-compile is fantastic, thanks :D
The code looks good to my eye, but one thing is unclear: how do we update to a newer version of PhysX? What's the path for upgrading structgen and the lists of source files?

So I came into this without knowing anything about the physx code base or how it evolves, so I was planning on doing the next upgrade myself so I could writeup complete documentation for it. I wasn't overly concerned with it due their extremely long release cadence though, so there are a few manual steps (like downloading the generated files from CI for all platforms manually to place them in the repo).

Works for me! Just don't get hit by a train, ktnx! :D

So far so good!


Use Quay in OSBS-BOX

Hi,
recently Quay got open-sourced[0]. Maybe you should consider replace current registry with quay.
[0] https://github.com/quay/quay/

Simple registry is suitable for osbs-box. We don't need complex system offered by quay for dev purposes.

I still think you should consider this as opt-in.
Some of your users may use quay as registry.
It would be better for developers if they can debug issues in local env.

@twaugh thoughts?


Views generated by the fs-bq-schema-views script don't parse firestore timestamps correctly

[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your configuration

Extension name: firestore-bigquery-export
Extension version: 0.1.5

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:

Have an instance of the extension set up to send updates to BigQuery from a collection where documents have a timestamp field
Use the fs-bq-schema-views script to generate views

Expected result
View shows timestamps corresponding to the value on firestore
Actual result
View has null values

On the generated view, the query goes something like this:
`firestore_export.firestoreTimestamp`(JSON_EXTRACT_SCALAR(data, '$.date')) AS date

I tried using JSON_EXTRACT() instead and apparently it yielded an actual timestamp

The script generates two schema views, one for the changelog and one for the latest. The latest schema view ignores the actual date for some reason:
SELECT
  *
EXCEPT
  (date)

I was able to tinker with the schema views actual queries and get the date part from the timestamp which is what I'm interested in, but I don't think this is an intended behaviour

I'm having the same issue. Here's some other information.
The "latest" schema excludes the timestamp field (for me it is called "createdAt") and two additional fields are created: createdAt_seconds, createdAt_nanoseconds.
The query for the "latest" view excludes createdAt in the GROUP_BY section, and adds an extra createdAt_seconds, createdAt_nanoseconds on the last line, where I expect to find the createdAt field name.

Yes, the firestore timestamp fields appear on the JSON as an object with _seconds' and _nanosecondskeys, the script actually generates a functionfirestoreTimestamp()to convert those seconds and nanoseconds to milliseconds, and then use the result to generate a timestamp with BigQuery'sTIMESTAMP_MILLIS(). But this doesn't work as intended because of the use of JSON_EXTRACT_SCALAR()on the timestamp object. Apparently, changing it toJSON_EXTRACT()` solves the issue on timestamps.

How can I use the updated script from the next branch (rather than the master) using npx?
npx @firebaseextensions/fs-bq-schema-views#next does not work for me


Enabling docker & enroot installation

Issue #, if available:
Description of changes:
I would like to use this space to discuss potential risks and feasibility of making docker enroot installation by default.

Due to https://github.com/aws-samples/awsome-distributed-training/issues/141 we have disabled docker/enroot installation in https://github.com/aws-samples/awsome-distributed-training/pull/142 but I believe that that permission issue is now taken cared by https://github.com/aws-samples/awsome-distributed-training/blob/78d906651b1de4fb5c068cd157c6d60331c44ad8/1.architectures/5.sagemaker-hyperpod/LifecycleScripts/base-config/utils/install_enroot_pyxis.sh#L64

Closing per discussion with @shimomut . We'll make this configurable through config file.


Remove useless duplicate lines in *.py files

This PR is to remove useless duplicate lines in *.py files.
Wrote a regex script to scan throught the python files in the repo, and found the remaining useless duplicate lines like saver_test.py#L104:

  self.assertEqual(v1.read_value().numpy(), 1.0)
  self.assertEqual(v1.read_value().numpy(), 1.0)

Cool, thanks!


Runtime Error

pixel_values = torch.cat([pv for pv in all_pixel_values if pv is not None], dim=0) if any(all_pixel_values) else None
RuntimeError: Boolean value of Tensor with more than one value is ambiguous
such error exist while I am using the finetune_lora_vision script

If you are using mixed-modality data, use zero2 for fine-tuning.


Rename 'module' symbols to avoid keyword conflict

Fixes #5148
('module' is a keyword starting with C++20)

Nasty... Thanks! How difficult would it be to add an inspect check for this? Let me know if you'd like me to add it.

If we had a C++20 builder then we wouldn't need an inspect check, I think.

Nasty... Thanks! How difficult would it be to add an inspect check for this? Let me know if you'd like me to add it.

If we had a C++20 builder then we wouldn't need an inspect check, I think.

Good point! We can definitely add that.


shouldOpen doesn't pass the actual event target to the callback

Items in the slick carousel might have controls added to them. It would be useful to pass the actual event object to the callback so that the event.target can be compared with the selector of a given control.
An example would be a slider with images having a "Remove this image" control and its respective event listener attached.  As it is, shouldOpen simply passes the slide itself, making it difficult to prevent both the lightbox being shown and the "Remove this image" event firing.

#36

thanks for the PR :+1:


Executing the build command through mode cannot resolve the path of the federation

Describe the bug
In a project using federation, it works fine if you use the yarn build command to package, but if you use yarn build --mode test, federation cannot be resolved

Reproduction
https://github.com/GOGOGOSIR/vite-build-issue.git
System Info
System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
    Memory: 731.51 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Browsers:
    Chrome: 96.0.4664.110
    Firefox: 92.0
    Safari: 13.1.3

Used Package Manager
yarn
Logs
vite:config bundled config file loaded in 47.73ms +0ms
  vite:config using resolved config: {
  vite:config   plugins: [
  vite:config     'alias',
  vite:config     'vite:modulepreload-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html-inline-proxy',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:worker-import-meta-url',
  vite:config     'vite:asset',
  vite:config     'vite:vue',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:watch-package-data',
  vite:config     'vite:build-html',
  vite:config     'commonjs',
  vite:config     'vite:data-uri',
  vite:config     'rollup-plugin-dynamic-import-variables',
  vite:config     'vite:asset-import-meta-url',
  vite:config     'originjs:federation',
  vite:config     'vite:build-import-analysis',
  vite:config     'vite:esbuild-transpile',
  vite:config     'vite:terser',
  vite:config     'vite:reporter',
  vite:config     'vite:load-fallback'
  vite:config   ],
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     polyfillModulePreload: true,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'js',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     cssTarget: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     sourcemap: false,
  vite:config     rollupOptions: { output: [Object] },
  vite:config     minify: 'terser',
  vite:config     terserOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     reportCompressedSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null,
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
  vite:config   },
  vite:config   mode: 'test',
  vite:config   define: { __VUE_OPTIONS_API__: true, __VUE_PROD_DEVTOOLS__: false },
  vite:config   ssr: { external: [ 'vue', '@vue/server-renderer' ] },
  vite:config   configFile: '/Users/mac/Desktop/vite-federation 2/vite.config.ts',
  vite:config   configFileDependencies: [ 'vite.config.ts' ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: 'test',
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     build: {}
  vite:config   },
  vite:config   root: '/Users/mac/Desktop/vite-federation 2',
  vite:config   base: '/',
  vite:config   resolve: { dedupe: undefined, alias: [ [Object], [Object] ] },
  vite:config   publicDir: '/Users/mac/Desktop/vite-federation 2/public',
  vite:config   cacheDir: '/Users/mac/Desktop/vite-federation 2/node_modules/.vite',
  vite:config   command: 'build',
  vite:config   isProduction: true,
  vite:config   server: {
  vite:config     preTransformRequests: true,
  vite:config     fs: { strict: true, allow: [Array], deny: [Array] }
  vite:config   },
  vite:config   preview: {
  vite:config     port: undefined,
  vite:config     strictPort: undefined,
  vite:config     host: undefined,
  vite:config     https: undefined,
  vite:config     open: undefined,
  vite:config     proxy: undefined,
  vite:config     cors: undefined,
  vite:config     headers: undefined
  vite:config   },
  vite:config   env: {
  vite:config     VITE_USER_NODE_ENV: 'production',
  vite:config     VITE_ENV_TYPE: 'test',
  vite:config     VITE_TEST_AK: '1be9b80c6b2444f01a3651ea28497821',
  vite:config     VITE_PRODUCTION_AK: '051977abcbe057055832888ea060973c',
  vite:config     BASE_URL: '/',
  vite:config     MODE: 'test',
  vite:config     DEV: false,
  vite:config     PROD: true
  vite:config   },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     warnOnce: [Function: warnOnce],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen],
  vite:config     hasErrorLogged: [Function: hasErrorLogged]
  vite:config   },
  vite:config   packageCache: Map(0) { set: [Function (anonymous)] },
  vite:config   createResolver: [Function: createResolver],
  vite:config   optimizeDeps: {
  vite:config     esbuildOptions: { keepNames: undefined, preserveSymlinks: undefined }
  vite:config   },
  vite:config   worker: {
  vite:config     format: 'iife',
  vite:config     plugins: [
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object],
  vite:config       [Object], [Object], [Object]
  vite:config     ],
  vite:config     rollupOptions: {}
  vite:config   }
  vite:config } +6ms

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Should this be an issue in vite-plugin-federation?

Should this be an issue in vite-plugin-federation?

If it's a vite-plugin-federation problem, then there should also be a problem with yarn build --mode production . But the truth is, it was a success. It will only appear if mode is not equal to production

Vite doesn't do anything special with the different modes, and if that somehow affects vite-plugin-federation (since the error is coming from an id that it should handle), then I think the maintainers there would have a better idea of what's going on.

@GOGOGOSIR please make sure your remote project is build and running.

Vite doesn't do anything special with the different modes, and if that somehow affects vite-plugin-federation (since the error is coming from an id that it should handle), then I think the maintainers there would have a better idea of what's going on.

After I checked, I found that it was indeed a vite-plugin-federation problem

Vite doesn't do anything special with the different modes, and if that somehow affects vite-plugin-federation (since the error is coming from an id that it should handle), then I think the maintainers there would have a better idea of what's going on.

After I checked, I found that it was indeed a vite-plugin-federation problem


NoVNC session in chrome doesn't work

When accessing the NoVNC server to use GMAT in a chrome browser, the session is established but cannot interact with the remote machine.

The issue was tested using a chrome browser on multiple computers, and the NoVNC worked fine.  It seems the issue is not caused by the quindar-deploy.  Most likely the issue is related to the computer software setting.


Add split offsets to manifest files

Instead of storing a single HDFS block size for each data file, Iceberg should store a list of split offsets. That will allow split planning to be more precise by using row group or stripe offsets, without reading file footers.

This issue has moved to the ASF repo: https://github.com/apache/incubator-iceberg/issues/37


First commit of RawThresholdClassifier

Coverage remained the same at 94.032% when pulling bcd203c154c086ce4bf24dfc242ce93742dda047 on raw-threshold into<PHONE_NUMBER>b8f9fddf7399bdec2adad8874db040 on master.

Coverage remained the same at 94.032% when pulling a716250c162fcedcf8143f259f5e7702461e4751 on raw-threshold into<PHONE_NUMBER>b8f9fddf7399bdec2adad8874db040 on master.


gh #27 Add DolbyMode Game Support

 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.


Google login button margin

When following instructions from the book, login button looks like this

I suggest to add right margin to img element inside the button
    <Button variant="raised" style={styleLoginButton} href="/auth/google">
      <img
        src="https://storage.googleapis.com/builderbook/G.svg"
        alt="Log in with Google"
        style={{ marginRight: '5px' }}
      />
      Log in with Google
    </Button>

It's better than     as dirty fixed in 3-end repo

@YuriGor Thanks, great suggestion.
I tried it locally and looks good, but I would go with 10px for a little more space. Would you like to create a pull request?
You can simply update it in the main repo (builderbook/pages/public/login.js), and I'll propagate the change to all other instances of the login button. Or you are welcome to update this code in all of the book folders, too.

Dont' forget to update text in the book too.
Chapter 3 / Login page and Nprogress

Thanks, I updated the book content too.


Build: Refactor creation to connect data

Now "other builds" is displayed without any interconnection, for example I can see images of other builds, but I don't know if that build is OK, or what.
So: Add section with other builds and get the data (eventually with graphs) of that build, so one could eventually see, which direction take when making a build.

Updated, but the original idea is still quite good, so won't do.


How to Set the Extension’s Image in the Extension Entry Point?

I would like to set the extension’s image/icon within the ExtensionConfiguration. However, I am unsure if there is a way to configure the extension’s image directly in the code or through metadata.
For example:
public override ExtensionConfiguration ExtensionConfiguration => new()
{
       Metadata = new(
        id: "CommandParentingSample.c30b7870-76bc-4ef6-93e8-15b9a54c9e2b",
        version: this.ExtensionAssemblyVersion,
        publisherName: "Microsoft",
        displayName: "Command Parenting Sample Extension",
        description: "Sample extension demonstrating command parenting"),
        imagePath: "Some path to the Image" // Example
};

You can use this piece of code:
    public override ExtensionConfiguration ExtensionConfiguration => new()
    {
        LoadedWhen = ActivationConstraint.SolutionState(SolutionState.FullyLoaded),
        Metadata = new(
            id: "TSVN.64f925a0-498e-45e3-a544-30ecbd32620d",
            version: ExtensionAssemblyVersion,
            publisherName: "Samir Boulema",
            displayName: "TSVN",
            description: "Control TortoiseSVN from within Visual Studio")
        {
            MoreInfo = "https://github.com/sboulema/TSVN.Gladstone",
            ReleaseNotes = "https://github.com/sboulema/TSVN.Gladstone/releases",
            Tags = ["SVN", "Source control", "Tortoise", "Repository"],
            // TODO: BUG? License file is missing
            //License = "Resources/License.txt",
            Icon = "Resources/TortoiseSVN.png",
            PreviewImage = "Resources/TortoiseSVN.png",
        },
    };


Invalid G/W port in API path

Bug Report
I am seeing an invalid port in the API path. This must be the g/w's tls port 443
root@null [ ~/dispatch ]# dispatch get api
     NAME    | FUNCTION | PROTOCOL | METHOD | DOMAIN |                 PATH                  | AUTH | STATUS | ENABLED
------------------------------------------------------------------------------------------------------------------------
  post-hello | hello-py | https    | POST   |        | https://localhost:8444/dispatch/hello |      | READY  | true
------------------------------------------------------------------------------------------------------------------------

Impact

[ ] Low - Annoyance, but does not impact business or functionality
[X] Medium - Issue can be worked around, but is causing pain
[ ] High - Blocker

Possible solution

Your Environment

Dispatch CLI version (or git commit):
Dispatch Chart version (or image[s] tag):
Operating System and version:
Kubernetes version (and distribution):
Etc (any other useful environmental information):

cc @kars7e @zimengyang

@neosab Here is the reason, In #709
the api gateway port is read from dispatch config file. but in the ova, the file don't contain api-https-port and api-http-port, so it show as default api gateway port 8444 and 8081.
So I think we should modify the config file

@pzmrzy Why is the server reading from config file? It must be reading from the --gateway-tls-port 443 flag right

Yes, the server read the flag, but client read the config file
When do dispatch get api, the server return only the relative url.
The port is been add in the client side

I missed that the URL is constructed by the client. Yup, in that case, we should fix the config file in the OVA.


add button to navigate to analysis from default SPOT page

The analysis page is somewhat hidden and only accessible by navigating directly to the endpoint. There should be a button somewhere on the default page to view the analysis page.

The analysis page is somewhat hidden and only accessible by navigating directly to the endpoint. There should be a button somewhere on the default page to view the analysis page.

Finished


Check the user name and password in DB

My team will handle this. @shirmenzely @VictoriaShumeruk @octopusShiva @eransevil

@Omeramsc are you sure? I think it better to do it under the 'sing up' team and to check it when the user is signed in

@BarakMerdler By authenticating we need to check if the username and password a user provided indeed exists in the DB, so no question about it when logging in.
You can write it for the signup process as well, but I think we may be able to use the same function.

made redundant by #102 & #103
@lioramilbaum please close this issue.


AddJoinedAppOptions

The main point of this PR is to be able to join two AppOptions lists to a single list. This can typically be used when you want to add custom text for a non-answer.
To use this, you need to already registrer two (or more) AppOptions (eg "country-no-sentinel" and "sentinel"), and then use the custom registrer function
services.AddJoinedAppOptions("country", "country-no-sentinel", "sentinel");

the "country" app option can then be used as any other optionId
If the providers set Parameters, the parameters from all subLists gets combined in a single dictionary with the optionId prefixed on each key.
Related Issue(s)

https://github.com/Altinn/app-lib-dotnet/issues/443
Previous PR that was closed because v8 work postponed the writing of a test of parameter combination https://github.com/Altinn/app-lib-dotnet/pull/444

Verification

[ ] Your code builds clean without any errors or warnings
[ ] Manual testing done (required)
[ ] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Looks good, added a few nitpick comments. Ss documentation updated?

Would be nice if the title is update to better reflect what this introduces as we are using the PR titles in our release notes


Upversion to 1.0.2

Fix for python paths with spaces
Fix to silence link_flags warning
Add platform.py to enable unit testing

Includes upstream commit of https://github.com/Tarang74/quty/pull/1


Unable to run s3ninja behind a reverse proxy

I've been testing s3ninja (docker tag scireum/s3-ninja:7.0) and attempting to run it behind a reverse proxy on a non-root URL, but I can't get the UI to appear correctly.
I've tried updating application.conf so that product.wondergemRoot points to /my/new/uri/ui but from what I can see there are still hardcoded references to the /ui uri within the application.
Is there a configuration option that can be used to allow s3ninja to run correctly in a reverse proxy setup?

@jakobvogel thanks for the response!
I do understand that S3 Ninja is for development purposes only: let me explain my use case. I am currently working on a prototype website that allows users to upload content to be made available to subscribers via S3. The rest of the site sits behind a reverse proxy with authentication so that the client can see the current work in progress.
Since S3 Ninja isn't covered by the same authentication domain then someone who knows the domain and port of the instance would be able to browse the copyrighted content directly via /ui without requiring a password.
In regards to s3cmd i'm currently using the AWS PHP SDK to access the S3 storage: for development sites I used the use_path_style_endpoint option which allows you to specify an arbitrary endpoint url instead of using the AWS host-based naming scheme. It is this feature that would enable me to S3 ninja behind a reverse proxy in this way.
I do understand that this may not be your primary use case, but I thought it would be worth mentioning why I think such a feature would be useful in future for developers in a similar situation.

Hello @mcayland! Many thanks for clarifying this. I have asked our IT administrator about his thoughts on this problem and will get back if we have an alternative suggestion. In any case, we will consider your idea for future development. 👍

@jakobvogel I thought it was worth adding an update here for anyone else who finds themselves in a similar situation: my realisation was that I could easily switch the application over to use a test configuration which doesn't require use_path_style_endpoint so in fact all I needed was to be able to allow access to the UI through the frontend proxy to allow developers to check access logs and the bucket contents.
Unfortunately the templates included with s3ninja have hard-coded absolute URLs causing the links and stylesheets to be incorrect, but I was able to get a basic UI working by using the following nginx configuration on the frontend proxy:
    #
    # s3ninja at /s3ninja/
    #

    # s3ninja assets
    location /s3ninja/assets/ {
        proxy_pass http://container-s3ninja:9000/assets/;
        proxy_set_header Accept-Encoding "";

        sub_filter_once off;
        sub_filter_types text/css;
        sub_filter '/assets/' '/s3ninja/assets/';
    }

    # s3ninja UI
    location /s3ninja/ui {
        proxy_pass http://container-s3ninja:9000/ui;
        proxy_set_header Accept-Encoding "";

        sub_filter_once off;
        sub_filter_types text/html;
        sub_filter '"/assets/' '"/s3ninja/assets/';
        sub_filter '"/ui' '"/s3ninja/ui';
    }

To summarise: it is possible to use s3ninja on a container network whilst forwarding access to the UI through a frontend reverse proxy using this configuration. However the use of sub_filter to fix up the absolute URLs seems quite heavy-handed, so would it be possible to use relative URLs in the UI so that this extra workaround is no longer required?

Hello @mcayland — Many thanks for sharing this. Please excuse my late reply, these are busy release times here. In theory, it is possible, of course. However, that would require quite a lot of time to do. The routing is done via our Sirius framework which basically knows multiple methods for dispatching data given a requested URL. In particular, re-routing everything below assets/ with relative paths would be challenging, and it would require changes in the library as well. Considering the special nature of your use case, and the effort required to change the paths, I would rather prefer to leave the paths as they are and stay with your rerouting solution via the configuration file. It looks to be the more solid solution.
Are there still paths not covered by your configuration?

The routing is done via our Sirius framework which basically knows multiple methods for dispatching data given a requested URL. In particular, re-routing everything below assets/ with relative paths would be challenging, and it would require changes in the library as well.

That makes sense. Presumably this is the root URL controlled by product.wondergemRoot? I'm just thinking that the easy fix here would be to relocate the assets from /assets to /ui/assets using a dispatcher that runs text/html pages through the existing templating engine as is already done in src/main/resources instead of src/assets. It would then be a case of simply doing a find/replace on /assets to @wondergemRoot/assets so that the correct path gets injected into the page.

Are there still paths not covered by your configuration?

I did a quick check and the only thing I spotted that doesn't work so far is adding a new bucket through the UI. However this is not important for our setup here, since when deploying to our test environment, the buckets (and content) are pre-seeded with data from a .tar.gz file.

Hello @mcayland! Unfortunately, the structure of Sirius is more complicated. Effectively, Sirius wraps netty. Whenever a request comes in, a sorted list of WebDispatcher instances is traversed, and asked to handle it. One of them is the AssetsDispatcher which handles everything beneath /assets. Moving the assets to a different directory requires to change the existing dispatcher, or a new one. This is feasible, of course, see the S3Dispatcher in this project, but I am reluctant to do it as it bloats the code only to support a not-so-common setting.
wondergem comes in at a later stage. Another dispatcher is the ControllerDispatcher that is checked with lower priority. Effectively, this dispatcher handles routes that are defined via methods marked with @Routed annotations residing in instances of Controller. See, for instance, the NinjaController in this project. Within such a method, the template engine tagliatelle/pasta/noodle can be used to generate output of any sort, but mostly HTML pages. In order to serve pages in a unified manner, we have two template libraries, the older wondergem with table-based layout, and the more recent tycho with card-based layout.
Bucket creation works via /ui/<bucket>?create. If you can open a bucket, you should be able to create one as well. 🤔 Do you encounter an error when attempting to create a bucket?

Closing this due to inactivity.


Fix for reszie in browser

What does the pull request do?
This solves a problem where last resize events were missed, resulting in incorrect canvas size.
Fixed issues
Fixes #12298

@dotnet-policy-service agree


Ledger Nano S/X Integration

Integration of MHW with Ledger Nano S and Nano X.

Officially submitted to Ledger for review. Pending their firmware upgrade and testing.


How to get currently used localization / locale

Is there any way to get the current used localization / locale?
Lest say I have localization files for en and de. My phone language is set to Swedish. How should I know which localization (language) my app is currently using?
Using I18n.currentLocale() Im able to get the phone current locale, but that is not the same as what localization my app is using.

What you want is something I18n.currentTranslation(), which is sadly not available in i18n-js.
But you can recreate it easily:

import I18n from 'react-native-i18n'

import en from '../locales/en'
import fr from '../locales/fr'

// Enable fallbacks if you want `en-US`
// and `en-GB` to fallback to `en`
I18n.fallbacks = true

// Available languages
I18n.translations = { en, fr }

const getUsedTranslation = () => {
  const availableTranslations = Object.keys(I18n.translations)
  const defaultLocales = I18n.locales.default()
  const currentLocale = defaultLocales.find(l => l in availableTranslations)

  return typeof currentLocale !== 'undefined'
    ? currentLocale
    : I18n.defaultLocale
}

In that case I would refactor it like this: 🎉
const getUsedLocale = () => {
  const usedLocale = I18n.locales.default().find(l => l in Object.keys(I18n.translations));
  return usedLocale || I18n.defaultLocale;
};

@henrikra You fire Object.keys at each iteration of I18n.locales.default() 😛

True 👍  I think this will make difference at if the array is like 1 000 000 000 items long :D

Thanks @zoontek 👍


node-pre-gyp angry

apparently node-pre-gyp demands more config
node-pre-gyp --nodedir=~/Documents/io.js/ rebuild
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using<EMAIL_ADDRESS>node-pre-gyp info using<EMAIL_ADDRESS>| darwin | x64
node-pre-gyp ERR! clean error
node-pre-gyp ERR! stack Error: v8-profiler package.json is not node-pre-gyp ready:
node-pre-gyp ERR! stack package.json must declare 'binary.template'
node-pre-gyp ERR! stack     at validate_config (/usr/local/lib/node_modules/node-pre-gyp/lib/util/versioning.js:79:25)
node-pre-gyp ERR! stack     at Object.module.exports.evaluate (/usr/local/lib/node_modules/node-pre-gyp/lib/util/versioning.js:95:5)
node-pre-gyp ERR! stack     at clean (/usr/local/lib/node_modules/node-pre-gyp/lib/clean.js:15:16)
node-pre-gyp ERR! stack     at Object.self.commands.(anonymous function) [as clean] (/usr/local/lib/node_modules/node-pre-gyp/lib/node-pre-gyp.js:53:37)
node-pre-gyp ERR! stack     at run (/usr/local/lib/node_modules/node-pre-gyp/bin/node-pre-gyp:72:30)
node-pre-gyp ERR! stack     at doNTCallback0 (node.js:407:9)
node-pre-gyp ERR! stack     at process._tickCallback (node.js:336:13)
node-pre-gyp ERR! stack     at Function.Module.runMain (module.js:473:11)
node-pre-gyp ERR! stack     at startup (node.js:117:18)
node-pre-gyp ERR! stack     at node.js:952:3
node-pre-gyp ERR! System Darwin 14.4.0
node-pre-gyp ERR! command "/usr/local/bin/iojs" "/usr/local/bin/node-pre-gyp" "--nodedir=~/Documents/io.js/" "rebuild"
node-pre-gyp ERR! cwd /Users/bradleymeck/Documents/test/v8-profiler
node-pre-gyp ERR! node -v v3.0.1-pre
node-pre-gyp ERR! node-pre-gyp -v v0.4.2
node-pre-gyp ERR! not ok

node-pre-gyp -v v0.4.2?
Why you use so outdated version?

@3y3 npm -g i node-pre-gyp gave me that version, today with node at 3.0.1-pre


ci: Do not run code coverage on forks

What?
Code coverage job will fail on forks since they cannot upload results to
Codecov. This adds a condition to control if the job should run or not. For
more details see GitHub Actions docs:
https://docs.github.com/en/actions/using-jobs/using-conditions-to-control-job-execution

Thanks for the PR, that's very useful!


[] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced via:
./hack/update-deps.sh --upgrade --release v0.21
./hack/update-codegen.sh

Details:
bumping knative.dev/networking 07536a6...dcc8744:
  > dcc8744 Remove out-of-date documentation (# 336)
  > 4751606 upgrade to latest dependencies (# 335)
bumping knative.dev/pkg 75d66b5...1bbf0a6:
  > 1bbf0a6 add LabelSelector to InformerFactory so that the informers only list and watch resources with the given labels (# 1940)

/lgtm
/approve

/lgtm
/approve


Fixed typo, Reporter::ChefServer does not exist.

Description
Line 241 calls Reporter::ChefServer however, this class doesn't exist.
I believe this should be Reporter::ChefServerCompliance based on the pattern of other reporters,  that Reporter::ChefServerCompliance exists, and this change resolves the error on my Chef Server.
Bumped to version 4.0.2 as I submitted PREQ #235 which bumps the version to 4.0.1.
$ grep Reporter:: files/default/handler/audit_report.rb
          Reporter::ChefAutomate.new(opts).send_report(report)
            Reporter::ChefServerAutomate.new(opts).send_report(report)
            Reporter::ChefCompliance.new(opts).send_report(report)
            Reporter::ChefServer.new(opts).send_report(report)
          Reporter::JsonFile.new({ file: path }).send_report(report)

Issues Resolved
#234
Check List

[X] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing. (N/A: Bug Fix)
[x] New functionality has been documented in the README if applicable (N/A: Bugfix)
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Thank you @qubitrenegade I rebased and removed the version bump in #253


Move jax.numpy's implementation into a private jax._src directory.

This PR is an experiment in adopting a Haiku-like convention where we separate the implementation of (a part of) JAX into a private _src directory, and use a public shim library as the interface.

I like this change. Is there a specific aspect that you want feedback on?

I mostly want agreement that we are happy with this layout, given this will be a disruptive change (e.g., it will cause merge problems for a bunch of outstanding PRs.)


refactor: validate cloudevent version agnostic

Proposed Changes

Simplify CE validation

Description

Fixes part of https://github.com/cloudevents/sdk-javascript/issues/273

Looks good to me. But I don't understand how it "fixes" #273 really.

I'd expect the Binary/Structured Receiver to be really easy to setup. A developer shouldn't need to know about what mode the CloudEvent is in when receiving.

This PR doesn't really have any impact on the end user experience. So maybe you can clarify what you mean here.

It doesn't fix #273, it's just helping for future PRs that allow for #273 to be fixed. Fixing #273 directly is a little bit more complicated as it touches many areas of the SDK.


Prisma fails to generate client using<EMAIL_ADDRESS>

Describe the Bug
Prisma fails to generate its client when<EMAIL_ADDRESS>is installed.
To Reproduce

Install Prisma<EMAIL_ADDRESS>Add typegraphql-prisma to the list of generators.
Attempt to generate the Prisma client.
The generator errors and enters into an infinite loop.

Expected Behavior
The Prisma client generates as expected.
Logs
Modified the project name to realproject - exposing it allows you to trace my IRL identity!
prisma:GeneratorProcess Error: Cannot find module 'fs-jetpack' +0ms
  prisma:GeneratorProcess Require stack: +0ms
  prisma:GeneratorProcess -<EMAIL_ADDRESS>+0ms
  prisma:GeneratorProcess -<EMAIL_ADDRESS>+0ms
  prisma:GeneratorProcess - /Users/skyezer/Projects/realproject/database/node_modules/typegraphql-prisma/lib/cli/prisma-generator.js +0ms
  prisma:GeneratorProcess - /Users/skyezer/Projects/realproject/database/node_modules/typegraphql-prisma/lib/cli/generator.js +0ms
  prisma:GeneratorProcess - /Users/skyezer/Projects/realproject/database/node_modules/typegraphql-prisma/lib/generator.js +0ms

Environment (please complete the following information):

OS: macOS Big Sur 11.3.1
Node v16.6.1
typegraphql-prisma version 0.18.4
Prisma v3.6.0 and 3.8.0 (likely affects other versions, only tested these two)
TypeScript version 4.5.4

Additional Context
Appears to be directly related to https://github.com/prisma/prisma/issues/11112, fixed in<EMAIL_ADDRESS>(unreleased, but dev builds exist). Caused by<EMAIL_ADDRESS>upgrade to<EMAIL_ADDRESS>Project is setup to use yarn workspaces, with a database project exposing the generated prisma client and typegraphql resolvers, for use in the backend and web crawler projects.

yarn add  -D fs-jetpack

My temporary fix is just to revert to v0.18.3.

 I'll close this issue for now!

Just to let you know that https://github.com/prisma/prisma/issues/11112 was fixed in Prisma patch version 3.8.1


Set up GitLab CI/CD for GitHub

Travis CI has been set up as part of #105, and is working. However even for the quicktest it takes on the order of 30 mins to run, due to the lack of GPUs.
A viable option for using GPUs is GitLab CI/CD for GitHub. Setting it up boils down to the following steps:

[ ] Connect GitHub project to GitLab
[ ] Create a personal access token on GitHub and activate it on GitLab
[ ] Register the Adelie runner on GitLab

Here is first test case where this was set up: https://github.com/NifTK/NiftyNet/issues/105#issuecomment-395312242
We should also decide what to do with the #105 changes. @wyli Do you see any value in keeping Travis?
In any case, we should probably continue using tox, as it allows for easy multi-Python-version testing. But maybe we should address this in another issue, to keep things simple.

Travis I think yes, because Gitlab to Adelie access is not immediately available after the move

[ ] Connecting GitHub project to GitLab fails with An error occurred while importing project: Error: Request failed with status code 422

[ ] how does this work for forks?

@wyli See the above green tick :) Please click and confirm that you can access it on gitlab.com
Also, I've added a TODO to check how this integration works with forks. If you can think of anything else that needs to be checked, please add a TODO for it.

@wyli I've dug a bit deeper into the GitLab integration with GitHub for CI/CD. It looks like it's set up only to build the tip of the branches of the original repository, and not of any forks. This might be due to security reasons. However being able to run CI/CD pipelines for pull requests is in my opinion essential with regards to catching regressions. So I've submitted a feature request on GitLab.
In the meantime, I suggest the following to enforce CI:

We add all active developers as "contributors" to this repository so that they can work on branches directly and not forks.
We merge each PR from forks onto a new branch tagged with that PR number (e.g. pr-123-bla-bla-bla), which should trigger the pipelines for that branch.

if checks pass: merge the PR into the main branch, and delete the PR branch
if checks fail: fix the code to make the checks pass

What do you think?
Adding @tomdoel to this discussion as well.

Sounds good @dzhoshkun, I'll update CONTRIBUTING.md and close this issue.


Remove lombok dependency in dao module

What is the purpose of the pull request
this pr is for remove lombok dependency in dao module
the getter & setter & toString method is already exist

Codecov Report

Merging #1683 into dev will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev    #1683      +/-   ##
==========================================
+ Coverage   15.09%   15.09%   +<.01%
==========================================
  Files         283      283
  Lines       13801    13796       -5
  Branches     2244     2239       -5
==========================================
  Hits         2083     2083
+ Misses      11496    11491       -5
  Partials      222      222

Impacted Files
Coverage Δ

...g/apache/dolphinscheduler/dao/entity/Schedule.java
0% <ø> (ø)
:arrow_up:

...pache/dolphinscheduler/dao/entity/WorkerGroup.java
0% <ø> (ø)
:arrow_up:

...a/org/apache/dolphinscheduler/dao/entity/User.java
0% <ø> (ø)
:arrow_up:

...he/dolphinscheduler/dao/entity/UserAlertGroup.java
0% <ø> (ø)
:arrow_up:

...dolphinscheduler/dao/entity/ProcessDefinition.java
0% <ø> (ø)
:arrow_up:

...ache/dolphinscheduler/dao/entity/TaskInstance.java
0% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Support python 2 and 3

Goal
Support both python version 2 and 3.
Design
This seems to be the simplest way of support both versions. There are other ways, but this felt good.
Changeset

Minor fix for missing headers if an error occurs
Support both python 2 and 3
Add info about python 3 support

Testing
Did some curl based tests with versions 2.7.18 and 3.8.10

Hi @bix0r,
Thanks for this. We are going to look to get this reviewed and merged in as soon as priorities allow.

Published as v1.3.0


Feature Request: Honor/inherit scrExclude from VitePress

Right now, excludePattern allows you to define file/directory exclusions based on patterns, just like srcExclude does.
It does work fine but, apparently, it requires you to declare both srcExclude and excludePattern (with the same values).
It would be great if VitePress Sidebar could honor srcExclude. That means it would inherit all srcExclude values, which probably makes sense since the srcExclude is declared at a "higher" level than the Sidebar plugin (it affects the whole VitePress project).

Hello, thank you for using vitepress-sidebar and leaving your feedback.
First, based on the current behavior, this plugin does not directly read VitePress' config because it is declared at the themeConfig -> sidebar level, not at the plugin level in Vite. Therefore, we need to find a way to read the settings in the config file to make this work.
For now, if you want to pass the same value with srcExclude, there is a way to define it as a global constant and use it on both sides.
const srcExclude = ['**/README.md', '**/TODO.md'];

export default defineConfig({
  title: 'VitePress Sidebar',
  srcExclude: srcExclude,
  themeConfig: {
    sidebar: generateSidebar({
        documentRootPath: '/docs',
        excludePattern: srcExclude,
      };
    }),
  }
});

It doesn't seem likely that this issue will be addressed quickly, but we'll keep it open for future reference for others.
Regards,


Implement low-memory image creation

Currently outputs are created using the built-in thumbnail function from the image crate. This is great to get things up and running, but in cases where the input file is large we should instead compute the the output image directly.
Since we know the input size and the desired output, we can define operations to map relevant input data to each output pixel.
This is done for SICD data, need to make things more generic or copy-pasta for other image types.
The brunt of this work is just going to be sorting out the array shape required to efficiently iterate over the image. As an initial pass, only implement non-blocked and 'simply blocked' (I don't remember the NITF parameter combination for this, but most data seems to be written like this)

This is done for SICD data, need to make things more generic or copy-pasta for other image types.

Done in #5


Create end-to-end example of using NATS in Unity

Hi @wallyqs , I am interested in learning about this project and want to work on this project under LFX Mentorship.
Please let me know about any materials or resources that I should learn to get a better understanding of the project and its requirements.
Additionally, I was wondering if there is anything else I can do to get started, such as research and learn about the project from the existing documentation.

Hey @wallyqs , I've had some experience with unity before and I'd love to work on this project while gaining more exposure to Unity and other stuffs related to the project.
So if you have any resources regarding the same I would love to go through it to in order to get better understanding of the project

Hi @wallyqs I am interested in working in this project, I have some experience in videogames, you can find some of my projects in this youtube playlist: https://youtube.com/playlist?list=PLnQePnPLK2QBgubSl7uaU176-ouU0FPJn ,some of them are made in Unity, some other with XNA C# and other technologies. Furthermore, I have also taken two CCNA courses related with networks, such as "CCNA 1: Introduction to networks" and "CCNA 2: Switching, routing and wireless essentials".
I am interested in learning about NATS and also learning about open-source development.
Link to my github account: https://github.com/JesusGH123

Here I created an example of using NATS with Unity
https://github.com/JesusGH123/Nats-blitz


PDF formatted docs for LiqCoolingBaseline, RearDoor, RackPDU and GPU

PDFs were autogenerated from Markdown files.

Approved to merge.


Self-nominating as a reviewer member of KubeVela Org

Hi guys. I want to nominate myself as the reviewer of KubeVela Org.
I have explored many repositories of KubeVela Org and I highly agree with KubeVela's philosophy and feel the enthusiasm of the community, I'd like to contribute ideas and code in the coming days.
If I can continue to build the community as a reviewer, I'll feel very honored. Thanks to the people who have helped me.

These are my contributions so far:

https://github.com/kubevela/kubevela/pull/4819
https://github.com/kubevela/kubevela/pull/4849
https://github.com/kubevela/catalog/pull/493
https://github.com/kubevela/catalog/pull/494
https://github.com/kubevela/kubevela.io/pull/986
https://github.com/kubevela/kubevela.io/pull/990
https://github.com/kubevela/kubevela.io/pull/989
https://github.com/kubevela/kubevela.io/pull/991
https://github.com/kubevela/kubevela/issues/4820
https://github.com/kubevela/kubevela/pull/4850
https://github.com/kubevela/kubevela.io/pull/1001

TODO:

Add source ComponentDefinition for fluxcd plugin
Support sourceName for kustomize
Update Ingress apiVersion from networking/v1beta1 to networking/v1 in velaql
(idea) add KubeFlow plugin

LGTM, great job

LGTM, thanks for contributing!

ping @barnettZQG @Somefive @chivalryq

LGTM, Much meaningful work has been done.

LGTM

LGTM. Thanks for your work!

@chengleqi Hi, you can raise a pull request to add yourself as reviewer member now, congratulations!

Thanks everyone, I appreciate it!


ecs: address #6635 by adding the spawn_id fn

Addresses #6635
Does not introduce any breaking change.

I don't like the addition of this method: it's a common pattern, but this doesn't make anything clearer or much shorter.
Not your fault: the code itself is correct.

Unless we find a very good name for this method, I would prefer to not add it

Considering the initial and valid pushback, I'll close the PR


How to convert the end-effector position to image pixel co-ordinates ?

Hey Paul,
I am working on a project where I need to convert the end-effector position (normalized from -1 to 1) from Mujoco environment to coordinate in the image rendered in Mujoco.
I am not sure how to do it. Could you help me ?

Hey, sorry for the late reply.
Did you have a look at https://github.com/PaulDanielML/MuJoCo_RL_UR5/blob/master/gym_grasper/controller/MujocoController.py#L761-L781 yet?
Not sure if this is what you are looking for, let me know


Tooltip Issues

[x] Tooltips are showing up in different places on the UI, tooltips should always show in same spot.  Some have no space between the tip and the header, some have space... other are in middle or at the end of the field.  Consistent sizing, spacing & placement

[x] Some tooltip don't work (Scaling/Upgrade policies on create workload)

[ ] Some tooltips don't make sense (this is mostly for the charts, but all the tooltips should be gone through and made sure they are useful)

fixed


Buffer Manipulation Regression

What did you expect to happen?
Managing buffers to work properly:

Killing buffers when in a tab to kill a buffer only when using SPC-b-d
Show other workspace buffers when using SPC-b-b
Kill other buffers when using SPC-b-O
Show doom-dashboard when starting a new window or killing buffers

What actually happened?
Buffers not working properly:

Entire tab window is killed when running SPC-b-d
0 workspace buffers are present, but shown in ibuffer
0 buffers are killed even when other buffers are present
doom-dashboard does not show, only the scratch buffer is shown

Additional details:
Personal Config
View Echo Area Messages
Starting Emacs daemon.
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) [2 times]
define-obsolete-function-alias: Wrong number of arguments: (3 . 4), 2
When done with this frame, type SPC q f
Buffer is read-only: #<buffer  *Treemacs-Scoped-Buffer-Perspective #1*>
o p is undefined
SPC ESC is undefined
Error in minibuffer-exit-hook (+ivy--set-jump-point-maybe-h): (void-variable +ivy--origin)
Switched to ’MPA2’
Loading /home/ohhskar/.emacs.d/.local/cache/recentf...done
Note: c-basic-offset, tab-width, evil-shift-width adjusted to 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) [2 times]
File mode specification error: (doom-hook-error +cc-init-rtags-maybe-h (wrong-number-of-arguments (3 . 4) 2))
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) [2 times]
Error in post-command-hook (rtags-post-command-hook): (wrong-number-of-arguments (3 . 4) 2)
Quit
SPC ESC is undefined
Note: c-basic-offset, tab-width, evil-shift-width adjusted to 2
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) [2 times]
File mode specification error: (doom-hook-error +cc-init-rtags-maybe-h (wrong-number-of-arguments (3 . 4) 2))
Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) [2 times]
Error in post-command-hook (rtags-post-command-hook): (wrong-number-of-arguments (3 . 4) 2)
Quit
Updating buffer list...
Formats have changed, recompiling...done
Updating buffer list...done
ibuffer-projectile: groups set
Commands: m, u, t, RET, g, k, S, D, Q; q to quit; h for help
Quit [5 times]
Killed 0 other buffers [2 times]
Quit [2 times]
evil-line-move: Beginning of buffer [2 times]

Steps to reproduce:

Start a new emacs instance ( Doom-dashboard not showing here)
Open a project and initial buffer SPC p p
Open a new buffer
3.1  using Dired SPC o -
or
3.2  using treemacs SPC o p
Kill other buffers SPC b O (0 buffers killed)
Try to change to another buffer in works SPC b b (0 workspaces shown)
Kill a buffer in tab SPC b d (Entire tab window killed)

System information:

SYSTEM  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      /usr/bin/fish
        uname      Linux 5.10.7-arch1-1 #1 SMP PREEMPT Wed, 13 Jan 2021 12:02:01 +0000 x86_64
        path       (~/.local/share/nvm/v15.6.0/bin /usr/local/sbin /usr/local/bin /usr/bin /usr/lib/emacs/28.0.50/x86_64-pc-linux-gnu/)
EMACS   dir        ~/.emacs.d/
        version    28.0.50
        build      Jan 17, 2021
        buildopts  --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --mandir=/usr/share/man --with-gameuser=:games --with-sound=alsa --with-modules --without-gconf --without-gsettings --with-nativecomp --with-pgtk --with-x-toolkit=gtk3 --without-xaw3d --without-m17n-flt --with-cairo --with-xwidgets --without-compress-install 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -g -fuse-ld=gold' CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now
        features   JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GLIB NOTIFY INOTIFY ACL GNUTLS LIBXML2 FREETYPE HARFBUZZ LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 PGTK XIM MODULES NATIVE_COMP THREADS XWIDGETS LIBSYSTEMD JSON PDUMPER LCMS2
        traits     (gui daemon server-running envvar-file)
DOOM    dir        ~/.doom.d/
        version    2.0.9
        font       #
        theme      doom-tomorrow-night
        build      grafted, HEAD -> develop, origin/develop, origin/HEAD b03fdabe 2021-01-13 14:07:47 -0500
        elc-files  0
        modules    (:completion company ivy :ui doom doom-dashboard hl-todo indent-guides modeline ophints (popup +defaults) treemacs vc-gutter vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold (format +onsave) snippets :emacs dired electric ibuffer undo vc :checkers syntax spell :tools (eval +overlay) lookup magit :lang cc emacs-lisp javascript markdown org sh web :config (default +bindings +smartparens))
        packages   (n/a)
        unpin      (n/a)
        elpa       (n/a)

I'm inclined to believe this is a Emacs 28+ issue based on #4534 as the same errors occur: Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2).

I'm inclined to believe this is a Emacs 28+ issue based on #4534 as the same errors occur: Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2).

It is indeed a duplicate of #4534. Your other issues are likely a result of the error. See #4534 for a workaround.

It is indeed a duplicate of #4534. Your other issues are likely a result of the error. See #4534 for a workaround.


fix gradle 7

@AvidanBaruchiN don't forget to create a tag and a release.
And we should updae in rhe capacitor beta branch to the new tag.


InputChips does not have restProps

Current Behavior
i found out that InputChip does not have restProps implemented as the page says:

First i tried to add an aria-label but it didnt work, so went into the source code and it wasnt there
Expected Behavior
It's actually really simple, FileDropzone uses prunedRestProps() to add the props to the input inside the component:

while InputChip does not have it:

Steps To Reproduce

using InputChip
add any aria-label to it
inspect the input in any browser, its not there

Link to Reproduction / Stackblitz
https://stackblitz.com/edit/stackblitz-starters-9nyhrh?file=src%2Froutes%2F%2Bpage.svelte
More Information
adding the prunedRestProps function
  function prunedRestProps() {
    delete $$restProps.class;
    return $$restProps;
  }

and {...prunedRestProps()} to the input fixes the issue, this code is already in FileDropzone

We've technically decided to put Skeleton v2 into a Feature Freeze. In theory, this might be small enough to still make the cut, but I'd like to wait for Chris verdict.

As Sarenor linked above, neither the team or myself have the bandwidth to maintain Skeleton v2 at the moment. So a pull request is welcome here if you would like to see this resolved in the short term. Either from you Skydow, or any other volunteer.


Arrow format string for format_str in _dtype_from_vaexdtype()

The code now uses NumPy format strings, while the docs for Column.dtype specify it must use the format string from the Apache Arrow C Data Interface (similar but slightly different). So we need a utility to map NumPy to Arrow format here.
Example - should say 'b' not |b1':
df = pd.DataFrame({"A": [True, False, False, True]})

>>> df.__dataframe__().get_column_by_name('A').dtype
(<_DtypeKind.BOOL: 20>, 8, '|b1', '|')

Source:
https://arrow.apache.org/docs/format/CDataInterface.html#data-type-description-format-strings
https://numpy.org/doc/stable/reference/arrays.interface.html#arrays-interface
https://numpy.org/doc/stable/reference/generated/numpy.dtype.itemsize.html
https://numpy.org/doc/stable/reference/generated/numpy.dtype.byteorder.html

@honno could you please verify that https://github.com/data-apis/dataframe-interchange-tests has a test checking that the format strings used in each dataframe library are indeed in Arrow format now?
xref https://github.com/data-apis/dataframe-api/pull/62, which has a basic test that may be reusable in case you don't yet have one.

could you please verify that https://github.com/data-apis/dataframe-interchange-tests has a test checking that the format strings used in each dataframe library are indeed in Arrow format now?

I had left it as a TODO, but just now updated test_dtype to test that the format strings are in Arrow format (for the most part—will explore testing some trickier scenarios later). I found vaex and cuDF were returning the NumPy-style format strings and filed issues respectively.

Thanks @honno. I think we are good here then. I double checked for Pandas, and that looks as expected:
>>> import pandas as pd
>>> pd.__version__
'1.5.0rc0'
>>> df = pd.DataFrame({"A": [True, False, False, True]})
>>> df.__dataframe__().get_column_by_name('A').dtype
(<DtypeKind.BOOL: 20>, 8, 'b', '|')

Let's close this. Thanks @AlenkaF and @honno

When demoing the dataframe protocol at EuroScipy, I actually ran into this, seeing that Vaex is returning a wrong value:
import vaex
df_vaex = vaex.example()[:1000]
df_obj = df_vaex.__dataframe__()
col_obj = df_obj.get_column_by_name("x")
col_obj.get_buffers()

gives
{'data': (VaexBuffer({'bufsize': 4000, 'ptr':<PHONE_NUMBER>14344, 'device': 'CPU'}),
  (<_DtypeKind.FLOAT: 2>, 32, '<f4', '<')),
 'validity': None,
 'offsets': None}

And so the third entry in the dtype tuple "<f4" is wrong, it should be "f" instead (it seems this is just the numpy descriptor).
So while this might now be tested in dataframe-interchange-tests, is this failing or skipped there? And are there issues in the libraries to keep track of this?

So while this might now be tested in dataframe-interchange-tests, is this failing or skipped there? And are there issues in the libraries to keep track of this?

Ayup, issue filed in https://github.com/vaexio/vaex/issues/2139, and it's failed in the test suite
https://github.com/data-apis/dataframe-interchange-tests/blob/73e4f74eb53eb04bc9632ea243d8b167c458dbfe/tests/conftest.py#L77-L79

Thanks!


updates punctuation for translations

What's this PR do?
updates po & pot files. added strings to POEditor to account for punctuation, translated and exported the po file to be uploaded.
How should this be reviewed?
...
Any background context you want to provide?
...
Relevant tickets
Fixes #
Checklist

[ ] Documentation added for new features/changed endpoints.
[ ] Tested on staging.
[ ] Pinged a PM if this is a larger PR that would benefit from some additional testing love
[ ] Post a message in #phoenix if this includes something that causes a rebuild!

@weerd just realized that I have no idea where all the 'month of the year' stuff is coming from?

@weerd re-uploaded


Specify a token while creating token

Proposal:
Specify a token while creating token.
Current behavior:
Describe what currently happens.
Desired behavior:
i want to specify token while creating token
Alternatives considered:
Use case:

Purpose, is to have same token over multiple influxdb servers.
When you are behind a F5 load balancer, whenever the choosen backend server, the request will always been authorized.
Same purpose here : https://github.com/influxdata/influxdb/issues/21478
Or do you have another solution for this ? (except cluster commercial one)

@wangshuang0220 can you elaborate a little bit on your desired behavior? As it is, to create a token, you do need to specify an existing token to authorize the request.

Purpose, is to have same token over multiple influxdb servers.
When you are behind a F5 load balancer, whenever the choosen backend server, the request will always been authorized.
Same purpose here : https://github.com/influxdata/influxdb/issues/21478
Or do you have another solution for this ? (except cluster commercial one)

Update ?


Allow disabling ligatures in Text

List of Changes

Allow users to disable ligatures and also fix Code with it.
Revert https://github.com/ManimCommunity/manim/pull/798
number of submobjects = number of chars if ligaratures are disabled.

Explanation for Changes
Better than using CairoText.
Testing Status

Acknowledgement

[x] I have read the Contributing Guidelines

After a provisional skimming, this looks good in general. I have to take a closer look. Could you please add a couple of tests?

This looks good to me, I also seem to be able to use a monospace font without problems:

Testing Code is a bit tedious as long as we are not able to pass code directly, but have to read a corresponding file. I'd be okay with delegating adding tests to a later point in time where the interface of Code has been refactored a bit.
I'm on the fence whether we should use the current implementation using CairoText for the release, or whether we should get this in before. I probably have a slight preference for merging it after the release.

I will only see a simple problem with this. This will not allow passing something like Arabic, or Hindi or some font which heavily depends on ligatures, from within the code and will look worse. This could be a fix for a short time but this definitely needs to be refactored so that Pango takes the responsibility of colouring it (which it does) instead of manipulating the arrays. But this can't be done for now as our SVG parser ignore style element without which it is not possible. One way it can be fixed is to make it not inherit from SVGMobject instead inherit directly from VMobject and provide methods for working directly with Pango which definitely requires a lot of work though. Also, the present bindings don't support Pango.Attributes without which this can't be done. So, that would require pangocffi to support that.

This will not allow passing something like Arabic, or Hindi or some font which heavily depends on ligatures, from within the code and will look worse.

This is why I'm fine with using this fix for CodeMobject, but not for Text itself. I agree this should only be a temporary fix.
Point taken on the tests.
Given the absence of tests, I vote we merge this right after the release.

Ready for review.

@naveen521kk could you please solve the merge conflict? :slightly_smiling_face:

I didn't expect this lol. Will do no worries 😊

@leotrs done. Also, typed(python typing) a few things.


buttons got inverted after latest ff update

Thanks for pointing out! This should be fixed in the latest release.


Fix compile error when disable-faultinjector

A compile error will occur when --disable-faultinjector option is added to the compilation parameters.
Discussion: https://github.com/cloudberrydb/cloudberrydb/issues/555

fix #ISSUE_Number

Change logs
Describe your change clearly, including what problem is being solved or what feature is being added.
If it has some breaking backward or forward compatibility, please clary.
Why are the changes needed?
Describe why the changes are necessary.
Does this PR introduce any user-facing change?
If yes, please clarify the previous behavior and the change this PR proposes.
How was this patch tested?
Please detail how the changes were tested, including manual tests and any relevant unit or integration tests.
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:

[x] Make sure your Pull Request has a clear title and commit message. You can take git-commit template as a reference.
[x] Sign the Contributor License Agreement as prompted for your first-time contribution(One-time setup).
[x] Learn the coding contribution guide, including our code conventions, workflow and more.
[x] List your communication in the GitHub Issues or Discussions (if has or needed).
[x] Document changes.
[x] Add tests for the change
[x] Pass make installcheck
[x] Pass make -C src/test installcheck-cbdb-parallel
[x] Feel free to request cloudberrydb/dev team for review and approval when your PR is ready🥳

fix https://github.com/apache/cloudberry/issues/555


Adding "open robot iniative"

Hi there! Here is a proposal to add the open source robot open robot initiative by @fgrimminger et al. 🤖

[x] I have checked that the build is open
[x] I have checked that the software to control the robot is open

Here is some information about the robot:

Type: Quadruped, Biped
License: CC0-1.0 license
Build instructions: https://github.com/open-dynamic-robot-initiative/open_robot_actuator_hardware
Model: https://github.com/open-dynamic-robot-initiative/open_robot_actuator_hardware
Software: https://github.com/orgs/open-dynamic-robot-initiative/repositories?type=all

Icing on the cake, here is a picture for the gallery:

Robotically,
A. René Geist

Done. Great initiative :smiley:


Fix typo in the variable name in logging.hpp

Codecov Report

Merging #1454 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1454      +/-   ##
==========================================
- Coverage   70.92%   70.92%   -0.01%
==========================================
  Files         142      143       +1
  Lines       19483    19492       +9
  Branches     2385     2385
==========================================
+ Hits        13818    13824       +6
- Misses       4771     4778       +7
+ Partials      894      890       -4

Impacted Files
Coverage Δ

src/core/thread/network_data_leader.cpp
80.09% <0%> (-0.5%)
:x:

src/core/thread/mle_router.cpp
80.06% <0%> (-0.49%)
:x:

src/core/thread/network_data_leader_ftd.cpp
67.99% <0%> (-0.47%)
:x:

src/core/thread/mesh_forwarder.cpp
74.39% <0%> (-0.34%)
:x:

src/core/thread/mle.cpp
81.08% <0%> (-0.22%)
:x:

examples/apps/ncp/main.c
100% <0%> (ø)

src/ncp/ncp_base.cpp
37.93% <0%> (+0.13%)
:white_check_mark:

src/core/mac/mac.cpp
80.59% <0%> (+0.14%)
:white_check_mark:

src/core/net/udp6.cpp
83% <0%> (+1%)
:white_check_mark:

src/core/common/message.cpp
95.43% <0%> (+1.24%)
:white_check_mark:

... and 2 more

Continue to review full report at Codecov.

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


Use encoded/decoded string when serializing / deserializing

Description of change
Calling serde::deserialize should work the same as SdJwt::parse and serde::serialize should work as SdJwt::presentation but RN they just serialize or deserialize the inner structure of SdJwt. This PR fixes this behaviour.
Type of change

Bug fix (a non-breaking change which fixes an issue)

[x] I have followed the contribution guidelines for this project

[x] I have performed a self-review of my own code

[x] I have commented my code, particularly in hard-to-understand areas

[x] I have made corresponding changes to the documentation

[ ] I have added tests that prove my fix is effective or that my feature works

[x] I have checked that new and existing unit tests pass locally with my changes

[x] I have updated the CHANGELOG.md, if my changes are significant enough

On second thought I removed the implementation of Serialize and Deserialize from SdJwt. The problem is that they depend on the representation of the implementer of Serializer and Deserializer. For instance when using serde_json, an sd_jwt encoded value is represented by a JSON string which requires data to be enclosed in double quotes (") and we don't want that. @abdulmth @eike-hass @wulfraem any thoughts?


Feat: watch network changes

Description
Godwoken Bridge can now detect if the current network has changed.
To be noted, these changes are probably not compatible with the PR #201.
Changes

Add event listener to detect if the current network has changed
Add check to prevent adding an already existing network

Changes

Add event listener to detect if the current network has changed
Add check to prevent adding an already existing network


Mixing std::uint64_t and std::size_t

Because of #536 i had a deeper look to your body implementations.
There you mix std::uint64_t and std::size_t.
Is this purpose or mistake?

It is on purpose. Beast supports HTTP messages whose Content-Length is up to 2^64-1 bytes, even when the address model used to build the application is 32-bit (i.e. when std::size_t is 32 bits). So I have been very careful to use std::size_t in places where it makes sense, such as when referring to the size of a dynamic allocation, and to use std::uint64_t when it refers to the size of something specified by the protocol such as the content length.

okay -> close


tests: adc_api: add counter handler to avoid exception

add counter interrupt handler for a valid test cases

this is a workaround for #72080

I am not sure what you are trying to fix but this is not the way to do it

@decsny this is a workaround for https://github.com/zephyrproject-rtos/zephyr/issues/72080, the pit counter driver missing a protestction, if we provide a null callback, this will crash the system.

I am not sure what you are trying to fix but this is not the way to do it

@decsny this is a workaround for #72080, the pit counter driver missing a protestction, if we provide a null callback, this will crash the system.

The top callback is allowed to be NULL in the API, the fact it crashes the system is a bug from the driver. In fact, the fact the test tests this case where the callback is NULL I think is the point of the test. So we should fix the bug rather than stop testing the case that is failing.

The top callback is allowed to be NULL in the API. This is something being tested by the test. We should fix the bug that was caught by the test rather than remove the case from the test that did its job.

@decsny , this adc_dma case is not intented to test the pit callback issue, we need add a case in counter testing.

fix by https://github.com/zephyrproject-rtos/zephyr/pull/72485