Curl install on RHEL 7.3 encounters "command not found"

Description
Outline the issue here:
sudo curl -L https://aka.ms/InstallAzureCli | bash
results in:
bash: line 33: /tmp/azure_cli_install_tmp_5U1E: Permission denied
So I tried this:
sudo bash /tmp/azure_cli_install_tmp_5U1E
resulted in a whole bunch of "command not found" on things like "from", "import", "try".
How should I be invoking this?
Attached is my terminal session with all of the output.
Terminal Saved Output - AzureCLI install.txt

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: Curl
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here: Whatever is at https://aka.ms/InstallAzureCli today
OS Version: What OS and version are you using?
Answer here: Red Hat Enterprise Linux Server release 7.3 (Maipo)
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: bash

@JanaJensen It's a Python script so sudo bash /tmp/azure_cli_install_tmp_5U1E wouldn't work.
You can use sudo /tmp/azure_cli_install_tmp_5U1E and the script will find a version of python on the machine and use that.
Alternatively, sudo python /tmp/azure_cli_install_tmp_5U1E and you specify your own python executable by replacing python to another python.

Thank you! That worked!


Momentum based scrolling

There may be a use for this, if anyone wants. I imagine a use case as something like scrolling while scanning a document, then hitting a key to stop the scroll.

I think I'm going to pass on this, in general.


⚠ ClamAV has degraded performance

In c8bc992, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 67 ms

Resolved: ClamAV performance has improved in 321eb18.


cannot set metrics temporality preference to use exponential bucket histogram

Is there an existing issue for this?

[x] I have searched the existing issues

Describe the bug
Using a Java app and the Java otel agent 2.8.0, when I tried to use the standalone dashboard http metrics did not display in chart and the table view said 'no metrics data found'

We use New Relic as our o11y platform, and configure the following in our apps:
otel.exporter.otlp.metrics.temporality.preference=delta
otel.exporter.otlp.metrics.default.histogram.aggregation=BASE2_EXPONENTIAL_BUCKET_HISTOGRAM

If both of those are set as above, the graphs & table charts for http.client.request.duration and http.server.request.duration don't show data.
If I change it to (the defaults for the Java agent):
otel.exporter.otlp.metrics.temporality.preference=cumulative
otel.exporter.otlp.metrics.default.histogram.aggregation=EXPLICIT_BUCKET_HISTOGRAM

then the charts display as I expect -- percentiles, exemplars all seem happy

Expected Behavior
If the bucket type is not supported, I'd still expect to see an error or warning in the table view.
It'd also be good to have some note in the documentation about supported formats -- should apps set cumulative or delta temporality? which histogram types are supported?
Steps To Reproduce
ran standalone local dashboard:
docker run --rm -it -p 18888:18888 -p 4317:18889 -p 4318:18890 -d --name aspire-dashboard -e DOTNET_DASHBOARD_UNSECURED_ALLOW_ANONYMOUS="true" mcr.microsoft.com/dotnet/aspire-dashboard:8.1.0

ran my application with the following env vars to direct it to the localhost:4317
OTEL_EXPORTER_OTLP_PROTOCOL=grpc
OTEL_LOGS_EXPORTER=otlp
OTEL_METRICS_EXPORTER=otlp
OTEL_TRACES_EXPORTER=otlp
OTEL_METRIC_EXPORT_INTERVAL=1000

Exceptions (if any)
No response
.NET Version info
No response
Anything else?
Aspire dashboard version: 8.1.0
JRE version:  temurin-17.0.7
Java OTel agent version: 2.8.0

Triage: Great feature request but it's not on a radar currently. We'll leave this issue open to get broader feedback.


TS AutoImport deep vs shallow imports

From @bradzacher on November 20, 2017 4:12
I noticed that when doing an autoimport in TS, code seems to prefer deep imports over shallow ones.
I.e. when working with graphql, if you try and import GraphQLString, code places this import import { GraphQLString } from 'graphql/type/scalars'; instead of using the import on the base package import { GraphQLString } from 'graphql';.
It would be good if code could detect this and prefer shallow imports where possible.
Esp with node module imports, because doing a deep import can technically be fragile (i.e. a module author may not intend you to import from one of the modules' internal folders).
Copied from original issue: Microsoft/vscode#38744

Possible duplicate of #19694

Should be working correctly in latest drop of TypeSript (typescript@next). VSCode ships with an older version of TypeScript. Please see Using Newer TypeScript Versions documentation for more details on updating your VSCode to use a different version of TypeScript.


msdd_model.diarize() RuntimeError: shape '[138, 50, 16, 192]' is invalid for input of size 84787200

Hello,
I have an issue while running the notebook with the msdd_model.diarize() method:
[NeMo I 2023-11-24 10:01:36 msdd_models:1092] Loading pretrained diar_msdd_telephonic model from NGC
[NeMo I 2023-11-24 10:01:36 cloud:58] Found existing object /root/.cache/torch/NeMo/NeMo_1.20.0/diar_msdd_telephonic/3c3697a0a46f945574fa407149975a13/diar_msdd_telephonic.nemo.
[NeMo I 2023-11-24 10:01:36 cloud:64] Re-using file from: /root/.cache/torch/NeMo/NeMo_1.20.0/diar_msdd_telephonic/3c3697a0a46f945574fa407149975a13/diar_msdd_telephonic.nemo
[NeMo I 2023-11-24 10:01:36 common:913] Instantiating model from pre-trained checkpoint
[NeMo W 2023-11-24 10:01:38 modelPT:161] If you intend to do training or fine-tuning, please call the ModelPT.setup_training_data() method and provide a valid configuration file to setup the train data loader.
    Train config :
    manifest_filepath: null
    emb_dir: null
    sample_rate: 16000
    num_spks: 2
    soft_label_thres: 0.5
    labels: null
    batch_size: 15
    emb_batch_size: 0
    shuffle: true

[NeMo W 2023-11-24 10:01:38 modelPT:168] If you intend to do validation, please call the ModelPT.setup_validation_data() or ModelPT.setup_multiple_validation_data() method and provide a valid configuration file to setup the validation data loader(s).
    Validation config :
    manifest_filepath: null
    emb_dir: null
    sample_rate: 16000
    num_spks: 2
    soft_label_thres: 0.5
    labels: null
    batch_size: 15
    emb_batch_size: 0
    shuffle: false

[NeMo W 2023-11-24 10:01:38 modelPT:174] Please call the ModelPT.setup_test_data() or ModelPT.setup_multiple_test_data() method and provide a valid configuration file to setup the test data loader(s).
    Test config :
    manifest_filepath: null
    emb_dir: null
    sample_rate: 16000
    num_spks: 2
    soft_label_thres: 0.5
    labels: null
    batch_size: 15
    emb_batch_size: 0
    shuffle: false
    seq_eval_mode: false

[NeMo I 2023-11-24 10:01:38 features:289] PADDING: 16
[NeMo I 2023-11-24 10:01:38 features:289] PADDING: 16
[NeMo I 2023-11-24 10:01:39 save_restore_connector:249] Model EncDecDiarLabelModel was successfully restored from /root/.cache/torch/NeMo/NeMo_1.20.0/diar_msdd_telephonic/3c3697a0a46f945574fa407149975a13/diar_msdd_telephonic.nemo.
[NeMo I 2023-11-24 10:01:39 features:289] PADDING: 16
[NeMo I 2023-11-24 10:01:40 clustering_diarizer:127] Loading pretrained vad_multilingual_marblenet model from NGC
[NeMo I 2023-11-24 10:01:40 cloud:58] Found existing object /root/.cache/torch/NeMo/NeMo_1.20.0/vad_multilingual_marblenet/670f425c7f186060b7a7268ba6dfacb2/vad_multilingual_marblenet.nemo.
[NeMo I 2023-11-24 10:01:40 cloud:64] Re-using file from: /root/.cache/torch/NeMo/NeMo_1.20.0/vad_multilingual_marblenet/670f425c7f186060b7a7268ba6dfacb2/vad_multilingual_marblenet.nemo
[NeMo I 2023-11-24 10:01:40 common:913] Instantiating model from pre-trained checkpoint
[NeMo W 2023-11-24 10:01:40 modelPT:161] If you intend to do training or fine-tuning, please call the ModelPT.setup_training_data() method and provide a valid configuration file to setup the train data loader.
    Train config :
    manifest_filepath: /manifests/ami_train_0.63.json,/manifests/freesound_background_train.json,/manifests/freesound_laughter_train.json,/manifests/fisher_2004_background.json,/manifests/fisher_2004_speech_sampled.json,/manifests/google_train_manifest.json,/manifests/icsi_all_0.63.json,/manifests/musan_freesound_train.json,/manifests/musan_music_train.json,/manifests/musan_soundbible_train.json,/manifests/mandarin_train_sample.json,/manifests/german_train_sample.json,/manifests/spanish_train_sample.json,/manifests/french_train_sample.json,/manifests/russian_train_sample.json
    sample_rate: 16000
    labels:
    - background
    - speech
    batch_size: 256
    shuffle: true
    is_tarred: false
    tarred_audio_filepaths: null
    tarred_shard_strategy: scatter
    augmentor:
      shift:
        prob: 0.5
        min_shift_ms: -10.0
        max_shift_ms: 10.0
      white_noise:
        prob: 0.5
        min_level: -90
        max_level: -46
        norm: true
      noise:
        prob: 0.5
        manifest_path: /manifests/noise_0_1_musan_fs.json
        min_snr_db: 0
        max_snr_db: 30
        max_gain_db: 300.0
        norm: true
      gain:
        prob: 0.5
        min_gain_dbfs: -10.0
        max_gain_dbfs: 10.0
        norm: true
    num_workers: 16
    pin_memory: true

[NeMo W 2023-11-24 10:01:40 modelPT:168] If you intend to do validation, please call the ModelPT.setup_validation_data() or ModelPT.setup_multiple_validation_data() method and provide a valid configuration file to setup the validation data loader(s).
    Validation config :
    manifest_filepath: /manifests/ami_dev_0.63.json,/manifests/freesound_background_dev.json,/manifests/freesound_laughter_dev.json,/manifests/ch120_moved_0.63.json,/manifests/fisher_2005_500_speech_sampled.json,/manifests/google_dev_manifest.json,/manifests/musan_music_dev.json,/manifests/mandarin_dev.json,/manifests/german_dev.json,/manifests/spanish_dev.json,/manifests/french_dev.json,/manifests/russian_dev.json
    sample_rate: 16000
    labels:
    - background
    - speech
    batch_size: 256
    shuffle: false
    val_loss_idx: 0
    num_workers: 16
    pin_memory: true

[NeMo W 2023-11-24 10:01:40 modelPT:174] Please call the ModelPT.setup_test_data() or ModelPT.setup_multiple_test_data() method and provide a valid configuration file to setup the test data loader(s).
    Test config :
    manifest_filepath: null
    sample_rate: 16000
    labels:
    - background
    - speech
    batch_size: 128
    shuffle: false
    test_loss_idx: 0

[NeMo I 2023-11-24 10:01:40 features:289] PADDING: 16
[NeMo I 2023-11-24 10:01:40 save_restore_connector:249] Model EncDecClassificationModel was successfully restored from /root/.cache/torch/NeMo/NeMo_1.20.0/vad_multilingual_marblenet/670f425c7f186060b7a7268ba6dfacb2/vad_multilingual_marblenet.nemo.
[NeMo I 2023-11-24 10:01:40 msdd_models:864] Multiscale Weights: [1, 1, 1, 1, 1, 1]
[NeMo I 2023-11-24 10:01:40 msdd_models:865] Clustering Parameters: {
        "oracle_num_speakers": false,
        "max_num_speakers": 8,
        "enhanced_count_thres": 80,
        "max_rp_threshold": 0.25,
        "sparse_search_volume": 30,
        "maj_vote_spk_count": false,
        "chunk_cluster_count": 50,
        "embeddings_per_chunk": 10000
    }
[NeMo W 2023-11-24 10:01:40 clustering_diarizer:411] Deleting previous clustering diarizer outputs.
[NeMo I 2023-11-24 10:01:40 speaker_utils:93] Number of files to diarize: 1
[NeMo I 2023-11-24 10:01:40 clustering_diarizer:309] Split long audio file to avoid CUDA memory issue
splitting manifest: 100%|██████████| 1/1 [00:00<00:00,  1.88it/s][NeMo I 2023-11-24 10:01:41 vad_utils:107] The prepared manifest file exists. Overwriting!
[NeMo I 2023-11-24 10:01:41 classification_models:272] Perform streaming frame-level VAD
[NeMo I 2023-11-24 10:01:41 collections:301] Filtered duration for loading collection is  0.00 hours.
[NeMo I 2023-11-24 10:01:41 collections:302] Dataset loaded with 12 items, total duration of  0.16 hours.
[NeMo I 2023-11-24 10:01:41 collections:304] # 12 files loaded accounting to # 1 labels

vad: 100%|██████████| 12/12 [00:04<00:00,  2.46it/s][NeMo I 2023-11-24 10:01:46 clustering_diarizer:262] Converting frame level prediction to speech/no-speech segment in start and end times format.

creating speech segments: 100%|██████████| 1/1 [00:00<00:00,  2.43it/s][NeMo I 2023-11-24 10:01:46 clustering_diarizer:287] Subsegmentation for embedding extraction: scale0, /content/temp_outputs/speaker_outputs/subsegments_scale0.json
[NeMo I 2023-11-24 10:01:46 clustering_diarizer:343] Extracting embeddings for Diarization
[NeMo I 2023-11-24 10:01:46 collections:301] Filtered duration for loading collection is  0.00 hours.
[NeMo I 2023-11-24 10:01:46 collections:302] Dataset loaded with 381 items, total duration of  0.32 hours.
[NeMo I 2023-11-24 10:01:46 collections:304] # 381 files loaded accounting to # 1 labels

[1/6] extract embeddings: 100%|██████████| 6/6 [00:01<00:00,  3.13it/s][NeMo I 2023-11-24 10:01:48 clustering_diarizer:389] Saved embedding files to /content/temp_outputs/speaker_outputs/embeddings
[NeMo I 2023-11-24 10:01:48 clustering_diarizer:287] Subsegmentation for embedding extraction: scale1, /content/temp_outputs/speaker_outputs/subsegments_scale1.json
[NeMo I 2023-11-24 10:01:48 clustering_diarizer:343] Extracting embeddings for Diarization
[NeMo I 2023-11-24 10:01:48 collections:301] Filtered duration for loading collection is  0.00 hours.
[NeMo I 2023-11-24 10:01:48 collections:302] Dataset loaded with 457 items, total duration of  0.32 hours.
[NeMo I 2023-11-24 10:01:48 collections:304] # 457 files loaded accounting to # 1 labels

[2/6] extract embeddings: 100%|██████████| 8/8 [00:02<00:00,  3.86it/s][NeMo I 2023-11-24 10:01:50 clustering_diarizer:389] Saved embedding files to /content/temp_outputs/speaker_outputs/embeddings
[NeMo I 2023-11-24 10:01:50 clustering_diarizer:287] Subsegmentation for embedding extraction: scale2, /content/temp_outputs/speaker_outputs/subsegments_scale2.json
[NeMo I 2023-11-24 10:01:50 clustering_diarizer:343] Extracting embeddings for Diarization
[NeMo I 2023-11-24 10:01:50 collections:301] Filtered duration for loading collection is  0.00 hours.
[NeMo I 2023-11-24 10:01:50 collections:302] Dataset loaded with 574 items, total duration of  0.32 hours.
[NeMo I 2023-11-24 10:01:50 collections:304] # 574 files loaded accounting to # 1 labels

[3/6] extract embeddings: 100%|██████████| 9/9 [00:02<00:00,  3.30it/s][NeMo I 2023-11-24 10:01:53 clustering_diarizer:389] Saved embedding files to /content/temp_outputs/speaker_outputs/embeddings
[NeMo I 2023-11-24 10:01:53 clustering_diarizer:287] Subsegmentation for embedding extraction: scale3, /content/temp_outputs/speaker_outputs/subsegments_scale3.json
[NeMo I 2023-11-24 10:01:53 clustering_diarizer:343] Extracting embeddings for Diarization
[NeMo I 2023-11-24 10:01:53 collections:301] Filtered duration for loading collection is  0.00 hours.
[NeMo I 2023-11-24 10:01:53 collections:302] Dataset loaded with 764 items, total duration of  0.32 hours.
[NeMo I 2023-11-24 10:01:53 collections:304] # 764 files loaded accounting to # 1 labels

[4/6] extract embeddings: 100%|██████████| 12/12 [00:03<00:00,  3.92it/s][NeMo I 2023-11-24 10:01:56 clustering_diarizer:389] Saved embedding files to /content/temp_outputs/speaker_outputs/embeddings
[NeMo I 2023-11-24 10:01:56 clustering_diarizer:287] Subsegmentation for embedding extraction: scale4, /content/temp_outputs/speaker_outputs/subsegments_scale4.json
[NeMo I 2023-11-24 10:01:56 clustering_diarizer:343] Extracting embeddings for Diarization
[NeMo I 2023-11-24 10:01:56 collections:301] Filtered duration for loading collection is  0.00 hours.
[NeMo I 2023-11-24 10:01:56 collections:302] Dataset loaded with 1148 items, total duration of  0.32 hours.
[NeMo I 2023-11-24 10:01:56 collections:304] # 1148 files loaded accounting to # 1 labels

[5/6] extract embeddings: 100%|██████████| 18/18 [00:03<00:00,  4.69it/s][NeMo I 2023-11-24 10:02:00 clustering_diarizer:389] Saved embedding files to /content/temp_outputs/speaker_outputs/embeddings
[NeMo I 2023-11-24 10:02:00 clustering_diarizer:287] Subsegmentation for embedding extraction: scale5, /content/temp_outputs/speaker_outputs/subsegments_scale5.json
[NeMo I 2023-11-24 10:02:00 clustering_diarizer:343] Extracting embeddings for Diarization
[NeMo I 2023-11-24 10:02:00 collections:301] Filtered duration for loading collection is  0.00 hours.
[NeMo I 2023-11-24 10:02:00 collections:302] Dataset loaded with 2296 items, total duration of  0.32 hours.
[NeMo I 2023-11-24 10:02:00 collections:304] # 2296 files loaded accounting to # 1 labels

[6/6] extract embeddings: 100%|██████████| 36/36 [00:05<00:00,  6.98it/s]
[NeMo I 2023-11-24 10:02:06 clustering_diarizer:389] Saved embedding files to /content/temp_outputs/speaker_outputs/embeddings
clustering: 100%|██████████| 1/1 [00:00<00:00,  1.37it/s][NeMo I 2023-11-24 10:02:06 clustering_diarizer:464] Outputs are saved in /content/temp_outputs directory

[NeMo W 2023-11-24 10:02:06 der:185] Check if each ground truth RTTMs were present in the provided manifest file. Skipping calculation of Diariazation Error Rate
[NeMo I 2023-11-24 10:02:07 msdd_models:960] Loading embedding pickle file of scale:0 at /content/temp_outputs/speaker_outputs/embeddings/subsegments_scale0_embeddings.pkl
[NeMo I 2023-11-24 10:02:07 msdd_models:960] Loading embedding pickle file of scale:1 at /content/temp_outputs/speaker_outputs/embeddings/subsegments_scale1_embeddings.pkl
[NeMo I 2023-11-24 10:02:07 msdd_models:960] Loading embedding pickle file of scale:2 at /content/temp_outputs/speaker_outputs/embeddings/subsegments_scale2_embeddings.pkl
[NeMo I 2023-11-24 10:02:07 msdd_models:960] Loading embedding pickle file of scale:3 at /content/temp_outputs/speaker_outputs/embeddings/subsegments_scale3_embeddings.pkl
[NeMo I 2023-11-24 10:02:07 msdd_models:960] Loading embedding pickle file of scale:4 at /content/temp_outputs/speaker_outputs/embeddings/subsegments_scale4_embeddings.pkl
[NeMo I 2023-11-24 10:02:07 msdd_models:960] Loading embedding pickle file of scale:5 at /content/temp_outputs/speaker_outputs/embeddings/subsegments_scale5_embeddings.pkl
[NeMo I 2023-11-24 10:02:07 msdd_models:938] Loading cluster label file from /content/temp_outputs/speaker_outputs/subsegments_scale5_cluster.label
[NeMo I 2023-11-24 10:02:07 collections:617] Filtered duration for loading collection is 0.000000.
[NeMo I 2023-11-24 10:02:07 collections:620] Total 3 session files loaded accounting to # 3 audio clips
  0%|          | 0/1 [00:00<?, ?it/s]
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
[<ipython-input-13-8cafa8c83657>](https://localhost:8080/#) in <cell line: 3>()
      1 # Initialize NeMo MSDD diarization model
      2 msdd_model = NeuralDiarizer(cfg=create_config(temp_path)).to("cuda")
----> 3 msdd_model.diarize()
      4
      5 del msdd_model

12 frames
[/usr/local/lib/python3.10/dist-packages/nemo/collections/asr/modules/msdd_diarizer.py](https://localhost:8080/#) in conv_forward(self, conv_input, conv_module, bn_module, first_layer)
    417         conv_out = conv_module(conv_input)
    418         conv_out = conv_out.permute(0, 2, 1, 3) if not first_layer else conv_out
--> 419         conv_out = conv_out.reshape(self.batch_size, self.length, self.cnn_output_ch, self.emb_dim)
    420         conv_out = conv_out.unsqueeze(2).flatten(0, 1)
    421         conv_out = bn_module(conv_out.permute(0, 3, 2, 1)).permute(0, 3, 2, 1)

RuntimeError: shape '[138, 50, 16, 192]' is invalid for input of size 84787200

Do you have any hint on how to solve this issue ?

Can you upload the audio you are using so I can reproduce it?

Yes of course. Thank you for your reactivity.
The audio is a french podcast and I'm running the notebook on colab with free T4 GPU.
podcast.mp3.zip

@Ko8rah did you ever find a solution? I am having the same problem.

The problem is caused by using meeting or general config, both are non-supported as for now, stick to telephonic


CUDAVectorApply(f, v) cannot access data in other vectors

Currently you write `CUDAVectorApply(f,v) and we insist that ‘f’ is just code. Nothing else. Ideally, we’d like for ‘f’ to be able to have other data (e.g. vectors) bound in its closure, so that we can access data in other vectors. Accessing data in vectors will involve:

marshalling the vector data into the GPU the same way we marshal “v”
modifying the Vector getitem code so that it actually converts properly to PTX. As it currently stands, we’re converting NativeExpression to PTX, and the NativeExpression objects we generate for Vector::GetItem calls are closely tied to the in-memory representation we have for the LLVM code to talk to.

One solution would be for the Axioms layer to provide alternative implementations depending on the target platform.
Another solution would be to walk the NativeCode objects and replace the relevant Axiom code with something simpler. This is easier to implement now, but less general for the future.

We need to decide what to do with bounds checks. Probably we leave them in, and if they fail, we use the exception-propagation model outlined below.

So, thinking more about this, here are a few smaller pieces that need to happen for this:

We need to do a lowering pass on the NativeCFG to get rid of tuples (called "Composite" in NativeCode objects). Basically, all functions that take a tuple (x,y) should take two arguments, one for x and one for y. We can get rid of arguments with no content (e.g. whose type is 'nothing'). All let bindings whose RHS is a "CreateComposite" call can be expanded in the same way. Load and Store operations on Composites can be expanded into a set of loads and stores for each value in the composite (eliding any empty loads/stores). By doing this, we'll compensate for the fact that PTX doesn't have a tuple notion.

We should explicitly model load and store operations in the NativeCode, and then translate that to PTX. Right now, we assume we have a function 'f', that takes an argument 'x', and then we apply 'f' to every element of "v". We currently only translate 'f', and then directly generate PTX code that loads the elements of 'v' from an array. If we allow NativeCode->PTX translated code to perform arbitrary reads and writes, it will then be easier to access vector data.

We need to allow 'f' to have data associated with it that we can then pass into the CUDA kernel. In this model, instead of creating a native function that accepts 'e', we will generate code with signature (F*, O*, I*, int), where "F" is the lowered type of 'f', O is the output type, I is the input type, and the integer is the offset in the grid we're executing. This will allow us to embed arrays in the data pointed to by 'I' and 'F'.

We need to pick a memory layout for Vector objects when translated to PTX. Initially, we can insist that these are homogenously typed vectors of simple composites (e.g. packed arrays of float, int, etc.) along with a length (so we can implement bounds checking). This can then be the common memory format for vector objects (in a first pass, no vector-of-vector, although this should be pretty easy to implement).

finally, we need to walk "f" and map it into the lowered memory model.

Incidentally, our native code assumes all NativeType objects are densely packed, not paying any attention to alignment. E.g. a tuple (Int64, Int8, Int64) has size 17 bytes, and the third component has alignment 9 - not at all what a C++ compiler would do.  On x86 hardware this is not so bad, but I suspect on the GPU that may have a substantial performance impact.

I take it back - no lowering is necessary because when we generate GPU code, we track composites as a tuple of PTX registers.

So we do need to be more careful on alignment. Non-aligned reads actually create a fault. This means we need to be careful to copy values out of FORA vectors and into CUDA memory with the correct alignment. E.g. if we have tuples (Int64, Int32, Int64), we need to copy them out of FORA into memory with 8 byte alignment for all of them.


[IE11] Dropdown: opening and closing menu leaves an empty white div rendered

Bug Report
Steps

Open  https://stardust-ui.github.io/react/ in IE11
Select 'Dropdown' component
Open and close any of the sample dropdowns

Expected Result
Dropdown closes without leaving any artifacts
Actual Result
After closing a high, empty white div is left rendered, obscuring the rest of the page:

Version
0.25.1
Testcase
Reproducible in https://stardust-ui.github.io/react/components/dropdown

does not repro in 0.35, closing the issue.


MINIFICPP-1499 Add clcache to Windows builds

After checking the available solutions for caching the build objects on Windows with Visual Studio, clcache was chosen. From the available options unfortunately sccache did not work properly with msbuild, and clcache seemed to be a better option than cclash.
Runtimes measured in Github Actions:
Without caching:
vs2017 build: 1h 28m 37s
windows-vs2019: 56m 44s
With caching:
windows-vs2017: 51m 24s
windows-vs2019: 27m 33s

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file?
[ ] If applicable, have you updated the NOTICE file?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

even though clcache is unmaintained, I am not against using it in the CI as the speed-up is substantial, at worst it could introduce inconsistencies between a fresh build a build using clcache (and in worst case false negatives), but as I understand clcache users voiced no such events/concerns

I have tested this in my fork. It works very well on a 2nd CI run in the same branch: https://github.com/fgerlits/nifi-minifi-cpp/actions/runs/729202774 but it does not speed up a compile of the same code in a new branch: https://github.com/fgerlits/nifi-minifi-cpp/actions/runs/729538166. Is there a way to make the cache work across branches?

Currently all cached builds try use 2 restore-keys for retrieving cache: the one for the current branch and the one for the main branch. It works the same way for the Windows builds. If a new branch is built and no cache is available for that yet, it will use the cache from the main branch. As the change is not yet submitted there is no available cache from the main branch that's why it is slow on the first compilation, but it should be available after the PR is merged.

I wanted to clarify my stance on this issue. I maintain that I'm opposed to introducing CI caching at the expense of a dependency on an unmaintained project, but if there is a majority support for it, I'm not vetoing it.
Based on this, I would be a -0.


Dataset problem

Would you like to make public the other two processed data sets mentioned in the paper?
If the data sets collected are in other formats, must be converted to .pickle format before they can be tested.
For example, the format of the data set I collected is .mat format. How should I deal with it?
I hope you can reply to me as soon as possible. Thank you.

I'm afraid I don't have the rights to make public those two proprietary datasets, which are owned by our cooperative companies.
You should convert your data into plain text files, whose format is specified in the Usage section in the documentation.


Modify superfluid/gov to set OsmoEquivilentMultiplier

Current gov proposal does not set OsmoEquivilentMultiplier, thus not being able to handle superfluid delegation upon first epoch after gov proposal has passed.
This PR modifies superfluid/gov to set OsmoEquivilentMultiplier at its initial state
Description

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #922 (9c7f4b7) into main (320cb4a) will increase coverage by 0.15%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main     #922      +/-   ##
==========================================
+ Coverage   20.32%   20.48%   +0.15%
==========================================
  Files         192      192
  Lines       24904    24993      +89
==========================================
+ Hits         5061     5119      +58
- Misses      18917    18929      +12
- Partials      926      945      +19

Impacted Files
Coverage Δ

x/superfluid/keeper/gov/gov.go
91.66% <60.00%> (-8.34%)
:arrow_down:

x/superfluid/keeper/epoch.go
66.66% <100.00%> (ø)

x/lockup/keeper/utils.go
88.88% <0.00%> (-6.67%)
:arrow_down:

x/lockup/keeper/synthetic_lock.go
67.85% <0.00%> (-5.73%)
:arrow_down:

x/lockup/keeper/invariants.go
33.33% <0.00%> (-3.04%)
:arrow_down:

x/lockup/keeper/store.go
87.38% <0.00%> (-0.80%)
:arrow_down:

x/incentives/keeper/distribute.go
60.73% <0.00%> (-0.32%)
:arrow_down:

x/superfluid/keeper/slash.go
100.00% <0.00%> (ø)

x/lockup/keeper/msg_server.go
24.67% <0.00%> (+0.35%)
:arrow_up:

x/superfluid/keeper/stake.go
50.00% <0.00%> (+2.07%)
:arrow_up:

... and 3 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 320cb4a...9c7f4b7. Read the comment docs.

Tested by @czarcas7ic !


GDScript: Fix type for index subscript on constant

const base := [0]

func test():
  var sub := base[0] # sub should be int, not variant now
  if sub is String: pass # analyzer error now

I was in process of moving this small thing from array PR to constants PR but woke up and found deepness already merged.

Thanks!


FHIR Messages Triggering Warning Messages

Bug
Warning Messages
FHIR messages coming from RS trigger warning messages that notify the user that a required value field is missing. The warnings come out of a few missing values from some, not all, Organization resources and the Practitioner resource. The warnings seem to be related to the universal-id-unknown-type and universal-id-type fields.
Impact
FHIR message might not have the proper structure.
To Reproduce

Run RS, ingest initial MN ORU file to create a FHIR message
Run TI and send the FHIR message to the API
Check container logs to see warnings

Expected Behavior
There is still more research to be done in order to find out if the message is missing a required field from the initial HL7 translation, or if the translation to FHIR is adding additional resources without their value field.
Screenshots
Organization is missing the value field for the url of universal-id-unknown-type and universal-id-type

Practitioner is missing the value fields for the url of universal-id-unknown-type and universal-id-type

Logs

Need to confirm that the MN ORU sample file we're using is realistic

This is what the warning looks like: {"@timestamp":"2024-06-14T17:34:20.69877Z","level":"WARN","message":"Resource is missing required element: value","thread_name":"JettyServerThreadPool-18"}

Translate older MN example into FHIR with latest RS.
a. Translated new MN 04 file.
See if MN FHIR sample generates warnings
a. Still receive warnings from RS
If warnings exist, find out why RS is generating FHIR that generates warnings.

I translated the new CA file in RS and checked TI for warnings. There were no warnings with the new up-to-date CA file. See branch story/940/sample-files for sample files.

Need to test with realistic AL and LA messages.

Test with current OML and ORU  test messages

Areas of concern in CA ORU 020 bundle:

Patient identifier has an extension with URL "CX.5", but no value
Patient name has an extension with URL "XPN.7", but no value
The ServiceRequest's obr-observation-request extension has a sub extension with URL "OBR.16", but no value


Adding Support for Property Injection

Hi,
I could not find any guidelines for contributing to your project, so let me know if I am missing anything 😄
Overview
The primary reason for this pull request is to add support for property based injection via Autofac's PropertiesAutowired functionality. To read more on that feature they have documentation here.
I think the best way to stay backwards compatible would be to add an optional parameter. Which is what I did. The new method signatures look like this, please note this would not break existing code:
// One assembly signature:
containerBuilder.RegisterAutoMapper(typeof(Program).Assembly, propertiesAutowired: true);

// Params overload signature:
containerBuilder.RegisterAutoMapper(propertiesAutowired: true, typeof(Program1).Assembly, typeof(Program2).Assembly);

// Configuration overload signature:
containerBuilder.RegisterAutoMapper(cfg => { cfg.AllowNullDestinationValues = true; },
                    typeof(Program).Assembly, propertiesAutowired: true);

// Configuration and params overload signature:
containerBuilder.RegisterAutoMapper(cfg => { cfg.AllowNullDestinationValues = true; },
                    propertiesAutowired: true,  typeof(Program1).Assembly,  typeof(Program2).Assembly);

Files Updated/Added

ContainerBuilderExtensions, here I just added the optional parameter, that is passed down to AutoMapperModule.
AutoMapperModule, after each registration I check if the properties should be autowired and tac that on to the end.
Test Classes:

Name, a two property class for mapping
NameDto, a class with one computed property IsValidFirstName
NameProfile, the mapping setup with the custom value resolver.
IsFirstNameValidResolver, an example where I have my property based dependency called TestConfiguration.
TestConfiguration, a class to simulate a dependency from appsettings config.

ContainerBuilderExtensionsTests, Here is where I added all of my new tests and ensured backward compatibility.

Testing
Three new unit tests were added, basically ensuring that it is, in fact, registering the Custom Value Resolver's property was injected and it's working. These are the new tests:

ContainerBuilderExtension_PropertiesAutoWiredNotSet_ExpectExceptions
ContainerBuilderExtension_PropertiesAutoWiredSet_NoExceptionsExpected
ContainerBuilderExtension_PropertiesAutowired_CustomValueResolverWithPropertyDependencyIsResolved

Hey,
thank you very much for this!

I could not find any guidelines for contributing to your project, so let me know if I am missing anything

There are indeed no guidelines but I would kindly ask you to squash your commits and give it one meaningful message.

I think the best way to stay backwards compatible would be to add an optional parameter. Which is what I did. The new method signatures look like this, please note this would not break existing code:

As far as I can tell those changes are breaking changes, aren't they?
The signature has changed, adding the additional parameter sometimes somewhere in the middle.
Someone who was previously using this:
builder.RegisterAutoMapper(typeof(Program).Assembly)

Would get a compiler error after upgrading, right?
Correct me if I am wrong :)

Sorry for the delay, juggling work and family life.
I squashed the commits and formatted my commit message to match your format. If it's not detailed enough, feel free to let me know and I can amend it.
Thanks!

@alsami bump! Happy New Year! Hoping you're still able to approve this :)

Happy new year to you too. Sorry also for the delay from my side, holidays and so on, totally forgot about it!
Thanks again, will cut a release soon! :)

Package being indexed as off now. Should be available soon! 👍🏽


Support for Virt driver

Rewrite from go-libvirt (go + C) to virsh (shell)

This has to be an external plugin:

https://github.com/lima-vm/lima/discussions/2007

https://github.com/lima-vm/lima/issues/2031

The alternative (to qemu+ssh://) is to ssh to the remote host, and run limactl from there...


[Caching] Give swiftmodule loaded from CAS a path identifier

Assign the path returned from dependency scanner for the module to the buffer identifier when loading modules from CAS. This fixes a warning in module trace file generation about invariant violation and also an assertion when generating swiftdeps file.
rdar://122905379

@swift-ci please smoke test

@swift-ci please smoke test


Error: Cannot find module 'semver'  :    i get this error while installation

Do you want to request a feature or report a bug?
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/stopachka/m6z0xn4r/.
What is the expected behavior?
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?

Hey @jpca999 thank you for reaching out :)
This is an error thrown by npm and it looks like it has nothing to do with draft.js.
You can see this in the stacktrace depicted in the screenshot that you posted (line 5)
Here's a related issue https://github.com/npm/npm/issues/16807
Also btw - please join the draft js community on slack for more immediate help: https://draftjs.herokuapp.com


More detailed doc on how to contribute

Documentation Is:

[X] Missing or needed?
[ ] Confusing
[ ] Not sure?

Please Explain in Detail...
is there any more detailed documentation on how to contribute?
I see this one: https://www.chartjs.org/docs/latest/developers/contributing.html but it's very general.
E.g. I can't figure out what should I do to make the tests pass.

I ran pnpm test
I had lots of warnings
Firefox didn't pass (a single test fails and karma bails out)

I expected first to make everything run correctly, then discuss the changes I'd like to contribute
But now I'm being stuck on the tests. And I'm not sure if I have to make all the tests pass, or is it normal (may be other people also have failing tests, warnings). The general doc doesn't answer this.

Put another way: how to deal with failing tests, warnings on pnpm run ? What will happen if tests pass in my environment but don't in someone else's one?
Your Proposal for Changes
Someone in a position of authority explains the asked questions.
Example
No response

The tests should pass, at least in the CI otheriwse a pr can't be merged. Locally all the test work for me. Which test fails for you?
For the warnings, you should try to write new code so that there are no new warnings. Some files already have them and then you can just work around those.

For the warnings, you should try to write new code so that there are no new warnings

It's rather hard when you have this many warnings to tell if there are new ones. Although as I see most (if not all) of them are related to some 'Filler plugin' being not registered.

Which test fails for you?

Looks like this one, always the same (may be there are others, which won't pass, but currently this is the only one):
[karma]   Chart.elements.PointElement
[karma]     auto
[karma]       ✗ /base/test/fixtures/element.point/rotation.js
[karma]         Fixture test failed:
[karma]           Difference: 1732px / 1.32%
[karma]           Threshold: 10%
[karma]           Tolerance: 0.1%
[karma]
[karma]         specFromFixture/</</_done/<@node_modules/.pnpm/chartjs-test-utils@0.4.0_jasmine@3.99.0_karma-jasmine@4.0.2_karma@6.4.1/node_modules/chartjs-test-utils/dist/chartjs-test-utils.js:1086:25 <- test/index.js:1091:27
I'll try to figure out what's the reason.

Could you answer please which operating system do you use, and what's your screen resolution ?
I use Fedora Linux on a rather small laptop. Like 13', 1920 x 1080

Now I ran tests for both Chrome and FF. A different FF test failed. (Previously I ran only for FF by editing the karma config file).
[karma]   Core.scale
[karma]     auto
[karma]       ✗ /base/test/fixtures/core.scale/tick-backdrop-rotation.js
[karma]         Fixture test failed:
[karma]           Difference: 3398px / 5.18%
[karma]           Threshold: 10%
[karma]           Tolerance: 0.16%
[karma]

First, I'll try to use a wider monitor. I have a 24' one

@LeeLenaleee the tests which fail seem to be random. Also the 24' display hasn't helped, tests still fail in FF.
Could you tell me which OS are you using

@LeeLenaleee and which node version are you using? I have 22.2.0

@LeeLenaleee Hi, I tweaked slightly the test configs and:

in the headless mode it all passes
in normal mode, if I leave the FF window open, this is how the report on failed tests (there are like 58 of them on average) looks:

Could you advise something on what should I do?

I don't know what you want to do but I would just leave the test's alone for now and wait for the CI to see what happens if you plan to make a small change

Thank you, I guess, it's the most convenient and reasonable way to proceed. At least Chrome passes, so I can test just in it for a time being.
@LeeLenaleee let me ask one more question (not even related to this opened issue): where can I discuss with someone in a position of authority the planned changes.
I'd like (as the doc advises) to have opinions/feedbacks beforehand: if it's worth it, should it be a plugin, how the api should look etc.

The best thing you can do is to just open a issue with your proposed changes I think

I'm closing this, b/c for me personally the issue has been resolved


Implement JSON Web Tokens (JWT)

Implement Signup and Login pages

Thinking how we can flesh out the auth flow process a bit while still using a static backend.
Components
Should redirect if logged in

signup
login

navbar

Should show signout and authenticated routes when logged in
Sign out

jwt token logic
Client

signup/login Mutation should return jwtToken
refresh page after mutation/token to make queries but with jwt token in header.
token should be checked if still valid before submitting with query
new token should be saved

Server

Server should check header when processing graphql requests
generate a jwt token with user object in payload
send a refresh token

Authenticated Routes

I mostly agree.

The easiest way to think about authentication is to have the viewer root query return null, if the no user exists, no token exists or the token is expired. Then if viewer is null, use router to redirect.
It should be possible to log a user in without a page reload. Should just be a matter of either FIELD_CHANGE mutation or using new Relay.Environment
We can access the request header by modifying the creation of graphqlHTTP

The best starting point is probably assigning a JWT token on a login mutation, for now, not considering username/password at all.

@Neitsch I've used this post as guidance atm
http://stackoverflow.com/questions/32535141/relayjs-authentication-using-relay-which-mutation-to-use
The viewer object always has the same viewer id, but with the token the viewer object then has a user object. Feels very hackish.

Good point. So, how I see it is, that the viewer query is without arguments, so no ID or anything. It returns the user mapped to that token, which then has the ID of the viewer assigned. The root query does not contain any arguments concerning the user ID, that should all be done on the backend:
If I query viewer { username, id }, it will return { username: 'Neitsch', id: 1234 }, but maybe I'm just at a misunderstanding about JWT. Looking at the guide, the resolve function would be something like this:
var GraphQLRoot = new GraphQLObjectType({
  user: {
  type: new GraphQLNonNull(GraphQLUser),
  description: 'the user',
  resolve: (root, {id}, {rootValue}, context) => co(function*() {
    var user = yield getUser(context.request.cookies.token);
    return user;
  })
}

About null, actually you're right. Null is never good. Instead the IMHO proper way is to have a viewer interface, that either implements a logged in or a logged out user.

Sign in forms on submit
loginUser = (form) => {
        form.preventDefault();
        const {viewer} = this.props.viewer;
        const {username, password} = this.state;
        const loginUserMutation = new LoginUserMutation({
            viewer,
            username,
            password
        });
        const onFailure = (transaction) => {
        };

        const onSuccess = (response) => {
            const jwtToken = response.loginUser.viewer.jwtToken;
            localStorage.setItem('jtx_token', jwtToken);
            this.props.router.push('/dashboard');
            window.location.reload()
        };

        Relay.Store.commitUpdate(loginUserMutation, {onSuccess, onFailure}
        );
    };

@Neitsch Yes thats my understanding as well.
The server reads the JWT Tokens Payload.
It should be a valid token.
The payload has a userID and sense it's signed and not expired we can trust it's validity
This medium post is somewhat interesting.
GraphQL Field Guide to Auth

Ah okay, I read up on it a little bit. My understanding of JWT was wrong.
That Medium post looks good, doesn't use Relay though, so we might have to play with that, if we follow their strategy for authorization. The authentication code lgtm.

This also has a really nice pattern that has the jwt token in the graphql query
GraphQL and Authentication

This was the concept I was thinking about above. I know how to do this with cookies. Not sure if JWT changes anything 😄

I have a lot of the client code here
Name
isAuthenticated and Authenticated Route higher order components in utils.js.
Some logic in regards to checking, setting and handling expired jwt tokens is in jwtUtils file.

That's looking very good to me 💯. It would be great if you could integrate the code into Relay Fullstack

@lvarayut definitely going to try to look into this the next few days.


Don't eat "pathless shebang lines" that could be actual Rust code

Howdy!  The following syntax has surprising results with Python-Markdown, because the markdown processor tries to hide the "shebang line without path":
#!test

The feature causing this problem is https://python-markdown.github.io/extensions/code_hilite/#shebang-no-path, which attempts to create an empty code block.  I think that structurally you should be able to represent anything you like inside a code block, including syntax that could be a pathless shebang line, and thus the correct solution is to either remove the "shebang-no-path" feature, or at least make it optional (probably default-off), which makes the above string not appear properly in code blocks.
See https://johnmacfarlane.net/babelmark2/?text=```
%23!test
```
 for what other implementations do, and https://github.com/zulip/zulip/issues/18591 for an example user experience with this feature (the original reproducer was actual Rust code).

I've personally never been a huge fan of the shebang notation. I'm sure this was added before things like fenced code blocks were a thing (though I'll admit I don't actually know the history here).
The fenced_code extension uses CodeHilite for the code highlighting which pulls in this feature, which I personally think is only useful in indented code blocks (though I don't like it there either). Personally, I use SuperFences for code highlighting. It does not use CodeHilite to do the highlighting so it does not pick up this side effect. Also, SuperFences allows nested fenced code under other constructs like lists which the shipped fenced_code does not handle well.
With all of that said, it may be possible to somehow have the default fenced_code extension still use CodeHilite, but circumvent this behavior. We'd have to see if @waylan disagrees with adding such functionality as I'm not sure if this functionality was intended.

I'm sure this was added before things like fenced code blocks were a thing

Yes it was. Back when the feature was added, it was the only way one could define a language for a code block. We later created fenced code blocks. In fact, I believe that because fenced code blocks became a thing (and became popular), other ways of defining languages for code blocks never became popular.
That said, the existing fenced code block implementation is limited in that it can only be used for code blocks at the document root. In other words, code blocks nested within list items, blockquotes, etc. must still use indented code blocks. The shebang line is the only way those code blocks can have a language defined.
And we have a lot of users with thousands of existing (and possibly many years old) documents which are relying on the existing default behavior of the extension. Therefore, we will not be changing the default.
... with one exception. Checking for shebang lines (and removing pathless shebang lines) is not supposed to happen on fenced code blocks. Apparently some recent change must have unintentionally altered that behavior. So we do have a bug in this respect alone.
Finally, I would like to point out that this is not "default" behavior. The user must explicitly enable the extension to get this behavior. If the user does not like the behavior of the extension, the user is free to use a different extension.

Cool. If I get a chance soon, I may look into this bug.

Thanks for the background!  I agree with the assessment that turning off this feature for fenced code blocks would resolve the issue.

There are two additional changes that could be made to indented code blocks:

We could add a new config option to the extension which optionally disabled handing of shebang lines for indented code blocks. The default behavior should remain the same, but the user would have the option to turn the feature off.
We could skip removal of the shebang line if the entire code block only consists of that one line. It is reasonable to believe that noone will ever intentionally want an empty code block. On the other hand, the likelihood that that would be useful in the real word seems pretty low to me.

Personally, I don't think either is worth the effort. If the first (or only) line of a code block could be mistaken for a pathless shebang line, you should include an actual shebang line before it:
    #!rust
    #!test

In fact, that is probably what you want as it ensures the code block is properly identified as rust for syntax highlighting, In the case where the block consists only of #!test, then the block would be identified as the test language, which is most certainly not what you want, regardless of whether the line is removed or not.

My main plan is simply to ensure fenced code doesn't use the shebang. I'm not seeing anyone calling out for shebang support to be removed from indented, so I'm fine with that. I don't use it as I really only use fenced code blocks, but I know there are people who do, so I don't plan to mess with that.

@timabbott So I've taken a look at this, so I may need some clarification as I cannot reproduce this issue. Consider the following script:
import markdown

text = """

#!test
"""

parser = markdown.Markdown(extensions=['fenced_code'])

print(markdown.__version__)
print(parser.convert(text))

Notice in the output things are parsed as expected:
3.3.4

#!test

I went back and looked at your example on Babelmark 2, and I noticed you are complaining about the handling, but the fenced_code extension is not enabled, so it is treating #!test as a header, not a shebang.
I would recommend turning on fenced_code (only works at root level) or try out SuperFences (which I maintain and works under nested lists etc.).
Fenced code is not part of the original Markdown spec, so it is often implemented via plugins. Some parsers may turn on such functionality by default in modern parsers, but Python Markdown does not.
If you are still having issues, please provide more information.

@facelessuser my understanding is that both fenced_code and codehilite extensions need to be enabled to get the reported behavior.
>>> print(markdown.markdown(text, extensions=['fenced_code', 'codehilite']))

1

Note that the code block only contains one blank line. #!test is missing.
The bug is in the codehilite extension. The extension is supposed to skip shebang line parsing when the codeblock is a fenced code block. I believe is only skips shebang line parsing if a language is predefined. In fact, with this input, the bug does not occur:
```rust
#!test
```

I suppose one could argue that this is not a bug in that the user has failed to specify the language. However, the intention was always to only parse shebang lines for indented code blocks. Regardless, I consider this a low priority as the user can always work around it by specifying a language.

Ah, thanks for the clarification. For some reason I thought Codehilite was implicitly used by fenced code. I ran through this too quickly. I'll take another look.


Migrating DOIs from Scholarsphere 3

DOIs are inconsistently applied in Scholarsphere 3. Their formats range from:

https://doi.org/10.18113/S1KW2H
10.1038/srep21619
doi:10.18113/S1964W
http://dx.doi.org/10.1080/17496535.2017.1318411
https://onlinelibrary.wiley.com/doi/abs/10.1002/ccd.25073
https://doi.org/10.1002/9781444367072.wbiee826
DOI: 10.1080/0194262X.2015.1102676

Is anything with "doi" in it an official DOI? Some also don't have the doi prefix but the minting authority ID, ex. 12.1234. Should migrate those as well?
WDLL

Procedure for determining which identifiers are actual DOIs that we want to migate
Migrate DOI identifiers to the DOI field
Migrate any other identifiers to the identifier field
Apply this to both collections and works

DOIs that we created we will move to the work-level DOI, DOIs created by other places will be migrated to the identifier field (which is where it is now).

We seem to have two main DOI prefixes: 10.18113 and 10.26207. The latter is more recent, and is listed under our DataCite account: https://doi.datacite.org/repositories/psu.scholar/prefixes
The 18113 prefix is NOT listed as one of our prefixes, but they are there. If you search for an DOI minted with that prefix it will show up in our DataCite account page.
Based on this, I'm going to surmise that the DOIs we want to migrate to the DOI field are only the ones that have either of these two prefixes. @srerickson can you verify this for me?

We're migrating prefixes 10.18113 and 10.26207.


Opening a site using commands

"commands": [
{
"displayName": "Test Action",
"path": "testAction"
}
]
If my managed application deploys a App Service - web app, what should the value of path be to open that site?
Is it possible to put the value of the output from mainTemplate.json into the "path" value so that it may open that site?

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

ID: a84f8e07-6352-3424-b87f-388ac1bbaaf9
Version Independent ID: 376e0b20-93f9-c84c-6a25-293a6267b0fd
Content: Overview of view definition - Azure Managed Applications
Content Source: articles/azure-resource-manager/managed-applications/concepts-view-definition.md
Service: managed-applications
GitHub Login: @lazinnat
Microsoft Alias: lazinnat

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

We're also interested in providing a action which opens a link (to our deployed web-app).
We do not want to call an Rest-API via a custom resource provider as all the examples do.
To provide a customized link for the deployed app we would need to get some information from the output.
Is there any option for it?
Thx!
Related:
https://stackoverflow.com/questions/60197764/opening-a-web-app-page-using-view-definition
https://stackoverflow.com/questions/64331250/azure-managed-app-viewdefinition-json-action-with-link-to-app

We reached out to the MS support and go the following response:

We got a confirmation from the product team, unfortunately,  it is not possible to add the dynamic link at the summary page. This is because Custom actions are only designed to perform custom provider actions and not supposed to open hardcoded links etc.

I created a feature request if someone like's to vote:
https://feedback.azure.com/forums/34192--general-feedback/suggestions/42098713-custom-links-at-overview-of-managed-apps

#reassign:davidsmatlak

I verified that path must use a custom provider action and doesn't accept dynamic values. I updated the article and after the pull request is merged, this issue will automatically close. After the merge, the updated document will be online within 24 hours.


Read/Subscribe handler eviction can put reporting engine in a bad state

Problem
When we evict Read/Susbcribe handlers, we call Close() on the handler.
This puts it into the AwaitingDestruction state, which means that in its destructor it does not call OnReportConfirm on the reporting engine.  If it was in the "awaiting report response" state before being evicted, we will fail to decrement mNumReportsInFlight and eventually we will stop being able to send reports at all, because we will think we have CHIP_IM_MAX_REPORTS_IN_FLIGHT in flight while we actually have none.
Proposed Solution
Actually, receiving a non-StatusResponse message looks like it would have the same problem.  So maybe the right fix is actually to either eliminate the AwaitingDestruction state entirely and just have Close call OnDone, or do the OnReportConfirm bits in Close before transitioning to the AwaitingDestruction state?
@erjiaqing @mrjerryjohns @yunhanw-google

We shouldn't actually move the OnReportConfirm logic to Close since it's possible to shut-down the handler by directly destroying it without calling Close (e.g InteractionModelEngine::Shutdown), so having the logic in the destructor I think is still the most right and safest thing.
We should just delete the AwaitingDestruction state since a) it's not used to check or guard any other API access and b) the destruction is fairly immediate and synchronous from the point that Close() is called.

We shouldn't actually move the OnReportConfirm logic to Close

I was not suggesting we move them.  I was suggesting we copy them, so we do it before we go into the AwaitingDestruction state, then in the destructor if we're still IsAwaitingReportResponse() we do it there too.

We should just delete the AwaitingDestruction state

That works for me.

Oh, hmm.  I guess we actually did handle this correctly in that MoveToState has that copy of the OnReportConfirm logic, when leaving the AwaitingReportResponse state!

That's not pretty. We should really fix that...


[Question] Why is the (main) bot token required?

I was wondering.. Why do you require the botToken to be supplied in the config if in the getting started example you execute loginBot() which handles the main bot's token internally?
I really don't believe Corde needs to have access to the main bot's token, only the secondary/test bot's token.

I just tested it, and it seems to work perfectly fine no matter what I set the token to in the config.
I'm really not sure why you would ask for the token and even make it required.

Hi @HeCorr!. It was my mistake. Actually, corde doesn't need botToken . I think that it was needed in an old version, but isn't today. I gonna try to release a version today removing it. Thank you for the appointment and sorry for that!

That makes sense. Thank you!


Fix segment timeline bar chart

A simple PR to fix #12781.
Hi @a2l007 , can you help to review this fix? Thanks
This PR has:

[x] been self-reviewed.
[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[X] been tested in a test Druid cluster.

Nice! this works side by side with https://github.com/apache/druid/pull/12788


jenkins/kola/azure: forward azure private networking parameters to kola

jenkins/kola/azure: forward azure private networking parameters to kola
These allow the configuration of virtual network for the created
instances to join, and tell kola to use the private instance IP for
connectivity.
How to use
Test with jenkins-os PR: https://github.com/kinvolk/jenkins-os/pull/201
Testing done
[Describe the testing you have done before submitting this PR. Please include both the commands you issued as well as the output you got.]

[ ] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)

Backport to all channels.


extend concept of catagory to products?

We should consider using standard product codes https://www.dgs.ca.gov/PD/Resources/Page-Content/Procurement-Division-Resources-List-Folder/United-Nations-Standard-Products-and-Services-Code-UNSPSC to represent products and services in place of categories. A standard product codes database could be augmented with the names of companies that sell products, making it possible to process implicit request such as “I want to buy milk” by starting a search with “milk” in standard product code database and retrieving the companies that sell milk.

Including all the products an enterprise sells may make the VRS database large and difficult to manage.  We could, instead, use the first level (The SS level) which includes a hundred descriptions of the various types of businesses.


Project portfolio

Coverage decreased (-0.01%) to 79.914% when pulling 83679be09567ea15e770ce410eebdf1b301f1d4c on cqhchan:ProjectPortfolio into 274e981dd8d9a624eaedbc5f5bf5664c719a4532 on CS2103AUG2017-T09-B1:master.

Coverage increased (+0.3%) to 80.253% when pulling 4904efc07e661266df01d19a43f20fb03ff64bb8 on cqhchan:ProjectPortfolio into 274e981dd8d9a624eaedbc5f5bf5664c719a4532 on CS2103AUG2017-T09-B1:master.


Add codeql

Add codeql to git workflow for code scanning on PRs

Resolves: #59
Test URLs:
N/A

Codecov Report

Merging #88 (fe4dfe1) into main (aa949d7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #88   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          359       359
=========================================
  Hits           359       359

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[csolution, cbuildgen] Add standard language options into translation controls

The standard language-C and language-CPP options should be accepted and handled according to the specification:
https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/YML-Input-Format.md#translation-control

@ReinhardKeil Can you please update the documentation? The language-C and language-CPP options are accepted in the same places as the other toolchain abstraction controls (namely optimize, debug and warnings).

Documentation got updated. Hence closing.
Reflecting changes in CMSIS-Toolbox 2.0 (https://github.com/Open-CMSIS-Pack/devtools/pull/1030)


Screen grabbing

I'm new to this, so not sure if this is a bug or a feature request.
I'm trying to run the following command capture the desktop screen:
ffmpeg.run('-f', 'avfoundation', '-framerate', '5', '-i', '"1"', '~/Desktop/ffmpeg-test-electron.mkv')
I get an error saying Unknown input format: 'avfoundation'.
The command works fine when run with ffmpeg directly in the command line (without the wasm build).
I understand that for this to work, ffmpeg uses it's library called libavdevice. Is that not part of the wasm build?

wasm can't access to your device screen directly
if you wanna capture the desktop screen, try navigator.mediaDevices.getDisplayMedia and MediaRecorder in JavaScript

Actually the whole reason I came to this library was because I didn’t want to use the browser’s getDisplayMedia method as Chrome doesn’t allow an option to never capture the cursor in the recording.
So you’re saying using the ffmpeg Wasm is a dead end?

ffmpeg.wasm runs on wasm and can be considered virtual, isolated from the operating system, so there is no direct access to the host
use package @ffmpeg-installer/ffmpeg instead, which runs directly on host


Update pipelines.py

Update pipelines.py by adding stratify parameter to train_test_split function of the sklearn library

[x] closes #91  (Replace 91 with the GitHub issue number)
[x] Tests added and passed if fixing a bug or adding a new feature.
[x] All code checks passed.
[ ] Added type annotations to new arguments/methods/functions.
[ ] Updated documentation.

Stratify parameter added added

Some tests are failing 🥶

I will check out the errors to find a solution

I have corrected the stratify variable


ISPN-5204 Don't include old schema files in the documentation and jars/distribution

https://issues.jboss.org/browse/ISPN-5204

Please squash the commits :)

Squshed. I've left the commits separate initially to make it easier to review.

Pushed, thanks


cert-manager upgrade failing due to existing resource conflict

Describe the bug:
When upgrading from v0.16.1 to v1.0.2, installing the new version of cert-manager is erroring due to a conflict with an existing resource:
Install CRDs:
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager.crds.yaml

Helm Install cert-manager:
helm upgrade cert-manager jetstack/cert-manager \
        --install \
        --timeout=300s \
        --wait \
        --version v1.0.2 \
        --namespace cert-manager \
        --set installCRDs=false \
        --set prometheus.servicemonitor.enabled=true \
        --set resources.limits.memory=128Mi \
        --set webhook.resources.limits.memory=128Mi \
        --set cainjector.resources.limits.memory=128Mi

Error: UPGRADE FAILED: rendered manifests contain a new resource that already exists. Unable to continue with update: existing resource conflict: namespace: , name: cert-manager-cainjector, existing_kind: rbac.authorization.k8s.io/v1, Kind=ClusterRole, new_kind: rbac.authorization.k8s.io/v1, Kind=ClusterRole
make: *** [cert-manager/cert-manager.mk:5: install_cert_manager] Error 1
make: *** [Makefile:78: docker_install_cert_manager] Error 2

Expected behaviour:
It is expected that the upgrade of cert-manager will handle this gracefully and successfully deploy.
Steps to reproduce the bug:
install cert-manager CRDs and install cert-manager v0.16.1. Attempt to upgrade from v0.16.1 to v1.0.2 via helm upgrade.
Anything else we need to know?:
Environment details::

Kubernetes version (e.g. v1.10.2): v1.16.13-gke.401
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): GKE
cert-manager version (e.g. v0.4.0): v1.0.2
Install method (e.g. helm or static manifests): helm

/kind bug

I also experienced this on a fresh install of v1.0.2

I noticed that after
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager.yaml

some resources are created that the Helm chart also wants to create. By setting global.rbac.create: false I could workaround the error that has been reported here, but then I run into the next error:
Error: rendered manifests contain a resource that already exists. Unable to continue with install: MutatingWebhookConfiguration "cert-manager-webhook" in namespace

Helm wants to install this resource which has already been installed and there seems to be no option to disable it.
I tried with 1.0.0, 1.0.1 and 1.0.2.

This seems to be some issue in Helm, I am guessing with upgrading versions of resources but I am not too sure. Could you file an issue with Helm for this?

This also was issue with me. On this page the code is listed twice. I believe it is wrong in the first box. Below text of "
Install the CustomResourceDefinitions and cert-manager itself:"
https://cert-manager.io/docs/installation/kubernetes/
If you run the first apply with cert-manager.yaml on the end you get errors. Do an uninstall and do the cert-manager.crds.yaml instead.
kubectl delete https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager.yaml

/kind documentation
/close


Removed gun scripts dependancys on fpscontroller and axis arrow scripts

Set object rotation to desired rotation on grab end just in case the lerp isn't finished at that point.

Again looks awesome :)


Refactor to use localized state management for conversation ID

Description
This PR fixes the usage of a global variable GlobalConversationID in Copilot.tsx. The global variable has been refactored to use localized state management with React's useState hook.
issue #115
Changes include:

Refactored createNewConversation function to accept a state setter for conversation ID.
Updated CopilotChat component to manage the conversation ID using the useState hook.
Adjusted relevant function calls and state management logic to accommodate these changes.

hey
@Arindam200  , @mason-at-pieces , @shivay-at-pieces
please could someone review my PR please , thank you

Hey
@Arindam200 ,
Please review the changes I made based on your request a few hours ago. Thanks!


Improvements to READ.me

Most important change is that the function to get emails is actually called emailStub/getEmails. There was also a lingering reference to stripe.

Merging this would've saved me 5 minutes :)

You can close this. He fixed the README already.

Very well then!


Valheimplus fails to load

This is more of a question than an issue. It's unclear to me whether the valheimplus mod is already in the package or I should download and implement it myself. I've tried using the "-e VALHEIM_PLUS=true" but to no avail. The folder and file neither get created.
using the following docker run command:
docker run -d
--name valheim-server-plus-true
-p 2456-2458:2456-2458/udp
-v /docker/valheim/config:/config
-e SERVER_NAME=****
-e WORLD_NAME=Valhalla
-e SERVER_PASS=****
-e VALHEIM_PLUS=true
-e VPCFG_Server_enabled=true
-e VPCFG_Server_enforceMod=false
-e VPCFG_Server_dataRate=200
lloesche/valheim-server

I just got the same issue trying to add the V+ mod to a server i host.
For now you can use the :dev version of the image, it pulling the mod, just tried it.

Just like the Valheim dedicated server ValheimPlus is automatically downloaded by the container when you VALHEIM_PLUS=true.
There's no need for you to add anything. Also it's been part of the :latest main branch for a while. No need to use the :dev tag.
Just make sure to pull the :latest image tag and don't have an old version of the image on your container host.

Looking at your command above I would also recommend creating /docker/valheim/data on your host and run with -v /docker/valheim/data:/opt/valheim. That way startup is faster as it doesn't have to download the 1 GB Valheim server from Steam each time you start.

Also, on first start make sure that your config/ folder has no directory named valheimplus. If the directory exists the installer assumes you have an existing ValheimPlus config and won't create it and copy the default V+ config.

@gitglennoo did this answer your question? I'll close the issue but feel free to create a new one if there's anything that's unclear or not working.


Remove cssutils warnings from tests

tests/test_get_links_css.py::test_links_css_static
tests/test_get_links_css.py::test_links_css_static
tests/test_get_links_css.py::test_links_css_static
tests/test_get_links_css.py::test_links_css_static
tests/test_get_links_css.py::test_links_css_all_external
tests/test_get_links_css.py::test_links_css_all_external
tests/test_get_links_css.py::test_links_css_all_external
tests/test_get_links_css.py::test_links_css_all_external
  /home/pviktori/dev/freezeyt/__venv__/lib64/python3.9/site-packages/cssutils/errorhandler.py:100: DeprecationWarning: The 'warn' method is deprecated, use 'warning' instead
    self._logcall(msg)

@encukou @adelpopelkova @TomasBalbinder  - Thank you for review 😌
Hello,
I'd like to ask you about your project - https://pypi.org/project/cssutils/
We choose your package cssutils for our project to get css links. Unfortunately we've received information about 'warn' method which is deprecated see the message below:
The 'warn' method is deprecated, use 'warning' instead
    self._logcall(msg)
So we decided that we'd like to make some fixes to your project to eliminate this warning message. Unfortunately we found out that links to your source of code is not available and your link on homepage does not working.
See https://cthedot.de/cssutils/ -> there is a link to source of code https://bitbucket.org/cthedot/cssutils, but this path does not exist.
I'd like to ask you where we could found your source of code and fix it, optionally ?
Thank you for your answer and have a nice day.Best regards.
David

I have a feeling, that I wrote a completely different e-mail. 🙃

Dear <name>
I'm writing to ask you about your project cssutils.
In our project, we choose cssutils to get links from CSS. Unfortunately we are getting deprecation warnings which come from cssutils/errorhandler.py. The full output is:
<the warning message isn't complete it is also linking to pytest docs>

We'd like to get rid of the warnings. Unfortunately we weren't able to find the source code.  We checked the documentation linked from PyPI. There we found a link to the source code but there is nothing there.
I'd like to ask you where can we find the source code and, possibly, fix the problem?
Thank you for your help.
Best regards
David <maybe even your surname unless you have a signature set>

Thank you, I will mix yours and mine. Summarize your english is better.

I've already sent the email to all maintainers of project cssutils (maintainers<EMAIL_ADDRESS>and mail@peterbe.com). I've got error of christopher email account
550 5.1.1<EMAIL_ADDRESS>Recipient address rejected: User unknown in virtual mailbox table

I've found project css-parser
I supposed from its README that css-parser is current fork of cssutil 1.0.2 and fix some its bugs.

Peter's answered:

Sorry David, I have no idea.

I don’t maintain it nor do I know what happened to the Bitbucket repo.
But if you wanted to, perhaps start a fresh new repo on GitHub or GitLab and copy the relevant LICENSE files from the raw sources.
Then, when it comes time to make a release to PyPI I can add you as a maintainer.

Actually, the css-parser you mentioned a few comments up is a fork of cssutils. They started from the last version on PyPI, and there is a commit where they renamed it. I tried to switch from cssutils to css-parser on my computer, and it has the function we use and there are no warnings after the test.


Android AAR binding. LibraryProjectZip is replaced by AndroidLibrary

There's no such option as LibraryProjectZip in BuildActions in Visual Studio 2022 17.7.5
AndroidLibrary is a new build action for simplifying how .jar and .aar files are included in projects. Link

@microsoft-github-policy-service agree


Fix createMutable to handle reactivity in case element is undefined

Summary
Fix for issue #1111
How did you test this change?
I was unable to run the test in local (i'll try again) but i've added a test in the test suite that should be run by the CI i guess.

Thank you. I know why this is failing but it does beg the question if everything goes through that check we probably don't need the signal to have the comparator and we can trim code and execution. That change has farther reaching implications. So this one might be better to merge into the next branch which I should be publishing today or tomorrow as part of pre-release for 1.5.

What I meant is that I was unable to run any test in local, but now I'm seeing that the CI is failing...I'll take a look and maybe go a little deeper if that's something that you are interested into fix.

It is and your fix is mostly right, but there is another change needed that I need to test repercussions on. So if you don't mind I will probably merge this as is, into next branch after I re-evaluate the other required changes.

You are the boss...out of curiosity: why is failing? Also...is there something I need to do to make test work locally? I had "unexpected token" errors.

Did you run npm run build before testing the first time?
The problem is the internal signal has a comparison function which prevents it from triggering anyway. undefined === undefined. But given we already do the equality check there I am thinking we might be able to remove the comparison function.

Did you run npm run build before testing the first time?
The problem is the internal signal has a comparison function which prevents it from triggering anyway. undefined === undefined. But given we already do the equality check there I am thinking we might be able to remove the comparison function.

Yes I did run npm run build but it still gave me the error...also tu build I had to npm install into every single package.


assert that list grows after event fires

I've got what feels like a fairly ordinary test- i need to assert that a table grows by one after an event. The catch is I don't know how big the table is when the test begins.
This is easy enough in pure cypress- I just check the current length, then chain the event, and finally assert that the new length has increased by 1.
Given that i'm now using cucumber, my cypress commands are decoupled, and I'm struggling to find an idiomatic way to represent this.
I've got it working by using a global variable that i'm setting in another step. Feels a bit awkward.
feature
Scenario: Add a new default asset
   When I add a new asset
   Then An asset is added to the table

then in javascript-
import { Given, Then, When, Before } from "cypress-cucumber-preprocessor/steps";

let tableRows = 0;

When("I add a new asset", () => {
        // store initial value
	cy.get("#assets-table")
		.get("tr")
		.its("length")
		.then(length => {
			tableRows = length;
		});
	cy.get("#add-asset-btn").click();
});

Then("An asset is added to the table", () => {
	cy.get("#assets-table")
		.get("tr")
		.its("length")
		.should("equal", tableRows + 1);
});

What would be an idiomatic solution for this problem using this library?

Hi, @danieleades
The preprocessor invokes your function bodies synchronously after each other, hence your approach won't work. You can achieve this using eg. aliases.

you're a gentleman and a scholar


remove KM

Replace the following knowledge-middleware methods:

link-amr
variable-extractions
pdf-extraction


Port remaining GPIOs from teensy4-rs

The PR ports GPIO additions from the teensy4-rs project. In mciantyre/teensy4-rs#47, we added additional GPIOs to support SPI master devices. This PR accounts for part of #9.
I'm targeting the existing hal_gpio branch. If accepted, we can add the safety as discussed in #22 in hal_gpio, then merge everything into master.

Didn't want to push right onto hal_gpio, in case you had other WIP.

Looks good, thanks for doing this


fix premint uid bug

Premint v1 was not storing the created token id for the uid.  this fixed that bug

Current dependencies on/for this PR:

main

PR #376   👈

This stack of pull requests is managed by Graphite.

Merge activity

Nov 20, 9:29 PM: @oveddan started a stack merge that includes this pull request via Graphite.


allow generating module_generator path for any path

https://github.com/ThrowTheSwitch/Ceedling/issues/208
inc_root is already working. But not source_root and any path which are already defined in module_generator.yml

Unfortunately I've got an error when the file exists:
rake aborted!
ERROR: File temp already exists. Exiting.
myproject/vendor/ceedling/vendor/unity/auto/generate_module.rb:197:in `generate'
myproject/vendor/ceedling/plugins/module_generator/lib/module_generator.rb:17:in `create'
vendor/ceedling/plugins/module_generator/module_generator.rake:20:in `block (3 levels) in <top (required)>'
vendor/ceedling/plugins/module_generator/module_generator.rake:13:in `each'
vendor/ceedling/plugins/module_generator/module_generator.rake:13:in `block (2 levels) in <top (required)>'
/var/lib/gems/2.3.0/gems/ceedling-0.28.2/bin/ceedling:287:in `block in <top (required)>'
/var/lib/gems/2.3.0/gems/ceedling-0.28.2/bin/ceedling:274:in `<top (required)>'
/usr/local/bin/ceedling:22:in `load'
/usr/local/bin/ceedling:22:in `<main>'
Tasks: TOP => module:create
(See full trace by running task with --trace)
ERROR: Ceedling Failed
Exception raised in plugin: stdout_pretty_tests_report, in method post_error
myproject/vendor/ceedling/lib/ceedling/plugin_manager.rb:100:in `block in execute_plugins': undefined method `post_error' for #<StdoutPrettyTestsReport:0x0055a7daa44a98> (NoMethodError)
Did you mean?  post_test
        from myproject/vendor/ceedling/lib/ceedling/plugin_manager.rb:98:in `each'
        from myproject/vendor/ceedling/lib/ceedling/plugin_manager.rb:98:in `execute_plugins'
        from myproject/vendor/ceedling/lib/ceedling/plugin_manager.rb:87:in `post_error'
        from vendor/ceedling/lib/../lib/ceedling/rakefile.rb:84:in `block in <top (required)>'

For those still wondering about the proper workaround: follow #208, then change vendor/ceedling/plugins/module_generator/config/module_generator.yml, like this (for instance):
:module_generator:
  :project_root: ./
  :source_root:  Src/
  :inc_root:     Inc/
  :test_root:    test/

I'd be grateful for a better solution.

Does anyone know if this is still an issue?

Do I still have to follow this routine?
myproject $ cd ..
$ ceedling new myproject
$ cd myproject/vendor/
$ rm -rf ceedling/
$ git clone --recursive https://github.com/throwtheswitch/ceedling.git
or update via gem should suffice?
I'm ready to make a clean experiment; suggest your guidelines.

This works but I think it might be better to implement a fix where the module_generator.yml is merged into the project config (\vendor\ceedling\lib\ceedling\configurator.rb line 186)
As it is right now, the plugin configs are merged into the project configs with deep_merge! which overwrites any duplicate values in the project config with the values from the plugin config.
    config_plugins.each do |plugin|
      config.deep_merge!( @yaml_wrapper.load(plugin) )
    end

I don't know Ruby very well and don't know if this would have a negative effect on other plugins but I think changing it to this would fix it using the non-dangerous deep_merge and switching the merge order:
    config_plugins.each do |plugin|
      config = @yaml_wrapper.load(plugin).deep_merge(config)
    end

FYI seems to work as intended if you comment out the lines in the
vendor/ceedling/plugins/module_generator/config/module_generator.yml file
or remove the file entirely.
Then can change the module generator paths in your project.yml file

Note, I had the same issue as this.  I just manually merged in the recommended fix and this fixed the generator, however it breaks the unit tests running.
I get this error:
unit_tests\_fff>ceedling test:encoder
Using fake function framework (fff)...

Test 'test_encoder.c'
---------------------
../../Project/motor_control/PWM.h:7:9: warning: #pragma once in main file
 #pragma once
         ^~~~
Generating runner for test_encoder.c...
Compiling test_encoder_runner.c...
Compiling test_encoder.c...
Compiling encoder.c...
Linking test_encoder.out...
Running test_encoder.out...
rake aborted!
NoMethodError: undefined method `plugins_display_raw_test_results' for #<Configurator:0x0000000003b7eb90>
C:/development/cframe/unit_tests/vendor/ceedling/lib/ceedling/plugin_manager.rb:75:in `post_test_fixture_execute'
C:/development/cframe/unit_tests/vendor/ceedling/lib/ceedling/generator.rb:172:in `generate_test_results'
C:/development/cframe/unit_tests/vendor/ceedling/lib/ceedling/rules_tests.rake:47:in `block in <top (required)>'
C:/development/cframe/unit_tests/vendor/ceedling/lib/ceedling/task_invoker.rb:74:in `invoke_test_results'
C:/development/cframe/unit_tests/vendor/ceedling/lib/ceedling/test_invoker.rb:104:in `block in setup_and_invoke'
C:/development/cframe/unit_tests/vendor/ceedling/lib/ceedling/test_invoker.rb:63:in `each'
C:/development/cframe/unit_tests/vendor/ceedling/lib/ceedling/test_invoker.rb:63:in `setup_and_invoke'
C:/development/cframe/unit_tests/vendor/ceedling/lib/ceedling/rules_tests.rake:62:in `block (2 levels) in <top (required)>'
C:/Ruby25-x64/bin/ceedling:23:in `load'
C:/Ruby25-x64/bin/ceedling:23:in `<main>'
Tasks: TOP => build/test/results/test_encoder.pass
(See full trace by running task with --trace)

Cheers.


Inverse increment conditions when needed.

fixes a bug in telamon-gen

bors r+

r-

bors r-

bors r+

bors r+


DCOS-21270: Create service puts cursor at wrong position in app id box

Put cursor at the end of inputbox when creating a service.
Closes https://jira.mesosphere.com/browse/DCOS-21270
Solution taken from https://coderwall.com/p/0iz_zq/how-to-put-focus-at-the-end-of-an-input-with-react-js .
Testing

Go to services
Create a single-container service
Verify that the cursor is at the end of the input after "/".
Repeat for pod.

Trade-offs
None.
Dependencies
None.
Screenshots

I bet it needs some lion 😅

@GeorgiSTodorov l10n, langpacks

@nLight , @DanielMSchmidt , @mperrotti , updated.

@GeorgiSTodorov all the plugins are gone. Please refer to the wiki page https://wiki.mesosphere.com/display/ENGINEERING/Extract+and+update+translation+messages

@nLight , thank you for noticing.

Thanks @GeorgiSTodorov! I should have pulled it down and tried it before saying something.

Updated message catalog format, please take another look when you have time.


Feature/google authentication

Add Google authentication to base template.
(Not really done yet mostly testing the new Codecov CI)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

closing the PR to check codecov will reopen again.


Fix some unhandled report issues

Changes proposed ✍

Fix the following errors thrown in log rocket:

TypeError: Cannot read properties of undefined (reading 'name')
TypeError Cannot read properties of undefined (reading 'some')

Fixes:

Add loading states to reports page and if report id does not exist prevent from rendering the page

Checklist ✅

[x] Label appropriately with Feature, Enhancement, or Bug.
[ ] Tests are passing.
[ ] New backend functionality has been unit-tested.
[ ] Environment variables have been updated:

[ ] Local frontend configuration: frontend/.env.dist.local, frontend/.env.dist.composed.
[ ] Local backend: backend/.env.dist.local, backend/.env.dist.composed.
[ ] Configuration docs have been updated.
[ ] Team members only: update environment variables in override, staging and production env. files and trigger update config script.

[ ] API documentation has been updated (if necessary) (see docs on API documentation).
[x] Quality standards are met.
[x] All changes have been tested in a staging site.
[x] All changes are working locally running crowd.dev's Docker local environment.

Changes look good to me, but I'm wondering why didn't/doesn't the app redirect the user to the /404 page after validating that the report does not exist (so after getting the 404 from the API) 🤔 Did you understand what was happening?

Thanks for raising that point!
I've actually update the PR overall description because some the errors there weren't fixed by this PR (sorry about that)
Nonetheless, from what I've checked and saw the current behaviour is if you try to access a report that doesn't exist you get redirected to the reports list page (I think this is also ok instead of redirecting to a 404, what do you say?). However, the problem is that in the reports view page components we were only protecting for the loading and not error state. So what I think was happening was that after the loading state and before the error state, a lot of properties were being used on a report object that did not exist. By preventing the page content from being rendered and accessed in an error scenario, we are preventing these undefined errors

I see, thanks for clarifying!

the current behaviour is if you try to access a report that doesn't exist you get redirected to the reports list page (I think this is also ok instead of redirecting to a 404, what do you say?)

You're right, I was not aware that this was how we're handling it at the moment. Not a big problem for me — ultimately I guess this might add less frustration to the user (since he won't be seeing the 404 page), but I'm not sure if this is "standard behaviour", maybe we should check it later on with Nuno.


winget install: If a single download fails or a paket was renamed, all following installs are skipped, even with --force

Brief description of your issue
If a packet in the list you provide to winget install fails to download or does not exist (anymore), all further installs are aborted, even if we add --force to it. likely this also happens when an install fails (did not test)
It seems that the similar issue for winget update ahs been fixed in 1.3, but not for install
https://github.com/microsoft/winget-cli/issues/2266
Steps to reproduce
Currently, the manifest of MPC-HC is broken (and has been for days) and this causes mpc-hc being not installed, obviously.
pick a tool you do not have installed TOOLNAME
use
winget install mpc-hc TOOLNAME
winget instal sdfkjsldf TOOLNAME
Expected behavior
Installation of TOOLNAME succeds and issues with mpc-hc/sdfkjsldf are reported by winget in the summary
Actual behavior
both will fail
Environment
Windows: Windows.Desktop v10.0.19044.4529
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.23.1791.0

@denelon - I don't believe this is a bug based on

https://github.com/microsoft/winget-cli/issues/2998

@Trenly @denelon 2998 is about not found only, this is about not found or found but disfunctional


Navigating "next" and "prev" links?

A feature I sorely miss in Vimium and others:
]]      Follow the link labeled 'next' or '>'. Helpful for browsing paginated sites.
[[      Follow the link labeled 'previous' or '<'. Helpful for browsing paginated sites.

Any chance of some equivalent in Vimari?

+1

This would be such a cool feature!

I would LOVE this feature!

Please, Implement this!

I too would love this feature!

I too would love this feature!


Express meta as JS

This idea courtesy of @JReinhold. It might be more natural to express meta as JS within the .svelte file leaving Svelte syntax for the stories themselves.
<script context="module">
  import Button from './Button.svelte';

  // exactly like default export in plain CSF
  export const meta = {
    title: "Special Buttons",
    component: Button,
    argTypes: {...},
    parameters: {...}
  };
</script>

The issue here is that "meta" should be statically analyzed to be part of the stories index. It's doable but not easy to do if it's plain JavaScript.

If it's in JavaScript couldn't you just use it directly rather than trying to statically analyze it?

It's not possible afaik. At least the first version of this plugin had been rejected because of that ^^
You have to extract a "stories.json" at compile time.
Storybook uses an AST from Babel to do that - cf https://github.com/storybookjs/storybook/tree/next/code/lib/csf-tools
Here, we should reimplement this logic with the AST from Svelte, or maybe reuse csf-tools, but IMO it's not part of the public api of storybook.
At least 3 properties should be exported at compile time: an id, a title, and the list of tags -  https://github.com/storybookjs/addon-svelte-csf/pull/134/files#diff-268ed31ede4f019aa45638117dd2ee766a1f44800c8f9d9a8b7557cce061a9c0L144
Others properties/parameters could be read at runtime.

I have an implementation of this issue in #134

It's not possible afaik.

I have an implementation of this issue in https://github.com/storybookjs/addon-svelte-csf/pull/134

I'm not quite sure how to interpret these two seemingly conflicting statements :laughing: It sounds like you originally thought it wasn't possible, but then figured it out, so I wanted to clarify if that's right?

Sorry, I was talking about this:

If it's in JavaScript couldn't you just use it directly rather than trying to statically analyze it?

It's not possible because it has to be parsed at compile time. It's implemented here in the PR: https://github.com/storybookjs/addon-svelte-csf/pull/134/files#diff-268ed31ede4f019aa45638117dd2ee766a1f44800c8f9d9a8b7557cce061a9c0R168


fix: update OpenSpace Soft color

ok!

:tada: This PR is included in version 1.2.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Website update

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes

0 out of 2 committers have signed the CLA.

[ ] denis-opsguru
[ ] adv4000

Have you signed the CLA already but the status is still pending? Recheck it.


ci: test cross platform

Test on Node.js 10 and 12, long term release support versions.
Test on Linux, Mac, and Windows machines.

I'm not sure why this is failing. Can anyone tell?

@tannerlinsley Looks like is-ci-cli may have an issue with Windows?

As far as I can tell, is-ci-cli has an issue where it is unable to detect travis ci for windows as a CI environment.
I've logged this upstream as https://github.com/watson/is-ci/issues/19
I could revert the windows part and keep the MacOS and Linux part for now to unblock this, if folks prefer.

👍
Tanner Linsley
On Oct 4, 2019, 11:00 AM -0600, Christian Murphy<EMAIL_ADDRESS>wrote:

As far as I can tell, is-ci-cli has an issue where it is unable to detect travis ci for windows as a CI environment.
I've logged this upstream as watson/is-ci#19
I could revert the windows part and keep the MacOS and Linux part for now to unblock this, if folks prefer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't see how it wouldn't be detecting the TravisCI as a CI environment. is-ci-cli uses is-ci which uses ci-info of which everything seems correct. Including your PR passing on Windows for is-ci. If is-ci-cli was failing to detect the CI environment, it should fallback to running test:dev script.
I put out a PR on is-ci-cli to use cross-spawn and throw any errors that try to silently fail. Hopefully this will catch it.

@ChristianMurphy Can you try v2.0.0 of is-ci-cli?

Thanks @stramel, updated to is-ci-cli version 2

Closing this in favor of #1578
The issue doesn't appear on GitHub actions CI workflow or in local testing.
I suspect the issue may with with Travis CI Windows beta issue.

@ChristianMurphy You can fix the issue by adding this to the .travis.yml
env:
  global:
    - YARN_GPG=no

@ChristianMurphy I wrote out a travis file for the is-ci-cli lib. https://github.com/YellowKirby/is-ci-cli/pull/6/files
https://travis-ci.org/stramel/is-ci-cli/builds/595780320

@ChristianMurphy You might want to try removing the quotes around the script. I think that is causing windows to fail.

I agree. I'm not even sure how the package-lock.json got in there TBH


add a project - movie-details-generator

I want to add a minor project that is used to search for various movies/ shows and displays its details ( imdb rating, plot, actors, directors, release date etc). details are fetched using a simple api
Example UI -

Hi @Astrodevil , please assign this to me