add in compatability with newer versions of openvino

Motivation and context

See this issue for additional context: https://github.com/opencv/cvat/issues/1830
this ended up being an easier fix than I anticipated
How has this been tested?

I have tested this using a locally compiled OpenVino version that has the latest changes in it. I do not have a previous version of OpenVINO to test this on.
Checklist

[ x ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ x] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[ x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Pull Request Test Coverage Report for Build 6275

0 of 5 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 65.142%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cvat/apps/auto_annotation/inference_engine.py
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

datumaro/datumaro/components/extractor.py
1
91.01%

Totals

Change from base Build 6272:
-0.02%

Covered Lines:
11049

Relevant Lines:
16552

💛  - Coveralls

@benhoff , thanks for all your support and help. We are going to remove the code. Thus I will close the PR.


Mosdepth multithread SIGSEGV error

When running the template gatk variant2 pipeline with multiple threads (bcbio_nextgen.py
-n 44 -t local ../config/bcbio_project_multhread.yaml) I get the error from mosdepth:
  File "bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/coverage.py", line 238, in run_mosdepth
    do.run(cmd.format(**locals()), message.format(**locals()))
  File "bcbio/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 23, in run
    _do_run(cmd, checks, log_stdout, env=env)
  File "bcbio/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 103, in _do_run
    raise subprocess.CalledProcessError(exitcode, error_msg)
subprocess.CalledProcessError: Command 'set -o pipefail; export MOSDEPTH_Q0=NO_COVERAGE && export MOSDEPTH_Q1=LOW_COVERAGE && export MOSDEPTH_Q2=CALLABLE && mosdepth -t 44 -F 1804 -Q 1 --no-per-base --by bcbio_project_multicore/work/coverage/SAMPLE-1/target-genome.bed --quantize 0:1:4: bcbio_project_multicore/work/bcbiotx/tmphwmctq/SAMPLE-1-variant_regions bcbio_project_multicore/work/align/SAMPLE-1/SAMPLE-1-sort.bam
SIGSEGV: Illegal storage access. (Attempt to read from nil?)
' returned non-zero exit status 1

It appears that this could have been arising from an old version of htslib  but my bcbio installation is using htslib 1.9.
In addition, I added the following to the end of my run config yaml file:
...
upload:
  dir: ../final
resources:
  mosdepth:
    cores: 1

but when I bcbio_nextgen.py with -n 44, it still runs mosdepth with 44 cores despite my specification that mosdepth should be run with 1 core. I would prefer not to run my whole project with 1 core. Am I doing something wrong?

Kendall;
Apologies about the issue. I haven't seen this problem with mosdepth before and have been trying to reproduce on different installs and can't seem to replicate. Would you be able to describe the system you're running on and the versions of mosdepth and htslib in your install?
$ bcbio_conda list | grep mosdepth
$ bcbio_conda list | grep htslib

It does seem like it's having problem with your shared filesystem but I'm not yet sure how to track down and fix. Does this happen consistently on every run, or is it dependent on how busy the filesystem is?
Apologies about the confusion with core configuration as well. Those are meant as hints to determine maximum cores for allocation, rather than specifications for defining exactly how many cores to use. We could try and provide a workaround if we can't isolate and fix the underlying problem. Thanks again for the report and help debugging.

Hi Brad,
Thanks for looking into this. We're running on a single machine with a local, high-speed hard drive.
I ran it three times with multiple cores, and it failed every time with this same error. I then ran it with only one core and it finished (albeit very slowly).
Here are the outputs from the commands you listed:
$ bcbio_conda list | grep mosdepth
mosdepth                  0.2.3                h99d1a69_0    bioconda
$ bcbio_conda list | grep htslib
hts-nim-tools             0.1.5               htslib1.7_1    bioconda
htslib                    1.7                           0    bioconda

However, if I run
$ samtools --version
samtools 1.9
Using htslib 1.9
Copyright (C) 2018 Genome Research Ltd.
$ which samtools
/bcbio/software/bin/samtools

So it appears that conda's htslib 1.7 may be causing this error?

Kendall;
Thanks for following up. I'm agreed that updating the latest mosdepth with htslib 1.9 would be the next thing to try to see if it helps. I just fixed a package blocking this so if you now do:
bcbio_conda install -c conda-forge -c bioconda mosdepth=0.2.3=he527e40_1

It should hopefully give you the latest version along with upgrading other tools built against htslib 1.9.
Fingers crossed this will avoid the issue and get you a clean run. Thanks for the help debugging this.

Thanks, this is old and is an install issue so should be all set now.


chore: add test coverage for after_paste_window_ready callback

:tada: This issue has been resolved in version 4.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add support for message position

General Troubleshooting

[X] I have checked for similar issues on the Issue-tracker.
[X] I have updated to the latest JDA version
[X] I have checked the branches or the maintainers' PRs for upcoming features.

Feature Request
https://discord.com/developers/docs/resources/channel#message-object
position:
A generally increasing integer (there may be gaps or duplicates) that represents the approximate position of the message in a thread, it can be used to estimate the relative position of the message in a thread in company with total_message_sent on parent thread
Example Use-Case
var position message.getPosition();

if(position == 0) {
    log.info("Is first message");
}

Can you provide a more concrete use-case of why you need this?

My use case would be to prevent people from using my bot by reacting on a message that's too old / too far away (the bot would only watch in threads anyway)

Available in 5.0.0-beta.4


Support run with --rm option

Docker allows starting new instances with the --rm option; what it does is, after the container execution ends, the container is removed.
If there is interest, I can submit a pull request.

@rjperes I think this goes beyond this library's responsibility, it's a client-side operation that can be already done by using the methods from this client library.
Wouldn't it be simply
try { run() } finally { rm() }

?

Also --rm can be used only when you're attaching to the container in interactive mode. I'm not sure if there's anybody using this library in interactive mode, .NET simply doesn't have an http hijacking implementation.

 Apparently, there was a discussion to move it to the daemon, but it has gone nowhere.
I'm gonna close this issue, as it doesn't make sense.


Docker-compose

Describe the solution you'd like
Create a dockerized version of Bulwark for easy & fast deployment with docker-compose.
Describe alternatives you've considered
https://docs.docker.com/compose/
Additional context
I'm the maintainer of the Rawsec Inventory, I recently added Bulwark to the Collaboration and Report category. I think the most similar project out there is pwndoc. They have a docker-compose that you can use as an example.

@noraj Thank you for the information.  We have had this on the backburner but it is now a good time to implement this.
cc @skewled

I'm the maintainer of the Rawsec Inventory, I recently added Bulwark to the Collaboration and Report category.

Awesome! Just FYI, it's misspelled in the inventory (remove the extra L).

it's misspelled in the inventory (remove the extra L).

It will be fixed in a few minutes.

@noraj We added steps for easy deployments with docker-compose.  If you are interested, the steps are located on the README.
https://github.com/softrams/bulwark#launch-with-docker


Want to create Mobile Application with the Help Of React Native

Hello, I'm eager to contribute to Plant disease detection mobile application with the help of React Native. Could you please provide guidance on how I can get involved?
Thanks,
Ishita Sharma #Yogesh


Development on hiatus as I have exams coming in May

I might return briefly to developing this around late May to early June.

 Project development CONTINUED until further notice.


Start SharedTree workspace VSCode terminals in root directory

This is for convenience since command line tools (npm i, lerna) are generally invoked from the root of the FluidFramework package.
Newly created terminals in VSCode will start in FluidFramework rather than FluidFramework/experimental/dds/tree

When I open a specific project in FF in vscode, I usually am doing so because I want to run commands in that specific directory (just build, test or debug that specific project).
Thus this seems counter productive to me.
Given that there are reasons to start in either directory, and starting in fluid framework's top level is more surprising (our other packages don't do that), and is hard to recover from (its easier to navigate to parent directories than to find specific child directories), I personally don't think this is a good change.

When I open a specific project in FF in vscode, I usually am doing so because I want to run commands in that specific directory (just build, test or debug that specific project). Thus this seems counter productive to me.
Given that there are reasons to start in either directory, and starting in fluid framework's top level is more surprising (our other packages don't do that), and is hard to recover from (its easier to navigate to parent directories than to find specific child directories), I personally don't think this is a good change.

This does not affect opening the project directory though. Opening the shared tree directory via VSCode and opening the shared tree workspace file are two different things. The former is what you want in your case, and still works just fine. The latter is designed specifically for this case - it's a way to open the FluidFramework repo as a whole and also have easy access to just the shared tree package.


added Latvian language

Added Latvian (lv) language.
My address:
62e2762010196c45ec6d06a218db6ae37816d5ab2e7cd37f9b4e01d016917cf4

@Zims On google translate, it shows - Healthy World. Are you sure this is the correct translation?

Healthy and "sveika" have close to the same meaning but "Sveika pasaule" is def. correct.
Google translate doesn't get the context

@odetolataiwo I have paid this earlier. Don't send coins. Can you make sure this is logged into the system?

@odetolataiwo I have paid this earlier. Don't send coins. Can you make sure this is logged into the system?

done


Set values in form

I load a form via ajax and i set this such as content, i am trying set the values to the inputs of this form, but when the form is showing the form is reset automatically

you must know that every element in the Content will be destroyed when you Close the jquery-confirm. so when you reopen it, all values will be reset.  If you want to set the values on open event use the "onOpenBefore" or "onContentReady" (see Callbacks in the dokumentation).

I appreciate your attention, I have read the documentation but those calls are not available for the version I use, I am currently working with the version 2.5.1

@cesarfinal1
I highly suggest to update.


[HxInput] Allow Input controls to add styles to the InputGroup

Please add an InputGroupCssClass property to HxInputBaseWithInputGroups and leverage it where appropriate to let me implement this feature of Bootstrap.

This could be achievable with InputGroupCssClass or (my preferred solution) InputGroupSize="InputGroupSize.Large" that would be applied only if InputGroupStartTemplate or InputGroupEndTemplate  is present. @hakenr what do you think?

So, using a string property instead an enum would also let you implement the "nowrap" feature just above the link I provided. I think that people are going to need to add classes to the input group, and just letting you manipulate the string covers more scenarios than having to implement specific enums for each feature on that Bootstrap documentation page.

I think that we will end up with both. But as far as we set the Input and Buttons sizes with Enums, we should stick with it in this scenario as well. For the "nowrap" case the InputGroupCssClass si clear.

Makes sense! Thanks for making this happen :)

Will look into it. I think we should not add InputGroupSize but rather use InputSize and apply the requested size correctly to input-groups scenario.

Current state: InputGroupCssClass is already there (comes from IFormValueComponentWithInputGroups) and should be rendered whenever set. Now we have to adjust the InputSize usage to set correct input-group-size when set.

@Harvey1214 Use IInputWithSize.InputSizeEffective and add input-group-sm or input-group-lg as needed (see https://getbootstrap.com/docs/5.1/forms/input-group/#sizing)


Expo Config Plugins Dependency for non-Expo apps

Prerequisites

[X] I checked the documentation and FAQ without finding a solution
[X] I checked to make sure that this issue has not already been filed
[X] I'm sure that question is related to the library itself and not Bluetooth Low Energy or Classic in general. If that so, please post your question on StackOverflow.
[X] I'm running the latest version

Question
With expo support added in v3.1.0, @expo/config-plugins has been added as a required dependency.  My project does not use expo and therefore I do not need this, but because it is a dependency of the package, it now gets pulled in.
Is it possible to utilize v3.1.0+ without requiring @expo/config-plugins?

@rnigro-rwb hi! thanks for the report. we'll get back to you soon. thanks for your patience 🙏

Hi @rnigro-rwb
From what I know @expo/config-plugins is being installed with the package (by js package manager), yet because you are not using any of plugin files the @expo/config-plugins is not being bundled in your final js file, and so should not affect your project.
The way of adding plugin for expo is established by expo itself.
I hope it answers your question in case of any problems please elaborate on the issue

Hi @rnigro-rwb
Do you still need help with the issue?


Feature request: "Anonymise Names" text transformation

Original author<EMAIL_ADDRESS>(November 01, 2010 21:22:25)
What feature would you like?
I would like to quickly be able to anonymise text in cells. While this is outside the original scope of Refine, e.g. cleaning & inputting data into Freebase, it would be a valuable transformation for agencies that are attempting to release sensitive info.
Here is a naive approach:

split the string into n-length characters
replace each letter with a randomly chosen letter, retaining the case
join characters together as a string

Original issue: http://code.google.com/p/google-refine/issues/detail?id=174

I don't think this is in the scope of the project. And it's very old.

This could be an OpenRefine extension to determine risk of PII leakage and give users options for anonymizing data with various algorithms.  See feature enhancement request #5642


[BUG]

Details
Spigot Version:
please run /ep debug and attach a screenshot

Describe the bug
i can type /suffix or /prefix to change my prefix without any permission

Expected behavior
it will show you don't have permission
Screenshots

Fixed.
Thank you!


Support repository_dispatch on Gitea Actions

Feature Description
I know gitea actions are brand new, but I'm quite enjoying them already. However, I'd like a way to trigger tests of one repo by committing to another (the two repos' tests are tangentially dependent).
For this end, I'd like to request the following feature - repository_dispatch
On GitHub, this allows one repo to send a message to another's action runner.
Thanks in advance.
Screenshots
No response

This is very important, now I want to implement a version rollback function is very troublesome.

I need it as well!

I also need this (to implement build chains).


fix(pkg/kube): validate with OpenAPI on install

the only other spot I was wondering about is whether test hooks should be validated as well, since they are not part of the execution hooks or the rendered manifest. What do you think, @adamreese?

nvm, after looking at the code, that's just test hooks to be deleted. LGTM!


Change Updates URL to updates.brackets.io

Changing the brackets updates(check for new versions/updates) URL.

This has been done in 1.4 pending issue #11482 . Closing This issue.


Set up entrypoint to AVL tree visualiser

I also added the AVL tree topic document in MongoDB. The AVL tree card should now link to the AVL tree visualiser dashboard (which is still reusing the BST visualiser until the AVL tree visualiser is added).


Bug: Newly Created Excel File(s) Not Visible on network location

Description
I created a new .xlsx file on a samba network drive via right-click, new, excel worksheet and depending on the filename it will either immediately disappear or disappear after a right-click refresh.  I looked on the samba server itself and the file is there as well as visible in the traditional file explorer.  I've opened & closed Files to no avail.  I further tested creating both .xls and .xlsx files directly in excel and saving them to the network drive via excel save-as and both filetypes do not show up in Files.  The drive in question is formatted as an NTFS drive. At the current time I do not have a drive available to test with a different file system though I will in a week's time.
I've performed the same right-click new, on a .txt & .docx file and they appear to function normally.  I also created a new .xlsx file on a normal system drive (a second drive on my pc in this case) via right-click, new and the file is visible like normal so it appears this is a network drive issue or maybe specific to a mapped samba server drive.  I should further clarify that there are already .xlsx files on the drive and those are visible in Files.  This bug pertains to newly created excel sheets from windows (regardless of method used) onto the network drive.
When I deleted test files en-masse via File Explorer while Files was open, I saw Files flash a few times so at the very least Files knows they are there but not making them visible.
Steps To Reproduce

Create a new excel spreadsheet on a network drive (possibly specific to samba server network drive)
File is created but not visible by Files

Requirements
Ensure excel file type is visible on network drive.
Files Version
<IP_ADDRESS>
Windows Version
11 Pro 10.0.22631.3007
Log File
debug.log

Thank you for the report


feat(tutorial): complete step 5 - BOEBLINGEN

App URL

https://carbon-tutorial-dkaulen.mybluemix.net/#/

@daka1510 Looks fantastic 💯! I've recorded your completion of step 5.
Feel free to stop your running application on IBM Cloud to avoid the possibility of incurring any charges.


Marriage abroad changes Egypt

Pivotal Tracker: https://www.pivotaltracker.com/projects/1270592/stories/109438156

Remove bullet point starting with "your [full birth certificate]"

Factcheck
https://smart-answers-pr-109438156.herokuapp.com/marriage-abroad/y/egypt/ceremony_country/partner_british/opposite_sex
Expected Changes
URL
* Remove bullet point with birth certificate and naturalisation certificate requirement
Before

After

This looks good to me.
As an aside, I find it useful to highlight the text that changes in the screenshots. It makes it easier to see at a glance what we're expecting to change.

@chrisroos will adopt that.. cheers


pio_proc::pio_file is only picking up file changes after a cargo clean

As the title says, pio_proc::pio_file seems to only pick up changes to the pio file after a cargo clean call and not otherwise.
If it is supposed to be this way I'd ask to at least reflect that in the documentation

@JomerDev I tried to reproduce this, but noticed that rust usually seems to pick up changes immediately, without needing a cargo clean. But this only works when the pio file is inside your source directory.
(I'm not saying that this isn't still a bug that should be fixed. I just try to fully understand what's happening.)

I got the issue inside embassy's examples directory. The pio file was also inside the same directory next to the code.
It could of course be that calling cargo run --bin pio_uart makes rust behave differently/ignore files with paths

I got the issue inside embassy's examples directory. The pio file was also inside the same directory next to the code. It could of course be that calling cargo run --bin pio_uart makes rust behave differently/ignore files with paths

Thank you, I was able to reproduce the issue. #54 should solve the issue, but is not yet tested sufficiently.

I'd love to see this get resolved. Let me know if there's anything I can do to help test.


Prepare infrastructure for C reimplementation of SonnetAmiga

[x] Repository
[ ] Build system
[ ] Plug into Jenkins

See #48 .

@DvdBoon How do we call the new implementation of SonnetAmiga? I suppose the new repository should be appropriately called.

PowerpcAmiga? Also, when do you expect files from me? I am doing this through cubeide and I have a makefile, an options file (i guess should be merged into the makefile) and one c file so far.

Any time you're ready. I'll let you know when the repo is ready, then you can send me necessary files.
If there's a GNU-compatible Makefile I am sure I can figure out how to automate the build.

CVS module "PowerPCAmiga" is ready.

Sending the files later today. If not, it will be Monday as I will be not available during the weekend.

I asked Elbox for permission to use the NDK on the git server.


[Tests] added more test cases

Some issues are found:

async function with params doesn’t work
rest element with default value doesn’t work correctly, in both objectPattern and arrayPattern
async for of  test case will lead to hang up,  which are commented out by default. Please uncomment after merging  in statement.test.ts

I will fix it when I have time


[patch] slipped to 1.21

r? @matklad
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 32beb11 has been approved by alexcrichton

:hourglass: Testing commit 32beb11aa72b92e73832626220a53718fe60319a with merge 31dd4e37d819c7eeb13388f8d92165c93cef5e9b...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 31dd4e37d819c7eeb13388f8d92165c93cef5e9b to master...


simple memory cards game js

Please go through the readme file and update your projects directory, plus add a few screenshots and working project link here


Do not show preview

Dear @daved01
I downloaded your repo, and tried on my iPad(ver15.7).
Program can run, and show the camera access, and granted, but cannot show any, just white blank.
Some thing wrong for my environment?
My Xcode is Version 14.0.1 (14A400)
I changed
guard let videoDevice = AVCaptureDevice.default(for: .video) else { return }
it works for my iPad.

Self closed


Allow translated strings in the help property

We use a lot of translated help texts in our projects. This fixes a lot of messages ;)
I took the liberty of taking gnuj test array.

@duncan412 thanks!


Unexpect excrption (divide by zero) on fast interpreter mode

Build commands
I compile the code with commit id 92bf8547aa64dddad2ecd387a352f89bbc475c88.
Platform: Ubuntu 20.04
CPU: amd64
compile:
export CC=/usr/lib/llvm-16/bin/clang
export CXX=/usr/lib/llvm-16/bin/clang++
cd product-mini/platforms/linux/;rm -rf build
cmake  -DWAMR_BUILD_INTERP=1 -DWAMR_BUILD_REF_TYPES=1 -DWAMR_BUILD_SIMD=1 -DWASM_ENABLE_BULK_MEMORY=1 -DWAMR_BUILD_AOT=0 -DCMAKE_BUILD_TYPE=Release -DWAMR_BUILD_FAST_INTERP=1 -DWAMR_BUILD_LIBC_WASI=0 -DWAMR_BUILD_LIBC_BUILTIN=1 -Bbuild

execute:
iwasm --heap-size=0  <tc_name>

Cases
iwasm_fast_jit_unexpected_devide_by_zero.zip
Actual behavior:
Exception: integer divide by zero

Expected behavior:
No exception

Fast JIT works normal, it should be the issue of fast-interp according to the build command and test result.

There is a typo in the title and I have fixed it now.

Thanks for reporting this, we've fixed in https://github.com/bytecodealliance/wasm-micro-runtime/pull/2974

Close this issue since it was fixed.


Use prop-types package

This remove warning messare related with React.propTypes is deprecated.

Nice! Can you release a new patch version? If 😄

Sure! I'm on the road right now. Will do it first thing tomorrow
On Mon, Jun 19, 2017 at 1:18 PM Kiko Beats<EMAIL_ADDRESS>wrote:

Nice! Can you release a new patch version? If 😄
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/vsubbotskyy/React-dotdotdot/pull/4#issuecomment-309399133,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHaFO0Vpyu2iSNX2RC0yUccXl1iuF2KPks5sFksLgaJpZM4N93Ix
.

--
regards,
Subotsky Vitaliy.

what about that? I can do it if you give me permissions 😄

I've added you as collaborator, will it do? I thought you meant to tag a new release, but I see that it's not that). If I can help you with what you need to accomplish please let me know

@vsubbotskyy thanks! Add me to npm registry as well for publish the new version:
npm owner add kikobeats react-clamp

of course you meant npm package, sorry I even forgot I own it)


GPII-2179: Pin to a published version of infusion that includes deletion relaying and new transforms.

See https://issues.gpii.net/browse/GPII-2179 for details.

@amb26, this should be reviewed once the infusion and docs PRs are merged.

@amb26, I propose reviewing the upcoming changes for GPII-2267 (improved cleanup) in this PR rather than creating a new one.

@the-t-in-rtf - sounds good to me!

@amb26, I have committed the changes.  In addition to confirming everything working with the existing persistence tests, I also closely monitored the temp directory during multiple runs.  All created temp directories are cleaned up.

Running tests/js/all-tests.js on this branch still leaves behind one PouchDB database in Temp, with the following contents:
C:\Users\Bosmon\AppData\Local\Temp>ls -ltr gpii-pouch-express-persistent
total 21
drwxrwx---+ 1 Bosmon None   0 Feb  3 14:50 _replicator
drwxrwx---+ 1 Bosmon None   0 Feb  3 14:50 pouch__all_dbs__
drwxrwx---+ 1 Bosmon None   0 Feb  3 14:50 _users
-rwxrwx---+ 1 Bosmon None 153 Feb  3 14:50 config.json
drwxrwx---+ 1 Bosmon None   0 Feb  3 14:50 persistence
drwxrwx---+ 1 Bosmon None   0 Feb  3 14:50 persistence-mrview-4571caff952754210024696e3967ac5b

Also - can you tell me how I can prevent testem from firing up Internet Explorer on my machine? I tried adding strings of various forms to this line in package.json but none of them worked:
"test:browser": "node node_modules/testem/testem.js ci --skip safari,phantomjs"

That content is clearly from the persistence tests, which are provisioned once and reused over a couple of restarts.  I'll have to add a final bit of cleanup.

I have hardened the persistence tests so that no content remains after the run.
I also confirmed that the following skips the IE tests on the standard Vagrant Windows 7 VM:
node node_modules/testem/testem.js ci --skip IE
The allowed values for the skip option can be determined using the following command:
node node_modules/testem/testem.js launchers

I also double-checked that there was no problem using "IE" in combination with other skips, the following (for example) worked for me:
node node_modules/testem/testem.js ci --skip safari,phantomjs,IE
@amb26, this should be ready for further review.

Thanks for the help on IE skipping, those options work for me! The cleanup code is looking promising, but it looks like there is some form of race condition during the cleanup - I'm unable to run the tests to conclusion, they always finish with a hang, and then a deferred rejection failure for one or other of the files in gpii-pouch-express-persistent - here are two samples:
14:14:37.128:  jq: Test concluded - Module "Testing persistence within a single restart..." Test name "Confirm that we have indexed records after a restart...":
 2/2 passed - PASS
14:14:37.149:  express pouchdb instance '920mr2ob-3087' initalizing...
14:14:37.174:  express baseDir: 'C:\Users\Bosmon\AppData\Local\Temp\gpii-pouch-express-persistent'...
14:14:37.177:  Express stopped...
14:14:37.177:  Express server listening on port 6798
14:14:37.178:  Express started...
14:14:37.181:  This database already has one or more records, no data will be loaded...
14:14:37.181:  Data loaded for database 'persistence'...
14:14:42.187:  Test case listener has not responded after 5000ms - at sequence pos 4 of 4 sequence element {
    "event": "{getAfterResetRequest}.events.onComplete",
    "listener": "jqUnit.assertEquals",
    "args": [
        "There should no longer be a record.",
        404,
        "{getAfterResetRequest}.nativeResponse.statusCode"
    ]
} of fixture Confirm that the record is no longer there after cleaning up the data and recreating express-pouchdb...
14:14:49.945:  Failure in task fixture {
    "task": "{harness}.cleanup",
    "resolve": "{getAfterResetRequest}.send",
    "resolveArgs": []
}: promise has received disposition "reject" with payload {
    "errno": -4082,
    "code": "EBUSY",
    "syscall": "unlink",
    "path": "C:\\Users\\Bosmon\\AppData\\Local\\Temp\\gpii-pouch-express-persistent\\pouch__all_dbs__\\LOG"
} when "resolve" was expected
14:14:49.949:  jq: FAIL: Module "Testing persistence within a single restart..." Test name "Confirm that the record is no longer there after cleaning up the dat
a and recreating express-pouchdb..." - Message: Failure in task fixture {
  "task": "{harness}.cleanup",
  "resolve": "{getAfterResetRequest}.send",
  "resolveArgs": []
}: promise has received disposition "reject" with payload {
  "errno": -4082,
  "code": "EBUSY",
  "syscall": "unlink",
  "path": "C:\\Users\\Bosmon\\AppData\\Local\\Temp\\gpii-pouch-express-persistent\\pouch__all_dbs__\\LOG"
} when "resolve" was expected
14:14:49.951:  jq: Source:     at pok (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\jqUnit\js\jqUnit.js:112:15)
    at Object.fail (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\jqUnit\js\jqUnit.js:129:13)
    at Array.<anonymous> (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:273:20)
    at Object.that.complete (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\FluidPromises.js:70:25)
    at Object.that.reject (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\FluidPromises.js:61:22)
    at E:\source\gits\gpii-pouchdb\src\js\pouch-express.js:9:7741
    at next (E:\source\gits\gpii-pouchdb\node_modules\rimraf\rimraf.js:74:7)
    at CB (E:\source\gits\gpii-pouchdb\node_modules\rimraf\rimraf.js:110:9)
    at E:\source\gits\gpii-pouchdb\node_modules\rimraf\rimraf.js:250:18
    at next (E:\source\gits\gpii-pouchdb\node_modules\rimraf\rimraf.js:74:7)
    at CB (E:\source\gits\gpii-pouchdb\node_modules\rim .... [output suppressed at 1024 chars - for more output, increase fluid.logObjectRenderChars]

and
14:15:48.251:  jq: Test concluded - Module "Testing persistence within a single restart..." Test name "Confirm that we have indexed records after a restart...":
 2/2 passed - PASS
14:15:48.283:  express pouchdb instance '15zga6yo-3087' initalizing...
14:15:48.307:  express baseDir: 'C:\Users\Bosmon\AppData\Local\Temp\gpii-pouch-express-persistent'...
14:15:48.309:  Express stopped...
14:15:48.309:  Express server listening on port 6798
14:15:48.310:  Express started...
14:15:48.312:  This database already has one or more records, no data will be loaded...
14:15:48.312:  Data loaded for database 'persistence'...
14:15:53.317:  Test case listener has not responded after 5000ms - at sequence pos 4 of 4 sequence element {
    "event": "{getAfterResetRequest}.events.onComplete",
    "listener": "jqUnit.assertEquals",
    "args": [
        "There should no longer be a record.",
        404,
        "{getAfterResetRequest}.nativeResponse.statusCode"
    ]
} of fixture Confirm that the record is no longer there after cleaning up the data and recreating express-pouchdb...
14:16:01.052:  Failure in task fixture {
    "task": "{harness}.cleanup",
    "resolve": "{getAfterResetRequest}.send",
    "resolveArgs": []
}: promise has received disposition "reject" with payload {
    "errno": -4082,
    "code": "EBUSY",
    "syscall": "unlink",
    "path": "C:\\Users\\Bosmon\\AppData\\Local\\Temp\\gpii-pouch-express-persistent\\pouch__all_dbs__\\000004.log"
} when "resolve" was expected
14:16:01.056:  jq: FAIL: Module "Testing persistence within a single restart..." Test name "Confirm that the record is no longer there after cleaning up the dat
a and recreating express-pouchdb..." - Message: Failure in task fixture {
  "task": "{harness}.cleanup",
  "resolve": "{getAfterResetRequest}.send",
  "resolveArgs": []
}: promise has received disposition "reject" with payload {
  "errno": -4082,
  "code": "EBUSY",
  "syscall": "unlink",
  "path": "C:\\Users\\Bosmon\\AppData\\Local\\Temp\\gpii-pouch-express-persistent\\pouch__all_dbs__\\000004.log"
} when "resolve" was expected
14:16:01.059:  jq: Source:     at pok (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\jqUnit\js\jqUnit.js:112:15)
    at Object.fail (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\jqUnit\js\jqUnit.js:129:13)
    at Array.<anonymous> (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:273:20)
    at Object.that.complete (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\FluidPromises.js:70:25)
    at Object.that.reject (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\FluidPromises.js:61:22)
    at E:\source\gits\gpii-pouchdb\src\js\pouch-express.js:9:7741
    at next (E:\source\gits\gpii-pouchdb\node_modules\rimraf\rimraf.js:74:7)
    at CB (E:\source\gits\gpii-pouchdb\node_modules\rimraf\rimraf.js:110:9)
    at E:\source\gits\gpii-pouchdb\node_modules\rimraf\rimraf.js:250:18
    at next (E:\source\gits\gpii-pouchdb\node_modules\rimraf\rimraf.js:74:7)
    at CB (E:\source\gits\gpii-pouchdb\node_modules\rim .... [output suppressed at 1024 chars - for more output, increase fluid.logObjectRenderChars]

System is Windows 7 x64, node 6.9.2 64-bit

Thanks, I will test with the standard windows VM to confirm, but I suspect I know exactly what's happening, as I had to migrate away from using fs.rmdir in another context for what I suspect are similar reasons.

Some improvement, but I now get either the following hang:
15:05:42.849:  Test case listener has not responded after 5000ms - at sequence pos 4 of 4 sequence element {
    "event": "{getAfterResetRequest}.events.onComplete",
    "listener": "jqUnit.assertEquals",
    "args": [
        "There should no longer be a record.",
        404,
        "{getAfterResetRequest}.nativeResponse.statusCode"
    ]
} of fixture Confirm that the record is no longer there after cleaning up the data and recreating express-pouchdb...

or else the following I/O error:
15:04:38.432:  This database already has one or more records, no data will be loaded...
15:04:38.432:  Data loaded for database 'persistence'...
Unhandled rejection OpenError: IO error: C:\Users\Bosmon\AppData\Local\Temp\gpii-pouch-express-persistent\_users/MANIFEST-000001: The system cannot find the fil
e specified.

    at E:\source\gits\gpii-pouchdb\node_modules\levelup\lib\levelup.js:119:34
    at E:\source\gits\gpii-pouchdb\node_modules\leveldown\node_modules\abstract-leveldown\abstract-leveldown.js:39:16

15:04:38.795:  Removed temporary directory 'C:\Users\Bosmon\AppData\Local\Temp\gpii-pouch-express-persistent'...
15:04:38.797:  Sending a GET request to: /persistence/new on port 6798
15:04:38.818:  jq: Test concluded - Module "Testing persistence within a single restart..." Test name "Confirm that the record is no longer there after cleaning
 up the data and recreating express-pouchdb...": 1/1 passed - PASS
15:04:38.840:  express pouchdb instance '21anfpy6-3722' initalizing...
15:04:38.841:  Creating directory 'C:\Users\Bosmon\AppData\Local\Temp\gpii-pouch-express-persistent' for express pouchdb instance '21anfpy6-3722'...
15:04:38.845:  jq: FAIL: Module "Testing persistence within a single restart..." Test name "Confirm that we have no indexed records after a reset..." - Message:
 Died on test #1     at Object.asyncTest (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\lib\qunit\js\qunit.js:405:9)
    at E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:651:29
    at Object.fluid.each (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:513:17)
    at Object.fluid.test.processTestCase (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:625:15)
    at E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:674:24
    at Object.fluid.each (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:513:17)
    at Object.fluid.test.processTestCaseHolder (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:667:15)
    at E: .... [output suppressed at 1024 chars - for more output, increase fluid.logObjectRenderChars]
15:04:38.848:  jq: Source: Error: EPERM: operation not permitted, mkdir 'C:\Users\Bosmon\AppData\Local\Temp\gpii-pouch-express-persistent'
    at Error (native)
    at Object.fs.mkdirSync (fs.js:922:18)
    at gpii.pouch.express.initExpressPouchdb (E:\source\gits\gpii-pouchdb\src\js\pouch-express.js:9:2502)
    at togo (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\FluidIoC.js:1796:33)
    at fire (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:1496:40)
    at Object.fire (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:1496:40)
    at Object.fluid.initComponent (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:2675:30)
    at creator (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:1929:30)
    at Object.fluid.invokeGlobalFunction (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:1113:25)
    at Object.fluid.initSubcomponentImpl (E:\source\ .... [output suppressed at 1024 chars - for more output, increase fluid.logObjectRenderChars]
15:04:38.850:  Express stopped...
15:04:38.864:  jq: Test concluded - Module "Testing persistence within a single restart..." Test name "Confirm that we have no indexed records after a reset..."
: 0/1 passed - FAIL
15:04:38.883:  express pouchdb instance '21anfpy6-3767' initalizing...
15:04:38.883:  Creating directory 'C:\Users\Bosmon\AppData\Local\Temp\gpii-pouch-express-persistent' for express pouchdb instance '21anfpy6-3767'...
15:04:38.887:  jq: FAIL: Module "Testing persistence within a single restart..." Test name "Clean up at the end of the run..." - Message: Died on test #1     at
 Object.asyncTest (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\lib\qunit\js\qunit.js:405:9)
    at E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:651:29
    at Object.fluid.each (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:513:17)
    at Object.fluid.test.processTestCase (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:625:15)
    at E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:674:24
    at Object.fluid.each (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:513:17)
    at Object.fluid.test.processTestCaseHolder (E:\source\gits\gpii-pouchdb\node_modules\infusion\tests\test-core\utils\js\IoCTestUtils.js:667:15)
    at E:\source\gits\gpii-pouch .... [output suppressed at 1024 chars - for more output, increase fluid.logObjectRenderChars]
15:04:38.890:  jq: Source: Error: EPERM: operation not permitted, mkdir 'C:\Users\Bosmon\AppData\Local\Temp\gpii-pouch-express-persistent'
    at Error (native)
    at Object.fs.mkdirSync (fs.js:922:18)
    at gpii.pouch.express.initExpressPouchdb (E:\source\gits\gpii-pouchdb\src\js\pouch-express.js:9:2502)
    at togo (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\FluidIoC.js:1796:33)
    at fire (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:1496:40)
    at Object.fire (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:1496:40)
    at Object.fluid.initComponent (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:2675:30)
    at creator (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:1929:30)
    at Object.fluid.invokeGlobalFunction (E:\source\gits\gpii-pouchdb\node_modules\infusion\src\framework\core\js\Fluid.js:1113:25)
    at Object.fluid.initSubcomponentImpl (E:\source\ .... [output suppressed at 1024 chars - for more output, increase fluid.logObjectRenderChars]
15:04:38.906:  jq: Test concluded - Module "Testing persistence within a single restart..." Test name "Clean up at the end of the run...": 0/1 passed - FAIL
15:04:43.822:  Test case listener has not responded after 5000ms - at sequence pos 2 of 5 sequence element {
    "listener": "fluid.identity",
    "event": "{testEnvironment}.events.onFixturesConstructed"
} of fixture Confirm that we have no indexed records after a reset...
15:04:43.866:  Test case listener has not responded after 5000ms - at sequence pos 2 of 3 sequence element {
    "listener": "fluid.identity",
    "event": "{testEnvironment}.events.onFixturesConstructed"
} of fixture Clean up at the end of the run...

Tests now pass again, but sadly we are back to the base directory not being cleaned up:
15:19:25.071:  Data loaded for database 'pouch__all_dbs__'...
15:19:37.968:  ERROR: Unable to remove base directory...
{
    "errno": -4082,
    "code": "EBUSY",
    "syscall": "unlink",
    "path": "C:\\Users\\Bosmon\\AppData\\Local\\Temp\\gpii-pouch-express-persistent\\_users\\000003.log"
}

and
15:19:51.546:  ERROR: Unable to remove base directory...
{
    "errno": -4082,
    "code": "EBUSY",
    "syscall": "unlink",
    "path": "C:\\Users\\Bosmon\\AppData\\Local\\Temp\\gpii-pouch-express-persistent\\_users\\LOCK"
}
15:19:51.575:  Express stopped...

I imagine there's a fault in gpii-pouch-express whereby it never actually closes the file handle?

As @amb26 pointed out, there are problems with the content in the _users database not being removed when the persistence tests are run.  After long investigation, I don't have an explanation yet, but I can confirm that it's only a problem with the persistence tests.  My hope is that by looking at the options and standard cleanup sequence steps used in the rest of the tests, we can hopefully find some clue.

I'd be fine with a "fake test fixture" that runs last and just blows away the surplus directory, plus a writeup of the problem

@amb26, after discovering quite a few ways to not actually remove anything, I ended up adding a "posttest" step.  This will handle all test runs that use "npm test", including CI builds.  I hope this will be adequate.

Thanks - the gpii-persistent dir is now cleaned up correctly. However, I do find what looks like 2 further directories created per run, I assume by testem - their names are of the form testem-nnnn and scoped_dir_nnnn_mmmm. I've linked to a gist containing some here:
https://gist.github.com/amb26/f5a648358153fb506448b451f603ac64
https://gist.github.com/amb26/0d5b63a26cac0a6ea4a0e3d8be09036a
Again I'd be happy with a blunt instrument that just makes best efforts to remove any dirs in temp whose names match this pattern in your posttest.

@amb26, I looked at the testem docs and then the code, starting with the local function provided by the testem prototype.  I searched the whole project for direct and indirect uses of that user directory, it looks like they don't provide a built-in option or code to handle this bit of cleanup.  Looking at their "launcher", I can see that the default is basically os.tmpdir plus the "testem-" prefix and a unique id, so a simple pattern match should be adequate.
I have already been seriously thinking about maturing my previous work with testem into a micromodule, as I believe it would help drive discussions around code coverage within testem, and would give us a new option for using QUnit browser tests in combination with node-side fixtures.
Rather than solving this per project, it makes sense to provide a cleanup mechanism as part of that package.
For the cleanup, I'd create a static function that can clean up after testem as part of that package.  That function would be wired into the shutdown cycle of the testem component of the kind you've seen in my work on gpii-binder.  We also need a painless way to trigger the cleanup mechanism from testem.json configuration files.  My idea is to use a "bin" definition in package.json and provide docs on calling that from testem.json.
I'll go ahead and write up my thoughts on the "gpii-testem" micromodule and share that ticket here.  If you're happy with that as the long term solution, I'll write that up and use it (or at least its cleanup) with everything I maintain that uses testem, including this package.

@amb26, I posted some thoughts to the mailing list and wrote up a ticket with my proposed approach.

@amb26, as discussed, I have updated the pull to use gpii-testem.  Running npm test will now result in cross-environment coverage reporting.

This also addresses the Testem cleanup concerns.

The testem tests hang in Chrome at the end of the run - after reaching test 13/13, the browser window stays open and the test run does not proceed any further. If I skip Chrome, IE shows the same visible behaviour but in addition reports this disconnection:
ok 5 IE 11.0 - Common tests for gpii.pouch component...: Test the POST method (without an ID)...
not ok 6 IE - error
---
message: >
Error: Browser exited unexpectedly
    Log: |
        { type: 'error', text: 'Error: Browser exited unexpectedly' }
...

1..6
tests 6
pass  5
skip  0
fail  1
The exit is reported at a randomly shifting position each run.
Running just the node tests shows that the cleanup is now nearly perfect - however there is now just one directory left behind in Temp, whose name is reports-1caovdlk-31 , containing a report.tap file

The report.tap file is not testing the ability to test, but actually represents machine-readable output from the test run itself.  It should therefore be preserved.  I have updated to leave it in "reports", as we've done in other projects.
The other failure seems to be a failure in calling the Testem callback at the end of a browser run.  On a hunch, I tried it in my Bootcamp VM (not a QI VM), and see the same hangs there.  Will investigate further, although it might be good to cover this in our next pairing session.

Now that the gpii-testem errors are resolved, I am seeing a test failure in IE, which seems to be down to a difference in the way the PouchDB "info" method works.  Troubleshooting now, I will advise when this is ready for review again.

I was seeing intermittent failures in the IE tests, particularly around the "info" method.  I only saw errors when running all tests at once.  By the time I finished working my way through running just the IE tests (which passed, repeatedly), then just the browser tests (which passed, repeatedly), the overall tests worked, I haven't observed a failure in 5 consecutive runs.
@amb26, are the tests running on your machine?  If so, I'd propose creating a ticket with the symptoms of the intermittent failures and tracking that if it comes up more frequently.

The Chrome tests now run and exit properly, but I get a browser disconnect from IE at some (early) point during its tests, as follows:
14:47:44.571:  ""
ok 1 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `info` method...
ok 2 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `POST` method (with an ID)...
ok 3 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `GET` method (with a non-existent ID)...
ok 4 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `PUT` method (with an ID)...
ok 5 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `POST` method (without an ID)...
ok 6 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `bulkDocs` function...
ok 7 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `allDocs` function...
ok 8 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `bulkGet` function...
ok 9 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `remove` function...
ok 10 Chrome 56.0 - Common tests for `gpii.pouch` component...: Test the `remove` method (with a non-existent ID)...
ok 11 Chrome 56.0 - Common tests for `gpii.pouch` component...: Testing `query` handling (passing a single map function)...
ok 12 Chrome 56.0 - Common tests for `gpii.pouch` component...: Testing `query` handling (passing a map function as part of a JSON document)...
ok 13 Chrome 56.0 - Common tests for `gpii.pouch` component...: Testing `query` handling (passing both map and reduce function)...
ok 14 IE 11.0 - Common tests for `gpii.pouch` component...: Test the `info` method...
ok 15 IE 11.0 - Common tests for `gpii.pouch` component...: Test the `POST` method (with an ID)...
ok 16 IE 11.0 - Common tests for `gpii.pouch` component...: Test the `GET` method (with a non-existent ID)...
not ok 17 IE - error
    ---
        message: >
            Error: Browser exited unexpectedly

        Log: |
            { type: 'error', text: 'Error: Browser exited unexpectedly' }
    ...

1..17
# tests 17
# pass  16
# skip  0
# fail  1

Windows 7 x64, IE version 11.0.9600.17843

The Windows 7 VM has IE 11.0.9600.18537.  Unfortunately I am struggling to get pouchdb and leveldown to build.  @amb26, what (if anything) did you have to do before you could run "npm install" in this project?

OK, I am having problems running the node tests in a VM (I can't find a package that will install a usable vcbuild.exe).  I noticed some initial behavior that suggested gpii-testem did not include recent improvements.
So, I updated gpii-testem to the latest dev release, and after that I am able to run the browser tests with Windows 7 and IE 11.0.9600.18537.   @amb26, please update and confirm if the browser tests work for you now.

In pushing through further changes ("root safe dedupe infusion"), I worked further with the Vagrant config.  The tests now pass on Windows 10, including in IE, with the following caveat:
Until https://issues.gpii.net/browse/GPII-2341 is resolved, the process for running the tests in Vagrant is as follows:

Run "vagrant up" from the host machine.
When this process completes, open the VM and open Internet Explorer once.
Click through the dialog to set the security settings.
When closing the browser, tick the box to automatically close multiple tabs.
Run "vagrant ci test" from the host machine

In the Vagrant Windows 10 VM, the tests are confirmed passing with IE 11.953.14393.0

The tests run well, but the following junk was left behind in Temp:
drwx------+ 1 Bosmon None   4096 Apr 24 15:10 qo0ul6m-184
drwx------+ 1 Bosmon None   4096 Apr 24 15:10 qo0ul6m-264
drwx------+ 1 Bosmon None   4096 Apr 24 15:10 qo0ul6m-339
-rwx------+ 1 Bosmon None   2578 Apr 24 15:11 log.txt
drwx------+ 1 Bosmon None      0 Apr 24 15:11 user_data_dir-4vhdetmh-31
-rwx------+ 1 Bosmon None 838067 Apr 24 15:11 CF13.tmp
-rwx------+ 1 Bosmon None  25927 Apr 24 15:11 D1B4.tmp
drwx------+ 1 Bosmon None      0 Apr 24 15:11 scoped_dir_8236_29761

So, for the failed cleanup for the directory with suffix "-184", here is the relevant section of the logs - which make no mention of cleanup, either successful or failed:
15:10:57.659:  express pouchdb instance 'qo0ul6m-184' initalizing...
15:10:57.663:  Creating directory 'C:\Users\Bosmon\AppData\Local\Temp\qo0ul6m-184' for express pouchdb instance 'qo0ul6m
-184'...
15:10:57.996:  express baseDir: 'C:\Users\Bosmon\AppData\Local\Temp\qo0ul6m-184'...
15:10:58.013:  Express server listening on port 9595
15:10:58.016:  Express started...
15:10:58.185:  Data loaded for database 'rgb'...
15:10:58.205:  DataSource Issuing HTTP request with options {
    "port": "9595",
    "method": "GET",
    "headers": {

    },
    "protocol": "http:",
    "auth": null,
    "host": "localhost:9595",
    "hostname": "localhost",
    "path": "/rgb/_design/rgb/_view/byColor?key=%22red%22",
    "url": "http://localhost:9595/rgb/_design/rgb/_view/byColor",
    "termMap": {

    },
    "directModel": {
        "key": "red"
    },
    "operation": "get",
    "reverse": false,
    "writeMethod": "PUT"
}
15:10:58.574:  jq: Test concluded - Module "Integration tests for gpii-pouch and the 'url encoding' express dataSource g
rade..." Test name "We should be able to retrieve a record using a single key...": 3/3 passed - PASS

Thanks, I will attempt to reproduce the cruft problems on my machine and then Windows VM.

Thanks for the tip about the second half of the component id being deterministic.  The same three tests are consistently leaving cruft behind on a clean Windows 10 VM.  I will investigate further.

As soon as I navigated to the temporary directory on my Mac, I could see that the same three ID segments (184, 264, 339) were also left behind.  Looking at the logs, I confirmed that all three were tests in  tests/js/express-dataSource-integration-tests.js.  Those tests were based off of a different caseHolder than the rest, and that specific caseHolder lacked the usual cleanup steps.  I updated the caseHolder and confirmed working on OS X.  Windows is another story.  There, a reasonable 1-2 second timeout results in failures to clean up those directories.  Setting the timeout to 60 seconds reveals a rimraf error about 15 seconds in:
Error removing temporary directory: { Error: EBUSY: resource busy or locked, unlink 'C:\Users\vagrant\AppData\Local\Temp\aq988kpz-184\_replicator\000003.log'
==> windows10:     at Error (native)
==> windows10:   errno: -4082,
==> windows10:   code: 'EBUSY',
==> windows10:   syscall: 'unlink',
==> windows10:   path: 'C:\\Users\\vagrant\\AppData\\Local\\Temp\\aq988kpz-184\\_replicator\\000003.log' }

I will review and see what I can do about that, but just to confirm, is a clearly logged timeout acceptable?  Is a 15 second timeout acceptable?  Either would be fairly easy.

OK, it turns out that this was entirely a byproduct of the dataSource integration tests having a separate caseHolder.  The caseHolder used in most tests in this package:

Cleans up after itself after each run.
Instantiates the databases that express-pouchdb uses so that it can clean them up afterward.

After starting down a few longer roads, I realized it was indeed just that simple, applied the fix, and confirmed that the content is cleared out on both OS X and Windows 10.
@amb26, this should be ready for further review.

Thanks, the situation is hugely improved with these fixes and I think this is now mergeable. For future reference, the files left behind in Temp on my system are now the following 2:
-rwxrwx---+ 1 Bosmon         None  2578 Apr 26 15:26 log.txt
drwxrwx---+ 1 Bosmon         None     0 Apr 26 15:26 user_data_dir-arxs6l3d-31

I imagine the latter is a pouch-express artefact, and I notice that I do now receive useful diagnostics from failed rimraf runs:
Error removing temporary directory: Rimraf failed to complete within 1000 milliseconds...

In fact I seem to receive more of these diagnostics than might be justified, given that there is only one directory for which cleanup has visibly failed.

Thanks for the merge.  There is no attempt to prevent rimraf from completing its work even if the timeout fires (we just prevent it from resolving/rejecting the promise if it already has a disposition).  I suspect that rimraf is managing to finish up in those cases in the time between the timeout and the teardown of the test fixtures.
The user_data_dir is in fact gpii-testem's fault, I have created a separate ticket to track that work: GPII-2396.
The log.txt file is indeed an omission in the express-pouchdb component cleanup, I have created a ticket here for that work: [GPII-2397}(https://issues.gpii.net/browse/GPII-2397)


[Launcher] Big delay on first query

From @crutkas: "Looking at first load, it is at 61 mb. After a query, it jumps to 90, so are plugins loaded yet?"

@jyuwono Is there anything else required to be done on this otherwise we can close this?

@crutkas is this still repro?

i think on init, it is fine, i still think init query seems to take time.

My feedback here is we need to start getting data driven here.  This is very 'gut' feeling versus data driven


Safari having issues With Autoplay

Current Behavior
From the video listing page of my website , If I click a video it will not autoplay.
 My assumption is Safari cracking down on unmuted autoplaying videos (much like Chrome and others)
https://bitmovin.com/autoplay-policies-safari-14-chrome-64/

I have tried that but no luck
Chrome and firefox work perfectly though without mute
I think safari maybe has permission issues with the format of the videos being served.

@Aman1706 Please reopen the issue when you have a jsFiddle or similar that demonstrates the problem.

@Aman1706 were you able to solve the issue ?


Error while pulling image

Expected behavior
crash
Actual behavior
error
Error while pulling image: Get https://index.docker.io/v1/repositories/juhofriman/borg/images: dial tcp: lookup index.docker.io on <IP_ADDRESS>:53: no such host
Information about the Issue
Steps to reproduce the behavior

...
...

Are you behind a firewall or VPN?
See our wiki for possible solutions:
https://github.com/docker/kitematic/wiki/Common-Proxy-Issues-&-Fixes


Blunt damage will do stamina damage on wide attacks

About the PR
Added stamina damage to right click wide arc attacks that do blunt damage
Why / Balance
Think it was a bug that blunt didn't do stamina on wide attacks, it's reported as a bug in https://github.com/space-wizards/space-station-14/issues/31693
Buffing wide against single is maybe kinda bad, but I think blunt should still do stamina in wide to keep blunt x pierce x cut balanced, and because it's unintuitive that it don't. Wide x single should be balanced in other ways.
This might be relevant to the new medical as it changes code dealing with damage.
Technical details
Just added a few lines checking for blunt damage and applying stamina damage to wide attacks, pretty similar to what single attacks had. in shared melee weapons system
Media
https://github.com/user-attachments/assets/df35ad5c-e4d1-4ebe-8999-ebe9edfb5543

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog
:cl:

fix: wide attacks that deal blunt damage will now deal stamina damage.

finally, I can use the truncheon as god intended

sounds ultra op
what if you took stamina damage when wide swinging?

sounds ultra op
what if you took stamina damage when wide swinging?

It’s already a thing, this just adds QOL by not needing to pixel hunt and allowing wideswings. How is it OP?

Yeah do note that blunt already do stamina damage when not wide swinging and truncheon is stronger than other blunt, it has a bonus blunt stamina damage.
As I said I think maybe wide doesn't need buffs against single. But they shouldn't be balanced by a exception to normal blunt stamina damage, because it doesn't really address the issue in general, just for blunt, it changes the balance between blunt and other damage types (since both will kill might as well ditch the truncheon for the fire axe), and it's a unexpected behavior that will confuse players, they will use wide truncheon expecting a less than lethal weapon and kill people. This just looks like a bug to me, not a intended way to keep wide balanced.

Prolly fine to do it here ig, might want to move it at some point to staminasystem though that likely needs attackedevent tweaks.

Why you do it with wideswing? Single hit - perfect solve for it. This is more skill-dependent


Strange high CPU usage / staggering framerates in fullscreen in macOS Mojave.

Hello.
This is something I noticed while I built my 3D engine using glfw in macOS Mojave.
The framerates were off. It was like the vsync was not happening, and the engine would be blasting frames to the screen too fast. I tried both with vsync enabled and disabled, no difference.
I also noticed my program was using unusually high CPU times, like around 50-60% for just a very simple scene, like one simple dodecahedron rendered, which previously hadn't taken anything above 10% ever IIRC.
I was wondering what the heck was happening, because I hadn't change anything, only thing I had done I had not built my engine on Mojave, last time I tried it was in High Sierra (10.13).
Now, trying to pinpoint the problem I started to look at how the examples shipped with glfw were behaving. Running even the basic examples that are bundled with glfw I'm seeing strange things. Running the bounce app in windowed mode is taking nearly 85% in CPU usage, as seen here reported by top:

This is strange I thought, this very simple app is making my MacBook Pro 2014 mid blowing it's fans. Something is not right here, I don't remember this happening before.
Trying to run the examples in fullscreen also result in jaggy performance, it's like the video output is not somehow even vsynced or it is trying to vsync multiple times per frame or something like this, the output is not smooth at all.
Here you can see a video recording of how it looks:
https://drive.google.com/open?id=1lBlc9F9jAzv-ZbrRgbzeJByb4NLLwZsl
Any idea why this is happening ? Incompatibility with Mojave ? Is this expected behaviour with the example apps ? It's making using my 3D engine at the time unusable, and I'm suspecting it has to do with glfw or the screen updates, as in High Sierra these used to work much more smoothly.
I'm testing with the current master branch, MacBook Pro 2014 mid (integrated graphics disabled, using the NVidia GeForce GT750M 2GB gpu).

Even testing with the most simple default example app, rotating a single triangle, results in 60-85% CPU usage, fans blowing and not even completely smooth framerate as far as I can see with my eyes:

This can't be correct behaviour for such a simple operation.

Allright digging into the issues I see that this is related to vsync broken in Mojave, as explained in https://github.com/glfw/glfw/pull/1417.
Tried the branch from https://github.com/amarcu5/glfw with the fix and with this the framerate issue is gone. Please merge and fix.

Thank you for testing the fix! It's held up by one final implementation issue but should be merged Any Day Now™.

Thanks for the reply and info! I'm gonna leave this issue open for now, if somebody else comes across the same thing, not entirely trivial to connect this to vsync and mojave.

I'm not sure if @amarcu5's fix solves this entirely.
I wrote a simple loop
while(!glfwWindowShouldClose(win)) {
	double startTime = glfwGetTime();
	glfwPollEvents();
	glfwSwapBuffers(win);
	double endTime = glfwGetTime();
	printf("%g fps\n", 1 / (endTime - startTime));
}

and out of a 30s profile, 16s were spent in the [NSOpenGLContext flushBuffer] method, which is directly called by glfwSwapBuffers, indicating that over 50% of a thread was used. This isn't the case on MacOS 10.13 or less, just 10.14 (Mojave).

Using @amarcu5's fork consistently gives better results.

But the expected result is that swapping buffers should only take 1-4% of CPU time per thread. Not sure what's going on with Apple's flushBuffer method.

The display link solution for this has been merged. It's not ideal but it does work.


Add Perl port of 90_Tower (Tower of Hanoi)

This Perl port of Tower of Hanoi keeps most of the look-and-feel of the original BASIC. As far as internals go, though, it is more a re-implementation than a port.

That's what we aim for .. same output, better implementation! Thank you!


chore: try to run benchtop

Experimental, do not merge.

#522  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @pepyakin and the rest of your teammates on  Graphite

Merge activity

Nov 1, 6:15 PM EDT: A user merged this pull request with Graphite.


Integration of single-spa with rspack for Micro-Frontends

Description
I'm looking to integrate single-spa into an existing project and utilize rspack to build and package micro-frontends efficiently. Has anyone had experience with this combination and could share examples or insights on how to do this effectively?
Context
We have an existing project where we're exploring the use of micro-frontends for modularity and scalability. We've decided to adopt Module Federation as our micro-frontend framework, and we're also considering using rspack for bundling and optimization. However, we're unsure about the best practices and potential challenges when integrating these two technologies together.
However, we also need to package it for single-spa  because there's another one that consumes this application with it. Today, we use Vite to do this.

cc @zhoushaw @ahabhgk

I don't have experience about single-spa so I can't give any suggestions about best practices.
Only for supporting single-spa in Rspack, Rspack should already support it and fully compatible with the configuration required by single-spa: https://github.com/single-spa/create-single-spa/blob/main/packages/webpack-config-single-spa/lib/webpack-config-single-spa.js

Its more than possible. Since single spa already suggests module federation for many use cases and we support all the build specifications required.  You can follow single spa's module federation recipe with rspack and it should work just fine.
Alternatively you can put it into systemjs mode, but the module sharing is more robust with federation

https://github.com/module-federation/core/discussions/2519 @douglaszaltron I think you can focus on this rfc,  module federation that also supports loading application levels


docker-compose.yml - doesn't work/incorrectly documented?

Hello everyone. I stumbled across the project and must say I like it very much.
I guess I found a few mistakes or at least for me confusing example in the file docker-compose.yaml. By the way you called the file .yaml, but in the documentation it says .yml. Only as a small note.
First I tried to install the GUI in the following way. Whether this was intended, I do not know, but this is how I understood it:
version: '3'

services:
  wg:
    build: .
    #image: ngoduykhanh/wireguard-ui:latest
    container_name: wgui
    environment:
      - SESSION_SECRET: 1234
    ports:
      - 5000:5000
    logging:
      driver: json-file
      options:
        max-size: 50m
    volumes:
      - ./db:/app/db
      - /etc/wireguard:/etc/wireguard

After a bit of trial and error I got it to work with the following configuration:
version: '3'

services:
  wg:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wgui
    environment:
      SESSION_SECRET: 1234
    ports:
      - 5000:5000
    logging:
      driver: json-file
      options:
        max-size: 50m
    volumes:
      - ./db:/app/db
      - /etc/wireguard:/etc/wireguard

I removed the build: ., uncommented the #image and changed the variables in evniroment.
If it doesn't cause any other problems, I would suggest that you change the configuration to the following. Maybe this will help others as well. Thank you.
services:
  wg:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wgui
    environment:
      SENDGRID_API_KEY:  <Your sendgrid api key>
      EMAIL_FROM:  <The email address you registered on sendgrid>
      EMAIL_FROM_NAME:  <The sender's email address>
      SESSION_SECRET:  <Random value>
    ports:
      - 5000:5000
    logging:
      driver: json-file
      options:
        max-size: 50m
    volumes:
      - ./db:/app/db
      - /etc/wireguard:/etc/wireguard

I tested it and a friend also tested it and it just doesn't work, it doesn't connect, I can create the user, read the QRCode, but it doesn't work, I tested 2 other projects that work. I suggest testing it before putting it to public, at least in docker.
Here is my configuration, the network at the end is that I use nginx proxy manager.
services:
  wg:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wgui
    cap_add:
      - NET_ADMIN
    environment:
      - SENDGRID_API_KEY=xxxxxxxxxxx
      -<EMAIL_ADDRESS>      -<EMAIL_ADDRESS>      - SESSION_SECRET=xxxxxxx
      - WGUI_USERNAME=admin
      - WGUI_PASSWORD=xxxxxxx
    logging:
      driver: json-file
      options:
        max-size: 50m
    volumes:
      - ./volumes/db:/app/db
      - ./volumes/etc/wireguard:/etc/wireguard
    ports:
      - 51820:51820/udp
    expose:
      - "5000"
    restart: always

networks:
  default:
    external:
      name: nginxproxymanager_default

Encountered an error, the wg0.conf file does not exist and is not created. I rotated the container and went inside it to see if there was something and there isn't, see:
/etc/wireguard # pwd
/etc/wireguard
/etc/wireguard # ls -a
.   ..
/etc/wireguard #

I don't know why that didn't work for you. But I am currently running two servers with this configuration and they are running fine. The only problem, that you have also mentioned, is that it doesn't use the configuration. The only thing you have to do is to restart the wireguard service manually, then it works.

Não sei por que isso não funcionou para você. Mas atualmente estou executando dois servidores com esta configuração e eles estão funcionando bem. O único problema, que você também mencionou, é que ele não usa a configuração. A única coisa que você precisa fazer é reiniciar o serviço wireguard manualmente, então ele funcionará.

Restarting would suffice a docker-compose down and up -d, but it doesn't work. Are you using network on the host?
how do you restart the service inside the docker?

The docker container only represents a graphical interface of the wireguard instance. Wireguard runs directly on the host and not in the container. Therefore, you simply restart the wireguard service on the host.

O contêiner docker representa apenas uma interface gráfica da instância wireguard. O Wireguard é executado diretamente no host e não no contêiner. Portanto, você simplesmente reinicia o serviço wireguard no host.

So I have to configure on systemd and install the system wireguard?
systemd
Create /etc/systemd/system/wgui.service

[Unit]
Description=Restart WireGuard
After=network.target

[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl restart<EMAIL_ADDRESS>
[Install]
RequiredBy=wgui.path
Create /etc/systemd/system/wgui.path

[Unit]
Description=Watch /etc/wireguard/wg0.conf for changes

[Path]
PathModified=/etc/wireguard/wg0.conf

[Install]
WantedBy=multi-user.target

This doesn't make much sense, the projects I've seen and tested, two others, work directly from the container, without having to install wireguard on the host.

Problem fixed by new docker-compose.yaml. The other issue is not related to the original issue.


Webservice - Optimize coordinates search

optimize coordinates search without JSON Parsing for performance reasons

is it done already? becomes obsolete with the "rise" of the geo index

wontfix


vscode.workspace.fs.readFile fails to open file via absolute path

Following call to the workspace.fs.readFile causes an unexpected error
vscode.workspace.fs.readFile(vscode.Uri.parse(context.asAbsolutePath('package.json')))

Error:
Error (FileSystemError): The path of resource 'c:\vscode-extension-samples\call-hierarchy-sample\package.json' must be absolute
extensionHostProcess.js:798
stack trace: Error (FileSystemError): The path of resource 'c:\vscode-extension-samples\call-hierarchy-sample\package.json' must be absolute
	at _handleError (c:\Users\[user]\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:552:466)

The path is obviously absolute.

VSCode Version: 1.40.0
OS Version: Win10

Steps to Reproduce:
There is no workspace folder open when I call this function and get the error. I call it from within the activate function.
Does this issue occur when all extensions are disabled?: It is caused by an extension code.

asAbsolutePath returns a path and Uri.parse expects a uri, e.g something in this for file:///path. Please the Uri.file which works with paths.

Indeed. My coding error! Sorry for the noise.
My wrong hypothesis that this is a bug was confirmed by the The path of resource 'c:...' must be absolute.


Cleanlab wrapper

close #223

WARNING! do not merge before https://github.com/knodle/knodle/pull/238


Develop & Run Cordova iOS

Describe the issue
I want to make some changes in the user interface, I'm trying to test it on the emulator, the command cordova run ios fails with error:
xcodebuild: Command failed with exit code 65
Full output:
The following build commands failed:
	CompileSwift normal x86_64 /Users/*****/outline-client/platforms/ios/Outline/Plugins/cordova-plugin-outline/OutlineConnection.swift
	CompileSwift normal x86_64 /Users/*****/outline-client/platforms/ios/Outline/Resources/vpn/Subnet.swift
	CompileSwift normal x86_64 /Users/*****/outline-client/platforms/ios/Outline/Resources/vpn/OutlineConnectionStore.swift
	CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
(4 failures)
xcodebuild: Command failed with exit code 65
npm ERR! code ELIFECYCLE
npm ERR! errno 65
npm ERR! outline-client@ ios: `yarn run clean && yarn && yarn gulp build --platform=ios && cordova emulate ios`
npm ERR! Exit status 65
npm ERR!
npm ERR! Failed at the outline-client@ ios script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/*****/.npm/_logs/2019-08-08T10_59_05_775Z-debug.log

Environment

OS: OSX
Yarn version: 1.15.2
Node.js version: v11.15.0

Additional questoin
Does outline license allow me to customise it and publish it under different app name?
I have seen that I have to be invited to to join the "Jigsaw Operations LLC" team. Is that mandatory. I can't deploy the app with my own team without being invited?

Hi @MWalid, the Outline iOS client does not support running on the simulator since the NetworkExtension framework is not available. You must deploy the app to a real device.

Does outline license allow me to customise it and publish it under different app name?

I believe so. You need to change your bundle ID and signing team/cert for both the Outline and VpnExtension targets. Xcode should be able to automatically create and download the corresponding provisioning profiles. Note that you also need to create an App Group and update it in the targets' capabilities.
Please let me know if you have any further questions.

Thank you so much @alamav for your reply

Hey @alalamav,
So I did some UI changes, rebuilt the the successfully using the command:
yarn run clean && yarn && yarn gulp build --platform=ios
However I did not find the ipa file to test it on my device.
Thank you,

I was able to build it by opening the project located in platforms/ios/outline of course Xcode v 10.1 is used.


Use the official JaCoCo version

Jazzer uses an internally maintained JaCoCo fork for coverage instrumentation. This fork contains optimizations to reduce the number of probes used in the instrumented code. Measurements indicate that the performance benefits are small and the fork creates maintenance costs and complicates the usage of Jazzer.
This PR will replace the used fork with the official JaCoCo version.

1 Measurements JMH
==================

  ,----
  | Benchmark                                                         Mode  Cnt    Score    Error  Units
  | EdgeCoverageInstrumentation.fork.benchmarkInstrumentedMethodCall  avgt   15  322.849 ±  4.183  ns/op
  | EdgeCoverageInstrumentation.orig.benchmarkInstrumentedMethodCall  avgt   15  345.619 ± 10.615  ns/op
  |
  | EdgeCoverageInstrumentation.fork.benchmarkInstrumentedMethodCall  avgt   30  316.404 ± 5.591  ns/op
  | EdgeCoverageInstrumentation.orig.benchmarkInstrumentedMethodCall  avgt   30  313.906 ± 9.468  ns/op
  |
  | Benchmark (with MockCoverageMap)                                  Mode  Cnt    Score   Error  Units
  | EdgeCoverageInstrumentation.benchmarkInstrumentedMethodCall       avgt   30  368.206 ± 8.372  ns/op 100
  | EdgeCoverageInstrumentation.fork.benchmarkInstrumentedMethodCall  avgt   30  370.279 ± 6.424  ns/op 100
  | EdgeCoverageInstrumentation.orig.benchmarkInstrumentedMethodCall  avgt   30  381.795 ± 1.863  ns/op 103
  |
  | Benchmark (with CoverageMap)                                      Mode  Cnt    Score   Error  Units
  | EdgeCoverageInstrumentation.benchmarkInstrumentedMethodCall       avgt   30  362.582 ± 6.794  ns/op 100
  | EdgeCoverageInstrumentation.fork.benchmarkInstrumentedMethodCall  avgt   30  374.424 ± 3.663  ns/op 103
  | EdgeCoverageInstrumentation.orig.benchmarkInstrumentedMethodCall  avgt   30  369.394 ± 12.964 ns/op 101
  |
  | Benchmark (with CoverageMap + no string operations)               Mode  Cnt    Score   Error  Units
  | EdgeCoverageInstrumentation.benchmarkInstrumentedMethodCall       avgt   30  118.987 ± 1.182  ns/op 100
  | EdgeCoverageInstrumentation.fork.benchmarkInstrumentedMethodCall  avgt   30  127.177 ± 0.986  ns/op 106
  | EdgeCoverageInstrumentation.orig.benchmarkInstrumentedMethodCall  avgt   30  133.852 ± 2.750  ns/op 112
  `----

2 Measurements Fuzzers
======================

   Type      Fuzzer                 Time
  ------------------------------------------------------------------------------------------------------------
   Original  KlaxonFuzzer           Stats over 20 runs: max = 4.8s, min = 4.3s, avg = 4.5s, dev = 0.1s
             TiffImageParserFuzzer  Stats over 20 runs: max = 47.4s, min = 37.7s, avg = 41.3s, dev = 2.1s
             Log4JFuzzer            Stats over 10 runs: max = 379.3s, min = 155.7s, avg = 246.6s, dev = 74.5s
  ------------------------------------------------------------------------------------------------------------
   Fork      KlaxonFuzzer           Stats over 20 runs: max = 3.0s, min = 2.6s, avg = 2.7s, dev = 0.1s
             TiffImageParserFuzzer  Stats over 20 runs: max = 142.1s, min = 120.2s, avg = 132.5s, dev = 4.7s
             Log4JFuzzer            Stats over 10 runs: max = 557.0s, min = 214.9s, avg = 335.8s, dev = 94.2s
  ------------------------------------------------------------------------------------------------------------

3 Counters
==========

   Type      Example                Counters
  -------------------------------------------
   Fork      KlaxonFuzzer               2048
             Tiffimageparserfuzzer      4096
             Log4JFuzzer               32768
  -------------------------------------------
   Original  KlaxonFuzzer               1024
             TiffImageParserFuzzer      4096
             Log4JFuzzer               32768
  -------------------------------------------


CS lime-190, Inefficient Struct PriceData

Description
The struct PriceData has two variables and is defined as:
struct PriceData { address oracle; uint256 decimals; }
decimals stores the number of decimals that the price is returned, hence its range is limited (currently the code returns prices with 30 decimals). Given that address occupies 20 bytes, the struct can be packed together in a single storage slot.
Integrations Checklist

[ ]  Have any function signatures changed? If yes, outline below.
[ ]  Have any features changed or been added? If yes, outline below.
[ ]  Have any events changed or been added? If yes, outline below.
[ ]  Has all documentation been updated?

Changelog

Efficient struct packing in PriceOracle.sol.

Event Signature Changes
Function Signature Changes
Features
Events

Codecov Report

Merging #266 (6e96cc6) into v1-alpha (2230ce8) will increase coverage by 0.09%.
The diff coverage is 100.00%.

:exclamation: Current head 6e96cc6 differs from pull request most recent head 9dc3f68. Consider uploading reports for the commit 9dc3f68 to get more accurate results

@@             Coverage Diff              @@
##           v1-alpha     #266      +/-   ##
============================================
+ Coverage     78.40%   78.49%   +0.09%
============================================
  Files            16       16
  Lines          1681     1679       -2
  Branches        310      309       -1
============================================
  Hits           1318     1318
+ Misses          363      361       -2

Impacted Files
Coverage Δ

contracts/CreditLine/CreditLine.sol
84.01% <ø> (+0.48%)
:arrow_up:

contracts/Pool/Extension.sol
84.05% <ø> (ø)

contracts/PriceOracle.sol
61.29% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add realm option to get default avatars from GitHub or Gravatar

It'd be really cool to have the ability to select the default avatar source for an organization as a realm setting. Some particular options that would be cool to support are:

Using gravatars -- what we currently do.
Defaulting to the user's GitHub avatar (if any) when they create an account with GitHub's SSO.
Some included-in-Zulip-avatar generator.

The initial project here would be to just build one of these options (including the settings UI for changing it); once that's done it'll be a much smaller project to add more options (which can happen on follow-up issues).  I might start with the salted vs. unsalted gravatar setting since that probably involves very little work.
The realm setting part of this can be done via http://zulip.readthedocs.io/en/latest/new-feature-tutorial.html

@timabbott can I take up on this issue, I was thinking of doing second option, i.e. when the user signs up using github then we can use his github gravatar for zulip.

@vedantrathore sorry for the slow reply (I've been sick); yes feel free to work on that.
Also, I'm going to update the description to clarify this, but we're actually currently using Gravatar properly.

We should think somewhat carefully about what the right user experience is for the GitHub avatar source before getting too far into implementation; what do you think the right approach is @vedantrathore?

One person I'm talking to just asked whether an organization's administrator can turn off avatars org-wide.

Can you explain the use case for disabling avatars?

From what I recollect: I know some people who prefer to use avatars that don't show their faces because they get more harassment if people know that they are of some discriminated-against minority (e.g., black people, women, and so on), and it levels the playing field, so to speak, when there are no avatars.

I think we're unlikely to support that in the near future just because it's a lot of design work to maintain and not something many folks have expressed interest in, but the path would to something like that would be to first implement a "dense mode" design that doesn't display avatars, and then add a setting to require that display style.

@zulipbot claim

please @timabbott can i have a hint on what i should know to solve this issue? and also can i know which file(s) need to be modified?

This issue is not great for folks who don't have significant experience, as it doesn't have a concrete set of next steps.  Removing a few labels.


Add tests for securing the deployment

These tests can go in after https://github.com/kubernetes/kubernetes/pull/47835 has been merged.

Yes! Love these tests. Will merge when the upstream PR lands.

The upstream PR landed. Merging this.


Remove option to split bills in rooms

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to a #announce room
Click on the attachment button

Expected Result:
There should not be an option for splitting bills.
Actual Result:
There's an option to split bills in workspace rooms.
Workaround:
N/A
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.0.94-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @Santhosh-Sellavel
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1631039739030300
View all open jobs on GitHub

Triggered auto assignment to @johnmlee101 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

I... believe that this should check isDefaultRoom around https://github.com/Expensify/Expensify.cash/blob/b8a3a578ec6d83834520c2bd933e4d38ed63a272/src/pages/home/report/ReportActionCompose.js#L519-L532
Should be a super easy fix. Tossing to external.

Triggered auto assignment to @Christinadobrzyn (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@isagoico, @johnmlee101 I am not able to search announce room from new chat window. Can any one guide me how to add announce room, So I can reproduce this issue. Thank you for your time in advanced.

You have to create a workspace and add at least 1 member. Once that is done, you have to search for #announce and it should appear. Let me know if that works for you :)

@isagoico I created workspace and added 1 member. Thereafter I can see #announce thanks.
In my case when I go to announce room and click attachment button it shows me Request Money button instead of Split Bill. I am new to understand the split bill related logic etc., so  wandering I am doing something wrong to reproduce the issue.  I am using V1.0.94-0
Below is the screenshot.

mmmm Maybe it shows request money since there are only 2 members in the room 🤔 I will try again on my side

@isagoico if only one member is added to the workspace it shows Request money.
My proposal here will solve both.
I hope @johnmlee101 also agree here https://github.com/Expensify/App/issues/5134#issuecomment-915376273

Proposal
Brief it out again for clarity.
Just add !isDefaultRoom check along the lines
https://github.com/Expensify/App/blob/e6ed8dd8c72f531d6f6ef066e4506f112bd6ae6b/src/pages/home/report/ReportActionCompose.js#L524-L526
As shown below,

This should be enough.
Optionally we can merge those checks into one boolean shouldAllowIOU variable if needed thanks!

Posted to Upwork!
Internal posting: https://www.upwork.com/ab/applicants/1435852224575746048/job-details
External posting: https://www.upwork.com/jobs/~01e8fdb54c8df622bb

Looks good @Santhosh-Sellavel !

@johnmlee101 Just the check or add new Boolean variable also? What do you prefer?

Check should be good enough for now!

Hired @Santhosh-Sellavel in upwork!

Heyo! Turns out this is intended functionality actually. @Santhosh-Sellavel
We're going to figure out where to go from here, since you've put effort into this already.

Closed contract in Upwork, paid @Santhosh-Sellavel for reporting the issue and for being hired for the fix.
We want to allow for split functionality in all rooms and groups, we should have this sooner in #expensify-open-source and added a comment.


Trying to use in Ionic 3

Environment

Ionic 3, Typescript
Browser and browser version: Chrome and Safari
OS version: OSX and iOS
xterm.js version: latest

Steps to reproduce
https://github.com/aircable/ionic-xterm
I created a test project to integrate xterm.js into a new Ionic 3 project.
But it's not working, has many problems, including the integration of addons etc.
It compiles, but just doesn't do it.
Layout is non-existent. Tried many things. Hope you guys can help. Thanks.

You don't have xterm declared as a dependency? https://github.com/aircable/ionic-xterm/search?utf8=✓&q=xterm&type=
I don't think anyone in the team knows anything about ionic/angular so I don't think we can help.

Closing this as it was answered here: https://stackoverflow.com/a/45557432/577598.


Only allow one modifier per DMA-BUF, split attributes struct in render/

The DMA-BUF attributes struct is starting to be used in various parts of wlroots, some of which have nothing to do with the linux-dmabuf protocol. This extracts the common struct into wlr/render/dmabuf.h.
This also removes the ability to have per-plane modifiers.
Fixes #908

Thanks!


spi pac update

For https://github.com/esp-rs/esp-pacs/pull/224

Not sure about second commit. Need tests
cc @MabezDev

I did a HIL test run (only C6 right now): https://github.com/esp-rs/esp-hal/actions/runs/8801550864/job/24155269572, looks like it passed :)

rebased


Update transaction limit to 100

https://github.com/aws/aws-dax-go/blob/8524b5d9a6599f1f44ecf30cc52dac8324f54c6a/dax/internal/client/request.go#L431
But Dynamo updated their transaction limit to 100: https://aws.amazon.com/about-aws/whats-new/2022/09/amazon-dynamodb-supports-100-actions-per-transaction/

Closing this issue as the underlying PR is closed.


Create the tournament Archived View Feature

These features have been implemented to address issue #238 :

Create an archived tournament list view to display all the archived tournaments. The tournament information displayed on the archived tournament list view is the same as that in the tournament list view, but the archived tournament list view only displays archived tournaments.
The set_archive function is called when an admin user clicks on the “archive” star button on the tournament list view, detail view, and the archived tournament list view (displayed if 1. login as an admin and 2. Tournament has ended). If the tournament is archived, then the star is yellow, and clicking it results in unarchiving the tournament; if it is not archived, then the star is white, and clicking it results in archiving the tournament. If a non-admin user visits the page, the "archive" star icon is not a button, so it cannot be clicked.
Add a button with the text "Switch to Archived Tournament List" to the tournament list view that, when clicked, redirects the user to the archived tournament list view, and vice versa "Switch to All Tournament List".

Hi Elizabeth, the archive view is implemented in this way in case we may want to add new features to the archive view. Therefore, if we use the same HTML file, then it would not be that flexible. For the second issue that you mentioned, I will add a check. Thanks!

Hi Elizabeth, the check has been added to the update view. Thanks!

In this pull request, all the features mentioned in issue #238 have been implemented. However, there are some issues that need to be solved in the future.
Issues to be addressed in the future: Currently, I think this is part of a larger system that needs further consideration, so I put the issue into the next step part of the final report. Basically, the idea is that we need to design what the archive list represents. If it represents tournaments that are memorable, then all the tournaments that have ended shall be removed (and deleted) from the tournament list, and those that have been archived will be preserved and put into the archived list. If it represents other concepts, then a different action may need to be conducted. (edited)
I am not sure how to deal with tournaments that have ended, so I just keep all these ended tournaments, regardless of their archived status, in the tournament list and allow more flexibility later.

In this pull request, @MikeChen012345 and @MuyanXie worked on creating the archived view and addressed feedback. @jb-01 helped with thinking about whether the archived view should be designed as a separate page or using the same template as the tournament list view.
@rqueiroz20 helped us with reviewing and testing the code. Thanks!

Issue Score: Excellent
Comments:
Sets the stage for future design choices of what an "archive view" looks like. Great work.


Correct timezone err on ‘is active’ slot indicator

The app relied on the client to determine “now” - what the time currently is.
The Slot component then used this timestamp to check if a current slot in the schedule was active.
I added a well-supported timezone library to anchor the “now” timestamp to the “Atlantic/Reykjavik” timezone so the “is-active” indicator always accurately reflects the conference schedule.
Fixes #100

QA

Pull down this feature branch
Run npm run dev
Navigate to http://localhost:8000/schedule/#!/conference/thursday
Open components/events/index.js
On line 96 - change 'Atlantic/Reykjavik' to 'Europe/Moscow' and verify that the schedule moves +3 hours

Thank you so much for this!


Make grt::have_routes  return 0/1 silently

Description
When scripting, it is useful to check if an operation that needs global routing should be skipped or not using grt::have_routes.
However, grt::have_routes prints warnings and errors.
[WARNING GRT-0097] No global routing found for nets. 0

Or if run with make gui_floorplan
>>> grt::have_routes
[ERROR GRT-0010] Instance ctrl.state.out\[0\]$_DFF_P_ is not placed.
[ERROR GUI-0070] GRT-0010

Since these errors/warnings are logged, catch is no help:
>>> catch {grt::have_routes} error
[ERROR GRT-0010] Instance ctrl.state.out\[0\]$_DFF_P_ is not placed.
1

Suggested Solution
grt::have_routes should silently return 0/1, but it can returns warnings and errors.
Additional Context
No response

@maliberty @luis201420 I made a fleeting vain attempt at removing the warning https://github.com/The-OpenROAD-Project/OpenROAD/pull/6305


import-scope false positive with lodash/fp

When using the member import style with the import-scope rule, imports from lodash/fp are incorrectly marked as errors.  E.g.,
import {
    filter as fpFilter,
    map as fpMap,
} from 'lodash/fp'

reports Import members from the full lodash module
IIRC, fp will be moved to a different module in the next lodash major version, but for now I think this is incorrect behavior?  If agreed, I can probably work up a PR to fix it.

Fix released in v2.3.5.
Thanks for reporting and fixing it!


[ADAP-620] [Bug] Incremental materialization with "append" strategy does not wrap dml with explicit transaction

Is this a new bug in dbt-snowflake?

[X] I believe this is a new bug in dbt-snowflake
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
When running an incremental model with "append" incremental strategy, the INSERT statement is not wrapped with an explicit transaction.
Expected Behavior
The INSERT statement should be wrapped as all other DML statements, leveraging the snowflake_dml_explicit_transaction macro.
Steps To Reproduce

create a model with incremental materialization and set incremental_strategy = "append"
check run sql under target folder: the statement is not wrapped with begin; coomit; end;

Relevant log output
No response
Environment
- OS: Linux
- Python: 3.8
- dbt-core: 1.4.6
- dbt-snowflake: 1.4.3

Additional Context
Should be easily fixed adding this here:
{% macro snowflake__get_incremental_append_sql(get_incremental_append_sql) %}     {% set dml = default__get_incremental_append_sql(get_incremental_append_sql) %}     {% do return(snowflake_dml_explicit_transaction(dml)) %} {% endmacro %}

@danielefrigo great catch! would you be interested in opening the corresponding pull request? I'd be glad to help you get it over the finish line.

hey @danielefrigo, just took the time to reproduce your result. Correct me if I'm wrong but the insert logic you hope to have wrapped in a transaction is get_insert_into_sql's, right?
I agree that this macro could be executed as a transaction, but I'm not sure what it would accomplish, because it is just a single SQL statement. I may be missing something, but I thought that transactions are helpful when executing a series of a related SQL statements. Instead the update logic of an append is just the following. right?
insert into TEST_DB.dbt_ajs.daniele ("ID", "FIRST_NAME", "LAST_NAME")
    (
        select "ID", "FIRST_NAME", "LAST_NAME"
        from TEST_DB.dbt_ajs.daniele__dbt_tmp
    )

Let's start saying that I was overriding the snowflake_dml_explicit_transaction, and then I noticed that the statements resulting from this kind of materialization were behaving differently from others.
I agree with your analysis, but the same applies to other statements that are currently wrapped (e.g. default__get_merge_sql), so I guessed this was intentionally done for some other reason like performance.
And this connects to my second question about Snowflake transactions management and hooks (
https://github.com/dbt-labs/dbt-core/issues/3480)


Incorrect reference to ADAL.js

The section "With Dynamics 365 for Customer Engagement or Internet-facing deployments" says "If you’re creating a single page application (SPA) using JavaScript you can use the adal.js library as described in...", but adal.js library was deprecated and replaced by MSAL.js library.

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

ID: ef5c715a-0f80-b112-62d8-fea136c7d23a
Version Independent ID: 36e0cae7-c91a-cdac-d0b3-853a3ec265fd
Content: Authenticate to Dynamics 365 Customer Engagement with the Web API (Developer Guide for Dynamics 365 Customer Engagement)
Content Source: ce/customerengagement/on-premises/developer/webapi/authenticate-web-api.md
Product: d365ce-op
GitHub Login: @JimDaly
Microsoft Alias: jdaly

Thanks for your comment, @dpecharroman. This issue has been assigned to the doc author for review.

Thank you.
I've fixed this


Feature/improved ios support

We found the iOS 8 Safari support lacking, extended the autoprefixer browser versions.
We also found that in our app mousedown was not working well with Safari on iOS, so we augmented the plugin with touchstart. In addition, we found that keeping contenteditable resulted in users getting the keyboard blocking the view and our users prefer using interactive controls anyway, so we removed contenteditable when we detect iOS.

Nice! Will test and deploy asap. Really nice additions. Thanks!