[turborepo] Cannot find module 'ui' or its corresponding type declarations.ts(2307)

What version of Turborepo are you using?
latest
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Windows
Describe the Bug
As the title says, I'm constantly getting this typescript error whenever I modify a simple UI component inside packages/ui - regardless if I'm running the server in dev or building or simply nothing.
Sometimes restarting the dev server and restarting typescript server in vscode fixes the issue.
I have experienced this with multiple turborepo repositories and so has my friends.
It's extremely annoying that I have to restart the dev server and typescript server several times during the development phase - in hope that it fixes the issue.
Expected Behavior
I expected the ts environment to be smart enough to understand that a UI component has changed and not throw any ts error when technically there aren't any.
To Reproduce
Create a turborepo project and modify a UI component or create your own and modify it.
Reproduction Repo
No response

Thanks for the issue @Delice0, we've seen this one before as well. I haven't been able to nail down a consistent reproduction yet that we could use to fix or take to the Typescript team. When I have seen this, restarting the Typescript Server in VSCode does fix it for me - but if you have more details, let us know!

Been experiencing this as well. sometimes works when I open package.json in the dependency library. Its bad for DX

Is this exclusive to yarn v1? Experiencing the exact same cloning the kitchen-sink example (npx create-turbo@latest -e kitchen-sink) with Yarn v1

I am also experiencing the same.
In the case of having a package and app server running concurrently, when I modify anything inside package, on the package successfully getting built, the app server throws the TS error (mostly imports not found).
To resolve it, I need to restart the app server. It's a major hit on developer productivity when having a design system under packages being used by multiple apps which need to be running together.

same issue, use pnpm@7 or pnpm@8

Thanks for the issue @Delice0, we've seen this one before as well. I haven't been able to nail down a consistent reproduction yet that we could use to fix or take to the Typescript team. When I have seen this, restarting the Typescript Server in VSCode does fix it for me - but if you have more details, let us know!

hi, https://github.com/vercel/turbo/issues/5044 This can be reproduced, just use your own example.

I'm running into the same issue on the Highlight repo.
Steps to reproduce in PowerShell:

git clone git@github.com:highlight/highlight.git && cd highlight
git submodule update --init --recursive
yarn
cd .\sdk\highlight-node\
yarn typegen

Having the same problem. Running "Typescript: Restart TS Server" fixes the problem .. but I have to run it a dozen times per day.

Having the same problem. Running "Typescript: Restart TS Server" fixes the problem .. but I have to run it a dozen times per day.

Same with me :)

Yup, happens on my project as well, was unable to figure out why.
Is there any update regarding this issue?

Happens both on VSCode and WebStorm with example kitchen-sink repo:

Was discussing this with @lfades, and he recommended using typesVersions to work around this issue:
For example:
  "typesVersions": {
    "*": {
      "*": [
        "src/*",
        "src/*/index"
      ]
    }
  },
  "publishConfig": {
    "typesVersions": {
      "*": {
        "*": [
          "dist/*.d.ts",
          "dist/*/index.d.ts"
        ]
      }
    }
  }

This ensures that:

During dev, you're TS types point to the source files, and don't have a reliance on the build process, and dist existing.
For production, the built dist outputs are still used.

This works well for multiple entry points as well, for example:
  "exports": {
    "./*": "./dist/index.*.js"
  },
  "publishConfig": {
    "typesVersions": {
      "*": {
        "*": [
          "./dist/index.*.d.ts"
        ]
      }
    }
  },
  "typesVersions": {
    "*": {
      "client": [
        "./src/client/index.client.tsx"
      ],
      "server": [
        "./src/server/index.server.ts"
      ]
    }
  },

From my own experimenting, this looks to have resolved this issue for me! We'll look into getting this ported into our examples.

Thanks @tknickman !
This worked for me!

can this update on example?

@tknickman can you please explain that a bit if possible or atleast point out some resources from where i can refer it

Still get the error even with the proposed fix. Clonning the tailwind example, just changed the package.json with the recommended fix but... nothing. Restarted TS server, etc and nope

I concur the proposed fix inconsistently resolves the problem. My temp solution that has been working is pretty low tech, basically don't run the clean step with tsup when in development and only clean in builds.
It's not ideal, but my guess with verification is it appears that maybe the clear step causes an issue with the ides or maybe the tsc server losing reference. Where when you run the build step with tsc not with tsup/esbuild there is no issue. So yeah the other option would just be to use tsc which perfect fine with small to mid size projects that don't need the boost of faster build times.
The example applications definitely need to be updated with a solution to this or at least some level of explanation from someone who knows the inner workings of all of these tools.

Same thing here, this fix don't work
turbo is able to track the dependency list correctly but wont build them in order to have the dist generated once ready to build the next dependency
libA > libB
libC > libB
libB > libD
libD should be built first in order to build libB then libA/libC in parallel

done almost all but nothing worked, can this issue be re open and fixed ?

The thing is the proposed fix, isn't a fix. It's a hack / work around to point to local files instead of the built ones for types. It has the potential to lead to inconsistent results due to not using the built assets.
Partially, I think this issue is an artifact of mixing esm/cjs projects that require being built within the same ecosystem. As the industry leans more towards pure esm this will be less of an issue.
Right now though, unless the typescript server also listens to changes and updates itself accordingly I don't think there is a solution that is just gonna work out of the box.
As for a solution, it's probably better that someone with extensive knowledge of the relevant topics documents this as a sorta "gotcha" issue and provides people with the actual issues and potential work arounds.

The proposed solution still not works on HMR. Whenever a line is changed in packages, the package rebuilds, but the app throws the same error of not finding the type declarations.

I encountered this problem when I integrated an old repository into my new turbo repo.
Config of my tsconfig package (packages/tsconfig):
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "display": "Default",
  "compilerOptions": {
    ...
    "moduleResolution": "node",
    ...
  },
  "exclude": ["node_modules"]
}

When you create a standalone NextJS project, the tsconfig will look like this:
{
  "compilerOptions": {
    ...
    "moduleResolution": "bundler",
    ...
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
  "exclude": ["node_modules"]
}

When creating the Turbo Repo, the NextJS project will have the tsconfig compilerOptions with     "moduleResolution": "node" but a standalone NextJS project has "moduleResolution": "bundler", which causes the error.
To fix:
"moduleResolution": "bundler",  ->  "moduleResolution": "node",

I was having this exact same problem with the with-tailwind example where VSCode would not be able find the ui module after a rebuild of the ui package. After some digging I discovered that the dist/index.d.ts was briefly disappearing when the ui package rebuilt. I think this problem is caused by tsup deleting dist/index.d.ts and then re-creating it. The TS server doesn't seem to be able to handle this. When I set clean: false in ./packages/ui/tsup.config.ts it now seems to work fine.

For those using vite instead of tsup this is the equivalent of @zhm's solution
import { defineConfig } from 'vite'

export default defineConfig({
  build: {
    emptyOutDir: false,
  },
  ⋮
})

You can also pass --emptyOutDir via the cli. Here's an example of my dev command:
"dev": "tsc && vite build --emptyOutDir false --watch"
Feel free to yell at me if you think I shouldn't be using Vite as my bundler for my package. I don't know what I'm doing.

If this can help, for me the fix was just replacing :
"main": "./dist/index.js",
"types": "./dist/index.d.ts"

by
"main": "./src/index.js",
"types": "./src/index.d.ts"

in packages/ui/package.json

btw i faced this issue for a very long time, for me it turned out to be

my pc had issues, i swtiched to ubuntu (just delete everything and do everything from start)
be very careful with package.json, the dependencies it has is the key to your packages
if using pnpm use pnpm workspaces then you have to add "workspace:*" for local package dependencies version
if using yarn or npm watch for root dir package.json and just use * for local package dependencies version,
https://github.com/me-imfhd/turbocell
take reference

Not sure what is happening on my case.
It works with yarn dev but does not build with yarn build
I get Cannot find module 'ui' or its corresponding type declarations.
In my ui package.json:
  ...
  main": "./dist/index.js",
  "module": "./dist/index.mjs",
  "types": "./dist/index.d.ts",
  "exports": {
    ".": "./dist",
    "./styles.css": "./dist/index.css"
  },
  "files": [
    "dist/**"
  ],
  ...

I was having this exact same problem with the with-tailwind example where VSCode would not be able find the ui module after a rebuild of the ui package. After some digging I discovered that the dist/index.d.ts was briefly disappearing when the ui package rebuilt. I think this problem is caused by tsup deleting dist/index.d.ts and then re-creating it. The TS server doesn't seem to be able to handle this. When I set clean: false in ./packages/ui/tsup.config.ts it now seems to work fine.

I set clean to false and tried restart the server but still same issue persist any alternative?

I found the problem. I had the following in my ui shared package:
...
"exports": {
  ".": "./dist",
  "./styles.css": "./dist/index.css"
},
...

Once I removed it, I could now run yarn build successfully.

In my project I have 2 packages,

typescript lib for the server(Nestjs)
ui  generated by turborepo for the front (NextJs).

Both build are ok, and in vscode I have the right references.
however :
yarn dev server ----> failed  Cannot find module lib xxxxx
yarn dev front ------> OK
I have looked into the front project closely and . I have seen in the next.config.js
module.exports = {
  reactStrictMode: true,
  transpilePackages: ["ui"],
};

Apparently the attributes transpilePackages allow you to bundle a dependency from local.  read more here

I found the problem. I had the following in my ui shared package:
...
"exports": {
  ".": "./dist",
  "./styles.css": "./dist/index.css"
},
...

Once I removed it, I could now run yarn build successfully.
However yarn dev now fails: Failed to resolve entry for package "ui". The package may have incorrect main/module/exports specified in its package.json. [plugin vite:dep-scan]
If we add the following lines to our vite.config.ts: optimizeDeps: { exclude: ['ui'] }
Now, yarn dev also runs.
References: OptimizeDeps Exclude Pre Bundling
The problem is that you need the exports in order to be able to import the styles in each app:
import 'ui/styles.css'
So, your exports in package.json will look something like:
...
"exports": {
  ".": {
    "types": "./dist/index.d.ts",
    "default": "./dist",
    "node": "./dist",
    "import": "./dist"
   },
  "./styles.css": "./dist/index.css"
},
...

If you encounter an error like "Module not found: Default condition should be last one",
remove "default": "./dist" like this.
...
"exports": {
  ".": {
     "types": "./dist/index.d.ts",
    // "default": "./dist", <= remove this
     "node": "./dist",
     "import": "./dist"
    },
   "./styles.css": "./dist/index.css"
 },
 ...

It should work fine after that.
(I was in a pnpm environment.)

i have also exported it correctly but dont know why its showing the error
can someone suggest me something

today, I was also facing the same issue,
try this

go to the root folder
run -> npm i

it worked for me, Hope will work u too.

naah that was not the issue . The issue was was not exporting as .ts
i included .ts at the end then it got resolved

Hi
I am facing this error when I try to run dev.

material-web-components-react:dev:  ELIFECYCLE  Command failed with exit code 1.
material-web-components-react:dev: ERROR: command finished with error: command (O:\Documents\GitHub\public\material-web-components-react\packages\ui) C:\Program Files\nodejs\pnpm.cmd run dev exited (1)
material-web-components-react#dev: command (O:\Documents\GitHub\public\material-web-components-react\packages\ui) C:\Program Files\nodejs\pnpm.cmd run dev exited (1)

 Tasks:    0 successful, 2 total
Cached:    0 cached, 2 total
  Time:    1.599s
Failed:    material-web-components-react#dev

 ERROR  run failed: command  exited (1)
 ELIFECYCLE  Command failed with exit code 1.```

I installed pnpm, and then ran the following commands from the root project:-
`pnpm install`
`pnpm run dev`

Am I doing something wrong? Do I need to configure anything else?

Also looking at the structure, inside the packages/ui folder, I will create a types folder and place all the type declarations there.

today, I was also facing the same issue,
try this

go to the root folder
run -> npm i

it worked for me, Hope will work u too.

for some weird reason , i tried it and it worked , whattt....

Adding that, in my case, for a just-in-time internal package shared across multiple apps in a Turborepo, I had to do the opposite of @owieth above.
I had to change from "moduleResolution": "node" to "moduleResolution": "NodeNext" (or bundler).
I have a very simplepackages/sanity-client which just exports an object shared across many of my apps, but after months of building fine began getting Module not found: Can't resolve '@repo/sanity-client' build errors.
Once I added an exports to my packages/sanity-client/package.json, I got a more helpful error:
bh-briet-market:build: Type error: Cannot find module '@repo/sanity-client' or its corresponding type declarations.
bh-briet-market:build:   There are types at<EMAIL_ADDRESS>but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.

My two apps had been set up with a default of "moduleResolution": "node",, but changing to "moduleResolution": "nodenext", (or bundler, depending on your taste for file extensions) was the key, along with adding
"exports": {
  "default": "./main.ts"
},

to my packages/sanity-client/package.json.


Fixed issue #351

PR Fixes: #351

Before:

After:

Resolves #351
Checklist before requesting a review

[x] I have performed a self-review of my code
[ ] I assure there is no similar/duplicate pull request regarding same issue

Something going wrong with the yarn.lock file, I will restart the process


MAINT: remove broken/legacy doctests from _intersection.pyx

These doctests were written to work with the bx-python intersection code before it was ported to scikit-bio (import paths are incorrect). After fixing imports, the doctests don't work in Python 3 due to unordered dict repr.
I'm removing the doctests instead of fixing because they are documenting package-private Cython code. For some reason, doctests in .pyx files aren't executed in Travis-CI tests, nor in source installs from PyPI. They are executed when running tests on a conda-built package, so I only noticed the failing doctests after I had built the 0.5.1 conda release.
If doctests in .pyx code is desirable in the future, we'll need to make sure those tests are executed by Travis-CI in order to catch any failing tests before releasing.

@RNAer or @ebolyen, could one of you guys review?

Thanks for looking into this! Did those doctests cause any travis error/test failure? I view them as valuable to demo the usage and they helped me understand the code a lot.
BTW, I did a quick google and see the work around for pyx doctest here: https://github.com/cython/cython/wiki/FAQ#how-can-i-run-doctests-in-cython-code-pyx-files

Did those doctests cause any travis error/test failure? I view them as valuable to demo the usage and they helped me understand the code a lot.

See what I wrote above:

For some reason, doctests in .pyx files aren't executed in Travis-CI tests, nor in source installs from PyPI. They are executed when running tests on a conda-built package, so I only noticed the failing doctests after I had built the 0.5.1 conda release.

Thanks for the link to getting Cython doctests to execute. I don't have bandwidth to get these tests running in Travis-CI and PyPI source installs. For now I recommend removing the doctests b/c they are failing and we don't have a way to verify them until the conda package has been built (and at that point in the release process, it is a major pain to go back and fix the tests). IMO it's better to remove them until the problem is solved generally, in case there's another release in the meantime.
It'd be great to solve this generally so .pyx doctests are discovered and verified like the other .py doctests. I created an issue to track progress on this: https://github.com/biocore/scikit-bio/issues/1458

yeah, I had seen you said it failed in conda build. I assume you get the doctest error when checking the build in the test section in the recipe? As long as all the travis and test pass, to check the conda build success, I think it is safe to run nosestests without --with-doctest to skip the doctest? Anyway, this is minor and I am ok with deleting them now.

I assume you get the doctest error when checking the build in the test section in the recipe?

No, the conda build (including whatever tests conda runs) is successful. The failing tests are only discovered and executed after installing scikit-bio from conda and running python -m skbio.test.

As long as all the travis and test pass, to check the conda build success, I think it is safe to run nosestests without --with-doctest to skip the doctest?

Travis is not running those doctests, so we don't see failures until the conda package is built and tested with the command I posted above. python -m skbio.test doesn't have an option to turn off doctests. Even if it did, I don't think that's the right solution here -- all doctests in the codebase (defined in .py and .pyx files) need to be executed during the Travis-CI build, otherwise broken doctests will make it into the codebase and be discovered much later on, when it is too late to go back and fix them (i.e. like what happened last night when I cut the release).

Anyway, this is minor and I am ok with deleting them now.

I will leave this up to you -- if the broken tests are left in the codebase, we'll need to fix them and resolve #1458 before the next release. I don't have bandwidth to do that but if you have time it would be nice to get that fixed.

I can try to fix it before the next release, which is ~5 months away? from what I can see from the past release cycle.

We don't really have a scheduled release cycle. I relabeled #1458 as "blocking" because those issues always get fixed before releases. Do you want me to close this PR and assign #1458 to you?

That sounds good.
On Mon, Nov 14, 2016 at 8:25 AM, Jai Ram Rideout<EMAIL_ADDRESS>wrote:

We don't really have a scheduled release cycle. I relabeled #1458
https://github.com/biocore/scikit-bio/issues/1458 as "blocking" because
those issues always get fixed before releases. Do you want me to close this
PR and assign #1458 https://github.com/biocore/scikit-bio/issues/1458
to you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/scikit-bio/pull/1457#issuecomment-260383681,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA9CeHVENKYeuT34KqAyQmKfeNPt7x6Sks5q-It-gaJpZM4Kww8_
.

Done, thanks!


Uglifying and styling errors

I have been working through getting FuseBox working it has been stressful but I am nearly there. Below is a screenshot of the error(s) i am getting.
I am getting a weird → WARNING Ignoring local @import of "/css-resources/281877879.css" as resource is missing. and the more obvious → Error during uglifying app

Here is my code/gist
Things I have tried:

I have tried using uglify-es.
I updated the version of uglify-js and -es to match in my package.json and the package.json in fuse-box/node_modules.
Deleting .fusebox folder (which I do in my clean task anyway)

Things I am thinking it might be related too:

my use of $(__dirname) messing around with paths?
uglify-js (or -es) specific error? Though I did uglify-js manually in my terminal with the following command uglifyjs app.js -c -m -o app.min.js on my unoptimised/non-production output and it worked.
fuse-box bug

Not sure what the issue might be and not sure on how to do the following:

get uglify-js error or log information
tell what options fuse-box uses to uglify
determine why the ignoring local @import css bug is occuring but my styles still builds

any help would be amazing! This has been much more stressful than it should have been unfortunately and don't really want to turn around and go back to webpack just because these two (what I hope are the last ones) errors are causing me grief :(
I will update the lists and scratch off ones i try
Edit
Just to test I added what is definitely newer than es5 code to my playground app below.
const ComponentTest = (props) => {
    return (
{props.test.toString()}{props.tests}
)
}

class App extends React.Component<{}, {}>
{
    public render()
    {
        const spreadstuff = {
            test: 5,
            tests: "test"
        };
        return

Hello World<ComponentTest {...spreadstuff}/>
<Login />
;
    }
}

and it compiled and uglyfied perfectly fine whether I set it to sue uglify-js or uglify-es, with pretty much the exact same (very very close) fuse.ts file to my main project.

So I removed that Env variable as a test and got the exact same error (including the line, col, pos).
Is there a way to have that IMAGE_PATH use absolute path as it is needed? Maybe definedExpressions?
Also any idea about the css issue aswell?

CSSResourcePlugin can't resolve your path that's the problem

Oh so after some thorough research last night it seems to be erroring on this code in my Constants file
Bundle code parsed to uglify
var Constants = function () {
    function Constants() {
        this.wholesalerSettings = [object Object];
        this.API = this.setHostUrl();
    }

Actual Code before build
    constructor() {
        this.wholesalerSettings = process.env.WHOLESALERSETTINGS;
        this.API = this.setHostUrl();
    }

Where I set WHOLESALERSETTINGS in Fuse.ts
EnvPlugin({
    WHOLESALERSETTINGS: this.wholesalerSettings,
    IMAGE_PATH: `./src/~/wholesalers/${this.wholesaler}/images/`
}),

So what is the correct way to have those global variables used?


Clueless on gradle and java, trying to make this work

We have an install of swagger2markup that generates HTML via adoc.  I am trying to make it generate markdown (just to evaluate).  I have no idea how.  I have no experience in Java / Gradle this and all my hacks have failed.  Any clues you can offer would be appreciated.
build.gradle:
buildscript {
    repositories {
        mavenLocal()
        jcenter()
    }

    dependencies {
        classpath 'io.github.robwin:swagger2markup:0.8.0'
    }
}

task gendocs << {
  io.github.robwin.swagger2markup.Swagger2MarkupConverter
    .from("./input.json")
    .withMarkupLanguage(MarkupLanguage.MARKDOWN)
    .build()
    .intoFolder("./");
  println '*** generating docs to ./'
}

errors:
Selected primary task 'gendocs' from project :
Tasks to be executed: [task ':gendocs']
:gendocs (Thread[main,5,main]) started.
:gendocs
Executing task ':gendocs' (up-to-date check took 0.002 secs) due to:
  Task has not declared any outputs.
reading from ./input.json
no property for v1.Binding, null
no property for v1.Binding, null
no property for v1.ComponentStatusList, null
no property for v1.ComponentStatus, null
no property for v1.EndpointsList, null
no property for v1.Endpoints, null
no property for v1.Endpoints, null
no property for json.WatchEvent, null
no property for v1.Endpoints, null
no property for v1.Endpoints, null
no property for v1.Endpoints, null
no property for unversioned.Patch, null
no property for v1.Endpoints, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.EndpointsList, null
no property for json.WatchEvent, null
no property for v1.EventList, null
no property for v1.Event, null
no property for v1.Event, null
no property for json.WatchEvent, null
no property for v1.Event, null
no property for v1.Event, null
no property for v1.Event, null
no property for unversioned.Patch, null
no property for v1.Event, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.EventList, null
no property for json.WatchEvent, null
no property for v1.LimitRangeList, null
no property for v1.LimitRange, null
no property for v1.LimitRange, null
no property for json.WatchEvent, null
no property for v1.LimitRange, null
no property for v1.LimitRange, null
no property for v1.LimitRange, null
no property for unversioned.Patch, null
no property for v1.LimitRange, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.LimitRangeList, null
no property for json.WatchEvent, null
no property for v1.NamespaceList, null
no property for v1.Namespace, null
no property for v1.Namespace, null
no property for json.WatchEvent, null
no property for v1.Namespace, null
no property for v1.Namespace, null
no property for v1.Namespace, null
no property for unversioned.Patch, null
no property for v1.Namespace, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.Namespace, null
no property for v1.Namespace, null
no property for v1.Namespace, null
no property for v1.Namespace, null
no property for v1.NodeList, null
no property for v1.Node, null
no property for v1.Node, null
no property for json.WatchEvent, null
no property for v1.Node, null
no property for v1.Node, null
no property for v1.Node, null
no property for unversioned.Patch, null
no property for v1.Node, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.Node, null
no property for v1.Node, null
no property for v1.PersistentVolumeClaimList, null
no property for v1.PersistentVolumeClaim, null
no property for v1.PersistentVolumeClaim, null
no property for json.WatchEvent, null
no property for v1.PersistentVolumeClaim, null
no property for v1.PersistentVolumeClaim, null
no property for v1.PersistentVolumeClaim, null
no property for unversioned.Patch, null
no property for v1.PersistentVolumeClaim, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.PersistentVolumeClaimList, null
no property for json.WatchEvent, null
no property for v1.PersistentVolumeClaim, null
no property for v1.PersistentVolumeClaim, null
no property for v1.PersistentVolumeList, null
no property for v1.PersistentVolume, null
no property for v1.PersistentVolume, null
no property for json.WatchEvent, null
no property for v1.PersistentVolume, null
no property for v1.PersistentVolume, null
no property for v1.PersistentVolume, null
no property for unversioned.Patch, null
no property for v1.PersistentVolume, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.PersistentVolume, null
no property for v1.PersistentVolume, null
no property for v1.PodList, null
no property for v1.Pod, null
no property for v1.Pod, null
no property for json.WatchEvent, null
no property for v1.Pod, null
no property for v1.Pod, null
no property for v1.Pod, null
no property for unversioned.Patch, null
no property for v1.Pod, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.PodList, null
no property for json.WatchEvent, null
no property for v1.Binding, null
no property for v1.Binding, null
no property for *int64, null
no property for *unversioned.Time, null
no property for *int64, null
no property for *int64, null
no property for v1.Pod, null
no property for v1.Pod, null
no property for v1.Pod, null
no property for v1.PodTemplateList, null
no property for v1.PodTemplate, null
no property for v1.PodTemplate, null
no property for json.WatchEvent, null
no property for v1.PodTemplate, null
no property for v1.PodTemplate, null
no property for v1.PodTemplate, null
no property for unversioned.Patch, null
no property for v1.PodTemplate, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.PodTemplateList, null
no property for json.WatchEvent, null
no property for v1.ReplicationControllerList, null
no property for v1.ReplicationController, null
no property for v1.ReplicationController, null
no property for json.WatchEvent, null
no property for v1.ReplicationController, null
no property for v1.ReplicationController, null
no property for v1.ReplicationController, null
no property for unversioned.Patch, null
no property for v1.ReplicationController, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.ReplicationControllerList, null
no property for json.WatchEvent, null
no property for v1.ReplicationController, null
no property for v1.ReplicationController, null
no property for v1.ResourceQuotaList, null
no property for v1.ResourceQuota, null
no property for v1.ResourceQuota, null
no property for json.WatchEvent, null
no property for v1.ResourceQuota, null
no property for v1.ResourceQuota, null
no property for v1.ResourceQuota, null
no property for unversioned.Patch, null
no property for v1.ResourceQuota, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.ResourceQuotaList, null
no property for json.WatchEvent, null
no property for v1.ResourceQuota, null
no property for v1.ResourceQuota, null
no property for v1.SecretList, null
no property for v1.Secret, null
no property for v1.Secret, null
no property for json.WatchEvent, null
no property for v1.Secret, null
no property for v1.Secret, null
no property for v1.Secret, null
no property for unversioned.Patch, null
no property for v1.Secret, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.SecretList, null
no property for json.WatchEvent, null
no property for v1.ServiceAccountList, null
no property for v1.ServiceAccount, null
no property for v1.ServiceAccount, null
no property for json.WatchEvent, null
no property for v1.ServiceAccount, null
no property for v1.ServiceAccount, null
no property for v1.ServiceAccount, null
no property for unversioned.Patch, null
no property for v1.ServiceAccount, null
no property for v1.DeleteOptions, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.ServiceAccountList, null
no property for json.WatchEvent, null
no property for v1.ServiceList, null
no property for v1.Service, null
no property for v1.Service, null
no property for json.WatchEvent, null
no property for v1.Service, null
no property for v1.Service, null
no property for v1.Service, null
no property for unversioned.Patch, null
no property for v1.Service, null
no property for unversioned.Status, null
no property for json.WatchEvent, null
no property for v1.ServiceList, null
no property for json.WatchEvent, null
no property for void, null
WARNING!  No property detected!  Falling back to string!
no property for null, null
no property for null, null
no property for any, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for any, null
no property for any, null
no property for any, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for any, null
no property for null, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for any, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for null, null
no property for any, null
no property for null, null
no property for null, null
:gendocs FAILED
:gendocs (Thread[main,5,main]) completed. Took 0.89 secs.

FAILURE: Build failed with an exception.

* Where:
Build file '/build/build.gradle' line: 13

* What went wrong:
Execution failed for task ':gendocs'.
> Could not find property 'MarkupLanguage' on task ':gendocs'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.

BUILD FAILED

Total time: 22.728 secs

Hi, have a look at https://swagger2markup.readme.io/docs/gradle-plugin
It shows how to configure and apply the Gradle plugin.
But if you don't want to use Gradle at all, you can also use the community-contributed Command Line Interface https://swagger2markup.readme.io/docs/cli
If you use and like Swagger2markup, I would love to get your GitHub Star.

I think I will create a Java App with an Rest Api and deploy it on heroku soon, so that people dont have to set-up an build environments.

Those all sound like options, but I am trying to be surgical (1 line change
to an extant workflow).  Is there something I am doing wrong?
a REST API sounds pretty nice, though...
On Sat, Oct 24, 2015 at 12:55 AM, Robert Winkler<EMAIL_ADDRESS>wrote:

Hi, have a look at https://swagger2markup.readme.io/docs/gradle-plugin
It shows how to configure and apply the Gradle plugin.
But if you don't want to use Gradle at all, you can also use the
community-contributed Command Line Interface
https://swagger2markup.readme.io/docs/cli
If you use and like Swagger2markup, I would love to get your GitHub Star.
—
Reply to this email directly or view it on GitHub
https://github.com/Swagger2Markup/swagger2markup/issues/40#issuecomment-150773489
.

Try
convertSwagger2markup {
inputDir file('src/docs/swagger')
markupLanguage MarkupLanguage.MARKDOWN
}

I apologize - this is LITERALLY the first time I have ever looked at
gradle.  Is that a block in the build.gradle?  How do I invoke it?
my existing gradle block is
task gendocs << {
  io.github.robwin.swagger2markup.Swagger2MarkupConverter
    .from("./input.json")
    .build()
    .intoFolder("./");
  println '*** generating docs to ./'

I need to make sure any change is the equivalent.
Adding .withMarkupLanguage(MarkupLanguage.MARKDOWN) in the middle is not
working
On Sat, Oct 24, 2015 at 1:06 AM, Robert Winkler<EMAIL_ADDRESS>wrote:

Try
convertSwagger2markup {
inputDir file('src/docs/swagger')
markupLanguage MarkupLanguage.MARKDOWN
}
—
Reply to this email directly or view it on GitHub
https://github.com/Swagger2Markup/swagger2markup/issues/40#issuecomment-150773806
.

I figured it out!  Thanks.
task gendocs << {
  io.github.robwin.swagger2markup.Swagger2MarkupConverter
    .from("./input.json")
    .withMarkupLanguage(io.github.robwin.markup.builder.MarkupLanguage.MARKDOWN)
    .build()
    .intoFolder("./");
  println '*** generating docs to ./'
}

Gradle has aa Gradle wrapper https://docs.gradle.org/current/userguide/gradle_wrapper.html to invoke Gradle scripts. Add the following to your script
task wrapper(type: Wrapper) {
    gradleVersion = '2.0'
}

Invoke the task with gradle wrapper and then always use gradlew instead of gradle to run tasks.
Then add the following to your buildscript
buildscript {
    repositories {
        jcenter()
    }

    dependencies {
        classpath 'io.github.robwin:swagger2markup:0.8.0'
    }
}
apply plugin: 'io.github.robwin.swagger2markup'

convertSwagger2markup {
    inputDir file('src/docs/swagger')
    markupLanguage MarkupLanguage.MARKDOWN
}

The apply plugin adds a tasks called convertSwagger2markup to your script which can be run with:
gradlew convertSwagger2markup
You can configure the tasks with
convertSwagger2markup{
//See documentation
}

Is it possible to invoke the Swagger2markup CLI from Go?
A Go Swagger2markup client/adapter would be nice :)


AzureStack Update Powershell for API2021-07-01

AzureStack Update Powershell for API2021-07-01

This is for squash of
https://github.com/Azure/azurestack-powershell/pull/153

/azp run


Test PR: Use dirhtml builder to see if #1407 works

Testing #1407 with dirhtml builder enabled

The test indicates that .html is trimmed. I'm not sure if the Canonical URL on PR builds is supposed to point to the stable branch, but it seems like a good idea to avoid search indexing PR builds.

I am noticing that sphinx itself would have the same issue here: https://github.com/sphinx-doc/sphinx/blob/master/sphinx/themes/basic/layout.html#L132
Probably best to use a mixture of https://www.sphinx-doc.org/en/master/development/templating.html#file_suffix
and https://www.sphinx-doc.org/en/master/development/templating.html#pagename

@Blendify responded here: https://github.com/readthedocs/sphinx_rtd_theme/pull/1407#issuecomment-1385266816


Page is no longer the descendant of top-level section in v0.69.0

What version of Hugo are you using (hugo version)?

$ hugo version
Hugo Static Site Generator v0.69.0/extended linux/amd64 BuildDate: unknown

Does this issue reproduce with the latest release?
Yes.

{{ $sectionPage := .CurrentSection }}
{{ $.Scratch.Delete "pages" }}

{{ range $.Site.RegularPages }}
    {{ if (.IsDescendant $sectionPage) }}
        {{ $.Scratch.Add "pages" (slice .) }}
    {{ end }}
{{ end }}

{{ $pages := $.Scratch.Get "pages" }}
{{ $pages }}

I think this may be related to #7096.
Downstream issue https://github.com/reuixiy/hugo-theme-meme/issues/116#issuecomment-614369427 (Non-English).
Related code:

tree-sections.html
list.html

Seems fixed in v0.69.2.


[py2py3] Check unittests from Slice 17 in py3

Intro
We need to make sure that the work done in the migration slices
is py3 compatible. In particular, we should make sure that the
unittests that are involved in each slice do not fail.
The schedule for this validation / bug-fixing campaign is kept at #10422
Details
This issue is about checking that the unittests from Slice 17,
issue #10141 and PR #10329, do not fail.
A non-exhaustive list of the ut that need to pass is
# ok
test/python/WMCore_t/WMSpec_t/WMWorkload_t.py
test/python/WMCore_t/Storage_t/StageOutMgr_t.py
test/python/WMCore_t/FwkJobReport_t/Report_t.py

#fixed
test/python/WMCore_t/WMRuntime_t/SandboxCreator_t.py
test/python/WMCore_t/WMRuntime_t/Tools_t/Scram_t.py

# env python problem
test/python/WMCore_t/ResourceControl_t/ResourceControl_t.py

# broken
test/python/WMCore_t/WorkQueue_t/WMBSHelper_t.py

test/python/WMCore_t/WMRuntime_t/Scripts_t/SetupCMSSWPset_t.py

# broken in py2 also
test/python/WMCore_t/WMRuntime_t/Scripts_t/UnpackUserTarball_t.py

broken:

[ ] test/python/WMCore_t/WorkQueue_t/WMBSHelper_t.py:WMBSHelper.testDuplicateSubscription

@amaltaro I have a question. Did we solve the problem that in py3 environment /usr/bin/env python loads py2.7?
Because in test/python/WMCore_t/ResourceControl_t/ResourceControl_t/ResourceControlTest.py:testInsertSite we call bin/wmagent-resource-control which starts with /usr/bin/env python. It fails when it tries to import os, since new os uses yield from syntax which was not available in py2.
If in bin/wmagent-resource-control i use /usr/bin/env python3, then the unittest succeeds.

Hmm, that should have been fixed at the build time, here: https://github.com/cms-sw/cmsdist/blob/comp_gcc630/wmagentpy3.spec#L29
And indeed it is:
[dmwm@38bb52cc0311 ~]$ head -n1 ./unittestdeploy/wmagent/1.4.9.pre6/sw/slc7_amd64_gcc630/cms/wmagentpy3/1.4.9.pre6/bin/wmagent-resource-control
#!/usr/bin/env python3

the problem is that we actually clone the repository and execute tests on top of it, without any modifications.
So we either have to:
a) migrate those scripts to python3 shebang line
b) have another script that somehow fixes those in our docker container and in jenkins
c) or, perhaps have some sort of symlink/alias from python pointing to the python3 binary. In a py3 environment.
I believe option c) would be the best, but I do not know whether it's recommended to do so and how precisely to make it :-)

Thanks for the answer! Now I see, this has been fixed in the deployment, but not in our dev environments. This is good to know!
suggestion for our dev environment
Changing what python points to in our docker is not advisable, it breaks tools like yum.
Changing all the shebangs lines will break the unittest in py2.
What we can do, though, is to change how we call those scripts. Instead of calling those scripts directly with
./path/to/myscrypt # starts with #!/usr/bin/env python

we can use
python3 ./path/to/myscript

This is working in my unittests at the moment. Instead of getting fixing the env to exactly the default we need, we can ask the runtime we want to run our scripts. The scripts are not changed and continue working in py2 as expected.


Unpropagated state in Succession

        circle = Circle()
        self.play(Succession(
            ApplyMethod(circle.move_to, 3*RIGHT),
            ApplyMethod(circle.move_to, 3*UP),
        ))

I expect this to move the circle first to the right, then diagonally up and left. However, it jumps back to the origin and moves up from there. This wouldn't be surprising if the implementation of Succession did not contain some state propagation mechanism (animation/composition.py:68-82) whose job is to initialize the second animation with the final state of the first. But to my eyes, something in that piece of code does not work correctly.
(The workaround to use successive play calls is not an option, as I am working on an animation class Draw that traces a pencil over a sequence of paths, while also moving the pen in between. So the succession of animations must be generated programatically.)

You can try:
self.play(circle.move_to, 3*RIGHT,
             circle.move_to, 3*UP)

Looking at the comment for Succession
https://github.com/3b1b/manim/blob/465951ab88211e4a07e1a17b7ad370cb662f7d06/animation/composition.py#L35-L46
I think what you want to do is
circle = Circle()
self.play(Succession(
    ApplyMethod, circle.move_to, 3*RIGHT,
    ApplyMethod, circle.move_to, 3*UP,
))

But this still strikes me as unexpected behavior, as I would expect this to move right, then move up from the right-shifted position.

But this still strikes me as unexpected behavior, as I would expect this to move right, then move up from the right-shifted position.

I was confusing move_to() with shift(), so it's actually working as expected. That said, the code for Succession does seem needlessly complicated for a comparatively simple effect. I'll have to look into simplifying it somehow.

I found a way to make it work, writing a wrapper class ScheduledAnimation that initializes the wrapped animation just in time, in update(0). This required suppressing premature update calls upon initialization through the introduction of an 'update_on_init' flag.
I still need to test this solution properly.  I'll keep you posted whether it does.

This is now fixed.


Dropdown: When clicking to close a dropdown, it fires "click" and "blur" events

This issue happens when controlling manually (via states) the status of a dropdown.
Steps
If you click the "Not ok button" to close the drop-down you will notice that it triggers the click and blur events (It shouldn't fire blur cause I'm still inside the component).
Now, if you click the "ok button" repeatedly, you will notice that only the click event is fired, regardless if the dropdown is opening or closing, and the blur happens only when you actually click outside of the related button, as expected.
Expected Result
When clicking the "not ok button" to close a drop-down, it should fire only a click event.
Actual Result
When clicking the "not ok button" to close a drop-down, it fires a click and blur event.
Version
0.78.3
OS: High Sierra
Testcase
https://codesandbox.io/s/3q781mpvw1

Thanks for the report and test case.  Here's our problem in Dropdown.js, the close handler is explicitly calling blur
handleClose = () => {
  debug('handleClose()')
  const hasSearchFocus = document.activeElement === this.searchRef
  const hasDropdownFocus = document.activeElement === this.ref
  const hasFocus = hasSearchFocus || hasDropdownFocus
  // https://github.com/Semantic-Org/Semantic-UI-React/issues/627
  // Blur the Dropdown on close so it is blurred after selecting an item.
  // This is to prevent it from re-opening when switching tabs after selecting an item.
  if (!hasSearchFocus) {
    this.ref.blur()
  }

  // We need to keep the virtual model in sync with the browser focus change
  // https://github.com/Semantic-Org/Semantic-UI-React/issues/692
  this.setState({ focus: hasFocus })
}

I believe the culprit is #627 (see inline comments in code above).  Rather than blurring the Dropdown to prevent the issue noted, it seems we should be detecting when the browser tab is switched back and no reopen.  I'd investigate which methods are being called when the browser tab is switched away and back.  That process needs to not re-open the Dropdown AND we should retain its focus.

I deleted
if (!hasSearchFocus) {
    this.ref.blur()
  }

from Dropdown.js and it fires only the click event.  Also, #627 seems to be unaffected.  I'll write some tests and issue a pull request

If I am missing something please let me know! Thanks

I have a pull request at #2776


502 Bad Gateway with Docker Image

On a Mac running OSX 10.11 I install and run the docker container running the commands in the docs:
When I docker run with the commands from the docs I see the following when the server starts up:
2017-02-09 03:43:00.606718 [-] Traceback (most recent call last):
2017-02-09 03:43:00.606898 [-]   File "/app/slyd/bin/slyd", line 28, in <module>
2017-02-09 03:43:00.607311 [-]     splash.server.main(server_factory=make_server, argv=[])
2017-02-09 03:43:00.607807 [-]   File "/usr/local/lib/python2.7/dist-packages/splash/server.py", line 372, in main
2017-02-09 03:43:00.608503 [-]     server_factory=server_factory,
2017-02-09 03:43:00.608762 [-]   File "/usr/local/lib/python2.7/dist-packages/splash/server.py", line 291, in default_splash_server
2017-02-09 03:43:00.609236 [-]     argument_cache_max_entries=argument_cache_max_entries,
2017-02-09 03:43:00.609671 [-]   File "/app/slyd/bin/slyd", line 25, in make_server
2017-02-09 03:43:00.610124 [-]     'docroot': opts.root}))
2017-02-09 03:43:00.610556 [-]   File "/app/slyd/slyd/tap.py", line 88, in makeService
2017-02-09 03:43:00.610973 [-]     root = create_root(config, settings_module)
2017-02-09 03:43:00.611358 [-]   File "/app/slyd/slyd/tap.py", line 61, in create_root
2017-02-09 03:43:00.611821 [-]     for file_name in listdir(config['docroot']):
2017-02-09 03:43:00.612268 [-] OSError: [Errno 2] No such file or directory: '/app/portiaui/dist'
Performing system checks...

System check identified no issues (0 silenced).

You have 12 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): auth, contenttypes, db_repo, sessions.
Run 'python manage.py migrate' to apply them.

February 09, 2017 - 03:43:01
Django version 1.10.1, using settings 'portia_server.settings'
Starting development server at http://<IP_ADDRESS>:8000/
Quit the server with CONTROL-C.

When trying to connect to localhost:9001 I get a 502 error from nginx when trying to connect to the root and I get a 404 when trying to connect to http://localhost:9001/static/index.html

@justnoise Can you try using the new instructions and scripts here: https://github.com/scrapinghub/portia/pull/700

Hi @ruairif.  Thanks for taking a look at this issue!
I tried the instructions that use the scrapinghub/portia container.  When connecting to http://localhost:9001 I get a 404.  When connecting to http://localhost:9001/static/index.html I get a traceback that shows that it can't connect to MySQL (mysql.connector.errors.InterfaceError: 2003: Can't connect to MySQL server on '<IP_ADDRESS>:3306' (111 Connection refused)).  That isn't too surprising since the container isn't running MySQL.
I'm going to give a shot at the updated instructions for Vagrant and running locally.  Let me know if I can get you additional information or do anything else to help.

@justnoise Can you give me the full traceback for the MySQL issue?

Hi @ruairif
I checkout the branch update_installation, in order to get the changes you proposed in https://github.com/scrapinghub/portia/pull/700/files for the Dockerfile.
I built using: docker build -t portia:2 . which seemed to work nice. I then run it using docker run -it --rm -v /tmp:/app/data/projects:rw -p 9001:9001 portia:2 which gives me the following output:
+ action=
+ shift
+ '[' -z '' ']'
+ _run
+ service nginx start
+ _set_env
+ path=/app/portia_server:/app/slyd:/app/slybot
+ export PYTHONPATH=/app/portia_server:/app/slyd:/app/slybot
+ PYTHONPATH=/app/portia_server:/app/slyd:/app/slybot
+ echo /app/portia_server:/app/slyd:/app/slybot
/app/portia_server:/app/slyd:/app/slybot
+ /app/portia_server/manage.py runserver
+ /app/slyd/bin/slyd -p 9002 -r /app/portiaui/dist
2017-02-17 12:55:58+0000 [-] Log opened.
2017-02-17 12:55:58.596842 [-] Splash version: 2.3.1
2017-02-17 12:55:58.597805 [-] WARNING: Lua scripting is not available because 'lupa' Python package is not installed
2017-02-17 12:55:58.598003 [-] Qt 5.5.1, PyQt 5.5.1, WebKit 538.1, sip 4.17, Twisted 16.1.1
2017-02-17 12:55:58.598452 [-] Python 2.7.6 (default, Oct 26 2016, 20:30:19) [GCC 4.8.4]
2017-02-17 12:55:58.598912 [-] Open files limit: 1048576
2017-02-17 12:55:58.599171 [-] Can't bump open files limit
2017-02-17 12:55:58.824787 [-] Xvfb is started: ['Xvfb', ':40910119', '-screen', '0', '1024x768x24']
2017-02-17 12:56:00.500999 [-] Traceback (most recent call last):
2017-02-17 12:56:00.501414 [-]   File "/app/slyd/bin/slyd", line 28, in <module>
2017-02-17 12:56:00.502279 [-]     splash.server.main(server_factory=make_server, argv=[])
2017-02-17 12:56:00.502794 [-]   File "/usr/local/lib/python2.7/dist-packages/splash/server.py", line 372, in main
2017-02-17 12:56:00.503494 [-]     server_factory=server_factory,
2017-02-17 12:56:00.503963 [-]   File "/usr/local/lib/python2.7/dist-packages/splash/server.py", line 291, in default_splash_server
2017-02-17 12:56:00.504556 [-]     argument_cache_max_entries=argument_cache_max_entries,
2017-02-17 12:56:00.504918 [-]   File "/app/slyd/bin/slyd", line 25, in make_server
2017-02-17 12:56:00.505359 [-]     'docroot': opts.root}))
2017-02-17 12:56:00.505737 [-]   File "/app/slyd/slyd/tap.py", line 88, in makeService
2017-02-17 12:56:00.506152 [-]     root = create_root(config, settings_module)
2017-02-17 12:56:00.506541 [-]   File "/app/slyd/slyd/tap.py", line 61, in create_root
2017-02-17 12:56:00.506967 [-]     for file_name in listdir(config['docroot']):
2017-02-17 12:56:00.507436 [-] OSError: [Errno 2] No such file or directory: '/app/portiaui/dist'
Performing system checks...

System check identified no issues (0 silenced).

You have 12 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): auth, contenttypes, db_repo, sessions.
Run 'python manage.py migrate' to apply them.

February 17, 2017 - 12:56:01
Django version 1.10.5, using settings 'portia_server.settings'
Starting development server at http://<IP_ADDRESS>:8000/

When I try to browse to localhost:9001 I still get a 502 Bad Gateway error. And pointing it to http://localhost:9001/static/index.html gives me a 404, just as @justnoise experienced.

You are missing the assets. I've described the full process here: https://github.com/scrapinghub/portia/issues/701#issuecomment-280086657
I'll update the PR to match those instructions if they work for you too

Thank you very much! That did the trick!
Here are the full steps I did to make it work!

mkdir portia
cd portia
git clone https://github.com/scrapinghub/portia.git
cd portia
git checkout update_installation
mkdir ~/data
cd portiaui
npm install && bower install
cd node_modules/ember-cli && npm install && cd ../../ && ember build
cd ..
docker build -t portia:v1 .
docker run -i -t --rm -p 9001:9001 -v ~/data:/app/data/projects ~/portia/portia/portiaui/dist:/app/portiaui/dist portia:v1
Point a browser to localhost:9001

Portia can now be installed and run with docker simply by running:
docker run -v ~/portia_projects:/app/data/projects:rw -p 9001:9001 scrapinghub/portia


Add support for branches in consumer version selectors

The Pact Broker now supports branches as first class entities. You can read more about this here: https://docs.pact.io/pact_broker/branches
Description
Please add support for specifying branch related properties in the consumer version selectors that are sent to the Pact Broker when requesting pacts to verify. Please do not do any verification of the consumer version selectors on the client side - the validation rules are subject to change. Just ensure that any error response is displayed to the user.

For implementations that wrap the pact-ruby-standalone, update to the latest standalone version
For implementations that use the rust implementation, update to the latest rust version.
Add a String branch property to the consumer version selector (if there is a domain model for this).
Add a Boolean mainBranch (or main_branch for snake case languages) property consumer version selector (if there is a domain model for this).
Add a Boolean matchingBranch (or matching_branch for snake case languages) property consumer version selector (if there is a domain model for this).
Expose and document the branch, mainBranch (or main_branch for snake case languages) and matchingBranch (or matching_branch) properties in the user facing API.
Pass the branch, mainBranch and matchingBranch (must be camelcase) through to the relevant implementation (ruby and/or rust)

Verifying the changes

Publish test pacts to the test broker

export PACT_BROKER_BASE_URL="https://test.pact.dius.com.au"
export PACT_BROKER_USERNAME="dXfltyFMgNOFZAxr8io9wJ37iUpY42M"
export PACT_BROKER_PASSWORD="O5AIZWxelWbLvqMd8PkAVycBJh2Psyg1"

docker run --rm  \
  -e PACT_BROKER_BASE_URL  \
  -e PACT_BROKER_USERNAME  \
  -e PACT_BROKER_PASSWORD  \
  pactfoundation/pact-cli:<IP_ADDRESS> \
  publish \
  /pact/example/pacts \
  --consumer-app-version fake-git-sha-for-demo-$(date +%s) \
  --branch main

docker run --rm  \
  -e PACT_BROKER_BASE_URL  \
  -e PACT_BROKER_USERNAME  \
  -e PACT_BROKER_PASSWORD  \
  pactfoundation/pact-cli:<IP_ADDRESS> \
  publish \
  /pact/example/pacts \
  --consumer-app-version fake-git-sha-for-demo-$(date +%s) \
  --branch feat/x

Using your pact client library, verify { "mainBranch": true }

You should receive the main pact

Using your pact client library, verify { "branch": "feat/x" }

You should receive the feat/x pact

Using your pact client library, verify { "matchingBranch": true } with the provider branch set to feat/x

You should receive the feat/x pact

added, but needs testing

@bethesque is there a reason you'd like these added as fields to the ConsumerVersionSelector model, but the others here https://github.com/jbwheatley/pact4s/issues/68 such as deployed and released aren't recommended to be strongly typed?

@jbwheatley I'm so sorry I never replied. This got lost in my never ending list of email alerts.


Error in deserializing FormCard type using load

Tested on versions: 0.12.1 and 0.13.0, works fine on 0.11.0
Running into deserialization on using FormCard.load(...).
Seems like, the error occurs when trying to deserialize FormCard.items which are serialized as a list of dictionaries into Component
Error
Traceback (most recent call last):
  File "/home/pramit/testing/q/apps/system/auto-insights/venv/lib/python3.7/site-packages/h2o_wave/server.py", line 278, in _process
    await self._handle(q)
  File "./.../ui/main.py", line 1591, in serve
    await handle_route(q)
  File "./.../ui/main.py", line 1527, in handle_route
    populate_previous_state(q)
  File "./.../ui/main.py", line 670, in populate_previous_state
    setattr(q.client, "insight_results", InsightResultsDoc.load(res[0]["data"]).res)
  File "./.../ui/doctypes.py", line 107, in load
    output[insight_type][card_id] = klass.load(card_data)
  File ".../venv/lib/python3.7/site-packages/h2o_wave/types.py", line 5754, in load
    _guard_vector('FormCard.items', __d_items, (Component,), False, False, True)
  File ".../venv/lib/python3.7/site-packages/h2o_wave/types.py", line 48, in _guard_vector
    _guard_scalar(f'{name} element', value, types, False, non_empty, False)
  File ".../venv/lib/python3.7/site-packages/h2o_wave/types.py", line 37, in _guard_scalar
    raise ValueError(f'{name}: want one of {types}, got {type(value)}')
ValueError: FormCard.items element: want one of (<class 'h2o_wave.types.Component'>,), got <class 'dict'>

https://github.com/h2oai/wave/blob/a543d41df837e9ba431653d8ea59cc9709287f72/py/h2o_wave/types.py#L5754

@pramitchoudhary - we can cut a 0.14 patch release if you want - let me know.


Crash when using SXSSFWorkbook:  ava.lang.NoClassDefFoundError: Failed resolution of: Ljava/awt/font/FontRenderContext;

SXSSFWorkbook is the Streaming version of XSSFWorkbook, It allows to write very large files without running out of memory as only a configurable portion of the rows are kept in memory at any one time.
This feature is quite relevant to Android where memory is not abundant.
https://poi.apache.org/apidocs/dev/org/apache/poi/xssf/streaming/SXSSFWorkbook.html
stack trace:
E/AndroidRuntime: FATAL EXCEPTION: main
    Process: org.dstadler.poiandroidtest.poitest, PID: 20594
    java.lang.NoClassDefFoundError: Failed resolution of: Ljava/awt/font/FontRenderContext;
        at org.apache.poi.ss.util.SheetUtil.<clinit>(SheetUtil.java:111)
        at org.apache.poi.ss.util.SheetUtil.getDefaultCharWidth(SheetUtil.java:271)
        at org.apache.poi.xssf.streaming.AutoSizeColumnTracker.<init>(AutoSizeColumnTracker.java:117)
        at org.apache.poi.xssf.streaming.SXSSFSheet.<init>(SXSSFSheet.java:82)
        at org.apache.poi.xssf.streaming.SXSSFWorkbook.createAndRegisterSXSSFSheet(SXSSFWorkbook.java:658)
        at org.apache.poi.xssf.streaming.SXSSFWorkbook.createSheet(SXSSFWorkbook.java:679)
        at org.apache.poi.xssf.streaming.SXSSFWorkbook.createSheet(SXSSFWorkbook.java:90)
        at org.dstadler.poiandroidtest.poitest.DocumentListActivity.writeWorkbook(DocumentListActivity.java:183)
        at org.dstadler.poiandroidtest.poitest.DocumentListActivity.onCreate(DocumentListActivity.java:72)
        at android.app.Activity.performCreate(Activity.java:7009)
        at android.app.Activity.performCreate(Activity.java:7000)

the issue can be easily replicated by modifying the method writeWorkbook() in DocumentListActivity.java of the piotest module. to the following:
private void writeWorkbook() throws java.io.IOException {
        Workbook wb = new SXSSFWorkbook(100);
        try {
            Sheet sheet = wb.createSheet("Sheet1");
            Row row = sheet.createRow(0);
            Cell cell = row.createCell(0);
            cell.setCellValue("cell-1");
            cell = row.createCell(1);
            cell.setCellValue("cell-2");
            cell = row.createCell(2);
            cell.setCellValue("cell-3");

            XSSFCellStyle style = (XSSFCellStyle) wb.createCellStyle();
            style.setFillBackgroundColor(new XSSFColor(new org.apache.poi.java.awt.Color(1, 2, 3)));

            Hyperlink link = wb.getCreationHelper().createHyperlink(HyperlinkType.URL);
            link.setAddress("http://www.google.at");
            link.setLabel("Google");
            cell.setHyperlink(link);

            cell.setCellStyle(style);

            sheet.setPrintGridlines(true);

            OutputStream stream = openFileOutput("test.xlsx", Context.MODE_PRIVATE);
            try {
                wb.write(stream);
            } finally {
                stream.close();
            }
        } catch (Exception e) {

            e.printStackTrace();

        } finally {
            wb.close();
        }
    }

I have now cherry-picked changes from https://github.com/LePat/poi-on-android/commit/d38372bd33860088c533f0838ee8830b3a945859 onto branch https://github.com/centic9/poi-on-android/commits/add_dummy_autosize to show how such missing classes from java.awt can be added.
But as the implementation just provides dummy implementations of the methods, I did not merge it into master. The resulting autosized column widths are far off and will not be useful unless a more sophisticated solution is implemented.
If you just want to get SXSSFWorkbook to work should be able to fetch these changes from there in your fork.
It can also serve as example of how to add a more useful implementation in the future.

The same issue is triggered by calling Sheet.autoSizeColumn(Int row), this also needs the FontRenderContext.
Thanks for adding the example of how to add implementations for missing classes!


Error compiling on Linux

Following your instructions I'm attempting to compile on my Fedora server and getting errors:
bakers@basement(~/github/Shox96)
:gcc -o shox96_0_2 shox96_0_2.c
shox96_0_2.c: In function ‘encodeCount’:
shox96_0_2.c:84:9: error: unknown type name ‘uint16_t’
   const uint16_t adder[7] = {0, 4, 36, 164, 676, 4772,  0};
		 ^~~~~~~~
shox96_0_2.c: In function ‘shox96_0_2_compress’:
shox96_0_2.c:204:9: error: unknown type name ‘uint16_t’
		 uint16_t to_lookup = c_in ^ in[l + 1] + ((in[l + 2] ^ in[l + 3]) << 8);
		 ^~~~~~~~
shox96_0_2.c: In function ‘readCount’:
shox96_0_2.c:362:9: error: unknown type name ‘uint16_t’
   const uint16_t adder[7] = {4, 0, 36, 164, 676, 4772,  0};
		 ^~~~~~~~
shox96_0_2.c: At top level:
shox96_0_2.c:507:28: error: unknown type name ‘uint8_t’
 int encode_unsigned_varint(uint8_t *buffer, uint64_t value) {
							^~~~~~~
shox96_0_2.c:507:45: error: unknown type name ‘uint64_t’
 int encode_unsigned_varint(uint8_t *buffer, uint64_t value) {
											 ^~~~~~~~
shox96_0_2.c:519:1: error: unknown type name ‘uint64_t’
 uint64_t decode_unsigned_varint(const uint8_t *data, int *decoded_bytes) {
 ^~~~~~~~
shox96_0_2.c:519:39: error: unknown type name ‘uint8_t’
 uint64_t decode_unsigned_varint(const uint8_t *data, int *decoded_bytes) {
									   ^~~~~~~
shox96_0_2.c: In function ‘decode_unsigned_varint’:
shox96_0_2.c:521:3: error: unknown type name ‘uint64_t’
   uint64_t decoded_value = 0;
   ^~~~~~~~
shox96_0_2.c:524:23: error: ‘uint64_t’ undeclared (first use in this function)
	 decoded_value |= (uint64_t)(data[i] & 0x7F) << shift_amount;
					   ^~~~~~~~
shox96_0_2.c:524:23: note: each undeclared identifier is reported only once for each function it appears in
shox96_0_2.c: In function ‘main’:
shox96_0_2.c:667:27: warning: implicit declaration of function ‘encode_unsigned_varint’ [-Wimplicit-function-declaration]
			 int len_len = encode_unsigned_varint((byte *) short_buf, clen);

Hi, Thank you for trying Shox96.  I have fixed the problem and found it working on Manjaro Linux.  It should be working on Fedora.  Please clone and try to compile again.
Please note Shox96 can only compress/decompress english text content.

That did indeed fix my problem compiling on Linux. Can you help me understand this output:
:./shox96_0_2 "Alas, poor Yorick! I knew him, Horatio"
42, -3, 113, -44, -123, 93, -7, 16, -3, -5, 0, 100, 127, 17, 98, 50, -42, 57, 7, -126, -50, -92, 65, -33, -86, 101, -101,
00101010 11111101 01110001 11010100 10000101 01011101 11111001 00010000 11111101 11111011 00000000 01100100 01111111 00010001 01100010 00110010 11010110 00111001 00000111 10000010 11001110 10100100 01000001 11011111 10101010 01100101 10011011
Alas, poor Yorick! I knew him, Horatio

len: 27/38=28.95

Elapsed:0

I'm guessing the 27 is how many bytes it compressed the original 38 down to? Saving 28.95%?

Yes, you are right..  This was code I used to verify the concept.  So I didn't put in too much descriptions.
I have given more descriptions, explanations, examples and screenshots in the projects in which the concept is used:
https://github.com/siara-cc/Shox96_Arduino_Progmem_lib
https://github.com/siara-cc/Shox96_Sqlite_UDF
https://github.com/siara-cc/esp32_arduino_sqlite3_lib
https://github.com/siara-cc/esp_arduino_sqlite3_lib
You might find the Proverbs example in the first project interesting :-)

The elapsed always shows 0. Is that seconds? Milliseconds?

It is in seconds. Only useful when you compress large files. I should probably remove it because Shox96 is meant for Short Strings.  For large files there are so many compressors available.
FYI, at first it displays the decimal representation of the compressed data (data type char[]).
Then the binary representation follows.
Then it displays the ratio and percentage.
Finally it displays the time taken.

Would it be possible to show the elapsed time in milliseconds? That would be good to know when comparing different encodes.

I have modified to show in milliseconds, along with other desc.  I am not sure if it is useful as it includes the time to show the descriptions.
Also, please note that the decompressor is not built for speed, but is built to consume less memory to run under 2kb (Arduino).  Usually a lookup table of atleast 256 bytes would be necessary to make it comparable with other decompressors - I have not give it much thought.

Thanks for addressing this so quickly!

esp_arduino_sqlite3_lib-master\src\shox96_0_2.cpp:365:61 error: 'adder' was not declared in this scope
int count = getNumFromBits(in, *bit_no_p, bit_len[idx]) + adder[idx];


lcase not supported?

Hello there,
I am trying to run the following query:
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
SELECT DISTINCT ?s ?type ?label (GROUP_CONCAT(?definition; SEPARATOR="\n") AS ?definitions) (GROUP_CONCAT(?altlabel; SEPARATOR="\n") AS ?altlabels) WHERE {
    ?s rdf:type ?type ;
       skos:prefLabel ?label.
    OPTIONAL {?s skos:definition ?definition.}
    OPTIONAL {?s skos:altLabel ?altlabel.}
    FILTER regex(?label, "position", "i")
}
GROUP BY ?s ?type ?label ?definition

which runs fine, but as soon as I add an LCASE(?label), I get an error "Invalid SPARQL query: REGEX expressions are currently supported only on variables." Which surprises me since this query runs fine - and correctly - on GraphDB.
I see in the features https://github.com/ad-freiburg/qlever/wiki/Current-deviations-from-the-SPARQL-1.1-standard that LCASE is supported.  Is that incorrect or am I doing something else wrong?
Query with LCASE:
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
SELECT DISTINCT ?s ?type ?label (GROUP_CONCAT(?definition; SEPARATOR="\n") AS ?definitions) (GROUP_CONCAT(?altlabel; SEPARATOR="\n") AS ?altlabels) WHERE {
    ?s rdf:type ?type ;
       skos:prefLabel ?label.
    OPTIONAL {?s skos:definition ?definition.}
    OPTIONAL {?s skos:altLabel ?altlabel.}
    FILTER regex(LCASE(?label), "position", "i")
}
GROUP BY ?s ?type ?label ?definition

The error messages says that you can only regex expressions on variables directly. LCASE is supported. What you do as a workaround is to bind your expression to a new variable and then apply the regex on that new variable.
This could look something like this:
    BIND (LCASE(?label) as ?label_lcase) .
    FILTER REGEX(?label_lcase, "position", "i")

We should probably document this on the wiki page that you also found. @joka921 what are the details of the constraint here?

@rmfranken @Qup42 It's exactly as the error message says: Currently, the first argument of the REGEX has to be a variable. Arbitrary expressions are not supported yet, but you can trivially simulate that by introducing an additional BIND(expression AS ?regex_var). It's one of the things that we "just" need to implement and it's on our list :-)

Thanks! Clear!


1drv.ms still on domains.list but not found in the backend

I already wrote about that http://1drv.ms/ is a redirect service for microsoft office shares. It was whitelisted after (I cannot find the issue).
I cannot find the domain with https://hosts.ubuntu101.co.za/app/contents/ in the backend but it's still in the domains.list
Something is wrong there...

Something is wrong there...

The search is buggy sometimes and it doesn't show any results for some reason.
It's working now and it found the domain in two of the lists here:

Oh thank you very much!


For 61 Tag

Sir, it's works fine. But I want parse 61 tag what should i do in this case? When i pass 61 tag it will through error.

i solve it


proxy: Use the same proxy map size as in BPF

Fixes: #3440
Fixes: #3472
Fixes: #3483
Signed-off-by: Romain Lenglet<EMAIL_ADDRESS>

test-me-please

Added reference to #3440 in the description

I broke this, sorry 😢

test-me-please

test-me-please

test-me-please

2 clean builds:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/1947/
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/1950/
Rebasing.

test-me-please

Unrelated conntrack test failure:
04:19:24 RuntimeValidatedConntrackTest
04:19:24 /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:238
04:19:24   Conntrack-related configuration options for endpoints [It]
04:19:24   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:270
04:19:24
04:19:24   The result of "curl -s --fail --connect-timeout 5 --max-time 5 http://[f00d::a0f:0:0:56ec]:80" from container "curl" to httpd1 does not match
04:19:24   Expected
04:19:24       <bool>: false
04:19:24   to be true
04:19:24
04:19:24   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/runtime/connectivity.go:649

test-me-please

test-me-please

CI infrastructure failure:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/1960/
Required context class hudson.FilePath is missing
Perhaps you forgot to surround the code with a step that provides this, such as: node

test-me-please

And again, failing in 3 seconds:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/1961/
Required context class hudson.FilePath is missing
Perhaps you forgot to surround the code with a step that provides this, such as: node

test-me-please

test-me-please

test-me-please

test-me-please


Upgraded NumSharp to 0.20.2

@kerryjiang, Is it ok to upgrade NumSharp to 0.20.2, no breaking changes in your project (TFHub) and compiles successfully.

I am fine with the part about TensorflowHub


No QSPI support for memories

Some of the features that would be required to communicate with memories over QSPI (instructions, dummy cycles..) are not supported

I'm wanting to interface with 25LP064 QSPI flash memory and so I'm hoping my efforts can help this HAL.
I'm wondering if you all have any advice for the API for this?
Would it make sense to add instruction: Option<u8> to read and write and mode: Option<u8> to read (I haven't seen mode in write)?
I'm assuming I can update the imode value based on the value set in admode ?

I've started implementing some new methods for interfacing with OCTOSPI flash memories, and these are probably applicable to QSPI also. I'll make a PR with the progress so far..

In the example in that PR there's an instruction with no address and no data phases (line 80), as well as an instruction with both address and data phases (line 84).
It should be close to working for QSPI memories also, but I've not tried it. If there's only small changes needed to work with the 25LP064, that would be very useful to know.

In the example in that PR there's an instruction with no address and no data phases (line 80), as well as an instruction with both address and data phases (line 84).
It should be close to working for QSPI memories also, but I've not tried it. If there's only small changes needed to work with the 25LP064, that would be very useful to know.

Great @richardeoin I'll give this a go soon.
Longer term, I'm guessing the original read/write would need to be altered to correctly do the setup_extended.. if they're not removed entirely?


TypeError When dealing with link clicks via Capybara::Session

Meta
Poltergeist Version: 1.6.0/1.18.1
(Tried both, saw issues with both)
Expected Behavior
I am attempting to confirm the correct function of a link with target="_blank" by switching to the window opened up when clicking the link, then checking the current_url. This should return the url opened by clicking the link.
Actual Behavior
In reality, I am getting the following error when attempting to switch_to_window:
Failure/Error: switch_to_window(new_window)

     Capybara::Poltergeist::JavascriptError:
       One or more errors were raised in the Javascript code on the page. If you don't care about these errors, you can ignore them by setting js_errors: false in your Poltergeist configuration (see documentation for details).

       TypeError: Attempting to configurable attribute of unconfigurable property.
       TypeError: Attempting to configurable attribute of unconfigurable property.
           at https://www.gstatic.com/recaptcha/api2/v1562567553145/recaptcha__en.js:5 in defineProperty
           at https://www.gstatic.com/recaptcha/api2/v1562567553145/recaptcha__en.js:5 in fZ
           at https://www.gstatic.com/recaptcha/api2/v1562567553145/recaptcha__en.js:16

If I attempt the switch_to_window in binding.pry, it gives this error code, but actually seems to process switching windows, since afterwards I can check current_url and get the correct result and a passing test.
Since I ran into this with versions 1.6.0 and 1.18.1, I decided to try to work around this by executing some javascript to reset the links' target to "self". After this workaround, when testing the specs involved individually, they typically pass. However, when I run the entire file of specs, they fail locally. They do pass in our CI process, though.
If this is an error in something in my implementation, please let me know.
Steps to reproduce
Here is the code I attempt:
new_window = window_opened_by { row_to_click.click_link }
sleep 3

switch_to_window(new_window)
expect(current_url).to include anticipated_url # use include in case routing adds path to root url

Here is my 'workaround' code:
before do
  execute_script("$('.link-to-click').each(function() {$(this).attr('target', '_self');})")
end

scenario 'the user is redirected to the correct path' do
  row_to_click.click_link
  sleep 3 # wait for event logging

  expect(current_url).to include anticipated_url # In case link redirects to more specific path
end

You're getting errors from the JS in the page you're loading.  PhantomJS (which Poltergeist depends on) went EOL a while ago and does a pretty terrible job of replicating a modern browser nowadays,  so there's a lot of JS libraries that are no longer compatible with it.  Thats a large part of the reason Poltergeist is no longer maintained.  You will have a better time if you upgrade to one of the newer, more modern browser using drivers - https://github.com/teamcapybara/capybara#drivers

Thanks for this feedback!


Fix merge script join bug

While running the merge workflow to help prepare to write docs, it had an error in the merge script. Here, I've found and fixed the bug!
The dplyr::left_join() code was using relationship = "one-to-one", but this means only 1 row should match between data frames. Instead, we expect one row in y to match many rows in x. So, I changed this to relationship = "many-to-one" and (edit, typo) the script to works now locally!
Here are left_join docs for reference:  https://dplyr.tidyverse.org/reference/mutate-joins.html
I'm re-running the workflow now to double check it works, but wanted to get this filed since I have a quick appointment to head out for (be back in about an hour or so).
Noting this original context for the dplyr code: https://github.com/AlexsLemonade/scpca-nf/pull/630#discussion_r1439704871
Also, I fixed a little purrr code to return a logical vector so R doesn't throw a warning about coercing it from a list to logical vector.

Everyone ignore https://github.com/AlexsLemonade/scpca-nf/pull/652/commits/9979c1c276349cbf27f097584aecdaa8c434020d and https://github.com/AlexsLemonade/scpca-nf/pull/652/commits/4deee3761eee9a9c8b5ecff2998978cdb8ffb719 🥴

Thanks for catching this 🚀

There are more bugs, testing fixes now... you'll be sad... But next commit is nearly incoming!

Two more fixes in https://github.com/AlexsLemonade/scpca-nf/pull/652/commits/14ed3643a71433d6360e720e8494bf4cda1ef3b6 and https://github.com/AlexsLemonade/scpca-nf/pull/652/commits/1788591a30bf9ed6580250f8fb00347e8f88bf57. In the main QC report, the SCEs we pass in are actual SCEs, but not so here! Have to read in.

Noting that SCPCP000001 ran to completion, but with this warning. Looks like the filter code to remove multiplex isn't working since there are two false's?
WARN: Input tuple does not match input set cardinality declared by process `export_anndata` -- offending value: [/nextflow-ccdl-data/work/f5/e77aefb0863692784f13d98712bd86/SCPCP000001_merged.rds, SCPCP000001, false, false]

I think we can change...
    // export merged objects to AnnData
    anndata_ch = merge_sce.out
      .filter{!it[3]} // remove multiplexed samples before export
      .take(3) // keep everything but multiplexed

--->
    // export merged objects to AnnData
    anndata_ch = merge_sce.out
      .take(3) // keep everything but multiplexed

since multiplexed is the 4th anyways?
merge_sce emits:
tuple path(merged_sce_file), val(merge_group_id), val(has_adt), val(multiplexed)

Ok, take doesn't seem to be working. I don't know what the deal there is? Going to come back to this tomorrow!
merge_sce.out.view()

// export merged objects to AnnData
anndata_ch = merge_sce.out
     .take(3) // keep everything but multiplexed

anndata_ch.view()

--->
[/nextflow-ccdl-data/work/eb/4115cff62aee5e5279760282a3a037/SCPCP000001_merged.rds, SCPCP000001, false, false]

[/nextflow-ccdl-data/work/eb/4115cff62aee5e5279760282a3a037/SCPCP000001_merged.rds, SCPCP000001, false, false]

Ok, take doesn't seem to be working. I don't know what the deal there is? Going to come back to this tomorrow!
merge_sce.out.view()

// export merged objects to AnnData
anndata_ch = merge_sce.out
     .take(3) // keep everything but multiplexed

anndata_ch.view()

I think the issue is that .take() in the context here is acting on the channel, so it is taking the first three channel elements, not the first three elements of the list. I think we want .map{it.take(3)}
So:
 // export merged objects to AnnData
    anndata_ch = merge_sce.out
      .filter{!it[3]} // remove multiplexed samples before export
      .map{it.take(3)} // keep everything but multiplexed

Ok, this approach definitely works:
 // export merged objects to AnnData
    anndata_ch = merge_sce.out
      .filter{!it[3]} // remove multiplexed samples before export
      .map{it.take(3)} // keep everything but multiplexed

But I'm not understanding why we need both filter and take?
The "before/after" is the same with and without filter. My sense was filter was left over from before we added take, but is there something I'm missing?
[/nextflow-ccdl-data/work/86/5d9a4c0a34d1b2d51702a6b64d2b3f/SCPCP000001_merged.rds, SCPCP000001, false, false]
[/nextflow-ccdl-data/work/86/5d9a4c0a34d1b2d51702a6b64d2b3f/SCPCP000001_merged.rds, SCPCP000001, false]

But I'm not understanding why we need both filter and take?
The "before/after" is the same with and without filter. My sense was filter was left over from before we added take, but is there something I'm missing?

filter is removing the channel elements that are multiplexed. map{take} is removing the 4th element from the non-multiplexed samples for the next step.

thanks @jashapiro !

SCPCP000001 has run to completion, but SCPCP000003 is still chugging along. It's exported the RDS, but still waiting on anndata because files are BIG. But I'm feeling confident that bugs have all been squashed, so going to re-request review now!


Added task4.txt

Issue: #5
Created new directory and created new file in it

Hey @Asheeesh9
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @Asheeesh9
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


I can't use commas nor dots to enter numbers

When I'm entering a new product, when I want to modify nutrition facts:

if I enter numbers with dots, when validating it says I can't (fields become red with "Numéro incorrect")
if I try to use commas, selecting comma on the keyboard does nothing

To ease the use, it should accept either commas either dots (the numbers are normalized on the server side).

We should allow both comma and dots as some phone number-keyboards just allow one of them

Looks great @g123k

My remarks:

it looks like again another external package, which I'm not very fan of.
the instant correction is cool.
2 keys for the comma is problematic (especially when in some countries you can use both ',' and '.', e.g. 1 ,200.45)
keys '-' and '_' mean nothing in our case.
the keyboard input is not enough: we must check that the value is correctly understood downhill.

On the website we use the hyphen (-) to tell that the value is not on the product. For example, it is really useful to tell that there is no fiber value printed on the packaging: in some case that does not mean there is no fiber, but only that the producer didn't print it.
See https://github.com/openfoodfacts/openfoodfacts-server/issues/1938
Should I open a new bug for this?

Yes, please open a new one @CharlesNepote


chore(main): release cli 1.1.3

:robot: I have created a release beep boop
1.1.3 (2024-06-03)
Bug Fixes

select option has white text and bg (aae178a), closes #40

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/flexydox/flexydox/releases/tag/cli%40v1.1.3 :sunflower:


[0.5/mtl] fix issue with fill_buffer when using offset and size

Port of #3248

bors r+

@grovesNL let's get this also before releasing


onnx result wrong

Hi, Thanks for your work. Recently I retrain U2net for my task and export onnx. The export code as follows:
model = U2NET(3, 1)
state_dict = torch.load("u2net_bce_itr_12000_train_0.127958_tar_0.012812.pth")
model.load_state_dict(state_dict)

model.eval()

input_names = ["input"]
output_names = ["output"]
input_tensor = torch.zeros([1, 3, 320, 320])

# I change the network to get 1 output: d1
torch.onnx.export(model,
                  input_tensor,
                  "human_seg.onnx",
                  opset_version=12,
                  export_params=True,
                  verbose=True,
                  input_names=input_names,
                  output_names=output_names,
                  dynamic_axes={"input": {0: "batch"},
                                "output": {0: "batch"}})

After successfully export onnx, I try to infer an image with onnx. The preprocess code as follows, but the result is wrong.
image = io.imread("xiaozheng.png")
size = (image.shape[1], image.shape[0])
bg = np.ones_like(image) * 255

src = transform.resize(image, (320, 320), mode='constant')

mean = np.array([0.485, 0.456, 0.406])
std = np.array([0.229, 0.224, 0.225])
src = src / np.max(src)
src = src - mean
src = src / std

src = np.transpose(src, [2, 0, 1])
src = np.expand_dims(src, 0)
src = src.astype(np.float32)

sess = onnxruntime.InferenceSession("human_seg.onnx")
d1 = sess.run([], {"input": src})[0]

Thanks for your help!
save_result func, I comment the "255".  Speechless, I am so, emmm.

@NingNanXin I have the same problem. Did you solve this?

@NingNanXin I have the same problem. Did you solve this?

Debug your preprocess and post-process, use torch.onnx.export() can get the right onnx model.

@NingNanXin Thanks for your reply. Can you explain more detail? How did you solve that?

@ducnguyen998

use a random generate image as an input
use torch and onnx to infer your image
use numpy.testing.assert_allclose to compare torch result and onnx result
For me, 3 is right, then compare your process code with the origin code

@NingNanXin Thank you.
I have my own model that produces accurate results when run in PyTorch format. However, when I convert it to ONNX format, the model gives incorrect results. I attempted to convert the author's pre-trained model to ONNX, and it successfully produced the same results as the PyTorch model. However, when I applied the same process to my own model, it did not work as expected.


Openapi generator

Description
add OpenAPI Generator

@eidottermihi @darenegade I'm not sure if the link to the github search makes sense, what do you think?

From my point of view, it makes no sense, as the search is less structured and offers no added value to those interested in open source.


x/telemetry/config: enable data collection for crash/* counters, for gopls

Counter names
crash/crash
crash/malformed
crash/no-running-goroutine
Description
crash/crash - compressed stack traces of running goroutines from unexpected crashes
crash/malformed - counter of failures to parse the stack trace
crash/no-running-goroutine - counter of stack traces that have no goroutine in "running" state (e.g. deadlock, lossy parse)
Rationale
The crash/crash stack counters are how we detect unexpected crashes (for any reason) in gopls, and any other Go-project tool that uses x/telemetry/crashmonitor. This helps us diagnose and fix bugs speedily, and assess their severity.
Do the counters carry sensitive user information?
No. In particular, the compressed stacks are generated by joining a list of program counters with the executable's symbol table, so there is no possibility of application data values being incorporated.
How?
https://pkg.go.dev/golang.org/x/telemetry/crashmonitor
Proposed Graph Config
(https://go.corp.google.com/go-telemetry-configuration)
counter: crash/crash
title: Unexpected Go crashes
description: stacks of goroutines running when the Go program crashed
type: stack
program: golang.org/x/tools/gopls
depth: 16
version: v0.15.0

counter: crash/malformed
title: Failure to parse runtime crash output
description: count of runtime crash messages that failed to parse
type: counter
program: golang.org/x/tools/gopls
version: v0.15.0

counter: crash/no-running-goroutine
title: Failure to identify any running goroutine in the crash output
description: count of runtime crash messages that don't have a running goroutine (e.g. deadlock)
type: counter
program: golang.org/x/tools/gopls
version: v0.15.0

New or Update
New

Thanks. Accepted in our meeting this afternoon. I think the type field needs to be histogram, but that is superficial.


Blob store assertion check

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Failing tests:
org.opensearch.repositories.url.URLRepositoryTests.testNonNormalizedUrl
org.opensearch.repositories.url.URLRepositoryTests.testIfNotAllowListedMustSetRepoURL
org.opensearch.repositories.url.URLRepositoryTests.testAllowListingRepoURL
org.opensearch.repositories.url.URLRepositoryTests.testMustBeSupportedProtocol
org.opensearch.repositories.s3.S3RepositoryTests.testDefaultBufferSize

Commenting out these tests to check if there are any further failures.


No configuration cache-compatible alternative to Project.configure is available

The Project class has a family of methods that allow simpler configuration of arbitrary objects:

configure(Object object, Closure configureClosure)
configure(Iterable<?> objects, Closure configureClosure)
configure(Iterable<T> objects, Action<? super T> configureAction)

These methods can have some uses even at the execution time. However, as these are provided by the Project instance, calling any of the methods at the execution time is not compatible with the configuration cache. There is no compatible alternative.
Groovy's built-in tap method has similar semantics, but configure has some Gradle-specific logic, so the former might not be a suitable replacement for all cases. However, our documentation suggests using apply as a replacement for Kotlin DSL, which has the same semantics as tap.
This issue is making the doc snippet snippet-tutorial-configure-object_groovy_configureObject.sample incompatible with the configuration cache.

#22042 fixes the snippet, but this issue may still be worth looking into.


fix(app): application won’t open on some users

:tada: This PR is included in version 2.76.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Store is undefined when nesting in require (require.js)

Having some issues where I try to load store.js through require.js and the result is that it differs from site to site (I am creating a bookmarklet). I am using the list of sites from here. https://github.com/jrburke/requirejs/wiki/Sites-using-RequireJS.
bbc.com and fool.com works, but the other ones (http://www.rtt.ag/en, http://www.usatoday.com/, http://www.hallmark.com/easter/ideas/easter-recipes/) are inconsistent. For example, sometimes the jquery is unavailable, sometimes the qtip is unavailable, sometimes store is unavailable.
if (window.require) {
    requirejs.config({
        paths: {
            jq: '//cdnjs.cloudflare.com/ajax/libs/jquery/1.8.2/jquery.min',
            qtip2: '//cdnjs.cloudflare.com/ajax/libs/qtip2/2.2.0/jquery.qtip',
            json2: '//cdnjs.cloudflare.com/ajax/libs/json2/20130526/json2.min',
            jstore: '//cdnjs.cloudflare.com/ajax/libs/store.js/1.3.14/store.min'
        },
        map: {
            'qtip2': { 'jq': 'jquery-private' },
            'json2': { 'jq': 'jquery-private' }
        },
        findNestedDependencies: true
    });

    define('jquery-private', ['jq'], function () {
        return jQuery.noConflict(true);
    });

    require(['jstore'], function(store){
        require(['jquery-private', 'qtip2', 'json2'], function (jay) {
            console.log(store);
            console.log(jay);
            qtip2Initializer(jay,store);

        });
    });

}

function qtip2Initializer(jay,store) {
    console.log(jay().jquery);
    // Your logic to execute when qTip2 is available
    jay(document).ready(function () {
      $('a').qtip();
      store.set("test",1);
    });
}

This may very well have been solved by 7c65e0a646c9c4743. @kgust, can you please verify and/or close?
Thanks for the patience!

This may very well have been solved by 7c65e0a646c9c4743. @whatsdis, can you please verify and/or close?
Thanks for the patience!

Feel free to reopen with more info.


Build failed

Build: https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_build/results?buildId=249119
Changes: https://github.com/Microsoft/vscode/compare/2feabcd...f9f1eaa
Related Test:
https://github.com/microsoft/vscode/blob/main/src/vs/editor/test/common/model/textModel.test.ts#L171
Seeing this test time out issue in recent builds often.
https://dev.azure.com/monacotools/Monaco/_build/results?buildId=249101&view=results

Usually these tests should run quite fast, probably the agent had a heavy load which caused the timeout.

Another on with similar timeouts and they're happening pretty frequently:
https://dev.azure.com/monacotools/Monaco/_build/results?buildId=249263&view=logs&j=55ac390b-ffb1-50ea-3650-525dd9a3fd80&t=c01b9029-2b08-503e-eba8-b45cf5956c33
Related test:
https://github.com/microsoft/vscode/blob/main/src/vs/editor/test/node/diffing/fixtures.test.ts#L16