aligning the page layout and making it responsive and removing hte need of horizontal scrollbar

pls assign me this issue as i am interested in contributing towards this project by enhancing the ui and improving the css
issue example:

Please assign me this project i will make it responsive and make it adjustable to auto with respect to device size.


Signup is unavailable

When I go to https://api.citation-api.com/signup the only message that appears is "An error occurred. Please contact support!"
This makes it impossible to use this plugin.

Added a screenshot for further info/proof.

I think this is the reason
https://github.com/ONLYOFFICE/plugin-easybib#important

Please be advised advised that the EasyBib Public Citation API will no longer be available after 5/31/2021.


Allow more generic firmware customization

This commit adds a new Kconfig setting CONFIG_CUSTOMIZATION. If enabled, the
subdirectory src/custom is added to the build. It can contain an own
CMakeLists.txt file to add several different C/C++ files.
Readme has been updated to explain also DTS overlays and custom prj.conf files.

Looks good to me

Alright, thanks for the quick review. So we'll go ahead with this approach.


arch: support common 64-bit mmio read and write

implement sys_read64 and sys_write64 to enable mmio to 64-bit
registers.  Previously these routines were only implemented
for 64-bit processor architectures.
Compilers for 32-bit architectures will generate instruction
load and store sequences for uint64_t types.  Atomicity of
these accesses is not guaranteed as the processor and/or
interconnects could split these accesses into smaller-sized
transactions.
Signed-off-by: Eugene Cohen<EMAIL_ADDRESS>

Agree with Andy, 64-bit MMIO on 32-bit machines will typically have some extra details to be aware of (e.g. order of the register accesses to ensure an atomic 64-bit transaction, or an extra control register for that). Better to have driver code deal with that explicitly. Generate a (compile-time) error/warning if these functions are used on 32-bit platforms?

Ah, did not expect controversy here ... so did some research.
I agree that on some architectures 64-bit accesses can imply multiple word accesses but that's not unique to 64-bit accesses.  Accesses can be split by compilers, processor load/store units and even interconnects and this isn't limited to the 64-bit case - the same has happened for smaller sizes in the past.  (Or put more cynically, hardware folks can mess up far more than just 64-bit accesses!!)
Doing some research in other OSes I see a mix of techniques:
Linux - create an explicit non-atomic 64-bit access interface where you specify the access order via #include choice (curious): https://github.com/torvalds/linux/blob/master/include/linux/io-64-nonatomic-hi-lo.h
edk2 (UEFI) - Just let the compiler do it: https://github.com/tianocore/edk2/blob/master/MdePkg/Library/BaseIoLibIntrinsic/IoLib.c#L355
FreeBSD - mixed results - x86 is X64 only but arm allows both 32 and 64-bit archs:
x86: https://cgit.freebsd.org/src/tree/sys/x86/include/bus.h#n494
arm: https://cgit.freebsd.org/src/tree/sys/arm/include/bus.h#n389
So my thought is that 64-bit registers can an do exist so we should at least have some way to enable a model for drivers to be re-used across all architectures.  And I think forcing all accesses to 64-bit registers to be explicitly split into sys_read32/sys_write32 pairs unnecessarily punishes architectures with native 64-bit access.
So a couple options as I see it:

allow sys_read64/sys_write64 to be used for 64-bit registers that do not have access size/order dependencies and then create variants (like Linux) for those that do
do what Linux does and create sys_read64_hilo and sys_read64_lohi and require every driver declare what access method they desire (preferably via API as opposed to #include)
do what UEFI and FreeBSD arm do and don't worry about it
do nothing - portable drivers doing 64-bit accesses are not supported

It seems like #3 is out of the question based on Andy and ruuddw's feedback.

I should also add one thing:
Many 32-bit processor architectures have native 64-bit access.   I can do an LDRD/STRD on arm32 which generates a multi-beat transfer on the interconnect.  Depending on downstream interconnects this could be delivered as a 64-bit atomic access or split into separate 32-bit accesses.   (And as a thought exercise, replace "64" with "32" and "32" with "16" to see my point that this is not necessarily a 64-bit only use case)

that's not unique to 64-bit accesses. Accesses can be split by compilers, processor load/store units and even interconnects

That's the whole point of providing MMIO APIs in the first place, though.  Zephyr requires that sys_read/write*()[1]  be atomic from the perspective of other users of the address.  If we didn't have those requirements, we'd just use regular C pointers and be done with it.  Platforms providing APIs for MMIO registers[2] need to do more work and make stronger promises.
We can't have a non-atomic sys_read(), basically.  That's breaking the promise.   As mentioned though, I'm fine with a "nonatomic/unsafe/be_careful" wrapper API.
[1] The k_atomic_t API lives in this space too, as does the barrier API that is in its infancy.
[2] Which are sometimes just C pointers, FWIW, but ones of specific type and carefully managed alignment.  The intel_adsp integration uses a bunch of volatile struct pointers for its register blocks, for example.

As mentioned though, I'm fine with a "nonatomic/unsafe/be_careful" wrapper API.

Got it.  From a naming perspective the "unsafe" is not my favorite - see how managed languages use unsafe keywords everywhere which force people to equate "safety" with "managed memory".  In this case we would be conflating "safety" with "register access atomicity".  So maybe we could choose a more direct wording like "nonatomic"?
So we would have:
sys_read64 - only on architectures that have native/atomic support
sys_read64_nonatomic - all platforms

I was going to create another PR for this but let me ask (RFC) now:
I was also doing to propose "_relaxed" MMIO functions in the same manner although I'm getting a bit worried about the permutations implied by width/atomic/relaxed:
sys_read64
sys_read64_relaxed
sys_read64_nonatomic
sys_read64_nonatomic_relaxed
We can defer the _relaxed discussion but wanted to give a heads-up

before I go ahead an push an update to the PR can I get confirmation that the nonatomic naming is acceptable @andyross ?

"_nonatomic" is certainly fine with me (though I guess I see it as providing minimal real value beyond aesthetics?  I mean, at this stage it's just a compiler-generated multiword pointer dereference).  Note that I'm about to leave for Ecuador for two weeks, so if I'm not around to approve the final version just point folks to this comment?

Similar discussion in https://github.com/zephyrproject-rtos/zephyr/pull/51163. We should try to progress on this.


Multiple result builders in async adapter

See Slack conversation: https://hamilton-opensource.slack.com/archives/C03M33QB4M8/p1720718536565439
Ryan Whitten
1 hour ago
Hey all, I'm upgrading to the new AsyncBuilder/AsyncDriver and wondering if I'm correctly setting the result_builder. With the regular Builder I would normally set it using with_adapters() , e.g.:
result_builder = base.PandasDataFrameResult()
await AsyncBuilder().with_config(self.config).with_modules(*self.included_modules).with_adapters(result_builder).build()
but this raises ValueError("You cannot pass more than one result builder to the async driver. Please pass in a single result builder") here: https://github.com/DAGWorks-Inc/hamilton/blob/main/hamilton/async_driver.py#L225-L229

Looks like that is due to a default DictResult getting set if the AsyncBuilder.result_builder is None: https://github.com/DAGWorks-Inc/hamilton/blob/main/hamilton/async_driver.py#L478-L480
I'm able to work around it by setting the builder's result_builder attr before calling build(), but not sure if that is the intended usage:
result_builder = base.PandasDataFrameResult()
builder = AsyncBuilder().with_config(self.config).with_modules(*self.included_modules)
builder.result_builder = result_builder
await builder.build()

async_driver.py
https://github.com/[DAGWorks-Inc/hamilton](https://github.com/DAGWorks-Inc/hamilton)|DAGWorks-Inc/hamiltonDAGWorks-Inc/hamilton | Added by GitHub
async_driver.py
https://github.com/[DAGWorks-Inc/hamilton](https://github.com/DAGWorks-Inc/hamilton)|DAGWorks-Inc/hamiltonDAGWorks-Inc/hamilton | Added by GitHub

We can close this once we push a release right?

This has been fixed in 1.71.0!


handleUncaughtExceptions passed to Cucumberjs

Hi,
I got problem when I use Protractor + CucumberJS. If I execute my test via cli and get exceptions, protractor will stop and does not execute the remaining scenario. I found the runner.js inside this plugin has this line:
require('source-map-support').install();
When I changed this to:
require('source-map-support').install({
handleUncaughtExceptions: false
});
Protractor will execute remaining scenario. Is there any way to pass this via config file instead of modifying this script directly ?

Hi
This is a sub-dependecy of protractor from gulp-protractor. I haven't access directly to config / change that.
And it seems to have an active issue on the protractor module: https://github.com/angular/protractor/issues/876
Maybe you can check more on this way to find a patch ?
Many thanks
Cheers

Hello,
It seems there is no way to achieve the solution by modify the runner directly. I made research on many tickets of protractor but all of them seem not be resolved yet. So I had to modify the script directly.
Best regards,
Cuong Nguyen


chore(deps): security upgrades

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


[Test] Disable deinit_escape test.

It's failing in CI, disable until we have a proper fix.
rdar://103369708

@swift-ci please smoke test and merge

Never mind, figured out a proper fix.


Fix clientID not added to ActionRequest

What this PR does / why we need it:
@ZhangYW18 - I added change the sample plugin to use your code as an example instead of sending alerts on timer.
This PR also makes sure viper binds a default maximum message size as plugins could also exceed this limit.
Which issue(s) this PR fixes

Fixes #1427

Signed-off-by: GuessWhoSamFoo<EMAIL_ADDRESS>

Good job, Octant team! Thanks for your hard work.


Added operator_overloading.cpp

Issue Number: 87
This submission will close the issue #87
Submissions Checklist:

[x] Have you followed the guidelines in CONTRIBUTING.md?
[x] Have you checked there aren't other open Pull Requests for the same hackerrank problem?

[x] Is your file name exactly same as the problem name of hackerrank, followed by the proper extension?
[x] Have you ensured that you have put the files in appropriate folders? (Folders are made according to the subdomain of hackerrank practice problems).

Hacktoberfest Contributor:

[x] Are you a hacktoberfest contributor?

Hackerrank Problem Link:
https://www.hackerrank.com/challenges/operator-overloading/problem?isFullScreen=true
Submitted Hackerrank Solution Link:
https://www.hackerrank.com/challenges/operator-overloading/submissions/code/293573254
Any other changes you made or something you would like to mention?
NA

I have made the required changes. Are they visible?

I have made the required changes. Are they visible?

@PurviSaini Sorry, It is not visible to me. Also make sure that your repo is up-to-date with the origin remote.

Do I need to create another PR for this update?

I have made the required changes in the branch issue87, the changes are visible on my side

Great!  it's fine now, Thanks for contributing!

Thankyou so much!!


Rename virtualenv

Summary and Scope

Issue Type

RFE Pull Request

The current virtualenv name shos as python, this doesn't offer any contextual information.
Using a virtualenv name that matches our app will make the PS1 more clear to a user when they are in our Python environment.
Before:
(python) ncn-m001:~/rusty #

After:
(libcsm-venv) ncn-m001:~/rusty #

Prerequisites

[ ] I have included documentation in my PR (or it is not required).
[ ] I have added unit tests for my code.

Idempotency

Risks and Mitigations

This is up for debate, but I don't think the python named virtualenv is a useful name.

This pulls in https://github.com/Cray-HPE/libCSM/pull/27#issuecomment-1485806669


[DO NOT MERGE] Basic 'az environment' implementation

Don't close the file descriptors!!! (+3 squashed commits)
Squashed commits:
[4afda6f] Tab completion modification
[c0a005b] Add license headers
[9ba2e73] Delete old nightly env, create new env. (+2 squashed commits)
Squashed commits:
[8d39610] Allow force deletion
[78ec91a] fix argparse (+1 squashed commit)
Squashed commits:
[0a07497] add todo (+6 squashed commits)
Squashed commits:
[e38045f] Basic version of curl installable
[21080ba] change main name
[0701d63] Read in modules from env var
[3725b5c] more pip installable magic
[db7bfcf] It's now pip installable
[d909222] basic version (not currently pip installable)

Will reopen with new fork


[Analysis] Analysis of Data replication (On prem / Cloud) requirements for SODA Hawaii release

Issue/Feature Description:
Analyse the key requirements for Data replication support in SODA and the corresponding changes and updates needed for the Dashboard.
Enable the user to utilise the Replication and failover mechanism intuitively from the Dashboard.
Why this issue to fixed / feature is needed(give scenarios or use cases):
Currently SODA supports on-prem volume replication. As we are working on providing host based replication and disaster recovery using the same, the user should be able to setup this mechanism and be notified intuitively on the Dashboard.
How to reproduce, in case of a bug:
Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

Started the analysis by looking at some existing solutions and demos.
Started with Dell EMC RecoverPoint (demo).

As per discussion with @rajat-soda the current replication feature will need updates to support Array and Host based replication. This design is still in discussion and the changes to dashboard will depend on the direction in which the replication feature is designed.


Customize Button component's flex direction

It doesn't override when I apply justify-start class on the component:
<ABtn :icon="item.icon" variant="text" class="w-full justify-start" >{{ item.title }}</ABtn>

I was hoping to add a prop for this.

Button is justified to center via justify-center, use !justify-start to override that.
<template>
  <div>
    <ABtn class="w-full !justify-start">
      Primary
    </ABtn>
  </div>
</template>


Locator seems not work?

hi,@nicholas-leonard
I'm trying to train my own dataset using your recurrent-attention-model structure. The dataset has 28*28 size and contains formula characters like [0-9],[a-z],(,),-,+, etc.
However, after 300 epoches, these are what I get:

For all characters, after 2 steps or so, the locator always go to corner and stop predicting new glimpse locations.It seems that the locator dosen't work well. Is there something I should change with respect to your RAM structure?
What should I do in this particular case? Any suggestions? Thank you

Hi, your glimpseSize seems really small. This is what I used to train the recurrent attention model on MNIST which is also 28x28:
th scripts/rnn-visual-attention.lua --cuda --useDevice 2 --rho 7 --rewardScale 1 --maxEpoch 2000 --maxTries 200 --learningRate 0.01 --sensorDepth 1 --momentum 0.9 --maxOutNorm -1 --batchSize 20 --saturateEpoch 800 --locatorStd 0.11 --uniform 0.1 --hiddenSize '{256}' --unitPixels 13 --glimpsePatchSize 8

The unitPixels argument is important as it prevents the model from getting stuck at the borders and corners.

Thank for your reply! Do u think a glimpse with 2scale may work better in this case? or just a glimpse with 1scale, but a larger size?

@OptimusPrimeCao Since your problem is so similar to MNIST, I would use exactly:
th scripts/rnn-visual-attention.lua --cuda --useDevice 2 --rho 7 --rewardScale 1 --maxEpoch 2000 --maxTries 200 --learningRate 0.01 --sensorDepth 1 --momentum 0.9 --maxOutNorm -1 --batchSize 20 --saturateEpoch 800 --locatorStd 0.11 --uniform 0.1 --hiddenSize '{256}' --unitPixels 13 --glimpsePatchSize 8

So a glimpse depth of 1 and a size of 8 pixels.

I would like to ask how to get the output location of the locator when doing evaluation? How to write the code? Thanks!


Assignment 1

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Added Anagram function, performed addition and sort function.
What did you learn from the changes you have made?
Learned about the uses of function and different data types.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
No
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
No
How were these changes tested?
Using Bash
A reference to a related issue in your repository (if applicable)
No
Checklist

[ Yes] I can confirm that my changes are working as intended

you did a great job here!
Please go ahead and close this pull request now. Thanks!


[stable/jenkins] Correcting descriptive text in values.yaml about AdminUser value

Signed-off-by: brendan<EMAIL_ADDRESS>I think this issue was probably caused by confusion due to wrong info in the values.yaml about AdminUser.  It needs to have Overall\Administer rights.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] title of the PR contains starts with chart name e.g. [stable/chart]

@holmesb Could you rebase your changes on master?


toFile Method is behaving strange

What are you trying to achieve?
Convert file top webp and lower the quality.
What goes wrong?
If i upload multiple images at the same time all the compressed images are replaced by the first one.
I cant rly see why this wont work as all the output files have the correct name
Are you able to provide a standalone code sample that demonstrates this question?
I ve a Cloud Function that gets triggered for every upload it. The shortened Version of the code:
import * as functions from 'firebase-functions';
const { Storage } = require('@google-cloud/storage');
const sharp = require('sharp');
const fs = require('fs-extra')
const gcs = new Storage();
const path = require('path');
import { tmpdir } from 'os';
import { join, dirname } from 'path';
import { ObjectMetadata } from 'firebase-functions/lib/providers/storage';
export const smaller = functions.storage.bucket('uploads')
  .object()
  .onFinalize(async (object: ObjectMetadata) => {

      const bucket = gcs.bucket(object.bucket);
      const filePath = object.name || "";
      const filePathArray = filePath.split('/')
      const fileName = filePathArray.pop() || "";
      const fileDir = filePathArray[0] || "";

      const bucketDir = dirname(filePath);
      const workingDir = join(tmpdir(), 'compress');

      const tmpFilePath = join(workingDir, 'source.png');

      // Exit Contion
     ......

      // 1. Ensure thumbnail dir exists
      await fs.ensureDir(workingDir);

      // 2. Download Source File
      await bucket.file(filePath).download({
        destination: tmpFilePath
      });

      const thumbName = ..

      const thumbPath = join(workingDir, thumbName);

      **// this code produces the error
       await sharp(tmpFilePath)
        .webp({ quality: 75 })
        .toFile(thumbPath);
      // With this everthing works
     await fs.createReadStream(tmpFilePath).pipe(fs.createWriteStream(thumbPath));**
      // Upload to GCS
      await bucket.upload(thumbPath, {
        destination: join(bucketDir, thumbName)
      });

      return fs.remove(workingDir);
    }
    return false;
  });

If the input filename is the same but the contents change, you'll need to prevent the use of libvips cache via sharp.cache(false)
https://sharp.pixelplumbing.com/en/stable/api-utility/#cache

each file has a timestamp in the name, but ll still try this

you should have had
const tmpFilePath = join(workingDir, fileName)

instead of
const tmpFilePath = join(workingDir, 'source.png')


Axon 2.4.x - Support for mongo-java-driver 3.x

Added a new mongo3 submodule with support for the version 3 of the mongo driver.

Any idea why the build is failing ? the error should have nothing with the changes I've made

Just for reference locally everything passes
`
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Axon Framework ..................................... SUCCESS [  0.623 s]
[INFO] Axon Framework core ................................ SUCCESS [02:20 min]
[INFO] Axon Framework Spring Integration Support .......... SUCCESS [  3.056 s]
[INFO] Axon Framework Spring Messaging Support ............ SUCCESS [  3.098 s]
[INFO] Axon Framework Test Fixtures ....................... SUCCESS [  6.087 s]
[INFO] Axon Framework Distributed CommandBus .............. SUCCESS [ 54.801 s]
[INFO] Axon MongoDB Components ............................ SUCCESS [ 21.019 s]
[INFO] Axon AMQP Connectors ............................... SUCCESS [ 12.786 s]
[INFO] Axon Integration tests ............................. SUCCESS [ 34.142 s]
[INFO] Axon MongoDB Components V3 ......................... SUCCESS [ 21.182 s]
[INFO] Axon - Google App Engine integration ............... SUCCESS [  3.416 s]
[INFO] Axon Monitoring - JMX Support ...................... SUCCESS [  1.394 s]
[INFO] Axon Quickstart .................................... SUCCESS [  3.023 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:05 min
[INFO] Finished at: 2016-07-21T22:56:00+02:00
[INFO] Final Memory: 48M/420M
[INFO] ------------------------------------------------------------------------
`

The build fails due to some timeouts in tests unrelated to this PR. The Travis build runs in a container with limited CPU. Therefore, timeout values for Travis need to be slightly higher.

Allard could you please release the module on maven. thanks

Will create a release today.


Cannot install package "luci-app-homeproxy" . . .

Hi . . .
I use your "kenzok8/small-package" package to build the "coolsnowwolf/lede" firmware, which is wonderful and has very good packages. But when I added Luci-app-homeproxy, which uses the Sing-Box core, to my package list, I encountered the following error.
Collected errors:
 * check_data_file_clashes: Package firewall4 wants to install file /home/m33ft/LEDE_RaspberryPi.4B/build_dir/target-aarch64_cortex-a72_musl/root-bcm27xx/etc/hotplug.d/iface/20-firewall
	But that file is already provided by package  * firewall
 * check_data_file_clashes: Package firewall4 wants to install file /home/m33ft/LEDE_RaspberryPi.4B/build_dir/target-aarch64_cortex-a72_musl/root-bcm27xx/etc/init.d/firewall
	But that file is already provided by package  * firewall
 * check_data_file_clashes: Package firewall4 wants to install file /home/m33ft/LEDE_RaspberryPi.4B/build_dir/target-aarch64_cortex-a72_musl/root-bcm27xx/sbin/fw3
	But that file is already provided by package  * firewall
 * opkg_install_cmd: Cannot install package firewall4.
 * check_data_file_clashes: Package firewall4 wants to install file /home/m33ft/LEDE_RaspberryPi.4B/build_dir/target-aarch64_cortex-a72_musl/root-bcm27xx/etc/hotplug.d/iface/20-firewall
	But that file is already provided by package  * firewall
 * check_data_file_clashes: Package firewall4 wants to install file /home/m33ft/LEDE_RaspberryPi.4B/build_dir/target-aarch64_cortex-a72_musl/root-bcm27xx/etc/init.d/firewall
	But that file is already provided by package  * firewall
 * check_data_file_clashes: Package firewall4 wants to install file /home/m33ft/LEDE_RaspberryPi.4B/build_dir/target-aarch64_cortex-a72_musl/root-bcm27xx/sbin/fw3
	But that file is already provided by package  * firewall
 * opkg_install_cmd: Cannot install package luci-app-homeproxy.
make[2]: *** [package/Makefile:70: package/install] Error 255
make[2]: Leaving directory '/home/m33ft/LEDE_RaspberryPi.4B'
make[1]: *** [package/Makefile:111: /home/m33ft/LEDE_RaspberryPi.4B/staging_dir/target-aarch64_cortex-a72_musl/stamp/.package_install] Error 2
make[1]: Leaving directory '/home/m33ft/LEDE_RaspberryPi.4B'
make: *** [/home/m33ft/LEDE_RaspberryPi.4B/include/toplevel.mk:231: world] Error 2

What I understood is that the homeproxy package uses Firewall 4 based on nftables which is supported by OpenWrt version 22.03, but here it is Firewall 3 !!!
You can see my ".config" file for RaspberryPi.4B here.
Thank you for your guidance.

homeproxy package uses Firewall 4  https://github.com/kenzok8/small-package/commit/51fce9e8575967317a3a7224612dbf4a67499a1e

You are absolutely right. When I asked the developer, he said:

homeproxy is firewall4 only
homeproxy is designed for ucode + js based luci, which is only available on OpenWrt 23.xx+


Manually Set DNS server for http(s) checks?

Info
Uptime Kuma Version: 1.7.3
Using Docker?: Yes
Docker Version: 20.10.8, build 3967b7d
OS: Ubuntu Server 21.04
Browser: Chrome
Is it possible to manually set the DNS server used for a particular check, or for the whole container? From my docker logs, it seems like a check is using <IP_ADDRESS> - and this means that can't check on internal services behind a reverse proxy.
Am I missing a config location, or is <IP_ADDRESS> hard-coded in for those checks?

Not hardcoded, it uses system's dns server.
You can override by using Docker's dns settings:
https://docs.docker.com/config/containers/container-networking/#dns-services

That's sorted it, thanks!


饼图能否只让selectedOffset变色

One-line summary [问题简述]

饼图能否实现像这种效果，hover时外圈的颜色跟圆的颜色有差异，用border好像又不是，不能只控制外圈？
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:
Browser version [浏览器类型和版本]:
OS Version [操作系统类型和版本]:

Expected behaviour [期望结果]
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息]

@Justin-Shen  Not for the time being. I have temporarily added functions by adding series.
http://gallery.echartsjs.com/editor.html?c=xZ9ppRyjWM&v=1，Do you see what you want?

@Justin-Shen Not for the time being. I have temporarily added functions by adding series.
http://gallery.echartsjs.com/editor.html?c=xZ9ppRyjWM&v=1
Do you see what you want?

thanks a ton!!!!


chore: Clean-up utility method that is public in detekt-api

isInternal() is defined publicly, no need to shamelessly reuse it :smile:
Relies on #24.

Thanks!
Nit: I would keep unrelated changes in different PRs. Gradle and java bumps could be their own prs.

It was! It was in #24. Stacked diff got muddled.

Thanks!
Nit: I would keep unrelated changes in different PRs. Gradle and java bumps could be their own prs.

It was! It was in #24. Stacked diff got muddled.

ah ok did not notice. Sounds good!


Shutdown stops after failure inside shutdown function

Describe the bug
A clear and concise description of what the bug is.
 Will be pushed to master and published once it is determined to be stable-ish


move rebranded doc site

Follow up to #185...
Need to move the docs site from bookkeeper.akuity.io to kargo-render.akuity.io
This is mostly a Netlify task, so I will handle.

All set: https://kargo-render.akuity.io


Add typescript section to bower/npm configs to support tsd link

As mentioned in https://github.com/photonstorm/phaser/issues/2180, tsd provides the ability to link to bundled definitions in bower and npm packages.  Since Phaser is available through both package managers, packages.json and bower.json have both been modified in this pull request to support tsd's linking ability.

+1 for this feature

+1 to this as well, I was about to go make a PR for this myself when I saw this.

Can't merge, wrong branch. Modified locally.


Failures due to presence of FASTLANE_PASSWORD

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
When FASTLANE_PASSWORD is present as an env var (configured on .zshrc or .bashrc) fastlane ignores the password inputed when asked on the terminal.
Environment
fastlane version (run fastlane -v):
1.105.2
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
Yes
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
chruby
What Xcode version do you use (e.g. 7.3, 8.0)
8.0
Worth noting that this isn't the first time I've experienced this; just that being the numbnuts i am i never took the time to file an issue about this.
Recently I tried on a fresh new machine at work (that I configured using my dotfiles repo which carried away the FASTLANE_PASSWORD var) and then I was faced again with a case of «your password is wrong» even though fastlanewas asking me to input it via terminal and I was copy/pasting it from LastPass.
When I was about to rage quit I realised that the variable was set and after removing it and fastlane asking me for the password again, adding the same one I used multiple times (without success) worked.
Hope this is enough info to repro; if not let me know and I'll be more than happy to provide more details.
PS. Thanks for the amazing work so far

@esttorhe Thanks for the report! Can you share your Fastfile so we can see which tools you're using?

Hi @asfalcone, can't share the Fastfile but we are using gym, match, sigh, pem, pilot
Let me know if this is not enough or if there's anything specific you need

@esttorhe Can you share the full output of one of your lanes and also share the output of fastlane env

@TKBurner fastlane env doesn't seem to be a recognisable thing
[!] Could not find 'env'. Available lanes: install_xcode, install_pods, install_bash_aliases, install_ohmyzsh_aliases, install_fish_aliases, setup, fetch_submodules, update_devices, dev_certificates_fetch, dist_certificates_fetch, dev_certificates_update, dist_certificates_update, build_debug, build_release, build_alpha, copy_provisioning_profiles, build_frank, build_core, build_ui, build_playback, build_search, build_payments, build_core_examples, build_ui_examples, build_playback_examples, build_search_examples, build_payments_examples, build_frameworks, build_frameworks_examples, ci, deploy_appstore, deploy_hockey, ab_testing, tests_core, tests_ui, tests_playback, tests_search, tests_payments, tests_all, tests_ruby, tests_app, acceptance_tests

you should upgrade fastlane - the env is only available since 1.106.1  -> https://github.com/fastlane/fastlane/releases/tag/1.106.1
is your FASTLAN_PASSWORD  maybe set to value that is just wrong?

@esttorhe Run fastlane run update_fastlane first. Thanks!

I will do that but I think you guys are deviating from the issue; this has been present since A LONG time ago and I'm almost 💯 the issue is still there unless someone actually addressed it.
I'll update and try to post the new stuff in here but I doubt that's going to be today since we are almost at our EOD.

@esttorhe Thanks! If you can provide a sample project affected by the issue that'll help us dig in. 👍

@TKBurner :( i feel like you guys are not actually reading the description of the issue.
There's no project specific setting I can provide you to reproduce other than this:

Set up a FASTLANE_PASSWORD env var on your ~/.zshrc or ~/.bashrc or your rc file of choice for your shell with a value of WRONG_PASSWORD
Launch a fastlane integration that requires the use of a username and password
fastlane will fail because the password is wrong and will ask you to set the correct one
Input the correct password
fastlane will fail saying that the password is incorrect
Remove the env var from your dotfiles and try again
fastlane will ask for the password
input the correct password again
See how fastlane succeeds

I hope this is enough information for you to reproduce

@esttorhe  i think now i got it :)
i tried reproducing as you said with following lane:
lane :demo do
  latest_testflight_build_number(app_identifier: "krone.at-fivexfive", username<EMAIL_ADDRESS>end

running it with (pw is wrong):  FASTLANE_PASSWORD=1234 fastlane demo
ends with:
DEBUG [2016-11-03 18:49:49.49]: Checking if there are any plugins that should be loaded...
INFO [2016-11-03 18:49:49.53]: Driving the lane 'demo' 🚀
INFO [2016-11-03 18:49:49.53]: --------------------------------------------
INFO [2016-11-03 18:49:49.53]: --- Step: latest_testflight_build_number ---
INFO [2016-11-03 18:49:49.53]: --------------------------------------------
INFO [2016-11-03 18:49:49.71]: Login to iTunes Connect<EMAIL_ADDRESS>WARN [2016-11-03 18:49:50.60]: Variable Dump:
INFO [2016-11-03 18:49:50.60]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"demo"}
ERROR [2016-11-03 18:49:50.60]: Invalid username and password combination. Used<EMAIL_ADDRESS>as the username.
INFO [2016-11-03 18:49:50.60]: Successfully generated documentation at path '/Users/hja/Desktop/SPORTPORTAL/fastlane/fastlane/README.md'

+------+--------------------------------+-------------+
|                  fastlane summary                   |
+------+--------------------------------+-------------+
| Step | Action                         | Time (in s) |
+------+--------------------------------+-------------+
| 💥    | latest_testflight_build_number | 1           |
+------+--------------------------------+-------------+

ERROR [2016-11-03 18:49:50.61]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...
Search query: The request could not be completed because:
	Invalid username and password combination. Used<EMAIL_ADDRESS>as the username.

URL: https://api.github.com/search/issues?q=The%20request%20could%20not%20be%20completed%20because:%0A%09Invalid%20username%20and%20password%20combination.%20Used%20'helmut@januschka.com'%20as%20the%20username.+repo:fastlane/fastlane
Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new
/Users/hja/.rvm/gems/ruby-2.2.5/gems/spaceship-0.36.2/lib/spaceship/client.rb:287:in `rescue in send_shared_login_request': [!] The request could not be completed because: (Spaceship::Client::InvalidUserCredentialsError)

and does not ask - for password. can you share your fastfile (or the relevant part atleast)?

@esttorhe Just to +1 what @hjanuschka said above - can you provide a simple lane that can demonstrate the issue. Specifically, what is your Fastfile calling that allows the password to be entered after it has been found to be invalid? I've tried a few things to try to reproduce the behavior you described, but the tools fail because of the invalid password and don't ask for the password to be re-entered. So, I suspect I'm just trying the wrong things.  😄

Have you tried match?
If I'm not mistaken this happened with match.
–
Esteban Torres
CraftKollective (http://craftkollective.com) Co-Founder
Phone: (+506)8813-0934 (tel:(+506)8813-0934)
Skype: esteban.a.torres.hernandez
Twitter: @esttorhe (https://twitter.com/esttorhe)
On 4 Nov 2016, 18:38 +0100, mpirri<EMAIL_ADDRESS>wrote:

@esttorhe (https://github.com/esttorhe) Just to +1 what @hjanuschka (https://github.com/hjanuschka) said above - can you provide a simple lane that can demonstrate the issue. Specifically, what is your Fastfile calling that allows the password to be entered after it has been found to be invalid? I've tried a few things to try to reproduce the behavior you described, but the tools fail because of the invalid password and don't ask for the password to be re-entered. So, I suspect I'm just trying the wrong things. 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/fastlane/fastlane/issues/6626#issuecomment-258498721), or mute the thread (https://github.com/notifications/unsubscribe-auth/AChTok2wXPbToWfphDgWDw_8Wv2QZXe8ks5q622dgaJpZM4Kau38).

@esttorhe when using match, was it with your git password or AppleID password?

@esttorhe  i really wan't to help you,and find the bug.
but i am unable to reproduce it.
tried match via fastfile
  match(
        git_url: "git@gitlab.krone.at:mobile/IOS-CERTIFICATES.git",
        app_identifier: "krone.at-new"
)

results in:
[12:10:30]: Driving the lane 'dd' 🚀
[12:10:30]: asdf
[12:10:30]: -------------------
[12:10:30]: --- Step: match ---
[12:10:30]: -------------------

+-----------------------+-------------------------------------------------+
|                        Summary for match 0.10.0                         |
+-----------------------+-------------------------------------------------+
| git_url               | git@gitlab.krone.at:mobile/IOS-CERTIFICATES.git |
| app_identifier        | krone.at-new                                    |
| git_branch            | master                                          |
| type                  | development                                     |
| keychain_name         | login.keychain                                  |
| readonly              | false                                           |
| verbose               | false                                           |
| force                 | false                                           |
| shallow_clone         | false                                           |
| force_for_new_devices | false                                           |
| skip_docs             | false                                           |
+-----------------------+-------------------------------------------------+

[12:10:31]: Cloning remote git repo...
[12:10:39]: 🔓  Successfully decrypted certificates repo
[12:10:39]: To not be asked about this value, you can specify it using 'username'
Your Apple ID Username<EMAIL_ADDRESS>[12:10:43]: Verifying that the certificate and profile are still valid on the Dev Portal...
The login credentials for<EMAIL_ADDRESS>seem to be wrong
The password was taken from the environment variable
Please make sure it is correct
Please run this tool again to apply the new password
[12:10:44]: An error occured while verifying your certificates and profiles with the Apple Developer Portal.
[12:10:44]: If you already have your certificates stored in git, you can run `match` in readonly mode
[12:10:44]: to just install the certificates and profiles without accessing the Dev Portal.
[12:10:44]: To do so, just pass `readonly: true` to your match call.
[12:10:44]: 🔒  Successfully encrypted certificates repo
[12:10:44]: Variable Dump:
[12:10:44]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"dd"}
[12:10:44]: Invalid User Credentials

+------+--------+-------------+
|      fastlane summary       |
+------+--------+-------------+
| Step | Action | Time (in s) |
+------+--------+-------------+
| 💥    | match  | 14          |
+------+--------+-------------+

and commandline
export FASTLANE_PASSWORD=1234
match -a krone.at-krone1.at

+-----------------------+--------------------+
|          Summary for match 0.10.0          |
+-----------------------+--------------------+
| app_identifier        | krone.at-krone1.at |
| git_branch            | master             |
| type                  | development        |
| keychain_name         | login.keychain     |
| readonly              | false              |
| verbose               | false              |
| force                 | false              |
| shallow_clone         | false              |
| force_for_new_devices | false              |
| skip_docs             | false              |
+-----------------------+--------------------+

[12:07:02]: To not be asked about this value, you can specify it using 'git_url'
URL to the git repo containing all the certificates: git@gitlab.krone.at:mobile/IOS-CERTIFICATES.git
[12:07:03]: Cloning remote git repo...
[12:07:12]: 🔓  Successfully decrypted certificates repo
[12:07:12]: To not be asked about this value, you can specify it using 'username'
Your Apple ID Username<EMAIL_ADDRESS>[12:07:17]: Verifying that the certificate and profile are still valid on the Dev Portal...
The login credentials for<EMAIL_ADDRESS>seem to be wrong
The password was taken from the environment variable
Please make sure it is correct
Please run this tool again to apply the new password
[12:07:18]: An error occured while verifying your certificates and profiles with the Apple Developer Portal.
[12:07:18]: If you already have your certificates stored in git, you can run `match` in readonly mode
[12:07:18]: to just install the certificates and profiles without accessing the Dev Portal.
[12:07:18]: To do so, just pass `readonly: true` to your match call.
[12:07:18]: 🔒  Successfully encrypted certificates repo


Our Crash Report URL is too long for GitHub

Examples
27662 characters length url (with 2.29?) - https://github.com/prisma/prisma/issues/8708
9074 characters length url (with 2.29.1) - https://github.com/prisma/prisma/issues/8915
If you take the https://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.[..] url from these issues you will see:

We should figure out what's the maximum length we can use and then adapt
https://github.com/prisma/prisma/blob/main/packages/engine-core/src/common/errors/utils/getErrorMessageWithLink.ts#L8:L8

Hi there,
As part of our effort to clean up our GitHub repo, we’re closing this issue to help focus on features and improvements that align with our focus areas and those of our community.
This issue was originally created for internal tracking purposes, but if you feel this is important to you, feel free to reopen the issue and get like-minded users to upvote as we will prioritize fixing issues based on community interest.
For more insight into our priorities and how we’re thinking about the future of Prisma, please see our blog post: https://www.prisma.io/blog/prisma-orm-manifesto.
Thank you for your understanding and support!


Cannot write post-request with request body

Hi,
thank you for your work in this module!
I want to do a post request with a request body. I created a changeset of the problem here.
I add the following line to playground/app.vue:
await $pets('/store/order', { body: { petId: petId.value }})
That won't compile with the following error:
Argument of type '{ body: { petId: number; }; }' is not assignable to parameter of type 'OpenFetchOptions<"post" | "POST", "post", { post: { requestBody?: { content: { "application/json": { id?: number | undefined; petId?: number | undefined; quantity?: number | undefined; shipDate?: string | undefined; status?: "placed" | ... 2 more ... | undefined; complete?: boolean | undefined; }; "application/xml":...'.   Property 'method' is missing in type '{ body: { petId: number; }; }' but required in type '{ method: "post" | "POST"; }'.ts(2345) fetch.ts(14, 77): 'method' is declared here.
When I do what TS wants, i.e. add that method parameter with a value of "post" it doesn't work either. Now it tells me the following:
Argument of type '{ method: "post"; body: { petId: number; }; }' is not assignable to parameter of type 'OpenFetchOptions<"post", "post", { post: { requestBody?: { content: { "application/json": { id?: number | undefined; petId?: number | undefined; quantity?: number | undefined; shipDate?: string | undefined; status?: "placed" | ... 2 more ... | undefined; complete?: boolean | undefined; }; "application/xml": { ...; }...'.   Type '{ method: "post"; body: { petId: number; }; }' is not assignable to type 'Record<string, never>'.ts(2345)
I tried digging into types, tried google, I cannot find the cause of the problem.
Is this a bug in nuxt-open-fetch or am I doing something wrong?
Thank you in advance for your response!
Regards,
Boris

Hi @uykusuz,
Good catch, it's definitely a bug!

@uykusuz Fixed in v0.7.0

Wow awesome, thank you!
-------- Original Message --------
On Apr 13, 2024, 11:48, Taras Batenkov wrote:

Closed #37 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Add support for grails environments in logback xml config using spring boot extensions

Transition logback xml config to use spring logback extensions which supports environment specific configuration
Close to old logback.groovy configuration, except it writes everything to console by default, which matches Spring Boot 2.
logback.xml becomes logback-spring.xml
https://docs.spring.io/spring-boot/docs/2.7.18/reference/html/howto.html#howto.logging.logback
https://docs.spring.io/spring-boot/docs/2.7.18/reference/html/features.html#features.logging.logback-extensions

I bumped it to 7, instead of 6.2.1.

Reviewed in Steering Committee meeting without objections.


[Training-Project] POC to use OpenCV to count vehicles and sent them to CEP

The following is a siddhi extension for $subject.

This need to be moved to Siddhi Extensions

moved to https://github.com/wso2/siddhi/tree/opencv-extension for future delopment


OCPBUGS-43508: fix proxy config and leader election test flakes

the TestOperandProxyConfiguration job has been flakying more and more lately. analysis show that the cause is not the test itself, but cluster recovery after the test teardown runs. it seems some components need longer to recover after a change in proxy configuration.
this commit increases the timeout from 5 to 10 minutes in hopes to stabilize this test.
Also changes TestLeaderElection to assert on leader lease acquiring instead of waiting on lease message as this would at times flake.

/label qe-approved

I'm going to trigger the e2e-aws-operator job a few more times so that we can get a better feeling of its passing rate.
/test e2e-aws-operator

Failure was unrelated to flake:
ERRO[2024-10-17T10:19:19Z] Timed out waiting for image pull secrets in the test namespace.

/retest

/retitle OCPBUGS-43508: fix proxy config and leader election test flakes

/cherry-pick release-4.17 release-4.16 release-4.15 release-4.14

/retest

/retest

/lgtm


Switch before_filter -> before_action

before_filter is deprecated in Rails 5.0 and removed in Rails 5.1.
Since the before_action syntax looks to have been added in Rails 4,
it should be safe to make this syntax change now, unless this fork is
used by anything on Rails < 4.

@PatrickTulskie Can you give this a review?  I think it's safe to merge now, if this is only a dependency for Rails 4+ projects.  We'll need to do this for Rails 5.1.

@chrishulton Done. Thanks for taking care of this!


Fixes longjump legs, fleshbeast splits, and devourer leaps.

-Fleshbeasts and devourers no longer break roofs.
-Longjump Legs now also jump walls like jump packs.

Nice work, should be published in 04713aa


[Typescript] useLenis should not require any argument

The first argument is the callback for effect of lenis instance. It shouldn't be required.

nice catch

this should be fixed in v0.0.46


Fix AsyncResource loading from URL

When a resource is coming from URL, the decoding in AsyncBitmapTexture is not stable and sometimes fails due to OOM error
even the inSampleSize is correctly set to downgrade the source file.
The root cause is the original java BufferInputStream used to wrap the url'ss inputStream  doesn't handle reset() properly
(it resets the offet of the internal buffer well) even the buffer provided is big enough to hold the resource we use in the
failed cases (possibly due to the internal buffer is cleared when resetting the offet).
This change provides a URLBufferedInputStream that resets the http connection everytime we do a reset to that inputStream,
preventing the incorrect offset in the http connection.
In addition, this change also provides an option to resouce loading api to choose between

only use internet streaming, and
download the resource in local cache,
so that the developer has a much more flexibility to control the consistency vs performance when
doing the resource loading.

This has been reviewed and merged to the other branch. Planning to merge here tomorrow.


Automated Package Upgrade

:tada: This PR is included in version 27.1.24 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Don't try to restore focus on non-existent inputs

Essentially the same check that happens here, for the focused input.

Turns out an unrelated test somehow fails :/
Will investigate...


Add support for obfuscation

dotnet pack should use obfuscated packages

I will decline this for now. I believe you can integrate obfuscation directly in your csproj and dotnet-releaser will pick-up whatever you have setup from your csproj.
Also, the main goal of dotnet-releaser is to ease the publishing process for public OSS projects. You can definitely obfuscate your private projects but you are on your own.


IULI

https://www.iuli.ac.id/

Here are the university profile registered in Government of Indonesia
https://pddikti.kemdikbud.go.id/data_pt/N0VEODM0MDEtMjg2Mi00RTEyLUFBNjAtNzlERUZFN0I5MEE4
(in bahasa)


Feature request - copy resource debug name to clipboard

Description

When viewing a shader that has a D3D11 debug name, it appears to be impossible to to copy that debug name to the clipboard. You might want to use this name in code when investigating something that you've seen in RenderDoc, and it would be nice to be able to guarantee you've transcribed it correctly.
Its name in the Shader section of the Pipeline State is not selectable, only clickable.
Its name in the Resource Inspector is not selectable.
Its name in the ID3D11Resource::SetDebugName section of the Resource Initialisation Parameters section of the Resource Inspector is not selectable.
Its name is not shown in the shader disassembler.
You can't copy its name from the shader disassembler tab.
I've mainly found this annoying with shaders, but I suppose being able to copy any resource's debug name would be nice.
Environment

RenderDoc version: Version v1.7 (built from a56af589)
Operating System: Version 1903 (OS Build 18362.720)
Graphics API: Direct3D11 (running over Remote Desktop, if that makes a difference...)

Its name in the ID3D11Resource::SetDebugName section of the Resource Initialisation Parameters section of the Resource Inspector is not selectable.

I'm not sure what you mean by this. I can select the row, and while it's not editable so you don't get a cursor, using ctrl+c while that row is selected gives something like: "Name MyShaderName" on the clipboard.
Also alternatively for any resource if you click the Rename Resource button then the editable text box to is populated with the current name, which you can also copy-paste from.
I don't think this merits having a dedicated UI button, so these methods seem sufficient for me. Please clarify if you're talking about something else, and I've misunderstood.


CI: Reduce the number of procs used to compiled ArborX

This should fix the CI issue we have gcc. The maximum amount of memory per process that we need is 3.4 GB (in benchmark). Since most of the programs in benchmark are light, we can afford to use make -j 4.

The maximum amount of memory per process that we need is 3.4 GB (in benchmark).

I don't quite understand. How do you know the max amount of memory per process we use? And if we run 4 processes, won't we still exceed the memory ($4 \times 3.4=13.6 > 8$)?

Potentially yes but not all the processes use the same amount of memory. We are lucky that when one process requires a lot of memory the others use almost nothing.

Does not sound like we get any guarantees. But we can try. Alternatively, we could see if CMake allows controlling the number of parallel processes for specific parts of the code.

GCC build took 9 minutes (without container rebuild). It was using cpu-node-6. Previously, it took 4 minutes on cpu-node-6, see this for example.


Update bazel-toolchains

Done.
https://mirror.bazel.build/github.com/bazelbuild/bazel-toolchains/releases/download/3.4.1/bazel-toolchains-3.4.1.tar.gz should be available now.


How do i stop the logger.

Is the the logger configurable. I don't want to output crawled data to stdout. Currently every crawled data is logged in stdout.

Hi @jamesjohnson1025, I'd suggest switching to a 3rd-party logging library for better control of outputs: https://github.com/seratch/notion-sdk-jvm#pluggable-logging My primary recommendation is logback library. You can place a configuration file under src/main/resources (e.g., logback.xml) to set logging level and how to write logs.


[React-Native] React-Navigation Plugin will crash app

Describe the bug
When trying to execute react-native in remote debug mode the app will crash, since synchronous calls are apparently no-op.
Too bad Bugsnag.getPlugin seems to fall in that category as well...
Steps to reproduce

Use bugsnag react navigation plugin
remote debug

Environment

Bugsnag version:
"@bugsnag/plugin-react-navigation": "^7.5.0",
"@bugsnag/react-native": "^7.3.5",
Browser framework version (if any):

React: react-native 0.63.3

Example code snippet
At the application root level:
Bugsnag.start({
  plugins: [new BugsnagPluginReactNavigation()],
});
const { createNavigationContainer } = Bugsnag.getPlugin('reactNavigation');

Error messages :
_Bugsnag$getPlugin is undefined

Hi @KDederichs
This is the same underlying issue as described on https://github.com/bugsnag/bugsnag-js/issues/1112 and we're considering how best we can fix this to cater for when a debugger is attached.
Until a fix is available you'd need to use a workaround similar to the one described on that issue:
https://github.com/bugsnag/bugsnag-js/issues/1112#issuecomment-722970857

Fixed in v7.6.1

Fixed in v7.6.1


Pull Requests: setting to allow edits by maintainers by default, tweak UI

Add setting to allow edits by maintainers by default, to avoid having to often ask contributors to enable this.
This also reorganizes the pull request settings UI to improve clarity. It was unclear which checkbox options were there to control available merge styles and which merge styles they correspond to.
Now there is a "Merge Styles" label followed by the merge style options with the same name as in other menus. The remaining checkboxes were moved to the bottom, ordered rougly by typical order of operations.

Before

After

LG-TM bot


KYLIN-1908 Add a document of query metrics

KYLIN-1908 Add a document of query metrics

Merged into 'document' branch. Please close this PR.


Update postgres plan in Heroku deployment docs

Description
Changes the command to create a heroku postgres addon
$ heroku addons:create heroku-postgresql:mini

 ›   Warning: heroku update available from 8.11.5 to 9.2.1.
Creating heroku-postgresql:mini on ⬢ location-tracker... !
 ▸    We tried to create heroku-postgresql:mini, but received an error from the add-on provider. Try the request again, or log a support ticket and include
 ▸    this message: The mini plan has reached end-of-life. You can try again with a valid plan. See the available plans with: heroku addons:plans
 ▸    heroku-postgresql.

The next cheapest heroku option is "essentials-0"
documentation: https://elements.heroku.com/addons/heroku-postgresql
$ heroku addons:create heroku-postgresql:essential-0

 ›   Warning: heroku update available from 8.11.5 to 9.2.1.
Creating heroku-postgresql:essential-0 on ⬢ location-tracker... ~$0.007/hour (max $5/month)
Database should be available soon
postgresql-silhouetted-14783 is being created in the background. The app will restart when complete...
Use heroku addons:info postgresql-silhouetted-14783 to check creation progress
Use heroku addons:docs heroku-postgresql to view documentation

Checklist:

[x] I've made sure that tests are updated accordingly (especially if adding or updating a template option)
[x] I've updated the documentation or confirm that my change doesn't require any updates

Rationale
This option (mini) is now longer valid

Thanks! Notes that a while back but completely forgot it was in our docs.

Might have to revert this. We gain the nav bar but the way messages are set up, now you see two of them.
Messages from allauth entrance.html and messages from base.html

One solution may be to move the messages into main, but I'm not sure if that serves the original purpose of main.html
    {% block main %}
      {% if messages %}
        {% for message in messages %}

            {{ message }}
            <button type="button"
                    class="btn-close"
                    data-bs-dismiss="alert"
                    aria-label="Close"></button>

        {% endfor %}
      {% endif %}
      {% block content %}

Use this document as a way to quick start any new project.

      {% endblock content %}
    {% endblock main %}

This would be an updated version that moves messages into main
https://github.com/cookiecutter/cookiecutter-django/pull/5410


Team: Tips and tricks about working remotely

Two good POVs on the idea:

From the perspective of a remote employee
From the perspective of someone in the office

How do we keep everyone engaged and part of the team?
What life is like for full time remote.

I think this is in there, right?

@swilliams That it is!


Add libraries for CUDA 11.3

~Blocked by #5192 (cuTENSOR 1.3)~ merged

pfnCI, test this please.

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

@asi1024 Failed to backport automatically.

Not cleanly cherry-picked


v23 rpc docs are missing

v23 is tagged
https://github.com/bitcoin/bitcoin/releases/tag/v23.0

See #869, the site doesn't seem to update though dunno why.

~See #869~
~Edit: oh this used to be about the site, I'm not sure it's a good idea to recycle issues for different topics, in any case the site is updated now.~

@laanwj sorry for the mess and thank you very much for getting the site up to date.


Release new version to support prawn:2.3 and ttfunk:1.6

Could you make a new release to allow people get support of prawn:2.3 and ttfunk:1.6 (commits 0aaf347c3659e562f0bff759dd4cf367c8dd1c40 and 3eec734a33ce848bc37a6bd84fb8868d80422922)?

I will be making a prerelease of Asciidoctor 2 later this week.
Since this is not itself a bug or a feature, you should ask it either on the mailinglist or the chat channel. Thanks.

Thanks a lot! And sorry for not using ML (normally I do for kernel, C projects, but for ruby I'm just a distro packager).


Use container name if supplied in archive logs

Summary
Use the container name within a step to generate the log file name when setting archiveLogs: true. Currently, it is main.log for every template with a single container instead of a containerSet. We have run into the issue that the artifact log file is always called main.log thus it is getting overwritten everytime in azure artifacts and we lose all logs besides the logs from the last step.
Use Cases
To have the ability to gather the logs from all steps easily
Useful information
I went through the code to find a solution and managed to find argo-workflows/workflow/executor/executor.go:600 (template.getmaincontainernames function) and argo-workflows/pkg/apis/workflow/v1alpha1/workflow_types.go:3105 (savelogs function)
I am now currently using a containerset with a single container to use the name of the container for the log file. It's a workaround for a feature that, I feel, should not be too hard to implement.

Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.

This sounds like a bug rather than a feature request; SaveLogs calls GetMainContainerNames, which does have logic to handle containerSets.
Could you please fill out the information the bug report template asks for? Such as versions tested, tested on :latest, a reproducible Workflow, etc

Ah I see what you mean now, thanks for clarifying!
The containerSet part in your description is only relevant for the workaround, so it made things a bit confusing as "no container set" is the default.

the logic in GetMainContainerNames basically only returns ["main"] when there is no container set

Yes, that's correct.
The overriding issue at the root cause here has its own bug report: https://github.com/argoproj/argo-workflows/issues/3417

/assign


Add note about ports range format

Add note for LocalPort and RemotePort options that ports range format can be used for specifying a continuous sequence of ports in one single ACL rule;
Add usage example for this feature.

Docs Build status updates of commit 771e70f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docset/winserver2012r2-ps/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:warning:Warning

Details

docset/mdop/appvclient/set-appvclientpackage.md
:warning:Warning

Details

docset/mdop/appvclient/set-appvclientmode.md
:warning:Warning

Details

docset/mdop/appvclient/sync-appvpublishingserver.md
:warning:Warning

Details

docset/mdop/appvclient/mount-appvclientpackage.md
:warning:Warning

Details

docset/windows/appvclient/Remove-AppvPublishingServer.md
:warning:Warning

Details

docset/mdop/agpm/add-controlledgpo.md
:warning:Warning

Details

docset/mdop/appvclient/repair-appvclientconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvclient/remove-appvpublishingserver.md
:warning:Warning

Details

docset/mdop/appvclient/remove-appvclientpackage.md
:warning:Warning

Details

docset/windows/appvclient/Set-AppvClientConfiguration.md
:warning:Warning

Details

docset/mdop/appvclient/stop-appvclientconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvclient/unpublish-appvclientpackage.md
:warning:Warning

Details

docset/mdop/appvsequencer/update-appvsequencerpackage.md
:warning:Warning

Details

docset/mdop/appvserver/get-appvserverpackagedeploymentconfiguration.md
:warning:Warning

Details

docset/windows/appvclient/Get-AppvClientPackage.md
:warning:Warning

Details

docset/mdop/appvserver/publish-appvserverconnectiongroup.md
:warning:Warning

Details

docset/windows/appvclient/Mount-AppvClientPackage.md
:warning:Warning

Details

docset/windows/appvsequencer/Update-AppvSequencerPackage.md
:warning:Warning

Details

docset/windows/appvclient/Sync-AppvPublishingServer.md
:warning:Warning

Details

docset/windows/appvclient/Repair-AppvClientConnectionGroup.md
:warning:Warning

Details

docset/mdop/appvclient/set-appvclientconfiguration.md
:warning:Warning

Details

docset/mdop/appvserver/grant-appvserverconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvserver/remove-appvserverpackage.md
:warning:Warning

Details

docset/mdop/appvserver/set-appvserverconnectiongrouppackage.md
:warning:Warning

Details

docset/windows/appvclient/Get-AppvClientConnectionGroup.md
:warning:Warning

Details

docset/mdop/appvserver/unpublish-appvserverpackage.md
:warning:Warning

Details

docset/windows/appvclient/Get-AppvClientApplication.md
:warning:Warning

Details

docset/mdop/appvclient/set-appvpublishingserver.md
:warning:Warning

Details

docset/mdop/mbam/get-mbambitlockerrecoverykey.md
:warning:Warning

Details

docset/mdop/appvserver/remove-appvserverconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvsequencer/new-appvsequencerpackage.md
:warning:Warning

Details

docset/mdop/appvclient/get-appvclientapplication.md
:warning:Warning

Details

docset/mdop/mbam/disable-mbamwebapplication.md
:warning:Warning

Details

docset/windows/appvclient/Remove-AppvClientConnectionGroup.md
:warning:Warning

Details

docset/mdop/appvserver/set-appvserverconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvserver/import-appvserverpackage.md
:warning:Warning

Details

docset/windows/appvclient/Set-AppvPublishingServer.md
:warning:Warning

Details

docset/windows/appvsequencer/New-AppvSequencerPackage.md
:warning:Warning

Details

docset/mdop/mbam/enable-mbamcmintegration.md
:warning:Warning

Details

docset/mdop/appvserver/update-appvserverconnectiongroup.md
:warning:Warning

Details

docset/mdop/mbam/read-adrecoveryinformation.md
:warning:Warning

Details

docset/mdop/mbam/get-mbamwebapplication.md
:warning:Warning

Details

docset/windows/appvclient/Unpublish-AppvClientPackage.md
:warning:Warning

Details

docset/mdop/appvclient/start-appvvirtualprocess.md
:warning:Warning

Details

docset/mdop/appvserver/new-appvserverconnectiongroup.md
:warning:Warning

Details

docset/mdop/appvsequencer/new-appvpackageaccelerator.md
:warning:Warning

Details

docset/mdop/mbam/disable-mbamcmintegration.md
:warning:Warning

Details

docset/mdop/mbam/enable-mbamdatabase.md
:warning:Warning

Details

docset/mdop/appvserver/get-appvserverpackage.md
:warning:Warning

Details

This comment lists only the first 50 files in the pull request.

docset/winserver2012r2-ps/hyper-v/Add-VMNetworkAdapterExtendedAcl.md

Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2017-10-30'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/set-appvclientpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/set-appvclientmode.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/sync-appvpublishingserver.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/mount-appvclientpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Remove-AppvPublishingServer.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/agpm/add-controlledgpo.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/repair-appvclientconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/remove-appvpublishingserver.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/remove-appvclientpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Set-AppvClientConfiguration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/stop-appvclientconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/unpublish-appvclientpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvsequencer/update-appvsequencerpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/get-appvserverpackagedeploymentconfiguration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Get-AppvClientPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/publish-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Mount-AppvClientPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvsequencer/Update-AppvSequencerPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Sync-AppvPublishingServer.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Repair-AppvClientConnectionGroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/set-appvclientconfiguration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/grant-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/remove-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/set-appvserverconnectiongrouppackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Get-AppvClientConnectionGroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/unpublish-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Get-AppvClientApplication.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/set-appvpublishingserver.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/mbam/get-mbambitlockerrecoverykey.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-file-not-found] Invalid file link: 'index.md'.

docset/mdop/appvserver/remove-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvsequencer/new-appvsequencerpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvclient/get-appvclientapplication.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/mbam/disable-mbamwebapplication.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Remove-AppvClientConnectionGroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/set-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/import-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/windows/appvclient/Set-AppvPublishingServer.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvsequencer/New-AppvSequencerPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/mbam/enable-mbamcmintegration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/update-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/mbam/read-adrecoveryinformation.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-file-not-found] Invalid file link: 'index.md'.

docset/mdop/mbam/get-mbamwebapplication.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/windows/appvclient/Unpublish-AppvClientPackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-windows' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvclient/start-appvvirtualprocess.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvserver/new-appvserverconnectiongroup.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/appvsequencer/new-appvpackageaccelerator.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

docset/mdop/mbam/disable-mbamcmintegration.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/mbam/enable-mbamdatabase.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.

docset/mdop/appvserver/get-appvserverpackage.md

Line 0, Column 0: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'powershell-mdop' is not valid with 'ms.prod' value 'w10'.
Line 0, Column 0: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'v-anbarr' is not a valid Microsoft alias.
Line 0, Column 0: [Warning-ms-date-invalid] Invalid date format for 'ms.date': '2016-12-05'. Must be a date in format MM/DD/YYYY, no more than 30 days from today.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Reopening to run checks

Docs Build status updates of commit 771e70f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.
@dariomws @get-itips @tseward
Peer review needed for this PR. Thanks.

The same information can also be added to W2016 article.

@dhmhd This PR is good to go once the suggested changes have been applied. Thank you.

Docs Build status updates of commit 49f3ba2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (win10-ps)

docset/winserver2012r2-ps/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 49f3ba2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (win10-ps)

docset/winserver2012r2-ps/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit dcdd981:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (win10-ps)

docset/winserver2012r2-ps/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

close > reopen

Docs Build status updates of commit 27d2094:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (win10-ps)

docset/winserver2012r2-ps/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 27d2094:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (win10-ps)

docset/winserver2012r2-ps/hyper-v/Add-VMNetworkAdapterExtendedAcl.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


0.7.3 automatically adding d.ts to all imported files

With new 0.7.3:
typings install chai
typings ERR! message Unable to read "lib\Chai.d.ts.d.ts" from "chai". You should check the entry in "typings.json" is correct

chai exposes byself as:
import {Chai} from './lib/Chai.d.ts';
...

This is intentional, but a better fix will be in the next minor release. Previously we were accidentally stripping some content from extensions. We need to make sure type definitions don't reference the full paths. /cc @unional

Should be fixed in the definition now.


TRUEHD in m2ts

hi!
Compression mode in m2ts (with TrueHD)  is not detected correctly

Compression mode in m2ts (with TrueHD) is not detected correctly

Oops, fixed, for next version.

@JeromeMartinez please also pay attention to the Stream size, it it also incorrect, must be larger

True, I reopen the ticket for the bitrate part, will be longer to implement (not sure about how I'll show that, I know the core bitrate but I don't know the global bitrate due to TS which does not store such info, I need to reorganize a lot of code for a good and generic handling of such kind of stream)

@JeromeMartinez TrueHD havent the core... i could be wrong, but the container holds two different streams: AC3 (640kbps) and TrueHD (8Mbps)

BTW. 31.250 fps is wrong. That must be 1200 fps. I suppose it reads PTS from MPEG-TS, but it should real PTS from raw .thd.

@JeromeMartinez
now is Compression mode   corret
but Stream size must be sum TrueHD stream+AC3(substream)Stream extension


Reduce redundant decoder forward passes by leveraging word-level timestamps

The goal is to leverage the high-quality word-level timestamps added in #38 as anchors to reliably seek the audio buffer forward at a higher frequency compared to current behavior:

Current behavior is to seek the audio forward if <|endoftext|> is generated or max_tokens tokens are generated.
Current behavior results in wasteful compute because each text token is re-decoded until the audio seeks beyond them.
This is up to 29 times redundant (worst case) for a 1 second audio refresh rate and a 30 second audio window for Whisper.

References:
[1] https://arxiv.org/abs/2005.11185
[2] https://arxiv.org/abs/2307.14743


Route53 acceptance tests hang

The immediate cause seems to be a Puppet hang while cleaning up test resources, e.g. while deleting AAAA and NS records. Disabling subsets of the tests did not resolve the issue. This may indicate bigger issues with the Route53 implementation.

I just realized this is a duplicate of #358


Add doc8 run to CI and lint checks

Summary
This commit adds running doc8 to our normal CI and lint workflows. Right
now we don't have any doc verification (aside from what pylint enforces
on docstrings in the tests, which doesn't get published anywhere) and when
it comes time to publish a new release there is a scramble to fix all the
warnings (and potentially errors) in the documentation. By running doc8 we
can verify that our documentation is formatted properly for sphinx to
compile the output without issue (and without any warnings).
Details and comments
The ipython requirement added in the tox.ini is necessary for doc8/pygments to be able to parse the jupyter noteboook code examples. If ipython isn't installed it's not able to parse the code blocks.

@jaygambetta this should be good to go now, I fixed all the issues reported by doc8 on the current master

Adding some numbers to better aid the discussion, comparing the make doc output of master and the changes in this PR - mostly using grep WARNING over the full documentation:

master
PR 52

total warnings
333
309

docstring warnings
245
245

non-docstring warnings
88
64

tox lint time
33s
83s

The numbers are just for reference and might vary a bit, but I think shed some light about the tradeoffs: our main source of warnings is the autodocs (ie. the docstrings), which are not tackled by the automatic linting - and for the non-docstring warnings, the linter is able to catch 22 of them, but most of them (64) still remain. Looking at the big picture and at the current PR and versions, we are arguably trading off ~50s in each build plus some strain on each contributor for solving ~7% of the warnings, which I personally think is not a good balance.
I think we basically will not be able to escape doing a round of manual fixing for those remaining warnings at one point or another, as the linter would not be able to pick a number of them, and would be more efficient to take advantage of that. What about:

have a plan for revising the warnings periodically (for example, before a major release) and do some style fixes locally if needed
place some effort in collaborating with each component's team for fixing the docstrings
for practical purposes, turn this PR into the first of those periodical ones (ie. keep the .rst changes themselves, to avoid losing the work and also aim for merging soon to avoid conflict solving, which I assume has not been too fun)

(For master, a341df0 was used; for the PR column, 2727dff was used (rendering both with the full stable autodocs, to avoid missing file warnings and replicate what finally gets pushed to the landing site). The lint time is based on the travis builds, although it probably has a wide variance.)

I see @diego-plan9 point but for this repo, it should not be run too many times. I am good with this addition as it picks up a few more errors. If we start to see this take too much time of travis lets reconsider this change.
@mtreinish can you fix the conflicts and then i approve so you can merge

@jaygambetta This can merge now


define Cursor#list for accessing event Dicts on a per-span basis

fixes #53
@xnomagichash what do you think of naming it list()?
at first, i was thinking events(), but really, it returns a list of spans where each span specifies the events it contains. this feels similar to dataframe()...except we're returning a list.

Using list as a method name is generally frowned on in python because it overrides the list top-level type. You can define the various methods that work with the list() function, but I'd stay away from that as a method name.
Also, it can't just be a list of events. We should probably rethink this.


gapi.client.request to cloudprint breaks with 404 error on  https://www.google.com/static/proxy.html.....

I'm trying to send a print job to the google cloud print api but it throws an 404 error after trying to reach this link
https://www.google.com/static/proxy.html?usegapi=1&jsh=m;/_/scs/apps-static/_/js/k=oz.gapi.es.ktq2e3L1j68.O/m=__features__/am=AQE/rt=j/d=1/rs=AGLTcCNotQl5iyROTuxOGXS-vOM3mN7FPA
How to reproduce the error?
gapi.load('client', () => gapi.client.init({
             'apiKey': MY_API_KEY
            'clientId': 'MY_CLIENT_ID.apps.googleusercontent.com',
            'scope': 'https://www.googleapis.com/auth/cloudprint'
        })
            .catch(e => console.error(e))
            .then(() => gapi.client.request({
                    method: 'POST',
                    path: 'https://www.google.com/cloudprint/submit',
                    body: {
                        printerid: MY_PRINTER_ID,
                        jobid: '',
                        title: 'HELLO WORLD',
                        contentType: 'text/html',
                        content: `HELLO WORLD`,
                        ticket: '{ "version": "1.0", "print": {}}'
                   }
                }))
            .then((response) => console.log(response.result),
                (reason) => console.log('Error: ' + reason.result.error.message))
            .catch(e => console.error(e)))

Thanks for any help

That API for Google Cloud Print predates API standardization at Google and does not work with the Google APIs Client Library for JavaScript. To use it you will need to follow its specific instructions: https://developers.google.com/cloud-print/docs/appDevGuide


Show city in tooltip even when using manual lat/lon

Use city returned by OpenWeatherMap.org when using manually entered lat/lon.  Normally app uses city from ip-api.com, so when we're bypassing that, we don't have a city to use in the tooltip.

Added ability to grab city from openweathermap.org in version 1.3.0