ReferenceError: setTimeout is not defined

Here is my code
require 'mini_racer'
ctx = MiniRacer::Context.new
ctx.eval('setTimeout(function(){console.log(1)}, 1000)')

The error info is
Traceback (most recent call last):
	7: from 1.rb:3:in `<main>'
	6: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:176:in `eval'
	5: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:176:in `synchronize'
	4: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:178:in `block in eval'
	3: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:264:in `timeout'
	2: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:179:in `block (2 levels) in eval'
	1: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:179:in `eval_unsafe'
JavaScript at <anonymous>:1:1: ReferenceError: setTimeout is not defined (MiniRacer::RuntimeError)

I tried in CentOS Linux release 7.5.1804 and Ubuntu 16.04.5 LTS

setTimeout and setInterval are not defined by v8, the platform needs to
provide them. if you want timeout you are going to have to implement in
Ruby and attach the method.
On Fri, Mar 29, 2019 at 8:28 PM hex0wn<EMAIL_ADDRESS>wrote:

Here is my code
require 'mini_racer'
ctx = MiniRacer::Context.new
ctx.eval('setTimeout(function(){console.log(1)}, 1000)')
The error info is
Traceback (most recent call last):
7: from 1.rb:3:in <main>' 	6: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:176:in eval'
5: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:176:in synchronize' 	4: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:178:in block in eval'
3: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:264:in timeout' 	2: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:179:in block (2 levels) in eval'
1: from /usr/local/rvm/gems/ruby-2.5.3/gems/mini_racer-0.2.4/lib/mini_racer.rb:179:in `eval_unsafe'
JavaScript at :1:1: ReferenceError: setTimeout is not defined (MiniRacer::RuntimeError)
I tried in CentOS Linux release 7.5.1804 and Ubuntu 16.04.5 LTS
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/discourse/mini_racer/issues/135, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAUXantwBeHkJ9gPOVjGkUW1WFIAVJfks5vbdUKgaJpZM4cR61g
.

I was thinking it might be useful to attach an (optional) event loop to a mini_racer context. Some libs require and event loop, so for now I just polyfill it like:
// Pseudo since I'm on phone
function setTimeout(func) { func() }

Obvious correctness issues there, but "It Works" ™.
There will be some complexity ensuring event loop is properly shut down and before exit, but it night be a worthwhile edition.

Technically this is doable today I have a reasonably efficient implementation of timer thread at:
https://github.com/SamSaffron/message_bus/blob/master/lib/message_bus/timer_thread.rb
It would be pretty straight forward to glue it on by attaching stuff. It is a bit tricky though getting full details of the func being called out of the boundary, so you would may need some sort of weakmap or something.


IPFS dataset

To be able to use the IPFS dataset we need to translate it in a way that can be used with our simulation. To this end, I extract all the CIDs, and its frequency. The bytes_returned shows the content size. In some cases, the bytes_returned differs for the same CID, so I pick the average.

This dataset is only from one gateway over 24 hours.


Add guideline to last step of the <Steps> component

Description
The initial design of the <Steps> component does not include a guideline for the last step:

Based on some feedback, this PR introduces a guideline for the last step to help visualizing the context of the last step, specially for long last steps.
Different approaches are possible:

Using the existing guideline
Fading the guideline linearly
Fading the guideline in the last 5rem

This PR uses the third approach, fading the guideline near the end of the last step.
I'm totally open to any feedback regarding the approach or values used.
Remaining tasks

[ ] Remove the docs/src/content/docs/guides/steps.mdx file

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
guides/steps.mdx
Source added, will be tracked.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Really like this! The only thing I'm not a fan of are the one-line last steps. I would prefer no trailing line if only a single line, but I can understand that may be tricky (if even possible at all) to do with text wrapping (unless using some magic-numbers).

Fade-outs are often used to imply that content continues off-screen or is truncated. When I see the guideline fade out it makes me think that there are additional steps hidden from view.
I think the existing design is preferable, even for long final steps. The content is indented, which communicates its hierarchy and relation to the number. No extra visuals needed.

The only thing I'm not a fan of are the one-line last steps.

This is indeed something I noticed as well but did not bother me. I'll try to see if there is some kind of trick we can use but I cannot think of an obvious one right now.

The content is indented, which communicates its hierarchy and relation to the number. No extra visuals needed.

I would guess this highly depends on the content and your screen size. If you're in the middle of a relatively long step, or on a phone or small window and cannot see the previous/next step number indicator, you have no point of reference to know the content you're seeing is indented. And this seems to be the case for most of the negative feedback I got on this. Definitely not saying this solution is the proper one ofc (it's just the only one we thought of so far), but I think there may be some room for improvement on our side to address the issue.

I wonder if actually the simpler solid line is the better choice given this?

I think this is perfectly fine too (it was one of the 3 suggested approaches in the original post) and it also addresses the issue. I updated the PR to remove the gradient.
As we discussed, the one-line case is indeed tricky and inconsistent and I don't think there is even an upcoming CSS feature that would allow us to address this in a more elegant/reliable way.


About Slice Layer

Hello,
I have a problem related to slice layer .
My model is like this
(I want to slice the ch dimension, and then concatenate them, i.e.,
I set axis attribute as 1 in slice layer in an onnx file)

I add a slice layer after the first conv layer
but while converting this model to tflite model, it will show that the input of concat layer  is mismatch
I print the shape of slice layer like this:

For the upper part, it is normal (slice input to two tensors with 4 channels and 12 channels),
but for lower part, it slices the wrong dimension
I use the setting of change_ordering=True with onnx2keras==0.0.17
Do you have any suggestion ? Thanks a lot :)

Hello.
I encountered a same issue, and the cause seems to be in tf.nn.strided_slice() according to my test.
I fixed it and you can tell by looking at the PR #55 .
Best regards.


ARM images

What did you do?
I tried to install the operator on an RaspberryPi 4 cluster (k3s). However, its doesn't seem that ARM variants of the operator are available (as I get an exec error, so it doesn't look that manifests for ARM images are deployed).
Did you expect to see some different?
'would love to use the operator on an ARM architecture.
Environment
K3s v1.17.0+k3s.1

Prometheus Operator version: v0.34.0
sha256:9fac37195cffbddb2762245033e36f40a33f7e127de0c1933bc4164727f4abf8

Kubernetes version information:

kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.1", GitCommit:"d647ddbd755faf07169599a625faf302ffc34458", GitTreeState:"clean", BuildDate:"2019-10-02T23:49:20Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0+k3s.1", GitCommit:"0f644650f5d8e9f091629f860b342f221c46f6d7", GitTreeState:"clean", BuildDate:"2020-01-06T23:20:30Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/arm"}

Hey, for my talk during KubeCon I recently ported (compiled) this Operator for ARM. I have a local branch that I never got to push publicly. Let me do that right. :blush:
Thanks for reminding me by opening this issue. :sweat_smile:

I created an initial PR at #2947 :blush:

@metalmatze cool, thanks ! Looking forward to try it out ...

It also looks like quay.io does not support docker manifest lists (aka multi-arch) so that you cannot push one image that works on multiple architectures. So in order to make multi arch work in quay.io I think you need to maintain multiple separate images.
E.g.
$ docker manifest inspect quay.io/coreos/prometheus-operator:latest
unsupported manifest media type and no default available: application/vnd.docker.distribution.manifest.v1+prettyjws

while the same against e.g nginx gives the following:
$ docker manifest inspect nginx
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 948,
         "digest": "sha256:89a42c3ba15f09a3fbe39856bddacdf9e94cd03df7403cad4fc105088e268fc9",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      },
[...]

Also when pulling from quay.io I get this warning:
[DEPRECATION NOTICE] registry v2 schema1 support will be removed in an upcoming release. Please contact admins of the quay.io registry NOW to avoid future disruption.

The multi-stage build from https://github.com/coreos/prometheus-operator/pull/2947#issuecomment-573419338 with quay.io and I get the following error:
#20 pushing layers 20.0s done
#20 pushing manifest for quay.io/rhuss/prometheus-operator:v0.34.0
#20 pushing manifest for quay.io/rhuss/prometheus-operator:v0.34.0 0.2s done
#20 ERROR: failed commit on ref "manifest-sha256:706572e8d8a60eec845bb3823ad885ba007da9f1fd116602a4fd5ce6ee42fcf1": unexpected status: 415 Unsupported Media Type
------
 > exporting to image:
------
failed to solve: rpc error: code = Unknown desc = failed commit on ref "manifest-sha256:706572e8d8a60eec845bb3823ad885ba007da9f1fd116602a4fd5ce6ee42fcf1": unexpected status: 415 Unsupported Media Type

So at least buildkit doesn't seem to be compatible with quay.io

The operator runs now smoothly on ARM, but unfortunately the Prometheus images from quay are not multi-arch, too. I switched over to the official Prometheus image hosted on Docker, but then I have the issue that the sidecars (configmap reloader) are not mulitarch either, and there is no way to change those images in a Prometheus installation.
That's my Prometheus CR with which I tried:
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  name: prometheus
spec:
  serviceAccountName: prometheus
  baseImage: prom/prometheus
  version: v2.15.2
  containers: []

but the sidecars get still in injected.
Any ideas how to move on from here ?

Does anyone knows where I find the source to quay.io/coreos/prometheus-config-reloader:v0.34.0 and quay.io/coreos/configmap-reload:v0.0.1 ?
Interestingly I can't find some on the web interface of quay.io (no coreos images at all). Seems to be coming from a private repo ?

Ok, found  https://github.com/jimmidyson/configmap-reload by @jimmidyson (oh my, should have known that ;-), which also has nice ARM support. BTW, also a very good blueprint for howto generate ARM images via circleci.

With
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  name: prometheus
spec:
  serviceAccountName: prometheus
  baseImage: prom/prometheus
  version: v2.15.2
  nodeSelector:
    tichny.org/local-storage-size: "big"
  containers:
  - name: prometheus-config-reloader
    image: maxromanovsky/prometheus-config-reloader:v0.34.0
  - name: rules-configmap-reloader
    image: jimmidyson/configmap-reload:v0.3.0
  storage:
    volumeClaimTemplate:
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 100Gi

I got Prometheus up and running.
Of course, it would be awesome if we could get Quay Prometheus images to be also multi-arch. But I have no idea how to contribute (as there is no indication where the Quay Prometheus source are)

cc @simonpasquier @pgier regarding prometheus’ docker Setup.

Regarding configmap-reloaded, this PR should simplify things: https://github.com/coreos/prometheus-operator/pull/2952

Of course, it would be awesome if we could get Quay Prometheus images to be also multi-arch

They should be (since https://github.com/prometheus/prometheus/pull/5031):

What's not working exactly?

Yeah. Prometheus and Alertmanager worked just fine without doing anything about it for me in November :blush:

What's not working exactly?

See https://github.com/coreos/prometheus-operator/issues/2946#issuecomment-573421272
I.e. using buildkit to push to quay.io doesn't work. But this could be more a buildkit interoperability issue, too. Maybe the way how Docker.io and Quay.io deal with publishing multi-arch images are just different.

We (Prometheus/Alertmanager) are successfully pushing images to Docker Hub and quay.io. On Quay you need to create the arch-specific repositories (e.g. https://quay.io/repository/prometheus/prometheus-linux-arm64) in advance while Docker Hub auto-creates them for you.
You can have a look at the following targets to see how we do it:
https://github.com/prometheus/prometheus/blob/aad8f89ecb2b6eade8877fb94742dc9a1773051a/Makefile.common#L211-L233

If I got the situation correctly, the prometheus/alertmanager images on quay.io are already multi-arch for ARM, only the prometheus-operator itself is missing, right?

If I got the situation correctly, the prometheus/alertmanager images on quay.io are already multi-arch for ARM, only the prometheus-operator itself is missing, right?

Correct. :)

Apparently quay does support multi-arch images, as of May 2019: https://thenewstack.io/red-hats-quay-3-container-supports-multiple-architectures/

Any updates on this or the accompanying pr? I would love to be able to run the prometheus operator on a raspberry pi.

Looks like mutli-arch was added to the Dockerfile/Makefile in #3035.
Unfortunately, it looks like building multi-arch is alpha in Travis CI: https://docs.travis-ci.com/user/multi-cpu-architectures/

For people that want arm support I have made https://github.com/rmb938/prometheus-operator-multi-arch
It uses github actions and clones this repo to do build and publish the image, no extra code needed. If you don't trust a random persons images (I don't blame you) feel free to fork my repo and set it up yourself.

Could you make a PR for this repo to do the same?

I can once https://github.com/coreos/prometheus-operator/issues/3162 is fixed. How I'm doing it is bypassing the makefile and I doubt the maintainers will be happy if I do that


[question] gota explosion

How to make explosions from viruses in gota(gota the explosion 1 large cell and 4 same small cell)
Well, or just how to make the explosion to a small cell was of equal mass
please respond with a normal response... and then you don't answer people clear answers and closed questions  I know that this does not apply to the project, but it is the question :) if it is the duplicate that write number of questions where this question is written

Also I am really wanting this, this has been duplicated I think.

the question number with the answer....

#332

ok but how to make the explosion, there were 4 SAME cells. Write what numbers should be inserted in virus.js to 4 SAME cells. I already suffer with these explosions 3 months maybe more (I found good values for explosions in vanilla

idk then. i knew what u meant in the first place, but idk how to do it myself.

Could you please give an example, thanks :)

@FantasyIsBae He already did.

idk why the 4 cells werent at the same angle, meh mustve messed up for me when i was screenshotting them

Refer to this answer, I myself don't know how the physics of gota work, so I cannot really assist you here.


Boruvka's Algorithm in C, C++, Java & Python

Is your feature request related to a problem? Please describe.
It is one of the oldest minimum spanning tree algorithms. On record, Boruvka came up in 1926. It was published as a method of constructing an efficient electricity network.
Describe the solution you'd like
1) Input is a connected, weighted and un-directed graph.
2) Initialize all vertices as individual components (or sets).
3) Initialize MST as empty.
4) While there are more than one components, do following
   for each component.
      a)  Find the closest weight edge that connects this
          component to any other component.
      b)  Add this closest edge to MST if not already added.
5) Return MST.

Additional context

I can work on this issue please assign it to me.

@Kumar-laxmi please assign it to me

Assigned!
@harshitaaa8 : C, C++, Java & Python

i would like to work on this issue , please assign it to me .


Chapter and Verse Navigation

Did the functionality for Chapter and Verse Navigation:
-1# Chapter Selector after book selection

2# Chapter selection popup on chapter number on app bar
3# Verse selector after chapter number

Not sure if responsible for UI aspect:
Chapter selection popup still has the "clickable" pointer on it for #2
You can still see verse and chapter for both #1 and #3

@Jason-Lopez8: I am sorry that I didn't realize that this PR was ready for review.
I have looked over the following 4 settings and I believe these are not the correct changes. Also, there have been significant changes in BookSelector and you will need to start over.
There are 4 settings that control the chapter and verse navigation that are relevant to what you are changing.
show-chapter-number-on-app-bar - already implemented
show-chapter-selector - already implemented
show-chapter-selector-after-book
show-verse-selector
See this document for how these last two affect the selectors.
https://docs.google.com/document/d/11To-nVTu2FKSlnSI5v3Q_nnv7x138zl8l7irVzOko_c/edit?usp=sharing


DPSGD example's dataset not shuffled between epochs

Since the dataset is turned into a list, the same batch order and batches are used for each epoch:
https://github.com/deepmind/optax/blob/30947fbc5743adc3e997c6242fa3775834862a74/examples/differentially_private_sgd.py#L131
Training loop:
https://github.com/deepmind/optax/blob/30947fbc5743adc3e997c6242fa3775834862a74/examples/differentially_private_sgd.py#L163-L168
The dataset should not be turned into a list at all, but there is a significant performance drop when the tf.data.Dataset is used directly (~4s/epoch with the tf.data.Dataset, ~0.7 seconds with the list). I was not able to improve this, so would appreciate if someone with tf.data expertise could take a look. Thanks!

It is a little hidden, but the shuffle on the dataset is happening in the function that creates the dataset:
https://github.com/deepmind/optax/blob/30947fbc5743adc3e997c6242fa3775834862a74/examples/datasets.py#L59-L62
(the default value for shuffle is True here)
For using a list(), according to the docs for tf.data.Dataset, it seems this is considered idiomatic in TF2:
https://www.tensorflow.org/api_docs/python/tf/data/Dataset#shuffle (noting that reshuffle_each_iteration defaults to True).
You are correct though that in the current factoring, the shuffling is deterministic across epochs (the list is only constructed once). One solution would be to construct the list() on each epoch.
I will look into improving this example.

Hi all!
Thanks @n2cholas for raising this!
I agree that we should not turn the dataset into a list. I have tried removing the list and I don't observe a big performance drop on CPU and GPU. There is a small change on GPU 0.7 --> 0.9 secs per epoch but this can be solved by adding prefetch(tf.data.AUTOTUNE) to the datasets.
I have filed PR #230 for removing the conversion to list and adding prefetching to the datasets by default. @n2cholas would it be easy for you to check your setup with the code from the PR or could you give details about the setup you tried? No worries if not! I just wanted to make sure the performance degradation you observed is also solved by prefetching.
Thanks a lot!

Thanks @mkunesch for working on this!  On a Tesla K80 on colab, I observe 4.62 s/epoch with your latest commit, while it's about 0.41 s/epoch on an older commit.
Here is the notebook: https://colab.research.google.com/drive/14rWb7QQSMNhNQZT_3iIBUhgQr6oH3YTo?usp=sharing. The current output is with the old commit, you can factory reset the runtime and comment out !cd optax && git checkout 4e5ac417e99b8a6067a8d73c41b38d72e835f637  to see the current time.
Also, I needed to change from optax.examples import datasets to import datasets for this script to run in Colab.

Thanks a lot @n2cholas for pointing this out and for the notebook to reproduce! I'll try to figure out what the difference between the setups is ... it's quite strange that there is no slowdown for me on a similar architecture 🤔.

Also, I needed to change from optax.examples import datasets to import datasets for this script to run in Colab.

Thanks a lot for pointing this out! This also affects the lookahead example and there is another error from jax (I think we'll have to increase the jax version requirement for the examples). I'll try to file a fix for this today or tomorrow and filed issue #240 so that we can prevent these errors in the future.

I had time to look into this now: the bottleneck was still the pre-processing on the colab GPU so caching again after preprocessing should solve the problem.
I filed #272 and checked commit 9fe0345 with the notebook @n2cholas sent above and it runs with 0.4s/epoch again now (the same performance we had originally when we were reusing the shuffling between epochs by mistake).

I think this issue is now solved: #230 fixes the bug itself and #272 fixes the performance issue that was surfaced by the bugfix. Thanks a lot again for raising this!


Kill container based on name if ID not available

If a job is undeploy right after it's deployed, we may have asked Docker to
create a container but still not gotten the ID back. In the past, we would
then leave this orphaned container around.
Now, if we don't have a container ID, we attempt to kill any container that
matches the predetermined container name to avoid this race condition.

@davidxia @gimaker
This should fix all those damn build errors due to DeploymentTest.

:+1: (but this is an area I'm certainly a novice in, so you should probably wait for another thumbs-up)


Add link to documentation on date/time formatting options.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Jaap Eldering seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Date column gets cast to uint16 in Arrow

Describe the bug
In [64]: r = client.query("SELECT * FROM pypi_downloads_per_month WHERE project = 'kedro'")

In [65]: r.named_results()
Out[65]: <generator object QueryResult.named_results at 0x13366e7a0>

In [66]: list(_)
Out[66]:
[{'month': datetime.date(2024, 5, 1), 'project': 'kedro', 'count': 36036},
 {'month': datetime.date(2023, 5, 1), 'project': 'kedro', 'count': 401975},
 {'month': datetime.date(2023, 6, 1), 'project': 'kedro', 'count': 376471},
 {'month': datetime.date(2023, 7, 1), 'project': 'kedro', 'count': 339635},
...

but:
In [67]: t_ = client.query_arrow("SELECT * FROM pypi_downloads_per_month WHERE project = 'kedro'")

In [68]: t_
Out[68]:
pyarrow.Table
month: uint16 not null
project: string not null
count: int64 not null
----
month: [[19844],[19478,19509,19539,19570],...,[19967],[19783,19814]]
project: [["kedro"],["kedro","kedro","kedro","kedro"],...,["kedro"],["kedro","kedro"]]
count: [[36036],[401975,376471,339635,345412],...,[92985],[527621,521359]]

(comes from pypi_downloads_per_month of clickpy https://clickhouse.com/blog/clickpy-one-trillion-rows)
Expected behaviour
I get a proper Date column in Arrow?
clickhouse-connect and/or ClickHouse server logs
?
Configuration
Environment

clickhouse-connect version: v0.7.19
Python version: 3.11.9
Operating system: macOS Sonoma 14.6.1

ClickHouse server

ClickHouse Server version:
ClickHouse Server non-default settings, if any:
CREATE TABLE statements for tables involved:
Sample data for these tables, use clickhouse-obfuscator if necessary

(These seem to be days since UNIX epoch btw)

Unlike the default/native formart clickhouse-connect doesn't do any conversion based on types for Arrow queries, it just returns what the PyArrow library does using the ClickHouse conversions here:  https://clickhouse.com/docs/en/interfaces/formats#data-format-arrow.  To stay consistent with ClickHouse, we don't intend to add any extra logic on top of either ClickHouse or PyArrow for particular data types.


Wrong type for codegen models for items with AWSJSON in their fields (DataStore)

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
React
Amplify APIs
Authentication, GraphQL API, DataStore, Storage
Amplify Categories
No response
Environment information

# Put output below this line
  System:
    OS: macOS 12.2.1
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 1.01 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    npm: 7.19.0 - {REDACTED}/node_modules/.bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  npmPackages:
    -: 0.0.1 => 0.0.1
    @aws-amplify/ui-react: ^2.8.0 => 2.8.0
    @aws-amplify/ui-react-internal:  undefined ()
    @aws-amplify/ui-react-legacy:  undefined ()
    @material-ui/core: ^4.12.2 => 4.12.2
    @material-ui/icons: ^4.11.2 => 4.11.2
    @testing-library/jest-dom: ^5.14.1 => 5.14.1
    @testing-library/react: ^11.2.7 => 11.2.7
    @testing-library/user-event: ^12.8.3 => 12.8.3
    @types/react: ^17.0.19 => 17.0.19
    @types/react-dom: ^17.0.9 => 17.0.9
    @types/react-router-dom: ^5.3.3 => 5.3.3
    @uiw/react-md-editor: ^3.6.3 => 3.6.3
    aws-amplify: ^4.3.14 => 4.3.14
    bootstrap: ^4.6.0 => 4.6.0
    g: ^2.0.1 => 2.0.1
    npm: ^7.19.0 => 7.19.0
    react: ^17.0.2 => 17.0.2
    react-app-rewired: ^2.1.8 => 2.1.8
    react-dom: ^17.0.2 => 17.0.2
    react-lorem-ipsum: ^1.4.9 => 1.4.9
    react-markdown: ^7.0.1 => 7.0.1
    react-player: ^2.9.0 => 2.9.0
    react-router-dom: ^5.2.0 => 5.2.0
    react-scripts: 4.0.3 => 4.0.3
    rehype-katex: ^5.0.0 => 5.0.0
    remark-math: ^5.1.0 => 5.1.0
    source-map-loader: ^3.0.0 => 3.0.0
    ts-loader: ^9.2.5 => 9.2.5
    typescript: ^4.3.5 => 4.3.5
    uuid: ^8.3.2 => 8.3.2 (3.3.2, 3.4.0)
    web-vitals: ^1.1.2 => 1.1.2
  npmGlobalPackages:
    @aws-amplify/cli: 7.6.22
    aws-cdk: 2.3.0
    corepack: 0.10.0
    npm: 8.1.2

Describe the bug
When getting an item that has AWSJSON in its fields, DataStore returns a Typescript JSON object for the AWSJSON field instead of a string.
However, the codegen models for Typescript label the field as a string instead of an object. Therefore, this causes issues since Typescript thinks an object is a string.
Expected behavior
The codegen models should have labeled AWSJSON fields as objects instead of strings.
Reproduction steps
(Not tested, hypothesized reproduction steps)

Create Schema with a type that has AWSJSON in one of its fields.
Use DataStore to query for an item of the above type
Log typeof type.field and it should return object instead of string.

}

Log output

// Put your logs below this line

aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
Workarounds
Use // @ts-ignore when assigning the value to another place and act as it is a JSON object.
Other symptoms
May cause A cross-origin error was thrown. React doesn’t have access to the actual error object in development. in React.
May be related to GraphQL Transformer V2 issues: https://github.com/aws-amplify/amplify-adminui/issues/426

Thanks! Another thing to add is that the data returned by API.GraphQL used to be in string form, but I'm not sure whether it's because of DataStore or the upgrade from Transformer V1 to V2.

Hi @thecodehen , thanks for bringing this to our attention. I was able to reproduce the issue. We will have a fix for this issue in upcoming releases.

Just to add some additional metadata, I created a test app to look at the different ways this surfaces. Note: I'm on amplify CLI version 9.2.1 and didn't explore the dimension of past releases. https://github.com/alharris-at/codegen-396-repro
My findings:
API Interface
Write only works when serialize to a string, so if we want to support object as an input type, it'll require library updates I think.
Retrieve always returns a string-ified version of the AWSJSON object.
Due to the simplicity of the API category interface, this isn't wholly surprising, there's no significant serde layer in API, so we expect correctly serialized values as inputs to graphql, and return serialized outputs for most things, i.e. the layer speaks JSON, and is therefore restricted by its limitations (this includes, dates, times, objects represented as strings in the backend, etc.).
From my perspective this is reasonable behavior, as it is inline with the rest of the behavior here.
DataStore Interface
Write works for either a serialized version of the AWSJSON object, or an object directly as well. Looks like the library is marshalling back to string as necessary.
Read always returns a parsed version of the AWSJSON object, not a string.
Updating the generated types to use object rather than string just works, suggesting that the DataStore use-case can be fixed purely in the codegen layer.
Because of the split behavior in datastore (write string, return object), we should make some change here to normalize.
I took a look at the behavior of AWSDateTime, to see how other serialized types are behaving today. They appear to be represented in the model as a string as well (not necessarily "correct" behavior) on both read and write.
While I'm not sure if that's the right long-term behavior for our system, it means that DataStore reads of AWSJSON is the only really out-of-band behavior here, and everything else appears consistent, if not ideal.
I'll raise this with the team, and propose a next step in this issue after that.


[SPARK-34417] [SQL] org.apache.spark.sql.DataFrameNaFunctions.fillMap(values: Seq[(String, Any)]) fails for column name having a dot

This PR fixes dataframe.na.fillMap() for column having a dot in the name as mentioned in SPARK-34417
What changes were proposed in this pull request?
Use resolved column name for comparison in case (k, _) => columnEquals(k, f.name)
Why are the changes needed?
dataframe.na.fillMap() does not work for column having a dot in the name
Does this PR introduce any user-facing change?
None
How was this patch tested?
Added unit test for the same

Can one of the admins verify this patch?

cc @cloud-fan @viirya

Please add [SQL] to the PR title, e.g. [SPARK-34417] [SQL] ...

ok to test

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39809/

Test build #135228 has started for PR 31545 at commit 20b8db7.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39809/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39809/

Test build #135228 has finished for PR 31545 at commit 20b8db7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135228/

Test build #135257 has started for PR 31545 at commit daf7c8a.

Test build #135257 has finished for PR 31545 at commit daf7c8a.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135257/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39837/

Test build #135260 has started for PR 31545 at commit 24302b9.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135260/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39840/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39840/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39840/

Jenkins retest this please

Test build #135349 has started for PR 31545 at commit 24302b9.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39930/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39930/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39930/

Test build #135349 has finished for PR 31545 at commit 24302b9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135349/

Test build #135537 has started for PR 31545 at commit cd0baa1.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40118/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40118/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40118/

Test build #135539 has started for PR 31545 at commit f49c742.

Test build #135539 has finished for PR 31545 at commit f49c742.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135539/

Test build #135537 has finished for PR 31545 at commit cd0baa1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135537/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40120/

Test build #135540 has started for PR 31545 at commit 5ee8bee.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40120/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40121/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40120/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40121/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40121/

Test build #135540 has finished for PR 31545 at commit 5ee8bee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135540/

Test build #135596 has started for PR 31545 at commit d0cbbe4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40177/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40177/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40177/

Test build #135596 has finished for PR 31545 at commit d0cbbe4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135596/

I updated the PR description a bit to fit the template more. Feel free to edit it.

Test build #135618 has started for PR 31545 at commit 896652c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40197/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40197/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40197/

Test build #135618 has finished for PR 31545 at commit 896652c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135618/

thanks, merging to master!

@amandeep-sharma if you have time, can you also help to fix the same problem in DataFrameNAFunctions.replace, Dataset.drop/withColumn?

@cloud-fan sure, i will create JIRA and work on it.


Material Select field floating label bug when using appearance

I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request

Current behavior
I am using a Material Select field, but when no option has been select and no value has been provided to the form, the floating label for the select field appears on top. This is when using appearance outline.
Expected behavior
When the field has not been touched, and no value has been provided thro the model, the label should not be floating.
Minimal reproduction of the problem with instructions
For a repro stackblitz go to: https://stackblitz.com/edit/angular-qwenyx.
There there is a bare mat-select with outline appearance and a ngx-formly mat select.
What is the motivation / use case for changing the behavior?

I would like all my form fields to look the same when the form is untouched
Please tell us about your environment:

Latest windows 10 build.

Angular version: 8.0.X

Browser: [Chrome  75.0.3770.142 | Firefox 68.01 | ]
Have not tested all the browsers

Language: [TypeScript ]

Btw, if someone could point me in the direction of the issue I would be more than happy to send a PR your way

already fixed yesterday, maybe next time :)!


Feature request: Check if thread ID is active

I'm trying to prevent users from double texting. I see that this is something LangGraph Cloud handles, but I'm hoping that this could be something that would be possible to do in plain LangGraph.
Maybe I'm missing some documentation and it is possible? How can one check if a thread ID is currently being processed?

There's a few strategies, one being adding some kind of queue mechanism in front of your graph:
https://langchain-ai.github.io/langgraph/cloud/how-tos/enqueue_concurrent/
There currently isn't yet an API for detecting this in the core LangGraph library though.


cmd/compile: ssa fails to flush return values during deferred func

Reduced from a bug in cmd/doc found by @robpike.
/cc @khr @dr2chase
The -ssa=0 behavior is correct: the program should print 1, not 0.
$ go run -gcflags -ssa=0 /tmp/x.go
1
$ go run /tmp/x.go
0
$ cat /tmp/x.go
package main

func main() {
	println(f())
}

func f() (x int) {
	for {
		defer func() {
			recover()
			x = 1
		}()
		panic(1)
	}
}
$

Upon further investigation, this seems unrelated to #14591.  It looks like x is allocated on the heap and we never copy the heap value back to the stack at the end of the function (after deferreturn).


Add support for LPI2C on S32K344

Reuse existing MCUX-based shim driver for LPI2C and update to compatible with the hardware block in S32K344. Configure the pins before initializing I2C to avoid happening bus busy.

Hello @henrikbrixandersen can you revisit PR please. Thanks.

Hello @henrikbrixandersen @danieldegrasse @manuargue I rebased to fix conflict. Pls help me reviews.

@congnguyenhuu, can you please help update west.yml and update merge conflicts.


Install only attribute flag

Description
For use cases like packer or other OS artifact builders, it is helpful to be able to only install the software that is need without configuring it to run as a service on initial boot.  For example, you can install consul on a instance and put in place a few standard checks that would be on all machines (Memory, CPU, Disk Utilization) and pack that into your build and it is preinstalled when you boot up your box and the provisioning step only needs configure any additional customizations..
I was originally going to create a consul::install recipe, but based on how baked in the installation code is in the service provider, it was not really possible.  This ends up making this a bit of a hack because the recipe ends up adding a service only to delete it, but based on what I can tell, deleting it will only remove the base config file and the service definition, but leave the binary in place.
My original workaround without this change was going to be the following:
include_recipe 'consul'

consul_service node['consul']['service_name'] do
  action :disable
end

But the delayed subscribes :restart that is baked into the consul::default recipe will actually fail because the service definition file on the machine will no longer exist.

I would prefer having a separate recipe for doing exactly this. What do you think?
It would also be great if you could add a section on embedding this into a Packer built image.

@johnbellone I think that makes sense, I just didn't want to get too invasive on my first run of things.  I can do a spike for this when I get a chance and you can let me know you think.

@johnbellone Alright, here is the spike as promised.
Rational
So, I ended up making a completely new lib strictly for installing consul, which does mostly what was done in consul_service, with a few tweaks:

Doesn't deal with making a poise service (probably obvious...)
Skips package resources on windows platforms since we are working with chocolatey to install the package on that platform
Handles uninstall cases a little more verbosely

I did this mainly because the consul_service was doing more than setting up a service, but also installing consul, and it was too hard to write the consul::install recipe with consul_service being the only way of installing things in this cookbook.  This unfortunately lead to a massive addition to the repo, and because I am a bit of an "over tester", quite the verbose set of chefspec tests for that resource.
I am going to try fixing the broken tests I now have on travis (working on my machine of course...), and breaking out installation code in the consul_service and updating the default recipe to make use of consul_install, and also make sure the integration tests are working as expected.  I think most of what I will be doing will a little more obvious now that I have the ground work laid out, and you can tell me what you would rather have done differently if needed.

I am wondering if this would make more sense to simply be an install action on the service provider. There would be a separate recipe called install (like you have already). The enable action would call action_install.

That would definitely make this a smaller change :smile:
I have just getting familiar with the poise libs this past week, so I was mostly trying to stay within the actions provided by poise-service out of the box, which install isn't one of them.  That said, what you are saying definitely seems possible and a much nicer for you to deal with, so I will try looking into that.  If it is pretty easy to do and doesn't require too much hackary, I will probably end up scraping this branch since it will just turn into a much of reverts.

That's a good point. I think I remember @coderanger telling me not to add actions to poise-service..

The optimal way to handle this would probably be separate providers for consul_service for each install type.

Current coverage is 49.01%

Merging #231 into master will increase coverage by +0.40% as of bf9d474

@@            master    #231   diff @@
======================================
  Files            6       7     +1
  Stmts          325     355    +30
  Branches         0       0
  Methods          0       0
======================================
+ Hit            158     174    +16
  Partial          0       0
- Missed         167     181    +14

Review entire Coverage Diff as of bf9d474

Powered by Codecov. Updated on successful CI builds.

Alright, I think this is where I want it... or at least for now.
A few things about the failing tests:

I Took out the windows/chocolatey tests since I wasn't sure why they were failing on .travis but not my machine.
Not sure what is up with the ruby 2.2 build, but I think that has been failing on master as well
The kitchen tests are passing for the binary install at least.  For the failures, here is what I ran into:

poise-service seems to detect upstart as the provider for centos-6.6, but 'serverspecis looking withchkconfig` to determine if the process is running.
The source builds didn't work because the package manager wasn't up to date
The Package builds failed because it couldn't find a consul package
For all of these, I was unsure if this was due to my changes or if they have always been failing, and haven't attempted any solutions to fix them since I am unsure where the integration tests fall in the pipeline.

Should I look into splitting up consul_install into separate providers?


Functionality added to trigger mail to KeyAccountManager if fixed budget project isn't having an end date.

Targets #{2315}

Description
If any fixed budget project does not have any end date, then a mail will send to Key Account Manager of the Project.
Checklist:

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

@Anshgupta456 Please fix CI checks then assign reviewers for review.

@Anshgupta456 please update mail template, I am sharing mail template.
Hi, KeyAccountManager

There are some fixed-budget projects which are not having any project end-date where you are assigned as a key account manager, please update these projects:

  	Project Name

1.	MegaFitMeals  (Link)
2.	PMG (Link)

Thanks,
Portal Team
ColoredCow


Fix incorrect env for token config

As pointed out by @mistydemeo, this is referring to the wrong env var. BUILDKITE_AGENT_ACCESS_TOKEN is the temporary token given to the agent by Buildkite, I'm pretty sure we mean BUILDKITE_AGENT_TOKEN here.
Fixes https://github.com/buildkite/agent/issues/490.


re riot panic: runtime error: invalid memory address or nil pointer dereference

Riot is not in the first GOPATH inside.

@vcaesar
Thanks, it's due to the problem, there is not GOPATH.


A memory limit option

Prevent rendering if expected memory usage will exceed the limit.

Not right now.


New version: flux.flux version 4.130

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

@HeitorAugustoLN please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree


Animation stack transition and playback apis

Removed AnimationAction::weight - use stack operation to blend instead
Removed: set_animation_blend (use set_animation_action_stack or play_animation_action_index)
Added: play_animation_action_index
Added AnimationActionStack::Transition - transitions the stack to another stack
Added AnimationActionStack::Start - resets the start time of the action with speed
Changed: set_animation_action_stack to include transition duration

https://github.com/AmbientRun/Ambient/assets/71590722/f7520cbe-86f1-4371-83bb-495f23fc34e7

Closing this, the api will go back to AnimationActions as its very similar to this approach but perhaps conceptually easier to understand.


Duplication issue when combined with Enviromine

I'm not sure what end is causing the issue... But I figured I'd start on this end since its duplicating your mods items.
When a Camelback (from the enviromine mod) is crafted onto an armored jetpack, attempting to remove the armor plating from the jetpack will cause a duplicate jetpack and armor plate to be created. The final result is that you have 2 identical armor plates, 1 jetpack still equiped with a camelback, and 1 clone jetpack without the camelback.
My best guess is that the camelback being attached is causing recipe confusion when removing the plate. I'm not sure how the meta/dmg/RF values are handled across this issue so I can't offer more info than that.
As a note: I haven't seen this issue occur with any other armor items that a camelback is attached/removed from.

Using EnviroMine 1.3.113, I can't even craft a Camelback onto a jetpack in the first place. Do I need to enable something to make that possible, or did something change?

You'll need to enable generate custom configs using Enviromine. Open enviromine's config and set these:
Will attempt to find and generate blank configs for any custom items/blocks/etc loaded before EnviroMine. Pack developers are highly encouraged to enable this! (Resets back to false after use)
B:"Generate Blank Configs"=true

# Generates EnviroMines initial default files
B:"Generate Defaults"=true

Run the game and enter into a world. This will generate enviromine's configs for all non-vanilla content. Once done, you should be able to craft the Camelback onto a jetpack.
My modpack can be found here if you prefer to pursue it that route:
http://www.technicpack.net/modpack/dangerous-depths.563211

EnviroMine's crafting handler seems to be conflicting with mine here. This is an issue on their side though; they are assuming there are no shapeless recipes with a chestplate as the only ingredient. Wrong in this case, as that is exactly how removing armor from my jetpacks works.
You'll either have to disable adding camel packs to my jetpacks, or the EnviroMine authors will have to figure something out here. They're effectively messing with my recipes, and I need those recipes so jetpacks can have their armor removed.

Understood. Thanks for looking into it.


out of memory during the training

Hi
I am trying to train a seq2seq model like it using my own dataset

th train.lua -data_file ../../data/demo-train.hdf5 -val_data_file ../../data/demo-val.hdf5 -savefile model-demo -brnn 1 -attn 1 -multi_attn 3 -gpuid 3 -max_batch_l 64 -lr_decay 0.8 -num_layers 4 -rnn_size 1024 -dropout 0.3 -curriculum 1

At the beginning, it works well. However, after 4800 batch, it threw an error about out of memory.
My machine has 196G memory with Tesla K40m. Since the training has begun, why it would fail during the training.

Epoch: 1, Batch: 4800/15072, Batch size: 64, LR: 1.0000, PPL: 246.53, |Param|: 690.31, |GParam|: 5.21, Training: 1817/1308/509 total/source/target tokens/sec
Epoch: 1, Batch: 4850/15072, Batch size: 64, LR: 1.0000, PPL: 244.21, |Param|: 691.18, |GParam|: 5.53, Training: 1816/1311/505 total/source/target tokens/sec
Epoch: 1, Batch: 4900/15072, Batch size: 64, LR: 1.0000, PPL: 241.79, |Param|: 692.06, |GParam|: 5.30, Training: 1815/1314/501 total/source/target tokens/sec
Epoch: 1, Batch: 4950/15072, Batch size: 64, LR: 1.0000, PPL: 239.34, |Param|: 692.97, |GParam|: 5.76, Training: 1814/1317/496 total/source/target tokens/sec
Epoch: 1, Batch: 5000/15072, Batch size: 64, LR: 1.0000, PPL: 236.97, |Param|: 693.87, |GParam|: 6.32, Training: 1813/1321/492 total/source/target tokens/sec
Epoch: 1, Batch: 5050/15072, Batch size: 64, LR: 1.0000, PPL: 234.39, |Param|: 694.76, |GParam|: 5.80, Training: 1812/1324/488 total/source/target tokens/sec
THCudaCheck FAIL file=/tmp/luarocks_cutorch-scm-1-2002/cutorch/lib/THC/generic/THCStorage.cu line=40 error=2 : out of memory
/home/work/dev/torch/distro/install/bin/luajit: ...v/torch/distro/install/share/lua/5.1/nngraph/nesting.lua:34: cuda runtime error (2) : out of memory at /tmp/luarocks_cutorch-scm-1-2002/cutorch/lib/THC/generic/THCStorage.cu:40
stack traceback:
[C]: in function 'resizeAs'
...v/torch/distro/install/share/lua/5.1/nngraph/nesting.lua:34: in function 'resizeNestedAs'
...v/torch/distro/install/share/lua/5.1/nngraph/gmodule.lua:37: in function 'getTotalGradOutput'
...v/torch/distro/install/share/lua/5.1/nngraph/gmodule.lua:404: in function 'neteval'
...v/torch/distro/install/share/lua/5.1/nngraph/gmodule.lua:454: in function 'updateGradInput'
...v/torch/distro/install/share/lua/5.1/nngraph/gmodule.lua:420: in function 'neteval'
...v/torch/distro/install/share/lua/5.1/nngraph/gmodule.lua:454: in function 'updateGradInput'
...ork/dev/torch/distro/install/share/lua/5.1/nn/Module.lua:31: in function 'backward'
train.lua:535: in function 'train_batch'
train.lua:745: in function 'train'
train.lua:1071: in function 'main'
train.lua:1074: in main chunk
[C]: in function 'dofile'
...rch/distro/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00405810

GPU memory usage is a (linear-ish) function of your source sequence length. Source sequence length varies for each batch. It's likely that the max source sequence length occurred around batch 5050, hence the failure.

Hi @yoonkim
If I want to solve this problem, I have those options below,  am I right? Is there any other methods?

make the network structure smaller, like smaller layers, less rnn_size.
reduce the batch size. Currently, the batch size is 64.
reduce the sequence length.
split the training to multiple-GPU, encode for gpu-device 0 and decode for gpu-device 1

that is correct


Anonymous states

Description
I wrote a whole thing and it got deleted because I forgot to submit the issue and I can't bother redoing it but I would hope for something like
let x = state(initial-value) // No way to access this state besides through `x`
let y = state(initial-value, key: "some-y-state-key") // Any state constructed with the same key will be associated with `y`.

This will break existing code, but using a named argument for the key makes existing code a hard error always, rather than things just not working sometimes (specifically with string-valued states)
There shouldn't be a way to construct a state with no arguments. If no initial value is provided, the state ought to be referencing some existing state in the document.
If you can think of a backwards compatible way to make the key optional I'd be open to hear it
Use Case
To avoid name collisions, and because usually there's no use for multiple states with the same key, so it just imposes a quirky and potentially brittle api

Due to the way state works, I believe there's no way around having to use some key, but there could certainly be some sort of "auto-generated" internal key which can never collide with custom user keys, perhaps with some sort of hash.

Due to function purity constraints, there are some limits to what we can do here. However, it would be possible to bind the key to the state's call site (more specifically, it's span). Then, two different state calls will always have unique keys, but one state call in a loop will always have the same key unless disambiguated by the user. Then, state itself isn't technically pure anymore, but a user function that calls state internally remains pure.

Yeah that's definitely something I had imagined, it sounds fair to me

The step function itself is pure, both invocations of it return the same value. You could store the return value of step() in a variable and use it in place of the two individual step() calls and the result would be the same. What's impure is the runtime that renders the content resulting from your code. This is similar to IO Actions in Haskell.

Additionally, you may think of display as taking a hidden location parameter and using it to determine the state of the state at that point in the document
also, this isn't really related to my issue, is it?

@emilyyyylime: already moved this to discussion #2501 to not pollute your issue 🙂

Regarding adding span as an implicit argument to state, I think that's quite dangerous; for example, consider:
#let create_state(i) = state(i + 2)

#let state1 = create_state(5)
#let state2 = create_state(9)

I'd expect state1 and state2 to be different states, but if they are implicitly disambiguated by their span then they will actually be the same state.

That's the question here: is it better or worse than the current way? Ultimately, because of function purity it's just hard to magically generate a unique state.
It could perhaps be made more explicit though. With a keyword or function that gives an id based on span which can be passed to state().

Regarding adding span as an implicit argument to state, I think that's quite dangerous; for example, consider:
#let create_state(i) = state(i + 2)

#let state1 = create_state(5)
#let state2 = create_state(9)

I'd expect state1 and state2 to be different states, but if they are implicitly disambiguated by their span then they will actually be the same state.

Here create_state creates a new state, hence we would like to use this call for the span, but can we actually know which call/reference to create state or not?

Well, I'm drawing a parallel to what code that goes something like this would do in a "typical" language:
function create_state(i) {
    return new State(i + 2);
}

let state1 = create_state(5)
let state2 = create_state(9)

So I don't think it's of much use to tie the state creation to some particular function call -- it's a bit more like there is some hidden variables being implicitly thread through the program, which get updated upon each state creation.

But then why is the span the same if it comes from 2 different calls?

Because the span is the actual location of the state call in the source code. Because the actual state call is in the same position in the source code (line 1, column 24), they would end up becoming the same state. (This is what I'm critiziing, and really believe should not be the case.)

Thing is span is instrumental to memoization at the moment and I don't know if it's easy (probs very very not) to remove it, so what I'm suggesting instead is that we change the used span to where we perceive the state is being created to have a small change still work in that scenario

Right. I just have no idea how we could figure that out. It may not even be possible in general.

Thing is span is instrumental to memoization at the moment

@astrale-sharp What exactly do you mean by this?

I'm suggesting instead is that we change the used span to where we perceive the state is being created to have a small change still work in that scenario

I just have no idea how we could figure that out. It may not even be possible in general.

I think no matter whether we use the span of state itself or any of its callees up the stack, there can be collisions where the full call stack is identical. A simple example is (1, 2).map(state) where there isn't even another call involved.

@astrale-sharp What exactly do you mean by this?

My current mental model is that when a typst function is called, comemo sees (unique span, arguments) and if they both are cached already, it gives the result.

I think no matter whether we use the span of state itself or any of its callees up the stack, there can be collisions where the full call stack is identical. A simple example is (1, 2).map(state) where there isn't even another call involved.

:thinking:

My current mental model is that when a typst function is called, comemo sees (unique span, arguments) and if they both are cached already, it gives the result.

Comemo generally has two kinds of arguments: Tracked ones (e.g. the world, not really relevant here), and hashed ones. If the tracked arguments are equivalent and the hashed ones have the same hash as in a previous call, comemo yields that call's result. Comemo itself does not care about spans. The spans are designed to be stable through edits to not hurt memoization too badly, but comemo would if anything work better without any spans. They are a necessary "evil" for useful diagnostics.

I see, does comemo has to be aware of span then? or can we just not avoid it cause they're here?

Comemo isn't aware of spans in particular, they are just part of the hashed data. They need to be part of that or else the memoization results would be invalid.

Thanks for the explanation!


Scrapper, Kseniya Torgasheva - 22FPL2

No activity in PR. It is right time to start working on it.

No progress since last review

No progress since last review

No progress since last review


Feature Request: Support mix format plugins

Elixir 1.13 added mix format plugins: https://hexdocs.pm/mix/1.13.2/Mix.Tasks.Format.html#module-plugins
ElixirLS should support these plugins if defined in the user's project.
Initially requested in: https://github.com/elixir-lsp/vscode-elixir-ls/discussions/224

Would this also enable support for elixir-ls to format, via LSP, *.html.heex files, too?

I may have time to make a PR to add support for this, what has to be done to make it work?

@zachdaniel -> https://github.com/elixir-lsp/vscode-elixir-ls/discussions/224#discussioncomment-2092096

Super pumped for this!

Anyone know if it works for elixir-ls in Emacs?

With the recent addition of the LiveView formatter in 0.17.8 I noticed that the formatting does work automatically in VSCode when using .ex files with the ~H sigil. But using html.heex files it gives the following error:
[Error - 07:32:49] Request textDocument/formatting failed.
  Message: Unable to format due to syntax error
  Code: -32603
MIX_ENV: test
MIX_TARGET:

I used the sample code from the elixir formatter docs.
test.html.heex:

   <%= @user.name %>

.formatter.exs
[
  import_deps: [:phoenix],
  plugins: [Phoenix.LiveView.HTMLFormatter],
  inputs: ["*.{heex,ex,exs}", "priv/*/seeds.exs", "{config,lib,test}/**/*.{heex,ex,exs}"]
]

@frankdugan3 Yeah I did that. Also deleted the build and deps folder. When running mix format directly on the .html.heexfile formatting works. But not when running through VSCode with the Elixir LSP.

@benvp I forgot to mention it, but it also requires Elixir v1.13.4. What version are you running?

I have the exact same situation as @benvp described.

running mix format in the console works
running the formatter through vscode results in the described error
I have version 1.13.4 running

I can confirm the same issue.
elixir v1.13.4
neovim 0.7.0 + lspconfig and ElixirLS build from master (7f37d59ffe7952d70ddc2f44100227d558c8ef6e)
.formatter.exs
[
  plugins: [Phoenix.LiveView.HTMLFormatter],
  import_deps: [:ecto, :phoenix],
  inputs: ["*.{heex,ex,exs}", "priv/*/seeds.exs", "{config,lib,test}/**/*.{heex,ex,exs}"],
  subdirectories: ["priv/*/migrations"]
]

Phoenix LiveView
      {:phoenix_live_view, "~> 0.17.9"},

.ex files with ~H are formatted correctly
.heex file returns error
"rpc.receive"   {  error = {    code = -32603,    message = "Unable to format due to syntax error"  },  id = 4,  jsonrpc = "2.0"}

Added inspect for the exception
Error: %SyntaxError{
  column: 1,
  description: "syntax error before: '<'",
  file: "nofile",
  line: 1,
  snippet: %{content: "
<%= @inner_content %>
",
  offset: 0
}

Slightly OT, VSCode instructions
For anything to work, you will need a recent Elixir version. I got 1.13.4 running. Also .formatters.exs must contain heex and the HTMLFormatter plugin:
[
  import_deps: [:ecto, :phoenix],
  plugins: [Phoenix.LiveView.HTMLFormatter],
  inputs: ["*.{heex,ex,exs}", "priv/*/seeds.exs", "{config,lib,test}/**/*.{heex,ex,exs}"],
  subdirectories: ["priv/*/migrations"]
]

Then apparently the .heex-files and ~H-sigil formatting isn't the same.
At least for me this plugin does not work with mix format from VSCode, neither calling it from the command bar in VSCode nor on autoformat on save.
ElixirLS: Elixir support and debugger
Id: JakeBecker.elixir-ls
Description: Elixir support with debugger, autocomplete, and more. Powered by ElixirLS.
Version: 0.9.0
Publisher: ElixirLS
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=JakeBecker.elixir-ls

However this plugin works for doing the same thing:
Name: Elixir Mix Formatter
Id: animus-coop.vscode-elixir-mix-formatter
Description: Elixir Mix Formatter integrated into Visual Studio Code.
Version: 1.0.1
Publisher: Animus Coop.
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=animus-coop.vscode-elixir-mix-formatter

You will have to change (or remove, and it will ask) the default formatter in your VSCode settings.json, example:
"[phoenix-heex]": {
  "editor.defaultFormatter": "animus-coop.vscode-elixir-mix-formatter", // Relevant line
  "editor.detectIndentation": false,
  "editor.formatOnPaste": true,
  "editor.formatOnSave": true,
  "editor.formatOnType": true,
  "editor.tabSize": 2,
  "editor.trimAutoWhitespace": true,
  "files.insertFinalNewline": false,
  "files.trimTrailingWhitespace": true
},

I hope this anyone.

The actual problem (IMHO) is that ElixirLS uses Code.format_string! which receives options from Mix.Tasks.Format.formatter_opts_for_file, but format_string! doesn't accept plugins as an option. So it doesn't know how to format .heex files.
mix format works because it understands the plugins.
What can be done here, is to use Mix.Tasks.Formatter.formatter_for_file/2 to format the source file, same as the mix format does.
Would this be a way to go? If this is valid, I might be able to prepare a PR for this.

Any update on this issue? It looks like the PR #690 is accepted but not merged. Thank you guys for your work on this!

🥳 🎉 🙇🏻 ❤

Note for others or future me to find. My formatter failed with plugin not found on vscode elixir-ls ONLY. Console worked properly. The issue was that elixir-ls was building as test env.
This failed as a result:
{:tailwind_formatter, "~> 0.4.0", only: :dev, runtime: false}
This obviously works:
{:tailwind_formatter, "~> 0.4.0", only: [:dev, :test], runtime: false}

@ddengler You can switch ElixirLS mix env to dev via extension config if that works better in your case

the suggestion of @lukaszsamson worked for me, I had :phoenix_live_reload, "~> 1.2", only: :dev}, in a project and the extension default environment is test, switching it to dev and restarting VSCode fixed the issue.


Discord service

Add discord to default settings

https://github.com/feelfreelinux/facegram/pull/14/commits/71389442264bd337fd7c85f6e44b08691609cfd5#diff-7e82dc7533620e594f349d3ea425b5b4
done already (?)


Details: module 'zlib' has no attribute 'Z_SYNC_FLUSH'

Checklist for submitting an issue to KickThemOut:

[x] I have carefully read the README file and haven't managed to resolve my issue.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] I am running the latest version of KickThemOut.

OS &  Name Version: Debian &  Strech
Python Version:  Python 3.6
Kamene Version:  Kamene 0.32
Nmap Version: Nmap 0.0.1
Link of Gist: https://github.com/tomasojea/Kickissue

Description:  I got the error Details: module 'zlib' has no attribute 'Z_SYNC_FLUSH' i have all the dependencies  on the site-packages but yet does not work I download the zlib and installed manually and the problem remains

Hey @tomasojea. Is this still an issue with the latest version of KickThemOut? Thanks.

Yes, it is.

Could you please uninstall all dependencies, re-install them, and share each of your steps here? Thanks!


verifyObject Signature Update

Implement the equivalent HashStore-java issue

When a client calls storeObject(InputStream stream), a data object is stored immediately with its content identifier. Then later, when the client calls verifyObject to confirm the metadata/checksums after they've received it and there is a mismatch, there is no easy way to remove the data object that was stored.
To assist with the clean-up process, we will add a new boolean argument to the signature of verifyObject, deleteInvalidObject.
public void verifyObject(
    ObjectMetadata objectInfo, String checksum, String checksumAlgorithm, long objSize, boolean deleteInvalidObject
)

When this is set to true, HashStore will attempt to delete the data object associated with the given ObjectMetadata and then throw an exception. Otherwise, it will only throw an exception.
Additional ToDo:

Ensure HashStore interface return value for verifyObject is accurate/descriptive

Also, rename verifyObject to deleteInvalidObject

This has been completed via Feature-124: verify_object Update


Getting duplicate random data unless using unique

Setup
I use Faker for seeding my database in Laravel. I define my factory method as follows (simplified):
$factory->define(App\Textfield::class, function (Faker $faker) {
    $faker->seed(1234);

    return [
        'name' => $faker->company,
        'x' => $faker->randomDigit,
        'effects' => $faker->randomElement(['b', 's', 'i', 'n', 'u', 'l', 'z', 'k', 'v', 'qn', 'hn', 'mn']),
    ];
});

I call this 10 times like this factory(App\Textfield::class, 10)->create();
Problem
Faker just spits out 10 rows of the same data, among all columns. When i change one of the calls to be unique, such as $faker->unique()->company, the company name gets generated uniquely, as well as all the other values.
What i would like to happen
The data gets created randomly, without me having to specify unique on one of the columns. I do not need the columns to be unique, i just want the values to be somewhat randomly distributed. Maybe this is a problem with Laravel though - i thought about calling the factory method in a loop, incrementing the seed with each iteration. I do not see an option of passing this to the factory method though.

The issue is likely to be that you always use the same seed. Thus, every call to your closure will result in the same data being generated.
Why do you need to specify the seed?

I would like to always get the same data when populating my database.
What happens here is expected behaviour, i would not even call it a bug. But somehow, using unique() on just one of the columns solves my problem. I was wondering if there is to generally apply the technique that unique uses to all of my generated data - ensuring to always get the same result on each run but with different tuples, allowing duplicate values.

Can you rephrase? I fail to understand your need.

I think what you want is to always get the same values when you run the seeder
In which case, set the seed before you call the method 10 times instead of during the method.

@fzaninotto A more concrete example of what i am experiencing:
Current behaviour
$factory->define(App\Textfield::class, function (Faker $faker) {
    $faker->seed(1234);

    return [
        'name' => $faker->company,
        'number' => $faker->randomDigit
    ];
});
... (in another file)
factory(App\Textfield::class, 3)->create();

Example output:

name
number

Foo
2

Foo
2

Foo
2

Using unique on one of the columns:
$factory->define(App\Textfield::class, function (Faker $faker) {
    $faker->seed(1234);

    return [
        'name' => $faker->unique()->company,
        'number' => $faker->randomDigit
    ];
});
... (in another file)
factory(App\Textfield::class, 3)->create();

Example output:

name
number

Foo
2

Bar
6

Baz
8

So, using unique here not only causes the first column to generate uniquely but also the second to at least get different values.
Wanted behaviour
$factory->define(App\Textfield::class, function (Faker $faker) {
    $faker->seed(1234);

    return [
        'name' => $faker->company,
        'number' => $faker->randomDigit
    ];
});
... (in another file)
factory(App\Textfield::class, 3)->create();

Example output:

name
number

Foo
2

Bar
4

Foo
8

I would like to be able to generate those values in a way that:

always yields the same result (using a seed)
does not spit out rows that are just the same
allow duplicate values to occur

What @PatrickRose suggest should fix the issue i am having, although it would require some rework in the code.
I brought this up because of the particular case of what calling ->unique() on one of the columns does, maybe there is a way to use that behaviour of semi-randomness but allow duplicates between multiple calls. I also see that what i am suggesting is a bit of a corner case, so i also would not mind the issue being closed - but if someone wants to take a stab at it that would be nice, too,

I'm not too familiar with Faker internals but I believe what's happening is
calling unique() moves the random number generator along until it gets a
unique value which is why you're seeing new values on each iteration.
To be honest, what you're trying to do seems a bit off - why do you want
faker to return the same values on each run? The idea is to get random data
so you can spot bugs.
On 3 Feb 2018 11:36, "Benedikt Franke"<EMAIL_ADDRESS>wrote:

@fzaninotto https://github.com/fzaninotto A more concrete example of
what i am experiencing:
Current behaviour
$factory->define(App\Textfield::class, function (Faker $faker) {
$faker->seed(1234);
return [
    'name' => $faker->company,
    'number' => $faker->randomDigit
];

});
... (in another file)
factory(App\Textfield::class, 3)->create();
Example output:
name number
Foo 2
Foo 2
Foo 2
Using unique on one of the columns:
$factory->define(App\Textfield::class, function (Faker $faker) {
$faker->seed(1234);
return [
    'name' => $faker->unique()->company,
    'number' => $faker->randomDigit
];

});
... (in another file)
factory(App\Textfield::class, 3)->create();
Example output:
name number
Foo 2
Bar 6
Baz 8
So, using unique here not only causes the first column to generate
uniquely but also the second to at least get different values.
Wanted behaviour
$factory->define(App\Textfield::class, function (Faker $faker) {
$faker->seed(1234);
return [
    'name' => $faker->company,
    'number' => $faker->randomDigit
];

});
... (in another file)
factory(App\Textfield::class, 3)->create();
Example output:
name number
Foo 2
Bar 4
Foo 8
I would like to be able to generate those values in a way that:

always yields the same result (using a seed)
does not spit out rows that are just the same
allow duplicate values to occur

What @PatrickRose https://github.com/patrickrose suggest should fix the
issue i am having, although it would require some rework in the code.
I brought this up because of the particular case of what calling
->unique() on one of the columns does, maybe there is a way to use that
behaviour of semi-randomness but allow duplicates between multiple calls. I
also see that what i am suggesting is a bit of a corner case, so i also
would not mind the issue being closed - but if someone wants to take a stab
at it that would be nice, too,
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fzaninotto/Faker/issues/1417#issuecomment-362799806,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmozGhUFwNlbmIbsDUpjNJCaHV-Or35ks5tRES5gaJpZM4R1iac
.

There are many valid reasons why you would always want to generate the same data. Especially for automated testing - it can be beneficial to work with a set of fixed inputs so you can test the outputs.
In my particular case, i am designing an API and am doing some transformations on the generated data before exposing it. And that i can only test when dealing with known base information.

Closing this issue since it is possible to get the wanted behaviour, it just requires a bit of a workaround from the laravel code.
Faker works as intended.


Add a function for insert.

I have an excel of users and an excel of addresses with the user full name, how I can seed the database converting the full name into the ID of the users?
where can I add a function that queries the id of the user with the name?

Hmm, this package may not be for you. In the interests of simplicity and speed, all this package does is map CSV rows to DB columns and does a chunked INSERT statement.
You could create two tables - imported_users and imported_addresses then after calling $seeder->run() do your SQL query merging the data into your users table I suppose.


[BUG] Unable to update apktool from the AUR

Information

2.7.0 -
Arch Linux -
No apk -
**Openjdk <IP_ADDRESS> 2023-08-24
OpenJDK Runtime Environment (build <IP_ADDRESS>+1)
OpenJDK 64-Bit Server VM (build <IP_ADDRESS>+1, mixed mode)
** -

Stacktrace/Logcat
:: Searching AUR for updates...
 -> Packages not in AUR: codetantra-sea  libsignon-glib  qt-gstreamer  telepathy-accounts-signon  telepathy-kde-accounts-kcm  telepathy-kde-approver  telepathy-kde-auth-handler  telepathy-kde-call-ui  telepathy-kde-common-internals  telepathy-kde-contact-list  telepathy-kde-contact-runner  telepathy-kde-desktop-applets  telepathy-kde-filetransfer-handler  telepathy-kde-integration-module  telepathy-kde-send-file  telepathy-kde-text-ui  telepathy-logger-qt
 -> Orphan (unmaintained) AUR Packages: telepathy-farstream  telepathy-qt
:: 1 package to upgrade/install.
1  aur/android-apktool  2.7.0-1 -> 2.8.1-2
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==>
AUR Explicit (1): android-apktool-2.8.1-2
:: PKGBUILD up to date, skipping download: android-apktool
  1 android-apktool                          (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
  1 android-apktool                          (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
==> Making package: android-apktool 2.8.1-2 (Sat 16 Sep 2023 11:52:46 AM IST)
==> Retrieving sources...
  -> Found android-apktool-2.8.1.tar.gz
  -> Found apktool-install-linux-r04-brut1.tar.bz2
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
    android-apktool-2.8.1.tar.gz ... Passed
    apktool-install-linux-r04-brut1.tar.bz2 ... Passed
:: (1/1) Parsing SRCINFO: android-apktool
==> Making package: android-apktool 2.8.1-2 (Sat 16 Sep 2023 11:52:47 AM IST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found android-apktool-2.8.1.tar.gz
  -> Found apktool-install-linux-r04-brut1.tar.bz2
==> Validating source files with sha256sums...
    android-apktool-2.8.1.tar.gz ... Passed
    apktool-install-linux-r04-brut1.tar.bz2 ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting android-apktool-2.8.1.tar.gz with bsdtar
  -> Extracting apktool-install-linux-r04-brut1.tar.bz2 with bsdtar
==> Starting prepare()...
==> Sources are ready.
==> Making package: android-apktool 2.8.1-2 (Sat 16 Sep 2023 11:52:50 AM IST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.3/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build

> Configure project :
Building SNAPSHOT (no .git folder found)

> Task :brut.j.common:javadoc FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':brut.j.common:javadoc'.
> Javadoc generation failed. Generated Javadoc options file (useful for troubleshooting): '/home/lavish/.cache/yay/android-apktool/src/Apktool-2.8.1/brut.j.common/build/tmp/javadoc/javadoc.options'

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 9s
6 actionable tasks: 6 executed
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: android-apktool-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
android-apktool - exit status 4

Steps to Reproduce

Try updating apktool from the AUR

I have no idea what that is - but it builds on our CI and my local so must be on their side.


Try to download files on Google Storage with curl.

Forked from pull request #435.

Codecov Report

Merging #436 into development will increase coverage by <.01%.
The diff coverage is 100%.

@@               Coverage Diff               @@
##           development     #436      +/-   ##
===============================================
+ Coverage        98.41%   98.41%   +<.01%
===============================================
  Files               38       38
  Lines             3090     3099       +9
  Branches           146      148       +2
===============================================
+ Hits              3041     3050       +9
  Misses              43       43
  Partials             6        6

Impacted Files
Coverage Δ

...ompute_engine/metadata_scripts/script_retriever.py
100% <100%> (ø)
:arrow_up:

...ne/metadata_scripts/tests/script_retriever_test.py
100% <100%> (ø)
: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 d2e4c6b...2c5e1cf. Read the comment docs.


Fix empty tooltip and missing required tooltip

Fixes #757 and #392

This doesn't seem easy to read. I don't think we want both a title and a popover menu. Maybe @astridu can help?

I made this change pending @astridu's feedback:

Yes, the second example looks much better (just the 1 tooltip). Thank you!

I'm seeing this now.  Since we have the tooltip, should we get rid of the <abbr/>?

@michelleif @jermnelson what sort of commitments to we have to accessibility?  I'm pretty sure the <abbr> with a title are useful for screen readers.   I'm pretty sure the <abbr> with a title are useful for screen readers. I'm not sure the popover is useful for anyone not using a mouse.

I would like us to be more accessible. We're running this elint plugin: https://www.npmjs.com/package/eslint-plugin-jsx-a11y with some rule exceptions.

So do we know if a screenreader can focus on a <sup> element that has a single child marked aria-hidden="true"?

I added a tabIndex to the sup to make it keyboard accessible, and role-tooltip for ARIA. Do you  think this will address the accessibility issues?

Yes, that probably ought to do it.


DNM: Kconfig.zephyr: check priorities by default

Dependencies:

#58312
#58333
#59633
#59634
#59635
#60168
#60169
#60170
#60178
#60221
#60223
#60304
#60338
#60340
https://github.com/zephyrproject-rtos/zephyr/pull/60889

#60814
#60816
TODO: s32z270dc2_rtu0_r52:samples/boards/nxp_s32/netc/sample.boards.nxp_s32.netc.psi

Push check branch on testing: https://github.com/zephyrproject-rtos/zephyr-testing/tree/vfabio-testing-branch

@manuargue this is the last down I have:
$ west build -p -b s32z270dc2_rtu0_r52 -T samples/boards/nxp_s32/netc/sample.boards.nxp_s32.netc.psi
$ ./scripts/build/check_init_priorities.py -vv
...
ERROR: /soc/ethernet@74000000/ethernet@74b00000 POST_KERNEL 60 79 < /soc/ethernet@74000000/mdio@74b60000/ethernet-phy POST_KERNEL 80 78

that's ethernet-phy under netc which would imply that netc initializes before, but that implication is not correct, I think that the fix is to move emdio: mdio@74b60000 { up one level in https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/arm/nxp/nxp_s32z27x_r52.dtsi#L607.
If that's correct and you want to open a PR and test it it'd be cool!

that's ethernet-phy under netc which would imply that netc initializes before, but that implication is not correct, I think that the fix is to move emdio: mdio@74b60000 { up one level in https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/arm/nxp/nxp_s32z27x_r52.dtsi#L607.
If that's correct and you want to open a PR and test it it'd be cool!

hi @fabiobaltieri , let me have a look because it may not be so trivial due to the way the HAL does the ethernet controller components initialization.

that's ethernet-phy under netc which would imply that netc initializes before, but that implication is not correct, I think that the fix is to move emdio: mdio@74b60000 { up one level in https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/arm/nxp/nxp_s32z27x_r52.dtsi#L607.
If that's correct and you want to open a PR and test it it'd be cool!

hi @fabiobaltieri , let me have a look because it may not be so trivial due to the way the HAL does the ethernet controller components initialization.

Hey I don't think we should change how init is done in this case, just the way the peripheral are declared in the tree.

Hey I don't think we should change how init is done in this case, just the way the peripheral are declared in the tree.

Actually I was reading it wrong, this may use a priority change, could you check if https://github.com/zephyrproject-rtos/zephyr/pull/60913 makes sense?


error when an array of events is used

Class: LokiEventEmitter - on
when it is passed to the method 'on' an array of events, this is not handled properly it.
Also in the code comments reads:
@returns {int} the index of the callback in the array of listeners for a particular event
but returns the callback.
I think the solution is:
LokiEventEmitter.prototype.on = function (eventName, listener) {
        var event;
        var self = this;

        if (Array.isArray(eventName)) {
          eventName.forEach(function(currentEventName) {
            self.on(currentEventName, listener);
          });
          return listener;
        }

        event = this.events[eventName];
        if (!event) {
          event = this.events[eventName] = [];
        }
        event.push(listener);
        return listener;
      };

I should make a pull request with this solution?

Hi @cristyansv the reason why the index of the listener is returned is that a single event can have many listeners, and if you want to remove one of those you need to know what position they occupy in the listeners array. It's an edge case as removing listeners isn't really a common practice, but I can't think of another way to do that. If you can please go ahead and submit a PR, i'll be happy to check it out.

the reason why the index of the listener is returned is that a single event can have many listeners, and if you want to remove one of those you need to know what position they occupy in the listeners array

Yes, I agree, but at this time, does not happen.
I'll make small change to accept arrays properly.

@techfort what you think about https://github.com/techfort/LokiJS/pull/501


Add id_with_brackets, table and id_without_bracket methods

Codecov Report

Merging #9 (b6ffe4c) into main (2d559ea) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is 100.0%.

Additional details and impacted files

Files
Coverage Δ

src/new_id.rs
100.0% <100.0%> (ø)


Feature/linking accession ids

Description

accessionIds of related objects are now linked.
Instead of typing manually, inside each form we can select accessionIds of other submitted objects according to ENA Metadata model: https://metadata-submitter.readthedocs.io/en/docs-metadata-and-auth/metadata.html

Related issues
https://github.com/CSCfi/metadata-submitter-frontend/issues/58
Type of change

[x] New feature (non-breaking change which adds functionality)

Changes Made

Modify dereferencedSchema in WizardFillObjectDetailsForm to add arrays of accessionId  of other ObjectTypes
Add e2e test for testing linking accessionIds of all ObjectTypes
Update unit test

Testing

[x] Unit Tests
[x] Integration Tests

Mentions

In Analysis form, there is a section for Analysis Reference and inside it there is a field for Accession Id. This could mean that Analysis could link to each other (?)
Users may confuse when they see only the accessionIds without knowing exactly which submission is which. We can add the title there for ones that have title.

FieldArray fields to automatically choose reference accession ID when clicking Add new item

--> This is not on purpose. I think it shouldn't render any selection in the beginning. It can be fixed in another PR.

Looks good! however the accession id might be something that users might find difficult to identify.
Is there a way to also put in the drop down the title near the id - but when it is selected just put in the field the accession id.
something like:
drop down :arrow_down_small:
359625734 (study 1)
589675476 (study 2)
When user selects 589675476 (study 2) in the field only 589675476 remains
This is not mandatory and could be part of another PR. What do you think?

Hi!
I did some limited testing, and had some trouble.
To replicate, create a new submission:

create and submit a sample
click "Experiment"->"Fill Form"

The site crashes with:
Uncaught (in promise) TypeError: s.filter is not a function         WizardJSONSchemaParser.js:356:39
    children WizardJSONSchemaParser.js:356
    _r WizardJSONSchemaParser.js:128
    React 7
    unstable_runWithPriority scheduler.production.min.js:18
    React 5
    e WizardFillObjectDetailsForm.js:466
    l runtime.js:63
    _invoke runtime.js:293
    S runtime.js:118
    Babel 2

Tested in firefox 89 and chrome 91.0.4472.101.

Looks good! however the accession id might be something that users might find difficult to identify.
Is there a way to also put in the drop down the title near the id - but when it is selected just put in the field the accession id.
something like:
drop down 🔽
359625734 (study 1)
589675476 (study 2)
When user selects 589675476 (study 2) in the field only 589675476 remains
This is not mandatory and could be part of another PR. What do you think?

This is a good idea. We can put the title next to AccessionId.
I also think that in some of submitted forms, they may not have the title because the title is not required, then we can only show the AccessionId. Or with the case of DAC form, we then need to show the title as Main Contact: Name.

Hi!
I did some limited testing, and had some trouble.
To replicate, create a new submission:

create and submit a sample
click "Experiment"->"Fill Form"

The site crashes with:
Uncaught (in promise) TypeError: s.filter is not a function         WizardJSONSchemaParser.js:356:39
    children WizardJSONSchemaParser.js:356
    _r WizardJSONSchemaParser.js:128
    React 7
    unstable_runWithPriority scheduler.production.min.js:18
    React 5
    e WizardFillObjectDetailsForm.js:466
    l runtime.js:63
    _invoke runtime.js:293
    S runtime.js:118
    Babel 2

Tested in firefox 89 and chrome 91.0.4472.101.

Hi! I hope my latest commit would fix this issue.


Decode

General requirements
Make sure that there are [no linter errors](https://github.com/microverseinc/linters-config). ✅ ✅
Make sure that you used [Gitflow](https://github.com/microverseinc/curriculum-transversal-skills/blob/main/git-github/articles/gitflow.md). ✅ ✅
Make sure that you documented your work [in a professional way](https://github.com/microverseinc/curriculum-transversal-skills/blob/main/documentation/articles/professional_repo_rules.md). ✅ ✅

Ruby requirements
Follow our list of [best practices for Ruby](https://github.com/microverseinc/curriculum-ruby/blob/main/articles/ruby_best_practices.md). ✅ ✅

Project requirements
Create a method to decode a Morse code character, takes a string parameter, and return the corresponding character in uppercase (e.g. decode_char(".-") returns "A"). ✅ ✅
Create a method to decode an entire word in Morse code, takes a string parameter, and return the string representation. Every character in a word will be separated by a single space (e.g. decode_word("-- -.--") returns "MY"). ✅ ✅
Create a method to decode the entire message in Morse code, takes a string parameter, and return the string representation. Every word will be separated by 3 spaces (e.g.

  decode("-- -.--   -. .- -- .")

returns "MY NAME"). ✅ ✅ ✅
Reuse methods whenever possible. Make sure that your code is DRY. ✅ ✅
Decode the message from the old bottle: ✅ ✅ ✅

  .-   -... --- -..-   ..-. ..- .-.. .-..   --- ..-.   .-. ..- -... .. . ...

[ ] Kindly remove the commented code from your codebase which has been introduced after the fix


MSN Users Can Recover Lost Email Accounts

Haven’t you signed-in to your MSN account for long? Is your account hacked? Whatever be the reason of losing your account, we are here to help. MSN users can recover their lost email accounts with Contact Email Support’s technical assistance. Our certified professionals will help you throughout the recovery process. Apart from account recovery, we offer solutions for email attachment issues, email sending and receiving, forgotten password etc.

Flagging as spam. I've removed the link the user posted, and will flag the user to Github as spam.


Enhance subSurfaceScattering

Find and develop a solution for mixed material: this would allow avoiding blue artifact at the bottom of the neck in https://playground.babylonjs.com/#SYQW69#506

Done

Done


Update Version in Package.Json (PAYM-503)

Motivation

I forgot to update the version in the last PR

Modification

Updated version

Results

Noodling on a way to check this in PRs

https://centeredge.atlassian.net/browse/PAYM-503

/merge


Make h0 and h1 in graphic perpendicular to surface in graphic

The graphic shows h0 and h1 parallel to each other, which might work for low values, but isn't actually what you are calculating (as seen in your explanation image).

No, if you study the graphic carefully you'll see h0 and h1 are perpendicular to the surface and therefore not parallel to each other.

I meant the graphic on http://dizzib.github.io/earth/curve-calc/index.html Your explanation graphic of course has the lines not parallel.

Oh yes I see, thanks!


Change cursor over < and > in instructions

The cursor should remain an arrow over these since they do nothing.

Fixed in f70b02787a981210f71aa76acbef2377f2ca101b.


Add 3 new contributors

@davidradl Please provide the github id of each of the three members.
I'll also propose a new template/doc update to document the process (see https://egeria-project.org/guides/project-operations/#contributors for

I see from CONTRIBUTORS.md you added
| Federica Donald |<EMAIL_ADDRESS>|
| Adinarayana Harida |<EMAIL_ADDRESS>|
| Sachin Naik |<EMAIL_ADDRESS>|

which seems to be:
@fedtried
@adinhtdsibm
@odttlnt
I have added these under https://github.com/odpi -> Teams -> Egeria Contributors
This group has 'read' access for egeria, as can be seen under
https://github.com/odpi/egeria/settings/access-> where it can be seen that this team has the role 'read'
This may not be the case for all repos (I'd need to check through them).  A quick look suggests it's done for the old ones, not the latest
I also think any 'member' (and usually this won't happen until they are a contributor) can ask for more access, but we should generally do that through the process that you linked, but which is incomplete -- so will be improved in the referenced issue

Note I think the user in question may receive an invite to the org, if not already a member. Any problems post back here.