Copying Images taking FOREVER

I ran the install.sh and everything was going well until it go to "cp images/dail.png  :images/dial.png"  It says " . . .  copying   9% [#----------]"  and it has been like this for about 30 minutes so far.  Is this normal??

It should not take that long. It has probably disconnected or crashed in some way. You can copy files manually using Thonny to patch things up such as changing the background png for a watch app. You should be able to mount the watch device on Thonny and look at the directories and files.
BTW Impressed that you got some useful advice from ChatGPT.

I was pretty impressed as well.  It got me going perfectly!  I went ahead and unplugged and re-plugged the watch and it looks like everything finished but the watch did not boot.
I can comment out the import loader in the boot.py file, but what does this mean:
"Then, using REPL type import tempos which should load all the drivers and - after a delay - display Loading ... on the watch screen."
How do I do this?

Ok. . . I think I figured out how to get into REPL thanks to chatGPT.  I have done so and typed import tempos and I get the following:
Traceback (most recent call last):
File "", line 1, in
File "./tempos.py", line 3, in
File "./drivers/st7789.py", line 16, in
ValueError: incompatible .mpy file
What are my steps to rectify this?  I just installed mpremote and mpy-cross today so they are the most up-to-date.

I am also getting these problems in the st7789.py driver
Import "micropython" could not be resolved [Ln 11, Col6]
Import "machine" could not be resolved [Ln12, Col6]
Import "framebuf" could not be resolved [Ln15, Col 8]

The error is an incompatibility in the graphics.mpy file. This file uses an micropython.viper directive which requires the cross compiler to pick up the correct architecture option. That is in compile.sh there is a -march=xtensawin option.  Either check this is being picked up by the cross compiler or you can delete the viper directive. The graphics will still work but will be slower.

The import errors may be caused by the same thing.

Cross="my_mpy_cross_path -march=xtensawin"

I saw another issue talking about fixing the viper issue, but I am not fully following what they did to fix it.  Would you mind (when you have a free moment) listing out how I can get the graphics.py recompiled and get the viper working?  I can start from square one if I need as this watch is just a black screen right now anyway.  Again, I am running the V3 watch.

At the command line type
"your path"/mpy-cross -march=xtensawin graphics.py
This will produce graphics.mpy which you can copy to the watch.

Also you check the version of the cross compiler with
"your path"/mpy-cross -version


get ssl and tcp time

can i get  ssl time and tcp time of http connection？

Canonical issue: #243


Entity disappearing when leaving home

I have a Bluetooth beacon attached to my dogs collar and this seems to working fine being picked up by my ESP32 BLE proxies around the house.
However when the beacon leaves the house and returns it seems to fall off and the entities become unavailable.
Using a BLE scanner on my phone I can see the beacon is still active
Some info and diagnostics below the device address is CB:B8:99:BD;E2:C9

config_entry-bermuda-01JA8XNHWNCZF52N0NQV8289XP (1).json

Hi Chris! Thanks for your report.
I think this might be fixed already in v0.6.9rc2 - it might be the same issue as #235
Can you turn on "Enable Beta versions" in HACS, and update your Bermuda to v0.6.9rc2 to see if it solves it for you?
I'll close this for now just because I am having difficulty tracking which issues I need to act on, but please feel free to re-open it if the problem still happens.

Thanks for getting back to me on this.
I've updated to the latest version and the entity does not disappear any longer.
However this beacon still drops off the network and won't be found again by Bermuda upon returning but will show in a scanning app on my phone so I'm not really sure what is happening with it.
I've attached a debug log if its helpful.
Thanks
config_entry-bermuda-01JA8XNHWNCZF52N0NQV8289XP (2).json

Hi Chris, thanks for your patience. I can see the "CityFinder" tag in the bluetooth backend in the diagnostics, but for some reason it's not being picked up by Bermuda. The latest advert was over 60 seconds ago though, had you maybe reloaded bermuda or restarted HA within a minute of doing the download diagnostics, perhaps? I often recommend that because some systems get bogged down creating the diagnostics after a long run-time. I can't think of other reasons for Bermuda not having put it into its history yet.
Could you share some screenshots of your phone bluetooth scanner? I assume you're using a scanner, but if you're using the app for the tag that could also be the issue, many BLE devices stop advertising once they are "connected" to something, so that's something else to check on.
It's probably worth updating to the release I put out today, v0.7.0, as it includes some other fixes, but nothing I can think of that would be directly related to your issue here.

Hey thanks for the update.
I'll do some more investigation and update to the latest version
I've added a shot from my phone app below

Hi Chris, I just released v0.7.1, and it contains some fixes which might be relevant to the issue you're seeing, in particular the way metadevices (ie, iBeacons and IRK devices) were treated. If you are able to try out 0.7.1, and if it still happens, could you send me a diagnostics taken shortly after returning home with the tag?


Prevent Room Member Badly Removed

This is linked to https://github.com/matrix-org/matrix-ios-sdk/issues/341
Signed-off-by: Jean-Philippe Rouault<EMAIL_ADDRESS>

To be checked if there is no impact with back pagination management.

This PR was a workaround on client to fix https://github.com/matrix-org/matrix-ios-sdk/issues/341 but this bug has been fixed server side.


WIP: Documentation

First draft for the documentation using sphinx. Work-in-progress.
Once finished, we can use Read the Docs to host the documentation.
For more explanations, see docs/README.md.
TODOs:

[ ] Classify and add documentation for some flows
[ ] Add documentation to classes/functions without documentation
[ ] Update and move example notebooks to examples
[x] Add all requirements to docs/requirements.yaml
[ ] Host using Read the Docs

Looks great! This is a great jumping-off point. Will merge this now. We can work on your open TODOs down the road.


Provide information when keytar fails due to in-availability of libsecret on linux

Receiving the following error when trying to log in to Grammarly:

Command 'Grammarly: Login to grammarly.com' resulted in an error (GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files)

And the extension does not show any issues highlighted even though on the Grammarly website there are 2 issues in that text.
I am running the extension version 0.12.1 on NixOS Linux.

I am also not able to login to grammarly. I get the same error as pointed above.
Using the extension (after downloading the vsix file) in linux.

@znck --- can you please help how to resolve this issue?

Need more information. Can you share extension log?

Extension version: 0.12.2 installed through vsix method
Vscode version: 1.45.1
Operating system: Manjaro Linux
When I execute the command Grammarly: Login to grammarly.com say on a text file, the extension does not produce any log. However, the following notification is shown:
Command 'Grammarly: Login to grammarly.com' resulted in an error (GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files)

When I execute the command Grammarly: Check grammar errors, I get the following log:
(node:3118) UnhandledPromiseRejectionWarning: Error: Request $/credentials failed with message: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
    at handleResponse (/home/bhatta/.vscode/extensions/znck.grammarly-0.12.2/out/server.js:5232:48)
    at processMessageQueue (/home/bhatta/.vscode/extensions/znck.grammarly-0.12.2/out/server.js:5059:17)
    at Immediate.<anonymous> (/home/bhatta/.vscode/extensions/znck.grammarly-0.12.2/out/server.js:5043:13)
    at processImmediate (internal/timers.js:439:21)
(node:3118) UnhandledPromiseRejectionWarning: Error: Request $/credentials failed with message: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
    at handleResponse (/home/bhatta/.vscode/extensions/znck.grammarly-0.12.2/out/server.js:5232:48)
    at processMessageQueue (/home/bhatta/.vscode/extensions/znck.grammarly-0.12.2/out/server.js:5059:17)
    at Immediate.<anonymous> (/home/bhatta/.vscode/extensions/znck.grammarly-0.12.2/out/server.js:5043:13)
    at processImmediate (internal/timers.js:439:21)
(node:3118) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 13)
(node:3118) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 13)

Let me know if you need any further information. Thanks

VS Code uses keytar to store secrets (Grammarly password in our case). Do you have libsecret (required by keytar) installed on your system?

My OS has libsecret (V 0.20.3).
Moreover, in the setup of this extension, where should I be providing/putting the Grammarly userID and password? Should I be mentioning it in settings.json?  (Checked the extension documents; nowhere this is mentioned.)

Command Grammarly: Login to grammarly.com would launch an input prompt for username/password.

In that case, I am not sure what is the problem. Because I have libsecret and I get the above mentioned error (GDBus.Error) when I run the command Grammarly: Login to grammarly.com.
Any suggestion on how to resolve this?

@znck I installed libsecret and still getting that error on login.
Do we also need to install keytar ?

The Solution is here  https://youtu.be/34iXHWuhsss

@znck - Glad to know that the extension is back! Can you please help us in resolving this issue?
This time, in a freshly installed OS (Manjaro KDE), I tried again --- installed the extension from marketplace. But again the same error.
So, looks like in linux systems, we need to do something else.

@znck - Glad to know that the extension is back! Can you please help us in resolving this issue?
This time, in a freshly installed OS (Manjaro KDE), I tried again --- installed the extension from marketplace. But again the same error.
So, looks like in linux systems, we need to do something else.

See my upper comment.. the solution is in the video

@Gameransari --- had seen your video; but was not sure how is that a solution.
Can you please give an explanation about it? For instance, what exactly happens with --disable-wm-check?
Also, your command and solution seems appropriate for xfce environment. What about KDE (which I use)?

@Gameransari --- had seen your video; but was not sure how is that a solution.
Can you please give an explanation about it? For instance, what exactly happens with --disable-wm-check?
Also, your command and solution seems appropriate for xfce environment. What about KDE (which I use)?

It's basically re-start or re-enable the stop service of desktop Menu. So disable wm make it to start desktop services which is already stopped

Ok so I don't understand how the linked Video relates to vscode or this issue at all...
On Arch Linux at least, this error is fixed by installing an optional dependency to libsecret that provides org.freedesktop.secrets as shown here in the dependencies section.

Ok so I don't understand how the linked Video relates to vscode or this issue at all...
On Arch Linux at least, this error is fixed by installing an optional dependency to libsecret that provides org.freedesktop.secrets as shown here in the dependencies section.

@pluth --- no luck. I went to the page you pointed, and tried to install all the dependencies which were not present in my current setup of Manjaro. But no help. Still getting the same issue :(

I've encountered similar issue. To solve it you have to provide some implementation of org.freedesktop.secrets like gnome-keyring or KeepassXC. In the NixOS case you can solve it using following configuration:
{
  services.gnome.gnome-keyring.enable = true;
}

On top of that, the keyring should be unlocked. By default this happens upon login (other distros should provide similar PAM-based solution). You can check if keyring is unlocked by running seahorse and looking for Login/Default collection.
Note that it is not strictly necessary to unlock keyring upon login.
With this configuration the issue with org.freedesktop.secrets should be solved.
However, when using manually configured distros (like Arch or NixOS) you may encounter another issue. After all, if keyring wasn't configured then it's likely that more things are missing. If you notice that after issuing login command nothing happens and after 5 minutes there is an error then you most likely have misconfigured default apps (xdg).
Currently, the plugin tries to open URL for oauth. Without default browser this operation will have no effect and you won't be able to complete authentication flow. In the case of NixOS you might fix it with following Home Manager's configuration:
{
  xdg.mimeApps.defaultApplications = {
    "x-scheme-handler/http" = "${pkgs.firefox-wayland}/share/applications/firefox.desktop";
    "x-scheme-handler/https" = "${pkgs.firefox-wayland}/share/applications/firefox.desktop";
    "x-scheme-handler/vscode" = "${vscodePackage}/share/applications/code-url-handler.desktop";
  };
}

Scheme handler for vscode is necessary, because confirmation url on the Grammarly's site will point to it.
Note that everything in this comment is specific to Linux distros and won't solve problems on Windows/MacOS.


Dont dispatch after optout

Hello,
When user switch to optout, remaining events that are waiting to be dispatched need to be loose.
This is a proposal.
Maybe choice should be given to dev.
From my point of view, and the legal one (in EU), when a user optout, remaining cached datas must not be sent, even if they have been collected before the change.
Thanks,
Eric

I've thought about this again and while I disagree with this being a "law" issue, I agree that the behavior would be confusing to users. Your favored behavior goes well with Piwik being more privacy oriented.
I've created #149 to stay open until your idea is implemented.
Wait for #148 though.
Either I add it in #148, or you submit a new PR when it is merged.


Missing "Acceptance Criteria" filed on Custom rule

I don't see "Acceptance Criteria" filed on custom rule as mentioned on this article.
Reference Link : https://docs.microsoft.com/en-us/azure/devops/organizations/settings/work/custom-rules?view=azure-devops

Hi @sureshmvp, thanks for reaching out. I'm looking into this and will be in touch! Thanks!

@sureshmvp could you please let me know whether the work item type you're trying to add to this rule has “Acceptance Criteria” on the type/layout?
By default, ‘Acceptance Criteria’ field is available in “scrum” process, but the states you have in the screenshot are default states of “agile."
Thanks!

Yes, work Item does have "Acceptance Criteria"

Your right, I did create a custom Agile Process to have different swimline and process.
Let me know if you have any other questions.
Thanks


Some modifications which let user uses it easilier

Let users input the source video path, instead of changing it in yolo_video.py
Let users get a output video if they want


Location of message showing after product image upload

Message should be displayed in the reg box under Add Product 1 Title

Verified Fixed Commit @Commit 12de18a


Additions to make stuff cooler

Rather than hardcoding the messages for like mutechat and stuff, you should use a config.yml and allow custom input. If you want i can help you do it cause you = bad :)
jk <3
Ill probably make a rather large pr

Yes, I'm going to do this soon. Thanks for the reminder. I'll make sure to get that out next time I update.


Add auth_type query parameter to facebook-oauth2#open

Similar to #199, I'm looking for a way to append &auth_type=rerequest to the end of the URL generated by the open() method of the facebook-oauth2 provider. It can't be a normal provider configurable—or at least I don't think so—because it should not be set under normal circumstances, only on demand. I've started making the changes that would allow such a parameter to be passed e.g. this.get('torii').open('facebook-oauth2', { auth_type: 'rerequest' }) but quickly felt like I was in over my head.
Before I get too much further into this I thought I'd ask if what I'm doing makes sense and if there might be a better approach that I haven't considered? Thank you in advance...

I just sucked it up and converted my login flow to use facebook-connect instead of facebook-oauth2. I need to make FB.api calls anyway and was initializing the SDK separately, so this probably makes more sense in the long run. Please disregard!


Project : GasGuys HomePage Clone added

Closes:
issue : #463

Title : GasGuys Home Page Clone
Name: :  G Avineshwar
Idenitfy yourself: : GSSOC

Describe the add-ons or changes you've made 📃
It is an home page developed using HTML, CSS and JavaScript with fully responsive website.
How Has This Been Tested? ⚙

Screenshots 📷

Type of change ☑

What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: ☑

[X] My code follows the Contributing Guidelines & Code of Conduct of this project.
[X] This PR does not contain plagiarized content.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly wherever it was hard to understand.
[X] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney , I PR the issue check my changes and merge the changes to make contribution to the project.
Thank you

@GAVINESHWAR as use of js, keep it inside the vanilla js directory

@Avdhesh-Varshney  Could specify basic,intermediate and advanced folder as well .

@GAVINESHWAR as use of js, keep it inside the vanilla js directory

@Avdhesh-Varshney Could specify basic,intermediate and advanced folder as well .

based on the attached labels level2 -> Intermediate ok


Correct the ANDs and ORs in presentation request restrictions

Signed-off-by: Stephen Curran<EMAIL_ADDRESS>

@TimoGlastra @TelegramSam -- please review this so that we can merge it.


displaying issues with Optifine and shaders

Albedo causes some displaying issues with lightings when Optifine is present.

This is uh, sorta what happens. OptiFfine uses internal shaders that are not compatible with Albedo. Optifine breaks many mods so you can't really expect it to work with stuff like this. So sorry, you'll have to go with one or the other.

Ah it's so annoying, Optifine tends to always break other mod. But I suppose there is nothing to do. :(


feat: add CORS proxy for Google calendar

@linuxbandit calendar.google.com is being bitchy about cors, therefore this


Added new Song

Description
Added New Song
Fixes #29
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

@all-contributors please add @S-Parker7000 for audio


truststore.jks in ConfigMaps updated on every pod restart

We have ConfigMaps with Certificates that we convert to JKS with the help of cert-utils-operator (cert-utils-operator.redhat-cop.io/generate-java-truststore annotation, currently using v1.3.9). We also have Stakater Reloader that restart our apps as truststores change.
We have discovered that when Cert-Utils-Operator restarts all our ConfigMaps are updated. And then Stakater Reloader kicks in and restarts apps. Even nothing has changed with certs.
This is probably due to the non-idempotent creation of the JKS which involves time.Now():
https://github.com/redhat-cop/cert-utils-operator/blob/master/controllers/configmaptokeystore/configmap_to_keystore_controller.go#L136-L147
Probably this is a required field. :-|

I think your assessment is correct. not sure what to do to prevent this. Asking internally...

maybe the CreationTimestamp of the ConfigMap could be used?
diff --git a/Dockerfile b/Dockerfile
index 2c1b7ca..4a107d5 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,5 +1,5 @@
 # Build the manager binary
-FROM golang:1.16 as builder
+FROM docker.io/library/golang:1.19 as builder

 WORKDIR /workspace
 # Copy the Go Modules manifests
diff --git a/controllers/configmaptokeystore/configmap_to_keystore_controller.go b/controllers/configmaptokeystore/configmap_to_keystore_controller.go
index 97c2233..a1ecb13 100644
--- a/controllers/configmaptokeystore/configmap_to_keystore_controller.go
+++ b/controllers/configmaptokeystore/configmap_to_keystore_controller.go
@@ -7,7 +7,6 @@ import (
        "errors"
        "reflect"
        "strconv"
-       "time"

        "github.com/go-logr/logr"
        keystore "github.com/pavel-v-chernykh/keystore-go"
@@ -136,7 +135,7 @@ func (r *ConfigMapToKeystoreReconciler) getTrustStoreFromConfigMap(configMap *co
        for p, rest := pem.Decode([]byte(ca)); p != nil; p, rest = pem.Decode(rest) {
                keyStore["alias"+strconv.Itoa(i)] = &keystore.TrustedCertificateEntry{
                        Entry: keystore.Entry{
-                               CreationDate: time.Now(),
+                               CreationDate: configMap.GetCreationTimestamp().Time,
                        },
                        Certificate: keystore.Certificate{
                                Type:    "X.509",

or a checksum of the ca-bundle.crt content could be computed and be persisted as annotation.

it would still be different than the one used to create the truststore. Maybe it's possible to inspect the truststore (if it exists) and use exactly that timestamp

@raffaelespazzoli I want to proceed with this., because it "hurts" our cluster every pod restart (dozens of java pods restarted).
found out the secrets keystore controller writes a annotation:
https://github.com/redhat-cop/cert-utils-operator/blob/7c20a03107b314a546eb3afb1e6457e94fe3e15e/controllers/secrettokeystore/secret_to_keystore_controller.go#L325-L338
I see these possible ways to fix this situation:

use a fixed value for creation timestamp (1970-01-01...). As this CreationDate has no real value IMHO the value can be anything.
use the same as for the secrets keystore controller. Store timestamp as annotation.
use the CreationTime timestamp from the ConfigMap
parse the keystore and re-use the effective keystore creationdate

any method but the last will  trigger a final "useless" update of the configmap.

let's use the configmap creation time. can you send a PR?

i've created a patch: https://github.com/redhat-cop/cert-utils-operator/compare/master...vinzent:cert-utils-operator:persistent-jks-creationdate-property?expand=1
Built image (https://quay.io/mueller/cert-utils-operator:latest).
Testing:

truststore.jks in ConfigMap still gets updated every restart.
comparing "keytool -list -keystore xyz.jks" before and after shows no difference

Stumbled upon this https://github.com/pavlo-v-chernykh/keystore-go/issues/34 (fun fact: created by @raffaelespazzoli ;-) ).  Maybe the WithOrderedAliases and WithCustomRandomNumberGenerator options also needs to be used?

I figured out that the configmaptokeystore uses an outdated keystore-go (2.0.1) lib. Current is 4.4.1. Also path to lib changed (pavel -> pavlo). And it requires at least go 1.17.
more changes pushed to my branch: https://github.com/redhat-cop/cert-utils-operator/compare/master...vinzent:cert-utils-operator:persistent-jks-creationdate-property?expand=1
So I think to fix this issue, following changes are needed:

update builder image go >1.17
update all code to use keystore-go 4.4.1
use configMap CreattionTimestamp for JKS CreationTime and WithOrderedAliases feature of keystore-go

ok, please confirm that this change fixes the issue, then send a PR?

The #144 is now ready to be reviewed.


ERROR: FluidPCA - Invalid JSON format

When I am running a script I am receiving this traceback error:
ERROR: FluidPCA - Invalid JSON format.
I cannot understand where is the exception code that triggered and give us this exception. Could anyone help me?
Thank you in advance!

Thank you for your prompt reply!
I m trying to connect this extension https://github.com/mirlca/code in SC3.
When I am running MIRLCa.new(path: z, creditsPath: y, modelsPath: x), Ι receive this error.

Yes, can confirm: the pca.json file in the https://github.com/mirlca/code package doesn't load – it's missing one of the JSON entries it needs('cols'). I've attached a JSON that (I think) fixes it (to go in the JSON subfolder of your mirlca installation).
Happier JSON:  pca.JSON.zip
Pinging @g-roma @axambo: are these JSON files being  generated from something else? As far as I can see, the FluidPCA JSON code has remained untouched since Sept 2020, so I wouldn't expect it to be missing keys (I'll test though...)

The error indeed is gone with the pca.json file you provided with the 'cols' key. For now it seems to work fine.
Thank you very much!!


Limit precision in send pane

I'm able to do this without errors in the send building. But if I submit this transaction, I get a OP_UNDERFUNDED.

Fixed in js-stellar-base: https://github.com/stellar/js-stellar-base/commit/6e7fa477a9bac86aedb6d2900ecd27be172f2c97. Will fix this after releasing new stellar-base version.


SD3847 - Implement retrieve and update order APIs with Akka HTTP

Code can be built and run

2 new APIs are implemented

2 new APIs are working as expected, handled in case of entity not found (but it is better to use a particular exception and then handle it through ExceptionHandler)

No UT implemented.


Consider input genome quality before building

Description of feature
E.g. with conterminator or https://github.com/ncbi/fcs/

But eek

But eek

😬
Would CheckM2 be useful here?

Sort of, but I think that only works for microorganisms?


Documentation

Hi, any documentation how to use this library?

Added some to the readme in this repo.  The bluetooth pairing is not included in this library but once you pair with the bluetooth OBD device (ELM327 only) then you can use the code in the readme to facilitate getting pids from it.

Readme updated here https://github.com/barnhill/AndroidOBD/commit/f2209b693405d7c108639fdeee29712b2a6910b9


int range not changing from default-range to 1-9

Hi All,
I am trying to limit the int value range from 1 to 100 to 1 to 9, but the custom options limit not working in the extension.

Can you share the page where you are having this problem?


Is the idea of uploading via WebRTC abandoned?

The branch https://github.com/VeliovGroup/Meteor-Files/tree/webrtc-data-channel of this project hasn't been updated in 3 years. Does this mean this idea is abandoned, or was there simply not have the time to complete it yet?
In case it's abandoned it would be nice to post an update about it. If not, I'd like to know a reason why it still could be a better idea over DDP or HTTP.

Does this mean this idea is abandoned, or was there simply not have the time to complete it yet?

Yes, it's abandoned

was there simply not have the time to complete

No, it happened due to lack of interest among our users (developers). I've raised a question few times with no response.

In case it's abandoned it would be nice to post an update about it. If not, I'd like to know a reason why it still could be a better idea over DDP or HTTP.

Current status: It was successful experiment, we succeed in transferring data from browser to server over webRTC. Due to complexity and immaturity of technology its development would mean a lot of extra hours, including later hours of maintenance. As community had no interest, webRTC branch was abandoned and never merged to master.

Thanks for the quick response.
Is there a real chance for webRTC to become a better choice than HTTP? On the branch I read that HTTP already was 2x faster than the current webRTC implementation, so if this implementation isn't particularly slow, it must have other benefits in order to prove itself worthy for other use-cases. Do you see any?
Just asking because I haven't seen a ticket about webRTC yet which would document your thoughts and insight on this.

Is there a real chance for webRTC to become a better choice than HTTP

It's will be just different, not better, not worse. In terms of speed, it might be slower than HTTP due to limits of package size in UDP and RTC/DC. But it definitely would be the overcomplicated solution, as it involves STUN and TURN servers you need to run (or rent out for production) and signaling. Signaling is covered, thanks to DDP, while TURN and STUN is the something you need to run and maintain and are necessary parts of communication, in real-world there's not much p2p (direct, in terms of networking) connections.
And you shouldn't forget we are discussing browser-to->server connection, while WebRTC was created for two-way browser<-to->browser connection. I believe WebRTC is the wrong technology (tool) for this purpose (task)


🐛 Bug Report: Support AsyncGenerators in aworkflow

Which component is this bug for?
Traceloop SDK
📜 Description
Current aentity method
The current implementation of aentity_method decorator incorrectly handles async generators by attempting to await them through _ahandle_generator, resulting in the error:
TypeError: object async_generator can't be used in 'await' expression

This prevents the decorator from being used with async generator functions, particularly in contexts like FastAPI endpoints where asyncio.run() cannot be used.
👟 Reproduction steps
Run the following sample code:
from traceloop.sdk.decorators import workflow, aworkflow, base
from traceloop.sdk import Instruments, Traceloop
from app.utils.tracing import CloudTraceLoggingSpanExporter
import asyncio

Traceloop.init(
    app_name="Sample",
    disable_batch=False,
    exporter=CloudTraceLoggingSpanExporter(),
    instruments={Instruments.VERTEXAI, Instruments.LANGCHAIN},
)
@aworkflow()
async def stream_numbers():
    for i in range(3):
        yield i
        await asyncio.sleep(0.1)

async def stream_numbers_no_decorator():
    for i in range(3):
        yield i
        await asyncio.sleep(0.1)

# Separate cells for testing each function
# Cell 1 - This should work:
async for num in stream_numbers_no_decorator():
    print(num)

# Cell 2 - This should fail with the TypeError: object async_generator can't be used in 'await' expression
async for num in await stream_numbers():
    print(num)

👍 Expected behavior
Expected Behavior
The decorator should preserve the async generator and wrap it to handle span lifecycle, allowing for proper streaming of results:
if isinstance(res, types.AsyncGeneratorType):
    async def wrapped_generator():
        try:
            async for item in res:
                yield item
        finally:
            span.end()
            context_api.detach(ctx_token)
    return wrapped_generator()

See this example for full implementation
👎 Actual Behavior with Screenshots
# Current implementation
if isinstance(res, types.AsyncGeneratorType):
    return await _ahandle_generator(span, ctx_token, res)

The decorator attempts to await an async generator, which is not valid Python behavior. I get:
TypeError: object async_generator can't be used in 'await' expression
🤖 Python Version
No response
📃 Provide any additional context for the Bug.
By overriding the aentity_method I managed to solve all errors and have all the spans properly flowing.
See this link
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
None

The issue with the aentity_method decorator in the Traceloop SDK arises because the decorator currently tries to handle async generators by incorrectly attempting to await them, which is not allowed in Python. Async generators, which are functions that yield results asynchronously, cannot be awaited directly—they must be iterated over using async for.
Potential Solution
To address this, the decorator should:
Detect if the function result (res) is an async generator.
If it is, wrap the generator in another async function that:
Manages the span lifecycle.
Iterates over the items in the async generator using async for.
Ensure that the span ends and context detaches once the generator has finished producing items.
@dosubot @eliasecchig. Assign me with the issue so I can create pull request and rectify the issue

Don't think I have enough rights to assign the issue sorry!


chore(ci): add node version

PR Checklist
If you have any questions, you can refer to the Contributing Guide
What is the current behavior?
Please describe the current behavior and link to a relevant issue.
Issue Number
Example: #123
What is the new behavior?
Please describe the new behavior or provide screenshots.
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Specific Instructions
Are there any specific instructions or things that should be known prior to review?
Other information

Looks build code in docker container, so why we need setup-node?

Because the CI RUN Failed. But we have no idea. @Rory-Z

Looks build code in docker container, so why we need setup-node?

Because the CI RUN Failed. But we have no idea. @Rory-Z

Check the error log, I guess this is a node.js error ?


[🚀esl-utils]: add ability to pass predicate to sequence finder

As an ESL consumer, I want to be able to pass the predicate function instead of the selector
Extended finder API
/** Create function that finds next dom element, that matches selector, in the sequence declared by `next` function */
export const createSequenceFinder = (next: (el: Element) => Element | null) => {
  return function (base: Element, sel: string | (el: Element) => boolean): Element | null {
     ...
  };
};

Priority: Normal

:tada: This issue has been resolved in version 4.0.0-beta.10 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Incorrect version number in the latest tag

The version in the pyproject.toml file in the latest tag (v0.0.81) is 0.0.0.dev0.
This seems to be not in line with the source distribution published in pypi.
Is this expected?

It is expected yes.
The 0.0.0.dev0 is replaced by the release process just before publish to pypi https://github.com/uktrade/stream-zip/blob/main/.github/workflows/deploy-package-to-pypi.yml#L19. Have to admit I've not seen this done elsewhere, but it makes releasing new versions very straightforward: we make a release in GitHub with no code change involved.
Is this causing a problem? (/do you have a better way?)

I'm packaging stream-zip for debian and the generated package has the version number that is in the pyproject.toml file, the incorrect one.
The current workaround is to patch the sources I would like to avoid to do it in the long term.
The option of using directly the source tarball in pypy (rather then the one in the github tag) is also problematic for me because the pypi tarball does not include, e.g., the test suite.

Ah I think understood… Will have a ponder on how best to approach this - I am quite keen to avoid having to manually change the version in code each time though, but also I have liked the ease at which I can just make a GitHub release and PyPI is automatically deployed to

Actually a question: do you have to take the code from a tag, or could you take from another asset from releases: https://github.com/uktrade/stream-zip/releases
So we can do any faffing with the version in code at our end rather than yours

Using releases should be fine

After a few false starts, now have a "Source code (with release version)" asset in new releases which is all of the source code, but with the correct version in pyproject.toml, e.g. at https://github.com/uktrade/stream-zip/releases/tag/v0.0.82

Thanks a lot @michalc
I have just tested the packaging of the new release and all works perfectly without patching the version number.
Closing

In Shoebot when we had a similar thing with versions, I ended up adding a unit test that failed if the versions wheren't synced (not pyproject.toml there, but setup.py as our project is old)


node_modules Mocks are not picked up by jest with latest react-scripts

Describe the bug
When upgrading from<EMAIL_ADDRESS>to latest the mocks are no longer picked up from /__mocks__ directory
Did you try recovering your dependencies?

YES
Which terms did you search for in User Guide?

jest manual mocks broken
Environment

Environment Info:
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
Binaries:
Node: 12.8.0 - /usr/local/bin/node
Yarn: 1.17.3 - ~/.yarn/bin/yarn
npm: 6.10.2 - /usr/local/bin/npm
Browsers:
Chrome: 76.0.3809.100
Firefox: 68.0.1
Safari: 12.1.1
npmPackages:
react: ^16.9.0 => 16.9.0
react-dom: ^16.9.0 => 16.9.0
react-scripts: 3.1.1 => 3.1.1
npmGlobalPackages:
create-react-app: 2.1.3
Steps to reproduce

(Write your steps here:)

create a manual mock of any node_modules package
put it to mocks directory
run your test

Expected behavior

Mocks are picked up by jest
Actual behavior

Mocks are not picked up
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

git clone https://github.com/tomitrescak/react-boilerplate -b Demo
cd react-boilerplate
yarn
yarn test
p -> 'button'
error: Trans not found (not being picked up by mocks)

To see that is works with previous react-scripts do

yarn add<EMAIL_ADDRESS>yarn test
You will recieve a snapshot erro which is fine

I can't reproduce this with 3.1.1, we have a __mocks__ folder under src/ with 2 different mocks (one of a node module and one of an internal module) and they both work

@FezVrasta __mocks__ for node modules should be located immediately next to the node_modules directory.
https://jestjs.io/docs/en/manual-mocks#mocking-node-modules

This may have been caused by #7480.

This is problematic because __mocks__ for user modules may collide with the __mocks__ for node_modules.
If we're not going to revert https://github.com/facebook/create-react-app/pull/7480, I feel we should at least document the new jest source since it is not standard and document the risk of collision.

@jnak even under src the mocks work just fine. I always did it that way

@jnak even under src the mocks work just fine. I always did it that way

I know they work. But it is not standard (as per the jest documentation) and you may be running into a __mocks__ collision.
Anyway, I don't feel strongly about it. I just wanted to let you know of this undocumented gotcha.

What to do guys? Shall we just move the mocks to src folder and hope for no collisions? We only have about 3-4 projects to upgrade.

Honestly I think #7480 should be reverted, or at least just let us set the roots config in our package.json so we can avoid anti-patterns like this.

No pressure, but would be good to know the decision if we should move the mocks to upgrade. Thanks!

We may be able to specify __mocks__ living in the project root as another entry in the roots configuration. If someone has time could they try this? This may be a good solution to keep the performance benefits of #7480 and supporting the __mocks__ next to node_modules convention.

@ianschmitz I've tried adding the project root to the roots configuration in package.json, but CRA threw an error saying that it wasn't supported and didn't run my tests at all.

Correct - we don't support modifying roots. What you'll have to do test this is edit the createJestConfig.js file in node_modules/react-scripts as was done here: https://github.com/facebook/create-react-app/pull/7480/files#diff-40a56a7d41499eab85303b5e977f9742.
Try something like:
{
  roots: ['<rootDir>/src', '<rootDir>/__mocks__'],
  ...
}

For those whose test are completely broken by this:
Moving __mocks__ under ./src solved the problem for me.

@brendanmc6 the issue is this is an anti-pattern.
The Jest documentation says that any external module manual mocks must live in the same level as node_modules, see https://jestjs.io/docs/en/manual-mocks#mocking-node-modules

As a temporary solution, I moved mocks to /src folder. But this is kind of very annoying bug, which blocks a very useful feature of Jest. As an example, I do want to mock Axios only once in my code for the whole project and it will be nice if it could be done according to Jest documentation.

Strangely this happened to me in two other projects as well, a Next.JS and a React Native project, both times because my CI was failing (local tests were passing). In both cases moving it to a subfolder other than root solved the problem. Just leaving this here for the paper trail-- I can't seem to find any other issues listed anywhere.

Can this be fixed soon, I can't mock node_modules as per jest documentation.

Hi @KennethSundqvist, how's it going with your proposed fix?

@brendanmc6 Thanks! spent about three hours to figure this out.

Is there any progress with the PR for this issue fix? This feature is quite helpful for my testing

still no fix? :/

I spent a lot of time today trying to figure out what I was doing wrong while following the jest module mock documentation very closely. Ideally CRA templates that use jest should contain the same defaults as plain-old-jest since react documentation directs newbies to use CRA.

Learning Create React App and trying to follow TDD, it is very frustrating to have spent two days doubting myself what I have done wrong only to find out it is due to a downstream change and that the patch to fix it has stagnated for more than half a year. If the fix is not making it in anytime soon, could you please at least leave a note in the documentation?

It's been more than half a year, should we expect the patch to fix this soon?

Not sure if this would solve the issue for everyone else. For me, I ended up using CRACO to override the default Jest configs.
Here's an example (my additional tests were in electron folder) of my craco.config.js in my project root,
module.exports = {
  jest: {
    configure: {
      roots: [
        '<rootDir>/electron',
      ],
      testMatch: [
        '<rootDir>/electron/**/__tests__/**/*.{js,jsx,ts,tsx}',
        '<rootDir>/electron/**/*.{spec,test}.{js,jsx,ts,tsx}',
      ],
    },
  },
};

Please update the documentation if there is no plan to rectify this. I (and many others, I'm sure) have wasted a lot of time trying to figure out why what is specified in the documentation doesn't work.

I've gone and used patch-package to fix this on my repos:
Step 1: create the __mocks__ dir
├── src
├── mocks
├── node_modules
├── package.json
Step 2: patch react-scripts
// node_modules/react-scripts/scripts/utils/createJestConfig.js
   const config = {
-    roots: ['<rootDir>/src'],
+    roots: ['<rootDir>/src', '<rootDir>/__mocks__'],

Warning: This breaks jest if the <rootDir>/__mocks__ dir doesn't exist.


⚠ Processors has degraded performance

In 85938d4, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 82 ms

Resolved: Processors performance has improved in 181ba7a.


[$500] Login - Expensify logo is too close to the top of the screen

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.42-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal team
Slack conversation:
Action Performed:

Launch New Expensify app.
Log out if logged in.

Expected Result:
There will be adequate spacing between Expensify logo and the top of the screen.
Actual Result:
Expensify logo is too close to the top of the screen.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01f5aa21ec0e08e780
Upwork Job ID:<PHONE_NUMBER>034033664
Last Price Increase: 2024-02-15

We think that this bug might be related to #vip-vsb
CC @quinthar

@ZhenjaHorbach's proposal LGTM! I agree this is a regression from https://github.com/Expensify/App/pull/34837, so depending on urgency we may want to let @rayane-djouah take a stab at fixing this first.
:ribbon::eyes::ribbon: C+ reviewed

I agree this should be fixed (& probably by the originating PR author) but not needed to fix asap as a deploy blocker

@rayane-djouah and @getusha may handle this

Proposal
Please re-state the problem that we are trying to solve in this issue.
Login - Expensify logo is too close to the top of the screen
What is the root cause of that problem?
The position of the logo is not set well
What changes do you think we should make in order to solve the problem?
set position to absolute and set the appropriate values for top, left

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01565b0a8934c1826a

Unassigning as @getusha will be handling this. cc @puneetlath

@rayane-djouah mind commenting here so I can assign you?

@rayane-djouah @getusha how's this going?


max_depth/1 option incorrect

There are two different objectives. One is that the output should be nice and consistent. That is desirable. But then there is a more fundamental issue: Sometimes the output is just incorrect. That is, the output cannot be used to (partially) reconstruct the original term. Here is such an example:
?- write_term_to_chars([[_|_]|_],[max_depth(1)],Chs).
   Chs = "[[...|[ ...]]|_2]", unexpected.
?- write_term([[_|_]|_],[max_depth(1)]).
[[...|[ ...]]|_2]   true, unexpected.

I know there are faults, as I said before it's in progress.
On Thu, 13 July 2023, 21:24 UWN, @.***> wrote:

There are two different objectives. One is that the output should be nice
and consistent. That is desirable. But then there is a more fundamental
issue: Sometimes the output is just incorrect. That is, the output cannot
be used to (partially) reconstruct the original term. Here is such an
example:
?- write_term_to_chars([[|]|],[max_depth(1)],Chs).
Chs = "[[...|[ ...]]|2]", unexpected
?- write_term([[|]|_],[max_depth(1)]).
[[...|[ ...]]|_2]   true.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/261, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEUNKXPTZXLKXMOZW7LXP7LHBANCNFSM6AAAAAA2IZOEVY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Back at this...


Suggestion - Why not extracting the time and getting the year the track was uploaded instead of just having a constant?

Rly, why not have real year? Its better than plain 2018

Indeed, there's no reason why this should be static. The information is readily available.


⚠ SceneTime has degraded performance

In acfb3fd, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 10035 ms

Resolved: SceneTime performance has improved in 715bdb4 after 5 minutes.


⚠ SceneTime has degraded performance

In 229402c, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1541 ms

Resolved: SceneTime performance has improved in 2523e88 after 9 minutes.


[Feature] TTS_FAIL to support <<

At the moment it seems like it doesn't

Same for TTS_EXPECT_COMPILES if I didn't mess that up

int x = 42;
TTS_FAIL("This is " << x << "!");

works as all info macro consume << chains.
There is no external logger though as no test are taking place.


remove integrate-ide from 2.12 and 2.13 release flows

when integrate-ide stopped working in 2.12, we kludged it by putting this in scripts/jobs/integrate/ide in the scala/scala repo:
echo "IDE integration not yet available on 2.12.x. Punting."
exit 0

on the assumption it would be fixed soon. but that was at least a year ago. in the meantime, every 2.12 and 2.13 pull request says e.g.:
integrate-ide — [4238] SUCCESS. Took 21 s. Details

which is just misleading noise. I suggest we actually take it out of the 2.12 and 2.13 flows. if it were ever made to work for 2.12 and/or 2.13, we could always just revert the change.
cc @sschaef

this happened in the recent redo


Fonts don't load outside VSCode - Probably not for other users either.

Could be a regression caused by https://github.com/excalidraw/excalidraw-vscode/issues/60.
When you save a drawing into, say, test-01.excalidraw.svg the svg will have:
      @font-face {
        font-family: "Virgil";
        src: url("https://file%2B.vscode-resource.vscode-cdn.net/Users/john.smith/.vscode/extensions/pomdtr.excalidraw-editor-3.5.1/public//dist/excalidraw-assets/Virgil.woff2");
      }

The font will not load anywhere outside VScode.  I suspect it wouldn't even load on other machines using VSCode (as the URL includes the username).
User Story
As a user, I'd like to save my files using the .excalidraw.svg extension so:

I can commit these into the repo for others to contribute.
I can reference them from *.md file (for documentation portals) so they load both locally and once deployed.

In other words, would help if these URLs point to some public URL.

Thanks for notifying me, this is definitely linked with #60.

Falling back to using .excalidraw.png for now. A solution for this issue with svg would be much appreciated.


my game crashes when i get a game over

Describe your bug here.
my game was working fine yesterday,i changed a ui line now the game straight up crashes when i get a game over
i checked everything,removed the code,removed the ui,and it still crashes
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes,i added a .lua script

nvm,i found what as wrong


Docker image for Sc2LadderServer

Is there a docker image that is available for the ladder manager.  This would allow any OS that supports docker to run a bot via ladder manager.

We're working on that at the moment, not sure when this might be ready though


Add flag to disable Core node process entirely (enables Celestia-Node in standalone format)

Should be done as part of making Full node independent from Core


IPv6 Support for afthelper.NextHopAddrsForPrefix

This is useful for obtaining NHs for an IPv6 RIB prefix.
Tested that lemming can use this helper routine to support IPv6 routes and IPv4-mapped IPv6 routes.

Thanks for the review @robshakir can you merge the PR as well?

Yup, of course -- apologies, forgot you don't have +w here.


Error in "npm run dev"

$ npm run dev

<EMAIL_ADDRESS>dev C:\Users\Clavis\Desktop\marzipano-master
scripts/dev

'scripts' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Clavis\AppData\                                                                                \Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "dev"
npm ERR! node v6.9.4
npm ERR! npm  v4.0.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>dev: scripts/dev
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script 'scripts/dev'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the marzipano package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     scripts/dev
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs marzipano
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls marzipano
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Clavis\Desktop\marzipano-master\npm-debug.log
err.txt
how to solve this error?

hello?We are unable to follow the getting started instructions.  This issue slows down getting started considerably.

This is a duplicate of #3 . Please run scripts/dev directly instead of using npm run.


[MB-15446] accounting for adjusted net weight in calculations

Jira ticket for this change
Summary
There was one more weight check function that needed updating - this PR ensures they take adjustedNetWeight into account 🎉
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Run make server_test
New test should pass, it takes adjustedNetWeight into account

Verification Steps for Author
These are to be checked by the author.

[x] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Messages

:book:
:link: MB-15446

  Generated by :no_entry_sign: dangerJS against 7085ad41e5ab816776a7a90d2a93b76fd3c89243


why?

D:\fubao\VCProject\RGB2Y\Debug>RGB2Y.exe
------------- RGB2Y ------------
Warming up...
Testing...
------------ OpenCV ------------
Warming up...
Testing...
0 pixels disagree.
RGB2Y      took 15139.5 us.
OpenCV     took 2592.71 us.
This is my test result.
OPENCV 3.4.3  version

Just pushed some performance improvements and bug fixes, please try now. Also please make sure you're using a nontrivial image (i.e. at least 128 or so rows and cols). Finally please make sure you have enabled RGB2Y's multithreading and AVX2 support. (i.e. the new default options should be good).
-Kareem


Add /cc command

The value passed may be one or more email addresses.  The format is the same as for the cc: footer in the PR body.

Very nice! Just one thing, we need to adjust the Azure Function, too:

You had mentioned it and I still managed to miss it.
Should the /cc command  be documented somewhere?

Thank you!

Should the /cc command be documented somewhere?

Maybe ;-)
While we're thinking about /cc, I would also love to have the option to, say, /cc @webstech (i.e. auto-map GitHub handles to email addresses, which might require having an internal map for users without public email addresses, or even https://github.com/gitgitgadget/gitgitgadget/issues/153 to be resolved)...


Add Carthage support

Why this PR ?

This PR allow TimelaneCombine to be available through Carthage.

What is required ?

After merging this PR you should push new TAG with new version (1.0.3)

How to test it after pushing new TAG ?

Add Cartfile to XCode project.
Add this to Cartfile :

github "icanzilb/TimelaneCombine" "1.0.4"

Run this command in terminal

carthage update

Link the output framework in you project.

Thanks @KarimEbrahemAbdelaziz - I'm wondering if we really need the checkouts included in this repo? What's the practice in other projects? I had a quick look at other repos and some include the carthage checkouts, some don't...

Hey @icanzilb,
As checkout folder is for carthage caching, I usually include it for the sake of consistency. So there is no room for forks to have any issue related to it.
So it's personal preferences in the projects 😅😃
Some projects don't include it as it will be generated again (cloned) when needed from carthage.
Do you think we still need it here? ☺

How about including the resolved cartfile but skip the actual checkouts?

Would be good too 👍
I will update the PR now

@icanzilb Check it now :)

Great, thank you!

Thank you @icanzilb ❤💪🏻

@KarimEbrahemAbdelaziz if you have some time - could you have a look at https://github.com/icanzilb/RxTimelane? I like how the cartage Xcode project in RxTimelane is in a sub-folder, but in RxTimelane the Xcode project is in the root. Would you be interested to re-organize the file structure and put also RxTimelane's framework project into a sub-folder?

@icanzilb Sure interested to do it 💪🏻
I gave it a look and I am currently working on restructure it. Wait my PR :)

Thank you!

Hey @icanzilb -
Carthage bootstrap or Carthage build commands should create the framework.
But It seems there is a problem with Carthage support in Timelane projects. I faced this issue while I am working on Zen and I just retested Timelanes now and found the issue and working on it's fix currently.


Input icon overflows input label

Hi,
and thanks for great datepicker!
I integrated it to my app and noticed two little issues.

I have am-show-input-icon="true" in my html. The issue is that Input icon is placed over beginning of input field and input label is below the icon. How to place icon in the front of the input field?

I have changed the background color of am-date-picker__month-year -div to dark and foreground color white in my am-date-picker.html and it works fine. Only issue is that the color of chevron icons remain dark. I have edited css-file: .am-date-picker__chevron {color: white;}, but no success. So how to change icon color to white?

Best regards

Hello,
Thank you for giving my datepicker a chance.
First of all, which version of am-date-picker and angular-material are you using?
Angular-material changes logic of placing md-icon in md-input-container from version to version, so I'm working on the solution how to fix it. So far it seems to work correct with angular-material 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.6.
I've made a codepen with applied css styles.

Hi, and thanks for answering!
I cloned your master branch yesterday so am-date-picker is latest version. My angular-material version is v1.1.0-rc1. I just copied content of src folder to my app repository and built it along with my gulp tasks.
I tried those lines in your codepen, but no success.. weird.. I use scss instead of less.

Installed 1.0.6 and yep, it's working now, thanks!
But css issue remains..

Hi again,
Found solution for css issue: .am-date-picker__chevron {fill: white;}
Best regards


Refactoring classes to functions

Please replace JS classes back to the functional style.

Implemented. Thank you Igor


Does remix-island interfere with server-side error handling?

Hey,
I found this remix-island issue posted on remix-run repo. I get the same issue in our app since upgrading to Remix v2. The problem is that any unhandled errors in any loader on initial load causes rendering problems in ErrorBoundary, which doesn't happen on client-side navigation. The ErrorBoundary triggered is not the one in root.tsx which unmounts the whole document, the problem still exists when we render an extra ErrorBoundary in a pathless route below root, which we call __Layout.
One of the Remix maintainers suggests in a reply it's likely caused because the reporter uses remix-island and it removes SSR errors.
Is deleting of these errors necessary for remix-island to work correctly? 🤔

Hy @hewelt
I don't really remember if the deleting of the errors is on the necessary :)
Unfortunately I currently don't have the capacity to dig further into this. Any help appreciated!


feat: update order details: add payment info and payment method

This PR resolves TX-925
Description

This PR updates order details screen: added payment information for wire transfers, updated payment method section.

PR Checklist

[X] I tested my changes on iOS / Android.
[X] I added screenshots or videos to illustrate my changes.
[X] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[X] I would like at least one of the reviewers to run this PR on the simulator or device(iOS).

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

That would be nice to test this changes on iOS device, can somebody help me with that?

@kiryl-zubarau I'll try to run eigen on IOS and send you screen shots.

@kiryl-zubarau I'm sorry, no success running it.


support libarchive

Summary
support libarchive
Impact
nothing
Testing
vela
mps3 archivefs demo

 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.


Could it handle realtime transcription?

This is more of a question than an issue, but could basic-pitch handle realtime transcription of audio (with low latency)?
It seems that it expects input in chunks of two seconds if I understand the code correctly, which suggests that you'd always have at least that much latency, but I could be wrong.

Good question. The inference in TF has been tested to be 3x faster than real time(I have to double check that number) if you're using the Typescript library (coming soon) on a mid-range chromebook.
However, the post processing step currently expects the output from fully processing the audio through the model. It may be possible to modify the post processing step to work on chunks at a time, but we haven't tested the approach and expect worse quality output if we were to try it.

That’s interesting to know, thanks for the details. I guess I was curious
whether this would ever be suitable for acoustic instrument recognition in
real time for e.g. music learning applications, where you ideally want the
feedback almost instantly. Sounds like it’s a “maybe”? :)
On Tue, 21 Jun 2022 at 15:00, David Rubinstein @.***>
wrote:

Good question. The inference in TF has been tested to be 3x faster than
real time(I have to double check that number) if you're using the
Typescript library (coming soon) on a mid-range chromebook.
However, the post processing step currently expects the output from fully
processing the audio through the model. It may be possible to modify the
post processing step to work on chunks at a time, but we haven't tested the
approach and expect worse quality output if we were to try it.
—
Reply to this email directly, view it on GitHub
https://github.com/spotify/basic-pitch/issues/19#issuecomment-1161788236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJURFRVTTEC5DFLFAA5RNLVQHDI5ANCNFSM5ZEYBNSA
.
You are receiving this because you authored the thread.Message ID:
@.***>

"Maybe" is a nice way of phrasing it :)

I'm intending to have a crack at implementing this, as I need it for my own project (and can imagine it being useful in many applications). I understand there will be a loss in quality which for my application is not a problem since I don't need accurate note onsets or timing information.
Just wondering if there is a reason this is a "bad idea"? I don't think it will require retraining as I simply wish to extract note probabilities pre-post-processing.
Any insight appreciated!

@supersational did you ever try this and could you share how it went, etc?

Didn't bother since no info on whether it's even possible without costly retraining... I switched to this simpler method https://github.com/alesgenova/pitch-detection-app


Enhanced README: Added Code of Conduct and Contribution Guidelines

This Pull Request enhances the project README by adding a Code of Conduct and Contributing Guidelines. These additions aim to foster a welcoming and inclusive environment for all contributors and provide clear instructions on participating in the project.
Key Changes:
Added Code of Conduct: A detailed Code of Conduct has been included to establish expected behavior within the community, ensuring that all participants feel safe and respected.
Included Contribution Guidelines: Clear guidelines on contributing to the project have been added. This includes steps for forking the repository, making changes, and submitting pull requests.
These enhancements are designed to improve the onboarding experience for new contributors and maintain a positive project culture. Feedback and suggestions for further improvements are welcome!

@yatulearn, I’ve made the requested changes.
Please take a look when you have time!

ok

ok

so can I merge my pull request?


Example private data from backend

[x] templates out auth routes
[x] leverage new templating feature to move fileupload to be optionally templated
[x] move status to app/
[x] adds a new route expecting oathkeeper to pass in headers for authenticated users x-user-id and x-user-email

Are you going to add the k8s changes in this PR as well or separately?

Are you going to add the k8s changes in this PR as well or separately?

@bmonkman the k8s changes as in the oathkeeper rules?  do i only need to create the rules resources?

Are you going to add the k8s changes in this PR as well or separately?

@bmonkman the k8s changes as in the oathkeeper rules? do i only need to create the rules resources?

Yes, creating the rules and also conditionally creating the ingress.


make fs-ro output better readable

The current output is rather hard do digest if there are many read-only filesystems:

This pull requests adds a few newlines:

which makes it more pleasant to read.

Thank you. I also will add /dev/loop to the DEFAULT_IGNORE list.


docs: Use release branch for ModelMesh links

Point users to the latest stable release instead.

/lgtm
/approve


add rekor-cli to homebrew tap

Add rekor-cli to be installed with homebrew 😄

do we want to call rekor-cli when installing or just rekor?


Proposal: enable optional bind mounts

When specifying mounts in devcontainer.json, we can use volume or bind mounts:
 "mounts": [
    // Keep command history
    {"type":"volume", "source": "my-bash-history", "target":"/home/vscode/commandhistory"},
    // Mounts the login details from the host machine to azcli works in the container
    {"type": "bind", "source": "${env:HOME}${env:USERPROFILE}/.azure", "target":"/home/vscode/.azure"},
    // Mount docker socket for docker builds
    {"type": "bind", "source": "/var/run/docker.sock", "target": "/var/run/docker.sock"}
  ],

By default, if the src doesn't exist on the host the dev container start fails. In some scenarios it is desirable to create a mount if it exists, but it is preferable to continue without the mount rather than fail to start.
An example is when you wish to mount the .azure folder from the host into the dev container to share login credentials between host and container as a convenience mechanism. In this scenario, it would be nice to make the mount optional, i.e. to strip the mount out of the configuration if the src doesn't exist on the host. In this example, this would be if the user doesn't have the azure CLI installed on the host. If the mount was optional, the dev container would still run and the user would log in inside the dev container.
With this extra property to items in the mounts array to allow bind mounts to be indicated as optional, the above bind mount for the .azure folder would look like:
 "mounts": [
    // Mounts the login details from the host machine to azcli works in the container
    {"type": "bind", "source": "${env:HOME}${env:USERPROFILE}/.azure", "target":"/home/vscode/.azure", "optional": true},
  ],

This could also be supported by the string form:
 "mounts": [
    // Mounts the login details from the host machine to azcli works in the container
    "type=bind,source=${env:HOME}${env:USERPROFILE}/.azure,target=/home/vscode/.azure,optional=true",
  ],

Instead of having a boolean for one case, it might make sense to allow different solutions if the desired mount target does not exist.
Example:
 "mounts": [
    // Keep command history
    {"type":"volume", "source": "my-bash-history", "target":"/home/vscode/commandhistory"}
  ]

would benefit from an automatically created host folder, instead of ignoring the mount.
My users are notoriously lazy when it comes to reading the repository readmes, they would complain if their shell history is lost with every recreate, just because the host folder doesn't exist.

@stuartleeks: If you use yamlc as language in your codeblock, it stops complaining about the comments 👍🏼

@max06, that's a good point.
In which case, potentially something like an onMissingSource option instead of optional:
 "mounts": [
    // Mounts the login details from the host machine to azcli works in the container
    {"type": "bind", "source": "${env:HOME}${env:USERPROFILE}/.azure", "target":"/home/vscode/.azure", "onMissingSource": "skip"},
  ],

This would allow for a value of skip which would give the same behaviour as optional:true in the original suggestion.
It could also allow create which would create the host folder.
That said, in discussion with @chrmarti, it sounds like there are challenges here as the docker context that is used for building/running containers could be remoted over SSH. In this scenario, I'm not clear how we would test for the existence of host paths.

That said, in discussion with @chrmarti, it sounds like there are challenges here as the docker context that is used for building/running containers could be remoted over SSH. In this scenario, I'm not clear how we would test for the existence of host paths.

PS C:\Users\max06> docker run -it --rm --mount type=bind,source=/home/max06/nada,target=/tmp/test ubuntu
docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /home/max06/nada.

This example (executed in windows) uses a docker context with a docker socket over ssh on a linux host. This requires the source of the mount to be located on that docker host. Testing for it is simple: Try to bind mount it. The docker cli returns an error if the source doesn't exist.

Trying to bind mount to test if something exists takes time. In the SSH case we also have an ssh connection that we use to run the docker (and other) commands, we can use that to check for files/folders. One edge case with that is when the Docker daemon still runs somewhere else and does not bind mount to the filesystem on the SSH server (similarly with local and WSL cases) - we might have to detect this and fall back to using a temporary container.

I don't think we'd need to test the bind mount as much as see if the source folder exists on the host. If it doesn't, we remove the mount.
FWIW - I hacked in a workaround into one of the templates to create the source folder if it doesn't exist in a way that works on both Windows and macOS/Linux.  It's a bit hacky though since I fake out "bash" on Windows using a bash.cmd file.
https://github.com/devcontainers/templates/tree/main/src/kubernetes-helm/.devcontainer

There's an "oldschool" way of using devcontainers on a remote machine, before it could be done through the ssh remote extension: By setting a docker context to a ssh target:
PS C:\Users\max06> docker context ls
NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT                             KUBERNETES ENDPOINT   ORCHESTRATOR
datengrab           moby<EMAIL_ADDRESS>
Not sure if you have a control channel to the target machine this way.

Yep. We've updated guidance here. https://code.visualstudio.com/remote/advancedcontainers/develop-remote-host#_connect-using-the-remote-ssh-extension-recommended

Guess I should update my setup here then 😅

This would be really powerful if we could also use variables in the mounts other than just the devcontainerId. I was thinking about how the various persistence features could be rolled into the features that install apps like the various cloud cli
I was thinking something like
{
  "options": {
    "persistence": {
      "type": "boolean",
      "description": "Should persistence be enable for authentication token",
      "default": true
    },
    "tokenpath": {
      "type": "string",
      "description": "Path to your existing token files",
      "default": ""
    }
  },
  "mounts": [
    {
      "source": "auth-token-volume",
      "target": "/dc/auth-token",
      "type": "volume",
      "enable": "${option:persistence}"
    },
    {
      "source": "${option:tokenpath}",
      "target": "/dc/bound-token",
      "type": "bind"
    },
    {
      "source": "${localEnv:APP_AUTH_PATH}",
      "target": "/dc/env-bound-token",
      "type": "bind"
    }
  ],
  "containerEnv": {
    "APP_AUTH_PATH": "/dc/bound-token"
  }
}

Having optional mounts would still be amazing, but we are getting around the mount point not existing with an initalize command:
"initializeCommand": {
    "mkdir-posix": "mkdir -p $HOME/.config $HOME/.docker || true",
},

Strong support here as well; running into issues where I need a directory to be present, both for Windows and POSIX hosts. Unsure how to handle this atm, optional would allow us to handle it after container init.

My use case is embedded development, where the serial tty devices may or may not exist depending on which one is in use. Writing firmware for hardware agnostic platforms like Zephyr RTOS, this happens a lot. I'm constantly switching from the ESP32's serial debug output on ttyACM0 to a different board with a different usb chip coming in as ttyUSB0 or the CMSIS-DAP adapter that needs a particular /dev/bus/usb device mounted. Currently, I have to unplug and replug the right device, determine where it'll be mounted, edit the config, and restart the container. it'd be preferred if I could list all of my device mounts, and have it just mount the ones that exist when the container restarts.


Update Makefile for CI

Descriptions:

add kind and non-kind options for when installing dependencies
add 'go mod vendor'

Will merge to unblock openshift/release PR and address comments in further PR.


Support for commonjs output - wouter-preact blocks ts-jest on import statements

Hello! :)
I've just added wouter-preact to my preact + typescript boilerplate. I'm using ts-jest for tests with ts-jest preset. Unfortunately I cannot test app.tsx component which contains
import { Link, Route } from 'wouter-preact';
After running yarn test I've got:

FAIL  src/app/app.spec.tsx
● Test suite failed to run
/home/mk/Documents/repos/preact-ts-parcel/node_modules/wouter-preact/index.js:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import locationHook from "./use-location.js";
                                                                                ^^^^^^^^^^^^

SyntaxError: Unexpected identifier

  1 | import { h } from 'preact';
> 2 | import { Link, Route } from 'wouter-preact';
    | ^
  3 | import { TypedComponent } from '../shared/typings/prop-types';
  4 | import { actions, StoreState } from '../store';
  5 | import { useAction, useSelector } from '@preact-hooks/unistore';

  at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
  at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:579:25)

I'm not saying that this is a problem with wouter-preact itself, because it may be e.g. ts-jest problem or maybe even I did something wrong in terms of configuration (see below) but could you add also commonjs output?
jest.config.js
module.exports = {
    preset: 'ts-jest',
    roots: ['<rootDir>/src'],
    verbose: true,
    transform: {
        '^.+\\.(t|j)sx?$': 'ts-jest',
    },
    testRegex: '(/__tests__/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$',
    moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx', 'json', 'node'],
};

tsconfig.json:

{
    "compilerOptions": {
        "outDir": "./dist",
        "sourceMap": true,
        "noImplicitAny": true,
        "module": "commonjs",
        "strict": true,
        "moduleResolution": "node",
        "esModuleInterop": true,
        "allowSyntheticDefaultImports": true,
        "target": "es6",
        "jsx": "react",
        "jsxFactory": "h",
        "allowJs": true
    },
    "include": ["./src/**/*"],
    "exclude": ["node_modules", "**/*.spec.ts", "**/*.spec.tsx"]
}

I've been trying with different tsconfig.json configurations (also without "include" & || "exclude" fields) but without success.
Related issue (?): https://github.com/molefrog/wouter/issues/70

For future readers:
There is transformIgnorePatterns key in jest.config.js whose default value is ["/node_modules/"] (according to: https://jestjs.io/docs/en/configuration#transformignorepatterns-array-string)
In that case white-listing helped:
transformIgnorePatterns: ['node_modules/(?!(wouter-preact)/)']
But still - it would be more convenient if we wouldn't have to do so.

Hey @kolodziejczakM thanks for the interest in the project. wouter-preact package is relatively new and didn't come with bundled CJS source, while the main package did.
I have just released a patch version v2.3.1 of both packages with proper Preact CJS sources. In<EMAIL_ADDRESS>you will have:
cjs/index.js
cjs/matcher.js
...
index.js
matcher.js
...

And the package.json file should now contain a main field poiting to the CJS entrypoint.


(Beta) UI component - Badge

As a: Full stack developer
I want: Use the "badge" from the UI library
so that: I can spend more time creating features or capabilities that will provide value to my users and stakeholders
Acceptance criteria

[x] Create web component
[x] Create React wrapper
[x] Passing unit tests
[x] Linting
[x] Include in "canvas" web component storybook
[x] Push to Alpha
[x] Manual design review

Presentable outcomes

[x] I can show the ui-component in storybook and provide the link to service teams so that they can view the component for themselves
[x] Show the service teams how to use the component in a sample project in either React or Angular

Sprint Ready Checklist

Acceptance criteria defined
Team has defined steps to satisfy acceptance criteria
acceptance criteria is verifiable / testable

Related issues:
GitHub issue: Blocked by #355
Resources:
Mockups: Badge design
Images:
Testing URL:
https://ui-components-ui-components-dev.os99.gov.ab.ca/?path=/docs/components-badge--page

Design review will be completed once issue #354 has been completed.

:tada: This issue has been resolved in version 1.0.0-alpha.9 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.4.0-alpha.12 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Noticed a styling issue with the "badge with text-only" variant @bluekurinji to investigate and provide options.

Issue blocked by issue #417 (need to get definition on what constitutes a Beta component)

Right now we don’t have the institutional knowledge to easily solve the accessibility knowledge gap. The issue will remain blocked until we can get some help/expertise to help out.

:tada: This issue has been resolved in version 1.0.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.0.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use the newer API to define autocmds

Now Neovim has Lua API's to set/get/delete autocmds. Use it.

mistaken ;(


[Feature]Add support to render advanced banner in list.,

Description
Add support rendering advanced banners in lists.

@deeg what do you think?

I will take a look today.

@volser I have added unit tests in clickup_frontend repo.
The unit tests for this repository are still broken, I have asked @mattlewis92  for help us taking a look.

@volser Added unit tests for banners. can I get approval on this PR?
Thanks:)


[SMALLFIX] A small fix to avoid null ptr

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12989/
Test PASSed.

@apc999  PTAL

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12990/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12991/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12992/
Test PASSed.

@apc999  updated the comment. PTAL. thanks

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12996/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12997/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12999/
Test PASSed.

@peisun1115  one minor comment left. Otherwise LGTM

@apc999 I've addressed your comment

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13000/
Test PASSed.


V0.10.0 release

v0.10.0

Change Scalar::from_bytes to work for Scalar<_, NonZero> as well.
Updated compatibility to rust-secp256k1 v0.28.0
Bumped MSRV to 1.63.0 to reduce friction
Added share_backup module in schnorr_fun
Added arithmetic_macros to make g! and s! macros into procedural macros
Made even Secret things Copy. See discussion here.

Release tagged at 90105182f9fc39d4d151cdd2b637b3bd26f160eb


Full support 64 bit integers with BigInt

Well this is not full ready yet, but I'd like to bring some discussions:

To use SQLite int64 instead of int32, because JS Number type is always 64 bits;
That would make possible to serialize BigInt in queries;
Also would make possible to use numbers (with BigInt) between 2^53 and -2^53.

This seems fine, why is it locked?

@renatoalencar Would you be able to rebase the PR? 🙂

@renatoalencar Would you be able to rebase the PR? 🙂

Sure! I'll try to do that later today.

@renatoalencar Thanks! I've had a quick look and I think the PR might need some gating on NAPI_VERSION, because I'd like to maintain N-API v3 support for Node 11/13 (preferably we can avoid doing a breaking release right now). But it LGTM otherwise 🙂

@renatoalencar Thanks! I've had a quick look and I think the PR might need some gating on NAPI_VERSION, because I'd like to maintain N-API v3 support for Node 11/13 (preferably we can avoid doing a breaking release right now). But it LGTM otherwise 🙂

I was expecting something like that, as I've mentioned my first implementation wasn't really ready. But I added the extra checks and seems to be working.
Thank you

In the meantime, I forked your repository at https://github.com/juanrgm/node-sqlite3/tree/int64-support and forced the build from source (https://github.com/juanrgm/node-sqlite3/commit/881d6bfa5809b8b6dd3e7e75d7f23a8ba70341a8) for installing with npm easily:
npm install https://github.com/juanrgm/node-sqlite3/tarball/int64-support

const sqlite3 = require('sqlite3').verbose();
const db = new sqlite3.Database(':memory:');

db.serialize(() => {
    db.run("CREATE TABLE t (v INTEGER)");
    const v =<PHONE_NUMBER>091516928n
    const stmt = db.prepare("INSERT INTO t VALUES (?)");
    stmt.run(v)
    stmt.finalize();
    db.each("SELECT v FROM t", (err, row) => {
        console.log({ row });
        if (row.v !== v)
            throw new Error('Not equal')
    });
});

db.close();


id-pool: Fix allocation overflow and the leak of the first ID.

The range of IDs should be [base, base + n_ids),
but id_pool_alloc_id() allocated the range of IDs is [base, base + n_ids].
And id_pool_free_id() cannot free the ID value base correctly.

I apologize for the unacceptably long time to review.
This looks like a useful bug fix to me.  Thank you.  Can you provide a Signed-off-by to allow us to apply it to the repository?
Thanks,
Ben.

@blp , thanks!
I added a Signed-off-by into the repository.

Thanks.  I applied this to master.


Add adst nft

Codecov Report
Patch coverage: 80.95% and project coverage change: -0.58% :warning:

Comparison is base (e422366) 63.72% compared to head (9b5ab53) 63.14%.
 Consider uploading reports for the commit f75d9de to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #381      +/-   ##
==========================================
- Coverage   63.72%   63.14%   -0.58%
==========================================
  Files          79       79
  Lines       22109    22127      +18
==========================================
- Hits        14088    13972     -116
- Misses       8021     8155     +134

Files Changed
Coverage Δ

pallets/adst/src/lib.rs
57.71% <74.60%> (+5.87%)
:arrow_up:

pallets/adst/src/tests.rs
95.96% <100.00%> (+0.82%)
:arrow_up:

... and 3 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


requestTemperatures() blocks until one sensor is ready not all of them

Docs imply that requestTemperatures will block until conversion is complete. I have 4 sensors on a single 1 wire channel and was noticing frequent failures. Digging into this library, it looks like isConversionComplete return when one of the sensors is ready rather than all of them.
I've changed checkForConversion to false to workaround the problem, but either the docs should be update for code enhanced to be clear that requestTemperatures doesn't check for all sensors to complete.

Hmm, interesting spot. Thanks for the report. We'll look into it


Python 3.x dependency

Is Python 3.x really a necessary dependency? There is an explicit version check in setup.py but it works on Python 2.7 if you comment it out.

Yeah I just came across this too. I've backtracked to an older version until this is fixed, or at least explained...

Indeed, Python 3 is not needed for installing (using setup.py).
However, there some auxilliary utils, e.g.  conversion functions in some extensions packages that still require python 3 (or at least have been written with Py3 in mind). You are welcome to check this, and perhaps propose a PR which may update the dependancy  in setup.py, but provide a clear Warning to the users.
You may also consider upgrading to py3... :-)

@edvald to which version did you backtrack to?

Sorry about the (very) late response. I had just checked out the commit hash previous to the setup.py change. But now I see that its been changed to show a warning instead of an error, so that works nicely!
I wish I could just switch to Py3 but, as is often the case, there's a whole lot of incompatible code that I need to deal with first... Hopefully I'll get there soon :)
And thanks for all the work on this project, it's been very useful!

Thanks for the feedback.


Enhancement: extend the spo site apppermission get command to show the roles

We should enhance the spo site apppermission get command to show the roles granted to the specific permission. Right now the role is missing which makes it hard to understand what permissions the particular app has granted on the site.

Hi @waldekmastykarz
Can I work on this?

Please do! Thank you! 👏

Hi @waldekmastykarz
We should also extend the spo site apppermission list command to show the roles.

Good idea. Could you please create a separate issue for it so that we can track it?


Browser themes

Adds dark mode and support for custom themes.  Themes are switched using a dropdown menu in the top right.  This uses localstorage, so theme choice should persist between sessions until the browser cache is cleared.  We're required to have "at least a landing page" by Wednesday, so a couple of minor things related to that are also in here.
Additionally, this updates our version of bootstrap from 5.1 to 5.3.

The dark blue theme changes the background but I didn't see any change with the dark theme.  Do I need to change something on my end?


Stuck boot on fresh install of ChimeraOS

After a fresh install of ChimeraOS, screen gets stuck at [drm] VT-d active for gfx access. I am unable to switch TTYs or do anything other than rebooting with the power button.

I would usually manage to resolve issues like this by adding nomodeset to the boot flags. However I have been unsuccessful in either getting an edit menu when booting, or locating the file to edit from the arch installer ISO.
System details:

Intel i9-12900
Nvidia RTX A5000

What version of the Nvidia drivers are installed? Perhaps they are not new enough for my GPU?

Don't know why I couldn't see it before but the boot config file is at /boot/EFI/BOOT/syslinux.cfg. I added nomodeset to the append line and now I am no longer stuck at the point shown in the OP.
I am now able to switch ttys, but the boot messages on tty6 never clears and after running chimera-session it just takes me back to the incomplete boot process.

I think you are in an (still unsupported) hybrid graphics configuration. Those unfortunately are hit n miss. Since you are able to enter a TTY, could you report on what does Xorg.0.log reports?

Looked earlier in dmesg and saw that the Nvidia driver hadn't loaded correctly.
Fixed the issue by adding ibt=off to the boot flags - see https://github.com/NVIDIA/open-gpu-kernel-modules/issues/256#issuecomment-1138851460.

Just to chime in: I had the exact same issue. Adding ibt=off workes great. Thanks!

Still the case on a new install with a 2070.
I also did a “steam os upgrade” whatever that is and I had to apply this fix again.

Note: ibt=off is now included in the kernel parameters written by frzr 0.11.2

Should be fixed in upcoming release


feat: enable splits for popup mode

Fixes #7542

Description of what you did:

My PR is a:

[ ] 💥 Breaking change
[ ] 🐛 Bug fix
[x] 💅 Enhancement
[ ] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

/lgtm


Provide a simple way to override schema type for a given field, prior to codegen step

Is your feature request related to a problem? Please describe.
My schema has a jsonb scalar fileld type. However, the TypeScript codgen plugin simply resolves this to an any TypeScript type. I am looking for a way to provide a custom override type for that field, so that I can get access the JSon contents of that field in a stongly typed way.
Describe the solution you'd like
I would like to simple mechanism to provide a custom type for a given field, so that the code-generation uses the custom priovided type instead of the original schema provided type
Describe alternatives you've considered

I have defined an additional client schema with the desired field type, but (logically) get codegen errors saying that the field is already defined
I have looked for ways of easily altering the schema prior to the code-gen step, but am struggling to figure it out.

Additional context
I am using an Hasura API, with typescript and typescript-react-apollo plugins

@ahrnee just overriding the field doesn't work?
redeclare it in a .graphql file and add it to your schema:, i think it should override the field type.

@dotansimha - thanks for your response, but that doesn't seem to work in my case. I get the following error:
  Unable to merge GraphQL type "MyEntity": Field "myjsonbfield" already defined with a different type.
  Declared as "MyCustomFieldType", but you tried to override with "jsonb"

Some Futher Details:

Im using the Hasura GraphQL engine, which always results in a "jsonb" scalar for all jsonb field types
I have a client .graphql where I tried to redeclare the field type

Sidenote
I also have a feature-request in with the Hasura Team to custom scalar types to be configured for jsonb fields, but at present this is not possible.

Same problem here.
We generate types from Datocms GraphQL API.
Most of enums are just Scalars['String'].
We really need to override for some fields and we can not change the source API.
We tried to define a local schema but we have the same Error
Unable to merge GraphQL type "TitleRecord": Field "variant" already defined with a different type. Declared as "Variant", but you tried to override with "String"
        Error: Unable to merge GraphQL type "TitleRecord": Field "variant" already defined with a different type. Declared as "Variant", but you tried to override with "String"

It would be very nice to allow merge if needed

Just checking, is it still the recommended way to use something like graphql-compose for this?
Getting an enum in a query (defined as string in the schema), and would like to override the generated type for it. Is there a plugin to modify the schema somehow before it is read by the code generator?

I think there's a good chance a lot of hasura users will be looking for something like this, here's a link to an example using a custom schema loader: https://github.com/hasura/graphql-engine/issues/3451#issuecomment-846426643


It’s too tiring to write open source by myself, so find a partner and write together.

It’s too tiring to write open source by myself, so find a partner and write together.
来个老铁，一起写开源吧，压力有点儿大，一起try!
Leave a positive message and I will respond actively.
留言即可有机会参与~~~

Hi, Bruce! I want to join your project.

Hi, Bruce! I want to join your project.

Contact me via WeChat (brucepang0618) or email (brucepang0618@gmail) to learn about your technical mastery