Document indexing system for geometry coordinates

Describe the indexing system used to map coordinates, breaks, and holes.

Comment from @BobSimons originally here: https://github.com/bekozi/netCDF-CF-simple-geometry/issues/8#issuecomment-223698709.
I've been thinking about this project this week. Your comments are a good lead in to what I've been thinking about.
It seems that our solution here is to use an indexed array as a way of adding support for a ragged array so that we can efficiently store Simple Geometries in our own encoding of WKT in .nc3 files, since .nc3 files don't support ragged arrays. That's fine. And the problem goes away in .nc4 because ragged arrays are available.
Similarly, it seems like Section 9 of CF (Discrete Sampling Geometries) is all about how to add support for ragged arrays in .nc3 files so that we can efficiently store ragged array DSG data in .nc3 files, since .nc3 files don't support ragged arrays.  That's fine. And the problem goes away in .nc4 because ragged arrays are available.
It seems like there is a general problem: people want to use ragged arrays for various data structures. .nc4 has support for ragged arrays. .nc3 doesn't. We seem to be adding support for ragged arrays on a case-by-case basis, and using slightly different systems.
Shouldn't we break the Simple Geometry problem/proposal into two parts:

Make a proposal for a general purpose system for ragged arrays in .nc3 files. Use cases: in addition to DSG and Simple Geometries, the most obvious use case is Strings. It would allow CF to add support for variable-length Strings. This would be a huge bridge between .nc3 and .nc4, allowing .nc3 to gain one of the big features of .nc4. My first pass proposal is: add support for two alternative systems:

A generalized version of attributes and indexes as currently used by DSG's Contiguous Ragged Array system.
A generalized version of attributes and indexes as currently used by DSG's Indexed Array system.

Make a proposal for storing our encoding of WKT in one of these new, standardized ragged arrays (or WKT/B itself as a variable length String). I have more to say about this, but you get the basic idea.

Thoughts?
Love it? Hate it?

Responses below. Only opinions of course.

I've been thinking about this project this week. Your comments are a good lead in to what I've been thinking about.

A dangerous pastime.

It seems that our solution here is to use an indexed array as a way of adding support for a ragged array so that we can efficiently store Simple Geometries in our own encoding of WKT in .nc3 files, since .nc3 files don't support ragged arrays. That's fine. And the problem goes away in .nc4 because ragged arrays are available.

Yes, that is the idea. The mapping used in the reference implementation follows UGRID: http://ugrid-conventions.github.io/ugrid-conventions/#2d-flexible-mesh-mixed-triangles-quadrilaterals-etc-topology. The conversions I’ve used for many-noded, variable-length polygons use ragged arrays first, always (at least a ragged array-like data structure). If the client is requesting an .nc3 file, then the ragged edges are padded with a fill value (like current UGRID). This is very inefficient for polygons of varying length. This inefficiency more or less disappears with file compression. However, it remains a very inefficient rectangular array when loaded from file. Nc3 support is kind of baked-in for node indexing in this regard and could be added to the reference implementation once reading/writing netCDF files is added.

It seems like there is a general problem: people want to use ragged arrays for various data structures. .nc4 has support for ragged arrays. .nc3 doesn't. We seem to be adding support for ragged arrays on a case-by-case basis, and using slightly different systems.

I think our approach supports ragged and rectangular. Storing efficiently with rectangular arrays with variable-length geometries is another story. Is the Discrete Sampling Geometry approach efficient in this regard? I know you were building to the nc3-nc4 ragged array bridge here, but I just wanted to repeat.

Make a proposal for a general purpose system for ragged arrays in .nc3 files. Use cases: in addition to DSG and Simple Geometries, the most obvious use case is Strings. It would allow CF to add support for variable-length Strings. This would be a huge bridge between .nc3 and .nc4, allowing .nc3 to gain one of the big features of .nc4.

Definitely a cool idea. I need to understand DSG better. This sounds a bit independent from simple geometries but something it could definitely use for .nc3 support.

Make a proposal for storing our encoding of WKT in one of these new, standardized ragged arrays (or WKT/B itself as a variable length String). I have more to say about this, but you get the basic idea.

Storing WKT as a string would be an option with the ragged array API. Storing only WKT limits the format’s applicability and also balloons storage as coordinates are stored as in ASCII-like encodings. Some linestrings and polygons can get quite large. I think the WKT/WKB would make for great extensions, but we should focus on storing coordinate arrays directly at first. Does that make sense? WKB is not human-readable which is a problem…

Love it? Hate it?

I’m somewhere on the interpolated (thin) line between. Again, I need to get a better appreciation for DSG.

I'll mostly echo what @bekozi said.
Near term, we are copying the already established DSG patterns for ragged arrays (rectangular and long styles) warts and all. The understanding is that when CF 2.0 supports NetCDF-4 data types (vlen) we'll have a more elegant encoding.
The idea of using strings for WKT/B representation came up and was shot down pretty quickly. It would more-or-less imply an implementation technology-space of the geospatial data domain, leaving many domain scientists to do some really heavy lifting to parse and work with the data.
Think we are all on the same page here for the most part. I need to spend more time with the readme content that I started drafting up. Will try and more clearly link it to the DSG spec for timeSeries.

Dave

Here is a slightly revised and more complete proposal with a complete example at the bottom:
A Proposal for Variable Length (VLen, AKA Ragged) Dimensions
and Arrays in NetCDF 3.0.
This is a general system for vlen dimensions and arrays that
is very similar to the Discrete Sampling Geometry (DSG)
Contiguous Ragged Array (CRA) system.

Use cases:

The ugrid proposal currently being developed includes a
custom system for vlen arrays.
The Simple Geometries proposal currently being developed
includes a custom system for vlen arrays.
A given geometry may have a few nodes or 10's of 1000's.
Discrete Sampling Geometry. This would be an alternative
to the current system for Contiguous Ragged Arrays.

Rationale:
In all of the use cases, a standard NetCDF 3.0 system for
vlen dimensions and arrays would offer a much more compact,
appropriate, and standard data structure for the vlen data.
It would be a general solution to the use cases above
and a wide variety of other use cases. It would allow
the CF 1.0 standard to avoid having different systems for
ragged arrays in different sections of the standard.

Since vlen dimensions/arrays and vlen Strings are already
supported by the NetCDF-C and -Java API's, it should be
possible to enhance the library to use the same
methods/interface to support reading vlen dimensions/arrays
and Strings from an enhanced NetCDF-3 file.
Since vlen dimensions/arrays are in NetCDF-4 files and will
presumably be in CF 2.0, this proposal offers a bridge
between NetCDF-3 and NetCDF-4 files, respectively.
This extends the life and usefulness of NetCDF-3 files.

Sample CDL showing 2 variables (polyLat and polyLon)
that share the same vlen dimension:

dimension
timeseries=?;
obs=?;
int timeseries_stop(timeseries);
:contiguous_ragged_dimension = "obs" ;
double polyLat(obs);
double polyLon(obs);

The variable names are not relevant to this proposal.
The attribute "contiguous_ragged_dimension" and its value
(the name of a dimension) are the key to this proposal.
A variable with this attribute MUST be an integer type
(byte, short, or int) and may be a scalar or multidimensional.
Any variable that uses that named dimension is to be interpreted
using the information encoded in timeseries_stop (in this case,
the stop index for each timeseries feature)
in variable that has the "contiguous_ragged_dimension" for that
dimension.
[The DSG CRA system encodes the length of each feature.
By storing the stop index of each feature instead,
we can make each vlen chunk randomly accessible.]
More than one variable in a file can have a
"contiguous_ragged_dimension" attribute, but each such
attribute must have a different value.
If a variable with "contiguous_ragged_dimension" is
a multidimensional variable, then you treat it as a
1-dimensional array by looking at all the dimension
permutations in row-major order. (See the example below.)
This gives us a system in CF 1.0/netcdf-3 to parallel vlen
dimensions/arrays in CF 2.0/netcdf-4.
The approach described here works when the vlen dimension
is the rightmost dimension. It is possible to
chain these structures to have the vlen dimension
in a different location or have a variable with
multiple vlen dimensions.
A complete multidimensional example:

If you wanted to store a 3-D array with
[dimA=2][dimB=3][vlen=*] doubles, with
[0,0]={12.0, 17.0}
[0,1]={14.0,  9.0, 3.0}
[0,2]={ 5.0}
[1,0]={ 8.0}
[1,1]={ 2.0, 16.0, 15.0}
[1,2]={ 7.0,  1.0}
or stated another way:
[0,0,0]=12.0
[0,0,1]=17.0
[0,1,0]=14.0
[0,1,1]=9.0
[0,1,2]=3.0
[0,2,0]=5.0
[1,0,0]=8.0
[1,1,0]=2.0
[1,1,1]=16.0
[1,1,2]=15.0
[1,2,0]=7.0
[1,2,1]=1.0
then

The CDL for the file is:
dimensions:
dimA = 2;
dimB = 3;
dimC = 12;
int var1(dimA, dimB);
:contiguous_ragged_dimension = "dimC" ;
double var2(dimC);
The size of each of the vlen sub arrays is
{{2,  3,  1},{ 1,  3,  2}}
var1 would have {{2,  5,  6},{ 7, 10, 12}}
which is the stop index (1 past the last index) for each
vlen chunk.
var2 would have {12.0, 17.0, 14.0, 9.0, 3.0, 5.0, 8.0, 2.0, 16.0, 15.0, 7.0, 1.0}

@BobSimons Nice. I don't follow it entirely to be sure. :confounded: I think this should be shifted to maybe a wiki page so it doesn't get lost in the tickets. Is that the best spot for this?

I think about where it should go.
I sorry you didn't follow. So let me restate it specifically for this group:
To store 2 timeseries with
polyLon={{-70, -71},{-62, -63, -64}}
polyLat={{45, 45.5},{52, 52.1, 52.2}}
Do this:

Use this CDL:
dimensions:
timeseries = 2;
nNodes = 5;
int timeseries_stop(timeseries);
:contiguous_ragged_dimension = "nNodes" ;
double polyLon(nNodes);
double polyLat(nNodes);
The size of the vlen sub arrays is
{2, 3}
so timeseries_stop would have {2, 5}
which is the stop index (1 past the last index) for each
vlen group.
Stated another way: this array has the cumulative size
of the vlen groups.
polyLon would have {-70, -71, -62, -63, -64}
polyLat would have {45, 45.5, 52, 52.1, 52.2}

Does that make sense?
On Wed, Jun 8, 2016 at 10:45 AM, Ben Koziol<EMAIL_ADDRESS>wrote:

@BobSimons https://github.com/BobSimons Nice. I don't follow it
entirely to be sure. 😖 I think this should be shifted to maybe a wiki
page so it doesn't get lost in the tickets. Is that the best spot for this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bekozi/netCDF-CF-simple-geometry/issues/11#issuecomment-224671693,
or mute the thread
https://github.com/notifications/unsubscribe/ABarOKPeiIeFnkwHHXZTwURPavte7er2ks5qJv-xgaJpZM4ItDZC
.

--
Sincerely,
Bob Simons
IT Specialist
Environmental Research Division
NOAA Southwest Fisheries Science Center
99 Pacific St., Suite 255A      (New!)
Monterey, CA 93940               (New!)
Phone:<PHONE_NUMBER>            (New!)
Fax:<PHONE_NUMBER>
Email<EMAIL_ADDRESS>The contents of this message are mine personally and
do not necessarily reflect any position of the
Government or the National Oceanic and Atmospheric Administration.
<>< <>< <>< <>< <>< <>< <>< <>< <><

@BobSimons I like this approach and appreciate you keeping the bigger picture of a general nc3 vlen solution within our perspective.  I also find the CF CRA approach of indicating counts rather than stop index values cumbersome.  I'd be interested in hearing what folks who actually use CRAs think about your approach.

I am guessing that from the file writer standpoint, 'count' is easier to
understand.
I'm one of those people who actually reads these files (in ERDDAP). The
only difference for the reader is:

with counts, to get one vlen group or many, you have to read the entire
array, convert it to the cumulative stop indices, then read the data.
with stops, you wouldn't have to read the entire array to get one
specific vlen group. That's the advantage of 'stop'. When the array is
small, it doesn't matter much. When the array is huge, then it will matter
some.

I'm not adamant about count vs size.  It is a little cumbersome either way,
but both of these options are file-size-efficient. If the CF group prefers
one or the other, that's fine with me.
On Wed, Jun 8, 2016 at 11:58 AM, Tim Whiteaker<EMAIL_ADDRESS>wrote:

@BobSimons https://github.com/BobSimons I like this approach and
appreciate you keeping the bigger picture of a general nc3 vlen solution
within our perspective. I also find the CF CRA approach of indicating
counts rather than stop index values cumbersome. I'd be interested in
hearing what folks who actually use CRAs think about your approach.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bekozi/netCDF-CF-simple-geometry/issues/11#issuecomment-224693063,
or mute the thread
https://github.com/notifications/unsubscribe/ABarOMVHfw3hZTY6yqWVLHH-ZGd6yp1hks5qJxDDgaJpZM4ItDZC
.

--
Sincerely,
Bob Simons
IT Specialist
Environmental Research Division
NOAA Southwest Fisheries Science Center
99 Pacific St., Suite 255A      (New!)
Monterey, CA 93940               (New!)
Phone:<PHONE_NUMBER>            (New!)
Fax:<PHONE_NUMBER>
Email<EMAIL_ADDRESS>The contents of this message are mine personally and
do not necessarily reflect any position of the
Government or the National Oceanic and Atmospheric Administration.
<>< <>< <>< <>< <>< <>< <>< <>< <><

I think I am following more closely now. I would definitely advocate for "stops" over "counts". Stops allow using the indices directly and with the addition of multi-part breaks and hole breaks, the "counts" do not make a lot of sense.
@BobSimons and others, why not store a start and stop? Assuming I understand their usage correctly.

The downside to storing just "counts" (or "size"), is that the reader has
to read the whole array, convert it to cumulative values, then figure out
the start and stop indices.
The downside to storing just stop is that the reader has to do some extra
work to figure out the start index.
The downside to storing start+stop is the extra space needed in the file.
Some people are always concerned about space and object when it is wasted.
Pick your poison.  I prefer storing just "stop".
On Thu, Jun 9, 2016 at 9:35 AM, Ben Koziol<EMAIL_ADDRESS>wrote:

I think I am following more closely now. I would definitely advocate for
"stops" over "counts". Stops allow using the indices directly and with the
addition of multi-part breaks and hole breaks, the "counts" do not make a
lot of sense.
@BobSimons https://github.com/BobSimons and others, why not store a
start and stop? Assuming I understand their usage correctly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bekozi/netCDF-CF-simple-geometry/issues/11#issuecomment-224952173,
or mute the thread
https://github.com/notifications/unsubscribe/ABarOK_W_pRz0T7T0HrWBY8OZABhGGr8ks5qKEDVgaJpZM4ItDZC
.

--
Sincerely,
Bob Simons
IT Specialist
Environmental Research Division
NOAA Southwest Fisheries Science Center
99 Pacific St., Suite 255A      (New!)
Monterey, CA 93940               (New!)
Phone:<PHONE_NUMBER>            (New!)
Fax:<PHONE_NUMBER>
Email<EMAIL_ADDRESS>The contents of this message are mine personally and
do not necessarily reflect any position of the
Government or the National Oceanic and Atmospheric Administration.
<>< <>< <>< <>< <>< <>< <>< <>< <><

Makes sense. To be clear, the "stop" is only needed for the non-vLen, continuous ragged array case where node indices are stored as a single vector. With vLen, ragged arrays, the "stop" does not really have a usage as the index into the ragged array dimension serves the same purpose.
I am fine with using only "stop" for the CRA case. Having a "start" is superfluous.
I am coming around to the idea of supporting both cases (nc4 ragged array and nc3 continuous ragged array). I added a ticket for this to be supported as an output option: #18.

I also vote for "only stop" and supporting nc4 ragged and nc3 CRA.

Moved CRA proposal to: https://github.com/bekozi/netCDF-CF-simple-geometry/wiki/ContinousRaggedArrays. Going to close this for now. I believe we got the "stops" figured out and moved to a ticket. We can edit the proposal in the wiki as needed.


FieldRadios: required property not working properly

I'm using the FieldRadios component and specifying a required prop with a message to display. The message is taken into account but the asterisk showing the field is required isn't displayed.

Thanks to @d-campbell-bs done in https://github.com/BearStudio/start-ui/pull/51


Reference bible with xelah editor.

scroll lock enabled for separate navigatoin.

when creating a new project, if we click on the save button this error comes


[libcontainer] Integrate WasmEdge Runtime

In this PR, WasmEdgeExecutor is  introduced into libcontainer for integrating WasmEdge Runtime.

Codecov Report

Merging #1320 (f35cf5c) into main (d99b665) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1320      +/-   ##
==========================================
- Coverage   68.72%   68.70%   -0.02%
==========================================
  Files         119      119
  Lines       12602    12607       +5
==========================================
+ Hits         8661     8662       +1
- Misses       3941     3945       +4

@apepkuss There is a build failure. Can you check?

@apepkuss There is a build failure. Can you check?

Thanks for your message. I checked the issues in the failed workflows: one is a clippy issue caused by an unstable feature, and the other is the wasmedge library was not installed in the CI environment so the wasmedge-sdk crate cannot find the dependency. We'll fix them asap. Thanks a lot!

@apepkuss May I ask you to update the documentation for the developer and users? Another PR is fine.
https://containers.github.io/youki/user/webassembly.html

@apepkuss May I ask you to update the documentation for the developer and users? Another PR is fine. https://containers.github.io/youki/user/webassembly.html

@utam0k Sure. I'll try to update the document in this PR. Thanks!

Also, I will mention this topic on KubeDay Japan^1. What do you think? If you have something to say, please let me know via Discord or Twitter DM, and I'll think of something.

@apepkuss May I ask you to update the documentation for the developer and users? Another PR is fine. https://containers.github.io/youki/user/webassembly.html

@utam0k Sure. I'll try to update the document in this PR. Thanks!

Thanks 🙏
@apepkuss Also, I will mention this topic on KubeDay Japan12. What do you think? If you have something to say, please let me know via Discord or Twitter DM, and I'll think of something.
Footnotes

https://events.linuxfoundation.org/kubeday-japan/ ↩
https://sched.co/1C8lS ↩

@utam0k Thanks for your invitation. I believe my colleague has already contacted you. Please discuss the details with my colleague. Thanks again!

@utam0k @Furisto I've made some changes in this PR for the previous issues. Please review the latest changes. Thanks a lot!

@utam0k @Furisto I've made some changes in this PR for the previous issues. Please review the latest changes. Thanks a lot!

It seems that the ci got failed. I guess you missed something to install in the ci.
stderr:
/tmp/rustdoctestxV6caY/rust_out: error while loading shared libraries: libwasmedge.so.0: cannot open shared object file: No such file or directory

@utam0k @Furisto I've made some changes in this PR for the previous issues. Please review the latest changes. Thanks a lot!

It seems that the ci got failed. I guess you missed something to install in the ci.
stderr:
/tmp/rustdoctestxV6caY/rust_out: error while loading shared libraries: libwasmedge.so.0: cannot open shared object file: No such file or directory

@utam0k  Yeah, I also noticed the error and am working on it. I'll let you know if the issue is fixed. Thanks!

@utam0k Thank you very much for the review!


OMRSE broken ontology (important)

Hey! I just noticed you have two bugs in your OMRSE release:

In line 617 there is <<<<<<< HEAD which suggests that someone manually resolved a conflict after a commit and did not clean up properly (this causes this file to be unparseable!

Line 885: Again this suggests manual hacking and should be carefully traced back to its source: The closing '</owl:Class>' Tag is missing (and maybe more)! (also causes the file to be unparseable)

Generally, be careful when you edit the text file of the ontology manually rather than with Protege. It makes always sense to open the ontology once more in Protege after editing to be sure everything is as expected.

Thanks. I just updated this from the devel branch.


pplocate not updating after pipe transfer

Steps to repro:

Put pearl in pipe
Activate pipe
have pearled player ppl

Currently this is the same behavior as hoppers.  @Maxopoly said he was going to look into make it work but as of now this isn't a super high priority.

Do you have it working for hoppers? I already added the event and everything

https://github.com/Civcraft/FactoryMod/blob/master/src/com/github/igotyou/FactoryMod/events/ItemTransferEvent.java

We do not currently have it working with hoppers.  I suppose now I can add it.


Add already connected err for repository

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 9.984%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
182

Relevant Lines:
1823

💛  - Coveralls


An unhandled rejection has occurred inside Forge

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
6.4.2
Electron version
26.3.0
Operating system
macOS 13.5
Last known working Electron Forge version
No response
Expected behavior
App should be successfully packaged, signed and stapled,
Actual behavior
An unhandled rejection has occurred inside Forge:
Error: Failed to staple your application with code: 66

Processing: /private/var/folders/zk/0mmxhpss3gsd8_hp4lgmj7r40000gn/T/electron-packager/darwin-x64/Favia-darwin-x64-7FnNqx/Favia.app
Properties are {
    NSURLIsDirectoryKey = 1;
    NSURLIsPackageKey = 1;
    NSURLIsSymbolicLinkKey = 0;
    NSURLLocalizedTypeDescriptionKey = Application;
    NSURLTypeIdentifierKey = "com.apple.application-bundle";
    "_NSURLIsApplicationKey" = 1;
}
Props are {
}
Cannot download ticket. CDHash must be set.
at /Users/alex/Projects/favia/desktop/node_modules/@electron/notarize/src/staple.ts:16:11
    at Generator.next (<anonymous>)
    at fulfilled (/Users/alex/Projects/favia/desktop/node_modules/@electron/notarize/lib/staple.js:4:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
error Command failed with exit code 1.

Steps to reproduce
I have a basic config in my forge.config.ts
osxSign: {
},
osxNotarize: {
  tool: "notarytool",
  appleId: process.env.APPLE_ID,
  appleIdPassword: process.env.APPLE_ID_PASSWORD,
  teamId: process.env.APPLE_TEAM_ID,
},

when I run yarn make which calls electron-forge make I get the error.
Additional information
forge.config.ts
const config: ForgeConfig = {
  packagerConfig: {
    asar: true,
    icon: "./icons/icon.icns",
    osxSign: {}, // object must exist even if empty
    osxNotarize: {
      tool: "notarytool",
      appleId: process.env.APPLE_ID,
      appleIdPassword: process.env.APPLE_ID_PASSWORD,
      teamId: process.env.APPLE_TEAM_ID,
    },
  },
  rebuildConfig: {},
  makers: [
    {
      name: "@electron-forge/maker-dmg",
      config: {
        name: "Favia",
        icon: "./icons/icon.icns",
        format: "ULFO",
        overwrite: true,
      },
    },
    new MakerSquirrel({}),
    new MakerRpm({}),
    new MakerDeb({}),
  ],
  plugins: [...]
}

Same issue

I know it's not necessarily helpful to have a bunch of people +1ing an issue, but I'm getting this, too and would really appreciate a fix. Running the same setup as above, but I'm on macOS 14.1.1 and running Electron 27.0.4.

Got rid of this error by updating Node version. Running it on 21.1.x solved it for me.

Damn, that didn't do it for me. Even tried both Node v21.2.0 and going back to Electron 26.3.0. Also still happens in my GH Actions. Sorrow.

Both Node v20.9.0 and v21.1.0 not work for me

The Forge 7.0 update fixed this for me! 🎉

Is there any new progress on this issue?

@TinsFox The problem is related to the certificate. I created a file CertificateSigningRequest.certSigningRequest and saved it to my drive. Then I created a Developer ID Application certificate, saved the new certificate then built again and it worked for me.
You can use the command security find-identity -p codesigning -v to check the certificate is valid, Developer ID Application is required in this list.
forge.config.js
module.exports = {
  packagerConfig: {
    asar: true,
    icon: './images/icon',
    osxSign: {
      identity: 'Developer ID Application: *** JOINT STOCK COMPANY (XXXXXXXXXX)', // important
      'hardenedRuntime': true,
      'gatekeeperAssess': false,
      'entitlements': './mac/entitlements.mac.plist',
      'entitlementsInherit': './mac/entitlements.mac.plist',
    },
    osxNotarize: {
      tool: 'notarytool',
      appleApiKey: process.APPLE_API_KEY,
      appleApiKeyId: process.APPLE_API_KEY_ID,
      appleApiIssuer: process.APPLE_API_ISSUER,
    },
  },
...
...
}

entitlements.mac.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.apple.security.cs.allow-jit</key>
    <true/>
    <key>com.apple.security.device.audio-input</key>
    <true/>
    <key>com.apple.security.device.bluetooth</key>
    <true/>
    <key>com.apple.security.device.camera</key>
    <true/>
    <key>com.apple.security.device.print</key>
    <true/>
    <key>com.apple.security.device.usb</key>
    <true/>
    <key>com.apple.security.personal-information.location</key>
    <true/>
  </dict>
</plist>

@tinhnvc-gadget Thank you for your reply, but I don't have the configuration related to signature at present

@TinsFox Code-signing is required before the app can be installed on another MacOS device.
If you have not configured signatures, you will need to remove osxSign and osxNotarize fields.

@TinsFox Code-signing is required before the app can be installed on another MacOS device. If you have not configured signatures, you will need to remove osxSign and osxNotarize fields.

It doesn't work for me. But anyway, thanks a lot!

Please help
For me it throws error when creating .pkg  file
An unhandled rejection has occurred inside Forge:
(The file “user_script.sh” doesn’t exist.)

makers: [
    new MakerSquirrel({ name: productName }),
    new MakerZIP({}, ['darwin']),
    new MakerRpm({}),
    new MakerPKG({

      scripts: './user_script.sh',
    }),
  ],


undefined args.doc.type in resolveParam(args) of validators

After commit 469cf99db04b792b534dd26f8ade4f509edad4dc args.doc.type in resolveParam(args) for maxLength validator (and maybe other validators) is undefined.
(in coffeescript)
ItemsCol = new Mongo.Collection('items')
Item = Astro.Class.create(
	name: 'Item'
	collection: ItemsCol
	secured: true
	# default (untranslated) error messages on server
	resolveError: ((args) -> translateErrorMessage(args)) if Meteor.isClient
	typeField: 'type'
	fields:
		choices:
			type: [Choice]
			default: -> [new Choice, new Choice, new Choice]
			validators: [
				{type: 'minLength', param: 3}
				{type: 'maxLength', resolveParam: (args) -> if args.doc.type is 'Foo' then MAX_CHOICES_NB else 3}
			]
)

Foo = Prem.inherit(
	name: 'Foo'
)

So when creating a new Foo I get:
W20160605-20:25:42.386(2)? (STDERR) /home/laurent/.meteor/packages/meteor-tool/.1.3.2_4.19r443t++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:267
W20160605-20:25:42.386(2)? (STDERR)             				throw(ex);
W20160605-20:25:42.386(2)? (STDERR)             				      ^
W20160605-20:25:42.564(2)? (STDERR) Error: Length of "choices" has to be at most 3 [validation-error]
W20160605-20:25:42.564(2)? (STDERR)     at new _class (packages/mdg:validation-error/validation-error.js:14:12)
W20160605-20:25:42.565(2)? (STDERR)     at throwError (packages/jagi:astronomy/lib/modules/validators/validator.js:63:15)
W20160605-20:25:42.565(2)? (STDERR)     at Validator.validate (packages/jagi:astronomy/lib/modules/validators/validator.js:89:9)
W20160605-20:25:42.565(2)? (STDERR)     at _validators2.default.(anonymous function) (packages/jagi:astronomy/lib/modules/validators/validator.js:101:17)
W20160605-20:25:42.565(2)? (STDERR)     at packages/jagi:astronomy/lib/modules/validators/utils/document_validate.js:125:13
W20160605-20:25:42.565(2)? (STDERR)     at arrayEach (/home/laurent/meteor/myapp/meteor/.meteor/local/isopacks/jagi_astronomy/npm/node_modules/lodash/lodash.js:498:11)
W20160605-20:25:42.565(2)? (STDERR)     at Function.forEach (/home/laurent/meteor/myapp/meteor/.meteor/local/isopacks/jagi_astronomy/npm/node_modules/lodash/lodash.js:8382:11)
W20160605-20:25:42.565(2)? (STDERR)     at packages/jagi:astronomy/lib/modules/validators/utils/document_validate.js:119:9
W20160605-20:25:42.565(2)? (STDERR)     at catchValidationError (packages/jagi:astronomy/lib/modules/validators/utils/document_validate.js:40:7)
W20160605-20:25:42.565(2)? (STDERR)     at packages/jagi:astronomy/lib/modules/validators/utils/document_validate.js:69:28

I don't think that it may have anything to do with this commit. Can you create reproduction?

Well I'm using inheritance and type field disappeared in my objects after that commit. After going back to previous commit with git reset --hard<PHONE_NUMBER>8f65e7992607b25e36677f0fa1469b everything is fine.
Still want me to create reproduction ?

Oh I see. It will be back in the next commit. I was just playing with different type of inheritance however it doesn't work well. I have a different solution which requires the type field to be in a doc.


Use the Builder patch for xhtml

This PR uses the Builder patch to the xhtml library.
Performance comparison was done in a similar manner to the CPS WriterT patch, notes on the xhtml PR.
tl;dr:

12% reduction in memory use for the entire Haddock run
48% reduction in time for the ppHtml phase

While it seems kinda funny to care too much about "oh wow 600ms to 300ms wow wow", we've got some big re-export modules at work that currently take 33 seconds to generate, and ppHtml allocates over 800GB.
EDIT:
Correctness
OK, I've tested the Haddock generation by building haddock with this patch and with the ghc-9.4 branch. The generated HTML is identical, as tested by diff.
Performance
This time I'm using persistent instead of persistent-test because it has fewer steps to get perf output from.
Haddock ghc-9.4
This is built using haddock on the ghc-9.4 branch.
ppHtml: alloc=1134416896 time=380.667
  15,979,133,408 bytes allocated in the heap
   2,437,895,544 bytes copied during GC
     238,259,312 bytes maximum residency (15 sample(s))
       5,391,248 bytes maximum slop
             554 MiB total memory in use (0 MB lost due to fragmentation)

                                     Tot time (elapsed)  Avg pause  Max pause
  Gen  0      3797 colls,     0 par    1.224s   1.226s     0.0003s    0.0031s
  Gen  1        15 colls,     0 par    0.875s   0.876s     0.0584s    0.1627s

  TASKS: 5 (1 bound, 4 peak workers (4 total), using -N1)

  SPARKS: 0 (0 converted, 0 overflowed, 0 dud, 0 GC'd, 0 fizzled)

  INIT    time    0.001s  (  0.000s elapsed)
  MUT     time    4.660s  (  5.192s elapsed)
  GC      time    2.099s  (  2.101s elapsed)
  EXIT    time    0.001s  (  0.007s elapsed)
  Total   time    6.761s  (  7.300s elapsed)

  Alloc rate    3,428,870,682 bytes per MUT second

  Productivity  68.9% of total user, 71.1% of total elapsed

Documentation created:
/home/matt/Projects/persistent/dist-newstyle/build/x86_64-linux/ghc-9.4.3/persistent-<IP_ADDRESS>/doc/html/persistent/index.html

HTML allocations: 1134    MB
HTML time:        380     ms
Total Memory:     554     MB
Total Allocated:  16.0    GB
Max residency:    238     MB
Total Time:       10.888  s

xhtml Builder
ppHtml: alloc=1140800792 time=197.762
  15,973,532,640 bytes allocated in the heap
   2,222,376,616 bytes copied during GC
     195,984,808 bytes maximum residency (14 sample(s))
       5,124,696 bytes maximum slop
             466 MiB total memory in use (0 MB lost due to fragmentation)

                                     Tot time (elapsed)  Avg pause  Max pause
  Gen  0      3727 colls,     0 par    1.203s   1.205s     0.0003s    0.0038s
  Gen  1        14 colls,     0 par    0.662s   0.662s     0.0473s    0.1180s

  TASKS: 5 (1 bound, 4 peak workers (4 total), using -N1)

  SPARKS: 0 (0 converted, 0 overflowed, 0 dud, 0 GC'd, 0 fizzled)

  INIT    time    0.001s  (  0.000s elapsed)
  MUT     time    4.659s  (  5.183s elapsed)
  GC      time    1.865s  (  1.867s elapsed)
  EXIT    time    0.001s  (  0.010s elapsed)
  Total   time    6.526s  (  7.060s elapsed)

  Alloc rate    3,428,220,794 bytes per MUT second

  Productivity  71.4% of total user, 73.4% of total elapsed

Documentation created:
/home/matt/Projects/persistent/dist-newstyle/build/x86_64-linux/ghc-9.4.3/persistent-<IP_ADDRESS>/doc/html/persistent/index.html

Log printed to dist-newstyle/haddock-logs/13:04_2022-04-21_haddock-builder.txt
Used haddock: /home/matt/.cabal/bin/haddock-builder

HTML allocations: 1141    MB
HTML time:        198     ms
Total Memory:     466     MB
Total Allocated:  16.0    GB
Max residency:    195     MB
Total Time:       6.526s   s

Final Performance Comparison:
Comparing these figures, we have:

Haddock Head
xhtml Builder
Absolute Difference
Relative Change

HTML allocations
1134 MB
1141 MB
+7 MB
0.6% worse

HTML time:
380 ms
198 ms
-182 ms
47.9% improvement

Total Memory:
554 MB
466 MB
-88 MB
15.9% improvement

Total Allocated:
16.0 GB
16.0 GB
0
No change

Max residency:
238 MB
195 MB
-43 MB
18.1% improvement

Total Time:
10.88 s
6.526s s
-4.354 s
40% improvement

Pretty pleased with these results.

I can't reproduce the performance, and when checking lately, I can't get this patch to be faster, at all. Going to close this out until I can figure out WTF is going on.


Provid Support for Alterative SourceRef's

I have a controller running that can monitor the source-controller types (Git, OCI, Bucket) for revisions and allowed for third-party transformations (cdk8s, CUE, Dhall, jsonnet).
My plan was to feed this back to FluxCD and allow the kustomize-controller to apply, but unfortunately that isn't possible because of the Kind checks.
I'd like to propose that FluxCD supports external / alternative sources provided they have .status.Artifact that can be deserialised.

There are several ideas around how to support source files other than Kubernetes yaml. We have been internally discussing different avenues on how to enable this, such as introducing a new Artifact API or simply using duck typing to fetch an arbitrary resource that promises to have a .status.artifact.  We want to publish an RFC soon, so that we can start work on this.


Fix invalid type check

typeof value will never be "integer", but will instead be "number" for integers. This fixes the type check, and adds proper assurances that the number is an integer.
This alert was found on LGTM.com, and there are a bunch of other alerts for this project that would probably be good to investigate.
Number.isInteger already has a polyfill added in this repo.
(Full disclosure: I'm part of the team behind LGTM.com)

Ah thanks for catching the typo!

Thank you for your PR. Your project seems very promising. It seems that it has some false positives, e.g. in context2d.js in line 1738 "This definition of textAlign is useless, since its value is never read." but I use it for a function call. But there are some good recommendations, which i will try to implement.

Hi @arasabbasi
Glad you think so! If you like, we also have automated code review that you can enable here: https://lgtm.com/projects/g/MrRio/jsPDF/ci/ This will make sure that alerts like these (and more serious security issues) never get (re)introduced. For example, the AMPHTML project uses that to keep their codebase clean: ampproject/amphtml#13060
As far as the false positive that you point out, I think the message may be a little confusing. It's not saying that the variable is never read from, but what it means is that the assignment specifically is not needed, because it's always reassigned to before being read, so the = 'left' part is unnecessary, and it can just be var textAlign; :)
If you do find anything else that may be a false positive please let me know however, we're keeping track of them as issues here: https://github.com/Semmle/ql/issues

@samlanning
Can you help me to write the lgtm.yaml file, please?

@arasabbasi certainly! What is it that you want to do, is it exclude particular files or queries? An lgtm.yml file is not necessary to correctly analyse your project as it's JavaScript and doesn't require compilation.

I would like e.g. to exclude the folder definetly_typed because that folder is  producing 43 alarms, even though it is not productive code. And spec-folder throws me possibly XSS-warning even though this is not productive code. If I want to add the lgtm-badge to the README.MD I would certainly would like to have an A-rating based on the /src/ folder and not based on all the code in the repo ;).

@arasabbasi I have opened #2414 to address this :)


Added Getter functions to CCPACSPositionings.h

Added Getter functions to CCPACSPositionings.h to make Positionings available via Python Bindings, which is currently not true for classes that store elements using the std::vector<std::unique_prt<TYPE>> and don't provide getter functions that return elements by index.
For further information see  https://github.com/RISCSoftware/cpacs_tigl_gen/issues/59
Description

New Functions:
CCPACSPositionings::GetPositioningCount()
CCPACSPositionings::GetPositioning(int index)

Implements Getter functions manually, as discussed in https://github.com/RISCSoftware/cpacs_tigl_gen/issues/59, to fix missing functionality as described in #936.
Functions returning the type std::vector<std::unique_prt<TYPE>> will still not be available via Python Bindings.
How Has This Been Tested?

Added a test, checking missing functionality described in #936
Checklist:

Task
Finished
Reviewer Approved

At least one test for the new functionality was added.
- [x] yes - [ ] does not apply
- [ ] OK

New classes have been added to the Python interface.
- [ ] yes - [x] does not apply
- [ ] OK

The code is properly documented with doxygen docstrings
- [x] yes - [ ] does not apply
- [ ] OK

Changes are documented at the top of ChangeLog.md
- [x] yes - [ ] does not apply
- [ ] OK

I'd like to add, I formatted some docstrings that were not part of this Issue, since we discussed improving tigls generated documentation by Doxygen.


Add React

See https://github.com/rexxars/react-markdown

This is too heavy a lift for the benefit it gives

I changed my mind! It allows me to keep relevant code together and no pass variables all over.


What's the latest stable release?

Hello, just wondering if 0.17.0 is stable enough to use. The releases page lists 0.16.1 as the latest stable one but there is a 0.17.0 tag. Additionally, 0.18.0alpha0 is now available as a pre-release.
I'm using 0.16.1 without any major issue so I'm just wondering if I can upgrade to 0.17.0 safely or if I should wait until 0.18.0 is released.
I'm particularly interested in the SynthStrip enhancement.
Thanks.

Are you working with infants or seniors? If not then 0.16.1 is going to be the most well-tested release for preprocessing.

This is also unclear to me, I see for instance that v0.18.0alpha0 has been released as the latest release, but if I look at the tagged versions (https://github.com/PennLINC/qsiprep/tags) I see a newer v0.18 version that is not (yet?) released?

I need to figure out how to automate the GitHub releases so they stay synced with DockerHub and PyPI. I just updated GitHub so it includes 0.18.0.

Thanks for your reply. I have been using 0.18 on 5-6 subjects without any issue and with an improved T1 skull stripping, at least visually.


#835 added printing all test environment information

Fixes #835
Test Plan

How do we know the code works?

Use on of a new CLI option to test this PR:

flank firebase test android|ios test-environment or flank android|ios test-environment - print Android|iOS available versions and devices to test against

More listing options of the test environment will be added in the next tasks
Checklist

[x] printing Android software versions and devices list together
[x] printing iOS software versions and devices list together
[x] Documented
[x] Unit tested
[x] release_notes.md updated

$ gcloud firebase test

Available groups for gcloud firebase test:

      android                 Command group for Android application testing.
      ios                     Command group for iOS application testing.
      network-profiles        Explore network profiles available for testing.

$ gcloud firebase test android

Available groups for gcloud firebase test android:

      locales                 Explore Android locales available for testing.
      models                  Explore Android models available in the Test
                              Environment catalog.
      versions                Explore Android versions available for testing.

Available commands for gcloud firebase test android:

      run                     Invoke a test in Firebase Test Lab for Android and
                              view test results.

Flank CLI commands should mirror the gcloud commands. The reason Flank supports the more verbose format: "flank firebase test android test-environment" is so that you can replace "flank" with "gcloud" and get the same result. This also helps simplify testing as we can compare Flank against the reference implementation.
It doesn't look like test-environment has a parallel command in the gcloud CLI tool?

$ gcloud firebase test

Available groups for gcloud firebase test:

      android                 Command group for Android application testing.
      ios                     Command group for iOS application testing.
      network-profiles        Explore network profiles available for testing.

$ gcloud firebase test android

Available groups for gcloud firebase test android:

      locales                 Explore Android locales available for testing.
      models                  Explore Android models available in the Test
                              Environment catalog.
      versions                Explore Android versions available for testing.

Available commands for gcloud firebase test android:

      run                     Invoke a test in Firebase Test Lab for Android and
                              view test results.

Flank CLI commands should mirror the gcloud commands. The reason Flank supports the more verbose format: "flank firebase test android test-environment" is so that you can replace "flank" with "gcloud" and get the same result. This also helps simplify testing as we can compare Flank against the reference implementation.
It doesn't look like test-environment has a parallel command in the gcloud CLI tool?

It does not have similar command for gcloud. This is special for flank :) Cause flank is more than gcloud


Update video_tutorials.md

Thank you @ishitach for the contribution. Appreciate it and looking forward for more :)


tensorflow lite : Convertion from keras works fine but execution on device fails : ByteBuffer is not a valid flatbuffer model

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Google Colaboratory / Android
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: Oneplus 6, Samsung Galaxy s8, ...
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): b'v1.13.0-rc1-2-gb6141b06f5' 1.13.0-rc1 (but also present in 1.12.0)
Firebase ML-Interpreter Version : 16.2.4
Python version: 3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: -
GPU model and memory: -

Describe the current behavior
We want to convert a keras model to a tflite model. Some architectures won't convert (ex: Reshape Layer followed by a BatchNorm layer), but some seem to be able to be converted, but when used on device the error "Caused by: java.lang.IllegalArgumentException: ByteBuffer is not a valid flatbuffer model" happens. Here is a simple model description demonstrating this issue :
Describe the expected behavior
If no errors are encountered when converting to tflite model, we should be able to run them with firebase model interpreter
Code to reproduce the issue
On google Colaboratory create the model :

from tensorflow.keras import Model
from tensorflow.keras.optimizers import Adam
from tensorflow.keras.losses import mse, categorical_crossentropy

state = Input((884,))
mask = Input((260,))

bn = BatchNormalization()(state)
rs1 = Reshape((52, 17))(bn)
lstm1= LSTM((256, unroll=True))(rs1)

policy_raw = Dense(260, activation=sigmoid)(lstm1)
policy_masked = Multiply()([mask, policy_raw])
output_policy = Activation(activation=softmax)(policy_masked)

output_value = Dense(1)(state)

model = Model([state, mask], [output_policy, output_value])
model.compile(optimizer=Adam(), loss=[categorical_crossentropy, mse])

model.save("keras_model.keras")

Convert the model :
from tensorflow.lite.python.lite import TFLiteConverter

path = "keras_model.keras"

converter = TFLiteConverter.from_keras_model_file(path)

tflite_model = converter.convert()

open(path + ".tflite", "wb").write(tflite_model)

Then download the tflite model :
from google.colab import files

files.download(path +'.tflite')

Then try to use the model on Android with tflite through Firebase ML Interpreter :
FirebaseModelInputOutputOptions dataOptions = new FirebaseModelInputOutputOptions.Builder()
                .setInputFormat(0, FLOAT32, new int[]{1, 884})
                .setInputFormat(1, FLOAT32, new int[]{1, 260})
                .setOutputFormat(0, FLOAT32, new int[]{1, 260})
                .setOutputFormat(1, FLOAT32, new int[]{1, 1})
                .build();

final FirebaseLocalModelSource modelSource = new FirebaseLocalModelSource.Builder("asset")
                .setAssetFilePath("keras_model.tflite").build();

FirebaseModelManager.getInstance().registerLocalModelSource(modelSource);

        final FirebaseModelOptions options = new FirebaseModelOptions.Builder()
                .setLocalModelName("asset")
                .build();

FirebaseModelInterpreter interpreter = FirebaseModelInterpreter.getInstance(options);

final FirebaseModelInputs inputs = new FirebaseModelInputs.Builder()
                .add(new float[][]{new float[884]})
                .add(new float[][]{new float[260]})
                .build();

interpreter.run(inputs, dataOptions)
                .continueWith(new Continuation<FirebaseModelOutputs, Object>() {
                    @Override
                    public Object then(@NonNull final Task<FirebaseModelOutputs> task) {
                        try {
                            task.getResult();
                        } catch (final Throwable e) {
                            Log.e("TFLITE", e.getMessage(), e);
                        } finally {
                        }

                        return null;
                    }
                });

You can find a converted model here :
keras_model.zip
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Error log :
com.google.firebase.ml.common.FirebaseMLException: The load task failed
    com.google.android.gms.tasks.RuntimeExecutionException: com.google.firebase.ml.common.FirebaseMLException: The load task failed
        at com.google.android.gms.tasks.zzu.getResult(Unknown Source:15)
        at com.iscoolentertainment.unity.tflite.UnityTFLiteRunner$1.then(UnityTFLiteRunner.java:92)
        at com.google.android.gms.tasks.zzd.run(Unknown Source:5)
        at android.os.Handler.handleCallback(Handler.java:873)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:193)
        at android.app.ActivityThread.main(ActivityThread.java:6863)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
     Caused by: com.google.firebase.ml.common.FirebaseMLException: The load task failed
        at com.google.android.gms.internal.firebase_ml.zzio.zzf(Unknown Source:65)
        at com.google.android.gms.internal.firebase_ml.zzij.call(Unknown Source:2)
        at com.google.android.gms.internal.firebase_ml.zzie.zza(Unknown Source:29)
        at com.google.android.gms.internal.firebase_ml.zzif.run(Unknown Source:2)
        at android.os.Handler.handleCallback(Handler.java:873)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at com.google.android.gms.internal.firebase_ml.zze.dispatchMessage(Unknown Source:5)
        at android.os.Looper.loop(Looper.java:193)
        at android.os.HandlerThread.run(HandlerThread.java:65)
     Caused by: com.google.firebase.ml.common.FirebaseMLException: Local model load failed:
        at com.google.android.gms.internal.firebase_ml.zzje.zza(Unknown Source:127)
        at com.google.android.gms.internal.firebase_ml.zzje.zzgd(Unknown Source:102)
        at com.google.android.gms.internal.firebase_ml.zziq.zzgg(Unknown Source:7)
        at com.google.android.gms.internal.firebase_ml.zziq.call(Unknown Source:23)
        at com.google.android.gms.internal.firebase_ml.zzie.zza(Unknown Source:29)
        at com.google.android.gms.internal.firebase_ml.zzif.run(Unknown Source:2)
        at android.os.Handler.handleCallback(Handler.java:873)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at com.google.android.gms.internal.firebase_ml.zze.dispatchMessage(Unknown Source:5)
        at android.os.Looper.loop(Looper.java:193)
        at android.os.HandlerThread.run(HandlerThread.java:65)
     Caused by: java.lang.IllegalArgumentException: ByteBuffer is not a valid flatbuffer model
        at org.tensorflow.lite.NativeInterpreterWrapper.createModelWithBuffer(Native Method)
        at org.tensorflow.lite.NativeInterpreterWrapper.<init>(NativeInterpreterWrapper.java:74)
        at org.tensorflow.lite.NativeInterpreterWrapper.<init>(NativeInterpreterWrapper.java:54)
        at org.tensorflow.lite.Interpreter.<init>(Interpreter.java:114)
        at com.google.android.gms.internal.firebase_ml.zzje.zzb(Unknown Source:222)
        at com.google.android.gms.internal.firebase_ml.zzjf.zzc(Unknown Source:0)
        at com.google.android.gms.internal.firebase_ml.zzje.zzb(Unknown Source:148)
        at com.google.android.gms.internal.firebase_ml.zzje.zza(Unknown Source:116)
        at com.google.android.gms.internal.firebase_ml.zzje.zzgd(Unknown Source:102)
        at com.google.android.gms.internal.firebase_ml.zziq.zzgg(Unknown Source:7)
        at com.google.android.gms.internal.firebase_ml.zziq.call(Unknown Source:23)
        at com.google.android.gms.internal.firebase_ml.zzie.zza(Unknown Source:29)
        at com.google.android.gms.internal.firebase_ml.zzif.run(Unknown Source:2)
        at android.os.Handler.handleCallback(Handler.java:873)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at com.google.android.gms.internal.firebase_ml.zze.dispatchMessage(Unknown Source:5)
        at android.os.Looper.loop(Looper.java:193)
        at android.os.HandlerThread.run(HandlerThread.java:65)

For information, if we use the model on Google collaboratory, it works fine :

import numpy as np
import tensorflow as tf

# Load TFLite model and allocate tensors.
interpreter = tf.lite.Interpreter(model_path="keras_model.tflite")
interpreter.allocate_tensors()

# Get input and output tensors.
input_details = interpreter.get_input_details()
output_details = interpreter.get_output_details()

# Test model on random input data.
input_shape = input_details[0]['shape']
input_shape_2 = input_details[1]['shape']
input_data = np.array(np.random.random_sample(input_shape), dtype=np.float32)
interpreter.set_tensor(input_details[0]['index'], input_data)
input_data = np.array(np.random.random_sample(input_shape_2), dtype=np.float32)
interpreter.set_tensor(input_details[1]['index'], input_data)

interpreter.invoke()
output_data = interpreter.get_tensor(output_details[0]['index'])
print(output_data)
output_data = interpreter.get_tensor(output_details[1]['index'])
print(output_data)

If we use Firebase ML Model Interpreter 17.0.3 instead of 16.2.4, the error message is gone and I can execute the model, but, the tflite output results are equivalent to the keras or protobuf frozen graph ones.
Here is (in attachment) a slightly different architecture, with the 3 versions (keras, frozen_graph and tflite), the keras one and the frozen graph are consistent, but not the tflite one, no error messages or warnings are issued during conversion.
Thank you in advance for your insights.
conversion_issues.zip

ByteBuffer is not a valid flatbuffer model" happens

The first thing to check is to make sure the .tflite model in your APK is not being compressed.  In gradle, this would be specified as:
aaptOptions {
        noCompress "tflite"
}

ByteBuffer is not a valid flatbuffer model" happens

The first thing to check is to make sure the .tflite model in your APK is not being compressed. In gradle, this would be specified as:
aaptOptions {
        noCompress "tflite"
}

I confirm this was correctly specified and the issue still happened.
The combination Batchnorm, Reshape, LSTM seems to be the culprit here as other model architectures work fine.
Thank you for your answer.

Just curious, have you tried running this model directly against the Android TFLite SDK? Trying to rule out whether this is perhaps a versioning issues between MLKit and TFLite.

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 44 days with no activity and the awaiting response label was assigned. Is this still an issue?

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Including speaker management to control the output source for an Audio file

This is not an issue, could possibly be a good enhancement. The ability to control the output source of sound. Sometimes I might require the sound to be played through the Earpiece of the phone instead of the primary speaker. I have a similar requirement and I have to use a different Library just for speaker modes.
Thanks in advance, great job with the repo guys. 👍

Can you give examples on use cases that this might be useful?

@Guichaguri Lets consider a user who wants to listen to a private Audio message. User would just use a button to switch to earpiece mode and listen to the message without anyone else knowing about it, no need to attach earphones.

Is the speaker management available on the latest build?
if yes, how can I use it?


STAN negative test report

For more information see the link below.
https://github.com/ballerina-platform/ballerina-standard-library/blob/main/docs/library-development-process.md#negative-test-report

Closing this since STAN module is deprecated and will be discontinued.
Ref: https://github.com/nats-io/nats-streaming-server#warning--deprecation-notice-warning


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1605 ms

Resolved: Bofrost.at performance has improved in e4c64b1.


React Router nesting reloads page

This is a copy of my SO question - https://stackoverflow.com/questions/59136493/react-router-nesting-reloads-page

I'm trying to set up nested routes in React using React Router so that the nested components load directly, however the page reloads when I attempt to go to a nested route.
Even the official example does the same - https://reacttraining.com/react-router/web/example/nesting
One thing I noticed was that if I actually change the route from within one of the child route components the page does not reload. But this is bad practice and I want to change the route in the component that defines the routes.
Has something changed recently? How can I achieve nested routes changes without page reload?
Parent
import { BrowserRouter as Router, Route, Switch } from "react-router-dom";

// At route /home
const Parent = (props: RouteComponentProps<any>) => {
  const changeRoute = () => {
    props.history.push('/home/test'); // Reloads page
  };

  return (
    <Router>
      <Switch>
        <Route component={Test} path="/home/test" />
        <Route component={Default} />
      </Switch>
      <button onClick={changeRoute}>Click</button>
    </Router>
  );
};

export default withRouter(Parent);

Child
const Default = (props: RouteComponentProps<any>) => {
  const changeRoute = () => {
    props.history.push('/home/test'); // Does not reload page
  };

  return (
    <button onClick={changeRoute}>Click</button>
  );
};

export default withRouter(Default);

I'm using react-router-dom v5.1.2.

Even the official example does the same - https://reacttraining.com/react-router/web/example/nesting

Note that the page is only refreshing in the designer. if you view the sample using "open in new window" this is working as expected.

@gpltaylor Thanks. Can you see anything in my example code that could be wrong?

The problem was that I was using  in Parent even though Parent was itself within  tags. Replacing  with  in Parent fixed the issue.


Use yarn in CI

Connected to https://github.com/rangle/rangle-starter/issues/189

@watrool any update on this?

@winkerVSbecks no updates from my side.

@SethDavenport Just update this PR with the official way to enable yarn on circle CI, and I also restored the e2e test part (to be same as the master)

:shipit:


Problem installing dlib with cocoapods (iOS, XCode 9.1, iOS 11.1)

I have some problem with install dlib with pods . On previous version of XCode (9.0.1) this is worked fine, but after update (XCode 9.1) I have this problem.
Podfile
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '9.0'

target 'ExampleProject' do
     pod 'OpenCV', '~> 3.3'
     pod 'dlib', '~> 19.4'
end

List of my actions.

created new xcode project (target ios 9.0) with new Podfile
write "pod install" in terminal
after delay I see a lot of red text

I think the error is in this, it's problem with new version of iOS/Xcode or something like that
Check dependencies
warning: iOS 11.1.0 does not support armv7
warning: iOS 11.1.0 does not support armv7s

I tried change target version to 11.1, install lib pod to other project - it does not change anything. Other installations on cocoapods (like opencv/gpuimage/afnetworking and some others) works fine.
Full list of Terminal Output:
pod install
Analyzing dependencies
Downloading dependencies
Using OpenCV (3.3.1)
Installing dlib (19.4)
[!] /bin/bash -c
set -e
mkdir build
cd build
cmake -Wno-dev -GXcode -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_FLAGS="-DPNG_ARM_NEON_OPT=0 -std=c++11" -DCMAKE_C_FLAGS="-DPNG_ARM_NEON_OPT=0" -DCMAKE_CXX_COMPILER_WORKS=1 -DCMAKE_C_COMPILER_WORKS=1 -DCMAKE_THREAD_LIBS_INIT="-lpthread" -DCMAKE_USE_PTHREADS_INIT=1 -DCMAKE_OSX_ARCHITECTURES="armv7 armv7s arm64" -DCMAKE_OSX_SYSROOT=$(xcode-select -p)/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk -DCMAKE_MACOSX_BUNDLE=ON -DCMAKE_XCODE_ATTRIBUTE_CODE_SIGNING_REQUIRED=NO -DLIBPNG_IS_GOOD=0 -DLIBJPEG_IS_GOOD=0 -DAPPLE=1 -DDLIB_NO_GUI_SUPPORT=1 -DDLIB_USE_CUDA=0 -DDLIB_USE_BLAS=0 -DDLIB_USE_LAPACK=0 -DUNIX=1 ../
CMAKE_VERSION=`cmake --version | tr -dc '0-9'`
if [ $CMAKE_VERSION -lt 300 ]; then sed -i '' 's~/build/dlib/Release~/build/dlib/Release-iphoneos~g' dlib/CMakeScripts/dlib_shared_postBuildPhase.makeRelease; fi
xcodebuild -arch armv7 -arch armv7s -arch arm64 -sdk iphoneos -configuration Release ONLY_ACTIVE_ARCH=NO -target ALL_BUILD build
xcodebuild -arch x86_64 -arch i386 -sdk iphonesimulator -configuration Release ONLY_ACTIVE_ARCH=NO -target ALL_BUILD build
sed -i '' 's~/build/dlib/Release~/build/dlib/Release-iphoneos~g' dlib/cmake_install.cmake
cmake -DCMAKE_INSTALL_PREFIX=install -P cmake_install.cmake
lipo -create install/lib/libdlib.19.4.0.dylib dlib/Release-iphonesimulator/libdlib.19.4.0.dylib -output libdlib.dylib
install_name_tool -id @rpath/libdlib.dylib libdlib.dylib

-- The C compiler identification is AppleClang <IP_ADDRESS>00038
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00038
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Detecting C compile features
-- Detecting C compile features - failed
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Detecting CXX compile features
-- Detecting CXX compile features - failed
-- Building a C++11 test project to see if your compiler supports C++11
-- C++11 activated.
-- Looking for pthread.h
-- Looking for pthread.h - not found
-- Found Threads: TRUE
-- Searching for BLAS and LAPACK
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.29.2")
-- Checking for module 'cblas'
--   No package 'cblas' found
-- Checking for module 'lapack'
--   No package 'lapack' found
-- Looking for sys/types.h
-- Looking for sys/types.h - not found
-- Looking for stdint.h
-- Looking for stdint.h - not found
-- Looking for stddef.h
-- Looking for stddef.h - not found
-- Check size of void*
-- Check size of void* - failed
-- Found LAPACK library
-- Found CBLAS library
-- Looking for cblas_ddot
-- Looking for cblas_ddot - not found
-- BLAS library does not have cblas symbols, so dlib will not use BLAS or LAPACK
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build
Build settings from command line:
    ARCHS = armv7 armv7s arm64
    ONLY_ACTIVE_ARCH = NO
    SDKROOT = iphoneos11.1

=== BUILD TARGET dlib OF PROJECT Project WITH CONFIGURATION Release ===

Check dependencies
warning: iOS 11.1.0 does not support armv7
warning: iOS 11.1.0 does not support armv7s

Write auxiliary files
/bin/mkdir -p /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7s
write-file /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7s/dlib.LinkFileList
/bin/mkdir -p /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7
write-file /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/dlib.LinkFileList
/bin/mkdir -p /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/arm64
write-file /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/arm64/dlib.LinkFileList

CompileC build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/base64_kernel_1.o dlib/base64/base64_kernel_1.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
    cd /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328
    export LANG=en_US.US-ASCII
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/ruslan/anaconda/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch armv7 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -Wno-trigraphs -fpascal-strings -O3 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wno-unused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wno-float-conversion -Wno-non-literal-null-conversion -Wno-objc-literal-conversion -Wno-shorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DCMAKE_INTDIR=\"Release-iphoneos\" -DDLIB_JPEG_STATIC -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.1.sdk -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -miphoneos-version-min=11.1 -Wno-sign-conversion -Wno-infinite-recursion -Wno-move -Wno-comma -Wno-block-capture-autoreleasing -Wno-strict-prototypes -Wno-range-loop-analysis -fembed-bitcode-marker -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Release-iphoneos/include -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/libpng -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/zlib -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/DerivedSources/armv7 -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/DerivedSources -Wmost -Wno-four-char-constants -Wno-unknown-pragmas -F/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Release-iphoneos -F/Library/Frameworks -DPNG_ARM_NEON_OPT=0 -std=c++11 -DDLIB_NO_GUI_SUPPORT -DDLIB_DISABLE_ASSERTS -DDLIB_JPEG_SUPPORT -DDLIB_PNG_SUPPORT -DNDEBUG -std=gnu++11 -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/libpng -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/zlib -F/Library/Frameworks -MMD -MT dependencies -MF /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/base64_kernel_1.d --serialize-diagnostics /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/base64_kernel_1.dia -c /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/base64/base64_kernel_1.cpp -o /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/base64_kernel_1.o
clang: error: invalid iOS deployment version '-miphoneos-version-min=11.1', iOS 10 is the maximum deployment target for 32-bit targets [-Winvalid-ios-deployment-target]

CompileC build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_2.o dlib/bigint/bigint_kernel_2.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
    cd /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328
    export LANG=en_US.US-ASCII
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/ruslan/anaconda/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch armv7 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -Wno-trigraphs -fpascal-strings -O3 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wno-unused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wno-float-conversion -Wno-non-literal-null-conversion -Wno-objc-literal-conversion -Wno-shorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DCMAKE_INTDIR=\"Release-iphoneos\" -DDLIB_JPEG_STATIC -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.1.sdk -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -miphoneos-version-min=11.1 -Wno-sign-conversion -Wno-infinite-recursion -Wno-move -Wno-comma -Wno-block-capture-autoreleasing -Wno-strict-prototypes -Wno-range-loop-analysis -fembed-bitcode-marker -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Release-iphoneos/include -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/libpng -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/zlib -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/DerivedSources/armv7 -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/DerivedSources -Wmost -Wno-four-char-constants -Wno-unknown-pragmas -F/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Release-iphoneos -F/Library/Frameworks -DPNG_ARM_NEON_OPT=0 -std=c++11 -DDLIB_NO_GUI_SUPPORT -DDLIB_DISABLE_ASSERTS -DDLIB_JPEG_SUPPORT -DDLIB_PNG_SUPPORT -DNDEBUG -std=gnu++11 -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/libpng -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/zlib -F/Library/Frameworks -MMD -MT dependencies -MF /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_2.d --serialize-diagnostics /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_2.dia -c /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/bigint/bigint_kernel_2.cpp -o /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_2.o
clang: error: invalid iOS deployment version '-miphoneos-version-min=11.1', iOS 10 is the maximum deployment target for 32-bit targets [-Winvalid-ios-deployment-target]

CompileC build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_1.o dlib/bigint/bigint_kernel_1.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
    cd /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328
    export LANG=en_US.US-ASCII
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/ruslan/anaconda/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch armv7 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -Wno-trigraphs -fpascal-strings -O3 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wno-unused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wno-float-conversion -Wno-non-literal-null-conversion -Wno-objc-literal-conversion -Wno-shorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DCMAKE_INTDIR=\"Release-iphoneos\" -DDLIB_JPEG_STATIC -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.1.sdk -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -miphoneos-version-min=11.1 -Wno-sign-conversion -Wno-infinite-recursion -Wno-move -Wno-comma -Wno-block-capture-autoreleasing -Wno-strict-prototypes -Wno-range-loop-analysis -fembed-bitcode-marker -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Release-iphoneos/include -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/libpng -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/zlib -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/DerivedSources/armv7 -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/DerivedSources -Wmost -Wno-four-char-constants -Wno-unknown-pragmas -F/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Release-iphoneos -F/Library/Frameworks -DPNG_ARM_NEON_OPT=0 -std=c++11 -DDLIB_NO_GUI_SUPPORT -DDLIB_DISABLE_ASSERTS -DDLIB_JPEG_SUPPORT -DDLIB_PNG_SUPPORT -DNDEBUG -std=gnu++11 -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/libpng -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/zlib -F/Library/Frameworks -MMD -MT dependencies -MF /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_1.d --serialize-diagnostics /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_1.dia -c /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/bigint/bigint_kernel_1.cpp -o /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_1.o
clang: error: invalid iOS deployment version '-miphoneos-version-min=11.1', iOS 10 is the maximum deployment target for 32-bit targets [-Winvalid-ios-deployment-target]

CompileC build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bit_stream_kernel_1.o dlib/bit_stream/bit_stream_kernel_1.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
    cd /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328
    export LANG=en_US.US-ASCII
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/ruslan/anaconda/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch armv7 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -Wno-trigraphs -fpascal-strings -O3 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wno-unused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wno-float-conversion -Wno-non-literal-null-conversion -Wno-objc-literal-conversion -Wno-shorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DCMAKE_INTDIR=\"Release-iphoneos\" -DDLIB_JPEG_STATIC -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.1.sdk -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -miphoneos-version-min=11.1 -Wno-sign-conversion -Wno-infinite-recursion -Wno-move -Wno-comma -Wno-block-capture-autoreleasing -Wno-strict-prototypes -Wno-range-loop-analysis -fembed-bitcode-marker -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Release-iphoneos/include -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/libpng -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/zlib -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/DerivedSources/armv7 -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/DerivedSources -Wmost -Wno-four-char-constants -Wno-unknown-pragmas -F/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Release-iphoneos -F/Library/Frameworks -DPNG_ARM_NEON_OPT=0 -std=c++11 -DDLIB_NO_GUI_SUPPORT -DDLIB_DISABLE_ASSERTS -DDLIB_JPEG_SUPPORT -DDLIB_PNG_SUPPORT -DNDEBUG -std=gnu++11 -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/libpng -I/Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/external/zlib -F/Library/Frameworks -MMD -MT dependencies -MF /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bit_stream_kernel_1.d --serialize-diagnostics /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bit_stream_kernel_1.dia -c /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/dlib/bit_stream/bit_stream_kernel_1.cpp -o /Users/ruslan/Library/Caches/CocoaPods/Pods/Release/dlib/19.4-4d328/build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bit_stream_kernel_1.o
clang: error: invalid iOS deployment version '-miphoneos-version-min=11.1', iOS 10 is the maximum deployment target for 32-bit targets [-Winvalid-ios-deployment-target]

 *****************************************************************************
 *** No BLAS library found so using dlib's built in BLAS.  However, if you ***
 *** install an optimized BLAS such as OpenBLAS or the Intel MKL your code ***
 *** will run faster.  On Ubuntu you can install OpenBLAS by executing:    ***
 ***    sudo apt-get install libopenblas-dev liblapack-dev                 ***
 *** Or you can easily install OpenBLAS from source by downloading the     ***
 *** source tar file from http://www.openblas.net, extracting it, and      ***
 *** running:                                                              ***
 ***    make; sudo make install                                            ***
 *****************************************************************************
2017-11-15 16:40:30.551 xcodebuild[6142:57435] [MT] PluginLoading: Required plug-in compatibility UUID C3998872-68CC-42C2-847C-B44D96AB2691 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/RTImageAssets.xcplugin' not present in DVTPlugInCompatibilityUUIDs
2017-11-15 16:40:30.551 xcodebuild[6142:57435] [MT] PluginLoading: Required plug-in compatibility UUID C3998872-68CC-42C2-847C-B44D96AB2691 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Alcatraz.xcplugin' not present in DVTPlugInCompatibilityUUIDs
** BUILD FAILED **

The following build commands failed:
	CompileC build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/base64_kernel_1.o dlib/base64/base64_kernel_1.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
	CompileC build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_2.o dlib/bigint/bigint_kernel_2.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
	CompileC build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bigint_kernel_1.o dlib/bigint/bigint_kernel_1.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
	CompileC build/dlib/Project.build/Release-iphoneos/dlib.build/Objects-normal/armv7/bit_stream_kernel_1.o dlib/bit_stream/bit_stream_kernel_1.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
(4 failures)

I've never heard of CocoaPods, but it seems pretty obvious that they have
messed up the dlib package.  You should get dlib from dlib.net.  Use the
official version and it will probably work fine.

I have used instruction on this post to build dlib on iOS. It has worked for me(but on iOS10). I am guessing it works for iOS11 too. Give it a try.

Thanks for the answers, I followed your recommendations and it helped me.

Hey @LamkoGithub , did you find any other solutions for this kind of problems?
Do we need to build the lib mannually instead of just using "pod 'dlib'" ?
Thanks.


Add French Translation

This PR adds French translation in the config flow.

Thanks 👍
I added credit to you in the README.


Filter out games that I commented on

I would like to be able to enter my username (or user id) so that I don't have to see all the games that I already commented on. Otherwise, I'll keep seeing the same games over and over again and it'll be hard to find something new.

Yep this would be very useful, especially for MiniLDs and very active commenters in general.
I guess the most simple yet performant approach would be to add a new search field with Select2 + a small web service for auto-completion (relevant SO).
Bonus: Maybe we could put that user selection in the header instead, to make it look like a login form ("view as"?), then remember that info in the session/cookie. OTOH it might not be worth trying too hard: for large events very little users rate more than 10% of the games, so the chances we'd see the same games again and again should be low enough for most people.

But if somebody (especially a large Jam team) is very active with rating, they'll continue to be at the top. It takes just a dozen of such teams to make the entire site less usable. So I think this might be important and am going to start implementing it now, exactly the way you suggest, except not putting it in the header (yet) because the header looks so nice and balanced currently :)

Note that I introduced an extra index (useful even if no username is specified), so you might want to rerun install.php for representative performance.

Excellent work! I just updated the sources on the live site.

But if somebody (especially a large Jam team) is very active with rating, they'll continue to be at the top. It takes just a dozen of such teams to make the entire site less usable.

True, I didn't think about that. I'm now wondering wondering whether we should tweak the coolness formula to favor the games with few comments over the very active commenters... Issue incoming.


style:--20220303 use the figure tag for images in CONTRIBUTION.md

Related Issue
Follow: #117
Propose changes
Using the figure tag for images instead of the markdown element in CONTRIBUTION.md
Additional information
NULL
Checklist

[x] update all images in CONTRIBUTION.md

Screenshoot
NULL

Some problems exist


Fix: None type error when invoking Workflow object manually

Description
After updating snakemake to its current version, the following code fails with TypeError: 'NoneType' object is not iterable:
workflow = Workflow(snakefile=snakefile)

This PR attempts to fix that issue.
QC

[x] The PR contains a test case for the changes or the changes are already covered by an existing test case.
[ ] The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

@johanneskoester could you please review / merge this PR?

@johanneskoester Any updates on this?
This bug is really annoying but also easily fixed by this PR...


edit to readme.md

James,
Next time I will have learnt more about github but meanwhile here are a couple of edits for readme.md:
Line 72: change status to static
Line 75: change DisplayAnythingVideoGallery to DisplayAnythingYouTubeGallery
Line 93: change FeatureImage to SomeImage
I'm using the code straight from the read me and I'm now getting the admin page to load but only getting the "Loading uploader..." message so far. I'm travelling for the rest of the week so may not get a chance to sort out my last bugs till next week. If they can be addressed with updates to the documentation, I'll let you know.
Congratulations on this module. Its exactly what I was looking for - no dependancies on other modules and I can implement my own front end without having to hack existing code.
cheers
bruce

Thanks Bruce, just pushed an update to readme.md
Graphical diff is here:
https://github.com/codem/DisplayAnything/commit/75edc38f3b4f12534745696e6867ee048a8d9e11

James,
Now for the next issue. When I create a gallery page, I get the Gallery, Image and Video tabs OK but the Loading Uploader... message never goes away. Looking at the html shows why:
Loading uploader...
The GetUploaderConfiguration returns that long string filled with " which, presumably, should trigger the javascript but fails to do so.
Any suggestions as to where to go next to get it working?
cheers
Bruce Bowden
Frogmouth Communications
40 Blackburn St, Bittern, Vic 3918
ph: 03 5983 0428
mobile: 0402 339 550
http://frogmouth.com.au/
On 09/01/2012, at 4:35 PM, James wrote:

Thanks Bruce, just pushed an update to readme.md
Graphical diff is here:
https://github.com/codem/DisplayAnything/commit/75edc38f3b4f12534745696e6867ee048a8d9e11

Reply to this email directly or view it on GitHub:
https://github.com/codem/DisplayAnything/issues/3#issuecomment-3407544

The rel attribute carries around some JSON encode information about the gallery.
Have you pulled the latest version from Github ? looks like some JS is not being fired. Try clearing your cache and reloading.
Also, what browser is this appearing in?

see Issue #5


reserved identifier violation

I would like to point out that an identifier like "__clmulhalfscalarproductwithoutreduction" does eventually not fit to the expected naming convention of the C language standard.
Would you like to adjust your selection for unique names?

@elfring
If you issue a PR to fix this, I will be happy to merge it.