Continuous appearance and disappearance of terminal windows

I use Windows 11 and Unity 2021.3.20f1. When the plugin attempts to send something to the server, it calls a CLI command program. I notice a lot of terminal windows appearing and disappearing quickly, which is really disrupting my work. How can I fix this?

This issue has occurred before and fixed before, do you have the latest main?

This issue has occurred before and fixed before, do you have the latest main?

Yes, I'm sure I'm using the latest version. I've never used this plugin before, so I discovered it on the same day that I wrote this issue. First, I installed it by adding the Git URL to the package manager, so it should have automatically downloaded the latest version. However, I then encountered the problem I described. I attempted to download the repository manually and put it in the assets folder so that I could edit the code (which is not possible if the plugin exists in packages), but I was unable to fix it properly.

I'll see if I can fix the issue once I find the time to get around to this. In the meantime, here is all the information that was collected so far for this issue.
I was already afraid this would happen before I created the Wakatime CLI implementation.

https://github.com/vanBassum/Wakatime.Unity/issues/7

For more information and things we have tried before, see:

https://github.com/vanBassum/Wakatime.Unity/issues/8
https://github.com/vanBassum/Wakatime.Unity/pull/9

If you want to try fixing this yourself, the following file is probably where you can find the issue:

https://github.com/vanBassum/Wakatime.Unity/blob/main/Editor/Utils/ProcessRunner.cs

This code is based on the example given by Wakatime:

https://github.com/wakatime/nuget-wakatime-shared-extension-utils/blob/master/src/WakaTime.Shared.ExtensionUtils/RunProcess.cs

Of course, If you have any questions, I'm glad to help you.

I can't reproduce this issue on my windows 10 system. I should try this again on a windows 11 system.

Merged the fix from @Kryeker to the main


[NEW] Adding from_designator + notes for usage

Fixes #170: minor changes because error handling for designators within this file wasn't standardized and should stay separated. This is a 2nd PR, first PR was done incorrectly.

I think the problem with the extra files in the previous PR was an artifact of at git (or github) deskop tool.
I've been told that a squashed commit will work in any case.


Feature/write file information to outbox repo gdev 280

Title for squash and merge:
Subscribes to file_staged_for_download, updates database entry, if ncessary

Description for squash and merge:
Subscribes to file_staged_for_download
Checks, if the file really exists in outbox
Updates the file related information in the database, if necessary

Tests also still missing, do not merge

Codecov Report

Merging #4 (d8b63d9) into dev (b33a6b1) will decrease coverage by 8.72%.
The diff coverage is 16.21%.

@@            Coverage Diff             @@
##              dev       #4      +/-   ##
==========================================
- Coverage   90.42%   81.70%   -8.73%
==========================================
  Files          19       20       +1
  Lines         282      317      +35
==========================================
+ Hits          255      259       +4
- Misses         27       58      +31

Impacted Files
Coverage Δ

drs3/pubsub/subscribe.py
0.00% <0.00%> (ø)

drs3/core/main.py
73.07% <22.22%> (-26.93%)
:arrow_down:

drs3/dao/db.py
86.15% <25.00%> (-8.59%)
:arrow_down:

drs3/config.py
100.00% <100.00%> (ø)

drs3/core/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #4 (b67d427) into dev (b33a6b1) will decrease coverage by 8.35%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##              dev       #4      +/-   ##
==========================================
- Coverage   90.42%   82.07%   -8.36%
==========================================
  Files          19       20       +1
  Lines         282      318      +36
==========================================
+ Hits          255      261       +6
- Misses         27       57      +30

Impacted Files
Coverage Δ

drs3/pubsub/subscribe.py
0.00% <0.00%> (ø)

drs3/core/main.py
65.51% <23.07%> (-34.49%)
:arrow_down:

drs3/dao/db.py
86.15% <25.00%> (-8.59%)
:arrow_down:

drs3/config.py
100.00% <100.00%> (ø)

drs3/core/__init__.py
100.00% <100.00%> (ø)

drs3/models.py
95.45% <100.00%> (ø)

drs3/pubsub/schemas/__init__.py
100.00% <100.00%> (ø)

drs3/pubsub/schemas/read_schemas.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #4 (11cbd8e) into dev (b33a6b1) will increase coverage by 0.74%.
The diff coverage is 97.43%.

@@            Coverage Diff             @@
##              dev       #4      +/-   ##
==========================================
+ Coverage   90.42%   91.16%   +0.74%
==========================================
  Files          19       20       +1
  Lines         282      317      +35
==========================================
+ Hits          255      289      +34
- Misses         27       28       +1

Impacted Files
Coverage Δ

drs3/dao/db.py
93.84% <87.50%> (-0.90%)
:arrow_down:

drs3/config.py
100.00% <100.00%> (ø)

drs3/core/__init__.py
100.00% <100.00%> (ø)

drs3/core/main.py
100.00% <100.00%> (ø)

drs3/models.py
95.45% <100.00%> (ø)

drs3/pubsub/__init__.py
100.00% <100.00%> (ø)

drs3/pubsub/schemas/__init__.py
100.00% <100.00%> (ø)

drs3/pubsub/schemas/read_schemas.py
100.00% <100.00%> (ø)

drs3/pubsub/subscribe.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #4 (2b5e3a7) into dev (b33a6b1) will increase coverage by 0.74%.
The diff coverage is 97.43%.

@@            Coverage Diff             @@
##              dev       #4      +/-   ##
==========================================
+ Coverage   90.42%   91.16%   +0.74%
==========================================
  Files          19       20       +1
  Lines         282      317      +35
==========================================
+ Hits          255      289      +34
- Misses         27       28       +1

Impacted Files
Coverage Δ

drs3/dao/db.py
93.84% <87.50%> (-0.90%)
:arrow_down:

drs3/config.py
100.00% <100.00%> (ø)

drs3/core/__init__.py
100.00% <100.00%> (ø)

drs3/core/main.py
100.00% <100.00%> (ø)

drs3/models.py
95.45% <100.00%> (ø)

drs3/pubsub/__init__.py
100.00% <100.00%> (ø)

drs3/pubsub/schemas/__init__.py
100.00% <100.00%> (ø)

drs3/pubsub/schemas/read_schemas.py
100.00% <100.00%> (ø)

drs3/pubsub/subscribe.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #4 (16d83eb) into dev (b33a6b1) will increase coverage by 0.74%.
The diff coverage is 97.43%.

@@            Coverage Diff             @@
##              dev       #4      +/-   ##
==========================================
+ Coverage   90.42%   91.16%   +0.74%
==========================================
  Files          19       20       +1
  Lines         282      317      +35
==========================================
+ Hits          255      289      +34
- Misses         27       28       +1

Impacted Files
Coverage Δ

drs3/dao/db.py
93.84% <87.50%> (-0.90%)
:arrow_down:

drs3/config.py
100.00% <100.00%> (ø)

drs3/core/__init__.py
100.00% <100.00%> (ø)

drs3/core/main.py
100.00% <100.00%> (ø)

drs3/models.py
95.45% <100.00%> (ø)

drs3/pubsub/__init__.py
100.00% <100.00%> (ø)

drs3/pubsub/schemas/__init__.py
100.00% <100.00%> (ø)

drs3/pubsub/schemas/read_schemas.py
100.00% <100.00%> (ø)

drs3/pubsub/subscribe.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


protoc-gen-go: fix test

Broken by addition of GoImportPath/GoPackageName.

GitHub pull requests could use a "quick approve" button. Maybe I'm blind and it's there.


Interfacing classifiers

If all classifiers would adhere to the same ClassifierInterface contract, wouldn't be easier for other contributors to add new classifiers?

How does this make thing easier or simpler?

It enforced necessary methods and their return types on classifiers, therefore avoiding the confusion what the class should contain.

Thanks for your contribution and the idea of adding interfaces 👍 .
Even though 1.0.0 has been released I think the Classifiers are still in a state of change.
In a future release I can see the need of an Interface/Contract system (for example when a user could add their own classifiers for their own "Components").
Until then we should keep it simple.


Promote AvatarStack to beta

Closes https://github.com/primer/view_components/issues/389

I think we're using this component only once in dotcom so far. Should we use it more before we go to beta?

I think we're using this component only once in dotcom so far. Should we use it more before we go to beta?

we can wait, no problem


Emulated view encapsulation invalidly compiles CSS custom properties in media queries

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [x] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node 9.4.0
npm 5.6.0
ng cli 7.1.3
Repro steps

Create a new component with scss or css styles (either one will repro the bug). In the styles, define a custom property scoped under a media query:
@media (max-width: 768px) {
  --kazaam: 'blue';
}

Desired functionality
CSS custom properties should be compiled as-is and not suffixed, however they get compiled like this:
@media (max-width: 768px) {
  --kazaam[_ngcontent-c2]: 'blue'[_ngcontent-c2];
}

CSS custom properties should be left unsuffixed, because it is invalid syntax.
Mention any other details that might be useful
A workaround is to nest them in a class, though they shouldn't need to be nested.
The same issue occurs for custom properties supplied under :root (:root gets prefixed) though it could be argued those should be defined in the global stylesheet. Custom properties defined under :host or a class are compiled properly.

I realized it's probably incorrect to not scope CSS custom properties within the media query- they should be scoped under a class or :host.


v6.7.3 breaks php7.0 support

As the title says, we came in this morning to builds failing with this error:

PHP Parse error:  syntax error, unexpected '?' in phar:///usr/local/bin/dep/vendor/symfony/console/Terminal.php on line 127

Digging into it, deployer is now bringing in Symfony 5 which isn't compatible with php 7.0
Appreciate that 7.0 is an older version but such a huge breaking change on a patch release isn't a good sign.
I can't even get to the docs to see about downgrading to an older release because the deployer site has gone down again (seems to be happening far too often, can't it be moved to github pages?)

deployed.org is online. And yes I was in rush for Symfony 5 and introduced BC.
I’m gonna fix it be releasing v7 with Symfony 5 only return compatibility with PHP 7.0.
Or you can fix version of deployer in composer.json.  What do you think?


Added Sample Demo application.

@neelamsharma12 I appreciate this PR! I'll try to squeeze some time in to review and merge :+1:

@neelamsharma12 unfortunately I cannot accept this PR as it contains unecessary pieces:

You are using Cocoapods to install the dependency where as it would be better to use SnapKit via a Subproject.
You have not added the Pods folder to .gitignore so the entirety of the Pods folder is now committed
There is a CoreData stack that is being created
Preference would be to not include any Storyboard files as they are not necessary to illustrate SnapKit's functionality
Preference would be to not include any image files as they are not necessary to illustrate SnapKit's functionality

I'm going to close this PR for now. I do appreciate the effort so if you do have time still and would like to fix the above issues and re-submit a new PR please do so.


pure-prompt: 1.19.0 -> 1.20.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sindresorhus/pure/releases.
meta.description for pure-prompt is: "Pretty, minimal and fast ZSH prompt"
meta.homepage for pure-prompt is: "https://github.com/sindresorhus/pure"
meta.changelog for pure-prompt is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.20.0 with grep in /nix/store/88pxg2mxybq8r1c3jycd55lh3b34d3l6-pure-prompt-1.20.0

found 1.20.0 in filename of file in /nix/store/88pxg2mxybq8r1c3jycd55lh3b34d3l6-pure-prompt-1.20.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
pure-prompt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/88pxg2mxybq8r1c3jycd55lh3b34d3l6-pure-prompt-1.20.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pure-prompt https://github.com/r-ryantm/nixpkgs/archive/526cb962e566a9b882b41b80bb20fffeac9a1e61.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/88pxg2mxybq8r1c3jycd55lh3b34d3l6-pure-prompt-1.20.0
ls -la /nix/store/88pxg2mxybq8r1c3jycd55lh3b34d3l6-pure-prompt-1.20.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pure-prompt

Maintainer pings
cc @pacien @pablo1107 for testing.

@ofborg eval


Maybe useful functions from syncomR

I created some functions to analyse in-vitro synthetic communities.
https://github.com/microsud/syncomR.
These include some functions for longitudinal data analysis and visualization.
Codes (not the best skills here) and data are tailored and bundled as R pkg for my manuscript (under review).
Some of these functions may be expanded to miaTime.

Whoever is the fastest, could try and make a PR out of the relevant ones. @microsud you are the best expert with these, if it is possible to make for instance one issue (and subsequent PR) per relevant functionality, including the details, that might help to keep things organized.

@microsud Thank you so much! I have found some functionalities that can be used for miaTime, but there is a problem occurring due to dependencies in the package. ERROR: dependency 'edgeR' is not available for package 'syncomR' That's why I couldn't run the examples but taxa_time_table , temporal_diversity , temporal_turnover functions can be suitable.

@microsud could you propose one or two functions to start with (but no visualization functions at this stage)? We could have a closer look on how to add those to miaTime.

Yes. we can start with https://github.com/microsud/syncomR/blob/master/R/short_term_change.R without the plotting step. This function essentially calculates the change in abundance over time for a microbe by abundancet2/ abundancet1 . I think it can be further improved as we start building this.
ref: Macroecological dynamics of gut microbiota

edgeR

You can try installing these before installing syncomR
if (!requireNamespace("BiocManager", quietly = TRUE))
    install.packages("BiocManager")

BiocManager::install("edgeR")

# Seqtime
library(devtools)
install_github("hallucigenia-sparsa/seqtime")
library(seqtime)

I think converting the test data in synComR into miaTime test data would be useful, specifically the SyncomFiltData as phyloseq object can be easily converted to TreeSE. It has species-level abundances in artificial in-vitro gut sampled ~20 days with ~3samples/day with various perturbations (article under review).

Very good for the demo data. Perhaps a separate issue could be opened about that one?
The abundance2/abundance1 thing: how about calculating this for all taxa at once? Implementation-wise it might be almost easier than doing it for a single taxa.

The function returns it for all taxa at once. Improvements to speed and code can be made for speed and efficiency.

TSE data added to miaTime #39

The functions still to be added, if I collect correctly from the thread above.
@YagmurSimsekk do you have any additional comments regarding the new functions if you had a look already?

Yup the function is not added. Once I have the codes ready, will create a new PR.

SyncomR has three options. Compared to starting Composition i.e. divergence, compared to each consecutive time point i.e. succession and compared to last sample i.e. convergence.

@Daenarys8 you could see if some of the syncomR functions could be translated to miaTime or miaViz

@Daenarys8 if you work on short_term_change, I have the following suggestions:
We would probably like to have both x-y and x/y differences available for time series. Both might be needed.
These are also sufficient. The logarithmic versions could be derived from them and in normally expected use cases one will not do log(x)/log(y), we only need x-y, x/y ,log(x)-log(y).
However, x/y = exp(log(x/y)) = exp(log(x) - log(y)). This can be calculated for logarithmized data with the "-" operation:
shortTermChange(tse, assay.type="counts") -> x-y
shortTermChange(tse, assay.type="log") -> log(x) - log(y) -> exp() -> x/y
So perhaps we could start by just having this function with the "-" operation because everything else that is usually needed can be derived from it?
First, try to check if such functionality is already available in some R package, there are really many R packages for time series and we would like to avoid overlapping work. I think there are R functions for calculating step-wise differences for univariate time series. Those could be used.
The planned functionality is univariate, but very closely related to the multivariate functions getStepwiseDivergence() and getBaselineDivergence() in miaTime.
In what data element you were planning to store the output from this function? colData, altExp, assay..?


Volumes: feature gates and some typos

Declared "CSIMigration" feature gate only exists in removed feature flags. According to this page section "CSIMigration" could be a switchable feature gate, but it looks like it is always on and cannot be switched off, so it it's strange that it's mentioned in the v1.27 documentation. All of this is probably more or less OK, as it's suitable for earlier versions of Kubernetes especially since there are deprecation warnings.
But it’s also unclear for which components this feature gate is intended. According to this page it's intended for kube-controller-manager.

https://kubernetes.io/docs/concepts/storage/volumes/#aws-ebs-csi-migration
https://kubernetes.io/docs/concepts/storage/volumes/#azuredisk-csi-migration
https://kubernetes.io/docs/concepts/storage/volumes/#azurefile-csi-migration
https://kubernetes.io/docs/concepts/storage/volumes/#gce-csi-migration

It is not clear for which components "CSIMigrationAzureFile" feature gate is intended.

https://kubernetes.io/docs/concepts/storage/volumes/#azurefile-csi-migration

It is not clear which controller manager is meant — cloud controller manager or kube-controller-manager. According to this page section it's intended for kube-controller-manager.

https://kubernetes.io/docs/concepts/storage/volumes/#aws-ebs-csi-migration-complete (InTreePluginAWSUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#azuredisk-csi-migration-complete (InTreePluginAzureDiskUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#azurefile-csi-migration-complete (InTreePluginAzureFileUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#openstack-csi-migration (InTreePluginOpenStackUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#gce-csi-migration-complete (InTreePluginGCEUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#vsphere-csi-migration-complete

It is not clear for which components "CSIMigrationRBD" feature gate is intended:

https://kubernetes.io/docs/concepts/storage/volumes/#rbd-csi-migration

It is not clear for which components "SizeMemoryBackedVolumes" feature gate is intended.

https://kubernetes.io/docs/concepts/storage/volumes/#emptydir

The description of "nodeExpandSecretRef" field does not start with a new line in the list.

https://kubernetes.io/docs/concepts/storage/volumes/#csi

The double word "node".

For Linux worker nodes, containerized CSI node node plugins are typically deployed as privileged containers.
https://kubernetes.io/docs/concepts/storage/volumes/#windows-csi-proxy

/language en

/assign RakshitKumar04

You can specify feature gates for all Kubernetes components (some might be no-ops). We could document that, but it'd be better to track that change as a separate issue.

@sftim, If you prefer to track this as separate issue, whether I should do something extra or not?

If you're willing to file a separate issue about that clarification @nnlkcncff, please do.

Let's stop mentioning CSIMigration in https://kubernetes.io/docs/concepts/storage/volumes/
You can specify feature gates for all Kubernetes components (some might be no-ops). We could document that, but it'd be better to track that change as a separate issue.
Let's remove the double use of node
Let's fix the formatting for nodeExpandSecretRef

@nnlkcncff these are useful things to point out. Thank you! If you find more, you can help further by opening one issue per thing that will need fixing.

I created separate issue https://github.com/kubernetes/website/issues/42199, so this issue should be closed after solving everything except point 2.

Hey, @nnlkcncff should I just work on typos here?

The description of "nodeExpandSecretRef" field does not start with a new line in the list.
https://kubernetes.io/docs/concepts/storage/volumes/#csi

The double word "node".
For Linux worker nodes, containerized CSI node node plugins are typically deployed as privileged containers.
https://kubernetes.io/docs/concepts/storage/volumes/#windows-csi-proxy

@RakshitKumar04, If it leads to a documentation fix, sure. Sorry, but I don't know enough about the workflow adopted here. I just feel it is my duty to help make the documentation better and I do my best.

Hey, @sftim Should I raise a PR correcting the documentation?


No opt for editing whitelist

@hnnam0906 edit Whitelist only for SINGLE mode by paste address to Input

It is ok but we should make a note for user know to use it.

Please review
@phoebehoang85 Should we update detail guide on git book for "edit whitelist" action?

Trong gitbook đã có hướng dẫn update whitelist rồi nhé. Close case


Problem With Github Actions/Azure

We would ideally like to run CI through GH Actions. Actions run on a VM through Azure:

GitHub hosts Linux and Windows runners on Standard_DS2_v2 virtual machines in Microsoft Azure with the GitHub Actions runner application installed. The GitHub-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work. For more information about the Standard_DS2_v2 machine resources, see "Dv2 and DSv2-series" in the Microsoft Azure documentation.

GitHub hosts macOS runners in GitHub's own macOS Cloud.

https://docs.github.com/en/free-pro-team@latest/actions/reference/specifications-for-github-hosted-runners

However, these VMs don't seem to expose the RAPL interface. Is there a workaround such that the VMs can expose RAPL or we can install RAPL? Maybe we might want to open an issue with GH Actions: https://github.com/actions/virtual-environments/issues

Waiting on support from GH/Azure.

Waiting on support from GH/Azure.


set prefer confirmed coinchooser as default

This will prevent using unconfirmed coins when doing mass operations, which leads to ancestor errors on lbrycrd.

😀😀


Tests failing due to ChannelResponseFilter._check_consistency_of_units

I think this failure is because I added a dummy unit conversion stage to the parkfield metadata, but I put it last and not first in the list.
Debugging... @kujaku11 I'll dig in and let you know what I find

Solved: Now that there are some sanity checks for the filters (like the output units of the previous filter match the input units of the next filter in sequence) as was just pushed to mt_metadata
specifically the method _check_consistency_of_units() in ChannelResponseFilter the mV/km triage that I put into the Parkfield metadata failed.
This is because the mV/km unit-conversion-filter (a conceptual kluge) was at the end of the sequence of filters, not at the start.  Issue resolved by changing from:
channel.filter.name.append(filter_name)
channel.filter.applied.append(False)

to:
channel.filter.name.insert(0,filter_name)
 channel.filter.applied.insert(0, False)

in aurora/sandbox/triage_metadata.py
Tests pass here


[Snyk] Upgrade org.yaml:snakeyaml from 2.0 to 2.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.yaml:snakeyaml from 2.0 to 2.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 24 days ago, on 2023-08-04.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

applied changes.


Allow being provided a list of services to bound to the apps

I'm adding a variable to be possible to provide a list of services to be bound to the apps. Such a feature is needed for example to send the apps logs to the log bucket.

Hi @loafoe, could you have a look at this PR? I'm adding a configuration to allow us to connect a logging service to the apps.

@l-lafin merged and created a new release


clean info about deleted spaces and indexes

This patch is similar to b17a3234daff03481d15efa9a0c24e0cf56888ed
after space is deleted there is no need to keep information about
it. At least it confuses users.
Closes #382

Please add a Changelog


Filtering and state_map

Within my filtering, I get none numerical battery levels (ex: high and low). I would like to use the "state_map" function together with my filtering as I would do for a known value. I just cannot figure out how to make it work.
Any idea?

Just use state_map at the root level of the config - at the card config level.
It will be applied to all entities


Can't pull rancher/system-upgrade-controller:latest image

                         node.kubernetes.io/unreachable:NoExecute op=Exists for 300s                                                                                │

│ Events:                                                                                │
│   Type    Reason   Age                    From     Message                                                                                │
│   ----    ------   ----                   ----     -------                                                                                │
│   Normal  BackOff  3m58s (x282 over 69m)  kubelet  Back-off pulling image "rancher/system-upgrade-controller:latest"

the same

Rancher got rid of the latest tag. You now need to specify the version, e.g.
system_upgrade_controller_manifest_url: https://raw.githubusercontent.com/rancher/system-upgrade-controller/v0.13.4/manifests/system-upgrade-controller.yaml

It's also mandatory to apply the whole manifest after cluster has been created otherwise some clusterRole bindings will go missing and system-upgrade-controller pod won't go up.
 kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/download/v0.13.4/system-upgrade-controller.yaml

I am planning to fix this in the next release this coming week.

This seems related to https://github.com/vitobotta/hetzner-k3s/issues/327.
As said in that issue I have fixed this on main (not released yet). If you could test it as well I would appreciate.

Hi @vitobotta already an idea, when the new release is comming?

Hi @vitobotta already an idea, when the new release is comming?

I am having some trouble to find the time at the moment because I have been promoted to a new role with more responsibilities and am having to prepare some stuff that takes time. I will try to work on it this coming weekend.

rc1 of v2 is now available, can anyone help with testing? see https://github.com/vitobotta/hetzner-k3s/discussions/385 for details.

Various improvements have been made in v2, which will be released probably next weekend. If you still have problems with v2 (currently rc4) then please open a separate issue with details on v2 :)


Error Handler, MD Shell: Better "Assertion failed" exception

This PR improves assertions in MD Shell and MD Debugger and Error Hander. It allows to invoke your own console programs when assertion fails and overhauls "Assertion failed" exception, which now displays the original assertion itself and the received value.

Changelog

Overhaul "Assertion failed" exception, display original assertion as-is and the received value;
Add optional console_program argument in assert macro to allow user to use custom debugger to handle failed assertion;
Save/restore CCR in assertion macro, so conditional flags aren't affected by it (this was already implemented for other macros);
Improve argument checks: check if argument is empty instead of missing (this allows to pass console_program to shorter assert form, e.g. assert.b d0, ne, , MyDebugger);
Upgrade AS version: 1.42 [build 55] -> 1.42 [build 212]. It's been a long-time coming. Previous version was rather old;
Implement tests for assertions (we are serious now!);
ASM68K-linkable bundle: greatly reduce assert/RaiseError size by pushing strings and data in RaiseError (used by assert under the hood) to dbgstrings section instead of inlining it in-between instructions;
ASM68K/AXM68K bundles: Fix a minor issue, where if "RaiseError" was used when "l" option was overriden, potentially breaking local label references used in its formatted string.

TODO

[ ] Make "Assertion failed: ... Got: ..." a global string template (we only need to dup it for .b, .w and .l argument sizes);
[ ] ASM68K bundle: Show warnings when post-increment and pre-decrement addressing modes are used (-(an), (an)+), because they have side effects and they are invoked twice now for the source operand (to display the actual value in the error handler).
[ ] Document new arguments and quicks of assert.
[ ] Test Windows builds.

New and improved assertions are finalized! (It's sure been a while)
Final implementation adds optional console_program argument to use your custom debuggers for assertion failures, greatly reduces generated code size for asm68k-linkable bundle, preserves CCR and more. See Changelog in the first post for more information.
I decided against doing some items on the original TODO-list, because this may make implementation extremely complicated without noticeable benefits.


Add deprecation warning to knife cookbook site

Our docs have been updated to point users to knife supermarket instead of knife cookbook site. We need to throw a warning when using knife cookbook site that suggests the same.

@tas50 seems deprecation warnings have been added for  knife cookbook site. I think we can close this issue?

Yep this is done


fix: Fix API deployment issues on a small ECS task

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines

What kind of change does this PR introduce?
Bug fix
What is the current behavior?
During deployment, Backend API service is never able to register a new Task Definition, because it never passes health checks.
Seems that we're running too many workers (2*cpu count + 1) on too small of a task (512 vCPU) and they just don't have enough CPU to work with.
What is the new behavior?
We limit number of workers when DEBUG is on. I think it's a better approach than increasing the size of the task to save costs.
I also moved gunicorn dependency to pytoml file.
Does this PR introduce a breaking change?
no

Fixes #347


Animating the SPR operation in PyGame

Right now going between marginal trees just draws a fresh tree. It would be great to add an animation of the process -- called an SPR for subtree pruning and regrafting. I already have some ideas on how to show this, but making it cover all the cases may require some casework of what sorts of SPRs can possibly show up. We can make the animation speed selectable by the user in a set of options on the side of the UI, with an option to turn animations off.

Sounds great @brianzhang01. It might be worth thinking about the full-arg case here as well, as it makes these SPRs easier to see. You can get these from an msprime simulation with record_full_arg=True.


[Coder] Searching for a pager from spotter does not scroll to it

Opening a package in spotter opens that package in coder, but it does not scroll to it

Also the package is not selected:


Feature: Added TypeScript Support for Directus Instance

🔧 Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Codebase improvement
[ ] Other (if none of the other choices apply)

🚨 Checklist

[x] I've read the guidelines for contributing
[x] I've added necessary documentation (if appropriate)
[x] I've ensured that my code additions do not fail linting or unit tests (if applicable)

Description
Description
This pull request introduces TypeScript support for the Directus instance, as described in the Directus SDK documentation. By adding TypeScript support, we can now benefit from enhanced type safety and improved code intelligence when interacting with the Directus instance in our codebase.
This enhancement allows developers to take full advantage of TypeScript's static type checking, catching potential errors early in the development process and providing better developer experience.

Thanks, this is a nice addition!


Datepicker value undefined does not update the displated value in the datepicker field

Describe the bug
The displayed value in DatePicker is not updated to the default "MM/DD/YYYY" when setting the value to undefined.
Steps to reproduce the bug

Set value in DatePicker to undefined (null not supported as null is not Date | undefined)
Observe that the value displayed does not get updated

Expected behavior
I expect that setting the date to undefined updates the displayed value to "MM/DD/YYYY", as is the initial state.
Specifications

Version: 0.37.0
Browser: firefox
OS:

Additional context
Add any other context or screenshots about the bug. An example in CodeSandbox is very helpful

Fix will be part of the next release of eds-core-react


Fixed simple filter applies to facet filter

Added a test when using a simple filter and a faceted filter at the same time

Codecov Report

Merging #102 (f74959d) into master (97b5009) will decrease coverage by 16.40%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master     #102       +/-   ##
===========================================
- Coverage   84.19%   67.80%   -16.40%
===========================================
  Files          66       66
  Lines        6732     6733        +1
  Branches      711      711
===========================================
- Hits         5668     4565     -1103
- Misses        810     1949     +1139
+ Partials      254      219       -35

Impacted Files
Coverage Δ

...ain/kotlin/dev/evo/elasticmagic/qf/QueryFilters.kt
92.45% <100.00%> (ø)

...ain/kotlin/dev/evo/elasticmagic/qf/SimpleFilter.kt
80.95% <100.00%> (-14.05%)
:arrow_down:

... and 39 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix: avoid accidental load of unnecessary Xcode setting lines

The original implementation grep-ed "CONFIGURATION", therefore it captured any lines that contain the word, not just the line starting with CONFIGURATION=. This PR fixes the issue so that relax now captures CONFIGURATION= line only.
Background: we faced a weird build issue where Swift compilation failed after I added
OTHER_SWIFT_FLAGS = "$(inherited) -D CONFIGURATION_XXX";

line in project.pbxproj file. Looking at the code, I noticed that relax captured this setting and exported it, which caused Xcode to use wrong OTHER_SWIFT_FLAGS option.

Thank you so much. This PR makes sense. Unfortunately, CI jobs are failed because they are too old to work on the current GitHub Actions environment. However it should work correctly after this change and then I merged this into the master branch.


Unclear what [channel] should be set to

Documents tell users which [distro] and [version] to use, but there is not information on what the channel should be, which channels are available, and what the differences are

Hello @dominique97. Can you please tell us to which article(s) your feedback applies? This will help us route this issue to the right team/writer.

Sorry bout that!  https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually

@dominique97 I think the information was added to the article, or was this part already in and you don't find it detailed enough.

@dominique97
The issue is being closed since your question seems to be answered. Feel free to re-open this issue if you feel that it hasn't been answered or that there are further suggestions to improve the documentation itself.
Thanks.


count occurrence of particular character in sentence

Related Issue

#1467

Proposed Changes

added code to count occurrence of particular character in sentence  with comments (explanation).
added a explanation in readme file with image.

Additional Info

changes are made in only S-String folder.
1st file : CountCharOccurrence.cpp
2nd file: README.md
tested with many input , screenshot of one of those is provided below.
time complexity O(n^2)

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the README.
[x] 🎀 I have updated the README accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1

Title goes here

Add a screenshot of the code with proper comments. add title to the screenshots properly

Add a screenshot of the code with proper comments. add title to the screenshots properly

@aditi944 changes asked by you are updated please review now

@Lakhankumawat kindly review my pr


Display custom greetings upon successfull login

It seems useful to be able to display a custom greetings prompt upon successful login (e.g; role of the CF target, pointer to documentation...).
Additional meta data about the current target (such as the support URL) could be displayed within the cf api or cf target command.
The v2/info endpoint returns a description field which can be set in the cf-release manifest (with a default empty value).  It would be a nice to display this field or a alternatively a new custom field returned in the /v2/info to be defined (e.g. greeting-prompt), as to preserve backward compatibility for existing Cf deployments that do currently return a non-empty description.
Command
cf login
Expected outpout
Given a description field set to Welcome to pre-prod instance. Planned maintenance on 24/08 8 pm. then the login displays the following prompt:
cf login
[...]
Authenticating...
[...]
OK
Welcome to pre-prod instance. Planned maintenance on 24/08 8 pm.
Use 'cf target' to view or set your target org and space

CLI Version
cf version 6.20.0+25b1961-2016-06-29

@SocalNick @Amit-PivotalLabs I like this idea. Do you have any concerns with us printing /v2/info's description field? Are we aware of installations where its value is used for other purposes?

I don't see an issue.  It's an unauthenticated endpoint anyways:
$ curl -s https://api.run.pivotal.io/v2/info | jq .description
"Cloud Foundry sponsored by Pivotal"

+1
Sent from my iPhone

On Jul 26, 2016, at 6:26 PM, Amit Gupta<EMAIL_ADDRESS>wrote:
I don't see an issue. It's an unauthenticated endpoint anyways:
$ curl -s https://api.run.pivotal.io/v2/info | jq .description
"Cloud Foundry sponsored by Pivotal"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@gberche-orange
About the timing of displaying the greeting (refer to this output example):

Before authentication allows the following:

Reminds the user what environment they're connecting to (staging/pre-prod/prod) before they enter their credentials (as those may depend on the target environment).
Allows the CF operator to (out of bounds) host a dummy /v2/info JSON file at the endpoint url with the maintenance notification during the maintenance period, useful if the subsequent authentication may fail.

After authentication before the org/space selection:

Reminds the user what environment they're connecting to (staging/pre-prod/prod) as it may influence the org/space name they want to connect to.

After the org/space selection, where it lists the summary of targeted API endpoint, User, Org and Space:

Any text above may have scrolled off the screen (especially if they didn't use -o and the cli prints their 50 orgs): The greeting stands out best near the end of the command completion.

Of course we could display messages at each step if CC (@SocalNick) exposes more fields, but for the initial solution, do you have a preference?
I'm leaning towards the first option because of its benefits, and also as it aligns well with what I see on my ftp server (not sure how that's set up though, but it displays a welcome message right after a one-line Connected to ftp.example.com and before asking my credentials):
diesk@cloud-cf:~/workspace$ cf login
API endpoint: https://api.bosh-lite.com
Welcome to pre-prod instance. Planned maintenance on 24/08 8 pm.

Email>

thanks @dkoper for considering this idea!
I agree with starting in a first simple step by displaying the normalized description field before authentication in the cf login and potentially cf auth command.
2nd step could be displaying the support address possibly in the cf help output
3rd step could be documenting extra custom keys that cf-release already supports through cc.info.custom keys.
For example, a documented convention name of a cli.greetings.target custom key that would display a greeting message as part of the cf target command. Such message could be more frequently updated by paas operators in order to notify users that benefit from automatically refreshed oauth tokens and would not otherwise frequently see the login greetings. Typical values for cli.greetings.target could be planned maintenance in 2 hours, or in progress maintenance affecting webui, check status on https://slack.my.org)

I have some concerns:

There is only one description field. I doubt it's localised and follows the API caller's Accept-Language header in picking what language to return. I need to check with @SocalNick whether localisation is implemented/planned, or whether we should define separate custom keys for that (cli.greetings.api.fr-FR, etc.) and let cf CLI pick the appropriate language.
cf CLI only calls the /v2/info API when running cf api or cf login -a. A cf login without -a, or cf target would either display a stale message (in particular with planned maintenance), or we'd have to make additional calls for certain commands. We use /v2/info for service discovery, not as a message board, so that requires an architectural discussion. For static info ("Welcome to pre-prod") this is less of a concern, we could cache it in ~/.cf/config.json.

We have no plans for localization that I'm aware of.

With the GA of the v7 CLI, we're no longer actively developing against the v6 line.  With an interest the overall hygiene of the CLI project we're closing this  issue.
If this issue is still occurring in v7 please feel free to comment and re-open. Thank you!

Hi @heyjcollins This feature request is still of interest against v7. Github does not allow non project members to reopen issues, would you mind reopening it ? This would avoid me resubmitting a duplicate and scattering comments and history ?


Attempt at PlayerUtils Null fix.

Type of change

[x] Bug fix
[ ] New feature

Description
I've added a check in EventBus, to check if the player is null or the world is null, if the check fails the event won't go through. And for EntityDamageEvent. I figured out that it causes a kick and added a world null check to it, seemed to fix it.
Checklist:

[ ] My code follows the style guidelines of ItziSpyder(ImproperIssues).
[x] I have added comments to my code in more complex areas.
[x] I have tested the code in both development and production environments.
[x] I have joined  the ClickCrystals Discord.

There is a concern, this PR does a player and world null check for every Event i believe that might cause some problems.

Nice 💯


Add validity requirement to contract descriptor

Specify that a contract descriptor needs to cover all possible outcomes that can be attested by the oracle(s).

Rephrased to emphasize that there should be a single payout per possible outcome, as having multiple payout per outcome should I think be prohibited.

Rephrased to emphasize that there should be a single payout per possible outcome, as having multiple payout per outcome should I think be prohibited.

Disjoint union contracts can have multiple payout per outcome, we may need an exception for that. Or describe it as per descriptor

Probably worth adding a note under the offer_dlc requirements
https://github.com/discreetlogcontracts/dlcspecs/blob/master/Protocol.md#requirements

Good point! updated

Rephrased to emphasize that there should be a single payout per possible outcome, as having multiple payout per outcome should I think be prohibited.

Disjoint union contracts can have multiple payout per outcome, we may need an exception for that. Or describe it as per descriptor

IIRC disjoint union conctracts use multiple contract descriptors, each with their own set of payouts and outcomes. So since the validity is defined on the contract_descriptor type I think it works (since a contract descriptor should still have only a single payout per outcome even with disjoint union).
It might change if we start supporting "and" contracts, but I'd say we should then update this when we do?

Merging as 3 people have approved

How we've implemented it: https://github.com/bitcoin-s/bitcoin-s/blob/ac3bae403bb34152c1372211847026bfad67da1c/core/src/main/scala/org/bitcoins/core/protocol/dlc/models/ContractOraclePair.scala#L14
Test cases:
https://github.com/bitcoin-s/bitcoin-s/blob/8857af2b66e8d493814d0bb7b817d8d46579709d/core-test/src/test/scala/org/bitcoins/core/protocol/dlc/ContractOraclePairTest.scala#L14

How we've implemented it: https://github.com/bitcoin-s/bitcoin-s/blob/ac3bae403bb34152c1372211847026bfad67da1c/core/src/main/scala/org/bitcoins/core/protocol/dlc/models/ContractOraclePair.scala#L14
Test cases: https://github.com/bitcoin-s/bitcoin-s/blob/8857af2b66e8d493814d0bb7b817d8d46579709d/core-test/src/test/scala/org/bitcoins/core/protocol/dlc/ContractOraclePairTest.scala#L14

My implementation is here for reference: https://github.com/p2pderivatives/rust-dlc/pull/40/files


Environments Example

Done in v0.3.3 in examples/environments/
Follow up task to write a guide for the docs site.


libtgvoip + tgcalls + tdlib vocie calls stuck on "exchanging keys " and disconnected after 20 secons

Any tdlib + libtgvoip or tgcalls v1 or v2 calls to any client  stuck on "exchnageinge keys " and disconnected after 20 secons
Very similar to tdlib bug
Maybe someone have any example of using tdlib + tgcalls v2?
Where does the key come from?

This can't be related to TDLib. Check that you provided correct reflectors and other data to tgcalls, and properly implemeted tgcalls callbacks, including the one which calls sendCallSignalingData.

sendCallSignalingData

I understand correctly that this is only needed for tgcalls?
for calls via libtgvoip, this is not necessary, right
now there is a strange situation when calls to telegram desktop clinet works
but on android apk via libtgvoip - no
looks like an issue of andoid apk itself with libtgvoip compatibility

for calls via libtgvoip, this is not necessary, right

Yes.

But you should use tgcalls instead of direct libtgvoip usage. libtgvoip is deprecated and its support can be removed any time in the future.

can be removed any time in the future.
looks like that moment has already arrived
in tgcalls legacy\InstanceImplLegacy.cpp - stoped work, seems it`s deprecated too


npm run coverage isn't working anymore

It outputs the message No coverage information was collected, exit without writing coverage information

I get a coverage report on a project started on Aug 19.

I have just started a new project yesterday and it doesn't work. I had
another project from some months ago and it was fine there, but when I did
a fresh npm install it also broke.
Can you try this?
On Mon, Sep 5, 2016 at 23:52 Frankie Bagnardi<EMAIL_ADDRESS>wrote:

I get a coverage report on a project started on Aug 19.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jbucaran/generator-rise/issues/34#issuecomment-244838184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC7Sk_xQ1H-_SIc5QHe9ELdtm3uesIznks5qnNVTgaJpZM4J1ai7
.

--
Haz

I get the no coverage info message on a fresh repo.

I read that isparta is deprecated. Maybe we can try the official nyc and babel-plugin-istanbul. But I can't make this work with tape.
Another solution would be tape-istanbul

If you do:
npm uninstall --save-dev isparta
npm install --save-dev nyc

And replace the coverage script with:
"coverage": "nyc --reporter=lcov --reporter=text npm run test",

Does it work? I did this and it fixed the problem. I can send a pull request.


MAINT: Fix a potential problem in nn_chain linkage algorithm

Motivated by #6788
Theoretically the previous algorithm could go in cycles, but I wasn't able to find an example data to trigger this. It seems nontrivial or maybe it even can't happen (but I can't prove it either). So I just followed the advice in the paper (by D. Müllner) which suggest to account for it. This change certainly can't violate correctness.
Another change is to make the algorithm follow the convention from fastcluster, again doesn't violate the correctness, but make results identical (if floating point computations works exactly the same) with fastcluster package.
I guess I will wait for couple of days and merge myself, if no one comments.

LGTM, merged. Thanks Nikolay!

While you were comparing with fastcluster, did you happen to do any timing comparisons? http://danifold.net/fastcluster.html?section=1 is certainly not correct anymore, but it would be nice to know if our implementation is now actually as fast or faster (that's even better than just having the right big-O scaling).

I did some comparison before, but not very thorough.

Asymptotically we as good as fastcluster.
Time-wise fastcluster is faster for O(N^2) methods: for a factor of ~1.7 in mst algorithm and for a factor of ~3.5 for nn-chain algorithm. I explain it by the fact that fastcluster is written in C++ directly and it also somewhat optimized for performance (like using a linked list for storing remaining nodes, etc.) I think improvements can be made on scipy's side.
The most interesting situation is with 'centroid' and 'median'. While their worst case complexity is listed as O(N^3), in practice they work much, much faster (about O(N^2) or something like that). Whereas the scipy's straightforward algorithm really makes N^3 operations. For example, clustering 2000 points with 'centroid':

scipy: 2.63 s
fastcluster: 31.4 ms
The idea is that fastcluster uses something quite interesting and efficient instead of the trivial algorithm for 'centroid' and 'median'. This algorithm is explained in Müllner's paper (it's his own development), I will try to investigate.

Thanks Nikolay, interesting. I'll open an issue about 'centroid'/'median' to not lose your comment.


Tunable knob for ASG Cooldown period

Thanks @prateek, can you tell us a bit more about your use case? Interested to hear a bit more about what problem you are trying to solve that needs the cooldown periods customized!

tl;dr - the 300 hardcoded value was not in line with my expectation of elasticity of the stack.
@lox sure thing! The use-case is standard CI - my team has one mega (github.com/m3db/m3) repo and some smaller repos (github.com/m3db/*) – we're in the process of consolidating in a monorepo right now. Developers in the team rely on the for quick PR feedback, so push to GH/CI frequently.
The reason for the PR might completely be misconfiguration (please tell me if it is).
Here are the knobs I had when I was testing:

ScaleUpAdjustment: 6
ScaleDownAdjustment: -3
ScaleDownPeriod: 120

Along with that, each of my CI builds has 6 jobs. So what would end up happening was I'd push some code, look at the build and go incorporate feedback. By the time I pushed again, the stack had hit the cooldown period once and had triggered an instance kill. At this point, it would wait for the cooldown period before spinning up more instances.

After some thought, if I have to choose between a config option with a warning on it and no control for folks that need it, I'll choose the config option. Let's get this merged in and documented and I'll do some testing. Thanks for the perspective @ecv and apologies it's taken me so long @prateek.


[Snyk] Upgrade htm from 2.1.1 to 2.2.1

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade htm from 2.1.1 to 2.2.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.

The recommended version was released on 5 years ago.

Release notes

Package name: htm

2.2.1 - 2019-07-31Maintenance release: adds .mjs copies of the new .module.js dist files to avoid broken unpkg links (#113).

2.2.0 - 2019-07-29
Adds support for namespaced JSX elements and attributes (<a:b c:d="e" />)

2.1.1 - 2019-02-28

    from htm GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.536%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
637

Relevant Lines:
640

💛  - Coveralls


Add cmss work flow

[x] Make sure you have followed Kube-OVN Code Style.

What type of this PR
Examples of user facing changes:

Features

修复一些 markdown lint err

release-1.12-cmss 分支是一个介于 master 和 release-1.12 之间的分支，用于 cmss 快速从 master 合并特性到 release-1.12.
该分支需要跑一下 build 和常规的 e2e 流水线，不需要 push 镜像

Which issue(s) this PR fixes:
Fixes #(issue-number)
WHAT

🤖 Generated by Copilot at 039af44
This pull request updates the GitHub templates and workflows for the kubeovn/kube-ovn repository. It improves the issue and pull request templates for clarity and consistency, and adds support for building and testing a custom branch release-1.12-cmss that has a specific use case of Kube-OVN.

🤖 Generated by Copilot at 039af44

Oh we're the crew of the release-1.12-cmss
We build and push our images with finesse
We test our Kube-OVN on every node
And we fix our templates to make them look good

HOW

🤖 Generated by Copilot at 039af44

Add a new branch release-1.12-cmss to the workflows for building, pushing, and testing the base image and the Kube-OVN components with various features. This branch is a custom branch for a specific use case of Kube-OVN. (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
Use headings instead of bold text for the templates of bug-report, feature-request, and pull-request for clarity and consistency. (link, link, link)
Move the checklist to the top of the pull-request template for visibility and change the order of the user facing changes to match the order of the labels in the repository. (link)

hi @oilbeater , could you help review this?

The DCO failed

The DCO failed

fixed


Generalize the firm's production function

We should generalize the firm production function from it's current Cobb-Douglas production function to a more general Constant Elasticity of Substitution function.  This will allow one to vary the elasticity of substitution.

This functionality added in PR #278


Support partial updates to Java file to replace/update generated protocol methods

This is a follow-up task of https://github.com/Azure/autorest.java/issues/1049. Autorest should support updating a Java file that has a mixture of generated and handwritten methods based on the method annotation.

This probably is not easy for autorest. autorest.java send the content of the file to autorest for writing.
Fluent codegen did some tricky stuff to first read the file (relative to output-folder), then write a new one based on its previous content, and finally send it to autorest.
https://github.com/Azure/autorest.java/blob/v4/fluentgen/src/main/java/com/azure/autorest/fluent/model/projectmodel/Project.java#L290-L302
It is probably not the best solution for large numbers of java files.
.NET can use partial class, which is not available to Java.

Another approach to persist manual change is writing customizations. It supports various types of customizations. However, it has limitations. It does not support adding custom code, e.g. changing the body of a method, adding a method. It is a common usage that add a wrapper on fundamental methods to provide high-level user experience.

Study of the issue.
https://microsoft-my.sharepoint.com/:w:/p/fey/EWSuAr4hPhxChdCtrxLOXYABIDpjWVZbKbhzP6bRTv3Z_A?e=UmmlRL

https://github.com/Azure/autorest.java/pull/1187

A few cases you need to cover in test:
Manually add class variable and method
They need to be kept.
Manually update method signature
E.g. https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/webpubsub/azure-messaging-webpubsub/src/main/java/com/azure/messaging/webpubsub/WebPubSubServiceClient.java#L496-L500
permission changed from String to WebPubSubPermission.
Manually remove method
E.g. https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/webpubsub/azure-messaging-webpubsub/src/main/java/com/azure/messaging/webpubsub/WebPubSubServiceClient.java#L108-L111
method changed to package private to remove it from public access.
Updated swagger adding new method
They need to be added.
Updated swagger removing method
They need to be removed if not customized.
Updated swagger update method signature
They need to be updated if not customized.


feat: add dates to resources in RH

@tanay1337 I made a design proposition for displaying the date (a full line instead of a chip), please let me know if you don't like it and I'll change it back to chips.

@louis-md I have requested a few minor updates via Slack.


feat: add resource rules to krm-kcl spec

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

fix #13

2. What is the scope of this PR (e.g. component or file name):
kcl-lang/krm-kcl/pkg/options/testdata/resource_list

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

Added resource matching rules to the krm-kcl spec
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[ ] N
[x] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

Please take a look, @Peefy

I think we should first implement this feature in the corresponding code before modifying the test cases.

I have added the MatchConstraints struct and the function to verify resource matching rules to config.go @Peefy

Could you please fix the CI?

I have modified the test cases in config_test.go to address the errors, and make test works fine now.
PASS
ok      kcl-lang.io/krm-kcl     7.814s
shruti@fedora:~/cncf/krm-kcl$

I think we should use the resourceRules field directly, and remove matchConstraints to resolve the following errors while testing.
FAIL: TestRunLocalPath (0.00s)
    --- FAIL: TestRunLocalPath/resource_list (0.00s)
        run_test.go:72: TestRunLocalPath() error = yaml: unmarshal errors:
              line 10: cannot unmarshal !!map into []config.ResourceRule, wantErr false

Is this the correct approach @Peefy.

I suggest keeping this field as it is consistent with Kubernetes CEL, please refer to https://kubernetes.io/docs/reference/access-authn-authz/validating-admission-policy/#creating -A-validatingadmissionpolicy

Any ideas on what might be causing this error @Peefy, since I have tried out correcting any possible syntax error or error in the test cases.

Done with the changes @Peefy.


Assert on pretty-printed json with built-in json-equals assertion

Switched to built-in phpunit json-equals assertion, which brings a number of improvements, namely:

Both json strings are validated to be valid json
Order or the object properties no longer matters

Added pretty-printing for json, which improves failure output. Whereas previously failed assertion would output entire json documents as different, now the output will focus on actual semantic changes, highlighting differences much more precisely.

This bumps the requirements for dev/test environment to php >=5.3.3, as it's the lowest version for PHPUnit 3.7 where this assertion method was introduced. Hopefully those few early 5.3.* releases are not really important, as travis shows this is only tested on 5.3.29.


mipmap support

You should add mipmap support for icon drawable.

There's no difference in retrieving these. MipMaps just allow you to use getDrawableForDensity rather than only getDrawable.

So you can manually use icon(Drawable) yourself.

But you can not assign R.mipmap.ic_smthg  to icon. I mean it is not possible to use     icon(R.mipmap.ic_smthg)

Yes, but there's no way to determine whether an integer represents a regular drawable or a mipmap. I could add a iconMipmap method but it would require additional parameters. At this point, it's easier if you manually get the Drawable yourself.


Add jupyter notebook examples

As the theory is quite rigorous, and a lack of documentation as of now, creating examples would help people use the library.

I guess this has been tackled in #72


Update get-networkcontrollerloadbalanceroutboundnatrule.md

Added descriptions and example

@AnirbanPaul,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


No points cloud data found in "testing_3d_camera_only_detection_testing_3d_camera_only_detection_000x.tar" ?

Hi, thank you for providing such a wonderful dataset.But I can't access the pc data in waymo_1.3.1 camera_only_test dataset.Is it not released?

As the rules written on the Waymo's website, the 3D camera-only challenge is supposed to be inferenced on camera images only.
Therefore, I think there is no point cloud data in the testset.


Support more configs for cluster and VCN creation

What would you like to be added:

Support the following config in  OCIManagedControlPlaneSpec:
https://github.com/oracle/cluster-api-provider-oci/blob/b53ef08340b0f763ca776f6e828348cfd9e4662e/api/v1beta2/ocimanagedcontrolplane_types.go#L147
Additional options:
serviceLbSubnetIds
https://docs.oracle.com/en-us/iaas/api/#/en/containerengine/20180222/datatypes/ClusterCreateOptions
https://github.com/oracle/cluster-api-provider-oci/blob/b53ef08340b0f763ca776f6e828348cfd9e4662e/api/v1beta2/ocimanagedcontrolplane_types.go#L88
Additional options:
subnetId
https://docs.oracle.com/en-us/iaas/api/#/en/containerengine/20180222/datatypes/CreateClusterEndpointConfigDetails

Support for prohibitPublicIpOnVnic
https://docs.oracle.com/en-us/iaas/api/#/en/iaas/20160918/datatypes/CreateSubnetDetails

Add support for customized route table:
https://docs.oracle.com/en-us/iaas/api/#/en/iaas/20160918/datatypes/CreateRouteTableDetails
Currently we can only choose to skip or not skip route tables
https://github.com/oracle/cluster-api-provider-oci/blob/b53ef08340b0f763ca776f6e828348cfd9e4662e/api/v1beta2/types.go#L1090

Add support for Dynamic Routing Gateways
https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/managingDRGs.htm

Why is this needed:
We would like to automate networking and cluster setup using CAPOCI. These features are required for our networking and cluster setup

Update:
For No.1 We are able to achieve this by adding the role parameter to the lb subnet and control-plane-endpoint subnet https://github.com/oracle/cluster-api-provider-oci/blob/main/api/v1beta2/types.go#L34
For No.2 We are able to set prohibitPublicIpOnVnic by setting the type of subnet https://github.com/oracle/cluster-api-provider-oci/blob/main/api/v1beta2/types.go#L858
For No.4: There is existing support to add DRG


[BUG] Azure AI Search SDK's paging seems to be broken in latest release

Library name and version
Azure.Search.Documents 11.5.0
Describe the bug
I'm migrating some existing code using "Azure.Search.Documents" from the 11.5.0-beta5 to the final 11.5.0 version but I'm getting an error while paging through the results that "The parameter 'semanticConfiguration' must not be empty". Digging a bit deeper I've noticed that the first page of results is fine (it does set "semanticConfiguration=default" in my case), and the API response includes<EMAIL_ADDRESS>but the next request that the SDK performs doesn't actually include most of those parameters.
Expected behavior
The SDK should request the next page of results with the same parameters as the initial request.
Actual behavior
The SDK requests the next page of results without the required parameters from the initial call (or those coming back from the service in<EMAIL_ADDRESS>Reproduction Steps
Client code:
var serviceResponse = await requestedSearchClient.SearchAsync<SearchDocument>(searchText, searchOptions);
foreach (var result in serviceResponse.Value.GetResults()) { ... }

Initial request:

Next page params from initial response:

Second request (lacking those parameters but including "skip=50"):

Error on second request:
{"error":{"code":"","message":"The parameter 'semanticConfiguration' must not be empty. Alternatively, set a default semantic configuration for this index.\r\nParameter name: semanticConfiguration"}}
Environment
.NET SDK:
Version:   7.0.114
Commit:    b2a71039cd
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.22631
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\7.0.114\
Host:
Version:      7.0.14
Architecture: x64
Commit:       808851b07a

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Thank you for bringing this issue to our attention. I can confirm that it is an issue, and I want to assure you that we are currently addressing it. I've submitted a PR here, and I'll keep you informed once we release the updated package with the fix. We apologize for any inconvenience caused by this issue and appreciate your understanding.

That was quick - thank you so much for the quick turnaround!

Hi @jelledruyts , we've released https://www.nuget.org/packages/Azure.Search.Documents/11.5.1 package containing this fix. Please confirm if it resolves your issue. Thank you!

Yes, I've retested and it works now - thanks again for the quick fix!


UOp rewrite const to the end of MUL

similar to ADD

slightly annoying and not really needed for now


No suggestion for method returning 'self'

Product and Version : VSCode 1.43.2
OS Version: Windows
IntelliCode Extension Version:  1.2.6
Target Platform or Language: Python
Hi, i have simple class:
class simpleA():
    def __init_(self):
        ...

    def method1(self):
        print 'hello'
        return self

    def method2(self)
        print 'world'
        return self

example:
simpleA(). -> suggestion: method1/method2
simpleA().method1(). -> no suggestions ;(
Is there chance to show suggestionst for methods returning self?

It does seem to work for me. Do you have both IntelliCode and the Python extensions installed and enabled?

hmm ...
can you check it inside class :P
class simpleA():
   . . .
    def run_all_methods(self)
        self.method1().method2()

Hi, consider trying the IntelliCode Completions extension.
It should be able to assist here.
https://marketplace.visualstudio.com/items?itemName=VisualStudioExptTeam.vscodeintellicode-completions


Fix bug with youtube.addPart('')

Lets say I wanted to add liveStreamingDetails to video when calling getById method :
var youtube = new Youtube(''KEY');
youtube.addPart('liveStreamingDetails');
youtube.getById('videoId', function(err, response){...});
liveStreamingDetails woudn't be included in the api call because you would first clear the parts and then call .getUrl method.
This way parts are cleared every time you serialize them to string.

Please fix conflicting.


Deezer Thumbnails

Deezer is not providing artwork urls anymore
but keeps providing the md5_image tag:
you can get the thumbnail by:
`https://cdns-images.dzcdn.net/images/cover/${deezerSearchRes.md5_image}/500x500.jpg`

as far as I can tell track.album.cover_xl still exists


Update metric API maintenance to use dynamoDB

If the incoming request is in the test, fetch the data for maintenance  from dynamo else, fetch the results from s3.
maintenance.timeline

Query for records from github-activity with key condition expression name=:plugin_name AND type_identifier BETWEEN :start_month AND :end_date and projection of installs and timestamp field.

aws dynamodb query \
--table-name dev-test-github-activity \
--key-condition-expression 'name = :plugin_name AND type_identifier BETWEEN :start_date AND :end_month' \
--expression-attribute-values '{
":plugin_name": {"S": "foo"},
":start_month": {"S": "MONTH:202202"},
":end_month": {"S": "MONTH:202301"},
}'
--projection 'number_of_commits, timestamp'

In the above query, replace table_name with the correct table name by stage and stack name. Also, update the expression attribute value to have relevant values for all the fields. The start_month and end_month should be computed dynamically based on the current date.

Then, transform the results from the dynamo to the expected format while adding records with a default value for installs for the missing months.

maintenance.stats.latest_commit_timestamp

Query for records from github-activity with key condition expression name=:plugin_name AND type_identifier BEGINS_WITH :type and projection of timestamp field.

aws dynamodb query \
--table-name dev-test-github-activity \
--key-condition-expression 'name = :plugin_name AND type_timestamp BEGINS_WITH :type' \
--expression-attribute-values '{
":plugin_name": {"S": "foo"},
":type": {"S": "LATEST:"}
}'
--projection 'timestamp'

In the above query, replace table_name with the correct table name by stage and stack name. Also, update the expression attribute value to have relevant values for the plugin_name field.

Then, transform the results from the dynamo to the expected format with a fallback to None if there are no records.

maintenance.stats.total_commits

Query for records from github-activity with key condition expression name=:plugin_name AND type_identifier BEGINS_WITH :type and projection of timestamp field.

aws dynamodb query \
--table-name dev-test-github-activity \
--key-condition-expression 'name = :plugin_name AND type_timestamp BEGINS_WITH :type' \
--expression-attribute-values '{
":plugin_name": {"S": "foo"},
":type": {"S": "TOTAL:"}
}'
--projection 'number_of_commits'

In the above query, replace table_name with the correct table name by stage and stack name. Also, update the expression attribute value to have relevant values for the plugin_name field.

If the result has a record, populate total_commits with the results from the records of type TOTAL:. Else set total_commits to 0.

In the above query, replace foo with the relevant plugin_name and table_name with the correct prefix.
Some of the data that could be useful to have logged:

Time taken for dynamo read
If plugin has query results

post-merge & post-release to-dos

Enable the feature flags in the appropriate environments
Ensure there are no relevant errors on Datadog, Lambda, etc
Verify the API endpoints work as expected in the appropriate environments
Verify the plugin page, and any other pages that may be relevant, load as expected
In this specific case, it requires us to backfill data (reset timestamp to 0) in parameter store so that the tables populate with the appropriate data; it is important to note that the specific steps may differ with each ticket
This process would be executed for staging (post-merge) and for production (post-release)

Similar to #854 #855 #856

@manasaV3 Sorry, I missed your question earlier.  How does this behave currently?

@manasaV3 Sorry, I missed your question earlier. How does this behave currently?

@richaagarwal It only returns the metrics on the repo currently associated to the plugin.

In cases where we have the repository updated for a specific plugin. Should the total_commits surfaced be a summation of the commits across both the repository or just the commits on the latest one? @neuromusic @richaagarwal

For posterity, this was discussed by the napari hub team on 5/15 and we have decided to maintain current behavior: only include the commits for the repository currently associated with the plugin.

Let's be sure to enable the feature flag in production once this is deployed next week


Customizable @media tag in scss (wanted for printing)

I'm trying to force lg styles for printing, and i'm not seeing an easy way to do that.
The reason i'm attempting to do this is mostly because chrome seems to always use the sm styles unless I change the scale in it's print preview and it's also a bit odd for the layout to change as the user changes the scale.
The only way i've been able to make it work so far is by manually editing the @media tags in the compiled bootstrap css. e.g., for sm/md/xl I changed @media (min-width: 576px) to @media screen and (min-width: 576px). Then for lg I changed @media (min-width: 992px) to @media screen and (min-width: 992px), print
I believe the proper way to change this would be to create a custom .scss file, however I don't see a way to edit the media tags the way I want. It looks like they are hard coded in this file: https://github.com/twbs/bootstrap/blob/v4-dev/scss/mixins/_breakpoints.scss
Some potential ways to add this feature:

Add scss variables that allow these media tags to be submitted as raw text.
Add scss variables that designate which styles have screen and/or print media tags.
Add a single scss variable that designates which grid size should be used for printing.

Add a single scss variable that designates which grid size should be used for printing.

This would be the path to take, but I'm unsure how to do it. Right now we just have a @media print { ... } for our selector.

We're likely going to remove the bulk of our custom print styles in v5—far too many issues with the sizing stuff I tried to do in v4. Closing this as a won't fix for now.


Chainer v5 requires CuPy v5

Jenkins, test this please.

Jenkins CI test (for commit c0c7bc93e5ba710d57099bf89b7801ba7565857a, target branch master) succeeded!


Remove ip_address_hash from std namespace

In similar vein to #1460  the ip_address_hash struct and specializations have been removed from polluting the std namespace.

After merging #1504, I force pushed an update to this branch.


AVStrans APE support

Find source code or
Implement from scratch

Code preprocessing
UI

woo! https://github.com/TomyLobo/eeltrans


precompiled

Hi, really nice work, Thanks
How to use the pre-compiled zip files?
Is it enough to copy the qtrb_v0.1.img to sd card and the run qmake for the programs on there?
Do you use QT Creator on Ubuntu or something with a remote toolchain?
I don't know how to get started with this.
Thank you very much!

Hello, thanks for your message.
Sorry for the poor documentation. This project is really experimental and I can't work as much as I want on this project.
I will try to write some documentation on the GitHub wiki page soon.

I put some documentation about how to use the pre-compiles zip files on the Wiki.
Check the page 1. How-to-install-a-release?

Wow, thanks for your work.
Can you run qtquick application with qml or just qwidget with it?
In my tests, only qwidget was working.
Error on compiling qtquick application: qtquick module not found.
The Configure output was the same as in your output. It says QtQuick: yes
On 21.03.2018, at 14:26, Guillaume Lazar <notifications<EMAIL_ADDRESS>wrote:
I put some documentation about how to use the pre-compiles zip files on the Wiki.
Check the page 1. How-to-install-a-release?https://github.com/GuillaumeLazar/qtrb/wiki/1.-How-to-install-a-release%3F
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/GuillaumeLazar/qtrb/issues/4#issuecomment-374935356, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AXJuOaL6EZTFIALrVCJ0i3yJlxlHD0Fcks5tglUKgaJpZM4SILmm.


Snapshot testing for string literals exhibits unexpected behaviour

🐛 Bug Report
The snapshot testing seem to render different snapshot for two different ways that would produce the same wrapper:

{this.props.whatever}{' for '}
{this.props.whatever}</strongr> for{' '}
In both cases, you would expect whitespace before and after for. However the snapshot for the above cases are different:
The first one produces:

          Dr Alan Yin

         for

        hospital admissions for

The second one produces:

          Dr Alan Yin

         for
        hospital admissions for

The difference is whether the whitespace after the first for will start on a new line.
To Reproduce
Steps to reproduce the behavior:

Set up a component that produce the above text snippet
Write a snapshot test for the component

Expected behavior
Both should produce the same snapshot, as writing it either way won't fail the actual test(for wrapper.text()). However the result shows that they produce different snapshots.
Link to repl or repo (highly encouraged)

Run npx envinfo --preset jest
Paste the results here:
    OS: macOS High Sierra 10.13.6
    CPU: x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
  Binaries:
    Node: 10.9.0 - /usr/local/bin/node
    npm: 6.2.0 - /usr/local/bin/npm
  npmPackages:
    jest: 21.2.1 => 21.2.1

How to you render and create the snapshot? Please include full example 🙂

@SimenB Hi Simen, thanks a lot for the prompt reply! After looking at it a few times, I started to realise that this is actually the desired feature.
e.g. <>{' for '}</> fundamentally should be different (in terms of code itself) to <> for{' '}, although they would both give the same text output.
I was just being ridiculous thinking this might be a bug or something. Please close this issue. Thank you!

You can close it yourself as well 🙂
And yeah, I think this is the desired behavior - we just serialize the tree. The fact that browsers collapse innerHTML to clean out whitespace in textContent is not something the serialization should care about.


add ViperC

Xcode template for VIPER Architecture written in Objective-C
Project URL
https://github.com/abdullahselek/ViperC
Description
ViperC creates modules for you when you want to use VIPER architecture in your projects
Why it should be included to awesome-ios (optional)
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Hey @abdullahselek thanks for contributing to awesome-ios. 😀


Updating env files on openai:install

This is more of a DX problem.
By the time I went to install openai, I had already renamed my .env to .env.local, additionally .env.example is already gone too.
Both of these situations lead to exceptions during openai:install:
file_get_contents(/app/.env): Failed to open stream: No such file or directory

file_get_contents(/app/.env.example): Failed to open stream: No such file or directory

Aren't you supposed to have an .env file before installing?

If you are using Laravel in a docker environment, it is advisable to rename .env to .env.local to avoid docker (compose) using the file to inject/interpolate those variables at container startup time.
Laravel supports environment specific files via .env.{environment-name}.
https://laravel.com/docs/11.x/configuration#additional-environment-files