Visual Studio Online build agent doesn't recognize adapter

I'm trying to get my VS Online build to exercise mspec tests. I've added the binaries from the VSIX into my repo (it's git, if that matters) and set the "Path to custom test adapters" setting to their location. When the test step of my build executes the following message appears in the log:
"Warning: The path 'C:\a\c8651a29\Configure\Machine.VSTestAdapter' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again."
I am able to discover the nUnit adapter using the same method, so I'm confident that my build definition isn't the problem.
I've been trying to figure out if something is missing that might cause this. The documentation available from MS is laughably scarce (as you're probably aware). My only thought at this point is that it might be the fact that there is no TestContainerDiscoverer in machine.vstestadapter. I'll investigate the possibility, but if you have any insight I'd love to hear it. Thanks!

I'll have a look into it, I've been trying to get the adapter to run from a nuget package and had similar issues, so could very well be related.

Quick update: the TestContainerDiscoverer is a non-starter. The nUnit adapter works fine without one.

With the help of Terje Sandstrom from the nUnit adapter team, I figured out why it's not getting picked up by the build server. Turns out that the adapter assembly name must end in ".TestAdapter.dll"  (NB: preceding period) in order for it to be recognized by vstest.console.exe which is how TFS build invokes the tests. Naming conventions strike again :)
Unfortunately, after fixing that I'm running into another issue. It appears as though the adapter isn't reporting results back to vstest.console properly. Here's the output from running against an test assembly that contains one intentionally failing spec:

Starting test execution, please wait...
Information: Machine Specifications Visual Studio Test Adapter - Discovering Specifications.

Information: Machine Specifications Visual Studio Test Adapter - Discovering...looking in C:\src\vso\Configure\Configure.Tests.Unit\bin\Debug\Configure.Tests.Unit.dll

Information: Machine Specifications Visual Studio Test Adapter - Discovery Complete - 1 specifications in 1 of 1 assemblies scanned.

Information: Machine Specifications Visual Studio Test Adapter - Executing Specifications.

Information: Machine Specifications Visual Studio Test Adapter - Executing tests in C:\src\vso\Configure\Configure.Tests.Unit\bin\Debug\Configure.Tests.Unit.dll

Information: Machine Specifications Visual Studio Test Adapter - Execution Complete - 1 specifications in 1 assemblies.

Warning: No test is available in the provided sources. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

Information: Additionally, you can try specifying '/UseVsixExtensions' command if the test discoverer & executor is installed on the machine as vsix extensions and your installation supports vsix extensions. Example: vstest.console.exe myTests.dll /UseVsixExtensions:true

I get a similar result when I run the tests as part of the VS Online build, only the messages from the adapter are omitted (I assume due to verbosity level).
So the question at this point is: do you want to close this issue with the name change and open a new one for this new thing. Or would you prefer that I edit this issue to reflect that the adapter isn't working right in the console runner?
By the way, I would be happy to provide a PR to fix the assembly name problem. Do you want it to be Machine.TestAdapter? Machine.VisualStudio.TestAdapter?

changed the name of this issue will try and sort that out for you, will probably only be able to get a chance to have a look nearer the end of the week

Don't stress about the PR I've been trying to get this thing to run from a nuget package so have actually changed the name already, hoping  to have that sorted soon.
Lets hope it sorts things out for you to.

Awesome. I'm going to continue to poke around as well. I'll let you know if I find anything.

What's the status of this? I am about to start looking into making my Mspec tests run in the new Visual Studio Online build system.

What is the status of this? I am just about to start looking into running my MSpec tests in the new Visual Studio Online build system.

Hi I haven't been able to look any further into this as yet hoping to get there in the coming weeks

@JonathanWilkins If you can give me any pointers as to where to start from - I am happy to try and have a look at this too. I assume the NUnit test adaptor works in VSO, so maybe pointers to what is implemented there vs what is missing in the mspec adaptor?

As far as I understand it does, that's really all I've been doing is trying to compare Nunit to what we have and see what might be missing. I know the one difference was the Assembly naming which we have sorted. Not sure what else it might be. If you want to take a look that would be a huge help.

I have successfully been able to run mspec tests in VSO (now VS Team Services) with the shortly to be released 1.7.0 nuget package and test output works fine. Tests show up in the Test Results report, etc.
I will close this issue once 1.7.0 is on nuget.org.

The release is now. Details on the nuget package here: https://github.com/machine-visualstudio/machine.vstestadapter/releases/tag/v1.7.0
This is what it looks like (note - screenshot is of a build with a failing test):


Add dutch translation

Let's see if our Dutch native friend @WouterJ can review this work before merging it :)

@flip111 I'm sorry to bother you, but today we added 1 new string to translate:
 <trans-unit id="post.blank_summary">
    <source>post.blank_summary</source>
    <target>Geef uw bericht een samenvatting.</target>
</trans-unit>
<trans-unit id="post.blank_content">
    <source>post.blank_content</source>
    <target> ... NEW TRANSLATION HERE ... </target>
</trans-unit>

@flip111 I'm sorry it took a long to merge your translation. The problem is that GitHub doesn't notify us when a pull reuqest is updated with more commits. In any case, your work is finally merged! Dank je


Added skipPreflight to RequestConfiguration

As per Solana Documentation skipPreflight is optional and set to false by default. However in some cases you need the flag to be set to true for transactions to succeed.
This PR will not break any existing projects that are using this SDK since the property is optional and nil by default.

Hi. Thank you for your contribution. We're merging it


For #23 - Handling UnsupportedOperationException

This PR only applies after my other one.

thanks i really like this second pr :)


Failed to Load Resource

console error Failed to Load Resource.
error is here.
function displayFavorites() {
let favImages = localStorage.getItem('saved-images');console.log(favImages);
// if (favImages === ''
favImages = JSON.parse(favImages);
Needs to have an if stating if no localstorage do something.
example for multiple images to be saved:
if(localStorage.getItem('saved-images') == null){
localStorage.setItem('saved-images', []);
}
if you use the above if statement, be sure to put literals around your array. (not quotations ' ' , " " ) (use literals   )
clear your localStorage then refresh page to see error.
Crystal Ripple - zMaG33z

Seems good.  Confliction on my end.  Old project resource file in localstorage not compatible.


FP for Attack Detector

https://app.forta.network/alerts/0x4d37512ee0850b335ac55d39f3e17a2828c21cb77721f382a5a3fec68dad4f12 (attacker has very large nonce. >13k)

Suspicious contract creation


feat: Parse actually installed mods

Instead of using solely enabledmods.json parse the mod.json of found mods in mods folder.
Use the mod.jsons to get list of mods and compare with enabledmods.json to set which mods are enabled.

Could you move the new methods inside the new mod_management package?

Done o7

So this is supposed to load mods list even if there's no enabledmods.json, right?
If yes, it's not working on my end.

So this is supposed to load mods list even if there's no enabledmods.json, right? If yes, it's not working on my end.

Good catch. It should work even with enabledmods.json missing. Fixed in f3d2e63e6a8922bce9f40b6c00c11df5ff4c0850

@Alystrasz anything else or is the PR ready to merge? ^^

@Alystrasz anything else or is the PR ready to merge from your side? ^^

I still have to try it on my machine, I'll have time this evening (I hope) to review again!

When user doesn't have enabledmods.json on his computer, FC correctly shows up the mods, but it's not possible to disable them (all appear enabled).

When user doesn't have enabledmods.json on his computer, FC correctly shows up the mods, but it's not possible to disable them (all appear enabled).

This is sorta "intended behaviour" in the sense that the issue is that we cannot yet set the value of an entry in enabledmods.json that doesn't exists yet. I'm planning to address that in a next PR but given that rn an end-user cannot install a mod using FlightCore, they'll barely run into this issue before I'll address it ^^
As for the being enabled part if entry doesn't exists in enabledmods.json (or the file doesn't exist at all), that basically mirrors the behaviour in Northstar. Maybe enabledmods.json should be called disabledmods.json by Northstar :P

Dope, time to make next release :D


gulp-typescript >= 2.11.0 gives different src() paths from <=2.10.0

Expected behavior:
I have a tsconfig.json that has "files" section like following
{
  "compilerOptions": { ... },
  "files": [ "path-to-directory/filename.ts" ]
}

and in my gulpfile.js, I invoke gulp-typescript like
var ts = require('gulp-typescript');
...
var tsProject = ts.createProject('tsconfig.json', { sortOutput: true });
var tsResult = tsProject.src().pipe(ts(tsProject));

After that, the script change the path of the output *.js files to store appropriate directories.
Now, the problem I've encountered is that, when using gulp-typescript 2.10.0 or older, src() emits paths like 'path-to-directory/filename.ts', though, using 2.11.0 or higher, it emits './filename.ts' instead.
Is this change of path behavior intended?
If so, how should we think about src()'s output? I mean, relative paths from where?

Before 2.11, the directory of the tsconfig.json file was considered to be the root directory. That behavior was incorrect. In 2.11, the common directory of all files is used as the root directory, which matches the behavior of tsc. Thus, if you're tsconfig is located in ./ and all your files in ./lib, and you set outDir to ./dest these files will be emitted as ./dest/.jsinstead of./dest/lib/.js`.
You can change the root directory by setting the rootDir compiler option in your tsconfig.json file.

Aha!
That output path is what my script do for after compilation.
Now, I can remove such renaming code. It's great!


feat(terraform): ensure tflint is installed

Ensures tflint (terraform linter) is installed when lazyvim.plugins.extras.lang.terraform is enabled

Thanks!


RTL breadcrumbs

Changes

Refactors breadcrumbs to use flexbox for layout.
Adds RTL version of breadcrumbs for arabic pages.

How to test this PR

Visit pages with long breadcrumbs in LTR and RTL languages, and resize to mobile and see that the breadcrumbs wrap correctly.

http://localhost:8000/consumer-tools/educator-tools/youth-financial-education/teach/activities/
http://localhost:8000/language/ar/coronavirus/mortgage-and-housing-assistance/help-for-homeowners/
Screenshots
Before:

After:

Arabic example:

I think it would be even better to extend the molecule such that these templates don't need their own custom logic, but can pass custom breadcrumbs to a macro, etc.

Added breadcrumbs template to agreements in https://github.com/cfpb/consumerfinance.gov/pull/7790/commits/a950eb99a0b7a99c334c6f1d9aac67cd2e875806


Toomany Indirections

Having to navigate through multiple references can slow things down. Wondering if you are willing to try your https://github.com/ObjectLayout/ObjectLayout to speed up referencing where relevant and avoid object with data structure in object with data structure in object with data structure layout?

Yes, I agree. Especially the matching engine and order book reconstruction could be improved quite a bit in this regard.
Thanks for the heads-up on ObjectLayout, I'll have a look at it.

Regarding this, I had a look at the NASDAQ order books on one day in 2014. On that day AAPL had the following characteristics:

maximum number of concurrent orders: 29948
maximum number of concurrent orders on one price level: 1545
maximum number of concurrent price levels: 3588

These are something to keep in mind when thinking about the optimal data structures for the matching engine and order book reconstruction.


Runpod compability

Hello.
I've noticed that the extension doesn't work on Runpod (I get a blank page when I open the editing window).
I don't know how the extension works in detail, but I imagine it's because the FastAPI server is only accessible via localhost:7860.
I imagine this is the case for any Automatic1111 server that runs in a docker.
Are there any plans to address this issue?

The url localhost:7860 is not hardcoded anywhere here in this repository or in the ControlNet repository (Except for testing).
If you can access A1111 in your browser, technically you should be able to access the editor page. The extension mounts an extra route on FastAPI app called openpose_editor_index.
Is there any console output when you click Edit? (Both backend in the terminal and frontend in the browser devtool console)

Thank you for your reply.
Clicking on "Edit" does not display an error message in the editor or on the console.
The url through which I access automatic1111 takes the form https://-3000.proxy.runpod.net/, using the browser inpector, I noticed that requests were indeed being sent to https://-3000.proxy.runpod.net/openpose_editor_index/, but that the request was failing due to a timeout, which seems to indicate that the api is indeed unreachable.
Having fairly rudimentary knowledge of networking or how docker/runpod works, I'm not sure which direction to investigate from here.

Update :
I just noticed that Firefox was displaying "Blocked loading mixed active content" errors during requests (which is probably also a problem in itself), after (temporarily) disabling the corresponding security option, now I have the "connection timeout" error directly in the window that opens when I press "Edit".
The console also displays a "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource" error concerning the same url.

Are you sure the [some string] here are the same?
https://[some string]-3000.proxy.runpod.net/
https://[some string]-3000.proxy.runpod.net/openpose_editor_index/
If they are the same string, it should not violate the same origin policy.

Yes, it's an identifier that is specific to the server instance, a similar url is used to access jupyter for example.
On closer inspection, the error seems to stem from the fact that the openpose_editor_index request triggers a redirect to a different ip and port than the server's for some reason.

Fixed. See #27 for more details.


North Atlantic mask misses some ocean area between Greenland and Iceland

I followed the approach from tutorial notebook and created a mask for North Atlantic. However, there is a small region (see while space between Greenland and Iceland in figure) that has nan values, even though there is an ocean in between. I have tried creating masks with 1 deg and 0.25 deg. Both had this issue.

Thanks for raising the issue @hmkhatri. The masking is ultimately based on combining smaller named subregions from regionmask. I suspect that a new one of these regions has been added during a recent update
@mathause, is this possible (also sorry for not responding on that old issue)?
@hmkhatri, could you follow the docs like this:
basins = regionmask.defined_regions.natural_earth.ocean_basins_50
basins.plot(add_ocean=False, add_label=False)

and zoom in on this region? I would be very curious to see what is going on, but do not currently have time to dig into this myself.

Indeed, there is a a bit of ocean not part of any region - but it's the same with both versions of the naturalearthdata. v4.1 is orange and v5.0 is blue.

@jbusecke you'll be able to specify the naturalearthdata version once the new version is released.

The code requires regionmask master or the upcoming 0.9 release.

%matplotlib

import cartopy.crs as ccrs
import regionmask

line_kws = dict(color="#ff7f00", lw=2)
ax= regionmask.defined_regions.natural_earth_v4_1_0.ocean_basins_50.plot(resolution="50m", line_kws=line_kws)

line_kws = dict(color="#1f78b4", lw=2, ls=":")
ax = regionmask.defined_regions.natural_earth_v5_0_0.ocean_basins_50.plot(resolution="50m", line_kws=line_kws)
ax.set_extent([-40, -10, 60, 90], ccrs.PlateCarree())

@mathause @jbusecke Thanks for looking into this. Seems like some manual tweaking is needed to incorporate the missing region in the North Atlantic mask.
It is not a major issue and I managed to get rid of white space by combining North Atlantic mask and ocean wet point mask. It would be nice to update the code for correcting it.  I am busy for next few weeks, but I would be happy to work on this later.

Hey @hmkhatri, does the problem occur if you use
basins = regionmask.defined_regions.natural_earth_v4_1_0

as mentioned here? I have thought about making the basin masking even easier in #119. If the above fixes your problem, I would be inclined to lock down v4.1.0 from natural earth and exclusively use that in this functionality. From my perspective we mostly care about large ocean basins, and for smaller stuff folks could just use regionmaks with their shapefile of choice?

Bummer to see that this is in fact baked into both NE versions. I have been thinking about refactoring the basin masking ability (#119) and maybe this should be part of it. Using the wetmask is not ideal IMO, since this method should really just rely on the lon/lat values of the model (which makes it quite universal). All that cmip6_pp does is just combine a bunch of shapefiles, so its concievable that we just add a manual correction there?
Then again, since I wrote this, I have actually used this in many more use cases outside of cmip6. I wonder if such a refactor should maybe include efforts upstream, to just publish a NE shapefile with ocean basins? This seems of much broader use than just for the cmip community. @mathause have you interacted with that community at all?

@mathause have you interacted with that community at all?

No I didn't so far, but you have ;-) nvkelso/natural-earth-vector#319

I pinged them over in https://github.com/nvkelso/natural-earth-vector/issues/697. Lets see what they think.


favicon.ico missing

Some browsers require favicon.ico, express app crashes with error no such file or directory .../favicon.ico

Thanks @JiLiZART, I have already uploaded a favicon


Add warning entry for missing instance driver

Sounds similar to #9194 which is supposed to be fixed in 4.19 which is what I reproduced it with:
$ snap list lxd
Name  Version  Rev    Tracking       Publisher   Notes
lxd   4.19     21624  latest/stable  canonical✓  -

$ journalctl -b0 -o cat --grep ' lvl=warn msg="'
t=2021-10-07T10:50:01-0400 lvl=warn msg=" - Couldn't find the CGroup blkio.weight, disk priority will be ignored"
t=2021-10-07T10:50:01-0400 lvl=warn msg="Instance type not operational" driver=qemu err="KVM support is missing" type=virtual-machine

$ lxc warning ls --all
+--------------------------------------+---------------------------------------+--------------+----------+-------+---------+-----------------------------+
|                 UUID                 |                 TYPE                  |    STATUS    | SEVERITY | COUNT | PROJECT |          LAST SEEN          |
+--------------------------------------+---------------------------------------+--------------+----------+-------+---------+-----------------------------+
| 64cb3bf5-ffa4-4c91-8b4f-0e71673022da | Couldn't find the CGroup blkio.weight | ACKNOWLEDGED | LOW      | 41    |         | Oct 7, 2021 at 2:50pm (UTC) |
+--------------------------------------+---------------------------------------+--------------+----------+-------+---------+-----------------------------+

In the last command, I would expect the "KVM support is missing" to show up.

I think that's because it usually gets logged as part of the startup-time messages and those are shown as a list, @monstermunchkin would know for sure :)

@stgraber Can I tackle this one?

Assigned to you. Thanks


⚠ Bofrost.at has degraded performance

In e1639c8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1343 ms

Resolved: Bofrost.at performance has improved in 1e9a74e after 10 minutes.


[CPU] Unify distribution tile size selection heuristic.

The revision removes special distribution heuristics for CPUDefault. It does not impact lit tests because the unified method covers some of them. The revision introduces a DistributionHeuristicConfig struct to hold heuristic factors. This avoids having four optional function arguments. We want to land two changes together because the intermediate stage looks bad.
The removal changes are in https://github.com/openxla/iree/pull/15928/commits/13d4b8a90368f5049c7623a803b3070ef6829c84 The DistributionHeuristicConfig struct changes are in https://github.com/openxla/iree/pull/15928/commits/723560774155d1ed8c32e96978691623ca1da59f.

The review would be easier if you review https://github.com/openxla/iree/commit/13d4b8a90368f5049c7623a803b3070ef6829c84 first, then https://github.com/openxla/iree/commit/723560774155d1ed8c32e96978691623ca1da59f


Test - add more tests

Created and updated the test cases. Fixed variable naming and checkstyle issues.

Close issue #68


[BUG] Currently, many-to-many entities must establish bidirectional associations. Otherwise, when deleting an entity, an error of 'still referenced' will be thrown at the database level.

For two entities with many-to-many associations, if only one side establishes a unidirectional many-to-many association, the following error will be thrown:
Key (id)=(77) is still referenced from table "user_role_mapping"

Fixed.


Aura Uploading + Client

Hello!
This inspired me! I spent some time over the past week looking into more of the Aura Frames API and ended up writing a client that tries to implement more functionality: https://github.com/zmanowar/auraupload
Lots of TODOs (and ugly patterns to fix) left but thought I'd shoot you a link in case you were curious!
Cheers

Nice, this is cool! I'll check it out. Glad you were inspired :)


On cluster, when run is hotReloadCapable, the Build command is not called after source sync

/kind bug
On cluster, when Run command is hotReloadCapable, the Build command is not executed after source sync.
On Podman, the Build command is executed after each source sync.
What versions of software are you using?
odo v3.8.0

Link to PR in devfile/api : https://github.com/devfile/api/pull/1091

Should not be merged before https://github.com/redhat-developer/odo/issues/6747 is closed/validated.


Fix color rendering bug introduced in parse_archit branch

It's related to issue #41

Resolved but replaced with another bug


Updating firmware on the field

Hi,
Not really a meta-tegra issue but just a general question to the users here.
Tegra flash will always format and overwrite the eMMC module. It’s obviously good for production.
I’d like to be able to upgrade our Tegra based firmware by inserting a USB stick / or download some sort of image on a different partition, then format the partitions one by one and exclude the ones with persistent data.
Where would you implement this?
I could for example format and write the image partition from initramfs script. Would it be wise to do it there or do you raise some red flags?
But what if I need to re-write the initramfs image or update the kernel then? Should this be implemented from u-boot or elsewhere? Any pointers at example or how to get started?
Thanks,

@lfdmn you could accomplish this with mender and standalone deployments.  If you'd rather not use mender you could use the source code to help understand how to implement your own scheme.  See https://github.com/Trellis-Logic/meta-mender-community/pull/11 for the latest zeus branch I've tried based on @madisongh's latest, just waiting on a Zeus update for https://github.com/mendersoftware/meta-mender-community before merging this.

Do not mean to hog the thread, but @dwalkes, Just an FYI, I started a zeus-test branch and will accept PR's there and convert that to a proper zeus branch once upstream has been tagged.

Thanks @mirzak I'll see if I can get a PR started there over the weekend.

Thanks @dwalkes, it looks interesting

i think your better of using ruac, ostree and aktualizer then mender.....

This topic has come up several times in different contexts.  I'm going to close this issue now - please feel free to start a discussion if you'd like to discuss further.


add codeowners file

This restricts approving PRs (that change any file) to members of the core team. On top, it automatically notifies them when a new PR is opened.

Actually this file alone does not restrict anything. But having allows us to add a branch protection rule that adds this restriction.


Add support for embeddable translations

Description
Right now crystal-i18n requires raw translations to be available on the file system where compiled binaries are deployed in order to allow translation lookups. While this works fine for a number of use cases, a common need is to be able to embed the raw translations inside compiled binaries.
In order to support this, we could allow translation loaders to define an optional embed macro that would be used to initialize loaders whose translations are embedded in the final binary:
I18n.config.loaders << I18n::Loader::YAML.embed("config/locales")

A simple emebed macro would already go a great way to enable self-contained applications.
As an idea for further enhancements I'd like to point to crinja's loader system: https://github.com/straight-shoota/crinja/blob/15c267c5280bcb78a1f3f472ac5cb3843176fdd1/src/loader.cr
It serves a similar purpose for loading templates at runtime, either from the file system or baked in. It's also extensible to allow additional sources (for example a database). There's also a component for overrides / fallback behaviour: ChoiceLoader. The exact usage requirements are a bit different because templates can be dynamically loaded at any point, whereas translations a probably loaded only once during the runtime of a program. But I could still see value in a hierarchial system, which essentially allows fallbacks for translation terms. For example the base translations for an app would be baked in, but they can be selectively overriden by translations in the local file system, or a database.

Thanks for your suggestion! 😃
I will have a look at it. Right now it's possible to configure multiple translations loaders and they are all used to initialize a single catalog of translations by default (the one used when doing lookups with the top-level I18n.t): this means that the order of loaders is important because the latest loaders can in theory "override" the translations that were defined by previous loaders. This "override" behavior only applies for a given locale of course ; fallbacks between locales are handled a bit differently through a dedicated configuration option.

Thanks @ellmetha 🙏🏻


[bug][v2][linux] fails to run on Fedora 40 tauri appimage built on GitHub Actions

Describe the bug
fails to run on Fedora 40 tauri appimage built on GitHub Actions.
in console output, those log are shown
Cannot get default EGL display: EGL_SUCCESS
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
Violación de segmento (`core' generado)

Downstream issue: vrc-get/vrc-get#1405
Reproduction

Build tauri app with github actions. I made this for testing
fails to launch tauri app due to error above

Expected behavior
No response
Full tauri info output
[✔] Environment
    - OS: Mac OS 14.4.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.81.0-beta.2 (08328a323 2024-07-25)
    ✔ cargo: 1.81.0-beta.2 (a2b58c3da 2024-07-16)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: beta-aarch64-apple-darwin (default)
    - node: 22.6.0
    - pnpm: 8.15.4
    - npm: 10.8.2

[-] Packages
    - tauri [RUST]: 2.0.0-rc.6
    - tauri-build [RUST]: 2.0.0-rc.6
    - wry [RUST]: 0.42.0
    - tao [RUST]: 0.29.1
    - tauri-cli [RUST]: 2.0.0-rc.3
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-rc.7

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: web

Stack trace
No response
Additional context
No response

Hi!
It is working fine here on Fedora 40 ( in VM hosted on Arch Linux via VirtualBox )

Are you using wayland by any chance?

https://github.com/vrc-get/vrc-get/issues/1405#issue-2482510583

I'm using Fedora 40, running Wayland.

Original reporter is using Wayland

It works on my Fedora system (a real one, not a VM) too but the error somewhat sounds like something nvidia specific which i can't test.
Can you ask your users to run the app with the WEBKIT_DISABLE_COMPOSITING_MODE=1 and/or WEBKIT_DISABLE_DMABUF_RENDERER=1 env var(s) set? This typically helps with nvidia specific issues (though this specific error is new to me so no promises)

Original reporter here! The system where I was having the issue does indeed have an nvidia GPU. I've just tried running the Tauri simple app on a laptop without an nvidia GPU also running Fedora 40 and the application indeed works. I'll try those env variables on my other system with the nvidia GPU and report back once I get home in a few hours.

Running the application using the WEBKIT_DISABLE_DMABUF_RENDERER=1 env variable works.

Okay that's good i guess. It also means that this issue isn't really in our hands though :/ (as long as we keep using webkitgtk).

Is there anything I can do for improving this problem?

You could use std::env::set_var to set said env var for every user of your app. Of course that reduces performance for those where the renderer does work fine.
Alternatively, we can only wait for new webkitgtk releases. They are actively working on the renderer (which at the same time is the reason why webkitgtk broke for so many people in the first place).

I thought "as long as we keep using webkitgtk" means it's not fixable due to architecture or something hard to fix in webkitgtk.
but if it might be fixed, I'll just just wait for newer release. Thank you!


[APPM-745] POST data is resent with the throttleout message

Request   POST http://gw.am.wso2.com:8285/restapi01/1.0/rest/user/add  POST data: {"employeeId":3,"firstName":"Andy1","lastName":"Perera","salary":133000.0,"status":"NOTSUSPENDED"}   Response   {"fault":{"code":"900800","message":"Message Throttled Out","description":"You have exceeded your quota"},"firstName":"Andy1","lastName":"Perera","salary":"133000.0","status":"NOTSUSPENDED"}   Issue : The POST data is sent back with the request. Reference: https://wso2.org/jira/browse/APPM-745

Not related to IoT server, hence closing


Removing an item from the "Hit" Report goes sometimes wrong

If the item to be removed is a variable and it is not the last one then all remaining ones disappear.

Note reproducible


Macro error in runnable.cr:4

Hi,
i created a project with crystal init app issue-minitest and added minitest to the dependencies and when i run the specs i get this error:
Error in ./libs/minitest/autorun.cr:9: instantiating 'Minitest:Module#run(Array(String))'

  exit_code = Minitest.run(ARGV)
                       ^~~

in ./libs/minitest/minitest.cr:72: instantiating 'Minitest::Runnable:Class#runnables()'

    suites = Runnable.runnables.shuffle
                      ^~~~~~~~~

in ./libs/minitest/minitest/runnable.cr:4: macro didn't expand to a valid program, it expanded to:

================================================================================
--------------------------------------------------------------------------------
  1. Minitest::Test, Minitest::Spec, Issue::MinitestSpec
--------------------------------------------------------------------------------
Syntax error in expanded macro: macro_85674176:1: unexpected token: EOF

Minitest::Test, Minitest::Spec, Issue::MinitestSpec
                                                   ^

================================================================================

      [self, {{ @type.all_subclasses.join(", ").id }}]

I also receive the error in my projects.
Crystal: 0.17.3
Minitest: master (v0.3.4)

I'm afraid I can't reproduce this. I created a project with Crystal 0.17.3 as you explained, then added Minitest 0.3.4 and modified spec/spec_helper.cr to require minitest/autorun instead of spec and I don't have this error.

The bug comes from using Minitest 0.3.3. Double check that the dependency is correct with: crystal deps list. If not you may remove libs/minitest then reinstall the dependency with crystal deps.

Thanks, silly mistake on my side. My project used a custom fork which was stuck on 0.3.3. Sorry :disappointed:

No problem :)


chore: switch to new maintainers package and upgrade version

This change removes the dependency on log4j 2.13.2, which contains a critical vulnerability, by switching to the new maintainers package and upgrading the version.
https://github.com/GradleUp/shadow?tab=readme-ov-file#gradle-shadow

Fixes #?
Context

Checklist

[ ] Review Contribution Guidelines.
[ ] Make sure all contributed code can be distributed under the terms of the
Apache License 2.0, e.g. the code was written by
you or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Update documentation when applicable.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Appears that the windows-latest build failure is a pre-existing failure and not related to these changes.

That is correct. Failures occur due to a file descriptor still in use when another task attempts to write to a file.

Thank you 😄


issue if there is just 1 video story

hi,
the app crashes if there is just 1 video story item. the storyItems must be just StoryItem(type:video) to replicate it.  having said that there must be no one more any other story. once the video story finish following crash occures:
A VideoPlayerController was used after being disposed.

Thanks for reporting @aligurelli. Let us investigate this issue and resolve this as soon as we can


Update clustered-indexes.md

Docs Build status updates of commit 09e5909:
:clock10: Full build: the average full build time is 6 min(s) 41 sec(s), this is based on the last 10 build(s) for this repository.
:warning: This is a FULL build due to a recent Docs Build service upgrade, normally no action is required on your part. In the result you find subsequent builds still performing full builds, please contact your repository admin to manually perform a full build on the 'live' branch. For more detailed info, please click here.

Docs Build status updates of commit 09e5909:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamicsax2012-msdn/clustered-indexes.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgergdpdutablefilenameidx-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupassetparametersdeprrates-dedei-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/entry-element.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtrans-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-basic-updatemappingsysrecordlevelsecurity-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcourseattendee-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/troubleshooting-forms.md
:warning:Warning
View
Details

dynamicsax2012-msdn/best-practices-for-perspectives.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupassetparametersdeprrates-dedat-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgergdpdurelationrelationidx-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/entity-overview-page-reference.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtrans-ru-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-basic-updatemappingfields-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompvarplanlevel-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/troubleshooting-enterprise-portal-development.md
:warning:Warning
View
Details

dynamicsax2012-msdn/best-practices-for-parameters.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupassetdepreciationzakat-saasset-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgergdpdufieldlinenumidx-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/effects-of-valid-time-state-tables-on-read-and-write-operations.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtrans-in.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatetransformdb50-basic-rcontracttypespreupgradeprocess-ru-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompvarenrollemplline-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/troubleshooting-charts.md
:warning:Warning
View
Details

dynamicsax2012-msdn/best-practices-for-designing-reports.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allowduptaxyearlycomsetupexclude-itexclu-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgergdpdufieldfieldnameidx-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/effect-of-disabling-a-table-or-column.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtrans-in-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatetransformdb50-basic-rcontracttypesdeltapreupgradeprocess-ru-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompvarenrollempl-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/troubleshooting-application-explorer.md
:warning:Warning
View
Details

dynamicsax2012-msdn/best-practices-for-constructors.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allowduptaxwithholdthresholdlimit-intaxw.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgerclosingtableshmnacctidx-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/edt-relation-migration-tool.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtable-taxsubstitution-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatetransformdb50-basic-rcontracttablepreupgradeprocess-ru-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompvarawardempl-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/troubleshooting-a-workspace.md
:warning:Warning
View
Details

dynamicsax2012-msdn/best-practice-for-destructors-finalize.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allowduptaxwithholdthresholdlimit-intaxw-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgerchartofaccountstreelevel.md
:warning:Warning
View
Details

dynamicsax2012-msdn/editor-scripts.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtable-taxsubstitution-br-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatetransformdb50-basic-rcontracttabledeltapreupgradeprocess-ru-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompperfplanempl-upgrade-script.md
:warning:Warning
View
Details

dynamicsax2012-msdn/transaction-integrity.md
:warning:Warning
View
Details

dynamicsax2012-msdn/best-practice-design-guidelines-for-cost-efficient-upgrades.md
:warning:Warning
View
Details

dynamicsax2012-msdn/releaseupdatedb60-ledger-allowduptaxwithholdthresholdlimit-in-upgrade-script.md
:warning:Warning
View
Details

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

dynamicsax2012-msdn/clustered-indexes.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgergdpdutablefilenameidx-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupassetparametersdeprrates-dedei-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/entry-element.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtrans-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-basic-updatemappingsysrecordlevelsecurity-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcourseattendee-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/troubleshooting-forms.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/best-practices-for-perspectives.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupassetparametersdeprrates-dedat-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgergdpdurelationrelationidx-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/entity-overview-page-reference.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtrans-ru-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-basic-updatemappingfields-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompvarplanlevel-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/troubleshooting-enterprise-portal-development.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/best-practices-for-parameters.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupassetdepreciationzakat-saasset-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgergdpdufieldlinenumidx-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/effects-of-valid-time-state-tables-on-read-and-write-operations.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtrans-in.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatetransformdb50-basic-rcontracttypespreupgradeprocess-ru-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompvarenrollemplline-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/troubleshooting-charts.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/best-practices-for-designing-reports.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
Line 93: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/cc593896' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.
Line 93: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/cc624233' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.
Line 97: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/cc571180' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.
Line 102: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/gg731917' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allowduptaxyearlycomsetupexclude-itexclu-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgergdpdufieldfieldnameidx-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/effect-of-disabling-a-table-or-column.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
Line 38: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/cc615265' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtrans-in-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatetransformdb50-basic-rcontracttypesdeltapreupgradeprocess-ru-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompvarenrollempl-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/troubleshooting-application-explorer.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/best-practices-for-constructors.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allowduptaxwithholdthresholdlimit-intaxw.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgerclosingtableshmnacctidx-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/edt-relation-migration-tool.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
Line 89: [Suggestion] Link 'http://go.microsoft.com/fwlink/?linkid=213126&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'. NOTE: This Suggestion will become a Warning on 12/20/2019.

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtable-taxsubstitution-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatetransformdb50-basic-rcontracttablepreupgradeprocess-ru-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompvarawardempl-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/troubleshooting-a-workspace.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
Line 32: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/aa496447(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.
Line 40: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/aa496447(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.
Line 44: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/aa496447(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.
Line 58: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/aa496447(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.
Line 62: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/aa496447(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.
Line 66: [Suggestion] Link 'https://msdn.microsoft.com/en-us/library/aa496447(v=ax.60)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

dynamicsax2012-msdn/best-practice-for-destructors-finalize.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allowduptaxwithholdthresholdlimit-intaxw-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allownodupledgerchartofaccountstreelevel.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/editor-scripts.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-updatetaxtable-taxsubstitution-br-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatetransformdb50-basic-rcontracttabledeltapreupgradeprocess-ru-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-hrm-updatehrmcompperfplanempl-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/transaction-integrity.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/best-practice-design-guidelines-for-cost-efficient-upgrades.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

dynamicsax2012-msdn/releaseupdatedb60-ledger-allowduptaxwithholdthresholdlimit-in-upgrade-script.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.

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


RangeError: Maximum call stack size exceeded

I was trying set up standard for mocha.
$standard --env mocha
I'm getting the following error logs on console.
Error:
standard: Unexpected linter output:
RangeError: Maximum call stack size exceeded
logs:
at Array.values (native)
at findVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:141:42)
at findVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:145:24)
at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:299:34)
at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)
at checkVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:386:21)
at checkVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)

I'm getting the same thing:
RangeError: Maximum call stack size exceeded
    at findVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:141:40)
    at findVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:145:24)
    at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:299:34)
    at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)
    at checkVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
    at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
    at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)
    at checkVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
    at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
    at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)

This is only happening on one project. Other projects on the same system seem to lint fine.

Same thing here. npm install standard --global; standard ... RangeError etc.

Same here as well

I was saw this problem on a project I am working on as well with version 10.0.2 of standard on OSX 10.12.5. The error message was
standard: Unexpected linter output:

RangeError: Maximum call stack size exceeded
    at inspect (util.js:168:13)
    at exports.format (util.js:69:24)
    at Console.log (console.js:43:37)
    at findVariable (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:139:13)
    at findVariable (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:147:24)
    at checkDestructuring (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:302:34)
    at checkProperties (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:376:21)
    at checkVariable (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:407:13)
    at checkDestructuring (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:304:21)
    at checkProperties (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:389:21)

After adding some debugging information to node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js so that I could see the file that was being checked I discovered that I had a nested folder with node_modules in it that appeared to be being checked by eslint. The path was something like /project-folder/nested-folder/node_modules/babel-jest/build/index.js.
Not sure if this is the actual problem or if I was just lucky that removing this unneeded folder solved my issue.

I see the same issue on npm repo reproduced via travis https://travis-ci.org/npm/npm/jobs/251196118

Same here on Linux, npm 5.0.3, standard 10.0.2 and eslint-plugin-node 4.2.2

https://github.com/standard/standard/issues/933

@vramana, @luispabon, @gingermusketeer i may help if post some files, or part of the files :)

@tunnckoCore You can reproduce it with npm latest branch. The error triggers on Travis, so you can use Travis if you can't reproduce it on your machine.

Okay, the empty project was somehow picking a file on the parent folder containing some dodgy code I reckon standard is looping through forever. I've managed to distill it all down to:
let fs = fs || require('fs')

Steps to reproduce:

make a folder somewhere
make a .js file containing the code above
run npm install standard
run node_modules/.bin/standard
Profit!

It seems specific to the fs component though.

Now we can close this, @ematipico :) v4.2.3 is released by @mysticatea! :tada:

Cool, if folks are having issues still, reinstall standard and it should pull the the fix down :)


US08: The question is displayed for both players.

See commit 994b6dc (https://github.com/sopra-fs24-group-34/sopra-fs24-group-34-client/commit/994b6dc4464b94d28aec735cb8fdf601284fb5c0)


fastlane snapshot uninstalls on all simulators after each test instead of just one

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
When I run snapshot in a simple lane containing:
    snapshot(
      languages: ["en-CA"],
      clear_previous_screenshots: true,
      app_identifier: "net.example.myapp",
      reinstall_app: true,
      number_of_retries: 3,
    )

For each device in the default list of devices being screenshot I see the roughly the following output:
[##:##:##]: Running Tests: ▸ Touching MyAppUITests.xctest
[##:##:##]: ▸ Signing {tmp}/Build/Products/Debug-iphonesimulator/MyAppUITests-Runner.app/PlugIns/MyAppUITests.xctest
[##:##:##]: ▸ All tests
[##:##:##]: ▸ Test Suite MyAppUITests.xctest started
[##:##:##]: ▸ AnonymousScreenshotTests
[##:##:##]: ▸ ✓ testLoginScreen (9.575 seconds)
[##:##:##]: ▸ AuthenticatedScreenshotTests
[##:##:##]: ▸ ✓ testInboxScreen (20.722 seconds)
[##:##:##]: ▸ 	 Executed 2 tests, with 0 failures (0 unexpected) in 30.296 (30.300) seconds
[##:##:##]: ▸
[##:##:##]: ▸ All tests
[##:##:##]: ▸ Test Suite MyAppTests.xctest started
[##:##:##]: ▸ 	 Executed 0 tests, with 0 failures (0 unexpected) in 0.000 (0.000) seconds
[##:##:##]: ▸
[##:##:##]: Collecting screenshots...
[##:##:##]: Found 2 screenshots...
[##:##:##]: Copying '{...}/fastlane/screenshots/en-CA/...-LoginScreen-....png'...
[##:##:##]: Copying '{...}/fastlane/screenshots/en-CA/...-InboxScreen-....png'...
[##:##:##]: snapshot run # of #
[##:##:##]: Patching all simulators '/Users/me/Library/Preferences/com.apple.iphonesimulator.plist' to scale to 100%
[##:##:##]: Launch Simulator iPhone 4s
[##:##:##]: $ xcrun instruments -w 51F98A72-DD48-4EF0-95C4-D32F8513BFF8 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 51F98A72-DD48-4EF0-95C4-D32F8513BFF8 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPhone 5
[##:##:##]: $ xcrun instruments -w AA906D32-C37F-476A-9706-3D7A9DA6C79F &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall AA906D32-C37F-476A-9706-3D7A9DA6C79F net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad Air
[##:##:##]: $ xcrun instruments -w 79CE4238-ECD7-4C91-BA8E-270C9B159338 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 79CE4238-ECD7-4C91-BA8E-270C9B159338 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPhone 4s
[##:##:##]: $ xcrun instruments -w 51F98A72-DD48-4EF0-95C4-D32F8513BFF8 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 51F98A72-DD48-4EF0-95C4-D32F8513BFF8 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPhone 5
[##:##:##]: $ xcrun instruments -w AA906D32-C37F-476A-9706-3D7A9DA6C79F &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall AA906D32-C37F-476A-9706-3D7A9DA6C79F net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad Air
[##:##:##]: $ xcrun instruments -w 79CE4238-ECD7-4C91-BA8E-270C9B159338 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 79CE4238-ECD7-4C91-BA8E-270C9B159338 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPhone 4s
[##:##:##]: $ xcrun instruments -w 51F98A72-DD48-4EF0-95C4-D32F8513BFF8 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 51F98A72-DD48-4EF0-95C4-D32F8513BFF8 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPhone 5
[##:##:##]: $ xcrun instruments -w AA906D32-C37F-476A-9706-3D7A9DA6C79F &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall AA906D32-C37F-476A-9706-3D7A9DA6C79F net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad Air
[##:##:##]: $ xcrun instruments -w 79CE4238-ECD7-4C91-BA8E-270C9B159338 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 79CE4238-ECD7-4C91-BA8E-270C9B159338 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad Pro
[##:##:##]: $ xcrun instruments -w C9622226-ABF2-448F-AD55-75EBDFD557FA &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall C9622226-ABF2-448F-AD55-75EBDFD557FA net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPhone 5
[##:##:##]: $ xcrun instruments -w AA906D32-C37F-476A-9706-3D7A9DA6C79F &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall AA906D32-C37F-476A-9706-3D7A9DA6C79F net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPhone 7
[##:##:##]: $ xcrun instruments -w 9C83729B-AD72-4791-BAFE-ACF5A5D4151D &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 9C83729B-AD72-4791-BAFE-ACF5A5D4151D net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPhone 7 Plus
[##:##:##]: $ xcrun instruments -w 624D086C-4676-4334-8BB6-E673B63E2DDC &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 624D086C-4676-4334-8BB6-E673B63E2DDC net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad Air
[##:##:##]: $ xcrun instruments -w 79CE4238-ECD7-4C91-BA8E-270C9B159338 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 79CE4238-ECD7-4C91-BA8E-270C9B159338 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad (5th generation)
[##:##:##]: $ xcrun instruments -w 06CE24F6-A10A-4964-AB33-BE8F7F2C2E36 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 06CE24F6-A10A-4964-AB33-BE8F7F2C2E36 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad Pro (9.7 inch)
[##:##:##]: $ xcrun instruments -w 47385F91-1BBF-4F68-ABFD-F19A374BED4E &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 47385F91-1BBF-4F68-ABFD-F19A374BED4E net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad Pro (12.9 inch)
[##:##:##]: $ xcrun instruments -w 1C0BA064-4D4A-4FF2-9588-72B685874F46 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 1C0BA064-4D4A-4FF2-9588-72B685874F46 net.example.myapp &> /dev/null
[##:##:##]: Launch Simulator iPad Pro (10.5-inch)
[##:##:##]: $ xcrun instruments -w 43A51F04-5ACA-4442-8AC3-643A53C4C737 &> /dev/null
[##:##:##]: Uninstall application net.example.myapp
[##:##:##]: $ xcrun simctl uninstall 43A51F04-5ACA-4442-8AC3-643A53C4C737 net.example.myapp &> /dev/null

As you can see, after it successfully executes the tests for one device, it in turn launches every single simulator to uninstall the app (and this actually launches a new simulator and waits a bit as it partially boots up). ie: Instead of only uninstalling the app for the device that was just used or the device that'll be used next or only uninstalling on every device at the start and end of the lane, it launches every single simulator after every single test/screenshot run on a single device.
Edit: I stripped out the timestamps to make the output match between runs, but that process from "Patching all simulators" to when it finishes uninstalling from the last simulator takes about 4-5 minutes to complete. After each device snapshot run.
So if you are snapshotting 5 devices snapshot will: Launch A, Run test/snapshot, (Launch A, uninstall, Launch B, uninstall, Launch C, uninstall, Launch D, uninstall, Launch E, uninstall), Launch B, Run test/snapshot, (Launch A, uninstall, Launch B, uninstall, Launch C, uninstall, Launch D, uninstall, Launch E, uninstall), Launch C, Run test/snapshot, (Launch A, uninstall, Launch B, uninstall, Launch C, uninstall, Launch D, uninstall, Launch E, uninstall), Launch D, Run test/snapshot, (Launch A, uninstall, Launch B, uninstall, Launch C, uninstall, Launch D, uninstall, Launch E, uninstall), Launch E, Run test/snapshot, (Launch A, uninstall, Launch B, uninstall, Launch C, uninstall, Launch D, uninstall, Launch E, uninstall), Launch F, Run test/snapshot, (Launch A, uninstall, Launch B, uninstall, Launch C, uninstall, Launch D, uninstall, Launch E, uninstall)
Instead of sanely just doing: (Launch A, Run test/snapshot, uninstall), (Launch B, Run test/snapshot, uninstall), (Launch C, Run test/snapshot, uninstall), (Launch D, Run test/snapshot, uninstall), (Launch E, Run test/snapshot, uninstall)
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.0.0

Bundler?
true

Git
git version 2.11.0 (Apple Git-81)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.12.6 (16G29)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib

OpenSSL Version
OpenSSL 0.9.8zc 19 Mar 2015

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.3.3

System Locale

Variable
Value

LANG
en_CA.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
{redacted}

`./fastlane/Appfile`
{redacted}

fastlane gems

Gem
Version
Update-Status

fastlane
2.54.3
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-versioning
0.2.7
✅ Up-To-Date

fastlane-plugin-android_versioning
0.3.0
✅ Up-To-Date

Loaded gems

Gem
Version

bundler
1.14.6

CFPropertyList
2.3.5

public_suffix
2.0.5

addressable
2.5.2

babosa
1.0.2

claide
1.0.2

colored
1.2

colored2
3.1.2

highline
1.7.8

commander-fastlane
4.4.5

declarative
0.0.9

declarative-option
0.1.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

dotenv
2.2.1

excon
0.58.0

multipart-post
2.0.0

faraday
0.13.1

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.12.2

fastimage
2.1.0

gh_inspector
1.0.3

jwt
1.5.6

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

memoist
0.16.0

os
0.9.6

signet
0.7.3

googleauth
0.5.3

httpclient
2.8.3

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.1.0

representable
3.0.4

retriable
3.1.1

google-api-client
0.13.4

json
2.1.0

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.3.0

rubyzip
1.2.1

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.8.0

unicode-display_width
1.3.0

terminal-table
1.8.0

tty-screen
0.5.0

word_wrap
1.0.0

nanaimo
0.2.3

xcodeproj
1.5.1

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
0.0.4

fastlane-plugin-android_versioning
0.3.0

fastlane-plugin-versioning
0.2.7

generated on: 2017-08-29

Hey @dantman - this is definitely a wild issue and for some reason I am not able to reproduce it on my own apps. Out of curiosity, are you running against Xcode 8 or a 9 beta?

Ah! I just was able to reproduce this issue, I missed the place where you were setting reinstall_app: true. Seems like that param causes some issues that we should look into fixing. Just curious: is there a particular reason you are using that flag?

@ohayon Still using XCode 8. I want to make sure tests start with a clean install (not using the release version, not already logged in, etc...).

This bug is still present. The fix for this is in PR #10459, which has not been merged yet.


[CST-5341] Link back to the item page in the now downloading page

References

Fixes #1477

Description
A "Back" button has been added to the download page
Instructions for Reviewers
Open any item with an attached file, e.g. this one, and download the file. The download page should have a "Back" button.

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes TSLint validation using yarn run lint
[x] My PR doesn't introduce circular dependencies
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

Hi @tdonohue, I changed the position of the button


Unified Databricks OpenAPI client

So it looks like attempting to merge the SDKs with the new OpenAPI schema is a bad idea: rust-analyzer does great but is overwhelmed with the amount of output. Closing to revisit splitting the schema into an SDK per domain.


Document app_key in configuration template

What does this PR do?
Documents app_key by adding it to the configuration template.
Also updates the link related to creating API keys.
Motivation
The application key can be used by the Datadog Intelligent Test Runner to query account settings when running in EVP mode.
Describe how to test/QA your changes
This PR was tested by:

running Datadog Agent locally
specifying app_key in the agent config (using the web UI) and restarting
running Datadog's Test Visibility product (using pytest) with the Intelligent Test Runner active, in EVP (non-agentless) mode
verifying that no error was received during the feature enablement check

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

I haven't added a team/* label since this shouldn't need QA.
I did not notify the docs team because the agent config page ( https://docs.datadoghq.com/agent/guide/agent-configuration-files/?tab=agentv6v7 ) does not explicitly list config keys, and instead says to refer to the configuration template.


Document the background growth of data in the cluster caused by timeseries data

Apologies if we already mention this somewhere. There's two pieces of this that are confusing -- the increase of the live bytes metric (as asked about here) and the increase in memory usage up to the RocksDB cache size (as asked about a number of times, but I don't have any examples offhand).
Would this fit in the FAQ, perhaps? Or should it be posted to StackOverflow?

Duplicate of #957


Update the readme to include new best practices from guild meeting

Summary
I've added some best practices that we had discussed on the iOS guild day last year.

Immutable over mutable variables and objects. (was already included)
Structs over classes. - I did not remember the rationale for this rule
Classes final by default. (was already included)
Prefer private by default. (was already included)
Fail loudly over silent errors.
Fail at compile time over runtime.
Avoid casting protocols to concrete objects.
Reduce the amount of third-party libraries.

Reasoning
We should keep our best practices up to date with the latest suggestions from the entire team.
Please react with 👍/👎 if you agree or disagree with this proposal.

Structs over classes
Also having a hard time calling this one way or another. Structs are kinda cool until you start putting reference types inside of them. They they become some kind of a Frankenstein's monster that's only partially copy-on-write.


Added Billing RP and Consumption RP Specs for GTM

Added Billing RP and Consumption RP Specs for GTM
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

Mind telling me which API Version this one is most similar to, so that I can expedite review?

@marstr Sure! This is similar to version 2018-03-01-preview. We have added some new APIs.

@asarkar84 - please set up a sync to go over the new APIs for GTM over skype. Loop in armapireview

Sure! Scheduling a meeting.

@asarkar84 Please add me to the invite as well.

Reviewed over skype call.

After the API Review board and meeting with the ARM team, are the changes in this PR settled enough for SDK review?

@marstr We have formalized most of the fields but there might be some additional properties which may be added or some properties may get renamed in next couple of weeks based on requirement changes. Those will not be major tough.

@asarkar84 says:
some additional properties which may be added or some properties may get renamed in next couple of weeks based on requirement changes

Mind if we close this PR and open it (or a new one) again when you believe it will be in a finalized state?  :)

I'm going to go ahead and close this for now. Feel free to ping me and/or my boss @salameer to have it re-opened.


Line breaks are weird for copy/pasting

When creating a new swarm, I do:

I then select that whole text and then when I paste it in a new instance, I get:

It seems as though the line breaks or character encoding isn't entirely happy with the clipboard or something like that.
Running on macOS Sierra + Chrome latest

@gvilarino got what you say, basically when the newline occurs, if you copy then a \n character will be copied which makes it impossible to paste it afterwards
@akalipetis do you know anything about this?

Yeah, that's spot on

I'll take a look @marcosnils @gvilarino - I believe this has been fixed in a recent version of Xterm.js.

@akalipetis thx. I'll try to update locally and let you know. Is it fixed in the core or though a plugin?

I'll need to take a look @marcosnils, not sure about this sorry.
On Tue, Dec 6, 2016 at 6:36 PM Marcos Nils<EMAIL_ADDRESS>wrote:

@akalipetis https://github.com/akalipetis thx. I'll try to update
locally and let you know. Is it fixed in the core or though a plugin?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/franela/play-with-docker/issues/66#issuecomment-265199243,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwHoiWf-72NlCVhxI3_hfpSVD4XZN7nks5rFY70gaJpZM4LEt7i
.

@akalipetis tried updating but nothing happened :(

Ok, I've lost track of this one. This is currently a bug in Xterm.js - the wrapped lines get a newline character at the end.
The best solution would be to give a minimum width to the Terminal maybe for now?
I have opened an Xterm.js issue too for tracking: sourcelair/xterm.js#443

@akalipetis thx for following up. I guess we can wait until this gets fixed in Xterm.js.

This has been finally fixed by the xterm.js team. Thx @tyriar for the hard work!


lmdb: Reduce number of heap allocations of MDB_val

I'm currently looking at allocation counts in the codebase I am working on, and I noticed that lmdb-go allocates short lived MDB_val objects, e.g. on every call to Txn.Get.
Would it be possible / safe to cache one or two MDB_val in Txn, and re-use them in Txn.Get and friends? I think there might be an issue with RawRead Txns, but I'm not sure I understand the code base sufficiently.
If this sounds like it could work I'd be happy to contribute a PR. It is not a straight up performance win, but it should reduce the pressure on the GC when querying lots and lots.

Hrm. Storing pointers to two MDB_vals in the Txn object sounds like it might speed things up a little. I don't think RawRead should really be an issue, though to be prudent it might be best to zero-out the MDB_val after each operation in which it is used (e.g. *txn.key = C.MDB_val{}).
Please go ahead and attempt this change. I am going to merge in #57 when I fix the travis-ci job. But otherwise I would like to see what happens when this change is made.
Worth noting though that at some point in the future I believe this optimization will be unnecessary. I think with the pointer passing restrictions introduced in go1.6 should allows pointer arguments to be considered as non-escaping. But I'm not sure when/if that is really going to happen.

An interesting side effect of the proposed change is that data races from concurrent Txn use (e.g. on a Readonly Txn) would be caught by the Go race detector. In the current implementation the only data races occur in C space, without write barriers, and are invisible to the race detector.

@lmb are you working on putting together a pull request for this? Have you been having any difficulty that I could help with?
My curiosity got the best of me and I quickly threw together something that works as a proof of concept. Indeed it looks like it is possible to benefit from the suggested change, especially during transactions with lots of accesses (e.g. a range scan). Turn on RawRead and you are flying, my friend (current benchmark shows %20 reduction in scan time).
After this is settled I definitely thing it will be worth revisiting the performance numbers using integer flags (#11).

Hi Bryan,
I was going to look into this today. Easter weekend got the best of me :)
Do you have your code on a branch somewhere? Happy to polish it up if that
needs doing.
Nice that this gives such a significant speed up!

Oh, of course. How rude of me. Weekends and holidays especially can fail to register with me. Forgive me, and don't worry about it.  It's is the sum of about 30 minutes of work so it is rough.
All transactions allocate two MDB_vals when they are created. I think there is at least one important thing that could be improved. Specifically, update transactions which will only issue Put commands do not need to allocate these MDB_vals (though PutReserve is special and requires one val), and the benchmarks in which this occur are slightly slower as I have written things.
It's also worth considering that transactions which are opened to Get exactly one key will not get any faster from this change (there is no chance to re-use the allocated MDB_vals).
So there is a balancing act that most be done here. I think you really just need to think it through a bit and potentially go through several permutations of ideas in the code. Let me know if you have any thoughts or questions.
Cheers.

No worries, I'll take a look. Which invocation do you use for benchmarks?
Re the single Get use case: in my opinion this will always be the worst
case, since you are incurring the allocation overhead for a tx every single
time (this includes acquiring a semaphore and writing to the lockfile).
While its important to not make this dog slow, anyone trying to seriously
use lmdb from Go has to batch operations anyways. Thoughts?
On 30 Mar 2016 8:23 am, "Bryan Matsuo"<EMAIL_ADDRESS>wrote:

Oh, of course. How rude of me. Weekends and holidays especially can fail
to register with me. Forgive me, and don't worry about it.  It's is the sum of
about 30 minutes of work so it is rough.
All transactions allocate two MDB_vals when they are created. I think
there is at least one important thing that could be improved. Specifically,
update transactions which will only issue Put commands do not need to
allocate these MDB_vals (though PutReserve is special and requires one
val), and the benchmarks in which this occur are slightly slower as I have
written things.
It's also worth considering that transactions which are opened to Get
exactly one key will not get any faster from this change (there is no
chance to re-use the allocated MDB_vals).
So there is a balancing act that most be done here. I think you really
just need to think it through a bit and potentially go through several
permutations of ideas in the code. Let me know if you have any thoughts or
questions.
Cheers.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/bmatsuo/lmdb-go/issues/59#issuecomment-203286655

When I run the benchmarks I use go test -run=None -bench=.. In this case adding the -benchmem flag may be good too.
You are mostly correct RE a single Get. Though I think it is actually probably quite common in reality. The overhead for any single-op transaction may outweigh allocation overhead.
This has got me thinking though, one thing I made no attempt to handle was subtransactions. It should actually be completely safe for subtractions to use their parent's MDB_val objects (parents must never be used while they have an active child). Subtransactions provide a batching mechanism for updates that is potentially quite useful for some applications. And it would be nice for them to benefit from reduced allocations.

Oh. And if you don't know about the benchcmp tool then you should be using that to compare benchmark results for different code versions. Just figured you should know if you didn't :)

I implemented you change, which gets rid of the allocation cost for subtransactions. Regarding slowing down Get, this is what I get when benchmarking the same code twice on my OS X box:
lorenz@antares ~/go/src/github.com/bmatsuo/lmdb-go (reuse-mdb-val)*
$ benchcmp new.txt new2.txt
benchmark                              old ns/op     new ns/op     delta
BenchmarkEnv_ReaderList-4              59673         58537         -1.90%
BenchmarkTxn_Put-4                     2073          2010          -3.04%
BenchmarkTxn_PutReserve-4              2805          1847          -34.15%
BenchmarkTxn_PutReserve_writemap-4     2101          1525          -27.42%
BenchmarkTxn_Put_writemap-4            2855          1632          -42.84%
BenchmarkTxn_Get_ro-4                  1423          1446          +1.62%
BenchmarkTxn_Get_raw_ro-4              1075          855           -20.47%
BenchmarkScan_ro-4                     7488830       5804052       -22.50%
BenchmarkScan_raw_ro-4                 1710047       1299006       -24.04%
BenchmarkCursor-4                      1118          829           -25.85%
BenchmarkCursor_Renew-4                198           196           -1.01%
BenchmarkTxn_Sub_commit-4              293740        149557        -49.09%
BenchmarkTxn_Sub_abort-4               281365        145835        -48.17%
BenchmarkTxn_abort-4                   19417         16261         -16.25%
BenchmarkTxn_commit-4                  17269         16284         -5.70%
BenchmarkTxn_ro-4                      122001        124584        +2.12%
BenchmarkTxn_unmanaged_abort-4         16617         16634         +0.10%
BenchmarkTxn_unmanaged_commit-4        16623         16808         +1.11%
BenchmarkTxn_unmanaged_ro-4            113743        120440        +5.89%
BenchmarkTxn_renew-4                   620           575           -7.26%
BenchmarkTxn_Put_append-4              789           808           +2.41%
BenchmarkTxn_Put_append_noflag-4       1013          1021          +0.79%

benchmark                              old allocs     new allocs     delta
BenchmarkEnv_ReaderList-4              113            113            +0.00%
BenchmarkTxn_Put-4                     4              4              +0.00%
BenchmarkTxn_PutReserve-4              2              2              +0.00%
BenchmarkTxn_PutReserve_writemap-4     2              2              +0.00%
BenchmarkTxn_Put_writemap-4            4              4              +0.00%
BenchmarkTxn_Get_ro-4                  3              3              +0.00%
BenchmarkTxn_Get_raw_ro-4              3              2              -33.33%
BenchmarkScan_ro-4                     8152           8127           -0.31%
BenchmarkScan_raw_ro-4                 5              5              +0.00%
BenchmarkCursor-4                      3              3              +0.00%
BenchmarkCursor_Renew-4                0              0              +0.00%
BenchmarkTxn_Sub_commit-4              3              3              +0.00%
BenchmarkTxn_Sub_abort-4               3              3              +0.00%
BenchmarkTxn_abort-4                   5              5              +0.00%
BenchmarkTxn_commit-4                  5              5              +0.00%
BenchmarkTxn_ro-4                      5              5              +0.00%
BenchmarkTxn_unmanaged_abort-4         5              5              +0.00%
BenchmarkTxn_unmanaged_commit-4        5              5              +0.00%
BenchmarkTxn_unmanaged_ro-4            5              5              +0.00%
BenchmarkTxn_renew-4                   0              0              +0.00%
BenchmarkTxn_Put_append-4              5              5              +0.00%
BenchmarkTxn_Put_append_noflag-4       5              5              +0.00%

benchmark                              old bytes     new bytes     delta
BenchmarkEnv_ReaderList-4              7408          7408          +0.00%
BenchmarkTxn_Put-4                     96            96            +0.00%
BenchmarkTxn_PutReserve-4              48            48            +0.00%
BenchmarkTxn_PutReserve_writemap-4     48            48            +0.00%
BenchmarkTxn_Put_writemap-4            96            96            +0.00%
BenchmarkTxn_Get_ro-4                  1149          1158          +0.78%
BenchmarkTxn_Get_raw_ro-4              66            65            -1.52%
BenchmarkScan_ro-4                     9106023       9202313       +1.06%
BenchmarkScan_raw_ro-4                 72            72            +0.00%
BenchmarkCursor-4                      33            33            +0.00%
BenchmarkCursor_Renew-4                0             0             +0.00%
BenchmarkTxn_Sub_commit-4              65            65            +0.00%
BenchmarkTxn_Sub_abort-4               65            65            +0.00%
BenchmarkTxn_abort-4                   97            97            +0.00%
BenchmarkTxn_commit-4                  97            97            +0.00%
BenchmarkTxn_ro-4                      97            97            +0.00%
BenchmarkTxn_unmanaged_abort-4         97            97            +0.00%
BenchmarkTxn_unmanaged_commit-4        97            97            +0.00%
BenchmarkTxn_unmanaged_ro-4            97            97            +0.00%
BenchmarkTxn_renew-4                   0             0             +0.00%
BenchmarkTxn_Put_append-4              104           104           +0.00%
BenchmarkTxn_Put_append_noflag-4       104           104           +0.00%

Seems like the timing info is very unreliable.

I also looked at reducing the number of allocations done in a Put, but no such luck. Do you know why there are 4 allocations happening? I would expect 2 allocations maybe, for the two unsafe.Pointer coversions.

I believe that the unexpected allocations you see are happening in the BenchmarkTxn_Put function itself (in bench_test.go). That is unfortunate throws the numbers off.
It always good to verify tests still pass :smile:  But indeed the timing is pretty erratic. And this doesn't seem too different from what I would expect. As long as relevant benchmarks go down that is good. But you typically do see weird spikes on unrelated bits. Like this,
BenchmarkCursor-4                      1118          829           -25.85%

No idea why that should be ~300ns faster now.
But you also see a similar reduction in scan time. That is good.
As a general word of caution though, it can be good to take a look at the benchmark to know what is really being timed. Some things may not work as you expect them to (also evidenced from you question about Put allocations).
In the case of BenchmarkScan_raw_ro, transaction initialization and cleanup is not being counted. It is worth knowing.

Also out of curiosity, what os/arch are you testing on? And are you in a VM?

OS X 10.11.4, x86_64, with the kernel pprof fix applied. How do you want to proceed with this? I can create a PR, but frankly you've done the work. I just added 4 lines for the subtxn case.
I did look at the Put benchmark:
(pprof) list lmdb.BenchmarkTxn_Put.func1
Total: 506370
ROUTINE ======================== github.com/bmatsuo/lmdb-go/lmdb.BenchmarkTxn_Put.func1 in /Users/lorenz/go/src/github.com/bmatsuo/lmdb-go/lmdb/bench_test.go
         0     440425 (flat, cum) 86.98% of Total
         .          .     77:	err = env.Update(func(txn *Txn) (err error) {
         .          .     78:		b.ResetTimer()
         .          .     79:		defer b.StopTimer()
         .          .     80:		for i := 0; i < b.N; i++ {
         .          .     81:			k := ps[rand.Intn(len(ps)/2)*2]
         .         21     82:			v := makeBenchDBVal(&rc)
         .     440404     83:			err := txn.Put(dbi, k, v, 0)
         .          .     84:			if err != nil {
         .          .     85:				return err
         .          .     86:			}
         .          .     87:		}
         .          .     88:		return nil

If I'm interpreting b.ResetTimer() correctly, only the allocations on line 82 & 93 should be taken into account for the benchmem output. This means that something like 99% of the 4 allocations per Put are really allocated in Put?

I think you can go ahead and open a PR with subtxn stuff. The commit I made is tagged with name/email. I don't think there's an attribution issue or anything.
I'm confused about that pprof output. Is it a memprofile? I actually have never been able to make effective use of a memprofile output for some reason.

Yeah thats a memprofile output, with -alloc_objects passed to go tool pprof. It shows the number of allocations done per line.

Oh, interesting. Maybe that flag is what has been keeping -memprofile from being useful to me... Thanks for the info.
I think I understand what you meant in your comment now. But I don't think the interpretation makes sense given the data. If it is the correct interpretation then I suspect there is a bug in profiling related to cgo. Lets look at the following two lines.
         .         21     82:           v := makeBenchDBVal(&rc)
         .     440404     83:           err := txn.Put(dbi, k, v, 0)

So, makeBenchDBVal allocated 21 objects (not 21 bytes, 21 slices). And txn.Put allocated 20,000X more objects. But, because one call always follows the other that means that txn.Put allocated 20000 objects per iteration on average. But as we've seen the numbers say that the benchmark allocated 4 objects per iteration. So my conclusion has to be that somewhere an assumption of how the tools work is wrong or there is a bug in one of the tools.
The number of txn.Put isn't the sum of all calls to Txn.Put is it? It is the sum of calls for which lmdb.BenchmarkTxn_Put.func1 was directly below it in the stack (potentially even more granular that that). Right? If I'm wrong about that then I'm not sure what to take away from the snippet you have provided :confused:

Oh. I think pprof may be counting allocations using malloc in C as well. If you look at the numbers using -alloc_space you see the size allocated in txn.Put is ~98MB. This may be approximately equal to the total amount of data in the  database at the end of the benchmark.

The confusing bit is that the output from go test only includes allocations between ResetTimer and StopTimer, but the memprofile includes all allocations.
I removed the makeBenchDBVal call from the benchmark loop, and go test still reports 4 allocations per op. Looking at the memory profile shows that all allocations happen at txn.Put. The numbers for txn.Put (in BenchmarkTxn_Put.func1) do not match up with Txn.Put since we populate the DB prior to running the benchmark.
 So you made a change which should have reduced the number of allocs/op as reported by the benchmark output, and the number of allocs/op did not change? This sounds like a bug in "testing" package, then. No?

This should probably be in a separate issue regardless.

I created #63 for this issue


ModuleNotFoundError: No module named 'Aidlab.Signal'

Dear,
While practicing "basic-sleep-detector.py" from https://www.aidlab.com/blog/basic-sleep-detector-in-python, I received de following error:
ModuleNotFoundError: No module named 'Aidlab.Signal'
Could you please check this?

This has been corrected in version 1.3.24


Add selfish staker profile

PR description
Add selfish staker profile
Use
besu --profile=selfishstaker
Fixed Issue(s)
fixes https://github.com/hyperledger/besu/issues/6324

@non-fungible-nelson maybe we should come up with a better name for this profile


int 0x80 doesn't work

Attempting to use the int 0x80 system call interface, which is present even in 64-bit mode, results in the program getting killed or similar.

This is a known limitation of WSL in that we don't support 32-bit applications. Given most applications are 64-bit, this has not surfaced to the top of the priority list.

This is like an x86-64 Linux kernel with CONFIG_IA32_EMULATION disabled.  Some Linux distros build their standard kernels this way, so even on real Linux you shouldn't depend on being able to use it from 64-bit user-space.  (Or at least it's not unusual to find Gentoo systems configured that way.)
Linux does officially support using int 0x80 from 64-bit user-space if it's enabled, but it's not recommended and rarely useful for anything.  See What happens if you use the 32-bit int 0x80 Linux ABI in 64-bit code?.  The biggest limitation is that you can't use 64-bit pointers, for example push "test" / mov rcx, rsp / ... / int 0x80 will return -EFAULT instead of printing a string from the stack, because ecx isn't a valid pointer for 32-bit sys_write.
AFAIK, the only real use-case for int 0x80 in 64-bit user-space is doing weird and crazy things with segment registers, like maybe doing a far-jump to a 32-bit code segment, where the syscall return path might set your segment registers back to fixed values instead of restoring the values from the entry point.


Fix apply - Cleanup of bolt_catalog output

On Windows, bolt_catalog starts its outputs with unwanted warnings about encoding issues.
This Pull request fixes https://github.com/puppetlabs/bolt/issues/2403

Wrong target


Clean up IAM V1 terraform and other infrastructure

Drop the version tags from our terraform files and clean up any associated IAM V1 tf data (should we visit acceptance environments as part of this card?):

https://github.com/chef/automate/blob/master/terraform/test-environments/scenarios/single_local_iamv2p1_fresh_install.tf
https://github.com/chef/automate/blob/master/terraform/test-environments/scenarios/single_local_iamv2p1_inplace_upgrade.tf

I think at this point we can drop all the "iam" specific envs