MITObim

Hi Christoph,
I am trying to reconstruct mitochondrial genomes from IonTorrent NGS data and as I have a reference genome from to the same species I thought of using the --quick approach (output message below). Apparently, my readpool does not contain any reads with reasonable match (kmer=31), which is quite surprising considering that I’m using a reference genome of the same species.
Then, I decided to run the two-step approach and after successfully mapping assembly with MIRA 4, I tried to run MITObim and got the below error message saying that miraconvert seems to have failed - see detailed output below. Any idea how to move forward?
Many thanks,
Regina L. Cunha
--quick option:
MITObim - mitochondrial baiting and iterative mapping
version 1.8
author: Christoph Hahn, (c) 2012-2016
quick option selected! -maf option will be ignored (if given)
./MITObim_1.8.pl -start 1 -end 30 -sample testpool -ref perna_mt_genome -readpool /home/regina/mtDNA/BZP.fastq --quick /home/regina/mtDNA/pernamtDNA.fa
All paramters seem to make sense:
startiteration: 0
enditeration: 30
sample: testpool
refname: perna_mt_genome
readpool: /home/regina/mtDNA/BZP.fastq
maf: 0
quick: /home/regina/mtDNA/pernamtDNA.fa
paired: 0 (off=0, on=1)
assembly mode: 0 (mapping=0, denovo=1)
verbose: 0 (off=0, on=1)
split: 0 (off=0, on=1)
minimum avg. coverage: 0 (off=0)
clean: 0 (off=0, on=1)
trim reads: 0 (off=0, on=1)
trim overhang: 0 (no=0, yes=1)
platform: iontorrent
kmer baiting: 31
Starting MITObim
==============
ITERATION 0
Dec  3 13:03:32
quick option baits reads from provided reference in iteration 0
fishing readpool using mirabait (k = 31)
mirabait: No bait files defined via -b and no -L given!
Did you use the command line for the old mirabait (<= 4.0.2)?
your readpool does not contain any reads with reasonable match (k = 31) to your reference - Maybe you want to different settings or even a different reference?
2-step option:
./MITObim_1.8.pl -start 1 -end 30 -sample testpool -ref perna_mt_genome -readpool /home/regina/mtDNA/BZP.fastq -maf /home/regina/mtDNA/initial-mapping-testpool-to-perna-mt_assembly/initial-mapping-testpool-to-perna-mt_d_results/initial-mapping-testpool-to-perna-mt_out.maf
All paramters seem to make sense:
startiteration: 1
enditeration: 30
sample: testpool
refname: perna_mt_genome
readpool: /home/regina/mtDNA/BZP.fastq
maf: /home/regina/mtDNA/initial-mapping-testpool-to-perna-mt_assembly/initial-mapping-testpool-to-perna-mt_d_results/initial-mapping-testpool-to-perna-mt_out.maf
quick: 0
paired: 0 (off=0, on=1)
assembly mode: 0 (mapping=0, denovo=1)
verbose: 0 (off=0, on=1)
split: 0 (off=0, on=1)
minimum avg. coverage: 0 (off=0)
clean: 0 (off=0, on=1)
trim reads: 0 (off=0, on=1)
trim overhang: 0 (no=0, yes=1)
platform: iontorrent
kmer baiting: 31
Starting MITObim
==============
ITERATION 1
Dec  3 13:19:02
recover backbone by running miraconvert on maf file
ConvPro::checkTypes: Unknown or illegal file type 'tmp' defined as
miraconvert	(MIRALIB version 4.9.5_2 )
Author:  Bastien Chevreux<EMAIL_ADDRESS>Purpose: convert assembly and sequencing file types.
Usage: [......]
miraconvert seems to have failed - see detailed output above

The issue has been picked up on the mailing list here and here. Closing this.


check_syntax: WITH HEADER LINE can only be used with internal table

abaplint 2.64.0
Issue:
/tmp/abaplint-NFCmkk/src/kalc/kgaldtyp.prog.abap[335, 1] - WITH HEADER LINE can only be used with internal table (check_syntax)
Source (from original SAP as part of dependency repo)
DATA: fieldtab TYPE rkea1_fieldtab WITH HEADER LINE.

Playground:
REPORT zfoobar.

TYPES: BEGIN OF rkea1_fieldtab_entry.
        INCLUDE STRUCTURE dd03p.
        INCLUDE STRUCTURE cefld.
TYPES: END OF rkea1_fieldtab_entry.

TYPES: rkea1_fieldtab TYPE rkea1_fieldtab_entry OCCURS 150.

DATA: fieldtab TYPE rkea1_fieldtab WITH HEADER LINE.

TYPES tab TYPE i OCCURS 150.
DATA fieldtab TYPE tab WITH HEADER LINE.

TYPES tab TYPE i OCCURS 150.
DATA fieldtab TYPE tab WITH HEADER LINE.

@ed-holland try again, 2.64.1 published

@ed-holland try again, 2.64.1 published

abaplint 2.64.1
Issue is still there in abaplint. It is gone in playground. Also VC does not see the problem.
Source code numbers in deps are different so using vc on the deps-repo.

abaplint 2.64.1
Issue is still there in abaplint. It is gone in playground. Also VC does not see the problem.
Source code numbers in deps are different so using vc on the deps-repo.

Closing as the issue is resolved.


internal: publish

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Codecov Report

Merging #1919 (ce82a40) into master (859d320) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1919   +/-   ##
=======================================
  Coverage   98.54%   98.54%
=======================================
  Files         102      102
  Lines        1922     1922
  Branches      399      399
=======================================
  Hits         1894     1894
  Misses         13       13
  Partials       15       15

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


chore(master): release 1.2.0

:robot: I have created a release beep boop
1.2.0 (2024-01-06)
Features

lunar插件新增获取农历信息方法 (11cc4d2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/lspriv/wx-calendar/releases/tag/v1.2.0 :sunflower:


Error downloading github:jspm/nodelibs-path

jspm install -y result in error:
err  Error downloading github:jspm/nodelibs-path
     Bad response code 406

Errors during npm install
sk-nav/node_modules/gulp-protractor/node_modules/protractor/node_modules/request/node_modules/form-data requires<EMAIL_ADDRESS>but will load  /sk-nav/node_modules/gulp-protractor/node_modules/async, which is version 0.7.0
sk-nav/node_modules/gulp-yuidoc/node_modules/gulp-util/node_modules/dateformat/node_modules/meow requires<EMAIL_ADDRESS>but will load sk-nav/node_modules/gulp-yuidoc/node_modules/gulp-util/node_modules/minimist, which is version 0.2.0
sk-nav/node_modules/gulp-yuidoc/node_modules/yuidocjs/node_modules/express/node_modules/connect requires<EMAIL_ADDRESS>but will load sk-nav/node_modules/gulp-yuidoc/node_modules/yuidocjs/node_modules/express/node_modules/buffer-crc32, which is version 0.2.5
sk-nav/node_modules/karma-6to5-preprocessor/node_modules/6to5-core/node_modules/regenerator-6to5/node_modules/commoner requires<EMAIL_ADDRESS>but will load sk-nav/node_modules/karma-6to5-preprocessor/node_modules/6to5-core/node_modules/commander, which is version 2.6.0

I don't think those are errors. It's just telling you how the semver is resolving. The first was an error, which probably had something to do with github at the time. I woud retry this. Also make sure your node is up tp date.

v0.10.32

Got it. My auth token didn't have public_repo access: https://github.com/jspm/github/commit/fe6af25d9f9d9f05fb73fd873425a05319d7cf51


Implementation detail about detectoRS

hi,
in the implementation of detectors_resnet.py, https://github.com/open-mmlab/mmdetection/blob/3a9f5eff39735871c55643927f5506ab5af2127a/mmdet/models/backbones/detectors_resnet.py#L300,the rfp feature seems not to be added to the first stage of the resnet, can explain the reason? and the paper seems not to mention it ?@joe-siyuan-qiao

We follow the official implementation from here.

We follow the official implementation from here.


Initial GlusterFS support

This only works on Debian, because gluster is neutered in Ubuntu.

There are some elements in this I can tease out into small patches. I'll set this as draft until I do that.

Sorry this is so big, its mostly deployment changes to be honest.


Move render_sky logic from effects into our sky object

When we extracted all the sky logic from the renderer into its own class some logic was still left in effects. Doesn't make a whole lot of sense seeing the shader logic itself was moved into the new class.
This PR just finishes that and does a bit of cleanup around private/public structures.

I broke something in stereoscopic rendering, let me check..

Thanks!


formatting

@previnWong sorry man...know this has lots of files but it's just auto-formatting updates should be no code changes

Are we getting these from CyberTech?  do we need tell them to change their format rules?

@previnWong seems like a good idea to sync up on it. I just haven't done a clean sweep in awhile


Flucca/feat/library assets

Closes #375
No side nav yet, need #464 to be merged in
Design: https://ibm.ent.box.com/file/913340274022
Testing / reviewing
Test all breakpoints against design, make sure linkout works on asset rows, test empty state
https://user-images.githubusercontent.com/40550942/162341860-e04c5109-e9d0-4cca-97c2-29effe26ddde.mov
https://user-images.githubusercontent.com/40550942/162341865-46765bf2-8c93-4df5-b02e-e66d822530b8.mov

Ready for first review.
Missing: clickable row (entire row). needs further discussion, might want to split this into a separate ticket.

@kingtraceyj added some screen records so you can take a look, happy to jump on a huddle/call as well and review!

@francinelucca quickly looking at this made me realize some updates I need to make to #375 to actually wire it up as a working nav

@kingtraceyj addressed comments + added text padding, ready for second review

@kingtraceyj updated lg columns! hang lgtm


Drop: Replace erf_cody with Standard Library's erf

Context:
In the previous performance analysis, I found that the standard library's erf function consistently outperforms custom erf_cody function. The performance tests showed that erf won in 3501 cases, while erf_cody won in 2735 cases. Additionally, the total execution time for erf was less than that for erf_cody (261666 nanoseconds for erf vs 293012 nanoseconds for erf_cody).
Changes:  This Pull Request implements the transition from using our custom erf_cody function to the standard library's erf function. The changes include:

Addition of erf_std.cpp file, which contain the standard erf, erfc, and erfcx functions.
Replacement of all instances of erf_cody, erfc_cody, and erfcx_cody with erf_std, erfc_std, and erfcx_std respectively in the codebase.
drop of erf_cody.cpp file.

Impact:
This refactor is expected to improve the performance of our code and reduce the maintenance overhead of our custom implementation. It will also make our code more standard and easier to understand for developers familiar with the C++ standard library.
Tests:
All test n confirmation of correct implementation we can find here: https://github.com/hayden4r4/blackscholes-rust/pull/6

this is awesome, really appreciate you digging into this.  I love increasing the performance without overly complicating the code, so this is right on target.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2455

Questions ?
Please refer to the Backport tool documentation


Re-worked to use a better and simpler way to do the backup of a datab…

…ase which defines the backup location, even if that is on a remote server
Re-worked the backing up of a database.  Uses a SQL script to perform the backup.  Uses a SQL command to create the backup folder locally, or on a remote server.  Updated unit tests.

Fixes #6


layout problems on microprofile.io

Maybe you know from this discussion (and here) about the layout on the microprofile.io homepage.

I think we could solve this by simply replacing the inline code fragments in the readme.adoc file like this:
...level is the `HealthCheck` interface.....

with italic style:
...level is the _HealthCheck_ interface.....

Should I create a pull request with those changes or did you already plan to fix this otherwise?

hi @rsoika, I don't think anyone has this already in progress. Please go ahead and create a PR. Thank you.


Updated the analyze.dart deprecation check to only look for beta branch versions.

The current analyzer bot script looks for dev versions in the deprecated warnings. As we no longer have dev releases this PR updates the check to only look for beta version numbers (i.e. vX.X.X).
This also cleans up some lint warnings for some of the regexp raw strings.
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[ ] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

Adding @gspencergoog for Regex readability

I'm still trying to understand this change, but from the PR description, I'm not sure this is the right change to make. Requesting changes for the moment while I do a more thorough review...


2.0 Reference Models: BERT (1 GPU, 8 GPU with dist strat and Keras)

BERT, or Bidirectional Encoder Representations from Transformers, is a new method of pre-training language representations which obtains state-of-the-art results on a wide array of Natural Language Processing (NLP) tasks.
The research team's academic paper describes BERT in detail and provides full results on a number of tasks: https://arxiv.org/abs/1810.04805.
An example of using BERT can be found here.
The purpose of this issue is to migrate models into the TF 2.0 Keras API. Each migrated model must be eager and distribution compatible, with tests, and all associated engineering artifacts.

I am interested on working on this issue.

@dynamicwebpaige Do I open a PR in models?

We are working on this internally and will publish the code before the end of May-2019 assigning to me for now.

https://github.com/tensorflow/models/tree/master/official/bert
The README has not been updated yet, but I think the information below will get you started.
I am only testing the GPU version but it was build for TPU so that would have been tested first.  I do not have the flags to use but I have the test cases we run nightly.  Below is what I know, I have not been going even a little deep into BERT so I don't know how to state the accuracy numbers other than what we are tracking nightly.
BERT (SQUAD):  ~.903
BERT (Classify):  .8603 with mrpc

Test Case SQUAD: official.bert.benchmark.bert_squad_benchmark.BertSquadBenchmarkReal.benchmark_8_gpu
Test Case Classify: official.bert.benchmark.bert_benchmark.BertClassifyAccuracy.benchmark_8_gpu_mrpc

I realize it is a bit painful but you can extract the FLAGS from the tests above. We are still working on performance but we are already exceeding the TF 1.0 for both single and multi-gpu single machine.  FP16 support will be coming soon.  We are working on SQUAD first but the gains would apply to both...in most instances.
Warning: The data in gs://cloud-tpu-checkpoints is public and you can pull that down.  I did not make the actual training data public because I have not taken time to find out if it can be shared directly.  It likely can, but I like to be careful.
I will help if I can; another group owns this but I deal with it daily as well for now.


feat(server-portal): unregister past service workers with script injection

This approach is wrong and it doesn't work. Closing the PR.


Issue 02. Same Style sheet is included in head tag twice

Description: In the head tag. two style tags are created and contexts are the same.

Issue 02 has been resolved


[Bug] IndexError: index 0 is out of bounds for dimension 0 with size 0

In the retrosynthesis tutorial
from torchdrug.utils import plot

for i in range(2):
    sample = reaction_dataset[i]
    reactant, product = sample["graph"]
    reactants = reactant.connected_components()[0]
    products = product.connected_components()[0]
    plot.reaction(reactants, products)

gives below error
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
Input In [14], in <cell line: 5>()
      8 reactants = reactant.connected_components()[0]
      9 products = product.connected_components()[0]
---> 10 plot.reaction(reactants, products)

File /usr/local/lib/python3.9/dist-packages/torchdrug/utils/plot.py:26, in reaction(reactants, products, save_file, figure_size, atom_map)
     14 """
     15 Visualize a chemical reaction.
     16
   (...)
     23     atom_map (bool, optional): visualize atom mapping or not
     24 """
     25 rxn = AllChem.ChemicalReaction()
---> 26 for reactant in reactants:
     27     mol = reactant.to_molecule()
     28     if not atom_map:

File /usr/local/lib/python3.9/dist-packages/torchdrug/data/graph.py:1159, in PackedGraph.__next__(self)
   1157 def __next__(self):
   1158     if self._iter_index < self.batch_size:
-> 1159         item = self[self._iter_index]
   1160         self._iter_index += 1
   1161         return item

File /usr/local/lib/python3.9/dist-packages/torchdrug/data/graph.py:1458, in PackedGraph.__getitem__(self, index)
   1455     index = (index,)
   1457 if isinstance(index[0], int):
-> 1458     item = self.get_item(index[0])
   1459     if len(index) > 1:
   1460         item = item[index[1:]]

File /usr/local/lib/python3.9/dist-packages/torchdrug/data/graph.py:1378, in PackedGraph.get_item(self, index)
   1376 edge_list = self.edge_list[edge_index].clone()
   1377 edge_list[:, :2] -= self._offsets[edge_index].unsqueeze(-1)
-> 1378 data_dict, meta_dict = self.data_mask(node_index, edge_index, graph_index=graph_index)
   1380 return self.unpacked_type(edge_list, edge_weight=self.edge_weight[edge_index], num_node=self.num_nodes[index],
   1381                           num_relation=self.num_relation, meta_dict=meta_dict, **data_dict)

File /usr/local/lib/python3.9/dist-packages/torchdrug/data/graph.py:1433, in PackedGraph.data_mask(self, node_index, edge_index, graph_index, include, exclude)
   1431     v = v[edge_index]
   1432 elif type == "graph" and graph_index is not None:
-> 1433     v = v[graph_index]
   1434 elif type == "node reference" and node_index is not None:
   1435     if node_mapping is None:

IndexError: index 0 is out of bounds for dimension 0 with size 0

Hi! Thanks for pointing out this issue. This bug is caused by a typo in the commit https://github.com/DeepGraphLearning/torchdrug/commit/f8d2de6fc91c1ff60a62b0279d61d1be8e1638ff, which slightly modified the data.Graph.split() method. I've fixed this typo in the commit https://github.com/DeepGraphLearning/torchdrug/commit/5e07dd36b6f7b58532315cbd99fd2e015d12d808 and it should work now.

Thanks, @KiddoZhu,
This issue is resolved with the latest commit


Remove spurious init variables

When you execute
In [1]: import human_readable_project_name as he
In [2]: help(he)
The help page would previously show version_file and version_filename
in the DATA section. Deleting these variables after use fixes that
problem.
Is this the right way to fix the problem?

I do not know.

I think this is fine for now :+1:

I am sorry for the bike shedding. I want to get to the bottom of this. Apparently, there are 7 common version resolution methods.
Of those methods, I like number 3 the most. An example can be found here.
It removes the need for a manifest.in file and does not require spurious variables in the init.py.
What do you think?

I still like 4 better -- it is very similar to 3, can be used in other tools as well, and personally I like that the versioning is not coupled with the code.

Thanks for looking into this Allard! I like 3 best since it avoids MANIFEST.in and our template is for a pure Python library anyway.

I changed the code to use a private function and am merging. The differences are marginal anyway.

I'm fine either way.


perfcollect pid filter produces empty dump in PerfView

# perfcollect collect sample-pid-threadtime -collectsec 10 -threadtime -pid 1
Collection started. Collection will automatically stop in 10 second(s). Press CTRL+C to stop early.

...STOPPED.

Starting post-processing. This may take some time.

Warning:
Processed 2682678 events and lost 89 chunks!

Check IO/CPU overload!

Generating native image symbol files
...FINISHED
Saving native symbols
Warning:
Processed 2682678 events and lost 89 chunks!

Check IO/CPU overload!

...FINISHED
Resolving JIT and R2R symbols
...FINISHED
Exporting perf.data file
...FINISHED
Compressing trace files
...FINISHED
Cleaning up artifacts
...FINISHED

Trace saved to sample-pid-threadtime.trace.zip

This produced a 173 MB zip file, but opening up in PerfView only shows the CPU Stack option with no content (only ROOT entry in By Name)
Ubuntu 18.04.6
perf version 4.15.18
lttng (LTTng Trace Control) 2.10.2 - KeKriek
dotnet 6.0.201
PerfView 3.03

Since the PID is 1, I'm wondering if you're running this inside a container.  That may have something to do with this.  Can you tell me more about the environment?  I also suspect that -pid and -threadtime aren't going to work well together since you are going to need sched_switch events from other processes to get a complete picture.

Yes, it is inside a container built on top of ubuntu bionic.

This text means that there were lost events during the trace, which does make the capture suspect:
Warning:
Processed 2682678 events and lost 89 chunks!

Check IO/CPU overload!

That said, I would have expected to see something in the trace, unless this resulted in some corruption.  Are you able to share the trace file?

This was done in a production container so I unfortunately cannot share the trace file but I will try to reproduce the issue in a generic container and get back to you.

I noticed an error in perfcollect.log on the dumps with -pid that is not present in the ones without -pid
Running /usr/bin/perf script -i perf-jit.data -F comm,pid,tid,cpu,time,period,event,ip,sym,dso,trace > perf.data.txt
'trace' not valid for hardware events. Ignoring.
'trace' not valid for software events. Ignoring.
'trace' not valid for unknown events. Ignoring.
'trace' not valid for unknown events. Ignoring.
'trace' not valid for unknown events. Ignoring.
Samples for 'cpu-clock' event do not have CPU attribute set. Cannot print 'cpu' field.

Running /usr/bin/perf script -i perf-jit.data -f comm,pid,tid,cpu,time,event,ip,sym,dso,trace > perf.data.txt
  Error: Couldn't find script `comm,pid,tid,cpu,time,event,ip,sym,dso,trace'

Could this be the cause for the empty results in PerfView?

Probably related to https://github.com/dotnet/corefx-tools/issues/92 and https://github.com/dotnet/corefx-tools/issues/84

Yes, it could.  Can you try capturing with this private copy of perfcollect and see if that solves the problem?
https://raw.githubusercontent.com/microsoft/perfview/04663ba0aa85c90e832f1e5a2ecb2fef972f2796/src/perfcollect/perfcollect

I suspect that these are two different issues.  The hang is likely just the fact that there is a lot of code being used in the app.  The more managed code that you use, the larger the "injection" phase will take, which is what occurs during Resolving JIT and R2R Symbols.  The failures that you're seeing are due to a having to try different command lines.  Are you still seeing nothing when you open the CPU stacks in PerfView?  If so, would it be possible for you to share the dockerfile that describes the setup that you're using for the hello world app?  I can try it out for myself and debug as necessary.


Deepspeed + SWA results in no optimizers

🐛 Bug
When using deepspeed_stage_2 with stochastic_weight_avg the configure_optimizers is not called resulting in the training thinking it has no optimizers
If I uncomment # stochastic_weight_avg="true", then I get the following error:
pytorch_lightning.utilities.exceptions.MisconfigurationException: SWA currently works with 1 optimizer.

To Reproduce

    import os
    import torch
    from torch import nn
    import torch.nn.functional as F
    from torchvision import transforms
    from torchvision.datasets import MNIST
    from torch.utils.data import DataLoader
    import pytorch_lightning as pl

    class LitAutoEncoder(pl.LightningModule):
      def __init__(self):
          super().__init__()
          self.encoder = nn.Sequential(nn.Linear(28 * 28, 64), nn.ReLU(), nn.Linear(64, 3))
          self.decoder = nn.Sequential(nn.Linear(3, 64), nn.ReLU(), nn.Linear(64, 28 * 28))

      def forward(self, x):
          # in lightning, forward defines the prediction/inference actions
          embedding = self.encoder(x)
          return embedding

      def training_step(self, batch, batch_idx):
          # training_step defined the train loop.
          # It is independent of forward
          x, y = batch
          x = x.view(x.size(0), -1)
          z = self.encoder(x)
          x_hat = self.decoder(z)
          loss = F.mse_loss(x_hat, x)
          # Logging to TensorBoard by default
          self.log("train_loss", loss)
          return loss

      def configure_optimizers(self):
          optimizer = torch.optim.Adam(self.parameters(), lr=1e-3)
          return optimizer

    trainer = pl.Trainer(
        gpus=1,
        precision=16,
        accelerator="gpu",
        strategy="deepspeed_stage_2",
        amp_backend="native",
        # stochastic_weight_avg="true",
    )

    dataset = MNIST(os.getcwd(), download=True, transform=transforms.ToTensor())
    train_loader = DataLoader(dataset)

    trainer.fit(LitAutoEncoder(), train_loader)

Expected behavior
Should be able to use deepspeed_stage_2 and SWA unless there is a fundamental reason this shouldn't be done.
Environment

CUDA:
- GPU:
- Tesla T4
- available:         True
- version:           11.3
Packages:
- numpy:             1.21.3
- pyTorch_debug:     False
- pyTorch_version:   1.10.0+cu113
- pytorch-lightning: 1.5.2
- tqdm:              4.62.3
System:
- OS:                Linux
- architecture:
- 64bit
- ELF
- processor:         x86_64
- python:            3.9.9
- version:           #61~18.04.1-Ubuntu SMP Thu Oct 28 04:16:28 UTC 2021

Additional context

cc @tchaton @SeanNaren @awaelchli @carmocca

Closing this old issue. DeepSpeed is not supported with this callback: https://github.com/Lightning-AI/lightning/blob/c21b6de3c732af85414060dc3a643801d89ba71b/src/lightning/pytorch/callbacks/stochastic_weight_avg.py#L143-L144


Enhance Continious Integration Process.

Currently, we are using only CI Eclipse infrastructure (jenkins) :  https://ci.eclipse.org/leshan/.
It allow us to :

build master to automatically deploy leshan sandbox.
build and release master and 1.x branch to deploy nightly build on eclipse repo. (more details)
release stable and milestone release on  maven central.

This is good but we also need some CI to do some automatic check on PR.
We should probably do that using Github Actions.
First step will probably be to check for each PR on master if :

code compile
unit tests are :heavy_check_mark:
integration tests are :heavy_check_mark:

Then next steps should be :

check code format.
check organize import ?
check PR does not contain merge commit.

And maybe more ? :thinking:

Here a very simple way for build + tests at : https://github.com/sbernard31/leshan/pull/2

Some idea about organize import : https://github.com/sbernard31/leshan/pull/4

See how to check that PR does not contains "merge commit" : https://github.com/sbernard31/leshan/pull/5

A better way to add build + tests using :

composite actions
add comment in case of error.

See https://github.com/sbernard31/leshan/pull/7

We could eventually use sortpom to ensure pom.xml are well formatted.
But it seems that java 11 is required. (https://github.com/Ekryd/sortpom/issues/225)

@adamsero, @JaroslawLegierski, I currently added this kind of tools to help new user to provide better PR.
The goal is to detect issues but also to provide some documentation to solve it.
I would really appreciate that you help me about this, providing feedback about that when you push PR.
(e.g. if documentation is not  clear enough or how we could enhance it, etc etc ...)

Some more improvement with :

https://github.com/eclipse/leshan/pull/1271
https://github.com/eclipse/leshan/pull/1276

I don't plan to add more at short term.
Maybe later with more checkstyle rules or code analysis tools.


[BUG] Tooltip labels for equal data not combining using mode: nearest

Expected Behavior
When hovering over two lines with equivalent data points, I would expect to see a tooltip with labels for both data points.
Current Behavior
When hovering over two lines with equivalent data points, the tooltip data does not combine. Rather, each individual tooltip "flashes" repeatedly one after the other.
Possible Solution
I would assume this would be an issue with the nearest method under Chart.Tooltip.positioners ?
Though there is also a getNearestItems function in core.interaction.js that might be worth checking out as well (side note: there is a typo in the getNearestItems comment, "teh" -> "the" 😄 )
Steps to Reproduce (for bugs)
From: http://www.chartjs.org/samples/latest/tooltips/interactions.html

Context
This doesn't impact me directly, but I could see it being an issue.
Environment

Chart.js version: Latest (2.7.2)
Browser name and version: Latest Chrome (65), Latest Firefox (59), Latest Safari (11)

@simonbrunel how do you feel about this?


Add HYR-SENSE

Insert URLs to the project here: https://github.com/CU-ESIIL/HYR-SENSE

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All projects listed will be posted on our Mastodon channel

@CibeleAmaral @serbinsh @ttuff


Adding "export log" feature

There have been several cases, when the app crashed while my phone wasn't connected to ADB console. As for now, there seem to be no opportunity to export logs after the crash from app functionality. What do you think about creating log export feature?
Android: 5.1.1
App version: 3.2.3

Could be a nice idea. Can you document how you would implement this ?

I've seen this feature in Android Mapillary app, its authors creates a button "Send debug info", which exports the whole app log, including debug and warning.
This schema was inconvenient because this button showed logs from app install (1 year old logs were excess).
In my humble opinion, it could look like that:

Writing app logs to some file using  logback or log4j library (stackoverflow example)
Cleaning this file on app startup once a day/week (to prevent this file from being too large), but not on every app startup (user may restart app after crash)
Placing the TextView about log file location or 'export log' Button somewhere in settings menu.
Adding Log.error (error_message); to the most sufficient Activity and database Exception handlers.


Address missing bean defining annotations in Lite portion of tests

With the non-Lite tests moved under the full package and labelled with the cdi-full test group, the Weld jboss-tck-runner emedded tests show the following failure count due to missing bean defining annotations:
[ERROR] Tests run: 1423, Failures: 385, Errors: 0, Skipped: 245
The next step in #273 is to add the missing bean defining annotations to obtain a clean run of the core tests under Weld.

@starksm64 I was planning on doing this once your PR was merged. If you want, I can take it over.

@manovotn sure, go ahead. I am currently working on #290 as I saw several decorator related tests using the Decorated qualifier that were not moved to cdi-full. I'm half way through that, so a PR will be coming shortly so you can avoid updating those tests.

Alright, I will start working on this tomorrow :)

@manovotn with the latest changes it looks like we are down to 95 errors with Weld on core tests:
[ERROR] Tests run: 1274, Failures: 95, Errors: 0, Skipped: 79
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:09 min
[INFO] Finished at: 2021-09-23T06:42:51-05:00
[INFO] ------------------------------------------------------------------------

You mentioned being off at some point this week, so just assign this issue to me if you don't finish before you leave.

@starksm64 yea, I have covered most at this point and I plan on finishing that today or tomorrow :-)
BTW I will be off next Tue through Fri.


Display attributes of a component in the sidebar

What problem does this feature solve?
Right now there is no way to see all the attributes passed to a component. In some cases it could be useful to see the values of $attrs in the sidebar, especially for functional components.
Additionally it would be nice to have an option to show the attributes in the component tree - this may get messy in some cases, so this would need to be opt-in via settings.
Reason for this feature request: Once #732 is merged we are one step closer to bringing VueDevtools into the NativeScript-Vue toolchain. In the upcoming 2.0 release of NativeScript-Vue we wrapped all elements into functional components, to be able to see them in VueDevtools, these elements can have attrivutes and it would help debug if we could see the values.
Example:
<ActionBar class="action-bar" title="Hello world"/>

(which is a component where we don't want to create props for every property) currently renders like so

it would be nice to see title: "Hello world" and class: "action-bar" in the component inspector
If this is something that would be considered, I'm willing to submit a PR with the changes.
What does the proposed API look like?
N/A

especially for functional components

but functional components are not displayed in components panel 😕

@sqal https://github.com/vuejs/vue-devtools/pull/719 :)


How to enable log

seems log middleware is not available yet.

@swuecho Following the CORS implementation, the way I do it in our system is to have something like this(while using zio-logging as the logging library):
object Log {
  def apply[R <: Logging, E](httpApp: HttpApp[R, E]): HttpApp[R, E] = Http.flatten {
    Http.fromEffectFunction[Request] { request =>
      for {
        _ <- log.info("some message")
      } yield
        httpApp.mapM { response =>
          for {
            _ <- response match {
              case response: Response.HttpResponse[R, E] => log.info(s"some other message about ${response.status}")
              case _ => ZIO.unit
            }
          } yield response
        }
    }
  }
}

But I agree that it would be better to have something built-in from the library, as it can take a while for some new comer to figure this out. Maybe we need some APIs to help user to build middleware in an easier way.


LLMSHERPA API LOCAL HOSTING

Hey everyone, I have a problem with the locally hosted llmsherpa api, I've followed every step on https://github.com/nlmatics/nlm-ingestor but still can't get my documents chunked once I'm connected to the endpoint, idk what's the issue

Is it a scanned pdf? If yes, you might wanna use the OCR option (add &applyOcr=yes in the api url).

The pdfs I tried parsing are not scanned but I tried adding the '&applyOcr=yes' and still haven't got the chunks/sections of the document, here's what I got in my cmd once I've tried adding the '&applyOcr=yes' in the api url :

Are you hosting the backend with the apache tikka server manually or use the docker image?


[e2e]: container tag branch1 default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v27.0.387
Run: https://github.com/slsa-framework/example-package/actions/runs/8364993174
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.tag.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.tag.branch1.default.slsa3.yml
Trigger: push
Branch: v27.0.387
Date: Wed Mar 20 19:56:11 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v27.0.388
Run: https://github.com/slsa-framework/example-package/actions/runs/8365356987
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.tag.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.tag.branch1.default.slsa3.yml
Trigger: push
Branch: v27.0.388
Date: Wed Mar 20 20:24:29 UTC 2024
Tests are passing now. Closing this issue.


Ability to loop over enums

Would be great if you could loop over an enum at get each single enum value.
Test :: enum {
     test1,
     test2,
     test3,
}

main :: proc() {
    for t in Test {
       // t == Test.test1/Test.test2/Test.3
    }
}

I've added it. How's this?
main :: proc() {
	Test :: enum {
		test1,
		test2,
		test3,
	}

	for t, i in Test {
		fmt.println(t, i, Test.names[i]);
	}
	/*
	test1 0 test1
	test2 1 test2
	test3 2 test3
	*/
}


Making snapshot with a present software keyboard?

I understand that this library doesn't snapshot the whole simulator window, so probably it would be hard to include the software keyboard on a snapshot, but I'm wondering if it would still be possible somehow, even with some effort?
The use case is that we have a view contained in a scroll view, where a text input field should scroll up to stay visible when a software keyboard is present. Currently, I'm not sure if this is possible to test with SnapshotTesting, could anyone give any pointers or ideas on what's the best way to implement this?

Hi @MaxDesiatov, I think you could take a look at this episode https://www.pointfree.co/episodes/ep86-swiftui-snapshot-testing#t657 I'm not sure, but with UIWindow it might be possible to get a keyboard on a snapshot.

@MaxDesiatov This is definitely a neat idea and we'd definitely take a PR that implements it! We're doing some spring cleaning on the issues board, though, and want to keep it focused on bugs over feature requests, so I'm going to close this for now and tag it with "enhancement."


OneLine initializer cant find CurrentInspector in 2019.2a

After upgrading to 2019.2a OneLine initializer fails with "OneLine can not initialize Inspector Window Utility.
You may experience some performance issues.
Please create an issue on https://github.com/slavniyteo/one-line/ and we will repair it."
The problem is that on the Initialize() call the currentInspector window is trying to be reflected and stored in the "window" variable. Unity seems to have removed the "s_CurrentInspectorWindow" field from InspectorWindow.
OneLine still manages to work though so the only problem is performance wise probably.

Thank you for reporting, I'll look at it tomorrow
сб, 30 марта 2019, 19:06 Efe Burak<EMAIL_ADDRESS>
After upgrading to 2019.2a OneLine initializer fails with "OneLine can not
initialize Inspector Window Utility.
You may experience some performance issues.
Please create an issue on https://github.com/slavniyteo/one-line/ and we
will repair it."
The problem is that on the Initialize() call the currentInspector window
is trying to be reflected and stored in the "window" variable. Unity seems
to have removed the "s_CurrentInspectorWindow" field from InspectorWindow.
OneLine still manages to work though so the only problem is performance
wise probably.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/slavniyteo/one-line/issues/34, or mute the thread
https://github.com/notifications/unsubscribe-auth/ARxmNu-BropsP8VX0HzCCPSFhbzhuC3vks5vb4ttgaJpZM4cT0Un
.

As you said, the problem is that they`ve removed internal property InspectorWindow.s_CurrentInspectorWindow.
Anyway, it doesn't affect OneLine functionality except it brokes culling optimization (do not draw properties which aren't visible on the window). And you'll leak it only if you manage really big scriptable objects  with thousands lines.
Unfortunately I don't work with Unity right now. But whey they release 2019.2 and publish Unity's source  code, I'll try to repair this optimization.
I keep this issue open in order to repair this functionality in the future.

To disable the error message, go to Window/OneLineSettings and switch off the Culling column (the second from the right).

Closed with #v0.5.2

Closed with #v0.5.2


Fix wrong num of user repos because of duplicated click delete button & performance optimization

fix #1078

LGTM

LGTM +1 for improving the removal of issues


Y Quantities go into graph when multiple

@olehkorkh-planeks could you please fix what is described in the image such that the Y Quantities do not go into the graph. Thanks.

@antoinefalisse Check the fix - https://github.com/stanfordnmbl/opencap-viewer/pull/237


Files consistently not uploading; "Upload Failed" message

Using SpeechDrop for COVID Debate, whenever we upload a document, the doc doesn't upload (shows a "upload failed" message) about 60% of the time.

@harleyglayzer I can't seem to repro this, tried with a bunch of different files etc. Is this still happening?


Not allowing negative target speeds

Description

Current situation: Vehicle does not move when negative target speeds are used.
Throws an exception for vehicle controllers npc_vehicle_control and vehicle_longitudinal_control when it encounters a negative target speed.
Using simple_vehicle_control allows for negative speeds, and the vehicle will reverse as expected.
Fixes #399
Where has this been tested?

Platform(s): Ubuntu 18.04
Python version(s): 2.7
Unreal Engine version(s): 4.24
CARLA version: <IP_ADDRESS>

Possible Drawbacks

This change is

Thanks for the idea, I'm using a slightly different approach, which is to directly check the sign before applying the throttle.


Fixed: import third-party packages after updating library path

Import this tcex package after the library paths are updated so it can properly find the package.
Fixed this error when running the custom app based on this template:
Traceback (most recent call last):
  File "/opt/python3.6.15/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/opt/python3.6.15/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "./__main__.py", line 3, in <module>
    from run import run
  File "./run.py", line 8, in <module>
    from tcex.app_config.install_json import InstallJson
ModuleNotFoundError: No module named 'tcex.app_config'

Thanks again!


Always run the checks on any push or pull request no matter the target

Description
Always run the checks on any push or pull request no matter the target.
Following the example from https://github.com/opensearch-project/opensearch-build/blob/bddbc06dd5ee6b67d3be3230cab922a083d4f15a/.github/workflows/python-tests.yml#L4
Issues Resolved

Resolves #1614

Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Note; I am not sure there was an issue with the Pull Request vs Push execution.  There might be a transient failure that we do not yet have a root cause for, but this should prevent any doubt of altered executions


Don't highlight or select dates that are blank. Fixes #23

This pull request was not applicable because it was made on the flex version.
Additionally, the fix should have been to prevent the events from firing, rather than ignoring them when they do.

The pull request was made 20 days ago and at the time and was made against the develop branch so was correct at the time.


Fix image data size

The stride from the external library is bytes per line while in Rust and most
other places, stride is the number of bytes in each array slot.
Previously, the raw pointer would be created with an incorrect size (exactly a factor of stride – e.g. 4 in the default image format – too little.)

Nice catch!
bors r+

Figured that rustfmt would fail since it requires nightly to work with the current config, will change the rustfmt things later today and merge after that

bors r+


2nd time starting / connecting music after a reboot results in no sound (DAC)

Describe the bug
When librespot / spocon stops playback, I believe the device is left open and is not forcefully reopened or killed when a new playback attempt is made. There are no clear logs that describe this. Spotify continues to play back, but no audio is heard.
To Reproduce

Reboot Raspberry Pi Zero W
Connect to Spotify, and play music.
Stop music by disconnecting / switching to another device, pausing, or manually playing a podcast.
Try to reconnect, no audio.

Additionally:

The same behaviour can be found by now running speaker-test.

Expected behavior

Starting and stopping audio should work.
Being interrupted by another user on spotify should play their music, rather than bricking audio playback until reboot.

Screenshots/Stracktraces/Logs
pi@spotipi:~ $ speaker-test -dcard:Device

speaker-test 1.1.8

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Playback open error: -16,Device or resource busy

Version/Commit
1.5.3
Using alsa.
I did see this in the logs, not sure if it helps.
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,437 DEBUG PlayerQueueEntry:209 - PlayerQueueEntry{0178c7756e730278d60e63eddecdf07c} has been removed from output.
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,461 TRACE PlayerQueueEntry:325 - PlayerQueueEntry{0178c7756e730278d60e63eddecdf07c} terminated.
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,467 TRACE PlayerQueue:141 - Queue has been cleared.
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,476 TRACE AsyncProcessor:57 - AsyncProcessor{put-state-worker} is shutting down
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,490 INFO  Session:417 - Closing session. {deviceId: 504c79f310ca50f51a6c0400ff9432d5b4fa2206}
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,496 TRACE AsyncProcessor:57 - AsyncProcessor{dealer-worker} is shutting down
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,517 DEBUG DealerClient:319 - Did not dispatch connection invalidated: null != xyz.gianlu.librespot.dealer.DealerClient$ConnectionHolder@ed20b7
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,526 TRACE AsyncProcessor:57 - AsyncProcessor{event-service-sender} is shutting down
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,566 TRACE MercuryClient:183 - Handling packet, cmd: MercuryReq, seq: 82, flags: 1, parts: 1
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,571 DEBUG EventService:35 - Event sent. {body: 12|37|13|504c79f310ca50f51a6c0400ff9432d5b4fa2206|0178c7756e730278d60e63eddecdf07c|00000000000000000000
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,578 TRACE MercuryClient:140 - Send Mercury request, seq: 83, uri: hm://event-service/v1/events, method: POST
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,727 TRACE MercuryClient:183 - Handling packet, cmd: MercuryReq, seq: 83, flags: 1, parts: 1
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,730 DEBUG EventService:35 - Event sent. {body: 10|20|cb14f1eac699da36ffbf0163c5123494892b54c9|0178c7756e730278d60e63eddecdf07c|0|0|0|0|0|0|5242880|117
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,746 TRACE MercuryClient:140 - Send Mercury request, seq: 84, uri: hm://event-service/v1/events, method: POST
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,890 TRACE MercuryClient:183 - Handling packet, cmd: MercuryReq, seq: 84, flags: 1, parts: 1
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,895 DEBUG EventService:35 - Event sent. {body: 372|1|0178c7756e730278d60e63eddecdf07c|spotify:track:5mAitcAt2Z23HIIINIcY0h|0|[[148,123169]], result: 2
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,901 TRACE AsyncProcessor:48 - AsyncProcessor{event-service-sender} is shut down
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,909 TRACE Session:1368 - Session.Receiver stopped
Dec 29 23:55:06 spotipi java[444]: 2020-12-29 23:55:06,931 INFO  Session:476 - Closed session. {deviceId: 504c79f310ca50f51a6c0400ff9432d5b4fa2206}

Can you try starting the playback, pausing, waiting 30 seconds and then executing speaker-test -dcard:Device. The device should be released after 20 seconds of inactivity (and also when the session is closed).

My config: (Note that I changed the releaseLineDelay to 2.)
### Device type (COMPUTER, TABLET, SMARTPHONE, SPEAKER, TV, AVR, STB, AUDIO_DONGLE, GAME_CONSOLE, CAST_VIDEO, CAST_AUDIO, AUTOMOBILE, WEARABLE, UNKNOWN_SPOTIFY, CAR_THING, UNKNOWN) ###
deviceType = "COMPUTER"
### Device name ###
deviceName = "SpotiPi"
### Device ID (40 chars, leave empty for random)  ###
deviceId = ""
### Log level (OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE, ALL) ###
logLevel = "TRACE"
### Preferred locale ###
preferredLocale = "en"

### Cache ###
[cache]
        dir = "./cache/"
        # Cache enabled
        enabled = true
        doCleanUp = true

### Authentication ###
[auth]
        # Credentials file (JSON)
        credentialsFile = "credentials.json"
        # Spotify password (USER_PASS only)
        password = ""
        # Spotify authentication blob Base64-encoded (BLOB only)
        blob = ""
        # Whether to store reusable credentials on disk (not a plain password)
        storeCredentials = false
        # Strategy (USER_PASS, ZEROCONF, BLOB, FACEBOOK, STORED)
        strategy = "ZEROCONF"
        # Spotify username (BLOB, USER_PASS only)
        username = ""

### Preload ###
[preload]
        # Preload enabled
        enabled = true

### Proxy ###
[proxy]
        # Basic auth password
        password = ""
        # The proxy hostname
        address = ""
        # The proxy port
        port = 0
        # Whether authentication is enabled on the server
        auth = false
        # The proxy type (HTTP, SOCKS)
        type = "HTTP"
        # Whether the proxy is enabled
        enabled = false
        # Basic auth username
        username = ""

### Zeroconf ###
[zeroconf]
        # Listen on all interfaces (overrides `zeroconf.interfaces`)
        listenAll = true
        # Listen on these interfaces (comma separated list of names)
        interfaces = ""
        # Listen on this TCP port (`-1` for random)
        listenPort = -1

### Time correction ###
[time]
        # Manual time correction in millis
        manualCorrection = 0
        # Time synchronization method (NTP, PING, MELODY, MANUAL)
        synchronizationMethod = "NTP"

### API ###
[api]
        # API port (`api` module only)
        port = 24879
        # API listen interface (`api` module only)
        host = "<IP_ADDRESS>"

### Player ###
[player]
        # Whether to apply the Spotify loudness normalisation
        enableNormalisation = true
        # Initial volume (0-65536)
        initialVolume = 65536
        # Release mixer line after set delay (in seconds)
        releaseLineDelay = 2
        # Normalisation pregain in decibels (loud at +6, normal at +3, quiet at -5)
        normalisationPregain = 3.0
        # Output metadata in Shairport Sync format (https://github.com/mikebrady/shairport-sync-metadata-reader)
        metadataPipe = ""
        # Autoplay similar songs when your music ends
        autoplayEnabled = true
        # Preferred audio quality (NORMAL, HIGH, VERY_HIGH)
        preferredAudioQuality = "VERY_HIGH"
        # Audio output device (MIXER, PIPE, STDOUT)
        output = "MIXER"
        # Crossfade overlap time (in milliseconds)
        crossfadeDuration = 0
        # Whether the player should retry fetching a chuck if it fails
        retryOnChunkError = true
        # Mixer/backend search keywords (semicolon separated)
        mixerSearchKeywords = "Device [plughw:1,0]"
        # Output raw (signed) PCM to this file (`player.output` must be PIPE)
        pipe = ""
        # Log available mixers
        logAvailableMixers = true
        # Number of volume notches
        volumeSteps = 64

Fresh Reboot

❯ speaker-test -dcard:Device -c2

speaker-test 1.1.8

Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 96 to 262144
Period size range from 48 to 131072
Using max buffer size 262144
Periods = 4
was set period_size = 65536
was set buffer_size = 262144
Hardware PCM card 1 'USB Modi Device' device 0 subdevice 0
Its setup is:
  stream       : PLAYBACK
  access       : RW_INTERLEAVED
  format       : S16_LE
  subformat    : STD
  channels     : 2
  rate         : 48000
  exact rate   : 48000 (48000/1)
  msbits       : 16
  buffer_size  : 262144
  period_size  : 65536
  period_time  : 1365333
  tstamp_mode  : NONE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 65536
  period_event : 0
  start_threshold  : 262144
  stop_threshold   : 262144
  silence_threshold: 0
  silence_size : 0
  boundary     :<PHONE_NUMBER>
  appl_ptr     : 0
  hw_ptr       : 0
 0 - Front Left
 1 - Front Right
Time per period = 5.539558
 0 - Front Left
 1 - Front Right
Time per period = 4.040951

Plays Sound ^

speaker-test -dcard:Device -c2 works.
sudo speaker-test or speaker-test -c2 works.

Alright, time to open spotify.

On my PC, I select SpotiPi. (On an android and iphone device SpotiPi does not appear until it has been activated on the PC.)

This connection tool 50 seconds to appear in desktop spotify.
Pressing play on a file resulted in no output on the speakers.
Pausing and unpausing resulted in the connection switching to my phone's instance with no prompt.
I am not unable to switch to SpotiPi from the PC.
Attempting from my phone resulted in no success.
Closing and reopening Spotify on my PC allowed me to connect to SpotiPi.
Playing audio at this point does not function.

Back to speaker-test.

Wait 30 seconds:

❯ speaker-test -c2

speaker-test 1.1.8

Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Playback open error: -16,Device or resource busy

Try again a few seconds later: (NO SOUND, and notice the huge period time.

❯ speaker-test -c2

speaker-test 1.1.8

Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 96 to 262144
Period size range from 48 to 131072
Using max buffer size 262144
Periods = 4
was set period_size = 65536
was set buffer_size = 262144
 0 - Front Left
 1 - Front Right
Time per period = 20.341798

Fresh Reboot

sudo reboot
Connect to SpotiPi (connection took about 30 seconds)
Pressing play results in audio.
Pause spotify.
Wait 30 seconds.
speaker-test -c2: Pink noise outputs.
Repeat test results in the same audio.
Pressing play in spotify results in no audio.
Pause spotify.
Immediate speaker-test -c2 results in Playback open error: -16,Device or resource busy
Wait 30 seconds.
speaker-test -c2: No audio.

Another fresh reboot attempt

sudo reboot
Connect to SpoiPi (connection took 60 seconds)
Pressing play resulted in 1 second of audio, and then nothing.
Pause spotify.
Wait 30 seconds.
speaker-test -c2: Device Busy
sudo systemctl restart spocon
speaker-test -c2: No audio.

Attempt number 3:

Reboot
Connect to SpotiPi
Play
Pause
speaker-test: (good, period 3 seconds)
Play (Got audio)
Pause
speaker-test: (no audio, not busy, period 20 seconds again)
Play (no audio)

https://pastebin.com/u5ayZSBD

I've ordered a Raspberry Pi 4 so I can use the likely better supported Java11 to see if it works better.

As you can see there is no clear pattern in what's happening. The fact is that a Raspberry Pi Zero can't run a Java program properly and in a reliable way. You'll see many of this problems disappear on the Raspberry Pi 4 (hopefully).

Yeah everything worked flawlessly on the first try with rpi4 and performance is far superior.
Perhaps you should add a warning at the front that using a Raspberry Pi Zero W is unsupported and wont work as expected.
Thanks!

Yeah everything worked flawlessly on the first try with rpi4 and performance is far superior.
Perhaps you should add a warning at the front that using a Raspberry Pi Zero W is unsupported and wont work as expected.
Thanks!


Idea: Synchronization with or validation against other data sources

I love the idea of this project, however, as I understand it, the data is only collected via manual PRs and not validated. More value could be generated by automatically comparing this projects data with other data sources, e.g. Wikidata.
If everyone maintains their own version of these date, they are less reliable and it is, in sum, more work to keep them accurate.
Repology is another project that might have an interested in eol dates: https://github.com/repology/repology-webapp/issues/117#issuecomment-600270337

Hi @dreua, sorry it took us so long to give you an answer.
It's a little bit more complicated data and it depends of the kind of data.
I do not know how was endoflife.date in 2021, but now updates for a lot of products release date, latest release and latest release dates are done automatically. This is explained in https://github.com/endoflife-date/endoflife.date/wiki/Automation. We are always looking to automate this when possible via our dedicated project https://github.com/endoflife-date/release-data/. You can see a list of all the products updated automatically in https://github.com/endoflife-date/release-data/tree/main/releases.
EOL, end of support and end of extended support dates are still maintained manually, but that's something we are looking to automate when possible in the future.
Data collected manually is most of the time collected from the vendor documentation. For example for Microsoft products we are using https://learn.microsoft.com/en-us/lifecycle/. Sure error can be done but usually endoflife.date is pretty close to the reality, which is enough for most users IMHO. Wikidata have similar issues: errors can be made too (but I agree, considering there are more users using and verifying Wikidata, it may be a little bit more accurate).
I did not know Wikidata, and looking at https://www.wikidata.org/wiki/Q28865 this is definitely something we could use on endoflife.date. I do not know how exactly for the time being, but will try to investigate when I have some time. Thanks for the idea !

Specifically for repology, we already plan to use the repos.d dataset as part of our package linkage. (See WIP). So it shouldn't be too hard for us to sync back the EOL dates for distros to repology. Will keep this in mind.

If everyone maintains their own version of these date, they are less reliable and it is, in sum, more work to keep them accurate

I agree, hence we have an API, as well as plans to regularly publish a (automatically updated) dataset as well. That way, we (or any other project) can take up syncing with other sources (such as Wikidata).

For repology: First check with the maintainer whether back syncing is appreciated to avoid implementing something that's never used.
Pulling from repology and the other ideas sound great!
At the time of creating this issue, I have been casually updating release and eol dates of Fedora Linux in Wikidata (most tables and graphics on Wikipedia are rendered from that). So my main use case would be to check and fix those dates and ideally have an automation to update the different databases at once. As a starting point: Are you aware of any scripts to compare wikidata with endoflife.date data?

Will check, of course.
Not aware of any such usage, we maintain a list of known users at our wiki.
We are working towards a offline copy of our dataset at https://github.com/endoflife-date/endoflife.date/issues/2530 and you might find @adriens's WIP SQLite database helpful: https://www.kaggle.com/datasets/adriensales/endoflifedate/

Hi guys, I finally could manage to get something quite consistant, check https://www.kaggle.com/code/adriensales/endoflife-date-offline-copy/notebook
exports.tar.gz
:point_up: Daily scheduled

Nos I have to add the enrich phasis :thought_balloon: , please let me know

:point_down:

https://github.com/adriens/endoflife-date-exports


zipped application link is broken

[Enter feedback here]
Not able to download the application zip file

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

ID: cddd74b1-e0f1-1cae-e92d-c7c2b81e77e3
Version Independent ID: f853e977-81c2-64d6-682e-1e712344cbad
Content: Docker tutorial - Get started with Docker
Content Source: docker/tutorials/docker-tutorial.md
Product: visual-studio-windows
Technology: vs-azure
GitHub Login: @nebuk89
Microsoft Alias: ghogen

@elraikhm -- Elena, thank you for your feedback. This issue is being tracked in #5827.
cc @nebuk89 @ghogen for awareness


Is it possible to use this library with a proxy?

I need to make an FTP call with a fixed IP, so I'm using Fixie Socks.
I evidently have the proxy socket opening with socksv5, but when trying to access the FTP site I get:
Error: connect ECONNREFUSED <IP_ADDRESS>:21
Here's the code:
        SocksV5.connect(socksV5ConnectArgs, async (socket: any) => {
          try {
            const ftpOptions = {
                secureOptions: { socket },
                user: FTP_USERNAME,
                password: FTP_PASSWORD,
              }

            const promiseFtpClient = new PromiseFtp();

            // Next line fails
            const ftpPromiseResult = await promiseFtpClient.connect(ftpOptions)

            const listResult = promiseFtpClient.list();
            console.log(listResult);
          } catch (err) {
            console.log(err);
          }
        });

I've tried a number of other combinations to try and get this to work, but there's no indication if I am or am not passing the socket correctly along with the username/password combo, and I don't know what exactly is failing because the error message is vague.  Is there a way to make this work?  Thank you!

I was wondering the same thing.  Any luck yet @lukewlms ?

@chevin99 no :\ have spent some hours on this - it really seems like a scenario no one supports at all unfortunately!

@lukewlms dang, well thanks anyway for responding back so quick 😄


use --to-address and --from-address for filtering

currently --to-address and --from-address only are used for eth_calls and trace_calls datasets
but they should also be usable for filtering
relevant datasets

txs
traces
native_transfers
erc20_transfers
erc721_transfers

Hi. If you don't mind can I take this task?

that would be great
I think this is probably the best solution path

define an optional_parameters() function that specifies which optional parameters each of these datasets should take. see logs.rs or erc20_transfers.rs for examples. this makes it so that in the extract() function for each dataset, the request object can now return request.to_address() and request.from_address()
the extract() function should be modified to skip the data that doesn't satisfy the filter. for txs dataset this will require modifying the Response type to be optional and modifying the process_transactions function.  for the other datasets, no modification required, can just return an empty list from extract

I struggled a while to take from_address arg into new Dim... but found it quite tricky. I will try to stick on implementing easier filters first, to_address and maybe erc transfers first.

oh right, I forgot that from_address was removed from the Dim. yea to_address would be a good start
where are the difficulties with from_address coming from?

Even I define dim and optional args for from_address the supplied argument does not seem to be passed to query. If debugging takes too long I will try to open a draft PR and ask for comments.

Maybe this issue can be closed now?


Updated python and opencv

I did the following changes:

Updated python from 3.7 to 3.9
Updated OpenCV from 4.1.1 to 4.5.0
Replaced deprecated MAINTAINER with LABEL

Thanks!


Add `#[serde(skip_serializing)] to skip serializing some fields

Closes #99
cc @kostya: Is this what you're looking for?

thanks, how to use it?
json.rs/src/main.rs:22:3: 22:38 error: The attribute `serde` is currently unknown to the compiler and may have meaning added to it in the future
json.rs/src/main.rs:22   #[serde(skip_serializing, default)]

@kostya: If you're using serde_macros, try adding #[feature(custom_attribute)]. If you're using syntex and serde_codegen you shouldn't need to do anything, it'll add that for you.


Don't delete files generated at config time when make clean

I think this is caused only by the examples from scientific software design, like the burgers example.
Problem description: make clean followed by make fails because compiler_capabilities.txt is added to additional_make_clean property in CMake which tells make to remove the file, but it is generated to configure time, not compile time, and therefore should probably not be removed by make clean

Two respsonses:

Over time, this issue will disappear because I no longer use compiler_capabilities.txt files in new code and I'll eventually remove them from old code when I get around to doing some housecleaning. A better approach is to use add_definitions(...).
The compiler_capabilities.txt files get generated at configure time (as you note), used at compile time, and then are not needed after a successful build. My previous work flow involved something like

mkdir Build
cd Build
../buildscripts/gnu-compilers-cmake.sh
make
make install
make clean
Thus, I usually only do "make clean" after all building is done.  Of course, iterations such as
make
make clean
make
won't work because a new configuration step is needed after the "make clean". Probably the best approach is to keep this Issue open as a reminder to me to refactor old codes to replace compiler_capabilities.txt with add_definition(...).  It will take a bit of grunt-work and is not a super-high priority, but I imagine I'll get to it within the next 1-2 months.

Also, should probably generate files in the binary directory, not the source directory... I'll try to fix this.


Update use-data-gateways-sources-power-bi.md

Embedded capacity doesn't seems a correct option to work with Vnet Data Gateway. Other source of documentation doesn't confirm as reported in this page.

@nikkiwaghani
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Visualization with updated Isometry class

Since the animations have been fixed I don't think there's any more issues with the new Isometry class and the visualizer, unless there's any other problems this issue can be closed.


A new line still remains part of the link.

Is there an existing issue for this?

[X] I have searched the existing issues

Flutter Quill version
10.6.3
Steps to reproduce

Focus the quill editor
Type https://google.com
Press new line
Type Hello

Expected results
The word "Hello" should not be part of the link.
Actual results
The word "Hello" is part of the link.
Code sample
No response
Additional Context
No response

I cannot reproduce this issue on desktop. 'Hello' is not part of the link.
What platform are you using?
Is there any other text in your document?
When you are about to press  what is the status of the link toolbar button?
Any other information that would help me to reproduce this issue?

iOS / Andriod mobile app is remain.

Thanks for the information.
I tried using an Android emulator and still cannot reproduce the problem.
Can you run the flutter quill example app and see if you get the same problem? This way we will be running the same code and should get the same result.
The key observation is that after entering the link with the dialog, the link toolbar button should not be lit up. In my case it is not, but in your video it is.
My best guess is your code is doing something that we are not expecting, and we are not handling this correctly. We just need to find out what that something is.

My apologies. I wasn’t paying attention to which version of flutter_quill I was running. I thought it was the latest version, but it turned out to be 10.1.5. This bug has been fixed in version 10.2.0 (https://github.com/singerdmx/flutter-quill/pull/2114). Apologies again for the inconvenience. I will close this issue.

Thank you for letting us know the problem is solved.
(I also have trouble keeping track of versions!)

We might consider changing the release workflow and also not publishing versions on daily basis.

I agree. The only downside is that contributors could be submitting fixes that conflict with pending PRs.
I've learnt to check pending PRs, but I have still made mistakes.
I think your suggestions are correct: Once an issue is confirmed as a bug, someone should assign themselves and then it (should be) visible to everyone that it is being worked on. But do people actually check for existing issues before submitting a new issue?
One other thought: If there was a stable (master?) branch for everyone and a working branch for contributors, we could always find conflicts. Working could be pushed to stable on a weekly(?) basis.

I The only downside is that contributors could be submitting fixes that conflict with pending PRs.

It depends on the changes, for my PRs it usually requires very little effort, if a significant change was made in a file then the other should know before introducing a change and then having conflict that requires more effort and check than usual.

But do people actually check for existing issues before submitting a new issue?

Some of them don't If we're familiar with the issue, we can close it as duplicated and then redirect the submitter to the original issue.

One other thought: If there was a stable (master?) branch for everyone and a working branch for contributors, we could always find conflicts. Working could be pushed to stable on a weekly(?) basis.

The code base itself is not stable yet, even if we have a branch called stable, I suggested previously in different issues and threads, (see #2269) to only accept critical bug fixes, new code quality changes, tests, docs, and bug fixes will be in dev branch, new features will usually no longer accepted, especially those like such as markdown conventions for mobile, soft keyboard or youtube support, table or hashtag/mention, we can have exceptions but we should discuss it first, and should be clear to all contributors before they put the effort and time and then reject their changes simply because it's not a PR issue.
Features like Flutter/WASM are important for most users and should be supported when possible.
I think it's important to create more issues and discussions all in one place, I have repeated this at least 20 times across different unrelated issues. We should not lose track of suggestions and things to handle, we have discussed many things in previous issues or PRs but never created their own issue, resulting into completely losing them.
Contributors sometimes don't explain their changes and their changes are not self-explanatory either, if you take a look at my changes in 2023 you will notice I did something very similar, however, I have cleaned at least most of them and still solving issues. This is not something everyone does which is why I don't want to merge things that we don't understand (regardless of the reason) and then contact contributors after a while asking them about their changes.


update(userspace/falco): introduce new engine_version_semver key in v…

…ersions endpoint

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area tests

/area proposals

/area CI

What this PR does / why we need it:
With this PR we introduce a new key in the Falco /versions endpoint. This key will be used by falcoctl to match new artifact configs containing a full semver string for representing the required engine version.
The rationale for this change is the following:

Falco is already able to read engine_version both as numeric valuer or semver string
Rules repositories must be updated to use a full semver string for required_engine_version (already did it for Falco rules, will need this also for plugin rules). This will require a major bump for each artifact
New artifact config layers will contains the new engine_version_semver key
Let's also point out that falcoctl is already "keys agnostic". It just starts processing and matching keys starting from the config layer, and as long as it finds the same key in the /versions endpoint, we are fine.

With this being said, we end up in this situation (example for falco rules, will be the same for plugin rules):

Falco version
Rules and CI versions
Outcome

< 0.37
<= 2.0.0
Nothing changed, will work as before

< 0.37
> 2.0.0
If you upgrade only the rules, falcoctl will find two different keys and will not be able to match them, causing an error in falcoctl, not upgrading the rules. Also, if you manually start Falco with the new rules (on host, maybe) Falco will not start. I think this is perfectly fine, cause the rule will have a new major, so you must update Falco as well (would be the same if the engine version was only bumped, even if it was numeric)

>= 0.37
<= 2.0.0
Falco is updated. You can continue to follow 2.x.y rules, because it is able to read both a numeric engine version and a semver one. If you want, you can also follow the new rules (3.0.0)(see below)

>= 0.37
>2.0.0
Everything is new, so it will work as expected by matching the new key

PRs for updating the config layers are coming soon!
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign mstemm for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

cc @alacuku, @LucaGuerra for visibility

Hey @loresuso, thanks for the PR!
I think we should write some integrations tests in falcoctl to cover all the cases described above. To make sure that we are not going to break running instances of falco when upgrading them. I wuold be happy to help writing those tests.

@alacuku Agreed, we should somehow mock the version endpoint for the falcoctl test and try the out the function that checks the requirments. Happy to review if you are up for doing it!

/milestone 0.37.0

LGTM label has been added.  Git tree hash: 17f09781c489476f8b20c1c9b60fdfe4cc109bb8

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, incertum, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, incertum, leogr, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,incertum,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Console error on copy, both inline and block

This morning I started seeing this error in the console in both Brave and Arc
1fe36c97-27ba-4932-8540-ebc57469db01:2 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading '2')
    at HTMLSpanElement.i (1fe36c97-27ba-4932-8…ebc57469db01:2:9320)

(this is from inline - it changes to reading '6' when copying a block)
TBQH it's been a while since I've used the functionality, so I have no idea when this may have started.
OS: macOS Ventura 13.4
Arc: Version 0.106.1 (39259) Chromium Engine Version 114.0.5735.45
Brave: [Version 1.52.117 Chromium: 114.0.5735.90 (Official Build) (arm64)](https://brave.com/latest/)
I'll try on some other browser when I can.

hmm I'll look into this, Does the extension still work for you?

hey sorry for the delay - it does not. I see the same error in Safari as well.

It has been a long time.
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading '2')

Long enough I'd say, the fix for this has been submitted to Roam for review. You can follow the pull request here

This fix is now live in Roam Depot!

LGTM! Thanks so much!


test: testcases for autocomplete using slash and mustache

Description
Added test cases for autocomplete using slash and mustache
Fixes #9490

if no issue exists, please create an issue and ask the maintainers about this first

How Has This Been Tested?
locally
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
No changes to code coverage between the base branch and the head branch

/ok-to-test sha=ca84394

/ok-to-test sha=ca84394

/ok-to-test sha=f2f4081


Match latest sink-resources features

Update the version of cert generator and validator
Set prometheus default input for namespace metric sinks
Add e2e tests that scrapes prometheus metrics
Add e2e test to validate the telegraf deployment image deployed by the metric-controller matches the image of the telegraf daemonset.
Remove BaseLogger and use t.Log instead. This is caused by updating knative/pkg/test.
Forward events to fluent-bit asynchronously
Simplify verification of codegen
Require TLS when validating log sink configs
Vendor in code generation
Update tests for requiring tls
Generate configuration for multiple fluent-bit-out-syslog plugin instances
Update fluent-bit-out-syslog to v0.19
Create daemonset and service for node exporter

Signed-off-by: Benjamin Fuller<EMAIL_ADDRESS>

/retest

/lgtm

/lgtm


API requires login on Deta since last update

Making API requests requires logging into my Deta Space account since the last update.
I need my app to be able to temporarily upload files, and I can't do that anymore.

Right now I can just run a dev build with /api/new* added to the public routes. I am curious why this got changed though.

I decided creating pastes was for the owner of the instance only, otherwise anyone would be able to add content into anyone's instance. If you want to use the API to create pastes, you can create an API key in the app's settings (I will add this setting to the Spacefile).
The last update was the final bit of migration from the old Deta Cloud model to the new Deta Space model, so the entire app is no longer a public centralized site.

I've released a new version with API keys enabled, closing this issue now. Thanks @TheShovel!

Alright. Thanks!


Draft: Final before switch

patch for laravel 11 ....
did the tests ever work ?

❯ php vendor/bin/codecept run --report
Codeception PHP Testing Framework v5.1.2 https://stand-with-ukraine.pp.ua
[Seed] 516772414
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: Prefers apm environment variables | "apm_active true".......Ok
ApmConfigTest: Prefers apm environment variables | "apm_secrettoken".......Ok
ApmConfigTest: Prefers apm environment variables | "apm_appversion"........Ok
ApmConfigTest: Prefers apm environment variables | "apm_backtracedepth"....Ok
ApmConfigTest: Prefers apm environment variables | "apm_serverurl".........Ok
ApmConfigTest: Transactions config env variables...........................Ok
ApmConfigTest: Prefers apm environment variables | "apm_active false"......Ok
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: Spans config env variables..................................Ok
ApmConfigTest: Server config env variables.................................Ok
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: App config env variables....................................Ok
ApmConfigTest: Prefers apm environment variables | "apm_appname"...........Ok
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: Env config variables........................................Ok
ApmConfigTest: Default values..............................................Ok
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: Supports elastic apm environment variables | "elastic_a.....Ok
ApmConfigTest: App name special characters.................................Ok
NoCurrentTransactionExceptionTest: Exception provided code.................Ok
AgentBuilderTest: Build agent with collectors..............................ERROR
SpanCollectorTest: Collector name..........................................Ok
MissingAppConfigurationExceptionTest: Exception provided code..............Ok
StopMeasuringTest: Instance creation.......................................Ok
EventDataCollectorTest: Has started measure................................Ok
ScheduledTaskCollectorTest: Scheduled task finished listener...............Ok
NoCurrentTransactionExceptionTest: Exception default code..................Ok
EventCounterTest: Indicates when limit is not reached......................Ok
ApmCollectorServiceTest: Capture throwable with disabled agent for cli.....Ok
JobCollectorTest: Job failed listener......................................Ok
ScheduledTaskCollectorTest: Scheduled task skipped listener ignored........ERROR
ApmAgentServiceTest: Adds traceparent header to request....................Ok
JobCollectorTest: Job failed listener ignored..............................Ok
AgentTest: Asserts does have current transaction...........................ERROR
EventDataCollectorTest: Direct adding of measures respects limit...........Ok
EventDataCollectorTest: Start measure with fixed start time................Ok
EventDataCollectorTest: Stops collecting events when limit is reached......Ok
JobCollectorTest: Job failed listener with missing transaction.............Ok
StopMeasuringTest: Extra parameters........................................Ok
ScheduledTaskCollectorTest: Scheduled task finished null result............Ok
RecordTransactionTest: Use route uri.......................................ERROR
ScheduledTaskCollectorTest: Scheduled task starting listener ignored.......ERROR
ScheduledTaskCollectorTest: Scheduled task skipped listener................Ok
JobCollectorTest: Job processed exception on send..........................Ok
EventDataCollectorTest: Event limit applies across collectors..............Ok
EventCounterTest: Starts with zero events..................................Ok
EventCounterTest: Indicates when limit is exceeded.........................Ok
AgentTest: Asserts does not have current transaction.......................ERROR
JobCollectorTest: Job processed listener ignored...........................Ok
ApmCollectorServiceTest: Add collector with disabled agent.................Ok
EventCounterTest: Indicates when limit is reached..........................Ok
RecordTransactionTest: Transaction terminate ignored.......................Ok
SpanCollectorTest: Register listeners......................................FAIL
RecordTransactionTest: Transaction context.................................ERROR
RecordTransactionTest: Start transaction...................................ERROR
ApmCollectorServiceTest: Capture throwable.................................Ok
JobCollectorTest: Job processed sync driver................................Ok
EventDataCollectorTest: Start measure at current time......................Ok
CommandCollectorTest: Command starting listener ignored....................ERROR
ApmCollectorServiceTest: Start measure event with default values...........Ok
JobCollectorTest: Collector name...........................................Ok
StartMeasuringTest: Extra parameters.......................................Ok
RequestStartTimeTest: Microseconds.........................................Ok
CommandCollectorTest: Command finished but exception thrown on send........Ok
CommandCollectorTest: Duplicated transaction for command starting will.....Ok
AgentBuilderTest: Missing configuration exception..........................Ok
AgentTest: Adds collector..................................................ERROR
ScheduledTaskCollectorTest: Scheduled task finished listener ignored.......ERROR
AgentTest: Clears current transaction......................................ERROR
RecordTransactionTest: Transaction terminate error.........................Ok
ApmCollectorServiceTest: Add collector.....................................Ok
EventDataCollectorTest: Collects events by start order when limit is r.....Ok
ApmCollectorServiceTest: Capture throwable with disabled agent.............Ok
RequestStartTimeTest: Start time setter....................................Ok
AgentTest: Puts new metadata event on connector on send....................ERROR
EventCounterTest: Uses provided limit......................................Ok
AgentTest: Collectors are reset on send....................................ERROR
DBQueryCollectorTest: Fallback query name..................................ERROR
ApmCollectorServiceTest: Capture throwable extra args......................Ok
CommandCollectorTest: Command finished listener............................Ok
StartMeasuringTest: Instance creation......................................Ok
AgentTest: Events are added to connector when collected....................ERROR
JobCollectorTest: Job processing listener ignored..........................Ok
EventCounterTest: Uses default limit.......................................Ok
DBQueryCollectorTest: Disabled fast query executed listener................Ok
RecordTransactionTest: Transaction terminate...............................Ok
EventDataCollectorTest: Not started measure................................Ok
JobCollectorTest: Job processed listener...................................Ok
ApmCollectorServiceTest: Stop measure event with default values............Ok
EventCounterTest: Increments count.........................................Ok
AgentTest: Starting transaction sets current transaction...................ERROR
DBQueryCollectorTest: Query executed listener..............................ERROR
HttpRequestCollectorTest: It can register route events.....................FAIL
RecordTransactionTest: Transaction metadata................................ERROR
HttpRequestCollectorTest: Collector name...................................Ok
ApmCollectorServiceTest: Start measure event with values...................Ok
AgentTest: Start new transaction sets as current...........................ERROR
AgentTest: Sets self as agent when adding collector........................ERROR
CommandCollectorTest: Command finished listener ignored....................ERROR
EventDataCollectorTest: Start measure duplication..........................Ok
ScheduledTaskCollectorTest: Command finished but exception thrown on send..Ok
CommandCollectorTest: Command starting listener............................Ok
AgentTest: Current transaction is cleared on send..........................ERROR
CommandCollectorTest: Collector name.......................................Ok
NoCurrentTransactionExceptionTest: Exception message.......................Ok
FrameworkCollectorTest: It can register booting event......................FAIL
FrameworkCollectorTest: Collector name.....................................Ok
ScheduledTaskCollectorTest: Collector name.................................Ok
EventCounterTest: Can be reset.............................................Ok
EventDataCollectorTest: Empty measures.....................................Ok
ApmAgentServiceTest: Gets current transaction..............................Ok
ApmCollectorServiceTest: Stop measure event with values....................Ok
DBQueryCollectorTest: Collector name.......................................Ok
EventDataCollectorTest: Stop non started measure...........................Ok
ScheduledTaskCollectorTest: Scheduled task starting listener...............Ok
MissingAppConfigurationExceptionTest: Exception default code...............Ok
AgentBuilderTest: Build agent..............................................ERROR
EventDataCollectorTest: Collector name.....................................Ok
JobCollectorTest: Job processing listener..................................Ok
AgentTest: Throws exception when no current transaction....................ERROR
AgentTest: Returns current transaction.....................................ERROR
MissingAppConfigurationExceptionTest: Exception message....................Ok
ApmCollectorServiceTest: Add collector with disabled agent for cli.........Ok
Codeception Results
Successful: 98. Failed: 52.
"with luck" the pipeline does not fail completely ... however quiete some fails @nivseb
did this ever run sucessfully ?

16 fails on master. completely broken in fix-span-data


Code Buddy - Header

I opened this PR to review my project if it is as requested 👀
Project requirements that are done:

Create empty nav ✔
Add style to nav ✔

Feel free to review my project 👀 and if you have any questions please ask me. 💪

STATUS: APROVED 🟢 👏
Hello @Donard97 , Your project is complete! There is nothing else to say other than... Great job 👏 Congratulations! 🎉
Now you can merge this branch and move on 🥇 HAPPY CODING AND GOOD LUCK WITH THE COMMING ONES 🤞 🍀

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

@ahzia Thank you for approving my project!


subiendo reto 3

Hello @rcccort! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file reto-03/PalyPalillo/main.py:

Line 8:1: E302 expected 2 blank lines, found 1
Line 14:1: E302 expected 2 blank lines, found 1
Line 22:60: E231 missing whitespace after ','
Line 23:29: E221 multiple spaces before operator
Line 23:80: E501 line too long (81 > 79 characters)
Line 27:1: E302 expected 2 blank lines, found 1
Line 28:1: W293 blank line contains whitespace
Line 29:17: E225 missing whitespace around operator
Line 32:1: W293 blank line contains whitespace
Line 36:1: W293 blank line contains whitespace
Line 39:23: E225 missing whitespace around operator
Line 42:5: E125 continuation line with same indent as next logical line
Line 42:80: E501 line too long (92 > 79 characters)
Line 45:1: E305 expected 2 blank lines after class or function definition, found 1
Line 46:11: W292 no newline at end of file


increase sysctl conf file to 99- prefix

Prevents GCP cloud platform's default security policy for instances, which uses prefix 60-, from overriding ip_forward. Also future-proofs against any other such default policy.
Closes #744

Thanks!


checks not done completely , when a pull request is synchronized

Scenario
create a pull request , let two approvers approve it so it is ready to merge.
Now add another commit to it , the status goes back to pending again(which is correct)
but now if any user comments anything on it , status moves to mergeable (which is incorrect , according to me , since it should again require two approvals ).
The issue is arising , since right now we call getApprovals whenever a comment is added and
getApprovals counts ALL the comments on the PR , hence the very first comment after a new commit on a approved PR , approves it again .
One solution would be to - replace LGTM with some "DUMMY_VALUE" in all comments when a synchronized webhooks is fired .
so that it does not count them.

This is the intended behavior. Feel free to fork and change to meet your exact needs

I have a fork that fixes this behavior: https://github.com/lgtmeow/lgtmeow


Removed subscriptionTracer from Tracers'

This tracer is passed using RunNetworkArgs to initNetwork.

bors r+

bors r+


Updates for v3.16.5

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 20a8db4beea1d1cd23c434ec78de0e9ce49dabe2
https://deploy-preview-4148--calico.netlify.app


Tv details crashing

Contact Details
No response
What happened?
Opening a tv details page causes the app to crash
In which device are you seeing the problem on?
No response
Relevant code
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

assign pls

Yes ofc


Service worker runtime cache

I am creating a progressive web app using service workers and i am using service worker toolbox to cache my content. Service worker code to cache my content :
Service worker code to cache my content :
toolbox.router.get('/(.)', toolbox.fastest);
toolbox.router.post('/(.)', toolbox.fastest);
toolbox.router.get('/(.)', toolbox.fastest, {origin: 'https://example.cloudfront.net'})
toolbox.router.get('/(.)', toolbox.fastest, {origin: 'https://example.in'})
The code is running fine as i am not seeing any error in the console. But how can i check whether the images from cloudfront or the url's configured above are getting cached and rendered from the cache itself.

you can use chrome devtools .
Go to Network tab ,under the size column, you will see '(from ServiceWorker)' if a request being served by  the service worker.
To check if a resource is present in cache or not , go to Resouces tab ,under Cache Storage you can see all the request cached by sw.

I am able to see the resources which need to be pre cahced. So , i will be able to see the files for runtime cache as well?

@acircuit  yes


Pagination state is not being saved when using yadcf with language option

I appreciate your awesome works.
I am working on DT 1.10.16 with yadcf
and everything works great other than using language option..
stateSave: true,
language: {
url: '/static/datatables/datatable-korean.json',
},
If i remove url, pagination state is being saved... otherwise it does not work
Thanks

please provide a jsfiddle test page


ACOPF with OPFData

Note ACOPF now has a quadratic objective.

@klamike please confirm that we should not see any errors on branch/gen status tests for ACOPF on this branch.
Rest LGTM.

LGTM as well

Same as SOC: not deleting the branch just yet. It can be safely deleted after merging #118 .


Transfer-encoding: "chunked" essentially is a blocking call in express? Breaking production.

const express = require('express')
const app = express()
const port = 3000

app.get('/', (req, res) => res.send('Hello World!'));
app.get("/stream", (req,res) => {
	res.write("HELLO WORLD\n"); // real world use case actually streams data through many .write calls.
	req.on("close", () => {
		res.end();
	})
});

app.listen(port, () => console.log(`Example app listening at http://localhost:${port}`))

Run this, open 6 browser tabs on /stream and a 7th to homepage, the homepage will never ever load because the 6 /stream calls are blocking the main thread somehow from processing anymore requests.
Close some of the /stream tabs and watch homepage load again.
What this means from what we can tell is if we're streaming concurrent to 6 people our application literally stops responding; Our first thought is this some kind of security feature to prevent slow loris or something?

Hi @ShanonJackson this is how Chrome works with any server software: you are only allowed to have 6 concurrent requests to a given hostname.

Thanks for the quick response @dougwilson i would have never expected chrome itself would be the culprit. Guess i'll stream everything over 1 connection rather than streaming everything over multiple connections. Thanks.