First run of container always exits with status 135 on Mac OS X 10.11.6 (El Capitan)

When starting a container for the very first time, it always exits with status 135.
If you bring the container down and then up again, it'll be fine.
Creating network "actordbfordocker_default" with the default driver
Creating actordbfordocker_actordb-server-1_1
Creating actordbfordocker_actordb-server-3_1
Creating actordbfordocker_actordb-server-2_1
Ians-MBP:actordb-for-docker ian$ docker-compose ps
               Name                             Command               State     Ports
-------------------------------------------------------------------------------------
actordbfordocker_actordb-server-1_1   dumb-init actordb foreground   Exit 135
actordbfordocker_actordb-server-2_1   dumb-init actordb foreground   Exit 135
actordbfordocker_actordb-server-3_1   dumb-init actordb foreground   Exit 135
Ians-MBP:actordb-for-docker ian$ docker-compose logs
Attaching to actordbfordocker_actordb-server-2_1, actordbfordocker_actordb-server-3_1, actordbfordocker_actordb-server-1_1
actordb-server-2_1  | config is OK
actordb-server-2_1  | -config /etc/actordb/app.config -args_file /etc/actordb/vm.args -vm_args /etc/actordb/vm.args
actordb-server-2_1  | Exec:  /usr/lib/actordb/erts-7.2/bin/erlexec -boot /usr/lib/actordb/releases/0.10.22/actordb               -config /etc/actordb/app.config -args_file /etc/actordb/vm.args -vm_args /etc/actordb/vm.args              -pa /usr/lib/actordb/lib/actordb-patches -noshell -- foreground
actordb-server-2_1  | Root: /usr/lib/actordb
actordb-server-3_1  | config is OK
actordb-server-2_1  | [os_mon] memory supervisor port (memsup): Erlang has closed
actordb-server-3_1  | -config /etc/actordb/app.config -args_file /etc/actordb/vm.args -vm_args /etc/actordb/vm.args
actordb-server-2_1  | [os_mon] cpu supervisor port (cpu_sup): Erlang has closed
actordb-server-3_1  | Exec:  /usr/lib/actordb/erts-7.2/bin/erlexec -boot /usr/lib/actordb/releases/0.10.22/actordb               -config /etc/actordb/app.config -args_file /etc/actordb/vm.args -vm_args /etc/actordb/vm.args              -pa /usr/lib/actordb/lib/actordb-patches -noshell -- foreground
actordb-server-3_1  | Root: /usr/lib/actordb
actordb-server-3_1  | [os_mon] cpu supervisor port (cpu_sup): Erlang has closed
actordb-server-3_1  | [os_mon] memory supervisor port (memsup): Erlang has closed
actordb-server-1_1  | config is OK
actordb-server-1_1  | -config /etc/actordb/app.config -args_file /etc/actordb/vm.args -vm_args /etc/actordb/vm.args
actordb-server-1_1  | Exec:  /usr/lib/actordb/erts-7.2/bin/erlexec -boot /usr/lib/actordb/releases/0.10.22/actordb               -config /etc/actordb/app.config -args_file /etc/actordb/vm.args -vm_args /etc/actordb/vm.args              -pa /usr/lib/actordb/lib/actordb-patches -noshell -- foreground
actordb-server-1_1  | Root: /usr/lib/actordb
actordb-server-1_1  | [os_mon] memory supervisor port (memsup): Erlang has closed
actordb-server-1_1  | [os_mon] cpu supervisor port (cpu_sup): Erlang has closed

Nothing is written to the console.log, crash.log, error.log or sasl-error.log files.

Experiments on different versions of macOS and Linux didn't suffer from the "Exit 135" problem, so it looks like might be an issue either with Mac OS X 10.11.6, or just my MacBook Pro.

Finally found the cause!
It seems to be that if you run the container with the /var/lib/actordb volume mounted somewhere within a Dropbox folder, it'll "Exit 135" when creating the lmdb and lmdb-lock files.
Not something my container or ActorDB can possibly ever address.
Just don't mount the container's /var/lib/actordb volume into a Dropbox folder, even during development!


issue #1084

Simplest change that leaves the field available for future text insertions. Translations will propagate automatically via Weblate

Thanks, @mariehuynh!


Sorting algorithm added

Bubble Sort,
Selection Sort,
Insertion sort added

@saransh79  Please add hacktoberfest-accepted label to this  PR.


Add recipe, patch

wasmtime-py 11.0.0
upstream

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:22: patch_must_be_in_build: patch must be in build when source/patches is set.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:22: patch_must_be_in_build: patch must be in build when source/patches is set.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:22: patch_must_be_in_build: patch must be in build when source/patches is set.
Errors were found


[tsserver] add support to fetch symbol references from only the current file.

🔍 Search Terms
Hey.
it will be awesome if the "references" command can only get references of a symbol at position (x,y) but only inside the current file.
✅ Viability Checklist

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
this can be added using currentFileOnly?: boolean; (like that inside interface NavtoRequestArgs).
📃 Motivating Example
i use it mainly for rewriting javascript files (usually obfuscated ones), so for each symbol i need to get all references but only for the currently opened file, so i wish there was a flag for it. as i thought it will be more performant (i.e. instead of searching references all across the project, if we restricted it to the current file - by a flag in a the request - then it can be more performant due to reduced search space?)
💻 Use Cases

What do you want to use this for?

rewriting js files accurately.

What shortcomings exist with current approaches?

performance issues.

What workarounds are you using in the meantime?

requesting references then filtering them if the ref['file'] key is the same as that supplied in references request. however, i think tsserver can be more performant than this approach.

The "document highlights" API may be what you want


.NET MAUI C# API Changes -> create Analyzers + Code fixes

Breaking up tasks from https://github.com/dotnet/upgrade-assistant/issues/590
Remaining work :
Color.[NamedColor] -> Microsoft.Maui.Colors.[NamedColor]
Color API Changes: https://gist.github.com/hartez/593fc3fb87035a3aedc91657e9c15ab3
Shapes, Point -> add using Microsoft.Maui.Graphics;
Colors follow up on BlueViolet if removed or back

This was done.


buggy BLS depths

The following tarball has a minimal working example (with dependencies from pipe-trex, + the lightcurves used):
bls_example.tar.gz
The BLS implementation from kbls seems to be doing a couple wonky things.

sometimes, the returned transit depth seems to sometimes have the wrong sign, e.g., for WASP-29b attached
other times (more frequently), the returned depth seems to be systematically too small.

The work-around I've been using for fast transit model-fitting has been to use the BLS period as an initial guess to fit trapezoidal models. This seems to produce robust depths.
However both (1) and (2) above are important to fix. (1) for obvious reasons, (2) because it affects the depths we measure, and thus the measured SNR of peaks.
WASP-4:

WASP-5:

WASP-29:

"""
example showing odd BLS behavior.
"""
import numpy as np
from lcstatistics import read_tfa_lc
from astrobase.periodbase import kbls
from astrobase.varbase import lcfit

##########################################
# change things below here

### WASP-29b: fails with transit depth NEGATIVE.
tfalcfile, plname = 'HAT-633-0000416.tfalc', 'WASP-29b'
### WASP-5b: seems ok, but depth is smaller than expected
#tfalcfile, plname = 'HAT-678-0001318.tfalc', 'WASP-5b'
### WASP-4b: seems ok, but depth is smaller than expected
#tfalcfile, plname = 'HAT-717-0001830.tfalc', 'WASP-4b'

# change things above here
##########################################

lc = read_tfa_lc(tfalcfile)

time = lc['btjd']
mag = lc['TF1']
err_mag = lc['RMERR1'] # raw mag err same as TFA mag err

# these zero-points do not matter; we care about relative flux. for the error
# transformation, note
#   sigma_flux = dg/d(mag) * sigma_mag, for g=f0 * 10**(-0.4*(mag-mag0)).
mag_0 = 10
flux_0 = 1000
flux = flux_0 * 10**(-0.4 * (mag - mag_0))
err_flux = np.abs(
    -0.4 * np.log(10) * flux_0 * 10**(-0.4*(mag-mag_0)) * err_mag
)

fluxmedian = np.nanmedian(flux)
flux /= fluxmedian
err_flux /= fluxmedian

# fit BLS model; plot resulting phased LC.
endp = 1.05*(np.nanmax(time) - np.nanmin(time))/2
nworkers=8
blsdict = kbls.bls_parallel_pfind(time, flux, err_flux,
                                  magsarefluxes=True, startp=0.1,
                                  endp=endp, maxtransitduration=0.15,
                                  nworkers=nworkers, sigclip=None)
fitd = kbls.bls_stats_singleperiod(time, flux, err_flux,
                                   blsdict['bestperiod'],
                                   maxtransitduration=0.15,
                                   magsarefluxes=True, sigclip=None,
                                   perioddeltapercent=5)

blsfit_savfile = '{}_bls_buggy.png'.format(plname)
lcfit._make_fit_plot(fitd['phases'], fitd['phasedmags'], None,
                     fitd['blsmodel'], fitd['period'], fitd['epoch'],
                     fitd['epoch'], blsfit_savfile, magsarefluxes=True)

I think the problem might lie in how eebls.f handles positive vs negative transit depths based on a quick look at its source. I'll look into it a bit more soon.
In the meantime, I've implemented Astropy's BoxLeastSquares functions in periodbase.abls, using an identical API to the existing periodbase.kbls.bls_{serial,parallel}_pfind functions. These only work for Astropy >= 3.1 (and Python >= 3). Still working out some bugs in there and have yet to implement the SNR functions similar to periodbase.kbls, but it should be OK to play with for the time being.

These are tests of the data above with the newest kbls.bls_stats_singleperiod, which uses lcfit.traptransit_fit_magseries to fit a trapezoid transit and get a better estimate of the depth, duration, etc. that way.
import numpy as np
import pandas as pd
from astrobase.periodbase import kbls
from astrobase.varbase import lcfit

lc = pd.read_csv('waspXX-lc.tfalc',delim_whitespace=True,header=None)
times, mags, errs = np.array(lc[0]), np.array(lc[30]), np.array(lc[15])
blsres = kbls.bls_parallel_pfind(times,mags,errs,sigclip=None,maxtransitduration=0.2,magsarefluxes=False)
stats = kbls.bls_stats_singleperiod(times,mags,errs,blsres['bestperiod'],ingressdurationfraction=0.1,sigclip=None,maxtransitduration=0.2,magsarefluxes=False)
lcfit._make_fit_plot(stats['phases'], stats['phasedmags'], None,
                     stats['blsmodel'], stats['period'], stats['epoch'],
                     stats['epoch'], 'waspXX.png', magsarefluxes=False, wrap=True)

I think for WASP29, eebls.f is being thrown off by sinusoidal variability. I'm not sure if it checks for always fainter transit features, so that's one thing to look into. For the other ones, the new stats function appears to work correctly now.
Using mags:
WASP4

WASP5

WASP29

Checking with fluxes now and using magsarefluxes=True as appropriate:
WASP4

WASP5

WASP29

It's a bit of work, but prewhitening the LC makes the BLS fit correct:
from astrobase.varbase import signals

# mask out the transit first
masked = signals.mask_signal(times,mags,errs,blsres['bestperiod'],1364.21365,maskphaselength=0.05,sigclip=None,maskphases=[0.0,1.0], plotfit='masked.png')

# fourier fit the remaining signal
ffit = lcfit.fourier_fit_magseries(masked['mtimes'],masked['mmags'],masked['merrs'],stats['period'],fourierorder=2,plotfit='ffit.png')

# prewhiten using the fit period and fourier params
whitened = signals.prewhiten_magseries(times,mags,errs,stats['period'],ffit['fitinfo']['finalparams'],sigclip=None,plotfit='whitened.png')

Then running bls_stats_singleperiod works correctly:
stats = kbls.bls_stats_singleperiod(whitened['wtimes'],whitened['wmags'],whitened['werrs'],blsres['bestperiod'],ingressdurationfraction=0.1,sigclip=None,maxtransitduration=0.2,magsarefluxes=False,perioddeltapercent=10)
lcfit._make_fit_plot(stats['phases'], stats['phasedmags'], None,stats['blsmodel'], stats['period'], stats['epoch'],stats['epoch'], 'wasp29-whitened.png', magsarefluxes=False, wrap=True)

Nice! Thank you for looking closely through these examples.
I agree that once the period is known, measuring the SNR using the trapezoidal model is a good patch. However for purposes of period-finding, it would be best if the power of BLS periodogram was a good measurement of the best-fitting SNR. (Which requires a decent depth and duration match).
DFM's astropy BLS (as you've wrapped in abls) solves the period-finding problem, because its depths aren't too shallow (these plots). But it has speed problems that we discussed on Friday.
A hitherto unmentioned BLS implementation that solves both the period-finding problem and the speed problem is the VARTOOLS implementation. For my own need to run BLS on many lightcurves, I might just opt for this. But this isn't an astrobase-internal solution.
One solution would be to deprecate kbls in favor of abls in some future release.
Another is to find & understand whatever is causing the shallow depths from eebls.f.
A final one (perhaps coupled with kbls deprecation) would be to add VARTOOLS TFA as a dependency.
It's surprising to me that the eebls.f & astropy BLS results are qualitatively so different. Suggests there's really something different happening in the implementations!

periodbase.kbls now uses scipy.optimize.curve_fit to do its trapezoid transit fits and can use parameter bounds to make sure the fit makes sense for mags vs. flux, ingress duration vs. total transit duration, etc. This appears to fix the problem encountered in the WASP29 fit above when kbls.get_stats_singleperiod is called or kbls.bls_parallel_pfind is called with get_stats=True without having to resort to additional trickery.


Non-optional direct dependency resolved as optional

context: https://github.com/lihaoyi/mill/issues/185
coursier 1.0.2
We have a private nexus repository
I try to look up the following:
val dep = Dependency(Module("my.company", "foo_2.12"), "6.1.1", optional = false)

But after resolution
resolution.artifacts(true).foreach{ a =>
    println(s"${a.url} optional=${a.isOptional}")
}

prints
https://nexus.company.com/repository/maven-releases/my/company/foo_2.12/6.1.1/foo_2.12-6.1.1.jar optional=true

I digged a bit deeper and it seems that coursier tries to do a dir listing on the maven repository, but nexus does not allow dir listings on https://nexus.company.com/repository/maven-releases/my/company/foo_2.12/6.1.1, you instead have to do to https://nexus.company.com/service/rest/repository/browse/maven-releases/my/company/foo_2.12/6.1.1
(also this listing might not be compatible with a maven central listing)
Because the listing fails, the publications for this project after resolution are empty, which in turn marks the jar dependency as optional.
Multiple solutions:

Detect nexus and request / parse listing differently
If listing request / parse fails make sure there is a default list of publications
Don't mark dependencies optional when they are requested as non-optional but end up with empty publictations (why is this done?)

@francisdb "Optional" artifacts doesn't mean that these can be safely ignored here. Users of coursier via its API have to try to download those. "Optional" just means that if one gets a not found error when trying to download one of them, then this artifact and its not found error can be ignored. Only not found error should be ignored. This was added late during the RC cycle while retaining binary compatiblity, so it doesn't appear clearly in the API (and all users don't handle them yet).
It was added precisely to handle private nexus repositories or nexus mirrors, that don't always list all the available artifacts.

Ok, that clarifies things, are you interested in also parsing nexus listings correctly?

I think parsing Nexus listings should actually be removed… It was added to handle POMs with defective packaging tags, but Nexus mirrors don't always list all the files (they typically only list the ones they have in cache). "Optional" artifacts solved the issue at the end. So Nexus listing handling is now unnecessary (it just flags some artifacts as non optional, but if users handle optionality fine, it's the same result at the end).


Please update documentation of componentWillReceiveProps and UNSAFE_componentWillReceiveProps

https://reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops
Documentation did not help me get rid of componentWillReceiveProps/UNSAFE_componentWillReceiveProps
There is a way more easy way to stop using  componentWillReceiveProps/UNSAFE_componentWillReceiveProps than written in docs.
Steps:
Add a nice, unique key to the component which used to receive props.
The key must contain data which supposed to change props (preferably ids)
<ComponentToReceiveProps
key={thing id  that this component depends on + other thing id that this component depends on }
{...props} />
Replace componentWillReceiveProps with componentDidMount in ComponentToReceiveProps.
Use props in ComponentToReceiveProps.
I hope this will help others too.

This part of the section refers to exactly that approach:

or fully uncontrolled with a key instead.

I think that part could be explained better with some example.

It links to an example.
https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html#recommendation-fully-uncontrolled-component-with-a-key


[MB-14296](User Story) Office users can see creation and updates to the backup contact information in the customer profile

Jira ticket for this change
Summary

[x] Update move query to show backup_contacts table.
[x] Add createServiceMemberBackupContact template and test
[x] Add updateServiceMemberBackupContact template and test
[x] Update field mapping with new tokens

Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the UI locally.
make client_run

Terminal 2
Start the Go server locally.
make server_run

Additional steps

WIP
Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Messages

:book:
:link: MB-14296

  Generated by :no_entry_sign: dangerJS against 5485c5412d1d45a16993c154fd197e72f7d05f41


add: form-item-taglist component with key/val appendable

essentially a grid with 2 columns, add button to render a new row of 2 columns, when parent form is submitted (if present) the key/value pairs are grouped into an object in the form data known as tags for the data points in our app


Add Visual Recognition re-training

Refer to the API Reference

This is similar to the createClassifier method. The difference is that it doesn't use the name parameter.

Complete with #399.


Updated plots of phenotypic UMAPS vs. omics and CRISPR essentiality

Linked to issue:
https://github.com/jump-cellpainting/morphmap/issues/14
New Scripts:

04.create-visualization/03.0.create-expr-essentiality-pheontypic-maps.ipynb - with code to generate plots of Phenotypic Map vs. Pooled CRISPR / Omics data

Modified:

00.download-and-process-annotations/09.download-and-process-depmap-data.ipynb - added processing of GeneEffect readout from DepMap

New Files:

00.download-and-process-annotations/output/CRISPRGeneEffect_U2OS.csv.gz
04.create-visualization/figures/crispr_umap_phenotypic_vs_depmap_crispr_gene_effect.png
04.create-visualization/figures/crispr_umap_phenotypic_vs_u2os_gene_expression.png
04.create-visualization/figures/orf_umap_phenotypic_vs_depmap_crispr_gene_effect.png
04.create-visualization/figures/orf_umap_phenotypic_vs_u2os_gene_expression.png

Thanks for the PR @tjetkaARD!


Hope add a values fencing

If Tile38 have a mechanism that can set a range of monitoring would be the best. For example,  the client sent the "fset" command to set the values of  a field can also bind a hook, specifically, if a truck‘s speed reaches a certain value,tile38 will  trigger a values fencing event.

This is possible by using the WHERE clause for your fence.
NEARBY trucks FENCE WHERE speed 25 +inf POINT 33.54 -115.67 1000

This will only trigger an event when the speed field of an object is 25+
For more information check out http://tile38.com/commands/intersects/#search-options

Awesome! it's good idea.
Thanks!


Implement Date.prototype.toISOString()

Moved toString() logic into the toISOString() method extended with a Z postfix as the standard said.
Since the toString() is "implementation-dependent" the toString() calls the toISOString() method.

Will this change unify smth later?

Looks good to me.

+1 lgtm

Looks good to me

LGTM

Merged 63083b3b51157b0f02d1170fc0296845f2bcf79f


OpenSSL1.1.1 and Boost 1.70+

OS: Ubuntu 20.04
CPU: amd64
OpenSSL: 1.1.1f
Boost: 1.71
I checked out tags/<IP_ADDRESS> received the following error during make -f makefile.unix:

LDOGE/src$ make -f makefile.unix
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -I/mnt/mirror/src/git/vashshawn/LDOGE/src -I/mnt/mirror/src/git/vashshawn/LDOGE/src/obj -DUSE_UPNP=0 -DENABLE_WALLET -I/mnt/mirror/src/git/vashshawn/LDOGE/src/leveldb/include -I/mnt/mirror/src/git/vashshawn/LDOGE/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -fPIE -D_FORTIFY_SOURCE=2  -MMD -MF obj/alert.d -o obj/alert.o alert.cpp
In file included from chainparams.h:9,
                 from alert.cpp:7:
bignum.h:57:24: error: invalid use of incomplete type ‘BIGNUM’ {aka ‘struct bignum_st’}
   57 | class CBigNum : public BIGNUM
      |                        ^~~~~~
In file included from /usr/include/openssl/crypto.h:25,
                 from allocators.h:16,
                 from serialize.h:24,
                 from alert.h:9,
                 from alert.cpp:5:
/usr/include/openssl/ossl_typ.h:80:16: note: forward declaration of ‘BIGNUM’ {aka ‘struct bignum_st’}
   80 | typedef struct bignum_st BIGNUM;
      |                ^~~~~~~~~
In file included from chainparams.h:9,
                 from alert.cpp:7:
bignum.h: In constructor ‘CBigNum::CBigNum()’:
bignum.h:62:9: error: ‘BN_init’ was not declared in this scope
   62 |         BN_init(this);
      |         ^~~~~~~
bignum.h: In copy constructor ‘CBigNum::CBigNum(const CBigNum&)’:
bignum.h:67:9: error: ‘BN_init’ was not declared in this scope
   67 |         BN_init(this);
      |         ^~~~~~~
bignum.h:68:30: error: cannot convert ‘CBigNum*’ to ‘BIGNUM*’ {aka ‘bignum_st*’}
   68 |         if (!BN_copy(this, &b))
      |                              ^
      |                              |
      |                              CBigNum*
In file included from bignum.h:13,
                 from chainparams.h:9,
                 from alert.cpp:7:
/usr/include/openssl/bn.h:219:25: note:   initializing argument 1 of ‘BIGNUM* BN_copy(BIGNUM*, const BIGNUM*)’
  219 | BIGNUM *BN_copy(BIGNUM *a, const BIGNUM *b);
      |                 ~~~~~~~~^
In file included from chainparams.h:9,
                 from alert.cpp:7:

This seems to require an update from OpenSSL 1.0.2 to 1.1.1 which reached EOL at the end of 2019. This commit from CureCoin seems useful: https://github.com/cygnusxi/CurecoinSource/commit/6b93af07005b90e4f6c5785c60c10c36fa52a333
I started to apply those changes but I'm not sure what to do about this:

rpcclient.cpp: In function ‘json_spirit::Object CallRPC(const string&, const Array&)’:
rpcclient.cpp:44:58: error: no matching function for call to ‘boost::asio::ssl::context::context(boost::asio::io_service&, boost::asio::ssl::context_base::method)’
   44 |     ssl::context context(io_service, ssl::context::sslv23);
      |                                                          ^
In file included from /usr/include/boost/asio/ssl/context.hpp:757,
                 from /usr/include/boost/asio/ssl.hpp:18,
                 from rpcprotocol.h:18,
                 from rpcclient.cpp:9:
/usr/include/boost/asio/ssl/impl/context.ipp:371:1: note: candidate: ‘boost::asio::ssl::context::context(boost::asio::ssl::context&&)’
  371 | context::context(context&& other)
      | ^~~~~~~
/usr/include/boost/asio/ssl/impl/context.ipp:371:1: note:   candidate expects 1 argument, 2 provided
/usr/include/boost/asio/ssl/impl/context.ipp:63:1: note: candidate: ‘boost::asio::ssl::context::context(boost::asio::ssl::context_base::method)’
   63 | context::context(context::method m)
      | ^~~~~~~
/usr/include/boost/asio/ssl/impl/context.ipp:63:1: note:   candidate expects 1 argument, 2 provided

I'm not sure what to do with https://github.com/nerdcorenet/LDOGE/blob/ssl%2Bboost/src/rpcclient.cpp#L44
For reference, the Boost 1.70 doc for ssl::context::context is here

May have to refactor the code a little bit to match the different interfaces.
https://github.com/cygnusxi/CurecoinSource/blob/6b93af07005b90e4f6c5785c60c10c36fa52a333/src/curecoinrpc.cpp#L758

May have to refactor the code a little bit to match the different interfaces.
https://github.com/cygnusxi/CurecoinSource/blob/6b93af07005b90e4f6c5785c60c10c36fa52a333/src/curecoinrpc.cpp#L758

commit 84bdccbfc2b17a598e424316fd32066a9724fcf2 resolves some of these issues though I cannot guarantee the resolution is correct or sane. ;)
Getting the following issues when trying to launch litedoged:
$ ./litedoged -datadir=/mnt/chains/litedogetest -testnet
Error: Error initializing wallet database environment /home/mike/.litedoge!
$ cat /mnt/chains/litedogetest/testnet/debug.log
LiteDoge version v<IP_ADDRESS>LiteDoge (2021-01-09 22:56:31 -0500)
Using OpenSSL version OpenSSL 1.1.1f  31 Mar 2020
Using BerkeleyDB version Berkeley DB 5.3.28: (September  9, 2013)
Startup time: 03/13/21 17:51:40
Default data directory /home/mike/.litedoge
Used data directory /mnt/chains/litedogetest/testnet
init message: Verifying database integrity...
dbenv.open LogDir=/mnt/chains/litedogetest/testnet/database ErrorFile=/mnt/chains/litedogetest/testnet/db.log
ERROR: CDB() : error Invalid argument (22) opening database environment
Moved old /mnt/chains/litedogetest/testnet/database to /mnt/chains/litedogetest/testnet/database.1615657900.bak. Retrying.
dbenv.open LogDir=/mnt/chains/litedogetest/testnet/database ErrorFile=/mnt/chains/litedogetest/testnet/db.log
ERROR: CDB() : error Invalid argument (22) opening database environment
: Error initializing wallet database environment /mnt/chains/litedogetest/testnet!
Shutdown : In progress...
StopNode()
Shutdown : done


GEODE-7437: one way ssl

Add some tests to verify one way SSL and chained certs in new framework, remove old tests.
@mreddington @vfordpivotal @dihardman @karensmolermiller @davebarnes97

Codecov Report

Merging #555 into develop will decrease coverage by 0.29%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop     #555     +/-   ##
==========================================
- Coverage    73.31%   73.02%   -0.3%
==========================================
  Files          649      642      -7
  Lines        51811    50953    -858
==========================================
- Hits         37986    37209    -777
+ Misses       13825    13744     -81

Impacted Files
Coverage Δ

cppcache/src/ServerLocation.hpp
86.04% <0%> (-4.66%)
:arrow_down:

cppcache/src/ThinClientBaseDM.cpp
67.51% <0%> (-2.55%)
:arrow_down:

cppcache/src/TcpSslConn.cpp
69.56% <0%> (-2.18%)
:arrow_down:

cppcache/src/ThinClientRedundancyManager.cpp
75.46% <0%> (-0.47%)
:arrow_down:

cppcache/src/ClientMetadataService.cpp
59.06% <0%> (-0.23%)
:arrow_down:

cppcache/integration-test/LocatorHelper.hpp
100% <0%> (ø)
:arrow_up:

cppcache/src/ThinClientPoolDM.cpp
76.04% <0%> (+0.5%)
:arrow_up:

cppcache/src/ThinClientPoolDM.hpp
90.16% <0%> (+1.63%)
:arrow_up:

cppcache/src/statistics/StatArchiveWriter.cpp
83.33% <0%> (+1.75%)
:arrow_up:

cppcache/include/geode/ExceptionTypes.hpp
38.4% <0%> (+1.81%)
:arrow_up:

... and 2 more

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 e3087f2...a71ce89. Read the comment docs.

Looks good to me. I've verified that these new tests pass on my machine. That's one of my key criteria!


Some corner cases for highlighting comments

disp /// /* ignored
"printed"

/**/ * disp "not printed"

local ninety 90
disp `ni/*comments are allowed inside locals*/nety'
disp `ni/*
/*These can be nested and span multiple lines*/
*/nety'
disp "`ninety/* Ignored but not a comment per se. Any non [0-9a-zA-Z_] character would do*/'"
disp "`ninety@This is also not evaluated, for example.'"

/*/ disp "printed"

/*/*
Note that /*/ opens end closes a multi-line block. And if you have a *
right after, then that opens a new one.
*/
 disp " printed"

I didn't realize that /// also ignored the rest of the line like // did

/**/ * disp "not printed"
I hadn't allowed there to be a space after a block comment and before a *. Easy fix.

your last example doesn't seem to work in isolation?
1:

2:

It seems as of Stata 14, /*/ no longer starts and ends a block. However, ending a block by */* does seem to start a new block.

that last part is now fixed

the right regex for globals should be [A-Za-z][A-Za-z0-9_]{0,31}|_[A-Za-z0-9_]{1,31}, even though Stata doesn't let you create a global with "global __ hi" or "global __z hi", only reference a local "_" or "_z" that's already been created.
Additionally, those aren't actually the right regexes, because we've been working only in the ASCII world.

that's also a valid local.
So I have to use \w in more places. And \w&&[^\d] when I want to refer to letters but not numbers.

Very impressive.

Switch to Atom!

Hydrogen is amazing. It works so seamlessly with remote servers too.

Well, I like the prettiness, but I don't know that i can get a ton of mileage out stuff like Hydrogen on the stuff I do daily (cool as it is). The language plugin ecosystem is more interesting (e.g. your package is certainly miles ahead the Stata package in Vim).
I wonder if marginal improvements justify the switching costs, though. Using Atom feels really slow. Other than the startup, however, Atom doesn't seem slow at all, so I'm pretty sure that it's because I don't have all the muscle memory I've built up using vim.
Modal editing is extremely functional; same for the way registers, markets, mappings, and macros work. I'm sure you can replicate most (all? more?) of that in Atom. Do I want to spent a ton of time re-learning (and, perhaps just as importantly, a ton of time porting everything)? Not yet. I wonder if it will ever reach a tipping point, though.

disp "ninety/* Ignored but not a comment per se. Any non [0-9a-zA-Z_] character would do*/'" disp "ninety@This is also not evaluated, for example.'"

@mcaceresb It appears that () doesn't end a local.
sysuse auto
local ar "not printed"
di "`ar()'"

Interestingly,
disp "`ar)'"

does work.

Interestingly, the `local ++i' convention works within locals as well!
local i = 1
disp `++i'
disp `i++'
disp `i++And, amazingly, this is allowed. even though ++ is operating on the local i!'
disp `i'

Actually, since locals are evaluated inside locals, you can't really call them comments:
local i 1
disp "i = `i++Locals here are evaluated. `++i', `++i', and `i++' are evaluated.'"

local i = 1
disp `i"/*`++i'*/"Does this print 1, 2, 3? /*"`++i'"*/'

The above prints 4 and stores 5 in the local i for the first chunk and prints 2 for the second chunk. Note that you can get errors from stuff you put here:
local j a '
disp `i#This is fine'
disp `i=`=This is a soft error''
disp `i#This is a hard error`j''

That's so crazy. I kinda give up on these corner cases

I would think it is better is to leave them as part of the local. I don't think many people are putting comments or such inside locals. Locals inside locals, on the other hand, are semi-common.

Locals inside locals works as long as there aren't huge spaces


Performance issues?

Hopefully I'm not the only one suffering performance issues after upgrading to 1.1.x. I had hoped upgrading to 1.1.2 would help, but it hasn't.
Performance is incredibly hit or miss with the bot for the past couple versions. If you type a message and then a command, it will fail to see the command. You'll have to run the command again to get the bot to respond to it.
Here's a recent example from a few minutes ago:

You can see the user quickly sent $race and then $jr, but the bot did not see it the first time and the command had to be repeated. This is easily replicate-able behavior and while not bot-breaking, it is incredibly inconvenient. 😛
Basically, wondering if anyone else is having any issues like this, if it's a known problem, etc. And before you ask if there's an issue with my server or proximity of the Discord server to the actual server, those are all non-issues. Server is severely over-spec'd. On a gigabit up and down connection. Home server is in Austin, Discord server location is US South.

read the patch notes in the future.
1.5s cooldown per command per user.

Hmm...must've missed that one! I do read and love showing off when new stuff is added. 😄

some commands, like $slot, have internal cooldowns to themselves, usually specified in the description (-h commandname)

I take it there's no way to remove the global cooldown? Skimmed through database briefly and saw the CommandCooldown table was empty. 😛

Also...is there any reason that would affect if you send a message that is not a command and then a message that is a command, it still is affected by that 1.5s cooldown? Because I can't think of anything else that would be causing that particular problem consistently. 😄

i was just about to look into that, yesterday when testing something, it seemed it was taking any message and triggering the cooldown

Glad to hear I'm not losing my mind (yet)! 😃

Taking that as a no for disabling global cooldown then? 😛

i'll reduce it to 750ms on self hosted

Good enough! Thanks for the responses, information, etc. 👍


MultiTenantSqlConnectionStringProvider, is it possible?

I'm trying to setup Fhir-Service in a multi-tenant way where a user claim determins the connection string to be used.
Do you think this concept will work if I disable all kinds of sql auto migrations and the Task Hostings?
I create a new class that implements ISqlConnectionStringProvider
  public class MultiTenantSqlConnectionStringProvider : ISqlConnectionStringProvider
  {
    private readonly SqlServerDataStoreConfiguration sqlServerDataStoreConfiguration;
    private readonly IHttpContextAccessor httpContextAccessor;
    private readonly IConfiguration configuration;

    public MultiTenantSqlConnectionStringProvider(IOptions<SqlServerDataStoreConfiguration> sqlServerDataStoreConfiguration, IHttpContextAccessor httpContextAccessor, IConfiguration configuration)
    {
      this.sqlServerDataStoreConfiguration = EnsureArg.IsNotNull<SqlServerDataStoreConfiguration>(sqlServerDataStoreConfiguration?.Value, nameof(sqlServerDataStoreConfiguration));
      this.httpContextAccessor = httpContextAccessor;
      this.configuration = configuration;
    }

    /// <inheritdoc />
    public Task<string> GetSqlConnectionString(CancellationToken cancellationToken)
    {
      var connectionString = sqlServerDataStoreConfiguration.ConnectionString;
      var httpContext = httpContextAccessor.HttpContext;
      if (httpContext != null)
      {
        var tenantId = httpContext?.User.Claims.FirstOrDefault(c => c.Type == "tenantId");
        connectionstring = tenantId != null ? configuration[$"Tenant{tenantId}:DCString"] : sqlServerDataStoreConfiguration.ConnectionString;
      }

      return Task.FromResult(connectionString );
    }
  }

Then in Startup.cs
      // Replace the connection string provider with my own
      var descriptor = new ServiceDescriptor(typeof(Microsoft.Health.SqlServer.ISqlConnectionStringProvider), typeof(Infrastructure.MultiTenantSqlConnectionStringProvider), ServiceLifetime.Singleton);
      services.Replace(descriptor);

or are there some internal stuff that prevents this from working?

Thanks for raising the question @Eneuman. We do not have support and do not plan to add in near future for mapping connection strings dynamically per tenant. Closing this issue. Please feel free to reach out for further questions.


Investigate improvements to meta data security

It would be entirely possible to rewrite the state and data store to provide meta data security. By simply storing the Ids in the database with encrypted blobs containing the meta data, one would easily be able to reduce the meta data to only contain:

Number of archives
Number of archive tokens
Number of admin tokens
Number of files in an archive

This sort of raises the concern of key management, the admin user would potentially have to handle further keys than now (one per archive). The meta data could be encrypted on a per-archive basis, re-using the key. This would make the API a lot less useful as it would not enable admins to easily create other applications without implementing ChaCha etc.
Currently, the meta data exposed to the server is filenames, archive names, creation dates etc. which might not be that serious given that the admin is thought to be in control of the server anyway.


lerna error while testing

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior. MVCE would definitely help.

While running npm test from root in Windows 10 pro

Screenshot

Can you please provide more information about your environment? cygwin, git-bash, WSL or other?

git-bash and Powershell I tried running the above command in both and got the same error.

Your previous image has some more information

You may be the only person with this setup that could properly reproduce and fix this bug.
I found this issue that could be related. But my bet would be with the escaping slash.
Please try this change in package.json
-    "test:packagelint": "lerna exec npmPkgJsonLint -- --quiet -c \$LERNA_ROOT_PATH/.npmpackagejsonlintrc.json .",
+    "test:packagelint": "lerna exec npmPkgJsonLint -- --quiet -c \"${LERNA_ROOT_PATH}\"/.npmpackagejsonlintrc.json .",

or this
-    "test:packagelint": "lerna exec npmPkgJsonLint -- --quiet -c \$LERNA_ROOT_PATH/.npmpackagejsonlintrc.json .",
+    "test:packagelint": "lerna exec npmPkgJsonLint -- --quiet -c '${LERNA_ROOT_PATH}/.npmpackagejsonlintrc.json' .",

and run:
npm run test:packagelint

@hugosenari still getting the same error.

The problem is with window's file path which is different from that of Linux, which I guess you guys have already figured out.
So, now the solution would be (at least what I think is) to use WSL2 for running your project in windows.
The steps are simple

Install WSL2 in your windows
Install node inside your WSL2.

Following is the link on how to install WSL2 and node.
How to install WSL2
How setup node inside WSL2


Added e2e integration test

Added e2e integration test for playgrounds:

[X] GraphiQL
[ ] Apollo Sandbox Explorer
[ ] Altari

I have:

[X] Added tests covering the bug / feature (see testing)
[ ] Updated any relevant documentation (see docs)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+3.7%) to 79.334%

Files with Coverage Reduction
New Missed Lines
%

codegen/config/binder.go
2
76.56%

codegen/object.go
2
68.57%

Totals

Change from base Build<PHONE_NUMBER>:
3.7%

Covered Lines:
6695

Relevant Lines:
8439

💛  - Coveralls


RDF4J Elastic Search shows only INFO level logs

I use the tests quite intensively and need have more detailed logs than INFO. I will replace slf4j-simple implementation to log4j2 one but for tests only.

Alternatively, you could stick with using SFL4J SimpleLogger, and just configure it to enable debug-level logging. See http://www.slf4j.org/api/org/slf4j/impl/SimpleLogger.html for details.


Remove Å

wat

Erm, how did I manage that...
On Sunday, 19 April 2015, James Kyle<EMAIL_ADDRESS>wrote:

Merged #245 https://github.com/babel/babel.github.io/pull/245.
--
Reply to this email directly or view it on GitHub
https://github.com/babel/babel.github.io/pull/245#event-284593889.

--
Sebastian McKenzie

I must have been trying to be cultural.
On Sunday, 19 April 2015, Sebastian McKenzie<EMAIL_ADDRESS>wrote:

Erm, how did I manage that...
On Sunday, 19 April 2015, James Kyle<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

Merged #245 https://github.com/babel/babel.github.io/pull/245.
--
Reply to this email directly or view it on GitHub
https://github.com/babel/babel.github.io/pull/245#event-284593889.

--
Sebastian McKenzie

--
Sebastian McKenzie


Add a Troubleshooting section and add service-linked roles

Recently I had an issue when applying a stack. This is due to our aws account not having the necessary service-linked role allowing aws to make changes from one service to another.
I have started a Troubleshooting guide here to feature things like this. This seems like the best place to put it because it will usually happen when you're using stack_master.

This isn't the right place to put this info


[New game]: Color swap

🎮 Game Request
"Color Swap" is a simple yet addictive browser-based game developed using HTML, CSS, and JavaScript. The game revolves around the player controlling a character or object that must pass through obstacles matching its color. The color of the character changes randomly, requiring quick reflexes and strategic thinking.
Point down the features
Simple Controls:
The player controls the character using the arrow keys or touch gestures on mobile devices.
The character moves left, right, up, or down to navigate through a series of color-coded obstacles.
Color Matching:
The character changes color periodically or when passing through special zones.
Players must guide the character through obstacles that match its current color to score points.
Increasing Difficulty:
As the game progresses, the speed and frequency of color changes increase.
More complex patterns and additional obstacles are introduced to challenge the player.

Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @aditya-bhaumik ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


IPv6 link failed between 06:50 and 10:05 (UTC) -> CloudFlare 5xx errors

As some of you may have noticed (#155, #156), the service went down shortly between 06:50 and 09:06 (UTC). It seems that the issue discovered in #109 reappeared: our IPv6 link with CloudFlare flipped, which disabled processing of images that were out-of-cache.
Below graph is in UTC+02:00:

Will track progress in investigating and fixing this issue here. Thank you for all reports!

To-do list:

[ ] Make sure temporary fix holds for a few days
[ ] Fix monitoring of IPv6-links
[ ] Prepare Roubaix DC to take current load
[ ] Warm-up Roubaix DC caches
[ ] Define maintenance window to switch to Roubaix DC
[ ] Switch to Roubaix DC
[ ] Use maintenance window to investigate & reconfigure IPv6-stack in Paris-Orly DC
[ ] Use maintenance window to test IPv6-link-flipping and monitoring
[ ] Switch back to Paris-Orly DC

The temporary fix didn't work quite as expected, lost connectivity again between 11:15 and 12:05.

Wrote a bit more permanent fix now, please bear with us..

All looks well now, new fix is working as expected, however, a maintenance window is still needed. Will need to prepare some things, which might take a few days. Graph is in UTC +02:00:

Cache warm-up started for Roubaix DC. A subset of requests will be passed through Roubaix DC. The amount will increase until 22:00 (UTC), at which time all requests will be processed by Roubaix DC.
Currently we're at:

[ ] 10%
[ ] 20%
[ ] 33% planned @ 14:00 UTC
[ ] 50% planned @ 16:00 UTC
[ ] 100% planned @ 22:00 UTC

Service switched to Roubaix DC. Maintenance has started.

Maintenance has ended. Service back on Paris-Orly DC. Will monitor situation, if anything happens we'll switch back to Roubaix DC.

No further problems discovered, issue solved.


Characters are visible instead of .png(media/ec60b062-1979-446d-b431-bf0baede0f8b.png)

https://docs.microsoft.com/ja-jp/onedrive/use-group-policy

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

ID: 04ad2f16-c861-7a1b-5c1d-e4601e8f3855
Version Independent ID: c47df4cd-f706-d807-5eac-172fba1e500f
Content: Use Group Policy to control OneDrive sync client settings
Content Source: OneDrive/use-group-policy.md
Service: one-drive
GitHub Login: @kaarins
Microsoft Alias: kaarins

@MollyMalone Thanks.
Same as MicrosoftDocs/OfficeDocs-o365seccomp#396


docker compose start fail

docker failed when running: docker compose up --build

update dockerfile that allow downgrade


Cross compilation TensorFlow Lite with CMake mat error

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf.2.8
Custom code
Yes
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
gcc-arm-10.3
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I want to get a libtensorflow.so for my Arm Linux.
Standalone code to reproduce the issue
ARMCC_FLAGS="-march=armv7-a -mfpu=neon-vfpv4 -funsafe-math-optimizations -mfp16-format=ieee"
cmake -DCMAKE_C_COMPILER=gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc \
  -DCMAKE_CXX_COMPILER=gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-g++ \
  -DCMAKE_C_FLAGS="${ARMCC_FLAGS}" \
  -DCMAKE_CXX_FLAGS="${ARMCC_FLAGS}" \
  -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \
  -DCMAKE_SYSTEM_NAME=Linux \
  -DCMAKE_SYSTEM_PROCESSOR=armv7 \
  ../tensorflow/lite/

make -j 16

then I get the Error:
w/tensorflow/build_sdk/xnnpack/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-1x16c4-minmax-neondot.c
[ 79%] Building C object _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o
cd /mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/_deps/xnnpack-build && /mnt/fileroot/guanghui.wan/nanoQ/Algorithm/tools/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -DEIGEN_MPL2_ONLY -DFXDIV_USE_INLINE_ASSEMBLY=0 -DNOMINMAX=1 -DPTHREADPOOL_NO_DEPRECATED_API=1 -DXNN_ENABLE_ARM_BF16=0 -DXNN_ENABLE_ARM_DOTPROD=1 -DXNN_ENABLE_ARM_FP16_SCALAR=1 -DXNN_ENABLE_ARM_FP16_VECTOR=1 -DXNN_ENABLE_ARM_I8MM=0 -DXNN_ENABLE_ASSEMBLY=1 -DXNN_ENABLE_CPUINFO=1 -DXNN_ENABLE_DWCONV_MULTIPASS=0 -DXNN_ENABLE_GEMM_M_SPECIALIZATION=1 -DXNN_ENABLE_JIT=0 -DXNN_ENABLE_MEMOPT=1 -DXNN_ENABLE_RISCV_VECTOR=1 -DXNN_ENABLE_SPARSE=1 -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/third_party/xla/third_party/tsl -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/xnnpack/src -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/pthreadpool-source/include -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/FXdiv-source/include -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/FP16-source/include -march=armv8-a -mfpu=neon-vfpv4 -funsafe-math-optimizations -mfp16-format=ieee -O3 -DNDEBUG -std=c99 -fPIC -Wno-psabi -O2 -pthread  -fno-math-errno  -marm  -march=armv8.2-a+dotprod -mfpu=neon-fp-armv8  -MD -MT _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o -MF CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o.d -o CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o -c /mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/xnnpack/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c
/tmp/ccrZ5z20.s: Assembler messages:
/tmp/ccrZ5z20.s:75: Error: selected processor does not support `vsdot.s8 q14,q12,d7[0]' in ARM mode
/tmp/ccrZ5z20.s:76: Error: selected processor does not support `vsdot.s8 q10,q9,d7[0]' in ARM mode
/tmp/ccrZ5z20.s:77: Error: selected processor does not support `vsdot.s8 q14,q11,d7[1]' in ARM mode
/tmp/ccrZ5z20.s:78: Error: selected processor does not support `vsdot.s8 q10,q8,d7[1]' in ARM mode
/tmp/ccrZ5z20.s:134: Error: selected processor does not support `vsdot.s8 q14,q9,d7[0]' in ARM mode
/tmp/ccrZ5z20.s:135: Error: selected processor does not support `vsdot.s8 q10,q8,d7[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49877: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-1x8c4-minmax-neondot.c.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/tmp/ccWEkUHN.s: Assembler messages:
/tmp/ccWEkUHN.s:81: Error: selected processor does not support `vsdot.s8 q12,q9,d7[0]' in ARM mode
/tmp/ccWEkUHN.s:82: Error: selected processor does not support `vsdot.s8 q13,q2,d7[0]' in ARM mode
/tmp/ccWEkUHN.s:83: Error: selected processor does not support `vsdot.s8 q15,q8,d7[0]' in ARM mode
/tmp/ccWEkUHN.s:85: Error: selected processor does not support `vsdot.s8 q10,q14,d7[0]' in ARM mode
/tmp/ccWEkUHN.s:91: Error: selected processor does not support `vsdot.s8 q12,q8,d7[1]' in ARM mode
/tmp/ccWEkUHN.s:93: Error: selected processor does not support `vsdot.s8 q13,q14,d7[1]' in ARM mode
/tmp/ccWEkUHN.s:99: Error: selected processor does not support `vsdot.s8 q10,q14,d7[1]' in ARM mode
/tmp/ccWEkUHN.s:100: Error: selected processor does not support `vsdot.s8 q15,q8,d7[1]' in ARM mode
/tmp/ccWEkUHN.s:184: Error: selected processor does not support `vsdot.s8 q13,q2,d7[0]' in ARM mode
/tmp/ccWEkUHN.s:185: Error: selected processor does not support `vsdot.s8 q12,q9,d7[0]' in ARM mode
/tmp/ccWEkUHN.s:186: Error: selected processor does not support `vsdot.s8 q10,q14,d7[0]' in ARM mode
/tmp/ccWEkUHN.s:187: Error: selected processor does not support `vsdot.s8 q15,q8,d7[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49905: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-1x16c4-minmax-neondot.c.o] Error 1
/tmp/ccEQXTmv.s: Assembler messages:
/tmp/ccEQXTmv.s:88: Error: selected processor does not support `vsdot.s8 q15,q11,d7[0]' in ARM mode
/tmp/ccEQXTmv.s:89: Error: selected processor does not support `vsdot.s8 q14,q9,d7[0]' in ARM mode
/tmp/ccEQXTmv.s:90: Error: selected processor does not support `vsdot.s8 q15,q10,d7[1]' in ARM mode
/tmp/ccEQXTmv.s:91: Error: selected processor does not support `vsdot.s8 q14,q8,d7[1]' in ARM mode
/tmp/ccEQXTmv.s:93: Error: selected processor does not support `vsdot.s8 q13,q11,d7[0]' in ARM mode
/tmp/ccEQXTmv.s:94: Error: selected processor does not support `vsdot.s8 q12,q9,d7[0]' in ARM mode
/tmp/ccEQXTmv.s:95: Error: selected processor does not support `vsdot.s8 q13,q10,d7[1]' in ARM mode
/tmp/ccEQXTmv.s:96: Error: selected processor does not support `vsdot.s8 q12,q8,d7[1]' in ARM mode
/tmp/ccEQXTmv.s:189: Error: selected processor does not support `vsdot.s8 q15,q9,d6[0]' in ARM mode
/tmp/ccEQXTmv.s:190: Error: selected processor does not support `vsdot.s8 q14,q8,d6[0]' in ARM mode
/tmp/ccEQXTmv.s:191: Error: selected processor does not support `vsdot.s8 q13,q9,d7[0]' in ARM mode
/tmp/ccEQXTmv.s:192: Error: selected processor does not support `vsdot.s8 q12,q8,d7[0]' in ARM mode
/tmp/ccmAlACc.s: make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49933: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-2x8c4-minmax-neondot.c.o] Error 1
Assembler messages:
/tmp/ccmAlACc.s:87: Error: selected processor does not support `vsdot.s8 q1,q10,q8' in ARM mode
/tmp/ccmAlACc.s:90: Error: selected processor does not support `vsdot.s8 q0,q5,q8' in ARM mode
/tmp/ccmAlACc.s:91: Error: selected processor does not support `vsdot.s8 q2,q9,q8' in ARM mode
/tmp/ccmAlACc.s:92: Error: selected processor does not support `vsdot.s8 q14,q4,q8' in ARM mode
/tmp/ccmAlACc.s:101: Error: selected processor does not support `vsdot.s8 q13,q5,q8' in ARM mode
/tmp/ccmAlACc.s:102: Error: selected processor does not support `vsdot.s8 q3,q10,q8' in ARM mode
/tmp/ccmAlACc.s:103: Error: selected processor does not support `vsdot.s8 q12,q4,q8' in ARM mode
/tmp/ccmAlACc.s:104: Error: selected processor does not support `vsdot.s8 q15,q9,q8' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49919: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-1x16c8-minmax-neondot-ld64.c.o] Error 1
/tmp/ccBfIgBU.s: Assembler messages:
/tmp/ccBfIgBU.s:109: Error: selected processor does not support `vsdot.s8 q14,q10,d6[0]' in ARM mode
/tmp/ccBfIgBU.s:110: Error: selected processor does not support `vsdot.s8 q13,q9,d6[0]' in ARM mode
/tmp/ccBfIgBU.s:111: Error: selected processor does not support `vsdot.s8 q12,q8,d6[0]' in ARM mode
/tmp/ccBfIgBU.s:112: Error: selected processor does not support `vsdot.s8 q1,q11,d6[0]' in ARM mode
/tmp/ccBfIgBU.s:114: Error: selected processor does not support `vsdot.s8 q0,q10,d7[0]' in ARM mode
/tmp/ccBfIgBU.s:115: Error: selected processor does not support `vsdot.s8 q4,q9,d7[0]' in ARM mode
/tmp/ccBfIgBU.s:116: Error: selected processor does not support `vsdot.s8 q5,q8,d7[0]' in ARM mode
/tmp/ccBfIgBU.s:117: Error: selected processor does not support `vsdot.s8 q6,q11,d7[0]' in ARM mode
/tmp/ccBfIgBU.s:126: Error: selected processor does not support `vsdot.s8 q14,q11,d6[1]' in ARM mode
/tmp/ccBfIgBU.s:127: Error: selected processor does not support `vsdot.s8 q0,q11,d7[1]' in ARM mode
/tmp/ccBfIgBU.s:128: Error: selected processor does not support `vsdot.s8 q13,q10,d6[1]' in ARM mode
/tmp/ccBfIgBU.s:129: Error: selected processor does not support `vsdot.s8 q4,q10,d7[1]' in ARM mode
/tmp/ccBfIgBU.s:130: Error: selected processor does not support `vsdot.s8 q12,q9,d6[1]' in ARM mode
/tmp/ccBfIgBU.s:131: Error: selected processor does not support `vsdot.s8 q1,q8,d6[1]' in ARM mode
/tmp/ccBfIgBU.s:132: Error: selected processor does not support `vsdot.s8 q5,q9,d7[1]' in ARM mode
/tmp/ccBfIgBU.s:133: Error: selected processor does not support `vsdot.s8 q6,q8,d7[1]' in ARM mode
/tmp/ccBfIgBU.s:255: Error: selected processor does not support `vsdot.s8 q13,q9,d6[0]' in ARM mode
/tmp/ccBfIgBU.s:256: Error: selected processor does not support `vsdot.s8 q4,q9,d7[0]' in ARM mode
/tmp/ccBfIgBU.s:258: Error: selected processor does not support `vsdot.s8 q14,q10,d6[0]' in ARM mode
/tmp/ccBfIgBU.s:260: Error: selected processor does not support `vsdot.s8 q0,q10,d7[0]' in ARM mode
/tmp/ccBfIgBU.s:262: Error: selected processor does not support `vsdot.s8 q12,q9,d6[0]' in ARM mode
/tmp/ccBfIgBU.s:263: Error: selected processor does not support `vsdot.s8 q5,q9,d7[0]' in ARM mode
/tmp/ccBfIgBU.s:264: Error: selected processor does not support `vsdot.s8 q1,q8,d6[0]' in ARM mode
/tmp/ccBfIgBU.s:265: Error: selected processor does not support `vsdot.s8 q6,q8,d7[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49947: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-2x16c4-minmax-neondot.c.o] Error 1
/tmp/ccDJj1kS.s: Assembler messages:
/tmp/ccDJj1kS.s:75: Error: selected processor does not support `vsdot.s8 q15,q12,q10' in ARM mode
/tmp/ccDJj1kS.s:76: Error: selected processor does not support `vsdot.s8 q2,q9,q10' in ARM mode
/tmp/ccDJj1kS.s:77: Error: selected processor does not support `vsdot.s8 q13,q11,q10' in ARM mode
/tmp/ccDJj1kS.s:78: Error: selected processor does not support `vsdot.s8 q3,q8,q10' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49891: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-1x8c8-minmax-neondot-ld64.c.o] Error 1
/tmp/ccRqcaMJ.s: Assembler messages:
/tmp/ccRqcaMJ.s:143: Error: selected processor does not support `vsdot.s8 q1,q14,d6[0]' in ARM mode
/tmp/ccRqcaMJ.s:146: Error: selected processor does not support `vsdot.s8 q5,q14,d5[0]' in ARM mode
/tmp/ccRqcaMJ.s:147: Error: selected processor does not support `vsdot.s8 q15,q14,d7[0]' in ARM mode
/tmp/ccRqcaMJ.s:149: Error: selected processor does not support `vsdot.s8 q6,q7,d5[0]' in ARM mode
/tmp/ccRqcaMJ.s:151: Error: selected processor does not support `vsdot.s8 q4,q7,d6[0]' in ARM mode
/tmp/ccRqcaMJ.s:152: Error: selected processor does not support `vsdot.s8 q0,q7,d7[0]' in ARM mode
/tmp/ccRqcaMJ.s:158: Error: selected processor does not support `vsdot.s8 q7,q14,d5[0]' in ARM mode
/tmp/ccRqcaMJ.s:159: Error: selected processor does not support `vsdot.s8 q13,q10,d5[0]' in ARM mode
/tmp/ccRqcaMJ.s:160: Error: selected processor does not support `vsdot.s8 q12,q14,d6[0]' in ARM mode
/tmp/ccRqcaMJ.s:162: Error: selected processor does not support `vsdot.s8 q11,q14,d7[0]' in ARM mode
/tmp/ccRqcaMJ.s:163: Error: selected processor does not support `vsdot.s8 q10,q1,d6[0]' in ARM mode
/tmp/ccRqcaMJ.s:166: Error: selected processor does not support `vsdot.s8 q14,q1,d7[0]' in ARM mode
/tmp/ccRqcaMJ.s:170: Error: selected processor does not support `vsdot.s8 q6,q1,d5[1]' in ARM mode
/tmp/ccRqcaMJ.s:171: Error: selected processor does not support `vsdot.s8 q5,q9,d5[1]' in ARM mode
/tmp/ccRqcaMJ.s:172: Error: selected processor does not support `vsdot.s8 q4,q1,d6[1]' in ARM mode
/tmp/ccRqcaMJ.s:173: Error: selected processor does not support `vsdot.s8 q0,q1,d7[1]' in ARM mode
/tmp/ccRqcaMJ.s:174: Error: selected processor does not support `vsdot.s8 q15,q9,d7[1]' in ARM mode
/tmp/ccRqcaMJ.s:177: Error: selected processor does not support `vsdot.s8 q1,q9,d6[1]' in ARM mode
/tmp/ccRqcaMJ.s:186: Error: selected processor does not support `vsdot.s8 q7,q9,d5[1]' in ARM mode
/tmp/ccRqcaMJ.s:187: Error: selected processor does not support `vsdot.s8 q10,q8,d6[1]' in ARM mode
/tmp/ccRqcaMJ.s:188: Error: selected processor does not support `vsdot.s8 q14,q8,d7[1]' in ARM mode
/tmp/ccRqcaMJ.s:191: Error: selected processor does not support `vsdot.s8 q13,q8,d5[1]' in ARM mode
/tmp/ccRqcaMJ.s:192: Error: selected processor does not support `vsdot.s8 q12,q9,d6[1]' in ARM mode
/tmp/ccRqcaMJ.s:193: Error: selected processor does not support `vsdot.s8 q11,q9,d7[1]' in ARM mode
/tmp/ccRqcaMJ.s:453: Error: selected processor does not support `vsdot.s8 q6,q9,d7[0]' in ARM mode
/tmp/ccRqcaMJ.s:454: Error: selected processor does not support `vsdot.s8 q5,q8,d7[0]' in ARM mode
/tmp/ccRqcaMJ.s:456: Error: selected processor does not support `vsdot.s8 q4,q9,d6[0]' in ARM mode
/tmp/ccRqcaMJ.s:457: Error: selected processor does not support `vsdot.s8 q0,q9,d5[0]' in ARM mode
/tmp/ccRqcaMJ.s:458: Error: selected processor does not support `vsdot.s8 q1,q8,d6[0]' in ARM mode
/tmp/ccRqcaMJ.s:460: Error: selected processor does not support `vsdot.s8 q15,q8,d5[0]' in ARM mode
/tmp/ccRqcaMJ.s:467: Error: selected processor does not support `vsdot.s8 q10,q9,d7[0]' in ARM mode
/tmp/ccRqcaMJ.s:468: Error: selected processor does not support `vsdot.s8 q12,q9,d6[0]' in ARM mode
/tmp/ccRqcaMJ.s:469: Error: selected processor does not support `vsdot.s8 q11,q9,d5[0]' in ARM mode
/tmp/ccRqcaMJ.s:472: Error: selected processor does not support `vsdot.s8 q13,q8,d7[0]' in ARM mode
/tmp/ccRqcaMJ.s:474: Error: selected processor does not support `vsdot.s8 q9,q8,d6[0]' in ARM mode
/tmp/ccRqcaMJ.s:478: Error: selected processor does not support `vsdot.s8 q9,q8,d5[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49961: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-3x16c4-minmax-neondot.c.o] Error 1
/tmp/ccuyJ4D9.s: Assembler messages:
/tmp/ccuyJ4D9.s:64: Error: selected processor does not support `vsdot.s8 q9,q11,d7[0]' in ARM mode
/tmp/ccuyJ4D9.s:66: Error: selected processor does not support `vsdot.s8 q8,q10,d7[0]' in ARM mode
/tmp/ccuyJ4D9.s:69: Error: selected processor does not support `vsdot.s8 q9,q10,d7[1]' in ARM mode
/tmp/ccuyJ4D9.s:73: Error: selected processor does not support `vsdot.s8 q8,q10,d7[1]' in ARM mode
/tmp/ccuyJ4D9.s:130: Error: selected processor does not support `vsdot.s8 q9,q11,d7[0]' in ARM mode
/tmp/ccuyJ4D9.s:132: Error: selected processor does not support `vsdot.s8 q8,q10,d7[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:50031: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-1x8c4-minmax-neondot.c.o] Error 1
/tmp/ccRNmUcC.s: Assembler messages:
/tmp/ccRNmUcC.s:110: Error: selected processor does not support `vsdot.s8 q4,q11,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:111: Error: selected processor does not support `vsdot.s8 q2,q9,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:112: Error: selected processor does not support `vsdot.s8 q4,q10,d7[1]' in ARM mode
/tmp/ccRNmUcC.s:113: Error: selected processor does not support `vsdot.s8 q2,q8,d7[1]' in ARM mode
/tmp/ccRNmUcC.s:116: Error: selected processor does not support `vsdot.s8 q0,q11,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:117: Error: selected processor does not support `vsdot.s8 q15,q9,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:118: Error: selected processor does not support `vsdot.s8 q0,q10,d7[1]' in ARM mode
/tmp/ccRNmUcC.s:119: Error: selected processor does not support `vsdot.s8 q15,q8,d7[1]' in ARM mode
/tmp/ccRNmUcC.s:123: Error: selected processor does not support `vsdot.s8 q1,q11,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:124: Error: selected processor does not support `vsdot.s8 q14,q9,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:125: Error: selected processor does not support `vsdot.s8 q1,q10,d7[1]' in ARM mode
/tmp/ccRNmUcC.s:126: Error: selected processor does not support `vsdot.s8 q14,q8,d7[1]' in ARM mode
/tmp/ccRNmUcC.s:129: Error: selected processor does not support `vsdot.s8 q13,q11,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:130: Error: selected processor does not support `vsdot.s8 q12,q9,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:131: Error: selected processor does not support `vsdot.s8 q13,q10,d7[1]' in ARM mode
/tmp/ccRNmUcC.s:132: Error: selected processor does not support `vsdot.s8 q12,q8,d7[1]' in ARM mode
/tmp/ccRNmUcC.s:300: Error: selected processor does not support `vsdot.s8 q4,q10,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:301: Error: selected processor does not support `vsdot.s8 q2,q9,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:303: Error: selected processor does not support `vsdot.s8 q0,q10,d6[0]' in ARM mode
/tmp/ccRNmUcC.s:304: Error: selected processor does not support `vsdot.s8 q15,q9,d6[0]' in ARM mode
/tmp/ccRNmUcC.s:305: Error: selected processor does not support `vsdot.s8 q1,q10,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:307: Error: selected processor does not support `vsdot.s8 q13,q10,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:309: Error: selected processor does not support `vsdot.s8 q14,q9,d7[0]' in ARM mode
/tmp/ccRNmUcC.s:311: Error: selected processor does not support `vsdot.s8 q12,q9,d7[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49975: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-4x8c4-minmax-neondot.c.o] Error 1
/tmp/ccNllqu0.s: Assembler messages:
/tmp/ccNllqu0.s:176: Error: selected processor does not support `vsdot.s8 q6,q11,d4[0]' in ARM mode
/tmp/ccNllqu0.s:177: Error: selected processor does not support `vsdot.s8 q4,q11,d5[0]' in ARM mode
/tmp/ccNllqu0.s:178: Error: selected processor does not support `vsdot.s8 q15,q11,d6[0]' in ARM mode
/tmp/ccNllqu0.s:179: Error: selected processor does not support `vsdot.s8 q14,q11,d7[0]' in ARM mode
/tmp/ccNllqu0.s:183: Error: selected processor does not support `vsdot.s8 q7,q12,d4[0]' in ARM mode
/tmp/ccNllqu0.s:184: Error: selected processor does not support `vsdot.s8 q5,q12,d5[0]' in ARM mode
/tmp/ccNllqu0.s:186: Error: selected processor does not support `vsdot.s8 q0,q12,d6[0]' in ARM mode
/tmp/ccNllqu0.s:189: Error: selected processor does not support `vsdot.s8 q1,q12,d7[0]' in ARM mode
/tmp/ccNllqu0.s:195: Error: selected processor does not support `vsdot.s8 q9,q11,d5[0]' in ARM mode
/tmp/ccNllqu0.s:196: Error: selected processor does not support `vsdot.s8 q8,q11,d7[0]' in ARM mode
/tmp/ccNllqu0.s:199: Error: selected processor does not support `vsdot.s8 q13,q11,d4[0]' in ARM mode
/tmp/ccNllqu0.s:200: Error: selected processor does not support `vsdot.s8 q12,q10,d4[0]' in ARM mode
/tmp/ccNllqu0.s:203: Error: selected processor does not support `vsdot.s8 q9,q10,d5[0]' in ARM mode
/tmp/ccNllqu0.s:211: Error: selected processor does not support `vsdot.s8 q9,q11,d6[0]' in ARM mode
/tmp/ccNllqu0.s:215: Error: selected processor does not support `vsdot.s8 q9,q10,d7[0]' in ARM mode
/tmp/ccNllqu0.s:221: Error: selected processor does not support `vsdot.s8 q11,q10,d6[0]' in ARM mode
/tmp/ccNllqu0.s:225: Error: selected processor does not support `vsdot.s8 q7,q10,d4[1]' in ARM mode
/tmp/ccNllqu0.s:226: Error: selected processor does not support `vsdot.s8 q5,q10,d5[1]' in ARM mode
/tmp/ccNllqu0.s:227: Error: selected processor does not support `vsdot.s8 q0,q10,d6[1]' in ARM mode
/tmp/ccNllqu0.s:228: Error: selected processor does not support `vsdot.s8 q1,q10,d7[1]' in ARM mode
/tmp/ccNllqu0.s:231: Error: selected processor does not support `vsdot.s8 q6,q9,d4[1]' in ARM mode
/tmp/ccNllqu0.s:232: Error: selected processor does not support `vsdot.s8 q4,q9,d5[1]' in ARM mode
/tmp/ccNllqu0.s:233: Error: selected processor does not support `vsdot.s8 q15,q9,d6[1]' in ARM mode
/tmp/ccNllqu0.s:234: Error: selected processor does not support `vsdot.s8 q14,q9,d7[1]' in ARM mode
/tmp/ccNllqu0.s:240: Error: selected processor does not support `vsdot.s8 q10,q9,d5[1]' in ARM mode
/tmp/ccNllqu0.s:241: Error: selected processor does not support `vsdot.s8 q13,q9,d4[1]' in ARM mode
/tmp/ccNllqu0.s:244: Error: selected processor does not support `vsdot.s8 q12,q8,d4[1]' in ARM mode
/tmp/ccNllqu0.s:245: Error: selected processor does not support `vsdot.s8 q11,q8,d6[1]' in ARM mode
/tmp/ccNllqu0.s:248: Error: selected processor does not support `vsdot.s8 q10,q8,d5[1]' in ARM mode
/tmp/ccNllqu0.s:255: Error: selected processor does not support `vsdot.s8 q10,q9,d6[1]' in ARM mode
/tmp/ccNllqu0.s:260: Error: selected processor does not support `vsdot.s8 q10,q9,d7[1]' in ARM mode
/tmp/ccNllqu0.s:264: Error: selected processor does not support `vsdot.s8 q9,q8,d7[1]' in ARM mode
/tmp/ccNllqu0.s:658: Error: selected processor does not support `vsdot.s8 q7,q9,d7[0]' in ARM mode
/tmp/ccNllqu0.s:659: Error: selected processor does not support `vsdot.s8 q6,q8,d7[0]' in ARM mode
/tmp/ccNllqu0.s:660: Error: selected processor does not support `vsdot.s8 q5,q9,d6[0]' in ARM mode
/tmp/ccNllqu0.s:661: Error: selected processor does not support `vsdot.s8 q4,q8,d6[0]' in ARM mode
/tmp/ccNllqu0.s:665: Error: selected processor does not support `vsdot.s8 q0,q9,d5[0]' in ARM mode
/tmp/ccNllqu0.s:667: Error: selected processor does not support `vsdot.s8 q15,q8,d5[0]' in ARM mode
/tmp/ccNllqu0.s:669: Error: selected processor does not support `vsdot.s8 q1,q9,d4[0]' in ARM mode
/tmp/ccNllqu0.s:670: Error: selected processor does not support `vsdot.s8 q14,q8,d4[0]' in ARM mode
/tmp/ccNllqu0.s:678: Error: selected processor does not support `vsdot.s8 q10,q8,d7[0]' in ARM mode
/tmp/ccNllqu0.s:679: Error: selected processor does not support `vsdot.s8 q13,q9,d7[0]' in ARM mode
/tmp/ccNllqu0.s:684: Error: selected processor does not support `vsdot.s8 q10,q9,d6[0]' in ARM mode
/tmp/ccNllqu0.s:689: Error: selected processor does not support `vsdot.s8 q10,q8,d6[0]' in ARM mode
/tmp/ccNllqu0.s:694: Error: selected processor does not support `vsdot.s8 q10,q9,d5[0]' in ARM mode
/tmp/ccNllqu0.s:699: Error: selected processor does not support `vsdot.s8 q10,q9,d4[0]' in ARM mode
/tmp/ccNllqu0.s:704: Error: selected processor does not support `vsdot.s8 q9,q8,d5[0]' in ARM mode
/tmp/ccNllqu0.s:708: Error: selected processor does not support `vsdot.s8 q9,q8,d4[0]' in ARM mode
/tmp/ccWKfZvp.s: Assembler messages:
/tmp/ccWKfZvp.s:65: Error: selected processor does not support `vsdot.s8 q10,q14,q8' in ARM mode
/tmp/ccWKfZvp.s:68: Error: selected processor does not support `vsdot.s8 q12,q13,q8' in ARM mode
/tmp/ccWKfZvp.s:71: Error: selected processor does not support `vsdot.s8 q9,q13,q8' in ARM mode
/tmp/ccWKfZvp.s:75: Error: selected processor does not support `vsdot.s8 q11,q13,q8' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49989: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-4x16c4-minmax-neondot.c.o] Error 1
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:50045: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-1x8c8-minmax-neondot-ld64.c.o] Error 1
/tmp/ccw5qRTa.s: Assembler messages:
/tmp/ccw5qRTa.s:183: Error: selected processor does not support `vsdot.s8 q6,q7,d2[0]' in ARM mode
/tmp/ccw5qRTa.s:184: Error: selected processor does not support `vsdot.s8 q4,q7,d3[0]' in ARM mode
/tmp/ccw5qRTa.s:185: Error: selected processor does not support `vsdot.s8 q10,q7,d4[0]' in ARM mode
/tmp/ccw5qRTa.s:186: Error: selected processor does not support `vsdot.s8 q15,q7,d5[0]' in ARM mode
/tmp/ccw5qRTa.s:188: Error: selected processor does not support `vsdot.s8 q11,q7,d6[0]' in ARM mode
/tmp/ccw5qRTa.s:189: Error: selected processor does not support `vsdot.s8 q5,q9,d2[0]' in ARM mode
/tmp/ccw5qRTa.s:190: Error: selected processor does not support `vsdot.s8 q0,q9,d3[0]' in ARM mode
/tmp/ccw5qRTa.s:193: Error: selected processor does not support `vsdot.s8 q10,q9,d4[0]' in ARM mode
/tmp/ccw5qRTa.s:196: Error: selected processor does not support `vsdot.s8 q12,q9,d5[0]' in ARM mode
/tmp/ccw5qRTa.s:197: Error: selected processor does not support `vsdot.s8 q14,q9,d6[0]' in ARM mode
/tmp/ccw5qRTa.s:198: Error: selected processor does not support `vsdot.s8 q13,q9,d7[0]' in ARM mode
/tmp/ccw5qRTa.s:201: Error: selected processor does not support `vsdot.s8 q10,q7,d7[0]' in ARM mode
/tmp/ccw5qRTa.s:206: Error: selected processor does not support `vsdot.s8 q6,q9,d2[1]' in ARM mode
/tmp/ccw5qRTa.s:207: Error: selected processor does not support `vsdot.s8 q5,q8,d2[1]' in ARM mode
/tmp/ccw5qRTa.s:208: Error: selected processor does not support `vsdot.s8 q4,q9,d3[1]' in ARM mode
/tmp/ccw5qRTa.s:209: Error: selected processor does not support `vsdot.s8 q0,q8,d3[1]' in ARM mode
/tmp/ccw5qRTa.s:210: Error: selected processor does not support `vsdot.s8 q10,q9,d7[1]' in ARM mode
/tmp/ccw5qRTa.s:212: Error: selected processor does not support `vsdot.s8 q15,q9,d5[1]' in ARM mode
/tmp/ccw5qRTa.s:213: Error: selected processor does not support `vsdot.s8 q1,q9,d4[1]' in ARM mode
/tmp/ccw5qRTa.s:214: Error: selected processor does not support `vsdot.s8 q12,q8,d5[1]' in ARM mode
/tmp/ccw5qRTa.s:216: Error: selected processor does not support `vsdot.s8 q11,q9,d6[1]' in ARM mode
/tmp/ccw5qRTa.s:217: Error: selected processor does not support `vsdot.s8 q14,q8,d6[1]' in ARM mode
/tmp/ccw5qRTa.s:220: Error: selected processor does not support `vsdot.s8 q13,q8,d7[1]' in ARM mode
/tmp/ccw5qRTa.s:221: Error: selected processor does not support `vsdot.s8 q1,q8,d4[1]' in ARM mode
/tmp/ccw5qRTa.s:513: Error: selected processor does not support `vsdot.s8 q6,q9,d7[0]' in ARM mode
/tmp/ccw5qRTa.s:514: Error: selected processor does not support `vsdot.s8 q5,q8,d7[0]' in ARM mode
/tmp/ccw5qRTa.s:515: Error: selected processor does not support `vsdot.s8 q4,q9,d6[0]' in ARM mode
/tmp/ccw5qRTa.s:516: Error: selected processor does not support `vsdot.s8 q0,q8,d6[0]' in ARM mode
/tmp/ccw5qRTa.s:517: Error: selected processor does not support `vsdot.s8 q15,q9,d4[0]' in ARM mode
/tmp/ccw5qRTa.s:519: Error: selected processor does not support `vsdot.s8 q12,q8,d4[0]' in ARM mode
/tmp/ccw5qRTa.s:520: Error: selected processor does not support `vsdot.s8 q3,q9,d5[0]' in ARM mode
/tmp/ccw5qRTa.s:521: Error: selected processor does not support `vsdot.s8 q11,q9,d3[0]' in ARM mode
/tmp/ccw5qRTa.s:523: Error: selected processor does not support `vsdot.s8 q10,q9,d2[0]' in ARM mode
/tmp/ccw5qRTa.s:524: Error: selected processor does not support `vsdot.s8 q14,q8,d3[0]' in ARM mode
/tmp/ccw5qRTa.s:527: Error: selected processor does not support `vsdot.s8 q13,q8,d2[0]' in ARM mode
/tmp/ccw5qRTa.s:528: Error: selected processor does not support `vsdot.s8 q3,q8,d5[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:50003: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-6x8c4-minmax-neondot.c.o] Error 1
/tmp/cczsG4jB.s: Assembler messages:
/tmp/cczsG4jB.s:76: Error: selected processor does not support `vsdot.s8 q12,q2,q8' in ARM mode
/tmp/cczsG4jB.s:79: Error: selected processor does not support `vsdot.s8 q3,q2,q8' in ARM mode
/tmp/cczsG4jB.s:82: Error: selected processor does not support `vsdot.s8 q11,q2,q8' in ARM mode
/tmp/cczsG4jB.s:85: Error: selected processor does not support `vsdot.s8 q15,q2,q8' in ARM mode
/tmp/cczsG4jB.s:88: Error: selected processor does not support `vsdot.s8 q10,q2,q8' in ARM mode
/tmp/cczsG4jB.s:91: Error: selected processor does not support `vsdot.s8 q14,q2,q8' in ARM mode
/tmp/cczsG4jB.s:94: Error: selected processor does not support `vsdot.s8 q9,q2,q8' in ARM mode
/tmp/cczsG4jB.s:98: Error: selected processor does not support `vsdot.s8 q13,q2,q8' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:50073: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-1x16c8-minmax-neondot-ld64.c.o] Error 1
/tmp/cchtznlO.s: Assembler messages:
/tmp/cchtznlO.s:236: Error: selected processor does not support `vsdot.s8 q7,q12,d2[0]' in ARM mode
/tmp/cchtznlO.s:238: Error: selected processor does not support `vsdot.s8 q6,q11,d2[0]' in ARM mode
/tmp/cchtznlO.s:240: Error: selected processor does not support `vsdot.s8 q5,q12,d3[0]' in ARM mode
/tmp/cchtznlO.s:242: Error: selected processor does not support `vsdot.s8 q4,q11,d3[0]' in ARM mode
/tmp/cchtznlO.s:245: Error: selected processor does not support `vsdot.s8 q0,q12,d4[0]' in ARM mode
/tmp/cchtznlO.s:246: Error: selected processor does not support `vsdot.s8 q9,q11,d4[0]' in ARM mode
/tmp/cchtznlO.s:247: Error: selected processor does not support `vsdot.s8 q14,q12,d5[0]' in ARM mode
/tmp/cchtznlO.s:250: Error: selected processor does not support `vsdot.s8 q13,q11,d5[0]' in ARM mode
/tmp/cchtznlO.s:251: Error: selected processor does not support `vsdot.s8 q15,q11,d7[0]' in ARM mode
/tmp/cchtznlO.s:255: Error: selected processor does not support `vsdot.s8 q9,q12,d6[0]' in ARM mode
/tmp/cchtznlO.s:261: Error: selected processor does not support `vsdot.s8 q9,q12,d7[0]' in ARM mode
/tmp/cchtznlO.s:267: Error: selected processor does not support `vsdot.s8 q12,q11,d6[0]' in ARM mode
/tmp/cchtznlO.s:274: Error: selected processor does not support `vsdot.s8 q9,q11,d2[0]' in ARM mode
/tmp/cchtznlO.s:275: Error: selected processor does not support `vsdot.s8 q8,q10,d3[0]' in ARM mode
/tmp/cchtznlO.s:281: Error: selected processor does not support `vsdot.s8 q9,q10,d2[0]' in ARM mode
/tmp/cchtznlO.s:286: Error: selected processor does not support `vsdot.s8 q9,q11,d3[0]' in ARM mode
/tmp/cchtznlO.s:291: Error: selected processor does not support `vsdot.s8 q9,q11,d4[0]' in ARM mode
/tmp/cchtznlO.s:296: Error: selected processor does not support `vsdot.s8 q8,q10,d4[0]' in ARM mode
/tmp/cchtznlO.s:301: Error: selected processor does not support `vsdot.s8 q9,q11,d5[0]' in ARM mode
/tmp/cchtznlO.s:306: Error: selected processor does not support `vsdot.s8 q8,q10,d5[0]' in ARM mode
/tmp/cchtznlO.s:311: Error: selected processor does not support `vsdot.s8 q9,q11,d6[0]' in ARM mode
/tmp/cchtznlO.s:316: Error: selected processor does not support `vsdot.s8 q8,q11,d7[0]' in ARM mode
/tmp/cchtznlO.s:321: Error: selected processor does not support `vsdot.s8 q9,q10,d7[0]' in ARM mode
/tmp/cchtznlO.s:329: Error: selected processor does not support `vsdot.s8 q11,q10,d6[0]' in ARM mode
/tmp/cchtznlO.s:335: Error: selected processor does not support `vsdot.s8 q8,q9,d4[1]' in ARM mode
/tmp/cchtznlO.s:336: Error: selected processor does not support `vsdot.s8 q7,q10,d2[1]' in ARM mode
/tmp/cchtznlO.s:339: Error: selected processor does not support `vsdot.s8 q5,q10,d3[1]' in ARM mode
/tmp/cchtznlO.s:340: Error: selected processor does not support `vsdot.s8 q0,q10,d4[1]' in ARM mode
/tmp/cchtznlO.s:341: Error: selected processor does not support `vsdot.s8 q14,q10,d5[1]' in ARM mode
/tmp/cchtznlO.s:344: Error: selected processor does not support `vsdot.s8 q8,q10,d6[1]' in ARM mode
/tmp/cchtznlO.s:347: Error: selected processor does not support `vsdot.s8 q12,q9,d6[1]' in ARM mode
/tmp/cchtznlO.s:348: Error: selected processor does not support `vsdot.s8 q6,q9,d2[1]' in ARM mode
/tmp/cchtznlO.s:349: Error: selected processor does not support `vsdot.s8 q4,q9,d3[1]' in ARM mode
/tmp/cchtznlO.s:352: Error: selected processor does not support `vsdot.s8 q8,q10,d7[1]' in ARM mode
/tmp/cchtznlO.s:353: Error: selected processor does not support `vsdot.s8 q13,q9,d5[1]' in ARM mode
/tmp/cchtznlO.s:356: Error: selected processor does not support `vsdot.s8 q15,q9,d7[1]' in ARM mode
/tmp/cchtznlO.s:367: Error: selected processor does not support `vsdot.s8 q10,q12,d2[1]' in ARM mode
/tmp/cchtznlO.s:368: Error: selected processor does not support `vsdot.s8 q11,q8,d6[1]' in ARM mode
/tmp/cchtznlO.s:372: Error: selected processor does not support `vsdot.s8 q10,q8,d2[1]' in ARM mode
/tmp/cchtznlO.s:377: Error: selected processor does not support `vsdot.s8 q10,q12,d3[1]' in ARM mode
/tmp/cchtznlO.s:382: Error: selected processor does not support `vsdot.s8 q10,q8,d3[1]' in ARM mode
/tmp/cchtznlO.s:387: Error: selected processor does not support `vsdot.s8 q10,q12,d4[1]' in ARM mode
/tmp/cchtznlO.s:392: Error: selected processor does not support `vsdot.s8 q10,q8,d4[1]' in ARM mode
/tmp/cchtznlO.s:397: Error: selected processor does not support `vsdot.s8 q9,q8,d7[1]' in ARM mode
/tmp/cchtznlO.s:404: Error: selected processor does not support `vsdot.s8 q10,q12,d5[1]' in ARM mode
/tmp/cchtznlO.s:409: Error: selected processor does not support `vsdot.s8 q10,q8,d5[1]' in ARM mode
/tmp/cchtznlO.s:414: Error: selected processor does not support `vsdot.s8 q10,q12,d6[1]' in ARM mode
/tmp/cchtznlO.s:419: Error: selected processor does not support `vsdot.s8 q10,q12,d7[1]' in ARM mode
/tmp/cchtznlO.s:1117: Error: selected processor does not support `vsdot.s8 q7,q9,d7[0]' in ARM mode
/tmp/cchtznlO.s:1118: Error: selected processor does not support `vsdot.s8 q6,q8,d7[0]' in ARM mode
/tmp/cchtznlO.s:1119: Error: selected processor does not support `vsdot.s8 q5,q9,d6[0]' in ARM mode
/tmp/cchtznlO.s:1120: Error: selected processor does not support `vsdot.s8 q4,q8,d6[0]' in ARM mode
/tmp/cchtznlO.s:1124: Error: selected processor does not support `vsdot.s8 q12,q8,d5[0]' in ARM mode
/tmp/cchtznlO.s:1126: Error: selected processor does not support `vsdot.s8 q0,q9,d5[0]' in ARM mode
/tmp/cchtznlO.s:1134: Error: selected processor does not support `vsdot.s8 q14,q9,d4[0]' in ARM mode
/tmp/cchtznlO.s:1136: Error: selected processor does not support `vsdot.s8 q13,q8,d4[0]' in ARM mode
/tmp/cchtznlO.s:1140: Error: selected processor does not support `vsdot.s8 q12,q9,d3[0]' in ARM mode
/tmp/cchtznlO.s:1147: Error: selected processor does not support `vsdot.s8 q12,q9,d2[0]' in ARM mode
/tmp/cchtznlO.s:1148: Error: selected processor does not support `vsdot.s8 q15,q8,d2[0]' in ARM mode
/tmp/cchtznlO.s:1151: Error: selected processor does not support `vsdot.s8 q9,q8,d3[0]' in ARM mode
/tmp/cchtznlO.s:1162: Error: selected processor does not support `vsdot.s8 q10,q9,d7[0]' in ARM mode
/tmp/cchtznlO.s:1166: Error: selected processor does not support `vsdot.s8 q10,q8,d7[0]' in ARM mode
/tmp/cchtznlO.s:1171: Error: selected processor does not support `vsdot.s8 q10,q9,d6[0]' in ARM mode
/tmp/cchtznlO.s:1176: Error: selected processor does not support `vsdot.s8 q10,q8,d6[0]' in ARM mode
/tmp/cchtznlO.s:1181: Error: selected processor does not support `vsdot.s8 q10,q9,d5[0]' in ARM mode
/tmp/cchtznlO.s:1186: Error: selected processor does not support `vsdot.s8 q10,q8,d5[0]' in ARM mode
/tmp/cchtznlO.s:1191: Error: selected processor does not support `vsdot.s8 q10,q9,d4[0]' in ARM mode
/tmp/cchtznlO.s:1196: Error: selected processor does not support `vsdot.s8 q10,q8,d4[0]' in ARM mode
/tmp/cchtznlO.s:1201: Error: selected processor does not support `vsdot.s8 q10,q9,d3[0]' in ARM mode
/tmp/cchtznlO.s:1206: Error: selected processor does not support `vsdot.s8 q10,q9,d2[0]' in ARM mode
/tmp/cchtznlO.s:1211: Error: selected processor does not support `vsdot.s8 q9,q8,d3[0]' in ARM mode
/tmp/cchtznlO.s:1216: Error: selected processor does not support `vsdot.s8 q9,q8,d2[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:50017: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-6x16c4-minmax-neondot.c.o] Error 1
/tmp/ccJrNOda.s: Assembler messages:
/tmp/ccJrNOda.s:72: Error: selected processor does not support `vsdot.s8 q8,q13,d7[0]' in ARM mode
/tmp/ccJrNOda.s:74: Error: selected processor does not support `vsdot.s8 q11,q12,d7[0]' in ARM mode
/tmp/ccJrNOda.s:77: Error: selected processor does not support `vsdot.s8 q10,q12,d7[0]' in ARM mode
/tmp/ccJrNOda.s:80: Error: selected processor does not support `vsdot.s8 q9,q12,d7[0]' in ARM mode
/tmp/ccJrNOda.s:83: Error: selected processor does not support `vsdot.s8 q8,q12,d7[1]' in ARM mode
/tmp/ccJrNOda.s:86: Error: selected processor does not support `vsdot.s8 q11,q12,d7[1]' in ARM mode
/tmp/ccJrNOda.s:89: Error: selected processor does not support `vsdot.s8 q10,q12,d7[1]' in ARM mode
/tmp/ccJrNOda.s:93: Error: selected processor does not support `vsdot.s8 q9,q12,d7[1]' in ARM mode
/tmp/ccJrNOda.s:171: Error: selected processor does not support `vsdot.s8 q8,q13,d7[0]' in ARM mode
/tmp/ccJrNOda.s:173: Error: selected processor does not support `vsdot.s8 q11,q12,d7[0]' in ARM mode
/tmp/ccJrNOda.s:176: Error: selected processor does not support `vsdot.s8 q10,q12,d7[0]' in ARM mode
/tmp/ccJrNOda.s:180: Error: selected processor does not support `vsdot.s8 q9,q12,d7[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:50059: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-1x16c4-minmax-neondot.c.o] Error 1
/tmp/cceW7UTH.s: Assembler messages:
/tmp/cceW7UTH.s:78: Error: selected processor does not support `vsdot.s8 q10,q11,d6[0]' in ARM mode
/tmp/cceW7UTH.s:80: Error: selected processor does not support `vsdot.s8 q13,q12,d6[0]' in ARM mode
/tmp/cceW7UTH.s:84: Error: selected processor does not support `vsdot.s8 q9,q11,d7[0]' in ARM mode
/tmp/cceW7UTH.s:85: Error: selected processor does not support `vsdot.s8 q8,q12,d7[0]' in ARM mode
/tmp/cceW7UTH.s:87: Error: selected processor does not support `vsdot.s8 q13,q11,d6[1]' in ARM mode
/tmp/cceW7UTH.s:89: Error: selected processor does not support `vsdot.s8 q8,q11,d7[1]' in ARM mode
/tmp/cceW7UTH.s:92: Error: selected processor does not support `vsdot.s8 q10,q11,d6[1]' in ARM mode
/tmp/cceW7UTH.s:93: Error: selected processor does not support `vsdot.s8 q9,q11,d7[1]' in ARM mode
/tmp/cceW7UTH.s:168: Error: selected processor does not support `vsdot.s8 q13,q12,d6[0]' in ARM mode
/tmp/cceW7UTH.s:169: Error: selected processor does not support `vsdot.s8 q8,q12,d7[0]' in ARM mode
/tmp/cceW7UTH.s:171: Error: selected processor does not support `vsdot.s8 q10,q11,d6[0]' in ARM mode
/tmp/cceW7UTH.s:172: Error: selected processor does not support `vsdot.s8 q9,q11,d7[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:50087: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o] Error 1
make[2]: Leaving directory '/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk'
make[1]: *** [CMakeFiles/Makefile2:6654: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/all] Error 2
make[1]: Leaving directory '/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk'
make: *** [Makefile:139: all] Error 2
guanghui.wan@rd01:/mnt/fileroot/guanghui.wan/tensorflow/tensorflow$

Relevant log output
[ 79%] Building C object _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o
cd /mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/_deps/xnnpack-build && /mnt/fileroot/guanghui.wan/nanoQ/Algorithm/tools/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -DEIGEN_MPL2_ONLY -DFXDIV_USE_INLINE_ASSEMBLY=0 -DNOMINMAX=1 -DPTHREADPOOL_NO_DEPRECATED_API=1 -DXNN_ENABLE_ARM_BF16=0 -DXNN_ENABLE_ARM_DOTPROD=1 -DXNN_ENABLE_ARM_FP16_SCALAR=1 -DXNN_ENABLE_ARM_FP16_VECTOR=1 -DXNN_ENABLE_ARM_I8MM=0 -DXNN_ENABLE_ASSEMBLY=1 -DXNN_ENABLE_CPUINFO=1 -DXNN_ENABLE_DWCONV_MULTIPASS=0 -DXNN_ENABLE_GEMM_M_SPECIALIZATION=1 -DXNN_ENABLE_JIT=0 -DXNN_ENABLE_MEMOPT=1 -DXNN_ENABLE_RISCV_VECTOR=1 -DXNN_ENABLE_SPARSE=1 -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/third_party/xla/third_party/tsl -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/xnnpack/src -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/pthreadpool-source/include -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/FXdiv-source/include -I/mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/FP16-source/include -march=armv8-a -mfpu=neon-vfpv4 -funsafe-math-optimizations -mfp16-format=ieee -O3 -DNDEBUG -std=c99 -fPIC -Wno-psabi -O2 -pthread  -fno-math-errno  -marm  -march=armv8.2-a+dotprod -mfpu=neon-fp-armv8  -MD -MT _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o -MF CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o.d -o CMakeFiles/microkernels-all.dir/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c.o -c /mnt/fileroot/guanghui.wan/tensorflow/tensorflow/build_sdk/xnnpack/src/qd8-f32-qc8w-gemm/gen/qd8-f32-qc8w-gemm-2x8c4-minmax-neondot.c
/tmp/ccrZ5z20.s: Assembler messages:
/tmp/ccrZ5z20.s:75: Error: selected processor does not support `vsdot.s8 q14,q12,d7[0]' in ARM mode
/tmp/ccrZ5z20.s:76: Error: selected processor does not support `vsdot.s8 q10,q9,d7[0]' in ARM mode
/tmp/ccrZ5z20.s:77: Error: selected processor does not support `vsdot.s8 q14,q11,d7[1]' in ARM mode
/tmp/ccrZ5z20.s:78: Error: selected processor does not support `vsdot.s8 q10,q8,d7[1]' in ARM mode
/tmp/ccrZ5z20.s:134: Error: selected processor does not support `vsdot.s8 q14,q9,d7[0]' in ARM mode
/tmp/ccrZ5z20.s:135: Error: selected processor does not support `vsdot.s8 q10,q8,d7[0]' in ARM mode
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:49877: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/qd8-f32-qc4w-gemm/gen/qd8-f32-qc4w-gemm-1x8c4-minmax-neondot.c.o] Error 1

@hfwanguanghui Could you please make sure that you are using the correct version of CMake?
As you are using Linux so please confirm if you have used right command for CMake as below,
cmake -S tensorflow/lite -B build -DCMAKE_TOOLCHAIN_FILE=path/to/toolchain.cmake

The toolchain file that you are using needs to be corrected. The toolchain file should specify the compiler and linker that you want to use for cross compiling TensorFlow Lite.
If you are still having issues then please provide more information about your environment and the steps that you are using to build the package.
Thank you!

I have the same issue and I can't solve the problem
this is the link for my issue


Android tracking fix

I can't test this. I can't get the Android simulator to simulate my locations.


Where to get Media URLs for MeetingSessionCreator

Hi, I wanted to know more about how you got the urls for the MeetingSessionCreator ?
I cannot find the details on the AWS chime for the following:
mediaPlacementAudioHostUrl:
mediaPlacementAudioFallbackUrl:
mediaPlacementSignalingUrl:
mediaPlacementTurnControlUrl:

Request you to provide more information on how to setup the plugin with my AWS credentials.
Regards,
Mohit

In case anyone else wonders: you need a server with the AWS SDK.
Example of how to handle that:
'use strict';

const {v4: uuidv4} = require('uuid');

const AWS = require('aws-sdk');

let chime;

function init()
{
    if (chime)
        return;

    AWS.config.loadFromPath('./secrets/aws.json');

    // You must currently use us-east-1 as the region (you can select a MediaRegion in the following step).
    chime = new AWS.Chime({region: 'us-east-1'});

    // https://github.com/aws/amazon-chime-sdk-js/issues/283
    // No DNS resolution to chime.<region>.amazonaws.com
    chime.endpoint = new AWS.Endpoint('https://service.chime.aws.amazon.com');
}

exports.listMeetings = async function listMeetings()
{
    init();

    const meetings = await chime.listMeetings().promise();

    return meetings.Meetings;
}

exports.listAttendees = async function listAttendees(meetingId)
{
    init();

    const attendees = await chime.listAttendees({MeetingId: meetingId}).promise();

    return attendees.Attendees;
}

exports.createMeeting = async function createMeeting(externalMeetingId)
{
    init();

    const clientRequestToken = uuidv4();
    // eu-central-1 = Frankfurt, Germany
    const mediaRegion = 'eu-central-1';
    const params =
        {
            ClientRequestToken: clientRequestToken,
            ExternalMeetingId: externalMeetingId,
            MediaRegion: mediaRegion
        };

    const meeting = await chime.createMeeting(params).promise();

    return meeting.Meeting;
}

exports.createAttendee = async function createAttendee(chimeMeetingId, externalUserId)
{
    init();

    const params =
        {
            ExternalUserId: externalUserId,
            MeetingId: chimeMeetingId
        };

    const attendee = await chime.createAttendee(params).promise();

    return attendee.Attendee;
}

Thank You !! Got it


docs: add vscode setup and PR naming guidelines

What this PR does

Add instructions for setting up VSCode environment
Add guidelines for naming PRs

How it was tested

Documentation only

PR checklist

[x] No API keys or other secrets committed to source?
[x] New functionality is added alongside appropriate tests?
[x] All source files have the following header?

# Copyright (c) {YEAR} Cohere Inc. and its affiliates.
#
# Licensed under the MIT License (the "License");
# you may not use this file except in compliance with the License.
#
# You may obtain a copy of the License in the LICENSE file at the top
# level of this repository.

I searched for PR naming convention but little comes up.

I agree with mads that probably defining the types is great.
Thanks for pointing out the conventions are for commit messages! IMO PR semantic naming should more general and some types for commit messages might rarely be used. How about just keeping the feat, fix and the rest will likely fall into the other category?

Added clarification that this is for PR titles, and their definitions here
1d1326c

I personally think an other category might be easily misused as a too-easy catch-all! I also find myself opening docs, style, and test PRs often.


update to group_by

this pr updates the the exports code example to 'group_by' and not 'group_bys'. it also update the saved queries parameter too.  reported by Steve Dowling here: https://dbt-labs.slack.com/archives/C02NCQ9483C/p1707782794575719

hey @nghi-ly ! thanks can you rereview pls


Tempo Change of Audio?

Yes, speed change and tempo change are two different aspects of audio manipulation.
Increasing speed increases sampling ratio and hence pitch also increases with speed of audio.
But increasing tempo only results in increase of playback speed, it works by time stretching phenomenon.
I am using this library in my project, where I need to increase the tempo of audio being played.
Well, I have been able to change speed of audio, but could find any way to increase tempo of the audio.
Can you help me with this? If its not  provided by this library,  Any mathematical algo to change this would be sufficient....

Hi Sourav,
Beep doesn't have this capability currently.
You already mentioned "time stretching", I'm sure you can find some algorithms using those terms. But it's a difficult subject & I'm not familiar enough to help you with this.


SRVKE-1523: Re-add removed HPA for ingress and filter

As per title

/hold we need to agree to have https://github.com/openshift-knative/serverless-operator/pull/2287 in the same release

@pierDipi should we unhold?


in pyspark how should I read the type: array the struct, after reading the xml?

Hi Hyukjin !
in pyspark how  I can to read the data type: array, struct type, after reading the xml? My xml has no fixed structure. Sometimes is Array in another xml is struct?
df_xml = spark.read.format('com.databricks.spark.xml').options(rowTag='ARTIGOS_PUBLICADOS', nullValue="", ).load(path_long)
best regards!!

I think we should avoid the schema inference and set the explicit schema. There should be a limitation as XML is semi-structured data ...


Update README.md

Hello i am Andres Lopez, i will learn about this tool to programming in COBOL languaje

Hello i am Andres Lopez, i will learn about this tool to programming in COBOL language in any plataform

Hello i am Andres Lopez, i will learn about this tool to programming in COBOL language in others plataforms