Download failure of multimedia messages in Docker edition

Hi
Installing the MTProto_Proxy on Docker using different methods mentioned on the project docs, the proxy on the clients works fine for text messages, but fails to download multimedia messages!
What would cause this problem?

Hi. The Docker Hub version is outdated (because they removed the free access for opensource projects), so I think it will only work if you build it yourself as described here:
https://github.com/seriyps/mtproto_proxy#to-run-with-custom-config-file

Thanks, but when I try to build the Docker image, I face some errors. Here is the complete log:
[+] Building 11.2s (9/22)
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 892B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/alpine:3.9                                                                                0.4s
 => [internal] load metadata for docker.io/library/erlang:21-alpine                                                                                0.4s
 => CACHED [builder  1/12] FROM docker.io/library/erlang:21-alpine@sha256:7b77dba3d0207eab81fd11a90569b8a08ca56a5c660bba02b69be630ddc6befe                                                                    0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 1.45kB                                                                                0.0s
 => CACHED [stage-1 1/5] FROM docker.io/library/alpine:3.9@sha256:414e0518bb9228d35e4cd5165567fb91d26c6a214e9c95899e1e056fcd349011                                                                            0.0s
 => ERROR [stage-1 2/5] RUN apk add --no-cache openssl &&     apk add --no-cache ncurses-libs &&     apk add --no-cache dumb-init                                                                            10.5s
 => ERROR [builder  2/12] RUN apk add --no-cache git                                                                                10.5s
------
 > [stage-1 2/5] RUN apk add --no-cache openssl &&     apk add --no-cache ncurses-libs &&     apk add --no-cache dumb-init:
#0 0.450 fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/main/x86_64/APKINDEX.tar.gz
#0 5.454 fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/community/x86_64/APKINDEX.tar.gz
#0 5.454 WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.9/main/x86_64/APKINDEX.tar.gz: temporary error (try again later)
#0 10.46   openssl (missing):
#0 10.46     required by: world[openssl]
#0 10.46 WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.9/community/x86_64/APKINDEX.tar.gz: temporary error (try again later)
#0 10.46 ERROR: unsatisfiable constraints:
------
------
 > [builder  2/12] RUN apk add --no-cache git:
#0 0.445 fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/main/x86_64/APKINDEX.tar.gz
#0 5.451 fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/community/x86_64/APKINDEX.tar.gz
#0 5.451 WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.13/main: temporary error (try again later)
#0 10.46   git (no such package):
#0 10.46     required by: world[git]
#0 10.46 WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.13/community: temporary error (try again later)
#0 10.46 ERROR: unable to select packages:
------
Dockerfile:21
--------------------
  20 |     FROM alpine:3.9
  21 | >>> RUN apk add --no-cache openssl && \
  22 | >>>     apk add --no-cache ncurses-libs && \
  23 | >>>     apk add --no-cache dumb-init
  24 |
--------------------
ERROR: failed to solve: process "/bin/sh -c apk add --no-cache openssl &&     apk add --no-cache ncurses-libs &&     apk add --no-cache dumb-init" did not complete successfully: exit code: 1

Oh, it might be that Alpine linux 3.9 is no longer available? Can you try to edit the Dockerfile and replace the following lines:
- FROM erlang:21-alpine as builder
+ FROM erlang:24-alpine as builder

- FROM alpine:3.9
+ FROM alpine:3.18

and run docker build -t mtproto-proxy-erl . again?

Did it, but not successful either:
[+] Building 11.2s (9/22)
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 893B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/alpine:3.18                                                                                0.2s
 => [internal] load metadata for docker.io/library/erlang:24-alpine                                                                                0.4s
 => CACHED [builder  1/12] FROM docker.io/library/erlang:24-alpine@sha256:51e0f2b9f3e82ba59257ae22bc6cb740efccfe0e1026332e9e69fa807e43a831                                                                    0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 1.45kB                                                                                0.0s
 => CACHED [stage-1 1/5] FROM docker.io/library/alpine:3.18@sha256:02bb6f428431fbc2809c5d1b41eab5a68350194fb508869a33cb1af4444c9b11                                                                           0.0s
 => ERROR [stage-1 2/5] RUN apk add --no-cache openssl &&     apk add --no-cache ncurses-libs &&     apk add --no-cache dumb-init                                                                            10.5s
 => CANCELED [builder  2/12] RUN apk add --no-cache git                                                                                10.6s
------
 > [stage-1 2/5] RUN apk add --no-cache openssl &&     apk add --no-cache ncurses-libs &&     apk add --no-cache dumb-init:
#0 0.392 fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
#0 5.398 fetch https://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
#0 5.398 WARNING: fetching https://dl-cdn.alpinelinux.org/alpine/v3.18/main: temporary error (try again later)
#0 10.40 WARNING: fetching https://dl-cdn.alpinelinux.org/alpine/v3.18/community: temporary error (try again later)
#0 10.40 ERROR: unable to select packages:
#0 10.40   openssl (no such package):
#0 10.40     required by: world[openssl]
------
Dockerfile:21
--------------------
  20 |     FROM alpine:3.18
  21 | >>> RUN apk add --no-cache openssl && \
  22 | >>>     apk add --no-cache ncurses-libs && \
  23 | >>>     apk add --no-cache dumb-init
  24 |
--------------------
ERROR: failed to solve: process "/bin/sh -c apk add --no-cache openssl &&     apk add --no-cache ncurses-libs &&     apk add --no-cache dumb-init" did not complete successfully: exit code: 1

Hi. The Docker Hub version is outdated (because they removed the free access for opensource projects), so I think it will only work if you build it yourself as described here:
https://github.com/seriyps/mtproto_proxy#to-run-with-custom-config-file

Would you please consider using Github Container registry instead of Docker Hub?

Hi. The Docker Hub version is outdated (because they removed the free access for opensource projects), so I think it will only work if you build it yourself as described here:
https://github.com/seriyps/mtproto_proxy#to-run-with-custom-config-file

Would you please consider using Github Container registry instead of Docker Hub?

You mean the project contributors should consider using GitHub Container registry instead of Docker Hub, so that we can use it, am I right?


[ADMINAPI-1017] OSSF Scorecard Implementation

 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.


Include file hierarchy in object file names?

"Collisions" among object files in a .a archive isn't a problem as the linker doesn't care about those file names. Reflecting the file hierarchy in the file name, like acton$rts.o for acton/rts.o would only be for humans to look at.
We don't really know what the debugger does. @nordlander had some difficulties with lldb on mac, which was asking for .o files etc. Until we know more and if it really influences things, I'm closing this. Let's keep things the way they are. If we have more information in the future, we can reopen and revisit.


Add functionality to make event headers optional

Sometimes the header image is sufficient (the name, date and place is included in it) so the overlay text is not needed.
A solution would be to add a boolean field to the event model that decides whether or not to display the header text.

It already exists.... Kek
Edit event -> text alignment


From whatsapp to my cordova app

I keep getting a column __data doesn't exist error when sharing from whatsapp to my app.
It only works on gallery and only on certain images.
My phone is Android 7.0
This does work on Android 6.0

I am facing the same problem for Android v7 and some phones which has v6.0.1

https://github.com/hiddentao/cordova-plugin-filepath/issues/5
solves the issue for Whatsapp as well.

Hi @hocker-app and @charlizesmith - are you still encountering issues with this?


It's not possible to refer to an external nodes in informationRequirement and knowledgeRequirement

Using informationRequirement and knowledgeRequirement can refer to internal and external nodes using the href attribute.
Please notice the case of internal nodes above:
        <informationRequirement>
            <requiredDecision href="_decision_001"/>
        </informationRequirement>
        <informationRequirement>
            <requiredInput href="_input_001"/>
        </informationRequirement>
        <knowledgeRequirement>
            <requiredKnowledge href="_bkm_001"/>
        </knowledgeRequirement>

This case is currently working as expected.
The spec 12.3.2 References within the DMN XSD states that is it possible to refer to external nodes using the following syntax:
        <informationRequirement>
            <requiredDecision href="http://www.montera.com.au/spec/DMN/0091-local-hrefs#_decision_001"/>
        </informationRequirement>
        <informationRequirement>
            <requiredInput href="http://www.montera.com.au/spec/DMN/0091-local-hrefs#_input_001"/>
        </informationRequirement>
        <knowledgeRequirement>
            <requiredKnowledge href="http://www.montera.com.au/spec/DMN/0091-local-hrefs#_bkm_001"/>
        </knowledgeRequirement>

This case is currently NOT working

@yesamer
IIUC, this is the test/model you are referring to, but the  namespace in the href attribute
href="http://www.montera.com.au/spec/DMN/0091-local-hrefs#_decision_001"
is the namespace of the model itself
<definitions namespace="http://www.montera.com.au/spec/DMN/0091-local-hrefs"
so it is not a reference to an external node

@gitgabrio Yes, that particular case refers to the same document. BUT, according to the specs ^^ (12.3.2 References within the DMN XSD) it should work with external nodes too. Is it correct or did I misunderstand the specs?

@gitgabrio So that means it's not working in the case the namespace points to itself, is that right?


add database branch password resource

fixes #6

Would you please cut a release after merging it?

@s1ntaxe770r would you please take a look this PR?

Oh snap , Thanks a bunch @cemo ,  looking over it now


Something went wrong with the indexing of a recent bag

e.g.
12:14:35.348 [main-actor-system-akka.actor.default-dispatcher-7] ERROR u.a.w.p.a.i.bags.BagIndexerWorker - java.lang.Exception: Failed to load BagRegistrationNotification(born-digital,cold_store/A Images,v1,RegisteredBagNotification), got BagTrackerNotFoundError()

We should debug what went wrong, and fix it. My guesses are a DynamoDB consistency error, or something to do with spaces.

[ ] Allow eventually consistent DynamoDB reads in scala-libs, and use them in the bag tracker
[ ] Retry BagNotFound errors in the indexers

Based on a conversation with @kenoir, we're going to fix this in two ways:

The bag tracker should do eventually consistent reads, so if we do a read-straight-after-write, we'll wait for the bag to be available.
The bag indexer should cope with a NotFound error from the bag tracker, and retry.

I'm going to reindex all the bags that have spaces, then we should be able to close this ticket.

Looks like it was a single bag, because @kenoir has been deleting all the old bags with spaces. Closing as done.


replace-dependency: fix a syntax error while generating references.nix

Description of changes
Fixes #177103
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Does this need to be backported to release-22.05?

I don't know whether the error started appear before or after 22.05 (and perhaps it's dependent on installed packages on the system in question).


Resolve undefined step for ocis localAPITests

Description
Seems like we have got some undefined or unimplemented steps on ocis for the step below. Find the step and resolve the undefined step. Also investigate why drone is not responding for undefined step.
Build Link : https://drone.owncloud.com/owncloud/ocis/15382/41/7
382 scenarios (372 passed, 4 failed, 6 undefined)
4017 steps (3998 passed, 4 failed, 6 undefined, 9 skipped)
16m39.97s (21.22Mb)

--- FeatureContext has missing steps. Define them with these snippets:

    /**
     * @Then as user :arg1 file :arg2 inside space :arg3 should contain a property :arg4 with value :arg5
     */
    public function asUserFileInsideSpaceShouldContainAPropertyWithValue($arg1, $arg2, $arg3, $arg4, $arg5)
    {
        throw new PendingException();
    }

    /**
     * @Then as user :arg1 folder :arg2 inside space :arg3 should contain a property :arg4 with value :arg5
     */
    public function asUserFolderInsideSpaceShouldContainAPropertyWithValue($arg1, $arg2, $arg3, $arg4, $arg5)
    {
        throw new PendingException();
    }```

@phil-davis  Upon debugging, the main problem why drone is not responding is due to expected to failure linting on ocis. Though the undefined steps makes the exit code 1 but the error for the not shown in the console for the undefined step and upon linting the expected to failure the it makes exit code 0 (success). May be a refactor to run.sh is required to make it work for the undefined step on ocis

May be a refactor

Yes, we need to somehow detect if the Behat run had any undefined steps. If so, then fail the pipeline straight away - do not bother trying to check expected-failures etc.

both pr has been merged so closing


Fix/rename promises

@jamessimone - Thoughts?
This PR renames Promise to QueueableProcess and EnqueueNextQueueableProcessStep.
documentation has been updated to reflect the new name, and why.
!closes #20

Those are definitely more explicit names! Thanks for putting this together.


Fix for few FPs

As promised in my last PR, here are 10 more FPs. There are a few more FPs, but I forgot to label them as PL 1 and they got mixed with my PL 2 FPs. @theseion if you find a typo or mistake, kindly make changes where necessary. Thank you.
Also, we need to update the plugin version to 1.0.1, as done with WordPress plugin.

Thanks you very much! Yes, we will increase the version number.

Thanks you very much! Yes, we will increase the version number.

I can increase it from my side. It's a simple sed command.

I can increase it from my side. It's a simple sed command.

No, I'd rather have a separate PR for that.

There's something wrong with the test setup. I need to investigate that before we can merge.
That reminds me: if you're up for it it would be nice to have your FP's covered by tests.

Guys, i would not change the version numbers yet. None of the plugins was officially released yet and there is no need for a version change. Let's wait until CRS 4.0 and then we will release all plugins under current versions (and also we will do a downloadable release here on github).

@Xhoenix Can you add yourself into the CONTRIBUTORS.md? Thanks.

@Xhoenix rule ID 9508602 is a duplicate, that's why the tests fail.

Thanks @Xhoenix. @azurit, I'll leave merging to you.

Merged, thanks to everyone!


Fix bug preventing GPU workers from being created

Damn I guess this has never worked huh lol.

When you merge this could you please update the dependency in pippin_nano_wallet to the latest commit hash. Thanks.


select statement

Add select to the language
examples:
a = make(chan int64, 1)
select {
    case <-a:
        pritnln("value received on a")
    default:
        pritnln("default")
}

a = make(chan int64, 1)
b = make(chan int64, 1)
b <- 2
val = 0
select {
    case val = <-a:
        pritnln("value " + val + " received on a")
    case val = <-b:
        pritnln("value " + val + " received on b")
}

Codecov Report

Merging #286 into master will increase coverage by 0.49%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #286      +/-   ##
=========================================
+ Coverage   84.41%   84.9%   +0.49%
=========================================
  Files           8       8
  Lines        1989    2054      +65
=========================================
+ Hits         1679    1744      +65
  Misses        227     227
  Partials       83      83

Impacted Files
Coverage Δ

vm/vmStmt.go
89.35% <100%> (+2.04%)
:arrow_up:

Continue to review full report at Codecov.

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

I fixed the PR, everything is working well now.

@alaingilbert Could you look again at some of the previous comments?


pom cleanup: gpg and javadoc

The pom had two different versions of the maven-gpg plugin specified, so I fixed that.
Javadoc also wasn't building in JDK8 because apparently self-closing HTML tags aren't allowed in Javadoc as of JDK8. Rather than changing all the javadocs, let's pass -Xdoclint:none to the javadoc plugin and disable that check for now.

Whoops, wrong fork.


Sample rate

Hello folks,
I have same questions about sample rate of the models.
I saw that in the configuration .json files it set to 200Hz. Let's assume I had sensor with different sample rate from 200Hz.
Is it need to train models, evaluate and export them changing the configuration parameter about sampling rate(in .json files) with my sensor sampling rate?
Also I saw this in the source code:
// print(generate_arm_biquad_sos(10, 30, 200, order=3, var_name="qrsBandPass"))
// print(generate_arm_biquad_sos(0.5, 30, 200, order=3, var_name="ecgBandPass"))
Those function also should be execute with my sensor sample rate. Am I right?
BR, Nikolay

Hi Nikolay,
That is correct- the current set of models are trained directly on 1-lead ECG data w/ specified sampling rate. The models will need to be retrained for different sampling rate -OR- resample your sensor data before running it through the model.
If the models are retrained, the filter coefficients will indeed need to be updated along with configs in constants.h and sample stimulus data in stimulus.h if looking to test on hardware.
As a heads up, I am working on revamp of HeartKit that will better separate tasks/classes, new models, different feature sets (e.g. HRV metrics, PPG), leverage PhysioKit, and add task-specific demos. This is currently under development in branch feat/physiokit.


A few rules with empty colors.

This theme has a few rules with empty colors, which is causing Python Interactive to break, as Monaco Editor does not handle those cases.
https://github.com/microsoft/vscode-python/issues/5827

Jeez, sorry man, never got a notification for the first issue 😬

Haha, no worries.


Do not merge Work in progess - Trust Model

Initial content/structure for Trust Model
Including contributions from<EMAIL_ADDRESS>Shifting work to individual PR's
Updating with individual PR links

Trust Model Introduction -> https://github.com/confidential-containers/documentation/pull/22
Trust Model Personas -> https://github.com/confidential-containers/documentation/pull/24
Trust Model Lifecycle -> TBD
Trust Model Tee Boundary -> TBD

Will close this PR once I have all above available
Signed-off-by: James Magowan<EMAIL_ADDRESS>

I see this is a very early draft, but when you update this, please include all the source files for the png files to allow others to update the diagrams subsequently.

@magowan - can this be closed or marked as draft to avoid confusion? We seem to have 3 open PRs containing a trust model doc (this one, #22 and #24).

Yup closing as it is now driven by individual Prs


NEW VERSION

Hello I have camera with news firmware 5.5.0 how I can reset password?

Ask Hikvision support.


Add Guid as a unique property for UserModule

Add two properties to the User DataService Model (UserId and CreatedBy)
Add a new migration records to Migrations directory
Change the event arguments of CurrentUserEvent to be a dictionary parameter
Update the related view model to fit with latest changes

Based on this PR changes:

Admin users should not delete themself during the UserManagementView.
Other admin users cannot be deleted super or default user "Admin" by the selection.


Added basic architecture for common tests

Signed-off-by: ahcorde<EMAIL_ADDRESS>🎉 New feature
Summary
This PR is a simplifycation of this other PR https://github.com/gazebosim/gz-physics/pull/354
This draft PR try to set up a common arquitecture to test all physics engine under the same tests avoiding duplication and improving coverage.
Test it
colcon test --merge-install --event-handlers console_direct+ --packages-select ignition-physics6 --ctest-args -R COMMON

Checklist

[x] Signed all commits for DCO
[x] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

I like this, it's very much in line with what we discussed.
@scpeters what do you think?

@steve what do you think about this logic ?

@scpeters I'm not really sure about adding command line arguments to gtest. I will take a look

@scpeters I added this draft PR https://github.com/gazebosim/gz-physics/pull/359 with the changes required to use cmd line arguments

@scpeters Do you mind to review this PR https://github.com/gazebosim/gz-physics/pull/359 which built on top of this one?

@scpeters Do you mind to review this PR #359 which built on top of this one?

I just approved it 😄


Array.from does not try to use iterator protocol

In Chrome (without Polyfill), the following snippet produces the expected result:
var o = {};
o[Symbol.iterator] = function() {
  let i = 0;
  return ({
    next: function() {
      i++;
      return { done: i > 5, value: i};
    }
  });
};
Array.from(o);

(5) [1, 2, 3, 4, 5]

The same in IE11 with https://cdn.polyfill.io/v2/polyfill.min.js?features=es6 loaded returns an empty array:
[object Array]   []
   length        0

I discovered this actually with MobX observables, for which Array.from also produces an empty array.

same for me


New logo for Babybuddy

I wanted to contribute to Babybuddy. I designed a logo for it. If you like it, I'll send you files and pr. i hope you like it :)
is there anything you want ?

Hey! This is very neat, I like where you are going with it. A couple of requests/thoughts -

Do you think the baby could have a smile or happy-neutral sort of expression? I worry that it would ruin the "clock face" effect (which I love), but I would also like the logo to convey that BB can help make for a happier baby.
I wonder also if the eyeballs could be in a more normal position? Something about going up in opposite directions is a little odd. Although, my son's eyes were like that sometimes in the early days (:
Lastly, I wonder if it could go a different direction with the overall color of the logo? I think a non-skin tone color might be more appropriate. Baby Buddy does not have a particularly great color scheme, so I'm not quite sure what the best approach would be. Any thoughts? If you don't think that would work, I would focus on the two boxed-in white ones on the bottom row, which I think would fit Baby Buddy's dark theme at the right size and could have any number of secondary colors.

Thanks for your efforts. I took a look at some of your other PRs and you've done lots of cool stuff!

I made a few more designs for you :) Please take a look at these. If you have another opinion, you can tell me.

Nice. I'm liking the single color versions in the fifth column. One more variation idea -
Could the center of the clock hands be circular, with the hands a bit thinner and/or tapering (e.g. more like this but without the overlap at the center)?

Oh, okay. How is that?

Nice! I like it. Happy to accept a PR adding the blue variation to the repo (I think babybuddy/static_src/logo would make sense) and README. For asset files I'd love to have one with the background and an inverted version of just the logo in white with trans for the features.
Thanks very much for your contribution!

I am glad you like it :) I sent pr but If there is something you want to change in PR please tell me because, in addition I have added horizontal and vertical versions.
https://github.com/cdubz/babybuddy/pull/39
Here are all the files;
https://drive.google.com/open?id=1UxqIdRHw677Zq90mjIkObJcnaqLRnUEX

Closed by #39. Thanks again, @reallinfo!


Audio Files are Distorted when imported to Ableton Live

When attempting to import any audio sample into Ableton Live 10, the wavelengths are completely distorted like above. This might be caused by some frequency compression either on the site or the original export of the files. I attempted this on multiple samples from different audio collections. You can see the exact sample for the image above in the bottom left corner.
Acceptance Criteria:

Downloaded audio files can be properly played back in Ableton Live.

thank you, @cozma!  this is the type of technical user testing i needed.
if it's possible, can you send me two files:
(1) the wav file that you linked above in the screenshot
(2) any wav file that does work in your Ableton Live 10... it could be anything.  i just would like to compare the two on my machine
You can upload them to my dropbox:
https://www.dropbox.com/request/agxFc8AQ0JYOdlf121yE
And lastly, what OS are you using?

thank you, @cozma! this is the type of technical user testing i needed.
if it's possible, can you send me two files:
(1) the wav file that you linked above in the screenshot
(2) any wav file that does work in your Ableton Live 10... it could be anything. i just would like to compare the two on my machine
You can upload them to my dropbox:
https://www.dropbox.com/request/agxFc8AQ0JYOdlf121yE
And lastly, what OS are you using?

No problem, happy to help!
I uploaded a random sample I've used KSHMR_Cello_17_Melody_120_Dm.wav and the file from the screenshot to the Dropbox. My OS is OSX 10.11.6

hey @cozma, just found Citizen DJ today.
I've downloaded a few songs from there this morning and have imported them into Ableton Live 10.1.3 with no issues or distortion.
I'm on OS X 10.14.6

@cozma I have a feeling this might be because the wav format is 32-bit, can you try out this file that's 16-bit?
https://www.dropbox.com/s/fdtyf20pxzmepk5/A-better-America_2001642615_004_00-00-30.wav?dl=1
If that works, I should probably just export these at 16-bit since the source material is 16-bit (i.e. no quality gain for increasing bit depth).  Thanks again for helping troubleshoot this.

@cozma I have a feeling this might be because the wav format is 32-bit, can you try out this file that's 16-bit?
https://www.dropbox.com/s/fdtyf20pxzmepk5/A-better-America_2001642615_004_00-00-30.wav?dl=1
If that works, I should probably just export these at 16-bit since the source material is 16-bit (i.e. no quality gain for increasing bit depth). Thanks again for helping troubleshoot this.

Yes, this file works! Thanks for looking into it

that's great to hear!   I've updated the .wav files on the website, so hopefully things will work now.  Apologies for having to re-download everything


Add sidekick checklist

Overview
Adding a checklist for PR reviewers.

After a few edits (sorry for the notifications noise) this has been verified to appear properly on my fork.

Closing this PR while we explore other options for adding a checklist to PRs.


Not receiving mail if email address has uppercase characters

Doesn't work:

Send a mail to<EMAIL_ADDRESS>Check the inbox<EMAIL_ADDRESS>There's nothing.

Works:

Send a mail to<EMAIL_ADDRESS>Check the inbox<EMAIL_ADDRESS>Mail is there.
Check the inbox<EMAIL_ADDRESS>Mail is also there.

Any updates on this yet? Anyone currently working on it?

Any updates on this yet? Anyone currently working on it?

Hi @codehakase, I will be working on it soon :) sorry for the wait!

Hi @codehakase! The update is implemented :D


how to use it(openssl) replace boringssl in the chromium

I want to use openssl replace boringssl in the chromium.

There are probably many boringssl API's that this does not implement.  This project is adding the de-facto QUIC API's to OpenSSL.  Closing this.


Fix cfg macro use for SMS integration test.

Little typo when SMS was added.  Before this PR:
$ cargo test --features sqs
   Compiling rusoto_tests v0.25.0 (file:///Users/matthew/Documents/rusoto/integration_tests)
error[E0463]: can't find crate for `rusoto_sms`
 --> tests/sms.rs:4:1
  |
4 | extern crate rusoto_sms;
  | ^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate

Afterwards it works as expected. 😁

Oops... LGTM! 👍


Added schema verification while importing model

Summary:

This PR resolves #510 by adding external schema verification to check whether the imported model aligns with the schema
Description for the changelog:

It uses ajv for schema verification and the schema that is used here is https://github.com/OWASP/www-project-threat-dragon/blob/main/assets/schemas/owasp.threat-dragon.schema.json. As the provided schema was little outdated so I have  updated the schema a bit so that it aligns with the schema used in threat model v2.
Other info:

Closes #510

Hey @jgadsden! I've made all the necessary changes. However, the issue with isValidSchema validating the malformed JSON model is likely due to the 'strict' option being set to false. This prevents Ajv from strictly verifying data type mismatches. Enabling strict mode, however, results in an error:
vue-router.esm.js:2316 Error: strict mode: unknown keyword: "0"     at checkStrictMode (util.js:174:1)     at checkUnknownRules (util.js:32:1)     at alwaysValidSchema (util.js:19:1)     at properties.js:23:1     at Array.filter (<anonymous>)     at Object.code (properties.js:23:1)     at keywordCode (index.js:464:1)     at index.js:222:1     at CodeGen.code (index.js:439:1)     at CodeGen.block (index.js:568:1)
This prevents users from importing any models initially. To mitigate this, I set the 'strict' property to false, temporarily disabling type matching. Despite attempting to resolve the problem, I've been unsuccessful so far. Any assistance from your side would be appreciated. Based on my investigation, the issue seems to be with the schema, but I'm not entirely certain. Even if we don't arrive at a solution, we can still merge this PR and create a separate issue for it.

Hey @jgadsden! I have made all the required changes. It now works well for v2 models and restrict the malformed models like these to move ahead.
{   "version": "2.1.3",   "summarize": {     "titled": "New threat model",     "owners": "",     "description": 0,     "id": "bad ID"   },   "details": {     "contribute": [],     "diagramming": [],     "diagramTop": "zero",     "reviewer": -1,     "threatTop": 0   } }

Hey @jgadsden! I have made all the required changes. It now works well for v2 models and restrict the malformed models like these to move ahead. { "version": "2.1.3", "summarize": { "titled": "New threat model", "owners": "", "description": 0, "id": "bad ID" }, "details": { "contribute": [], "diagramming": [], "diagramTop": "zero", "reviewer": -1, "threatTop": 0 } }

Also note that I have put the strict option in ajv-SchemaVerification.js as false as it is still causing a problem and refraining user for the initial import.
`import Ajv from 'ajv';
import { schema } from '@/assets/threat-model-schema';
import { schema as schemaV2 } from<EMAIL_ADDRESS>const ajv = new Ajv({'allowUnionTypes' : true , "strict" : false});
const validate = ajv.compile(schema);
const validateV2 = ajv.compile(schemaV2);
export const isValidSchema = (jsonFile) => {
// use the latest schema, otherwise try the original V1 schema
let valid = validateV2(jsonFile);

if (!valid) {
    valid = validate(jsonFile);
    if (!valid) {
        console.error('Failed to validate', validate.errors);
        return false;
    }
}

console.debug('Schema validate success');
return true;

}
`

thanks for this @raghav1030 , I will merge this to main and if there are any further issues they can be fixed later


Access forbidden to examples URL

http://www.linuxdigest.org/misc/script_examples/DataTables-Hide-Empty-Columns/examples/
The above results in a 403 Forbidden for me :'(

For the benefit of others: if you add 'index.html' to the end of the URL it works: http://www.linuxdigest.org/misc/script_examples/DataTables-Hide-Empty-Columns/examples/index.html

This should be working now. Let me know if you have any other issues.

Yep, works for me now. Cheers


Query run twice

Please help, my query runs twice before I used mysql 8 and laravel 8 databases it was not a problem, but not with this version
My code:
$data = Sekolah::query();

return DataTables::of($data)->make();

Operating System : Windows 11 x64
PHP Version : 8.1.2
Laravel Version : 9
Laravel-Datatables Version : 10
Database : Postgre v14

today in production, xhr runs twice

if I use empty data from array it gets messy

finally I decided to downgrade to v9, and it went really well

Thanks for reporting, I haven't encountered the same issue since I upgraded to v10 but will check/fix this as soon as I can.

Thanks for reporting, I haven't encountered the same issue since I upgraded to v10 but will check/fix this as soon as I can.

Thanks sir Aryjay, try to use laravel debugbar, it shows multiple query.

@adeiming I think the 2 queries are expected since we need count 2x. First is for total count and 2nd is for filtered records count. On initial load, it is expected to have the same query.
XHR runs twice is another thing and I think is a javascript issue. Can't replicate this.

in laravel debugbar, the same query will be marked with a yellow background, like the image above, also in the previous version when using an empty array there was no error on the page number, unlike this version

Were you able to update to latest version available? Several patches added. Also, the change in behavior might be related to this PR https://github.com/yajra/laravel-datatables/pull/2778.
Can't replicate the null recordsFiltered, can you provide script on how to replicate it?

Were you able to update to latest version available? Several patches added. Also, the change in behavior might be related to this PR #2778.
Can't replicate the null recordsFiltered, can you provide script on how to replicate it?

like this:
return DataTables::of([])->make()

become:
{
  "draw": 1,
  "recordsTotal": 0,
  "recordsFiltered": null,
  "data": [],
  "input": {
    "draw": "1",
    "columns": [
      {
        "data": "uuid",
        "name": null,
        "searchable": "false",
        "orderable": "false",
        "search": {
          "value": null,
          "regex": "false"
        }
      },
      {
        "data": "tanggal",
        "name": "pendaftaran.updated_at",
        "searchable": "true",
        "orderable": "true",
        "search": {
          "value": null,
          "regex": "false"
        }
      },
      {
        "data": "nisn",
        "name": "p.nisn",
        "searchable": "true",
        "orderable": "true",
        "search": {
          "value": null,
          "regex": "false"
        }
      },
      {
        "data": "nama_lengkap",
        "name": "p.nama_lengkap",
        "searchable": "true",
        "orderable": "true",
        "search": {
          "value": null,
          "regex": "false"
        }
      },
      {
        "data": "jk",
        "name": "p.jk",
        "searchable": "true",
        "orderable": "true",
        "search": {
          "value": null,
          "regex": "false"
        }
      },
      {
        "data": "asal_sekolah",
        "name": "rs.name",
        "searchable": "true",
        "orderable": "true",
        "search": {
          "value": null,
          "regex": "false"
        }
      },
      {
        "data": "aksi",
        "name": null,
        "searchable": "false",
        "orderable": "false",
        "search": {
          "value": null,
          "regex": "false"
        }
      }
    ],
    "order": [
      {
        "column": "1",
        "dir": "asc"
      }
    ],
    "start": "0",
    "length": "10",
    "search": {
      "value": null,
      "regex": "false"
    },
    "_": "1656035512995"
  }
}

if I compare with version 9, recordsFiltered is not NULL, it's 0

as you can see, this is now 3 queries, the same 2 with a yellow background.
I hope this helps

I already updated the version when running this

Yes 2 queries for count then another one for the actual dataset, expected behavior.
I think the issue here is on null recordsFiltered only. Will review this, thanks!


Amazon EC2 node driver clusters are stuck in provisioning

Rancher Server Setup

Rancher version: 2.6-head commit id: 8898bf8
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Info:
Cluster Type (RKE1, RKE2, k3s, EKS, etc): RKE1
Node Setup: 3 nodes all roles
Version: 1.21.4

Information about the Cluster

Kubernetes version: v1.21.3-rc6+rke2r2
Cluster Type (Local/Downstream): Downstream RKE2 EC2

Describe the bug
Amazon EC2 node driver clusters are stuck in provisioning
To Reproduce

Deployed EC2 rke2 driver clusters with 1 node all roles.
Cluster is stuck in Provisioning

Note:

But i was able to deploy a couple of clusters that came up Active in same Rancher setup.
VPC/Subnet in the node pool was being changed
API request did have the VPC/SG sent by the UI
No other error on the cluster or the machine pool
Nothing obvious from journalctl logs

Did you compare the VPC/Subnets to ensure the security groups had the same ports open and available?
Is it a specifc VPC/subnet?

@sowmyav27 We should really only be testing using the default rancher-machine security group that Rancher creates as well as testing if you come from an upgraded setup that had an old rancher-machine and you re-use it, it still works.

I am not able to reproduce this. I tried using different VPCs and subnets, but was always able to successfully provision a cluster in EC2.

On 2.6-head commit id: b8a44fa
Fresh Install use case.
I am not able to reproduce this issue.


fix(esl-utils): add IE compatibility for window rect obtaining

In bounds of this PR:

added Internet Explorer compatibility for window rect obtaining

I have read the CLA Document and I hereby sign the CLA

:tada: This PR is included in version 4.0.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Kubebench operator ks package

We need to create ksonnet package for kubebench operator.

/assign

duplicate of https://github.com/kubeflow/kubeflow/issues/2110


Feature/rename for release

Hi @vatanaksoytezer!
Could I get you to take a look at this PR? It renames the packages as requested in our first rosdistro PR (https://github.com/ros/rosdistro/pull/35488).
This had some follow-on changes:

Update the README to reflect new package names, reduce duplication, and bring it up to date for release.
Add migration rules that handle the renaming.

However, I'm not sure what is the standard way to test migration rules in released message packages.
Right now, I have a script that generates a bagfile with old versions of all of the messages. I used its output to manually test the migration. I went ahead and committed it, but wasn't sure whether it really belonged in the repo.
I think it would be pretty cool if we were able to set it up such that CI checks successful migration of messages on any future pull request. Is this something that's easy to set up?

@CaptKrasno -- If you have existing bag files that you care about, could I get you to test the bag migration rules on this PR?

In the absence of any comments, I plan to merge this branch on Thursday, April 20.
Speak now or forever hold your peace ;-)  @rolker @CaptKrasno
I'll also bump the version to 2.0


Release 67.0.0

See: https://github.com/alphagov/gds-api-adapters/pull/995

Just curious - how come we went from v63 to v67 instead of v64?

Arrghh! 🤦
I incremented the minor version (6) to end up with 7. Hmmm how best to resolve this.

It turns out that I can't count either 🤦


Connectivity demo crashes with method not found TJDWNetworkCallback on D11.3

I've discovered a crash in the connectivity feature, which raises an EMethodNotFound exception for TJDWNetworkCallback class.
Seems to be raising this on all my test devices (Samsung, OnePlus, Oppo).
This exception is being raised in DW.Connectivity.Android.pas in TNetworkCallbackDelegate.Create (when initialising the JDWNetworkCallback instance). Commenting out this call (or wrapping with exception handling), and the app runs ok.
dw-kastri-base-2.0.0.jar is in the Libraries, and I'm using Delphi 11.3.
Any ideas?

It looks like you've updated the header to .init() in that Java class to include a new parameter but didn't update/rebuild the dw-kastri-base-2.0.0 jar so it's expecting the old signature still.

Updated jar has been pushed


NCBI FCS tutorial first commit

Add NCBI FCS Tutorial

Add short tutorial, workflow, images
Need help with Warning box embedded in "Hands-On Interpreting FCS Output"
Need help with embedded citation Astashya2024 . Does author format need to be changed?

This is shaping up to be a fantastic tutorial, really looking forward to this!!

I have

made some small whitespace changes
cherry-picked in the TRS snippet improvements and made the associated cleanups
improved some alt-text (it wasn't descriptive enough for those using screen readers, for ADA compliance.)

but I think this is now ready to ship!
There are some other features we could take advantage of in the future (i.e. are on the main branch and would require rebasing), e.g. the new workflow preview to avoid the need for a screenshot but, otherwise I think it looks good as-is.

Thanks for all of the patience making our requested changes @tvedtees, they have made for a more FAIR and accessible tutorial!

@hexylena this looks great overall! I will be going over this again to look for any small enhancements to add.

There are some other features we could take advantage of in the future (i.e. are on the main branch and would require rebasing), e.g. the new workflow preview to avoid the need for a screenshot but, otherwise I think it looks good as-is.

I clicked on the link under the new snippet
{% snippet faqs/galaxy/workflows_run_trs.md path="topics/sequence-analysis/tutorials/ncbi-fcs/workflows/NCBI-Foreign-Contamination_Screen.ga" title="NCBI Foreign Contamination Screen Workflow" %}
(i.e. Click to Launch NCBI Foreign Contamination Screen Workflow)
selected the galaxy server use.galaxy.org, which then redirected to the galaxy instance but had a large error box. Is this expected?

could you share the error box? i see one on EU for a missing tool, but not on .org

ah interesting, that was fixed in #4902, not sure, maybe you have a cached copy of the site or so? try force refreshing and the link should work (we've added linting in 4902 to prevent this specific error in the future as well)

Yes it does work now. Excellent.


swift: add @frozen annotation to filter statuses

This suppresses the following warning when switching over filter return values:

Switch covers known cases, but 'FilterHeaderStatus' may have additional unknown values

Note that while we are not guaranteeing ABI stability, we will use semantic versioning going forward.
Signed-off-by: Michael Rebello<EMAIL_ADDRESS>

Thanks @keith, updated the description


update protobuf to v3.7.1

similar to https://github.com/golang/protobuf/pull/757; no significant changes when regenerating

Wah; what happened here? Target branch changed?


Configuration Differences between Standard and Larger Runners

Description
I've recently migrated some workflows from the standard runner to a larger runner. The same docker container is used on the larger runner, and the webfactory/ssh-agent action sets up Github deploy keys for our projects. The container is configured as a non-root user.
On the larger runner, we're seeing an EACCES: permission denied error when the ssh-agent action tries to copy keys. I've been able to get the workflow to pass on the larger runner by adding options: --user root to the container config, but we'd like to continue using a non-root user.
The only difference I can find in the two action reports is that the larger runners are using an older runner image (20221204.2) compared to the standard runner (20230109.1). Maybe there are other runner specific settings that we don't have visibility into.
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Standard Runner at version: 20230109.1
Larger Runner at Version: 20221204.2
Is it regression?
Version 20230109.1 works on standard runners, but 20221204.2 does not work on larger runners
Expected behavior
Build will succeed on both standard and larger runners.
Actual behavior
Standard runners work as expected. Larger runners fail with permissions issues trying to add files to the users home directory.
Repro steps
The repo and workflows are in private repos, but I would expect that a job with the following steps can reproduce the issue:
jobs:
  permissions_test:
    runs-on: ubuntu-20.04
    container:
      image: <some docker image based on ubuntu:20.04>
    steps:
      - uses<EMAIL_ADDRESS>        with:
          ssh-private-key: |
            ${{ secrets.SOME_REPO_DEPLOY_KEY }}

Hey @swyphcosmo! We'll take a look asap.

@erik-bershel Has there been any progress made on this issue? Thanks in advance.

@swyphcosmo I think the problem is Larger Runner treats ssh sockets differently, i.e. it is not direct docker's fault.
@maxim-lobanov, could you please take a look and advise?

Hi @swyphcosmo ,
Could you please share the full error message which you see? Does it contain any text after EACCES: permission denied (usually some path is displayed after this text). And also could you please share the logs of webagent/ssh-agent step if possible.
I was able to reproduce only this error. Is it the same error that you see on your side?

Hi @maxim-lobanov,
I do see a similar error:

In our Dockerfile:
FROM "ubuntu:20.04"

# Add a user with id 1001 to match permissions with the github env.
RUN useradd -u 1001 -M github && \
    mkdir -p /github/home && \
    chown -R github:github /github && \
    ln -s /github/home /home/github

# Run commands as the github user by default.
USER 1001

Let me know if you need any more information. Thanks for your help.

@swyphcosmo , thank you for sharing this example, it was super useful and I think I now understand what is going on.
Root cause
On both Standard Runners and Larger Runners, we run agent on behalf of runner user. But this user has different UIDs.

1001 on Standard Runner:$ cat /etc/passwd
...
runneradmin:x:1000:1000:Ubuntu:/home/runneradmin:/bin/bash
runner:x:1001:122:,,,:/home/runner:/bin/bash

And 1000 on Larger Runner:$ cat /etc/passwd
...
runner:x:1000:1000:Ubuntu:/home/runner:/bin/bash

runner user has different UID on Standard Runners and Larger Runners because we use a bit different and simpler infrastructure (deployment process) for Larger Runners so we don't add intermediate user runneradmin which takes 1000 UID on Standard Runners.
Why UID of "runner" user on host machine matters
When agent runs container job, it mounts a lot of folders from host machine to docker container (from Initialize containers step logs):
/usr/bin/docker create --name 8bd1167c200a4e6bbeb1ff05a0e0d609_ghcriobbqbeetstestdockerimage_002f2e
--label 49859c --workdir /__w/mlobanov-test-repo/mlobanov-test-repo --network
github_network_0b1fa05952164636be4acdf6cdb3e23e -e "HOME=/github/home" -e GITHUB_ACTIONS=true
-e CI=true
-v "/var/run/docker.sock":"/var/run/docker.sock"
-v "/home/runner/work":"/__w"
-v "/home/runner/runners/2.301.1/externals":"/__e":ro
-v "/home/runner/work/_temp":"/__w/_temp"
-v "/home/runner/work/_actions":"/__w/_actions"
-v "/opt/hostedtoolcache":"/__t"
-v "/home/runner/work/_temp/_github_home":"/github/home"
-v "/home/runner/work/_temp/_github_workflow":"/github/workflow"
--entrypoint "tail" ghcr.io/bbq-beets/test-docker-image "-f" "/dev/null"

Agent doesn't set any special permissions for these mounted folders and they are owned by runner user on host machine. So when UID of user on host machine is equal to UID of user in docker container, permissions for mounted folders are inherited from host user and user in docker container has correct permissions on mounted folders.
I have performed small experiment:

Build super simple docker imageFROM "ubuntu:20.04"
RUN useradd github
USER github

Run the following workflow:runs-on: ubuntu-20.04 # standard runner
container:
      image: <my_test_image>
steps:
 - run: |
      whoami
      echo "----"
      ls -la $GITHUB_ENV
      echo "----"
      ls -la $HOME
      echo "----"
      cat /etc/passwd

Results$ whoami
github

$ ls -la $GITHUB_ENV
-rw-r--r-- 1 1001 122 0 Feb  1 11:41 /__w/_temp/_runner_file_commands/set_env_27af1008-076d-41ad-8cf9-a0eb8e02f3e4

$ ls -la $HOME
total 8
drwxr-xr-x 2 1001  122 4096 Feb  1 [11](https://github.com/bbq-beets/mlobanov-test-repo/actions/runs/4063967778/jobs/6996824762#step:5:12):41 .
drwxr-xr-x 4 root root 4096 Feb  1 11:41 ..

$ cat /etc/passwd
...
github:x:1000:1000::/home/github:/bin/sh

As you can see from etc/passwd, we don't have user with UID 1001 in docker container at all but all mounted folders are owned by this user. This user exists only on host machine.
Workarounds

You can rebuild docker image to user UID 1000 for github user instead of 1001. I have tested that it will well on Larger Runners. And it should unblock you if you use only Larger Runners.
If you use both Standard Runners and Larger Runners with the same image in parallel, I guess this workaround won't work for you well.
Invoke chmod -R 777 on the a couple of folders /__w, /__t, /github. Again, it is not ideal workaround too.

Longer term solutions
As I mentioned earlier, runner user has different UIDs on Standard Runners and Larger Runners because they have a bit different deployment process and we have to create intermediate user runneradmin during deployment on Standard Runners. So on standard runners runneradmin has UID 1000 and runner has UID 1001. On Larger Runners, we don't have runneradmin and runner has UID 1000. We are definitely trying to make Larger Runners as consistent as possible with Standard Runners to simplify users' migration.
We can't get rid of runneradmin for Standard Runners. And we can't force runner to be 1001 on Larger Runners without adding intermediate runneradmin.
So one possible solution could be adding runneradmin on Larger Runners too so runner will have UID 1001 consistently with Standard Runners. Honestly, I don't like this option because it looks more as workaround on our side instead of real solution 🤔 On standard runners, we need this intermediate user but on Larger Runners we don't need it and we shouldn't create it without real necessity.
In my understanding, this issue should be solved on agent side and agent should ensure proper permissions for all folders which it mounts to docker container and it shouldn't rely on equality of user UIDs because I can imagine that some users with self-hosted runners can have any random UID on host machine and they will have to deal with the same problem.
I have created an issue for agent team. Let's take a look what they will say: https://github.com/actions/runner/issues/2411

Thanks @maxim-lobanov!
@swyphcosmo please follow https://github.com/actions/runner/issues/2411 then as our hands are tied here due to the problem being out of our scope.


webgl

It'd be awesome to convert this to WebGL so that it's buttery smooth even on older phones if they have a GPU.
I tested on my Lumia 1020 Windows Phone, and the fps was low. I mean, it's Windows, but still. IE11 supports WebGL (most of it), so the globe would probably be smooth on IE11 mobile if it were in WebGL. Many of the Three.js WebGL demos run buttery smooth on my Windows Phone.
Microsoft Edge is about to land on my phone in a day or two, which will have even better WebGL support!

A WebGL version of this project is interesting and would certainly be cool, and it's something I've thought about toying with, but it would be a separate project.


Duplicates entries on Planetscale

There are duplicate entries appearing on the SQL database. This is not good. There are useless writes happening.

This seems to be a synchronization error. The code is working, but the context in which its working makes it create a failure.

A refresh would just require just pulling the current Reddit posts, comparing it to the SQL database from the table's beginning then, removing everything past the similar the post which is the last similarity.

A possible cause for this issue is also in the ID system. Before data is entered into the Planetscale Database, an ID is assigned to it. Once there the remote database is out of sync with current Reddit posts, making new IDs exacerbates the ordering and duplicate issue.


process.env is prefered over import.meta.env

Environment
node 20.11
std-env 3.7
Reproduction
not really relevant
Describe the bug
So I'm not sure if I'd call this a bug per-se, maybe more of an observation to open up a discussion how we could solve this.
Astro is a bit (if you ask me) dumb in the way that they have a process.env on the server but they don't populate it with stuff from your env file. That stuff goes on import.meta.env. This means that the following logs undefined:
import { process } from "std-env";
console.log(process.env.SOME_ENV_FROM_ENVFILE);

This is cause (like I said), process does exists, so std-env chooses it as the env object: https://github.com/unjs/std-env/blob/7528b1324ab48dea93c0739b0b046e0d5607fcf5/src/env.ts#L5-L10
Any ideas how to solve this in a nice way? I think this is just a stupid behavior from Astro but any workaround we can do to support this would be great. We recently moved to std-env in uploadthing to have a single source of truth for accessing environment variables but then I stumbled on this edge-case...
Additional context
No response
Logs
process.env {
  MANPATH: '/opt/homebrew/share/man::',
  COREPACK_ROOT: '/Users/julius/Library/Application Support/fnm/node-versions/v20.11.0/installation/lib/node_modules/corepack',
  BUNCH_OF_STUFF: "THAT I REMOVED",
  NODE_ENV: 'development'
}
import.meta.env {
  BASE_URL: '/',
  MODE: 'development',
  DEV: true,
  PROD: false,
  SSR: true,
  SITE: undefined,
  ASSETS_PREFIX: undefined,
  UPLOADTHING_SECRET: 'sk_live_xxxxxx' // <-- this is coming from .env.local
}

cc @pi0 any thoughts?

Opened one at astro too https://github.com/withastro/astro/issues/9827

Thanks for explaining the issue! Well this is interesting. I will followup your upstream issue.
It is i guess more of a question that for std-env we shall prefer import.meta.env over process.env or not. From other discussions and also considering the breaking changes risk it can bring to the ecosystem (at least UnJs/Nitro are safe. We have both and they are the same) it is probably not something we should do and strange enough about Vite side..
Also as mentioned in astro's discussion, if Astro (or even Vite) needs a special logic, i am open to it.
Do you think we should still track it here for std-env too?

What do you think about merging them?
So like Object.assign({}, process.env, import.meta.env) (with safeguards since one might not exist?

We can...But it also costs. Also makes another issue. If there is a later change to process.env or import.meta.env objects, we do lose them (imagine in runtime a code setting process.env.FOOBAR -- I know many places do this)
One other thing we can do is that inside proxy, we iterate over sources and check each if exists and key exists in it. I think it is an acceptable compromise and middle-ground to fix the issue.


[Ansible] Deployment - Include File-mgmt

[Ansible] Deployment - Include File-mgmt

Observed in devops board.


Use supported flake8 version for python2.6

Thanks. Can you make travis pass? I think You need something like
[testenv:py26]
deps =
    nose
    flake8==2.6.2
commands = ./run-tests.sh

in tox.ini

Going to close this since https://github.com/tebeka/fastavro/pull/110 was merged.


Can this software act as a transmitter?

Good day! Thanks for your efforts! I need to emulate a receiver on Linux and connect via a UART converter to the flight controller. I want to transmit control actions via SBUS, which will be synthesized on Linux. Am I correct in understanding that your software can act as both a receiver and a transmitter?

Yes, I recommend the passthrough example https://github.com/Carbon225/raspberry-sbus/blob/master/examples/passthrough.cpp

Thanks a lot!


deadlock situations may occur with v0.40.0 - regression

Describe the bug
Jan 23 21:13:56 tapx go-dnscollector[43716]: INFO: 2024/01/23 21:13:56.462172 [fileA] logger=file - execute compress postrotate command: /var/tap/dnstap-1706040822558956943.log.gz
Jan 23 21:14:04 tapx go-dnscollector[43716]: ERROR: 2024/01/23 21:14:04.747554 [tapA] collector=powerdns - recv buffer is full, 136058 packet(s) dropped
Jan 23 21:14:14 tapx go-dnscollector[43716]: ERROR: 2024/01/23 21:14:14.749079 [tapA] collector=powerdns - recv buffer is full, 164877 packet(s) dropped
Jan 23 21:14:24 tapx go-dnscollector[43716]: ERROR: 2024/01/23 21:14:24.749696 [tapA] collector=powerdns - recv buffer is full, 158886 packet(s) dropped

Jan 24 10:22:54 tapx go-dnscollector[54904]: INFO: 2024/01/24 10:22:54.432103 [fileA] transformer=reducer#0 - enabled
global:
  trace:
    verbose: true

multiplexer:
  collectors:
    - name: tapIN
      powerdns:
        listen-ip: <IP_ADDRESS>
        listen-port: 6000
      transforms:
        normalize:
          qname-lowercase: true
        latency:
          measure-latency: true

  loggers:
    - name: fileA
      logfile:
        file-path:  "/var/tap/dnstap.log"
        max-size: 250
        max-files: 10
        mode: text
        compress: true
        compress-postcommand: "/var/tap/postrotate.sh"
        text-format: "localtime identity operation queryip family protocol qname qtype rcode latency reducer-occurences"
      transforms:
        reducer:
          repetitive-traffic-detector: true
          watch-interval: 5

    - name: prom
      prometheus:
        listen-ip: <IP_ADDRESS>
        listen-port: 8080
        top-n: 10
      transforms:
        filtering:
          log-queries: false

  routes:
    - from: [ tapIN  ]
      to: [ fileA, prom ]

regression related to https://github.com/dmachard/go-dnscollector/issues/521


Rough Start of Level 1

@vitormaduro Since I am doing the blocking, let me know if I should close this one or let it be.


Accept payments page Implementaion

Completed all tables and codeBlocks respectively
Created a code block to render dynamically
In completion of #17

BUG

The text color for response code does not change even after force i.e !color...
The code block should have a bg-neu-700 prop but it doesn't affect the change even when specified
image desc

@asapconet  please resolve conflict

@Frontend-io can you please help me check the versel error msg so I can debug from my end?
ThAnks.


Compile-time constant replacement (like DefinePlugin)

Command
build
Description
In our app, we use Sentry. It ships debug code by default, with instructions for tree-shaking in prod.
Such tree-shaking is based on replacing a global constant at compile time. https://docs.sentry.io/platforms/javascript/configuration/tree-shaking/#tree-shaking-with-webpack
e.g
new webpack.DefinePlugin({
      __SENTRY_DEBUG__: false,
      __SENTRY_TRACING__: false,
      __RRWEB_EXCLUDE_IFRAME__: true,
      __RRWEB_EXCLUDE_SHADOW_DOM__: true,
      __SENTRY_EXCLUDE_REPLAY_WORKER__: true,
    }),

Angular doesn't expose the underlying webpack configuration for extending (for good reasons). Unfortunately for us, it means the prod bundles include debug code, which we cannot tree-shake at the compile time
Describe the solution you'd like
Ability to define compile-time constants replacements, abstracted away from the underlying build tool (whether webpack or esbuild).
Describe alternatives you've considered
No response

This is already possible with the application builder, which includes a define option. For more details, refer to this PR: https://github.com/angular/angular-cli/pull/27047.

I'm getting
Error: Schema validation failed with the following errors:
  Data path "" must NOT have additional properties(define).

Is there documentation on how to use it correctly?

Against which version are you testing this ? Care to share the angular.json you tried ?

We use the "@angular-devkit/build-angular:browser" builder.

As Alan mentionned, this is only for the application builder.

Is there a plan to port this functionality to the webpack-based builder?

No, generally new features are not added to the webpack based builders.

Thanks!


Add support new files

Summary
Add support for the new files list method in the client
Details and comments

@korgan00 can you put data-folder branch as base? In main you are not going to have the required end-points to pass the tests

@korgan00 I just saw too that your branch is based on main. You will need to apply a rebase if you can over data-folder. I can take a look to it Monday if you want.


formatter

i want to use oxc to format my code but it seems formatter was removed and prettier is not supported yet? https://github.com/oxc-project/oxc/issues/1941

it seems wip but is there any way to use it like npx oxc@beta format? https://github.com/oxc-project/oxc/tree/main/crates/oxc_prettier


Issue #1073: Allow arbitrary data in product detail meta snippet

Closes #1073.

As you can see the functionality is very much duplicated but I was not able to find a pretty way of extracting it.


[WbKitBrowser] Updating WbKitBrowser plugin to version 2.42 of WPEWebKit

consoleMessageSentCallback() has to be marked as DEPRECATED, since webkit_console_message_get_text() has been deprecated in version 2.40 of WebKit in this PR: https://github.com/WebKit/WebKit/pull/6784. It seems like at the moment there is no other way to get the console messages: https://bugs.webkit.org/show_bug.cgi?id=247791#c4.

@VeithMetro , were you able to test on RPI these changes? and seeing QuotaExceededError in case of exceeded?

@modeveci I tested it after the changes on RPI, I changed indexeddbenabled to true in the config, and didn't see anything worrying in the logs. But I haven't seen QuotaExceededError either - what can I do to exceed the quota in order to check if I get this error?

I thin you can check these examples, and play with the values you provided with config files:
https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API#examples

@modeveci I tested indexeddb with the examples that you suggested:

https://mdn.github.io/dom-examples/to-do-notifications/
https://mdn.github.io/dom-examples/indexeddb-examples/idbcursor/
https://mdn.github.io/dom-examples/indexeddb-examples/idbindex/
https://mdn.github.io/dom-examples/indexeddb-examples/idbkeyrange/

and also played with the settings. It looks like everything works on my end - if indexeddb is disabled in the config, then nothing shows in these examples, and you can't add anything to the database, as expected. Then if you enable indexeddb in the config, you can see all database items properly displayed, and it is also possible to create and add new ones. When I set the quota too low, then the database was no longer displayed (if it was already too big), or it was not possible to add anything new to it.


test-already-present: test that package is already present

what

Test changes for myself over in #61

why

Looks okay, just want to be sure before cutting a release.

references
#62 #61

^ realized there were no changes under src/ so no published development orb :P

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:ea88c140558b2e47480e5a700086ccb96c1a3e60

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:42fae687fbac8dc88c268ea26b44b6fb61fe8cbf

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:9a59707be79279c52dfaba9d9c8f4809c12bf707

Huh. Looks like something may be off here?
https://app.circleci.com/pipelines/github/bjd2385/dynamic-continuation-orb/447/workflows/4497141e-8be9-4298-be01-fd7cb33cb59d/jobs/1301?invite=true#step-102-7

Also dunno why the scripts/-workflow is running.

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:69c085c7b3a281731db9b9a40280a82b1c0115bb

New logic appears to work as intended. Curious why it's running the scripts/-workflow, however.

# Ignore everything outside of the target directory users can add and remove files from here.
.*
!scripts/
circleci@cc5e43f65df0:~/project$ git diff-tree --no-commit-id --name-only -r HEAD "master" . | awk NF | wildmatch -c ".circleci/scripts.ignore"
src/jobs/continue.yml```

circleci@cc5e43f65df0:~/project$ git diff-tree --no-commit-id --name-only -r HEAD "master" . | awk NF | wildmatch -c ".circleci/scripts.ignore"
circleci@cc5e43f65df0:~/project$ cat .circleci/scripts.ignore
# Ignore everything outside of the target directory users can add and remove files from here.
*
.*
!scripts/

Looks like I'm not ignoring everything that needs to be ignored by default.

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:40067090dce5e111960bacd5fa8dd089151ac2da

Lol wait, now all i see is the scripts-workflow.

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:61578adf60c55af1ff47f38e82d49448b3f6b5af

^ actually, this should be running scripts now, .circleci/scripts.yml has changed.

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:b6f15449db04e2a0cd38a4f4ccb4951566f9497c

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:b05df008e687412850ec506e955177d2c5dec656

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:1c88ebb7d0693e171e6baa9738bb1e5b002872e9

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:75c1c0eec095f96d64cc3399ebda088b16464309


Restore previous static server behaviour

This is my intent (choose one)

[ ] I want to report a bug
[ ] I want to request a feature or change
[X] I want to provide or change a feature

The problem
It used to be possible to start a production mode Express server without a Hops built middleware. This is now impossible (https://github.com/xing/hops/blob/master/packages/express/app.js#L33).
Proposed solution
Move the check for the existence of the middleware to hops-local-cli and only bail if HOPS_MODE is not static and the middleware is missing.
Paging @matthias-reis, @ZauberNerd

Resolved by @matthias-reis in https://github.com/xing/hops/commit/f8855dfd48a181456ed766f9bf0f7c073754c6f6


fix: android artifacts in a release package

Summary
Android artefacts in a release package are missing, as a result, users are not able to run 0.64.0-rc.0 on Android. Locally, everything works.
After several hours of testing, we found out that running ./gradlew ReactAndroid:installArchives will "sometimes" fix it and I have managed to verify both locally and on the CI, that running Gradle without cache is broken, but when running Gradle once again (right after corrupted build completed, but there is cache already) fixes the issue.
Seems to be Gradle related.
In this PR, I am adding a validation to publish-npm.js script to make sure this kind of errors never happen again in the future. We also attempt to rebuild Android once, hoping that it will pass the validation.
Here's the truncated output of the script:
BUILD SUCCESSFUL in 8m 9s
41 actionable tasks: 41 executed
Artifacts are corrupted. Rebuilding with Gradle once again to fix it

BUILD SUCCESSFUL in 6s
43 actionable tasks: 12 executed, 31 up-to-date
Artifacts validated, continuing.

Test Plan
Run the newly added code via node and you should see the script re-running installArchives and creating correct artifact. You can use this gist contents to just paste into publish-npm.js.
Remember to update the version in package.json to 0.64.0-rc.0 and run:
rm -rf android
rm -rf .gradle
rm -rf ReactAndroid/build

before doing anything, to make sure you start fresh.

Shipped 0.64.0-rc.1 with that script included, and everything works. Here's the output! https://app.circleci.com/pipelines/github/facebook/react-native/7266/workflows/58b22daf-d6db-41e2-a4bd-51ffad4e650c/jobs/178795
android/com/facebook/react/react-native/0.64.0-rc.1/react-native-0.64.0-rc.1.aar is missing contents. Rebuilding with Gradle again in an effort to try to fix it.

Ready to be merged.

Thanks for sending the PR. I'm closing this as the logic is completely rewritten now.


Self host dotnet.exe

dotnet.exe should be able to compile itself, and so be a .NET Core app.

BTW, we should keep it as a .NET Framework project too. At this point it's easier to develop and debug with VS support. Later on (when we have solid support for our console apps), we can stop building it as a .NET Framework app.

This is done


Bot Channels Registration Issue

I've been having issues getting OAuth sign-in to work with my bot, so I tried starting from scratch with the Bot Authentication with MS Graph tutorial (the dotnet core one). After cloning the sample repo, I began following these directions, but got stuck on the creation of a Bot Channels Registration resource in my Azure portal. I created one in the portal, but there was no Application Settings blade under the App Service Settings tab, and I thus have no way to access the client secret that I just created.

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

ID: a9a43e68-83a3-1adc-0c55-e277ddb98c6b
Version Independent ID: 5c46848d-bc20-480e-4571-00a283d930a2
Content: Add authentication to your bot via Azure Bot Service - Bot Service
Content Source: articles/v4sdk/bot-builder-authentication.md
Service: bot-service
Sub-service: abs
GitHub Login: @JonathanFingold
Microsoft Alias: v-jofing

After doing a little more digging, I discovered that a Bot Channels Registration is only necessary if the Bot is hosted outside of Azure. If it is not, then this resource is not required. However, the way that it is described makes it seem that you have to create a new Bot Channels Registration, even if your Bot is in Azure.
The documentation should be changed to address this discrepancy, with something like:
Create your bot resource on Azure
Create a Bot Channels Registration using the Azure Portal.
Note: This step is unnecessary if the Bot is hosted in Azure.
Record your bot's app ID and password. To gather this information, see Manage a bot.

Fixed issue as requesetd.


Assignment 1, Sprint 3

Statistical Tests and Experiments

Apply the t-test to real data

Load and clean the data (or determine the best method to drop observations when running tests)

Consider using the expected values of 1 and 0 for boolean columns. It would make the means you calculate later easier to interpret.
What other options are there for filling in NaN's besides dropping them? There are a large number of NaN's in some columns, how will this effect the t-tests?

Using hypothesis testing, find an issue that democrats support more than republicans with p < 0.01

Practice explaining the result. What's going on here? What does this result mean?

Using hypothesis testing, find an issue that republicans support more than democrats with p < 0.01

As above.

Using hypothesis testing, find an issue where the difference between republicans and democrats has p > 0.1 (i.e. there may not be much of a difference)

As above.

Nice work, MIsqual

Build a confidence interval
Confidence Intervals:

Generate and numerically represent a confidence interval

✅ Well done.

Graphically (with a plot) represent the confidence interval

✅ See if you can make the scale different for more effective visualization

Interpret the confidence interval - what does it tell you about the data and its distribution?

✅ Great mathematical 'explanation', putting it into words is important, too.

Chi-squared tests:

Take a dataset that we have used in the past in class that has categorical variables. Pick two of those categorical variables and run a chi-squared tests on that data

By hand using Numpy

✅ Nice work creating the contingency table and doing the calculations.

In a single line using Scipy

✅ Checks all the way down.

Excellent job, Misqual


Fix indentation problem in label commentor workflow file

This PR fixes #3549
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3552 (8ece66a) into master (420482e) will decrease coverage by 7.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3552      +/-   ##
==========================================
- Coverage   17.24%   10.18%   -7.07%
==========================================
  Files          37       37
  Lines        3299     3299
==========================================
- Hits          569      336     -233
- Misses       2585     2896     +311
+ Partials      145       67      -78

Flag
Coverage Δ

gointegrationtests
?

unittests
10.18% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/start.go
1.20% <0.00%> (-52.21%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
0.90% <0.00%> (-39.10%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.48% <0.00%> (-22.23%)
:arrow_down:

Continue to review full report at Codecov.

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


Update README.md

● trojan.service - trojan                                                                 Loaded: loaded (/etc/systemd/system/trojan.service; enabled; vendor preset: enabled)   Active: failed (Result: exit-code) since Wed 2021-04-21 18:27:56 UTC; 874ms ago          Docs: https://trojan-gfw.github.io/trojan/config https://trojan-gfw.github.io/trojan/                                          Process: 4043 ExecStart=/usr/local/bin/trojan /usr/local/etc/trojan/config.json (code Main PID: 4043 (code=exited, status=1/FAILURE)                                                                                Apr 21 18:27:55 Tt systemd[1]: trojan.service: Main process exited, code=exited, statusApr 21 18:27:55 Tt systemd[1]: trojan.service: Failed with result 'exit-code'.         Apr 21 18:27:56 Tt systemd[1]: trojan.service: Service hold-off time over, scheduling rApr 21 18:27:56 Tt systemd[1]: trojan.service: Scheduled restart job, restart counter iApr 21 18:27:56 Tt systemd[1]: Stopped trojan.                                         Apr 21 18:27:56 Tt systemd[1]: trojan.service: Start request repeated too quickly.     Apr 21 18:27:56 Tt systemd[1]: trojan.service: Failed with result 'exit-code'.         Apr 21 18:27:56 Tt systemd[1]: Failed to start trojan.                                 lines 1-16/16 (END)

Have error


delay loading of EventSource and WebSocket

Delay the loading of EventSource and WebSocket until they are used. This allows kvlt to be used on browsers that don't support them as long as the features are not actually used.

Related to #20 and #25.

@loomis: Thanks!
Because the single arg constructor calls are the only two times those defines are used, maybe this might be cleaner than the let?
(def eventsource (delay (js/require "eventsource")))

(defn event-source [url]
  (if (exists? js/EventSource)
    (js/EventSource. url)
    (try
     (@eventsource. url)
     (catch js/Error e
       ...))))

at least with recent clojurescript builds, this works:
cljs.user> (def x (delay js/Object))
#'cljs.user/x
cljs.user> (@x.)
#js {}

but if it doesn't, generally, then confining the local binding to that function might be cleaner.
If that's a pain for you, I can merge this into a branch and take care of it.

@moea No problem.  I'll refactor the PR and retest.

@loomis This looks good to me, I'll merge and push an updated 0.2.0-SNAPSHOT after updating the promesa dep.

@moea Thanks for the feedback.  I've refactored the PR.  This is working for me and the standard tests pass now.  You'll notice that the only change between the last two commits was switching from:
(@websocket-node. url)

which fails the unit test to
(let [ws @websocket-node]
  (ws. url)

which passes.  I don't pretend to understand why the first works fine from the repl, but fails when compiled.

0.1.5-SNAPSHOT, rather, as there are no breaking changes in this branch.  Just released to clojars.


Log in Portal

a React UI for an inventory management system with a login page and dashboard, intended to connect with a Business Central (BC) backend:
Project Setup:
Create a new React project using Create React App or a similar tool.
Set up the basic project structure with components, styles, and necessary dependencies.
Login Page:
Design a simple login form with fields for username and password.
Include error handling for invalid inputs.
Implement state management to store user input.
Create a function to handle form submission.
Dashboard:
Design a layout to display user information and BC data.
Include placeholders for various data points or widgets.
Plan for components to display different types of BC data (e.g., sales figures, inventory, etc.).

a React UI for an inventory management system with a login page and dashboard, intended to connect with a Business Central (BC) backend:
Project Setup:
Create a new React project using Create React App or a similar tool.
Set up the basic project structure with components, styles, and necessary dependencies.
Login Page:
Design a simple login form with fields for username and password.
Include error handling for invalid inputs.
Implement state management to store user input.
Create a function to handle form submission.
Dashboard:
Design a layout to display user information and BC data.
Include placeholders for various data points or widgets.
Plan for components to display different types of BC data (e.g., sales figures, inventory, etc.).


Can support for M1 Mac?

Bacause most of our dev devices are M1 Mac now, whose speed is fast.

Bacause most of our dev devices are M1 Mac now, whose speed is fast.

I can build this project on M1 mac just without asm supporting.
And you need disable the sdl atomic in the Preprocessor macro:  SDL_ATOMIC_DISABLED


use push instead concat in unique

concat will create an Array, which is not necessary

But push retuns the new length of the array instead of the array itself. Do the tests pass in local? Something went wrong with CircleCI's PhantomJS, but I'm pretty sure some tests should be failing now (or they need to be extended).

I would also say that this is mostly a micro optimization. I'll try running some tests*, but probably within the first few 1000s of elements there's no noticeable difference. If the code changed to the proposed one it'd be fine, but if it has to become more complex I am not sure if it's worth it. I'll post the tests when I get them.
*This is itself difficult because different browsers are optimized differently but I'll try anyway

Probably consider using Set
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set
It is supported in IE11

clean.indexOf(node) === -1  can be slow on large array. Set or object can solve the issue

But unfortunately it is not well supported in most mobile browsers:

Are you finding speed problems when using Umbrella? If so, what's the case/situation? While in general for arrays indexOf() might be slow, I think for the vast majority of the situations where Umbrella's unique() is used (small-ish arrays) it's totally acceptable.

OK. Thanks.


another bug :( File "C:\Users\crist\AppData\Local\Programs\Python\Python39\lib\site-packages\pywhatkit\remotekit.py", line 6, in      from flask import Flask, request

Description
File "C:\Users\crist\AppData\Local\Programs\Python\Python39\lib\site-packages\pywhatkit\remotekit.py", line 6, in
from flask import Flask, request
To Reproduce
Steps to Reproduce the Bug
Screenshots

Version Information

OS: [Windows 10]
Browser: [OPERAGX]
Python: [3.9.10 AMD64]
PyWhatKit: [5.2]

You can Check the PyWhatKit Version using
print(pywhatkit.__VERSION__)

pip install pywhatkit

thanks


Install Anchor fails under macOS

Hi all,
I am getting this error when trying to install Anchor:
    Updating git repository `https://github.com/coral-xyz/anchor`

warning: skipping duplicate package `shared` found at `/Users/thefox/.cargo/git/checkouts/anchor-50c4b9c8b5e0501f/4540c82/tests/zero-copy/programs/shared`
warning: skipping duplicate package `shared` found at `/Users/thefox/.cargo/git/checkouts/anchor-50c4b9c8b5e0501f/4540c82/tests/typescript/programs/shared`
warning: skipping duplicate package `external` found at `/Users/thefox/.cargo/git/checkouts/anchor-50c4b9c8b5e0501f/4540c82/tests/declare-program/programs/external`
warning: skipping duplicate package `swap` found at `/Users/thefox/.cargo/git/checkouts/anchor-50c4b9c8b5e0501f/4540c82/tests/cfo/deps/swap/programs/swap`
warning: skipping duplicate package `docs` found at `/Users/thefox/.cargo/git/checkouts/anchor-50c4b9c8b5e0501f/4540c82/tests/docs/programs/docs`
warning: skipping duplicate package `relations-derivation` found at `/Users/thefox/.cargo/git/checkouts/anchor-50c4b9c8b5e0501f/4540c82/tests/relations-derivation/programs/relations-derivation`
  Installing avm v0.30.0 (https://github.com/coral-xyz/anchor#4540c825)
    Updating crates.io index
warning: package `ahash v0.7.6` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
   Compiling libc v0.2.153
   Compiling proc-macro2 v1.0.79
   Compiling unicode-ident v1.0.12
   Compiling autocfg v1.1.0
error: failed to run custom build command for `proc-macro2 v1.0.79`

Caused by:
  process didn't exit successfully: `/var/folders/vw/20gt5mnj3bbc16jcq14zcnc40000gn/T/cargo-installlCuYZ7/release/build/proc-macro2-c0dfe5d9e48dc013/build-script-build` (signal: 9, SIGKILL: kill)
warning: build failed, waiting for other jobs to finish...
error: failed to compile `avm v0.30.0 (https://github.com/coral-xyz/anchor#4540c825)`, intermediate artifacts can be found at `/var/folders/vw/20gt5mnj3bbc16jcq14zcnc40000gn/T/cargo-installlCuYZ7`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

How can I get this working?

error: failed to run custom build command for proc-macro2 v1.0.79

Not sure what the cause is but searching for this gives a few results in other places. I'd check these GitHub issues regarding this error message and try the mentioned fixes.


Not able to load file autoload.php , i have created php environment inside docker

PHP Warning:  require(vendor/autoload.php): failed to open stream: No such file or directory in /var/www/html/sampleapi.php on line 6
PHP Fatal error:  require(): Failed opening required 'vendor/autoload.php' (include_path='.:/usr/share/php') in /var/www/html/sampleapi.php on line 6

Hi @Rachit77s,
Have you resolved your problem yet? If not, please provide more information
about what exactly you are trying to do and what exact steps you took. To
me, it looks like you didn't use Composer (correctly) to install this
library.

Yes , i got the solution.
Thank you!
On Thu 12 Jul, 2018, 12:34 PM Christian Flach<EMAIL_ADDRESS>wrote:

Hi @Rachit77s,
Have you resolved your problem yet? If not, please provide more information
about what exactly you are trying to do and what exact steps you took. To
me, it looks like you didn't use Composer (correctly) to install this
library.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cmfcmf/OpenWeatherMap-PHP-Api/issues/124#issuecomment-404410957,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae4lmk_RizdI8IK7eyg6-GTZ1I-iE4QBks5uFvUHgaJpZM4VITkI
.


Fix linting

Changed linting rules:

no-unused-vars is now a warning

Woops.  This was not intentional.  It was supposed to go to a forked repository, but the git repository was misconfigured.


add vladimir

Thanks a lot for your PR Simon, but you have a few compile errors. Please try to fix them!


Remove IOException throws from source() and close() on ResponseBody.

source() throwing was the result of legacy integrations which now eagerly open their streams. This eliminates the need for this method to throw as well as a few downstream methods like byteStream() and charStream().
close() throwing puts the caller in an awkward position. They have already read the body (or are ignoring it) and just want to ensure resource cleanup happens. If this fails, however, and the IOException was throw there is no reasonable action for them to take other than ignoring. As such, we take the liberty of ignoring it for them.
Closes #1696.

Ugh. I broke something in the least understood part (for me) of the library. Will dig later.


Re-implement HistoryMessage to use ExpirableObjectBucket

Benefits - cleaner code and removal of message pruning job.

Didn't have to change much, as HistoryMessage was already implemented very similarly to ExpirableObject. I removed functionality that can be inherited, and added a HistoryMessageBucket class that extends ExpirableObjectBucket, and updated all other code references. It also moved from lib/DiscordBot to lib/ExpirableObject/HistoryBucket.


fix(gps): support source urls that point directly to go.googlesource.com

This fixes a bug which can be reproduced simply:
$ dep ensure golang.org/x/crypto:go.googlesource.com/crypto
list versions for golang.org/x/crypto(https://go.googlesource.com/crypto): unable to deduce repository and source type for "https://go.googlesource.com/crypto": unable to read metadata: go-import metadata not found

The problem comes up because there was no deducer for
go.googlesource.com, and go.googlesource.com itself does not have any
metatags that can be used to deduce the vcs.
Generally speaking, this bug would not come up because most users would
target golang.org/x/crypto, which does have all of the required
metadata, but it's a bug all the same.
I encountered the bug (and @sdboyer confirmed it) while working on #818.

I would change goSource to googlesource for consistency with the other sources.
Otherwise, LGTM.

@ibrasho Yeah I had that at first. Not sure why I changed it.

I think we actually need something else here, because there's a bug in the way we handle those source URLs.
Deduction should only really be happening on the import path. Which means the problem here goes back to the same essential problems of #411, where source URLs were being subjected to import path-shaped validation. These paths need to be separated further.
When an alternate source is specified, the system should basically just assume that it's pointing directly at a repository. What's a little hinky here is that we still have to figure out the VCS type, which...well, probably the only easy thing there is to assume it's the same as what was deduced from the import path.
We could merge this, but it should be with a note explicitly saying that it's temporary, and that the real fix is fixing #411. However, I'd prefer that we fix the real problem here, which is better teasing apart how these inputs are validated.

That makes sense, I think. What are your thoughts on deducing just the VCS from a source if it's not otherwise specified? So in cases like go.googlesource.com gps can have code that knows those are git repositories?
Alternatively, it could act like pip, where if you are specifying the source the source must be fully qualified (ie, <vcs>(+<protocol>)?://, such as git+https://go.googlesource.com or git+ssh:// or git://); this could also allow for file:/// as a source.

Alternatively, it could act like pip,

iiinteresting.

this could also allow for file:/// as a source

this is kind of a can of worms; i absolutely believe that we need some kind of solution for arbitrary local code paths, but it has the potential to break lockfile portability in nasty, unpredictable ways. ("lockfile portability" is a concept that i need to do a standalone writeup about.)
the rest is good, though - let's just put a pin in this part for now.

edit: Although I suppose the alternative option may result in a backwards incompatible change

i had the same thought - to require a vcs as part of the scheme would be a backwards incompatible change, and is thus off the table to do in a way that invalidates old, vcs-less schemes. But, the only cases where we wouldn't be able to infer the vcs type from the import path are cases where this would have been failing already.
this suggests to me that we could:

add support for schemes which specify the vcs type
issue warnings when the current project's manifest has source schemes that lack vcs type
error immediately if the current project's manifest has a source schemes without vcs types paired with an un-deducible import path

when it finally comes time to jump into the toolchain, we may allow mild BC breaks like this. if so, we can drop support for vcs-less schemes then.

I agree re: file:///, that won't hold well in a lock file for obvious reasons; so I'm more than comfortable skipping it.
Otherwise, it seems like there's enough possibility here to take a stab at an implementation. Do you mind if I take it on? Should I close this PR and start fresh with one aimed at closing #411?

@avidal that'd be great! fair warning, this will be pretty involved, and touch a number of things 😄

(so, don't hesitate to put up a WIP PR and ask plenty of questions as needed)

🖖 Closing this and opening a WIP PR when I get a chance.


fix filter removal for http filter

Found this bug in this PR https://github.com/istio/istio/pull/36404. Http filter removal does not work correctly.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
42cd279a1ed590c8d417a5a4413daa80abda5053
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

network filter removal has test but not http filter removal. Added a test for it. PTAL.

In response to a cherrypick label: new pull request created: #37961


[Feature] Support Variant type

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Add Variant type to paimon data type
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

This feature is based on Spark 4.x: https://github.com/apache/paimon/issues/3940


feat(icons): add advanced sql icon

Description

Add advanced_sql icon.
Add a readme file for custom icons.

Test Steps

[x] npm run storybook
[x] Open Icon component
[x] Open Covalent icon and select advanced_sql icon in storybook controls

General Tests for Every PR

[x] npm run start still works.
[x] npm run lint passes.
[x] npm run stylelint passes.
[x] npm test passes and code coverage is not lower.
[x] npm run build still works.

Screenshots or link to StackBlitz/Plunker

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

v8.12.0
GitHub release

Your semantic-release bot :package::rocket:


Local in-development apps should connect to the system being run in a local docker

As a developer implementing the Smart Cities data platform, I want an easy way to run the entire system on my machine.
A developer should be able to run an app with iex -S mix and connect to the rest of the system running in docker on their machine.
Acceptance Criteria:

All other apps besides Discovery API and Discovery UI are able to talk to the rest of the system running in Docker
Scos system test (run locally) passes for each app pulled out into iex
Minimum of configuration changes

Technical Notes:

Depends on #41
Configuration should be done in integration.exs
Phoenix apps may need to have a host file changed

rejected 08/14/19 by Carrie and Johnson


Add account settings page with Name and Email fields

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on enhancing the account settings functionality by implementing email confirmation and account update features, including UI adjustments and new API integrations.
Detailed summary

Added a new route for /account/settings.
Implemented updateAccount and confirmEmailWithOTP functions for updating account details and confirming email.
Updated AccountSettingsPage to handle email updates and account name changes.
Enhanced AccountSettingsPageUI to integrate email confirmation and account updates.
Refactored email update logic and UI components to support OTP verification.
Improved error handling for email sending and updating processes.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5461  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.