init/init.sh not running in dust-front Docker image

front/Dockerfile currently has 2 CMD commands. But Docker only allows one per Dockerfile. So the first one is getting ignored.
https://github.com/dust-tt/dust/blob/eaef34ba33b680ef015cf7a559f9391eef2f9ba9/front/Dockerfile#L9-L12
The first one is the command that sets up the database so this is failing silently and then I got a database error. When I logged into the docker image and ran the init script it fixed things.

Hi hi! The Docker has not been maintained. Let me update the README

Updated. Let me know if that works for you :+1:

Hi @spolu,
I though to contribute docker support for easier setup and found out that it actually existed before this issue:
https://github.com/dust-tt/dust/commit/7743768915b83640110c5b73bfe3a1c9b20c2796
I understand that Docker support would need to be continuously updated with the latest changes to the application, but just wanted to ask what's your opinion to have docker support in general?

Last support rotted pretty quick. Happy to revisit if useful to you :+1:

Sorry, just noticed your reply.
I was able to spin it up on ubuntu:
# Install Rust
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -y

# FIX: error: linker `cc` not found
sudo apt update
sudo apt install build-essential
# FIX: Could not run `\"pkg-config\"
sudo apt install pkg-config
# FIX:  could not find system library 'openssl'
sudo apt install libssl-dev

# Install dust CLI
git clone https://github.com/dust-tt/dust.git
cd dust/core
cargo build --release --bin dust
alias dust="$(pwd)/target/release/dust"

# Install nodejs
sudo apt install nodejs

# Start rust web app
cargo run --bin dust-api >> dust-api.log &

# Front end app
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash
nvm install v19.6.0
nvm use v19.6.0

cat <<EOF >> .env.local
URL=http://localhost:3000

NEXTAUTH_URL=$URL
NEXTAUTH_SECRET=25da29db5485fcd27d2f671c5e28d5df8f325e9470c36cb6bf0a9d19c662255a

FRONT_DATABASE_URI=sqlite:front_store.sqlite
XP1_DATABASE_URI=sqlite:xp1_store.sqlite

GITHUB_ID=47ec837fcbac1c6f1690
GITHUB_SECRET=d59af0da231fc697d7dd8d3002ed1d9765e11c7f

DUST_API=http://localhost:3001

THUM_IO_KEY=0-Foo
GA_TRACKING_ID=Foo
EOF

XP1_DATABASE_URI=sqlite:xp1_store.sqlite FRONT_DATABASE_URI=sqlite:front_store.sqlite ./init/init.sh

npm run dev &


Create workbooks for the katas/tutorials, part 2

(This issue is the second part of #208)
The katas offer a set of programming exercises on quantum computing and reference solutions to them, but we often hear that it would be helpful to have the solutions explained, with the logic steps necessary to arrive from the problem description to the code spelled out. It is especially important for people who go through the katas on their own, without a study group to support them.
To address this, we came up with the idea of "workbooks" - explanations of the solutions to the tasks offered in the katas/tutorials, written in Jupyter Notebook format. You can check any of the workbooks completed in #208 to get an idea of what the workbooks look like.
Here are the katas and tutorials that don't have a workbook yet and seem like a good fit for one.

[x] BasicGates (@TonyHoldroyd)
[ ] GraphColoring, part IV triangle-free coloring
[x] KeyDistribution_BB84 (@devikamehra)
[ ] MagicSquareGame
[ ] PhaseEstimation (@PratikSathe)
[ ] QEC_BitFlipCode (@japanavi)
[x] QFT (@WaywardPhoton)
[ ] RippleCarryAdder (@Parisha-Agrawal)
[ ] SuperdenseCoding (@CemNurlu)
[ ] Teleportation (@CemNurlu)
[ ] TruthTables (@olstulo)
[ ] tutorials/Oracles (offline)
[x] tutorials/RandomNumberGeneration (@ssc1729)

I would love to work on them, @tcNickolas. Will it be okay if I move with a slow pace for these?

@born-2learn Sure! Usually I recommend to pick one workbook to work on and claim it, so that if somebody else wants to take another one, they can; once that one is complete, can pick another one if you want, and so on. The #208 took about a year to complete :-) (though it had more workbooks in it)

@tcNickolas Alright, I would like to try out the Phase Estimation workbook then.

@tcNickolas  Is there anything I can work on? I'd be happy to create workbooks for QFT if that is something that would be needed.  It seems like there isn't one currently available.

@tcNickolas  Is there anything I can work on? I'd be happy to create workbooks for QFT if that is something that would be needed.  It seems like there isn't one currently available.

Hi Ana,
Absolutely! I'm not aware of anybody else working on the QFT kata workbook,
so you're welcome to it! Please let me know if you need any help from me to
get started.
On Fri, May 28, 2021 at 9:22 PM Ana Madalena @.***>
wrote:

@tcNickolas https://github.com/tcNickolas Is there anything I can work
on? I'd be happy to create workbooks for QFT if that is something that
would be needed. It seems like there isn't one currently available.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/QuantumKatas/issues/542#issuecomment-850766755,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNFAAEIR5PIUQH3NBY2U2DTQBTZZANCNFSM4S2RPEBA
.

@tcNickolas  I'd love some general guidelines on content. I know that the solution already exists (and all I have to do is explain it) but if there is anything specific that explanations are required to have I'd like to know!

The best way to get an idea of how the workbook should look is probably
checking out the ones for other katas. Typically we want to explain the way
to come to the solution mathematically, and then to highlight some Q#
features/library operations that come in handy but can be not obvious for
someone who is just getting started with the language.
On Sat, May 29, 2021 at 2:51 PM Ana Madalena @.***>
wrote:

@tcNickolas https://github.com/tcNickolas I'd love some general
guidelines on content. I know that the solution already exists (and all I
have to do is explain it) but if there is anything specific that
explanations are required to have I'd like to know!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/QuantumKatas/issues/542#issuecomment-850903999,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNFAACJWBVTUQ42F4FTZBTTQFOV7ANCNFSM4S2RPEBA
.

Hi @born-2learn and @WaywardPhoton,
Are you still working on the PhaseEstimation and QFT workbooks, respectively? Let me know if you want to drop them or need any help from me - I finally have a little breathing room compared to the past few months, and hope to catch up on the open source work on the Katas in the next few weeks!

Hi, yes, I am almost done the QFT. Has been a busy two weeks with school.
Just doing some research to figure out part 3. I can send you what I have if you want.

@WaywardPhoton
Oh, I forgot we had part 3 in the QFT kata at all!  You can definitely skip that one, those are tasks from the Q# Coding Contest #3 and they're pretty advanced. We have writeups of the solutions at https://assets.codeforces.com/rounds/1357/problems-e1e2-2.pdf, so I'll be able to hunt down the sources from which we generated that pdf and to reuse them, or to upload the pdf as a whole and use it as is.
If you have parts 1 and 2, please feel free to send the pull request and I'll take a look next week. We'll deal with part 3 later.

Gone ahead and made the pull request. Thanks!

@tcNickolas Ciao, I should like to either: develop a workbook for the Quantum BasicGates kata, or: develop a kata for the Classical language features of Q# (possibly subdidivided into smaller programmatical logocal units) , as per your notifications. As far as I can tell, nobody has taken these on yet.Please would you kindly let me know which, if either, of these, (or both in the fullness of time) you would support for my first foray into MS documentation development. Thankyou Mariia..

@TonyHoldroyd I'll be happy to support you in both of these endeavors! I recommend starting with the workbook for the BasicGates kata, since it is a well-defined work. Meanwhile I'll think about the way to organize the classical features kata and open a new issue for it - it's been on the roadmap forever and I never got to writing that down (thank you for the reminder!!) It seems that it can be very modular but probably not to the point of having separate katas for each of the variables, loops, conditional branching, etc.

About the scopes of the individual katas for classical features of Q#: sure thing, I expect logical groupings of the features into around about 4 sets might be the order of the day.

Ciao Mariia, to edit the workbooks (and katas) do you recommend working with markdown and Latex directly in Jupyter Notebooks or use some other editor? Thanks

I edit Jupyter Notebooks directly in their environment - they're very
convenient in that you can edit the Markdown of the cells and then
immediately view it in the same environment, and the same with the code
cells, you can write the code and run it in the same place.
On Thu, Sep 23, 2021 at 5:49 AM Tony Holdroyd @.***>
wrote:

Ciao Mariia, to edit the workbooks (and katas) do you recommend working
with markdown and Latex directly in Jupyter Notebooks or use some other
editor? Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/QuantumKatas/issues/542#issuecomment-925783686,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNFAAABXBDZAV3LYMAK5H3UDMO5DANCNFSM4S2RPEBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@tcNickolas Thank you Mariia, good, yes, that's what I was hoping you would say, I've used Jupyter Notebooks extensively in the past and have started with them for this work.
What do you think about the idea of adding a small extension task at the end of the solution to each Basic Gates  Task please?
The reason I ask is that in the Learning Path, Basic Gates follows Single Qubit Gates; the work involved in Basic Gates is largely recall or looking-up and I thought a little reinforcement might be in order.
Here is an example I thought to suggest for Task 1:
Extension task: A single qubit is in a superposition  |𝜓⟩=𝛼|0⟩+𝛽|1⟩  with  𝛼=0.42 . Work out  𝛽 , (to 2 decimal places), and write down  |𝜓⟩  both before and after applying the Pauli-X gate to it.

@tcNickolas Ciao Mariia, I have had a stab at the first two Tasks in the Basic Gates kata and was wondering if you have time to review  them for me  please?

@TonyHoldroyd Sure, you can attach the notebook to this thread and I'll take a look. (You might have to rename it to .txt, I think GitHub is not happy about .ipynb attachments.)
For the actual pull request, I recommend waiting until October 1st if you're interested in participating in Hacktoberfest - they have nice t-shirts if you like that kind of thing :-)

Hello,
If it's still up for grabs, i can start working on Superdense Coding and Teleportation Workbooks. Is there a specific format guideline for the workbooks? If not i can start working now.

@CemNurlu Yes, these are still up for grabs! The workbooks do follow a specific structure, with a standard introduction followed by a sequence of tasks, with a task description, solution description, and solution code, and links to and from the kata notebook to link the respective tasks in both. You can check out any existing workbooks to see the structure; a recent example of a pull request adding a workbook is https://github.com/microsoft/QuantumKatas/pull/636.

@TonyHoldroyd I took a quick look your workbook draft, here are a few comments:

When we reference tutorials or katas from notebooks, we use relative links to .ipynb tutorial files instead of absolute GitHub links - this way, if a person is on Binder or running the notebook locally, the link will take them directly to the tutorial referenced, rather than back to GitHub to find their way back to the notebook version of the tutorial
When discussing a task, we usually put the solution description first, and the code cell second - this way the learner can take a peek at the beginning of the solution, realize what they've been missing in their thinking, and keep trying to do it on their own, rather than being faced with the answer right away
Looks like in some tasks you're using formulas and in some tasks (like task 1.2) - Unicode. The katas started with .qs files - they are actually older than Q# Jupyter Notebooks! - which don't support formulas, so I had to get creative with Unicode there (and I'm still using plenty of Unicode in GitHub comments). In Jupyter Notebooks, though, we're using formulas, both for uniformity across all notebooks and because they render prettier
The product in the formulas is best denoted with \cdot macro
In task 1.1, we probably don't need the note in italics, since this is not a tutorial that introduces the gates, but an exercise to practice using them
For the extension tasks, it probably makes sense to move the tasks themselves to the kata, and add the solutions to them to the workbook? Similar to the programming tasks, but without the code cells
For task 1.2E, I'm not sure what you mean by checking that H|+⟩ = 0.7071(|0⟩ +|1⟩) - did you mean to check that H|+⟩=|0⟩?
Task 1.3E seems to be very similar to exercise 3 from SingleQubitGates tutorial? Maybe we could do something more interesting here, say, combine H with Z?
When we work with angles, we usually express them in radians - fractions of 𝜋 are a lot more common in quantum computing than degrees. I think it makes sense to stick to this convention in this tutorial as well

I hope these notes make sense - let me know if you have questions about them! Once you've addressed them, I think you can send the pull request with the first four tasks. Smaller pull requests make it easier for me to review them promptly. You might also want to split adding the extension tasks into a separate pull request, since they'll need extra work on the solutions as well.

Ciao Mariia, thank you very much for taking the time to leave me such detailed and helpful feedback notes, all of which make total sense.
What I thought was, if I make a pull request for every 4 workbook tasks would that be manageable?  I could do less, whatever would suit you, . Then I can merge all the tasks into one workbook at the end when you have approved them (I have found a little Python program for that). Also I'll put all the extension tasks into one or two files as they are short. I've registered with Hacktoberfest.

@tcNickolas, I would like to contribute on this. I can start with tutorials/RandomNumberGeneration. Let me know if it already taken.

@ssc1729 Sounds great - I don't think anybody's working on RandomNumberGeneration so you're welcome to it!

I can do QEC_BitFlipCode!

@japanavi Sounds good!

Hi @tcNickolas , I would like to work on one of the workbooks or tutorials. It seems to me that the Oracles Tutorial might be up for grabs. Is MagicSquareGame, or any other one taken?

Hi @PratikSathe, welcome back! :-)
Let me check quickly with someone who expressed interest in the workbook for the Oracles tutorial; all others that are not marked as taken are up for grabs!

Hi @tcNickolas , I would like to work on Phase Estimation!

@PratikSathe Sounds good!

Hi @tcNickolas  , I would like to work on the tasks in Ripple Carry Adder. I am planning to send 3-4 workbook tasks in a PR so that it is manageable with my college course. Would that be ok with you?

Thanks @tcNickolas . I will get started on "Ripple Carry Adder" workbook then. I will update this thread when my first draft is ready  :-)

Hi @tcNickolas , I have created pull request to add workbook tasks 1.1 - tasks 1.3 in pull request. https://github.com/microsoft/QuantumKatas/pull/794
Would be glad to receive your feedback.


[Knight] Riddler Doesn't Mark as Completed in NG+

Optimally, for Knight we leave a riddle unsolved in NG and therefore can't finish Riddler in NG for the sake of file setup. This causes issues with NG+, because all NG+ does is check if the save ID is present twice in the save file. But since after beating Riddler in NG+ it'll only be present once, it won't mark as completed.
Unsure how to work around this.

Apparently this was resolved quite a while ago.


Upgrade babel-plugins

Upgrading all babel-plugin-* dependencies due to conversation in https://github.com/babel/ember-cli-babel/pull/382#issuecomment-792146538

@babel/plugin-proposal-decorators
@babel/plugin-transform-modules-amd
@babel/plugin-transform-runtime
@babel/plugin-transform-typescript
babel-plugin-ember-modules-api-polyfill

/cc @rwjblue

Updated the package.json 👍

Hmmm. Something is causing the floating dependencies tests to time out.

@rwjblue seeing this in CI. Will have a dig later

Seems like the same thing being reported in later comments over in https://github.com/babel/ember-cli-babel/issues/384

Interesting, so bumping a few other babel-related deps has caused the issue to manifest in the non-"floating dependencies" tests. Unfortunately it's only happening in CI for me, I can't reproduce locally, so will need to rollback each of those upgrades I just did one-by-one.

I've canceled some of the CI runs (to try to get faster turn around)


Add DNS caching and update dependencies

cc @wikimedia/services

Coverage remained the same at 86.076% when pulling b8ef149af458b14e299151f1ca5083a916362610 on Pchelolo:new-service-runner into 11f1945c4c91ed9ab73274995d5f56b18f6540b5 on wikimedia:master.

Coverage remained the same at 86.076% when pulling b8ef149af458b14e299151f1ca5083a916362610 on Pchelolo:new-service-runner into 11f1945c4c91ed9ab73274995d5f56b18f6540b5 on wikimedia:master.

Coverage remained the same at 86.076% when pulling b8ef149af458b14e299151f1ca5083a916362610 on Pchelolo:new-service-runner into 11f1945c4c91ed9ab73274995d5f56b18f6540b5 on wikimedia:master.

:+1:

Coverage remained the same at 86.076% when pulling 8c499448a947d16cfcefcacba6e0d6f50dba5242 on Pchelolo:new-service-runner into 11f1945c4c91ed9ab73274995d5f56b18f6540b5 on wikimedia:master.

Coverage remained the same at 86.076% when pulling 8c499448a947d16cfcefcacba6e0d6f50dba5242 on Pchelolo:new-service-runner into 11f1945c4c91ed9ab73274995d5f56b18f6540b5 on wikimedia:master.

Coverage remained the same at 86.076% when pulling 8c499448a947d16cfcefcacba6e0d6f50dba5242 on Pchelolo:new-service-runner into 11f1945c4c91ed9ab73274995d5f56b18f6540b5 on wikimedia:master.


Box

fix https://github.com/quark-zju/gcmodule/issues/8

This removes an optimization. The old code will not track types like Box<T> where T is known to be untracked. That means Cc<Box<T>> won't be inserted to the linked list and Cc<Box<T>> takes less space in memory.


ARROW-3397: [C++] Change a CMake relative path for modules

Change the path of the modules to support Arrow inclusion to other
CMake projects

My JIRA username is luc1ph3r, if I understood you correctly


How to make sure there's no stray container not removed when using withDockerfileFromBuilder?

Hi guys,
On XWiki, and since the upgrade to TC 1.15.0 (might not be related but didn't notice it before),  I've noticed on our CI agents, that there are some TC-created containers that are not always removed on agents. For example:

These containers are created with the following:
                LOGGER.info("(*) Build a dedicated image embedding LibreOffice...");
                // The second argument of the ImageFromDockerfile is here to indicate we won't delete the image
                // at the end of the test container execution.
                container = new XWikiLocalGenericContainer(new ImageFromDockerfile(imageName, false)
                    .withDockerfileFromBuilder(builder -> {
                        builder
                            .from(baseImageName)
                            .user("root")
                            .env("LIBREOFFICE_VERSION", officeVersion)
                            .env("LIBREOFFICE_DOWNLOAD_URL", "https://downloadarchive.documentfoundation.org/"
                                + "libreoffice/old/$LIBREOFFICE_VERSION/deb/x86_64/"
                                + "LibreOffice_${LIBREOFFICE_VERSION}_Linux_x86-64_deb.tar.gz")
                            // Note that we expose libreoffice /usr/local/libreoffice so that it can be found by
                            // JODConverter: https://bit.ly/2w8B82Q
                            .run("apt-get update && "
                                + "apt-get --no-install-recommends -y install curl unzip procps libxinerama1 "
                                    + "libdbus-glib-1-2 libcairo2 libcups2 libsm6 && "
                                + "rm -rf /var/lib/apt/lists/* /var/cache/apt/* && "
                                + "wget --no-verbose -O /tmp/libreoffice.tar.gz $LIBREOFFICE_DOWNLOAD_URL && "
                                + "mkdir /tmp/libreoffice && "
                                + "tar -C /tmp/ -xvf /tmp/libreoffice.tar.gz && "
                                + "cd /tmp/LibreOffice_${LIBREOFFICE_VERSION}_Linux_x86-64_deb/DEBS && "
                                + "dpkg -i *.deb && "
                                + "ln -fs `ls -d /opt/libreoffice*` /opt/libreoffice")
                            // Increment the image version whenever a change is brought to the image so that it can
                            // reconstructed on all machines needing it.
                            .label(OFFICE_IMAGE_VERSION_LABEL, imageVersion);
                        if (this.testConfiguration.getServletEngine() == ServletEngine.JETTY) {
                            // Create the right jetty user directory since it doesn't exist
                            builder.run("mkdir -p /home/jetty && chown jetty:jetty /home/jetty")
                                // Put back the user as jetty since it's a best practice to not execute the container as
                                // root.
                                .user("jetty");
                        }

                        builder.build();
                    }));

See https://github.com/xwiki/xwiki-platform/blob/eaced75f5a08b4131e36504fb5f6c71d6b392fa8/xwiki-platform-core/xwiki-platform-test/xwiki-platform-test-docker/src/main/java/org/xwiki/test/docker/internal/junit5/servletengine/ServletContainerExecutor.java#L286 for more details.
Would you have any idea what could be happening and what we could do?
Thanks a lot

This is still happening (we upgraded to 1.15.1). The days when the container exited suggest that the container is removed most of the time but sometimes it's not. Since it only happens for the container we dynamically build with withDockerfileFromBuilder, there must be something special with it I guess.
@rnorth @bsideup would you have any idea or direction for me to look at to debug this problem?
Thanks a lot

@vmassol could you please docker inspect one of such containers and share it? (e.g. as a Gist)
I'd assume that, while building the image, Docker creates a temporary container that we cannot control, and somehow fails to remove it afterwards. Although in such case there isn't much we can do and it requires a help from the Docker team (unless you can verify that it worked with 1.14.x, for example)

@vmassol could you please docker inspect one of such containers and share it? (e.g. as a Gist)

https://gist.github.com/vmassol/fbe1c8190313eb5b5e3be7a7040e262e

(unless you can verify that it worked with 1.14.x, for example)

What's sure is that it wasn't happening in the past. But I don't know if it's related to a TC version or a Docker version or some other factor.
Thanks for the help!

Oh yeah, the container is missing org.testcontainers.* labels, meaning that we have no control over it.
We do add the labels to buildImageCmd to control it, so maybe Docker introduced a regression and build containers no longer have them? Although I would still expect Docker to take care of the temporary containers that it creates.
I am afraid there isn't much we can do on our side. Consider reporting this regression to Docker...

Note that, seen the pattern, most of the containers from that custom image are removed when the tests stop. It's only under some conditions that they're not removed (jvm crash, low memory, etc?).
Just checked now and I have on one agent:
CONTAINER ID   IMAGE                         COMMAND                   CREATED          STATUS                      PORTS                                       NAMES
33746d529429   xwiki/build:latest            "setup-xwiki-ssh /bi…"    16 minutes ago   Up 16 minutes               22/tcp                                      frosty_joliot
b1cf5ca28954   zenika/alpine-chrome:latest   "chromium-browser --…"    10 hours ago     Up 10 hours                 <IP_ADDRESS>:9222->9222/tcp, :::9222->9222/tcp   headless-chrome-pdf-printer
559f799a9493   3164a570eeda                  "/bin/sh -c 'apt-get…"    6 weeks ago      Exited (127) 6 weeks ago                                                cranky_johnson
e1bdd2a24a61   b90919f94b34                  "/bin/sh -c 'apt-get…"    6 weeks ago      Exited (127) 6 weeks ago                                                elastic_lewin
a26ca27ee938   3164a570eeda                  "/bin/sh -c 'apt-get…"    7 weeks ago      Exited (127) 7 weeks ago                                                infallible_panini
0ad07d8be43c   97239b5261ad                  "/bin/sh -c 'apt-get…"    8 weeks ago      Exited (127) 8 weeks ago                                                infallible_keldysh
08b40212f071   97239b5261ad                  "/bin/sh -c 'apt-get…"    2 months ago     Exited (127) 2 months ago                                               relaxed_clarke
f8689d670a70   db4dc2c95281                  "/bin/sh -c 'apt-get…"    2 months ago     Exited (127) 2 months ago                                               naughty_moser
1ab73e2dd7d5   db4dc2c95281                  "/bin/sh -c 'apt-get…"    2 months ago     Exited (127) 2 months ago                                               trusting_beaver
fe7336414a6e   c4be6f55f475                  "/bin/sh -c 'apt-get…"    2 months ago     Exited (127) 2 months ago                                               musing_antonelli
f0f9e9dc13e5   db4dc2c95281                  "/bin/sh -c 'apt-get…"    2 months ago     Exited (127) 2 months ago                                               nostalgic_chatelet
e3238a68bc86   95b12cdf8c88                  "/bin/sh -c 'apt-get…"    2 months ago     Exited (127) 2 months ago                                               eager_jackson
a4a1b30fbab7   db4dc2c95281                  "/bin/sh -c 'apt-get…"    2 months ago     Exited (127) 2 months ago                                               quirky_kirch
04fc608fd010   db4dc2c95281                  "/bin/sh -c 'apt-get…"    2 months ago     Exited (127) 2 months ago                                               unruffled_swirles
01f33815fab1   db4dc2c95281                  "/bin/sh -c 'apt-get…"    3 months ago     Exited (127) 3 months ago                                               tender_sammet
f2178e641cad   db4dc2c95281                  "/bin/sh -c 'apt-get…"    3 months ago     Exited (127) 3 months ago                                               fervent_liskov
0a5de21cf39d   e02cd5ad11c2                  "/bin/sh -c 'apt-get…"    6 months ago     Exited (4) 6 months ago                                                 dreamy_feynman
fe481ef87177   e02cd5ad11c2                  "/bin/sh -c 'apt-get…"    6 months ago     Exited (4) 6 months ago                                                 ecstatic_montalcini
9adc2b921d1d   eff629089685                  "docker-entrypoint.s…"    13 months ago    Exited (0) 13 months ago                                                jolly_swirles
fc376cf6e641   testcontainers/sshd:1.0.0     "sh -c 'echo \"root:$…"   13 months ago    Exited (137) 5 weeks ago                                                serene_euler

(it's all the "apt-get" ones)
I wanted to work around this but I don't see how to do it. If I do an explicit remove at the end of the test (in a JUnit5 extension for ex), it probably won't help since those are probably removed correctly already.
Is there any way I could manually register this container against ryuk so that it removes it after the test is done?
Thanks

Actually I know how to do it! :) I'll put a "docker prune --filter" in our jenkins pipeline before the build starts. Just need to find the tags to identify these containers.

Just need to find the tags to identify these containers.

Done in:

https://github.com/xwiki/xwiki-platform/commit/5b750f342f5459fcb67c472c56fe622d9c11b364
https://github.com/xwiki/xwiki-jenkins-pipeline/commit/5643e3f1aad27f1b89b9dd77f31c203b573fc9a6

Let's see if it works now...


How to work with JavaScript Date in C++

I am using duktape to implement some JavaScript calls in C++:
I have a script that is something like this:
myFunction(new Date(););
My question is, how do I declare myFunction so that I can access the time information in that date parameter (in double format, for example)?
All the JS/C examples I see are about strings and numbers, but I haven't seen anything dealing with dates.
Thanks,

The simplest thing would probably be to do the equivalent of:
function myFunction(x) {
    var t = x.valueOf();  // time in milliseconds
    // ...
}

In C one would do something like:
duk_ret_t myFunction(duk_context *ctx) {
    /* Index 0: argument Date */
    duk_push_string(ctx, "valueOf");
    duk_call_prop(ctx, 0 /*Date instance*/, 0 /*nargs*/);
    /* Stack here: [ ... time ] */
    double t = (double) duk_get_number(ctx, -1);
    /* ... */
}

@jcmerlin Was this question resolved from your point of view?


DOC: Add contribution thanks in changelog

Let me know if you'd rather have a contributors file, and if you think we should credit specific PRs to listed contributors.
Also update the copyright to 2017 and to include me.

We should have a zenodo file. I'll set it up after this release. We also need to appropriatelly credit all of the methods used in FMRIPREP (calls for a duecredit coding sprint).


Check for new verified projects with Optimism addresses: Drop 7

We'll need to query the db to check for verified projects that have added an OP address. You know the drill @mohammadranjbarz
Then I will compare against our previous data to find the new projects and setup the distribution of 25 OP each and set it up via our multisig
Once setup and sent we will inform the comms team to make external communication.
Here is the spreadsheet I've been keeping data in for reference
https://docs.google.com/spreadsheets/d/1pZ7SUtFcf6sNZ3A8fZXBvtDGAn_w21qD3WOaB4baDOE/edit?usp=sharing

@divine-comedian
related to https://github.com/Giveth/giveth-dapps-v2/issues/2637#issuecomment-1677422274
Query
SELECT
    pa."createdAt" as "walletAddressAddedTime",
    pa."projectId",
    pa.address,
    p.slug
FROM
    project_address pa
JOIN
    project p ON pa."projectId" = p.id
WHERE
    pa."networkId" = 10 AND pa."isRecipient" = true AND p.verified = true AND p."statusId"=5
ORDER BY
    pa."createdAt" ASC;

Response
active-verified-projects-that-have-optimism-address-drop7.csv


ocamlPackages.tar: 2.6.0 -> 3.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mirage/ocaml-tar/releases.
meta.description for ocamlPackages.tar is: Decode and encode tar format files in pure OCaml
meta.homepage for ocamlPackages.tar is: https://github.com/mirage/ocaml-tar
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.0 with grep in /nix/store/fsqpxs0d5icwivl3mmhy377a56kch8fg-ocaml5.1.1-tar-3.0.0
found 3.0.0 in filename of file in /nix/store/fsqpxs0d5icwivl3mmhy377a56kch8fg-ocaml5.1.1-tar-3.0.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

comby
ligo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fsqpxs0d5icwivl3mmhy377a56kch8fg-ocaml5.1.1-tar-3.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.tar https://github.com/r-ryantm/nixpkgs/archive/1d3d54fa20ee188c5f36957fe35970f77e2242ed.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1d3d54fa20ee188c5f36957fe35970f77e2242ed#ocamlPackages.tar

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fsqpxs0d5icwivl3mmhy377a56kch8fg-ocaml5.1.1-tar-3.0.0
ls -la /nix/store/fsqpxs0d5icwivl3mmhy377a56kch8fg-ocaml5.1.1-tar-3.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

comby
ligo

2 packages built:

ocamlPackages.tar
ocamlPackages.tar-unix

Maintainer pings
cc @ulrikstrid for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mirage/ocaml-tar/releases.
meta.description for ocamlPackages.tar is: Decode and encode tar format files in pure OCaml
meta.homepage for ocamlPackages.tar is: https://github.com/mirage/ocaml-tar
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.1.2 with grep in /nix/store/1f0c0ynkj30vv38p99ag3z1n7r2yz1dw-ocaml5.1.1-tar-3.1.2
found 3.1.2 in filename of file in /nix/store/1f0c0ynkj30vv38p99ag3z1n7r2yz1dw-ocaml5.1.1-tar-3.1.2

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

comby
ligo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1f0c0ynkj30vv38p99ag3z1n7r2yz1dw-ocaml5.1.1-tar-3.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.tar https://github.com/r-ryantm/nixpkgs/archive/ea69a706c4536e8f130ff64bf25142d50a72f761.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ea69a706c4536e8f130ff64bf25142d50a72f761#ocamlPackages.tar

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1f0c0ynkj30vv38p99ag3z1n7r2yz1dw-ocaml5.1.1-tar-3.1.2
ls -la /nix/store/1f0c0ynkj30vv38p99ag3z1n7r2yz1dw-ocaml5.1.1-tar-3.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

comby
ligo

2 packages built:

ocamlPackages.tar
ocamlPackages.tar-unix

Maintainer pings
cc @ulrikstrid for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


fix: pickle array attributes

This PR should have been done earlier (it fell off my To-Do list!). It introduces a versioned unpickling scheme (through dedicated unpickling functions) that ensures we also serialise the attrs and behavior dictionaries. As per the semantics of attrs, we drop any prefixed keys.
@lgray it occurs to me that inter-worker transfer would break arrays which depend upon @foo keys existing in the attrs dict. I can't imagine that we would want that. Maybe we need to discuss the issue further, though this PR can merge as-is.

For @foo it's setup by construction, and in fact exploited, in coffea that those attrs disappear on serialization.
For more general use I see the issue but I tend to consider @foo client-side only attributes.

@lgray I think we've hithertoo thought about these attributes disappearing during serialisation of the graph, but not of the serialisation that occurs when a result is moved between workers during graph execution. As I understand it, should Dask decide to do this, the high-level behaviour would break because these attributes would no longer exist.

My view is also that we should always drop attributes at serialisation time. My question is whether a chained operation that doesn't get fused and runs on multiple nodes would ever need the things you're storing in attrs under @-prefixed keys. If it's only needed at graph building time, then we're fine!
Otherwise something more magical, e.g. behavior-overloads for pickling, would be needed.

In my case what you're mentioning never happens. Everything I need @foo for is during task-graph creation as opposed to execution. Though, for sure I can imagine people doing much more clever things where what you're saying may happen... But then they should just use a regular attr, no?


 Maybe we can manipulate with headers before GOLINT

@kuritka I definitely don't want to employ super sophisticated machinery with lots of rubygem dependencies here.
Also tried https://github.com/google/addlicense . It does pretty much the same stuff as the tiny shell script provided.
So I suggest we stick with the simplest version of it which does not bring in any new dependencies


Auth

First swing at the topic (probably I have no clue what i'm doing, so be gentle
Signed-off-by: Jasmin Gacic<EMAIL_ADDRESS>Fixes #399

Closed in favor of #452


Add LICENSE full text into source license and remove NOTICE

Following @justinmclean vote suggestion, I will try to fix this in master branch first, whether we need a second round vote for 5.0.0-RC or not.

According to this vote thread<EMAIL_ADDRESS>

Coverage remained the same at 16.046% when pulling 6d597f0c419f4e0e4eefaaeea920b5c1cbc9a92c on fix-v6-LICENSE into 73679fc0f01ce22f6cd0c3df2254269533b43e7e on master.


tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'LeakyRelu' in binary running on cb56f6cc53b2. Make sure the Op and Kernel are registered in the binary running in this process. Note that if you are loading a saved graph which used ops from tf.contrib, accessing (e.g.) tf.contrib.resampler should be done before importing the graph, as contrib ops are lazily registered when the module is first accessed.

tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'LeakyRelu' in binary running on cb56f6cc53b2. Make sure the Op and Kernel are registered in the binary running in this process. Note that if you are loading a saved graph which used ops from tf.contrib, accessing (e.g.) tf.contrib.resampler should be done before importing the graph, as contrib ops are lazily registered when the module is first accessed.

Make sure to import the contrib.decent_q module:
import tensorflow.contrib.decent_q

I  have import ，the problem is  about the tensorflow version ，xilinx  version is 1.12，my model for yolov3 is  1.13.1


Allow redis keys to be namespaces

I would like to add the ability to namespace keys in redis so that we can reduce the number of collisions in redis. I'm going to start working on this and hopefully make a PR for it once I'm done. Just wanted to open the issue and get some feedback on this.

Nevermind, I see that this is allowed by passing in a namedspaced redis instance.


ERROR: Error response from daemon: datastore for scope "global" is not initialized

I create successfully a swarm, with two nodes. However when I use docker-compose build && docker-compose up in order to start my project it crashes erroring out this:
ERROR: Error response from daemon: datastore for scope "global" is not initialized
It's a very very simple process:
docker run swarm create
swarm hash:
1477bcd7778d083e02a80c352d4f1b87
docker-machine create -d virtualbox --swarm --swarm-master --swarm-discovery token://1477bcd7778d083e02a80c352d4f1b87 myswarmmaster
docker-machine create -d virtualbox --swarm --swarm-discovery token://1477bcd7778d083e02a80c352d4f1b87 myremotenode1
eval $(docker-machine env --swarm myswarmmaster)
docker-compose build && docker-compose up
And then I get the error:
ERROR: Error response from daemon: datastore for scope "global" is not initialized
By the way this is the entire content of my docker-composer.xml
version: '2'
services:
    debian:
        image: debian

I'm running Docker version 1.12.6 on Fedora 25.

Any clue? @mavenugo @thaJeztah
Appreciate all efforts to help me out!

In order to create overlay networks (default when creating networks on classic swarm) you must set the correct options on the daemon, specifically: --cluster-store, and --cluster-advertise.
This is because overlay networks on classic swarm requires use of an external K/V store.
If you use the new swarm-mode in 1.12, none of this is required.
Closing as it is a non-issue.

Thanks @cpuguy83! Answer very helpful!
I have two question tho:

It's not clear for which version I'm using, would you help me saying if I'm over version 1.12 please?

$ docker version
Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 08:21:51 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 08:21:51 2017
 OS/Arch:      linux/amd64
 Experimental: false

You mentioned I'm using the classic swarm. How can I make sure I'm using swarm-mode instead?

17.03 is the latest release.
To use swarm-mode: https://docs.docker.com/engine/swarm/#swarm-mode-cli-commands


Inherent method now doc hidden

Doesn't work yet. Details inline.

I'd just move the one #[doc(hidden)] from the impl to the struct and update the expected outputs file, and this is good to merge.

Just to make sure everything is clear, the outputs file I initially committed was already what I was expecting without the false positive. Now that I moved the #[doc(hidden)], the output matches the file.

One check failing. I think I overheard you saying something about an issue with CI?
I'm not sure if this repo enables squash merges so I'll push one more rebasing all the WIPs.

One check failing. I think I overheard you saying something about an issue with CI?
I'm not sure if this repo enables squash merges so I'll push one more rebasing all the WIPs.

I'll resolve the nightly failure shortly, that's on me and not caused by this PR.
We squash-merge PRs by default, so don't worry about rewriting git history any particular way.

I fixed the nightly build and merged main into your PR to make CI all green again.
We'll squash-merge the PR so don't worry about making it a linear history again.

Thanks for putting this together! 🚀


DBG Test Fails

For #8684

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Has a news entry file (remember to thank yourself!).
[x] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[x] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #8698 (c5c7bca) into main (c60dcfd) will increase coverage by 0%.
The diff coverage is 75%.

:exclamation: Current head c5c7bca differs from pull request most recent head 55053c1. Consider uploading reports for the commit 55053c1 to get more accurate results

@@          Coverage Diff          @@
##            main   #8698   +/-   ##
=====================================
  Coverage     71%     71%
=====================================
  Files        384     384
  Lines      24666   24674    +8
  Branches    3794    3795    +1
=====================================
+ Hits       17655   17736   +81
+ Misses      5469    5391   -78
- Partials    1542    1547    +5

Impacted Files
Coverage Δ

...t/datascience/jupyter/interactiveWindowDebugger.ts
63% <75%> (+<1%)
:arrow_up:

...ience/variablesView/variableViewMessageListener.ts
77% <0%> (-23%)
:arrow_down:

...ent/common/application/webviewViews/webviewView.ts
67% <0%> (-11%)
:arrow_down:

src/client/extensionActivation.ts
94% <0%> (-2%)
:arrow_down:

src/client/common/types.ts
100% <0%> (ø)

src/client/datascience/utils.ts
47% <0%> (ø)

src/client/datascience/jupyter/kernels/kernel.ts
75% <0%> (ø)

...ence/notebook/intellisense/intellisenseProvider.ts
80% <0%> (+<1%)
:arrow_up:

...t/datascience/notebook/vscodeNotebookController.ts
80% <0%> (+<1%)
:arrow_up:

src/client/api/pythonApi.ts
65% <0%> (+<1%)
:arrow_up:

... and 28 more

One full green run, going to remove the logging and try a second one.

Looks good on another run, just forgot to add news so adding that and up for review.

Green on this run

(2x) Green. In we go.


bind/bindAll not directly usable with controllerAs syntax / paving the road to angular 2

I'm moving my code base to use the angular "controllerAs" syntax as much as possible which is somewhat paving the path to angular 2.
I was able to completely remove $scope from most of my controllers by defining them as a class properties (TypeScript, but ES6 supports classes as well) containing my view bindings as properties.
Now I would like to bind the datastore to a property of my class which would lead to only use the $scope as service for setting up the watch and in the html I could bind to a property of my controller as all other properties are when using the "controllerAs"-syntax.
Here some insight on the "controllerAs"-syntax: http://toddmotto.com/digging-into-angulars-controller-as-syntax/
As I see it, we would have to enhance the interface of the js-data-angular bind functions especially the expression-parameter.

Does this not work for you?
angular.module('myApp', ['ngRoute', 'js-data'])
  .config(function ($routeProvider) {
    $routeProvider.when('/user/:id', {
      controller: 'UserCtrl',
      controllerAs: 'UserCtrl',
      template: '

',
      resolve: {
        user: function ($route, User) {
          return User.find($route.current.params.id);
        }
      }
    });
  })
  .service('User', function (DS) {
    return DS.defineResource('user');
  })
  .controller('UserCtrl', function ($scope, $routeParams, User) {
    User.bindOne($scope, $routeParams.id, 'UserCtrl.user');
  });

Aah, seems I had another issue with shadowed controllers because I accidentally named two controllers the same when trying to get the binding to work. Thanks :)


[Go][Parquet] Writing a Parquet file from a slice of structs

Describe the usage question you have. Please include as many useful details as  possible.
I'm hoping to get suggestions on the best way to use the library to write a Parquet file given a slice of structs (Golang structs instead of Arrow's array.Struct).
The parquet.NewSchemaFromStruct() function looks like a useful starting point to generate a Parquet schema from a struct.
The pqarrow.NewFileWriter() function is helpful for creating a writer.  And I can see how to convert a Parquet schema to an Arrow schema with the pqarrow.FromParquet() function.
The writer.WriteBuffered() method looks like a convenient way to write an Arrow record.  So the gap is then to get from a slice of structs to the Arrow record.
I was looking for something like array.RecordFromSlice().  The array.RecordFromStructArray() looks useful, but I think I would have to do a fair bit of reflection to work with the struct builder.  It looks like  array.RecordFromJSON() does the same sort of reflection that I would have to do to use the struct builder.
I know it is not efficient, but I see that I can encode my struct slice as JSON and then generate a record from that.  Here is a working test that uses the pqarrow.FileWriter to write a slice of structs as Parquet:
package pqarrow_test

import (
	"bytes"
	"encoding/json"
	"strings"
	"testing"

	"github.com/apache/arrow/go/v14/arrow/array"
	"github.com/apache/arrow/go/v14/arrow/memory"
	"github.com/apache/arrow/go/v14/parquet"
	"github.com/apache/arrow/go/v14/parquet/pqarrow"
	"github.com/apache/arrow/go/v14/parquet/schema"
	"github.com/stretchr/testify/require"
)

func TestFileWriterFromStructSlice(t *testing.T) {
	type Row struct {
		Name  string `parquet:"name=name, logical=String" json:"name"`
		Count int    `parquet:"name=count" json:"count"`
	}

	rows := []*Row{
		{
			Name:  "row-1",
			Count: 42,
		},
		{
			Name:  "row-2",
			Count: 100,
		},
	}

	data, err := json.Marshal(rows)
	require.NoError(t, err)

	parquetSchema, err := schema.NewSchemaFromStruct(rows[0])
	require.NoError(t, err)

	arrowSchema, err := pqarrow.FromParquet(parquetSchema, nil, nil)
	require.NoError(t, err)

	rec, _, err := array.RecordFromJSON(memory.DefaultAllocator, arrowSchema, strings.NewReader(string(data)))
	require.NoError(t, err)

	output := &bytes.Buffer{}

	writer, err := pqarrow.NewFileWriter(arrowSchema, output, parquet.NewWriterProperties(), pqarrow.DefaultWriterProps())
	require.NoError(t, err)

	require.NoError(t, writer.WriteBuffered(rec))
	require.NoError(t, writer.Close())
}

Again, I know there are more efficient ways to go from a slice of structs to a Parquet file.  I'm just looking for advice on the most "ergonomic" way to use this library to do that.  Am I missing a way to construct an Arrow record from a slice of structs?  Or should I not be using the pqarrow package at all to do this?
Component(s)
Go, Parquet

@tschaub I have an initial version of this using reflection here, in case this is helpful:
https://github.com/chelseajonesr/rfarrow
I'm using this for a specific use case so some conversions may not have been tested; feel free to let me know if anything doesn't work.

Looks useful, @chelseajonesr.
My only real current use case has been to create Parquet data for tests.  I've written a test.ParquetFromJSON() function for this purpose.  Maybe also specific to my use case, but this relies on incrementally building up a schema based on a configurable number of input (JSON) rows - to allow for cases where nulls may be present in early rows and the appropriate field type isn't known until reading more data.  So I have an Arrow schema builder for this.  This does't yet cover all the types you might encounter with an arbitrary struct - I'm just adding support for the cases I need to handle.
So while I think it could be useful to have something in this library to generate Arrow data from a slice of structs (to compliment the current parquet.NewSchemaFromStruct() function), I just wanted to say that I don't have an urgent need for this now.  I'll close this unless someone else thinks it is a worthwhile issue to keep open.

I found this issue trying to figure out how to write out a parquet file based on a go struct as well. In my case I already have some data in a arrow data structure which I have been able to write out via the pqarrow package, but then I had a need to also write out some other data where I am not using arrow data structures for the storage. Given the separation between the pqarrow  convenience package and the more general file package I was not sure if the latter aims to be a "general" parquet writer for use even if arrow is not used for the input data.
As a comparison the https://github.com/xitongsys/parquet-go package allows you to basically do:
pw, err := writer.NewParquetWriterFromWriter(..., new(myStruct), ...)
pw.Write(myStructInstance)

I was trying to see if there was something like that present in file but was not able to find it. Of course it would make sense if what I was looking for is out of scope for this project and I should just use another package for that, like the one above.

@eest You're correct that the file package is intended to be a "general" parquet writer for use even if arrow is not used for the input data. The idea was that all "arrow" specific things would be contained in the pqarrow package, while the rest are general parquet packages.
Issues I had encountered with https://github.com/xitongsys/parquet-go was actually the motivating factor which led to me creating the parquet package here, and is why I had created the initial methods that let you create a parquet schema from a struct / vice versa. Having a writer that will allow you to write instances of a struct was out of scope when I was originally building this package, but given the nature of Go it does seem like a reasonable addition to get written. I just never did it because I didn't see any interest in that until now.
If either of you would be willing to put together a PR for adding this functionality, I'd happily help iterate on it with you. Unfortunately I don't have the bandwidth currently to work on adding that functionality myself at this time.

I could also see @chelseajonesr's repo as definitely a good starting point for this kind of functionality and would happily accept a refined version into the Arrow lib itself if a PR is made

@zeroshade Sure, I'd be happy to - will also need to fill in a few data types I left out and expand the tests; should be able to start on that next week.


Tools: Fix Creator tool

Changelog Description
This affects DCC with old Pyblish which will be hopefully soon obsolete.
Additional info
Found during testing Harmony.

Might be good to include in the PR description that this is a PySide6 related fix, right?


Online demo?

Do you have an online demo?

Oh wait, I'm guessing this is it: http://elevatedevdesign.com/blog


Recognized text is not correct and irrelevant

Hi,
I have a wav file and when I try to recognize speech using node.js sdk it shows a different result. Sometimes it recognizes precisely but other times shows very odd words and irrelevant text.
as an example, when the real text should be:

section two you'll hear a tour guide giving a talk about a museum center called riverside industrial village first you have some time to look at questions eleven to thirteen now listen carefully and answer questions eleven to thirteen

it shows:

Shop Hun.Hello hello as I'm not true dat. Boi have my shine shine goosefish can phone.Fish hello how long **** **** **** ****Call from London Luges Hongs Awesome ****

Here is my code

 recognizer.startContinuousRecognitionAsync(function () {}, function (err) {
                    console.trace("err - " + err);
                    cstat = 100;
                    removefile(url);
                    res.json({
                        status: "OK",
                        message: tempText
                    });
                });

                recognizer.canceled = function (s, e) {
                    var str = "(cancel) Reason: " + sdk.CancellationReason[e.reason];
                    if (e.reason === sdk.CancellationReason.Error) {
                        str += ": " + e.errorDetails;
                    }

                    cstat = 100;
                    removefile(url);
                    res.json({
                        status: "OK",
                        message: tempText
                    });
                }

                recognizer.recognized = function (s, e) {
                    // Indicates that recognizable speech was not detected, and that recognition is done.
                    if (e.result.reason === sdk.ResultReason.NoMatch) {
                        var noMatchDetail = sdk.NoMatchDetails.fromResult(e.result);
                        console.log("\r\n(recognized)  Reason: " + sdk.ResultReason[e.result.reason] + " NoMatchReason: " + sdk.NoMatchReason[noMatchDetail.reason]);
                        // tempText += e.result.text;
                    } else {
                        console.log("\r\n(recognized)  Reason: " + sdk.ResultReason[e.result.reason] + " Text: " + e.result.text);
                        tempText += e.result.text;
                    }
                };

                recognizer.recognizing = function (s, e) {
                    //var str = "(recognizing) Reason: " + e.result + "---"+e.privResult;
                    console.log(e);
                };
                recognizer.sessionStopped = function (s, e) {
                    recognizer.stopContinuousRecognitionAsync()
                    var str = "(sessionStopped) SessionId: " + e.sessionId;
                    cstat = 100;
                    removefile(url);
                    res.json({
                        status: "OK",
                        message: tempText
                    });
                    console.log(str);
                };

is it possible to share the wave file so we can reproduces and analyze the problem in house?
thx
Wolfgang

Thanks for your reply.
Here are 2 files.
https://www.dropbox.com/sh/cp71s91com4ggaw/AAAle_OXK5trY_Ed1BAbc7XRa?dl=0

@therowf
we are looking into this ... the preferred bitrate is 256kbps, but unfortunately we still see some issues with one of your files.
...looking into it...

@wolfma61 Thanks

@therowf - these are a couple of interesting issues you discovered ;)
some more investigation is needed - but so far:
there is a problem in the JS SDK with 44khz audio files, that makes your m*81.wav audio file fail using the javascript.sdk (it is really a special file). It works with the native SDK (C#, Python etc). We will fix this in the JS sdk in an upcoming version. Converting to 16khz the file transcribes fine (as expected)
Your m*76.wav file converted to 16khz creates wrong results when converted with Audacity. The desired transcription is generated, but not as the best result. This seems to be a model issue, which is being investigated by the service team.
Wolfgang

this should create good results now


Sticky header tabs - gene function

Type

[ ] Bug fix
[x ] New feature
[ ] Improvement to existing feature

Related JIRA Issue(s)
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-757
Description
Relationship between tabs and header panel to be maintained - only the transcript list and protein panels should scroll behind
Deployment URL
http://sticky-tabs.review.ensembl.org/entity-viewer/homo_sapiens_GCA_000001405_28/gene:ENSG00000139618?view=protein
Views affected
Entity viewer
Possible complications
Nothing at the moment :-)

Tested with ENSG00000109339, which has over 190 transcripts. Looks good.


fix: genesis validators root had an extra new line

was running into the same bug as a few months ago -  https://github.com/flashbots/mev-boost-relay/issues/507

without the tr


Exporting Jupyter to PDF -Plotly does not display

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
In trying to export my notebook to a pdf, I cannot seem to get it to display the output of the graphs I made with plotly. I have found another solution on this website that applies to HTML and ideally should thus apply to PDF exports (here: https://github.com/microsoft/vscode-jupyter/issues/6999), but the suggested line of code that manipulates the plotly renderers does not seem to work; I get an error essentailly that says "DataFrame constructor not properly called!". I thus have no idea how else to manipulate the renederes and get the PDF to show the Plotly objects I have created
VS Code Version
Version: 1.81.1 (user setup) Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794 Date: 2023-08-09T22:22:42.175Z Electron: 22.3.18 ElectronBuildId: 22689846 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: <IP_ADDRESS>-electron.0 OS: Windows_NT x64 10.0.19045
Jupyter Extension Version
N/A
Jupyter logs
Nothing to report here

Coding Language and Runtime Version
Python 3.10.11
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Is there any additional information I should add? I apologize if I have not added enough

I'm sorry for not getting back to you on this, please could you share a simple ipynb file with the output that you have tried to export to PDF.

the suggested line of code that manipulates the plotly renderers does not seem to work; I get an error essentailly that says "DataFrame constructor not properly called!". I thus have no idea how else to manipulate the renederes and get the PDF to show the Plotly objects I have created

Where is this error message displayed? Is this dislayed by nbformat/nbconvert
Please could you share a screen sample or logs where this message is displayed along with the details of the message

I'm not sure if I can share a simplified version of this file and this is the only file on hand that I have created using plotly, but I can show you some screenshots of the output and send you the pdf itself to show you what I am talking about.
The output in the file should consist of several plotly objects. For example, the first such output should be a graph such as this:

When rednering to pdf, I appear to get no errors in rendering, but the pdf displays these outputs as compelltly blank:
8.14.23.pdf
The line of code I was referring to that  Itry to add that gave me an error was the following:
import plotly.express as px
import plotly.io as pio
pio.renderers.default = "notebook"
fig = px.line(...)
fig.show()
These lines of code however produce this error:
ValueError                                Traceback (most recent call last)
Cell In[5], line 8
1 # # This ensures Plotly output works in multiple places:
2 # # plotly_mimetype: VS Code notebook UI
3 # # notebook: "Jupyter: Export to HTML" command in VS Code
4 # # See https://plotly.com/python/renderers/#multiple-renderers
6 pio.renderers.default = "notebook"
----> 8 fig = px.line(...)
9 fig.show()
File ~\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\plotly\express_chart_types.py:264, in line(data_frame, x, y, line_group, color, line_dash, symbol, hover_name, hover_data, custom_data, text, facet_row, facet_col, facet_col_wrap, facet_row_spacing, facet_col_spacing, error_x, error_x_minus, error_y, error_y_minus, animation_frame, animation_group, category_orders, labels, orientation, color_discrete_sequence, color_discrete_map, line_dash_sequence, line_dash_map, symbol_sequence, symbol_map, markers, log_x, log_y, range_x, range_y, line_shape, render_mode, title, template, width, height)
216 def line(
217     data_frame=None,
218     x=None,
(...)
258     height=None,
259 ) -> go.Figure:
260     """
261     In a 2D line plot, each row of data_frame is represented as vertex of
262     a polyline mark in 2D space.
263     """
--> 264     return make_figure(args=locals(), constructor=go.Scatter)
File ~\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\plotly\express_core.py:2003, in make_figure(args, constructor, trace_patch, layout_patch)
2000 layout_patch = layout_patch or {}
2001 apply_default_cascade(args)
-> 2003 args = build_dataframe(args, constructor)
2004 if constructor in [go.Treemap, go.Sunburst, go.Icicle] and args["path"] is not None:
2005     args = process_dataframe_hierarchy(args)
File ~\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\plotly\express_core.py:1313, in build_dataframe(args, constructor)
1311         args["data_frame"] = args["data_frame"].to_pandas()
1312     else:
-> 1313         args["data_frame"] = pd.DataFrame(args["data_frame"])
1314 df_input = args["data_frame"]
1316 # now we handle special cases like wide-mode or x-xor-y specification
1317 # by rearranging args to tee things up for process_args_into_dataframe to work
File ~\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pandas\core\frame.py:781, in DataFrame.init(self, data, index, columns, dtype, copy)
778 # For data is scalar
779 else:
780     if index is None or columns is None:
--> 781         raise ValueError("DataFrame constructor not properly called!")
783     index = ensure_index(index)
784     columns = ensure_index(columns)
ValueError: DataFrame constructor not properly called!
Not really sure where else to go with these lines of code, as I am pretty sure that it is something with the plotly objects themselves that is preventing them from showing on the pdf.

Is this better?
13:10:03.414 [info] End cell 6 execution @<PHONE_NUMBER>413, started @<PHONE_NUMBER>254, elapsed time = 10.159s
13:10:03.414 [warn] Cancel all remaining cells due to cancellation or failure in execution
13:10:03.414 [debug] Cancel pending cells
13:10:03.414 [debug] Cell 6 executed with state Error
13:10:07.453 [info] Loading webview. View is notset
13:10:07.454 [info] Loading web view...
13:10:07.454 [info] Webview panel created.
13:10:08.821 [info] Web view react rendered
13:10:08.883 [debug] Executing silently Code (idle) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info
13:10:08.883 [debug] Executing silently Code (idle) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info
13:10:08.904 [debug] Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info with 1 output(s)
13:10:08.980 [debug] Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info with 1 output(s)

@sadasant
Please can you replicate the issue and then share the logs
Based on the logs, I do not see any export takingplace.

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.


nil pointer dereference in mm-go-irckit.CmdPrivMsg (2)

On 7451baa:
time="2019-05-07T16:18:24+02:00" level=debug msg="B: \"<- PRIVMSG redacted :hey\"\n" module=matterircd
time="2019-05-07T16:18:25+02:00" level=debug msg="flushing buffer: &irc.Message{Prefix:(*irc.Prefix)(nil), Command:\"PRIVMSG\", Params:[]string{\"redacted\"}, Trailing:\"hey\", EmptyTrailing:false}\n" module=matterircd
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x8f008b]

goroutine 19296 [running]:
github.com/42wim/matterircd/mm-go-irckit.CmdPrivMsg(0xb2ba40, 0xc000097520, 0xc0000e5cc0, 0xc02b5cf0e0, 0xc0001dab70, 0xc005193a01)
        /home/dan/.go/src/github.com/42wim/matterircd/mm-go-irckit/server_commands.go:498 +0xbdb
github.com/42wim/matterircd/mm-go-irckit.commands.Run(0xc0001a1aa0, 0xb2ba40, 0xc000097520, 0xc0000e5cc0, 0xc02b5cf0e0, 0x0, 0x0)
        /home/dan/.go/src/github.com/42wim/matterircd/mm-go-irckit/commands.go:57 +0x159
github.com/42wim/matterircd/mm-go-irckit.(*server).handle.func1(0xc000097520, 0xc0000e5cc0, 0xc000010020)
        /home/dan/.go/src/github.com/42wim/matterircd/mm-go-irckit/server.go:365 +0x7d
created by github.com/42wim/matterircd/mm-go-irckit.(*server).handle
        /home/dan/.go/src/github.com/42wim/matterircd/mm-go-irckit/server.go:364 +0x108

This is similar to #247. Not sure if this is the connection being nil, or something else. But presumably the connection can still be closed after the nil check.

Hm yes, but strange that you get hit by this again.
Do you have a flaky mattermost connecion? Or anything else special?

should be fixed


Add is_complete method to ExecutionState

def is_complete(self) -> bool:
    return self == ExecutionState.COMPLETED

Please assign me

Done, Thanks in advance!

Will this issue be hacktoberfest accepted?

I could try and add the repo to the event by tagging it.

I added the hacktoberfest topic to the project description. Should be good to go. Will confirm on my own.

Seems to have worked! Happy hacking.

I'm guess since October is over that you have decided not to do this?


Catch and display KaTeX Errors in Markdown Prose

Fix #603. Fix #571. By adding an error boundary around katex calls.

As an alternative we might just not throw and but display broken latex in red:

Closed in favour of #606.


[$1000] Wrong message when searching invalid phone number

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

Action Performed:

Open search page
Type max length + 1 (15 - (your country code length) + 1) of phone number
Notice it shows "No results found" instead of "Please enter a valid phone number..."

Expected Result:
The message should show "Please enter a valid phone number..."
Actual Result:
The message show "No result found"
Workaround:
unknown
Platforms:

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

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.2.77-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Expensify/Expensify Issue URL:
Issue reported by: @bernhardoj
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1677516260452839
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ebc731c72a7371c6
Upwork Job ID:<PHONE_NUMBER>584202240
Last Price Increase: 2023-03-08

Triggered auto assignment to @strepanier03 (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

This is not a bug because of the way we validate phone numbers. We validate via Twilio, and we don't know it's not a valid phone number until after the chat is started.
Some additional context can be found here. And validating phone numbers has been added to the Testing Guidelines for QA doc here.

Chatting about this one internally.

I can recreate this behavior.
At 15 digits I see the No Result Found message, at 16+ digits I see "Please enter a valid phone number" message.
While doing some Googling, it appears there are countries which have 15 digits including country code and that 15 digits is the maximum number. So it makes sense to me that we don't show the valid message until you hit 16 digits.
I raised it in the OG bug report in Slack and pinged Bug Zero for some extra thoughts.

Sending on for some expert opinions, I'm still a little torn on the behavior here and what is expected.

Job added to Upwork: https://www.upwork.com/jobs/~01ebc731c72a7371c6

Current assignee @strepanier03 is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (External)

Triggered auto assignment to @deetergp (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Adding my proposal from the discussion.
Proposal
Please re-state the problem that we are trying to solve in this issue.
"No result found" message shown instead of "Please enter a valid phone number..." when we are searching for an invalid phone number (length > 15, includes the country code)
What is the root cause of that problem?
When we are searching a user with phone number, it will append a country code if it does not exist.
https://github.com/Expensify/App/blob/84e37e63f7f29762269af9be3b54662c36dcfa5b/src/libs/OptionsListUtils.js#L579-L583
However, we don't do the same thing when getting the correct error message.
https://github.com/Expensify/App/blob/84e37e63f7f29762269af9be3b54662c36dcfa5b/src/libs/OptionsListUtils.js#L752-L772
What changes do you think we should make in order to solve the problem?

Create a common function to append a country (use the logic from getOptions) code to a phone number to unify the logic and use the new function to both getHeaderMessage and getOptions.

@rushatgabhane @deetergp - Have you had a chance to look at the proposal above?

@deetergp - If the proposal for Bernhard looks good feel free to assign them to the GH or leave a comment for me and I can do it. Thanks!

I agree with @rushatgabhane, let's go with @bernhardoj's proposal 👍

📣 @bernhardoj You have been assigned to this job by @deetergp!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

@deetergp @strepanier03 @rushatgabhane @bernhardoj this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

PR is ready for review.
cc: @rushatgabhane

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.2.87-1 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/15976

If no regressions arise, payment will be issued on 2023-03-28. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@rushatgabhane / @deetergp] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@rushatgabhane / @deetergp] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@rushatgabhane / @deetergp] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@strepanier03] Determine if we should create a regression test for the bug.
[ ] [@rushatgabhane] If we decide to create a regression test for the bug, please propose the regression test steps to the appropriate location to ensure the same bug will not reach production again.
[ ] [@strepanier03] Review the proposed regression test steps and location.
[ ] [@strepanier03] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Looks like something related to react-navigation may have been mentioned in this issue discussion.
As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.
Feel free to drop a note in #expensify-open-source with any questions.

I'm relatively certain this has behaved like this since the app's inception, so there wasn't a PR that introduced it. Do we feel we need a regression test for this going forward? I'm pretty on the fence about it and am happy to be persuaded to jump either way, but all things being equal, I'll always favor :donothing:.

The issue comes from this PR https://github.com/Expensify/App/pull/15122 where we append the phone number with country code only in OptionsListUtils.getOptions, but not with OptionsListUtils.getHeaderMessage.

Okay, I stand corrected 😅  Thanks @bernhardoj! Do we think regression steps are necessary? I don't feel they are, but am willing to be convinced otherwise.

I'm also on the fence if a new regression test is necessary. I lean towards not doing a new reg test for this one.

I've hired both @bernhardoj and @rushatgabhane to the job. I will pay the bonuses in that job as well so $1750 for Berhard and $1500 for Rushat.

Paid out both @bernhardoj and @rushatgabhane.
Finished the BZ checklist and am closing the GH out. Well done everyone 👏


Translation for several board and some minor fix

Fix and tweaked translation for LicheePi4A, LicheeCluster4A and LicheeConsole4A.

Fix some link and format issue

Mayby ready? I tried to correct where I can find out.

Mayby ready? I tried to correct where I can find out.

Has been busy on other stuff these days. Will review later.


Use TFS 2015 object model instead of TFS 2013 ones

I'd like to avoid installing TFS 2013 object model on TFS 2015/2017 on prem. Could you please upgrade the plugin?

#48 is ongoing therefore.

@sorgeas Would you like to test a snapshot version?

I've setup the 2.3-SNAPSHOT on SonarQube <IP_ADDRESS>370 to communicate with an onprem TFS 2018.
I'm getting the following error:
ERROR: SCM-TFVC: Unable to annotate the project which raised the following authentication exception: TF30063: You are not authorized to access https://mytfs/tfs/projectcoll.
Could you please let me know if this version also supports TFS 2018? Should I use my domain user & password or rather a PAT?

We are using always PAT to be configured at https://[...]/admin/settings?category=scm.
I'm glad to hear you succeeded.
So, this feature will be included in next release.


[FEAT] Support Cloudflare Pages on Free Plan, using NextJS on Refine

Is your feature request related to a problem? Please describe.
Basically, when you create a refine app, and try to publish it on Cloudflare Pages on Free Plan, you'll get this: Error: Failed to publish your Function. Got error: Your Functions script is over the 1 MiB size limit (workers.api.error.script_too_large)
My CRUD app that uses NextJS and Appwrite does not go over the 1 MiB size limit, so I am not sure if this is more of a Refine app thing?
Describe alternatives you've considered
No response
Additional context
No response
Describe the thing to improve
It seems that the Refine app has a size over 1 MiB after compression, is there a way to minimize this? Especially for a barebones refine project...?

Hey @jackprogramsjp can you analyze your app with bundle analyzer and let us know the results?


History is sorted from latest to oldest

A small UX stuff, usually we need the latest history entries on top. So we can avoid the high amounts of scroll

Hey @AndrewBastin,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: f6bb16e0-c4e2-11e9-8712-75d78f9b457f

Hey @AndrewBastin,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: f7d33da0-c4e2-11e9-8712-75d78f9b457f


async-17: MiniMap WIP

Description
WIP to get MiniMap rendering tile coverage in real-time.

This GIF shows the MiniMap now displays only the currently visible tiles. Not we are drawing all the tiles in the main window. The next step is drawing only the visible tiles. But the MiniMap shows we have that information.

This PR Is very unstable right now, with crashes. Still figuring them out.

Note: The PR Is very unstable right now, with crashes. Not sure what's causing them yet.

Wow, I love the minimap!! So cool :-)

Now the minimap shows the actual view bounds. Things are still unstable I think it's from drawing too many new ImageVisuals in one frame. Will try to pace it out a few per frame, which we need to do anyway. If that doesn't help might be forced to do the single-visual TiledImageVisuals sooner rather than later.

Wow, I love the minimap so much, definitely new favourite feature!!

This is so cool, @pwinston !

I added some more octree info on the right. And in the octree level dropdown you can pick AUTO, which will be the normal mode. But it's not hooked up yet:

I marked this ready for review. It's 100% experimental except for a 1 line perf time change to print less digits (print up to microseconds only).

I want to clear the decks for async-18 because I think it will have some non-experimental changes.
We needVispyTiledImageLayer to update itself as the camera moves. This is unlike normal visuals. With a normal visual we throw it into the scene once, and then we let the camera move around and draw that fixed things from different view.
Instead VispyTiledImageLayer needs to shuffle tiles in/out as the camera moves. So it's not one fixed thing getting drawn from multiple views. It kind of morphs itself based on where the camera is.
I was thinking just pass the camera into VispyTiledImageLayer. Probably into VispyBaseLayer because where we create these layers in create_vispy_visual() we create them uniformally.
But maybe there is some other way to get the camera into VispyTiledImageLayer or else have some external thing receive the camera events and then call into VispyTiledImageLayer? Not positiive.

Okay I'm moving on to async-18.


Publish test results even if build is canceled

If build is cancelled due to agent timeout, some tests results may have already been generated and should still be published

Build of "java - core - ci": https://dev.azure.com/azure-sdk/public/_build/results?buildId=209341&view=results

/azp run java - appconfiguration - tests

/azp run java - core - ci

/azp run java - core - ci

/azp run java - appconfiguration - tests

Build of "java - core - ci": https://dev.azure.com/azure-sdk/public/_build/results?buildId=209341&view=results

/azp run java - appconfiguration - tests


Fix bug in win?/3

Unfortunately found a bug in the previous version. It makes an incorrect assumption that the first card’s value is less than that of the second card. The new version uses Enum.sort/1 to not rely on that assumption being true.

Appreciated!! 🤗


Add security header authorizers

See: https://github.com/Jasig/cas-server-security-filter/pull/18

Perfect!

PR: https://github.com/pac4j/pac4j/pull/336


Add support for Heat Mode detection for Heat Pumps - Fixes #26547

Since the ecobee component started to dynamically set the supported HVAC modes based on querying the device a few releases ago, users with Heat Pumps noticed that the Heat mode was no longer offered as an option by HA. Some of us did not actually notice until the summer was over :). This commit fixes that.
For heatpumps, ecobee returns:
'coolStages': 1,
'heatStages': 0,
'hasHeatPump': True,
Fix tested on HA 100.1 and 100.3
Fixes bug https://github.com/home-assistant/home-assistant/issues/26547
Breaking Change:

Description:
Related issue (if applicable): fixes #
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @arigit,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @arigit,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

CLA just signed

Looks fairly straightforward to me, but I don’t have a heat pump to test!

Looks fairly straightforward to me, but I don’t have a heat pump to test!

In the related bug we have at least two different users that confirmed the API response includes
'heatStages': 0,
'hasHeatPump': True,
i.e. no heatStages + a heat pump flag.

@marthoc can you confirm that this change in support of heatpumps does not break your setup (which does not seem to have one)?

@arigit can confirm. Just pulled and ran your branch with no issues. It would appear that the hasHeatPump key is present in my API response even though I don't have a heat pump so no need to catch a KeyError.

@marthoc done - reformatted with black and added a second commit. checkformat now passes.

As a heat pump owner, I can confirm this also fix the issue for me. I can now see and use the heat mode. Thanks!

Looks good to me!


Investigate our performance on https://github.com/the-benchmarker/web-frameworks

It has been reported in our Slack that we are not performing well when running this benchmark, in comparison to other Swift frameworks.
As we are not familiar with this benchmark we will take a look.

The Kitura implementation doesn't seem to include the NIO mode. May be we should add that too.

David Jones and I investigated yesterday and he immediately noticed that Kitura is running inside an Ubuntu 14.04 Docker container, which is a performance penalty compared to running on 16.04 or 18.04 (related to an old + poorly performing libicu on that old distro)
Unfortunately, our generated projects specify ibmcom/swift-ubuntu:5.0.1 rather than using the official swift:5.0.1 image.  The former is based on 14.04, which is something that David has raised that we need to address.  Long-term we believe we will be moving Kitura projects to use the official Swift images.
We can change
FROM: ibmcom/swift-ubuntu:5.0.1
to
RUN apt-get update && apt-get install -y openssl-dev libcurl4-openssl-dev

after which we are ~35% faster.
Here's a set of results which David ran locally (bare-metal Ubuntu 16.04 server, he modified the client/docker commands to run on 8 CPUs equivalent to the benchmark author's setup):

Language (Runtime)
Framework (Middleware)
Requests / s
Throughput

swift (4.2)
[perfect] (3.1)
142786.33
134.38 MB

swift (5.0)
[kitura-1804] (2.7)
100213.67
186.64 MB

swift (5.0)
[kitura-1804] (2.6)
99507.67
185.31 MB

swift (5.0)
[vapor] (3.3)
93971.33
157.05 MB

swift (5.0)
[kitura-1604] (2.7)
89525.33
166.74 MB

swift (4.2)
[kitura-1604] (2.7)
80761.00
150.42 MB

swift (5.0)
[kitura-1404] (2.6)
74396.33
138.55 MB

swift (5.0)
[kitura-nio-1804] (2.7)
73765.33
139.60 MB

swift (5.0)
[kitura-1404] (2.7)
73496.33
136.87 MB

swift (5.0)
[kitura-nio] (2.7)
60809.00
115.02 MB

... we also don't see the regression between Kitura 2.6 and Kitura 2.7.  They are about equal in performance.
David has submitted a PR to update the Kitura dockerfiles to 18.04:
FYI, https://github.com/the-benchmarker/web-frameworks/pull/1346
At this point we're going to close off this issue and have raised two other separate issues covering two other items which we noticed whilst running this benchmark:

#1452
https://github.com/IBM-Swift/Kitura-NIO/issues/207

FYI, I am working on running this on production-ready IaaS (instead of docker) on https://github.com/the-benchmarker/web-frameworks/pull/632


Change pfSimpleFilter directive to use two sub-component directives

pfSimpleFilter directive needs to be split up so that the components for the fields area, and the components for the current results and active filters area can be placed separately on the toolbar or where ever an application would like them. Currently, this one directive takes up the entire toolbar area and won't allow (easily) for additional toolbar components.

LGTM


Changing default search engine?

Is it possible to override the search engine currently used with one of our own choosing?

It is.
You can clone yourself the mod_strip and change the lib/box.js file on line ~224 and change the submit_url to an engine you want to use. P.e. for duckduckgo it would look like this afterwards:
else {
submit_url = 'https://www.duckduckgo.com/?' +
                     'q=' + escape(data.input) + '&' +
                     'ie=UTF-8';
}

Then use your local mod_strip and when you then type something in the searchbox, it will be using your favorite search engine.

I was digging through the source files before asking but didn't find where this was as I still don't know the folder structure and how it works. Thank you @Seonnyn !


Updated new features

Breaking changes Re-organise configuration structures
Apply chase-stop-loss-limit order for buy signal as well
Added more candle periods - 1m, 3m and 5m
Allow to disable local tunnel

Codecov Report

Merging #37 (30de387) into master (60643b2) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #37   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           22        37   +15
  Lines          756       746   -10
  Branches        97        79   -18
=========================================
- Hits           756       746   -10

Impacted Files
Coverage Δ

app/helpers/logger.js
100.00% <ø> (ø)

app/websocket/handlers/symbol-update.js
100.00% <ø> (ø)

app/jobs/index.js
100.00% <100.00%> (ø)

app/jobs/trailingTrade.js
100.00% <100.00%> (ø)

app/jobs/trailingTrade/common.js
100.00% <100.00%> (ø)

app/jobs/trailingTrade/configuration.js
100.00% <100.00%> (ø)

app/jobs/trailingTrade/step/determine-action.js
100.00% <100.00%> (ø)

app/jobs/trailingTrade/step/get-account-info.js
100.00% <100.00%> (ø)

...pp/jobs/trailingTrade/step/get-exchange-symbols.js
100.00% <100.00%> (ø)

...obs/trailingTrade/step/get-global-configuration.js
100.00% <100.00%> (ø)

... and 33 more

Continue to review full report at Codecov.

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


IsolatedStorageException

IsolatedStorageException thrown on CreateFile if path contains a Directory that does not exist.
Summary
Isolated storage exception example, and doc change
Fixes #Issue_Number (if available)

connected to
https://github.com/dotnet/docs/pull/18769

Thanks!


Testserver for the exampe app

@mattab Is it possible to get a test server/instance of piwik we can add as target for the example app?
I think the old one was supplied by @dotsbb and is no longer available.

@mattab Can we use http://demo.piwik.org/ for this purpose? Could You create a new site there?

Hi @d4rken @dotsbb - Sure, I've just sent you the credentials. Happy testing!

@dotsbb your CC email does not work anymore, can you please email me from your private email? i'll send you credentials


Fix plots not showing on deployed dash

This PR tries to solve the issue with plotly plots not being shown on the deployed dash. It uses R plotly instead of Python one.

This is the look locally (trying to match colours in https://github.com/os-maintenance/arrowdash/pull/18

@thisisnic if you are ok with how this looks and the R code in this PR, I would merge to see if it actually fixes the issue.


Allow for inactive port

@ibuildthecloud @alena1108

LGTM, but there is a bug in lb_service test that is fixed as a part of pending https://github.com/rancherio/cattle/pull/391. By now you can just mark that test as skipped; and I will re-enable it once my stuff gets merged.


Create page and description for Flock print.

Create page and description for Flock print.

[x] Add good SEO description
[x] Add good quality image
[x] Add linking
[x] Add price table

:)

Flock printing, uses high quality matte polyurethane film with thermally activated adhesive, our prints are characterized by deep texture and color intensity.The elasticity and softness of the material make them pleasant to the touch and non-reflective. Ideal for work clothes, sports and leisure wear and decorative elements on textiles. With the ability to be used on a variety of materials, including cotton, polyester and blends, our flock prints will meet every expectation. Trust professionalism and choose quality, choose flock filmhere you can easily calculate the price: Calculate!here is the price table: Pricing Table


JSONArray构造方法中，由null List会引发的NPE问题

在创建JSONArray时，如果传入是null类型的List，JSONArray会被正常创建，但在调用add方法时会抛出NullPointException，所以我在创建JSONArray时，添加了List是否等于null的判断。

Codecov Report

Merging #2815 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master    #2815      +/-   ##
============================================
- Coverage     80.14%   80.11%   -0.03%
+ Complexity     7146     7139       -7
============================================
  Files           145      145
  Lines         26964    26966       +2
  Branches       6449     6450       +1
============================================
- Hits          21609    21604       -5
- Misses         3495     3497       +2
- Partials       1860     1865       +5

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/com/alibaba/fastjson/JSONArray.java
89.01% <0%> (-1.05%)
81 <0> (ø)

...com/alibaba/fastjson/serializer/SerialContext.java
72.91% <0%> (-4.17%)
19% <0%> (ø)

...main/java/com/alibaba/fastjson/util/FieldInfo.java
86.2% <0%> (-0.35%)
90% <0%> (-1%)

...n/java/com/alibaba/fastjson/util/JavaBeanInfo.java
87.6% <0%> (-0.17%)
206% <0%> (-2%)

...java/com/alibaba/fastjson/parser/ParserConfig.java
83.41% <0%> (-0.17%)
206% <0%> (-1%)

.../java/com/alibaba/fastjson/parser/JSONScanner.java
76.11% <0%> (-0.17%)
506% <0%> (-2%)

...ava/com/alibaba/fastjson/serializer/DateCodec.java
88.82% <0%> (+1.76%)
41% <0%> (+1%)
: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 7f41acc...57c9008. Read the comment docs.


Aggregating the output parameters of parallel steps

Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST
When we use the loop feature:
https://github.com/argoproj/argo/blob/master/examples/loops-param-result.yaml
Or even when we run steps in parallel,
It does not seem possible to aggregate the outputs of all the steps in an array to provide to a next step.
For instance, imagine the following case in an ML context:

The first step of the workflow outputs that a model must be computed with parameter values X=3, X=4 and X=5.
The workflows then starts 3 branches: one branch computing a model for X=3, one branch computing a model for X=4, one branch computing a model for X=5.
The final step of each branch outputs the accuracy of the model (11 for branch 1, 22 for branch 2, 33 for branch 3) and the location of the model (gcs://11, gcs://22, gcs://33)
We then would like to execute a next step that would get as an input

[{X=11, location=gcs://11}, {X=22, location=gcs://22}, {X=33, location=gcs://33},]
The next step can then select the most accurate model and produce this result as an output.
The next step can then deploy this model to a server that can then server predictions.
Would it be possible to support something like this?

@qimingj

I agree some sort of aggregation is needed in the DSL. We also need to support output artifacts as well as parameters (see #854). I'm thinking the controller should provide some new variables, which would be json list of what the variable is referring to. Consider the following step:
    steps:
    - - name: test-linux
        template: cat-os-release
        arguments:
          parameters:
          - name: image
            value: "{{item.image}}"
          - name: tag
            value: "{{item.tag}}"
        withItems:
        - { image: 'debian', tag: '9.1' }
        - { image: 'debian', tag: '8.9' }
        - { image: 'alpine', tag: '3.6' }
        - { image: 'ubuntu', tag: '17.10' }

I am proposing to make make steps.test-linux.outputs.parameters return a json list containing all output parameters from the expanded steps. A similar thing could be done for output artifacts (e.g. steps.test-linux.outputs.artifacts.

@jessesuen I really like that Idea, and I think it would easily address #854 as well

@jessesuen how would you provide paths for a list of artifacts? Each artifact loaded into a step requires a full path, do you think the paths can be generated using a variable to an iterator?
Maybe something like this?
input:
artifacts:
- name: myfiles
- path: /tmp/file_{{item.index}}

@javierbq, yes -- I think something like what you are proposing is needed. I filed #934 to handle artifacts separately, since I have a fix coming for parameters.

Is it somehow possible to access the aggregated output parameters by steps within the initial loop? i want to interrogate the status of other steps in the loop at the time any given step in the loop starts