Bundle maintenance

HI,
I really like your bundle and have some ideas how to improve it.

fix coding standards,
allow service calls before and after fixtures file is loaded (not after object is persisted)
normalize tests,
add other loaders (maybe XML?)
add configuration option to fixtures file to define which fixtures should be loaded before... (order by filenames is very hard to maintain when there a lot of fixtures).

So, consider this issue as discussion (i couldn't find your email). If you agree I can start to implement them.

I think it would be a better idea to slpit this issue in several so we can track the advancement of them :

CS : https://github.com/khepin/KhepinYamlFixturesBundle/issues/55


Suggest to use C++ attribute instead of compiler extension attributes for forceinline stuffs

#if __has_cpp_attribute(gnu::always_inline)
[[gnu::always_inline]]
#elif __has_cpp_attribute(msvc::forceinline)
[[msvc::forceinline]]
#endif
inline

inline keyword has nothing to do with inlining in C++. It means mr. compiler please do not violate ODR.

This sounds reasonable, but I think the benefit is marginal. Of course everyone (including me) hates macros, but current usages of macros has little possibility to cause any problem (I believe), and also it does not leak outside the header file. So I think this change just unnecessarily makes the code more verbose.

This sounds reasonable, but I think the benefit is marginal. Of course everyone (including me) hates macros, but current usages of macros has little possibility to cause any problem (I believe), and also it does not leak outside the header file. So I think this change just unnecessarily makes the code more verbose.


Test Checklist for Atom plugins NuclideReason and language-reason

Overview: There are three separate Atom plugins for Reason. Not to worry, the user will only deal with one at the end of the day. Two of the three are the actual plugins (syntax highlighting plugin language-reason, and the actual IDE integration plugin NuclideReason). The third, atom-reason is the plugin users install and merely syncs the other two with opam.

language-reason: Syntax highlighting plugin (automatically installed)
NuclideReason: Actual IDE/formatting/Merlin integration (automatically installed)
atom-reason: This is the plugin that users actually install. Users don't need to know that the first two exist. Users merely install this one plugin, which will install the other two behind the scenes from the current opam installation of Reason. The reason we do it this way, is that the IDE features are tightly coupled to the features of the Reason syntax. We never want them to get out of sync. The user will install atom-reason, and that's it - the IDE is kept up to date based on what you have installed in opam. atom-reason lets them know if there's a new version of the plugin in opam to install.
In order for atom-reason to detect that it needs to install new versions of plugins in from the opam Reason installation, we need the two other plugins NuclideReason/language-reason to bump their versions every time a major feature is pushed to them. How can we ensure that we always bump the version?
What are the main test workflows we need to perform every time we upgrade either Reason or the editor plugins? I'll list test cases below as I think of them:

Test cases:

You have an existing, older version of the plugins installed, but you upgrade your installation of Reason. The plugins should automatically resync, or at least detect what you need to do to resync them easily.
You update Reason to a new version, and that new version of Reason has a new added dependency (npm install/update should be executed).
Test with Nuclide installed. Test with Nuclide not installed.
Test with bleeding edge beta of Atom. Test with stable Atom. Test with internal distribution of Atom.
We have a new installer plugin called atom-reason which installs the other two plugins from opam. There's a special field in NuclideReason and language-reason called messagesToInstaller that "sends messages" to the installer. This is so that in case we need to push an update to the two plugins and that in someway needs the auto-installer to update, we can tell the user of the auto-installer "hey, you need to update the auto-installer itself". Otherwise we'd get strange errors. Part of the test plan is to ensure that we can still "send messages" to atom-reason (the auto-installer plugin).
In atom-reason, the check box for "Automatically keep plugins in sync with OPAM installation" should be honored.

Stale

Eeeh let's keep it open because the idea's still great


Can you cause the Frame-Generation feature of FSR 3 to affect the GUI's icons, too?

The frame-generation feature functions perfectly for me, because it could boost 30 FPS to 60. It's extremely smooth, but the icons that move, like the red quest marker, and the chatboxes above characters, still are rendered with 30 FPS, so the beautifully smooth game is ruined by the stuttering icons while turning the camera. I know FSR3 is specifically designed to NOT affect the GUI, but could you force it to?

Yes, this would be super nice. The icons on the HUD jittering like that is really irritating.

up

Another thing you can notice is that the "transparency" effect of the UI uses the native frame as source, not the frame gen frames. This is most noticeable when you have quick travel prompt (e.g. after a sidequest) and move your camera around quickly while the native FPS is low. It will practically look like it's tearing underneat the UI.
I personally decided to combine FSR quality combined with framegen. It bumps the native FPS enough that the UI runs decently smooth. (though i don't like the amount of smearing that FSR quality produces in cutscenes...)


Offline Sideloading

Ran into an issue with offline sideloading.  It doesn't appear that the annotation extension framework can find sprites on the offline map, and I see error messages for the sprite lookup in the console...
Task <B9DFFF00-5671-4E15-BCAA-6298DF3432F6>.<160> finished with error [-1009] Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo={NSUnderlyingError=0x282f69110 {Error Domain=kCFErrorDomainCFNetwork Code=-1009 "(null)" UserInfo={_kCFStreamErrorCodeKey=50, _kCFStreamErrorDomainKey=1}}<EMAIL_ADDRESS>
Tried explicitly adding the image to the style like so, without any luck...
func mapView(_ mapView: MGLMapView, didFinishLoading style: MGLStyle) {
     if let image = UIImage(named: "aircraft-image") {
          style.setImage(image, forName: "aircraft")
     }

For grins, I tried the same process by adding as a layer rather than using the annotation-extension framework.  Layer was able to find the sprite in the offline map no problem.  Any thoughts?

Turns out, this is a larger issue related to MGLSymbolLayers and offline sideloading... https://github.com/mapbox/mapbox-gl-native-ios/issues/216


Test and evaluate the quality of response after ingestion of stackoverflow APIs

After ingestion using stackoverflow APIs we need to run the same test plan again and evaluate the results.
Depends on: #126

This has to be separate

verified this I do not see any regression
Results


Android Build Fails on OSX 10.13.1

io:~ i$ sudo weex build android
Last login: Thu Nov 23 14:40:57 on ttys005
/Users/i/Apps/iic/weex-cool/cool/start ; exit;
io:~ i$ /Users/i/Apps/iic/weex-cool/cool/start ; exit;
*****************************************************************************
*                             Welcome to Weex                               *
*                                                                           *
*             A framework for building Mobile cross-platform UI.            *
*                                                                           *
*                      https://github.com/alibaba/weex                      *
*****************************************************************************
~/Apps/iic/weex-cool/cool ~

><EMAIL_ADDRESS>serve /Users/i/Apps/iic/weex-cool/cool
> webpack-dev-server --config webpack.dev.js --watch --open

server is running! Please open http://<IP_ADDRESS>:8080/
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE <IP_ADDRESS>:8081
    at Object.exports._errnoException (util.js:1022:11)
    at exports._exceptionWithHostPort (util.js:1045:20)
    at Server._listen2 (net.js:1262:14)
    at listen (net.js:1298:10)
    at doListening (net.js:1397:7)
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
    at Module.runMain (module.js:607:11)
    at run (bootstrap_node.js:420:7)
    at startup (bootstrap_node.js:139:9)
    at bootstrap_node.js:535:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>serve: `webpack-dev-server --config webpack.dev.js --watch --open`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>serve script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
~
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

同上

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


[release-1.16] Run update_deps.sh

Please provide a description of this PR:
Ran update_deps.sh

@ericvn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio_release-1.16
b5b1ab121aa00df5130a79abb2de48295c2db953
link
true
/test release-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/test release-test

@ericvn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio_release-1.16
b5b1ab121aa00df5130a79abb2de48295c2db953
link
true
/test release-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


feat(git_push_test.go): add git push interrupt test

Still some TODOs to address that I can move forward with if it sounds like this will still be wanted after Still need to align with work done in https://github.com/deis/workflow-e2e/pull/235
Adds spec for https://github.com/deis/builder/pull/369
cc @mboersma

OK to test


Why are the leaderboards empty?

Check https://intercode-benchmark.github.io/#ctf and https://intercode-benchmark.github.io/#swe

Afaik, no one has submitted to these leaderboards.
I'll probably deprecate the SWE one soon. The idea behind that has taken on a life of its own in the form of the SWE-bench + SWE-agent projects.


Normalized cache viewer does not work with incubating cache

We've started using the incubating cache for Relay-style pagination as described here. It's working beautifully 🙌  however the normalized cache viewer in the Android Studio plugin no longer works. We see the following when attempting to pull from device:

Thanks for reporting! I'll have a look.

The fix is merged and will be in the next release.


eza: 0.10.9 -> 0.11.0

Description of changes

Bumped to v0.11.0
Added changelog
Added lib.platforms.windows

Changelog: https://github.com/eza-community/eza/releases/tag/v0.11.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 253216 run on x86_64-linux 1

2 packages built:

eza
eza.man


deps: fake the old bench-utils structure to avoid pulling in ark-std 0.3.0

When I followed the upstream refactoring earlier, it induced a dependency on the newer ark-std, causing our downstream code (like the Plumo prover) to transitively depend on it as well.
Tested
Builds, tests pass, and there is no ark 0.3.x in the dependency tree anymore.
Related issues
This is part of the fix for the plumo prover build https://github.com/gtank/plumo-prover/commit/a8abea11bea6e43824ed6c74e89575b33baab9f5

Followup thought: should we specify revs for each of the old ark dependencies or continue to rely on the lockfile?


Checnge the timing for lessons git intro on the schedule

As undoing changes introduce need to change the timing somewhat

This issue is super old. If timing is still an issue. Please reopen,


[Python] Remove deprecated APIs

Remove APIs that have been deprecated for long enough.
This probably includes the old filesystem layer as well as the custom serialization layer.
Reporter: Antoine Pitrou / @pitrou
Subtasks:

[x] [Python] Remove deprecated pyarrow.serialization functionality
[x] [Python] Remove the deprecated pyarrow.filesystem legacy implementations
[X] [Python] Remove deprecated APIs from <= 1.0.0
[X] [Python] Remove remaining deprecated APIs from <= 1.0.0

Note: This issue was originally created as ARROW-13555. Please see the migration documentation for further details.

Closing this issue as all subtasks are completed.


Revert "NIFI-6530 - HTTP SiteToSite server returns 201 in case no dat…

…a is available"
This reverts commit f01668e66ad2e45197915769e966a4be27e1592e.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

am watching this

We'll want to update the commit message to reference NIFI-7200 as well.  Will do when time to merge


TypeError: Cannot read properties of undefined (reading 'vertical')

TypeError: Cannot read properties of undefined (reading 'vertical')
at StoryProvider (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:201:101138)
at https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at SnackbarProvider (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:262:29113)
at https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at HistoryProvider (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:2690233)
at https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at Media3pApiProvider (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:238:9786)
at https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at FileProvider (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:246:68345)
at https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at APIProvider (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:213:3094)
at https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:236:3021012
at ConfigProvider (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:201:113084)
at _ (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:5:25443)
at Fe (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:1:32060)
at ce (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:1:29079)
at FlagsProvider (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:213:3908)
at StoryEditor (https://saralhistory.com/wp-content/plugins/web-stories/assets/js/wp-story-editor.js?ver=5a042ce20663b9f38756c841ab41c17a:5:46918)

@manojrao001 All support for the Web Stories plugin is provided on our WordPress.org support forum. If you create a new topic there, we'd be happy to take a look and help you troubleshoot. Thanks!


Test

Linter check found the following problems:
Skipping unknown check missing_doc_source_url
Skipping unknown check missing_license_url
Skipping unknown check missing_doc_source_url
Skipping unknown check missing_license_url
Skipping unknown check missing_doc_source_url
Skipping unknown check missing_license_url
Skipping unknown check missing_doc_source_url
Skipping unknown check missing_license_url
Skipping unknown check missing_doc_source_url
Skipping unknown check missing_license_url
Skipping unknown check missing_doc_source_url
Skipping unknown check missing_license_url
Skipping unknown check missing_doc_source_url
Skipping unknown check missing_license_url
The following problems have been found:
ERROR: build.sh:27: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found


[RFC] Avoiding the wrong window size at the moment of opening popup

How do you envision this feature/change to look/work like?

I know that the way to run react is through the js to generate html, but the moment you open the popup, due to the js has not been loaded, resulting in the html is not rendered, there will be a very small window, rather affect the experience, is there any way to change this?
What is the purpose of this change/feature? Why?
Improve the user experience
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contribution

[ ] I would like to contribute to this RFC via a PR

Verify canary release

[X] I verified that the issue exists in plasmo canary release

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

I'm using a not-so-good solution to solve this
editing build/popup.html and adding width and height to the body, but I think the framework should add this feature to initialize the size of popups


GraphQL aliased subqueries with different parameters return identical results

Description:
When I execute a query with aliased subqueries that have different parameters, the results returned are identical. This behavior is unexpected, as the subqueries should return distinct values based on the provided parameters.
Implementation
const AccountValuesFilter = builder.prismaWhere("Value", {
  fields: (t) => ({
    date: builder.prismaFilter("Date", {
      ops: ["gte", "lte", "equals"],
    });
  })
});

export const Account = builder.prismaNode("Account", {
  name: "Property",
  id: { field: "id" },
  values: t.relatedConnection("values", {
    cursor: "id",
    totalCount: true,
    defaultSize: 10000,
    args: {
      date: t.arg({ type: AccountValuesFilter }),
    },
    query: (args) => {
      console.log("-> args", args);
      return {
        where: args.filter ?? {}
      };
    },
  })
});

The query looks like the following:
{
  account(id: "1") {
    currentValues: values(filter: { date: { equals: { "2022-01-01" } } }) {
      edges {
        node {
          date
          value
        }
      }
    }
    previousValues: values(filter: { date: { equals: "2021-01-01" } } }) {
      edges {
        node {
          date
          value
        }
      }
    }
  }
}

Here's the results:
{
  "data": {
    "account": {
      "currentValues": {
        "edges": [
          {
            "node": {
              "date": "2021-07-01",
              "value": 68551864.7
            }
          }
        ]
      },
      "previousValues": {
        "edges": [
          {
            "node": {
              "date": "2021-07-01",
              "value": 68551864.7
            }
          }
        ]
      }
    }
  }
}

Notice that both currentValues and previousValues have the same date value, even though I'm filtering by different dates. I logged the args value and it seems that the issues happens after query().
-> args {
  date: 2022-07-01T00:00:00.000Z
}
-> args {
  date: 2021-07-01T00:00:00.000Z
}

Expected Behavior:
The aliased subqueries with different parameters should return distinct results based on the provided parameters.
Actual Behavior:
The aliased subqueries with different parameters return identical results, suggesting that the library might be reusing the parameters from the first subquery.
Library Version:
Pothos Core 3.33.0
"@pothos/core": "3.33.0",
"@pothos/plugin-add-graphql": "3.1.1",
"@pothos/plugin-errors": "3.11.1",
"@pothos/plugin-prisma": "3.57.0",
"@pothos/plugin-prisma-utils": "0.11.0",
"@pothos/plugin-relay": "3.43.1",
"@pothos/plugin-simple-objects": "3.7.0",
"@pothos/plugin-tracing": "0.5.8",
"@pothos/plugin-validation": "3.10.0",
"@prisma/client": "5.2.0"
"prisma": "5.2.0"

Additional Information:
This issue happens not only with relatedConnection, but also with field with select and args attributes defined.
// ...
score: t.float({
  nullable: true,
  args: t.arg({ type: "Date" }),
  select: args => {
    scores: {
      select: {
        value: true,
      },
      where: { date: args.date },
      take: 1,
    },
  },
  resolve: ({ ids }) => ids?.[0].value ?? null
}),

I just noticed that it works it the args isn't deeply nested. for instance, if I introduce another arg like orderBy and pass in a different value, the query works as expected.
{
  account(id: "1") {
    currentValues: values(orderBy: { date: Asc }, filter: { date: { equals: { "2022-01-01" } } }) {
      edges {
        node {
          date
          value
        }
      }
    }
    previousValues: values(orderBy: { date: Desc }, filter: { date: { equals: "2021-01-01" } } }) {
      edges {
        node {
          date
          value
        }
      }
    }
  }
}

So my guess is that it does a shallow comparison. make sense?

hey, thanks for the report.  Unfortunately I haven't been able to reproduce the issue.
I created a repo with a minimal reproduction based on your description, but it doesn't cause the same issue, any chance you could see if you can modify the example to more accurately reproduce the issue you are running into?
Here is my attempted reproduction: https://github.com/hayes/pothos-prisma-alias-bug

Awesome, thanks! I've just created a PR there!

should be fixed now! Definitely an interesting bug, thanks for helping to track this down


nix: patchShebangs tests for bootstrapping from older versions

Without this, building a newer nix (2.15) on an older nix (2.3) with sandboxing enabled will fail, which is problematic for doing a self-contained update on an older system.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Why does it fail

When building -A nix via nix 2.3 on 21b3094ca2de8906aa19f83c855959988e9b12e4, the error looks like this:
ran test tests/ca/substitute.sh... [FAIL]
    ++++(/build/source/tests/common/vars-and-functions.sh:274) trap onError ERR
    +++(../common.sh:8) [[ -n '' ]]
    ++(common.sh:3) enableFeatures ca-derivations
    ++(/build/source/tests/common/vars-and-functions.sh:230) local features=ca-derivations
    ++(/build/source/tests/common/vars-and-functions.sh:231) sed -i 's/experimental-features .*/& ca-derivations/' /build/nix-test/tests/ca/substitute/etc/nix.conf
    ++(common.sh:5) restartDaemon
    ++(/build/source/tests/common/vars-and-functions.sh:138) [[ -z '' ]]
    ++(/build/source/tests/common/vars-and-functions.sh:138) return 0
    +(substitute.sh:7) needLocalStore '“--no-require-sigs” can’t be used with the daemon'
    +(/build/source/tests/common/vars-and-functions.sh:219) [[ '' == \d\a\e\m\o\n ]]
    +(substitute.sh:9) rm -rf /build/nix-test/tests/ca/substitute/binary_cache
    +(substitute.sh:11) export REMOTE_STORE_DIR=/build/nix-test/tests/ca/substitute/binary_cache
    +(substitute.sh:11) REMOTE_STORE_DIR=/build/nix-test/tests/ca/substitute/binary_cache
    +(substitute.sh:12) export REMOTE_STORE=file:///build/nix-test/tests/ca/substitute/binary_cache
    +(substitute.sh:12) REMOTE_STORE=file:///build/nix-test/tests/ca/substitute/binary_cache
    +(substitute.sh:19) clearStore
    +(/build/source/tests/common/vars-and-functions.sh:74) echo 'clearing store...'
    clearing store...
    +(/build/source/tests/common/vars-and-functions.sh:75) chmod -R +w /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:76) rm -rf /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:77) mkdir /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:78) rm -rf /build/nix-test/tests/ca/substitute/var/nix
    +(/build/source/tests/common/vars-and-functions.sh:79) mkdir /build/nix-test/tests/ca/substitute/var/nix
    +(/build/source/tests/common/vars-and-functions.sh:80) clearProfiles
    +(/build/source/tests/common/vars-and-functions.sh:69) profiles=/build/nix-test/tests/ca/substitute/test-home/.local/state/nix/profiles
    +(/build/source/tests/common/vars-and-functions.sh:70) rm -rf /build/nix-test/tests/ca/substitute/test-home/.local/state/nix/profiles
    +(substitute.sh:20) nix copy --to file:///build/nix-test/tests/ca/substitute/binary_cache --file ./content-addressed.nix
    warning: you don't have Internet access; disabling some network-dependent features
    these 7 derivations will be built:
      /build/nix-test/tests/ca/substitute/store/5ij4pc9x6hafh35zb0lfvdfr142dqd1k-simple-input-addressed.drv
      /build/nix-test/tests/ca/substitute/store/9hdnchxn0qd08671ld2dq3nxdb9jvf80-rootCA.drv
      /build/nix-test/tests/ca/substitute/store/xlyjw5k36dkz4a06qsbg8qvvwcasw7yv-dependent.drv
      /build/nix-test/tests/ca/substitute/store/b1n5cknf76m68b3wk5lkycayf1a0z5lj-dependent-fixed-output.drv
      /build/nix-test/tests/ca/substitute/store/cl3j77wq9r3mazp0h6fr6fb20c491kly-transitively-dependent.drv
      /build/nix-test/tests/ca/substitute/store/v1y33skffczjalqdl37qp5gmwrmh0jcb-dependent-non-ca.drv
      /build/nix-test/tests/ca/substitute/store/zzj2q12i6mhcla645g7qgrn50ypf17vs-runnable-thing.drv
    building '/build/nix-test/tests/ca/substitute/store/5ij4pc9x6hafh35zb0lfvdfr142dqd1k-simple-input-addressed.drv'...
    building '/build/nix-test/tests/ca/substitute/store/272sjfm68kpv7wvcfl3k5c676rdgwhwm-rootCA.drv'...
    building '/build/nix-test/tests/ca/substitute/store/ippsy51k6y49gzml56xz8arj4cgbw1w1-dependent-non-ca.drv'...
    building '/build/nix-test/tests/ca/substitute/store/50c5ssa92978jpn2d4ivrybq5xs8g2h2-dependent.drv'...
    building '/build/nix-test/tests/ca/substitute/store/2s5jwgpl9ay20bva6kqhigwsr5crhvch-runnable-thing.drv'...
    building '/build/nix-test/tests/ca/substitute/store/mx4izwcknc113ki1cvh903s0f1p9zhi3-dependent-fixed-output.drv'...
    building '/build/nix-test/tests/ca/substitute/store/6xdz6jfp3b2p54dh9sn1kyn7j29djqcq-transitively-dependent.drv'...
    copying 9 paths...
    copying path '/build/nix-test/tests/ca/substitute/store/3vxm659ffkp26lij9s611nxh490zdwsp-dependent-fixed-output' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/xf6l51diijwn41biq6smhvvgzxw47k7x-simple-input-addressed' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/9mmvwhxf5hzc4xk04vyzgmk2qvsgd57p-runnable-thing' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/p47vs5ka8w3sildrynvz2myyqlkiymdy-rootCA' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/14f4vgcwyibbz9qnckp6g6bfbbd3y10p-rootCA-foo' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/ypkzca05ab09mj7jlddjvsj6zbmxzm3r-rootCA-dev' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/10dx3bxpb716ajq54rbd30dzs629h2b5-dependent-non-ca' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/vqypk04lb0yxf1j4yx5d7z6zf954mmdi-dependent' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/iqrvx8i366z4iyh5wfvwjvagn7fg0djj-transitively-dependent' to 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    +(substitute.sh:23) clearStore
    +(/build/source/tests/common/vars-and-functions.sh:74) echo 'clearing store...'
    clearing store...
    +(/build/source/tests/common/vars-and-functions.sh:75) chmod -R +w /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:76) rm -rf /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:77) mkdir /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:78) rm -rf /build/nix-test/tests/ca/substitute/var/nix
    +(/build/source/tests/common/vars-and-functions.sh:79) mkdir /build/nix-test/tests/ca/substitute/var/nix
    +(/build/source/tests/common/vars-and-functions.sh:80) clearProfiles
    +(/build/source/tests/common/vars-and-functions.sh:69) profiles=/build/nix-test/tests/ca/substitute/test-home/.local/state/nix/profiles
    +(/build/source/tests/common/vars-and-functions.sh:70) rm -rf /build/nix-test/tests/ca/substitute/test-home/.local/state/nix/profiles
    +(substitute.sh:24) buildDrvs --substitute --substituters file:///build/nix-test/tests/ca/substitute/binary_cache --no-require-sigs -j0 transitivelyDependentCA
    +(substitute.sh:15) nix build --file ./content-addressed.nix -L --no-link --substitute --substituters file:///build/nix-test/tests/ca/substitute/binary_cache --no-require-sigs -j0 transitivelyDependentCA
    warning: you don't have Internet access; disabling some network-dependent features
    these 3 derivations will be built:
      /build/nix-test/tests/ca/substitute/store/9hdnchxn0qd08671ld2dq3nxdb9jvf80-rootCA.drv
      /build/nix-test/tests/ca/substitute/store/xlyjw5k36dkz4a06qsbg8qvvwcasw7yv-dependent.drv
      /build/nix-test/tests/ca/substitute/store/cl3j77wq9r3mazp0h6fr6fb20c491kly-transitively-dependent.drv
    this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
      /build/nix-test/tests/ca/substitute/store/xf6l51diijwn41biq6smhvvgzxw47k7x-simple-input-addressed
    copying path '/build/nix-test/tests/ca/substitute/store/xf6l51diijwn41biq6smhvvgzxw47k7x-simple-input-addressed' from 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/p47vs5ka8w3sildrynvz2myyqlkiymdy-rootCA' from 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/vqypk04lb0yxf1j4yx5d7z6zf954mmdi-dependent' from 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    copying path '/build/nix-test/tests/ca/substitute/store/iqrvx8i366z4iyh5wfvwjvagn7fg0djj-transitively-dependent' from 'file:///build/nix-test/tests/ca/substitute/binary_cache'...
    +(substitute.sh:26) nix realisation info --file ./content-addressed.nix transitivelyDependentCA
    warning: you don't have Internet access; disabling some network-dependent features
    sha256:3e4163dea7e3bac8077836091aabe1c81dd14b8ba8d6690dcc8ccbaef5e94cd0!out /build/nix-test/tests/ca/substitute/store/iqrvx8i366z4iyh5wfvwjvagn7fg0djj-transitively-dependent
    +(substitute.sh:28) nix realisation info --file ./content-addressed.nix dependentCA
    warning: you don't have Internet access; disabling some network-dependent features
    sha256:880c5679eee6c9631c8010d4d108d6bab79366721ebc4403d044389ee49aea57!out /build/nix-test/tests/ca/substitute/store/vqypk04lb0yxf1j4yx5d7z6zf954mmdi-dependent
    +(substitute.sh:31) isDaemonNewer 2.13
    +(/build/source/tests/common/vars-and-functions.sh:149) [[ -n '' ]]
    +(/build/source/tests/common/vars-and-functions.sh:149) return 0
    +(substitute.sh:32) pushToStore=../push-to-store.sh
    +(substitute.sh:45) clearStore
    +(/build/source/tests/common/vars-and-functions.sh:74) echo 'clearing store...'
    clearing store...
    +(/build/source/tests/common/vars-and-functions.sh:75) chmod -R +w /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:76) rm -rf /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:77) mkdir /build/nix-test/tests/ca/substitute/store
    +(/build/source/tests/common/vars-and-functions.sh:78) rm -rf /build/nix-test/tests/ca/substitute/var/nix
    +(/build/source/tests/common/vars-and-functions.sh:79) mkdir /build/nix-test/tests/ca/substitute/var/nix
    +(/build/source/tests/common/vars-and-functions.sh:80) clearProfiles
    +(/build/source/tests/common/vars-and-functions.sh:69) profiles=/build/nix-test/tests/ca/substitute/test-home/.local/state/nix/profiles
    +(/build/source/tests/common/vars-and-functions.sh:70) rm -rf /build/nix-test/tests/ca/substitute/test-home/.local/state/nix/profiles
    +(substitute.sh:46) nix build --file ../simple.nix -L --no-link --post-build-hook ../push-to-store.sh
    warning: you don't have Internet access; disabling some network-dependent features
    this derivation will be built:
      /build/nix-test/tests/ca/substitute/store/2vbx9wjgss5a7nhrwaqqvwsj7m85z759-simple.drv
    building '/build/nix-test/tests/ca/substitute/store/2vbx9wjgss5a7nhrwaqqvwsj7m85z759-simple.drv'...
    simple> PATH=
    running post-build-hook '../push-to-store.sh'...
    simple (post)> ../push-to-store.sh: line 5: syntax error: bad substitution
    error: program '../push-to-store.sh' failed with exit code 2
    ++(substitute.sh:46) onError
    ++(/build/source/tests/common/vars-and-functions.sh:237) set +x
    substitute.sh: test failed at:
      main in substitute.sh:46
make: *** [mk/lib.mk:123: tests/ca/substitute.sh.test] Error 1

I suspect it is an impurity of some kind, because adding --keep-failed, going into the failed dir, sourcing environment, adding export TMPDIR=$(pwd), and running make installcheck by hand works. The script in question refers to /bin/sh, so I guess that it either does not exist is the sandbox on 2.3, or it is outdated/broken in some way there.

Yay, thanks!


[SPARK-40015][PYTHON] Add sc.listArchives and sc.listFiles to PySpark

What changes were proposed in this pull request?
Add sc.listArchives and sc.listFiles to PySpark
Why are the changes needed?
for function parity
Does this PR introduce any user-facing change?
yes, new APIs
How was this patch tested?
added doctests

Merged to master.

Thank you @HyukjinKwon !


bump: org-contrib

emacsmirror/org-contrib@0231706232f2 -> emacsmirror/org-contrib@e3183921779e
The previous commit seems to no longer exist upstream

I've bumped org-contrib as part of a larger bump in cc73c2f, which should resolve this issue. Thanks for bringing it to my attention!


Preserving type for 'flatten' methods

Based on this discussion: https://github.com/dart-lang/sdk/issues/40315, I added two more extensions to Iterable class.
The actual implementation has a method flatten that returns an Interable<dynamic>, wich loses type on returned Iterable.
Those two new extensions will help preserving the type for Lists and Iterables  :)
(tests included)

@shinayser please check if your problems would be solved when #56 lands.

Great job! I think it is really fine =)


毎週同じ番組のみエンコード失敗

録画終了時に以下のスクリプトを走らして
ジャンルごとに圧縮比率を変えてエンコードしているのですが、
毎週同じ番組のみエンコードが失敗します。
なぜなのでしょうか・・・。
スクリプト
#!/bin/sh
INPUT=$(echo $1)
chmod -v 777 "$1"
day=$(date +%Y_%m_%d_%H:%M:%S)
category=$(echo $2 | jq '.category' | sed -e 's/"//g')
title=$(echo $2 | jq '.title' | sed -e 's/"//g' | sed -e 's/()//g' | sed -e 's/（）//g' | sed -e 's/　/ /g')
episode=$(echo $2 | jq '.episode' | sed -e 's/"//g')
echo "${day}_${title}_EncodeStart" >> "/media/Server/video/log/_log_.txt"
case ${category} in
        "anime")
		title=$(echo "${title} #${episode}")
		title=$(echo ${title} | sed -e 's/水曜アニメ・水もん //g' | sed -e 's/アニメ //g' | sed -e 's/ #null//g')

                echo "${day} animeEnc" >> "/media/Server/video/log/${title}.txt"
                avconv -y -threads:v:3 -threads:a:1 -i "$1" \
                -preset:v slow -tune ssim -crf 20 \
                -profile:a aac_he -b:a 198k -afterburner 1 \
		"/media/Server/video/anime/${title}.mp4" 2>> "/media/Server/video/log/${title}.txt"
		rm $1
                ;;
        "drama")
                echo "${day} dramaEnc" >> "/media/Server/video/log/${title}.txt"
                avconv -y -threads:v:3 -threads:a:1 -i "$1" \
                -preset:v slow -tune ssim -crf 20 \
                -profile:a aac_he -b:a 128k -afterburner 1 \
		"/media/Server/video/drama/${title}.mp4" 2>> "/media/Server/video/log/${title}.txt"
		rm $1
		;;
        "cinema")
                echo "${day} cinemaEnc" >> "/media/Server/video/log/${title}.txt"
                avconv -y -threads:v:3 -threads:a:1 -i "$1" \
                -preset:v slow -tune ssim -crf 20 \
                -profile:a aac_he -b:a 128k -afterburner 1 \
                "/media/Server/video/cinema/${title}.mp4" 2>> "/media/Server/video/log/${title}.txt"
                rm $1
                ;;
esac

day=$(date +%Y_%m_%d_%H:%M:%S)
echo "${day} end" >> "/media/Server/video/log/${title}.txt"
echo "${day}_${title}_EncodeEnd" >> "/media/Server/video/log/_log_.txt"
exit

エンコード失敗時のログ
2015_05_24_02:27:53 animeEnc
avconv version 11.3, Copyright (c) 2000-2014 the Libav developers
  built on Apr  7 2015 21:14:39 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
[mpegts @ 0x1ea0a80] PES packet size mismatch
    Last message repeated 1 times
[NULL @ 0x1ecade0] start time is not set in estimate_timings_from_pts
[mpegts @ 0x1ea0a80] PES packet size mismatch
Input #0, mpegts, from '/media/Server/rec/2015_58_24_01:05_gr2064-2wy.m2ts':
  Duration: 00:29:56.60, start: 57428.665333, bitrate: 10767 kb/s
  Program 2064
  No Program
    Stream #0.0[0x112]: Data: [0][0][0][0] / 0x0000
    Stream #0.1[0x111]: Data: [0][0][0][0] / 0x0000
    Stream #0.2[0x115]: Data: [0][0][0][0] / 0x0000
    Stream #0.3[0x114]: Data: [0][0][0][0] / 0x0000
Codec AVOption threads () specified for input file #0 (/media/Server/rec/2015_58_24_01:05_gr2064-2wy.m2ts) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some decoder which was not actually used for any stream.
Codec AVOption preset (Set the encoding preset (cf. x264 --fullhelp)) specified for output file #0 (/media/Server/video/anime/終わりのセラフ #8.mp4) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
Codec AVOption tune (Tune the encoding params (cf. x264 --fullhelp)) specified for output file #0 (/media/Server/video/anime/終わりのセラフ #8.mp4) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
Codec AVOption crf (Select the quality for constant quality mode) specified for output file #0 (/media/Server/video/anime/終わりのセラフ #8.mp4) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
Codec AVOption profile (Set profile restrictions (cf. x264 --fullhelp) ) specified for output file #0 (/media/Server/video/anime/終わりのセラフ #8.mp4) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
Codec AVOption b (set bitrate (in bits/s)) specified for output file #0 (/media/Server/video/anime/終わりのセラフ #8.mp4) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
Codec AVOption afterburner (Afterburner (improved quality)) specified for output file #0 (/media/Server/video/anime/終わりのセラフ #8.mp4) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
Output #0, mp4, to '/media/Server/video/anime/終わりのセラフ #8.mp4':
Output file #0 does not contain any stream
2015_05_24_02:27:54 end

エンコード成功時のログ
2015_05_23_00:19:53 animeEnc
avconv version 11.3, Copyright (c) 2000-2014 the Libav developers
  built on Apr  7 2015 21:14:39 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
[mpeg2video @ 0x2690980] Invalid frame dimensions 0x0.
[aac @ 0x2691320] get_buffer() failed
[mpeg2video @ 0x2690980] Invalid frame dimensions 0x0.
    Last message repeated 9 times
[mpegts @ 0x268ca80] PES packet size mismatch
    Last message repeated 6 times
[NULL @ 0x2691c40] start time is not set in estimate_timings_from_pts
[NULL @ 0x2692560] start time is not set in estimate_timings_from_pts
[NULL @ 0x2692e80] start time is not set in estimate_timings_from_pts
[NULL @ 0x26937a0] start time is not set in estimate_timings_from_pts
[NULL @ 0x26940c0] start time is not set in estimate_timings_from_pts
[NULL @ 0x26949e0] start time is not set in estimate_timings_from_pts
[NULL @ 0x26ad520] start time is not set in estimate_timings_from_pts
[mpegts @ 0x268ca80] PES packet size mismatch
    Last message repeated 1 times
Input #0, mpegts, from '/media/Server/rec/2015_50_22_23:05_gr43056-a2.m2ts':
  Duration: 00:29:56.80, start: 83619.218922, bitrate: 12167 kb/s
  Program 43056
    Stream #0.0[0x100]: Video: mpeg2video (Main), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 24000 kb/s, 29.97 fps, 90k tbn, 59.94 tbc
    Stream #0.1[0x110]: Audio: aac, 48000 Hz, stereo, fltp, 305 kb/s
    Stream #0.2[0x138]: Data: [6][0][0][0] / 0x0006
    Stream #0.3[0x1440]: Data: [13][0][0][0] / 0x000D
    Stream #0.4[0x1450]: Data: [13][0][0][0] / 0x000D
    Stream #0.5[0x1457]: Data: [13][0][0][0] / 0x000D
    Stream #0.6[0x1458]: Data: [13][0][0][0] / 0x000D
    Stream #0.7[0x145e]: Data: [13][0][0][0] / 0x000D
    Stream #0.8[0x1460]: Data: [13][0][0][0] / 0x000D
Codec AVOption threads () specified for input file #0 (/media/Server/rec/2015_50_22_23:05_gr43056-a2.m2ts) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some decoder which was not actually used for any stream.
[libx264 @ 0x26b5740] using SAR=1/1
[libx264 @ 0x26b5740] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
[libx264 @ 0x26b5740] profile High, level 5.0
[libx264 @ 0x26b5740] 264 - core 146 r2 121396c - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=1 ref=5 deblock=1:0:0 analyse=0x3:0x113 me=umh subme=8 psy=0 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=2 b_bias=0 direct=3 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=50 rc=crf mbtree=1 crf=20.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=2:1.00
Output #0, mp4, to '/media/Server/video/anime/レーカン！ #8.mp4':
  Metadata:
    encoder         : Lavf56.1.0
    Stream #0.0: Video: libx264, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], q=-1--1, 29.97 fps, 30k tbn, 29.97 tbc
    Metadata:
      encoder         : Lavc56.1.0 libx264
    Stream #0.1: Audio: libfdk_aac (HE-AAC), 48000 Hz, stereo, s16, 198 kb/s
    Metadata:
      encoder         : Lavc56.1.0 libfdk_aac
Stream mapping:
  Stream #0:0 -> #0:0 (mpeg2video (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (aac (native) -> aac (libfdk_aac))
Press ctrl-c to stop encoding
[aac @ 0x26b9080] Number of bands (17) exceeds limit (14).
Error while decoding stream #0:1
[mpeg2video @ 0x26b8c80] warning: first frame is no keyframe
frame=   56 fps= 45 q=0.0 size=       0kB time=2.03 bitrate=   0.2kbits/s
frame=   69 fps= 28 q=26.0 size=     203kB time=0.53 bitrate=3108.7kbits/s
frame=   77 fps= 25 q=26.0 size=     275kB time=0.80 bitrate=2817.0kbits/s
frame=   90 fps= 25 q=26.0 size=     356kB time=1.23 bitrate=2362.0kbits/s
.
.
.

ここは libav / ffmpeg のサポートをするところでは無いのですが, 一つヒントを出すならば libav の代わりに ffmpeg を使用すると良いかもしれません

ffmpegでエンコードすれば失敗はなくなりました。
ありがとうございました。


Delete failures

Add possibility to delete a failure via the events api

Coverage increased (+0.003%) to 99.716% when pulling 94500d551834d9548390fefec3495ef024751fcb on delete-failures into 5bb157c15e508813ac5e575cd256c848c750f7f0 on master.

Coverage increased (+0.003%) to 99.72% when pulling 8c6c8137f00d58112d2e2cde2d4642b3f16e435c on delete-failures into<PHONE_NUMBER>9d2d0844e3e19d532d34710ead57fa on master.


Page out of date

Page is now incorrect. connector has attachement name and content fields now.

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

ID: efceafa2-4c75-9534-5826-8d6f13391c8b
Version Independent ID: 41bbd300-95aa-6eac-fa8a-dbc735c94102
Content: Power Automate - Send SharePoint files as attachments
Content Source: Community/power-automate-send-sharepoint-files-as-attachments.md
Service: power-platform
GitHub Login: @JimmyHang
Microsoft Alias: daisyfeller

@JimmyHang Is this something you'd like to look at?

@ResRudeBoy - Our apologies for not responding sooner. Thanks very much for the issue.
I just took a look at the Send an email (v2) action, and there are still two modes, depending on how you'd like to provide the attachment info.
Default:

Array input:

In this article, @JimmyHang has chosen to use the latter option because he wants to send an array of attachments he's built in prior actions.
I'm going to close this issue, but please let us know if you think I'm missing something by opening a new issue.


Getting TLS peer certificate

If I've made a TLS broker server along the lines of tls_server.cpp...
First, it appears that these examples are a bit outdated and only support v3 or v5 but not both (although they can be combined to support both).  And they appear to be missing support for some apparently necessary things (eg. #502 recommended adding pingreq handlers).
Is test_broker.cpp a better example to base a new broker on instead?
But anyway, the real question is: from an accept (or connect) handler (when I know that the underlying connection is a TLS stream), how do I get the peer client certificate?  My use case requires validating the MQTT CONNECT against information in that certificate.
I've combed through the Boost.Asio docs and as far as I can tell the only method is to call SSL_get_peer_certificate(sslstream.native_handle()) directly.  However I'm not sure how to get at the sslstream, given the server_tls<>::endpoint_t passed to the accept handler.
ep.socket() returns an mqtt::socket, but that's some kind of type-erased thing and not the underlying as::ssl::stream<as::ip::tcp::socket> (buried somewhere in mqtt::server_tls<>::socket_t), which is what I need to get at.

Mostly as an exercise, https://github.com/uecasm/mqtt_cpp/commit/3105c02 was an attempt to add native_handle to mqtt::socket.
It doesn't work (or compile).  I don't really know what I'm doing with Boost.TypeErasure -- in particular how to tell it that native_handle() returns T::native_handle_type (which is different types).  Or if that's even possible.  (The TypeErasure docs seemed to suggest that it might be, however.)

Thank you reporting the issue.
Do you want to do client certification authentication on server side?
I don't check the problem deeply but I guess that there are two possible approaches.
Both requires mqtt_cpp modify.
Approach 1
The socket in endpoint is type erased. So we need to add extracting function to get native socket. It is just you trying approach.
Approach2
Add client certification authorization mechanism on server.hpp before the type is erased.
I don't have much time now so those approach is just idea. I'm not sure it is possible.
I'm doing other issue and pull requests on mqtt_cpp. After finished them, I will take a look the issue.

No, it's not client certificate authentication -- that can already be done in a handler on the ``ssl::context`.  But the context handler is agnostic of a particular client socket.
What I'm trying to do is that after SSL has successfully completed client certificate authentication and the MQTT CONNECT is being processed, I want to look up some data from the client certificate that was presented earlier and compare it with the MQTT client id and username.
Having access to asio::ssl::stream::native_handle() would suffice for that.

Well, it looks like https://github.com/uecasm/mqtt_cpp/commit/a0d7c747f1adf57f4f75c85e63140620f03fb51e works, although it makes use of boost::any as the return type, which isn't ideal.  (But maybe that's the best we can do in a type-erased context?)
Given this, the peer certificate can be extracted with:
auto cert = SSL_get_peer_certificate(boost::any_cast<SSL*>(ep.socket().native_handle()));

(I can turn it into a PR if you like, although I'm not sure if it's complete.  Or the right way to do it.)

I guess that websocket support is required.
I wrote #577. Could you check this?
The return value type any is the best choice.
I use any. That means MQTT_NS::any. It is std::any or boost::any depend on compile option (or cmake option), the default is boost::any.

#577 seems to work ok.
Although (since upgrading from 7.0.1) the new dup/retain enums seem more annoying (and error prone) than the bools.  Also there's a copy/paste error in dup_to_str.  And ideally is_dup etc shouldn't duplicate the bitmasks.

#577 seems to work ok.

Thanks, I close the issue.
Please don't write unrelated topic. If you have some issue, create new one


Look in /Application and Utilities first

First /Applications, then /Applications/Utilities, and then Spotlight. Maybe we should be prepared that DEPnotify should be installed in Utilities, so customDestination="/Applications/Utilities/"could ba a thing.

Thanks!


GEODE-10292: Bump to boost 1.79.0

Initially complained that it did not know what boost::filesystem::ofstream before adding the header file

surprised at the sad time for windows.  I thought on my windows 10/vs2019 personal machine things were fine, but guess will have to check again

ok I think the problem is _WIN32_WINNT needs to be updated, but I don't quite understand why bumping boost would require changing what windows version to target

Hello Michael,
Any plan when this will be merged? Thanks!

Probably not anytime soon as I haven't made time to to figure out this problem.  Will close the PR since I'm not making progress on it


Forward port rel/7.1 to rel/7.2

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/17672' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/rel/7.2",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "rel/7.2",
    "SCALITY_S3_BRANCH": "forward/rel/7.1"
}

:broken_heart: :umbrella: circleCI test failed.

PR has been updated. Reviewers, please be cautious.

@ironman-machine try

Hello @nicolas2bert
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/17705' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/rel/7.2",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "rel/7.2",
    "SCALITY_S3_BRANCH": "forward/rel/7.1"
}

:sunny: :+1: circleCI test succeeded!


1274: Combine release prepare & release prepare no maven

Add in boolean for stating wherever to run maven commands or not in release prepare
Call only release prepare
Issue: https://github.com/SecureApiGateway/SecureApiGateway/issues/1274

How does bumping the version work when using gradle?

How does bumping the version work when using gradle?

It is a manual change which we identified needs looking at - as there's two versions that get changed which can likely go to one - https://github.com/SecureApiGateway/secure-api-gateway-ob-uk-functional-tests/pull/190/files
Ideally we'll also change this to take the input number when running the workflow


['Document cannot be parsed.'] - SPDX format file being used

(ntia-conformance-checker) (base) ricardo@MB cli_tools % python checker.py
File name: /Users/ricardo/_git/spdx_sboms/us-demo-org-2_react.spdx
['Document cannot be parsed.']
Is there a way to produce more details on the error why the document cannot be parsed?
I'm referencing a standard SPDX file format. I have presented absolute path to the source file, and I have even moved the file inside the cli_tools/ directory where checker.py is located.
(ntia-conformance-checker) (base) ricardo@MC cli_tools % python checker.py
File name: us-demo-org-2_react.spdx
['Document cannot be parsed.']
Thanks.

@RicardoAReyes, thanks for the request.
It might indeed be possible to produce more details. I'll investigate.
It would help if I could use the actual SPDX SBOM document you are using. Are you willing and able to share it?

sure, more than happy to share one of the spdx files @jspeed-meyers , our system generated an SBOM SPDX format file for the React framework.
https://drive.google.com/file/d/1qVTIbDVAXy9AJPg75rqoj7cRjreFSAU9/view?usp=share_link

here is a second example, react_app.spdx file
https://drive.google.com/file/d/11mirJpnD2PkWrQde0nhToOPr0YKRCz7S/view?usp=share_link

Excellent, thank you, @RicardoAReyes.

@RicardoAReyes, I pushed a branch that prints out more information. See PR #29.
When I run:
python3 ntia_conformance_checker/cli_tools/checker.py --file ~/Desktop/react.spdx

The error I now see is:
['Document cannot be parsed: FileType Not Supported/Users/johnspeedmeyers/Desktop/react.spdx']

When I check filetype, I get:
file ~/Desktop/react.spdx
/Users/johnspeedmeyers/Desktop/react.spdx: ASCII text

Hmm, I'm not an SPDX file type expert. I'm not able to quickly solve this. Let's call in reinforcements. @goneall or @linynjosh, any thoughts?
If nothing turns up, I can investigate more next week :)

I just ran the SPDX Tools Online Validator on the file and it did parse without any exceptions.  It did produce a few warnings, but I don't think they are related to this issue.
Below are the warnings:
The following warning(s) were raised: [Package at line 8345 invalid: Missing required package files for yocto-queue, Package at line 8345 invalid: Missing required package verification code for package yocto-queue, Missing required copyright text for yocto-queue in yocto-queue, Missing required license information from files for yocto-queue, Missing required package files for yocto-queue, Missing required package verification code for package yocto-queue]

Thank you for pushing that code exception fix @jspeed-meyers and for validating the SBOM spdx file with the online tool.
@jspeed-meyers do you think checker.py needs more reviews as to why it not able to parsed our files?

@RicardoAReyes, feel free to take a look. I'm not sure of the bug right now. It might be in the underlying python library doing the parsing. Feel free to investigate or submit a PR.
I will take a look early next week :)

I looked at the dependencies and this library is using a fork of the tools-python library.
There has recently been a lot of improvements in the library which are not reflected in the fork.
I'm thinking we should migrate to the most recent release of the tools-python code.  It looks like there are 3 commits we'll want to move over.

@goneall, ahh, good find. Let's do that migration and then come back to this issue. I suspect they're related.
For "moving over" these commits, do you mean submitting a PR to upstream of tools-python with those 3 additional commits?

For "moving over" these commits, do you mean submitting a PR to upstream of tools-python with those 3 additional commits?

Yes - that what I was thinking.  I recall @linynjosh was going to make a PR to the Python libraries - not sure if it was already done.
@licquia - let me know if you recall if the upstream changes were made.

@RicardoAReyes, I believe this bug is fixed due to now-merged PR #31.
When I now run the tool:
python3 ntia_conformance_checker/cli_tools/checker.py --file react.spdx

I get this,  which I have abridged to make it easier to read:
['us-demo-org-2/react: Document  version SPDX-2.0 not supported.', 'us-demo-org-2/react: Document has no author.', 'us-demo-org-2/react: abab has no supplier.', 'us-demo-org-2/react: abab has no supplier.',...

To get a machine-readable JSON output, you can use this command:
python3 ntia_conformance_checker/cli_tools/checker.py --file ../../../react.spdx --output json

You will get this output, which I have abridged to make it easier to read:
{
  "componentVersions": {
    "nonconformantComponents": [],
    "allProvided": true
  },
  "componentIdentifiers": {
    "nonconformantComponents": [],
    "allProvided": true
  },
  "componentSuppliers": {
    "nonconformantComponents": [
      "us-demo-org-2/react:",
     ...
    ],
    "allProvided": false
  },
  "componentNames": {
    "numNonconformantComponents": 0,
    "allProvided": true
  },
  "authorNameProvided": false,
  "timestampProvided": true,
  "dependencyRelationshipsProvided": true,
  "isNtiaConformant": false,
  "sbomName": "us-demo-org-2/react"
}

PTAL and let me know if this output looks right. Further bug reports welcome, though please open separate issues (assuming the issue is different then the ['Document cannot be parsed .'] issue). Thank you again for bringing this bug to our attention!!!
I'll close this issue in a week, and if you can't get to this issue by then, feel free to re-open it then if there is still an outstanding issue.

Thank you @jspeed-meyers @goneall  I appreciate everyone's contribution to address the issue so rapidly. I will continue to test and submit new issues should I run into more problems.


Validate that there is sufficient font fallback on macOS

See #30700 for context. Most of the issues that have been reported have been on Linux, but we should do more testing on macOS to ensure that we have sufficient fallback logic implemented on macOS (in particular for cases like emoji and other character-not-available-in-this-font cases).

I've tested this thoroughly on Linux, and confirmed on Mac. The current fallback steps are

Look for a fallback family font specified by the host


nginx syntax highlighting error

There's a problem with nginx conf files where comments sometimes isn't proper highlighted. If ou look here https://gist.github.com/plentz/6737338#file-nginx-conf-L6-L9 some comments aren't displayed in grey. But looking at the same file inside sublime text using nginx syntax, it looks okey.

maybe related with #2125

Hi @plentz - we use this grammar to highlight files on GitHub. Would you mind opening an issue over there? Once the bug is fixed in the grammar we can pull the changes in here.

@arfon Except this time, the grammar works fine in Sublime Text :/ (I checked with the last dev version). This issue is very close to #2125 so it's probably best to follow it there.

@pchaigno thanks :)

Turns out I had an error in my regex and sublime is a bit more forgiving (see my fix: https://github.com/brandonwamboldt/sublime-nginx/commit/872afddd2d61acae85560fa009658257f4030244). I will submit a PR to update the submodule here :)

Ok thanks for the follow up. Does that mean this issue can be closed?
On Tue, Feb 24, 2015 at 7:30 PM, Brandon Wamboldt
<EMAIL_ADDRESS>wrote:

Turns out I had an error in my regex and sublime is a bit more forgiving (see my fix: https://github.com/brandonwamboldt/sublime-nginx/commit/872afddd2d61acae85560fa009658257f4030244). I will submit a PR to update the submodule here :)
Reply to this email directly or view it on GitHub:
https://github.com/github/linguist/issues/2155#issuecomment-75888367

@arfon Once my PR gets created and merged :)


building - Updating iOS platform.

The build never ends.
I get always always this message in visual studio 2015: (it run for more than 2 hours)
Checking on build status from http://X.X.X.X:3000/cordova/build/tasks/3781 [Attempt XX]
1>  building - Updating iOS platform
The last message of the build.log on my mac is:
Attempt to update xcode project: /Users/juasan00/.taco_home/remote-builds/taco-remote/builds/3159/cordovaApp/platforms/ios/ROOMobile.xcodeproj/project.pbxproj
I have now xcode7, before I had xcode6 and had the same issue.
I tried already to uninstall-install and update everything... any idea how to fix this?
Thank you!

What version of nodejs are you running on the mac with remotebuild? There is a known issue in cordova under nodejs 4.X where if you have certain options specified in config.xml, the build process won't finish correctly. When using cordova directly this shows up as the build terminating immediately, but when this happens in remotebuild it shows up as a hung process waiting for an event that will never happen.
Until Cordova comes up with a solution your best bet is to revert back to nodejs version 0.12.7, or you can make sure that your config.xml does not specify any preferences relating to iOS version or whether it is for phone or tablet.

Thank you! it works with nodejs 0.12.7


Update VCRedist Dependency

null
Microsoft Reviewers: Open in CodeFlow

@denelon - Seems all of VMware.WorkstationPlayer is now having Binary-Validation-Error. What should we do here?

cc @OfficialEsco @jedieaston

@wingetbot run

@wingetbot run

This needs further investigation, will follow up once the issue is resolved.

/azp run

/azp run


refactor middleware injector interface

Some middleware/plugins may require multiple middleware phase registering interface. For those cases provide a convenient interface, such as:
type Binder interface {
Bind(Pluggable)
}

Done!


Add Hungary

Would you add It to the official list? :P

Yes it would be nice to see.

Added in a370ac8


FreeType issue

Hi, I'm trying to create a PDF using the node-red-contrib-pdfnode.
Node-Red crashes because of an error running phantomjs.
What are the steps to reproduce?
Try this flow:
[{"id":"d14643fe.354bf","type":"tab","label":"Flow 2","disabled":false,"info":""},{"id":"bdf6da8d.e3fd2","type":"HTML-PDF","z":"d14643fe.354bf","name":"HTML-PDF","output":"stream","x":610,"y":140,"wires":[["2ff5a2c6.67d0b6"]]},{"id":"2ff5a2c6.67d0b6","type":"debug","z":"d14643fe.354bf","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":790,"y":140,"wires":[]},{"id":"d64b45b9.5d7108","type":"inject","z":"d14643fe.354bf","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":280,"y":140,"wires":[["cda78a40.e9716"]]},{"id":"cda78a40.e9716","type":"template","z":"d14643fe.354bf","name":"","field":"payload","fieldType":"msg","format":"handlebars","syntax":"mustache","template":"\n    \n
This is the payload: {{payload}} !
\n    \n","output":"str","x":440,"y":140,"wires":[["bdf6da8d.e3fd2"]]}]

What happens?
Node-Red crashes then is restarted by Docker:
kaalut-node-red  | 10 Dec 17:35:50 - [red] Uncaught Exception:
kaalut-node-red  | 10 Dec 17:35:50 - Error: spawn /data/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs ENOENT
kaalut-node-red  |     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
kaalut-node-red  |     at onErrorNT (internal/child_process.js:415:16)
kaalut-node-red  |     at process._tickCallback (internal/process/next_tick.js:63:19)
kaalut-node-red  | npm ERR! code ELIFECYCLE
kaalut-node-red  | npm ERR! errno 1
kaalut-node-red  | npm ERR<EMAIL_ADDRESS>start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" "npm" "start" "--" "--userDir" "/data" "--settings" "/usr/src/node-red/.node-red/settings.js"`
kaalut-node-red  | npm ERR! Exit status 1
kaalut-node-red  | npm ERR!
kaalut-node-red  | npm ERR! Failed at the<EMAIL_ADDRESS>start script.
kaalut-node-red  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
kaalut-node-red  |
kaalut-node-red  | npm ERR! A complete log of this run can be found in:
kaalut-node-red  | npm ERR!     /root/.npm/_logs/2019-12-10T16_35_50_340Z-debug.log

What do you expect to happen?
A PDF file to be created.
Please tell us about your environment:

[X] Node-RED version: 1.0.3
[ ] Node.js version: -
[ ] npm version: -
[X] Platform/OS: x86_64/Debian
[ ] Browser: -

More information:
In the container:
bash-4.4# file /data/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs
/data/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.26, BuildID[sha1]=d0f2a21ff9e0b82113a2095e7cbca7dceaba88fb, stripped
bash-4.4# /data/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs
bash: /data/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs: No such file or directory

So, binary is here but won't run. Looking closer:
bash-4.4# ldd /data/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs 2>&1|head
        /lib64/ld-linux-x86-64.so.2 (0x7fb12a19d000)
        libz.so.1 => /lib/libz.so.1 (0x7fb12a183000)
Error loading shared library libfontconfig.so.1: No such file or directory (needed by /data/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs)
Error loading shared library libfreetype.so.6: No such file or directory (needed by /data/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs)
        libdl.so.2 => /lib64/ld-linux-x86-64.so.2 (0x7fb12a19d000)
        librt.so.1 => /lib64/ld-linux-x86-64.so.2 (0x7fb12a19d000)
        libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7fb12a19d000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7fb12a02e000)
        libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7fb12a19d000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fb12a01a000)

Hi there.
Please raise this issue against the contrib node that is causing the crash. This repo is for the core Node-RED runtime and editor which doesn't do anything with phantomjs.

Alas, following this link leads to a 404 on GitHub :(
And I can't find a way to install FreeType libraries in the container ? Thanks for any hint.


Delete does not work if config is pointing to a branch other than master

- Do you want to request a feature or report a bug?
Report a Bug
- What is the current behavior?
When the api does a GET to show the collection or look at a specific item in the collection from github it includes a ref GET param specifying which branch to use for the request, but the delete workflow does not specify this GET param. The resulting behavior is you can only delete content on the master branch and if you have a multi branch configuration you will mistakenly have content deleted on master instead of the branch you are working on or if it does not exist on master then an error will be surfaced.
- If the current behavior is a bug, please provide the steps to reproduce.
To reproduce, setup the config pointing to a non master branch.
backend:
    name: github
    repo: # Path to your Github repository
    branch: develop

Then in the CMS

Create a new piece of content
Click to edit it
Delete it

You will see an error message and network logs will show a request with a 404 to the master branch verifying that it cannot verify the content is present. Deleting will not proceed. If that content was on master it would be deleted.
- What is the expected behavior?
The expected behavior is that a ref=develop GET param would be passed for the GET confirmation and subsequent deletion.
- Please mention your node.js, and operating system version.
This is the case running on Netlify production

@VitaminDAgency are you running off a released version? This should be fixed as of #604 being merged, but the fix hasn't been released yet.

I am running on release 0.4. I searched open tickets. I should have search all tickets. That is my oversight. My apologies.

@VitaminDAgency no problem, thanks for filing an issue when you ran into a bug!


Update Endpoints

We need to update the API endpoints to make sure more of the business logic is done on the back end.

We'll track this as individual items on a as need basis instead of tracking it all together in this issue.


Note that only user@domain is supported for vSphere master creds

Story for context: https://www.pivotaltracker.com/story/show/158904932
[#158904932]

Thanks @chinangela!


Add vdo-opencl-filtering example

Change-Id: I75369e203019a83321bb55ba2049cbd058db18ee

I think this was pushed to wrong repo since this example is not yet approved for opensource by IPR etc. Can you push it to acap3-examples-staging repo instead?


Increase code coverage

Codecov Report

Merging #2 (5c21364) into main (43df029) will increase coverage by 4.54%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main       #2      +/-   ##
============================================
+ Coverage     71.21%   75.75%   +4.54%
  Complexity        3        3
============================================
  Files             4        4
  Lines            66       66
  Branches         32       32
============================================
+ Hits             47       50       +3
+ Misses            2        0       -2
+ Partials         17       16       -1

Impacted Files
Coverage Δ
Complexity Δ

...c/main/kotlin/com/github/pgreze/process/Process.kt
67.56% <0.00%> (+2.70%)
0.00 <0.00> (ø)

...in/kotlin/com/github/pgreze/process/InputSource.kt
72.72% <0.00%> (+18.18%)
0.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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


Data Quality

As discussed in https://github.com/MoritzStefaner/ach-ingen-zell/issues/1 and e.g. this twitter conversation https://twitter.com/opendatazurich/status/685149554405195777, it seems that using OSM instead of GeoNames is a valid option.
In particular, check out @TobWen 's comments in the other issue:

https://github.com/MoritzStefaner/ach-ingen-zell/issues/1#issuecomment-172386225
https://github.com/MoritzStefaner/ach-ingen-zell/issues/1#issuecomment-172457213

Any opinions, ideas, ... welcome!

Note: In my own fork/repo, I set up 3 stages of OSM data (using overpass turbo), see here:
http://bgrsquared.com/placeNamesExp/
where the filters can be found here:
https://gist.github.com/chroth7/43ca48597a3a28ef3dbe
Also, I am tracking the comments (if any :) ) here:
https://github.com/bgrsquared/placeNames/issues/1

Note: my repo is now fully based on OSM
(new live link: http://bgrsquared.com/places/)
Using overpass queries to grab data and some sed/awk/bash action to parse it :)


Slime vr FBT?

I read the read me but I couldn’t find any reccomendations regarding slime vr FBT setup, let alone if it even supports it. Am I missing something?

Slime VR will work fine with ALVR

You do need to change a setting so that it doesn't deregister itself or other drivers though

Which setting?

You'll find it, it's near the bottom I don't remember the exact name


Coy theme: height CSS tag creates design issues.

The height=100% CSS tag in the coy theme - which doesn't seem to exist in other theme CSS definitions - is causing the code block to render as the browser's height:
Broken:

Fixed:

Since it is such a minor change, I will propose a code change via GitHub to remove this single line from the Coy theme. Thanks for your efforts, they are widely appreciated!

I'm not sure what it was for... But I couldn't find any explicit browser issue without the height property, so I guess it's ok to remove it. Thanks!


 See issue #747

This was 100% my fault -- I made olzraiti take out "index" before merging #653. Thanks for fixing it.


Plugin breaks down when map size is not square

See title, setting map to anything not square causes really weird glitching in the created map.
If you set an expansion limit to something like a 100 cells, you'll notice that multiple "wave-fronts" seem to be created.

That is possible, I have not run this project in a while. It is possible that the scenenet branch has commits that fix the issue. I am not actively working on this project at the moment. I have been meaning to clean it up and bring it into a good shape since few people seem to be using it, but let's face it, I don't find the time right now. A pull request is appreciated and I will try to test and review it quickly. Thanks!


Add more route matching tests

This covers some of the intended fixes made by https://github.com/rackt/react-router/pull/2421.

thank you @taion


Use reflection to circumvent api changes in Selenium 4

Fixes #4593

@kiview What is your opinion to my approach?

Superseded by #4914.


Details of the calculation when referencing a quantized TFLite CNN model

Issue type
Documentation Feature Request
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.14.0
Custom code
Yes
OS platform and distribution
Window10
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
for the purpose of research and learning, I am trying to understand the series of mathematical operations needed to operate when using a CNN quantized model. I started with quantized conv2D layers.
I studied a paper about the quantization method and inference method. As I understand, when operating conv2D, an affine function is applied to input data and kernels; then, we add bias to the result. Finally, we quantize the result to uint8 (also using an affine function), so the uint8 quantized result can be used for the next layer.
I created a very simple model that contains only one conv2D layer, with 1 input channel and 1 output channel. So, the only operation this layer performs is the convolution between the input and the simple kernel that I created.
input = np.array([[[[1] for _ in range(4)] for _ in range(4)]])
custom_matrix = np.array([[1,1,1], [0.5, 0.5, 0.5], [1, 1, 1]]).astype(np.float32)

custom_initializer = Constant(value=custom_matrix)
def creat_model():
    model = Sequential(
        [
             Conv2D(1, (3,3), padding="same", input_shape = (4,4,1),      kernel_initializer=custom_initializer),

        ]
    )
    return model

model = creat_model()

Then, i quantized the simple model
random_matrices = np.random.randint(0, 256, size=(50, 4, 4, 1))
print(random_matrices[0].shape)
x_train = random_matrices / 255.0
x_train = np.asarray(x_train).astype(np.float32)
x_train = np.asarray(x_train).astype(np.float32)
def representative_data_gen():
  for input_value in tf.data.Dataset.from_tensor_slices(x_train).batch(1).take(40):
    yield [input_value]

converter = tf.lite.TFLiteConverter.from_keras_model(model)

converter.optimizations = [tf.lite.Optimize.DEFAULT]
converter.representative_dataset = representative_data_gen
converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS_INT8]
converter.inference_input_type = tf.uint8
converter.inference_output_type = tf.uint8
tflite_quant_model = converter.convert()

I succesfully infer using this quantized model (the result of the origin model & of quantized model are quite the same).
But when i print details about the quantized model using
interpreter = tf.lite.Interpreter(model_content=tflite_quant_model, experimental_preserve_all_tensors=True)
interpreter.allocate_tensors()
tensor_details = interpreter.get_tensor_details()

for tensor_detail in tensor_details:
    print(tensor_detail['index'], "   Name: ", tensor_detail["name"])
    print("     Quant_parameters:", tensor_detail["quantization"])
    print("     Type:", tensor_detail["dtype"])

The result is
0    Name:  serving_default_conv2d_4_input:0
     Quant_parameters: (0.003921568859368563, 0)
     Type: <class 'numpy.uint8'>
1    Name:  sequential_4/conv2d_4/BiasAdd/ReadVariableOp
     Quant_parameters: (3.0878494726493955e-05, 0)
     Type: <class 'numpy.int32'>
2    Name:  sequential_4/conv2d_4/Conv2D
     Quant_parameters: (0.007874015718698502, 0)
     Type: <class 'numpy.int8'>
3    Name:  tfl.quantize
     Quant_parameters: (0.003921568859368563, -128)
     Type: <class 'numpy.int8'>
4    Name:  StatefulPartitionedCall:01
     Quant_parameters: (0.023214150220155716, -128)
     Type: <class 'numpy.int8'>
5    Name:  StatefulPartitionedCall:0
     Quant_parameters: (0.023214150220155716, 0)
     Type: <class 'numpy.uint8'>
6    Name:
     Quant_parameters: (0.0, 0)
     Type: <class 'numpy.int8'>

I tried to find documetation about these tensors for many days but i can't. I think that the first tensor is used to convert input value range from [0,1] to [0,255]. The second tensor for operating with bias parameters. The third tensor for convolution operation. But i don know how last tensors operate with their quantization parameters to get final result.
My questions is:

How my data calculate thought these tensors with specific input value. And why is the last tensor look so strange (no name and all paramers are equal 0)

I tried to quantization with all parameters is uint8, but i can't find supported parameter to configure for converter

I really need and will appreciate any help or suggestions I may receive. Thank you so much.
Standalone code to reproduce the issue
(code above)

Relevant log output
No response

Hi @Truongdhvnu,
It's appreciable for your research interest on TFLite quantization.

How my data calculate thought these tensors with specific input value. And why is the last tensor look so strange (no name and all paramers are equal 0)

In the TFLite quantization process, the input values, weights and bias data types(float) at each layer are converted to  either to int8/int16/float16/...  during conversion depending on target device. The quantization might be symmetric(-127to +128) or affine(Unsymmetric 0-255) .  To know how  tensors are quantized, please refer  link1.
The last unnamed tensor might be an unused tensor created during the conversion process.

I tried to quantization with all parameters is uint8, but i can't find supported parameter to configure for converter

For more clear interpretation about tensors and their quantized values add the following command for tflite file.tf.lite.experimental.Analyzer.analyze(model_content=tflite_quant_model)   and  use link2 for better visualization of the quantized model .
interpreter = tf.lite.Interpreter(model_content=tflite_quant_model, experimental_preserve_all_tensors=True)
interpreter.allocate_tensors()
tensor_details = interpreter.get_tensor_details()
tf.lite.experimental.Analyzer.analyze(model_content=tflite_quant_model)

Thank You


Request for power=pole preset

I'm not sure if this is a duplicate request, if so, please link to older.
I found this tagging many times, but it seems there is no preset for adding such standalone (power=pole) node.
https://wiki.openstreetmap.org/wiki/Tag:power%3Dpole
https://taginfo.openstreetmap.org/tags/power=pole
Thank you

Yes, we currently only allow the power=pole to be a node along a way, for example a power=line.  Is it common to need just the pole with no line attached?

Hi - thanks for reading and checking.
Actually I'm not sure if I understand correctly, or if I didn't tell enough details for my preset request.

Yes, we currently only allow the power=pole to be a node along a way, ...

That's fine, if there is a preset available only for tagging key “power”=”pole” on node objects I'm would be very happy.

Is it common to need just the pole with no line attached?

It's not common to use a pole without a line for my mapping process, and I also think for others. But sometimes you will not be able to see the next pole at the imagery => so there is no option to draw the power_line line (I meant at the beginning without local survey). But this is not my point, I usually don't want do a mapping of standalone power-pole nodes.
I try to explain.
My request is for increasing mapping speed. When I start mapping energy infrastructure (pole nodes and e.g. minor_line lines) I usually start mapping by drawing the pole nodes. For this step it would be convenient to have a preset. Maybe for search-word "pole" should be a preset item available, let’s say "Power Pole", it could be displayed at the left object list, and by selecting(clicking) the item it should automatically fill the "power"="pole" tag to the "All tags (1)" chapter.  So then there is no need to enter manually “power” and “pole“ for each object each time. (Currently I use a workaround: I copy a node with already given tagging "power"="pole" and I paste it to the area of the map where want to add the next pole object…)
Similar if you add a street lamp.
You can put "lamp" in the search-box, the first line of the search result will show "Street Lamp", when you left click on it, the tagging box is automatically filled with "highway"="street_lamp" (and the white color of the node circle area changes and shows a small icon of a lamp). Same I would prefer to have for power pole. (The icon is not important, because after drawing the “power”=”minor_line” tag to the nodes, then the node decreases to a size of a very small dot without icon => the icon is at the end useless)
Or is my common tagging procedure wrong? What is your procedure to map these kind of objects?
So I would appreciate to have a preset also combined which the nice function/feature that the most recent tagging objects will show on the top area of the recent list :-) so it’s even faster to add object 2,3,4, and so on.
Thank you

@bhousel , It would be useful when you are trying to work out where the line goes to and from but what would be better would be that as you drop new nodes on a minor line, it drops a power pole by default.
Even better still would be to check the last node and replicate it if it is a tower or pole on line or minor line. Mapping the 300km line from Darwin to Katherine power line would be so much easier!

(Currently I use a workaround: I copy a node with already given tagging "power"="pole" and I paste it to the area of the map where want to add the next pole object…)

Oh that's a good way to do it.  I think Copy-Paste is probably what I would recommend for repetitive mapping in iD (street lamps or power poles or picnic tables).
If you really want to add the power=pole tags very quickly, I'd just draw the line however you want to, then in JOSM do an overpass query to select all the child nodes and add the tag all at once.
#590 also sounds kind of like what you want - the ability to just keep repeat adding the same thing.  I haven't added that to iD yet because I don't want to just add a bunch of buttons for things people want, but rather add another dedicated place for these toggle-able editing states to live (thats #3123)

Thanks a lot :-)


[consolidated] Retry on reconcile subscriber error

Proposed Changes

Retry on reconcile subscriber error

Release Note

Retry on reconcile subscriber error

/cherry-pick release-1.2

/cherry-pick release-1.1

/cherry-pick release-1.0

/lgtm


CLOUDSTACK-8820: Showing error when try to add vCenter 6

CLOUDSTACK-8820: Showing error when try to add advance zone using VMware ESXi 6.0 host
Summary: In vCenter 6.0, response headers need to be fetched after service login for server cookie unlike previous versions of vCenter.

Great PR @sureshanaparti I was going to work on supporting this as ESXi6 works well on top of KVM; I can test this for you next week; LGTM on code change (not tested though)

change makes sense but I have some comments on the coding style.

@sureshanaparti Nice work! The PR title confused me a bit though. What about:
CLOUDSTACK-8820: Support for VMware vCenter 6 data center
@bhaisaab Would appreciate it if you could test this. Thanks! Nice feature to go with ACS 4.6 :-)

@remibergsma sure, but can do this next week (lack infra right now)

@remibergsma That sounds good.

FWIW LGTM

@sureshanaparti code LGTM.
I will test this patch today in my lab and will get back.

Alright, let's wait for lab tests to confirm the patch and only then we should merge it.
Thanks for helping test it @sateesh-chodapuneedi

Tested adding ESXi 6.0 host to advanced ACS zone successfully.
Session logic is working fine.
@bhaisaab you might want to go ahead merge it. Thanks.


Sanitizing username to prevent invalid email

In certain locales (e.g. nl_NL), special characters are used in names such as ç; when using these characters for generating email addresses, this will result in an invalid email address (e.g<EMAIL_ADDRESS>or sarah.ünal@example.com), which causes tests in my case to fail.

@EmileBons I'm not sure that should be necessary as utf8 email address become actually an accepted option :

http://en.wikipedia.org/wiki/Email_address#Internationalization
http://tools.ietf.org/html/rfc5335

We're now using transliteration ; this is not necessary anymore. Thanks anyway for your PR.


Import aliased path for scss causes rollup error with Rollup failed to resolve import

Describe the bug
We are using rollup-plugin-includepath and typescript-plugin-css-modules with scss includePaths configured, to be able to import React components and .module.scss modules in our components, without the need for relative references (../../../).
This works fine with both tsc and during development with vite start.
However, with vite build, we get an rollup-error caused by ?used parameter on the .scss files.
For example in our .tsx file:
import listItem from 'components/header/ListItem.module.scss';
and in our .scss file:
@import 'scss/variables.module.scss';
In vitejs I found this that might cause the error for us:
https://github.com/vitejs/vite/commit/3e3c20364d6c065026f7362bbcb7094099705cc9#diff-121079017d1fa98d6a0ea3354d5c73df45ab277078228cd7384c7a4e84c5a813R187
As a workaround, I implemented a small rollup-plugin.
resolveId(source: string) {
if (source.endsWith('?used')) {
return { id: src/${source.slice(0, -'?used'.length)}, external: false };
}
return null;
},
Are we using these imports the wrong way, or is this a bug in vitejs?

Reproduction
Clone sample repository, npm install, npm run build
https://github.com/johannessorheim/Vite5811
This line triggers causes vite build to fail, and works with vite dev:
https://github.com/johannessorheim/Vite5811/blob/main/src/some/deep/folder/component.tsx#L4
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
    Memory: 4.00 GB / 15.74 GB
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.1.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 96.0.4664.45
    Edge: Spartan (44.19041.1266.0), Chromium (96.0.1054.29)
    Internet Explorer: 11.0.19041.1202
  npmPackages:
    @vitejs/plugin-react: ^1.0.8 => 1.0.8
    vite: ^2.6.14 => 2.6.14

Used Package Manager
npm
Logs
[vite]: Rollup failed to resolve import "components/header/ListItem.module.scss?used" from "src\components\header\small\NavigationMenu.tsx".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
error during build:
Error: [vite]: Rollup failed to resolve import "components/header/ListItem.module.scss?used" from "src\components\header\small\NavigationMenu.tsx".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@yyx990803
https://github.com/vitejs/vite/commit/3e3c20364d6c065026f7362bbcb7094099705cc9#diff-121079017d1fa98d6a0ea3354d5c73df45ab277078228cd7384c7a4e84c5a813R177

I find that the plugin rollup-plugin-includepath seems to be obsolete and not maintained.
Are there any other recommended way to have scss typescript support with Vite + React Typescript, both in tsx-files and in scss-files?

Seems this issue has been resolved by https://github.com/vitejs/vite/issues/8245


Anisotrop fix ipv6 accept options

Resolved conflicts with develop. The regular expression seemed to miss an IPv6 adress between brackets (because of the mandatory @ sign). Proposing a simplification to try to extract the host and port by generic expression. If the expression doesn't match the value could be a port. Otherwise is host only and it should be rejected. Some of the tests don't cover the changed method since they fail earlier.

shouldRequireExplicitPortOnIPv6FromString
shouldRequireExplicitPortOnIPv6

Exception is thrown at
org.kaazing.gateway.resource.address.URLUtils.modifyURIAuthority(URLUtils.java:61)
	at org.kaazing.gateway.resource.address.uri.URIUtils.modifyURIAuthority(URIUtils.java:305)
	at org.kaazing.gateway.resource.address.tcp.TcpResourceAddressFactorySpi.newResourceAddresses0(TcpResourceAddressFactorySpi.java:203)
	at org.kaazing.gateway.resource.address.ResourceAddressFactorySpi.newResourceAddress(ResourceAddressFactorySpi.java:130)
	at org.kaazing.gateway.resource.address.ResourceAddressFactorySpi.newResourceAddress(ResourceAddressFactorySpi.java:72)
	at org.kaazing.gateway.resource.address.ResourceAddressFactorySpi.newResourceAddress(ResourceAddressFactorySpi.java:68)
	at org.kaazing.gateway.resource.address.tcp.TcpResourceAddressFactorySpiTest.shouldRequireExplicitPortOnIPv6(TcpResourceAddressFactorySpiTest.java:100)
[...]

@jitsni I have updated the pull request, by re-including network interfaces support, moving the method in a general purpose class and adding unit tests. Can you please review ?


Remove crypto-only related components from all.sh

This PR handles the removal of crypto-only components from all.sh tests.
More details here.

@RonEld

component_test_depends_hashes, component_test_depends_pkalgs: these check dependencies in X.509 tests and #ifdef guards in X.509 and TLS code.
component_test_null_entropy: Although the corresponding #ifdef is only used in a crypto module, this could have an impact on how some programs run, so I think it should be tested in a broader context.
component_test_min_mpi_window_size: ah, that's new. It wasn't there when we looked at what to remove. I agree that it should be removed. Thanks for spotting it!
component_test_no_udbl_division, component_test_no_64bit_multiplication, component_build_arm_none_eabi_gcc_no_udbl_division, component_build_arm_none_eabi_gcc_no_64bit_multiplication: these are borderline. In principle they apply to the whole source base, but in practice only some crypto code is likely to violate them. My recommendation is to keep the build_arm_ ones and remove the test_ ones because these test different things:

If the corresponding #ifdef breaks something, it should be in the crypto code and caught by crypto's corresponding test_ components.
If there's code that uses a forbidden operation, it could be anywhere, and that's what the build_arm_ components test.

Thanks @gilles-peskine-arm for your answer.
As long as the sections I mentioned were knowingly kept, I'm fine with that.
I'll approve once component_test_min_mpi_window_size, component_test_no_udbl_division and component_test_no_64bit_multiplication will be removed, according to your recomendation

@RonEld - as for the component_test_min_mpi_window_size - my bad, I haven't noticed it after rebasing. As for the rest of the build_arm ones - I wasn't  sure about these, so thanks for your input @gilles-peskine-arm  and @RonEld.
I have now amended the previous commit to contain all changes.

Please resolve conflicts (by deciding what to do about component_test_new_ecdh_context). Thanks.

I have rebased this PR and removed the forementioned component - component_test_new_ecdh_context.
@RonEld, @gilles-peskine-arm  - please re-review.

CI failure on head is flaky DTLS test. The merge result tests fine, so ready to merge.