PHP Intl

@sashaaro Could you explain why this is required? Is there an issue associated to this?

@philtrep Even i am facing this issue as well. Some external composer packages ask for it. Homebrew provides it in stock install (as I moved my repo from homebrew to laradock) and composer install broke.
Problem 1
    - Installation request for jeremykendall/php-domain-parser 3.0.0 -> satisfiable by jeremykendall/php-domain-parser[3.0.0].
    - jeremykendall/php-domain-parser 3.0.0 requires ext-intl * -> the requested PHP extension intl is missing from your system.
  Problem 2
    - Installation request for league/uri 4.2.2 -> satisfiable by league/uri[4.2.2].
    - league/uri 4.2.2 requires ext-intl * -> the requested PHP extension intl is missing from your system.

Why not add Intl by default. Many packages required it

@sashaaro I am getting this error when adding the changes in my local dockerfile as shown in the PR request. However i keep getting the following. To be just sure I also added google dns by adding it to daemon.json at /etc/docker/daemon.json but to no avail. Also this is happening only to this statement.
Suggested packages:
  icu-doc
The following NEW packages will be installed:
  icu-devtools libicu-dev libicu52
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 14.6 MB of archives.
After this operation, 65.6 MB of additional disk space will be used.

ERROR: Service 'php-fpm' failed to build: The command '/bin/sh -c apt-get install -y libicu-dev && pecl install intl && docker-php-ext-install intl' returned a non-zero code: 100

Seems It work for me long time ago. At least I have not docker's errors.
I think it is only from php-fpm. But for composer install should change workspace Dockerfile.
I don't know exactly.
Someone know better than me should correct it.
By the way you can avoid it by use run composer install --ignore-platform-reqs

@sashaaro  composer install --ignore-platform-reqs worked for me but seems unsafe to ignore platform requirements. @philtrep Is there a better way to do it? Would really appreciate to add it to the laradock itself but if not then how can we proceed about it. So that its available for both php-fpm and cli if required.

@sashaaro @dannysood This should be a build argument on both the workspace and php-fpm images. I don't think there's a better way to do this with just docker-compose.

I'm also having this same issue. libicu-dev fails the build install. Anyone know how to fix it?
Step 16/40 : RUN apt-get install -y zlib1g-dev libicu-dev g++
 ---> Running in 214b167d7568
Reading package lists...
Building dependency tree...
Reading state information...
g++ is already the newest version.
zlib1g-dev is already the newest version.
Suggested packages:
  icu-doc
The following NEW packages will be installed:
  icu-devtools libicu-dev libicu52
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 14.6 MB of archives.
After this operation, 65.6 MB of additional disk space will be used.
Err http://httpredir.debian.org/debian/ jessie/main libicu52 amd64 52.1-8+deb8u3
  404  Not Found [IP: <IP_ADDRESS> 80]
Err http://security.debian.org/ jessie/updates/main libicu52 amd64 52.1-8+deb8u3
  404  Not Found
Err http://security.debian.org/ jessie/updates/main icu-devtools amd64 52.1-8+deb8u3
  404  Not Found
Err http://security.debian.org/ jessie/updates/main libicu-dev amd64 52.1-8+deb8u3
  404  Not Found
E: Failed to fetch http://security.debian.org/pool/updates/main/i/icu/libicu52_52.1-8+deb8u3_amd64.deb  404  Not Found

E: Failed to fetch http://security.debian.org/pool/updates/main/i/icu/icu-devtools_52.1-8+deb8u3_amd64.deb  404  Not Found

E: Failed to fetch http://security.debian.org/pool/updates/main/i/icu/libicu-dev_52.1-8+deb8u3_amd64.deb  404  Not Found

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
ERROR: Service 'php-fpm' failed to build: The command '/bin/sh -c apt-get install -y zlib1g-dev libicu-dev g++' returned a non-zero code: 100


2:<IP_ADDRESS>.3 Expected Actions

Suggest changing this:
When the Patient Identifier Cross-reference Manager receives the Remove Patient message of the Patient Identity Feed transaction, it shall cross-reference the patient identifiers provided by removing any references it is maintaining internally to the patient identifier provided.
to this:
When the Patient Identifier Cross-reference Manager receives the Remove Patient message, it shall remove any references it is maintaining internally to the patient identifier provided.

http://build.fhir.org/ig/IHE/ITI.PIXm/branches/master/ITI-104.html#23104433-expected-actions


feat: Adds support to load stores that are created with a single default export

Issue: nuxt2 could automatically load stores defined as a single export
export default {
  state: () => ({
    one: false,
    two: false,
  }),
  actions: {
    async pageOne ({ commit }) {
      commit('pageONE')
    },
  },
  mutations: {
    pageONE (state) {
      state.one = true
    },
  },
}

A little related to issue https://github.com/vedmant/nuxt3-vuex/issues/14

I added 1 test to exemplify

@guska8 Thanks, merged and released


how to train

can i use the GlyphControl to train my own dataset?

Thanks for asking! We will release the training codes in a week or so.

Excellent work!
I am also looking forward to the release of the training code.


Implement a learning rate warmup

Note also that the ideal training hyperparameters seem to vary with model layer; I would imagine this extends to learning rate, and it certainly extends to the L1 regularization term.

(Classified as "bug" because circuits aren't clean, presumably due to poor autoencoder solutions.)


Missing the 'puppetversion' fact

I'm not sure if this is intended or not, but this gem seems to be missing the puppetversion fact, which has been around since at least Facter 1.6.
I'm currently using the following workaround:
let(:facts) do
  facts.merge!({ :puppetversion => ENV['PUPPET_VERSION'] || '3.7.0' })
end

@rji this is intentional as it depends on the puppet version you are using. I use this as a wrokaround:
let(:facts) do
  facts.merge({ :puppetversion => Puppet.version })
end


Is Mapper::unmap really safe?

I don't think it is. For example, if we unmap the page where the kerenl stack exists, page fault should happen.

The question always is how you define safe and unsafe. For this crate, we use a quite narrow definition of safe. Instead of "cannot cause bad things", we define it as "cannot break memory safety". By this definition, a page fault or even a double/triple fault is not unsafe since no memory is corrupted and no undefined behavior occurs.
The Rust standard library uses a similar definition. This is the reason that functions like forget (leaks memory) or even abort (kills the whole process) are safe.

I understand. Thank you!


Albert xLarge pretraining idles on single v3-8 tpu

I'm trying to train with ~ 568 tfrecord files totaling upto 1.9 TB, created from ~30GB of text and generated using 128 max_seq_length and custom vocab comparable to the original vocab size.
Here are my training flasgs:
nohup python3 run_pretraining.py
--input_file=gs://databucket-*
--output_dir=gs://output bucket
--export_dir==gs://export bucket
--do_train=True
--do_eval=True
--albert_config_file=gs://\albert_config.json
--train_batch_size=512
--eval_batch_size=64
--max_seq_length=128
--max_predictions_per_seq=20
--num_train_steps=2000000
--num_warmup_steps=10000
--learning_rate=1e-4
--use_tpu=True
--tpu_name=gorilla-alb-tpu
--save_checkpoints_steps=10000
--max_eval_steps=100
--num_tpu_cores=8
--user_tpu=True
--keep_checkpoint_max=500
> iter001.log &
I tried this on the preemptible tpu first and did not even get one checkpoint, but later on the second iteration, I used a dedicated TPU, but after the global step 19000 its started idling and did not produce any checkpoints, as can be seen in the logs below.
Q1: Any idea what am I missing here?
Q2: Also, why is the train time so slow compared to BERT, which stepped through 10K/20 mins, here it seems 10K/1.15 hr or more?
Q3: What is the recommended batch size for single TPU instance and how does it impact the train steps and the learning rate?
Extract of the logs showing idling here :
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:04:59.069434<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:loss = 6.453083, step = 19000 (1816.160 sec)
I1124 07:05:04.021676<PHONE_NUMBER>29568 basic_session_run_hooks.py:260] loss = 6.453083, step = 19000 (1816.160 sec)
INFO:tensorflow:global_step/sec: 0.550612
I1124 07:05:04.024546<PHONE_NUMBER>29568 tpu_estimator.py:2307] global_step/sec: 0.550612
INFO:tensorflow:examples/sec: 281.913
I1124 07:05:04.024918<PHONE_NUMBER>29568 tpu_estimator.py:2308] examples/sec: 281.913
INFO:tensorflow:Enqueue next (1000) batch(es) of data to infeed.
I1124 07:05:04.025995<PHONE_NUMBER>29568 tpu_estimator.py:600] Enqueue next (1000) batch(es) of data to infeed.
INFO:tensorflow:Dequeue next (1000) batch(es) of data from outfeed.
I1124 07:05:04.026226<PHONE_NUMBER>29568 tpu_estimator.py:604] Dequeue next (1000) batch(es) of data from outfeed.
INFO:tensorflow:Outfeed finished for iteration (19, 12)
I1124 07:05:28.020126<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 12)
I1124 07:05:29.137331<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:05:29.192949<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:05:59.262590<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:05:59.311209<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:06:29.373492<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:06:29.447152<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 46)
I1124 07:06:29.709674<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 46)
I1124 07:06:59.522179<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:06:59.572463<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:07:29.611606<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:07:29.668322<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 80)
I1124 07:07:31.398825<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 80)
I1124 07:07:59.732999<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:07:59.793257<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:08:29.856629<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:08:29.919902<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 114)
I1124 07:08:33.089343<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 114)
I1124 07:08:59.989946<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:09:00.072418<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:09:30.138386<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:09:30.192759<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 148)
I1124 07:09:34.782029<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 148)
I1124 07:10:00.262878<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:10:00.322918<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:10:30.385881<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:10:30.438601<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 182)
I1124 07:10:36.469368<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 182)
I1124 07:11:00.488457<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:11:00.554763<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:11:30.607665<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:11:30.657622<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 216)
I1124 07:11:38.161521<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 216)
I1124 07:12:00.723495<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:12:00.779349<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:12:30.844133<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:12:30.897756<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 250)
I1124 07:12:39.851271<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 250)
I1124 07:13:00.941801<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:13:00.998180<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:13:31.063151<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:13:31.136875<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 284)
I1124 07:13:41.539725<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 284)
I1124 07:14:01.204144<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:14:01.270991<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:14:31.314057<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:14:31.368036<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 318)
I1124 07:14:43.230399<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 318)
I1124 07:15:01.408405<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:15:01.466477<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:15:31.531250<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:15:31.588218<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 352)
I1124 07:15:44.920365<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 352)
I1124 07:16:01.650633<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:16:01.709294<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:16:31.747833<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:16:31.803840<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 386)
I1124 07:16:46.611431<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 386)
I1124 07:17:01.843595<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:17:01.905045<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:17:31.969744<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:17:32.024375<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
INFO:tensorflow:Outfeed finished for iteration (19, 420)
I1124 07:17:48.304604<PHONE_NUMBER>39584 tpu_estimator.py:279] Outfeed finished for iteration (19, 420)
I1124 07:18:02.091745<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:18:02.247168<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:18:32.311644<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:18:32.362884<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:19:02.426864<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:19:02.486614<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:19:32.542831<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:19:32.602440<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
I1124 07:20:02.665383<PHONE_NUMBER>46880 transport.py:157] Attempting refresh to obtain initial access_token
WARNING:tensorflow:TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
W1124 07:20:02.727149<PHONE_NUMBER>46880 preempted_hook.py:91] TPUPollingThread found TPU b'gorilla-alb-tpu' in state READY, and health HEALTHY.
iter001.log

Same problem, also here: https://github.com/tensorflow/tpu/issues/609

@dhruvsakalley @josecannete Google Cloud has had a bug internally for about a month.  They just pushed a fix.  I had to delete and re-recreate my TPUs, but now I see uninterrupted training.  It's unclear if your issue is due to the same bug, but you might try re-creating your TPUs.  (Don't just stop-start them, you have to delete them apparently).  https://github.com/tensorflow/tpu/issues/609#issuecomment-558819717

Hi all. I am facing the same issue, tried deleting and re-creating the TPUs but it didn't solve the problem. @dhruvsakalley @josecannete would you mind telling me how you solved the problem?

After the bugfix on the TPU VM I didn't encounter the issue again.

Same for me. The problem was not in our part.


#59 Fix documentation broken links in README

Signed-off-by: Rajat Varyani<EMAIL_ADDRESS>

@payes Can you please retrigger the CI?


Discuss about using blank token in VITS2

The "add_blank" is True in vits2_ljs_base.json. In the original VITS paper, the authors said that they did not use the blank token.
Can you explain to me why you set "add_blank" as True?

Yes, my bad. We can turn if off in the config. I missed that part. Thanks for the catch!


Adding circuit images for better understanding

It would be nice to have an overview of inner working of each of the APIs in Microsoft Quantum Machine Learning library. Also for better intuition building, these articles can include images of example circuits.

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

ID: e1e62567-13c8-19c2-ba15-65920a49afb3
Version Independent ID: 5c7af935-d4af-6f50-1bb7-4f64ffcf836e
Content: CyclicEntanglingLayer function (Microsoft.Quantum.MachineLearning) - Q# reference - Microsoft Quantum
Content Source: api/qsharp/microsoft.quantum.machinelearning.cyclicentanglinglayer.yml
Product: quantum
GitHub Login: @cgranade

Thanks for raising this, @J1990! We'll look at how to add more examples of using those QML library functions in API documentation.
As a side note, you may also be interested in the feature at https://github.com/microsoft/iqsharp/pull/231.

@cgranade @KittyYeungQ , I think this is a great suggestion. Will it be possible to include circuit diagrams in some parts of the documentation?

Part of the problem is that Q# operations really aren't circuits; while tools like %trace provided with IQ# can show execution paths when running Q# programs, I think it would be very confusing to equate circuit diagrams with those programs themselves. That aside, though, I don't believe we currently have a pipeline in place for deploying images used in API documentation at all, especially since API documentation can be consumed in a variety of different places (e.g.: docs.microsoft.com, IQ#'s ? commands, VS Code or VS 2019 hover information), not all of which support richer features like images.

That makes sense. There are, however, some Q# operations for which having an example circuit diagram to explain the concept can be helpful. Like you said; Q# programs aren't circuits, but circuits can be helpful to explain some parts of the program.
My suggestion would be to have an internal discussion about this and see how we can use circuits to our advantage whilst still making a clear distinction between circuits and Q# programs. Then we can see if we can implement a feature to deploy images in API documentation (which would be platform-dependent as you noted). Would something like that work?


Support for React Components

specifically, internal links should not refresh the page, i.e. ATM
[contact me](/contact/) refreshes the browser

You can use whatever components you want, just specify them in the renderers prop.
See other issues like #29 and #65

oh of course
thanks


Add Terms of Service and Privacy Policy Links

Include links to the Terms of Service and Privacy Policy, and create corresponding content for transparency and user compliance.
Tasks:

[ ] Content for the Terms of Service outlining user responsibilities, platform rules, and liability.
[ ] Content for the Privacy Policy explaining data usage, storage, and sharing practices.
[ ] Add a "Terms of Service" link to the footer or relevant sections of the app.
[ ] Add a "Privacy Policy" link alongside the Terms of Service link.
[ ] Ensure the links open in a new tab or modal without disrupting the user flow.

Acceptance Criteria:

[ ] Terms of Service and Privacy Policy are created.
[ ] Clicking the links opens the respective documents in a new tab or modal.

@shuaibq3 Bhai @Shahed-Chy-Suzan We can this app to generate the  content.


[1000 BANK] Update token modal

The existing token modal does not have a way to disconnect/change wallets. It does not display the full address nor does it allow a one-click "add to metamask".
Requirements
Per a new design from Logan, update the existing token modal with the following changes:

Change modal title to "BANK Account"
Update modal design
Add current account address
Add clickable eyeball icon to toggle obfuscation of address
Add clickable text to copy address
Add external link to the address on Etherscan
Add clickable text to change/disconnect wallet (let us know what is possible here)
Update BANK section design / copy
Fun: On hover, the token icon should play a rotating gif.
Add a clickable (/claim) block if the user has claimable funds associated with the account; otherwise do not show.
If connected to MetaMask, show clickable text to "Add token to MetaMask".

Omit: the "Bank Stats" link will be for future iterations
REWARD: 1000 BANK
We can add the primary dev to Figma

@wpmonty This one sounds fun, count me in!

Closing this issue, this is now live.


Error: Model is disposed!

I have found the error below in my logs, very confident that this is from
https://github.com/microsoft/vscode/blob/82af26f7068754312f5454175c45f8648a45eac1/src/vs/editor/browser/widget/diffEditor/workerBasedDocumentDiffProvider.ts#L44
(minified source reference for reference)

ERR Model is disposed!: Error: Model is disposed!
    at q.ib (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:728:263)
    at q.getLineCount (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:730:4302)
    at p.computeDiff (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:41595)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:47044
    at g._runFn (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:14193)
    at g.k (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:15081)
    at g.endUpdate (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:15420)
    at i.finish (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:11735)
    at p (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:11170)
    at o.trigger (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:21685)
    at W.a (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:681:44567)
    at W.h (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:149:19415)
    at W.g (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:149:19399)

Thanks for reporting!
The duplicates are not really duplicates btw., they just happen to throw the same error.


some enhancements for social buttons..

@shivarajnaidu  I'm closing this because

Reg the intending. Some of them are already changed. I am working default with master. Many mentioned changes are already done on my PC. Some of them are as in my code editor. It will change back to what it is now. I don't use GitHub online.
There is no need for Readme file for this repo. I omitted it on purpose. It is a website and I intend to cut out anything that is not needed.
You have changed many single line css codes into multiple lines for neat arrangement. However I prefer to keep them in a single line. In fact I am working on my PC in merging more similar codes into a single line. Less the no of lines easier to navigate and work with.
Regarding stopping the animation upon hovering, it is great however I am closing this pull request for other reasons mentioned above.

Majority of your changes are well thought and acceptable. But I am already working with it on my PC.

It's okay... No problem.. So you just add 0 animation on hovering... and Remade File would be helpful to other people who will look at on this repo.. so consider this... add one yourself...

Will add compressed/minified CSS shortly.


[NO MERGE] 3958 geocode all null or false

cartodb_georef_status semantics:

NULL: not processed (before geocoding) or errored (a failure on our side)
TRUE: succesful geocoding
FALSE: failed geocoding (miss)

So at the beginning of the geocoding:

formerly: all rows WHERE cartodb_georef_status IS NULL are to be processed
now: all rows WHERE cartodb_georef_status IS NOT TRUE are to be processed

Changes:

Add a column force_all_rows to the geocodings table
Add parameter force_all_rows to create and estimation_for endpoints
Modify Geocoding#processable_rows to take an optional param force_all_rows and account for it
Rename s/add_georef_status_column/ensure_georef_status_colummn_valid
Add a couple of methods reset_cartodb_georef_status and mark_rows_to_geocode
Modify some of the sql expressions to keep consistent with everything

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

:+1:  nice!

Frontend tests were OK :+1: (details)


[WIP] Text component

One thing that needs to be discussed is that React native also provides Text component and having a component that has the same name would be confusing or could possibly cause a naming conflict.
We also might be able to refactor the Title component since Title is just a special version of Text.

For some reason the tslinter in CircleCI is smarter and finds more lint flaws while the one in my local machine is stupid and doesn't check anything.

@yuki24 you need to run yarn type-check which runs on CI. we should run it locally as well which by adding it to precommit hook script list in package.json

Good point, but for now we don't need to worry about the details of a shared code base just yet.


fix(client): fix default cursor autofocus (#610)

closes #610

@daniloff200 Thank you for the PR ! 🎉
I'm going to hold onto this PR because @akbansa was already working on this via #695 . I'm going to wait for him to correct his PR over the next 2 days. If he doesn't have time, then I'll accept this PR as the fix. Hope you understand.

@mohanarpit  Yes, sure thing.

Closing as duplicate of #923


graphRAG on an existing knowledge graph

Thank you very much for your project, I have learnt a lot of new and innovative things.
If now I have built a knowledge graph in neo4j, how can I use LLM for graphRAG based on this KG in the UI?
Any replies will be greatly appreciated.

Hi @AI7Xiao thanks you so much for your words regarding existing knowledge graph you can refer #889


Send confirmation instructions when a user updates the email address from nil

Send confirmation instructions when a user updates his email from nil.
Skip reconfirmation in the case that a record is created with #save called in callbacks in a proper way.

@lmduc Thank you for your contribution. Nice catch!
Which version are you using?

@ulissesalmeida Thank you. I am using Devise version 3.5.6


not work in nextjs 9.3x + compose plugin

Hi
Using

module.exports = withPlugins([
[optimizedImages, { inlineImageLimit: -1 }],
nextImagesPlugin,
], nextEnvConfig)

image inner background and others result empty or corrupted

Hi @vincalkr
This problem should now be resolved with version v2.6.0 (just published a few minutes ago).
Can you please try it again? If you still have problems, feel free to open a new issue. Thanks!

Hi @cyrilwanner but still it not work.
here are some indications ..

thanks

is there an update on this?

nothing
Il giorno dom 24 mag 2020 alle 23:09, Pablo Díaz
<EMAIL_ADDRESS>ha scritto:

is there an update on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


initial informal rewrite of the governance spec

factories? feels like Java. I'll be thinking about other possible ways to do it later.

Currently implemeting a much simpler PubKeyHash==TokenSymbol` based approach, will see if we need to go to this version

lets discuss two different user-agent
the end-user who owns GOV tokens
the developer-user who Mints GOV tokens, and wants to utilize the government contract
so this has limited the utility of the contract in 2 important ways:
the developer-user cannot disperse rewards or obtain voting information for users in an ad-hoc fashion
the end user must regularly interact with the staked tokens, increasing the liklihood they will sell.
Often, discouraging users from keeping the GOV token in their wallet is part of the intended behavior of the contract.
additionally, xGOV tokens may be delegated to a contract that allows rewards and Gov tokens to be reclaimed separately.

closing as currently we decided to go with the original approach + a technical workaround


tab completion before prefix length

Currently hitting <tab>to trigger completion before prefix length shows <09>;
Instead, how about falling back to <tab> ?
I could not yet wrap my head around how to actually does what <tab> is supposed to do (which is nr2char(&wildcharm) in scripts).

See also https://github.com/girishji/vimsuggest/pull/10 implementing prefix

Yes, so I think something like sending <tab> instead of nr2char(&wildcharm) is going on inside the plugin

But I couldn't pinpoint where

It is done here:

Do you want completion window to popup when you hit <tab> AND when typed text is less than prefix  length?

Anything's better than outputting <09>, yes, the completion window is natural as hitting <tab> for me is manual completion (in contrast to autocompletion). The other alternative would be to make <tab> do what it would do without this plug-in, but I suppose that's more difficult (and somehow it must be unmapped to make it work?)

https://github.com/girishji/vimsuggest/commit/65ea3d5b611be3987d08c7fd1b4226948bd13096

Sorry for late response. Should be fixed now.

Thank you very much, I didn't dare to tackle this and there's no hurry. I took note of the sensibly changed option name, but behavior kept being the same, still emitting <09> instead of vimsuggest's completion menu kicking in

You have this: https://github.com/girishji/vimsuggest/commit/2dfdd698b9871a33e7755b7e5bd3afcde4a6f7c6 ?
What options are you using?

You have this: 2dfdd69 ?

Yes, it's included.
In fact, :e<tab> now works, but after more than one character (but less than prefixlen) :ed it stops working.
That should be a simple oversight.

What options are you using?

Running vim --clean -u ~/.viminrc with the latter reading
vim9script
set nocompatible
# To avoid scrambled non english letters.
language messages en_US.utf-8

# # Load plugin
# let &rtp = '/usr/share/vim/vim91/plugin' . ',' . &rtp
&rtp = '~/.vim/plugged/vimsuggest/' .. ',' .. &rtp

filetype plugin indent on
syntax on

# # options go here
# set hidden

var vim_suggest = {}
vim_suggest.cmd = {
    enable: true,
    pum: true,
    exclude: [],
    onspace: ['b\%[uffer]', 'colo\%[rscheme]'],
    alwayson: true,
    popupattrs: {},
    wildignore: true,
    addons: true,
    ctrl_np: false,
    reverse: false,
    prefixlen: 3,
}
vim_suggest.search = {
    enable: true,
    pum: true,
    fuzzy: false,
    alwayson: true,
    popupattrs: {
      'maxheight': 12
    },
    range: 100,
    timeout: 200,
    async: true,
    async_timeout: 3000,
    async_minlines: 1000,
    highlight: true,
    ctrl_np: false,
    prefixlen: 3,
}
autocmd VimEnter * call g:VimSuggestSetOptions(vim_suggest)

# ex:ft=vim

Then :ed<tab> shows ^I, whereas with my vimrc it shows <09>.

Should be fixed. Please try now.


204 in HTTP or HTTPS

when i use node.js and Django to create my app, when i set response with status code 204 with some content in Chrome, if the url begin with https, it will response pending on the web and it do not return any thing, but when i use http://localhost:8080, it will return 204 with other content, Why is it that this non-compliant request can get a response over HTTP, but is restricted over HTTPS?

Hello, I couldn't reproduce your problem.
here is a project I created trying to reproduce this problem. It is a Minimal, Reproducible Example. Based on what you are trying to do. Here is the source code from this project:
app.js
const express = require('express')
const https = require('https')
const fs = require('fs')
const path = require('path')
const app = express();

app.use('/', (req, res) => {
    res.status(204).end();
});

const options = {
    key: fs.readFileSync(path.join(__dirname, './cert/key.pem')),
    cert: fs.readFileSync(path.join(__dirname, './cert/cert.pem'))
}
const port = process.env.PORT || 8080;
const sslServer = https.createServer(options, app);
sslServer.listen(port, () => {
    console.log(`Secure server is listening on port ${port}`)
});
const anotherPort = process.env.ANOTHERPORT || 8081;

app.listen(anotherPort, () => {
    console.log(`Server is listening on port ${anotherPort}`)
});

Making the request in a browser or a request/response tool (like postman, curl or insomnia) I receive the same results.
Here is the output I collected from curl with command curl -I https://localhost:8080/ -k here I use -k argument is for disable certificate validation (as it is a self-signed certificate). It is stated by the documentation:
HTTP/1.1 204 No Content
X-Powered-By: Express
Date: Thu, 08 Aug 2024 13:19:51 GMT
Connection: keep-alive
Keep-Alive: timeout=5

The same output is shown when used the same server (but now without https), curl -I  http://localhost:8081:
HTTP/1.1 204 No Content
X-Powered-By: Express
Date: Thu, 08 Aug 2024 13:20:43 GMT
Connection: keep-alive
Keep-Alive: timeout=5

If you have any concerns, please let me know.
The reason to create a project in GitHub is to keep everything needed to run the project self-contained (an express project and the certificates needed to run the https server).
I generated the certificates using this blog post as a resource.

Hello, I couldn't reproduce your problem.
here is a project I created trying to reproduce this problem. It is a Minimal, Reproducible Example. Based on what you are trying to do. Here is the source code from this project:
app.js
const express = require('express')
const https = require('https')
const fs = require('fs')
const path = require('path')
const app = express();

app.use('/', (req, res) => {
    res.status(204).end();
});

const options = {
    key: fs.readFileSync(path.join(__dirname, './cert/key.pem')),
    cert: fs.readFileSync(path.join(__dirname, './cert/cert.pem'))
}
const port = process.env.PORT || 8080;
const sslServer = https.createServer(options, app);
sslServer.listen(port, () => {
    console.log(`Secure server is listening on port ${port}`)
});
const anotherPort = process.env.ANOTHERPORT || 8081;

app.listen(anotherPort, () => {
    console.log(`Server is listening on port ${anotherPort}`)
});

Making the request in a browser or a request/response tool (like postman, curl or insomnia) I receive the same results.
Here is the output I collected from curl with command curl -I https://localhost:8080/ -k here I use -k argument is for disable certificate validation (as it is a self-signed certificate). It is stated by the documentation:
HTTP/1.1 204 No Content
X-Powered-By: Express
Date: Thu, 08 Aug 2024 13:19:51 GMT
Connection: keep-alive
Keep-Alive: timeout=5

The same output is shown when used the same server (but now without https), curl -I http://localhost:8081:
HTTP/1.1 204 No Content
X-Powered-By: Express
Date: Thu, 08 Aug 2024 13:20:43 GMT
Connection: keep-alive
Keep-Alive: timeout=5

If you have any concerns, please let me know.
The reason to create a project in GitHub is to keep everything needed to run the project self-contained (an express project and the certificates needed to run the https server).
I generated the certificates using this blog post as a resource.

I use http://localhost:8080 and a cloud server in the same environment, my function is.                return HttpResponse( json.dumps({'message':'delete successfully '})，content_type='application/json'，status=204)  ,when i use curl ,the data will be deleted in database and the program will over, but when i use curl to request the cloud server (https), the data also be deleted, but the program without any response, when I debug in the chrome, i saw the status and size is “(pending)”,

@oceanusXXD how is your problem related to Express?
This is Python code, not JavaScript:
return HttpResponse(json.dumps({'message':'delete successfully '})，content_type='application/json'，status=204)

@oceanusXXD how is your problem related to Express?
This is Python code, not JavaScript:
return HttpResponse(json.dumps({'message':'delete successfully '})，content_type='application/json'，status=204)

Sorry~I will close it soon, but if you can reproduce this issue on your local or cloud server, it may indicate that it is a common problem.


Source control providers view always everything selected

Version: 1.41.0-insider (user setup)
Commit: 1c9fd8a59787487ca71d8c5ce140569a0e036a15
Date: 2019-11-19T06:28:41.868Z
Electron: 6.1.4
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.17763
Steps to Reproduce:
Update VS Code to the version above

Go to the source control providers view
All git repos are always selected an it is not possible to unselect them or select just one. Always all of the are selected

The only special setting regarding scm providers I have changed:
"scm.providers.visible": 30
Does this issue occur when all extensions are disabled?: Yes

Fixed with another VS Code update:
Version: 1.41.0-insider (user setup)
Commit: 29b99f85e54aa5af6cd4edf918a67d4f70a10aea
Date: 2019-11-19T10:22:48.048Z
Electron: 6.1.4
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.17763


redis-om-node and node-redis - different clients?

Why do the implementation of client differ? redis-om-node uses createClient from node-redis, but chooses not to expose the it directly.
If I need to use features from node-redis, should I create another connection?

Found the answer in the readme: https://github.com/redis/redis-om-node#-connect-to-redis-with-a-client
I am now connecting to node-redis and reusing the connection for redis-om-node.


Return matched tx indices from NewMerkleBlock.

This pull request modifies the NewMerkleBlock function to return the matched transaction indices instead of their hashes.  This is being done because it is much easier for the caller to lookup the matched transactions from the original passed block based on their transaction index within the block versus their hashes.

OK


Add support for logging frontend JS errors

https://github.com/open-telemetry/opentelemetry-js

Awaiting https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1560

Rolled our own version of this in #4


DOC: import create_sql_query_chain is incorrectly imported in SQL + CSV document

Checklist

[X] I added a very descriptive title to this issue.
[X] I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:
https://python.langchain.com/docs/use_cases/sql/quickstart/
this is link to the document with incorrect import statement for create_sql_query_chain
In chain section of above document the correct import statement should be from langchain.chains.sql_database.query import create_sql_query_chain
but is incorrect in document, provided the ss of same the 1st statement of code area

Idea or request for content:
No response

@sam1231ui  Actually, this link is OK. It works fine.
It works because the namespace is flattened in the langchain/chains/__init__.py file, line 82.
You can use the langchain.chains namespace for this symbol.


feature: limit argo workflow name length

first draft for fixing argo workflows workflow name maxLength. Previously 253 characters have been allowed, but this causes  launching workflows through Argo UI to fail for names longer than 63 characters, as Argo wants to set the workflow template name as a Kubernetes label for the workflow.
Idea is to introduce a new limit of 63 characters, which checks for existence of a >63char deployment upon name resolving and raises an exception in case one is found. User can circumvent this by applying a flag to use the old name lengths for argo workflow commands:
argo-workflows --old-name-length [command]

Note: This can in some cases affect GitOps setups and other CI solutions for deploying flows. An easy workaround for those would to apply the --old-name-length flag for deployments to retain the original functionality.
attempts to address #1521 and unblock implementing #1416

[ ] requires some guard against truncating project flows to invalid DNS subdomain names (dot followed by dash)
[ ] possibly rethink how project flows are truncated (visibility: project part vs. flow name). we could opt for truncating the project part and keeping flow name visible instead

closing this in favour of #2082


Joincondition can only receive 'basiccolumn'

Unable to implement:
select * from t_bill bill left join t_trade trade on trade.id=bill.trade_id and **bill.del=false**

There is an SqlBuilder method for creating a BasicColumn with a constant value. You can do  constant("false") for this case.


Adjustments in scrollbar calculations

Still slightly off but it looks decent.

Done is separate commit with extras. :)


[SYS-2803] Fix terraform destroy slow

Reverting what is included in the v2.9.0 version, as we noticed slow Terraform destroy from that version onwards.
Using local variable, this slow destroy issue is resolved.

Output from the TF destroy test - MIS instance is uninstalled below 15min:
00:14:25.196  Destroy complete! Resources: 44 destroyed. 00:14:25.196  2020/06/04 20:00:54  ### Task multi_instance_network destroy - SUCCEEDED! ### 00:14:25.196  2020/06/04 20:00:54 === Destroying cloud network resources:  - DONE === 00:14:25.196  2020/06/04 20:00:54 Done!


Since DRF 3.2 now supports Django 1.8 can we update this to as well?

As above

do you mean all the deprecated things like request.data vs request.DATA, etc?

It was more of a question, the README states that this doesn't support >Django1.7 since DRF 3 does not but DRF 3.2(which I believe to be the current version) does. Do you foresee anything breaking if I try to use this 1.8 and DRF 3.2?

Sorry for late response. At the conference now. When I get back Ill verify that it works with 3.2 but as far as I know it should still continue working with 3.2. If not Ill fix that and will add a patch.

That would be great, thanks. I have it up and seemingly running on 3.2 so it shouldn't take much work if any! Thanks again.

I think this could be better clarified in the README to explain DRF < 3.0 requires Django < 1.8, but DRF > 3.0 has no specific Django requirement (it follows the DRF requirements).


Add support for setMaxInboundMessageBodySize

This commit adds an additional parameter to #connect to support setting the maximum size of inbound messages.

Note: This commit re-adds the ability for users of this library to consume messages larger than the default message body size of 64MiB, that was removed due to the change in the Java client in #162


Clarification needed on Datasheets

Currently there are around 3-4 versions or revisions of the AHT20 datasheets running around online from the manufacturer.
They all seem mostly similar but have various translation mistakes and disagree with each other on what bits are reserved or not.
The data sheets in question also list parameter bytes that have an unexplained purpose.
These need to be looked into and some tests need to be preformed with the physical sensor to ensure that the data-sheets and physical hardware correspond to each-other correctly.
I'm thinking maybe building a small tool/program to interactively allow I2C usage. Or perhaps another way to verify sensor functionality.
GOALS

[ ] Build More cohesive datasheet?
[ ] Document sensor interactions.
[ ] Build I2C sensor verification program?

So far I'm moving forwards by doing my best to just kinda glue the datasheets info together in the code implementation.
I think verification will have to be done physically on the bluepill+sensor combo.
So I'll work on figuring that part out next.

Datasheets v1.0 and v1.1 are in conflict. Under section 5.4 in both datasheets they have conflicting information of the 6bytes of data they are supposed to send.
V1.0 indicates two 20bit sequences for the humidity and temperature respectively;
where as v1.1 indicates a 24bit humidity reading and a 16bit temperature reading.
V1.1

V1.0

Example data

I've documented the sensor interaction in the test's I've written using the actual data.


add SubmitEvent to web_sys Event types

The SubmitEvent should be included in the list of event types.
Related issues:
https://github.com/rustwasm/wasm-bindgen/issues/2712
https://github.com/yewstack/yew/issues/2691

👍


Error with AOT compilation and filereplacement

🐞 Bug report
Command (mark with an x)

[ ] new
[ x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 I don't know, I have this problem after some changes, but I did I lot and don't know exactly when stars
(by the way, I have open other similar issue in STOF
https://stackoverflow.com/questions/62590862/differences-between-angular-compilations
Description
 AOT compilation do a lot of checks I don't know if are mandatory but made imposible to reduce the size of the app
🔬 Minimal Reproduction

In angular.json I hava a filereplacemente
{
  "replace": "src/app/pages/bookappointments/bookappointments.page.ts",
  "with": "src/app/customizations/database/bookappointments.page-database.ts"
},

but when try to compile with aot have this error:
🔥 Exception or Error
`ERROR in : Couldn't resolve resource ./bookappointments.page.scss relative to D:/desarrollos/PatientPortal/front/src/app/customizations/database/bookappointments.page-database.ts`

And it's true, relative to this file I don't have the bookappointments.page.scss, but I have relative to the one wich replace, src/app/pages/bookappointments/bookappointments.page.ts
🌍 Your Environment

"@angular/cli": "^8.0.1",
Anything else relevant?

I want to understand it well because I preffer to use it to compile, but with this errors I can't, and in this case I think my code is ok and I don't want to duplicate it.

I ask too this in STOF
https://stackoverflow.com/questions/62636616/aot-compilation-and-filereplacement
but I really thing is a bug. Sorry if not

This is expected and working as intended.
When using fileReplacements only the contents of the file is replaced. Think of it as a copy and paste.
To get around this, you need to update the templateUrl and styleUrl‘ to be relative from bookappointments.page.ts`. In general, I wouldn’t recommend in replacing a component file. This functionality is mainly intended to replace configuration files.


Few questions

Hi,
Thanks for great extension. have couple of doubts, Hope you help me clear those :

How to handle api request which has expired token?
How to validate token manually in some cases?
How to expire token forcefully?

Thanks

#43


Pull users for a Jira project

Pull the list of users on a Jira project and make them the default for autocomplete when assigning a user.
Can non project admins list the users on a project?
Refs #39

Closed in favour of #116


encoding/xml: Expose xml.Decoder.line

What version of Go are you using (go version)?

$ go version
go version go1.15.1 linux/amd64

Does this issue reproduce with the latest release?
yes
What did you do?
Creating custom XML schema validator.
What did you expect to see?
It would be great to expose xml.Decoder.line. Creating custom errors with line numbers is better then offset. The offset is already available through InputOffset() method.

Merging into proposal #45628


better stats printer

Codecov Report

Merging #7 into master will decrease coverage by -0.64%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
- Coverage   89.13%   88.49%   -0.64%
==========================================
  Files           7        7
  Lines         690      704      +14
==========================================
+ Hits          615      623       +8
- Misses         75       81       +6

Impacted Files
Coverage Δ

voropy/about.py
100% <100%> (ø)
:white_check_mark:

voropy/mesh_tri.py
92.15% <25%> (-1.25%)
:x:

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 40128d6...e2d8749. Read the comment docs.


RTL auto-detection makes PostMeta messy

Describe the bug
RTL auto-detection causes @-character in PostMeta to be misplaced.
To Reproduce
Steps to reproduce the behavior:
See https://bsky.app/profile/pastures.bsky.social for example.
Expected behavior
@-character should always precede the handle, since the handle is inherently LTR-text, event if the display name is RTL-text.
Screenshots

Details

Platform: Android and Windows Edge. Presumably iOS also.
Platform version: 13 / 126
App version: 1.86

Additional context
This behavior appears to be the output of the BIDI algorithm, see this post for a link to the spec and a playground.
I consider this a minor inconvenience considering the overall state of Bluesky RTL support, but have a fix in mind that I will contribute soon.

Here's how Signal handles Unicode bidi, seems worth taking a look
https://github.com/signalapp/Signal-Desktop/blob/ce0fb220411b97722e1e080c14faa65d23165784/ts/util/unicodeBidi.ts#L124

Merged this in, thank you!


fix the mime database generation

if only one package (for example: shared-mime-info) provides mime data, then $out/share/mime/packages is a symlink into it, which is read-only, causing the mime-database to not generate
this change resolves the issue and fixes a large portion of xfce

@vcunat looks good to me? share/mime has to be writable, not share/mime/packages, right?

I believe the command is supposed only to update/create share/mime/mime.cache, but I only re-skimmed the man page and specs ATM. This PR certainly seems an improvement. It can still happen e.g. that share/mime is a symlink, but that seems a seldom case.


chore(lint): lint staged integration

In the scope of this PR I added lint-staged integration in order to run pre-commit checks only on files that are staged. This small change will speed up committing process

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

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Rasperry image has no LAN drivers?

This might be a stupid question, so I am sorry in advance, but when i install the Pi image to my 1B+ the LAN port doesn'T work.
So I was wondering if the Pi image maybe is missing the NIC drivers?

I'm surprised that the pi image boots at all on a 1!
The image is built for arm64, which should only work on a 3/4 (maybe a 2?), but I cant vouch for the reliability of anything below a 4. It may or may not have the same usb reliability issues experienced with companion-pi.
That said, I am running a couple of non-streamdeck devices off a zero-w2. I am having issues with wifi, but I think that is unrelated to satellite or the usb device connected.
I don't think I am using the satellite image currently for it, I think I installed it before making the image

Thanks @Julusian for the reply.
Would it be possible to install companion satellite under the rasperryOS?
The OS works fine, incl. the nic, so if i could install it under the OS it might even work :)

The image is raspberrypi os, but the 64bit version. That image shouldnt have booted at all on that model, as its not a 64bit cpu..
It is possible to install manually on the 32bit os, but from memory running nodejs on the pi 1 was tricky, as noone builds or distributes it for armv6 (most places do armv7)
There are some rough steps in the readme https://github.com/bitfocus/companion-satellite#manual-headless--raspbrry-pi.
Im going to close this, as this is kind of by design, or hopefully you managed to figure something out


Fix 'clear all' deselecting components while dependents are still selected

Turns out one can select a component with its dependencies in one channel, then switch to a different channel and use 'clear all' to simply deselect the dependencies without the original item.
Example: select Java Development in Guided Development channel -> go to Java Development channel -> click Clear All -> everything in Java Dev channel gets deselected even though Guided Development is still selected
This PR should check if the deselected component still has something depending on it before committing.

test this

test this

Codecov Report

Merging #1395 into master will decrease coverage by 0.61%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master    #1395      +/-   ##
==========================================
- Coverage   92.67%   92.06%   -0.62%
==========================================
  Files          47       47
  Lines        4904     5003      +99
  Branches      548      865     +317
==========================================
+ Hits         4545     4606      +61
- Misses        359      366       +7
- Partials        0       31      +31

Impacted Files
Coverage Δ

browser/pages/selection/controller.js
84.21% <83.33%> (-1.67%)
:arrow_down:

browser/model/devstudio-autoinstall.js
97.29% <0%> (-2.71%)
:arrow_down:

browser/pages/install/controller.js
91.86% <0%> (-1.75%)
:arrow_down:

browser/model/helpers/downloader.js
95.53% <0%> (-1.68%)
:arrow_down:

browser/model/che.js
95% <0%> (-1.62%)
:arrow_down:

browser/model/jdk-install.js
93.78% <0%> (-1.51%)
:arrow_down:

browser/services/platform.js
98.14% <0%> (-1.48%)
:arrow_down:

browser/pages/account/controller.js
98.61% <0%> (-1.39%)
:arrow_down:

browser/model/cdk.js
97.6% <0%> (-1.16%)
:arrow_down:

... and 25 more

Continue to review full report at Codecov.

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


Suggest mixin and formatter names in -st-named when importing from JS/TS

Mixins and formatters are not suggested in -st-named when importing from JS/TS.

Fixed. JS mixins are now suggested for import.


wasm: re-use //export mechanism for exporting identifiers within wasm modules

Right now, compiling the following piece of Go code:
package main

func main() {
	println("hello")
	println("1+3=", MyAdd(1, 3))
}

//export MyAdd
func MyAdd(i, j int32) int32 {
	return i + j
}

like so:
$> GOOS=js GOARCH=wasm go build -o foo.wasm ./main.go

will produce the following foo.wasm module:
$> wasm-objdump -h ./foo.wasm

foo.wasm:	file format wasm 0x1

Sections:

     Type start=0x0000000e end=0x00000048 (size=0x0000003a) count: 10
   Import start=0x0000004e end=0x000000ce (size=0x00000080) count: 6
 Function start=0x000000d4 end=0x0000042c (size=0x00000358) count: 854
    Table start=0x00000432 end=0x00000437 (size=0x00000005) count: 1
   Memory start=0x0000043d end=0x00000442 (size=0x00000005) count: 1
   Global start=0x00000448 end=0x0000047b (size=0x00000033) count: 10
   Export start=0x00000481 end=0x0000048f (size=0x0000000e) count: 2
     Elem start=0x00000495 end=0x00000acf (size=0x0000063a) count: 1
     Code start=0x00000ad5 end=0x000a3b7a (size=0x000a30a5) count: 854
     Data start=0x000a3b80 end=0x001290fd (size=0x0008557d) count: 7
   Custom start=0x00129103 end=0x0012f117 (size=0x00006014) "name"

especially:
$> wasm-objdump -j export -x ./foo.wasm

foo.wasm:	file format wasm 0x1

Section Details:

Export:
 - func[750] <_rt0_wasm_js> -> "run"
 - memory[0] -> "mem"

ie: the user can not control what is exported.
the recommended way to export something currently, is to use js.NewCallback.
this is - mainly - because one needs to setup a few things for the Go and js runtimes to cooperate nicely together.
I would argue that, in the same spirit than when one compiles the same main.go file with -buildmode=c-shared, it should be possible to achieve the same thing for GOOS=xyz GOARCH=wasm, and only export what is //export-ed.
initialization of the runtime(s) would be performed via the wasm module's start function.
(this is a re-hash of neelance/go#22.)

I've hit the same rough patches after doing some "real" work with wasm in Go, and trying to integrate my module into a JS workflow.
To me, the primary issue is how Go functions are provided to JS. Presently, it seems that polluting the global object (window) with Go functions is the only route. The method I've found to keep collisions to a minimum is to declare a new map[string]interface{} as a "namespace" which translates to a JS Object. Then to use this object to add typed js.Funcs:
func main() {
	done := make(chan struct{})
	js.Global().Set("protolock", make(map[string]interface{}))
	module := js.Global().Get("protolock")
	module.Set("initialize",
		js.FuncOf(func(this js.Value, args []js.Value) interface{} {
			if args == nil {
				fmt.Println("initialize: not enough args")
				return nil
			}

			return toJson(initialize(args[0].String()))
		}),
	)
	module.Set("status",
		js.FuncOf(func(this js.Value, args []js.Value) interface{} {
			if args == nil || len(args) < 2 {
				fmt.Println("status: not enough args")
				return nil
			}

			return toJson(status(args[0].String(), args[1].String()))
	}))
	<-done
}

While this works, it doesn't make for a very seamless integration with modern JS workflows. Ideally, we'd be able to generate at minimum a .d.ts file and stubs for the JS functions made available from the wasm module, to fit into the ES6 import style used by the majority of JS toolchains (webpack, rollup, etc).
wasm-pack does a pretty good job with this, but it's not clear to me how we can achieve a similar experience with Go. Ideally, there would be a common interface to populate the instance.exports object, and to generate those populated functions as stubs that wrap an invocation of instance.exports.myFunc in a JS package which can be imported by other JS code.
This would make the interoperability between wasm modules in a JS environment much simpler, hiding the fact that a function is run in wasm.
I'm not sure the //export  mechanism is right, which would complicate go build, and lock Go into a particular way of doing things. I'm not opposed to using //export , but would like to consider an option that doesn't need to be as deeply integrated. Rather, some code-gen tooling to read Go AST, output JS stubs and definition files (in ES6 module format). The tooling would need to be aware of how the compiled Go code translates into accessible JS calls - and this is the part where I need to do more digging... I'm very interested in helping out here, but I think there is more discourse to be had around the workflow.
Do we have a working doc/wiki anywhere to track this? I couldn't find anything in an admittedly rather shallow search. Happy to kick it off if one does not exist yet.

I'm not sure the //export mechanism is right, which would complicate go build, and lock Go into a particular way of doing things. I'm not opposed to using //export , but would like to consider an option that doesn't need to be as deeply integrated.

After more digging and a quick browse through @neelance's wasm implementation as well as the disassembled .wat of a Go compiled .wasm binary, it's much more clear that the //export semantics are definitely needed.. I have a hacked together PoC of some AST tooling that generates the JS bridge code, but its nowhere near the ideal. Having control of what is explicitly provided to the instance.exports is the most usable way for JS integration, and hopefully future wasm->wasm module imports.

TinyGo exposes this functionality via a //go:export pragma. Personally I don't really like magic comments, especially when there is a way to do this in pure Go with syscall/js.

//export vs //go:export seems like just a difference in the specific text fragment to use.
The meaning for each approach seems the same though: "this function should be included in the wasm exports list, functions without it will not be".
@johanbrandhorst When you say there's a way to do it in pure Go with syscall/js, what are you meaning?

//go:export is basically an alias for //export in TinyGo so you could use that as well.

I mean that you can also do
js.Global().Set("myexport", js.FuncOf(func(this js.Value, args []js.Value) interface{} {
    //stuff
})

the point of my original request is exactly to not only target and support js, but also browser-less environments, especially now with wasi picking up speed. (my own original use case being wagon)

It'll be hard to say whether we'll have the same capability to set exports via syscall/wasi until work has begun on that, so we can't really judge whether we'll need the pragma for that use case either. Don't we all agree that magic comments are pretty smelly?

the wasm can't be used in webworker also.

Why can’t the wasm be used in a webworker?

@pkieltyka because the exported function is mounted on window or global variable, but in webworker, we should add it on self

Shouldn't standard Go exporting rules be used?
ie. all functions beginning with an uppercase letter would be exported.

I was coming from the cgo machinery when I wrote that.
but you do have a point, even if there is a bit of an uncanny valley effect wrt the fact that, right now, a Wasm module needs (AFAIR) to be a main Go package.
taking a regular Go package (non-main), and populating the resulting Wasm module with the Go-exported functions using the regular Go-exporting rules would go a long way towards making the Go->Wasm experience more streamlined (and in line with the usual expectations of a Go developer).

Note that exporting all Go symbols starting with an uppercase character may drastically increase file size, as the linker won't be able to do dead code elimination. I'm not sure whether this is happening right now, but it's something to keep in mind.

the point of my original request is exactly to not only target and support js, but also browser-less environments, especially now with wasi picking up speed. (my own original use case being wagon)

Agree, i would love to experiment golang wasm target for extending a golang software through a plugin like mechanism, running it in wasm intepreters like https://github.com/go-interpreter/wagon, https://github.com/perlin-network/life or https://github.com/wasmerio/go-ext-wasm

Note that exporting all Go symbols starting with an uppercase character may drastically increase file size, as the linker won't be able to do dead code elimination. I'm not sure whether this is happening right now, but it's something to keep in mind.

I would imagine only the Go symbols in the root/main package would need to be exported.

Another possible option would be a compiler(or linker) argument with a list of functions that need to be exported.

Please see https://github.com/golang/go/issues/38248, which I believe solves the same issue in a different way.

I have been adding exports to the global Go object, which is created by wasm_exec.js. Something does need to be done about this but ideally it would also generate bindings (like rust's wasm-bindgen) so you are not limited to exporting functions of specific numbers of int32, int64, f32, and f64.

There are some really great thoughts on this issue, but I'm curious about the current direction and magnitude of momentum on this topic.
After scanning the open issues, I've come to the following two conclusions for myself:

There is a lot of sense in having a go build mode for the purpose of generating more idiomatic WASM modules.  E.g., modules that export functions that are actually intended to be used in human-written code like JS in a browser.  This has been mentioned by @sbinet here and @cherrymui in https://github.com/golang/go/issues/29108.  Though there are other apparent pain points that I imagine could be addressed with such a build mode.  Perhaps the use of a start function, or even factorization of the Go runtime into another module?
Go already has handy export semantics on the package level, and (as implied by @Splizard) these semantics can be used with a new build mode to determine what is exported in the WASM module.  Presumably, only what is exported by the "root" package should be exported in the module.  Perhaps there is still a need for special directives to give details, but there is also kind of a way to implicitly declare imports in a go build mode specific to idiomatic WASM modules: declare a function prototype without a body.  AFAICT, this is being explored already in tinygo.

At a high level: it is currently painful to turn Go code into useful and concise WASM.  The lack of idiomatic use of modules appears to be at the heart of that pain.

Way late in the comment process, but the ability to mix host binary code along with WASM code linked into the same binary and not be forced to have 2 separate projects, each with its own GOOS= GOARCH= .  Just my 2 cents here.

@nilslice I know it has been a long, long time since you wrote this:

To me, the primary issue is how Go functions are provided to JS. Presently, it seems that polluting the global object (window) with Go functions is the only route.

I'm currently looking at how to make it possible to mix wasm modules compiled with different versions of Go or TinyGo in the same application.   I can't see any way to do this using the stock wasm_exec.js as long as Go() itself is a global.  I'm considering starting a Go proposal which would completely remove globalThis from wasm_exec.js.  Do you recall if you tried that yourself way back when?
Extism completely bypasses this problem and enables both mixed-version as well as mixed-language apps via its plugins, right?  Skimming through the code, it looks like you're using Rust as the runtime entrypoint, which gives you more flexibility in the first place versus what's implemented in Go's wasm_exec.js?

@stevegt

I know it has been a long, long time since you wrote this

:smile: wow, has it really been 5 years!? ...a long time indeed!
To be honest, I'm not sure I tried TinyGo back then. I can see how what aiming to do is challenging though. If you're able to, it might help to drop support for anything syscall/js provides and only use wasip1 as the GOOS. In the browser, you'd polyfill WASI with something like https://github.com/bjorn3/browser_wasi_shim on the "host" side. Both TinyGo and Go can target this environment, but it's up to you to plumb through the imports to give the modules access to anything on the JS side.

Extism completely bypasses this problem and enables both mixed-version as well as mixed-language apps via its plugins, right? Skimming through the code, it looks like you're using Rust as the runtime entrypoint, which gives you more flexibility in the first place versus what's implemented in Go's wasm_exec.js?

Yes, Extism bypasses this probelm entirely enabling precisely what you mention. However, in the browser, we have a pure TypeScript implementation of the Extism ABI / runtime. So it doesn't require Rust at all. Extism was created to solve the problem you describe, and normalize the guest/host environment to provide consistency -- not dissimilar to how jQuery smoothed over the nuances between browser APIs back in the day.
We're currently in the midst of publishing a v1.0 of Extism and are near ready to release this JS SDK (which works universally in the browser, Node, Deno and Bun): https://github.com/extism/js-sdk
If you're interested, it would be a great time to try this out and share feedback. For a JS host, please use this branch if you're also using the latest version of our PDKs.
I don't mean to clog up this issue with Extism stuff, so if you'd like to chat more about it I'm always available on our Discord or on the repo issue tracker!

I think this issue can be closed in favor of the new wasmexport proposal: https://github.com/golang/go/issues/42372.

#65199 is implemented. Closing this as a dup. Thanks.

@cherrymui https://docs.github.com/en/issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate#marking-duplicates 🙃


Minor edits to the README.

If merged, this pull request addresses some minor issues in the README — some rogue character segments, a vestigial HTML closing tag, that sort of thing.  I also added a link to the license.

Thanks for your help


Implement FatalReporter

In reporter.go, we already have AssertReporter (uses testify/assert) and RequireReporter (uses testify/require), for non-fatal and fatal assertions, respectively.
If you don't use testify, you can directly use testing.T as reporter. httpexpect will call its Errorf method, so assertions will be non-fatal.
If you don't use testify, and want fatal assertions, you have to write your own reporter that invokes t.Fatalf. It would be nice to fill this gap and provide FatalReporter that does that for you - provides Errorf method that just invokes t.Fatalf.
Note: FatalReporter should use testing.TB interface, not testing.T struct.
Note: we should also update comments for Reporter interface and Config.Reporter field. Those comments list available reporter implementations.

Can I check this?


Add blog about sunsetting docker.io publishing

@Naros Applied, thanks! When live please follow with Twitter and mailing list announcement.


Cryptography related dependencies are not represented correctly

If cryptographic values are interdependent, the “internal” cryptographic references should be used to define these relationships.
Example:
if a key dependence on an algorithm use the cryptoRef field in the relatedCryptoMaterialsProperties to reference the algorithm.

At the moment, this topic is on hold. In the current version of CBOM, there is no option to reference algorithms from other algorithms. This is necessary for many scenarios (signature algorithm uses digest algorithm). As this reference cannot be expressed via the algorithm properties and for reasons of conciseness, we present all dependencies in the Dependencies section.


Add csi node user-facing configuration

Which issue(s) this PR addresses:

Closes USHIFT-168

@copejon - could we reorganize the commits into at most 3?

Just not to forget, please, squash the commits if possible to avoid having 25 commits in history.

/kind feature

/retest

I'm happy with this version. I'd like to give @fzdarsky a chance to comment on the configuration layout and whether we want to put the storage-related settings in a subsection.
/lgtm
/hold

I have two questions:

Some files under controllers/, pkg/mdns and pkg/util contain tabulation changes in the license text. Do we want these in the current PR?
Do we need to have user documentation updated to reflect this new functionality?

I have two questions:
* Some files under controllers/, pkg/mdns and pkg/util contain tabulation changes in the license text. Do we want these in the current PR?

It seems that it won't pass the verify check otherwise.  Not sure why this is being caught now though.

* Do we need to have user documentation updated to reflect this new functionality?

I'll circle back and make sure the in-repo docs are accurate.

/retest

/retest

/retest

/retest

/hold cancel


Check metrics-mongodb.rb crashed after Sensu upgrade

Hello,
After upgrading Sensu client to latest version (currently 1.0.2) check metrics-mongodb.rb throws this error:
/opt/sensu/embedded/lib/ruby/site_ruby/2.4.0/rubygems/specification.rb:2288:in `raise_if_conflicts': Unable to activate sensu-plugins-mongodb-1.4.0, because sensu-plugin-2.3.0 conflicts with sensu-plugin (~> 1.2) (Gem::ConflictError)

I had to remove sensu-plugin gem v2.3.0 and v2.0.1, as it only works with v1.4.5>
Any idea how to fix this?

We should bump the dependency here on sensu-plugin to 2.x and release like this: https://github.com/sensu-plugins/sensu-plugins-aws/commit/a4b161986d68964f84de8b5be616d428fce223f5
This is something we need to do with almost all the plugins...Any chance you would be willing to create a PR for this?

To be clear this is not technically a bug, it is just not compatible yet with the sensu-plugin 2.x library which is included by default in sensu 1.x setups. Unfortunately I checked and did not see anything in the sensu changelog specifying that this was changed and should be called out as a breaking change like we do on plugins...

Hello @majormoses
Tell me how to fix version as I have to options.
bin/metrics-mongodb.rb
Add line:
gem 'sensu-plugin', '=1.4.5'
or /sensu-plugins-mongodb.gemspec
change
s.add_runtime_dependency 'sensu-plugin',      '~> 1.2'
to
s.add_runtime_dependency 'sensu-plugin',      '1.4.5'

well we should figure out the go forward path with updating  s.add_runtime_dependency 'sensu-plugin', '~> 2.0' this may require other changes in order to work but that is the starting point.

@mdzidic can you try validating if using that PR solves your problems? I don't have the time to figure out all the check/metric options but I can do some testing if you can give me the options you would use.

Hello,
Now I have same problem with latest metrics-mongodb.rb plugin but different sensu-plugin version.
/opt/sensu/embedded/lib/ruby/site_ruby/2.4.0/rubygems/specification.rb:2288:in `raise_if_conflicts': Unable to activate sensu-plugins-mongodb-2.0.2, because sensu-plugin-3.0.0 conflicts with sensu-plugin (~> 2.0) (Gem::ConflictError)
	from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.0/rubygems/specification.rb:1408:in `activate'
	from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.0/rubygems.rb:220:in `rescue in try_activate'
	from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.0/rubygems.rb:213:in `try_activate'
	from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:126:in `rescue in require'
	from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:39:in `require'
	from /etc/sensu/plugins/metrics-mongodb.rb:32:in `<main>'

@mdzidic are you pinning your versions? There are very few plugins that have been updated to support the 3.x release of sensu-plugins library. We follow semver and all breaking changes are made in major versions. This means that you can pin your versions and only pull in when all your plugins have been updated to support the breaking changes. If you want to open a Pull request to update it (see reference PR for the ~> 2.0 bump) otherwise I will get to it when I have the time.

Yes, I pin version but also I update Sensu client and plugins to latest version from time to time.
Okay, I'll go with pull request for ~> 3.0, thanks!


Crash on order disk by size

When running with the -d flag and trying to order by size with s - a crash occurs with the followng output:
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x55f6aa158bd8]

goroutine 1 [running]:
github.com/rivo/tview.(*Application).Run.func1()
	github.com/rivo/tview@v0.0.0-20210217110421-8a8f78a6dd01/application.go:243 +0x4d
panic({0x55f6aa38b3a0, 0x55f6aa560a90})
	runtime/panic.go:1038 +0x215
github.com/dundee/gdu/v5/pkg/analyze.(*Dir).GetPath(0x1)
	github.com/dundee/gdu/v5/pkg/analyze/file.go:139 +0x18
github.com/dundee/gdu/v5/tui.(*UI).showDir(0xc000126240)
	github.com/dundee/gdu/v5/tui/tui.go:181 +0x45
github.com/dundee/gdu/v5/tui.(*UI).setSorting(0xc000126240, {0x55f6aa1d287d, 0x4})
	github.com/dundee/gdu/v5/tui/tui.go:382 +0x15a
github.com/dundee/gdu/v5/tui.(*UI).keyPressed(0xc000126240, 0xc000010040)
	github.com/dundee/gdu/v5/tui/keys.go:119 +0x6cc
github.com/rivo/tview.(*Application).Run(0xc000220000)
	github.com/rivo/tview@v0.0.0-20210217110421-8a8f78a6dd01/application.go:318 +0x6d2
github.com/dundee/gdu/v5/tui.(*UI).StartUILoop(0xc000126240)
	github.com/dundee/gdu/v5/tui/tui.go:163 +0x22
github.com/dundee/gdu/v5/cmd/gdu/app.(*App).Run(0xc000137d60)
	github.com/dundee/gdu/v5/cmd/gdu/app/app.go:120 +0x2d2
main.runE(0x55f6aa566300, {0xc00008cb80, 0x0, 0x1})
	github.com/dundee/gdu/v5/cmd/gdu/main.go:96 +0x418
github.com/spf13/cobra.(*Command).execute(0x55f6aa566300, {0xc0000aa010, 0x1, 0x1})
	github.com/spf13/cobra@v1.1.3/command.go:852 +0x60e
github.com/spf13/cobra.(*Command).ExecuteC(0x55f6aa566300)
	github.com/spf13/cobra@v1.1.3/command.go:960 +0x3ad
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.1.3/command.go:897
main.main()
	github.com/dundee/gdu/v5/cmd/gdu/main.go:100 +0x25

Appreciate there isnt much system debug information here, so please advise what, if anything you'd like to know and I can get it and provide.

Ah ok that makes sense why it doesn’t work then! =)
To be honest didn’t check if it was a feature or not - just went for it as am performing a home server migration and wanted to quickly see where the bulk of space was being used across drives.
Perfect use case and way quicker than ncdu.
Thanks for the great project.

Sorting of devices added in 5.7.0


Process ignored paths while being aware of RequestUrlPrefix

Fixes #8383
If there is a ReequestUrlPrefix, and the url we are processing begins with it, try to remove it. But also try to keep it for retrocompatibility with current configurations.
basically:
RequestUrlPrefix: "foo"
Request Url: "/foo/bar"
We test whether we should ignore either "/bar" or "/foo/bar".
The second test in this example is to ensure that anything that works before this change, keeps working afterwards.
If there is no RequestUrlPrefix, nothing changes compared to the current.
I took the liberty of caching the urls to ignore, evicting that cache whenever the cache for the settings as a whole is also evicted.

Should I merge this myself?

Yes, if we approve, since you have merge commits. Use Squash/Merge. We mentioned it at our last meeting.


Using reef.polyfills.es causes "Proxy polyfill does not support trap 'deleteProperty'" error in IE 11

There is no codepen since it can't be tested in IE.
I was getting an error in IE when using the pollyfill version of Reef.
Unhandled promise rejection TypeError: Proxy polyfill does not support trap  'deleteProperty'
After some digging online it looks like most Proxy polyfills do not support deleting object properties. Only get and set. So for my situation I commented out line 166 through 170
deleteProperty: function (obj, prop) {
    delete obj[prop];
    debounceRender(instance);
    return true;
}

But then I was getting this error:
Unable to get property 'childNodes' of undefined or null reference
After debugging in IE, the error was on line 647, inside of the stringToHTML function. For reasons I couldn't figure out, the head element was returning a null value. For my situation I commented out the following if statement inside of the stringToHTML function.
if (support) {

  // Create document
  var parser = new DOMParser();
  var doc = parser.parseFromString(str, 'text/html');

  // If there are items in the head, move them to the body
  if (doc.head.childNodes.length > 0) {
    Array.prototype.slice.call(doc.head.childNodes).reverse().forEach(function (node) {
      doc.body.insertBefore(node, doc.body.firstChild);
    });
  }

  return doc.body;

}

Forcing Reef to use the old school method.
var dom = document.createElement('div');
dom.innerHTML = str;
return dom;

It's like you read my mind. I was just looking into this today!

Let me know if you need me to test anything on PC. I'd be happy to help out!

Fortunately, I have access to a windows machine for testing, but thanks!
This should be fixed with v7.3.2 (including the stringToHTML() issue). Let me know if it's still not working for you, though.


feat: Add access to Chrome DevTools Protocol

In another project, CefSharp, we generated code based on the CDP of the browser which can be downloaded from http://localhost:9222/json/protocol which looks something like this: https://raw.githubusercontent.com/cefsharp/CefSharp/master/CefSharp/DevTools/DevToolsClient.Generated.netcore.cs
So the user can use actual types / events and sees the documentation instead passing strings / dictionaries around.
Would that also be something you would want to add / support?
(The CDP to csharp parser itself isn't public.)


Adding the timesync_ntp_allow variable for setuping a server as source server

We started to use the role in a private cloud and we are using a single server that connect to externals ntp servers for synchronization while other are offline.
We would like to use it as an NTP server and client at the same time.
From what I read we need to use the configuration allow https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sect-understanding_chrony_and-its_configuration
We should add a new variable to handle this in timesync/templates/chrony.conf.j2, for example:
timesync_allow_network:
  - ip_net: <IP_ADDRESS>/24

Which would result in the vars like this:
{% if timesync_allow_network is defined %}
{% for value in timesync_allow_network %}
{{ 'allow' if 'ip_net' in value and value['ip_net'] }} {{value['ip_net'] }}
{% endfor %}
{% endif %}

Resulting in in the configuration as follow :
allow <IP_ADDRESS>/24

As currently documented, this role is meant only for configuring NTP clients and/or PTP slaves. It might make sense to extend it into a NTP server, but we need to consider all supported use cases and how it will work with future improvements. For instance, if the role is configured with a single PTP domain, there is no ntpd/chronyd currently running. Should it be started? Or would it be better to rely on a separate "NTP server" role?
PR #46 is a similar issue.

Use timesync_chrony_custom_settings


cosign-artifacts: all release artifacts

Sign release artifacts and provide documentation about how to verify them.
The following public artifacts-generating jobs need caching under /artifacts in order for this to function properly.

[ ] helm-release-nexus
[ ] helm-release-ecr
[ ] python-release-poetry
[ ] python-release-setuptools
[ ] docker-github
[ ] docker-hub

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

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


Do "smart" dumping of tests

The client currently writes to every single test file regardless of whether or not they have changed. Add a "modified" attribute to each serilizable object and only right to files that contain modified objects.
Safely dump files -- right now if an error occurs in ok_main, test files might get corrupted
Add a --no-save flag to choose never to dump, even if tests are modified

Test dumping works fine.


[4.3.0] Update instructions for deployment patterns

Description
Need to remove the links to the deployment patterns from the Deploy Integrations Using Helm Resources page as MI currently does not support them.
Once the deployment patterns are defined for MI, need to update the documentation.

https://github.com/wso2/helm-mi/pull/12

This will be removed via https://github.com/wso2/docs-mi/pull/842.

@DinithiDiaz @KalinduGandara can we close this git issue now?

Fixed already


Jenkins sample ch.5 broken - client is newer than server

The Jenkins example in ch.5 does not build. Please assist.
Error message is:
Error response from daemon: client is newer than server (client API version: 1.24, server API version: 1.21)

I enclose complete log fro the failing run, strangely IMAGE is set to kB\t\t, which does not make sense. Must be the result of some wrong output during the fawlty build.
NB: the tr -d "\t" is not present in the sample script in your book; it is an attempt of mine to execute the following sudo docker run, but the image name is hopelessly wrong.
Thank you for your attention.

Started by user admin
Building in workspace /var/jenkins_home/jobs/Docker_test_job/workspace
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/jamtur01/docker-jenkins-sample.git # timeout=10
Fetching upstream changes from https://github.com/jamtur01/docker-jenkins-sample.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/jamtur01/docker-jenkins-sample.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 82216cfafe447662b00832d4a4aca83413cb87fd (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 82216cfafe447662b00832d4a4aca83413cb87fd
 > git rev-list 82216cfafe447662b00832d4a4aca83413cb87fd # timeout=10
[workspace] $ /bin/sh -xe /tmp/hudson1308588033301505213.sh
+ sudo docker build .
+ tail -1
+ awk { print $NF }
+ tr -d \r
Error response from daemon: client is newer than server (client API version: 1.24, server API version: 1.21)
+ IMAGE=kB
+ MNT=/var/jenkins_home/jobs/Docker_test_job/workspace/..
+ sudo docker run -d -v /var/jenkins_home/jobs/Docker_test_job/workspace/..:/opt/project/ kB /bin/bash -c cd /opt/project/workspace && rake spec
docker: Error parsing reference: "kB" is not a valid repository/tag.
See 'docker run --help'.
+ CONTAINER=
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Finished: FAILURE

A bit of info more. I am running Docker 1.9. Reading better the beginning of the book, I see it mentions that the content is focused on 1.12.
I am using Ubuntu 15.04 (vivid). Release 1.9 is what the standard Docker install procedure delivers on my laptop. Can I use 1.12 with vivid, or there's no hope?

Solved after upgrading to Xenial. Thank you for your assistance.


parallel in github actions

I think ECS should run in parallel mode per default on github actions.
I searched the codebase but could not find indication, whether ECS runs in parallel mode in github actions or not.
Is this something you considered, or maybe the tool is even doing already, but I just was not able to find it?

The parallel is enabled by default, unless told not to :) https://github.com/symplify/easy-coding-standard/blob/c0b63d80c2fcdc6bb87e1cb62aa72acaa9064f5c/config/config.php#L46-L47
The problem is, Github Actions have only 2 cores (AFAIK), so the performance improvement is no that high for parallel tools.

I see thx.
the way the readme is written I got the feeling one needs to enable the parallel mode explicitly
https://github.com/symplify/easy-coding-standard#parallel-run

That README needs and update :)

Done :+1:


REFACTOR-digitalmarketplace-api/app/main/views/users.py

Standardise imports
Move helper function to live at top of file

Looks like you made Flake 8 sad :joy:

@TheDoubleK Whaaaaa?? It's flake8ing the git refs 🤔

@TheDoubleK https://github.com/alphagov/digitalmarketplace-api/pull/697

Yeah good call, those utils files are a bit weird but there is another view helper in there. I think those files would make more sense in app/main/views/utils/supplier_utils.py. And then stuff like app/service_utils.py::commit_and_archive_service would live in app/main/models/utils/service_utils.py. Maybe that's overkill but feels like there's a logical split there. Not exactly the most urgent thing to do.


Improving JSONLD output

Fixing dc:publisher, @context and @id.
Separate dc:date and dcterms:created (fixes #81)
Using ISO 639 language codes (fixes #82)

Looks good


Check whether subscript is present in config

Otherwise missing subscripts (eg, from changing the config to an empty object) are replaced with undefined.

Thanks, makes sense!


[misc][cuda] use nvml query to avoid accidentally cuda initialization

fixes https://github.com/vllm-project/vllm/issues/6004

Should we add a test to catch #6004? The distributed tests are already pretty overloaded though.

@robertgshaw2-neuralmagic can you add a followup pr to add GPTQ with tp > 1? I cannot find it in existing tests. I manually tested it locally, and it works with this PR.
from vllm import LLM, SamplingParams
prompts = [
    "Hello, my name is",
    "The president of the United States is",
    "The capital of France is",
    "The future of AI is",
]
sampling_params = SamplingParams(temperature=0.8, top_p=0.95)
llm = LLM(model="TheBloke/TinyLlama-1.1B-Chat-v1.0-GPTQ", tensor_parallel_size=2)
outputs = llm.generate(prompts, sampling_params)

# Print the outputs.
for output in outputs:
    prompt = output.prompt
    generated_text = output.outputs[0].text
    print(f"Prompt: {prompt!r}, Generated text: {generated_text!r}")

@DarkLight1337 I think we can go with this PR first, and add GPTQ test later.