added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| created
timestamp[us]date 2001-10-09 16:19:16
2025-01-01 03:51:31
| id
stringlengths 4
10
| metadata
dict | source
stringclasses 2
values | text
stringlengths 0
1.61M
|
|---|---|---|---|---|---|
2025-04-01T06:38:38.181685
| 2015-01-14T09:44:17
|
54302048
|
{
"authors": [
"dopcn",
"kastiglione"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5782",
"repo": "facebook/chisel",
"url": "https://github.com/facebook/chisel/pull/72"
}
|
gharchive/pull-request
|
add ppath command
Print application's 'Documents' directory path.
@dopcn What do you think about having option flags to allow the desired directory to be opened in Terminal, or maybe Finder as well? For example ppath -t to open in Terminal. These don't need to be added to this pull request, but they'd be nice to add sooner or later.
@dopcn What do you think of the comments I made?
@kastiglione sorry, back and working on it now...
Update copy to the pasteboard before print
Thanks @dopcn, I'm happy to accept this. Before that, can you merge from master because there are now conflicts.
Thanks @dopcn!
|
2025-04-01T06:38:38.189494
| 2022-06-02T08:56:37
|
1257896587
|
{
"authors": [
"josecarneiro",
"todinhvin"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5783",
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/12459"
}
|
gharchive/issue
|
Can't run project
I can't run the server in this project. Please help me. This error bellow. Thank you so much
express-session deprecated req.secret; provide secret option index.js:64:9
/home/lap12703/Code/kahoot-clone/node_modules/passport-auth0/lib/index.js:36
throw new Error('You must provide the ' + k + ' configuration value to use passport-auth0.');
^
Error: You must provide the domain configuration value to use passport-auth0.
This is not an issue with create-react-app, you're probably running an express server and forgot to pass the express-session middleware a secret option. Refer to the express-session package documentation.
|
2025-04-01T06:38:38.198851
| 2018-05-23T07:06:31
|
325574607
|
{
"authors": [
"Timer",
"vishu9219"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5784",
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/4506"
}
|
gharchive/issue
|
Service Controller not rendering
Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes, no issue with dependency.
Package.json
{
"name": "public",
"version": "0.1.0",
"private": true,
"homepage": "./",
"dependencies": {
"bootstrap": "^3.3.7",
"lodash": "^4.17.5",
"prop-types": "^15.6.1",
"react": "^16.3.2",
"react-dom": "^16.3.2",
"react-render-html": "^0.6.0",
"react-router-dom": "^4.2.2",
"react-scripts": "1.1.4",
"reactstrap": "^5.0.0-beta.3"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "jest",
"eject": "react-scripts eject"
},
"devDependencies": {
"babel-jest": "^22.4.3",
"babel-preset-env": "^1.6.1",
"babel-preset-react": "^6.24.1",
"jest": "^22.4.3",
"react-test-renderer": "^16.3.2"
}
}
12:22:10 › npm --version
5.6.0
Environment
Development
Steps to Reproduce
You launch react application
Let's say react is running on localhost:3000
Setup a proxy server which takes the request on localhost:4000.
All the request coming from localhost:4000/xyzabc should redirect to localhost:3000
Expected Behavior
Whatever coming on localhost:3000 should come on localhost:4000/xyzabc
Actual Behavior
JS CSS everything is getting downloaded but nothing is showing on UI. UI is totally blank
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
Closing as a duplicate of #4468, this is a known issue. Sorry!
It should be fixed in v2.
|
2025-04-01T06:38:38.203924
| 2019-08-29T06:31:01
|
486763991
|
{
"authors": [
"bullettrang",
"fengxinming"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5785",
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/7606"
}
|
gharchive/issue
|
Failed to compile after configuring rules
{
"extends": "react-app",
"rules": {
"no-unused-expressions": "off"
}
}
Failed to compile.
./src/components/Tree/index.js
Line 24: Expected an assignment or function call and instead saw an expression no-unused-expressions
Search for the keywords to learn more about each error.
Can you post your index.js file?
@bullettrang
class TreeItem extends PureComponent {
render() {
const { item, selected, isFirst, isLast, folded, onFold, onClickItem } = this.props;
const { children, text } = item;
let fragment;
// 节点块样式
let itemCls = isFirst
? isFirst === isLast
? 'l-onlychild'
: 'l-first'
: isLast
? 'l-last'
: '';
if (children) { // 文件夹
const lastIndex = children && (children.length - 1);
// 节点样式
let expandCls = '';
let folderCls = '';
// eslint-disable-next-line no-unused-expressions
folded
? (expandCls = 'l-expandable-close', folderCls = 'l-tree-icon-folder')
: (expandCls = 'l-expandable-open', folderCls = 'l-tree-icon-folder-open');
const isLastFolder = isLast;
where is the return statement for your render()?
https://stackoverflow.com/questions/53996916/unable-to-turn-off-eslint-no-unused-expressions
Did you already take a look at above link?
Also what happens if you put 'folded' on the same line with the ternary expression like below?
// eslint-disable-next-line no-unused-expressions folded ? (expandCls = 'l-expandable-close', folderCls = 'l-tree-icon-folder') : (expandCls = 'l-expandable-open', folderCls = 'l-tree-icon-folder-open'); const isLastFolder = isLast;
Seems like putting certain statements on a separate line throws the 'Expected an assignment or function call and instead saw an expression no-unused-expressions' as explained by the link below with the return statement.
https://stackoverflow.com/questions/53013437/expected-assignment-or-function-call-no-unused-expressions-reactjs
@bullettrang The issue means I disabled this eslint rule, but it was compiled failed.
|
2025-04-01T06:38:38.208938
| 2019-02-10T01:52:48
|
408491235
|
{
"authors": [
"JBallin",
"ianschmitz"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5786",
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/pull/6386"
}
|
gharchive/pull-request
|
[docs] revert removal of newlines from html
An unintended change was merged in #6062
I'm not seeing the changed files here on GitHub. Can you clarify what snuck through?
@ianschmitz it seems to be something that husky is doing automatically, and unfortunately I'm unable to override it. The form tag is being converted to one line:
https://github.com/facebook/create-react-app/pull/6062/files#diff-167d7aa95e8f35443e07dd102611e442L48
Ah yes you mean prettier. I wasn't aware they format code blocks inside of markdown files: https://twitter.com/bohdan_kh/status/1012367393656483841.
You should be able to get prettier to ignore that code block and restore the formatting to how it was previously: https://prettier.io/docs/en/ignore.html#range-ignore
Do you mind using the range ignore instead to just cover the code block?
@ianschmitz, should be ready now (FYI). Cheers.
Hmm, i'm not sure why but something looks off in the docs in this PR:
https://deploy-preview-6386--create-react-app.netlify.com/create-react-app/docs/adding-custom-environment-variables
You'll see the section that was edited here looks broken compared to master:
https://facebook.github.io/create-react-app/docs/adding-custom-environment-variables
I was able to fix the new issue with the code displaying properly by adding space above and below the code block, but prettier is not being ignored. I think it may make sense to just leave this as is and close the PR, thoughts?
|
2025-04-01T06:38:38.210261
| 2020-05-15T05:53:26
|
618717299
|
{
"authors": [
"eddiemonge",
"sarupbanskota"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5787",
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/pull/9013"
}
|
gharchive/pull-request
|
ZEIT Now → Vercel
ZEIT has rebranded to Vercel.
This PR updates the deployment section to reflect the new name.
#9099 is a more comprehensive version of this
|
2025-04-01T06:38:38.224427
| 2023-11-09T17:55:31
|
1986134557
|
{
"authors": [
"mohamedsaleh1984",
"slorber"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5788",
"repo": "facebook/docusaurus",
"url": "https://github.com/facebook/docusaurus/issues/9524"
}
|
gharchive/issue
|
Navigate to page sections using # doesn't work
Have you read the Contributing Guidelines on issues?
[X] I have read the Contributing Guidelines on issues.
Prerequisites
[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).
Description
when you paste the url including the section, the browser doesn't navigate to the section mentioned after # in th URL
https://dev2-everoed.evero.com/docs/-screen-descriptions/billing/billing_billing_claimbatchpending#raise-issue-button
You can notice the scroll doesn't move down to the bottom of the page.
Reproducible demo
No response
Steps to reproduce
Open https://dev2-everoed.evero.com/docs/-screen-descriptions/billing/billing_billing_claimbatchpending
Click Videos on the right side
Copy the URL
https://dev2-everoed.evero.com/docs/-screen-descriptions/billing/billing_billing_claimbatchpending#raise-issue-button
Paste in new tab (Doesn't scroll to videos) as original page does
Expected behavior
scroll down to the section mentioned from the URL # value
Actual behavior
The scroll doesn't move down to the section
Your environment
Public source code: NA
Public site URL: https://dev2-everoed.evero.com/
Docusaurus version used: 3.0.0
Environment name and version (e.g. Chrome 89, Node.js 16.4): Chrome Version 118.0.5993.89
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Windows
We have created Test user account for you
Username: etester
Password: DocusaurusTest123!
Self-service
[ ] I'd be willing to fix this bug myself.
This is not a Docusaurus bug, but a bad config of your host.
Your host should serve the appropriate static html file built by Docusaurus, but does not currently and always serve first the html of your homepage. It's only React that finally fixes the UI by rendering the correct page client-side.
This can easily be seen because your homepage "flashes" when you load any page.
This is what I see if I disable JS for example.
If your host is configured properly then you should see the good page content even with JS disabled.
If you don't know how to host a static deployment, then use Vercel, Netlify or another CDN that does it correctly for you out of the box. We can't help you configuring appropriately your custom setup.
we have built custom compoenent to serve dynamic content.
This is our docusourus config file., package if you have can spot an issue please let me know.
The project was setup many years ago and I don't know what's the correct setup for it.
docusaurus.config.js
const path = require("path");
const isDevelopment = process.env.NODE_ENV == "development";
module.exports = {
onBrokenLinks: "ignore",
title: "Our Digital Learning Repository",
tagline:
"eVero Ed is home to eVero-made resources and provides quick access to guidance documents, videos and recordings, a listing of scheduled webinars, and detailed release notifications.",
url: "https://evero.com",
baseUrl: "/",
baseUrlIssueBanner: false,
favicon: "img/Ed_MorePolished2.svg",
organizationName: "evero",
projectName: "ed",
customFields: {
isDev: isDevelopment,
devServer: "https://localhost:44312",
},
scripts: [
{
src: "/external/accessibe.js",
async: true,
},
{
src: "https://static.evero.com/evero-shared-all.js",
async: true,
},
],
themeConfig: {
navbar: {
title: "eVero Ed",
logo: {
alt: "eVero Ed Logo",
src: "img/FlatEd.png",
},
items: [
{
type: "doc",
label: "Guidance",
position: "left",
className: "spacing-nav-item",
docId: "home",
},
{
type: "docSidebar",
position: "left",
label: "Screen Descriptions",
sidebarId: "barScreenDescriptions",
className: "spacing-nav-item",
}
,
{
to: "videos-v2",
label: "Videos",
position: "left",
className: "spacing-nav-item",
},
{
to: "webinars",
label: "Webinars",
position: "left",
className: "spacing-nav-item",
},
{
type: "doc",
label: "Release Notifications",
position: "left",
className: "spacing-nav-item",
sidebarId: "barNotifications",
docId: "releases",
},
{
to: "contact-us",
label: "Contact Us",
position: "left",
className: "spacing-nav-item",
},
].filter((x) => !!x),
},
footer: {
style: "dark",
links: [
],
copyright: `Copyright © ${new Date().getFullYear()} eVero Corporation`,
},
},
presets: [
[
"@docusaurus/preset-classic",
{
docs: {
sidebarPath: require.resolve("./sidebars.js"),
// editUrl: "https://github.com/facebook/docusaurus/edit/master/website/"
},
blog: {
showReadingTime: true,
// editUrl: "https://github.com/facebook/docusaurus/edit/master/website/blog/",
},
theme: {
customCss: require.resolve("./src/css/custom.css"),
},
},
],
],
plugins: [
require.resolve("docusaurus-lunr-search"),
path.resolve(__dirname, "./plugins/event-plugin"),
// '@docusaurus/plugin-google-gtag'
],
};
package.json
{
"name": "evero-da-documentation",
"version": "0.0.0",
"private": true,
"scripts": {
"start": "docusaurus start",
"build": "docusaurus build",
"swizzle": "docusaurus swizzle",
"deploy": "docusaurus deploy",
"prodtest":"rm -r build & npm run build & cd build & npx http-server & explorer http://<IP_ADDRESS>:8081/"
},
"dependencies": {
"@docusaurus/core": "2.4.1",
"@docusaurus/plugin-content-pages": "2.4.1",
"@docusaurus/plugin-google-gtag": "2.4.1",
"@docusaurus/preset-classic": "2.4.1",
"@fortawesome/fontawesome-svg-core": "^1.2.36",
"@fortawesome/free-solid-svg-icons": "^5.15.4",
"@fortawesome/react-fontawesome": "^0.1.15",
"@mdx-js/react": "^1.6.21",
"autocomplete.js": "^0.38.0",
"clsx": "^1.1.1",
"docusaurus-lunr-search": "^2.1.14",
"lodash.debounce": "^4.0.8",
"moment": "^2.29.1",
"react": "^16.8.4",
"react-big-calendar": "^0.33.5",
"react-debounce-input": "^3.2.4",
"react-dom": "^16.8.4",
"react-router-dom": "^5.2.0",
"use-debounce": "^7.0.0"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
The bug is likely not in your docusaurus project, but in your hosting config. We can't help fixing it.
If you run docusaurus serve it should work fine.
|
2025-04-01T06:38:38.233052
| 2019-02-24T06:42:00
|
413788567
|
{
"authors": [
"BrodaNoel",
"CommerceOwl",
"MBach",
"svitekpavel"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5789",
"repo": "facebook/draft-js",
"url": "https://github.com/facebook/draft-js/issues/2013"
}
|
gharchive/issue
|
Using SSR with Next.js: TypeError: undefined is not an object (evaluating 'editorState.getBlockTree(anchorBlockKey).getIn')
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When using server side rendering, Rich Text example ( https://github.com/facebook/draft-js/tree/master/examples/draft-0-10-0/rich ) throws this error when pressing enter and at other times.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/stopachka/m6z0xn4r/.
Use Next.js to setup SSR.
Create a component called RichText from example here ( https://github.com/facebook/draft-js/tree/master/examples/draft-0-10-0/rich )
When page refreshes from server using next.js development server, start typing in the rich text editor and hit enter.
You'll see these errors appear multiple times.
What is the expected behavior?
Not to have errors in the browser console.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Draft.js version: 0.10.28
Browser: Chrome 71 & Safari 12.0.3
OS: Mac OS: 10.14.3
Not sure if this worked in previous version of Draft.js
This is a problem with server-side rendering. Not sure about the reason, but you can work around this by rendering the editor only on client side.
import dynamic from 'next/dynamic';
const NoSSREditor = dynamic(() => import('../components/Editor'), { ssr: false });
render() {
return <NoSSREditor .... />
}
Works for me.
Thanks @svitekpavel! Working for me as well.
Hi @svitekpavel
I've tried your solution but unfortunately, I have an infinite loop when I'm starting my server. My memory is getting consumed very fast, and I cannot render a single page, until the server crashes.
Windows 10 x64 - 16 GB of RAM
Node.JS 12.8.0
Next.JS 9.0.3
Draft 0.11.0
Hi @svitekpavel
I've tried your solution but unfortunately, I have an infinite loop when I'm starting my server. My memory is getting consumed very fast, and I cannot render a single page, until the server crashes.
The rendering should not be called on server, so my best guess is that something else is wrong. Try to revert changes and get the server running normally. Then again try to change it.
|
2025-04-01T06:38:38.244343
| 2019-01-31T20:07:27
|
405416703
|
{
"authors": [
"jimmydief",
"skeggse",
"vicapow"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5790",
"repo": "facebook/flow",
"url": "https://github.com/facebook/flow/issues/7422"
}
|
gharchive/issue
|
Support for arrays in disjoint unions refinements
Flow version: v0.91.0
Expected behavior
With the following code, I would expect flow to understand how control flow interacts with the union type, and refine the associated function type to be compatible with the function invocations. That is, I would expect this code to not error.
type Args =
[false, () => void] |
[true, (number) => number];
function applyTheThing(...args: Args): number | void {
const [acceptsMore, fn] = args;
if (acceptsMore) return fn(100);
fn();
}
Actual behavior
The above code snippet produces (see flow.org/try) the following error:
9: if (acceptsMore) return fn(100);
^ Cannot call `fn` because no arguments are expected by function type [1].
References:
4: [false, () => void] |
^ [1]
10: fn();
^ Cannot call `fn` because function [1] requires another argument.
References:
5: [true, (number) => number];
^ [1]
The same applies if the array entries are dereference directly instead of first re-bound to local bindings (see flow.org/try).
@skeggse Correct. It errors to show you that flow isn’t smart enough to know it shouldn’t error. I realize it may seem unusual for this behavior to be expected but Flow tends to error when it can’t be sure something is safe.
Yeah that makes perfect sense - I wasn't sure how that example was intended to differ from the example I gave, as it was producing the same error.
This is one of the more frustrating parts of Flow that I've encountered. I would personally expect Flow to be able to refine the type of this:
const x: Array<string> | Array<Array<string>> = ['a'];
Similarly, I can understand why Flow isn't able to refine x to a specific type in the following example, but it's unclear to me why an error would be surfaced prior to me trying to do something with x that isn't valid for all possible types in the union.
const x: Array<string> | Array<Array<string>> = [];
Try Flow
|
2025-04-01T06:38:38.413188
| 2017-05-03T20:45:49
|
226109448
|
{
"authors": [
"Billy-",
"Temirtator",
"abramz",
"abritinthebay",
"ahtashamabbasse",
"alex-dixon",
"amiteshore",
"balovbohdan",
"ecoker",
"franciscop",
"machineghost",
"nithrm",
"rickhanlonii",
"slavafomin",
"tfoxy",
"thymikee",
"vitaly-t"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5791",
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/issues/3457"
}
|
gharchive/issue
|
Test if object, array or string.
Is there a way to check if a component is an object, array or string? This would be similar to chai's 'should.be.a' Ex.: validationResult.SSN[0].should.be.a('string').
No, there isn't. You'll find the list of all available matchers here: https://facebook.github.io/jest/docs/en/expect.html
You can also use plain JavaScript or helper library like lodash for that:
test('name', () => {
// array
expect(Array.isArray(['value'])).toBe(true);
// string
expect(typeof 'value').toBe('string');
// object
expect({value: 'value'}).toBeTruthy();
expect(typeof {value: 'value'}).toBe('object');
})
Minor point - this doesn't help with promise results.
expect(somePromise).resolves.toBe(...) at this point there is no way to check type. I hoped expects.stringContaining("") to be a work around but that doesn't work either.
@abritinthebay I am in exact that situation and this is the first result in Google, maybe this should be reopened?
Certainly it should be thought about a bit more. My workaround was to add to the chain so that does the typeof part. eg:
expect(somePromise.then(data => typeof data)).resolves.toBe("object");
it works, but it's not exactly clean.
@thymikee Checking types of things is a common enough use case (universal) that there isn't really any excuse for a testing framework that lacks them. Your alternatives are unacceptable as we lose all context of what we are testing.
This expect(Array.isArray(['value'])).toBe(false); fails with
expect(received).toBe(expected)
Expected value to be (using ===):
false
Received:
true.
So we either get terrible assertion messages or we have to extend Jest to support these sorts of checks. Doesn't it make more sense for the maintainers of Jest to do this once as opposed to every person that uses requires these features implementing them on their own?
Create your own matchers with expect.extend then and publish as an npm module. If it gets popular, we may merge it to Jest core eventually ;)
A simple toBeType extension for those who want it
expect.extend({
toBeType(received, argument) {
const initialType = typeof received;
const type = initialType === "object" ? Array.isArray(received) ? "array" : initialType : initialType;
return type === argument ? {
message: () => `expected ${received} to be type ${argument}`,
pass: true
} : {
message: () => `expected ${received} to be type ${argument}`,
pass: false
};
}
});
describe("testing extended expect", () => {
it("tests normal types correctly", () => {
expect("").toBeType("string");
expect({}).toBeType("object");
expect(1).toBeType("number");
});
it("tests array types correctly", () => {
expect([]).toBeType("array");
});
it("works with promises", () => {
expect(Promise.resolve([])).resolves.toBeType("array");
});
});
Pretty simple to implement. Really should be in core tbh.
Thanks @abritinthebay
So I wrapped that up in an npm module if people want it:
https://www.npmjs.com/package/jest-tobetype
describe("assertion framework", ()=> {
it("should check primitive types", () => {
expect(expect.toBeA).toBeA("function")
})
})
Failed: expect(...).toBeA is not a function
TypeError: expect(...).toBeA is not a function
I've been using toBeInstanceOf in my tests:
expect($wrapper.vm.countries).toBeInstanceOf(Array);
Create your own matchers with expect.extend then and publish as an npm module. If it gets popular, we may merge it to Jest core eventually ;)
Yeah, and might write your own jest framework, while you're at it.
This one just might top the worst answers you can get on GitHub.
So @abritinthebay did exactly what was requested by @thymikee (which was far more than the standard pull request).
Now that that brave soul did all the work, when can the rest of us finally get this matcher (without having to install yet another library)? Are the maintainers still pushing the idea that this doesn't belong in Jest, or did this just fall off their radar?
We are pretty strict with what makes it into core and don't typically add sugar matchers. Jest core is a fairly large architecture and every matcher we add increases the maintenance cost
For sugar, we generally recommend https://github.com/jest-community/jest-extended
One man's sugar is another man's (or in this case, at least seven other people's) really useful and logical feature that belongs in the core library.
Obviously as a maintainer your vote trumps all of ours, and you have all sorts of concerns we don't so I fully respect that. But I'd simply ask that you look at why everyone here considers this feature to belong in the core library (so strongly that one person jumped through multiple hoops to write the code for you). There's a need here, and if you ignore it Jest core library users (and let's be honest, 90% of them will never even hear about jest-extended) will lose out.
As abritinthebay suggested, it's not really about sugar, it's about "necessary" and "unnecessary" (for the core library) sugar. You've got a bunch of people in this thread saying "hey, being able to check all types is something that should be in the core of a testing library".
Listen to us or don't, again as maintainer you have lots of other concerns. But I don't think the right response is to come say "your's is just inherently unnecessary sugar" when it's not inherent: it's 100% your call whether Jest can check all types or not.
I think this is the way to go :)
describe('type check', () => {
test('should be type string', () => {
expect(typeof '').toBe('string')
})
test('should be type number', () => {
expect(typeof 10).toBe('number')
})
test('should be type boolean', () => {
expect(typeof true).toBe('boolean')
})
test('should be type undefined', () => {
expect(typeof undefined).toBe('undefined')
})
test('should be type object', () => {
expect(typeof { foo: 'bar' }).toBe('object')
})
test('should be type function', () => {
expect(typeof function() {}).toBe('function')
})
test('should be type null', () => {
expect(typeof null).toBe('object')
})
})
I refactored the implementation provided by @abritinthebay. It seems for me a little bit comfortable to work with.
`expect.extend({
toBeType(received, arg) {
const initialType = typeof received;
const type = initialType === 'object'
? Array.isArray(received)
? 'array'
: initialType
: initialType;
return {
pass: type === arg,
message: () => `Expected '${received}' to be type '${arg}'`
};
}
});`
You should check out my module (linked above). It does a bit more than that. But if that works for you: use it!
I think this is the way to go :)
describe('type check', () => {
test('should be type string', () => {
expect(typeof '').toBe('string')
})
test('should be type number', () => {
expect(typeof 10).toBe('number')
})
test('should be type boolean', () => {
expect(typeof true).toBe('boolean')
})
test('should be type undefined', () => {
expect(typeof undefined).toBe('undefined')
})
test('should be type object', () => {
expect(typeof { foo: 'bar' }).toBe('object')
})
test('should be type function', () => {
expect(typeof function() {}).toBe('function')
})
test('should be type null', () => {
expect(typeof null).toBe('object')
})
})
It's works like a charm as well as more readable and maintainable for the future.
I think this is the way to go :)
describe('type check', () => {
test('should be type string', () => {
expect(typeof '').toBe('string')
})
test('should be type number', () => {
expect(typeof 10).toBe('number')
})
test('should be type boolean', () => {
expect(typeof true).toBe('boolean')
})
test('should be type undefined', () => {
expect(typeof undefined).toBe('undefined')
})
test('should be type object', () => {
expect(typeof { foo: 'bar' }).toBe('object')
})
test('should be type function', () => {
expect(typeof function() {}).toBe('function')
})
test('should be type null', () => {
expect(typeof null).toBe('object')
})
})
test('should be type object', () => {
expect(typeof { foo: 'bar' }).toBe('object')
// passes
expect(typeof ['foo', 'bar']).toBe('object')
// passes
expect(typeof null).toBe('object')
})
😞
This is why I suggest my addon above: takes care of this.
InstanceOf is slightly better but prone to similar issues.
thanks for solution @abritinthebay
Another solution:
expect('example').toEqual(expect.any(String));
expect(123).toEqual(expect.any(String));
The second one would fail with:
Expected: Any<String>
Received: 123
It's extremely weird that Jest doesn't provide so basic functionality out of the box. It's a nonsense that you need to install a third-party library just to check the type of a variable in a clear and semantic manner.
|
2025-04-01T06:38:38.415667
| 2018-01-15T14:15:07
|
288607879
|
{
"authors": [
"dlmr",
"manu-st"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5792",
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/pull/5316"
}
|
gharchive/pull-request
|
feat(jest-cli): return results object from jest.run
Summary
This makes it easier to run Jest directly, like when wrapping it in a custom script.
Test plan
Tests passes as before.
The major disadvantage is that runCLI does not process the command line arguments and the functions that do that are not exported. I'd like to use run but unfortunately there is no way to find out if it was successful or not, unless I missed something.
|
2025-04-01T06:38:38.423854
| 2018-12-25T05:50:48
|
393966665
|
{
"authors": [
"H1Gdev",
"codecov-io"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5793",
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/pull/7546"
}
|
gharchive/pull-request
|
Remove duplicate 'the'.
Summary
before:
the the
after:
the
Codecov Report
Merging #7546 into master will not change coverage.
The diff coverage is n/a.
@@ Coverage Diff @@
## master #7546 +/- ##
=======================================
Coverage 67.91% 67.91%
=======================================
Files 248 248
Lines 9507 9507
Branches 6 6
=======================================
Hits 6457 6457
Misses 3048 3048
Partials 2 2
Impacted Files
Coverage Δ
packages/expect/src/matchers.js
99.39% <ø> (ø)
:arrow_up:
packages/jest-snapshot/src/index.js
52.63% <ø> (ø)
:arrow_up:
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 bfdd4e1...0d92c27. Read the comment docs.
|
2025-04-01T06:38:38.427864
| 2024-12-09T16:02:20
|
2727550083
|
{
"authors": [
"Srishtihere",
"ritikaGupta4"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5794",
"repo": "facebook/lexical",
"url": "https://github.com/facebook/lexical/issues/6926"
}
|
gharchive/issue
|
Bug: RTE components when resizing or scroll doesn't seem to be contained or collapsed
RTE components when resizing or scroll doesn't seem to be contained or collapsed.
Lexical version: 0.18.0
Steps To Reproduce
Go to the lexical playground and add lengthy texts to make it scrollable and table
Click on table dropdown and scroll the editor.
Now you'll see that dropdown is not being contained and not getting attached with table dropdown.
https://github.com/user-attachments/assets/cd24854e-8966-4cde-bc9f-abe4a399309d
Link to code example: https://playground.lexical.dev/
The current behavior
Components are not getting contained.
The expected behavior
Make it contained.
Impact of fix
can I work on this issue ?
|
2025-04-01T06:38:38.430185
| 2023-10-05T15:53:07
|
1928606100
|
{
"authors": [
"Piliuta"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5795",
"repo": "facebook/lexical",
"url": "https://github.com/facebook/lexical/pull/5087"
}
|
gharchive/pull-request
|
Update anchor selection if split by patching style
Problem
Setting styles using $patchStyleText does not update the selection when the anchor node is split. This causes the selection to contain a node that is not part of the selection. As a result, the toolbar/$getSelectionStyleValueForProperty is not able to determine the correct selection style.
https://github.com/facebook/lexical/assets/1575198/e438e605-4d4d-4c78-9967-e3176ed531f8
Solution
Update the selection anchor with the new text node after splitting.
https://github.com/facebook/lexical/assets/1575198/22c177ae-fd17-4b30-bb68-2adab21a9b78
Failed tests seem spurious 😏
|
2025-04-01T06:38:38.432210
| 2013-07-22T08:24:50
|
17035427
|
{
"authors": [
"facebook-github-bot-1",
"wez"
],
"license": "apache-2.0",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5796",
"repo": "facebook/libphenom",
"url": "https://github.com/facebook/libphenom/issues/1"
}
|
gharchive/issue
|
Add BSER load/dump support for variants
BSER is a local-IPC only serialization format for dynamic data:
https://github.com/facebook/watchman/blob/master/BSER.markdown
Adding support for this to Phenom requires adding load/dump APIs similar to the JSON load/dump API.
It also means adding API support for "Array of Templated Objects". In Watchman, this is achieved simply by storing the template definition as a special property of the object type.
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.
|
2025-04-01T06:38:38.453797
| 2019-06-12T16:40:05
|
455316403
|
{
"authors": [
"OndraM",
"riotCode",
"temptationdrops"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5797",
"repo": "facebook/php-webdriver",
"url": "https://github.com/facebook/php-webdriver/issues/646"
}
|
gharchive/issue
|
Issue with hotfix for w3c chromeOptions
What are you trying to achieve? (Expected behavior)
Adapt acceptance testing with Codeception for ChromeDriver v75, using webdriver v1.7.0.
What do you get instead? (Actual behavior)
In the code of the hotfix for w3c I get an error toArray() called on Array for Facebook\WebDriver\Remote\RemoteWebDriver line 112.
if (!isset($chromeOptions->toArray()['w3c'])) {
How could the issue be reproduced? (Steps to reproduce)
Using Codeception pass capabilities to chromeOptions
modules:
enabled:
- WebDriver:
url: http://localhost:8000
browser: chrome
port: 9515
restart: true
capabilities:
chromeOptions:
args: ["--headless", "--disable-gpu", "--no-sandbox"]
Details
Php-webdriver version: 1.7.0
PHP version: 7.3
Operating system: Linux
Browser used + version: ChromeDriver v75
I believe the cause is that the hotfix assumes the class Facebook\WebDriver\Chrome\ChromeOptions is always used, but before the hotfix it allowed passing an array instead.
Ah, nevermind I see now it is fixed in main branch, just not released yet.
Yes, fixed in 1.7.1.
Ref. #642 .
Still no substance
|
2025-04-01T06:38:38.457665
| 2016-01-12T17:21:10
|
126228593
|
{
"authors": [
"cberner",
"dain"
],
"license": "apache-2.0",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5798",
"repo": "facebook/presto",
"url": "https://github.com/facebook/presto/pull/4319"
}
|
gharchive/pull-request
|
Fix theoretical memory tracking leak
DriverFactory is not guaranteed to be closed. It's only closed when all
splits have been received and drivers created for them. However,
several OperatorFactories rely on close() being called.
For example, LookupJoinOperatorFactory will "leak" memory in the memory
tracking system, if close() is not called.
looks good
|
2025-04-01T06:38:38.462980
| 2022-04-06T11:41:50
|
1194489457
|
{
"authors": [
"Simek",
"lunaleaps"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5799",
"repo": "facebook/react-native-website",
"url": "https://github.com/facebook/react-native-website/pull/3059"
}
|
gharchive/pull-request
|
update Docusaurus and other deps, fix broken styles
Why & how
Superseeds:
#3022
This PR updates Docusaurus to latest beta (beta.18) and most of the other dependencies.
Due to changes in Docusaurus code, I had to adjust the config and add a bunch of fixes to our custom styles, which become broken after the update. I also had to duplicate the GA move in the config, otherwise the website won't start.
Test plan
I have run the updated version of the website on localhost and I used the currently shipped website as a 1:1 comparison, so the style issues was easier to spot, however, there still might be small display problems which I was not able to catch. If you see any regression in preview deploy, please let me know!
I think this looks good! Are there particular places we should look for breakages? I guess, also should we confirm that GA tracking is working (tbh not sure how to do that)
Are there particular places we should look for breakages?
Generally every layout have at least one issue, sidebars too, only home page looks correct after upgrade, so it's hard to point on the specific thing. I usually test few pages, with focus on the origin diversity:
homage (custom JS)
versioned doc page (docs plugin)
blog post list and blog post (blog plugin)
community page (custom MD)
I guess, also should we confirm that GA tracking is working (tbh not sure how to do that)
The fix has been deployed yesterday in separate PR, so you probably should see a data spike on the GA dashboard now, if everything is working correctly.
Oh actually I do think I found an issue -- I thought it was a general issue but it's not reproing off prod: https://github.com/facebook/react-native-website/issues/3061
I have fixed the mobile menu hover issue and the deploy preview should be updated.
Please let me know, if now it looks fine for you.
|
2025-04-01T06:38:38.468794
| 2017-02-25T20:32:26
|
210259933
|
{
"authors": [
"ericvicenti",
"kirkstrobeck",
"rogerkerse"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5800",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/12582"
}
|
gharchive/issue
|
Jest coverage is throwing packager errors
Description
What I did
I added Jest to my project and started generating code coverage reports, which creates a folder named "coverage" at the project root.
What you expect to happen
I expected nothing to happen with the code.
What actually happens
Packager is looking at it for some reason, and it is causing an error.
TransformError /PATH/coverage/lcov-report/sort-arrow-sprite.png: Unexpected character '�' (1:0)
Reproduction
Having trouble reproducing.
Solution
The coverage folder should not be included in the packager logic or I should be able to ignore it. It’s unclear why it is looking in there as I have not linked to any files in the folder.
Additional Information
React Native version: 0.39.2
Platform: iOS
Operating System: OS X 10.12.3
cc @cpojer
I have since upgraded to 0.41.2 and am still experiencing the issue, so any additional notes may be applicable to only this newer version
Tried https://github.com/facebook/react-native/issues/7271#issuecomment-215375355 and it didn’t work
It throws the error when the coverage report is generated. If I hit reload, I can use my app just fine even though the offending .png is still present. It seems to be that the Packager file watcher is having/starting/causing the issue.
This worked for me http://stackoverflow.com/a/41963217/537998
This still feels like a bug to me, but I’ll close since the issue can be resolved.
this is more like a bug. Quite unintuitive to do this with every react native project
|
2025-04-01T06:38:38.470798
| 2017-03-16T17:23:36
|
214779457
|
{
"authors": [
"damathryx",
"hramos"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5801",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/12978"
}
|
gharchive/issue
|
Prevent system font from overriding app font
I need to force app font inside the app and not to be overridden by system font. Namely font size and fontFamily. I also added the font I am using in assets and resources for android and iOS respectively.
rn: 0.42
Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!
|
2025-04-01T06:38:38.479627
| 2019-01-29T09:51:23
|
404205560
|
{
"authors": [
"adititipnis",
"cinder92",
"eleallegue",
"luoyushouchai",
"saeedhassankhan"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5802",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/23200"
}
|
gharchive/issue
|
Error calling JSTimers.CallTimers
Environment
[skip envinfo]
Description
I am trying to run my app on Android (One plus 6t). This was working fine before making a call to firebase but as soon as I add the line onSend={Fire.shared.send} to Chat.js, the app crashes. The logs just show Uncaught Error: Error calling JSTimers.CallTimers. Haven't seen this error anywhere else. Does anyone know what's the issue?
Reproducible Demo
Here's the snack: https://snack.expo.io/@adititipnis/community
i have same issue as you, any help?
Does anyone know a solution to this issue?
React Native Version: 0.59.9;
Platform: Android
Reproduce step:
1、 start an animation in react native view!
Animated.timing(translateX, {
toValue: 10,
duration: 200,
easing: Easing.inOut // this config crash and throw Error calling JSTimers.callTimers
// easing: Easing.in //this config work well.
}
)
render() {
const { translateX } = this.state;
const marginRight = translateX.interpolate({
inputRange: [0,1],
outputRange: [-100, 0]
})
return <Animated.View style={{marginRight}}>...</Animated.View>
}
my same problem fixed by this way :
if (!isNaN(toValue)) {
//start animation
}
//full code may be help you
const { duration, marqueeDelay, loop, isInteraction, useNativeDriver, easing, children, scrollingSpeed } = this.props
this.setTimeout(() => {
if (!isNaN(this.distance)) {
Animated.sequence([
Animated.timing(this.animatedValue, {
toValue: this.distance,
duration: duration || (this.distance) * scrollingSpeed,
easing: easing,
isInteraction: isInteraction,
useNativeDriver: useNativeDriver
}),
Animated.timing(this.animatedValue, {
toValue: 0, //-this.distance ,
duration: duration || (this.distance) * scrollingSpeed,
easing: easing,
isInteraction: isInteraction,
useNativeDriver: useNativeDriver
})
]).start(({ finished }) => {
if (finished) {
this.hasFinishedFirstLoop = true
}
if (loop) {
this.animateBounce()
}
})
} else {
this.start()
}
}, this.hasFinishedFirstLoop ? 0 : marqueeDelay)
|
2025-04-01T06:38:38.488294
| 2023-05-30T19:43:15
|
1732887513
|
{
"authors": [
"rvasseur31",
"solveit-andrey-savich"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5803",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/37627"
}
|
gharchive/issue
|
Could not find module ... for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator,
Description
Hello.
Context
We have RN iOS project with CocoaPods dependecies, but we want to add some dependencies via SPM.
In our Podfile, we have following lines:
installer.pods_project.build_configurations.each do |config|
config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end
Without this lines — build fails by different errors from Pods
Right now if we will try to add SPM package to project, we have two scenarios:
Option 1 : Rosetta — turn on, project with connected SPM + Pods builds correctly. We don't want to use Rosetta at all
Option 2 : Rosetta — turn off, project build with connected SPM + Pods fails with an error Could not find module PACKAGE NAME for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator
What we want to achive
We want to be able to add SPM packages to Xcode project, continue to use Pods and don't use Rosetta . Does any one faced with this problem or has some solutions?
React Native Version
0.7
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 13.1
CPU: (10) x64 Apple M1 Pro
Memory: 227.15 MB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.20.0 - /usr/local/opt/node@16/bin/node
Yarn: 1.22.11 - ~/Documents/WORK/Breadfast/ReactNative-customer-app/node_modules/.bin/yarn
npm: 6.14.13 - ~/Documents/WORK/Breadfast/ReactNative-customer-app/node_modules/.bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: Not Found
Python: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Xcode project generated by RN tools
Any SPM package
Turn off Rosetta on Mac
Snack, code example, screenshot, or link to a repository
Hi, you can use this in your podfile :
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"
end
end
end
|
2025-04-01T06:38:38.491810
| 2017-09-18T05:43:06
|
258374796
|
{
"authors": [
"Kureev",
"deecewan"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5804",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/15979"
}
|
gharchive/pull-request
|
uniq with an iteratee is uniqBy
The wrong version of the function was being used which was resulting in flow errors.
See https://lodash.com/docs/4.17.4#uniqBy for reference.
Test Plan
There should probably be a test for this. According to the lodash source, calling uniq with a second argument is not supported.
Flow correctly picks up on this, and is causing errors in my project.
I believe we merged similar PR a couple of weeks ago 🤔
Just found it. Seems we already have a PR that has been opened for a while (26 days). I don't want to discourage you, but I would prefer merging it that PR as far as it was the first one and we already reviewed it. Thanks for pointing out that we didn't merge it yet (in my mind we did haha)!
Hope to see more contributions from you in the future!
That's all good, just want to get it merged :)
|
2025-04-01T06:38:38.542195
| 2015-09-14T11:36:53
|
106323494
|
{
"authors": [
"Noitidart",
"brentvatne",
"cgilboy",
"ehd",
"ekryski",
"esauter5",
"facebook-github-bot-7",
"ide",
"janmonschke",
"javache",
"joel100",
"mkonicek",
"nicklockwood",
"sahrens",
"satya164",
"webgoudarzi",
"yelled3"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5805",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/2668"
}
|
gharchive/pull-request
|
[TextInput] Add controlled selection prop
For prior discussion with @brentvatne @sahrens @yelled3 see #2478
Again, some notes and points for discussion:
I think using a NSDictionary is fine for the native prop type.
Should RCTTextView and RCTTextField share the implementation of setSelectionRange, or would that not be worth the effort? There's a little bit of duplication there.
In iOS you can set selectedTextRange to nil. It removes the cursor but keeps the input focused and available for inputs from the keyboard. I decided not to support it in this PR.
I'd love to follow this up with a PR for selection change events :smile:
Looks like some flow version change makes the e2e build fail: https://travis-ci.org/facebook/react-native/jobs/80185569#L929
I guess I'll just wait until that's resolved in master and re-run the build or rebase the PR?
LGTM @ehd
By the way, if there's any feasible way to offer the same functionality via an external npm package I'd also love to do that. I'm not sure whether it's possible to tie into native internals (I doubt it). I know that the maintainers are super busy right now and I'd like to test the API for a bit, let people try this out and maybe have someone contribute android parity.
Was curious about the status on this. Really excited about this feature! Hope to see it soon.
I'm going to rebase these changes on top of the current master soon.
@sahrens Since we talked in #2478, anything you want me to do to get this to review?
I merged these changes into my own branch and it worked great. The example in UIExplorer was helpful. The only gotcha for me was that at first I was trying to call setSelectionRange immediately after calling setState (in order to auto-insert a forward slash for a date). This did move the cursor properly which I'm guessing is due to the asynchronous nature of setState. This was solved by calling setSelectionRange either in componentDidUpdate or the setState callback.
This will be super helpful to start building some higher order text inputs with auto-insert and auto-complete. Nice job @ehd.
@brentvatne you think this could this be included in v0.14.0?
One question I have is whether the selection range should be a controlled prop. I bet there are some lessons learned from <Input> elements in the browser and whether a prop or an imperative method is preferable. Someone from FB UIE should take a look.
Otherwise this feature looks good... cc @sahrens
@ide I updated the PR to resolve the merge conflicts and update the warning log message text. Would be great to get some feedback regarding controlled prop vs. imperative method!
Have you looked into how this is going to work on Android? Ideally it should have the same API on both.
Have you looked into how this is going to work on Android? Ideally it should have the same API on both.
@mkonicek I haven't yet. I was thinking it would be great if someone familiar with Android development could look into this. Also, if they could comment on the user-facing API that would already help a lot, I think.
I'm really excited about the new rich text in TextInput support on iOS! Going to rebase this code on top of v0.15.0-rc and master tonight.
The implementation looks good to me as far as it goes. But I'm curious how this is used though without having an equivalent "onSelectionChange" event. It seems like you'd have no way of knowing what selection the user currently has, so you'd be overriding blindly, without being able to extend or restore the original values.
@ide's idea of making it a controlled property is also interesting - that would certainly make sense given how setting the text value works currently, as you'd probably want to implement text and selection updates in lock-step if you were doing something like real-time text replacement.
The implementation looks good to me as far as it goes. But I'm curious how this is used though without having an equivalent "onSelectionChange" event. It seems like you'd have no way of knowing what selection the user currently has, so you'd be overriding blindly, without being able to extend or restore the original values.
That is correct. This would make a lot more sense with the selection change event working. Can I ask: Is there any internal version on this? I've seen references to DocumentSelectionState. I'm happy to implement that event in this PR.
@ide's idea of making it a controlled property is also interesting - that would certainly make sense given how setting the text value works currently, as you'd probably want to implement text and selection updates in lock-step if you were doing something like real-time text replacement.
Like this, for example?
<TextInput
selectionRange={[0, 3]} // Array variant
selectionRange={{start: 0, end: 3}} // Object variant
value='Foobar'
/>
Yeah, we do have a selectionChanged event internally. I'll add that to the open source version so we're consistent
Yeah, we do have a selectionChanged event internally. I'll add that to the open source version so we're consistent
That sounds great. So how about this:
onSelectionChange event and prop are added to the open source version
I make a controlled-prop version of selectionRange as @ide suggested, which is feasible with the event. I think I prefer that as an API.
Thats sounds good to me. @sahrens ?
I've landed the onSelectionChange event: https://github.com/facebook/react-native/commit/5a34a097f2d2324e5515e876a20fd5b7a376aa3e
@nicklockwood Thank you! I'll see to the controlled-prop API for selectionRange.
Apologies for the delay, I'm finally getting to this. Let me know if someone's got a better idea or a hot commit sitting somewhere. Otherwise I'll update the branch head to a new commit on top of the current master with this API:
class ControlledSelectionRange extends React.Component {
state = {
selectionRange: {start: 0, end: 0}
}
render() {
return (
<TextInput
selectionRange={this.state.selectionRange}
onSelectionChange={selectionRange => this.setState({selectionRange})}
/>
)
}
}
cc @nicklockwood @sahrens
Just resolved some merge conflicts with master. Now working on the API changes.
Since we're not going with the DOM API inspired naming anymore I'm changing the prop's name to just selection.
This turns out to be more difficult than I thought. I can't find a way to set selections programatically that won't also trigger the onSelectionChange event handler and thus cause a loop.
Similar to setText I'm comparing the input's current selectedTextRange, but this can't solve the problem of different selection change events causing overlaps and an change event -> set state -> change event -> set state loops.
Any ideas? I also commented here: https://github.com/facebook/react-native/commit/5a34a097f2d2324e5515e876a20fd5b7a376aa3e
Can't you filter out events that don't actually change anything? That
should be able to break any loops.
In general this seems like the right approach.
On Thursday, December 3, 2015, Stephan Seidt<EMAIL_ADDRESS>wrote:
This turns out to be more difficult than I thought. I can't find a way to
set selections programatically that won't also trigger the
onSelectionChange event handler and thus cause a loop.
Similar to setText I'm comparing the input's current selectedTextRange,
but this can't solve the problem of different selection change events
causing overlaps and an change event -> set state -> change event -> set
state loops.
Any ideas? I also commented here: 5a34a09
https://github.com/facebook/react-native/commit/5a34a097f2d2324e5515e876a20fd5b7a376aa3e
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/pull/2668#issuecomment-161814405
.
@sahrens I tried doing that by comparing the requested selection range's start and end offsets with the textField or textView's current selectedTextRange start and end offset, but under certain circumstances they always perfectly did not match up properly. I also tried comparing with _previousSelectedRange but that didn't work either. I'll push what I tried in a bit.
:+1:
@ehd Any updates on this?
@satya164 I would get back to this next week, in vacation mode right now.
@ehd Awesome. looking forward to it.
Happy new year :wink: I'm on this again, @janmonschke is in, too! :smile:
Ouch, I think I got it... It works quite nicely, without a loop now. Here's what I did wrong in my setSelection method:
BAD:
_textView.selectedTextRange = selectedTextRange;
_previousSelectionRange = selectedTextRange;
GOOD (set the previous value first so the event handler won't trigger):
_previousSelectionRange = selectedTextRange;
_textView.selectedTextRange = selectedTextRange;
I didn't anticipate that the event handler would be called in the former case.
Polishing this now, then pushing to my branch and we can bikeshed on the API. Yay :fireworks:
This is the API:
<TextInput
selection={{start: 0, end: 5}}
value="Hello, World"
/>
There's an extensive demo in UIExplorer -> .
@satya164: This is working now!
@sahrens: Thanks for the hint again.
@nicklockwood: What do you think?
Hmm. How to handle changing the selection and value props at the same time, actually?
@ehd the selection should presumably always be applied after the value? It might make sense to use the didUpdateProps method instead of overriding the setText and setSelection setters, then you can ensure they are applied in the correct order.
Yeah, what @nicklockwood says. :+1:
the selection should presumably always be applied after the value?
Yep, that was my intuition. I think this would be the least surprising behaviour:
Set text only: Keep sensible selection (current behaviour from #4716)
Set selection only: Change selection
Set text and selection: Change text and selection
It might make sense to use the didUpdateProps method instead of overriding the setText and setSelection setters, then you can ensure they are applied in the correct order.
Oh yeah, that sounds interesting! This is what I understand the text setter is doing right now:
Ignore text update if there's event lag
Ignore text update if native text is the same value
Manage cursor and selection, changed recently in #4716 to "keep the distance of the cursor from the end of the text constant"
@nicklockwood I was trying to come up with a plan, but I'd like to clarify a few things first:
If we don't override the setters, where are we going to coordinate text and selection management in the native component? Where to compensate for lag and same-value updates?
Should there be a single native setter for changing both text and selection?
If possible I would also like to do something about the almost duplicate setText code in UITextField.m and UITextView.m.
@ehd you may still want to override one or both of the setters, but just do some extra logic in didUpdateProps (like actually applying the selection to the view).
Regarding duplicate logic - I suggest creating an RCTTextUtils file and moving any common logic into there as static C functions (much as we've done with RCTImageUtils).
Eventually, I'd like to combine RCTTextField and RCTTextView into a single class, but that's a big job that I don't think we're ready to do just yet.
@ehd you may still want to override one or both of the setters, but just do some extra logic in didUpdateProps (like actually applying the selection to the view).
@nicklockwood Could you give me an example of how to do that? For example, if I overwrote both setters I wouldn't know how to use them properly in didUpdateProps. Maybe didUpdateProps is something other than componentDidUpdate?
@ehd didUpdateProps: is a native method that you can define on RCTTextView. It will be called after the native prop setters have been called, and its parameter contains an array of all props that were updated.
@ehd Ah, sorry, it's called didSetProps:, not didUpdateProps:. My bad 😬
Example:
(void)didUpdateProps:(NSArray<NSString *> *)changedProps
{
if ([changedProps containsObject:@"selection"]) {
//set the selection
}
}
@nicklockwood Holy cow, exactly what we need, thanks!
@nicklockwood Do we need to implement both setters in any case, just so we can intercept the prop value and store it in an instance variable? Or is there another way to access the props (since changedProps just contains key names)?
@ehd Declaring NSDictionary *_selection; along with the other ivars in RCTTextView.m (line 64) should be sufficient. If the ivar exists, it will be set automatically by the view manager.
@nicklockwood Yup, that works nicely for storing the prop values!
So now most of setText is in didSetProps (event lag guard, set text, maintain selection). I'm adjusting it so it works for setting just text, just selection or both text and selection. I think that is the only way, because if text or selection are changed before didSetProps it's a mess to save intermediate values for those in more ivars (old selection, old length).
When that code works it'll move into a helper that's used from both TextView and TextField, probably also the rich text input handling in TextView.
One thing I haven't fully understood yet is _previousSelectedRange. Is it to prevent selection change loops?
@ehd it's just because textViewDidChangeSelection: sometimes fires in situations where the range hasn't actually changed, so I use that to verify that the new range is different before sending the event.
@nicklockwood I see, good to know! While working on this I've also observed selection changing to place the cursor at the end of the text when setting the selection prop, not sure yet why.
I did some research on the current onSelectionChange event behaviour comparing UITextField and UITextView. It seems to be inconsistent :cry:
How to reproduce:
Create a <TextInput>
Set value to "Hello World"
Focus by tapping on area right of text
Place cursor at "Hello| World" by hand
Set value to "Well, Hello World"
Results in cursor at "Well, Hello| World" (as per #4716)
The onSelectionChange events of a single line TextInput (UITextField):
{start: 5, end: 5} (from step 4)
{start: 11, end: 11} (from step 5)
Note that there is no selection change event caused by step 3 which is not what I expected. Imagine a Twitter-like completion UI where the value is "Hi @" with the cursor at "Hi @|", the completion would not know about the cursor position on focus and not provide a completion. A solution could be having to set a controlled selection prop to {start: value.length, end: value.length} in JS when needed.
The onSelectionChange events of a multiline TextInput (UITextView):
{start: 11, end: 11} (from step 2, not caused by step 3!)
{start: 5, end: 5} (from step 4)
{start: 17, end: 17} (from step 5)
{start: 11, end: 11} (also from step 5)
I did not expect the 17,17 event to appear, and it causes flickering & other problems when selection is a controlled prop. I haven't yet found out whether that behaviour is exhibited by UITextView itself or RCTTextView. The 11,11 event is originating from RCTTextView's cursor placement. The multiline TextInput emits selection events even if the field isn't focused, the single line TextInput doesn't. I suggest we consolidate these behaviours:
First: Can an unfocused field have a selection at all?
TextInput should emit an initial event when it's focused
TextInput shouldn't emit selection change events if field isn't focused
TextInput shouldn't emit multiple events on cursor correction
@nicklockwood Should single line and multiline emit the same events and behave the same way?
Any opinions on this?
@ehd, sorry I thought I'd replied :-/
Thanks for doing that research, and yes, ideally we'd want single line and multiline events to behave the same, and I agree with your suggestions for what the expected behavior should be.
@nicklockwood No worries, I really appreciate all your help and input! I'm going to look into normalizing the events :smile:
Thanks for working on this feature! I've been looking into what is needed for Android parity, has anyone taken a stab at it yet?
@ehd Since no one has chimed in, I've pushed a branch to do the most basic setting of text selection on Android. It currently sets the text selection directly in the property setter, as opposed to doing the event normalization described above:
https://github.com/Ginger-Labs/react-native/tree/text-input-set-selection-android
Let me know if this is useful. It does contain a bug that keeps the selection from sticking when the selection change immediately follows a user tapping to place the cursor. I found a suboptimal workaround for this (https://github.com/Ginger-Labs/react-native/tree/hack-to-fix-android-text-input-selection), but it is not the proper way to address the issue, which appears to come from somewhere deep in the redraw/input lifecycle.
Any update on whether / when this might get merged? This would be very helpful.
@cgilboy Thanks for doing the Android work :)
@joel100 Currently I got stuck before normalizing the selection change events. The selection prop won't work properly unless the events are emitted in a sound way, regardless of whether it's a single line or a multiline input.
@sahrens would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.
I'll try assigning this to @sahrens as Nick has too many PRs to review. Do we want to proceed with this?
I did a really quick implementation for setting the selection on Android in https://github.com/exponentjs/react-native/commit/7a59fba694ee0bdeaa9f63e97033abdb2ea7c807 -- I'm happy to flesh it out to work the same as this one once this PR lands.
@brentvatne Do you know if this PR needs changes? Spencer commented 15 days ago and I added the Needs revision label based on his comment.
I'm actually not sure @mkonicek -- @sahrens @ehd - what's the status here?
FWIW this looks good to me. Nice work @ehd! @mkonicek The only change requested that is left was to switch to dot notation.
@brentvatne do you have a PR in for the Android side? 😁
Would love to see this land. Can't really do any input masking without this feature.
@ekryski - no PR for this yet but I'm going to have some cycles soon to clean up some of the stuff we've done on our internal fork so I made a note to come back to this one
Closing in favour of @janicduplessis PR's.
I can't figure out how to programatically call setSelection. It's not on the ref like .focus and .blur, would I have to use setNativeProps? Or is using the selection property the only way? I just needed a one time thing so I was trying the method call way.
Oh figured it out. Yep setNativeProps does the trick. Super cool thanks guys!
this.input.setNativeProps({ selection:{ start:1, end:1 } })
|
2025-04-01T06:38:38.546424
| 2022-05-20T12:57:44
|
1243115202
|
{
"authors": [
"fortmarek",
"hramos"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5806",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/33881"
}
|
gharchive/pull-request
|
Fix hermes compilation in the react-native package
Summary
When releasing the latest RC, we have noticed pod install is broken since the downloaded react-native package is missing hermes scripts and shelljs dependency (needed by hermes-utils.js).
Changelog
[Internal] - Fix compiling hermes in the release version.
Test Plan
Run test-manual-e2e.sh with template and Hermes on iOS
Ooof, thank you for fixing this!
|
2025-04-01T06:38:38.550433
| 2016-04-23T10:07:12
|
150538869
|
{
"authors": [
"bestander",
"ide"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5807",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/7172"
}
|
gharchive/pull-request
|
[CI] Exit with the error status code from xcodebuild
See https://github.com/supermarin/xcpretty#usage -- xcpretty will suppress xcodebuild's status code so we need to add && exit ${PIPESTATUS[0]}.
Test Plan: Look at Travis CI results and see that an error with the Obj-C tests is properly reported as a CI error.
Let's see the CI results
Travis tests are green because the 2nd retry of the Obj-C tests actually succeeded. Not sure if this diff truly fixes the status code, but it can't make things worse.
Shipit :)
We will monitor stability over time
On Saturday, 23 April 2016, James Ide<EMAIL_ADDRESS>wrote:
Travis tests are green because the 2nd retry of the Obj-C tests actually
succeeded. Not sure if this diff truly fixes the status code, but it can't
make things worse.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/pull/7172#issuecomment-213714716
@facebook-github-bot shipit
|
2025-04-01T06:38:38.556200
| 2016-06-10T13:08:16
|
159631386
|
{
"authors": [
"facebook-github-bot-7",
"javache",
"p16"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5808",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/8045"
}
|
gharchive/pull-request
|
Update docs for textDecorationStyle
This PR fixes the documentation for the textDecorationStyle prop in the Text component documentation.
textDecorationLine and textDecorationStyle were added for Android in https://github.com/facebook/react-native/releases/tag/v0.25.1
Only textDecorationLine was updated at the time https://github.com/facebook/react-native/commit/2039be9d32a52552db02239040bd8e7257bb80f0#diff-8d238dc2c74635b2aaca431551873addL55
By analyzing the blame information on this pull request, we identified @trave7er and @Kudo to be potential reviewers.
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!
As far as I can see, textDecorationStyle is still not available on Android. The release notes also no longer mention this.
Hi @javache,
maybe I did not link it but in the 0.27 release it's already in the android examples and in my project using 0.26 it's working :)
Could you link to the native code that implements this?
@javache you are right, I cannot find anything for textDecorationStyle that is like like the implementation for setTextDecorationLine . And, at the moment, it's working only the solid value for textDecorationStyle. Sorry about that.
|
2025-04-01T06:38:38.560751
| 2016-07-01T21:53:26
|
163480285
|
{
"authors": [
"JoelMarcey",
"facebook-github-bot-2",
"facebook-github-bot-5",
"facebook-github-bot-8",
"hramos"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5809",
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/8530"
}
|
gharchive/pull-request
|
Add post documentation lockdown survey link
We did a survey prior to the doc lockdown to get an idea of what we should focus on. Now we have a yes/no style survey to ensure that we met the user needs when it came to our start of improving the docs.
This diff adds the survey link to the bottom of each page. And we will cherry-pick it into 0.29 as well, which will be the first official release with the new doc content
NOTE: The content via the links in this survey will not be valid until 0.29 is actually released. So I have not enabled the questions for the survey until then.
Test Plan:
http://localhost:8079/react-native/docs/getting-started.html
By analyzing the blame information on this pull request, we identified @Andreyco and @caabernathy to be potential reviewers.
LGTM. Minor nit regarding the use of lockdown but I don't feel too strongly about it.
@hramos Ah - good point. Fixed.
@facebook-github-bot shipit
Something went wrong when importing this pull request. Please cc someone from the team at fb to help with importing this.
@facebook-github-bot shipit
Thanks for importing. If you are an FB employee go to Phabricator to review.
|
2025-04-01T06:38:38.583131
| 2018-03-05T06:30:00
|
302185857
|
{
"authors": [
"bsansouci",
"chenglou",
"mrkaspa",
"ubsan"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5810",
"repo": "facebook/reason",
"url": "https://github.com/facebook/reason/issues/1845"
}
|
gharchive/issue
|
Better syntax error for return foo
Something like "return doesn't exist in Reason; blabla"
What if someone names a function return, as with monads (although that's a terrible name, it's still used)
We could make it a hint, like we’ve done in the past. The hints are 100% accurate but they help give some idea of what caused the problem. Like “did you miss a semicolon” etc
return foo is invalid syntax, not a function
Reason does not need something like this :/
Folks, please read the title. It's to provide better syntax error message when people attempt to do return foo, which is invalid in reason. Right now the error message is <UNKNOWN SYNTAX ERROR>
|
2025-04-01T06:38:38.586342
| 2016-05-18T07:11:44
|
155431257
|
{
"authors": [
"SanderSpies",
"chenglou",
"yunxing"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5811",
"repo": "facebook/reason",
"url": "https://github.com/facebook/reason/pull/476"
}
|
gharchive/pull-request
|
Add eval opam config env
I followed the installation instructions, but the rebuild command didn't work - but after running eval opam config env everything worked.
Good catch. One does need to eval opam config env to make new opam configs take effects in the current shell. We should definitely put this instruction in the doc.
The instruction to add opam config env is a few line above (in case you didn't see it)
(Hey again!)
@chenglou I think we need to be explicit that people have to type it in the current shell.
@SanderSpies Could you move the line right below opam switch 4.02.3 ? If someone was using another switch before he switched to 4.02.3, the package pinned below will be pinned to the original switch instead of 4.02.3 unless he types eval opam config env.
@yunxing Will do.
@chenglou (Hey!) Right, my mistake indeed.
|
2025-04-01T06:38:38.603591
| 2015-04-03T23:02:21
|
66243487
|
{
"authors": [
"jasta",
"rickbrew"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5812",
"repo": "facebook/stetho",
"url": "https://github.com/facebook/stetho/pull/137"
}
|
gharchive/pull-request
|
Upgrade gh-pages to reflect v1.1.0
This adds an elements screenshot and bumps the version numbers.
looks good (y)
|
2025-04-01T06:38:38.639214
| 2017-09-07T19:19:47
|
256042615
|
{
"authors": [
"Timer",
"gaearon",
"radhey113"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5813",
"repo": "facebookincubator/create-react-app",
"url": "https://github.com/facebookincubator/create-react-app/issues/3093"
}
|
gharchive/issue
|
From React
I am getting this issue:->
ERROR in ./client/index.js
Module build failed: SyntaxError: 'import' and 'export' may only appear at the top level (6:1)
4 | render components from here
5 | */
6 | import react from 'react';
| ^
7 | import reactDom from 'react-dom';
8 | import APP from './components/App.js';
9 | reactDom.render(, document.getElementById('app'));
@ multi main
Please provide the complete code.
I'll close this as it's been a day and it's likely you resolved it.
Effectively, you are not allowed to run any code before an import. They must be first.
Please move any code that is not an import below the imports.
|
2025-04-01T06:38:38.668459
| 2017-04-28T08:46:52
|
225017163
|
{
"authors": [
"TheTFo",
"Timer",
"bgard6977",
"caiobalthazar",
"cdaringe",
"dchambers",
"gaearon",
"jgoz",
"lifeiscontent",
"valorize"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5814",
"repo": "facebookincubator/create-react-app",
"url": "https://github.com/facebookincubator/create-react-app/pull/2041"
}
|
gharchive/pull-request
|
:art: add first class debugging support
continuation of #1360. re-implemented per code review remarks, and conflicts resolved. needs 👀 re-review :).
problem statement
react-scripts does not offer ready-to-roll jest debugging.
solution
add it!
closes #594
test
checkout this feature branch
/path/to/this/branch/create-react-app/bin/create-react-app dummy-app
cd dummy-app
modify npm test to add a debug flag ^^
tell your editor to honor source maps
npm test
connect the remote debugger
go.
back at cha
good news! debugging is working reliably! good enough where i think we should ship, after any polish requested is applied.
bad news, --inspect* is no bueno. essentially facebook/jest#1652 prevents us from using JSDom in jest & the inspector protocol simultaneously. i'm not enough of a jest+JSDOM wizard to figure that out.
the code has been annotated, and --debug-brk still works great :), even in watch mode!
note, jest in watch mode in master is really, painfully slow on OSX for whatever reason. unrelated to this PR, but woof!
i'm not sure when react-scripts is targeting another release, but i would really like to be able to bump my projects and start debugging asap! go team ⚽️
When can we expect a release including this issue?
BTW, I think the build needs to be kicked started again. I don't think my pathes are the source of failure. An extra set of :eyes: would be appreciated
@cdaringe I don't want to leave this hanging, but I don't know if we're going to ship this until https://github.com/facebook/jest/issues/1652 is resolved.
I feel very uncomfortable relying on a flag that's already deprecated 😞; are there workarounds we can implement to get inspect working?
I’m going to push this back to 0.11 so we can have the time to figure this out.
@Timer @gaearon,
why is node's flag deprecation a threat? i don't see any risk here. we only add value/capability in this PR. there's zero loss to stakeholders. we can rev react-scripts later when the jest team gets this sorted out.
i do not think there's a jest hack to make --inspect work in the interim
i'm not sure what more we need to figure out. there's a known open issue against our dependency stack, but there is a reliable, non-hacky workaround--just limit usage to the older, but well tested & supported protocol.
debug capability, IMHO, is super important, & this is the 2nd time I've implemented it. i'm not upset, but i do not want to have to do it a 3rd time. can you speak more to why you feel we shouldn't get this in sooner?
I strongly agree with @cdaringe, this is very important for productivity and one of the worst parts of CRA testing.
I agree, with @cdaringe also. My team needs this capability as soon as
possible.
On Mon, May 8, 2017, 6:35 PM Caio Balthazar<EMAIL_ADDRESS>wrote:
I strongly agree with @cdaringe https://github.com/cdaringe, this is
very important for productivity and one of the worst parts of CRA testing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/pull/2041#issuecomment-300010026,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgWoPOhKMtJexaWThVfx5D9uuBG-fvlks5r35iUgaJpZM4NLNqS
.
https://github.com/facebook/jest/issues/1652 has been closed with no action taken.
There is nothing Jest can do to fix it. Please express your support for https://github.com/nodejs/node/issues/7593.
At this point we just need somebody to help push this through.
https://github.com/nodejs/node/pull/9272#issuecomment-304365983
Any volunteers?
@cdaringe sorry I didn't respond earlier
why is node's flag deprecation a threat? i don't see any risk here. we only add value/capability in this PR. there's zero loss to stakeholders. we can rev react-scripts later when the jest team gets this sorted out.
It's not so much that it's a threat, but if it becomes something we support, it's turns into our job to maintain that feature going forward.
When Node 8 is released, it is highly likely that --debug will not exist anymore and the only option will be --inspect.
Jest doesn't work with --inspect, so we'd have to tell users to not upgrade their Node versions if they'd like to debug.
This puts us in a bad position because people will expect test debugging to work across all LTS versions of Node (as they should).
IMO, this is plunging us back into the era of JavaScript F***gue where environment matters and tools don't work reliably.
Secondly, Create React App is a toolchain focused at beginners first, but we still consider advanced users and try to accommodate their needs.
Teaching beginners how to debug using a deprecated method and then telling them they have to switch to --inspect (external of our control [based on their environment]) would be painful and cause a potentially poor/confusing experience.
debug capability, IMHO, is super important, & this is the 2nd time I've implemented it. i'm not upset, but i do not want to have to do it a 3rd time.
I'm really sorry that you feel your development efforts are being wasted.
We try really hard to incorporate as many changes as we can and try to ensure developers feel valued. (and we do value your contributions very much, really.)
We will use your work (and not waste it 😄) as a foundation for building out this feature in the future if you are unable to allocate time, but I hope you can understand our position.
I would feel comfortable adding support for --debug if we had a solid timeline and plan for Jest supporting --inspect (which is blocked by Node currently).
I think any effort here should be directed towards unblocking Node. Let's just fix it there.
Just dropping this here, speculation was correct and --debug is dead:
Joes-MacBook-Pro:16s-website joe$ node --debug
(node:70606) [DEP0062] DeprecationWarning: `node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead.
Really looking forward to https://github.com/nodejs/node/issues/7593 and https://github.com/nodejs/node/pull/9272#issuecomment-304365983 progressing.
Doesn’t seem like anybody wants to take ownership 😞 .
My support hath been cast!
This and various related issues have been open since fall 2016. It seems like debugging is a second class citizen in the react/jest/CRA community? I know some folks think if tests are so complicated you need to debug them, then you are doing it wrong, but I personally think a debugger (with good tests) is one of the most productivity enhancing tools of all times. It would give me great confidence in the react community if debugging was a first-class concern.
We'd really like to implement this feature but Node does not support it. See https://github.com/nodejs/node/issues/7593 and https://github.com/nodejs/node/pull/9272#issuecomment-304365983.
If you can help implement the feature in Node, that'd be great!
@timer can we move forward on this yet now that inspector has been merged in node?
FYI, debugging Jest tests with inspector is now possible as of Node 8.4.0 (https://github.com/nodejs/node/pull/14465).
@jgoz Thank you for mentioning that here! I'll upgrade and try it again. I'm very happy to see this fixed!
This and various related issues have been open since fall 2016. It seems like debugging is a second class citizen in the react/jest/CRA community?
No. We were just as frustrated about this. Unfortunately we lacked the necessary knowledge (knowing C, understanding of how contexts work in Node and V8) to fix this. We are also glad the fix has landed! Sometimes a hard fix is just a hard fix, and not some intentional choice. :-)
I don't understand what you mean about profiles.
Can any provide guidance as to how to debug Jest tests using Node.js 8.4.0? I've so far tried:
npm test -- --inspect-brk
and:
node --inspect-brk node_modules/jest/bin/jest.js -i
with no joy.
Can any provide guidance as to how to debug Jest tests using Node.js 8.4.0? I've so far tried:
npm test -- --inspect-brk
and:
node --inspect-brk node_modules/jest/bin/jest.js -i
with no joy.
@dchambers, see https://github.com/facebookincubator/create-react-app/issues/594#issuecomment-322842515. make sure you're using version 1.0.11+
Thanks @cdaringe, upgrading 'react-scripts' to 1.0.11 then running ./node_modules/.bin/react-scripts --inspect --inspect-brk test --env=jsdom --runInBand did it for me 🎉
Closing this as support has been added in 1.0.11, thanks for all of your hard work!
Hey all,
I think this is broken. I'm having issues with debugging my thinks.
Here's repro branch
https://github.com/TheTFo/cria/tree/jest-debug?files=1
Attempt to debug tests from vscode launcher, placing a break point on the line indicated in comment in this file:
https://github.com/TheTFo/cria/blob/jest-debug/src/actions/todoActions.js
Breakpoints don't appear to hit the appropriate lines. Not sure what's causing it. I don't see transpiled code, just wierd breakpoints hits.
@TheTFo had the same problem. Comment https://github.com/facebookincubator/create-react-app/issues/594#issuecomment-245426594 fixed it for me
|
2025-04-01T06:38:38.719278
| 2019-05-14T00:50:47
|
443661774
|
{
"authors": [
"DavidWangW",
"agnosticdev",
"lnicco",
"siyengar",
"udippant"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5815",
"repo": "facebookincubator/mvfst",
"url": "https://github.com/facebookincubator/mvfst/issues/11"
}
|
gharchive/issue
|
EchoClient and EchoServer unable to establish connection
I can successfully compile the project on Ubuntu. 18.04,but when I run the sample client I get the following error:
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=server -host=<IP_ADDRESS> -port=6666 -colorlogtostderr=true -alsologtostderr=true
I0514 08:35:31.092536 28271 EchoServer.h:80] Echo server started at: [::]:6666
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=client -host=<IP_ADDRESS> -port=6666 -colorlogtostderr=true -log_dir="/home/vmtest/Documents/ietf_quic/mvfst/_build/build/quic/samples/" -alsologtostderr=true
I0514 08:36:33.769158 28283 EchoClient.h:127] EchoClient connecting to <IP_ADDRESS>:6666
E0514 08:36:33.771145 28283 EchoClient.h:82] EchoClient error: Connect failed
It seems that the handshake method failed. (ClientHandshake::connect() )
What should I do to make the client and server connect successfully?
Can you include the verbose log from both the client and the server?
i.e. ./echo -mode=server -host=<IP_ADDRESS> -port=6666 -colorlogtostderr=true -alsologtostderr=true --v=10
@udippant
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=client -host=<IP_ADDRESS> -port=6666 -colorlogtostderr=true -log_dir="/home/vmtest/Documents/ietf_quic/mvfst/_build/build/quic/samples/" -alsologtostderr=true --v=10
I0514 09:01:18.038892 28311 EventBase.cpp:117] EventBase(): Created.
I0514 09:01:18.039906 28312 EventBase.cpp:280] EventBase(): Starting loop.
I0514 09:01:18.040313 28312 QuicClientTransport.cpp:50] client created client CID=b1fbc0e40a8a05dc server CID=None peer address=
I0514 09:01:18.040407 28312 EchoClient.h:127] EchoClient connecting to <IP_ADDRESS>:6666
I0514 09:01:18.041589 28312 StateMachine-inl.h:41] Transition from Uninitialized to ExpectingServerHello
I0514 09:01:18.041658 28312 QuicTransportFunctions.cpp:862] Client writing data using scheduler=CryptoAndAcksScheduler client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.041740 28312 QuicPacketScheduler.cpp:487] Wrote crypto frame offset=0 bytesWritten=234 client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.042423 28312 QuicTransportFunctions.cpp:184] Client sent packetNum=0 in space=InitialSpace size=1255 client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.042490 28312 QuicTransportFunctions.cpp:71] Client sent packetNum=0 space=InitialSpace client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.042683 28312 QuicTransportFunctions.cpp:559] Client written crypto and acks data type=Initial packets=1 client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.042752 28312 QuicLossFunctions.h:189] setLossDetectionAlarm setting transmission alarm=99ms method=Handshake outstanding=1 handshakePackets=1 pureAckPackets=0 Client client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.042807 28312 QuicTransportBase.cpp:1974] schedulePathValidationTimeout cancel timeout client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.042855 28312 QuicTransportBase.cpp:1038] Client stopping write looper client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.042981 28312 AsyncUDPSocket.cpp:491] AsyncSocket::handleErrMessages(): recvmsg returned 1
I0514 09:01:18.043046 28312 AsyncUDPSocket.cpp:491] AsyncSocket::handleErrMessages(): recvmsg returned -1
I0514 09:01:18.043131 28312 QuicTransportBase.cpp:274] Stopping read looper due to immediate close client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.043187 28312 QuicTransportBase.cpp:692] Stopping read looper client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.043282 28312 QuicTransportBase.cpp:1000] Stopping peek looper client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
I0514 09:01:18.043331 28312 QuicTransportBase.cpp:1025] Client stopping write looper because conn closed client CID=b1fbc0e40a8a05dc server CID=None peer address=<IP_ADDRESS>:6666
E0514 09:01:18.043413 28312 EchoClient.h:82] EchoClient error: Connect failed
I was able to reproduce this as well with the echo client / server examples:
./echo -mode=client -host=<IP_ADDRESS> -port=6666 -colorlogtostderr=true -log_dir="/home/agnosticdev/Documents/code/cpp/mvfast/_build/build/quic/samples/logs" -alsologtostderr=true
./echo -mode=server -host=<IP_ADDRESS> -port=6666 -colorlogtostderr=true -alsologtostderr=true --v=10
I0513 21:20:21.171392 14234 EchoServer.h:80] Echo server started at: [::]:6666
I0513 21:20:21.171388 14241 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d74f0 thread=139644201064192 processId=0
I0513 21:20:21.171394 14240 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d7210 thread=139644209456896 processId=0
I0513 21:20:21.171360 14236 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6680 thread=139644450768640 processId=0
I0513 21:20:21.171360 14237 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6960 thread=139644442375936 processId=0
I0513 21:20:21.171406 14242 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d77d0 thread=139644192671488 processId=0
I0513 21:20:21.171408 14234 EventBase.cpp:280] EventBase(): Starting loop.
I0513 21:20:21.171394 14238 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6c20 thread=139644433983232 processId=0
It looks like after resumeRead() calls out to AsyncUDPSocket and nothing else is recorded after that.
void QuicServerWorker::start() {
CHECK(socket_);
if (transportSettings_.pacingEnabled && !pacingTimer_) {
pacingTimer_ = TimerHighRes::newTimer(
evb_, transportSettings_.pacingTimerTickInterval);
}
socket_->resumeRead(this);
VLOG(10) << "Registered read on worker=" << this
<< " thread=" << folly::getCurrentThreadID()
<< " processId=" << (int)processId_;
}
void AsyncUDPSocket::resumeRead(ReadCallback* cob) {
CHECK(!readCallback_) << "Another read callback already installed";
CHECK_NE(NetworkSocket(), fd_)
<< "UDP server socket not yet bind to an address";
readCallback_ = CHECK_NOTNULL(cob);
if (!updateRegistration()) {
AsyncSocketException ex(
AsyncSocketException::NOT_OPEN, "failed to register for accept events");
readCallback_ = nullptr;
cob->onReadError(ex);
return;
}
}
Will keep digging.
there looks to be something off with bind. can you try remove the —client and —server arguments from your commands?
@lnicco
After updating the commands to:
Echo Server: ./echo --v=10
Echo Client: ./echo -mode=client --v=10
I am now able to see data being echoed on the server side:
I0514 05:09:48.316179 25235 QuicTransportBase.cpp:1143] Delivered eof to app for stream=0 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316190 25235 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316202 25235 QuicTransportBase.cpp:1023] Stopping peek looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316215 25235 QuicTransportBase.cpp:1043] Server stopping write looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316227 25235 EchoHandler.h:73] Got len=5 eof=1 total=5 **data=mvfst**
I0514 05:09:48.316241 25235 QuicTransportBase.cpp:1038] Server running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316254 25235 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316267 25235 QuicTransportBase.cpp:1038] Server running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316282 25235 QuicTransportFunctions.cpp:865] Server writing data using scheduler=FrameScheduler client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316308 25235 QuicWriteCodec.cpp:118] writing frame stream=0 offset=0 data=10 fin=1
Client:
b90af82c7 peer address=[::1]:6666
I0514 05:09:41.108058 25237 QuicTransportBase.cpp:1979] schedulePathValidationTimeout cancel timeout client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108064 25237 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108070 25237 QuicTransportBase.cpp:1023] Stopping peek looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108076 25237 QuicTransportBase.cpp:1043] Client stopping write looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
mvfst
I0514 05:09:48.315528 25237 QuicTransportBase.cpp:581] Setting setReadCallback for stream=0 cb=0x7ffcd4996c48 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315577 25237 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315599 25237 QuicTransportBase.cpp:1038] Client running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315615 25237 **EchoClient.h:167] EchoClient wrote "mvfst", len=5 on stream=0**
I0514 05:09:48.315644 25237 QuicTransportFunctions.cpp:865] Client writing data using scheduler=FrameSchedulerWithoutCrypto client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315671 25237 QuicWriteCodec.cpp:118] writing frame stream=0 offset=0 data=5 fin=1
Do you want me to put a PR up to switch the echo example on the README?
I have a feeling like it’s something wrong with the binding to the v4 interface on the host. By default we bind to the v6 localhost which is ::1.
Ya please feel free to put up a pr to fix it to v6 localhost.
Ahh, yes. I see it now. It looks like the client() takes the FLAGS_host argument while the server is started with just FLAGS_port and FLAGS_port, so the server is then by default binding to ::1. Thank you!
if (FLAGS_mode == "server") {
EchoServer server(FLAGS_port, FLAGS_port);
server.start();
} else if (FLAGS_mode == "client") {
if (FLAGS_host.empty() || FLAGS_port == 0) {
LOG(ERROR) << "EchoClient expected --host and --port";
return -2;
}
EchoClient client(FLAGS_host, FLAGS_port, FLAGS_pr);
client.start();
} else {
LOG(ERROR) << "Unknown mode specified: " << FLAGS_mode;
return -1;
}
The update above does include passing in a IPv4 or IPv6 host argument to the echo server as well as a README fix.
Addressed on https://github.com/facebookincubator/mvfst/pull/13
|
2025-04-01T06:38:38.724804
| 2024-11-26T06:14:14
|
2693312943
|
{
"authors": [
"yingsu00"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5816",
"repo": "facebookincubator/velox",
"url": "https://github.com/facebookincubator/velox/issues/11661"
}
|
gharchive/issue
|
Remove the BloomFilter classes from dwio/parquet/writer/arrow/tests/
Description
The classes were moved from Arrow Parquet writer to dwio/parquet/common in "Move arrow parquet bloom filter code to velox dwio (#10516)", but there is still another copy in velox/dwio/parquet/writer/arrow/tests/. The references in velox/dwio/parquet/writer/arrow/tests/ shall be updated to the ones in dwio/parquet/common
cc @pedroerp @nmahadevuni
|
2025-04-01T06:38:38.726544
| 2023-05-09T10:55:59
|
1701850022
|
{
"authors": [
"majetideepak"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5817",
"repo": "facebookincubator/velox",
"url": "https://github.com/facebookincubator/velox/pull/4875"
}
|
gharchive/pull-request
|
Update Types documentation
Update Decimal and Interval Day to Second type documentation since they
are now logical types.
Add documentation for Presto Types.
@mbasmanova I addressed your comments. Can you make another pass? Thanks.
I added a note for OPAQUE and UNKNOWN types as well.
@mbasmanova thank you for your feedback. I addressed all of them.
|
2025-04-01T06:38:38.728957
| 2023-10-19T12:43:03
|
1952168490
|
{
"authors": [
"duanmeng",
"mbasmanova"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5818",
"repo": "facebookincubator/velox",
"url": "https://github.com/facebookincubator/velox/pull/7138"
}
|
gharchive/pull-request
|
Add ContainerRowSerde::compareWithNulls API for ByteStream compare
Presto aggregate functions that compare values of complex types must detect
cases when complex values contain nulls. The new
ContainerRowSerde::compareWithNulls API allows signaling the case when a complex
type value contains a null when comparing ByteStream with ByteStream.
Similar to https://github.com/facebookincubator/velox/pull/6419.
I'm getting Diff too old error. Would you rebase?
I'm getting Diff too old error. Would you rebase?
@mbasmanova Got it, done.
@duanmeng Thanks.
|
2025-04-01T06:38:38.804923
| 2020-09-03T11:52:51
|
691903308
|
{
"authors": [
"rpartsey",
"srama2512"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5819",
"repo": "facebookresearch/OccupancyAnticipation",
"url": "https://github.com/facebookresearch/OccupancyAnticipation/issues/2"
}
|
gharchive/issue
|
Train models config directory path
Shouldn't the model config path in the configs table in the README.md Training models section contain model_configs directory as shown below?
Model
Config directory
ANS(rgb)
configs/model_configs/ans_rgb
ANS(depth)
configs/model_configs/ans_depth
OccAnt(rgb)
configs/model_configs/occant_rgb
OccAnt(depth)
configs/model_configs/occant_depth
OccAnt(rgbd)
configs/model_configs/occant_rgbd
OccAnt(GT)
configs/model_configs/occant_ground_truth
The pre-models that are available do not obey this directory structure. The above was just an indication pointing to sample config files for each model. In each case, the paths for the following must be changed based on the user's needs:
TENSORBOARD_DIR
EVAL_CKPT_PATH_DIR
VIDEO_DIR
CHECKPOINT_FOLDER
Got it.
In my humble opinion, it's a bit confusing because we have the configs directory in the project root.
And I initially thought that the path is specified relative to the configs directory.
Maybe it would be better to add some explanation and angle brackets around config like this
Model
Config directory
ANS(rgb)
<configs>/ans_rgb
ANS(depth)
<configs>/ans_depth
OccAnt(rgb)
<configs>/occant_rgb
OccAnt(depth)
<configs>/occant_depth
OccAnt(rgbd)
<configs>/occant_rgbd
OccAnt(GT)
<configs>/occant_ground_truth
where <config> is an indication pointing to sample config files for each model.
All paths in the repo are relative the main directory. So, the paths specified are valid paths for example config files. Is it an issue with the pre-trained models?
No no, I just got confused, because the paths specified in the Config directory column don't exist.
For example, there is a configs directory in the project root, but the path configs/ans_rgb doesn't exist (but the path configs/model_configs/ans_rgb does exist).
That's why I suggested either change it to the correct path or to add an explanation that the config is an indication pointing to sample config files for each model.
Oh, got it. The model_configs was missing. Yes, I will fix this in my next update. Thanks!
|
2025-04-01T06:38:38.846291
| 2019-08-02T08:11:45
|
476053815
|
{
"authors": [
"Skylixia",
"chengfx",
"myleott",
"nonononanana",
"yarakhater"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5820",
"repo": "facebookresearch/fairseq",
"url": "https://github.com/facebookresearch/fairseq/issues/955"
}
|
gharchive/issue
|
Where is fairseq-preprocess
When I run following command in the shell script
for input_index in $(seq 1 2); do
fairseq-preprocess \
--only-source \
--trainpref $processed_data_dir/train.${input_index}.bpe \
--validpref $processed_data_dir/dev.${input_index}.bpe \
--testpref $processed_data_dir/test.${input_index}.bpe \
--destdir $processed_data_dir/Input.${input_index} \
--workers 4 \
--srcdict ${roberta_vocab_dir}/dict.txt
done
There is an issue that command not found
fairseq-preprocess: command not found
You need to run “pip install --editable .” to install the fairseq-preprocess executable.
sorry, from which directory shall I run “pip install --editable .” ?
You need to run “pip install --editable .” to install the fairseq-preprocess executable.
@myleott
Even after running this and having fairseq successfully installed the fairseq-preprocess is not found
@Skylixia Were you able to fix this?
|
2025-04-01T06:38:38.902157
| 2020-07-27T19:35:08
|
666534732
|
{
"authors": [
"KenaHemnani",
"Skylion007",
"VladislavHrosinkov",
"aclegg3",
"erikwijmans"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5821",
"repo": "facebookresearch/habitat-sim",
"url": "https://github.com/facebookresearch/habitat-sim/issues/703"
}
|
gharchive/issue
|
accessing build/viewer
❓ Questions and Help
How does one access build/viewer code? It does not seem to be on GitHub.
Just pass -DBUILD_GUI_VIEWERS=ON to CMake.
Forgive me, but how is CMake involved? I know it it a dependency, but I have installed it without specifically in invoking it.
How does one access build/viewer code
Is this what you are looking for: https://github.com/facebookresearch/habitat-sim/blob/master/src/utils/viewer/viewer.cpp?
How to build this viewer as it is already not there in build folder?
You'll need to build habitat-sim for a system with display as described here: https://github.com/facebookresearch/habitat-sim/blob/master/BUILD_FROM_SOURCE.md (i.e., do not include the --headless argument).
Hii @aclegg3 thank you for response , I installed habitat-sim using the same .But, still got error as :
./build/viewer no such file or directory exists.
@KenaHemnani then we'll need more info from your build before we can move forward. You should see an alias to viewer in the habitat-sim/build directory and a habitat-sim/utils/viewer/ directory containing the viewer application.
Hii @aclegg3 I reinstalled habitat-sim using conda . The headless version is working fine , but with display I am not able to visualize even with VNC , Yes I do have habitat-viewer inside habitat-sim/utils/viewer/ directory .So, I run following command
./habitat-viewer ~/DIR/habitat-lab/data/scene_datasets/hitat-test-scenes/skokloster-castle.glb
It shows following `error:
Is there any other way to visualize the performance of agents as how it is navigating inside 3D habitat environment? locally on small dataset.
`
|
2025-04-01T06:38:38.911964
| 2024-08-23T18:43:15
|
2483681211
|
{
"authors": [
"jturner65"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5822",
"repo": "facebookresearch/habitat-sim",
"url": "https://github.com/facebookresearch/habitat-sim/pull/2457"
}
|
gharchive/pull-request
|
--[BE][WIP] - Dataset Diagnostics and Attributes Deduplication
Motivation and Context
This PR introduces a transparent dataset diagnostics protocol that can be controlled by setting flags using the optional tag "request_diagnostics" placed in the scene dataset config, followed by either an individual string or a list of strings, each specifying a desired diagnostic to be performed.
As a proof of concept, as well as to address an existing issue with the base hssd scene instances, the following tags are currently supported :
SaveCorrected : save any files that have been tested and corrected. Ignored if no tests specified
TestForSceneInstanceDuplicates : test for duplicate rigid/articulated object instances on scene instance load, not loading duplicates if found.
TestForSemanticRegionDuplicates : test for duplicate semantic region definitions on semantic attributes load, not loading duplicates if found.
This PR will perform conditional de-duplication of any loaded subconfiguration, such as Object Instances from the Scene Instance configuration file, if the appropriate test (TestForSceneInstanceDuplicates) is requested. If multiple such object instances are loaded that have identical data, then the extra duplicates will not be saved as part of the internal representation of the scene instance.
If SaveCorrected is specified, the scene instance, in this case, minus the extra duplicates, will be saved to disk. Otherwise, it will just be retained in memory for the lifetime of the execution.
This functionality is also available for SemanticAttributes/configs, should identical SemanticRegion definitions exist within the original json config description.
This PR is currently set up to prevent any duplicate SceneObjectInstanceAttributes or SceneAOInstanceAttributes from being saved when a SceneInstanceAttributes is being created for manual save to disk.
This PR also includes a renaming refactor for attributes and attributes manager base classes to fall in line with standard naming protocol and be less confusing.
Still needed :
Actually saving the modified attributes if the diagnostics indicate it and the user requested saving.
Tests
How Has This Been Tested
Locally c++ and python tests pass (currently transparent pass-through)
Types of changes
[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
So currently to request a diagnostic, say on duplicate scene object instances, you would add the following line to the scene dataset config :
"request_diagnostics":"TestForSceneInstanceDuplicates",
or
"request_diagnostics":["TestForSceneInstanceDuplicates"],
if you wanted to save the scene instances that were corrected by the diagnostic process, you would use
"request_diagnostics":["TestForSceneInstanceDuplicates", "SaveCorrected"],
and when you do not wish for any diagnostics anymore, you would just delete the line from the scene dataset config.
Other mechanisms for performing these diagnostics would be easy to implement, this was just the mechanism I started with.
|
2025-04-01T06:38:38.913617
| 2024-08-07T12:26:34
|
2453359549
|
{
"authors": [
"RanDing2000",
"yvsriram"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5823",
"repo": "facebookresearch/home-robot",
"url": "https://github.com/facebookresearch/home-robot/issues/514"
}
|
gharchive/issue
|
Problems opening GUI
Does anyone know how to open gui for the ovmm?
Hey this is the script for GUI: https://github.com/facebookresearch/habitat-lab/blob/ovmm_v0.2.5/examples/interactive_play.py.
|
2025-04-01T06:38:38.922673
| 2018-11-01T01:16:26
|
376217113
|
{
"authors": [
"Jiayuan-Gu",
"fmassa"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5824",
"repo": "facebookresearch/maskrcnn-benchmark",
"url": "https://github.com/facebookresearch/maskrcnn-benchmark/issues/84"
}
|
gharchive/issue
|
Reduce the training loss
❓ Questions and Help
Is it necessary to reduce the training losses through multiple processes in trainer.py?
I think current reduction on losses only work for logging instead of backward.
Could anyone explain about which parts of codes average the gradients from all processes when doing distributed training?
The reduction in the losses is indeed only needed for logging purposes, and not for training.
The gradient averaging is handled by DistributedDataParallel, and is done automatically for us when we call .backward.
I'm closing this issue as I believe I have answered your question, but let me know if something isn't clear.
|
2025-04-01T06:38:38.925780
| 2018-11-27T04:33:13
|
384618269
|
{
"authors": [
"JackUrb",
"luzhilin19951120"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5825",
"repo": "facebookresearch/visdom",
"url": "https://github.com/facebookresearch/visdom/issues/514"
}
|
gharchive/issue
|
Where is envs buffers?
I encounter a problem when trying to find the JSON files of all the visdom envs.
First of all, I can not find where the visdom server save all the envs buffer path. I use buffer path" referring to the path where all the unsaved envs are kept. This buffer seems to be automatically cleared when the visdom server is shut down. However I need to find and use it when the server is still on.
Its path is definitely not "~/.visdom", and I would like to know where it is
The other thing is that I need to save some of the good envs and reload them freely. So far, the save button can save the envs file to "~/.visdom", but I can not find anyway to use these JSON files other than simply reboot the server.
How can I use another server (That say new IP new port) to load all the JSON file I pick(I would get the file from save button and move them elsewhere) from any path I set?
This 'buffer' is entirely in the server's python local memory in self.state[eid], it doesn't exist as a file. Hard saves are the only thing that push data to a file.
For the latter question you can move the files to a different folder and start the server with the -env_path <directory> option to point to that folder.
@JackUrb Thanks~ This is what we are doing now. ^_^
|
2025-04-01T06:38:38.937084
| 2021-09-16T23:43:00
|
998771139
|
{
"authors": [
"facelessuser"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5826",
"repo": "facelessuser/coloraide",
"url": "https://github.com/facelessuser/coloraide/pull/70"
}
|
gharchive/pull-request
|
Even better upgrades to playground
Allow loading notebook pages
Add spinner to show pyodide is loading and/or working
@gir-bot lgtm
|
2025-04-01T06:38:38.957739
| 2024-03-12T11:17:54
|
2181362222
|
{
"authors": [
"faddat",
"kienn6034"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5829",
"repo": "faddat/ibc-apps",
"url": "https://github.com/faddat/ibc-apps/pull/1"
}
|
gharchive/pull-request
|
test: update tests for wasmhooks
Notes
update simapp and tests to be compatible with sdk 50, and make all tests pass
Tests pass
@faddat hey, i'm implementing ibc-hooks for eve, and since there is no completed version of ibc-hooks v8, i will continue working on your branch
@faddat hi sir, tests and lint passed, please review this PR
thank you!
|
2025-04-01T06:38:38.981550
| 2020-09-15T10:45:16
|
701821135
|
{
"authors": [
"carloscaverobarca",
"miquinti"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5830",
"repo": "fair4health/f4h-portal-ui",
"url": "https://github.com/fair4health/f4h-portal-ui/pull/83"
}
|
gharchive/pull-request
|
Add authorization token to be allowed to access the backend
Change endPoint to Access to platform backend to get dynamic projects list
Proposed Changes
Add endPiont to evirioment
Add header to include valid token to access
Get project list from server
Pull request checklist
Please check if your PR fulfills the following requirements:
[ ] Tests
[x] Build locally
[ ] Code format / lint
[ ] Docs have been reviewed and added
Pull request type
Please check the type of change your PR introduces:
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):
What is the current behavior?
Issue Number: N/A
The sistem access to backend to get the list of project available using a valid token
Fixes #81
What is the new behavior?
Does this introduce a breaking change?
[ ] Yes
[x] No
Other information
Be careful with the blank spaces in the checkbox of the PR. Try to put labels, use the issue in the Kanban project and assign the PR to someone
|
2025-04-01T06:38:39.012707
| 2020-04-28T12:53:29
|
608293669
|
{
"authors": [
"kardwen",
"markstos",
"teutat3s"
],
"license": "WTFPL",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5831",
"repo": "fairyglade/ly",
"url": "https://github.com/fairyglade/ly/issues/205"
}
|
gharchive/issue
|
[sway systemd setup] unable to re-login after exiting sway
Hello,
thank you for making this beautiful display manager!
OS: manjaro with latest linux55 kernel
$ sway --version
sway version 1.4
wlroots version 0.10.1-1
ly version: installed via yay -S ly-git v0.5.0.r9.gaa25ede-1
When trying to logout and then re-login with sway I see the following errors:
Click to expand!
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: unable to locate daemon control file
Apr 28 14:53:59 teutates-laptop audit[657]: USER_AUTH pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,p>
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: stashed password to try later in open session
Apr 28 14:53:59 teutates-laptop audit[657]: USER_ACCT pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix>
Apr 28 14:53:59 teutates-laptop audit[657]: CRED_ACQ pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shell>
Apr 28 14:53:59 teutates-laptop ly[657]: pam_unix(ly:session): session opened for user teutates by (uid=0)
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: unable to locate daemon control file
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Apr 28 14:53:59 teutates-laptop audit[657]: USER_START pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pa>
Apr 28 14:53:59 teutates-laptop systemd[1037]: Started sway - SirCmpwn's Wayland window manager.
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] Linux teutates-laptop 5.5.19-1-MANJARO #1 SMP PREEMPT Tue>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:168] Contents of /etc/lsb-release:
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_ID=ManjaroLinux
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_RELEASE=20.0
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_CODENAME=Lysia
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_DESCRIPTION="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:168] Contents of /etc/os-release:
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] NAME="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ID=manjaro
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ID_LIKE=arch
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] PRETTY_NAME="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ANSI_COLOR="1;32"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] HOME_URL="https://www.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] SUPPORT_URL="https://www.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] BUG_REPORT_URL="https://bugs.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] LOGO=manjarolinux
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] LD_LIBRARY_PATH=(null)
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] LD_PRELOAD=(null)
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] PATH=/home/teutates/.local/bin:/sbin:/bin:/usr/local/sbin:/us>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] SWAYSOCK=/run/user/1000/sway-ipc.1000.1062.sock
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/server.c:40] Preparing Wayland server initialization
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/wayland/backend.c:255] Creating wayland backend
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/wayland/backend.c:271] Could not connect to remote display: No such fi>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/noop/backend.c:51] Creating noop backend
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/server.c:47] Unable to create backend
Apr 28 14:53:59 teutates-laptop systemd[1037]: sway.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 14:53:59 teutates-laptop systemd[1037]: sway.service: Failed with result 'exit-code'.
Apr 28 14:53:59 teutates-laptop ly[657]: pam_unix(ly:session): session closed for user teutates
Apr 28 14:53:59 teutates-laptop audit[657]: USER_END pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam>
Apr 28 14:53:59 teutates-laptop audit[657]: CRED_DISP pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shel
Steps to reproduce:
I have setup sway to start with systemd as described in the sway wiki (follow the whole page, also setup sway itself as a --user service)
setup ly as a systemd service as well
exit sway with swaymsg exit
get logged out and redirected correctly to ly
try to login again: ly seems to refresh itself and does not open sway. in the logs the mentioned error messsages show up
Expected:
ly should start a new sway session successfully.
I am very curious if this is reproducable for others and would be happy to provide more debugging info as needed.
I cannot reproduce with Sway 1.5 on Arch Linux, but I'm not running Sway as a systemd service.
Consider trying the sway-services project instead, available as sway-services-git package in the Arch Linux AUR.
One thing it does is to clean up some environment variables set by Sway upon exit. Perhaps if these are not unset it could cause a problem upon re-login:
https://github.com/xdbob/sway-services/blob/master/bin/sway-user-service
You see the sway.service file also contains code to clean-up environment vars:
https://github.com/xdbob/sway-services/blob/5ccb33b92c78a0b95216b3c3470d0d45e76cea2c/systemd/sway.service
Consider trying the sway-services project instead, available as sway-services-git package in the Arch Linux AUR.
One thing it does is to clean up some environment variables set by Sway upon exit. Perhaps if these are not unset it could cause a problem upon re-login:
https://github.com/xdbob/sway-services/blob/master/bin/sway-user-service
You see the sway.service file also contains code to clean-up environment vars:
https://github.com/xdbob/sway-services/blob/5ccb33b92c78a0b95216b3c3470d0d45e76cea2c/systemd/sway.service
Thank you @markstos, I'll definitely check that out and report back how it goes.
Thank you @markstos, I'll definitely check that out and report back how it goes.
Nice! This little detail in sway.service does the trick:
https://github.com/xdbob/sway-services/blob/eab69fa5253ad494921833e46b6476d7bf675ed4/systemd/sway.service#L19
ExecStopPost=/usr/bin/systemctl --user unset-environment SWAYSOCK DISPLAY I3SOCK WAYLAND_DISPLAY
Nice! This little detail in sway.service does the trick:
https://github.com/xdbob/sway-services/blob/eab69fa5253ad494921833e46b6476d7bf675ed4/systemd/sway.service#L19
ExecStopPost=/usr/bin/systemctl --user unset-environment SWAYSOCK DISPLAY I3SOCK WAYLAND_DISPLAY
There seems to be an similiar issue with River WM
|
2025-04-01T06:38:39.025608
| 2021-12-23T09:07:19
|
1087517040
|
{
"authors": [
"chamini2",
"mkam039",
"thomasaarholt"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5832",
"repo": "fal-ai/fal",
"url": "https://github.com/fal-ai/fal/issues/87"
}
|
gharchive/issue
|
fal installation instructions with dbt 1.0
Trying fal now after a recommendation through Slack. I installed dbt 1.0 by pip install dbt-core, as well as fal by pip install fal.
I ran into a few snags when installing fal in a clean python 3.9 environment, and it might be worth adding a note about dbt 1.0 to the fal readme.
fal currently doesn't install dbt. I assume this is because of the change from dbt to dbt-core.
fal relies on bigquery here, which means that one needs to run pip install dbt-bigquery. This should be explicitly stated on the readme, and preferably not be a requirement.
For the second point, it would be much better to use:
from dbt.adapters.factory import load_plugin
load_plugin("bigquery") # returns dbt.adapters.bigquery.connections.BigQueryCredentials
Hi @thomasaarholt! Thanks for raising this issue. We are actively working on supporting dbt 1.0 (see #69) and should release the new version soon. You're right, we should add a note about dbt 1.0 in README.
Ah! I searched for 1.0 and didn't find the PR (I had to type 1.0.0...) :)
My bigquery fix above works on 0.20 as well, I just checked:
Should I make a PR?
Ah, I see you have a fix as well in the 1.0.0 PR :) I'll leave that to you!
@thomasaarholt, we have just released a version compatible with dbt 1.0.0.
pip install fal==0.1.35
Please let us know how it goes and if anything else comes up!
|
2025-04-01T06:38:39.039074
| 2022-05-02T13:12:17
|
1222871186
|
{
"authors": [
"FedeDP"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5833",
"repo": "falcosecurity/driverkit",
"url": "https://github.com/falcosecurity/driverkit/issues/142"
}
|
gharchive/issue
|
Driverkit Debian/Ubuntu builder wrong kernel version
Describe the bug
Basically, kernel-crawler kernels list is exporting fields like:
"kernelrelease": "5.10.103-1-amd64",
(https://github.com/falcosecurity/kernel-crawler/blob/main/kernels/x86_64/list.json#L7368),
whose url is http://security.debian.org/pool/updates/main/l/linux/linux-headers-5.10.0-12-amd64_5.10.103-1_amd64.deb
But Driverkit is reading those as 5.10.0-12 kernelversion instead, using a regex that expects:
href="(linux-headers-5\.10\.103-1-(amd64)_.*(amd64|all)\.deb)"
This means that running driverkit with:
driverkit docker --output-module /tmp/falco.ko --kernelversion=1 --kernelrelease=5.10.103-1-amd64 --target=debian
will fail, because it expects 5.10.0-12 kernelrelease.
Fact is, kernel-crawler is right because it is using packages metadata, eg (notice the Version line):
Package: linux-headers-5.10.0-12-common
Source: linux
Version: 5.10.103-1
Installed-Size: 51854
Maintainer: Debian Kernel Team<EMAIL_ADDRESS>Architecture: all
Description: Common header files for Linux 5.10.0-12
Homepage: https://www.kernel.org/
Description-md5: ab592fb1c299fa53a862c8eecd4486e6
Multi-Arch: foreign
Section: kernel
Priority: optional
Filename: pool/updates/main/l/linux/linux-headers-5.10.0-12-common_5.10.103-1_all.deb
Size: 8940952
SHA256: 9753625d0256066b37dd92d55621ebb5a76c3a9e6c2579607531b0809f6b3552
Of course, changing the way driverkit behaves would break every existing config.
I am not sure whether "breaking" kernel-crawler to match driverkit output would be a good idea.
I can try to add a new parameter to driverkit configs header_urls[], that when set, would force certain headers instead of trying to fetch the correct one programmatically.
Moreover, i could even try to double the matching pattern, trying the current driverkit before, and if it fails, fallbacking at trying the new pattern.
What would you think?
Do you have any idea?
/cc @zuc @maxgio92
Proposed PR for arm support (https://github.com/falcosecurity/driverkit/pull/143) address this issue using both evaluated options:
adds a kernelurls param
doubled the matching pattern
|
2025-04-01T06:38:39.047554
| 2020-10-29T10:27:32
|
732190830
|
{
"authors": [
"leogr",
"poiana"
],
"license": "CC-BY-4.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5834",
"repo": "falcosecurity/falco-website",
"url": "https://github.com/falcosecurity/falco-website/pull/307"
}
|
gharchive/pull-request
|
update(data/en): correct and update gRPC config description
What type of PR is this?
/kind bug
/kind cleanup
/kind content
Any specific area of the project related to this PR?
/area documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:
The gRPC config description was not updated w.r.t the unix socket binding type.
Fixes #
Special notes for your reviewer:
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leogr
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
LGTM label has been added. Git tree hash: 332d7cb66b9919b5415f0854bc947fbf6b345fe8
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS [fntlnz]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
|
2025-04-01T06:38:39.068513
| 2023-07-12T09:43:26
|
1800591408
|
{
"authors": [
"incertum",
"leogr",
"loresuso",
"poiana"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5835",
"repo": "falcosecurity/rules",
"url": "https://github.com/falcosecurity/rules/pull/98"
}
|
gharchive/pull-request
|
wip: new(rules): add rule for detecting fileless execution via memfd_create
What type of PR is this?
Uncomment one (or more) /kind <> lines:
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
Any specific area of the project related to this PR?
Uncomment one (or more) /area <> lines:
/area rules
/area registry
/area build
/area documentation
What this PR does / why we need it:
This PR takes advantage of a new incoming Falco feature for detecting fileless execution via memfd_create. This is a very well known defense evasion technique that threat actors might use to execute malware on victim machines. It has been used in the past, but also pretty recently as reported by these two articles:
https://cybersecurity.att.com/blogs/labs-research/malware-using-new-ezuri-memory-loader
https://www.wiz.io/blog/pyloose-first-python-based-fileless-attack-on-cloud-workloads
Putting this on wip until the feature lands in Falco.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign andreagit97 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@loresuso we can soon start with merging rules that make the rules file incompatible with the current Falco as the next release is planned for end of Sep.
After merging this rule at maturity_incubating we can bump to maturity_stable in a follow up PR. That way we honor our new guidelines. CC @darryk10 @leogr
After merging this rule at maturity_incubating we can bump to maturity_stable in a follow up PR. That way we honor our new guidelines. CC @darryk10 @leogr
:+1:
Rules files have been split. @loresuso could you rebase this PR and address the above suggestions, please? :pray:
IMO it makes sense to uniformly bump the engine version. In this way, when we graduate rules, we don't need to bother or remember how the version should be bumped, and just move the rule between files, but I'm open to discuss!
/hold
We need to bump the required engine version. @leogr @LucaGuerra do we bump the rules engine uniformly in all rules files? I would vote for that!
What's the benefit of having the same required_engine_version?
The only two consequences I see
We will have to bump the minor version in all rules files https://github.com/falcosecurity/rules/blob/main/RELEASE.md#versioning-a-ruleset
We will make all files not compatible with a previous Falco engine (even if they are)
Moreover, the CI should already be able to check (and inform us) when an engine version bump is required. Indeed, this jobs matrix indicates that falco-incubating_rules.yaml is no longer compatible with 0.35.0 because the missing field
In the end, I don't have a strong opinion and am open to any solution. I just don't see the benefit of doing this (perhaps am I missing something? :thinking: )
In case we decide to bump all files, I still would avoid bumping falco-deprecated_rules.yaml, since it does not make much sense to me.
@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?
@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?
The required_engine_version applies at the single file level only (@jasondellaluce correct me if I'm wrong). It acts as a validation condition when loading the rules files, so it won't be overridden by other rules files. Basically, files will be validated one by one, the first failure will stop the whole process, regardless of the loading order.
@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?
The required_engine_version applies at the single file level only (@jasondellaluce correct me if I'm wrong). It acts as a validation condition when loading the rules files, so it won't be overridden by other rules files. Basically, files will be validated one by one, the first failure will stop the whole process, regardless of the loading order.
ok then let's just bump it in the respective file for now, thanks!
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS [incertum]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
LGTM label has been added. Git tree hash: 01650113bdbe0bb5383a3ee06151604fd4526b6b
/unhold
|
2025-04-01T06:38:39.109849
| 2024-01-22T07:08:45
|
2093236603
|
{
"authors": [
"VPraharsha03",
"fang2hou"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5836",
"repo": "fang2hou/starship-gruvbox-rainbow",
"url": "https://github.com/fang2hou/starship-gruvbox-rainbow/issues/1"
}
|
gharchive/issue
|
Nerd font and color scheme used for mac-os preview ?
@fang2hou Thanks for the preset, it looks amazing 🌟
Just one more thing, if you wouldn't mind could you please also share the nerd font and terminal color scheme used in the Mac-OS preview ? as it looks the best among all the previews
I am using alacritty now.
The font is JetBrainsMono Nerd Font, you can download it from here.
My alacrity TOML
[colors.bright]
black = "#4b4b4b"
blue = "#9ac2bb"
cyan = "#aedea0"
green = "#c8c847"
magenta = "#eaa4b7"
red = "#ff5f4f"
white = "#ffffff"
yellow = "#ffc24b"
[colors.normal]
black = "#282828"
blue = "#80aa9e"
cyan = "#8bba7f"
green = "#b0b846"
magenta = "#d3869b"
red = "#f2594b"
white = "#e2cca9"
yellow = "#e9b143"
[colors.primary]
background = "#282828"
foreground = "#e2cca9"
[font]
size = 15.0
[font.bold]
family = "JetBrainsMono Nerd Font"
style = "Bold"
[font.bold_italic]
family = "JetBrainsMono Nerd Font"
style = "Bold Italic"
[font.italic]
family = "JetBrainsMono Nerd Font"
style = "Italic"
[font.normal]
family = "JetBrainsMono Nerd Font"
style = "Light"
[font.offset]
x = 0
y = 1
[window]
decorations = "full"
dynamic_padding = false
option_as_alt = "OnlyLeft"
resize_increments = true
[window.dimensions]
columns = 180
lines = 35
[window.padding]
x = 12
y = 12
Thank you for sharing the color scheme. I figured it out, I was using a regular styled mono version of the JetBrains Mono font, after changing to a non-mono medium styled version it looks similar
|
2025-04-01T06:38:39.147187
| 2022-12-09T05:13:52
|
1486016795
|
{
"authors": [
"pfletcherhill",
"varunsrin"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5837",
"repo": "farcasterxyz/hub",
"url": "https://github.com/farcasterxyz/hub/issues/280"
}
|
gharchive/issue
|
feat: support nft urls in reactions and replies
What is the feature you would like to implement?
Allow reactions and cast-replies to point to an NFT as their parent. We will eventually want to expand this to work for generic web URLs as well, though that can be cut if it adds a lot of complexity.
Why is this feature important?
Merkle supports NFT likes in a centralized manner, and NFT comments is one of the most requested features from users. If the protocol doesn't support it, clients will continue doing it in a centralized manner. Doing it in a decentralized way, makes this data more portable and available to other clients.
Will the protocol spec need to be updated??
Yes, we'll need to change the specification for the message fields for cast parents and reaction targets.
How should this feature be built? (optional)
TBD
Closing in favor of existing ticket https://github.com/farcasterxyz/hub/issues/231
|
2025-04-01T06:38:39.156363
| 2017-10-25T10:19:20
|
268343123
|
{
"authors": [
"ahundt",
"arodiss",
"infelane"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5838",
"repo": "farizrahman4u/keras-contrib",
"url": "https://github.com/farizrahman4u/keras-contrib/pull/174"
}
|
gharchive/pull-request
|
Fixed and extended Dead ReLU detector callback
Initially 'DeadReLUDetectorCallback was only working for Dense layers and the percentage of dead relu neurons was incorrect.
Corrected the percentage calculations
Extended for all layers with a ReLU activation (tested for conv2d and dense)
Tested on python 3.5 TF and Theano
For testing I had 1 fail, however I'm quite certain it is independent of my additions.
`self = <backend_test.TestBackend object at 0x7f4f68019470>
def test_moments(self):
input_shape = (10, 10, 10, 10)
x_0 = np.zeros(input_shape)
x_1 = np.ones(input_shape)
x_random = np.random.random(input_shape)
th_axes = [0, 2, 3]
tf_axes = [0, 1, 2]
for ip in [x_0, x_1, x_random]:
for axes in [th_axes, tf_axes]:
for keep_dims in [True, False]:
ip_th = KTH.variable(ip)
th_mean, th_var = KCTH.moments(ip_th, axes, keep_dims=keep_dims)
ip_tf = KTF.variable(ip)
tf_mean, tf_var = KCTF.moments(ip_tf, axes, keep_dims=keep_dims)
th_mean_val = KTH.eval(th_mean)
tf_mean_val = KTF.eval(tf_mean)
th_var_val = KTH.eval(th_var)
tf_var_val = KTF.eval(tf_var)
assert_allclose(th_mean_val, tf_mean_val, rtol=1e-4)
assert_allclose(th_var_val, tf_var_val, rtol=1e-4)
E AssertionError:
E Not equal to tolerance rtol=0.0001, atol=0
E
E (mismatch 100.0%)
E x: array([[[[ 0.]],
E
E [[ 0.]],...
E y: array([[[[ 6.938894e-18]],
E
E [[ 6.938894e-18]],...
If people need a return vallue/callback, the request will come naturally.
Now... My check failed multiple times. For a test that worked on my pc (both py2.7 Tensorflow and py3.5 Tensorflow) an never by the 'ravis CI build'. In the end I just commented that part of the test, but now it gives errors about an other package. I don't know what I can/should do about that
@infelane I took a look at the errors and it seems they aren't related to your changes. Does that seem correct to you?
@ahundt The errors that raised were indeed outside my additions. I checked the code that raised the error and might have found a bug overthere. Do you think the dead_relu_detector can be merged? Maybe reopen the backend_test?
LGTM, merging, thanks for the contribution! 👍
Congrats for getting it merged
|
2025-04-01T06:38:39.172514
| 2019-05-04T03:44:32
|
440280792
|
{
"authors": [
"fasiha"
],
"license": "Unlicense",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5839",
"repo": "fasiha/curtiz-japanese-nlp",
"url": "https://github.com/fasiha/curtiz-japanese-nlp/issues/1"
}
|
gharchive/issue
|
Notes
1
For an @-subcard during a local quiz, the prompt sentence will be shown but with a piece of it replaced with the @-subprompt. In order to know which piece of the prompt sentence to hide, the @-subcard's pieces will be examined for cloze marks.
if no cloze marks found, look for the prompt, and if that fails, look for the responses, and if that fails, throw.
if cloze marks found in one item (or more, though that's probably an error), hide that in the sentence.
We can have a "linter" that will warn when no clozes are present in @-subcard and the prompt/response chosen is repeated in the sentence. Also if more than one item has a cloze mark.
2
Two Ebisu models are associated each global card. One global one shared by all instances of it. And one local one personal to it and this sentence. When you do a global review (all by itself), the local ones all get an active update. When you do a local review (with a single sentence), the global get a passive update.
3
Exponential decay and SRS might optimize long-term just-about-to-forget, hard-to-recall recall, but what if you want to optimize rapid recall? You see kanji on the subway, and sure if you've been doing your SRS you'll likely eventually get the answer (with a probability given by Ebisu), but you'll have rolled past it. The only way to do that is regular exposure.
When you do a local review (with a single sentence), the global get a passive update, and all other local reviews get an active update.
|
2025-04-01T06:38:39.173816
| 2023-05-13T20:57:30
|
1708738832
|
{
"authors": [
"camenduru",
"fasmide"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5840",
"repo": "fasmide/remotemoe",
"url": "https://github.com/fasmide/remotemoe/issues/21"
}
|
gharchive/issue
|
Is the remotemoe tunnel down?
I have been getting the error message 'This page isn't working' for more than five days 😭. Am I doing something wrong, or is the remotemoe tunnel down?
See https://github.com/fasmide/remotemoe/issues/19
|
2025-04-01T06:38:39.193280
| 2020-03-04T04:57:16
|
575137480
|
{
"authors": [
"cwza",
"sgugger"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5841",
"repo": "fastai/fastai2",
"url": "https://github.com/fastai/fastai2/pull/141"
}
|
gharchive/pull-request
|
fix AWD_LSTM not contiguous bug
Error: rnn: hx is not contiguous
This error happens when
bidir=True
bs decrease
run on gpu
The 1 and 2 cause self.hidden[l][0][:,:bs] be not contiguous, and with 3 the error happens.
Fix it by adding contiguous() after self.hidden[l][0][:,:bs] and add a test that can reproduce this error with cuda flag.
Thanks a lot for fixing!
|
2025-04-01T06:38:39.196656
| 2020-10-28T15:07:49
|
731530577
|
{
"authors": [
"armsp",
"hamelsmu"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5842",
"repo": "fastai/fastpages",
"url": "https://github.com/fastai/fastpages/issues/442"
}
|
gharchive/issue
|
Is there a way to have custom javascript in the rendered HTML for a blog post?
I have a blog post with Altair visualization made from Jupyter Notebook as usual. However, I want to add some custom JavaScript to it.
Inside the Jupyter notebook, you have to run the cell with the JavaScript every time you open it to see its effects, even though the rest of the interactivity of the Altair chart works without executing any cell. Because of this behavior, just publishing the jupyter notebook with the JavaScript code would probably not have any effect (I haven't actually tested it).
Similar to https://github.com/fastai/fastpages/pull/171 I want to have fastpages add a little JavaScript code in the rendered HTML for one of the posts, so that the already existing HTML for the charts are modified a little.
Is there a way to achieve this?
This is example of how custom javascript is injected into fastpages: https://github.com/fastai/fastpages/blob/master/_includes/custom-head.html
This requires you to customize fastpages and learn about how the internals work a bit more.
@hamelsmu That helped a lot and I just got it working. I think it's actually better to have custom scripts enabled via Jekyll.
great!
|
2025-04-01T06:38:39.198486
| 2021-01-25T14:48:39
|
793445003
|
{
"authors": [
"hamelsmu",
"spiritLHL"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5843",
"repo": "fastai/fastpages",
"url": "https://github.com/fastai/fastpages/issues/493"
}
|
gharchive/issue
|
Automatically generate a sitemap
I want to add my blog to the Google search engine, I need to generate a sitemap of the blog.
So can you add a feature that automatically generate a sitemap?
thanks. try this https://github.com/jekyll/jekyll-sitemap
thanks. try this https://github.com/jekyll/jekyll-sitemap
|
2025-04-01T06:38:39.216335
| 2024-05-13T02:50:34
|
2291692472
|
{
"authors": [
"3to1null",
"AIdjis",
"AdmWinther",
"Jkrox",
"Omachonu-prosper",
"RasmusN",
"Sarmad426",
"WilliamStam",
"ankit-brijwasi",
"arslanahmad768",
"atomicjarrod",
"ceb10n",
"killjoy1221",
"kingcwt",
"linpan",
"mavic111",
"pmsmanishchauhan",
"qodzero",
"rutexd",
"thecouchcoder"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5844",
"repo": "fastapi/fastapi",
"url": "https://github.com/fastapi/fastapi/issues/11573"
}
|
gharchive/issue
|
fastapi dev runs stuck
Privileged issue
[X] I'm @tiangolo or he asked me directly to create an issue here.
Issue Content
The first time I ran fastapi dev, there was no problem, but I encountered a code error. Then after I modified the code and saved it, a WARNING: WatchFiles detected changes in 'tool/index.py'. Reloading... then got stuck and could not exit.
Any updates on this @kingcwt? facing the same issue!
Could be related to: https://github.com/encode/uvicorn/issues/2000
I currently have a slightly different issue from yours @kingcwt but it's still an issue with fastapi cli (dev and run)
The Code
The Error
do not use the fastapi dev to run your application just use uvicorn instead, i do not face any issues with uvicorn
I tryied to reproduce it, but without success.
But sometimes I get the same problem running uvicorn with --reload in cmder/windows. I think it is related to uvicorn instead of fastapi
I'm having the same issue here on windows 10.
I think this is related: https://www.reddit.com/r/FastAPI/comments/13oynf6/keeps_old_routes_after_changing_cache_problem/
It is like fastapi keeps an old version of the code cached somewhere. Even if I force kill fastpi and restart it, it loads an old version of my code.
It works (for a while) if I change port.
I think uvicorn dev server is better as of now. As we are not getting any updates about the Fast API cli. Its important to note that this may be fixed in near future. It happens a lot with Fast API server. So you have to kill the terminal and open a new one to re-run the project. Its painful.
@Sarmad426 Yes, you are right i am also facing the same issue I tried with both the commands such as
fast API dev filename
or
if name == "main":
uvicorn.run("main:app", host="<IP_ADDRESS>", port=8000, reload=True)
Sometimes it stuck you have to forcefully close the server but still, the port is running on the cache. So you have to run the server again on a different port.
Running into a similar issue. I can I kill the the process with ctrl+c, but I cannot run on the same port. Attempting to run on the same port prints out the message like everything is working fine, but trying to access /docs spins forever. Switching to a new port works fine.
in pycharm if you use the "run" method to run the project then it tends to hand after reloading. if you task manager kill python it reloads again. something definately fishy there.
if you just do uvicorn --reload in terminal it tends to work better but still a massive PITA on windows :( easier to just not run it with reload
win11, py3.12, pycharm
can confirm. win 11.
issue present at least month.
WARNING: WatchFiles detected changes in 'config.py'. Reloading... and its stuck. No pycharm, vscode + venv, server command started by hand in terminal (❯ fastapi dev webserver.py --port 8080)
I wonder if this would still happen with uvicorn's --timeout-graceful-shutdown option. Using fastapi dev, you have to set it using an environment variable UVICORN_TIMEOUT_GRACEFUL_SHUTDOWN=5.
I have been getting this same problem whether uvicorn main:app --reload or fastapi dev method launching from powershell. (no pycharm here)
Win11.
VSCode
Python 3.12.6
FastAPI 0.115.0
Uvicorn 0.31.0
Resorting to Task Manager (Ctrl+Shift+Esc) and killing python tasks as Ctrl+C often won't quit server and closing powershell window and launching another doesn't seem to kill it either.
Installed fastapi using "fastapi[standard]" and also removed and tried just installing separately fastapi and uvicorn
Based on this thread #2000 just to test tried downgrading just uvicorn to 0.22 with no difference then to 0.21 (0.21.1) and sure enough it stops being stuck and reloads in a second?
WARNING: StatReload detected changes in 'api.py'. Reloading...
INFO: Started server process [9192]
INFO: Waiting for application startup.
INFO: Application startup complete.
I am also facing this issue recently with FastAPI reloading.
When we start the server, it works fine, and the APIs are functioning correctly.
However, when we make changes to the code and save it, the FastAPI server does not respond when the API is hit again, and the FastAPI server page shows the reload icon for a long time.
Windows stuff, I see, using WSL2 never encountered this issue.
For me the problem was avast scanning the app before allowing it to execute thus taking a long time. Disabled avast and suddenly it was working well
I am facing a similar issue using Uvicorn. When I make changes to the code and save it, Uvicorn reloads, showing the message 'Application shutdown completed.' After that, the APIs stop responding, and the terminal becomes unresponsive. Even pressing Ctrl+C doesn't work
I had the same problem with PyCharm FastAPI. When introducing a change, it used to get stuck on reload. (most likely couldn't kill the current process.) But I could resolve it by just using the terminal and running
uvicorn main:app --reload
It then worked like a charm.
I noticed that no matter what I do in Run/Debug Configuration of PyCharm, it wont be fixed there. I.E. if I choose Uvicorn in Run/Debug Config, I would still have the same problem. For me it works only when I lunch the server from terminal using Uvicorn.
I had same problem, fastapi dev got stuck. Then after i killed the terminal and started again, the schemas in the docs got stucks, it won't be updated even i modify the model schemas, it will works again when you start dev server with different port.
how fix it>
backto uvicorn ==0.20.0, this v can work.
backto uvicorn ==0.20.0, this v can work.
I have tried this method too, but the issue persists.
|
2025-04-01T06:38:39.220243
| 2023-07-20T12:24:10
|
1813880675
|
{
"authors": [
"MarkusSintonen",
"tiangolo"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5845",
"repo": "fastapi/fastapi",
"url": "https://github.com/fastapi/fastapi/pull/9916"
}
|
gharchive/pull-request
|
Fix ValidationExceptions missing type annotations after v0.100.0
Type information got lost from ValidationExceptions after v0.100.0. This PR brings them back. ErrorDetails is used as is from Pydantic V2. With V1 its compatible with Pydantic V1 .errors().
Related https://github.com/tiangolo/fastapi/discussions/9907
Checking the conversation in the discussion to understand the use case, it seems the use case would be solved by using a custom exception, that would be much simpler and independent of FastAPI internals. :nerd_face:
Given that, I'll pass on this one, but thanks for the interest! :coffee:
@tiangolo why the errors() can not be properly typed when the class is documented https://fastapi.tiangolo.com/tutorial/handling-errors/#override-request-validation-exceptions ?
|
2025-04-01T06:38:39.228954
| 2024-12-09T02:07:17
|
2725763804
|
{
"authors": [
"sacha-escudier",
"sinaatalay"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5846",
"repo": "fastfem/fastfem",
"url": "https://github.com/fastfem/fastfem/pull/38"
}
|
gharchive/pull-request
|
Connect functionalities from mesher and elements to plotter
This PR will connect functionalities from mesher and elements, and use PyVista to provide visual aid.
For reference, here is my playground script (for now).
import fastfem.mesh as m
import fastfem.plotter as p
import numpy as np
nh = 10
nv = 10
hl = 3
vl = 3
mesh = m.create_a_rectangle_mesh(
horizontal_length=hl,
vertical_length=vl,
nodes_in_horizontal_direction=nh,
nodes_in_vertical_direction=nv,
element_type="triangle",
file_name=None,
)
# Domains:
bottom_boundary = mesh["bottom_boundary"]
right_boundary = mesh["right_boundary"]
top_boundary = mesh["top_boundary"]
left_boundary = mesh["left_boundary"]
rectangle = mesh["surface"]
visualizer = p.VisualMesh(mesh)
visualizer.plot_mesh()
# Time
time_steps = 240
temperatures = np.zeros((time_steps, nv, nh))
# Dummy data
left_right_temp = 15
top_temp = 10
bottom_temp = 25
for t in range(time_steps):
for i in range(nv):
for j in range(nh):
x = j / (nh - 1) * hl
y = i / (nv - 1) * vl
if j == 0 or j == nh - 1:
temperatures[t, i, j] = left_right_temp
elif i == 0:
temperatures[t, i, j] = bottom_temp
elif i == nv - 1:
temperatures[t, i, j] = top_temp
else:
temperatures[t, i, j] = 20 + 20 * np.sin(2 * np.pi * x / hl) * \
np.cos(2 * np.pi * y / vl) * \
np.sin(np.pi * t / time_steps)
visualizer.animate_mesh(30, time_steps, temperatures)
Hi @sacha-escudier, I rebased this branch to main. There is an issue related to our API Reference in docs.
If you run
hatch run docs:serve
you will get this error:
WARNING - griffe: fastfem/plotter/mesh_visual.py:13: No type or annotation for parameter 'mesh'
WARNING - griffe: fastfem/plotter/mesh_visual.py:16: No type or annotation for returned value 1
That's why docs workflow fail currently.
Could you add all the type hints until there aren't any error in docs?
@sinaatalay type issue should be fixed now.
|
2025-04-01T06:38:39.254833
| 2021-12-28T11:48:50
|
1089837772
|
{
"authors": [
"mcollina"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5847",
"repo": "fastify/process-warning",
"url": "https://github.com/fastify/process-warning/pull/45"
}
|
gharchive/pull-request
|
Renamed to process-warning
Signed-off-by: Matteo Collina<EMAIL_ADDRESS>Fixes #43
Checklist
[ ] run npm run test and npm run benchmark
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message and code follows the Developer's Certification of Origin
and the Code of conduct
I'll bump the major and deprecate the previous module once this lands.
|
2025-04-01T06:38:39.262529
| 2018-04-02T10:25:30
|
310450838
|
{
"authors": [
"taquitos"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5848",
"repo": "fastlane/ci",
"url": "https://github.com/fastlane/ci/issues/499"
}
|
gharchive/issue
|
If the bot doesn't have push access, we crash. Maybe we should be friendly?
[2018-04-02 18:20:55] DEBUG GitRepo: Not setup yet, sleeping (time before timeout: 300.0) https://github.com/fastlane/ci
Thread terminated with exception: git '--git-dir=/Users/liebowitz/.fastlane/ci/fastlane-ci-config/.git' '--work-tree=/Users/liebowitz/.fastlane/ci/fastlane-ci-config' push 'origin' 'master' 2>&1:remote: Permission to fastlane/ci-config-heroku.git denied to fastlanebot.
fatal: unable to access 'https://github.com/fastlane/ci-config-heroku/': The requested URL returned error: 403
[2018-04-02 18:20:55] DEBUG GitRepo: Starting commit_changes! https://github.com/fastlane/ci-config-heroku for<EMAIL_ADDRESS>/Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:937:in command' /Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:742:in push'
/Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/base.rb:329:in push' /Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:396:in block in push'
/Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:320:in perform_block' /Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:391:in push'
/Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:384:in block in commit_changes!' /Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/bundler/gems/TaskQueue-5b3f459be5c4/lib/queue_worker.rb:82:in block in process'
[2018-04-02 18:20:55] DEBUG GitRepo: Using Clone User credentials with<EMAIL_ADDRESS>as author information on https://github.com/fastlane/ci-config-heroku
bundler: failed to load command: rackup (/Users/liebowitz/.rbenv/versions/2.3.3/bin/rackup)
Git::GitExecuteError: git '--git-dir=/Users/liebowitz/.fastlane/ci/fastlane-ci-config/.git' '--work-tree=/Users/liebowitz/.fastlane/ci/fastlane-ci-config' push 'origin' 'master' 2>&1:remote: Permission to fastlane/ci-config-heroku.git denied to fastlanebot.
fatal: unable to access 'https://github.com/fastlane/ci-config-heroku/': The requested URL returned error: 403
/Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:937:in command' /Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:742:in push'
/Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/base.rb:329:in push' /Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:396:in block in push'
/Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:320:in perform_block' /Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:391:in push'
/Users/liebowitz/dev/ci/app/shared/models/git_repo.rb:384:in block in commit_changes!' /Users/liebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/bundler/gems/TaskQueue-5b3f459be5c4/lib/queue_worker.rb:82:in block in process'
We actually now post a notification 🎉
|
2025-04-01T06:38:39.272558
| 2018-04-15T22:49:35
|
314459950
|
{
"authors": [
"minuscorp",
"taquitos"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5849",
"repo": "fastlane/ci",
"url": "https://github.com/fastlane/ci/issues/674"
}
|
gharchive/issue
|
Builds are failing due to missing dependencies that exist in gemfile
build http://mydoghatestechnology.com/projects_erb/32903571-271e-4c87-9b32-11df3c82d5aa/builds/461
failed because of a missing gem that is referenced. Locally, the build works fine. It also works fine on the build machine if I bundle install there in a terminal and run be fastlane rspec_me
So I think our Bundler environment isolation isn't working as expected, or something else is going on.
# Logfile created on 2018-04-15 15:45:55 -0700 by logger.rb/56438
[15:45:55]: Driving the lane 'rspec_me' 🚀
[15:45:55]: ----------------------------------
[15:45:55]: --- Step: cd ..;bundle install ---
[15:45:55]: ----------------------------------
[15:45:55]: $ cd ..;bundle install
[15:45:55]: ▸ Running `bundle install` with bundler 1.16.1
[15:45:55]: ▸ Found no changes, using resolution from the lockfile
[15:45:55]: ▸ Using rake 12.3.1
[15:45:55]: ▸ 0: rake (12.3.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rake-12.3.1.gemspec
[15:45:55]: ▸ Using CFPropertyList 3.0.0
[15:45:55]: ▸ 0: CFPropertyList (3.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/CFPropertyList-3.0.0.gemspec
[15:45:55]: ▸ Using abstract_type 0.0.7
[15:45:55]: ▸ 0: abstract_type (0.0.7) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/abstract_type-0.0.7.gemspec
[15:45:55]: ▸ Using ice_nine 0.11.2
[15:45:55]: ▸ 0: ice_nine (0.11.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/ice_nine-0.11.2.gemspec
[15:45:55]: ▸ Using thread_safe 0.3.6
[15:45:55]: ▸ 0: thread_safe (0.3.6) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/thread_safe-0.3.6.gemspec
[15:45:55]: ▸ Using memoizable 0.4.2
[15:45:55]: ▸ 0: memoizable (0.4.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/memoizable-0.4.2.gemspec
[15:45:55]: ▸ Using adamantium 0.2.0
[15:45:55]: ▸ 0: adamantium (0.2.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/adamantium-0.2.0.gemspec
[15:45:55]: ▸ Using public_suffix 2.0.5
[15:45:55]: ▸ 0: public_suffix (2.0.5) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/public_suffix-2.0.5.gemspec
[15:45:55]: ▸ Using addressable 2.5.2
[15:45:55]: ▸ 0: addressable (2.5.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/addressable-2.5.2.gemspec
[15:45:55]: ▸ Using ast 2.4.0
[15:45:55]: ▸ 0: ast (2.4.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/ast-2.4.0.gemspec
[15:45:55]: ▸ Using atomos 0.1.2
[15:45:55]: ▸ 0: atomos (0.1.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/atomos-0.1.2.gemspec
[15:45:55]: ▸ Using babosa 1.0.2
[15:45:55]: ▸ 0: babosa (1.0.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/babosa-1.0.2.gemspec
[15:45:55]: ▸ Using backports 3.11.1
[15:45:55]: ▸ 0: backports (3.11.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/backports-3.11.1.gemspec
[15:45:55]: ▸ Using bcrypt 3.1.11
[15:45:55]: ▸ 0: bcrypt (3.1.11) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/bcrypt-3.1.11.gemspec
[15:45:55]: ▸ Using bundler 1.16.1
[15:45:55]: ▸ 0: bundler (1.16.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/bundler-1.16.1.gemspec
[15:45:55]: ▸ Using byebug 10.0.2
[15:45:55]: ▸ 0: byebug (10.0.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/byebug-10.0.2.gemspec
[15:45:55]: ▸ Using claide 1.0.2
[15:45:55]: ▸ 0: claide (1.0.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/claide-1.0.2.gemspec
[15:45:55]: ▸ Using coderay 1.1.2
[15:45:55]: ▸ 0: coderay (1.1.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/coderay-1.1.2.gemspec
[15:45:55]: ▸ Using colored 1.2
[15:45:55]: ▸ 0: colored (1.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/colored-1.2.gemspec
[15:45:55]: ▸ Using colored2 3.1.2
[15:45:55]: ▸ 0: colored2 (3.1.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/colored2-3.1.2.gemspec
[15:45:55]: ▸ Using highline 1.7.10
[15:45:55]: ▸ 0: highline (1.7.10) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/highline-1.7.10.gemspec
[15:45:55]: ▸ Using commander-fastlane 4.4.6
[15:45:55]: ▸ 0: commander-fastlane (4.4.6) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/commander-fastlane-4.4.6.gemspec
[15:45:55]: ▸ Using equalizer 0.0.11
[15:45:55]: ▸ 0: equalizer (0.0.11) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/equalizer-0.0.11.gemspec
[15:45:55]: ▸ Using concord 0.1.5
[15:45:55]: ▸ 0: concord (0.1.5) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/concord-0.1.5.gemspec
[15:45:55]: ▸ Using json 2.1.0
[15:45:55]: ▸ 0: json (2.1.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/json-2.1.0.gemspec
[15:45:55]: ▸ Using docile 1.1.5
[15:45:55]: ▸ 0: docile (1.1.5) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/docile-1.1.5.gemspec
[15:45:55]: ▸ Using simplecov-html 0.10.2
[15:45:55]: ▸ 0: simplecov-html (0.10.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/simplecov-html-0.10.2.gemspec
[15:45:55]: ▸ Using simplecov 0.14.1
[15:45:55]: ▸ 0: simplecov (0.14.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/simplecov-0.14.1.gemspec
[15:45:55]: ▸ Using tins 1.16.3
[15:45:55]: ▸ 0: tins (1.16.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/tins-1.16.3.gemspec
[15:45:55]: ▸ Using term-ansicolor 1.6.0
[15:45:55]: ▸ 0: term-ansicolor (1.6.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/term-ansicolor-1.6.0.gemspec
[15:45:55]: ▸ Using thor 0.19.4
[15:45:55]: ▸ 0: thor (0.19.4) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/thor-0.19.4.gemspec
[15:45:55]: ▸ Using coveralls 0.8.21
[15:45:55]: ▸ 0: coveralls (0.8.21) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/coveralls-0.8.21.gemspec
[15:45:55]: ▸ Using daemons 1.2.6
[15:45:55]: ▸ 0: daemons (1.2.6) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/daemons-1.2.6.gemspec
[15:45:55]: ▸ Using declarative 0.0.10
[15:45:55]: ▸ 0: declarative (0.0.10) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/declarative-0.0.10.gemspec
[15:45:55]: ▸ Using declarative-option 0.1.0
[15:45:55]: ▸ 0: declarative-option (0.1.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/declarative-option-0.1.0.gemspec
[15:45:55]: ▸ Using diff-lcs 1.3
[15:45:55]: ▸ 0: diff-lcs (1.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/diff-lcs-1.3.gemspec
[15:45:55]: ▸ Using digest-crc 0.4.1
[15:45:55]: ▸ 0: digest-crc (0.4.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/digest-crc-0.4.1.gemspec
[15:45:55]: ▸ Using unf_ext <IP_ADDRESS>
[15:45:55]: ▸ 0: unf_ext (<IP_ADDRESS>) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/unf_ext-<IP_ADDRESS>.gemspec
[15:45:55]: ▸ Using unf 0.1.4
[15:45:55]: ▸ 0: unf (0.1.4) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/unf-0.1.4.gemspec
[15:45:55]: ▸ Using domain_name 0.5.20170404
[15:45:55]: ▸ 0: domain_name (0.5.20170404) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/domain_name-0.5.20170404.gemspec
[15:45:55]: ▸ Using dotenv 2.2.1
[15:45:55]: ▸ 0: dotenv (2.2.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/dotenv-2.2.1.gemspec
[15:45:55]: ▸ Using equatable 0.5.0
[15:45:55]: ▸ 0: equatable (0.5.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/equatable-0.5.0.gemspec
[15:45:55]: ▸ Using tzinfo 1.2.5
[15:45:55]: ▸ 0: tzinfo (1.2.5) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/tzinfo-1.2.5.gemspec
[15:45:55]: ▸ Using et-orbi 1.1.0
[15:45:55]: ▸ 0: et-orbi (1.1.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/et-orbi-1.1.0.gemspec
[15:45:55]: ▸ Using eventmachine 1.2.5
[15:45:55]: ▸ 0: eventmachine (1.2.5) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/eventmachine-1.2.5.gemspec
[15:45:55]: ▸ Using excon 0.62.0
[15:45:55]: ▸ 0: excon (0.62.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/excon-0.62.0.gemspec
[15:45:55]: ▸ Using multipart-post 2.0.0
[15:45:55]: ▸ 0: multipart-post (2.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/multipart-post-2.0.0.gemspec
[15:45:55]: ▸ Using faraday 0.14.0
[15:45:55]: ▸ 0: faraday (0.14.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/faraday-0.14.0.gemspec
[15:45:55]: ▸ Using http-cookie 1.0.3
[15:45:55]: ▸ 0: http-cookie (1.0.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/http-cookie-1.0.3.gemspec
[15:45:55]: ▸ Using faraday-cookie_jar 0.0.6
[15:45:55]: ▸ 0: faraday-cookie_jar (0.0.6) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/faraday-cookie_jar-0.0.6.gemspec
[15:45:55]: ▸ Using faraday-http-cache 2.0.0
[15:45:55]: ▸ 0: faraday-http-cache (2.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/faraday-http-cache-2.0.0.gemspec
[15:45:55]: ▸ Using faraday_middleware 0.12.2
[15:45:55]: ▸ 0: faraday_middleware (0.12.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/faraday_middleware-0.12.2.gemspec
[15:45:55]: ▸ Using parser <IP_ADDRESS>
[15:45:55]: ▸ 0: parser (<IP_ADDRESS>) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/parser-<IP_ADDRESS>.gemspec
[15:45:55]: ▸ Using procto 0.0.3
[15:45:55]: ▸ 0: procto (0.0.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/procto-0.0.3.gemspec
[15:45:55]: ▸ Using unparser 0.2.7
[15:45:55]: ▸ 0: unparser (0.2.7) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/unparser-0.2.7.gemspec
[15:45:55]: ▸ Using fastfile-parser 0.0.0 from https://github.com/fastlane/fastfile-parser (at master@a9707d8)
[15:45:55]: ▸ 0: fastfile-parser (0.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/bundler/gems/fastfile-parser-a9707d87eb6b/fastfile-parser.gemspec
[15:45:55]: ▸ Using fastimage 2.1.1
[15:45:55]: ▸ 0: fastimage (2.1.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/fastimage-2.1.1.gemspec
[15:45:55]: ▸ Using gh_inspector 1.1.3
[15:45:55]: ▸ 0: gh_inspector (1.1.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/gh_inspector-1.1.3.gemspec
[15:45:55]: ▸ Using jwt 2.1.0
[15:45:55]: ▸ 0: jwt (2.1.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/jwt-2.1.0.gemspec
[15:45:55]: ▸ Using little-plugger 1.1.4
[15:45:55]: ▸ 0: little-plugger (1.1.4) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/little-plugger-1.1.4.gemspec
[15:45:55]: ▸ Using multi_json 1.13.1
[15:45:55]: ▸ 0: multi_json (1.13.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/multi_json-1.13.1.gemspec
[15:45:55]: ▸ Using logging 2.2.2
[15:45:55]: ▸ 0: logging (2.2.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/logging-2.2.2.gemspec
[15:45:55]: ▸ Using memoist 0.16.0
[15:45:55]: ▸ 0: memoist (0.16.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/memoist-0.16.0.gemspec
[15:45:55]: ▸ Using os 0.9.6
[15:45:55]: ▸ 0: os (0.9.6) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/os-0.9.6.gemspec
[15:45:55]: ▸ Using signet 0.8.1
[15:45:55]: ▸ 0: signet (0.8.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/signet-0.8.1.gemspec
[15:45:55]: ▸ Using googleauth 0.6.2
[15:45:55]: ▸ 0: googleauth (0.6.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/googleauth-0.6.2.gemspec
[15:45:55]: ▸ Using httpclient 2.8.3
[15:45:55]: ▸ 0: httpclient (2.8.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/httpclient-2.8.3.gemspec
[15:45:55]: ▸ Using mime-types-data 3.2016.0521
[15:45:55]: ▸ 0: mime-types-data (3.2016.0521) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/mime-types-data-3.2016.0521.gemspec
[15:45:55]: ▸ Using mime-types 3.1
[15:45:55]: ▸ 0: mime-types (3.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/mime-types-3.1.gemspec
[15:45:55]: ▸ Using uber 0.1.0
[15:45:55]: ▸ 0: uber (0.1.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/uber-0.1.0.gemspec
[15:45:55]: ▸ Using representable 3.0.4
[15:45:55]: ▸ 0: representable (3.0.4) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/representable-3.0.4.gemspec
[15:45:55]: ▸ Using retriable 3.1.1
[15:45:55]: ▸ 0: retriable (3.1.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/retriable-3.1.1.gemspec
[15:45:55]: ▸ Using google-api-client 0.13.6
[15:45:55]: ▸ 0: google-api-client (0.13.6) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/google-api-client-0.13.6.gemspec
[15:45:55]: ▸ Using mini_magick 4.5.1
[15:45:55]: ▸ 0: mini_magick (4.5.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/mini_magick-4.5.1.gemspec
[15:45:55]: ▸ Using multi_xml 0.6.0
[15:45:55]: ▸ 0: multi_xml (0.6.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/multi_xml-0.6.0.gemspec
[15:45:55]: ▸ Using plist 3.4.0
[15:45:55]: ▸ 0: plist (3.4.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/plist-3.4.0.gemspec
[15:45:55]: ▸ Using rubyzip 1.2.1
[15:45:55]: ▸ 0: rubyzip (1.2.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rubyzip-1.2.1.gemspec
[15:45:56]: ▸ Using security 0.1.3
[15:45:56]: ▸ 0: security (0.1.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/security-0.1.3.gemspec
[15:45:56]: ▸ Using naturally 2.1.0
[15:45:56]: ▸ 0: naturally (2.1.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/naturally-2.1.0.gemspec
[15:45:56]: ▸ Using simctl 1.6.3
[15:45:56]: ▸ 0: simctl (1.6.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/simctl-1.6.3.gemspec
[15:45:56]: ▸ Using slack-notifier 2.3.2
[15:45:56]: ▸ 0: slack-notifier (2.3.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/slack-notifier-2.3.2.gemspec
[15:45:56]: ▸ Using terminal-notifier 1.8.0
[15:45:56]: ▸ 0: terminal-notifier (1.8.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/terminal-notifier-1.8.0.gemspec
[15:45:56]: ▸ Using unicode-display_width 1.3.0
[15:45:56]: ▸ 0: unicode-display_width (1.3.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/unicode-display_width-1.3.0.gemspec
[15:45:56]: ▸ Using terminal-table 1.8.0
[15:45:56]: ▸ 0: terminal-table (1.8.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/terminal-table-1.8.0.gemspec
[15:45:56]: ▸ Using tty-screen 0.6.4
[15:45:56]: ▸ 0: tty-screen (0.6.4) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/tty-screen-0.6.4.gemspec
[15:45:56]: ▸ Using tty-cursor 0.5.0
[15:45:56]: ▸ 0: tty-cursor (0.5.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/tty-cursor-0.5.0.gemspec
[15:45:56]: ▸ Using tty-spinner 0.8.0
[15:45:56]: ▸ 0: tty-spinner (0.8.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/tty-spinner-0.8.0.gemspec
[15:45:56]: ▸ Using word_wrap 1.0.0
[15:45:56]: ▸ 0: word_wrap (1.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/word_wrap-1.0.0.gemspec
[15:45:56]: ▸ Using nanaimo 0.2.5
[15:45:56]: ▸ 0: nanaimo (0.2.5) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/nanaimo-0.2.5.gemspec
[15:45:56]: ▸ Using xcodeproj 1.5.7
[15:45:56]: ▸ 0: xcodeproj (1.5.7) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/xcodeproj-1.5.7.gemspec
[15:45:56]: ▸ Using rouge 2.0.7
[15:45:56]: ▸ 0: rouge (2.0.7) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rouge-2.0.7.gemspec
[15:45:56]: ▸ Using xcpretty 0.2.8
[15:45:56]: ▸ 0: xcpretty (0.2.8) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/xcpretty-0.2.8.gemspec
[15:45:56]: ▸ Using xcpretty-travis-formatter 1.0.0
[15:45:56]: ▸ 0: xcpretty-travis-formatter (1.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/xcpretty-travis-formatter-1.0.0.gemspec
[15:45:56]: ▸ Using fastlane 2.89.0 from https://github.com/fastlane/fastlane (at master@c579921)
[15:45:56]: ▸ 0: fastlane (2.89.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/bundler/gems/fastlane-c579921dcf7a/fastlane.gemspec
[15:45:56]: ▸ Using websocket-extensions 0.1.3
[15:45:56]: ▸ 0: websocket-extensions (0.1.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/websocket-extensions-0.1.3.gemspec
[15:45:56]: ▸ Using websocket-driver 0.7.0
[15:45:56]: ▸ 0: websocket-driver (0.7.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/websocket-driver-0.7.0.gemspec
[15:45:56]: ▸ Using faye-websocket 0.10.7
[15:45:56]: ▸ 0: faye-websocket (0.10.7) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/faye-websocket-0.10.7.gemspec
[15:45:56]: ▸ Using git 1.3.0
[15:45:56]: ▸ 0: git (1.3.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/git-1.3.0.gemspec
[15:45:56]: ▸ Using google-cloud-env 1.0.1
[15:45:56]: ▸ 0: google-cloud-env (1.0.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/google-cloud-env-1.0.1.gemspec
[15:45:56]: ▸ Using google-cloud-core 1.2.0
[15:45:56]: ▸ 0: google-cloud-core (1.2.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/google-cloud-core-1.2.0.gemspec
[15:45:56]: ▸ Using google-cloud-storage 1.5.0
[15:45:56]: ▸ 0: google-cloud-storage (1.5.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/google-cloud-storage-1.5.0.gemspec
[15:45:56]: ▸ Using method_source 0.9.0
[15:45:56]: ▸ 0: method_source (0.9.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/method_source-0.9.0.gemspec
[15:45:56]: ▸ Using mustermann 1.0.2
[15:45:56]: ▸ 0: mustermann (1.0.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/mustermann-1.0.2.gemspec
[15:45:56]: ▸ Using sawyer 0.8.1
[15:45:56]: ▸ 0: sawyer (0.8.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/sawyer-0.8.1.gemspec
[15:45:56]: ▸ Using octokit 4.8.0
[15:45:56]: ▸ 0: octokit (4.8.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/octokit-4.8.0.gemspec
[15:45:56]: ▸ Using parallel 1.12.1
[15:45:56]: ▸ 0: parallel (1.12.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/parallel-1.12.1.gemspec
[15:45:56]: ▸ Using tty-color 0.4.2
[15:45:56]: ▸ 0: tty-color (0.4.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/tty-color-0.4.2.gemspec
[15:45:56]: ▸ Using pastel 0.7.2
[15:45:56]: ▸ 0: pastel (0.7.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/pastel-0.7.2.gemspec
[15:45:56]: ▸ Using powerpack 0.1.1
[15:45:56]: ▸ 0: powerpack (0.1.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/powerpack-0.1.1.gemspec
[15:45:56]: ▸ Using pry 0.11.3
[15:45:56]: ▸ 0: pry (0.11.3) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/pry-0.11.3.gemspec
[15:45:56]: ▸ Using pry-byebug 3.6.0
[15:45:56]: ▸ 0: pry-byebug (3.6.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/pry-byebug-3.6.0.gemspec
[15:45:56]: ▸ Using rack 2.0.4
[15:45:56]: ▸ 0: rack (2.0.4) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rack-2.0.4.gemspec
[15:45:56]: ▸ Using rack-protection 2.0.1
[15:45:56]: ▸ 0: rack-protection (2.0.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rack-protection-2.0.1.gemspec
[15:45:56]: ▸ Using rack-test 1.0.0
[15:45:56]: ▸ 0: rack-test (1.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rack-test-1.0.0.gemspec
[15:45:56]: ▸ Using rainbow 3.0.0
[15:45:56]: ▸ 0: rainbow (3.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rainbow-3.0.0.gemspec
[15:45:56]: ▸ Using rspec-support 3.7.1
[15:45:56]: ▸ 0: rspec-support (3.7.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rspec-support-3.7.1.gemspec
[15:45:56]: ▸ Using rspec-core 3.7.1
[15:45:56]: ▸ 0: rspec-core (3.7.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rspec-core-3.7.1.gemspec
[15:45:56]: ▸ Using rspec-expectations 3.7.0
[15:45:56]: ▸ 0: rspec-expectations (3.7.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rspec-expectations-3.7.0.gemspec
[15:45:56]: ▸ Using rspec-mocks 3.7.0
[15:45:56]: ▸ 0: rspec-mocks (3.7.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rspec-mocks-3.7.0.gemspec
[15:45:56]: ▸ Using rspec 3.7.0
[15:45:56]: ▸ 0: rspec (3.7.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rspec-3.7.0.gemspec
[15:45:56]: ▸ Using ruby-progressbar 1.9.0
[15:45:56]: ▸ 0: ruby-progressbar (1.9.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/ruby-progressbar-1.9.0.gemspec
[15:45:56]: ▸ Using rubocop 0.52.1
[15:45:56]: ▸ 0: rubocop (0.52.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rubocop-0.52.1.gemspec
[15:45:56]: ▸ Using rufus-scheduler 3.4.2
[15:45:56]: ▸ 0: rufus-scheduler (3.4.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/rufus-scheduler-3.4.2.gemspec
[15:45:56]: ▸ Using tilt 2.0.8
[15:45:56]: ▸ 0: tilt (2.0.8) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/tilt-2.0.8.gemspec
[15:45:56]: ▸ Using sinatra 2.0.1
[15:45:56]: ▸ 0: sinatra (2.0.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/sinatra-2.0.1.gemspec
[15:45:56]: ▸ Using sinatra-contrib 2.0.1
[15:45:56]: ▸ 0: sinatra-contrib (2.0.1) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/sinatra-contrib-2.0.1.gemspec
[15:45:56]: ▸ Using taskqueue 0.0.0 from https://github.com/fastlane/TaskQueue (at master@5b3f459)
[15:45:56]: ▸ 0: taskqueue (0.0.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/bundler/gems/TaskQueue-5b3f459be5c4/taskqueue.gemspec
[15:45:56]: ▸ Using thin 1.7.2
[15:45:56]: ▸ 0: thin (1.7.2) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/thin-1.7.2.gemspec
[15:45:56]: ▸ Using tty-command 0.7.0
[15:45:56]: ▸ 0: tty-command (0.7.0) from /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/specifications/tty-command-0.7.0.gemspec
[15:45:56]: ▸ Bundle complete! 23 Gemfile dependencies, 129 gems now installed.
[15:45:56]: ▸ Use `bundle info [gemname]` to see where a bundled gem is installed.
[15:45:56]: -------------------------------------
[15:45:56]: --- Step: cd ..;bundle exec rspec ---
[15:45:56]: -------------------------------------
[15:45:56]: $ cd ..;bundle exec rspec
[15:45:57]: ▸ warning: parser/current is loading parser/ruby23, which recognizes
[15:45:57]: ▸ warning: 2.3.5-compliant syntax, but you are running 2.3.3.
[15:45:57]: ▸ warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
[15:45:57]: ▸ [Coveralls] Set up the SimpleCov formatter.
[15:45:57]: ▸ [Coveralls] Using SimpleCov's default settings.
[15:45:59]: ▸ An error occurred while loading ./spec/dashboard_controller_spec.rb.
[15:45:59]: ▸ Failure/Error: require [1;31m"sinatra/flash[1;31m"
[15:45:59]: ▸
[15:45:59]: ▸ LoadError:
[15:45:59]: ▸ cannot load such file -- sinatra/flash
[15:45:59]: ▸ # ./app/shared/controller_base.rb:4:in `require'
[15:45:59]: ▸ # ./app/shared/controller_base.rb:4:in `'
[15:45:59]: ▸ # ./app/shared/authenticated_controller_base.rb:2:in `require_relative'
[15:45:59]: ▸ # ./app/shared/authenticated_controller_base.rb:2:in `'
[15:45:59]: ▸ # ./app/features/dashboard/dashboard_controller.rb:1:in `require_relative'
[15:45:59]: ▸ # ./app/features/dashboard/dashboard_controller.rb:1:in `'
[15:45:59]: ▸ # ./spec/dashboard_controller_spec.rb:2:in `require'
[15:45:59]: ▸ # ./spec/dashboard_controller_spec.rb:2:in `'
[15:45:59]: ▸ An error occurred while loading ./spec/notification_controller_spec.rb.
[15:45:59]: ▸ Failure/Error: require [1;31m"sinatra/flash[1;31m"
[15:45:59]: ▸
[15:45:59]: ▸ LoadError:
[15:45:59]: ▸ cannot load such file -- sinatra/flash
[15:45:59]: ▸ # ./app/shared/controller_base.rb:4:in `require'
[15:45:59]: ▸ # ./app/shared/controller_base.rb:4:in `'
[15:45:59]: ▸ # ./app/shared/authenticated_controller_base.rb:2:in `require_relative'
[15:45:59]: ▸ # ./app/shared/authenticated_controller_base.rb:2:in `'
[15:45:59]: ▸ # ./app/features/notifications/notifications_controller.rb:1:in `require_relative'
[15:45:59]: ▸ # ./app/features/notifications/notifications_controller.rb:1:in `'
[15:45:59]: ▸ # ./spec/notification_controller_spec.rb:2:in `require'
[15:45:59]: ▸ # ./spec/notification_controller_spec.rb:2:in `'
[15:45:59]: ▸ Finished in 0.0004 seconds (files took 2.9 seconds to load)
[15:45:59]: ▸ 0 examples, 0 failures, 2 errors occurred outside of examples
[15:45:59]: ▸ [Coveralls] Submitting to https://coveralls.io/api/v1
[15:46:00]: ▸ [Coveralls] Job #461.1
[15:46:00]: ▸ [Coveralls] [4mhttps://coveralls.io/jobs/35630153
[15:46:00]: ▸ Coverage is at 37.33%.
[15:46:00]: ▸ Coverage report sent to Coveralls.
[15:46:01]: Lane Context:
[15:46:01]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"rspec_me"}
[15:46:01]: Exit status of command 'cd ..;bundle exec rspec' was 1 instead of 0.
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.5-compliant syntax, but you are running 2.3.3.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
[Coveralls] Set up the SimpleCov formatter.
[Coveralls] Using SimpleCov's default settings.
An error occurred while loading ./spec/dashboard_controller_spec.rb.
Failure/Error: require [1;31m"sinatra/flash[1;31m"
LoadError:
cannot load such file -- sinatra/flash
# ./app/shared/controller_base.rb:4:in `require'
# ./app/shared/controller_base.rb:4:in `'
# ./app/shared/authenticated_controller_base.rb:2:in `require_relative'
# ./app/shared/authenticated_controller_base.rb:2:in `'
# ./app/features/dashboard/dashboard_controller.rb:1:in `require_relative'
# ./app/features/dashboard/dashboard_controller.rb:1:in `'
# ./spec/dashboard_controller_spec.rb:2:in `require'
# ./spec/dashboard_controller_spec.rb:2:in `'
An error occurred while loading ./spec/notification_controller_spec.rb.
Failure/Error: require [1;31m"sinatra/flash[1;31m"
LoadError:
cannot load such file -- sinatra/flash
# ./app/shared/controller_base.rb:4:in `require'
# ./app/shared/controller_base.rb:4:in `'
# ./app/shared/authenticated_controller_base.rb:2:in `require_relative'
# ./app/shared/authenticated_controller_base.rb:2:in `'
# ./app/features/notifications/notifications_controller.rb:1:in `require_relative'
# ./app/features/notifications/notifications_controller.rb:1:in `'
# ./spec/notification_controller_spec.rb:2:in `require'
# ./spec/notification_controller_spec.rb:2:in `'
Finished in 0.0004 seconds (files took 2.9 seconds to load)
0 examples, 0 failures, 2 errors occurred outside of examples
[Coveralls] Submitting to https://coveralls.io/api/v1
[Coveralls] Job #461.1
[Coveralls] [4mhttps://coveralls.io/jobs/35630153
Coverage is at 37.33%.
Coverage report sent to Coveralls.
[15:46:01]: fastlane finished with errors
[15:46:01]: Exit status of command 'cd ..;bundle exec rspec' was 1 instead of 0.
warning: parser/current is loading parser/ruby23, which recognizes
warning: 2.3.5-compliant syntax, but you are running 2.3.3.
warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
[Coveralls] Set up the SimpleCov formatter.
[Coveralls] Using SimpleCov's default settings.
An error occurred while loading ./spec/dashboard_controller_spec.rb.
Failure/Error: require [1;31m"sinatra/flash[1;31m"
LoadError:
cannot load such file -- sinatra/flash
# ./app/shared/controller_base.rb:4:in `require'
# ./app/shared/controller_base.rb:4:in `'
# ./app/shared/authenticated_controller_base.rb:2:in `require_relative'
# ./app/shared/authenticated_controller_base.rb:2:in `'
# ./app/features/dashboard/dashboard_controller.rb:1:in `require_relative'
# ./app/features/dashboard/dashboard_controller.rb:1:in `'
# ./spec/dashboard_controller_spec.rb:2:in `require'
# ./spec/dashboard_controller_spec.rb:2:in `'
An error occurred while loading ./spec/notification_controller_spec.rb.
Failure/Error: require [1;31m"sinatra/flash[1;31m"
LoadError:
cannot load such file -- sinatra/flash
# ./app/shared/controller_base.rb:4:in `require'
# ./app/shared/controller_base.rb:4:in `'
# ./app/shared/authenticated_controller_base.rb:2:in `require_relative'
# ./app/shared/authenticated_controller_base.rb:2:in `'
# ./app/features/notifications/notifications_controller.rb:1:in `require_relative'
# ./app/features/notifications/notifications_controller.rb:1:in `'
# ./spec/notification_controller_spec.rb:2:in `require'
# ./spec/notification_controller_spec.rb:2:in `'
Finished in 0.0004 seconds (files took 2.9 seconds to load)
0 examples, 0 failures, 2 errors occurred outside of examples
[Coveralls] Submitting to https://coveralls.io/api/v1
[Coveralls] Job #461.1
[Coveralls] [4mhttps://coveralls.io/jobs/35630153
Coverage is at 37.33%.
Coverage report sent to Coveralls.
As I made the PR with the Bundler isolation, I'm trying to trace the issue here.
|
2025-04-01T06:38:39.279284
| 2019-04-18T13:23:25
|
434768570
|
{
"authors": [
"UPCman",
"jakubpetrik",
"janpio"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5850",
"repo": "fastlane/fastlane",
"url": "https://github.com/fastlane/fastlane/issues/14621"
}
|
gharchive/issue
|
latest_testflight_build_number returns always 0
Using this code on Fastfile:
build_number = latest_testflight_build_number(
version: 2.3.1,
team_id: XXXXXXX,
initial_build_number: 0
)
Always I get build number 0.
[14:32:08]: --------------------------------------------
[14:32:08]: --- Step: latest_testflight_build_number ---
[14:32:08]: --------------------------------------------
[14:32:09]: Login to App Store Connect XXXXXXXXXXXXXX
[14:32:11]: Login successful
[14:32:12]: Fetching the latest build number for version 2.3.1
[14:32:13]: Latest upload for version 2.3.1 is build: 0
I'm using version 2.119.0 of Fastlane.
With the same code, it worked until a few weeks ago. Since then it always fails with the same result.
The result is the same with or without any active builds numbers on Testflight.
Checklist
[x] I read the similar issues. Closed as solved, but i have not exactly the same issue.
[x] Change the version number.
[x] Try on another project with the same Fastfile.
Please upgrade to the latest version of fastlane and report if you still have issues. The Testflight stuff was greatly rewritten there because Apple changed a lot on their side, so it is expected that you have to use fastlane 2.120.0.
Hey @UPCman, could you please check if this problem still exists with a current release of fastlane? We tried to fix a lot of these "error 410 gone" errors, and now need your feedback if this covered yours as well. Thanks!
I update my fastlane to v2.120.0 and the issue is solved.
Thanks!!
@janpio happening also on 2.121.1
Awesome 🥇 All credit goes to @joshdholtz who did a great job fixing this mess.
|
2025-04-01T06:38:39.327629
| 2019-10-16T02:30:24
|
507575764
|
{
"authors": [
"AlexParfenjuk",
"Peretz30",
"derpoliuk",
"drayan85",
"fromkk",
"gkhloptov",
"herald25santos",
"janpio",
"joshdholtz",
"michzio",
"timMorrill"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5851",
"repo": "fastlane/fastlane",
"url": "https://github.com/fastlane/fastlane/issues/15506"
}
|
gharchive/issue
|
firebase_app_distribution plugin doesn't work in macOS Catalina
New Issue Checklist
[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues
Issue Description
I'd like to try to use firebase_app_distribution plugin with Fastlane.
So I executed fastlane add_plugin firebase_app_distribution and use with fastlane firebase_app_distribution command.
But, failed with error.
Command executed
fastlane add_plugin firebase_app_distribution
[✔] 🚀
[11:11:34]: fastlane detected a Gemfile in the current directory
[11:11:34]: however it seems like you don't use `bundle exec`
[11:11:34]: to launch fastlane faster, please use
[11:11:34]:
[11:11:34]: $ bundle exec fastlane add_plugin firebase_app_distribution
[11:11:34]:
[11:11:34]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[11:11:35]: Plugin 'fastlane-plugin-firebase_app_distribution' was added to './fastlane/Pluginfile'
[11:11:35]: Make sure to commit your Gemfile, Gemfile.lock and Pluginfile to version control
Installing plugin dependencies...
Successfully installed plugins
Complete output when running fastlane, including the stack trace and command used
fastlane firebase_app_distribution
[✔] 🚀
[11:12:46]: fastlane detected a Gemfile in the current directory
[11:12:46]: however it seems like you don't use `bundle exec`
[11:12:46]: to launch fastlane faster, please use
[11:12:46]:
[11:12:46]: $ bundle exec fastlane firebase_app_distribution
[11:12:46]:
[11:12:46]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[11:12:47]: Error loading plugin 'fastlane-plugin-firebase_app_distribution': cannot load such file -- fastlane/plugin/firebase_app_distribution
[11:12:47]: It seems like you wanted to load some plugins, however they couldn't be loaded
[11:12:47]: Please follow the troubleshooting guide: https://docs.fastlane.tools/plugins/plugins-troubleshooting/
+-------------------------------------------+-----------+------------------+
| Used plugins |
+-------------------------------------------+-----------+------------------+
| Plugin | Version | Action |
+-------------------------------------------+-----------+------------------+
| fastlane-plugin-firebase_app_distribution | undefined | No actions found |
+-------------------------------------------+-----------+------------------+
[11:12:47]: ----------------------------------------
[11:12:47]: --- Step: Verifying fastlane version ---
[11:12:47]: ----------------------------------------
[11:12:47]: Your fastlane version 2.134.0 matches the minimum requirement of 2.119.0 ✅
[11:12:47]: ------------------------------
[11:12:47]: --- Step: default_platform ---
[11:12:47]: ------------------------------
+------------------+-----+
| Lane Context |
+------------------+-----+
| DEFAULT_PLATFORM | ios |
+------------------+-----+
[11:12:47]: Could not find lane 'ios firebase_app_distribution'. Available lanes: ios version, ios deploy, ios test, ios beta, ios release, ios dsyms
+------+----------------------------+-------------+
| fastlane summary |
+------+----------------------------+-------------+
| Step | Action | Time (in s) |
+------+----------------------------+-------------+
| 1 | Verifying fastlane version | 0 |
| 2 | default_platform | 0 |
+------+----------------------------+-------------+
Looking for related GitHub issues on fastlane/fastlane...
➡️ Malformed version number string undefined
https://github.com/fastlane/fastlane/issues/14663 [closed] 1 💬
23 Jun 2019
➡️ Sign in with the app-specific password you generated
https://github.com/fastlane/fastlane/issues/7380 [closed] 5 💬
22 Aug 2017
🔗 You can ⌘ + double-click on links to open them directly in your browser.
Traceback (most recent call last):
20: from /usr/local/bin/fastlane:23:in `'
19: from /usr/local/bin/fastlane:23:in `load'
18: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/bin/fastlane:23:in `'
17: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
16: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
15: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/commands_generator.rb:349:in `run'
14: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
12: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
11: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
10: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/lane_manager.rb:76:in `cruise_lane'
6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/lane_manager_base.rb:20:in `finish_fastlane'
5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:26:in `show_update_status'
4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:26:in `each'
3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:29:in `block in show_update_status'
2: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:203:in `new'
1: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:203:in `new'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:212:in `initialize': Malformed version number string undefined (ArgumentError)
20: from /usr/local/bin/fastlane:23:in `'
19: from /usr/local/bin/fastlane:23:in `load'
18: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/bin/fastlane:23:in `'
17: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
16: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
15: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/commands_generator.rb:349:in `run'
14: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
12: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
11: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
10: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/lane_manager.rb:76:in `cruise_lane'
6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/lane_manager_base.rb:20:in `finish_fastlane'
5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:26:in `show_update_status'
4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:26:in `each'
3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:29:in `block in show_update_status'
2: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:203:in `new'
1: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:203:in `new'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:212:in `initialize': [!] Malformed version number string undefined (ArgumentError)
11: from /usr/local/bin/fastlane:23:in `'
10: from /usr/local/bin/fastlane:23:in `load'
9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/bin/fastlane:23:in `'
8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/commands_generator.rb:53:in `start'
6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/commands_generator.rb:43:in `ensure in start'
5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:26:in `show_update_status'
4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:26:in `each'
3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.134.0/fastlane/lib/fastlane/plugins/plugin_update_manager.rb:29:in `block in show_update_status'
2: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:203:in `new'
1: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:203:in `new'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/version.rb:212:in `initialize': Malformed version number string undefined (ArgumentError)
Environment
🚫 fastlane environment 🚫
Stack
Key
Value
OS
10.15
Ruby
2.6.3
Bundler?
false
Git
git version 2.21.0
Installation Source
/usr/local/bin/fastlane
Host
Mac OS X 10.15 (19A583)
Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib
OpenSSL Version
LibreSSL 2.8.3
Is contained
false
Is homebrew
false
Is installed via Fabric.app
false
Xcode Path
/Applications/Xcode.app/Contents/Developer/
Xcode Version
11.0
System Locale
Error
No Locale with UTF8 found 🚫
fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command
# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`
# If you want to automatically update fastlane if a new version is available:
# update_fastlane
# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.119.0"
appVersion = "3.0.0"
xcodeproj = "Type.xcodeproj"
buildNumber = `git log --oneline | wc -l`.strip
default_platform :ios
platform :ios do
before_all do
# ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
#cocoapods
#carthage
end
lane :version do |options|
version_number = options[:version] || appVersion
increment_version_number(version_number: version_number, xcodeproj: xcodeproj)
increment_build_number(build_number: buildNumber, xcodeproj: xcodeproj)
end
lane :deploy do |options|
commit_message = `git log --format=%B -n 1 HEAD`.strip
ipa_path = options[:ipa_path]
app_id = options[:app_id] || "1:22804013810:ios:ee16d150e1ffecd2"
groups = options[:groups] || "開発者"
firebase_cli_path = options[:firebase_cli_path] || "/usr/local/lib/node_modules/firebase-tools/lib/bin/firebase.js"
firebase_app_distribution(
app: app_id,
groups: groups,
release_notes: commit_message,
ipa_path: ipa_path,
firebase_cli_path: firebase_cli_path
)
end
desc "Runs all the tests"
lane :test do
scan
end
desc "Submit a new Beta Build to Apple TestFlight"
desc "This will also make sure the profile is up to date"
lane :beta do
# match(type: "appstore") # more information: https://codesigning.guide
gym(scheme: "Type") # Build your app - more options available
pilot
# sh "your_script.sh"
# You can also use other beta testing services here (run `fastlane actions`)
end
desc "Deploy a new version to the App Store"
lane :release do
# match(type: "appstore")
# snapshot
# gym(scheme: "Type") # Build your app - more options available
deliver(force: true)
# frameit
end
lane :dsyms do |options|
version_number = options[:version] || get_info_plist_value(path: 'Type/Info.plist', key: "CFBundleShortVersionString")
app_identifier = "me.fromkk.Type"
download_dsyms(
version: version_number,
app_identifier: app_identifier
)
upload_symbols_to_crashlytics(
gsp_path: "Type/Resources/GoogleService-Info.plist"
)
clean_build_artifacts
end
# You can define as many lanes as you want
after_all do |lane|
# This block is called, only if the executed lane was successful
# slack(
# message: "Successfully deployed new App Update."
# )
end
error do |lane, exception|
# slack(
# message: exception.message,
# success: false
# )
end
end
# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions
# fastlane reports which actions are used. No personal data is recorded.
# Learn more at https://github.com/fastlane/fastlane#metrics
`./fastlane/Appfile`
app_identifier "me.fromkk.Type" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address
team_id "K84E4S7G4C" # Developer Portal Team ID
# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md
fastlane gems
Gem
Version
Update-Status
fastlane
2.134.0
✅ Up-To-Date
Loaded fastlane plugins:
Plugin
Version
Update-Status
fastlane-plugin-badge
1.3.0
✅ Up-To-Date
Loaded gems
Gem
Version
did_you_mean
1.3.0
slack-notifier
2.3.2
atomos
0.1.3
claide
1.0.3
colored2
3.1.2
nanaimo
0.2.6
xcodeproj
1.12.0
rouge
2.0.7
xcpretty
0.3.0
terminal-notifier
2.0.0
unicode-display_width
1.6.0
terminal-table
1.8.0
plist
3.5.0
public_suffix
2.0.5
addressable
2.7.0
multipart-post
2.0.0
word_wrap
1.0.0
tty-screen
0.7.0
tty-cursor
0.7.0
tty-spinner
0.9.1
babosa
1.0.3
colored
1.2
highline
1.7.10
commander-fastlane
4.4.6
excon
0.67.0
unf_ext
<IP_ADDRESS>
unf
0.1.4
domain_name
0.5.20190701
http-cookie
1.0.3
faraday-cookie_jar
0.0.6
faraday
0.17.0
faraday_middleware
0.13.1
fastimage
2.1.7
gh_inspector
1.1.3
mini_magick
4.9.5
multi_xml
0.6.0
rubyzip
1.3.0
security
0.1.3
xcpretty-travis-formatter
1.0.0
dotenv
2.7.5
bundler
2.0.2
naturally
2.2.0
simctl
1.6.6
jwt
2.1.0
uber
0.1.0
declarative
0.0.10
declarative-option
0.1.0
representable
3.0.4
retriable
3.1.2
mime-types
3.3
memoist
0.16.0
os
1.0.1
googleauth
0.6.7
httpclient
2.8.3
google-api-client
0.23.9
digest-crc
0.4.1
google-cloud-storage
1.16.0
emoji_regex
1.0.1
CFPropertyList
3.0.1
json
2.2.0
mime-types-data
3.2019.1009
multi_json
1.14.1
signet
0.12.0
google-cloud-env
1.2.1
google-cloud-core
1.3.2
forwardable
1.2.0
logger
1.3.0
stringio
0.0.2
ipaddr
1.2.2
openssl
2.1.2
ostruct
0.1.0
strscan
1.0.0
date
2.0.0
fileutils
1.1.0
etc
1.0.1
io-console
0.4.7
zlib
1.0.0
libxml-ruby
3.1.0
rexml
3.1.9
psych
3.1.0
mutex_m
0.1.0
curb
0.9.10
badge
0.11.0
fastlane-plugin-badge
1.3.0
generated on: 2019-10-16
I've faced with identical issue on Ubuntu 18.04.1. Plugin installed, but can't be loaded.
Looks like the fastlane firebase_app_distribution or fastlane env commands has not enough privileges to get access to plugin. Try to run command as Administrator.
Did you search for previous issues about this plugin?
Did you post this at the plugin's Github repo?
I'm having the same issue on Mojave
I'm also having the same issue on Mojave
Upgrade ruby to 2.5.5 will work
https://github.com/fastlane-community/fastlane-plugin-firebase_app_distribution/issues/15
You need to edit Fastfile like in the docs
https://firebase.google.com/docs/app-distribution/ios/distribute-fastlane
@fromkk Heyyy 👋 The command should be fastlane run firebase_app_distribution (not fastlane firebase_app_distribution ). The run is important 😇
In my case the error was resolved after using
sudo fastlane firebase_app_distribution
Also mu custom lane to distribute app via firebase need to start with sudo
sudo fastlane my_custom_distribution_lane
Looks like files in firebase_app_distribution plugin have incorrect permissions, 640 by default. This can be fixed with
sudo chmod -R a+r /Library/Ruby/Gems/2.6.0/gems/fastlane-plugin-firebase_app_distribution-0.1.4
so you don't need to run fastlane itself with sudo
@gkhloptov thank you, changing permissions helped me.
Hi sir gkhloptov! I can't update my rubygems into updated I'm currently using 2.3.7.
This error message that I got whenever I tried to update gems
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions for the /Library/Ruby/Gems/2.3.0 directory.
|
2025-04-01T06:38:39.639031
| 2019-12-18T12:51:56
|
539662167
|
{
"authors": [
"MephestoKhaan"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5852",
"repo": "fastlane/fastlane",
"url": "https://github.com/fastlane/fastlane/issues/15813"
}
|
gharchive/issue
|
Exit Status 70. But rewriting the -exportArchive plist does something.
New Issue Checklist
[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues
Issue Description
Using fastlane to automate builds generated from Unity3D into testflight. I am not using my own certificate/provisioning profile since this is for a client (his personal account, not company). So he sent me the .p12 and .mobileprovisioning.
I can distribuite it OK using XCode 11.0 directly.
But when using fastlane I get the infamous:
+ xcodebuild -exportArchive -exportOptionsPlist /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_config20191218-68019-9q8o9z.plist -archivePath '/Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2019-12-18/wrld 2019-12-18 12.37.54.xcarchive' -exportPath /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_output20191218-68019-1m5pzng
2019-12-18 12:43:30.674 xcodebuild[69223:318216] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/Unity-iPhone_2019-12-18_12-43-30.673.xcdistributionlogs'.
error: exportArchive: "wrld.app" requires a provisioning profile.
Error Domain=IDEProvisioningErrorDomain Code=9 ""wrld.app" requires a provisioning profile." UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription="wrld.app" requires a provisioning profile., NSLocalizedRecoverySuggestion=Add a profile to the "provisioningProfiles" dictionary in your Export Options property list.}
** EXPORT FAILED **
[12:43:31]: Exit status: 70
[12:43:31]: No provisioning profile provided
[12:43:31]: Make sure to pass a valid provisioning for each required target
[12:43:31]: Check out the docs on how to fix this: https://docs.fastlane.tools/actions/gym/#export-options
There is a plot twist.
If I simply execute manually the xcodebuild -exportArchive [...] command afterward, it still fails. But if then I open the plist it is pointing at which contains
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>app-store</string>
<key>provisioningProfiles</key>
<dict>
<key>com.XXXXXXXX.wlrd</key>
<string>Luca Mefisto</string>
</dict>
<key>signingStyle</key>
<string>manual</string>
<key>teamID</key>
<string>RXXXXXXXXA</string>
</dict>
</plist>
Removed everything and pasted this other version that I modified manually once, although it looks pretty much the same (note that if I simply remove the top xml line it still fails... I can only make it work if I replace everything)
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>app-store</string>
<key>provisioningProfiles</key>
<dict>
<key>com.XXXXXXXX.wrld</key>
<string>Luca Mefisto</string>
</dict>
<key>signingStyle</key>
<string>manual</string>
<key>teamID</key>
<string>RXXXXXXXXA</string>
</dict>
</plist>
Then I get:
Copying this file manually
Mac-mini:joeboyle jenkins$ vi /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_config20191218-72360-3epuey.plist
Manually pasting into this one
Mac-mini:joeboyle jenkins$ vi /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_config20191218-74350-10oeug0.plist
Mac-mini:joeboyle jenkins$ xcodebuild -exportArchive -exportOptionsPlist /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_config20191218-74350-10oeug0.plist -archivePath '/Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2019-12-18/wrld 2019-12-18 13.30.19.xcarchive' -exportPath /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_output20191218-74350-1tikyo9
2019-12-18 13:40:37.401 xcodebuild[75963:350134] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/Unity-iPhone_2019-12-18_13-40-37.400.xcdistributionlogs'.
Exported Unity-iPhone to: /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_output20191218-74350-1tikyo9
** EXPORT SUCCEEDED **
Command executed
##Fastfile
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>app-store</string>
<key>provisioningProfiles</key>
<dict>
<key>com.XXXXXXXX.wrld</key>
<string>Luca Mefisto</string>
</dict>
<key>signingStyle</key>
<string>manual</string>
<key>teamID</key>
<string>RXXXXXXXXA</string>
</dict>
</plist>
fastlane ios beta
Complete output when running fastlane, including the stack trace and command used
fastlane ios beta
[✔] 🚀
[13:30:11]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[13:30:13]: ------------------------------
[13:30:13]: --- Step: default_platform ---
[13:30:13]: ------------------------------
[13:30:13]: Driving the lane 'ios beta' 🚀
[13:30:13]: -----------------
[13:30:13]: --- Step: gym ---
[13:30:13]: -----------------
[13:30:13]: $ xcodebuild -showBuildSettings -scheme Unity-iPhone -project ./Unity-iPhone.xcodeproj
[13:30:16]: Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...
[13:30:19]: Detected provisioning profile mapping: {:"com.XXXXXX.wlrd"=>"Luca Mefisto"}
+-------------------------------------------------------------+-------------------------------------------------------------------+
| Summary for gym 2.137.0 |
+-------------------------------------------------------------+-------------------------------------------------------------------+
| scheme | Unity-iPhone |
| export_method | app-store |
| export_options.signingStyle | manual |
| export_options.teamID | RXXXXXXXXA|
| export_options.provisioningProfiles.com.jXXXXXXt.wlrd | Luca Mefisto |
| project | ./Unity-iPhone.xcodeproj |
| destination | generic/platform=iOS |
| output_name | wrld |
| build_path | /Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2019-12-18 |
| clean | false |
| output_directory | . |
| silent | false |
| skip_package_ipa | false |
| result_bundle | false |
| buildlog_path | ~/Library/Logs/gym |
| skip_profile_detection | false |
| xcode_path | /Applications/Xcode.app |
+-------------------------------------------------------------+-------------------------------------------------------------------+
[13:30:19]: $ set -o pipefail && xcodebuild -scheme Unity-iPhone -project ./Unity-iPhone.xcodeproj -destination 'generic/platform=iOS' -archivePath /Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2019-12-18/wrld\ 2019-12-18\ 13.30.19.xcarchive archive | tee /Users/Shared/Jenkins/Library/Logs/gym/wrld-Unity-iPhone.log | xcpretty
[13:30:21]: ▸ Copying /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Data
[13:30:22]: ▸ Compiling LaunchScreen-iPhone.xib
[13:30:25]: ▸ Compiling LaunchScreen-iPad.xib
[13:30:27]: ▸ Processing Info.plist
[13:30:27]: ▸ User-supplied CFBundleIdentifier value 'com.joeboyle.arkit.wrld' in the Info.plist must be the same as the PRODUCT_BUNDLE_IDENTIFIER build setting value ''. (in target 'Unity-iPhone' from project 'Unity-iPhone')
[13:30:27]: ▸ 'UILaunchImages' has been deprecated, use launch storyboards instead. (in target 'Unity-iPhone' from project 'Unity-iPhone')
[13:30:28]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/UnityInterface.h:148:36: 'UILocalNotification' is deprecated: first deprecated in iOS 10.0 - Use UserNotifications Framework's UNNotificationRequest [-Wdeprecated-declarations]
[13:30:28]: ▸ void UnitySendLocalNotification(UILocalNotification* notification);
[13:30:28]: ▸ ^
[13:30:29]: ▸ Precompiling /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Prefix.pch
[13:30:29]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/UnityInterface.h:148:36: 'UILocalNotification' is deprecated: first deprecated in iOS 10.0 - Use UserNotifications Framework's UNNotificationRequest [-Wdeprecated-declarations]
[13:30:29]: ▸ void UnitySendLocalNotification(UILocalNotification* notification);
[13:30:29]: ▸ ^
[13:30:29]: ▸ Compiling UnresolvedVirtualCallStubs.cpp
[13:30:30]: ▸ Compiling UnityICallRegistration.cpp
[13:30:30]: ▸ Compiling UnityClassRegistration.cpp
[13:30:30]: ▸ Compiling RegisterMonoModules.cpp
[13:30:30]: ▸ Compiling RegisterFeatures.cpp
[13:30:30]: ▸ Compiling InternalProfiler.cpp
[13:30:30]: ▸ Compiling Il2CppTypeDefinitions.cpp
[13:30:38]: ▸ Compiling Il2CppReversePInvokeWrapperTable.cpp
[13:30:38]: ▸ Compiling StoreReview.m
[13:30:38]: ▸ Compiling main.mm
[13:30:38]: ▸ Compiling iPhone_Sensors.mm
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/iPhone_Sensors.mm:516:42: 'GCGamepad' is deprecated: first deprecated in iOS 10.0 [-Wdeprecated-declarations]
[13:30:38]: ▸ static void ReportJoystickBasic(int idx, GCGamepad* gamepad)
[13:30:38]: ▸ ^
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/iPhone_Sensors.mm:641:26: 'gamepad' is deprecated: first deprecated in iOS 10.0 [-Wdeprecated-declarations]
[13:30:38]: ▸ else if ([controller gamepad] != nil)
[13:30:38]: ▸ ^
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/iPhone_Sensors.mm:642:46: 'gamepad' is deprecated: first deprecated in iOS 10.0 [-Wdeprecated-declarations]
[13:30:38]: ▸ ReportJoystickBasic(idx, [controller gamepad]);
[13:30:38]: ▸ ^
[13:30:38]: ▸ Compiling WWWConnection.mm
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/WWWConnection.mm:223:27: implicit conversion loses integer precision: 'NSInteger' (aka 'long') to 'unsigned int' [-Wshorten-64-to-32]
[13:30:38]: ▸ transmitted = [_outputStream write: bytes maxLength: dataSize];
[13:30:38]: ▸ ^
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/WWWConnection.mm:398:52: 'initWithRequest:delegate:startImmediately:' is deprecated: first deprecated in iOS 9.0 - Use NSURLSession (see NSURLSession.h) [-Wdeprecated-declarations]
[13:30:38]: ▸ delegate.connection = [[NSURLConnection alloc] initWithRequest: request delegate: delegate startImmediately: NO];
[13:30:38]: ▸ ~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/WWWConnection.mm:374:40: implicit conversion loses integer precision: 'CFIndex' (aka 'long') to 'unsigned int' [-Wshorten-64-to-32]
[13:30:38]: ▸ unsigned transmitted = CFWriteStreamWrite(writeStream, (UInt8*)bytes, dataSize);
[13:30:38]: ▸ ^
[13:30:38]: ▸ Compiling VideoPlayer.mm
[13:30:38]: ▸ Compiling UnityViewControllerListener.mm
[13:30:38]: ▸ Compiling UnityViewControllerBase.mm
[13:30:38]: ▸ Compiling UnityViewControllerBase+tvOS.mm
[13:30:38]: ▸ Compiling UnityViewControllerBase+iOS.mm
[13:30:38]: ▸ Compiling UnityView.mm
[13:30:38]: ▸ Compiling UnityView+tvOS.mm
[13:30:38]: ▸ Compiling UnityView+iOS.mm
[13:30:38]: ▸ Compiling UnityView+Keyboard.mm
[13:30:38]: ▸ Compiling UnityReplayKit_Scripting.mm
[13:30:38]: ▸ Compiling UnityReplayKit.mm
[13:30:38]: ▸ Compiling UnityAppController.mm
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/UnityAppController.mm:182:78: 'UILocalNotification' is deprecated: first deprecated in iOS 10.0 - Use UserNotifications Framework's UNNotificationRequest [-Wdeprecated-declarations]
[13:30:38]: ▸ - (void)application:(UIApplication*)application didReceiveLocalNotification:(UILocalNotification*)notification
[13:30:38]: ▸ ~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/UnityAppController.mm:182:1: implementing deprecated method [-Wdeprecated-implementations]
[13:30:38]: ▸ - (void)application:(UIApplication*)application didReceiveLocalNotification:(UILocalNotification*)notification
[13:30:38]: ▸ ^
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/UnityAppController.mm:252:9: 'UILocalNotification' is deprecated: first deprecated in iOS 10.0 - Use UserNotifications Framework's UNNotificationRequest [-Wdeprecated-declarations]
[13:30:38]: ▸ if (UILocalNotification* notification = [launchOptions objectForKey: UIApplicationLaunchOptionsLocalNotificationKey])
[13:30:38]: ▸ ^
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/UnityAppController.mm:252:74: 'UIApplicationLaunchOptionsLocalNotificationKey' is deprecated: first deprecated in iOS 10.0 - Use UserNotifications Framework's -[UNUserNotificationCenterDelegate didReceiveNotificationResponse:withCompletionHandler:] [-Wdeprecated-declarations]
[13:30:38]: ▸ if (UILocalNotification* notification = [launchOptions objectForKey: UIApplicationLaunchOptionsLocalNotificationKey])
[13:30:38]: ▸ ^
[13:30:38]: ▸ Compiling UnityAppController+ViewHandling.mm
[13:30:38]: ▸ Compiling UnityAppController+UnityInterface.mm
[13:30:38]: ▸ Compiling UnityAppController+Rendering.mm
[13:30:38]: ▸ Compiling UnityAdsUnityWrapper.mm
[13:30:38]: ▸ Compiling SplashScreen.mm
[13:30:38]: ▸ Compiling RenderPluginDelegate.mm
[13:30:38]: ▸ Compiling OrientationSupport.mm
[13:30:38]: ▸ Compiling OnDemandResources.mm
[13:30:38]: ▸ Compiling MetalHelper.mm
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/MetalHelper.mm:96:9: 'OSAtomicCompareAndSwap32Barrier' is deprecated: first deprecated in iOS 10.0 - Use std::atomic_compare_exchange_strong() from instead [-Wdeprecated-declarations]
[13:30:38]: ▸ OSAtomicCompareAndSwap32Barrier(surface->bufferChanged, 0, &surface->bufferChanged);
[13:30:38]: ▸ ^
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/MetalHelper.mm:100:13: 'OSAtomicCompareAndSwap32Barrier' is deprecated: first deprecated in iOS 10.0 - Use std::atomic_compare_exchange_strong() from instead [-Wdeprecated-declarations]
[13:30:38]: ▸ OSAtomicCompareAndSwap32Barrier(surface->bufferCompleted[i], -1, &surface->bufferCompleted[i]);
[13:30:38]: ▸ ^
[13:30:38]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/MetalHelper.mm:86:28: implicit conversion loses integer precision: 'MTLPixelFormat' to 'unsigned int' [-Wshorten-64-to-32]
[13:30:38]: ▸ surface->colorFormat = colorFormat;
[13:30:38]: ▸ ^
[13:30:38]: ▸ Compiling LifeCycleListener.mm
[13:30:38]: ▸ Compiling Keyboard.mm
[13:30:38]: ▸ Compiling Il2CppOptions.cpp
[13:30:38]: ▸ Compiling Il2CppMethodPointerTable.cpp
[13:30:38]: ▸ Compiling Il2CppMetadataUsage.cpp
[13:30:38]: ▸ Compiling Il2CppMetadataRegistration.cpp
[13:30:38]: ▸ Compiling Il2CppInvokerTable.cpp
[13:30:57]: ▸ Compiling Il2CppInteropDataTable.cpp
[13:30:57]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Native/Il2CppInteropDataTable.cpp:1406:26: 'extern' variable has an initializer [-Wextern-initializer]
[13:30:57]: ▸ extern Il2CppInteropData g_Il2CppInteropData[419] =
[13:30:57]: ▸ ~ ^~~~~~~~~~~
[13:30:57]: ▸ Compiling Il2CppGenericMethodTable.cpp
[13:30:57]: ▸ Compiling Il2CppGenericMethodPointerTable.cpp
[13:30:57]: ▸ Compiling Il2CppGenericMethodDefinitions.cpp
[13:30:57]: ▸ Compiling Il2CppGenericInstDefinitions.cpp
[13:30:57]: ▸ Compiling Il2CppGenericComDefinitions0.cpp
[13:30:57]: ▸ Compiling Il2CppGenericClassTable.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_9Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_8Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_7Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_6Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_5Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_57Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_56Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_55Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_54Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_53Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_52Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_51Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_50Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_4Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_49Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_48Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_47Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_46Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_45Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_44Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_43Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_42Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_41Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_40Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_3Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_39Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_38Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_37Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_36Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_35Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_34Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_33Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_32Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_31Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_30Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_2Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_29Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_28Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_27Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_26Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_25Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_24Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_23Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_22Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_21Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_20Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_1Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_19Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_18Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_17Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_16Table.cpp
[13:30:57]: ▸ Compiling Il2CppCompilerCalculateTypeValues_15Table.cpp
[13:30:58]: ▸ Compiling Il2CppCompilerCalculateTypeValues_14Table.cpp
[13:30:58]: ▸ Compiling Il2CppCompilerCalculateTypeValues_13Table.cpp
[13:30:58]: ▸ Compiling Il2CppCompilerCalculateTypeValues_12Table.cpp
[13:30:58]: ▸ Compiling Il2CppCompilerCalculateTypeValues_11Table.cpp
[13:30:59]: ▸ Compiling Il2CppCompilerCalculateTypeValues_10Table.cpp
[13:30:59]: ▸ Compiling Il2CppCompilerCalculateTypeValues_0Table.cpp
[13:30:59]: ▸ Compiling Il2CppCompilerCalculateTypeValuesTable.cpp
[13:30:59]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Native/Il2CppCompilerCalculateTypeValuesTable.cpp:3853:23: 'extern' variable has an initializer [-Wextern-initializer]
[13:30:59]: ▸ extern const int32_t* g_FieldOffsetTable[5706] =
[13:30:59]: ▸ ^
[13:30:59]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Native/Il2CppCompilerCalculateTypeValuesTable.cpp:15268:41: 'extern' variable has an initializer [-Wextern-initializer]
[13:30:59]: ▸ extern const Il2CppTypeDefinitionSizes* g_Il2CppTypeDefinitionSizesTable[5706] =
[13:30:59]: ▸ ^
[13:31:00]: ▸ Compiling Il2CppCodeRegistration.cpp
[13:31:00]: ▸ Compiling Il2CppAttributes.cpp
[13:31:21]: ▸ Compiling GlesHelper.mm
[13:31:21]: ▸ Compiling GenericMethods7.cpp
[13:31:21]: ▸ Compiling GenericMethods6.cpp
[13:31:21]: ▸ Compiling GenericMethods5.cpp
[13:31:21]: ▸ Compiling GenericMethods4.cpp
[13:31:21]: ▸ Compiling GenericMethods3.cpp
[13:31:21]: ▸ Compiling GenericMethods2.cpp
[13:31:21]: ▸ Compiling GenericMethods1.cpp
[13:31:21]: ▸ Compiling GenericMethods0.cpp
[13:31:21]: ▸ Compiling FullScreenVideoPlayer.mm
[13:31:21]: ▸ Compiling Filesystem.mm
[13:31:21]: ▸ Compiling EAGLContextHelper.mm
[13:31:21]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/EAGLContextHelper.mm:21:44: implicit conversion loses integer precision: 'EAGLRenderingAPI' to 'const int' [-Wshorten-64-to-32]
[13:31:21]: ▸ const int targetApi = parent ? parent.API : api;
[13:31:21]: ▸ ^
[13:31:21]: ▸ Compiling DisplayManager.mm
[13:31:21]: ▸ Compiling DeviceSettings.mm
[13:31:21]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Classes/Unity/DeviceSettings.mm:281:1: control may reach end of non-void function [-Wreturn-type]
[13:31:21]: ▸ }
[13:31:21]: ▸ ~~~~~~~~~ ^~~~~~~~~~
[13:31:21]: ▸ Compiling CrashReporter.mm
[13:31:21]: ▸ Compiling Clipper.m
[13:31:21]: ▸ Compiling CameraCapture.mm
[13:31:21]: ▸ Compiling CVTextureCache.mm
[13:31:21]: ▸ Compiling CMVideoSampling.mm
[13:31:21]: ▸ Compiling Bulk_netstandard_0.cpp
[13:31:21]: ▸ Compiling Bulk_mscorlib_9.cpp
[13:31:28]: ▸ Compiling Bulk_mscorlib_8.cpp
[13:31:28]: ▸ Compiling Bulk_mscorlib_7.cpp
[13:31:28]: ▸ Compiling Bulk_mscorlib_6.cpp
[13:31:30]: ▸ Compiling Bulk_mscorlib_5.cpp
[13:31:36]: ▸ Compiling Bulk_mscorlib_4.cpp
[13:31:36]: ▸ Compiling Bulk_mscorlib_3.cpp
[13:31:36]: ▸ Compiling Bulk_mscorlib_20.cpp
[13:31:36]: ▸ Compiling Bulk_mscorlib_2.cpp
[13:31:42]: ▸ Compiling Bulk_mscorlib_19.cpp
[13:31:43]: ▸ Compiling Bulk_mscorlib_18.cpp
[13:31:43]: ▸ Compiling Bulk_mscorlib_17.cpp
[13:31:44]: ▸ Compiling Bulk_mscorlib_16.cpp
[13:31:49]: ▸ Compiling Bulk_mscorlib_15.cpp
[13:31:51]: ▸ Compiling Bulk_mscorlib_14.cpp
[13:31:52]: ▸ Compiling Bulk_mscorlib_13.cpp
[13:31:54]: ▸ Compiling Bulk_mscorlib_12.cpp
[13:31:58]: ▸ Compiling Bulk_mscorlib_11.cpp
[13:32:00]: ▸ Compiling Bulk_mscorlib_10.cpp
[13:32:00]: ▸ Compiling Bulk_mscorlib_1.cpp
[13:32:03]: ▸ Compiling Bulk_mscorlib_0.cpp
[13:32:08]: ▸ Compiling Bulk_UnityEngine_0.cpp
[13:32:08]: ▸ Compiling Bulk_UnityEngine.UnityWebRequestTextureModule_0.cpp
[13:32:08]: ▸ Compiling Bulk_UnityEngine.UnityWebRequestModule_0.cpp
[13:32:08]: ▸ Compiling Bulk_UnityEngine.UnityAnalyticsModule_0.cpp
[13:32:08]: ▸ Compiling Bulk_UnityEngine.UI_3.cpp
[13:32:08]: ▸ Compiling Bulk_UnityEngine.UI_2.cpp
[13:32:11]: ▸ Compiling Bulk_UnityEngine.UI_1.cpp
[13:32:11]: ▸ Compiling Bulk_UnityEngine.UI_0.cpp
[13:32:12]: ▸ Compiling Bulk_UnityEngine.UIModule_0.cpp
[13:32:12]: ▸ Compiling Bulk_UnityEngine.TextRenderingModule_0.cpp
[13:32:12]: ▸ Compiling Bulk_UnityEngine.SharedInternalsModule_0.cpp
[13:32:12]: ▸ Compiling Bulk_UnityEngine.PhysicsModule_0.cpp
[13:32:12]: ▸ Compiling Bulk_UnityEngine.Physics2DModule_0.cpp
[13:32:12]: ▸ Compiling Bulk_UnityEngine.ParticleSystemModule_0.cpp
[13:32:13]: ▸ Compiling Bulk_UnityEngine.JSONSerializeModule_0.cpp
[13:32:13]: ▸ Compiling Bulk_UnityEngine.ImageConversionModule_0.cpp
[13:32:13]: ▸ Compiling Bulk_UnityEngine.IMGUIModule_0.cpp
[13:32:17]: ▸ Compiling Bulk_UnityEngine.GameCenterModule_0.cpp
[13:32:17]: ▸ Compiling Bulk_UnityEngine.CoreModule_2.cpp
[13:32:17]: ▸ Compiling Bulk_UnityEngine.CoreModule_1.cpp
[13:32:21]: ▸ Compiling Bulk_UnityEngine.CoreModule_0.cpp
[13:32:23]: ▸ Compiling Bulk_UnityEngine.AudioModule_0.cpp
[13:32:23]: ▸ Compiling Bulk_UnityEngine.AnimationModule_0.cpp
[13:32:23]: ▸ Compiling Bulk_Unity.TextMeshPro_3.cpp
[13:32:28]: ▸ Compiling Bulk_Unity.TextMeshPro_2.cpp
[13:32:32]: ▸ Compiling Bulk_Unity.TextMeshPro_1.cpp
[13:32:34]: ▸ Compiling Bulk_Unity.TextMeshPro_0.cpp
[13:32:34]: ▸ Compiling Bulk_System_9.cpp
[13:32:34]: ▸ Compiling Bulk_System_8.cpp
[13:32:37]: ▸ Compiling Bulk_System_7.cpp
[13:32:40]: ▸ Compiling Bulk_System_6.cpp
[13:32:40]: ▸ Compiling Bulk_System_5.cpp
[13:32:44]: ▸ Compiling Bulk_System_4.cpp
[13:32:45]: ▸ Compiling Bulk_System_3.cpp
[13:32:49]: ▸ Compiling Bulk_System_2.cpp
[13:32:49]: ▸ Compiling Bulk_System_1.cpp
[13:32:52]: ▸ Compiling Bulk_System_0.cpp
[13:32:53]: ▸ Compiling Bulk_System.Xml_9.cpp
[13:32:59]: ▸ Compiling Bulk_System.Xml_8.cpp
[13:32:59]: ▸ Compiling Bulk_System.Xml_7.cpp
[13:33:03]: ▸ Compiling Bulk_System.Xml_6.cpp
[13:33:03]: ▸ Compiling Bulk_System.Xml_5.cpp
[13:33:08]: ▸ Compiling Bulk_System.Xml_4.cpp
[13:33:09]: ▸ Compiling Bulk_System.Xml_3.cpp
[13:33:16]: ▸ Compiling Bulk_System.Xml_2.cpp
[13:33:16]: ▸ Compiling Bulk_System.Xml_14.cpp
[13:33:16]: ▸ Compiling Bulk_System.Xml_13.cpp
[13:33:18]: ▸ Compiling Bulk_System.Xml_12.cpp
[13:33:24]: ▸ Compiling Bulk_System.Xml_11.cpp
[13:33:24]: ▸ Compiling Bulk_System.Xml_10.cpp
[13:33:25]: ▸ Compiling Bulk_System.Xml_1.cpp
[13:33:29]: ▸ Compiling Bulk_System.Xml_0.cpp
[13:33:29]: ▸ Compiling Bulk_System.Xml.Linq_0.cpp
[13:33:29]: ▸ Compiling Bulk_System.Runtime.Serialization_0.cpp
[13:33:29]: ▸ Compiling Bulk_System.Numerics_0.cpp
[13:33:30]: ▸ Compiling Bulk_System.Net.Http_0.cpp
[13:33:35]: ▸ Compiling Bulk_System.IO.Compression_0.cpp
[13:33:35]: ▸ Compiling Bulk_System.Globalization.Extensions_0.cpp
[13:33:35]: ▸ Compiling Bulk_System.Diagnostics.StackTrace_0.cpp
[13:33:35]: ▸ Compiling Bulk_System.Data_7.cpp
[13:33:37]: ▸ Compiling Bulk_System.Data_6.cpp
[13:33:42]: ▸ Compiling Bulk_System.Data_5.cpp
[13:33:42]: ▸ Compiling Bulk_System.Data_4.cpp
[13:33:44]: ▸ Compiling Bulk_System.Data_3.cpp
[13:33:49]: ▸ Compiling Bulk_System.Data_2.cpp
[13:33:49]: ▸ Compiling Bulk_System.Data_1.cpp
[13:33:52]: ▸ Compiling Bulk_System.Data_0.cpp
[13:33:55]: ▸ Compiling Bulk_System.Core_0.cpp
[13:33:55]: ▸ Compiling Bulk_System.Configuration_0.cpp
[13:33:55]: ▸ Compiling Bulk_Newtonsoft.Json_3.cpp
[13:33:59]: ▸ Compiling Bulk_Newtonsoft.Json_2.cpp
[13:34:00]: ▸ Compiling Bulk_Newtonsoft.Json_1.cpp
[13:34:02]: ▸ Compiling Bulk_Newtonsoft.Json_0.cpp
[13:34:05]: ▸ Compiling Bulk_Mono.Security_1.cpp
[13:34:05]: ▸ Compiling Bulk_Mono.Security_0.cpp
[13:34:09]: ▸ Compiling Bulk_Generics_9.cpp
[13:34:10]: ▸ Compiling Bulk_Generics_8.cpp
[13:34:10]: ▸ Compiling Bulk_Generics_7.cpp
[13:34:13]: ▸ Compiling Bulk_Generics_6.cpp
[13:34:18]: ▸ Compiling Bulk_Generics_5.cpp
[13:34:18]: ▸ Compiling Bulk_Generics_4.cpp
[13:34:19]: ▸ Compiling Bulk_Generics_3.cpp
[13:34:20]: ▸ Compiling Bulk_Generics_26.cpp
[13:34:25]: ▸ Compiling Bulk_Generics_25.cpp
[13:34:26]: ▸ Compiling Bulk_Generics_24.cpp
[13:34:29]: ▸ Compiling Bulk_Generics_23.cpp
[13:34:29]: ▸ Compiling Bulk_Generics_22.cpp
[13:34:35]: ▸ Compiling Bulk_Generics_21.cpp
[13:34:36]: ▸ Compiling Bulk_Generics_20.cpp
[13:34:38]: ▸ Compiling Bulk_Generics_2.cpp
[13:34:38]: ▸ Compiling Bulk_Generics_19.cpp
[13:34:44]: ▸ Compiling Bulk_Generics_18.cpp
[13:34:44]: ▸ Compiling Bulk_Generics_17.cpp
[13:34:45]: ▸ Compiling Bulk_Generics_16.cpp
[13:34:46]: ▸ Compiling Bulk_Generics_15.cpp
[13:34:52]: ▸ Compiling Bulk_Generics_14.cpp
[13:34:52]: ▸ Compiling Bulk_Generics_13.cpp
[13:34:53]: ▸ Compiling Bulk_Generics_12.cpp
[13:34:57]: ▸ Compiling Bulk_Generics_11.cpp
[13:35:01]: ▸ Compiling Bulk_Generics_10.cpp
[13:35:01]: ▸ Compiling Bulk_Generics_1.cpp
[13:35:01]: ▸ Compiling Bulk_Generics_0.cpp
[13:35:07]: ▸ Compiling Bulk_GLTFSerialization_1.cpp
[13:35:07]: ▸ Compiling Bulk_GLTFSerialization_0.cpp
[13:35:09]: ▸ Compiling Bulk_DOTween_0.cpp
[13:35:09]: ▸ Compiling Bulk_Assembly-CSharp_9.cpp
[13:35:09]: ▸ Compiling Bulk_Assembly-CSharp_8.cpp
[13:35:13]: ▸ Compiling Bulk_Assembly-CSharp_7.cpp
[13:35:16]: ▸ Compiling Bulk_Assembly-CSharp_6.cpp
[13:35:17]: ▸ Compiling Bulk_Assembly-CSharp_5.cpp
[13:35:17]: ▸ Compiling Bulk_Assembly-CSharp_4.cpp
[13:35:22]: ▸ Compiling Bulk_Assembly-CSharp_3.cpp
[13:35:26]: ▸ Compiling Bulk_Assembly-CSharp_2.cpp
[13:35:26]: ▸ Compiling Bulk_Assembly-CSharp_1.cpp
[13:35:26]: ▸ Compiling Bulk_Assembly-CSharp_0.cpp
[13:35:30]: ▸ Compiling AppDelegateListener.mm
[13:35:30]: ▸ Compiling ActivityIndicator.mm
[13:35:30]: ▸ Compiling AVCapture.mm
[13:35:30]: ▸ Compiling ARWorldMap.mm
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:292:10: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ if ([ARImageAnchor class])
[13:35:30]: ▸ ^
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:306:37: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ featuresSupported &= (bool)[ARWorldMap class];
[13:35:30]: ▸ ^~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:308:37: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ featuresSupported &= (bool)[ARReferenceObject class];
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:315:10: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ if ([ARReferenceObject class])
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:406:16: 'ARPlaneDetectionVertical' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ret |= ARPlaneDetectionVertical;
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:21:5: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:21:38: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:45:5: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = [NSKeyedUnarchiver unarchiveObjectWithData:wmdata];
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:52:5: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:52:38: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:59:5: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:59:38: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:69:5: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = [NSKeyedUnarchiver unarchiveObjectWithData:wmdata];
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:79:5: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:79:38: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:93:5: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:93:38: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:107:5: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARWorldMap.mm:107:38: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ARWorldMap* worldMap = (__bridge ARWorldMap*)worldMapPtr;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ Compiling ARSessionNative.mm
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:292:10: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ if ([ARImageAnchor class])
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:306:37: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ featuresSupported &= (bool)[ARWorldMap class];
[13:35:30]: ▸ ^~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:308:37: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ featuresSupported &= (bool)[ARReferenceObject class];
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:315:10: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ if ([ARReferenceObject class])
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:406:16: 'ARPlaneDetectionVertical' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ ret |= ARPlaneDetectionVertical;
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:62:94: 'ARWorldMappingStatus' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ static inline UnityARWorldMappingStatus GetUnityARWorldMappingStatusFromARWorldMappingStatus(ARWorldMappingStatus worldMappingStatus)
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:80:15: 'AREnvironmentTexturing' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ static inline AREnvironmentTexturing GetAREnvironmentTexturingFromUnityAREnvironmentTexturing(UnityAREnvironmentTexturing& unityEnvTexturing)
[13:35:30]: ▸ ^
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:102:21: 'setMaximumNumberOfTrackedImages:' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ appleConfig.maximumNumberOfTrackedImages = unityConfig.maximumNumberOfTrackedImages;
[13:35:30]: ▸ ^
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:106:21: 'setAutoFocusEnabled:' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ appleConfig.autoFocusEnabled = (BOOL) unityConfig.enableAutoFocus;
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:109:49: 'ARVideoFormat' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ appleConfig.videoFormat = (__bridge ARVideoFormat*) unityConfig.ptrVideoFormat;
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:109:25: 'setVideoFormat:' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ appleConfig.videoFormat = (__bridge ARVideoFormat*) unityConfig.ptrVideoFormat;
[13:35:30]: ▸ ^~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:115:49: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ appleConfig.initialWorldMap = (__bridge ARWorldMap*)unityConfig.ptrWorldMap;
[13:35:30]: ▸ ^~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:115:21: 'setInitialWorldMap:' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ appleConfig.initialWorldMap = (__bridge ARWorldMap*)unityConfig.ptrWorldMap;
[13:35:30]: ▸ ^~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:116:21: 'setEnvironmentTexturing:' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ appleConfig.environmentTexturing = GetAREnvironmentTexturingFromUnityAREnvironmentTexturing(unityConfig.environmentTexturing);
[13:35:30]: ▸ ^~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:146:90: 'ARPlaneGeometry' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ inline void UnityARPlaneGeometryFromARPlaneGeometry(UnityARPlaneGeometry& planeGeometry, ARPlaneGeometry arPlaneGeometry)
[13:35:30]: ▸ ^~~~~~~~~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:173:88: 'geometry' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ UnityARPlaneGeometryFromARPlaneGeometry(anchorData.planeGeometry, nativeAnchor.geometry);
[13:35:30]: ▸ ^
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:238:92: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ inline void UnityARImageAnchorDataFromARImageAnchorPtr(UnityARImageAnchorData& anchorData, ARImageAnchor nativeAnchor)
[13:35:30]: ▸ ^~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:400:55: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ UnityARImageAnchorDataFromARImageAnchorPtr(data, (ARImageAnchor*)anchor);
[13:35:30]: ▸ ^
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:407:55: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ UnityARImageAnchorDataFromARImageAnchorPtr(data, (ARImageAnchor*)anchor);
[13:35:30]: ▸ ^~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:414:55: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ UnityARImageAnchorDataFromARImageAnchorPtr(data, (ARImageAnchor*)anchor);
[13:35:30]: ▸ ^~~~~~~~~~~~~
[13:35:30]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:500:103: 'worldMappingStatus' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:30]: ▸ unityARCamera.worldMappingStatus = GetUnityARWorldMappingStatusFromARWorldMappingStatus(frame.worldMappingStatus);
[13:35:30]: ▸ ^~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:792:84: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ [nativeSession->_classToCallbackMap setObject:imageAnchorCallbacks forKey:[ARImageAnchor class]];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:842:36: incompatible pointer types assigning to 'NSMutableSet<ARReferenceObject > ' from 'NSSet<ARReferenceObject > ' [-Wincompatible-pointer-types]
[13:35:31]: ▸ referenceObjects = dynamicReferenceObjects;
[13:35:31]: ▸ ^~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:820:15: 'ARReferenceImage' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ NSSet<ARReferenceImage > referenceImages = [ARReferenceImage referenceImagesInGroupNamed:strResourceGroup bundle:nil];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:820:55: 'ARReferenceImage' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ NSSet<ARReferenceImage > referenceImages = [ARReferenceImage referenceImagesInGroupNamed:strResourceGroup bundle:nil];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:821:16: 'setDetectionImages:' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ config.detectionImages = referenceImages;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:826:22: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ NSMutableSet<ARReferenceObject > referenceObjects = nullptr;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:830:58: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ [referenceObjects setByAddingObjectsFromSet:[ARReferenceObject referenceObjectsInGroupNamed:strResourceGroup bundle:nil]];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:835:19: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ NSSet<ARReferenceObject > dynamicReferenceObjects = (__bridge NSSet<ARReferenceObject > )unityConfig.ptrDynamicReferenceObjects;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:835:83: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ NSSet<ARReferenceObject > dynamicReferenceObjects = (__bridge NSSet<ARReferenceObject > )unityConfig.ptrDynamicReferenceObjects;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:846:16: 'setDetectionObjects:' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ config.detectionObjects = referenceObjects;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:958:28: 'setWorldOrigin:' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ [session->_session setWorldOrigin:arWorldMatrix];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1093:13: 'ARVideoFormat' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ for(ARVideoFormat arVideoFormat in ARWorldTrackingConfiguration.supportedVideoFormats)
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1093:74: 'supportedVideoFormats' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ for(ARVideoFormat arVideoFormat in ARWorldTrackingConfiguration.supportedVideoFormats)
[13:35:31]: ▸ ^~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1099:43: implicit conversion loses integer precision: 'NSInteger' (aka 'long') to 'int' [-Wshorten-64-to-32]
[13:35:31]: ▸ videoFormat.framesPerSecond = arVideoFormat.framesPerSecond;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1122:1: control reaches end of non-void function [-Wreturn-type]
[13:35:31]: ▸ }
[13:35:31]: ▸ ~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1155:30: 'getCurrentWorldMapWithCompletionHandler:' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ [nativeSession->_session getCurrentWorldMapWithCompletionHandler:^(ARWorldMap worldMap, NSError error)
[13:35:31]: ▸ ^
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1155:72: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ [nativeSession->_session getCurrentWorldMapWithCompletionHandler:^(ARWorldMap worldMap, NSError error)
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1184:30: 'createReferenceObjectWithTransform:center:extent:completionHandler:' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ [nativeSession->_session createReferenceObjectWithTransform:transform center:center extent:extent completionHandler:^(ARReferenceObject * referenceObject, NSError * error)
[13:35:31]: ▸ ^~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1184:123: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ [nativeSession->_session createReferenceObjectWithTransform:transform center:center extent:extent completionHandler:^(ARReferenceObject * referenceObject, NSError * error)
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARSessionNative.mm:1195:10: 'AREnvironmentProbeAnchor' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ if ([AREnvironmentProbeAnchor class])
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ Compiling ARPointCloud.mm
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:292:10: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ if ([ARImageAnchor class])
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:306:37: 'ARWorldMap' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ featuresSupported &= (bool)[ARWorldMap class];
[13:35:31]: ▸ ^~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:308:37: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ featuresSupported &= (bool)[ARReferenceObject class];
[13:35:31]: ▸ ^~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:315:10: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ if ([ARReferenceObject class])
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:406:16: 'ARPlaneDetectionVertical' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ret |= ARPlaneDetectionVertical;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARPointCloud.mm:18:12: implicit conversion loses integer precision: 'NSUInteger' (aka 'unsigned long') to 'int' [-Wshorten-64-to-32]
[13:35:31]: ▸ return [pointCloud count];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ Compiling ARKitNativeObjectDetection.mm
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:308:37: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:315:10: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ if ([ARReferenceObject class])
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:406:16: 'ARPlaneDetectionVertical' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ret |= ARPlaneDetectionVertical;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ 'ARObjectAnchor' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:39:136: 'ARObjectScanningConfiguration' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ inline void GetARSessionConfigurationFromARKitObjectScanningSessionConfiguration(ARKitObjectScanningSessionConfiguration& unityConfig, ARObjectScanningConfiguration appleConfig)
[13:35:31]: ▸ ^
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:68:57: 'ARObjectAnchor' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ UnityARObjectAnchorDataFromARObjectAnchorPtr(data, (ARObjectAnchor)anchor);
[13:35:31]: ▸ ^
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:99:85: 'ARObjectAnchor' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ [nativeSession->_classToCallbackMap setObject:objectAnchorCallbacks forKey:[ARObjectAnchor class]];
[13:35:31]: ▸ ^~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:109:12: 'ARObjectScanningConfiguration' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ return ARObjectScanningConfiguration.isSupported;
[13:35:31]: ▸ ^~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:115:5: 'ARObjectScanningConfiguration' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARObjectScanningConfiguration config = [ARObjectScanningConfiguration new];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:142:5: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject referenceObject = (__bridge ARReferenceObject)ptr;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:142:52: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject referenceObject = (__bridge ARReferenceObject)ptr;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:158:5: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject referenceObject = (__bridge ARReferenceObject)referenceObjectPtr;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:158:52:
[13:35:31]: ▸ 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:182:5: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject referenceObject = [NSKeyedUnarchiver unarchiveObjectWithData:rodata];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:195:5:
[13:35:31]: ▸ 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:222:5: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject referenceObject = [NSKeyedUnarchiver unarchiveObjectWithData:rodata];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:232:5: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject referenceObject = (__bridge ARReferenceObject*)ptr;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:246:5:
[13:35:31]: ▸ 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:246:52: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject* referenceObject = (__bridge ARReferenceObject*)ptr;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:260:5: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:260:52:
[13:35:31]: ▸ 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:269:5: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject* referenceObject = (__bridge ARReferenceObject*)ptr;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:269:52: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ARReferenceObject* referenceObject = (__bridge ARReferenceObject*)ptr;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:294:18: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ NSMutableSet<ARReferenceObject*> referenceObjectsSet = [[NSMutableSet<ARReferenceObject> alloc] init];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:294:76: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ NSMutableSet<ARReferenceObject*> referenceObjectsSet = [[NSMutableSet<ARReferenceObject> alloc] init];
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:300:18: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ NSMutableSet<ARReferenceObject*> referenceObjectsSet = (__bridge NSMutableSet<ARReferenceObject> )roSet;
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:300:84:
[13:35:31]: ▸ 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:301:5:
[13:35:31]: ▸ 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitNativeObjectDetection.mm:301:46:
[13:35:31]: ▸ 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ Compiling AREnvironmentProbe.mm
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:292:10: 'ARImageAnchor' is only available on iOS 11.3 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ if ([ARImageAnchor class])
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:308:37:
[13:35:31]: ▸ 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ ^~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/ARKitDefines.h:315:10: 'ARReferenceObject' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ if ([ARReferenceObject class])
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~
[13:35:31]: ▸ ⚠️ /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle/Libraries/UnityARKitPlugin/Plugins/iOS/UnityARKit/NativeInterface/AREnvironmentProbe.mm:113:77: 'AREnvironmentProbeAnchor' is only available on iOS 12.0 or newer [-Wunguarded-availability-new]
[13:35:31]: ▸ UnityAREnvironmentProbeAnchorDataFromAREnvironmentProbeAnchorPtr(data, (AREnvironmentProbeAnchor)anchor);
[13:35:31]: ▸ ^~~~~~~~~~~~~~~~~~~~~~~~
[13:35:31]: ▸ Linking wrld
[13:35:37]: ▸ Generating 'wrld.app.dSYM'
[13:35:54]: ▸ Running script 'Run Script'
[13:35:56]: ▸ Touching wrld.app (in target 'Unity-iPhone' from project 'Unity-iPhone')
[13:35:57]: ▸ Archive Succeeded
[13:35:57]: Generated plist file with the following values:
[13:35:57]: ▸ -----------------------------------------
[13:35:57]: ▸ {
[13:35:57]: ▸ "signingStyle": "manual",
[13:35:57]: ▸ "teamID": "RXXXXXXXXA",
[13:35:57]: ▸ "provisioningProfiles": {
[13:35:57]: ▸ "com.XXXXXX.wlrd": "Luca Mefisto"
[13:35:57]: ▸ },
[13:35:57]: ▸ "method": "app-store"
[13:35:57]: ▸ }
[13:35:57]: ▸ -----------------------------------------
[13:35:57]: $ /usr/bin/xcrun /Library/Ruby/Gems/2.3.0/gems/fastlane-2.137.0/gym/lib/assets/wrap_xcodebuild/xcbuild-safe.sh -exportArchive -exportOptionsPlist '/var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_config20191218-74350-10oeug0.plist' -archivePath /Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2019-12-18/wrld\ 2019-12-18\ 13.30.19.xcarchive -exportPath '/var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_output20191218-74350-1tikyo9'
xcodebuild -exportArchive -exportOptionsPlist /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_config20191218-74350-10oeug0.plist -archivePath '/Users/Shared/Jenkins/Library/Developer/Xcode/Archives/2019-12-18/wrld 2019-12-18 13.30.19.xcarchive' -exportPath /var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/gym_output20191218-74350-1tikyo9
2019-12-18 13:35:58.007 xcodebuild[75486:347077] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/43/934fh5xn7ybbq17dhjvc7qk000008b/T/Unity-iPhone_2019-12-18_13-35-58.006.xcdistributionlogs'.
error: exportArchive: "wrld.app" requires a provisioning profile.
Error Domain=IDEProvisioningErrorDomain Code=9 ""wrld.app" requires a provisioning profile." UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription="wrld.app" requires a provisioning profile., NSLocalizedRecoverySuggestion=Add a profile to the "provisioningProfiles" dictionary in your Export Options property list.}
** EXPORT FAILED **
[13:35:58]: Exit status: 70
[13:35:58]: No provisioning profile provided
[13:35:58]: Make sure to pass a valid provisioning for each required target
[13:35:58]: Check out the docs on how to fix this: https://docs.fastlane.tools/actions/gym/#export-options
+---------------+-------------------------+
| Build environment |
+---------------+-------------------------+
| xcode_path | /Applications/Xcode.app |
| gym_version | 2.137.0 |
| export_method | app-store |
| sdk | iPhoneOS13.0.sdk |
+---------------+-------------------------+
[13:35:58]: ▸ Touch /Users/Shared/Jenkins/Library/Developer/Xcode/DerivedData/Unity-iPhone-brfpbvtvkeekdsffhbfwvorceqej/Build/Intermediates.noindex/ArchiveIntermediates/Unity-iPhone/InstallationBuildProductsLocation/Applications/wrld.app (in target 'Unity-iPhone' from project 'Unity-iPhone')
[13:35:58]: ▸ cd /Users/Shared/Jenkins/Home/workspace/SpatialFirst_Testflight/iOS/joeboyle
[13:35:58]: ▸ /usr/bin/touch -c /Users/Shared/Jenkins/Library/Developer/Xcode/DerivedData/Unity-iPhone-brfpbvtvkeekdsffhbfwvorceqej/Build/Intermediates.noindex/ArchiveIntermediates/Unity-iPhone/InstallationBuildProductsLocation/Applications/wrld.app
[13:35:58]: ▸ ** ARCHIVE SUCCEEDED **
[13:35:58]:
[13:35:58]: ⬆️ Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
[13:35:58]: 📋 For the complete and more detailed error log, check the full log at:
[13:35:58]: 📋 /Users/Shared/Jenkins/Library/Logs/gym/wrld-Unity-iPhone.log
[13:35:58]:
[13:35:58]: Looks like fastlane ran into a build/archive error with your project
[13:35:58]: It's hard to tell what's causing the error, so we wrote some guides on how
[13:35:58]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[13:35:58]: Before submitting an issue on GitHub, please follow the guide above and make
[13:35:58]: sure your project is set up correctly.
[13:35:58]: fastlane uses xcodebuild commands to generate your binary, you can see the
[13:35:58]: the full commands printed out in yellow in the above log.
[13:35:58]: Make sure to inspect the output above, as usually you'll find more error information there
[13:35:58]:
+------------------+----------+
| Lane Context |
+------------------+----------+
| DEFAULT_PLATFORM | ios |
| PLATFORM_NAME | ios |
| LANE_NAME | ios beta |
+------------------+----------+
[13:35:58]: Error packaging up the application
+------+------------------+-------------+
| fastlane summary |
+------+------------------+-------------+
| Step | Action | Time (in s) |
+------+------------------+-------------+
| 1 | default_platform | 0 |
| 💥 | gym | 344 |
+------+------------------+-------------+
[13:35:58]: fastlane finished with errors
[!] Error packaging up the application
Environment
✅ fastlane environment ✅
Stack
Key
Value
OS
10.14.6
Ruby
2.3.7
Bundler?
false
Git
git version 2.21.0 (Apple Git-122)
Installation Source
/usr/local/bin/fastlane
Host
Mac OS X 10.14.6 (18G2022)
Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib
OpenSSL Version
LibreSSL 2.6.5
Is contained
false
Is homebrew
false
Is installed via Fabric.app
false
Xcode Path
/Applications/Xcode.app/Contents/Developer/
Xcode Version
11.0
System Locale
Variable
Value
LANG
en_GB.UTF-8
✅
LC_ALL
LANGUAGE
fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
# https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
# https://docs.fastlane.tools/plugins/available-plugins
#
# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane
default_platform(:ios)
platform :ios do
desc "Push a new beta build to TestFlight"
lane :beta do
gym(
scheme: 'Unity-iPhone',
export_method: 'app-store',
export_options: {
signingStyle:"manual",
teamID:"RXXXXXXXXXA",
provisioningProfiles: {
"com.XXXXXXXXX.wlrd"=>"Luca Mefisto"
}
})
upload_to_testflight(skip_waiting_for_build_processing: false)
end
end
`./fastlane/Appfile`
app_identifier("com.XXXXXXXX.wrld") # The bundle identifier of your app
<EMAIL_ADDRESS># Your Apple email address
itc_team_id("1XXXXXXX6") # App Store Connect Team ID
team_id("RXXXXXXXXA") # Developer Portal Team ID
# For more information about the Appfile, see:
# https://docs.fastlane.tools/advanced/#appfile
fastlane gems
Gem
Version
Update-Status
fastlane
2.137.0
✅ Up-To-Date
Loaded fastlane plugins:
No plugins Loaded
Loaded gems
Gem
Version
did_you_mean
1.0.0
slack-notifier
2.3.2
rouge
2.0.7
xcpretty
0.3.0
terminal-notifier
2.0.0
terminal-table
1.8.0
plist
3.5.0
public_suffix
2.0.5
addressable
2.6.0
multipart-post
2.0.0
word_wrap
1.0.0
babosa
1.0.2
colored
1.2
highline
1.7.10
commander-fastlane
4.4.6
http-cookie
1.0.3
faraday-cookie_jar
0.0.6
faraday
0.17.1
faraday_middleware
0.13.1
fastimage
2.1.5
mini_magick
4.9.5
multi_xml
0.6.0
rubyzip
1.3.0
security
0.1.3
xcpretty-travis-formatter
1.0.0
bundler
2.0.1
naturally
2.2.0
simctl
1.6.5
jwt
2.1.0
uber
0.1.0
declarative
0.0.10
declarative-option
0.1.0
representable
3.0.4
retriable
3.1.2
mime-types
3.2.2
multi_json
1.13.1
signet
0.11.0
memoist
0.16.0
googleauth
0.6.7
httpclient
2.8.3
google-api-client
0.23.9
google-cloud-core
1.3.0
digest-crc
0.4.1
google-cloud-storage
1.16.0
emoji_regex
1.0.1
tty-cursor
0.7.0
tty-spinner
0.9.1
tty-screen
0.7.0
json
2.2.0
io-console
0.4.5
excon
0.65.0
CFPropertyList
3.0.0
libxml-ruby
2.9.0
atomos
0.1.3
claide
1.0.2
colored2
3.1.2
nanaimo
0.2.6
xcodeproj
1.11.0
unf
0.1.4
domain_name
0.5.20190701
unicode-display_width
1.6.0
os
1.0.1
psych
<IP_ADDRESS>
mime-types-data
3.2019.0331
generated on: 2019-12-18
I somehow "narrowed" down the problem and worked around it (but still would love to understand why it happens).
Instead of passing a export_options dictionary. I am passing an entire .plist like the ones above. After fiddling with it I discovered that the problem is the entry:
<key>com.XXXXXXXX.wrld</key>
Simply deleting it and writting it again manually allows the plist to work.
Maybe a weird character? It uses all normal characters really so not sure what is going on (but has 3 dots, com.something.somethingelse.wrld.
|
2025-04-01T06:38:39.671392
| 2017-03-07T11:32:43
|
212406041
|
{
"authors": [
"KrauseFx",
"hjanuschka",
"kas-kad"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5853",
"repo": "fastlane/fastlane",
"url": "https://github.com/fastlane/fastlane/issues/8456"
}
|
gharchive/issue
|
undefined local variable or method `cert' for #Sigh::Runner:...
New Issue Checklist
[yes] Updated fastlane to the latest version
[no] I have read the Contribution Guidelines
Issue Description
Complete output when running fastlane, including the stack trace and command used
You can use: --capture_output as the last commandline argument to get that collected for you
$ fastlane sigh --development
+-------------------------------------+-------------------------------------+
| Summary for sigh 2.19.2 |
+-------------------------------------+-------------------------------------+
| development | true |
| adhoc | false |
| skip_install | false |
| force | false |
| app_identifier | com.infobip.mobilemessaging.example |
| team_id | T6U248P7YM |
| ignore_profiles_with_different_name | false |
| skip_fetch_profiles | false |
| skip_certificate_verification | false |
| platform | ios |
+-------------------------------------+-------------------------------------+
[11:51:44]: To not be asked about this value, you can specify it using 'username'
Your Apple ID Username<EMAIL_ADDRESS>[11:51:51]: Starting login with user<EMAIL_ADDRESS>[11:51:54]: Successfully logged in
[11:51:54]: Fetching profiles...
[11:51:55]: Verifying certificates...
Looking for related GitHub issues on fastlane/fastlane...
➡️ undefined local variable or method `cert' for #<Sigh::Runner:...>
https://github.com/fastlane/fastlane/issues/8456 [open] 0 💬
17 minutes ago
➡️ undefined method `[]=' for nil:NilClass for sigh manage
https://github.com/fastlane/fastlane/issues/6751 [closed] 15 💬
4 weeks ago
➡️ Undefined method `fetch` for nil:NilClass (NoMethodError) again?
https://github.com/fastlane/fastlane/issues/7307 [closed] 4 💬
3 weeks ago
and 34 more at: https://github.com/fastlane/fastlane/search?q=undefined%20%60cert'%20for%20Sigh::Runner&type=Issues&utf8=✓
🔗 You can ⌘ + double-click on links to open them directly in your browser.
/usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/runner.rb:126:in `block (2 levels) in fetch_profiles': [!] undefined local variable or method `cert' for #<Sigh::Runner:0x007f8caaa520b0> (NameError)
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/runner.rb:119:in `each'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/runner.rb:119:in `block in fetch_profiles'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/runner.rb:101:in `each'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/runner.rb:101:in `find_all'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/runner.rb:101:in `fetch_profiles'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/runner.rb:20:in `run'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/manager.rb:7:in `start'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/commands_generator.rb:55:in `block (2 levels) in run'
from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.3/lib/commander/command.rb:178:in `call'
from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.3/lib/commander/command.rb:153:in `run'
from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.3/lib/commander/runner.rb:446:in `run_active_command'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:38:in `run!'
from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.3/lib/commander/delegates.rb:15:in `run!'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/commands_generator.rb:123:in `run'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/sigh/lib/sigh/commands_generator.rb:11:in `start'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/fastlane/lib/fastlane/cli_tools_distributor.rb:51:in `take_off'
from /usr/local/lib/ruby/gems/2.3.0/gems/fastlane-2.19.2/bin/fastlane:15:in `<top (required)>'
from /usr/local/bin/fastlane:23:in `load'
from /usr/local/bin/fastlane:23:in `<main>'
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
🚫 fastlane environment 🚫
Stack
Key
Value
OS
10.11.5
Ruby
2.3.1
Bundler?
false
Git
git version 2.10.1 (Apple Git-78)
Installation Source
/usr/local/bin/fastlane
Host
Mac OS X 10.11.5 (15F34)
Ruby Lib Dir
/usr/local/Cellar/ruby/2.3.1_2/lib
OpenSSL Version
OpenSSL 1.0.2j 26 Sep 2016
Is contained
false
Is homebrew
false
Is installed via Fabric.app
false
Xcode Path
/Applications/Xcode.app/Contents/Developer/
Xcode Version
8.2.1
System Locale
Error
No Locale with UTF8 found 🚫
fastlane gems
Gem
Version
Update-Status
fastlane
2.19.2
✅ Up-To-Date
Loaded fastlane plugins:
Plugin
Version
Update-Status
fastlane-plugin-wait_xcrun
0.1.1
✅ Up-To-Date
Loaded gems
Gem
Version
did_you_mean
1.0.0
slack-notifier
1.5.1
claide
1.0.1
colored
1.2
nanaimo
0.2.3
xcodeproj
1.4.2
rouge
1.11.1
xcpretty
0.2.4
terminal-notifier
1.7.1
unicode-display_width
1.1.3
terminal-table
1.7.3
plist
3.2.0
public_suffix
2.0.5
addressable
2.5.0
multipart-post
2.0.0
word_wrap
1.0.0
tty-screen
0.5.0
babosa
1.0.2
highline
1.7.8
commander
4.4.3
faraday
0.11.0
http-cookie
1.0.3
faraday-cookie_jar
0.0.6
gh_inspector
1.0.3
mini_magick
4.5.1
multi_json
1.12.1
multi_xml
0.6.0
security
0.1.3
xcpretty-travis-formatter
0.0.4
bundler
1.13.5
json
2.0.3
io-console
0.4.5
excon
0.55.0
rubyzip
1.2.1
fastlane-plugin-wait_xcrun
0.1.1
generated on: 2017-03-07
the commit that broke things:
https://github.com/fastlane/fastlane/commit/1e7b08032d9e030c998cf65c7fc7256beb6ce5fa
this PR https://github.com/fastlane/fastlane/pull/8394 @joshdholtz can you have a look ? looks like cert is not defined in this case.
@kas-kad i prepared a PR: https://github.com/fastlane/fastlane/pull/8457 could you give it a try?
@hjanuschka
now it's better
+-------------------------------------+-------------------------------------+
| Summary for sigh 2.19.2 |
+-------------------------------------+-------------------------------------+
| development | true |
| adhoc | false |
| skip_install | false |
| force | false |
| app_identifier | com.infobip.mobilemessaging.example |
| team_id | T6U248P7YM |
| ignore_profiles_with_different_name | false |
| skip_fetch_profiles | false |
| skip_certificate_verification | false |
| platform | ios |
+-------------------------------------+-------------------------------------+
[12:26:28]: To not be asked about this value, you can specify it using 'username'
Your Apple ID Username<EMAIL_ADDRESS>[12:26:35]: Starting login with user<EMAIL_ADDRESS>[12:26:40]: Successfully logged in
[12:26:40]: Fetching profiles...
[12:26:41]: Verifying certificates...
[12:26:48]: Certificate for Provisioning Profile 'Mobile Messaging Example - Development' not available locally: D8HLFR9G6T, skipping this one...
[12:26:48]: Certificate for Provisioning Profile 'Mobile Messaging Example - Development' not available locally: 62NRV5PBES, skipping this one...
[12:26:49]: Certificate for Provisioning Profile 'Mobile Messaging Example - Development' not available locally: 528498GTG5, skipping this one...
[12:26:49]: Certificate for Provisioning Profile 'Mobile Messaging Example - Development' not available locally: E345RE9WRX, skipping this one...
[12:26:49]: Certificate for Provisioning Profile 'Mobile Messaging Example - Development' not available locally: U5VVSCF3TG, skipping this one...
[12:26:50]: Certificate for Provisioning Profile 'Mobile Messaging Example - Development' not available locally: 2GG4P54QQK, skipping this one...
[12:26:53]: Cannot download cert X4XHH93295 - Couldn't download certificate, got this instead: {"responseId"=>"80def118-52ef-472f-9695-20b6fde1efc5", "resultCode"=>7100, "resultString"=>"Certificate 'X4XHH93295' not found", "userString"=>"There is no certificate with ID 'X4XHH93295' on this team.", "creationTimestamp"=>"2017-03-07T12:26:53Z", "protocolVersion"=>"QH65B2", "userLocale"=>"en_US", "requestUrl"=>"https://developer.apple.com/services-account/QH65B2/account/ios/certificate/downloadCertificateContent.action", "httpCode"=>200}
[12:26:54]: Cannot download cert H29YDV5Z7X - Couldn't download certificate, got this instead: {"responseId"=>"e6a769ec-6e96-4048-9a3c-8aadd09b2926", "resultCode"=>7100, "resultString"=>"Certificate 'H29YDV5Z7X' not found", "userString"=>"There is no certificate with ID 'H29YDV5Z7X' on this team.", "creationTimestamp"=>"2017-03-07T12:26:54Z", "protocolVersion"=>"QH65B2", "userLocale"=>"en_US", "requestUrl"=>"https://developer.apple.com/services-account/QH65B2/account/ios/certificate/downloadCertificateContent.action", "httpCode"=>200}
[12:26:57]: Certificate for Provisioning Profile 'com.infobip.mobilemessaging.example Development' not available locally: D8HLFR9G6T, skipping this one...
[12:26:57]: Certificate for Provisioning Profile 'com.infobip.mobilemessaging.example Development' not available locally: 62NRV5PBES, skipping this one...
[12:26:58]: Certificate for Provisioning Profile 'com.infobip.mobilemessaging.example Development' not available locally: 528498GTG5, skipping this one...
[12:26:58]: Certificate for Provisioning Profile 'com.infobip.mobilemessaging.example Development' not available locally: E345RE9WRX, skipping this one...
[12:26:58]: Found 1 matching profile(s)
[12:26:58]: Downloading provisioning profile...
[12:27:01]: Successfully downloaded provisioning profile...
[12:27:01]: Installing provisioning profile...
@kas-kad many thx for your help - working on adding a spec for the PR
This should be resolved now 👍 Thanks everybody
|
2025-04-01T06:38:39.684199
| 2017-03-28T18:36:03
|
217653275
|
{
"authors": [
"KrauseFx",
"ohayon",
"parleer"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5854",
"repo": "fastlane/fastlane",
"url": "https://github.com/fastlane/fastlane/pull/8688"
}
|
gharchive/pull-request
|
Resolves failure when deliver() called with name: argument and name.txt exists in locale-based metadata.
Checklist
[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.
Description
Resolves an issue that prevents fastlane from submitting to AppStore. Specifically, when metadata/[language]/name.txt exists AND a name is passed to deliver(), fastlane errors with 'string not matched'. Other scenarios may also reproduce this error, but this is mine.
Motivation and Context
In load_from_filesystem() in upload_metadata.rb, the line options[key][language] ||= File.read(path) attempts to assign the value of a file to the options[key][language] variable. But if options[key] already exists, then the prior line, options[key] ||= {}, never gets executed and options[key] is not an object, thus failing with the error 'string not matched'. There is no doubt a more elegant way to resolve this issue, but this worked for me.
https://github.com/fastlane/fastlane/issues/8482
This change was required in order to deliver my app to the AppStore.
I signed it.
Hey @parleer, thanks for the PR. Please update the PR title to describe what this PR changes
I'm not sure why the circleci tests are failing. Appears unrelated to my code change?
Hey @parleer thanks for submitting this PR and apologies for the long time since a response. I was wondering if you could take a look at https://github.com/fastlane/fastlane/pull/9337 and see if it solves some of the same problems you were having? We have made a couple other changes to how languages are handled recently too. Let us know if this is still a PR you are trying to get through and maybe it should be rebased on #9337 when that gets merged in? Thanks! 🚀
David, the latest fastlane 2.38.1 appears to be working for my specific
issue. I do see the following error in the log, but it appears to be
working.
[11:49:30]: Activating language en-US...
[11:50:03]: Error with provided 'name'. Must be a hash, the key being the
language.
[11:50:03]: Uploading metadata to iTunes Connect
[11:50:05]: Successfully uploaded set of metadata to iTunes Connect
[11:50:07]: Uploading binary to iTunes Connect
[11:50:07]: Going to upload updated app to iTunes Connect
On Tue, Jun 13, 2017 at 11:05 AM, David Ohayon<EMAIL_ADDRESS>wrote:
Hey @parleer https://github.com/parleer thanks for submitting this PR
and apologies for the long time since a response. I was wondering if you
could take a look at #9337
https://github.com/fastlane/fastlane/pull/9337 and see if it solves
some of the same problems you were having? We have made a couple other
changes to how languages are handled recently too. Let us know if this is
still a PR you are trying to get through and maybe it should be rebased on
#9337 https://github.com/fastlane/fastlane/pull/9337 when that gets
merged in? Thanks! 🚀
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/pull/8688#issuecomment-308166385,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHbd84srUWVUP3F2e93IYAnZg4Agpawks5sDrM0gaJpZM4MsBk6
.
Hey @parleer thanks again for the PR! I am going to close this for now as it seems like some other changes fixed your issue. Let us know if there is anything else we can do to help or if there are any other changes you would want to submit 😄 🐙 🚀 !
|
2025-04-01T06:38:39.699992
| 2022-12-27T12:28:44
|
1511757754
|
{
"authors": [
"fatih-yavuz",
"mohanshetty"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5855",
"repo": "fatih-yavuz/links.dev",
"url": "https://github.com/fatih-yavuz/links.dev/issues/112"
}
|
gharchive/issue
|
How to add custom js like adding custom css
How to add custom js like adding custom css
you cannot add custom js.
ok thank you
|
2025-04-01T06:38:39.735466
| 2020-07-27T16:18:52
|
666418194
|
{
"authors": [
"JackCloudman",
"fbaligand"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5856",
"repo": "fbaligand/kibana-enhanced-table",
"url": "https://github.com/fbaligand/kibana-enhanced-table/issues/123"
}
|
gharchive/issue
|
Can't add visualization to Canvas
Hello, I tested the plugin(v1.9.1) for kibana 7.8 and i want add my document table to canvas, but when i search elements dont return results
Visualize:
Canvas:
Hi,
Honestly, I didn’t tried this feature yet.
If you add a standard data table, does it work fine?
Yes it works with standard kibana visualizations, i don't know if is necessary a tag that enable discover it in canvas tab.
Well, it seems that something special is required so that a visualization can be added in canvas (given your tests).
For now, I don’t know what, but I will ask the question to kibana team.
Good news: enhanced table v1.10.0 is out with this issue fixed for Kibana 7.9+ and more enhancements!
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.10.0
|
2025-04-01T06:38:39.766448
| 2016-05-10T00:56:36
|
153902110
|
{
"authors": [
"braingineer",
"nouiz",
"tboquet"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5857",
"repo": "fchollet/keras",
"url": "https://github.com/fchollet/keras/issues/2678"
}
|
gharchive/issue
|
keras crashing when using convolutions
hi all,
recently updated to theano 0.9 and cudnn v5, things broke. downgraded 0.8.2 and things were moderately working again ( I could import theano... ). But then I tried to run some things and ran into the issue pasted below. I pull the master branch from keras and it still happens. I tried it with a lasagne mnist example, and it doesn't happen. I haven't tried downloading theano or cudnn yet.
(DL)cogniton [examples] $ python imdb_cnn.py
Using Theano backend.
Using gpu device 0: GeForce GTX 980 (CNMeM is disabled, cuDNN 5004)
Loading data...
Downloading data from https://s3.amazonaws.com/text-datasets/imdb.pkl
33218560/33213513 [==============================] - 1s
20000 train sequences
5000 test sequences
Pad sequences (samples x time)
X_train shape: (20000, 400)
X_test shape: (5000, 400)
Build model...
Traceback (most recent call last):
File "imdb_cnn.py", line 84, in <module>
validation_data=(X_test, y_test))
File "/home/cogniton/research/code/keras/keras/models.py", line 405, in fit
sample_weight=sample_weight)
File "/home/cogniton/research/code/keras/keras/engine/training.py", line 996, in fit
self._make_test_function()
File "/home/cogniton/research/code/keras/keras/engine/training.py", line 676, in _make_test_function
**self._function_kwargs)
File "/home/cogniton/research/code/keras/keras/backend/theano_backend.py", line 517, in function
return Function(inputs, outputs, updates=updates, **kwargs)
File "/home/cogniton/research/code/keras/keras/backend/theano_backend.py", line 503, in __init__
**kwargs)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/compile/function.py", line 320, in function
output_keys=output_keys)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/compile/pfunc.py", line 479, in pfunc
output_keys=output_keys)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/compile/function_module.py", line 1777, in orig_func
tion
defaults)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/compile/function_module.py", line 1641, in create
input_storage=input_storage_lists, storage_map=storage_map)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/link.py", line 690, in make_thunk
storage_map=storage_map)[:3]
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/vm.py", line 1003, in make_all
no_recycling))
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/sandbox/cuda/__init__.py", line 256, in make_thunk
compute_map, no_recycling)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/op.py", line 970, in make_thunk
no_recycling)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/op.py", line 879, in make_c_thunk
output_storage=node_output_storage)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/cc.py", line 1200, in make_thunk
keep_lock=keep_lock)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/cc.py", line 1143, in __compile__
keep_lock=keep_lock)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/cc.py", line 1595, in cthunk_factory
key=key, lnk=self, keep_lock=keep_lock)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/cmodule.py", line 1142, in module_from_key
module = lnk.compile_cmodule(location)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/cc.py", line 1506, in compile_cmodule
preargs=preargs)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/sandbox/cuda/nvcc_compiler.py", line 410, in compile
_str
return dlimport(lib_filename)
File "/home/cogniton/anaconda/envs/DL/lib/python2.7/site-packages/theano/gof/cmodule.py", line 299, in dlimport
rval = __import__(module_name, {}, {}, [module_name])
RuntimeError: ('The following error happened while compiling the node', GpuDnnConv{algo='small', inplace=True}(GpuContiguous.0,
GpuContiguous.0, GpuAllocEmpty.0, GpuDnnConvDesc{border_mode='valid', subsample=(1, 1), conv_mode='conv', precision='float32'}
.0, Constant{1.0}, Constant{0.0}), '\n', 'could not create cuDNN handle: CUDNN_STATUS_NOT_INITIALIZED', "[GpuDnnConv{algo='smal
l', inplace=True}(<CudaNdarrayType(float32, (False, False, False, True))>, <CudaNdarrayType(float32, 4D)>, <CudaNdarrayType(flo
at32, 4D)>, <CDataType{cudnnConvolutionDescriptor_t}>, Constant{1.0}, Constant{0.0})]")
Fixed the issue. The bug was due to drivers.
B.
Can you tell more? I have see a few report of this, it could help other.
Can you tell what your GPU was, what is the driver version you had problems
and which one worked well?
On Tue, May 10, 2016 at 5:54 AM, Brian McMahan<EMAIL_ADDRESS>wrote:
Fixed the issue. The bug was due to drivers.
B.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/fchollet/keras/issues/2678#issuecomment-218111540
@braingineer I also have weird errors because I updated the drivers (see Theano/Theano#4495). Do you have a working solution to this bug?
short version:
I have a gtx 980
originally (last year) started with linux display drivers then upgraded to cuda 7.0
yesterday, upgraded to cudnn v5 and cudnn v5 assumes cuda 7.5
tried to then upgrade cuda to 7.5
if cuda 7.5 got mucked for any reason, it creates issues
assuming the cuda 7.5 install not being exactly what cudnn v5 expects, my only (desperate last attempt) solution was to completely wipe the os and reinstall to 7.5 from a fresh install
uninstalling cuda drivers to get a fresh install seems to be problematic (according to cuda forum posts)
longer version:
The only reported case I could find for CUDNN_STATUS_NOT_INITIALIZED was here: https://github.com/karpathy/neuraltalk2/issues/57
So that lead me to believe I had the wrong cuda version. It turns out cuDNN is for 7.5 or later. cuDNN v5 Release Candidate (RC) (April, 2016), for CUDA 7.5 and later.. So, I tried to upgrade. This lead to some other issues because installing the cuda 7.5 install script wasn't quite working.
For me, most of the difficulty stemmed from a crappy attempt to get ethereum working and even before that, having originally installed the drivers specific to my card (the display drivers) rather than the cuda drivers. The internet (and accumulating frustrating experiences) pointed at having to just completely wipe the OS and reinstall because of residual traces of the drivers. (which, it wasn't so bad because I have a separate partition for the os contents..).
Hope that helps.
|
2025-04-01T06:38:39.773490
| 2015-07-29T17:24:10
|
97986456
|
{
"authors": [
"fchollet",
"geminatea",
"harpone",
"quantlearn"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5858",
"repo": "fchollet/keras",
"url": "https://github.com/fchollet/keras/issues/460"
}
|
gharchive/issue
|
Hessian-free optimization?
Just probing here a little bit to see if there was an interest for a Hessian-free optimizer, as e.g. in theano-hf by boulanni. Don't know the Keras code much yet, but I'd like to get some input if that's doable in a reasonable amount of time...
It would definitely be possible to add it as an Optimizer (see keras/optimizers.py).
It's not a priority, since HF has been shown to underperform RMSprop and Adagrad, while being more computationally intensive.
Oh OK, wasn't aware of that... can you point me to a paper etc. with some benchmarks etc?
Can't find any paper, but what I would recommend you do is simply to implement it in Keras (should be quick to adapt boulanni's code) and benchmark it (time and accuracy) against other optimizers. Then you can answer the question without having to rely on what I remember reading about.
The fact is, nobody uses Hessian-Free optimization. If there was any advantage to it, everybody would be using it.
Just a FYI to everybody seeing this: a paper by Sutskever et al discusses Heassian-free vs. momentum methods here:
http://machinelearning.wustl.edu/mlpapers/paper_files/icml2013_sutskever13.pdf
Quote: "Momentum-accelerated SGD, despite being a firstorder
approach, is capable of accelerating directions
of low-curvature just like an approximate Newton
method such as HF. Our experiments support the idea
that this is important, as we observed that the use of
stronger momentum (as determined by µ) had a dramatic
e↵ect on optimization performance, particularly
for the RNNs. Moreover, we showed that HF can be
viewed as a first-order method, and as a generalization
of NAG in particular, and that it already derives some
of its benefits through a momentum-like mechanism."
So yeah, probably Hessian-free is not very useful...
For what it's worth (responding to an old thread) the above quote by @harpone does not establish the conclusion. Actually the 2013 ICML paper quoted above demonstrates that careful use of momentum methods almost closes the gap in performance that existed between HF-based methods and other first-order methods. That is, as of 2013, the HF-based methods of Martens + Sutskever were still better than the momentum methods employed in the 2013 paper. (at least for a number of important tasks, esp. training SRNs)
Perhaps the conversation subsequently evolved to the point that HF-based methods no longer tops after the advent of Adam and others. But that requires more reading. Perhaps I will find the paper Chollet refers to about Adagrad and RMSprop as I read further.
I also have a need for a HF optimizer for estimating RNN parameters. I have played around with various first order optimizers but I am seeing too much noise, I was wondering if anyone has build a HF optimizer for Keras yet or whether I need to build one from scratch. I am currently looking at the Optimizer class to figure out what needs to be done.
|
2025-04-01T06:38:39.774668
| 2016-10-13T21:19:31
|
182903734
|
{
"authors": [
"fchollet",
"jayanthkoushik"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5859",
"repo": "fchollet/keras",
"url": "https://github.com/fchollet/keras/pull/4052"
}
|
gharchive/pull-request
|
Return decay from get_config of all optimizers
This commit adds the decay strength to the config dicts of all optimizers where it was not present.
LGTM, thanks
|
2025-04-01T06:38:39.782880
| 2016-04-05T19:38:33
|
146089426
|
{
"authors": [
"acoburn",
"awoods"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5860",
"repo": "fcrepo4/fcrepo4",
"url": "https://github.com/fcrepo4/fcrepo4/pull/1015"
}
|
gharchive/pull-request
|
Add link headers to versioned resources
Resolves both:
https://jira.duraspace.org/browse/FCREPO-1975 and
https://jira.duraspace.org/browse/FCREPO-1974
It seems that most of this involves adding headers using javax.servlet. When the response is generated, though, we are using javax.ws.rs.
This certainly works, but I wonder why we wouldn't just use JAX-RS for everything? That would mean using the JAX-RS API such as ok(...).header(...).header(...).build() rather than relying on changing the state of the internal servletResponse field.
That is a good point, however, this PR is actually a very minor change to FedoraVersions with some refactoring of the location of existing private and protected methods. I definitely think there would be value in re-examining/refactoring our use of JAX-RS.
I'm OK with using the servlet-api as is currently the case. I'm more noting the fact that we should evaluate our use of JAX-RS along the lines of this much neglected ticket that has my name on it: https://jira.duraspace.org/browse/FCREPO-1664
Merged via 15a0b2687156498a1c4722abe182fcdca9dde154
|
2025-04-01T06:38:39.792304
| 2017-05-10T02:53:24
|
227553565
|
{
"authors": [
"Neverbirth",
"SlavaRa",
"matrix3d"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5861",
"repo": "fdorg/flashdevelop",
"url": "https://github.com/fdorg/flashdevelop/issues/1625"
}
|
gharchive/issue
|
airsdk compress swf not be used
all fws
Can you explain more?
adobe air sdk 25
setting optimize bytecode =true.not use.
my proj get swf 3M size.
and i addtional compiler options -compress=true,
i get swf 1M size.
This setting only works in release mode.
@matrix3d This issue can be considered solved?
|
2025-04-01T06:38:39.840796
| 2017-04-22T11:09:07
|
223557521
|
{
"authors": [
"eddyystop",
"imdpk"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5862",
"repo": "feathersjs/feathers-guide",
"url": "https://github.com/feathersjs/feathers-guide/issues/9"
}
|
gharchive/issue
|
Comment:Step-Basic-Real-time
The link is invalid for server code:
https://github.com/feathersjs/feathers-docs/blob/master/examples/step/01/WebSocket/1.js
The link that worked for me was:
https://github.com/feathersjs/feathers-docs/blob/master/examples/step/01/websocket/1.js
Thanks for the catch! There's a PR waiting to fix this.
On Sat, Apr 22, 2017 at 7:09 AM, Damian Phillips-king <
<EMAIL_ADDRESS>wrote:
The link is invalid for server code:
https://github.com/feathersjs/feathers-docs/blob/master/
examples/step/01/WebSocket/1.js
The link that worked for me was:
https://github.com/feathersjs/feathers-docs/blob/master/
examples/step/01/websocket/1.js
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/feathersjs/feathers-guide/issues/9, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABezn4t0Q-nvDVJCWqkzOu6D66rKqgjyks5ryd_TgaJpZM4NFDYH
.
|
2025-04-01T06:38:39.902239
| 2022-09-05T05:53:36
|
1361439000
|
{
"authors": [
"codecov-commenter",
"elsirion",
"jkitman",
"justinmoon",
"okjodom"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5863",
"repo": "fedimint/fedimint",
"url": "https://github.com/fedimint/fedimint/pull/495"
}
|
gharchive/pull-request
|
Gateway detection and support for internal payments within a Mint
Enable gateways to detect payments internal to a mint, and resolve these without paying itself (the gateway) over the LN network.
To detecting internal payments when attempting to pay an invoice (outgoing contract), the gateway uses the invoice hash to requests for any existing offer from the gateway. Existence of such an offer indicates that the payment is internal to a gateway, otherwise gateway should treat this invoice as a normal external route.
On detecting an internal payment from an invoice, the gateway attempts to buys the offer and then proceeds to request a decryption of the preimage from the offer it bought. With decrypted preimage, the gateway proceeds to claim the original outgoing contract, thereby collecting fees for it's work facilitating this internal payment.
Additional:
If a gateway does not get a decrypted preimage after paying the offer, it can proceed to claw back funds from the offer
Closes #461, Closes #486
Codecov Report
Merging #495 (477a1c8) into master (2a02caa) will decrease coverage by 0.12%.
The diff coverage is 51.68%.
@@ Coverage Diff @@
## master #495 +/- ##
==========================================
- Coverage 72.74% 72.62% -0.13%
==========================================
Files 83 83
Lines 10637 10862 +225
==========================================
+ Hits 7738 7888 +150
- Misses 2899 2974 +75
Impacted Files
Coverage Δ
ln-gateway/src/ln.rs
0.00% <0.00%> (ø)
ln-gateway/src/lib.rs
38.36% <44.44%> (-3.07%)
:arrow_down:
client/client-lib/src/lib.rs
86.13% <68.42%> (-2.16%)
:arrow_down:
fedimint-api/src/db/mem_impl.rs
84.48% <0.00%> (-2.19%)
:arrow_down:
fedimint/src/consensus/mod.rs
92.90% <0.00%> (-2.03%)
:arrow_down:
client/client-lib/src/mint/mod.rs
81.64% <0.00%> (-0.95%)
:arrow_down:
modules/fedimint-mint/src/lib.rs
90.38% <0.00%> (-0.37%)
:arrow_down:
fedimint/src/net/peers.rs
92.68% <0.00%> (-0.23%)
:arrow_down:
... and 9 more
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
On our group call list week didn't we agree to have the gateway do it all?
It seems here everything is happening in the client?
Doing it all in the client is very straightforward: When the /pay_invoice method is exercised, check if you can buy the preimage from the federation before doing any RPC calls with your lightning node.
It seems here that internal payment detection is happening in the client? I don't think this is necessary.
I'm currently doing this within the Gateway client, which I believe runs as a core part of the gateway right? I may not have fully understood the boundaries of client apps!
@okjodom We should probably have an integration test for this, I could help you modify the test fixtures to create one.
@okjodom We should probably have an integration test for this, I could help you modify the test fixtures to create one.
Excellent! IMO the biggest gaps I came across with the fixtures as they are is that
GatewayTest has a public user : UserTest that has been sufficient for validating sends through gateway, but now we need two users independent and a gateway?
I'm not sure how to associate an invoice from LightningTest with a receiving UserTest so we can simulate a 3-step hop between user to gateway to user, in validating an internal payment
Possibly other gaps I haven't realized. I'd love to pair program at your next availability to add tests
This is my attempt at internal routing btw, not tested yet, just wanted to see how I'd architect it: bf083967c83c85abf6aa570681730577790891cd
This is my attempt at internal routing btw, not tested yet, just wanted to see how I'd architect it: 11c451ffedb675651b1c5c4099faf436fa9243b6
EDIT: I got more of an appreciation for some of the choices you made btw 😄 it's a hard-ish problem to do it elegantly
😎 I hope we learn more to do solve it better with future iterations.
This is my attempt at internal routing btw, not tested yet, just wanted to see how I'd architect it: 11c451ffedb675651b1c5c4099faf436fa9243b6
EDIT: I got more of an appreciation for some of the choices you made btw 😄 it's a hard-ish problem to do it elegantly
@elsirion , your proposal works nearly out of box! I adopted most of it, leaving out the fallback where you would attempt routing as external if routing as internal payment failed. My primary reasoning is that it's better to just fail early because cln would still fail us in self-payment scenario.
The utils are not necessary if we don't need the fallback behavior.
Much cleaner!
Just for completeness from yesterday's chat:
The use case for fallback is: someone has a private channel with our LN node and thus adds it as a routing hint. When they want to receive it looks like a federation-internal payment but isn't and CLN would succeed routing it.
Closing current PR in favor of #533
|
2025-04-01T06:38:39.931551
| 2017-03-28T14:21:48
|
217576762
|
{
"authors": [
"nialldonnellyfh",
"wtrocki"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5864",
"repo": "feedhenry-raincatcher/raincatcher-demo-mobile",
"url": "https://github.com/feedhenry-raincatcher/raincatcher-demo-mobile/pull/50"
}
|
gharchive/pull-request
|
Bump fh-wfm-workflow-angular version
Related to https://github.com/feedhenry-raincatcher/raincatcher-workflow-angular/pull/4
Outdated. Closing
|
2025-04-01T06:38:39.933852
| 2018-09-27T14:21:34
|
364500859
|
{
"authors": [
"camilamacedo86",
"shannon"
],
"license": "apache-2.0",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5865",
"repo": "feedhenry/fh-js-sdk",
"url": "https://github.com/feedhenry/fh-js-sdk/pull/286"
}
|
gharchive/pull-request
|
Upgrade version of fh-sync-js
Jira link(s)
https://issues.jboss.org/browse/RHMAP-20023
What
Update version of fh-sync-js to 1.3.2
Version bump to 3.0.10
Changelog update
Why
To pull in this fix: https://github.com/feedhenry/fh-sync-js/pull/45
/restest
retest this
|
2025-04-01T06:38:39.937391
| 2020-05-21T09:33:23
|
622375772
|
{
"authors": [
"girba",
"syrel"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5866",
"repo": "feenkcom/gtoolkit",
"url": "https://github.com/feenkcom/gtoolkit/issues/1069"
}
|
gharchive/issue
|
Completion popup should not move with the cursor, but stay with the beginning of the completed text
In most cases the completion does its best to not move with the cursor. However, due to some limitations in the editor it may not always be the case
|
2025-04-01T06:38:39.969692
| 2016-02-03T10:10:07
|
130978536
|
{
"authors": [
"danpalmer",
"matthiask",
"mjl"
],
"license": "bsd-3-clause",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5867",
"repo": "feincms/feincms",
"url": "https://github.com/feincms/feincms/issues/620"
}
|
gharchive/issue
|
Page admin showing each extension twice, breaks admin page
We've just started setting up a FeinCMS based blog, but have encountered a small problem.
We set up the Page model in the normal way, and register a few extensions like this:
Page.register_extensions(
'feincms.module.extensions.datepublisher',
'feincms.module.page.extensions.excerpt',
'feincms.module.page.extensions.relatedpages',
)
The extensions appear to only be loaded once - that line of code is run once, no "AlreadyRegistered" exceptions, and the migrations all work fine which implies the model is being created properly.
However, the admin shows two tabs for each extension. The tabs contain the same content, but only one (non-deterministic) tab will work at any time, which means you have to enter data twice in the admin to be sure that it will save. Also some widgets in the repeated tabs just don't work, an example of this is the multiple selection widget for the "relatedpages" extension.
I don't know enough about FeinCMS to know where to even begin looking for what might be causing this. Does anyone have any ideas about what might be causing this, or even a good place to start looking?
Thanks for the report! Which version of FeinCMS and Django are you using?
Sounds like something that should be immediately fixed.
Hi, Django 1.9.1 and FeinCMS 1.11.4. I can test on 1.9.2 soon as well, but I don't remember anything in the release notes that would affect this.
Thanks! I'll have a look at this later today.
Does the browser Javascript Console show any errors?
@mjl Yes, when I use "relatedpages", I get the following error:
Uncaught TypeError: Cannot read property 'id' of null
window.SelectFilter.init @ SelectFilter2.js:24
(anonymous function) @ VM5379:1
This appears to be an issue with there being two of the same multiple selection widgets on the page, but I'm not certain.
It seems that for some reason the initialization of the selectbox is run twice.
SelectFilter2.js renames the old select box to <name>_old, therefore the element cannot be found anymore, and that's the reason for the JavaScript error above. Probably Django's addEvent is run twice:
First when parsing the HTML
Afterwards when reinserting the HTML when building the tabbed interface (https://github.com/feincms/feincms/blob/master/feincms/static/feincms/item_editor.js#L398) — @mjl we should probably not reinsert the HTML, but instead reinsert the DOM nodes directly with $.fn.append or node.appendChild...
... unfortunately I still can't reproduce the problem with extension tabs appearing twice.
It seems that for some reason the initialization of the selectbox is run twice.
I've seen that message in the console for quite some while, it doesn't appear to be harmful though. More a red herring I'm afraid.
Some more info that might help... We override item_editor.html to add a conditional on whether there are translations available, since we a) don't use translations, and b) raise template syntax errors on any missing template variables, however this doesn't appear to make a difference (I've tried not overriding it, and we still have the issue).
If I modify relatedpages.py to call add_extension_options twice I get the same problem. But why should relatedpages.Extension.handle_modeladmin and friends be called twice?
Ok, I think I'm getting closer to finding the issue. I haven't confirmed this yet, but:
FeinCMS registers the Page with the default admin site, however we use a custom admin site instance. When autodiscover is on for admin modules, Django reads in FeinCMS's admin.py and causes the registration to happen to the default site, which we don't use. Our own registering to our custom admin site is then a second load, which is causing the extensions to be loaded twice.
I'm not sure what the solution here is. We are trying to disable autodiscover as we don't want it, but I guess the ultimate aim for FeinCMS would be to support custom admin sites, with and without autodiscover.
Great! Is there a reason why you can't just set FEINCMS_USE_PAGE_ADMIN = False in your settings?
This would of course still mean that FeinCMS pages cannot be used in more than one admin site at the same time...
Ah, that looks perfect! We hadn't seen that in the documentation. Thanks!
It's not even mentioned in the page documentation, only under settings. Does it work?
@danpalmer Does it work for you now? If yes we should document this, and also document FEINCMS_USE_PAGE_ADMIN.
The TypeError above is fixed in https://github.com/feincms/feincms/commit/ed973ac9c3ccbfca5c8b8bbc11e02c68d9978933.
Some documentation has been added in https://github.com/feincms/feincms/commit/94ffa872ac0a3addca8a8f8b26860b96f66826bd#diff-3fd23e085e479501733d484b109d838aR91
Closing this issue. @danpalmer Please reopen if things do not work for you. Thanks!
|
2025-04-01T06:38:39.998174
| 2022-11-19T19:47:29
|
1456635950
|
{
"authors": [
"felipecrs",
"tommymogensen"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5868",
"repo": "felipecrs/hass-expose-camera-stream-source",
"url": "https://github.com/felipecrs/hass-expose-camera-stream-source/issues/1"
}
|
gharchive/issue
|
error: expose_camera_stream_source - Integration
Hi There
Trying to implement this and get my TUYA cam in grigate :)
when i update my configuration.yaml i get thoe below error at restart.
First i just pasted "expose_camera_stream_source:" into the end of my config ...thats not working.
then "expose_camera_stream_source: camera.denver_shc_150" ...thats not working.
so i am a bit usunre what i am doing wrong?
Failed to restart Home Assistant
The system cannot restart because the configuration is not valid: Integration error: expose_camera_stream_source - Integration 'expose_camera_stream_source' not found.
Install from HACS
Restart HA
Add expose_camera_stream_source: in your configuration.yaml (do not add anything else)
Restart HA
Can you double check you followed these steps?
First i just pasted "expose_camera_stream_source:" into the end of my config ...thats not working.
If it continues to fail here, let me know what exactly is not working. Check your HA logs for hints.
the issue is that i cant restart HA after update of config.
i bet that i am doing something wrong it just says:
Failed to restart Home Assistant
The system cannot restart because the configuration is not valid: Integration error: expose_camera_stream_source - Integration 'expose_camera_stream_source' not found.
Are you sure you restarted HA after installing from HACS?
Oh, of course, remove expose_camera_stream_source: from your configuration.yaml if you have added it before restarting after installing with HACS.
ok sorry about that!
it seems that it where NOT isntalled even though i where sure that i installed it.
Thank you!
Weird. Anyway, let me know if you managed to add your Tuya camera to Frigate after all. :)
so folowing the guide: https://github.com/felipecrs/hass-expose-camera-stream-source
I guess that the ip...is the IP of my homeassistant installation keeping the port as that is the port of the RTSP stream that you create?
in my case my home assistant in running on <IP_ADDRESS> i guess i could be using "homeassistant.local"
so it should be as below?
frigate.yml
my_camera:
ffmpeg:
inputs:
- path: rtsp://<IP_ADDRESS>:8554/my_camera
Your example seems correct to me. I'm not sure if homeassistant.local would work, feel free to test though.
ill give it a try if /when all is working
i got Frigate running though the feed is just green.
Sanity check:
should i be able in like VLC player to open:
rtsp://<IP_ADDRESS>:8554/camera.denver_shc_150
"camera.denver_shc_150" is the entity name i HA
Yes you should be able to view the RTSP link in VLC first. But the URL should have the name of the stream you configured in go2rtc, not the name of the HA camera. Unless you configured the name in go2rtc to be exactly equal the name in HA.
go2rtc.yaml
streams:
my_camera:
- echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.denver_sho_110
So in thise case it will be:
rtsp://<IP_ADDRESS>:8554/my_camera
Correct.
Em sáb., 19 de nov. de 2022 18:23, tommymogensen @.***>
escreveu:
go2rtc.yaml
streams:
my_camera:
echo:bash
/config/custom_components/expose_camera_stream_source/get_stream.sh
camera.denver_sho_110
So in thise case it will be:
rtsp://<IP_ADDRESS>:8554/my_camera
—
Reply to this email directly, view it on GitHub
https://github.com/felipecrs/hass-expose-camera-stream-source/issues/1#issuecomment-1320972623,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBWMEJOMTO4OS7K5DYVEG3WJFAODANCNFSM6AAAAAASFO5XVE
.
You are receiving this because you commented.Message ID:
@.***
com>
i got it working in frigate now!
How do i send you a beer?
Hahaha. Great! I'm happy it worked for you!
If you can star the repo that would be already awesome. Thanks!
|
2025-04-01T06:38:40.002070
| 2017-10-17T18:16:51
|
266227558
|
{
"authors": [
"aadityakhare",
"felipecustodio"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5869",
"repo": "felipecustodio/algorithms",
"url": "https://github.com/felipecustodio/algorithms/pull/13"
}
|
gharchive/pull-request
|
Re: Issue #10
Contribution to issue #11
Hello, friend!
@aadityakhare can you describe a little bit what you are adding? Thank you so much and good Hacktoberfesting!
Well, I'd been working on a repository to add algorithms in 3 languages: C, Java, Python.
some of them are not in all 3 languages.
My addition has algorithms on the following:
Searching and sorting (Binary, Radix, Selection, Shell, etc.
Math (Armstrong no., tower of Hanoi, Integration, etc.)
Cryptography ciphers (atbash, vigenere, etc.)
Robotic Locomotion (PID, a*)
@aadityakhare that is awesome! C is a powerful beast, we love it here at my college.
Textbooks, internet resources? Have you used it in real world problems?
Thanks for the pull-request, I'll definitely take a look at the code. 👍
@felipecustodio Yeah I love C too. Since my majors is Electronics and Communication, my resources for studying anything including cryptography in coding were mainly from the internet. Study strategy: never just read up on a concept and leave it there, do implement it and see how it works, what it does. I hunt for problems on sites like hackerrank and codechef and implemt it there.
|
2025-04-01T06:38:40.009125
| 2023-07-12T18:39:38
|
1801556810
|
{
"authors": [
"felipesud"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5870",
"repo": "felipesud/temple-finder-app",
"url": "https://github.com/felipesud/temple-finder-app/issues/5"
}
|
gharchive/issue
|
Testing and Debugging - Backend and Frontend
Test the backend routes using a tool like Postman to ensure they handle CRUD operations correctly. Test the frontend components and services to verify their integration with the backend API. Debug and fix any issues or errors that arise during testing.
Branch: feature/testing
Branch: bugfix/debugging-issues
|
2025-04-01T06:38:40.022732
| 2015-11-11T19:00:59
|
116399108
|
{
"authors": [
"Emaasit",
"elbamos",
"felixcheung"
],
"license": "apache-2.0",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5871",
"repo": "felixcheung/vagrant-projects",
"url": "https://github.com/felixcheung/vagrant-projects/issues/3"
}
|
gharchive/issue
|
R interpreter for zeppelin
Hello Felix,
I saw your talk on youtube about SparkR + Zeppelin at the Seattle Spark meetup and I wanted to inquire how you set up the R interpreter for zeppelin. Is it officially supported in Zeppelin-0.5 or 0.6?
Let me know.
Thanks,
Daniel
Hello!
R interpreter is not currently merged to a Zeppelin release yet.
You are welcome to join the Zeppelin community for discussions/questions/requests: http://zeppelin.incubator.apache.org/community.html
@felixcheung Seriously?
I just watched the youtube video, Felix. Wow. Really, just wow.
@elbamos I'm not sure what you are saying, but you are welcome to talk to me directly, since you have my contacts.
@felixcheung Well, it looks like you took code that you didn't write -- where you had threatened to (falsely) claim the code was stolen from you, unless you were listed as a developer, even though you hadn't done any work -- and passed it off toward the user group as though it were your own.
@felixcheung
No Felix, you are lying. And now you are trying to cover it up. This belongs in your repo for discussion because you are the wrongdoer.
Since you have been trying to delete comments, here's one of the key ones:
@felixcheung Well, it looks like you took code that you didn't write -- where you had threatened to (falsely) claim the code was stolen from you, unless you were listed as a developer, even though you hadn't done any work -- and passed it off toward the user group as though it were your own.
To clarify, my implementation is completely my own and has been made available on day-1 as documented on my slides in my fork on github. I have not made a PR and do not plan to update it further.
The Zeppelin community is welcome to follow up on the best implementation and discuss as I've pointed out above.
Thanks, more community contribution is welcome!
@felixcheung That's a lie Felix. You never wrote a working interpreter.
Your code never implemented the "interpret" function. It was an empty shell that said it was an interpreter but actually did absolutely nothing.
You demanded to participate with me when you saw how much progress I'd made.
And since you were caught, you've been going around doing demos passing off the code I wrote as your own.
|
2025-04-01T06:38:40.066039
| 2022-11-21T04:38:17
|
1457298803
|
{
"authors": [
"bassmanitram",
"build3r"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5872",
"repo": "ferdium/ferdium-recipes",
"url": "https://github.com/ferdium/ferdium-recipes/issues/242"
}
|
gharchive/issue
|
[Bug]: Google Chat (Hangout chat) Text input focus lost
Preflight Checklist
[X] I have read the Contributing Guidelines for this project.
[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Ferdium Version
6.2.0
Recipe Name
hangoutschat
Recipe Version
1.6.0
Last Known working version of the recipe
n/a
Steps to reproduce
Open any char window
The focus remain on editor box for a second and then focus is lost.
Expected Behavior
Focus should remain on text input.
Actual Behavior
Focus is lost
Screenshots
Not applicable
Additional Information
No response
Same thing with Teams
|
2025-04-01T06:38:40.068850
| 2023-05-03T20:33:00
|
1694767056
|
{
"authors": [
"Alphrag",
"Arthur-Huan"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5873",
"repo": "ferdium/ferdium-recipes",
"url": "https://github.com/ferdium/ferdium-recipes/pull/350"
}
|
gharchive/pull-request
|
Skype & Discord icon update
Pre-flight Checklist
Please ensure you've completed all of the following.
[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
Description of Change
Updated the Skype and Discord logos to their current forms.
Hi @Arthur-Huan thanks for the PR. In order for the change to be pushed to users, the version of the recipe in their corresponding package.json need to be increased (by adding 1 to the patch number for each of them).
|
2025-04-01T06:38:40.089348
| 2023-02-24T22:59:31
|
1599373302
|
{
"authors": [
"itowlson",
"karthik2804",
"tpmccallum",
"vdice"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5874",
"repo": "fermyon/developer",
"url": "https://github.com/fermyon/developer/issues/369"
}
|
gharchive/issue
|
CI/deploy for search index (data.json)
@karthik2804 and I were discussing the following pain point: Currently, this website's search index (static/data.json) needs to be updated in each applicable PR (any PRs updating documentation content, no matter how small, are applicable). There is a command to do so (npm run build-index) and a note/reminder on the PR template, but it is still an extra step for contributors -- not to mention it introduces the common scenario of merge conflicts occuring to in-flight PRs as others are merged in.
Therefore, we'd like to find a solution where CI/automation does this chore work in the background, removing the need for contributor PRs to update this file (and eliminating the frequent merge conflict potential).
In brainstorming with @karthik2804, these are the top candidates that seemed preferable to some other scenarios discussed.
Context
Currently, the website itself is published to bindle as a Spin app after cloning this repo at a configured branch and/or commit. The live website consists of a spin up --bindle-id command using the published bindle ID.
Publish/deploy from OCI registry reference
Added below, bumped up to top potential candidate (bonus: dogfoods Spin's newly-added OCI reference support):
On every push to main, an automation agent (eg GH action) would clone the repo and run npm run build-index, then publish the website (Spin app) to an OCI registry (obvious choice: ghcr.io/fermyon/developer) via spin registry push. We'd remove Bindle from the equation and the website Nomad job would be updated to run from the pushed image reference, eg spin up -f ghcr.io/fermyon/developer:<tag>. As the search index is commited in the form of an image, we'd .gitignore the file.
Considerations: To achieve parity with current deployment workflows, which allow for deploying from arbitrary branches/commits on the fermyon origin, we'd perhaps want to add publishing of images on PRs (again just for branches on the fermyon org). Or, we could decide that ad hoc/out-of-band publishing by those with access to this repo's container registry is sufficient prior to non-main deploys. For the default website image, we could use a mutable tag like latest that would be updated on every push to main. Alternatively, we could follow the convention of using unique/"immutable" tags but would want to look into storage costs and/or automated cleanup.
Alternative:
Deploy website from branch other than main
This retains current behavior of tracking the search index in git, albeit via a different branch from main.
On every push to main, an automation agent (eg GH action) would clone the repo and run npm run build-index. To avoid churn from then having the agent push to main again (if so, we'd have one automation commit paired with every contributor commit to main), automation would push its changes to a separate branch, say, deploy (where static/data.json will still be tracked by git, as opposed to on main where we'd .gitignore it).
The website would then be deployed from the deploy branch, similar in spirit to the classic gh-pages approach. The deploy action would be updated to watch push events to this branch and the publish/website jobs would be updated similarly.
Thoughts/feedback @tpmccallum, others?
You know what, @karthik2804, we could also have the GH action publish the site to an OCI registry (obvious choice: ghcr.io/fermyon/developer) and then we could just remove bindle from the mix and update the website Nomad job to run from the reference, eg spin up -f ghcr.io/fermyon/developer:<tag>. We wouldn't need a separate deploy branch as the data.json changes would only be committed in the form of said image.
That sounds like a good idea to me @vdice.
Thanks @karthik2804, I updated the original issue description w/ the OCI approach. Added a note around your question (out-of-band) around deploying arbitrary branches/commits and potential storage costs of accrued OCI tags -- good points to raise.
I would love to see this. data.json is one of the banes of my life.
Is the "Deploy website from branch other than main" approach able to be implemented in the short term to trial?
I really like this idea.
@vdice @karthik2804 is there anything you need from me; testing/usage?
I think implementing a solution to the data.json file conflicts would be epic.
@tpmccallum I can revise https://github.com/fermyon/developer/pull/423 to allow deployments from branches other than main (which is possible today using the bindle-based approach, so it would be maintaining feature parity).
Apologies for having the draft PR sit so long. To utilize GHCR, which is the most convenient container registry for this purpose, it being provided/paired to this self-same repo, we need a future release of the spin cli with its oci client updated (primarily to get concurrent pushes and pulls, so we don't time out attempting to push this Developer website app, what with its many layers of static assets). @karthik2804 and I were talking about this today, actually, and we should be good to update the cli to use our fork of this oci library (see https://github.com/fermyon/oci-distribution).
Alternatively, we could utilize fermyon's DockerHub account and move this forward. This would take a bit more config (eg passing in credentials for signing in to the registry) but certainly do-able.
While we mull over the preferred registry approach, I can update the draft PR with the changes mentioned in the first paragraph above...
|
2025-04-01T06:38:40.091250
| 2023-03-07T07:41:25
|
1612901318
|
{
"authors": [
"tpmccallum"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5875",
"repo": "fermyon/developer",
"url": "https://github.com/fermyon/developer/pull/426"
}
|
gharchive/pull-request
|
Verify developer docs subdomain
Signed-off-by: tpmccallum<EMAIL_ADDRESS>
Fixed by https://github.com/fermyon/developer/pull/426
|
2025-04-01T06:38:40.100596
| 2022-06-13T03:10:34
|
1268838213
|
{
"authors": [
"ejmg",
"vdice"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5876",
"repo": "fermyon/spin",
"url": "https://github.com/fermyon/spin/pull/565"
}
|
gharchive/pull-request
|
Update Headers Env Routes Integration Test to use Rust SDK.
Following up on #534 for #216, this updates the headers-env-routes-test test binary used by spin's integrations.
Signed-off-by: elias<EMAIL_ADDRESS>
Realizing I jumped the gun because the integration is now failing. I probably won't have the time to sit down and correct the test behavior until tomorrow night or Tuesday (so apologies on my part) but my debugging seems to indicate that I entirely failed to insert the headers??? :upside_down_face:
Hi @ejmg, thank you for your help in updating tests to use the SDK. We've now closed out the issue tracking these updates (https://github.com/fermyon/spin/issues/216) and so I'll close this Draft PR. (Thanks for laying the groundwork in this PR as well!)
|
2025-04-01T06:38:40.101689
| 2024-06-14T20:31:12
|
2354048463
|
{
"authors": [
"vdice"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5877",
"repo": "fermyon/spinkube-performance",
"url": "https://github.com/fermyon/spinkube-performance/pull/70"
}
|
gharchive/pull-request
|
feat(apps): add password hasher app
Adds a password hasher app with toggles for cpu (iterations), mem usage, password value and sleep
Ok, sounds like we're fine to get this in as-is and tweak/tune as needed.
|
2025-04-01T06:38:40.103031
| 2024-05-07T13:34:25
|
2283368009
|
{
"authors": [
"abvthecity",
"dsinghvi"
],
"license": "Apache-2.0",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5878",
"repo": "fern-api/fern",
"url": "https://github.com/fern-api/fern/pull/3553"
}
|
gharchive/pull-request
|
fix: treat multipart form as form
adds a more robust way to parse and check media types (case-insensitive, and aware of parameters, i.e. charset=utf-8)
updates parseFileUploadRequest to check if the media type is a multipart formdata rather than isFile=true
@abvthecity looks like an ete test is failing, otherwise this looks great
|
2025-04-01T06:38:40.115000
| 2016-01-11T22:29:10
|
126051944
|
{
"authors": [
"cesarandreu",
"davidjamesstone",
"dcousens",
"feross",
"rstacruz"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5879",
"repo": "feross/standard",
"url": "https://github.com/feross/standard/issues/381"
}
|
gharchive/issue
|
function expression vs statement
I was wondering about folks preference in regards to expression vs statements.
Clearly it's important to understand the differences between the two in regards hoisting and also the use cases of each but there are often times where either could be used.
I can't find a recommendation - is there a guideline or for this in standardjs?
I see there's the "Enforce Function Style (func-style)" rule in ES Lint. I don't think I'm suggesting this be implemented but it would be nice to have an official line on the preferred approach.
Many thanks
Dave
Could you post some example code? Probably easier to self-parse and understand what you're referring to?
Hi Daniel,
Thanks for your reply.
I'm generally referring to 'private' helper type functions that don't have value outside of their enclosing function. Take the save function below.
Here a function expression or declaration would suffice. For consistency, which one should I opt for?
/*
* Example adding a comment with an optional replyToId
*/
function addComment (body, inReplyToId, callback) {
// Define the save function with a function declaration
function save (comment) {
comment.save(function (err) {
if (err) {
callback(err)
}
callback(null, comment)
})
}
// The above function could have been a function expression...
// var save = function (comment) {
// comment.save(function (err) {
// if (err) {
// callback(err)
// }
// callback(null, comment)
// })
// }
if (inReplyToId) {
Comment.findById(inReplyTo, function (err, doc) {
if (err) {
callback(err)
}
save(new Comment({ body: body, inReplyTo: doc.id }))
})
} else {
save(new Comment({ body: body }))
}
}
Hope this helps
Dave
I personally opt for function save, but I don't think there is a hard-rule for this in standard.
Maybe there should be.
@feross ?
xo has one. I don't mind it.
Likewise I have opted for function save () {...} in the past. This is the also the advice from Crockford.
More recently I have noticed people using var save = function () {...} quite a lot.
While I don't have a strong preference, I would like to see some consistency within code base/across teams.
More recently though I have noticed people using var save = function () {...} a lot more.
Probably because you have to use that syntax if you are using context capturing lambdas:
var save = () => {}
I use arrow functions with callbacks or when I need to preserve context.
I'm not sure this holds true anymore, since it seems most engines have improved this by now... But it used to be that the following would give you worse stack traces:
// Anonymous function
const foo = function () {}
// Could be fixed by giving it a name
const foo = function foo () {}
With babel the default behavior seems to be to name the function:
Function declarations are preferred.
Function declarations have more intuitive hoisting behavior, i.e. you can use the function anywhere that's in-scope. With function expressions, only the variable is hoisted, so you can only use the function after the line where the assignment occurs.
Just tried enabling func-style to enforce function declarations, while making an exception for arrow function expressions, and got this result:
# tests 427
# pass 331
# fail 96
Full output: https://gist.github.com/feross/0d57fdddde82f55d618a
It's a high number, so leaning toward not enabling this. Much as I like it. Maybe if we do standard-strict?
For documentation, here's the rule I tested with:
"func-style": [2, "declaration", { "allowArrowFunctions": true }]
@feross how about V6? I think it is a reasonable enough change and absolutely in the spirit of our existing rules.
@dcousens Agreed, but it's quite a bit of breakage (22% of the ecosystem).
@feross its also a break that could probably be resolved with a regex expression.
%sno/var \(\.\+\) = function \.\*(/function \1 (/gc
closing - we can move discussion of potential "next gen" or big breaking rule to the standard-strict issue: https://github.com/feross/standard/issues/382
|
2025-04-01T06:38:40.118262
| 2018-03-08T13:20:49
|
303476914
|
{
"authors": [
"feross",
"sunrize531"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5880",
"repo": "feross/typedarray-to-buffer",
"url": "https://github.com/feross/typedarray-to-buffer/issues/14"
}
|
gharchive/issue
|
Republish with updated NPM
The version of module which is currently published in npm registry appears to be affected by this npm bug:
https://github.com/npm/npm/issues/16734
Which prevents the application using this module (indirectly) from being deployed on Amazon AWS:
https://github.com/aws/aws-cli/issues/2639
Republishing the module using newer (or stable) version of npm should resolve the issue.
Installed the latest Node.js LTS and npm and republished. Hope this fixes the issue for you.
node -v
v8.10.0
npm -v
5.7.1
Published as 3.1.5.
|
2025-04-01T06:38:40.119588
| 2024-09-17T19:26:21
|
2531932153
|
{
"authors": [
"Skullians",
"Sweattypalms"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5881",
"repo": "ferrumc-rs/ferrumc",
"url": "https://github.com/ferrumc-rs/ferrumc/pull/50"
}
|
gharchive/pull-request
|
Create issue templates
Add issue templates, see https://github.com/Skullians/ferrumc/issues/new/choose for a demo.
I approve
sick
|
2025-04-01T06:38:40.135403
| 2018-01-21T23:27:18
|
290316373
|
{
"authors": [
"adbeem",
"cowboysdude",
"mikeb8319"
],
"license": "MIT",
"license_source": "github-api",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5883",
"repo": "fewieden/MMM-voice",
"url": "https://github.com/fewieden/MMM-voice/issues/20"
}
|
gharchive/issue
|
Error when starting
Platform (Hardware/OS):
Unbuntu 16
Node version:
8.9.4
MagicMirror version:
2.2.2
Module version:
Lastest Master
Description of the issue:
when starting it intializes then goes right to ERROR
When run in debug: true it says undefined.
I ran the command line and my mic is 0.....
Not sure what's undefined but I've tried the mic at 0 and 1......still get ERROR
Not sure how I missed that. Thanks, homie.
hi fewieden, i tried the two commands:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
sudo ldconfig
but nothing showed up. i check the file directory and i cant seem to find any ldconfig file (also in hidden mode). it is missing somewhere?
It starts from initializing then ready choose a mode and immediately goes to ERROR, i checked the error.log it shows 1 1 1 1 1 1 ...
|
2025-04-01T06:38:40.162306
| 2015-08-10T10:26:51
|
100029714
|
{
"authors": [
"ff-"
],
"license": "mit",
"license_source": "bigquery",
"license_type": "permissive",
"provenance": "gharchive-dolma-0000.json.gz:5884",
"repo": "ff-/markiki",
"url": "https://github.com/ff-/markiki/issues/4"
}
|
gharchive/issue
|
Markdown interpretation caching
Now every time an article gets loaded, its markdown content is compiled to html, and this makes the page flickers for a moment just after the click.
Possible solutions:
Compile the markdown to html on app loading, and cache everything (client side). Downside: long app loading time.
"Memoize" the markdown compilation, so compiling it only the first time and caching the result (client side). Downside: still flickering.
Compile everything server side. Downside: there's the possibility of having to send two copies of the data (one with html, and one without - for searching)
Is this really necessary?
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.