text:
ci/cd: Automate versioning and releases

One possible solution:
name: Release and Deploy

on:
  push:
    branches:
      - main

jobs:
  release:
    runs-on: ubuntu-latest

    steps:
    - name: Checkout code
      uses: actions/checkout@v2

    - name: Setup Node.js
      uses: actions/setup-node@v2
      with:
        node-version: 14

    - name: Install dependencies
      run: npm ci

    - name: Bump version
      run: |
        # Bump the version in package.json
        npm version patch

    - name: Publish to npm
      run: |
        # Publish the package to npm
        npm publish

This action will run automatically when you push to the main branch. It will bump the version in package.json using npm version patch command, and then it will use npm publish to deploy the package to the npm registry.
Please make sure you have npm token as secret in your repository.

Another possible solution ( more control over versions ):
name: Release and Deploy

on:
  push:
    branches:
      - main

jobs:
  release:
    runs-on: ubuntu-latest
    env:
      VERSION_TYPE: ${{ env.VERSION_TYPE }}
    steps:
    - name: Checkout code
      uses: actions/checkout@v2
    - name: Setup Node.js
      uses: actions/setup-node@v2
      with:
        node-version: 14
    - name: Install dependencies
      run: npm ci
    - name: Bump version
      run: |
        # Bump the version in package.json
        if [ "${{ env.VERSION_TYPE }}" = "patch" ]; then
          npm version patch
        elif [ "${{ env.VERSION_TYPE }}" = "minor" ]; then
          npm version minor
        elif [ "${{ env.VERSION_TYPE }}" = "major" ]; then
          npm version major
        fi
    - name: Publish to npm
      run: |
        # Publish the package to npm
        npm publish

This action will run automatically when you push to the main branch. It will take the VERSION_TYPE from the environment variable and use npm version command to bump the version in package.json accordingly and then it will use npm publish to deploy the package to the npm registry. You can trigger the workflow with version type as minor, patch or major and it will bump the package version accordingly.
Please make sure you have npm token as secret in your repository.

repo: wise-introvert/deepsearchjs


text:
OSS Sync | Thu Dec 22 11:35:42 UTC 2022

#autorebase

source: gharchive/pull-request

repo: wix/greyhound

license: MIT

license_type: permissive

license_source: github-api


text:
autocomplete: evaluator documentation

changed to #411

repo: wix/quix


text:
Setitem

https://github.com/wix-private/velo-docs/pull/404
https://wix.monday.com/boards/892806647/pulses/3028938253

repo: wix/wix-code-docs


text:
fix: missing adv data cassandra-reaper

what is the diff with this one https://github.com/wolfi-dev/advisories/pull/4117 ?

Closing this PR! But we need to get these PRs merged or automatically assigned to us for a review.

repo: wolfi-dev/advisories


text:
Can I rent a GPU from a cloud server vendor to run it?

314b param, 16bit per float, "a" gpu ?

you need a cluster of gpus

Please move to close this issue and move to:
https://github.com/xai-org/grok-1/discussions
Reason:
https://github.com/xai-org/grok-1/issues/69

source: gharchive/issue

authors: helloyangy rudyrdx trholding yuhanchen0311


text:
Create FAWA_Fast_Adversarial_Watermark_Attack

👷 Deploy Preview for songxia processing.
🔨 Explore the source changes: be3ece1c2025e43b4cb5a02c5ae5a0fdea729771
🔍 Inspect the deploy log: https://app.netlify.com/sites/songxia/deploys/612c9d335b02a20007651e09

ww

repo: xiasongnihao/starter-hugo-academic


text:
请问Real-ESRGAN/options/finetune_realesrgan_x4plus_pairdata.yml配置文件中的gt_size是指什么的尺寸?

gt = ground truth

网络输入的大小

在这个项目中，gt_size可以理解为处理的高分辨率图片的分辨率吗？如果训练的图片分辨率大于gt_size，那么训练时会把一个图片拆分为多个长宽均为gt_size的图片，分多次读入进行训练？

authors: ffssea jorjiang sunjian2015 tumuyan

repo: xinntao/Real-ESRGAN


text:
Dispatch jobs of different architectures onto matching machines.

Supr supersedes this

authors: tdaede vibhoothi


text:
chore: fix typo in the title

I'm sorry, I forgot to update the README.zh.md.

I'm sorry, I forgot to update the README.zh.md.

Oh I'm sorry, I just saw this reply now...
It's okay. You reminded me :)

authors: liby xlboy

repo: xlboy/ts-type-hidden


text:
请问代码中的关系超图注意力是只使用了一层吗？可以改为多层注意力吗？

你好，
是的，我们的代码里使用了单层的。你可以通过修改超参数把它改为多层使用。

请问是修改哪一个超参呢？您测试过不同层的效果吗？单层的效果是最好的吗？

可以修改该行的超参数：https://github.com/xlxwalex/HyCxG/blob/712c85c99ea073886196d7791a3b0c13379fd946/HyCxG/config.py#L30
我没有对每个任务做过对比，不过在ABSA上基本上单层性能要更好。因为我们在取cxs的时候有一步离线的选择优化，因此单层的就足够了。如果你不需要/没有使用启发式搜索这步的话，可以增加层数应该会比较有效。

好的，感谢解答！

客气啦：）

authors: Allan-waker xlxwalex

repo: xlxwalex/HyCxG


text:
Fix save to be out of the lua loop

Fixes #559

The error comes from the fact that save calls history.get, which then calls vim.nvim_buf_get_name which needs to be scheduled.

I'm not sure why delaying safe a few milliseconds will be a problem tho.

Hi @aarnphm can you please help me with this?

Looks like this proposed fix is the way it was suggested in this other closed issue on plenary repo.

This fix looks fine.

Can this get merged then? It's currently blocking me from using a local LLM.


text:
Bump YBM CLI to 0.1.9

@kc-yb

Yes, the releases view here contains all the info: https://github.com/yugabyte/ybm-cli/releases (and users can compare revisions)
Yes, the CLI will periodically (once per day) check GitHub if there is a new release and prompt the users to update.
Yes, but it also feels like we would duplicate all this information from the GitHub repo. While we can automate this, it has not been a priority so far.

@cdavid This is great. Thanks for the clarifications.
Re (3) - can we add a link in the documentation page to these release versions? Please ignore if the link already exists.

Re (2) - just wanted to check that we don't do that for json output format. This might break scripting

authors: cdavid kc-yb

repo: yugabyte/homebrew-tap


text:
fix paths for Windows

Thanks, with some adjustment I'll accept it.

authors: tigrazone yuphin

repo: yuphin/Lumen


text:
如何将渲染好的动画导出成mp4文件

能否在EvaAnimPlayer里增加导出播放的视频？

repo: yylive/YYEVA-Android


text:
More JSystem borrowing

Are the inlines that you added part of debug? I know some of the repositories have some inlines that aren't actually there.

Some do. Haven't verified all of them.
On Sat, Jul 22, 2023, 19:36 jdflyer @.***> wrote:

Are the inlines that you added part of debug? I know some of the
repositories have some inlines that aren't actually there.
—
Reply to this email directly, view it on GitHub
https://github.com/zeldaret/tp/pull/383#issuecomment-1646625936, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYQXXNB4A6VBRF2TJBROZLXRP6QDANCNFSM6AAAAAA2T4ID7U
.
You are receiving this because you authored the thread.Message ID:
@.***>

repo: zeldaret/tp


text:
Deprecate Only top bar in compact

Just nuke it 🤣

repo: zen-browser/theme-store


text:
no port setting :(

fixed in #14
please, use 0.3.2 version

thank you!

fixed in #14 please, use 0.3.2 version

tank you

authors: Advencher zifter

repo: zifter/clickhouse-migrations


text:
updated CI to sync with zingomobile

Yes it is designed to fail on cache miss which triggers the build job ☺
On Thu, 20 Apr 2023, 11:40 Gygaxis Vainhardt, @.***>
wrote:

@.**** commented on this pull request.
In .github/workflows/ci.yaml
https://github.com/zingolabs/zingolib/pull/313#discussion_r1172848624:

   abi: [ x86, x86_64, armeabi-v7a, arm64-v8a ]

continue-on-error: true
steps:

 - name: Checkout zingo-mobile

   uses: ***@***.***

   with:

     repository: zingolabs/zingo-mobile

 - name: Check if native rust cache exists

   id: check-build-cache

   uses: ***@***.***

   with:

     path: android/app/src/main/jniLibs/${{ matrix.abi }}

     key: native-rust-${{ matrix.abi }}-${{ env.CACHE-KEY }}

     lookup-only: true

     fail-on-cache-miss: true

This seems to be causing the integration test jobs to also fail due to the
cache miss...is this intended?
—
Reply to this email directly, view it on GitHub
https://github.com/zingolabs/zingolib/pull/313#pullrequestreview-1394390816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2CCHYQ2FCOYURAONXSJBLLXCFRIHANCNFSM6AAAAAAXE24Y7Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

repo: zingolabs/zingolib


text:
add PrimeField::char method

Isn't this the sort of value you don't want to allow to "escape" into the public API because technically it's invalid? (i.e. field elements are exclusive of the modulus)

Yeah, though note that this is returning a PrimeField::Repr which is a byte encoding, so while that is technically a type error (as the characteristic can never be a field element representation), it isn't as bad as returning a PrimeField instance.
We also already expose the modulus via PrimeFieldBits::char_le_bits, but the only place I'm aware of that being used is inside bellman's boolean gadget, and there only so we can drop the leading zeroes in the bit representation of the field element (to handle cases where the bit representation is larger than PrimeField::NUM_BITS).
I am currently -1 on merging another way to expose the modulus without having a use case.

In a discussion with @ebfull, we decided that we would not merge this PR as-is, because PrimeField::Repr is semantically intended to be a field element representative which the modulus will never be. Separately, we are going to add a const MODULUS: &'static str associated constant to PrimeField for debugging purposes, but that is treated as opaque (so if you are using a particular field concretely then you could parse it to obtain the modulus, but in generic code you won't know its encoding).

authors: bchyl str4d tarcieri

repo: zkcrypto/ff


text:
Unity toolbar setting is not customized after installation

This is very trivial and shouldn't be confusing even when done manually. So I set wontfix.

license_source: bigquery


text:
linux-generic-stable 4.15

cherry-picked @mrchapp changes

authors: fboudra roxell

license: mit


text:
[WIP]Check parameters in contracts

:x: Build AElf 1.0.0.3747 failed (commit https://github.com/AElfProject/AElf/commit/0857095e66 by @xiangxingxing)

:white_check_mark: Build AElf 1.0.0.3753 completed (commit https://github.com/AElfProject/AElf/commit/2d6b8c0d54 by @xiangxingxing)

:white_check_mark: Build AElf 1.0.0.3757 completed (commit https://github.com/AElfProject/AElf/commit/01b874fc95 by @xiangxingxing)

:white_check_mark: Build AElf 1.0.0.3774 completed (commit https://github.com/AElfProject/AElf/commit/fefa6d0bb6 by @xiangxingxing)

:x: Build AElf 1.0.0.4443 failed (commit https://github.com/AElfProject/AElf/commit/feab24b9b7 by @xiangxingxing)

authors: AppVeyorBot xiangxingxing

repo: AElfProject/AElf


text:
Implement GUI Attendance header and update Calendar command

lgtm

authors: CranstonYeo suwoons


text:
(#141) Removed duplicate check before adding an item to the list

Oh, I didn't notice this includes my last change. I will create new PR.

repo: AdamRamberg/unity-atoms


text:
Add alluxio-common.sh to tarball

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6238/
Test PASSed.

alluxio-bot, merge this please

authors: AmplabJenkins Xenorith ZacBlanco

repo: Alluxio/alluxio


text:
[DOCFIX]docfix for docs/cn/Running-Hadoop-MapReduce-on-Alluxio.md

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16345/
Test PASSed.

authors: AmplabJenkins ParanoiaW


text:
Use Swagger to generate rest docs

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3851/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3855/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3856/
Test FAILed.

jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3859/
Test FAILed.

jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3870/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3919/
Test FAILed.

jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3933/
Test FAILed.

jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3934/
Test FAILed.

jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3937/
Test FAILed.

jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3938/
Test PASSed.

oh great it finally passed @ZacBlanco

@Xenorith This will only generate docs for the nondeprecated endpoints, but I think that is probably better.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3961/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3962/
Test FAILed.

Jenkins, test this please.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3964/
Test FAILed.

@Xenorith seems like the test failure is similar to the previous one that was flaking. I will merge this since the follow up changes are mostly formatting related.

alluxio-bot, merge this please.

authors: AmplabJenkins Xenorith ZacBlanco calvinjia


text:
Resolve issue #3170

Thanks @slozier.  Can you add a test?
@bagnell can you review this?

@pjcozzi Done.

@bagnell can you review this?

@slozier This looks good. Can you merge in master? Thanks!

@bagnell Done.

authors: bagnell pjcozzi slozier

repo: AnalyticalGraphicsInc/cesium


text:
Workaround for truncated text issue on ListView

Can you please show a screenshot of the issue or something?

Hi !,
I think I've just realised when it fails.
This is when you define the setMinTextSize() by XML, this is so because I
have a CustomTextView class that extends of your AutoFitTextView, and I
define custom attrs, such as 'customMinTextSize', then I call to
setMinTextSize()  within my CustomTextView class. If I remove
'customMinTextSize' attr from XML it works fine.
In the screeshots, the wrong one has the 'customMinTextSize' attr set in
XML for the first textview. The second textview has no 'customMinTextSize'
attr in neither of the screenshots
good
.[image: Imágenes integradas 2]
wrong
[image: Imágenes integradas 1]
Regards!
2015-02-26 17:55 GMT+01:00 AndroidDeveloperLB notifications@github.com:

Can you please show a screenshot of the issue or something?
—
Reply to this email directly or view it on GitHub
https://github.com/AndroidDeveloperLB/AutoFitTextView/pull/14#issuecomment-76216534
.

I don't see the images.

Here are images, sorry ;)
wrong

good

can you please make a sample project to show this? I never noticed a truncated text before.

Sorry, I've tried to make a sample but it works perfectly (unfortunately ;)).
In my project, where this fails, the above images are a header (injected with  tag) within an item layout of a ListView, and when the app starts the headers are ok, but when scrolling the listview they are become wrong, and the others layouts where I use the same header are displayed wrong.
Maybe this is a ghost bug, but it solved my issue.
Anyway my solution is use post() to wait the view is drawed.
Regards!

I'm not sure if I should merge this pull request.
Is this the only way to solve it?
Is it the best way?
Would it still work on normal scenarios?

Ok, if I find out anything, I'll keep you informed.

ok.
On Thu, Feb 26, 2015 at 11:38 PM, miguelbcr notifications@github.com
wrote:

Ok, if I find out anything, I'll keep you informed.
—
Reply to this email directly or view it on GitHub
https://github.com/AndroidDeveloperLB/AutoFitTextView/pull/14#issuecomment-76279477
.

I was able to reproduce the bug.
You can see the sample app here :
https://github.com/miguelbcr/AutoFitTextView/tree/master/sampleTruncated
search for 'FIXME' in files and comment/uncomment the blocks or lines of code and observe the textview's on the listview how they are truncated

I've got the sample, but I don't see truncated text when running "sampleTruncated" :

I see you didn't change the code there, as there is the original code un-commented, and your new code being commented:

Yes I left the original code to see the bug, and then you can alternate between one code and the other one to see the behaviour.
Here is my bug, but it is when you do scroll, and not of all fails, only some list items

Ohhh.... It's so subtle and tiny that I didn't notice.
So you think I should merge it?
Is this the only way to solve it?
Is it the best way?
Would it still work on normal scenarios?

I dont know if it is the best way to solve it or if you should merge it, but I spent a lot of time with this behaviour and at the end I found that workaround, and also I don't know if this is a good code or simply a shit, because Im aN average programmer, but this did that avoid to use another library, because I like yours.

ok, you've convinced me. I will now merge it.
Thank you for your contribution for the library.

Thank you for your library ;)

ummmm... I think I've merged the new sample too somehow.

This is the first time I collaborate on github and I'm not an expertise with Git, so I committed the sample code because I didn't know how upload it for you could see it, but you have freedom to delete or change whatever you want, I don't mind, because the bug fixing comment , maybe, is not appropriate either.

That's what I did.
I've never done what you did, but I have written the code in the post
instead. How do you do it?
On Sat, Feb 28, 2015 at 4:21 PM, miguelbcr notifications@github.com wrote:

This is the first time I collaborate on github and I'm not an expertise
with Git, so I committed the sample code because I didn't know how upload
it for you could see it, but you have freedom to delete or change whatever
you want, I don't mind, because the bug fixing comment , maybe, is not
appropriate either.
—
Reply to this email directly or view it on GitHub
https://github.com/AndroidDeveloperLB/AutoFitTextView/pull/14#issuecomment-76527879
.

I don't know what are you referring with 'How do you do it?', but I've changed the title of my pull request. All this is new for me, forks, pull request, ... so don't ask me complex things,... by the moment... ;)

But this is it. I never done such a thing as pull-request.
What are the steps till you've shown me to merge the code? Did you fork it perhaps?

Yes, I click on Fork (top right icon), and then I clone the repository (my fork) and modified the AutoResizeTextView.java, and then I commited my changes into my fork and pushed it. Now on github I cliked on 'pull request' link (top right menu) and  'create a pull request' link (inside the box). Then you can see my pull request, with the change to merge.
But when you ask me for a sample code, I did it on my fork, so when I pushed it, seems that it was added automatically on the previous pull request. Maybe I should have done another fork to avoid mix the workaround and the sample in the same pull request.

Nice. Thank you. Maybe I will try it next time.

@miguelbcr The code of "post(...)" seems to cause issues on Android 5.x . I will now remove this code till there is a better way to solve this.

ok
El 03/06/2015 23:05, "AndroidDeveloperLB" notifications@github.com
escribió:

@miguelbcr https://github.com/miguelbcr The code of "post(...)" seems
to cause issues on Android 5.x . I will now remove this code till there is
a better way to solve this.
—
Reply to this email directly or view it on GitHub
https://github.com/AndroidDeveloperLB/AutoFitTextView/pull/14#issuecomment-108628597
.

@miguelbcr If you find a way to fix it for all to use (original post here: https://github.com/AndroidDeveloperLB/AutoFitTextView/issues/19 ) , please let me know.

authors: AndroidDeveloperLB miguelbcr

repo: AndroidDeveloperLB/AutoFitTextView


text:
Remove unused app_id parameters

https://ocd.appscale.com:8080/job/Daily Build/2809/

repo: AppScale/appscale


text:
[HO-44] Complete user registration with passed all definition of done

Пацаны и пацанессы, надо закончить эту юзерстори

repo: ArtemTereshkovich/HostOcean


text:
Add editor bind, add global timeout for spec

Pull Request Test Coverage Report for Build 102

20 of 21 (95.24%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 82.129%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/editor/editor.component.js
12
13
92.31%

Totals

Change from base Build 101:
0.05%

Covered Lines:
2561

Relevant Lines:
2924

💛  - Coveralls

authors: coveralls korosakikun

repo: Atlantis-Software/atlantis-ui


text:
Add divider for link title field

There seems to be more going on in here than just adding a divider.

authors: matt-sm maxious

repo: AusDTO/dto-digitalmarketplace-frontend


text:
Add U2I and user history API

Hi @mikaelsitruk, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (mikaels). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Author approved.

authors: azurecla mikaelsitruk rmca14

repo: Azure/azure-content


text:
11/29 PM Publish

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azurermps-6.13.0/uninstall-azurerm-ps.md
:white_check_mark:Succeeded
View (azurermps-6.13.0)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

authors: VSC-Service-Account huypub

repo: Azure/azure-docs-powershell


text:
Communication - Phone Numbers - Corrected LRO status

/azp run python - communication - tests

/azp run python - communication - tests

/azp run python - communication - tests

repo: Azure/azure-sdk-for-python


text:
[Storage]fix retry on large block upload

Just to confirm this fix is related to https://github.com/Azure/azure-sdk-for-python/pull/17078/files?

@tasherif-msft good suggestion! Also I will make this pr into two since these two commits are not related, then I will quote your description there

authors: tasherif-msft xiafu-msft


text:
Updating package references (upgrading/consolidating)

@davidebbo and @mathewc, can you please take a look at this? A few package updates:

Consolidate package references across projects
Match dependencies taken by the extensions

@fabiocav, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

Closing this as I'm reverting the changes that are causing the issue.

authors: dnfclas fabiocav

repo: Azure/azure-webjobs-sdk-script


text:
Change & check config filename from ENV

cf #115

I think this PR changes that ENV must override settings from a config file. Please see #161.
I've just added a test to check this behaviour.

repo: Bailador/Bailador


text:
Develop

major update, new features:
W2S, etc.

repo: BookOps-CAT/overload


text:
08-31-2017 Deploy

👍

authors: rubinsingh yntema

repo: BranchMetrics/web-branch-deep-linking


text:
Ignore invalid certificate common name when checkSsl disabled

Coverage remained the same at 100.0% when pulling e88832ed102af06a9b2444ead2def0c0b6706fe6 on richardjennings:feature/disable-ssl-checks into 20b6bc8b9bb0295f072fe1e11550b0c0ea581c6e on Brunty:feature/disable-ssl-checks.

Coverage remained the same at 100.0% when pulling e88832ed102af06a9b2444ead2def0c0b6706fe6 on richardjennings:feature/disable-ssl-checks into 20b6bc8b9bb0295f072fe1e11550b0c0ea581c6e on Brunty:feature/disable-ssl-checks.

@richardjennings you're ace, thanks for this! 👍

authors: Brunty coveralls richardjennings

repo: Brunty/cigar


text:
Can users edit their own names?

I think we should mark this as enhancement. Would require an account settings area.

Just to clarify, the things I've marked as "questions" are things that aren't specified in the user stories and need clarification from a TA or Abram.  This is just a way to get some team input before asking officially.
Things currently marked as "enhancements" are known requirements/use cases.  It's probably a bad tag name, so I want the planning team to weigh in on how issues, issue tags, and milestones are used. @kuzi117 , @TheLastBanana , can you let us know when you get a chance?

I think it's reasonable to keep known requirements and potential requirements separate. Once we know for sure that it's needed, we can mark it as an enhancement.

Agree with Ryan in that this is another enhancement, but in regards to how to answer this question, I feel like we've already answered this question in Slack chat.
If (for now, until possible spec changes) we're modeling a user as a just a wrapper for a string, no UUID or special auth, then changing your name is just a simple as backing up to the root of the activity stack and logging in with a different name.
Now if we're talking about changing current items in the database whose names are the same as the current logged in user to be attached to a different user name then it's another issue entirely and I don't think it should be allowed. (E.G. a user Bill has some number of database items (tags/claims/etc.) attached to his name, Fred similarly has some number of items. Fred changes his name to Bill and then back to Fred. Does that change his items to be named Fred, and then include Fred's items to be switched back to Bill?)

I feel like this question has been resolved:

Users log in with whatever name
We treat that as their unique user ID
We hide that beneath a User model object, which we can extend with a password hash, non-unique first and last names, etc

So for current requirements, if we already have a "Bob" and another Bob wants to play the claim game, then he logs in as "Bob2" or something.  If requirements change later, we can allow them to both change their name to bob, but leave their IDs as Bob and Bob2.
If there are no complaints, this issue can probably be closed.

Yeah, that sounds good to me.


text:
Features/tests for coverage

Coverage remained the same at 88.456% when pulling 224fda6060a19acd01b1707836410c20972eb385 on features/tests_for_coverage into e3eead3a1ed0a859b7b87656937c367cdfbe74d4 on master_V0.5.

Coverage increased (+1.4%) to 89.855% when pulling c1d5748d72b95b2d7b82123fcaaf8d380aa832c4 on features/tests_for_coverage into e3eead3a1ed0a859b7b87656937c367cdfbe74d4 on master_V0.5.

90% 🎉 🎉

Coverage increased (+1.9%) to 90.355% when pulling 041c82956e34a9f7266d6c270ae85337a08ef268 on features/tests_for_coverage into e3eead3a1ed0a859b7b87656937c367cdfbe74d4 on master_V0.5.

authors: coveralls huanhock jjingrong


text:
Update About us

Coverage remained the same at 92.67% when pulling 61ecfcc1ff99c2b3d7a54964a6fe2de38f845e44 on Edit-about-us into 212e8032be38194f0b59e981b76e2c396b2bfd73 on master.

Coverage remained the same at 92.67% when pulling b1782b3de3187d6c5263269e42a3583c73d18cea on Edit-about-us into 212e8032be38194f0b59e981b76e2c396b2bfd73 on master.

Coverage remained the same at 92.67% when pulling 79eacf999904d23a3748e28a54b00ee9206e27fc on Edit-about-us into 212e8032be38194f0b59e981b76e2c396b2bfd73 on master.

authors: Fyelight coveralls


text:
pull test

Coverage remained the same at 89.093% when pulling 66219b517eeba9875c2a66bb96c5622ad005f08d on user_guide into b3b6a340a1e32442b408f86c57439b42504dc29d on V0.0_mattheus_pull_test.

authors: coveralls mattheuslee


text:
Add automatic sort function in the background to display the tasks in either chronological order or prioirty order.

feature implemented #147

authors: Li-Shicheng chishien


text:
V0.24.3

Not showing but passed: https://travis-ci.org/github/CamDavidsonPilon/lifelines/builds/665837913?utm_medium=notification&utm_source=github_status

repo: CamDavidsonPilon/lifelines


text:
title background-color (#F5F5F5)

Hi @sbouchy by title background-color did you mean the  with id="header"?

Title is div.object div.name (i.e. title of an entry in the response, in js notation).
#207 proposes to fix that.

authors: Adijav TeXitoi sbouchy

repo: CanalTP/navitia-playground


text:
imports synchronization without a log

💚 Acceptance. Tried importing a sync without log both in master and in this branch, failing in the first case :)

authors: AleGoiko amartinj

repo: CartoDB/cartodb


text:
NO-TICKET: update handling of CL_EVENT_MAX_MICROSECS env var

bors r+

repo: CasperLabs/casper-node


text:
Adaptation of plot_metagene to strand col from table

This commit not deal completly with the changes because I still have to adapt the non boolean nature of pruning_mode to the code. I did not notice that before, a second commit will come.
Change force_seqlevels into pruning_mode in metagene.R and bam_handler.R

repo: CharlesJB/metagene


text:
month should be initialized with the first day of the month

Worthwhile change.
Are you seeing this actually break something? The only places month gets used are to retrieve the actual month, so it shouldn't really matter.

@ChiperSoft Actually the users of our system found this bug.
The next month button was getting disabled on 'today-past' mode even though it still has one month ahead.

Ah, I think somebody had reported that bug a long time ago but I couldn't reproduce it.
Thank you!

0.6.1 is published with this fix.

authors: ChiperSoft IlanFrumer

repo: ChiperSoft/Kalendae


text:
fixed sonar violation

Coverage remained the same at 100.0% when pulling 895fdd97137493da78ec40ea8424550d0863c4a8 on lamora:compaction-sonar-fix into 2353fc766799e41e34e15f79cacc10be378ecc33 on ChronixDB:master.

Coverage remained the same at 100.0% when pulling 895fdd97137493da78ec40ea8424550d0863c4a8 on lamora:compaction-sonar-fix into 2353fc766799e41e34e15f79cacc10be378ecc33 on ChronixDB:master.

Coverage remained the same at 100.0% when pulling 895fdd97137493da78ec40ea8424550d0863c4a8 on lamora:compaction-sonar-fix into 2353fc766799e41e34e15f79cacc10be378ecc33 on ChronixDB:master.

authors: coveralls lamora


text:
VM: Add basic vm

Codecov Report

Merging #166 into dev will decrease coverage by 3.91%.
The diff coverage is 34.66%.

@@            Coverage Diff            @@
##              dev    #166      +/-   ##
=========================================
- Coverage   56.82%   52.9%   -3.92%
=========================================
  Files          58      76      +18
  Lines        2096    2546     +450
=========================================
+ Hits         1191    1347     +156
- Misses        818    1085     +267
- Partials       87     114      +27

Impacted Files
Coverage Δ

pkg/vm/stack/builder.go
0% <0%> (ø)

pkg/vm/stack/boolean.go
0% <0%> (ø)

pkg/vm/stack/invocationstack.go
0% <0%> (ø)

pkg/vm/stack/instruction.go
0% <0%> (ø)

pkg/vm/stack/array.go
0% <0%> (ø)

pkg/vm/stack/context.go
0% <0%> (ø)

pkg/vm/vm_ops.go
100% <100%> (ø)

pkg/vm/stack/stackitem.go
20% <20%> (ø)

pkg/vm/vm_ops_exceptions.go
40% <40%> (ø)

pkg/vm/stack/bytearray.go
50% <50%> (ø)

... and 26 more

Continue to review full report at Codecov.

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

Award decentralizedkev 1000 points

https://neoscan.io/transaction/81db58e8e3fcae21d4d614c008935de2fcb2d53bdf05ce5b4a40e13c3a110314

authors: codecov-io decentralisedkev hal0x2328 lllwvlvwlll

repo: CityOfZion/neo-go


text:
Fix lever toggles

When testing this locally, ensure to test across restarts too (setting the state should persist over restart)

Not ready yet, need a day or two until can come back to look at how to better save the togglelever across restarts

Ready for review

I think I had an issue on my local test server where snitches wouldnt persist across restarts but it was resolved when using the devoted test server, tested these and they work as intended

repo: CivClassic/JukeAlert


text:
Use mapit for geolocation and shapes in downloads

@xybrnet

:+1:

authors: longhotsummer xybrnet


text:
Convert hard coded routes to the routes name #588

This has been fixed in #656

repo: ColoredCow/employee-portal


text:
Create logB2

confirmed:B2

confirmed:B2

authors: mrdaddyru supermario


text:
Clicking "continue" from interactive tutorial creates pop-up warning about leaving the page

Which scenario do you see this on?

All of them.  Steps to reproduce:
https://containersolutions.github.io/kubernetes-bootcamp/1-2.html
On a Chrome browser:

Go to the interactive tutorial
Click minikube version
Click Module 1 quiz
Pop comes up asking if you want to leave the page

Also, after clicking this, I get a page where my only action is to click 'begin'.  I would expect to be taken straight into the quiz.

@craigbox that's the agreed workflow/design: that you shouldn't jump directly into the quiz, but have an intermediate screen.

@pwittrock This is by design. It's to stop users mid-way from accidentally closing the tab. I'll let @jocatalin decide if it should be disabled or not.

@pwittrock re. the jumping into the quiz - what purpose is the intermediate screen supposed to serve?  It could be enhanced by adding some text and/or having a "Skip" button?
(I was further surprised there was only one question in the quiz)

Looks like if you move past the last step (click the arrow after "Step X of X") to the "Congrats" screen, you don't get the popup.
Is there a way to add a "Continue" button to the last step that moves to the "Congrats" screen? This could solve this issue, however #22 would be a bigger issue

@craigbox I created a separate issue for your comment #25

There's no longer a quiz.
/close

authors: BenHall craigbox jeffmendoza jocatalin pwittrock

repo: ContainerSolutions/kubernetes-bootcamp


text:
API Bundle::GetProperties is deprecated, but it's not marked US_DEPRECATED

Merged with #278 .

authors: ksubramz saschazelzer

repo: CppMicroServices/CppMicroServices


text:
Test creation:bcf.py: get_bymac #324

Codecov Report

Merging #325 into master will increase coverage by 0.79%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #325      +/-   ##
==========================================
+ Coverage   84.35%   85.14%   +0.79%
==========================================
  Files          22       22
  Lines        1304     1313       +9
  Branches       91       91
==========================================
+ Hits         1100     1118      +18
+ Misses        178      169       -9
  Partials       26       26

Impacted Files
Coverage Δ

...thBoundControllerAbstraction/proxy/bcf/test_bcf.py
99.2% <100%> (+0.12%)
:arrow_up:

...bstraction/test_NorthBoundControllerAbstraction.py
96.05% <0%> (-0.2%)
:arrow_down:

...r/NorthBoundControllerAbstraction/proxy/bcf/bcf.py
67.07% <0%> (+5.48%)
:arrow_up:

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 e28c1f5...9c0daf7. Read the comment docs.

authors: codecov-io d-grossman

repo: CyberReboot/poseidon


text:
Semi-automatically convert libmscoff and scanmscoff to D

Now passing.

Auto-merge toggled on

authors: MartinNowak yebblies

repo: D-Programming-Language/dmd


text:
ose4g assignment done

m

m

repo: DSC-Unilag/HTML-Study-Group


text:
JCF: Issue #20: mark the level of each package's documentation

The idea of this PR is to let DUNE DAQ software developers/users know what documentation is up-to-date, and what documentation isn't.

This Issue didn't get sufficient enthusiasm, so I'm closing it.

repo: DUNE-DAQ/docs


text:
Replace galaxy with lens galaxy

We are doing this in the sprinkler here.

Good! Your code reminds me that
newlens['REFF'] = 1.0 # Hard coded for now. See issue in OM10 GitHub.

I'll raise this here too so I don't forget to fix this before the summer.
On Thu, Feb 11, 2016 at 3:53 PM, Bryce Kalmbach notifications@github.com
wrote:

Closed #57
https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/57.
—
Reply to this email directly or view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/57#event-547930002
.

It would be good to check this on a few images.  When I was looking around at the images I found a few quasar images on whopping bright galaxies.  Of course, it could just be coincidence.

Or realistic? The typical lens galaxy should be around m=19-20, z=0.5, I
think.
On Fri, Feb 12, 2016 at 9:12 AM, SimonKrughoff notifications@github.com
wrote:

It would be good to check this on a few images. When I was looking around
at the images I found a few quasar images on whopping bright galaxies. Of
course, it could just be coincidence.
—
Reply to this email directly or view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/57#issuecomment-183417030
.

O.K.  That's pretty bright.  I guess we should just do the plots you suggested yesterday and compare to what's coming out in the images.

Yeah - actually we want the lens galaxy visible, that's one of the things
that will make the LSST lens systems stand out from the crowd. When the
quasar and lens brightness is comparable, you get a much better outlier in
catalog space.
On Fri, Feb 12, 2016 at 1:34 PM, SimonKrughoff notifications@github.com
wrote:

O.K. That's pretty bright. I guess we should just do the plots you
suggested yesterday and compare to what's coming out in the images.
—
Reply to this email directly or view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/57#issuecomment-183496386
.

authors: SimonKrughoff drphilmarshall jbkalmbach

repo: DarkEnergyScienceCollaboration/Twinkles


text:
Divide Ballocks Cove into tides

done

repo: DevJackSmith/mh-map-helper


text:
patch 1 Create Palindrom.py

Too simple code


text:
how do I link containers through the gui?

@VisualBean DockStation works with projects based on Docker Compose and all containers from the same project links between themselves by default.
If you usually work with Docker via docker run ... you have 3 ways

If you know Docker Compose you can manually create config file (by default all containers will be link between themselves from compose v2).
You can create project via Parser

You can create project via Scheme

@VisualBean Is the issue still relevant?

Great!  - the reason I was asking, was because I was trying to figure out how to link a mysql container with a wordpress container -
But for that I think i need to use docker compose - is this correct?

@VisualBean
If you wanna use DockStation all your containers will be linked by default.
If you work with Docker via terminal you should use --link option.
Also you can check my Docker WP config.
https://github.com/igor-lemon/docker_wordpress_stacksight

Hi! :)
Can i add my 5 cents to your discussion?
If you are using User Defined Network you shoud not need to use link. All containers will resolves by name or network alias using Embedded DNS.
Links uses in Docker's default bridge network.
So if you use docker-compose, it creates UDN for your project containers by default. :)
And DockStation use docker-compose. :)

authors: VisualBean bit0rez igor-lemon

repo: DockStation/dockstation


text:
Update README

Also update precedence.md to include . (getter/setter).

repo: DylanSp/wheel-lang


text:
Req testes aceitaçao

Doc sem validação necessária- Merged

authors: jessicamegane jmgsoares


text:
Add MODX

Closed in favor of https://github.com/EagerIO/EmbedBox/projects/1#card-96256

repo: EagerIO/EmbedBox


text:
Develop to main

this should be on mm now

repo: EscolaLMS/Categories


text:
Pre 100.6.0 release README update

Links won't work until Wiki has been updated.

repo: Esri/arcgis-runtime-toolkit-android


text:
翻譯 練習\initial

check the item

repo: EvanYP/NewTest


text:
Updates

❤ @Exelord

authors: Exelord PoslinskiNet

repo: Exelord/Monarchy


text:
Added image text extraction (OCR) extensions

Just an idea, what if we can write to RTDB or Firestore as another option?

Just an idea, what if we can write to RTDB or Firestore as another option?

Just an idea, what if we can write to RTDB or Firestore as another option?

Agreed, same for #8. Some thoughts on the options:

Support text file in Storage only (keep it as-is)

Pros: No additional permissions required, doesn't assume developer uses another Firebase product
Cons: Developer has to write their own code to download text file and parse it, slower than reading from DB

Support RTDB only, or Firestore only

Pros: Simpler implementation,
Cons: Only works with a single DB, doesn't work for developers that don't use that DB, need to add additional permissions to Extension to allow it to write to a DB

Support RTDB, Firestore, and writing to a text file in Storage (settable via param)

Pros: Works great for developers that use RTDB and Firestore, and is fine even for those that don't use a Firebase DB
Cons: More complex implementation, extension would require permission for multiple products (even if a developer doesn't use all of them)

I lean toward the second two options, but the first one works too! It's up to you @pavelgj.

Just an idea, what if we can write to RTDB or Firestore as another option?

Agreed, same for #8. Some thoughts on the options:

Support text file in Storage only (keep it as-is)

Pros: No additional permissions required, doesn't assume developer uses another Firebase product
Cons: Developer has to write their own code to download text file and parse it, slower than reading from DB

Support RTDB only, or Firestore only

Pros: Simpler implementation,
Cons: Only works with a single DB, doesn't work for developers that don't use that DB, need to add additional permissions to Extension to allow it to write to a DB

Support RTDB, Firestore, and writing to a text file in Storage (settable via param)

Pros: Works great for developers that use RTDB and Firestore, and is fine even for those that don't use a Firebase DB
Cons: More complex implementation, extension would require permission for multiple products (even if a developer doesn't use all of them)

I lean toward the second two options, but the first one works too! It's up to you @pavelgj.

My vote would be for (2) with Firestore as the only option (for now). If developers are installing an extension to OCR a file, chances are they want to have the content of that file more readily accessible than re-downloading the file would make it.
Separate note: we should really figure out how to have "variants" of an extension (e.g. a Firestore and RTDB version of this one).

My vote would be for (2) with Firestore as the only option (for now). If developers are installing an extension to OCR a file, chances are they want to have the content of that file more readily accessible than re-downloading the file would make it.
Separate note: we should really figure out how to have "variants" of an extension (e.g. a Firestore and RTDB version of this one).

Thanks @pavelgj! Can you please add docs in the form of PREINSTALL.md and POSTINSTALL.md files? Here are some samples: preinstall, postinstall, dynamic links extension

Done.

Thanks @pavelgj! Can you please add docs in the form of PREINSTALL.md and POSTINSTALL.md files? Here are some samples: preinstall, postinstall, dynamic links extension

Done.

Updated the extension to write extracted text to Firestore.

Updated the extension to write extracted text to Firestore.

authors: elvisun jhuleatt mbleigh pavelgj


text:
Add composer-require-checker to static analysis checks

This is likely blocked by https://github.com/maglnet/ComposerRequireChecker/pull/201 or an equivalent change, at least to keep the phpunit/php8 matrix happy.
The actual static analysis check this adds is somewhat expected to fail due to the tool (quite reasonably) erroring if no symbols are found. Ideally this would be done by adding a dummy file, but I'm not sure if there's a way to keep that dummy file out of projects that use this template.

repo: Firehed/php-library-template