Table Component?

Is there work for a table component for the CSS and js?

Hi,
there is no plan to do this yet.
Can you explain what benefit a table component would bring to your project?

Well, since the semantic ui main install has a dependency on jQuery for its functionality - I turned to ng2-semantic-ui but it seems to have many components... besides table, are there plans to add it?

Hey,
like I said we do not plan to bring up a table component yet.
Nevertheless I am very interested in the benefit you expect from such a component.
What is the reason why simpy applying the CSS styles of SemanticUI do not satisfy you?

I am planning on using Semantic-UI in an Angular 4 application and updating the Angular 4 application to the latest version later on. Currently, I have the application set up using Webpack - I wanted to see if Semantic-UI could work in an Angular 4 project.

Hi there, so essentially, this project is a rewrite of the Semantic UI components that leverage jQuery in pure Angular. In order to keep the scope manageable, it relies on plain CSS as much as possible, hence why a lot of components, despite using Angular, still rely on the user adding classes for visual functionality (see Accordion). Therefore, we don't plan to add any components that don't require javascript - using just the Table CSS classes alone will cover all of the functionality Semantic UI already provides. I hope that all makes sense!

It would be useful to have the sortable table variant from SUI though which relies on jQuery.

Me aswell. I want to sort the data in tables.


Problems with --show-ref (gvcf mode)

Hello...
I'm attempting to run v0.2.0 of Clair3-rna and have some observations:
docker run -v `pwd`:/data -it hkubal/clair3-rna:v0.2.0   /opt/bin/run_clair3_rna --bam_fn /data/test.bam --ref_fn /data/reference.fasta --sample_name test --platform=ont_dorado_drna004 --output_dir /data/test --output_prefix=test --include_all_ctgs --print_ref_calls -t 10 --min_coverage 0

Leads to the following error:
usage: call_var_bam.py [-h] [--platform PLATFORM] --bam_fn BAM_FN --chkpnt_fn
                       CHKPNT_FN --ref_fn REF_FN [--call_fn CALL_FN]
                       [--vcf_fn VCF_FN] [--ctgName CTGNAME]
                       [--ctgStart CTGSTART] [--ctgEnd CTGEND]
                       [--bed_fn [BED_FN]] [--sampleName [SAMPLENAME]]
                       [--min_af MIN_AF] [--snp_min_af SNP_MIN_AF]
                       [--indel_min_af INDEL_MIN_AF] [--gvcf GVCF]
                       [--qual QUAL] [--samtools SAMTOOLS] [--pypy PYPY]
                       [--python PYTHON] [--fast_mode FAST_MODE]
                       [--enable_phasing_model ENABLE_PHASING_MODEL]
                       [--minCoverage MINCOVERAGE] [--minMQ MINMQ]
                       [--minBQ MINBQ] [--bp_resolution] [--haploid_precise]
                       [--haploid_sensitive] [--call_snp_only CALL_SNP_ONLY]
                       [--enable_long_indel ENABLE_LONG_INDEL]
                       [--keep_iupac_bases KEEP_IUPAC_BASES]
                       [--phasing_info_in_bam] [--base_err BASE_ERR]
                       [--gq_bin_size GQ_BIN_SIZE]
                       [--temp_file_dir TEMP_FILE_DIR] [--use_gpu USE_GPU]
                       [--tensorflow_threads TENSORFLOW_THREADS]
                       [--extend_bed [EXTEND_BED]]
call_var_bam.py: error: unrecognized arguments: --show_ref

We can prevent this error by editing /opt/bin/run_clair3_rna to envoke the --gvcf option.
But, when we get the gvcf not all reference positions are present. You get only a handful of RefCall sites.
It seems if you set --snp_min_af to 0 this outputs most of the sites in the reference as expected, however those at the very start of the reference are omitted. Is this expected behaviour? Adding --indel_min_af 0 does not help any further.
#CHROM  POS     ID      REF     ALT     QUAL    FILTER  INFO    FORMAT  test
REF       17      .       T       .       19.07   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:19:558:545:0.9767:990
REF        18      .       T       .       19.19   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:19:563:549:0.9751:990
REF        19      .       T       .       15.37   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:15:573:567:0.9895:990
REF        20      .       A       .       16.23   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:16:574:565:0.9843:990

They are well covered:
samtools depth test.bam | more
REF        1       364
REF       2       415
REF        3       425
REF        4       434
REF        5       436
REF        6       448
REF        7       449
REF        8       399
REF       9       391
REF        10      500
REF       11      478
REF        12      532
REF        13      520
REF        14      544
REF        15      554
REF        16      556

I do notice the following message:
[faidx] Truncated sequence: REF:1-2312

If I index my reference there is no problem:
samtools faidx reference.fasta
cat reference.fasta.fai
REF       1312    10      1312    1313

This may or may not be related to omission of positions at the start of the reference in the VCF?

We further observed that the sites output to the vcf file varied with depth. Using a ~1kb transcript at very high depth (>1000x) we find that we get a line in the vcf for all except the first/last 16 bases (as noted above), but at 50x depth a number of sites are missing from the output.
1000x depth output
...
sample  90      .       C       .       20.49   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:20:991:964:0.9728:990
sample  91      .       A       .       18.54   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:18:992:962:0.9698:990
sample  92      .       A       .       10.16   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:10:993:981:0.9879:990
sample  93      .       G       .       11.40   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:11:993:986:0.9930:990
sample  94      .       G       .       13.96   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:13:993:988:0.9950:990
sample  95      .       G       .       16.93   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:16:993:988:0.9950:990
sample  96      .       C       .       18.39   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:18:993:974:0.9809:990
sample  97      .       G       .       15.67   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:15:993:978:0.9849:990
sample  98      .       A       .       20.74   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:20:993:973:0.9799:990
sample  99      .       G       .       19.93   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:19:996:983:0.9869:990
sample  100     .       G       .       16.31   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:16:996:987:0.9910:990
...

50x depth output
...
sample  89      .       G       .       17.67   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:17:50:49:0.9800:990
sample  91      .       A       .       19.12   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:19:50:48:0.9600:990
sample  96      .       C       .       21.01   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:21:50:49:0.9800:990
sample  99      .       G       .       20.49   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:20:50:47:0.9400:990
sample  100     .       G       .       21.81   RefCall .       GT:GQ:DP:AD:AF:PL       0/0:21:50:49:0.9800:990
...

There doesn't seem an obvious pattern to those included/excluded at lower depths. For example position 93, 98 have the lowest/highest QUAL at high depth and are both missing from the low depth data, similarly 91, 100 are included and represent the lowest/highest allelic depth.
These output were run with the following settings, with --print_ref_calls switch for --gvcf in the run_clair3_rna script
./run_clair3_rna --bam_fn input_data.bam --ref_fn reference.fasta --threads 16 --platform ont_dorado_drna004 --output_dir output --snp_min_af 0.0 --min_coverage 1 --sample_name sample1 --output_prefix sample --include_all_ctgs --print_ref_calls --indel_min_af 0.0

The GVCF output module in Clair3-RNA was for Clair3 and has not yet been tuned for Clair3-RNA. For me to plan better, may I ask how often would GVCF output be used for RNA-Seq based variant calling?

@mattdmem  We have released an update v0.2.1 to fix the bug that misses a few variants with the --print_ref_calls option.
Missing variants in the head and tail 16 bp of each sequence was another issue and was caused by the design of the Clair3 networks. Alignments were usually less reliable in these regions, and insufficient context will be fed to the Clair3 networks for candidates in these regions, causing increased FP. In the new version, we added a new option --enable_variant_calling_at_sequence_head_and_tail to get the variants in these regions called. We required reads with MQ≥5, and not secondary and supplementary alignments in these regions.
Please re-pull the docker image and give the new version a try. Let us know for any questions.

@davidnewman02
Clair3-RNA skips considering those positions with only reference allele support as candidates, even when --snp_min_af and --indel_min_af are set to 0. This explains why some RefCall positions with a higher coverage are shown, but those with a lower coverage are not shown (because there is no alternative allele at the positions). This is the current behavior of Clair3-RNA that we have chosen to speed up Clair3-RNA by reducing the number of candidates. Let us know if those positions with no alternative alleles should also be considered as candidates so as to show them as RefCall when --print_ref_call is enabled, and we can modify the behavior.

Thanks - I think we would expect, like you do with a gVCF to have all positions regardless of the presence of an alternative allele.

@mattdmem
Thanks. We have modified the logic to output all positions with at least one read support when --snp_min_af or --indel_min_af is set to 0.0. Please kindly try the updated docker image.

Hi @zhengzhenxian,
Thanks for implementing these changes. I can confirm that the --print_ref_calls options now works as expected, however, I couldn't get the --enable_variant_calling_at_sequence_head_and_tail option to work.
(built-locally from commit: a101dc6b)
[INFO] Pileup Model Prediction                                                                                [INFO] RUN THE FOLLOWING COMMAND:

( parallel -C " " --joblog /data/clair3_rna_eval/tmp_out/logs/parallel_1_predict.log -j 16 python3 /data/clair3_rna_eval/Clair3-RNA/clair3_rna.py call_var_bam --chkpnt_fn ~/miniconda3/envs/clair3_rna/bin/clair3_rna_models/ont_dorado_drna004/variables --bam_fn /data/clair3_rna_eval/input_data/subsample.8000.bam --call_fn /data/clair3_rna_eval/tmp_out/tmp/pileup_output/pileup_{1}_{2}.vcf --sampleName sample1 --ref_fn /data/clair3_rna_eval/fake_refs/refs/ref_10_G.fasta --extend_bed /data/clair3_rna_eval/tmp_out/tmp/split_beds/{1} --ctgName {1} --chunk_id {2} --chunk_num {3} --platform ont --snp_min_af 0.0 --indel_min_af 0.0 --minMQ 5 --minCoverage 20 --samtools samtools --pileup  --cmd_fn /data/clair3_rna_eval/tmp_out/tmp/CMD --enable_variant_calling_at_sequence_head_and_tail True  :::: /data/clair3_rna_eval/tmp_out/tmp/CHUNK_LIST ) 2>&1 | tee /data/clair3_rna_eval/tmp_out/logs/1_call_var_bam_pileup.log

[INFO] Delay 1 seconds before starting variant calling ...
[faidx] Truncated sequence: sample:1-2022
[mpileup] 1 samples in 1 input files
Calling variants ...
Exception in thread Thread-1:
Traceback (most recent call last):
  File "~/miniconda3/envs/clair3_rna/lib/python3.9/threading.py", line 950, in _bootstrap_inner
    self.run()
  File "~/miniconda3/envs/clair3_rna/lib/python3.9/threading.py", line 888, in run
    self._target(*self._args, **self._kwargs)
  File "/data/clair3_rna_eval/Clair3-RNA/clair3_rna/call_variants.py", line 1491, in load_mini_batch
    mini_batches_loaded.append(next(tensor_generator))
  File "/data/clair3_rna_eval/Clair3-RNA/clair3_rna/utils.py", line 113, in tensor_generator_from
    if seq[param.flankingBaseNum] not in BASE2NUM:
IndexError: string index out of range
Total processed positions in sample (chunk 1/1) : 0
Total time elapsed: 0.17 s
[INFO] No vcf output for file /data/clair3_rna_eval/tmp_out/tmp/pileup_output/pileup_sample_1.vcf, remove empty file
Traceback (most recent call last):
  File "/data/clair3_rna_eval/Clair3-RNA/clair3_rna/../clair3_rna.py", line 108, in <module>
    main()
  File "/data/clair3_rna_eval/Clair3-RNA/clair3_rna/../clair3_rna.py", line 102, in main
    submodule.main()
  File "/data/clair3_rna_eval/Clair3-RNA/src/create_tensor_pileup.py", line 684, in main
    CreateTensorPileup(args)
  File "/data/clair3_rna_eval/Clair3-RNA/src/create_tensor_pileup.py", line 539, in CreateTensorPileup
    tensor_can_fp.stdin.write(l)
BrokenPipeError: [Errno 32] Broken pipe

I tried a few different configurations including with/without --print_ref_calls and introducing a fake-variant in the edge region, but couldn't get this to work.

@davidnewman02
We attempted to repeat your error using different data and configurations but still failed on our slide. Not sure if the issue is related to the reference. Could you please send your reference and BAM files to my email at<EMAIL_ADDRESS>for our testing? Many thanks for your help.
Zhenxian

@mattdmem just in case the reference and bam cannot be shared, would you mind tweaking the code a bit and print out param.flankingBaseNum to see how it goes out of the range?

Although I cannot share the original data I've been able to reproduce this error by generating a random pileup of data and running Clair3-RNA on that.
Clair3-RNA_issue-6.zip

@davidnewman02  Great thanks for sharing the demo data. We have fixed the reference range issue, please try the latest code, thanks.
Zhenxian


Error: subtle is not defined in the enviroment, please provide a valid ponyfill object with the parameter 'ponyfill.subtle'.

Describe the bug
When I run the exmple from here:
https://github.com/Secreto31126/whatsapp-api-js#:~:text=Now you can write code like this%3A
I fill in the TOKEN and APP_SECRET and I get the error:
Error: subtle is not defined in the enviroment, please provide a valid ponyfill object with the parameter 'ponyfill.subt
le'.
To Reproduce
Steps to reproduce the behavior:

Open new project
Import the project
Copy the exmple
Fill in the TOKEN and SECRET
Run it
Get the error

Expected behavior
The app should run locally.
Desktop (please complete the following information):

OS: Windows 10
Runtime Node.js v18.16.0
Library Version 2.1.1

You might want to use the setup helpers defined in "whatsapp-api-js/setup"
https://whatsappapijs.web.app/functions/setup.Node18.html
https://github.com/Secreto31126/whatsapp-api-js/blob/main/EXAMPLES/main.md#using-the-setup-helpers
https://github.com/Secreto31126/whatsapp-api-js/blob/main/ENVIRONMENTS.md
I will update the error message to make it clear there's a method to fix this issue.


show pie charts legend according to "hideLegend" field

fixes https://github.com/demisto/etc/issues/37630
Report builder:

report:

@yanyo87
Regarding the failed test... it is also failed on master locally


Unsatisfied linear constraint with no free enforcement literal: enforcement_literal [occurs sometimes]

What version of OR-Tools and what language are you using?
CP-SAT solver v9.9.3963 Release version
Language: Minizinc
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
CP-SAT
What operating system (Linux, Windows, ...) and version?
Windows
What did you do?
The original minizinc mzn/dzn combination was compiled to fzn and executed against fzn-cp-sat.exe.  I typically run the model in parallel with 24 CPUs.
What did you expect to see
Most of the time the solver completes successfully [see attached result_successful_solve.txt].
What did you see instead?
About once every five runs, the executable terminates with an error:
F0410 10:29:09.107739   44632 cp_model_postsolve.cc:105] Unsatisfied linear constraint with no free enforcement literal: enforcement_literal: 2323 linear { vars: 2305 coeffs: 1 domain: 0 domain: 0 }
Make sure you include information that can help us debug (full error message, model Proto).
I've included the fzn file.
Anything else we should know about your project / environment
I'm currently running fzn-cp-sat in a Windows 10 environment.
ortools_error.zip

I can reproduce.
It would be super nice if you could reduce the size of the model.

Dear Laurent,
I've attempted to reduce the model's size, but it seems that the likelihood of the error now occurring is lower.  However, I could repeat the issue with the attached model as well:
fzn-cp-sat.exe error_2024_04_10_reduced.fzn --time_limit=120 --threads=24 --cp_model_stats=true --display_all_solutions=true --statistics=true --cp_trace_search=true  --v=99999  1>result_002.txt
F0411 09:35:05.807726   14216 cp_model_postsolve.cc:106] Unsatisfied linear constraint with no free enforcement literal: enforcement_literal: -1191 linear { vars: 1184 coeffs: 1 domain: 0 domain: 0 }
*** Check failure stack trace: ***
@   00007FF66DC8BFE9  (unknown)
@   00007FF66D9B58ED  (unknown)
@   00007FF66D9B4620  (unknown)
@   00007FF66D9B5392  (unknown)
@   00007FF66D93392B  (unknown)
@   00007FF66D7A26A2  (unknown)
@   00007FF66DB3AB24  (unknown)
@   00007FF66DB3A55F  (unknown)
@   00007FFEEC381BB2  (unknown)
@   00007FFEECF87614  (unknown)
@   00007FFEEEA026B1  (unknown)
I've included two additional txt files: result_001.txt shows where it succeeded, and result_002.txt where it failed.
I have not been able to reduce the size of the model further as yet.
Sincere regards.
ortools_error_2.zip

Thanks.


mongoid and cancancan: uninitialized constant ActiveRecord::Base (NameError)

Hi,
I'm using mongoid (4.0.2).  rails g devise_google_authenticator:install is throwing below error,
/Users/uname/.rvm/gems/ruby-2.1.2/gems/cancancan-1.9.2/lib/cancan/model_adapters/active_record_adapter.rb:146:in `<top (required)>': uninitialized constant ActiveRecord::Base (NameError)
Any idea why install command throwing error ?
Thanks

I was facing the same issue when using CanCanCan and Mongoid. I solve it including the Mongoid::Document module on my Ability.rb
Ps: after 4 years, I think you already solve your problem haha. But it may help someone else :D_
class Ability
  include Mongoid::Document
  include CanCan::Ability

  def initialize(store)
    # my code
  end
end


WIP - Starter kit

Hygieia Start kit is designed to be a quick setup live demo instance of Hygieia.
Current State:

Image for setting up UI, API, and DB.
Currently image pulls from snapshots but this will be updated to pull from releases

@chtompki Can you provide some feedback as well?


Adding CICD trigger to allow non versioned release genomio container builds

This PR is simply attempting to allow genomio maintainers to decouple the creation of a genomio python container from the current paradigm of A (Create versioned release) -> trigger CICD docker generation and publish to gitlab + dockerhub.
If a user wants to for whatever reason rebuild the docker container (in this case we needed to rebuild as the container was missing 'ps') then commits can be made, then tagged with a format specific git tag. This should (in principle), though as of now is untested, allow for manual triggering of the pipeline via selection of said git tag.
Tag format:
GenomioDockerRebuild_v[0-9]+.[0-9]+.[0-9]+[a-z]$
In this case, the first ever manual trigger is named: GenomioDockerRebuild_v1.5.0a
I wanted to keep the genomio version information intact as this should aid future tag creation and history tracing.
Users wanting to create a new tag for the above purpose of CICD pipeline initiation should follow the format and check before creation using git tag -l --merged. If a second tag is needed on the same version of genomio (i.e. release version), then serially increment the suffix letter a-> b-> c-> d... etc.

Thank you guys, will update on the success or lack thereof of this approach.


[No QA] Add unit test for report should be displayed in LHN

Explanation of Change

Implement unit tests to verify that the following report types are correctly displayed in the LHN:

[x] Current report: Ensure the currently active report is highlighted appropriately.
[x] Reports with violations (RBR): Confirm that reports with outstanding violations are displayed at the top of the list with a red dot indicator.
[x] Reports requiring attention (GBR): Validate that reports needing user action display a green dot and are sorted correctly.
[x] Report with draft comment: Check that reports with valid draft comments are indicated and sorted by name.
[x] Pinned report: Verify that pinned reports are at the top of the list and sorted correctly.
[x] Unread chat in Focus Mode: Ensure unread chats in focus mode are displayed with bold text.
[x] Archived report in Default Mode: Confirm that archived reports are shown correctly in default mode, sorted by lastVisibleActionCreated.
[x] Self-DM report: Verify that self-DM reports are included in the LHN when the corresponding setting is enabled.

Fixed Issues

$ https://github.com/Expensify/App/issues/52032
PROPOSAL: https://github.com/Expensify/App/issues/52032#issuecomment-2493146883
Tests

Verify the mock test data and the expected is correct
Verify that all requirement cases are covered
Verify all tests are passed in this PR

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Left one minor comment. Besides LGTM.

@OlimpiaZurek I updated.

@mountiny I updated.

@mountiny Done.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


How do I build this

Where is gradle?

The project is currently on hiatus because I'm on vacation, I'll do a commit in 3 days when I get home. Where I will put the additional elements. If you want to build this project really really wip, go back to the old version and get all the net/Minecraft and all the rest of the code and copy and paste it into an mcp. But don't worry I will change the structure of the project soon using the mixing system of spongepowered


Develop pull requests

This pull requests adjusts 2 things. One is an issue when the 2nd and 3rd parameters have null passed to them it throws an error. The second adjusts the field meta data function (_fieldData) to provide an array of options handy for enum field types or even float.

Being picky, but we expect commits to be GPG-signed :)


Write more detail to README

[ ] Write dependencies
[ ] Add demo video using https://asciinema.org/
[ ] Write usage


Add Redis plugin

Plugin Requirements
Backend

[ ] Use redis-rs to connect to a local redis instance
[ ] Expose Redis as data in all handlers
[ ] (optional) if the auth plugin is enabled, cache auth checks in redis

Hey, guys where are we on this?
Can we get some redis-rs integration going on?
Redis is establishing itself as the top in-memory data structure store. It is no longer just for caching.
I'd love to see redis plugin added to this repo soon.

Hey @XChikuX, hope things are well.
I’d love help pushing this forward if you have the time. Let me know and I can give some pointers!

I'm just getting started with rust myself. If you still think I can accomplish this with your guidance, I'd be happy to help!


Extending signalr-go-server for async hub methods and methods with multiple results

Invocation of hub methods which return a chan T. It is waited for the channel to return a single result in a separate goroutine , then the completion is sent
Simple extension for methods returning multiple results

@philippseith are you planning to make those suggested changes?

@philippseith Are you planning to contribute this back? I'd love to merge the PR but it seems as though you're trying to make a standalone repo for the go server impl (which I'd be open to as well).

My final target is to make a standalone repo, because it will be more useful for other go projects. But i might create a new branch with the code changes but without the moving and renaming and open a new pull request  for it.

My final target is to make a standalone repo, because it will be more useful for other go projects. But i might create a new branch with the code changes but without the moving and renaming and open a new pull request for it.

I'd like to own that repo so lets coordinate here. Can we first work on getting your contribution back into this repo then work on making a repo that can be used as a golang package?

I'd like to own that repo so lets coordinate here. Can we first work on getting your contribution back into this repo then work on making a repo that can be used as a golang package?

Yes, we can. I will close this pull request and open another where structure is preserved


ANTLR grammar does not reflect the current state of TSL

It seems the ANTLR grammar file is not used by the project which instead uses a handcrafted parser, as a consequence, the grammar file does not seem to be updated whenever the features of the language evolve thus preventing implementations which rely on the ANTLR4 grammar to be up to date.
As an example, functions such as fill and fillValue are not present in the ANTLR files.
Are there any plans to actually use the grammar file for the go implementation so it would be kept up to date?

Oh, thank you! I will add the missing function into our ANTLR grammar ASAP.
The grammar reflects how the TSL language is parsed. At the moment, we do not have any plan to use the grammar file for our golang parser. It is more a spec to specify how TSL could be supported to query a Time Series Data-Base (as native queries).
Contributions are welcome, of course!

The ANTLR grammar is now up to date and match the TSL 0.0.2 release: https://github.com/ovh/tsl/releases/tag/0.0.2


fix: move output below input to be less confusing

...in some scenarios. it's a stacked graph, so the total height is in+out, when out is tiny and in is large it is not obvious that out is a tiny sliver stacked on top.

fixes #1797
License: MIT
Signed-off-by: Oli Evans<EMAIL_ADDRESS>

Up next, actually seperate out in vs out.

it's also confusing that the 2 guages do not use the same range, but are ranged per direction... it makes visual comparison of the 2 gauages meaningless. They need to share the same max value.

last commit fixes it so out going bandwidth is negative so you can visually compare in vs out

Rebased and reverted BW unit change from https://github.com/ipfs/ipfs-webui/pull/1791 – WebUI should now show the same numeric values as ipfs stats bw.
I also tweaked units, values in tooltip and legend to be unified as well:

Just to be sure, units+values match confirmed with quick eyeballing:


Support X-TIMESTAMP-MAP for WebVTT

On the vtt subtitle fragments, when opened in the subtitle edit, it does a correction/conversion, showing the "translated" times, but with pysubs2, as well with ffmpeg or another program where I can do a simple direct conversion from vtt to srt, this "translation" of the respective times does not happen... I tried to find the logic behind it and noticed that there is a delay based on the MPEGTS value, found at the beginning of the subtitle... does it have anything to do with it?
I am attaching a file where you can see this problem that I mention
file-1_vtt.zip

WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:368640

Yes, the X-TIMESTAMP-MAP seems to be specifying an offset of subtitle times vs. media times ( https://sdks.support.brightcove.com/features/synchronizing-webvtt-captions.html ), though this is not part of the standard ( https://www.w3.org/TR/webvtt1/ ).
To handle this, it would be necessary to know what is the time scale of the MPEGTS timestamp:

Is it 368640 * 1 microsecond?
Is it 368640 * some constant defined in the MPEG-TS standard?
Does it depend on the input file? (let's hope not)

to solve this problem i made a workarround 🤣
delay = TIMESTAMP / 90
so I take this delay value in ms and apply it to the whole subtitle

Note for implementation of X-TIMESTAMP-MAP: The MPEG timestamps should be Presentation Timestamps (PES) with one unit being 1/90000 s. See also https://www.rfc-editor.org/rfc/rfc8216#section-3.5

Here is how SubstitleEdit implemented it:
How it "detect" the presence of X-TIMESTAMP-MAP

https://github.com/SubtitleEdit/subtitleedit/blob/1304bccf757009d8b234f60fa7cc7e951ba46447/src/libse/SubtitleFormats/WebVTT.cs#L270-L274
https://github.com/SubtitleEdit/subtitleedit/blob/1304bccf757009d8b234f60fa7cc7e951ba46447/src/libse/SubtitleFormats/WebVTT.cs#L233-L248

The function that return of how much the subtitle need to be delayed:

https://github.com/SubtitleEdit/subtitleedit/blob/1304bccf757009d8b234f60fa7cc7e951ba46447/src/libse/SubtitleFormats/WebVTT.cs#L398-L457


fix asyncStorageCache

Issue #, if available:
Fix asyncStorageCache getItem() method
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #412 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #412   +/-   ##
=======================================
  Coverage   89.38%   89.38%
=======================================
  Files          54       54
  Lines        2610     2610
  Branches      534      534
=======================================
  Hits         2333     2333
  Misses        266      266
  Partials       11       11

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 b1d6d7a...a039371. Read the comment docs.


Add changes to DG

Codecov Report

Merging #214 (bbe9e0f) into master (8973d1b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #214   +/-   ##
=========================================
  Coverage     65.81%   65.81%
  Complexity      717      717
=========================================
  Files           114      114
  Lines          2542     2542
  Branches        294      294
=========================================
  Hits           1673     1673
  Misses          753      753
  Partials        116      116

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 8973d1b...bbe9e0f. Read the comment docs.


[MMCA-4734] Updated PVAT statements page to be consistent with other statement pages

as per ticket , we should also remove below statements. Let me know if i am missing something.
Statements are only created for periods in which you imported goods.
You can view and download your statements for the last 6 months on this service. Older statements can be requested using the request options at the bottom of this page.

As per ticket, it should be as below. Have a look
As per ticket
Your statements will usually be available after the 10th working day of each month.
With existing code
Your certificates will usually be available after the 10th working day of each month.

The Welsh translation for 'Declarations made using CHIEF' as per ticket should be as below
As per ticket
Datganiadau a wnaed gan ddefnyddio CHIEF
With existing code
Datganiadau a wnaed gan ddefnyddio’r gwasanaeth CHIEF

The Welsh translation for 'Declarations made using CHIEF' as per ticket should be as below. Let me know if the existing is correct Welsh translation
As per ticket
Datganiadau a wnaed gan ddefnyddio CHIEF
With existing code
Datganiadau a wnaed gan ddefnyddio’r gwasanaeth CHIEF

@tyagikumarvineet regarding your comment for welsh.. I’m re-using what’s been used in C79 and Duty Deferment.
The purpose of this ticket is to make all pages in-sync

The Welsh translation for 'Declarations made using CHIEF' as per ticket should be as below. Let me know if the existing is correct Welsh translation
As per ticket
Datganiadau a wnaed gan ddefnyddio CHIEF
With existing code
Datganiadau a wnaed gan ddefnyddio’r gwasanaeth CHIEF

@tyagikumarvineet regarding your comment for welsh.. I’m re-using what’s been used in C79 and Duty Deferment. The purpose of this ticket is to make all pages in-sync

@wg-hmrc okay, if you are saying that is the correct translation, I will approve it. Only thing here is that Welsh translation in the existing code does not match the translation provided in the ticket. Will mention this (for Sujay) in the ticket  so that he can check once he is back


ethportal-api: Re-export PossibleHistoryContentValue and ContentValueError

What was wrong?
Portal-hive tests want to match on PossibleHistoryContentValue which is not exported via ethportal-api.
How was it fixed?
Re-export PossibleHistoryContentValue and ContentValueError from trin-types.
To-Do

[ ] Add entry to the release notes (may forgo for trivial changes)
[x] Clean up commit history

Merging this as it is a hotfix for portal-hive.


Questions about  the Content of Training and Testing Sets in Each 'expk' Folder of the kittival Dataset

Hello.  Thank you for sharing your work. I am a newbie to the field and currently attempting to replicate the experiments from your great paper. I have noted the method of classification by modulus 5 as discussed in previous issues, which has been helpful.
However, I have a specific query about the dataset structure within the individual 'expk' folders. According to the 5-fold cross-validation schema, I understand that the overall dataset is divided into five distinct subsets. What I am seeking to confirm is whether, within a single 'expk' folder, the contents of the 'training' and 'testing' subfolders are identical or if they differ.
Understanding this will help ensure that my replication study adheres strictly to the methodology outlined in your paper. Your guidance on this matter is greatly appreciated.
Thank you for your time and assistance. I am looking forward to your insights.

I apologize, it's just that I have a bit of a blur about the concept of k-fold cross-validation


enhancement reduce memory usage for failed broker loads

Proposed changes
Issue Number: close #xxx
Problem summary
there are still lot of memory of failed broker load after #15895, this pr try to fix this
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run allbuild

run buildall


combine React JSX components and custom loaders

Versions
<!--
Output from: `ng --version`.
If nothing, output from: `node --version` and `npm --version`.
  Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
-->

Observed behavior
<!-- Normally this includes a stack trace and some more information. -->

I have a task, I need to embed the "React" components. But since angular-cli can not load jsx files then compilation produces an error. You may need an appropriate loader to handle this file type.
I dont want use ng eject.
Desired behavior
I would like see any possibility extend webpack config.

Mention any other details that might be useful (optional)

Checkout the slides from this talk by Kyle McNutt. He was able to import React components and package them in an Angular library without needing to eject. The good stuff starts around slide 13.


First pass on developing an policy for the chisel experimental convention

Let the users decide!

With macros it should be possible to implement an @experimental warning. At the minimum, we can do something like the runtime deprecated warnings, and it might also be possible (but difficult) to implement compile-time warnings. Main question would be how to present these warnings:

Should they be verbose by default, or lean by default? If the latter, the default could be "you're using experimental APIs x, y, z, re-run with --verbose-experimental for more details", where it's reasonable to live with the out-of-the-box (no additional flags - and no code to change later) behavior. But the former makes the experimental warnings more obvious, you have to explicitly "acknowledge" and suppress it.
Should the warnings be fully suppressible? How, and in a way that avoids the "you need to remove the suppression flags when features graduate from experimental"? A blanket experimental warnings suppression would work, but might not be useful (it'll probably just get spammed everywhere), while suppression on a per-feature basis is more targeted but requires more code changes. One option could be a project-wide experimental suppression flag, so if you need to change code, at least it's just one place.

I do think that the experimental imports get a bit tedious, and given how often they're used it seems like many are fine living on the bleeding edge, and a more lightweight mechanism is useful.

I vote for proposal 2 and @ducky64's suggestion to use the @experimental annotation to trigger a warning. I think the warning should be lean by default, unless there's an actual API change - this may be too difficult to implement efficiently.
It would be nice if we could use a similar (the same?) mechanism that's used to manage deprecation warnings to suppress @experimental warnings.

There's something to be said about warnings getting lost in noise...

I don't believe there is much of a noise difference between the two proposals, particularly if we create a @experimental annotation. Error will be generated either way

For being more explicit I vote for Proposal 1.
When one imports chisel3.experimental._ then if the experimental feature becomes stable and is moved to chisel3 there is no need for a code change at all, as one imports chisel3._ anyway.
Martin

On 27 Aug, 2019, at 19:33, Chick Markley<EMAIL_ADDRESS>wrote:
Merged #8 https://github.com/freechipsproject/rfcs/pull/8 into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/freechipsproject/rfcs/pull/8?email_source=notifications&email_token=AAE63GC5LIGHG5YULPVHHX3QGVQM3A5CNFSM4INNU3GKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTJAEADA#event-2587901964, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE63GCSVNWKJZL4XE4JVMDQGVQM3ANCNFSM4INNU3GA.

On 27 Aug, 2019, at 21:48, Jack Koenig<EMAIL_ADDRESS>wrote:
When one imports chisel3.experimental._ then if the experimental feature becomes stable and is moved to chisel3 there is no need for a code change at all, as one imports chisel3._ anyway.
If it's moved you won't have to change code, but then if you did import chisel3.experimental.feature your code will break. If the features are copied and deprecated within the experimental package, then if you do import chisel3.experimental._, your code will break due to duplicate definitions

Therefore, the code shall be moved and not copied ;-) Dropping the line chisel3.experimental.feature is a super minimal code change.
Martin


Add parameters to support Okta

Notes
This patch adds parameters to support Okta. Note that it is not possible to dynamically hide or disable a configuration section based on the choosen OIDC provider in CloudFormation, however it is possible to separate the parameters in different sections using the AWS::CloudFormation::Interface metadata, which is the approach adopted in this PR.

Tests
Verified that by choosing Cognito everything continues to work correctly.
PR Quality Checklist

[x] I checked that clusters are listed correctly
[x] I checked that a new cluster can be created (config is produced and dry run passes)
[x] I checked that login and logout work as expected

In order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Please try to run update_infrastructure.sh on the demo environment before merging

The CLIENT_SECRET will var will be changed to take the secret name, the idea is to manage it in a similar way as to what we do for Cognito (https://github.com/aws-samples/pcluster-manager/blob/main/infrastructure/pcluster-manager-cognito.yaml#L51-L137).


add mac compatibility

Now there is a makefile for mac systems.
Additionally, some strictness of clang meant I needed to adjust the unused variables a bit.

bump


⚠ TorrentLeech has degraded performance

In e03594c, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 2654 ms

Resolved: TorrentLeech performance has improved in 601fcf8 after 11 minutes.


⚠ Jenkins Plugins Artifactory has degraded performance

In 339f7e9, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1265 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 5f05078 after 47 minutes.


Merge doc dir with meeting minutes to master

Proposed Changes

add [proj_dir]/doc directory with meeting minutes
this way we can add minutes directly to master after all meetings as well

Related

n/a

We decided against this so we don't have to create new pull requests for each meeting. Instead, we will keep our meeting notes in the doc/meetingnotes.


GradleRunner.withDebug(true) causes tests using --configuration-cache to fail with org.apache.groovy.json.FastStringServiceFactory: Provider org.apache.groovy.json.DefaultFastStringServiceFactory not a subtype

Expected Behavior
Tests can be run with debug enabled without failing
Current Behavior
Tests fail with the following:
FAILURE: Build failed with an exception.
* What went wrong:
Failed to notify build listener.
> org.apache.groovy.json.FastStringServiceFactory: Provider org.apache.groovy.json.DefaultFastStringServiceFactory not a subtype
* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Exception is:
org.gradle.internal.event.ListenerNotificationException: Failed to notify build listener.
	at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:86)
	at org.gradle.internal.event.BroadcastDispatch$CompositeDispatch.dispatch(BroadcastDispatch.java:346)
	at org.gradle.internal.event.BroadcastDispatch$CompositeDispatch.dispatch(BroadcastDispatch.java:249)
	at org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:141)
	at org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37)
	at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
	at com.sun.proxy.$Proxy253.buildFinished(Unknown Source)
…

Context
I'm trying to add tests to Spring Boot's Gradle plugin that use --configuration-cache as part of addressing https://github.com/spring-projects/spring-boot/issues/22922,
Steps to Reproduce

Clone https://github.com/wilkinsona/spring-boot
Check out with-debug-cache-configuration-problem
Run ./gradlew spring-boot-project:spring-boot-tools:spring-boot-gradle-plugin:build

Your Environment
Build scan URL: https://ge.spring.io/s/uyg5ntm6wg4na

That issue is when you use a groovy-json library with a version from 2.5 to up, you could try to use a old version like 2.4.20

Still relevant, AFAIK.


v1.26 docs don't document WindowsHostProcessContainers as generally available

This is a Bug Report

Problem:
https://kubernetes.io/docs/concepts/workloads/pods/#privileged-mode-for-containers states

If your cluster has the WindowsHostProcessContainers feature enabled, you can create a Windows HostProcess pod by setting the windowsOptions.hostProcess flag on the security context of the pod spec. All containers in these pods must run as Windows HostProcess containers. HostProcess pods run directly on the host and can also be used to perform administrative tasks as is done with Linux privileged containers.

However, this feature is in fact GA in v1.26 and cannot be disabled, so we should tweak that wording.
Proposed Solution:
Tweak that wording.
Page to Update:
https://kubernetes.io/docs/concepts/workloads/pods/#privileged-mode-for-containers

Kubernetes Version:
1.26 (unreleased at time issue was filed)
Additional Information:
/sig node
/sig windows
If making changes before the v1.26 release, file a PR against the dev-1.26 branch.

PR https://github.com/kubernetes/website/pull/37340 could have included this update.

/remove-lifecycle rotten


tiny import issue in one of the example demos

I just wanted to check out the animation and ran accross this issue while compiling
ERROR in ./demos/sunburst/index.js
Module not found: Error: Can't resolve './Partition' in '.../react-spring/examples/demos/sunburst'
 @ ./demos/sunburst/index.js 10:0-36 101:27-36
 @ ./demos lazy ^\.\/.*$ namespace object
 @ ./index.js
 @ multi (webpack)-dev-server/client?http://localhost:8080 index.js
ℹ ｢wdm｣: Failed to compile.

It's basically just a typo in this import from Sunburst demo:
import Partition from './Partition'
Uppercase instead of the lowercase P in ... from './Partition'

Strange, it's uppercase in my local repo, but lower on Github. Have to Google this, never came across something like it before.

git config core.ignorecase false did it, it's updated now ... Thanks!

you could also use:
import { Partition } from '@vx/hierarchy'

if you wanted


Updating drivers for *Scream from \Scream\Install\driver\x64\Scream.inf

My CI project was running on Windows and today (07/JUL/2023) it started to fail:
Run Invoke-WebRequest https://github.com/duncanthrax/scream/releases/download/3.8/Scream3.8.zip -OutFile Scream3.8.zip

PSParentPath: Microsoft.PowerShell.Security\Certificate::LocalMachine\TrustedPublisher

Thumbprint                                Subject
----------                                -------
Device node created. Install is complete when drivers are installed...
Updating drivers for *Scream from D:\a\my-project\my-project\Scream\Install\driver\x64\Scream.inf.
Error: The operation was canceled.

In the last revision, the file scream-master\Install\driver\x64\scream.cat appears with the certificate expired (JUL/07/2023).

Time flies :) I'll get a new signing cert next week.

Any chance of renewing the cert?
Really appreciate the project btw 🙏 It's made cross-platform audio testing a breeze.

These days, code signing requires a hardware key store and an extraordinary amout of money. I have ordered a kit from certum.eu, but it hasn't arrived yet. They have special pricing for Open Source projects. I hope that this will work.

Ugh, that's horrible. Thank you for the update!

Thank you @duncanthrax, this is an unfortunate limitation of windows.
I now edited the registry with:
New-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Control\CI\Policy" -Name "UpgradedSystem" -Value "00000001"  -PropertyType "dword"

But the command:
Scream\Install\helpers\devcon-x64.exe install Scream\Install\driver\x64\Scream.inf *Scream

still fails with:
Device node created. Install is complete when drivers are installed...
Updating drivers for *Scream from C:\Users\Gustl\Downloads\test audio device\Scream\Install\driver\x64\Scream.inf.
devcon-x64.exe failed.

I appreciate the work and I understand if this is not something on the priority list :) Have a nice day ;D

FYI, you can still buy a code signing certificate without a hardware key. We purchased one ourselves from here (sectigo.com) and it's been working fine

@adonisd it seems that since June 1 this year, a hardware key is required. But that isn't the problem, see my next post.

Some bad news. I've jumped through all the burning hoops to get a hardware kit, new cert + the signtool plumbing right. I've used certum.pl, they have an "Open Source" offering for code signing at a very reasonable price (EUR 25 per year).
However, that cert uses a chain which does not allow verification for kernel mode drivers. You'd need the EV mode cert, which isn't available for the Open Source pricing. The EV mode cert comes in at around EUR 250 per year, if you take the 3-year package (749 EUR total). That is a bit too much for me to spend on a hobby project. I have looked for alternatives, but there are none, it seems.
Going forward, I need someone else to sign the driver. Wether that person (or Organization) already has a kernel-capable EV cert, or buys one, does not really matter. It also does not matter whose name is baked into the signature. I don't think any of the Scream users care.
So, if any of you guys have a commercial or philantrophic interest, and you already have an EV cert, or can spare the cash to afford one, let me know.

Here is a portion of my script that works:
  $currentDate = Get-Date

  Write-Host "Current Date: $currentDate";
  $newDate = Get-Date "2023-07-04 12:00:00";

  Write-Host "Setting date to: $newDate to circumvent cert issue";
  Set-Date $newDate;
  # ! Scream driver certificate expired on July 5th, to avoid issues while installing driver we set the clock to July 4th, install the driver
  # ! then revert back to the original date/time
  # ? Get Latest release from the github repo
  $gitRepo = "duncanthrax/scream";
  $latest = (Invoke-RestMethod -Method Get -Uri https://api.github.com/repos/$gitRepo/releases/latest | Select-Object -ExpandProperty tag_name);
  # ? Download latest release
  Invoke-Webrequest -Uri https://github.com/duncanthrax/scream/releases/download/$latest/Scream$latest.zip -Out "scream.zip";
  Expand-Archive scream.zip
  # ? Extract the certificate from the driver file
  # ! We need to import the certificate to TrustedPublisher so that we can install the driver unattended.
  $driverFile = 'scream\install\driver\x64\Scream.sys';
  # ? Extract Cert
  $cert = (Get-AuthenticodeSignature $driverFile).SignerCertificate;
  Export-Certificate -Cert $cert -FilePath $PWD\scream\scream.crt
  # ? Install Cert in Cert:\LocalMachine\TrustedPublisher
  Import-Certificate -FilePath $PWD\scream\scream.crt -CertStoreLocation Cert:\LocalMachine\TrustedPublisher
  # ! We need to remove the "pause" at the end of their batch script to make sure we can go ahead unattended.
  Set-Content -Path $PWD\scream\install\install-x64.bat -Value (get-content -Path $PWD\scream\install\install-x64.bat | Select-String -Pattern 'pause' -NotMatch)
  # ? Install the SCREAM WDDM driver
  cmd.exe /c $PWD\scream\install\install-x64.bat
  # ? Cleanup
  rmdir -Force -Recurse .\scream
  rm -Force .\scream.zip
  # ? Enable Audio SRV STARTUP
  Set-Service -Name audiosrv -StartupType Automatic;
  Set-Service -Name audiosrv -Status Running -PassThru;
  # ? Revert back to current date
  Set-Date $currentDate;

If you're not sure about running scripts you can also open an admin command prompt, type "date" and enter a new date - quickly install the driver - then type "date" again to set the date back to today.

@adonisd I think resyncing is more precise:
Set-Date (Get-Date "2023-07-04 12:00:00")
# Do installation ...
w32tm /resync /force; $currentDate = Get-Date; Write-Host "Current Date: $currentDate";

@adonisd I think resyncing is more precise:
net stop w32time; Set-Date (Get-Date "2023-07-04 12:00:00")
# Do installation ...
net start w32time; w32tm /resync /force; $currentDate = Get-Date; Write-Host "Current Date: $currentDate";

For Github Actions, note that you have to disable the time sync for Hyper-V before, see actions/runner-images#8105 (comment) :
      - name: Disable time sync with Hyper-V
        run: |
          Set-Service -Name vmictimesync -Status stopped -StartupType disabled
          Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\services\W32Time\Parameters -Name 'Type' -Value 'NoSync'

It's ridiculous that this is required, but I can confirm this still works on Windows 11 24H2 as of today.

I was wrong. Changing the time no longer works. I misread the output the first time.


BTableProviderContext isn't exported by the root import

If you want to use BTableProviderContext you need to import directly from the relevant file in the dist directory as it's not included in dist/types/exports/index.d.ts :
import {BTableProviderContext} from "bootstrap-vue-next/src/types/components";

However, due to the use of exports in package.json, vite complains with:
✘ [ERROR] [plugin vite:dep-scan] Missing "./dist/types/components" specifier in "bootstrap-vue-next" package

    script:/var/www/html/resources/js/components/report_requests/ReportRequestList.vue?id=0:86:7:
      86 │ import "bootstrap-vue-next/dist/types/components"
         ╵        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  This error came from the "onResolve" callback registered here:

    node_modules/esbuild/lib/main.js:1287:20:
      1287 │       let promise = setup({

fixed 0.15


fix compatibility with recent websocket-client module

Does this need a >= version check on websocket-client here? https://github.com/omniploy/python-actioncable-zwei/blob/bd0addb1e52053854d0ceccab4036bf0a52fc1dc/setup.py#L13

Ok I pinned the first release which was including this commit : https://github.com/websocket-client/websocket-client/commit/eaf1b8cd4d915a4c8cb68f21a8a9dc81a9db7d15


Repository tabs with invalid dir settings cannot be selected

When you edit a repository configuration and set an invalid dir value (one that does not exist), tab hangs up when attempting to select the tab
If the directory does not exist, tab should produce a warning and not set any working directory.
The logs don't show anything obvious, but maybe the shell process is failing to initialize?

Here is a log of a tab hangup.  There is no CLI output.
log.txt

Fix implemented in #175, going out in 0.4.0

Closing, v0.4.0 is released!


Maintain an rsync log

Maintain a log of the rsync stdout so the user can inspect it

Now happens automatically since the rsync log goes into stdout


Fix build errors.

Followup #8.
Fixes #12.

Can you please split this into two PRs, one that just fixes the breakage, and one with your improvements and layout changes? Thanks.

Can I split it into 2 commits within that PR? Or do you really want 2 separate PRs?

Make it two PRs, please. The fix for the breakage can likely be merged as is; the other changes my warrant discussion.

All right, sure.

PTAL.

Thank you.


Al's directions for updating the cdc.csv

Heres a thought of a short term hack that might work in the long term.  Hard to really visualize without doing it and seeing what pops up but...:

could determine which columns in data-raw/cdc/cdc.csv are needed to tie Species Code to Element Code. Make a new csv called xref_sp_element_codes.csv (or something) and burn just those columns to it
Not sure I understand this part but I know there are a bunch of columns in the old cdc.csv that we need to join to our updated cdc resutls because they are missing. Columns such as Kingdom, Phylumn, Class, Order, etc, and Species Code. This is done later.
download both exports from the cdc website into data-raw.  keep their names as is if they are descriptive (can't remember)
In a new data-raw/cdc.R file read in xl files with readxl (I think you need to open them first and close or some weird thing to avoid a  error - link to help url in your .R file  if you run into it) and export both of those as csvs with their original exported names in data-raw.
In data-raw/cdc.R join  both exports from the cdc website together by Element Code excluding any duplicated columns - then join to  xref_sp_element_codes.  if there are missing Species Code entries in any rows we have new codes to find (don't know how yet) and if there are less unique(cdc$Species Code) than before we lost some. Can document that in data
burn over data-raw/cdc/cdc.csv
Run through fishbc/data-raw/data-raw.R and  run usethis::use_data(cdc, overwrite = TRUE)
build the repo locally (just like fpr)
Worst that can happen is we redo using new branch....

Not sure I understand this part but I know there are a bunch of columns in the old cdc.csv that we need to join to our updated cdc resutls because they are missing. Columns such as Kingdom, Phylumn, Class, Order, etc, and Species Code. This is done later.


Connection API accepts SDP for receivers lacking ts-refclk or mediaclk media attributes

As an example, the following PATCH request was accepted
uuid=191941ea-84e5-52ae-81ee-ccf59bba9f1b; curl -v -H Content-Type: application/json -H Accept: application/json -X PATCH  http://d13:3215/x-nmos/connection/v1.0/single/receivers/191941ea-84e5-52ae-81ee-ccf59bba9f1b/staged  -d '{"master_enable": false, "transport_file": { "data": "v=0\r\no=- 1234 2 IN IP4 <IP_ADDRESS>\r\ns=!\r\nt=0 0\r\nm=audio 20111 RTP/AVP 97\r\ni=Second PCM audio pair, 24-bit samples\r\nc=IN IP4 <IP_ADDRESS>/32\r\na=source-filter:incl IN IP4 <IP_ADDRESS> <IP_ADDRESS>\r\na=rtpmap:97 L24/48000/4\r\na=fmtp:97 channel-order=SMPTE2110.(ST)\r\na=ptime:1\r\na=mediaclk:direct=0\r\n", "type": "application/sdp"},"activation": {"mode": "activate_immediate"}}'
For reference, SMPTE 2110-10 §8 requires these attributes.

Relatedly and belatedly, the contents of the ts-refclk entry don't seem to get parsed very carefully, either. The following all get through:
a=ts-refclk:ntp=23<IP_ADDRESS>
a=ts-refclk:ntp=;<IP_ADDRESS>
a=ts-refclk:ptp=IEEE1588-2008:08-00-11-ff-fe-21-db-34:127:42
a=ts-refclk:ptp=IEEE1588-2008:408-00-11-ff-fe-21-db-34:127
a=ts-refclk:ptp=IEEE1588-2008:08-00-11-ff-fe-21-db-34:337

That said, I don't know how particular the parser can be. The first one, in particular, pushes up against the old "what is a host name?" question.

OK, reviewing ts-refclk and mediaclk first before getting on to the wider issue...
ST 2110-10:2017 Section 8.1 says:

All stream descriptions shall have a media-level mediaclk attribute as per IETF RFC 7273 section 5.2 The direct reference should be used.

To be clear, RFC 7273 Section 5.2 defines how to signal a "direct-referenced media clock" but doesn't make it mandatory, that's all ST 2110-10. RFC 7273 also defines how "signalling included at session level provides default parameters for all RTP sessions and sources in the session description. More specific signalling included at the media level overrides session-level signalling." ST 2110-10 is overruling that, which seems somewhat heavy-handed.
ST 2110-10:2017 Section 8.2 says:

All stream descriptions shall have a media-level ts-refclk attribute as specified in IETF RFC 7273 section 4.

And as above, RFC 7273 Section 4 defines "timestamp reference clock source signalling" but it's ST 2110-10 that's making it required at the media level.
Although NMOS is designed to support RTP streams that aren't ST 2110 (as well as other transports completely), it seems reasonable for nmos::get_session_description_sdp_parameters and nmos::validate_sdp_parameters etc. (declared in nmos/sdp_utils.h) to be focused on ST 2110.
However, since we know implementations exist that don't signal ts-refclk and mediaclk as required by ST 2110-10, what should we do?
It would be easy enough to reject them - e.g. for ts-refclk, a small change in nmos::get_session_description_sdp_parameters to throw details::sdp_processing_error("missing timestamp reference clock source") if it's not present.
However, I can imagine implementations wanting to "do their best" with such incoming SDP files?

To recap how the Connection API is intended to reject PATCH /staged requests that it doesn't like, it's a 400 response if the JSON is invalid (syntax or schema) or doesn't meet the /constraints, or a 500 "if the transport file could not be parsed, or there is some failure caused by activation which was not caused by a violation or schema or constraints."
The case that we're talking about of staging an SDP file that can be parsed, but isn't valid according to ST 2110 falls in a grey area therefore. But probably a 500 response to the PATCH /staged request is expected, even if the request didn't specify activation.
In nmos-cpp, we don't actually have the ability to allow user code to validate a Connection API request until activation, and that's arguably too late. :disappointed:
One potential solution is to use more state-transitions in the Connection API as @billt-hlit originally proposed, storing the merged request in e.g. "staging", next to "staged" and "active". I am coincidentally wondering about using an "auto" sibling to allow simpler but greater flexibility than the current resolve_auto approach.

A better solution to validating PATCH /staged requests before they are applied, let alone before activation, may be to add std::function callbacks (or hooks as @jwpwh has called them in #77, etc.) to nmos::make_connection_api (the Connection API factory function). This makes sense for things which do not need to be asynchronous, such as parsing and validating the SDP file (also cf. #38, #39, #74) and possibly for resolve_auto at the point of activation.

I like your callback idea. The callback could even enforce more semantic constraints (like "this receiver only supports HD") that might be particular to the hardware.

I think all of the above can be dealt with once PR #81 is merged.
Handle "staging an SDP file that can be parsed, but isn't valid according to ST 2110" or has "things that the actual node implementation doesn't like", or "enforce more semantic constraints (like "this receiver only supports HD")" by providing a custom nmos::transport_file_parser callback and/or a custom nmos::details::connection_resource_patch_validator callback.

Closed by #81.


Feature/audit logs

Entire log path is recorded as a shared volume of the compose script so no need to alter that.

Pull Request Check List

~Unit Tests & Regression Tests Added (Optional)~
[x] Removed Unnecessary Logs/System.Outs/Comments/TODOs
[x] Added enough Logging to monitor expected behaviour change
[x] Security - Injection - everything run by an interpreter (SQL, OS...) is either validated or escaped
[x] Security - Data Exposure - PII is not stored or sent unencrypted
[x] Security - Data Exposure - Test any altered or created endpoints using swagger
[x] Security - Access Control - Check authorisation on every new endpoint
[x] Security - New dependency - configured sensibly not relying on defaults
~Updated Release Procedure & Documentation (& Considered Implications to Previous Versions)~
[ ] Peer-Reviewed

I know this will now be a pain, having looked at the code, but I had hoped we could record both the JSESSIONID and the Segue user ID (or null), since both separately are useful for working out what is going on.

I know this will now be a pain, having looked at the code, but I had hoped we could record both the JSESSIONID and the Segue user ID (or null), since both separately are useful for working out what is going on.

I had though that that could maybe be useful, that's OK shouldn't be too difficult 👍

I'm excited to see how this works in practice!
One last thing that occurs to me; does the AuditMonitor filter happen inside the PerformanceMonitor timings, or outside it? I.e. will we be able to see if this causes a performance overhead, or will that monitoring miss any delay this adds? Does the order the filters are registered matter?

Good question. It looks like we can apply a priority to the filter. Thankfully, from testing, priority 0 (or low) means apply first on request, last on response which is exactly what we want for the performance monitor.


[core]Verify that the number of partition fields should not be the same as the field

Purpose
Verify that the number of partition fields should not be the same as the field，When I create an append-only table and set the number of partitions to be consistent with the number of fields, the data under each partition is the same.
Tests
org.apache.paimon.schema.TableSchemaTest#testValidatePartitionKeys
API and Format
Documentation

@JingsongLi  cc


2D or 3D when testing

Hey! You guys really did an excellent and meaningful job! I've read your paper and am slightly confused about the data dimension. I wonder if you test the final result as 2D data or treat it as 3D data when using DSC and NSD methods? Thanks a lot! this can help me to understand your work better!

Sorry, I didn't make it clear. Of course, I am uncertain about the data dimension you use to quantity test the result when processing the CT, MR, or PET, these 3D image segmentation tasks.

Hi @WuJuli ,
Thanks for your interest.
For 3D data, the inference was done in a slice-by-slice way (2D). However, the computation of DSC and NSD was in 3D. You can find more details in the inference script.

Thank you for your answer! I've read the code part! I have some other questions, do you have different values of spacing_mm for the different tasks when calling the function compute_surface distances(mask_gt, mask_pred, spacing_mm)? And can you share your training data?

do you have different values of spacing_mm for the different tasks

They were set to (1,1,1) for all tasks. Since all the methods were compared under the same spacing, the comparison is still fair.

And can you share your training data?

All the datasets are publicly available and you can download them from the given data source. For most of the datasets, we don't have right to redistribute them.

Thank you for your detailed explanation! Appreciate that!


Enabled OIDC in terraspace_plugin_azurerm

terraform provider supports oidc but when we use this block in terraspace it give ARM Rest error
Support for OpenID Connect was added in version 3.7.0 of the Terraform AzureRM provider.
As per terraform doc
It is recommend using the required_providers block to set the
Azure Provider source and version being used
terraform {
required_providers {
azurerm = {
source  = "hashicorp/azurerm"
version = "=3.7.0"
}
}
}
Configure the Microsoft Azure Provider
provider "azurerm" {
use_oidc = true
features {}
}
with OIDC support export of client_secret should not be needed.
Terraspace error:
Exception Armrest::Error: #Net::HTTPUnauthorized:0x000055e98bb9da78
/var/lib/gems/3.0.0/gems/armrest-0.1.3/lib/armrest/api/base.rb:43:in request' /var/lib/gems/3.0.0/gems/armrest-0.1.3/lib/armrest/api/base.rb:18:in block (2 levels) in class:Base'
/var/lib/gems/3.0.0/gems/armrest-0.1.3/lib/armrest/services/resource_group.rb:20:in create_or_update' var/lib/gems/3.0.0/gems/terraspace_plugin_azurerm-0.7.0/lib/terraspace_plugin_azurerm/interfaces/backend/resource_group_creator.rb:19:in create_or_update_resource_group'

Did you find a solution/workaround to this by any chance? Experiencing same behavior and error:
#297
Building .terraspace-cache/eastus/dev/stacks/demo
Current directory: .terraspace-cache/eastus/dev/stacks/demo
Creating Resource Group dev-eastus...
Exception Armrest::Error: #Net::HTTPUnauthorized:0x0000556a81945408
/opt/terraspace/embedded/lib/ruby/gems/3.0.0/gems/armrest-0.1.3/lib/armrest/api/base.rb:43:in request' /opt/terraspace/embedded/lib/ruby/gems/3.0.0/gems/armrest-0.1.3/lib/armrest/api/base.rb:18:in block (2 levels) in class:Base'
/opt/terraspace/embedded/lib/ruby/gems/3.0.0/gems/armrest-0.1.3/lib/armrest/services/resource_group.rb:20:in create_or_update' /opt/terraspace/embedded/lib/ruby/gems/3.0.0/gems/terraspace_plugin_azurerm-0.7.0/lib/terraspace_plugin_azurerm/interfaces/backend/resource_group_creator.rb:19:in create_or_update_resource_group'


In App Purchase: Allow subscription upgrade or downgrade

Hi,
I was wondering whether subscription upgrades, by passing the product IDs for the current subscription and the future (upgraded or downgraded) subscription to the BillingFlowParams, are already supported in https://pub.dev/packages/in_app_purchase?
More context:

Android: https://developer.android.com/google/play/billing/billing_subscriptions#Allow-upgrade
iOS: https://medium.com/revenuecat-blog/ios-subscription-groups-explained-8c5b8325d4ab

Tx for your input,
Philip

This is very important, i'm also needing it for my app, thanks for the help

Please wee need this, it is a very important feature, thanks for the support

+1

I already made a feature request for this
https://github.com/flutter/flutter/issues/32395

Closing as duplicate as @rahulraj64 pointed out.


Items are not removed immediately

Actual behaviour

I have Remove automatically read items set to Immediately
When I read the feed and come back, the read items are not removed.
When I switch to the Unread tab and back to Subscriptions, the items are removed

Expected behaviour

Read items should be removed immediately

Steps to reproduce
https://www.dropbox.com/s/lzyena9k4cajhy7/bug.mov?dl=0
Configuration

Miniflux version: Hosted
OS: MacOSX 10.12.2
Browser: Chrome

I just deployed a fix, it should work better now.

Confirmed. Thanks.


MicroHacks for Managed Kubernetes Service (AKS) and Microservices with Azure Container Apps

@microsoft-github-policy-service agree company="MaibornWolff GmbH"

@judithmh can you check for the last comment pls? :)

Thank you very much @judithmh and @rajata07


ESLint server stopped in VSCode DevContainer

Using this extenstion, ESLint stop working: With the following error:
[Info  - 8:46:46 AM] ESLint server is starting.
[Info  - 8:46:47 AM] ESLint server running in node v16.17.1
[Info  - 8:46:48 AM] ESLint server is running.
[Info  - 8:46:50 AM] ESLint library loaded from: /workspaces/xxx/node_modules/eslint/lib/api.js
<--- Last few GCs --->
[652:0x4e60de0]    28495 ms: Scavenge (reduce) 2045.3 (2082.5) -> 2045.0 (2082.5) MB, 5.4 / 0.0 ms  (average mu = 0.437, current mu = 0.389) allocation failure
[652:0x4e60de0]    29260 ms: Mark-sweep (reduce) 2047.2 (2084.0) -> 2046.7 (2084.3) MB, 716.5 / 0.0 ms  (+ 306.8 ms in 80 steps since start of marking, biggest step 5.2 ms, walltime since start of marking 1117 ms) (average mu = 0.293, current mu = 0.192)
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0xb02960 node::Abort() [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
2: 0xa18149 node::FatalError(char const*, char const*) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
3: 0xcdd22e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
4: 0xcdd5a7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
5: 0xe94c15  [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
6: 0xea48dd v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
7: 0xea75de v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
8: 0xe68852 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
9: 0xe6316c v8::internal::FactoryBasev8::internal::Factory::AllocateRawArray(int, v8::internal::AllocationType) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
10: 0xe63245 v8::internal::FactoryBasev8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Handlev8::internal::Map, int, v8::internal::Handlev8::internal::Oddball, v8::internal::AllocationType) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
11: 0x10cbace v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocatev8::internal::Isolate(v8::internal::Isolate*, int, v8::internal::AllocationType) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
12: 0x10cbb83 v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehashv8::internal::Isolate(v8::internal::Isolate*, v8::internal::Handlev8::internal::OrderedHashMap, int) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
13: 0x11d7cb5 v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
14: 0x15d54f9  [/vscode/vscode-server/bin/linux-x64/695af097c7bd098fbf017ce3ac85e09bbc5dda06/node]
[Info  - 8:47:17 AM] Connection to server got closed. Server will restart.
How to extend the memory of NODE.JS running in a DevContainer?

There is a setting that you can use to control the heap size for the ESLint server. It is eslint.execArgv and the documentation shows how to increase the heap size (https://github.com/microsoft/vscode-eslint/blob/main/README.md).


How to see if a user(JID) is online or connected?? Last_activity time(Ejabberd)

I am trying to see if there is anyway to detect if a user JID is online or connected when i don't know the SID(session id). Do i have to use the roster? Or if there is a plugin that would do the job?
Or would i have to check their last activity? I am using Ejabberd.

I don't think you can do it without a SID, at least not when you're using BOSH. That's like trying to see whether someone is online without being connected to an XMPP server.

Hi, thanks for the reply. Would it work if i send an iq to request the last activity time? So if there is no last activity time, then i assume its online, if it returns a last activity time then i know the user isnt online? I tried doing the below....but it isnt working.
 var iq = $iq({
          type: 'get',
          id: 'last1',
          to<EMAIL_ADDRESS>})
.c('query', {xmlns: 'jabber:iq:last'});
conn.sendIQ(iq);

Do you have a valid SID and BOSH session when you do that?

The "requesting person" is connected/does, so jid1 connects, and sendiq to check jid2 last activity, like below....do you think it will work??
var iq = $iq({
          type: 'get',
          id: 'last1',
          to<EMAIL_ADDRESS>})
.c('query', {xmlns: 'jabber:iq:last'});
conn.sendIQ(iq);

From the "last activity" spec: It is typically used by an IM client to retrieve the most recent presence information from an offline contact by sending a last activity request to the server that hosts the account controlled by the contact.
So it doesn't tell you whether another contact is online or not. If you're subscribed to that contact, then you should automatically get presence updates informing you whether that contact is online or not.

Hi, thanks! I managed to get it working, i made the subscribed process automatic and then it worked for my need thank!


Controller loses shipyard-swarm-manager

Hi,
After having got Shipyard up and running with the automated deploy script I have been really impressed. However, after a few hours of running I am coming across an issue whereby the containers disappear from the list and the web UI is showing a loading spinner that never stops and nothing else happens. The controller itself isn't broken because I can load up a new tab, login etc.
I've removed and reinstalled the whole thing which solves the issue but after a few hours it happens again.
There's nothing of interest in the container logs and I'm not sure what to consider next. Any ideas?
Thanks.

docker restart shipyard-swarm-manager seems to get it back. What is the problem likely to be with swarm manager?

This will happen if the Swarm agent stops.  Is there any memory constraints that would be causing the container to be killed?  Can you paste your Docker version info?

Having this issue as well...  restarting manager does get everything back up and running... checked the manager's log... not much useful info there

Can you paste the logs of the controller. It may help even if it doesn't
seem like it. It's most likely an etcd issue as it's not HA.
On Dec 12, 2015 23:41, "ephemeraleclipse"<EMAIL_ADDRESS>wrote:

Having this issue as well... restarting manager does get everything back
up and running... checked the manager's log... not much useful info there
—
Reply to this email directly or view it on GitHub
https://github.com/shipyard/shipyard/issues/644#issuecomment-164223008.

 What are the logs from the other containers?

Swarm Agent's log is just bunch of "Registering on the discovery service every 20s..."
Swarm Manager's log is:
INFO[0000] Listening for HTTP                            addr=<IP_ADDRESS>:3375 proto=tcp
INFO[0000] Leader Election: Cluster leadership lost
ERRO[0000] Discovery error: Unexpected watch error
ERRO[0000] Leader Election: watch leader channel closed, the store may be unavailable...
INFO[0000] Leader Election: Cluster leadership acquired
INFO[0020] Registered Engine us1 at {{IP Redacted}}:2375
ERRO[0663] Get http://{{IP Redacted}}:2375/v1.15/info: dial tcp {{IP Redacted}}:2375: connection refused
INFO[46680] Registered Engine docker-node-1 at {{IP Redacted}}:2375
INFO[0000] Listening for HTTP                            addr=<IP_ADDRESS>:3375 proto=tcp
INFO[0000] Leader Election: Cluster leadership lost
INFO[0000] Registered Engine us1 at {{IP Redacted}}:2375
INFO[0000] Registered Engine docker-node-1 at {{IP Redacted}}:2375
ERRO[0003] HTTP error: No elected primary cluster manager  status=500
ERRO[0009] HTTP error: No elected primary cluster manager  status=500
INFO[0014] Leader Election: Cluster leadership acquired

etcd logs:
[etcd] Dec 11 06:16:31.005 WARNING   | Using the directory f164b7a508cc.etcd as the etcd curation directory because a directory was not specified.
[etcd] Dec 11 06:16:31.006 INFO      | f164b7a508cc is starting a new cluster
[etcd] Dec 11 06:16:31.009 INFO      | etcd server [name f164b7a508cc, listen on :4001, advertised url http://{{{{IP Redacted}}}}:4001]
[etcd] Dec 11 06:16:31.009 INFO      | peer server [name f164b7a508cc, listen on :7001, advertised url http://{{IP Redacted}}:7001]
[etcd] Dec 11 06:16:31.010 INFO      | f164b7a508cc starting in peer mode
[etcd] Dec 11 06:16:31.010 INFO      | f164b7a508cc: state changed from 'initialized' to 'follower'.
[etcd] Dec 11 06:16:31.010 INFO      | f164b7a508cc: state changed from 'follower' to 'leader'.
[etcd] Dec 11 06:16:31.010 INFO      | f164b7a508cc: leader changed from '' to 'f164b7a508cc'.
[etcd] Dec 11 07:29:13.600 INFO      | f164b7a508cc: snapshot of 10003 events at index 10003 completed
[etcd] Dec 11 08:41:44.094 INFO      | f164b7a508cc: snapshot of 10006 events at index 20009 completed
[etcd] Dec 11 09:54:14.596 INFO      | f164b7a508cc: snapshot of 10006 events at index 30015 completed
[etcd] Dec 11 11:06:45.089 INFO      | f164b7a508cc: snapshot of 10006 events at index 40021 completed
[etcd] Dec 11 12:19:15.583 INFO      | f164b7a508cc: snapshot of 10005 events at index 50026 completed
[etcd] Dec 11 13:31:46.083 INFO      | f164b7a508cc: snapshot of 10007 events at index 60033 completed
[etcd] Dec 11 14:44:16.590 INFO      | f164b7a508cc: snapshot of 10005 events at index 70038 completed
[etcd] Dec 11 15:56:47.097 INFO      | f164b7a508cc: snapshot of 10006 events at index 80044 completed
[etcd] Dec 11 17:08:44.591 INFO      | f164b7a508cc: snapshot of 10008 events at index 90052 completed
[etcd] Dec 11 18:18:15.076 INFO      | f164b7a508cc: snapshot of 10009 events at index 100061 completed
[etcd] Dec 11 19:27:48.577 INFO      | f164b7a508cc: snapshot of 10008 events at index 110069 completed
[etcd] Dec 11 20:37:16.093 INFO      | f164b7a508cc: snapshot of 10001 events at index 120070 completed
[etcd] Dec 11 21:46:46.586 INFO      | f164b7a508cc: snapshot of 10007 events at index 130077 completed
[etcd] Dec 11 22:56:14.077 INFO      | f164b7a508cc: snapshot of 10002 events at index 140079 completed
[etcd] Dec 12 00:05:41.584 INFO      | f164b7a508cc: snapshot of 10001 events at index 150080 completed
[etcd] Dec 12 01:15:12.079 INFO      | f164b7a508cc: snapshot of 10009 events at index 160089 completed
[etcd] Dec 12 02:24:39.570 INFO      | f164b7a508cc: snapshot of 10001 events at index 170090 completed
[etcd] Dec 12 03:34:10.059 INFO      | f164b7a508cc: snapshot of 10007 events at index 180097 completed
[etcd] Dec 12 04:43:37.547 INFO      | f164b7a508cc: snapshot of 10002 events at index 190099 completed
[etcd] Dec 12 05:53:05.032 INFO      | f164b7a508cc: snapshot of 10001 events at index 200100 completed
[etcd] Dec 12 07:02:35.526 INFO      | f164b7a508cc: snapshot of 10009 events at index 210109 completed
[etcd] Dec 12 08:12:03.010 INFO      | f164b7a508cc: snapshot of 10002 events at index 220111 completed
[etcd] Dec 12 09:21:30.487 INFO      | f164b7a508cc: snapshot of 10001 events at index 230112 completed
[etcd] Dec 12 10:31:00.969 INFO      | f164b7a508cc: snapshot of 10009 events at index 240121 completed
[etcd] Dec 12 11:40:31.446 INFO      | f164b7a508cc: snapshot of 10007 events at index 250128 completed
[etcd] Dec 12 12:50:01.923 INFO      | f164b7a508cc: snapshot of 10007 events at index 260135 completed
[etcd] Dec 12 13:59:29.408 INFO      | f164b7a508cc: snapshot of 10003 events at index 270138 completed
[etcd] Dec 12 15:08:59.893 INFO      | f164b7a508cc: snapshot of 10007 events at index 280145 completed
[etcd] Dec 12 16:18:27.387 INFO      | f164b7a508cc: snapshot of 10002 events at index 290147 completed
[etcd] Dec 12 17:27:54.872 INFO      | f164b7a508cc: snapshot of 10001 events at index 300148 completed
[etcd] Dec 12 18:37:25.357 INFO      | f164b7a508cc: snapshot of 10007 events at index 310155 completed
[etcd] Dec 12 19:46:52.837 INFO      | f164b7a508cc: snapshot of 10002 events at index 320157 completed
[etcd] Dec 12 20:56:20.325 INFO      | f164b7a508cc: snapshot of 10001 events at index 330158 completed
[etcd] Dec 12 22:05:50.823 INFO      | f164b7a508cc: snapshot of 10007 events at index 340165 completed
[etcd] Dec 12 23:15:18.311 INFO      | f164b7a508cc: snapshot of 10002 events at index 350167 completed
[etcd] Dec 13 00:24:45.805 INFO      | f164b7a508cc: snapshot of 10001 events at index 360168 completed
[etcd] Dec 13 01:34:16.292 INFO      | f164b7a508cc: snapshot of 10009 events at index 370177 completed
[etcd] Dec 13 02:43:46.769 INFO      | f164b7a508cc: snapshot of 10009 events at index 380186 completed
[etcd] Dec 13 03:53:20.286 INFO      | f164b7a508cc: snapshot of 10005 events at index 390191 completed
[etcd] Dec 13 05:02:50.774 INFO      | f164b7a508cc: snapshot of 10007 events at index 400198 completed
[etcd] Dec 13 06:12:21.262 INFO      | f164b7a508cc: snapshot of 10009 events at index 410207 completed

Ya try a manager restart. We should get a proper HA deploy that would
handle restarts more graceful.
On Dec 12, 2015 23:55, "ephemeraleclipse"<EMAIL_ADDRESS>wrote:

Swarm Agent's log is just bunch of "Registering on the discovery service
every 20s..."
Swarm Manager's log is:
INFO[0000] Listening for HTTP                            addr=<IP_ADDRESS>:3375 proto=tcp
INFO[0000] Leader Election: Cluster leadership lost
ERRO[0000] Discovery error: Unexpected watch error
ERRO[0000] Leader Election: watch leader channel closed, the store may be unavailable...
INFO[0000] Leader Election: Cluster leadership acquired
INFO[0020] Registered Engine us1 at {{IP Redacted}}:2375
ERRO[0663] Get http://{{IP Redacted}}:2375/v1.15/info: dial tcp {{IP Redacted}}:2375: connection refused
INFO[46680] Registered Engine docker-node-1 at {{IP Redacted}}:2375
INFO[0000] Listening for HTTP                            addr=<IP_ADDRESS>:3375 proto=tcp
INFO[0000] Leader Election: Cluster leadership lost
INFO[0000] Registered Engine us1 at {{IP Redacted}}:2375
INFO[0000] Registered Engine docker-node-1 at {{IP Redacted}}:2375
ERRO[0003] HTTP error: No elected primary cluster manager  status=500
ERRO[0009] HTTP error: No elected primary cluster manager  status=500
INFO[0014] Leader Election: Cluster leadership acquired
etcd logs:
[etcd] Dec 11 06:16:31.005 WARNING   | Using the directory f164b7a508cc.etcd as the etcd curation directory because a directory was not specified.
[etcd] Dec 11 06:16:31.006 INFO      | f164b7a508cc is starting a new cluster
[etcd] Dec 11 06:16:31.009 INFO      | etcd server [name f164b7a508cc, listen on :4001, advertised url http://{{{{IP Redacted}}}}:4001]
[etcd] Dec 11 06:16:31.009 INFO      | peer server [name f164b7a508cc, listen on :7001, advertised url http://{{IP Redacted}}:7001]
[etcd] Dec 11 06:16:31.010 INFO      | f164b7a508cc starting in peer mode
[etcd] Dec 11 06:16:31.010 INFO      | f164b7a508cc: state changed from 'initialized' to 'follower'.
[etcd] Dec 11 06:16:31.010 INFO      | f164b7a508cc: state changed from 'follower' to 'leader'.
[etcd] Dec 11 06:16:31.010 INFO      | f164b7a508cc: leader changed from '' to 'f164b7a508cc'.
[etcd] Dec 11 07:29:13.600 INFO      | f164b7a508cc: snapshot of 10003 events at index 10003 completed
[etcd] Dec 11 08:41:44.094 INFO      | f164b7a508cc: snapshot of 10006 events at index 20009 completed
[etcd] Dec 11 09:54:14.596 INFO      | f164b7a508cc: snapshot of 10006 events at index 30015 completed
[etcd] Dec 11 11:06:45.089 INFO      | f164b7a508cc: snapshot of 10006 events at index 40021 completed
[etcd] Dec 11 12:19:15.583 INFO      | f164b7a508cc: snapshot of 10005 events at index 50026 completed
[etcd] Dec 11 13:31:46.083 INFO      | f164b7a508cc: snapshot of 10007 events at index 60033 completed
[etcd] Dec 11 14:44:16.590 INFO      | f164b7a508cc: snapshot of 10005 events at index 70038 completed
[etcd] Dec 11 15:56:47.097 INFO      | f164b7a508cc: snapshot of 10006 events at index 80044 completed
[etcd] Dec 11 17:08:44.591 INFO      | f164b7a508cc: snapshot of 10008 events at index 90052 completed
[etcd] Dec 11 18:18:15.076 INFO      | f164b7a508cc: snapshot of 10009 events at index 100061 completed
[etcd] Dec 11 19:27:48.577 INFO      | f164b7a508cc: snapshot of 10008 events at index 110069 completed
[etcd] Dec 11 20:37:16.093 INFO      | f164b7a508cc: snapshot of 10001 events at index 120070 completed
[etcd] Dec 11 21:46:46.586 INFO      | f164b7a508cc: snapshot of 10007 events at index 130077 completed
[etcd] Dec 11 22:56:14.077 INFO      | f164b7a508cc: snapshot of 10002 events at index 140079 completed
[etcd] Dec 12 00:05:41.584 INFO      | f164b7a508cc: snapshot of 10001 events at index 150080 completed
[etcd] Dec 12 01:15:12.079 INFO      | f164b7a508cc: snapshot of 10009 events at index 160089 completed
[etcd] Dec 12 02:24:39.570 INFO      | f164b7a508cc: snapshot of 10001 events at index 170090 completed
[etcd] Dec 12 03:34:10.059 INFO      | f164b7a508cc: snapshot of 10007 events at index 180097 completed
[etcd] Dec 12 04:43:37.547 INFO      | f164b7a508cc: snapshot of 10002 events at index 190099 completed
[etcd] Dec 12 05:53:05.032 INFO      | f164b7a508cc: snapshot of 10001 events at index 200100 completed
[etcd] Dec 12 07:02:35.526 INFO      | f164b7a508cc: snapshot of 10009 events at index 210109 completed
[etcd] Dec 12 08:12:03.010 INFO      | f164b7a508cc: snapshot of 10002 events at index 220111 completed
[etcd] Dec 12 09:21:30.487 INFO      | f164b7a508cc: snapshot of 10001 events at index 230112 completed
[etcd] Dec 12 10:31:00.969 INFO      | f164b7a508cc: snapshot of 10009 events at index 240121 completed
[etcd] Dec 12 11:40:31.446 INFO      | f164b7a508cc: snapshot of 10007 events at index 250128 completed
[etcd] Dec 12 12:50:01.923 INFO      | f164b7a508cc: snapshot of 10007 events at index 260135 completed
[etcd] Dec 12 13:59:29.408 INFO      | f164b7a508cc: snapshot of 10003 events at index 270138 completed
[etcd] Dec 12 15:08:59.893 INFO      | f164b7a508cc: snapshot of 10007 events at index 280145 completed
[etcd] Dec 12 16:18:27.387 INFO      | f164b7a508cc: snapshot of 10002 events at index 290147 completed
[etcd] Dec 12 17:27:54.872 INFO      | f164b7a508cc: snapshot of 10001 events at index 300148 completed
[etcd] Dec 12 18:37:25.357 INFO      | f164b7a508cc: snapshot of 10007 events at index 310155 completed
[etcd] Dec 12 19:46:52.837 INFO      | f164b7a508cc: snapshot of 10002 events at index 320157 completed
[etcd] Dec 12 20:56:20.325 INFO      | f164b7a508cc: snapshot of 10001 events at index 330158 completed
[etcd] Dec 12 22:05:50.823 INFO      | f164b7a508cc: snapshot of 10007 events at index 340165 completed
[etcd] Dec 12 23:15:18.311 INFO      | f164b7a508cc: snapshot of 10002 events at index 350167 completed
[etcd] Dec 13 00:24:45.805 INFO      | f164b7a508cc: snapshot of 10001 events at index 360168 completed
[etcd] Dec 13 01:34:16.292 INFO      | f164b7a508cc: snapshot of 10009 events at index 370177 completed
[etcd] Dec 13 02:43:46.769 INFO      | f164b7a508cc: snapshot of 10009 events at index 380186 completed
[etcd] Dec 13 03:53:20.286 INFO      | f164b7a508cc: snapshot of 10005 events at index 390191 completed
[etcd] Dec 13 05:02:50.774 INFO      | f164b7a508cc: snapshot of 10007 events at index 400198 completed
[etcd] Dec 13 06:12:21.262 INFO      | f164b7a508cc: snapshot of 10009 events at index 410207 completed
—
Reply to this email directly or view it on GitHub
https://github.com/shipyard/shipyard/issues/644#issuecomment-164223403.

any idea when that would be? Thanks :+1:
also as a side note i'm getting this on chrome as well... is this a known issue?
TypeError: Cannot read property 'Names' of null
    at shortestContainerName (containers.controller.js:288)
    at ContainersController.containerName (containers.controller.js:278)
    at angular.js:12474
    at Object.<anonymous> (angular.js:12883)
    at n.$digest (angular.js:14404)
    at n.$apply (angular.js:14675)
    at l (angular.js:9725)
    at F (angular.js:9915)
    at XMLHttpRequest.C.onload (angular.js:9856)

Not sure on the HA deploy.  Contributions welcome :)
That looks like you are on an older version of Swarm or the Engine perhaps.
On Sat, Dec 12, 2015 at 11:58 PM, ephemeraleclipse<EMAIL_ADDRESS>
wrote:

any idea when that would be? Thanks [image: :+1:]
also as a side note i'm getting this on chrome as well... is this a known
issue?
TypeError: Cannot read property 'Names' of null
at shortestContainerName (containers.controller.js:288)
at ContainersController.containerName (containers.controller.js:278)
at angular.js:12474
at Object. (angular.js:12883)
at n.$digest (angular.js:14404)
at n.$apply (angular.js:14675)
at l (angular.js:9725)
at F (angular.js:9915)
at XMLHttpRequest.C.onload (angular.js:9856)
—
Reply to this email directly or view it on GitHub
https://github.com/shipyard/shipyard/issues/644#issuecomment-164223478.

hmm... okay... thanks :)

I got the same issue yesterday. Looks like it might be related to Swarm Manager leader election.
If the master's swarm manager shuts down or restarts for some reason, one of the nodes will be elected as the "primary cluster manager" (awesome failover!). The problem is.. that either all managers or the shipyard controller needs to communicate with the newly elected leader.. on port 3375 which is not exposed from the manager container to the host and between hosts.
@ehazlett please add me as a contributor so I can open a pull request
I've changed the deployment script on the starm_swarm_manager function, adding
-p $SWARM_PORT:$SWARM_PORT \
start_swarm_manager() {
get_ip
TLS_OPTS=""
if [ $ENABLE_TLS = 1 ]; then
    TLS_OPTS="--tlsverify --tlscacert=$SSL_CA_CERT --tlscert=$SSL_CERT --tlskey=$SSL_KEY"
fi

EXTRA_RUN_OPTS=""

if [ -z "$DISCOVERY" ]; then
    DISCOVERY="$DISCOVERY_BACKEND://discovery:$DISCOVERY_PORT"
    EXTRA_RUN_OPTS="--link $PREFIX-discovery:discovery"
fi
ID=$(docker run \
    -ti \
    -d \
    -p $SWARM_PORT:$SWARM_PORT \
    --restart=always \
    --name $PREFIX-swarm-manager \
    --volumes-from=$PREFIX-certs $EXTRA_RUN_OPTS \
    swarm:1.1.2 \
    m --replication --addr $SHIPYARD_IP:$SWARM_PORT --host tcp://<IP_ADDRESS>:$SWARM_PORT $TLS_OPTS $DISCOVERY)

}
I simulated it with manually restarting the master's swarm manager container... and then I got 504 from the controller for a minute or two.. and then everything went back live.